Re: /proc/scsi/map

[Chris Adams]

Once upon a time, Doug Ledford  <[e-mail]> said:
>Umm, this patently fails to meet the criteria you posted of "stable device 
>name".  Adding a controller to a system is just as likely to blow this 
>naming scheme to hell as it is to blow the traditional linux /dev/sd? 
>scheme.  IOW, even though the /proc/scsi/map file looks nice and usefull, 
>it fails to solve the very problem you are trying to solve.

I use OSF/1^WDigital Unix^WCompaq^WHP Tru64 Unix here at work, and with
version 5, they've got a nice persistent device naming system (I don't
claim to know how it works however).  The first hard drive found is
/dev/disk/dsk0, the second is /dev/disk/dsk1, etc.  It doesn't matter
how you get to the drive (which is important if you want multipathing -
the controller and bus should NOT figure into the device name or you are
going to have problems).  If you remove dsk0, there won't be another
dsk0 (unless you clean it out of the device database).

-- 
Chris Adams <[e-mail]>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.