In article <[EMAIL PROTECTED]>, Colin Watson <[EMAIL PROTECTED]> wrote: >Decklin Foster <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: >>Cesar Eduardo Barros <[EMAIL PROTECTED]> writes: >>> There are too many boot messages, and they sometimes scroll too >>> fast. It would be nice to log all the output from the boot scripts. >> >>Huh? does dmesg not do what you want? > >dmesg doesn't log the output from init.d scripts. >(I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).)
Have a look at "bootlogd" from sysvinit. It isn't installed by default since it's not quite finished yet, but I think it does what you want. It captures all screen output while booting and keeps it in memory until it is able to write to /var/log/boot.log. Needs no special support, hacked scripts etc. The reason that it isn't used yet is that I'm not sure it actually is a good idea - it wouldn't work with a 'pretty startup' like RedHat has, for example. I'm not quite sure what exactly the best way to solve this is. Most probably extending /etc/init.d/rc and /etc/init.d/rcS, which need a rewrite anyway to get merged into 1 script. But we do need some way to store the messages produced when the root filesystem is still read only and/or /var isn't mounted yet. So it's not a trivial problem. Mike. -- "en daarom zoeken wij voor de uitbreiding van de it-afdeling een vrolijke, hard werkende, enthousiaste systeembeheerder! lijkt dit je wat, reageer dan nu!" -- marleen in nl.susy
