Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!noao!coyote!ejm
From: ejm@coyote.datalog.com (E.J. McKernan)
Newsgroups: comp.unix.sysv386
Subject: Re: X386 on AT&T lockup problem
Message-ID: <1991Apr21.011156.9659@coyote.datalog.com>
Date: 21 Apr 91 01:11:56 GMT
References: <1991Apr12.122901.379@virtech.uucp> <1991Apr14.022422.6177@coyote.datalog.com> <1991Apr20.062159.7333@emisle.uucp>
Organization: Datalog Consulting, Tucson, AZ
Lines: 15

In article <1991Apr20.062159.7333@emisle.uucp> dvb@emisle.UUCP (David Van Beveren) writes:
>
>How about a little more general:
>            comp.windows.x.sysv386.
>X386 is not the only sysv386 x-windows product. (Just the best :^) ) And there
>are some issues that relate to more than X386.
>
>That would take a lot of traffic from this group, and some from comp.windows.x. 
Can't argue with that. Sounds good here.

-- 
   /|_|\   Datalog Consulting, Tucson, AZ
  ( . . )  ejm@datalog.com
   \   /   ...!noao!datalog.com!ejm
    \_/