Re: [newbie] linux-out to lunch
On Sat, 29 Nov 2003 22:35:43 -0500 Mike Adolf [EMAIL PROTECTED] wrote: After I rebooted, it got the same error, THE PERMISSONS WERE SET BACK TO ORIGINAL VALUES!! That's msec in action: http://www.mandrakeuser.org/docs/secure/smsec.html Linux isn't out to lunch, it's protecting you from yourself. Having the perms 777 is inherantly dangerous, the degree of danger depending on your security setup and situation. -- JoeHill ++ ICQ # 280779813 Registered Linux user #282046 Homepage: www.orderinchaos.org +++ The philosophers have only interpreted the world in various ways. The point, however, is to change it.-- Karl Marx Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] linux-out to lunch
On Sat, 29 Nov 2003 22:35:43 -0500 Mike Adolf [EMAIL PROTECTED] wrote: I added a second user using userdrake. When I tried to logon to the new account. I get No Write Permission on HOME KDE can't start. SO, although the new home has the same permissions as my home, I change the permission to 777 on new HOME. Tried to log on again (without rebooting), and it worked. I thought, OK problem solved. Wrong! After I rebooted, it got the same error, THE PERMISSONS WERE SET BACK TO ORIGINAL VALUES!! I repeated the chmod again just to make sure I wasn't nuts. I wasn't. I opened userdrake and it had the userid = 500 and groupid = 500. BUT doing an ls -l on /home shows that the new home has user and group both 502 BTW, were the two usernames the same? I've never tried to create two users with the same name, I'm not sure how the system would react with that. I've certainly never run into this problem creating a new user with a *different* name before. -- JoeHill ++ ICQ # 280779813 Registered Linux user #282046 Homepage: www.orderinchaos.org +++ Behind every great fortune is a crime. -- Balzac Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] linux-out to lunch
On Sunday 30 Nov 2003 12:28 pm, JoeHill wrote: On Sat, 29 Nov 2003 22:35:43 -0500 Mike Adolf [EMAIL PROTECTED] wrote: I added a second user using userdrake. When I tried to logon to the new account. I get No Write Permission on HOME KDE can't start. SO, although the new home has the same permissions as my home, I change the permission to 777 on new HOME. Tried to log on again (without rebooting), and it worked. I thought, OK problem solved. Wrong! After I rebooted, it got the same error, THE PERMISSONS WERE SET BACK TO ORIGINAL VALUES!! I repeated the chmod again just to make sure I wasn't nuts. I wasn't. I opened userdrake and it had the userid = 500 and groupid = 500. BUT doing an ls -l on /home shows that the new home has user and group both 502 BTW, were the two usernames the same? I've never tried to create two users with the same name, I'm not sure how the system would react with that. I've certainly never run into this problem creating a new user with a *different* name before. I'm coming in a bit late here, but can I assume the Original Poster reinstalled their system without reformatting their /home? When you do that it is important to add the users in precisely the same order or else the user will have a different UID/GID and will not own their own home directory. The installer will add users beginning with UID 501, but userdrake will add a user starting from UID 500 The solution is not to change the perms to 777, but to change the UID/GID on all the folders in /home derek -- -- www.jennings.homelinux.net http://twiki.mdklinuxfaq.org Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] linux-out to lunch
On Sunday 30 November 2003 08:08 am, Derek Jennings wrote: On Sunday 30 Nov 2003 12:28 pm, JoeHill wrote: On Sat, 29 Nov 2003 22:35:43 -0500 Mike Adolf [EMAIL PROTECTED] wrote: I added a second user using userdrake. When I tried to logon to the new account. I get No Write Permission on HOME KDE can't start. SO, although the new home has the same permissions as my home, I change the permission to 777 on new HOME. Tried to log on again (without rebooting), and it worked. I thought, OK problem solved. Wrong! After I rebooted, it got the same error, THE PERMISSONS WERE SET BACK TO ORIGINAL VALUES!! I repeated the chmod again just to make sure I wasn't nuts. I wasn't. I opened userdrake and it had the userid = 500 and groupid = 500. BUT doing an ls -l on /home shows that the new home has user and group both 502 BTW, were the two usernames the same? I've never tried to create two users with the same name, I'm not sure how the system would react with that. I've certainly never run into this problem creating a new user with a *different* name before. I'm coming in a bit late here, but can I assume the Original Poster reinstalled their system without reformatting their /home? When you do that it is important to add the users in precisely the same order or else the user will have a different UID/GID and will not own their own home directory. The installer will add users beginning with UID 501, but userdrake will add a user starting from UID 500 The solution is not to change the perms to 777, but to change the UID/GID on all the folders in /home derek derek, You hit the nail on the head! Long, long time ago when I first installed MDK, I set up a second user for my wife. However, she wanted nothing to to with linux. Since then, it was necessary to reinstall linux (no reformatting) and I only created one user. Now that our windows half is down, waiting on a new modem, she thinks linux might me OK for getting her mail. So, I used userdrake to set up a second user by the same original name; and I thought the home directory was just created then. Wrong. It was the old one from before with a UID=502 (as expected since done on an install). Anyway, I just trashed the directory and made a new user using userdrake. It used UID= 500. All is well. I do feel that the different numbering schems should be cleared up in the next release. Thanks, mike Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] linux-out to lunch
On Sunday 30 November 2003 04:25 am, JoeHill wrote: On Sat, 29 Nov 2003 22:35:43 -0500 Mike Adolf [EMAIL PROTECTED] wrote: After I rebooted, it got the same error, THE PERMISSONS WERE SET BACK TO ORIGINAL VALUES!! That's msec in action: http://www.mandrakeuser.org/docs/secure/smsec.html Linux isn't out to lunch, it's protecting you from yourself. Having the perms 777 is inherantly dangerous, the degree of danger depending on your security setup and situation. True, but sometimes you may want a directory with perms 777(NOT your /home though--ever). The problem is, msec, in its wisdom, and with its mission to protect you from yourself, will reset the permissions. If you know what you are doing, and actually want these permissions you can either edit a perms.local file, or turn off msec. How do you turn off msec? Actually, the easiest way is to go to /usr/sbin/msec and rename the executable to DISABLEmsec. Presto! msec will not change permissions again. And, to re-enable the little sucker, just rename the executable back to msec. I am no fan of msec, obviously. erylon Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] linux-out to lunch
On Sunday 30 November 2003 19:29, E. Hines wrote: On Sunday 30 November 2003 04:25 am, JoeHill wrote: On Sat, 29 Nov 2003 22:35:43 -0500 Mike Adolf [EMAIL PROTECTED] wrote: After I rebooted, it got the same error, THE PERMISSONS WERE SET BACK TO ORIGINAL VALUES!! That's msec in action: http://www.mandrakeuser.org/docs/secure/smsec.html Linux isn't out to lunch, it's protecting you from yourself. Having the perms 777 is inherantly dangerous, the degree of danger depending on your security setup and situation. True, but sometimes you may want a directory with perms 777(NOT your /home though--ever). The problem is, msec, in its wisdom, and with its mission to protect you from yourself, will reset the permissions. If you know what you are doing, and actually want these permissions you can either edit a perms.local file, or turn off msec. How do you turn off msec? Actually, the easiest way is to go to /usr/sbin/msec and rename the executable to DISABLEmsec. Presto! msec will not change permissions again. And, to re-enable the little sucker, just rename the executable back to msec. I am no fan of msec, obviously. erylon On the other hand, msec is very handy when having multiple users on the same system, say a whole family, and you want every member to have a little privacy. Setting msec to high will accomplish this. Then again, it is often practical to have a partition in common. For example family photo albums etc.. Or for those people who still dual-boot with another OS it is a convenience to have a FAT32 partition around. Now, instead of messing around with permissions like 777, which msec in high position will change soon, it is much easier to edit the fstab with the option : umask=0. Of course, that's only valid for a partition, not a directory. HTH Kaj Haulrich. -- ** Sent from a 100 % Microsoft-free computer ** Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] linux-out to lunch
Mike Adolf wrote: On Sunday 30 November 2003 08:08 am, Derek Jennings wrote: On Sunday 30 Nov 2003 12:28 pm, JoeHill wrote: On Sat, 29 Nov 2003 22:35:43 -0500 Mike Adolf [EMAIL PROTECTED] wrote: I added a second user using userdrake. When I tried to logon to the new account. I get No Write Permission on HOME KDE can't start. SO, although the new home has the same permissions as my home, I change the permission to 777 on new HOME. Tried to log on again (without rebooting), and it worked. I thought, OK problem solved. Wrong! After I rebooted, it got the same error, THE PERMISSONS WERE SET BACK TO ORIGINAL VALUES!! I repeated the chmod again just to make sure I wasn't nuts. I wasn't. I opened userdrake and it had the userid = 500 and groupid = 500. BUT doing an ls -l on /home shows that the new home has user and group both 502 BTW, were the two usernames the same? I've never tried to create two users with the same name, I'm not sure how the system would react with that. I've certainly never run into this problem creating a new user with a *different* name before. I'm coming in a bit late here, but can I assume the Original Poster reinstalled their system without reformatting their /home? When you do that it is important to add the users in precisely the same order or else the user will have a different UID/GID and will not own their own home directory. The installer will add users beginning with UID 501, but userdrake will add a user starting from UID 500 The solution is not to change the perms to 777, but to change the UID/GID on all the folders in /home derek derek, You hit the nail on the head! Long, long time ago when I first installed MDK, I set up a second user for my wife. However, she wanted nothing to to with linux. Since then, it was necessary to reinstall linux (no reformatting) and I only created one user. Now that our windows half is down, waiting on a new modem, she thinks linux might me OK for getting her mail. So, I used userdrake to set up a second user by the same original name; and I thought the home directory was just created then. Wrong. It was the old one from before with a UID=502 (as expected since done on an install). Anyway, I just trashed the directory and made a new user using userdrake. It used UID= 500. All is well. I do feel that the different numbering schems should be cleared up in the next release. In similar situations, I've found something like chown -R fred /home/fred to work. In fact, if you're dealing with lots of users, you could probably write a script to do it automatically. Sir Robin -- Certitude is possible for those who only own one encyclopedia. - Robert Anton Wilson Robin Turner IDMYO Bilkent Univeritesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] linux-out to lunch
On Sun, 30 Nov 2003 02:35 pm, many eyes noted that Mike Adolf wrote: Sometimes linux looses it. I added a second user using userdrake. When I tried to logon to the new account. I get No Write Permission on HOME KDE can't start. SO, although the new home has the same permissions as my home, I change the permission to 777 on new HOME. Tried to log on again (without rebooting), and it worked. I thought, OK problem solved. Wrong! After I rebooted, it got the same error, THE PERMISSONS WERE SET BACK TO ORIGINAL VALUES!! I repeated the chmod again just to make sure I wasn't nuts. I wasn't. I opened userdrake and it had the userid = 500 and groupid = 500. BUT doing an ls -l on /home shows that the new home has user and group both 502 Linux has almost defeated me! mike. try chown -cv mike: /home/mike or whatever it is supposed to be*** See how that works? Charlie -- And all the loveliest things that there be Come simply, so it seems to me. Edna St. Vincent Millay This email is guaranteed to be wholly Linux Mandrake 9.1, Kmail v1.5 and OpenOffice.org1.1.0 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
