linux-kernel - Re: fs/Kconfig question regarding CONFIG

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:	Tue, 17 Oct 2006 14:57:52 -0400
From:	Valdis.Kletnieks@...edu
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	jens.axboe@...cle.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: fs/Kconfig question regarding CONFIG_BLOCK

On Tue, 17 Oct 2006 20:41:41 +0200, Jan Engelhardt said:

> fs/Kconfig has:
> 
> if BLOCK
> menu "DOS/FAT/NT Filesystems"

> Why is it wrapped into BLOCK, or, why are all of the other filesystems 
> which require a block device?

Some filesystems (such as /proc, /sys, and so on - basicaly, the "pseudo" file
systems) are able to stand by themselves.  Filesystems that read actual blocks
of data off actual media will require the services of the block layer to do
that.  So if you've built a tiny embedded kernel that doesn't include the block
layer, you can't read those sorts of filesystems....

Content of type "application/pgp-signature" skipped