What's up with CONFIG_BLK_DEV?

CONFIG_BLOCK disables the block layer.
CONFIG_BLK_DEV disables the block devices.

Is there _ever_ a time you want the block layer but no block devices?

(I ask because this is the first time I've had to add a symbol to my User Mode 
Linux miniconfig since 2.6.12, and I can't figure out what the actual purpose 
of this symbol is.)

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: What's up with CONFIG_BLK_DEV?
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: Re: [PATCH] sigqueue_free: fix the race with collect_signal()
• Next by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
• Previous by thread: [PATCH] fix undefined reference to device_power_up/resume
• Next by thread: Re: What's up with CONFIG_BLK_DEV?
• 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]