HDTenEightyP/NetNews huggingface dataset:
From: terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert)
Subject: Re: backup w/ compression for UN*X?
Organization: Novell NPD -- Sandy, UT
Date: Thu, 3 Sep 1992 16:57:02 GMT

In article <1992Sep3.015437.15379@msuinfo.cl.msu.edu> paoletti@cps.msu.edu (David R. Paoletti) writes:
>Does anyone know of any software for UN*X, 386BSD or otherwise,
>that does on-the-fly compression?  Thinking of looking into
>writing my own, or getting some 386BSD people together to help,
>as soon as I get my new machine built with enough HD space to
>re-compile 386BSD...  This would be really nice for people with
>floppies, or even people who want to save on tapes.

ctar (LoneStar software, I believe... Hi guys!)

Doesn't gnutar support -z (LZW compression)?

Some flavors of ftpd, if you want net backup.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu

---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
Newsgroups: comp.unix.bsd
From: steve@nuchat.sccsi.com (Steve Nuchia)
Subject: Re: Restrictions on free UNIX / 386BSD (Re: selling 386BSD)
Organization: South Coast Computing Services, Inc.  Houston
Date: Fri, 28 Aug 1992 17:46:39 GMT

In article <9208251653.26@rmkhome.UUCP> rmk@rmkhome.UUCP (Rick Kelly) writes:
>It would be a strange to build SVR4 with gcc.  Commodore probably started

Make of it what you will -- I had occasion earlier today to
run nm on Dell's V.4 kernel.  Came back with a whole boatload
of "gcc2_compiled" symbols.
-- 
Steve Nuchia      South Coast Computing Services, Inc.      (713) 661-3301
From: allard@isi.edu (Dennis Allard)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] What and where is the latest X386 release?
Date: 28 Aug 92 17:14:35 GMT
Reply-To: allard@isi.edu (Dennis Allard)
Distribution: world
Organization: USC Information Sciences Institute

david@mlb.geomechanics.csiro.au (David Le Blanc) writes:
> > ... core-{bin,server,fonts,inc,lib,man}-1.0.3.tar.Z
> > from agate.berkeley.edu
> Hey? Where are these? Are they a new X386 release?
> I can't find them on agate..

They are in pub/incoming/X386.

(protection bits make it impossible to do a dir when cwd is pub/incoming,
but you can still cd from there to X386)

Dennis
allard@isi.edu
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: new boot roms
Date: 2 Sep 92 21:36:31 GMT
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu

Okay, here's a thought.  Why doesn't someone write up some new boot
room code that would make a PC act a lot like a Sun when you turn it
on.  Get rid of all the gunky MS-DOS support.  Put in a nice little
monitor to examine memory and various registers and i/o ports and
allow easy booting from any device and any partition on that device.

This would effectively disable the machines ability to run MS-DOS, but
that wouldn't be a great loss anyway.  It might be possible to dump
the ROM code before replacing the ROM's, and store it on the last
couple, or first couple, tracks of a hard disk.  Then the new boot
code could, upon detecting an MS-DOS boot, load the old ROM code,
twiddle a few bits and bytes and jump to the old code and let it
finish loading MS-DOS and provide the BIOS support that it needs.

This is far, far beyond any skills I have, but it seems like it might
be worthwhile and would solve a lot of the problems and workarounds
that people are having and using now.  Maybe someone should get on
AMI's or Phoenix's back and get them to add some support for other
OS's than MS-DOS in their boot code.

++Brett;
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: lockd on 386BSD
Organization: Weber State University  (Ogden, UT)
Date: Sun, 23 Aug 92 20:51:17 GMT

In article <BtFxC8.3r0@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>
>	Well, still no luck in being able to ">>" (append) properly
>	to a BSD partition NFS mounted to my Dell system.  Tried all
>	sorts of different mount options, tried different shells, etc.
>	Append works ok on a Novell 3.11 mounted NFS partition, and another
>	SYSVR4 (AT&T) system.  Now, I have noticed that 386BSD is not
>	running any sort of lock daemon, i.e. lockd.  Not even any mention
>	of it in any of the man pages having to do with NFS.
>	Is this normal?

1)	lockd is an addon.  It's normal to not have it.  You may want to
	add it on, though.

2)	The append failure is not a result of NFS.  It's a result of a rather
	loose interpretation of the "a" and "a+" modes in POSIX 1003.1.  You
	would be better off fixing the shell, or you're bound to repeat the
	performance later with some other box.


					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
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: eje@irenaeus.mlo.dec.com (Eric James Ewanco)
Subject: Re: Extracting 386bsd bin01 on another machine
Reply-To: ewanco@kalvin.enet.dec.com
Organization: Digital Equipment Corporation
Date: Thu, 27 Aug 1992 19:27:04 GMT


> In <babraham.714900677@unpcs1> babraham@unpcs1.cs.unp.ac.za (Bobby Abraham) writes:

> >Can someone tell me how to extract the bin01 files on another unix
> >machine.  

> >I don't have enough space for the unextracted files in addition
> >to the extracted files.  I would like to ftp only the extracted files.

> >thank you



> >--
> >Bobby Abraham
> >Computer Science
> >University of Natal, Pietermaritzburg
> >email: babraham@unpcs1.cs.unp.ac.za

> If you do not have some "braindead-cpio" system which swaps bytes (Sun3 and
> other 68xxx related systems have this "feature") you might try the following:

> # have the bin01.* files HERE
> mkdir distdir
> cd distdir
> cat ../bin01.* | uncompress | cpio -idvalmu

> into a directory under 'distdir'. But be warned: there may be complaints
> about some devices in distdir/dev/* which cannot be created if you are not
> root (depends on whether you may execute mknod). You may have to rebuild the
> devices on the 386bsd system manually.

> This procedure has been tested on a Sun4 Sparc.

I have heard you might need to add the -C option to cpio.

Nevertheless I myself said "Screw it" and solved the problem in another way.

FTP to gatekeeper.dec.com and get the SOURCES to real BSD cpio.  It's in
pub/bsd-sources-2/usr.bin/cpio.c.Z.  Create a .h file paths.h with 
#define _PATH_TTY "/dev/"

in it.  Compile it, ignoring the libraries in the initial comment.  It works
great.  

Eric

--
/=============================================================================\
| Eric Ewanco - Software Engineer     For the rash and outrageous opinions ex-|
| Digital Equipment Corp, Maynard MA  pressed herein I alone am responsible;  |
| ewanco@kalvin.enet.dec.com          they do not belong to DIGITAL(TM).      |
\==============================- 2 Th 2:15 -==================================/
    "...[T]he greatest and most ancient Church known to all, founded and
    organized at Rome by [] Peter and Paul, [is] that Church which has the
    tradition and faith which comes down to us after having been announced
    to men by the Apostles.  For with this Church, because of its superior
    origin, all Churches must agree ...  and it is in her that the
    faithful everywhere have maintained the Apostolic tradition."
       -- St. Irenaeus, Against Heresies, c. 180 A.D., 3,3,3.

Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: disklabel bug, 2nd swap partion problems
Organization: Nanyang Technological University - Singapore
X-Newsreader: Tin 1.1 PL4
Date: Wed, 26 Aug 1992 03:56:47 GMT


I'm running out of virtual memory space during installing of petdingo
software which is used for communication protocol specification, written
in g++.

When I modify disklabel to include fs type swap, during disklabel read,
it does not show that the type is swap.

swapon /dev/wd0d gave error warning of incompatible fs type (?)

I used disklabel -w wd0 qp230at

May be -w -r should do the trick?


--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: Is ISA ok?  or should I wait for EISA?
Date: 2 Sep 92 05:05:43 GMT
Organization: St. Peter's College, US

In article <47065@shamash.cdc.com>, pbd@runyon.cim.cdc.com (Paul Dokas) writes:
> My question is:  how does 386bsd perform with an ISA bus
> 386/486?  I'm especially interested in SCSI (Adaptec 1542B)
> throughput and X performance.
>
> So, here's your chance.  If you bought/have a machine and are
> disappointed or really happy with some piece of it (CPU, DISK,
> SVGA, etc) please let me know.  I'm especially interested in
> whether an ISA bus is capable of supporting X performance and
> SCSI disks without sluggishness.  If there is interest, I will
> post a summary.

  I've used the Jolitz's 386 port on a 386DX/25. I switched to BSDI's 386
port as I wanted to get my software developed, not work on the OS. However,
for this discussion, they should be performing about the same when run on
the same hardware.

  In short: it screams! I'm very happy with the speed of ISA systems running
Unix. I'm running an Everex 386DX/25, 16Mb, 64Kb cache, motherboard SVGA,
using both the built-in IDE and an Adaptec 1542B with a Maxtor 8760S I had
laying around. I've also used it with all of /usr NFS mounted from a Sun 3/60
and my login directory NFS mounted from a VAX 785. Disk I/O-intensive oper-
ations are faster on the 386 using NFS served disks than locally on the VAX,
which is amazing considering that the VAX is serving them to the 386.

  Also, things that take an hour to compile on the VAX take only 10 minutes
on the 386. I'm now doing most of my Unix development on the 386.

	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
From: ws@tools.de (Wolfgang Solfrank)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD: buffer space allocation -- a small bugfix.
Date: 29 Aug 92 19:11:32
Organization: TooLs GmbH, Bonn, Germany
NNTP-Posting-Host: kurt.tools.de
In-reply-to: tih@barsoom.nhh.no's message of Fri, 28 Aug 1992 08:14:08 GMT

In the place you mention the parameter cantwait doesn't have
any real relevance. But since the caller of kmem_malloc()
with canwait set probably doesn't check the return code
it's better to panic right away than by letting the kernel
use the NULL pointer and dereference it. If canwait is
clear the caller has to check the result anyway, so it
can return a NULL pointer as indication of failure.

The real canwait decision is done further down in the code.

Hope this helps...
--
ws@tools.de     (Wolfgang Solfrank, TooLs GmbH) +49-228-985800
Newsgroups: comp.unix.bsd
From: thostr@stud.cs.uit.no (Thomas Strandenaes)
Subject: Re: Small X for 386 bsd??
Organization: University of Tromsoe, Norway
Date: Mon, 31 Aug 1992 21:41:29 GMT

What he is looking for, is something similar to MGR; a subset
of X, with half the pain, and 3/4 the pleasure. Actually, I`m
too longing for something niftyer than X, which won`t make my
machine go slo-mo.

MGR, anyone?

//thomas
From: hpw@cunixb.cc.columbia.edu (Harry P Warren)
Newsgroups: comp.unix.bsd
Subject: Re: X386 and Diamond Stealth: not solution
Date: 25 Aug 92 21:13:16 GMT
Reply-To: hpw@cunixb.cc.columbia.edu (Harry P Warren)
Distribution: comp.unix.bsd, comp.unix.sysv386, comp.windows.x
Organization: Columbia University


>  For the interim, take your Stealth back to the store and get something
>  like an Orchid Farenheit svga! Or, wait till the end of the week till I get
>  more technically familiar the Farenheit svga card.

I am confused about the status of drivers for X386 running under
386BSD. From what I have read, it appears that the only support
currently available is for Tseng ET 4000 based video cards and clearly
S3 support is not available yet. What about ATI? And does "local bus"
effect compatibility?

I am going to purchase a 486 very soon and am trying to sort out all
of my hardware/OS options. As a former mac user/owner I am not used to
so many degrees of freedom . . .

harry warren
hpw@cunixb.cc.columbia.edu
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Re: Jim Blade's question on IDE drives' installation
Date: 26 Aug 92 16:06:19 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

In article <1992Aug19.040750.442@microsoft.com> jhenshaw@microsoft.com (Jeff Henshaw) writes:
|
|In article 3773 in comp.unix.bsd, jim@blade (Jim Rump)
|writes...
|
||  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?
|
|Please forgive me if this type of issue has been
|re-hashed before, but I didn't see a response off hand.
|
|Machine:	WYSE 386/16	4 Mb. RAM
|		80 Mb. Seagate IDE HD
|		3.5 & 5.25" floppies
|		Video7 VGA
|
|I tried installing 386BSD (0.1) from the "Tiny BSD" install
|diskette using the install script.  I'm installing
|from the 3-1/2" 1.44Mb drive, onto the 80Mb Seagate IDE
|drive [which is the only HD in the machine].
|
|The TinyBSD floppy boots perfectly, although is doesn't 
|list the name of my HD, as the install notes suggest it
|should (the install notes suggest checking the cabling, but
|everything else recognizes the drive).  Anyway, I proceed
|to install, and everything is apparently copied properly
|(I can hear the HD writing as the install script reports
|its actions).  However, upon getting the
|prompt "Press enter to boot from the HD," I hit enter,
|and after the floppy drives are checked, I'm left with
|a frozen machine with the A: (3.5") drive light on, even
|though the drive is empty.
|
|I've tried using FDISK to have a DOS and BSD partition,
|as well as letting the install script overwrite the whole
|drive.  I noticed that after booting the TinyBSD floppy,
|one can use the command "shutdown -todos" to restart and
|boot from a DOS partition.  Upon doing this [attempts to
|troubleshoot], the hard disk continually tries to initialize
|itself, and gets caught in a nasty, violent thrashing loop.
|
I've got similar problems. I couldn't get install to work (see previous
posting) so I installed everything by hand. When I rebooted I had the
same result, a: drive light on and a hang. Rebooting from floppy was ok
and everthying on my two partitions is still there. It just won't boot
from the hard disk.

I tried to fdisk my drive but that doesn't work either now. My hard disk
seems to be totally trashed. Using edpart it seems to think that I have
1023 cyls, 255 heads and 0 sectors!! Using diskedit gives the same
results. My bios settings are fine.

Are these parameters stored on the disk somewhere and have they been
overwritten?? Anyone got any ideas?

The drive is a seagate st1144a IDE.

-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr
+++
Newsgroups: comp.unix.bsd,comp.unix.sysv386,comp.windows.x
From: stu@jpusa1.chi.il.us (Stu Heiss)
Subject: Xconfig for Cardinal 742
Reply-To: stu@jpusa1.chi.il.us (Stu Heiss,925,6326,none)
Organization: JPUSA - Chicago, IL
Date: Fri, 4 Sep 1992 03:33:36 GMT

I have the lastest X for BSD386 and could use a working
Xconfig for the Cardinal 742 (et4000,max res 1280x1024i).
The monitor is oem'd for Tatung and can do whatever the
Cardinal can do.  If you have an Xconfig that would/should
work for this setup, please email me a copy.  Alternatively,
if you can advise me on how to figure this out, the book
for the Cardinal has a table of mode/pixel/hfreq/vfreq.
Any help would be highly apreciated.

Thanks, Stu
-- 
Stu Heiss - stu@jpusa1.chi.il.us
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Tape drive choices for 386BSD?
Organization: Weber State University  (Ogden, UT)
Date: Sun, 30 Aug 92 21:15:31 GMT

In article <1992Aug30.081319.7539@msuinfo.cl.msu.edu> paoletti@cps.msu.edu (David R. Paoletti) writes:
>I'd rather buy a simple QIC-80 such as a Colorado 250 for about
>$250.  Is someone working on support for drives of this type?

	Timing is critical on QIC-80 and QIC-40 drives.  I don't know if
anyone has gone in and added sufficient granularity to the scheduler and/or
interrupt code to fix this, but I seriously doubt it.

	There are several SCSI-based drives that have been tested and seem
to work on 386BSD... they are listed in a posting prior to this one about
the mudular SCSI system (not posted by me).

	I don't know what the status is on Computone/Archive drives which
come with their own controller (Anyone have one of these working?), but I
syspect you won't be able to get away very cheaply in any case unless you
are using SCSI.

					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
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: [386bsd] Virtual memory exhausted. Do I need more swap?
Date: 31 Aug 92 08:38:27 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <david.714981284@mlb.geomechanics.csiro.au> david@mlb.geomechanics.csiro.au (David Le Blanc) writes:

>When compiling some programs with GCC, I get the message 'virtual memory
>exhausted'. I have 40Meg virtual memory, so I am sure that is not the problem.

>Is there a setting with GCC which I should raise or what??

>Thanks.

>--
>David Le Blanc                         :
>Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
>CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
>P.O. Box 54 Mt Waverley 3149	       : in Alien^3.

You use the csh, don't you?

Enter 'limit' and you see why.
Enter 
'limit datasize unlimited' and
'limit memoryuse unlimited'.

I found this was a catch when I tried to compile X11.

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"
Newsgroups: comp.unix.bsd,comp.os.os2.misc
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: DOS + OS/2 2.0 + 386bsd 0.1 installation .....
Date: 31 Aug 92 10:05:53 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <1992Aug28.220423.9273@umr.edu> jlu@cs.umr.edu (Eric Jui-Lin Lu) writes:


>Dear netters,

>I have browsed thru the FAQs without any luck, although I think this
>question should be mentioned somewhere.  If I missed something, please
>no flame.

>After spending nights of reformats, reboots, and reinstallations, I
>kinda came out a wierd combination of DOS, OS/2, and 386bsd in one
>hard disk.  I used os-bs as the boot manager and its menu looks
>like DOS -- part 0, OS/2 part 1, and 386bsd in part 3.  Partition 2
>is for logical HPFS OS2.  I'm not quite satisfied with this.  Since
>when I choose OS/2, OS2 boot manager menu comes up.  I wish to
>eliminate this OS/2 boot manager totally.  Is there a way to do
>this? (this will save me another ~1.5MB.)  Thanks!

>--Eric
>--jlu@cs.umr.edu
>-- 
>***************************************---       Grad. student 		---*
>* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
>* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
>***************************************---   Univ. of Missouri-Rolla    ---*

I think there is an option in OS2 fdisk to enable or disable boot manager,
and to delete the partition. However, it is nearly impossible to
recombine the free space to any of the adjecent partitions on the disk
without remaking the corresponding filesystem.
As a replacement for the boot manager, there are different flavors of 
boot managers available (should be something about that in the FAQ(?)).

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"
Newsgroups: comp.unix.bsd
From: david@mlb.geomechanics.csiro.au (David Le Blanc)
Subject: [386bsd] can you boot from C: (wd0a) but use as0a as / (root)
Organization: CSIRO DIT (Melb.)
Date: 27 Aug 92 09:33:06 GMT

I want to have a partition on wd0a (C:) which contains boot code
and a copy of 386bsd (the kernel).

I want it to be configured to switch to as0a for mounting '/' on.

Can it be done?

--
David Le Blanc                         :
Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
P.O. Box 54 Mt Waverley 3149	       : in Alien^3.
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Extracted {bin,src,etc}dist and X386?
Organization: Weber State University  (Ogden, UT)
Date: Thu, 27 Aug 92 00:53:43 GMT

In article <colin.714802377@marsh> colin@marsh.cs.curtin.edu.au (Colin Manning) writes:
>Hi,
>	Is there anywhere that individual files from the {bin,src,etc}dist's
>can be got from (anon ftp?)?

agate.berkeley.edu.  Root directory is a directory under:

	pub/386BSD/386bsd-0.1/

X386 is not a standard distribution piece yet, but is under the ports
directory:

	pub/386BSD/ports-0.1/ (may be a little off on the actual name)

as a lump.  There is apparently a patched kernel in with it, as well as the
kernel patches to patch your own.


					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: zingelman@adcalc.fnal.gov
Newsgroups: comp.unix.bsd
Subject: workaround for kmem panic/hang w/NFS
Keywords: NFS, panic, hang, fix
Date: 31 Aug 92 14:31:00 GMT
Organization: Fermi National Accelerator Laboratory, AD/Controls
News-Software: VAX/VMS VNEWS 1.41

Here is a workaround that seems to fix problems with kmem panics and
hangs while doing NFS... (it has worked for at least one other person)

mount using the options "-o rsize=4096,wsize=4096" (the defaults are 8192.)

Since doing this, we have not seen another panic!  As a side effect, NFS
seems to run faster!

    This is our best guess, description of our system:
        a generic clone 80386 motherboard with an AMI MK-II AT BIOS,
        8 meg of memory, 80387, Twinhead EGA card, WD1007A disk controller
        with 2 CDC Wren III ESDI drives, and a 3com Etherlink II card.

    This is a list of patches we have applied:
        original 2nd drive patch
        MAX_KMAPENT increase patch
        bufpages = min(NKMEMCLUSTERS/2, bufpages) patch
        npx 0xf1 -> 0xb1 patch

"Tim Zingelman" <zingelman@adcalc.fnal.gov>