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]

Message-ID: <20060824155814.GL19810@stusta.de>
Date:	Thu, 24 Aug 2006 17:58:14 +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 04:44:34PM +0100, David Woodhouse wrote:
> On Thu, 2006-08-24 at 17:29 +0200, Adrian Bunk wrote:
> >         bool "Enable the block layer" depends on EMBEDDED 
> 
> Please. no. CONFIG_EMBEDDED was a bad idea in the first place -- its
> sole purpose is to pander to Aunt Tillie.

It's not for Aunt Tillie.
It's for an average system administrator who compiles his own kernel.

CONFIG_BLOCK=n will only be for the "the kernel must become as fast as 
possible, and I really know what I'm doing" people.

There's no reason for getting linux-kernel swamped with
"my kernel doesn't boot" messages by people who accidentally disabled 
this option.

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