HDTenEightyP/NetNews huggingface dataset:
From: engel@opal.cs.tu-berlin.de (Christian Engel)
Subject: 386BSD 0.1 success and tape problem
Summary: error reading tapes, resid: 10240
Keywords: 386BSD, SCSI-Tape
Organization: Techn. University of Berlin, Germany
Date: Fri, 31 Jul 1992 15:03:11 GMT

Hi out there,

I got the 386BSD0.1 working on my system. I have two problems.

Here is the system configuration :

	486/33MHz - 256KB Cache
	16 MB RAM
	ET4000/1MB VGA card
	AT-IO
	ADAPTEC 1542B
	SCSI Drive 0 : 330 MB Wren
	SCSI Drive 1 : 660 MB Wren
	SCSI Tape  2 : Wangtek 5150 ES

I had no problems installing the system on my harddisk(s). 
I built a new kernel with the lp.c driver for the printer which was 
contributed to the 386BSD-0.0. I attached a terminal to com1 and everything
worked fine up until this point.
I installed the previously posted kmem-patch (problem occurred).

I can write tapes without any problems. I am even able to read these tapes. 
By the way there are no speed problems, writing to and reading from tape
works with reasonable speed.

But I run into trouble trying to read tapes from a SUN (gnu-tar) and from 
another 486 machine with ISC-UNIX (SysV-ISC tar). 386BSD-0.1 shows the 
following behaviours:

1) SUN tape: (command: tar -xvf /dev/ras2a)
	- tape begins to run but does not read any input. After a while the
	system stops with resid: 10240 error

2) ISC tape: (same command as above)
	- system reads about 40 MBytes from the tape. Then it stops with
	an error message and resid: 10240 error


Has anyone out there any ideas ? Unfortunately I have no manuals for the
Adaptec controller so I cannot try to fix it by myself.


:::::::::::
2nd Problem
:::::::::::

When I built a new kernel, I normally try to copy it to the root directory
using a name, that doesn't exist in the root directory. 
Sometimes the system just stops execution while copying. 
No message is printed.
After a restart 
and the file system repair, you can see that a file was created but that its 
length is zero.

Any ideas or similar problems ?


--
------------------------------------------------------------------------
Christian Engel, TU-Berlin 	             mail: engel@cs.tu-berlin.de
TFS, dept of theoretical computer science,  formal specifications
address:   TU-Berlin, FR6-1, Franklinstr. 28/29, 1000 Berlin 10, Germany
Newsgroups: comp.unix.bsd
From: jsr@dexter.mi.org (Jay S. Rouman)
Subject: Re: AT&T sues BSDI
Organization: Private System, Mt. Pleasant, MI, USA
Date: Fri, 24 Jul 1992 16:14:44 GMT

In article <1992Jul24.004536@eklektix.com> rcd@raven.eklektix.com (Dick Dunn) writes:
>redistributing it.  I don't claim I understand it; all I'm saying is that
>it *appears* they don't want to restrict Net 2 _per_se_.

People interested in the "why" of this situation might want to read
the article by Gary Andrew Poole in the August _UnixWorld_.  The piece
begins, "Roel Pieper, president and CEO of UNIX System Laboratories,
Inc., doesn't care about the UNIX community's past.  He just wants to
make money."  Although written before the BSDI lawsuit began, the
article gives some good insight into the thought processes and
attitudes at USL.
-- 
Jay S. Rouman  (jsr@dexter.mi.org)
From: sand@milton.u.washington.edu (Derek Upham)
Newsgroups: comp.unix.bsd
Subject: 386BSD: Dinky little socket(?) bug -- ^V as escape character?
Date: 30 Jul 92 00:07:20 GMT
Organization: University of Washington

I've noticed the following problem while running "screen" on 386BSD
(both of these from the vanilla bin01 and etc01 sources): control-v
needs to be typed twice for it to be received by a process.  For
example, under tcsh, the key sequence

        echo ^V^G

which should enter a literal ^G (BEL, 0x7) on the command line, simply
beeps.  Similarly, "^V^B", which should enter a literal ^B (0x2),
moves the cursor back one space.  Both of these DO work correctly when
you type two ^V characters instead of one.  Inserting some suitable
printf's in "screen" indicates that the problem occurs before the data
stream reaches the program---somewhere in the pty or socket code,
looks like.  Anyone else noticed this problem?

Derek

-- 
Derek Lynn Upham                                     University of Washington
sand@u.washington.edu                University Computing Services Operations
=============================================================================
"Ha!  Your Leaping Tiger Kung Fu is no match for my Frightened Piglet Style!"
Newsgroups: comp.unix.bsd
From: eichin@athena.mit.edu (Mark W. Eichin)
Subject: Re: Some questions, some fixes, some suggestions
Organization: Massachusetts Institute of Technology
Date: Sat, 25 Jul 1992 23:14:05 GMT

According to dealwisb@cognos.com (Brian de Alwis):
>>	   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...
	On closer inspection, it appears that rather than changing
nextc, all of the *uses* of nextc were changed. If you look at
tty_ring.c, all of the ring buffer ops consistently take a struct
ringb* as the "last" argument. In 0.0, all uses of nextc passed the
ringb as the first argument, probably because someone read the order
of the argument declarations in the definition of nextc...
	For clarity, I'd still suggest that line 83 be changed from:
		nextc(cpp, rbp) struct ringb *rbp; char **cpp; {
to
		nextc(cpp, rbp) char **cpp; struct ringb *rbp; {
so that people are less confused by it; there have been C compilers
that got the argument handling wrong if the order didn't match, though
the compiler you'd be using to compile this isn't one of them.
	(Thanks for pointing this out and getting me to look at it
further. I still want to know why line 25 says " * NOT MAKE USE THIS
WORK."  instead of "* NOT MAKE USE OF THIS WORK." as it did in 0.0...
and the reference in 2.12 of terry@npd.Novell.COM (Terry Lambert)'s
unofficial FAQ should probably be elided. The tty problems aluded to
there are from some other source.)

				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
From: mm@mentor.cc.purdue.edu (Mike MacKenzie)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Summary: We can stop using AT&T as a long distance carrier.
Keywords: BSDI AT&T
Date: 21 Jul 92 17:20:07 GMT
Organization: Purdue University

In article <1992Jul20.211811.3152@algor2.algorists.com>, jeffrey@algor2.algorists.com (Jeffrey Kegler) writes:
> According to today's _ComputerWorld_ (July 20, 1992, page 16) AT&T's
> USL has sued Berkeley Software Design, Inc. in U.S. District Court in
> NJ.  Copyright and patent infringement are apparently *not* involved,
> the grounds being specified as "trademark infringement, false
> advertizing and unfair competition."
> 


AT&T can do this, and I can stop using them as my long distance carrier.
Also, when I need a new cordless phone, Panasonic & Sony make fine
cordless phones.
The 386bsd INSTALL.NOTES claims about 100,000 sites.  If every site were
to switch to MCI or Sprint, would AT&T notice?


Michael MacKenzie	(Purdue University Unix Group)
mm@mentor.cc.purdue.edu
From: terry@npd.Novell.COM (Terry Lambert)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 27 Jul 92 21:36:57 GMT
Organization: Novell NPD -- Sandy, UT

In article <1992Jul27.193757.3628@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>In article <1992Jul27.164228.28312@gateway.novell.com> terry@npd.Novell.COM (Terry Lambert) writes:
>>1)	SysVr3.x has got to be SVR3.2 or later.  It didn't include streams
>>	prior to that.
>
>Some platforms had STREAMS as early as SysVr3.0.

They were either retrofits of non-AT&T code (like SCO and Unisys' use of
the Lachman code), or other independant developement.  *None* of my source
tapes from AT&T prior to SVR3.2 show streams source from AT&T.  If you are
referring to non-AT&T streams, then it still isn't AT&T encumbered.

>>2)	OSF has licensed Mentat streams for inclusion, not AT&T.  The code
>>	is un-AT&T-encumbered, and runs on many diverse platforms (for
>>	instance, it also runs on VMS).
>
>That's nice.  They also bought a SysVr3.x license, about three or four years
>ago, and the code they are shipping as "OSF/1," for both the macro- and
>micro-kernel stuff, still requires a USL source license, if you want source.

But not for the streams.  The OSF/1 (supposedly available in August) of OSF/1
for the HP PA/RISC boxes uses Mentat, as does HP/UX 9.0, available in October.
The AT&T encumberance here is the "shell", which pretends it's SVR4.

>>3)	OSF/2 is the beast of interest, and it is based on Mach 3.0.
>
>OSF/2 does not exist, nor is there any guarantee from OSF that they will
>ever ship a Mach3.0-based system.

I've heard from some very reliable sources that it's currently in the process
of being ported to several well-known platforms, and have been offered beta
code, if I wanted it.  That aside, there is no "guarantee" from OSF to provide
any code whatsoever, just as there is no "guarantee" of SVR4.3 being released
to the general public by AT&T... still, I wouldn't bet against it, unless I
had some sort of inside knowledge to that effect not available to me currently.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
Newsgroups: comp.unix.bsd
From: bambi@bu.oz.au (David J. Hughes)
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: ITS, Bond University
Date: Wed, 22 Jul 1992 01:14:39 GMT

merlin@neuro.usc.edu (merlin) writes:

>The bottom line is that AT&T claims NET2 is contaminated with intellectual
>property misappropriated from AT&T -- perhaps not direct copies of source
>code -- but at least ways of doing things (trade secrets) -- and therefore
>any system derived from NET2 requires an AT&T source code license [it used
>to be about $10,000 to get an AT&T source license].  The threat is twofold


By this somewhat wide definition, AT&T could also claim that anyone who
has read either Bach or Lefler et al. has a knowledge of the way things
are done and as such cannot work on a kernel without use of AT&T
intellectual property.

Oh well, there goes about 99% of the UNIX community.  The sooner this is
thrown out of court the better.


   ___                                 David J. Hughes     bambi@bu.oz.au
  /   \                /  /    /        
 /  __/ __   __   ____/  /    / __          Senior Network Programmer
/    \ /  \ /  \ /   /  /    / /  \  /    Comms Development & Operation
\____/ \__//   / \__/   \___/ /   / /       AUSTRALIA  (+61 75 951450)
Newsgroups: comp.unix.bsd
From: eichin@athena.mit.edu (Mark W. Eichin)
Subject: ddb man page
Organization: Massachusetts Institute of Technology
Date: Wed, 29 Jul 1992 23:00:42 GMT

The mach ddb man page is in ernst.mach.cs.cmu.edu:src/mk/kernel/man/ddb.man
(386bsd ddb is just my port of pace@blitz.com's port of the mach ddb.) 
				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
From: MLUCI@fuel.abb.com (Mark Lucia 2915)
Newsgroups: comp.unix.bsd
Subject: Adding users
Date: 24 Jul 92 19:01:41 GMT
Reply-To: Mark Lucia 2915 <MLUCI@fuel.abb.com>
Organization: J. Deitch & Associates
Originator: 386bsd-gate@jadpc.cts.com
Precedence: bulk


       Please pardon the newbe question, but I'm having trouble adding 
       users (me) to 386bsd-0.1.
       
       If there is a better place to ask newbe type questions, please 
       let me know.
       
       I tried the following:
       	1. looking for a 'adduser' etc program/script
       
       	2. makeing an entry in the /etc/passwd file
       	   makeing am entry in the /etc/master.passwd file
           adding the home directory in /usr
       
       	3. rebooting the machine after 2
       
       when I try to chown the /usr/mark directory, I get something 
       similar to "no user match" (I confess, I didn't write it down)
       
       I looked for a /mail directory for other users, but I can't find 
       it.
       
       Any ideas?
       
       Also: I started making a map of the file system for my own 
       benifit. Does such a thing already exsist? If so where? If not, 
       would anyone find it usefull?
       
       BTW - Great OS. I'm having a great time. Thankx Bill & Lynne.
       
       Thankx for your help.
       
       /------------------------------------------------------------\
       | Mark Lucia  ABB/Combustion Eng                             |
       | internet:   mluci@fuel.abb.com                             |
       | compuserve: 71535,172                                      |
       \------------------------------------------------------------/
From: dealwisb@cognos.com (Brian de Alwis)
Newsgroups: comp.unix.bsd
Subject: Re: extract etc01 problem?
Summary: negative values in df(1) reports
Date: 26 Jul 92 14:43:25 GMT
Organization: Cognos Incorporated, Ottawa CANADA

In article <1992Jul26.095910.29737@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de writes:
>>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?)

BSD's FFS reserves (by default) 10% of each disk to aid in allocating
contiguous blocks for files. Once this 10% is reached, only root is
allowed to allocate further files. The percentage and avail fields in
df are actually reported as compared the remaining 90% of the disk.
So, if you have 92000 blocks allocated, and your disk has 100000
blocks (of which 10%=10000blks are 'reserved'), df would report that
there were -2000 blocks, or 102%, free. See df(1) as well.

The errors extracting the etc01 distribution are because extract
simply cat(1)'s all of the etc01.* files into a pipe - but as
distributed, cat(1) does not close each file-descriptor when finished
with the file [at least, this is what I gather from previous msgs
about this]. A solution may be to do the extract yourself:

for i in /tmp/etc01.*; do cat $i; done | uncompress | cpio -idalmu

(in Bourne shell - I don't like or use C-shell) This should close each
file after cat(1)'ting it, but will be much slower (you'll be running
60-odd cat(1) processes sequentially).
	   This problem is because the default maximum-of-open-files per
process is 64 - three are already taken used as std{in,out,err},
leaving only 61.

Hope this helps.
-- 
+++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"
From: markl@spuddy.uucp (Mark Liversedge)
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: 23 Jul 92 15:43:09 GMT
Organization: Spuddy's Public Usenet Domain

As a recent purchaser of BSD/386 I was a little stunned to read this 
newsgroup for the first time in a while and see *THIS*.

If BSDI lose we all lose. AT&T can F??K OFF if they want what I got back. 

Why is the world like this?
-- 
Mark

 * Meeeeow ! Call Spud the Cat on > +44 203 638780 < for free Usenet access *
Newsgroups: comp.unix.bsd
From: greg@ecse.rpi.edu (Greg)
Subject: 386bsd 0.1 - Speed dependent boot problem
Date: Tue, 21 Jul 1992 19:24:26 GMT


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


Newsgroups: comp.unix.bsd
From: terry@npd.Novell.COM (Terry Lambert)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Novell NPD -- Sandy, UT
Date: Mon, 27 Jul 1992 16:42:28 GMT

In article <1992Jul24.185653.3196@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>In addition, OSF specifically licensed parts of the SysVr3.x code from USL
>in order to include it in OSF/1.  Specifically, the STREAMS code, as there
>were no such things in the original Mach code.
>
>If OSF/1 becomes based on Mach3.0, *and* the UNIX servers are written from
>scratch, or based on ones that do not contain any USL code (such as the
>Net/2 based one, although that would be as debatable as BSDi's product),
>*then* purchasing an OSF/1 system might not cause in any license fees to
>USL.
>
>Buying Motif from OSF results in USL making $0, true, but that is an
>entirely different kettle of fish.

Buzzzzzzz.

1)	SysVr3.x has got to be SVR3.2 or later.  It didn't include streams
	prior to that.

2)	OSF has licensed Mentat streams for inclusion, not AT&T.  The code
	is un-AT&T-encumbered, and runs on many diverse platforms (for
	instance, it also runs on VMS).

3)	OSF/2 is the beast of interest, and it is based on Mach 3.0.

4)	Doesn't AT&T have patents on BLIT that effect Motif?


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
Newsgroups: comp.unix.bsd
From: quanstro@lars.StOlaf.edu (goon)
Subject: Re: I wonder, did AT&T backstab BSDI?
Organization: St. Olaf College, Northfield, MN USA
	<1992Jul29.144859.8222@bas-a.bcc.ac.uk>
	<1992Jul29.182141.10399@prism.poly.edu>
	<1992Jul29.232935.5130@news.eng.convex.com>
Date: 30 Jul 92 08:21:28

In article <1992Jul29.232935.5130@news.eng.convex.com> Tom Christiansen <tchrist@convex.COM> writes:
   From the keyboard of kapela@prism.poly.edu (Theodore S. Kapela):
   :SVR4 is System V, Release 4.  System 7 was an early version of Unix

   Is it really?  I thought you had to be SQUID compacent to be called
   Unix, and I don't think v7 is.

I'd still rather have v7 than any of the junk available to me now. You
could actually run 60 simultanious users on a PDP-11/70 with 2MB. Our
PDP was less endowed, but it could handle 40 users---yes slowly, but
not painfully so. Then we upgraded to a VAX-11/780 and BSD 4.2. Things
got _noticablly_ slower, and by the time we retired the machine (three
days ago) we were running 4.3Mt. Xinu and the absolute maximum was 10
logins and almost everything was painfully slow. Now we have 2 670MPs
with 128MB RAM which can probablly handle more simultanious users than
the PDP, but I wonder if that will still be true once Solaris 2.0
comes out. 

From: fwb@hpfcso.FC.HP.COM (Frank Bennett)
Date: Tue, 28 Jul 1992 20:05:44 GMT
Subject: other Drivers/kernels?
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.unix.bsd

It's been said:

	"U**x and the like is abunch of drivers with a little bit of code
wrapped around it".

	So anybody out there got a driver/kernel for Future Domain TMC950?
Does the driver need to be in the boot_image & the root_image?

 yeah, yeah that Future Domain is only an 8bit non bus mastering.....but SCSI 
controller in general are faster than MFM controllers (8 bits vrs 1bit). 

	I was also successful in booting & mounting the root_image, so the
Future Domain floppy controller is compatiable with the Western Digital bla,
bla, bla. I did get a message to the effect "no hd controllers found" &
install asks about "Installing the OS on my TV"

	I also was able to cpio the src tree in under ISC, but there not much
chance of making a kernel there. Make was seriously confused about:

	.include <bizmumble.stuff>

It's hard to even make make.

	The binarys are not compatible either. Isn't there some kind of object
or executable standard (COFF) such that one can execute 386 bin created under 
one OS on a different OS (ISC vrs SCO for example)? Or is their many standards
to choose from (ISC, SCO, Minix, Linux, 386BSD)? 

It would be nice if 386BSD at least supported a list of drivers similar to
say ISC or SCO. I have ISC up and running with my Future Domain and a Wantek
tape drive (but why not support any tape that has the SCSI common command set?)
Minix had a bios_wini, which helped.

So I did poke around Linux Land on headrest.woz.colorado.edu:/pub/linux in 
the SCSI stuff. And I subscribed to the "automated mailer??" thingy, sort of
got tired messing with this loser.

>        Some patches for Future Domain TMC 950 boards were posted to
>        the net   These will be incorporated into the
>        "Standard" SCSI release RSN.
What's a RSN? RealSooN? version 0.97 is going to include what?

	Adaptec 1542b        go for $285 or so, floppy controller?
	Future domain TMC950 go for  $85 and it also has a floppy controller
	Seagate ST0* only support segate drives

So for the price differential, we all could have a SCSI tape drive!

regards & Thanks,

Frank
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject:  compiling kernel hangs machine
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sun, 26 Jul 92 20:58:19 GMT


Could it be that the swap default space (5MB) is too small for compiling
a kernel with a 4 MB machine. I tried a first kernel build this
afternoon on a 386SX 4MB and when I came back after several hours the machine seemed to be dead - login from outside was not possible (telnet hung also).

This happened during the compilation of tty.c .

Is it possible to increase the swap space simply by swapping to a file (swapon)?

--Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

Newsgroups: comp.unix.bsd
From: zbig@wariat.org (Zbigniew J. Tyrlik)
Subject: Re: anonymous UUCP for 0.1 386BSD ?
Followup-To: comp.unix.bsd
Reply-To: zbig@wariat.org (Zbigniew J. Tyrlik)
Organization: Akademia Pana Kleksa, Public Access Uni* Site
Date: Sun, 26 Jul 1992 00:23:49 GMT

As quoted from <1992Jul24.182408.4895@sharm.uucp> by nsharma@sharm.uucp (Nawien Sharma):

+---------------
> Is a dialup available for anonymous UUCP access for 0.1 386BSD ?
> I recall that "stanton" was gracious enough to maintain it for release 0.0 .
> 

I will put whatever I can grab from agate for anonymous uucp on wariat. 
phones: 216-481-9445 ( USR DS )
	216-481-9425 ( WorldBlazer with PEP )

login: nuucp no password. 

One can request first /x/files/ls-lR.Z to get some ideas what I do keep here.
Also, please set up bigger requests to arrive between 00-12 EDT.

PS: it should be here tonight....

> 
> Thank you.
> -- 
> Nawien Sharma, Sharmtech Systems Inc. ..uunet.ca!snitor!sharm!nsharma
> 106 Norton Avenue, Willowdale, Ontario, Canada M2N 4A5
> (TEL): 416-512-7878 (UUCP): sharm.UUCP

_zjt

-- 
********************************************************************
Zbigniew J. Tyrlik             wariat!zbig           zbig@wariat.org
IBM PC SIG Sysop - Cleveland Free-Net    aa609@cleveland.freenet.edu
Akademia Pana Kleksa   Public Access UNI* Cleveland,  (216)-481-9445
E-mail, news feeds, shell accounts        UnixBBS distribution point 
********************************************************************