![]() ![]() Schluchc alludes to looking at the man page for chmod, do this by running man chmod. readme.txt (./ tells the bash to look in the current directory for the intended command rather that search the $PATH variable). I can now execute this file if I want to by running. If I want to add execute rights to this file I would execute chmod 755 readme.txt and that permissions portion would become rwxr-xr-x. The 9 characters from the right can be split into groups of 3 characters of 'rwx' (read, write, execute). ![]() This shows the permissions for that file. You will notice that the readme.txt file says -rw-r-r- on the left. Perhaps if you provided 'real' information we could provide some troubleshooting commands for you. If you are still having problems you can check the permissions on the file by running ls -l while in the same directory as the ruby script. What are the File Permissions and ACLs present on your ficticious 'folder 'A'. You should never have permission issues there and there wont be a risk of it accessing or modifying anything critical to your OS. Move it to ~/ or a sub directory and execute from there. ~/dvtcolorconvert.rb ~/Themes/ObsidianCode.xccolortheme That said, DON'T DO THIS! If you are running a script on your computer and don't need it to access core components of your operating system (I'm guessing you're not since you are invoking the script on something inside your home directory (~/)), then it should be running from your home directory, ie: ![]() This should allow you to execute almost anything from the command line. The sudo command executes the commands which follow it with 'superuser' or 'root' privileges. Try running sudo /dvtcolorconvert.rb ~/Themes/ObsidianCode.xccolortheme Please read the whole answer before attempting to run with sudo ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |