HDTenEightyP/NetNews huggingface dataset:
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.unix.bsd
Subject: Re: I wonder, did AT&T backstab BSDI?
Keywords: AT&T speculation lawsuit BSDI
Date: 29 Jul 92 23:29:35 GMT
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Originator: tchrist@pixel.convex.com
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

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.

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

Not all others -- consider tar, ar, dump, restore, and dd.

I think they should probably tolerate the minus, but it's frustrationg to
*require* it when so many of us learned them the other way.  I'm sure
1003.2 will "fix" all these for us, though.

Now if only all programs would recognize '-' for input as stdin 
and for output to be stdout.

--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist
On Monday mornings I am dedicated to the proposition that all men are
created jerks.
                -- H. Allen Smith, "Let the Crabgrass Grow"
Newsgroups: comp.unix.bsd
From: michael@resonex.com (Michael Bryan)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Resonex Inc., Sunnyvale CA
Date: Wed, 29 Jul 1992 13:24:00 GMT

In article <1992Jul29.073959.3841@nebulus.ampr.ab.ca> dennis@nebulus.ampr.ab.ca (Dennis Breckenridge VE7TCP) writes:
>joeg@gagme (joe grosch) writes:
>
>>I urge all those on the net who have copys of either Net2, BSDI, or 386BSD
>>to start making copys and distributing them as far and wide as possible.
>...
>Are you absolutely out of your mind? Distributing licensed sources is 
>not only immoral but totally illegal.

Well, NET2 and 386BSD (based on NET2) are currently freely distributable,
according to the folks at UCBerkeley.  Until such time as USL asks for
and is granted an injunction against the distribution of NET2 sources,
they can be copied anywhere.  BSDI *is* a different kettle of fish,
however, as their license agreement says you cannot distribute their
source.    So Joe's request is reasonable in 2 of the 3 items he cites.

-- 
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: gnb@duke.bby.com.au (Gregory N. Bond)
Newsgroups: comp.unix.bsd
Subject: Re: Fix for problem with tip in 386BSD
Date: 29 Jul 92 23:34:29 GMT
Organization: Burdett, Buckeridge & Young, Melbourne, Australia

>>>>> On 28 Jul 92 15:03:07 GMT, brians@rigel.cs.pdx.edu (Brian Smith) said:

>> So, I then recommend that newbies such as myself make tip sgid.

I have just been playing with tipx (based on the 4.3/net2 tip; I
assume the 386BSD one is similar). I have installed it setgid to a
uucp group (which has write permission in the /var/spool/locks
directory and the /var/adm/aculog file and read permissions on
/etc/phones and /etc/remote).

The problem was that tip does various setregid() calls going into and
out of privileged mode and can't open the phone file (which it does
from non-privileged mode).  A temporary workaround is either remove
the setreuid calls (there are three, I think) or make the phones file
world readable (OK on a PC, possible privacy/security implications on
a "real" system).

I also have a dialer for v32 hayes-like modems if anyone needs them.

Greg.

--
Gregory Bond <gnb@bby.com.au> Burdett Buckeridge & Young Ltd Melbourne Australia
``USL has never sold long distance.  You're going after the wrong men in black 
  hats.  (Or, in the case of Plan 9, black space suits)'' - Tom Limoncelli
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: IDE drive woes (need for comp.unix.386bsd)
Date: 21 Jul 92 20:33:45 GMT
Organization: St. Peter's College, US

In article <zxmsd01.711733046@mailserv>, zxmsd01@mailserv.zdv.uni-tuebingen.de (Gunther Schadow) writes:
> According to Bill and Lynne (see INSTALL.NOTES) they are about to
> achieve a group comp.os.386bsd.

  Hmmm. I just looked in news.announce.newgroups, and I don't see this group
listed in either the RFD or CFV stage. Thus, it's at _least_ a month away,
assuming a favorable vote.

  That is, unless they go the Inet route. Given the controversy over the most
recent Inet groups, I don't think that would be a good idea, though.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
From: jds@cs.umd.edu (James da Silva)
Newsgroups: comp.unix.bsd
Subject: Re: NFS patch ==> 'panic: kmem-malloc: kmem-map too small'
Summary: bump MAX_KMAPENT to 1000 in /sys/vm/vm_map.h
Date: 28 Jul 92 03:39:10 GMT
Organization: University of Maryland, Department of Computer Science

In article <l74il5INN20p@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>Well, for reading directories and a few small files the recently posted
>patch to originate NFS mounts and NFS requests from a privileged port
>worked quite well.  

If you are referring to Rob Fristrom's NFS reserved-port patch, I'm glad to
hear that it works under 386BSD; we had only tried it under BSDI.

>However, when I mounted a SUN disk on my 386BSD box
>as follows:
>  [...]
>and then pressed the system quite hard:
	  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>  [...]
>the kernel panics with 'panic: kmem-malloc: kmem-map too small' after
>only about half a megabyte is transferred.  
>
> [...]
>Does anyone have any insight into or fix for this problem?

I don't think this is related to the NFS patch.  Bill posted about this
problem last week.  A kernel table is sized too small for active machines
with large (12MB or more) memory.  Try modifying the value of MAX_KMAPENT
in /sys/vm/vm_map.h from 500 to 1000.  It worked for me.

Jaime
............................................................................
: Stand on my shoulders, : jds@cs.umd.edu  :		      James da Silva
: not on my toes.	 : uunet!mimsy!jds : Systems Design & Analysis Group
Newsgroups: comp.unix.bsd
From: knight@hal.gnu.ai.mit.edu (Knight of the Living Dead)
Subject: I wonder, did AT&T backstab BSDI?
Summary: SYSV r4 is quite similar to BSD 
Keywords: AT&T speculation lawsuit BSDI
Organization: It doesn't look like much, but its a system. 
Date: Tue, 28 Jul 1992 15:37:50 GMT


As I recall when System 5 Revision 4.0 was released, it was described
(to me, anyway) as an attempt to gain "BSD Compatibility".  I'm wondering
if the reason why AT&T held out sueing BSDI this long is so they could
claim copyright of BSD's code/style/look/feel/etc while it was still
popular, and then smash all the competition.

If so, Steve Jobs at NeXT may find MACH being charged with having
unlicenced BSD-like code that is property of AT&T.

I guess it would be impossible to find a copy of AT&T's System 5
source code..  BSD sure got suckered and coldcocked.  I'd suggest
bringing in the EFF to help out -- its unfair for small business
to pay thier own court fees against such huge businesses. 

I agree with some people that a victory for AT&T could spell the demise
for computer science as we know it currently.  U**X really is a great
operating system, the best I ever used.

-- Eric Knight

------------------------------------------------------------------------
These opinions are my own, and my employeer doesn't want me ruining his
life anymore than I absolutely have to.
                                            EBKnight@dockmaster.ncsc.mil
------------------------------------------------------------------------


Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: Re: Suggestion to somebody who's really bored (hack SCSI driver!)
Keywords: SCSI, ugly, 386bsd, boredom, project, driver, panic, crash, burn
Organization: TRW Financial Systems
Date: Wed, 29 Jul 1992 06:26:09 GMT

I have a full scsi subsystem that autoconfigures itself
It has been made available to the mach people at cmu and so
is available.

It runs on mach2.5, OSF/1 and has run on the Net2 release here 
in house.

It is available if someone has the time to make the minor hacks needed
to get it working under the jolitz distribion:

needs:
The disk driver assumes MACH FS layout but could be changed by dumping
the wd driver onto the top of it

The config files would need to be tailored to suit it.

features:

FULLY adapter independent. Presently runs on adapted 1542b
and bustek 742a (EISA) in Native mode.
I will be writing the native mode for the adaptec 1740 in the next couple
of weeks.

Autoconfigures. Quieries the scsi bus and attaches what ever it finds
to the closes approximatin driver it has available

is running solidly in several comercial sites.

supports generic retries and timeouts on all commands.

has been seen to run on
1/ many scsi disks
2. wangdat dat drive
3. cypher 3480 compatible tape drive
4. exabyte
5. Calera csci print recog. engine
6. AEG hand-print recog engine.

(5 and 6 are proprietary sub drivers, but it took
a couple of hours to impliment them each.)

Things I'd LOVE to see:

someone to take it and merge in the better bits of Pace's drivers
and port it to BSD386 (or was that 386BSD? 8-)

It's VERY modular and has quite good performance.
If someone does this, I will supply a working 1740 NATIVE
mode driver as well in a few weeks (THAT will give performance!)

Philsuth? you interested?


+----------------------------------+       ______ _  __
|   __--_|\  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
From: cgd@agate.berkeley.edu (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: (new, unofficial) patched bootables on agate...
Summary: maybe it'll work for you now!
Keywords: 386bsd, 0.1, patched, boot floppy, dist.fs, fixit.fs
Date: 23 Jul 92 06:27:39 GMT
Organization: Kernel Hackers 'r' Us
NNTP-Posting-Host: agate.berkeley.edu

I've put some new patched boot floppies in
agate.berkeley.edu:~ftp/pub/386BSD/386bsd-0.1/unofficial/newbootables.cgd

They have the fix for the wd boot block, the fix for the wd driver,
and there are various combinations of ones having no
Isolink driver in the kernel, no "we" driver in the kernel, and
ones having debugging bootstraps installed...

there's a readme, but it's almost as useful as this post is... 8-)

enjoy!

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: greg@ecse.rpi.edu (Greg)
Subject: 386bsd-0.1: primary bootstrap (wdbootblk.c) problem & fix.
Summary: I have solved a timing dependent boot problem by adding a delay.
Keywords: 386bsd boot bootstrap wdbootblk.c
Date: Sun, 26 Jul 1992 00:46:45 GMT

   In a recent post I described a booting problem I was having: I could only
boot about 20% of the time in high speed mode. I tried all the latest patches,
but the problem persisted. By putting a printf at the top of boot.c, I          determined that it was not making it out of wdbootblk.c.

   I managed to learn enough 386 assembly language from reading the source, to
enable me to write directly to the video buffer. By placing video writes 
throughout the bootstrap, I was able to figure out where it was getting hung up.

from wdbootblk.c:

	readblk:
        	movl    $ IO_WD1+wd_status,%edx
       		NOP
        	inb     %dx,%al
        	testb   $ WDCS_BUSY,%al
        	jnz readblk

It would get stuck in this loop, thinking that the controller was busy.
my code:

readblk:
# beware, ugly hack ahead!!
# it is safe to clobber ax, cx here
        movl    $0xff,%ecx
blink:  movw     $0x0f30,%ax
        movw     %ax, VIDEO
        movw     $0x0f5c,%ax
        movw     %ax, VIDEO+160
        movw     $0x0f21,%ax
        movw     %ax, VIDEO+160
        movw     $0x0f2f,%ax
        movw     %ax, VIDEO+160
        movw     $0x0f5f,%ax
        movw     %ax, VIDEO+160
        decl    %ecx
        movl    %ecx,%eax
        jnz     blink
# end of ugly hack

        movl    $ IO_WD1+wd_status,%edx
        NOP
        inb     %dx,%al
        testb   $ WDCS_BUSY,%al
        jnz readblk

     After adding this, I was able to successfully boot 30 consecutive times at
full speed. I appologize if its ugly, as my knowledge of 386 assembly 
language is entirely based on reading wdbootblk.c. I appeal to someone who 
actually knows 386 assembler to write a proper delay loop. My version works 
fine, but I am sure it can be more compactly coded. Also, in a final version
the video writes would be removed.
     If someone could help me recode this into a more "publishable" form,
it can be made available as a patch and a patched binary. I don't think
(at least I hope), that this will "break" the bootstrap with respect
to machines other than mine. Also, I wonder if anyone has any insight as to the 
cause of this problem. Perhaps there is a better fix for it.

      Happily booting and rebooting,
                                     Greg  -  greg@megas.ecse.rpi.edu
From: james@raid.dell.com (James Van Artsdalen)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD-0.1/BRLCAD4.0 benchmark -- poor floating point performance
Date: 30 Jul 92 17:31:06 GMT
Reply-To: james@raid.cactus.org (James Van Artsdalen)
Organization: Dell Computer Co

In <l7ctu0INN880@neuro.usc.edu>, merlin@neuro.usc.edu (merlin) wrote:

> Does gcc 2.2 actually use 80387 inline code for transcedental functions?

No.  But this would not be very hard to implement.  sqrt is built-in
if -ffast-math is used: make similar changes for the other functions.
-- 
-- 
James R. Van Artsdalen          james@bigtex.cactus.org   "Live Free or Die"
Dell Computer Co    9505 Arboretum Blvd Austin TX 78759         512-338-8789
From: qs101@cl.cam.ac.uk (Quentin Stafford-Fraser)
Newsgroups: comp.unix.bsd
Subject: Re: More booting problems...
Date: 21 Jul 92 08:49:15 GMT
Reply-To: qs101@cl.cam.ac.uk (Quentin Stafford-Fraser)
Organization: U of Cambridge Computer Lab, UK

In article <14f4n8INNe18@agate.berkeley.edu>, wjolitz@soda.berkeley.edu 
(William F. Jolitz) writes:

|> This sounds like the 4MB is split in the middle, and I don't know why.

Well, I wouldn't put it past HP, but nothing else seems to mind this (Linux,
DOS, Windows etc...)

|> .... At a guess, could this machine be setup for 512K of base memory 
|> instead of 640K?

It isn't - at least not in the CMOS.

I didn't get 0.0 going on here either, (but I didn't try very hard).

As Terry Lambert points out, there is a bus mouse built in....

Many thanks for your help...
Quentin


 -----------------------------------
 Quentin Stafford-Fraser            
 Cambridge University Computer Lab  
 qs101@cl.cam.ac.uk
 Tel +44 223 334645
 -----------------------------------
Newsgroups: comp.unix.bsd
From: zmz@small.caltech.edu (Steven Zhou)
Subject: HELP! cpio problem?
Keywords: cpio, 386bsd
Organization: California Institute of Technology, Pasadena
Date: Fri, 24 Jul 1992 19:11:22 GMT

I was excited by all the successes and failures news on installing 386bsd  
posted here. So, I decided to give it a try. Having 
fidlling around for a couple of days, I started booting the  tiny 386bsd.
After the 386bsd partition is created, it starts to formating the  
partition and displays an array of numbers. Then the following message  
showed up and the booting process stopped:
	Mounting 386BSD file system.
	Installing files from installation floppy.
	cpio: No such file or directory.
	Could not install files. Installation failed.
Is there anyone have this problem with installation? Did I do anything 
wrong?  I am new to 386BSD. Please, someone help me. I am anxious to get
it running.

SZ
From: bvickers@valentine.ics.uci.edu (Brett J. Vickers)
Subject: SLIP over /dev/com1
Newsgroups: comp.unix.bsd
Organization: Univ. of Calif., Irvine, Info. & Computer Sci. Dept.
Keywords: SLIP IP com serial
Date: 23 Jul 92 19:32:59 GMT

I've been having some problems with SLIP over /dev/com1 lately.

For the most part it works fine, but every once in a while, it
will get "stuck."  No more information will flow from my
machine over the SLIP connection, and vice versa.  The only way
to get it going again is to kill the slattach process, wait
for any buffers to be flushed, and then restart the slattach
process.

Weird?  This tends to happen usually when a lot of information
is being sent at once.  Overflowing buffers, possibly?

I've tried using the original com.c driver and the bi-directional
one by Chris (using /dev/ttyd1).  Neither has solved the problem.

--
 ___            _    _     _  _        _
(  _) ___ ___ _( )__( )_  ( )( ) o  __( ) _  ___  ___  ___
(___)(_) (__=) (_)_ (_)_   (__) (_)(_((_)(_'(__=)(_) _(_)
Brett Vickers (bvickers@ics.uci.edu)
Newsgroups: comp.unix.bsd
From: terry@npd.Novell.COM (Terry Lambert)
Subject: Re: 386BSD Bug in wd.c
Keywords: wd.c malloc bzero
Organization: Novell NPD -- Sandy, UT
Date: Thu, 30 Jul 1992 17:37:14 GMT

In article <1992Jul30.024553.2340@linus.mitre.org> wheeler@heckle.mitre.org (Brien L. Wheeler) writes:
>I sent this bug report off to Lynne Jolitz tonight.  Some non-initialized
>memory in wd.c prevents my machine from warm-rebooting.  Trivial context
>diff attached.

	This is one of the fixes in Chris's (CGD's) fixes in the unofficial
directory on agate.berkeley.edu.  The same problem applies to some portables
on initial boot, due to not clearing memory on power-on.

					-- Terry
From: rick@postmaster@hq.af.mil (Rick Weldon)
Newsgroups: comp.unix.bsd
Subject: Setting up bootable DOS pertition by hand
Keywords: DOS
Date: 29 Jul 92 14:42:46 GMT
Reply-To: rick@hq.af.mil
Organization: 7TH Communications Group

I want to be able to boot DOS as well as 386BSD from the 
HD. I haven't seen much discussion on this specifically.
Most of the discussion seems to be around accessing DOS 
from 386BSD.

My questions though are centered around getting DOS to boot.

I tried to use the automated install script and it blew up.
I did as the release notes suggested and used fdisk to create
a DOS partion on the beginning of the drive, but install munged
things, so I ended doing a manual install to the whole disk.
I used Chris Demetriou's method to install everything on seperate
partitions. Boot from HD-- no problem --all is well.

Now what I want to do is set up that DOS partition by
hand. I want to use the first 30Mb of the disk and leave the
rest for 386BSD. I am assuming that I will have to write the
disklabel by hand taking into consideration the DOS partition.

So I am assuming something like this: 

wd0a 32 Mb into the disk -- to 37 Mb
wd0b 37 Mb to 42 Mb swap
wd0c whole disk
wd0d 0 Mb to 30mb for DOS
wd0h 42Mb to end of disk

Now the  fun part. 

1. If I put DOS on to the first 30 Mb of the 
drive how does the boot image know where to go to boot 386BSD.
I would assume that it reads the disklabel and then looks for 
the kernel image 32 Mb into the disk on the wd0a partition.
Is this the case?

2. When I shutdown todos I assume that the shutdown program
tweaks the boot image to tell it to boot DOS instead, Or 
simply makes the DOS partition active. If the latter
is true all I should have to do is run fdisk and de-activate
the DOS partition to get back to 386BSD. This is where
things get hazy, I was hoping someone might be able to explain 
this a little better.  Another words how do I get back and
forth between DOS and 386BSD. 


I also remember reading that a lot of people were having trouble
with the shutdown -to-dos script. A complaint that shutdown
couldn't make dos bootable or something similar. Was this ever 
resolved? 


Any help at all would be appreciated. I was hoping for 
something like Chris Demetriou's step by step, but edited
to include how to set up a DOS partition by hand.

Please post here.
I read this group all of the time |-).

(Have you ever noticed that the people who want the most
information from a particular group don't read the group.
They always ask for any helpers to e-mail because they don't have
time to read the news.) 

If anyone cares I'll put the whole thing together and post it.
I have Chris's step by step. 

Thanks so much to Bill, Lynne and Chris Demitriou 

-- 
Rick Weldon     I-NET Inc. (Pentagon, 7TH Com Group)
E-mail: rick@hq.af.mil
Phone:  703-695-5060
Newsgroups: comp.unix.bsd
From: pk@cs.few.eur.nl (Paul Kranenburg)
Subject: Re: Some questions, some fixes, some suggestions
Reply-To: pk@cs.eur.nl
Organization: Erasmus University Rotterdam
Date: Mon, 27 Jul 1992 10:10:18 GMT

In <1992Jul25.182354.14203@cognos.com> dealwisb@cognos.com (Brian de Alwis) writes:

> [...]

>	   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).

For those interested, a version of kern_execve.c based on v0.1 with the
`#!' magic enabled is available via anon-FTP at ftp.cs.few.eur.nl in
directory ~ftp/386BSD/unofficial.

[Note that I have made no attempt to prevent execution of setuid/setgid
shell scripts, just dont't set those bits]

-pk

Newsgroups: comp.unix.bsd
From: perv@flash.emf.mcgill.ca (Irwin Roger Gibson)
Subject: Making/altering distribution diskette
Organization: Engineering Microcomputing Facility
Date: Mon, 27 Jul 92 17:37:32 GMT


      Could anyone explain how to go about altering/making a new
distribution diskette for 386BSD.   I am having some difficulty
in booting.  My computer hangs immediately after reading the dist.fs
floppy.  The Num Lock, Caps Lock and Scroll Lock lights blink twice,
and then the diskette is read for 20 seconds, and all activity 
ceases with the drive light on.  

      I tried the latest bootables on agate.berkeley.edu, but to no
avail.  Even the debug version showed absolutely nothing on the 
screen, and the computer also hanged.

     What I would like is a brief discription on how to go about changing 
the boot disk myself.

     Is enough code to do it contained in the bin01 distribution?

     Can it be done (I assume it can) from dos with an assembler and
     C compiler?

Whatever help I can get concerning this would be appreciated.  Thank
you.

Irwin Gibson
perv@flash.emf.mcgill.ca
perv@emf.lan.mcgill.ca

          
Newsgroups: comp.unix.bsd