On Mon, 22 May 2006, Adrian Bunk wrote:
>
> Is it a new policy that the kernel mustn't break any buggy userspace
> code?
It's not a new policy, dammit.
Guys, a kernel developer who cannot understand that user space is
important should just drop their pretentions of being a kernel developer,
and go play with some toy system like Hurd instead. There you can say
"user space doesn't matter".
The kernel has _one_ mission in life, and one mission only. Guess what
that is? It's to be the buffer between user space and shared resources.
That's it. NOTHING ELSE MATTERS.
If the kernel breaks user space, the kernel is broken. End of story.
Yes, there are reasons we must occasionally allow for it anyway, but they
should all be some pretty damn major ones. Like "we simply _had_ to, there
was no choice, because the alternatives broke user space more".
Which isn't even _remotely_ the case here.
The whole point of a kernel is that it doesn't do anything for itself.
It's there to serve user space.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
