Okay... I have successfully reproduced this bug. It's definitely a Linux
kernel bug -- mkisofs correctly puts file numbers (inode numbers) in the
PX Rock Ridge entries.
Unfortunately it is a pretty deep decision in the Linux isofs that the
inode number is the offset of the directory entry; isofs pretty much needs
to be rewritten to be dentry-centric rather than inode-centric on order to
resolve this. Note that dentry-centric operation is the sane thing for
something like isofs, so this wouldn't be a bad idea.
Unfortunately, that doesn't solve all problems: there is no structure to
the inode numbers provided in the PX entries, and there is the potential
for collision when used on a disc which is only partially RockRidge (which
is legal.) This has to be taken into account, and all of these things
have to be done without reading the whole disc first...
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jan 31 2002 - 21:00:52 EST