09.04.2013 21:58, Mark Saad пишет:
>> While not the same you can always do this
>>
>> mdconfig -a -t vnode -f yourfreebsd-version.iso
>>
>> mount -t cd9660 /dev/md0 /cdrom
>>
>> Then use pax, cpio , cp, rsync etc to copy the data off the image .
This way breaks hardlinks, so /rescue expands to 690M instead of 5M.
>> Also if memory serves me right libarchive may be able to unpack an iso much
>> like a tar or cpio archive . Double check that .
> Also for what its worth, tar does work at extracting an iso as well
bsdtar/libarchive fails to expand these images correctly do to its own bugs:
# ktrace -i tar xf ../FreeBSD-8.4-BETA1-amd64-livefs.iso
usr/bin/make: Can't create 'usr/bin/make'
usr/bin/pic: Can't create 'usr/bin/pic'
usr/bin/post-grohtml: Can't create 'usr/bin/post-grohtml'
usr/include/_semaphore.h: Can't create 'usr/include/_semaphore.h'
usr/lib/libarchive.so.5: Can't create 'usr/lib/libarchive.so.5'
^C
# kdump | grep -B 12 "'usr/bin/make'"
10247 bsdtar CALL link(0x284eff20,0x284c6180)
10247 bsdtar NAMI "usr/bin/mailq"
10247 bsdtar NAMI "usr/bin/make"
10247 bsdtar RET link -1 errno 18 Cross-device link
10247 bsdtar CALL umask(S_IWGRP|S_IWOTH)
10247 bsdtar RET umask 0
10247 bsdtar CALL write(0x2,0x7fbfe788,0xc)
10247 bsdtar GIO fd 2 wrote 12 bytes
"usr/bin/make"
10247 bsdtar RET write 12/0xc
10247 bsdtar CALL write(0x2,0x7fbfe788,0x1d)
10247 bsdtar GIO fd 2 wrote 29 bytes
": Can't create 'usr/bin/make'"
> So , what issues does this cause ? Have your filed a pr with FreeBSD or
> NetBSD ?
Not yet.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
