Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!mips!mips!sdd.hp.com!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!menudo.uh.edu!sugar!taronga!peter
From: peter@taronga.com (Peter da Silva)
Newsgroups: comp.unix.bsd
Subject: Re: time for comp.unix.bsd.386
Message-ID: <I2NI1F7@taronga.com>
Date: 25 Aug 92 01:40:45 GMT
References: <1992Aug23.052605.14262@uniwa.uwa.edu.au> <177pd8INNrb1@rodan.UU.NET> <1992Aug24.074542.29794@resonex.com>
Organization: Taronga Park BBS
Lines: 18
In article <1992Aug24.074542.29794@resonex.com> michael@resonex.com (Michael Bryan) writes:
>[I know there are a lot of strong feelings about comp.unix.bsd.386bsd
>vs comp.os.386bsd, and other such issues. If this is going to go
>any further at this time, though, I'd say hold off until we get into
>news.groups...]
FWIW, if we're going to have a bunch of comp.os.unix-alike groups, then
this should be comp.os.386bsd. I think it would be better to put the
unix-alikes together in a common hierarchy, but for political reasons
we shouldn't single out 386bsd as a special case.
As a compromise, how about a comp.posix hierarchy for those operating
systems that use the POSIX API as the primary programming interface?
--
`-_-'
Have you hugged your wolf today? 'U`
Peter da Silva, Taronga Park BBS, Houston, TX +1 713 568 0480/1032