HDTenEightyP/NetNews huggingface dataset:
From: sa1@Ra.MsState.Edu (Sujith Abey)
Newsgroups: comp.unix.bsd
Subject: Where is a FAQ?  (and other novice questions)
Date: 23 Jul 92 19:06:12 GMT
Organization: Mississippi State University

Is there a FAQ anywhere?  I can't find one.  Here are some of
my questions anyway:

I just downloaded and installed 386BSD, and it worked fine on my
386 clone at home, but not on my Compaq at work.  I haven't seen
any answers to this problem on this newsgroup, so has this been
answered before?  I see that Compaq is a financial supporter of this
project, so it seems that it would be working on their machines.

According to the ROADMAP, there should be a 'userdirectory' file inside
of 386bsd0.1, but I couldn't find it at any site.  Does this file
exist?

Does anyone have any directions for starting slip?  In the INSTALL guide
page 20, it simply says "attach a SLIP connections to com1 serial port..".
I know how to tell my host to start the connections, but I guess I need
to be in a terminal mode first so I can do this, right?  Then what?

 

thanks
Newsgroups: comp.unix.bsd
From: tal@Warren.MENTORG.COM (Tom Limoncelli)
Subject: USL vs. BSDI, and what to do
Organization: Mentor Graphics, Silicon Design Division
Date: Fri, 24 Jul 1992 17:04:47 GMT

In <l6vt9sINN93u@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:


>     o  Domestic and international letters should be addressed to:

>        o  Mr. Robert E. Allen              
>           Chief Executive Officer and
>              Chairman of the Board of Directors
>[...]

I hate to say this, but Bob has nothing to do with this.  AT&T didn't
bring the law suit.  USL did.  USL has a different chair person, and
has their own lawyers (from what I've heard, they don't share lawyers...
so much for the "army of lawyers").

>     o  These letters should also point out that the release notes for
>        the public releases of 4.3BSD-NET1 (June 1988) and 4.3BSD-NET2
>        distributions clearly state that they contain no code licensed
>        by AT&T or others -- instead, the code is owned by the Regents 
>        of the University of California -- and the code may be used by
>        anyone for any purpose as long as due credit is given to the
>        University and the University copyright notices are retained.

Thought I haven't seen a complete copy of the suit (could someone post
it or email it to me?) I believe all it claims is that proper black box
techniques were not used  to generate the NET2 (not NET1) release.
(blackbox techniques means like what Phoenix used when developing their
BIOS clone).  Doesn't that make the above statement moot?

Hype from all over, more heat than light, more flames than news.
I think I'll start reading talk.bizarre instead.

Tom
-- 
Tom Limoncelli -- tal@warren.mentorg.com (work) -- tal@plts.uucp (play)
      Maybe Bush will follow Perot's lead.
Newsgroups: comp.unix.bsd
From: cs8023@ee21.ncu.edu.tw (ee76536)
Subject: Sorry, a foolish beginner's question...
Keywords: 386BSD 0.1, INSTALL.NOTE
Organization: Dep. of EECS, National Central University, Chungli, Taiwan, R.O.C.
Date: Thu, 30 Jul 1992 12:39:15 GMT

Dear all 386BSD experters:
I had a foolish question: for those distribution files (bin01.hh
etc01.hh, and src01.hh), how can you download them onto floppies?

I have a 486 machine which does not have any model, network, tape
devices, just only floppies, so I must download files via my
work-station account, then download again to the PC in my department,
I must copy them onto flooppies and bring these floppies to home,
then I must try to cpio them onto my machine.
now, how can I transfer these XXX01.hh onto floppies? use `voldump' ?
no, this is not a DOS batch file, 
it is only one possible way, copy them by DOS's COPY? XCOPY? or PCShell?
just use binary copy onto a MSDOS formatted floppies?

Perhaps INSTALL.NOTE is not clear for such situation, can you enlight
me?
thanks, best regards,
Anthony Li



-- 
>>> Anthony Li <Li3, Shih4 Hao2><Li:fruit's Name><Shih:Scholar><Hao:Hero>   <<<
<<< Institute of CSEE, National Central Univ, Chungli, Taoyuan, Taiwan, ROC >>>
<<< Bitnet:	U230700@twncu865.bitnet					    <<<
>>> Internet:	U230700@ncu865.ncu.edu.tw oper2@ncuee.ncu.edu.tw	    >>>
From: dxper@dtek.chalmers.se (Per Anders Olausson)
Newsgroups: comp.unix.bsd
Subject: 386bsd and I/O...sheduler bug?
Date: 29 Jul 92 11:53:55 GMT
Organization: Chalmers University of Technology, Gothenburg Sweden


  I have been suspecting all the time since V0.0 that there is something very
strange relating to disk i/o in 386bsd. This is either a bug or feature of the
BSD 4.3 sheduling algorithm. 

  Yesterday I therefore tried out the following simple program:

#include <stdio.h>

main()
{
	char	data[8192];
	FILE	*f;
	
	f = fopen("Test2.file", "w+");
	while(1)
	{
		fread(data, 1, 8192, f);
v		rewind(f);
		fwrite(data, 1, 8192, f);
	}
}

===

  If I run this at normal priority the system will turn on the disk led and
just grind to a halt. That is, it will not let any other process run as long
as it is running.

  If I run it with a nice value of 20 the system will let me use the shell
until I decide to do something and then it will hang. If you use the elbow
technique you'll sporadicly get hold of the cpu but after a while it will hang
to.

  So it appears as if processes doing I/O is somehow not accredited their usage
of the CPU. If you check out the load average while doing make depend or
something like that it seems a bit low too.

  Can anyone confirm if this has been fixed or does anyone have any clues as
to where the fault lies?

pao



--
-------------------------------Andrew Olausson--------------------------------
--------------------------Unemployed Unix Specialist--------------------------
------------------------------pao@cd.chalmers.se------------------------------
-------------------------------pa-ola@proxxi.se-------------------------------
From: brad@Cayman.COM (Brad Parker)
Newsgroups: comp.unix.bsd
Subject: re: email read by corp higher-ups
Date: 26 Jul 92 13:51:34 GMT
Distribution: comp
Organization: Cayman Systems Inc., Cambridge, MA


   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.

I disagree.  Scott McNealy reads his email.  I know this for a fact.
Most CEO's of small companies (like Cayman) read their email.

I think you'd be suprised if you tried "telnet xxx.com 25; VRFY <ceo-name>".

-brad
--
A metaphor is like a simile.

Brad Parker	Cayman Systems, Inc., Cambridge, Ma.	brad@cayman.com
From: BSC_PAT@vd.seqeb.gov.au
Newsgroups: comp.unix.bsd
Subject: Availability of 386BSD_0.1 in Australia
Date: 23 Jul 92 09:57:12 EST
Organization: South East Queensland Electricity Board

Does anyone know where 386BSD_0.1 is available in Australia or the Pacific
region.

Thankyou.

Patrick Collins
BSC_PAT@seqeb.gov.au

Newsgroups: comp.unix.bsd
From: terry@npd.Novell.COM (Terry Lambert)
Subject: Re: Removing 386BSD from the hard disk
Keywords: 386BSD
Organization: Novell NPD -- Sandy, UT
Date: Tue, 28 Jul 1992 19:14:14 GMT

In article <wutcd.712344627@hrz.tu-chemnitz.de> wutcd@hrz.tu-chemnitz.de (Joerg Wunsch) writes:
>Kwan-Seng Law advised to low-level format the disk. If you don't want to
>do this (on an IDE, about 10 % of IDE drives are problematically with this),
>write a simple DOS program which nullifies all sectors of the first tracks
>(via BIOS hard disk interrupt); i'm sure this will help, at least when done
>on the whole disk.
>
>	good luck,
>		J"org

From th release notes:

	1)	boot tinybsd floppy
	2)	cat /386bsd >/dev/wd0d

Or, if you don't want to lose a large chunk off the front of the disk:

	1)	boot DOS 5.0 or above
	2)	fdisk /mbr


					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: osynw@warp.mhd.montana.edu (Nate Williams)
Subject: Unofficial User Supported Bug List being created
Organization: Try to get some.
Date: Wed, 29 Jul 1992 17:42:21 GMT


Since the Jolitz's and Chris are very busy people, I figured it would be
nice for them and for us to have a bug list.  Since I have some free time
until school starts (1 month), I am volunteering to try and make an
organized bug list for 386BSD 0.1.

I will attempt to keep this list current with recent official and unofficial
patches, so when the first patch to 0.1 is released, I will try to update
my list (assuming I have it out by the time the patch is released).

The advantages to us doing it are:
----------------------------------
1) It takes some work of the developers.
	When I get the list organized, I can send it off to the
maintainers of 386BSD,  and as people send in more bugs I can try and
organize them in a (hopefully) coherent manner.

2) It may help co-ordination of the user group's efforts.  There are
alot of talented people who read news, and it would be nice to know
who is working on what so we don't get redundancy.

3) This kinda of thing may help new users.  I hope to integrate Terry 
Lambert's FAQ into this list, and separate bugs into kernel bugs, 
installation bugs, user program bugs, and other misc. bugs.

4) It's just plain nice to know sometimes that what you are seeing is
a bug, and not you going crazy expecting something else. ;-)


What I propose is people fill out a simple bug report form, which is hopefully
easier to fill out than fixing the bugs.  If you would send me the
bug report, with a mail heading of 386BSD BUGS, I can organize these
reports and then re-post them to the network and/or upload them to the
ftp sites.

Here is my second shot at a BUG REPORT form.

----------------------------BUG REPORT------------------------
Name:
Email address:
Date:

Hardware info:
[Whatever you think is necessary for creating the problem
CPU, BIOS, Chipset, Memory, cards, disk, ....]

Problem description: 
[As much info as you can give, how to re-produce, etc..]

Problem suspicions:
[What/where you think the problem is if you don't have a fix]

Solution:

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

So if you know of bugs in 386BSD 0.1, please send me email with
the subject line of: 386BSD BUGS, and I will try and get this thing together
sometime this week.

At first, if your bug-list is in a different format, and you think I
will understand it, send it to me in whatever form you can, but
as time goes by, I would like to auto-mate this a little so as
you find new bugs, try and use the form. (which will problaby
change as time goes on)

Thanks a lot Bill and Lynne et al. for giving us 386BSD,


Nate

(if you have problems emailing this account, try the one in my .sig)
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home.  Anyone  interested
work: (406) 994-5991         |  in a used Sys. Admin., which alot of 
home: (406) 586-0579         |  good hacks left?
From: barnesdo@CS.ColoState.EDU (douglas barnes)
Newsgroups: comp.unix.bsd
Subject: One booting success, one failure
Date: 31 Jul 92 00:16:29 GMT
Organization: Colorado State University, Computer Science Department

A booting success and a failure (tried three different boot diskettes
on two different systems, all worked on one, none worked on the other).

Diskettes used:
   dist.fs (Jollitz .1.24), dist.fs, (cgd) fixit.fs (cgd)

Symptoms: 
   Copyright notice appears, disk access light stays on, cursor blinks,
   nothing else ever happens. I think I have seen a similar problem on
   this group but not the solution. Tried all three diskettes, disabled or
   disconnected all optional hardware, disabled various CMOS settings.
   All three diskettes had exact same problem. 

Failed to boot on:
   486/33mhz OPTI-486WB with 8MB RAM
   OPTI chipset, AMI BIOS (6/6/91)
   "Groundhog Graphics" ET4000 SVGA card
   Quantum 234mb IDE drive
   1.2mb and 1.44mb drives (1.2mb is boot)
   All serial and parallel cards removed after initial failure
   All "shadow" options disabled in CMOS after initial failure
   All caches disabled in CMOS after initial failure
   Speed reduced to "16mhz" after additional failures

Same diskettes booted just fine on:
   386/25mhz no-name board with 4mb RAM (so Taiwanese the "manual" is
      in Chinese...)
   OPTI chipset, AMI BIOS (ca. 1989)
   "Tronics" ET3000 
   Adaptec 1542B SCSI adapter
   Quantum 120mb SCSI drive 
   generic 2serial/1parallel card

Any ideas on this mysterious failure would be greatly appreciated. When
the larger hard drive arrives, I can start hacking but until then...

doug
-- 
-----------
douglas barnes, barnesdo@CS.ColoState.EDU
Newsgroups: comp.unix.bsd
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Kithrup Enterprises, Ltd.
Date: Fri, 24 Jul 1992 18:59:23 GMT
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD

In article <14105@ksr.com> jfw@ksr.com (John F. Woods) writes:
>AT&T's problem might be that they
>have been too slow to act -- in particular, "The Design of the 4.3BSD Operating
>System" has been out for quite some time, and presumably would have disclosed
>the same trade secrets (one hopes that they will try to avoid claiming anything
>that *they* published in the Bach book, to avoid looking really stupid).  

McKusick et al stated, just after the book was published, that they were
very careful to discuss only the same algorithms discussed in Bach, if those
algorithms came from AT&T code.  (If the algorithms came from elsewhere,
then, of course, there was no problem.)

-- 
Sean Eric Fagan  | "My psychiatrist says I have a messiah
sef@kithrup.COM  |  complex.  But I forgive him."
-----------------+              -- Jim Carrey
Any opinions expressed are my own, and generally unpopular with others.
Newsgroups: comp.unix.bsd
From: penney@cl-next4.msu.edu (Chris C. Penney)
Subject: C Libraries in 386BSD
Organization: Michigan State University
Date: Wed, 29 Jul 92 15:41:10 GMT

I tried compliling a couple of modem comm programs in 386BSD.  I got 
the same error message when compiling both of them.  It seems to be 
missing "termio.h".  Is it supposed to be there?  Is there anywhere I
can get it? 

Consequently, I also cannont get tip to work either; however, I haven't 
tried the ownership changes.

====                                                                 ====
= Christopher C. Penney              E-mail:    13501ccp@ibm.cl.msu.edu =
= Computer Consultant             NeXT Mail: penney@cl-next4.cl.msu.edu =
= ACM Vice Chairman     CPS, SEC & ACM Mail:         penney@cps.msu.edu =     
= SEC/ACM Representative                      Michigan State University =
= SEC/CASE Center Representative               East Lansing,  Michigan  =
====                                                                 ====
Newsgroups: comp.unix.bsd
From: ephraim@fysas.fys.ruu.nl (Michiel Ephraim)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Utrecht university
	<1992Jul21.131433.16450@ntuix.ntu.ac.sg>
	<1992Jul30.173606.28357@kas.helios.mn.org>
Date: 31 Jul 92 12:48:31

>>>>> On 30 Jul 92 17:36:06 GMT, rhealey@kas.helios.mn.org (Rob Healey) said:

Rob> 	Just to remind the non-US audience, this legal action is being
Rob> 	done in the US so by definition of the US legal system NOTHING
Rob> 	is insane or absurd because the US "legal" system IS insane and
Rob> 	absurd. This comes from lawyers controlling the legal, judicial,
Rob> 	legistative and executive branches of the US government, i.e. a
Rob> 	complete monopoly, to make the government and law infinitely complex
Rob> 	and absurd.

Rob> 	Be glad you don't have to deal with our excuse for a legal system...

Rob> 		-Rob

Then BSDI should move to Europe, here in the old world we simply try
to make better systems, competition is seen as an encouragement to
do better.

-- Michiel --
From: torek@horse.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.bsd
Subject: Re: STDIO Mode "a+" screwed up
Date: 29 Jul 92 08:04:17 GMT
Reply-To: torek@horse.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
NNTP-Posting-Host: 128.3.112.15

In article <24972@dog.ee.lbl.gov> I wrote:
[stdio "a+" mode is supposed to work the way it does]
>[The rogue score code] should use "w+" mode.

This should be "r+" mode; "w+" would wipe out any previous scores.
Thanks to Andras Radics <andras@cyber.net> for catching this.

Of course, r+ mode will not create the file if it does not exist.
(On the other hand, in this case the permissions for the file may
be a problem; some user may run rogue with umask 0777, for instance.)
Perhaps the simplest approach is:

	if ((fd = open(path, O_RDWR | O_CREAT, mode)) < 0)
		... handle open error ...
	(void)fchmod(fd, mode);	/* undo any user umask */
	if ((fp = fdopen(fd, "r+")) == NULL)
		... handle fopen error ...

Since rogue's score file is special, the mode here might legitimately
be something other than 0666, like, oh, say, 0600....
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 510 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov
From: marty@ccwf.cc.utexas.edu (marty)
Newsgroups: comp.unix.bsd
Subject: Is there a FAQ anywhere?  (and some novice questions)
Date: 23 Jul 92 15:24:14 GMT
Reply-To: marty@ccwf.cc.utexas.edu (marty)
Organization: The University of Texas at Austin, Austin TX
Originator: marty@thumper.cc.utexas.edu

Is there a FAQ anywhere?  I can't find one.  Here are some of
my questions anyway:

I just downloaded and installed 386BSD, and it worked fine on my
386 clone at home, but not on my Compaq at work.  I haven't seen
any answers to this problem on this newsgroup, so has this been
answered before?  I see that Compaq is a financial supporter of this
project, so it seems that it would be working on their machines.

According to the ROADMAP, there should be a 'userdirectory' file inside
of 386bsd0.1, but I couldn't find it at any site.  Does this file
exist?

Does anyone have any directions for starting slip?  In the INSTALL guide
page 20, it simply says "attach a SLIP connections to com1 serial port..".
I know how to tell my host to start the connections, but I guess I need
to be in a terminal mode first so I can do this, right?  Then what?

 

thanks
Newsgroups: comp.unix.bsd
From: clement@arp.anu.edu.au (CJ Canon)
Subject: Re: AT&T sues BSDI
Organization: Centre for Information Science Research ANU
Date: Fri, 24 Jul 92 06:49:22 GMT


My 2 cents (wirth) worth:


  It seems to me that Ma Bell is annoyed with BSDi, because it needs a test 
case to prove that it can do what it wants with UNIX, the name UNIX, and any 
derivatives of same. That of course includes killing off (or buying out, 
maybe?) smaller companies. Seems to be just a tad on the monopoly side,
doesn't it?
 
  I'd like to know why Ma hasn't gotten the claws pointed at the Jolitz' port.
The reasoning behind this lack might show some of the logic (if any) of the 
current suit.

Comments, anyone?

CJ
Newsgroups: comp.unix.bsd
From: israel@informatik.tu-chemnitz.de (Andreas Israel)
Subject: Success, but HD problems (Controller WD1007V)
Organization: tu-chemnitz
Date: Wed, 29 Jul 1992 16:48:35 GMT

Hello,

I finally managed to install 386BSD 0.1 on a 486 with HD controller
WD1007V (ESDI). The install program put very strange things in the
disklabel, so I used the fixit.fs to write the disklabel and installed
it manually.
Although the system boots from the hd and goes multi-user, I have
strange effects in the filesystem. There are some blocks I can write,
but I cannot read it.
Bad blocks! Bad144? I thought of that, but whenever I try to enable
bad sector forwarding, the system says that my bad sector table is
corrupt. But it is also impossible to clear the bad sector table with
'bad wd0 0'.
BTW: I tried dd to find the bad blocks, but it will stop on the first
occurance and refused to read behind this block even with skip=bno.

(I lowlevel-formatted the disk before I started and the program found
one additional bad sector and added it to the bad sector table of the
disk - but it used the physical sectors of the hd. - Is it possible that
I could overwrite this bad sector table with the filesystem, but the
controller refuses attempts to initialize the bad sector table?)

Maybe my disktab entry is wrong? Should I use the parameter the
controller simulates? Or should I use the physical parameter of the
hd?
Could someone with deeper insight to this controller business give me
some ideas on how this bad sector forwarding works and what I can try
next to get rid of these effects?

Any help appreciated!

Andreas

--
Name: Andreas Israel   Chemnitz University of Technology        Email:
Nick: Easy             Dept. of Computer Science         ai@hrz.tu-chemnitz.de
Phone: +49 371 668 423 Germany, O-9010 Chemnitz, PSF 964 
"Think of your family tonight. Try to crawl home after the computer crashes."
Newsgroups: comp.unix.bsd
From: darylm@sequent.com (Daryl V. McDaniel)
Subject: Re: Berkeley Strikes Back?
Organization: Sequent Computer Systems, Inc.
Distribution: sqnt
Date: Thu, 30 Jul 92 20:46:27 GMT

gwh@soda.berkeley.edu (George William Herbert) writes:

>...
>  Berkeley could conceivably pull the right for USL to
>resell anything with "Copyright the Regents..." in it,
>or derived therefrom.

I have scanned many of the Berkeley contributed portions of SVR4 (using strings
for binaries, etc) and haven't seen any Copyright notice mentioning Berkeley.

For example:  The /usr/ucblib/makewhatis script is IDENTICAL to the makewhatis
script in the Net-2 release except that in SVR4 the "Regents" copyright is
replaced with Copyright notices from USL, Microsoft, and Sun.  In addition,
while makewhatis works fine on BSD4.X, it doesn't work in SVR4 because of
restrictions on command line length.  This is compounded by USL moving all
of section-8 into section-1.  Add X, networking, and developers man pages
and it becomes even imposible to do a "ls /usr/share/man/man1/*n".

In the first three months of using SVR4, we submitted 168 bugs against
SVR4 to our vendor.  Ten of these bugs are of a nature to prevent our intended
use of the system (login accounting broken, for one).  Over 80% of the bugs
were directly attributable to USL.  The remaining bugs MAY have been
introduced by the vendor.

Monday, I sent off a check to BSDI.  With sources and the quality inherent in
the BSD code, I KNOW that I will be able to get a stable system running within
a couple months.  I KNOW that SVR4 will NEVER be of sufficient quality to stake
my company's livelyhood on.  I think that USL knows that they have a garbage
product and is frightened by the prospect of an affordable, supported,
POPULAR, quality OS competing with them.

These views are entirely mine.  They do not represent the views of Micronetics,
or any customers or clients of Micronetics.
--------
Daryl V. McDaniel		(503) 643-6137
Micronetics
Aloha Research Group		darylm@illian.mnet.com
Beaverton, Oregon USA
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: X386 for 386BSD?
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Thu, 30 Jul 1992 22:49:57 GMT


In article <1992Jul30.205717.18227@lgc.com> danson@lgc.com (Doug Anson) writes:
   Does anyone know what the current status of X386 running on 386BSD is?
   Has anyone got it running on 386BSD with a Logitech Bus mouse?

an annoucement of the X386 patches and binaries was posted  this
morning.  There is code for the bus mouse, but no one as tested it
under 386BSD yet.
--
Newsgroups: comp.unix.bsd