HDTenEightyP/NetNews huggingface dataset:
From: lancelot@spock.uucp (Thor Lancelot Simon)
Subject: Re: BSDI/USL Lawsuit -- More Bad News for Human Beings...
Organization: Choate Rosemary Hall
Date: Fri, 22 Jan 1993 00:59:10 GMT

In article <1993Jan15.223746.24608@fnbc.com> jja@fnbc.com (Joseph Alotta) writes:
>
>since i don't know anything about operating systems,
>perhaps i can get a cushy job writing one now.
>
>that makes me100% uncontaminated by any knowledge
>of my subject matter.
>
>are you listening usl?
>
>joe.

I can do you one better.  I've had access to AT&T Unix sources for at least four
years.  I've examined fairly closely, and at times modified, bits-n-pieces of
the V7 and 32V kernel source.  I've also worked with the 4.3 kernel guts, though
not as much.  However:

I'm a minor.  So I'm not bound by any contractual obligation, to AT&T or anyone
else.  If USL is still working on the trade-secret angle in their lawsuit, I
or others like me will, once we hit the mainstream of the computer industry,
be exactly the type of legal conduit for information that removes trade-secret
protection.  I doubt that USL has the legal resources to fight with the common
law...

-- 
*******************************************************************************
*Thor Simon             * Okay, just a little pin-prick...There'll be no more-*
*tls@panix.COM          * Aieeeeaaaugh!-but you may feel a little _sick_.     *
*tls@spock.UUCP         *   ---Pink Floyd                                     *
*******************************************************************************
From: richard@castle.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] automatic bootup
Keywords: bootup
Date: 25 Jan 93 14:32:45 GMT
Organization: Edinburgh University

In article <g88d4938.44.727626263@giraffe.ru.ac.za> g88d4938@giraffe.ru.ac.za (MR GE DOYLE) writes:

>   b)  ./.X11: no such file or directory

This is due to find deleting the directory and then trying to chdir to it...

-- Richard
Newsgroups: comp.unix.bsd,comp.periphs.scsi
From: kamil@alumni.cs.colorado.edu (Kamil Maheshwari)
Subject: Best Bargain for a SCSI Host Adapter Board for a DOS PC ??
Organization: University of Colorado, Boulder
Date: Thu, 21 Jan 1993 16:53:33 GMT


---------------------------------------------------------------------
Hi Y'all,

I am interested in finding out the BEST bargain (most bang for the buck)
SCSI Host Adpater Board for a DOS/PC. Please let me know if you have a
compiled list, or if you have any favorites. Money IS a concern along
with future expandability and flexibility. E-mail works best for me.

thanks gang. kamil@alumni.cs.colorado.edu
---------------------------------------------------------------------
Newsgroups: comp.unix.bsd,alt.sources
From: gary@sci34hub.sci.com (Gary Heston)
Subject: Re: BSDI/USL Lawsuit -- More Bad News for Human Beings...
Reply-To: gary@sci34hub.sci.com (Gary Heston)
Organization: SCI Systems, Inc., Huntsville, Al.
Date: Thu, 28 Jan 1993 18:45:51 GMT

In article <1993Jan28.050526.22773@unislc.uucp> erc@unislc.uucp (Ed Carp) writes:
>Thor Lancelot Simon (lancelot@spock.uucp) wrote:

   [ has had source access, but... ]
>: I'm a minor.  So I'm not bound by any contractual obligation, to AT&T or anyone
>: else.  If USL is still working on the trade-secret angle in their lawsuit, I
>: or others like me will, once we hit the mainstream of the computer industry,
>: be exactly the type of legal conduit for information that removes trade-secret
>: protection.  I doubt that USL has the legal resources to fight with the common
>: law...

I doubt Thor has a clue as to the pigheadedness of AT&T/USLs' legal staff,
and their willingness to squander millions trying to ruin someone on the
other side of a lawsuit. Common law won't stand a chance without $10 million
or so to support it.

>The problem with that is that whoever gave you access to the source can be sued
>(and successfully, I might add) for giving you such access, because you are not
>an adult, and cannot enter into a legal binding contract - this is a clear
>violation of the AT&T licensing agreement.

Based on this rational, AT&T/USL shouldn't have issued a source license
to a educational institution; virtually every student falls under the 
classification of "minor". Unless the agreement specifically prohibited 
access by students, that's tacit approval of a non-enforcable situation.
I'm sure the schools' lawyers would have a field day with that...

-- 
Gary Heston    SCI Systems, Inc.  gary@sci34hub.sci.com   site admin
The Chairman of the Board and the CFO speak for SCI. I'm neither.
Windows NT documentation: "Command to change password    CTL-ALT-DEL"
Newsgroups: comp.unix.bsd
From: msmith@beta.tricity.wsu.edu (Dragon Lord)
Subject: [386BSD] 3com ethernet cards
Organization: Washington State University Tri-Cities, Richland
Date: Sat, 23 Jan 93 05:26:40 GMT

I'm looking at the prices on the 3COM Etherlink III 3C509 cards.

Questions.

Has anybody tried them with 386BSD?   

How well do the work?

Mark
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: new scsi tape driver for the brave hearted
Organization: Trw Financial Systems
Date: Thu, 28 Jan 1993 07:19:57 GMT

This is anouncing an 'alpha test' of some changes to the scsi system
I'm looking for guinea pigs.

I have rewritten parts of the scsi tape driver
it's available in
ref.tfs.com:/usr/src/sys.extras/julian-scsi/scsi

you'll probably need new copies of the other files in that directory too.

I'd like some brave souls to try it out on fixed record length
tape drives as I only have the variable type.

main changes are:

better handling of end of file (filemark handling on read)
better handling of variable record size.
some minor numbers should push some drives into differnt densities
hopefilly better handling of some 'silly' drives
  (but this isn't completed yet).. eventually
  this will be run-time configurable with an ioctl interface.


Also for the brave..
sd.c has been changed so that if your drive doesn't support
the geometry inquiry, it uses a ficticious one.
Also has a better default disklabel for unlabeled drives.

I only suggest this for people already running my scsi system.
The rest of the system should remain compatible

hey maybe you want to try the new scsiconf.c too
(takes a config variable SCSI_DELAY in seconds form the config
file if you need to wait for a slow device to wake up on boot)
(also probes faster)

remember
this is only for experienced scsi hackers or people 
desperate to get a new device working..

Also see the new ultrastore 14f driver support
First release anywhere!
Be the second person in the world to run a 14f under 386bsd!
(real adventurers only) (i386/isa/ultra14f.c)

(if you're an experienced kernel hacker with scsi experience
who wants a chalenge.. I have a tmc1670 driver 99.5% working..
apply within..)


julian
+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\
	  v


Xref: sparky comp.unix.bsd:11772 comp.unix.wizards:5634 gnu.misc.discuss:4622
From: tzs@stein.u.washington.edu (Tim Smith)
Newsgroups: comp.unix.bsd,comp.unix.wizards,gnu.misc.discuss
Subject: Re: ENOUGH! Re: BSDI/USL Lawsuit -- More Bad News for Human Beings...
Date: 24 Jan 1993 09:21:37 GMT
Organization: University of Washington School of Law, Class of '95
NNTP-Posting-Host: stein.u.washington.edu

boyd@prl.dec.com (Boyd Roberts) writes:
>>  * vi (eek - but better than ed)	BSD
>
>rob pike's jim & sam
>

Amusing but irrelevant comment: Pike wrote these editors after the following
statement: "Everybody writes an editor.  It's easy to do and makes them feel
important.  Tell them to work on something useful."

Those of us that this comment was about (a couple of people at Caltech who
got involved in a "I could write a better editor than you" "Oh no you can't,
I can" match, and then spent the night at terminals across the room writing
editors and shouting out to each other what features they had just added)
were quite amused when, a couple of months later, Pike started working on
jim!

--Tim Smith
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: HELP! What do I need?
Organization: Weber State University  (Ogden, UT)
Date: Sun, 24 Jan 93 01:24:59 GMT

In article <7111@tuegate.tue.nl> ramon@blade.stack.urc.tue.nl (Ramon Kolb) writes:
>I want to buy a computer and run UNIX on it. The unix I'm gonna run must be
>nice and stable. I consider taking BSD386 as it is in public domain now, 
                                    ^^^^^^
				    BSD/386?!?

I think you mean 386BSD.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: poirot@aio.jsc.nasa.gov (Daniel T. Poirot/LESC)
Subject: Re: floating point exceptions (DBL_MIN DBL_MAX)
Keywords: signal 6, gcc2.3.3
Organization: NASA Johnson Space Center
Date: Tue, 26 Jan 1993 14:36:46 GMT

In article <31080@toad.com> curt@toad.com (Curt Mayer) writes:
>alright, so i reinstalled from ground zero for the 4th time, installed
>the latest patch kit from agate, recompiled the world, so why do i
>still get these signal 6's all over the place when trying to recompile ?

The problem is in DBL_MAX and DBL_MIN in /usr/include/float.h.  I
changed them to:

#define DBL_MIN         2.2250738585072014E-308
#define DBL_MAX         1.7976931348623157E+308

and STILL got 'signal 6's all over the place' (particularly in
recompiling g++).  I then changed DBL_MAX to 1.7976931348623147E+308
(note second to last digit) and had better luck.

I would really like to see a definitive answer on this and see it fixed
in the distribution files or patchkit.

-- 
Daniel Poirot           poirot@aio.jsc.nasa.gov
NASA JSC                "The mind is a terrible thing."
ER3                     tel: (713)483-8793
Houston, TX 77058       fax: (713)483-3204
Newsgroups: comp.unix.bsd
From: scott@pita.cns.ucla.edu (Scott Burris)
Subject: Re: Where can I pick up the FAQ from?
Date: 27 Jan 93 13:53:41 PST

migieger@delos.stgt.sub.org (Michael Giegerich) writes:

>Hi,

>>You might find the FAQ and BUGLIST (really an FAQ) on agate:
>>anon ftp agate.berkeley.edu; ~/pub/386BSD/386bsd-0.1/unofficial/{*FAQ,*BUGLIST}

>I wonder what could be the reason to keep the FAQ and the BUGLIST
>(and BTW, the patch-kit) "hidden" on agate.berkeley.edu; this
>forces many people without access to ftp-connections asking the
>same questions again and again...

>Any hints?

>(And YES, I would appreciate seeing those files among the other
>tons of FAQs, BUGLISTs e.a. in a news.group).


For those of you wanting to easily get the FAQ and buglist via Email,
send a message to:

	386bsdfaq@pita.cns.ucla.edu

	or

	386bsdbuglist@pita.cns.ucla.edu

The subject and content are not important.  The software which will return
the file to you is rather simpleminded, but as long as the headers in the
message aren't too badly munged, you should get a reply back.  You will
likely get several messages back, as the files get split into parts, each
no more than about 17K.

-- 
----------
Scott Burris
UCLA Campus Network Services
cnetslb@oac.ucla.edu (310) 206-4860 - OR - scott@pita.cns.ucla.edu
Newsgroups: comp.unix.bsd
From: dmuntz@quip.eecs.umich.edu (Dan Muntz)
Subject: [386BSD] RT 4-port patch for cgd's com.c
Organization: University of Michigan EECS Dept., Ann Arbor, MI
Date: Tue, 26 Jan 1993 16:47:18 GMT


Here is the patch to apply to the latest com.c from cgd to add support
for the RT 4-port serial card.  This patch fixes a small bug in the
previous one which isn't evident when the 4-port card is used in conjunction
with a standard pc serial card.  When the 4-port card is the only card
in the system, it must be configured as ports 0-3.  This may also apply
to standard serial cards, but I haven't tested this (i.e., it seems necessary
to have an actual device at com00 (maj. 8 min. 0) for higher ports to work).
My kernel configuration for the RT card looks like this:

device          com0    at isa? port 0x1230 tty irq 10 vector comintr
device          com1    at isa? port 0x1238 tty irq 10 vector comintr
device          com2    at isa? port 0x1240 tty irq 10 vector comintr
device          com3    at isa? port 0x1248 tty irq 10 vector comintr

  -Dan
   dmuntz@eecs.umich.edu

*** /usr/sys/i386/isa/com.c.cgd	Tue Jan 26 11:31:15 1993
--- /usr/sys/i386/isa/com.c	Tue Jan 26 11:32:44 1993
***************
*** 163,168 ****
--- 163,185 ----
  int comprobe(dev)
  struct isa_device *dev;
  {
+ 	/* reset interrupts if we're an RT card (only once per card) */
+ 	if ((dev->id_iobase >= 0x1230) && 
+ 		((dev->id_iobase & 0x00000fff) == 0x00000230)) {
+ 		switch (ffs(dev->id_irq)-1) {
+ 			case  9: outb(0x2f2,0); 
+ 				 printf("resetting irq 9\n"); 
+ 				 break;
+ 			case 10: outb(0x6f2,0);
+ 				 printf("resetting irq 10\n");
+ 				 break;
+ 			case 11: outb(0x6f3,0);
+ 				 printf("resetting irq 11\n");
+ 				 break;
+ 			default: printf("irq unsupported by RT card\n");
+ 		}
+ 	}
+ 
  	/* force access to id reg */
  	outb(dev->id_iobase+com_cfcr, 0);
  	outb(dev->id_iobase+com_iir, 0);
***************
*** 575,580 ****
--- 592,605 ----
  	register int i,j;
  	register u_char code;
  	register char possiblymoreirqs;
+ 
+ 	/* reset interrupt 9,10,11 if that's the origin of this one */
+ 	switch (ffs(com_irq[unit])-1) {
+ 		case  9: outb(0x2f2,0); break;
+ 		case 10: outb(0x6f2,0); break;
+ 		case 11: outb(0x6f3,0); break;
+ 		default: ;
+ 	}
  
  /* printf ("%d\n",unit); XXX */
  	do {
From: jvaisane@snakemail.hut.fi (Jukka V{is{nen)
Newsgroups: comp.unix.bsd
Subject: NE2000 kernel - anywhere?
Date: 26 Jan 93 15:21:21 GMT
Organization: Helsinki University of Technology, Finland
Distribution: comp
NNTP-Posting-Host: lk-hp-7.hut.fi


I've been setting up a 386BSD system and it works fine except it has the
'startart' thingy. The FAQ says: remake kernel. Well I don't have the
the diskspace to remake the thing and the kernel I now use was FTP:d w/o
sources (someone had fixed it work with NE2000). Now I'd like to know if
there is a bin-distribution kernel somewhere that can handle the NE2000.

jvaisane@snakemail.hut.fi

please, if you reply via mail, send a cc: to hhelanto@vipunen.hut.fi
--

-------------------------------------------------------------------------------

	Oh all right! Who stole my .signature file! I'll get ya...

-------------------------------------------------------------------------------
From: paul@isl.cf.ac.uk (Paul)
Newsgroups: comp.unix.bsd
Subject: 386BSD: Assorted questions
Date: 27 Jan 93 17:34:35 GMT
Organization: Intelligent Systems Lab, ELSYM, Universiity of Wales, College of 
              Cardiff.


I've restructured my source tree after re-installing the sources for the
pacthkit and I've got a few queries.

Firstly, I've moved games, etc and share from othersrc to their proper
place in /usr/src -- I just prefer it that way.

I then tried to do a make clean from /usr/src to see if everything was
as it should be and I found a few anomalies.

Firstly -- in /usr/src/usr.bin/groff the makefile references a sub-dir
grotty which doesn't exist.

Secondly -- in /usr/src/usr.bin/tn3270/api/makefile there's a reference
to 386bsd.lib.mk. This doesn't exist, I assume it should just be
bsd.lib.mk

Thirdly -- in /usr/src/share/doc/smm/Makefile there's an entry for the
10.newsop directory in SUBDIR. This dir only contains one file tmac.n
so obviously the makefile recursion fails. What is this tmac.n anyway?

Ok, so the above are a little petty but I was having a bit of a tidy up
and I just felt they were loose ends. Is there anyone bored enough to
tell what the above are?


On another note:

I noticed when running make clean that the makefiles still try and
remove core files. I've been wondering for some time if there was
a way of cleaning the system of core files. On a SUN I just run a find
job but of course with the new core.filename system this doesn't work.

Anyone have any solutions to this problem. When did the new
core.filename system get introduced since the makefiles haven't
been modified to take account of the changes.
-- 
  Paul Richards, University of Wales, College Cardiff

  JANET:paul@uk.ac.cf.isl	Internet:paul@isl.cf.ac.uk
  UUCP: paul@cf-isl.UUCP or ...!uunet!mcsun!uknet!cf!isl!paul
From: fn@waldorf.informatik.uni-dortmund.de (Frank Nobis)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Problem with Wangtek tape
Date: 28 Jan 1993 13:50:28 GMT
Organization: CS Department, Dortmund University, Germany
NNTP-Posting-Host: waldorf.informatik.uni-dortmund.de
Keywords: 386BSD, tape

Hi there

I have a problem with my tape. When creating a backup with tar a verify fails.
Tar tells me 'tar: Skipping to next file header' a few times and then stops
with 
an unexpected EOF.

I created a big tar image on disk and copied it with dd if=image of=/dev/rwt0.
This can be read from tar. Cpio works correct, too.

Has somebody a hint for this bug?

regards
       Frank
-- 
  Frank Nobis                     fn@irb.informatik.uni-dortmund.de
  Univ. Dortmund, IRB             Tel. +49 231 755 2106
  Postfach 500500  
  D-4600 Dortmund 
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
From: dmw@teal.csn.org (Dave Warner)
Subject: Re: ATI Mach32 and Xfree86 or XS3?
Organization: Colorado SuperNet, Inc.
Date: Thu, 28 Jan 1993 14:34:27 GMT

news@csi.compuserve.com (Usenet News) writes:

>In article <1993Jan26.162704.13442@usasoc.soc.mil> ted@usasoc.soc.mil (Mr. Ted Nolan) writes:
>>Hello folks,
>>
>>I'm plugging along in my quest to spec out a nice 486 system to get and
>>run 386BSD and X on.  I've seen a few advertisements for the ATI Mach32
>>video card.  It seems this is a local bus card that can do 1024x1280 in
>>256 color mode.  Does anyone know if this has an S3 or ET4000 chipset?
>>Can you run X on it?
>>

>Ted,

>The Mach32 IS the "chipset".  It serves the same functions as the S3 although
>considerably faster.  I'm hoping someone will post an X driver for the Mach32
>so I can justify getting an ATI Ultra Plus (This is an unabashed hint to all
>386BSD System programmers with ATI Ultra Plus's)

>-Rell
	The following are xbench results on the same hardware for
	both Xfree and Kevin Martin's X8514 on linux -- I don't know
	if there's an X8514 version for 386BSD.


==================================
Gateway 2000 4DX2-66V, 8Mb
ATI Ultra Pro, 68MHz, local bus
Xfree1.1, no tcp
Linux0.99.1, 1024x768
==================================
TOTAL    193536 lineStones
TOTAL     22459 fillStones
TOTAL     10049 blitStones
TOTAL   4052466 arcStones
TOTAL    212437 textStones
TOTAL     24836 complexStones
TOTAL     31045 xStones

==================================
Gateway 2000 4DX2-66V, 8Mb
ATI Ultra Pro, 62MHz, local bus
X8514, no tcp
Linux0.99.1, 1024x768
==================================
TOTAL    185822 lineStones
TOTAL     55528 fillStones
TOTAL     36191 blitStones
TOTAL   5236912 arcStones
TOTAL    134406 textStones
TOTAL     92614 complexStones
TOTAL     79209 xStones

dave
-- 

| Dave Warner            | e-mail: dmw@csn.org |
| 151 Sky Trail Road     | USWest: 443-9589    |
| Boulder, CO 80302      |    FAX: 443-6791    |
Newsgroups: comp.unix.bsd
From: osynw@gemini.oscs.montana.edu (Nate Williams)
Subject: Re: [386bsd] com-beta.tar.Z installation problems
Keywords: com-beta.tar.Z bidirectional comdrivern
Organization: Montana State University
Date: Sat, 23 Jan 1993 00:49:34 GMT

In article <fYjR1dj@quack.sac.ca.us> dfox@quack.sac.ca.us (David Fox) writes:
>
>I'm having some problems installing cgd's com driver.  Apparently due to
>the inconsistencies (possibly?) between patchkit 0.1, which I have, and
>patchkit 0.2, which I don't have, and apparently can't get yet), the
>patch for com.c doesn't go all the way through.

Hmm, looking at the new patchkit, I don't remember any new patches to
com.c ...... Oh, maybe it's the slip fix that was screwed up in the 
original version.

I could email you the patch, but I am going to release the new patchkit
at the end of this weekend. (Barring any large bugs) When I do that, it
would be a pain to back out a new com.c with the old patchkit installed.

Wait a couple more days, and everything should be on the up and up.

Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home. 
work: (406) 994-5991         |  Keeper of the Unofficial 386BSD Bug Report
home: (406) 586-0579         |  Please send bugs and/or fixes you find.
Newsgroups: comp.unix.bsd
From: murrayc@hansford.com (Charles H. Murray)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] boot disk does absolutely nothing on gateway 4dx33v
Date: Thu, 21 Jan 93 20:23:46 -0700
Organization: The Hansford Group - Contract Software Engineering and Consulting

In <1jkdpeINNkeg@cat.cis.Brown.EDU> tim@news.Brown.EDU (Timothy Miller) writes:
>I have acquired the boot disk image for 386bsd, and no matter what I try,
>when my system starts up, it displays all the bios messages, and then hangs
>with the floppy drive light on.

>My system is a Gateway 2000 4DX-33V with the ATI ultra pro VESA card, 8M of
>memory, the gateway 124 (?not sure of exact #) keyboard, and otherwise 
>basically standard settings (one 340M IDE hard drive, no SCSI, no ethernet,
>no funny other cards).

I would be VERY interested in the answer to this as this is the system
I want to purchase for running 386BSD.  I would probably go with SCSI for
the disk though.

Timothy, if you get info via mail, either post it or send it to me, as I
want to make my purchase fairly soon.


-- 
Charles H. Murray
Software Engineering Consultant         "On assignment at IBM in
Breckenridge, Colorado USA               Research Triangle Park
murrayc@hansford.com                     North Carolina USA"