Yes; Eric Youngdale wrote a program called scsidev which does it for
SCSI devices.
> > > Putting devices in "scan order" never made sense to me. Why should
> > > the first SCSI drive scanned be /dev/sda? What happens when I switch
> > > the cables and drives around. Same filesystems, but the devices have
> > > all changed.
> >
> > And this doesnt need kernel help either. In fact using device scan
> > order is often more convenient than device position. When it comes
> > to volume management of a big system both of these (and Solaris)
> > are equally dumb approaches.
>
> Convenient for whom? Kernel programmers or admins/users?
>
> What would you suggest as a smart approach to volume management?
>
> > It all comes down to
> >
> > mount `wherehasitgone --uuid=blah` /mnt/mydisk
> >
> > And wherehasitgone is a tool to walk the disk tree and find a
> > volume by uuid and/or maybe ask LDAP/NIS maps to find it via NFS
>
> What would this look like in /etc/fstab?
>
Probably something like:
uuid:"blah" /mnt/mydisk ...etc...
Yes, support needs to be added for it, but it is the right way to
solve this problem; *most* reconfigurations of systems large enough
for this to be an issue at all involve controller, bus, and/or ID
changes, which means that volume labels and uuids are what matters,
not "location".
-hpa
--
PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74
See http://www.zytor.com/~hpa/ for web page and full PGP public key
I am Bahá'í -- ask me about it or see http://www.bahai.org/
"To love another person is to see the face of God." -- Les Misérables
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html