Re: bootlog starting late
On Dec 12, 2006, at 10:54 AM, Wu-Kung Sun wrote:
Hi list,
Bootlogd was fine in sarge but when I updated to etch about a month
ago it doesn't capture nearly as much as it used to. Judging by what
I'm able to see in dmesg, about 75% of the messages appear in dmesg
and the last 25% appear in /var/log/boot. In /etc/rcS.d there is
S05bootlogd.
What is happening here?
In Sarge, the first few things in /etc/rcS.d are
S02mountvirtfs
S04udev
S05bootlogd
S05initrd-tools.sh
S05keymap.sh
S10checkroot.sh
But in Etch, the first few things are
S01glibc.sh
S02hostname.sh
S02mountkernfs.sh
S03udev
S04mountdevsubfs.sh
S05bootlogd
S05keymap.sh
S07hdparm
S10checkroot.sh
In Sarge, bootlogd is one of the very first things that gets done.
In Etch there's a lot of (interesting) stuff that gets done before
bootlogd starts up.
Does anybody know if this is deliberate? Has anybody tried changing
S05bootlogd to (say) S02boologd ? What happened when you did?
Does anybody know enough about the early boot process to say
definitively what would break if this were done?
Rick
Reply to: