Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!uunet!uunet.uu.net!rick
From: rick@uunet.uu.net (Rick Adams)
Newsgroups: comp.mail.misc
Subject: Re: BITFTP grief!
Summary: Not Invented WHERE?
Message-ID: <1991May24.231527.7057@uunet.uu.net>
Date: 24 May 91 23:15:27 GMT
References: <1991May16.224338.286@crom2.uucp> <1991May17.200736.8137@uu.psi.com> <22813@shlump.lkg.dec.com>
Sender: usenet@uunet.uu.net (UseNet News)
Distribution: na
Organization: UUNET Communications Services
Lines: 25
Nntp-Posting-Host: uunet.uu.net

In article <22813@shlump.lkg.dec.com>, lan_csse@netrix.nac.dec.com (CSSE LAN Test Account) writes:
> Ummm...UUCP over TCP has been in existence for years; quite a lot of
> vendors supply it.  See if your library has uucpd in it; you might also
> check your /etc/services or /etc/inetd.conf files for its name.  If it
> exists on your system, it is a whole lot nicer than ftp. It retries if
> the call doesn't go through; it does proper error checking and doesn't
> hand you garbaged files; it runs easily from a script; you don't have 
> to do it twice because you forgot to say "binary" the first time, and 
> all those good things.  Plus, when I've done timing tests, it has often
> run 3-4 time faster than ftp for big files.
> 
> If the BSD crowd didn't have such a bad case of NIHitis, we'd all have
> it by now...


Huh. UUCP over TCP was popularized by ME. (I also "invented" it. It was
also "invented" inside of Bell Labs at about the same time.) I wrote the code.
I integrated it into 4.2BSD. I gave it away to hundreds (of properly licensed)
sites. UUCP over TCP was what kept usenet alive until nntp came along.

Now, given that I freely admit to being one of the BSD crowd, exactly
what is my NIHitis and how did giving code away to all comers keep
"you all" from having it? 

---rick