From: Jens Axboe <jens.axboe@oracle.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Valdis.Kletnieks@vt.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: fs/Kconfig question regarding CONFIG_BLOCK
Date: Tue, 17 Oct 2006 21:36:45 +0200 [thread overview]
Message-ID: <20061017193645.GM7854@kernel.dk> (raw)
In-Reply-To: <Pine.LNX.4.61.0610172119420.928@yvahk01.tjqt.qr>
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
next prev parent reply other threads:[~2006-10-17 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 18:41 fs/Kconfig question regarding CONFIG_BLOCK Jan Engelhardt
2006-10-17 18:57 ` Valdis.Kletnieks
2006-10-17 19:21 ` Jan Engelhardt
2006-10-17 19:36 ` Jens Axboe [this message]
2006-10-17 19:47 ` Jan Engelhardt
2006-10-18 7:09 ` Jens Axboe
2006-10-18 17:56 ` Randy Dunlap
2006-10-19 12:20 ` Jens Axboe
2006-10-21 0:14 ` Horst H. von Brand
2006-10-21 0:17 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2006-10-17 18:38 Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061017193645.GM7854@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.