Re: bsdtar(1) can't extract new ISO images

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 have to be filled with 0x20 characters, too.
I am also preparing a patch for libarchive (different things), but that
won't fix that one bug - makefs needs to be fixed.

Dňa 3. 8. 2011 15:22, Test Rat wrote / napísal(a):
> 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 FreeBSD-9.0-BETA1-amd64-bootonly.iso
>   $ cpio -ti <FreeBSD-9.0-BETA1-amd64-bootonly.iso
>   2 blocks
>   $ tar tf FreeBSD-8.2-RELEASE-amd64-bootonly.iso
>   .
>   boot
>   boot/zfs
>   boot/firmware
>   boot/kernel
>   ^C
>   $ cpio -ti <FreeBSD-8.2-RELEASE-amd64-bootonly.iso
>   .
>   boot
>   boot/zfs
>   boot/firmware
>   boot/kernel
>   ^C
>
> I think it's also reproducable on daily snapshots from allbsd.org
> /stable/8 vs. /head. So, does this count as regression?
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"


-- 
Martin Matuska
FreeBSD committer
http://blog.vx.sk