Xref: utzoo news.admin:7677 news.groups:14782 comp.mail.uucp:3775 comp.os.vms:19760
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!xanth!mcnc!ecsvax.uncecs.edu!dukeac!wolves!ggw
From: ggw@wolves.uucp (Gregory G. Woodbury)
Newsgroups: news.admin,news.groups,comp.mail.uucp,comp.os.vms
Subject: Re: New newsgroup hierarchy
Summary: Why?
Keywords: top level group names hierarchies
Message-ID: <1989Nov20.005435.14063@wolves.uucp>
Date: 20 Nov 89 00:54:35 GMT
References: <1618.25614348@mccall.uucp> <1989Nov16.172110.21492@utzoo.uucp>
Reply-To: ggw@wolves.UUCP (Gregory G. Woodbury)
Followup-To: news.groups
Organization: Wolves Den UNIX BBS
Lines: 24

In article <1989Nov16.172110.21492@utzoo.uucp> (Henry Spencer) writes:
>In article <1618.25614348@mccall.uucp> tp@mccall.uucp writes:
>>...newsgroups vmsnet.*. 
>
>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.

	Henry, please elaborate on your contention that there are
"too many top-level names already".  To me it seems that the creation of
a new top-level name is an ideal way to handle the potential traffic for
lots of new sites that may come on the heels of this new set of software.
	Not only do they avoid the fol-de-rol of a newgroup election, but
it is easier to tailor the feeds or sys files with a new top-level.

<Followups to news.groups>
-- 
Gregory G. Woodbury
Sysop/owner Wolves Den UNIX BBS, Durham NC
UUCP: ...dukcds!wolves!ggw   ...dukeac!wolves!ggw           [use the maps!]
Domain: ggw@cds.duke.edu  ggw@ac.duke.edu  ggw%wolves@ac.duke.edu
Phone: +1 919 493 1998 (Home)  +1 919 684 6126 (Work)
[The line eater is a boojum snark! ]           <standard disclaimers apply>