summaryrefslogtreecommitdiff
path: root/en/boot-installer/ia64.xml
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2006-12-09 19:03:58 +0000
committerFrans Pop <elendil@planet.nl>2006-12-09 19:03:58 +0000
commit82733c090b72f30b064d1a656c5214b2e57bd8c6 (patch)
tree80bd6a756250bd2012d1c6dc4c63a5ecdb933d3c /en/boot-installer/ia64.xml
parent7cdbdbc52b18b9aebb345aa46f982f17b8a5e3d7 (diff)
downloadinstallation-guide-82733c090b72f30b064d1a656c5214b2e57bd8c6.zip
Fix inconsistencies in architecture names; thanks to Tapio Lehtonen
Diffstat (limited to 'en/boot-installer/ia64.xml')
-rw-r--r--en/boot-installer/ia64.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/en/boot-installer/ia64.xml b/en/boot-installer/ia64.xml
index 3fa028406..be6fb04fb 100644
--- a/en/boot-installer/ia64.xml
+++ b/en/boot-installer/ia64.xml
@@ -337,7 +337,7 @@ set up the language locale, network, and disk partitions.
<sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title>
<para>
-Booting an IA64 system from the network is similar to a CD boot.
+Booting an IA-64 system from the network is similar to a CD boot.
The only difference is how the installation kernel is loaded.
The EFI Boot Manager can load and start programs from a server on
the network.
@@ -352,7 +352,7 @@ rather than the CD drive.
<para>
-Network booting an ia64 system requires two architecture-specific actions.
+Network booting an IA-64 system requires two architecture-specific actions.
On the boot server, DHCP and TFTP must be configured to deliver
<command>elilo</command>.
On the client a new boot option must be defined in the EFI boot manager
@@ -364,7 +364,7 @@ to enable loading over a network.
<title>Configuring the Server</title>
<para>
-A suitable TFTP entry for network booting an ia64 system looks something
+A suitable TFTP entry for network booting an IA-64 system looks something
like this:
<informalexample><screen>