install-guide fedora-install-guide-acknowledgements-en.xml, 1.4, 1.5 fedora-install-guide-adminoptions-en.xml, 1.9, 1.10 fedora-install-guide-bootloader-en.xml, 1.14, 1.15 fedora-install-guide-diskpartitioning-en.xml, 1.16, 1.17 fedora-install-guide-en.xml, 1.41, 1.42 fedora-install-guide-packageselection-en.xml, 1.18, 1.19 rpm-info.xml, 1.6, 1.7
Stuart Ellis (elliss)
fedora-docs-commits at redhat.com
Thu Feb 2 00:13:03 UTC 2006
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv21748
Modified Files:
fedora-install-guide-acknowledgements-en.xml
fedora-install-guide-adminoptions-en.xml
fedora-install-guide-bootloader-en.xml
fedora-install-guide-diskpartitioning-en.xml
fedora-install-guide-en.xml
fedora-install-guide-packageselection-en.xml rpm-info.xml
Log Message:
- Added section on new remote logging feature.
- Amended Disk Partitioning section to address hardware RAID vs. software RAID.
- Amended Boot Loader section to address bug #173582.
- Note: Package selection is complete for test2, but needs further updates to match post-test2 development.
Index: fedora-install-guide-acknowledgements-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-acknowledgements-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-acknowledgements-en.xml 15 May 2005 18:39:09 -0000 1.4
+++ fedora-install-guide-acknowledgements-en.xml 2 Feb 2006 00:12:55 -0000 1.5
@@ -2,12 +2,11 @@
<chapter id="ch-acknowledgements">
<title>Acknowledgements</title>
-
<para>
- Many useful comments and suggestions were provided by Rahul
- Sundaram and the Anaconda team.
+ Many useful comments and suggestions were provided by Rahul Sundaram
+ and the Anaconda team. David Neimi and Debra Deutsch contributed
+ additional information on boot loader and RAID configurations.
</para>
-
</chapter>
<!--
Index: fedora-install-guide-adminoptions-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-adminoptions-en.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-adminoptions-en.xml 29 Jan 2006 20:37:55 -0000 1.9
+++ fedora-install-guide-adminoptions-en.xml 2 Feb 2006 00:12:55 -0000 1.10
@@ -73,11 +73,17 @@
<para>
To set the language for both the installation process and the
final system, specify the ISO code for that language with the
- <option>lang</option> option. For example, the ISO code
- <userinput>fr</userinput> identifies the French language:
+ <option>lang</option> option. Use the <option>keymap</option>
+ option to configure the correct keyboard layout.
+ </para>
+
+ <para>
+ For example, the ISO codes <userinput>el_GR</userinput> and
+ <userinput>gr</userinput> identify the Greek language and the
+ Greek keyboard layout:
</para>
<screen>
-<userinput>linux lang=<replaceable>fr</replaceable></userinput>
+<userinput>linux lang=<replaceable>el_GR</replaceable> keymap=<replaceable>gr</replaceable></userinput>
</screen>
</section>
@@ -416,7 +422,7 @@
<prompt>boot:</prompt>
prompt:
</para>
-<!--SE: The "text" option is necessary to stop the installer switching to graphical mode and losing the telnet interface. Possibly a bug. -->
+<!--SE: The "text" option is necessary to stop the installer switching to graphical mode and losing the telnet interface. This is expected behavior. -->
<screen>
<userinput>linux text telnet</userinput>
</screen>
@@ -438,7 +444,99 @@
with restricted access.
</para>
</caution>
-<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. There is also a "syslog" option to route logging to a remote system. -->
+<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. -->
+ </section>
+ <section id="sn-remote-logging">
+ <title>Logging to a Remote System</title>
+
+ <para>
+ By default, the installation system sends log messages to the
+ console. You may configure the system to log to a remote system
+ that runs a
+ <indexterm>
+ <primary>syslog</primary>
+ </indexterm>
+ <firstterm>syslog</firstterm> service.
+ </para>
+
+ <para>
+ To enable remote logging, specify the IP address of the remote
+ system with the <option>syslog</option> option. For example, to
+ connect to a <command>syslog</command> service on the system
+ <systemitem
+ class="ipaddress">192.168.1.20</systemitem>, enter
+ the following at the
+ <prompt>boot:</prompt>
+ prompt:
+ </para>
+<screen>
+<userinput>linux syslog=<replaceable>192.168.1.20</replaceable></userinput>
+</screen>
+ <para>
+ &FED; uses <command>syslogd</command> to provide a syslog service. The
+ default configuration of <command>syslogd</command> rejects
+ messages from remote systems.
+ </para>
+
+ <caution>
+ <title>Only Enable Remote Syslog Access on Secured Networks</title>
+
+ <para>
+ The <command>syslogd</command> service includes no security
+ measures. &FED; systems that enable remote access to this
+ service may be attacked by sending large quantities of log
+ messages. In addition, crackers may intercept or falsify
+ messages sent to the service.
+ </para>
+ </caution>
+
+ <para>
+ To enable remote systems to send log messages to a &FED; system,
+ edit the file <filename>/etc/sysconfig/syslog</filename>. Add the
+ <option>-r</option> to the <command>SYSLOGD_OPTIONS</command>.
+ </para>
+
+ <example>
+ <title>Syslogd Options Configuration</title>
+<screen>
+<computeroutput><![CDATA[
+SYSLOGD_OPTIONS="-m 0 -r"
+]]></computeroutput>
+</screen>
+ </example>
+
+ <para>
+ You must use <systemitem class="username">root</systemitem>
+ privileges to edit the file
+ <filename>/etc/sysconfig/syslog</filename>.
+ </para>
+
+ <para>
+ Restart the <command>syslogd</command> service to apply the
+ change:
+ </para>
+<screen>
+<userinput>su -c '/sbin/service syslog restart'</userinput>
+</screen>
+ <para>
+ Enter the <systemitem class="username">root</systemitem> password
+ when prompted.
+ </para>
+
+ <note>
+ <title>Firewall Reconfiguration Required</title>
+
+ <para>
+ By default, the syslog service listens on UDP port
+ <systemitem>514</systemitem>. To update the &FED; firewall
+ configuration to permit connections to this port from other
+ systems, choose <menuchoice> <guimenu>System</guimenu>
+ <guisubmenu>Administration</guisubmenu> <guimenuitem>Security
+ Level and Firewall</guimenuitem> </menuchoice>, enter
+ <userinput>514:udp</userinput> in the <guilabel>Other
+ ports:</guilabel> field, and select <guilabel>OK</guilabel>.
+ </para>
+ </note>
</section>
<section id="sn-automating-installation">
<title>Automating the Installation with Kickstart</title>
Index: fedora-install-guide-bootloader-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-bootloader-en.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- fedora-install-guide-bootloader-en.xml 29 Jan 2006 20:37:55 -0000 1.14
+++ fedora-install-guide-bootloader-en.xml 2 Feb 2006 00:12:55 -0000 1.15
@@ -21,7 +21,7 @@
does not recognize Linux partitions, you may not be able to boot
&FC;. Use <application>GRUB</application> as your boot loader to
boot Linux and most other operating systems. Follow the directions
- in this section to install <application>GRUB</application>.
+ in this chapter to install <application>GRUB</application>.
</para>
<warning>
<title>Installing GRUB</title>
@@ -87,6 +87,16 @@
IG. - PWF. -->
</para>
</important>
+
+ <para>
+ You may need to customize the GRUB installation to correctly
+ support some hardware or system configurations. To specify
+ compatibility settings, select <guilabel>Configure advanced boot
+ loader options</guilabel>. This causes a second screen of options
+ to appear when you choose <guibutton>Next</guibutton>.
+ <xref linkend="sn-bootloader-advanced"/> explains the features of
+ the additional screen.
+ </para>
</section>
<section id="sn-bootloader-others">
<title>Booting Additional Operating Systems</title>
@@ -249,17 +259,23 @@
</para>
<para>
- Tto keep your current boot loader in the <abbrev>MBR</abbrev>, use
- the advanced settings to place <application>GRUB</application> in
- the first sector of the partition holding the Linux root file
- system.
+ To keep your current boot loader in the <abbrev>MBR</abbrev> and
+ install GRUB as a secondary boot loader, use the advanced settings
+ to place <application>GRUB</application> in the first sector of
+ the partition holding the Linux root file system.
</para>
<para>
You may also need the advanced options if your
- <abbrev>BIOS</abbrev> enumerates your disk devices differently
- than &FC; expects. On a few systems, &FC; may not configure the
- disk drive geometry for large disks correctly because of a broken
+ <abbrev>BIOS</abbrev> enumerates your drives or RAID arrays
+ differently than &FC; expects. If necessary, use the
+ <guibutton>Change Drive Order</guibutton> dialog to set the order
+ of the devices in &FC; to match your BIOS.
+ </para>
+
+ <para>
+ On a few systems, &FC; may not configure the disk drive geometry
+ for large disks correctly because of limitations within the
<abbrev>BIOS</abbrev>. To work around this problem, mark the
<guibutton>Force LBA32</guibutton> checkbox.
</para>
Index: fedora-install-guide-diskpartitioning-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-diskpartitioning-en.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- fedora-install-guide-diskpartitioning-en.xml 10 Dec 2005 17:51:38 -0000 1.16
+++ fedora-install-guide-diskpartitioning-en.xml 2 Feb 2006 00:12:55 -0000 1.17
@@ -5,11 +5,30 @@
<para>
&FC; creates and uses several <firstterm>partitions</firstterm> on
the available hard drives. You may customize both the partitions,
- and how the drives on your system are managed. On systems with more
- than one hard drive you may also configure &FC; to operate several
- drives as a group, or array, with RAID. Partitions and RAID arrays
- are explained in <xref linkend="sn-partitioning-general"/>, and
- <xref linkend="sn-disk-druid"/>.
+ and how the drives on your system are managed.
+ <xref linkend="sn-partitioning-general"/> explains drive partitions
+ in more detail.
+ </para>
+ <important>
+ <title>Configuring RAID Devices</title>
+
+ <para>
+ <indexterm>
+ <primary>RAID</primary>
+ <secondary>hardware</secondary>
+ </indexterm>
+ <firstterm>RAID</firstterm> facilities enable a group, or array,
+ of drives to act as a single device. Configure any RAID functions
+ provided by your mainboard, or attached controller cards, before
+ you install &FC;. Active RAID arrays appear as one drive.
+ </para>
+ </important>
+<!-- SE: Note that this chapter uses the term "Linux software RAID" to differentiate RAID provided by the kernel from the functions of ATA RAID controllers, which are often also called "software RAID". Unfortunately. -->
+ <para>
+ On systems with more than one hard drive you may configure &FC; to
+ operate several of the drives as a Linux RAID array without
+ requiring any additional hardware. Linux software RAID arrays are
+ explained in <xref linkend="sn-disk-druid"/>.
</para>
<note>
<title>Changing Your Mind</title>
@@ -129,33 +148,39 @@
</para>
<para>
- Data partitions have a <indexterm>
- <primary>mount point</primary>
- </indexterm> <firstterm>mount point</firstterm>. The mount point
- indicates the directory whose contents reside on that partition. A
- partition with no mount point is not accessible by users. Data not
- located on any other partition resides in the
- <filename>/</filename> (or <indexterm>
- <primary>partition</primary>
- <secondary>root</secondary>
- </indexterm> <firstterm>root</firstterm>) partition.
+ Data partitions have a
+ <indexterm>
+ <primary>mount point</primary>
+ </indexterm>
+ <firstterm>mount point</firstterm>. The mount point indicates the
+ directory whose contents reside on that partition. A partition
+ with no mount point is not accessible by users. Data not located
+ on any other partition resides in the <filename>/</filename> (or
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm>
+ <firstterm>root</firstterm>) partition.
</para>
<important>
<title>Root and <filename>/root</filename></title>
<para>
- The <filename>/</filename> (or <indexterm>
- <primary>partition</primary>
- <secondary>root</secondary>
- </indexterm> root) partition is the top of the directory
- structure. The <indexterm>
- <primary>partition</primary>
- <secondary><filename>/root</filename>
- </secondary>
- </indexterm> <filename>/root</filename> (sometimes pronounced
- "slash-root") directory is the home directory of the user
- account for system administration.
+ The <filename>/</filename> (or
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm>
+ root) partition is the top of the directory structure. The
+ <indexterm>
+ <primary>partition</primary>
+ <secondary><filename>/root</filename>
+ </secondary>
+ </indexterm>
+ <filename>/root</filename> (sometimes pronounced "slash-root")
+ directory is the home directory of the user account for system
+ administration.
</para>
</important>
@@ -205,25 +230,31 @@
<title>Partition Types</title>
<para>
- Every partition has a <indexterm>
- <primary>partition</primary>
- <secondary>type</secondary>
- <seealso>file system</seealso>
- </indexterm> <firstterm>partition type</firstterm>, to indicate
- the format of the <indexterm>
- <primary>file system</primary>
- </indexterm> <firstterm>file system</firstterm> on that
- partition. The file system enables Linux to organize, search,
- and retrieve files stored on that partition. Use the <indexterm>
- <primary><systemitem
+ Every partition has a
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>type</secondary>
+ <seealso>file system</seealso>
+ </indexterm>
+ <firstterm>partition type</firstterm>, to indicate the format of
+ the
+ <indexterm>
+ <primary>file system</primary>
+ </indexterm>
+ <firstterm>file system</firstterm> on that partition. The file
+ system enables Linux to organize, search, and retrieve files
+ stored on that partition. Use the
+ <indexterm>
+ <primary><systemitem
class="filesystem">ext3</systemitem>
- </primary>
- <see>file system</see>
- </indexterm><indexterm>
- <primary>file system</primary>
- <secondary
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary
sortas="filesystem"><systemitem>ext3</systemitem>
- </secondary>
+ </secondary>
</indexterm>
<systemitem
class="filesystem"><firstterm>ext3</firstterm></systemitem>
@@ -236,27 +267,32 @@
<section id="sn-partitioning-lvm">
<title>Understanding LVM</title>
<indexterm>
- <primary>LVM</primary>
- <secondary>understanding</secondary>
+ <primary>LVM</primary>
+ <secondary>understanding</secondary>
</indexterm>
<para>
LVM (Logical Volume Management) partitions provide a number of
advantages over standard partitions. LVM partitions are
- formatted as <indexterm>
- <primary>LVM</primary>
- <secondary>physical volume</secondary>
- </indexterm> <firstterm>physical volumes</firstterm>. One or
- more physical volumes are combined to form a <indexterm>
- <primary>LVM</primary>
- <secondary>volume group</secondary>
- </indexterm> <firstterm>volume group</firstterm>. Each volume
- group's total storage is then divided into one or more
+ formatted as
<indexterm>
- <primary>LVM</primary>
- <primary>logical volume</primary>
- </indexterm> <firstterm>logical volumes</firstterm>. The logical
- volumes function much like standard data partitions. They have a
- file system type, such as
+ <primary>LVM</primary>
+ <secondary>physical volume</secondary>
+ </indexterm>
+ <firstterm>physical volumes</firstterm>. One or more physical
+ volumes are combined to form a
+ <indexterm>
+ <primary>LVM</primary>
+ <secondary>volume group</secondary>
+ </indexterm>
+ <firstterm>volume group</firstterm>. Each volume group's total
+ storage is then divided into one or more
+ <indexterm>
+ <primary>LVM</primary>
+ <primary>logical volume</primary>
+ </indexterm>
+ <firstterm>logical volumes</firstterm>. The logical volumes
+ function much like standard data partitions. They have a file
+ system type, such as
<systemitem
class="filesystem">ext3</systemitem>, and a mount
point.
@@ -265,9 +301,9 @@
<para>
An administrator may grow or shrink logical volumes without
destroying data, unlike standard disk partitions. If the
- physical volumes in a volume group are on separate drives then
- administrators may also spread a logical volume across multiple
- disks and RAID arrays.
+ physical volumes in a volume group are on separate drives or
+ RAID arrays then administrators may also spread a logical volume
+ across the storage devices.
</para>
<note>
@@ -319,16 +355,22 @@
<para>
<indexterm>
- <primary>Disk Druid</primary>
- </indexterm> <application><firstterm>Disk
- Druid</firstterm></application> is an interactive program for
- editing disk partitions. Users run it only within the &FC;
- installation system. Disk Druid supports <indexterm>
- <primary>RAID</primary>
- </indexterm> <firstterm>RAID</firstterm> and <indexterm>
- <primary>LVM</primary>
- </indexterm> <firstterm>LVM</firstterm> to provide more extensible
- and reliable data storage.
+ <primary>Disk Druid</primary>
+ </indexterm>
+ <application><firstterm>Disk Druid</firstterm></application> is an
+ interactive program for editing disk partitions. Users run it only
+ within the &FC; installation system. Disk Druid enables you to
+ configure
+ <indexterm>
+ <primary>RAID</primary>
+ <secondary>Linux software</secondary>
+ </indexterm>
+ Linux software RAID and
+ <indexterm>
+ <primary>LVM</primary>
+ </indexterm>
+ <firstterm>LVM</firstterm> to provide more extensible and reliable
+ data storage.
</para>
<figure id="fig-disk-setup">
<title>Disk Setup Screen</title>
@@ -354,13 +396,15 @@
<term><guilabel>New</guilabel></term>
<listitem>
<para>
- Select this option to add a partition <indexterm>
- <primary>partition</primary>
- <secondary>adding</secondary>
- </indexterm> or LVM physical volume to the disk. In the
- <guilabel>Add partition</guilabel> dialog, choose a mount
- point and a partition type. If you have more than one disk
- on the system, choose which disks the partition may inhabit.
+ Select this option to add a partition
+ <indexterm>
+ <primary>partition</primary>
+ <secondary>adding</secondary>
+ </indexterm>
+ or LVM physical volume to the disk. In the <guilabel>Add
+ partition</guilabel> dialog, choose a mount point and a
+ partition type. If you have more than one disk on the
+ system, choose which disks the partition may inhabit.
Indicate a size in megabytes for the partition.
</para>
<important>
@@ -368,9 +412,10 @@
<para>
<indexterm>
- <primary>partition</primary>
- <secondary>illegal</secondary>
- </indexterm> The <filename>/bin/</filename>,
+ <primary>partition</primary>
+ <secondary>illegal</secondary>
+ </indexterm>
+ The <filename>/bin/</filename>,
<filename>/dev/</filename>, <filename>/etc/</filename>,
<filename>/lib/</filename>, <filename>/proc/</filename>,
<filename>/root/</filename>, and
@@ -378,9 +423,10 @@
for separate partitions in <application>Disk
Druid</application>. These directories reside on the
<indexterm>
- <primary>partition</primary>
- <secondary>root</secondary>
- </indexterm> <filename>/</filename> (root) partition.
+ <primary>partition</primary>
+ <secondary>root</secondary>
+ </indexterm>
+ <filename>/</filename> (root) partition.
</para>
<para>
@@ -445,12 +491,12 @@
<para>
Select this option to edit an existing partition,
<indexterm>
- <primary>partition</primary>
- <secondary>editing</secondary>
- </indexterm> LVM volume group, or an LVM physical volume
- that is not yet part of a volume group. To change the size
- of a LVM physical volume partition, first remove it from any
- volume groups.
+ <primary>partition</primary>
+ <secondary>editing</secondary>
+ </indexterm>
+ LVM volume group, or an LVM physical volume that is not yet
+ part of a volume group. To change the size of a LVM physical
+ volume partition, first remove it from any volume groups.
</para>
<warning>
<title>Removing LVM Physical Volumes</title>
@@ -489,29 +535,32 @@
<para>
You may not label Windows partitions that use the
<indexterm>
- <primary><systemitem
+ <primary><systemitem
class="filesystem">NTFS</systemitem>
- </primary>
- <see>file system</see>
- </indexterm> <indexterm>
- <primary>file system</primary>
- <secondary><systemitem
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary><systemitem
class="filesystem">NTFS</systemitem>
- </secondary>
+ </secondary>
</indexterm>
<systemitem
class="filesystem">NTFS</systemitem> file
system with a mount point in the &FC; installer. You may
- label <indexterm>
- <primary><systemitem
+ label
+ <indexterm>
+ <primary><systemitem
class="filesystem">vfat</systemitem>
- </primary>
- <see>file system</see>
- </indexterm> <indexterm>
- <primary>file system</primary>
- <secondary><systemitem
+ </primary>
+ <see>file system</see>
+ </indexterm>
+ <indexterm>
+ <primary>file system</primary>
+ <secondary><systemitem
class="filesystem">vfat</systemitem>
- </secondary>
+ </secondary>
</indexterm>
<systemitem
class="filesystem"><firstterm>vfat</firstterm></systemitem>
@@ -534,11 +583,12 @@
installation program allows you to erase or retain data on
specific partitions. If your user data is on a separate
<indexterm>
- <primary>partition</primary>
- <secondary><filename>/home</filename>
- </secondary>
- </indexterm> <filename>/home</filename> partition, you may
- retain that data while erasing system partitions such as
+ <primary>partition</primary>
+ <secondary><filename>/home</filename>
+ </secondary>
+ </indexterm>
+ <filename>/home</filename> partition, you may retain that
+ data while erasing system partitions such as
<filename>/boot</filename>.
</para>
</listitem>
@@ -550,11 +600,12 @@
<para>
Select this option to erase an existing partition
<indexterm>
- <primary>partition</primary>
- <secondary>deleting</secondary>
- </indexterm> or LVM physical volume. To delete an LVM
- physical volume, first delete any volume groups of which
- that physical volume is a member.
+ <primary>partition</primary>
+ <secondary>deleting</secondary>
+ </indexterm>
+ or LVM physical volume. To delete an LVM physical volume,
+ first delete any volume groups of which that physical volume
+ is a member.
</para>
<para>
If you make a mistake, use the <guilabel>Reset</guilabel>
@@ -578,9 +629,11 @@
<term><guilabel>RAID</guilabel></term>
<listitem>
<para>
- Select this button to set up software RAID <indexterm>
- <primary>RAID</primary>
- </indexterm> on your &FED; system.
+ Select this button to set up software RAID
+ <indexterm>
+ <primary>RAID</primary>
+ </indexterm>
+ on your &FED; system.
</para>
<variablelist>
<varlistentry>
@@ -627,11 +680,13 @@
<term><guilabel>LVM</guilabel></term>
<listitem>
<para>
- Select this button to set up LVM <indexterm>
- <primary>LVM</primary>
- </indexterm> on your &FED; system. First create at least one
- partition or software RAID device as an LVM physical volume,
- using the <application>New</application> dialog.
+ Select this button to set up LVM
+ <indexterm>
+ <primary>LVM</primary>
+ </indexterm>
+ on your &FED; system. First create at least one partition or
+ software RAID device as an LVM physical volume, using the
+ <application>New</application> dialog.
</para>
<para>
To assign one or more physical volumes to a volume group,
Index: fedora-install-guide-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-en.xml,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- fedora-install-guide-en.xml 29 Jan 2006 20:37:55 -0000 1.41
+++ fedora-install-guide-en.xml 2 Feb 2006 00:12:55 -0000 1.42
@@ -6,14 +6,14 @@
<!ENTITY DOCNAME "fedora-install-guide">
<!ENTITY DOCLANG "en">
-<!ENTITY DOCVERSION "1.16">
-<!ENTITY DOCDATE "2006-01-29">
+<!ENTITY DOCVERSION "1.17">
+<!ENTITY DOCDATE "2006-02-02">
<!ENTITY DOCID "&DOCNAME;-&DOCLANG;-&DOCVERSION; (&DOCDATE;)">
<!-- Bugzilla bug number for the draft notice -->
<!ENTITY BUG-NUM "129911">
<!ENTITY FCLOCALVER "5">
-<!ENTITY DOCLOCALVER "1.16"> <!-- what's this for again? -->
+<!ENTITY DOCLOCALVER "1.17"> <!-- what's this for again? -->
<!ENTITY FDP-INFO SYSTEM "fdp-info-en.xml" >
<!ENTITY INTRODUCTION SYSTEM "fedora-install-guide-intro-en.xml">
Index: fedora-install-guide-packageselection-en.xml
===================================================================
RCS file: /cvs/docs/install-guide/fedora-install-guide-packageselection-en.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- fedora-install-guide-packageselection-en.xml 29 Jan 2006 20:37:55 -0000 1.18
+++ fedora-install-guide-packageselection-en.xml 2 Feb 2006 00:12:55 -0000 1.19
@@ -5,8 +5,9 @@
<remark role="FIXME">TEXT SUBJECT TO CHANGE: The package selection screen is still being developed.</remark>
<para>
By default, the &FED; installation process loads a selection of
- software that is suitable for a desktop system. The package selection screen enables
- you to customize the set of software to match your requirements.
+ software that is suitable for a desktop system. The package
+ selection screen enables you to customize the set of software to
+ match your requirements.
</para>
<para>
&FED; divides included software into
@@ -81,13 +82,59 @@
</menuchoice>.
</para>
</tip>
- <section id="sn-mandatory-packages">
- <title>Core Software</title>
- <para>
- <remark role="FIXME">Mention some base stuff that is part of every &FC; system: SMTP, SSH, CUPS, NFS, Python and <command>yum</command>...</remark>
- </para>
- </section>
+ <section id="sn-mandatory-services">
+ <title>Core Network Services</title>
+
+ <para>
+ All Fedora Core installations run the following network services:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ email through SMTP (Simple Mail Transfer Protocol)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ network file sharing through NFS (Network File System)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ remote access through SSH (Secure SHell)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The default installation also includes:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ printing through CUPS (Common UNIX Printing System)
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Some automated processes on your Fedora system use the email
+ service to send reports and messages to the system administrator.
+ By default, the email and printing services do not accept
+ connections from other systems. Although Fedora connects to NFS
+ services on other systems, the NFS sharing component is disabled
+ by default. You may configure your Fedora system after
+ installation to offer email, NFS, or print services.
+ </para>
+
+ <para>
+ The SSH service is enabled by default. This enables administrators
+ to remotely access systems immediately after the installation
+ process completes.
+ </para>
+ </section>
<section id="sn-lang-packages">
<title>Additional Language Support</title>
@@ -107,13 +154,14 @@
difficult, and not recommended.
</para>
</warning>
+
+ <para>
+ After you choose the desired packages, select
+ <guilabel>Next</guilabel> to proceed. &FC; checks your selection,
+ and automatically adds any extra packages required to use the
+ software you select.
+ </para>
</section>
- <para>
- After you choose the desired packages, select
- <guilabel>Next</guilabel> to proceed. &FC; checks your selection,
- and automatically adds any extra packages required to use the
- software you select.
- </para>
</chapter>
<!--
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- rpm-info.xml 29 Jan 2006 20:37:55 -0000 1.6
+++ rpm-info.xml 2 Feb 2006 00:12:55 -0000 1.7
@@ -28,10 +28,15 @@
<!--PLEASE ADD A TRANSLATION FOR EACH ADDITIONAL LANGUAGE.-->
</titles>
<changelog order="newest-first">
+ <revision date="2006-02-02" number="1.17" role="doc">
+ <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+ <details>Added section on remote logging.</details>
+ </revision>
<revision date="2006-01-29" number="1.16" role="doc">
<author worker="StuartEllis"/>
<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
- <details>Updated indexing.</details>
+ <details lang="en">Updated indexing.</details>
</revision>
<revision date="2006-01-26" number="1.15" role="doc">
<author worker="StuartEllis"/>
More information about the Fedora-docs-commits
mailing list