[o0sdaq0o]

I am having trouble running the create_hdd_region.sh script. check out the image here to see what happens. I modified the script to echo the command so you can see the parameters. Any ideas? thanx in advance.

image

[xerxesrex]

Originally Posted by o0sdaq0o run this: # cat create_hdd_region.sh | tr -d "\r" > /tmp/create_hdd_region2.sh # . /tmp/create_hdd_region2.sh this will get rid of the return characters in the script (you copied this file from a windows machine didn't you?) then copy the file to /tmp where it will be ran from there.

care to explain the | tr -d "\r" part? something to do with how windows handles the return as the script is written meant for unix?

cheers

[Fido4life]

Hello guys. Yesterday i was trying to install everything, as it was shown in the video above. It was a little creepy because in the middle of the process gitbrew.org became down, and as i can see the site is still not working. Luckily i got downloaded almost all necessary files, before the shutdown only one thing got me in a VERY BIG confusion: wich cfw should i use ? SS patch or without SS patch ?

I would like to play games of course and sometimes search the web on linux (still don'T understand why there is not a native homebrew browser for the ps3, but whatever)

Right now i got the otheros++ cfw WITHOUT SS patch. Petitboot worked finely, altough i couldn't create a hdd region, but i will work on that later.

So please, can someone tell me i am using the right CFW ?

Thanks in advance.

[Fido4life]

Originally Posted by o0sdaq0o run this: # cat create_hdd_region.sh | tr -d "\r" > /tmp/create_hdd_region2.sh # . /tmp/create_hdd_region2.sh this will get rid of the return characters in the script (you copied this file from a windows machine didn't you?) then copy the file to /tmp where it will be ran from there.

You Are Awsome !! Thank you very much, i own you a beer !

[o0sdaq0o]

Originally Posted by Fido4life You Are Awsome !! Thank you very much, i own you a beer !

cool, I love beer, especially when it is cold

Originally Posted by xerxesrex care to explain the | tr -d "\r" part? something to do with how windows handles the return as the script is written meant for unix? cheers

exactly, it appears that copying the file from a windows machine inserts a carriage return as well as a newline (\r\n), and on linux you only have a newline (\n). the command replaces instances of \r\n with just \n.

[xerxesrex]

Originally Posted by o0sdaq0o cool, I love beer, especially when it is cold exactly, it appears that copying the file from a windows machine inserts a carriage return as well as a newline (\r\n), and on linux you only have a newline (\n). the command replaces instances of \r\n with just \n.

got it, both systems handle carriage return differently. thanks for the explanation.