mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Adrian Bunk <bunk@stusta.de>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	David Howells <dhowells@redhat.com>, Jens Axboe <axboe@suse.de>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer
Date: Thu, 24 Aug 2006 10:34:59 -0700	[thread overview]
Message-ID: <20060824103459.77e5569c.rdunlap@xenotime.net> (raw)
In-Reply-To: <1156439763.3012.155.camel@pmac.infradead.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

  reply	other threads:[~2006-08-24 17:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 13:00 David Howells
2006-08-24 13:13 ` David Woodhouse
2006-08-24 13:34 ` David Howells
2006-08-24 13:40   ` David Woodhouse
2006-08-24 13:54   ` David Howells
2006-08-24 13:47 ` Christoph Hellwig
2006-08-24 14:42 ` Nick Piggin
2006-08-24 15:29 ` Adrian Bunk
2006-08-24 15:44   ` David Woodhouse
2006-08-24 15:58     ` Adrian Bunk
2006-08-24 16:00       ` David Woodhouse
2006-08-24 16:09         ` Adrian Bunk
2006-08-24 16:47           ` Alexey Dobriyan
2006-08-24 17:07             ` Adrian Bunk
2006-08-24 17:16               ` David Woodhouse
2006-08-24 17:34                 ` Randy.Dunlap [this message]
2006-08-24 17:48                   ` David Woodhouse
2006-08-24 17:59                     ` Sam Ravnborg
2006-08-25  6:23                       ` Jan Engelhardt
2006-08-25  7:19                         ` Sam Ravnborg
2006-08-24 18:01                     ` Randy.Dunlap
2006-08-25  6:21                 ` Jan Engelhardt
2006-08-25  6:07               ` Jan Engelhardt
2006-08-25 10:37                 ` Adrian Bunk
2006-08-25 13:09                   ` Alexey Dobriyan
2006-08-24 16:39       ` Jan Engelhardt
2006-08-24 16:44         ` David Woodhouse
2006-08-24 16:48         ` Adrian Bunk
2006-08-24 21:31           ` Johannes Stezenbach
2006-08-25  6:04           ` Jan Engelhardt
2006-08-24 18:39         ` Matthias Schniedermeyer
2006-08-25  6:06           ` Jan Engelhardt
2006-08-24 17:18     ` David Howells
2006-08-24 17:23       ` Adrian Bunk
2006-08-24 16:23 ` Stefan Richter
2006-08-25 12:16 ` Jens Axboe
2006-08-25 13:40 ` David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060824103459.77e5569c.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=adobriyan@gmail.com \
    --cc=axboe@suse.de \
    --cc=bunk@stusta.de \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®