lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 24 Aug 2006 18:09:26 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	David Howells <dhowells@...hat.com>, Jens Axboe <axboe@...e.de>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] BLOCK: Make it possible to disable the block layer

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 and too many ways for 
people to create non-working kernels.

There's no need for additional traps.

> dwmw2

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ