HDTenEightyP/NetNews huggingface dataset:
From: jim@ferkel.ucsb.edu (Jim Lick)
Subject: Re: AT&T sues BSDI
Organization: University of California, Santa Barbara
Date: Mon, 27 Jul 1992 23:04:11 GMT

In <1992Jul27.140005.23776@ryptyde.cts.com> scott@ryptyde.cts.com (Scott McClure) writes:
>I don't think that it would do much, considering the break up of AT&T.
>USL is no longer directly connected to it (at least, that's what I've 
>heard).  You'd be bashing seperate company.

AT&T is still the majority owner of USL though.  I believe they own
55% of USL, although that figure could just be my imagination.  In
this case, any harm against AT&T would cause them to exert pressure
on USL to change.  And any harm against USL would mean less profit
for AT&T.  Sounds pretty well connected to me.

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

More directly, I am not upgrading from Esix 4.0.3a to Esix 4.0.4.
I don't know how much in the way of licensing USL loses from this,
but it's probably substantial.

                            Jim Lick		       
Work: University of California	| Play: 1236 Camino Meleno
      Santa Barbara		|       Santa Barbara, CA 93111-1007
      Dept. of Mechanical Engr. |	(805) 964-2088 voice/msg
      2311 Engr II Building     |	(805) MUD-SPY1 data
      (805) 893-4113            |       jim@case.isla-vista.ca.us
      jim@ferkel.ucsb.edu	|       jim@cave.isla-vista.ca.us
Newsgroups: comp.unix.bsd
From: mak@tgivan.wimsey.bc.ca (Bob Makowski)
Subject: Re: STREAMS and OSF [Was: AT&T vs. BSDI ad nauseam
Followup-To: comp.unix.bsd
Summary: STREAMS and OSF
Keywords: STREAMS OSF licence
Organization: Not Hardly
Distribution: na
Date: Wed, 29 Jul 1992 22:01:42 GMT

In article <1992Jul24.185653.3196@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>In addition, OSF specifically licensed parts of the SysVr3.x code from USL
>in order to include it in OSF/1.  Specifically, the STREAMS code, as there
>were no such things in the original Mach code.
>

Sean,

Are U sure?

I was aware that OSF had a streams project ongoing, but I've heard nothing
to suggest that OSF resolved this via the distribution, and concomitant
royalties, of *any* post-SVR2 source baseline.

(STREAMS circa) SVR3 and AT&T's licencing changes were major points
of contention that eventually evolved into OSF. The problem was that AT&T's
original SVR3 licence was contrived to require SVID compliance for the
entire O/S, and not just the portion that a vendor ported from SVR3. A big
bruhaha resulted in relaxing into a piecemeal SVID compliance revision of
the licencing agreement, but I've noticed that every OSF vendor only cites
AT&T/UNIX copyrights through SVR2 to this day.

There's more to this saga, which is important to note in the AT&T/BSDI
thread, but I haven't completed my review thereof.

= Mak
Newsgroups: comp.unix.bsd
From: erc@unislc.uucp (Ed Carp)
Subject: Re: AT&T sues BSDI
X-Newsreader: Tin 1.1 PL4
Organization: Unisys Corporation SLC
Date: Tue, 21 Jul 1992 23:57:27 GMT

quanstro@lars.StOlaf.edu (goon) writes:

:    Imminent death of free-UN*X systems predicted...
: 
: Wouldn't that be great!
: 
: Imagine being creative and trying to sythesize all that's been learned
: from Unix (R) in the last twenty years and actually trying to break
: out of the YAU (yet another Uni*) mold. . .

And AT&T would probably sue you, claiming that you got the ideas from any
exposure that you have had to any UNIX code derived (or claim to be derived)
from AT&T "proprietary" code.

The bottom line is that, if AT&T wins, any piece of code that any programmer
has written or will write that contains even the slightest hint of containing
"intellectual property" of AT&T (such as "for(i=0;i<XYZ; i++)") will be
claimed by AT&T as derivitive of that so-called "intellectual property".

Oops ... I just did it, didn't I? :)
-- 
Ed Carp, N7EKG		erc@apple.com	<-- preferred email address!
"In wildness is the preservation of the world."  - Henry David Thoreau
** Member, Linux port team - uucp division ** :)   801/269-8125
Newsgroups: comp.unix.bsd
From: vepaepck@immd4.informatik.uni-erlangen.de (Volker Paepcke (CIP87))
Subject: 386BSD-0.1: Problems with ifconfig ne0
Organization: CSD., University of Erlangen, Germany
Date: Thu, 23 Jul 1992 15:28:27 GMT

Hi!
  I've got running the new release after installation from the TINY disk
and it's booting from the harddisk now. But then, after running ifconfig
ne0 <myadress>, the system is printing messages of the form: startart
all over the screen. I can run route add default <adress> and start ftp
without problems, but the messages are still coming. There is no string
like this in any of the kernel-sources so I don't know to get rid of
this problem.

  If there is anybody, who has similar problems or any hints, please
email me! 

    Thanks, Volker.

Volker Paepcke, Universitaet Erlangen-Nuernberg
email: vepaepck@cip.informatik.uni-erlangen.de
From: randy@psg.com (Randy Bush)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 27 Jul 92 15:26:14 GMT
Organization: Pacific Systems Group, Portland Oregon, US

Let's get down to basics.  This is going to cost a lot of cash to fight.  So
where do we send donations?
-- 
randy@psg.com   ...!uunet!m2xenix!randy
Xref: sparky comp.unix.bsd:2700 comp.unix.misc:3003 comp.sys.sun.admin:4909 comp.unix.admin:4290 comp.unix.internals:1598 comp.unix.solaris:111 comp.unix.sysv386:12342 comp.unix.wizards:3291
From: dennis@nebulus.ca (Dennis S. Breckenridge)
Newsgroups: comp.unix.bsd,comp.unix.misc,comp.sys.sun.admin,comp.unix.admin,comp.unix.internals,comp.unix.solaris,comp.unix.sysv386,comp.unix.wizards
Subject: Re: AT&T sues BSDI
Keywords: BSDI AT&T
Date: 23 Jul 92 17:34:15 GMT
Organization: Alchemy Mindworks, Edmonton, Alberta

lyndon@ampr.ab.ca (Lyndon Nerenberg) writes:

>I discovered yesterday that AT&T is the long distance carrier for
>Cantel (the biggest cellular telephone carrier in Canada), at least for
>calls placed from Alberta and British Columbia. (Strange, eh?)

Cellular One has a billing relationship with Cantel as well. I get
them as my carrier when I travel to the U.S. with my cell phone. I
wonder if they have a similar relationship. I too will complain to
Cantel. 

This is not the first time the Corporate Giant squashes the little
guy in litigation expenses. Send your $1000.00 to BSDI and get a 
source license now. They will need the money and we will benefit
as well. AT&T Canada put an individual in the poor house a couple
of years ago. It was splattered all over W5. 

This thread is splintered all over the place. Can we all post to 
comp.unix.bsd. The AT&T <-> BSDI is showing up everywhere. There
are good ideas in all of the groups, but it would benefit all if
we kept it in one group. 

Boycott AT&T
-- 
-------------------------------------------------------------------------------
    Dennis S. Breckenridge VE7TCP@VE7TCP [44.135.160.59]  dennis@nebulus.ca
Just because everything is different doesn't mean anything has changed - Oracle
-------------------------------------------------------------------------------
Xref: sparky comp.unix.bsd:2832 comp.sys.ibm.pc.hardware:20260
From: heiko@uwesa.hanse.de (Heiko Weber)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1 and Net/2 - Are there diff's ?
Date: 29 Jul 92 21:28:39 GMT

I just picked up a copy of the Net/2 tape ... but the
release 0.0 included a diff to the Net/2 release,
will there be also a diff for the actual one, 0.1 or
any releases in the future ?

Heiko

--
| Heiko Weber jun. | heiko@uwesa.hanse.de | carrier: 049-4169-448 |
| D-2151 Sauensiek | Loehe 5 |  Germany   | voice:  049-4169-1366 |
+------------------+----------------------+-----------------------+
Newsgroups: comp.unix.bsd
From: mgrjtb@nextwork.rose-hulman.edu
Subject: Re: AT&T sues BSDI
Organization: Rose-Hulman Institute of Technology
Date: Tue, 21 Jul 1992 16:11:00 GMT


In article <1992Jul21.064525.19093@resonex.com> michael@resonex.com (Michael  
Bryan) writes:
> In article <1992Jul21.030532.10307@kithrup.COM> sef@kithrup.COM (Sean Eric  
Fagan) writes:
> >In other words (potentially *wrong* words, mind you, since I'm not a
> >lawyer), *anything* based on the Net/2 tape, according to USL, requires an
> >AT&T/USL license!! (EEEEP!)
> >
> >Comments, anyone?
> 
> Imminent death of free-UN*X systems predicted...

Is BSD net/2 the only free real UN*X?!!!  Horse hockey....

Linux is almost ready for version 1.0 in about a year and a half...and you  
predict death of free UN*X's?!!!!

With Mach and Hurd, I was planning for the death of unrealistically high priced  
UN*X's.  
 
> -- 
> Michael Bryan        michael@resonex.com                     |     ,_,
> "Pretenders I meet are making a trail along the way.         |    /oo \
> They say that they know how to show me a path to guide my    |    <>__|
> way to truth..." --- David York, "The Quiet of a Candle"     |    |  U|

--
____________________________________________________________
         Joseph T. Batt - deranged CS undergrad...

     mgrjtb@nextwork.rose-hulman.edu = &(Joseph T. Batt);
____________________________________________________________
        Real programmers start counting with zero....
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: 386BSD-0.1/BRLCAD4.0 benchmark -- poor floa
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Wed, 29 Jul 1992 15:29:14 GMT

In article l7ctu0INN880@neuro.usc.edu, merlin@neuro.usc.edu (merlin) writes:
>It looks like the floating point processor is used for simple floating
>point operations (+, -, /, *) but not for higher functions -- these go
>to /usr/src/lib/libm/ieee/support.c where they get emulated (ie _sqrt)
>very slowly.  Perhaps someone has a redistributable i386 library which
>could be plugged in place of the default 4.3BSD mathematics library.
>
>This is likely why BRLCAD 4.0 runs correctly but very slowly at the
>present time.  Any help or suggestions which would fix this problem
>would be very much appreciated.  
>
>Does gcc 2.2 actually use 80387 inline code for transcedental functions?

No. I just looked :-(.  (Unless it is very well hidden).

It could probably be made to though.  There appears to be some support for
inlining transcendental functions for the Moto 68881.

	Chris Flatters
	cflatter@nrao.edu

Newsgroups: comp.unix.bsd
From: tg@utstat.uucp (Tom Glinos)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: University of Toronto, Dept. of Statistics
Date: Fri, 24 Jul 1992 20:05:04 GMT

In article <1992Jul24.165236.10937@Warren.MENTORG.COM> tal@Warren.MENTORG.COM (Tom Limoncelli) writes:
>The press releases I was talking about MOSTLY mention OSF!  Buying OSF
>results in USL making 0 $$$.

Wrong. If OSF has any technology based on AT&T source then they pay $$$ to
USL.
-- 
=================
No regrets, ever!			| Tom Glinos @ U of Toronto Statistics
For down that path, lies madness	| tg@utstat.toronto.edu
Newsgroups: comp.unix.bsd
From: mark@csd4.csd.uwm.edu (Mark Bamberg)
Subject:  BSD Unix for 68040 (MVME167)
Originator: mark@csd4.csd.uwm.edu
Organization: Computing Services Division, University of Wisconsin - Milwaukee
Distribution: usa
Date: Wed, 22 Jul 1992 17:51:07 GMT

We are looking for a BSD4.2/SUN OS3.5 compatible UNIX that runs on
a Motorola 68040 board (MVME 167) .

We prefer real time extensions, cross development from a SPARC running
SUN OS 4.1.1.  

Any help would be appreciated.

Another frustrated former SUN/68020 left tangling by my half-word aligned 
addresses.

Mark

Newsgroups: comp.unix.bsd
From: kwan@netcom.com (Kwan-Seng Low)
Subject: tip to modem not working...
Date: Fri, 31 Jul 92 07:45:10 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Keywords: 386bsd0.1, tip, modem

Finally, got my tip to work properly, but I still can't talk to my
modem...
tip com2
connected       (follow with a beep)

no response from modem no matter what I type. I'm using telebit T1000.
The DTR light is on. Has anyone gotten 386bsd0.1 working with modem yet?
If someone could share their experience on getting the modem to work,
especially on telebit or modem in general, would be appreciated.
 
Kwan-Seng Low
Newsgroups: comp.unix.bsd
From: chmr@fstgds01.tu-graz.ac.at (Christoph Robitschko)
Subject: Re: 386BSD: Dinky little socket(?) bug -- ^V as escape character?
Organization: Technical University of Graz, Austria
Date: Thu, 30 Jul 92 08:10:47 GMT

In article <1992Jul30.011650.5292@pasteur.Berkeley.EDU> sim@cory.Berkeley.EDU (Peng-Toh Sim) writes:
>In article <sand.712454840@milton> sand@milton.u.washington.edu (Derek Upham) writes:
[complains that he has to press ^V twice to be interpreted in a screen session]
>
>
>I believe this bug is due to misinterpretation of POSIX.1 .
>I have seen this bug under 0.0 with screen3.2 and kermit 5a.
>When screen3.2 or kermit is compiled with POSIX.1 termios, it
>switches to RAW mode by resetting ICANON in c_lflags for the
>terminal.  This, however, does not disable IEXTEN under the
>current implementation of 386bsd, so keys enabled by IEXTEN like
>^V still gets processed.  Since with screen (or kermit), you go
>though the tty discipline twice, ^V gets processed twice.
>Example, if you want to enter ^V itself, you have to hit it four times!!!
>I figure this from "POSIX Programmer's Guide" by Donald Lewine.
>However, this book does not say if the kernel should ignore IEXTEN when
>ICANON is not set.  So I don't know who's bug this is.
>My modified version of screen3.2 and kermit disables the IEXTEN flag
>when they switch to RAW mode so I don't see this problem.
>
>Can somebody who has access to the actual POSIX.1 document comment
>on this please?
>
>PT
>sim@cory.berkeley.edu
>
From "Portable Operating System Interface (POSIX) Part 1: System Application
Program Interface (API) [C Language]" ("IEEE Std 1003.1 - 1990"), Chapter
7.1.2.4:

# If IEXTEN is set,implementation-defined functions shall be recognized from the
# input data. It is implementation defined how IEXTEN being set interacts with
# ICANON, ISIG, IXON, or IXOFF. If IEXTEN is not set, then implementation-
# defined functions shall not be recognized, and the corresponding input
# characters shall be processed as described for ICANON, ISIG, IXON, or IXOFF.

Typing errors are my own intellectual property 8->

							Christoph
-- 
------------------------------------------------------------------------
Christoph M. Robitschko  | "the only man who got his work done by Friday
chmr@edvz.tu-graz.ac.at  |             was Robinson Crusoe."
Newsgroups: comp.unix.bsd
From: jimj@miller.cs.uwm.edu (James Jegers)
Subject: MS-DOS arc programs available
Keywords: arc, zip, unzip, zoo
Organization: University of Wisconsin, Milwaukee
Date: Wed, 22 Jul 1992 20:41:33 GMT


    Since we are running 386bsd on top of a machine that is usually
    running MS-DOS.  It sometimes comes in handy to have some more
    MS-DOS utilities.  So I have compiled

       arc - v5.21
       lharc - the new v1.02 
       zip - v1.0
       unzip - v5.0
       zoo - 2.1

   I put the sources and binaries on   agate.berkeley.edu 
   and also have them locally here on  (129.89.9.117)

				vernam.cs.uwm.edu:/386bsd/compression.tar.Z

-- 
     ______________________________________________________________
    /\               University of Wisconsin -- Milwaukee          \
    \_| Computing Services Division     Computer Science Department |
      |   jimj@csd4.csd.uwm.edu           jimj@miller.cs.uwm.edu    |
Newsgroups: comp.unix.bsd
From: rv@cs.brown.edu (rodrigo vanegas)
Subject: Re: AT&T sues BSDI
Organization: Dept. of Computer Science, Brown University
	<1821@adagio.UUCP> <1992Jul24.064922.8448@newshost.anu.edu.au>
	<1992Jul24.111727.373@cine88.cineca.it>
Date: Fri, 24 Jul 1992 13:32:24 GMT

In article <1992Jul24.111727.373@cine88.cineca.it>, campo@sunthpi3.difi.unipi.it (Massimo Campostrini) writes:

> Should we rename this newsgroup
> comp.unix(*).bsd.(*)UNIX.is.a.trade.mark.of.AT&T ?

seriously though... how about comp.os.bsd?

rodrigo_vanegas@brown.edu
From: brians@eecs.cs.pdx.edu (Brian Smith)
Newsgroups: comp.unix.bsd
Subject: Re: SCSI tape drive not accessible
Date: 28 Jul 92 14:48:13 GMT
Distribution: comp
Organization: Portland State University, Portland, OR

In article <1992Jul23.080507.29145@news.uni-stuttgart.de> zrgl0376@helpdesk.rus.uni-stuttgart.de (Cowboy aka Bjoern Lemke) writes:
>In article <TMH.92Jul23041936@keks.first.gmd.de> tmh@keks.first.gmd.de (Thomas Hoberg) writes:
>>I managed to get the "Tiny BSD" floppy accross the modem and got
>>386BSD installed on my system (486/33, 16MB, ET4000/8514, AHA1542, 1GB
>>Wren VII + 88MB Syquest SCSI drives, Tandberg TDC3800 QIC 525 SCSI
>>Streamer). The SCSI disks are at targets 0+1, the tape drive is at
>>target 4. On boot up, only the first disk is recognized. Trying to
>
>I run into a similar problem. I used a Fujitsu 2624 Harddisk with the same
>Streamer (Tandberg). Setting the tape drive to target 4, resulted in 
>nonrecognizing the streamer. (My harddisk is set to target 0). But after
>setting the tape device to target 1, the scsi controller got it and
>i was able to read and write from the device (/dev/ras1a) including some
>scsi error messages (sense 0 0 0 0 .. and so on). I am not a scsi guru
>and I don't know if this method is proper, but for the moment it works.

This is in the faq recently posted.  Apparently, the scsi driver in
386BSD only probes targets until it finds an empty spot.  So, if you had
target 0, target 1 and target 4, then the driver would find target 0, then
target 1, then look for target 2 (finding it empty/non-responsive), and
conclude that no more devices were on the scsi bus.  The workaround is to
make your scsi devices all contiguous and starting at 0.

Brian


/---------------------------------------|------------------------------------\
| #include <std/disclaim.h>             | Inet: brians@cs.pdx.edu            |
| #include <human/erors.h>              | UUCP: tektronix!pdxgate!brians     |
|---------------------------------------|------------------------------------|
| Behold the warranty.. the bold print giveth and the fine print taketh away.|
\----------------------------------------------------------------------------/
Newsgroups: comp.unix.bsd
From: bhv@areaplg2.corp.mot.com (Bronis Vidugiris)
Subject: Re: Best Reaction to AT&T Suit == Join LPF
Organization: Motorola, CCR&D, CORP, Schaumburg, IL
Date: Wed, 29 Jul 1992 00:06:03 GMT

In article <1992Jul24.013957.10852@algor2.algorists.com> jeffrey@algor2.algorists.com (Jeffrey Kegler) writes:

)1) AT&T's hints of wide ranging legal action are so far just that --
)strong hints.  Perhaps our response should be proportional.

Ha!  If AT&T immediately & publically dropped its suit against BSDI, that
would be a good start.  Then we could start asking some questions about
their exact involvement in operation Sundevil (related to the Steve Jackson
Games case).
From: kaneko@ICSI.Berkeley.EDU (Seiji Kaneko)
Newsgroups: comp.unix.bsd
Subject: [386bsd]Re: Which SCSI Controllers
Date: 22 Jul 1992 21:06:32 GMT
Organization: international computer science institute
NNTP-Posting-Host: axiom.icsi.berkeley.edu

In article <13281@ns-mx.uiowa.edu> williams@herky.cs.uiowa.edu (Kent Williams) writes:
>If I wanted to buy a SCSI controller to use with 386BSD, which ones work???

Besides officially supported board, BusTek BT-742A(EISA) is 
working fine on my machine. But I use it to access my second 
drive(swap and user file), so I have not tested it as root 
partition drive controller.
-- 
Seiji Kaneko  kaneko@icsi.Berkeley.EDU,kaneko@sdl.hitachi.co.jp
.................................... 76270.2466@compuserve.com
Newsgroups: comp.unix.bsd
From: vixie@pa.dec.com (Paul A Vixie)
Subject: 386BSD tapes (was Re: address needed)
Organization: DEC Network Software Lab
Date: 25 Jul 92 12:23:50

>i am looking for Paul Vixie USMAIL address to send him a tape, could you help?

It's in the FAQ.  But for the record, tapes with stamped/addressed return 
mailers can be sent to 386BSD, c/o Paul Vixie, 3477 South Court, Palo Alto,
CA, 94306, U.S.A.  Tapes arriving without stamped/addressed return mailers
are mine to keep with no notice to you.  No, I will not reuse the container
you ship me the tape in.  Any kind of tape is OK, except DECtape-I since I've
just disconnected that and shipped it back to oblivion from whence it came.

I'm going to start making tapes now.  Folks have been waiting several months
for these and I don't want to delay it further until the first patch comes
out -- presumably people will be able to get the first patch via ftpmail if
noone posts it here.
--
Paul Vixie, DEC Network Systems Lab	
Palo Alto, California, USA         	"Don't be a rebel, or a conformist;
<vixie@pa.dec.com> decwrl!vixie		they're the same thing, anyway.  Find
<paul@vix.com>     vixie!paul		your own path, and stay on it."  -me
Newsgroups: comp.unix.bsd
From: gclarkii@NeoSoft.com (Gary Clark II)
Subject: Kernel & others
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Fri, 31 Jul 1992 05:39:44 GMT
Followup-To: comp.unix.bsd 
Summary: problems and success 

Hello,
I've been running 386BSD here for about a week.  Here is the system I'm running it on (Note: this system has ran everything I've given it)..       
                
                 386SX-16 (Beaver Tech out of CA)
                 6 megs (70ns)
                 Oak VGA 512K
                 Clone IDE & floppy controller
                 WD Caviaur(sic) 80MB HD
                 1.2 & 1.44 FD
                 Clone Multi-IO card
Dos has 16 Megs and BSD has 65.  No problems with the install but later the com
port kept reporting silo overflows so I got one of the patches for the com problems and just patched the kernel.  

Now for my question...
Has anyone written anything like a guide to whats what in the kernel?  What
I mean is if I want to find out where to go modify the file system where would
I look?  (Yes I know, I go file by file and look but....)

BTW: to my last question (Emacs type editor), Jove works fine when compiled as
for a 4.3BSD system, You just have to define stty and gtty (Someone posted it
a couple of days ago but I don't remember the name... thanks for the help)

Gary Clark II (N5VMF)             Just another out work BSD hacker.....
gclarkii@tghost.gbdata.com        Yeah right..... 
gclarkii@neosoft.com

Newsgroups: comp.unix.bsd
From: wutcd@hrz.tu-chemnitz.de (Joerg Wunsch)
Subject: Re: 386BSD 0.1 lpt.c - anyone got it to work?
Organization: tu-chemnitz
Date: Fri, 31 Jul 1992 16:35:24 GMT

T.D.G.Sandford@bradford.ac.uk (TDG SANDFORD) writes:

>Another point: what is the method used to create the diff-like patches
>that are posted to this group - and what is the way to apply them to the
>files automatically, rather than typing them in by hand :-( ?
Quiet simple: a tool named patch understand all kind of diff output
(simple diff, diff -e, or [you mean] diff -c, the context diff).

>Has anyone managed to get the lpt.c (parallel printer driver) supplied
>in the 0.1 kernel sources to work? I've managed to get it to compile :-)
>but it won't even find my lpt1: port at 0x378.
So, there's a problem. Since i had holidays, i'm not up-to-date, and still
running 0.0. Thus i don't know which lpt driver they included. But i posted
one some weeks ago (which is okay on my 0.0), and since my name is included
in the contributors' list, i guess, it could be my lpt driver.

So try to be more detailed, and e-mail your report to me. I'll see what
to do. Furthermore, i hope to upgrade to 0.1 as soon as possible. Please,
refer only to the address in the signature (it's different from the sender
address of this posting since i'm modem-logged-in here only).

			enjoy, 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