release-notes/devel/en_US ArchSpecific.xml,1.10,1.11
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Tue Sep 26 05:31:51 UTC 2006
Author: kwade
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11438
Modified Files:
ArchSpecific.xml
Log Message:
XML fixes to match test3 usage.
Index: ArchSpecific.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/ArchSpecific.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- ArchSpecific.xml 24 Sep 2006 23:08:53 -0000 1.10
+++ ArchSpecific.xml 26 Sep 2006 05:31:49 -0000 1.11
@@ -17,23 +17,23 @@
<para>
<emphasis role='strong'>RPM</emphasis> supports parallel installation of
multiple architectures of the same package. A default package listing such
- as <code>rpm -qa</code> might appear to include duplicate packages, since
- the architecture is not displayed. Instead, use the <code>repoquery</code>
- command, part of the <code>yum-utils</code> package in Fedora Extras,
- which displays architecture by default. To install <code>yum-utils</code>,
+ as <command>rpm -qa</command> might appear to include duplicate packages, since
+ the architecture is not displayed. Instead, use the <command>repoquery</command>
+ command, part of the <package>yum-utils</package> package in Fedora Extras,
+ which displays architecture by default. To install <package>yum-utils</package>,
run the following command:
</para>
<screen><![CDATA[su -c 'yum install yum-utils'
]]></screen>
<para>
To list all packages with their architecture using
- <code>rpm</code>, run the following command:
+ <command>rpm</command>, run the following command:
</para>
<screen><![CDATA[rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"
]]></screen>
<para>
- You can add this to <code>/etc/rpm/macros</code> (for a system
- wide setting) or <code>~/.rpmmacros</code> (for a per-user
+ You can add this to <filename>/etc/rpm/macros</filename> (for a system
+ wide setting) or <filename>~/.rpmmacros</filename> (for a per-user
setting). It changes the default query to list the architecture:
</para>
<screen><![CDATA[%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
@@ -57,7 +57,7 @@
</listitem>
<listitem>
<para>
- Fedora Core 6 supports only the “New World†generation of Apple
+ Fedora Core 6 supports only the "New World" generation of Apple
Power Macintosh, shipped from circa 1999 onward.
</para>
</listitem>
@@ -89,8 +89,8 @@
taken up by Fedora Core 6 after installation is complete. However,
additional disk space is required during installation to support the
installation environment. This additional disk space corresponds to
- the size of <code>/Fedora/base/stage2.img</code> (on Installation Disc
- 1) plus the size of the files in <code>/var/lib/rpm</code> on the
+ the size of <filename>/Fedora/base/stage2.img</filename> (on Installation Disc
+ 1) plus the size of the files in <filename>/var/lib/rpm</filename> on the
installed system.
</para>
<para>
@@ -110,13 +110,14 @@
<section>
<title>The Apple keyboard</title>
<para>
- The <code>Option</code> key on Apple systems is equivalent
- to the <code>Alt</code> key on the PC. Where documentation
- and the installer refer to the <code>Alt</code> key, use the
- <code>Option</code> key. For some key combinations you may
- need to use the <code>Option</code> key in conjunction with
- the <code>Fn</code> key, such as
- <code>Option</code>-<code>Fn</code>-<code>F3</code> to
+ The <keycap function="option">Option</keycap> key on Apple systems is equivalent
+ to the <keycap function="alt">Alt</keycap> key on the PC. Where documentation
+ and the installer refer to the <keycap function="alt">Alt</keycap> key, use the
+ <keycap function="option">Option</keycap> key. For some key combinations you may
+ need to use the <keycap function="option">Option</keycap> key in conjunction with
+ the <keycap function="other">Fn</keycap> key, such as
+ <keycombo>
+ <keycap function="option">Option</keycap><keycap function="other">Fn</keycap><keycap>F3</keycap></keycombo> to
switch to virtual terminal tty3.
</para>
</section>
@@ -125,7 +126,7 @@
<para>
Fedora Core Installation Disc 1 is bootable on supported
hardware. In addition, a bootable CD image appears in the
- <code>images/</code> directory of this disc. These images
+ <filename>images/</filename> directory of this disc. These images
behave differently according to your system hardware:
</para>
<itemizedlist>
@@ -135,10 +136,10 @@
appropriate 32-bit or 64-bit installer.
</para>
<para>
- The default <code>gnome-power-manager</code> package includes power
+ The default <package>gnome-power-manager</package> package includes power
management support, including sleep and backlight level management.
- Users with more complex requirements can use the <code>apmud</code>
- package in Fedora Extras. To install <code>apmud</code> after
+ Users with more complex requirements can use the <package>apmud</package>
+ package in Fedora Extras. To install <package>apmud</package> after
installation, use the following command:
</para>
</listitem>
@@ -153,7 +154,7 @@
</para>
<para>
After using Open<emphasis role='strong'/>Firmware to
- boot the CD, the bootloader, <code>yaboot</code>,
+ boot the CD, the bootloader, <command>yaboot</command>,
automatically boots the 64-bit installer.
</para>
</listitem>
@@ -164,7 +165,7 @@
<para>
So-called "Legacy" iSeries models, which do not use Open<emphasis
role='strong'/>Firmware, require use of the boot image located in
- the <code>images/iSeries</code> directory of the installation tree.
+ the <filename>images/iSeries</filename> directory of the installation tree.
</para>
</listitem>
<listitem>
@@ -173,7 +174,7 @@
</para>
<para>
After using Open<emphasis role='strong'/>Firmware to boot the CD,
- select the <code>linux32</code> boot image at the <code>boot:</code>
+ select the <filename>linux32</filename> boot image at the <prompt>boot:</prompt>
prompt to start the 32-bit installer. Otherwise, the 64-bit
installer starts and fails.
</para>
@@ -185,8 +186,7 @@
<para>
At the time of writing, firmware with full support for ISO9660 file
systems has not yet been released for the Pegasos. You can use the
- network boot image, however. At the Open<emphasis
- role='strong'/>Firmware prompt, enter the following command:
+ network boot image, however. At the OpenFirmware prompt, enter the following command:
</para>
</listitem>
</itemizedlist>
@@ -195,10 +195,10 @@
<itemizedlist>
<listitem override='none'>
<para>
- You must also configure Open<emphasis role='strong'/>Firmware on the
+ You must also configure OpenFirmware on the
Pegasos manually to make the installed Fedora Core system bootable.
- To do this, set the <code>boot-device</code> and
- <code>boot-file</code> environment variables appropriately.
+ To do this, set the <envar>boot-device</envar> and
+ <envar>boot-file</envar> environment variables appropriately.
</para>
</listitem>
<listitem>
@@ -207,14 +207,14 @@
</para>
<para>
Combined images containing the installer kernel and ramdisk are
- located in the <code>images/netboot/</code> directory of the
+ located in the <filename>images/netboot/</filename> directory of the
installation tree. They are intended for network booting with TFTP,
but can be used in many ways.
</para>
<para>
- The <code>yaboot</code> loader supports TFTP booting for IBM pSeries
+ The <command>yaboot</command> loader supports TFTP booting for IBM pSeries
and Apple Macintosh. The Fedora Project encourages the use of
- <code>yaboot</code> over the <code>netboot</code> images.
+ <command>yaboot</command> over the <command>netboot</command> images.
</para>
</listitem>
</itemizedlist>
@@ -287,8 +287,8 @@
is required during the installation to support the
installation environment. This additional disk space
corresponds to the size of
- <code>/Fedora/base/stage2.img</code> on Installation Disc
- 1 plus the size of the files in <code>/var/lib/rpm</code>
+ <filename>/Fedora/base/stage2.img</filename> on Installation Disc
+ 1 plus the size of the files in <filename>/var/lib/rpm</filename>
on the installed system.
</para>
<para>
@@ -349,8 +349,8 @@
is required during the installation to support the
installation environment. This additional disk space
corresponds to the size of
- <code>/Fedora/base/stage2.img</code> on Installation Disc
- 1 plus the size of the files in <code>/var/lib/rpm</code>
+ <filename>/Fedora/base/stage2.img</filename> on Installation Disc
+ 1 plus the size of the files in <filename>/var/lib/rpm</filename>
on the installed system.
</para>
<para>
More information about the Fedora-docs-commits
mailing list