HDTenEightyP/NetNews huggingface dataset:
From: dawes@physics.su.OZ.AU (David Dawes)
Subject: Re: Motif on X386???
Organization: School of Physics, University of Sydney, Australia
Date: Wed, 19 Aug 1992 15:31:31 GMT

In article <1992Aug19.062455.12847@BitBlocks.com> bvs@BitBlocks.com (Bakul Shah) writes:
>hasty@netcom.com (Amancio Hasty Jr) writes:
>
>>In article <1992Aug18.174802.9845@BitBlocks.com> bvs@BitBlocks.com (Bakul Shah) writes:
>>>Make sure you are using the latest com.c driver (with select()
>>>bug fixed).  But even then there is some problem with the mouse
>>>code in X386 as the very first button press is not seen until
>>>after you either release the button or move the mouse a bit.
>>>
>>>If you wish to track this problem down, check out file
>>>$X11R5/mit/server/ddx/x386/x386Io.c.  Routine x386MseEvents()
>>>seems to be the culprit.
>>>
>>Rich (rich@rice.edu) already fix this problem in the next upcoming release 
>>of X386 1.2E 1.0.2 for 386bsd 0.1, please ask him for the fix. The problem
>>in a nutshell is that X386Io.c is not setting the cflag. the fix was also
>>previously posted by me.
>
>I have already applied that patch but I still see the same symptom.
>May be this only happens with a Microsoft compatible mouse.

If you have 3ButtonEmulation turned on then this is the reason.  With
this enabled the button push event is not acknowledged until another
mouse event is received.  This happens with X386 on all platforms.

If someone can some up with a better 3button emulation method for 2 button
mice, then let us know.

David
--
------------------------------------------------------------------------------
 David Dawes (dawes@physics.su.oz.au)    DoD#210      | Phone: +61 2 692 2639
 School of Physics, University of Sydney, Australia   | Fax:   +61 2 660 2903
------------------------------------------------------------------------------
From: duplain@rtf.bt.co.uk (Andy Duplain)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD won't boot off Compaq 386sx/16
Date: 20 Aug 92 08:17:44 GMT
Organization: BT Customer Systems, Brighton, UK

In article <1992Aug19.144226.7836@super.org> rminnich@super.org (Ronald G Minnich) writes:
>
>yup, 0.0 dist.fs boots fine, but you can not build a boot
>track for floppy from 0.0, nor can you boot 0.1 dist.fs at all. 
>You are not alone. something weird about compaqs, i have heard about
>this from 486, 386, everybody with one of those !@#$#@$! compaqs. 
>There is one guy i have heard from, who has many compaqs, and precisely
>one of these machines will boot 0.1! it is in no known way different.
  
	This may be the same for Zenith PCs also... 0.1 boots from some
	older Zenith machines (386DX and 386SX 16MHz), but not the newer
	386SX 20MHz... bummer.  Has anyone managed to get 0.1 booting on
	the newer Zeniths ???

-- 
Andy Duplain, BT Customer Systems, Brighton, UK.            duplain@rtf.bt.co.uk
#define	DISCLAIMER      My views and opinions are my own, and not my company's
Newsgroups: comp.unix.bsd
From: news@hp832.informatik.hu-berlin.de (H.Boehme U.Kunitz)
Subject: 386BSD 0.1: trouble with western digital card 8013 EBT
Keywords: 386BSD
Organization: Humboldt University Berlin, Department of Computer Science
Date: Tue, 18 Aug 1992 11:06:30 GMT

Hi,

We installed 386BSD 0.1 on a 386 AT. Everything works fine, but ...
We tried to use the networking features. It seems that there is
a software problem. The programm isn't able to read networking packets
correctly. Following messages are printed:
reject: 65xxx. (xxx stands for different numbers.)

We found that in the memory on every second byte is a 0xff.
We checked the WD-Card under MS-DOS and we couldn't find an error.

Maybe somebody knows, where we can find the bug.

Thanks, Harald.
From: jim@blade (Jim Rump)
Newsgroups: comp.unix.bsd
Subject: Difference between same HD's?
Summary: HD, boot
Keywords: HD
Date: 17 Aug 92 16:38:10 GMT
Organization: MCGV Stack, Eindhoven University of Technology, the Netherlands.
X-Newsreader: Tin 1.1 PL4

Hi,

I experienced some strange things lately. 
What I have tried is this:

- I tried to install 386bsd on a IDE (KALOK)  drive running DOS.
  Therefore I used the install script.
  All went well until I did a reboot.
  The result was an endless loop of booting.
  What really happend was that 386bsd did boot but, after the opening banner
  a reboot began.

- A week later I bought an other IDE (SEAGATE).
  Of course I tried to run the install script.
  The result: BSD did work with DOS on the same HD.

My question is: Why do two IDE's differ in the way discribed above?

Any response is welcome.

Jim.

--
   \_  \_  \_\_  \_ \_   Jim@stack.urc.tue.nl
    \_  \_  \_  \_   \_ 
     \_  \_  \_       \_     
  \_\_    \_  \_       \_    I,m always seeing an opinion.
From: rmk@rmkhome.UUCP (Rick Kelly)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on free UNIX / 386BSD (Re: selling 386BSD)
Date: 17 Aug 92 22:21:27 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats

In article <PHR.92Aug17112028@soda.berkeley.edu> phr@soda.berkeley.edu (Paul Rubin) writes:
>    >... Next, Sun (In Solaris 2), and I believe MIPS ship GCC with
>    >their products, in some cases as the primary compilers.  This
>    >sort of distribution is not practical for an operating system.
>
>    And from reading comp.unix.solaris, I get the idea that a number
>    of development shops will buy compilers for Solaris 2.0 because of
>    the GNU Copyleft.
>
>The copyleft does not prevent development shops from using GCC.
>If they think it does, they haven't been paying attention, or they are
>letting their decisions be controlled by paranoid knee-jerk reactions
>instead of by intelligence.  I'm sure this makes Sun happy; there's
>one born every minute, as the saying goes.  I don't see this as a
>reason to let Sun and others make proprietary GCC's.  I can't see
>any benefit of a non-copyleft GCC that could outweigh sacrificing
>the hundreds of improvements, ports, etc. that people have been
>allowed to contribute because the marketroids they work for weren't 
>permitted to grab the improvements for themselves.

But some lawyers believe that the use of GCC to develop proprietary
applications that are shipped "binary only" may be hazardous to a
companies legal health.  The GPL has not been tested deeply in court.

I'm not a lawyer, and normally I don't worry about these things.

>We saw the same situation with Unix, but it didn't work out so well.
>Dozens of companies made proprietary improvements and fixes, so you
>had your choice of N incompatible Unixes, each with a different subset
>of the original bugs fixed.  One of the hopes of the GNU OS and its
>copyleft is to prevent this from happening again.

There is now going to be the choice of N incompatible freely-copyable
unixes, each with their own definition of UNIX.

It soon may be too late for a GNU OS, except for those who are interested
in using Mach in a distributed computing environment.

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: 2nd drive file ... (Actually wd ESDI problems)
Date: 13 Aug 1992 11:05:49 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <193@asgard.mlb.dmt.csiro.au>, mjj@mlb.dmt.csiro.au (Murray Jensen) writes:
> tih@barsoom.nhh.no (Tom Ivar Helbekkmo):
> > bs@Germany.EU.net (Bernard Steiner) writes:
> >>I noticed that with my ESDI drives I had to give disklabel one cylinder less
> >>than what the physical drive parameters are...
> > I thought of this too, but I've tried reducing the number of available
> > cylinders to about a fourth of the real number with no improvement...

The *instructions* for my second drive claim it's got 969 cyls of which 967
are "user accessible" - hmm. I allocated 968...

> Now on to my problem: someone posted about using dd on the block device to
> find out where the bad sectors are.
[...]
> (Trick - use the
> following: "dd if=/dev/wd0c of=/dev/null bs=512 conv=sync,noerror" and you
> will get all the bad blocks in one hit
[...]
> However, fsck would still fail - quite badly too - obviously because there
> were still bad sectors on the disk. But I had not got any errors from dd on
> the block device, so I tried fsck on the block device and it ran through
> perfectly!

Well, I don't have DOS. However, I noticed that dd'ing off 386bsd pertitions
will not find all bad blocks, whereas dd'ing off the 'd' 'partition' does.

BTW did your kernel actually print out the bad sectors or are you using a
modified kernel ? If it's the standard thing it does, would you mind
telling us about any magic flags you gave disklabel.

Thanks

Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: wd1 bad144 woes & workaround (& another idea)
Date: 13 Aug 1992 11:10:14 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <1992Aug13.001403.10404@bitcave.in-berlin.de>, jdb@bitcave.in-berlin.de (Joern D. Busch) writes:
> bs@Germany.EU.net (Bernard Steiner) writes:
> >swapon: wd1b: device not configured and mount complained in a very similar
> >fashion.
> 
> I'm not really sure about the necessity of this, but does your config
> file include something like:
> config	"386bsd"	root on wd0 swap on wd0 and wd1

Yes.
I was talking about re-booting the next morning.
BTW to those who don't know yet - just adding that line to your configuration
certainly does NOT do the trick - install Tom's patches to fd.c, wd.c,
ioconf.c and the config program first...

-Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd
From: juengst@boss1.physik.uni-bonn.de (Henry G. Juengst)
Subject: Re: Help on floppy drive access in 386bsd
Organization: Universit"at Bonn, Informatikinstitut, R"omerstr 154, W-5300 Bonn 1
Date: Fri, 21 Aug 1992 14:06:08 GMT

In article <1992Aug20.161801.29526@news.columbia.edu>, cl45@cunixf.cc.columbia.edu (Ching-Tse Liu) writes:
> Hi,
>    I have installed 386bsd on my hard drive. When I tried to do
>    mount /dev/fd0a /mnt, an error message would come out --
> 
>    "fd0: hard error (ST0 44 ST1 2 ST2 0 ST3 1C cyl 1 hd 7 sec 2) ."
> 
>    However, I could still do 'ls /mnt ' etc, but the error messages
>    kept coming up. I didn't have any problem during the installation.
>    When it boots, the following (reguarding to floppy) appears on the
>    screen --
> 
>    "fd0 drives 0: 1.44M, 1: 1.2 M at 0x3f0 irq 6 drq 2 on isa ."
> 
>    Another question is: How do I read MS-DOS partitions and MS-DOS
>    floppy disks. I don't know how to use those mtools.
> 
>    Thanks for any help.
> 
>        		                     	***********************
> --cliu@merlin.appmath.columbia.edu	*   CLifton T. Liu    *
> --cl45@cunixf.cc.columbia.edu		***********************
> 

I get these errors when I mount a write protected disk without -r option.
It's ok with -r option. I don't that.

Henry

-- 
juengst@boss1.physik.uni-bonn.de [131.220.221.30]
juengst@saph2.physik.uni-bonn.de [131.220.221.12]
juengst@pib1.physik.uni-bonn.de  [131.220.221.2] (strange particle)

I'm only speaking for myself, but not for anybody else !
Newsgroups: comp.unix.bsd
From: nerd@percival.rain.com (Michael Galassi)
Subject: Re: PATCH for Routing Problem on two wd8003e with 386BSD
Organization: Percy's mach, Portland, OR
Date: Thu, 13 Aug 1992 17:25:34 GMT

nerd@percival.rain.com (Michael Galassi) writes:

Folks, I screwed up!  I did not realize that "i386/isa/iomacr.h" is
not a part of the standard distribution.  The lines in the patch I
posted that references it should not have been there.

*** These two lines should be deleted with prejudice ***

83d82
< #include "i386/isa/iomacr.h"


As long as I'm pouring ashes over myself, I apologize for the
normal diff, it was an excercise in false economy that won't
repeat in the future.

-michael
-- 
Michael Galassi -- nerd@percival.rain.com
From: jim@blade (Jim Rump)
Newsgroups: comp.unix.bsd
Subject: announcing ftp-site in Europe!
Summary: ftp
Keywords: ftp
Date: 19 Aug 92 11:10:39 GMT
Organization: MCGV Stack, Eindhoven University of Technology, the Netherlands.
X-Newsreader: Tin 1.1 PL4

Announcing a new bsd ftp-side in Europe:

Adress: ftp.stack.urc.tue.nl (131.155.2.71) 
in:     pub/386bsd.

Good luck,

Jim.

--
   \_  \_  \_\_  \_ \_   Jim@stack.urc.tue.nl
    \_  \_  \_  \_   \_ 
     \_  \_  \_       \_     
  \_\_    \_  \_       \_    I,m always seeing an opinion.
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (R
Organization: Weber State University  (Ogden, UT)
Date: Tue, 18 Aug 92 01:59:03 GMT

In article <1992Aug17.191129.19698@nrao.edu> cflatter@nrao.edu writes:
>In article 7751@gateway.novell.com, terry@ithaca.Eng.Sandy.Novell.COM (Terry Lambert) writes:
>>In article <5146@airs.com> ian@airs.com (Ian Lance Taylor) writes:
>>>I know this issue gets chased around and around a lot, but, after all,
>>>just because the Hurd is covered by the GPL does not mean it can not
>>>be sold shrinkwrapped in a store.  The GPL just means that the
>>>distributor has to put a piece of paper in the shrinkwrap saying
>>>``send $100 for complete source code'' as well as another saying ``you
>>>may give this software to your friends.''
>>
>>I'm a bit confused by this statement -- $100 for GNU Hurd's source code,
>>or $100 for ABXZ Computing's modified GNU source code?  Does this require
>>that ABXZ Computing run a GNU tape copying site for their users, or can they
>>give GNU's address on the card?  Do they *have* to have a card if the software
>>is modified?  Do they *have* allow access to their modifications source?  Do
>>they have to allow you to give away their software to their friends, or only
>>the GNU stuff?
>
>The GPL is very clear on these issues.  If ABXZ modifies any GNU
>software then the modified software is a derivative work and falls
>under the GPL.  This includes the modifications made by ABXZ.  ABXZ
>must make the source (including their modifications) available to third
>parties and charge no more than the cost of copying and distribution unless
>they include the source with the distributed binaries.  ABXZ must include
>a written offer (valid for at least 3 years) to make the source available
>with the binaries; referring buyers to the FSF is not sufficient.

Does this mean that I can't sell my own program (we'll call it '/usr/bin/true')
for $500.00, and then give away GNU Hurd in order to run it, but don't tell
anyone what the program is (except you all know now ;-)), offer to send source,
like in GPL, but say they can't copy it because they can't distinguish my
part from GNU's part?

Because Hurd is an OS, does this mean that *any* application that runs on it
is a derivitive work and falls under GNU Public License?

					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: Re: Choice of SCSI tape drive for 386bsd
Keywords: SCSI, tape, 386bsd
Date: 20 Aug 92 07:17:40 GMT
Organization: HCS GmbH, Hamburg, Europe

In <1992Aug19.112710.25394@olymp.informatik.uni-bonn.de> volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt ) writes:

>In article <1992Aug19.083635.214@cc.uow.edu.au> pejn@cc.uow.edu.au (Paul Nulsen) writes:
>>What type of SCSI tape drive would you recommend for use in a 386bsd system?

>I have a Wangtek 5150ES which works OK.  It's a little loud since I have it
>sitting on a desk in its own little box.  When I bought it, it was the least
>expensive, compared to Archive and Tandberg.  Cipher wouldn't work.

i have a cipher 150S-I working on it. the only modifications i made was to
disable the soft error report - otherwise it is working flawlessly.
it even works with dist.fs/fixit.fs, because this was how i installed 0.1.

hellmuth
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
From: STDN%MARIST@VM.MARIST.EDU (Dan Newcombe)
Newsgroups: comp.unix.bsd
Subject: What is needed to compile with MATH libs?
Date: 16 Aug 1992 19:10:32 -0500
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

I have a C program that is a demonstration of back propigation. It
compiles fine but bombs out on the link phase.

cc -o qp -lm quickprop1.c
quickprop1.o: Undefined symbol _exp referenced from text segment

quickprop1.o: Undefined symbol _exp referenced from text segment

quickprop1.o: Undefined symbol _log referenced from text segment


What's missing from this picture?  Thanks:)

  -Dan
STDN@vm.marist.edu
From: tj2n+@andrew.cmu.edu (Tao Jiang)
Newsgroups: comp.unix.bsd
Subject: Open xterm
Date: 14 Aug 92 19:56:00 GMT
Article-I.D.: andrew.IeX81Ee00WB8R3NEp6
Organization: Doctoral student, Statistics, Carnegie Mellon, Pittsburgh, PA

Hi, can somebody tell me how I can open more than two xterms?

I tried to open the third xterm today, but it complained as:
xterm: no available ptys

Thanx in advance!
Newsgroups: comp.unix.bsd
From: Minh Lang <minh@inst-sun1.jpl.nasa.gov>
Subject: Is there anyone running 386bsd on SCSI other than 1542??
Organization: Jet propulsion Laboratory
X-Useragent: Nuntius v1.1b2
Date: Fri, 21 Aug 1992 17:17:47 GMT

I would appreciate any info. I have 2 controllers in my 386. One is a
MFM with a 72Mb Miniscribe and the second controller is a SCSI
Future Domain 845 with a Quantum 210Mb. The boot drive is the MFM
(MFM has to be the boot drive if we have both MFM and SCSI controller).
I have no problem booting 386bsd from the MFM drive, however it didn't
recognize that I have a second SCSI drive at all. As I would like to
install 
all 386bsd source on the second drive, I would really appreciate any info
or comments.
If I take out the MFM controller and drive, will I be able to install
everything
on the SCSI drive? Giving that the controller is not an Adaptec 1542?
Thank you very much.

  == Minh  ==
Newsgroups: comp.unix.bsd
From: ssmku01@convex.zdv.uni-tuebingen.de (P. Kurz)
Subject: WD8003E plus IDE -> hang
Summary: HELP! Get hangs whenreading from IDE-Disc and writing to NFS-Mounted pa
Keywords: WD8003E WD
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Sun, 23 Aug 1992 14:10:18 GMT

Hello out there!

386BSD is great, but ... 

I do have the following problem:

The UNIX-PC is connected via an WD8003E-Card to an HP 9000/345 Workstation.
The Disc of the workstation is mounted via NFS. Doing an
   cp local_largefile foreign_largefile
where local is on the PC-disc and foreign is on the disc of the workstation
the system will hang after some time. Usually this happens after
100-1000KB of data beeing transfered. Well, let me say that the PC does
not hang entirely, but the drive-light stayes on, and the following
disc access will hang the machine.
There must be something going wrong with the interrupt handling. This would
explain why only reading fail, but writing to the local disc works. Perhaps
we miss an interrupt, and the initated read is not served. But until now
I was not able to track the problem down to where th things REALLY happen.

Anyone out there with the same Problem, any suggestions?


Tanks a lot

The Configuration is th following:
486-PC, 33Mhz, 16MB-RAM, ST1239A-Disc, WD8003EP-Elite Card
No slip and mfs configured,

HP9000/345, 12MB, HP-UX 8.0, 425MB Disc



Michael Class: ssmku01@convex.zdv.uni-tuebingen.de
From: toreh@bootes.sds.no (Tore Haraldsen)
Newsgroups: comp.unix.bsd
Subject: NIS & Jolix (386bsd)
Date: 19 Aug 92 14:45:32 GMT
Organization: Statens Datasentral A/S, SDS, Norway

... maybe a naive question in the light of NIS (Yp) being proprietary of
Sun (or isn't it?)...

and don't write lots of "What do you want that stuff for, when you got Bind?"

Is there a version of NIS(YP) available for 386bsd, either in source or
binary form?

-- tore
From: deal@hightop.nrl.navy.mil (Richard Deal)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Date: 17 Aug 92 23:12:02 GMT
Organization: Naval Research Labs (Washington DC)

In article <1992Aug17.073954.15969@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
 >In article <5146@airs.com> ian@airs.com (Ian Lance Taylor) writes:
 >>Apple seems to do fairly
 >>well with a freely redistributable operating system.
 >
 >APPLE DOES NOT HAVE A FREELY REDISTRIBUTABLE OPERATING SYSTEM!
 >
 >Any macintosh is licensed for the Apple OS, but that is *it*.  Any and all
 >clones that might, or might not, exist are not allowed to run the code.
 >
 >That is an important point.
 >

An important point but a little inacurate.  You can run any OS you whant to on 
the Mac's, you can run mac OS system 7 on any machine that it will run on
also.  You do need the roms or ram copy of them to do it.  There are several
clones of the mac that use old roms as well as several emulators (one for 
the SPARC), these all run mac OS.  You can ftp the mac OS on the net from 
Apple sites or pay for a srink wrap version with docs.  


-- 
#include <std/*>
The Butcher                  
Butch Deal                   deal@hightop.nrl.navy.mil
--------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: ghelmer@dsuvax.dsu.edu (Guy Helmer)
Subject: ESDI disk performance under 386BSD
Organization: Dakota State University
Date: Fri, 14 Aug 1992 17:01:48 GMT

Having been running 386bsd 0.1 on a 25Mhz 386 w/ WD1007V-SE2
controller connected to a Wren VI (330Mb) disk and 16Mb of memory,
I've noticed that the system seems seriously disk-bound.  Any work on
the disk drive seems to take forever - mkdir takes a few seconds to
execute; extracting a tar file brings the system to a crawl.  Not
knowing much about BSD internals yet, I am wondering if there is a
fairly simple answer to the obvious question of how to improve the
disk's performance.  The only thing that comes to mind is the
possibility that the disk driver is too slow and doesn't keep up with
the disk's interleave, requiring one whole revolution of the disk for
each sector read.

Any thoughts on things I could tune or code I could rewrite :-) ?

-- 
Guy Helmer, Dakota State University Computing Services - ghelmer@dsuvax.dsu.edu
White congressmen can't jump, but they sure can bounce.
Newsgroups: comp.unix.bsd
From: Minh Lang <minh@inst-sun1.jpl.nasa.gov>
Subject: Does 386BSD work with other SCSI controllers??
Organization: Jet propulsion Laboratory
X-Useragent: Nuntius v1.1b2
Date: Tue, 18 Aug 1992 15:14:34 GMT

Does 386bsd work with any other controllers other than the 
supported Adaptec 1542? I have a SCSI drive with a Future
Domain 845 and 386bsd doesn't recognize it. Is there a 
patch so that I can install 386bsd on my scsi drive. It's
a Quantum 210S, BTW. I would appreciate any info/comments.
Thanks.
  == Minh ==