HDTenEightyP/NetNews huggingface dataset:
From: lyndon@ampr.ab.ca (Lyndon Nerenberg)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Summary: We don't give a shit; we're The Phone Company
Date: 23 Jul 92 07:34:08 GMT
Organization: Alberta Packet Radio Network

erc@unislc.uucp (Ed Carp) writes:

> The bottom line is that, if AT&T wins, any piece of code that any programmer
> has written or will write that contains even the slightest hint of containing
> "intellectual property" of AT&T (such as "for(i=0;i<XYZ; i++)") will be
> claimed by AT&T as derivitive of that so-called "intellectual property".

Hrumph! I worked at a shop with a SVR3 source license. I guess I really
wanted to get out of this damned business anyway.

> Oops ... I just did it, didn't I? :)

I'm still looking for a bass player :-)
Newsgroups: comp.unix.bsd
From: wrp@cyclops.micr.Virginia.EDU (Bill Pearson)
Subject: Re: problems bringing up 386BSD 0.1
Organization: University of Virginia
Date: Tue, 28 Jul 1992 23:04:27 GMT

	I am also having problems bringing up 386bsd 0.1 on a DOS disk
that contains two DOS 5.0 partitions.  I have succeeded in bringing up
the system when I gave it the entire disk (I was able to ftp
bindist/bin01*; extract did not terminate after 1 hr, but the system
behaved properly), but when I try part of the disk, install goes fine,
but when I reboot from the hard disk, the boot messages come up, and
then a message about copying 1 Meg of memory somewhere (it always
disappears before I can decipher it), and the machine reboots again
and again and again.

	I would appreciate advice from anyone who has succeeded in
installing 386BSD 0.1 on a hard disk (Maxtor 4380 with ESDI controller,
AMI 486 Mk? motherboard with 8 Mb, ATI VGAwonder board) that contains
two (or even one) DOS 5.0 partition.

Bill Pearson

Newsgroups: comp.unix.bsd,comp.unix.sysv386
From: jim@ferkel.ucsb.edu (Jim Lick)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!
Organization: University of California, Santa Barbara
Date: Fri, 24 Jul 1992 18:19:36 GMT

I had been planning on getting an upgrade from Esix 4.0.3A to the recently
released Esix 4.0.4.  However, because of this action by USL/AT&T, I will
not be purchasing an upgrade.  I have just sent off a note to Esix
informing them of my action, and reasons.  Remember, long distance service
isn't the only thing we can boycott.  Besides, I've never been an AT&T long
distance customer, so I can't boycott that any more than I already am.
If anyone else is considering the purchase of any AT&T or USL licensed
product (which includes all the System V Unixes), you might consider holding
off on the purchase.  But the important thing if you do is to tell your
vendor and USL what you're doing and why.

                            Jim Lick		       
Work: University of California	| Play: 1236 Camino Meleno
      Santa Barbara		|       Santa Barbara, CA 93111-1007
      Dept. of Mechanical Engr. |	(805) 964-2088 voice/msg
      2311 Engr II Building     |	(805) MUD-SPY1 data
      (805) 893-4113            |       jim@case.isla-vista.ca.us
      jim@ferkel.ucsb.edu	|       jim@cave.isla-vista.ca.us
Newsgroups: comp.unix.bsd
From: chmr@fstgds01.tu-graz.ac.at (Christoph Robitschko)
Subject: 386bsd: select(2) on com port and other questions
Organization: Technical University of Graz, Austria
Date: Wed, 29 Jul 92 16:32:13 GMT

Well, for the first part: I tried select(2) on /dev/com2 and it says
there is something to read (although there is nothing to read). 
A followng read then blocks (or returns EAGAIN if O_NONBLOCK is set).
This works well on the console. Any hints ? workarounds ? fixes ?

I also found that stty from the bin01 distribution cannot set the baud rate.
I recompiled it and everything works.

Another question: Where can I find the patch for ps.c (or kvm.c) so
that ps u works ? Where is the kern_execve.c that supports #! lines and
checks file permissions (rather than checking for owner-execute rights) ?
I did not find these on agate.

							Christoph
-- 
------------------------------------------------------------------------
Christoph M. Robitschko  | "the only man who got his work done by Friday
chmr@edvz.tu-graz.ac.at  |             was Robinson Crusoe."
Newsgroups: comp.unix.bsd
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Re: How to check Checksums?
Organization: Iowa State University, Ames IA
Date: Tue, 21 Jul 1992 14:49:09 GMT

In <NEAL.92Jul21085411@neal.ctd.comsat.com> neal@neal.ctd.comsat.com (Neal Becker) writes:

>Maybe this is a stupid question.  I got bin01.00-bin01.56, ftp'd 'em
>to a pc, put 'em on floppies, took 'em home.  Then I'm told bin01.11
>is corrupt.  Major dissapointment!

>How can I check the checksums in the MANIFEST on my unix machine at
>work *before* I transferring to my PC?

Two other people pointed out the probable cause of this.  I was having
this problem also.  It kept telling me bin01.12 and .13 were corrupt.
So, I'd rm them and go back to school and download them again and still
corrupt.  But, it wasn't the files themselves that were corrupt.

What it was seeing was a bad spot on the hard drive that the files were
sitting over.  For some reason, the stripped down utils on the dist.fs
disk didn't see the bad spot, just the corrupted file.

The fix is this:
	1) Load all the bin01 files to the /tmp dir (if they're not
	   already there).
	2) Do NOT rm the file.  Rename it: mv bin01.11 bad.bin01.11.
	   That way it will hold the bad spot on your hard disk so
	   nothing else gets put there.
	3) Simply reread bin01.11 to the /tmp dir, like this:
		mread a:bin01.11 /tmp
	4) Run extract again.  If it complains about another file being
	   corrupt, repeat the procedure for that file.

Good luck and hope this fixes your problem.
-- 
------------------------------------------------------------------------------
Michael L. VanLoon                                     "Ignorance is bliss..."
michaelv@iastate.edu      --       Computer Engineering, Iowa State University
------------------------------------------------------------------------------
From: dec@lazarus.nrtc.northrop.com (Dwight E. Cass)
Newsgroups: comp.unix.bsd
Subject: STDIO Mode "a+" screwed up
Date: 27 Jul 92 17:35:48 GMT
Organization: Northrop Research & Technology Center, Palos Verdes, CA

Hi folks,

   I have just spent the weekend trying to find out why rogue crashes
when it attempts to update its score file and have found the problem:

   In: /usr/src/lib/libc/stdio/flags.c - Mode "a+" translates to an
       open flag with O_APPEND (in __sflags()).  This means that if
       you seek the file to the beginning and start writting, all the
       written will be APPENDED to the end of the file - rather than
       updating the top of the file as specified by the plus sign.

   What's the cure - ouch.  It seems that __sflags() is called by all of
the open routines and that there is not a clean way of passing back
the fact that append is desired (why pass it back - you have to seek
to the bottom of the file [lseek (fd, 0, SEEK_END)] after the file
is opened (i.e., after you have returned from __sflags()).  So - my
proposal (which I will implement tonight and send patches for
tommorrow), add one more flag to the ->flags work in the FILE *
structure.  This flag, __SUPD 0x4000, will indicate that the file
has been opened in an append mode (i.e., I will always set this flag
for "a", "a+", "ab+", and look at it rather than O_APPEND to make the
decision as to whether to lseek or not.)  We will see what
side-effects this has.

Any other ideas?
/dec

Dwight E. Cass                 dec@nrtc.northrop.com | But there's a hole
Automation Sciences Laboratory, Northrop Corporation |   in the bucket
One Research Park, Palos Verdes Peninsula, CA  90274 | Dear Liza,
(310) 544-5393                                       |   Dear Liza...
Newsgroups: comp.unix.bsd
From: blancha@seq.uncwil.edu (Chris Blanchard)
Subject: Help needed with 0.1 and vi/elvis (2nd post)
Organization: Univ. of North Carolina @ Wilmington
Date: Fri, 31 Jul 1992 08:20:00 GMT



Hi,
    I posted this a couple of days ago and haven't heard anything so I'm
operating under the assumption that it it didn't make it out. Anyway I'm having
problems with vi under 0.1 ie it doesn't work. What I'm getting is a screen too
small error followed by bus error (core dumped). This is happening from the
console with a color vga ATI Wonder card under as many termcaps as I've had the
patience to try. If anyone has any clues PLEASE help, as this is pretty much
worthless without an editor to change things about.. :(
Thanks in advance..

--
-----------------------------------------------------------------------------
| Internet:                        |Chris Blanchard | Phone: (919) 452-9638 |
| blancha@seq.uncwil.edu           |-----------------------------------------
|                                  |   Think of it as evolution in action   |
|                                  |                           -Larry Niven |
|----------------------------------|----------------------------------------|
|---------------------------------------------------------------------------|
From: bsd4me@ssg.com (Rick Emerson)
Newsgroups: comp.unix.bsd
Subject: Re: Using IRQ 2 & VGA
Date: 20 Jul 92 14:02:03 GMT
Article-I.D.: ssg.4Vm8NB2w165w
Reply-To: bsd4me@ssg.com (Rick Emerson)
Organization: J. Deitch & Associates
Originator: 386bsd-gate@jadpc.cts.com
Precedence: bulk

james@bigtex.cactus.org (James Van Artsdalen) writes:

> [problem omitted] 
> If this is the problem, you can use Scotch tape to cover the IRQ 2
> signal on the VGA's ISA connector.
>
 
NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Cut the trace (very carefully!), slip UNGUMMED paper, or a NONCONDUCTIVE
film over the pin (risky stuff!) but NEVER, NEVER, NEVER, NEVER put adhesive
tape on a board unless you want to ...ah-hem... gum up the works FOREVER.

Rick
From: lyndon@ampr.ab.ca (Lyndon Nerenberg)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 25 Jul 92 20:33:27 GMT
Organization: Boycott AT&T!

terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) writes:

>   If AT&T/USL wins this case, this means that any vendor can claim that they
> have rights of "intellectual ancestry" or some such balderdash over any pack-
> age found on the net. What would you think if they claimed that AT&T/USL had
> "rights" to GCC because the specification of C was originally developed by
> them?

It is exactly this scenario that is covered by copyright law. And this
is the part that makes the least sense to anyone. If their assertion is
that BSD/386 is a derivative work based on System V, why are they not
challenging this as a copyright violation?

As for the C vs. gcc argument, the feeling is that you cannot protect
a programming language per se, although you can prevent someone from
calling it 'C' if you properly protect the name 'C' as used in conjunction
with that programming language. Witness what DOD has done to protect
the name Ada. This is also similar to protection of font names. You can
protect the name, but you can't protect the font itself.

So given the existance of legal remedy to deal with both these examples,
why is USL invoking smoke and mirrors instead of pursuing damages under
copyright or patent law? I think the answer is obvious.

--lyndon
From: cgd@agate.berkeley.edu (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: General problems (serial line, spontaneous reboots) (fix)
Date: 21 Jul 1992 15:19:01 -0700
Organization: Kernel Hackers 'r' Us
NNTP-Posting-Host: agate.berkeley.edu
Keywords: 386bsd serial COM

In article <1992Jul21.030339.15654@ponds.uucp> rivers@ponds.uucp (Thomas David Rivers) writes:
>I have just discovered that replacing the COM driver with the 
>bidirectional one from Chris (cgd@agate.berkely.edu) solved the
>problems I was having with screen over a serial line.

<sigh>  well, i guess i'm going to have to hack harder on the 0.1 serial
driver... there'll be a 'beta' com driver out in a day or two...

> [stuff about smaller kernel being larger...]
>
>Now, that driver isn't *too* different from the older one, and certainly
>without the 3 ethernet drivers, the kernel should be smaller.  But, 
>my new kernel is *MUCH* larger.

(I had to be "Mr. Shoehorn" to get the unoffical dist floppies i put
up the other day to work, and this was one of the things i had to figger
out...)

the kernel, as distributed, it "strip"ped...  this is generally a bad
thing, but for a application like that (where nothing wants its symbol
table or name list) it's ok...

also of note, the floppy filesystems were created with:
newfs -c 32 -i 32768 /dev/rfd0a 5in

<sigh>  nothing like tweaking filesystem params to get more space... 8-)

Chris
-- 
                            Chris G. Demetriou
                             cgd@berkeley.edu

     I'm not from the computer center, and I'm *NOT* here to help *YOU*!
From: lidl@rodan.UU.NET (Kurt J. Lidl)
Newsgroups: comp.unix.bsd
Subject: Re: Highest com port speed
Date: 21 Jul 1992 15:25:54 -0400
Organization: AlterNet -- Falls Church, Virginia, USA
NNTP-Posting-Host: rodan.uu.net
Keywords: com ports, baud rate

In article <1992Jul20.231857.17659@thunder.mcrcim.mcgill.edu> perv@flash.emf.mcgill.ca (Irwin Roger Gibson) writes:
>
>	However it seems that the highest speed supported is 38400.
>Will this be changed in a later release?      

I looked at the sources :-)

It would appear that the highest data rate is what you would want
with a V.32bis connection running with a full V.42bis compression
rate in your modem:  57600 bps.

Good luck.

-Kurt
-- 
/* Kurt J. Lidl (lidl@uunet.uu.net)   | Unix is the answer, but only if you */
/*                                    | phrase the question very carefully. */
/* Don't even think of confusing my opinions with my employer's opinions!   */
Newsgroups: comp.unix.bsd
From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz)
Subject: Archive tape driver
Organization: University of Michigan EECS Dept., Ann Arbor, MI
Date: Fri, 24 Jul 1992 11:26:00 GMT

Anyone who finds that the recently posted version of wt.c works with
their system should send me mail to receive a newer version with
significant performance improvements.  It isn't quite finished yet,
but I'll probably need testers in a day or two.

  -Dan

Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: bug: second disk drive halts 386bsd0.1
Date: Thu, 30 Jul 92 02:23:54 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: comp.unix.bsd

Currently running 386bsd 0.1 with two IDE drives during the make of X11R5 
the system seems to freeze. This is a reproducible problem in my system.
so are there any patches floating around to fix such a symptom?


Tnks,
amancio

Newsgroups: comp.unix.bsd
From: faldor@seq.uncwil.edu (Faldor Inglorion)
Subject: tip (help!)
Organization: Univ. of North Carolina @ Wilmington
Date: Mon, 27 Jul 1992 16:35:36 GMT

I'm running a 386/25MHz with 386bsd 0.1  and have com1 as a modem.
When it boots up it connects com1 and com2 to their respective devices.
When I use tip as in: "tip com1" per the install notes... I get:
	lock: open:
	all ports used.
What am I doing wrong?

Thanx in advance,
Faldor

.___________________________________________________________________.
|               University of North Carolina at Wilmington          |
|                          Faldor Inglorion                         |
|                        faldor@seq.uncwil.edu                      |
|-------------------------------------------------------------------|
|  Alien Invasion Division : Integration/Substitution Group. (ISG)  |
.___________________________________________________________________.
Newsgroups: comp.unix.bsd
From: bzs@ussr.std.com (Barry Shein)
Subject: Re: AT&T sues BSDI
Organization: The World
	<1992Jul23.180514.26289@cshl.org> <1992Jul24.004536@eklektix.com>
	<14100@ksr.com>
Date: Sat, 25 Jul 1992 21:28:33 GMT


From: jfw@ksr.com (John F. Woods)
>It is possible that AT&T's *lawyers* do not understand the concept of
>"anonymous ftp", and when someone finally explains it to them, they'll
>shit bricks.

Gold bricks no doubt.

Although they may not understand anon ftp per se they almost certainly
understand that the NET 2 software is being freely redistributed (even
if their conception of this is pimply teen-agers looking roughly like
Matthew Broderick in War Games running to their friends' houses with a
black jacketed 5 1/4" floppy.)

It's all very peculiar.

--
        -Barry Shein

Software Tool & Die    | bzs@world.std.com          | uunet!world!bzs
Purveyors to the Trade | Voice: 617-739-0202        | Login: 617-739-WRLD
From: duplain@rtf.bt.co.uk (Andy Duplain)
Newsgroups: comp.unix.bsd
Subject: DDB under 386BSD 0.1
Date: 30 Jul 92 09:15:47 GMT
Organization: BT Customer Systems, Brighton, UK


	Has anyone managed to get ddb working under 386bsd 0.1 ?  I compiled
	it into the kernel and it seems to work OK (although I don't have
	any info on how to use it) it doesn't seem to want to get out of
	debug mode (I assume the `continue' command would do this), it just
	seems to trap the CPU again.  What _should_ happen ?
	
	Thanks in advance.
	
	

-- 
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: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: Packaging 386BSD 
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sun, 26 Jul 92 10:09:29 GMT


Does anyone have an idea what the best strategy for packaging 386BSD to floppies
would be? 

I tried to produce .tar.Z files but it seems to me that the files
in the *dist directories are already packed files.

It would be nice to have one central command (cpio,tar or whatever) to
produce a shippable floppy disk distribution of the whole package.  

-- Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: Where can I find Disk Manager???
Date: 23 Jul 92 14:09:24 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <5497@umriscc.isc.umr.edu> jlu@cs.umr.edu (Eric Jui-Lin Lu) writes:

>Where can I find the Disk Manager mentioned in INSTALL.NOTES?
>Thanks in advance!!

>--Eric

>-- 
>***************************************---       Grad. student 		---*
>* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
>* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
>***************************************---   Univ. of Missouri-Rolla    ---*

I is a commercial product. Seagate often puts a disk with it together with
their larger disks (>40MB, at least they did).
Alternatively you can use Norton Diskedit (or NU), any version, to
patch the MBR.

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"
Newsgroups: comp.unix.bsd
From: jsaker@cwis.unomaha.edu (James R. Saker Jr.)
Subject: sendmail.cf help for a sendmail novice
Keywords: sendmail,uucp,aarg
Organization: University of Nebraska at Omaha
Date: Thu, 30 Jul 1992 03:43:12 GMT

Could anyone pass along some suggestions as to properly configuring
/etc/sendmail.cf in 386BSD 0.1? I'd like to configure it on a
system where my uucp mail feed will come from, say,  
mailman.omahug.org via a nightly uucp feed.

Any suggestions or sample sendmail.cf's would be greatly
appreciated!


.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
.  Jamie Saker					jsaker@cwis.unomaha.edu    .
.  Network Costing Analyst			Business/MIS Major	   .
.  Telenational Communications			Univ. Nebraska at Omaha	   .
.  (402) 392-7548							   .
.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .


Newsgroups: comp.unix.bsd
From: leisner@trianguli (Marty Leisner 311/? x?)
Subject: filesystems/sys is a symbolic link on agate
Reply-To: leisner.henr801c@xerox.com
Organization: Xerox
X-Newsreader: Tin 1.1 PL4
Date: Tue, 21 Jul 1992 13:35:44 GMT

I'm going to agate.berkeley.edu to get a BSD-0.1 distribution.

pub/386BSD/386bsd-0.1/filesystem/sys is a symbolic (unreadable) to /usr/src/sys.386bsd

On bootable, theres:
dist.fs.Z   fixit.fs.Z

Is dist the 386BSD which boots a system from one floppy?



--
marty
leisner.henr801c@xerox.com  
Member of the League for Programming Freedom
From: dburr@sbphy.physics.ucsb.edu (Donald Burr)
Newsgroups: comp.unix.bsd
Subject: Latest 386BSD Distribution on DEC TK50 tape?
Date: 30 Jul 92 23:19:22 GMT
Reply-To: dburr@sbphy.physics.ucsb.edu
Organization: UCSB Physics Department

Is there anyone out there who would be willing to put the latest 386BSD
distribution onto DEC TK50 tape for me?  Our site does not have Internet
access, but we have many students who are eager for a UNIX operating
system to run on their home computers (so they can do work at home,
etc.)  Please get back to me through Email if you can.  Thanks.

: Donald Burr, Coordinator          : dburr@sbphy.physics.ucsb.edu   INTERNET :
: Santa Barbara Area Network(SBANET): dburr@gnu.ai.mit.edu (Backup)  ======== :
: Santa Barbara, CA  USA            : DonaldBurr@aol.com (AOL gateway)        :
: uunet!dsc.com!dschub!sbanet!dburr : America OnLine: DonaldBurr              :
Newsgroups: comp.unix.bsd
From: spel@hippo.ru.ac.za (Dr. Eberhard W. Lisse)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD
Organization: Katatura State Hospital, Windhoek, Namibia
Date: Fri, 24 Jul 1992 11:13:57 GMT

In <1823@adagio.UUCP> grog@adagio.UUCP (Greg Lehey) writes:

>In article <1992Jul22.212903.29537@gateway.novell.com> terry@npd.Novell.COM (Terry Lambert) writes:
>>*** prediction alert *** prediction alert *** prediction alert ***
>>
>>I think that AT&T will win; not on the merits of reality, but on the merits
>>of their arguments.  It will be difficult, without educating the judge to
>>the point of a CS degree, to draw the distinctions necessary to prove
>>non-infringement by BSDI.  It certainly *looks* like BSDI is infringing
>>to a layman, and that's what the judge will be.

>Well, I sincerely hope you're wrong; but I also believe you will be.
>Certainly AT&Ts win/lose situation won't be based on `the merits of
>reality', but on the other hand they have so far not been able to give
>a single example of where the alleged infringement is. I don't believe
>they want to win; they're playing this court case relatively low-key,
>and I suspect their motives are more to keep BSDI from doing real work
>(like a production release of BSD/386) and to keep potential customers
>away. That way, they don't need to win.

On a recent congress I attended in Boston one of the speakers
(a Professorin Consumer Law) on medical liability said
something which applies here:

'You must make 12 idiots from the street (who were too stupid
to avoid jury duty in the first place) understand a complex 
situtation. So nobody can predict how this is going to come out'

:-)-O


It really doesn't help to discuss the ifs and whens and so on
if this trial is going to a jury. Send letters to the board of
USL's parent company telling why you start using MCI, that
will hlep if enough people do it (but how many will do this
100, 1000? They laugh about it)

If they go after Jolix then I suggest they put the sources on
one of the boxes in the CIS where there is no copyright.

regards, el
-- 
Dr. Eberhard W. Lisse    \          /                   (spel@hippo.ru.ac.ZA)
Katatura State Hospital   \        |                            (el@lisse.NA)
Dept of Obstetrics & Gyn   \ *    /                         Private Bag 13215
Windhoek, Namibia           ;____/ (postmaster@uonamib.NA) Postmaster NAmibia
Newsgroups: comp.unix.bsd