Messages in this thread |  | | Subject | Re: Given an image, how can show its config? | Date | Sat, 23 Sep 2000 13:27:54 -0400 | From | Horst von Brand <> |
| |
Keith Owens <kaos@ocs.com.au> said:
[...]
> I worry about anything that increases the on disk size of bzImage, even > if the extra data does not get loaded into kernel memory. > > 629590 2.2.16/arch/i386/boot/bzImage > 786273 2.4.0-test8/arch/i386/boot/bzImage > > cat .config System.map | gzip | wc -c > 107591 > > That would take my 2.4.0 bzImage to 893864, it does not leave much room > out of a 1.4Mb floppy for LILO files. We could have multiple make > targets, with and without appended config/map but that just complicates > the build environment.
Boot floppies shouldn't use "full" kernels with bells and whistles in any case.
> This is all to protect those few poor 'administrators' who cannot keep > track of three separate files. We should not coddle such idiots, if > they cannot track 3 files they should not be configuring Linux. > Anybody who loses their config and System.map will learn from their > mistake and only do it once or they will never learn, in which case > they are better off running Windows.
Very true. -- Horst von Brand vonbrand@sleipnir.valparaiso.cl Casilla 9G, Vin~a del Mar, Chile +56 32 672616 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |