HDTenEightyP/NetNews huggingface dataset:
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: Re: 3 button mouse for X386
Date: 9 Sep 92 00:18:50
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu
In-reply-to: rjw9917@bcstec.ca.boeing.com's message of 8 Sep 92 23:22:41 GMT

In article <3577@bcstec.ca.boeing.com> rjw9917@bcstec.ca.boeing.com (Robert J. Willard) writes:

>I've got 386bsd and X386 running smoothly, using
>a microsoft serial mouse.  However, I'm accustomed
>to using a 3 button mouse with X and am wondering
>which mouse (preferably a CHEAP one) would be good.
>Any ideas?

I've got a mouse called "Aero Mouse" which was dirt cheap.  It works
fine for me and emulates either Microsoft or Mouse Systems mice.  It
is three button, 300 dpi resolution.  It works fine with the mouse
systems driver under X386 and you get 3 buttons that way.  It also
works fine under the microsoft driver, but you only get 2 buttons
that way.

I've also heard that Dexa mice are okay cheap mice.  You can probably
get one at your local HyperMart (that's where I've seen them around
here).

++Brett;
Newsgroups: comp.unix.bsd
Subject: Help: 386bsd NFS Filename Truncation
From: <AI4CPHYW@MIAMIU.BITNET>
Date: Tuesday, 8 Sep 1992 10:36:21 EDT
Organization: Miami University - Academic Computer Service

I installed the binary release of 386bsd on my machine and it works
fine.  So I tried to install the source distribution and ran out of
disk space (80MB drive in the machine).  After some thought I realized
that I could do an NFS mount of another Unix machine (an Intergraph
CAD server running Clix, I-graph's flavor of Unix) and use that disk
space to hold the source distribution.
 
So after successfully NFS mounting more disk space to the /usr/src
directory (using the -o wsize=4096,rsize=4096 option) I tried a
"manual" unpack of the src01.* files, to the NFS mounted disk, with
the cat /tmp/src* | uncompress | cpio -idalmu.  I got a bunch of
errors about how cpio couldn't modify permissions in the /usr/src
directory and couldn't write to directories sub to /usr/src.
 
I halted the uncompress and decided to work the other way.  I NFS
mounted more disk space to the /tmp directory, dumped the src01.*
files there and ran the manual unpack to dump the source distribution
on the local disk.  No problem, other than a 97% full local drive.
Then I tried to copy the entire /usr/src tree to the NFS mounted disk
to clear space on the local drive.  The cp -R   command seemed to work
fine, except when I went to compare the directory trees to each other,
I found differences.  First, the ownership was different (the files on
the local disk were owned by root and the copies were owned by 32767
(not a problem for chown, but still :)  Second, and more important,
the long filenames were truncated.  (i.e. Makefile.symlinks on the
local drive appeared as Makefile.symli on the remote disk
elvispreserve.8 appeared as elvispreserve. and so on.)  Renaming the
files to their correct names failed (i.e. mv elvispreserve.
elvispreserve.8 seems to come back successfully, but an ls elvis*
shows the filename is still elvispreserve.)
 
Frankly, I'm at a loss.  I don't know if this a problem with the
implementation of NFS, or if I'm doing something wrong, or if the
machine I'm borrowing disk space from needs to have something done to
it.  If anyone can provide some insight, I would appreciate it.
 
 
 
                      -Alec D. Isaacson
                       AI4CPHYW @ miamiu.acs.muohio.edu
                       isaacson @ rogue.acs.muohio.edu (NeXt Mail)
                       Miami University, Oxford, OH
-------------------------------------------------------------------------
Only a barbarian would eat chive cream cheese and blackberry jam on the
same bagel.                          -Spenser
From: root@ibmpcug.co.uk (The root of all evil)
Newsgroups: comp.unix.bsd
Subject: Re: kvm.c patch wanted
Date: 8 Sep 92 09:46:32 GMT
Organization: The IBM PC User Group, UK.

In article <1992Sep7.190727.9631@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de writes:
>
>Has anyone gotten ps to output the user command line?
>
>There were two posts on that issue in July, I believe. These two patches
>for kvm.c at al.gave this  "hunk 2 failed" - oh I love these kind of
>messages. Should add it to my .signature file :-)

Thats because whoever did the patch missed off semi-colons in the
most awkward of places... The best plan is to look at the original
and the patch and decide which semicolons to delete from the patch :)

If you e-mail me, I will send you a patched copy of kvm.c.

-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
Newsgroups: comp.unix.bsd
From: eichin@athena.mit.edu (Mark W. Eichin)
Subject: Re: which X386 in agate is better?
Organization: Massachusetts Institute of Technology
	<1992Sep9.211847.10985@menudo.uh.edu>
Date: Fri, 11 Sep 1992 08:30:11 GMT

> Is there any archive site which has 'stripped' X11 binaries ?
> Downloading 12M bytes of X386 server only (even though it is compressed)
> does not make sense to me since I'll never debug X386 server.
	Since I run at the end of a SLIP line (38,400 wire, but still
not ethernet) and I've mostly filled a 200M disk, I wanted a smaller
release for a lot of reasons... there are two things I've done that
you might find helpful (that I'd also like to see in any future X
binary release):
	1) strip all binaries. If I care, I'll build with symbols. If
*you* care, write a version of "pirts" and keep the symbols yourself.
[pirts is a reverse strip, I've seen a few people write them under BSD
-- it takes the symbols and puts them in a different file. Then, when
debugging something, you should be able to tell gdb "symbol-file
foo.syms" and have it look there instead of in the exec-file...]
	2) compress all the fonts. The X11R5 has inline code to
uncompress them on the fly... all you have to do with the current
release is remember to delete fonts.dir and run mkfontdir again in
each of the font directories (75dpi, 100dpi, misc.) I haven't noticed
any performance difference.
	My current installation only uses 40M (compressing the fonts
saves 6M by itself; stripping X386 saves over 10M...) and has *all* of
the user-level functionality of the original release...
				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
				Cygnus Support <eichin@cygnus.com>
ps. Above numbers using the agate:ports... version of Xfree86, not the
one in pub/incoming.
Newsgroups: comp.unix.bsd
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: 386bsd & timezone
Organization: tu-chemnitz
Date: Fri, 11 Sep 1992 16:35:42 GMT

Well folks, have seen the problems, too. In early 0.0 times, i've had
a look at those kernel sources which deal with CMOS time, and i remember
a comment of Bill saying ``probably we should keep CMOS time at UTC'' or
so. Of course, he is right. Well Americans, think far beyond your own
boundaries. Modern BSD's have a well designed time zone system on high
level. This respects the fact that European countries generally switch
to DST on other days than U.S., so the simple algorithm in the low level
kernel sources won't solve the problem even if it works fine. So i don't
know whether it's better to keep out all of TZ handling off the kernel,
and shouldn't we solve the problem of DOS not being able to handle the
UTC CMOS time???

	With best wishes
	J"org

--
J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
                                                              \     ~.~. 
	joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de         \   ~  | ~ 
	voice: +49-351-5965 137                                 \    ===
Newsgroups: comp.unix.bsd
From: paoletti@cps.msu.edu (David R. Paoletti)
Subject: 386BSD: 8MB fixed kernel available?
Originator: paoletti@pacific.cps.msu.edu
Organization: Dept. of Computer Science, Michigan State University
Date: Tue, 15 Sep 92 06:27:56 GMT

Is there an ftp site that has the patched kernel for the
8MB memory problem?  Anyone who's created one willing to
upload it to a site?

Thanks!
  Dave Paoletti :)
From: terry@uivlsi.csl.uiuc.edu (Terry Lee)
Newsgroups: comp.unix.bsd
Subject: Problem with OPTi?
Date: 7 Sep 92 06:19:11 GMT
Organization: Center for Reliable and High-Performance Computing, University of Illinois at Urbana-Champaign
NNTP-Posting-Host: uivlsi.csl.uiuc.edu
Keywords: OPTi

	Has anyone been able to get 0.1 to run on any 486 machine based on
an OPTi chipset?  If so, are you using the 486SXWB or 486WB motherboard?
I think I am experiencing bug BOOT009 in Nate Williams's bug list version 0.2,
where all of the boot floppies lock up the system after displaying the initial
copyright message (before listing any devices found).  I have an OPTi 486SXWB
motherboard (486DX-33, 06/06/91 AMI BIOS).  Please, I really need help with
this!  Also, if no one has found a fix, new buyers should be warned away from
this motherboard (or chipset)!  Thanks.

----------
Terry Lee
terry@uivlsi.csl.uiuc.edu
Newsgroups: comp.unix.bsd
From: mishra@joust1.dsg.dec.com (Alok Kumar Mishra)
Subject: X386/*/386BSD.X386-1.2E.bin.tar.Z-* cannot unpack 
Reply-To: mishra@joust1.dsg.dec.com (Alok Kumar Mishra)
Organization: Digital Equipment Corporation
Date: Sat, 12 Sep 1992 01:10:34 GMT

	I copied these files using ftp with image/binary option and when I tried
	
	cat /mnt/386BSD.X386* | uncompress | tar -xf -

	I got 

	stdin: not in compressed format

	then I tried  

	cat /mnt/386BSD.X386* |  tar -xf -

	I got

	cat: /mnt/386BSD.X386-1.2E.bin.tar: Input/output error
	tar: Skipping to next file header...

	Please tell me what I am doing wrong,

	also /pub/incoming/ 

	I cannot read ( this is because incoming directory do not have read permission
)
	Please tell me what are the files I should be looking for ,I want  entire 
	X11R5 distribution.

								Thanks
								Alok Kumar


Newsgroups: comp.unix.bsd
From: karn@servo.qualcomm.com (Phil Karn)
Subject: Re: [386BSD]
Organization: Qualcomm, Inc
Date: Sun, 13 Sep 1992 06:30:08 GMT

In article <Aug.29.15.45.59.1992.3059@athos.rutgers.edu> hedrick@athos.rutgers.edu (Charles Hedrick) writes:
>Character loss is normally in the device-level code.  If you're using
>a normal PC serial interface, the kernel must respond to an interrupt
>for each character before the next is ready.  At 9600 bps this
>requires an interrupt latency somewhat less than 1 msec. [...]

I've spent a *lot* of time minimizing interrupt latency in my code.
Even so, I strongly recommend using NS16550As with their 16-byte
FIFOs. With 16550As, even a lowly 10 Mhz 80286 running NOS easily
handles solid streams at 115.2 kb/s from a V.fast modem. The FIFO high
water mark immediately goes to 13 (the trigger point is at 4) so it's
obvious that the port would roll over and die without the '550.  Given
the greater complexity and context switching overhead of the 386BSD
kernel, I'd expect it to be much less able to keep up with a fast SLIP
link. (This is not meant as a slap at 386BSD, since that'd be
comparing apples and oranges. Or more precisely, timesharing systems
and dedicated routers. But sometimes there are significant advantages
to using dedicated routers.)

Phil
From: sxjcb@orca.alaska.edu (Jay C. Beavers)
Newsgroups: comp.unix.bsd
Subject: Spontaneous Reboots
Date: 4 Sep 92 21:14:59 GMT
Followup-To: comp.unix.bsd
Organization: University of Alaska Computer Network


In the past two days, I've had 386BSD 0.1 reboot twice.  Yesterday, the
only interactive session running was an ftp session out and today, the only
interactive session was running cops 1.04 in the foreground.  Previous to
yesterday, I never saw 386BSD 0.1 reboot itself like this.  Has anyone ever
seen this problem before?

 - jcb

______________________________________________________________________________
                                        |    jay@seaspray.uacn.alaska.edu
Jay C. Beavers                          |    sxjcb@orca.alaska.edu
University of Alaska Computer Network   |    sxjcb@alaska.bitnet
________________________________________|_____________________________________
Newsgroups: comp.unix.bsd
From: david@mlb.geomechanics.csiro.au (David Le Blanc)
Subject: Re: 386BSD PARTIAL PATCH KIT NOW AVAILABLE
Organization: CSIRO DIT (Melb.)
Date: 14 Sep 92 02:00:45 GMT

terry@cs.weber.edu (A Wizard of Earth C) writes:

>I have uploaded the first 19 patches and the patchkit software to the
>directory /pub/incoming/terry on agate.berkeley.edu.  This is not a
>complete set, as there are still 10-20 patches not yet in patchkit format.

>The following is a list of the patches in the current patch kit.
>Remember that the patchkit expects to start with a "virgin" kernel... no
>strange hacks allowed.

Please note that this is rather rude, and very restrictive.

Is your patch kit going to help me with the bus mouse driver I have to patch
in? Or make things hard?

Will it work with, or cause problems for those installing the patches for
using X386 ?

Will the X386 patches be incorporated?

Granted I have not seen the patchkit software, I would be happy if you
allowed a modular approach, so that I could add a patch to the
'patchkit' directory, edit some central config file, and run the software.

I may then select the new patch, and have it applied.

Could all patches be kept in a compressed form?

--
David Le Blanc                         :
Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
P.O. Box 54 Mt Waverley 3149	       : in Alien^3.
From: pjm@seeker.mystic.com (Patrick Miller)
Newsgroups: comp.unix.bsd
Subject: Does anyone have 386BSD working with a Bustek 542B?
Date: 14 Sep 92 13:47:41 GMT
Distribution: na
Organization: Mystic Software Pittsburg, Ca


  I have No Name 386/40 with a Cyrix CoProcessor.
  I can boot 386BSD off the floppy, and install the os. When I go to boot
  off the harddisk my floppy light stays on and the machine is hung.

  If I boot off the fixit disk I can mount and look at my hard disk.

  Machine: 
     386/40
     4 MB Ram
     Bustek 542B
     Maxtor XT8380
     Orchid Pro Designer 2s
     
  Thanks.
   pat

-- 

| Patrick J. Miller:                                                          |
| pjm@seeker.mystic.com || ns.pacbell.com!seeker!pjm                          |
|   ......and another Inode bytes the dust.                                   |
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: how do I put 386bsd on drive 2 <An answer>
Organization: TRW Financial Systems
Distribution:  comp
Date: Wed, 9 Sep 1992 06:15:46 GMT

In article <1992Sep8.135124.947@corax.udac.uu.se> goran@astro.uu.se (Goran Hammarback) writes:
>In article <92252.033510MHS108@psuvm.psu.edu>, Mark Solsman <MHS108@psuvm.psu.edu> writes:
>
>|> I have two esdi drives, I would like to make the first drive msdos, and
>|> the second drive 386bsd.  Can I do this, and how?  I am not sure, because
>|> 386bsd install only seems to look at drive one, and doesn't notice the big
>|> vacient sign on the partition table for drive two...
>
>There are two possibilites:
>
>* Open your PC and change cables and settings so the second disk
>  is the first disk, boot from the tinyBSD disk and let install do
>  it's stuff (or use the fixit disk and makeo a custom disklabel and
>  install so you get a decently sized swap partition).
>
>* Get a kernel that supports two disks, strip it and replace the kernel
>  on the fixit disk, boot from fixit, disklabel the second disk, mount
>  it and custom install.
>
>Either way, you now have a DOS disk, and a 386BSD disk.  The problem is
>that the PC ROM only allows you to boot from the first (DOS) disk, so to
>boot from the other disk you have to physically make it that disk the first
>one.
>This is not very practical (although I use that myself now, but that's
>because my stupid diskcontroller won't realize I have two disks on it 8-(.
>I bought a new one today, I hope that one works 8-) ).
>

I have my port of the MACH bootblocks in 'sortof alpha' testing at the
moment. One of the things it allows you to do is load the kernel from
the second drive. In my test system, disk1 is an ESDI and disk2 is a
SCSI drive. The bootblock from disk1 can load kernels from a BSD partition
on either drive. (the hard bit is making it stick.. even though
I tell the kernel what the bootdev is it always goes back to the
first one to act as root, but I'll fix that tomorrow I guess.)

anyhow, That allows you to boot with as little as
16 blocks on the first disk used up as the BSD bootloader.
I will be looking at modifying the os-bs stuff to have a menu
option of 'try other disk'
so even that (the 16 blocks) may not be needed.

The MACH bootblocks allow the sd(1,a)386bsd
type of line to be typed in.  ^  ^ ^ ^
			      |  | | |
			      |  | | Filename
			      |  | Partition
			      |  Disk number
			      Disk type (e.g. hd or fd)
looks real neat,
will be releasing as soon as I figure out how to get
the kernel from disk2 to mount disk2 as root, not disk1

+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v

Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Danpex EW-2016 Ethernet card on 386BSD?
Date: Sat, 05 Sep 92 09:04:48 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

Danpex EW-2016 is an inexpensive (US$85.) allegedly WD8013-compatible
ethernet card.  I was wondering if anyone has gotten 386BSD to
recognize it, and if so, what configuration and jumper settings they
used.

First of all, I am assuming that the card should be recognized even if
it is not connected to a network (my "network" is 2 computers, one of
which is down...).  Is this a reasonable assumption?

Second, the card does not support IRQ 2 (so much for compatibility...),
so I tried IRQ 9 and IRQ 15 and reconfigured the kernel accordingly, to
no avail.

But it is not clear what "iomem" should be.  The default for we0 is
0xd0000.  I presume this corresponds to the "RAM buffer base address"
jumper setting on the EW-2016.  If so, these addresses appear to be
tied to specific interrupt values.  For IRQ 15, for instance, I/O
(i.e., port) address 0x200 and iomem 0xdc00 (sic) are required.  I
tried iomem 0xdc000 too (with appropriate changes to the kernel), but
this didn't work either.  What are the implications, if any, of such
small iomem values (i.e., 0xd000 as opposed to 0xd0000)?

Finally, the default iosiz for we0 is 8K (8196).  Does it matter that
the EW-2016 RAM buffer size is 16K?  I tried both iosiz 8196 and 16384
to no avail.

As I am completely in the dark on this, any direction would be greatly
appreciated.  
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: SCSI -- CDROM Problems...
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Fri, 11 Sep 1992 21:38:17 GMT

I am attempting to connect a NEC CDR-37 CDROM drive to the AHA-1542
in my 386BSD system, without much luck.  I keep getting the famous
SCSI Sense: 0 0 0... message (say, in responst to a cat /dev/ras1a).

1) Is there a collected set of patches for SCSI support?

2) Has anyone succeeded in getting this or a similar configuration
working?

-- 
 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: david@mlb.geomechanics.csiro.au (David Le Blanc)
Subject: BUS mouse phantom button presses while swapping.
Organization: CSIRO DIT (Melb.)
Date:  7 Sep 92 00:56:19 GMT


While under a heavy load under X, with the machine paging to disk etc,
If I grab the mouse and move the pointer quickly, a menu might pop up, or
the text in an XTerm may get highlighted, then suddenly pasted back to the
xterm.

These phantom clicks  can be annoying. Has anyone else found  this?

If so, what have you done about it.

If not, what is your configuration?
Are you using the 30 or 60 interrupt setting?

--
David Le Blanc                         :
Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
P.O. Box 54 Mt Waverley 3149	       : in Alien^3.
From: tj2n+@andrew.cmu.edu (Tao Jiang)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Problem in using tip!
Date: 7 Sep 92 04:55:18 GMT
Organization: Doctoral student, Statistics, Carnegie Mellon, Pittsburgh, PA


I posted my question two days ago but no response yet.  Here is my
problem again.  Sorry for that.

I got a problem in using tip. After the dialing tone, (I think it connected
to the remote computer, cause the sound was just like I got via using kermit),
but after that, I lost connection.  The process is like the folowing:

[~/tmp] 41 --> dial-annex

dialing...
RING
call failed
[EOT]


I dont know what the problem is.  Can some one gives me help?

My .remote file is:

dial-annex|9600 Baud dial-out to another UNIX system:\
        :el=^U^C^R^O^D^S^Q:ie=%$:oe=^D:tc=SLIP-UNIX:
### the baud rate must match the rate you set on your modem...
SLIP-UNIX|9600 Baud Hayes attributes:\
        :dv=/dev/com1:br#9600:cu=/dev/com1:at=hayes:du:pn=5789896

Thanks!

TJ
From: adrian@ibmpcug.co.uk (Adrian Hall)
Newsgroups: comp.unix.bsd
Subject: Re: setting up 3c503
Date: 4 Sep 92 09:59:08 GMT
Organization: The IBM PC User Group, UK.

In article <0edeipG00WBK47QEVF@andrew.cmu.edu> aw2t+@andrew.cmu.edu (Alex R.N. Wetmore) writes:
>I need some help getting my 3c503 card to work with 386bsd.  bsd finds
>it on bootup (lists the ec0 device driver).  However, I think that the
>kernel is configured to use the BNC port instead of the AUI port.  I got
>mail from someone telling me to make the minor number of the device
>(/dev/ec0 i assume) less then 127, but I don't know the major number.  I
>have done a bit of pokeing around in the kernel sources, but haven't
>found anything (device.i386 doesn't list it).

This does not bode well for me in the future. The file you would want 
to look at I assume is /sys/sys.i386/isa/if_ec.[ch] (I think - I havent
got the src dist unpacked at this precise moment) - somewhere in there,
there will be the major and minor number of the device.

PS - If you get it going, please let me know what you did.

Adrian
-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
Newsgroups: comp.unix.bsd