HDTenEightyP/NetNews huggingface dataset:
From: david@mlb.geomechanics.csiro.au (David Le Blanc)
Subject: Re: [386bsd]
Organization: CSIRO DIT (Melb.)
Date:  2 Sep 92 04:45:35 GMT

Tao Jiang <tj2n+@andrew.cmu.edu> writes:

>Hi, anyone has idear about what the functions "doscan, doprnt and
>svc_fdset, svc_getreq" are?  Do the semilar functions exist in
>the c libary?

I was porting the XVIEW toolkit, since that is what I use on the sun's here
and I came up with the same problems.

Except that doscan and doprnt were '_doscan' and '_doprnt'.

You will find the svc_* functions in the rpc library. Add -lrpc to the
link line of the utilities you are linking.

Any ideas on _doscan and _doprnt?

PS, when I fudged up some replacements (which were easy enough) the 
xview tools crashed with a segmentation fault anyhow. (Nothing to do with
_doprnt and _doscan)

Has anyone compiled xview?

>Thanks in advance!
--
David Le Blanc                         :
Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
P.O. Box 54 Mt Waverley 3149	       : in Alien^3.
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: gas manual (as.1) empty in source distribution (386BSD) ?
Date:  1 Sep 92 11:22:02 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung
Keywords: 386BSD gas

In <1992Sep1.064725.2551@autelca.ascom.ch> nbladt@autelca.ascom.ch (Norbert Bladt) writes:

>Hi 386BSD-users, bug-fixers, etc. !

>I have access to a distribution host via NFS. On this host there
>is the full distribution (bindist, srcdist, etcdist, etc.) and another
>tree with the sources unpacked. Now, I copied all the sources to my local
>harddisk because it's faster due to the slow link used by NFS.
>However, the file gas/as.1 is empty !
>I checked the srcdist on this server by the famous
>cat src??.?? | uncompress | cpio -itv usr/src/usr.bin/gas/as.1
>commandline and the result was:
>100444 root        0  Mar  3 09:28:09 1991  usr/src/usr.bin/gas/as.1
>meaning that this file is really empty in the srcdist set of files.

That is unfortunately true: The file is empty.
But when looking into the tar archive of GNU gas, I didn't find a 
man page either. So there is none. There is however a texinfo file for 
inclusion into GNU EMACS help.
The empty file, however must be there, to make the 'make' lucky.

>Did anybody else discover this problem or is it just this server ?

>I would like to get a complete distribution, so, if somebody can mail
>this file to me, I will be happy.

The info file is called gas-doc.tar.Z and should be available from anywhere
you can get GNU sources.

>Thank you in advance,

>Norbert.
>-- 
>Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
>Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
>Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: alexk@otc.otca.oz.au (Alex Kowalenko)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] Installing X386
Keywords: 386bsd, X386, installation
Date: 3 Sep 92 03:30:33 GMT
Organization: R&D, OTC Sydney, Australia

I've got a missing /dev/vga too!

-- 

    Alex Kowalenko                 ACSnet: alexk@otc.otca.oz
    R&D Contractor                   UUCP: {uunet,mcvax}!otc.otca.oz!alexk
    |||| OTC ||                       Fax: +6 2 287 3299
                                    Phone: +6 2 287 3131
                                    Snail: GPO Box 7000, Sydney 2001, Australia
From: cappucci@crs.cl.msu.edu (horny Italian bastard)
Newsgroups: comp.unix.bsd
Subject: 386BSD on DISK?
Keywords: bsd 386bsd stuff
Date: 31 Aug 92 01:58:29 GMT
Organization: Michigan State University

If I ever do get a 386/486, which is way off, where can I get the dist.
disks from? I don't mean anonymous ftp, I mean in the mail. And not the
Tiny386BSD either, the whole shot. How much would it cost? Thanks...
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] namelist hassles
Date: 2 Sep 92 10:00:19
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu
In-reply-to: ccml@hippo.ru.ac.za's message of Wed, 2 Sep 1992 09:48:11 GMT

In article <1992Sep2.094811.17592@hippo.ru.ac.za> ccml@hippo.ru.ac.za (Mike Lawrie) writes:

>Several programs on 386bsd-0.1 produce namelist error messages - what
>does one do to fix this? I've done a pretty vanilla install of
>{bin,src,etc}dist on a 560 Mb SCSI, 8 Mb RAM 386, and am far from being
>a bsd expert.
>
>For example:
>
>netstat (the one referred to in the FAQ) produces "filehead or nfiles
>not in namelist"
>
>netstat -r produces "rthashsize: symbol not in namelist"
>
>ps -aux produces "ps: nlist: can't find the following symbols: _fscale
>_avail_start _avail_end:

The kernel that comes with the distribution is stripped so you can't
get any of the names from it.  You need to compile a new kernel and
install it and reboot.  From then on it should work fine.

++Brett;
Newsgroups: comp.unix.bsd
From: frank@martha.utcc.utk.edu (frank segner (phrank))
Subject: why does nobody post faq (weekly) (shall I ?)
Keywords: faq?
Organization: University of Tennessee Computing Center
X-Newsreader: Tin 1.1 PL3
Date: Thu, 3 Sep 1992 03:47:15 GMT

concerning the subject:
this could avoid some obsolete 'news-traffic'...
comments desired.
frank
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 3c503 AUI support?
Organization: Weber State University  (Ogden, UT)
Date: Thu, 27 Aug 92 01:00:18 GMT

In article <1992Aug26.051010.18443@ctr.columbia.edu> vikki@e40-008-9.MIT.EDU (Vikki King) writes:
>Hi!
>
>     Is anyone using a 3c503 ethernet adapter with the AUI port rather than
>the coax connector?  Our whole net is 10BT.  I know that when using a 3c503
>card in a Novell Netware server you have to explicitly tell the o/s to use the
>AUI port if that's your configuration.  Since I seem to be getting notthing but
>silence from my 3c503 and 386BSD on our 10BT LAN, I figure that the kernel is
>assuming the connection to the LAN is via the coax port.  Anyone have any tips?
>

Minor device number.  Remknod the ethernet device.  From the sources
(at /usr/src/sys.386bsd/i386/isa/if_ec.c):

 *   Since I couldn't really think of any non-creative way (other than
 *   using a #define) of configuring the board to use the onboard xceiver,
 *   I kludged the isa_device->unit to contain this information.  Simply
 *   put, if bit-7 of isa_device->unit is set (>127) then the driver
 *   configures that unit to onboard-xceiver (BNC) and if <128 it assumes
 *   AUI.  ec_attach informs the user of this on bootup.  Also, ec_probe
 *   repairs this bit after obtaining it's information since I didn't know
 *   what else within the depths of the kernel would freak out if I left it.

re mknod it with bit 7 off.

Use the source, luke.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386bsd:ne1000 and /dev/lp probs
Organization: Weber State University  (Ogden, UT)
Date: Sun, 30 Aug 92 20:42:16 GMT

In article <21qbe-gh/@clmqt.marquette.MI.US> scott@clmqt.marquette.MI.US (Scott Reynolds) writes:
>In <1992Aug26.135535.100@Urmel.Informatik.RWTH-Aachen.DE>
>>Could the one who posted a ne1000/2000 driver enhancement please re-post
>>or leave a mail. Thank you.
>
>I'm interested in any enhancements to the driver, also; perhaps we can
>get it included in the unofficial patches on agate?

	I have a copy of the patch.  I will make it available (with several
other patches posted here) in documented patch format by uploading it to
agate tomorrow (monday) or the day after.

	When it goes into the "unofficial" directory is based on when Chris
can find the time to do it.  He, like I, is pretty overloaded at the moment.

					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
From: eje@irenaeus.mlo.dec.com (Eric James Ewanco)
Newsgroups: comp.unix.bsd
Subject: Re: new boot roms
Date: 3 Sep 92 14:44:21 GMT
Reply-To: ewanco@mlo.dec.com
Organization: Digital Equipment Corporation


In article <183c4vINNfit@maverick.ksu.ksu.edu>, brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:
> From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
> Subject: new boot roms
> Date: 2 Sep 1992 16:36:31 -0500

> Okay, here's a thought.  Why doesn't someone write up some new boot
> room code that would make a PC act a lot like a Sun when you turn it
> on.  Get rid of all the gunky MS-DOS support.  Put in a nice little
> monitor to examine memory and various registers and i/o ports and
> allow easy booting from any device and any partition on that device.

I think that is an excellent idea -- in fact I think hosing the BIOS is going
to be a necessary step in moving to more advanced operating systems.  BIOS is
out of date.  We need SCSI support in the ROMs, a monitor, and flexible booting
choices.  We need BIOS code written in protected mode (like IBM's PS/2 code),
not in real mode.  We need support for seven disk drives and other things.

> This is far, far beyond any skills I have, but it seems like it might
> be worthwhile and would solve a lot of the problems and workarounds
> that people are having and using now.  Maybe someone should get on
> AMI's or Phoenix's back and get them to add some support for other
> OS's than MS-DOS in their boot code.

Some company should propose a standard.  Maybe Digital.  IBM if they don't try
to extract license fees from everyone.

With 1 MB flash ROMs 1 mm thick, 8 mm wide and 15 cm long, we can afford to put
a lot of ROM in PCs and put lots of stuff in it.  With memory management we can
swap unused ROM out or compatibility ROM in.

It is certainly something desparately needed.
--
/=============================================================================\
| Eric Ewanco - Software Engineer     For the rash and outrageous opinions ex-|
| Digital Equipment Corp, Maynard MA  pressed herein I alone am responsible;  |
| ewanco@kalvin.enet.dec.com          they do not belong to DIGITAL(TM).      |
\==============================- 2 Th 2:15 -==================================/
From: snark@thistledown.img.com.au (Simon Burge)
Newsgroups: comp.unix.bsd
Subject: Re: news software
Keywords: rn nn news inn
Date: 1 Sep 92 18:27:09 GMT
Organization: img Consultants, Melbourne, Australia

In <1992Aug30.191106.712@Urmel.Informatik.RWTH-Aachen.DE> kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:


>Anyone gotten the usenet news directory from agate to work?

I'm assuming that you're talking about INN here.

>The most severe problems were:

>- test: too may arguments

I did that make's by hand in each directory.  Not the best solution, but
easily the most workable at 5 am!

>- lint missing. BTW, is lint still 'encumbered'? Or is there a GNU lint that
>   might help?

I answered NO to the question about linting.

>- /usr/include/sys/resource.h is missing an entry RLIMIT_NOFILE

I believe RLIMIT_OFILE should be the equivalent.

I did manage to produce some binaries, but then gave up totally for the night
before trying to write the config files...

Hope this helps,
  Simon.
-- 
Simon Burge					snark@thistledown.img.com.au
Newsgroups: comp.unix.bsd
From: pederiva@cobolt.enet.dec.com (Pascal Pederiva)
Subject: Q: 386BSD UUCP help, Ingres/Postgres ported ?
Keywords: question uucp 
Organization: Digital Equipment Corporation
Date: Thu, 3 Sep 1992 21:58:12 GMT


 Hi 386BSD Community,

-UUCP & sendmail once again. I am trying to set my PC up to run UUCP on a
 line directly connected to my Amiga. Everything works fine, but I can't
 figure out how to send Mail *OUT* of the PC via UUCP. Something I missed
 in the config files or is it a patched sendmail that I need ?

 I believe that this has been discussed before , but I couldn't find the
 solution to it anywhere. Maybe it can be put into the unofficial FAQ ,too ?

-Does anybody know if there is a working version of ingres (or postgres)
 for 386BSD ..or if there's another good database program around that
 could be used instead ? ( Or how difficult it would be to port one of
 those programs .. )

 Thanks in advance for you help,
 Pascal Pederiva 


Pascal Pederiva                     | Disclaimer: The opinions expressed are
Field Service                       |             my own and not those of my
Digital Equipment Corp.,Switzerland |             current employer.
-------------------------------------------------------------------------------
From: zhang@kuhub.cc.ukans.edu
Newsgroups: comp.unix.bsd
Subject: 386bsd. How to get modem/COM4 work?
Date: 25 Aug 92 22:44:44 CDT
Organization: University of Kansas Academic Computing Services

I loaded the Binary Distribution of 386bsd to my hard disk.
Everything works OK!  But the internal modem I have is at
COM4.  Can anyone tell me how to get the modem work at COM4?
Thank you!

F. Zhang
Email:ZHANG@KUHUB.CC.UKANS.EDU
   or:ZHANG@UKANVAX (for bitnet)
From: jtsilla@damon.ccs.northeastern.edu (James Tsillas)
Newsgroups: comp.unix.bsd
Subject: Re: X386 and Diamond Stealth: not solution
Date: 25 Aug 92 15:08:34 GMT
Distribution: comp.unix.bsd, comp.unix.sysv386, comp.windows.x
Organization: Northeastern University, Boston, MA

In article <-bannhr.hasty@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes:
Path: random.ccs.northeastern.edu!chaos!mintaka.lcs.mit.edu!olivea!decwrl!csus.edu!netcom.com!hasty
   From: hasty@netcom.com (Amancio Hasty Jr)
   Newsgroups: comp.unix.bsd
   Date: 25 Aug 92 05:58:14 GMT
   Distribution: comp.unix.bsd
   Organization: Netcom - Online Communication Services  (408 241-9760 guest)
   Lines: 42


   Hello,

   This is a quick update on Diamond Stealth (S3 based svga).

   According to Geoff Orr, from Diamond, they are not going to publicly 
   release information on how to set their clocks. All new Diamond cards
   not just the S3 based cards will use this method. 

Nice move Diamond, I guess you're really going after that 32 protected
mode market. What a shame after they did such a great job with the new
hardware. Fortunately there are many S3 based cards to choose from now.

Speaking for the X386E project, we have no plans in supporting the
Diamond Stealth but instead will focus on hardware for which we can get
some technical documentation from the vendors. This probably means that
we won't be supporting any of the Diamond products until they feel
differently about providing us with techincal information. Orchid has
been much more cooperative in this.
--
	***                                                      ***
	***  James Tsillas  jtsilla@damon.ccs.northeastern.edu   ***
	*** "He is after me. Jim is after him."                  ***
	***          - Hop on Pop, Dr. Seuss                     ***
From: cflatter@nrao.edu (Chris Flatters)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] namelist hassles
Date: 2 Sep 92 15:04:38 GMT
Reply-To: cflatter@nrao.edu
Organization: NRAO

In article 17592@hippo.ru.ac.za, ccml@hippo.ru.ac.za (Mike Lawrie) writes:
>Several programs on 386bsd-0.1 produce namelist error messages - what
>does one do to fix this? I've done a pretty vanilla install of
>{bin,src,etc}dist on a 560 Mb SCSI, 8 Mb RAM 386, and am far from being
>a bsd expert.
>
>For example:
>
>netstat (the one referred to in the FAQ) produces "filehead or nfiles
>not in namelist"
>
>netstat -r produces "rthashsize: symbol not in namelist"
>
>ps -aux produces "ps: nlist: can't find the following symbols: _fscale
>_avail_start _avail_end:

If you haven't done it already, you should rebuild the kernel.  The version
on the distribution floppy has been stripped (so it doesn't have any symbols
in it at all).

	Chris Flatters
	cflatter@nrao.edu
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: Help with installing srcdist in 386bsd
Date: 31 Aug 92 08:20:26 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <1992Aug27.181005.25135@news.columbia.edu> cl45@cunixf.cc.columbia.edu (Ching-Tse Liu) writes:

>Hi,

>	I have problem installing the source distribution. Right after
>I installed the binaries distribution, I typed "rm bin01.*" then "
>loadfd". Now when it came to src01.37, the system stopped and refused
>to copy anymore files and didn't respond to control-c. I had no choice
>but to reboot. Of course it came up with the content of /tmp cleared.
>What did I do wrong ? I tried this twice with the same problem.
>	Is it possible to install the source with the binaries installed?
>Or do I have to start all over ? Any help will be greatly appreciated.

>       		                     	***********************
>--cliu@merlin.appmath.columbia.edu	*   CLifton T. Liu    *
>--cl45@cunixf.cc.columbia.edu		***********************

There is an entry in the FAQ relating to a similiar problem with install.
I was caught with the same problem when I reinstalled my disk for more
swap space. If, after reboot, fsck does not complain about something odd
in filesystem, there is good chance that the bin release is still intact.
To install bin+src+etc I recommend the following procedure:

Install the dist.fs to the disk, as usual. Save the 'extract' utility that
is in /tmp to somewhere (e.g. to a new directory /usr/install)
Copy the bin release to the disk, with mread, e.g. by
$ for i in 1 2 3 4 5 6 7 8 9 10
> do
> echo insert disk $i and hit return
> read answer
> mread "a:bin*" /tmp
> done
$ cd /tmp
$ /usr/install/extract bin01

and after it has completed, reboot. Get a /bin/csh afterwards, and
change
$ limit openfiles 128
Get the src or etc release with the same procedure as above.

Hope that helps

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd:ne1000 and /dev/lp probs
Date: 26 Aug 92 13:55:35 GMT
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen


In article <714768522snx@nutt.demon.co.uk>, pnutty@nutt.demon.co.uk (Peter C Allnutt) writes:
>1: I can't get my ne1000 cards to work. Upon booting 386bsd sees
>the cards but reports the wrong ethernet address. It skips every
>other byte of the cards address. Has any one got ethernet running
>with ne1000 cards? All help gratefully received.
>
I got mine working together with a wd8013 ETB Elite 16 bit card.
Its a ne1000 (klone).

ne0 io 360 irq 5
we0 io 300 irq 10 mem d0000

Works so la la. I had lots of reject 65xxx messages one time when I  was doing bit ftp transfers over the gateway (Yes, I have enable the kernel GATEWAY option). Performance could be better - I have seen enhancements posted here
but 'the dog ate it'.

Could the one who posted a ne1000/2000 driver enhancement please re-post
or leave a mail. Thank you.

--Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Re: time for comp.unix.bsd.386
Organization: Taronga Park BBS
Date: Sat, 29 Aug 1992 03:34:27 GMT

In article <17m9u1INN4sg@network.ucsd.edu> brian@ucsd.edu (Brian Kantor) writes:
>In article <6XQIKDA@taronga.com> peter@taronga.com (Peter da Silva) writes:
>>I think this hierarchy would be more useful if the name implied "unix like"
>>not "posix conforming".

>So maybe you want
>	comp.os.sue-me-too.bsdi

(sigh)

No, I thought I'd made it clear that was why I was having problems with the
name.
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
Newsgroups: comp.unix.bsd
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: Re: ncsa and bsd timeouts
Date: 4 Sep 1992 21:23:02 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu

In article <TJwkqB1w165w@student.business.uwo.ca> mark@student.business.uwo.ca (Mark Bramwell CS Staff) writes:
>..Has any been able to make ncsa connect directly into the 386bsd?

There is a bug in telnet. You have to recompile telnetd with the -kludge
linemode option. (This is one of those (perverse) reverse compatibility
items that bite every now and then).

Lynne Jolitz.

Newsgroups: comp.unix.bsd
From: tsprad@rei.com (6692)
Subject: Re: Restrictions on free UNIX / 386BSD (Re: selling 386BSD)
Date: Fri, 28 Aug 1992 00:24:34 GMT
Organization: Recognition Equipment, Inc.

I'm posting this from a Data General Aviion running SVR4.  The native 
compiler is:

gcc version DG 1.37 (88open OCS/BCS, DG-1.37.31, Apr 25 1991)
-- 
Ted Spradley   Recognition Equipment, Inc.|Opinions are mine, not theirs.
1st choice:          ...!uunet!rei2!tsprad|
2nd choice:           3_hour_tour/SPRADLEY|
voice "mail":                 214-579-6692|
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: BSD4.4 (oh boy! oh boy! oh boy! oh boy!)
Date: 4 Sep 92 15:00:04 GMT
Organization: ICEM Systems, Inc.

Well, I just read the posting made by Keith Bostic in
comp.bugs.4bsd.ucb-fixes announcing that BSD4.4-alpha (encumbered
I assume) is now ready for wider distribution, but still only
to those with an USL license >:-(

Hopefully, this means that BSD4.4-lite (unencumbered :-) will be
coming out sometime in the next few months.  Does anyone know
of any plans to fold in the Net2 -> BSD4.4 diffs into 386BSD?
Is this what the Jolitz's are planning for 386BSD 0.2?

On a very related topic.  Does anyone know if UCB is still planning
a BSD4.4-lite release?  Or has the USL law suit made UCB decide to
cancel the BSD4.4-lite release?

-- 
#include <std.disclaimer>
#define FULL_NAME               "Paul Dokas"
#define EMAIL_PRIMARY           "pbd@runyon.cim.cdc.com"
#define EMAIL_SECONDARY         "pbd@power1.cim.cdc.com"
/*** "modern" humans are the embodiment of koyaanisqatsi ***/
Newsgroups: comp.unix.bsd