On Wed, Jun 22, 2011 at 09:07:41PM +0200, Wouter Coene wrote:
> On 22 jun 2011, at 20:53, Kenneth R Westerback wrote:
> > On Wed, Jun 22, 2011 at 06:48:14PM +0200, Wouter Coene wrote:
> >> The patch below builds on the disk UID code to implement disk names. Disk
> >> names must match [a-zA-Z0-9_]{1,10} and are stored encoded as 6 bits per
> >> character into the disklabel UID field. With this patch, you can use disk
> >> names in /etc/fstab:
> >>
> >> bootdisk.a / ffs rw 1 1
> >
> > Why? This seems to add nothing but extra code and increase the
> > chances some twit will name multiple disks 'MYDISK' and screw
> > her/himself royally. Also, DUIDs identify a DISKLABEL and not a
> > disk.
>
> Right now, nothing is stopping you from naming multiple disks 1234567890abcdef
> either. Twits will be twits, I'm just looking for something that's easier to
> type (and remember) than a hex-string.
>
> Also, this is certainly not useless if you have more than a handfull of disks
> or SAN volumes, or for removable media. Which of the following is more
> readable?
>
> mount 1234567890abcdef.a /mnt
> mount backups.a /mnt
For this type of stuff, you are looking for hotplugd(8); And duids make
writing hotplug scripts much easier.
While I do see the allure of having nice names for "disks", this is
problematic (like ken pointed out) so I think I'll have to agree with
ken for now that this is extra code for a very minimal gain.
Anyways, always nice to see diffs!
cheers, thib.
