Holger Lubitz wrote:
>
> "D. Stimits" proclaimed:
> > down to 1.44 MB. But then it would also have to be self-extracting,
> > which complicates it, so I'm wondering how effective this current
> > compression is, and if a more bzip2-like system would be beneficial as
> > kernels get larger?
>
> b
"D. Stimits" proclaimed:
> down to 1.44 MB. But then it would also have to be self-extracting,
> which complicates it, so I'm wondering how effective this current
> compression is, and if a more bzip2-like system would be beneficial as
> kernels get larger?
bzip2 has pretty large memory requireme
"Khachaturov, Vassilii" wrote:
>
> > Question 2, apparently ramdisk uses gzip compression; the name of the
> > kernel from make bzImage seems to maybe refer to bzip2 compression. Is
> > the kernel image using gzip or bzip2 compression for bzImage? Would
> bzImage stands for "big zImage" - this is
> Question 2, apparently ramdisk uses gzip compression; the name of the
> kernel from make bzImage seems to maybe refer to bzip2 compression. Is
> the kernel image using gzip or bzip2 compression for bzImage? Would
bzImage stands for "big zImage" - this is a format invented for kernels that
don't
First I have a question about the compression of bzDisk. While trying to
debug the reason for a modular boot failure versus a successful
non-module boot (XFS filesystem for root), I found that I can mount my
initial ramdisk on loopback as a means of examining which modules are
available to it. How
5 matches
Mail list logo
