Xref: utzoo news.admin:7646 news.groups:14699 comp.mail.uucp:3762 comp.os.vms:19700
Path: utzoo!attcan!uunet!samsung!usc!apple!voder!pyramid!csg
From: csg@pyramid.pyramid.com (Carl S. Gutekunst)
Newsgroups: news.admin,news.groups,comp.mail.uucp,comp.os.vms
Subject: Re: New newsgroup hierarchy
Message-ID: <91457@pyramid.pyramid.com>
Date: 17 Nov 89 10:02:05 GMT
References: <1618.25614348@mccall.uucp> <1989Nov16.172110.21492@utzoo.uucp>
Reply-To: csg@pyramid.pyramid.com (Carl S. Gutekunst)
Organization: Pyramid Technology Corp., Mountain View, CA
Lines: 23

In article <1989Nov16.172110.21492@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>In article <1618.25614348@mccall.uucp> tp@mccall.uucp writes:
>>...newsgroups vmsnet.*.... This hierarchy is for topics of interest to
>>VAX/VMS sites.
>
>We will unhesitatingly carry them if and when they become subgroups of
>comp.os.vms.  We will be very reluctant to carry them if you insist on
>having your own top-level name; there are too many top-level names already,
>and I utterly fail to see why you need one of your own.

No! This is a different distribution -- therefore it definitely should have
its own top-level name. The whole inet thing -- running a completely separate
distribution within the traditional namespace -- has adaquately demonstrated
that this is the wrong way to go. It's easy to handwave and blame it on poor
software, or poor adminsitration; but the fact remains that running different
distributions within the same namespace just doesn't work very well. Think of
it as administrative friendliness.

What next? Fold biz.all and clari.all into the comp, sci, etc. hierarchy?

vmsnet.* is the right way to go.

<csg>