From: Adrian Bunk <bunk@stusta.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
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 19:07:09 +0200 [thread overview]
Message-ID: <20060824170709.GO19810@stusta.de> (raw)
In-Reply-To: <20060824164752.GC5205@martell.zuzino.mipt.ru>
On Thu, Aug 24, 2006 at 08:47:52PM +0400, Alexey Dobriyan wrote:
> On Thu, Aug 24, 2006 at 06:09:26PM +0200, Adrian Bunk wrote:
> > On Thu, Aug 24, 2006 at 05:00:16PM +0100, David Woodhouse wrote:
> > > On Thu, 2006-08-24 at 17:58 +0200, Adrian Bunk wrote:
> > > > There's no reason for getting linux-kernel swamped with
> > > > "my kernel doesn't boot" messages by people who accidentally disabled
> > > > this option.
> > >
> > > By that logic, you should make it necessary to set CONFIG_EMBEDDED
> > > before you can set CONFIG_EXT3 != Y or CONFIG_IDE != Y too.
> >
> > That's the difference between Aunt Tillie and a system administrator:
> > A system administrator knows which filesystems he wants to use.
> >
> > > However you dress it up, it's pandering to someone who either lacks the
> > > wit, or just can't be bothered, to _look_ at what they're doing when
> > > they configure their kernel. And it's a bad thing.
> >
> > We already have too many user visible options
>
> Examples please.
>...
Do a "make menuconfig" and look at the number of options.
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.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-08-24 17:07 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 [this message]
2006-08-24 17:16 ` David Woodhouse
2006-08-24 17:34 ` Randy.Dunlap
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=20060824170709.GO19810@stusta.de \
--to=bunk@stusta.de \
--cc=adobriyan@gmail.com \
--cc=axboe@suse.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
Powered by JetHome