On Fri, Apr 11, 2003 at 12:28:27PM -0700, Joel Becker wrote:> On Fri, Apr 11, 2003 at 11:31:28AM -0700, Kevin P. Fleming wrote:> > - if any partitions are found, they are registered with the kernel using > > device-mapper ioctls> > - because these new "mapped sections" of the drive are _also_ usable block > > devices in their own right, they generate hotplug events> > In reality, we need /dev/disk0 for disks, and /dev/part0 for> partitions, and /dev/lv0 for logical volumes from the LVM.

Well, that's maybe what _you_ want to call your disks and partitions,but not what I want to call them :)

> There's going to be a war over this naming, and that's why this is> hard.

No, there isn't. That's what I am trying to completely avoid with udev.It will allow you to plug in whatever device naming scheme that youwant. This will keep all of the disc vs. disk flamewars from everyhappening in the kernel community (well, I can hope...)

I'll be providing a small default name scheme that happens to match thecurrent Documentation/devices.txt names, and possibly a devfs namingscheme for those people who like that scheme. After that, it will bequite easy for you to create a Oracle naming scheme where you givedifferent prefixes to your partitions vs. disks.

This scheme allows you to use databases, flat files, or even send amessage across the network to a admin console to get the name of a newdevice. Much more flexible than setting a kernel naming scheme, andmoves this whole argument and policy out of the kernel.