#1 a lot of people use ssh to ssh from a unix to unix machine, this means
there are no "checkboxes"
#2 ftp / sftp / scp are used to transfer
files... and they really should never have been allowed to alter file
contents when transfering...
#3 once your file is transfered run dos2unix or unix2dos or if you in
windows or mac.. the equivilant and you should be all set.. =)
-pete
--
''~``
( o o )
+-------------------------.oooO--(_)--Oooo.-----------+
| Peter J. DiCostanzo Jr. ComPath Incorporated |
| Systems Engineer -= www.compath.com =- |
| (Solaris / Linux / NT) [EMAIL PROTECTED] |
| [EMAIL PROTECTED] |
| |
|Disk space is too good .oooO |
| for them -BOFH #11 ( ) Oooo. GOT LINUX?|
+----------------------------\ (----( )-------------+
_) ) /
(_/
On Sat, 10 Mar 2001, Bob Babcock wrote:
> > Humm, very strange. SSH always transfers in binary mode, it never does
> > translations. If you are on a UNIX machine there are no CRs at the end of
> > the line just LFs, the Mac uses just CRs and windoze uses a CRLF
> > sequence. SSH will not touch any of these on any platform as far as I
> > know.
>
> To be blunt, why are the programs that implement the ssh protocol so stupid?
> Ftp solved this problem years ago by making ascii transfers part of the
> protocol. Apparently ssh doesn't do this, but that doesn't stop an ssh
> program from doing the trivial line termination translations when it sends a
> file. All that would be needed are commands or checkboxes for, say,
> "binary", "to-unix", "to-dos" and "to-mac". Auto-sensing is a little harder,
> and I don't know if an ssh program can tell what OS is running on the other
> end.
>
