Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site turtlevax.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!hao!noao!amd!turtlevax!ken From: ken@turtlevax.UUCP (Ken Turkowski) Newsgroups: net.news.group Subject: Re: Divisions of net.unix* Message-ID: <620@turtlevax.UUCP> Date: Sat, 5-Jan-85 03:45:52 EST Article-I.D.: turtleva.620 Posted: Sat Jan 5 03:45:52 1985 Date-Received: Sun, 6-Jan-85 01:18:24 EST References: <823@amdahl.UUCP> <190@masscomp.UUCP> <2151@nsc.UUCP> Reply-To: ken@turtlevax.UUCP (Ken Turkowski) Distribution: net Organization: CADLINC, Inc. @ Menlo Park, CA Lines: 19 Keywords: ARPANET In article <2151@nsc.UUCP> chuqui@nsc.UUCP (Chuqui Q. Koala) writes: >There is a BIG problem with splitting net.unix*, something people seem to >be forgetting. > >It is called the ARPAnet. A good percentage of the volume of >net.unix-wizards and net.unix comes off of the arpanet, and the arpanet >gets everything funneled back up to it. Unless you can talk the arpanet >people into splitting their end as well, you are creating a BIG logistical >problem. If you post something to net.unix.wizards.games.zork.hints, it is >easy to simply ship that to INFO-UNIX-WIZARDS on the net, but how does >something come back? and where? This is irrelevant. We are engineering only one net: that of the USENET. Whatever conventions the ARPANET or any other network needn't concern us. -- Ken Turkowski @ CADLINC, Menlo Park, CA UUCP: {amd,decwrl,nsc,spar}!turtlevax!ken ARPA: turtlevax!ken@DECWRL.ARPA