Date: Mon, 07 Sep 1998 09:16:50 -0500 From: Chris Csanady <ccsanady@friley-185-114.res.iastate.edu> To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM device naming.. Message-ID: <199809071416.JAA06605@friley-185-114.res.iastate.edu> In-Reply-To: Your message of "Sun, 06 Sep 1998 20:51:26 PDT." <Pine.LNX.4.02.9809062049180.2392-100000@feral-gw>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >On Sun, 6 Sep 1998, Chris Csanady wrote: > >> As the device naming is different in CAM anyways, would there be any >> possibility of taking it one step further? I have found it to be >> quite nice in other OS's that actually use subdirectories for disk >> names, terminals, etc. It makes /dev a much cleaner place imho. >> >> Also, I would love for the names to actually be based upon the >> scsi controller, id, lun, partition etc.. although, I suppose there >> is no way in hell this will happen. :P It sucks when a disk goes >> away, and then every last entry in your fstab is incorrect though. > >In a multipathing environment this is not right. It has no meaning >on fibre fabrics. I'm sorry, but I don't follow here. I was under the impression that the cam layer was intended for scsi.. >I really strongly suggest that leaving the names the way they >are right now is fine until a suitable volume binder exists. The thing I don't like about the current scheme is that a particular device name, in no way corresponds to a particular device. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809071416.JAA06605>