On Sat, Oct 02, 1999 at 01:15:53PM +0300, Narvi wrote:
>
> On Fri, 1 Oct 1999 [EMAIL PROTECTED] wrote:
>
> > [EMAIL PROTECTED] wrote:
>
> [snip]
>
> > >
> > > That's an interesting argument on the part of a few people. The
> > > commercial UNIX I first adminned had wired down, short names for disks
> > > (rz0, rz1, rz2, ... ). This was very nice.
> >
> > This one does not resolve the controller problem either as
> > [EMAIL PROTECTED] said.
> >
> > So, I guess dac0t0, dac0t1, ... dac3t4, will be good enough if we want
> > to be short, but anything shorter than this will be meaningless.
> >
>
> As long as you don't move a hard disk from one bus on the controller to
> the other 8-)
Yes something like dac0t0... is realy nice - but AFAIK it's not general enough
for fibre channel.
The main point is that I only see this problem with removeable disks and
other kind of SCSI-devices, which I usually wire down.
Most of my fixed disks are running with vinum.
vinum is able to handle if a drive has changed it's ID and/or name.
It's an important thing to have something like this if you want to be able
to hotplug a drive (or power up later). Sometimes it's getting another name
than it would have after reboot!
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
