[Top][All Lists]

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

Re: [Libcdio-devel] Rock Ridge and libisofs/xorriso 'AL' extension

From: Thomas Schmitt
Subject: Re: [Libcdio-devel] Rock Ridge and libisofs/xorriso 'AL' extension
Date: Wed, 26 Jul 2017 11:58:43 +0200


i cloned a libcdio git and build it.
Now i realize that "isoinfo" is not a libcdio program. Duh.
So i go on with libcdio's ./src/.libs/iso-info . 

To force linking with the freshly compiled libraries i do:


Then i try with the 50 KB test iso from the bug report:

  ./src/.libs/iso-info -f -i 

It says
  ISO-9660 Information
  Error getting above directory information

Is this a known symptom of the problem we deal with ?
Or am i seeing something different here ?

Other ISOs yield a list of files.

I will start with experiments and debugger now.


The other user who urges me to record xorrisofs options by default,
showed me a live-build script which indeed has xorrisofs option
So i posted a test proposal to
in order to find out whether this is really the trigger which caused the
"AL" SUSP entires in the ISO.

Update: Pete found the same script meanwhile. So it is very likely
the origin of the KALI ISO and its "AL" entries. 

Now i wonder what Raphael intended with the commit that introduced
option --hardlinks for ISOs with SYSLINUX/ISOLINUX bootloader:
  author        Raphaƫl Hertzog <address@hidden>        2016-12-02 14:42:59 
  "Instead of renaming kernel for syslinux, create hardlinks"

As already stated, my users are more inventive than i am.
(Let me hope this does not rely on a bug or unintentional feature of

Have a nice day :)


reply via email to

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