HDTenEightyP/NetNews huggingface dataset:
From: ferrick@acsu.buffalo.edu (Patrick K. Ferrick)
Newsgroups: comp.unix.bsd
Subject: EISA: (informed) speculation wanted
Date: 7 Apr 92 16:01:45 GMT
Organization: UB


Seeing as how somebody else has already asked, I'll go ahead and
put out a request for some educated guessing on the part of those
who are more well-informed and knowledgeable than myself.

I am also looking forward to buying a 486 motherboard to run
386/BSD, and I am quite curious about whether (or if) it is at
all likely that this OS will support the EISA bus.  For that
matter, what I'd REALLY love is to get an EISA-based SCSI card
and so on.  

Before you flame the *(*&% out of me for asking for the world,
(considering that people are still hammering out tty bugs etc.)
let me say that what I'd like to hear about is the <probability>
that 386BSD will support this config and <when>.  I know thatwhat 
what I'm asking for is a major undertaking; I'm just wondering how 
many (if any) of you talented OS-types out there are
thinking about it, or perhaps working on it.  That's all!

Thanks in advance,
pat

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|  Patrick K. Ferrick / KA2AYK       |   Round up the usual suspects !!!!!    |
|  ferrick@autarch.acsu.buffalo.edu  |                           L.R.         |
|      BAN JUNK MAIL!!!!!!!          |                                        |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Newsgroups: comp.unix.bsd,comp.unix.sysv386,comp.periphs,comp.os.linux
From: dje@sspiff.UUCP (Doug Evans)
Subject: Which 1gig disk to buy?
Organization: Edmonton, Alberta
Date: Wed, 15 Apr 1992 16:59:48 GMT
Followup-To: poster

I want to upgrade my system with a 1gig scsi disk and was wondering if anyone
has any advice on ones to get, ones to avoid, etc. ...
I'd appreciate responses from satisfied owners as well as dissatisfied ones!

Fuji?
Seagate?
???

I'll be using it with Linux and/or 386bsd.

Please reply by email (Followup-To: poster).
1e6 thanks in advance.
-- 
Doug Evans                   |
..!{canada,uunet}!sspiff!dje | Vancouver 11, Calgary 0
dje@sspiff.UUCP (prefered!)  | There is no joy in Cowtown.
dje@ersys.edmonton.ab.ca     | But how 'bout those Canucks, eh?
From: richard@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.bsd
Subject: NMI crash - fixed(?)
Date: 9 Apr 92 12:58:08 GMT
Organization: AIAI, University of Edinburgh, Scotland

Last week I reported that I was gettting frequent crashes following
non-maskable interrupts.  Several people suggested that I was getting
parity errors because of faulty memory, but that seemed unlikely
since Minix runs very reliably.

I've now found what seems to be a workaround - remove the "halt"
instruction from the idle loop.  Since doing this the problem seems to
have vanished.  If anyone else is having similar problems, I suggest
trying it.

And if anyone could explain just why this works, I'd be interested.

-- Richard
-- 
Richard Tobin,
AI Applications Institute,                                R.Tobin@ed.ac.uk
Edinburgh University.
From: mm@mentor.cc.purdue.edu (Mike MacKenzie)
Newsgroups: comp.unix.bsd
Subject: Archive server nova.cc.purdue.edu
Keywords: 386bsd archive
Date: 10 Apr 92 17:03:34 GMT
Organization: Purdue University

We've set up a 386bsd archive server here at Purdue.  So far
the only thing of interest is a memory resident boot disk. It
reads the entire floppy into memory, then boots from a memory
device driver, freeing the floppy drive.  We plan to release
sources as soon as we've cleaned them up.

We've had luck booting memory resident on machines that previously
hung at the pc0<color> stage.

You can get boot.memory via anonymous ftp from nova.cc.purdue.edu
/pub/386bsd/submissions.  Soon we'll set it up so that you can get
submissions via email.


Michael MacKenzie	(Purdue University Unix Group)
mm@mentor.cc.purdue.edu
From: etnasse@skrue.etn.ericsson.se (Serussi Asher)
Newsgroups: comp.unix.bsd
Subject: Re: mounting fd0
Date: 14 Apr 92 12:59:38 GMT
Organization: Ericsson Telecom AS

In article <45250@mentor.cc.purdue.edu> mm@mentor.cc.purdue.edu (Mike MacKenzie) writes:

   Our 5 1/4 driver didn't seem to work at all, however if it was the
   boot device, I suspect it will work for you.

   Michael MacKenzie	(Purdue University Unix Group)
   mm@mentor.cc.purdue.edu


I had the same problem when I tryed to run from /dev/fd0a as root :
tar xvf /dev/fd1b 

all I got is : Stray int ST0 = 0xc0 PCN = 0 .

any idea what is wrong ?!

Thanks for any help !!!

Asher
--
----------------------------------------------------------------------

Asher Serussi				Tel : +47 41 19487
R&D Engineer
ETN/HU/C				E-mail : etnasse@etn.ericsson.se
Ericsson Telecom AS
Tangen Alle 39 P.O.Box 44		Memo : etn.etnasse
N-4817 His
Norway

------------------------------------------------------------------------
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: negative values from df
Date: 14 Apr 92 18:14:00 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

Following my query regarding negative blocks available from df I had a
number of replies by mail pointing out that the capacity goes up to 110%
for root. 

Even so, df should still not return negative values. At least with
SunOS4.1, the only one I have that's short of filespace, the available
blocks is listed as zero, when the 100% value is reached and stays at
zero for the last 10%. I propose thast the df in 386bsd should behave 
in the same way.

What are negative blocks? Is the disk claiming I'm indebted to it or
what :-)
-- 
  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: wswire3@rw9.urc.tue.nl (G. van Rooij)
Newsgroups: comp.unix.bsd
Subject: Some questions abt 386BSD
Date: 7 Apr 92 18:47:51 GMT
Reply-To: wswire3@urc.tue.nl
Organization: Eindhoven University of Technology, The Netherlands

Hi,

In the release notes coming with 386BSD something was said about the
serial port support being non-reliable. Did anyone actually use it e.g.
for an additional terminal? And..did it work? 
I'm not running 386BSD yet, but when i do it would be nice to have an
aditional terminal line....

-Guido
-- 
===============================================================================
WIRE, Wiskundig Ingenieurs Eindhoven  |  wire@win.tue.nl
PO Box 6421                           |   
5600 HK Eindhoven The Netherlands     |
Newsgroups: comp.unix.bsd
Subject: Re: mtools
From: rich@gal.utexas.edu (rich)
Date: 15 Apr 92 00:10:46
Reply-To: Rich@lamprey.Gal.UTexas.edu
Organization: Department of Electrical and Computer Engineering, RiceUniversity
In-reply-to: knie2586@csd4.csd.uwm.edu's message of Tue, 14 Apr 1992 20:40:54 GMTLines: 12

In article <1992Apr14.204054.19829@uwm.edu> knie2586@csd4.csd.uwm.edu (Robert Joseph Knier) writes:
      Anyone have any luck with the mtools?  I tried the mdir command
   and the system just gave me a couple of FD errors then stopped.

I've been using mdir for a week or more now.  You can try `dd
if=/dev/rfd0a of=/dev/null bs=9k count=1' to test reading from the
floppy.  If that doesn't work, then the problem isn't in mdir.  Rich
--
Rich Murphey				(409) 772-5487
Physiology & Biophysics Rt. F-41  	Fax: (409) 772-3381        
Univ. of Texas Medical Branch		InterNet: rich@rice.edu
Galveston, Texas 77555-0641             Uucp: rich@rice.UUCP
Newsgroups: comp.unix.bsd
From: vixie@pa.dec.com (Paul A Vixie)
Subject: Re: What happens if you have both BSD/386 and 386BSD?
Organization: DEC Network Software Lab
	<VIXIE.92Apr11201925@cognition.pa.dec.com>
	<1992Apr13.160409.21059@pegasus.com>
Date: 14 Apr 92 15:46:49

> It is obvious that BSDI follows and maintains a presence in comp.unix.bsd.
> Important fundamental questions about licensing have repeatedly been asked
> here, yet BSDI has chosen not to respond to them.  I would say that this
> is `reason to suspect'.

It could also be that they're too busy to bother with us riff-raff, as they've
got a product to ship and no time to engage in philosophical debates.  Or it
could be that they consider the question beneath contempt.  Or it could be that
their lawyers have told them to lay low and not make any declarations or prom-
ises except in response to full-blown accusations.  Or it may be that they just
don't know what their policy is going to be yet.

We can spend a lot of time here second-guessing them, or we can hope for the
best and get on with the non-commercial product.  If you have a large business
decision to make, I'm betting that the BSDi people would love to hear from you
and if you call them up and tell them you're thinking of buying N licenses,
they'll probably try hard to answer your questions about their plans WRT the
redistributable code base from CSRG.

> (Am I supposed to go kick the dog now Paul?)

Just don't kick mine, and we'll get along.
--
Paul Vixie, DEC Network Systems Lab	
Palo Alto, California, USA         	"Ready, Fire, Aim"
<vixie@pa.dec.com> decwrl!vixie
<paul@vix.com>     vixie!paul          alt.pink.bunny.boom.boom.boom moderator
Newsgroups: comp.unix.bsd
From: bambi@bu.oz.au (David J. Hughes)
Subject: Re: To make 386bsd coexist with DOS partitions??
Organization: ITS, Bond University
Date: Thu, 9 Apr 1992 01:26:00 GMT

keithe@sail.LABS.TEK.COM (Keith Ericson) writes:

>Look on the SIMTEL20 archive machine (or a mirror) in the sysutl directory
>for a file called bootany.zip.  It contains a complete system to re-groove
>the boot record as you describe (hit a Function key to select the partition
>you want to boot from), and source is included...

I beat up the sources of bootany a whle back to handle a public access
lab management problem we had and it works well.  You still have
problems of the restricted size ( and bootany's habit of wanting to fire
up ROM basic :-) but it'll do the job well with a bit of work.

As for the selection of a particular kernel from which to boot, how
about a 2 level boot strap to cover this.  Bootany (or whatever) allows
you to select the partition from which to boot.  It then loads what it
thinks is the loader and executes it.  That loader could be made aware
of multiple kernels with a lot less problems than adding that function
to bootany.

I admit that I haven't checked out the source to the BSD boot code but I
can't see it as being a problem.


bambi
   ___                                 David J. Hughes     bambi@bu.oz.au
  /   \                /  /    /        
 /  __/ __   __   ____/  /    / __          Senior Network Programmer
/    \ /  \ /  \ /   /  /    / /  \  /    Comms Development & Operation
\____/ \__//   / \__/   \___/ /   / /       AUSTRALIA  (+61 75 951450)
Xref: sparky comp.unix.bsd:726 comp.unix.internals:1090 comp.unix.questions:6034 comp.lang.c:7412
From: etxaax@falcon2.ericsson.se (Anders Axelsson)
Newsgroups: comp.unix.bsd,comp.unix.internals,comp.unix.questions,comp.lang.c
Subject: errno questions
Date: 9 Apr 92 14:25:19 GMT
Article-I.D.: falcon2.etxaax.702829519
Organization: Ericsson

Does anyone know if errno can be 0 after a Unix error? sys_errlist[0] does
have a value, a cryptic message "Error 0". In our version of errno.h (from
SunOS 4.1), there is no #define for the value 0.

Thanks

  /Anders

-- 
==========================================================================
Anders Axelsson                           Phone : +46 8 719 6616
Dep. VB/ETX/TM/FG, Ericsson Telecom AB    E-mail: etxaax@beppe.ericsson.se
S - 126 25 Stockholm, SWEDEN              MEMO  : ETX.ETXAAX 
--
==========================================================================
Anders Axelsson                           Phone : +46 8 719 6616
Dep. VB/ETX/TM/FG, Ericsson Telecom AB    E-mail: etxaax@beppe.ericsson.se
S - 126 25 Stockholm, SWEDEN              MEMO  : ETX.ETXAAX
From: tinguely@plains.NoDak.edu (Mark Tinguely)
Newsgroups: comp.unix.bsd
Subject: kern_execve.c
Date: 6 Apr 92 19:23:18 GMT
Article-I.D.: plains.16489
Organization: North Dakota State University, Fargo


 It is good to see so many fixes for 386 BSD, but I think 
 the kern_execve.c fixes (and soon some other files) are getting
 too inter-related. I think we need standardize on a copy (some of
 the fixes are now conflicting).

 Jo Torsmyr has a point, we are going in different directions on
 patches and people working on problems are duplicating services.


Mark Tinguely  North Dakota State University  Fargo, ND  58105. (701) 237-7786
 tinguely@plains.NoDak.edu || uunet!plains!tinguely || tinguely@plains.bitnet
From: mm@mentor.cc.purdue.edu (Mike MacKenzie)
Newsgroups: comp.unix.bsd
Subject: timeout() bug
Keywords: timeout callout
Date: 13 Apr 92 15:04:35 GMT
Article-I.D.: mentor.45105
Organization: Purdue University


We were trying to get the apdatec SCSI driver working on machine with
an IDE drive as the boot disk and an hp97548s 648 meg SCSI drive
as the second drive.

The machine would crash mysterious in different places.  Marc Mengel
traced it down to a problem with the timeout buffer list not being NULL
terminated.  This is the fix for that problem.

In i386/i386/machdep.c:
***************
*** 223,228 ****
--- 223,229 ----
        callfree = callout;
        for (i = 1; i < ncallout; i++)
                callout[i-1].c_next = &callout[i];
+       callout[i-1].c_next = (struct callout *)0;      /* null terminate list -- mwm */
  
        /*printf("avail mem = %d\n", ptoa(vm_page_free_count));*/
  

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

This made the machine panic consistently.  Then we increased the number
of timeout buffers by increasing MAXUSERS from 2 to 40.  We're
working on a better fix.  Idealy when the machine is out of timeout
buffers, it should wait for a few timeouts, rather than panic.


Michael MacKenzie	(Purdue University Unix Group)
mm@mentor.cc.purdue.edu
From: u8acb@ohm.york.ac.uk (Alex Barclay)
Newsgroups: comp.unix.bsd
Subject: Recompiling the bootcode. Fix for my PC
Date: 11 Apr 92 21:02:39 GMT
Organization: Electronics Department, University of York, UK

Could anyone out there in net land help me with a cure that I'm trying to
make BSD 386 boot on my PC (386SX AMI Bios, IDE H/D Seagate).

I can get the thing to boot off the floppy by... Wait for it...

1) Telling the BIOS that the HD isn't present so it doesn't try to boot from it

2) Waiting after switch on till the machine realises that there isn't a
   bootable device and aska for a boot disk.

3) Inserting the dist.fs disk and pressing the key as instructed. The OS
   now boot perfectly. And I can play with it, including the tty hangup
   demonstrated by the more command.

4) I can access the hard disk, label it, make a file system but the machine
   displays the same problem trying to boot off that as off the floppy. The
   strange bit is that the floppy drive light comes on when the HD boot fails.

This is definately strange and I'm am looking for a cure, involving going
through the chip datasheets that I have and checking what the code is doing.

The problem is that I have no way of testing my theories. Is there anyone
who could compile/assemble up some boot code that I send them on a working
386BSD system, then send the resulting binaries back so I can glue
them onto the front of a boot disk???

		Any help appreciated...

				Alex.
From: knie2586@csd4.csd.uwm.edu (Robert Joseph Knier)
Newsgroups: comp.unix.bsd
Subject: mounting fd0
Date: 13 Apr 92 21:09:01 GMT
Article-I.D.: uwm.1992Apr13.210901.2384
Organization: Computing Services Division, University of Wisconsin - Milwaukee


    Just a dumb question:

	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!


					Can't wait to get a tape drive,

					Bob Knier
					(knie2586@csd4.csd.uwm.edu)
From: ptuomola@clinet.fi (Petri Tuomola)
Newsgroups: comp.unix.bsd
Subject: 386BSD says "ISA strayintr 0" but works..
Keywords: 386bsd
Date: 14 Apr 92 16:33:24 GMT
Organization: Clinet, Helsinki, Finland

My machine is 386/33MHz w/ 64Kb cache, 8MB memory, 150MB hard disk (ATID),
*NO* co-processor, SVGA and 4 serial ports, 2 printer ports and SoundBlastee Pro

Just for fun, I tried yesterday to boot 386bsd on this machine. First it didn't
work, just displayed message "Operator abort - didn't load 386bsd, will try ..."
but when I disabled all shadow rams and cache memory, it booted fine and got up.

BUT! It displays all the time messages saying "ISA strayintr 0", written black
on blue background. It it impossible to even try to do something when the screen
fills in few seconds. Between those messages I could see that it worked fine.

So, I ask you, wizards, what does cause this message? Is there anything that
I should look for? Any cards to remove? Any settings to change? When I get
math co-processor I will try to install 386bsd on my machine, and it would
be nice to get rid of those messages before that.

Thanks in advance.

Petri

-- 
-------------------------------------------------------------------------------
Petri Tuomola  OH2LJY | InterNet: ptuomola@clinet.fi or ptuomola@unidex.pp.fi
Ylipalontie 10AC      | FidoNet : Petri Tuomola@2:220/63
00670 Helsinki 	      | UUCP    : ...!mcsun!fuug!clinet!ptuomola
Voice +358 0 7542881  | Data	: +358 0 749094 V22bis, V21 24H
-- 
-------------------------------------------------------------------------------
Petri Tuomola  OH2LJY | InterNet: ptuomola@clinet.fi or ptuomola@unidex.pp.fi
Ylipalontie 10AC      | FidoNet : Petri Tuomola@2:220/63
00670 Helsinki 	      | UUCP    : ...!mcsun!fuug!clinet!ptuomola
Newsgroups: comp.unix.bsd
From: cchase@theory.TC.Cornell.EDU (Craig Chase)
Subject: Ditto: Status of next release??
Organization: Electrical Engineering, Cornell University, Ithaca NY
Date: Wed, 15 Apr 1992 20:56:50 GMT

It would be nice to know what the plans (if any) are for a new release
in the near future.  I'd particularly like to know what the status is
of the bad sector maps for the wd driver.  This driver appears to be
different between the /386bsd binary and wd.c source in the 3/17/92
release.  

Anyway, has anyone had experience with the GNU CVS revision control
system?  It is a front end to RCS and, based on the descriptions I've
read, would seem ideal for supporting the 386BSD development effort.
It supports heirarchical source distributions (i.e. sub directories)
and I think gnu diff/patch can supply patches for binary files.  This
functionality should allow someone to define the CVS-modules in such a
way that complete binary and/or source diffs for the entire 386BSD
distribution could be generated with a single command.  There may also
be a little bit of support for concurrent editing of the source files
by different people.

We've had a few people offering their (and their computer's) services
as archives.  Would someone be willing to set up a CVS repository for
386BSD?  It might help to get the current patch confusion under control.

Craig


-- 
    "... [putting out an oil-well fire] that's the easy part.  Once you've
    gotten the debris cleared away from the well head, a brownie troop  
    can put out the fire"                                ^^^^^^^^^^^^^
            paraphrased from one of the fire fighters seen in the Nova
From: gt0178a@prism.gatech.EDU (Jim Burns)
Newsgroups: comp.unix.bsd
Subject: Re: boot code binary to make 386BSD coexist with DOS
Date: 11 Apr 92 02:13:58 GMT
Organization: Georgia Institute of Technology

in article <dirkst.702913970@rama>, dirkst@rama.informatik.rwth-aachen.de (Dirk Steinberg) says:

> You need to install a regular DOS master boot block in sector 0 of your
> harddisk. The BSD disklabel goes into sector 1. Sectors 2-15 contain

> You can put it there with 'dd if=bootwd of=/dev/wd0c seek=2'. Note that
> the disklabel program writes to sector 0 of your disk, destroying your
> DOS master boot. You can *first* grab your DOS master boot with
> 'dd if=/dev/wd0c of=wdboot count=1', then move wdboot and bootwd to
> /etc/mdec, and then run disklabel. That should do the work.

Why are you saving the Dos boot? Are you using it for something, or only if
you want to go back to the old way? Or are those filenames special to
disklabel?

> /dev/wd0c with dd; anyway the first 8K of a partition are reserved in BSD,
> so you can still start your first partition on sector 0).

> Create a DOS partition that starts on sector 2 (or sector 3 in Norton).
> The Length does not matter, but you may want it to include all of BSD.
> Mark the partition as active. Reboot...

Only a Dos partition? Nothing reserved for 386bsd? And is it sector 0 or 2?
You said both.

> Now you can enter hex numbers. The contents of that address will be
> displayed. At address 0 should be something like 0x1234....
> Type a capital 'C' at the start of a line to kick of BSD.

What is this? Some kind of debugger/memory dumper? What is the definition
of the 'C' command?

Is this 386 code, or can I use it on a 286 as well? Thanx.
-- 
BURNS,JIM (returned student)
Georgia Institute of Technology, 30178 Georgia Tech Station,
Atlanta Georgia, 30332            | Internet: gt0178a@prism.gatech.edu
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt0178a
Newsgroups: comp.unix.bsd
From: sean@u36.uucp (Sean Goggin)
Subject: List of known partition IDs
Organization: U36 Research
Date: Sun, 5 Apr 1992 00:08:00 GMT

Xenix and ISC allocate there partitions inside a regular PC partition.
This permits accessing partitions of other operating systems as well.

>The boot strap starts with the usual master boot program in the master
>boot sector which looks for the active id in the partition
>table get the location of the first partition sector and try
>to execute it as the second stage boot code of the respective OS.

Linux and Minix often use the public domain bootstrap loader 
called a shoelace which sounld be convert for use with 386BSD.

We must find a free Partition id for 386BSD

Know partition ids are

Partition Type 		Number 	
no partition 		0x00
Dos 12			0x01
Xenix			0x02
Old Xenix		0x03
Dos 16			0x04
Dos Extended		0x05
Dos huge type		0x06
AIX			0x08
Opus			0x0A
Novell ?		0x51
CPM ?			0x52
386/IX			0x63
Novell			0x64
PCIX			0x75
Minix 			0x81
Minix Old		0x80
CPM			0xDB
Bad Blocks		0xFF

please mail me if you can add to this partition list

sean@u36.kwnet.on.ca
sean@u36.uucp

unknown

Xinu
OS/2 HPFS	
Mt Xinu MACH
GNU Hurd
Coherent
Windows NT
Solaris Fast
Solaris Sys 5
BSDI Fast
Linux VF
Linux Regular
-- 
Sean.Goggin....sean@u36.uucp.....................................U36.Research...
From: chris@alderan.sdata.de (Christoph Splittgerber)
Newsgroups: comp.unix.bsd
Subject: Re: Bug fix coordination
Date: 10 Apr 92 00:20:36 GMT
Organization: C. Splittgerber Datentechnik, Denkendorf, Germany

In article <1992Apr3.141000.8354@ugle.unit.no> jot@zevs.ifi.unit.no (Jo Torsmyr) writes:

>I would appreciate any suggestions for organizing patchleves!

Maybe we should send our patches to somebody by email who is collecting
them. Then this somebody passes the patches to a few other people to
validate them and then put them together to an "official" patch assigning
a official patch-number and post it to this group.

IMHO it is a very important thing to get organized as fast as possible.

                  Chris
-- 
******************** It's not a bug, it's a feature !!! ********************
Replies-To:  chris@alderan.sdata.de    UUCP: uunet!mcsun!unido!alderan!chris 
Phone:       +49 711 344375            Fax:  +49 711 3460684
Newsgroups: comp.unix.bsd