From: Kyle Moffett <mrmacman_g4@mac.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Rogan Dawes <lists@dawes.za.net>,
David Newall <david@davidnewall.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: stripping down the kernel-parameters.txt file
Date: Wed, 12 Sep 2007 13:47:38 -0400 [thread overview]
Message-ID: <3E869809-EA55-4F90-B364-788081ACEC00@mac.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709121034450.25084@localhost.localdomain>
On Sep 12, 2007, at 10:44:29, Robert P. J. Day wrote:
> in the end, there should be a nice, *short* reference for what i
> like to call "basic" kernel parms (defined by __setup() or
> early_param()), while anyone who wants to learn about any module-
> specific parms should then have to go look up the info for that
> given module, that's all.
>
> as a trivial starting point, this would involve nothing more than
> shifting current content around in kernel-parameters.txt, putting
> the basic stuff at the top, and the module-specific stuff after
> that. heck, that would even give module authors the chance to add
> a line or two of module description if they wanted. how does life
> get any better than that?
Well, maybe if modules could be used similarly to: "modprobe
my_module --help" to give a description of the available module
parameters. That information might be merged into modules from text
file(s) or vice-versa, but I can see it being significantly more
useful. Another mildly-useful feature would be to stick the basic
boot params and those for built-in modules into a little text file
which could optionally be embedded in the initramfs along with the
"less" binary, so that a "vmlinuz --help" could be made to work
usefully from your bootloader.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2007-09-12 17:48 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
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 [this message]
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=3E869809-EA55-4F90-B364-788081ACEC00@mac.com \
--to=mrmacman_g4@mac.com \
--cc=david@davidnewall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@dawes.za.net \
--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®