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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 20 Dec 2009 13:29:37 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	jidanni@...anni.org
CC:	561764@...s.debian.org, linux-kernel@...r.kernel.org,
	561229@...s.debian.org
Subject: Re: Bug#561764: some warnings fly off screen and are not saved in
 any file

On 12/20/2009 11:39 AM, jidanni@...anni.org 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?".
>
> 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..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/