On Mon, 14 Jul 1997, Michael Neuffer wrote:
> On Sun, 13 Jul 1997, Harald Milz wrote:
>
> > Date: Sun, 13 Jul 1997 15:54:00 +0200
> > From: Harald Milz <hm@seneca.muc.de>
> > To: linux-kernel@vger.rutgers.edu
> > Subject: Re: kernel-managed /dev, revisited
> >
> > Teunis Peters (teunis@usa.net) wrote:
> > >
> > > Now that I think about it though, I toss in a vote for:
> > > s<?><id><lun>
> > > on naming though (eg tape on ID 4 lun 0 == st40 or the like)
> >
> > Err - this limits you to 9 LUNs per SCSI ID. Please don't do it... SSA will
> > allow many, many disks per (virtual mapped) SCSI ID and would definitely
> > not profit from it!
> >
> > It's easier to unambiguously parse something like
> > s<host>i<target id>l<lun>
>
> This would be incomplete, since a controller can have more then one bus,
> it would have to be:
>
> s<host>c<channel>i<target id>l<lun>
OK, I can get my teeth into the above scheme.
Suggestion instead of 's' use 'h' for host, this
will allow the scheme to be utilized for -all- disk
types rather that just scsi.
One more suggestion, Have an option to allow for somesort
of verbosity , Please. like ... (Yes I know links could be used)
'type'-host#<host>,channel#<channel>,id#<target id>,lun#<lun>
scsi-host#1,channel#2,id#3,lun#4
ide-host#1,channel#2,id#3,lun#4 < never know may happen ;-)
mscp-host#1,channel#2,id#3,lun#4 < Will happen ;-)
'...'-host#1,channel#2,id#3,lun#4
You get the picture.
Tia, JimL
+-----------------------------------------------------------------------+
| James W. Laferriere - Network Engineer - babydr@nwrain.net |
| System Techniques - 25416 - 22nd S. - Kent, WA 98032 |
| Give me VMS -or- Give me Linux -but- only on AXP |
+-----------------------------------------------------------------------+
|-> Linux-Vax Port, Still in Progress . IE: No Progress To Report ;-) <-|
+-----------------------------------------------------------------------+