HDTenEightyP/NetNews huggingface dataset:
From: lr@cs.brown.edu (Luigi Rizzo)
Subject: mountd/portmap/NFS problem
Reply-To: luigi@iet.unipi.it
Organization: Brown University Department of Computer Science
Date: Thu, 5 Nov 1992 17:53:51 GMT


It must be something trivial but... I installed 386bsd 0.1 on a
486-33 with IDE drive, we8013-clone ethernet with no problems.
Everything including the network seems to work (at least, ftp, telnet,
rsh  work fine and quickly in both directions). However, when I try to
boot with the nfs-related stuff enabled (portmap, mountd etc.) mountd
hangs without being able to register with portmap. If I press ^C on the
console during boot, things proceed more or less regul;arly and the
system comes up (the only thing is, mountd takes most of CPU time).
Other things (nfsd, nfsiod) apparently register correctly (as shown by
using rpcinfo from another machine).  Now, I cannot either NFS-mount
the 386 disk from another machine (clearly because mountd does not
work, the error message is

nfs_mount: bsd386a:/ server not responding: rpc program not registered

or mount other disks on the 386bsd machine. (this time the error
message is 

Bad MNT RPC: RPC: Authentication error; why = Invalid client credential


I haven't installed the crypt routines or any of the patches yet,
because from the descriptions I have it's not clear which ones
apply to my problem. Any help from the net ?

	Thanks
	Luigi
==================================================================
Luigi Rizzo                Brown University & Univ. di Pisa
e-mail: lr@cs.brown.edu, luigi@iet.unipi.it
==================================================================
Newsgroups: comp.unix.bsd,comp.os.minix,comp.os.linux
From: n217cg@tamuts.tamu.edu (Scott Taylor)
Subject: Re: Floppy overrun/underrun messages...what does it mean?
Followup-To: comp.os.linux
Summary: me, too
Keywords: floppies, SCSI
Organization: Texas A&M University
Date: Thu, 12 Nov 1992 22:09:05 GMT

In article <1992Nov12.004814.22770@news.nd.edu> bselling@darwin.helios.nd.edu (brian selling) writes:
>
>I recently switched from an ESDI setup to a SCSI setup.  On reinstalling
>linux from SLS ver 0.98pl1 i got numerous floppy overrun/underrun errors...
>retrying, etc.  This happened both when I was mkefs -c -ing the drive, and
>on the install from floppies.  I don't remember this happening when I installed
>on the ESDI drive.  My new controller is a Ultrastore 14F.  But everything
>seems to work in the end.  I have X and all up and running, so I guess the
>retries worked, but anyone know why I might have gotten these errors or whether
>its serious or not?
>

I have a 14F and had the same problem with 0.98, so I cheated and commented
out the printk() in floppy.c that displayed the message.  It only happened on
my 1.44 MB floppy, and everything seemed to work despite the messages, so I
lost 'em.  It seems to be cleared up in 0.98 pl4.

I kind of wonder if it's a problem with the 14F or a kernel problem; I didn't
get the error under previous versions.

>--
>Teresa Selling
>South Bend, IN

Scott Taylor
n217cg@tamuts.tamu.edu
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: bonnie i/o test results
Organization: Nanyang Technological University - Singapore
X-Newsreader: TIN [version 1.1 PL6]
Date: Fri, 6 Nov 1992 14:47:49 GMT

Julian 486/50 16M RAM, bustek SCSI-2 disk,

              -------Sequential Output-------- ---Sequential Input-- --Random--
              -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU  /sec %CPU
           32   405 48.2   389  8.4   152  5.6   505 53.1   461 10.3  20.0  5.0

My machine 386/25 8M RAM , IDE Maxtor 200M disk,

              -------Sequential Output-------- ---Sequential Input-- --Random--
              -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU  /sec %CPU
           16   121 99.2   350 15.6   190 17.7   108 99.8   454 16.4  25.9  8.9

Just look at the Random seek figure, the smaller IDE is faster despite having
more CPU load.

Once I get to a 486/33, then you'll see comparable or even better performance
for IDE SCSI.
	Some people posts to have the bigger file sizes but it is not to
my liking because it is not realistic to my use.
	My prefered size is 500Kbyte, how large is xterm?

If you like to see how fast your disk it, you can use bonnie to find out.
What is important is your usual application.
	Bonnie does not represent your normal C program because it now
does not use the default BUFSIZE, and there are attempts to minimise 
the ability for a compiler to optimize its code.
	bonnie is now more meant for people who use the same bufzie as bonnie,
i do not know what size it is,(trying to find out, any volunteer?),
and know how to code efficiently without relying on compilers to optimize its
code. I'm not one of those people. I do not have time for that.
--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet

Newsgroups: comp.unix.bsd
From: tdphette@mke.ab.com (Thad Phetteplace x4461)
Subject: Re: XView - how much of it is available?
Organization: Allen-Bradley Co.
X-Newsreader: Tin 1.1 PL4
Date: Wed, 11 Nov 1992 15:25:27 GMT

kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:
: 
: I saw some mentioning of Xview lately.
: 
:    o how much has been ported?
: 
:    o Where is the site carrying the port?
: 
:    o Is the olwm Window Manager available? 
: 
: --
: --Chris
: Christoph P. U. Kukulies
: kuku@acds.physik.rwth-aachen.de
: *** Error code 1
:  
: Stop.
: 

I managed to port the props program (executed by the Properties menu
selection) a few weeks ago.  I'm currently working on the termsw bug
(suggestions welcome).  I'll put the modified props source code and
executable on my ftp server tinman.mke.ab.com sometime tommorow.  It
will be in the /pub/386bsd/ports directory.  I will put my ported
version of pcomm in there as well.  I will make an attempt at
compiling xlock tonight and if that works I will finish porting
Xlockup.

--
Thad Phetteplace
Network Systems Analyst, Allen-Bradley Co.
Phone: (414)382-4461
Email: tdphette@mke.ab.com

The opinions expressed here are entirely my own and not that of my employer.
I am not a slob, I am simply doing an experiment in domestic entropy!

Newsgroups: comp.unix.bsd
From: peter@ferranti.com (peter da silva)
Subject: Re: 386BSD or LINUX?
Organization: Xenix Support, FICC
Date: Mon, 9 Nov 1992 22:09:19 GMT

In article <1dkhffINNj4t@escargot.xx.rmit.OZ.AU> s902113@minyos.xx.rmit.oz.au (Luke Mewburn) writes:
> Enuf ranting, my question is: does linux have kconfig (will 386BSD
> get it)?

That's a System V thing. The BSD and System V system config stuff is radically
different. I personally like the SV stuff myself.
-- 
% Peter da Silva % 77487-5012 % +1 713 274 5180 %
true(<<VV$@\\$'&O 9$O%'$LT$&$"V6"$&$<4$?'&$ #I&&?$=$<<@)24 24 scale 3 21 moveto
{dup 36 eq{pop not}{dup 7 and 4 sub exch 56 and 8 div 4 sub 2 index{rlineto}{
rmoveto}ifelse}ifelse}forall stroke pop showpage % Har du kramat din varg idag?
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: why erase/kill echoed by [c]sh in xterm? [386BSD/X386]
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Sat, 7 Nov 1992 11:19:35 GMT

The new X386 is wonderful!  And it is with much trepidation I ask the
world: why does the erase char print under the 386BSD shell, rather than go
backwards one char (it does delete a char backwards, it just doesn't
move the cursor backwards)?  I tried the -tn -tm and -cu options to xterm, but
I can't seem to get a destructive backspace (or kill).  Here's the output
of stty -a:

speed 9600 baud; 24 rows; 80 columns;
lflags: icanon isig iexten echo -echoe -echok -echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -mdmbuf -flusho -pendin
-nokerninfo -extproc
iflags: istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk
brkint -inpck -ignpar -parmrk
oflags: opost onlcr -oxtabs
cflags: cread cs7 parenb -parodd hupcl -clocal -cstopb crtscts
cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = <undef>;
eol2 = <undef>; erase = ^H; intr = ^C; kill = ^U; lnext = ^V;
quit = ^\; reprint = ^R; start = ^Q; status = <undef>; stop = ^S;
susp = ^Z; werase = ^W;

Doubtless the answer is silly, but eludes me.  BTW, erase works fine in
vi or if I call a remote system via tip.  I am running X from the
console via xinit (that OK?) and 386BSD pl58+.  Thanks.
-Andrew Moore <alm@netcom.com>

Newsgroups: comp.unix.bsd
From: dfishman@teal.csn.org (Dan Fishman)
Subject: Re: remote lpr/lpd problems...
Organization: Colorado SuperNet, Inc.
X-Newsreader: Tin 1.1 PL4
Date: Fri, 13 Nov 1992 14:36:10 GMT

sastdr@torpid.unx.sas.com (Thomas David Rivers) writes:
: 
: I'm having an interesting problem with the lpd on 386bsd.
: 
: Namely, if I (from a remote lpr) print a small file, things work
: fine.  However, if I remotely print a large file the lpd on 386bsd
: "looses the connection."
: 
: Looking at the lpd sources, I see such a message emitted if a read
: from the incoming socket returns <= 0; which is reasonable. (i.e. it
: either got EOF sooner than expected or there was a problem.)
: 
: The number of bytes read before this happens is *always* 5120; which is
: a rather suspicious number.
: 
: So, I was wondering if there is a limit somewhere I'm running into.  I
: couldn't find anything, but thought I would post and ask..
: 
: 
: 	- Thanks -
: 	- Dave Rivers -
: 	(rivers@ponds.uucp (home))
: 	(sastdr@unx.sas.com (work))
: 
: 
: -- 
: UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express

I'm not currently a 386BSD user but this could be a basic datacomm issue
such as I have seen in a BSD4.2 port.  If the printer is serial attached
(RS232) then it may be doing BOTH a XON/XOFF flow control handshake and
an DTR HI/LOW flow control handshake.  DTR is the norm for DOS, XON/XOFF
is the norm for most UNIX.   The DTR handshake however may appear to the
UNIX serial line driver as a lost line (lost modem control).  

If this is the issue, many (I don't know about 386BSD) drivers have a control 
(ioctl) to enable/disable modem control protocols (or possibly even use DTR as
a standard handshake).  Another solution is to modify a cable so as to
preclude the DTR handshake from reaching the CPU side of the cable as any
modem control signal.  This would mean tying required modem control signals
high or low as required for your serial IF/driver.

OR NOT!  It could be a more subtle networking problem since you specifically
mentioned remote printing?  Hope this helps.

Dan  Fishman (dfishman@csn.com)
Xref: sparky comp.unix.bsd:8565 comp.benchmarks:1622 comp.arch:10504 comp.arch.storage:750
From: klimmek@hummel.mw.uni-kl.de (Axel Klimmek)
Subject:  Help:  ftp does not work for installation
Organization: University of Kaiserslautern, Germany
Date: Mon, 9 Nov 1992 09:33:06 GMT

I have the Tiny BSD on my  harddisk and want to download the distribution files
by ftp.
The system can find my Ne2000 card. I can type

ifconfig ne0 <my adress> netmask <my netmask>
route add default <my gateway>

without any error. Then I type 

ftp <distribution host>

and after a few minutes I got the error: 

connect: Connetion time out.

My system is a 486/50MHZ . 
Any ideas to fix the problem?

Thanks

Axel Klimmek


Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: [386bsd] Install?
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: na
Date: Tue, 10 Nov 1992 04:07:22 GMT

In article <1992Nov10.031011.18762@netcom.com> glenc@netcom.com (Glen Collins) writes:
>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

I am just guessing, but if you have an MFM disk and RLL controller
which squeezes 50% more  the capacity into  the disk, you might try a
manual install and be careful to specify the number of sectors/track as
seen by the RLL (e.g., 26 instead of 17).  I have heard rumorred (by
someone whom I made a fool of myself quoting in the past...) that some
MFM disks are not fast enough to be RLL'ed.  Anyhow, you might consider
this a potential source of problems if neither Linux nor 386BSD
installs...
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: jbkang@csking.kaist.ac.kr (Joongbin Kang)
Subject: 386bsd: cc goes insane?
Organization: KAIST in Seoul, Korea
X-Newsreader: Tin 1.1 PL3
Date: Fri, 13 Nov 92 21:06:08 GMT


I have successfully installed 386bsd on my machine which has
      4MB memory, 200MB ESDI hard, no 80387, and so on.
When I finished installing XFree86, I was quite impressed!
But...when I tried to install 'hanterm' (modified xterm for Korean),
the compilation goes over 30 minutes and then the system hangs!
  With shorter files (less than 500 lines), cc succeeds to produce
object codes, but when it comes larger files, the system dies.
What shall I do? Is it because of small memory or slow CPU?  :O

Posting or E-mail, any help would be appriciated.

		Joongbin Kang
		CS dept., Korea Advanced Institute of Science & Technology

		e-mail: jbkang@adam.kaist.ac.kr
Newsgroups: comp.unix.bsd
From: a590700@hp9000.csc.cuhk.hk (USS Account Creation account)
Subject: Re: HELP! GCC CHOKING ON COMPILES!
Organization: The Chinese University of Hong Kong
Date: Sat, 7 Nov 1992 04:21:43 GMT

In article <14858.9211051457@thor.cf.ac.uk> spedpr@thor.cf.ac.uk (Paul Richards) writes:
>In article <1992Nov4.043335.18409@news.ysu.edu> ae007@yfn.ysu.edu (Daniel Newcombe) writes:
>|
>|I was trying to compile the DKB Ray Tracing program that I
>|got from wuarchive.wustl.edu /graphics/graphics/ray/dbktrace.
>|I copied the unix.mak and unix.conf to Makefile and config.h
>|and typed make.  Much to my surprise, I didn't get errors 
>|saying that all the C stuff was incompatiable.  Instead I
>|went to watch Star Trek and came back an hour later...and it
>|was still trying to compile.  It had only done 4 files!!!
>|I wanted to see how long it had been running so I suspened
>|the job and typed ps.  The system stopped.  I had this problem
>|earlier with another program I was compiling.  Has anyone
>|else had problems like this.  It really sucks that I can't
>|develop anything new on the system :(
>
>Yes. I've had problems like this. I think it just runs out of memory,
>how much have you got. When I try to compile xview apps the system is
>unusable because of continuous disk access so the cpu spends all its
>time servicing interrupts (I think). If you then run out of memory as
>well and it starts swapping you're in big trouble.
>
>My 8Mb 33Mhz 486, with 200Mb maxtor IDE drive just isn't up to compiling
>xview apps, which have huge include files. Instead I use Julian's
>machine which doesn't suffer from these problems, partly because it has
>more memory but mainly I think because disk access doesn't kill
>performance.
>

How large is your swap partition?  A small swap partition may limit your
main memory usage!

Just my 2 cents.

Stephen Wong.
(a590700@hp9000.csc.cuhk.hk)
Newsgroups: comp.unix.bsd
From: nate@nate.oscs.montana.edu (Nate Williams)
Subject: Feedback on patches in Terry Lambert's patchkit
Summary: problems?
Keywords: n
Organization: None
Date: Sun, 8 Nov 1992 22:51:18 GMT

I am in the process of adding some patches to Terry's patchkit, and I
was wondering if those of you who have installed the patches could
give me some feedback on the patches that are already there.

I already know about the patch00019 problems with the extra return, but
are there any other problems that I need to know about?  

Right now my plan is to move all the 'necessary' patches to the front of
the list, and patches such as making all the games compile, and
hardware dependent patches will be moved to later numbers ( > 500) so
when you do a IALL, you get all the necessary ones, and then the later
patches will be installed until you have a problems, such as not having
installed the games, etc....

Any other hints or suggestions are greatly welcomed, so please email 
your reponse this week.  I hope to bring a portable to ComDex(sp?) and
work on this, as I should have some free time in the evenings when I
should be doing homework and such.


Thanks,

Nate

ps. Hopefully in the next couple weeks I can get a new version of the 
Bug Report out with the appropriate patches in Terry's patchkit format.
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home. 
work: (406) 994-5991         |  Keeper of the Unofficial 386BSD Bug Report
home: (406) 586-0579         |  Please send bugs and/or fixes you find.
Newsgroups: comp.unix.bsd
From: vikki@e40-008-11.MIT.EDU (Vikki King)
Subject: Re: XFree86 problems (keyboard hangs overnight)
Organization: Massachvsetts Institvte of Technology
X-Newsreader: Tin 1.1 PL4
Date: Fri, 13 Nov 1992 06:34:45 GMT

  I've noticed a similar problem to the one described below, except that
it happens to me in a matter of minutes after starting to use X.  The
mouse is still alive and I can telnet to the host ok.  If I can kill
the server remotely and start again, I'm ok for another little while.
I don't think that this happens though if I'm not running twm (like,
no window manager at all).  I am using the bus mouse driver that was
ported by a kind person from BSD386.  I have a mylex 386/33Mhz board,
16MB RAM, Paradise 265K VGA board, AHA1542B, and I'm running X386mono.
I also have a 387/33.  Anyone else had similar troubles?

-John
jackson@a1.mec.mass.edu

sastdr@torpid.unx.sas.com (Thomas David Rivers) writes:
: 
:   I'm running into a strange problem with XFree86 & xdm, 
:  and a little time.
: 
:   Every morning, I come to my machine and try to log in on the xdm
: login screen, but the keyboard is locked, the mouse works fine.
: I have to telnet/rlogin from another machine and kill the X server.  
: When the X server restarts, the keyboard returns.
: 
:   I have discovered that if I don't log out - and leave my session
: there - when I return in the morning the keyboard is locked again,
: so pressing a key doesn't get my screen back (i.e. it's been blanked.)
: *But* - moving the mouse will... In fact, all the mouse stuff works
: fine.  
: 
:   My current work-around is to not log out overnight, then in the 
: morning, use my mouse to pull down the twm menu and exit twm.  This
: ends my session (logs me off) and the X server dies;  xdm starts up
: a new server which is fine.
: 
:   Also, I've noticed some problems with the capslock key; sometimes
: the capslock is engaged, and I can't disengage it without restarting
: the server.   In this regard, none of the keyboard lights (capslock, numlock,
: etc...) seem to function.
: 
:   Finally, did anyone ever find out where the <bell> went?
: 
: 	- Dave Rivers -
: 	(rivers@ponds.uucp (home))
: 	(sastdr@unx.sas.com (work))
: -- 
: UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express
Newsgroups: comp.unix.bsd
From: jkh@esel.lotus.com (Jordan K Hubbard)
Subject: [386BSD] capslock -> control key mapping
Organization: Lotus Ireland
Distribution: comp
Date: Tue, 10 Nov 1992 13:26:05 GMT

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
Newsgroups: comp.unix.solaris,comp.unix.bsd
From: pirzyk@cs.uiuc.edu (Jim Pirzyk)
Subject: Re: Solaris 1.1 vs. Solaris 2.0 (BSD vs AT&T)
Organization: University of Illinois at Urbana-Champaign
Date: Thu, 12 Nov 1992 15:04:08 GMT

In <kzin.721442926@cc.gatech.edu> kzin@terminus.gatech.edu (John Rudd) writes:

>     I'm getting ready to buy a workstation..and I'm basically looking
>at a used SS2, a new IPX, or a new SparcClassic.  The advantage of the
>first two, is that they run SunOS 4... unfortunately, the Classic only
>runs Solaris 2.  The reason I feel this is unfortunate, is that I very
>much prefer the BSD programming model.  However, I've been told that
>Solaris 2 will be 100% source code compatable to the older versions.  Is
>this true?  and to what extent is it true? I mean.. if I have a program
>that uses bsd kernel calls (ioctl and fcntl type things), will it compile
>under Solaris 2.0? or will I have to re-write it around the AT&T type
>programming model?

If the program accesses the kernel (not just by system calls) or if the 
program access some of the system files that have changed (like /etc/fstab =>
/etc/vfstab), it will have to be ported.  No one can say for sure without
more information on the programs.

>Does Solaris have BSD Sockets of both the Unix and Internet types?
>I imagine since it's AT&T it will have shared memory.

They are built upon the AT&T STREAMS package.

>Does it have the "dump" utility?  if not, what backup type utility
>does it have in its place?  Are the utilities mostly AT&T, or does
>it preserve the BSD like utilities of SunOS?  if not, can I get
>copies of those BSD utilites that will run on Solaris 2.0? (ie. if
>I want a version of ps that has bsd options instead of at&t options,
>can I get one that will run on solaris 2.0?) (this might be an
>interesting market place for BSDI...)

it has dump, but it is called /usr/lib/fs/ufs/ufsdump (it took me 2 weeks to
find it).

>(also, in that last question, can I get a copy of dump that runs on
>solaris 2.0?)

>Last but not least.. someone please ask sun why they have done this
>henous act to us :-)

In the name of "progress".

>Sorry if some parts are dumb questions.. I'm just trying to get
>unambiguous, detailed answers to those things I don't want to
>have to speculate about.

They are not dumb questions but show that you are not following blindly Sun's
lead.

- Jim
-- 
[Jim] pirzyk@uiuc.edu -------------------------------------------------
TAC System Administrator, USArmy Construction Engineering Research Labs
/* Hello, we're the government and we're here to help you. :) */
Xref: sparky comp.unix.solaris:293 comp.unix.bsd:8742