Using the text-based FTP interface helps you understand what each action in a graphical FTP session does. This understanding can be handy when, for example, the graphic client does not automatically detect the file type being transferred. In this situation, a binary file is transferred as an ASCII file and is therefore useless. Conversely, an ASCII file transferred as a binary prints the ^m control character at the end of each line. This error typically occurs when transferring files from older Microsoft Windows operating systems to Linux, as the Windows FTP client defaulted to ASCII, not binary transfers.
Was this article helpful?