Deployment Config
Step 11. Typo error... End Of Life ... should be End Of Line
Explanation:
This relates to the fact that windows OS uses 2 characters as the "end of a line", while unix uses only 1 character.
Windows uses CR+LF - Carriage Return and Line Feed --- like and old manual typewriter it places the "Carriage" back to it's starting position on the next line, while unix uses only the LF character.
When transferring a text file (Binary) from unix to Windows, then open in Notepad - you apparently see no "linebreaks" and it might look messy.
When transferring a file from Windows to unix, you see the ^M (CR) character visible ... which several programs will take as an invalid special character...
One method to avoid this is to use "ASCII transfer" for text files - which often will identify this and adjust EOL to your OS. *)
If you've got a file with ^M characters on unix and want to get rid of this character, you can easily do this like this (using unix tr command)
cat mywindowsfile.txt | tr -d '\r' > myunixfile.txt
*) depending on your transfer program