corrected line endings (LF)

[cfoellmann]

This changes the line endings (from CR+LF to LF) of files connected to the guest cmd.
There are still some files like my.cnf that have Windows line endings which is not breaking anything but is not good either.

My tests show that this change results in
FIX Close #430
FIX Close #419
FIX Close #358
Improves #413

[jeremyfelt]

@cfoellmann Is there any chance that #367 would solve this on a local level rather than in the repo? I'm no good with line endings :)

Also - I think the permissions on these files are best left at 0755, it looks like they got changed to 0644 in the commit.

[cfoellmann]

I tested #367. If it worked all the non-LF files should pop up as changed after the .gitattribute change.
Is this really the permission? I don't see how that is possible.
Yes, its possible. Will change that.

[cfoellmann]

#367 is working after all. This whole issue is because Git on Win just decides to use its own line endings for whatever reason because it has to decide (auto). When I download the zip via GitHub the files have the right line endings 👿

For me it only works when I clone the remote again with the new .gitattribute. Git on Win does not recognize the rule change.

[cfoellmann]

#430 seems to be working as good as this.
Just please get this in soon. It is really a pain for all windows users

[jeremyfelt]

Cool, this is good to know. I think merging #367 may be the right answer. I was hesitant at first because I'm not sure if changing the line endings on all the files was a big deal, but it may be ok.

I'm going to leave this open for now, but merge #367. @cfoellmann, thanks for all your testing!

[cfoellmann]

Yes. Merge that one. Since all the files "run" on a Linux host within the vm LF should be the way to go in the first place.
There are no files being changed by this gitattribute change. It is git on windows that decides to check these files out with the wrong line endings.

[jeremyfelt]

Closing this out, thanks for the work on this, @cfoellmann!