4477048 bytes. Uhgh. I suppose my only remaining question is - why is this kernel so much larger than 2.4.21? Most of the options I added to the config were modules. Why is this kernel so much larger?
Guh. Time to trim the kernel config, I suppose... Thanks again. On Thu, Jan 08, 2004 at 11:12:30AM -0500, Ben Collins said: > Date: Thu, 8 Jan 2004 11:12:30 -0500 > From: Ben Collins <[EMAIL PROTECTED]> > To: Mike Edwards <[EMAIL PROTECTED]> > Cc: D Lambrou <[EMAIL PROTECTED]>, [email protected] > Subject: Re: uncompressed image too long? > User-Agent: Mutt/1.5.4i > X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=ham version=2.60 > X-Spam-Level: > > On Thu, Jan 08, 2004 at 10:39:34AM -0500, Mike Edwards wrote: > > vmlinuz itself is 1821650 bytes, though, so I'm not sure why I'm running > > into this limit (is the uncompressed image really > 3.5 MB?). > > > > Also - would I not run into the same problem if I tried to use the vmlinux > > image? > > The size of vmlinuz isn't the issue...it's the uncompressed size. > Doesn't make a difference if it's compressed or not. > > So just do "zcat vmlinuz > vmlinux" and you can see the size. > > > And lastly - I'm using make-kpkg to create a custom kernel package for > > this. How can I have it use the vmlinux image instead of vmlinuz? > > Latest kernel-package in unstable will use the correct file. > > -- > Debian - http://www.debian.org/ > Linux 1394 - http://www.linux1394.org/ > Subversion - http://subversion.tigris.org/ > WatchGuard - http://www.watchguard.com/ -- Mike Edwards <[EMAIL PROTECTED]> System Administrator Psychology Department, Rutgers University, Newark campus 973-353-5440 x246
