From: Mike Fedyk <mfedyk@matchmail.com>
To: Jurriaan <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cutting down on boot messages
Date: Fri, 25 Jul 2003 13:04:40 -0700 [thread overview]
Message-ID: <20030725200440.GA1686@matchmail.com> (raw)
In-Reply-To: <20030725195752.GA8107@middle.of.nowhere>
On Fri, Jul 25, 2003 at 09:57:52PM +0200, Jurriaan wrote:
> of messages? I'm now at 22k of dmesg, including raid, usb, apic etc, for
> a single CPU system.
And you want more static buffers to store that in than now? Many people
won't like that.
You'd do better to have a boot time command line option to limit printk
messages to err, or above. Most of the printk messages have been given a
severity already, so this shouldn't be a problem, and it will probably
uncover some errors in the severity of certain messages.
Anyway, there are other ways to peel this union, including having the
messages to to tty2 instead of console (I've seen patches for this posted
before).
next prev parent reply other threads:[~2003-07-25 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 19:57 cutting down on boot messages Jurriaan
2003-07-25 20:04 ` Mike Fedyk [this message]
2003-07-25 21:09 ` Krzysztof Halasa
2003-07-25 21:43 ` Kurt Wall
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=20030725200440.GA1686@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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