HDTenEightyP/NetNews huggingface dataset:
From: randy@chinet.chi.il.us (Randy Suess)
Subject: Re: Minor XFree86 problems, long function key string bug in elvis
Organization: Chinet - Public Access UNIX
Date: Wed, 30 Dec 1992 14:24:53 GMT

In article <1992Dec30.005909.15079@tackle.uucp> jc@tackle.uucp (John Capo) writes:
>I have XFree86 running and only have a few problems left to solve.
>Another thing I have noticed is that my machine is on its knees when
>I am compiling and running X at the same time.  
>    No name 386/33, 8M RAM, 128K cache.

	I have found that 8 megs memory is enough to bring X up with
	an xterm and that is about it without swapping.  Putting
	another 4 megs of ram in helps a lot and 16 megs makes it
	the fastest x86 based X system I have seen.
	This is not bad, as my sysvr4 system will barely run all
	by itself with 8 megs, and even with 16 megs, it swaps all
	over the place with X.
-- 
	I am created Shiva the Destroyer; Death, the shatterer of worlds!
	Who is this dog meat who stands before me now?
	That's the biz, sweetheart.
Randy Suess					 randy@chinet.chi.il.us
From: DS1437@acspr1.acs.brockport.edu
Newsgroups: comp.unix.bsd
Subject: 386BSD Kernel hang problems on Gateway 2000 486/DX2
Date: 22 Dec 1992 12:19:39 -0600
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu


    I am trying to install 386bsd on a GateWay 2000 486 50Mhz DX/2. The
system has a 205 Mb IDE Drive. I can run the install disk fine, however
when I boot off the hard drive the screen looks like this:

pc0<color> at 0x60 irq 1 on isa
com1 at 0x3f8 irq 4 on isa
com2 at 0x2f8 irq 3 on isa
/* There is a sufficient long delay here for some reason */
fd0 drives 0:1.44M, 1:1.2M at 0x3f0 irq 6 drq 2 on isa
ne0 ethernet address 02:00:00:00:14:e4 at 0x300 irq 9 on isa
npx0 at 0xf0 irq 13 on isa

PANIC: Cannont mount root
trap type 12 code=fe060000 eip=fe01278a cs=8 eflags=10282 cr2 14 cpl a

PANIC: trap

/* It then says something about dumping the memory to the device and */
/* Gets a --device bad message */

    Notice that the hard drive controller was never listed in the list,
however when I boot from the fixit or install disk it looks the exact same
except where the delay occurs I get a line like:

wd0 <WDC AC2200F> at 0x1f0 irq 14 on isa

If I boot with the fixit disk, I then can mount the hard drive without
a problem. I tried copying the kernel from the fixit to the hard drive,
and even tried changing the device files still it did it.
I downloaded the unofficial fixes which claim that wd.c was fixed, and that
still did not change a thing. (In directory newbootables)
I have not tried the compaq bootable fixed yet, however what I have
been told by Adrian@rachel.ibmpcug.co.uk that the compaq fix is something
totally different, and that fix would not work in this case.
    Do anyone have any incling why the kernel is not initializing the
hard drive controller correctly as that looks like the problem to me?


****************************************************************************
Name: Donald L. Schleede                      Snail-Mail:
Call: KB2LZF (kb2lzf@wb2wxq.ny.na.usa)          Dept. Earth Sciences
E-mail Addresses:                               SUNY Brockport
 ds1437@acspr1.acs.brockport.edu                Brockport, NY 14420
 dschleede@unidata.ucar.edu                   Twisted Pair:
 root@kb2lzf.UUCP                               (716) 395-5718
Planet: Earth
****************************************************************************
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: [386bsd] looking for logitech bms driver 
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Fri, 1 Jan 1993 06:09:32 GMT

In article <1992Dec31.155414.9400@Informatik.TU-Muenchen.DE> gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
>You get obtain it from ftp.informatik.tu-muenchen.de in
>/pub/BSD/386BSD/0.1/unofficial/drivers/mouse/logitech

Well, how can people in psi.net get it?  Your ftp server blows me off because
I'm coming in through psi.net.
-- 
-- Email info@NeoSoft.com for info on getting interactive Internet access.
"In a minute, I'll burp up your droid."
Newsgroups: comp.unix.bsd
From: dawes@physics.su.OZ.AU (David Dawes)
Subject: Re: [386bsd] happy new year
Keywords: clock.c patch
Organization: School of Physics, University of Sydney, Australia
Date: Sun, 3 Jan 1993 03:48:05 GMT

In article <fXrM6yq@quack.sac.ca.us> dfox@quack.sac.ca.us (David Fox) writes:
>Hi.
>
>I've tried both Andrew Chernov's and Bruce Evans' patches for the
>'happy new year' problem where the date was repeated - i.e., on
>Jan 1 93, 386bsd reports the date as 12/31/92.
>
>I don't experience the problem as such.  On my 386bsd, I get two
>Jan 1 dates - on Jan 2 (today), 386bsd reports the date as Jan 1.
>
>Bruce says it might be because of timezone differences, nevertheless,
>I've tried both patches, and neither works for me.  With the patch
>installed (doesn't matter which one), the date returned is 'Mon Jan 6';
>clearly incorrect.

I assume the year is showing up as 1992 (6 Jan 1992 was a Monday).

The patch works for me, but both Andrew, Bruce (and I) are east of GMT/UTC
while you are west (so the TZ sign will be different).  Anyone else
tried these patches?  The results from someone at GMT might be
interesting.

David
--
------------------------------------------------------------------------------
 David Dawes <dawes@physics.su.oz.au>    DoD#210      | Phone: +61 2 692 2639
 School of Physics, University of Sydney, Australia   | Fax:   +61 2 660 2903
------------------------------------------------------------------------------
 I was so satisfied, deep down inside, like a hand in a velvet glove -- AC/DC
------------------------------------------------------------------------------
From: duplain@rtf.bt.co.uk (Andy Duplain)
Newsgroups: comp.unix.bsd
Subject: Patch to allow ps(1) to identify console-controlled processes
Date: 21 Dec 92 15:46:52 GMT
Organization: BT Customer Systems, Brighton, UK


	Hi, here is a hack to allow ps(1) to see processes that have the
	console as there controlling tty.  I don't understand why there
	is both a console and a PC console device, but basically all
	processes that are controlled from the console have the major device
	number of 12, while /dev/console has a major device number of 0.  An
	alternative solution _could_ be to add a filesystem node for the
	PC console device and then run dev_mkdb(8) again (having changed the
	definition of _PATH_CONSOLE from /dev/console to /dev/whatever).

	I don't have X running so these things may have been patched properly
	by someone else...

	Apply these patches at your own risk --  THEY CERTAINLY ARE A HACK!

*** ps.c.ORIG	Mon Dec 21 15:23:58 1992
--- ps.c	Mon Dec 21 15:33:45 1992
***************
*** 195,203 ****
  			struct stat stbuf;
  			char pathbuf[MAXPATHLEN];
  
! 			if (strcmp(optarg, "co") == 0)
! 				ttypath = _PATH_CONSOLE;
! 			else if (*optarg != '/')
  				(void) sprintf(ttypath = pathbuf, "%s%s",
  				    _PATH_TTY, optarg);
  			else
--- 195,204 ----
  			struct stat stbuf;
  			char pathbuf[MAXPATHLEN];
  
! 			if (strcmp(optarg, "co") == 0) {
! 				ttydev = 0x0c00;	/* HACK!!! */
! 				break;
! 			} else if (*optarg != '/')
  				(void) sprintf(ttypath = pathbuf, "%s%s",
  				    _PATH_TTY, optarg);
  			else
*** devname.c.ORIG	Mon Dec 21 15:09:00 1992
--- devname.c	Mon Dec 21 15:27:04 1992
***************
*** 54,59 ****
--- 54,65 ----
  	static int failure;
  	DBT data, key;
  
+ 	/* hack to allow processes with the PC console device as there
+ 	   controlling tty to be seen -- duplain@btcs.bt.co.uk */
+ 
+ 	if (major(dev) == 12)
+ 		return ("co");
+ 
  	if (!db && !failure &&
  	    !(db = hash_open(_PATH_DEVDB, O_RDONLY, 0, NULL))) {
  		(void)fprintf(stderr,


-- 
Andy Duplain, BT Customer Systems, Brighton, UK.           duplain@rtf.bt.co.uk
#define	DISCLAIMER      My views and opinions are my own, and not my company's
Newsgroups: comp.unix.bsd
From: /S=BLANSFIE/OU=EM-01/O=CCMGW/PRMD=GOV+USDOE.G02/ADMD=ATTMAIL/C=US/@mailgw.er.doe.gov
Newsgroups: comp.unix.bsd
Subject: [386bsd] 2 drive kernel and NE2000.
Date: 30 Dec 1992 09:49:06 -0600
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

     I recently installed the 2 drive kernel from Randy Suess and it saw 
     the other drive fine but he has the NE2000 irq set to 11.  In my 
     previous version irq was set to 9 (which is really irq 2 on the 
     board).  My question is has anybody got this to work on an NE2000 and 
     if so what irq settings on the board do you use for irq 11?
     
     Any help appreciated and shared!
     
     Mike
     blansfie@mailgw.er.doe.gov
     WAN Services CDSI - DOE EM  
     "EM = Environmental Management = an oxymoron"
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (& Murphey)
Subject: Re: Font Problems with Xfree86
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Thu, 31 Dec 1992 04:26:20 GMT

>>>>> In article <9212302201.AA01419@deepthought.cs.utexas.edu>, DS1437@acspr1.acs.brockport.edu writes:
R>From: rich@Rice.edu (& Murphey)
R>Subject: Re: Xfree86 Font directory problem?
R>>>>>> In article <9212300215.AA00524@deepthought.cs.utexas.edu>, DS1437@acspr1.acs.brockport.edu writes:
R>D> NNTP-Posting-Host: cs.utexas.edu
R>
R>D>     I am having problems getting Xfree86 running, it seems to initiaize
R>D> the screen fine , but then switches back to text, and hangs the console
R>D> port (still can telnet in). I found out that there is an error that
R>D> the server is reporting but never showing, I can only get this error on
R>D> a system that is telneted in, it is:
R>
R>D> failed to set default font path '/usr/X386/lib/X11/fonts/misc/,/usr/X386
R>D> /lib/X11/fonts/75dpi/'
R>D> Fatal server error:
R>D> could not open default font 'fixed'
R>
R>The XFree86 1.1 server checks the font path  more thoroughly if you
R>set it in your Xconfig than if you use the default.  Try setting it:
R>
R>FontPath "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/75dpi/"
R>
R>and see if that helps.  We are working on improving this for the next
R>release.  Rich

D>     I think thats where the server was getting the name for the font
D> directories. Sorry I was going to include my Xconfig file in the message
D> too, but I forgot. Here it is --


D> #########################################################################
D> RGBPath                "/usr/X386/lib/X11/rgb"
D> FontPath         "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/75dpi/"
[...]

I was mistaken about the version 1.1 XFree86 server -- It doesn't
verify the font path at all.  So you need make sure that every
directory in your font path is a valid directory containing fonts.dir
file, etc.  You could simplify it to a single directory such as:

FontPath         "/usr/X386/lib/X11/fonts/misc/"

Another tip: the fonts distributed with the 386BSD binaries are
intensionally compressed.  If you uncompress them you must run
'mkfontdir' to rebuild the fonts.dir file.  Uncompressing them and
failing to do that could cause the "could not open default font
'fixed'" message.  Rich
From: brad@FCR.COM (Brad Parker)
Newsgroups: comp.unix.bsd
Subject: BSD Multicast on 386BSD?
Date: 23 Dec 92 12:41:45 GMT
Distribution: inet
Organization: FCR Software Inc., Boston, MA
NNTP-Posting-Host: stemwinder.fcr.com


I saw someone ask about about multicast extensions to 386BSD.  I'm adding
them as we speak (looks very straight forward).  I was wondering if I
was duplicating efforts?

If anyone wants to run a multicase tunnel and test audio, let me know.

-brad
--
Politically correct term for `corrupt': Ethically different, morally challenged

Brad Parker	FCR Software, Inc., Boston, Ma.	brad@fcr.com
Newsgroups: comp.unix.bsd
From: bde@runx.oz.au (Bruce Evans)
Subject: Re: [386 BSD] Permissions set wrong - HELP
Organization: RUNX Un*x Timeshare.  Sydney, Australia.
Date: Fri, 1 Jan 93 10:53:59 GMT

In article <C0618x.6uL@ais.org> draper@ais.org (Patrick Draper) writes:
>
>The directory /tmp didn't have access for others to write to it. Also, the
>directory /var/tmp didn't have access either.
>
>Why are these directories set up this way? I switched them, but I don't know
>what problems this will cause in the future.

They are just wrong.  If you unpack the bin01 distribution, it will create
the directory /tmp with permissions rwxr-xr-x because /tmp is not actually
in the bin01 distribution, only the file /tmp/install.bin01 is there, so
cpio creates /tmp with the default permissions.

I'm not very familiar with /tmp and had trouble getting the right
directories in the archive when I repacked the src01 distribution.  (The
src01 distribution can be packed in only 34 files of size 240640 instead
of 61, by removing 2.5MB of junk uucp binaries and compressing it with
zip).  One advantage of cpio over tar is that it restores directory
permissions so the default /tmp permissions would get fixed up by a
/tmp with the correct permissions in another archive.
-- 
Bruce Evans  (bde@runx.oz.au)
From: mark@roissy.umd.edu (Mark Sienkiewicz)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] Kernel build dies, unref symbol _version
Date: 23 Dec 92 16:22:02 GMT
Organization: University of Maryland

In article <BznK64.AGL@NeoSoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes:
>>"init_main.o: something about an unreferenced symbol _version"
>>is there a standard fix for this?
>
>Yeah, ATFP.  Add The Fine Patchkit.  This problem is fixed by patch #1.
>

If you look in the ls-lR file from agate.berkeley.edu (which appears
to be the primary ftp site for 386bsd), you will find a directory
that looks like this:

	pub/386BSD/386bsd-0.1/patches:
	total 0

Hmmmm... doesn't look promising...  BUT if you look long enough, you may
also find

	pub/386BSD/386bsd-0.1/unofficial/terry/beta.patch.kit:
	total 372
	-rw-r--r--  1 cgd          2172 Oct  5 11:33 README.1ST.Beta-1
	-rw-r--r--  1 cgd          8569 Oct  5 11:33 README.Beta-1
	-rw-r--r--  1 cgd        358400 Oct  5 11:33 patchkit-0.1.tar.Beta-1

Which _appears_ to be the patchkit that everybody is talking about.  Can
anyone confirm or deny that "unofficial/terry/beta.patch.kit" is the
"official" patch kit?
From: smace@nyx.cs.du.edu (Scott Mace)
Subject: [386BSD] XLock-2.3 avaiable on ref
Organization: Nyx, Public Access Unix @ U. of Denver Math/CS dept.
Distribution: usa
Date: Mon, 28 Dec 92 06:47:06 GMT

Here is Xlock 2.3 X-Windows screen saver for Xfree86

get it from ref.tfs.com  /usr/packages/xlock/XLock-2.3

I added several ifdef's for 386bsd-- particularly for usleep() and rint().

usleep.c:   decided to use xlock's usleep instead of 386bsd's 

worm.c:     used floor() instead of rint(), since rint() wasn't in libm.a
            hopefully this will work without a math coprocessor..
	    please send mail if it does...

xlock.c:    used usleep_xlock() instead of usleep() 

xlock.386bsd.diff:   diff to original xlock sources..

sources included are allready patched.

use xmkmf -a  and use the Imakefile instead of the makefile that comes
with the original sources...

Do    make install    and    make install.man    to install everything.

Scott Mace
emace@tenet.edu
--
*********************************************************************
*    Scott Mace                internet:    smace@nyx.cs.du.edu     *
*                                           emace@tenet.edu         *
*********************************************************************
Newsgroups: comp.unix.bsd
Newsgroups: comp.unix.bsd


Hello,

  I think you have all the ifconfig lines in /etc/netstart 
uncommented. You should only uncomment the ifconfig line of the
interface you actually have.

  a short list:

ne0  Novell NE2000 ethernet card
ec0  3Com              "     "
sl0  Slip serial interface
we0  Western disgital/ smc 8000 ethernet card
is0  isolan isolink ethernet
lo0  Local loopback interface. (uncomment this one to test the TCP/IP
                                software. recommended!)


Reinier Kleipool

  /\
-(  )-/##---------------------------------------------------------------------
  }{/   ##    One has to look out  -- Overschie ------------------------------
.====.        for engineers- they  -- Reinier Kleipool  ----------------------
| [] |   begin with sewing machi-  -- Mail -----------------------------------
|    |   nes and  end up with the  -- X400: C=nl A=400net P=hp O=hp S=Kleipool
|    |   atomic bomb.....          -- desk: Reinier Kleipool/ hpitcb/75     --
| [] |              Marcel Pagnol  -- unix: reink@hpuamsa.heth.hp.cm        --
------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: ashley@gidday.enet.dec.com (STEPHEN ASHLEY)
Subject: 386bsd on a laptop (extract wait?)
Organization: Digital Equipment Corporation
Date:  1 JAN 93 02:53:28 AES


        I am trying to install 386bsd on to my laptop, its a 386sx16, 2Mb ram
and a 40Meg drive. Now I know its nothing flash or fast, but the release notes
indicated that you could fit the bin01 on to a 40Meg drive and that 386bsd
would run with only 2Mb of memory. The install went through fine, but the
extract is taking "for ever" (over 5 hours now). How long should I wait? It
seems to be doing some thing, the Hard drive LED is working over time. Has
anyone done an install on to a 40Meg drive? Or have I got it all wrong.
Please E-Mail replys to ashley@yakka.enet.dec.com or ashley@wokka.enet.dec.com

	Thanks,
	Stephen Ashley.
	Alice Springs Out Back Australia.
Newsgroups: comp.unix.bsd
From: gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart)
Subject: Re: Any idiot-proof partitioning software?
Organization: Technische Universitaet Muenchen, Germany
Date: Wed, 30 Dec 1992 11:19:33 GMT

In article <bob-291292152735@beamlab.ps.uci.edu> bob@beamlab.ps.uci.edu (bob prohaska) writes:
>
>Does there exist a foolproof (!) partitioning program which
>can be used to set up partitions for 386BSD?  I gather that
>expert use of disklabel will do the job, but I've read
>the man pages and don't want to become that expert if it can
>be avoided.  The disk to be partitioned is under control of
>an adaptec 1542b.

There was a 386bsd-version of FDISK posted recently. For those who
are more familiar with that DOS-partitioner, it might be easier to partition
their disk with it. But you still have to mark the 386BSD-Partition 
with the A5-ID so that the install program will find the 386BSD-partition
and write a correct disklabel.
Fdisk can be found at ftp.informatik.tu-muenchen.de in 
/pub/BSD/386BSD/0.1-ports/misc/fdisk.Z

Ralf
Newsgroups: comp.unix.bsd,comp.os.linux
From: s0356514@let.rug.nl (H.H. Bergman)
Subject: Re: UNICODE (was Dumb Americans (was INTERNATIONALIZATION:...)
Organization: Faculteit der Letteren, Rijksuniversiteit Groningen, NL
X-Newsreader: TIN [version 1.1 PL6]
Date: Mon, 21 Dec 1992 19:49:42 GMT

Ed Carp (erc@unislc.uucp) wrote:
: Richard L. Goerwitz (goer@kimbark.uchicago.edu) wrote:
: 
: : One of the big criticism leveled at US Engineers is that they are either
: : too dumb or lazy to build into their software support for non-Western
: : scripts.
: 
: I'd be more than happy to build internationalization into my code, if I knew how
: to do it... <sigh>
Plan 9 supports Unicode/UTF. They have postscript manuals available somewhere
too. Unicode uses 16 bit characters with the usual 7-bit ASCII set included
in the beginning. UTF is a special encoding that is compatible with normal
7-bit ASCII files, as long as you use only the regular ASCII chars. For
higher characters it uses a multibyte sequence.
The problem with Unicode is of course, that to support it fully, you'll need
to adapt all existing programs. [And displaying non-ascii characters on a 
simple terminal is out of the question.]

There are two books published by the Unicode Consortium that describe
the unicode standard. I've only seen the second part, but from reading
that, the first part seems to be pretty essential. They cost about $40
here each, I think, so I haven't bought them yet.

It would be possible to map a subset of the Unicode characters to ASCII or
Latin-1 in order to display tex on simple non-graphic terminals. 
Xwindows seems to support 16-bit characters too, but I have no
info about that at all.

*Lots* [I dare say, nearly every C program in existence] of programs
assume sizeof(char)=1 byte.  With Unicode this is no longer true, causing
lots of problems for characters > 127.

If enough people want this, I may consider writing a support library for
Unicode/UTF to provide basic manipulations. [But I'll first have to do
some more hacking on my QIC-02 driver...] Somebody want to donate Unicode
fonts to GNU? [They also need other free fonts btw.]

Once the GNU text/file/bin utils support Unicode/UFT, others will probably
follow, but it would still require *lots* of effort.

Linus, how would you feel about having Unicode support in the kernel?
Having Unicode filenames would be really cool. ;-)

: -- 
: Ed Carp			erc@apple.com, erc@saturn.upl.com	801/538-0177

--Hennus Bergman
Newsgroups: comp.unix.bsd
From: adrian@rachel.ibmpcug.co.uk (Adrian Hall)
Subject: New kernel on rachel.ibmpcug.co.uk
Organization: The IBM PC User Group, UK.
Date: Tue, 22 Dec 1992 17:54:31 GMT

For those with not enough memory/disk space to compile their own
kernels, the latest (?) kernel on rachel.ibmpcug.co.uk has the
following in it :-

	Standard srcdist kernel
	All patches (1-58) except patch 47 applied
	New NE-2000 driver.

The config for the kernel is in kernels/current.CONFIG, and the
kernel itself is in kernels/current. At the moment, it has drivers
for

	wd0/wd1
	as0/as1
	fd0/fd1
	com1/com2
	npx0
	ne0/we0/ec0/ic0
	wt0

	32 users, 48 ptys

If anyone has the context diffs required to make the kernel with
a nice lpt driver could they please mail adrian@rachel.ibmpcug.co.uk
with them, and I will put them in.

	Adrian
-- 
------------------------------------------------------------------------------
Adrian Hall				Telephone: +44 (0)81 863 1191
Connect Systems Manager			Fax:	   +44 (0)81 863 6095
The IBM PC User Group			Internet:  adrian@ibmpcug.co.uk
Newsgroups: comp.unix.bsd,comp.os.linux