en-US/Boot_Init_Shutdown.xml en-US/firstboot.xml en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml en-US/Trouble_During_common-python-errors.xml en-US/Trouble_During_x86_ppc-section-2-para-2a.xml en-US/Trouble_During-x86.xml

Fri Jul 24 06:45:40 UTC 2009

en-US/Boot_Init_Shutdown.xml                           |   37 +++++++++++--
 en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml |    4 -
 en-US/Trouble_During-x86.xml                           |    3 +
 en-US/Trouble_During_common-python-errors.xml          |    4 +
 en-US/Trouble_During_x86_ppc-section-2-para-2a.xml     |    7 ++
 en-US/firstboot.xml                                    |   48 +++++++----------
 6 files changed, 71 insertions(+), 32 deletions(-)

New commits:
commit a6b126dbc7c28f19a4d14024df48dcbe2b205a28
Author: Ruediger Landmann <r.landmann at redhat.com>
Date:   Fri Jul 24 16:45:09 2009 +1000

    More fixes for BZ#498991

diff --git a/en-US/Boot_Init_Shutdown.xml b/en-US/Boot_Init_Shutdown.xml
index c8f299c..eeb26a1 100644
--- a/en-US/Boot_Init_Shutdown.xml
+++ b/en-US/Boot_Init_Shutdown.xml
@@ -306,7 +306,7 @@
 			</para>
 			 
 			<para>
-				The <command>init</command> command then runs the <filename>/etc/inittab</filename> script, which describes how the system should be set up in each <firstterm>SysV init runlevel</firstterm>. Runlevels are a state, or <firstterm>mode</firstterm>, defined by the services listed in the SysV <filename>/etc/rc.d/rc<replaceable><x></replaceable>.d/</filename> directory, where <replaceable><x></replaceable> is the number of the runlevel. For more information on SysV init runlevels, refer to <xref linkend="s1-boot-init-shutdown-sysv"/>.
+				The <command>init</command> command then processes the jobs in the <filename>/etc/event.d</filename> directory, which describe how the system should be set up in each <firstterm>SysV init runlevel</firstterm>. Runlevels are a state, or <firstterm>mode</firstterm>, defined by the services listed in the SysV <filename>/etc/rc.d/rc<replaceable><x></replaceable>.d/</filename> directory, where <replaceable><x></replaceable> is the number of the runlevel. For more information on SysV init runlevels, refer to <xref linkend="s1-boot-init-shutdown-sysv"/>.
 			</para>
 			 
 			<para>
@@ -445,7 +445,7 @@ S99local -> ../rc.local
 			</note>
 			 
 			<para>
-				After the <command>init</command> command has progressed through the appropriate <filename>rc</filename> directory for the runlevel, the <filename>/etc/inittab</filename> script forks an <command>/sbin/mingetty</command> process for each virtual console (login prompt) allocated to the runlevel. Runlevels 2 through 5 have all six virtual consoles, while runlevel 1 (single user mode) has one, and runlevels 0 and 6 have none. The <command>/sbin/mingetty</command> process opens communication pathways to <firstterm>tty</firstterm> devices<footnote>
+				After the <command>init</command> command has progressed through the appropriate <filename>rc</filename> directory for the runlevel, <application>Upstart</application> forks an <command>/sbin/mingetty</command> process for each virtual console (login prompt) allocated to the runlevel by the job definition in the <filename>/etc/event.d</filename> directory. Runlevels 2 through 5 have all six virtual consoles, while runlevel 1 (single user mode) has one, and runlevels 0 and 6 have none. The <command>/sbin/mingetty</command> process opens communication pathways to <firstterm>tty</firstterm> devices<footnote>
 				<para>
 					Refer to the Red Hat Enterprise Linux Deployment Guide for more information about <filename>tty</filename> devices.
 				</para>
@@ -453,7 +453,7 @@ S99local -> ../rc.local
 			</para>
 			 
 			<para>
-				In runlevel 5, the <filename>/etc/inittab</filename> runs a script called <filename>/etc/X11/prefdm</filename>. The <filename>prefdm</filename> script executes the preferred X display manager<footnote>
+				In runlevel 5, <application>Upstart</application> runs a script called <filename>/etc/X11/prefdm</filename>. The <filename>prefdm</filename> script executes the preferred X display manager<footnote>
 				<para>
 					Refer to the Red Hat Enterprise Linux Deployment Guide for more information about display managers.
 				</para>
@@ -464,6 +464,35 @@ S99local -> ../rc.local
 				Once finished, the system operates on runlevel 5 and displays a login screen.
 			</para>
 		</section>
+		<section id="s2-boot-init-shutdown-jobs">
+		<title>Job definitions</title>
+		<para>
+			Previously, the <package>sysvinit</package> package provided the <application>init</application> daemon for the default configuration. When the system started, this <application>init</application> daemon ran the <filename>/etc/inittab</filename> script to start system processes defined for each runlevel. The default configuration now uses an event-driven <application>init</application> daemon provided by the <package>Upstart</package> package. Whenever particular <firstterm>events</firstterm> occur, the <application>init</application> daemon processes <firstterm>jobs</firstterm> stored in the <filename>/etc/event.d</filename> directory. The <application>init</application> daemon recognises the start of the system as such an event. 
+		</para>
+		<para>
+			Each job typically specifies a program, and the events that trigger <application>init</application> to run or to stop the program. Some jobs are constructed as <firstterm>tasks</firstterm>, which perform actions and then terminate until another event triggers the job again. Other jobs are constructed as <firstterm>services</firstterm>, which <application>init</application> keeps running until another event (or the user) stops it.
+		</para>
+		<para>
+			For example, the <filename>/etc/events.d/tty2</filename> job is a service to maintain a virtual terminal on <application>tty2</application> from the time that the system starts until the system shuts down, or another event (such as a change in runlevel) stops the job. The job is constructed so that <application>init</application> will restart the virtual terminal if it stops unexpecedly during that time:
+		</para>
+<screen># tty2 - getty
+#
+# This service maintains a getty on tty2 from the point the system is
+# started until it is shut down again.
+
+start on stopped rc2
+start on stopped rc3
+start on stopped rc4
+start on started prefdm
+
+stop on runlevel 0
+stop on runlevel 1
+stop on runlevel 6
+
+respawn
+exec /sbin/mingetty tty2
+</screen>
+		</section>
 	</section>
 	<section id="s1-boot-init-shutdown-run-boot">
 		<title>Running Additional Programs at Boot Time</title>
@@ -603,7 +632,7 @@ S99local -> ../rc.local
 			</para>
 			 
 			<para>
-				The default runlevel for the system is listed in <filename>/etc/inittab</filename>. To find out the default runlevel for a system, look for the line similar to the following near the top of
+				The default runlevel for the system is listed in <filename>/etc/inittab</filename>. To find out the default runlevel for a system, look for the line similar to the following near the bottom of
 				<filename>/etc/inittab</filename>:
 			</para>
 <screen>
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml b/en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml
index d24e160..45ad8b2 100644
--- a/en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml
+++ b/en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml
@@ -56,7 +56,7 @@
 	
 	<para>
 		<command>
-			<replaceable>/publicly/available/directory</replaceable> <replaceable>client.ip.address</replaceable>(ro,no_root_squash)
+			<replaceable>/publicly/available/directory</replaceable> <replaceable>client.ip.address</replaceable>
 		</command>
 	</para>
 		
@@ -66,7 +66,7 @@
 	
 	<para>
 		<command>
-			<replaceable>/publicly/available/directory</replaceable> *(ro,no_root_squash)
+			<replaceable>/publicly/available/directory</replaceable> *
 		</command>
 	</para>
 	
diff --git a/en-US/Trouble_During-x86.xml b/en-US/Trouble_During-x86.xml
index 43a1b03..7e51d6b 100644
--- a/en-US/Trouble_During-x86.xml
+++ b/en-US/Trouble_During-x86.xml
@@ -47,6 +47,9 @@
 		 
 		<!-- Second paragraph -->
 		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-para-2.xml"/>
+		
+		<!-- Between the second and third paragraphs -->
+		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-para-2a.xml"/>
 		 
 		<!-- Third paragraph -->
 		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-para-3.xml"/>
diff --git a/en-US/Trouble_During_common-python-errors.xml b/en-US/Trouble_During_common-python-errors.xml
index 12f3520..8ab5736 100644
--- a/en-US/Trouble_During_common-python-errors.xml
+++ b/en-US/Trouble_During_common-python-errors.xml
@@ -33,6 +33,10 @@ p4  (dp5  S'progressWindow'  p6   <failed><!--</computeroutput>-->
 		</para>
 		
 		<para>
+			If the error occurs after the graphical installer stage of <application>anaconda</application> has commenced, you can submit the error to Red Hat's bug tracking system, Bugzilla. You will need to supply your Bugzilla username and password, and a description of the bug. 
+		</para>
+		
+		<para>
 			If you experience such an error, first try to download any available updates for <application moreinfo="none">anaconda</application>. Updates for <application>anaconda</application> and instructions for using them can be found at:
 		</para>
 <screen>
diff --git a/en-US/Trouble_During_x86_ppc-section-2-para-2a.xml b/en-US/Trouble_During_x86_ppc-section-2-para-2a.xml
new file mode 100644
index 0000000..9874448
--- /dev/null
+++ b/en-US/Trouble_During_x86_ppc-section-2-para-2a.xml
@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+
+<para>
+	If you already have an account in Red Hat's bug-tracking system, Bugzilla, you can choose to submit details of the problem there. You will need to supply your Bugzilla username and password, and a description of the bug. 
+</para>
diff --git a/en-US/firstboot.xml b/en-US/firstboot.xml
index 7322746..fdf5a70 100644
--- a/en-US/firstboot.xml
+++ b/en-US/firstboot.xml
@@ -27,7 +27,7 @@
 </figure>
   
   <para>
-    Select <guibutton>Forward</guibutton> to start the
+    Select <guibutton>Forward</guibutton> to start 
     <application>Firstboot</application>.
   </para>
   <note>
@@ -190,31 +190,27 @@
       server or server pool from the list, select the name and click
       <guilabel>Delete</guilabel>.
     </para>
-    <para>If your machine is always connected to the Internet through a
-      wired connection, select the <guilabel>Synchronize system clock
-	before starting service</guilabel> option.  This option may
-      cause a short delay during startup but ensures accurate time on
-      your system even if the clock is significantly wrong at boot
-      time.</para>
-    <important>
-      <title>Laptops and NTP</title>
-      <para>Do not use this option with laptop computers that sometimes
-	use wireless networks.</para>
-    </important>
-    <para>
-      If the hardware clock in your computer is highly inaccurate, you
-      may turn off your local time source entirely. To turn off the
-      local time source, select <guilabel>Show advanced
-      options</guilabel> and then deselect the <guilabel>Use Local Time
-      Source</guilabel> option. If you turn off your local time source,
-      the NTP servers take priority over the internal clock.
-    </para>
-
-    <para>
-      If you enable the <guilabel>Enable NTP Broadcast</guilabel>
-      advanced option, Fedora attempts to automatically locate time
-      servers on the network.
-    </para>
+	<section>
+		<title>Advanced options</title>
+		<variablelist>
+			<varlistentry>
+				<term>Synchronize system clock before starting service</term>
+				<listitem>
+					<para>
+						If your computer is always connected to the Internet and  <application>NetworkManager</application> is disabled or not installed, and you need accurate time information obtained as quickly as possible after the system boots, select the <guilabel>Synchronize system clock before starting service</guilabel> option. By default, Fedora uses <application>NetworkManager</application> to manage network interfaces. 
+					</para>
+				</listitem>
+			</varlistentry>
+			<varlistentry>
+				<term>Use Local Time Source</term>
+				<listitem>
+					<para>
+						The NTP daemon (<application>ntpd</application>) on your computer usually refers to external NTP servers for authoritative information about the time. You can set the daemon running on your system to serve time to its NTP clients even if no source of synchronized time is available. To use this feature, select the <guilabel>Use Local Time Source</guilabel> option. This option is useful only under limited and unusual circumstances.
+					</para>
+				</listitem>
+			</varlistentry>
+		</variablelist>
+	</section>
   </section>
   <section id="sn-smolt">
     <title>Hardware Profile</title>



