Because at this point, the simple upgrade of a kernel, quite literally,
breaks behavior, compared to every single other UNIX out there. (And some
programs my very well DEPEND upon mount returning an error if an FS is
already mounted.
yes, policy belongs in userspace.
however, this "policy" has been set, in previous..
The least we could do, is not break what precedents have been set.
Rule #1) Never change behavior of a userspace app that may already have
been written to depend on something.
Hell, I may be entirely wrong here. But, seems to me that if I write a
userspace program, I'd really like to be able to depend on a particular
interface's behavior, rather than having to go bug hunting every time I
upgrade kernels.
Chad
> Why not?
>
> Since there does not seem to be security issues in there, it's a
> matter of policy. Policy belongs to userspace. So do the test in the
> userspace mount, not in the kernel.
>
> OG.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 31 2000 - 21:00:25 EST