From: Chuck Ebbert <76306.1226@compuserve.com>
To: Randy Dunlap <rddunlap@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Roman Zippel <zippel@linux-m68k.org>
Subject: [PATCH] Wanted: a limit on kernel log buffer size
Date: Tue, 8 Apr 2003 00:42:26 -0400 [thread overview]
Message-ID: <200304080045_MC3-1-3378-3CDB@compuserve.com> (raw)
Randy Dunlap wrote:
>Here's a [modified] patch that limits kernel log buffer size
>to 1 MB max and 4 KB min.
That's even better.
Maybe the kernel config system could just use multi-choice,
something like this?
( ) 8K
( ) 16K
( ) 32K
( ) 64K
( ) 128K
( ) 256K
A subset of your larger range should be enough, and this
would be less prone to user error.
--
Chuck
<insert witty statement here>
next reply other threads:[~2003-04-08 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 4:42 Chuck Ebbert [this message]
2003-04-08 4:52 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2003-04-07 1:34 Chuck Ebbert
2003-04-07 2:49 ` Randy.Dunlap
2003-04-07 3:35 ` Randy.Dunlap
2003-04-07 23:17 ` [PATCH] " Randy.Dunlap
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=200304080045_MC3-1-3378-3CDB@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®