HDTenEightyP/NetNews huggingface dataset:
From: peter@wiesel.cosy.sbg.ac.at (Peter Burgstaller)
Subject: Problems with XFree86
Organization: University of Salzburg / Austria
Date: Tue, 10 Nov 1992 09:21:54 GMT

Hi netters!
I installed 386bsd + XFree86 a few months ago!
Yesterday I got new hardware (harddisks ...) and wanted to install
some extra stuff.

1) I have a 386/40 with 2 Seagate disks 130MB (st3144a)
	The first harddisk was made by install, the
	second one I created a disktab with 16MB swap partition.
	I made the filesystem on the wd1 - everything ok.
	Then I tried to mount the swap-partition via swapon -a
	in rc and declared the /dev/rwd1b	sw	sw rw 0 0.
	but on bootup there is a message:
mount_sw sw no such file or directory.
	The same error occurs if i change the fstab-entry to:
	/dev/wd1b	sw	sw rw 0 0
or	/dev/rwd1b 	swap	swap rw 0 0 etc.

So this is my first problem.

2) I have a 486/33 with 2 connor disks cp30174E and wanted to have
	DOS and BSD on the 1st HD. Before I had the 2 seagates in this
	computer with also DOS and BSD on the 1st HD and it worked fine.
	Now (the same configuration like before with the seagates) I
	can't start X anymore (only from the 486, it works fine from 
	6 386 and it worked fine with the 486 and the seagates!)
	X tries to switch to 800x600 mode than holds a second and
	reboots the computer!
This is my second problem.

Any suggestions?
PLEASE!!!
- Peter 8-(
---
/-------------------------------------------------------------------\
| Peter Burgstaller| Student of Computerscience			    |
| (peter@cosy.sbg.ac.at)| in Salzburg, Austria (Europe)		    |
| "So Long, and Thanks for All the Fish" (Douglas Adams)	    |
\-------------------------------------------------------------------/


--
/-------------------------------------------------------------------\
| Peter Burgstaller| Student of Computerscience			    |
| (peter@cosy.sbg.ac.at)| in Salzburg, Austria (Europe)		    |
| "So Long, and Thanks for All the Fish" (Douglas Adams)	    |
\-------------------------------------------------------------------/
From: jcargill@oka.cs.wisc.edu (Jon Cargille)
Newsgroups: comp.unix.bsd
Subject: Re: CDROM for 386bsd (Re: ftp software inc, their address is...)
Date: 13 Nov 92 02:26:34 GMT
Organization: U of Wisconsin Madison - Computer Sciences

awb@ed.ac.uk (Alan W Black) writes:

>I suppose the whole question comes down to whether there are enough
>people out there that would be willing to buy a CDROM set up for
>(almost exclusive) use on 386bsd (and Linux).  I suppose
>eventually this will be the case but I'll just have to wait for
>the time being.

>Alan

I'm hoping that you won't have to wait all that long.  I guess I'm a
bit more optimistic about the number of interested people, though.
I'm hoping that if the cost is low enough, we'll have *lots* of
interested people.

Take part in my CD-ROM survey (posted separately today), so we know
what the real situation is!

Jon
-- 
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.
Jon Cargille		jcargill@cs.wisc.edu
Want your .sig compressed?  Reasonable rates
and fast turnaround. Call today!
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: BSD and Domain Name Server
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Thu, 12 Nov 1992 17:39:02 GMT

In article <1992Nov11.220849.11467@netcom.com> adasal@netcom.com (Salvatore Collora) writes:
   DOES ANYONE!!! know how to set up BSD 386 as a Domain Name Server.  I
   can't seem to get any of the available BIND programs running on it correctly.
   They all look for specific files and call certain commands that I am not
   familiar with.  

   Any help would be appreciated..

   Sal

ready to print (PostScript) sections from the net-2 release system
maintainer manual are available by anon ftp on gatekeeper.dec.com in
/.0/BSD/manuals and on nova.cc.purdue.edu (128.210.7.22) in
/pub/386bsd/submissions/bsd.manuals.

smm.11.named.ps.Z describes the files you create to set up the name
server.  There are examples of the files you need to create for a
given type of name server --- primary, secondary, or caching.  Rich
From: bob@obiwan.uucp (Bob Willcox)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd and D-Link DE 200+
Date: 12 Nov 92 03:52:48 GMT
Organization: Bob's Place, Austin TX

In article <1992Nov10.114652.42542@urz.unibas.ch> balmer@urz.unibas.ch writes:
>I successfully got 386bsd up and running. Unfortunately it does not 
>recognize my D-Link DE-200+ Ethernet adaptor. Does anybody know of
>a driver for this Ethernet adaptor?

I am running a DE-200 (no +) on my 386bsd system.  The DE-200 is
(according to D-link and my experience) a clone of the Novell NE-2000
and I am using the ne device driver.

-- 
Bob Willcox                ...!{rutgers|ames}!cs.utexas.edu!uudell!obiwan!bob
Phone: 512 258-4224 (home)
       512 838-3914 (work)
Newsgroups: comp.unix.bsd
From: bbs.barfeau@tsoft.sf-bay.org (David Fox)
Subject: [386bsd] patches for bash 1.12
Organization: The TSoft BBS and Public Access Unix, +1 415 969 8238
Date: Fri, 6 Nov 1992 18:57:15 GMT

Has anyone successfully compiled bash version 1.12 for 386bsd?  Could
you email me those patches or tell me where I could get them?  I got
the thing from GNU last night but it doesn't exactly compile correctly.
 

--
David Fox (bbs.barfeau@tsoft.sf-bay.org)
Newsgroups: comp.unix.bsd
From: gday@ignatz.inde.bc.ca (Gordon Day)
Subject: Re: Creating 386BSD bootable using a SUN
	<1992Nov13.073633.8338@autelca.ascom.ch>
Date: Fri, 13 Nov 1992 19:22:28 GMT
Organization: INDE Electronics, Inc.

> In article <1992Nov13.073633.8338@autelca.ascom.ch> nbladt@autelca.ascom.ch (Norbert Bladt) writes:
> 
>   % rich@catalpa.ssc.gov (Rich Verdier CAD) writes:
>   %
>   % I am trying to create the Tiny 386BSD bootable floppy after down
>   % loading the dist.fs file to my SUN.
>   %
>   % What is the approach now to create the floppy, the
>   % existing FAQ that Ihave acquired is unclear and the INSTALL.NOTES
>   % doesn't have pertinent info.
> 
> I did not try it, but the following should work, if you have a 3.5 floppy drive
> on your Sparcstation (don't know much about the 3/x0, although it should work
> an any UN*X system).
> 
> Just use "cp" to write the file to the floppy device /dev/fd0.
> If that fails, try "dd if=dist.fs of=/dev/fd0".
> That's about it.

Actually, you will _have_ to use the dd command (cp requires a file
system :-).  Be prepared to wait quite a while, however (e.g. 3-5
minutes). 

Ta,

Gordon.

_______________________________________________________________________________
gordon day, inde electronics, +1-403-430-1446.

--

_______________________________________________________________________________
gordon day, inde electronics, +1-403-430-1446.

Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: CDROM and Bill Jolitz's current work on CDROM
Organization: Trw Financial Systems
Date: Fri, 13 Nov 1992 20:30:25 GMT

Bill jolitz is doing work on CDrom at the moment
he has the high-sierra filesystem mountable and
is supporting the extended system that supports long filenames and 
arbitrary tree structures.

see his upcoming article in Dr Dobbs for more info.
I guess he should be included in any talk about what filesystem
to use on cdrom because he is working toward a bootable cdrom
and is not far away from achieving it as far as I know.

I will ask him to post a brief summary so we know which direction
we are heading in. (he normally doesnt get direct usenet).

also:
people have been asking what is in 0.2 and when it is due.

bill has told me that these are some things he would LIKE
to have in 0.2. whether they happen is unknown..

hi-sierra filesystem (apparently works)
merged vm/buffer cache (apparently more-or-less working)
different device interface..

somewhere in his plans he wants to also:
make shared libraries (kernel independent (!))
make loadable device drivers and filesystems.

of course he is very busy and these are only things he would like to do
so no guarentees on any of these, but I just thought I'd
mention them so that people don't get the idea that nothing is happenning.

julian
+----------------------------------+       ______ _  __
|   __--_|\  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,comp.sys.ibm.pc.hardware
From: davem@extro.ucc.su.OZ.AU (David Monro)
Subject: Re: bsd386 & msdos in 1 micro
Organization: Sydney University Computing Service, Sydney, NSW, Australia
Date: Thu, 12 Nov 1992 15:08:35 GMT

br.pct@RLG.Stanford.EDU (Peter C Tam) writes:

>Hi,

>  May be this is a FAQ, but I certainly do not know where the FAQ is.

>  I try to configure a 386/486 with IDE drive for: MSDOS, Window 3.1,  OS/2, 
>BSD386. The problem is 386/486 only boot off C disk. But looking  at things, 
>BSD386 seems to have a different file system than MSDOS (true?)

>  Does that implies I have to at least have 2 disk partitions, one for  
>BSD386 & 1 for the rest (MSDOS, Windows3.1, OS/2), & FDISK to activate  
>whichever partition?

>  Or have 2 hard disks, one for Unix, one for the rest, but than what 
>happens to the boot off only C drive restriction Or is some micro has boot
>drive configurable from CMOS?

>  Or is there another solution to this?

>  Thanks for any INFO!!!!!

>+---------------------------------------------------------------------------+
>| Peter C. Tam                         InterNet: br.pct@RLG.Stanford.EDU    |
>| Fax: (415) 964-0943                  BitNet:   br.pct@RLG.BITNET          |
>+---------------------------------------------------------------------------+

I'm running a machine which supports Linux (a free 386 *nix clone) and dos on
the same drive. Yes, you need multiple partitions - the unix will need its own,
and I think I've seen references to the OS/2 filesystem, so I guess it needs one
too.

Booting is not such a hassle - you install a program which gives you a menu to
play with, which then boots the appropriate partition. I believe OS/2 comes
with such a program, and Linux comes with one capable of booting other OS's
as well as itself.

These programs should also overcome the second-drive boot problem - but I don't
know about that as I only have one drive. In any case, you could have a small
boot partition on the first drive and keep most of the system on the other
for two of the operating systems. I am fairly certain I saw reference a while
back to someone running a two drive system running dos, OS/2 and Linux, all
selectable on bootup.

Anyway, good luck with it, it shouldn't be too hard to do - as long as you
have a fairly large drive to put it all on.

	David Monro
-- 
David Monro
e-mail: davem@extro.ucc.su.OZ.AU
-- 
David Monro
e-mail: davem@extro.ucc.su.OZ.AU
Xref: sparky comp.unix.bsd:8492 comp.os.linux:15805
From: hlu@eecs.wsu.edu (H.J. Lu)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Re: GNUCC 2.3.1 Available
Date: 5 Nov 92 22:13:50 GMT
Article-I.D.: serval.1992Nov5.221350.22943
Organization: School of EECS, Washington State University

>You can now get GCC 2.3.1 from pub/gnu/gcc-2.3.1.tar.Z
>on prep.ai.mit.edu by anonymous ftp.  Compressed diffs
>from version 2.2.2 in gcc-2.2.2-2.3.1.diff.Z are almost 2 meg.

I won't use gcc 2.3.1. It breaks quite a few things. I have made it
for Linux. But I will wait for at least 2.3.2.

H.J.
Newsgroups: comp.unix.bsd,comp.os.linux
From: mad@math.keio.ac.jp (MAEDA Atusi)
Subject: Re: IDE faster than SCSI-2
Reply-To: mad@math.keio.ac.jp
Organization: Faculty of Sci. and Tech., Keio Univ., Yokohama, Japan.
	<1992Nov6.012510.12371@ntuix.ntu.ac.sg>
Date: Sat, 7 Nov 1992 12:02:50 GMT

In article <1992Nov6.012510.12371@ntuix.ntu.ac.sg> eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:

 >MAEDA Atusi (mad@math.keio.ac.jp) wrote:
 >: The file size of one megabyte is too short to get meaningful result.
 >: You are just measuring the speed of copying to/from buffer cache.
 >
 >You may be right there but remember that Julian's machine runs at 50Mhz,
 >whereas mine at 33Mhz.
[deleted]
 >	  If you want a figure excluding the disk/buffer cache, take the read
 >figure.
 >	  If it were really all from buffer cache, then the write figure should
 >be much higher, equivalent to memory bandwidth, i.e. 25Mbyte/second.
 >	  Assuming 4 cycles of 50Mhz, 32 bit per cycle.

Maybe yes, maybe no.  The result includes buffer cache searching
overhead (which increases with more buffer cache pages).
25Mbyte/sec is unrealistic, even when no real I/O is performed.
System call of 1MB/512 = 2048 times can not be negligible.

 >	  buffer cache from 386bsd cannot be as large as 1 Mbyte.

I'm surprised with this.  I'm using Linux, which dynamically changes
buffer cache size according to system usage.  I oftenly observe the
size of buffer cache grows over 4MB on my system (8MB RAM) with heavy
I/O load.

FYI, on my systems (486DX/33, 256K cache, 8MB RAM, 200MB IDE, running
Linux 0.97pl6), IOZONE reports more than 5MB/sec given numbers smaller
than 4MB.  I wouldn't say my disk is 10 times faster than your SCSI-2 :-).
If I switch my disk to SCSI-2 and run the same test, the result wouldn't
be improved at all.

 >At least we are testing the efficiency of the use of buffer cache.
 >The latest version of iozone actually flushes the cache but I do not like this,
 >because that is not how we use unix file system. It does not measure realistic
 >situation.

If the buffer cache never exceeds 1 MB in 386bsd, just one linkage or
text formatting (with larege fonts) can easily flush the entire
contents of buffer cache.  And it's the usual way how we use unix file
systems.  Anyway, if you are testing the I/O speed in such a way, you
can never tell about the difference between IDE and SCSI2, because
disk speed is totally irrelevant.

 >: 
 >: You should give numbers at least twice as large as your RAM size.
 >: 
 >Actually I did that, but the figures are not informative. Not relevant to our
 >usual use. It confused more than it explains.
 >	  I advise people to ignore these "unrealistically high load".

IOZONE *is* intended to be given larege numbers.  Any other usage is
out of consideration of the author and thus (I think) results are not
very informative then.

;;;  Keio University
;;;    Faculty of Science and Technology
;;;      Department of Math
;;;		MAEDA Atusi (In Japan we write our family names first.)
;;;		mad@math.keio.ac.jp
Newsgroups: comp.unix.bsd
From: danson@lgc.com (Doug Anson)
Subject: NFS problems with 386bsd (pl58+)
Keywords: NFS 386BSD SVR4
Organization: LandMark Graphics Corporation LGC
Date: Mon, 9 Nov 1992 19:38:50 GMT

Hi:

I have a small two node network where one machine is running 386bsd and the
other is running SVR4.0.3.6. I have been NFS mounting a partition from the
386bsd machine to the SVR4.0.3.6 machine. With this mount, I have tried compiling a large application (i.e. gcc.2.3.1) for use in the SVR4 environment.
However, I have run into what looks like a memory leak in 386bsd within the
NFS (or wd8003) subsystem. 

Basically, what happens is that the NFS mount works fine when the NFS traffic
is fairly light. However, during heavy NFS I/O, I'll sometimes panic the
386bsd kernel. The panic complains:
                          kmem_malloc: kmem_map too small

I have increased the define  MAX_KMAPENT from 1000 to 1500 (I believe that
one of the 58 patches increased this define from 500 to 1000). This only
extends the life of the kernel but does not solve the problem.  I managed
to have the NFS up and flying for a day but it still crashed with the same
problem.

I basically want to know if anyone else has encountered this.. If so, I'll
begin snooping around to find any memory leaks. I have a virgin kernel patched
to pl58 with Terry's patches plus some added patches (locore.s alignment,
"ping" memory leak problem,... that were posted to this group. None of the
patches involed NFS and the "ping" patch fixed a memory leak in the ICMP level
I believe). The machine  running 386BSD is a Compaq 386/20 with 5Mb ram. The
standard install was used.

On another note, I noticed a posting regarding 0.2 of 386bsd.. I 
havent heard hide nor hare from the Jolitz's in a couple of months.. 
With the 58+ patches for 0.1 I agree that it is time to change the version.

Regarding 0.2, does anybody know that features, added value, etc... 0.2 will
contain?  Maybe the Jolitz's (without any added dates or other added stress...)
could give a brief list of the differences between 0.1 and 0.2 as they 
they currently stand.  I would personally be interested in knowing where 0.2
is going eventhough I am quite satisfied with 0.1.		

Doug
-- 
-------------------------------------------
Doug Anson					
Internet: danson@lgc.com			
Phone:	  713.560.1274
FAX:	  713.560.1277
SNAIL:    Landmark Graphics Corporation LGC	
	  15150 Memorial Drive
	  Houston, TX 77079			
-------------------------------------------
From: wade@leland.Stanford.EDU (Wade Hennessey)
Newsgroups: comp.unix.bsd
Subject: Using X386 with a PS/2 style mouse port
Date: 11 Nov 1992 05:44:09 GMT
Organization: DSG, Stanford University, CA 94305, USA
Distribution: world
NNTP-Posting-Host: sunrise.stanford.edu

Does anybody know how to get X386 to work with a microsoft mouse
connected to a PS/2 style mouse port? I'm runing 386bsd on
a Toshiba 4400sx notebook computer, and I can get X386mono to work
with the mouse connected to the com1 serial line. However, I want
to connect the mouse to the PS/2 style mouse port so I can use
/dev/com1 as a modem line. I've tried specifying "/dev/com2" as my
mouse device, that doesn't work. -wade
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] capslock -> control key mapping
Date: 11 Nov 92 11:59:36 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Distribution: comp
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <JKH.92Nov10142605@esel.lotus.com> jkh@esel.lotus.com (Jordan K Hubbard) writes:

>This is a very small patch, though it saves me numerous hairs pulled
>out.  To use it, apply the patch, set 'option "CAPS_LOCK_CTL"' in your
>kernel config file and remake/boot a new kernel.  Your caps lock key will
>then become your control key.  Note that this will *not* affect your
>key settings in X!  To do that, you'll need to use xmodmap to achieve
>the same effect (very easily done, fortunately).

>					Jordan


>*** /usr/src/sys.386bsd/i386/isa/pccons.c.pl3	Fri Nov  6 18:48:09 1992
>--- /usr/src/sys.386bsd/i386/isa/pccons.c	Tue Nov 10 15:18:41 1992
>***************
>*** 1205,1211 ****
>--- 1208,1218 ----
>  	KP,	"*",		"*",		"*",		/* 55 kp * */
>  	ALT,	"",		"",		"",		/* 56 alt */
>  	ASCII,	" ",		" ",		" ",		/* 57 space */
>+ #ifdef CAPS_LOCK_CTL
>+ 	CTL,	"",		"",		"",		/* 58 ctl */
>+ #else
>  	CAPS,	"",		"",		"",		/* 58 caps */
>+ #endif
>  	FUNC,	"\033[M",	"\033[Y",	"\033[k",	/* 59 f1 */
>  	FUNC,	"\033[N",	"\033[Z",	"\033[l",	/* 60 f2 */
>  	FUNC,	"\033[O",	"\033[a",	"\033[m",	/* 61 f3 */

>			PCS Computer Systeme GmbH, Munich, West Germany
>	UUCP:		pyramid!pcsbst!gj gj@meepmeep.pcs.com
>	EUNET:		unido!pcsbst!gj

This patch is obsolete with codriver (aka keycap-0.1.1.tar.Z), it has been
obsolete since the first days of the 0.1.0 version and Helmut Michaelis'
vgadrv. Don't mess around with the internal keyboard tables just to get
some special behavior; it is highly nonportable.

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|  | /   Dept. of Electr. Eng.   |   Sorry, the above really good fortune has
|  |/    Inst. f. Dataprocessing |      been CENSORED because of obscenity"
From: lumpi@dobag.in-berlin.de (Joern Lubkoll)
Newsgroups: comp.unix.bsd
Subject: < SpeedStar 24X and XFree386 >
Date: 10 Nov 1992 22:23:19 +0100
Organization: dobag Berlin
NNTP-Posting-Host: dobag.in-berlin.de

Is it possible to run the speedstar 24X with XFree86 - I can't even get it
to run in the normal VGA Mode. X386 starts clear the screen and simply dies.

What do i have to do to run it ? (Patches are installed, so that X may run)

jl



-- 
The left being rich - trying to shut their guilt for knocking down dreams, 
before they'r even build.	(Anne Clark)

lumpi@{dobag.in-berlin.de,fu-berlin.de], lubkoll@cs.tu-berlin.de
Newsgroups: comp.unix.bsd
From: glenc@netcom.com (Glen Collins)
Subject: [386bsd] Install?
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: na
Date: Tue, 10 Nov 1992 03:10:11 GMT

Hello!

	Well I have not yet received any reply's for help in installing
386bsd. Can you please e-mail mer post here about a solution????
I can now see that it maybe a bios setting. I have tried to install
linux also with the same problems. Here is what I have:

	Hot307 80386 33/40
	AMI Bios/ OPTI chipset
	Total of now 6 Megs of memory
	104 Meg harddrive (rll'ed)
		68 Megs for 386bsd
		 5 Meg boot partition
		30 Meg extended dos partition
	Generic WD Harddrive/Floppy controller
	Trident SVGA card (1 meg)
	Microsoft mouse
	Proaudio spectrum card



Now the problem I am having is when I type install it seems to work okay
until it gets to the high level formating of 386bsd storage. The system
hangs and I must use the reset button to restart. Could this be a problem
with newfs and chipset settings? I have taken all cards out except the svga
card and floppy/harddrive controller and still no dice. Could it be a stray
interrupt problem with the floppy drive? I noticed when I tried to install
linux, it said there  was a stray interrupt. Could it be that? Please help!
I have in the past week picked up the WD bootable fix from berekely and
the dist.fs for no ehternet controller but it still won't continue from
that sticking point.
From: gfoster@charm.isi.edu (Glen A. Foster)
Newsgroups: comp.unix.bsd
Subject: Stupid new user questions
Date: 12 Nov 92 18:08:55 GMT
Organization: USC/ISI, Marina del Rey, CA


Got through the install scripts with no difficulty and am having a
couple of problems.

1) after an ifconfig of the ethernet board I get a recurring error
message "reject 65531" (underlined) about once a second. Board is a
WD8003e IRQ 2 I/O 280. The error messages stop if one downs the
interface.  When pinging the address from another machine, no echo
reply is returned. 

2) the floppy drive light lights up when booting off the hard disk and
stays on thereafter. Any attempt to access it results in the program
used (mread and/or loadfd) hanging indefinitely with the disk spinning
but the head never moving. Board is an Adaptec 1542b, system is an
Everex 3000 386.

Any "instant fixes" for these? 

Any assistance will be greatly appreciated.

Glen Foster
Newsgroups: comp.unix.bsd