Clean-up of outdated/no longer used content (remove docs for non-release archs)

13 files changed, 10 insertions, 337 deletions

diff --git a/en/using-d-i/components.xml b/en/using-d-i/components.xml
index 702185e97..f2a627cae 100644
--- a/en/using-d-i/components.xml
+++ b/en/using-d-i/components.xml
@@ -94,9 +94,6 @@ like RAID, LVM or encrypted devices.
 
 &module-s390-dasd.xml;
 &module-partman.xml;
-&module-autopartkit.xml;
-&module-partitioner.xml;
-&module-partconf.xml;
 &module-partman-md.xml;
 &module-partman-lvm.xml;
 &module-partman-crypto.xml;
@@ -139,22 +136,13 @@ network connection.
 
 If you are installing a diskless workstation, obviously, booting off
 the local disk isn't a meaningful option, and this step will be
-skipped. <phrase arch="sparc">You may wish to set OpenBoot to boot
-from the network by default; see <xref
-linkend="boot-dev-select-sun"/>.</phrase>
+skipped.
 
 </para>
 
 &module-os-prober.xml;
-&module-hppa-palo-installer.xml;
 &module-x86-grub-installer.xml;
-&module-ia64-elilo-installer.xml;
-&module-mipsel-colo-installer.xml;
-&module-powerpc-yaboot-installer.xml;
-&module-powerpc-quik-installer.xml;
 &module-powerpc-grub-installer.xml;
-&module-s390-zipl-installer.xml;
-&module-sparc-silo-installer.xml;
 &module-arm-flash-kernel-installer.xml;
 &module-nobootloader.xml;
   </sect2>
diff --git a/en/using-d-i/modules/autopartkit.xml b/en/using-d-i/modules/autopartkit.xml
deleted file mode 100644
index 67c575a36..000000000
--- a/en/using-d-i/modules/autopartkit.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
diff --git a/en/using-d-i/modules/hppa/palo-installer.xml b/en/using-d-i/modules/hppa/palo-installer.xml
deleted file mode 100644
index eb5398812..000000000
--- a/en/using-d-i/modules/hppa/palo-installer.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-  <sect3 arch="hppa">
-  <title><command>palo</command>-installer</title>
-<para>
-
-The bootloader on PA-RISC is <quote>palo</quote>.
-<command>PALO</command> is similar in configuration and usage to
-<command>LILO</command>, with a few exceptions.  First of all,
-<command>PALO</command> allows you to boot any kernel image on your
-boot partition.  This is because <command>PALO</command> can actually
-read Linux partitions.
-
-</para><para condition="FIXME">
-
-hppa FIXME ( need more info )
-
-</para>
-  </sect3>
diff --git a/en/using-d-i/modules/ia64/elilo-installer.xml b/en/using-d-i/modules/ia64/elilo-installer.xml
deleted file mode 100644
index ff117d5c1..000000000
--- a/en/using-d-i/modules/ia64/elilo-installer.xml
+++ /dev/null
@@ -1,135 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-  <sect3 arch="ia64">
-  <title>Install the <command>ELILO</command> Boot Loader
-         on a Hard Disk</title>
-<para>
-
-The &architecture; boot loader is called <quote>elilo</quote>.
-It is modeled on the <quote>lilo</quote> boot loader for the
-x86 architecture and uses a similar configuration file.
-However, instead of writing an MBR or partition boot record to
-the disk, it copies the necessary files to a separate FAT formatted
-disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem>
-menu in the firmware to point to the files in the EFI partition.
-The <command>elilo</command> boot loader is really in two parts.
-The <filename>/usr/sbin/elilo</filename> command manages the partition and
-copies files into it.
-The <filename>elilo.efi</filename> program is copied into the EFI
-partition and then run by the <quote>EFI Boot Manager</quote> to
-do the actual work of loading and starting the Linux kernel.
-
-</para><para>
-
-The <quote>elilo</quote> configuration and installation is done as the
-last step of installing the packages of the base installation.
-&d-i; will present you with a list of potential disk partitions that it
-has found suitable for an EFI partition.
-Select the partition you set up earlier in the installation, typically
-a partition on the same disk that contains your
-<emphasis>root</emphasis> filesystem.
-
-</para>
-
-  <warning><title>Choose the correct partition!</title>
-
-<para>
-
-The criterion for selecting a partition is that it must be a FAT format
-filesystem with its <emphasis>boot</emphasis> flag set.
-&d-i; may show multiple choices depending on what it finds from scanning
-all of the disks of the system including EFI partitions of other system
-disks and EFI diagnostic partitions.
-Remember, <command>elilo</command> may format the partition during
-the installation, erasing any previous contents!
-
-</para></warning>
-
-  </sect3>
-
-  <sect3 arch="ia64">
-  <title>EFI Partition Contents</title>
-
-<para>
-
-The EFI partition is a FAT filesystem format partition on one of the
-hard disks of the system, usually the same disk that contains the
-<emphasis>root</emphasis> filesystem.
-It is normally not mounted on a running system as it is only needed
-by the <quote>EFI Boot Manager</quote> to load the system and the
-installer part of the <command>elilo</command> writes to the filesystem
-directly.
-The <command>/usr/sbin/elilo</command> utility writes the following files
-into the <filename>efi/debian</filename> directory of the EFI
-partition during the installation.
-Note that the <quote>EFI Boot Manager</quote> would find these files
-using the path <filename>fs<replaceable>n</replaceable>:\efi\debian</filename>.
-There may be other files in this filesystem as well over time as
-the system is updated or re-configured.
-
-</para>
-
-<variablelist>
-
-<varlistentry>
-<term><filename>elilo.conf</filename></term>
-<listitem><para>
-
-This is the configuration file read by the boot loader when it starts.
-It is a copy of the <filename>/etc/elilo.conf</filename> with
-the filenames re-written to refer to files in the EFI partition.
-
-</para></listitem></varlistentry>
-
-<varlistentry>
-<term><filename>elilo.efi</filename></term>
-<listitem><para>
-
-This is the boot loader program that the <quote>EFI Boot Manager</quote>
-runs to boot the system.
-It is the program behind the <guimenuitem>&debian; GNU/Linux</guimenuitem>
-menu item of the <quote>EFI Boot Manager</quote> command menu.
-
-</para></listitem></varlistentry>
-
-<varlistentry>
-<term><filename>initrd.img</filename></term>
-<listitem><para>
-
-This is the initial root filesystem used to boot the kernel.
-It is a copy of the file referenced in the
-<filename>/etc/elilo.conf</filename>.
-In a standard &debian; installation it would be the file in
-<filename>/boot</filename> pointed to by the symbolic link
-<filename>/initrd.img</filename>.
-
-</para></listitem></varlistentry>
-
-<varlistentry>
-<term><filename>readme.txt</filename></term>
-<listitem><para>
-
-This is a small text file warning you that the contents of the
-directory are managed by the <command>elilo</command> and that
-any local changes would be lost at the next time
-<filename>/usr/sbin/elilo</filename> is run.
-
-</para></listitem></varlistentry>
-
-<varlistentry>
-<term><filename>vmlinuz</filename></term>
-<listitem><para>
-
-This is the compressed kernel itself.
-It is a copy of the file referenced in the
-<filename>/etc/elilo.conf</filename>.
-In a standard &debian; installation it would be the file in
-<filename>/boot</filename> pointed to by the symbolic link
-<filename>/vmlinuz</filename>.
-
-</para></listitem></varlistentry>
-
-</variablelist>
-
-  </sect3>
diff --git a/en/using-d-i/modules/mipsel/colo-installer.xml b/en/using-d-i/modules/mipsel/colo-installer.xml
deleted file mode 100644
index 67c575a36..000000000
--- a/en/using-d-i/modules/mipsel/colo-installer.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
diff --git a/en/using-d-i/modules/partconf.xml b/en/using-d-i/modules/partconf.xml
deleted file mode 100644
index 67c575a36..000000000
--- a/en/using-d-i/modules/partconf.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
diff --git a/en/using-d-i/modules/partitioner.xml b/en/using-d-i/modules/partitioner.xml
deleted file mode 100644
index 53394db87..000000000
--- a/en/using-d-i/modules/partitioner.xml
+++ /dev/null
@@ -1,3 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
diff --git a/en/using-d-i/modules/partman.xml b/en/using-d-i/modules/partman.xml
index e880d4800..bb56e017f 100644
--- a/en/using-d-i/modules/partman.xml
+++ b/en/using-d-i/modules/partman.xml
@@ -7,21 +7,7 @@ If you are uncomfortable with partitioning, or just want to know more
 details, see <xref linkend="partitioning"/>.
 
 </para>
-<warning arch="sparc"><para>
-<!-- BTS: #384653 -->
 
-If a hard disk has previously used under Solaris, the partitioner may not
-detect the size of the drive correctly. Creating a new partition table
-does not fix this issue. What does help, is to <quote>zero</quote> the
-first few sectors of the drive:
-
-<informalexample><screen>
-# dd if=/dev/zero of=/dev/sd<replaceable>X</replaceable> bs=512 count=2; sync
-</screen></informalexample>
-
-Note that this will make any existing data on that disk inaccessible.
-
-</para></warning>
 <para>
 
 First you will be given the opportunity to automatically partition
@@ -162,7 +148,7 @@ The following file systems are supported.
   <listitem><para>
     <emphasis>FAT16</emphasis>, <emphasis>FAT32</emphasis>
   </para></listitem>
-  <listitem arch="x86;ia64"><para>
+  <listitem arch="x86"><para>
     <emphasis>NTFS</emphasis> (read-only)
   </para><para>
     Existing NTFS partitions can be resized and it is possible to assign
diff --git a/en/using-d-i/modules/powerpc/quik-installer.xml b/en/using-d-i/modules/powerpc/quik-installer.xml
deleted file mode 100644
index 07ba1e66b..000000000
--- a/en/using-d-i/modules/powerpc/quik-installer.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-  <sect3 arch="powerpc">
-  <title>Install <command>Quik</command> on a Hard Disk</title>
-<para>
-
-The boot loader for OldWorld Power Macintosh machines is
-<command>quik</command>.  You can also use it on CHRP. The installer
-will attempt to set up <command>quik</command> automatically. The
-setup has been known to work on 7200, 7300, and 7600 Powermacs, and on
-some Power Computing clones.
-
-</para>
-  </sect3>
diff --git a/en/using-d-i/modules/powerpc/yaboot-installer.xml b/en/using-d-i/modules/powerpc/yaboot-installer.xml
deleted file mode 100644
index 29383ae5d..000000000
--- a/en/using-d-i/modules/powerpc/yaboot-installer.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-  <sect3 arch="powerpc">
-  <title>Install <command>Yaboot</command> on a Hard Disk</title>
-<para>
-
-Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as
-their boot loader. The installer will set up <command>yaboot</command>
-automatically, so all you need is a small 820k partition named
-<quote>bootstrap</quote> with type
-<emphasis>Apple_Bootstrap</emphasis> created back in the partitioning
-component.  If this step completes successfully then your disk should
-now be bootable and OpenFirmware will be set to boot &debian-gnu;.
-
-</para>
-  </sect3>
diff --git a/en/using-d-i/modules/sparc/silo-installer.xml b/en/using-d-i/modules/sparc/silo-installer.xml
deleted file mode 100644
index fe6d0f607..000000000
--- a/en/using-d-i/modules/sparc/silo-installer.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-  <sect3 arch="sparc">
-  <title>Install the <command>SILO</command> Boot Loader
-         on a Hard Disk</title>
-<para>
-
-The standard &architecture; boot loader is called <quote>silo</quote>.
-It is documented in
-<filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is
-similar in configuration and usage to <command>LILO</command>, with
-a few exceptions. First of all, <command>SILO</command> allows you to
-boot any kernel image on your drive, even if it is not listed in
-<filename>/etc/silo.conf</filename>.  This is because
-<command>SILO</command> can actually read Linux partitions.  Also,
-<filename>/etc/silo.conf</filename> is read at boot time, so there is
-no need to rerun <command>silo</command> after installing a new kernel
-like you would with <command>LILO</command>. <command>SILO</command>
-can also read UFS partitions, which means it can boot SunOS/Solaris
-partitions as well. This is useful if you want to install GNU/Linux
-alongside an existing SunOS/Solaris install.
-
-</para>
-  </sect3>
diff --git a/en/using-d-i/modules/x86/lilo-installer.xml b/en/using-d-i/modules/x86/lilo-installer.xml
deleted file mode 100644
index cc22d1e0f..000000000
--- a/en/using-d-i/modules/x86/lilo-installer.xml
+++ /dev/null
@@ -1,67 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-  <sect3 arch="x86">
-  <title>Install the <command>LILO</command> Boot Loader
-         on a Hard Disk</title>
-<para>
-
-The second &architecture; boot loader is called <quote>LILO</quote>.
-It is an old complex program which offers lots of functionality,
-including DOS, Windows, and OS/2 boot management.  Please carefully
-read the instructions in the directory
-<filename>/usr/share/doc/lilo/</filename> if you have special needs;
-also see the <ulink url="&url-lilo-howto;">LILO mini-HOWTO</ulink>.
-
-</para>
-<note><para>
-
-Currently the LILO installation will only create menu entries for other
-operating systems if these can be <firstterm>chainloaded</firstterm>.
-This means you may have to manually add a menu entry for operating
-systems like GNU/Linux and GNU/Hurd after the installation.
-
-</para></note>
-<para>
-
-&d-i; offers you three choices on where to install the
-<command>LILO</command> boot loader:
-
-<variablelist>
-<varlistentry>
-<term>Master Boot Record (MBR)</term><listitem><para>
-
-This way the <command>LILO</command> will take complete control of the
-boot process.
-
-</para></listitem></varlistentry>
-<varlistentry>
-<term>new &debian; partition</term><listitem><para>
-
-Choose this if you want to use another boot
-manager. <command>LILO</command> will install itself at the beginning
-of the new &debian; partition and it will serve as a secondary boot
-loader.
-
-</para></listitem></varlistentry>
-<varlistentry>
-<term>Other choice</term><listitem><para>
-
-Useful for advanced users who want to install <command>LILO</command>
-somewhere else. In this case you will be asked for desired
-location. You can use traditional device names such as
-<filename>/dev/sda</filename>.
-
-</para></listitem></varlistentry>
-</variablelist>
-
-</para><para>
-
-If you can no longer boot into Windows 9x (or DOS) after this step,
-you'll need to use a Windows 9x (MS-DOS) boot disk and use the
-<userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS
-master boot record &mdash; however, this means that you'll need to use
-some other way to get back into &debian;!
-
-</para>
-  </sect3>
diff --git a/en/using-d-i/using-d-i.xml b/en/using-d-i/using-d-i.xml
index a8da81983..e4f3cc59a 100644
--- a/en/using-d-i/using-d-i.xml
+++ b/en/using-d-i/using-d-i.xml
@@ -22,7 +22,10 @@ used by default unless you select an <quote>Graphical install</quote>
 option in the boot menu. For more information about booting the
 graphical installer, please refer to <xref linkend="graphical"/>.
 
-</para><para arch="powerpc">
+</para>
+
+<!--
+<para arch="powerpc">
 
 For this architecture the &d-i; supports two different user interfaces: a
 text-based one and a graphical one. The text-based interface is
@@ -30,7 +33,10 @@ used by default unless you select an <quote>Graphical install</quote>
 option in the boot menu. For more information about booting the
 graphical installer, please refer to <xref linkend="graphical"/>.
 
-</para><para condition="not-gtk">
+</para>
+-->
+
+<para condition="not-gtk">
 
 For this architecture the installer uses a text-based user interface.
 A graphical user interface is currently not available.
@@ -335,25 +341,6 @@ in &debian;.
 </varlistentry>
 <varlistentry>
 
-<term>partitioner</term><listitem><para>
-
-Allows the user to partition disks attached to the system. A
-partitioning program appropriate to your computer's architecture
-is chosen.
-
-</para></listitem>
-</varlistentry>
-<varlistentry>
-
-<term>partconf</term><listitem><para>
-
-Displays a list of partitions, and creates file systems on
-the selected partitions according to user instructions.
-
-</para></listitem>
-</varlistentry>
-<varlistentry>
-
 <term>partman-lvm</term><listitem><para>
 
 Helps the user with the configuration of the