Skip to contentSkip to conversation

Bug#561764: some warnings fly off screen and are not saved in any file

DISCUSSION [email protected] 2 participants 2 messages Dec 20, 2009

lore
Share & tools
lore
#0 lore raw

OK, via

$ zcat /boot/initrd.img-2.6.32-trunk-686|strings|less
I think I found one of the messages I saw:
SYSFS{}= will be removed in a future udev version
which is in /sbin/udevadm ... bug #561229 perhaps.

However, what I'm saying is "how bad it is that there be any messages that fly off the screen at boot and are not also 'remembered into some log file' one can read later?".

Either remember all messages into those /var/log/ files, or remember none. Remembering 95% makes one think that they see all of them.

There is some step so early in the boot process that recording has not been turned on yet. That step is making error messages that fly off the screen... with only one small laptop one is not going to be able to see these messages. One should not be required to attach other equipment to see them.

#1 lore raw
Quoted 10 lines · On 12/20/2009 11:39 AM, [email protected] wrote:

OK, via

$ zcat /boot/initrd.img-2.6.32-trunk-686|strings|less
I think I found one of the messages I saw:
SYSFS{}= will be removed in a future udev version
which is in /sbin/udevadm ... bug #561229 perhaps.

However, what I'm saying is "how bad it is that there be any messages that fly off the screen at boot and are not also 'remembered into some log file' one can read later?".

Quoted 7 lines

Either remember all messages into those /var/log/ files, or remember none. Remembering 95% makes one think that they see all of them.

There is some step so early in the boot process that recording has not been turned on yet. That step is making error messages that fly off the screen... with only one small laptop one is not going to be able to see these messages. One should not be required to attach other equipment to see them.

Not sure why this is CCed to LKML, the kernel isn't responsible for logging anything to files..