Xref: utzoo comp.sys.3b1:52 comp.sys.att:11663
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!uunet!mtek!bbh
From: bbh@mtek.com (Bud Hovell @ Mtek)
Newsgroups: comp.sys.3b1,u3b.misc,comp.sys.att
Subject: Re: "comp.sys.3b2" and "comp.sources.3b2" anyone?
Keywords: time to move the process elsewhere?
Message-ID: <1991Jan31.195359.4344@mtek.com>
Date: 31 Jan 91 19:53:59 GMT
References: <1991Jan29.010521.1037@mccc.edu> <1991Jan29.125635.8145@unhtel.uucp> <653@quad.sialis.com>
Distribution: na
Organization: MTEK International, Inc.
Lines: 28

In article <653@quad.sialis.com> dts@quad.sialis.com (David Sandberg) writes:
<In article <1991Jan29.125635.8145@unhtel.uucp> paul@unhtel.uucp (Paul S. Sawyer) writes:

<Hmm.  Isn't it interesting that the first sustained topic to appear in
<comp.sys.3b1 is about every AT&T machine _but_ the 3b1?
<
<Hmm... <confused look>

Well, the articles, you will notice, are being cross-posted. The original
article that launched this discussion was *specifically* directed to the
topic of whether it would make any sense to move u3b.* to comp.*.3b2.

Since the u3b.* groups (I am confident) suffer at least the same limits
to distribution as have the unix-pc.* groups, I thought a more-general
posting would be appropriate as a means of bringing up the subject amongst
those readers most-likely to have an interest.

This may have been an error in judgement on my part.

Perhaps we should *not* cross-post this discussion to comp.sys.3b1, since
those persons interested will most-probably be reading comp.sys.att anyway,
even if they cannot get u3b.*

But that was the real point, wasn't it? :-)
-- 
____________
bud@mtek.com
"When all else fails, lower standards." - bumper sticker