move manual to top-level directory, split out of debian-installer package

5 files changed, 616 insertions, 0 deletions

diff --git a/nl/preparing/bios-setup/i386.xml b/nl/preparing/bios-setup/i386.xml
new file mode 100644
index 000000000..668d4ed20
--- /dev/null
+++ b/nl/preparing/bios-setup/i386.xml
@@ -0,0 +1,332 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 arch="i386" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title>
+
+<para>
+
+BIOS provides the basic functions needed to boot your machine to allow
+your operating system to access your hardware.  Your system probably
+provides a BIOS set-up menu, which is used to configure the BIOS.
+Before installing, you <emphasis>must</emphasis> ensure that your BIOS
+is setup correctly; not doing so can lead to intermittent crashes or
+an inability to install Debian.
+
+</para><para>
+
+The rest of this section is lifted from the
+<ulink url="&url-pc-hw-faq;"></ulink>, answering the question, <quote>How do I
+enter the CMOS configuration menu?</quote>.  How you access the BIOS (or
+<quote>CMOS</quote>) configuration menu depends on who wrote your BIOS
+software:
+
+</para>
+
+<!-- From: burnesa@cat.com (Shaun Burnet) -->
+<variablelist>
+
+<varlistentry>
+ <term>AMI BIOS</term>
+ <listitem><para>
+
+<keycap>Delete</keycap> key during the POST (power on self test)
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Award BIOS</term>
+ <listitem><para>
+
+<keycombo>
+  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap>
+</keycombo>, or <keycap>Delete</keycap> key during the POST
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry><term>DTK BIOS</term>
+ <listitem><para>
+
+<keycap>Esc</keycap> key during the POST
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry><term>IBM PS/2 BIOS</term>
+ <listitem><para>
+
+<keycombo>
+  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap>
+</keycombo>
+after
+<keycombo>
+  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap>
+</keycombo>
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+ <term>Phoenix BIOS</term>
+ <listitem><para>
+
+<keycombo>
+  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap>
+</keycombo>
+or
+<keycombo>
+  <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap>
+</keycombo>
+or
+<keycap>F1</keycap>
+
+</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>
+
+Information on invoking other BIOS routines can be found in
+<ulink url="&url-invoking-bios-info;"></ulink>.
+
+</para><para>
+
+Some &arch-title; machines don't have a CMOS configuration menu in the
+BIOS.  They require a software CMOS setup program.  If you don't have
+the Installation and/or Diagnostics diskette for your machine, you can
+try using a shareware/freeware program.  Try looking in
+<ulink url="&url-simtel;"></ulink>.
+
+</para>
+  </sect2>
+
+  <sect2 arch="i386" id="boot-dev-select"><title>Boot Device Selection</title>
+
+<para>
+
+Many BIOS set-up menus allow you to select the devices that will be
+used to bootstrap the system. Set this to look for a bootable
+operating system on <filename>A:</filename> (the first floppy disk),
+then optionally the first CD-ROM device (possibly appearing as
+<filename>D:</filename> or <filename>E:</filename>), and then from
+<filename>C:</filename> (the first hard disk).  This setting enables
+you to boot from either a floppy disk or a CD-ROM, which are the two
+most common boot devices used to install Debian.
+
+</para><para>
+
+If you have a newer SCSI controller and you have a CD-ROM device
+attached to it, you are usually able to boot from the CD-ROM.  All you
+have to do is enable booting from a CD-ROM in the SCSI-BIOS of your
+controller.
+
+</para><para>
+
+Other popular option is to boot from a USB storage (also called USB
+memory stick or USB key).  Some BIOSes can boot USB storage directly,
+and some cannot. You may need to configure your BIOS to boot from
+a <quote>Removable drive</quote> or even a <quote>USB-ZIP</quote> to
+get it to boot from the USB device.
+
+</para><para>
+
+Here are some details about how to set the boot order. Remember to
+reset the boot order after Linux is installed, so that you restart
+your machine from the hard drive.
+
+</para>
+
+   <sect3 id="ctbooi">
+   <title>Changing the Boot Order on IDE Computers</title>
+
+<orderedlist>
+<listitem><para>
+
+As your computer starts, press the keys to enter the BIOS
+utility. Often, it is the <keycap>Delete</keycap> key. However,
+consult the hardware documentation for the exact keystrokes.
+
+</para></listitem>
+<listitem><para>
+
+Find the boot sequence in the setup utility. Its location depends on
+your BIOS, but you are looking for a field that lists drives.
+
+</para><para>
+
+
+Common entries on IDE machines are C, A, cdrom or A, C, cdrom.
+
+</para><para>
+
+
+C is the hard drive, and A is the floppy drive.
+
+</para></listitem>
+<listitem><para>
+
+Change the boot sequence setting so that the CD-ROM or the
+floppy is first. Usually, the <keycap>Page Up</keycap> or
+<keycap>Page Down</keycap> keys cycle
+through the possible choices.
+
+</para></listitem>
+<listitem><para>
+
+Save your changes. Instructions on the screen tell you how to
+save the changes on your computer.
+
+</para></listitem>
+</orderedlist>
+   </sect3>
+
+   <sect3 id="ctboos">
+   <title>Changing the Boot Order on SCSI Computers</title>
+<para>
+
+<orderedlist>
+<listitem><para>
+
+As your computer starts, press the keys to enter the SCSI setup
+utility.
+
+</para><para>
+
+You can start the SCSI setup utility after the memory check and
+the message about how to start the BIOS utility displays when you
+start your computer.
+
+</para><para>
+
+The keystrokes you need depend on the utility. Often, it is
+<keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>.
+However, consult your hardware documentation for the
+exact keystrokes.
+
+</para></listitem>
+<listitem><para>
+
+Find the utility for changing the boot order.
+
+</para></listitem>
+<listitem><para>
+
+Set the utility so that the SCSI ID of the CD drive is first on
+the list.
+
+</para></listitem>
+<listitem><para>
+
+Save your changes. Instructions on the screen tell you how to
+save the changes on your computer. Often, you must press
+<keycap>F10</keycap>.
+
+</para></listitem>
+</orderedlist>
+
+</para>
+   </sect3>
+  </sect2>
+
+  <sect2 arch="i386">
+  <title>Miscellaneous BIOS Settings</title>
+
+   <sect3 id="cd-settings"><title>CD-ROM Settings</title>
+<para>
+
+Some BIOS systems (such as Award BIOS) allow you to automatically set
+the CD speed.  You should avoid that, and instead set it to, say, the
+lowest speed.  If you get <userinput>seek failed</userinput> error
+messages, this may be your problem.
+
+</para>
+   </sect3>
+
+   <sect3><title>Extended vs. Expanded Memory</title>
+<para>
+
+If your system provides both ex<emphasis>ten</emphasis>ded and
+ex<emphasis>pan</emphasis>ded memory, set it so that there is as much
+extended and as little expanded memory as possible. Linux requires
+extended memory and cannot use expanded memory.
+
+</para>
+   </sect3>
+
+   <sect3><title>Virus Protection</title>
+<para>
+
+Disable any virus-warning features your BIOS may provide. If you have
+a virus-protection board or other special hardware, make sure it is
+disabled or physically removed while running GNU/Linux. These aren't
+compatible with GNU/Linux; moreover, due to the file system
+permissions and protected memory of the Linux kernel, viruses are
+almost unheard of<footnote>
+<para>
+
+After installation you can enable Boot Sector protection if you
+want. This offers no additional security in Linux but if you also run
+Windows it may prevent a catastrophe. There is no need to tamper with
+the Master Boot Record (MBR) after the boot manager has been set up.
+
+</para>
+</footnote>.
+
+</para>
+   </sect3>
+
+   <sect3><title>Shadow RAM</title>
+<para>
+
+Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS
+caching. You may see settings for <quote>Video BIOS Shadow</quote>,
+<quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis>
+all shadow RAM.  Shadow
+RAM is used to accelerate access to the ROMs on your motherboard and
+on some of the controller cards. Linux does not use these ROMs once it
+has booted because it provides its own faster 32-bit software in place
+of the 16-bit programs in the ROMs. Disabling the shadow RAM may make
+some of it available for programs to use as normal memory.  Leaving
+the shadow RAM enabled may interfere with Linux access to hardware
+devices.
+
+</para>
+   </sect3>
+
+   <sect3><title>Memory Hole</title>
+<para>
+
+If your BIOS offers something like <quote>15&ndash;16 MB Memory
+Hole</quote>, please disable that. Linux expects to find memory there if
+you have that much RAM.
+
+</para><para>
+
+We have a report of an Intel Endeavor motherboard on which there is an
+option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>.
+This had two settings: <quote>Disabled</quote> and <quote>1
+Megabyte</quote>. Set it to <quote>1 Megabyte</quote>.
+When disabled, the installation floppy was not read correctly, and the
+system eventually crashed. At this writing we don't understand what's
+going on with this particular device &mdash; it just worked with that
+setting and not without it.
+
+</para>
+   </sect3>
+
+<!-- no other platforms other than x86 provide this sort of thing, AFAIK -->
+
+   <sect3><title>Advanced Power Management</title>
+<para>
+
+If your motherboard provides Advanced Power Management (APM),
+configure it so that power management is controlled by APM. Disable
+the doze, standby, suspend, nap, and sleep modes, and disable the hard
+disk's power-down timer.  Linux can take over control of these modes,
+and can do a better job of power-management than the BIOS.
+
+</para>
+   </sect3>
+  </sect2>
diff --git a/nl/preparing/bios-setup/m68k.xml b/nl/preparing/bios-setup/m68k.xml
new file mode 100644
index 000000000..e68cb35d7
--- /dev/null
+++ b/nl/preparing/bios-setup/m68k.xml
@@ -0,0 +1,23 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28672 untranslated -->
+
+
+  <sect2 arch="m68k" id="firmware-revs">
+  <title>Firmware Revisions and Existing OS Setup</title>
+
+<para>
+
+&arch-title; machines are generally self-configuring and do not require
+firmware configuration.  However, you should make sure that you have
+the appropriate ROM and system patches.  On the Macintosh, MacOS
+version >= 7.1 is recommended because version 7.0.1 contains a bug in
+the video drivers preventing the boot loader from deactivating the
+video interrupts, resulting in a boot hang.  On the BVM VMEbus systems
+you should make sure you are using BVMBug revision G or higher boot ROMs.
+The BVMBug boot ROMs do not come as standard on the BVM systems but are
+available from BVM on request free of charge.
+
+</para>
+
+  </sect2>
+
diff --git a/nl/preparing/bios-setup/powerpc.xml b/nl/preparing/bios-setup/powerpc.xml
new file mode 100644
index 000000000..2368a0853
--- /dev/null
+++ b/nl/preparing/bios-setup/powerpc.xml
@@ -0,0 +1,52 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28672 untranslated -->
+
+
+  <sect2 arch="powerpc" id="invoking-openfirmware">
+  <title>Invoking OpenFirmware</title>
+<para>
+
+There is normally no need to set up the BIOS (called OpenFirmware) on
+&arch-title; systems. PReP and CHRP are equipped with OpenFirmware,
+but unfortunately, the means you use to invoke it vary from
+manufacturer to manufacturer.  You'll have to consult the hardware
+documentation which came with your machine.
+
+</para><para>
+
+On &arch-title; Macintoshes, you invoke OpenFirmware with
+<keycombo><keycap>Command</keycap> <keycap>option</keycap>
+<keycap>O</keycap> <keycap>F</keycap></keycombo> while booting.  Generally it
+will check for these keystrokes after the chime, but the exact timing
+varies from model to model.  See
+<ulink url="&url-netbsd-powerpc-faq;"></ulink> for more hints.
+
+</para><para>
+
+The OpenFirmware prompt looks like this:
+
+<informalexample><screen>
+ok
+0 &gt;
+</screen></informalexample>
+
+Note that on older model &arch-title; Macs, the default and sometimes
+hardwired I/O for OpenFirmware user interaction is through the serial
+(modem) port. If you invoke OpenFirmware on one of these machines, you
+will just see a black screen. In that case, a terminal program running
+on another computer, connected to the modem port, is needed to
+interact with OpenFirmware.
+
+</para><para>
+
+The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1
+and 2.4, is broken. These machines will most likely not be able to
+boot from the hard drive unless the firmware is patched. A firmware
+patch is included in the <application>System Disk 2.3.1</application>
+utility, available from Apple at
+<ulink url="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"></ulink>.
+After unpacking the utility in MacOS, and launching it, select the
+Save button to have the firmware patches installed to nvram.
+
+</para>
+  </sect2>
diff --git a/nl/preparing/bios-setup/s390.xml b/nl/preparing/bios-setup/s390.xml
new file mode 100644
index 000000000..b2ed18855
--- /dev/null
+++ b/nl/preparing/bios-setup/s390.xml
@@ -0,0 +1,106 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28672 untranslated -->
+
+
+  <sect2 arch="s390"><title>BIOS Setup</title>
+<para>
+
+In order to install &debian; on a &arch-title; or zSeries
+machine you have first boot a kernel into the system.  The boot
+mechanism of this platform is inherently different to other ones,
+especially from PC-like systems: there are no floppy devices available
+at all. You will notice another big difference while you work with
+this platform: most (if not all) of the time you will work remote,
+with the help of some client session software like telnet, or a
+browser.  This is due to that special system architecture where the
+3215/3270 console is line-based instead of character-based.
+
+</para><para>
+
+Linux on this platform runs either natively on the bare machine, in a
+so-called LPAR (Logical Partition) or in a virtual machine supplied by
+the VM system.  You can use a boot tape on all of those systems; you
+may use some other boot media, too, but those may not be generally
+available.  For example, you can use the virtual card reader of a
+virtual machine, or boot from the HMC (Hardware Management Console) of
+an LPAR if the HMC and this option is available for you.
+
+</para><para>
+
+Before you actually perform an installation, you have to go over some
+design and preparation steps.  IBM has made documentation available
+about the whole process, e.g. how to prepare an installation medium
+and how actually boot from that medium.  Duplicating that information
+here is neither possible nor necessary.  However, we will describe
+here which kind of Debian-specific data is needed and where do you
+find them.  Based on both sources of information you have to prepare
+your machine and the installation medium and to perform a boot from
+it.  When you see the welcome message in your client session join this
+document again for the Debian-specific installation steps.
+
+</para>
+  </sect2>
+
+  <sect2 arch="s390">
+  <title>Native and LPAR installations</title>
+<para>
+
+Please refer to chapter 5 of the
+<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf">
+Linux for &arch-title;</ulink>
+Redbook and chapter 3.2 of the
+<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf">
+Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink>
+Redbook on how to set up an LPAR for Linux.
+
+</para>
+  </sect2>
+
+  <sect2 arch="s390">
+  <title>Installation as a VM guest</title>
+
+<para>
+
+Please refer to chapter 6 of the
+<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf">
+Linux for &arch-title;</ulink>
+Redbook and chapter 3.1 of the
+<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf">
+Linux for IBM eServer zSeries and  &arch-title;: Distributions</ulink>
+Redbook on how to set up a VM guest for running Linux.
+
+</para><para>
+
+You need to copy all the files from the <filename>generic</filename>
+sub-directory to your CMS disk. Be sure to transfer
+<filename>kernel.debian</filename> and
+<filename>initrd.debian</filename> in binary mode with a fixed record
+length of 80 characters.
+
+</para>
+  </sect2>
+
+  <sect2 arch="s390">
+  <title>Setting up an installation server</title>
+
+<para>
+
+If you don't have a connection to the Internet (either directly or via
+a web proxy) you need to create a local installation server that can
+be accessed from your S/390. This server keeps all the packages
+you want to install and must make them available using NFS, HTTP or
+FTP.
+
+</para><para>
+
+The installation server needs to copy the exact directory structure
+from any &debian; mirror but of only the s390 and
+architecture-independent files are required. You can also copy the
+contents of all installation CDs into such a directory tree.
+
+</para><para condition="FIXME">
+
+<emphasis>FIXME: more information needed &mdash; from a Redbook?</emphasis>
+
+</para>
+  </sect2>
diff --git a/nl/preparing/bios-setup/sparc.xml b/nl/preparing/bios-setup/sparc.xml
new file mode 100644
index 000000000..591ea1415
--- /dev/null
+++ b/nl/preparing/bios-setup/sparc.xml
@@ -0,0 +1,103 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 28997 untranslated -->
+
+
+  <sect2 arch="sparc" id="invoking-openboot"><title>Invoking OpenBoot</title>
+
+<para>
+
+OpenBoot provides the basic functions needed to boot the &arch-title;
+architecture.  This is rather similar in function to the BIOS in the
+x86 architecture, although much nicer.  The Sun boot PROMs have a
+built-in forth interpreter which lets you do quite a number of things
+with your machine, such as diagnostics, simple scripts, etc.
+
+</para><para>
+
+To get to the boot prompt you need to hold down the
+<keycap>Stop</keycap> key (on older type 4 keyboards, use the
+<keycap>L1</keycap> key, if you have a PC keyboard adapter, use
+the <keycap>Break</keycap> key) and press the
+<keycap>A</keycap> key. The boot PROM will give you a prompt,
+either <userinput>ok</userinput> or <userinput>&gt;</userinput>. It is
+preferred to have the <userinput>ok</userinput> prompt. So if you get
+the old style prompt, hit the <keycap>n</keycap> key to get the new
+style prompt.
+
+</para><para>
+
+If you are using a serial console, send a break to the machine. With Minicom,
+use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type
+<userinput>%~break</userinput>. Consult the documentation of your terminal
+emulator if you are using a different program.
+
+</para>
+  </sect2>
+
+  <sect2 arch="sparc" id="boot-dev-select-sun">
+  <title>Boot Device Selection</title>
+
+<para>
+
+You can use OpenBoot to boot from specific devices, and also to change
+your default boot device.  However, you need to know some details
+about how OpenBoot names devices; it's much different from Linux
+device naming, described in <xref linkend="device-names"/>.
+Also, the command will vary a bit, depending on what version of
+OpenBoot you have.  More information about OpenBoot can be found in
+the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
+
+</para><para>
+
+Typically, with newer revisions, you can use OpenBoot device such as
+<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>,
+<quote>disk</quote>, or <quote>disk2</quote>.  These have the obvious
+meanings; the <quote>net</quote> device is for booting from the network.
+Additionally, the device name can specify a particular partition of a disk,
+such as <quote>disk2:a</quote> to boot disk2, first partition.  Full
+OpenBoot device names have the form
+
+<informalexample>
+<screen>
+<replaceable>driver-name</replaceable>@
+<replaceable>unit-address</replaceable>:
+<replaceable>device-arguments</replaceable>
+</screen></informalexample>.
+
+In older revisions of OpenBoot, device naming is a bit different: the
+floppy device is called <quote>/fd</quote>, and SCSI disk devices are of
+the form <quote>sd(<replaceable>controller</replaceable>,
+<replaceable>disk-target-id</replaceable>,
+<replaceable>disk-lun</replaceable>)</quote>.  The command
+<userinput>show-devs</userinput> in newer OpenBoot revisions is useful
+for viewing the currently configured devices.  For full information,
+whatever your revision, see the
+<ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
+
+</para><para>
+
+To boot from a specific device, use the command <userinput>boot
+<replaceable>device</replaceable></userinput>.  You can set this
+behavior as the default using the <userinput>setenv</userinput>
+command.  However, the name of the variable to set changed between
+OpenBoot revisions.  In OpenBoot 1.x, use the command
+<userinput>setenv boot-from
+<replaceable>device</replaceable></userinput>.  In later revisions of
+OpenBoot, use the command <userinput>setenv boot-device
+<replaceable>device</replaceable></userinput>. Note, this is also
+configurable using the <command>eeprom</command> command on Solaris,
+or modifying the appropriate files in
+<filename>/proc/openprom/options/</filename>, for example under Linux:
+
+<informalexample><screen>
+# echo disk1:1 &gt; /proc/openprom/options/boot-device
+</screen></informalexample>
+
+and under Solaris:
+
+<informalexample><screen>
+eeprom boot-device=disk1:1
+</screen></informalexample>
+
+</para>
+  </sect2>