Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Jul 2009 09:52:49 -0400
From:      Lowell Gilbert <freebsd-current-local@be-well.ilk.org>
To:        Tim Kientzle <kientzle@freebsd.org>
Cc:        John Hay <jhay@meraka.org.za>, "'freebsd-current@freebsd.org'" <freebsd-current@freebsd.org>
Subject:   Re: Joliet and release ISOs?
Message-ID:  <4463doaifi.fsf@lowell-desk.lan>
In-Reply-To: <4A62D689.1050906@freebsd.org> (Tim Kientzle's message of "Sun\, 19 Jul 2009 01\:17\:13 -0700")
References:  <4A615602.4090000@freebsd.org> <20090719075459.GA31256@zibbi.meraka.csir.co.za> <4A62D689.1050906@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Tim Kientzle <kientzle@freebsd.org> writes:

> John Hay wrote:
>> On Fri, Jul 17, 2009 at 09:56:34PM -0700, Tim Kientzle wrote:
>>> Do we need Joliet extensions on the release ISOs?
>>>
>>> The reason I ask is a little involved:  jkim@ recently
>>> pointed out to me that tar in -CURRENT can no longer
>>> extract symlinks from the release ISOs.
>>>
>>> I tracked this down to the fact that the release ISOs
>>> have both Joliet and RockRidge extensions and tar now
>>> supports (and actually prefers) Joliet extensions when
>>> it sees them. Joliet doesn't support symlinks, so tar
>>> doesn't see symlinks on disks with both kinds of extensions.
>>
>> What is the reason for prefering Juliet in tar? Can't we
>> just swap the preference?
>
> Because of the way libarchive works internally coupled with
> basic differences in how Joliet and RockRidge information
> is stored, it turns out that libarchive has to decide
> whether or not to use the Joliet information before it
> can tell whether RockRidge information is available.
> So preferring RockRidge is actually quite difficult.
>
> I would like to change this, but it's going to be
> quite a while before I have enough time to work on it.

Sounds like you're out of good options then.  Maybe a good temporary
workaround would be a switch to disable Joliet support?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4463doaifi.fsf>