From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Randy.Dunlap" Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer Date: Thu, 24 Aug 2006 10:34:59 -0700 Message-ID: <20060824103459.77e5569c.rdunlap@xenotime.net> References: <32640.1156424442@warthog.cambridge.redhat.com> <20060824152937.GK19810@stusta.de> <1156434274.3012.128.camel@pmac.infradead.org> <20060824155814.GL19810@stusta.de> <1156435216.3012.130.camel@pmac.infradead.org> <20060824160926.GM19810@stusta.de> <20060824164752.GC5205@martell.zuzino.mipt.ru> <20060824170709.GO19810@stusta.de> <1156439763.3012.155.camel@pmac.infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Adrian Bunk , Alexey Dobriyan , David Howells , Jens Axboe , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Return-path: Received: from xenotime.net ([66.160.160.81]:58295 "HELO xenotime.net") by vger.kernel.org with SMTP id S1030395AbWHXRbs (ORCPT ); Thu, 24 Aug 2006 13:31:48 -0400 Received: from midway.site ([71.117.233.155]) by xenotime.net for ; Thu, 24 Aug 2006 10:31:47 -0700 To: David Woodhouse In-Reply-To: <1156439763.3012.155.camel@pmac.infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 24 Aug 2006 18:16:03 +0100 David Woodhouse wrote: > On Thu, 2006-08-24 at 19:07 +0200, Adrian Bunk wrote: > > Do a "make menuconfig" and look at the number of options. > > Why would I do that? I haven't done that for _years_. I've just edited > the .config file, removed the line which turns some option on or off, > then run 'make oldconfig'. I get asked about the option in question, and > then if I've turned something on I get asked about other options which > depend on it and which are now possible but weren't before. How do you do that if you have all of ISDN disabled and want/need to enable one ISDN driver? or same problem for V4L(2)/dvb? or several other subsystems? (e.g. sound) > Increasingly, these days, that approach has been failing due to all this > Aunt Tillie crap. I tried turning off CONFIG_KALLSYMS the other day, but > it took me a while to work out how. And the increasing use of 'select' > is even worse. > > > There's e.g. no reason to ask all users whether they want to compile all > > I/O schedulers into their kernel. > > > > To avoid misunderstandings: > > > > I'm not talking about people subscribed to this list. > > > > It's more about a system administrator who must for some reason (e.g. > > hardware support or the requirement of some external patch) compile his > > own kernel. > > Why on earth would they create a config file from scratch instead of > using a defconfig or the config from their distribution and modifying it > so suit their needs? > > For most things, they ought to be able to just build extra modules to > _match_ their distribution's kernel, without having to rebuild the > kernel itself. (Although people doing stupid things in the kernel like > #ifdef CONFIG_foo_MODULE tends to screw them sometimes -- I can't build > IPv6 for my Nokia 770 without replacing its kernel, for example). > > People just don't have that much cause to create configs from scratch -- > there's little benefit in pandering to those who are less able. Make the > _defaults_ sane, by all means -- but don't just start hiding options. > > However you dress it up, it's still ESR's Aunt Tillie come to haunt us. > And it's a PITA. --- ~Randy