scp is a lot simpler to use, but you've got a lot of cpu overhead from the encrypt-decrypt processing.
"Thousands of years ago, cats were worshipped as gods. Cats have never forgotten this." _ Anonymous Gordon Wolfe, Ph.D. (425)865-5940 VM Technical Services, The Boeing Company > ---------- > From: Alex deVries > Reply To: Linux on 390 Port > Sent: Thursday, January 22, 2004 1:35 PM > To: [EMAIL PROTECTED] > Subject: Re: SLES Installation: extended passive mode? > > How about just using scp? It's much simpler. > > e.g. on your ia32 Linux system, run: > > scp <file-to-transfer> root@<ip-address-of-instance>:/tmp > > > - Alex > > > Nick Laflamme wrote: > > > Post, Mark K wrote: > > > >> No suggestions, yet, but a question. Are there any sort of firewalls > >> or proxies between you and the FTP server? > >> > > > > There's a firewall in place, but I can FTP from the Linux guest to > > another PC in my office OK, and I can FTP from a CMS user on the same > > side of the firewall to the Linux PC in question. I don't think the > > firewall is an issue. > > > >> Well, one suggestion. If I were you, I would try using NFS instead > >> of FTP. I've always had better luck installing SUSE over an NFS mount. > >> > > > > Said firewall rules out NFS. > > > >> Mark Post > >> > >> > > > > Nick > > > >
