Actually, that's not really valid, as some architectures require you to
fit your kernel in a smaller space so the loader can deal with it, such as
the 1MB sparc limit.  Kris

> Or maybe a better question is do we really need to compress the kernel
> anymore?  With 80G hard drives the norm today do we really need to save
> space?
>
> -----Original Message-----
> From: James Colannino [mailto:email2jamez@covad.net]
> Sent: Monday, May 05, 2003 11:56 AM
> To: kclug@kclug.org
> Subject: Re: kernel presentation at ILUG on Sat.
>
>
>> It depends on what make target you specified when you built your
>> kernel. I always use "make dep && make clean bzImage modules
>> modules_install". This creates a bzip2'd kernel. IIRC, the grub/lilo
>> boot loader does the uncompressing so if you use bzip2, you need a
>> boot loader that supports it.
>
>
> Oh ok.  That clears up a lot.  I was under the impression that it was
> the kernel itself that was doing the uncompressing.  So how exactly is
> the kernel itself (uncompressed) constructed?  I assume many different C
>  programs are being mashed together into one giant binary, or is the
> image comprised of many binary files which are simply read into memory
> consecutively to form one large runtime monolithic kernel?
>
> James
>
>
>
>
> This transmission (and any information attached to it) may be
> confidential and is intended solely for the use of the individual or
> entity to which it is addressed. If you are not the intended recipient
> or the person responsible for delivering the transmission to the
> intended recipient, be advised that you have received this transmission
> in error and that any use, dissemination, forwarding, printing, or
> copying of this information is strictly prohibited. If you have received
> this transmission in error, please immediately notify LabOne at the
> following email address: securityincidentreporting@labone.com
>
>
>
>