From: Jeff Dike <jdike@addtoit.com>
To: Rob Landley <rob@landley.net>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Blaisorblade <blaisorblade@yahoo.it>
Subject: Re: [uml-devel] Triage on the pending patches
Date: Thu, 03 Mar 2005 13:43:48 -0500 [thread overview]
Message-ID: <200503031844.j23IhmDS003473@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 03 Mar 2005 00:08:51 EST." <200503030008.51336.rob@landley.net>
rob@landley.net said:
> Well, just in case your job was too easy, here's one more. Using the
> "quiet" option shows a couple of lines being printed out by printf
> that should be printed out by printk (so they'll _shut_up_ when you
> ask it to).
Those are printfs for a reason. Early boot mesages (before the kernel is
actually running) won't be seen if they are printk-d and the thing crashes
before the console is initialized. The messages will be stuck in the printk
buffer, and you will be none the wiser.
So, they can be made quiet if you really want, but that's not the way.
Jeff
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-03-03 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 8:22 [uml-devel] Triage on the pending patches Jeff Dike
2005-03-03 5:08 ` Rob Landley
2005-03-03 18:43 ` Jeff Dike [this message]
2005-03-04 2:11 ` Rob Landley
2005-03-05 15:57 ` Blaisorblade
2005-03-06 19:59 ` Rob Landley
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=200503031844.j23IhmDS003473@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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