[lkml]   [2000]   [Sep]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Given an image, how can show its config?
Keith Owens wrote:
> Daniel Phillips <> wrote:
> > I'd just like to remind you of Alan Cox's suggestion about appending
> > .config.gz to bzImage so that it doesn't get loaded into memory, and
> > my suggestion to put there as well.
> 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 | 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.

This is no argument when talking about hard disks. You are talking
only about floppy disks. I think you are smart enough to leave out
the gzip files if you are building for a floppy.

The zipped .config is considerably smaller than the system map, only
about 4K in size. Surely you would have no problem with that?

> Anybody who loses their config and will learn from their
> mistake and only do it once or they will never learn, in which case
> they are better off running Windows.
> "Think of it as evolution in action".

OK, I'm thinking about it that way. I concluded that somebody who
accidently selects both the 'bzImage includes System map' and 'bzImage
includes System config' options then complains that the boot file is
too big needs to be selected out.

Please note that when you're talking about idiots you're talking about
people like me and Alan, and we idiots resent that. ;-)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:45    [W:0.089 / U:5.604 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site