Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!gvlf3.gvl.unisys.com!topsail!cmurcko
From: cmurcko@Topsail.ORG (Chuck Murcko)
Newsgroups: comp.unix.sysv386
Subject: Re: X386 on AT&T lockup problem
Message-ID: <1991Apr13.232453.22916@Topsail.ORG>
Date: 13 Apr 91 23:24:53 GMT
References: <1991Apr12.122901.379@virtech.uucp> <1991Apr13.162338.20814@pandora.matrox.com>
Organization: The Topsail Group
Lines: 20

In article <1991Apr13.162338.20814@pandora.matrox.com> jstark@magrethea.matrox.com writes:
>
>Or at least urge those who are having problems with X386 to post into the
>proper newsgroup, which is comp.windows.x.  I am getting tired of slogging through
>X Window related stuff in a Sysv UNIX newsgroup.
>
I hate to remind you of this, but this is X386, a 386 Unix thingie. Most of
the problems I've seen (or at least SOME of 'em) are system level, and also
relevant to other 386 X product users. I see system specific X-related stuff
on most all other system specific newsgroups. However, there is a movement
to set up a user mailing list for this. Comp.windows.x seems to be more for
generic X stuff. Those types of queries aren't what I've seen here. I agree
with Conor about the volume picking up as more people use it. Maybe it does
rate its own group.
'Till then, try using your kill file. That will avoid wading through all the
X386 and other stuff to get to what you want to see.
-- 
Chuck Murcko   The Topsail Group   538 E. Church Rd., Elkins Park, PA 19117
Internet: cmurcko@topsail.Topsail.ORG
UUCP: ...!uunet!lgnp1!gvlv2!topsail!cmurcko