HDTenEightyP/NetNews huggingface dataset:
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Kithrup Enterprises, Ltd.
Date: Fri, 24 Jul 1992 19:01:43 GMT

In article <1992Jul24.170640.11127@Warren.MENTORG.COM> tal@Warren.MENTORG.COM (Tom Limoncelli) writes:
>USL has never sold long distance.  You're going after the wrong men in
>black hats.  (Or, in the case of Plan 9, black space suits)

Don't be stupid.

AT&T is currently the single largest shareholder of USL; it has a
controlling interest, I believe.  Therefore, boycotting AT&T long distance
communications, and informing AT&T of this, is a valid, proper, and
effective way of getting the point across to USL -- as AT&T is the only
company that needs to vote to drop the lawsuit.

-- 
Sean Eric Fagan  | "My psychiatrist says I have a messiah
sef@kithrup.COM  |  complex.  But I forgive him."
-----------------+              -- Jim Carrey
Any opinions expressed are my own, and generally unpopular with others.
From: mcuddy@fensende.Rational.COM (Mike Cuddy)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD
Date: 22 Jul 92 09:00:34 GMT

jjsmith@nyx.cs.du.edu (Jonathan J. Smith) writes:


>Hrm well to the uneducated in legalieze (me) this sounds just a tad unlikely,
>First of I believe that AT&T has to PROVE that said things actually were
>based on derived from intellectual property of AT&T.  I also believe that
>burden of proof lies with AT&T.  To me it sounds a shade unlikely that they
>could possibly prove that , I COULD be totaly wrong here however.  Just 
>doubting that is will happen i guess, sounds way to unreasonable.

Heh, you forget that USL/ATT have lots of money for lawyers.  How many 5 to 10
thousand dollar lawsuits can BSDI withstand?  5?  10?  That's a lot of money
for a startup, however, it's piss in a bucket for ATT/USL. *SIGH*   Do not
forget the principles this country is decaying under:  Only the financially 
advantaged win :-(.

Boycott AT&T, don't use the phone. ;-)

--Mike Cuddy (mcuddy@rational.com, fensende!mcuddy@apple.com)
To Anachreon in Heav'n/Where he sat in full glee/A few sons of harmony sent a 
petition/That he them inspi-re and patron would be/When this answer arrived/
from the jolly old Grecian/"Boys fiddle and flute,/no longer be mute,/
I'll lend 'ye my name/And inspire ya' ta' boot/And besides I'll instruct 'ye/
like me, to entwine/ the Myrtle of Venus with Bacchus' vine!
-- sing to the tune of the star spangled banner... (these are the orig words,
yes folks, our national anthem is a ``let's get drunk and F*** song'').
Newsgroups: comp.unix.bsd
From: ejh@slustl.slu.edu (Eric J. Haug)
Subject: com port names on 0.0 and 0.1
Organization: St. Louis Univ.
Date: Wed, 22 Jul 1992 00:51:28 GMT

Please be aware that the com drivers are slightly different in 0.0 and 0.1.
Careful perusal of the code will show strategically placed -1's.
DO NOT JUST DROP THE OLD DRIVER IN THE KERNEL AND RECOMPILE.
change the system config file, reconfigure, and remake the device nodes.
how?  note in 0.0 com0 and com1, and in 0.1 com1 and com2.
MAKEDEV in 0.1 also wants to make com00 and com01 or some such.

Somebody wanted to ease the use of 0.1 and DOS users
to the confusion of others.
Please note that my lpt patches in unoffical on agate follow the same
strange logic.
eric   ejh@slustl.slu.edu
From: fty@bizarre.rtpnc.epa.gov (Frank Terhaar-Yonkers)
Newsgroups: comp.unix.bsd
Subject: Re: adding another swap partition
Date: 24 Jul 92 12:55:21 GMT
Organization: United States Environmental Protection Agency

Anybody get this to boot?  It won't on my 486/33, while all the
other 0.1 kernels I've tried work okay ...

In article <1992Jul23.114610.27579@ms.uky.edu>, risner@ms.uky.edu (James Risner) writes:
kwan@netcom.com (Kwan-Seng Low) writes:

>>Is there any way you can post the multiple swap partition kernel
>>(dist.fs) on the net (ftp on one of the disty. site). I'm dying to get the
>>kernel that do this , to swap on my 2nd disk.
>>Thanks in advance.
>
>>PS: if you decided to do that, can you post the instruction as well.
>
>>Kwan
>
>A recompiled kernel with second drive support and second drive swap support
>is available on f.ms.uky.edu:/pub2/386bsd-0.1/unofficial/second.drive.randy/*
>
>Risner

-- 
-------------------------------------------------
Frank Terhaar-Yonkers	fty@bizarre.rtpnc.epa.gov
Unisys/U.S. EPA		(919)541-2297
From: gpw10@phoenixcd.amdahl.com (Gary Ward)
Newsgroups: comp.unix.bsd
Subject: Re: SCSI tape drive not accessible
Date: 24 Jul 92 02:23:00 GMT
Distribution: comp
Organization: Amdahl Corporation, Sunnyvale CA

I have a very similar setup, 486/33, AHA1542B, 2 SCSI drives and an Archive
Viper SCSI tape drive.  The disks are at 0 & 1, the tape drive was at 4.  No
amount of coaxing convinced the tape drive to work.  I then changed its SCSI
address to 2, as implied in the install file (they mention dumping from tape
via /dev/ras2a) and it worked immediately.  Perhaps the SCSI driver requires
consequative addresses?

By the way, accessing /dev/as1a does attach the second drive for me as well,
but I haven't got it working yet...
-- 
+------------------------+---------------------------+
| Gary Ward              |  Amdahl Corporation       |
| gpw10@cd.amdahl.com    |  1250 East Arques Avenue  |
|                        |  P.O. Box 3470 M/S 142    |
|                        |  Sunnyvale, CA 94088-3470 | 
+------------------------+---------------------------+
From: greggb@nic.cerf.net (Gregg Brekke)
Newsgroups: comp.unix.bsd
Subject: Kernel Compiling
Date: 24 Jul 92 19:47:43 GMT
Organization: CERFnet;  La Jolla, CA

Hi All,

Stupid question, maybe, but I am clueless...

How do I rebuild the kernel with 386bsd?  I know how to use the config
program, but the needed configure files seem to be missing from the
binary distribution.  Where should I 'cd' to and what file do I use
for the FILE_SYSTEM in 'config FILE_SYSTEM'?

Do I need to get the etc01.* distribution for these files?  

Any help you can offer will be greatly appreciated.  If possible, please
reply email as I am desparate for a reply and this machine unbatches
news about every other day.

Gregg Brekke
greggb@acme.fred.org
From: jnpotts@iastate.edu (James N. Potts)
Subject: Using a terminal to access a 386bsd system
Organization: Iowa State University, Ames IA
Date: Sun, 26 Jul 1992 22:15:01 GMT

I've got an extra terminal sitting next to my system, and I was wondering if
it was possible to connect it to my computer via a com port, and log in a
session.  If so, what do I need to do to allow this?

Thanks for any help!

-- 
_____________________________________________________________________
James N. Potts          |  "To err is human.  To get multiple UAE's 
jnpotts@iastate.edu     |   requires MS Windows."
tabp6@isuvax.iastate.edu|                      - Me
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: 386BSD-0.1 Install problem: can't relabel disk, etc...
Date: 29 Jul 92 08:31:12 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung
Keywords: 386bsd

In <1992Jul28.200625.11771@donau.et.tudelft.nl> franky@duteca.et.tudelft.nl (Frank W. ten Wolde) writes:

>I'm having trouble installing 386BSD-0.1 to my system.

[...]

>When I prepare a partition of type A5 on my disk and try to install again
>(install -debug) I get:

>	 bios finds: cyl 1001 heads 15 sectors 17
>	Partitions:
>	offset	size	type	flag
>	17	153748	a5	0
>	153765	101235	81	0
>	0	0	0	0
>	0	0	0	0
>	Do you want to install <...> disk drive's 386BSD partition? (y/n) y
>	making root size 143055 offset 17
>	making swap size 10000 offset 143265
>	label written at sector 17
>	High level formatting of 386 BSD disk storage:
>	...
>	...
>	super-block backups (for fsck -b #) at:
>	32, ...
>	...
>	...
>	...					, 134704, 138816
>	newfs: ioctl (WDINFO): No such process
>	newfs: /dev/rwd0a: can't rewrite disk label

>and the installation fails again.
>Can someone please explain? I also tries the fixit.fs boot floppy and
>used disklabel. Then I get errors about not being able to find/write the
>disk label and I get '/dev/rwd0a: invalid argument' errors.

This should be in the FAQ (but is not yet :-(
Your listing shows that you A5 partition does not start at a cylinder boundary.
It starts at head 1, cylinder 0, sector 1 according to your disk parameters.
This happens as a "feature" when you prepare the partition by FDISK and 
change the ID to A5 then. 
NEWFS does not like to start at a non-cylinder boundary and does not find the
location to store the disk label. I think this is not a bug, but a vital
feature, so don't patch the newfs source to get the remaining 238 sectors
(they won't save your life).

Change the offset to 15*17 = 255 and adjust the size accordingly (subtract
255-17). Install should work then.

>My system is:	386/33 (unknown chipset)
>		4 Mb core
>		no NCP
>		ST1144AT	(drive 1: 125Mb)
>		ST251AT		(drive 2: 43Mb)
>		SC499		(tape controller)

I am not sure about your tape controller, but the rest is not critical.

>	
>Thanks!

>-Frank ten Wolde

>--
>#############################################################################
># Frank W. ten Wolde (PA3FMT)    | E-mail: franky@duteca.et.tudelft.nl
># Delft University of Technology |
># The Netherlands                |

Hope that helps

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 28 Jul 92 10:55:21 GMT
Organization: St. Peter's College, US

In article <1992Jul27.152614.25898@psg.com>, randy@psg.com (Randy Bush) writes:
> Let's get down to basics.  This is going to cost a lot of cash to fight.  So
> where do we send donations?

  Well, I sent BSDI a check last Wednesday. I received my tapes yesterday,
and today I'm running. Seems like a good idea to me 8-)

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
Newsgroups: comp.unix.bsd
From: vixie@pa.dec.com (Paul A Vixie)
Subject: Re: AT&T sues BSDI & Our Retaliation
Organization: DEC Network Software Lab
	<UEKLEINF.92Jul29092927@queen.mcs.Drexel.edu>
Date: 29 Jul 92 09:20:24

[Erik (uekleinf@mcs.drexel.edu)]
>     Now there is an idea.  You want to start getting noticed, pull any PD
> software out there that you originally made, restate the copyright, and put
> it back out on the net.  AT&T should really start getting the idea when they
> have to start paying for everything or risk Copyright Infringment.

No worries there.  AT&T had (til they gave it to USL) a rather bad case of NIH.
I wrote a PD-ish "cron" replacement in 1986 and though I tried very hard to get
AT&T to take it and blow away the ridiculous one they still ship in their
latest SysV releases, they politely declined.

So did every other vendor I offered it to, because they already had the SYSV
one and they didn't want to become incompatible with it.  (A pox on NIH!)
--
Paul Vixie, DEC Network Systems Lab	
Palo Alto, California, USA         	"Don't be a rebel, or a conformist;
<vixie@pa.dec.com> decwrl!vixie		they're the same thing, anyway.  Find
<paul@vix.com>     vixie!paul		your own path, and stay on it."  -me
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Nanyang Technological University - Singapore
Date: Tue, 21 Jul 1992 13:14:33 GMT

In article <1992Jul21.104627.3353@mel.dit.csiro.au> smart@wanda.mel.dit.CSIRO.AU (Robert Smart) writes:

: This is insanity. Surely this will be thrown out of court.
Who is going to defend NET/2?
--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet

Newsgroups: comp.unix.bsd
From: zxmsd01@mailserv.zdv.uni-tuebingen.de (Gunther Schadow)
Subject: Re: IDE drive woes (need for comp.unix.386bsd)
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Tue, 21 Jul 1992 15:37:26 GMT

In <1992Jul19.062932.17244@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:


>I think now that 0.1 is out there will be a strong need for a comp.unix.386bsd
>There will be a lot of questions which may be profane and boring to those
>not interested in 386bsd but interested in bsd in general.

According to Bill and Lynne (see INSTALL.NOTES) they are about to
achieve a group comp.os.386bsd.

>What has to be done to achieve this?
maybe ask Bill otherwise just wait for it to come.

>To start with one of these above mentioned question:

>I think the 0.1 distribution has problems with IDE drives.  
>I tried to format my Maxtor 7120 with various combinations of
>tracks/heads/sectors and always I get either 

I think that Seagate ST3144A is an IDE drive and I have no problem
with it. Check if your drive is (1) correctly installed (2) correctly
partitioned (by DOS' fdisk) (3) correctly (medium-level) formated by
DOS' format (4) that the install program finds a partition with type
0xa5 (= 165) (5) that the disktab entry is correct (ST3144A was
automaticly detected by 386BSD) and (6) that the 386bsd partition is
correctly high level formated by 386BSD's disklabel.

>Input/Output error on /dev/wd0a
DOS'formated? disktab?
> or 
>cd: can't cd to /mnt 
> or
>mount: /dev/wd0a invalid argument

>Can anyone confirm that there is a problem or do I have to change hardware?

No I don't think so. I even don't think that there has any software to
be changed.

>--Christoph P. Kukulies 
schoene Gruesse
-Gunther
--
-------------------------------------------------------------------------------
Gunther Schadow,	          e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE
Sudetenstrasse 25,	          Phone:  (49) 7071/37527
7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject:  we driver woes (wd8013/wd8003) 
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Thu, 30 Jul 92 11:38:30 GMT


I built a new kernel having a we0 at io 300 irq 10 (up tonow I only
have been able to bootstrap from the dist-WE800.fs with mt only
WD8003 card (for that reason a SCO system is down for a weeks where
i need this card urgently).

So I decided to build a new kernel. Worked fine with one exception:
vers.c seemed to be missing in the new kernel directory generated by
'config'. I added vers.o to the $OBJS definitinos in the Makefile in
/sys/compile/MYKERNEL/Makefile and it worked.

Now to the problem: 

The new kernel recognizes that I have a we0 at io 300 irq 10 but it
does not do any correct networking action. All I get is a 'reject 65531'
repeatedly at the console when I try to ping from outside.

Any idea what is broken with the we driver? 

-- Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
Newsgroups: comp.unix.bsd
Subject: Re: Interleving supported on 386BSD?
From: billp@jupiter.cse.utoledo.edu (bill parquet)
Date: 28 Jul 92 17:43:27 EST
Distribution: comp

jtsilla@damon.ccs.northeastern.edu (James Tsillas) writes:
: 
: I am running a 386SX-16 Mhz based system with an RLL drive. Tesing has
: shown that maximum drive performance can only be achieved using a 2:1
: interleve. I noticed there was no mention of interleve anywhere in the
: installation procedure. Does 386BSD lack support for interleving or is
: this handled by the low level format?

Your interleave is set when you intially low-level format your hard drive.
Whatever operationg system you install will use that interleave (dos/386bsd/
whatever)

billp@jupiter.cse.utoledo.edu
From: scott@ryptyde.cts.com (Scott McClure)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 27 Jul 92 14:00:05 GMT
Organization: Ryptyde TimeSharing, San Diego, CA

rt@MAGEC.COM (P.A. Marshall  x8330) writes:


[...]

>In a posting by Mike MacKenzie (mm@mentor.cc.purdue.edu) it was
>suggested that we might change our phone service from AT&T to another
>carrier, IMO a fine idea, but let's make sure AT&T gets the word on
>why users are switching (Ideas anyone?).

I don't think that it would do much, considering the break up of AT&T.
USL is no longer directly connected to it (at least, that's what I've 
heard).  You'd be bashing seperate company.

We need to find a way to bash USL directly for this outrage.


>-- 
>Al Marshall
>rt@magec.com					Standard Disclaimer...
>netwrk!rt

Just my $0.02

Scott

-- 
INTERNET:  scott@ryptyde.cts.com                     | "Nuke the homeless gay
ARPANET:   ryptyde!scott@nosc.mil                    |  baby whales for Jesus!"
UUCP:      {crash, nosc}!ryptyde!scott               |    - bumper sticker
From: friedl@informatik.uni-kl.de (Ralf Friedl)
Newsgroups: comp.unix.bsd
Subject: diffs between 386bsd-0.0 and 386bsd-0.1
Date: 22 Jul 92 20:59:09 GMT
Reply-To: Ralf Friedl <friedl@informatik.uni-kl.de>
Organization: J. Deitch & Associates
Originator: 386bsd-gate@jadpc.cts.com
Precedence: bulk


Has anybody diffs between 386bsd-0.0 and 386bsd-0.1 ?
In the 0.0 distribution there were two diffs, one for the kernel and one for
the executables. I haven't found similar diffs in the new 0.1 distribution.
Such diffs have several advantages:

- It's not necessary to get the whole 15 MB (source distribution).
- They show what is changed in the system.

----
Ralf Friedl
friedl@informatik.uni-kl.de
Newsgroups: comp.unix.bsd
From: tmt@osf.org (Tom Talpey)
Subject: Re: STREAMS and OSF [Was: AT&T vs. BSDI ad nauseam
Keywords: STREAMS OSF licence
Organization: Open Software Foundation
Distribution: na
Date: Thu, 30 Jul 1992 13:27:09 GMT

In article <1992Jul29.220142.3524@tgivan.wimsey.bc.ca>, mak@tgivan.wimsey.bc.ca (Bob Makowski) writes:
|> In article <1992Jul24.185653.3196@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
|> >In addition, OSF specifically licensed parts of the SysVr3.x code from USL
|> >in order to include it in OSF/1.  Specifically, the STREAMS code, as there
|> >were no such things in the original Mach code.
|> >
|>
|> I was aware that OSF had a streams project ongoing, but I've heard nothing
|> to suggest that OSF resolved this via the distribution, and concomitant
|> royalties, of *any* post-SVR2 source baseline.

OSF/1 requires a System V R2.2 license but contains no other System V code.
The STREAMS implementation in OSF/1 comes from Mentat, Inc. and contains
features only now showing up in SysV4, such as parallel operation. OSF1/1.0
is SVID2 compliant (SVR3 spec), while OSF1/1.1 is SVID3 compliant (SVR4).
It was in part the restrictions first placed on the V.3 licenses which led
to chartering OSF to create a more freely licensable alternative.

Tom Talpey
tmt@osf.org
Newsgroups: comp.unix.bsd
From: tal@Warren.MENTORG.COM (Tom Limoncelli)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Mentor Graphics, Silicon Design Division
Date: Fri, 24 Jul 1992 16:52:36 GMT

In <1331@pacsoft.com> mike@pacsoft.com (Mike Stefanik) writes:

>tal@Warren.MENTORG.COM (Tom Limoncelli) writes:
>: USL has been publishing press releases saying that Windows NT is the
>: real enemy, and they don't care who's Unix you buy, just as long as you
>: buy something that looks like Unix... because they'd rather see people
>: switch to Unix than Windows NT.

>Of course.  Since USL has it's fingers in (nearly) all of the pies, they
>really don't care who you buy the end product from ... they *are* getting
>a piece of the action with every sale.

Your statement is complete wrong.

The press releases I was talking about MOSTLY mention OSF!  Buying OSF
results in USL making 0 $$$.

Tom
P.S.  Why is AT&T bashed for this when it's USL that is making the law
suit.
-- 
Tom Limoncelli -- tal@warren.mentorg.com (work) -- tal@plts.uucp (play)
      Maybe Bush will follow Perot's lead.
Newsgroups: comp.unix.bsd
From: jlitvin@speedstr.intel.com (John Litvin)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Intel Corporation, Multibus Unix Engineering, Hillsboro, OR
	<1992Jul22.163407.10823@Warren.MENTORG.COM> <14101@ksr.com>
	<BZS.92Jul25165147@ussr.std.com>
Date: Wed, 29 Jul 1992 00:12:15 GMT

   > From: jfw@ksr.com (John F. Woods)
   > >AT&T probably spends more money on coffee for employees than BSDI will ever
   > >handle.  Assuming they aren't squished like a bug by AT&T's legal staff.

   From: bzs@ussr.std.com (Barry Shein)
   > First, it's USL doing the suing. I'm not sure exactly what difference
   > that makes but I suspect it makes at least some difference. I do
   > think, however, sending any message to AT&T will be helpful.

   > Does anyone have a list of USL shareholders? I believe Novell is a
   > large shareholder in USL. May as well get the targets right, because
   > ultimately all this activity by USL has to please their shareholders,
   > especially the big ones.

Here is the list of the 11 companies that bought shares of USL from
AT&T.  AT&T easily remains the majority owner.  (I dug this list out
of the June 1991 Unix Review that mentioned the USL press release).

	Amdahl Corp.
	Motorola Inc.
	Novell Inc.
	Sun Microsystems Inc.
	ICL plc.
	Ing. C. Olivetti & Co. S.p.A.
	Fujitsu Ltd.
	Institute for Information Industry (Taiwan)
	NEC Corp.
	OKI Electric Industry Co. Ltd.
	Toshiba Corp.

John Litvin
Newsgroups: comp.unix.bsd
From: explorer@iastate.edu (Michael Graff)
Subject: Re: (new, unofficial) patched bootables on agate...
Keywords: 386bsd, 0.1, patched, boot floppy, dist.fs, fixit.fs
Organization: Iowa State University, Ames IA
Date: Thu, 23 Jul 1992 16:07:29 GMT

In <14ljgrINNka3@agate.berkeley.edu> cgd@agate.berkeley.edu (Chris G. Demetriou) writes:

>I've put some new patched boot floppies in
>agate.berkeley.edu:~ftp/pub/386BSD/386bsd-0.1/unofficial/newbootables.cgd

>They have the fix for the wd boot block, the fix for the wd driver,
>and there are various combinations of ones having no
>Isolink driver in the kernel, no "we" driver in the kernel, and
>ones having debugging bootstraps installed...

Ok, I got the new binaries (I've tried dist.fs-noIS.debug, dist.fs-noIS,
and dist.fs) and now my Z-386/25 boots...  And boots...  And boots...

I get some sort of panic right after the floppy found message, and have NO
idea what the rest says, other than a "trap 12" or something like that...
the blasted thing clears the screen too quickly!

This is the same problem I had on my PC at home (386 clone) and only
seemed to appear when I use a partition rather than the entire disk for
386.

It seems that 386BSD might not quite have the partition thing down yet...

Thanks to Chris for providing that kernel!  Now I can compile at home, and
I'm getting closer on the Z-386!

-- 
--
Michael Graff    Iowa State University Computation Center      Project Vincent
215 Durham                voice: (515) 294-4994           explorer@iastate.edu
Ames, IA  50010           fax:   (515) 294-1717           gg.mlg@isumvs.bitnet