Date: Fri, 25 Jul 2003 13:04:40 -0700
From: Mike Fedyk <mfedyk@matchmail.com>
To: Jurriaan <thunder7@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cutting down on boot messages
Message-ID: <20030725200440.GA1686@matchmail.com>
Mail-Followup-To: Jurriaan <thunder7@xs4all.nl>,
	linux-kernel@vger.kernel.org
References: <20030725195752.GA8107@middle.of.nowhere>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030725195752.GA8107@middle.of.nowhere>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 920
Lines: 20

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).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/