[Josh Triplett] > Not concerned about the util-linux bug here. bootlogd should start as > early as possible, to capture as many of the boot messages as possible.
I agree that it should run as early as possible, but there are a lot of dependencies to take into account. :) > Of those, only mountdevsubfs and its dependencies udev and > mountkernfs *need* to start before bootlogd. Right. I could push it a bit further by adding more scripts to X-Start-Before. I can also make sure it run alone and sometimes a bit earlier by adding the Interactive flag, but am not sure it make sense. > Then again, does bootlogd even work with parallel init scripts? If > not, feel free to chalk this bug up to "need replacement for > bootlogd". Hopefully the replacement will log starting from the > beginning of the boot process. Bootlogd seem to work just fine with parallel booting, so I believe it is no need for that. If it can't run well with other scripts running at the same time, the 'X-Interactive: true' flagg need to be added. Try to modify your /etc/init.d/bootlogd script, modifying the header to have these entries: # X-Start-Before: keymap keyboard-setup procps pcmcia hwclock hwclockfirst hdparm To activate the change with dependency based boot sequencing, run 'insserv -v'. Did it help, and is it still working for you? If so, I will add more scripts to the X-Start-Before header in init.d/bootlogd. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
