Roland McGrath <[EMAIL PROTECTED]> writes:
Hello,
>> The first question was: If shadowfs supports having an explicitely
>> specified writable filesystem[0], shadowfs might has to create whole
>> directory hierarchies - how can this be done? (Or should it be done at
>> all?.)
>
> In a shadowfs th
> However, this assumes that shadowfs always has at least the permissions of
> the user. If for example root wants to create a directory, he can not do it
> through shadowfs if it runs as a user, he will not be able to do it through
> shadowfs, right? Not that this is a big problem, as root is a
On Fri, Oct 12, 2001 at 05:12:12AM -0400, Roland McGrath wrote:
> I think I disagree with all of your conclusions
Only because you thought of io_restrict_auth, and we didn't :-P
I am very glad to hear that there is a solution.
> So,
> use io_restrict_auth to get a port to the writable underlyin
> there was a discussion about Shadowfs' write support on IRC (#hurd @
> openprojects.net) and Marcus suggested to post the conclusions - so
> here they are.
I think I disagree with all of your conclusions, but I'm very glad you've
been talking about the subject. (I hope this means someone wants
Hello,
there was a discussion about Shadowfs' write support on IRC (#hurd @
openprojects.net) and Marcus suggested to post the conclusions - so
here they are.
The first question was: If shadowfs supports having an explicitely
specified writable filesystem[0], shadowfs might has to create whole
d
