Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ucdavis!iris!tuck
From: tuck@iris.ucdavis.edu (Devon Tuck)
Newsgroups: comp.unix.xenix
Subject: Re: Change name of news group
Keywords: sco xenix
Message-ID: <6958@ucdavis.ucdavis.edu>
Date: 8 Mar 90 19:56:17 GMT
References: <206@pcssc.UUCP>
Sender: uucp@ucdavis.ucdavis.edu
Reply-To: tuck@iris.ucdavis.edu (Devon Tuck)
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Lines: 34

In article <206@pcssc.UUCP> dma@pcssc.UUCP (Dave Armbrust) writes:
>
>Because SCO is shipping both unix and xenix it may be to our
>advantage to change the name of this news group to comp.unix.sco.
>
>If that seems unreasonable lets start a new group by that name.
>
>

I think this is a wonderful suggestion!  We would then have a unix group
for the well known Xenix package, (comp.unix.xenix), as well as one for SCO
Unix, (comp.unix.sco).  This makes good logical sense, since SCO is
quickly becoming a 'household name' in the PC Unix market, and their
ultimate goal is to approach their own highly compatible version of Unix
System V.

If we are to support two groups, however, we must decide whether we want
only SCO Unix specific items discussed on comp.unix.sco, or whetehr we
want only SCO Xenix specific items discussed  on comp.unix.xenix.  If we
think long range, we can imagine comp.unix.xenix dwindling in use over
the next 5-10 years, while comp.unix.sco should become immensly popular
over the next 1-2 years.  We can even imagine a comp.unix.sco.{od,desktop,open}
emerging for Open-Desktop specific items, and a comp.unix.sco.x for
SCO-Xsight, or SCO-Motif specific development issues.  If we do create
this new group, human nature dictates that the first option will prevail
until enough people move to SCO-Unix, and until the amount of SCO-Unix
specific discussion greatly overwhelmes SCO-Xenix specific discussion.


No matter what happens, I think the one thing we don't want to do is shatter
the steady and unchecked flow of general discussion on issues which apply to
both systems.

Devon Tuck -- tuck@iris.ucdavis.edu