Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site osiris.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!panda!talcott!harvard!seismo!umcp-cs!aplvax!osiris!eric From: eric@osiris.UUCP (Eric Bergan) Newsgroups: net.unix-wizards Subject: Re: UUCP & you Message-ID: <161@osiris.UUCP> Date: Sat, 2-Mar-85 20:17:31 EST Article-I.D.: osiris.161 Posted: Sat Mar 2 20:17:31 1985 Date-Received: Tue, 5-Mar-85 02:29:28 EST References: <8831@brl-tgr.ARPA> Organization: Johns Hopkins Hospital Lines: 29 > Yeah, but I bet you read the articles on UUCP in the manual set. How > straight can you get? Who is going to know that you read the code? > Experience is not copyrighted, patententable, or protected by trade > secret. I suppose that if your license said you couldn't run yacc on > Tuesdays, you probably wouldn't do it. Agreements often are more > restrictive than they have to be in order to apply to the real misuses. > There is a fine line between fair use and outright piracy. Try to find > the happy medium. BTW, why do you call it UUCP? Isn't that stealing > their name? > > jim > */ Is personal integrity such a vanishing quantity these days? Having met Lauren, I suspect he did not look at the code. Having looked at the code myself, I can state that it probably wouldn't have helped that much. The interaction of the various parts of UUCP, particularly the 'g' protocol itself, are arcane, to say the least. What I really don't understand is this attack! Lauren trys to explain some of the facts about UUCP, and you jump all over his case. Lauren has never tried to keep his knowledge of UUCP to himself, and has always answered questions (including some pretty inane ones) in a professional manner. This is, after all, unix-wizards, not net.flame. -- eric ...!seismo!umcp-cs!aplvax!osiris!eric