Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!decvax!mcnc!ecsvax!bet From: bet@ecsvax.UUCP Newsgroups: net.news Subject: Re: Posting object code to net.sources Message-ID: <3083@ecsvax.UUCP> Date: Thu, 9-Aug-84 00:34:08 EDT Article-I.D.: ecsvax.3083 Posted: Thu Aug 9 00:34:08 1984 Date-Received: Fri, 10-Aug-84 07:56:44 EDT References: turtleva.466 Lines: 19 Wait, wait, wait. USENET is a network of sites running UNIX so we aren't interested in CP/M (or MS-DOS, as has been the case) object code? So why does net.micro.* exist? For the matter of that, if material must relate to UNIX to be appropriate to USENET, why have *any* of the non-technical groups? Now it may be the case that net.sources should be named net.unix.sources, but I haven't ever heard this claim presented before. If people are really down on distributing uuencoded binaries through net.sources, then let's make up another group for these things, sharing the feature of net.sources of being set up for large files. The description I have heard for net.sources is something like "large files, such as source code", and I have seen other things besides source code (in particular large documents) posted to this group. I can't understand all the squawking. Do people have broken 'n' keys? Or is it a new experience to find something not if interest to *everybody* in net.sources? Bennett Todd ...{decvax,ihnp4,akgua}!mcnc!ecsvax!bet