[deployment-guide/comm-rel: 232/727] (multiple): remove all anachronistic lang='<langs>' atts
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:44:00 UTC 2010
commit 6abfe33814f9d00b453be9c8da88175bc027912b
Author: Douglas Silas <dhensley at redhat.com>
Date: Mon Aug 2 21:41:39 2010 +0200
(multiple): remove all anachronistic lang='<langs>' atts
en-US/Automated_Tasks.xml | 18 ++--
en-US/Controlling_Access_to_Services.xml | 2 +-
en-US/Deployment_Guide.xml | 82 +++++++-------------
en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml | 5 +-
en-US/Email.xml | 6 +-
en-US/FTP.xml | 12 +--
en-US/Introduction.xml | 15 +---
.../Lightweight_Directory_Access_Protocol_LDAP.xml | 6 +-
en-US/Network_Interfaces.xml | 12 +--
en-US/RPM.xml | 3 +-
en-US/Samba.xml | 6 +-
en-US/The_sysconfig_Directory.xml | 10 +--
en-US/Users_and_Groups.xml | 7 +-
13 files changed, 66 insertions(+), 118 deletions(-)
---
diff --git a/en-US/Automated_Tasks.xml b/en-US/Automated_Tasks.xml
index 006aba4..182b3b4 100644
--- a/en-US/Automated_Tasks.xml
+++ b/en-US/Automated_Tasks.xml
@@ -22,10 +22,10 @@
</primary>
</indexterm>
<para>Both, Cron and Anacron, are daemons that can be used to schedule the execution of recurring tasks according to a combination of the time, day of the month, month, day of the week, and week.</para>
- <para>Cron assumes that the system is on continuously. If the system is not on when a job is scheduled, it is not executed. Cron allows jobs to be run as often as every minute. Anacron does not assume the system is always on, remembers every scheduled job, and executes it the next time the system is up. However, Anacron can only run a job once a day.
+ <para>Cron assumes that the system is on continuously. If the system is not on when a job is scheduled, it is not executed. Cron allows jobs to be run as often as every minute. Anacron does not assume the system is always on, remembers every scheduled job, and executes it the next time the system is up. However, Anacron can only run a job once a day.
To schedule reccurring jobs, refer to <xref linkend="s2-configuring-anacron-jobs"/> or <xref linkend="s2-configuring-cron-jobs"/>. To schedule one-time jobs, refer to <xref linkend="s1-autotasks-at-batch"/>.</para>
<para>To use the cron service, the <filename>cronie</filename> RPM package must be installed and the <command>crond</command> service must be running. <filename>anacron</filename> is a sub-package of <filename>cronie</filename>. To determine if these packages are installed, use the <command>rpm -q cronie cronie-anacron</command> command. </para>
- <section id="s2-autotasks-cron-service" 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">
+ <section id="s2-autotasks-cron-service">
<title>Starting and Stopping the Service</title>
<para>To determine if the service is running, use the command <command>/sbin/service crond status</command>. To start the cron service, use the command <command>/sbin/service crond start</command>. To stop the service, use the command <command>/sbin/service crond stop</command>. It is recommended that you start the service at boot time. Refer to <xref linkend="ch-Controlling_Access_to_Services"/> for details on starting the cron service automatically at boot time.</para>
</section>
@@ -67,7 +67,7 @@ START_HOURS_RANGE=3-22
@monthly 45 cron.monthly nice run-parts /etc/cron.monthly
</screen>
<para>
- The first three lines are variables used to configure the environment in which the anacron tasks are run. The <computeroutput>SHELL</computeroutput> variable tells the system which shell environment to use (in this example the bash shell). The <computeroutput>PATH</computeroutput> variable defines the path used to execute commands. The output of the anacron jobs are emailed to the username defined with the <computeroutput>MAILTO</computeroutput> variable. If the <computeroutput>MAILTO</computeroutput> variable is not defined, (i.e. is empty, <computeroutput>MAILTO=</computeroutput>), email is not sent.
+ The first three lines are variables used to configure the environment in which the anacron tasks are run. The <computeroutput>SHELL</computeroutput> variable tells the system which shell environment to use (in this example the bash shell). The <computeroutput>PATH</computeroutput> variable defines the path used to execute commands. The output of the anacron jobs are emailed to the username defined with the <computeroutput>MAILTO</computeroutput> variable. If the <computeroutput>MAILTO</computeroutput> variable is not defined, (i.e. is empty, <computeroutput>MAILTO=</computeroutput>), email is not sent.
</para>
<para>
The next two lines are variables that modify the time for each scheduled job. The <computeroutput>RANDOM_DELAY</computeroutput> variable denotes the maximum number of minutes that will be added to the <filename>delay in minutes</filename> variable which is specified for each job. The minimum delay value is set, by default, to 6 minutes. A <computeroutput>RANDOM_DELAY</computeroutput> set to 12 would therefore add, randomly, between 6 and 12 minutes to the <filename>delay in minutes</filename> for each job in that particular anacrontab. <computeroutput>RANDOM_DELAY</computeroutput> can also be set to a value below 6, or even 0. When set to 0, no random delay is added. This proves to be useful when, for example, more computers that share one network connection need to download the same data every day. The <computeroutput>START_HOURS_RANGE</computeroutput> variable defines an interval (in hours) when scheduled jobs can be run. In case this time interval is missed, for example
, due to a power down, then scheduled jobs are not executed that day.
@@ -119,7 +119,7 @@ START_HOURS_RANGE=16-20
@monthly 45 monthlyjob ls /proc >> /tmp/proc
</screen>
<para>
- All jobs defined in this <filename>anacrontab</filename> file are randomly delayed by 6-30 minutes and can be executed between 16:00 and 20:00. Thus, the first defined job will run anywhere between 16:26 and 16:50 every day. The command specified for this job will execute all present programs in the <filename>/etc/cron.daily</filename> directory (using the <command>run-parts</command> script which takes a directory as a command-line argument and sequentially executes every program within that directory). The second specified job will be executed once a week and will execute the <filename>weeklyjob.bash</filename> script in the <filename>/etc</filename> directory. The third job is executed once a month and runs a command to write the contents of the <filename>/proc</filename> to the <filename>/tmp/proc</filename> file (e.g. <computeroutput>ls /proc >> /tmp/proc</computeroutput>).
+ All jobs defined in this <filename>anacrontab</filename> file are randomly delayed by 6-30 minutes and can be executed between 16:00 and 20:00. Thus, the first defined job will run anywhere between 16:26 and 16:50 every day. The command specified for this job will execute all present programs in the <filename>/etc/cron.daily</filename> directory (using the <command>run-parts</command> script which takes a directory as a command-line argument and sequentially executes every program within that directory). The second specified job will be executed once a week and will execute the <filename>weeklyjob.bash</filename> script in the <filename>/etc</filename> directory. The third job is executed once a month and runs a command to write the contents of the <filename>/proc</filename> to the <filename>/tmp/proc</filename> file (e.g. <computeroutput>ls /proc >> /tmp/proc</computeroutput>).
</para>
<section id="s3-disabling-anacron">
<title>Disabling Anacron</title>
@@ -219,7 +219,7 @@ minute hour day month day of week user command
<note>
<title>Note</title>
<para>
- When using the <command>crontab</command> utility, there is no need to specify a user when defining a job.
+ When using the <command>crontab</command> utility, there is no need to specify a user when defining a job.
</para>
</note>
<para>The <filename>/etc/cron.d/</filename> directory contains files that have the same syntax as the <filename>/etc/crontab</filename> file. Only root is allowed to create and modify files in this directory.</para>
@@ -246,9 +246,9 @@ minute hour day month day of week user command
<section id="s2-black-white-listing-of-cron-jobs">
<title>Black/White Listing of Cron Jobs</title>
<para>
- Black/White listing of jobs is used to omit parts of the defined jobs that do not need to be executed. When calling the <command>run-parts</command> script on a cron folder, such as <filename>/etc/cron.daily</filename>, we can define which of the programs in this folder will not be executed by <command>run-parts</command>.
+ Black/White listing of jobs is used to omit parts of the defined jobs that do not need to be executed. When calling the <command>run-parts</command> script on a cron folder, such as <filename>/etc/cron.daily</filename>, we can define which of the programs in this folder will not be executed by <command>run-parts</command>.
</para>
- <para>To define a black list, create a <filename>jobs.deny</filename> file in the folder that <command>run-parts</command> will be executing from. For example, if we need to omit a particular program from /etc/cron.daily, then, a file <filename>/etc/cron.daily/jobs.deny</filename> has to be created. In this file, specify the names of the omitted programs from the same directory. These will not be executed when a command, such as <computeroutput>run-parts /etc/cron.daily</computeroutput>, is executed by a specific job.</para>
+ <para>To define a black list, create a <filename>jobs.deny</filename> file in the folder that <command>run-parts</command> will be executing from. For example, if we need to omit a particular program from /etc/cron.daily, then, a file <filename>/etc/cron.daily/jobs.deny</filename> has to be created. In this file, specify the names of the omitted programs from the same directory. These will not be executed when a command, such as <computeroutput>run-parts /etc/cron.daily</computeroutput>, is executed by a specific job.</para>
<para>To define a white list, create a <filename>jobs.allow</filename> file.</para>
<para>
The principles of <filename>jobs.deny</filename> and <filename>jobs.allow</filename> are the same as those of <filename>cron.deny</filename> and <filename>cron.allow</filename> described in section <xref linkend="s2-autotasks-cron-access"/>.
@@ -383,7 +383,7 @@ minute hour day month day of week user command
<para>If the file <filename>at.allow</filename> exists, only users listed in it are allowed to use <command>at</command> or <command>batch</command>, and the <filename>at.deny</filename> file is ignored.</para>
<para>If <filename>at.allow</filename> does not exist, users listed in <filename>at.deny</filename> are not allowed to use <command>at</command> or <command>batch</command>.</para>
</section>
- <section id="s2-autotasks-at-batch-service" 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">
+ <section id="s2-autotasks-at-batch-service">
<title>Starting and Stopping the Service</title>
<para>To start the <command>at</command> service, use the command <command>/sbin/service atd start</command>. To stop the service, use the command <command>/sbin/service atd stop</command>. It is recommended that you start the service at boot time. Refer to <xref linkend="ch-Controlling_Access_to_Services"/> for details on starting the cron service automatically at boot time.</para>
</section>
@@ -421,7 +421,7 @@ minute hour day month day of week user command
</listitem>
<listitem>
<para>
- <filename>anacrontab</filename> man page — contains an overview of the <filename>anacrontab</filename> file.
+ <filename>anacrontab</filename> man page — contains an overview of the <filename>anacrontab</filename> file.
</para>
</listitem>
<listitem>
diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml
index ee8a6c2..6c8a627 100644
--- a/en-US/Controlling_Access_to_Services.xml
+++ b/en-US/Controlling_Access_to_Services.xml
@@ -12,7 +12,7 @@
<para>
This chapter explains the concept of runlevels, and describes how to set the default one. It also covers the setup of the services to be run in each of them using three different utilities: the <application>Service Configuration</application> graphical application, the <application>ntsysv</application> text user interface, and the <application>chkconfig</application> command line tool. Finally, it describes how to start, stop, and restart the services on a command line using the <application>service</application> command.
</para>
- <important 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">
+ <important>
<title>Important</title>
<para>
When you allow access for new services, always remember that both the firewall and <application>SELinux</application> need to be configured as well. One of the most common mistakes committed when configuring a new service is neglecting to implement the necessary firewall configuration and SELinux policies to allow access for it. Refer to the &MAJOROS; <citetitle pubwork="book">Security Guide</citetitle> (see <xref linkend="s1-services-additional-resources" />) for more information.
diff --git a/en-US/Deployment_Guide.xml b/en-US/Deployment_Guide.xml
index 4355909..64896c2 100644
--- a/en-US/Deployment_Guide.xml
+++ b/en-US/Deployment_Guide.xml
@@ -14,8 +14,7 @@
xmlns:xi="http://www.w3.org/2001/XInclude"
href="Introduction.xml"/>
<part
- id="pt-pkg-management"
- 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,fr-FR,es-ES">
+ id="pt-pkg-management">
<title>Package Management</title>
<partintro>
<para>All software on a &MAJOROS; system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on &MAJOROS; using the <application>Yum</application> and <application>RPM</application> package managers and the <application>PackageKit</application> suite of graphical package management tools.</para>
@@ -35,64 +34,50 @@
href="Red_Hat_Network.xml"/>-->
</part>
<part
- id="pt-network-related-config"
- 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,de-DE,ru-RU,fr-FR,zh-CN,it-IT,es-ES,ja-JP">
+ id="pt-network-related-config">
<title>Network-Related Configuration</title>
<partintro>
<para>After explaining how to configure the network, this part discusses topics related to networking such as how to allow remote logins, share files and directories over the network, and set up a Web server.</para>
</partintro>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Network_Interfaces.xml"
- 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,de-DE,ru-RU,fr-FR,zh-CN,it-IT,es-ES,ja-JP"/>
+ href="Network_Interfaces.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Network_Configuration.xml"
- 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,de-DE,fr-FR,it-IT,es-ES,pt-BR,ja-JP"/>
+ href="Network_Configuration.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Controlling_Access_to_Services.xml"
- 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,ja-JP,es-ES,fr-FR"/>
+ href="Controlling_Access_to_Services.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="The_BIND_DNS_Server.xml"
- 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,it-IT,es-ES,ja-JP,de-DE,fr-FR"/>
+ href="The_BIND_DNS_Server.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="OpenSSH.xml"
- 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,de-DE,fr-FR,it-IT,es-ES,ja-JP"/>
+ href="OpenSSH.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Samba.xml"
- 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,ja-JP,fr-FR,es-ES"/>
+ href="Samba.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Dynamic_Host_Configuration_Protocol_DHCP.xml"
- 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,de-DE,fr-FR,it-IT,es-ES,ja-JP"/>
+ href="Dynamic_Host_Configuration_Protocol_DHCP.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="The_Apache_HTTP_Server.xml"
- 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,ja-JP,es-ES,fr-FR"/>
+ href="The_Apache_HTTP_Server.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="FTP.xml"
- 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,it-IT,es-ES,ja-JP,fr-FR"/>
+ href="FTP.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Email.xml"
- 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,ja-JP,es-ES,fr-FR"/>
+ href="Email.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Lightweight_Directory_Access_Protocol_LDAP.xml"
- 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,ja-JP,es-ES,fr-FR"/>
+ href="Lightweight_Directory_Access_Protocol_LDAP.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Authentication_Configuration.xml"
- 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,ja-JPi,es-ES,fr-FR"/>
+ href="Authentication_Configuration.xml"/>
</part>
<part
- id="pt-sysconfig"
- 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,de-DE,es-ES,fr-FR,it-IT,ja-JP">
+ id="pt-sysconfig">
<title>System Configuration</title>
<partintro>
<para>Part of a system administrator's job is configuring the system for various tasks, types of users, and hardware configurations. This section explains how to configure a &MAJOROS; system.</para>
@@ -101,52 +86,40 @@
This chapter will be replaced by one or more (of a combination of) ConsoleKit, PolicyKit and sudo chapters/sections (bugs 617222, 617221, 617224)
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Console_Access.xml"
- 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,ja-JP,zh-CN,fr-FR,es-ES"/>-->
+ href="Console_Access.xml"/>-->
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- 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,ja-JP,zh-CN,fr-FR,es-ES"
href="The_proc_File_System.xml" />
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="The_sysconfig_Directory.xml"
- 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,ja-JP,es-ES,zh-CN,fr-FR"/>
+ href="The_sysconfig_Directory.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Date_and_Time_Configuration.xml"
- 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,de-DE,pt-BR,es-ES,ja-JP,zh-CN,fr-FR"/>
+ href="Date_and_Time_Configuration.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Keyboard_Configuration.xml"
- 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,pt-BR,es-ES,zh-CN,fr-FR"/>
+ href="Keyboard_Configuration.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="The_X_Window_System.xml"
- 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,ja-JP,es-ES,fr-FR"/>
+ href="The_X_Window_System.xml"/>
<!--<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Configuring_the_X_Window_System.xml"
- 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,de-DE,fr-FR,zh-CN,pt-BR,it-IT,ko-KR,es-ES,ja-JP"/>-->
+ href="Configuring_the_X_Window_System.xml"/>-->
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Users_and_Groups.xml"
- 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,ja-JP,es-ES,fr-FR"/>
+ href="Users_and_Groups.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Printer_Configuration.xml"
- 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,ja-JP,fr-FR,es-ES"/>
+ href="Printer_Configuration.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Automated_Tasks.xml"
- 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,es-ES,ja-JP,fr-FR"/>
+ href="Automated_Tasks.xml"/>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="Log_Files.xml"
- 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,ja-JP,es-ES,fr-FR"/>
+ href="Log_Files.xml"/>
</part>
<part
- id="pt-system-monitoring"
- 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,fr-FR,es-ES">
+ id="pt-system-monitoring">
<title>System Monitoring</title>
<partintro>
<para>System administrators also monitor system performance. &MAJOROS; contains tools to assist administrators with these tasks.</para>
@@ -162,8 +135,7 @@
href="ABRT.xml" />
</part>
<part
- id="pt-kernel-configuration"
- 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,fr-FR,es-ES">
+ id="pt-kernel-configuration">
<title>Kernel and Driver Configuration</title>
<partintro>
<para>System administrators can learn about and customize their kernels. &MAJOROS; contains kernel tools to assist administrators with their customizations.</para>
diff --git a/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml b/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
index 5730104..a03dfdb 100644
--- a/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
+++ b/en-US/Dynamic_Host_Configuration_Protocol_DHCP.xml
@@ -250,8 +250,7 @@ group {
<para>If the same server is also running BIND as a DNS server, this step is not necessary, as starting the <command>named</command> service automatically checks for a <filename>dhcpd.leases</filename> file.</para>
</important>
<para>To start the DHCP service, use the command <command>/sbin/service dhcpd start</command>. To stop the DHCP server, use the command <command>/sbin/service dhcpd stop</command>.</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">
+ <para>
By default, the DHCP service does not start at boot time. To configure the daemon to start automatically at boot time, refer to <xref
linkend="ch-Controlling_Access_to_Services"/>.</para>
<indexterm
@@ -343,7 +342,7 @@ DHCPDARGS=eth0
<primary>DHCP</primary>
<secondary>connecting to</secondary>
</indexterm>
-
+
<para>To configure a DHCP client manually, modify the <filename>/etc/sysconfig/network</filename> file to enable networking and the configuration file for each network device in the <filename>/etc/sysconfig/network-scripts</filename> directory. In this directory, each device should have a configuration file named <filename>ifcfg-eth0</filename>, where <filename>eth0</filename> is the network device name.</para>
<para>The <filename>/etc/sysconfig/network-scripts/ifcfg-eth0</filename> file should contain the following lines:</para>
<screen>
diff --git a/en-US/Email.xml b/en-US/Email.xml
index a5c9d39..20b3a90 100644
--- a/en-US/Email.xml
+++ b/en-US/Email.xml
@@ -2,8 +2,7 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<chapter
- id="ch-email"
- lang="en-US">
+ id="ch-email">
<title>Email</title>
<indexterm
significance="normal">
@@ -69,8 +68,7 @@
<para>
<emphasis>APOP</emphasis> — POP3 with MDS authentication. An encoded hash of the user's password is sent from the email client to the server rather then sending an unencrypted password.</para>
</listitem>
- <listitem
- 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,pt-BR">
+ <listitem>
<para>
<emphasis>KPOP</emphasis> — POP3 with Kerberos authentication.</para>
</listitem>
diff --git a/en-US/FTP.xml b/en-US/FTP.xml
index 5174019..45f04a0 100644
--- a/en-US/FTP.xml
+++ b/en-US/FTP.xml
@@ -187,8 +187,7 @@
<filename>/etc/rc.d/init.d/vsftpd</filename> — The <emphasis>initialization script</emphasis> (<firstterm>initscript</firstterm>) used by the <command>/sbin/service</command> command to start, stop, or reload <command>vsftpd</command>. Refer to <xref
linkend="s1-ftp-vsftpd-start"/> for more information about using this script.</para>
</listitem>
- <listitem
- 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">
+ <listitem>
<para>
<filename>/etc/pam.d/vsftpd</filename> — The Pluggable Authentication Modules (PAM) configuration file for <command>vsftpd</command>. This file specifies the requirements a user must meet to login to the FTP server. For more information on PAM, refer to the <citetitle pubwork="chapter">Pluggable Authentication Modules (PAM)</citetitle> chapter of the &MAJOROSVER; <citetitle>Security Guide</citetitle>.</para>
</listitem>
@@ -269,8 +268,7 @@
<screen>
<command>/sbin/service vsftpd condrestart</command>
</screen>
- <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">
+ <para>
By default, the <command>vsftpd</command> service does <emphasis>not</emphasis> start automatically at boot time. To configure the <command>vsftpd</command> service to start at boot time, use an initscript utility, such as <command>/sbin/chkconfig</command>, <application>/usr/sbin/ntsysv</application>, or the <application>Services Configuration Tool</application> program. Refer to <xref
linkend="ch-Controlling_Access_to_Services"/> for more information regarding these tools.</para>
<section
@@ -373,8 +371,7 @@
</important>
<para>Comment lines must be preceded by a hash mark (<command>#</command>) and are ignored by the daemon.</para>
<para>For a complete list of all directives available, refer to the man page for <filename>vsftpd.conf</filename>.</para>
- <important
- 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">
+ <important>
<title>Important</title>
<para>For an overview of ways to secure <command>vsftpd</command>, refer to the &MAJOROSVER; <citetitle>Security Guide</citetitle>.</para>
</important>
@@ -402,8 +399,7 @@
<command>listen_ipv6</command> — When enabled, <command>vsftpd</command> runs in stand-alone mode, but listens only to IPv6 sockets. This directive cannot be used in conjunction with the <command>listen</command> directive.</para>
<para>The default value is <command>NO</command>.</para>
</listitem>
- <listitem
- 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">
+ <listitem>
<para>
<command>session_support</command> — When enabled, <command>vsftpd</command> attempts to maintain login sessions for each user through Pluggable Authentication Modules (PAM). Refer to <!-- TBD6: <xref
linkend="ch-pam"/> --> for more information. If session logging is not necessary, disabling this option allows <command>vsftpd</command> to run with less processes and lower privileges.</para>
diff --git a/en-US/Introduction.xml b/en-US/Introduction.xml
index 25c63de..b4f097e 100644
--- a/en-US/Introduction.xml
+++ b/en-US/Introduction.xml
@@ -2,8 +2,7 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<preface
- id="ch-intro"
- lang="en-US">
+ id="ch-intro">
<title>Introduction</title>
<indexterm
significance="normal">
@@ -11,11 +10,9 @@
</indexterm>
<para>Welcome to the <citetitle>&MAJOROS; Deployment Guide</citetitle>.</para>
<para>The &MAJOROS; Deployment Guide contains information on how to customize your &MAJOROS; system to fit your needs. If you are looking for a comprehensive, task-oriented guide for configuring and customizing your system, this is the manual for you.</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">
+ <para>
This manual discusses many intermediate topics such as the following:</para>
- <itemizedlist
- 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">
+ <itemizedlist>
<listitem>
<para>Setting up a network interface card (NIC)</para>
</listitem>
@@ -35,11 +32,9 @@
<para>Upgrading your kernel</para>
</listitem>
</itemizedlist>
- <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">
+ <para>
This manual is divided into the following main categories:</para>
- <itemizedlist
- 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">
+ <itemizedlist>
<listitem>
<para>File systems</para>
</listitem>
diff --git a/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml b/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
index d4129b6..7c95f9b 100644
--- a/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
+++ b/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
@@ -444,8 +444,7 @@
name service and flat authentication files.</para>
-->
<para>The <filename>pam_ldap</filename> module allows PAM-aware applications to authenticate users using information stored in an LDAP directory. PAM-aware applications include console login, POP and IMAP mail servers, and Samba. By deploying an LDAP server on a network, all of these applications can authenticate using the same user ID and password combination, greatly simplifying administration.</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">
+ <para>
For more information about configuring PAM, refer to refer to the <citetitle pubwork="chapter">Pluggable Authentication Modules (PAM)</citetitle> chapter of the &MAJOROSVER; 6 <citetitle>Security Guide</citetitle> and the PAM man pages.</para>
</section>
<section
@@ -770,8 +769,7 @@ group: files ldap
</primary>
<secondary>and LDAP</secondary>
</indexterm>
- <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">
+ <para>
To have standard PAM-enabled applications use LDAP for authentication, run the <application>Authentication Configuration Tool</application> (<command>system-config-authentication</command>) and select <guilabel>Enable LDAP Support</guilabel> under the the <guilabel>Authentication</guilabel> tab. For more information about configuring PAM, refer to the <citetitle pubwork="chapter">Pluggable Authentication Modules (PAM)</citetitle> chapter of the &MAJOROSVER; <citetitle>Security Guide</citetitle> and the PAM man pages.</para>
</section>
<section
diff --git a/en-US/Network_Interfaces.xml b/en-US/Network_Interfaces.xml
index 66fa939..0b06570 100644
--- a/en-US/Network_Interfaces.xml
+++ b/en-US/Network_Interfaces.xml
@@ -67,8 +67,7 @@
<para>This file specifies the IP addresses of DNS servers and the search domain. Unless configured to do otherwise, the network initialization scripts populate this file. For more information about this file, refer to the <filename>resolv.conf</filename> man page.</para>
</listitem>
</varlistentry>
- <varlistentry
- 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">
+ <varlistentry>
<term>
<filename>/etc/sysconfig/network</filename>
</term>
@@ -113,8 +112,7 @@
<title>Warning</title>
<para>The <filename>/etc/sysconfig/networking/</filename> directory is used by the <application>Network Administration Tool</application> (<command>system-config-network</command>) and its contents should <emphasis
role="bold">not</emphasis> be edited manually. <!-- RHEL5: ddomingo at redhat.com: string removed as per Harald Hoyer <string> In addition, any use of the <application>Network Administration Tool</application> (even launching the application) will override any directives previously set in <filename>/etc/sysconfig/network-scripts</filename>.</string> -->Using only one method for network configuration is strongly encouraged, due to the risk of configuration deletion.</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">
+ <para>
For more information about configuring network interfaces using the <application>Network Administration Tool</application>, refer to <xref
linkend="ch-Network_Configuration"/>
</para>
@@ -162,8 +160,7 @@ USERCTL=no</screen>
<screen>DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes</screen>
- <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">
+ <para>
The <application>Network Administration Tool</application> (<command>system-config-network</command>) is an easy way to make changes to the various network interface configuration files (refer to <xref
linkend="ch-Network_Configuration"/> for detailed instructions on using this tool).</para>
<para>However, it is also possible to manually edit the configuration files for a given network interface.</para>
@@ -526,8 +523,7 @@ BOOTPROTO=dhcp</screen>
<para>Since the default value for the <command>USERCTL</command> directive is <command>no</command> if it is not specified, users cannot bring this interface up and down. To give users the ability to control the interface, create a clone by copying <filename>ifcfg-eth0</filename> to <filename>ifcfg-eth0-user</filename> and add the following line to <filename>ifcfg-eth0-user</filename>:</para>
<screen>USERCTL=yes</screen>
<para>This way a user can bring up the <filename>eth0</filename> interface using the <command>/sbin/ifup eth0-user</command> command because the configuration options from <filename>ifcfg-eth0</filename> and <filename>ifcfg-eth0-user</filename> are combined. While this is a very basic example, this method can be used with a variety of options and interfaces.</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">
+ <para>
The easiest way to create alias and clone interface configuration files is to use the graphical <application>Network Administration Tool</application>. For more information on using this tool, refer to <xref
linkend="ch-Network_Configuration"/>.</para>
</section>
diff --git a/en-US/RPM.xml b/en-US/RPM.xml
index f3252a1..95ac586 100644
--- a/en-US/RPM.xml
+++ b/en-US/RPM.xml
@@ -2,8 +2,7 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<chapter
- id="ch-RPM"
- lang="en-US">
+ id="ch-RPM">
<title>RPM</title>
<indexterm>
<primary>RPM Package Manager</primary>
diff --git a/en-US/Samba.xml b/en-US/Samba.xml
index 3bea9d7..cc0e6cb 100644
--- a/en-US/Samba.xml
+++ b/en-US/Samba.xml
@@ -2,8 +2,7 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<chapter
- id="ch-Samba"
- lang="en-US">
+ id="ch-Samba">
<title>Samba</title>
<indexterm
significance="normal">
@@ -862,8 +861,7 @@ password server = kerberos.example.com
<!-- RHEL5: ddomingo at redhat.com: above replaces below, less confusion
<screen>root# <userinput>kinit administrator at EXAMPLE.COM</userinput></screen>
-->
- <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,pt-BR">
+ <para>
The <command>kinit</command> command is a Kerberos initialization script that references the Active Directory administrator account and Kerberos realm. Since Active Directory requires Kerberos tickets, <command>kinit</command> obtains and caches a Kerberos ticket-granting ticket for client/server authentication. For more information on Kerberos, the <command>/etc/krb5.conf</command> file, and the <command>kinit</command> command, refer to <!-- TBD6: <xref linkend="ch-kerberos"/> -->.</para>
<para>To join an Active Directory server (windows1.example.com), type the following command as root on the member server:</para>
<screen>
diff --git a/en-US/The_sysconfig_Directory.xml b/en-US/The_sysconfig_Directory.xml
index 4095482..a6b1340 100644
--- a/en-US/The_sysconfig_Directory.xml
+++ b/en-US/The_sysconfig_Directory.xml
@@ -875,8 +875,7 @@
<command>/sbin/service iptables save</command>
</screen>
<para>Once this file exists, any firewall rules saved in it persists through a system reboot or a service restart.</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">For more information on <command>iptables</command>, refer to <xref linkend="ch-iptables" /> .</para>
+ <para>For more information on <command>iptables</command>, refer to <xref linkend="ch-iptables" /> .</para>
</section>-->
<!-- silas: commenting out irda per rvokal
<section
@@ -1553,8 +1552,7 @@
<filename>/etc/sysconfig/system-config-securitylevel</filename>
</secondary>
</indexterm>
- <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">
+ <para>
The <filename>/etc/sysconfig/system-config-securitylevel</filename> file contains all options chosen by the user the last time the <application>Security Level Configuration Tool</application> (<command>system-config-securitylevel</command>) was run. Users should not modify this file by hand. For more information about the <application>Security Level Configuration Tool</application>, refer to <xref linkend="s1-basic-firewall" /> .</para>
</section>-->
<section id="s2-sysconfig-rcu">
@@ -1638,7 +1636,7 @@
</varlistentry>
</variablelist>
</section>
- <section id="s2-sysconfig-xinetd" 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">
+ <section id="s2-sysconfig-xinetd">
<title><filename>/etc/sysconfig/xinetd</filename></title>
<indexterm>
<primary><filename class="directory">sysconfig</filename> directory</primary>
@@ -1793,7 +1791,7 @@
<term><filename>/usr/share/doc/initscripts-<replaceable>version</replaceable>/sysconfig.txt</filename></term>
<listitem>
<para>
- A more authoritative listing of the files found in the <filename class="directory">/etc/sysconfig/</filename> directory and the configuration options available for them.
+ A more authoritative listing of the files found in the <filename class="directory">/etc/sysconfig/</filename> directory and the configuration options available for them.
</para>
</listitem>
</varlistentry>
diff --git a/en-US/Users_and_Groups.xml b/en-US/Users_and_Groups.xml
index 70b8ea2..4cca672 100644
--- a/en-US/Users_and_Groups.xml
+++ b/en-US/Users_and_Groups.xml
@@ -31,8 +31,7 @@
<firstterm>Groups</firstterm> are logical expressions of organization, tying users together for a common purpose. Users within a group can read, write, or execute files owned by that group.</para>
<para>Each user is associated with a unique numerical identification number called a <firstterm>userid</firstterm> (<firstterm>UID</firstterm>); likewise, each group is associated with a <firstterm>groupid</firstterm> (<firstterm>GID</firstterm>).</para>
<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">
+ <para>
&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
@@ -682,7 +681,7 @@
<entry>
Specifies the number of inactive days after the password expiration before locking the account. If the value is 0, the account is not locked after the password expires.
</entry>
- </row>
+ </row>
<row>
<entry>
<option>-l</option>
@@ -690,7 +689,7 @@
<entry>
Lists current account aging settings.
</entry>
- </row>
+ </row>
<row>
<entry>
<option>-m</option> <replaceable><days></replaceable>
More information about the docs-commits
mailing list