HDTenEightyP/NetNews huggingface dataset:
From: zxmsd01@mailserv.zdv.uni-tuebingen.de (Gunther Schadow)
Subject: 386BSD: TeX01 distribution on the way to agate!
Keywords: TeX 386BSD
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Fri, 31 Jul 1992 15:49:20 GMT

Hi all,

as I promised last week, though with delay, I am about to upload my
TeX01 distribution onto agate.berkeley.edu.
I could incorporate a set of dvi-drivers too, so you can do real work
with TeX quite easyly. All you have to do is to compile the fonts for
your appropriate printing device.

Enjoy
-Gunther

--
-------------------------------------------------------------------------------
Gunther Schadow,	          e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE
Sudetenstrasse 25,	          Phone:  (49) 7071/37527
7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA
Newsgroups: comp.unix.bsd
From: derry@beaufort.sfu.ca (Andrew Derry)
Subject: Re: Removing 386BSD from the hard disk
Keywords: 386BSD
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Thu, 23 Jul 1992 20:31:31 GMT

kwan@netcom.com (Kwan-Seng Low) writes:

>low level format your hard disk.

nono.. don't do that..  just use

fdisk /mbr

that should fix your boot sector.

Cheers
---
Andrew
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: Re: SCSI tape drive not accessible
Date: 23 Jul 92 15:20:26 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu


In article <TMH.92Jul23041936@keks.first.gmd.de> tmh@keks.first.gmd.de (Thomas Hoberg) writes:
> ... Any attempt to
>read /dev/ras4a results in an error. cat </dev/ras4a returns "bad file
>descriptor"....


Thos Sumner reported that the major device number for target four (files
/dev/ras4a and /dev/ras4d) were set to the WRONG number (11, not 13).
This stands out like a sore thumb if you do an "ls -l /dev/ras*".


Bill.
Newsgroups: comp.unix.bsd
From: msk@mudhoney.micro.umn.edu (Mark S. Kassem)
Subject: 3 1/2" Boot Disks
Summary: Booting with 3.5"
Keywords: 3.5"
Organization: University of Minnesota, Minneapolis: Under Grad Workstation Lab.
Date: Mon, 27 Jul 1992 13:35:01 GMT

	Howdy all

	My question has probably been asked here before, and I must have missed
	it.  But here goes nothing (flame at will)...

	How do I get a 3.5" Boot disk for 386BSD 0.1??  I have only seen the
	5.25" 1.2Mb boot disks on the ftp ditribution sites.  Can someone
	please point me in the right direction?  Or may be please send me
	further instructions on how to boot with the currently available
	1.2Mb boot disks.  I would like to boot 386BSD on an IBM PS/2 L40SX
	20MHz and 6 Megs Ram and 62Meg Drive.  This laptop is an AT bus and
	should be able to host 386BSD easily.
	
	Thank You much for your help.


	P.S.  Thanx to all that have made 386BSD possible
-- 
Standard Disclaimer Follows...

#########       U of M ACM President        msk@epx.cis.umn.edu
    #                                       Mark S. Kassem
  #####         CIS Network Composer        113-A Shepherd Labs
 #  #                                       Minneapolis, MN 
  #####       				   (612) 625-9836                
    #  #  "How Will I laugh Tomorrow, If I can't even smile Today!"  
  #####   						ST-FLSDJV
From: rcd@raven.eklektix.com (Dick Dunn)
Newsgroups: comp.unix.bsd
Subject: AT&T or USL, and extrapolation
Date: 23 Jul 92 06:40:28 GMT
Organization: eklektix - Boulder, Colorado

The discussion about the BSDI lawsuit seems to be focusing on AT&T.  These
days, it's really USL which is responsible for the development (such as it
is) and the licensing of UNIX systems.  Now, my understanding is that USL
isn't exactly a piece of AT&T but isn't exactly separate either.  Can any-
one explain the real nature of this neither-fishy-nor-foul relationship? 
It bears on things such as whether it means anything at all to protest by
changing your long-distance service.  Could any information actually
trickle down/across to USL?  (I doubt that it has much effect in the best
case, but I'm wondering if it has any at all.)
_ _ _ _ _

Next...There's been a lot of extrapolation from what is known about the
lawsuit to what it might mean.  People are off guessing how AT&T must think
that nobody who's seen the inside of UNIX can do OS work without revealing
trade secret and nobody's going to be able to work in the field any more...
Let's hold on.  The best we can say is that, to the typical reader among
us, the suit simply Doesn't Make Sense.  We don't know what it is that USL
claims as violations--in fact, the defendants don't even know what the
alleged violations are.  It's one thing to be wary--and I think we'd all
better watch this one carefully--but it's another thing to extrapolate from
lack of facts or lack of substantive accusations to doomsday scenarios.
There just isn't any justification for them (yet), and it would help us
understand the facts if we didn't have to keep filtering out the uninformed
guesses.
-- 
Dick Dunn    rcd@raven.eklektix.com   -or-   raven!rcd    Boulder, Colorado
  ...The way to meet an impossible circumstance is with voluntary craziness.
From: danson@lgc.com (Doug Anson)
Newsgroups: comp.unix.bsd
Subject: Re: Is AT&T listening?...
Date: 22 Jul 92 16:57:06 GMT
Organization: LandMark Graphics Corporation LGC

In article <1992Jul23.200547.22246@cs.rose-hulman.edu>, mgrjtb@nextwork.rose-hulman.edu writes:
|> 
|> 
|> AT&T, are you listening?

No, AT&T's phone is out of order....

(I just couldnt pass this one up)
Have a great day.
Doug
-- 
-------------------------------------------
Doug Anson					
Internet: danson@lgc.com			
Phone:	  713-579-4739
SNAIL:    Landmark Graphics Corporation LGC	
	  333 Cypress Run			
	  Houston, TX 77094			
-------------------------------------------
From: Sean.Levy@cs.cmu.edu
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 31 Jul 92 05:33:11 GMT
Article-I.D.: cs.EeSI4LW00hMgJ7SGhT
	<1992Jul30.174414.28488@kas.helios.mn.org>
Organization: Carnegie Mellon, Pittsburgh, PA

Excerpts from netnews.comp.unix.bsd: 30-Jul-92 Re: AT&T vs. BSDI -->
4.3BS.. Rob Healey@kas.helios.mn (1256)

> Even micro kernels
> 	like MACH and probably NT borrow QUITE a bit from the UNIX(tm) system
> 	in system call names and symantics

At least in the case of MACH, nope. The services and abstractions that
the Mach microkernel is interested in supplying can be easily mapped
into the concepts present in Unix(tm)*, but (and I'm not speaking as a
Mach guru or anything, my site name not withstanding -- I'm just a happy
user) they themselves are totally orthogonal. Mach talks about ports,
access rights, tasks, threads and virtual memory; communication with the
kernel is done through these ports by dint of these rights by threads in
tasks sitting in regions of VM. I believe that talking to the kernel
looks like any other IPC, which is not the case in Unix(tm). Now, the
BSD emulation sitting on top of the Mach on the box I'm on now sure
looks a whole hell of a lot like BSD (well, it *is* BSD), but what's
underneath doesn't.

I have no idea about NT, other than I've hated Microsoft from the first
day I used their brain-damaged BASIC on a PC and have had no reason to
change my mind since.

----
*Or DOS, or whatever. There was a talk given around here recently on a
DOS emulation built on top of Mach, which I, regretably, missed... The
point is, if you're talking about interfaces (system calls), that's one
thing. If you're talking about concepts (semantics) like files as
unstructured streams of bytes, file descriptors (I seem to recall the
term "resource descriptors" being used in some of the 4.2BSD tech
papers, which is a better term) being able to have all sorts of things
on the "other side", UID, etc... then, I don't see how AT&T/USL can
claim anything, as almost all of the key concepts were leveraged from
earlier efforts, as has been pointed out. As I understand it, they're
bellyaching about actual lines of code of theirs having made their way
into someone else's product -- as I understand it, there isn't anything
else they CAN legally bellyache about, no?
----

Cheers,
			-- Sean
--
Sean Levy, n-dim Group, EDRC, CMU, 5000 Forbes Ave, PGH, PA 15213
Email: snl+@cmu.edu, Phone: +1 412 268 5221, Fax: +1 412 268 5229
Newsgroups: comp.unix.bsd
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Subject: Re: 386BSD: Anyone using gcc-2.x on 0.1?
Date: Wed, 29 Jul 1992 17:31:10 GMT
Organization: SAS Institute Inc.

I'm not sure that v 2.2.x is a pre-requisite for shared libraries; I
ran for a long time w/ 1.38 & 1.39 on ISC unix and was able to build
shared libraries fine.  You may want to look there and see how they
did it...  (The original X11R4 done by Thomas Roell was a shared library
built with gcc 1.38).

     - Dave Rivers -
    (rivers@ponds.uucp)
-- 
UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express
Newsgroups: comp.unix.bsd
From: danson@lgc.com (Doug Anson)
Subject: Removing 386BSD from the hard disk
Keywords: 386BSD
Organization: LandMark Graphics Corporation LGC
Date: Tue, 21 Jul 1992 15:22:25 GMT

Hello 386BSD'ers:

After many hours rebuilding kernels, etc.. the time came for me to uninstall
386BSD so that I can continue with my work (arg!!).  Anyway, I just tried
reinstalling DOS. I was able to produce a DOS partition (386BSD occupied my
entire disk), format it and install the dos system onto it. When I then tried
to reboot the machine off of the hdisk (thus DOS), my system can no longer
boot off of the hdisk! It simply resets again and again after trying....

Could it be that the some part of the 386BSD boot strap on the hdisk is still
there? When I fdisked the hdisk in DOS everthing seemed to work fine.

Any help, comments would be appreciated.

Doug

-- 
-------------------------------------------
Doug Anson					
Internet: danson@lgc.com			
Phone:	  713-579-4739
SNAIL:    Landmark Graphics Corporation LGC	
	  333 Cypress Run			
	  Houston, TX 77094			
-------------------------------------------
Newsgroups: comp.unix.bsd
From: leisner@trianguli (Marty Leisner 311/? x?)
Subject: Checksum for bootable system?
Reply-To: leisner.henr801c@xerox.com
Organization: Xerox
X-Newsreader: Tin 1.1 PL4
Date: Tue, 21 Jul 1992 21:11:21 GMT

I snarfed the system (and lots of other stuff)

I formated a 1.2 meg floppy in my sparcstation, did:

zcat dist.fs.Z >/dev/rfd0a

and on a few Compaq 486 machines, it tries to boot (doesn't say anything) and goes back in an infinitely
loop for a RAM count...

I tried it again (fdformat, cat dist.fs >/dev/rfd0a

When I ran beav, there was something on the disk  (the first few bytes say `4386BSD'.

I ran:
cmp dist.fs /dev/rfd0a

and got this after a while...
cmp: I/O error on /dev/rfd0a: Invalid argument

Hints?


--
marty
leisner.henr801c@xerox.com  
Member of the League for Programming Freedom
Newsgroups: comp.unix.bsd
From: bzs@ussr.std.com (Barry Shein)
Subject: Re: USL vs. BSDI, and what to do
Organization: The World
	<l6vrqvINN91g@neuro.usc.edu> <l6vt9sINN93u@neuro.usc.edu>
	<1992Jul24.170447.11039@Warren.MENTORG.COM>
Date: Sat, 25 Jul 1992 22:45:53 GMT


From: tal@Warren.MENTORG.COM (Tom Limoncelli)
>I hate to say this, but Bob has nothing to do with this.  AT&T didn't
>bring the law suit.  USL did.  USL has a different chair person, and
>has their own lawyers (from what I've heard, they don't share lawyers...
>so much for the "army of lawyers").

AT&T is a major shareholder in USL.

Consider the action analogous to putting pressure on advertisers who
sponsor some offensive TV show or whatever. In this case it's even
more significant as USL is closely-held (i.e. not openly traded on the
stock market.)

AT&T has a big vote on whether or not USL pursues the lawsuit. So do
other large USL shareholders (who are they?)

--
        -Barry Shein

Software Tool & Die    | bzs@world.std.com          | uunet!world!bzs
Purveyors to the Trade | Voice: 617-739-0202        | Login: 617-739-WRLD
Newsgroups: comp.unix.bsd
From: "Andrew A. Chernov, canton Uri's citizen" <ache@astral.msk.su>
Subject: BSDI & DOS on same disk, HOW?
Keywords: BSDI DOS
Organization: Kurchatov Institute of Atomic Energy, Moscow
Date: 30 Jul 92 15:08:08 GMT

How I can  choose BSDI/DOS at boot time and integrate DOS partition
into BSDI scheme?
Please tell me if any solutions exists.
			       Thanx in advance.
-- 
In-This-Life:  Andrew A. Chernov    |  "Hay mas dicha, mas contento
Internet:      ache@astral.msk.su   |  "Que adorar una hermosura
Organizations: The RELCOM, Demos/+, |  "Brujuleada entre los lejos
               Moscow, Russia       |  "De lo imposible?!"  (Calderon)
From: cflatter@nrao.edu (Chris Flatters)
Newsgroups: comp.unix.bsd
Subject: Re: Jolitz 386BSD-0.1 -- floating point perform
Date: 22 Jul 92 15:28:54 GMT
Reply-To: cflatter@nrao.edu
Organization: NRAO

In article l6qc51INN1gu@neuro.usc.edu, merlin@neuro.usc.edu (merlin) writes:
>I have most of the US Army BRLCAD three dimensional CSG modeling and
>distributed ray tracing system ported to the Jolitz 386BSD-0.1.  But,
>I am getting only about one fifth of the floating point performance
>previously measured using AT&T pcc and GNU gcc 1.4x on ATT UNIX SYSV.
>
>Does the compiler default to '387 emulation?  Is there some flag which
>needs to be set to actually use the coprocessor?  Or are there reasons
>386BSD-0.1 would exhibit relatively poor floating point performance?

The problem is that there is a mismatch between gcc 1.4 and Intel coprocessors.
gcc expects floating-point registers while the 80x87s have a stack.  This
leads to a fairly large performance hit.  gcc 2.x can produce optimised code
for the 80x87.  Is anyone working on porting gcc 2.x to 386BSD? Come to
think of it, is there anything that needs to be done to do this (wouldn't
the BSD/386 configuration work)?

NB: the coprocessor shows up as device psx0 during the bootstrap sequence.  If
this doesn't show up 386BSD thinks you don't have a coprocessor.

	Chris Flatters
	cflatter@nrao.edu
From: donaldh@cs.hw.ac.uk (Donald I. Hunter)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1 kernel sources ?
Keywords: 386BSD KERNEL SOURCES
Date: 29 Jul 92 17:04:44 GMT
Organization: Dept of Computer Science, Heriot-Watt University, Scotland

To get the 386BSD kernel sources do I have to download the entire source distribution ?  I don't have the space (nor will I ever have) to take the whole distribution so I was wondering if someone would be kind enough to provide just the Kernel sources for anonymous FTP.

Cheers, Donald.
-- 

 +--------------------------------------------------------+
 | Donald I. Hunter                   donaldh@uk.ac.hw.cs |
 +--------------------------------------------------------+
 | Hello. Just walk along and try NOT to think about your |
 |    INTESTINES being almost FORTY YARDS LONG!!          |
 +--------------------------------------------------------+
Newsgroups: comp.unix.bsd
From: rminnich@super.org (Ronald G Minnich)
Subject: questions on 386BSd on compaq deskpro 386/25 (ca. 1988 machine)
Organization: Supercomputing Research Center (Bowie, MD)
Date: Tue, 21 Jul 1992 16:07:14 GMT

dist.fs won't boot. if i put my working 0.0 kernel on the dist.fs 
disk, in place of the 0.1 386bsd on dist.fs, 
it still won't boot. In either case, crashes all the way back to the 
power-on memory test. 

the 0.0 dist.fs boots just fine. 

anybody seen this one?

also, how do you tell install that yes, you want to wipe out the installed 
3896BSD? it seems it won't take yes for an answer.

thanks,
ron
-- 
--------------------------------------------------------------------------------
satisfaction: the feeling you get when you        | rminnich@super.org
run newfs on a DOS disk so you can install 386BSD.| (301)-805-7451
Now if only I could do this to AIX on the RS/6k ...|
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: taunted by happy extract command
Date: 22 Jul 1992 08:22:12 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <14g475INNknj@agate.berkeley.edu>, wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
> This is due to the fact that the buffer cache is allocated out of kmem_map,
> and is undersized for systems above 12MB (you lucky devil, I've only 8MB!).

Hmm.
You mean, "12MB and more", right ? I got that sort of problem while extracting
the srcdist.

BTW the system tends to re-boot for no appearant reason sometimes, and without
any messages about panics and the like.

Ahem. I'll send out the registration and a thank-you-note as soon as I've got
the mail and uucp system configured :)

Bernard
Newsgroups: comp.unix.bsd,misc.jobs.misc
From: fran@Cadence.COM (Fran Peterson)
Subject: Re: AT&T sues BSDI
Organization: Cadence Design Systems, Inc.
Distribution: usa 
Date: Wed, 29 Jul 1992 16:37:04 GMT

In article <s6j1Hp4!q8@atlantis.psu.edu> hvozda@wilbur.psu.edu (Eric Hvozda) writes:
>
>This whole mess reminds me of an article I read about two companies in
>Eastern PA.  Company X had setup shop in a small town.  The plant was the
>town's livelyhood.  Company X decided to pull out.  A new company, company Y,
>who is a competitor of X, decided to purchase the old plant.  They offer jobs
>to most of X's employees that X had layed-off.
>


I did not read the original posting, but from reading the reply above,
I remembered an article I read in the newspaper several years ago.  It
involved a baker.  Not just any baker.  But the head baker for a very
large English muffin bakery.  In fact, as I recall the two companies
were Thomas and Orwheat.  

I don't remember which one the baker worked for, but he gave notice
we'll say to bakery A to go to work at bakery B.  Bakery A said you
can't do that.  Trade secrets and all that.  They sued bakery B and
the baker.  They went to court.  Judge said the case was the first
of it's kind and would have to have research done.  And in the meantime
while the research work was being done, bakery A was to continue to
pay the baker his salary until the case was settled.  The baker could
not go to work for bakery B until the case was settled.  

It took one year before the case was settled as follows:

	Baker was allowed to go to work at bakery B

	Bakery A paid the baker to stay home for one year at his 
	current salary.

	Bakery A had to pay the difference between their salary
	and the one bakery B was going to pay him.

Bottom line was that a man cannot be kept from gainful employment if
that's his only livelyhood.  

Also I had a contract that prohibited me from working for a competitor
within a 50 mile radius.  But I got out of it.

In these times of such large employment numbers I think the person would
have a good case.

Who ever they are I wish them luck.  While it's the big guys that fight
in court.  It's us little guys that get the shaft.

Disclaimer:  The above is totally my own recall of several years past,
		with a memory that's even even farther past!

Fran Peterson

F [:)
From: james@raid.dell.com (James Van Artsdalen)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1 scsi tape problem
Date: 28 Jul 92 03:30:36 GMT
Reply-To: james@raid.dell.com (James Van Artsdalen)
Organization: Dell Computer Co

I am running 386BSD 0.1 on a Dell 433P with 16 MB of DRAM, using an
Adaptec 1542B with a 660 MB Micropolis SCSI disk and an HP 2 GB SCSI
DAT tape drive.  I am having trouble writing to the tape drive.

The major/minor numbers I'm using are 13/32.  Here's the contents of
/var/log/messages after "tar cvf /dev/ras4a /usr/local/src":

   pc0<color> at 0x60 irq 1 on isa
   com1 at 0x3f8 irq 4 on isa
   com2 at 0x2f8 irq 3 on isa
   fd0 drives 0: 1.2M at 0x3f0 irq 6 drq 2 on isa
   as0 at 0x330 irq 11 drq 5 on isa
   we0 starlan address 00:00:c0:6e:66:23 at 0x300 irq 9 on isa
   npx0 at 0xf0 irq 13 on isa
   changing root device to as0a
   as0: attached tgt 0 <MICROP 1588-15MB1036511 AS0C> winchester disk 
   as0: attached tgt 4 <HP HP35480A A> tape 
   as4a: controller error 0x12 writing fsbn 0-19
   scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
   as4a: controller error 0x12 writing fsbn 20-39
   scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 

... more controller errors and scsi sense lines...

Any guesses as to what's wrong?
-- 
-- 
James R. Van Artsdalen          james@bigtex.cactus.org   "Live Free or Die"
Dell Computer Co    9505 Arboretum Blvd Austin TX 78759         512-338-8789
From: dec@lazarus.nrtc.northrop.com (Dwight E. Cass)
Newsgroups: comp.unix.bsd
Subject: Mtools binaries are bad?
Date: 27 Jul 92 17:44:18 GMT
Organization: Northrop Research & Technology Center, Palos Verdes, CA

With the exception of the mread utility, I have been unable to get the
mtools binaries to work, as distributed in the /usr/local/bin
directory after installing the system.  However, the binaries in
/usr/othersrc/public/mtools-2.0.5/bin work just fine.  Is this a 
problem with the distribution?

/dec
Dwight E. Cass                 dec@nrtc.northrop.com | You are in a
Automation Sciences Laboratory, Northrop Corporation |   twisty maze of
One Research Park, Palos Verdes Peninsula, CA  90274 | Sendmail rules,
(310) 544-5393                                       |   all obscure...
Newsgroups: comp.unix.bsd
From: juengst@boss1.physik.uni-bonn.de (Henry G. Juengst)
Subject: Q: QIC-02, mountain tape 150 Mbyte
Keywords: QIC-02, mountain tape, file safe
Organization: Universit"at Bonn, Informatikinstitut, R"omerstr 154, W-5300 Bonn 1
Date: Mon, 27 Jul 1992 08:27:53 GMT

Hello,

  I've got a problem with a Mountain tape - I think it's a file safe 7160
(it's not here, but sure it's a 150 Mbyte tape) - with a QIC-02 interface.
The interface card look like

     *
     *  DMA
     *

     *       *
     *       * DMA
     *       *
     * IRQ
     *                     sorry, I've forgotten to notice its name

     *
     * I/O address
     *
     *
     *

############################## ISA bus

I use I/O address 300H, IRQ 5 and DMA channel 1 as described in INSTALL.NOTES,
but autoconf doesn't find wt0 and of course /dev/rwt0 says device not
configered. It does work under msdos. No other device was found with any of
these hardware parameters.

Can anybody help ? Thanks in advance.

Henry
Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Pax (was Re: Sorry, everyone, but I'm cpio clueless...)
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Tue, 21 Jul 1992 20:08:27 GMT

Pax, a public domain program, can read tar and cpio archives all the way back
to version 7 tar, and can write IEEE Std 103.1 tar and cpio archives, both
of which are, in fact, byte-sex independent, plus cpio can archive /dev and
friends.

It has tar and cpio command line interfaces, as well as a pax command line,
which has more control and can read and write tar and cpio archives from
the same command-line interface.

It was funded by Usenix, and can be found about anywhere on the net.
It's also /usr/5bin/pax on your Sun, /usr/bin/pax under SCO.

It was supposed to bring peace to the tar and cpio camps, but that would cut
down too much on the flaming. :)

Cheers,
-- 
-- Email info@NeoSoft.com for info on getting Internet access.
"Silent gratitude isn't very much use to anyone." -- G. B. Stearn
Newsgroups: comp.unix.bsd
Subject: Re: Precedent... Whitesmiths Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!