HDTenEightyP/NetNews huggingface dataset:
From: dror@netcom.com (Oz Dror)
Subject:  Exclusive Access to a Parallel port by Dos under Unix
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Mon, 16 Nov 1992 00:38:23 GMT

I have a LaserDisk controlled by a signal from a parallel port.
There is a special driver that controls the laser disk.

The system works Under DOS, but does not work in dos Under unix
(SCO 3.2.2, with dos merge).

I issue the following command:
  dos +alp2
and in config.sys I setup the driver.
when dos boots it initializes the driver, but the program freezes (actually it
goes to an infinite loop.

My understanding is that the driver is time dependent.

Does anyone have any idea how to solve this problem. Do I need to increase the
interrupt level of the serial port, if so how can I do is without changing the
dos Driver.
-- 
NAME   Oz Dror, Los Angeles, California
SMAIL  dror@netcom.com
PHONE  (213) 874-7978  Fax (213) 667-6908
From: ssanbeg@visual.spk.wa.us (Scott Sanbeg)
Newsgroups: comp.unix.sysv386
Subject: Re: Trying to install SCO UNIX 3.2 on a clone 386dx 40
Date: 19 Nov 92 03:32:45 GMT
Organization: The Visual Market - Spokane, WA

In article <199211181255.AA07646@europa.eng.gtefsd.com> stewart@europa.eng.gtefsd.com (Brad Stewart) writes:
>Trying to install SCO UNIX 3.2 on a clone 386dx 40.  After booting the first 
>installation disk, the installation procedure goes through a series of test 
>(A through Z).  My system hangs at G8.  The installation procedure does not 

I'm running SCO UNIX 3.2.4 on an AMD 40Mhz chip-ed motherboard. It's run
fine for nearly 9 months - very fine. So I doubt your complaint is
chip related...

>tell me what this means.  By trial and error I installed a serial i/o card, I 
>get to the same spot where the error G8 occurs and then the system 
>automatically re-sets and re-boots even though it shouldn't (I think) and 

Assuming we're running the same version of the OS, the serial ports
are not installed until after the system installation. The Link Kit
included. After booting into maintenance mode, I went into sysadmsh:
System -> Hardware -> Parallel. There, I installed two 16550AFN ports
on *one* card as follows - first installing 1 IBM port at the default
address; secondly, installing 1 IBM port at the default address again;
the first as COM1 and then COM2. I did *not* (could not) install
this card as a multi-port card.

Shoot some email my way if you want some more help with this.
Scott


 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Scott Sanbeg     UNIX Systems Administrator       (509)535-2561
ssanbeg@visual.spk.wa.us (or) ...!uunet!tau-ceti!visual!ssanbeg
From: tan@bronson.uucp (Tan Bronson)
Newsgroups: comp.unix.sysv386
Subject: Installing SAS 1.25 on Dell's svr4 Issue 2.2
Date: 13 Nov 92 23:31:47 GMT
Organization: Microvation Consultants 20 Sperry Rd Madison, Ct 04663


    I got fed up with Dell Issue 2.2 hanging as I've described
in previous posting. i.e. hung with one the folloing console messages:
    - asyrtmout: no msg blocks 
    - ldterm(ldtermsrv) out of blocks
    Dell technical support is supposed to be working on the problem,
but I'm not aware of any fixes available for this.  So as per a suggestion
from "tsm@UUCP-GW.CC.UH.EDU (Tami S. Mondy)" I decided to try installing
SAS 1.25.

    I'm trying to replace the com{1,2} driver, so my first attempt
to load both the sas and asy driver failed to an address conflict.
I decided to disable asy by editing /etc/conf/sdevice.d/asy and
rebuilt the kernel using /etc/conf/bin/idbuild. This resulted in
an undefined 'asy_tty'.

    Has anyone managed to install SAS to replace the default 'asy'
driver on Dell Issue 2.2? What will break if a bogus 'asy_tty' is
created?

    Is it possible to have both the 'asy' and 'sas' drivers installed
and only chose one of them at run time? I recall that I could do so
with ISC 2.2, but I may have been mistaken.

    Any clues on how to install this driver or where to RTFM will
be greatly appreciated!
-- 
Tan Bronson		tan@Microvation.COM (or tan@bronson.UUCP)
Microvation Consultants 20 Sperry Road 		Madison, CT 06443
			Voice: (203)-421-5061	Fax: (203)-421-5292
Newsgroups: comp.unix.sysv386
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: ISC 2.2 (Sys V Rel 3.2) Adding Swap?
Organization: American Micro Group, Ft. Lee  NJ
Date: Wed, 18 Nov 1992 03:24:17 GMT

In article <1992Nov11.235250.11604@wixer.cactus.org> george@wixer.cactus.org (George Wenzel) writes:
>In article <BxAp6y.4Mr@maxed.amg.com> ed@maxed.amg.com (Ed Whittemore) writes:
>>In article <1dbrn2INN9ch@iskut.ucs.ubc.ca> stlouis@unixg.ubc.ca (Phill St. Louis) writes:
>>>I have read the manual and the 386 FAQ, and my question was not answered, so...
>>>
>>>When adding a second disk to an ISC Sys V Rel. 3.2 machine, in the partitioning,
>>>the screen comes up with a partition for swap.  Does this work for adding
>>>extra swap?  It seems too simple to believe.  I have previously added disks
>>>to a Sun and the documentation for SunOs states very clearly how to do it,
>>>but the ISC docs are lacking in info about this stuff.
>>>
>>
>>It works. When you're done, type `swap -l` and see what you get.
>
>Almost but not quite.  Read the man-page for swap.  Simply creating the
>partition does not add it to the swap space... there is a swap command you
>need to execute, and put in your rc3.d somewhere. 
>
>The command is "swap -a /dev/dsk/1s1 0 123456"... where /dev/dsk/1s1 is the
>device, 0 is the starting block, and 123456 is the length.
>
>If you look in /etc/partitions for the swap areas, you can find the above
>numbers for the device (the first digit is the drive number, than an s,
>then one more digit indicating the partition number).
>
>Be sure to get the length correct... swap won't check, so you could trash
>something.
>
Sorry, I didn't mean to imply you that you don't
need to explicitly add the swap space--you do.

The best place for your swap file to automatically add swap partitions on
boot is in /etc/rc.d, where the file named swap might have a line or
2 like:

swap -a /dev/dsk/1s2 0 22528
swap -a /dev/dsk/c0t2s2 0 49152

-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: tar problems
Organization: The Gator Conferencing System 219-289-3745 
Date: Fri, 20 Nov 1992 10:43:52 GMT

gary@sci34hub.sci.com (Gary Heston) writes:

>I was told today (Thursday) that Dell had been off the internet for
>four days, and had just gotten things back up. Apparently some 
>equipment died, but I don't know what or how much. Things should be
>working now, although the backlog may be pretty big...

Their T1 is back up and and been nntping news with gator now for the last
2 days..


-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
From: pvr@wang.com
Newsgroups: comp.unix.sysv386
Subject: Re: 120Mb tapes on SCO UNIX
Date: 18 Nov 92 14:42:33 GMT
Organization: Wang Labs, Lowell MA, USA

davidsen@sixhub.UUCP (Wm E. Davidsen Jr) writes:

>In article <1992Nov6.232519.5474@mr.med.ge.com> frigo@opustech.com writes:
>| You can write DC600A tapes in a 150 M byte drive, but SCO will
>| only allow you to put 60 M bytes on the tape.

>Could you give a little more detail on taht? In what way does your SCO
>software stop you from writing  more on the tape (other than spacifying
>the tape size to the software you use, if applicable)?

	What frigo@opustech.com said was not quite correct.
The tape driver was not limiting his tape capacity but rather
the /etc/default/tar file had 60 meg as the device limit.
SCO must have shipped 3.2.0 that way.   3.2.1 and 3.2.2 were
shipped with 0 in that field.   This allows unlimited writes
by tar.   This was only a tar issue.

--
>>>>>>>>>>>> Peter Reilley ..... pvr@wiis.wang.com ..... KA1LAT <<<<<<<<<<<<<
                     Well, that about says it.
Newsgroups: comp.unix.sysv386,comp.unix.bsd,comp.windows.x
From: roell@informatik.tu-muenchen.de (Thomas Roell)
Subject: Re: I need 8514/ATI Graphics Ultra support for ISC UNIX SVR3.2 & X11R4
	<PATRY.92Nov16102428@jy.Software.Mitel.COM>
	<1992Nov16.213215.4701@netcom.com>
Organization: Inst. fuer Informatik, Technische Univ. Muenchen, Germany
Date: Mon, 23 Nov 1992 07:38:00 GMT
Distribution: na

>   >We are using the Metrolink X11R4 software with Motif 1.1.3 on ISC 3.0.
>   >They support the ATI ultra very well. For information call
>   >
>   >(305) 970-7353
>   >
>   >They also have X11R5 with Motif 1.1.4 available.
>   >
>   It is trivial to port XBSD8514 to ISC.
>   XBSD8514 is known to work with the ATI Ultra and has been clocked
>   at 60k xstones.

Well, the issue here is that MetroLink (and SGCS) have access to the
full documents about the Mach8/Mach32 chipsets. Since you can get them
only under a NDA, a free X-server would never give you the same power as a
commercial version, which can make use of these details. Furthermore,
you have to use DOS to setup a 1024x768 NI mode. The comercial
products don't require the use of DOS to do that. 

- Thomas

PS: BTW, X386 1.3: 85k xstones on a Ultra ....




--
-------------------------------------------------------------------------------
Das Reh springt hoch, 				e-mail: roell@sgcs.com
das Reh springt weit,				#include <sys/pizza.h>
was soll es tun, es hat ja Zeit ...
From: dsiegel@optima.UUCP (Dave Siegel)
Newsgroups: comp.unix.sysv386
Subject: ATI Ultra Pro and Xmach *pull hair out*
Date: 18 Nov 92 23:23:10 GMT

I've been beating my head over my keyboard for the last two evenings trying
to get the ATI Ultra Pro to work with my Ideki/iyama 5421-a on Dell 2.2.

has anybody else been able to get it to work? I think the problem is
that the ati keyword defaults to the clock timings for the Vantage?  for some
reason, the "clocks" keyword doesn't get recognized to over-ride these, and
I don't have any idea how to define a new chipset type.  Is there any hope?

-dave

--
Dave Siegel              dsiegel@cs.arizona.edu    dsiegel@biosci.arizona.edu
SysMgr, Biotec, U of Az  dsiegel@hacks.arizona.edu dsiegel@seagull.tucson.az.us
"The opinions expressed herein are not necessarily those of my employer,
not necessarily mine, and probably not necessary."
From: davidsen@yeti.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: Re: Using 16550AFN with SCO 3.2.4
Date: 23 Nov 92 16:57:23 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <VU48FYS@geminix.in-berlin.de>, gemini@geminix.in-berlin.de (Uwe Doering) writes:
| davidsen@ariel.crd.GE.COM (william E Davidsen) writes:
| 
| >The one thing about the SCO driver is that
| >it seems to support more types of serial device than FAS, although you
| >have source with FAS.
| 
| I can't really believe that SCO's driver supports more serial device
| types. While it is true that FAS comes with config files for only
| a few serial cards, FAS' support is in no way limited to these cards.

  I didn't realize that FAS worked with smart cards. I certainly will go
back and look at the source again, but I had the impression that the
documentation even said FAS was for dumb cards. Of course SCO supports a
number of smart cards.


| >  Sure wish FAS run with Linux.
| 
| Well, that's another story. While Linux tries hard to be compatible
| with UNIX, I suspect that the driver interface in the kernel is not
| very similar to the SysV interface. So a port to Linux would be
| a major effort. I wish someone would prove to me that I'm wrong,
| but I have the distinct feeling I'm not.

  The interface is totally different, and only some of the ideas have
made it from FAS to the Linux drivers. Not that the drivers are all that
bad, but the minor device stuff really mkes FAS worth using. I would
bother with it for the difference in the speed of the current drivers
from SCO, although the old ones were pretty grim.


| If someone else wants to port FAS to Linux, do it. However, if
| there are more than a few changes necessary, I won't include
| them into FAS because I can't test them myself. The Linux port
| would have to become an independent product with a different
| name (the same story as with SASS for SysVr4).

  And an independent set of bugs...
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
Newsgroups: comp.unix.sysv386
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: Names no longer being seen (gethostbyname stops) with ISC 2.2.1
Organization: The Gator Conferencing System 219-289-3745 
Date: Mon, 16 Nov 1992 17:38:05 GMT

sam@csi.compuserve.com (Sam Neely) writes:

>Now that I've got that off my chest...  My guess is that you changed
>your nameserver information when you updated sendmail.  Check out
>what you've got in /etc/resolv.conf.  If that looks kosher, make
>sure you've got a route to the nameserver(s) with netstat -nr.

I'm using uunet for my nameserver as defined in /etc/resolv.conf --
how long before entries to uunet's namesever are shared around the
world with the various other nameservers?

-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
From: dan@dribble.c-mols.siu.edu (Dan Ellison)
Newsgroups: comp.unix.sysv386
Subject: Re: Need compiled POPPER daemon for SCO 386
Keywords: POP
Date: 19 Nov 92 13:10:54 GMT
Distribution: usa
Organization: Southern Illinois University - Carbondale, IL (SIU-C)

In <1992Nov18.195400.19357@nstn.ns.ca> rballard@fox.nstn.ns.ca (Rick Ballard) writes:

>I have tried compiling POPPER, the pop mail daemon, on a local SCO 386 box.
>Due to a plethora of missing libraries, the link always fails. I can't even
>find the crypt function. Does anyone have a compiled POP demon I could FTP?
>The machine I need to put it on does not have the development system.
>Thanks.
> 

The precompiled popper deamon is available on ftp.c-mols.siu.edu in 
the sco-ports/binaries directory.  The patched source is also available
in sco-ports/pop3.  If you grab the source you may need my libbsd
stuff as well.  It can be found in sco-ports as well.  The only client
I have had any problems with is the QVTnet popmail send client.  THis
particular client seems to hang the daemon for some unknown reason.
Otherwise, it works flawlessly for us.  Help yourselves and enjoy.

BTW, there is also a pop2 server available on this same machine if
anyone needs that.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Dan Ellison, Network Spec 	  -    	Computing Affairs, SIU-C 	| 
| Southern Illinois University 	  - 	Carbondale, IL 62901            |   
| FAX:      (618) 453-3459        -   	PHONE:    (618) 453-6149 	|     
Newsgroups: comp.unix.sysv386
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: Esix/Motif Question
Organization: The Gator Conferencing System 219-289-3745 
Date: Tue, 17 Nov 1992 20:13:04 GMT

duncan@cnw01.storesys.coles.oz.au (Duncan Goode) writes:

>Esix's stand on the position is unknown - I have faxed them a report
>on the problem twice with no responce, and have mailed it once. (I

Last I heard, a good portion of ESIX's technical support
team quit..

I have no idea if they have been replaced as of yet..


-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
From: bam@jutland.ColumbiaSC.NCR.COM (Bo Muldbak)
Subject: Re: tar problems
Reply-To: Bo.Muldbak@ColumbiaSC.NCR.COM
Organization: NCR Corporation, MCPD Columbia SC.
Date: Tue, 17 Nov 92 17:52:59 GMT

In article <1992Nov12.164004.9850@netnews.whoi.edu>, gie@charon.er.usgs.gov
(Gerald I. Evenden) writes:
|> I am having problems with tar files created under Dell SVR4-i2.2 not
|> un-tar-ing properly on other systems.  More specifically, directories

With those "other" systems, you must mean BSD like systems.
The problem with BSD like systems are, that they do not use the "type" field
in the tar headers. A directory is type "5", but this is ignored by BSD.
They look for only the '/' suffix. The tar command on SVR4 has had a LOT
of changes put into it to make it read all kind of weird archives from Xenix,
BSD, multi-floppy archives. All issues resolved by teaching SVR4 to
understand
the whole world. This last issue I think should be resolved by BSD tar.
A BSD tar archive has filetype '0' (impossible) for all files/directories.

	tar compatibilies:

	AIX	-> 	BSD	OK, Since a AIX tar has only files, no 
				directories. (No problem of no '/' suffix)

	BSD	->	AIX	OK, AIX understands that '/' suffix really
				means filetype '5'.
	
	SVR4	->	BSD	Problem, since SVR4 archives has directories
				and are not using the silly '/' suffix.
				Instead we are using the tar filetype field.

	BSD	->	SVR4	OK, since SVR4 tar has been fixed to take
				special care of BSD archives. Like above
				for AIX.


	Regards
		Bo Muldbak


-- 
//// Bo Asbjorn Muldbak             // Email:  Bo.Muldbak@ColumbiaSC.NCR.COM
/
/// Support & Deployment           // Phone :  +1 (803) 791-6871           
//
// NCR Corporation, MCPD-Columbia // Telefax:  +1 (803) 739-7371          
///
/ Opinions stated are my own. They do not represent my employer or others
////
Newsgroups: comp.unix.sysv386
From: iscoper8@nuscc.nus.sg (Ms Koh Geck Cheng Jocelyn)
Subject: NIS in AT&T SYSV Rel 4.0
Organization: National University of Singapore
X-Newsreader: Tin 1.1 PL4
Date: Wed, 18 Nov 1992 09:51:12 GMT


Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
From: seiferth@rufous.cs.unm.edu (Justin Seiferth)
Subject: C++ Compiler, debugger really, under SVR4
Organization: Computer Science Department, University of New Mexico
Date: Tue, 24 Nov 1992 01:14:08 GMT


We purchased Liant's C++ compiler only to find it supports a proprietary
debugging protocol and they have no plans to support templates. So...

Any recommendations on where else we should look?  I really would like to
stick with g++ but have been unable to get either mxgdb or xxgdb to 
run/compile under SVR4.  So if anyone has recommendation on where we should
go for a good C++ compiler/debugger combo or has been able to get mxgdb 
or xxgdb running under SVR4, I'm all ears!

Thanks..
Justin
From: jef@diva.Berkeley.EDU (Jay Fleischman)
Newsgroups: comp.unix.sysv386
Subject: ESIX 4.0.4 in-line assembly in c
Date: 20 Nov 1992 18:29:06 GMT
Organization: University of California, Berkeley
NNTP-Posting-Host: diva.berkeley.edu
Summary: What is the syntax?  How do you do it?

Hi unix people!

I would like to do some in-line assembly in a small portion of my C - code
program.  I would also like information about the syntax etc. of 
assembly routines and linking them with c programs.

I've asked tech support at ESIX, and they say they know nothing about
it, and don't know in which manual I could look (actually, they said
it's not there, and they have no reference either)

PLEASE, anyone who has done this, could you tell me?  If there is a
good reference that you might recommend, what is it?  I had hoped to be
able to use the symbolic variable names etc. in the assembly.  Perhaps
one of those excellent X386/XFree people have done some of this?  I
understand that there were some binary routines written to improve the
speed...

Please email your response to jef@swordfish.berkeley.edu  or post.

Thanks alot.
Jay Fleischman

Newsgroups: comp.unix.sysv386,biz.sco.opendesktop,biz.sco.general
From: adh@cbnews.cb.att.com (andrew.d.hay)
Subject: Re: Bug with ScoSession connecting to XTerm with >16 colors
Organization: AT&T
Distribution: na
Date: Tue, 17 Nov 1992 15:34:13 GMT

In article <BxL0DA.IFw@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:
[]
"       Now, if you had a compiler that behaved like this, exactly how
"do you go about feeding something to just the "preprocessor", and
"arranging to get your output before it makes it to the "code parser"?

simple -- link cc to cpp and have it examine argv[0] to determine its
behavior.

-- 
		+--------------------------------------------------------------+
Andrew Hay	|	I am not an expert,				       |
a_d_hay@att.com	|			 but I play one on the Internet!       |
		+--------------------------------------------------------------+
Newsgroups: comp.unix.sysv386
From: curtis@NeoSoft.com (Curtis Keller)
Subject: generating shared libraries on SCO Open Desktop
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Wed, 18 Nov 1992 22:10:11 GMT
Keywords: shared libraries SCO


Could someone detail the procedure of producing shared libraries
under SCO Open Desktop - or point me to the appropriate documentation.
I was told that several pitfalls exist - but the "teller" could not
provide me with the actual problems.   
 
I'll be glad to post a summary of the steps required and workarounds
to use.  Thanks.
-- 
Curtis Keller
713-953-8309
curtis@neosoft.com
From: darcy@druid.uucp (D'Arcy J.M. Cain)
Subject: Writing to disk destroys data
Date: Fri, 20 Nov 1992 01:55:56 GMT
Organization: D'Arcy Cain Consulting

I have problem with my floppies.  I am using an Adaptec 1542B controller
on a 486 with two floppies.  The hard disk access is fine and there is
no problem with the floppies under DOS but under Unix (Esix SVR4.0.4) I
can't write to a disk without destroying the data on it.  Even mounting
a file system (I have to create it on another box) ruins the disk as it
writes to the super block.  If I mcopy a file to a DOS disk with a label
of "ABCDEFG" the label becomes "A C E G" and the rest of the disk is
similarly destroyed.

I have the hardware dealer checking this out but since it works under
DOS they are trying to blame the OS.  Of course Esix handles the 1542B
fine on other installations so they blame the hardware.  Has anyone seen
anything like this and can you suggest where the problem lies.  Thanks.

-- 
D'Arcy J.M. Cain (darcy@druid.com)  |
D'Arcy Cain Consulting              |   There's no government
Toronto, Ontario, Canada            |   like no government!
+1 416 424 2871          DoD#0082   |
Newsgroups: comp.unix.sysv386
From: ignatz@chinet.chi.il.us (Dave Ihnat)
Subject: Re: 386 Unix - is 5,000 logins realistic?
Summary: Well, disk access should be better...
Organization: Chinet - Public Access UNIX
Date: Fri, 20 Nov 1992 00:23:00 GMT

In article <1992Nov18.221254.13744@openage.openage.com> gryphon@openage.openage.com (The Golden Gryphon) writes:
>todd@toolz.uucp (Todd Merriman) writes:
>
>
>>Is it realistic to support about 5,000 logins with a 386 Unix?
>
>Passwd search times will make logging in slow.  5000 users in 1 group may make
>/etc/group unuseable, because they all have to be on one line.  You may be able
>to fix that with "\"'s at the end of every x number of users.
>
Frankly, unless I have an overwhelming reason to put everyone in the same
group, I give every login its own group.  This aids security, while I can allow
group access via 'newgrp' or other such ploys.

I would suggest that you order both your group and passwd files by use; that
way, the most frequent users get the fastest login.

>You will also have directory search problems if all their home directories
>reside in the same place.  You can changes this and keep different parent
>directories based on their names or something.  It will probably be best to
>subdivide them further.

Possibly; although on BSD, Sun, or SVR4 systems the hashed directory structure
will mitigate this problem greatly.

Cheers,

		Dave Ihnat
		ignatz@homebru.chi.il.us (preferred return address)
		ignatz@chinet.chi.il.us
Xref: sparky comp.unix.sysv386:16749 comp.unix.bsd:9247