comp.at.my.domain:/dxs/users2/research/X /home/X nfs rw,addr=xxx.xxx.xxx.xxx 0 0
That looks like you are using nfs
to mount the remote directory.
I'll bet that the remote computer does not have the no_root_squash
option in /etc/exports
. (And as enabling this is a security risk, it is unlikely they'll put it in for you!). Basically, this means that you cannot have your own root's rights apply to the remote files, only local ones.
There is a workaround though. You may have the same username on both computers, but it is quite likely that the UID
's of those usernames are different. This is what is giving you permissions problems, as permissions go by the UID's and GID's, not the names associated with them. To find what your UID is do a grep username /etc/passwd
, you'll get something like this:
grep tredegar /etc/passwd
My UID is the first "501".
Also, of you look at the remote systems nfs mounted files with konqueror (Make sure you have View->Details->Show Owner selected), or do a ls -l
and you may not see your username as the "owner" - maybe just a number in the "owner" column - this is your UID on the remote system, which probably doesn't correspond with any user on your local system.
You need to find out what your UID is on the remote computer, and then create a user on your computer with the same uid
as your username on the remote computer. Then you will be able to access your files as if they were your own (which they are).
You need to assign yourself (locally) to a group that has the same GID as a group you belong to on the other computer, and fiddle about with group permissions on the remote computer (you'll probably need to be logged in to it to do this - either go there in person, or maybe you can get into your account with ssh
). This may be more painful.
I hope I have explained this OK. Also, I hope I know what I am talking about!
Re-reading your original post, I realsie that you already have access to your files, as yourself.
So, not being able to do things as root on the remote filesystem is normal behaviour (because of the no_root_squash non-option). If you want to be root on the remote system, you'll have to ssh there and
know the root password.