HDTenEightyP/NetNews huggingface dataset:
From: niko@iastate.edu (Nikolaus E Schuessler)
Subject: * Disklabels - help please
Organization: Iowa State University, Ames, IA
Date: Fri, 1 Jan 1993 17:29:37 GMT

Howdy. I'm trying to write a disk label onto a floppy (from
a non-unix os), which I could do if I knew what to write...

Here is a description of the drive (for 400k ug):

Tracks     Sectors/Trk
0-15           12
16-31          11
32-47          10
48-63           9
64-79           8

I guess the drive rpm is variable as well...

so, what should the disktab have in it? Should I make descriptive
disknames like 'floppy800' and 'floppy1440' and just know from the
type that this is the scheme?

I could do something like:

ns=10
nt=1
nc=80
se=512

so that calculations for total disk space would come out correctly...
(a disk doesn't really have cylinders... right?)

Also, what partitons should a floppy have? just an `a' or `c' partition
(making the others 0 length)? 

since sector size is 512 bytes and the disk is tiny, 
block size = 1k and fragment size=512bytes? Or does one still want them to 
be 8k and 1k (respectively) like the defaults seem to be?

-- 
Niko Schuessler               
Project Vincent Systems Manager              email: niko@iastate.edu
Iowa State University Computation Center     voice: (515) 294-1672
Ames IA 50011                                snail: 272 Durham 
Newsgroups: comp.unix.bsd
From: dawes@physics.su.OZ.AU (David Dawes)
Subject: Re: XFree86 problem in XDrawSegments
Organization: School of Physics, University of Sydney, Australia
Date: Thu, 31 Dec 1992 03:01:08 GMT

In article <1992Dec30.140352.18037@ponds.uucp> rivers@ponds.uucp (Thomas David Rivers) writes:
>In article <1992Dec30.063602.8978@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>>In article <1992Dec30.013451.13074@ponds.uucp> rivers@ponds.uucp (Thomas David Rivers) writes:
>>>
>>> In trying to get cbzone up and running in 386bsd; I discovered the 
>>> following problem.
>>>
>>> I'm using XFree86 version 1.1 as available on agate.
>>>
>>> After the game starts up (opens the display and does some drawing) it
>>> will bomb out with the following message:
>>>
>>>XIO:  fatal IO error 14 (Bad address) on X server ":0.0"
>>>      after 400 requests (399 known processed) with 17 events remaining.
>>>
>>>
>>>  A breakpoint in _XDefaultIOError() reveals the following traceback:
>>>
>>>    _XDefaultIOError()
>>>    _XIOError()
>>>    _XSend()
>>>    _XDrawSegments()
>>>    multiline()              <----- cbzone function
>>>    drawhorizone()           <----- cbzone function
>>>    main()()                 <----- cbzone function
>>>
>>> It would appear that something is wrong in XDrawSegments....
>>>
>>> Has anyone else run into this?
>>
>>I have run into a similar problem (resulting in "BadMatch" errors) on an
>>AT&T X terminal.  The problem traced back to a modification of the GC
>>occurring before a draw, but not being forced to take effect (basically,
>>an event queueing problem).  Using an XSync( Display, False); prior to
>>the draw fixed the problem.
>>
>>
>>					Terry Lambert
>>					terry@icarus.weber.edu
>>					terry_lambert@novell.com
>>---
>>Any opinions in this posting are my own and not those of my present
>>or previous employers.
>>-- 
>>-------------------------------------------------------------------------------
>>                                        "I have an 8 user poetic license" - me
>> Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
>>-------------------------------------------------------------------------------
>
>
>
> Well, I was anxious and since that sounded plausible, I tried it out.
>
> Unfortunately, it didn't seem to change the situation.  I'm beginning
> to wonder if this is simply a R5 problem - except that I build it
> regularly at work with my own R5 X libraries for the IBM 370 (really, honest.)

I've built and run cbzone on XFree86 on a SVR4 box -- without any
problems.  The version of cbzone I have is PatchLevel 0.

David
--
------------------------------------------------------------------------------
 David Dawes <dawes@physics.su.oz.au>    DoD#210      | Phone: +61 2 692 2639
 School of Physics, University of Sydney, Australia   | Fax:   +61 2 660 2903
------------------------------------------------------------------------------
 I was so satisfied, deep down inside, like a hand in a velvet glove -- AC/DC
------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: msmith@beta.tricity.wsu.edu (Dragon Lord)
Subject: 386bsd Any QIC-80 tape drivers yet?
Organization: Washington State University Tri-Cities, Richland
Date: Thu, 31 Dec 92 00:04:03 GMT

Are there any QIC-80 drivers yet for 386BSD?  I have a Colorado Memory
Systems Jumbo 250 (DJ-20) run from my tape controller and I'd like to
use it for tape backup (beats swapping floppies on a 200 Meg drive!).

Thanks
From: redsonja@src4src.linet.org (Red Sonja)
Newsgroups: comp.unix.bsd
Subject: Re: IBM--What does it mean? (was: Reading joystick)
Date: 26 Dec 92 17:56:00 GMT
Organization: The Source for Source

In article <373@sleepy.UUCP> pat@sleepy.UUCP (Pat Eyler   ) writes:
>In article <michaelv.724971348@tbird.cc.iastate.edu>, michaelv@iastate.edu (Michael L. VanLoon) writes:
>> In <1247@galileo.rtn.ca.boeing.com> dmp3592@galileo.rtn.ca.boeing.com (Dean M. Phillips) writes:
>> >IBM: Incompatible Brain-damaged Machinery  ;-)
>> IBM: Inferior But Marketable
>> IBM: Industry's Biggest Mistake
>> Any others? :)
>
>IBM:  International Brotherhood of Magicians
>    (It's all smoke and mirrors and/or, they keep all their tricks secret.)
>
>      Pat Eyler   pat@sleepy.boeing.com

Ignorant Blissful Monomaniacs...
Idiots Believe Merchants...
Idolatry Becomes Marketing...

(I could go on forever!!)

-- 
------------------------------------------------------------------------------
redsonja@src4src.linet.org     \\\RS///    Self possession is 9/10 of the law.
------------------------------------------------------------------------------
From: peterson@notredame.ac.jp (Greg Peterson)
Newsgroups: comp.unix.bsd
Subject: RE: 386bsd - reinstall woes (solved)
Date: 27 Dec 92 16:58:20 GMT
Organization: Notre Dame Women's College, Kyoto, Japan.


I wrote:

> the system on the new disk (the whole disk), but the install program
> was interrupted. When I restarted "Tiny 386bsd" and ran install
> again, it reported that it was installed, then asked if I wanted to
> reinstall the system.

Thanks to tjb@NeoSoft.com (Timothy J. Bogart), who replied:

> There is a reference to an additional switch needed to remove
> 386bsd from an entire-disk installation mentioned in the install
> notes.  I don't remember the switch, but it explained that you

Yes, it is explained in INSTALL.NOTES. (When in doubt, read the
manual!) In order to set up the disk again, this time with both 
PC-DOS and 386BSD partitions, I had to use both methods documented
in INTSTALL.NOTES:

     Tiny 386BSD:  # cat /386bsd > /dev/ras0d
     PC-DOS:       A:>fdisk /mbr  
                     (then run fdisk to create primary DOS partition)

The order above is important.  First I tried just fdisk /mbr, which
seemed to work okay for DOS, but then when I tried to reinstall
386BSD, install went into an endless loop.  After following the steps
above, in that order, I was able to get both PC-DOS (IBM DOS J5.0/V -
Japanese DOS/V) and 386BSD set up. 

--
Greg Peterson - peterson@notredame.ac.jp
Notre Dame Women's College, Kyoto, JAPAN (Phone: +81 75 781-1173)
Home: Phone: +81 775 53-8614  Fax: +81 775 52-7768
From: ljo@r2d2.eeap.cwru.edu (L. Jonas Olsson)
Newsgroups: comp.unix.bsd
Subject: mawk (Was Re: gcc-2.3.2 and kernel build)
Date: 31 Dec 1992 17:15:22 GMT
Organization: Case Western Reserve Univ. Cleveland, Ohio (USA)
NNTP-Posting-Host: proteus.eeap.cwru.edu

In article <1ht0i9INNev6@life.ai.mit.edu> mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes:
>
>In article <1hqciuINN620@usenet.INS.CWRU.Edu> ljo@murphy.eeap.cwru.edu
>(L. Jonas Olsson) writes:
>>
>> One program that breaks is awk, but as this is the GNU gawk it should
>> perhaps be replaced by the latest version anyway.
>
>The `awk' which comes with 386BSD is *not* `gawk'; it is `mawk'.  I
>have installed gawk 2.14, and it works fine for me.

Yes I was wrong about this.
Onno van der Linden sent me patches for mawk1.1.2.tar.Z that I have put
in ref.tfs.com:/usp/packages/mawk. This mawk supposedly passes all tests
when compiled with gcc2, I have not had to test it myself though.

>> I will follow up with fixes as soon as I get uucp and Emacs up.

This is a mis-quoute, I did not write about uucp and Emacs.

>Emacs 18.59 comes with support for 386BSD; it is trivial to compile.
>
>-- 
> \  /   Charles Hannum, mycroft@ai.mit.edu
> /\ \   PGP public key available on request.  MIME, AMS, NextMail accepted.
>Scheme  White heterosexual atheist male (WHAM) pride!


Newsgroups: comp.unix.bsd
From: rivers@ponds.uucp (Thomas David Rivers)
Subject: XFree86 problem in XDrawSegments
Date: Wed, 30 Dec 1992 01:34:51 GMT


 In trying to get cbzone up and running in 386bsd; I discovered the 
 following problem.

 I'm using XFree86 version 1.1 as available on agate.

 After the game starts up (opens the display and does some drawing) it
 will bomb out with the following message:

XIO:  fatal IO error 14 (Bad address) on X server ":0.0"
      after 400 requests (399 known processed) with 17 events remaining.


  A breakpoint in _XDefaultIOError() reveals the following traceback:

    _XDefaultIOError()
    _XIOError()
    _XSend()
    _XDrawSegments()
    multiline()              <----- cbzone function
    drawhorizone()           <----- cbzone function
    main()()                 <----- cbzone function

 It would appear that something is wrong in XDrawSegments....

 Has anyone else run into this?

	- Dave Rivers -
	(rivers@ponds.uucp)
From: josephs@msen.com (Joseph Stroup)
Newsgroups: comp.unix.bsd
Subject: Help with CD ROM-BSDI
Date: 2 Jan 1993 19:47:42 -0500
Organization: Msen, Inc. -- Ann Arbor, Michigan
Distribution: world
NNTP-Posting-Host: garnet.msen.com

To make a long story short I have BSDI Gamma .0.9.4 and a Mitsumi CD ROM.
They say to set the CD up as Port 340 IRQ 2/9 and DRQ as 3. If anyone
of you experts has done this please e-mail me with the settings. 

I have set the jumpers to IRQ and the port correctly but there is not
a spot for the DMA jumper 3 on 5,6 and 7. The Rom works fine under dos 5
and I tried to run the install. It gets to the root question looking
for the device name , then I enter the  CD ROM code mcd0 after that it
see's the rom and hangs. The box its on is running a Conner IDE drive
and I know that one reason why the different settings.

I know that something simple will fix this and I have hardware all over
the place. I also have e-mail into BSDI and will call Monday a.m. Meanwhile
I just hoped one of you out there in Net land has done this andis running
this.

                  Email  josephs@garnet.msen.com

                  Thanks in advance.
                  `:wq
                  
-- 
Joseph Stroup
From: rob@wzv.win.tue.nl (Rob J. Nauta)
Newsgroups: comp.unix.bsd
Subject: Small 386BSD rexecd.c bug
Date: 28 Dec 92 21:30:58 GMT
Organization: None

I've noticed a small rexecd bug in the standard 386BSD code.

The protocol reads data from the socket, to be precise an ASCII
number, username, password, command. All separated by a NULL
byte. The number is used as the number of an additional socket 
for stderr. When the user is validated, the rexecd returns a null
byte and a shell is started with the in- and output connected to
the socket(s).

The problem is, that the standard distribution has a crypt()
routine which contains:
	char *
	crypt (k, s) char *k,*s; {
		write(2,"Crypt not present in system\n", 29);
		return(k);
	}

Now, this crypt() writes on stderr. The remote rexec eats the
first byte, so the user sees
	rypt not present in system
instead of the real error, and the connection fails.

Now, I know that most people immediately install a crypt-replacement
package, so before I patch this, I'd like to ask the net if
- It has been patched already ?
- Is it worth it to fix ??

Please send email

Rob
-- 
/-----------------------------------------------\       Never              ,==.
| Rob J. Nauta, UNIX computer security expert.  |        Apologize,       /@  |
| rob@wzv.win.tue.nl, Phone: +31-40-837549      |         Never          /_  <
| Feel free to email me for free advice         |          Explain.     =" `g'
From: knier@miller.cs.uwm.edu (Robert Knier )
Newsgroups: comp.unix.bsd
Subject: SCSI card supported with new drivers (Julians)
Date: 4 Jan 1993 01:37:40 GMT
Organization: University of Wisconsin, Milwaukee
NNTP-Posting-Host: 129.89.9.13

	All:

		I came across a Future Domain compatible SCSI card and had
some questions.  This card is a Dandy-3400 which claims to be compatible with
the Future Domain card.  It contains the TMC - 950 Chip (Manufactured by 
Future Domain).  Although it looks like a 16 bit card upon closer evaluation,
it only uses a 8 bit data path (The additional lines from the 16 bit slot
seem to be for a wider range of interrupt settings).  This card only has two
settings, the IRQ line and the BIOS address range (additionally it can act as
a FDD controller).  Would anyone know anything about this card?  What port(s)
does it use?  It doesn't seem to use DMA transfers - is this true?  Is this
supported by Julian's drivers?
	I am also looking at the Always IN 2000 SCSI card.  How does this
stack up?  Is it supported by Julian's drivers?


Many thanks in advance, 


Robert Knier
(knier@miller.cs.uwm.edu)
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (& Murphey)
Subject: Re: iBCS2 / SCO 3.2.4
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Thu, 31 Dec 1992 04:41:13 GMT

Dave> In article <1992Dec30.154921.23024@cognos.com> nigelc@cognos.com 
Dave>   (Nigel Campbell) originally posted in comp.unix.misc:
>This follows a recent post looking for a list of vendors who are
>'binary' compatible with SCO UNIX (I assume 3.2.4). Is there
>a list somewhere of these vendors and commercial software known
>to run/not run on systems other than SCO. How does one certify
>adherence to the iBCS2 definition. What is it. 
>

Dave>   I was wondering if any of the 386bsd developers had ever heard of the iBCS2
Dave> definition, and is it reasonable to try to get 386bsd compliant with it.  If
Dave> this 'standard' is reasonable, it would seem a good thing to be binary
Dave> compatible with somebody, n'est pas?

Lynne Jolitz posted a bibliography a few days ago in which she
suggested we use '"The Intel 386 Architecture and System V BCS" for an
understanding of defined interfaces.'

Intel's publishing/sales dept (1-800-548-4724) says it isn't available
yet.  They do have a generic "386 BCS Spec 2" that Lynne suggested
would not be as useful as the System V BCS specific book.  Rich
Newsgroups: comp.unix.bsd
From: dmuntz@quip.eecs.umich.edu (Dan Muntz)
Subject: Re: [386BSD] as a router
Organization: University of Michigan EECS Dept., Ann Arbor
Date: Tue, 29 Dec 1992 03:51:49 GMT

In article <1992Dec28.190134.25314@kumr.lns.com> pozar@kumr.lns.com (Tim Pozar) writes:
>
>   I would like to investigate the possibilities of using 386bsd as a
>router to replace my KA9Q box.  When I looked through the FAQ (question
>2.47) it mentions that it is possible but it is "hard wired off".  How
>does one, hard wire it back on?

I'm using a 386bsd machine as a slip router, and as far as I know, I'm
running the distribution version of the routing code.  I did add an
'options GATEWAY' to my kernel config file.

  -Dan
   dmuntz@eecs.umich.edu

Newsgroups: comp.unix.bsd
From: vpham@cs.ulowell.edu (vinh)
Subject: Re: Install bindist from C: or FTP+NE1000
Organization: University of Massachusetts at Lowell Computer Science
Date: Tue, 29 Dec 1992 22:50:37 GMT

In article <21250011@hpuamsa.neth.hp.com> reink@hpuamsa.neth.hp.com (Reinier Kleipool) writes:
>Hello,
>
>
>  That is right. The ne driver is internal in the kernal only.
>It does not have a /dev/ specialfile. So
why is it that network cards dont' conforrm to the standard 
UNIX device(neither a block nor a character device).
Is there any historical reason?
Thanks.`
From: mike@starburst.umd.edu (Michael F. Santangelo)
Newsgroups: comp.unix.bsd
Subject: Re: S3 question - Amancio, are you there?
Date: 28 Dec 1992 05:15:00 GMT
Organization: University of Maryland, Chesapeake Biological Laboratory
NNTP-Posting-Host: starburst.umd.edu

mike@starburst.umd.edu (Michael F. Santangelo) writes:

>hasty@netcom.com (Amancio Hasty Jr) writes:

>...stuff deleted...

>>The January issue of Byte magazine voted the Actix's GraphicEngine32 (801)
>>as one of the best overall graphic accelarated cards for window applications.
>>At least on Byte's tests the 801 was faster than the ATI Ultra Pro (mach 32).
>>And, I really doubt that the tests were executed at low clock frequencies.
>>However, the article did not state the dot clock frequency which the tests 
>>were executed at.  The other faster cards were based on the 34020 and cost
>>more than $1400.

>The BYTE article says on p. 206 that they used 1024x768 resolution, 72Hz at
>256 colors with all the cards in that test that could support it.

Again [wups] they did not explicitly say 72Hz, my mistake, it was on
the table on p.204-205 as the max refresh rate for this card.  They
definitly did use 1024x768 resolution though.  The author might have,
we just aren't sure.  Unfortunately the only email address listed
for the author is on BIX ("rick_g").

Apologies.

>--
>-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>Michael F. Santangelo                 + Internet: mike@cbl.umd.edu      [work]
>Computer & Network Systems Head       +           mike@kavishar.umd.edu [home]
>Univ MD: CEES / CBL (Solomons Island) + BITNET:   MIKE@UMUC  [fwd to mike@cbl]
--
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Michael F. Santangelo                 + Internet: mike@cbl.umd.edu      [work]
Computer & Network Systems Head       +           mike@kavishar.umd.edu [home]
Univ MD: CEES / CBL (Solomons Island) + BITNET:   MIKE@UMUC  [fwd to mike@cbl]
Newsgroups: comp.unix.bsd,comp.unix.wizards,alt.security
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: WEIRD IDEA? (chroot) Some corrections.
Originator: tchrist@pixel.convex.com
Date: Tue, 29 Dec 1992 20:32:31 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: Convex Computer Corporation, Colorado Springs, CO
Keywords: chroot, shadow login, pirates BBS
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

Chroot may not be so wondrous as you may think.

If your interloper should manage to crack root inside of the chroot box,
you can still be in for big problems.  A kmem or a disk device inode
inside the box is as valid as one outside, allowing someone to peek 
anywhere in the kernel or disk or even poke himself out of the box!
Remember also that privileged sockets have no concept of chroot, so
anyone could be impersonated going over the net.

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist


    "We don't care.  We don't have to.  We're the Phone Company."
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: [386bsd] GNU malloc in favor of BSD ma
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Fri, 1 Jan 1993 03:14:38 GMT

In article 15123@serval.net.wsu.edu, hlu@eecs.wsu.edu (H.J. Lu) writes:
>In article <1hvu79INNjqq@ftp.UU.NET>, sef@Kithrup.COM (Sean Eric Fagan) writes:
>|> In article <JKH.92Dec31154004@whisker.lotus.ie> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes:
>|> >I say we petition Bill to use GNU malloc in preference.
>|> 
>|> GNU malloc is copylefted.  Using it in a library means that every program
>|> compiled using that library is copylefted.  That is almost certainly the
>|> reason why it is not used, and I cannot fault anyone for that.
>
>Is that under GLGPL? Another `feature' in GNU malloc is malloc (0) returns
>NULL.

The version of malloc in GNU libc is under the library license.

malloc(0) returning a NULL pointer conforms to the ANSI C standard (malloc(0)
may either return NULL or an unique, implementation-defined pointer.

	Chris Flatters
	cflatter@nrao.edu
From: tjw00@zombie.uucp (Tom Wye)
Newsgroups: comp.unix.bsd
Subject: Does 386BSD work on systems with 20 megabytes of memory! HELP!
Date: 28 Dec 92 23:09:29 GMT
Distribution: comp.unix.bsd
Organization: Amdahl Corporation

Does 386BSD work on machines with 20 megabytes of memory or more? HELP!!!!

The system slowly crashs and burns when I boot with 20 megabytes of storage     
installed. The same kernel runs ok with 4 megabytes.
--------------------------------------------------------------------------------
My configuration is as follows:

PC Clone
Motherboard: NICE 486DX50 Mhz 256K cache
AMI BIOS
Memory in bank 0 - 4 x 1m sims for 4M 
Memory in bank 1 - 4 x 4m sims for 16M 
Adaptec 1542BB

With 4 megabytes of memory installed I can rebuild the kernel!

Kernal rebuilt (GENERICISA) with Terry Lamberts patch kit all patches
except Patch00026, 27 and Patch00056 included.
------------------------------------------------------------------------
Symptom (same kernel ok with only 4 megabytes of memory)

With 20 megabytes installed. The system panics in various places.

Example:

I boot the system with 20M installed, the system comes up ok, but various
commands will die. Do a MAKE and I get a "Bus error" *** error code 138.
Do a ls and get a core dump. But in most cases the entire system panics and 
either hangs or reboots. Seems the file system gets pretty messed up too.
-------------------------------------------------------------------------------
So any HELP would be appreciated!
Newsgroups: comp.unix.bsd
From: brad@bradley.bradley.edu (Bradley E. Smith)
Subject: Re: IBM--What does it mean? (was: Reading joystick)
Organization: Bradley University
Date: Thu, 24 Dec 92 16:33:39 GMT

In <822@nfsun.UUCP> gchamber@nfsun.UUCP (Glenn Chambers) writes:
>>>IBM: Incompatible Brain-damaged Machinery  ;-)
>>IBM: Inferior But Marketable
>>IBM: Industry's Biggest Mistake
>IBM: I've Been Moved
>IBM: International Brotherhood of Magicians
>    (an actual organization)
>IBM: Itty Bitty Machine company
>    (an actual, probably defunct, computer store on the left coast)
IBM: I've Been Mislead
-- 
Bradley Smith			 brad@bradley.edu ---  309-677-2337
Network & Technical Services @ Bradley University, Peoria, IL

"It's amazing how much scrap metal you get from 4 cans of beer"
Newsgroups: comp.unix.bsd
From: glenc@netcom.com (Glen Collins)
Subject: QIC-80 Tape drivers
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: na
Date: Sun, 3 Jan 1993 03:33:35 GMT

I was wondering, I just picked up the other day a QIC-80 tape driver
from (opp, forgot), anyways hase anyone been able to compile it on
386BSD? I have not yet installed my BSD system, so I cannot try it, but
they do mention in the documenation that it will support the colorado
tape. The filename as I remember is ftape.tar.Z. Looks like it's a
fairly complete driver, but since I have not compiled it I have no
idea!

-Glen Collins
	(glenc@netcom.com)