HDTenEightyP/NetNews huggingface dataset:
From: hlu@poly2.eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.unix.bsd
Subject: Re: Fixed: Runs at 8MHz, Crashes at 33MHz, 386bsd
Keywords: bug
Date: 12 Sep 92 21:53:25 GMT
Article-I.D.: serval.1992Sep12.215325.2451
Organization: Washington State University

In article <1992Sep12.134712.17755@news.cs.indiana.edu>, "Michael Squires" <mikes@moose.cs.indiana.edu> writes:
|> When running SCO XENIX 386 and UNIX 386 on various clones it became clear that
|> all brands of clone were not alike and all brands of memory were not alike.
|> In some cases I know that there were problems with the memory bus caused by
|> poor design or unreliable DRAM.  I personally would not try to run 386 UNIX
|> on a really cheap motherboard, unless I'd already tested in some other way
|> (and the Checkit/AMIDIAG type of tester doesn't stress the hardware enough
|> to find the problems).  
|> 
|> I wonder if there is a program that is small enough to fit on the boot disk
|> which would really stress memory which could be used to test prospective
|> clones in the store or at the hamfest/computerfest/Trenton/Dayton Hamvention?
|> 
|> -- 
|> 
|> Mike Squires (mikes@iuvax.cs.indiana.edu)     812 855 3974 (w) 812 333 6564 (h)
|> mikes@iuvax.cs.indiana.edu          546 N Park Ridge Rd., Bloomington, IN 47408

Get the lastest bootimage and rootimage for Linux. I was told it was a very
good testing program. It just takes two disks. In the rootimage, there are
quite a few Unix stuffs. It has almost every basic stuff, except for gcc
2.2.2.

H.J.
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: SLIP set up, but how to connect?
Date: Wed, 09 Sep 92 02:10:25 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

I am using "Unix System Administration" by Nemeth, Synder, Seebass as a
reference, which is very helpful, but it doesn't seem  to cover SLIP...

On one system SLIP autologin is set up as per the sliplogin man page
(sliplogin linked to /etc/, passwd entry added with vipw, etc).  On the
second system, only the 386bsd distribution installation disk is
installed (and a patched kernel from the first system).   I can use
the second  system as a serial terminal (connecting  with tip) on the
first.  But how to I get a SLIP connection?

Following the 386bsd installation instructions for loading 386bsd via
SLIP, I do:

# slattach /dev/com2 9600
# ifconfig sl0 192.100.92.2 192.100.92.1

(192.100.92.1 and .2 are the arbitrary IP addresses that I have
assigned to the first and second system, respectively.  They appear
in the first system's /etc/hosts file).

Is the route command necessary now?  If so, do I use the first system's
IP address as the <local gate number>?

In the mean time, I try:
# ftp 192.100.92.1

No complaint, but no connection either.  So I try:
# route add default 192.100.92.1

adds default OK.  Again:
# ftp 192.100.92.1

nothing.  So then I try tip, but that doesn't work now.

Other variations I have tried:

login via tip before slattach to the first system using SLIP login
name (Sworm).  autolgoin fails in slip.login.

connect via tip and at the "login: " prompt ^Z back to local system.
Do slattach, fg back to tip - the diagnostic appears: "write not
support by device" 

etc.  What am I doing wrong?
-Andrew Moore <alm@netcom.com>
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: Mon, 7 Sep 1992 06:49:22 GMT

In article <1992Sep06.065525.8475@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>In article <QG0JYC1@taronga.com> peter@taronga.com (Peter da Silva) writes:
>>You're assuming that "posix compliant" means anything actually useful.
>>From what I've seen it's seriously incomplete for any real applications,
>>and so amounts to no more than a checkmark on a requirements sheet.

>I don't know about that.  gcc, gas, GNU make, the GNU binutils (and,
>perforce, the GNU BFD library) can all be built in a POSIX-only environment.

That makes perfect sense, since they're hackerware. All they do is file
translation, and the only OS services they need are reading and writing
files. Of course the code generator for GCC is system specific, and gas
needs to know the instruction set and details of the executable format.

>Those are real applications, after all.

They're tools, not applications. Applications are the things people buy
the computers for. Apart from developers, people rarely buy computers
for compilers. And developers need support for the code they're developing.
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: Re: Xfree386 1.0.2
Date: 10 Sep 1992 16:59:47 -0500
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu
In-reply-to: wigodsky@cwis.unomaha.edu's message of Thu, 10 Sep 1992 20:14:34 GMT

In article <wigodsky.716156074@cwis> wigodsky@cwis.unomaha.edu (Andrew Wigodsky) writes:

>Would someone mind telling me why X386 is _so_ disk intensive. 
>Whenever I scroll from one Xterm to another, it seems to take 
>_forever_ because of all the disk access that is going on.
>
>I am running on a  386-40 (AMD. of course)  and my unix partition
>is on an 80MB maxtor IDE..  any clues as to why X386 is so slow?

How much RAM do you have?  If you are running with less than 8M you
have too little and are paging everything but X and the current xterm
to disk.

++Brett;
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: Re: ps -aux yields Floating exception
Keywords: ps FP exception Floating
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Tue, 15 Sep 92 09:55:55 GMT



In article <19228rINNorq@corax.udac.uu.se>, goran@astro.uu.se (Goran Hammarback) writes:
>In article <1992Sep13.171803.3954@Urmel.Informatik.RWTH-Aachen.DE>, kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:
>|> 
>|> I recently installed a kvm.c patch (though I'm not sure if I installed
>|> it completely and c orrect) - anyway, when I do a ps -aux I get
>|> the header line of ps (CPU % etc..) and then in the next line a 
>|> Floating exception.
>|> 
>|> Is this a known and already mentioned problem or do I have to 'patch harder'
>|> :-)? 
>
>
>Did you forget to patch ps itself?
>
>From: davidg@agora.rain.com (David Greenman):
>
>*** /usr/src/bin/ps/ps.c.01orig	Mon Jul  1 17:54:45 1991
>--- /usr/src/bin/ps/ps.c	Sun Aug  9 05:35:26 1992
>***************
>*** 78,83 ****
>--- 78,84 ----
>  
>  uid_t	getuid();
>  char	*ttyname();
>+ double	getpcpu();
>  
>  char dfmt[] = "pid tt state time command";
>  char jfmt[] = "user pid ppid pgid sess jobc state tt time command";
>
>
>-- 

Yes, I forgot to apply this tiny but essential patch to ps itself. 
--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
From: adrian@ibmpcug.co.uk (Adrian Hall)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Install Query
Summary: What Swap Space is configured into the install kernel?
Date: 4 Sep 92 10:22:42 GMT
Organization: The IBM PC User Group, UK.

What amount of swap space is configured into the kernel/disk by
the install script?

Adrian

-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
From: jim@blade (Jim Rump)
Newsgroups: comp.unix.bsd
Subject: Microfield T8C questions ???
Summary: X
Keywords: X
Date: 13 Sep 92 20:59:53 GMT
Organization: MCGV Stack, Eindhoven University of Technology, the Netherlands.
X-Newsreader: Tin 1.1 PL4

Hi all,

I'm a student who has a 19" monitor (Unisys)  with a Microfield T8C video-card.
With this card a MS-windows driver was supplied. 
Since I'm running X386 on a BSD based system I really would like to
use the T8C to operate with X386. The following questions also applies to 
X386 on a Linux based system.
The questions I have are:

* Are there drivers for the Microfield T8C-card for X-windows. If this is
  the case, where can I obtain this and at what price? 

* I know there is a manual for programming the T8C-card. The name is:
  `Microprogrammer's reference manual for the T8C Color Graphics Controller`.
  Where can I get this manual?

* Does anyone know the adress of Microfield or perhaps an e-mail adress?

An other question I have is if someone has allready succesfully used a
19" monitor connected to a 1MB vga-card e.g. a et4000 based one.

Thanks,

Jim (jim@stack.urc.tue.nl)



--
   \_  \_  \_\_  \_ \_   Jim@stack.urc.tue.nl
    \_  \_  \_  \_   \_ 
     \_  \_  \_       \_     
  \_\_    \_  \_       \_    I,m always seeing an opinion.
From: goran@astro.uu.se (Goran Hammarback)
Newsgroups: comp.unix.bsd
Subject: [386BSD] (IDE & AT bus expert help needed) Thanks
Date: 14 Sep 1992 12:25:58 GMT
Organization: Uppsala University
Distribution: world
NNTP-Posting-Host: solaris.astro.uu.se

I posted a mail here last week for help on getting two IDE HD's
working on my machine.  I got may replies (Thank you!) and the
solution I used was to jumper my Conner disk correctly to work
as master (Sorry, but I had no info on the drive).
Here is a table on how to jumper Conner disks that worked for my
CP30104:

From torsten@techfac.uni-bielefeld.de:
> The jumper settings for one and two Conner drives (CP3504, 500MB
> and CP3104, 100MB). If the jumpers on your drive are labelled as
> below, you might try this one (no guarantee):
>
>  CONFIGURATION         HSP     C/D     DSP     ACT
>  -------------         ---     ---     ---     ---
>  One drive             Off     On      Off     On
>  Two drives
>  Master                Off     On      On      On
>  Slave                 Off     Off     Off     On
>
> where "on" means to place the jumper and "off" to remove it.



I didn't try to use two controllers, since the easy solution worked,
but if someone else needs to do this, you need a controller where you
can change the address space for the registers from 1F0 to 170, and you
need to change the interrupt from the controller from IRQ 14 to for
example IRQ 15, either by moving a jumper, if that is supported, or by
soldering.  Here is the layout of that part of the bus:

From rcd@eklektix.com Thu Sep 10 04:25:49 1992:
> First, orientation:  Looking down on the motherboard, with the rear panel
> away from you - component sides of boards are to the right - the high-
> numbered interrupts are on the secondary connectors (exist only on 16-bit
> slots) which are nearer to you.  The positions are numbered D1-D18 on the
> left from top to bottom and C1-C18 on the right from top to bottom.  The
> interrupt lines are:
>	D3	IRQ10
>	D4	IRQ11
>	D5	IRQ12
>	D6	IRQ15
>	D7	IRQ14
> (Of course, you should be able to verify that you're in the right place by
> checking that your current card has a connection at D7 (IRQ 14) - 7th
> position down on secondary connector, foil side of the card.)
>
> >Which interrupt should I use (IRQ 15 as tih?)??
>
> 15 is OK.  The unassigned IRQ's in the second group are 10, 11, 12, and 15.





Thank you everybody that helped me with this!

Goran

------------------------------+---------------------------------
Goran Hammarback              |     goran@astro.uu.se
Astronomiska Observatoriet    |
Uppsala Universitet           |
S-751 20 SWEDEN               |
------------------------------+---------------------------------
Newsgroups: comp.unix.bsd
From: cproto@marsh.cs.curtin.edu.au (Computer Protocol)
Subject: Re: 386bsd -- The New Newsgroup
Keywords: newsgroup 386bsd news group
Organization: Curtin University of Technology
Date: Wed, 9 Sep 1992 12:44:38 GMT

veit@du9ds3.uni-duisburg.de (Holger Veit) writes:

>In <1992Sep8.200625.2894@socrates.umd.edu> john@socrates.umd.edu (John VanAntwerp) writes:

>>In article <18iprpINNg6e@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
>>>
>>>As per Bill's suggestion, here's a breakdown of some of the suggested 
>>>topics and groups:
>>>
>>>	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)

>>I think that this is a fine set of newsgroups...

>>						John

>You should not multiply entities unless it is absolutely necessary
>(free translation of William of Occam's well-known statement). 

>We have considerably high traffic on 'I cannot boot with my configuration', say
>'newbie' stuff. Since I follow this group quite long, I would have an idea
>where to post such a question, but if I were a beginner and desperate 
>because of 386bsd had just cleaned my whole disk, I would perhaps ignore 
>the different groups and send my mail to all of them, perhaps to find 
>one who can answer.

>I haven't seen much on shared libraries yet in this group, so why sharedlib.
>Or did I misunderstand this, because you mean a common library (archive) for
>all who want to share software? This might be called 'comp.os.386bsd.contrib'.

>I if found just a bug in /sys/kern/kern_execve.c, should I post to
>comp.os.386bsd.bugs or c.o.3.kernel, just because my detected effects could be
>for interest for the latter group as well? And if I fixed the bug on the fly,
>should I also send it to c.o.3.ann? Similiar things might happen with
>network related things.

>BTW, when the AT&T/USL or similiar junk should come up again, where will it
>go? I assume from the previous stories (before alt.suit-bsdi ?) was created,
>the articles were scattered around everything that had *.unix.* in its name.

>*** I am not against a new group comp.os.386bsd, but why should it be a whole
>*** tree directly? Confusion will be built-in.

I couldn't agree more. I don't even see the need to change the current
status quo. All traffic in this newsgroup is related to 386bsd (forget
the 0.001% exceptions). Its seems completely crazy to disturb something
which works well (don't fix something which ain't broken). So please
leave things as they are - but at least please please please don't
create 20 different newsgroups all with duplicate messages (people will
crosspost). There are plenty of us who dial in from home with 1200 or
2400 b/s and read mail and news. So it's a real pain having to sift
through the some message several times.

Regards - Tibor Sashegyi (cproto@abel.cs.curtin.edu.au)

Newsgroups: comp.unix.bsd
From: pk@cs.few.eur.nl (Paul Kranenburg)
Subject: Re: Program dies with FP Exception
Reply-To: pk@cs.eur.nl
Organization: Erasmus University Rotterdam
Date: Mon, 14 Sep 1992 15:15:55 GMT

In <1992Sep13.083846.6134@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:

>In article <STARK.92Sep13002650@sbstark.cs.sunysb.edu> stark@cs.sunysb.edu (Gene Stark) writes:
>>Here's a tough one I've been trying to track down -- maybe somebody out there
>>who knows more can guess what is going on.
>>
[...]
>First of all, like all other signals, the SIGFPE gets delivered to a process
>as a result of the sigtrampoline code.  The *only* way you get a signal is
>on return from a system call.  The problem is that there appears to be no

.. or you get your signal immediately, provided you have a handler set, or
you get it on return from the interrupt (trap), provided the AST (Async.
System Trap) stuff is implemented which is then invoked from `signotify()'.

-pk
Newsgroups: comp.unix.bsd
From: rcd@raven.eklektix.com (Dick Dunn)
Subject: Re: Controller manufacturers (was Re: Colorado Memory Systems)
Summary: not all manufacturers are so tight with info
Organization: eklektix - Boulder, Colorado
Date: Sat, 5 Sep 1992 19:39:29 GMT

staylor@snidely.UUCP (Scott G. Taylor) writes:
><h!mn#wj.hasty@netcom.com>, Amancio Hasty Jr wrote:
>>...Also, you may add that [Colorado Memory Systems] will not release any
>> technical information on their interface!
>
>Colorado Memory Systems people are not special in this respect.  I have yet
>to find a tape drive controller manufacturer who will even discuss the
>programming of their tape drive controllers...

I suspect this applies more (or only?) to the manufacturers of the little
cassette drives.  They're in a very price-competitive market; they need all
the help they can get for "product differentiation".  This tends to lead to
uncooperative behavior.

But as far as I know, the manufacturers of the larger (cartridge) drives
are much better.  I recall that Wangtek was not just cooperative, but help-
ful, when ISC was creating a driver for the Wangtek cartridge drives.  I
seem to recall that there was some hassle even back then, even with ISC,
getting info on one of the cassette drives.

>...Do these people believe
>they have God's Gift to tape drives, and to release *ANY* information 
>would jeopardize their niche?  

Incorrectly, yes, but that's what they believe.  It's a pretty incredible
situation with some of them...sort of like having to sign a nondisclosure
agreement to get a shop manual for your car.

>These companies are not in the software business...

Most of them are also not in the business of dealing with end-users, and
this makes your problem of getting info harder still.  In fact, the way
they're set up, they just don't have provisions for dealing with more than
a few privileged software writers for their products.
-- 
Dick Dunn    rcd@raven.eklektix.com   -or-   raven!rcd    Boulder, Colorado
				Cats!
Newsgroups: comp.unix.bsd
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: 386BSD #!/bin/csh
Organization: Kithrup Enterprises, Ltd.
Date: Thu, 10 Sep 1992 04:50:48 GMT

(`comp' is not a valid Distribution.  By putting 'Distribution: comp' in the
header, you have caused a growing number of sites around the world to just
drop your article on the floor.  Is that what you wanted?)

In article <1992Sep9.171327.20998@gateway.novell.com> terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert) writes:
>Instead of:
>	#!/bin/sh
>use:
>	:
>	#

Alternatively, and I personally think this is "better," modify the exec*
source code to, if the system call fails, open up the file in question and
to the processing itself, instead of relying on the kernel.

Just a thought...

-- 
Sean Eric Fagan  | "You can't get lost in one room, no matter how
sef@kithrup.COM  |  little effort you make to learn your way around."
-----------------+    -- William E Davidsen (william@crd.GE.COM)
Any opinions expressed are my own, and generally unpopular with others.
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Shared Libraries and BSD 
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Sun, 6 Sep 1992 19:40:53 GMT

I remember some discussion about shared libraries but I can't find
any referrences.  Can someone comment on the state of the art of
shared libraries WRT BSD 4.3, 4.4, and 386BSD?  Pointers to references
would be appreciated...

-- 
 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
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: DAT tape (SCSI) supported? 
Keywords: SCSI DAT driver
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sun, 13 Sep 92 17:21:26 GMT


Recently I saved all my user data etc. from a SCO system to a DAT tape (TLZ04,
DEC attached to a 1542), scratched the disk (intentionally) and now I'm
starting to build up a 386bsd on it. 

My question: will there be a chance in the near future to get that data read back into the 'new born' 386BSD system by means of a 386BSD DAT SCSI driver?

 

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

Organization: Doctoral student, Statistics, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.unix.bsd
Date: Tue, 15 Sep 1992 21:06:31 -0400 
From: Tao Jiang <tj2n+@andrew.cmu.edu>
Subject: [386bsd]ppp

Hi,

Does anyone know whether  PPP has been ported to 386bsd or
not ?  If so, where I can find the source or binary?  What's the
difference between ppp and slip?

Thanks!

TJ
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: 386bsd Xfree
Date: 15 Sep 1992 09:20:02 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

Folks,
I suspect there's folks out there with a '387 and folks without.
I suspect further that the X11 server and basic stuff is linked with -lm.
Well, the standard libm.a is really *slow* and since there will be quite
a few of us who have a co-processor, may I suggest/request that someone
in the know (and with enough disk space) re-compile X and put the object
files in a sensible place ?

BTW drop me a note if this has been done already.

Thanks,
	Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
From: lmjm@doc.ic.ac.uk (Lee M J McLoughlin)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] Real partitioning on SCSI system?
Date: 7 Sep 92 17:46:18 GMT
Distribution: comp
Organization: Dept. of Computing, Imperial College, London. U.K.
NNTP-Posting-Host: swan.doc.ic.ac.uk
In-reply-to: fridlund@mermaid.micro.umn.edu's message of 6 Sep 92 00:53:41 GMT


In article <FRIDLUND.92Sep5185341@stingray.micro.umn.edu> fridlund@mermaid.micro.umn.edu (Jim Fridlund) writes:
Jim> # mount /dev/as0a /mnt
Jim> mount: /dev/as0a: Invalid argument.

This usually means either no /dev/as0a or no /mnt - mount was never
very good at error reporting.
	Lee
--
--
Lee McLoughlin.                          Phone: +44 71 589 5111 X 5085
Dept of Computing, Imperial College,     Fax: +44 71 581 8024
180 Queens Gate, London, SW7 2BZ, UK.    Email: L.McLoughlin@doc.ic.ac.uk