if the goal is to simply put all of the basic boot-time kernel parms
along with the module-specific ones into a single file, sorted in
alphabetical order, then i contend that this is, in fact, "silly".
the end result would be a somewhat chaotic mess since i think it's
clear that those "basic" kernel parms (as i call them) are
qualitatively different from the module-specific ones, and should be
segregated as such.
now, if they're still going to go into a single file, it *would* make
sense to put the basic ones at the top and, following that, the
module-specific ones, one module at a time. *that* would make perfect
sense. but to mix them as they are now doesn't.
rday
p.s. by "basic", i mean those boot-time parms defined by either
"__setup()" or "early_param()". which means that module writers
should, as much as possible, stop using those macros to define
command-line parameters for their modules. that would go a long way
to restoring some order, and allowing for some decent and readable
documentation.
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
-
