> Always starting from machine_a, where machine_b is the "original" remote > host. > > METHOD A. > 1. ssh u...@machine_b > 2. scp -v u...@machine_a:/some/tar/ball . > 3. untar ... > 4. chmod u+x > 5. ./whatever > 6. scp -v output.txt u...@machine_a:/home/user/. > 7. exit > > > METHOD B. > 1. scp -v /some/tar/ball u...@machine_b:/home/user/. > 2. ssh u...@machine_b > 3. untar ... > 4. chmod u+x > 5. ./whatever > 6. exit > 7. scp -v u...@machine_b:/home/user/output.txt . >
Yes, Method A is closest to what I was hoping to achieve, but Method B was closest to what I was doing. Method A is cumbersome because it lacks lcd and forces the user to remember (and type) the username, password, IP address, and full path to the file. I was hoping for an elegant solution that did not need all that (sftp does not). And maybe having a "lls" (local ls) would have been nice too, something I've always missed from sftp. -- Dotan Cohen http://bido.com http://what-is-what.com Please CC me if you want to be sure that I read your message. I do not read all list mail. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/880dece01003211708r569fa06dq6b37bc1abfc0...@mail.gmail.com
