- Switch Finnish from XML-based to PO-based translation

- Correct placement of changelog entries from Joey

6 files changed, 0 insertions, 2593 deletions

diff --git a/fi/appendix/chroot-install.xml b/fi/appendix/chroot-install.xml
deleted file mode 100644
index cd72a3a88..000000000
--- a/fi/appendix/chroot-install.xml
+++ /dev/null
@@ -1,460 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 36758 untranslated -->
-
- <sect1 id="linux-upgrade">
- <title>Installing &debian; from a Unix/Linux System</title>
-
-<para>
-
-This section explains how to install &debian; from an existing
-Unix or Linux system, without using the menu-driven installer as
-explained in the rest of the manual. This <quote>cross-install</quote>
-HOWTO has been requested by users switching to &debian; from
-Red Hat, Mandrake, and SUSE. In this section some familiarity with
-entering *nix commands and navigating the file system is assumed. In
-this section, <prompt>$</prompt> symbolizes a command to be entered in
-the user's current system, while <prompt>#</prompt> refers to a
-command entered in the Debian chroot.
-
-</para><para>
-
-Once you've got the new Debian system configured to your preference,
-you can migrate your existing user data (if any) to it, and keep on
-rolling. This is therefore a <quote>zero downtime</quote> &debian;
-install. It's also a clever way for dealing with hardware that
-otherwise doesn't play friendly with various boot or installation
-media.
-
-</para>
-
-  <sect2>
-  <title>Getting Started</title>
-<para>
-
-With your current *nix partitioning tools, repartition the hard
-drive as needed, creating at least one filesystem plus swap. You
-need at least 150MB of space available for a console only install,
-or at least 300MB if you plan to install X.
-
-</para><para>
-
-To create file systems on your partitions. For example, to create an
-ext3 file system on partition <filename>/dev/hda6</filename> (that's
-our example root partition):
-
-<informalexample><screen>
-# mke2fs -j /dev/hda6
-</screen></informalexample>
-
-To create an ext2 file system instead, omit <userinput>-j</userinput>.
-
-</para><para>
-
-Initialize and activate swap (substitute the partition number for
-your intended Debian swap partition):
-
-<informalexample><screen>
-# mkswap /dev/hda5
-# sync; sync; sync
-# swapon /dev/hda5
-</screen></informalexample>
-
-Mount one partition as <filename>/mnt/debinst</filename> (the
-installation point, to be the root (<filename>/</filename>) filesystem
-on your new system). The mount point name is strictly arbitrary, it is
-referenced later below.
-
-<informalexample><screen>
-# mkdir /mnt/debinst
-# mount /dev/hda6 /mnt/debinst
-</screen></informalexample>
-
-</para>
-<note><para>
-
-If you want to have parts of the filesystem (e.g. /usr) mounted on
-separate partitions, you will need to create and mount these directories
-manually before proceding with the next stage.
-
-</para></note>
-  </sect2>
-
-  <sect2>
-  <title>Install <command>debootstrap</command></title>
-<para>
-
-The tool that the Debian installer uses, which is recognized as the
-official way to install a Debian base system, is
-<command>debootstrap</command>. It uses <command>wget</command> and
-<command>ar</command>, but otherwise depends only on
-<classname>/bin/sh</classname> and basic Unix/Linux tools<footnote>
-
-<para>
-
-These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>.
-
-</para>
-
-</footnote>. Install <command>wget</command> and
-<command>ar</command> if they aren't already on your current system,
-then download and install <command>debootstrap</command>.
-
-</para>
-
-<!-- The files linked to here are from 2004 and thus currently not usable
-<para>
-
-If you have an rpm-based system, you can use alien to convert the
-.deb into .rpm, or download an rpm-ized version at
-<ulink url="http://people.debian.org/~blade/install/debootstrap"></ulink>
-
-</para>
--->
-
-<para>
-
-Or, you can use the following procedure to install it
-manually. Make a work folder for extracting the .deb into:
-
-<informalexample><screen>
-# mkdir work
-# cd work
-</screen></informalexample>
-
-The <command>debootstrap</command> binary is located in the Debian
-archive (be sure to select the proper file for your
-architecture). Download the <command>debootstrap</command> .deb from
-the <ulink url="http://ftp.debian.org/debian/pool/main/d/debootstrap/">
-pool</ulink>, copy the package to the work folder, and extract the
-binary files from it. You will need to have root privileges to install
-the binaries.
-
-<informalexample><screen>
-# ar -x debootstrap_0.X.X_arch.deb
-# cd /
-# zcat /full-path-to-work/work/data.tar.gz | tar xv
-</screen></informalexample>
-
-</para><para>
-
-Note that running <command>debootstrap</command> may require you to have
-a minimal version of <classname>glibc</classname> installed (currently
-GLIBC_2.3). <command>debootstrap</command> itself is a shell script, but
-it calls various utilities that require <classname>glibc</classname>.
-
-</para>
-  </sect2>
-
-  <sect2>
-  <title>Run <command>debootstrap</command></title>
-<para>
-
-<command>debootstrap</command> can download the needed files directly
-from the archive when you run it. You can substitute any Debian
-archive mirror for <userinput>http.us.debian.org/debian</userinput> in
-the command example below, preferably a mirror close to you
-network-wise. Mirrors are listed at
-<ulink url="http://www.debian.org/misc/README.mirrors"></ulink>.
-
-</para><para>
-
-If you have a &releasename; &debian; CD mounted at
-<filename>/cdrom</filename>, you could substitute a file URL instead
-of the http URL: <userinput>file:/cdrom/debian/</userinput>
-
-</para><para>
-
-Substitute one of the following for <replaceable>ARCH</replaceable>
-in the <command>debootstrap</command> command:
-
-<userinput>alpha</userinput>,
-<userinput>arm</userinput>,
-<userinput>hppa</userinput>,
-<userinput>i386</userinput>,
-<userinput>ia64</userinput>,
-<userinput>m68k</userinput>,
-<userinput>mips</userinput>,
-<userinput>mipsel</userinput>,
-<userinput>powerpc</userinput>,
-<userinput>s390</userinput>, or
-<userinput>sparc</userinput>.
-
-<informalexample><screen>
-# /usr/sbin/debootstrap --arch ARCH &releasename; \
-     /mnt/debinst http://http.us.debian.org/debian
-</screen></informalexample>
-
-</para>
-  </sect2>
-
-  <sect2>
-  <title>Configure The Base System</title>
-<para>
-
-Now you've got a real Debian system, though rather lean, on disk.
-<command>Chroot</command> into it:
-
-<informalexample><screen>
-# LANG= chroot /mnt/debinst /bin/bash
-</screen></informalexample>
-
-</para>
-
-   <sect3>
-   <title>Mount Partitions</title>
-<para>
-
-You need to create <filename>/etc/fstab</filename>.
-
-<informalexample><screen>
-# editor /etc/fstab
-</screen></informalexample>
-
-Here is a sample you can modify to suit:
-
-<informalexample><screen>
-# /etc/fstab: static file system information.
-#
-# file system    mount point   type    options                  dump pass
-/dev/XXX         /             ext3    defaults                 0    1
-/dev/XXX         /boot         ext3    ro,nosuid,nodev          0    2
-
-/dev/XXX         none          swap    sw                       0    0
-proc             /proc         proc    defaults                 0    0
-
-/dev/fd0         /mnt/floppy   auto    noauto,rw,sync,user,exec 0    0
-/dev/cdrom       /mnt/cdrom    iso9660 noauto,ro,user,exec      0    0
-
-/dev/XXX         /tmp          ext3    rw,nosuid,nodev          0    2
-/dev/XXX         /var          ext3    rw,nosuid,nodev          0    2
-/dev/XXX         /usr          ext3    rw,nodev                 0    2
-/dev/XXX         /home         ext3    rw,nosuid,nodev          0    2
-</screen></informalexample>
-
-Use <userinput>mount -a</userinput> to mount all the file systems you
-have specified in your <filename>/etc/fstab</filename>, or to mount
-file systems individually use:
-
-<informalexample><screen>
-# mount /path   # e.g.: mount /usr
-</screen></informalexample>
-
-You can mount the proc file system multiple times and to arbitrary
-locations, though <filename>/proc</filename> is customary. If you didn't use
-<userinput>mount -a</userinput>, be sure to mount proc before continuing:
-
-<informalexample><screen>
-# mount -t proc proc /proc
-</screen></informalexample>
-
-</para><para>
-
-The command <userinput>ls /proc</userinput> should now show a non-empty
-directory. Should this fail, you may be able to mount proc from outside
-the chroot:
-
-<informalexample><screen>
-# mount -t proc proc /mnt/debinst/proc
-</screen></informalexample>
-
-</para>
-   </sect3>
-
-   <sect3>
-   <title>Configure Keyboard</title>
-<para>
-
-To configure your keyboard:
-
-<informalexample><screen>
-# dpkg-reconfigure console-data
-</screen></informalexample>
-
-</para><para>
-
-Note that the keyboard cannot be set while in the chroot, but will be
-configured for the next reboot.
-
-</para>
-   </sect3>
-
-   <sect3>
-   <title>Configure Networking</title>
-<para>
-
-To configure networking, edit
-<filename>/etc/network/interfaces</filename>,
-<filename>/etc/resolv.conf</filename>,
-<filename>/etc/hostname</filename> and
-<filename>/etc/hosts</filename>.
-
-<informalexample><screen>
-# editor /etc/network/interfaces
-</screen></informalexample>
-
-Here are some simple examples from
-<filename>/usr/share/doc/ifupdown/examples</filename>:
-
-<informalexample><screen>
-######################################################################
-# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
-# See the interfaces(5) manpage for information on what options are
-# available.
-######################################################################
-
-# We always want the loopback interface.
-#
-auto lo
-iface lo inet loopback
-
-# To use dhcp:
-#
-# auto eth0
-# iface eth0 inet dhcp
-
-# An example static IP setup: (broadcast and gateway are optional)
-#
-# auto eth0
-# iface eth0 inet static
-#     address 192.168.0.42
-#     network 192.168.0.0
-#     netmask 255.255.255.0
-#     broadcast 192.168.0.255
-#     gateway 192.168.0.1
-</screen></informalexample>
-
-Enter your nameserver(s) and search directives in
-<filename>/etc/resolv.conf</filename>:
-
-<informalexample><screen>
-# editor /etc/resolv.conf
-</screen></informalexample>
-
-A simple <filename>/etc/resolv.conf</filename>:
-
-<informalexample><screen>
-search hqdom.local\000
-nameserver 10.1.1.36
-nameserver 192.168.9.100
-</screen></informalexample>
-
-Enter your system's host name (2 to 63 characters):
-
-<informalexample><screen>
-# echo DebianHostName &gt; /etc/hostname
-</screen></informalexample>
-
-If you have multiple network cards, you should arrange the names of
-driver modules in the <filename>/etc/modules</filename> file into the
-desired order. Then during boot, each card will be associated with the
-interface name (eth0, eth1, etc.) that you expect.
-
-</para>
-   </sect3>
-
-   <sect3>
-   <title>Configure Locales</title>
-<para>
-
-To configure your locale settings to use a language other than
-English, install the locales support package and configure it:
-
-<informalexample><screen>
-# apt-get install locales
-# dpkg-reconfigure locales
-</screen></informalexample>
-
-NOTE: Apt must be configured beforehand by creating a sources.list and
-running apt-get update.
-Before using locales with character sets other than ASCII or latin1,
-please consult the appropriate localization HOWTO.
-
-</para>
-   </sect3>
-  </sect2>
-
-  <sect2>
-  <title>Install a Kernel</title>
-<para>
-
-If you intend to boot this system, you probably want a Linux kernel
-and a boot loader. Identify available pre-packaged kernels with
-
-<informalexample><screen>
-# apt-cache search <phrase condition="classic-kpkg">kernel</phrase><phrase condition="common-kpkg">linux</phrase>-image
-</screen></informalexample>
-
-Then install your choice using its package name.
-
-<informalexample><screen>
-# apt-get install <phrase condition="classic-kpkg">kernel</phrase><phrase condition="common-kpkg">linux</phrase>-image-<replaceable>&kernelversion;-arch-etc</replaceable>
-</screen></informalexample>
-
-</para>
-  </sect2>
-
-  <sect2>
-<title>Set up the Boot Loader</title>
-<para>
-
-To make your &debian; system bootable, set up your boot loader to load
-the installed kernel with your new root partition. Note that debootstrap
-does not install a boot loader, though you can use apt-get inside your
-Debian chroot to do so.
-
-</para><para arch="i386">
-
-Check <userinput>info grub</userinput> or <userinput>man
-lilo.conf</userinput> for instructions on setting up the
-bootloader.  If you are keeping the system you used to install Debian, just
-add an entry for the Debian install to your existing grub
-<filename>menu.lst</filename> or <filename>lilo.conf</filename>.  For
-<filename>lilo.conf</filename>, you could also copy it to the new system and
-edit it there. After you are done editing, call lilo (remember it will use
-<filename>lilo.conf</filename> relative to the system you call it from).
-
-</para><para arch="i386">
-
-Here is a basic <filename>/etc/lilo.conf</filename> as an example:
-
-<informalexample><screen>
-boot=/dev/hda6
-root=/dev/hda6
-install=menu
-delay=20
-lba32
-image=/vmlinuz
-label=Debian
-</screen></informalexample>
-
-</para><para arch="powerpc">
-
-Check <userinput>man yaboot.conf</userinput> for instructions on
-setting up the bootloader.  If you are keeping the system you used to
-install Debian, just add an entry for the Debian install to your
-existing <filename>yaboot.conf</filename>.  You could also copy it to
-the new system and
-edit it there. After you are done editing, call ybin (remember it will
-use <filename>yaboot.conf</filename> relative to the system you call it from).
-
-</para><para arch="powerpc">
-
-Here is a basic <filename>/etc/yaboot.conf</filename> as an example:
-
-<informalexample><screen>
-boot=/dev/hda2
-device=hd:
-partition=6
-root=/dev/hda6
-magicboot=/usr/lib/yaboot/ofboot
-timeout=50
-image=/vmlinux
-label=Debian
-</screen></informalexample>
-
-On some machines, you may need to use <userinput>ide0:</userinput>
-instead of <userinput>hd:</userinput>.
-
-</para>
-  </sect2>
- </sect1>
diff --git a/fi/appendix/files.xml b/fi/appendix/files.xml
deleted file mode 100644
index ad7332bf8..000000000
--- a/fi/appendix/files.xml
+++ /dev/null
@@ -1,298 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 33887 untranslated -->
-
-
- <sect1 id="linuxdevices"><title>Linux Devices</title>
-<para>
-
-In Linux you have various special files in
-<filename>/dev</filename>. These files are called device files. In
-the Unix world accessing hardware is different.  There you have a
-special file which actually runs a driver which in turn accesses the
-hardware. The device file is an interface to the actual system
-component. Files under <filename>/dev</filename> also behave
-differently than ordinary files. Below are the most important device
-files listed.
-
-</para><para>
-
-<informaltable><tgroup cols="2"><tbody>
-<row>
-  <entry><filename>fd0</filename></entry>
-  <entry>First Floppy Drive</entry>
-</row><row>
-  <entry><filename>fd1</filename></entry>
-  <entry>Second Floppy Drive</entry>
-</row>
-</tbody></tgroup></informaltable>
-
-<informaltable><tgroup cols="2"><tbody>
-<row>
-  <entry><filename>hda</filename></entry>
-  <entry>IDE Hard disk / CD-ROM on the first IDE port (Master)</entry>
-</row><row>
-  <entry><filename>hdb</filename></entry>
-  <entry>IDE Hard disk / CD-ROM on the first IDE port (Slave)</entry>
-</row><row>
-  <entry><filename>hdc</filename></entry>
-  <entry>IDE Hard disk / CD-ROM on the second IDE port (Master)</entry>
-</row><row>
-  <entry><filename>hdd</filename></entry>
-  <entry>IDE Hard disk / CD-ROM on the second IDE port (Slave)</entry>
-</row><row>
-  <entry><filename>hda1</filename></entry>
-  <entry>First partition of the first IDE hard disk</entry>
-</row><row>
-  <entry><filename>hdd15</filename></entry>
-  <entry>Fifteenth partition of the fourth IDE hard disk</entry>
-</row>
-</tbody></tgroup></informaltable>
-
-<informaltable><tgroup cols="2"><tbody>
-<row>
-  <entry><filename>sda</filename></entry>
-  <entry>SCSI Hard disk with lowest SCSI ID (e.g. 0)</entry>
-</row><row>
-  <entry><filename>sdb</filename></entry>
-  <entry>SCSI Hard disk with next higher SCSI ID (e.g. 1)</entry>
-</row><row>
-  <entry><filename>sdc</filename></entry>
-  <entry>SCSI Hard disk with next higher SCSI ID (e.g. 2)</entry>
-</row><row>
-  <entry><filename>sda1</filename></entry>
-  <entry>First partition of the first SCSI hard disk</entry>
-</row><row>
-  <entry><filename>sdd10</filename></entry>
-  <entry>Tenth partition of the fourth SCSI hard disk</entry>
-</row>
-</tbody></tgroup></informaltable>
-
-<informaltable><tgroup cols="2"><tbody>
-<row>
-  <entry><filename>sr0</filename></entry>
-  <entry>SCSI CD-ROM with the lowest SCSI ID</entry>
-</row><row>
-  <entry><filename>sr1</filename></entry>
-  <entry>SCSI CD-ROM with the next higher SCSI ID</entry>
-</row>
-</tbody></tgroup></informaltable>
-
-<informaltable><tgroup cols="2"><tbody>
-<row>
-  <entry><filename>ttyS0</filename></entry>
-  <entry>Serial port 0, COM1 under MS-DOS</entry>
-</row><row>
-  <entry><filename>ttyS1</filename></entry>
-  <entry>Serial port 1, COM2 under MS-DOS</entry>
-</row><row>
-  <entry><filename>psaux</filename></entry>
-  <entry>PS/2 mouse device</entry>
-</row><row>
-  <entry><filename>gpmdata</filename></entry>
-  <entry>Pseudo device, repeater data from GPM (mouse) daemon</entry>
-</row>
-</tbody></tgroup></informaltable>
-
-<informaltable><tgroup cols="2"><tbody>
-<row>
-  <entry><filename>cdrom</filename></entry>
-  <entry>Symbolic link to the CD-ROM drive</entry>
-</row><row>
-  <entry><filename>mouse</filename></entry>
-  <entry>Symbolic link to the mouse device file</entry>
-</row>
-</tbody></tgroup></informaltable>
-
-<informaltable><tgroup cols="2"><tbody>
-<row>
-  <entry><filename>null</filename></entry>
-  <entry>Everything pointed to this device will disappear</entry>
-</row><row>
-  <entry><filename>zero</filename></entry>
-  <entry>One can endlessly read zeros out of this device</entry>
-</row>
-</tbody></tgroup></informaltable>
-
-</para>
-
-  <sect2>
-<title>Setting Up Your Mouse</title>
-
-<para>
-
-The mouse can be used in both the Linux console (with gpm) and the X window
-environment. The two uses can be made compatible if the gpm repeater is used
-to allow the signal to flow to the X server as shown:
-
-<informalexample><screen>
-mouse =&gt; /dev/psaux  =&gt; gpm =&gt; /dev/gpmdata -&gt; /dev/mouse =&gt; X
-         /dev/ttyS0             (repeater)        (symlink)
-         /dev/ttyS1
-</screen></informalexample>
-
-Set the repeater protocol to be raw (in <filename>/etc/gpm.conf</filename>) while
-setting X to the original mouse protocol in <filename>/etc/X11/XF86Config</filename>
-or <filename>/etc/X11/XF86Config-4</filename>.
-
-</para><para>
-
-This approach to use gpm even in X has advantages when the mouse is
-unplugged inadvertently.  Simply restarting gpm with
-
-<informalexample><screen>
-# /etc/init.d/gpm restart
-</screen></informalexample>
-
-will re-connect the mouse in software without restarting X.
-
-</para><para>
-
-If gpm is disabled or not installed with some reason, make sure to set X to
-read directly from the mouse device such as /dev/psaux. For details, refer
-to the 3-Button Mouse mini-Howto at
-<filename>/usr/share/doc/HOWTO/en-txt/mini/3-Button-Mouse.gz</filename>,
-<userinput>man gpm</userinput>,
-<filename>/usr/share/doc/gpm/FAQ.gz</filename>, and
-<ulink url="&url-xorg;current/doc/html/mouse.html">README.mouse</ulink>.
-
-</para><para arch="powerpc">
-
-For PowerPC, in <filename>/etc/X11/XF86Config</filename> or
-<filename>/etc/X11/XF86Config-4</filename>, set the mouse device to
-<userinput>"/dev/input/mice"</userinput>.
-
-</para><para arch="powerpc">
-
-Modern kernels give you the capability to emulate a three-button mouse
-when your mouse only has one button. Just add the following lines to
-<filename>/etc/sysctl.conf</filename> file.
-
-<informalexample><screen>
-# 3-button mouse emulation
-# turn on emulation
-/dev/mac_hid/mouse_button_emulation = 1
-# Send middle mouse button signal with the F11 key
-/dev/mac_hid/mouse_button2_keycode = 87
-# Send right mouse button signal with the F12 key
-/dev/mac_hid/mouse_button3_keycode = 88
-# For different keys, use showkey to tell you what the code is.
-</screen></informalexample>
-
-</para>
-  </sect2>
- </sect1>
-
- <sect1 id="tasksel-size-list">
- <title>Disk Space Needed for Tasks</title>
-
-<!-- Note for d-i and manual maintainers
- Sizes of tasks should be determined by running "tasksel new" on a system
- that been fully installed without selecting any tasks. By selecting a
- task together with the "manual selection" option, aptitude will be started
- and show the sizes for the task. After deselecting the packages to be
- installed, quit aptitude and repeat for other tasks.
- Space requirements need to be determined from tasksel as tasksel will not
- install recommended packages while selecting a task from aptitude will.
--->
-
-<para>
-
-The base installation for i386 using the default 2.4 kernel,
-including all standard packages, requires 573MB of disk space.
-
-</para><para>
-
-The following table lists sizes reported by aptitude for the tasks listed
-in tasksel. Note that some tasks have overlapping constituents, so the
-total installed size for two tasks together may be less than the total
-obtained by adding up the numbers.
-
-</para><para>
-
-Note that you will need to add the sizes listed in the table to the size
-of the base installation when determining the size of partitions.
-Most of the size listed as <quote>Installed size</quote> will end up in
-<filename>/usr</filename>; the size listed as <quote>Download size</quote>
-is (temporarily) required in <filename>/var</filename>.
-
-</para><para>
-
-<informaltable><tgroup cols="4">
-<thead>
-<row>
-  <entry>Task</entry>
-  <entry>Installed size (MB)</entry>
-  <entry>Download size (MB)</entry>
-  <entry>Space needed to install (MB)</entry>
-</row>
-</thead>
-
-<tbody>
-<row>
-  <entry>Desktop</entry>
-  <entry>1392</entry>
-  <entry>460</entry>
-  <entry>1852</entry>
-</row>
-
-<row>
-  <entry>Web server</entry>
-  <entry>36</entry>
-  <entry>12</entry>
-  <entry>48</entry>
-</row>
-
-<row>
-  <entry>Print server</entry>
-  <entry>168</entry>
-  <entry>58</entry>
-  <entry>226</entry>
-</row>
-
-<row>
-  <entry>DNS server</entry>
-  <entry>2</entry>
-  <entry>1</entry>
-  <entry>3</entry>
-</row>
-
-<row>
-  <entry>File server</entry>
-  <entry>47</entry>
-  <entry>24</entry>
-  <entry>71</entry>
-</row>
-
-<row>
-  <entry>Mail server</entry>
-  <entry>10</entry>
-  <entry>3</entry>
-  <entry>13</entry>
-</row>
-
-<row>
-  <entry>SQL database</entry>
-  <entry>66</entry>
-  <entry>21</entry>
-  <entry>87</entry>
-</row>
-
-</tbody>
-</tgroup></informaltable>
-
-<note><para>
-
-The <emphasis>Desktop</emphasis> task will install both the Gnome and KDE
-desktop environments.
-
-</para></note>
-
-</para><para>
-
-If you install in a language other than English, <command>tasksel</command>
-may automatically install a <firstterm>localization task</firstterm>, if one
-is available for your language. Space requirements differ per language;
-you should allow up to 200MB in total for download and installation.
-
-</para>
- </sect1>
diff --git a/fi/appendix/gpl.xml b/fi/appendix/gpl.xml
deleted file mode 100644
index ba5782af2..000000000
--- a/fi/appendix/gpl.xml
+++ /dev/null
@@ -1,512 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 29618 untranslated -->
-
-<appendix id="appendix-gpl"><title>GNU General Public License</title>
-
-<para>
-
-Version 2, June 1991
-
-</para><para>
-
-Copyright (C) 1989, 1991 Free Software Foundation, Inc.
-&mdash;
-51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
-</para><para>
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
-</para>
-
- <sect1><title>Preamble</title>
-<para>
-
-The licenses for most software are designed to take away your freedom
-to share and change it. By contrast, the gnu General Public License
-is intended to guarantee your freedom to share and change free
-software &mdash; to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit
-to using it. (Some other Free Software Foundation software is covered
-by the gnu Library General Public License instead.) You can apply it
-to your programs, too.
-
-</para><para>
-
-When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge
-for this service if you wish), that you receive source code or can
-get it if you want it, that you can change the software or use pieces
-of it in new free programs; and that you know you can do these
-things.
-
-</para><para>
-
-To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the
-rights. These restrictions translate to certain responsibilities for
-you if you distribute copies of the software, or if you modify it.
-
-</para><para>
-
-For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
-</para><para>
-
-We protect your rights with two steps: (1) copyright the software,
-and (2) offer you this license which gives you legal permission to
-copy, distribute and/or modify the software.
-
-</para><para>
-
-Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on,
-we want its recipients to know that what they have is not the
-original, so that any problems introduced by others will not reflect
-on the original authors' reputations.
-
-</para><para>
-
-Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making
-the program proprietary. To prevent this, we have made it clear that
-any patent must be licensed for everyone's free use or not licensed
-at all.
-
-</para><para>
-
-The precise terms and conditions for copying, distribution and
-modification follow.
-
-</para>
- </sect1>
-
- <sect1><title>GNU GENERAL PUBLIC LICENSE</title>
-<para>
-
-TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-</para>
-
-<itemizedlist><listitem><para>
-
-This License applies to any program or other work which contains a
-notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-</para><para>
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the
-Program is covered only if its contents constitute a work based on
-the Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-</para></listitem>
-<listitem><para>
-
-You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any
-warranty; and give any other recipients of the Program a copy of this
-License along with the Program.
-
-</para><para>
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a
-fee.
-
-</para></listitem>
-<listitem><para>
-
-You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-</para><para>
-
-a) You must cause the modified files to carry prominent notices
-stating that you changed the files and the date of any change.
-
-</para><para>
-
-b) You must cause any work that you distribute or publish, that in
-whole or in part contains or is derived from the Program or any part
-thereof, to be licensed as a whole at no charge to all third parties
-under the terms of this License.
-
-</para><para>
-
-c) If the modified program normally reads commands interactively when
-run, you must cause it, when started running for such interactive use
-in the most ordinary way, to print or display an announcement
-including an appropriate copyright notice and a notice that there is
-no warranty (or else, saying that you provide a warranty) and that
-users may redistribute the program under these conditions, and
-telling the user how to view a copy of this License. (Exception: if
-the Program itself is interactive but does not normally print such an
-announcement, your work based on the Program is not required to print
-an announcement.)
-
-</para><para>
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote
-it.
-
-</para><para>
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-</para><para>
-
-In addition, mere aggregation of another work not based on the
-Program with the Program (or with a work based on the Program) on a
-volume of a storage or distribution medium does not bring the other
-work under the scope of this License.
-
-</para></listitem>
-<listitem><para>
-
-You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the
-following:
-
-</para><para>
-
-a) Accompany it with the complete corresponding machine-readable
-source code, which must be distributed under the terms of Sections 1
-and 2 above on a medium customarily used for software interchange;
-or,
-
-</para><para>
-
-b) Accompany it with a written offer, valid for at least three years,
-to give any third party, for a charge no more than your cost of
-physically performing source distribution, a complete
-machine-readable copy of the corresponding source code, to be
-distributed under the terms of Sections 1 and 2 above on a medium
-customarily used for software interchange; or,
-
-</para><para>
-
-c) Accompany it with the information you received as to the offer to
-distribute corresponding source code. (This alternative is allowed
-only for noncommercial distribution and only if you received the
-program in object code or executable form with such an offer, in
-accord with Subsection b above.)
-
-</para><para>
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-</para><para>
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-</para></listitem>
-<listitem><para>
-
-You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this
-License. However, parties who have received copies, or rights, from
-you under this License will not have their licenses terminated so
-long as such parties remain in full compliance.
-
-</para></listitem>
-<listitem><para>
-
-You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-</para></listitem>
-<listitem><para>
-
-Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject
-to these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted
-herein. You are not responsible for enforcing compliance by third
-parties to this License.
-
-</para></listitem>
-<listitem><para>
-
-If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do
-not excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under
-this License and any other pertinent obligations, then as a
-consequence you may not distribute the Program at all. For example,
-if a patent license would not permit royalty-free redistribution of
-the Program by all those who receive copies directly or indirectly
-through you, then the only way you could satisfy both it and this
-License would be to refrain entirely from distribution of the
-Program.
-
-</para><para>
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended
-to apply and the section as a whole is intended to apply in other
-circumstances.
-
-</para><para>
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is
-willing to distribute software through any other system and a
-licensee cannot impose that choice.
-
-</para><para>
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-</para></listitem>
-<listitem><para>
-
-If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-</para></listitem>
-<listitem><para>
-
-The Free Software Foundation may publish revised and/or new
-versions of the General Public License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns. Each version is
-given a distinguishing version number. If the Program specifies a
-version number of this License which applies to it and "any later
-version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number
-of this License, you may choose any version ever published by the
-Free Software Foundation.
-
-</para></listitem>
-<listitem><para>
-
-If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the
-author to ask for permission. For software which is copyrighted by
-the Free Software Foundation, write to the Free Software Foundation;
-we sometimes make exceptions for this. Our decision will be guided by
-the two goals of preserving the free status of all derivatives of our
-free software and of promoting the sharing and reuse of software
-generally.
-
-</para><para>
-
-NO WARRANTY
-
-</para></listitem>
-<listitem><para>
-
-because the program is licensed free of charge, there is no
-warranty for the program, to the extent permitted by applicable law.
-except when otherwise stated in writing the copyright holders and/or
-other parties provide the program "as is" without warranty of any
-kind, either expressed or implied, including, but not limited to, the
-implied warranties of merchantability and fitness for a particular
-purpose. the entire risk as to the quality and performance of the
-program is with you. should the program prove defective, you assume
-the cost of all necessary servicing, repair or correction.
-
-</para></listitem>
-<listitem><para>
-
-in no event unless required by applicable law or agreed to in
-writing will any copyright holder, or any other party who may modify
-and/or redistribute the program as permitted above, be liable to you
-for damages, including any general, special, incidental or
-consequential damages arising out of the use or inability to use the
-program (including but not limited to loss of data or data being
-rendered inaccurate or losses sustained by you or third parties or a
-failure of the program to operate with any other programs), even if
-such holder or other party has been advised of the possibility of
-such damages.
-
-</para></listitem>
-</itemizedlist>
-<para>
-
-END OF TERMS AND CONDITIONS
-
-</para>
- </sect1>
-
- <sect1><title>How to Apply These Terms to Your New Programs</title>
-<para>
-
-If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make
-it free software which everyone can redistribute and change under
-these terms.
-
-</para><para>
-
-To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-</para><para>
-
-one line to give the program's name and a brief idea of what it
-does.
-
-</para><para>
-
-Copyright (C) year name of author
-
-</para><para>
-
-This program is free software; you can redistribute it and/or modify
-it under the terms of the gnu General Public License as published by
-the Free Software Foundation; either version 2 of the License, or (at
-your option) any later version.
-
-</para><para>
-
-This program is distributed in the hope that it will be useful, but
-without any warranty; without even the implied warranty of
-merchantability or fitness for a particular purpose. See the gnu
-General Public License for more details.
-
-</para><para>
-
-You should have received a copy of the gnu General Public License
-along with this program; if not, write to the Free Software
-Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
-MA  02110-1301, USA.
-
-</para><para>
-
-Also add information on how to contact you by electronic and paper
-mail.
-
-</para><para>
-
-If the program is interactive, make it output a short notice like
-this when it starts in an interactive mode:
-
-</para><para>
-
-Gnomovision version 69, Copyright (C) year name of author
-
-</para><para>
-
-Gnomovision comes with absolutely no warranty; for details type `show
-w'.
-
-</para><para>
-
-This is free software, and you are welcome to redistribute it under
-certain conditions; type `show c' for details.
-
-</para><para>
-
-The hypothetical commands `show w' and `show c' should show the
-appropriate parts of the General Public License. Of course, the
-commands you use may be called something other than `show w' and
-`show c'; they could even be mouse-clicks or menu items &mdash; whatever
-suits your program.
-
-</para><para>
-
-You should also get your employer (if you work as a programmer) or
-your school, if any, to sign a "copyright disclaimer" for the
-program, if necessary. Here is a sample; alter the names:
-
-</para><para>
-
-Yoyodyne, Inc., hereby disclaims all copyright interest in the
-program `Gnomovision' (which makes passes at compilers) written by
-James Hacker.
-
-</para><para>
-
-signature of Ty Coon, 1 April 1989
-
-</para><para>
-
-Ty Coon, President of Vice
-
-</para><para>
-
-This General Public License does not permit incorporating your
-program into proprietary programs. If your program is a subroutine
-library, you may consider it more useful to permit linking
-proprietary applications with the library. If this is what you want
-to do, use the gnu Library General Public License instead of this
-License.
-
-</para>
- </sect1>
-</appendix>
diff --git a/fi/appendix/plip.xml b/fi/appendix/plip.xml
deleted file mode 100644
index 74913ab34..000000000
--- a/fi/appendix/plip.xml
+++ /dev/null
@@ -1,194 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 29687 untranslated -->
-
- <sect1 id="plip" arch="i386">
- <title>Installing &debian; over Parallel Line IP (PLIP)</title>
-
-<para>
-
-This section explains how to install &debian; on a computer without
-Ethernet card, but with just a remote gateway computer attached via
-a Null-Modem cable (also called Null-Printer cable). The gateway
-computer should be connected to a network that has a Debian mirror
-on it (e.g. to the Internet).
-
-</para><para>
-
-In the example in this appendix we will set up a PLIP connection using
-a gateway connected to the Internet over a dial-up connection (ppp0).
-We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP
-interfaces on the target system and the source system respectively
-(these addresses should be unused within your network address space).
-
-</para><para>
-
-The PLIP connection set up during the installation will also be available
-after the reboot into the installed system (see <xref linkend="boot-new"/>).
-
-</para><para>
-
-Before you start, you will need to check the BIOS configuration (IO base
-address and IRQ) for the parallel ports of both the source and target
-systems. The most common values are <literal>io=0x378</literal>,
-<literal>irq=7</literal>.
-
-</para>
-
-  <sect2>
-  <title>Requirements</title>
-
-<itemizedlist>
-<listitem><para>
-
-A target computer, called <emphasis>target</emphasis>, where Debian will be
-installed.
-
-</para></listitem>
-<listitem><para>
-
-System installation media; see <xref linkend="installation-media"/>.
-
-</para></listitem>
-<listitem><para>
-
-Another computer connected to the Internet, called <emphasis>source</emphasis>,
-that will function as the gateway.
-
-</para></listitem>
-<listitem><para>
-
-A DB-25 Null-Modem cable. See the
-<ulink url="&url-plip-install-howto;">PLIP-Install-HOWTO</ulink> for more
-information on this cable and instructions how to make your own.
-
-</para></listitem>
-</itemizedlist>
-
-  </sect2>
-
-  <sect2>
-  <title>Setting up source</title>
-<para>
-
-The following shell script is a simple example of how to configure the
-source computer as a gateway to the Internet using ppp0.
-
-<informalexample><screen>
-#!/bin/sh
-
-# We remove running modules from kernel to avoid conflicts and to
-# reconfigure them manually.
-modprobe -r lp parport_pc
-modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable>
-modprobe plip
-
-# Configure the plip interface (plip0 for me, see dmesg | grep plip)
-ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up
-
-# Configure gateway
-modprobe iptable_nat
-iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE
-echo 1 > /proc/sys/net/ipv4/ip_forward
-</screen></informalexample>
-
-</para>
-  </sect2>
-
-  <sect2>
-  <title>Installing target</title>
-<para>
-
-Boot the installation media. The installation needs to be run in
-expert mode; enter <userinput>expert</userinput> at the boot prompt.
-Below are the answers that should be given during various stages of
-the installation.
-
-</para>
-
-<orderedlist>
-<listitem><para>
-
-<guimenuitem>Load installer components</guimenuitem>
-
-</para><para>
-
-Select the <userinput>plip-modules</userinput> option from the list; this
-will make the PLIP drivers available to the installation system.
-
-</para></listitem>
-<listitem><para>
-
-<guimenuitem>Detect network hardware</guimenuitem>
-
-</para>
-
- <itemizedlist>
- <listitem><para>
-
-If target <emphasis>does</emphasis> have a network card, a list of driver
-modules for detected cards will be shown. If you want to force &d-i; to
-use plip instead, you have to deselect all listed driver modules.
-Obviously, if target doesn't have a network card, the installer will not
-show this list.
-
- </para></listitem>
- <listitem><para>
-
-Prompt for module parameters: Yes
-
- </para></listitem>
- <listitem><para>
-
-Because no network card was detected/selected earlier, the installer will
-ask you to select a network driver module from a list.
-Select the <userinput>plip</userinput> module.
-
- </para></listitem>
- <listitem><para>
-
-Additional parameters for module parport_pc:
-<userinput><replaceable>io=0x378 irq=7</replaceable></userinput>
-
- </para></listitem>
- <listitem><para>
-
-Additional parameters for module plip: leave empty
-
- </para></listitem>
- </itemizedlist>
-
-</listitem>
-<listitem><para>
-
-<guimenuitem>Configure the network</guimenuitem>
- 
- <itemizedlist>
- <listitem><para>
-
-Auto-configure network with DHCP: No
-
- </para></listitem>
- <listitem><para>
-
-IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>
-
- </para></listitem>
- <listitem><para>
-
-Point-to-point address:
-<userinput><replaceable>192.168.0.2</replaceable></userinput>
-
- </para></listitem>
- <listitem><para>
-
-Name server addresses: you can enter the same addresses used on
-source (see <filename>/etc/resolv.conf</filename>)
-
- </para></listitem>
- </itemizedlist>
-
-</para></listitem>
-</orderedlist>
-
-  </sect2>
- </sect1>
diff --git a/fi/appendix/preseed.xml b/fi/appendix/preseed.xml
deleted file mode 100644
index b64c281f2..000000000
--- a/fi/appendix/preseed.xml
+++ /dev/null
@@ -1,1119 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 36758 untranslated -->
-
-<!--
-Be carefull with the format of this file as it is parsed to generate
-the example preconfiguration file.
-In that file all text between <informalexample> tags that have the
-attribute 'role="example"' set is included, except if a 'condition'
-attribute is in force that does not match the specified release or if an
-'arch' attribute is in force that does not match the specified architecture.
-
-Currently only a single variant of the example file is generated (for i386).
--->
-
-<appendix id="appendix-preseed">
-<title>Automating the installation using preseeding</title>
-
-<para>
-
-This appendix explains the intricacies of preseeding answers to questions in
-&d-i; to automate your installation.
-
-</para><para>
-
-The configuration fragments used in this appendix are also available as an
-example preconfiguration file from &urlset-example-preseed;.
-
-</para>
-
- <sect1 id="preseed-intro">
- <title>Introduction</title>
-<para>
-
-Preseeding provides a way to set answers to questions asked during the
-installation process, without having to manually enter the answers while
-the installation is running. This makes it possible to fully automate most
-types of installation and even offers some features not available during
-normal installations.
-
-</para>
-
-  <sect2 id="preseed-methods">
-  <title>Preseeding methods</title>
-<para>
-
-There are three methods that can be used for preseeding:
-<firstterm>initrd</firstterm>, <firstterm>file</firstterm> and
-<firstterm>network</firstterm>. Initrd preseeding will work with any
-installation method and supports preseeding of more things, but it requires
-the most preparation. File and network preseeding each can be used with
-different installation methods. With file and network preseeding the first
-few installer questions cannot be preseeded because the preconfiguration
-file is only loaded after they have been asked.
-
-</para><para>
-
-The following table shows which preseeding methods can be used with which
-installation methods.
-
-<informaltable>
-<tgroup cols="4">
-<thead>
-<row>
-  <entry>Installation method</entry><entry>initrd</entry>
-  <entry>file</entry><entry>network</entry>
-</row>
-</thead>
-
-<tbody>
-<row>
-  <entry>CD/DVD</entry>
-  <entry>yes</entry>
-  <entry>yes</entry>
-  <entry>no</entry>
-</row><row>
-  <entry>netboot</entry>
-  <entry>yes</entry>
-  <entry>no</entry>
-  <entry>yes</entry>
-</row><row>
-  <entry>hd-media <phrase condition="bootable-usb">(including usb-stick)</phrase></entry>
-  <entry>yes</entry>
-  <entry>yes</entry>
-  <entry>no</entry>
-</row><row condition="supports-floppy-boot">
-  <entry>floppy based (cd-drivers)</entry>
-  <entry>yes</entry>
-  <entry>yes</entry>
-  <entry>no</entry>
-</row><row condition="supports-floppy-boot">
-  <entry>floppy based (net-drivers)</entry>
-  <entry>yes</entry>
-  <entry>no</entry>
-  <entry>yes</entry>
-</row><row arch="s390">
-  <entry>generic/tape</entry>
-  <entry>yes</entry>
-  <entry>no</entry>
-  <entry>yes</entry>
-</row>
-</tbody>
-
-</tgroup></informaltable>
-
-</para><para>
-
-An important difference between the preseeding methods is the point at which
-the preconfiguration file is loaded and processed. For initrd preseeding
-this is right at the start of the installation, before the first question is
-even asked. For file preseeding this is after the CD or CD image has been
-loaded. For network preseeding it is only after the network has been
-configured.
-
-</para><para>
-
-In practical terms this means for file and network preseeding that the
-questions about language, country and keyboard selection will already have
-been asked. For network preseeding add to that any questions related to
-network configuration. Some other questions that are only displayed
-at medium or low priority (like the first hardware detection run) will
-also already have been processed.
-
-</para><para>
-
-Obviously, any questions that have been processed before the
-preconfiguration file is loaded cannot be preseeded.
-<xref linkend="preseed-bootparms"/> offers a way to avoid these
-questions being asked.
-
-</para>
-  </sect2>
-
-  <sect2 id="preseed-limitations">
-  <title>Limitations</title>
-<para>
-
-Although most questions used by &d-i; can be preseeded using this method,
-there are some notable exceptions. You must (re)partition an entire disk
-or use available free space on a disk; it is not possible to use existing
-partitions. You currently cannot use preseeding to set up RAID.
-
-</para>
-  </sect2>
-
-<!-- Joeyh feels this is too technical, so leave it out for now
-  <sect2 id="preseed-debconf">
-  <title>Debconf basics</title>
-<para>
-
-Preseeding makes use of the <classname>debconf</classname> framework. This
-framework is the preferred mechanism used in Debian to interact with the user
-when configuring packages and also forms the heart of &d-i;.
-In the <classname>debconf</classname> framework questions or dialogs are
-based on <firstterm>templates</firstterm>. There are different types of
-templates for different types of questions. The actual questions are
-<quote>generated</quote> from templates at runtime;  multiple questions can
-use the same template.
-
-</para><para>
-
-The following types of templates are relevant for preseeding.
-
-</para>
-
-<itemizedlist>
-<listitem><para>
-  string: allows the user to type any value
-</para></listitem>
-<listitem><para>
-  password: similar to string but the value typed is not displayed
-</para></listitem>
-<listitem><para>
-  boolean: for yes/no or true/false type of questions
-</para></listitem>
-<listitem><para>
-  select: allows the user to select one option from a list
-</para></listitem>
-<listitem><para>
-  multiselect: allows the user to select zero, one or more options from a list
-</para></listitem>
-<listitem><para>
-  note: used to display a message
-</para></listitem>
-</itemizedlist>
-
-<para>
-
-In &d-i; templates are stored in a readable file
-<filename>/var/cache/debconf/templates.dat</filename>. This file contains all fixed
-text and all translations. It can also contain a default value for the
-template. The fixed text can include variables that will be replaced at
-runtime.
-
-</para><para>
-
-Another readable file <filename>/var/cache/debconf/questions.dat</filename>
-is used to store the values for variables and the answers given to questions.
-A question always refers to the template used to ask it. For obvious
-security reasons the values for templates of type <quote>password</quote>
-are stored in a separate, non-readable file in the same directory.
-
-</para>
-  </sect2>
--->
-
-  <sect2 id="preseed-hooks">
-  <title>Running custom commands during the installation</title>
-<para>
-
-A very powerful and flexible option offered by the preconfiguration tools
-is the ability to run commands or scripts at certain points in the
-installation. See <xref linkend="preseed-shell"/> for details.
-
-</para>
-
-<itemizedlist>
-<listitem><para>
-  <userinput>preseed/early_command</userinput>: is run as soon as the
-  preconfiguration file has been loaded
-</para></listitem>
-<listitem><para>
-  <userinput>preseed/late_command</userinput>: is run just before the reboot
-  at the end of the install, but before the <filename>/target</filename>
-  filesystem has been unmounted
-</para></listitem>
-</itemizedlist>
-
-  </sect2>
-
-  <sect2 id="preseed-seenflag">
-  <title>Using preseeding to change default values</title>
-<para>
-
-It is possible to use preseeding to change the default answer for a
-question, but still have the question asked. To do this the
-<firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after
-setting the value for a template.
-
-</para>
-
-<informalexample><screen>
-d-i foo/bar string value
-d-i foo/bar seen false
-</screen></informalexample>
-
-  </sect2>
- </sect1>
-
- <sect1 id="preseed-using">
- <title>Using preseeding</title>
-<para>
-
-Of course you will first need to create a preconfiguration file and place it in
-the location from where you want to use it. Creating the preconfiguration file
-is covered later in this appendix. Putting it in the correct location is fairly
-straightforward for network preseeding or if you want to read the file off
-a floppy or usb-stick. If you want to include the file on a CD or DVD, you
-will have to remaster the ISO image. How to get the preconfiguration file
-included in the initrd is outside the scope of this document; please consult
-the developers documentation for &d-i;.
-
-</para><para>
-
-An example preconfiguration file that you can use as basis for your own
-preconfiguration file is available from &urlset-example-preseed;. This file is
-based on the configuration fragments included in this appendix.
-
-</para>
-
-  <sect2 id="preseed-loading">
-  <title>Loading the preconfiguration file</title>
-<para>
-
-If you are using initrd preseeding, you only have to make sure a file named
-<filename>preseed.cfg</filename> is included in the root directory of the
-initrd. The installer will automatically check if this file is present and
-load it.
-
-</para><para>
-
-For the other preseeding methods you need to tell the installer what file
-to use when you boot it. This is normally done by passing the kernel a boot
-parameter, either manually at boot time or by editing the bootloader
-configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the
-parameter to the end of the append line(s) for the kernel.
-
-</para><para>
-
-If you do specify the preconfiguration file in the bootloader configuration,
-you might change the configuration so you don't need to hit enter to boot the
-installer. For syslinux this means setting the timeout to <literal>1</literal>
-in <filename>syslinux.cfg</filename>.
-
-</para><para>
-
-To make sure the installer gets the right preconfiguration file, you can
-optionally specify a checksum for the file. Currently this needs to be a
-md5sum, and if specified it must match the preconfiguration file or the
-installer will refuse to use it.
-
-</para>
-
-<informalexample><screen>
-Boot parameters to specify:
-- if you're netbooting:
-  preseed/url=http://host/path/to/preseed.cfg
-  preseed/url/checksum=5da499872becccfeda2c4872f9171c3d
-
-- if you're booting a remastered CD:
-  preseed/file=/cdrom/preseed.cfg
-  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d
-
-- if you're installing from USB media (put the preconfiguration file in the
-  toplevel directory of the USB stick):
-  preseed/file=/hd-media/preseed.cfg
-  preseed/file/checksum=5da499872becccfeda2c4872f9171c3d
-</screen></informalexample>
-
-<para>
-
-While you're at it, you may want to add a boot parameter
-<userinput>debconf/priority=critical</userinput>. This will avoid most
-questions even if the preseeding below misses some.
-
-</para>
-  </sect2>
-  
-  <sect2 id="preseed-dhcp">
-  <title>Using a DHCP server to specify preconfiguration files</title>
-<para>
-
-It's also possible to use DHCP to specify a preconfiguration file to download
-from the network. DHCP allows specifying a filename. Normally this is a file
-to netboot, but if it appears to be an URL then installation media that
-support network preseeding will download the file from the URL and use it as a
-preconfiguration file. Here is an example of how to set it up in the dhcpd.conf
-for version 3 of the ISC DHCP server (the dhcp3-server Debian package).
-
-</para>
-
-<informalexample><screen>
-if substring (option vendor-class-identifier, 0, 3) = "d-i" {
-    filename "http://host/preseed.cfg";
-}
-</screen></informalexample>
-
-<para>
-
-Note that the above example limits this filename to DHCP clients that identify
-themselves as "d-i", so it will not affect regular DHCP clients, but only
-the installer. You can also put the text in a stanza for only one particular
-host to avoid preseeding all installs on your network.
-
-</para><para>
-
-A good way to use the DHCP preseeding is to only preseed values specific to
-your network, such as the Debian mirror to use. This way installs on your
-network will automatically get a good mirror selected, but the rest of the
-installation can be performed interactively. Using DHCP preseeding to fully
-automate Debian installs should only be done with care.
-
-</para>
-  </sect2>
-
-  <sect2 id="preseed-bootparms">
-  <title>Using boot parameters to supplement preseeding</title>
-<para>
-
-Some parts of the installation process cannot be automated using some forms
-of preseeding because the questions are asked before the preconfiguration
-file is loaded. For example, if the preconfiguration file is downloaded over
-the network, the network setup must be done first. One reason to use initrd
-preseeding is that it allows preseeding of even these early steps of the
-installation process.
-
-</para><para>
-
-If a preconfiguration file cannot be used to preseed some steps, the install
-can still be fully automated, since you can pass preseed values to the kernel
-on the command line. Just pass <userinput>path/to/var=value</userinput>
-for any of the preseed variables listed in the examples.
-
-</para><para>
-
-A <quote>&ndash;&ndash;</quote> in the boot options has special meaning.
-Kernel parameters that appear after it will be copied into the installed
-bootloader configuration (if supported by the installer for the
-bootloader). Note that the <quote>&ndash;&ndash;</quote> may already be
-present in the default boot parameters.
-
-</para>
-<note><para>
-
-The 2.4 kernel accepts a maximum of 8 command line options and
-8 environment options (including any options added by default for the
-installer). If these numbers are exceeded, 2.4 kernels will drop any
-excess options and 2.6 kernels will panic. For kernel 2.6.9 and later,
-you can use 32 command line options and 32 environment options.
-
-</para></note>
-<para>
-
-For most installations some of the default options in your bootloader
-configuration file, like <literal>vga=normal</literal>, may be safely
-removed which may allow you to add more options for preseeding.
-
-</para>
-<note><para>
-
-It may not always be possible to specify values with spaces for boot
-parameters, even if you delimit them with quotes.
-
-</para></note>
-  </sect2>
- </sect1>
-
- <sect1 id="preseed-creating">
- <title>Creating a preconfiguration file</title>
-<para>
-
-The preconfiguration file is in the format used by the
-<command>debconf-set-selections</command> command. The general format of
-a line in a preconfiguration file is:
-
-<informalexample><screen>
-&lt;owner&gt; &lt;template name&gt; &lt;template type&gt; &lt;value&gt;
-</screen></informalexample>
-
-</para><para>
-
-There are a few rules to keep in mind when writing a preconfiguration file.
-
-</para>
-
-<itemizedlist>
-<listitem><para>
-  Put only a single space or tab between type and value: any additional
-  whitespace will be interpreted as belonging to the value.
-</para></listitem>
-<listitem><para>
-  A line can be split into multiple lines by appending a backslash
-  (<quote><literal>\</literal></quote>) as the line continuation character.
-  A good place to split a line is after the template name; a bad place is
-  between type and value.
-</para></listitem>
-<listitem><para>
-  Most templates need to be preseeded using the values valid in English and
-  not the translated values. However, there are some templates (for example
-  in <classname>partman</classname> where the translated values need to be
-  used.
-</para></listitem>
-<listitem><para>
-  Some templates take a code as value instead of the English text that is
-  shown during installation.
-</para></listitem>
-</itemizedlist>
-
-<para>
-
-The easiest way to create a preconfiguration file is to use the example file
-linked in <xref linkend="preseed-contents"/> as basis and work from there.
-
-</para><para>
-
-An alternative method is to do a manual installation and then, after
-rebooting, use the <command>debconf-get-selections</command> from the
-<classname>debconf-utils</classname> package to dump both the debconf
-database and the installer's cdebconf database to a single file:
-
-<informalexample><screen>
-$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>
-$ debconf-get-selections &gt;&gt; <replaceable>file</replaceable>
-</screen></informalexample>
-
-</para><para>
-
-However, a file generated in this manner will have some items that should
-not be preseeded, and the example file is a better starting place for most
-users.
-
-</para>
-
-<note><para>
-
-This method relies on the fact that, at the end of the installation, the
-installer's cdebconf database is saved to the installed system in
-<filename>/var/log/installer/cdebconf</filename>. However, because the
-database may contain sensitive information, by default the files are only
-readable by root.
-
-</para><para>
-
-The directory <filename>/var/log/installer</filename> and all files in it
-will be deleted from your system if you purge the package
-<classname>installation-report</classname>.
-
-</para></note>
-
-<para>
-
-To check possible values for templates, you can use <command>nano</command>
-to examine the files in <filename>/var/lib/cdebconf</filename> while an
-installation is in progress. View <filename>templates.dat</filename> for
-the raw templates and <filename>questions.dat</filename> for the current
-values and for the values assigned to variables.
-
-</para><para>
-
-To check if the format of your preconfiguration file is valid before performing
-an install, you can use the command <command>debconf-set-selections -c
-<replaceable>preseed.cfg</replaceable></command>.
-
-</para>
- </sect1>
-
- <sect1 id="preseed-contents">
- <title>Contents of the preconfiguration file</title>
-<para>
-
-The configuration fragments used in this appendix are also available as an
-example preconfiguration file from &urlset-example-preseed;.
-
-</para><para>
-
-Note that this example is based on an installation for the Intel x86
-architecture. If you are installing a different architecture, some of the
-examples (like keyboard selection and bootloader installation) may not be
-relevant and will need to be replaced by debconf settings appropriate for
-your architecture.
-
-</para>
- 
-  <sect2 id="preseed-l10n">
-  <title>Localization</title>
-<para>
-
-Setting localization values will only work if you are using initrd preseeding.
-With all other methods the preconfiguration file will only be loaded after
-these questions have been asked.
-
-</para><para>
-
-The locale can be used to specify both language and country.
-To specify the locale as a boot parameter, use
-<userinput>debian-installer/locale=<replaceable>en_US</replaceable></userinput>.
-
-<informalexample role="example"><screen>
-# Locale sets language and country.
-d-i debian-installer/locale string en_US
-</screen></informalexample>
-
-</para><para>
-
-Keyboard configuration consists of selecting a keyboard architecture and a
-keymap. In most cases the correct keyboard architecture is selected by
-default, so there's normally no need to preseed it. The keymap must
-be valid for the selected  keyboard architecture.
-
-<informalexample role="example"><screen>
-# Keyboard selection.
-#d-i console-tools/archs select at
-d-i console-keymaps-at/keymap select us
-# Example for a different keyboard architecture
-#d-i console-keymaps-usb/keymap select mac-usb-us
-</screen></informalexample>
-
-</para><para>
-
-To skip keyboard configuration, preseed
-<classname>console-tools/archs</classname> with
-<userinput>skip-config</userinput>.
-This will result in the kernel keymap remaining active.
-
-</para>
-
-<note><para>
-
-The changes in the input layer for 2.6 kernels have made the keyboard
-architecture virtually obsolete. For 2.6 kernels normally a <quote>PC</quote>
-(<userinput>at</userinput>) keymap should be selected.
-
-</para></note>
-  </sect2>
-
-  <sect2 id="preseed-network">
-  <title>Network configuration</title>
-<para>
-
-Of course, preseeding the network configuration won't work if you're
-loading your preconfiguration file from the network. But it's great when
-you're booting from CD or USB stick. If you are loading preconfiguration
-files from the network, you can pass network config parameters by using
-kernel boot parameters.
-
-</para><para>
-
-If you need to pick a particular interface when netbooting before loading
-a preconfiguration file from the network, use a boot parameter such as
-<userinput>netcfg/choose_interface=<replaceable>eth1</replaceable></userinput>.
-
-</para>
-
-<informalexample role="example"><screen>
-# netcfg will choose an interface that has link if possible. This makes it
-# skip displaying a list if there is more than one interface.
-d-i netcfg/choose_interface select auto
-
-# To pick a particular interface instead:
-#d-i netcfg/choose_interface select eth1
-
-# If you have a slow dhcp server and the installer times out waiting for
-# it, this might be useful.
-#d-i netcfg/dhcp_timeout string 60
-
-# If you prefer to configure the network manually, uncomment this line and
-# the static network configuration below.
-#d-i netcfg/disable_dhcp boolean true
-
-# If you want the preconfiguration file to work on systems both with and
-# without a dhcp server, uncomment these lines and the static network
-# configuration below.
-#d-i netcfg/dhcp_failed note
-#d-i netcfg/dhcp_options select Configure network manually
-
-# Static network configuration.
-#d-i netcfg/get_nameservers string 192.168.1.1
-#d-i netcfg/get_ipaddress string 192.168.1.42
-#d-i netcfg/get_netmask string 255.255.255.0
-#d-i netcfg/get_gateway string 192.168.1.1
-#d-i netcfg/confirm_static boolean true
-
-# Any hostname and domain names assigned from dhcp take precedence over
-# values set here. However, setting the values still prevents the questions
-# from being shown, even if values come from dhcp.
-d-i netcfg/get_hostname string unassigned-hostname
-d-i netcfg/get_domain string unassigned-domain
-
-# Disable that annoying WEP key dialog.
-d-i netcfg/wireless_wep string
-# The wacky dhcp hostname that some ISPs use as a password of sorts.
-#d-i netcfg/dhcp_hostname string radish
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-mirror">
-  <title>Mirror settings</title>
-<para>
-
-Depending on the installation method you use, a mirror may be used both to
-download additional components of the installer, the base system and to
-set up the <filename>/etc/apt/sources.list</filename> for the installed
-system.
-
-</para><para>
-
-The parameter <classname>mirror/suite</classname> determines the suite for
-the installed system.
-
-</para><para>
-
-The parameter <classname>mirror/udeb/suite</classname> determines the suite
-for additional components for the installer. It is only useful to set this
-if components are actually downloaded over the network and should match the
-suite that was used to build the initrd for the installation method used for
-the installation.
-By default the value for <classname>mirror/udeb/suite</classname> is the
-same as <classname>mirror/suite</classname>.
-
-</para>
-
-<informalexample role="example"><screen>
-d-i mirror/country string enter information manually
-d-i mirror/http/hostname string http.us.debian.org
-d-i mirror/http/directory string /debian
-d-i mirror/http/proxy string
-
-# Suite to install.
-#d-i mirror/suite string testing
-# Suite to use for loading installer components (optional).
-#d-i mirror/udeb/suite string testing
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-partman">
-  <title>Partitioning</title>
-<para>
-
-Using preseeding to partition the harddisk is very much limited to what is
-supported by <classname>partman-auto</classname>. You can choose to either
-partition existing free space on a disk or a whole disk. The layout of the
-disk can be determined by using a predefined recipe, a custom recipe from
-a recipe file or a recipe included in the preconfiguration file. It is
-currently not possible to partition multiple disks using preseeding nor to
-set up RAID.
-
-</para>
-
-<warning><para>
-
-The identification of disks is dependent on the order in which their drivers
-are loaded. If there are multiple disks in the system, make very sure the
-correct one will be selected before using preseeding.
-
-</para></warning>
-
-<informalexample role="example"><screen>
-# If the system has free space you can choose to only partition that space.
-# Note: this template must be preseeded with a localized (translated) value.
-#d-i partman-auto/init_automatically_partition \
-#      select Use the largest continuous free space
-
-# Alternatively, you can specify a disk to partition. The device name can
-# be given in either devfs or traditional non-devfs format.
-# For example, to use the first disk devfs knows of:
-d-i partman-auto/disk string /dev/discs/disc0/disc
-
-# You can choose from any of the predefined partitioning recipes.
-# Note: this template must be preseeded with a localized (translated) value.
-d-i partman-auto/choose_recipe \
-       select All files in one partition (recommended for new users)
-#d-i partman-auto/choose_recipe \
-#       select Separate /home partition
-#d-i partman-auto/choose_recipe \
-#       select Separate /home, /usr, /var, and /tmp partitions
-
-# Or provide a recipe of your own...
-# The recipe format is documented in the file devel/partman-auto-recipe.txt.
-# If you have a way to get a recipe file into the d-i environment, you can
-# just point at it.
-#d-i partman-auto/expert_recipe_file string /hd-media/recipe
-
-# If not, you can put an entire recipe the preconfiguration file in one
-# (logical) line. This example creates a small /boot partition, suitable
-# swap, and uses the rest of the space for the root partition:
-#d-i partman-auto/expert_recipe string                         \
-#      boot-root ::                                            \
-#              40 50 100 ext3                                  \
-#                      $primary{ } $bootable{ }                \
-#                      method{ format } format{ }              \
-#                      use_filesystem{ } filesystem{ ext3 }    \
-#                      mountpoint{ /boot }                     \
-#              .                                               \
-#              500 10000 1000000000 ext3                       \
-#                      method{ format } format{ }              \
-#                      use_filesystem{ } filesystem{ ext3 }    \
-#                      mountpoint{ / }                         \
-#              .                                               \
-#              64 512 300% linux-swap                          \
-#                      method{ swap } format{ }                \
-#              .
-
-# This makes partman automatically partition without confirmation.
-d-i partman/confirm_write_new_label boolean true
-d-i partman/choose_partition \
-       select Finish partitioning and write changes to disk
-d-i partman/confirm boolean true
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-time">
-  <title>Clock and time zone setup</title>
-
-<informalexample role="example"><screen>
-# Controls whether or not the hardware clock is set to UTC.
-d-i clock-setup/utc boolean true
-
-# You may set this to any valid setting for $TZ; see the contents of
-# /usr/share/zoneinfo/ for valid values.
-d-i time/zone string US/Eastern
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-apt">
-  <title>Apt setup</title>
-<para>
-
-Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration
-options is fully automated based on your installation method and answers to
-earlier questions. You can optionally add other (local) repositories.
-
-</para>
-
-<informalexample role="example"><screen>
-# You can choose to install non-free and contrib software.
-#d-i apt-setup/non-free boolean true
-#d-i apt-setup/contrib boolean true
-# Uncomment this to avoid adding security sources, or
-# add a hostname to use a different server than security.debian.org.
-#d-i apt-setup/security_host string
-
-# Additional repositories, local[0-9] available
-#d-i apt-setup/local0/comment string local server
-#d-i apt-setup/local0/repository string \
-#       deb http://local.server/debian stable main
-# URL to the public key of the local repository
-#d-i apt-setup/local0/key string http://local.server/key
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-account">
-  <title>Account setup</title>
-<para>
-
-The password for the root account and name and password for a first regular
-user's account can be preseeded. For the passwords you can use either clear
-text values or MD5 <emphasis>hashes</emphasis>.
-
-</para>
-<warning><para>
-
-Be aware that preseeding passwords is not completely secure as everyone
-with access to the preconfiguration file will have the knowledge of these
-passwords. Using MD5 hashes is considered slightly better in terms of
-security but it might also give a false sense of security as access to a
-MD5 hash allows for brute force attacks.
-
-</para></warning>
-
-<informalexample role="example"><screen>
-# Skip creation of a root account (normal user account will be able to
-# use sudo).
-#d-i passwd/root-login boolean false
-# Alternatively, to skip creation of a normal user account.
-#d-i passwd/make-user boolean false
-
-# Root password, either in clear text
-#d-i passwd/root-password password r00tme
-#d-i passwd/root-password-again password r00tme
-# or encrypted using an MD5 hash.
-#d-i passwd/root-password-crypted password [MD5 hash]
-
-# To create a normal user account.
-#d-i passwd/user-fullname string Debian User
-#d-i passwd/username string debian
-# Normal user's password, either in clear text
-#d-i passwd/user-password password insecure
-#d-i passwd/user-password-again password insecure
-# or encrypted using an MD5 hash.
-#d-i passwd/user-password-crypted password [MD5 hash]
-</screen></informalexample>
-
-<para>
-
-The <classname>passwd/root-password-crypted</classname> and
-<classname>passwd/user-password-crypted</classname> variables can also
-be preseeded with <quote>!</quote> as their value. In that case, the
-corresponding account is disabled. This may be convenient for the root
-account, provided of course that an alternative method is setup to allow
-administrative activities or root login (for instance by using SSH key
-authentication or <command>sudo</command>).
-
-</para><para>
-
-An MD5 hash for a password can be generated using the following command.
-
-<informalexample><screen>
-$ echo "r00tme" | mkpasswd -s -H MD5
-</screen></informalexample>
-
-</para>
-  </sect2>
-
-  <sect2 id="preseed-base-installer">
-  <title>Base system installation</title>
-<para>
-
-There is actually not very much that can be preseeded for this stage of the
-installation. The only questions asked concern the installation of the kernel.
-
-</para>
-
-<informalexample role="example"><screen>
-# Select the initramfs generator used to generate the initrd for 2.6 kernels.
-#d-i base-installer/kernel/linux/initramfs-generators string yaird
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-bootloader">
-  <title>Boot loader installation</title>
-
-<informalexample role="example"><screen>
-# Grub is the default boot loader (for x86). If you want lilo installed
-# instead, uncomment this:
-#d-i grub-installer/skip boolean true
-
-# This is fairly safe to set, it makes grub install automatically to the MBR
-# if no other operating system is detected on the machine.
-d-i grub-installer/only_debian boolean true
-
-# This one makes grub-installer install to the MBR if if finds some other OS
-# too, which is less safe as it might not be able to boot that other OS.
-d-i grub-installer/with_other_os boolean true
-
-# Alternatively, if you want to install to a location other than the mbr,
-# uncomment and edit these lines:
-#d-i grub-installer/bootdev  string (hd0,0)
-#d-i grub-installer/only_debian boolean false
-#d-i grub-installer/with_other_os boolean false
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-pkgsel">
-  <title>Package selection</title>
-<para>
-
-You can choose to install any combination of tasks that are available.
-Available tasks as of this writing include:
-
-</para>
-
-<itemizedlist>
-<listitem><para>
-  <userinput>standard</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>desktop</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>gnome-desktop</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>kde-desktop</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>web-server</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>print-server</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>dns-server</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>file-server</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>mail-server</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>sql-database</userinput>
-</para></listitem>
-<listitem><para>
-  <userinput>laptop</userinput>
-</para></listitem>
-</itemizedlist>
-
-<para>
-
-You can also choose to install no tasks, and force the installation of a
-set of packages in some other way. We recommend always including the
-<userinput>standard</userinput> task.
-
-</para>
-
-<informalexample role="example"><screen>
-tasksel tasksel/first multiselect standard, desktop
-#tasksel tasksel/first multiselect standard, web-server
-#tasksel tasksel/first multiselect standard, kde-desktop
-
-# Some versions of the installer can report back on what software you have
-# installed, and what software you use. The default is not to report back,
-# but sending reports helps the project determine what software is most
-# popular and include it on CDs.
-#popularity-contest popularity-contest/participate boolean false
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-finish">
-  <title>Finishing up the first stage install</title>
-
-<informalexample role="example"><screen>
-# Avoid that last message about the install being complete.
-d-i prebaseconfig/reboot_in_progress note
-
-# This will prevent the installer from ejecting the CD during the reboot,
-# which is useful in some situations.
-#d-i cdrom-detect/eject boolean false
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-mailer">
-  <title>Mailer configuration</title>
-<para>
-
-During a normal install, exim asks only a few questions. Here's how to
-avoid even those. More complicated preseeding is possible.
-
-</para>
-
-<informalexample role="example"><screen>
-exim4-config exim4/dc_eximconfig_configtype \
-       select no configuration at this time
-exim4-config exim4/no_config boolean true
-exim4-config exim4/no_config boolean true
-exim4-config exim4/dc_postmaster string
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-X">
-  <title>X configuration</title>
-<para>
-
-Preseeding Debian's X config is possible, but you probably need to know
-some details about the video hardware of the machine, since Debian's X
-configurator does not do fully automatic configuration of everything.
-
-</para>
-
-<informalexample role="example"><screen>
-# X can detect the right driver for some cards, but if you're preseeding,
-# you override whatever it chooses. Still, vesa will work most places.
-#xserver-xorg xserver-xorg/config/device/driver select vesa
-
-# A caveat with mouse autodetection is that if it fails, X will retry it
-# over and over. So if it's preseeded to be done, there is a possibility of
-# an infinite loop if the mouse is not autodetected.
-#xserver-xorg xserver-xorg/autodetect_mouse boolean true
-
-# Monitor autodetection is recommended.
-xserver-xorg xserver-xorg/autodetect_monitor boolean true
-# Uncomment if you have an LCD display.
-#xserver-xorg xserver-xorg/config/monitor/lcd boolean true
-# X has three configuration paths for the monitor. Here's how to preseed
-# the "medium" path, which is always available. The "simple" path may not
-# be available, and the "advanced" path asks too many questions.
-xserver-xorg xserver-xorg/config/monitor/selection-method \
-       select medium
-xserver-xorg xserver-xorg/config/monitor/mode-list \
-       select 1024x768 @ 60 Hz
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-other">
-  <title>Preseeding other packages</title>
-
-<informalexample role="example"><screen>
-# Depending on what software you choose to install, or if things go wrong
-# during the installation process, it's possible that other questions may
-# be asked. You can preseed those too, of course. To get a list of every
-# possible question that could be asked during an install, do an
-# installation, and then run these commands:
-#   debconf-get-selections --installer > file
-#   debconf-get-selections >> file
-</screen></informalexample>
-
-  </sect2>
- </sect1>
-
- <sect1 id="preseed-advanced">
- <title>Advanced options</title>
-
-  <sect2 id="preseed-shell">
-  <title>Shell commands</title>
-
-<informalexample role="example"><screen>
-# d-i preseeding is inherently not secure. Nothing in the installer checks
-# for attempts at buffer overflows or other exploits of the values of a
-# preconfiguration file like this one. Only use preconfiguration files from
-# trusted locations! To drive that home, and because it's generally useful,
-# here's a way to run any shell command you'd like inside the installer,
-# automatically.
-
-# This first command is run as early as possible, just after
-# preseeding is read.
-#d-i preseed/early_command string anna-install some-udeb
-
-# This command is run just before the install finishes, but when there is
-# still a usable /target directory. You can chroot to /target and use it
-# directly, or use the apt-install and in-target commands to easily install
-# packages and run commands in the target system.
-#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh
-</screen></informalexample>
-
-  </sect2>
-
-  <sect2 id="preseed-chainload">
-  <title>Chainloading preconfiguration files</title>
-<para>
-
-It is possible to include other preconfiguration files from a preconfiguration
-file. Any settings in those files will override pre-existing settings from
-files loaded earlier. This makes it possible to put, for example, general
-networking settings for your location in one file and more specific
-settings for certain configurations in other files.
-
-</para>
-
-<informalexample><screen>
-# More that one file can be listed, separated by spaces; all will be
-# loaded. The included files can have preseed/include directives of their
-# own as well. Note that if the filenames are relative, they are taken from
-# the same directory as the preconfiguration file that includes them.
-#d-i preseed/include string x.cfg
-
-# The installer can optionally verify checksums of preconfiguration files
-# before using them. Currently only md5sums are supported, list the md5sums
-# in the same order as the list of files to include.
-#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d
-
-# More flexibly, this runs a shell command and if it outputs the names of
-# preconfiguration files, includes those files. 
-#d-i preseed/include_command \
-#      string echo if [ "`hostname`" = bob ]; then echo bob.cfg; fi
-</screen></informalexample>
-
-  </sect2>
- </sect1>
-</appendix>
diff --git a/fi/appendix/random-bits.xml b/fi/appendix/random-bits.xml
deleted file mode 100644
index 4d3fff8f9..000000000
--- a/fi/appendix/random-bits.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 33719 untranslated -->
-
-<appendix id="random-bits"><title>Random Bits</title>
-
-&files.xml;
-&chroot-install.xml;
-&plip.xml;
-
-</appendix>