On Friday 24 August 2007 3:36:54 pm Jan Engelhardt wrote:
> On Aug 24 2007 22:34, Jan Engelhardt wrote:
> >On Aug 24 2007 15:17, Rob Landley wrote:
> >>CONFIG_BLOCK disables the block layer.
> >>CONFIG_BLK_DEV disables the block devices.
> >
> >menuconfig BLK_DEV
> > bool "Block devices"
> > depends on BLOCK
> > default y
> > ---help---
> > Say Y here to get to see options for various different block
> > device drivers. This option alone does not add any kernel code.
> >
> > If you say N, all options in this submenu will be skipped and
> > disabled only do this if you know what you are doing.
> >
> >>Is there _ever_ a time you want the block layer but no block devices?
>
> Well, where do you think your hard disk drivers come from? Definitely
> not from the BLK_DEV menu...
Actually I hadn't looked that far into it. Juggling seven things yesterday
and offline most of today, and what I actually _noticed_ was that my
miniconfig that had worked unchanged to build UML since 2.6.12 finally broke
on a kernel upgrade, and I have no idea what the actual reason for the change
is other than possibly aesthetics. Oh well.
Now that I look I see that all the devices in this menu (at least in User Mode
Linux) are actually virtual block devices (UBD, loopback, and ramdisk), which
the menu help doesn't indicate.
Now I'm trying to think of a better user interface way of cross-referencing
this sort of thing. Network block devices live in the networking menu,
device drivers for hardware live off in another menu. What I really want is
a way to dynamically create menus via search critiera: "Show me all the block
devices"...
Also "here's a symbol, show me a menu containing everything else that is
either required by or enabled by this symbol..." That sounds like a more
powerful abstraction, since the previous one is "show me everything that
depends on CONFIG_BLOCK".
(I wonder if this would be a largeish rewrite of the menuconfig
infrastructure? Hmmm...)
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/
[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]
