H. Peter Anvin wrote:
> b. This patch will override a user-provided command line if one
> exists. This is the wrong behaviour; instead, the builtin command
> line should only apply if no user-specified command line is present.
I'd prefer that the kernel default command line was appended
to the user-supplied one, instead of replacing it. (Or vice-versa.)
This way I can leave the user-specified command line empty and
get the behaviour described above. Or, I can choose a few
specific options to come from the bootloader and have others
come from the default command line (in the kernel).
I'm VERY interested in this feature, for purposes of automated
testing on multiple architectures. I have a test rig that can easily
set the command line at kernel compilation time. However,
coming up with a mechanism to control command line options on
multiple different bootloaders, for the variety of embedded platforms
I deal with, is very difficult. Right now this part of my
test rig works on all popular embedded arches except x86.
Eventually, I'd like to automatically test many different
kernel command line options, on multiple platforms.
Regards,
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]