Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site down.FUN Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!down!honey From: honey@down.FUN (Peter Honeyman) Newsgroups: net.micro.att Subject: Re: 3b2 has no uuencode/uudecode?? Message-ID: <516@down.FUN> Date: Tue, 4-Jun-85 08:30:59 EDT Article-I.D.: down.516 Posted: Tue Jun 4 08:30:59 1985 Date-Received: Thu, 6-Jun-85 01:53:49 EDT References: <198@uwvax.UUCP> <1072@cp1.UUCP> <200@uwvax.UUCP> <508@down.FUN> <205@uwvax.UUCP> <1828@ukma.UUCP> <2259@sun.uucp> Organization: Princeton University, EECS Lines: 30 yes, system v uucp supported forwarding under some circumstances, but did so in a tasteless, arcane manner. (it looked at the incoming S request, and if it saw a !, well ...) the forwarding code was formidable -- massive and obscure. so we trashed it. then we fought about it. nowitz observed that a multi-hop uucp request could be effected by turning it into uux nexthost!uucp ... honeyman and redman opined that this was a job for a special utility, a la uusend, not a task for uucp. nowitz demonstrated that the implementation could be made concise and tasteful, unlike the previous efforts. honeyman and redman continued to sniff in disgust. nowitz, being bigger and louder than redman and honeyman put together, won. then we fought some more. redman observed that uucp could be made into a shell script that called uux on the nexthost, that consistency demanded etc., that code maintenance would be simplified, that etc. etc. redman, a passive and diminutive soul, lost this battle. in summary, both honey danber and system v uucp's support multi-hop requests, but they are incompatible with one another and all other versions of uucp. we judged that our ideas were so much better than our predecessors' that we could justify this incompatibility. besides, eventually everyone will run honey danber. cover the earth. addressing your other point, honey danber supported 4.2bsd sockets long before 4.*bsd uucp did. peter