To make a long story short, (trying to install lightscribe), It has installed to computer>opt>lightscribe>simple labeler> (launchbrowser.sh), which is a root folder. I am trying to open a terminal and cd to the folder so I can take ownership so I can run the program. However every time I try the cd command I get the error msg "user/HOME/computer does not exist". How do i do this, or is there a better way of accessing this program, I really don't want to have to reboot into windows every day just to burn a few disk. I have seen several forum post where other people were having problems and eventually got it working, and I tried what they did and it did not work for me.
Firstly, I'm not sure what you mean by "user/HOME/computer does not exist". I figure out what you're calling "computer" is the root directory, which under Linux is denoted with a slash character
And notice how the pathname begins with a
... or by quoting the whole pathname:
Now secondly, I don't really think you need to take the ownership of a program in order to run it. Almost all programs we install are installed somewhere under the root folder, owned by the root user -- not in normal users' home directories, and not owned by them.
Whether the program's main binary is under somewhere like
That all being said, since you can browse there, then the problem is just mistyping the path in the terminal. The tips above should suffice to typing it correctly, I think. And keep in mind that pathnames under Linux are case-sensitive. You can't type
Finally, and to make life easier, I think any file manager you might be using should have an "Open terminal here" command so that you don't have to separately open a terminal and manually
Hope this helps. (Edit: I'm slowpoke, people already answered.)
Error messages are usually trying to tell you something. If the folder exists but you don't have permission to view/execute it, the error will say so. So your first problem is to figure out what directory you should be launching from.
Then, if you have permission to run the script running it from the command line should work fine:
Or, it will give you a new, different, equally useful error to work from.