> For reference, here is how the current xorriso is configured:
The current theory (obviously already known to Colin Watson)
is that the combination of -b and -e is to blame for the
reaction of the Mac.
As soon as more than one single -b (or -e) was given, it offers
the user an unusable choice menu of boot images.
-------------------------------------------------------------
Some upstream nitpicking:
> -checksum_algorithm_iso md5,sha1
This option is a surplus remnant of Jigdo production.
Being alone, it has no effect.
I already asked at debian-cd why this option is used although no
HFS+ image file is added as third boot image (as Fedora does).
It seems that Macs which want an Apple Partition Map also want HFS+.
(We will never find out if the option is not omitted until
somebody reports that it really would be needed.)
Hi,
> For reference, here is how the current xorriso is configured:
The current theory (obviously already known to Colin Watson)
is that the combination of -b and -e is to blame for the
reaction of the Mac.
As soon as more than one single -b (or -e) was given, it offers
the user an unusable choice menu of boot images.
------- ------- ------- ------- ------- ------- ------- ------- -----
Some upstream nitpicking:
> -checksum_ algorithm_ iso md5,sha1
This option is a surplus remnant of Jigdo production.
Being alone, it has no effect.
(One can record MD5 for image and each data file by option --md5. bazaar. launchpad. net/~libburnia- team/libisofs/ scdbackup/ view/head: /doc/checksums. txt
The checksums are stored in an array at the end of the ISO.
Format described in
http://
)
> -isohybrid- apm-hfsplus
I already asked at debian-cd why this option is used although no
HFS+ image file is added as third boot image (as Fedora does).
It seems that Macs which want an Apple Partition Map also want HFS+.
(We will never find out if the option is not omitted until
somebody reports that it really would be needed.)
Have a nice day :)
Thomas