From owner-freebsd-hackers  Fri Oct  1 11:35:29 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from postal1.lbl.gov (postal1.lbl.gov [128.3.7.82])
	by hub.freebsd.org (Postfix) with ESMTP id A7EA3153EF
	for <hackers@FreeBSD.ORG>; Fri,  1 Oct 1999 11:35:12 -0700 (PDT)
	(envelope-from jin@george.lbl.gov)
Received: from SpamWall.lbl.gov (localhost [127.0.0.1])
	by postal1.lbl.gov (8.9.3/8.9.3) with ESMTP id LAA06829
	for <hackers@FreeBSD.ORG>; Fri, 1 Oct 1999 11:35:09 -0700 (PDT)
From: jin@george.lbl.gov
Received: from george.lbl.gov (george.lbl.gov [131.243.2.12])
	by SpamWall.lbl.gov (8.9.3/8.9.3) with ESMTP id LAA06210;
	Fri, 1 Oct 1999 11:33:46 -0700 (PDT)
Received: (from jin@localhost)
	by george.lbl.gov (8.9.1b+Sun/8.9.1) id LAA20871;
	Fri, 1 Oct 1999 11:33:46 -0700 (PDT)
Date: Fri, 1 Oct 1999 11:33:46 -0700 (PDT)
Message-Id: <199910011833.LAA20871@george.lbl.gov>
To: bmah@CA.Sandia.GOV
Subject: Re: SCSI disk naming problem
Cc: hackers@FreeBSD.ORG, narvi@haldjas.folklore.ee
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

bmah@CA.Sandia.GOV wrote:
> If memory serves me right, jin@george.lbl.gov wrote:
> > > See LINT on details of how to wire down scsi devices...
> > > 
> > > Your proposal doesn't take adding a second scsi card into account.
> > 
> > Well, I did not mean that has to be da0, da1, etc., but similar thing
> > like dac0t0d0, dac0t1d0, ... dac3t4d0, etc. which is much clear what
> > disk is.
> > A few people does not like this one because the name is long, and it
> > is like some commerical configuration. They said that this is Free
> > software.
> 
> 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
narvi@haldjas.folklore.ee 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.

> > Manually wiring down disks is OK for a small set of hosts. 100+ hosts
> > with two or three controllers with 100 TB disks will be terribly pain
> > during the setup and maintenance.
> 
> It depends on what you mean by "manually".  Presumably, these 100+ 
> hosts have fairly similar kernel configurations, so you only need to 
> build a small number of "wired down" kernels, and then distribute these 
> out to the hosts.
> 
> I've found that that having wired down SCSI devices is a Good Thing
> (TM), and it's one of the first things that I fix when I start building
> kernels for a new version of FreeBSD.  I guess I've just gotten used to 
> it.
> 
> Bruce.

I guess you missed the point that I do want to wire down the name.
This is the original debate. But, I do not want to wire down the
name by hand. The system should be able to take care this simple
thing. As you mentioned, digit UNIX does it, Solaris does it, why
not FreeBSD? Because it is FreeWare so we cannot do some thing good
as commercial UNIXs do?

	-Jin



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