View Single Post
Old 01-04-2013, 08:22 AM   #7
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by ixtab View Post
You could create an init script which periodically reads the output of dmesg and/or showlog, reformats it and uses eips to draw it on the screen. You'll still need to get rid of the original boot screen, but that's (probably) just disabling a few lines in other init files.
You need to filter what you send to eips to remove characters that make it fail. One of my published scripts did that (an early attempt at a simple, text-only onscreen terminal).

For early boot messages, you would need to add your code to the initial ramdisk in the kernel partition.
geekmaster is offline   Reply With Quote