HDTenEightyP/NetNews huggingface dataset:
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: 386BSD BETA-1 PATCH KIT AVAILABLE
Reply-To: terry@icarus.weber.edu
Organization: Weber State University  (Ogden, UT)
Date: Mon, 5 Oct 92 19:43:31 GMT

	I have just been notified by Chris that the Beta-1 patch kit has
been put in the public area on agate for download and mirroring to other
FTP sites.

It can be accessed as either:

	/pub/386BSD/386bsd-0.1/unofficial/patch-kit

or:

	/pub/386BSD/386bsd-0.1/unofficial/terry/beta.patch.kit

In theory, this will cause it to show up on the mirror archives soon; I
suspect that agate will be pretty busy for a while, so you may want to
download it from a more local site when it becomes available.


	This version of the patch kit has all known bugs that were in the
limited distribution alpha patch kits fixed.  Many suggestions from too
many people to mention here have been incorportated, including installing
all the patches without asking for confirmation each time.  I would like
to thank both Rodney Grimes (the beta beta tester) and Nathan Williams
(the bug list maintainer and patch collector) for their help in getting
this out the door.  I would also like to thank Chris Demetriou (who
runs agate, both for the excessive use of his "incoming" directory this
weekend and his work in general. 8-).


*	Special note to X users
	
	You will still have to add the recommended options to your kernel
	configuration file before rebuilding the kernel:

	option XSERVER
	option UCONSOLE

*	Special note to WD8013 users

	You will need to add the following option to your kernel configuration
	file to enable 16 bit transfers.  Do this only if you do not have
	Western Digital WD8003 or compatable cards in the machine:

	option WD8013

*	Special note to WD compatable ethernet card users:

	You will need to add the following option to your kernel configuration
	file if you are using a WD80x3 compatable ethernet card, but your
	kernel does not recognize it on boot.  DO NOT ADD THIS OPTION TO YOUR
	KERNEL CONFIGURATION IF YOU DO NOT HAVE A WD80x3 COMPATABLE CARD:

	option WDCOMPAT

Everything else you nead to know should be covered in the documentation
accompanying the patch kit software.



					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: FAQ questions: X386.
Date: 28 Sep 92 16:42:24 GMT
Article-I.D.: fcom.1992Sep28.164224.22530
Organization: Weber State University  (Ogden, UT)

In article <2AC68B02.12922@ics.uci.edu> bvickers@valentine.ics.uci.edu (Brett J. Vickers) writes:
>1. What are the minor and major device numbers for /dev/vga?
>2. Where can I find the patches for pccons and locore?
>3. Why is the installation information for X386 on 386BSD so
>   damn terrible?
>
>All these things should be in the FAQ, but there isn't one.  Help!

I disagree.  The buglist, the patches, and the topics you note here should
be in the FAQ (although it is getting musty and will be updated soon).

A possible exception is the /dev/vga numbers, which would not be a problem
if you run the install program provided with the current X distribution.
If you steadfastly refuse to use an install program to install something,
an obviously indefensable position, then you can type:

	mknod vga c 12 0

This is an exception because it truly is frequently asked, but it is only a
possible exception because, like 2 and 3, it is on the XFree86 FAQ which
is occasionally posted here (I believe by Amacio Hasty).

The "unofficial buglist" is a list of bugs.  While these may frequently
generate questions, they are not, themselves, questions, nor do I have
any problems whatsoever with the fine job Nate has been doing.

Patches have been generated by a number of people, myself included, and
my small efforts in this area have only been to organize them so that they
don't conflict with themselves.  The first "real" release of a patch kit
(Beta) is scheduled for 01 Oct 92.  It *does* include the X patches as 
well, but it is not intended primarily as a thing to make X work.  The
size of the kit, and it's ability to install new binaries (supported but
not currently used) make it unsuitable for inclusion in the FAQ.

The installation instructions are a result of programmers writing just
enough documentation to allow their efforts to be used by the majority
of other programmers out there -- in other words, 386BSD and associated
software is what Peter would refer to as "hackerware".  If you are a
technical writer, or you know one you want to volunteer, I'm sure any
efforts in this area would be greatly appreciated.


					Terry Lambert
					terry_lambert@npd.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: kzin@terminus.gatech.edu (John Rudd)
Subject: BSD/386 and 50Mhz 486
Summary: 2 questions
Keywords: maximum users, drivers
Organization: Georgia Tech College of Computing
Date: Wed, 30 Sep 1992 03:15:50 GMT

I'm looking in to running 2 486/50's running BSD/386 by
BSDI.  I need to know what multi-port boards it has drivers
for (since most of them only come with drivers for sysv), or
that I can get drivers for, and how many users people think it'll
support.

each will be EISA machines, networked to a third box that provides
a 56k line to the internet.  Each will have a 1.2 GB scsi drive (one
for users, one for news).  Both will play NFS server for the other.
I'm wanting to hang 24 users off of each machine.  That sound overtly
unreasonable? (no one will be doing anything off of the console..
except maybe regular terminal like things..definitely no heavy x work
or anything.  Also, most of the things I expect people to do are vi,
news, mail, and network chat/mud programs.  Probably some people will
be compiling stuff, but I don't expect it to be widespread)

(alternate configurations are welcome too, but try to keep the price
range of this setup in mind (under $30k for the two 486's and their
multiport boards))
John Rudd  --  kzin@cc.gatech.edu         ex- kzin@ucscb.ucsc.edu
All opinions expressed here are my own, and no one elses.
--If Happy Fun Ball begins to smoke, leave the area immediately,
  seek shelter, and cover your head.  Do NOT Taunt Happy Fun Ball.
Newsgroups: comp.unix.bsd
From: jdevries@apple.com (Jeff DeVries)
Newsgroups: comp.unix.bsd
Subject: [386BSD] How do I fix 'com0: silo overflow' problem?
Date: 27 Sep 92 23:26:42 GMT
Distribution: usa
Organization: Apple Computer Inc, Cupertino, CA

I've installed the bootstrap system onto my hard disk.  When I try to
use the /dev/com1 port, I occasionally get: com0: silo overflow

What's wrong?  Better yet, how do I fix it?

Thanks!
Jeff De Vries
jdevries@apple.com
Newsgroups: comp.unix.bsd
From: jlu@cs.umr.edu ( Eric Jui-Lin Lu )
Subject: {SOLVED + SUMMARY} Re: Help: Xconfig for Xfree86 ....
Date: Tue, 6 Oct 1992 03:09:59 GMT
Organization: University of Missouri - Rolla
Originator: jlu@mcs213i.cs.umr.edu

First of all, I'll like to thank those who help me out and who
make 386bsd and Xfree86.  I'm really happy now.

For those who are collecting Xconfig info, here is mine:

"800x600" 40  800 892 1044 1136   600 603 609 630
[NOTE: there are more than one combination.]

Hareware:
VGA MENTOR: ET4000 based (Turbo MegaVGA Chip and BIOS)
NEC 2A.

For those who do know much about Xconfig, here is some sugguestions:

1. READ X386 man page first.  It'll give you a rough idea about the
   structure of Xconfig.
   Note: Refer to Xconfig.sample when you're reading X386 man page.

2. Grab a copy of xclk from agate.berkeley.edu.  It was in pub/incoming/X386
   when I ftped it.

3. READ Bob Crosson's Xconfig.Notes.

4. Have your monitor's and adapter's manuals handy.

5. Run "xinit >& <file-name>", without quotes, to get your clocks
   setting.

Again, thank you all netters.


  --Eric  
-- 
***************************************---       Grad. student          ---*
* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
***************************************---   Univ. of Missouri-Rolla    ---*
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: device 0/0 0/1
Keywords: as0 sd0 boot swap root device
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sat, 3 Oct 92 18:41:45 GMT


I'm running 386bsd on a ah1542b with as0a as root, as0b swap, as0h /usr.
Yesterday I installed Julian Elischers (thank you, Julian), scsibeta2.1
release because my DAT tape (DEC TLZ04) was never recognized by the as
driver. With the above SCSI driver it is recognized.

But I have a strange behaviour when booting. I always get 
no swap space present (yet)   and  later: 
savecore: device not configured as0b.

I could not figure out where this string occurs in the kernel code. I did a 
strings 386bsd and the only string 'as' was in wdswfdwtas (or something like )
which I located in autoconf.c. The new driver is using sd0 instead of as0.
I'm not using wd0 (wdc0) in my config file. Should I? Presently I don't 
know whether my system is using swap space at all. Following the messages
it does not but I did a lot of kernel builds etc. on the system without
problems. I'd rather solve this problem than continue to live with it.

Any help/comments etc. are much appreciated.

--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

Newsgroups: comp.unix.bsd,comp.os.linux
From: peter@ferranti.com (peter da silva)
Subject: 386BSD and Linux SCSI device drivers.
Summary: Multiple SCSI units on a single SCSI id.
Organization: Xenix Support, FICC
Date: Fri, 2 Oct 1992 22:41:18 GMT

Do 386BSD or Linux support SCSI devices with multiple units? I am looking at
a cheap drive array consisting of 4 ESDI disk drives (Miniscribe 9380E or
equivalent) on a single SCSI-bus ESDI controller. The drives are, so far
as I can tell, unit 0 through unit 4. I would like to use these from a SCSI
controller.
-- 
Peter da Silva                                          `-_-'
Ferranti Intl. Ctls. Corp.                               'U` 
Sugar Land, TX  77487-5012
+1 713 274 5180                           Heb jij vandaag je wolf al geaaid ?
From: paul@frcs.Alt.ZA (Paul Nash)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD - what a pain to install!
Date: 27 Sep 92 08:17:36 GMT
Article-I.D.: frcs.1992Sep27.081736.13282
Organization: Free Range Computer Systems CC

Thus spake spel@hippo.ru.ac.za (Dr. Eberhard W. Lisse):

> I have an archive controller and a priam et-60 drive which
> works on a proprietary ms-dos backup software as Archive FT-60
> (and actually is amazingly fast on my 33 mhz 386 :-)-O)

As far as I can tell, 386bsd currently only supports Wangtek tapes.
If anyone has written an Archive driver, I will quite happily mail
or FTP a new tinybsd floppy to you.
 
 ---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---
 Paul Nash                                         paul@frcs.Alt.ZA
 Box 12475, Onderstepoort, 0110 South Africa         +27-12-5611879

 "Standards are great -- everyone should have one" (Kent Landfield)
From: donegan@stanton.UUCP (Steven P. Donegan)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD Questions
Summary: Memory Limits
Date: 27 Sep 92 14:33:34 GMT
Organization: Stanton Public Domain Systems, Stanton, Ca.

In article <53950@dime.cs.umass.edu>, shri@unreal.cs.umass.edu (H.Shrikumar) writes:
> In article <2013.416.uupcb@pcb.batpad.lgb.ca.us> mike.batchelor@pcb.batpad.lgb.ca.us (Mike Batchelor) writes:
> >
> >   this even an issue for 386BSD?  How about the Mylex and AMI
> >   brands?  Generic Taiwanese OPTI/AMI?  I read elsewhere in this
> >   group a reference to a 16Mb limit, but couldn't find any other
> >   details.  16M is a good amount to start with, but I would surely
> >   want to go to 32 or 64 later.
> 
>    If this 16 MB limit is dues to 24 bits of address on the ISA, then
> does it hold for memories (SIMMs) directly on the mother board ?
> On the Generic Taiwan OPTi/AMI boards ?
> 
> -- shrikumar ( shri@legato.cs.umass.edu, shri@iucaa.ernet.in )

There may be a 24 bit limit on the ISA (I don't have a hardware manual at
the moment) but why on earth would you be loony enough to want to put
memory on the ISA or EISA for that matter. There be wait states between
thee and the bus...


As to a limit of 16 meg of RAM that's rubbish unless you have a poorly 
designed motherboard (and in these days of 600$ US 486 motherboards you
should be able to replace a faulty design). My made in the USA 486/33 clone
handles 16 meg (actually 20 as there are 4 1 meg simms there as well as
the 4 meg simms) quite nicely. So there is no inherent design flaw which
precludes 32 meg usage at least in my board. For going the next leap to 64
meg - well I haven't done it myself and don't know offhand of any boards
with enough simm sockets at 4megX9 to accomodate 64 meg so you're on your
own :-)

By the way - what do you need 64 meg for anyway... Some major simulation?
Or far too many users for the CPU horsepower of a 486 :-)
-- 
Steven P. Donegan                     The opinions expressed here are mine
Senior Telecommunications Engineer    donegan@stanton.cts.com, stanton!donegan 
Information Services                  714-932-6055 voicemail
Western Digital Corporation           714-894-2246 uucp - nuucp no word
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: FAQ questions: X386.
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Wed, 30 Sep 1992 07:38:52 GMT

In article <2AC73B5E.15562@ics.uci.edu> bvickers@ics.uci.edu (Brett J. Vickers) writes:
>I wrote:
>>>1. What are the minor and major device numbers for /dev/vga?
>>>2. Where can I find the patches for pccons and locore?
>>>3. Why is the installation information for X386 on 386BSD so
>>>   damn terrible?
>
>terry@cs.weber.edu (A Wizard of Earth C) writes:
>>I disagree.  The buglist, the patches, and the topics you note here should
>>be in the FAQ (although it is getting musty and will be updated soon).
>
>Terry, I did not mean to imply that your 386BSD FAQ was not good.  On
>the contrary, it's wonderful.  Only one minor complaint about it
>though: there was only one section describing X386.  I think it would
>be nice if some knowledgeable person would put together a 386BSD/X386
>FAQ that dwells solely on installation and troubleshooting issues for X.
>
>>A possible exception is the /dev/vga numbers, which would not be a problem
>>if you run the install program provided with the current X distribution.
>
>My main problem appears to be that I have installed the X386 that was
>in agate.berkeley.edu:/pub/386BSD/0.1-ports/X386/X386-1.2E.bin.tar.Z-split.
>Unfortunately, that version did not come with any nice install scripts.
>As soon as I get time, I will take Amancio's advice and get the version
>in agate.berkeley.edu:/pub/incoming/X386.
>
>>This is an exception because it truly is frequently asked, but it is only a
>>possible exception because, like 2 and 3, it is on the XFree86 FAQ which
>>is occasionally posted here (I believe by Amacio Hasty).
>
>Ah, so there is such a FAQ.  Could this FAQ be made available on anon ftp
>sites, or possibly be posted more regularly?  I made sure to look for
>such a FAQ before I asked my earlier questions, but I didn't find it.
>
>Brett
>--
>Brett J. Vickers		 "Don't go around saying the world owes you
>bvickers@ics.uci.edu		 a living.  The world owes you nothing.
>				 It was here first."  - Mark Twain

There is a reason why there are two separate releases of X386.
From an X11R5 besides the xconsole problem, all the questions/problems
with X386 have been answered with the release in
agate.berkeley.edu:/pub/incoming/X386. The /pub/incoming/X386 release
is waiting for kernel changes. Please, don't ask me for what kernel changes!
I know that is sounds strange...

For questions such as the now famous "/dev/vga", please read the
readme file in /pub/incoming/X386. If you are experiencieng problems
with your mouse behavior such as in microsoft mode, just get
the release on /pub/incoming/X386. 

We  will prepared a FAQ before the week is  over and I will be
more than happy to send it to Terry.

Hope this helps,
From: jlu@cs.umr.edu ( Eric Jui-Lin Lu )
Newsgroups: comp.unix.bsd
Subject: help: Xconfig for Xfree86
Date: 5 Oct 92 02:53:42 GMT
Organization: University of Missouri - Rolla
Originator: jlu@mcs213g.cs.umr.edu

Greetings *,

I have asked for help last Friday.  Since I got no response so far,
I think I better asking for help again.  I have problem to start up
X in 386bsd 0.1.  I believe it's caused by Xconfig.  I have followed
the instruction in Bob Crosson's Tutorial to come up the following
numbers:

 "800x600"  50  800  1012  1204  1416   600  603  609  630

I tried that, but in vain.  Also, I tried xclk found in agate and
run with the following numbers:

 "800x600"  50  800   832  1032  1064   600  603  609  630
 "640x480"  50  640   672   872   904   480  483  489  504

but failed.

What I have in my Xconfig:

vga256
chipset "et4000"
virtual 1152 900
viewport 0 0
[NOTE: I don't have clocks setting since I don't know how to do it.]
Modes "800x600" "640x480"

VGA card: VGA MENTOR (based on Tseng's ET4000 Turbo MegaVGA Chip and BIOS)
          a little tin can shows 50.000 MHz
          (I assumed it's 50MHz)
Monitor:  NEC 2A  (max. 800x600)
          Horizontal frequencies: 31.5 and 35 (or 35.2?) KHz.
          Vertical   frequencies: 56, 60, and 70 Hz.

Help me!  Somebody.......


   --Eric
-- 
***************************************---       Grad. student          ---*
* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
***************************************---   Univ. of Missouri-Rolla    ---*
Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS STAFF)
Subject: fax software for 386bsd?
Organization: University of Western Ontario
Date: Fri, 2 Oct 1992 21:55:29 GMT

My modem is a fax capable modem.

Under dos/windows, I can use WinFaxPro to send and receive faxes.  I am
 am not interested in receiving faxes, just sending them.

Is there any fax software for unix based machines?  text or X11?


mark@student.business.uwo.ca (Mark Bramwell CS STAFF)
Western Business School  --  London, Ontario
From: venkat@uxh.cso.uiuc.edu (Venkat Swaminathan)
Newsgroups: comp.unix.bsd
Subject: XFree86 gives me a blank screen !
Keywords: X Xfree86 install
Date: 30 Sep 92 19:34:49 GMT
Organization: University of Illinois at Urbana

Hi folks,

I downloaded the XFree86 binaries from agate:/pub/incoming/X386 and have been
[unsuccessfully] trying to install XFree86. After I type 'sh startx' or 
'xinit' there is a 3-4 second pause and then the message "Waiting for X
server to begin accepting connections" followed by a number of periods - two
to a line. After a minute or two the screen just blanks and nothing short of a
reboot will get the screen back. The keyboard is apparently working because
of the disk activity pattern when I type a command etc.  I have spent hours
on trying out different values in the Xconfig file to no avail. I am using the
kernel binary from agate:/pub/incoming/X386/386bsd.kernel... whatever.

DETAILS:
	386/25 MHz machine with 4MB RAM/125MB HD; Diamond Speedstar VGA video
	card with 1MB video RAM; MAG PMV 1448 monitor; Microsoft compatible
	mouse on com1.

Any help will be appreciated either by email or USENET. Thanks !

Venkat
Newsgroups: comp.unix.bsd
From: ujlh@pool.info.sunyit.edu (James Henrickson)
Subject: Re: Catch What They're Saying About Us...
Organization: State University of New York -- Institute of Technology
Date: Fri, 2 Oct 1992 02:07:37 GMT

In article <1992Oct1.032323.6425@unislc.uucp> erc@unislc.uucp (Ed Carp) writes:
>Sean Eric Fagan (sef@kithrup.COM) wrote:
>
>: If I needed an OS to do work, it would probably be BSD/386.  If I were going
>: to install an OS on a machine for the express purpose of playing, it would
>: be either Linux or 386BSD (probably the latter, at least until networking is
>: available and stable in Linux).
>
>You might want to drop into comp.os.linux from time to time.  We've had
>networking in the kernel for some time.  It's pretty stable at the moment... :)
>
>I believe Ross Biro is the person who's doing the most with it...
>-- 


Linux has networking, but only for WD80[01]3 Ethernet cards.  I switched
to 386BSD because it supports my NE2000 clones.  :-)
-- 
Jim H.
*
* James L. Henrickson
* ujlh@sunyit.edu        "Some day I might have a real .signature!"
From: alan@ulka.zso.dec.com (F. Alan Jones)
Newsgroups: comp.unix.bsd
Subject: Re: Corruption in BIN01.56?
Date: 5 Oct 92 16:12:14 GMT
Article-I.D.: ninja.1992Oct5.161214.22538
Reply-To: alan@ulka.zso.dec.com (F. Alan Jones)
Organization: Digital Equipment Corporation


It is not a VAX problem.  I have a 3100 under EFT ULTRIX 4.3 that had
the same problem.  My theory is ftp.  You will not that the size of
the file on the the ftp server is correct.

To repeat the solution.  Check the size of files you have downloaded.
If a file is one byte to large, delete the last byte to aviod curruption
messages in your installation.  I used emacs (ESC > BS).

Alan
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: Re: X386 gives a bus error in ET4000EnterLeave()
Date: 5 Oct 92 14:22:15 GMT
Organization: ICEM Systems, Inc.

|> 
|> This problem at inb/outb occurs when the xserver does not run in the 
|> protection ring 0. The kernel patches to pccons accomplish that in the
|> CONSOLE_X_MODE_ON/OFF ioctl's. If they are not present, you get this 
|> fault. Also the xserver must be setuid root.
|> BTW, a simple stupid question: you may have done the XSERVER patches, but
|> did you rebuild the kernel with the XSERVER option in your config file,
|> and did you do a make depend?

Yes and yes (XSERVER is in config file and I did a make depend and make).

I'm going to try a clean pccons.c and locore.s  There might be problems in
the installed patches.
-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/* we are realizing infinite possibilities in exchange for our soul */
Newsgroups: comp.unix.bsd