Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!unisoft!gethen!bdt!david
From: david@bdt.UUCP (David Beckemeyer)
Newsgroups: comp.sys.ibm.pc
Subject: Re: UNIX to PC File transfer
Message-ID: <168@bdt.UUCP>
Date: 3 Mar 88 22:22:02 GMT
References: <1054@ur-tut.UUCP>
Reply-To: david@bdt.UUCP (David Beckemeyer)
Organization: Beckemeyer Development Tools, Oakland, CA
Lines: 22
Keywords: xmodem

In article <1054@ur-tut.UUCP> aptr@ur-tut.UUCP (The Wumpus) writes:
>I suggest using xmodem protocol to move files.  Xmodem has been around
>for many years and almost every communications package supports
>atleast the default version of it (I have not seen any programs that
>do not support it).  There are several Xmodem drivers available for
>UNIX.  I have the sources to two different ones.  If there is enough
>interest, I am willing to post one of the sources, but it may be out
>of date.

This is dead end argument.  Kermit has been around for many years too.
The PC-DOS and CP/M types can say "well xmodem is on all the PC machines
so put it on UNIX and use Xmodem."  Well the same argument works both
ways.  Nether Xmodem nor Kermit is a great protocol.  Every UNIX machine
has kermit.  Kermit is available for DOS free.  Most DOS machines have
Xmodem (is this really true?).  Xmodem is availabe for UNIX free.  So
why force one or the other down everybody's throat.

If you want X-modem, use X-modem.  If I want kermit, I'll use kermit.
-- 
David Beckemeyer			| "To understand ranch lingo all yuh
Beckemeyer Development Tools		| have to do is to know in advance what
478 Santa Clara Ave, Oakland, CA 94610	| the other feller means an' then pay
UUCP: ...!ihnp4!hoptoad!bdt!david 	| no attention to what he says"