On 4/20/05, Miklos Szeredi <[EMAIL PROTECTED]> wrote:
>
> The user expects to have the see the same files in all sessions,
> whether those be local logins, remote logins, ftp/scp/etc sessions.
>
>
> A single global namespace makes perfect sense here. Why do people
> want private namespaces?
>
I disagree with this, I think there are plenty of situations where I
may want to have several different namespaces for several different
sessions. Once you unlock namespace manipulation for users, all sorts
of new models of how to interact with the system fall out of that
capability.
Not to mention the fact that if you accidentally screw up your private
name space, fixing it is as easy as exiting that shell (or closing
that window, etc.) Could you imagine if your PATH environment
variable was shared between all your shells and logins? A simple typo
when extending your PATH in a single shell would screw all your
sessions.
-eric
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
