HDTenEightyP/NetNews huggingface dataset:
From: randy@chinet.chi.il.us (Randy Suess)
Newsgroups: comp.unix.bsd
Subject: Re: adding another swap partition
Date: 22 Jul 92 14:21:07 GMT
Organization: Chinet - Public Access UNIX

In article <14inptINN564@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
>To add swap space, the device needs to be compiled into the kernel
>in advance, even if you don't plan to use it. It reserves space in
>it's swap space map for this (so eventually it can interleave them).

	Ok, that did it.  Thanks.  I am now able to have the swap
	partition on the second drive added with swapon. (at least
	the command completes with no errors.  Any way to actually
	see if the system knows about the second swap partition?)

	in /sys/compile/YOUR_SYSTEM_NAME/swap386bsd.c,
	duplicate the makedev(0,1) line in the swdevt struct
	and change the 1 to a 9.

	Thanks, Bill.

-- 
	I am created Shiva the Destroyer; Death, the shatterer of worlds!
	Who is this dog meat who stands before me now?
	That's the biz, sweetheart.
Randy Suess					 randy@chinet.chi.il.us
From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.unix.bsd
Subject: Re: install 0.1 problems
Date: 22 Jul 92 15:28:37 GMT
Organization: Naval Medical Research & Development Command

In article <1992Jul21.224908.5459@nrao.edu> cflatter@nrao.edu writes:
>In article 6250@thyme.jpl.nasa.gov, kaleb@thyme.jpl.nasa.gov (Kaleb Keithley) writes:
>>
>>3.  Would anyone "in the know" care to suggest when a fix for the bus
>>    mouse problem might be available.  It's going to be a real drag
>>    to pull the card every time I want to switch. :-)  I'm even offering
>>    to help to solve it, if I can surmount the above obstacles.
>
>Funny... I have a Logitech bus mouse installed and it didn't faze BSD at all.
>You might check the jumpers on the mouse card --- you might be able to find
>a configuration that works both with OS/2 and 386BSD.
>
When I booted Tiny on a machine with a Microsoft Bus Mouse on IRQ 5, it
identified it as wt0 at 0x300 IRQ 5.  Now I do have an Everex tape at that
address on IRQ 2/9.  However, booting up was fine.  I haven't tried to
install and run the full version on this box yet.
>	Chris Flatters
>	cflatter@nrao.edu


-- 
LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.3     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2  R3.2           | MCI-Mail: 377-2719 or 0003772719@mcimail.com
Newsgroups: comp.unix.bsd
From: dulitz@cs.cornell.edu (Dan Dulitz)
Subject: 386BSD success, but now DOS won't boot off floppy
Summary: shutdown -todos won't work either
Organization: Cornell University CS Dept.
Date: Thu, 23 Jul 1992 21:12:08 GMT

Thanks to everyone who made the 0.1 release of 386BSD possible.  It
was worth the wait:  robust and full-featured.  Kudos to all.

Unfortunately, I've got too much of a good thing!  I still need MS-DOG
occasionally, but it won't boot.

/usr/distbin/shutdown -todos doesn't work.  It claims "cannot make
DOS partition active" or something of the sort.  Placing a bootable
copy of DOS 5.0 in drive A: doesn't work either.  The drive light
turns on for a while and then 386BSD boots off the hard disk.

Tiny 386BSD and the fixit disk both boot correctly off the floppy.

And yes, the DOS partitions (115 Mb primary and 45 Mb extended) were
fully functional this morning before I installed 386BSD.  I used the
Tiny BSD "install" program; I told it to create a 330 Mb partition for
BSD on the hard disk.  It did:  df -k gives 330 Mb total space.

If 386BSD's boot loader won't recognize a DOS disk, IMHO it's broken
and I will try to fix it.  But I don't have source yet, so I would
appreciate your help.

setup:
    Tandy 4000 motherboard, 386DX-16, no 387, 8 Mb RAM
    Micropolis 1680 660 Mb SCSI disk
    Wangtek 5525ES SCSI tape
    Adaptec 1542B SCSI host adapter
    ET4000 SVGA card
    no Ethernet
    1.2 Mb and 1.44 Mb floppies

Thanks a lot.  What a system, though!  This gives me more time to
play!
-- 

Dan Dulitz
dulitz@cs.cornell.edu
Newsgroups: comp.unix.bsd
From: wutcd@hrz.tu-chemnitz.de (Joerg Wunsch)
Subject: Re: 386BSD-0.1 ftp almost works... but?
Organization: tu-chemnitz
Date: Thu, 30 Jul 1992 15:41:32 GMT

chris@lslsun4.epfl.ch (Christian Iseli) writes:

>First strange thing is that the card is supposed to be on level 2 IRQ,
>but 386BSD insists on finding it on level 9...
Quiet simple: your card gives IRQ2, but this is (in the AT) redirected
to IRQ9 since IRQ2 is used by PIC1 as a cascade entry for PIC2.

		bye, J"org
--
J"org Wunsch		         joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de
Textil Computer Design GmbH
R"ahnitzgasse 18, D-O-8060 Dresden
                              If anything can go wrong, it will. (Murphy's Law)
Newsgroups: comp.unix.bsd
From: hsu@cs.hut.fi (Heikki Suonsivu)
Subject: Re: 386BSD & AHA1542B & CDC94171-9 Disk problem
Organization: Helsinki University of Technology, Finland
Date: Wed, 22 Jul 1992 23:01:42 GMT


In article <1992Jul21.162155.24728@ulrik.uio.no> toreh@bootes.sds.no (Tore Haraldsen) writes:
   with retun of residual length >>.
...
   1542A adapters can get a rom upgrade...

Well, the difference between A and B versions shouldn't be that large, that
it would force everyone to upgrade the roms?

Replacing the opcode in the driver make the driver see the disk, though it
won't access it.  Probably this also could be sorted out?  What is
"residual length"?  Block size?

I don't have a working debugging environment yet, so I can't do anything
about it myself?

Anyone had any bad block related problems installing on MFM drives?

-
Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND,
hsu@{otax.tky.hut,cs.hut,clinet}.fi  +385-0-8031121
/G=Heikki/S=Suonsivu/O=hut/OU=cs/PRMD=Inet/ADMD=Fumail/C=FI,
mcsun!hutcs!hsu, riippu SN, Email preferable.
From: drg@bubba.ma30.bull.com (Daniel R Guilderson)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 31 Jul 92 22:47:06 GMT
	<Bs9nLo.I2n@cs.psu.edu>
Organization: Bull World Wide Information Systems, Billerica MA USA

In article <Bs9nLo.I2n@cs.psu.edu> ehrlich@cs.psu.edu (Dan Ehrlich) writes:

   If USL/AT&T can convince a court that NET-2 is a "derived work" the
   implications are unfathomable.  Would this mean that any code in NET-2 would
   now require USL/AT&T licenses?  Would Van Jacobsen's TCP/IP code then
   require a license?

Obviously not.  Otherwise, Microsoft would be able to claim that every
application written for DOS is a derived work of DOS.  TCP/IP is an
application/system which happens to run on UNIX among other platforms.
Is TCP/IP a derived work of DOS?  It was written for DOS (PC/TCP among
others).  The answer is no; it is not derived from DOS nor UNIX.  It
might be derived from something else but there was no functionality in
either DOS or UNIX which approaches that of TCP/IP so what could it
possibly have been derived from?  The cat/type program maybe?

   Richard Stallman is right when he says that software copyrights are evil.

This is totally bogus.  Stallman copyrights every single piece of code
he writes.  He puts all his code under the GNU license.  He has never
claimed that software copyrights are evil.  User interface copyright
is a completely different ball game.
From: rmiller@yoda.eecs.wsu.edu (Robert Miller - EECS)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Keywords: BSDI AT&T
Date: 21 Jul 92 20:19:04 GMT
Article-I.D.: serval.1992Jul21.201904.3472
Organization: Washington State University!

In article <54661@mentor.cc.purdue.edu> mm@mentor.cc.purdue.edu (Mike MacKenzie) writes:
>
>
>AT&T can do this, and I can stop using them as my long distance carrier.
>Also, when I need a new cordless phone, Panasonic & Sony make fine
>cordless phones.
>The 386bsd INSTALL.NOTES claims about 100,000 sites.  If every site were
>to switch to MCI or Sprint, would AT&T notice?
>
>
>Michael MacKenzie	(Purdue University Unix Group)
>mm@mentor.cc.purdue.edu

  my thoughts EXACTLY !


rob miller

rmiller@eecs.wsu.edu
Newsgroups: comp.unix.bsd
From: rivers@ponds.uucp (Thomas David Rivers)
Subject: kill -9 0 ?
Keywords: 386bsd 
Date: Tue, 21 Jul 1992 02:55:12 GMT



I've often used kill -9 0 to log off.  The special pid of 0 usually
means "everything associated with this terminal."

Did that function go away with BSD?  It doesn't seem to work that way
in 386bsd 0.1...

    - Just Curious -
   - Dave Rivers -
  - (rivers@ponds.uucp) -
Newsgroups: comp.unix.bsd
From: neal@neal.ctd.comsat.com (Neal Becker)
Subject: Help! Bad Spot on Disc??
Organization: COMSAT Labs
Date: Wed, 22 Jul 1992 14:27:22 GMT

I have 386-40 generic board, WD1007SE2 controller, and a 150MB
Micropolis ESDI drive. (1022 cyl, 8 h, 35 s/t).

No jumper were changed on the controller board from their defaults.
The drive was low-level formatted without using the sector sparing
option.  Surface verification was done.  All this using the BIOS on
the controller.  No problems.

Try #1) After loadfd bin01, extract reports "bin01.11 corrupt".  I
renamed bin01.11 to junk, and loaded another copy of bin01.11.  Now
extract succeeds.

When fsck -p was run, it reported "unknown inode type...".  When fsck
run I cleared several of these, but each time fsck is run again the
same errors are reported!

Looks like a bad spot, right?  But why?  Doesn't the software
recognize the sectors already marked bad on the disk?

Try #2) Rerun surface verification.  Repartion.  Reload software.
Now, same thing but bin01.12 is bad.  That's cause last time I gave
dos 40 Mb, and this time 20Mb.  Trying cp bin01.12 junk gives io
error, confirming a problem accessing the disk.  Again, mv bin01.12
junk and reload bin01.12.

This time boots OK.  Running fsck shows no problems.  But now a new
problem.  This message keeps showing up (a lot):
  swap_pager_finish: clean of page xxx failed

Sounds nasty.  Is this a different problem?  Or related to disk
access?  HELP!  Does anyone know what's wrong?  This seems to be a
very generic setup.
From: williams@herky.cs.uiowa.edu (Kent Williams)
Newsgroups: comp.unix.bsd
Subject: Which SCSI Controllers
Date: 22 Jul 92 13:24:22 GMT

If I wanted to buy a SCSI controller to use with 386BSD, which ones work???
--
Kent Williams         | "Do you see your cerebellum as a lightbulb or a cog? I
williams@cs.uiowa.edu | saw mine as gristle so I fed it to the dog. But it 
Quote: Bevis Frond    | taste so bad, that she left it in the bowl ..."
From: wheeler@heckle.mitre.org (Brien L. Wheeler)
Newsgroups: comp.unix.bsd
Subject: 386BSD Bug in wd.c
Keywords: wd.c malloc bzero
Date: 30 Jul 92 02:45:53 GMT
Organization: The MITRE Corporation, Bedford, MA

I sent this bug report off to Lynne Jolitz tonight.  Some non-initialized
memory in wd.c prevents my machine from warm-rebooting.  Trivial context
diff attached.

The system really looks great -- thanks Bill and Lynne!
-----

BUG FINDER INFORMATION

NAME:    Brien L. Wheeler
TITLE:   Technical Staff
FIRM:    The MITRE Corporation
ADDRESS: Mail Stop K331
         202 Burlington Road
         Bedford, MA  01730
COUNTRY: USA
PHONE:   617-271-2567
FAX:     617-271-2352
EMAIL:   blw@mitre.org


PC INFORMATION

1.   What  is  your  PC	system	configuration?	Please	be
     specific,	as  success  can  vary	with a difference in
     manufacture date or variation.

	 386/486/387:             Zenith Z-386 (386 + 387) (16 MHz?)
	 ISA/EISA/SCSI:           ISA
	 RAM size:                5 MB
	 drive(s) type and size:  Winchester 80 MB (Seagate?)
                                  Winchester 40 MB (Seagate?)
	 tape(s) type and size:   None
	 ethernet type:           WD 8013 Elite
	 graphics type:           VGA
	 serial type:
	 parallel type:
	 other:                   None


Bugs

1.   What bugs have you found in this system? Please  attach
     any  pertinent  printouts	and  system messages. Please
     also attach any bug fixes for others to use.


In usr/src/sys.386bsd/i386/isa/wd.c, the memory malloc'd for a
new struct disk in wdprobe() is not bzero'd before its use.  On
my machine, this prevents a warm reboot -- malloc grabs the same
memory as the previous boot sequence, and sees the disk as
already open (du->dk_state == 3).  This causes wdsize() to return
a -1 to swapconf() (since dk_state is not zero the wdopen() is not
called, leaving val uninitialized, resulting in a return code of -1).
This screws everything up royally.  The fix is easy -- bzero the
memory malloc'd in wdprobe().  Context diff follows.

-----
*** wd.c.orig	Tue Jul 14 20:55:21 1992
--- wd.c	Wed Jul 29 22:33:58 1992
***************
*** 149,154 ****
--- 149,155 ----
  	if ((du = wddrives[unit]) == 0) {
  		du = wddrives[unit] = (struct disk *)
  			malloc (sizeof(struct disk), M_TEMP, M_NOWAIT);
+ 		bzero(du, sizeof(*du));
  		du->dk_unit = unit;
  	}


-- 
     Brien L. Wheeler  |  I don't speak for MITRE, and they
     blw@mitre.org     |  don't speak for me.

"When I think back on all the crap I learned in high school..."
Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Precedent... Whitesmiths
	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]
Organization: Taronga Park BBS
Date: Sun, 26 Jul 1992 18:37:16 GMT

>AT&T's claim though if litigated
>well -- and AT&T has some of the best attorneys in the country -- may form
>a basis for asserting a property right in virtually any compatible version
>of a UNIX type operating system.

I believe there may be a precedent here, in the Whitesmiths C library and
Whitesmith's UNIX lookalike, from back in the early '80s. The original
release of Whitesmith's C and (I believe) Idris used a non-standard variant
of the UNIX standard I/O library to avoid any possible attack from AT&T (for
example, "putfmt()" instead of "printf()". This was changed, from what I
recall, after AT&T indicated that the interface defined in the UNIX
programmer's manual (the look and feel) was public domain.

In addition, of course, there is the precedent of donating the setuid patent
to the public domain.
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
Newsgroups: comp.unix.bsd
From: zhao@unixg.ubc.ca (Jiansheng Zhao)
Subject: 386bsd-0.1 with Hercule Card?
Organization: University of British Columbia, Vancouver, B.C., Canada
Date: Fri, 31 Jul 1992 17:36:23 GMT

I tried to boot Tiny 386bsd-0.1 on my 386Dx/33 with a Hercules Graphic
card, without success. It was mentioned in 0.1 release note that 386bsd
support HGC, am I wrong?
-- 
Jiansheng Zhao
Dept. Chem. Eng, Univ. of B. C., Canada. V6T 1Z4
zhao@unixg.ubc.ca
Newsgroups: comp.unix.bsd
From: jgreely@morganucodon.cis.ohio-state.edu (J Greely)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Originator: jgreely@morganucodon.cis.ohio-state.edu
Organization: Ohio State University Computer and Information Science
	<7009@skye.ed.ac.uk> <1992Jul24.201744.20071@cs.sfu.ca>
Date: Mon, 27 Jul 1992 15:38:01 GMT

In article <1992Jul24.201744.20071@cs.sfu.ca> bremner@cs.sfu.ca
 (David Bremner) writes:
>I was going to suggest that people ftp the legalize  from ftp.uu.net,  
>but to forstall the requests for mailed  copies, I will append the documents
>from the directory vendor/bsdi/usl.

Thanks for posting this.  After wading through, I happened to glance
up and notice my copy of Kernighan & Pike.  The book is called _The
UNIX Programming Environment_, without a (TM) or (R) on the cover or
spine.  Without opening the book, you can't tell that UNIX is a
trademark of anyone.  Anyone who looks through a book store could
quite reasonably assume that UNIX refers to a family of operating
systems rather than a specific AT&T product.  Indeed, several book
stores I frequent file books about SCO, XENIX, BSD, SVR4 and others
under the generic label "Unix".
-- 
J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)
Newsgroups: comp.unix.bsd
From: tls@panix.com (Thor Lancelot Simon)
Subject: Re: AT&T sues BSDI
Date: Sat, 25 Jul 1992 01:04:19 GMT
Organization: PANIX Public Access Unix & Internet, NYC

In article <1992Jul24.171828.11246@Warren.MENTORG.COM> tal@Warren.MENTORG.COM (Tom Limoncelli) writes:
>[ I can't resist one more post ]
>
>In <14ojorINNlm5@disaster.Germany.EU.net> bs@Germany.EU.net (Bernard Steiner) writes:
>
>>Does that mean that anyone having seen a Ford and then goes off designing
>>hir own car will be sued by Ford for the reason of having been exposed
>>to Ford cars ?
>
>There is a difference between reading the source, and using the
>program.
>
>HAS ANYONE COMPARED THE CODE THEMSELVES?  Could someone with a source
>license FTP the damn NET2 release, pass them through "indent" and then
>compare them?

I've got a source license, as well as a few disk packs with running 32V systems
on them.  I haven't the time to compare *everything* -- and I don't think it's
practical, in any case.  The kernel's just changed too much.  Compare _what_
to _what_?  I could have a look about for the same code for the same purpose,
but not throughout the whole kernel.  It's not so simple as just doing a set of
diffs.

Of course, the fact that I've seen the 32V source code seems to mean that I'm
eternally unemployable in the field of operating systems work, if AT&T wins.
It seems to me that state laws limiting the maximum length of noncompete
agreements come into play here.  Actually, since I was a minor the last time I
looked at the 32V source (or 4.3BSD, for that matter...) I suppose in my case
it's all rather academic.  There, now all BSDI need do is hire me and they've
got that clean channel for all the trade secret information... ;-)
-- 
Thor Lancelot Simon	 tls@panix.COM

"Better be careful there.  John might decide to start taking legal action
against people who refuse to buy stuff from him."  --Kevin McBride
From: gdonl@sunrise.ssi1.com (Don Lewis)
Newsgroups: comp.unix.bsd
Subject: Re: Is AT&T listening?...
Date: 28 Jul 92 05:27:00 GMT
Organization: Silicon Systems, Nevada City CA

In article <1834@adagio.UUCP> grog@adagio.UUCP (Greg Lehey) writes:
>The number of lines of code is irrelevant; what's important is the
>copyright notice. Look, for example, at an AT&T version of /etc/fstab.
>Do you have something like:
>
>#	Copyright (c) 1984, 1986, 1987, 1988 AT&T
>#	  All Rights Reserved
>
>#	THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T
>#	No, come to think of it, this is utter bullshit. Apart
>#	from this copyright notice, everything in this file has
>#	been created by the local sysop. It contains no source
>#	code whatsoever.
>#	The copyright notice above does not evidence any
>#	actual or intended publication of such source code.
>
>#ident	"@(#)fstab.sh	2.3 - 88/05/26"
>
># format: mountdev fs [-[rd]] [fstype]
># This file is used by /etc/mount, /etc/mountall, and /etc/rmountall
>
>
>/dev/dsk/0s3	/usr
>/dev/dsk/1s4	/src
>allegro:/usr	/allegro/usr	NFS,rsize=8192,wsize=8192,soft
>allegro:/	/allegro/root	NFS,rsize=8192,wsize=8192,soft
>allegro:/bsdi	/bsdi		NFS,rsize=8192,wsize=8192,soft
>allegro:/var	/var		NFS,rsize=8192,wsize=8192,soft
>allegro:/pub	/pub		NFS,rsize=8192,wsize=8192,soft
># grave:/		/grave  NFS,rsize=8192,wsize=8192,soft
># /dev/dsk/0p1 	/c	DOS	


Maybe you should sue AT&T for claiming copyright to your intellectual
property.
-- 
Don "Truck" Lewis              Phone: +1 916 478-8284   Silicon Systems
Internet: gdonl@ssi1.com       FAX:   +1 916 478-8290   138 New Mohawk Road
UUCP: {uunet,tektronix!gvgpsa.gvg.tek.com}!ssigv!gdonl  Nevada City, CA  95959
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Need a disklabel dump
Date: 22 Jul 92 13:36:43 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

Could someone please send me an *exact* copy of
'disklabel -r wd0' (or if available 'disklabel -r wd1') of
a disk which has an A5 partition anywhere in the middle of the disk,
i.e. not starting with cylinder 0 or 1 and not ending with the largest
cylinder.

I am not interested in disktab entries for any disk type. My request is just
informational, I need it because I am willing to write a more user friendly 
fdisk/install procedure.

Please cancel your reply when the current date is 25th July or later, I
expect, I have enough responses then.

Thanks

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: rjs@crs.cl.msu.edu (Robert J. Stanton)
Newsgroups: comp.unix.bsd
Subject: Does 386BSD (BSD386?) require a math coprocessor ?
Date: 27 Jul 92 19:46:26 GMT
Distribution: comp.unix.bsd
Organization: Michigan State University

I have been waitinng to install 0.1  until I have a math
coprocessor, but I recently read in one of the posts that
someone was able to _boot_ without one.

What about running 0.1 in general without a math coprocessor?
Will it work?

Also, _must_ I install the tcp/ip, nfs stuff, or can I also
get away witout having a network card ?

Finally, is 0.1 the latest release ?

And, finally, finally, if I can get away with installing
just the RTS and the development system, how much disk
space will I need?

Thanx.

rjs@crs.cl.msu.edu
From: rivers@ponds.uucp (Thomas David Rivers)
Newsgroups: comp.unix.bsd
Subject: Re: compiling kernel hangs machine
Date: 27 Jul 92 11:45:44 GMT


> Could it be that the swap default space (5MB) is too small for compiling
> a kernel with a 4 MB machine. I tried a first kernel build this
> afternoon on a 386SX 4MB and when I came back after several hours the machine seemed to be dead - login from outside was not possible (telnet hung also).
> 
> This happened during the compilation of tty.c .
> 
> Is it possible to increase the swap space simply by swapping to a file (swapon)?
> 
> --Chris
> -----------------------------------------------------------------
> kuku@acds.physik.rwth-aachen.de
> *** Error code 1
>  
> Stop.

  Again, to add data to this problem, my swap partition is 18MB; this
 appears to offer no remedy to the problem.

  However, Andrew Torda (torda@igc.ethz.ch) reports that he got
 around this problem by slowing his 33Mhz machine down to 8Mhz.

      - Dave Rivers -
      (rivers@ponds.uucp)
From: alanh@logitek.co.uk (Alan Hourihane)
Newsgroups: comp.unix.bsd
Subject: 386BSD v0.1
Date: 27 Jul 92 10:00:22 GMT
Distribution: comp
Organization: Logitek Plc.

Has anyone out there in the U.K. got 386BSD v0.1, and are willing to supply
a copy on tape.

I will reimburse for any costs incurred ......


Cheers

Alan Hourihane
email: alanh@logitek.co.uk