Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!news
From: mchinni@pica.army.mil (Michael J. Chinni, SMCAR-CCS-E)
Newsgroups: comp.unix.questions
Subject: Re:  *nix - an abbreviation?
Message-ID: <22714@adm.BRL.MIL>
Date: 9 Mar 90 22:44:49 GMT
Sender: news@adm.BRL.MIL
Lines: 16

In article recently (8 Mar 90 13:25:13 GMT) Conor P. Cahill 
<cpcahil@virtech.uucp> writes:
>In article <1344@sys.uea.ac.uk> cmp8118@sys.uea.ac.uk (D.S. Cartwright) writes:
>>other, similar systems. Therefore, using the standard UNIX wildcard *, the
>>term *NIX (or more accurately *IX to allow for those like AIX which don't fit
>>*NIX) is used to get across the concept of 'all (or most) UNIX-like systems'.
>I guess it will have to be *X to allow for hp/ux and a/ux.  :-}

So how do you handle "RTU" Concurrent's (formerly MassComp) Real-Time Unix

I don't think that anyone will ever find a SINGLE name like that (e.g. *NIX,
*IX, *X, etc.) that will work for ALL variations of UNIX by any company.

...Mike Chinni <mchinni@pica.army.mil>

                  Life is not a cabaret - it's a f*ing circus