Re: [PATCH] private mounts

[Bryan Henderson]

>> Just to be clear, then: this idea is fundamentally different from the 
>> mkdir/cd analogy the thread starts with above.
>
>NACK, it's very similar to the cd "$HOME" (or ulimit calls) done by the
>login mechanism,

That's not a NACK.  The cd "$HOME" and ulimit calls done by the login 
process (more precisely, by a shell profile) are quite different from the 
mkdir/cd the thread started with.  Who creates a new directory in his 
shell profile?  I assume the mkdir/cd analogy is a case of a person doing 
a mkdir and cd in a running shell.  (That is indeed analogous to what one 
would like to do with a private mount).

When you said "by the login process or by wrappers like nice," in response 
to my pointing out that setnamespace would need to be a shell builtin 
command, I assumed you were talking about putting it in the code that 
execs the shell as opposed to in the shell profile, thus eliminating the 
need for a shell builtin.

But the important thing is just to recognize, as you say explicitly now, 
that setnamespace has to be shell builtin command for 
setnamespace/mknamespace to be analogous to mkdir/cd.  That was my 
original statement, if somewhat indirect:

>> >> >mknamespace -p users/$UID # (like mkdir -p)
>> >> >setnamespace users/$UID   # (like cd)
>> >>                               ^^^^^^^^
>> >> You realize that 'cd' is a shell command, and has to be, I hope. 
That 
>> >> little fact has thrown a wrench into many of the ideas in this 
thread.

--
Bryan Henderson                          IBM Almaden Research Center
San Jose CA                              Filesystems
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/