[prev in list] [next in list] [prev in thread] [next in thread]
List: netbsd-tech-kern
Subject: Re: union mount directory permissions
From: David Laight <david () l8s ! co ! uk>
Date: 2004-09-28 7:09:27
Message-ID: 20040928070927.GA891 () snowdrop ! l8s ! co ! uk
[Download RAW message or body]
>
> * policy: when creating the shadow directory in the
> * upper layer, create it owned by the user who did
> * the mount, group from parent directory, and mode
> * 777 modified by umask (ie mostly identical to the
> * mkdir syscall). (jsp, kb)
>
> uhm.. so, why? File permissions and ownership are copied. Shouldn't
> directories behave the same?
When I wrote a union fs, I created directories with the permissions
of their real parent.
I also deceided that the 'copy file into top layer' action was
unnecessary. Nothing we ran needed it.
I did try to use the feature of SVR4 VOP_OPEN() that allows it to return
a different vnode (use for clone open on special devices) but not all
of the kernel liked me doing that.
David
--
David Laight: david@l8s.co.uk
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic