Directory ownership
Greetings, This is my first real useradmin job, :) have a look at the ls output below, I have many users on the system and the all access the pro5 directory, so made it aacessable to users, and all users are mebers of the users group. Who must the pro5 folder be owned by as it can't be owned by any of the users because they must all be have read write and execute rights to it? drwxr-xr-x 9 ngn users 840 Sep 9 2004 ngn drwxr-xr-x 18 ngolfnet users 1120 Jun 10 10:00 ngolfnet drwx------ 9 payroll users 736 Jun 10 10:00 payroll drwx------ 9 pos users 736 Jun 10 10:00 pos drwxrxr-x 10 700 users 1608 Feb 3 02:56 pro5 -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On Friday 10 June 2005 09:04, Chadley Wilson wrote:
Greetings,
This is my first real useradmin job, :)
have a look at the ls output below, I have many users on the system and the all access the pro5 directory, so made it aacessable to users, and all users are mebers of the users group. Who must the pro5 folder be owned by as it can't be owned by any of the users because they must all be have read write and execute rights to it?
drwxr-xr-x 9 ngn users 840 Sep 9 2004 ngn drwxr-xr-x 18 ngolfnet users 1120 Jun 10 10:00 ngolfnet drwx------ 9 payroll users 736 Jun 10 10:00 payroll drwx------ 9 pos users 736 Jun 10 10:00 pos drwxrxr-x 10 700 users 1608 Feb 3 02:56 pro5
Should be drwxrwxr-x How do users access the directory? With samba, or with NFS? For samba, have this in smb.conf inherit permissions = yes
On Fri, 2005-06-10 at 09:26 +0300, Silviu Marin-Caea wrote:
On Friday 10 June 2005 09:04, Chadley Wilson wrote:
Greetings,
This is my first real useradmin job, :)
have a look at the ls output below, I have many users on the system and the all access the pro5 directory, so made it aacessable to users, and all users are mebers of the users group. Who must the pro5 folder be owned by as it can't be owned by any of the users because they must all be have read write and execute rights to it?
drwxr-xr-x 9 ngn users 840 Sep 9 2004 ngn drwxr-xr-x 18 ngolfnet users 1120 Jun 10 10:00 ngolfnet drwx------ 9 payroll users 736 Jun 10 10:00 payroll drwx------ 9 pos users 736 Jun 10 10:00 pos drwxrxr-x 10 700 users 1608 Feb 3 02:56 pro5
Should be drwxrwxr-x
How do users access the directory? With samba, or with NFS?
For samba, have this in smb.conf inherit permissions = yes
No actually they access from thinclient through the network. They login with their own user names, and in the home folders are customised profiles, -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On Friday 10 June 2005 09:59, Chadley Wilson wrote:
drwxrxr-x 10 700 users 1608 Feb 3 02:56 pro5
Should be drwxrwxr-x
No actually they access from thinclient through the network. They login with their own user names, and in the home folders are customised profiles,
Then, probably your problem is the default umask. Ie, users create files with these rights: rwxr-xr-x And you'd like rwxrwxr-x Edit /etc/profile and replace "umask 022" with 002
Thanks Sorted nicely just made ngn owner as it doesn't matter anymore who own it. On Fri, 2005-06-10 at 10:35 +0300, Silviu Marin-Caea wrote:
On Friday 10 June 2005 09:59, Chadley Wilson wrote:
drwxrxr-x 10 700 users 1608 Feb 3 02:56 pro5
Should be drwxrwxr-x
No actually they access from thinclient through the network. They login with their own user names, and in the home folders are customised profiles,
Then, probably your problem is the default umask. Ie, users create files with these rights:
rwxr-xr-x
And you'd like
rwxrwxr-x
Edit /etc/profile and replace "umask 022" with 002
-- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On Fri, 2005-06-10 at 10:35 +0300, Silviu Marin-Caea wrote:
On Friday 10 June 2005 09:59, Chadley Wilson wrote:
drwxrxr-x 10 700 users 1608 Feb 3 02:56 pro5
Should be drwxrwxr-x
No actually they access from thinclient through the network. They login with their own user names, and in the home folders are customised profiles,
Then, probably your problem is the default umask. Ie, users create files with these rights:
rwxr-xr-x
And you'd like
rwxrwxr-x
Edit /etc/profile and replace "umask 022" with 002
Changing umask will not change ownership and you may not want this to apply to files in their home dir. You can set the perms for the dir with 6770 which will set the sticky bit for the owner and group and should make all new files created have the owner/group the same as the parent dir. Perhaps a change of the umask with setting the sticky bit would be best. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Friday 10 June 2005 14:29, Ken Schneider wrote:
Changing umask will not change ownership and you may not want this to apply to files in their home dir. You can set the perms for the dir with 6770 which will set the sticky bit for the owner and group and should make all new files created have the owner/group the same as the parent dir. Perhaps a change of the umask with setting the sticky bit would be best.
Yes, all this. I have only replied with the exact solution to his particular problem. Some reading required for more generic stuff.. :-)
On Fri, 2005-06-10 at 14:47 +0300, Silviu Marin-Caea wrote:
On Friday 10 June 2005 14:29, Ken Schneider wrote:
Changing umask will not change ownership and you may not want this to apply to files in their home dir. You can set the perms for the dir with 6770 which will set the sticky bit for the owner and group and should make all new files created have the owner/group the same as the parent dir. Perhaps a change of the umask with setting the sticky bit would be best.
Yes, all this.
I have only replied with the exact solution to his particular problem. Some reading required for more generic stuff.. :-)
Great all these things are certainly helping me, I would rather have 10 different options and find the one that works best, than sit with two that are not right for my situation. Thank you all so much for all the input, it really helps. -- Chadley Wilson Redhat Certified Technician Cert Number: 603004708291270 Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
On Fri, 2005-06-10 at 08:04 +0200, Chadley Wilson wrote:
Greetings,
This is my first real useradmin job, :)
have a look at the ls output below, I have many users on the system and the all access the pro5 directory, so made it assessable to users, and all users are members of the users group. Who must the pro5 folder be owned by as it can't be owned by any of the users because they must all be have read write and execute rights to it?
drwxr-xr-x 9 ngn users 840 Sep 9 2004 ngn drwxr-xr-x 18 ngolfnet users 1120 Jun 10 10:00 ngolfnet drwx------ 9 payroll users 736 Jun 10 10:00 payroll drwx------ 9 pos users 736 Jun 10 10:00 pos drwxrxr-x 10 700 users 1608 Feb 3 02:56 pro5
Since every new user on SuSE linux belongs to the users group you may want to pick something different. Change the perms to 770 to restrict access to the owner and group members. You can also look into using extended perms, ACL's, for granting access as well. If only someone will come up with a GUI for ACL's it would sure help the new people. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Chadley Wilson wrote:
Greetings,
This is my first real useradmin job, :)
have a look at the ls output below, I have many users on the system and the all access the pro5 directory, so made it aacessable to users, and all users are mebers of the users group. Who must the pro5 folder be owned by as it can't be owned by any of the users because they must all be have read write and execute rights to it?
drwxr-xr-x 9 ngn users 840 Sep 9 2004 ngn drwxr-xr-x 18 ngolfnet users 1120 Jun 10 10:00 ngolfnet drwx------ 9 payroll users 736 Jun 10 10:00 payroll drwx------ 9 pos users 736 Jun 10 10:00 pos drwxrxr-x 10 700 users 1608 Feb 3 02:56 pro5
So long as the group rights are suitable, the directory can be owned by anyone. That "anyone" doesn't even have to be a real user. However, since it doesn't appear that you want most users to access payroll or pos, you might want to change the owner of them.
When installing SuSE 9.3 on a system that has an ALI15x chipset, and then moving the harddisk to another system, that uses a via chipset, it will not boot (can't find the harddisk). The correct driver is present in SuSE 9.3, as I can boot from the SuSE cd/dvd. How do I make it load the via chipset module/driver, and not just give up because the ali chipset is no longer present. Thanks in advance Bo
On Fri, 2005-06-10 at 15:23 +0200, Bo Jacobsen wrote:
When installing SuSE 9.3 on a system that has an ALI15x chipset, and then moving the harddisk to another system, that uses a via chipset, it will not boot (can't find the harddisk). The correct driver is present in SuSE 9.3, as I can boot from the SuSE cd/dvd.
How do I make it load the via chipset module/driver, and not just give up because the ali chipset is no longer present.
Thanks in advance Bo
Boot to the rescue DVD/CD mount the drive to /mnt-tmp can be anything, your choice chroot to mount point If you have /boot on a seperate part. mount it vi /etc/sysconfig/kernel Modify INITRD_MODULES="" to include the correct module. run mkinitrd to rebuild /boot/initrd(your kernel) umount /boot if it was booted earlier cntr d to exit chroot The system should now boot using the correct module to access the disk. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
It worked as described. Thanks. /Bo
participants (5)
-
Bo Jacobsen -
Chadley Wilson -
James Knott -
Ken Schneider -
Silviu Marin-Caea