[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-xorriso] xorriso.x86_64 1.5.0 - 'No Joliet present'

From: Thomas Schmitt
Subject: Re: [Bug-xorriso] xorriso.x86_64 1.5.0 - 'No Joliet present'
Date: Fri, 22 Mar 2019 15:56:58 +0100


Ricky Tigg wrote:
> I realise option '-isohybrid-apm-hfsplus' was left unselected source
> code as part of  the copy/paste operation

So together with my mail client's way to show your mail client's
inappropriate links, we can explain the deviations between your
posted "as_mkisofs" report and mine here.

> Options '-Jrlo', '-V ’Fedora-WS-dvd-x86_64-29’' used in command 'xorriso -as
> mkisofs'  produced error messages
> [...]
> # xorriso -as mkisofs -Jrlvo ’m.iso’ iso-t
> xorriso : FAILURE : -as mkisofs: Unrecognized option '-Jrlvo'

Hm. The emulator dislikes option -o in a condensed option list.
Probably because -o expects a file path as parameter.
The emulator would recognize this:

  -Jrlv -o m.iso

Best is to give each option as separate argument

  -J -r -l -v -o m.iso

In any case it does not help to first create m.iso with those options and
to then overwrite m.iso by a run without them.
You need a single run of xorriso with all arguments that you desire to use.

So just add

  -J -r -l -v

to your xorriso -as mkisofs run:

  xorriso -as mkisofs  -J -r -l -v -o 'm.iso' -V ’Fedora-WS-dvd-x86_64-29’ 

-J causes a Joliet directory tree, in case somebody wants to read the
files by a MS-Windows system. -r sets the access permissions of files
inside the ISO to essentially read-only for everyone. This gets into effect
when the ISO is mounted by GNU/Linux or other Unix-like operating systems.
-l permits ISO 9660 file names up to 31 characters. This might be necessary
to use files with long names during the ISOLINUX bootloader stage. (Wise
ISOLINUX compositions use only names of DOS style 8.3 in order to avoid
any length problems.)
-v lets xorriso report entertaining messages while it runs.

> May I take "can join the genisoimage habit" as a recommendation ?

No. I decided that the hallmark is best stored in "Preparer Id".
But you pointed this out in your list of unexpected deviations.

> Is then command ' -A "@xorriso@" -p """  aimed to be executed by
> relying on 'xorriso -as mkisofs' ?

Yes. mkisofs or genisoimage won't recognize "@xorriso@" as command to
insert their own signature. Of course you could submit your own text
for the field.

As far as i know, the content of both PVD fields does not matter to
any boot firmware or boot loader system.


> I took my first inspiration from
> http://www.tuxfixer.com/mount-modify-edit-repack-create-uefi-iso-including-kickstart-file/

Except that this leaves out the third boot image 'macboot.img', the steps
5 and 6 should create an ISO that boots from DVD and USB stick via BIOS
or EFI firmware.
With EFI this depends on a suitable content in image file "efiboot.img"
which is supposed a FAT filesystem with EFI boot programs and their helpers.

The xorrisofs options -isohybrid-mbr and -isohybrid-gpt-basdat do about
the same within the xorriso run. So no run of program "isohybrid" (step 6)
is necessary.

> Since I failed to produce a ISO image that would boot, I investigated and
> took  a new inspiration – a last one – from
> https://www.centos.org/forums/viewtopic.php?t=55697
> which at last served well my purpose.

Aha. Myself three years ago explaining the then new feature to ask xorriso
for advise about options to replay the boot equipment of existing ISOs.

Well, it was not a total success. The USB stick did not work.

Have a nice day :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]