<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:rgb(51,0,51)">Depending on which distro you have and what packages are installed, there's a handy dandy little pair of utilities for working with these differences between "dos" and "unix" machines. Not surprisingly, the pair of utilities are called "dos2unix" and "unix2dos" - and it deals with the ^M you see when you bring a dos-edited package over to Linux/UNIX, and similarly, it puts the ^L in with the ^M to make it not all run together as one long line when you bring a file written on UNIX/Linux over to Dos.<br><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:rgb(51,0,51)">Usage is pretty much as you'd expect:<br><br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:rgb(51,0,51)">dos2unix original.txt > outputfile<br></div><div class="gmail_default" style="font-family:verdana,sans-serif;font-size:small;color:rgb(51,0,51)"><br>and so forth.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 13, 2015 at 2:18 PM, Scott Merrill <span dir="ltr"><<a href="mailto:skippy@skippy.net" target="_blank">skippy@skippy.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On May 13, 2015, at 2:12 PM, Steve VanSlyck <<a href="mailto:s.vanslyck@postpro.net">s.vanslyck@postpro.net</a>> wrote:<br>
><br>
> Umpf.<br>
><br>
> Yes, I have seen it before, now you mention it. Seems my old windows machines always started with PATH=.;... Or at least I seem to remember it that way. Regardless, I always *assumed* the computer always looked in the current directory first.<br>
><br>
> Anyway, as you saw in previous email i am now getting this<br>
> [root@vslaw2 ~]# ./server_setup.sh<br>
> -bash: ./server_setup.sh: /bin/bash^M: bad interpreter: No such file or directory<br>
> error.<br>
><br>
> No idea what the ^M means. I don't see anything when looking at the file in nano and confirmed it with VI/VIM just to be sure, with same result<br>
><br>
<br>
</span>You’re running into one of the frustrating differences between Windows and UNIX (and Mac!) systems.<br>
<br>
<a href="http://www.cs.toronto.edu/~krueger/csc209h/tut/line-endings.html" target="_blank">http://www.cs.toronto.edu/~krueger/csc209h/tut/line-endings.html</a><br>
<br>
<a href="https://en.wikipedia.org/wiki/Newline" target="_blank">https://en.wikipedia.org/wiki/Newline</a><br>
<br>
If you’re editing files on Windows and then transferring them over to Linux, you’ll likely keep having this problem. There are several solutions.<br>
<br>
You can use a text editor that understands different line endings. The default Windows Notepad application *does not* understand anything other than Windows line endings.<br>
<br>
You can use a tool called `dos2unix` on your Linux systems to convert Windows line endings to UNIX line endings.<br>
<br>
Cheers,<br>
Scott<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</div></div></blockquote></div><br></div>