Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!ogicse!orstcs!sapphire!pvo
From: pvo@sapphire.OCE.ORST.EDU (Paul O'Neill)
Newsgroups: comp.sys.next
Subject: Re: NeXT's,Disks and Magic
Message-ID: <1991May01.034440.3213@lynx.CS.ORST.EDU>
Date: 1 May 91 03:44:40 GMT
References: > <1991Apr10.031342.27656@dgbt.doc.ca> <7952@jhunix.HCF.JHU.EDU> <1991Apr19.174923.4113@nntp-server.caltech.edu>
Sender: @lynx.CS.ORST.EDU
Reply-To: pvo@sapphire.OCE.ORST.EDU (Paul O'Neill)
Distribution: comp
Organization: Coastal Imaging Lab, Oregon State University, Corvallis, OR
Lines: 22
Nntp-Posting-Host: sapphire.oce.orst.edu

In article <1991Apr19.174923.4113@nntp-server.caltech.edu> anne@nntp-server.caltech.edu (Anneliese Lilje) writes:
>
>We have an Andataco 1.2 GByte SCSI drive (Wren VII). When it 
>boots it displays something like:
>
>Name of Disk and Model Number, as sd0 at sc0 target 1 lun 0
>
>There is NO disktab entry for this drive on my system (yet).
>So what magical thing does the NeXT do to grab this information?

Who knows?  But it's pretty cute and it's the reason I've abandoned my
project to collect and make available disktab entries for 3rd party drives.

Basically, you can slave for hours optimizing a disktab entry and this
automatic stuff that 2.0 does comes up within a couple of Megs of your
optimized stuff.  Not worth it.


Paul O'Neill--Coastal Imaging Lab	pvo@oce.orst.edu	DoD 000006 
OREGON STATE UNIVERSITY
OCEANOGRAPHY ADMIN BLDG 104
CORVALLIS OR 97331-5503			503-737-3251