Messages in this thread | | | Date | Fri, 11 Apr 2003 16:26:59 -0700 | From | Joel Becker <> | Subject | Re: [ANNOUNCE] udev 0.1 release |
| |
On Fri, Apr 11, 2003 at 12:38:49PM -0700, Kevin P. Fleming wrote: > No doubt. And then you get into the situation where the devices themselves > have names and/or UUIDs, and you want that to be incorporated into the > device name. As it stands today, the only way to achieve that is pass that > information to device-mapper so it can create devices with those names.
Oh, I don't want that ever in the name. I don't want to have to know much about my disks, except that once the association is there, it's there until I delete it.
> Personally, I wouldn't be upset if _all_ "physical volumes" (meaning an > accessible block devices or portion thereof) appeared under /dev/volume/... > Even logical volumes could be done that way, since they have names as well. > I don't really see the need to have "whole disks", "partitions" and other > types of volumes in separate directories under /dev, but then I may be way > off base with the rest of the world wants to do :-)
There are multiple reasons. I need to know what's a disk so I can configure it. I need to know what's a partition or a logical volume so I can put filesystems on it. It's always fun these days when folks try to use 'whole disks' and 'partitions' as equivalent things. They are indeed from a block device standpoint, but they aren't from an administration standpoint.
Joel
--
Life's Little Instruction Book #99
"Think big thoughts, but relish small pleasures."
Joel Becker Senior Member of Technical Staff Oracle Corporation E-mail: joel.becker@oracle.com Phone: (650) 506-8127 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |