HDTenEightyP/NetNews huggingface dataset:
From: terry@uivlsisd.csl.uiuc.edu (Terry Lee)
Newsgroups: comp.unix.bsd
Subject: Bad144 sector mapping tips
Date: 24 Jul 1992 21:41:09 GMT
Organization: Coordinated Science Lab., Univ. of Illinois at Urbana-Champaign
NNTP-Posting-Host: uivlsisd.csl.uiuc.edu
Keywords: bad144

	Thanks Bill and Lynne for making 386BSD possible!  For anyone who is
trying to get bad144 bad sector mapping to work for MFM/RLL/ESDI drives, here's
some tips and anomalies (?) I've discovered:

1.  The install program might not put the 'sf' flag (enable bad144 handling) in
    the disklabel.  The output of 'disklabel -r wd0' should have a line that
    says "flags: badsect".  If 'badsect' is not there, use 'disklabel -e wd0'
    to put it there.

2.  According to INSTALL.NOTES, when a bad sector is accessed, an error message
    should indicate the bad sector number.  So far, I've only gotten an error
    message (and not in the form given in INSTALL.NOTES) when the bad sector
    is in the swap partition.  And the sector number reported is relative to
    the start of the 386BSD partition (bad144 expects sector numbers relative
    to cylinder 0).

3.  Be sure to use 'bad144 wd0 0' to first clear the bad sector list.

4.  To find bad sectors in the 386BSD partition, use
    'dd if=/dev/wd0c of=/dev/null bs=512'.  If error 5 is reported, then a bad
    sector is found.  For example, let's assume the offset of wd0c is 200000.
    If 'dd if=/dev/wd0c of=/dev/null bs=512' reports

    error 5 ...
    13500+0 records in
    13500+0 records out

    then sector #213500 (relative to cylinder 0) is bad.  However, the last
    part of /dev/wd0c (one cylinder + 126 sectors) is reserved for bad sector
    mapping; don't try to map any bad sectors found in this area!

5.  According to INSTALL.NOTES, 'bad144 -a wd0 213500' (for our example) should
    have done the trick.  But on my system, 'bad144 -a -c wd0 213500' is
    needed.  Is this a bug?

6.  Repeat steps 4 and 5 until all bad sectors (except those in the last
    cylinder + 126 sectors) are mapped out (I know, yech!).  This is not very
    elegant, but it works.  I'll try to write a program sometimes to do this
    better.  Is someone already working on this?

	I hope this helps someone.  Of course, standard disclaimers apply!

----------
Terry Lee
terry@uivlsi.csl.uiuc.edu
Newsgroups: comp.unix.bsd
From: kris@tpki.toppoint.de (Kristian Koehntopp)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
X-Copyright: (C) Copyright 1992 Kristian Koehntopp -- All rights reserved.
		 Reproduktion, auch auszugsweise, ausserhalb elektronischer,
		 nichtkommerzieller Datennetze nur mit ausdruecklichem,
		 schriftlichem Einverstaendnis des Autors.
Organization: Toppoint Mailbox e.V.
Date: Tue, 28 Jul 1992 09:37:57 GMT
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD]
X-Excuse: X-Copyright wegen Emma, Suedwestpresse und /C'T/DISKUSSIONEN.

In <l6rld6INN3dh@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>This isn't just AT&T vs. BSDI -- it's AT&T vs. the academic community which 
>produced most of the intellectual property which makes the 'AT&T UNIX' and 
>'Berkeley UNIX' compatible operating systems so valuable today -- virtual
>memory management, interprocess communication, networking, fast filesystems,
>efficient compilers -- and all of the other things which weren't contained
>in the Bell Research 32V system turned over to UC Regents so many years ago.

So then:

Can anyone who has developed such valuable concepts sue AT&T
for using them and integrating them into their product on the
very same grounds?

Kristian
-- 
Kristian Koehntopp, Harmsstrasse 98, FRG W-2300 Kiel, +49 431 676689
"AT&T --- anything better is illegal."
	-- Keith Lofstrom, comp.unix.bsd, "AT&T sues BSDI" thread
Newsgroups: comp.unix.bsd,comp.os.linux,comp.periphs.scsi
From: neese@adaptx1.UUCP (Roy Neese)
Subject: Re: Query: Drivers for AHA >1522< ?
Organization: Adaptec Inc., Texas
Date: Wed, 29 Jul 1992 20:48:34 GMT

In article <1992Jul23.232138.20172@colorado.edu> drew@ophelia.cs.colorado.edu (Drew Eckhardt) writes:
> In article <14hjqoINNr78@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
> >In article <adam.711725819@mcrware> adam@microware.com (Adam Goldberg) writes:
> >>...The 1542 is a bus-mastering controller.  This 1522 is not.  That makes
> >>the 1542 much faster (at least in a protected-mode OS like Linux, with
> >>properly written drivers).  
> >
> >One of the reasons that 386BSD works so well with the 1542B is the
> >bus-mastering, the advantages of which are lost on DOS. There may
> >be a false economy in getting a 1522, because the entire advantage
> >of going to SCSI is the bandwidth improvement over the programmed I/O
> >AT/IDE controllers. 
> 
> If you're talking about sustained transfer rate, it's going to be 
> faster to do polled I/O because you don't have the couple of clock
> cycles associated with each bus on period - you just crank data 
> across the AT bus topspeed, 16 bits at a time.

Nope.  Polled I/O can never be faster than bus master DMA as it takes
twicw as many cycles to move each word doing polled I/O as it does for a
bus master to move the same word.
The overhead you speak of is for acquiring the bus, wchi takes 2 cycles
and then of course it takes another 2 cylces to release the bus.  But to
show a more subjective view.  Let's make some assumptions, good
assumptions.  Let's say 1 cycle per word for bus master DMA and 2 cycles
per word for polled I/O (you have to do a read and write for polled I/O,
whereas bus masters do either a read or a write).  Now let's move 512
bytes of data.  Let's see,... for polled that would be 1024 cycles and
for a bus master 512 + 2 + 2 = 516.  Nuff' said.
 
> However, if you can DMA to memory, and replace multiple interrupts with 
> a single interrupt, you'll come out ahead in terms of speed because 
> you're looking at ~200 clocks overhead for an interrupt on the i386
> in protected mode.

True.
 
> SCSI-I also allows you to have one outstanding command per LUN 
> (you can have one disk seeking, or transfering to local buffer 
> while yoou're transfering data to another disk), which IDE and 
> "traditional" disk controllers do not.

Nope.  SCSI has never forced command queueuing as mandatory.  SCSI-2
makes it optional as well.  Host adapters can do command queueing, but
it doesn't have a thing to do with the SCSI spec.
---

			Roy Neese
			Adaptec Senior UNIX/SCSI Software Engineer
			UUCP:	convex!egsner!adaptex!neese
			Inet:	neese%adaptex@cirr.com
Newsgroups: comp.unix.bsd
From: pjm@cshl.org (Pat Monardo)
Subject: What has AT&T to lose? Plenty!
Organization: Cold Spring Harbor Laboratory
Date: Thu, 23 Jul 92 01:20:46 GMT

The BSDI product couldn't have come at a worse time.
The UNIX War may be coming to the same end as the Cold War --
with barely a shot being fired. I've been hearing stories
that OSF won't be able to compete with the new UNIX from ATT/Sun.
So here's this huge war machine that AT&T is starting to feel
confident won't have to be used against the OSF Pact forces
and, lo and behold, here comes BSDI (Sounds of AT&T aiming and FIRE!).
On top of that, people DON'T believe Microsoft's hype about NT,
Apple is making home appliances, and DEC is hemorrhaging
(have you seen their last few 4th quarter reports, what can
we expect from 4Q92? ... VMS appears extremely vulnerable ).
So AT&T can win big and after the unification efforts of the last few
years wont allow a UNIX variant to prosper.

-- 
-- Pat Monardo		What is the cause, what the reason
-- pjm@cshl.org		for the manifestation of a smile?
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: FTP problems with Tiny BSD -- Kills SVR4 FTPD
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Thu, 30 Jul 1992 23:06:44 GMT

Tiny 386BSD installs on the 2nd partition of my (AHA1542 scsi
connected) perfectly, and runs perfectly.  The ethernet card
is detected correctly (*after* cutting the IRQ2 trace, see more about
which at the end).  I can get ftp to connect to the local host where
the rest of the stuff is stored, but the ftpd there exits immediatly
due to a SYST packet sent from 386BSD ftp.  This is almost certainly
the ftpd's fault (a SVR4.0.3.0 Interactive system).  Syslog tells me
that the ftpd doesn't understand the SYST packet...

Q1.  Is it necessary for 386BSD's ftp to send this packet? and
Q2.  Can I stop it from sending that packet in some easy way?
Q3.  Alternatively, can I stop the SVR4 ftpd from croaking?

RE: IRQ2.  The cutting of this trace must be a very common thing.  On
the card I am using (A Trident 8800 card) there is a little 2 sided
donut with a trace running through the middle near the connector for
this pin that is obviously intended to make the trace cutting easy to
do and to undo.  That this fixes ethernet problems is obvious:  The
diagnostics for the card (an 8013ebt) failed until I cut the VGA card
trace.

-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
From: brian@ucsd.edu (Brian Kantor)
Newsgroups: comp.unix.bsd
Subject: Re: Writing a driver for QIC-40, floppy controller tape drives
Keywords: QIC-40 tape
Date: 27 Jul 92 22:14:05 GMT
Organization: The Avant-Garde of the Now, Ltd.
NNTP-Posting-Host: ucsd.edu

In article <greg.712272225@hibp1.ecse.rpi.edu> greg@ecse.rpi.edu (Greg) writes:
>   Meanwhile, I wonder if anyone has any info on this type of drive. Right now,

The documents describing the QIC interfaces are available from Quarter
Inch Cartridge Standards, Inc, somewhere in the Bay Area on 805-963-3853.

QIC-40 and QIC-80 apparently describe the tape formats.  QIC-117 is the
floppy-controller-style interface.  Or so the people at Colorado Memory
Systems say.

I don't know how much they standards cost.  Our library has copies, but
they're checked out right now so I haven't seen them.
	- Brian
From: uhclem@trsvax.tandy.com
Date: 22 Jul 92 09:42 CDT
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Message-ID: <1390200001@trsvax>
Nf-ID: #R:algor2.algorists.com:3152:trsvax:1390200001:000:1086
Nf-From: trsvax.tandy.com!uhclem    Jul 22 09:42:00 1992


<>
[0]According to today's _ComputerWorld_ (July 20, 1992, page 16) AT&T's
[0]USL has sued Berkeley Software Design, Inc. in U.S. District Court in
[0]NJ.  Copyright and patent infringement are apparently *not* involved,
[0]the grounds being specified as "trademark infringement, false
[0]advertizing and unfair competition."

The story I got (from a well-placed source) was that the false
advertising claim was that BSDI purchasers don't  need an
AT&T *NIX license and AT&T feels they do.   Got that?

"So, none of our code is in your product, eh?  Well, we demand you buy a
 license anyway.  That'll be $150,000 per copy, please."


My opinion, and not that of my employer who would rather everyone go out
and buy several DOS systems with Windows (sell more RAM that way) and
throw out all those nasty *NIX systems that several people can use.

						
Frank Durda IV <uhclem@trsvax.tandy.com>    |"More Hardware!  Less Software!"
...utacfd.uta.edu!trsvax!uhclem	 	    | 
...letni!rwsys!trsvax!uhclem	            |
...decvax!microsoft!trsvax!uhclem	    | - Old Marketing Chant
From: dennis@nebulus.ampr.ab.ca (Dennis Breckenridge VE7TCP)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 29 Jul 92 07:39:59 GMT
Organization: Alchemy Mindworks, Edmonton, Alberta

joeg@gagme (joe grosch) writes:

>I urge all those on the net who have copys of either Net2, BSDI, or 386BSD
>to start making copys and distributing them as far and wide as possible.
...
Are you absolutely out of your mind? Distributing licensed sources is 
not only immoral but totally illegal. A license is a privilege NOT a 
right to deal with the sources that were supplied to you in the way
that YOU feel is appropriate. This is a waste of bandwidth even flaming you!
-- 
-------------------------------------------------------------------------------
At first sight, the idea of any rules or principles being superimposed on the
creative mind seems more likely to hinder than to help,but this is quite untrue
in practice. Disciplined thinking focus inspiration rather than blinkers it. 
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: pred@iitmax.iit.edu (Predrag S. Bundalo)
Newsgroups: comp.unix.bsd
Subject: Re: problems bringing up 386BSD 0.1
Date: 29 Jul 92 23:50:17 GMT
Organization: Illinois Institute of Technology

In article <1992Jul28.230427.2258@murdoch.acc.Virginia.EDU> wrp@cyclops.micr.Virginia.EDU (Bill Pearson) writes:
>	I am also having problems bringing up 386bsd 0.1 on a DOS disk
>that contains two DOS 5.0 partitions.  I have succeeded in bringing up
>the system when I gave it the entire disk (I was able to ftp
>bindist/bin01*; extract did not terminate after 1 hr, but the system
>behaved properly), but when I try part of the disk, install goes fine,
>but when I reboot from the hard disk, the boot messages come up, and
>then a message about copying 1 Meg of memory somewhere (it always
>disappears before I can decipher it), and the machine reboots again
>and again and again.

>Bill Pearson

I have the same exact problem except I'm using a 33-386 with 8MB memory and
a 100 MB IDE disk.

Can whoever is going to help Bill please CC me as well?  Or post.

Respectfully,

Pred
-- 
:::  Predrag S. Bundalo                  Academic Computing Center     :::
:::  Illinois Institute of Technology    Chicago, Illinois             :::
..........................................................................
:::  Internet:  pred@{iitmax, elof}.iit.edu, syspredrag@minna.iit.edu  :::
:::  BITNET  :  syspredrag@iitvax.BITNET                               :::
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: Re: Announcing 386BSD Release 0.1
Date: 30 Jul 92 03:41:16 GMT
	<10916@platypus.uofs.uofs.edu>
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu
In-reply-to: bill@prijat.cs.uofs.edu's message of 21 Jul 92 17:27:16 GMT

In article <10916@platypus.uofs.uofs.edu> bill@prijat.cs.uofs.edu (Bill Gunshannon) writes:

>In article <1992Jul20.135540.12384@uvm.edu>, wollman@trantor.emba.uvm.edu (Garrett Wollman) writes:
>|> 
>|>   3.  As far as everybody who is not employed by AT&T and its
>|> licensees is concerned, BSD *is* UNIX, whether it actually contains
>|> AT&T code or not.
>|> 
>
>I believe that AT&T has started a lawsuit against BSDI that is going to
>put an end to this idea real quick.  If it don't say AT&T, it ain't UNIX.

I'm curious how this stands up against the common usage law.  When
does UNIX come up for trademark/copyright renewal?  It's my
understanding that when a word becomes common usage to describe a
general idea and not a specific product the rights of that trademark
are lost and anyone can use it to describe their product.  I'd say
that UNIX is pretty much a common usage term used to describe a way
of doing things more than a specific product from a specific vendor.

++Brett;
Newsgroups: comp.unix.bsd
From: hsu@cs.hut.fi (Heikki Suonsivu)
Subject: Re: Bad144 sector mapping tips
Organization: Helsinki University of Technology, Finland
Date: Mon, 27 Jul 1992 02:56:02 GMT


In article <l70u7lINNbh2@roundup.crhc.uiuc.edu> terry@uivlsisd.csl.uiuc.edu (Terry Lee) writes:
   3.  Be sure to use 'bad144 wd0 0' to first clear the bad sector list.

In the boot, I get

wd0: error in bad-sector file

Any ideas?

The message comes early, before any kernel boot messages (it might be given
by the loader?).

Tried initializing the bad block table from fixdist and hard disk boot,
relabeling and other combinations.  Always the same result, and no bad
block mapping.

-
Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND,
hsu@{otax.tky.hut,cs.hut,clinet}.fi  +385-0-8031121
/G=Heikki/S=Suonsivu/O=hut/OU=cs/PRMD=Inet/ADMD=Fumail/C=FI,
mcsun!hutcs!hsu, riippu SN, Email preferable.
Newsgroups: comp.unix.bsd
From: mgrjtb@nextwork.rose-hulman.edu
Subject: Is AT&T listening?...
Organization: Rose-Hulman Institute of Technology
Date: Thu, 23 Jul 1992 20:05:47 GMT


I have seen people from apple.com very active in the Linux newsgroup, which  
would seem like treason to me, and ADM and Intel people in the comp.sys.intel  
group, but we haven't heard from AT&T here.

AT&T, are you listening?
_______________________________
Joseph T. Batt
mgrjtb@nextwork.rose-hulman.edu
_______________________________
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: 0.1 success and x11r5 status
Date: Sat, 25 Jul 92 21:49:13 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: comp.unix.bsd

Hi

First of all, thank you Bill and Lynne.
The installation went flawless. In fact it was so easy that I was 
afraid that I had overlook something. 

After allocating the entire disk to bsd the system booted the first time.
Because the standard release does not support two drives my binary
installation was somewhat different. I first loaded the distribution
into my second drive using 0.0. Attempts to load 0.1 into the first 
partition and then dos failed. I supposed with some more insight it
will be possible. So then I booted 0.0 with support for 2 drives and
copy my bin distribution to my first drive, booted 0.1 and install
the bin distribution, great!. Now I am on 0.1, rebuild the kernel
for the second drive, booted again. The system failed to mount my
second drive; it complained about a bad file format; so I re-wrote
the label making sure that I didn't specify the sf. Presto, my second
drive was mountable. I am home free...

My sorest point is the com driver with its com overflow problems. It 
took several days to download the sources and bin distribution. I think
this is  a serious problem due to the size of 0.1. Not many of us have
access to ethernet. (I know, Chris Demetrius, has com a driver which solves
this problem) 

On my efforts to port X11R5, it seems to be alive and well under 0.1. with
X386-2E 1.0! A couple of other net hackers are also hammering away
and have had success with X11R5 patch level 12. (I wish to protect them
from e-mail till they finish their work). Please don't ask me for patches
yet because I wish to make a clean distribution, rather than a set of 
of collective pieces of patches.

Many thanks to Bill, Lynne and the 386bsd community!

Cheers,
Amancio
Newsgroups: comp.unix.bsd
From: peter@close.demon.co.uk (Peter Curran)
Subject: 386BSD and UK Keyboard
Distribution: world
Organization: Close Consultants
Date: Thu, 30 Jul 1992 16:35:48 +0000

Is it possible to plug a mapping of a UK keyboard into 386bsd-0.1?

It is a bit boring trying to remember the 'strange' US layout.  
Presumably there must be a bit of code somewhere that translates
the keyboard scan codes into ascii.  Could somebody point me in the
right direction please.

Peter

-----------------------------------------------------------------------------
Peter Curran                                   Mail: peter@close.demon.co.uk
Close Consultants          'Not necessarily the ravings of a completely sane
Dorking,UK                    person - but better than most politicians....'
-----------------------------------------------------------------------------
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: multi-file driver source, how to config /sys/i386/conf/files.i386 ?
Keywords: 386bsd 0.0new, system generation, multi-file driver
Date: 26 Jul 92 15:09:40 GMT
Organization: HCS GmbH, Hamburg, Europe

hi,

when a device driver is split up into several source and header files, how
is it entered into /sys/i386/conf/files.i386 ?

assume one has files pccons1.c pccons2.c and pccons3.c .

the following entry does NOT work:

i386/isa/pccons1.c	optional pc device-driver
i386/isa/pccons2.c	optional pc device-driver
i386/isa/pccons3.c	optional pc device-driver

if i have to RTFM, please give me a hint where to search !

hellmuth
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
Newsgroups: comp.unix.bsd
From: cctony@sun1.mcsr.olemiss.edu (Tony Reynolds)
Subject: Kernel Recompilation Problems
Organization: Mississippi Center for Supercomputing Research
Distribution: na
Date: Fri, 24 Jul 1992 18:42:23 GMT


Well, I now have 0.1 running on:
486/33DX  Opti Chipset 
4MB RAM
300MB Micropolis 1558-14 Hard Disk
...etc...

and am trying to recompile the kernel.  I did a make depend with
GENERICISA as my configuration file.  I am (and have...) attempting
to compile the kernel so I can get the hang of it.  I noticed
the compilation taking an excessive amount of disk activity (math_emulate.c)
and tried to Suspend the process so I could take a look at the process
table to see what was eating my disk.

Well, even after the job was suspeneded, the disk was still going crazy!
I waited for some disk activity and hit the reset button, and brought
it back up.

Its restarted now, and the level of disk activity seems to be "normal,"
but I can't wait for it to screw up again.  Does anyone have any clue
as to why this is happening to me?

On the bright side, Everything else seems normal.  I ftp'd a2ps, an
ascii-to-postscript conversion utility, compiled it, set up my printcap,
and I now have the local print server ready for use for printing the
docs that come with the software.  Hey, what more can you ask for?

thanks in advance for the help!





-- 
Tony Reynolds            Have you hugged      cctony@sun1.mcsr.olemiss.edu
Cray Network Intern    your Washburn today?                  (601)232-7206
Newsgroups: comp.unix.bsd
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Re: NFS (mount hangs)
Keywords: NFS mount  
Organization: Iowa State University, Ames IA
Date: Mon, 27 Jul 1992 20:55:01 GMT

In <1992Jul25.152207.9033@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:


>Does the initial kernel (what you have when install has been run, the hard disk is booted and the bin01 files are installed) have NFS built in?

Yes, that's how I installed my system (extracted the files directly off
the ftp archive).

>In case it has NFS then why does it hang when I want to

>    mount host:/u /mnt            ?

Dunno.  Worked great for me.
-- 
------------------------------------------------------------------------------
Michael L. VanLoon                                     "Ignorance is bliss..."
michaelv@iastate.edu      --       Computer Engineering, Iowa State University
------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Subject: Re: AT&T sues BSDI
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Thu, 23 Jul 1992 12:14:09 GMT

erc@unislc.uucp (Ed Carp) writes:
+---------------
| sef@kithrup.COM (Sean Eric Fagan) writes:
| : One of the complaints was about the 1-800-ITS-UNIX (I didn't know ITS was
| : unix compatible... hmm), which is no longer a valid phone number, seeming,
| : to me at least, that that part of the complaint is either resolved or no
| : longer relevant.
| 
| Huh?  You mean that Pande Inc. (which has the number 1-800-SOS-UNIX), as well
| as anyone else that has UNIX in their phone number, has to change it?
| That's utter nonsense...
+---------------

No, I think the issue was more that BSDI was claiming "ITS-UNIX" ("it's Unix")
when it wasn't. ("Unix" *is* a trademark of AT&T.)


-Rob

p.s. Just what *are* we going to call these things that are "similar
to but not derived from 'Unix' (trademark of AT&T and/or USL)", anyway?
Just "BSD", maybe?

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com
Silicon Graphics, Inc.		(415)390-1673
2011 N. Shoreline Blvd.
Mountain View, CA  94043

Newsgroups: comp.unix.bsd