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

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 17:00:16 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Adrian Bunk <bunk@...sta.de>
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, 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.

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.

-- 
dwmw2

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