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 21:36:45 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	Valdis.Kletnieks@...edu,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: fs/Kconfig question regarding CONFIG_BLOCK

On Tue, Oct 17 2006, Jan Engelhardt wrote:
> 
> >> 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.

Feel free to send in patches that make things more consistent.

-- 
Jens Axboe

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