Re: Release ISO images have broken RockRidge data

2013-04-11 Thread Thomas Schmitt
Hi, i am not sure whether this is the correct source code version of makefs, but here i can see the reason for the bad Rock Ridge TF entries http://svnweb.freebsd.org/base/stable/8/usr.sbin/makefs/cd9660/iso9660_rrip.c?revision=224835&view=markup Line 688 has: p->attr.rr_entry.TF.h.l

Re: Release ISO images have broken RockRidge data

2013-04-10 Thread Eugene Grosbein
11.04.2013 00:27, Warren Block пишет: > On Wed, 10 Apr 2013, Eugene Grosbein wrote: > >> 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,

Re: Release ISO images have broken RockRidge data

2013-04-10 Thread Warren Block
On Wed, 10 Apr 2013, Thomas Schmitt wrote: Hi, Warren Block wrote: sync will support hard links with -H But how shall rsync know that the files in the ISO image stem from hardlink siblings on the hard disk where the image was produced ? Well, no it won't recreate them by inferral. Althoug

Re: Release ISO images have broken RockRidge data

2013-04-10 Thread Thomas Schmitt
Hi, Warren Block wrote: > sync will support hard links with -H But how shall rsync know that the files in the ISO image stem from hardlink siblings on the hard disk where the image was produced ? I succeeded with this post-pr

Re: Release ISO images have broken RockRidge data

2013-04-10 Thread Warren Block
On Wed, 10 Apr 2013, Eugene Grosbein wrote: 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 hard

Re: Release ISO images have broken RockRidge data

2013-04-09 Thread Eugene Grosbein
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 69

Re: Release ISO images have broken RockRidge data

2013-04-09 Thread Thomas Schmitt
Hi, thanks for flying xorriso. :)) I am its developer and came to this thread by googling, not by being subscribed here. Sorry for not having a message-id by which i could attach this mail to the thread. >>> libisofs: WARNING

Re: Release ISO images have broken RockRidge data

2013-04-09 Thread Mark Saad
On Tue, Apr 9, 2013 at 9:21 AM, Mark Saad wrote: > > > On Apr 9, 2013, at 7:00 AM, Eugene Grosbein wrote: > >> Hi! >> >> Release ISO images located at >> ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/ >> were generated with mkisofs until switch to makefs. For example, >> ftp://ftp.

Re: Release ISO images have broken RockRidge data

2013-04-09 Thread Mark Saad
On Apr 9, 2013, at 7:00 AM, Eugene Grosbein wrote: > Hi! > > Release ISO images located at > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/ > were generated with mkisofs until switch to makefs. For example, > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/8.2/FreeBS

Release ISO images have broken RockRidge data

2013-04-09 Thread Eugene Grosbein
Hi! Release ISO images located at ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/ were generated with mkisofs until switch to makefs. For example, ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/8.2/FreeBSD-8.2-RELEASE-amd64-livefs.iso was generated with mkisofs and has c