linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Wall <kwall@kurtwerks.com>
To: Jurriaan <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cutting down on boot messages
Date: Fri, 25 Jul 2003 17:43:51 -0400	[thread overview]
Message-ID: <20030725214351.GG28205@kurtwerks.com> (raw)
In-Reply-To: <20030725195752.GA8107@middle.of.nowhere>

Quoth Jurriaan:
> If I boot my system, there are copious messages. 
> 

[...]

> Now these messages are often uninteresting - but sometimes they are.
> So just deleting them, or requiring a recompile or reboot is not good
> enough.
> Also, I noted that these messages were almost always grouped together.
> 
> Suppose these messages were removed from the normal output, but instead
> stored in a buffer in the kernel.

How about the "quiet" kernel command line parameter, which quiets
down the boot process but still stores the messages in the ring
buffer?

Kurt
-- 
Support bacteria -- it's the only culture some people have!

      parent reply	other threads:[~2003-07-25 21:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 19:57 Jurriaan
2003-07-25 20:04 ` Mike Fedyk
2003-07-25 21:09   ` Krzysztof Halasa
2003-07-25 21:43 ` Kurt Wall [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=20030725214351.GG28205@kurtwerks.com \
    --to=kwall@kurtwerks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder7@xs4all.nl \
    --subject='Re: cutting down on boot messages' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).