Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso
From: Dag-Erling Smørgrav (des_at_des.no)
Date: 06/23/05
- Previous message: John Baldwin: "Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso"
- In reply to: John Baldwin: "Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: John Baldwin <jhb@FreeBSD.org> Date: Thu, 23 Jun 2005 21:32:22 +0200
John Baldwin <jhb@FreeBSD.org> writes:
> Even if mkisofs is patched this change isn't a bug in mkisofs. It's
> really a bug in our iso9660 filesystem. :(
Yes, but it's a lot harder to fix there than in mkisofs :)
Actually, -CURRENT doesn't have this bug, but it has another: it bases
the inode number on the position of the directory entry, so hard links
are lost. It doesn't make a big difference, because mkisofs seems
unable to generate ISO 9660 file systems with hard links.
DES
-- Dag-Erling Smørgrav - des@des.no _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
- Previous message: John Baldwin: "Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso"
- In reply to: John Baldwin: "Re: Duplicate inodes in 5.4-RELEASE-i386-disc1.iso"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|