Remove alpha from English version of the manual

19 files changed, 7 insertions, 1195 deletions

diff --git a/en/boot-installer/accessibility.xml b/en/boot-installer/accessibility.xml
index a042e7c10..3ae0d15fc 100644
--- a/en/boot-installer/accessibility.xml
+++ b/en/boot-installer/accessibility.xml
@@ -7,7 +7,7 @@
 
 Some users may need specific support because of e.g. some visual
 impairment.
-<phrase arch="alpha;ia64;powerpc;x86">USB braille displays are detected
+<phrase arch="ia64;powerpc;x86">USB braille displays are detected
 automatically, but most other</phrase>
 <phrase arch="arm;hppa;mips;mipsel;sparc">Most</phrase>
 accessibility features have to be enabled manually.
@@ -19,7 +19,7 @@ loader interprets your keyboard as a QWERTY keyboard.
 
 </para>
 
-  <sect2 arch="alpha;ia64;powerpc;x86">
+  <sect2 arch="ia64;powerpc;x86">
   <title>USB Braille Displays</title>
 <para>
 
@@ -35,7 +35,7 @@ url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>.
 </para>
   </sect2>
 
-  <sect2 arch="alpha;ia64;powerpc;x86">
+  <sect2 arch="ia64;powerpc;x86">
   <title>Serial Braille Displays</title>
 <para>
 
diff --git a/en/boot-installer/alpha.xml b/en/boot-installer/alpha.xml
deleted file mode 100644
index d7a7a2ef7..000000000
--- a/en/boot-installer/alpha.xml
+++ /dev/null
@@ -1,454 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
- <sect2 arch="alpha" id="alpha-firmware">
- <title>Alpha Console Firmware</title>
-<para>
-
-Console firmware is stored in a flash ROM and started when an Alpha
-system is powered up or reset.  There are two different console
-specifications used on Alpha systems, and hence two classes of console
-firmware available:
-
-</para>
-
-<itemizedlist>
-<listitem><para>
-
-  <emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem
-  specification, which provides an operating environment for OpenVMS, Tru64
-  UNIX, and Linux operating systems.
-
-</para></listitem>
-<listitem><para>
-
-  <emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the
-  Advanced RISC Computing (ARC) specification, which provides an operating
-  environment for Windows NT.
-
-</para></listitem>
-</itemizedlist>
-
-<para>
-
-From the user's perspective, the most important difference between SRM
-and ARC is that the choice of console constrains the possible
-disk-partitioning scheme for the hard disk which you wish to boot off
-of.
-
-</para><para>
-
-ARC requires that you use an MS-DOS partition table (as created by
-<command>cfdisk</command>) for the boot disk.  Therefore MS-DOS partition
-tables are the <quote>native</quote> partition format when booting from
-ARC.  In fact, since AlphaBIOS contains a disk partitioning utility, you may
-prefer to partition your disks from the firmware menus before
-installing Linux.
-
-</para><para>
-
-Conversely, SRM is <emphasis>incompatible</emphasis><footnote>
-
-<para>
-Specifically, the bootsector format required by the Console Subsystem
-Specification conflicts with the placement of the DOS partition table.
-</para>
-
-</footnote> with MS-DOS partition tables. Since Tru64 Unix uses the BSD
-disklabel format, this is the <quote>native</quote> partition format for
-SRM installations.
-
-</para><para>
-
-GNU/Linux is the only operating system on Alpha that can be booted from
-both console types, but &debian; &release; only supports booting on
-SRM-based systems.  If you have an Alpha for which no version of SRM is
-available, if you will be dual-booting the system with Windows NT, or if
-your boot device requires ARC console support for BIOS initialization,
-you will not be able to use the &debian; &release; installer.  You can
-still run &debian; &release; on such systems by using other install
-media; for instance, you can install Debian woody with MILO and upgrade.
-
-</para><para>
-
-Because <command>MILO</command> is not available for any of the Alpha
-systems currently in production (as of February 2000), and because it
-is no longer necessary to buy an OpenVMS or Tru64 Unix license to have
-SRM firmware on your older Alpha, it is recommended that you use SRM
-when possible.
-
-</para><para>
-
-The following table summarizes available and supported system
-type/console combinations (see <xref linkend="alpha-cpus"/> for the
-system type names).  The word <quote>ARC</quote> below denotes any of the
-ARC-compliant consoles.
-
-</para><para>
-
-<informaltable><tgroup cols="2">
-<thead>
-<row>
-  <entry>System Type</entry>
-  <entry>Console Type Supported</entry>
-</row>
-</thead>
-
-<tbody>
-<row>
-  <entry>alcor</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>avanti</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>book1</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>cabriolet</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>dp264</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>eb164</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>eb64p</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>eb66</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>eb66p</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>jensen</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>lx164</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>miata</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>mikasa</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>mikasa-p</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>nautilus</entry>
-  <entry>ARC (see motherboard manual) or SRM</entry>
-</row><row>
-  <entry>noname</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>noritake</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>noritake-p</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>pc164</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>rawhide</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>ruffian</entry>
-  <entry>ARC only</entry>
-</row><row>
-  <entry>sable</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>sable-g</entry>
-  <entry>SRM only</entry>
-</row><row>
-  <entry>sx164</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>takara</entry>
-  <entry>ARC or SRM</entry>
-</row><row>
-  <entry>xl</entry>
-  <entry>ARC only</entry>
-</row><row>
-  <entry>xlt</entry>
-  <entry>ARC only</entry>
-</row>
-
-</tbody>
-</tgroup>
-</informaltable>
-
-</para><para>
-
-Generally, none of these consoles can boot Linux directly, so the
-assistance of an intermediary bootloader is required.  For the SRM
-console, <command>aboot</command>, a small, platform-independent
-bootloader, is used.  See the (unfortunately outdated) <ulink
-url="&url-srm-howto;">SRM HOWTO</ulink> for more information on
-<command>aboot</command>.
-
-</para><para condition="FIXME">
-
-The following paragraphs are from the woody install manual, and are
-included here for reference; they may be useful to someone at a later
-date when Debian supports MILO-based installs again.
-
-</para><para condition="FIXME">
-
-Generally, none of these consoles can boot Linux directly, so the
-assistance of an intermediary bootloader is required.  There are two
-mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>.
-
-</para><para condition="FIXME">
-
-<command>MILO</command> is itself a console, which replaces ARC or SRM in
-memory.  <command>MILO</command> can be booted from both ARC and SRM and is
-the only way to bootstrap Linux from the ARC console.
-<command>MILO</command> is platform-specific (a different <command>MILO</command>
-is needed for each system type) and exist only for those systems, for
-which ARC support is shown in the table above.  See also the
-(unfortunately outdated) <ulink url="&url-milo-howto;">MILO HOWTO</ulink>.
-
-</para><para condition="FIXME">
-
-<command>aboot</command> is a small, platform-independent bootloader, which
-runs from SRM only.  See the (also unfortunately outdated) <ulink
-url="&url-srm-howto;">SRM HOWTO</ulink> for more information on
-<command>aboot</command>.
-
-</para><para condition="FIXME">
-
-Thus, three scenarios are generally possible, depending on the
-system's console firmware and whether or not <command>MILO</command> is
-available:
-
-<informalexample><screen>
-SRM -&gt; aboot
-SRM -&gt; MILO
-ARC -&gt; MILO
-</screen></informalexample>
-
-Because <command>MILO</command> is not available for any of the Alpha
-systems currently in production (as of February 2000), and because it
-is no longer necessary to buy an OpenVMS or Tru64 Unix license to have
-SRM firmware on your older Alpha, it is recommended that you use SRM and
-<command>aboot</command> on new installations of GNU/Linux, unless you wish
-to dual-boot with Windows NT.
-
-</para><para>
-
-The majority of AlphaServers and all current server and workstation
-products contain both SRM and AlphaBIOS in their firmware.  For
-<quote>half-flash</quote> machines such as the various evaluation boards,
-it is possible to switch from one version to another by reflashing the
-firmware.  Also, once SRM is installed, it is possible to run
-ARC/AlphaBIOS from a floppy disk (using the <command>arc</command>
-command).  For the reasons mentioned above, we recommend switching to
-SRM before installing &debian;.
-
-</para><para>
-
-As on other architectures, you should install the newest available
-revision of the firmware<footnote>
-
-<para>
-Except on Jensen, where Linux is not supported on firmware versions
-newer than 1.7 &mdash; see <ulink url="&url-jensen-howto;"></ulink>
-for more information.
-</para>
-
-</footnote> before installing &debian;.
-For Alpha, firmware updates can be obtained from
-<ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>.
-
-</para>
- </sect2>
-
-
-  <sect2 arch="alpha"><title>Booting with TFTP</title>
-<para>
-
-In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput>
-prefix, and will be listed in the output of the <userinput>show dev</userinput> command,
-like this (edited slightly):
-
-<informalexample><screen>
-&gt;&gt;&gt; show dev
-ewa0.0.0.9.0               EWA0              08-00-2B-86-98-65
-ewb0.0.0.11.0              EWB0              08-00-2B-86-98-54
-ewc0.0.0.2002.0            EWC0              00-06-2B-01-32-B0
-</screen></informalexample>
-
-You first need to set the boot protocol:
-
-<informalexample><screen>
-&gt;&gt;&gt; set ewa0_protocols bootp
-</screen></informalexample>
-
-Then check the medium type is correct:
-
-<informalexample><screen>
-&gt;&gt;&gt; set ewa0_mode <replaceable>mode</replaceable>
-</screen></informalexample>
-
-You can get a listing of valid modes with <userinput>&gt;&gt;&gt;set ewa0_mode</userinput>.
-
-</para><para>
-
-Then, to boot from the first Ethernet interface, you would type:
-
-<informalexample><screen>
-&gt;&gt;&gt; boot ewa0 -flags ""
-</screen></informalexample>
-
-This will boot using the default kernel parameters as included in the
-netboot image.
-
-</para><para>
-
-If you wish to use a serial console, you <emphasis>must</emphasis>
-pass the <userinput>console=</userinput> parameter to the kernel.
-This can be done using the <userinput>-flags</userinput> argument to
-the SRM <userinput>boot</userinput> command.  The serial ports are
-named the same as their corresponding files in
-<userinput>/dev</userinput>.  Also, when specifying additional kernel
-parameters, you must repeat certain default options that are needed by
-the &d-i; images.  For example, to boot from <userinput>ewa0</userinput>
-and use a console on the first serial port, you would type:
-
-<informalexample><screen>
-&gt;&gt;&gt; boot ewa0 -flags &quot;root=/dev/ram ramdisk_size=16384 console=ttyS0&quot;
-</screen></informalexample>
-
-</para>
-  </sect2>
-
-  <sect2 arch="alpha"><title>Booting from CD-ROM with the SRM Console</title>
-<para>
-
-The &debian; install CDs include several preconfigured boot options for
-VGA and serial consoles.  Type
-
-<informalexample><screen>
-&gt;&gt;&gt; boot xxxx -flags 0
-</screen></informalexample>
-
-to boot using VGA console, where <replaceable>xxxx</replaceable> is your
-CD-ROM drive in SRM notation.  To use serial console on the first 
-serial device, type
-
-<informalexample><screen>
-&gt;&gt;&gt; boot xxxx -flags 1
-</screen></informalexample>
-
-and for console on the second serial port, type
-
-<informalexample><screen>
-&gt;&gt;&gt; boot xxxx -flags 2
-</screen></informalexample>
-
-</para>
-  </sect2>
-
-  <sect2 arch="alpha" condition="FIXME">
-  <title>Booting from CD-ROM with the ARC or AlphaBIOS Console</title>
-<para>
-
-To boot a CD-ROM from the ARC console, find your sub-architecture code
-name (see <xref linkend="alpha-cpus"/>), then enter
-<filename>\milo\linload.exe</filename> as the boot loader and
-<filename>\milo\<replaceable>subarch</replaceable></filename> (where
-<replaceable>subarch</replaceable> is the proper subarchitecture name)
-as the OS Path in the `OS Selection Setup' menu. Ruffians make an
-exception: You need to use <filename>\milo\ldmilo.exe</filename> as
-boot loader.
-
-</para>
-  </sect2>
-
-
-  <sect2 arch="alpha" condition="supports-floppy-boot">
-  <title>Booting from Floppies with the SRM Console</title>
-<para>
-
-At the SRM prompt (<prompt>&gt;&gt;&gt;</prompt>), issue the following
-command:
-
-<informalexample><screen>
-&gt;&gt;&gt; boot dva0 -flags 0
-</screen></informalexample>
-
-possibly replacing <filename>dva0</filename> with the actual device
-name.  Usually, <filename>dva0</filename> is the floppy; type
-
-<informalexample><screen>
-&gt;&gt;&gt; show dev
-</screen></informalexample>
-
-to see the list of devices (e.g., if you want to boot from a CD).
-Note that if you are booting via MILO, <command>-flags</command> argument
-is ignored, so you can just type <command>boot dva0</command>.
-If everything works OK, you will eventually see the Linux kernel boot.
-
-</para><para>
-
-If you want to specify kernel parameters when booting via
-<command>aboot</command>, use the following command:
-
-<informalexample><screen>
-&gt;&gt;&gt; boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments"
-</screen></informalexample>
-
-(typed on one line), substituting, if necessary, the actual SRM boot
-device name for <filename>dva0</filename>, the Linux boot device name for
-<filename>fd0</filename>, and the desired kernel parameters for
-<filename>arguments</filename>.
-
-</para><para>
-
-If you want to specify kernel parameters when booting via
-<command>MILO</command>, you will have to interrupt bootstrap once you get
-into MILO.  See <xref linkend="booting-from-milo"/>.
-</para>
-  </sect2>
-
-
-  <sect2 arch="alpha" condition="supports-floppy-boot">
-  <title>Booting from Floppies with the ARC or AlphaBIOS Console</title>
-
-<para>
-
-In the OS Selection menu, set <command>linload.exe</command> as the boot
-loader, and <command>milo</command> as the OS Path.  Bootstrap using the
-newly created entry.
-
-</para>
-  </sect2>
-
- <sect2 arch="alpha" condition="FIXME" id="booting-from-milo"><title>Booting with MILO</title>
-<para>
-
-MILO contained on the bootstrap media is configured to proceed straight
-to Linux automatically.  Should you wish to intervene, all you need is to
-press space during MILO countdown.
-
-</para><para>
-
-If you want to specify all the bits explicitly (for example, to supply
-additional parameters), you can use a command like this:
-
-<informalexample><screen>
-MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->
-</screen></informalexample>
-
-If you are booting from something other than a floppy, substitute
-<filename>fd0</filename> in the above example with the appropriate device name
-in Linux notation.  The <command>help</command> command would give you a brief
-MILO command reference.
-
-</para>
- </sect2>
diff --git a/en/boot-installer/boot-installer.xml b/en/boot-installer/boot-installer.xml
index 057d730f9..f5f6739c6 100644
--- a/en/boot-installer/boot-installer.xml
+++ b/en/boot-installer/boot-installer.xml
@@ -5,7 +5,7 @@
 
 <!-- Include only archs that are documented to avoid build-errors -->
 <!-- The arch="..." condition can be deleted when al archs are present -->
- <sect1 arch="alpha;arm;x86;ia64;mips;mipsel;s390;powerpc;sparc">
+ <sect1 arch="arm;x86;ia64;mips;mipsel;s390;powerpc;sparc">
  <title>Booting the Installer on &arch-title;</title>
 
 <!-- This info is so architecture dependent, that I have turned the   -->
@@ -30,7 +30,6 @@ For information on how to boot the graphical installer, see
 
 </para></note>
 
-&boot-installer-alpha.xml;
 &boot-installer-arm.xml;
 <!-- &boot-installer-hppa.xml; -->
 &boot-installer-x86.xml;
diff --git a/en/boot-installer/parameters.xml b/en/boot-installer/parameters.xml
index 0c091141a..d99bc044b 100644
--- a/en/boot-installer/parameters.xml
+++ b/en/boot-installer/parameters.xml
@@ -416,7 +416,7 @@ disable that authentication.
 </para></listitem>
 </varlistentry>
 
-<varlistentry arch="alpha;mips;mipsel">
+<varlistentry arch="mips;mipsel">
 <term>ramdisk_size</term>
 <listitem><para>
 
diff --git a/en/hardware/accessibility.xml b/en/hardware/accessibility.xml
index ccb27947e..dedd68d41 100644
--- a/en/hardware/accessibility.xml
+++ b/en/hardware/accessibility.xml
@@ -1,7 +1,7 @@
 <!-- retain these comments for translator revision tracking -->
 <!-- $Id$ -->
 
-  <sect2 id="braille-displays" arch="alpha;ia64;powerpc;x86">
+  <sect2 id="braille-displays" arch="ia64;powerpc;x86">
   <title>Braille Displays</title>
 <para>
 
diff --git a/en/hardware/hardware-supported.xml b/en/hardware/hardware-supported.xml
index f25468c63..9daa55afd 100644
--- a/en/hardware/hardware-supported.xml
+++ b/en/hardware/hardware-supported.xml
@@ -55,13 +55,6 @@ variations of each architecture known as <quote>flavors</quote>.
   <entry></entry>
 </row>
 
-<row arch="alpha">
-  <entry>DEC Alpha</entry>
-  <entry>alpha</entry>
-  <entry></entry>
-  <entry></entry>
-</row>
-
 <row>
   <entry morerows="4">ARM</entry>
   <entry morerows="4">armel</entry>
@@ -194,7 +187,6 @@ as well.
   </sect2>
 
 <!-- supported cpu docs -->
-&supported-alpha.xml;
 &supported-amd64.xml;
 &supported-arm.xml;
 &supported-hppa.xml;
diff --git a/en/hardware/installation-media.xml b/en/hardware/installation-media.xml
index 541b506cb..d8d938ec5 100644
--- a/en/hardware/installation-media.xml
+++ b/en/hardware/installation-media.xml
@@ -61,15 +61,6 @@ on using CD-ROMs with Linux.
 USB CD-ROM drives are also supported, as are FireWire devices that
 are supported by the ohci1394 and sbp2 drivers.
 
-</para><para arch="alpha">
-
-Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long
-as the controller is supported by the SRM console.  This rules out many
-add-on controller cards, but most integrated IDE and SCSI chips and
-controller cards that were provided by the manufacturer can be expected
-to work.  To find out whether your device is supported from the SRM
-console, see the <ulink url="&url-srm-howto;">SRM HOWTO</ulink>.
-
 </para><para arch="arm">
 
 IDE/ATAPI CD-ROMs are supported on all ARM machines.
@@ -218,15 +209,6 @@ IDE systems (such as the UltraSPARC 5) are also supported. See
 <ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink>
 for more information on SPARC hardware supported by the Linux kernel.
 
-</para><para arch="alpha">
-
-Any storage system supported by the Linux kernel is also supported by
-the boot system.  This includes both SCSI and IDE disks.  Note, however,
-that on many systems, the SRM console is unable to boot from IDE drives,
-and the Jensen is unable to boot from floppies.  (see
-<ulink url="&url-jensen-howto;"></ulink>
-for more information on booting the Jensen)
-
 </para><para arch="powerpc">
 
 Any storage system supported by the Linux kernel is also supported by
diff --git a/en/hardware/supported/alpha.xml b/en/hardware/supported/alpha.xml
deleted file mode 100644
index 3504e7f84..000000000
--- a/en/hardware/supported/alpha.xml
+++ /dev/null
@@ -1,457 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-
-  <sect2 arch="alpha" id="alpha-cpus"><title>CPU, Main Boards, and Video Support</title>
-<para>
-
-Complete information regarding supported DEC Alphas can be found at
-<ulink url="&url-alpha-howto;">Linux Alpha HOWTO</ulink>.  The
-purpose of this section is to describe the systems supported
-by the boot disks.
-
-</para><para>
-
-Alpha machines are subdivided into different system types because there
-are a number of generations of motherboard and supporting chipsets.
-Different systems (<quote>sub-architectures</quote>) often have radically
-different engineering and capabilities.  Therefore, the process of
-installing and, more to the point, booting, can vary from system to system.
-
-</para><para>
-
-The following table lists the system types supported by the Debian
-installation system.  The table also indicates the <emphasis>code
-name</emphasis> for these system types.  You'll need to know this code
-name when you actually begin the installation process:
-
-</para>
-
-<informaltable>
-<tgroup cols="4">
-<colspec colname="c1"/>
-<colspec colname="c2"/>
-<colspec colname="c3"/>
-<colspec colname="c4"/>
-<thead>
-<row>
-  <entry namest="c1" nameend="c2">Hardware Type</entry>
-  <entry>Aliases</entry><entry>MILO image</entry>
-</row>
-</thead>
-
-<tbody>
-<row>
-  <entry morerows="3">ALCOR</entry>
-  <entry>AlphaStation 500 5/266.300</entry>
-  <entry>Maverick</entry>
-  <entry>alcor</entry>
-</row><row>
-  <entry>AlphaStation 500 5/333...500</entry>
-  <entry>Bret</entry>
-  <entry>alcor</entry>
-</row><row>
-  <entry>AlphaStation 600/266...300</entry>
-  <entry>Alcor</entry>
-  <entry>alcor</entry>
-</row><row>
-  <entry>AlphaStation 600/300...433</entry>
-  <entry>XLT</entry>
-  <entry>xlt</entry>
-</row>
-
-<row>
-  <entry>BOOK1</entry>
-  <entry>AlphaBook1 (laptop)</entry>
-  <entry>Alphabook1/Burns</entry>
-  <entry>book1</entry>
-</row>
-
-<row>
-  <entry morerows="7">AVANTI</entry>
-  <entry>AlphaStation 200 4/100...166</entry>
-  <entry>Mustang</entry>
-  <entry>avanti</entry>
-</row><row>
-  <entry>AlphaStation 200 4/233</entry>
-  <entry>Mustang+</entry>
-  <entry>avanti</entry>
-</row><row>
-  <entry>AlphaStation 205 4/133...333</entry>
-  <entry>LX3</entry>
-  <entry>avanti</entry>
-</row><row>
-  <entry>AlphaStation 250 4/300</entry>
-  <entry>M3+</entry>
-  <entry>avanti</entry>
-</row><row>
-  <entry>AlphaStation 255 4/133...333</entry>
-  <entry>LX3+</entry>
-  <entry>avanti</entry>
-</row><row>
-  <entry>AlphaStation 300 4/266</entry>
-  <entry>Melmac</entry>
-  <entry>avanti</entry>
-</row><row>
-  <entry>AlphaStation 400 4/166</entry>
-  <entry>Chinet</entry>
-  <entry>avanti</entry>
-</row><row>
-  <entry>AlphaStation 400 4/233...300</entry>
-  <entry>Avanti</entry>
-  <entry>avanti</entry>
-</row>
-
-<row>
-  <entry morerows="3">EB164</entry>
-  <entry>AlphaPC164</entry>
-  <entry>PC164</entry>
-  <entry>pc164</entry>
-</row><row>
-  <entry>AlphaPC164-LX</entry>
-  <entry>LX164</entry>
-  <entry>lx164</entry>
-</row><row>
-  <entry>AlphaPC164-SX</entry>
-  <entry>SX164</entry>
-  <entry>sx164</entry>
-</row><row>
-  <entry>EB164</entry>
-  <entry>EB164</entry>
-  <entry>eb164</entry>
-</row>
-
-<row>
-  <entry morerows="2">EB64+</entry>
-  <entry>AlphaPC64</entry>
-  <entry>Cabriolet</entry>
-  <entry>cabriolet</entry>
-</row><row>
-  <entry>AlphaPCI64</entry>
-  <entry>Cabriolet</entry>
-  <entry>cabriolet</entry>
-</row><row>
-  <entry>EB64+</entry>
-  <entry>EB64+</entry>
-  <entry>eb64p</entry>
-</row>
-
-<row>
-  <entry morerows="1">EB66</entry>
-  <entry>EB66</entry>
-  <entry>EB66</entry>
-  <entry>eb66</entry>
-</row><row>
-  <entry>EB66+</entry>
-  <entry>EB66+</entry>
-  <entry>eb66p</entry>
-</row>
-
-<row>
-  <entry morerows="2">JENSEN</entry>
-  <entry>DEC 2000 Model 300(S)</entry>
-  <entry>Jensen</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>DEC 2000 Model 500</entry>
-  <entry>Culzen</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>DECpc 150</entry>
-  <entry>Jensen</entry>
-  <entry>N/A</entry>
-</row>
-
-<row>
-  <entry morerows="7">MIATA</entry>
-  <entry>Personal WorkStation 433a</entry>
-  <entry>Miata</entry>
-  <entry>miata</entry>
-</row><row>
-  <entry>Personal WorkStation 433au</entry>
-  <entry>Miata</entry>
-  <entry>miata</entry>
-</row><row>
-  <entry>Personal WorkStation 466au</entry>
-  <entry>Miata</entry>
-  <entry>miata</entry>
-</row><row>
-  <entry>Personal WorkStation 500a</entry>
-  <entry>Miata</entry>
-  <entry>miata</entry>
-</row><row>
-  <entry>Personal WorkStation 500au</entry>
-  <entry>Miata</entry>
-  <entry>miata</entry>
-</row><row>
-  <entry>Personal WorkStation 550au</entry>
-  <entry>Miata</entry>
-  <entry>miata</entry>
-</row><row>
-  <entry>Personal WorkStation 600a</entry>
-  <entry>Miata</entry>
-  <entry>miata</entry>
-</row><row>
-  <entry>Personal WorkStation 600au</entry>
-  <entry>Miata</entry>
-  <entry>miata</entry>
-</row>
-
-<row>
-  <entry morerows="3">MIKASA</entry>
-  <entry>AlphaServer 1000 4/200</entry>
-  <entry>Mikasa</entry>
-  <entry>mikasa</entry>
-</row><row>
-  <entry>AlphaServer 1000 4/233..266</entry>
-  <entry>Mikasa+</entry>
-  <entry>mikasa</entry>
-</row><row>
-  <entry>AlphaServer 1000 5/300</entry>
-  <entry>Mikasa-Pinnacle</entry>
-  <entry>mikasa</entry>
-</row><row>
-  <entry>AlphaServer 1000 5/300</entry>
-  <entry>Mikasa-Primo</entry>
-  <entry>mikasa</entry>
-</row>
-
-<row>
-  <entry morerows="1">NAUTILUS</entry>
-  <entry>UP1000</entry>
-  <entry>Nautilus</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>UP1100</entry>
-  <entry>Galaxy-Train/Nautilus Jr.</entry>
-  <entry>N/A</entry>
-</row>
-
-<row>
-  <entry morerows="1">NONAME</entry>
-  <entry>AXPpci33</entry>
-  <entry>Noname</entry>
-  <entry>noname</entry>
-</row><row>
-  <entry>UDB</entry>
-  <entry>Multia</entry>
-  <entry>noname</entry>
-</row>
-
-<row>
-  <entry morerows="6">NORITAKE</entry>
-  <entry>AlphaServer 1000A 4/233...266</entry>
-  <entry>Noritake</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer 1000A 5/300</entry>
-  <entry>Noritake-Pinnacle</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer 1000A 5/333...500</entry>
-  <entry>Noritake-Primo</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer 800 5/333...500</entry>
-  <entry>Corelle</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaStation 600 A</entry>
-  <entry>Alcor-Primo</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>Digital Server 3300</entry>
-  <entry>Corelle</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>Digital Server 3300R</entry>
-  <entry>Corelle</entry>
-  <entry>N/A</entry>
-</row>
-
-<row>
-  <entry>PLATFORM 2000</entry>
-  <entry>P2K</entry>
-  <entry>P2K</entry>
-  <entry>p2k</entry>
-</row>
-
-<row>
-  <entry morerows="4">RAWHIDE</entry>
-  <entry>AlphaServer 1200 5/xxx</entry>
-  <entry>Tincup/DaVinci</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer 4000 5/xxx</entry>
-  <entry>Wrangler/Durango</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer 4100 5/xxx</entry>
-  <entry>Dodge</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>Digital Server 5300</entry>
-  <entry>Tincup/DaVinci</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>Digital Server 7300</entry>
-  <entry>Dodge</entry>
-  <entry>N/A</entry>
-</row>
-
-<row>
-  <entry morerows="5">RUFFIAN</entry>
-  <entry>DeskStation AlphaPC164-UX</entry>
-  <entry>Ruffian</entry>
-  <entry>ruffian</entry>
-</row><row>
-  <entry>DeskStation RPL164-2</entry>
-  <entry>Ruffian</entry>
-  <entry>ruffian</entry>
-</row><row>
-  <entry>DeskStation RPL164-4</entry>
-  <entry>Ruffian</entry>
-  <entry>ruffian</entry>
-</row><row>
-  <entry>DeskStation RPX164-2</entry>
-  <entry>Ruffian</entry>
-  <entry>ruffian</entry>
-</row><row>
-  <entry>DeskStation RPX164-4</entry>
-  <entry>Ruffian</entry>
-  <entry>ruffian</entry>
-</row><row>
-  <entry>Samsung AlphaPC164-BX</entry>
-  <entry>Ruffian</entry>
-  <entry>ruffian</entry>
-</row>
-
-<row>
-  <entry morerows="3">SABLE</entry>
-  <entry>AlphaServer 2000 4/xxx</entry>
-  <entry>Demi-Sable</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer 2000 5/xxx</entry>
-  <entry>Demi-Gamma-Sable</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer 2100 4/xxx</entry>
-  <entry>Sable</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer 2100 5/xxx</entry>
-  <entry>Gamma-Sable</entry>
-  <entry>N/A</entry>
-</row>
-
-<row>
-  <entry>TAKARA</entry>
-  <entry>21164 PICMG SBC</entry>
-  <entry>Takara</entry>
-  <entry>takara</entry>
-</row>
-
-<row>
-  <entry morerows="3">TITAN</entry>
-  <entry>AlphaServer DS15</entry>
-  <entry>HyperBrick2</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer DS25</entry>
-  <entry>Granite</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer ES45</entry>
-  <entry>Privateer</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>UNKNOWN</entry>
-  <entry>Yukon</entry>
-  <entry>N/A</entry>
-</row>
-
-<row>
-  <entry morerows="12">TSUNAMI</entry>
-  <entry>AlphaServer DS10</entry>
-  <entry>Webbrick</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer DS10L</entry>
-  <entry>Slate</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer DS20</entry>
-  <entry>Catamaran/Goldrush</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer DS20E</entry>
-  <entry>Goldrack</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer DS20L</entry>
-  <entry>Shark</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer ES40</entry>
-  <entry>Clipper</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>DP264</entry>
-  <entry>DP264</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>SMARTengine 21264 PCI/ISA SBC</entry>
-  <entry>Eiger</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>UNKNOWN</entry>
-  <entry>Warhol</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>UNKNOWN</entry>
-  <entry>Windjammer</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>UP2000</entry>
-  <entry>Swordfish</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>XP1000</entry>
-  <entry>Monet/Brisbane</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>XP900</entry>
-  <entry>Webbrick</entry>
-  <entry>N/A</entry>
-</row>
-
-<row>
-  <entry morerows="1">WILDFIRE</entry>
-  <entry>AlphaServer GS160</entry>
-  <entry>Wildfire</entry>
-  <entry>N/A</entry>
-</row><row>
-  <entry>AlphaServer GS320</entry>
-  <entry>Wildfire</entry>
-  <entry>N/A</entry>
-</row>
-
-<row>
-  <entry>XL</entry>
-  <entry>XL-233...266</entry>
-  <entry>XL</entry>
-  <entry>xl</entry>
-</row>
-
-</tbody></tgroup></informaltable>
-
-<para>
-
-It is believed that Debian &releasename; supports installing on all
-alpha sub-architectures with the exception of the ARC-only Ruffian and
-XL sub-architectures and the Titan subarchitecture, which requires a
-change to the kernel compile options.
-
-</para>
-  </sect2>
diff --git a/en/install-methods/download/alpha.xml b/en/install-methods/download/alpha.xml
deleted file mode 100644
index 280187987..000000000
--- a/en/install-methods/download/alpha.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-
-   <sect3 arch="alpha"><title>Alpha Installation Files</title>
-<para>
-
-If you choose to boot from ARC console firmware using
-<command>MILO</command>, you will also need to prepare a disk
-containing <command>MILO</command> and <command>LINLOAD.EXE</command>
-from the provided disk images. See <xref linkend="alpha-firmware"/>
-for more information on Alpha
-firmware and boot loaders. The floppy images can be found in the
-<filename>MILO</filename> directory as
-<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>.
-
-</para><para>
-
-Unfortunately, these <command>MILO</command> images could not be
-tested and might not work for all subarchitectures. If you find it
-doesn't work for you, try copying the appropriate
-<command>MILO</command> binary onto the floppy
-(<ulink url="&disturlftp;main/disks-alpha/current/MILO/"></ulink>).
-Note that those <command>MILO</command>s don't support ext2 <quote>sparse
-superblocks</quote>, so you can't use them to load kernels from newly
-generated ext2 file systems. As a workaround, you can put your kernel
-onto the FAT partition next to the <command>MILO</command>.
-
-</para><para>
-
-<command>MILO</command> binaries are platform-specific.  See
-<xref linkend="alpha-cpus"/> to determine the appropriate
-<command>MILO</command> image for your Alpha platform.
-
-</para>
-   </sect3>
diff --git a/en/install-methods/downloading-files.xml b/en/install-methods/downloading-files.xml
index 7be75fd04..8ec61a025 100644
--- a/en/install-methods/downloading-files.xml
+++ b/en/install-methods/downloading-files.xml
@@ -26,7 +26,6 @@ The installation images are located on each Debian mirror in the directory
 lists each image and its purpose.
 </para>
 
-&download-alpha.xml;
 &download-arm.xml;
 &download-powerpc.xml;
 
diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml
index eff4340da..ea56b6889 100644
--- a/en/install-methods/install-tftp.xml
+++ b/en/install-methods/install-tftp.xml
@@ -38,23 +38,6 @@ For PowerPC, if you have a NewWorld Power Macintosh machine, it is a
 good idea to use DHCP instead of BOOTP.  Some of the latest machines
 are unable to boot using BOOTP.
 
-</para><para arch="alpha">
-
-Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM
-console will <emphasis>not</emphasis> use RARP to obtain its IP
-address, and therefore you must use BOOTP for net booting your
-Alpha<footnote>
-
-<para>
-Alpha systems can also be net-booted using the DECNet MOP (Maintenance
-Operations Protocol), but this is not covered here.  Presumably, your
-local OpenVMS operator will be happy to assist you should you have
-some burning need to use MOP to boot Linux on your Alpha.
-</para>
-
-</footnote>. You can also enter the IP configuration for network
-interfaces directly in the SRM console.
-
 </para><para arch="hppa">
 
 Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP.
@@ -221,22 +204,6 @@ to <command>tftpd</command> as the filename to boot.
 
 </para>
 
-   <sect3 arch="alpha">
-   <title>Alpha TFTP Booting</title>
-<para>
-On Alpha, you must specify the filename (as a relative path to the
-boot image directory) using the <userinput>-file</userinput> argument
-to the SRM <userinput>boot</userinput> command, or by setting the
-<userinput>BOOT_FILE</userinput> environment variable.  Alternatively,
-the filename can be given via BOOTP (in ISC <command>dhcpd</command>,
-use the <userinput>filename</userinput> directive).  Unlike Open
-Firmware, there is <emphasis>no default filename</emphasis> on SRM, so
-you <emphasis>must</emphasis> specify a filename by either one of
-these methods.
-
-</para>
-   </sect3>
-
    <sect3 arch="sparc">
    <title>SPARC TFTP Booting</title>
 <para>
diff --git a/en/partitioning/partition-programs.xml b/en/partitioning/partition-programs.xml
index 778e00a48..d77cefe85 100644
--- a/en/partitioning/partition-programs.xml
+++ b/en/partitioning/partition-programs.xml
@@ -128,7 +128,6 @@ includes steps you should take if you are sharing your disk with MacOS.
 
 </para>
 
-&partition-alpha.xml;
 &partition-hppa.xml;
 &partition-x86.xml;
 &partition-ia64.xml;
diff --git a/en/partitioning/partition/alpha.xml b/en/partitioning/partition/alpha.xml
deleted file mode 100644
index 6cca8373a..000000000
--- a/en/partitioning/partition/alpha.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-
-  <sect2 arch="alpha"><title>Partitioning for &arch-title;</title>
-<para>
-
-Booting Debian from the SRM console (the only disk boot method supported
-by &releasename;) requires you to have a BSD disk label, not a DOS
-partition table, on your boot disk.  (Remember, the SRM boot block is
-incompatible with MS-DOS partition tables &mdash; see
-<xref linkend="alpha-firmware"/>.)  As a result, <command>partman</command>
-creates BSD disk labels when running on &architecture;, but if your disk
-has an existing DOS partition table the existing partitions will need to be
-deleted before <command>partman</command> can convert it to use a disk label.
-
-</para><para>
-
-If you have chosen to use <command>fdisk</command> to partition your
-disk, and the disk that you have selected for partitioning does not
-already contain a BSD disk label, you must use the <quote>b</quote>
-command to enter disk label mode.
-
-</para><para>
-
-Unless you wish to use the disk you are partitioning from Tru64 Unix
-or one of the free 4.4BSD-Lite derived operating systems (FreeBSD,
-OpenBSD, or NetBSD), you should <emphasis>not</emphasis> create the
-third partition as a <quote>whole disk</quote> partition (i.e. with
-start and end sectors to span the whole disk), as this renders the
-disk incompatible with the tools used to make it bootable with aboot.
-This means that the disk configured by the installer for use as the
-Debian boot disk will be inaccessible to the operating systems mentioned
-earlier.
-
-</para><para>
-
-Also, because <command>aboot</command> is written to the first few
-sectors of the disk (currently it occupies about 70 kilobytes, or 150
-sectors), you <emphasis>must</emphasis> leave enough empty space at
-the beginning of the disk for it.  In the past, it was suggested that
-you make a small partition at the beginning of the disk, to be left
-unformatted.  For the same reason mentioned above, we now suggest that
-you do not do this on disks that will only be used by GNU/Linux.  When
-using <command>partman</command>, a small partition will still be
-created for <command>aboot</command> for convenience reasons.
-
-</para><para condition="FIXME">
-
-For ARC installations, you should make a small FAT partition at the
-beginning of the disk to contain <command>MILO</command> and
-<command>linload.exe</command> &mdash; 5 megabytes should be sufficient, see
-<xref linkend="non-debian-partitioning"/>. Unfortunately, making FAT
-file systems from the menu is not yet supported, so you'll have to do
-it manually from the shell using <command>mkdosfs</command> before
-attempting to install the boot loader.
-
-</para>
-  </sect2>
diff --git a/en/preparing/needed-info.xml b/en/preparing/needed-info.xml
index 8dfffbd71..7daf77b3c 100644
--- a/en/preparing/needed-info.xml
+++ b/en/preparing/needed-info.xml
@@ -52,19 +52,13 @@ 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;alpha;sparc;mips;mipsel">
+ <itemizedlist arch="x86;sparc;mips;mipsel">
 <listitem arch="x86"><para>
 
 <ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>
 
 </para></listitem>
 
-<listitem arch="alpha"><para>
-
-<ulink url="&url-alpha-faq;">Linux/Alpha FAQ</ulink>
-
-</para></listitem>
-
 <listitem arch="sparc"><para>
 
 <ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink>
diff --git a/en/preparing/non-debian-partitioning.xml b/en/preparing/non-debian-partitioning.xml
index 3ebf133cc..2ac423346 100644
--- a/en/preparing/non-debian-partitioning.xml
+++ b/en/preparing/non-debian-partitioning.xml
@@ -24,10 +24,6 @@ If you already have an operating system on your system
 (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, &hellip;)
 </phrase>
 
-<phrase arch="alpha">
-(Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, &hellip;)
-</phrase>
-
 <phrase arch="s390">
 (VM, z/OS, OS/390, &hellip;)
 </phrase>
@@ -184,7 +180,6 @@ Boot the Debian installer to continue installing Debian.
 
 </para>
 
-&nondeb-part-alpha.xml;
 &nondeb-part-x86.xml;
 &nondeb-part-sparc.xml;
 &nondeb-part-powerpc.xml;
diff --git a/en/preparing/nondeb-part/alpha.xml b/en/preparing/nondeb-part/alpha.xml
deleted file mode 100644
index 2743367ba..000000000
--- a/en/preparing/nondeb-part/alpha.xml
+++ /dev/null
@@ -1,83 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-
-  <sect2 arch="alpha"><title>Partitioning in Tru64 UNIX</title>
-<para>
-
-Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly
-known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk
-label</quote>, which allows for up to eight partitions per disk drive.  The
-partitions are numbered <quote>1</quote> through to <quote>8</quote> in
-Linux and <quote>lettered</quote> <quote>a</quote> through to
-<quote>h</quote> in UNIX.  Linux kernels 2.2 and higher always correspond
-<quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote>
-and so on.  For example, <filename>rz0e</filename> in Tru64 UNIX would most
-likely be called <filename>sda5</filename> in Linux.
-
-</para><para>
-
-Partitions in a Tru64 disk label may overlap.  Moreover, if this disk
-will be used from Tru64, the <quote>c</quote> partition is required to span
-the entire disk (thus overlapping all other non-empty partitions).  Under
-Linux this makes <filename>sda3</filename> identical to
-<filename>sda</filename> (<filename>sdb3</filename> to
-<filename>sdb</filename>, if present, and so on).  However, the partman
-partitioning tool used by &d-i; cannot handle overlapping partitions at
-present.  As a result, it is currently not recommended to share disks
-between Tru64 and Debian.  Partitions on Tru64 disks can be mounted
-under Debian after installation has been completed.
-
-</para><para>
-
-Another conventional requirement is for the <quote>a</quote> partition to
-start from the beginning of the disk, so that it always includes the boot
-block with the disk label. If you intend to boot Debian from that disk, you
-need to size it at least 2MB to fit aboot and perhaps a kernel.
-Note that this partition is only required for compatibility; you must
-not put a file system onto it, or you'll destroy data.
-
-</para><para>
-
-It is possible, and indeed quite reasonable, to share a swap partition
-between UNIX and Linux.  In this case it will be needed to do a
-<command>mkswap</command> on that partition every time the system is rebooted
-from UNIX into Linux, as UNIX will damage the swap signature.  You may
-want to run <command>mkswap</command> from the Linux start-up scripts before
-adding swap space with <command>swapon -a</command>.
-
-</para><para>
-
-If you want to mount UNIX partitions under Linux, note that Digital UNIX
-can use two different file system types, UFS and AdvFS, of which Linux
-only understands the former.
-
-</para>
-  </sect2>
-
-  <sect2 arch="alpha"><title>Partitioning in Windows NT</title>
-
-<para>
-
-Windows NT uses the PC-style partition table.  If you are manipulating
-existing FAT or NTFS partitions, it is recommended that you use the
-native Windows NT tools (or, more conveniently, you can also
-repartition your disk from the AlphaBIOS setup menu).  Otherwise, it
-is not really necessary to partition from Windows; the Linux
-partitioning tools will generally do a better job.  Note that when you
-run NT, the Disk Administrator may offer to write a <quote>harmless
-signature</quote> on non-Windows disks if you have any.
-<emphasis>Never</emphasis> let it do that, as this signature will destroy
-the partition information.
-
-</para><para>
-
-If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you
-will need a (small) FAT partition for MILO.  5 MB is quite
-sufficient.  If Windows NT is installed, its 6 MB bootstrap partition
-can be employed for this purpose.  Debian &releasename; does not support
-installing MILO.  If you already have MILO installed on your system, or
-install MILO from other media, Debian can still be booted from ARC.
-
-</para>
-  </sect2>
diff --git a/en/using-d-i/components.xml b/en/using-d-i/components.xml
index 283516245..438b36183 100644
--- a/en/using-d-i/components.xml
+++ b/en/using-d-i/components.xml
@@ -145,7 +145,6 @@ linkend="boot-dev-select-sun"/>.</phrase>
 </para>
 
 &module-os-prober.xml;
-&module-alpha-aboot-installer.xml;
 &module-hppa-palo-installer.xml;
 &module-x86-grub-installer.xml;
 &module-x86-lilo-installer.xml;
diff --git a/en/using-d-i/modules/alpha/aboot-installer.xml b/en/using-d-i/modules/alpha/aboot-installer.xml
deleted file mode 100644
index 1a40905d0..000000000
--- a/en/using-d-i/modules/alpha/aboot-installer.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-  <sect3 arch="alpha">
-  <title>Install <command>aboot</command> on a Hard Disk</title>
-<para>
-
-If you have booted from SRM and you select this option, the installer
-will write <command>aboot</command> to the first sector of the disk on
-which you installed Debian.  Be <emphasis>very</emphasis> careful &mdash; it
-is <emphasis>not</emphasis> possible to boot multiple operating
-systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix
-a.k.a. Tru64 Unix, or OpenVMS) from the same disk.  If you also have a
-different operating system installed on the disk where you have
-installed Debian, you will have to boot GNU/Linux from a floppy
-instead.
-
-</para>
-  </sect3>
diff --git a/en/using-d-i/modules/partman.xml b/en/using-d-i/modules/partman.xml
index afddd78a6..f266da65c 100644
--- a/en/using-d-i/modules/partman.xml
+++ b/en/using-d-i/modules/partman.xml
@@ -157,12 +157,6 @@ for the EFI boot loader.
 There is also an additional menu item in the formatting menu to manually
 set up a partition as an EFI boot partition.
 
-</para><para arch="alpha">
-
-If you choose guided partitioning for your Alpha system, an
-additional, unformatted partition will be allocated at the beginning of
-your disk to reserve this space for the aboot boot loader.
-
 </para><para>
 
 After selecting a scheme, the next screen will show your new partition