summaryrefslogtreecommitdiff
path: root/nl/boot-installer
diff options
context:
space:
mode:
authorJeroen Schot <schot@a-eskwadraat.nl>2012-08-29 15:10:27 +0000
committerJeroen Schot <schot@a-eskwadraat.nl>2012-08-29 15:10:27 +0000
commita292182f917a4104b223016e041410498f4d47a3 (patch)
tree31983bd3bb12e47ca30a949da0d472b93796a9ea /nl/boot-installer
parentf842e23756734b3ce4932695707bc416810e46cc (diff)
downloadinstallation-guide-a292182f917a4104b223016e041410498f4d47a3.zip
Restart Dutch translation of D-I manual in PO format.
Diffstat (limited to 'nl/boot-installer')
-rw-r--r--nl/boot-installer/accessibility.xml110
-rw-r--r--nl/boot-installer/arm.xml236
-rw-r--r--nl/boot-installer/boot-installer.xml49
-rw-r--r--nl/boot-installer/hppa.xml12
-rw-r--r--nl/boot-installer/ia64.xml464
-rw-r--r--nl/boot-installer/intro-cd.xml35
-rw-r--r--nl/boot-installer/intro-firmware.xml18
-rw-r--r--nl/boot-installer/intro-hd.xml16
-rw-r--r--nl/boot-installer/intro-net.xml19
-rw-r--r--nl/boot-installer/mips.xml61
-rw-r--r--nl/boot-installer/mipsel.xml54
-rw-r--r--nl/boot-installer/parameters.xml678
-rw-r--r--nl/boot-installer/powerpc.xml262
-rw-r--r--nl/boot-installer/s390.xml36
-rw-r--r--nl/boot-installer/sparc.xml46
-rw-r--r--nl/boot-installer/trouble.xml572
-rw-r--r--nl/boot-installer/x86.xml433
17 files changed, 0 insertions, 3101 deletions
diff --git a/nl/boot-installer/accessibility.xml b/nl/boot-installer/accessibility.xml
deleted file mode 100644
index 6ce4ca335..000000000
--- a/nl/boot-installer/accessibility.xml
+++ /dev/null
@@ -1,110 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 62899 untranslated -->
-
- <sect1 id="boot-installer-accessibility" arch="not-s390">
- <title>Accessibility</title>
-<para>
-
-Some users may need specific support because of e.g. some visual
-impairment.
-<phrase arch="ia64;powerpc;x86">USB braille displays are detected
-automatically, but most other</phrase>
-<phrase arch="arm;hppa;mips;mipsel;sparc">Most</phrase>
-accessibility features have to be enabled manually.
-<phrase arch="x86">On machines that support it, the boot menu emits a beep
-when it is ready to receive keystrokes.</phrase>
-Some boot parameters can <phrase arch="x86">then</phrase> be appended to
-enable accessibility features. Note that on most architectures the boot
-loader interprets your keyboard as a QWERTY keyboard.
-
-</para>
-
- <sect2 arch="ia64;powerpc;x86">
- <title>USB Braille Displays</title>
-<para>
-
-USB braille displays should be automatically detected. A textual version
-of the installer will then be automatically selected, and support for the
-braille display will be automatically installed on the target system.
-You can thus just press &enterkey; at the boot menu.
-Once <classname>brltty</classname> is started, you can choose a braille
-table by entering the preference menu. Documentation on key
-bindings for braille devices is available on the <ulink
-url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>.
-
-</para>
- </sect2>
-
- <sect2 arch="ia64;powerpc;x86">
- <title>Serial Braille Displays</title>
-<para>
-
-Serial braille displays cannot safely be automatically detected
-(since that may damage some of them). You thus need to append the
-<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput>
-boot parameter to tell <classname>brltty</classname> which driver it
-should use. <replaceable>driver</replaceable> should be replaced by the
-two-letter driver code for your terminal (see the
-<ulink url="&url-brltty-manual;">driver code list</ulink>).
-<replaceable>port</replaceable> should be replaced by the name of the
-serial port the display is connected to, <userinput>ttyS0</userinput> is
-the default. <replaceable>table</replaceable> is the name of the braille
-table to be used (see the <ulink url="&url-brltty-manual;">table code
-list</ulink>); the English table is the default. Note that the table can
-be changed later by entering the preference menu. Documentation on key
-bindings for braille devices is available on the <ulink
-url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>.
-
-</para>
- </sect2>
-
- <sect2 arch="x86">
- <title>Hardware Speech Synthesis</title>
-<para>
-
-Support for hardware speech synthesis devices is available only alongside
-support for graphical installer. You thus need to select the
-<quote>Graphical install</quote> entry in the boot menu.
-
-</para><para>
-
-Hardware speech synthesis devices cannot be automatically detected. You
-thus need to append the
-<userinput>speakup.synth=<replaceable>driver</replaceable></userinput>
-boot parameter to tell <classname>speakup</classname> which driver it should
-use. <replaceable>driver</replaceable> should be replaced by the driver code
-for your device (see <ulink url="&url-speakup-driver-codes;">driver code
-list</ulink>). The textual version of the installer will then be
-automatically selected, and support for the speech synthesis device will be
-automatically installed on the target system.
-
-</para>
- </sect2>
-
- <sect2 arch="linux-any"><title>Board Devices</title>
-<para>
-
-Some accessibility devices are actual boards that are plugged inside the
-machine and that read text directly from the video memory. To get them
-to work framebuffer support must be disabled by using the
-<userinput arch="x86">vga=normal</userinput> <userinput>fb=false</userinput>
-boot parameter. This will however reduce the number of available languages.
-
-</para><para arch="x86">
-
-If desired a textual version of the bootloader can be activated before adding
-the boot parameter by typing <userinput>h</userinput> &enterkey;.
-
-</para>
- </sect2>
-
- <sect2><title>High-Contrast Theme</title>
-<para>
-
-For users with low vision, the installer can use a high-contrast
-theme that makes it more readable. To enable it, append the
-<userinput>theme=dark</userinput> boot parameter.
-
-</para>
- </sect2>
- </sect1>
diff --git a/nl/boot-installer/arm.xml b/nl/boot-installer/arm.xml
deleted file mode 100644
index d295d0894..000000000
--- a/nl/boot-installer/arm.xml
+++ /dev/null
@@ -1,236 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 62875 untranslated -->
-
- <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title>
-
-&boot-installer-intro-net.xml;
-
- </sect2>
-
-
- <sect2 arch="arm"><title>Booting from CD-ROM</title>
-
-&boot-installer-intro-cd.xml;
-
- </sect2>
-
-
- <sect2 arch="arm" id="boot-firmware"><title>Booting from Firmware</title>
-
-&boot-installer-intro-firmware.xml;
-
- <sect3 arch="arm" id="boot-firmware-nslu2"><title>Booting the NSLU2</title>
-<para>
-
-There are three ways how to put the installer firmware into flash:
-
-</para>
-
- <sect4 arch="arm"><title>Using the NSLU2 web interface</title>
-<para>
-
-Go to the administration section and choose the menu item
-<literal>Upgrade</literal>. You can then browse your disk for the
-installer image you have previously downloaded. Then press the
-<literal>Start Upgrade</literal> button, confirm, wait for a few minutes
-and confirm again. The system will then boot straight into the installer.
-
-</para>
- </sect4>
-
- <sect4 arch="arm"><title>Via the network using Linux/Unix</title>
-<para>
-
-You can use <command>upslug2</command> from any Linux or Unix machine to
-upgrade the machine via the network. This software is packaged for
-&debian;.
-
-First, you have to put your NSLU2 in upgrade mode:
-
-<orderedlist>
-<listitem><para>
-
-Disconnect any disks and/or devices from the USB ports.
-
-</para></listitem>
-<listitem><para>
-
-Power off the NSLU2
-
-</para></listitem>
-<listitem><para>
-
-Press and hold the reset button (accessible through the small hole on the
-back just above the power input).
-
-</para></listitem>
-<listitem><para>
-
-Press and release the power button to power on the NSLU2.
-
-</para></listitem>
-<listitem><para>
-
-Wait for 10 seconds watching the ready/status LED. After 10 seconds it
-will change from amber to red. Immediately release the reset button.
-
-</para></listitem>
-<listitem><para>
-
-The NSLU2 ready/status LED will flash alternately red/green (there is a 1
-second delay before the first green). The NSLU2 is now in upgrade mode.
-
-</para></listitem>
-</orderedlist>
-
-See the <ulink
-url="http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary">NSLU2-Linux
-pages</ulink> if you have problems with this.
-
-Once your NSLU2 is in upgrade mode, you can flash the new image:
-
-<informalexample><screen>
-sudo upslug2 -i di-nslu2.bin
-</screen></informalexample>
-
-Note that the tool also shows the MAC address of your NSLU2, which may come
-in handy to configure your DHCP server. After the whole image has been
-written and verified, the system will automatically reboot. Make sure you
-connect your USB disk again now, otherwise the installer won't be able to
-find it.
-
-</para>
- </sect4>
-
- <sect4 arch="arm"><title>Via the network using Windows</title>
-<para>
-
-There is <ulink
-url="http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip">a
-tool</ulink> for Windows to upgrade the firmware via the network.
-
-</para>
- </sect4>
- </sect3>
-
- <sect3 arch="arm" id="boot-firmware-ss4000e">
- <title>Booting the SS4000-E</title>
-<para>
-
-Due to limitations in the SS4000-E firmware, it unfortunately is not
-possible to boot the installer without the use of a serial port at
-this time. To boot the installer, you will need a serial nullmodem
-cable; a computer with a serial port<footnote id="arm-s4ke-port">
-
-<para>
-A USB serial converter will also work.
-</para>
-
-</footnote>; and a ribbon cable with a male DB9 connector at one end,
-and a 10-pin .1" IDC header at the other<footnote id="arm-s4k-rib">
-
-<para>
-This cable is often found in older desktop machines with builtin 9-pin
-serial ports.
-</para>
-
-</footnote>.
-
-</para><para>
-
-To boot the SS4000-E, use your serial nullmodem cable and the ribbon
-cable to connect to the serial port of the SS4000-E, and reboot the
-machine. You need to use a serial terminal application to communicate
-with the machine; a good option on a &debian; GNU/Linux is to use the
-<command>cu</command> program, in the package of the same name. Assuming
-the serial port on your computer is to be found on
-<filename>/dev/ttyS0</filename>, use the following command line:
-
-</para>
-
-<informalexample><screen>
-cu -lttyS0 -s115200
-</screen></informalexample>
-
-<para>
-
-If using Windows, you may want to consider using the program
-<classname>hyperterminal</classname>. Use a baud rate of 115200,
-8 bits word length, no stop bits, and one parity bit.
-
-</para><para>
-
-When the machine boots, you will see the following line of output:
-
-</para>
-
-<informalexample><screen>
-No network interfaces found
-
-EM-7210 ver.T04 2005-12-12 (For ver.AA)
-== Executing boot script in 1.000 seconds - enter ^C to abort
-</screen></informalexample>
-
-<para>
-
-At this point, hit Control-C to interrupt the boot
-loader<footnote id="arm-s4ke-sec">
-
-<para>
-Note that you have only one second to do so; if you miss this window,
-just powercycle the machine and try again.
-</para>
-
-</footnote>. This will give you the RedBoot prompt. Enter the
-following commands:
-
-<informalexample><screen>
-load -v -r -b 0x01800000 -m ymodem ramdisk.gz
-load -v -r -b 0x01008000 -m ymodem zImage
-exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
-</screen></informalexample>
-
-</para><para>
-
-After every <command>load</command> command, the system will expect a
-file to be transmitted using the YMODEM protocol. When using cu, make
-sure you have the package <classname>lrzsz</classname> installed, then
-hit enter, followed by the <quote>~&lt;</quote> escape sequence to start
-an external program, and run <command>sb initrd.gz</command> or
-<command>sb vmlinuz</command>.
-
-</para><para>
-
-Alternatively, it is possible to load the kernel and ramdisk using
-HTTP rather than YMODEM. This is faster, but requires a working HTTP
-server on the network. To do so, first switch the bootloader to RAM mode:
-
-<informalexample><screen>
-fis load rammode
-g
-</screen></informalexample>
-
-</para><para>
-
-This will seemingly restart the machine; but in reality, it loads
-reboot to RAM and restarts it from there. Not doing this step will cause
-the system to hang in the necessary ip_address step that comes next.
-
-</para><para>
-
-You will need to hit Ctrl-C again to interrupt the boot. Then:
-
-<informalexample><screen>
-ip_address -l 192.168.2.249 -h 192.168.2.4
-load -v -r -b 0x01800000 -m http /initrd.gz
-load -v -r -b 0x01008000 -m http /zImage
-exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
-</screen></informalexample>
-
-</para><para>
-
-The installer will now start as usual.
-
-</para>
- </sect3>
- </sect2>
diff --git a/nl/boot-installer/boot-installer.xml b/nl/boot-installer/boot-installer.xml
deleted file mode 100644
index 7aaad3b0e..000000000
--- a/nl/boot-installer/boot-installer.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 61147 untranslated -->
-
-<chapter id="boot-installer"><title>Booting the Installation System</title>
-
-<!-- Include only archs that are documented to avoid build-errors -->
-<!-- The arch="..." condition can be deleted when al archs are present -->
- <sect1 arch="arm;any-x86;ia64;mips;mipsel;s390;powerpc;sparc">
- <title>Booting the Installer on &arch-title;</title>
-
-<!-- This info is so architecture dependent, that I have turned the -->
-<!-- structure inside out for this chapter. Each arch has a document. -->
-<!-- Note: arch hppa is currently missing -->
-
-<warning arch="any-x86;powerpc"><para>
-
-If you have any other operating systems on your system that you wish to
-keep (dual boot setup), you should make sure that they have been properly
-shut down <emphasis>before</emphasis> you boot the installer.
-Installing an operating system while another operating system is in
-hibernation (has been suspended to disk) could result in loss of, or damage
-to the state of the suspended operating system which could cause problems
-when it is rebooted.
-
-</para></warning>
-<note condition="gtk"><para>
-
-For information on how to boot the graphical installer, see
-<xref linkend="graphical"/>.
-
-</para></note>
-
-&boot-installer-arm.xml;
-<!-- &boot-installer-hppa.xml; -->
-&boot-installer-x86.xml;
-&boot-installer-ia64.xml;
-&boot-installer-mips.xml;
-&boot-installer-mipsel.xml;
-&boot-installer-s390.xml;
-&boot-installer-powerpc.xml;
-&boot-installer-sparc.xml;
-
- </sect1>
-
-&boot-installer-accessibility.xml;
-&boot-installer-parameters.xml;
-&boot-installer-trouble.xml;
-
-</chapter>
diff --git a/nl/boot-installer/hppa.xml b/nl/boot-installer/hppa.xml
deleted file mode 100644
index 619d3eaf1..000000000
--- a/nl/boot-installer/hppa.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 24701 untranslated -->
-
- <sect2 arch="hppa">
- <title></title>
-<para>
-
-<!-- Placeholder document; please write and include in
- boot-installer.xml and build/templates/docstruct.ent -->
-
-</para>
- </sect2>
diff --git a/nl/boot-installer/ia64.xml b/nl/boot-installer/ia64.xml
deleted file mode 100644
index 17104727e..000000000
--- a/nl/boot-installer/ia64.xml
+++ /dev/null
@@ -1,464 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 43841 untranslated -->
-
- <sect2 arch="ia64"><title>Booting from a CD-ROM</title>
-
-&boot-installer-intro-cd.xml;
-
- <note>
- <title>CD Contents</title>
-
-<para>
-
-There are three basic variations of &debian; Install CDs.
-The <emphasis>Business Card</emphasis> CD has a minimal installation
-that will fit on the small form factor CD media.
-It requires a network connection in order to install the rest of the
-base installation and make a usable system.
-The <emphasis>Network Install</emphasis> CD has all of the packages
-for a base install but requires a network connection to a &debian;
-mirror site in order to install the
-extra packages one would want for a complete system .
-The set of &debian; CDs can install a complete system from the wide
-range of packages without needing access to the network.
-</para>
- </note>
-
-<para>
-
-The IA-64 architecture uses the next generation Extensible Firmware Interface
-(EFI) from Intel.
-Unlike the traditional x86 BIOS which knows little about the boot
-device other than the partition table and Master Boot Record (MBR),
-EFI can read and write files from FAT16 or FAT32 formatted disk
-partitions.
-This simplifies the often arcane process of starting a system.
-The system boot loader and the EFI firmware that supports it have
-a full filesystem to store the files necessary for booting the
-machine.
-This means that the system disk on an IA-64 system has an additional
-disk partition dedicated to EFI instead of the simple MBR or boot
-block on more conventional systems.
-
-</para><para>
-
-The &debian; Installer CD contains a small EFI partition where the
-<command>ELILO</command> bootloader, its configuration file, the installer's
-kernel, and initial filesystem (initrd) are located.
-The running system also contains an EFI partition where the necessary
-files for booting the system reside.
-These files are readable from the EFI Shell as described below.
-
-</para><para>
-
-Most of the details of how <command>ELILO</command> actually loads and
-starts a system are transparent to the system installer.
-However, the installer must set up an EFI partition prior to installing
-the base system. Otherwise, the installation of <command>ELILO</command>
-will fail, rendering the system un-bootable.
-The EFI partition is allocated and formatted in the partitioning step
-of the installation prior to loading any packages on the system disk.
-The partitioning task also verifies that a suitable EFI partition is
-present before allowing the installation to proceed.
-
-</para><para>
-
-The EFI Boot Manager is presented as the last step of the firmware
-initialization.
-It displays a menu list from which the user can select
-an option.
-Depending on the model of system and what other software has been
-loaded on the system, this menu may be different from one system
-to another.
-There should be at least two menu items displayed,
-<command>Boot Option Maintenance Menu</command> and
-<command>EFI Shell (Built-in)</command>.
-Using the first option is preferred, however, if that
-option is not available or the CD for some reason does not
-boot with it, use the second option.
-
-</para>
-
- <warning>
- <title>IMPORTANT</title>
-<para>
-The EFI Boot Manager will select a default boot action, typically
-the first menu choice, within a pre-set number of seconds.
-This is indicated by a countdown at the bottom of the screen.
-Once the timer expires and the systems starts the default action,
-you may have to reboot the machine in order to continue the installation.
-If the default action is the EFI Shell, you can return to the Boot Manager
-by running <command>exit</command> at the shell prompt.
-</para>
- </warning>
-
- <sect3 arch="ia64" id="bootable-cd">
- <title>Option 1: Booting from the Boot Option Maintenance Menu</title>
-<para>
-
-</para>
-
-<itemizedlist>
-
-<listitem><para>
-Insert the CD in the DVD/CD drive and reboot the machine.
-The firmware will display the EFI Boot Manager page and menu after
-it completes its system initialization.
-</para></listitem>
-
-<listitem><para>
-Select <command>Boot Maintenance Menu</command> from the menu
-with the arrow keys and press <command>ENTER</command>.
-This will display a new menu.
-</para></listitem>
-
-<listitem><para>
-Select <command>Boot From a File</command> from the menu
-with the arrow keys and press <command>ENTER</command>.
-This will display a list of devices probed by the firmware.
-You should see two menu lines containing either the label
-<command>Debian Inst [Acpi ...</command> or
-<command>Removable Media Boot</command>.
-If you examine the rest of the menu line, you will notice that
-the device and controller information should be the same.
-</para></listitem>
-
-<listitem><para>
-You can choose either of the entries that refer to the CD/DVD
-drive.
-Select your choice with the arrow keys and press <command>ENTER</command>.
-If you choose <command>Removable Media Boot</command> the machine
-will immediately start the boot load sequence.
-If you choose <command>Debian Inst [Acpi ...</command> instead, it
-will display a directory listing of the bootable portion of the
-CD, requiring you to proceed to the next (additional) step.
-</para></listitem>
-
-<listitem><para>
-You will only need this step if you chose
-<command>Debian Inst [Acpi ...</command>.
-The directory listing will also show
-<command>[Treat like Removable Media Boot]</command> on the next to
-the last line.
-Select this line with the arrow keys and press <command>ENTER</command>.
-This will start the boot load sequence.
-</para></listitem>
-
-</itemizedlist>
-
-<para>
-
-These steps start the &debian; boot loader which will display a
-menu page for you to select a boot kernel and options.
-Proceed to selecting the boot kernel and options.
-
-</para>
- </sect3>
-
- <sect3 arch="ia64" id="boot-with-efi">
- <title>Option 2: Booting from the EFI Shell</title>
-<para>
-
-If, for some reason, option 1 is not successful, reboot the machine
-and when the EFI Boot Manager screen appears there should be
-one option called <command>EFI Shell [Built-in]</command>.
-Boot the &debian; Installer CD with the following steps:
-
-</para>
-
-<itemizedlist>
-
-<listitem><para>
-Insert the CD in the DVD/CD drive and reboot the machine.
-The firmware will display the EFI Boot Manager page and menu after
-it completes system initialization.
-</para></listitem>
-
-<listitem><para>
-Select <command>EFI Shell</command> from the menu with the arrow keys
-and press <command>ENTER</command>.
-The EFI Shell will scan all of the bootable devices and display
-them to the console before displaying its command prompt.
-The recognized bootable partitions on devices will show a device name of
-<filename>fs<replaceable>n</replaceable>:</filename>.
-All other recognized partitions will be named
-<filename>blk<replaceable>n</replaceable>:</filename>.
-If you inserted the CD just before entering the shell, this may
-take a few extra seconds as it initializes the CD drive.
-</para>
-</listitem>
-
-<listitem><para>
-Examine the output from the shell looking for the CDROM drive.
-It is most likely the <filename>fs0:</filename> device although
-other devices with bootable partitions will also show up as
-<filename>fs<replaceable>n</replaceable></filename>.
-</para></listitem>
-
-<listitem><para>
-Enter <command>fs<replaceable>n</replaceable>:</command> and press
-<command>ENTER</command> to select that
-device where <replaceable>n</replaceable> is the partition number for the
-CDROM. The shell will now display the partition number as its prompt.
-</para></listitem>
-
-<listitem><para>
-Enter <command>elilo</command> and press <command>ENTER</command>.
-This will start the boot load sequence.
-</para></listitem>
-
-</itemizedlist>
-
-<para>
-
-As with option 1, these steps start the &debian; boot loader which will
-display a menu page for you to select a boot kernel and options.
-You can also enter the shorter
-<command>fs<replaceable>n</replaceable>:elilo</command> command at
-the shell prompt.
-Proceed to selecting the boot kernel and options.
-
-</para>
-
- </sect3>
-
- <sect3 arch="ia64" id="serial-console">
- <title>Installing using a Serial Console</title>
-
-<para>
-
-You may choose to perform an install using a monitor and keyboard
-or using a serial connection. To use a monitor/keyboard setup,
-select an option containing the string [VGA console]. To install
-over a serial connection, choose an option containing the string
-[<replaceable>BAUD</replaceable> baud serial console], where
-<replaceable>BAUD</replaceable> is the speed of your serial console.
-Menu items for the most typical baud rate settings on the ttyS0
-device are preconfigured.
-
-</para><para>
-
-In most circumstances, you will want the installer to use the same
-baud rate as your connection to the EFI console. If you aren't
-sure what this setting is, you can obtain it using the command
-<command>baud</command> at the EFI shell.
-
-</para><para>
-
-If there is not an option available that is configured for the serial
-device or baud rate you would like to use, you may override the console setting
-for one of the existing menu options. For example, to use a
-57600 baud console over the ttyS1 device, enter
-<command>console=ttyS1,57600n8</command> into
-the <classname>Boot:</classname> text window.
-
-</para>
-
-<note><para>
-Most IA-64 boxes ship with a default console setting of 9600 baud.
-This setting is rather slow, and the normal installation process
-will take a significant time to draw each screen. You should consider
-either increasing the baud rate used for performing the installation,
-or performing a Text Mode installation. See the <classname>Params</classname>
-help menu for instructions on starting the installer in Text Mode.
-</para></note>
-
-<warning><para>
-If you select the wrong console type, you
-will be able to select the kernel and enter parameters but both
-the display and your input will go dead as soon as the kernel starts,
-requiring you to reboot before you can begin the installation.
-</para></warning>
- </sect3>
-
- <sect3 arch="ia64" id="kernel-option-menu">
- <title>Selecting the Boot Kernel and Options</title>
-
-<para>
-
-The boot loader will display a form with a menu list and a text
-window with a <classname>Boot:</classname> prompt.
-The arrow keys select an item from the menu and any text typed
-at the keyboard will appear in the text window.
-There are also help screens which can be displayed by pressing
-the appropriate function key.
-The <classname>General</classname> help screen explains the menu
-choices and the <classname>Params</classname> screen explains
-the common command line options.
-
-</para><para>
-
-Consult the <classname>General</classname> help screen for the
-description of the kernels and install modes most appropriate
-for your installation.
-You should also consult <xref linkend="boot-parms"/> below for any additional
-parameters that you may want to set in the <classname>Boot:</classname>
-text window.
-The kernel version you choose selects the kernel version that will be
-used for both the installation process and the installed system.
-If you encounter kernel problems with the installation, you may also
-have those same problems with the system you install.
-The following two steps will select and start the install:
-
-</para>
-
-<itemizedlist>
-
-<listitem><para>
-Select the kernel version and installation mode most
-appropriate to your needs with the arrow keys.
-</para></listitem>
-
-<listitem><para>
-Enter any boot parameters by typing at the keyboard.
-The text will be displayed directly in the text window.
-This is where kernel parameters (such as serial console
-settings) are specified.
-</para></listitem>
-
-<listitem><para>
-Press <command>ENTER</command>. This will load and start the
-kernel.
-The kernel will display its usual initialization messages followed
-by the first screen of the &debian; Installer.
-</para></listitem>
-
-</itemizedlist>
-
-<para>
-
-Proceed to the next chapter to continue the installation where you will
-set up the language locale, network, and disk partitions.
-
-</para>
- </sect3>
- </sect2>
-
- <sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title>
-
-<para>
-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.
-Once the installation kernel is loaded and starts, the system install
-will proceed through the same steps as the CD install with the exception
-that the packages of the base install will be loaded from the network
-rather than the CD drive.
-
-</para>
-
-&boot-installer-intro-net.xml;
-
-<para>
-
-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
-to enable loading over a network.
-
-</para>
-
- <sect3 arch="ia64" id="boot-tftp-server">
- <title>Configuring the Server</title>
-<para>
-
-A suitable TFTP entry for network booting an IA-64 system looks something
-like this:
-
-<informalexample><screen>
-host mcmuffin {
- hardware ethernet 00:30:6e:1e:0e:83;
- fixed-address 10.0.0.21;
- filename "debian-installer/ia64/elilo.efi";
-}
-</screen></informalexample>
-
-Note that the goal is to get <command>elilo.efi</command> running on
-the client.
-
-</para><para>
-
-Extract the <filename>netboot.tar.gz</filename> file into the directory used
-as the root for your tftp server. Typical tftp root directories include
-<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>.
-This will create a <filename>debian-installer</filename> directory
-tree containing the boot files for an IA-64 system.
-
-</para><para>
-
-<informalexample><screen>
-# cd /var/lib/tftp
-# tar xvfz /home/user/netboot.tar.gz
-./
-./debian-installer/
-./debian-installer/ia64/
-[...]
-</screen></informalexample>
-
-The <filename>netboot.tar.gz</filename> contains an
-<filename>elilo.conf</filename> file that should work for most configurations.
-However, should you need to make changes to this file, you can find it in the
-<filename>debian-installer/ia64/</filename> directory.
-
-It is possible to have different config files for different clients by naming
-them using the client's IP address in hex with the suffix
-<filename>.conf</filename> instead of <filename>elilo.conf</filename>.
-See documentation provided in the <classname>elilo</classname> package
-for details.
-
-</para>
- </sect3>
-
- <sect3 arch="ia64" id="boot-tftp-client">
- <title>Configuring the Client</title>
-<para>
-
-To configure the client to support TFTP booting, start by booting to
-EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>.
-
-<itemizedlist>
-<listitem><para>
-
-Add a boot option.
-
-</para></listitem>
-<listitem><para>
-
-You should see one or more lines with the text
-<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more
-than one of these entries exist, choose the one containing the
-MAC address of the interface from which you'll be booting.
-Use the arrow keys to highlight your choice, then press enter.
-
-</para></listitem>
-<listitem><para>
-
-Name the entry <userinput>Netboot</userinput> or something similar,
-save, and exit back to the boot options menu.
-
-</para></listitem>
-</itemizedlist>
-
-You should see the new boot option you just created, and selecting it
-should initiate a DHCP query, leading to a TFTP load of
-<filename>elilo.efi</filename> from the server.
-
-</para><para>
-
-The boot loader will display its prompt after it has downloaded and
-processed its configuration file.
-At this point, the installation proceeds with the same steps as a
-CD install. Select a boot option as in above and when the kernel
-has completed installing itself from the network, it will start the
-&debian; Installer.
-
-</para><para>
-
-Proceed to the next chapter to continue the installation where
-you will set up the language locale, network, and disk partitions.
-
-</para>
- </sect3>
- </sect2>
diff --git a/nl/boot-installer/intro-cd.xml b/nl/boot-installer/intro-cd.xml
deleted file mode 100644
index 4c00e2593..000000000
--- a/nl/boot-installer/intro-cd.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 39614 untranslated -->
-
-<para>
-
-The easiest route for most people will be to use a set of &debian; CDs.
-If you have a CD set, and if your machine supports booting directly off
-the CD, great! Simply
-<phrase arch="x86">
-configure your system for booting off a CD as described in
-<xref linkend="boot-dev-select"/>,
-</phrase>
-insert your CD, reboot, and proceed to the next chapter.
-
-</para><para>
-
-Note that certain CD drives may require special drivers, and thus be
-inaccessible in the early installation stages. If it turns out the
-standard way of booting off a CD doesn't work for your hardware,
-revisit this chapter and read about alternate kernels and installation
-methods which may work for you.
-
-</para><para>
-
-Even if you cannot boot from CD-ROM, you can probably install the
-&debian; system components and any packages you want from CD-ROM.
-Simply boot using a different media, such as floppies. When it's
-time to install the operating system, base system, and any additional
-packages, point the installation system at the CD-ROM drive.
-
-</para><para>
-
-If you have problems booting, see <xref linkend="boot-troubleshooting"/>.
-
-</para>
diff --git a/nl/boot-installer/intro-firmware.xml b/nl/boot-installer/intro-firmware.xml
deleted file mode 100644
index fe869608e..000000000
--- a/nl/boot-installer/intro-firmware.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 35309 untranslated -->
-
-<para>
-
-There is an increasing number of consumer devices that directly boot from a
-flash chip on the device. The installer can be written to flash so it will
-automatically start when you reboot your machines.
-
-</para><note><para>
-
-In many cases, changing the firmware of an embedded device voids your
-warranty. Sometimes you are also not able to recover your device if there
-are problems during the flashing process. Therefore, please take care and
-follow the steps precisely.
-
-</para></note>
-
diff --git a/nl/boot-installer/intro-hd.xml b/nl/boot-installer/intro-hd.xml
deleted file mode 100644
index 4df9f39b8..000000000
--- a/nl/boot-installer/intro-hd.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 61184 untranslated -->
-
-<para>
-
-Booting from an existing operating system is often a convenient
-option; for some systems it is the only supported method of
-installation.
-
-</para><para>
-
-To boot the installer from hard disk, you will have already completed
-downloading and placing the needed files as described in
-<xref linkend="boot-drive-files"/>.
-
-</para>
diff --git a/nl/boot-installer/intro-net.xml b/nl/boot-installer/intro-net.xml
deleted file mode 100644
index 79189195c..000000000
--- a/nl/boot-installer/intro-net.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
-
-<para>
-
-Booting from the network requires that you have a network
-connection and a TFTP network boot server (DHCP, RARP, or BOOTP).
-
-</para><para arch="hppa">
-
-Older systems such as the 715 might require the use of an RBOOT server
-instead of a BOOTP server.
-
-</para><para>
-
-The installation method to support network booting is described in <xref
-linkend="install-tftp"/>.
-
-</para> \ No newline at end of file
diff --git a/nl/boot-installer/mips.xml b/nl/boot-installer/mips.xml
deleted file mode 100644
index d1ef4d252..000000000
--- a/nl/boot-installer/mips.xml
+++ /dev/null
@@ -1,61 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 59840 untranslated -->
-
-
- <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title>
-
- <sect3>
- <title>SGI TFTP Booting</title>
-<para>
-
-After entering the command monitor use
-
-<informalexample><screen>
-bootp():
-</screen></informalexample>
-
-on SGI machines to boot linux and to begin installation of the &debian;
-Software. In order to make this
-work you may have to unset the <envar>netaddr</envar> environment
-variable. Type
-
-<informalexample><screen>
-unsetenv netaddr
-</screen></informalexample>
-
-in the command monitor to do this.
-
-</para>
- </sect3>
-
- </sect2>
-
- <sect2 arch="mips"><title>Boot Parameters</title>
-
- <sect3>
- <title>SGI TFTP Booting</title>
-<para>
-
-On SGI machines you can append boot parameters to the
-<command>bootp():</command> command in the command monitor.
-
-</para><para>
-
-Following the <command>bootp():</command> command you can give the
-path and name of the file to boot if you did not give an explicit name
-via your bootp/dhcp server. Example:
-
-<informalexample><screen>
-bootp():/boot/tftpboot.img
-</screen></informalexample>
-
-Further kernel parameters can be passed via <command>append</command>:
-
-<informalexample><screen>
-bootp(): append="root=/dev/sda1"
-</screen></informalexample>
-
-</para>
- </sect3>
-
- </sect2>
diff --git a/nl/boot-installer/mipsel.xml b/nl/boot-installer/mipsel.xml
deleted file mode 100644
index 7680c9cdb..000000000
--- a/nl/boot-installer/mipsel.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 59840 untranslated -->
-
- <sect2 arch="mipsel" id="boot-tftp"><title>Booting with TFTP</title>
-
- <sect3>
- <title>Cobalt TFTP Booting</title>
-<para>
-
-Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to
-install an NFS server and put the installer files in
-<filename>/nfsroot</filename>. When you boot your Cobalt, you have to
-press the left and the right cursor buttons at the same time and the
-machine will boot via the network from NFS. It will then display several
-options on the display. There are the following two installation methods:
-
-<itemizedlist>
-<listitem><para>
-
-Via SSH (default): In this case, the installer will configure the network
-via DHCP and start an SSH server. It will then display a random password
-and other login information (such as the IP address) on the Cobalt LCD.
-When you connect to the machine with an SSH client you can start with
-the installation.
-
-</para></listitem>
-<listitem><para>
-
-Via serial console: Using a null modem cable, you can connect to the serial
-port of your Cobalt machine (using 115200 bps) and perform the installation
-this way.
-
-</para></listitem>
-</itemizedlist>
-
-</para>
- </sect3>
-
- </sect2>
-
- <sect2 arch="mipsel"><title>Boot Parameters</title>
-
- <sect3>
- <title>Cobalt TFTP Booting</title>
-<para>
-
-You cannot pass any boot parameters directly. Instead, you have to edit
-the <filename>/nfsroot/default.colo</filename> file on the NFS server and
-add your parameters to the <replaceable>args</replaceable> variable.
-
-</para>
- </sect3>
-
- </sect2>
diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml
deleted file mode 100644
index 545d1a5f4..000000000
--- a/nl/boot-installer/parameters.xml
+++ /dev/null
@@ -1,678 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 62899 untranslated -->
-
- <sect1 id="boot-parms"><title>Boot Parameters</title>
-<para arch="linux-any">
-
-Boot parameters are Linux kernel parameters which are generally used
-to make sure that peripherals are dealt with properly. For the most
-part, the kernel can auto-detect information about your peripherals.
-However, in some cases you'll have to help the kernel a bit.
-
-</para><para>
-
-If this is the first time you're booting the system, try the default
-boot parameters (i.e., don't try setting parameters) and see if it works
-correctly. It probably will. If not, you can reboot later and look for
-any special parameters that inform the system about your hardware.
-
-</para><para arch="linux-any">
-
-Information on many boot parameters can be found in the
-<ulink url="http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html"> Linux
-BootPrompt HOWTO</ulink>, including tips for obscure hardware. This
-section contains only a sketch of the most salient parameters. Some
-common gotchas are included below in
-<xref linkend="boot-troubleshooting"/>.
-
-</para><para arch="linux-any">
-
-When the kernel boots, a message
-
-<informalexample><screen>
-Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available
-</screen></informalexample>
-
-should be emitted early in the process.
-<replaceable>total</replaceable> should match the total amount of RAM,
-in kilobytes. If this doesn't match the actual amount of RAM you have
-installed, you need to use the
-<userinput>mem=<replaceable>ram</replaceable></userinput> parameter,
-where <replaceable>ram</replaceable> is set to the amount of memory,
-suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for
-megabytes. For example, both <userinput>mem=65536k</userinput> and
-<userinput>mem=64m</userinput> mean 64MB of RAM.
-
-</para><para arch="linux-any" condition="supports-serial-console">
-
-If you are booting with a serial console, generally the kernel will
-autodetect this.
-If you have a videocard (framebuffer) and a keyboard also attached to
-the computer which you wish to boot via serial console, you may have
-to pass the
-<userinput>console=<replaceable>device</replaceable></userinput>
-argument to the kernel, where <replaceable>device</replaceable> is
-your serial device, which is usually something like
-<filename>ttyS0</filename><footnote>
-
-<para>
-In order to ensure the terminal type used by the installer matches your
-terminal emulator, the parameter
-<userinput>TERM=<replaceable>type</replaceable></userinput> can be added.
-Note that the installer only supports the following terminal types:
-<literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>,
-<literal>vt102</literal> and <literal>dumb</literal>. The default for
-serial console in &d-i; is <userinput>vt102</userinput>.
-</para>
-
-</footnote>.
-
-</para><para arch="sparc">
-
-For &arch-title; the serial devices are <filename>ttya</filename> or
-<filename>ttyb</filename>.
-Alternatively, set the <envar>input-device</envar> and
-<envar>output-device</envar> OpenPROM variables to
-<filename>ttya</filename>.
-
-</para>
-
-
- <sect2 id="installer-args"><title>&debian; Installer Parameters</title>
-<para>
-
-The installation system recognizes a few additional boot parameters<footnote>
-
-<para>
-
-With current kernels (2.6.9 or newer) you can use 32 command line options and
-32 environment options. If these numbers are exceeded, the kernel will panic.
-
-</para>
-
-</footnote> which may be useful.
-
-</para><para>
-
-A number of parameters have a <quote>short form</quote> that helps avoid
-the limitations of the kernel command line options and makes entering the
-parameters easier. If a parameter has a short form, it will be listed in
-brackets behind the (normal) long form. Examples in this manual will
-normally use the short form too.
-
-</para>
-
-<variablelist>
-<varlistentry>
-<term>debconf/priority (priority)</term>
-<listitem><para>
-
-This parameter sets the lowest priority of messages to be displayed.
-
-</para><para>
-
-The default installation uses <userinput>priority=high</userinput>.
-This means that both high and critical priority messages are shown, but medium
-and low priority messages are skipped.
-If problems are encountered, the installer adjusts the priority as needed.
-
-</para><para>
-
-If you add <userinput>priority=medium</userinput> as boot parameter, you
-will be shown the installation menu and gain more control over the installation.
-When <userinput>priority=low</userinput> is used, all messages are shown
-(this is equivalent to the <emphasis>expert</emphasis> boot method).
-With <userinput>priority=critical</userinput>, the installation system
-will display only critical messages and try to do the right thing without fuss.
-
-</para></listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>DEBIAN_FRONTEND</term>
-<listitem><para>
-
-This boot parameter controls the type of user interface used for the
-installer. The current possible parameter settings are:
-
-<itemizedlist>
-<listitem>
-<para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para>
-</listitem><listitem>
-<para><userinput>DEBIAN_FRONTEND=text</userinput></para>
-</listitem><listitem>
-<para><userinput>DEBIAN_FRONTEND=newt</userinput></para>
-</listitem><listitem>
-<para><userinput>DEBIAN_FRONTEND=gtk</userinput></para>
-</listitem>
-</itemizedlist>
-
-The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>.
-<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for
-serial console installs. Generally, only the
-<userinput>newt</userinput> frontend is available on default install
-media. On architectures that support it, the graphical installer uses
-the <userinput>gtk</userinput> frontend.
-
-</para></listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>BOOT_DEBUG</term>
-<listitem><para>
-
-Setting this boot parameter to 2 will cause the installer's boot process
-to be verbosely logged. Setting it to 3 makes debug shells
-available at strategic points in the boot process. (Exit the shells to
-continue the boot process.)
-
-<variablelist>
-<varlistentry>
-<term><userinput>BOOT_DEBUG=0</userinput></term>
-<listitem><para>This is the default.</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><userinput>BOOT_DEBUG=1</userinput></term>
-<listitem><para>More verbose than usual.</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><userinput>BOOT_DEBUG=2</userinput></term>
-<listitem><para>Lots of debugging information.</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term><userinput>BOOT_DEBUG=3</userinput></term>
-<listitem><para>
-
-Shells are run at various points in the boot process to allow detailed
-debugging. Exit the shell to continue the boot.
-
-</para></listitem>
-</varlistentry>
-</variablelist>
-
-</para></listitem>
-</varlistentry>
-
-
-<varlistentry>
-<term>INSTALL_MEDIA_DEV</term>
-<listitem><para>
-
-The value of the parameter is the path to the device to load the
-&debian; installer from. For example,
-<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput>
-
-</para><para>
-
-The boot floppy, which normally scans all floppies it can to find the
-root floppy, can be overridden by this parameter to only look at the
-one device.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>lowmem</term>
-<listitem><para>
-
-Can be used to force the installer to a lowmem level higher than the one
-the installer sets by default based on available memory. Possible values
-are 1 and 2. See also <xref linkend="lowmem"/>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>noshell</term>
-<listitem><para>
-
-Prevents the installer from offering interactive shells on tty2 and tty3.
-Useful for unattended installations where physical security is limited.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>debian-installer/framebuffer (fb)</term>
-<listitem><para>
-
-Some architectures use the kernel framebuffer to offer installation in
-a number of languages. If framebuffer causes a problem on your system
-you can disable the feature using the parameter
-<userinput arch="x86">vga=normal</userinput> <userinput>fb=false</userinput>.
-Problem symptoms are error messages about bterm or bogl, a blank screen,
-or a freeze within a few minutes after starting the install.
-
-</para><para arch="hppa">
-
-Such problems have been reported on hppa.
-
-</para><note arch="sparc"><para>
-
-Because of display problems on some systems, framebuffer support is
-<emphasis>disabled by default</emphasis> for &arch-title;. This can result
-in ugly display on systems that do properly support the framebuffer, like
-those with ATI graphical cards.
-If you see display problems in the installer, you can try booting with
-parameter <userinput>debian-installer/framebuffer=true</userinput> or
-<userinput>fb=true</userinput> for short.
-
-</para></note></listitem>
-</varlistentry>
-
-<varlistentry arch="not-s390">
-<term>debian-installer/theme (theme)</term>
-<listitem><para>
-
-A theme determines how the user interface of the installer looks (colors,
-icons, etc.). What themes are available differs per frontend. Currently
-both the newt and gtk frontends only have a <quote>dark</quote> theme that was
-designed for visually impaired users. Set the theme by booting with
-<userinput>theme=<replaceable>dark</replaceable></userinput>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>netcfg/disable_dhcp</term>
-<listitem><para>
-
-By default, the &d-i; automatically probes for network configuration
-via DHCP. If the probe succeeds, you won't have a chance to review and
-change the obtained settings. You can get to the manual network setup
-only in case the DHCP probe fails.
-
-</para><para>
-
-If you have a DHCP server on your local network, but want to avoid it
-because e.g. it gives wrong answers, you can use the parameter
-<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring
-the network with DHCP and to enter the information manually.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>hw-detect/start_pcmcia</term>
-<listitem><para>
-
-Set to <userinput>false</userinput> to prevent starting PCMCIA
-services, if that causes problems. Some laptops are well known for
-this misbehavior.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>disk-detect/dmraid/enable (dmraid)</term>
-<listitem><para>
-
-Set to <userinput>true</userinput> to enable support for Serial ATA RAID
-(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer.
-Note that this support is currently experimental. Additional information
-can be found on the <ulink url="&url-d-i-wiki;">Debian Installer Wiki</ulink>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>preseed/url (url)</term>
-<listitem><para>
-
-Specify the url to a preconfiguration file to download and use for
-automating the install. See <xref linkend="automatic-install"/>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>preseed/file (file)</term>
-<listitem><para>
-
-Specify the path to a preconfiguration file to load for
-automating the install. See <xref linkend="automatic-install"/>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>preseed/interactive</term>
-<listitem><para>
-
-Set to <userinput>true</userinput> to display questions even if they have
-been preseeded. Can be useful for testing or debugging a preconfiguration
-file. Note that this will have no effect on parameters that are passed as
-boot parameters, but for those a special syntax can be used.
-See <xref linkend="preseed-seenflag"/> for details.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>auto-install/enable (auto)</term>
-<listitem><para>
-
-Delay questions that are normally asked before preseeding is possible until
-after the network is configured.
-See <xref linkend="preseed-auto"/> for details about using this to
-automate installs.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>finish-install/keep-consoles</term>
-<listitem><para>
-
-During installations from serial or management console, the regular
-virtual consoles (VT1 to VT6) are normally disabled in
-<filename>/etc/inittab</filename>.
-Set to <userinput>true</userinput> to prevent this.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>cdrom-detect/eject</term>
-<listitem><para>
-
-By default, before rebooting, &d-i; automatically ejects the optical
-media used during the installation. This can be unnecessary if the system
-does not automatically boot off the CD. In some cases it may even be
-undesirable, for example if the optical drive cannot reinsert the media
-itself and the user is not there to do it manually. Many slot loading,
-slim-line, and caddy style drives cannot reload media automatically.
-
-</para><para>
-
-Set to <userinput>false</userinput> to disable automatic ejection, and
-be aware that you may need to ensure that the system does not
-automatically boot from the optical drive after the initial
-installation.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>base-installer/install-recommends (recommends)</term>
-<listitem><para>
-
-By setting this option to <userinput>false</userinput>, the package
-management system will be configured to not automatically install
-<quote>Recommends</quote>, both during the installation and for the
-installed system. See also <xref linkend="di-install-base"/>.
-
-</para><para>
-
-Note that this option allows to have a leaner system, but can also result
-in features being missing that you might normally expect to be available.
-You may have to manually install some of the recommended packages to
-obtain the full functionality you want. This option should therefore only
-be used by very experienced users.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>debian-installer/allow_unauthenticated</term>
-<listitem><para>
-
-By default the installer requires that repositories be authenticated
-using a known gpg key. Set to <userinput>true</userinput> to
-disable that authentication.
-<emphasis role="bold">Warning: insecure, not recommended.</emphasis>
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry arch="mips;mipsel">
-<term>ramdisk_size</term>
-<listitem><para>
-
-This parameter should already be set to a correct value where needed;
-set it only it you see errors during the boot that indicate the ramdisk
-could not be loaded completely. The value is in kB.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry condition="gtk">
-<term>mouse/protocol</term>
-<listitem><para>
-
-For the gtk frontend (graphical installer), users can set the mouse
-protocol to be used by setting this parameter.
-Supported values are<footnote>
-
-<para>
-See the man page for
-<citerefentry><refentrytitle>directfbrc</refentrytitle>
-<manvolnum>5</manvolnum></citerefentry> for additional information.
-</para>
-
-</footnote>:
-<userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>,
-<userinput>MS</userinput>, <userinput>MS3</userinput>,
-<userinput>MouseMan</userinput> and <userinput>MouseSystems</userinput>.
-In most cases the default protocol should work correctly.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry condition="gtk">
-<term>mouse/device</term>
-<listitem><para>
-
-For the gtk frontend (graphical installer), users can specify the mouse
-device to be used by setting this parameter. This is mostly useful if the
-mouse is connected to a serial port (serial mouse). Example:
-<userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry condition="gtk">
-<term>mouse/left</term>
-<listitem><para>
-
-For the gtk frontend (graphical installer), users can switch the mouse to
-left-handed operation by setting this parameter to <userinput>true</userinput>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry condition="gtk">
-<term>directfb/hw-accel</term>
-<listitem><para>
-
-For the gtk frontend (graphical installer), hardware acceleration in directfb
-is disabled by default. Set this parameter to <userinput>true</userinput> to
-enable it.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>rescue/enable</term>
-<listitem><para>
-
-Set to <userinput>true</userinput> to enter rescue mode rather than
-performing a normal installation. See <xref linkend="rescue"/>.
-
-</para></listitem>
-</varlistentry>
-
-</variablelist>
-
- </sect2>
-
- <sect2 id="preseed-args">
- <title>Using boot parameters to answer questions</title>
-<para>
-
-With some exceptions, a value can be set at the boot prompt for any question
-asked during the installation, though this is only really useful in specific
-cases. General instructions how to do this can be found in
-<xref linkend="preseed-bootparms"/>. Some specific examples are listed below.
-
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term>debian-installer/language (language)</term>
-<term>debian-installer/country (country)</term>
-<term>debian-installer/locale (locale)</term>
-<listitem><para>
-
-There are two ways to specify the language, country and locale to use for
-the installation and the installed system.
-
-</para><para>
-
-The first and easiest is to pass only the parameter <literal>locale</literal>.
-Language and country will then be derived from its value. You can for example
-use <userinput>locale=de_CH</userinput> to select German as language and
-Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default
-locale for the installed system). Limitation is that not all possible
-combinations of language, country and locale can be achieved this way.
-
-</para><para>
-
-The second, more flexible option is to specify <literal>language</literal>
-and <literal>country</literal> separately. In this case
-<literal>locale</literal> can optionally be added to specify a specific
-default locale for the installed system. Example:
-<userinput>language=en country=DE locale=en_GB.UTF-8</userinput>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>anna/choose_modules (modules)</term>
-<listitem><para>
-
-Can be used to automatically load installer components that are not loaded
-by default.
-Examples of optional components that may be useful are
-<classname>openssh-client-udeb</classname> (so you can use
-<command>scp</command> during the installation)<phrase arch="not-s390"> and
-<classname>ppp-udeb</classname> (see <xref linkend="pppoe"/>)</phrase>.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>netcfg/disable_dhcp</term>
-<listitem><para>
-
-Set to <userinput>true</userinput> if you want to disable DHCP and instead
-force static network configuration.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>mirror/protocol (protocol)</term>
-<listitem><para>
-
-By default the installer will use the http protocol to download files from
-&debian; mirrors and changing that to ftp is not possible during installations
-at normal priority. By setting this parameter to <userinput>ftp</userinput>,
-you can force the installer to use that protocol instead. Note that you
-cannot select an ftp mirror from a list, you have to enter the hostname
-manually.
-
-</para></listitem>
-</varlistentry>
-
-<varlistentry>
-<term>tasksel:tasksel/first (tasks)</term>
-<listitem><para>
-
-Can be used to select tasks that are not available from the interactive task
-list, such as the <literal>kde-desktop</literal> task.
-See <xref linkend="pkgsel"/> for additional information.
-
-</para></listitem>
-</varlistentry>
-
-</variablelist>
-
- </sect2>
-
- <sect2 id="module-parms">
- <title>Passing parameters to kernel modules</title>
-<para>
-
-If drivers are compiled into the kernel, you can pass parameters to them
-as described in the kernel documentation. However, if drivers are compiled
-as modules and because kernel modules are loaded a bit differently during
-an installation than when booting an installed system, it is not possible
-to pass parameters to modules as you would normally do. Instead, you need
-to use a special syntax recognized by the installer which will then make
-sure that the parameters are saved in the proper configuration files and
-will thus be used when the modules are actually loaded. The parameters
-will also be propagated automatically to the configuration for the installed
-system.
-
-</para><para>
-
-Note that it is now quite rare that parameters need to be passed to modules.
-In most cases the kernel will be able to probe the hardware present in a
-system and set good defaults that way. However, in some situations it may
-still be needed to set parameters manually.
-
-</para><para>
-
-The syntax to use to set parameters for modules is:
-
-<informalexample><screen>
-<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable>
-</screen></informalexample>
-
-If you need to pass multiple parameters to the same or different modules,
-just repeat this. For example, to set an old 3Com network interface card
-to use the BNC (coax) connector and IRQ 10, you would pass:
-
-<informalexample><screen>
-3c509.xcvr=3 3c509.irq=10
-</screen></informalexample>
-
-</para>
- </sect2>
-
- <sect2 id="module-blacklist">
- <title>Blacklisting kernel modules</title>
-<para>
-
-Sometimes it may be necessary to blacklist a module to prevent it from
-being loaded automatically by the kernel and udev. One reason could be that
-a particular module causes problems with your hardware. The kernel also
-sometimes lists two different drivers for the same device. This can cause
-the device to not work correctly if the drivers conflict or if the wrong
-driver is loaded first.
-
-</para><para>
-
-You can blacklist a module using the following syntax:
-<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>.
-This will cause the module to be blacklisted in
-<filename>/etc/modprobe.d/blacklist.local</filename> both during the
-installation and for the installed system.
-
-</para><para>
-
-Note that a module may still be loaded by the installation system itself.
-You can prevent that from happening by running the installation in expert
-mode and unselecting the module from the list of modules displayed during
-the hardware detection phases.
-
-</para>
- </sect2>
- </sect1>
diff --git a/nl/boot-installer/powerpc.xml b/nl/boot-installer/powerpc.xml
deleted file mode 100644
index c11cbc4ba..000000000
--- a/nl/boot-installer/powerpc.xml
+++ /dev/null
@@ -1,262 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 56248 untranslated -->
-
- <sect2 arch="powerpc" id="boot-cd"><title>Booting from a CD-ROM</title>
-
-&boot-installer-intro-cd.xml;
-
-<para>
-
-Currently, the only &arch-title; subarchitectures that support CD-ROM
-booting are PReP (though not all systems) and New World PowerMacs.
-On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of
-<keycap>Command</keycap>, <keycap>Option</keycap>,
-<keycap>Shift</keycap>, and <keycap>Delete</keycap>
-keys together while booting to boot from the CD-ROM.
-
-</para><para>
-
-OldWorld PowerMacs will not boot a &debian; CD, because OldWorld
-computers relied on a Mac OS ROM CD boot driver to be present on the CD,
-and a free-software version of this driver is not available. All
-OldWorld systems have floppy drives, so use the floppy drive to launch
-the installer, and then point the installer to the CD for the needed
-files.
-
-</para><para>
-
-If your system doesn't boot directly from CD-ROM, you can still use
-the CD-ROM to install the system. On NewWorlds, you can also use an
-OpenFirmware command to boot from the CD-ROM manually. Follow the
-instructions in <xref linkend="boot-newworld"/> for booting from
-the hard disk, except use the path to <command>yaboot</command> on the
-CD at the OF prompt, such as
-
-<informalexample><screen>
-0 &gt; boot cd:,\install\yaboot
-</screen></informalexample>
-
-</para>
- </sect2>
-
- <sect2 arch="powerpc" id="install-drive">
- <title>Booting from Hard Disk</title>
-
-&boot-installer-intro-hd.xml;
-
-<!--
- <sect3><title>Booting CHRP from OpenFirmware</title>
-
-<para>
-
- <emphasis>Not yet written.</emphasis>
-
-</para>
- </sect3>
--->
-
- <sect3><title>Booting OldWorld PowerMacs from MacOS</title>
-<para>
-
-If you set up BootX in <xref linkend="files-oldworld"/>, you can
-use it to boot into the installation system. Double click the
-<guiicon>BootX</guiicon> application icon. Click on the
-<guibutton>Options</guibutton> button and select <guilabel>Use
-Specified RAM Disk</guilabel>. This will give you the
-chance to select the <filename>ramdisk.image.gz</filename> file. You
-may need to select the <guilabel>No Video Driver</guilabel> checkbox,
-depending on your hardware. Then click the
-<guibutton>Linux</guibutton> button to shut down MacOS and launch the
-installer.
-
-</para>
- </sect3>
-
-
- <sect3 id="boot-newworld">
- <title>Booting NewWorld Macs from OpenFirmware</title>
-<para>
-
-You will have already placed the <filename>vmlinux</filename>,
-<filename>initrd.gz</filename>, <filename>yaboot</filename>, and
-<filename>yaboot.conf</filename> files at the root level of your HFS
-partition in <xref linkend="files-newworld"/>.
-You will now have to boot into OpenFirmware (see <xref linkend="invoking-openfirmware"/>).
-At the prompt, type
-
-<informalexample><screen>
-0 &gt; boot hd:<replaceable>x</replaceable>,yaboot
-</screen></informalexample>
-
-replacing <replaceable>x</replaceable> with the partition number of
-the HFS partition where the
-kernel and yaboot files were placed, followed by a &enterkey;. On some
-machines, you may need to use <userinput>ide0:</userinput> instead of
-<userinput>hd:</userinput>. In a few more seconds you will see a
-yaboot prompt
-
-<informalexample><screen>
-boot:
-</screen></informalexample>
-
-At yaboot's <prompt>boot:</prompt> prompt, type either
-<userinput>install</userinput> or <userinput>install video=ofonly</userinput>
-followed by a &enterkey;. The
-<userinput>video=ofonly</userinput> argument is for maximum
-compatibility; you can try it if <userinput>install</userinput>
-doesn't work. The &debian; installation program should start.
-
-</para>
- </sect3>
- </sect2>
-
- <sect2 arch="powerpc" condition="bootable-usb" id="usb-boot">
- <title>Booting from USB memory stick</title>
-<para>
-
-Currently, NewWorld PowerMac systems are known to support USB booting.
-
-</para>
-
-<para>
-
-Make sure you have prepared everything from <xref
-linkend="boot-usb-files"/>. To boot a Macintosh system from a USB stick,
-you will need to use the Open Firmware prompt, since Open Firmware does
-not search USB storage devices by default.
-<!-- TODO: although it could be made to; watch this space -->
-See <xref linkend="invoking-openfirmware"/>.
-
-</para><para>
-
-You will need to work out where the USB storage device appears in the
-device tree, since at the moment <command>ofpath</command> cannot work
-that out automatically. Type <userinput>dev / ls</userinput> and
-<userinput>devalias</userinput> at the Open Firmware prompt to get a
-list of all known devices and device aliases. On the author's system
-with various types of USB stick, paths such as
-<filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>,
-<filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and
-<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work.
-
-</para><para>
-
-Having worked out the device path, use a command like this to boot the
-installer:
-
-<informalexample><screen>
-boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\:tbxi
-</screen></informalexample>
-
-The <replaceable>2</replaceable> matches the Apple_HFS or
-Apple_Bootstrap partition onto which you copied the boot image earlier,
-and the <userinput>,\\:tbxi</userinput> part instructs Open Firmware to
-boot from the file with an HFS file type of "tbxi" (i.e.
-<command>yaboot</command>) in the directory previously blessed with
-<command>hattrib -b</command>.
-
-</para><para>
-
-The system should now boot up, and you should be presented with the
-<prompt>boot:</prompt> prompt. Here you can enter optional boot
-arguments, or just hit &enterkey;.
-
-</para><warning><para>
-
-This boot method is new, and may be difficult to get to work on some
-NewWorld systems. If you have problems, please file an installation
-report, as explained in <xref linkend="submit-bug"/>.
-
-</para></warning>
- </sect2>
-
- <sect2 arch="powerpc" id="boot-tftp"><title>Booting with TFTP</title>
-
-&boot-installer-intro-net.xml;
-
-<para>
-
-Currently, PReP and New World PowerMac systems support netbooting.
-
-</para><para>
-
-On machines with Open Firmware, such as NewWorld Power Macs, enter the
-boot monitor (see <xref linkend="invoking-openfirmware"/>) and
-use the command
-
-<informalexample><screen>
-0 &gt; boot enet:0
-</screen></informalexample>
-
-If this doesn't work, you might have to add the filename like this:
-
-<informalexample><screen>
-0 &gt; boot enet:0,yaboot
-</screen></informalexample>
-
-PReP and CHRP boxes
-may have different ways of addressing the network. On a PReP machine,
-you should try
-
-<informalexample><screen>
-boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable>
-</screen></informalexample>
-
-On some PReP systems (e.g. Motorola PowerStack machines) the command
-<userinput>help boot</userinput> may give a description of syntax and
-available options.
-
-</para>
- </sect2>
-
-
- <sect2 arch="powerpc" condition="supports-floppy-boot">
- <title>Booting from Floppies</title>
-<para>
-
-Booting from floppies is supported for &arch-title;, although it is
-generally only applicable for OldWorld systems. NewWorld systems are
-not equipped with floppy drives, and attached USB floppy drives are
-not supported for booting.
-
-</para><para>
-
-You will have already downloaded the floppy images you needed and
-created floppies from the images in <xref linkend="create-floppy"/>.
-
-</para><para>
-
-To boot from the <filename>boot-floppy-hfs.img</filename> floppy,
-place it in floppy drive after shutting the system down, and before
-pressing the power-on button.
-
-</para><note><para>
-For those not familiar with Macintosh
-floppy operations: a floppy placed in the machine prior to boot will
-be the first priority for the system to boot from. A floppy without a
-valid boot system will be ejected, and the machine will then check for
-bootable hard disk partitions.
-
-</para></note><para>
-
-After booting, the <filename>root.bin</filename> floppy is
-requested. Insert the root floppy and press &enterkey;. The installer
-program is automatically launched after the root system has been
-loaded into memory.
-
-</para>
- </sect2>
-
-
- <sect2 arch="powerpc"><title>PowerPC Boot Parameters</title>
-<para>
-
-Many older Apple monitors used a 640x480 67Hz mode. If your video
-appears skewed on an older Apple monitor, try appending the boot
-argument <userinput>video=atyfb:vmode:6</userinput> , which will
-select that mode for most Mach64 and Rage video hardware. For Rage 128
-hardware, this changes to
-<userinput>video=aty128fb:vmode:6</userinput> .
-
-</para>
- </sect2>
diff --git a/nl/boot-installer/s390.xml b/nl/boot-installer/s390.xml
deleted file mode 100644
index f7991b127..000000000
--- a/nl/boot-installer/s390.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 43745 untranslated -->
-
- <sect2 arch="s390"><title>s390 Limitations</title>
-<para>
-
-In order to run the installation system a working network setup and
-ssh session is needed on S/390.
-
-</para><para>
-
-The booting process starts with a network setup that prompts you for
-several network parameters. If the setup is successful, you will login
-to the system by starting an ssh session which will launch the
-standard installation system.
-
-</para>
- </sect2>
-
-
- <sect2 arch="s390"><title>s390 Boot Parameters</title>
-<para>
-
-On S/390 you can append boot parameters in the parm file. This file can
-either be in ASCII or EBCDIC format.
-A sample parm file <filename>parmfile.debian</filename> is provided with
-the installation images.
-
-<!-- Link is bad; commented out for now
-Please read
-<ulink url="&url-s390-devices;">Device Drivers and Installation Commands</ulink>
-for more information about S/390-specific boot parameters.
--->
-
-</para>
- </sect2>
diff --git a/nl/boot-installer/sparc.xml b/nl/boot-installer/sparc.xml
deleted file mode 100644
index faf39b310..000000000
--- a/nl/boot-installer/sparc.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 58021 untranslated -->
-
- <sect2 arch="sparc" id="boot-tftp"><title>Booting with TFTP</title>
-
-&boot-installer-intro-net.xml;
-
-<para>
-
-On machines with OpenBoot, simply enter the boot monitor on the
-machine which is being installed (see
-<xref linkend="invoking-openboot"/>).
-Use the command <userinput>boot net</userinput> to boot from a TFTP
-and RARP server, or try <userinput>boot net:bootp</userinput> or
-<userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP
-or DHCP server. You can pass extra boot parameters to &d-i; at the end
-of the <userinput>boot</userinput> command.
-
-</para>
- </sect2>
-
-
- <sect2 arch="sparc"><title>Booting from a CD-ROM</title>
-
-&boot-installer-intro-cd.xml;
-
-<para>
-
-Most OpenBoot versions support the <userinput>boot cdrom</userinput>
-command which is simply an alias to boot from the SCSI device on ID 6
-(or the secondary master for IDE based systems).
-
-</para>
- </sect2>
-
- <sect2 arch="sparc"><title>IDPROM Messages</title>
-<para>
-
-If you cannot boot because you get messages about a problem with
-<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which
-holds configuration information for you firmware, has run out. See the
-<ulink url="&url-sun-nvram-faq;">Sun NVRAM FAQ</ulink> for more
-information.
-
-</para>
- </sect2>
diff --git a/nl/boot-installer/trouble.xml b/nl/boot-installer/trouble.xml
deleted file mode 100644
index 392e7f1f0..000000000
--- a/nl/boot-installer/trouble.xml
+++ /dev/null
@@ -1,572 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 56669 untranslated -->
-
- <sect1 id="boot-troubleshooting">
- <title>Troubleshooting the Installation Process</title>
-<para>
-</para>
-
- <sect2 arch="not-s390" id="unreliable-cd">
- <title>CD-ROM Reliability</title>
-<para>
-
-Sometimes, especially with older CD-ROM drives, the installer may fail
-to boot from a CD-ROM. The installer may also &mdash; even after booting
-successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return
-errors while reading from it during the installation.
-
-</para><para>
-
-There are many different possible causes for these problems. We can
-only list some common issues and provide general suggestions on how to
-deal with them. The rest is up to you.
-
-</para><para>
-
-There are two very simple things that you should try first.
-
-<itemizedlist>
-<listitem><para>
-
-If the CD-ROM does not boot, check that it was inserted correctly and that
-it is not dirty.
-
-</para></listitem>
-<listitem><para>
-
-If the installer fails to recognize a CD-ROM, try just running the option
-<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice>
-a second time. Some DMA related issues with older CD-ROM drives are known to
-be resolved in this way.
-
-</para></listitem>
-</itemizedlist>
-
-</para><para>
-
-If this does not work, then try the suggestions in the subsections below.
-Most, but not all, suggestions discussed there are valid for both CD-ROM and
-DVD, but we'll use the term CD-ROM for simplicity.
-
-</para><para>
-
-If you cannot get the installation working from CD-ROM, try one of the
-other installation methods that are available.
-
-</para>
-
- <sect3>
- <title>Common issues</title>
-
-<itemizedlist>
- <listitem><para>
-
-Some older CD-ROM drives do not support reading from discs that were burned
-at high speeds using a modern CD writer.
-
- </para></listitem>
- <listitem><para>
-
-If your system boots correctly from the CD-ROM, it does not necessarily
-mean that &arch-kernel; also supports the CD-ROM (or, more correctly, the controller
-that your CD-ROM drive is connected to).
-
- </para></listitem>
- <listitem><para>
-
-Some older CD-ROM drives do not work correctly if <quote>direct memory
-access</quote> (DMA) is enabled.
-
- </para></listitem>
-</itemizedlist>
-
- </sect3>
-
- <sect3>
- <title>How to investigate and maybe solve issues</title>
-<para>
-
-If the CD-ROM fails to boot, try the suggestions listed below.
-
-<itemizedlist>
- <listitem><para>
-
-Check that your BIOS actually supports booting from CD-ROM (older systems
-possibly don't) and that your CD-ROM drive supports the media you are using.
-
- </para></listitem>
- <listitem><para>
-
-If you downloaded an iso image, check that the md5sum of that image matches
-the one listed for the image in the <filename>MD5SUMS</filename> file that
-should be present in the same location as where you downloaded the image
-from.
-
-<informalexample><screen>
-$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>
-a20391b12f7ff22ef705cee4059c6b92 <replaceable>debian-testing-i386-netinst.iso</replaceable>
-</screen></informalexample>
-
-Next, check that the md5sum of the burned CD-ROM matches as well. The
-following command should work. It uses the size of the image to read the
-correct number of bytes from the CD-ROM.
-
-<informalexample><screen>
-$ dd if=/dev/cdrom | \
-> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \
-> md5sum
-a20391b12f7ff22ef705cee4059c6b92 -
-262668+0 records in
-262668+0 records out
-134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s
-</screen></informalexample>
-
- </para></listitem>
-</itemizedlist>
-
-</para><para>
-
-If, after the installer has been booted successfully, the CD-ROM is not
-detected, sometimes simply trying again may solve the problem. If you have
-more than one CD-ROM drive, try changing the CD-ROM to the other drive.
-If that does not work or if the CD-ROM is recognized but there are errors
-when reading from it, try the suggestions listed below. Some basic knowledge
-of &arch-kernel; is required for this.
-To execute any of the commands, you should first switch to the second
-virtual console (VT2) and activate the shell there.
-
-<itemizedlist>
- <listitem><para>
-
-Switch to VT4 or view the contents of <filename>/var/log/syslog</filename>
-(use <command>nano</command> as editor) to check for any specific error
-messages. After that, also check the output of <command>dmesg</command>.
-
- </para></listitem>
- <listitem><para>
-
-Check in the output of <command>dmesg</command> if your CD-ROM drive was
-recognized. You should see something like (the lines do not necessarily
-have to be consecutive):
-
-<informalexample><screen>
-Probing IDE interface ide1...
-hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive
-ide1 at 0x170-0x177,0x376 on irq 15
-hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
-Uniform CD-ROM driver Revision: 3.20
-</screen></informalexample>
-
-If you don't see something like that, chances are the controller your CD-ROM
-is connected to was not recognized or may be not supported at all. If you
-know what driver is needed for the controller, you can try loading it manually
-using <command>modprobe</command>.
-
- </para></listitem>
- <listitem><para>
-
-Check that there is a device node for your CD-ROM drive under
-<filename>/dev/</filename>. In the example above, this would be
-<filename>/dev/hdc</filename>.
-There should also be a <filename>/dev/cdrom</filename>.
-
- </para></listitem>
- <listitem><para>
-
-Use the <command>mount</command> command to check if the CD-ROM is already
-mounted; if not, try mounting it manually:
-
-<informalexample><screen>
-$ mount /dev/<replaceable>hdc</replaceable> /cdrom
-</screen></informalexample>
-
-Check if there are any error messages after that command.
-
- </para></listitem>
- <listitem><para>
-
-Check if DMA is currently enabled:
-
-<informalexample><screen>
-$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>
-$ grep using_dma settings
-using_dma 1 0 1 rw
-</screen></informalexample>
-
-A <quote>1</quote> in the first column after <literal>using_dma</literal>
-means it is enabled. If it is, try disabling it:
-
-<informalexample><screen>
-$ echo -n "using_dma:0" >settings
-</screen></informalexample>
-
-Make sure that you are in the directory for the device that corresponds
-to your CD-ROM drive.
-
- </para></listitem>
- <listitem><para>
-
-If there are any problems during the installation, try checking the integrity
-of the CD-ROM using the option near the bottom of the installer's main menu.
-This option can also be used as a general test if the CD-ROM can be read
-reliably.
-
- </para></listitem>
-</itemizedlist>
-
-</para>
- </sect3>
- </sect2>
-
- <sect2 condition="supports-floppy-boot" id="unreliable-floppies">
- <title>Floppy Disk Reliability</title>
-
-<para>
-
-The biggest problem for people using floppy disks to install &debian;
-seems to be floppy disk reliability.
-
-</para><para>
-
-The boot floppy is the floppy with the worst problems, because it
-is read by the hardware directly, before Linux boots. Often, the
-hardware doesn't read as reliably as the Linux floppy disk driver, and
-may just stop without printing an error message if it reads incorrect
-data. There can also be failures in the driver floppies, most of which
-indicate themselves with a flood of messages about disk I/O errors.
-
-</para><para>
-
-If you are having the installation stall at a particular floppy, the first
-thing you should do is write the image to a <emphasis>different</emphasis>
-floppy and see if that solves the problem. Simply reformatting the old
-floppy may not be sufficient, even if it appears that the floppy was
-reformatted and written with no errors. It is sometimes useful to try
-writing the floppy on a different system.
-
-</para><para>
-
-One user reports he had to write the images to floppy
-<emphasis>three</emphasis> times before one worked, and then
-everything was fine with the third floppy.
-
-</para><para>
-
-Normally you should not have to download a floppy image again, but if you
-are experiencing problems it is always useful to verify that the images
-were downloaded correctly by verifying their md5sums.
-
-</para><para>
-
-Other users have reported that simply rebooting a few times with the
-same floppy in the floppy drive can lead to a successful boot. This is
-all due to buggy hardware or firmware floppy drivers.
-
-</para>
- </sect2>
-
- <sect2><title>Boot Configuration</title>
-
-<para>
-
-If you have problems and the kernel hangs during the boot process,
-doesn't recognize peripherals you actually have, or drives are not
-recognized properly, the first thing to check is the boot parameters,
-as discussed in <xref linkend="boot-parms"/>.
-
-</para><para>
-
-Often, problems can be solved by removing add-ons and peripherals, and
-then trying booting again. <phrase arch="any-x86">Internal modems, sound
-cards, and Plug-n-Play devices can be especially problematic.</phrase>
-
-</para><para>
-
-If you have a large amount of memory installed in your machine, more
-than 512M, and the installer hangs when booting the kernel, you may
-need to include a boot argument to limit the amount of memory the
-kernel sees, such as <userinput>mem=512m</userinput>.
-
-</para>
- </sect2>
-
- <sect2 arch="x86" id="i386-boot-problems">
- <title>Common &arch-title; Installation Problems</title>
-<para>
-
-There are some common installation problems that can be solved or avoided by
-passing certain boot parameters to the installer.
-
-</para><para>
-
-Some systems have floppies with <quote>inverted DCLs</quote>. If you receive
-errors reading from the floppy, even when you know the floppy is good,
-try the parameter <userinput>floppy=thinkpad</userinput>.
-
-</para><para>
-
-On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506
-disk drivers), the IDE drive may not be properly recognized. Again,
-try it first without the parameters and see if the IDE drive is
-recognized properly. If not, determine your drive geometry
-(cylinders, heads, and sectors), and use the parameter
-<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>.
-
-</para><para>
-
-If you have a very old machine, and the kernel hangs after saying
-<computeroutput>Checking 'hlt' instruction...</computeroutput>, then
-you should try the <userinput>no-hlt</userinput> boot argument, which
-disables this test.
-
-</para><para>
-
-Some systems (especially laptops) that have a native resolution that is not
-a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank
-display after the installer has been booted. In that case adding the boot
-parameter <userinput>vga=788</userinput><footnote>
-
-<para>
-The parameter <userinput>vga=788</userinput> will activate the VESA
-framebuffer with a resolution of 800x600. This will probably work, but may
-not be the optimal resolution for your system. A list of supported
-resolutions can be obtained by using <userinput>vga=ask</userinput>, but
-you should be aware that list may not be complete.
-</para>
-
-</footnote> may help. If that does not work,
-try adding the boot parameter <userinput>fb=false</userinput>.
-
-</para><para>
-
-If your screen begins to show a weird picture while the kernel boots,
-eg. pure white, pure black or colored pixel garbage, your system may
-contain a problematic video card which does not switch to the
-framebuffer mode properly. Then you can use the boot parameter
-<userinput>fb=false</userinput> to disable the framebuffer
-console. Only a reduced set of
-languages will be available during the installation due to limited
-console features. See <xref linkend="boot-parms"/> for details.
-
-</para>
-
- <sect3>
- <title>System Freeze During the PCMCIA Configuration Phase</title>
-<para>
-
-Some laptop models produced by Dell are known to crash when PCMCIA device
-detection tries to access some hardware addresses. Other laptops may display
-similar problems. If you experience such a problem and you don't need PCMCIA
-support during the installation, you can disable PCMCIA using the
-<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can
-then configure PCMCIA after the installation is completed and exclude the
-resource range causing the problems.
-
-</para><para>
-
-Alternatively, you can boot the installer in expert mode. You will
-then be asked to enter the resource range options your hardware
-needs. For example, if you have one of the Dell laptops mentioned
-above, you should enter <userinput>exclude port
-0x800-0x8ff</userinput> here. There is also a list of some common
-resource range options in the <ulink
-url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System
-resource settings section of the PCMCIA HOWTO</ulink>. Note that you
-have to omit the commas, if any, when you enter this value in the
-installer.
-
-</para>
- </sect3>
-
- <sect3>
- <title>System Freeze while Loading USB Modules</title>
-<para>
-
-The kernel normally tries to install USB modules and the USB keyboard driver
-in order to support some non-standard USB keyboards. However, there are some
-broken USB systems where the driver hangs on loading. A possible workaround
-may be disabling the USB controller in your mainboard BIOS setup. Another option
-is passing the <userinput>nousb</userinput> parameter at the boot prompt.
-
-</para>
- </sect3>
- </sect2>
-
- <sect2 arch="sparc" id="sparc-boot-problems">
- <title>Common &arch-title; Installation Problems</title>
-<para>
-
-There are some common installation problems that are worth mentioning.
-
-</para>
- <sect3>
- <title>Misdirected video output</title>
-<para>
-
-It is fairly common for &arch-title; to have two video cards in one machine,
-for example an ATI card and a Sun Creator 3D. In some cases, this may result
-in the video output getting misdirected soon after the system boots. In
-typical cases, the display will only show:
-
-<informalexample><screen>
-Remapping the kernel... done
-Booting Linux...
-</screen></informalexample>
-
-To work around this, you can either pull out one of the video cards, or
-disable the one not used during the OpenProm boot phase using a kernel
-parameter. For example, to disable an ATI card, you should boot the
-installer with <userinput>video=atyfb:off</userinput>.
-
-</para><para>
-
-Note that you may also have to manually add this parameter to the silo
-configuration (edit <filename>/target/etc/silo.conf</filename> before
-rebooting) and, if you installed X11, modify the video driver in
-<filename>/etc/X11/xorg.conf</filename>.
-
-</para>
- </sect3>
-
- <sect3>
- <title>Failure to Boot or Install from CD-ROM</title>
-<para>
-
-Some Sparc systems are notoriously difficult to boot from CD-ROM and
-even if they do boot, there may be inexplicable failures during the
-installation. Most problems have been reported with SunBlade systems.
-
-</para><para>
-
-We recommend to install such systems by netbooting the installer.
-
-</para>
- </sect3>
- </sect2>
-
- <sect2 id="kernel-msgs">
- <title>Interpreting the Kernel Startup Messages</title>
-
-<para>
-
-During the boot sequence, you may see many messages in the form
-<computeroutput>can't find <replaceable>something</replaceable></computeroutput>,
-or <computeroutput><replaceable>something</replaceable>
-not present</computeroutput>, <computeroutput>can't initialize
-<replaceable>something</replaceable></computeroutput>,
-or even <computeroutput>this driver release depends
-on <replaceable>something</replaceable></computeroutput>.
-Most of these messages are harmless. You
-see them because the kernel for the installation system is built to
-run on computers with many different peripheral devices. Obviously, no
-one computer will have every possible peripheral device, so the
-operating system may emit a few complaints while it looks for
-peripherals you don't own. You may also see the system pause for a
-while. This happens when it is waiting for a device to respond, and
-that device is not present on your system. If you find the time it
-takes to boot the system unacceptably long, you can create a
-custom kernel later <phrase arch="linux-any">(see <xref linkend="kernel-baking"/>)</phrase>.
-
-</para>
- </sect2>
-
-
- <sect2 id="problem-report">
- <title>Reporting Installation Problems</title>
-<para>
-
-If you get through the initial boot phase but cannot complete the install,
-the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful.
-It lets you store system error logs and configuration information from the
-installer to a floppy, or download them using a web browser.
-
-This information may provide clues as to what went wrong and how to
-fix it. If you are submitting a bug report, you may want to attach
-this information to the bug report.
-
-</para><para>
-
-Other pertinent installation messages may be found in
-<filename>/var/log/</filename> during the
-installation, and <filename>/var/log/installer/</filename>
-after the computer has been booted into the installed system.
-
-</para>
- </sect2>
-
- <sect2 id="submit-bug">
- <title>Submitting Installation Reports</title>
-<para>
-
-If you still have problems, please submit an installation report. We also
-encourage installation reports to be sent even if the installation is
-successful, so that we can get as much information as possible on the largest
-number of hardware configurations.
-
-</para><para>
-
-Note that your installation report will be published in the &debian; Bug
-Tracking System (BTS) and forwarded to a public mailing list. Make sure that
-you use an e-mail address that you do not mind being made public.
-
-</para><para>
-
-If you have a working &debian; system, the easiest way to send an installation
-report is to install the <classname>installation-report</classname> and
-<classname>reportbug</classname> packages
-(<command>aptitude install installation-report reportbug</command>),
-configure <classname>reportbug</classname> as explained in
-<xref linkend="mail-outgoing"/>, and run the command <command>reportbug
-installation-reports</command>.
-
-</para><para>
-
-Alternatively you can use this template when filling out
-installation reports, and file the report as a bug report against the
-<classname>installation-reports</classname> pseudo package, by sending it to
-<email>submit@bugs.debian.org</email>.
-
-<informalexample><screen>
-Package: installation-reports
-
-Boot method: &lt;How did you boot the installer? CD? floppy? network?&gt;
-Image version: &lt;Full URL to image you downloaded is best&gt;
-Date: &lt;Date and time of the install&gt;
-
-Machine: &lt;Description of machine (eg, IBM Thinkpad R32)&gt;
-Processor:
-Memory:
-Partitions: &lt;df -Tl will do; the raw partition table is preferred&gt;
-
-Output of lspci -knn (or lspci -nn):
-
-Base System Installation Checklist:
-[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
-
-Initial boot: [ ]
-Detect network card: [ ]
-Configure network: [ ]
-Detect CD: [ ]
-Load installer modules: [ ]
-Detect hard drives: [ ]
-Partition hard drives: [ ]
-Install base system: [ ]
-Clock/timezone setup: [ ]
-User/password setup: [ ]
-Install tasks: [ ]
-Install boot loader: [ ]
-Overall install: [ ]
-
-Comments/Problems:
-
-&lt;Description of the install, in prose, and any thoughts, comments
- and ideas you had during the initial install.&gt;
-</screen></informalexample>
-
-In the bug report, describe what the problem is, including the last
-visible kernel messages in the event of a kernel hang. Describe the
-steps that you did which brought the system into the problem state.
-
-</para>
- </sect2>
- </sect1>
diff --git a/nl/boot-installer/x86.xml b/nl/boot-installer/x86.xml
deleted file mode 100644
index e090058db..000000000
--- a/nl/boot-installer/x86.xml
+++ /dev/null
@@ -1,433 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 62896 untranslated -->
-
- <sect2 arch="any-x86"><title>Booting from a CD-ROM</title>
-
-&boot-installer-intro-cd.xml;
-
-<!-- We'll comment the following section until we know exact layout -->
-<!--
-CD #1 of official &debian; CD-ROM sets for &arch-title; will present a
-<prompt>boot:</prompt> prompt on most hardware. Press
-<keycap>F4</keycap> to see the list of kernel options available
-from which to boot. Just type your chosen flavor name (idepci,
-vanilla, compact, bf24) at the <prompt>boot:</prompt> prompt
-followed by &enterkey;.
-
-</para><para>
-
-If your hardware doesn't support booting of multiple images, put one
-of the other CDs in the drive. It appears that most SCSI CD-ROM drives
-do not support <command>isolinux</command> multiple image booting, so users
-with SCSI CD-ROMs should try either CD2 (vanilla) or CD3 (compact),
-or CD5 (bf2.4).
-
-</para><para>
-
-CD's 2 through 5 will each boot a
-different ``flavor'' depending on which CD-ROM is
-inserted. See <xref linkend="kernel-choice"/> for a discussion of the
-different flavors. Here's how the flavors are laid out on the
-different CD-ROMs:
-
-<variablelist>
-<varlistentry>
-<term>CD 1</term><listitem><para>
-
-Allows a selection of kernel images to boot from (the idepci flavor is
-the default if no selection is made).
-
-</para></listitem></varlistentry>
-<varlistentry>
-<term>CD 2</term><listitem><para>
-
-Boots the <quote>vanilla</quote> flavor.
-
-</para></listitem></varlistentry>
-<varlistentry>
-<term>CD 3</term><listitem><para>
-
-Boots the <quote>compact</quote> flavor.
-
-</para></listitem></varlistentry>
-<varlistentry>
-<term>CD 4</term><listitem><para>
-
-Boots the <quote>idepci</quote> flavor.
-
-</para></listitem></varlistentry>
-<varlistentry>
-<term>CD 5</term><listitem><para>
-
-Boots the <quote>bf2.4</quote> flavor.
-
-</para></listitem></varlistentry>
-
- </variablelist>
-
-</para><para>
-
--->
-
- </sect2>
-
- <sect2 arch="any-x86" id="boot-win32">
- <title>Booting from Windows</title>
-<para>
-
-To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM
-or USB memory stick installation media as described in
-<xref linkend="official-cdrom"/> and <xref linkend="boot-usb-files"/>.
-
-</para><para>
-
-If you use an installation CD or DVD, a pre-installation program should be
-launched automatically when you insert the disc.
-In case Windows does not start it automatically, or if you are using a USB
-memory stick, you can run it manually by accessing the device and executing
-<command>setup.exe</command>.
-
-</para><para>
-
-After the program has been started, a few preliminary questions will be
-asked and the system will be prepared to start the &debian-gnu; installer.
-
-</para>
- </sect2>
-
-<!-- FIXME the documented procedure does not exactly work, commented out
- until fixes
-
- <sect2 arch="x86" id="install-from-dos">
- <title>Booting from a DOS partition</title>
-
-&boot-installer-intro-hd.xml;
-
-<para>
-
-Boot into DOS (not Windows) without any drivers being loaded. To do
-this, you have to press <keycap>F8</keycap> at exactly the right
-moment (and optionally select the <quote>safe mode command prompt only</quote>
-option). Enter the subdirectory for the flavor you chose, e.g.,
-
-<informalexample><screen>
-cd c:\install
-</screen></informalexample>.
-
-Next, execute <command>install.bat</command>.
-The kernel will load and launch the installer system.
-
-</para><para>
-
-Please note, there is currently a loadlin problem (#142421) which
-precludes <filename>install.bat</filename> from being used with the
-bf2.4 flavor. The symptom of the problem is an
-<computeroutput>invalid compressed format</computeroutput> error.
-
-</para>
- </sect2>
-
-END FIXME -->
-
- <sect2 arch="x86" id="boot-initrd">
- <title>Booting from Linux Using <command>LILO</command> or
- <command>GRUB</command></title>
-
-<para>
-To boot the installer from hard disk, you must first download
-and place the needed files as described in <xref linkend="boot-drive-files"/>.
-</para>
-
-<para>
-If you intend to use the hard drive only for booting and then
-download everything over the network, you should download the
-<filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its
-corresponding kernel
-<filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you
-to repartition the hard disk from which you boot the installer, although you
-should do so with care.
-</para>
-
-<para>
-Alternatively, if you intend to keep an existing partition on the hard
-drive unchanged during the install, you can download the
-<filename>hd-media/initrd.gz</filename> file and its kernel, as well as
-copy a CD (or DVD) iso to the drive (make sure the file is named ending in
-<literal>.iso</literal>). The installer can then boot from the drive
-and install from the CD/DVD image, without needing the network.
-</para>
-
-<para>
-For <command>LILO</command>, you will need to configure two
-essential things in <filename>/etc/lilo.conf</filename>:
-<itemizedlist>
-<listitem><para>
-
-to load the <filename>initrd.gz</filename> installer at boot time;
-
-</para></listitem>
-<listitem><para>
-
-have the <filename>vmlinuz</filename> kernel use a RAM disk as
-its root partition.
-
-</para></listitem>
-</itemizedlist>
-
-Here is a <filename>/etc/lilo.conf</filename> example:
-
-</para><para>
-
-<informalexample><screen>
-image=/boot/newinstall/vmlinuz
- label=newinstall
- initrd=/boot/newinstall/initrd.gz
-</screen></informalexample>
-
-For more details, refer to the
-<citerefentry><refentrytitle>initrd</refentrytitle>
-<manvolnum>4</manvolnum></citerefentry> and
-<citerefentry><refentrytitle>lilo.conf</refentrytitle>
-<manvolnum>5</manvolnum></citerefentry> man pages. Now run
-<userinput>lilo</userinput> and reboot.
-
-</para><para>
-
-The procedure for <command>GRUB</command> is quite similar. Locate your
-<filename>menu.lst</filename> in the <filename>/boot/grub/</filename>
-directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an
-entry for the installer, for example (assuming <filename>/boot</filename>
-is on the first partition of the first disk in the system):
-
-<informalexample><screen>
-title New Install
-root (hd0,0)
-kernel /boot/newinstall/vmlinuz
-initrd /boot/newinstall/initrd.gz
-</screen></informalexample>
-
-</para><para>
-
-From here on, there should be no difference between <command>GRUB</command>
-or <command>LILO</command>.
-
-</para>
- </sect2>
-
- <sect2 arch="any-x86" condition="bootable-usb" id="usb-boot">
- <title>Booting from USB Memory Stick</title>
-<para>
-
-Let's assume you have prepared everything from <xref
-linkend="boot-dev-select"/> and <xref linkend="boot-usb-files"/>. Now
-just plug your USB stick into some free USB connector and reboot the
-computer. The system should boot up, and you should be presented with
-the <prompt>boot:</prompt> prompt. Here you can enter optional boot
-arguments, or just hit &enterkey;.
-
-</para>
- </sect2>
-
- <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot">
- <title>Booting from Floppies</title>
-<para>
-
-You will have already downloaded the floppy images you needed and
-created floppies from the images in <xref linkend="create-floppy"/>.
-<!-- missing-doc FIXME If you need to, you can also modify the boot floppy; see
-<xref linkend="rescue-replace-kernel"/>. -->
-
-</para><para>
-
-To boot from the installer boot floppy, place it in the primary floppy
-drive, shut down the system as you normally would, then turn it back
-on.
-
-</para><para>
-
-For installing from an LS-120 drive (ATAPI version) with a set of
-floppies, you need to specify the virtual location for the floppy
-device. This is done with the <emphasis>root=</emphasis> boot
-argument, giving the device that the ide-floppy driver maps the device
-to. For example, if your LS-120 drive is connected as the first IDE
-device (master) on the second cable, you enter
-<userinput>install root=/dev/hdc</userinput> at the boot prompt.
-
-</para><para>
-
-Note that on some machines, <keycombo><keycap>Control</keycap>
-<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not
-properly reset the machine, so a <quote>hard</quote> reboot is recommended. If
-you are installing from an existing operating system (e.g., from a DOS
-box) you don't have a choice. Otherwise, please do a hard reboot when
-booting.
-
-</para><para>
-
-The floppy disk will be accessed, and you should then see a screen
-that introduces the boot floppy and ends with the <prompt>boot:</prompt>
-prompt.
-
-</para><para>
-
-Once you press &enterkey;, you should see the message
-<computeroutput>Loading...</computeroutput>, followed by
-<computeroutput>Uncompressing Linux...</computeroutput>, and
-then a screenfull or so of information about the hardware in your
-system. More information on this phase of the boot process can be
-found below in <xref linkend="kernel-msgs"/>.
-
-</para><para>
-
-After booting from the boot floppy, the root floppy is
-requested. Insert the root floppy and press &enterkey;, and the
-contents are loaded into memory. The installer program
-<command>debian-installer</command> is automatically launched.
-
-</para>
- </sect2>
-
- <sect2 arch="x86" id="boot-tftp"><title>Booting with TFTP</title>
-
-&boot-installer-intro-net.xml;
-
-<para>
-
-There are various ways to do a TFTP boot on i386.
-
-</para>
-
- <sect3><title>NIC or Motherboard that support PXE</title>
-<para>
-
-It could be that your Network Interface Card or Motherboard provides
-PXE boot functionality.
-This is a <trademark class="trade">Intel</trademark> re-implementation
-of TFTP boot. If so, you may be able to configure your BIOS to boot from the
-network.
-
-</para>
- </sect3>
-
- <sect3><title>NIC with Network BootROM</title>
-<para>
-
-It could be that your Network Interface Card provides
-TFTP boot functionality.
-
-</para><para condition="FIXME">
-
-Let us (<email>&email-debian-boot-list;</email>) know how did you manage it.
-Please refer to this document.
-
-</para>
- </sect3>
-
- <sect3><title>Etherboot</title>
-<para>
-
-The <ulink url="http://www.etherboot.org">etherboot project</ulink>
-provides bootdiskettes and even bootroms that do a TFTPboot.
-
-</para>
- </sect3>
- </sect2>
-
- <sect2 arch="x86" id="boot-screen">
- <title>The Boot Screen</title>
-<para>
-
-When the installer boots, you should be presented with a friendly graphical
-screen showing the &debian; logo and a menu:
-
-<informalexample><screen>
-Installer boot menu
-
-Install
-Graphical install
-Advanced options >
-Help
-
-Press ENTER to boot or TAB to edit a menu entry
-</screen></informalexample>
-
-Depending on the installation method you are using, the <quote>Graphical
-install</quote> option may not be available.
-
-</para><para>
-
-For a normal installation, select either the <quote>Install</quote> or
-the <quote>Graphical install</quote> entry &mdash; using either the
-arrow keys on your keyboard or by typing the first (highlighted) letter
-&mdash; and press &enterkey; to boot the installer.
-
-</para><para>
-
-The <quote>Advanced options</quote> entry gives access to a second menu
-that allows to boot the installer in expert mode, in rescue mode and for
-automated installs.
-
-</para><para>
-
-If you wish or need to add any boot parameters for either the installer
-or the kernel, press &tabkey;. This will display the default boot command
-for the selected menu entry and allow to add additional options. The help
-screens (see below) list some common possible options. Press &enterkey; to
-boot the installer with your options; pressing &escapekey; will return you
-to the boot menu and undo any changes you made.
-
-</para><para>
-
-Choosing the <quote>Help</quote> entry will result in the first help screen
-being displayed which gives an overview of all available help screens.
-Note that it is not possible to return to the boot menu after the help
-screens have been displayed. However, the F3 and F4 help screens list
-commands that are equivalent to the boot methods listed in the menu. All
-help screens have a boot prompt at which the boot command can be typed:
-
-<informalexample><screen>
-Press F1 for the help index, or ENTER to boot:
-</screen></informalexample>
-
-At this boot prompt you can either just press &enterkey; to boot the
-installer with default options or enter a specific boot command and,
-optionally, boot parameters. A number of boot parameters which might be
-useful can be found on the various help screens. If you do add any
-parameters to the boot command line, be sure to first type the boot method
-(the default is <userinput>install</userinput>) and a space before the
-first parameter (e.g., <userinput>install fb=false</userinput>).
-
-<note><para>
-
-The keyboard is assumed to have a default American English layout at this
-point. This means that if your keyboard has a different (language-specific)
-layout, the characters that appear on the screen may be different from what
-you'd expect when you type parameters. Wikipedia has a
-<ulink url="&url-us-keymap;">schema of the US keyboard layout</ulink> which
-can be used as a reference to find the correct keys to use.
-
-</para></note>
-<note><para>
-
-If you are using a system that has the BIOS configured to use serial console,
-you may not be able to see the initial graphical splash screen upon booting
-the installer; you may even not see the boot menu. The same can happen if
-you are installing the system via a remote management device that provides a
-text interface to the VGA console. Examples of these devices include the text
-console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's
-<quote>Integrated Remote Assistant</quote> (IRA).
-
-</para><para>
-
-To bypass the graphical boot screen you can either blindly press &escapekey;
-to get a text boot prompt, or (equally blindly) press <quote>H</quote>
-followed by &enterkey; to select the <quote>Help</quote> option described
-above. After that your keystrokes should be echoed at the prompt.
-To prevent the installer from using the framebuffer for the rest of the
-installation, you will also want to add <userinput>vga=normal fb=false</userinput>
-to the boot prompt, as described in the help text.
-
-</para></note>
-</para>
-
- </sect2>