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

8 files changed, 17 insertions, 246 deletions

diff --git a/en/preparing/bios-setup/powerpc.xml b/en/preparing/bios-setup/powerpc.xml
index f03f3d23c..5b83af691 100644
--- a/en/preparing/bios-setup/powerpc.xml
+++ b/en/preparing/bios-setup/powerpc.xml
@@ -2,6 +2,7 @@
 <!-- $Id$ -->
 
 
+<!--
   <sect2 arch="powerpc" id="invoking-openfirmware">
   <title>Invoking OpenFirmware</title>
 <para>
@@ -50,6 +51,7 @@ installed to nvram.
 
 </para>
   </sect2>
+-->
 
   <sect2 arch="ppc64el;powerpc" id="update-firmware">
   <title>How to update bare metal ppc64el firmware</title>
diff --git a/en/preparing/bios-setup/sparc.xml b/en/preparing/bios-setup/sparc.xml
deleted file mode 100644
index a88c9fe1a..000000000
--- a/en/preparing/bios-setup/sparc.xml
+++ /dev/null
@@ -1,105 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-
-  <sect2 arch="sparc" id="invoking-openboot"><title>Invoking OpenBoot</title>
-
-<para>
-
-OpenBoot provides the basic functions needed to boot the &arch-title;
-architecture.  This is rather similar in function to the BIOS in the
-x86 architecture, although much nicer.  The Sun boot PROMs have a
-built-in forth interpreter which lets you do quite a number of things
-with your machine, such as diagnostics and simple scripts.
-
-</para><para>
-
-To get to the boot prompt you need to hold down the
-<keycap>Stop</keycap> key (on older type 4 keyboards, use the
-<keycap>L1</keycap> key, if you have a PC keyboard adapter, use
-the <keycap>Break</keycap> key) and press the
-<keycap>A</keycap> key. The boot PROM will give you a prompt,
-either <userinput>ok</userinput> or <userinput>&gt;</userinput>. It is
-preferred to have the <userinput>ok</userinput> prompt. So if you get
-the old style prompt, hit the <keycap>n</keycap> key to get the new
-style prompt.
-
-</para><para>
-
-If you are using a serial console, send a break to the machine. With Minicom,
-use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type
-<userinput>%~break</userinput>. Consult the documentation of your terminal
-emulator if you are using a different program.
-
-</para>
-  </sect2>
-
-  <sect2 arch="sparc" id="boot-dev-select-sun">
-  <title>Boot Device Selection</title>
-
-<para>
-
-You can use OpenBoot to boot from specific devices, and also to change
-your default boot device.  However, you need to know some details
-about how OpenBoot names devices; it's considerably different from Linux
-device naming, described in <xref linkend="device-names"/>.
-Also, the command will vary a bit, depending on what version of
-OpenBoot you have.  More information about OpenBoot can be found in
-the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
-
-</para><para>
-
-<!--
-Typically, with newer revisions, you can use OpenBoot devices such as
-<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>,
-<quote>disk</quote>, or <quote>disk2</quote>.  These have the obvious
-meanings; the <quote>net</quote> device is for booting from the network.
-Additionally, the device name can specify a particular partition of a disk,
-such as <quote>disk2:a</quote> to boot disk2, first partition.  Full
-OpenBoot device names have the form:
-
-<informalexample>
-<screen>
-<replaceable>driver-name</replaceable>@
-<replaceable>unit-address</replaceable>:
-<replaceable>device-arguments</replaceable>
-</screen></informalexample>
-
-In older revisions of OpenBoot, device naming is a bit different: the
-floppy device is called <quote>/fd</quote>, and SCSI disk devices are of
-the form <quote>sd(<replaceable>controller</replaceable>,
-<replaceable>disk-target-id</replaceable>,
-<replaceable>disk-lun</replaceable>)</quote>.  The command
-<userinput>show-devs</userinput> in newer OpenBoot revisions is useful
-for viewing the currently configured devices.  For full information,
-whatever your revision, see the
-<ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
-
-</para><para>
--->
-
-To boot from a specific device, use the command <userinput>boot
-<replaceable>device</replaceable></userinput>.  You can set this
-behavior as the default using the <userinput>setenv</userinput>
-command.  However, the name of the variable to set changed between
-OpenBoot revisions.  In OpenBoot 1.x, use the command
-<userinput>setenv boot-from
-<replaceable>device</replaceable></userinput>.  In later revisions of
-OpenBoot, use the command <userinput>setenv boot-device
-<replaceable>device</replaceable></userinput>. Note, this is also
-configurable using the <command>eeprom</command> command on Solaris,
-or modifying the appropriate files in
-<filename>/proc/openprom/options/</filename>, for example under Linux:
-
-<informalexample><screen>
-# echo disk1:1 &gt; /proc/openprom/options/boot-device
-</screen></informalexample>
-
-and under Solaris:
-
-<informalexample><screen>
-eeprom boot-device=disk1:1
-</screen></informalexample>
-
-</para>
-  </sect2>
diff --git a/en/preparing/minimum-hardware-reqts.xml b/en/preparing/minimum-hardware-reqts.xml
index c5e373ec1..84f8c7352 100644
--- a/en/preparing/minimum-hardware-reqts.xml
+++ b/en/preparing/minimum-hardware-reqts.xml
@@ -20,11 +20,15 @@ risk being frustrated if they ignore these suggestions.
 A Pentium 4, 1GHz system is the minimum recommended for a desktop
 system.
 
-</para><para arch="powerpc">
+</para>
+
+<!--
+<para arch="powerpc">
 
 Any OldWorld or NewWorld PowerPC can serve well as a desktop system.
 
 </para>
+-->
 
 <table>
 <title>Recommended Minimum System Requirements</title>
diff --git a/en/preparing/needed-info.xml b/en/preparing/needed-info.xml
index b9e6e220d..2db3a4d23 100644
--- a/en/preparing/needed-info.xml
+++ b/en/preparing/needed-info.xml
@@ -52,20 +52,14 @@ Often contains useful information on configuring or using your hardware.
 
  <!-- We need the arch dependence for the whole list to ensure proper xml
       as long as not architectures have a paragraph -->
- <itemizedlist arch="x86;sparc;mips;mipsel;mips64el">
+ <itemizedlist arch="x86;mipsel;mips64el">
 <listitem arch="x86"><para>
 
 <ulink url="&url-debian-wiki-hardware;">The Debian Wiki hardware page</ulink>
 
 </para></listitem>
 
-<listitem arch="sparc"><para>
-
-<ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink>
-
-</para></listitem>
-
-<listitem arch="mips;mipsel;mips64el"><para>
+<listitem arch="mipsel;mips64el"><para>
 
 <ulink url="&url-linux-mips;">Linux/MIPS website</ulink>
 
diff --git a/en/preparing/non-debian-partitioning.xml b/en/preparing/non-debian-partitioning.xml
index c634c17d5..9f53f611a 100644
--- a/en/preparing/non-debian-partitioning.xml
+++ b/en/preparing/non-debian-partitioning.xml
@@ -74,37 +74,8 @@ to the partitioning step, select the option for manual partitioning, select
 the partition to resize, and simply specify its new size.
 </para>
 
-<para arch="hppa" condition="FIXME">
-
-<emphasis>FIXME: write about HP-UX disks?</emphasis>
-
-</para><para>
-
-Creating and deleting partitions can be done from within &d-i; as
-well as from an existing operating system. As a rule of thumb,
-partitions should be created by the system for which they are to
-be used, i.e. partitions to be used by &debian-gnu; should be
-created from within &d-i; and partitions to be used from another
-operating system should be created from there. &d-i; is
-capable of creating non-&arch-kernel; partitions, and partitions created
-this way usually work without problems when used in other operating
-systems, but there are a few rare corner cases in which this could
-cause problems, so if you want to be sure, use the native partitioning
-tools to create partitions for use by other operating systems.
-</para><para>
-
-If you are going to install more than one operating system on the same
-machine, you should install all other system(s) before proceeding with
-the &debian; installation. Windows and other OS installations may destroy
-your ability to start &debian;, or encourage you to reformat non-native
-partitions.
-
-</para><para>
-
-You can recover from these actions or avoid them, but installing
-the native system first saves you trouble.
-
-</para><para arch="powerpc">
+<!--
+<para arch="powerpc">
 
 In order for OpenFirmware to automatically boot &debian-gnu; the &arch-parttype;
 partitions should appear before all other partitions on the disk,
@@ -117,66 +88,8 @@ tools later during the actual install, and replace it with &arch-parttype;
 partitions.
 
 </para>
-
-<!-- paragraph scheduled for removal
-<para>
-
-If you currently have one hard disk with one partition (a common setup
-for desktop computers), and you want to multi-boot the native
-operating system and &debian;, you will need to:
-
-  <orderedlist>
-<listitem><para>
-
-Back up everything on the computer.
-
-</para></listitem>
-<listitem><para>
-
-Boot from the native operating system installer media such as CD-ROM
-or tapes.
-
-<phrase arch="powerpc">When booting from a MacOS CD, hold the
-<keycap>c</keycap> key while
-booting to force the CD to become the active MacOS system.</phrase>
-
-</para></listitem>
-<listitem><para>
-
-Use the native partitioning tools to create native system
-partition(s). Leave either a place holder partition or free space for
-&debian-gnu;.
-
-</para></listitem>
-<listitem><para>
-
-Install the native operating system on its new partition.
-
-</para></listitem>
-<listitem><para>
-
-Boot back into the native system to verify everything's OK,
-    and to download the &debian; installer boot files.
-
-</para></listitem>
-<listitem><para>
-
-Boot the &debian; installer to continue installing &debian;.
-
-</para></listitem>
-</orderedlist>
-
-</para>
--->
-
-<!-- &nondeb-part-x86.xml; currently includes only outdated information;
-     don't use it for building the manual.
-
-&nondeb-part-x86.xml;
-
 -->
 
-&nondeb-part-sparc.xml;
 &nondeb-part-powerpc.xml;
 
  </sect1>
diff --git a/en/preparing/nondeb-part/powerpc.xml b/en/preparing/nondeb-part/powerpc.xml
index 6681589f4..c88b75c91 100644
--- a/en/preparing/nondeb-part/powerpc.xml
+++ b/en/preparing/nondeb-part/powerpc.xml
@@ -2,6 +2,7 @@
 <!-- $Id$ -->
 
 
+<!--
   <sect2 arch="powerpc"><title>Mac OS X Partitioning</title>
 
 <para>
@@ -37,3 +38,4 @@ file systems are supported by MacOS 9, Mac OS X and GNU/Linux.
 
 </para>
   </sect2>
+-->
diff --git a/en/preparing/nondeb-part/sparc.xml b/en/preparing/nondeb-part/sparc.xml
deleted file mode 100644
index 040feb008..000000000
--- a/en/preparing/nondeb-part/sparc.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-
-  <sect2 arch="sparc"><title>Partitioning from SunOS</title>
-
-<para>
-
-It's perfectly fine to partition from SunOS; in fact, if you intend to
-run both SunOS and &debian; on the same machine, it is recommended that
-you partition using SunOS prior to installing &debian;.  The Linux
-kernel understands Sun disk labels, so there are no problems there.
-SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS
-(SunOS), romfs or iso9660 (CDROM) partitions.
-
-</para>
-  </sect2>
-
-  <sect2 arch="sparc"><title>Partitioning from Linux or another OS</title>
-
-<para>
-
-Whatever system you are using to partition, make sure you create a
-<quote>Sun disk label</quote> on your boot disk.  This is the only kind of
-partition scheme that the OpenBoot PROM understands, and so it's the
-only scheme from which you can boot.  In <command>fdisk</command>, the
-<keycap>s</keycap> key is used to create Sun disk labels. You only need to do this
-on drives that do not already have a Sun disk label. If you are using a
-drive that was previously formatted using a PC (or other architecture) you
-must create a new disk label, or problems with the disk geometry will most
-likely occur.
-
-</para><para>
-
-You will probably be using <command>SILO</command> as your boot loader (the
-small program which runs the operating system kernel).
-<command>SILO</command> has certain requirements for partition sizes and
-location; see <xref linkend="partitioning"/>.
-
-</para>
-  </sect2>
diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml
index aa80fff54..13ba18ec8 100644
--- a/en/preparing/pre-install-bios-setup.xml
+++ b/en/preparing/pre-install-bios-setup.xml
@@ -16,7 +16,6 @@ hardware; it is most critically invoked during the bootstrap process
 
 &bios-setup-i386.xml;
 &bios-setup-powerpc.xml;
-&bios-setup-sparc.xml;
 &bios-setup-s390.xml;
 &bios-setup-arm.xml;
 
@@ -127,7 +126,7 @@ hardware; it is most critically invoked during the bootstrap process
     </para>
 
   </sect2>  
-  <sect2 arch="x86;powerpc" id="hardware-issues">
+  <sect2 arch="x86" id="hardware-issues">
   <title>Hardware Issues to Watch Out For</title>
 
    <formalpara arch="x86">
@@ -144,6 +143,7 @@ keyboard emulation</quote> or <quote>USB keyboard support</quote> options.
 </para>
    </formalpara>
 
+<!--
    <formalpara arch="powerpc">
    <title>Display-visibility on OldWorld Powermacs</title>
 
@@ -159,5 +159,7 @@ colors instead of <quote>thousands</quote> or <quote>millions</quote>.
 
 </para>
    </formalpara>
+-->
+
   </sect2>
  </sect1>