Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!vtserf.cc.vt.edu!csugrad.cs.vt.edu!not-for-mail
From: briggs@csugrad.cs.vt.edu (Allen X Briggs)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: Problem with Julian's SCSI drivers
Date: 16 Sep 1993 15:25:11 -0400
Organization: Virginia Tech Computer Science Dept, Blacksburg, VA
Lines: 25
Message-ID: <27aein$jlr@csugrad.cs.vt.edu>
References: <CD7EyC.4Ax@nas.nasa.gov> <CDErsF.1Cx@cbnewsj.cb.att.com> <CDEzuF.519@veda.is>
NNTP-Posting-Host: csugrad.cs.vt.edu
In article <CDEzuF.519@veda.is> adam@veda.is (Adam David) writes:
>dwex@mtgzfs3.att.com (David E. Wexelblat) writes:
>[about dynamically configured device numbers]
>>Which is a horribly bad way to do things. SVR4 does this, too. I hate it.
>Normally, however I would agree with the original complaint that assigning
>device ids in the order that disks are found is often a silly idea. What I
>would like to see is a file that maps SCSI ids to device ids and back.
When you build a kernel, you can setup in your config file which IDs
should map to which devices. This seems to work OK...
MacBSD (aka NetBSD/mac) will actually switch devices around so that sd0
is ALWAYS the disk that you booted from. This is kind of kludgy at the
moment since it actually allocates all the drives, the swaps sd0 and the
boot drive. BUT it's real nice when sneaker-netting external drives w/
root partitions from here to there... Landing who knows where in the
chain...
-allen
--
Allen Briggs \ Swift has sailed into his rest;/Savage indignation
briggs@csugrad.cs.vt.edu | there/Cannot lacerate his breast./Imitate him
- end / if you dare,/World-besotted traveller; he/
killing - / Served human liberty. -- W.B.Yeats, 1931