What Erin said gives a clue, where she mentions "an exec channel".
The problem (or "feature") is that SCP is layered on SSH, which itself is a GOOD thing. SSH performs A/E translation because its main purpose in life is to provide command access (whether batched or interactive). So as annoying as the A/E astonishment is, for me its an old story. There are so many other points where text or binary must be handled differently ... but this isn't necessarily helping. Consider this: ssh remotehost tar cf - /something | tar xf - will flat out not work when hitting z/OS (USS) or when issued to an ASCII system from there. SCP at least gets the content across intact. (Translated, yes, but intact.) A little pipe-think would resolve the TAR issue. Dunno if it would help in the SCP case. (EG: convert binary to base64 before transport, then restore base64 back to its binary form on the receiving end.) -- R; ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
