Re: ISO-9660 Rock Ridge gives different links different inums

Mark H. Wood (mwood@IUPUI.Edu)
Wed, 15 Jan 2003 16:07:13 -0500 (EST)


On Fri, 10 Jan 2003, Horst von Brand wrote:
> Peter Chubb <peter@chubb.wattle.id.au> said:
> [...]
> > The problem is that in Unix the fundamental identity of a file is
> > the tuple (blkdev, inum); names are merely indices (links) that resolve to
> > that tuple. Personally, I'd swap to a pair of system calls to map
> > name to (blkdev, inum), and open(blkdev, inum). Think of the inode
> > number as a unique within-filesystem index.
>
> That way any joker can go ahead and open any file, without any regard to
> permission bits on the directories that lead there. Not nice.

Welcome to VMS, which can open files by INDEXF.SYS offset. Some app.s
which create and delete files rapidly never bother to make directory
entries at all. It may not be what you're used to, and it may be contrary
to expected Unix semantics, but it's not unthinkable.

-- 
Mark H. Wood, Lead System Programmer   mwood@IUPUI.Edu
MS Windows *is* user-friendly, but only for certain values of "user".

- 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/