On Aug 7, 2011, at 9:23 AM, Bruce Cran wrote:
> On 06/08/2011 18:02, Martin Matuska wrote:
>> The error is in FreeBSD ISO images.
>> They are created using makefs and that doesn't create ISO files that
>> strictly comple to the ECMA-119 (ISO9660 standard).
>>
>> I have already filed a PR at NetBSD
On 06/08/2011 18:02, Martin Matuska wrote:
The error is in FreeBSD ISO images.
They are created using makefs and that doesn't create ISO files that
strictly comple to the ECMA-119 (ISO9660 standard).
I have already filed a PR at NetBSD (bin/45217):
http://gnats.netbsd.org/cgi-bin/query-pr-single
On Sat, 06 Aug 2011 20:37:38 +, Baptiste Daroussin wrote:
On Sat, 06 Aug 2011 19:02:49 +0200, Martin Matuska wrote:
The error is in FreeBSD ISO images.
They are created using makefs and that doesn't create ISO files that
strictly comple to the ECMA-119 (ISO9660 standard).
I have already fil
On Sat, 06 Aug 2011 19:02:49 +0200, Martin Matuska wrote:
The error is in FreeBSD ISO images.
They are created using makefs and that doesn't create ISO files that
strictly comple to the ECMA-119 (ISO9660 standard).
I have already filed a PR at NetBSD (bin/45217):
http://gnats.netbsd.org/cgi-bin/
The error is in FreeBSD ISO images.
They are created using makefs and that doesn't create ISO files that
strictly comple to the ECMA-119 (ISO9660 standard).
I have already filed a PR at NetBSD (bin/45217):
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45217
The volume_set_id doesn't h
It's often convenient to extract pieces of iso9660 images for recovery
purposes or a jail. As libarchive no longer recognizes them one has to
resort to mdconfig + mount_cd9660. On a zfs-only system this populates
bufspace unused by arc cache and never gives memory back... nevermind.
$ tar tf Fre