install-guide/en_US entities.xml, 1.6, 1.7 fedora-install-guide-intro.xml, 1.4, 1.5
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29456/en_US
Modified Files:
entities.xml fedora-install-guide-intro.xml
Log Message:
- Replaced use of cat /proc/mounts with dmesg, which makes the instructions a bit tidier.
Index: entities.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/entities.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- entities.xml 30 Apr 2006 21:21:03 -0000 1.6
+++ entities.xml 30 Apr 2006 22:15:07 -0000 1.7
@@ -14,7 +14,7 @@
</entity>
<entity name="DOCVERSION">
<comment>Document version</comment>
- <text>1.31</text>
+ <text>1.32</text>
</entity>
<entity name="DOCDATE">
<comment>Document date</comment>
Index: fedora-install-guide-intro.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/fedora-install-guide-intro.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-intro.xml 30 Apr 2006 21:33:05 -0000 1.4
+++ fedora-install-guide-intro.xml 30 Apr 2006 22:15:07 -0000 1.5
@@ -557,9 +557,17 @@
</para>
<para>
- The <command>dd</command> utility requires the name of the
- device file that corresponds to the physical media. To learn the
- device file, carry out the following steps:
+ The <command>dd</command> utility requires you to specify the
+ device file that corresponds to the physical media. The name of
+ the device file matches the name assigned to the device by your
+ system. All device files appear in the directory
+ <filename>/dev/</filename>. For example,
+ <filename>/dev/sda</filename> denotes the first USB or SCSI
+ device that is attached to the system.
+ </para>
+
+ <para>
+ To learn the name that your system assigns to the media:
</para>
<procedure>
<step>
@@ -573,23 +581,20 @@
</step>
<step>
<para>
- Type this command, to show the currently attached drives:
+ Attach or insert the media.
</para>
-<screen>
-<userinput>cat /proc/mounts</userinput>
-</screen>
</step>
<step>
<para>
- Attach or insert the media.
+ In the terminal window, type the following command:
</para>
- </step>
- <step>
+<screen>
+<userinput>dmesg</userinput>
+</screen>
<para>
- Enter <userinput>cat /proc/mounts</userinput> again. The
- media appears as a new entry at the bottom of the list. Note
- the device file for the media, which appears in the first
- column for the entry.
+ Look for the items in the <command>dmesg</command> output
+ that relate to the detection of a new SCSI device. Linux
+ systems treat USB media as forms of SCSI device.
</para>
</step>
<step>
@@ -610,7 +615,7 @@
</procedure>
<para>
To write an image file to boot media with <command>dd</command>
- on a current version of &FC;:
+ on a current version of &FC;, carry out the following steps:
</para>
<procedure>
<step>
17 years, 10 months
install-guide rpm-info.xml,1.22,1.23
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29456
Modified Files:
rpm-info.xml
Log Message:
- Replaced use of cat /proc/mounts with dmesg, which makes the instructions a bit tidier.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- rpm-info.xml 30 Apr 2006 21:21:02 -0000 1.22
+++ rpm-info.xml 30 Apr 2006 22:15:06 -0000 1.23
@@ -28,10 +28,15 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="2006-04-30" number="1.32" role="doc">
+ <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+ <details>Amended USB media instructions to use dmesg.</details>
+ </revision>
<revision date="2006-04-30" number="1.31" role="doc">
<author worker="StuartEllis"/>
<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
- <details>Improved LVM and partitioning information.</details>
+ <details lang="en_US">Improved LVM and partitioning information.</details>
</revision>
<revision date="2006-04-30" number="1.30" role="doc">
<author worker="StuartEllis"/>
17 years, 10 months
install-guide/en_US fedora-install-guide-intro.xml,1.3,1.4
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26921/en_US
Modified Files:
fedora-install-guide-intro.xml
Log Message:
- Amended typo.
Index: fedora-install-guide-intro.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/fedora-install-guide-intro.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide-intro.xml 30 Apr 2006 18:28:28 -0000 1.3
+++ fedora-install-guide-intro.xml 30 Apr 2006 21:33:05 -0000 1.4
@@ -576,7 +576,7 @@
Type this command, to show the currently attached drives:
</para>
<screen>
-<userinput>ls /proc/mounts</userinput>
+<userinput>cat /proc/mounts</userinput>
</screen>
</step>
<step>
@@ -586,7 +586,7 @@
</step>
<step>
<para>
- Enter <userinput>ls /proc/mounts</userinput> again. The
+ Enter <userinput>cat /proc/mounts</userinput> again. The
media appears as a new entry at the bottom of the list. Note
the device file for the media, which appears in the first
column for the entry.
17 years, 10 months
install-guide/en_US entities.xml, 1.5, 1.6 fedora-install-guide-acknowledgements.xml, 1.1, 1.2 fedora-install-guide-diskpartitioning.xml, 1.1, 1.2
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26571/en_US
Modified Files:
entities.xml fedora-install-guide-acknowledgements.xml
fedora-install-guide-diskpartitioning.xml
Log Message:
- Amended text to clarify LVM, based on the changes proposed in bug 170728, comment 12.
Index: entities.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/entities.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- entities.xml 30 Apr 2006 18:28:28 -0000 1.5
+++ entities.xml 30 Apr 2006 21:21:03 -0000 1.6
@@ -14,7 +14,7 @@
</entity>
<entity name="DOCVERSION">
<comment>Document version</comment>
- <text>1.30</text>
+ <text>1.31</text>
</entity>
<entity name="DOCDATE">
<comment>Document date</comment>
Index: fedora-install-guide-acknowledgements.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/fedora-install-guide-acknowledgements.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-acknowledgements.xml 17 Mar 2006 19:40:20 -0000 1.1
+++ fedora-install-guide-acknowledgements.xml 30 Apr 2006 21:21:03 -0000 1.2
@@ -17,7 +17,7 @@
<para>
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.
+ additional information on boot loader and RAID configurations. The sections on LVM benefited from the contributions of Bob McKay.
</para>
</chapter>
Index: fedora-install-guide-diskpartitioning.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/fedora-install-guide-diskpartitioning.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide-diskpartitioning.xml 17 Mar 2006 19:40:20 -0000 1.1
+++ fedora-install-guide-diskpartitioning.xml 30 Apr 2006 21:21:03 -0000 1.2
@@ -169,17 +169,39 @@
<para>
Many systems have more partitions than the minimum listed above.
- Choose partitions based on your particular system needs. If you
- are not sure how best to configure the partitions for your
+ Choose partitions based on your particular system needs. For
+ example, consider creating a separate <filename>/home</filename>
+ partition on systems that store user data, for the reasons
+ explained in <xref linkend="sn-partitioning-home"/>.
+ </para>
+
+ <para>
+ If you are not sure how best to configure the partitions for your
computer, accept the default partition layout.
</para>
<para>
- Data partitions have a
+ The RAM installed in your computer provides a pool of memory for
+ running systems. Linux systems use
+ <indexterm>
+ <primary>swap partitions</primary>
+ </indexterm>
+ <firstterm>swap</firstterm> partitions to expand this pool, by
+ automatically moving portions of memory between RAM and swap
+ partitions if insufficient RAM is available. In addition, certain
+ power management features store all of the memory for a suspended
+ system in the available swap partitions. If you manually specify
+ the partitions on your system, create one swap partition that has
+ more capacity than the computer RAM.
+ </para>
+
+ <para>
+ Data partitions provide storage for files. Each data partition has
+ a
<indexterm>
<primary>mount point</primary>
</indexterm>
- <firstterm>mount point</firstterm>. The mount point indicates the
+ <firstterm>mount point</firstterm>, to indicate the system
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
@@ -325,13 +347,24 @@
<secondary>logical volume</secondary>
</indexterm>
<firstterm>logical volumes</firstterm>. The logical volumes
- function much like standard data partitions. They have a file
- system type, such as
+ function much like standard partitions. They have a file system
+ type, such as
<systemitem
class="filesystem">ext3</systemitem>, and a mount
point.
</para>
+ <note>
+ <title>The <filename>/boot</filename> Partition and LVM</title>
+
+ <para>
+ Only an active Linux system may read or write to LVM volumes.
+ For this reason, the <filename>/boot</filename> partition that
+ initializes your system must be held outside of the LVM
+ physical volumes.
+ </para>
+ </note>
+
<para>
An administrator may grow or shrink logical volumes without
destroying data, unlike standard disk partitions. If the
@@ -342,18 +375,20 @@
<para>
You may lose data if you shrink a logical volume to a smaller
- capacity than the data on the volume requires. For this reason,
- create logical volumes to meet your current needs, and leave
- excess storage capacity unallocated. You may safely grow logical
- volumes to use unallocated space, as your needs dictate.
+ capacity than the data on the volume requires. To ensure maximum
+ flexibility, create logical volumes to meet your current needs,
+ and leave excess storage capacity unallocated. You may safely
+ grow logical volumes to use unallocated space, as your needs
+ dictate.
</para>
<note>
<title>LVM and the Default Partition Layout</title>
<para>
- By default, the installation process creates partitions within
- LVM volumes.
+ By default, the installation process creates data and swap
+ partitions within LVM volumes, with a separate
+ <filename>/boot</filename> partition.
</para>
</note>
</section>
@@ -364,7 +399,7 @@
<para>
If you expect that you or other users will store data on the
system, create a separate partition for the
- <filename>/home</filename> directory within an LVM volume. With
+ <filename>/home</filename> directory within a volume group. With
a separate <filename>/home</filename> partition, you may upgrade
or reinstall &FC; without erasing user data files. LVM provides
you with the ability to add more storage capacity for the user
@@ -414,6 +449,18 @@
<firstterm>LVM</firstterm> to provide more extensible and reliable
data storage.
</para>
+
+ <note>
+ <title>Modifying the Default LVM Layout</title>
+
+ <para>
+ The default layout pools all of the available storage into a
+ single LVM physical volume, with one LVM logical volume for the
+ system. To make capacity available for additional partitions,
+ <guibutton>Edit</guibutton> the logical volume with the mount
+ point <filename>/</filename>, and reduce it's size as necessary.
+ </para>
+ </note>
<figure id="fig-disk-setup">
<title>Disk Setup Screen</title>
<mediaobject>
17 years, 10 months
install-guide rpm-info.xml,1.21,1.22
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26571
Modified Files:
rpm-info.xml
Log Message:
- Amended text to clarify LVM, based on the changes proposed in bug 170728, comment 12.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- rpm-info.xml 30 Apr 2006 18:28:28 -0000 1.21
+++ rpm-info.xml 30 Apr 2006 21:21:02 -0000 1.22
@@ -28,10 +28,15 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="2006-04-30" number="1.31" role="doc">
+ <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+ <details>Improved LVM and partitioning information.</details>
+ </revision>
<revision date="2006-04-30" number="1.30" role="doc">
<author worker="StuartEllis"/>
<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
- <details>Amended section on formatting USB media.</details>
+ <details lang="en_US">Amended section on formatting USB media.</details>
</revision>
<revision date="2006-04-30" number="1.29" role="doc">
<author worker="StuartEllis"/>
17 years, 10 months
install-guide/en_US entities.xml, 1.4, 1.5 fedora-install-guide-intro.xml, 1.2, 1.3
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18301/en_US
Modified Files:
entities.xml fedora-install-guide-intro.xml
Log Message:
- Fixed bug 186114.
Index: entities.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/entities.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- entities.xml 4 Apr 2006 00:26:35 -0000 1.4
+++ entities.xml 30 Apr 2006 18:28:28 -0000 1.5
@@ -14,11 +14,11 @@
</entity>
<entity name="DOCVERSION">
<comment>Document version</comment>
- <text>1.28</text>
+ <text>1.30</text>
</entity>
<entity name="DOCDATE">
<comment>Document date</comment>
- <text>2006-04-04</text>
+ <text>2006-30-04</text>
</entity>
<entity name="DOCID">
<comment>Document ID string</comment>
Index: fedora-install-guide-intro.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/fedora-install-guide-intro.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-intro.xml 6 Apr 2006 03:42:16 -0000 1.2
+++ fedora-install-guide-intro.xml 30 Apr 2006 18:28:28 -0000 1.3
@@ -257,10 +257,11 @@
<para>
The &FP; maintains a list of HTTP and FTP public mirrors, sorted
- by region, at <ulink
- url="http://fedora.redhat.com/download/mirrors.html"/>.
- To determine the complete directory path for the
- installation files, add
+ by region, at
+ <ulink
+ url="http://fedora.redhat.com/download/mirrors.html"/>.
+ To determine the complete directory path for the installation
+ files, add
<filename>/&FCLOCALVER;/<replaceable>architecture</replaceable>/os/</filename>
to the path shown on the webpage.
</para>
@@ -453,81 +454,78 @@
directory for your particular architecture.
</para>
- <para>
- The &FC; distribution is also downloadable as a set of
- CD-sized ISO image files or a single DVD-sized ISO image
- file. You can record these files to CD or DVD using a CD or
- DVD burning program on your current operating system:
- </para>
-
- <variablelist>
- <varlistentry>
- <term>Windows operating systems</term>
- <listitem>
- <para>
- Burn an ISO image to disc using your installed CD or DVD
- burning software. Most software has an option labeled
- <guilabel>Burn image file to disc</guilabel> or
- <guilabel>Make disc from ISO image</guilabel>. If your
- software offers a choice of image formats, choose "ISO
- image" as the file type. If several ISO formats are
- offered, choose the closest match to "Mode 1, 2048-byte
- blocks."
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Apple MacOS X</term>
- <listitem>
- <para>
- Open the <guilabel>Disk Copy</guilabel> application,
- found in the
- <filename>/Applications/Utilities</filename> folder.
- From the menu, select <menuchoice>
- <guimenu>Image</guimenu>
- <guimenuitem>Burn Image...</guimenuitem>
- </menuchoice>. Select the CD image to burn, check that the
- burn options are correct, and select the
- <guilabel>Burn</guilabel> button.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Linux operating systems</term>
- <listitem>
- <para>
- If you are using a recent version of the GNOME desktop
- environment, right-click the ISO image file and choose
- <guilabel>Write to disc</guilabel>. If you are using a
- recent version of the KDE desktop environment, use
- <application>K3B</application> and select <menuchoice>
- <guimenu>Tools</guimenu>
- <guimenuitem>Burn CD Image</guimenuitem>
- </menuchoice>, or <menuchoice>
- <guimenu>Tools</guimenu>
- <guimenuitem>Burn DVD ISO Image</guimenuitem>
- </menuchoice> if appropriate. The following command
- line works for many other environments:
- </para>
+ <para>
+ The &FC; distribution is also downloadable as a set of CD-sized
+ ISO image files or a single DVD-sized ISO image file. You can
+ record these files to CD or DVD using a CD or DVD burning
+ program on your current operating system:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Windows operating systems</term>
+ <listitem>
+ <para>
+ Burn an ISO image to disc using your installed CD or DVD
+ burning software. Most software has an option labeled
+ <guilabel>Burn image file to disc</guilabel> or
+ <guilabel>Make disc from ISO image</guilabel>. If your
+ software offers a choice of image formats, choose "ISO
+ image" as the file type. If several ISO formats are
+ offered, choose the closest match to "Mode 1, 2048-byte
+ blocks."
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Apple MacOS X</term>
+ <listitem>
+ <para>
+ Open the <guilabel>Disk Copy</guilabel> application, found
+ in the <filename>/Applications/Utilities</filename>
+ folder. From the menu, select <menuchoice>
+ <guimenu>Image</guimenu> <guimenuitem>Burn
+ Image...</guimenuitem> </menuchoice>. Select the CD image
+ to burn, check that the burn options are correct, and
+ select the <guilabel>Burn</guilabel> button.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Linux operating systems</term>
+ <listitem>
+ <para>
+ If you are using a recent version of the GNOME desktop
+ environment, right-click the ISO image file and choose
+ <guilabel>Write to disc</guilabel>. If you are using a
+ recent version of the KDE desktop environment, use
+ <application>K3B</application> and select <menuchoice>
+ <guimenu>Tools</guimenu> <guimenuitem>Burn CD
+ Image</guimenuitem> </menuchoice>, or <menuchoice>
+ <guimenu>Tools</guimenu> <guimenuitem>Burn DVD ISO
+ Image</guimenuitem> </menuchoice> if appropriate. The
+ following command line works for many other environments:
+ </para>
<screen>
<userinput>cdrecord --device=<replaceable>cdwriter-device</replaceable> -tao -eject <replaceable>image-file.iso</replaceable></userinput>
</screen>
+ </listitem>
+ </varlistentry>
+ </variablelist>
- </listitem>
- </varlistentry>
- </variablelist>
- <note>
- <title>OS-Specific Instructions</title>
- <para>
- Unfortunately this guide cannot offer specific instructions
- for every possible combination of hardware and software.
- Consult your operating system's documentation and online
- support services, and <xref linkend="sn-web-help"/> for
- additional help if needed.
- </para>
- </note>
+ <note>
+ <title>System-Specific Instructions</title>
+ <para>
+ Unfortunately this guide cannot offer specific instructions
+ for every possible combination of hardware and software.
+ Consult your operating system's documentation and online
+ support services, and <xref linkend="sn-web-help"/> for
+ additional help if needed.
+ </para>
+ </note>
</section>
<section id="sn-preparing-usb-media">
@@ -555,9 +553,64 @@
<para>
Several software utilities are available for Windows and Linux
that can write image files to a device. Linux includes the
- <command>dd</command> command for this purpose. To write an
- image file to boot media with <command>dd</command> on a current
- version of &FC;:
+ <command>dd</command> command for this purpose.
+ </para>
+
+ <para>
+ The <command>dd</command> utility requires the name of the
+ device file that corresponds to the physical media. To learn the
+ device file, carry out the following steps:
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Open a terminal window. On a &FED; system, choose
+ <menuchoice><guimenu>Applications</guimenu>
+ <guisubmenu>Accessories</guisubmenu>
+ <guimenuitem>Terminal</guimenuitem> </menuchoice> to start a
+ terminal.
+ </para>
+ </step>
+ <step>
+ <para>
+ Type this command, to show the currently attached drives:
+ </para>
+<screen>
+<userinput>ls /proc/mounts</userinput>
+</screen>
+ </step>
+ <step>
+ <para>
+ Attach or insert the media.
+ </para>
+ </step>
+ <step>
+ <para>
+ Enter <userinput>ls /proc/mounts</userinput> again. The
+ media appears as a new entry at the bottom of the list. Note
+ the device file for the media, which appears in the first
+ column for the entry.
+ </para>
+ </step>
+ <step>
+ <para>
+ Unmount the media. On a &FED; system, right-click the icon
+ that corresponds to the media, and select
+ <guimenuitem>Unmount Volume</guimenuitem>. Alternatively,
+ enter this command in a terminal window:
+ </para>
+<screen>
+<userinput>umount <replaceable>/dev/sda</replaceable></userinput>
+</screen>
+ <para>
+ Replace <filename>/dev/sda</filename> with the name of the
+ correct device file for the media.
+ </para>
+ </step>
+ </procedure>
+ <para>
+ To write an image file to boot media with <command>dd</command>
+ on a current version of &FC;:
</para>
<procedure>
<step>
@@ -586,8 +639,12 @@
In the terminal window, type the following command:
</para>
<screen>
-<userinput>dd if=diskboot.img of=/dev/sda</userinput>
+<userinput>dd if=diskboot.img of=<replaceable>/dev/sda</replaceable></userinput>
</screen>
+ <para>
+ Replace <filename>/dev/sda</filename> with the name of the
+ correct device file for the media.
+ </para>
</step>
</procedure>
</section>
17 years, 10 months
install-guide rpm-info.xml,1.20,1.21
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18301
Modified Files:
rpm-info.xml
Log Message:
- Fixed bug 186114.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- rpm-info.xml 30 Apr 2006 14:03:27 -0000 1.20
+++ rpm-info.xml 30 Apr 2006 18:28:28 -0000 1.21
@@ -28,11 +28,15 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="2006-04-30" number="1.30" role="doc">
+ <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+ <details>Amended section on formatting USB media.</details>
+ </revision>
<revision date="2006-04-30" number="1.29" role="doc">
<author worker="StuartEllis"/>
<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
- <details>Noted that Fedora package tools require
- network access.</details>
+ <details lang="en_US">Noted that Fedora package tools require network access.</details>
</revision>
<revision date="2006-04-05" number="1.28.1" role="doc">
<author worker="PaulWFrields"/>
17 years, 10 months
yum-software-management/en_US doc-entities.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10485/en_US
Modified Files:
doc-entities.xml
Log Message:
- Amended entities file.
Index: doc-entities.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/doc-entities.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- doc-entities.xml 29 Mar 2006 23:49:44 -0000 1.1
+++ doc-entities.xml 30 Apr 2006 15:17:04 -0000 1.2
@@ -9,11 +9,11 @@
</entity>
<entity name="DOCVERSION">
<comment>Version number</comment>
- <text>1.3</text>
+ <text>1.31</text>
</entity>
<entity name="DOCDATE">
<comment>Date of last revision</comment>
- <text>2006-03-24</text>
+ <text>2006-04-30</text>
</entity>
<entity name="DOCID">
<comment>Document ID</comment>
17 years, 10 months
yum-software-management/en_US yum-software-management.xml,1.5,1.6
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8233/en_US
Modified Files:
yum-software-management.xml
Log Message:
- Amended search section, per bug 179483.
Index: yum-software-management.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/yum-software-management.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- yum-software-management.xml 24 Mar 2006 20:37:28 -0000 1.5
+++ yum-software-management.xml 30 Apr 2006 14:47:52 -0000 1.6
@@ -1006,9 +1006,8 @@
<para>
If you do not know the name of the package, use the
<option>search</option> or <option>provides</option> options.
- Alternatively, use wild cards or regular expressions with any
- <command>yum</command> search option to broaden the search
- criteria.
+ Alternatively, use wild cards with any <command>yum</command>
+ search option to broaden the search criteria.
</para>
<para>
@@ -1069,13 +1068,6 @@
<screen>
<userinput>su -c 'yum list <replaceable>tsc\*</replaceable>'</userinput>
</screen>
- <tip>
- <title>Regular Expressions</title>
- <para>
- Use Perl or Python regular expressions to carry out more
- complex queries.
- </para>
- </tip>
</section>
<section id="sn-package-matches">
@@ -1085,7 +1077,7 @@
Searches with <command>yum</command> show all of the packages
that match your criteria. Packages must meet the terms of the
search exactly to be considered matches, unless you use
- wild-cards or a regular expression.
+ wild-cards.
</para>
<para>
17 years, 10 months
yum-software-management rpm-info.xml,1.5,1.6
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8233
Modified Files:
rpm-info.xml
Log Message:
- Amended search section, per bug 179483.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/rpm-info.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- rpm-info.xml 24 Mar 2006 20:37:13 -0000 1.5
+++ rpm-info.xml 30 Apr 2006 14:47:51 -0000 1.6
@@ -28,10 +28,15 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="2006-04-30" number="1.31" role="doc">
+ <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+ <details>Amended search section.</details>
+ </revision>
<revision date="2006-03-24" number="1.3" role="doc">
<author worker="StuartEllis"/>
<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
- <details>Minor restructuring of sections.</details>
+ <details lang="en_US">Minor restructuring of sections.</details>
</revision>
<revision date="2006-03-19" number="1.2" role="doc">
<author worker="StuartEllis"/>
17 years, 10 months