HDTenEightyP/NetNews huggingface dataset:
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 25 Jul 92 10:14:13 GMT
Organization: St. Peter's College, US

In article <QUANSTRO.92Jul24122923@lars.StOlaf.edu>, quanstro@lars.StOlaf.edu (goon) writes:
> What a sec. Perhaps I am being rather dense. But aside from size and
> age (two factors which are rather irrevelent) What's the difference
> between BSDI and AT&T. They are both trying to __sell__ a rather
> expensive operating system. And since _when_ does selling a system
> have to do with intellectual freedom. Suppose that BSDI were to
> continue with their operating system and suppose that in ten years
> somebody else tried to say that they were BSDI UNIX. Don't you think
> that BSDI would get a little upset?

  The important thing is that BSDI took some code which was publicly avail-
able, put a lot of effort into polishing it up and porting it to a new ar-
chitecture, and began selling it, and that AT&T/USL claims that they do not
have the right to do so.

  If AT&T/USL wins this case, this means that any vendor can claim that they
have rights of "intellectual ancestry" or some such balderdash over any pack-
age found on the net. What would you think if they claimed that AT&T/USL had
"rights" to GCC because the specification of C was originally developed by
them?

  How about the Jolitz's code? They've done essentially the same thing as
BSDI except that they're not charging for it. Note that the law does not dis-
tinguish between "free" and "commercial" in cases of trademark law. In other
words, I can't give away boxes of tissues labeled "Kleenex" (a registered
trademark of Kimberly-Clark Corporation) if they aren't in fact Kleenex brand.

  In fact, in order to retain trademark protection, AT&T/USL would be _re-
quired_ to sue any and all infringers if the infringers refused to cease and
desist the unlawful trademark usage, or if AT&T/USL desired recompense for
losses due to such wrongful usage.

  Aside from the trademark claim (item 1 in the complaint), the rest of the
claims attempt to do exactly this. As far as the trademark claim, a BSDI bro-
chure that I FTP'd from UUnet in March did _not_ have the "ITS UNIX" number
in it, so I believe BSDI made a good faith effort to comply with AT&T's prior
request to cease using that number. Thus, I don't see why the first claim is
included in the suit, except possibly to attach some stigma to BSDI.

> Er, we aren't talking about anything _really_ important here. There
> are much more important things to get upset about.

  I hope you'll change your mind after reading my comments.

  By the way, the day I heard about this, I went out and bought a copy of
BSDI/386 and a support agreement. I hope those of you who need a commercial
quality 386 Unix will do the same (note that the Jolitz's state that their
code should not be used for commercial purposes).

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
Newsgroups: comp.unix.bsd
From: kapela@prism.poly.edu (Theodore S. Kapela)
Newsgroups: comp.unix.bsd
Subject: Re: I wonder, did AT&T backstab BSDI?
Keywords: AT&T speculation lawsuit BSDI
Date: 29 Jul 92 18:21:41 GMT
Organization: Polytechnic University, New York

In article <1992Jul29.144859.8222@bas-a.bcc.ac.uk> ucacmsu@ucl.ac.uk (Mr Stephen R Usher) writes:
>In article <1992Jul28.153750.8395@mintaka.lcs.mit.edu> knight@hal.gnu.ai.mit.edu (Knight of the Living Dead) writes:
>>
>>As I recall when System 5 Revision 4.0 was released, it was described
>>(to me, anyway) as an attempt to gain "BSD Compatibility".  I'm wondering
>The only problem with this idea is that SYSVr4 (NOT System 5, that was
>another Unix way back) doesn't look like BSD, it still looks like SYSV to

SVR4 is System V, Release 4.  System 7 was an early version of Unix
way back (in the pre-dawn era :-) )

>the normal user, ie you have horrid syntax for the ps utility where you need
>to use a hyphen in front of the arguments and the devices... yuck!

Actually, this would make "ps" *consistent* with other unix utilities.  In
general, options are preceded by a dash, arguments to those options aren't.

>
>The only real thing I've seen which is BSD is the socket library (not
>complete) and the BSD compatibility library which is not complete either.
>

What about POSIX signals?  They are derived from Berkeley signals. 
The old System V (pre- R4) methods of handling signals was brain-dead.

-- 
..............................................................................
 Theodore S. Kapela				kapela@poly.edu
 Center for Applied Large-Scale Computing	
 Polytechnic University
Newsgroups: comp.unix.bsd
From: niko@iastate.edu (Nikolaus E Schuessler)
Subject: Re: 386bsd security enhancements are needed before using INTERNET!
Organization: Iowa State University, Ames, IA
Date: Mon, 27 Jul 1992 21:42:49 GMT


>
>It isn't that the algorithms are crackable -- it's that they take what the
>NSA considers an unreasonable amount of time to crack, and, as such,
>distribution of a working crypt library represents a perceived threat to
>the national interest (USA).  This is, in point of fact, a real problem,
>in that you can encrypt sensitive data in the US and send it out on a public
>channel.  By the time it has been decrypted, the damage has already been
>done, as the distribution of the data is no longer taking place and can not
>be thwarted.
>

So the inherent problem you are worried about is that everyone is using
the same crypt library, right? Because it is far easier to use the one
given as is than to create a new one? Who generated it? Does anyone
know? There must be a way to generate a different one, right?

I think I may not be understanding something fully.




-- 
Niko Schuessler               
Project Vincent Systems Manager              email: niko@iastate.edu
Iowa State University Computation Center     voice: (515) 294-1672
Ames IA 50010                                snail: 272 Durham 
Newsgroups: comp.unix.bsd
From: terry@npd.Novell.COM (Terry Lambert)
Subject: Re: 386BSD 0.1 installed on DECstation 325
Organization: Novell NPD -- Sandy, UT
Date: Thu, 30 Jul 1992 17:46:41 GMT

In article <1992Jul30.070050.194@rdg.dec.com> hitchens@untadh.enet.dec.com (Francis J. Hitchens) writes:
>I have installed 386BSD on a DECstation 325, a 386 with connors
>CP30104 and WD8003EP ethernet card.
>
>First try was on a 40mb partition, with the patched dist.fs from
>agate.berkley.edu . The system part came up after the INSTALL reboot,
>but only as far as printing the ethernet device info, then it crashed
>with some vm_bla... error, it was too fast for me to read.
>
>I then installed on the whole disk, and it reboots ok without
>crashing. Anybody know why this is so and how to fix it, as I will
>have to put DOS back on the whole machine soon if I can't reserve 40mb
>for 386BSD alone ?

Number one cause of this problem:  Your swap partition isn't on an even
boundry.  Make sure your 386BSD partion starts on an even boundry.

					-- Terry
Newsgroups: comp.unix.bsd,can.general
From: dwex@cbnewsj.cb.att.com (david.e.wexelblat)
Subject: Re: AT&T sues BSDI & Our Retaliation
Organization: AT&T
Distribution: usa
Date: Tue, 28 Jul 1992 17:25:42 GMT

In article <1992Jul24.075238.12570@apt.bungi.com> brian@apt.bungi.com (Brian Litzinger) writes:
> In article <9207231306.AA06854@GRANNY.CS.NYU.EDU> m-jk8594@GRANNY.CS.NYU.EDU (James Kyriannis) writes:
> >I don't believe simply disconnecting your AT&T service, destroying your AT&T
> >calling/credit cards, or boycotting System V is going to make AT&T notice
> >your disgust in their policies.
> >
> >Simply telling a 'phone rep.' that you want your long distance service
> >disconnected because AT&T sucks isn't enough -- your telephone conversation
> >with the 'rep' is not going to be recorded and played back to his/her 
> >manager.  People of higher authority have to hear your statement if you
> >want to make any sort of impact.
> 
> I called my local AT&T sales droid and told them that I was upset
> over this USL (AT&T) vs BSDI lawsuit and that I would disconnect
> my long distance service with AT&T if AT&T didn't drop that suit.
> 
> I expected, of course, sort of a yawn from the sales droid.  Instead
> the sales droid was very interested and wanted to write down the
> details of my complaint, and said that she was going to forward them
> to some big-wig somewhere.
> 
> However, I agree with James' assessment.  A letter is in the works.
> 
> brian@apt.bungi.com


[I work for AT&T, not USL.  I am not making any judgements, or even stating
 my beliefs.]

When you tell the AT&T sales resp why you are switching service to another
vendor this information DOES get written down, and this data is tabulated
and forwarded up the ladder.  I really have no idea if this data has any
impact on anyone (I'm just a lowly software developer :->), but it DOES
NOT go into the bit-bucket.  A complaint lodged through this channel will
have at least as much impact as a letter (it may have more, because it
gets directly into the appropriate channels this way).

So if you decide to switch vendors, be sure to tell AT&T the reason why.
It may help your cause in the long run.  I can only hope that you will
switch back if things are resolved to your satisfaction.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
David Wexelblat             | dwex@mtgzfs3.att.com  | Somebody get me a
AT&T Bell Laboratories      | ...!att!mtgzfs3!dwex  |   cheeseburger!
200 Laurel Ave - 4B-421     |                       |      
Middletown, NJ  07748       | (908) 957-5871        | --Steve Miller Band
From: dec@lazarus.nrtc.northrop.com (Dwight E. Cass)
Newsgroups: comp.unix.bsd
Subject: Ouch...The System Reboots...
Date: 27 Jul 92 17:41:46 GMT
Organization: Northrop Research & Technology Center, Palos Verdes, CA

Does the following happen on your system?

	1. Create the /var/games directory (so rogue has a place to
	   put its scores)
	2. Start the distributed copy of rogue (do NOT recompile)
	3. Quit immediately - creating a score record
	4. Restart rogue and this time, allow yourself to be killed
	   by a monster - causing a score record to change

	Does your system reboot?  Mine does - no panic, no messages,
no crash dump, just a reboot.

If you rebuild rogue - that version will core dump with either a
segmentation violation or memory fault (see my earlier post about bugs
in stdio) - but the distributed program (which is actually just a link
to /usr/games/dm) cause the system to reboot.

Anyone got any ideas - anyone got an Emulator to look at this one?
/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...
From: toreh@bootes.sds.no (Tore Haraldsen)
Subject: Re: 386BSD & AHA1542B & CDC94171-9 Disk problem
Organization: Statens Datasentral A/S, SDS, Norway
Date: Tue, 21 Jul 1992 16:21:55 GMT

Yes, my problem is different. I discovered that after discovering how
I had goofed up:

	I DON'T HAVE A 1542B, I GOT A 1542A Rev.D w/3.07 proms.

which is quite a different animal. David Eyre mailed me and explained
it all, and I think I got the gist of it:

The driver supplied with 386BSD-0.1 uses opcodes that have no support
in the older boards, namely opcodes 3 & 4, << scatter/gather read/write
with retun of residual length >>.

Mr.Haug also ventilated some worries in that direction. I have put up
the problem in comp.periphs.scsi, and asked if we hapless owners of
1542A adapters can get a rom upgrade...

In the meantime David Eyre is trying to mail me an updated boot disk.
(We have no public ftp places, any of us). If there are more people
needing a modified Tiny, I will try to put it onto one of the offical
servers (tell me the correct one, so it will spred itself nicely).

Mail me, you with the same problem, and I will tell you when and where
it is available, maybe I even could announce it HERE!!

-- Tore Haraldsen
From: faldor@seq.uncwil.edu (Faldor Inglorion)
Subject: color usage
Organization: Univ. of North Carolina @ Wilmington
Date: Wed, 29 Jul 1992 19:42:23 GMT

	I was wondering, how do you set the background, echo, etc... colors
for a color monitor using 386bsd-0.1's own stuff.  I know it can do it,
as I watched it goto blue and yellow when it did the automatic reboot.
Any help would be greatly appreciated.

Thanx,
Faldor

.___________________________________________________________________.
|               University of North Carolina at Wilmington          |
|                          Faldor Inglorion                         |
|                        faldor@seq.uncwil.edu                      |
|-------------------------------------------------------------------|
|  Alien Invasion Division : Integration/Substitution Group. (ISG)  |
.___________________________________________________________________.
Newsgroups: comp.unix.bsd
From: blancha@seq.uncwil.edu (Chris Blanchard)
Subject: Problems with vi/elvis HELP!!
Organization: Univ. of North Carolina @ Wilmington
Distribution: World
Date: Tue, 28 Jul 1992 06:36:04 GMT

  Hi all,
        I have a slight problem with vi/elvis under 386BSD 0.1. Basically
it dumps core. When I vi anything, or for that matter nothing, I get an error
that the screen size is too small and then a bus error core dumped. This is
from the console. If anyone has any advice please help me out. 
Thanks in advance.
Chris. 

-- 
-----------------------------------------------------------------------------
| Internet:                        |Chris Blanchard | Phone: (919) 452-9638 |
| blancha@seq.uncwil.edu           |-----------------------------------------
|                                  |   Think of it as evolution in action   |
Newsgroups: comp.unix.bsd
From: jbev@iscden.jbsys.com (Jim Bevier - J B Systems)
Subject: Using fixit.fs to build disk?
Organization: J B Systems on HiPeak, Morrison, Co.
Date: Wed, 22 Jul 1992 23:41:17 GMT


I have been trying to install 386BSD using the fixit.fs disk.
I am using a Miniscribe 9380 which is 1224 x 15 x 35 when 
formatted with the alternate sector option.  I was able to
install using the dist.fs and it seemed to work fine.  I saw
Chris Demetriou's suggestion on how to to a "real installation"
and thought I would give it a try.  I have a DOS 5.0 partition
on the disk which covers the first 620 cylinders.  I used the
information from the disklabel -r wd0 from the dist.fs system
as a basis for the disktab entry.  I followed Chris's instructions
on how to do it.  When I try to reboot the system, I either get
random colors all over the screen, with the harddisk seeking, and
the floppy light on, or an error message saying there is an error
in the bad-sector file, followed by other stuff to fast to read,
and endless reboots.  After this, the disk partition table
is gone. 8-(

So after several attempts, with the same results, I went back
to the dist.fs disk, thinking one file system wasn't so bad.
Install tells me I have 154mb of space.  If I try 154, 150,
140, 120, 100, or 80mb, all goes well until I try to reboot.
I get an error message saying there is an error in the
bad-sector file, then more messages and the system reboots.
Over and over.  So, what did I hose up?  Where is this error
coming from?  It worked once, but no more.

Ideas?

Jim Bevier
jbev@jbsys.com

-- 
+=+     From the mountains of Colorado:   jbev@jbsys.com      +=+
+=+           when it's not snowing, the sun is shining       +=+
+=+     Jim Bevier    -   J B Systems   (303)-697-1038        +=+
+=+         10136 Horizon View, Morrison, CO 80465            +=+
Newsgroups: comp.unix.bsd
From: tal@Warren.MENTORG.COM (Tom Limoncelli)
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: Mentor Graphics, Silicon Design Division
Date: Wed, 22 Jul 1992 16:34:07 GMT

In <3674@vidiot.UUCP> brown@vidiot.UUCP (Vidiot) 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.

Maybe I've been reading a New York Times from an alternate universe,
but I thought AT&T is a bit tight on money these days and doesn't have
"virtually unlimited funds for legal expenses"... or do you just mean
"more funds than BSDI"

USL has been publishing press releases saying that Windows NT is the
real enemy, and they don't care who's Unix you buy, just as long as you
buy something that looks like Unix... because they'd rather see people
switch to Unix than Windows NT.

In article <l6nibgINNje6@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>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.

Gee, I went to a tiny liberal arts school that doesn't get all those
favors and perks from Corporate America.  I never have seen a source
license.  I guess that just bumped up the value of my degree?  HHOS.

Tom
HHOS -- "Ha, ha, only serious".
-- 
Tom Limoncelli -- tal@warren.mentorg.com (work) -- tal@plts.uucp (play)
      Maybe Bush will follow Perot's lead.
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: Another 0.1 success
Date: 20 Jul 92 16:57:29 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <1992Jul20.140617.17787@usl.edu> pml@cacs.usl.edu (Patrick M. Landry) writes:

>I brought up 0.1 on a stock ComuAdd 486/50 this weekend.
>Absolutely no problems other than the nits that have been
>discussed here already. I left 100 meg around for DOS
>and gave the rest of my 400 meg disk to BSD.

>I will be trying to get a PPP link up to my office this
>week. I am also looking forward to the X release mentioned
>here recently.

>Thanks Bill and Lynne! Great work!

>I have one newbie question. Since the install only creates
>one partition by default where does the system do swapping?
>--
>patrick

I does not create only one partition, it really makes two. Use the 
disklabel program to see that the last 10000 blocks (5MB) of the whole
disk (wd0c) are used for the swap file system wd0b.

More interesting are the asterisks for wd0b in this display (if you have
some). This is a cylinder misalignment of the swap partition. I haven't
run into the problem of extreme swapping, so: has the bug been corrected that
overwrites part of the adjecent partitions on misalignment? What will 
happen if the 5MB allocated are not sufficient for a 'memory hog' task?

Curious to know about that

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
Newsgroups: comp.unix.bsd
From: fredw@mks.com (Fred Walter)
Subject: Re: What kind of tape is OK w/ 386BSD?
Organization: Mortice Kern Systems Inc., Waterloo, Ontario, CANADA
Date: Wed, 29 Jul 1992 16:14:38 GMT

dc@cobi.gsfc.nasa.gov writes:
>Can someone point me toward a list of 386BSD compatible
>tape devices, so I'll know that what I'm buying will work?

I don't know if there is a list, but if not, let's start one :

	Wangtek 5099EN
	Wangtek 5150EQ

I have both of these and both work under 386BSD 0.1. Maybe that FAQ-guy
could add this question to his FAQ.

I imagine any tape drive controlled by a PC-36 controller card will work.

	fred
-- 
Disclaimer: everything I write is my *personal* opinion and does not represent
or reflect the opinion of the company which employs me.
From: rt@MAGEC.COM (P.A. Marshall  x8330)
Newsgroups: comp.unix.bsd
Subject: AT&T sues BSDI
Date: 22 Jul 92 21:13:20 GMT
Organization: MAGNAVOX Electronics Systems Co., Fort Wayne


>vixie@pa.dec.com (Paul A Vixie) writes:
>> [If AT&T is that worried about everyone having a license, why haven't they
>> gotten uunet/dec/etc. to pull the Net-2 sources out of the public archives?]
>
>i'm sure that if they win their court case, they will try very hard to do that

and

>eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:
>In article <1992Jul21.104627.3353@mel.dit.csiro.au>
>	smart@wanda.mel.dit.CSIRO.AU (Robert Smart) writes:
>
>: This is insanity. Surely this will be thrown out of court.
>Who is going to defend NET/2?


In the past some postings to this newsgroup have been critical of the
approach BSDI has taken with BSD.  IMHO, now is the time to put all
these feelings aside and stand by BSDI.  If BSDI goes down we stand
to lose our access to a 'free' BSD (possibly to any free Un*x).
In a posting by Mike MacKenzie (mm@mentor.cc.purdue.edu) it was
suggested that we might change our phone service from AT&T to another
carrier, IMO a fine idea, but let's make sure AT&T gets the word on
why users are switching (Ideas anyone?).
  Now here I go, sticking my butt into the line of fire.  Many a
business has gone under fighting legal battles that eat up both time
and money.  It is to our advantage to help (if possible) BSDI win this
battle--  If BSDI wins, this silly question of 'have you ever seen a
fragment of AT&T code' will be over, moot, done.  However if AT&T wins
then the same question can be asked of any other free Un*x, and there is
only one place that this can end... *no* free Un*x.  There is one way we
can help BSDI in this battle with the Death Star, money, buy a copy of 
BSD from BSDI.  If you were thinking of doing it some day, if you were
going to talk the boss into getting a copy, what ever, do it now.  I
have placed my money were I think my interest in 'free' Un*x can best be
served in this battle and placed my order (1.800.800.4BSD) for a copy.

Keep Unix Free, or Wish You Had.

I am not connected in any way with or have any interest in BSDI.
-- 
Al Marshall
rt@magec.com					Standard Disclaimer...
netwrk!rt
Newsgroups: comp.unix.bsd
From: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Subject: Help wanted to write a device driver for DE200 DEPCA card.
Reply-To: hitchens@untadh.enet.dec.com (Francis J. Hitchens)
Organization: Digital Equipment Corporation
Date: Thu, 30 Jul 1992 07:09:25 GMT


Hi,

I would like to try and write a device driver for the DE200 DEPCA
Turbo ethernet board from DEC.

I have the relevant technical DOCS, but am lacking a guide to writing
device drivers for 386BSD. Anybody got such a thing, or any other
idiot aid.

regards Francis J. Hitchens
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: 386BSD on ALR??
Date: 29 Jul 92 13:58:47 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <1992Jul29.122935.4015@nynexst.com> rjc@nynexst.com (Robert Casazza) writes:

>I'm having trouble booting the "tiny" distribution diskette.
>I've tried the debugging version with no success.  I get
>no messages, the system just hangs and I have to power down.
>I've tried cold booting with no success.

>Configuration:

>ALR BusinessVEISA 386/33, 8Mb, 200M IDE Conner, Paradise SVGA,
             ^^^^^
>shadow bios disabled.

>Does anybody have 386BSD running on an ALR??

>Thanks,
>Bob
>-- 
>Robert Casazza                                rjc@nynexst.com
>NYNEX Science & Technology Center
>White Plains, NY 10604

Does the above really read EISA? If so:

	N O  S U P P O R T  F O R  E I S A  A N D  M I C R O C H A N N E L

	A R C H I T E C T U R E S  Y E T !!!

Give it up.

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
Newsgroups: comp.unix.bsd