Hello Lars, hello all,
> > > System is 552kB
> > > System is too big
> > > What does this mean? How can I sort it?
> >
> > You can sort it by using "make bzImage" instead of "make zImage"
>
> Taking the risk of being a nitpicker, I'd like to make a small
> correction...
>
> You can *TRY* to sort the problem out by using "make bzImage". What that
> does is it uses a better compression algorithm to compress the kernel
> image (the Burrows-Wheeler blocksorting text compression algorithm if I'm
> not completely mistaken, see "man bzip2") so you can have a larger kernel
> image but not arbitrarily large. Eventually you run into the same
> problem...
Simply repeating a wrong statement does not make it necessarily
true.
bzImage has NOTHING to do with bzip or bzip2!
bzImage has NOTHING to do with bzip or bzip2!
bzImage has NOTHING to do with bzip or bzip2!
And, once again:
bzImage has NOTHING to do with bzip or bzip2!
It simply means "big" zImage causing programs like lilo to use
another loading algorithm for the kernel image. It is still
compressed using gzip.
> My recommendation is modules. I have _everything_ as modules in my kernel
> except what is needed to mount my root partition (ie. IDE and ext2
> support). It takes some work to sort out conf.modules etc. but IMHO the
> advantages outweigh the disadvantages.
That's my opinion, too.
Cheers, 73
Gerd
P.S.: Oh, I think I've missed something:
bzImage has NOTHING to do with bzip or bzip2!
bzImage has NOTHING to do with bzip or bzip2!
bzImage has NOTHING to do with bzip or bzip2!
But I guess there always will be a lot of people not believing this
just like there are still some folks thinking Earth is a disk....
