HDTenEightyP/NetNews huggingface dataset:
From: mod@westford.ccur.com (Michael O'Donnell 508-392-2915)
Subject: EISA, Xwindows, graphics, WD7000 SCSI
Organization: Concurrent Computer Corp.
Distribution: na
Date: Thu, 9 Apr 1992 21:02:35 GMT



I'm only moderately uninformed regarding EISA, Xwindows and
BSDJ, so I was wondering if the following is unreasonable:
I want to have BSDJ on a 486 box with a bus mastering EISA
graphics card with enough processing power and RAM onboard to
run the entire X server, so the 486 isn't saddled with all that
graphics bit bashing.  Resolution would have to be a MINUMUM
1280x1024, and I can at least HOPE to have 12bits per pixel
(R/G/B -> 4/4/4) but that may require too many dollars.  How
tough would it be to do this?  I am interested in organizing
a group purchase of the appropriate stuff for two important
reasons: 1) I'd hope to get a volume discount, and 2) I'd know
that I wouldn't be the only one in the world trying to run BSDJ
with an oddball Xwindows configuration unsupported by the rest
of the BSDJ gang.  Let me know if you'd be interested in "such
a deal", assuming that we can all agree on what we want.

Also, I have a WD7000 SCSI controller (no computer, just the
controller and some drives, so far...) and I'd like to hear
about it if anybody has a BSDJ driver for it.  I'd be spastic
with gratitude if anybody has BSDJ actually *booting* from a
WD7000, but I suppose even expecting a working driver is a bit
much at this point.

I'm sitting here with $$$$ waiting to buy a UNIX box and BSDJ
has made it look pretty certain that it'll be a 486DX of some
sort, even though that nasty, stinking, stupid, useless, dain
bramaged ISA/EISA architecture will be beneath it (and I *DO*
mean "beneath" - aacchh, icky-poo!).  I came within inches of
buying an Amiga 3000, but Commodore wouldn't know a market if
it bit'em in the (ahem!) nose.  What I'd really like to own is
one of the boxes my company makes, with three 68040's on a 6U
VME card with our symmetric, realtime, multiprocessor UNIX, X
windows, full networking, etc.  But we just get the runaround
when we try to get an employee discount, so an MSDOG box will
have to suffice...  Life is cruel!                  ;->

 ------------------------------------------------------------------
 Michael O'Donnell     mod@westford.ccur.com     uunet!masscomp!mod
 Concurrent Computer Corporation     Westford, MA     (508)392-2915
 NOTE:  Opinions I express are unlikely to be those of my employer.
 ------------------------------------------------------------------
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Newsgroups: comp.unix.bsd
Subject: Version 0.1?
Date: 8 Apr 92 16:47:08 GMT
Article-I.D.: unx.1992Apr08.164708.29521
Organization: SAS Institute Inc.


  Well, it's time for my weekly post - or at least it seems to be weekly
  now.

  Don't get me wrong; I'm not complaining (it's kinda hard to complain
  about a "freebie" i.e. beggars can't be choosers) I'm just anxious to 
  try an get started...

  Does anybody have any updated idea about when to expect the new
  *real* version 0.1?  It's been 'sometime next week' for a couple
  of weeks now...

  Hopefully, this promised version will fix the problems I have
  booting.

  Just to possible help someone else, I was able to boot the floppy
  (the 3/17/92) release when I put in a CGA card (using a hercules 
  monitor in CGA emulation mode) - and slowing the speed down to 8MHZ,
  *and* pressing the 'd' key.  

  Once booted, I was able to determine a disktab entry (for my ancient
  micropolis 1325 (that's right 1325, not 1335) and get everything
  installed on the hard disk... *but* when booting off of the hard
  disk, no combination of speed/key-presses get's me past the
  lock up.

      - Anxiously waiting -
        - Dave Rivers -
      (rivers@ponds.uucp)
-- 
UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express
Newsgroups: comp.unix.bsd
From: pace@blitz.com (Pace Willisson)
Subject: SCSI boot for 386BSD
Organization: Blitz Product Development Corporation
Date: Sat, 11 Apr 92 15:52:14 GMT

I just posted the sources for my scsi boot programs to alt.sources
with the subject "SCSI boot for 386BSD".  (I would have put them here,
but someone complained the last time I posted a source file to this
group.)

Sorry, but it is still not packaged for easy use.  If that's what you
need, hang on a little while longer - someone's working on that, and
he'll be posting his work soon.


Here is the top of the README file:

This package contains programs to support booting from a SCSI drive
using an Adaptech 1542 controller.  I did the work in my port of
the net2 kernel, so there may be some details that need fixing
for 386BSD.  (I'm eagerly awaiting release 0.1, since I'll be able
to sync with the rest of the network when it finally comes out.)
(Also, this release does not have the recent changes for the Archive
tape drive.  I'll make sure they appear in the next release.)

Anyway, think of this as a kit to build a boot program...  Or,
continue to be patient and look forward to the day that this is
all in the standard distribution.

Pace Willisson
pace@blitz.com
From: spedpr@thor (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: disktab
Date: 7 Apr 92 02:38:41 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

Does anyone have a disktab entry for a Seagate ST-1144A?

I've played around with a few entries but I keep getting errors. The most
common is bad format in bad144 file or something like that. I also had
some warnings when I used newfs about unallocated sectors so I think my
disktab isn't quite right.

I don't have any spec for my system. I don't even know what controller
I've got (aprt from it's an IDE). The only info I can get from the
machine is 1021 cyl, 7 heads and 35 sectors (122Mb) which I used for nc,
nt and ns respectively.

This is one area where Linux really leads the way. I think it uses the
bios to sort this out, whatever it does it's totally automatic.

-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@thor.cf.UUCP or ...!uunet!mcsun!ukc!cf!thor!spedpr
+++
From: bvickers@bonnie.ics.uci.edu (Brett J. Vickers)
Subject: Adaptec SCSI boot disk for 386BSD
Newsgroups: comp.unix.bsd
Organization: Univ. of Calif., Irvine, Info. & Computer Sci. Dept.
Date: 7 Apr 92 03:01:04 GMT
Distribution: na

Has anyone successfully rebuilt the 386BSD kernel using the Adaptec
SCSI driver that was recently posted here by Pace Willisson?  If so,
will a boot image be made available anywhere anytime soon?  I'd like
to install 386BSD to my hard drive, but I'm kept from doing so
by the lack of said driver.

--
bvickers@ics.uci.edu | "Wherever the real power in a Government lies, there
brett@ucippro.bitnet |  is the danger of oppression." - James Madison
From: smv@apollo.hp.com (Steve Valentine)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD - I solved my boot problem
Date: 8 Apr 92 01:51:08 GMT
Organization: Hewlett-Packard Corporation, Chelmsford, MA

In article <1992Apr6.232126.2518@raid.dell.com> james@raid.cactus.org (James Van Artsdalen) writes:
>> (It may be of interest to note that my current HD controller had problems
>> at bus speeds > 10MHz.  I run my current bus at 8MHz and it works, but
>> my boot problems might've been due to marginal timings on the controller...)
>
>I *strongly* encourage people not to change the ISA bus clock away
>from 8 MHz (or 6 MHz).  Very few peripherals actually work that fast.
>Perhaps some hard disk controllers do, but that's only one of a dozen
>things hanging off of that bus (keyboard controller, VGA, etc).

Please forgive a question from a PC neophyte:
Does this advice apply to EISA bus systems as well?
Does this mean that it is foolish to go out and buy a >25-MHz 486 EISA system
if you might want to plug something other than state-of-the-art EISA boards
into it?  (In addition to SOTA boards that is.)

Are there separate EISA-specific clock lines which let you run EISA boards
fast and ISA boards at 8MHz?

Also, has anybody booted 386BSD (BSDJ) on an EISA system yet?
Someone else postulated that while 386BSD doesn't support EISA yet,
supported ISA boards plugged into an EISA bus should work.

I currently have no machine at home, and have been thinking about bootstrapping
my way up to a fast 486 EISA system with BSDJ and cheap ISA boards to start out.

If this won't work, does anybody have a clue about how you would go about
porting BSDJ to an EISA system?  (Without sinking too much money in slower gear)
-- 
Steve Valentine - smv@apollo.hp.com
Hewlett-Packard Company, Apollo Systems Division, Chelmsford, MA
Hermits have no peer pressure. -Steven Wright
Newsgroups: comp.unix.bsd
From: vepaepck@immd4.informatik.uni-erlangen.de (Volker Paepcke)
Subject: 386bsd & NFS??
Keywords: 386bsd NFS
Organization: CSD., University of Erlangen, Germany
Date: Fri, 10 Apr 1992 15:56:26 GMT

Hi,

We got 386BSD up and running on a no-name 386 (AMI BIOS/C&T chips). After
getting a new kernel with INET defined compiled (and being able to use our
NE 2000 board) we tried to go one step further and add in NFS. Yet, this does
not work out as expected (i.e. boot) - during boot loading (before any
messages have a chance to appear at all) the screen goes blank and the machine
does a reset.

We just added "options NFS" to our config file - is there anything else to
be observed? Has anyone gotten the 3-17-92 version to work with NFS so far at
all?

Also, we're observing some pretty strange behavior of the 386 - after rebooting
or during power-up the PC more often than not does not find/execute the boot
loader on the hard disk - only in 1 out of 4 times (on the average) does it
start up as expected. Did anyone out there experience something like that, too?

Any replies appreciated!
From: pjh@mccc.edu (Pete Holsberg)
Newsgroups: comp.unix.bsd
Subject: Re: The great BSD name-off...
Date: 14 Apr 92 17:07:06 GMT
Distribution: usa
Organization: The College On The Other Side Of Route One

In article <1992Apr13.160903.17738@NeoSoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes:
=In article <id.57VO.87G@ferranti.com> peter@ferranti.com (Peter da Silva) writes:
=>"Free S D" or "Freenix".
=
=Pnix or Penix, because I like the thought of a really obscene-sounding Unix...

Great. Then we'll have Pnix envy on computers!

Pete
-- 
Prof. Peter J. Holsberg      Mercer County Community College
Voice: 609-586-4800          Engineering Technology, Computers and Math
FAX: 609-586-6944            1200 Old Trenton Road, Trenton, NJ 08690
Internet: pjh@mccc.edu       Trenton Computer Festival: April ??-??, 1993
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Problems with RLL controller and 386bsd?
Date:  7 Apr 92 06:53:05 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

Yesterday, after backup of my disk I tried to boot 386bsd from
the 5in dist.fs.

The system came up identifying the recognized devices
COM,FD,HD at the correct I/O locations and IRQs and then hangs
at <color>, doing an immediate cold reboot at key hit.
I figured out after several trys (it clears screen very fast) the following
message:

panic: trap
syncing ... trap type = 12
code = fe030000 eip = fe011c66
cs = 8 flags = 10282 cr2 14 cpl 12
dumping to dev 1, offset 0
dump offset bad

(... clears screen and reboots ...)

The hardware configuration:

noname 386DX/20 with Phoenix BIOS, 8MB RAM
Optima VGA Tseng ET3000, 512K
common multi functions card (2 COM + 1 LPT + 1 Game)
>>> DTC 5280 RLL Controler with ST4144R (Disk 0) + ST251R (Disk 1)
(other cards were pulled for the experiments)

I suppose that the hd controler is the problem. It has an onboard ROM
(format + bootup) and gets the disk configuration from a disk sector 
and stores it in a reserved ram at seg 0xcb80 (real mode). BTW, it has
26 sectors/track, not the common 17.

Has anyone positive or negative experience with such a configuration, and
can verify this?

(The disk contents were not touched, fortunately :-)

Greetings 
Holger


-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | X.400: /S=veit /O=du9ds3 /P=uni-duisburg
|  |/    Inst. f. Dataprocessing |        /A=dbp /C=de
Newsgroups: comp.unix.bsd
From: ablassme@Informatik.TU-Muenchen.DE (Klaus Ablassmeier)
Subject: booting BSD386 with a conner type 55 (60MB) ?
Organization: Technische Universitaet Muenchen, Germany
Date: Wed, 8 Apr 1992 18:04:08 GMT

Hi BSD386 folks!

Did anyone succed to get BSD386 running on a harddisk
type 55 on compaq deskpro/20 ?

I got disklabel running (obviously havimg made all the
required disktab entries) but the newfs command reports
a 'floating point exception' and doesn't complete. (btw 
I have a numeric copro installed!)

Anybody to explain this strange behaviour to me? What am
I doing wrong ?


Klaus Ablassmeier        
ablassme@hphalle3.informatik.tu-muenchen.de

Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: mounting fd0
Reply-To: Rich@Lamprey.Gal.UTexas.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Tue, 14 Apr 1992 05:17:52 GMT

In article <1992Apr13.210901.2384@uwm.edu> knie2586@csd4.csd.uwm.edu (Robert Joseph Knier) writes:
	   How do you mount the floppy drive? - I would like to backup some of
   the new diffs and utils.  From what I could gander, one would use the 
   'disklabel -r -w fd0 floppy5' command (5 1/4 drive) then a 'newfs fd0b'.
   This doesn't seem to work though.  Any suggestions?  Thanks in advance!

If all you want is backups you can use GNU tar which comes with the
system.  The -M option writes multiple volumes.  The only catch is
that you can't write compressed multi-volume archives simply using tar
-zM.  Maybe you could pipe compressed tar output (tar czf - ...) to
something equivalent to mr.  I plan to look at this eventually....
--
From: cd28+@andrew.cmu.edu (Christopher Davis)
Newsgroups: comp.unix.bsd
Subject: Token ring
Date: 14 Apr 92 19:25:35 GMT
Organization: Freshman, Electrical and Computer Engineering, Carnegie Mellon, Pittsburgh, PA

I was wondering. Does 386BSD work with a token ring board?





The above opinions are not the personal views of the Andrew Message System.
Newsgroups: comp.unix.bsd
From: pace@blitz.com (Pace Willisson)
Subject: Re: scheduling (was Experiences with 386BSD)
In-reply-to: torek@horse.ee.lbl.gov's message of 11 Apr 1992 04:52:08 GMT
Organization: Blitz Product Development Corporation
Date: Sat, 11 Apr 92 16:03:23 GMT

>>I found out that the following program locks the machine ...
>>null.c:		main () {while (1) ;}
>>... The scheduling seems to be non-preemptive!?
>This suggests that ASTs are (still) broken.

I've added the missing ast stuff, and sent it to Bill last week.  If anyone
else really wants to do some low level hacking, I'll mail it to you.  Be
warned that there is a good bit of difference between 0.0 and my kernel
in these areas...

Pace
From: richard@pegasus.com (Richard Foulk)
Newsgroups: comp.unix.bsd
Subject: Re: BSD names (was: BSD on floppies)
Date: 11 Apr 92 14:52:07 GMT
Article-I.D.: pegasus.1992Apr11.145207.21518
Organization: Pegasus,  Honolulu

>
>When will you guys stop arguing about those stupid names. BSDI call
>their product BSD/386, Bill calls his stuff 386BSD. You don't have
>to be too bright to remember those two names. So please stop the
>bullshit and fix bugs, write new device drivers or contribute
>something else more useful.
>

Sounds good to me.  What's wrong with sticking with the name Bill gave it?


-- 
Richard Foulk		richard@pegasus.com
Newsgroups: comp.unix.bsd
From: bergt@informatik.tu-chemnitz.de (Birko Bergt)
Subject: Re: disktab
Organization: tu-chemnitz
Date: Tue, 7 Apr 1992 15:00:44 GMT

spedpr@thor (Paul Richards) writes:

>Does anyone have a disktab entry for a Seagate ST-1144A?

st1144a|Seagate 124MB IDE  B.B.:\
        :dt=ESDI:ty=winchester:se#512:nt#15:ns#17:nc#996:sf: \
        :pa#13824:oa#0:ta=4.2BSD:ba#4096:fa#512: \
        :pb#13824:ob#13824:tb=swap: \
        :pc#253980:oc#0: \
        :ph#226332:oh#27648:th=4.2BSD:bh#4096:fh#512:

   This is my /etc/disktab entry. It works without error messages.

>--
>  Birko Bergt at Chemnitz university, D.
>  bergt@informatik.tu-chemnitz.de or bergt@hrz.uni-bayreuth.de
>
>  X.400:  S=Bergt; OU=Informatik; P=TU-Chemnitz; A=dbp; C=de        
>          S=Bergt; OU=Hrz; P=Uni-Bayreuth; A=dbp; C=de
>  TU Chemnitz, Fachbereich Informatik  
>+++
From: jrv@sdimax2.mitre.org (VanZandt)
Newsgroups: comp.unix.bsd
Subject: Re: ftp'ing 386BSD
Summary: how to ftp multiple directories all at once
Date: 31 Mar 92 17:50:35 GMT
Article-I.D.: linus.1992Mar31.175035.5390
Organization: The MITRE Corporation

Craig Chase (cchase@theory.TC.Cornell.EDU) recently posted the following...

> FYI, the ftp server at ftp.uu.net understands how to tar up
> directories for you.
> 
> For example, to get the complete 386BSD source distribution...
> marvin> ftp ftp.uu.net
> login: ftp
> password: cchase@ee.cornell.edu
> 230- ....lots-o-messages......
> ftp> cd pub/OS
> ftp> bin
> ftp> hash
> ftp> get 386BSD.tar

When I checked out ftp.uu.net I found that this procedure would fetch
TWO copies of the source code - one packaged for 5.25" disks, and one
packaged for 3.5".  I've since read that the 5.25" version is a recent
addition - it may not have been there when Craig posted the message.
Regardless, some care is in order so as not to waste the bandwidth. 
(The FAQ suggests getting just the docs and binaries the first time
around - a good idea.)

                   - Jim Van Zandt (jrv@mbunix.mitre.org)
Newsgroups: comp.unix.bsd
From: kolstad@uunet.uu.net (Rob Kolstad)
Subject: New BSDI Info Phone Number
Keywords: BSDI, contact info
Organization: UUNET Technologies, Inc
Date: Wed, 8 Apr 1992 14:55:24 GMT

BSDI's information line has a new phone number.  In North America, please
call +1 800 800 4BSD.  The double 800 surprised me, but it does work.
Overseas phone access is via +1 703 876 5040.

The info@bsdi.com email address is also available.

					Cheers,
						Rob

-- 
         /\      Rob Kolstad           Berkeley Software Design, Inc. 
      /\/  \     kolstad@bsdi.com      7759 Delmonico Drive
     / /    \    719-593-9445          Colorado Springs, CO  80919
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: To make 386bsd coexist with DOS partitions??
Date: 8 Apr 92 23:08:01 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <1992Apr8.142645.21143@newshub.sdsu.edu>,
turtle@newshub.sdsu.edu (Andrew Scherpbier) writes:
> Why not change the boot loader to behave similar to the one for SCO
Xenix?
> It provides a boot prompt at which point one can decide from which
partition
> to boot, but also from which kernel.  I do a lot of kernel hacking and
I have
> to boot off floppy quite often because I screwed up /386bsd and I
can't seem
> to boot from /386bsd.old (eventhough the bootfd source claims you
should be
> able to...).  This boot loader would then have a timeout and a default
way of
> booting so that it will boot correctly after a power failure (heaven
> forbid!!!) or panic (never!!!) when nobody is around to manually boot
it.
>
> I have been looking at the xxboot and bootxx code to see how easy/hard
this
> would be, but right now I am working on a new console driver.  So if
someone
> else wants to take on the task of writing a new boot loader, we
should
> exchange some ideas.

I believe this has been mentioned before but there are a variety of boot
loaders
already out on the net that, I think, do what you want.  I use one to
manage my
DOS and ISC Unix partitions on my system.  It displays the partition
table and an optional comment line next to each partition.  You then
type '1', '2', '3' or
'4' to boot from that partition.  Another flavor will automatically
select the
currently active partition and boot if a response is not given within a
certain time interval.  This can be setup to automatically boot the unix
partition.  The program I am using is called 'bootmenu'. 

I have not used 386BSD yet because I have only SCSI drives but on ISC, the
bootstrap will assume /unix (I think this is the name).  If this is not what
you want (i.e. the new kernel is broken) you can hit the space bar during the
ISC bootstrap and it will ask you which kernel file you want to load.  The
386BSD bootstrap must do something similar to this (or at least could be made
to work this way with a relatively simple hack if you wanted).

I think that the two of these will do what you want with little or no 386BSD
code changes (except you may have to debug 'bootfd').
-- 
Gary Browning                   INET: gab10@griffin.cd.amdahl.com
Amdahl Corporation
1250 East Arques, Sunnyvale, CA 94088
Newsgroups: comp.unix.bsd
From: cproto@marsh.cs.curtin.edu.au (Computer Protocol)
Subject: Re: BSD names (was: BSD on floppies)
Organization: Curtin University of Technology
Date: Thu, 9 Apr 1992 17:07:15 GMT

grog@adagio.UUCP (Greg Lehey) writes:

>In article <1992Apr8.110359.10948@pegasus.com> richard@pegasus.com (Richard Foulk) writes:

>>Besides, the I J sillyness makes it seem like BSD386 came before 386BSD ...

>Yes, but it did. I'm not taking sides in this rift, but the fact is
>that Jolitz worked for BSDI before going his own way and bringing out
>386BSD. Even his articles in Dr. Dobbs and UNIX Magazin call it
>BSD386, not 386BSD.


Wrong, read the articles.

-- Tibor Sashegyi
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Compiling source
Date: 15 Apr 92 01:44:06 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

I thought I'd try and compile the source as a precursor to some hacking
to build an isolink ethernet driver. Well, first off, make depend
doesn't work and it's difficult to get patches down without a network
connection so I just ignored that and did make. 

Firstly, the shell doesn't understand [ so I ignored them as well :-).
I saw a mailing that said link /bin/\[ to /bin/test but there's no test
on my machine either, is this right?

Things went OK for a while until I got, "don't know how to make newvers."
Oh well, I had a look at newvers.sh but that doesn't work because
there's no [ or expr. Anyway, it seems to be a directory that isn't in
the make path. This brings up something else. What is the source
directory structure meant to look like?

I did a config in /sys/i386/conf which creates an obj directory at
/sys/compile/NAME. Now, newvers.sh resides in /sys/conf, what is it
doing there and what else is this directory for?

I've managed to get a kernel compiled by hand after mangling the
makefile in /sys/compile/NAME which I fully expected to have to do at
this stage of 386bsd's life but could someone enlighten me as to what
the source structure should be.

p.s. My signalvar.h was corrupted. I got the source floppy images from
ic.doc.src in the UK and this was the only file that was damaged. I
doubt, therefore, that it was my copy since the diskimage would not have
uncompressed, I could be wrong though. Anyhow, it's probably worth
checking the archive.
-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@thor.cf.UUCP or ...!uunet!mcsun!ukc!cf!thor!spedpr
+++
Newsgroups: comp.unix.bsd