chown troubles
I'm not sure what I'm doing wrong here. My goal is to make sure I have ownership of the directory, /home/tom/.kde/share/apps/amarok.
So that I wouldn't have to type out that long path, I used cd to get to the directory: /home/tom/.kde/share/apps/ I figured the rest would be simple, but I must be doing something wrong. Here's a cut'n'paste of what I did: Code:
tom@toms-jukebox:~/.kde/share/apps$ ls Code:
tom@toms-jukebox:~/.kde/share/apps$ sudo chown -R tom: amarok Code:
tom@toms-jukebox:~/.kde/share/apps/amarok$ sudo chown -R tom. collection.db |
Instead of using sudo I would:
Code:
su - sometimes if sudo is not set up right it can cause weird problems so I don't use it unless I set it up for a specific thing. most likely however the problem is that colon. what gave you the Idea to put that in there? try it like this: Code:
chown -R tom folder/ |
Don't ignore problems that are staring you in the face:
Code:
sudo: unable to resolve host toms-jukebox Code:
127.0.0.1 toms-jukebox Code:
sudo chown tom: amarok # Correct, but don't need : after owner (chown tom amarok) Code:
sudo chown -R tom amarok |
The help here is greatly appreciated. The problem is solved.
|
Mr. C,
I'm just curious; why would chown try to look up the hostname? as far as I know it has nothing to do with the network at all. I never set hostnames on my network I always just use static IP addresses. all hosts are called localhost and I've never encountered such an error unless I try to substitute a hostname for an IP like with ping. |
Chown doesn't, sudo does. Sudo can be configured to allow privilege elevation for only certain clients (or users, or groups, ...).
Therefore, it looks up your hostname and IP. The first clue to any command's errors when launched by the shell is the first part: Code:
sudo: unable to resolve host toms-jukebox |
All times are GMT -5. The time now is 04:00 AM. |