From: David Newall <david@davidnewall.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: stripping down the kernel-parameters.txt file
Date: Wed, 12 Sep 2007 22:13:36 +0930 [thread overview]
Message-ID: <46E7DEF8.50201@davidnewall.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709120339470.26177@localhost.localdomain>
Robert P. J. Day wrote:
> while killing some time between compiles and ridding the
> kernel-parameters.txt file of out-of-date or incorrect cruft, it
> occurs to me that that file is borderline valueless since it
> apparently tries to document every possible boot-time parameter,
> including those associated with individual modules. that's just
> silly.
>
"Silly" is such a negative word. I think it's aspirational. It
probably can't be achieved, but that's no reason to give up, nor to
remove existing text.
> i suggest that that file record only the basic boot-time params, and
> the documentation for module-specific parameters be moved closer to
> the module source itself. there's no point in that poor file trying
> to keep up with all of the module development in the tree.
Better yet, would be if module maintainers updated the file as they
update their modules.
next prev parent reply other threads:[~2007-09-12 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 7:50 Robert P. J. Day
2007-09-12 12:43 ` David Newall [this message]
2007-09-12 13:11 ` Robert P. J. Day
2007-09-12 13:32 ` David Newall
2007-09-12 14:06 ` Robert P. J. Day
2007-09-12 14:30 ` Rogan Dawes
2007-09-12 14:44 ` Robert P. J. Day
2007-09-12 17:47 ` Kyle Moffett
2007-09-12 17:56 ` 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=46E7DEF8.50201@davidnewall.com \
--to=david@davidnewall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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®