I find the vi on unRAID really weird. It seems to work just like vim which i am used to but is differernt enough to be annoying. The main rason i post though is i find that vi seems to be adding ^M in as line returns.

 

Anyone else seeing this?

I find the vi on unRAID really weird. It seems to work just like vim which i am used to but is differernt enough to be annoying. The main rason i post though is i find that vi seems to be adding ^M in as line returns.

 

Anyone else seeing this?

no

I think I've seen that before when I edited a script on my windows machine and dropped it back in unRAID.  I fixed that by using Notepad++ which can save the file in UNIX format (Select between Windows/UNIX/Mac in the format menu).  If you mean it is simply adding ^M as you edit within vi, I haven't seen that.

yup in vi no where near windows.

 

in fact i just uploaded the go script from the 4.3.3 zip file as a test. It is full of windows ^M carriage returns. No one else sees this... weird.

yup in vi no where near windows.

 

in fact i just uploaded the go script from the 4.3.3 zip file as a test. It is full of windows ^M carriage returns. No one else sees this... weird.

They are there in the original "go" script, vi is not adding them, just showing you they are there.  Tom did that to make it easier for users to edit the script in windows notepad.

 

The "go" script is passed through the "fromdos" filter to remove the CTL-M's before being interpreted as /var/tmp/go in /etc/rc.d/rc.local.

rc.local:# Invoke the 'go' script

rc.local:if [ -f /boot/config/go ]; then

rc.local:  fromdos </boot/config/go >/var/tmp/go

rc.local:  chmod +x /var/tmp/go

rc.local:  /var/tmp/go

 

thanks joe that explains alot.

That explains the issue i've been having as well (using windows for script editing and seeing all kinds of wierdness when it gets to the box)

 

I'll get notepad++ tonight!