Re: bzImage patch ? for monolithic kernels
Rick Hohensee (humbubba@smarty.smart.net)
Sat, 7 Aug 1999 16:58:14 -0400 (EDT)
>
>> Whilst the bzImage format itsef can handle kernels up to 16M in size,
>> there is a problem with boot loaders once the kernel gets to be over
>> 1M in size, and that is the current limit.
>>
>> There HAS to be a way round that limit, but I for one haven't the
>> foggiest what it is...
>>
>
>That's completely bogus. Those boot loaders (which??) are broken. I
>know for a fact that SYSLINUX has no such limit, lbcon definitely will
>not have it, and hard-coding that limit into the kernel compile
>sequence is a BUG.
>
>If LILO, say, doesn't support loading a bzImage > 1 MB then LILO
>should complain, but not prevent someone from compiling the image for
>use with another boot loader.
>
> -hpa
>
whew. Glad to hear that.
This is also an example of why things that could go in the bootloader
shouldn't.
Simple wins.
The whole kernel commandline thing has always struck me as odd.
"Programming in the large" isn't the same for a kernel. The kernel doesn't
have a main(), why should it have argv/argc ? It seems to me that the
kernel could ask for parameters, or rdev could be generalized, or both.
As I said before, something like this is a net simplification, although it
complicates the kernel.
Rick Hohensee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/