X86 kernel build chain - how bzImage gets created

lists.kernelnewbies.org

44 points·DiabloD3··7 comments

Interesting, I thought bzImage contained a bzip2ed image - vmlinux.bin to (I assume) vmlinux.bin.bz2. This shows vmlinux.bin.gz.

I really should RTFMakefile, but I'm too tired after eating lots of turkey...

I'm a little fuzzy on it, but its named gz for historical purposes due to boot loaders. There is even lzma2 compressed images, and they are still named .gz afaik (which admittedly is less than it should be).

No it stands for "Big Zipped Image". Nothing to do with bzip2.

The choice of compression is not encoded in the filename.

http://www.kernel.org/doc/menuconfig/init-Kconfig.html#HAVE_...

I think the bzImage kernel image file might predate the release of bzip2. I'm not sure where to lookup when the kernel source first built a bzImage though.

Before it was the Big Zipped Image it was the Zipped Image, zImage or vmlinuz. Google has results as far back as 2001 or 2002 for vmlinuz so it's safe to say the tradition predates bzip2.

It's worth noting that Linux can in fact use bzip2 today, and the resulting image is still typically called bzImage.

I think bzImage and bzip2 were approximately contemporaneous - I certainly remember using bzip2 in the late 90s (it was not real fast on a P90!).

Oh, it is older than I thought. Wikipedia says version 0.15 was released in 1996.

Either way "bz" stands for Big Zipped and is unrelated to bzip2.

Reply on news.ycombinator.com