not to sound like I'm Microsoft-bashing, but having their software version numbers be the (supposed) year of release was icky and gross. it doesn't give you any idea of what sort of development activity has gone on since the last release, like a "normal" versioning system does.
> Your boot image may be too large. This is why we > now have the option to build a (smaller) > bzip-compressed image, instead of a > gzip-compressed image. make bzImage doesn't make a bzipped kernel image. the 'b' stands for 'big'. from Documentation/kbuild/commands.txt in the 2.2 source tree:
Note: the difference between 'zImage' files and 'bzImage' files is that 'bzImage' uses a different layout and a different loading algorithm, and thus has a larger capacity. Both files use gzip compression. The 'bz' in 'bzImage' stands for 'big zImage', not for 'bzip'!
(I used to think it meant bzip as well, until I r'd tfm.)
Slashdot Mirror
> Sun Solaris went from 2.6 to 7.
well, not exactly.
Solaris 2.x was really SunOS 5.x. and I think perhaps SunOS 6.x as well. so, going from Solaris 2.6 to Solaris 7 wasn't quite the leap that it seems.
not to sound like I'm Microsoft-bashing, but having their software version numbers be the (supposed) year of release was icky and gross.
it doesn't give you any idea of what sort of development activity has gone on since the last release, like a "normal" versioning system does.
- Note: the difference between 'zImage' files and 'bzImage' files is that 'bzImage' uses a different layout and a different loading algorithm, and thus has a larger capacity. Both files use gzip compression. The 'bz' in 'bzImage' stands for 'big zImage', not for 'bzip'!
(I used to think it meant bzip as well, until I r'd tfm.)