🚀 go-pugleaf

Tim Tuck (Tim.Tuck@penrith.net) wrote:

: OH and there seems to be some serious documentation errors such as the
: the boot linux gets call linuz instead of linux.gz - or is this
: symptomatic of other problems ?

A boot file name, if it is compressed or not, if it has suffix .gz or
not, etc.  is plain immaterial.  You may call it "mickeymouse" is such
fancy will strike you (but then watch for Disney lawyers knocking to
your door :-).  Some years ago first version of a loader on Alpha indeed
looked if '.gz' is present or not but this is an ancient prehistory.

BTW - a compressed form of a kernel loads faster (time differences
are really not that important :-)  as your memory and processor are
substantially faster than your disk.  Why Red Hat in recent
distributions (not only Alpha) stuck in /boot both compressed and
uncompressed versions of boot images is not something for which
I can find any rational explanation.

  Michal

p.s. If you load your boot images from a device with a file system
different than ext2 (like FAT or "pure" ISO9660, for example) you better
keep file names for that withing constraints that fs or you will have
problems to find them in a boot time.  This actually applies universally
but it is hard to create on ext2, for example, a file with a name which
ext2 does not recognize.