From: Robert Hancock <hancockrwd@gmail.com>
To: jidanni@jidanni.org
Cc: 561764@bugs.debian.org, linux-kernel@vger.kernel.org,
561229@bugs.debian.org
Subject: Re: Bug#561764: some warnings fly off screen and are not saved in any file
Date: Sun, 20 Dec 2009 13:29:37 -0600 [thread overview]
Message-ID: <4B2E7B21.4070907@gmail.com> (raw)
In-Reply-To: <87skb5zgri.fsf@jidanni.org>
On 12/20/2009 11:39 AM, jidanni@jidanni.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..
prev parent reply other threads:[~2009-12-20 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-20 17:39 Bug#561764: some warnings fly off screen and are not saved in any file jidanni
2009-12-20 19:29 ` Robert Hancock [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B2E7B21.4070907@gmail.com \
--to=hancockrwd@gmail.com \
--cc=561229@bugs.debian.org \
--cc=561764@bugs.debian.org \
--cc=jidanni@jidanni.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox