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

Attachment: pgpAow2eTGrPS.pgp
Description: PGP signature

---

• Follow-Ups:
  • Re: fs/Kconfig question regarding CONFIG_BLOCK
    • From: Jan Engelhardt <[email protected]>

• References:
  • fs/Kconfig question regarding CONFIG_BLOCK
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: Re: potential mem leak when system is low on memory
• Next by Date: Re: [RFC] Cpuset: explicit dynamic sched domain control flags
• Previous by thread: fs/Kconfig question regarding CONFIG_BLOCK
• Next by thread: Re: fs/Kconfig question regarding CONFIG_BLOCK
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]