[deployment-guide/comm-rel: 66/74] UsersGroups: update complete chapter
dsilas
dsilas at fedoraproject.org
Tue Jul 6 21:14:58 UTC 2010
commit 6ff3e332b6d9a344bbf7dd6c4adf5143403cf531
Author: fnadge <fnadge at redhat.com>
Date: Tue Jun 29 14:44:16 2010 +0200
UsersGroups: update complete chapter
en-US/Users_and_Groups.xml | 17 +++++++++--------
en-US/images/Users_Groups-Create_New_User.png | Bin 129307 -> 123723 bytes
en-US/images/group-new.png | Bin 43377 -> 20994 bytes
en-US/images/group-properties.png | Bin 66401 -> 50829 bytes
en-US/images/user_pass_info.png | Bin 15665 -> 45963 bytes
5 files changed, 9 insertions(+), 8 deletions(-)
---
diff --git a/en-US/Users_and_Groups.xml b/en-US/Users_and_Groups.xml
index ac0aa63..6365bb5 100644
--- a/en-US/Users_and_Groups.xml
+++ b/en-US/Users_and_Groups.xml
@@ -33,7 +33,7 @@
<para>A user who creates a file is also the owner and group owner of that file. The file is assigned separate read, write, and execute permissions for the owner, the group, and everyone else. The file owner can be changed only by the root user, and access permissions can be changed by both the root user and file owner.</para>
<para
lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN">
- &MAJOROS; also supports <firstterm>access control lists</firstterm> (<firstterm>ACLs</firstterm>) for files and directories which allow permissions for specific users outside of the owner to be set. For more information about ACLs, refer to <!-- TBD6: <xref linkend="ch-acls" />. -->
+ &MAJOROS; also supports <firstterm>access control lists</firstterm> (<firstterm>ACLs</firstterm>) for files and directories which allow permissions for specific users outside of the owner to be set. For more information about ACLs, refer to chapter<citetitle>ACLS</citetitle>. <!-- TBD6: <xref linkend="ch-acls" />. -->
</para>
<section
id="s1-users-configui">
@@ -105,7 +105,7 @@
</indexterm>
<para>To view a list of local users on the system, click the <guilabel>Users</guilabel> tab. To view a list of local groups on the system, click the <guilabel>Groups</guilabel> tab.</para>
<para>To find a specific user or group, type the first few letters of the name in the <guilabel>Search filter</guilabel> field. Press <keycap>Enter</keycap> or click the <guibutton>Apply filter</guibutton> button. The filtered list is displayed.</para>
- <para>To sort the users or groups, click on the column User Name or Group Name. The users or groups are sorted according to the value of that column.</para>
+ <para>To sort the users, click on the column User Name and for groups click on Group Name. The users or groups are sorted according to the value of that column.</para>
<para>&MAJOROS; reserves user IDs below 500 for system users. By default, the <application>User Manager</application> does not display system users. To view all users, including the system users, go to <guimenuitem>Edit</guimenuitem> > <guimenuitem>Preferences</guimenuitem> and uncheck <guimenuitem>Hide system users and groups</guimenuitem> from the dialog box.</para>
<section
id="s2-redhat-config-users-user-new">
@@ -126,6 +126,7 @@
<para>&MAJOROS; uses a <firstterm>user private group</firstterm> (UPG) scheme. The UPG scheme does not add or change anything in the standard UNIX way of handling groups; it offers a new convention. Whenever you create a new user, by default, a unique group with the same name as the user is created. If you do not want to create this group, unselect <guilabel>Create a private group for the user</guilabel>.</para>
<para>To specify a user ID for the user, select <guibutton>Specify user ID manually</guibutton>. If the option is not selected, the next available user ID above 500 is assigned to the new user. Because &MAJOROS; reserves user IDs below 500 for system users, it is not advisable to manually assign user IDs 1-499.</para>
<para>Click <guibutton>OK</guibutton> to create the user.</para>
+
<figure
id="user-new-fig">
<title>Creating a new user</title>
@@ -245,8 +246,8 @@
<primary>group configuration</primary>
<secondary>adding groups</secondary>
</indexterm>
- <para>To add a new user group, click the <guibutton>Add Group</guibutton> button. A window similar to <xref
- linkend="group-new-fig"/> appears. Type the name of the new group to create. To specify a group ID for the new group, select <guibutton>Specify group ID manually</guibutton> and select the GID. Note that &MAJOROS; also reserves group IDs lower than 500 for system groups.</para>
+ <para>To add a new user group, select <guibutton>Add Group</guibutton> from the toolbar. A window similar to <xref
+ linkend="group-new-fig"/> appears. Type the name of the new group. To specify a group ID for the new group, select <guibutton>Specify group ID manually</guibutton> and select the GID. Note that &MAJOROS; also reserves group IDs lower than 500 for system groups.</para>
<figure
float="0"
id="group-new-fig">
@@ -332,7 +333,7 @@
<command>groupadd</command>
</tertiary>
</indexterm>
- <para>Managing users and groups can be a tedious task; this is why &MAJOROS; provides tools and conventions to make them easier to manage.</para>
+ <para>Managing users and groups can be tiresome; this is why &MAJOROS; provides tools and conventions to make this task easier to manage.</para>
<para>The easiest way to manage users and groups is through the graphical application, <application>User Manager</application> (<command>system-config-users</command>). For more information on <application>User Manager</application>, refer to <xref
linkend="s1-users-configui"/>.</para>
<para>The following command line tools can also be used to manage users and groups:</para>
@@ -2517,8 +2518,8 @@ crypt.crypt("<replaceable><password></replaceable>","<replaceable><salt
<primary>user private groups</primary>
<secondary>and shared directories</secondary>
</indexterm>
- <para>Many IT organizations like to create a group for each major project and then assign people to the group if they need to access that project's files. Using this traditional scheme, managing files has been difficult; when someone creates a file, it is associated with the primary group to which they belong. When a single person works on multiple projects, it is difficult to associate the right files with the right group. Using the UPG scheme, however, groups are automatically assigned to files created within a directory with the <firstterm>setgid</firstterm> bit set. The setgid bit makes managing group projects that share a common directory very simple because any files a user creates within the directory are owned by the group which owns the directory.</para>
- <para>Let us say, for example, that a group of people need to work on files in the <filename>/usr/share/emacs/site-lisp/</filename> directory. Some people are trusted to modify the directory, but certainly not everyone is trusted. First create an <computeroutput>emacs</computeroutput> group, as in the following command:</para>
+ <para>System administrators usually like to create a group for each major project and assign people to the group when they need to access that project's files. With this traditional scheme, file managing is difficult; when someone creates a file, it is associated with the primary group to which they belong. When a single person works on multiple projects, it becomes difficult to associate the right files with the right group. However, with the UPG scheme, groups are automatically assigned to files created within a directory with the <firstterm>setgid</firstterm> bit set. The setgid bit makes managing group projects that share a common directory very simple because any files a user creates within the directory are owned by the group which owns the directory.</para>
+ <para>For example, a group of people need to work on files in the <filename>/usr/share/emacs/site-lisp/</filename> directory. Some people are trusted to modify the directory, but not everyone. First create an <computeroutput>emacs</computeroutput> group, as in the following command:</para>
<screen>
<command>/usr/sbin/groupadd emacs</command>
</screen>
@@ -2527,7 +2528,7 @@ crypt.crypt("<replaceable><password></replaceable>","<replaceable><salt
<command>chown -R root.emacs <filename>/usr/share/emacs/site-lisp</filename>
</command>
</screen>
- <para>Now, it is possible to add the proper users to the group with the <command>gpasswd</command> command:</para>
+ <para>Now, it is possible to add the right users to the group with the <command>gpasswd</command> command:</para>
<screen>
<command>/usr/bin/gpasswd -a <replaceable><username></replaceable> emacs</command>
</screen>
diff --git a/en-US/images/Users_Groups-Create_New_User.png b/en-US/images/Users_Groups-Create_New_User.png
index b38f7b3..8b8a6c1 100644
Binary files a/en-US/images/Users_Groups-Create_New_User.png and b/en-US/images/Users_Groups-Create_New_User.png differ
diff --git a/en-US/images/group-new.png b/en-US/images/group-new.png
index 61eb0c3..a9ad250 100644
Binary files a/en-US/images/group-new.png and b/en-US/images/group-new.png differ
diff --git a/en-US/images/group-properties.png b/en-US/images/group-properties.png
index 36b0541..2fd40e4 100644
Binary files a/en-US/images/group-properties.png and b/en-US/images/group-properties.png differ
diff --git a/en-US/images/user_pass_info.png b/en-US/images/user_pass_info.png
index c6414bb..5eaedfe 100644
Binary files a/en-US/images/user_pass_info.png and b/en-US/images/user_pass_info.png differ
More information about the docs-commits
mailing list