From owner-freebsd-scsi Tue Mar 30 22: 4: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 07AC514E88 for ; Tue, 30 Mar 1999 22:04:01 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id BAA24884; Wed, 31 Mar 1999 01:03:20 -0500 (EST) Date: Wed, 31 Mar 1999 01:03:20 -0500 (EST) From: "Matthew N. Dodd" To: Kurt Seel Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sd device numbering In-Reply-To: <37015B8B.6DDC0429@utcorp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 30 Mar 1999, Kurt Seel wrote: > Is there some config file magic to lock an sd dev to a scsi id? i.e. > scsi 0 -> sd0 > scsi1 -> sd1 > scsi2 -> sd2 > So that if I pull scsi 1 out, it looks like this : > scsi 0 -> sd0 > scsi 2 -> sd2 > sd1 'disappears' and my fstab remains valid for all the other drives. You can wire your SCSI devices down. Check LINT for details. I'd really love to see something like Solaris has hung off of DEVFS that would automagically present devices in the form of /dev/dsk/busX/targY/lunZ/... But that ends up being too long which leads me to think that assign a 'name' to the device and presenting it under /dev/dsk/{name} would be the way to go. But that would imply both DEVFS and SLICE which doesn't seem all that likely at this point. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message