HDTenEightyP/NetNews huggingface dataset:
From: engel@opal.cs.tu-berlin.de (Christian Engel)
Subject: X386 xdm with crypt, other tools, printer EXPERIENCES
Summary: xdm compiled with crypt.cgd code available 
Keywords: xdm X386 crypt lpt.c
  
Organization: Techn. University of Berlin, Germany
Date: Wed, 9 Sep 1992 12:23:32 GMT

ftp.cs.tu-berlin.de

Directory:

pub/os/386BSD/386bsd-0.1/unofficial/local/xdm-crypt.engel.Z


Btw, I was able to compile the following software:

gnu find3.7
gnu make3.62
gnu gcc2.2.2
gnu libg++2.2 (libg++.a, iostream, stdio++)
gnu emacs18.58
gnu epoch4.1pl0
gnu texinfo2.15
gnu readline1.1
gnu bison1.18
xdviPl15
bricons
xtexcad1.2
xfig
xmenu


Kernel Patches
==============

I patched my kernel with the Unofficial Buglist (patches.tar.Z), new.com.cgd,
crypt.cgd, lptWithoutInterrupts, BusmouseV2, dmaFix, GreenmanFix (w/out no 5, I
think), ttyFix, ...
Since then I have no problems with crashing kernels anymore.


Printer Support
===============

I had many problems using the original lpt.c driver although patched with
lpt-haugh and the lp.c drivers.
Printing of normal ascii files was ok using the lp.c driver. But when I tried to
print a .dvi-djc file (Deskjet 500 output from dvi), character losses and even
crashes (lpt.c) occurred.
Switching off the printer caused a reboot.
I could solve the problem for lpt.c using an output filter, that flushed the
output and waited for a while (usleep) after a certain amount of characters were
sent to the printer.
I didn't need to use this filter for the new version of lpt.c that does busy
waiting.


X386
====

I am using one of the binary versions that were supplied. In the beginning I
used a serial mouse. In the beginning the mouse wasn't read properly. I worked a
bit on this problem using a mouse-test programme supplied with X11 for Linux,
that I had to change  a bit and figured out, that the terminal
characteristics weren't set properly.
The same seemed to occur with the X386 kernel.
Therefor I included an ``stty cs7 ...'' line into my .xinitrc and
/usr/lib/X11/xdm/Xsetup_0 and then the mouse worked fine. 




I hope these remarks help others to solve some of there problems with 386bsd.
If you want to have more information or other binaries made available, feel free
to contact me.


	Christian  (engel@cs.tu-berlin.de)





--
Christian Engel, TU-Berlin 	             mail: engel@cs.tu-berlin.de
TFS, dept of theoretical computer science,  formal specifications
address:   TU-Berlin, FR6-1, Franklinstr. 28/29, 1000 Berlin 10, Germany

Newsgroups: comp.unix.bsd
From: terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert)
Subject: Re: Trouble using an NFS filesystem
Organization: Novell NPD -- Sandy, UT
Date: Thu, 10 Sep 1992 22:08:06 GMT

In article <1992Sep10.162146.1@woods.ulowell.edu> jackson@woods.ulowell.edu writes:
>Now, for something related:
> 
>After ifconfig'ing ec0 and successfully ftp'ing/ping'ing a host on our net,
>I am having problems trying to access an NFS server.  The NFS server is a
>netware 3.11 box with Netware NFS v1.1.  I can get the server volume to mount
>on the 386bsd filesystem and running df gives an accurate report of the space
>available, but I am unable to do anything in the directory where the NFS
>volume is mounted.  Trying to do an ls or cp'ing something into that directory
>just gives me a permission denied error.  Doing an ls -l of the mount
>directory after I've mounted the volume shows the privledges as being:
> 
> drwx------     4 root          512 Sep 9 16:30 mcet1/    
> 
>It would seem as if I had the proper privledges, right?  Last, if I explicitly
>try to mount the NFS volume by hand with the command line:        
> 
> # mount /bsd386/@mcet1: /mcet1 (I know, I know, it should be /386bsd/ :-) )
> 
>I get a message that reads "Can't get net id for host".  I can't figure out if
>I've got something set up incorrectly on the Netware NFS hosts's side or if
>the problem is somewhere in how I've configured the 386bsd system.  Anyone
>want to offer any suggestions?    

1.	What are the permissions on the directory you are mounting over?  I
	suspect that you don't have permission.

2.	This information implies that you are root trying to access
	something in a directory owned by root on a remote machine.  Have
	you done a "root=<client host name>" as an option on the exporting
	host?  If not, you are coming in as id -2 ("nobody") and will not
	be allowed to access the directory.  I realize that doing this is
	"a bit different" using NetWare as a server.

3.	If you can't get an id for it, the host "mcet1" isn't in your hosts
	database.  If it is, perhaps the "<directory>@<host>" syntax is
	broken on your NFS.  Try "<host>:<directory>" instead.  One way
	this "break" might show up is your use of a ":" and an "@" in the
	same line, configuing BFS into thinking "/bsd386/@mcet1" was the
	host name and "" was the file name (the part with no whitespace
	seperator following the colon is empty in the line you gave).

Please post a followup telling which, if any of these, solved your problem.


					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.
From: aw2t+@andrew.cmu.edu (Alex R.N. Wetmore)
Newsgroups: comp.unix.bsd
Subject: questions
Date: 6 Sep 92 12:40:45 GMT
Article-I.D.: andrew.keeanBK00Voj4ICElE
Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA

Okay, thanks to all who answered my last questions.  Here are a few more:

1) is there a copy of netstat anywhere for 386bsd?

2) My machine can't seem to find localhost (which mail seems to use).  I
have it defined in /etc/hosts, however I am also using a nameserver. 
telneting to 127.0.0.1 does work however.  whats up here?

alex
From: jlackey@pimacc.pima.edu
Newsgroups: comp.unix.bsd
Subject: [386BSD] libm.a
Date: 15 Sep 92 00:48:41 GMT


Who is currently working on the math libraries?  Has any significant work
been done to fix them yet, or do I have to start from scratch?

Let me at 'em.

---
jlackey@pimacc.pima.edu
or sometimes
Josh.
Xref: sparky comp.unix.bsd:5489 comp.protocols.tcp-ip:4379
From: feoh@hal.gnu.ai.mit.edu (Chris Patti)
Newsgroups: comp.unix.bsd,comp.protocols.tcp-ip
Subject: nameserver resolution by adress (HELP!!!)
Date: 10 Sep 92 21:51:07 GMT
Organization: MIT Laboratory for Computer Science

We have a nameserver for a subdomain, and the nameserver one level
above us knows enough about us to be able to correctly resolve names,
but not addresses.  (i.e. the server above us has an NS record with
our nameserver listed to resolve all names with our domain postfix).
Does anyone happen to know the syntax necessary to make the 
nameserver above us send ADDRESS requests to our nameserver as well?
(A gethostbyname on a foreign host is successful, but then taking
that addr and trying to gethostbyaddr is NOT successful.)

Posting here is cool, or if you feel like it, please reply to:
bild@ncm.interlan.com

Thanks bunches...
bild
-- 
-------------------------------------------------------------------------------
Chris Patti | feoh@gnu.ai.mit.edu: A guest of the Free Software Foundation
=========#include <gratuitous_witty_quotes_section_to_waste_bandwidth>=========
"War is a symphony of destruction, orchestrated by few, paid for by many."
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: HP Vectra and 386BSD, hope it's not a FAQ
Date: 15 Sep 92 16:45:29 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de
Keywords: HP Vectra

In <u4901ac.716556561@sun7> u4901ac@sun7.LRZ-Muenchen.DE () writes:

>Hi,
>I tried to boot the tiny boot diskette on a HP Vectra 386/25 with 170 MB disk
>space. But the PC always reboots a few seconds after displaying the rom bios
>copyright. I've read bsd.faq very carefully and read nearly everything related
>in this newsgroup -- nothing seems to help me. I think it a problem of the 4
>extra k that this machine  uses for the rom bios. I tried the instructions
>recommended in bsd.faq but they are for an american setup program - I have
>a german one.

>Has anyone an idea to get rid of these 4 k ?


>-----------------------------------------------------------------------------
>Henning Brockfeld        u4901ac@sun7.lrz-muenchen.de
>Institute for economic geography
>University of Munich
>-----------------------------------------------------------------------------

I don't think that the 4k BIOS space will influence operation, because from
the moment the secondary bootloader is loaded the system is "flying" without
any BIOS support. So thether or not the data area is overwritten or
reserved for other things, is irrelevant then (unless is it mapped out of
the normal world by some chipset on the motherboard - then it is away).

I suspect that many problems relate to special, incompatible handling of 
essential facilities, here in particular the Gate A20 code. There are a couple
of different ways to enable this address bit, the keyboard controller method
used by IBM (and "compatibles") is just one. When I disassembled some version
of HIMEM.SYS long ago (just to find out what is does, no documentation on
XMS was available that time), I was really shocked to find undocumented
instructions (LOADALL'286) and about a dozen of different methods to 
detect special hardware and then switch this simple A20 bit on and off. 

I think, some sort of Compaq and the HP Vectra was among those incompatible
systems, but I am not quite sure. 

Holger

-- 
|  |   / Dr. 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: hedrick@athos.rutgers.edu (Charles Hedrick)
Newsgroups: comp.unix.bsd
Subject: more about 386BSD SLIP
Date: 7 Sep 92 18:41:54 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

Aside from the well-known silo overflow problem, I think there's
another problem in the serial driver.  I just had output hang in SLIP.
There's a well-known problem that causes output interrupts not to
happen sometimes.  I've heard people who really know the serial
devices claim that with correct interrupt handling code this won't
happen, but in every piece of device-level code I've seen, it has.
The problem showed up in SLIP8250 (the MSDOS packet driver -- I have a
fixed version), in the FTP Inc SLIP implementation (they fixed it a
couple of years ago), and Linux (until it was fixed several releases
ago).  The obvious solution is to time out serial writes.  If you send
a character and don't get output done within a reasonable time, just
assume the output worked and go ahead with the next.
Organization: Penn State University
Date: Fri, 11 Sep 1992 21:59:52 EDT
From: Mark Solsman <MHS108@psuvm.psu.edu>
Newsgroups: comp.unix.bsd
Subject: [386BSD] tinyBSD Does not recognize QIC-02 Drive

TinyBSD does not recognize my Archive VP402 QIC-02 controller and
Wangtek 5150EQ Drive.  I played around with the jumper settings, and none
of the following made any differnce..

Base I/O 200h irq 3 dma 1
 "       300h  "  3  "  1
         200h     5     1
         300h     5     1

Anyone have any suggestions? Anyone have this combo working in their system?


-----
Mark Solsman

The Pennsylvania State University  -  University Park, Pennsylvania
                "My opinions are not that of my own"
Newsgroups: comp.unix.bsd
From: richard@pegasus.com (Richard Foulk)
Subject: Re: 386bsd -- The New Newsgroup
Organization: Pegasus,  Honolulu
Date: Sun, 13 Sep 92 14:55:30 GMT

>>...More importantly, why comp.os.386bsd,...
>
>Because that's what it has been called since 1989 -- 386BSD! 250,000+ people
>can't be wrong.
>

And a zillion people call it Unix.  So why not:

	comp.unix.whatever... ?


-- 
Richard Foulk		richard@pegasus.com
From: jdb@bitcave.in-berlin.de (Joern D. Busch)
Newsgroups: comp.unix.bsd
Subject: (X386/Xfree86) clock.exe wanted
Date: 9 Sep 92 00:46:15 GMT
Organization: BitCave BBS, Berlin, FRG

I'm looking for the msdos binary clock.exe as included in X11R4's
X386.  I have no idea what my card's clocks are -- there are no
oscillators.  It's a Tseng 'MegaEva/1024'.  It seems the values
in modedb for Tseng HiColor don't apply (there are at least two
hicolor cards from Tseng).

thanks,
	Joern.
-- 
     Joern D. Busch, Postfach 210401, 1000 Berlin 21, FRG, (+49 30) 3931111
jdb@bitcave.in-berlin.de ..!mcsun!unido!fub!einoed!bitcave!jdb ..which reality? 
Newsgroups: comp.unix.bsd
From: ccml@hippo.ru.ac.za (Mike Lawrie)
Subject: Re: 386bsd -- The New Newsgroup
Keywords: newsgroup 386bsd news group
Organization: Rhodes University, Grahamstown, South Africa
Date: Sat, 12 Sep 1992 19:33:46 GMT

In <veit.716026274@du9ds3> veit@du9ds3.uni-duisburg.de (Holger Veit) writes:

>In <1992Sep8.200625.2894@socrates.umd.edu> john@socrates.umd.edu (John VanAntwerp) writes:

>>In article <18iprpINNg6e@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
>>>
>>>As per Bill's suggestion, here's a breakdown of some of the suggested 
>>>topics and groups:
>>>
>>>	comp.os.386bsd		(general questions and trivia)
>>>	comp.os.386bsd.kernel	(discussion on kernel content/structure)
>>>	comp.os.386bsd.windows	(ditto, on windowing systems like X)
>>>	comp.os.386bsd.sharedlib (shared library and programming environment)
>>>	comp.os.386bsd.net	(networking topics)
>>>	comp.os.386bsd.bugs	(new bugs)
>>>	comp.os.386bsd.ann	(announcements, fixes, additions)

>>I think that this is a fine set of newsgroups...

>>						John

>You should not multiply entities unless it is absolutely necessary
>(free translation of William of Occam's well-known statement). 

Evolution is better than revolution - surely if _one_ newsgroup is
handling (moderately well?) _all_ unix.bsd stuff, then there is no need
to move to _six_ additional groups? One additional group will suffice
until the test of time proves otherwise.

Mike
-- 
Mike Lawrie                                    <ccml@hippo.ru.ac.za>
Director, Computing Services                   ph +27 461 22023 x 279
Rhodes University, Drostdy Rd                  fx +27 461 25049
Grahamstown 6140, South Africa
Newsgroups: comp.unix.bsd
From: richard@pegasus.com (Richard Foulk)
Subject: Re: Controller manufacturers (was Re: Colorado Memory Systems)
Organization: Pegasus,  Honolulu
Date: Tue, 8 Sep 92 07:01:30 GMT

>>>...Also, you may add that [Colorado Memory Systems] will not release any
>>> technical information on their interface!
>> [...]
>
>Most of them are also not in the business of dealing with end-users, and
>this makes your problem of getting info harder still.  In fact, the way
>they're set up, they just don't have provisions for dealing with more than
>a few privileged software writers for their products.
>-- 

Sounds like acting like a large developer or someone that might buy
a zillion of them, when you call, might help a bit ...



-- 
Richard Foulk		richard@pegasus.com
From: eddy@aludra.usc.edu (George Edmond Eddy)
Newsgroups: comp.unix.bsd
Subject: Re: Help Needed on Installtion to my IDE HD
Date: 15 Sep 1992 09:48:22 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: aludra.usc.edu

benjie@quack.sac.ca.us (Android) writes:

>I post the problem two weeks ago and didn't get any answer.  Here I will
>try it again.
>I am having the reboot-loop problem, which the disklabel is missing.  I
>did the installation process through install* on disk.fs.
>I tried to install the system myself, but I don't know how to partition
>the harddrive using Tiny386.
>Please help.
>Ben

i am not sure what you meen by disklabel is missing?  anyway, the way i got
around the reboot loop was to remove the badsect flag from the disklabel,
using `disklabel -r -e wd0', or better yet, remove the :sf field from
the disktab entry.  I do not know if this is the proper thing to
do but, it is all i could come up with.
 
>I tried to install the system myself, but I don't know how to partition
>the harddrive using Tiny386.
 
you must boot from the fixit floppy and create your own disktab entry
to create *real* partitioning.  The process can be found in the FAQ,
from your favorite ftp site.


>-- 
>     BBB		Benjie Chen
>    BCCCB 		benjie@quack.sac.ca.us
>    BCCCB		No Axiomatic System Could Produce All Number-
>     BBB		Theoretical Truths, Unless It Is Inconsistent.

- rusty

--

eddy@usc.edu
Newsgroups: comp.unix.bsd
From: richard@pegasus.com (Richard Foulk)
Subject: Re: An overview of 17" monitors
Organization: Pegasus,  Honolulu
Date: Mon, 7 Sep 92 01:04:19 GMT

>>I don't know just what it is that keeps monitor prices so high.  (Conspiracy
>>theorists, this is your invitation!)  But the prices are entirely inelastic,
>>and unlike all other equipment in the same market, improvement has been
>>minimal-to-nonexistent.
>
>Monitors must be almost the oldest component of a computer outside of the
>keyboard and the fuse. I'd suspect their costs reflect the absence of 
>significant technological advances which translate to reduced cost of 
>production.

I don't think so.  Lack of volume is the problem.

Take a look at the difference in price between a 14" color tv and, say
a 20" one.

If the PC vendors would promote larger monitors more prices would start
coming down.  Fortunately more competition for 17" and larger monitors
is starting to show up, so hopefully things will start to change.

It's a catch-22, so movement from either side should get prices coming
down.


-- 
Richard Foulk		richard@pegasus.com
From: adam@micromuse.co.uk (Adam Kerrison)
Newsgroups: comp.unix.bsd
Subject: FORTRAN for 386BSD
Keywords: 386bsd fortran
Date: 11 Sep 92 15:46:27 GMT
Reply-To: adam@micromuse.co.uk
Organization: MicroMuse Ltd, London, Uk

Hi net-world,

Anybody know of a FORTRAN compiler suitable for 386BSD (i.e. freely 
available in source form) ????

Thanks

Adam


---
===========================================================================
Adam Kerrison                  | Phone : +44 71 352 7774
Technical Support              | Fax   : +44 71 351 7834
MicroMuse Ltd                  | Personal E-mail: adam@micromuse.co.uk 
London SW10 0RN                | Support E-mail : support@micromuse.co.uk 
===========================================================================
"When you kill a man, you're a murderer. Kill many, and you're a conqueror.
Kill them all, you're a god !" - Think about it
===========================================================================
From: davidg@lsil.com (Dave Gluss 7518)
Newsgroups: comp.unix.bsd
Subject: 386BSD, Re: Colorado Memory Systems tape drive
Keywords: IDE, Colorado Memory Systems
Date: 4 Sep 92 20:20:47 GMT
Reply-To: davidg@lsil.com
Organization: LSI Logic Microprocessor Group

I also tried to get documents from Colorado Memory Systems,
specifically about their TC-15 compressing interface board.  The
interface to that board is NOT standard and IS proprietary.  They
(Andy Grilnick at CMS) promised to send me some documentation for
interfacing with a standard floppy controller, but didn't.

The QIC standards committee will send you documentation, but you
have to know what to ask for--they don't know what's in the
documents, only how to send them to you.  The number there is
805-963-3853.  I have asked for QIC-80 rev D and QIC-117.

On another subject I am trying to get my new Maxtor 340A drive to
work as drive 1 with 386BSD--it bombs at the end of newfs with
"wdsetcntlr status 51 error 4".  I added Christoph Robitschko's
patches so I could access the drive.  I also uncommented the line
919 (in isa/wd.c) report on disk geometry-the disk reports 128
bytes/sector???  But everything else seems OK--the setcntrlr call
has 512 bytes/sector.  The bug always occurs at the end of the
newfs, even if I just newfs /dev/wd1a.

Has anyone succeeded at this?

---
--Dave Gluss    davidg@lsil.com     408-433-7518
From: goran@astro.uu.se (Goran Hammarback)
Newsgroups: comp.unix.bsd
Subject: Re: emacs for bsd386??
Date: 15 Sep 1992 14:20:47 GMT
Organization: Uppsala University
Distribution: world
NNTP-Posting-Host: solaris.astro.uu.se

In article <bcrawfor.716490140@sol.UVic.CA>, bcrawfor@sol.UVic.CA (Bryan Crawford) writes:
|> an anuyone point me in the right direction for acquiring
|> emacs (preferably GNU) which has been ported to BSD386.
|> 

Get the sources for emacs-18.58 and apply the patches in articles
2754 (clfatter@nrao.edu), and 3370 (sommerfeld@apollo.hp.com) from
comp.unix.bsd.
I did and it works (almost) perfectly.
-- 

Goran

------------------------------+---------------------------------
Goran Hammarback              |     goran@astro.uu.se
Astronomiska Observatoriet    |
Uppsala Universitet           |
S-751 20 SWEDEN               |
------------------------------+---------------------------------
Newsgroups: comp.unix.bsd
From: zawada@softage.demon.co.uk.demon.co.uk (Mark D Simpson)
Subject: PPP for 0.1
Distribution: world
Organization: Softage Solutions
Date: Fri, 4 Sep 1992 23:59:16 +0000

Has anybody out there got ppp working under 0.1 BSD, or is there
anyone working on it at the moment?

Thanks in advance.

Mark
--
Mark Simpson
SoftAge Solutions.
Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: 386BSD - Filesystem Trashed !!
Organization: /etc/organization
Date: Sun, 13 Sep 1992 15:31:46 GMT

We had files get trashed under 0.0 when swap wasn't on cylinder boundaries,
but have had *zero* problems with the filesystem since, plus 0.1 with SCSI.
-- 
-- Email info@NeoSoft.com for info on getting interactive Internet access.
You will now awaken feeling relaxed and refreshed, remembering everything 
you've read except the details of the Omega contingency plan.
From: deal@hightop.nrl.navy.mil (Richard Deal)
Newsgroups: comp.unix.bsd
Subject: /386bsd: reject 65340
Date: 14 Sep 92 15:01:50 GMT
Organization: Naval Research Labs (Washington DC)
Originator: deal@hightop

I have a 386 with binnary installed from disks.  It has an SMC ether
card that is recognised as we0.  everything was working nicely till I 
tried to set up the network on it.  I uncomented the we0 line in 
/etc/netstart and rebooted.  the console is flooded with 

/386bsd: reject65340   messages.  The number is mostly 65340 but is some
times 65342, 65344, 65366.  if I type 

ifconfig we0 down 
the messages stop but this doesn't help to get the network started.  Is 
there something I am missing (probably so) and what is it.  

thanks in advance.
butch deal

-- 
#include <std/*>
The Butcher                  
Butch Deal                   deal@hightop.nrl.navy.mil
--------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: fridlund@mermaid.micro.umn.edu (Jim Fridlund)
Subject: [386bsd] Real partitioning on SCSI system?
Organization: U of MN Computer Science, U of MN Astronomy
Distribution: comp
Date: Sun, 6 Sep 1992 00:53:41 GMT

Hi all,

I have a question about setting up 386BSD with "real
partitioning".  I'm using the method from the FAQ by
Chris Demetriou "How do I get 386bsd 0.1 installed with
'real' partitioning?".  I reached step 4, but it will
not allow me to mount my new root partition on /mnt.

Here's the error message I got:

# mount /dev/as0a /mnt
mount: /dev/as0a: Invalid argument.


I have a Maxtor XT8380S on an Adaptec 1542B.  I'm using
the 0.1 fixit.fs that suppose to have fixes by cgd, but
I think the fixes only applied to MFM or IDE.  The 'newfs'
command worked with the following homemade disktab:

maxtor8380|Maxtor XT8380S SCSI:\
	:dt=SCSI:ty=winchester:se#512:nt#8:ns#53:nc#1632:sf:\
	:pa#79000:oa#100:ta=4.2BSD:ba#4096:fa#512:\
	:pb#21600:ob#80000:tb=swap:\
	:pc#691968:oc#0:\
	:pd#200000:od#160000:td=4.2BSD:bd#4096:fd#512:\
	:ph#331968:oh#360000:th=4.2BSD:bh#4096:fh#512:

I have no idea what is wrong.  Did anybody ever run in to this
kind of problem before?  Am I using the wrong fixit.fs?  Any
help greatly appreciated.  Thanks much.


--
Jim Fridlund                                     U of MN - Computer Science
fridlund@mermaid.micro.umn.edu                   Institute of Technology
Newsgroups: comp.unix.bsd