Re: makefs -t cd9660 vs. mkisofs

Hubert Feyrer <[email protected]> Mon, 12 Sep 2005 04:26:57 +0200 (CEST)

Newsgroups	gmane.os.netbsd.devel.general
Message-ID	<[email protected]>

On Mon, 12 Sep 2005, Hubert Feyrer wrote:
> 1) mkisofs -b cdboot -no-emul-boot -o nb.iso isodir.hf
> 2) obj.i386/tooldir.NetBSD-2.0-i386/bin/nbmakefs -t cd9660 -o \
> 	"rockridge,bootimage=i386;isodir.hf/cdboot,no-emul-boot" \
> 	nb.iso isodir.hf

Comparing the output further (using "isoinfo -l" on both), I see two 
differences:

  * makefs directories are printed as "BIN.;1" while for mkisofs I get
    "BIN". This is probably not so thrilling...
  * mkisofs writes a file "BOOT.CAT;1" which makefs doesn't write (at all).
    Looking at mkisofs' manpage, that file seems to  be needed for booting.

Looking at the output from makefs -t cd9660, some boot catalog seems still 
to be written, and the output is printed by cdboot before it hangs, so I 
wonder if that's a bug in makefs or cdboot...

  - Hubert