HDTenEightyP/NetNews huggingface dataset:
From: cejjb@marlin.jcu.edu.au (Jeffrey J Bird)
Subject: 8Mb stability patches DESPERATELY needed!
Organization: James Cook University
Date: Tue, 8 Sep 92 06:27:25 GMT

I am in very desparate need of the patches that stop 386BSD 0.1
freezing when there is more than 8Mb of memory in the machine.

Any help greatly appreciated,
			Jeff Bird

-- 
    Jeff Bird - Department of Electrical and Computer Engineering
	        James Cook University of North Queensland
AARNET/Internet:	cejjb@marlin.jcu.edu.au
			jeff@wench.ece.jcu.edu.au
Newsgroups: comp.unix.bsd
From: st923150@pip.cc.brandeis.edu
Subject: Re: Shared Libs for X11?, was Re: 386bsd -- The New Newsgroup
Reply-To: st923150@pip.cc.brandeis.edu
Organization: Brandeis University
Date: Tue, 15 Sep 1992 14:34:58 GMT

Well, in a way, the mechanism involved by SunOS does use self-modifying code.
Sorta, that is.  The executable image is modified in place immediately before
execution begins.  A small kernel extension may be needed to alias the text
segment to a r/w data segment (as Intel text segments are either execute only
or execute/read, but not e/r/w).  Still, this is the simplest way I can think
of to do good (i.e.- not fixed offset dependent where if you recompile the lib
you must recompile all the executables that need it) shared libs.  All that is
needed is writing a C code-generator preamble to call the dynamic linker in
all executables, the dynamic linker itself, and maybe very small kernel mods
to allow the dynamic linker to find the text and alias it as data.  There
would be no need to reverse-engineer anything Sun did, and I doubt that the
_concept_ is patentable (lawyer's opinion appreciated here).  The dynamic
linker needed is actually _almost_ ld itself, and, indeed, were I to write
it, I would do so by patching ld.  Small modifications to ld are also necessary,
so that we get the needed library names (stuff that Sun puts in a struct
called __DYNAMIC in each executable) into the executables, too.  Well, those
are my thoughts.  I might volunteer to work on this, or at least part of it,
if people think it is a viable approach...
-ben
Newsgroups: comp.unix.bsd
From: fontenot@ravl.rice.edu (Dwayne Jacques Fontenot)
Subject: local bus and 386bsd compatible?
Organization: Rice University
Date: Thu, 10 Sep 1992 08:00:09 GMT


hello,

I will very soon be in the market for a machine on which to run 386bsd.
I intend to get an EISA machine because I know that EISA drivers will be
written sooner or later :-)

But what I want to know is this: Is there any reason to not get a local bus
machine? I intend to only run unix (well, maybe OS/2 too :-). I really want
to run XFree86 -- that is my main application.

So, are there any local bus video/SCSI controller drivers out there?
Are any being worked on? Or is local bus inherently incompatible with
unix?

thank you for you time,

Dwayne Fontenot
Newsgroups: comp.unix.bsd
From: tri@niksula.hut.fi (Timo Rinne)
Subject: Re: 386BSD PARTIAL PATCH KIT NOW AVAILABLE
Reply-To: Timo.Rinne@hut.fi
Organization: Helsinki University of Technology
	<david.716436045@mlb.geomechanics.csiro.au>
	<1992Sep14.172427.1194@fcom.cc.utah.edu>
Date: 15 Sep 92 00:40:41

Would it be impossible to put all patched source files (not just
diffs) available, maybe in tar format. Then we, who have hacked kernel
to fit our needs could just cd to /usr/src and 'tar xvf'. Then just
recompile patched parts of the system (kernel and a few system binaries).
Much easier than sexy automatic patch installation systems, IMHO.

-- 
  I Timo Rinne         I Cirion oy      I Working computer hardware is a lot I
  I Timo.Rinne@hut.fi  I PL 250         I like an erect penis: It stays up   I
  I tri@cirion.fi      I 00120 HELSINKI I as long as you don't fuck with it. I

     Hi! I am a .signature virus. Copy me into your .signature to join in!
Newsgroups: comp.unix.bsd
From: eschwart@netcom.Netcom.COM (Eric Schwartz)
Subject: Installing the 'barebones' 386bsd
Date: Sun, 13 Sep 92 06:40:42 GMT
Organization: Netcom Online Communications Service
Distribution: comp

A few days ago I downloaded the file that contained the binary image of
the distribution disk for 386bsd (dist.fs.Z, at a site I can't remember now).

I successfully got the file in binary mode, uncompressed it, and then
puzzled over what I was to do with a file with an '.fs' extension.
How do you get this onto a 1.2 mb floppy so that it becomes bootable?

I am interested in getting 386bsd on a machine with (at least for the 
moment) very minimal disk space.  I'm hoping to use the startup floppy
to make a SLIP connection to another site, then get the rest via SLIP.

Any advice will be eagerly received!

Thanks,

Eric
--

Eric Schwartz
WhyaNeXT!eric@netcom.com (NeXTmail spoken here)
work )408( 279-7191
FAX  )408( 279-7167

"A five is an old four."--from 'The Silly Record' by Stoo Hample

-- 

Eric Schwartz
WhyaNeXT!eric@netcom.com (NeXTmail spoken here)
work )408( 279-7191
FAX  )408( 279-7167

"A five is an old four."--from 'The Silly Record' by Stoo Hample

Newsgroups: comp.unix.bsd
From: cproto@marsh.cs.curtin.edu.au (Computer Protocol)
Subject: Re: Some more on NMI problems (some meager advancement)
Organization: Curtin University of Technology
Date: Tue, 8 Sep 1992 09:37:33 GMT

rivers@ponds.uucp (Thomas David Rivers) writes:


>Well, I thought I would relay my current status with the NMI
>investigation.

>  Right now, I'm thinking it has something to do with an IDE
> controller/disk drive, so I have been examining the wd.c driver
> trying to divine what it might be; without too much luck. (I 
> know very little about the IDE/WD disk controllers.)

[STUFF DELETED]

>  - Dave Rivers -
>   (rivers@ponds.uucp)

I'm also experiencing the problem. I disagree with the IDE controller
idea. I still think it's a spurious parity error. Note that the NMI
interrupt reports the value of I/O port 61. This value has the highest
bit set which indicates a parity error. But after running QAPLUS for
several days I'm convinced my memory is ok.

Could it be some sort of setup problem - e.g. wait states which can
be configured in my AMI BIOS.

BTW I do have a IDE controller/disk so Dave might be right.

Regards - Tibor Sashegyi (cproto@abel.cs.curtin.edu.au)
From: adrian@ibmpcug.co.uk (Adrian Hall)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD & COMPAQ 486/33
Date: 8 Sep 92 11:50:33 GMT
Organization: The IBM PC User Group, UK.

In article <92252.095938HEUER@DMSWWU1A.UNI-MUENSTER.DE> Stephan Heuer <HEUER@DMSWWU1A.UNI-MUENSTER.DE> writes:
>I have 386BSD 0.1 running on a Compaq Deskpro 386/20 with 387,
>ethernet and 60MB hard disk. 0.1 refused to boot, but I had 0.0 running
>so I used the 0.0 boot block. I just copied the first 8k from the 0.0
>boot disk to the 0.1 boot disk and voila ... I have *not* changed my 0.0
>disklabel on the hard disk!

And I had lost hope of ever running 0.1 on a Compaq.

Is there an archive with the 0.0 boot disk on it? Could you send me
a uuencoded version + instructions of what you did? Or post it to the
net - I am sure this will be helpful to a number of people.

Adrian

-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Tue, 8 Sep 1992 19:52:18 GMT

In article <1992Sep8.134824.5149@pegasus.com>,
richard@pegasus.com (Richard Foulk) writes regarding the lack of
termcap in Posix:

| A good example of the problem that half a standard (POSIX) creates!

If POSIX is half-a-standard because it doesn't include Termcap then
unix is half-an-operating-system because it doen't include all the features
of VMS.  And any book is half-a-book because it doesn't include everything
from every other book on the face of the earth.

You solve problems one step at a time.  If you believe that a partial
solution to a problem is worthless, and that only complete solutions that 
comprise life, the universe, and everything, are meaningfull, how do
you ever get out of bed in the morning?

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
From: aw2t+@andrew.cmu.edu (Alex R.N. Wetmore)
Newsgroups: comp.unix.bsd
Subject: 386bsd questions
Date: 5 Sep 92 17:38:22 GMT
Article-I.D.: andrew.MeeK4CS00Vp801tSYg
Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA

A few questions that I have:

1) With the network, it doesn't seem to start unless I run ifconfig
manually. I have added the line:
ifconfig ec0 inet 128.2.111.111 netmask 255.255.0.0
in /etc/netstart, but my nameservers don't seem to work until i run the
same command manually from a root login.

2) My com1: port locks up.  There is something about a tty_ring.c
replacment in the FAQ, but I couldn't find it.  com2: works fine.
2b) is there support for com3: and com4:?

3) is there a ansi driver for the console with better emulation.  For
now I have been using a z29 and a pc on com ports, but with one of the
out and two people who use the machine (my roommate and i), it would be
nice to have two working terminals.  The driver doesn't seem to emulate
a vt100 or ansi very well though, and is missing a lot of attributes
(like rev-video).

4) I have 6 megs unpartitioned on my hard drive.  Is there a way to add
this as swap space.  I assume I have to disklabel and newfs it, but I am
not sure how to access it from bsd?  Do I make a partition with dos
fdisk or norton and work from there?

5) The distributed kernel is about 400k or so.  After compiling the
default kernel, I had a kernel of 460k or so.  What has been added? 
Mostly just courious.

otherwise, thanks to those who have gotten this project out of the door.
 Everything is running great!

alex
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD #!/bin/csh
From: tom@afthree.as.arizona.edu (Thomas J. Trebisky)
Date: 11 Sep 92 18:49:29 GMT
Distribution: comp
Organization: University of Arizona, Tucson, AZ

Timo.Rinne@hut.fi writes:
>386bsd 0.1 doesn't seem to respect #! in beginning
>of the shell scripts, Anyone knows why? Fixes?

I am kinda shooting from the hip, but I think this kind of thing gets
handled in kern/kern_execve.c, you might want to take a look there.

I expect some some simplification was done in the free version rewrite.
The exec header is read and magic number is checked against ZMAGIC and
that is it.  You might want to hack it and check the first 16 bits
against "#!" and figure out how to invoke the interpreter of your
choice.

If "#" gets you to the sh in the current version, it is a mystery to me
how it works, unless "sh" itself is handling it.
--
	Tom Trebisky	ttrebisky@as.arizona.edu
...."There's no sense in being precise when you don't even
.... know what you're talking about." 
                       - John von Neumann  
Newsgroups: comp.unix.bsd
From: cchase@cs.cornell.edu (Craig Chase)
Subject: Re: Help: 386bsd NFS Filename Truncation
Organization: Electrical Engineering, Cornell University, Ithaca NY
Date: Tue, 8 Sep 1992 17:14:15 GMT

In article <92252.103621AI4CPHYW@MIAMIU.BITNET>, <AI4CPHYW@MIAMIU.BITNET> writes:
|> [..]  After some thought I realized
|> that I could do an NFS mount of another Unix machine (an Intergraph
|> CAD server running Clix, I-graph's flavor of Unix) and use that disk
|> space to hold the source distribution.
|>  [...]
|> I found differences.  First, the ownership was different (the files on
|> the local disk were owned by root and the copies were owned by 32767
|> (not a problem for chown, but still :)  Second, and more important,
|> the long filenames were truncated.  

First: The uid 32767 is *nobody* in NFS land.  When you NFS mount something without 
the -root option (in /etc/exports on the server machine), root on the client machine 
is translated into nobody on the server machine.  This is for security (i.e. it's 
supposed to work that way).  
Solution: chown, and consider changing /etc/expors on the Clix machine.

Second: SYSV (pre release 4) only allowed 14 (or there abouts) characters in the
filenames.   Since you're writing the files onto a SYSV variant of unix,
all filenames are truncated to this length.
Solution: don't use SYSV :-)

Craig

-- 
------------------------------------------------------------------------
| Craig Chase            |          This space for rent                |
| cchase@ee.cornell.edu  |                555-8968                     |
------------------------------------------------------------------------
From: mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Newsgroups: comp.unix.bsd
Subject: Re: How to extract src01 files?
Keywords: 386bsd
Date: 6 Sep 92 14:07:26 GMT
Organization: University of Western Ontario

rkrouse@netcom.com (Robert K. Rouse) writes:

> 
> 
>   I just install bsd and now i want to look at the source.
> 
>   I move the src01 files into a directory.
> 
>   How do i extract them?  What format are they in?

I was able to extract them by:

go into srcdist directory and    ln * /tmp
go into  /tmp  and type   extract src01

I found that extract was missing, and I had to     mount /dev/fd0a /mnt
(mount dist fs floppy in A:), then look for the extract program.

I found extract in one of the .Z files.  I was able to  cpio -i -d filename
(I think I remembered that one ok)

For some stupid reason, extract is placed in the  /tmp directory during the
install, and when install reboots your machine, it wipes all of /tmp

mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Western Business School  --  London, Ontario
Newsgroups: comp.unix.bsd
From: torda@igc.ethz.ch (Andrew Torda)
Subject: Fixed: Runs at 8MHz, Crashes at 33MHz, 386bsd
Summary: buy faster memory
Organization: Computational Chemistry, ETH, Zuerich
Date: Tue, 8 Sep 1992 07:07:31 GMT

Some time ago, I complained with the following problem:

     At 8 MHz, my machine appears perfectly stable.
     At 33 MHz, I get repeated trap type 12 panics.
     
     What can be dependent on timing like this ?
     If there are any suggestions as to where I can insert
     debugging lines ?
     
     I am not sure if this particular panic (trap type 12) holds all
     the answers. The machine (at 33 MHz) has often done a
     crash/reboot and wiped the errors off the screen.
     
     Machine details:
     386 clone (Blackship), no maths chip, 8M memory
     ATI motherboard (ATI-386/B2-33, 64K cache)
     AMI BIOS (04/09/90)
     video: ET4000 based, DFI VG-5000 with 1 Mb
     pc0 <color> at 0x60 irq1 on isa
     com1 at 0x3f8 irq4 on isa
     com2 at 0x2f8 irq3 on isa
     wd0 (MAXTOR LXT-213A> at 0x1f0 irq 14 on isa
     fd0 drives 0:1.2M, 1: 1.44M at 0x3f0 irq 6 drq2 on isa
     
The most concrete suggestions were to either add wait states or buy
faster memory. Couldn't add any more wait states, but I managed to
swap 8Mb of 80ns simms for 70 ns simms.

Instantly, I could rebuild kernels or run my little crash program
which simply allocated ever increasing amounts of memory and scribbled
through it.
The peculiarity is that with the old memory, I had been able to run
dos, windows in enhanced mode and even SCO unix.
It would still be nice to know what the cause is and why 386bsd
provokes the problem.

Thanks to several, especially forsyth@minster.york.ac.uk
-Andrew
-- 

Andrew Torda, Computational Chemistry, ETH, Zurich, torda@igc.ethz.ch
Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Re: 386bsd -- The New Newsgroup
Keywords: newsgroup 386bsd news group
Organization: Curtin University of Technology
Date: Wed, 9 Sep 1992 01:50:20 GMT

wjolitz@soda.berkeley.edu (William F. Jolitz) writes:

>	comp.os.386bsd		(general questions and trivia)
>	comp.os.386bsd.kernel	(discussion on kernel content/structure)
>	comp.os.386bsd.windows	(ditto, on windowing systems like X)
>	comp.os.386bsd.sharedlib (shared library and programming environment)
>	comp.os.386bsd.net	(networking topics)
>	comp.os.386bsd.bugs	(new bugs)
>	comp.os.386bsd.ann	(announcements, fixes, additions)

Sounds great. - The fragmented groups should make reading easier 'cause we
won't have to read the stuff we are not particually interested in.

>Lynne Jolitz.

Colin.

--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Organization: Taronga Park BBS
Date: Wed, 9 Sep 1992 01:46:24 GMT

In article <1992Sep08.085437.419@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>In article <QA2J6LM@taronga.com> peter@taronga.com (Peter da Silva) writes:
>>Sorry, if you have to provide your own termcap you're back where you started:

[silly "if you have to provide..." lines deleted]

>The termcap library is *SMALL*.

And it's (more importantly) standard. If it had to be provided by every
application it wouldn't be.

>It's better if it's on every system, but
>it's small enough that it can be provided as part of your application and
>not be terribly visible.  Emacs does that, or did at one point (although
>emacs is not something I like using as an example).

Proof. Emacs uses its own terminal independence database. So does every
editor on CP/M, where Termcap isn't a standard. So you have to configure
every application independently. "Oh", you say "termcap is so standard
now nobody would ever do that". Not so. AT&T did.

THAT is the point of having, and providing, a standard set of interfaces.

POSIX wimped out on too much of the API, and what remains isn't enough.

>1.  Pnews and Rnmail work quite well with 1003.2 utilities.

Mail isn't part of 1003.2.

>3.  As for mail, tell you what, Peter:  why don't you come up with a mail
>system (reader, sender, interface, system-to-system interface, file format,
>filesystem layout, etc.) that can work on all systems, and then I'll add the
>code to t?rn to support that.

I don't need to. It already exists. The name varies slightly (rmail/smail/
sendmail) but the *interface* is pretty much standard.

I don't know why you're taking this position, that basic things like
termcap and mail are optional. They're not.
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd -- The New Newsgroup
Date: 9 Sep 92 19:23:26 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu

In article <1992Sep9.022007.4473@cs.sfu.ca> bremner@cs.sfu.ca (David Bremner) writes:
>...More importantly, why comp.os.386bsd,...

Because that's what it has been called since 1989 -- 386BSD! 250,000+ people
can't be wrong.

Lynne Jolitz.
Newsgroups: comp.unix.bsd
From: gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart)
Subject: Anyone ported GNU-make to 386BSD ?
Organization: Technische Universitaet Muenchen, Germany
Date: Sun, 6 Sep 1992 00:40:52 GMT

I think the subject says it all.

I need gmake to install the GNU-netfax package. It would be much work
to rewrite the package to be compatible to usual make.
After playing aroung with some defines I got gmake compiled but it 
keeps core-dumping.
So if anyone ported the GNU-make already (or even the FAX-package)
please let me know.

  Ralf "Snake" Gebhart


----------------------------------------------------------------------------
Ralf 'Snake' Gebhart                     Techn. University Munich
System-Administrator           Email: Ralf.Gebhart@Informatik.TU-Muenchen.de
Newsgroups: comp.unix.bsd
From: david@mlb.geomechanics.csiro.au (David Le Blanc)
Subject: Re: 386BSD - Seems to stop my disks from booting...
Organization: CSIRO DIT (Melb.)
Date: 14 Sep 92 03:16:23 GMT

andrew@zone4.ocunix.on.ca (Andrew Low) writes:
>In article <kjb.716286770@godzilla.cgl.citri.edu.au> 
>kjb@cgl.citri.edu.au (Kendall Bennett) writes:
>>120M Western Digitial 2120 hard disks (WDC AC2120M). 

>IDE drives *should* be used in their native geometry, this often means
>... That and find out the native geometry of
>your IDE drive, it might make all the difference in the world.


I have a WD 120M 'WDC 2120' (It has the large 'Caviar' label on it.

The geometry I use is type 47..

Heads 8, sectors 35, cyl 872

--
David Le Blanc                         :
Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
P.O. Box 54 Mt Waverley 3149	       : in Alien^3.
Newsgroups: comp.unix.bsd
From: cs120323@rucs2.sunlab.cs.runet.edu (cs120323)
Subject: pascal compiler for 386BSD
Organization: Radford University
Date: Thu, 10 Sep 92 03:07:26 GMT

I am looking for a pascal compiler for 386BSD Unix.
the source code needs to be in C as that is the only 
compiler I have on my system at this time.

My name is Dave Scardina and my internet address is:

cs120323@rucs2.sunlab.cd.runet.edu

Thanks in advance for your replies

Dave S.
From: osynw@terra2.oscs.montana.edu (Nathan Williams)
Newsgroups: comp.unix.bsd
Subject: 386 Buglist status report
Summary: Still on its way
Keywords: patience is a good thing
Date: 7 Sep 92 22:37:55 GMT
Organization: Montana State University

Sorry for the long delay on the buglist, but I just got time this
weekend (Labor day in U.S.A., for those outside) to work on the
list a little more.

1) I have added a few more bugs, and have some fixes for others, but
I haven't gotten a whole lot more done with it.

2) If you have posted a fix to the net, PLEASE can I have you send it
to me via email to "osynw@terra.oscs.montana.edu".  Since pulling stuff
from the newsgroup is sometimes sporadic, I sometimes get old fixes,
or bad fixes or non-fixes.

3) I think I am going to post a project list of things I see that should
be done to make 386BSD more stable.  Take it for what it is worth.

If/when I get some more stuff done on it, I will post it again.  If I don't
get much of anything done by this coming weekend, I'll post what I have
and try to get to the rest later.


Thanks for your patience.


Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home.  Anyone  interested
work: (406) 994-5991         |  in a used Sys. Admin., with alot of 
home: (406) 586-0579         |  good hacks left?
Newsgroups: comp.unix.bsd
From: stark@cs.sunysb.edu (Gene Stark)
Subject: Re: How to make mwrite work?
Organization: SUNY at Stony Brook Computer Science Dept.
Distribution: usa
Date: Tue, 8 Sep 1992 12:36:42 GMT

>How does one use mwrite correctly:
...
>Everything responds with "open(): no such file or directory.  astro.zoo
>is definitely there.

I had a similar problem: after installing the bin distribution, "mcopy"
worked, but "mdir", "mcd", "mwrite", etc. gave errors such as you describe.
After recompiling the source from scratch, things worked.  I don't know
the explanation.  I can now read, write, and dir both floppy drives and
my DOS partition on the hard drive.

							- Gene Stark