Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932202AbVIEEgT (ORCPT ); Mon, 5 Sep 2005 00:36:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932203AbVIEEgT (ORCPT ); Mon, 5 Sep 2005 00:36:19 -0400 Received: from willy.net1.nerim.net ([62.212.114.60]:27666 "EHLO willy.net1.nerim.net") by vger.kernel.org with ESMTP id S932202AbVIEEgT (ORCPT ); Mon, 5 Sep 2005 00:36:19 -0400 Date: Mon, 5 Sep 2005 06:36:14 +0200 From: Willy Tarreau To: Sean Cc: Alex Davis , linux-kernel@vger.kernel.org Subject: Re: RFC: i386: kill !4KSTACKS Message-ID: <20050905043613.GD30279@alpha.home.local> References: <35547.10.10.10.10.1125892279.squirrel@linux1> <20050905040311.29623.qmail@web50204.mail.yahoo.com> <50570.10.10.10.10.1125893576.squirrel@linux1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50570.10.10.10.10.1125893576.squirrel@linux1> User-Agent: Mutt/1.5.10i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3019 Lines: 59 Hi, On Mon, Sep 05, 2005 at 12:12:56AM -0400, Sean wrote: > On Mon, September 5, 2005 12:03 am, Alex Davis said: > > > > What if you don't have a choice? When someone comes to me with their > > laptop > > containing a built-in wireless card not natively supported by Linux, am I > > supposed to tell them "go buy a Linux-supported card" when there's a way > > I can make their existing card work? I don't think so. > > You always have a choice in life. Nobody is stopping you from doing what > _you_ choose to do. That doesn't mean that developers who are concerned > with the creation and promotion of open source should care one whit about > your particular take on the situation. Go do whatever you want just > don't expect the open source developers to pay for it; you maintain the > crufty patches yourself. 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. However, those employees generally start with "easy to install" distros, such as fedora or similar. Those don't ship with standard kernels anyway, and they provide what is necessary to stay compatible with the tools which support crappy hardware. So (and it's sad), all those people don't care at all about kernel development, nor do they care about 2.6.13, 2.6.14, etc... It's just *us* who tell them "ah, you can't do that because you use a prehistorical kernel, let me install you the last one", and then and only then, that fails and we whine about the crappy hardware and the "easy to install" distro which seem to be made to work together. So I tend to consider that ndiswrapper users won't care about what will be in 2.6.14, but only about the fact that *their distro* will still support ndiswrapper. Of course, it would have been easier if the kernel would have stabilized and was only in maintenance mode, not breaking anything on every new release, but Linus has decided differently, so be it. Those users did not have a choice in the beginning, otherwise they would have chosen a laptop supported by Linux. And honnestly, I know plenty of them. In fact, it's the other way around. I know very few people who can actually choose their laptop. So you're both half-right from your point of view. But you're both half-wrong too : no, people can't always choose, and no, people who don't choose their laptop are not impacted by development kernels. So let's turn the page and wait for a stable kernel. Regards, Willy - 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/