Re: RFC: i386: kill !4KSTACKS

From: Willy Tarreau
Date: Mon Sep 05 2005 - 00:02:10 EST


On Mon, Sep 05, 2005 at 12:47:03AM -0400, Sean wrote:
> On Mon, September 5, 2005 12:36 am, Willy Tarreau said:
>
> > Well, to be fair, most laptop users today are in companies which provide
> > them with the model the staff has chosen for all the employees. And
> > employees
> > try to install Linux on them anyway. That's how you end up with things
> > like
> > ndiswrapper, because the people who make those notebooks for companies
> > don't
> > care at all about their customers ; what they want is negociate with the
> > staff to sell them 2000 laptops, and that's all.
>
> Companies that provide laptops to their employees tend to frown on the
> users installing a bunch of stuff anyway.

But how do you think Linux has penetrated the enterprise market ???
We all have put dual boots on every windows machine we had access to,
eventhough this was clearly forbidden. And after repeatedly showing
to the staff that you saved their day with your Linux, they finally
start to get interested to it. One of my best customers has finally
bought about one hundred RHEL3 licences to replace amateur installs
on production machines. They would never have looked at it without
us braving unauthorized dual boots.

> If the company was buying the
> laptop to run Linux it would be spec'd appropriately.
>
> But the real crux of the argument here is not whether or not people should
> ever use binary-only drivers, it's whether the open source kernel
> developers should spend any time worrying about it or not.

I think we should not worry about it, but we should not deliberately break
it in a stable series when that does not bring anything. The fact that
Adrian proposed to completely remove the option is sad. It's in the windows
world that you can't choose. In Linux, you make menuconfig and choose what
suits your needs.

Regards,
Willy

-
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/