> |Adequate file transfer in SSH would look something like this:
>
> |local% scp remote:files_I_want/* . <-- multiple file transfer
>
> I do that frequently using scp. The _only_ problem is that
> the * must be communicated to the other side of the connection.
overlooked that. Okay, that point is fine.
> ssh remote 'cd /; find directory-list -depth -print |
> sed -e "s/^\///" | cpio -oc' | cpio -icmud
> |Right now, we are forced to tar/zip the files we want, then log out, scp
> |the archive, and log back in (assuming a single remote login). Since we use
> |challenge/response tokens, that's a 2 minute process MINIMUM.
>
> Sorry, that is your problem, not ssh's.
> SSH does provide those services. You just have to have
> a little imagination and learn to use the UNIX small
> tool model for obtaining results instead of expecting
> the program to do every for you by itself.
Wow. Who needs functionality when almighty arrogance will do instead?
You miss the point. Every single one of your examples forces me to log out,
transfer the files I want, then log back in again.
You just have to learn that imagination won't do half as good as a working
implementation.
Also, bitch not about users using FTP when the alternative is a 5 pipe 90
character command line.
--
Joe Rhett Systems Engineer
[EMAIL PROTECTED] ISite Services
PGP keys and contact information: http://www.noc.isite.net/Staff/
