diff options
author | Frans Pop <elendil@planet.nl> | 2006-08-07 15:50:11 +0000 |
---|---|---|
committer | Frans Pop <elendil@planet.nl> | 2006-08-07 15:50:11 +0000 |
commit | 2d555470068ccdc434b41a8f438c3c2b56109305 (patch) | |
tree | c3f942e1ae8459d1784a4068401c8d764e01e5bf /da/preparing | |
parent | eaf56720ee96ae00de0acc841c8cfc7832bac7d7 (diff) | |
download | installation-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 'da/preparing')
-rw-r--r-- | da/preparing/bios-setup/i386.xml | 6 | ||||
-rw-r--r-- | da/preparing/minimum-hardware-reqts.xml | 2 | ||||
-rw-r--r-- | da/preparing/needed-info.xml | 10 | ||||
-rw-r--r-- | da/preparing/non-debian-partitioning.xml | 6 | ||||
-rw-r--r-- | da/preparing/nondeb-part/i386.xml | 2 | ||||
-rw-r--r-- | da/preparing/pre-install-bios-setup.xml | 12 |
6 files changed, 19 insertions, 19 deletions
diff --git a/da/preparing/bios-setup/i386.xml b/da/preparing/bios-setup/i386.xml index 46df78793..119ec2fa9 100644 --- a/da/preparing/bios-setup/i386.xml +++ b/da/preparing/bios-setup/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 18674 untranslated --> - <sect2 arch="i386" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> + <sect2 arch="x86" id="bios-setup"><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/da/preparing/minimum-hardware-reqts.xml b/da/preparing/minimum-hardware-reqts.xml index 62f2cf987..5a3641a4c 100644 --- a/da/preparing/minimum-hardware-reqts.xml +++ b/da/preparing/minimum-hardware-reqts.xml @@ -15,7 +15,7 @@ Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions. -</para><para arch="i386"> +</para><para arch="x86"> A Pentium 100 is the minimum recommended for desktop systems, and a Pentium II-300 for a Server. diff --git a/da/preparing/needed-info.xml b/da/preparing/needed-info.xml index a794642ed..d2a59b07a 100644 --- a/da/preparing/needed-info.xml +++ b/da/preparing/needed-info.xml @@ -44,7 +44,7 @@ Often contains useful 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> @@ -166,7 +166,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. @@ -283,19 +283,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/da/preparing/non-debian-partitioning.xml b/da/preparing/non-debian-partitioning.xml index ed5529957..c09859b73 100644 --- a/da/preparing/non-debian-partitioning.xml +++ b/da/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, …) </phrase> @@ -48,7 +48,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> @@ -103,7 +103,7 @@ special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway. -</para><para arch="i386"> +</para><para arch="x86"> If your machine has a FAT filesystem, as used by DOS and older versions of Windows, you can wait and use Debian installer's partitioning program to diff --git a/da/preparing/nondeb-part/i386.xml b/da/preparing/nondeb-part/i386.xml index 389121384..a6d1f1be7 100644 --- a/da/preparing/nondeb-part/i386.xml +++ b/da/preparing/nondeb-part/i386.xml @@ -2,7 +2,7 @@ <!-- original version: 22664 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/da/preparing/pre-install-bios-setup.xml b/da/preparing/pre-install-bios-setup.xml index c386a4eb6..049d336bb 100644 --- a/da/preparing/pre-install-bios-setup.xml +++ b/da/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 may need |