>>> Is there a known method/patch/etc to making a monolithic kernel
>>> under 2.3.xx without modules. I kept getting the "System too
>>> big" crap and dutifully used modules but I am trying to figure
>>> out if a monolithic kernel will ever be supported again.
>> `make bzImage'. Any chance of making this the default and
>> retaining an `ozImage' target for the times when bzImages won't
>> work?
> I should clarify - 8-}
> I am using bzImage. I get the following errors that are all
> related to the fact that the kernel size is > 1 Meg.
> Root device is (8, 1)
> Boot sector 512 bytes.
> Setup is 3440 bytes.
> System is 1036 kB
> System is too big. Try using modules.
> make[1]: *** [bzImage] Error 1
> make[1]: Leaving directory
> `/mnt/micropolis2/src/linux.2312/arch/i386/boot'
> make: *** [bzImage] Error 2
> Anyone know a fix? I know that some previous debate had raged
> about bzImage should be able to handle up to 16M kernel sizes
> but have found no data/patches/etc on what to do to get past 1M.
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...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
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/