Managing users and groups has traditionally been tedious. Red Hat Linux has a few tools and conventions that make user and groups easier to manage, and more useful.

Red Hat Linux uses a user private group (UPG) scheme, which makes UNIX groups much easier to use. The UPG scheme does not add or change anything in the standard UNIX way of handling groups. It simply offers a new convention for handling groups. Whenever you create a new user, by default, he or she has a unique group. The scheme works as follows:

User Private Group

Each user has it's own primary group, to which only it is a member.

umask = 002

The traditional UNIX umask is 022, which prevents other users and other members of a user's primary group from modifying a user's files. Since every user has their own private group in the UPG scheme, this ``group protection'' is not needed. A umask of 002 will prevent users from modifying other users' private files. The umask is set in /etc/profile.

SGID bit on Directories

If you set the SGID bit on a directory (with chmod g+s directory), files created in that directory will have their group set to the directory's group.

Most computing sites like to create a group for each major project and assign people to the groups they need to be in. Managing files traditionally has been difficult, though, because when someone creates a file it is owned by the primary group he or she belongs to. When a single person works on multiple projects, it becomes hard to make the files owned by the group that is associated with that project. In the UPG scheme, groups are automatically assigned to files on a project-by-project basis, which makes managing group projects very simple.

Let's say you have a big project called devel, with many people editing the devel files in a devel directory. Make a group called devel, chgrp the devel directory to devel, and add the all the devel users to the devel group. Now, all the devel users will be able to edit the devel files and create new files in the devel directory, and these files will always retain their devel group. Thus, they will always be edit-able by other devel users.

If you have multiple projects like devel, and users who are working on multiple projects, these users will never have to change their umask or group when they move from project to project. The SGID bit on each project's main directory ``selects'' the proper group.

Since each user's HOME directory is owned by the user and their private group, it is safe to set the SGID bit on the HOME directory. However, by default, files are created with the primary group of the user, so the SGID bit would be redundant.

Since the UPG scheme is new, many people have questions about it, and they wonder why it is necessary. The following is the rationale for the scheme.

• You'd like to have a group of people work on a set of files in say, the
  /usr/lib/emacs/site-lisp directory. You trust a few people to mess around in there, but certainly not everyone.
• So you enter:

  chown -R root.emacs /usr/lib/emacs/site-lisp
  

  and you add the proper users to the group.
• To allow the users to actually create files in the directory you enter:

  chmod 775 /usr/lib/emacs/site-lisp
  

• But when a user creates a new file it is assigned the group of the users default group (usually users). To prevent this you enter

  chmod 2775 /usr/lib/emacs/site-lisp
  

  which causes everything in the directory to be created with the ``emacs'' group.
• But the new file needs to be mode 664 for another user in the emacs group to be able to edit it. To do this you make the default umask 002.
• Well, this all works fine, except that if your default group is ``users'', every file you create in your home directory will be writable by everybody in ``users'' (usually everyone).
• To fix this, you make each user have a ``private group'' as their default group.

At this point, by making the default umask 002 and giving everyone a private default group, you can easily set up groups that users can take advantage of without doing any magic. Just create the group, add the users, and do the above chown and chmod on the group's directories.