[deployment-guide/comm-rel: 73/74] Merge branch 'flo'
by dsilas
commit 8e15f0bc01b96f3070444fb405de34e717f50e40
Merge: 6d65476... 7ec256e...
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Tue Jul 6 23:01:19 2010 +0200
Merge branch 'flo'
en-US/Manually_Upgrading_the_Kernel.xml | 82 ++++++++++++++++++-------
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
6 files changed, 69 insertions(+), 30 deletions(-)
---
13 years, 11 months
[deployment-guide/comm-rel: 72/74] Merge branch 'martin'
by dsilas
commit 6d6547662bbe5e78d284905a06fad0ec108d3a1e
Merge: ce97d5f... 87d6fb2...
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Tue Jul 6 23:01:17 2010 +0200
Merge branch 'martin'
en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml | 26 ++++++++++++-------
1 files changed, 16 insertions(+), 10 deletions(-)
---
13 years, 11 months
[deployment-guide/comm-rel: 71/74] Merge branch 'jarek'
by dsilas
commit ce97d5f2d363b35dc6b4dbf6f56b6e0a2221f53b
Merge: 2301129... 40eec0a...
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Tue Jul 6 23:01:15 2010 +0200
Merge branch 'jarek'
en-US/Controlling_Access_to_Services.xml | 31 ++++++++++++++++++++++-------
en-US/Date_and_Time_Configuration.xml | 5 +++-
2 files changed, 27 insertions(+), 9 deletions(-)
---
13 years, 11 months
[deployment-guide/comm-rel: 70/74] gitignore: linkchecker-out.txt
by dsilas
commit 2301129f2113201cf589329eb2fed69030021017
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Tue Jul 6 23:00:09 2010 +0200
gitignore: linkchecker-out.txt
.gitignore | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index daf3114..7bf2203 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@ tmp
var/drafts/NetworkManager.html
.*.swp
\#*
+linkchecker-out.txt
13 years, 11 months
[deployment-guide/comm-rel: 69/74] ABRT: linkchecker: chg to http://www.kerneloops.org/
by dsilas
commit a06034bacc81b1509e84c8b9bd8c96d373cde85d
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Tue Jul 6 18:19:17 2010 +0200
ABRT: linkchecker: chg to http://www.kerneloops.org/
en-US/ABRT.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/ABRT.xml b/en-US/ABRT.xml
index 7e182ff..50da673 100644
--- a/en-US/ABRT.xml
+++ b/en-US/ABRT.xml
@@ -36,7 +36,7 @@
<listitem>
<para>
<package>abrt-addon-kerneloops</package> — this plugin provides support for catching and analyzing <firstterm>kernel oopses</firstterm>, i.e. errors that occur in the kernel and which may or may not result in a kernel panic. Also, the <package>abrt-addon-kerneloops</package> plugin provides a way to send its report to a specified server, such as <ulink
- url="http://kerneloops.org/">kerneloops.org</ulink>.</para>
+ url="http://www.kerneloops.org/">kerneloops.org</ulink>.</para>
</listitem>
<listitem>
<para>
13 years, 11 months
[deployment-guide/comm-rel: 67/74] UpgradeKernel: indexed
by dsilas
commit 7ec256e6cf4eec55db806ee1d074b0972d29031e
Author: fnadge <fnadge(a)redhat.com>
Date: Tue Jun 29 14:45:19 2010 +0200
UpgradeKernel: indexed
en-US/Manually_Upgrading_the_Kernel.xml | 82 ++++++++++++++++++++++--------
1 files changed, 60 insertions(+), 22 deletions(-)
---
diff --git a/en-US/Manually_Upgrading_the_Kernel.xml b/en-US/Manually_Upgrading_the_Kernel.xml
index f5a72e1..eae8798 100644
--- a/en-US/Manually_Upgrading_the_Kernel.xml
+++ b/en-US/Manually_Upgrading_the_Kernel.xml
@@ -7,51 +7,82 @@
<indexterm
significance="normal">
<primary>kernel</primary>
- <secondary>upgrading</secondary>
+ <secondary>upgrading the kernel</secondary>
</indexterm>
<para>The &MAJOROS; kernel is custom-built by the &MAJOROS; kernel team to ensure its integrity and compatibility with supported hardware. Before Red Hat releases a kernel, it must first pass a rigorous set of quality assurance tests.</para>
- <para>&MAJOROS; kernels are packaged in the RPM format so that they are easy to upgrade and verify using the <application>Yum</application> or <application>PackageKit</application> package managers. <application>PackageKit</application> automatically queries the Red Hat Network servers and informs you of packages with available updates, including kernel packages.</para>
+ <para>&MAJOROS; kernels are packaged in the RPM format <indexterm><primary>kernel</primary><secondary>package</secondary></indexterm>
+ <indexterm><primary>kernel</primary><secondary>RPM package</secondary></indexterm>
+ <indexterm><primary>package</primary><secondary>kernel RPM</secondary></indexterm>
+ so that they are easy to upgrade and verify using the <application>Yum</application> or <application>PackageKit</application> package managers. <application>PackageKit</application> automatically queries the Red Hat Network servers and informs you of packages with available updates, including kernel packages.</para>
<para>This chapter is therefore <emphasis>only</emphasis> useful for users who need to manually update a kernel package using the <command>rpm</command> command instead of <command>yum</command>.</para>
<warning>
<title>Use Yum to Install Kernels Whenever Possible</title>
- <para>Whenever possible, use either the <application>Yum</application> or <application>PackageKit</application> package manager to install a new kernel because they always <emphasis>install</emphasis> a new kernel instead of replacing the current one, which could potentially leave your system unable to boot.</para>
+ <para>Whenever possible, use either the <application>Yum</application> or <application>PackageKit</application> package manager <indexterm><primary>kernel</primary><secondary>installing kernel packages</secondary></indexterm>
+ <indexterm><primary>installing the kernel</primary></indexterm> to install a new kernel because they always <emphasis>install</emphasis> a new kernel instead of replacing the current one, which could potentially leave your system unable to boot.</para>
</warning>
<warning>
<title>Important</title>
<para>Building a custom kernel is not supported by the Red Hat Global Services Support team, and therefore is not explored in this manual.</para>
</warning>
- <para>For more information on installing kernel packages with <application>Yum</application>, refer to <xref
+ <para>For more information on installing kernel packages<indexterm><primary>kernel</primary><secondary>installing kernel packages</secondary></indexterm> with <application>Yum</application>, refer to <xref
linkend="sec-Updating_Packages"/>. For information on Red Hat Network, refer to <xref
linkend="ch-rhnetwork"/>.</para>
<section
id="s1-kernel-packages">
<title>Overview of Kernel Packages</title>
- <para>&MAJOROS; contains the following kernel packages:</para>
+ <para>&MAJOROS; contains the following kernel packages: <indexterm><primary>kernel</primary><secondary>kernel packages</secondary></indexterm></para>
<itemizedlist>
<listitem>
<para>
- <package>kernel</package> — Contains the kernel for single, multicore and multiprocessor systems.</para>
+ <package>kernel</package> —
+ <indexterm><primary>kernel package</primary><secondary>kernel</secondary><tertiary>for single,multicore and multiprocessor systems</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel</secondary><tertiary>for single,multicore and multiprocessor systems</tertiary></indexterm>
+ Contains the kernel for single, multicore and multiprocessor systems.</para>
</listitem>
<listitem>
<para>
- <package>kernel-devel</package> — Contains the kernel headers and makefiles sufficient to build modules against the <package>kernel</package> package.</para>
+ <package>kernel-devel</package> —
+ <indexterm><primary>kernel package</primary><secondary>kernel-devel</secondary><tertiary>kernel headers and makefiles</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel-devel</secondary><tertiary>kernel headers and makefiles</tertiary></indexterm>
+ Contains the kernel headers and makefiles sufficient to build modules against the <package>kernel</package> package.</para>
</listitem>
<listitem>
<para>
- <package>kernel-doc</package> — Contains documentation files from the kernel source. Various portions of the Linux kernel and the device drivers shipped with it are documented in these files. Installation of this package provides a reference to the options that can be passed to Linux kernel modules at load time.</para>
+ <package>kernel-doc</package> —
+ <indexterm><primary>kernel package</primary><secondary>kernel-doc</secondary><tertiary>
+ documentation files</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel-doc</secondary><tertiary>
+ documentation files</tertiary></indexterm>
+ documentation files from the kernel source. Various portions of the Linux kernel and the device drivers shipped with it are documented in these files. Installation of this package provides a reference to the options that can be passed to Linux kernel modules at load time.</para>
<para>By default, these files are placed in the <filename>/usr/share/doc/kernel-doc-<replaceable><kernel_version></replaceable>/</filename> directory.</para>
</listitem>
<listitem>
<para>
- <package>kernel-headers</package> — Includes the C header files that specify the interface between the Linux kernel and user-space libraries and programs. The header files define structures and constants that are needed for building most standard programs.</para>
+ <package>kernel-headers</package> —
+ <indexterm><primary>kernel package</primary><secondary>kernel-headers</secondary><tertiary>
+ C header files files</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel-headers</secondary><tertiary>
+ C header files files</tertiary></indexterm>
+ Includes the C header files that specify the interface between the Linux kernel and user-space libraries and programs. The header files define structures and constants that are needed for building most standard programs.</para>
</listitem>
<listitem>
<para>
- <package>kernel-firmware</package> — Contains all of the firmware files that are required by various devices to operate.</para>
+ <package>kernel-firmware</package> —
+ <indexterm><primary>kernel package</primary><secondary>kernel-firmware</secondary><tertiary>
+ firmware files</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>kernel-firmware</secondary><tertiary>
+ firmware files</tertiary></indexterm>
+ Contains all of the firmware files that are required by various devices to operate.</para>
</listitem>
<listitem>
<para>
- <package>perf</package> — Technically a documentation instead of kernel package, <package>perf</package> contains supporting documentation for the perf tool shipped in each kernel image subpackage.</para>
+ <package>perf</package> —
+ <package>kernel-firmware</package> —
+ <indexterm><primary>kernel package</primary><secondary>perf</secondary><tertiary>
+ firmware files</tertiary></indexterm>
+ <indexterm><primary>packages</primary><secondary>perf</secondary><tertiary>
+ firmware files</tertiary></indexterm>
+ Technically a documentation instead of kernel package, <package>perf</package> contains supporting documentation for the perf tool shipped in each kernel image subpackage.</para>
</listitem>
</itemizedlist>
<!-- TBD6: ensure the release notes contain kernel-source pkg build instructions -->
@@ -69,7 +100,12 @@
significance="normal">
<primary>boot media</primary>
</indexterm>
- <para>Before upgrading the kernel, it is recommended that you take some precautionary steps. The first step is to make sure working boot media exists for the system in case a problem occurs. If the boot loader is not configured properly to boot the new kernel, the system cannot be booted into &MAJOROS; without working boot media.</para>
+ <para>Before upgrading the kernel
+ <indexterm><primary>kernel</primary><secondary>upgrading</secondary><tertiary>preparing</tertiary></indexterm>
+ <indexterm><primary>kernel upgrading</primary><secondary>preparing</secondary></indexterm>
+ , it is recommended that you take some precautionary steps. </para>
+ <para>In the first step, make sure working boot media exists
+ <indexterm><primary>kernel</primary><secondary>upgrading</secondary><tertiary>working boot media</tertiary></indexterm>for the system in case a problem occurs. If the boot loader is not configured properly to boot the new kernel, the system cannot be booted into &MAJOROS; without working boot media.</para>
<!--silas: the following instructions for making (USB) boot media are adapted from the RHEL6 beta Installation Guide, "Alternative Method to Make Minimal USB Boot Media" section-->
<para>USB media often comes in the form of flash devices sometimes called <firstterm>pen drives</firstterm>, <firstterm>thumb disks</firstterm>, or <firstterm>keys</firstterm>, or as an externally-connected hard disk device. Almost all media of this type is formatted as a <systemitem
class="filesystem">VFAT</systemitem> file system. You can create bootable USB media on media formatted as <systemitem
@@ -80,7 +116,7 @@
<para>You can transfer a distribution image file or a minimal boot media image file to USB media. Make sure that sufficient free space is available on the device. Around <constant>4 GB</constant> is required for a distribution DVD image, around <constant>700 MB</constant> for a distribution CD image, or around <constant>10 MB</constant> for a minimal boot media image.</para>
<para>You must have a copy of the <filename>boot.iso</filename> file from a &MAJOROS; installation DVD, or installation CD-ROM#1, and you need a USB storage device formatted with the <systemitem
class="filesystem">VFAT</systemitem>
- file system and around <constant>16 MB</constant> of free space. The following procedure will not affect existing files on the USB storage device unless they have the same path names as the files that you copy onto it. To create USB boot media, perform the following commands as the root user:</para>
+ file system and around <constant>16 MB</constant> of free space. The following procedure will not affect existing files on the USB storage device unless they have the same path names as the files that you copy onto it. To create USB boot media, perform the following commands as the root user:</para>
<procedure>
<step>
<para>Install the <application>SYSLINUX</application> bootloader on the USB storage device:</para>
@@ -182,14 +218,14 @@ kernel-headers.x86_64 2.6.32-17.el6 installed
<primary>kernel</primary>
<secondary>downloading</secondary>
</indexterm>
- <para>There are several ways to determine if an updated kernel is available for the system.</para>
+ <para>There are several ways to determine<indexterm><primary>kernel</primary><secondary>upgrade kernel available</secondary></indexterm> if an updated kernel is available for the system.</para>
<itemizedlist>
<listitem>
- <para>Security Errata — Refer to <ulink
+ <para>Security Errata — <indexterm><primary>kernel</primary><secondary>upgrade kernel available</secondary><tertiary>Security Errata</tertiary></indexterm>Refer to <ulink
url="http://www.redhat.com/security/updates/"/> for information on security errata, including kernel upgrades that fix security issues.</para>
</listitem>
<listitem>
- <para>Via Red Hat Network — Download and install the kernel RPM packages. Red Hat Network can download the latest kernel, upgrade the kernel on the system, create an initial RAM disk image if needed, and configure the boot loader to boot the new kernel. For more information, refer to <ulink
+ <para>Via Red Hat Network — <indexterm><primary>kernel</primary><secondary>upgrade kernel available</secondary><tertiary>via Red Hat network</tertiary></indexterm>Download and install the kernel RPM packages. Red Hat Network can download the latest kernel, upgrade the kernel on the system, create an initial RAM disk image if needed, and configure the boot loader to boot the new kernel. For more information, refer to <ulink
url="http://www.redhat.com/docs/manuals/RHNetwork/"> http://www.redhat.com/docs/manuals/RHNetwork/</ulink>.</para>
</listitem>
</itemizedlist>
@@ -201,7 +237,7 @@ kernel-headers.x86_64 2.6.32-17.el6 installed
<section
id="s1-kernel-perform-upgrade">
<title>Performing the Upgrade</title>
- <para>After retrieving all of the necessary packages, it is time to upgrade the existing kernel.</para>
+ <para>After retrieving all of the necessary packages<indexterm><primary>kernel</primary><secondary>performing kernel upgrade</secondary></indexterm>, it is time to upgrade the existing kernel.</para>
<important>
<title>Important</title>
<para>It is strongly recommended that you keep the old kernel in case there are problems with the new kernel.</para>
@@ -217,7 +253,7 @@ kernel-headers.x86_64 2.6.32-17.el6 installed
<title>Verifying the Initial RAM Disk Image</title>
<!--dracut creates an initial image used by the kernel for preloading the block device modules (such as
IDE, SCSI or RAID) which are needed to access the root filesystem.-->
- <para>The job of the initial RAM disk image is to preload the block device modules, such as for IDE, SCSI or RAID, so that the root file system, on which those modules normally reside, can then be accessed and mounted. On &MAJOROSVER; systems, whenever a new kernel is installed using either the <application>Yum</application>, <application>PackageKit</application>, or <application>RPM</application> package manager, the <application>Dracut</application> utility is always called by the installation scripts to create an <firstterm>initramfs</firstterm> (initial RAM disk image).</para>
+ <para>The job of the initial RAM disk image <indexterm><primary>initial RAM disk image</primary><secondary>verifying</secondary></indexterm> is to preload the block device modules, such as for IDE, SCSI or RAID, so that the root file system, on which those modules normally reside, can then be accessed and mounted. On &MAJOROSVER; systems, whenever a new kernel is installed using either the <application>Yum</application>, <application>PackageKit</application>, or <application>RPM</application> package manager, the <application>Dracut</application> utility is always called by the installation scripts to create an <firstterm>initramfs</firstterm> (initial RAM disk image).</para>
<para>On all architectures other than <trademark
class="registered">IBM</trademark> <trademark
class="trade">eServer</trademark> <trademark
@@ -310,14 +346,14 @@ drwxr-xr-x 2 root root 0 May 3 22:34 etc/modprobe.d
</procedure>
<bridgehead
id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i">Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i</bridgehead>
- <para>On IBM eSeries System i machines, the initial RAM disk and kernel files are combined into a single file, which is created with the <command>addRamDisk</command> command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by &OSORG;; thus, it does not need to be executed manually. To verify that it was created, use the command <command>ls -l /boot/</command> to make sure the <filename>/boot/vmlinitrd-<replaceable><kernel_version></replaceable>
+ <para>On IBM eSeries System i machines <indexterm><primary>initial RAM disk image</primary><secondary>verifying</secondary><tertiary>IBM eServer System i</tertiary></indexterm>, the initial RAM disk and kernel files are combined into a single file, which is created with the <command>addRamDisk</command> command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by &OSORG;; thus, it does not need to be executed manually. To verify that it was created, use the command <command>ls -l /boot/</command> to make sure the <filename>/boot/vmlinitrd-<replaceable><kernel_version></replaceable>
</filename> file already exists (the <filename><replaceable><kernel_version></replaceable>
</filename> should match the version of the kernel just installed).</para>
</section>
<section
id="s1-kernel-boot-loader">
<title>Verifying the Boot Loader</title>
- <para>When you install a kernel using <command>rpm</command>, the kernel package creates an entry in the boot loader configuration file for that new kernel. However, <command>rpm</command> does <emphasis>not</emphasis> configure the new kernel to boot as the default kernel. You must do this manually when installing a new kernel with <command>rpm</command>.</para>
+ <para>When you install a kernel using<command>rpm</command>, the kernel package creates an entry in the boot loader configuration file<indexterm><primary>boot loader</primary><secondary>verifying</secondary></indexterm> for that new kernel. However, <command>rpm</command> does <emphasis>not</emphasis> configure the new kernel to boot as the default kernel. You must do this manually when installing a new kernel with <command>rpm</command>.</para>
<!-- TBD6: insert link to Installation Guide -->
<para>It is always recommended to double-check the boot loader configuration file after installing a new kernel with <command>rpm</command> to ensure that the configuration is correct. Otherwise, the system may not be able to boot into &MAJOROS; properly. If this happens, boot the system with the boot media created earlier and re-configure the boot loader.</para>
<para>In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "Refer to" link to jump to the correct instructions for your system.</para>
@@ -409,7 +445,7 @@ drwxr-xr-x 2 root root 0 May 3 22:34 etc/modprobe.d
<section
id="s3-kernel-boot-loader-grub">
<title>Configuring the GRUB Boot Loader</title>
- <para>GRUB's configuration file, <filename>/boot/grub/grub.conf</filename>, contains a few lines with directives, such as <computeroutput>default</computeroutput>, <computeroutput>timeout</computeroutput>, <computeroutput>splashimage</computeroutput> and <computeroutput>hiddenmenu</computeroutput> (the last directive has no argument). The remainder of the file contains 4-line <firstterm>stanzas</firstterm> that each refer to an installed kernel. These stanzas always start with a <computeroutput>title</computeroutput> entry, after which the associated <computeroutput>root</computeroutput>, <computeroutput>kernel</computeroutput> and <computeroutput>initrd</computeroutput> directives should always be indented. Ensure that each stanza starts with a <computeroutput>title</computeroutput> that contains a version number (in parentheses) that matches the version number in the <computeroutput>kernel /vmlinuz-<replaceable><version_number></replaceable>
+ <para>GRUB's configuration file<indexterm><primary>GRUB boot loader</primary><secondary>configuring</secondary></indexterm><indexterm><primary>GRUB boot loader</primary><secondary>configuration file</secondary></indexterm>, <filename>/boot/grub/grub.conf</filename>, contains a few lines with directives, such as <computeroutput>default</computeroutput>, <computeroutput>timeout</computeroutput>, <computeroutput>splashimage</computeroutput> and <computeroutput>hiddenmenu</computeroutput> (the last directive has no argument). The remainder of the file contains 4-line <firstterm>stanzas</firstterm> that each refer to an installed kernel. These stanzas always start with a <computeroutput>title</computeroutput> entry, after which the associated <computeroutput>root</computeroutput>, <computeroutput>kernel</computeroutput> and <computeroutput>initrd</computeroutput> directives should always be indented. Ensure that each stanza starts with a <computeroutput>title</computeroutpu
t> that contains a version number (in parentheses) that matches the version number in the <computeroutput>kernel /vmlinuz-<replaceable><version_number></replaceable>
</computeroutput> line of the same stanza.</para>
<example
id="ex-_boot_grub_grub.conf">
@@ -480,7 +516,9 @@ title Red Hat Enterprise Linux 6 (2.6.32-17.el6.x86_64)
<title>Configuring the <trademark
class="registered">OS/400</trademark> Boot Loader</title>
<para>The <filename>/boot/vmlinitrd-<replaceable><kernel-version></replaceable>
- </filename> file is installed when you upgrade the kernel. However, you must use the <command>dd</command> command to configure the system to boot the new kernel.</para>
+ </filename> file
+ <indexterm><primary>OS/400 boot loader</primary><secondary>configuring</secondary></indexterm>
+ <indexterm><primary>OS/400 boot loader</primary><secondary>configuration file</secondary></indexterm> is installed when you upgrade the kernel. However, you must use the <command>dd</command> command to configure the system to boot the new kernel.</para>
<orderedlist
continuation="restarts"
inheritnum="ignore">
13 years, 11 months
[deployment-guide/comm-rel: 66/74] UsersGroups: update complete chapter
by dsilas
commit 6ff3e332b6d9a344bbf7dd6c4adf5143403cf531
Author: fnadge <fnadge(a)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
13 years, 11 months
[deployment-guide/comm-rel: 65/74] modified chapter DHCP
by dsilas
commit 87d6fb20332917ac85b4939dc2b6b8c88d160137
Author: Martin Prpic <mprpic(a)redhat.com>
Date: Tue Jun 29 13:02:01 2010 +0200
modified chapter DHCP
en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml | 26 ++++++++++++-------
1 files changed, 16 insertions(+), 10 deletions(-)
---
diff --git a/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml b/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
index 334562c..5730104 100644
--- a/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
+++ b/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
@@ -402,7 +402,6 @@ DHCPDARGS="eth0";
</screen>
<para>The following is a basic <filename>/etc/dhcp/dhcpd.conf</filename> file, for a server that has two network interfaces, <filename>eth0</filename> in a 10.0.0.0/24 network, and <filename>eth1</filename> in a 172.16.0.0/24 network. Multiple <computeroutput>subnet</computeroutput> declarations allow different settings to be defined for multiple networks:</para>
<screen>
-ddns-update-style <replaceable>interim</replaceable>;
default-lease-time <replaceable>600</replaceable>;
max-lease-time <replaceable>7200</replaceable>;
subnet 10.0.0.0 netmask 255.255.255.0 {
@@ -419,7 +418,7 @@ subnet 172.16.0.0 netmask 255.255.255.0 {
<variablelist>
<varlistentry>
<term>
- <computeroutput>subnet <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable> netmask <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
+ <computeroutput>subnet <replaceable>10.0.0.0</replaceable> netmask <replaceable>255.255.255.0</replaceable>;</computeroutput>
</term>
<listitem>
<para>A <computeroutput>subnet</computeroutput> declaration is required for every network your DHCP server is serving. Multiple subnets require multiple <computeroutput>subnet</computeroutput> declarations. If the DHCP server does not have a network interface in a range of a <computeroutput>subnet</computeroutput> declaration, the DHCP server does not serve that network.</para>
@@ -438,7 +437,7 @@ dhcpd: Not configured to listen on any interfaces!
</varlistentry>
<varlistentry>
<term>
- <computeroutput>option subnet-mask <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
+ <computeroutput>option subnet-mask <replaceable>255.255.255.0</replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>option subnet-mask</computeroutput> option defines a subnet mask, and overrides the <computeroutput>netmask</computeroutput> value in the <computeroutput>subnet</computeroutput> declaration. In simple cases, the subnet and netmask values are the same.</para>
@@ -446,7 +445,7 @@ dhcpd: Not configured to listen on any interfaces!
</varlistentry>
<varlistentry>
<term>
- <computeroutput>option routers <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
+ <computeroutput>option routers <replaceable>10.0.0.1</replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>option routers</computeroutput> option defines the default gateway for the subnet. This is required for systems to reach internal networks on a different subnet, as well as external networks.</para>
@@ -454,7 +453,7 @@ dhcpd: Not configured to listen on any interfaces!
</varlistentry>
<varlistentry>
<term>
- <computeroutput>range <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
+ <computeroutput>range <replaceable>10.0.0.5</replaceable> <replaceable>10.0.0.15</replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>range</computeroutput> option specifies the pool of available IP addresses. Systems are assigned an address from the range of specified IP addresses.</para>
@@ -480,7 +479,6 @@ dhcpd: Not configured to listen on any interfaces!
<para>The following <filename>/etc/dhcp/dhcpd.conf</filename> example creates two subnets, and configures an IP address for the same system, depending on which network it connects to:</para>
</formalpara>
<screen>
-ddns-update-style <replaceable>interim</replaceable>;
default-lease-time <replaceable>600</replaceable>;
max-lease-time <replaceable>7200</replaceable>;
subnet 10.0.0.0 netmask 255.255.255.0 {
@@ -515,7 +513,7 @@ host example1 {
</varlistentry>
<varlistentry>
<term>
- <computeroutput>hardware ethernet <replaceable><mac_address></replaceable>;</computeroutput>
+ <computeroutput>hardware ethernet <replaceable>00:1A:6B:6A:2E:0B</replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>hardware ethernet</computeroutput> option identifies the system. To find this address, run the <command>ip link</command> command.</para>
@@ -523,7 +521,7 @@ host example1 {
</varlistentry>
<varlistentry>
<term>
- <computeroutput>fixed-address <replaceable><ipv4_address></replaceable></computeroutput> <emphasis>or</emphasis> <computeroutput><replaceable><ipv6_address></replaceable>;</computeroutput>
+ <computeroutput>fixed-address <replaceable>10.0.0.20</replaceable>;</computeroutput>
</term>
<listitem>
<para>The <computeroutput>fixed-address</computeroutput> option assigns a valid IP address to the system specified by the <computeroutput>hardware ethernet</computeroutput> option. This address must be outside the IP address pool specified with the <computeroutput>range</computeroutput> option.</para>
@@ -576,8 +574,16 @@ dhcpd: Configuration file errors encountered -- exiting
</section>
<section id="s1-dhcp_for_ipv6_dhcpv6">
<title>DHCP for IPv6 (DHCPv6)</title>
+ <indexterm>
+ <primary>DHCP</primary>
+ <secondary>DHCPv6</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>DHCP</primary>
+ <secondary>dhcpd6.conf</secondary>
+ </indexterm>
<para>
- The ISC DHCP includes support for IPv6 (DHCPv6) since the 4.x release with a DHCPv6 server, client and relay agent functionality. The server, client and relay agents support both IPv4 and IPv6. However, the client and server agents can only operate one protocol at a time — for dual support they must be started separately for IPv4 and IPv6.
+ The ISC DHCP includes support for IPv6 (DHCPv6) since the 4.x release with a DHCPv6 server, client and relay agent functionality. The server, client and relay agents support both IPv4 and IPv6. However, the client and the server can only manage one protocol at a time — for dual support they must be started separately for IPv4 and IPv6.
</para>
<para>
The DHCPv6 server configuration file can be found at <filename>/etc/dhcp/dhcpd6.conf</filename>.
@@ -622,7 +628,7 @@ subnet6 2001:db8:0:1::/64 {
</listitem>
<listitem>
<para>
- <filename>dhcpd.leases</filename> man page — Explains how to configure the DHCP leases file; includes some examples.</para>
+ <filename>dhcpd.leases</filename> man page — Describes a persistent database of leases.</para>
</listitem>
<listitem>
<para>
13 years, 11 months
[deployment-guide/comm-rel: 64/74] Another minor formatting enhancements.
by dsilas
commit 40eec0a368f0440673a69c4849cfac86811843f4
Author: Jaromir Hradilek <jhradile(a)redhat.com>
Date: Tue Jun 29 11:57:40 2010 +0200
Another minor formatting enhancements.
en-US/Date_and_Time_Configuration.xml | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Date_and_Time_Configuration.xml b/en-US/Date_and_Time_Configuration.xml
index 0877174..abc7a7c 100644
--- a/en-US/Date_and_Time_Configuration.xml
+++ b/en-US/Date_and_Time_Configuration.xml
@@ -233,8 +233,11 @@ Password: </screen>
<para>
You can check your current settings by typing <command>date</command> without any additional argument:
</para>
- <screen>~]$ <command>date</command>
+ <example id="ex-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">
+ <title>Displaying the current date and time</title>
+ <screen>~]$ <command>date</command>
Wed Jun 2 11:58:48 CEST 2010</screen>
+ </example>
</section>
<section id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">
<title>Network Time Protocol Setup</title>
13 years, 11 months