Messages in this thread | | | Date | Thu, 19 Oct 2006 01:29:32 +0200 | From | (Joerg Schilling) | Subject | Re: Linux ISO-9660 Rock Ridge bug needs fix |
| |
Bodo Eggert <7eggert@gmx.de> wrote:
> On Wed, 18 Oct 2006, Joerg Schilling wrote: > > Bodo Eggert <7eggert@elstempel.de> wrote: > > > > BTW2, Just to be cautionous: what will happen if somebody forces the same > > > inode number on two different entries? > > [...] > > This is something you cannot check. > > Exactly that's why I'd ignore the on-disk "inode number" and instead use > the generated one untill someone comes along with a clever idea to fix > the issue or can show that it's mostly hermless.
I could understand you in case that Linux would do some basic consistency checks in the iso-9660 code already.....
Show me another program besides mkisofs that implements inode numbers _and_ does it wrong.
Jörg
-- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily - 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/
| |