Stefan Voelker wrote:
>
> Thanks to all who suggested using bzImage. Lilo now installs the new
> kernel. Although, somehow the whole thing doesn't make sense to me. Why
> does lilo have no problem with the out-of-the-box kernel (570kB), but does
> complain that my custom kernel (425kB) compiled using zImage is too big?
> And why does compiling the same kernel using bzImage make lilo happy
> although the actual file size is reduced by a mere 8 bytes. Can somebody
> explain this to me?
Don't get hung up on physical file sizes for determining whether
something needs bzImage or just zImage. The real problem is that when
your custom kernel is unpacked upon boot, it will overflow the size
allowed for zImages. By using bzImage, you create a larger pool for
unpacking.
> On Wed, 29 Sep 1999, John Aldrich wrote:
>
> > On Wed, 29 Sep 1999, you wrote:
> > > Hi all,
> > >
> > > I have a weird problem with lilo. I just recently installed Mandrake 6.1.
> > > The install went smooth. No problems. After finishing the installation,
> > > I decided to build a custom kernel, since the one that comes with Mandrake
> > > supports a lot of things I don't need and consequently is fairly big at
> > > 570kB. So I built custom kernel which is about 425kB. I modified
> > > /etc/lilo.conf copied the new kernel and System.map into /boot and ran
> > > lilo. Lilo failed. The error message said something to the extend that
> > > my custom kernel was too big. Lilo does not complain about the original
> > > Mandrake kernel being too big! Which makes???? Has anyone else
> > > encountered this problem? Any help would be greatly appreciated.
> > >
> > Try recompiling and make bzImage instead of zImage.
> > John
> >
--
Steve Philp "The Internet is like crack
Network Administrator for smart people..."
Advance Packaging Corporation --Arsenio Hall
[EMAIL PROTECTED]
