HDTenEightyP/NetNews huggingface dataset:
From: grog@adagio.UUCP (Greg Lehey)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 23 Jul 92 17:19:55 GMT
Organization: LEMIS, Schellnhausen 2, W-6324 Feldatal, Germany

In article <14kcimINNcr5@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
>In article <1821@adagio.UUCP> grog@adagio.UUCP (Greg Lehey) writes:
>>....
>>The real issue here is, of course, not the source. AT&T must know
>>about Bill Jolitz; according to the text here, he's guilty of the same
>>`crime'....
>
>To put any concerns to rest, we have not been contacted by anyone
>regarding our 386BSD code, nor have we heard anything negative about the
>386BSD releases. As 386BSD is intended for the research and educational
>communities and is freely available (not proprietary), all code we have 
>written is fully disclosed.

That's what I expected.

>Please refrain from using inflammatory words such as "crime" with respect to
>386BSD and the developers, as we are not involved in this matter.  We have 
>no relationship with BSDi or CSRG, nor do we condone the actions of any
>party involved in this dispute.

Bill, don't get me wrong. Note the `' around the word `crime'. I don't
believe you have done anything wrong, and I don't believe BSDI have
done anything wrong. But AT&T is claiming that Net 2 contains AT&T
licensed material. Under those circumstances, whether you like it or
not, you *are* involved in this matter, and they could theoretically
sue you as well. The intention of my post was to suggest that AT&T
isn't interested in doing that, and thus show what the real motives
for their action are.

>
>BTW, patches should be out in a few days, if we can ever get through mail.

Keep up the good work.
-- 
Greg Lehey                       | Tel: +49-6637-1488              
LEMIS                            | Fax: +49-6637-1489
Schellnhausen 2, W-6324 Feldatal, Germany
*** NOTE ***: Headers are mangled - reply to grog%lemis@Germany.EU.net
Newsgroups: comp.unix.bsd
From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
Newsgroups: comp.unix.bsd
Subject: Re: Jolitz 386BSD-0.1 -- floating point perform
Date: 23 Jul 92 01:03:41 GMT
Organization: University of Helsinki

In article <1992Jul22.152854.27730@nrao.edu> cflatter@nrao.edu writes:
> [ deleted ]  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)?

One thing that migth be a problem with porting gcc-2.2.2 to 386BSD is
that gcc-2.2.2 has added the 'fsqrt' command to the list of floating
point instructions that gcc can create code for - and I don't know if
the 386bsd math emulator emulates that particular command yet.  I've
already written the code (it's in linux), but it wasn't available back
when people ported the emulator to 386bsd. 

If 386bsd 0.1 does indeed use the linux math-emulator (I haven't even
checked: maybe they found something better) it shouldn't be difficult to
add the fsqrt support in there (the linux math-emulator may not be fast
or complete, but it's simple and relatively modular).  The code can be
gotten from any linux site: while the linux source is generally
copylefted, the math-code can be used freely for 386bsd (but /only/ for
386bsd - if you want to use it for something else and cannot accept the
copyleft conditions, contact me). 

		Linus
Newsgroups: comp.unix.bsd
From: pk@cs.few.eur.nl (Paul Kranenburg)
Subject: Re: NFS mount of /usr
Reply-To: pk@cs.few.eur.nl
Organization: Erasmus University Rotterdam
Date: Thu, 30 Jul 1992 11:45:52 GMT

In <sxjcb-290792093009@sxjcb.uacn.alaska.edu> sxjcb@orca.alaska.edu (Jay C. Beavers) writes:

>I've been playing around with NFS and such and it's working just fine, so
>I've
>tried to take NFS to it's next logical step on my 39 MB system -- NFS
>mounting
>/usr.  However, 386BSD seems to think that this is just a horrible idea and
>I've had no end of trouble.

>If I leave the rc file intact, I get a system hang after 'starting system
>logger'.

>If I edit the rc file to hardcode my old usr directory (/oldusr) to every
>file located in /usr I get a hang after the rc file ends.  

I have used a NFS mounted /usr from day 1 (never had a /usr partition on
the local HD). You need to set the correct parameters to enable your network
device to handle the traffic generated by the server. I am currently using a
WD8003 card which has an 8K buffer, so the default NFS read/write packet size
of 8K will most likely generate to many back-to-back ethernet packets when
mounting from a fast server. I use this entry in /etc/fstab:

bridei:/export/exec/i386	/usr	nfs rw,rsize=4096,wsize=4096 0 0

Reading from the NFS mounted filesystem is actually faster than from the local
hard disk (not much, but it was above expectations).

-pk
From: brown@vidiot.UUCP (Vidiot)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD
Date: 22 Jul 92 02:06:42 GMT
Reply-To: brown@vidiot.UUCP (Vidiot)
Organization: Vidiot's Hangout

In article <l6nibgINNje6@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
<
<All in all, this filing by a corporate giant with virtually unlimited funds
<for legal expenses would seem to spell the doom of 'free' UNIX projects as
<they are presently conceived.  There is simply too much risk someone with a
<prior exposure to AT&T source codes could manage to contaminate the product.
<
<Sigh, AJ

Sigh is right.  It is virtually impossible to not have had access to a Unix
system in one's career of computer science.  If that is allowed to stand,
AT&T will win every time.  Yuch.
-- 
      harvard\     att!nicmad\          spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot  ucbvax!uwvax..........!astroatc!vidiot!brown
      rutgers/            INTERNET:vidiot!brown%astroatc.UUCP@spool.cs.wisc.edu
                                   brown@wi.extrel.com
Newsgroups: comp.unix.bsd
From: rodeen@buddha.ncc.umn.edu (Rick Odeen)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD
Date: 21 Jul 92 15:20:07 GMT
Organization: Nutrition Coordinating Center, University of Minnesota

In article <l6nibgINNje6@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>Further, AT&T's question about the time investment of BSDI in bringing out
>their product [compared with their own cost over many years] will likely go
>a long way toward supporting their unfair competition claim.  If it took a
>small company like BSDI only a couple of years with a small team of people
>to produce BSD/386 vs the multi year investment of a corporate giant - then
>it is very possible AT&T may prevail on the unfair competition claim.

I don't think this is a valid claim, Linus Torvalds developed the Linux
system in less than one year from scratch.

-Rick Odeen


-- 
"MINIX costs $169, but the license allows  | Rick Odeen 
making two backup copies, so the effective | rodeen@buddha.ncc.umn.edu 
price can be under $60."                   | rutgers!umn-cs!buddha!rodeen
         - ast@cs.vu.nl (Andy Tanenbaum)   |
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: Where can I find Disk Manager???
Date: Thu, 23 Jul 92 10:07:37 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <5497@umriscc.isc.umr.edu> jlu@cs.umr.edu (Eric Jui-Lin Lu) writes:
>Where can I find the Disk Manager mentioned in INSTALL.NOTES?

Disk Manager is a commercial product (MSDOS-based, at least).  A data
recovery service claims that Disk Manager is the major cause of disk
crashes that they see.  Evidently it has something to do with Disk
Manager lifting the write heads during low-level format of MFM/RLL
drives.  This makes a disk vulnerable to small alignment changes.

If you only use Disk Manager to partition your disk, then this
shouldn't be a problem.  A similar utility which evidently is less
harmful is SpeedStor.  This is also a commercial MSDOS product.  On the
other hand, if  all you want to do is partition your disk, DOS fdisk or
even public domain utilities (see Linux archives, for instance) are
probably your best bet.  
-Andrew Moore <alm@netcom.com>
From: rick@pubah.hq.af.mil (Rick J Weldon)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD MSDOS partition recognition?
Date: 24 Jul 92 18:51:47 GMT
Reply-To: rick@pubah.hq.af.mil (Rick J Weldon)
Organization: J. Deitch & Associates
Originator: 386bsd-gate@jadpc.cts.com
Precedence: bulk



Reply-To: kevinz@storage.tandem.com (Kevin Ziegler)
Version: 5.31 -- Copyright (c) 1991, Anastasios Kotsikonas
From: kevinz@storage.tandem.com (Kevin Ziegler)
To: 386bsd-gate@jadpc.cts.com
Subject: 386BSD MSDOS partition recognition?


kevinz@storage.tandem.com (Kevin Ziegler) writes:
>I repartitioned my 120 MB hard disk over the weekend to create a 60 MB DOS
>and a 60 MB BSD partition, and then installed 0.1.  The installation went
>without a hitch, and the system booted fine.  However, when I tried to do
>a /usr/distbin/shutdown -todos to make the DOS partition active from within
>386BSD, I got a 'Can't make dos bootable' error.  Has anyone else seen this?0
>Do I need to do something to make 386BSD recognize my DOS partition?  Any
>help would be appreciated.

>KZ

Kevin if you get any resonses to this I would like to know also.
I installed manually using seperate partitions for / and /usr. 
I would like to know how to manually add a DOS partition that I can get
to.

Thanks a bundle
Rick Weldon     I-NET Inc. (Pentagon, 7TH Com Group)
E-mail: rick@hq.af.mil
Phone:  703-697-4654
Newsgroups: comp.unix.bsd
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: AT&T sues BSDI
Organization: Kithrup Enterprises, Ltd.
Date: Sat, 25 Jul 1992 21:12:16 GMT

In article <102@ampr.ab.ca> lyndon@ampr.ab.ca (Lyndon Nerenberg) writes:
>If their assertion is
>that BSD/386 is a derivative work based on System V, why are they not
>challenging this as a copyright violation?

Copyright, trade secret, and patents.  They just don't specify which one,
nor do they specify *what* has been used without license.

>As for the C vs. gcc argument, the feeling is that you cannot protect
>a programming language per se, although you can prevent someone from
>calling it 'C' if you properly protect the name 'C' as used in conjunction
>with that programming language. 

There are movements, both here (US) and abroad, to allow the patenting or
copyrighting of *languages*.  Ashton-Tate would have dearly loved that
ability.  Go ask in gnu.misc.discuss for more details.

>Witness what DOD has done to protect
>the name Ada. 

The DOD has dropped the trademark status of Ada.  Anyone can call anything
'Ada' now, I believe.

-- 
Sean Eric Fagan  | "My psychiatrist says I have a messiah
sef@kithrup.COM  |  complex.  But I forgive him."
-----------------+              -- Jim Carrey
Any opinions expressed are my own, and generally unpopular with others.
Newsgroups: comp.unix.bsd
From: douglas@s.ms.uky.edu (John Douglas Turner)
Subject: 386BSD and X with Local Bus
Keywords: X, 386BSD, Local Bus
Organization: University of Kentucky
Date: Wed, 22 Jul 1992 14:25:11 GMT

I am looking into getting a 486 with Local Bus and want to run
386BSD and X.  What video cards are currently supported?
I can either get the ET-4000 or a Targa S3 Accelerator, are either of these
supported?

john.....
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: Re: extract etc01 problem?
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sun, 26 Jul 92 09:59:10 GMT


>I successfully installed the bin01 set, and then tried to install the 
>etc01 set.  It ran for 10-20 minutes, and then a stream of errors 
>something like (from memory):
>
>extract:  etc01.xx : open:  too many open files
>
I got this same problem with etc01. When I looked at 'df's' output I saw
that my disk had run full  free -18619  106% (maybe the negative number is not
a bug but a feature?), and I blamed the fact that I had all of bin01,etc01 and src01 in /tmp at that time. I will get to extracting etc01 soon and will see
if extract will work now.

-- Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: Re: Help! Bad Spot on Disc??
Date: 22 Jul 1992 15:17:06 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu

In article <NEAL.92Jul22092722@neal.ctd.comsat.com> neal@neal.ctd.comsat.com (Neal Becker) writes:
>Try #1) After loadfd bin01, extract reports "bin01.11 corrupt".  I
>renamed bin01.11 to junk, and loaded another copy of bin01.11.  Now
>extract succeeds.
>

Do the two files compare (cmp) identical?

>When fsck -p was run, it reported "unknown inode type...".  When fsck
>run I cleared several of these, but each time fsck is run again the
>same errors are reported!
>

Please send me details (e.g. create a script file and send it). I noticed
a problem on initial reboot with socket inode types, but this vanished
after the first fsck and did not perpetuate (I assume that the binary
dump has some unecessary socket inodes on it that cpio is not
recreating properly, thus a nuisance).

>Looks like a bad spot, right?  But why?  Doesn't the software
>recognize the sectors already marked bad on the disk?

Currently, the system does not do the correct thing with fresh badblocks,
partially due to new work in the wd driver that alters the way that
retries work.

> ...
>problem.  This message keeps showing up (a lot):
>  swap_pager_finish: clean of page xxx failed
>
>Sounds nasty. 

It's not. It means that the VM system saw that the page was modified
after an attempted write to disk (it was dirtied by a program accessing
it). For the moment, consider it a soft error. Much more is involved here,
and I especially want to here if this happens more than sporadically on
systems with > 4MB of RAM, but for the moment ignore this diagnostic.

Don't worry, the sky is not falling (yet) !

Bill.
From: wzhang@cse.fau.edu (Wei Zhang)
Newsgroups: comp.unix.bsd
Subject: 386bsd0.1
Date: 22 Jul 92 03:21:21 GMT
Distribution: comp.unix.bsd
Organization: Florida Atlantic University, Boca Raton, FL, USA


Hi, folks:


I am new to this group. I have access to SUNSparc stations. Now I have
ftped some binary files, eg. dist.fs, etc., how do I cpio them to floppy?
We have a 1.4M floppy driver in our system. Beyond that, once I get the
bootable disk, how do I get the binary into the floppy. I think that
I would do it on the SUN system rather than kermit the executable to my 
PC, which takes long long time. I do not want to rawrite either. Please
any help is appreciated. I figure that these are rather simple questions.


Thank you.


Wei Zhang
From: sxjcb@skyfire.uacn.alaska.edu (Jay C. Beavers)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd 0.1 - Speed dependent boot problem
Date: 21 Jul 92 20:30:43 GMT
Organization: University of Alaska Computer Network

In article <greg.711746666@hibp2.ecse.rpi.edu> greg@ecse.rpi.edu (Greg) writes:
>Newsgroups: comp.unix.bsd
>Path: raven.alaska.edu!decwrl!mips!zaphod.mps.ohio-state.edu!rpi!greg
>From: greg@ecse.rpi.edu (Greg)
>Subject: 386bsd 0.1 - Speed dependent boot problem
>Message-ID: <greg.711746666@hibp2.ecse.rpi.edu>
>Nntp-Posting-Host: hibp2.ecse.rpi.edu
>Date: Tue, 21 Jul 1992 19:24:26 GMT
>Lines: 22


>I seem to have a problem booting that is timing dependant. My machine will
>boot off wd0 about 95 % the time when in low speed mode. In high speed (33MHz)
>it boots only about 20% of the time.

>My equipment:
>386-33 Advanced Integration Research motherboard (1 CHIPS & 2  ETEQ VLSIs)
>Quantum 105lp IDE
>Trident 8900 vga
>Novell Ne2000 ethernet


>I started to poke around in the boot stuff. I put a printf at the begining of
>boot.c. I rebuilt wdboot and bootwd and then re-disklabeled. I verified that
>boot.c was not reached when the boot failed. When it succeeded, I saw my
>debugging message. My 80x06 assembly is a bit rusty, so I hesitated to
>plunge into wdbootblk.c. Before I do this, I wonder if anyone can give me any
>possible stategies.

>      Thanks, Greg                 greg@megas.ecse.rpi.edu

Perhaps. but not necessarily clockspeed alone.  My 386/25 always boots 
correctly, while my 486/25 boots maybe one in eight times......

 - jcb
______________________________________________________________________________
                                      |
Jay C. Beavers                        |   sxjcb@orca.alaska.edu 
University of Alaska Computer Network |   sxjcb@alaska.bitnet
______________________________________|_______________________________________
Newsgroups: comp.unix.bsd
From: tg@utstat.uucp (Tom Glinos)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD]
Organization: University of Toronto, Dept. of Statistics
Date: Fri, 24 Jul 1992 19:53:10 GMT

"In a mortal battle between two opponents, the attacker must vanquish,
the defender, need only survive."

Not having done my own homework, (ie compare the 32V source with
the BSDI source) I would hazard to guess that USL's position
is without merit.

BSDI will prevail if they can hold out and continue on with business.
-- 
=================
No regrets, ever!			| Tom Glinos @ U of Toronto Statistics
For down that path, lies madness	| tg@utstat.toronto.edu
Newsgroups: comp.unix.bsd
From: wagner@utoday.com (Mitch Wagner)
Subject: Re: AT&T or USL, and extrapolation
Organization: Open Systems Today
Date: Thu, 30 Jul 92 15:56:34 GMT

In article <1992Jul23.064028@eklektix.com> rcd@raven.eklektix.com (Dick Dunn) writes:
#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.)

AT&T is a majority shareholder in USL. 

What does this mean as far as how much clout AT&T has. I don't know,
and I think anybody who CLAIMS to know without sitting in on some
Board of Directors meetings for USL is simply blowing smoke. AT&T is a
mighty big corporation and USL---which has about $100 million
revenues---is might small stuff to them.

          -- mitch w.
From: bill@prijat.cs.uofs.edu (Bill Gunshannon)
Newsgroups: comp.unix.bsd
Subject: Re: Announcing 386BSD Release 0.1
Date: 21 Jul 92 17:27:16 GMT
Reply-To: bill@platypus.uofs.edu
Organization: University of Scranton, Scranton, PA

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.

bill

-- 

     Bill Gunshannon          |        If this statement wasn't here,
     bill@platypus.uofs.edu   |  This space would be left intentionally blank
     bill@tuatara.uofs.edu    |         #include <std.disclaimer.h>
From: vera@fanaraaken.Stanford.EDU (James S. Vera)
Subject: Re: USL vs. BSDI, and what to do
Organization: Program Analysis and Verification Group, Stanford University
Date: 26 Jul 92 05:28:26 GMT

tinguely@plains.NoDak.edu (Mark Tinguely) writes:

>In article <scs.712004511@wotan.iti.org> scs@iti.org (Steve Simmons) writes:

> I was under the impression that AT&T sold most if not all of its interest
> in USL.

Quoting from the complaint:
  USL is a subsidiary of American Telephone and Telegraph ("AT&T") ...

Newsgroups: comp.unix.bsd
From: baird@rushes.enet.dec.com (Alasdair Baird)
Subject: Re: 386bsd security enhancements are needed before using INTERNET!
Reply-To: baird@films.enet.dec.com
Organization: Digital Equipment Corporation
Date: Wed, 29 Jul 1992 08:57:07 GMT

In article <1992Jul28.164752.7422@gateway.novell.com>, terry@npd.Novell.COM (Terry Lambert) writes:
|> 
|>	There are exceptions, and it is possible to get an export license
|>for crypt libraries.  It is much easier to get an export license for a
|>set of binaries (login, passwd, rshd, rlogind, etc.) than it is to get one
|>for the library itself.  Part of the terms of the license include who you
|>are allowed to sell it to. Internet access is restricted in a similar fashion,
|>thus it is likely that a grant of license to distribute binary utilities for
|>386BSD would be allowed, if requested.  But this would mean that not all of
|>386BSD is publically distributable as source.
|> 

Of course if someone were to implement the DES algorithm outside the US, say in
Australia (perhaps using one of the many books that are freely available which
explain the algorithm) and then make the source available outside the US, there
is no problem as it can be imported and used in the US (though not re-exported)
and obtained and used elsewhere too without breaking US regulations.  I think
the main restriction here is that is has to be DES so the NSA can be sure of
breaking it any time they want.  This would also have the unfortunate effect of
splitting the distribution in two.

But then you shouldn't beleive anything I say, because not being a US citizen
I'm probably considered to be an agent of a hostile power...

---------
Alasdair Baird                              Digital Equipment Co.
Speaking only for myself.                   Livingston, Scotland.
Newsgroups: comp.unix.bsd
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Re: Adding users
Organization: Iowa State University, Ames IA
Date: Mon, 27 Jul 1992 19:34:50 GMT

In <1992Jul24.215139.26837@nrao.edu> cflatter@nrao.edu (Chris Flatters) writes:

>	2 - (Optional) If you want the new user to be able to use the su 
>            command add his user name to the wheel group in /etc/group.

Just out of curiosity, where did the name for this group, "wheel," come
from, anyway?  I've always wondered this...

-- 
------------------------------------------------------------------------------
Michael L. VanLoon                                     "Ignorance is bliss..."
michaelv@iastate.edu      --       Computer Engineering, Iowa State University
------------------------------------------------------------------------------
From: randy@chinet.chi.il.us (Randy Suess)
Newsgroups: comp.unix.bsd
Subject: Re: Hard boot needed for WD ethernet card to be recognized
Date: 22 Jul 92 14:05:43 GMT
Organization: Chinet - Public Access UNIX

In article <1992Jul21.190622.26756@ugle.unit.no> Havard.Eidnes@runit.sintef.no (Havard Eidnes) writes:
>Hi,
>
>I've not seen this mentioned before, so I thought I should ask whether any-
>The error is that one have to do a hard reset of the machine in order for
>the autoconfigure to find the ethernet card!  

	I found the same thing, with any ethernet card at int 2 and
	io 280.  When I re-compiled the kernel and removed the other
	ethernet devices, this went away.  I think the boot config
	program is being confused by one of the other card definitions.

-- 
	I am created Shiva the Destroyer; Death, the shatterer of worlds!
	Who is this dog meat who stands before me now?
	That's the biz, sweetheart.
Randy Suess					 randy@chinet.chi.il.us