[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: Pete Batard
Subject: Re: [Libcdio-devel] Rock Ridge and libisofs/xorriso 'AL' extension
Date: Tue, 25 Jul 2017 15:52:36 +0100
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

On 2017.07.25 12:49, Thomas Schmitt wrote:
That would be "original research" which Wikipedia forbids.

Hopefully, I shared my views on that in my other reply. ;)

I use the prepared extension opportunity of SUSP. Any SUSP compliant
software should have no problem with this.


Further it was the decision of Kali developers to record the device and
inode numbers of the input files on hard disk.
(Possibly by xorrisofs option --hardlinks, if not by xorriso command
In a Debian ISO i do not get any match from

   xorriso -indev $iso -find / -has_any_xattr -exec get_any_xattr --

So AAIP in published distro ISOs is rather exotic. Neither fast
incremental backup preparations nor hardlink recording are of much use
in an installation ISO. Hardlinks rather serve for high backup fidelity.

Okay. I can try to get back to the Kali maintainers on that, but I'm not sure how much they're gonna like being asked about this for the 3rd time in a row...

You can ask me about ISO 9660 at any time on e.g. address@hidden
(or via address@hidden if it's somewhat confidential).

Thanks. In retrospect, it's clear I should have hit this mailing list as soon as I found about 'AL' being used But I was hoping the Kali people could point me in the right direction first.

The Wikipedia article structure is misleading. SUSP is the boss of
Rock Ridge, not a part of it.

Would you have a conflict of interest in editing the pages that aren't related to AAIP and 'AL'? As far as I'm concerned, technical Wikipedia topics are better left to the person with the most expertise on the matter, regardless of the conflicts of interest Wikipedia moderators fear they might bring... ;)

In any case, AAIP belongs to the paragraph "Variants", where Amiga is

Yeah, I wondered about that too... But I wasn't clear whether AAIP was to be considered as a something that might fall outside established standards. I'll see if I can edit this when I get a chance.

Further, AAIP does not only record ACL but arbitrary extended file

Yup, I got that. But this is a one line entry in a Wikipedia article, so I didn't want to go into too much details.

I'm attaching a patch proposal for review, which I'll be happy to commit to
libcdio if everyone agrees.

I think we should first re-investigate the bug which led to the
list of known SUSP entry names, which by the triggered program reaction
actually violates the specs.

Ack. I think your reply a few minutes after that patch proposal made it clear that it should be off the table for now.

It would be interesting to see the xorriso command line they use.

Well, since I was talking about this issue with some other people, who mentioned this specific item to me, I'll take that as a cue to point out that, from what they reported, xorriso and genisoimage decided to drop what they considered one of the most useful feature from mkisofs, which was to store the options being passed to the commandline application into the ISO itself.

I guess we sure wouldn't mind if that feature had found its way into the new utilities right now... Maybe something that could be added to xorriso in the future? ;)

Of course, this doesn't help us much for the time being, and yeah, I was hoping that the Kali people would also be able to give me the command line they used for ISO generation, and spared a lot of information digging, when I logged that issue with them...

Trying to read e.g.;a=blob;;h=e97709799b9408374777895f5cbedbd9098886a3;hb=HEAD

I'm not sure there's much to find in live-build-config. I've done just that when trying to see if I could figure out the Kali ISO generation command, and it just seems to invoke another set of commands that come from the system and not the git repo. I didn't push it further at the time, as I didn't want to have to go through a Kali install on a VM...

Still if you're interested, here's a web accessible clone of the latest git version:



reply via email to

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