Re: [PATCH] BLOCK: Make it possible to disable the block layer

From: Adrian Bunk
Date: Thu Aug 24 2006 - 13:04:36 EST


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

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