Re: what's next for the linux kernel?

[Valdis.Kletnieks@vt.edu]

On Wed, 05 Oct 2005 11:09:42 BST, Luke Kenneth Casson Leighton said:
> On Wed, Oct 05, 2005 at 01:22:33AM +0000, D. Hazelton wrote:
> > On Tuesday 04 October 2005 19:47, Marc Perkel wrote:
> 
> > As someone else pointed out, this is because unlinking is related to 
> > your access permissions on the parent directory and not the file.
>  
>  that's POSIX.
> 
>  i trust that POSIX has not been hard-coded into the entire design of
>  the linux kernel filesystem architecture _just_ because it's ... POSIX.

No, what got hard-coded were the concepts of inodes as the actual description
of filesystem objects, directories as lists of name-inode pairs, and the whole
user/group/other permission thing.  "unlink depends on the directory
permissions not the object unlinked" has been the semantic that people depended
on ever since some code at Bell Labs started supporting tree-structured
directories and multiple hardlinks.  POSIX merely codified existing behavior in
this case.

Attachment: pgp0q8wS8iAyT.pgp
Description: PGP signature