On 9/4/06, Paul Mackerras <[email protected]> wrote:
Alon Bar-Lev writes:
> Current implementation stores a static command-line
> buffer allocated to COMMAND_LINE_SIZE size. Most
> architectures stores two copies of this buffer, one
> for future reference and one for parameter parsing.
Under what circumstances do we actually need a command line of more
than 256 bytes?
Sure!
With static modules options, splash support, disk encryption, suspend,
local initrd settings we need much more than 256 bytes...
It seems to me that if 256 bytes isn't enough, we should take a deep
breath, step back, and think about whether there might be a better way
to pass whatever information it is that's using up so much of the
command line.
But the command line is a wonderful tool... It allows you to compile
the same kernel/initramfs and install it on different machines,
modifying only the boot loader configuration file. It also allows
several boot profiles at boot loader level, without the need to
replaces files or have complex initrd...
So it worth modifying current implementation.
Best Regards,
Alon Bar-Lev.
--
VGER BF report: H 0
-
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]
