Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!zehntel!hplabs!sri-unix!wcwells%ucbopal.CC@Ucb-Vax.ARPA From: wcwells%ucbopal.CC@Ucb-Vax.ARPA Newsgroups: net.micro.cpm Subject: Re: Umodem Message-ID: <12590@sri-arpa.UUCP> Date: Sat, 18-Aug-84 23:15:32 EDT Article-I.D.: sri-arpa.12590 Posted: Sat Aug 18 23:15:32 1984 Date-Received: Mon, 20-Aug-84 01:47:23 EDT Lines: 32 From: William C. WellsIn reply to: Date: Sat, 18 Aug 84 12:37:24 edt From: gvax.rej@Cornell.ARPA (Ralph Johnson) Message-Id: <8408181637.AA06294@CORNELL-GVAX.ARPA> To: wcwells@BERKELEY Subject: Re: Umodem You really want to use uucp to transfer files from one Unix machine to another. It's the standard. Is there some reason why you can't do this? I do not want to use "uucp" because the it requires disk space for spool files and human intervention to set up and maintain. In the next couple of years we expect to have over 2000 microcomputer/workstations on campus. Many of those microcomputer/workstations will be Unix systems with modems and terminal emulation software. The overhead in maintain uucp links with 1000+ workstations would be to high. So what I am looking for is a "xmodem" (cf. MDM7xx) program written in C that will permit a user on a Unix system (eg. a Unix microcomputer) to dial out to a remote Unix system, login to a remote Unix system (via terminal access dial-up lines), execute a remote "umodem" program to start a file transfer, escape back to the local program, and fire up the local end of the file transfer. Bill Wells wcwells@ucbvax.ARPA ucbvax!wcwells wcwells@ucbjade.BITNET