Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mac OS X Leopard 10.6.2, Windows 2003 Server/Vista/7/XP/2000/NT/98, Ubuntux64, CentOS4.8/5.4
Posts: 2,986
Rep:
How to give permission to /home partition
I did an installation of Mandriva 10.2 and saved my /home partition before upgrading. Mandriva notices that there is a /home partition, but I am unable to read or write to it because it says that I do not have permission to write to that /home partition. I've had this happen before when I upgraded to Mandrake 9.2 and I can't find my thread anymore. I have to do something funky like chmod ### something or chown ### something.
A few years ago when switching distros I had a similar problem. It turned out that the old distro had assigned my user uid:gid as 500:500 while the new distro used 501:501. Changing the entry in /etc/passwd fixed it.
A recursive chown may also fix the problem, but there may be files in there that have been setup for another group such as "audio" to access.
Distribution: Mac OS X Leopard 10.6.2, Windows 2003 Server/Vista/7/XP/2000/NT/98, Ubuntux64, CentOS4.8/5.4
Posts: 2,986
Original Poster
Rep:
Quote:
Originally posted by camelrider A few years ago when switching distros I had a similar problem. It turned out that the old distro had assigned my user uid:gid as 500:500 while the new distro used 501:501. Changing the entry in /etc/passwd fixed it.
A recursive chown may also fix the problem, but there may be files in there that have been setup for another group such as "audio" to access.
Camel - how do you figure out what your old uid:gid was? My current one now is 500:500
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.