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]

Message-ID: <Pine.LNX.4.61.0610172119420.928@yvahk01.tjqt.qr>
Date:	Tue, 17 Oct 2006 21:21:44 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Valdis.Kletnieks@...edu
cc:	jens.axboe@...cle.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: fs/Kconfig question regarding CONFIG_BLOCK


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

Never mind, I see that some filesystems have 'depends on BLOCK' instead 
of being wrapped into if BLOCK. Not really consistent but whatever.


	-`J'
-- 
-
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/