summaryrefslogtreecommitdiff
path: root/eu/preparing
diff options
context:
space:
mode:
authorFrans Pop <elendil@planet.nl>2006-08-07 15:50:11 +0000
committerFrans Pop <elendil@planet.nl>2006-08-07 15:50:11 +0000
commit2d555470068ccdc434b41a8f438c3c2b56109305 (patch)
treec3f942e1ae8459d1784a4068401c8d764e01e5bf /eu/preparing
parenteaf56720ee96ae00de0acc841c8cfc7832bac7d7 (diff)
downloadinstallation-guide-2d555470068ccdc434b41a8f438c3c2b56109305.zip
Initial commit preparing to add variant for AMD64.
This commit basically creates the AMD64 variant as a copy of the i386 manual. Further commits will be needed to differentiate the AMD64 variant from i386 where needed. Commit includes changes for all translations.
Diffstat (limited to 'eu/preparing')
-rw-r--r--eu/preparing/bios-setup/i386.xml6
-rw-r--r--eu/preparing/minimum-hardware-reqts.xml2
-rw-r--r--eu/preparing/needed-info.xml10
-rw-r--r--eu/preparing/non-debian-partitioning.xml6
-rw-r--r--eu/preparing/nondeb-part/i386.xml2
-rw-r--r--eu/preparing/pre-install-bios-setup.xml12
6 files changed, 19 insertions, 19 deletions
diff --git a/eu/preparing/bios-setup/i386.xml b/eu/preparing/bios-setup/i386.xml
index 1ee5be4cd..f9f796155 100644
--- a/eu/preparing/bios-setup/i386.xml
+++ b/eu/preparing/bios-setup/i386.xml
@@ -2,7 +2,7 @@
<!-- original version: 11648 untranslated -->
- <sect2 arch="i386"><title>Invoking the BIOS Set-Up Menu</title>
+ <sect2 arch="x86"><title>Invoking the BIOS Set-Up Menu</title>
<para>
@@ -101,7 +101,7 @@ try using a shareware/freeware program. Try looking in
</para>
</sect2>
- <sect2 arch="i386" id="boot-dev-select"><title>Boot Device Selection</title>
+ <sect2 arch="x86" id="boot-dev-select"><title>Boot Device Selection</title>
<para>
@@ -229,7 +229,7 @@ save the changes on your computer. Often, you must press
</sect3>
</sect2>
- <sect2 arch="i386">
+ <sect2 arch="x86">
<title>Miscellaneous BIOS Settings</title>
<sect3 id="cd-settings"><title>CD-ROM Settings</title>
diff --git a/eu/preparing/minimum-hardware-reqts.xml b/eu/preparing/minimum-hardware-reqts.xml
index 410bf6c71..d4c7c0327 100644
--- a/eu/preparing/minimum-hardware-reqts.xml
+++ b/eu/preparing/minimum-hardware-reqts.xml
@@ -15,7 +15,7 @@ Zure beharren arabera, zuk beheandagoen taula gomendaturiko beharrak
baino gutxiagorekin lan egin ahal dezakezu. Hala ere erabiltzaile
gehienak frustraturik sentituko dira gomendio horiek ez bete ezkero.
-</para><para arch="i386">
+</para><para arch="x86">
Idazmahai makinetarako Pentium 100 bat gomendatzen da
eta zerbitzarietarako Pentium II-300.
diff --git a/eu/preparing/needed-info.xml b/eu/preparing/needed-info.xml
index fdccf38b5..f65e7a0f3 100644
--- a/eu/preparing/needed-info.xml
+++ b/eu/preparing/needed-info.xml
@@ -45,7 +45,7 @@ information on configuring or using your hardware.
</para>
<itemizedlist>
-<listitem arch="i386"><para>
+<listitem arch="x86"><para>
<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>
@@ -233,7 +233,7 @@ The cases and boxes for each piece of hardware.
</para></listitem>
-<listitem arch="i386"><para>
+<listitem arch="x86"><para>
The System window in the Windows Control Panel.
@@ -350,19 +350,19 @@ Many brand name products work without trouble on Linux. Moreover,
hardware for Linux is improving daily. However, Linux still does not
run as many different types of hardware as some operating systems.
-</para><para arch="i386">
+</para><para arch="x86">
In particular, Linux usually cannot run hardware that requires a
running version of Windows to work.
-</para><para arch="i386">
+</para><para arch="x86">
Although some Windows-specific hardware can be made to run on Linux,
doing so usually requires extra effort. In addition, Linux drivers
for Windows-specific hardware are usually specific to one Linux
kernel. Therefore, they can quickly become obsolete.
-</para><para arch="i386">
+</para><para arch="x86">
So called win-modems are the most common type of this hardware.
However, printers and other equipment may also be Windows-specific.
diff --git a/eu/preparing/non-debian-partitioning.xml b/eu/preparing/non-debian-partitioning.xml
index 5f9f67229..11bc81616 100644
--- a/eu/preparing/non-debian-partitioning.xml
+++ b/eu/preparing/non-debian-partitioning.xml
@@ -20,7 +20,7 @@ an LPAR or VM guest in this case.
If you already have an operating system on your system
-<phrase arch="i386">
+<phrase arch="x86">
(Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, &hellip;)
</phrase>
@@ -44,7 +44,7 @@ root.
You can find information about your current partition setup by using
a partitioning tool for your current operating system
-<phrase arch="i386">, such as fdisk or PartitionMagic</phrase>
+<phrase arch="x86">, such as fdisk or PartitionMagic</phrase>
<phrase arch="powerpc">, such as Drive Setup, HD Toolkit, or MacTools</phrase>
@@ -63,7 +63,7 @@ backups before doing any repartitioning. Using the analogy of the
house, you would probably want to move all the furniture out of the
way before moving a wall or you risk destroying it.
-<phrase arch="i386"> Luckily, there is an alternative for some users; see
+<phrase arch="x86"> Luckily, there is an alternative for some users; see
<xref linkend="lossless"/>. </phrase>
</para>
diff --git a/eu/preparing/nondeb-part/i386.xml b/eu/preparing/nondeb-part/i386.xml
index 43d0b622f..5ab8df92b 100644
--- a/eu/preparing/nondeb-part/i386.xml
+++ b/eu/preparing/nondeb-part/i386.xml
@@ -2,7 +2,7 @@
<!-- original version: 11648 untranslated -->
- <sect2 arch="i386"><title>Partitioning From DOS or Windows</title>
+ <sect2 arch="x86"><title>Partitioning From DOS or Windows</title>
<para>
If you are manipulating existing FAT or NTFS partitions, it is
diff --git a/eu/preparing/pre-install-bios-setup.xml b/eu/preparing/pre-install-bios-setup.xml
index c4cdd6b7f..073d5d9b5 100644
--- a/eu/preparing/pre-install-bios-setup.xml
+++ b/eu/preparing/pre-install-bios-setup.xml
@@ -54,7 +54,7 @@ FIXME: more description of this needed.
</emphasis></phrase>
-</para><para arch="i386">
+</para><para arch="x86">
The very best motherboards support parity RAM and will actually tell
you if your system has a single-bit error in RAM. Unfortunately, they
@@ -65,7 +65,7 @@ in your data. Thus, the best systems have motherboards that support
parity and true-parity memory modules; see
<xref linkend="Parity-RAM"/>.
-</para><para arch="i386">
+</para><para arch="x86">
If you do have true-parity RAM and your motherboard can handle it, be
sure to enable any BIOS settings that cause the motherboard to
@@ -73,7 +73,7 @@ interrupt on memory parity errors.
</para>
- <sect3 arch="i386"><title>The Turbo Switch</title>
+ <sect3 arch="x86"><title>The Turbo Switch</title>
<para>
Many systems have a <emphasis>turbo</emphasis> switch that controls
@@ -87,7 +87,7 @@ accidentally touch the software control for the turbo switch.
</para>
</sect3>
- <sect3 arch="i386"><title>Cyrix CPUs and Floppy Disk Errors</title>
+ <sect3 arch="x86"><title>Cyrix CPUs and Floppy Disk Errors</title>
<para>
Many users of Cyrix CPUs have had to disable the cache in their
@@ -106,7 +106,7 @@ the cache being invalid after a switch from 16-bit to 32-bit code.
</para>
</sect3>
- <sect3 arch="i386"><title>Peripheral Hardware Settings</title>
+ <sect3 arch="x86"><title>Peripheral Hardware Settings</title>
<para>
You may have to change some settings or jumpers on your computer's
@@ -124,7 +124,7 @@ amount of RAM in your system.
</para>
</sect3>
- <sect3 arch="i386" id="usb-keyboard-config"><title>USB keyboards</title>
+ <sect3 arch="x86" id="usb-keyboard-config"><title>USB keyboards</title>
<para>
If you have no AT-style keyboard and only a USB model, you will need