HDTenEightyP/NetNews huggingface dataset:
From: ian@airs.com (Ian Lance Taylor)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!
Date: 25 Jul 92 03:55:46 GMT

andrew@alice.att.com (Andrew Hume) writes:

>an embargo against plan 9, as some have proposed, would be utterly pointless.
>do you seriously think for a femtosecond that USL gives a damn about you
>using plan 9? (i'm sure they are indifferent but if they had an opinion, they
>are probably glad you aren't using plan 9.)

I think it's fairly clear that avoiding Plan 9 will have little or no
effect on the law suit against BSDI.  However, it appears to me that
avoiding Plan 9 would be a good way to avoid law suits in the future.
Once upon a time Unix was available as a research system, and many
people looked at it.  USL is now essentially alleging that those
people can no longer produce untainted OS code.  What's to stop the
same thing from happening with Plan 9 in the future?  Much as I
respect Mr. Hume and the people who have worked on Plan 9, and
although I find its ideas quite interesting, you could not pay me to
look at that code now.
-- 
Ian Taylor | ian@airs.com | First to identify quote wins free e-mail message:
``It takes a man months and months to reconcile himself to a new hat.  And
  just when you're preparing to send it to the jumble sale, he says, `That's
  rather a nice hat you've got on, where did you get it?' ''
From: cgd@agate.berkeley.edu (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Suggestion to somebody who's really bored (hack SCSI driver!)
Date: 24 Jul 1992 02:49:12 -0700
Organization: Kernel Hackers 'r' Us
Distribution: world
NNTP-Posting-Host: agate.berkeley.edu
Summary: 386bsd SCSI driver needs rewrite; make nice project for somebody
Keywords: SCSI, ugly, 386bsd, boredom, project, driver, panic, crash, burn

Any *bored* 386bsd 0.1 hackers out there?

Here's a suggestion for a project:

re-write Pace Willison's SCSI driver...

He's not going to have a chance to work on it much more, as i
understand, and, in my opinion, it *DEFINITELY* needs work...

Note, however, that this would require some *major* design changes --

when i say it needs work, i mean "you should have the disk and tape
drivers *outside* the SCSI controller driver, *AND* there should
be the possibility of dropping in *OTHER* SCSI controller drivers,
if they're ever written...", etc...

this would do several things:

(1) Make disk and tape devices easier to debug,
(2) make the scsi controller driver easier to debug (and make the
	interface "line" nicer...)
(3) allow people to add drivers for new SCSI controllers more easily,
and, finally,
(4) allow people to add drivers for new SCSI devices more easily...

If no body bites on this one, i'll probably start work on it
when i get a "real" machine capable of running 386bsd ... (while
a 4M 386-20, with 100M disk is better than some systems and is,
in fact better than what 386bsd was developed on, I don't really
want to suffer that much... 8-)

If you're thinking about doing something along these lines,
send me mail!  i'd be glad to discuss it w/people, and if they (you?)
want to do it, i wouldn't mind writing some of the drivers...


cheers,

Chris
-- 
                            Chris G. Demetriou
                             cgd@berkeley.edu

     I'm not from the computer center, and I'm *NOT* here to help *YOU*!
Newsgroups: comp.unix.bsd
From: wkt@rodos1.cs.adfa.oz.au (Warren Toomey)
Subject: 386BSD Bug: Setting empty DOS part'n to A5 stops 0.1 boot
Organization: Australian Defence Force Academy, Canberra, Australia
Date: Tue, 21 Jul 1992 00:14:44 GMT

I wrote in yesterday asking about getting a 10M 386BSD (A5) partition to
co-exist with 2 other DOS partitions. Obviously, the install on the Tiny
disk is a no-go, so I decided to do it manually.

Ok, so using Disk Manager I converted the empty (00) 10M DOS partition 3
to A5 (DOSPTYP_386BSD) and booted Fixit. It hangs after ``using fd0a as
root device'' (or a similar message). The Tiny disk does likewise.

Next step, attempt to change 00 -> A5 _after_ booting Fixit, by a clever
use of dd(1): read in the first block from /dev/rwd0d into a temp file,
overwrite the 00 with an A5 from another file (clever use of seek and skip
here), and write the modified block back to /dev/rwd0d.

Problem: You can't _write_ rwd0d. dd fails, as does cat  > /dev/rwd0d.

So I'm stuck. Could anybody who has made a small 386BSD partition that
co-exists with a DOS partition please send me some mail!!! Thanks.


  Warren Toomey VK1XWT, on the path to insanity
  No longer in the bowels of ADFA Comp Science.
   `Version 7 Job Control: just use ptrace(2).'
Newsgroups: comp.unix.bsd,misc.jobs.misc
From: zrgl0376@helpdesk.rus.uni-stuttgart.de (Cowboy aka Bjoern Lemke)
Newsgroups: comp.unix.bsd
Subject: 386bsd-0.1 avail. on rusinfo
Date: 21 Jul 92 11:34:20 GMT
Article-I.D.: news.1992Jul21.113420.19713
Organization: User Help Desk, Comp. Cent. (RUS), U of Stuttgart, FRG

Hi all!
The complete 386bsd-0.1 distribution is available on the softserver of
the university of stuttgart called:

	rusinfo.rus.uni-stuttgart.de 
	(or rusmv1.rus.uni-stuttgart.de [129.69.1.12])

You can get the stuff via anonymous ftp, cd /soft/unix/i386/386BSD.
The files stored under bootable and bindist are checked for correctness,
all files in srcdist and etcdist still must be checked.

	Enjoy,
		Bjoern

-- 
Bjoern Lemke --*-- RUS --*-- University of Stuttgart --*-- Germany
Voice: 0711/4579533    \_,@         Mail: lemke@rus.uni-stuttgart.de
                        >>   Be insatiable! 
Newsgroups: comp.unix.bsd
From: randy@chinet.chi.il.us (Randy Suess)
Subject: Re: second drive on 0.1
Date: Wed, 22 Jul 1992 13:47:00 GMT
Organization: Chinet - Public Access UNIX

In article <explorer.711733278@tbird.cc.iastate.edu> explorer@iastate.edu (Michael Graff) writes:
>>Could someone make a kernel configured for two drives available on one of
>>the FTP sites?  

	I have had a number of offers to make the kernel I have running
	with 2 drives available on some ftp archive sites.  Gonna do that
	today.  The kernel also has the ne2000 set for int 11 to get around
	the problems some people are having with vga cards.

-- 
	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
Newsgroups: comp.unix.bsd
From: eichin@athena.mit.edu (Mark W. Eichin)
Subject: 0.1, incrementally...
Organization: Massachusetts Institute of Technology
Date: Wed, 29 Jul 1992 02:20:55 GMT

Since my 0.0 system is actually "on the air" (I can rlogin to it, ftp,
run emacs...) I've been slightly reluctant to "blow everything away"
to upgrade. Since an important reason for me to use 386bsd is to learn
even more about BSD than I already know, I made diffs of the kernels
and read things before trying it out. I built a 0.1 build tree and set
up a sufficient config file (no scsi, no ethernet, no tape, MFS but
not ISOFS, ddb, unofficial/com.cgd) and built a 0.1 kernel on the 0.0
system. It booted, then hung; turns out it needed the 0.1 init, so I
copied that in too... That booted to a (garbled, of course :-) login
prompt. Did some mknod's to fix com1 and com2 for the new driver. ps
-u dies with a floating exception, but we've seen that here before
too. 
	NFS over SLIP still hangs, but now it seems more clearly
related to silo overflow than before, so I've got something to
diagnose now :-)
				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
				Cygnus Support <eichin@cygnus.com>

Newsgroups: comp.unix.bsd
From: dealwisb@cognos.com (Brian de Alwis)
Subject: Some questions, some fixes, some suggestions
Organization: Cognos Incorporated, Ottawa CANADA
Date: Sat, 25 Jul 1992 18:23:54 GMT

I've finally installed 386bsd 0.1 (my problems were due to lack of
time though :-). I've applied whatever patches I managed to snarf from
the net, some of which I question.

	   The tty_ring patch from Mark Eichin (eichin@athena.mit.edu) in
<EICHIN.92Jul21092841@tweedledumber.mit.edu> says that the rbp and cpp
paramters to nextc() were reversed - not so in my code...

	   The new-and-improved execve() no longer accepts '#!' magic
codes... This is best demonstrated by which(1), a csh command, when
running /bin/sh. I haven't even tried doing anything with this (yet).

	   The samples for named(8), the bind server, are unfortunately no 
longer part of the distribution. I believe the should be placed back
in (unless they're included in the etc01).

How easy is it to add 720K drive support? [I haven't looked!]

And now back to fiddling...
-- 
+++BdA  Brian de Alwis. Brain on loan to Cognos Inc, Ottawa, Ontario.
	dealwisb@cognos.com, or bsdealwi@napier.{waterloo.edu,uwaterloo.ca}
	"Nine out of ten men who tried camels said they preferred women"
Newsgroups: comp.unix.bsd
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Subject: Re: Highest com port speed
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Thu, 23 Jul 1992 12:04:41 GMT

lidl@rodan.UU.NET (Kurt J. Lidl) writes:
+---------------
| It would appear that the highest data rate is what you would want
| with a V.32bis connection running with a full V.42bis compression
| rate in your modem:  57600 bps.
+---------------

Well, *I* want to be able to do (10/8)*64000 = 80000 bps, so that when
I'm talking async to an external ISDN terminal adapter I can feed it at
full speed... ;-}

Actually, does anyone know of a cheap ISDN BRI card for the ISA bus?
(Who needs terminal adapters, anyway? ;-}  )


-Rob

-----
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
From: niko@iastate.edu (Nikolaus E Schuessler)
Subject: **** Is anyone keeping track? ****
Organization: Iowa State University, Ames, IA
Distribution: usa
Date: Tue, 28 Jul 1992 15:57:35 GMT

Howdy... I've been watching this newsgroup for awhile mostly
because I've seen 386BSD in action and I hope to by a pc compatible
here soon, but I had a question:

With all the potential bugs being found, and all the fixes, is * someone *
checking to make sure that the bugs really exist, the fixes really fix,
and all the fixes make it into the * same * copy of the source and
get released together?

I don't wanna miss the fixes that work, and don't wanna put in fixes
that I don't need.

There may also be a lot of duplicate efforts here...


-- 
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: toreh@bootes.sds.no (Tore Haraldsen)
Subject: 386bsd - mt missing...
Organization: Statens Datasentral A/S, SDS, Norway
Date: Wed, 22 Jul 1992 13:49:48 GMT

In my wisdom I made me a streamer tape with bin01.* as the first tar set,
src01.* as the second, and etc01.* as the third. And I find to my dismay
that I got no way to position the tape. So, I can install the bin01 set,
but the rest is out of reach, unless

a)	somebody tells me how to create no-rewind device names, or
b)	some kind soul makes me a binary of mt (or equivalent, I only
	need to skip files).

I cannot find any (explicit) tape control support in libc.a...

Thanks a bunch, whoever helps me out!

-- Tore Haraldsen
From: mmorg@ruf.rice.edu (Matt Morgan)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 23 Jul 92 22:51:44 GMT
Organization: Rice University
X-Newsreader: Tin 1.1 PL4

lyndon@ampr.ab.ca (Lyndon Nerenberg) writes:
: 
: With the university source release of Plan 9 just around the corner
: the academic research community has an excellent opportunity to make
: their displeasure known by boycotting the software release. As much as
: I like the direction Plan 9 is going in, there is no way I could chance signing
: a license with AT&T for it (and I may be in a position to do so shortly).

I've been following the development of Plan 9 for a while, and had
eagerly anticipated a publicly available release.  However, the
position taken by AT&T in their suit against BSDI is ridiculous.
Hopefully, the case will be dismissed, if only due to the vagueness of
AT&T's claims.  However, I refuse to deal with a company that engages
in such monopolistic and unfair practices, and I will let AT&T know 
via letter the reasons for my cancellation of service.

AT&T, you have lost another customer, not just for long-distance phone
service, but for Plan 9 as well.

- Matt
--
-- Matt Morgan, Idahoan number 3 - mmorg@rice.edu - Rice U. - Houston, Texas --
][][][]][]][][][][][][[][]][[]][[][]][][][][[][]][[][][[][[[]]][][[[[[][]][]]]]
 "There is nothing right or wholesome anywhere in today's politics."
                                             - Plato (The Republic)
From: jeff@aiai.ed.ac.uk (Jeff Dalton)
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: 24 Jul 92 18:44:35 GMT
Organization: AIAI, University of Edinburgh, Scotland

In article <1992Jul22.212903.29537@gateway.novell.com> terry@npd.Novell.COM (Terry Lambert) writes:
>*** prediction alert *** prediction alert *** prediction alert ***
>
>I think that AT&T will win; not on the merits of reality, but on the merits
>of their arguments.  It will be difficult, without educating the judge to
>the point of a CS degree, to draw the distinctions necessary to prove
>non-infringement by BSDI.  It certainly *looks* like BSDI is infringing
>to a layman, and that's what the judge will be. 

I am not convinced of this.  A long time ago, UCB developed an
OS based on a system from AT&T.  That system lacked almost every
interesting thing now in BSD, including virtual memory.  Since then,
many man years of effort have gone into developing the system at
UCB.  Since all of the improvements are new, they were not based
on the AT&T code.  Finally, the last traces of AT&T code were removed.
(Presumably, UCB and co can produce a list of what these last traces
were, to show their insignificance.)

Why would this look like infringment?

However, we cannot be sure the courts will make a rational decision.

One thing that worries me is the claim of "unfair competition",
which seems to be based in part on the idea that BSDI was able
to develop a system quickly while AT&T has taken many man years
on their alternative.  Now, this is a bogus comparison, because
it leaves out all the man years of work at UCB, but suppose the
argument carries the day nonetheless.

The result may be this: anyone who takes public domain code and
produces a commercial system can be sued for unfair competition
by anyone who started from scratch.  Indeed, people who distribute
free systems might be sued.  So much for ___ (fill in favorite
source of free software) ___.

(NB -- my statements about AT&T's case are based entriely on
what I've read in this newsgroup.  I could easily be wrong.)

-- jd
From: adam@soda.berkeley.edu (Adam J Richter)
Newsgroups: comp.unix.bsd
Subject: Copyright infringement added to AT&T suit?
Date: 30 Jul 1992 21:22:25 GMT
Organization: University of California, Berkeley
NNTP-Posting-Host: soda.berkeley.edu


        On Tuesday, I had a telephone conversation with Larry Lankel
of USL yesterday.  Larry told me that AT&T is indeed the majority
shareholder of USL.  Therefore, it is reasonable to pressure
AT&T to change USL's actions.

        Larry claimed that USL has added copyright infringement
to the lawsuit and that USL has found "specific and substantive"
sections of code that "were copied or could not have been written
without looking at the [USL] source code."  However, Larry also told
me that USL will not reveal which sections of the BSD Net 2 code that
it claims to be able to restrict.

	It seems to me that even if the the dubious claim that a section
of code could not have been written without looking at the original were
found to be true that that would necessarily establish copyright
infringement.  For example, either of the following might be defenses
against such a copyright infringement claim:

                1. "We had to look at the code to copy some of
                    the ideas, but we did not copy the expression."

                2. "The expression and functionality were inseparably
		    interwined and there was only a limited number of
		    ways to implement this functionality."

        I am not a lawyer.  This is just my layman's understanding of
the law; it is not legal advice.  For legal advice, consult a lawyer.

	If some enterprising person would like to make AT&T's filings
available for anonymous FTP, the copy department of the US district
court in New Jersey can be reached at (201) 645-4565 until 4:30pm on
weekdays.

-- 
Adam J. Richter				409 Evelyn Avenue, Apt. 312
richter@cerf.net			Albany, CA 94706
					(510)528-3209
Another member of the League for Programming Freedom (league@prep.ai.mit.edu).
From: michael@resonex.com (Michael Bryan)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 21 Jul 92 12:25:30 GMT
Organization: Resonex Inc., Sunnyvale CA

How long has the NET2 distribution (and other AT&T-void sources) been
available?  If this is indeed the first legal action that AT&T/USL has
taken, perhaps a point in BSDI's favor is that AT&T has waited until
now to protest.  The NET2 distribution was no secret, nor were the
various projects which are based upon it (especially Jolitz's 386BSD
and BSDI's BSD/386).

It obviously reeks of someone saying "Omigawd, these BSD systems are
actually becoming popular, and we might lose our stranglehold!  Quick,
do something!"  I certainly hope that the courts tell them where they
can stuff it.

Of course, I don't have a lot of faith in our legal system's ability
to do sensible things in the realm of software...

-- 
Michael Bryan        michael@resonex.com                     |     ,_,
"Pretenders I meet are making a trail along the way.         |    /oo \
They say that they know how to show me a path to guide my    |    <>__|
way to truth..." --- David York, "The Quiet of a Candle"     |    |  U|
From: rjs@crs.cl.msu.edu (Robert J. Stanton)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1 Boot and Video Problems
Keywords: 386BSD
Date: 30 Jul 92 01:01:00 GMT
Distribution: comp.unix.bsd
Organization: Michigan State University

I have  installed the 386BSD stuff from  the boot
floppy and am impressed and   ready  for  more.

I am having two problems:

1)  I have a 105Mg  HD and want a  16 Meg partition
    for DOS 5.0.  When I partition the  disk this
    way, it always boots into DOS, even though I
    use   fdisk  to make  the BSD partition
    active.  Any clues  on how  to fix this?

2)  When I  use  "nn" or   use   more on the
    INSTALL  notes, I get blinking text
    instead of highlighted text.

Any help will be appreciated.

Also, I wish that the cursor did not flash so
rapidly.

rjs@crs.cl.msu.edu

Did the  comp.os.386bsd  ever  get started ?

Still  impressed
From: mm@mentor.cc.purdue.edu (Mike MacKenzie)
Newsgroups: comp.unix.bsd
Subject: Re: What kind of tape is OK w/ 386BSD?
Summary: Wangtek 5150ES doesn't stream
Date: 30 Jul 92 20:14:37 GMT
Organization: Purdue University

In article <1992Jul29.161438.6372@mks.com>, fredw@mks.com (Fred Walter) writes:
> 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 :
> 

I have a Wangtek 5150ES SCSI-36 tape drive and it works, but slowly.
It took over 12 hours to back up ~80 meg.  I've tried various buffer
sizes with dd with no improvment.


Michael MacKenzie	(Purdue University Unix Group)
mm@mentor.cc.purdue.edu
Xref: sparky comp.unix.bsd:2736 can.general:3404
From: lyndon@ampr.ab.ca (Lyndon Nerenberg)
Newsgroups: comp.unix.bsd,can.general
Subject: Re: AT&T sues BSDI & Our Retaliation
Date: 24 Jul 92 01:31:55 GMT
Followup-To: comp.unix.bsd
Organization: Boycott AT&T!

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.

> What I am going to do, and I believe others should as well, if they wish
> to be heard, is to write a letter to the AT&T regional manager, or someone
> of higher authority, explaining to that individual that you are aware of
> the current 'tactics' that AT&T is using to monopolize the UNIX-type operating
> system market.

You are correct, and I wasn't clear enough about emphasising the second
point. In my example it is necessary that Cantel be made very aware,
at a management level, that I won't contribute to AT&T revenues, and
why I won't do so. It's also important that Cantel management realize
that they too stand to loose money due to this boycott. If enough of
us voice our opinions on this, there is a chance (and only a chance)
that Cantel will let AT&T know that a portion of their (Cantel's)
customer base is pissed off enough at AT&T to take action.

It's only a drop in the bucket, but a few million here and a few
million there and suddenly your talking about real money :-)

--lyndon
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: 386BSD 0.1 & Com ports
Date: Mon, 27 Jul 92 09:04:52 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Keywords: com tip ttys remote

In article <sxjcb.37.711773132@skyfire.uacn.alaska.edu> sxjcb@skyfire.uacn.alaska.edu (Jay C. Beavers) writes:
>I've been trying to use tip to talk to both a line driver or a modem on com2 
>and I've had no end of trouble.  My hardware setup worked under Dos and 
>worked using the TinyBSD boot disk and basic distribution on the hard drive, 
>but once I loaded BIN01, trouble started.

    You might look in /usr/386bsd.errata.  Not having crypt might be
    part of the problem.  Unfortunately, I haven't been able to figure
    out how to get crypt on my system because mread hasn't worked since
    bin01 was installed... 
    -Andrew Moore <alm@netcom.com>
From: lyndon@ampr.ab.ca (Lyndon Nerenberg)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs BSDI: email address?
Summary: Put it on PAPER!
Date: 24 Jul 92 18:56:19 GMT
Organization: Boycott AT&T!

Sean.Levy@cs.cmu.edu writes:

> Is there an email address inside AT&T to which complaints (as opposed to
> termcaps :-) can be sent re their suit?

A basic rule of business computer usage: the higher up in management a
person is, the less likely they are to soil their fingers on a keyboard.

If you want to let AT&T/USL know how you feel, write a letter (on PAPER)
and send it (reggistered) to the CEO's of AT&T and USL (addresses posted
elsewhere in this group). Make sure you send copies to the trade rags as
well (Unix World, Open Systems Today, Computer Reseller, Sun Expert, Unix
Review, etc.). If enough of us boycott AT&T it might make a (very) small
impact. If we start shitting on them in the press they will sit up and
take notice.
Xref: sparky comp.unix.bsd:2675 can.general:3379