Xref: utzoo comp.mail.uucp:1482 comp.protocols.tcp-ip:4145
Path: utzoo!attcan!uunet!oddjob!gargoyle!att!alberta!access!edm!steve
From: steve@edm.UUCP (Stephen Samuel)
Newsgroups: comp.mail.uucp,comp.protocols.tcp-ip
Subject: Re: UUCP Over TCP/IP (why?)
Message-ID: <3232@edm.UUCP>
Date: 19 Jul 88 09:41:08 GMT
References: <387@comdesign.UUCP>
Distribution: all
Organization: Unexsys Systems Inc., Edmonton,AB.
Lines: 33

From article <387@comdesign.UUCP>, by pst@comdesign.uucp (Paul Traina):
> Pardon my ignorance,  but I'm confused about running uucp over TCP links.
> 
> My question is why?  The ftp/smtp/bsmtp interface seems much better for
> handling files & mail, and for those who run it, the rsh interface seems
> better than uux.  So, I ignorantly ask,  why do some folk run uucp over TCP?

Simple: Why do people use fortran on a MIPS?? 
	Because it still works, and people are used to it.

For a lot of things, it's much easier to add TCP support under UUCICO
than it is to rewrite everything else that is used to the UUCP interface
program set.

It's a lot easier being able to go from a serial line connection to
an ethernet connection by changing one line in L.sys (or Systems)
than it is to teach everybody how to use the "new and improved" stuff
Besides -- UUCP is kinka fire-and-forget. Who cares what protocol it uses
as long as it works.
rsh/ftp/rcp require a supporting UID on the remote system, and that's not
necessarily easy to arrange. They also need a bit more babysitting than FAF
UUCP.

-- 
-------------
 Stephen Samuel 			Disclaimer: You betcha!
  {ihnp4,ubc-vision,mnetor,vax135}!alberta!edm!steve
  BITNET: USERZXCV@UOFAMTS
-- 
-------------
 Stephen Samuel 			Disclaimer: You betcha!
  {ihnp4,ubc-vision,mnetor,vax135}!alberta!edm!steve
  BITNET: USERZXCV@UOFAMTS