Re: udev device naming policy concerns
Theodore Ts'o <email@example.com> writes:
> On Sat, Apr 03, 2004 at 12:00:48AM +0200, Goswin von Brederlow wrote:
> > Won't work for cdroms, partition formats without UUID,
> > filesystems without label .... but lets ignore those for a moment.
> (1) Removeable medias have their own problem since what's important is
> generally not *which* CD-ROM player/drive, but *which* CD-ROM has been
> inserted, regardless of which drive the CD-ROM happened to be inserted
At university we have an automounter that will put CDs under
/cdrom/<name> and "eject <name>" will eject the said cdrom.
Once you figure it out its a nice feature.
> (2) ISO 9660 and do have label support. Mount doesn't support it yet,
> but there are patches that convert it to use the blkid library, and it
> woudln't be that hard to add label support for CD-ROM's. This would
> actually be far more useful, since we could now mount the CD-ROM in a
> different location based on the contents of the CD-ROM, rather than
> based on the CD-ROM's SCSI id or position in the SCSI chain, both of
> which are equally wrong, although simpler.
> (3) Most filesystems have UUID's and/or Labels at this point.
> > If you use this argument you should be in support of using LABEL= or
> > UUID= when creating the fstab in the Debian-Installer, right?
> Correct, I would be in favor of doing this, since it correctly solves
> the problem even if the SCSI id of the device changes. This will
> become even more important if people are using devices that are based
> on Firewire or USB, where the SCSI id is even more subject to change,
> and therefore just as useless as "/dev/sda". You really should be
> mounting based on filesystem UUID or Label.
> - Ted
Its always intresting to see people react to "use LABEL= or UUID="
when they come and ask how to solve the changing name issue. Most
users are completly unaware thats even possible.