Xref: utzoo comp.sys.3b1:19 comp.sys.att:11629
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!rex!uflorida!mthvax!aem
From: aem@mthvax.cs.miami.edu (a.e.mossberg)
Newsgroups: comp.sys.3b1,u3b.misc,comp.sys.att
Subject: Re: "comp.sys.3b2" and "comp.sources.3b2" anyone?
Keywords: time to continue the process?
Message-ID: <1991Jan28.152827.8986@mthvax.cs.miami.edu>
Date: 28 Jan 91 15:28:27 GMT
References: <1991Jan28.012133.13672@mtek.com>
Reply-To: aem@mthvax.cs.miami.edu
Distribution: na
Organization: University of Miami Department of Mathematics & Computer Science
Lines: 26

In <1991Jan28.012133.13672@mtek.com> bbh@mtek.com (Bud Hovell @ Mtek) writes:

>Any chance that the folks in the 'u3b' groups might like to come over
>and play under the new schema?

>Particularly for those such as we who have older 3B2 machines, the logic for
>doing so may be as compelling as that which the vast majority of us
>supported in voting the switchover from unix-pc.* to comp.*.3b1. It appears
>the 'u3b' groups suffer equally from lack of general distribution. And there
>are alot more 3B2 machines of various shades than 3B1s, so readership
>should not be an issue, it would seem.


It seems that it would make more sense from the beginning to have a
comp.sys.3b and comp.sources.3b since neither the unix-pc nor the u3b
hierarchies are exactly high volume, then in the future if it was
warranted subgroups comp.*.3b.1, comp.*.3b.2 could have been created.
What do I know though?

aem
sysadmins for logical usenet naming (SLUN)

-- 
aem@mthvax.cs.miami.edu .......................................................
Contaminate your bed, 
and you will one night suffocate in your own waste.	- Chief Seattle