Xref: utzoo news.groups:25757 comp.sys.att:10956
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!bcm!lib!thesis1.hsch.utexas.edu
From: jmaynard@thesis1.hsch.utexas.edu (Jay Maynard)
Newsgroups: news.groups,comp.sys.att
Subject: Re: Reorganization of comp.sys.att (was: CFD: create comp.sys.3b1)
Message-ID: <4371@lib.tmc.edu>
Date: 27 Nov 90 11:19:40 GMT
References: <1990Nov20.040329.5968@bagend.uucp> <8352@gollum.twg.com> <1990Nov27.042139.2315@news.gvl.unisys.com>
Sender: usenet@lib.tmc.edu
Followup-To: news.groups
Organization: University of Texas Medical School at Houston
Lines: 18
Nntp-Posting-Host: thesis1.hsch.utexas.edu

In article <1990Nov27.042139.2315@news.gvl.unisys.com> markw@GVL.Unisys.Com (Mark H. Weber) writes:
>    comp.sys.att.3b1    7300's, 3b1's and related CT machines
>                .3b2    Can include the 3b2-clones (3b5, 3b15, 3b20..)
>                .misc   Other stuff

I'm surprised that nobody else has mentioned this yet...

Some systems can't handle newsgroups with leading digits in parts of
the name. A number of groups have been originally proposed that way, and
they all have been changed due to this problem...in fact, the u3b.*
hierarchy started out in life as the 3b.* hierarchy and had to be renamed.

No, I don't have a specific suggestion, but having groups named .3b1 and
.3b2 will cause problems.
-- 
Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can
jmaynard@thesis1.hsch.utexas.edu  | adequately be explained by stupidity.
         "With design like this, who needs bugs?" - Boyd Roberts