It is probably fairly easy to increase the LILO command line to 512
bytes (including terminator). Beyond 512 there are complicating factors:
1. "lilo -R ..." -- the space reserved for the stored command line
is 1 sector.
2. configuration option "fallback" -- again 1 sector is the amount reserved.
There are 2 buffers used for the command line. Since these are
allocated on sector boundaries, 512 should present no serious problems.
--John
At 07:35 AM Friday 5/5/2006, H. Peter Anvin wrote:
Alon Bar-Lev wrote:
This should be a simple modification and I don't see why we
should fight on the LILO problem (if exists) when we have
the compile time config options alternative.
People who uses LILO may leave the default 256 value. Other
may migrate to a higher one.
This is cargo-cult programming, sorry. Let's find out what the
problem is and fix it right. If that involves fixing LILO and/or
dealing with a LILO bug, we have ways we can do that.
-hpa
PGP KeyID: 6781C9C8 (good until 31-Dec-2008)
Keyserver at ldap://keyserver.pgp.com OR http://pgp.mit.edu
LILO links at http://freshmeat.net/projects/lilo
and Help link at http://lilo.go.dyndns.org
-
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]
