You do not have the permissions necessary to view the contents of “data”.
and the same error for the other partition “data 2”
These 2 partitions are made with fedora 12.
Both are ext3 filesistem.
In file browser when i selecte one of these partitions, after it asks for the password the partition disappears from “places”
yorulezkos wrote:
> You do not have the permissions necessary to view the contents of
> “data”.
> and the same error for the other partition “data 2”
> These 2 partitions are made with fedora 12.
>
as you know permissions are tied to user ID, though the word/name you
use as an ID might be the same on both Fedora and openSUSE, both
systems actually use a UID number to track permissions…
you can see yours UID in openSUSE via YaST > Security Users (mine this
second is 1000)
so, you can have the same name on both openSUSE and Fedora but in
actuality have two different numbers, and therefore NOT have permission…
that is if your ID name on Fedora is not associated with the same
UID number you have on openSUSE, you can’t get in…
i think what you can do is associate your name on openSUSE with the
UID used on Fedora, but sorry, i’m not sure how to do that…(dumb
because i stick to one distro at a time)
> yorulezkos wrote:
>> You do not have the permissions necessary to view the contents of
>> “data”.
>> and the same error for the other partition “data 2”
>> These 2 partitions are made with fedora 12.
>>
>
> as you know permissions are tied to user ID, though the word/name you
> use as an ID might be the same on both Fedora and openSUSE, both
> systems actually use a UID number to track permissions…
>
> you can see yours UID in openSUSE via YaST > Security Users (mine this
> second is 1000)
>
> so, you can have the same name on both openSUSE and Fedora but in
> actuality have two different numbers, and therefore NOT have permission…
>
> that is if your ID name on Fedora is not associated with the same
> UID number you have on openSUSE, you can’t get in…
>
> i think what you can do is associate your name on openSUSE with the
> UID used on Fedora, but sorry, i’m not sure how to do that…(dumb
> because i stick to one distro at a time)
I run into this all the time when I try to transfer a DB2 backup between
servers. The default UID, usually 1000 for the first user defined during
installation, is incremented and assigned as the users are created.
Creating additional users in a different order one different servers
usually ends up with the same user on two different servers unable to use
the backup on both machines until you use root privilege to re-assign the
UID on the backup files to the one applicable to the server of the moment.
Using Yast doesn’t seem to work if you use it to change a user’s ID - it
never gets the new UID for all the affected files in the user’s home
directory. I’ve gotten to the point that I keep a script to create the
users when the same person has accounts on multiple machines just to avoid
the issue.
Will Honea wrote:
> Using Yast doesn’t seem to work if you use it to change a user’s ID - it
> never gets the new UID for all the affected files in the user’s home
> directory. I’ve gotten to the point that I keep a script to create the
> users when the same person has accounts on multiple machines just to avoid
> the issue.
> Will Honea wrote:
>> Using Yast doesn’t seem to work if you use it to change a user’s ID - it
>> never gets the new UID for all the affected files in the user’s home
>> directory. I’ve gotten to the point that I keep a script to create the
>> users when the same person has accounts on multiple machines just to
>> avoid the issue.
>
> interesting…i wonder if you have the time to see if there is a bug
> filed against YaST on that, and if not do so??
> <http://en.opensuse.org/Submitting_Bug_Reports>
>
> **
Guilty
I’ve only run into the problem with Yast and changing UID in one
circumstance and that was with the DB2 instance owner so I’m reasonably
certain that the real problem is in the DB2 config files (arcane critters!)
rather than with the permissions in the file system. The other part of
permissions on backup media doing transfers is straight forward and working
as it should. The one filesystem sets ACLs on the files and the two
machines use different UIDs for what should be the same user/group so the
original user/group is unknown to the second machine. I just have to change
them via chown when I hit a strange machine.