![]() | |||||||||||||
Messages in this thread |
On 6/21/05, Pavel Machek <pavel@ucw.cz> wrote:
> >
> > An emotional argument again. What's "strange" about it?
>
> Not so emotional argument...
>
> System where users can mount their own filesystems should not be
> called "Unix" any more. It introduces new mechanism, similar to
> ptrace.
I think that's a rather severe statement. I don't see allowing user
mounts damaging standard UNIX system semantics as long as certain
rules are followed. After all, user-mounts and private name spaces
are what the original authors of UNIX went on to develop.
> It restricts root in ways not seen before. How is
> updatedb/locate supposed to work on system with this? How is it going
> to interact with backup tools?
>
I think requiring user-mounts to be in private name spaces solves many
of these issues -- you don't have to worry about system daemons and/or
other users wandering into synthetic file systems.
-eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
| ||||||||||||
| Last update: 2005-06-22 16:54 [from the cache] ©2003-2008 | |||||||||||||