Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Jul 2000 16:43:28 -0700 (PDT)
From:      Matthew Jacob <mjacob@feral.com>
To:        "Kenneth D. Merry" <ken@kdm.org>
Cc:        Poul-Henning Kamp <phk@critter.freebsd.dk>, Jack Rusher <jar@integratus.com>, freebsd-arch@FreeBSD.ORG
Subject:   Re: SANs, disks, & devfs
Message-ID:  <Pine.BSF.4.05.10007241634440.15581-100000@semuta.feral.com>
In-Reply-To: <20000724163141.A58251@panzer.kdm.org>

next in thread | previous in thread | raw e-mail | index | archive | help

> I think that might be good for a first shot at it, but it might be nice to
> eventually have a way of dealing with more than just CAM-attached devices.
> 
> e.g., you could have some sort of generic kernel registry/database/list
> that each peripheral driver instance would register itself with, along
> with a serial number of some sort.
> 
> da0 would register its serial number of ABC138557232, and da1 would
> register its serial number of XyZ138475393, and ad0 would register its
> serial number of XLP83733312.
> 
> You could have a name located in the disklabel take precendence over an
> in-disk serial number if it is present, and possibly have an automatically
> generated serial number to name table that is loaded in by the loader.  So
> you could have a name for your tape drive, even though you can't put a
> disklabel on it.  (Such a table might be generated by sysinstall, or by
> some other program.)
> 
> You'd probably also want to have a way to include positional information as
> a qualifying argument for the case where you have more than one device with
> identical identifiers.  So if you had two disks with the name "Fred" in the
> disklabel, you would need to call one "Fred@scbus0:1:0" and the other
> "Fred@scbus1:3:0".
> 
> If you had two identical disklabel names, you could conceivably qualify
> them by the disk serial number, if available, but otherwise you'd have to
> fall back on the positional information.

All of this is good- and useful. Some of which is addressed in a full devfs.
Some of which in possibly enhancing vinum. 

I'm looking right for a short term solution unless the others show up (which I
haven't the time nor charter to chase).

-matt




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10007241634440.15581-100000>