Removal suggestions and changes by Helge Kreutzmann.

CVS version numbers english/ports/alpha/egcs-bugs.wml: 1.6 -> 1.7(DEAD) english/ports/alpha/glibc21-page.wml: 1.5 -> 1.6(DEAD) english/ports/alpha/port-status.wml: 1.9 -> 1.10 english/ports/alpha/faq/FAQ-1.html: 1.2 -> 1.3(DEAD) english/ports/alpha/faq/FAQ-10.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-11.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-12.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-13.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-14.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-15.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-16.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-17.html: 1.2 -> 1.3(DEAD) english/ports/alpha/faq/FAQ-18.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-19.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-2.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-3.html: 1.2 -> 1.3(DEAD) english/ports/alpha/faq/FAQ-4.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-5.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-6.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-7.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-8.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ-9.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/FAQ.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/alpha-sys.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/alphabios-howto.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/index.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-1.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-10.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-2.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-3.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-4.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-5.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-6.html: 1.2 -> 1.3(DEAD) english/ports/alpha/faq/milo-7.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-8.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo-9.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/milo.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/srm-1.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/srm-2.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/srm-3.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/srm-4.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/srm.html: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/otherformats/FAQ.dvi.gz: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/otherformats/FAQ.lyx.gz: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/otherformats/FAQ.ps.gz: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/otherformats/FAQ.sgml.gz: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/otherformats/FAQ.tex.gz: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/otherformats/FAQ.tgz: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/otherformats/FAQ.txt.gz: 1.1 -> 1.2(DEAD) english/ports/alpha/faq/otherformats/index.html: 1.1 -> 1.2(DEAD)
author: Frank Lichtenheld <djpig> 2004-04-15 20:28:55 +0000
committer: Frank Lichtenheld <djpig> 2004-04-15 20:28:55 +0000
commit: 4dbe170de7d7931109b309063fdd09abb48569bb (patch)
tree: a411312ec0b41546a4938d72783c375059ee7348 /english/ports/alpha
parent: d24dad9691b0b2a9a6ffd25d780c919b7c418490 (diff)
50 files changed, 19 insertions, 6340 deletions
diff --git a/english/ports/alpha/egcs-bugs.wml b/english/ports/alpha/egcs-bugs.wml
deleted file mode 100644
index bba699945c9..00000000000
--- a/english/ports/alpha/egcs-bugs.wml
+++ /dev/null
@@ -1,16 +0,0 @@
-#use wml::debian::template title="EGCS Optimiser Bug List"
-#include "$(ENGLISHDIR)/ports/alpha/menu.inc"
-
-<p>While trying to test out new binutils and egcs releases, it occurred
-to a few of us that we need to keep track of the packages that show the
-bugs in egcs and/or binutils.  So, here's a budding list...</p>
-
-<ul>
-<li><b>gs_5.10-1</b> - EGCS Optimiser bug.</li>
-<li><b>emacs20-any</b> - EGCS unknown bug (miscompiles emacs).</li>
-<li><b>nextaw_0.5.1-29</b> - EGCS Optimiser bug (Scrollbar.c: not even with -O but yes without it).</li>
-<li><b>postgresql_6.4.2-8</b> - EGCS Optimiser bug (miscompiles spinlock code).</li>
-<li><b>r-base_0.64.1-1</b> - EGCS Optimiser bug (src/main/dotcode.c).</li>
-<li><b>xpdf-0.80-5</b> - EGCS Optimiser bug (xpdf/Gfx.cc).</li>
-<li><b>xspread-3.1.1c-6</b> - EGCS Optimiser bug (xpsread-3.1.1c/interp.c).</li>
-</ul>
diff --git a/english/ports/alpha/faq/FAQ-1.html b/english/ports/alpha/faq/FAQ-1.html
deleted file mode 100644
index c7b6732776c..00000000000
--- a/english/ports/alpha/faq/FAQ-1.html
+++ /dev/null
@@ -1,471 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: What State Is Linux/Alpha In? </TITLE>
- <LINK HREF="FAQ-2.html" REL=next>
-
- <LINK HREF="FAQ.html#toc1" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-2.html">Next</A>
-Previous
-<A HREF="FAQ.html#toc1">Contents</A>
-<HR>
-<H2><A NAME="What State Is Linux/Alpha In"></A> <A NAME="s1">1. What State Is Linux/Alpha In? </A></H2>
-
-<P> Linux/Alpha is for real: pretty much everything is up and running:
-there is XFree86, LaTeX, ghostview, Mosaic, Emacs, gcc, C++, NFS,
-automounter, all sorts of shells, perl, python, Java, Tcl/Tk, scheme,
-apache HTTP server, and pretty much anything else that's freely
-available.  X11 works well on several video cards (see below).  Thanks
-to Dave Taylor and Linus Torvalds, there is now even a 
-<A HREF="ftp://ftp.digital.com/pub/DEC/Linux-Alpha/X11">Quake binary</A> for Linux/Alpha!
-Since April 1997, it is now also possible to run many Linux/x86
-binaries through the em86 emulator. (See section 
-<A HREF="FAQ-16.html#em86">em86</A>
-)
-The list of applications supported by em86 includes gems
-such as applix, netscape, and acrobat.  The emulator has been made
-available free of charge by Jim Paradis of Digital Semiconductor.
-<P>Linux/Alpha presently runs on most of the Alpha boxes that come with
-the PCI or EISA bus.  This excludes the old TURBOchannel based DEC
-3000 series of workstations.
-<P>
-<P>
-<H2><A NAME="ss1.1">1.1 Supported Drivers</A>
-</H2>
-
-<P><B>Drivers that are known to work</B> (let us known if there is something new):
-<UL>
-<LI> X11:  Almost all XFree86 drivers work on Linux/Alpha.  Perhaps the
-biggest missing feature is packed 24-bit support.  32bpp/depth 24
-works fine, though. <BR>
-The SVGA server on Alpha supports only a subset of the cards supported
-on Intel: Matrox and S3Virge are supported, but a number of older chipsets 
-are not.<BR>
-SuSE is actively involved with the developement of XFree. If you have a
-card that isn't supported yet, you may find a driver at their 
-<A HREF="http://www.suse.com/">website</A>. <BR>
-
-There are some development X servers available from Digital's FTP
-<A HREF="ftp://ftp.digital.com/pub/DEC/Linux-Alpha/X11">site</A>;
-you might check there if XFree86 doesn't work on your system. <BR>
-
-Commercial X-servers are available from MetroLink and XiGraphics.
-(See the section on commercial software.) You may need these if you have
-a very new graphics card.
-</LI>
-<LI> keyboard</LI>
-<LI> console (TGA, EGA+ or VGA+ compatible cards)</LI>
-<LI> selection (console mouse support)</LI>
-<LI> serial</LI>
-<LI> line-printer (centronics port)</LI>
-<LI> floppy</LI>
-<LI> SCSI: disks, CD-ROMs, and tapes seem to work fine.  Host adapters that
-are known to work:
-<UL>
-<LI>NCR/Symbios 53c810, 825, 875 (use the ncr53c8xx driver)</LI>
-<LI>aha1740 (on Jensen, at least)</LI>
-<LI>BusLogic (all cards ISA or PCI cards should work fine except
-for the Flashpoint; EISA cards may be flaky in older EISA systems).</LI>
-<LI>Qlogic ISP1020</LI>
-<LI>support for Adaptec cards has been problematic in the past,
-but is improving rapidly.</LI>
-</UL>
-
-</LI>
-<LI> ftape (QIC-80 tape drives): you'll need the
-<A HREF="ftp://ftp.azstarnet.com/pub/linux/axp/sys">BFD-based insmod</A> utility.</LI>
-<LI> IDE driver: disks and CD-ROMs (ATAPI) are known to work.</LI>
-<LI> Networking:
-<UL>
-<LI>Ethernet drivers: de4x5, de500, depca, ewrk3, ne2000.
-The following drivers are supposed to be working as well:
-<UL>
-<LI>Western Digital (aka SMC Elite) wd80x3</LI>
-<LI>SMC Ultra</LI>
-<LI>SMC EtherEZ</LI>
-<LI>3Com 3c503, 3c503/16, 3c509</LI>
-<LI>Cabletron e2100</LI>
-<LI>Hewlett Packard PC Lan  (model 27245, uses hp.c) </LI>
-<LI>Hewlett Packard PC Lan+ (model 27247 or 27252A, uses hp-plus.c) </LI>
-<LI>Ansel AC3200 EISA card.</LI>
-<LI>AMD PCnetPCI (79C970 and 79C970A) based Ethernet cards
-(LANCE32 driver).</LI>
-</UL>
-
-If you experience problems with one of these, you might want to drop
-a note to
-<A HREF="mailto:gpg109@rsphy1.anu.edu.au">Paul Gortmaker</A>.
-</LI>
-<LI>Other drivers: ppp, ibmtr (IBM token ring driver).
-</LI>
-<LI>ISDN: ICN 2B and ICN 4B cards (if you have problems with them,
-contact 
-<A HREF="mailto:tsbogend@bigbug.franken.de">Thomas        Bogendoerfer</A>).
-</LI>
-</UL>
-
-</LI>
-<LI> Cameras/Scanners: QuickCam (both grayscale and color
-versions).  HP ScanJet reportedly work.  Mustek flat
-scanners are supported, too (you may want to subscribe to the
-sane-devel mailing list in this case; send a mail containing
-"subscribe" to 
-<A HREF="mailto:sane-devel-request@listserv.azstarnet.com">sane-devel-request@listserv.azstarnet.com</A>).
-</LI>
-<LI> Sound cards: SoundBlaster compatible cards seem to work well.
-The Microsoft Sound System compatible card built into the
-<A HREF="http://www.annex.co.uk/systems/udb.html">UDB</A> is
-supported, too.
-</LI>
-<LI> Joystick: The joystick interface on a
-SoundBlaster16 (which is just a regular PC joystick port) is
-known to work with joystick-0.7.3 (as a module).  There were a
-few minor patches that had to be applied.  If you want it, send
-mail to 
-<A HREF="mailto:David.Mosberger@acm.org">David Mosberger</A>.  The "koules" game is known
-to work with the joystick.</LI>
-</UL>
-<P>
-<H2><A NAME="ss1.2">1.2 Known Bugs And Workarounds</A>
-</H2>
-
-<P>This section lists known bugs in Linux/Alpha and discusses how they
-can be avoided or worked around.  As things are under constant
-development, this section is rather volatile.  Just because it isn't
-listed here doesn't mean the problem isn't known already.  On the
-other hand, if you run a recent distribution, it's likely that most of
-the problems have been addressed already.  In any case, before sending
-mail off to 
-<A HREF="mailto:axp-list@redhat.com">axp-list</A>, be
-sure to check this section first.  If you discover a new
-problem/workaround, we would appreciate if you could send us a report
-(preferably in linuxdoc SGML format).
-<P>
-<DL>
-<P>
-<DT><B>Kernel hangs or panics when trying to mount root file system:</B><DD><P>The Linux
-kernel currently has <CODE>/dev/sda2</CODE> hardcoded as its default root
-file system.  Thus, if your root file system is on any other
-disk or partition, you will have to specify the boot
-option <CODE>root=/dev/</CODE><I>root-partition</I>.
-For example, if the root file system is on <CODE>/dev/hda1</CODE>,
-you'd specify <CODE>root=/dev/hda1</CODE>.
-<P>
-<DT><B>ELF <CODE>gdb</CODE> behaves odd w.r.t. shared functions.</B><DD><P>When
-using <CODE>gdb</CODE> on a dynamically linked binary, it is best
-to force eager resolution of dynamic symbols.  To do this,
-simply issue the command <CODE>set env
-LD_BIND_NOW=1</CODE> from within <CODE>gdb</CODE>.  Otherwise,
-you may see unexpected behavior when trying to step into
-or over a shared function.  The source of this problem is known,
-but nobody has had time yet to fix the problem.
-<P>
-<DT><B>Kernel reports 2.88MB floppy drive:</B><DD><P>On the Alphas, the kernel
-<EM>always</EM> reports floppy drives as having 2.88MB capacity
-even if a smaller capacity drive is installed.  This is nothing
-to worry about: normally, the floppy driver automatically
-detects and selects the correct capacity so everything will work
-fine.  The only exception to this rule is when formatting a
-new floppy disk.  To do this, you'll need to select the device
-name with the correct capacity.  For example, if the system
-has a 1.4MB drive, format <CODE>/dev/fd0H1440</CODE> instead of
-<CODE>/dev/fd0</CODE>.
-<P>
-<DT><B>Unaligned accesses:</B><DD><P>The Alpha, like all real RISC CPUs, requires that memory
-accesses are <EM>naturally aligned</EM>.  For example, reading
-a 4 byte integer from memory requires that the address of the
-integer be a multiple of 4.  Similarly, 8 byte integers need
-to start at an address that is a multiple of 8.  If the CPU
-attempts to access a word that is not properly aligned,
-the CPU will trap into the kernel and issue a warning message.
-The kernel will then go ahead and emulate the unaligned access
-so that the user-level process executes as if nothing had
-happened (except for a substantial slow-down due to the
-fault).
-<P>Typically, an unaligned fault message looks like this:
-<BLOCKQUOTE><CODE>
-<PRE>
-X(26738): unaligned trap at 000000012004b6f0: 00000001401b20ca 28 1
-        
-</PRE>
-</CODE></BLOCKQUOTE>
-
-What this means is that the process executing command <CODE>X</CODE>
-(the X11 server) with process id 26738 caused an
-unaligned fault accessing address 0x1401b20ca.  This access
-was performed by the instruction located at address
-0x12004b6f0.  The other numbers are less important, but if
-you check the kernel sources, you'll find that they tell you
-more info on what kind of instruction caused the fault (e.g.,
-a load vs. a store).
-<P>You do not need to be overly alarmed when seeing such a message.
-The program causing the faults will work <EM>correctly</EM>.
-Eventually, all unaligned accesses will be fixed, but
-in the meantime, just ignore these messages (if you're a programmer,
-please take a minute and fix the source of the unaligned access
-instead...).
-<P>
-<DT><B>Linker issues <CODE>warning: using multiple gp values</CODE> message:</B><DD><P>This is a warning message that
-is often issued by the linker when building a large program.
-Unless you're into low-level hacking, you don't want to know what
-it means. The good news is: you can safely ignore this message and
-this warning will be optional in the future.
-<P>
-<DT><B>IDE driver causes time to run slow:</B><DD><P>The default configuration of the
-IDE driver disables interrupts for extended periods of time.  This
-causes the kernel to loose timer interrupts and as a result, time
-runs slow.  To avoid this, use the following command on all of the
-IDE drives in your system:
-<BLOCKQUOTE><CODE>
-<PRE>
-                hdparm -u 1 /dev/hd?
-        
-</PRE>
-</CODE></BLOCKQUOTE>
-
-This reconfigures the IDE driver to reenable interrupts as quickly
-as possible.
-<P>
-<DT><B><CODE>minlabel</CODE>,<CODE>fdisk</CODE> fail to update kernel partition table:</B><DD><P>Do not attempt to use a system after changing the partition
-table.  Even if <CODE>minlabel</CODE> and/or <CODE>fdisk</CODE> show the correct
-values you <EM>will</EM> have to reboot the machine before the new
-values take effect.
-<P>
-<DT><B><CODE>tar xvMf /dev/fd0</CODE> hangs.</B><DD><P>(This bug should not occur
-on GNU libc-based systems.)  Due to a bug in the
-malloc package that comes with libc-0.43, multivolume tar
-archives do not work. Recompile and link with the gmalloc
-standalone package, or get an updated libc.
-<P>
-<DT><B>Clock seems to be off by 20 years:</B><DD><P>This is not really a bug, but
-many people seem to have problems with it. Here's Jay Estabrook's
-Definitive Solution.
-<BLOCKQUOTE><CODE>
-<PRE>
-ARC console and SRM console keep dates in the time-of-year (TOY) clock
-in slightly different formats (actually, only the "year" field differs).
-
-The "/sbin/clock" binary normally expects the format which SRM uses; you can,
-however, tell it to expect ARC format instead, using the "-A" flag.
-Thus, to read the clock when its kept in ARC format, say "clock -r -A", and
-to write it, "clock -w -A". If its not written in the expected format, the
-console (ARC or SRM) will prolly complain about it the next time it has a
-chance... :-\
-
-The best way to ensure you're using the correct format, is to set the date via
-the console's date-setting facility; under ARC, it's a menu item some place,
-under SRM it's a command (IIRC; try "help date").
-
-Then you must ensure that the "clock" call in the RH script
-/etc/rc.d/rc.sysconfig KNOWS WHAT FORMAT TO READ THE TOY IN!!!!
-
-If you're using ARC console to boot MILO/kernel, do:
-
-1. running RH 4.1, make sure /etc/sysconfig/clock contains:
-
-        CLOCKMODE="ARC"
-
-2. running RH 4.2, make sure /etc/sysconfig/clock contains (at least):
-
-        ARC=true
-
-Now, If you're using SRM console to directly boot a kernel, then:
-
-1. RH 4.1, same file, set CLOCKMODE=""
-
-2. RH 4.2, same file, set ARC=false
-
-Refer to /etc/rc.d/rc.sysconfig for details about how the above are used to
-call "clock" with the appropriate arguments.
-        
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<DT><B>Clock gets set to a random date and time</B><DD><P>This occurs on the PC164/LX164/SX164 mainboards.
-This is due to a slightly different version of the TOY clock
-hardware on these boards. As seen above, your system clock gets
-set from the TOY clock during bootup, using <CODE>clock</CODE>.
-To test if your setup has this problem try the following command:
-<BLOCKQUOTE><CODE>
-<PRE>
-while true; do /sbin/clock -r [-A]; done
-        
-</PRE>
-</CODE></BLOCKQUOTE>
-
-(use the -A option when your hardware TOY clock is in ARC format)<BR>
-If you see any inconsistent results, you need to upgrade your
-<CODE>/sbin/clock</CODE>. Get one of:
-<BLOCKQUOTE><CODE>
-<PRE>
-gatekeeper.dec.com:/pub/DEC/Linux-Alpha/Kernels/clock-pc164-rh4.2
-gatekeeper.dec.com:/pub/DEC/Linux-Alpha/Kernels/clock-pc164-rh50
-        
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<DT><B>0>0>0>0>0>0></B><DD><P>Standard MILO images are configured to talk to the first serial  
-port as well as the screen. When you have a modem connected it
-will talk back. To resolve this, either make sure your modem is
-turned off at boot time, connect it to a different port, or build
-your own MILO, disabling serial port echo.
-<P>
-<DT><B><CODE>fdisk</CODE> doesn't recognize my disk's partitions.</B><DD><P>This may occur when
-you're using BSD-style partitioning, e.g when partitioned using
-Digital Unix's <CODE>disklabel</CODE> utility. Just go into <CODE>fdisk</CODE>'s BSD
-mode and you will be allright.
-<P>
-<DT><B><CODE>vi</CODE> handles keystrokes in batches of four</B><DD><P>In fact, other apps will show the same behaviour: it really is a <CODE>ncurses</CODE>
-problem. It may be related to the <CODE>termio</CODE> vs. <CODE>termios</CODE> programming error
-described in the section below. A workaround is to issue <CODE>stty eof '^a'</CODE>
-before starting vi.
-<P>
-<DT><B>X will not start on Ruffian (164UX)</B><DD><P>Starting X fails with "Failed to set IOPL for I/O".
-Cause: the stock 5.1 GLIBC doesn't recognize the RUFFIAN 
-system type. So, do <EM>exactly</EM> the following (as root):
-<BLOCKQUOTE><CODE>
-<PRE>
-ln -s EB164 /etc/alpha_systype
-        
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<DT><B><CODE>ipfwadm</CODE> fails.</B><DD><P>Red Hat 5.1 and 5.2 for Alpha shipped with a buggy ipfwadm. The common
-workaround is to use ipfwadm from Red Hat 5.0. (Note: when you're running 
-a 2.1.* or 2.2.* kernel you'll be using ipchains instead.)
-<P>
-<DT><B>Instable configurations with Adaptec SCSI controllers.</B><DD><P>This seems to occur with Adaptec 2940 on PC164 in particular. Improvement
-has been reported after turning off the autodetection of device speed, width
-and termination. Get the utility from:
-<BLOCKQUOTE><CODE>
-<PRE>
-http://www.windowsnt.digital.com/support/drivers/drivers.asp/
-        
-</PRE>
-</CODE></BLOCKQUOTE>
-
-Put it on a floppy, or any FAT partition, and select "Run a program" from
-the ARCBIOS menu. (Newer systems will allow you to configure SCSI controllers
-by running the onboard utility through the i386 emulator in the firmware.)
-<P>
-<DT><B>XL266 refuses to boot after setting time.</B><DD><P>When you forget to use the -A option when setting the hardware clock on an XL266,
-the ARCBIOS may see an invalid time, and refuse to boot any OS until this has
-been corrected. Unfortunately, when the setting is sufficiently invalid, it will
-not allow you to do so. (This is definitely a bug...) To recover you need a modified
-version of linload.exe. (Thanks to Juergen Schroeder this is available from 
-<A HREF="ftp://ftp.ub.uni-marburg.de/pub/unix/linux/alpha/linload_auto.exe">ftp://ftp.ub.uni-marburg.de/pub/unix/linux/alpha/linload_auto.exe</A>.)
-Put it on a floppy, together with your favorite MILO, and
-use the "Run a Program" option to start it. Once in MILO you can boot linux, and
-set the clock again. Be sure to use -A this time...<BR>
-(I believe the modification to linload.exe is that the location of MILO is
-hardwired into the program.)
-<P>
-</DL>
-<P>
-<H2><A NAME="ss1.3">1.3 Porting to Alpha: the <CODE>long</CODE> and <CODE>short</CODE> of it</A>
-</H2>
-
-<P> Here is a somewhat random collection of popular ways of shooting
-yourself in the foot on Unix when programming in C.  This has
-practically nothing to do with Linux or Alpha, but since Linux/Alpha
-is among the pioneers in 64-bit land, these errors are more likely to
-show on such systems.
-<P>
-<DL>
-<DT><B><CODE>sizeof(long)!=32</CODE></B><DD><P>Many programs assume a long is
-32 bits wide.  This is non-sense.  The ANSI C standard
-does not specify anything like that.  For example, on
-an Alpha running a grown up operating system such as
-DEC Unix or Linux, the fundamental C types have the following
-sizes and alignment restrictions:
-<UL>
-<LI><CODE>char</CODE>: 8 bits as usual, byte alignment is fine.</LI>
-<LI><CODE>short</CODE>: 16 bits as usual, 2 byte alignment required.</LI>
-<LI><CODE>int</CODE>: 32 bits as usual, 4 byte alignment required.</LI>
-<LI><CODE>float</CODE>: 32 bits as usual, 4 byte alignment required.</LI>
-<LI><CODE>long</CODE>: 64 bits, 8 byte alignment required.</LI>
-<LI><CODE>void*</CODE>: 64 bits, 8 byte alignment required.</LI>
-<LI><CODE>double</CODE>: 64 bits as usual, 4 byte alignment required.</LI>
-</UL>
-
-Note that the above implies that you cannot cast a pointer
-to an integer without loosing bits.  In fact, Alpha binaries
-by default are purposely arranged in such a way that if you
-try to do this, they'll dump core---it is much better to
-learn about such program errors via a core dump than through
-some subtle errors.
-<P>If you need a variable with exactly <I>n</I> bits in it, you can
-use the following types in Linux applications (and most other
-systems that are based on GNU libc):
-<UL>
-<LI><CODE>int8_t</CODE>: signed integer type with 8 bits.</LI>
-<LI><CODE>int16_t</CODE>: signed integer type with 16 bits.</LI>
-<LI><CODE>int32_t</CODE>: signed integer type with 32 bits.</LI>
-<LI><CODE>int64_t</CODE>: signed integer type with 64 bits.</LI>
-<LI><CODE>u_int8_t</CODE>: unsigned integer type with 8 bits.</LI>
-<LI><CODE>u_int16_t</CODE>: unsigned integer type with 16 bits.</LI>
-<LI><CODE>u_int32_t</CODE>: unsigned integer type with 32 bits.</LI>
-<LI><CODE>u_int64_t</CODE>: unsigned integer type with 64 bits.</LI>
-</UL>
-
-In the kernel, use the following types instead:
-<UL>
-<LI><CODE>__s8</CODE>: signed integer type with 8 bits.</LI>
-<LI><CODE>__s16</CODE>: signed integer type with 16 bits.</LI>
-<LI><CODE>__s32</CODE>: signed integer type with 32 bits.</LI>
-<LI><CODE>__s64</CODE>: signed integer type with 64 bits.</LI>
-<LI><CODE>__u8</CODE>: unsigned integer type with 8 bits.</LI>
-<LI><CODE>__u16</CODE>: unsigned integer type with 16 bits.</LI>
-<LI><CODE>__u32</CODE>: unsigned integer type with 32 bits.</LI>
-<LI><CODE>__u64</CODE>: unsigned integer type with 64 bits.</LI>
-</UL>
-
-However, the availability of these types is somewhat system
-dependent.  In particular, on a 32 bit machine, the 64 bit
-integers are typically available only when using GNU C.  Also,
-keep in mind that there are still machines out there that
-have odd word sizes, such as 36 bits.  So, for the sake of
-portability, these types should be used sparingly.
-<P>
-<DT><B>Error return value of <CODE>inet_addr</CODE>()</B><DD><P>It is a common myth
-to assume that <CODE>inet_addr()</CODE> returns -1 in case of
-error.  In fact, even the Linux man-page propagates this
-superstitious belief.  But don't be misguided: in truth,
-<CODE>inet_addr()</CODE> returns <CODE>INADDR_NONE</CODE> in case
-of error.  This manifest constant is defined in
-<CODE>netinet/in.h</CODE>.  An even better solution is to avoid
-this function alltogether.  Reasonably modern libraries provide
-the <CODE>inet_aton</CODE>() function that has an unmistakable
-return value to indicate success or failure.
-<P>
-<DT><B><CODE>struct termio</CODE> does <EM>not</EM> equal <CODE>struct termios</CODE></B><DD><P>Many Linux programs incorrectly assume it is all right to mix
-and match <CODE>struct termio</CODE> and <CODE>struct termios</CODE> and their
-<CODE>ioctl()</CODE> calls.  Well, not quite.  The two interfaces are in fact
-incompatible on many systems (for historic reasons, this can't be
-fixed easily).  Thus, if you use <CODE>struct termio</CODE>, then be
-sure to use the termio calls <EM>only</EM> (<CODE>TCGETA</CODE>, <CODE>TCSETAF</CODE>,
-<CODE>TCSETAW</CODE>, and <CODE>TCSETA</CODE>).  In constrast, if you use the termios
-structure, be sure to use its calls only (<CODE>TCGETS</CODE>, <CODE>TCSETSF</CODE>,
-<CODE>TCSETSW</CODE>, and <CODE>TCSETS</CODE>).
-<P>
-<DT><B>Atomicity of sub-word loads/stores</B><DD><P>It is generally not safe to assume that reading or writing a
-quantity that is smaller than the machine's word size is
-atomic.  In particular, all early Alpha chips do not have
-atomic instructions to read or write a byte or a short (16
-bits).  Unless you're into kernel hacking where you need to
-synchronize with devices and/or interrupts, you probably won't
-care.  But even in user-space this can cause problems in case
-your program is sharing data with another process through
-shared memory, for example.
-</DL>
-<P>
-<P>
-<HR>
-<A HREF="FAQ-2.html">Next</A>
-Previous
-<A HREF="FAQ.html#toc1">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-10.html b/english/ports/alpha/faq/FAQ-10.html
deleted file mode 100644
index f66ba34d32d..00000000000
--- a/english/ports/alpha/faq/FAQ-10.html
+++ /dev/null
@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: AlphaStation 200</TITLE>
- <LINK HREF="FAQ-11.html" REL=next>
- <LINK HREF="FAQ-9.html" REL=previous>
- <LINK HREF="FAQ.html#toc10" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-11.html">Next</A>
-<A HREF="FAQ-9.html">Previous</A>
-<A HREF="FAQ.html#toc10">Contents</A>
-<HR>
-<H2><A NAME="s10">10. AlphaStation 200</A></H2>
-
-<P> These boxes have become quite popular recently because they are now
-available cheaply (Digital is clearing out the warehouse ??) which makes
-them the successor to the UDB as a lower end way into the Alpha 
-world. 
-<A HREF="http://www.onsale.com">Onsale</A> and 
-<A HREF="http://www.webauction.com">Webauction</A> are the places to get them.
-<P>
-<P> Rick Taylor (
-<A HREF="mailto:charlet@hubcap.clemson.edu">Charles E. Taylor IV</A>) supplied the following details:
-<P>
-<DL>
-<P>
-<DT><B>CPU</B><DD><P>The AS200 comes with 21064 or 21064A CPUs. Speeds are 166MHz and 233 MHz.
-The support chipset is the 21071-AA.
-<DT><B>cache</B><DD><P>Apart from the on-chip cache, there is 512K of cache on the mainboard.
-<DT><B>memory</B><DD><P>There are 6 slots for 72 pin true parity SIMMs. Slots must be filled
-in pairs. According to the specs, 384 megs of RAM can be added. The items 
-from Onsale seem to come with 16 MB. You may want to add some before
-installing Linux.
-<DT><B>disc</B><DD><P>The base configuration does not include any discs...
-<DT><B>video</B><DD><P>.. nor a graphics card. Any Alpha supported PCI video card should work:
-S3Virge DX (4MB) and S3Trio64V2 (2MB) definitely do.
-<P>
-</DL>
-<P>
-<P>Some more quotes from Rich's mail:
-<P>
-<UL>
-<LI>"As with most of these older Alphas, upgrading the firmware is all but a
-necessity to install Linux.  Mine came with an older SRM that just wouldn't
-load the Linux kernel without locking, and upgrading to the latest ARC fixed
-the problem.  Mine came from the batch of Alphas that onsale and webauction
-have been (and still are, in the case of webauction) selling, so I'd assume
-other new AS200 owners might have similar problems."
-</LI>
-<LI>"To get the builtin sound card to work you need to recompile the kernel on
-Redhat.  Fairly simple, but I just talked a guy through it on the redhat-AXP
-list, so I thought I'd mention it. :)"
-</LI>
-<LI>"Something that surprised me when I first installed (before I hooked the
-machine into the local ethernet network and while I was using PPP): my modem
-wouldn't work on the first com port.  I suspect that had something to do with
-the serial console setting.  The symptom was the modem constantly getting
-traffic when no program should have been talking to it.  Not too tough to
-figure out, but it could be rather confusing to someone who didn't get the
-documentation with their machine.  A quick fix is to simply use the other com
-port for the modem."
-</LI>
-<LI>"My AS200 came with something of an oddity - an ISA card with two PCMCIA slots
-on it.  According to the DEC shipping label it was an option, but as I don't
-have any PCMCIA devices, I removed the card from the machine and put it in
-storage.  I'm not sure if/how the card works in Linux, and I didn't get any
-documentation for the card, so I don't have much information on it."</LI>
-</UL>
-<P>
-<P> If you have bought one of them you may find the following URL's
-useful: both give a step by step recipe to get Linux installed.<BR>
-<A HREF="http://www.toast.net/~strycher/AS200.html">http://www.toast.net/~strycher/AS200.html</A><BR>
-<A HREF="http://www.mindspring.com/~ccsf-lug/AS200.htm">http://www.mindspring.com/~ccsf-lug/AS200.htm</A><P>
-<HR>
-<A HREF="FAQ-11.html">Next</A>
-<A HREF="FAQ-9.html">Previous</A>
-<A HREF="FAQ.html#toc10">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-11.html b/english/ports/alpha/faq/FAQ-11.html
deleted file mode 100644
index 7334dce8cb2..00000000000
--- a/english/ports/alpha/faq/FAQ-11.html
+++ /dev/null
@@ -1,205 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Samsung APC164UX (Ruffian): The Irreverent Guide </TITLE>
- <LINK HREF="FAQ-12.html" REL=next>
- <LINK HREF="FAQ-10.html" REL=previous>
- <LINK HREF="FAQ.html#toc11" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-12.html">Next</A>
-<A HREF="FAQ-10.html">Previous</A>
-<A HREF="FAQ.html#toc11">Contents</A>
-<HR>
-<H2><A NAME="s11">11. Samsung APC164UX (Ruffian): The Irreverent Guide </A></H2>
-
-<P> (This section is written by 
-<A HREF="mailto:stig@alpha-processor.com">Stig Telfer</A>.)
-<P>
-<H2><A NAME="ss11.1">11.1 Ruffian Links</A>
-</H2>
-
-<P>
-<UL>
-<LI>
-<A HREF="http://www.theophys.kth.se/~jurijus/alpha/">A detailed installation guide</A> for Red Hat 5.2. 
-</LI>
-<LI>
-<A HREF="http://www.usa.samsungsemi.com/products/alpha/alpha-prodinfo.htm">Samsung Semiconductor page</A> giving a good introduction to their Alpha systems.
-</LI>
-<LI>
-<A HREF="http://www.usa.samsungsemi.com/products/browse/alphaboards.htm">Samsung Semiconductor page</A> for specs on UX, LX motherboards. 
-</LI>
-<LI>
-<A HREF="ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/Kernels">Gatekeeper</A>, Digital's Linux support page. Several useful Ruffian upgrades available here. 
-</LI>
-<LI>
-<A HREF="http://192.84.116.34:80/linux/">Deskstation's Ruffian Information</A> (Deskstation are the designers of the Ruffian)
-- beware, the install guide is a little dated (Red Hat 4.1?) 
-</LI>
-</UL>
-<P>p><B>Note</B>: This section of the FAQ is brand new, and I accept no responsibility for anything that 
-goes wrong as a consequence of reading it. If you have anything to add to it, please do! 
-<P>
-<P>
-<H2><A NAME="ss11.2">11.2 Introduction</A>
-</H2>
-
-<P> For some people, the Ruffian is the absolute business. Compared to the LX, it has more memory
-capacity, more PCI slots, onboard SCSI and ethernet and takes higher-clocked processors. Yet it 
-is plagued with a bad reputation.
-<P>
-<H3>The Caveat</H3>
-
-<P> While the vast majority have no trouble with their Ruffians (author included), a handful of
-users find fundamental shortcomings that make the board unusable for their applications. 
-<P>
-<H3>The Symptoms</H3>
-
-<P> A virtual memory stress-test that induces continuous heavy paging can cause the machine to die. 
-The problem manifests itself through various "Unable to handle kernel paging request", "killing 
-the swapper", "attempting to swap the idle process" messages, and a register dump. The system 
-may become unusable after that. 
-<P>
-<P> The stress-test may run without failure (I have run it for three days without fault), 
-or it may fail within two seconds. I have seen both
-behaviours on the same machine, in different configurations. 
-<P>
-<P> Some people claim this problem only arises with large memory configurations. 
-<P>
-<H3>The Cause</H3>
-
-<P> Empirical evidence (above) suggests heavy paging causes this situation. However, some
-people have seen their Ruffians fail within seconds. I can induce rapid failure by 
-reordering the DIMM pairs in my machine. However, on putting them back in the original order,
-the problem remains for a while! Could there be some non-volatile state that is being confused? 
-<P>
-<H3>The Fix</H3>
-
-<P> There are several suggested fixes: 
-<UL>
-<LI>     Use the latest milo and ldmilo available on gatekeeper (see below). </LI>
-<LI>     The patched 2.0.35 kernel sources on that site are also worth installing. </LI>
-<LI>     Another empirical fix is to set the memory available to Linux to be a small
-amount less than the total memory. </LI>
-</UL>
-<P>
-<P>Hopefully a definite fix beyond these heuristic measures will be found soon, and 
-several people are involved with the problem (in spare time...) 
-<P>
-<P>
-<H2><A NAME="ss11.3">11.3 The Red Hat Release CDs and the Ruffian </A>
-</H2>
-
-<P>Unfortunately, both Red Hat 5.1 and 5.2 releases have flaws to be aware of when installing on a Ruffian.
-<P>
-<H2><A NAME="ss11.4">11.4 Red Hat 5.1 </A>
-</H2>
-
-<P>For your first disk, you should use a different milo and ldmilo.exe file, which are 
-downloadable from Gatekeeper, Digital's FTP server:
-<P>
-<UL>
-<LI>    
-<A HREF="ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/Kernels/milo-ruffian-981020">ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/Kernels/milo-ruffian-981020</A></LI>
-<LI>    
-<A HREF="ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/Kernels/ldmilo-ruffian-981020">ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/Kernels/ldmilo-ruffian-981020</A></LI>
-</UL>
-<P>
-<H3>How to build your milo disk</H3>
-
-<P>
-<OL>
-<LI>   Take a DOS-formatted floppy </LI>
-<LI>   Copy the two files above onto it, renaming them to 'ldmilo.exe' and 'milo' </LI>
-<LI>   Thats it, you're done :-) </LI>
-</OL>
-<P>
-<H3>Running XFree with Red Hat 5.1 </H3>
-
-<P>If the XFree X server fails to start on your system, try adding the following link:
-<P>
-<P><CODE>cd /etc; ln -s EB164 alpha_systype</CODE>
-<P>
-<P>If your graphics card uses the SVGA X-server (eg, if you have a Matrox graphics card), 
-you should also pick up the patched SVGA server. ( 
-<A HREF="ftp://mea.tmt.tele.fi/pub/XFree86/">ftp://mea.tmt.tele.fi/pub/XFree86/</A> ) 
-<P>
-<H3>Reading the time and date correctly with Red Hat 5.1 </H3>
-
-<P>The Ruffian ARCSBIOS uses a different format for time and date. In releases of Red Hat 
-up to 5.1, this meant that Linux would not report the correct date and time. 
-<P>
-<P>This can be fixed using: 
-<UL>
-<LI>     An updated version of the clock binary (try gatekeeper), </LI>
-<LI>     by getting your date and time from another system on the network using rdate -s, </LI>
-<LI>     or by using xntpd. </LI>
-</UL>
-<P>
-<P>Date and time issues are fixed for the Ruffian in Red Hat 5.2 
-<P>
-<H2><A NAME="ss11.5">11.5 Red Hat 5.2 </A>
-</H2>
-
-<P>Unfortunately the Ruffian kernel provided on the Red Hat 5.2 CD doesn't contain 
-support for the Symbios 875 on-board SCSI. However, you can take the kernel image 
-from Red Hat 5.1 to perform the install. Once installed, you can build your own kernel 
-- the sources on 
-<A HREF="ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/Kernels">ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/Kernels</A> 
-for 2.0.35 are tried and trusted.
-<P>
-<P>
-<P>
-<H2><A NAME="ss11.6">11.6 Hardware Issues with the Ruffian </A>
-</H2>
-
-<H3>Ruffian On-board Ethernet </H3>
-
-<P>The Ruffian's on-board DEC Tulip Ethernet is not very good at auto-sensing a 100Mbit 
-link with the Linux Tulip driver. However, one of the recent versions (0.89H) seems to 
-work for most cases. Other people have reported problems with version 0.90.
-<P>
-<P>The tulip device driver page is well documented at:
-<UL>
-<LI> 
-<A HREF="http://maximus.bmen.tulane.edu/~siekas/tulip.html">http://maximus.bmen.tulane.edu/~siekas/tulip.html</A> </LI>
-<LI> 
-<A HREF="http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.html">http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.html</A> </LI>
-</UL>
-<P>
-<P>These pages also contain instructions on how to install the driver. Alternatively, 
-try looking at the section on building your own kernel in this FAQ. (The location 
-of the tulip device driver in the linux source tree is drivers/net/tulip.c, copy 
-your newly-downloaded version in here and you're ready to build)
-<P>
-<P>If your ethernet doesn't autosense 100Mbit, there are some other options I have 
-found to sometimes work, although we're in experimental territory here and what may 
-work for me may not work for you.
-<P>
-<P>Your first option is to hard-code your ethernet interface to be 100baseTX, 
-bypassing the autosensing mechanism. However, this doesn't always work. What 
-does sometimes work is hard-coding the medium to be 10Mbit, and then 100Mbit. 
-The first packet will fail transmission, but after that the link is brought up 
-in 100Mbit mode. To bypass the auto-sensing mechanism, edit tulip.c and put 
-numbers into the options array, according to your media type as defined in 
-an array further down the code (10baseT is 12, 100baseT is 4). If you still 
-can't get this to work, try this patched version of the tulip driver, actually 
-patched for the Miata by Loic Prylli. What it does is to keep trying with 
-user-specified hard-coded media.
-<P>
-<P>Again, your experience may vary...
-<P>
-<H3>Video Cards </H3>
-
-<P>To boot Linux on the Ruffian, you must put the video card in the 64-bit slot. 
-This is the only slot on PCI bus 0. All other slots are behind a PCI-PCI bridge 
-that Milo doesn't fully support. 
-<P>
-<HR>
-<A HREF="FAQ-12.html">Next</A>
-<A HREF="FAQ-10.html">Previous</A>
-<A HREF="FAQ.html#toc11">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-12.html b/english/ports/alpha/faq/FAQ-12.html
deleted file mode 100644
index 6430224f8fa..00000000000
--- a/english/ports/alpha/faq/FAQ-12.html
+++ /dev/null
@@ -1,130 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: What Graphics Cards Work With Linux/Alpha?</TITLE>
- <LINK HREF="FAQ-13.html" REL=next>
- <LINK HREF="FAQ-11.html" REL=previous>
- <LINK HREF="FAQ.html#toc12" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-13.html">Next</A>
-<A HREF="FAQ-11.html">Previous</A>
-<A HREF="FAQ.html#toc12">Contents</A>
-<HR>
-<H2><A NAME="s12">12. What Graphics Cards Work With Linux/Alpha?</A></H2>
-
-<P> Linux/Alpha supports both DEC's TGA and generic VGA cards.  The
-new PowerStorm cards from DEC are not supported yet.
-<P>
-<H2><A NAME="ss12.1">12.1 TGA Card</A>
-</H2>
-
-<P> TGA is DEC's (first) family of workstation graphics cards for the
-PCI bus.  It makes for nice and very quick cards.  The only drawback
-is that since it is coming from the workstation market, it does
-<EM>not</EM> support 16-bit color mode.
-<P>There are three versions of the TGA card.  They are all based on the
-21030 chip:
-<BLOCKQUOTE><CODE>
-<PRE>
-Model:  Description:
-ZLXp-E1  8-plane TGA (256 colors)
-ZLXp-E2 24-plane TGA (16 million colors)
-ZLXp-E3 24-plane TGA + 32-plane Zbuffer (16 million colors and 3D support)
-</PRE>
-</CODE></BLOCKQUOTE>
-
-Caveat: as described below, only the ZLXp-E1 is currently supported by
-an X server.
-<P>
-<H2><A NAME="ss12.2">12.2 VGA Cards</A>
-</H2>
-
-<P> Linux boots in VGA mode, so pretty much any graphics card should
-do for Linux.  However, the graphics card also needs to work with the
-firmware.  This is non-trivial since many PCI cards need proprietary
-wakeup sequences to bring them into a VGA compatible mode.  To solve
-this problem, the firmware includes an x86 emulator that is used to
-execute the BIOS initialization code on the graphics card.  In theory,
-it is therefore possible plug in any PC graphics card.
-<P>DEC implemented an x86 emulator that is used by the MILO (Linux), SRM
-(DEC Unix), and ARC (Windows NT) firmware.  This emulator is mature
-and can indeed initialize most, if not all, cards.  To be on the safe
-side, take a look at the hardware-compatibility lists for DEC Unix and
-Windows NT before deciding on a card.
-<P>MILO also comes with an (optional) emulator that is free.  It is not
-nearly as mature as DEC's emulator, but it nevertheless is able to
-initialize at least following graphics cards:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-bus card type:                  chip:   BIOS version:                   Note:
-=== =========================== ======  ===========================     =====
-ISA Orchid Fahrenheit 1280      S3 805  ????                            4
-ISA #9 GXE Level 12             S3 928  BIOS Version 1.13.03S
-PCI #9 GXE 64 PCI               S3 864  BIOS Version 1.02.09u
-PCI Diamond Stealth 64 DRAM PCI S3 864  BIOS Version 1.14               1
-PCI Diamond Video 64 DRAM PCI   S3 868  BIOS Version 1.02               1
-PCI Diamond Stealth 64 DRAM     S3 764  BIOS Version 2.01               2,3
-
-Notes:
-======
-1:     Reported by pgwduane@mail.atnet.net.
-2:     The S3 764 chip is mostly known as Trio64.
-3:     Reported by viper@ludd.luth.se.
-4:     Reported by jestabro@amt.tay1.dec.com.
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss12.3">12.3 Cards Supported by the X Windowing System</A>
-</H2>
-
-<P> According to the XFree 3.3.3.1 Release Notes:
-<BLOCKQUOTE><CODE>
-<PRE>
-The following X servers are available for Alpha hardware:
-
-          XMa64.tgz       Mach 64 server
-          XMono.tgz       Mono server (generic driver only)
-          XP9K.tgz        P9000 server
-          XTGA.tgz        DEC 21030 (TGA) server
-          XS3.tgz         S3 server
-          XS3V.tgz        old S3 ViRGE server (please use SVGA server)
-          XSVGA.tgz       SVGA server (Matrox Millennium and S3 ViRGE drivers only)
-</PRE>
-</CODE></BLOCKQUOTE>
-
-The S3 server is known to work with 764x, 805, 864,
-928 based cards (e.g., Orchid Fahrenheit 1280, #9 GXE64, #9
-Level 12, #9 Motion 771).  The Mach64 server is known to work
-with WinTurbo GX-VRAM and Graphics Xpression CX-DRAM cards.
-<P>
-<P> These servers are available from 
-<A HREF="ftp://ftp.xfree86.org/pub/">ftp://ftp.xfree86.org/pub/</A>.
-More recent developments are availabel from 
-<A HREF="http://www.suse.com/">SuSE</A>. Check out the section on commercial software for other options.
-<P>
-<P> For TGA not just one, but two servers exist: the first one is by the
-XFree project, as mentioned above. It's relatively young so it's not
-well-optimized yet, but it's definitively usable and since sources are
-available for it, anybody can improve it.<BR> The other one is
-based on DEC-proprietary code (sources are not available). It is fast
-and relatively stable and can be found 
-<A HREF="ftp://ftp.digital.com/pub/DEC/Linux-Alpha/X11">here</A>.
-<P>
-<H2><A NAME="ss12.4">12.4 Can Linux/Alpha Run Without Graphics Card?</A>
-</H2>
-
-<P> The firmware can be controlled over a serial line terminal at 9600
-Baud and it is possible to boot Linux/Alpha in that manner, but Linux
-itself does not currently support headless boots.  There are kernel
-patches floating on the net that add this functionality, however.
-<P>
-<P>
-<HR>
-<A HREF="FAQ-13.html">Next</A>
-<A HREF="FAQ-11.html">Previous</A>
-<A HREF="FAQ.html#toc12">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-13.html b/english/ports/alpha/faq/FAQ-13.html
deleted file mode 100644
index 017296209ce..00000000000
--- a/english/ports/alpha/faq/FAQ-13.html
+++ /dev/null
@@ -1,118 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Where Do I Get Linux Software?</TITLE>
- <LINK HREF="FAQ-14.html" REL=next>
- <LINK HREF="FAQ-12.html" REL=previous>
- <LINK HREF="FAQ.html#toc13" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-14.html">Next</A>
-<A HREF="FAQ-12.html">Previous</A>
-<A HREF="FAQ.html#toc13">Contents</A>
-<HR>
-<H2><A NAME="Where Do I Get Linux Software"></A> <A NAME="s13">13. Where Do I Get Linux Software?</A></H2>
-
-<P> There are currently aproximately four end-user installable Linux
-distributions for the Alpha available. Two are from Red Hat and DLD.
-Debian  and Stampede will be ready shortly. A distribution from SuSE
-is expected to be presented at the '99 CeBIT.
-More information on each of these distributions can be
-found below.  The 
-<A HREF="http://www.ssc.com/lj/">Linux Journal</A> periodically publishes reviews of these distributions.
-Check those for a general who's who.
-<P>Commercial products for Linux/Alpha also start to appear slowly.  Some
-noteworthy products are listed in the next section.
-<P>If you know of any other Linux/Alpha distributions or products, please
-mail 
-<A HREF="mailto:geerten@bart.nl">us</A>.
-<P>
-<H2><A NAME="ss13.1">13.1 Red Hat</A>
-</H2>
-
-<P> Red Hat is distributing the Alpha version of its well-known Linux
-distribution.  Red Hat for Alpha is ELF-based and available both
-on CD-ROM and via ftp.  The distribution uses the RPM system (Red Hat
-Package Manager) which allows easy installation of both sources and
-binaries.  Besides installing packages, it also allows to keep track
-of what's installed and it can even uninstall packages that you don't
-like anymore.  But Red Hat is a lot more than just RPM.  Be sure
-to check their 
-<A HREF="http://www.redhat.com/">web site</A> for
-all the details. <BR>
-<P>The Red Hat distribution is available via ftp from the Red Hat
-<A HREF="ftp://ftp.redhat.com/pub/">site</A>. Version 5.2 has been
-available for some time now. Be sure to downoad the errata as well.
-<A HREF="ftp://ftp.redhat.com/pub/MIRRORS.html">Mirror sites</A>
-all over the world are available as well.
-<P>
-<P>
-<H2><A NAME="ss13.2">13.2 DLD</A>
-</H2>
-
-<P> Die Deutsche Linux Distribution gibt es jetzt auch f&uuml;r Alpha. This uses
-Red Hat's RPM format, and generally seems to be based on the Red Hat
-distribution, but it's completely in German. Check out 
-<A HREF="http://www.delix.de">www.delix.de</A><P>
-<P>
-<H2><A NAME="ss13.3">13.3 Debian GNU/Linux</A>
-</H2>
-
-<P> Debian is working on a distribution for the Alpha. It should be ready
-for distribution "Real Soon Now". See the 
-<A HREF="http://www.debian.org/">Debian home page</A> for info on how
-to subscribe to the relevant mailing list.
-<P>
-<P>
-<H2><A NAME="ss13.4">13.4 Stampede</A>
-</H2>
-
-<P> It seems that a distribution for Alpha is also being prepared by
-<A HREF="http://www.stampede.org">Stampede</A>.
-<P>
-<P>
-<H2><A NAME="ss13.5">13.5 Sources</A>
-</H2>
-
-<P> The Linux/Alpha homepage contains a list of ftp sites and mirrors
-that are used by the developers to make the latest and greatest
-version of various programs available.  The Linux/Alpha home page is
-located 
-<A HREF="http://www.alphalinux.org">here</A>.
-<P>Of course, the regular Linux ftp sites such as 
-<A HREF="ftp://sunsite.unc.edu:/pub/Linux">ftp://sunsite.unc.edu:/pub/Linux</A> or 
-<A HREF="ftp://tsx-11.mit.edu/pub/linux">ftp://tsx-11.mit.edu/pub/linux</A> are good for Linux/Alpha, too.
-<P>
-<H2><A NAME="ss13.6">13.6 Building a Kernel</A>
-</H2>
-
-<P>If you want to build your own kernel you may want to follow 
-<A HREF="http://www.bart.nl/~geerten/patches.txt">this</A>
-recipe, by Harvey J. Stein. It's for 2.0.30: clean patches for 2.0.32
-are available as well, and these can be used for 2.0.33 too.<BR>
-A similar Howto has been compiled by Hugo van der Kooij, which can be
-found at 
-<A HREF="http://www.nllgg.nl/linux/Alpha/RHL5kernel.html">http://www.nllgg.nl/linux/Alpha/RHL5kernel.html</A>. This has some
-specifics related to the Red Hat 5.0 distribution.
-<P>Patches for more recent 2.0 kernels (up to 2.0.35) are available from
-<A HREF="ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/">gatekeeper</A>.
-A set for 2.0.36 will appear as soon as Jay Estabrook finds the time to
-create them. Some people report some success by using the 2.0.35 patches
-on a 2.0.36 kernel.
-<P>Recent 2.1.xxx kernels will compile on Alpha without patches.
-For kernels up to 2.1.131, do not forget to comment out "SMP = 1"
-in the Makefile (unless you are compiling for an SMP-system..)
-In 2.1.132 SMP has been changed into a normal config option.
-With the system-type selections they also include a 'generic' option,
-to create a kernel that will run on any supported Alpha platform.
-<P>Likewise for 2.2.0 and 2.2.1 (2.2.* is just the continuation of 2.1.*,
-now declared stable.) Beware of 2.2.2. though: it needs additional
-patches to compile on non-intel platforms.
-<P>
-<HR>
-<A HREF="FAQ-14.html">Next</A>
-<A HREF="FAQ-12.html">Previous</A>
-<A HREF="FAQ.html#toc13">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-14.html b/english/ports/alpha/faq/FAQ-14.html
deleted file mode 100644
index 4a1e322f17d..00000000000
--- a/english/ports/alpha/faq/FAQ-14.html
+++ /dev/null
@@ -1,88 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Commercial Applications</TITLE>
- <LINK HREF="FAQ-15.html" REL=next>
- <LINK HREF="FAQ-13.html" REL=previous>
- <LINK HREF="FAQ.html#toc14" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-15.html">Next</A>
-<A HREF="FAQ-13.html">Previous</A>
-<A HREF="FAQ.html#toc14">Contents</A>
-<HR>
-<H2><A NAME="s14">14. Commercial Applications</A></H2>
-
-<P> The list of native Linux/Alpha applications currently includes the
-following:
-<DL>
-<P>
-<DT><B>Applixware</B><DD><P>The Applixware suite of office applications, which has 
-already earned some fame in the Linux arena, is now available
-for Linux/Alpha too: 
-<A HREF="http://linux.applixware.com">http://linux.applixware.com</A><P>
-<DT><B>BRU backup software</B><DD><P>Backup software is available from 
-<A HREF="http://www.estinc.com/">EST Inc</A> (the personal edition of BRU is included with
-Craftwork Linux v2.2/AXP).
-<P>
-<DT><B>NDP Fortran</B><DD><P>Microway sells Fortran compilers for Linux/Alpha.  Information is
-available at 
-<A HREF="http://www.microway.com/">Microway's home page</A>.
-<P>
-<DT><B>NAG Fortran90</B><DD><P>Alternatively, there's a compiler from NAG. Linux/Alpha is just one of
-many platforms supported. Check out their 
-<A HREF="http://www.nag.co.uk/">home page</A>.
-<P>
-<DT><B>CLIO</B><DD><P>CLIO is E-Mail software. Look 
-<A HREF="http://www.clio.com">here</A> for details.
-<P>
-<DT><B>Motif</B><DD><P>Motif for Linux/Alpha is available from 
-<A HREF="http://www.metrolink.com/products/motif/index.html">MetroLink</A>, from
-<A HREF="http://www.redhat.com/products/product-details.phtml?id=rhm-sa">Red Hat</A>, and from 
-<A HREF="http://www.lsl.com/catalog/motif.html">LSL</A>.
-<P>
-<DT><B>X servers</B><DD><P>
-<A HREF="http://www.metrolink.com/">MetroLink</A> also produces
-a commercial X-server. If your graphics hardware is not supported by
-XFree, you may want to check out their homepage, or visit 
-<A HREF="http://www.xig.com">XiGraphics</A>, who offer a similar product.
-<P>
-<DT><B>Open Sound System</B><DD><P>More and better sound-card support compared to what comes with the
-Linux kernel.  Available from 
-<A HREF="http://www.4front-tech.com/oss.html">4Front Technologies</A>.
-<P>
-<DT><B>XVScan</B><DD><P>XVScan is, you guessed it, scanning software to use with John Bradley's
-<EM>xv</EM>. It supports "Most HP Scanjets, including the ancient ScanJet
-Plus..". Check out 
-<A HREF="http://www.tummy.com/xvscan">tummy.com,   ltd.</A>. (Thanks to Michael Champigny for pointing this out.)
-<P>
-<DT><B>Picture Elements</B><DD><P>
-<A HREF="http://www.picturel.com">Picture Elements</A>'s PCI image processing
-boards are actively supported under Linux/alpha. They also distribute some
-free 
-<A HREF="http://www.picturel.com/software.html">software</A>,
-including tools/patches that will help you crosscompile from Linux/Alpha
-for a variety of other platforms.
-<P>
-<DT><B>Net/Equater</B><DD><P>If you run a web server you might be interested in this Load-Balancing and
-High-Availability Software, by 
-<A HREF="http://www.bscsoft.com">Budnik and Sporner Computer Software, LLC</A><P>
-<DT><B>Multimedia software</B><DD><P>A variety of Multimedia software is available from 
-<A HREF="http://www.mpegtv.com">MpegTV</A>, some of it for Linux/Alpha.
-<P>
-</DL>
-<P>
-<P> Aside from the above native applications many Linux/x86
-applications can be run under Linux/Alpha using the em86 emulator.
-See Section 
-<A HREF="FAQ-16.html#em86">em86</A>
- for details.
-<P>
-<P>
-<HR>
-<A HREF="FAQ-15.html">Next</A>
-<A HREF="FAQ-13.html">Previous</A>
-<A HREF="FAQ.html#toc14">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-15.html b/english/ports/alpha/faq/FAQ-15.html
deleted file mode 100644
index 20fb1fa4ebd..00000000000
--- a/english/ports/alpha/faq/FAQ-15.html
+++ /dev/null
@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: How To Boot Linux/Alpha?</TITLE>
- <LINK HREF="FAQ-16.html" REL=next>
- <LINK HREF="FAQ-14.html" REL=previous>
- <LINK HREF="FAQ.html#toc15" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-16.html">Next</A>
-<A HREF="FAQ-14.html">Previous</A>
-<A HREF="FAQ.html#toc15">Contents</A>
-<HR>
-<H2><A NAME="How To Boot Linux/Alpha"></A> <A NAME="s15">15. How To Boot Linux/Alpha?</A></H2>
-
-<P> There are basically three ways of getting Linux/Alpha booted,
-depending on what firmware you're using.  The preferred method of
-booting used to be to install MILO into the flash ROM. However,
-in that way newer hardware may not be initialized properly.  If
-that is the case, one can boot MILO from within the ARC or AlphaBIOS
-console (Windows NT firmware). <BR>  Finally, if MILO
-has not been ported to a machine, it is still possible to boot Linux
-using the SRM firmware (DEC Unix).  Installation of and booting with
-MILO is described in the the 
-<A HREF="milo.html">MILO Howto</A>.
-Be sure to use a recent MILO!
-Booting with SRM is described in the 
-<A HREF="srm.html">SRM Howto</A>.
-<P>
-<P>
-<HR>
-<A HREF="FAQ-16.html">Next</A>
-<A HREF="FAQ-14.html">Previous</A>
-<A HREF="FAQ.html#toc15">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-16.html b/english/ports/alpha/faq/FAQ-16.html
deleted file mode 100644
index b797280e7e7..00000000000
--- a/english/ports/alpha/faq/FAQ-16.html
+++ /dev/null
@@ -1,149 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: EM86: How To Run Linux/x86 Apps on Linux/Alpha</TITLE>
- <LINK HREF="FAQ-17.html" REL=next>
- <LINK HREF="FAQ-15.html" REL=previous>
- <LINK HREF="FAQ.html#toc16" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-17.html">Next</A>
-<A HREF="FAQ-15.html">Previous</A>
-<A HREF="FAQ.html#toc16">Contents</A>
-<HR>
-<H2><A NAME="em86"></A> <A NAME="s16">16. EM86: How To Run Linux/x86 Apps on Linux/Alpha</A></H2>
-
-<P>Thanks to Jim Paradis, it is now possible to run Linux/x86
-binaries on your Alpha box. The em86 emulator is based on the
-FX!32 emulator/binary translator Digital produced for Windows NT.
-(Unfortunately the second part is <EM>not</EM> available for Linux.)
-<P>
-<P>The emulator is currently considered beta-quality, but it works very
-well for applications such as Netscape or Applix.  At present, a UDB
-may not be fast enough for em86 (depending on your patience, of
-course) but anything starting at a 300MHz 21164 should do nicely.
-(If you are not satisfied with the speed, but happen to own a Digital Unix
-license for your machine, you may want to take a look at the next chapter.)<BR>
-A future version of em86 may include the ability to redirect
-shared-library calls to the native libs, rather than load the x86 versions
-which must be run through the emulator. This will not only improve the
-speed, but also save you a lot of discspace.
-<P>
-<P>See the 
-<A HREF="ftp://ftp.digital.com/pub/DEC/Linux-Alpha/em86/">em86 ftp directory</A> for details. The README file will provide you
-with all the info you need to install the emulator. Note that for kernel
-version 2.0.30 the em86-patches are included in the 
-<A HREF="ftp://gatekeeper.dec.com/pub/DEC/Linux-Alpha/Kernels/">alpha-patches</A> at gatekeeper, which may save you some work.
-<P>
-<H2><A NAME="ss16.1">16.1 Two quotes from the README</A>
-</H2>
-
-<P>Here is what you can do with em86..
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-        Application Notes
-
-              EM86 has been tested on numerous test cases and small
-              applications (xtetris, for example). In addition, three
-              major packages have been verified to run to varying
-              degrees under EM86. Following are notes on each package.
- 
-              __________________________________________________________
-              Application___________Notes_______________________________
-
-              Netscape Navigator    Install Netscape Navigator Gold
-              Gold 3.01             as per the supplied installation
-                                    instructions.
-
-                                    _____________ WARNING_____________
-
-                                    DO NOT under ANY circumstances enable
-                                    Java or JavaScript until further notice.
-                                    Attempting to use these WILL crash your
-                                    browser. While this is a known problem
-                                    even under Linux/x86, none of the suggested
-                                    workarounds improved the situation. We are
-                                    currently investigating this problem.
-                                    __________________________________
-
-                                    If Netscape has trouble locating
-                                    Internet hosts, but you can ping
-                                    these hosts from the command line,
-                                    try installing an /etc/nsswitch.conf
-                                    file.
-
-
-              Adobe Acrobat Reader  Use the supplied install procedure
-              3.0                   to install Acrobat Reader. With
-                                    the em86-patch applied to your
-                                    kernel, this application should
-                                    run normally. Otherwise, you will
-                                    need to modify the script
-
-                                    /usr/local/Acrobat3/bin/acroread
-
-                                    to use EM86 to invoke the acroread
-                                    binary.
-
-              Applixware 4.2        Because Applixware uses rpm for
-                                    installation, you must override
-                                    the architecture check. (rpm does
-                                    not normally allow you to install
-                                    the binaries for one architecture
-                                    onto a machine of a different
-                                    architecture). To override, copy
-                                    the install script from the CD to
-                                    a writable location, then edit the
-                                    script to supply the "-ignorearch"
-                                    flag to rpm. Since Applixware has
-                                    binaries that invoke other binaries,
-                                    you need to apply the em86-patch
-                                    to the kernel for it to run. Since
-                                    Applixware pushes lots of data on
-                                    the stack, you also need to apply
-                                    the traparg patch to the kernel.
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>..and here is what you cannot..
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-        Restrictions
-
-              The EM86 restrictions are as follows:
-
-              o   EM86 emulates user-mode code only.
- 
-              o   EM86 cannot run programs that access virtual memory 
-                  above the address 78000000.
-
-              o   EM86 does not now, nor will in the future, support the 
-                  following system calls: setup, break, ptrace, stty, 
-                  gtty, prof, acct, phys, lock, mpx, ulimit, profil, 
-                  ioperm, iopl, idle, mx86, modify-Ldt, create_module,
-                  init_module, delete_module, get_kernel_syms, bdflush, 
-                  afs_syscall, and sysctl.
-
-              o   EM86 0.9.1 does not support the following system
-                  calls that will be supported in future releases: mount, 
-                  umount, uselib, old_readdir, sysinfo, ipc sigreturn, 
-                  clone, adjtimex, quotactl, sysfs, flock, msync, mlock, 
-                  munlock, mlockall, munlockall, sched_setparam,
-                  sched_getparam, sched_setscheduler, sched_getscheduler, 
-                  sched_yield, sched_get_priority_max, sched_get_priority_min,
-                  sched_rr_get_interval, nanosleep, and mremap.
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>And if you don't care to spend all those CPU cycles while your Alpha
-pretends to be an Intel CPU, then the next chapter shows you an other way
-to make many applications available.
-<P>
-<HR>
-<A HREF="FAQ-17.html">Next</A>
-<A HREF="FAQ-15.html">Previous</A>
-<A HREF="FAQ.html#toc16">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-17.html b/english/ports/alpha/faq/FAQ-17.html
deleted file mode 100644
index 2543bc7ace1..00000000000
--- a/english/ports/alpha/faq/FAQ-17.html
+++ /dev/null
@@ -1,194 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: How To Run DEC Unix Netscape on Linux/Alpha</TITLE>
- <LINK HREF="FAQ-18.html" REL=next>
- <LINK HREF="FAQ-16.html" REL=previous>
- <LINK HREF="FAQ.html#toc17" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-18.html">Next</A>
-<A HREF="FAQ-16.html">Previous</A>
-<A HREF="FAQ.html#toc17">Contents</A>
-<HR>
-<H2><A NAME="s17">17. How To Run DEC Unix Netscape on Linux/Alpha</A></H2>
-
-<P>(This section was contributed by 
-<A HREF="mailto:gander@voyager.netcomi.com">Gerald Anderson</A>.  Note that the Linux/x86
-Netscape binary can be run through 
-<A HREF="ftp://ftp.digital.com/pub/DEC/Linux-Alpha/em86/">em86</A>.
-This is a bit slower, but doesn't require any special licenses.
-Now that Netscape's sourcecode is available, we expect to see a native
-Linux/Alpha version in the near future. However porting to 64bit proved
-more difficult than expected. A fairly stable version of Mozilla is
-available for download from 
-<A HREF="http://www.alphalinux.org">the Alpalinux Homepage</A>. Or check out 
-<A HREF="http://www.unix-ag.org/Linux-Alpha/Mozilla/">Nils Faerber</A>'s
-page for the latest developments.)
-<P>
-<P> Support for running ECOFF (the OSF and DU version of <CODE>a.out</CODE>)
-binaries must have been built into the Linux/Alpha kernels.  In
-effect, this allows you to run with minimal difficulty a large variety
-of programs that were orginally compiled on an OSF/1 or Digital Unix
-Alpha.
-<P>
-<BLOCKQUOTE>
-<B>IMPORTANT:</B> All Digital software mentioned in this section is
-copyright by Digital and other parties.  You cannot legally use any of
-this software on your Linux box without the appropriate license(s) for
-that machine.  If your machine is owned by a university, it may be
-covered by a campus license agreement---check with your local
-representative.
-</BLOCKQUOTE>
-<P>
-<P>
-<H2><A NAME="ss17.1">17.1 Requirements</A>
-</H2>
-
-<P>There are two separate lists of requirements depending on if you
-have access to OSF/1 v3.x or Digital Unix 4.x (Editor's note: Digital
-renamed DEC OSF/1 to DEC Unix somewhere around release 3.2---it's the
-same OS, just different releases).
-<P>
-<DL>
-<DT><B>For DEC OSF/1 up to and including v3.2:</B><DD><P>
-<UL>
-<LI>Linux kernel version 2.0.x or 2.1.x (you must have ECOFF
-support compiled in)</LI>
-<LI> Access to an Alpha running OSF/1 3.x</LI>
-</UL>
-<DT><B>For DEC Unix version v4.0 or newer:</B><DD><P>
-<UL>
-<LI> Linux kernel version 2.1.23+ (you must have ECOFF support
-compiled in)</LI>
-<LI> Access to an Alpha running DU 4.x</LI>
-</UL>
-</DL>
-<P>
-<P>
-<H2><A NAME="ss17.2">17.2 How-To</A>
-</H2>
-
-<P>For both OSF/1 3.x and Digital Unix 4.x you must complete the
-following.
-<P>
-<OL>
-<LI> Get <CODE>/sbin/loader</CODE> from the Digital machine and place it
-in <CODE>/sbin/loader</CODE> on your Linux box.
-</LI>
-<LI>  Create a directory on your Linux box for <CODE>/usr/shlib</CODE>
- </LI>
-<LI>  Get the following libraries from the Digital box and place in the 
-<CODE>/usr/shlib</CODE> directory on your Linux box
-<UL>
-<LI><CODE>libXm.so</CODE></LI>
-<LI><CODE>libXmu.so</CODE></LI>
-<LI><CODE>libm.so</CODE></LI>
-<LI><CODE>libX11.so</CODE></LI>
-<LI><CODE>libXt.so</CODE></LI>
-<LI><CODE>libdnet_stub.so</CODE></LI>
-<LI><CODE>libc.so</CODE></LI>
-<LI><CODE>libXext.so</CODE></LI>
-</UL>
-
-If you are going to use Digital Unix 4.0 libs/loader you must also get:
-<UL>
-<LI><CODE>libSM.so</CODE></LI>
-<LI><CODE>libICE.so</CODE></LI>
-</UL>
-
- </LI>
-<LI> Get the file <CODE>/etc/svc.conf</CODE> from the Digital box and
-place it in <CODE>/etc/svc.conf</CODE> on your Linux box.
- </LI>
-<LI>  Download from 
-<A HREF="ftp://ftp.netscape.com/">ftp.netscape.com</A> the OSF/Alpha version of navigator
-(e.g., get <CODE>netscape-v301-export.alpha-dec-osf2.0.tar.gz</CODE>
-from 
-<A HREF="ftp://ftp.netscape.com/pub/navigator/3.01/unix/">this</A>
-directory).
- </LI>
-<LI>  Install it
- </LI>
-<LI>  Run it!!  </LI>
-</OL>
- 
-<P>
-<H2><A NAME="ss17.3">17.3 Conclusion</A>
-</H2>
-
-<P> This procedure has been tested on a Red Hat 4.0 and Red Hat 4.1 box
-with kernel versions 2.0.27, 2.0.28 (for OSF/1 3.x) and 2.1.23 (for DU
-4.x).  It seems to be very stable when running the OSF/1 libs/loader
-but I've noticed some problems with Segmentation Faults using the DU
-4.0 libs/loader.  I've also noticed that when using DU 4.0 libs/loader
-that the <CODE>/etc/svc.conf</CODE> file is not as necessary as when
-running the OSF/1 stuff.  It does complain, but it is not fatal.
-<P>If you have questions regarding this document please first refer to
-the archives for the axp-list mailing list/archive at 
-<A HREF="http://www.redhat.com/support/mailing-lists/">http://www.redhat.com</A>, then if you
-didn't find your answer feel free to mail me at 
-<A HREF="mailto:gander@voyager.netcomi.com">gander@voyager.netcomi.com</A>.
-<P>All other comments regarding this section may be sent directly to 
-<A HREF="mailto:gander@voyager.netcomi.com">gander@voyager.netcomi.com</A>.
-<P>
-<BLOCKQUOTE>
-<B>NOTE:</B> Java applets do not work with any version of OSF/1 or DU
-libs/loader.  I have not heard if anybody is working on this, or what
-the problem is.
-</BLOCKQUOTE>
-<P>Following is a note received from Linus regarding support for DU 4.0
-libs/loader, if you do email him, please insure as noted that the
-problem is detailed and reproducible.
-<P>Notes about using Digital Unix 4.0
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-From axp-list@redhat.com
-> 
-> Please report any problems wrt Digital UNIX binary compatibility to me,
-> and I'll look into them (assuming the report is detailed and reproducible
-> enough). There is a known problem with initial argument handling: argv[0]
-> is /sbin/loader instead of the program we actually run, and I haven't
-> looked into this one yet (and currently that's pretty low on my list of
-> things to look at..). This problem _may_ be related to netscape getting a
-> SIGSEGV if you start it without any arguments (but if you give it
-> arguments it works fine at least for me). 
-> 
->               Linus
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss17.4">17.4 Mail</A>
-</H2>
-
-<P>After setting Netscape up like this, sending E-Mail still fails. Oleg
-Gusev came up with the following solution:
-<UL>
-<LI>mkdir /etc/sia/</LI>
-<LI>touch /etc/sia/siainitgood</LI>
-<LI>copy /etc/sia/matrix.conf from DU to Linux</LI>
-</UL>
-
-He also came up with a patch to fix the argv[0] problem mention in Linus'
-quote. Check the axp-list archive at Red Hat.
-<P>
-<H2><A NAME="ss17.5">17.5 Threads</A>
-</H2>
-
-<P>When you receive errors that mention DECthreads you need to do the following:
-<UL>
-<LI> (re)move libpthread.so and libpthreads.so from the shared library directory</LI>
-<LI> <CODE>ln -sf /usr/shlib/libc.so /usr/shlib/libpthread.so/</CODE></LI>
-<LI> <CODE>ln -sf /usr/shlib/libc.so /usr/shlib/libpthreads.so/</CODE></LI>
-</UL>
-
-This problem is known to occur with recent Netscapes and with Adobe Acrobat 3.
-<P>
-<HR>
-<A HREF="FAQ-18.html">Next</A>
-<A HREF="FAQ-16.html">Previous</A>
-<A HREF="FAQ.html#toc17">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-18.html b/english/ports/alpha/faq/FAQ-18.html
deleted file mode 100644
index a9adc03ade3..00000000000
--- a/english/ports/alpha/faq/FAQ-18.html
+++ /dev/null
@@ -1,186 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Change Log</TITLE>
- <LINK HREF="FAQ-17.html" REL=previous>
- <LINK HREF="FAQ.html#toc18" REL=contents>
-</HEAD>
-<BODY>
-Next
-<A HREF="FAQ-17.html">Previous</A>
-<A HREF="FAQ.html#toc18">Contents</A>
-<HR>
-<H2><A NAME="s18">18. Change Log</A></H2>
-
-<P>
-<DL>
-<DT><B>v1.1.5:</B><DD><P>A number of new FAQ's in "Known Bugs and Workarounds".
-Linking around pthreads libraries to run DU software.
-Martin O.'s final contribution to the Jensen section.
-Updates in "Where to get Alpha Hardware".
-Dropped the section on documentation.
-<DT><B>v1.1.4:</B><DD><P>Stig Telfer's chapter on Ruffian.
-Rick Taylor's info on AS200.
-Additional update on X support.
-Commercial X-servers from MetroLink and XiGraphics.
-New chapter "How fast is the Alpha?".
-Removed chapter "Acknowledgements".
-<DT><B>v1.1.3:</B><DD><P>Patch to Jensen section (Martin O.)
-Applixware for Alpha.
-Andy Isaacson's update on X support.
-Some updates to list of resellers.
-Started chapter on AS200.
-Stampede disribution.
-Problem with keystrokes in vi.
-Links to 164RX, 264DP boards.
-Spelling fixes, repaired some links.
-<DT><B>v1.1.2:</B><DD><P>Small patch to Jensen section (Martin O.)
-Update on Swedish resellers by Knut Markus Johansson.
-Deutsche Linux Distribution. Note on Red Hat 5.0.
-URL for Hugo van der Kooij's Kernel Build HOWTO.
-Jay Estabrooks' table of system types.
-<DT><B>v1.1.1:</B><DD><P>Minor changes: spelling fixes, repaired some links.
-<DT><B>v1.1:</B><DD><P>(never released)<BR>
-Dropped some FAQ's that were relevant to ancient
-distributions. Added FAQ's about PC164 clock, Milo/modem.
-Info/links for PC164LX/SX/UX. Miata now
-listed under supported systems.
-Mentions partial support for Millenium II in X11.
-<DT><B>v1.08:</B><DD><P>NAG Fortran under commercial applications.
-Ditto Net/Equater by BSC Software.
-Ditto Clio E-Mail package.
-A Reference to Harvey J. Stein's Patch Notes.
-<DT><B>v1.07:</B><DD><P>Updated Jensen section (Martin Ostermann).
-Added Jay Estabrook's description of clock problems.
-Updated David Mosberger-Tang's E-mail.
-<DT><B>v1.06:</B><DD><P>Added Red Hat as supplier for Motif.
-Added ReQAS to list of hardware suppliers.
-<DT><B>v1.05:</B><DD><P>Added XVScan, Picture Elements to list of commercial applications.
-Added PSDS to list of hardware suppliers.
-Fixed some broken links.
-<DT><B>v1.04:</B><DD><P>Added Geerten Kuiper as new maintainer.
-Added info on comp.os.linux.alpha.
-Combined em86 references in new chapter.
-<DT><B>v1.03:</B><DD><P>Added info on X server for Jensen (Martin Osterman).
-<DT><B>v1.02:</B><DD><P>Added Italian company Bergamo Perego and updated BVC entry.
-<DT><B>v1.01:</B><DD><P>Added Finnish company PSS-Trade.  Fixed voice number of
-AVNET Italy.  Mention em86 in "Commercial Applications"
-section as well as in several other places.
-<DT><B>v1.0:</B><DD><P>Mention Debian as a (forthcoming) Linux/Alpha distributor.
-Turn Motif section into section listing commercial
-applications for Linux/Alpha.  Add note that
-Acknowledgment section is out of date.  Add pointer to
-Alpha Compiler Cookbook to section on on-line documentation
-and on-line Alpha architecture handbook.  Add Parsys to
-list of UK resellers.  Add Nirocenta to list of Swedish
-resellers.  Add mention of ALPHAbook1, Miata, and (Demi-)Sable.
-Various other fixes.  
-<DT><B>v0.992:</B><DD><P>Added section on how to run Netscape on Linux/Alpha
-(contributed by Gerald Anderson).
-<DT><B>v0.991:</B><DD><P>Removed Kenetics info.  Moved UDB links from
-DEC to http://www.annex.co.uk/systems/udb.html.
-<DT><B>v0.99:</B><DD><P>Jensen update by Martin.  Added Enorex info.
-<DT><B>v0.98:</B><DD><P>Added scanner entry to list of supported devices.
-Fixed link to AXPpci33 info.  Updated info on
-available Red Hat and Craftworks distributions.
-<DT><B>v0.97:</B><DD><P>Document need of LD_BIND_NOW for gdb.
-<DT><B>v0.96:</B><DD><P>More networking and ISDN drivers (info by Thomas
-Bogendoerfer).  Updated XL entry in respect to
-Matrox Millenium.
-<DT><B>v0.95:</B><DD><P>Added Finish vendor.  Update C++ info.  Added Quake info.
-<DT><B>v0.94:</B><DD><P>Updated Jensen section (by Martin).  Updated graphics card
-section to be more explicit about TGA (thanks to Jay).
-<DT><B>v0.93:</B><DD><P>Status update on ELF.  Update on XL Turbo.  Added pointer
-to DEC semiconductor on-line library.  Added Motif
-info.
-<DT><B>v0.92:</B><DD><P>Added section on common porting problems (thanks to
-Jay Estabrook for the nifty title!).  More pointers
-to online docs.
-Qlogic ISP1020 driver works fine now (requires kernel 2.0.1
-or newer). BusLogic SCSI cards, reportedly work, too.
-<DT><B>v0.91:</B><DD><P>Updated XL section with info by Jay Estabrook (all errors
-are mine).
-<DT><B>v0.9:</B><DD><P>Jensen section rewritten (and now maintained) by Martin.
-Added DEC Australia contact.  Added Aspen Timberline as an
-alias for eb164. The isp1020 SCSI driver has been reported
-to work with Linux/Alpha.
-<DT><B>v0.8:</B><DD><P>Added UK reseller.  Added info on Crafwork Linux.
-Updated price for Kentics boards (it's cheaper now).
-Various other minor fixes and updates.
-<DT><B>v0.77:</B><DD><P>Explain unaligned access faults in "Known Bugs and Workarounds"
-section.  Updated pricing and availability of PCI 64/164
-boards.  Added section on on-line documentation.
-<DT><B>v0.76:</B><DD><P>Lots of UDB info is available at the
-<A HREF="http://www.digital.com/info/udb">UDB InfoCenter</A>, so
-all UDB links now point to that URL.
-Updated section on supported drivers (de500 Fast Ethernet
-card works as well).  Added info on Japanese Linux/Alpha
-mailing list and ftp site.  Updated section on German
-Alpha resellers.
-<DT><B>v0.75:</B><DD><P>Updated "International Technology Sales" info and
-recommendation to avoid BLADE (thanks, Jon!).
-Removed section listing CD-ROM vendors---there are
-just too many of them to keep up with this FAQ.
-<DT><B>v0.74:</B><DD><P>Added to "Known Bugs and Workarounds" section.
-<DT><B>v0.73:</B><DD><P>Workaround for IDE interrupt-loosing problem added.
-IBM tokenring driver added to list of working drivers.
-<DT><B>v0.72:</B><DD><P>Rewrote motherboard section, added Alpha PCI info.
-Added one or two vendors.
-<DT><B>v0.71:</B><DD><P>Expanded Platform 2000.
-<DT><B>v0.70:</B><DD><P>Various updates to the list of French resellers.  Added
-Swiss reseller.  Added
-section with CD-ROM resellers.  Updated performance section
-for Noname based on data received from Francois Potard.
-Section on Noname boards now contains the caveat that
-ARC can't boot in 8MB.
-<DT><B>v0.51:</B><DD><P>The X11 TGA server is now available as a Beta version!
-See Section 
-<A HREF="FAQ-1.html#What State Is Linux/Alpha In">What State Is Linux/Alpha In</A>
-.
-Added info on Kenetics Technology board.
-<DT><B>v0.50:</B><DD><P>Linux now runs on the Alpha XL and EB164!
-Support for IDE CD-ROMs (ATAPI) has been added.
-SRM section is now a separate HOWTO.  Most sections
-got revised.
-<DT><B>v0.42:</B><DD><P>Updated <CODE>aboot</CODE> documentation to reflect version 0.3.
-<DT><B>v0.41:</B><DD><P>Added Austrian Alpha vendor.  Updated list of known bugs
-and workarounds (fully compliant IEEE math is now possible if
-one desires so).
-<DT><B>v0.40:</B><DD><P>ewrk3 Ethernet driver added to the list of working
-drivers.
-<DT><B>v0.39:</B><DD><P>Updated US vendor section (contributed by Maddog).
-<DT><B>v0.38:</B><DD><P>Various minor updates throughout the document.
-<DT><B>v0.37:</B><DD><P>
-<UL>
-<LI>Started list of known bugs/workarounds.</LI>
-<LI>Mention <CODE>aboot-0.2</CODE> in Jensen section.</LI>
-</UL>
-<DT><B>v0.36:</B><DD><P>
-<UL>
-<LI> Added Jensen installation information.</LI>
-<LI> Joystick driver now works too (as a module).</LI>
-<LI> Universal Desktop Box is now supported! (See Section
-<A HREF="FAQ-5.html#Supported Systems">Supported Systems</A>
-.)</LI>
-<LI> Updated Section 
-<A HREF="FAQ-13.html#Where Do I Get Linux Software">Where Do I Get Linux Software</A>
-.</LI>
-<LI> Updated entry for Red Hat as the first 50 or so packages are
-available now.</LI>
-<LI> Updated Section 
-<A HREF="FAQ-5.html#Supported Systems">Supported Systems</A>
-.</LI>
-<LI> Expanded discussion on how to boot Linux with the
-SRM firmware (Section 
-<A HREF="FAQ-15.html#How To Boot Linux/Alpha">How To Boot Linux/Alpha</A>
-).</LI>
-</UL>
-</DL>
-<P>
-<HR>
-Next
-<A HREF="FAQ-17.html">Previous</A>
-<A HREF="FAQ.html#toc18">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-19.html b/english/ports/alpha/faq/FAQ-19.html
deleted file mode 100644
index 76cfce4ebc7..00000000000
--- a/english/ports/alpha/faq/FAQ-19.html
+++ /dev/null
@@ -1,181 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Change Log</TITLE>
- <LINK HREF="FAQ-18.html" REL=previous>
- <LINK HREF="FAQ.html#toc19" REL=contents>
-</HEAD>
-<BODY>
-Next
-<A HREF="FAQ-18.html">Previous</A>
-<A HREF="FAQ.html#toc19">Contents</A>
-<HR>
-<H2><A NAME="s19">19. Change Log</A></H2>
-
-<P>
-<DL>
-<DT><B>v1.1.4:</B><DD><P>Stig Telfer's chapter on Ruffian.
-Rick Taylor's info on AS200.
-Additional update on X support.
-Commercial X-servers from MetroLink and XiGraphics.
-New chapter "How fast is the Alpha?".
-Removed chapter "Acknowledgements".
-<DT><B>v1.1.3:</B><DD><P>Patch to Jensen section (Martin O.)
-Applixware for Alpha.
-Andy Isaacson's update on X support.
-Some updates to list of resellers.
-Started chapter on AS200.
-Stampede disribution.
-Problem with keystrokes in vi.
-Links to 164RX, 264DP boards.
-Spelling fixes, repaired some links.
-<DT><B>v1.1.2:</B><DD><P>Small patch to Jensen section (Martin O.)
-Update on Swedish resellers by Knut Markus Johansson.
-Deutsche Linux Ditribution. Note on Red Hat 5.0.
-URL for Hugo van der Kooij's Kernel Build HOWTO.
-Jay Estabrooks' table of system types.
-<DT><B>v1.1.1:</B><DD><P>Minor changes: spelling fixes, repaired some links.
-<DT><B>v1.1:</B><DD><P>(never released)<BR>
-Dropped some FAQ's that were relevant to ancient
-distributions. Added FAQ's about PC164 clock, Milo/modem.
-Info/links for PC164LX/SX/UX. Miata now
-listed under supported systems.
-Mentions partial support for Millenium II in X11.
-<DT><B>v1.08:</B><DD><P>NAG Fortran under commercial applications.
-Ditto Net/Equater by BSC Software.
-Ditto Clio E-Mail package.
-A Reference to Harvey J. Stein's Patch Notes.
-<DT><B>v1.07:</B><DD><P>Updated Jensen section (Martin Ostermann).
-Added Jay Estabrook's description of clock problems.
-Updated David Mosberger-Tang's E-mail.
-<DT><B>v1.06:</B><DD><P>Added Red Hat as supplier for Motif.
-Added ReQAS to list of hardware suppliers.
-<DT><B>v1.05:</B><DD><P>Added XVScan, Picture Elements to list of commercial applications.
-Added PSDS to list of hardware suppliers.
-Fixed some broken links.
-<DT><B>v1.04:</B><DD><P>Added Geerten Kuiper as new maintainer.
-Added info on comp.os.linux.alpha.
-Combined em86 references in new chapter.
-<DT><B>v1.03:</B><DD><P>Added info on X server for Jensen (Martin Osterman).
-<DT><B>v1.02:</B><DD><P>Added Italian company Bergamo Perego and updated BVC entry.
-<DT><B>v1.01:</B><DD><P>Added Finnish company PSS-Trade.  Fixed voice number of
-AVNET Italy.  Mention em86 in "Commercial Applications"
-section as well as in several other places.
-<DT><B>v1.0:</B><DD><P>Mention Debian as a (forthcoming) Linux/Alpha distributor.
-Turn Motif section into section listing commercial
-applications for Linux/Alpha.  Add note that
-Acknowledgment section is out of date.  Add pointer to
-Alpha Compiler Cookbook to section on on-line documentation
-and on-line Alpha architecture handbook.  Add Parsys to
-list of UK resellers.  Add Nirocenta to list of Swedish
-resellers.  Add mention of ALPHAbook1, Miata, and (Demi-)Sable.
-Various other fixes.  
-<DT><B>v0.992:</B><DD><P>Added section on how to run Netscape on Linux/Alpha
-(contributed by Gerald Anderson).
-<DT><B>v0.991:</B><DD><P>Removed Kenetics info.  Moved UDB links from
-DEC to http://www.annex.co.uk/systems/udb.html.
-<DT><B>v0.99:</B><DD><P>Jensen update by Martin.  Added Enorex info.
-<DT><B>v0.98:</B><DD><P>Added scanner entry to list of supported devices.
-Fixed link to AXPpci33 info.  Updated info on
-available Red Hat and Craftworks distributions.
-<DT><B>v0.97:</B><DD><P>Document need of LD_BIND_NOW for gdb.
-<DT><B>v0.96:</B><DD><P>More networking and ISDN drivers (info by Thomas
-Bogendoerfer).  Updated XL entry in respect to
-Matrox Millenium.
-<DT><B>v0.95:</B><DD><P>Added Finish vendor.  Update C++ info.  Added Quake info.
-<DT><B>v0.94:</B><DD><P>Updated Jensen section (by Martin).  Updated graphics card
-section to be more explicit about TGA (thanks to Jay).
-<DT><B>v0.93:</B><DD><P>Status update on ELF.  Update on XL Turbo.  Added pointer
-to DEC semiconductor on-line library.  Added Motif
-info.
-<DT><B>v0.92:</B><DD><P>Added section on common porting problems (thanks to
-Jay Estabrook for the nifty title!).  More pointers
-to online docs.
-Qlogic ISP1020 driver works fine now (requires kernel 2.0.1
-or newer). BusLogic SCSI cards, reportedly work, too.
-<DT><B>v0.91:</B><DD><P>Updated XL section with info by Jay Estabrook (all errors
-are mine).
-<DT><B>v0.9:</B><DD><P>Jensen section rewritten (and now maintained) by Martin.
-Added DEC Australia contact.  Added Aspen Timberline as an
-alias for eb164. The isp1020 SCSI driver has been reported
-to work with Linux/Alpha.
-<DT><B>v0.8:</B><DD><P>Added UK reseller.  Added info on Crafwork Linux.
-Updated price for Kentics boards (it's cheaper now).
-Various other minor fixes and updates.
-<DT><B>v0.77:</B><DD><P>Explain unaligned access faults in "Known Bugs and Workarounds"
-section.  Updated pricing and availability of PCI 64/164
-boards.  Added section on on-line documentation.
-<DT><B>v0.76:</B><DD><P>Lots of UDB info is available at the
-<A HREF="http://www.digital.com/info/udb">UDB InfoCenter</A>, so
-all UDB links now point to that URL.
-Updated section on supported drivers (de500 Fast Ethernet
-card works as well).  Added info on Japanese Linux/Alpha
-mailing list and ftp site.  Updated section on German
-Alpha resellers.
-<DT><B>v0.75:</B><DD><P>Updated "International Technology Sales" info and
-recommendation to avoid BLADE (thanks, Jon!).
-Removed section listing CD-ROM vendors---there are
-just too many of them to keep up with this FAQ.
-<DT><B>v0.74:</B><DD><P>Added to "Known Bugs and Workarounds" section.
-<DT><B>v0.73:</B><DD><P>Workaround for IDE interrupt-loosing problem added.
-IBM tokenring driver added to list of working drivers.
-<DT><B>v0.72:</B><DD><P>Rewrote motherboard section, added Alpha PCI info.
-Added one or two vendors.
-<DT><B>v0.71:</B><DD><P>Expanded Platform 2000.
-<DT><B>v0.70:</B><DD><P>Various updates to the list of French resellers.  Added
-Swiss reseller.  Added
-section with CD-ROM resellers.  Updated performance section
-for Noname based on data received from Francois Potard.
-Section on Noname boards now contains the caveat that
-ARC can't boot in 8MB.
-<DT><B>v0.51:</B><DD><P>The X11 TGA server is now available as a Beta version!
-See Section 
-<A HREF="FAQ-1.html#What State Is Linux/Alpha In">What State Is Linux/Alpha In</A>
-.
-Added info on Kenetics Technology board.
-<DT><B>v0.50:</B><DD><P>Linux now runs on the Alpha XL and EB164!
-Support for IDE CD-ROMs (ATAPI) has been added.
-SRM section is now a separate HOWTO.  Most sections
-got revised.
-<DT><B>v0.42:</B><DD><P>Updated <CODE>aboot</CODE> documentation to reflect version 0.3.
-<DT><B>v0.41:</B><DD><P>Added Austrian Alpha vendor.  Updated list of known bugs
-and workarounds (fully compliant IEEE math is now possible if
-one desires so).
-<DT><B>v0.40:</B><DD><P>ewrk3 Ethernet driver added to the list of working
-drivers.
-<DT><B>v0.39:</B><DD><P>Updated US vendor section (contributed by Maddog).
-<DT><B>v0.38:</B><DD><P>Various minor updates throughout the document.
-<DT><B>v0.37:</B><DD><P>
-<UL>
-<LI>Started list of known bugs/workarounds.</LI>
-<LI>Mention <CODE>aboot-0.2</CODE> in Jensen section.</LI>
-</UL>
-<DT><B>v0.36:</B><DD><P>
-<UL>
-<LI> Added Jensen installation information.</LI>
-<LI> Joystick driver now works too (as a module).</LI>
-<LI> Universal Desktop Box is now supported! (See Section
-<A HREF="FAQ-5.html#Supported Systems">Supported Systems</A>
-.)</LI>
-<LI> Updated Section 
-<A HREF="FAQ-14.html#Where Do I Get Linux Software">Where Do I Get Linux Software</A>
-.</LI>
-<LI> Updated entry for Red Hat as the first 50 or so packages are
-available now.</LI>
-<LI> Updated Section 
-<A HREF="FAQ-5.html#Supported Systems">Supported Systems</A>
-.</LI>
-<LI> Expanded discussion on how to boot Linux with the
-SRM firmware (Section 
-<A HREF="FAQ-16.html#How To Boot Linux/Alpha">How To Boot Linux/Alpha</A>
-).</LI>
-</UL>
-</DL>
-<P>
-<HR>
-Next
-<A HREF="FAQ-18.html">Previous</A>
-<A HREF="FAQ.html#toc19">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-2.html b/english/ports/alpha/faq/FAQ-2.html
deleted file mode 100644
index ddfe2148e5a..00000000000
--- a/english/ports/alpha/faq/FAQ-2.html
+++ /dev/null
@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Are There Any Mailing Lists I Should Join?</TITLE>
- <LINK HREF="FAQ-3.html" REL=next>
- <LINK HREF="FAQ-1.html" REL=previous>
- <LINK HREF="FAQ.html#toc2" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-3.html">Next</A>
-<A HREF="FAQ-1.html">Previous</A>
-<A HREF="FAQ.html#toc2">Contents</A>
-<HR>
-<H2><A NAME="s2">2. Are There Any Mailing Lists I Should Join?</A></H2>
-
-<P> Yes, we suggest subscribing to the "axp-list" mailing list.  To
-subscribe, simply send mail with a subject of "subscribe" (no
-message-body) to: 
-<A HREF="mailto:axp-list-request@redhat.com">axp-list-request@redhat.com</A>.
-<P>
-<P> There's also the Debian-Alpha mailinglist. It's a must when you
-use that distribution, but it also carries discusssions on topics that
-Red Hat users might be interested in. Visit 
-<A HREF="http://www.debian.org">Debian home page</A> to subscribe.
-<P>
-<P> If you're curious to see what's going on in the Japanese
-Linux/Alpha scene, the "linux-alpha-jp" mailing list is for you.
-Subscribe to that list by sending mail to 
-<A HREF="mailto:majordomo-zagato@kuamp.kyoto-u.ac.jp">majordomo-zagato@kuamp.kyoto-u.ac.jp</A> with a body containing
-the line "subscribe linux-alpha-jp".  Be advised that many mails are
-written in Japanese (ISO-2022-JP).
-<P>
-<H2><A NAME="ss2.1">2.1 And How About NewsGroups?</A>
-</H2>
-
-<P> The group 
-<A HREF="news:comp.os.linux.alpha">comp.os.linux.alpha</A> started in june 1997. It should be available on
-most servers by now, and can also be read through 
-<A HREF="http://xp7.dejanews.com/qs.xp?QRY=comp.os.linux.alpha&amp;OP=dnquery.xp&amp;defaultOp=AND&amp;svcclass=dncurrent&amp;maxhits=20&amp;nofilt=1">DejaNews</A>.
-<P>
-<HR>
-<A HREF="FAQ-3.html">Next</A>
-<A HREF="FAQ-1.html">Previous</A>
-<A HREF="FAQ.html#toc2">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-3.html b/english/ports/alpha/faq/FAQ-3.html
deleted file mode 100644
index 1f397c9fb86..00000000000
--- a/english/ports/alpha/faq/FAQ-3.html
+++ /dev/null
@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: What's The Minimum Configuration To Run Linux/Alpha?</TITLE>
- <LINK HREF="FAQ-4.html" REL=next>
- <LINK HREF="FAQ-2.html" REL=previous>
- <LINK HREF="FAQ.html#toc3" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-4.html">Next</A>
-<A HREF="FAQ-2.html">Previous</A>
-<A HREF="FAQ.html#toc3">Contents</A>
-<HR>
-<H2><A NAME="s3">3. What's The Minimum Configuration To Run Linux/Alpha?</A></H2>
-
-<P> Linux/Alpha is known to run on machines with as little as 8MB of
-RAM and a 170MB harddisk.  In those 8MB of RAM, you can run
-Emacs-19.28 without swapping, but that's about it.  A system with 16MB
-RAM and 500MB is perfectly reasonable to work with, even when using
-X11. 32MB RAM and on the order of 1GB of disk should satisfy even
-power-hungry users, though, as usually is the case: the more the
-better.
-<P>
-<P> (Well, I guess one's perception of what is reasonable can change with
-time, and with DRAM prices. I know that by now many people would consider
-32MB the bare minimum, 64MB usable. Recent releases of Red Hat seem to need
-at least 24MB just to install...<BR>
-And you'll have a hard time looking for a hard disk smaller than 2GB.)
-<P>
-<P> Note that, though many Alpha mainboards support EIDE, performance is 
-reported to be unsatisfactory. SCSI is recommended.
-<P>
-<P>
-<HR>
-<A HREF="FAQ-4.html">Next</A>
-<A HREF="FAQ-2.html">Previous</A>
-<A HREF="FAQ.html#toc3">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-4.html b/english/ports/alpha/faq/FAQ-4.html
deleted file mode 100644
index 3742df1731f..00000000000
--- a/english/ports/alpha/faq/FAQ-4.html
+++ /dev/null
@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: How fast is the Alpha ?</TITLE>
- <LINK HREF="FAQ-5.html" REL=next>
- <LINK HREF="FAQ-3.html" REL=previous>
- <LINK HREF="FAQ.html#toc4" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-5.html">Next</A>
-<A HREF="FAQ-3.html">Previous</A>
-<A HREF="FAQ.html#toc4">Contents</A>
-<HR>
-<H2><A NAME="s4">4. How fast is the Alpha ?</A></H2>
-
-<P> This depends on the type of system you have, and what you are trying to do.
-<P>
-<P> The Alpha is a RISC processor: it has fewer and simpler instructions. Thus,
-at the same clockspeed, it will generally be slower than a CISC processor. But,
-being simpler, it will be easier to build processors that run at higher speeds.
-The fastest Alpha (now at 700MHz) will outpace the fastest Intel processor
-(450 MHz.) This will remain true for many years to come. (It will also be
-more expensive.)
-<P>
-<P> In BogoMIPS, Alpha's up to the 164 show a speed approximately equal to the
-clock frequency in MHz (like Intel's 486 and early Pentium processors.) The
-264 has a BM value of twice the clock speed (like Pentium MMX and higher.)<BR>
- This, however can not be taken as a true indication of the speed for
-real applications.
-<P>
-<P> RISC instructions are fewer and simpler, so you need to execute more of
-them to get the same amount of work done. On top of that, they are also larger.
-So, to keep your Alpha running at full speed, you need large caches and high
-memory bandwith. Most Alpha's have two levels of cache on chip, and the newer
-boards also provide wide (128 or 256 bit) memory busses. Some of the older
-Alpha systems, however, do suffer from lack of memory bandwith.
-<P>
-<P> The Alpha has earned itself a reputation for floating point performance.
-However, it takes a very good compiler and libraries to achieve the optimum.
-Until recently, this meant that the real numbercrunchers would often revert 
-to Digital Unix. Recently, though the compilers in the Open Source arena 
-still lag behind, large improvements have been made w.r.t. the libraries.
-Handcoded, highly optimized math libaries are available now from 
-<A HREF="http://people.frankfurt.netsurf.de/Joachim.Wesner/">http://people.frankfurt.netsurf.de/Joachim.Wesner/</A><P>
-<HR>
-<A HREF="FAQ-5.html">Next</A>
-<A HREF="FAQ-3.html">Previous</A>
-<A HREF="FAQ.html#toc4">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-5.html b/english/ports/alpha/faq/FAQ-5.html
deleted file mode 100644
index f2a02db4e6d..00000000000
--- a/english/ports/alpha/faq/FAQ-5.html
+++ /dev/null
@@ -1,264 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: What Systems Does Linux/Alpha Run On?</TITLE>
- <LINK HREF="FAQ-6.html" REL=next>
- <LINK HREF="FAQ-4.html" REL=previous>
- <LINK HREF="FAQ.html#toc5" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-6.html">Next</A>
-<A HREF="FAQ-4.html">Previous</A>
-<A HREF="FAQ.html#toc5">Contents</A>
-<HR>
-<H2><A NAME="Supported Systems"></A> <A NAME="s5">5. What Systems Does Linux/Alpha Run On?</A></H2>
-
-<P> The number of Alpha platforms that are supported by Linux is
-quickly increasing. The following is a list of workstations and
-motherboards that are known to work with Linux.
-If you have any corrections to the list, please send 
-<A HREF="mailto:geerten@bart.nl">us</A> mail.
-<P>
-<UL>
-<LI> <B>
-<A HREF="http://www.digital.com/alphaoem/alph esc.htm">The latest products</A></B> are the 164RX (next
-generation RUFFIAN), and 
-<A HREF="http://www.alpha-processor.com/product/alphapc264dp.asp/">264DP</A>,
-a dual processor 264 based board.
-        </LI>
-<LI> <B>
-<A HREF="http://www.usa.samsungsemi.com/products/browse/alphaboards.html">AlphaPC 164UX</A></B> is currently the high end board. Interestingly,
-this is not a Digital product. It was developed by Deskstation,
-(called RUFFIAN then), and is now being sold by Samsung. It supports
-speeds up to 800 MHz, and comes with on-board Ultra Wide SCSI
-(Symbios Logic 53C875), and 10/100 Mb Ethernet (Digital 21143).
-Like the 164SX an LX, it uses DIMMs (SDRAM) for memory, but
-it has 6 slots rather then 4.
-</LI>
-<LI> <B>
-<A HREF="http://www.dec.com/semiconductor/alpha/dsc-pc164lx.html">AlphaPC 164LX</A></B> is Digital's best bet. It's based on the
-<B>
-<A HREF="http://www.dec.com/semiconductor/alpha/dsc-pc164mb.html">AlphaPC 164</A></B>, but with speeds up to 600 MHz, and using
-DIMMs rather than SIMMs. (i.e. SDRAM rather then DRAM.)
-</LI>
-<LI> The low end of the current generation is the <B>
-<A HREF="http://www.digital.com/semiconductor/alpha/dsc-pc164sx.html">AlphaPC 164SX</A></B>. It uses the 21164PC variant of the
-Alpha microprocessor, at 400 or 533 MHz. This board is targeted
-at the NT Workstation market, but it will run Linux just fine.
-</LI>
-<LI> For a complete Workstation you may want to look at <B>
-<A HREF="http://www.workstation.digital.com/products/perswork.html">Miata</A> </B> (Personal Workstation). This comes with a Graphics
-Card (Powerstorm) for which X11 support does not (yet) exist,
-but Matrox Millennium is a popular replacement.
-</LI>
-<LI>  <B>
-<A HREF="http://www.workstation.digital.com/products/a600.html">Alcor</A> (AS600),
-<A HREF="http://www.workstation.digital.com/products/a500.html">Bret</A> (AS500)</B>.  The Alcor kernel
-is supposed to work fine with the AlphaStation 500 as
-well.  If you can confirm this, please let us know.
-</LI>
-<LI>  <B>EB164</B>.  The Aspen Timberline and Summit machines are
-similar to this machine/motherboard.  The EB164 has been replaced
-by the PC164 and it's successors (see above).
-</LI>
-<LI> <B>
-<A HREF="http://www.digital.com/semiconductor/alpha/dsc-pc64mb.html">Cabriolet</A> (aka AlphaPC64):</B>
-This is a PCI-bus based motherboards using the 21064 Alpha CPU.  
-It is more pricey than the 21066 systems but it does make for a
-real nice system and many third-party products are based on this
-design.  This board typically runs at 275MHz but some vendors sell
-an (overclocked) 300MHz version. It really is historical now, but
-you may be able to find them at very attractive prices.
-</LI>
-<LI> <B>
-<A HREF="http://www.digital.com/info/alphaserver/alphasrv1000/alphasrv1000_abstract.html">Mikasa</A></B> (AlphaServer 1000).  Noritake (AlphaServer 1000a)
-is supported as well, if you use kernels 2.0.30 or higher, with the
-appropriate patches. However, the builtin Cirrus graphics card
-is not (or very poorly) supported by X11.
-</LI>
-<LI> <B>
-<A HREF="http://www.workstation.digital.com/products/a200.html">Mustang</A> (AS200),
-<A HREF="http://www.workstation.digital.com/products/a250.html">M3</A> (AS250)
-<A HREF="http://www.workstation.digital.com/products/a255.html">???</A> (AS255)
-<A HREF="http://www.workstation.digital.com/products/a400.html">Avanti</A> (AS400)
-:</B> Linux now runs on all of these AlphaStations.
-The reason for clumping all these machines together is that they are
-all very similar to program.  In particular, they all can run one
-and the same kernel when booted using the same firmware.  Thus,
-when configuring a kernel, simply pick "Avanti" as the system type
-since that covers all of the above machines.
-</LI>
-<LI> 
-<A HREF="http://www.workstation.digital.com/products/alphaxl.html">XL</A>
-The XL machine is also know as the "Windows NT Dream Machine."
-Well, for what it's worth, (most of them) are perfectly happy
-running Linux.
-
-The regular XL is based on the 21064 CPU and runs either at 233
-or 266MHz with 512KB or 2MB of second level cache, respectively.
-
-The newer XL Turbo is based on the 21164A CPU and runs either at
-300 or 366MHz.  The Turbo always comes with 2MB of
-second-level cache.
-</LI>
-<LI><B>
-<A HREF="http://www.tadpole.com/products/alpha.html">ALPHAbook 1</A></B>
-The ALPHAbook 1 is a 21066A based notebook (the first and only
-portable Alpha, so far).  Linux works fine on this machine with
-a few extra patches.  An X server is available for this machine
-as well.
-</LI>
-<LI> <B>
-<A HREF="http://ftp.digital.com/pub/DEC/Alpha/systems/as1000/docs/SOC/Feb94/ch-1-b.txt">Jensen</A> (aka DEC 2000 aka DECpc AXP 150):</B>
-This is the oldest of all Alpha PCs and comes with an EISA bus.
-You probably don't want to buy such a machine new anymore since
-you can now get faster machines for less money.  However, it is
-not uncommon to get really amazing deals for these machines and
-a Jensen definitively would make a nice home box.  The
-firmware seems a little picky about what graphics card and SCSI
-controllers
-it wants, but if you're just looking for an affordable Alpha box,
-it might be worthwhile to look into it.
-</LI>
-<LI> <B>
-<A HREF="http://www.digital.de/orgs/OEM/products/boards/axppci33.html">Noname</A> (aka AXPpci33):</B>
-This is a PCI-bus based motherboard using the 21066 Alpha CPU
-(Low-Cost Alpha).  The core of the 21066 is the same as the 21064.
-The only difference is that the 21066 also has a memory and I/O
-controller integrated into the chip (which has the effect that the
-external interface is much simpler and therefore much cheaper).
-This board is available in a 166 and a 233MHz version.
-</LI>
-<LI> <B>
-<A HREF="http://www.annex.co.uk/systems/udb.html">UDB</A>:</B>
-Linux/Alpha also runs well on the Universal Desktop Box.
-(That's the box that's called "Multia" when it's running Windows NT.)
-The TGA graphics card and the builtin soundcard
-are supported.  The UDB is basically a Noname board with more
-hardware builtin and wrapped into a neat little box.  So when
-configuring a kernel for it, simply select the "Noname" system
-type.  The UDB currently provides the lowest-cost entry point
-into the Alpha world.
-</LI>
-<LI> <B>EB*:</B>
-Digital used to sell various other evaluation boards (e.g.,
-EB66, EB64+, etc.). Reportedly, Linux/Alpha may run on some of
-these.  But they were relatively pricey and should now be
-considered obsolete.</LI>
-</UL>
-<P>
-<H2><A NAME="ss5.1">5.1 Unsupported Systems</A>
-</H2>
-
-<P> Linux/Alpha is unlikely to support the TURBOchannel-based Alpha
-systems in the near (or any) future (this is the DEC 3000 series of
-workstations).  The reason for this is two-fold: first, these machines
-have an I/O system that is very different from PCI-based machines and
-therefore do not look anything like PCs (e.g., pretty much all drivers
-would have to be written from scratch).  Second, with the advent of
-PCI, the TURBOchannel is pretty much dead technology (for better or
-worse) and it just isn't all that much fun to develop software for
-dead technology (on the other hand, it may soon be possible to buy
-such systems cheaply, which would make them more interesting to Linux
-users, I suppose).
-<P>If you have such a machine and want to run a free OS, look for the
-*BSD's. At least one of them supports the 3000 series.
-<P>
-<H2><A NAME="ss5.2">5.2 Table</A>
-</H2>
-
-<P>The table below (one of Jay Estabrooks many invaluable contributions)
-may prove useful to select the right MILO/Kernel/bootfloppy for your
-system.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-The following table may be useful; sorry, but I haven't put in the "family" designations
-explicitly, but the groupings and MILOs are indicative, mostly.
-
---Jay++
-
-------------------------------------------------------------------------------- 
-Note: "AS" can equally stand for "AlphaStation" and "AlphaServer", though
-      both may *not* be available for a given platform.
-
-Hardware Type           Aliases                 MILO image
-=============           =======                 ==========
-
-DECpc 150               JENSEN                  N/A     
-DEC 2000 Model 300(S)   JENSEN
-DEC 2000 Model 500      CULZEAN
-
-AS 600                  ALCOR                   xlt-alcor
-
-AS 500                  MAVERICK,BRET           xlt-alcor
-XL-300                  XLT
-XL-366                  XLT
-XL-433                  XLT
-
-AS 200 4/*              MUSTANG                 avanti
-AS 205 4/*              LX3
-AS 250 4/*              M3
-AS 255 4/*              LX3+
-AS 300 4/*              MELMAC
-AS 400 4/*              AVANTI
-
-XL-233                  XL                      xl
-XL-266                  XL                      xl
-
-Personal Workstation    MIATA                   miata
-PWS 433a(u)
-PWS 500a(u)
-PWS 600a(u)
-
-AS 2100 (EV4)           SABLE                   N/A
-AS 2100 (EV5)           GAMMA-SABLE             N/A
-AS 2000 (EV4)           DEMI-SABLE
-AS 2000 (EV5)           DEMI-GAMMA-SABLE
-
-AS 1000 (EV4)           MIKASA                  N/A
-AS 1000 (EV5)           MIKASA-PRIMO            N/A
-
-AS 1000A (EV4)          NORITAKE                N/A
-AS 1000A (EV5)          NORITAKE-PRIMO          N/A
-AS 600A                 ALCOR-PRIMO
-AS 800                  CORELLE
-
-AXPpci33                NONAME                  udb-noname
-UDB                     MULTIA
-
-AlphaBook1 (laptop)     ALPHABOOK1              N/A
-
-AlphaPC64               CABRIOLET               cabrio
-AlphaPCI64
-
-AlphaPC164              PC164                   pc164
-
-AlphaPC164-LX           LX164                   lx164
-
-AlphaPC164-SX           SX164                   sx164
-
-EB164                   EB164                   eb164
-
-EB64+                   EB64+                   eb64p
-
-EB66+                   EB66+                   eb66p
-
-EB66                    EB66                    eb66
-
-AS 4100                 RAWHIDE                 N/A
-AS 4000                 RAWHIDE                 N/A
-AS 1200                 TINCUP                  N/A
-
--------------------------------------------------------------------------------
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>
-<HR>
-<A HREF="FAQ-6.html">Next</A>
-<A HREF="FAQ-4.html">Previous</A>
-<A HREF="FAQ.html#toc5">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-6.html b/english/ports/alpha/faq/FAQ-6.html
deleted file mode 100644
index 0ebe8f97311..00000000000
--- a/english/ports/alpha/faq/FAQ-6.html
+++ /dev/null
@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: So, what should I buy?</TITLE>
- <LINK HREF="FAQ-7.html" REL=next>
- <LINK HREF="FAQ-5.html" REL=previous>
- <LINK HREF="FAQ.html#toc6" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-7.html">Next</A>
-<A HREF="FAQ-5.html">Previous</A>
-<A HREF="FAQ.html#toc6">Contents</A>
-<HR>
-<H2><A NAME="s6">6. So, what should I buy?</A></H2>
-
-<H2><A NAME="ss6.1">6.1 Boards</A>
-</H2>
-
-<P> By now, there are a number of vendors that sell Alpha based
-motherboards.  First, there is Digital Semiconductor which provides
-reference designs and also sells so called "evaluation boards".  The
-most popular boards are currently the AlphaPC 164LX and SX. The PC164
-is also still available. Some resellers will offer nice deals on the PC64
-(Cabriolet).
-More info can be found at 
-<A HREF="http://www.digital.com/semiconductor/alpha/alpha.htm">Digital Semiconductor's</A> web site.
-<P>
-<P> 
-<A HREF="http://www.digital.de/oem/products/boards">Digital OEM</A> also offers Alpha
-boards: the low-end Noname (AXPpci33) and the higher-end Alpha PCI
-boards.  The Noname board was the first Alpha PCI motherboard sold by
-DEC and the section below describes it in detail.  The Alpha PCI
-boards are newer and also a lot more performant.  Volume shipment
-started April 96. Then came the generation PC164 (with variations such
-as SX, LX, RX) and now were looking forward to the 264DP.
-<P>
-<P> Samsung also produces boards, which are sold through it's subsidiary
-<A HREF="http://www.alpha-processor.com">Alpha Processor, Inc.</A>
-They tend to be very similar (identical?) to the Digital OEM offerings,
-but API seems to be targeted more towards the NT market. Don't let that
-worry you: they support Linux too.
-<P>
-<H2><A NAME="ss6.2">6.2 Systems</A>
-</H2>
-
-<P>In general, it's likely that buying a complete system will actually be
-cheaper than putting one together yourself.  This is especially true
-for many of the third-party systems and for Digital's XL machines.  If
-you add the costs of all the components to the price of the
-motherboard, you'll quickly find that it's difficult to beat those
-prices.  The good news about this is of course that it will also save
-you the trouble of having to find appropriate parts.
-A number of third-party vendors can be found through the 
-<A HREF="http://www.alphapowered.com">AlphaPowered</A> page. They typically
-offer configurations based on 164LX and 164SX boards, but some may have
-nice deals on the older boards as well.
-<P>
-<P>Linux will also run on some of Digital's server-class systems. Check the
-table in the previous chapter.
-<P>
-<H2><A NAME="ss6.3">6.3 Brief Alpha Systems Overview</A>
-</H2>
-
-<P> A brief (but unfortunately rather dated) introduction and overview of
-various Alpha systems and processors on the market can be found in 
-<A HREF="alpha-sys.html">Brief Alpha System Overview</A>.
-<P>
-<P>
-<HR>
-<A HREF="FAQ-7.html">Next</A>
-<A HREF="FAQ-5.html">Previous</A>
-<A HREF="FAQ.html#toc6">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-7.html b/english/ports/alpha/faq/FAQ-7.html
deleted file mode 100644
index 55db2fd69c0..00000000000
--- a/english/ports/alpha/faq/FAQ-7.html
+++ /dev/null
@@ -1,580 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Where Do I Get Alpha Hardware?</TITLE>
- <LINK HREF="FAQ-8.html" REL=next>
- <LINK HREF="FAQ-6.html" REL=previous>
- <LINK HREF="FAQ.html#toc7" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-8.html">Next</A>
-<A HREF="FAQ-6.html">Previous</A>
-<A HREF="FAQ.html#toc7">Contents</A>
-<HR>
-<H2><A NAME="s7">7. Where Do I Get Alpha Hardware?</A></H2>
-
-<P>First check the 
-<A HREF="http://www.alphapowered.com">AlphaPowered</A> page, which contains a list of vendors. If you prefer
-to deal with someone local, check the list below.
-<P>
-<H2><A NAME="ss7.1">7.1 Australia (country code: 61)</A>
-</H2>
-
-<P>
-<DL>
-<P>
-<DT><B>Digital Equipment Corporation</B><DD><P>Digital OEM Products <BR>
-410 Concord Road <BR>
-Rhodes, NSW 2138 <BR>
-<B>voice:</B> 2-561-5406 <BR>
-<B>fax:</B> 2-561-5777 <BR>
-<B>contact:</B> 
-<A HREF="mailto:allan@twoday.enet.dec.com">Allan Homulos</A> <BR>
-<P>
-<DT><B>Cetus Technology</B><DD><P>36 Bouvardia St<BR>
-Asquith<BR>
-<B>voice:</B> +61 2 9482 1566 <BR>
-<B>fax:</B> +61 2 9482 3781 <BR>
-<B>contact:</B> 
-<A HREF="mailto:lychan@cetustech.com.au">Leonard Chan</A> <BR>
-<B>web:</B> 
-<A HREF="http://www.cetustech.com.au">www.cetustech.com.au</A><P>
-<P>
-</DL>
-<P>
-<H2><A NAME="ss7.2">7.2 Austria (country code: 43)</A>
-</H2>
-
-<P>
-<DL>
-<P>
-<DT><B>EDV-Beratung DREYER</B><DD><P>Hintnausdorf 14 <BR>
-A-9300 St. Veit/Glan <BR>
-<B>voice:</B> 4212-90555-0 <BR>
-<B>fax:</B>   4212-90555-555 <BR>
-<B>cellular:</B> 664-2038200 <BR>
-<B>desc:</B> Sells various Alpha systems/boards.<BR>
-<B>contact:</B> 
-<A HREF="mailto:wdr@quant-x.com">wdr@quant-x.com</A> <BR>
-<B>web:</B> 
-<A HREF="http://www.quant-x.com">www.quant-x.com</A></DL>
-<P>
-<P>
-<H2><A NAME="ss7.3">7.3 Canada (country code: 1)</A>
-</H2>
-
-<P>
-<DL>
-<P>
-<DT><B>Hard Data Ltd.</B><DD><P>11060 - 166 Avenue,<BR>
-Edmonton, AB T5X 1Y3<BR>
-<B>voice:</B> (403) 456-1510<BR>
-<B>fax:</B> (403) 456-1510 or 457-1338<BR>
-<B>email:</B> 
-<A HREF="mailto:maurice@ellpspace.math.ualberta.ca">Maurice Hilarius</A> <BR>
-<B>desc:</B> DEC Technical OEM and business partner. Motherboards,
-Parts, and complete systems in various configurations are available.
-This Digital TOEM in Canada is both Linux friendly, and willing to
-sell to end-users.
-<P>
-</DL>
-<P>
-<P>
-<H2><A NAME="ss7.4">7.4 Finland (country code: 358)</A>
-</H2>
-
-<P>
-<DL>
-<P>
-<DT><B>Damicon Kraa</B><DD><P>Tekniikantie 17B <BR>
-02150 Espoo <BR>
-<B>voice:</B> 9 437 5557 <BR>
-<B>email:</B> 
-<A HREF="mailto:damicon@damicon.fi">damicon@damicon.fi</A><BR>
-<B>URL:</B> 
-<A HREF="http://www.damicon.fi/">www.damicon.fi/</A><BR>
-<B>contact:</B> Mikko Siren <BR>
-<P>
-<DT><B>PSS-Trade Ltd Oy</B><DD><P>Kauppanelio 4 <BR>
-60120 Seinajoki <BR>
-<B>voice:</B> 6 420 2000 <BR>
-<B>fax:</B> 6 420 2001 <BR>
-<B>email:</B> 
-<A HREF="mailto:alphasales@pss.fi">alphasales@pss.fi</A><BR>
-<B>contact:</B> Mr. 
-<A HREF="mailto:jp@pss.fi">Jukka Peltola</A><BR>
-<B>web:</B> 
-<A HREF="http://www.pss.fi/">http://www.pss.fi/</A><BR>
-<B>desc:</B> PSS-Trade is a OEM partner of Aspen Systems Inc. and is
-reselling both Aspen and Digital boards and systems (brand Citum) to
-Skandinavia.  Pre-installed Linux / DEC Unix / Win NT systems available.
-<P>
-</DL>
-<P>
-<P>
-<H2><A NAME="ss7.5">7.5 France (country code: 33) </A>
-</H2>
-
-<P>
-<DL>
-<DT><B>Digital Equipment France</B><DD><P>TOEM (C&amp;P BU) <BR>
-5, rue de la renaissance <BR>
-92187 Antony Cedex <BR>
-<B>voice:</B> 33-1 69 87 13 26 <BR>
-<B>fax:</B> 33-1 69 87 57 17 <BR>
-<B>main:</B> 33-1 69 87 51 11 <BR>
-<B>email:</B> 
-<A HREF="mailto:potard@atyisb.enet.dec.com">Francois Potard</A> <BR>
-<B>contact:</B> Francois POTARD
-<P>
-<DT><B>Alcove</B><DD><P>12 place Indira Ghandi <BR>
-92230 Gennevilliers <BR>
-<B>voice:</B> 33-1 47 33 82 84 <BR>
-<B>fax:</B> 33-1 47 33 76 98 <BR>
-<B>contact:</B> Mr Lucien Petit <BR>
-<B>desc:</B> Sells enterprise servers, LINUX only. <BR>
-<B>URL:</B> 
-<A HREF="http://www.alcove.fr">www.alcove.fr</A> <BR>
-<P>
-<DT><B>METROLOGIE</B><DD><P>Tour d'Asnieres <BR>
-4, avenue Laurent Cely <BR>
-92606 Asnieres Cedex <BR>
-<B>voice:</B> 33-1 40 80 90 00 <BR>
-<B>fax:</B> 33-1 40 86 04 85 <BR>
-<B>contact:</B> Mr Jean-Claude BACH <BR>
-<B>desc:</B> Master reseller, sells both boards and systems. <BR>
-<P>
-<DT><B>LUCCA</B><DD><P>37, Route de Versailles - Champlan <BR>
-91163 Longjumeau Cedex <BR>
-<B>voice:</B> 33-1 64 54 07 35 <BR>
-<B>contact:</B> Mr Giorgio FLORI <BR>
-<B>desc:</B> Sells boards.
-<P>
-<DT><B>E.S.C.</B><DD><P>8, avenue de l'Isle Saint Martin <BR>
-92737 NANTERRE Cedex <BR>
-<B>voice:</B> 33-1 69 85 31 00 <BR>
-<B>fax:</B> 33-1 69 85 58 21 <BR>
-<B>email:</B> 
-<A HREF="mailto:devins@escdirect.fr">devins@escdirect.fr</A> <BR>
-<B>URL:</B> 
-<A HREF="http://www.escdirect.fr">www.escdirect.fr</A> <BR>
-<B>contact:</B> Philippe DEVINS <BR>
-<B>desc:</B> Sells boards and systems. <BR>
-<P>
-<DT><B>DialEcrans</B><DD><P>70, rue Maurice Ripoche <BR>
-75014 Paris <BR>
-<B>voice:</B> 33-1 45 43 56 26 <BR>
-<B>fax:</B> 33-1 45 43 17 78 <BR>
-<B>email:</B> 
-<A HREF="mailto:dialec@dialup.francenet.fr">dialec@dialup.francenet.fr</A> <BR>
-<B>contact:</B> Philippe DEGOY <BR>
-<B>desc:</B> Sells boards. <BR>
-<P>
-<DT><B>Newtek</B><DD><P>8, rue de l'Esterel <BR>
-SILIC 583  <BR>
-94663 Rungis Cedex <BR>
-<B>voice:</B> 33-1 46 87 22 00 <BR>
-<B>fax:</B> 33-1 46 87 60 49 <BR>
-<B>contact:</B> Mr Roger MOCAER <BR>
-<B>desc:</B> Distributor for "Digital Semiconductor".
-Sells Alpha AXP Microprocessors and Evaluation boards.
-</DL>
-<P>Some integrators who resell complete solutions using the AXPpci33 and
-AlphaPC64 SBCs:
-<P>
-<DL>
-<P>
-<DT><B>A.G.M.D.</B><DD><P>778, rue Labat <BR>
-75018 Paris <BR>
-<B>voice:</B> 33-1 42 52 01 01  <BR>
-<B>fax:</B> 33-1 42 52 00 10 <BR>
-<B>contact:</B> Gilles Le Richom <BR>
-<B>desc:</B> Sells boards and systems. <BR>
-<P>
-<DT><B>Concept Informatique</B><DD><P>4, rue H. Lahuppe <BR>
-06220 Golfe Juan <BR>
-<B>voice:</B> 33 93 63 15 55 <BR>
-<B>fax:</B> 33 93 63 71 04 <BR>
-<B>contact:</B> Thomas AIME <BR>
-<B>desc:</B> Sells boards and systems. <BR>
-<P>
-<DT><B>GETEK</B><DD><P>113, rue Aristide Briand <BR>
-91401 Orsay Cedex <BR>
-<B>voice:</B> 33-1 60 14 44 32 <BR>
-<B>fax:</B> 33-1 69 31 35 82 <BR>
-<B>contact:</B> Dan COSTOVICI <BR>
-<B>desc:</B> Sells systems. <BR>
-<P>
-</DL>
-<P>
-<P>
-<H2><A NAME="ss7.6">7.6 Germany (country code: 49) </A>
-</H2>
-
-<P>
-<DL>
-<P>
-<DT><B>ixsoft</B><DD><P><B>web:</B> 
-<A HREF="http://www.ixsoft.de">http://www.ixsoft.de</A><BR>
-<B>desc:</B> Alpha-Systems (Linux preinstalled) and -components. 
-<P>
-<DT><B>DELEKTRON Datensysteme GbR</B><DD><P>Landwehrstra&szlig;e 32b <BR>
-80336 M&uuml;nchen <BR>
-<B>voice:</B> (089) 59 88 51 <BR>
-<B>web:</B> 
-<A HREF="http://www.delektron.de">http://www.delektron.de</A> <BR>
-<B>desc:</B> Alpha-components
-<P>
-<DT><B>Quant-X</B><DD><P>EDV-beratung DREYER (see the Austrian section) can also be 
-reached in Germany. <BR>
-<B>voice:</B> +49-89-21939-181 <BR>
-<B>fax:</B>   +49-89-21939-182 <BR>
-<P>
-<DT><B>RCH</B><DD><P>Computer-Gro&szlig;handel <BR>
-Dieter Rimmler <BR>
-Zussdorfer Stra&szlig;e 67 <BR>
-D-88271 Wilhelmsdorf <BR>
-<B>voice:</B> +49 7503 9300-0 <BR>
-<B>fax:</B> +49 7503 930050 <BR>
-<P>
-<DT><B>Schell Computersysteme</B><DD><P>Zehntwiesenstra&szlig;e 7 <BR>
-76275 Ettlingen <BR>
-<B>voice:</B> 07243-37700 <BR>
-<B>fax:</B>   07243-377039 <BR>
-<B>email:</B> 
-<A HREF="mailto:sales@schell.de">mailto:sales@schell.de</A> <BR>
-<B>desc:</B> Alpha based components and complete systems based on 
-Samsung boards.<BR>
-<P>
-<DT><B>Scholz Elektronik</B><DD><P>Freisch&uuml;tzstra&szlig;e 94 <BR>
-D-81927 M&uuml;nchen <BR>
-<B>voice:</B> (089) 957-2430 <BR>
-<B>fax:</B>   (089) 957-24333 <BR>
-<B>desc:</B> Scholz Elektronik is reselling both Aspen and Digital
-boards.<BR>
-<P>
-</DL>
-<P>
-<H2><A NAME="ss7.7">7.7 Hong Kong (country code: 852) </A>
-</H2>
-
-<P>
-<DL>
-<P>
-<DT><B>Genesis Systems Int'l ltd.</B><DD><P>7/F., Honytex Building<BR>
-22 Ashley Road, T. S. T. Kowloon, Hong Kong<BR>
-<B>voice:</B>  +852 2815 0728<BR>
-<B>fax:</B>    +852 2815 0729<BR>
-<B>web:</B> 
-<A HREF="http://www.genesis.com.hk/">http://www.genesis.com.hk/</A><BR>
-<B>E-mail</B> 
-<A HREF="mailto:info@genesis.com.hk">mailto:info@genesis.com.hk</A><BR>
-<B>desc:</B> Provides 21164SX and LX based Alpha Linux servers.
-<P>
-</DL>
-<P>
-<H2><A NAME="ss7.8">7.8 Italy (country code: 39) </A>
-</H2>
-
-<P>
-<DL>
-<P>
-<DT><B>Avnet EMG</B><DD><P>Via Novara 570<BR>
-I-20153 Milano<BR>
-<B>voice:</B>  (02) 381901<BR>
-<B>fax:</B>    (02) 3800 2988<BR>
-<B>contact:</B> Mr. Bernardini<BR>
-<B>desc:</B> Industrial Distributor for all Digital SBCs (single-board
-computers).  Can sell Noname systems as well as other board-level
-products in small volumes.
-<P>
-<DT><B>Bergamo Jolly srl</B><DD><P>Via Baertsch, 4 <BR>
-I-24100 Bergamo Bg <BR>
-<B>voice:</B> (035) 4124004 <BR>
-<B>fax:</B> (035) 4124528 <BR>
-<B>URL:</B> 
-<A HREF="http://www.jollybg.com/">www.jollybg.com/</A> <BR>
-<B>contact:</B> 
-<A HREF="mailto:sales@jollybg.com">Roberto Perego</A> <BR>
-<B>desc:</B> Reseller for Digital boards, barebones and complete systems.
-Distributor for clone 21164 and 21264 systems.
-<P>
-<DT><B>Unidata Srl</B><DD><P>Via S. Damaso 20<BR>
-I-00165 Rome<BR>
-<B>contact:</B> 
-<A HREF="mailto:pab@uni.net">Paolo Bevilacqua</A><BR>
-<B>voice:</B> (06) 3938 7319<BR>
-<B>fax:</B>   (06) 3936 6949<BR>
-<B>web:</B> 
-<A HREF="http://www.unidata.it">www.unidata.it</A><BR>
-<B>email:</B> 
-<A HREF="mailto:info@unidata.it">info@unidata.it</A><BR>
-<B>desc:</B> Unidata Srl is a business partner of DEC Italy. This means
-that they have all the DEC Alpha boards (Noname and newer) available,
-barebones or assembled in complete systems.<BR>
-<P>
-</DL>
-<P>
-<P>
-<H2><A NAME="ss7.9">7.9 Japan (country code: 81) </A>
-</H2>
-
-<P>
-<DL>
-<DT><B>Frontier Kojiro</B><DD><P><B>voice:</B> 820-53-1358 <BR>
-<B>fax:</B>   820-52-5565 <BR>
-<B>desc:</B> Sells Noname systems running Windows NT. <BR>
-</DL>
-<P>
-<P>
-<H2><A NAME="ss7.10">7.10 Netherlands (country code: 31)</A>
-</H2>
-
-<P>
-<DL>
-<DT><B>ReQuest Automation Services b.v.</B><DD><P>Postbus 182, 1400 AD  Bussum<BR>
-Energiestraat 23a <BR>
-1411 AR  Naarden <BR>
-<B>voice:</B> 035-6949441 <BR>
-<B>fax:</B>   035-6946202 <BR>
-<B>web:</B>   
-<A HREF="http://www.request.nl">www.request.nl</A>
-<B>email:</B>   
-<A HREF="mailto:sales@request.nl">sales@request.nl</A></DL>
-<P>
-<P>
-<H2><A NAME="ss7.11">7.11 Sweden (country code: 46) </A>
-</H2>
-
-<P>
-<DL>
-<DT><B>Digital Equipment AB</B><DD><P>Tommy Danielsson <BR>
-Allen 6 <BR>
-172 89 Sundbyberg <BR>
-<B>voice:</B> 8-6297980 (direct) or 8-6298000 (operator) <BR>
-<B>email:</B> 
-<A HREF="mailto:danielsson.tommy@a1stkai1.stkmts.mts.dec.com">Tommy Danielsson</A> <BR>
-<B>x400:</B> C=se;A=400net;P=digital;S=Danielsson;G=Tommy <BR>
-<P>
-<DT><B>Ericsson Components Distribution</B><DD><P>164 81 Kista <BR>
-<B>voice:</B> +46 (0)8-757 53 44 <BR>
-<B>contact:</B> Jan Pettersson <BR>
-<B>desc:</B> importer of digital hardware parts. Sells 164SX boards, 21164PC
-processors, Axxion DL-17 cases, etc.
-<P>
-<DT><B>Trade 4 Future</B><DD><P>Gammelstadsv. 2 <BR>
-Gammelstadens Fabriker B:3 <BR>
-415 02 Gothenburg <BR>
-<B>voice:</B> +46 (0)31 84 17 50 <BR>
-<B>fax:</B> +46 (0)31 84 72 40 <BR>
-<B>desc:</B> Sells 164SX boards, 21164PC
-processors, Axxion DL-17 cases, etc.
-<P>
-</DL>
-<P>
-<P>
-<H2><A NAME="ss7.12">7.12 Switzerland (country code: 41)</A>
-</H2>
-
-<P>
-<DL>
-<DT><B>DEC Digital Equipment Corporation AG</B><DD><P>&Uuml;berlandstrasse 1 <BR>
-Postfach <BR>
-8600 D&uuml;bendorf <BR>
-<B>voice:</B> +1 801 21 11 <BR>
-<B>fax:</B> +1 801 23 23 <BR>
-<B>contact:</B> 
-<A HREF="mailto:ivo.portmann@zuo.mts.dec.com">Ivo Portmann</A></DL>
-<P>
-<P>
-<H2><A NAME="ss7.13">7.13 U.K. (country code: 44)</A>
-</H2>
-
-<P>
-<DL>
-<DT><B>Compusys Ltd</B><DD><P>58 Edison Road <BR>
-Rabans Lane Industrial Estate <BR>
-Aylesbury <BR>
-Bucks <BR>
-HP19 3TE <BR>
-<B>voice:</B> 01296 505100 <BR>
-<B>fax:</B> 01296 24165 <BR>
-<B>contact:</B> 
-<A HREF="mailto:Andy@compusys.co.uk">Andy Pitt</A> <BR>
-<B>descrip:</B> We are now able to offer systems based on a range of
-Alpha's from the 166MHz 21066 to the 266MHz 21164 system. Our core
-business is based on building finished CE marked systems to customer
-specifications.
-<P>
-<DT><B>Parsys Ltd</B><DD><P>Boundary House <BR>
-Boston Road<BR>
-London<BR>
-W7 2QE <BR>
-<B>voice:</B> 7000 PARSYS (727797) <BR>
-<B>fax:</B> 181 579 8365 <BR>
-<B>contact:</B> 
-<A HREF="mailto:sales@parsys.co.uk">sales@parsys.co.uk</A> <BR>
-<B>web:</B> 
-<A HREF="http://www.parsys.com/">http://www.parsys.com</A><BR>
-<B>descrip:</B> Workstations for Linux/NT/Digital UNIX
-using AXP 21164A 366/433/500 MHz processors.
-Clustered systems based on the above processors,
-message passing over 100 Mb/s Ethernet 
-or switched interconnects at speeds up to 1.3Gb/s.
-</DL>
-<P>
-<P>
-<P>
-<H2><A NAME="ss7.14">7.14 U.S. (country code: 01)</A>
-</H2>
-
-<P> The listings in this section are limited to vendors that are
-willing and capable to sell Linux/Alpha boxes both in large and small
-quantities, and are willing to accept credit card orders or checks as
-well as Purchase Orders.  You can expect that these companies have at
-least heard the word "Linux" before and that they sell at least one
-type of Linux-capable systems.
-<P>Please send additional requests for listings to 
-<A HREF="mailto:maddog@zk3.dec.com">maddog</A>, with the subject line "YET ANOTHER
-GREAT VENDOR OF LINUX ALPHA SYSTEMS" (in all caps, to attract the
-over-worked maddog's attention).  He will appreciate it if you will
-give in your email <EM>all</EM> of your contact information and an
-indication that you meet the above-stated criteria for this list.
-<P>
-<P>
-<DL>
-<P>
-<DT><B>Aspen Systems Inc.</B><DD><P>4026 Youngfield St. <BR>
-Wheat Ridge CO 80033 <BR>
-<B>voice:</B> (303) 431-4606 <BR>
-<B>email:</B> 
-<A HREF="mailto:randyp@aspsys.com">randyp@aspsys.com</A><BR>
-<B>URL:</B> 
-<A HREF="http://www.aspsys.com">http://www.aspsys.com</A><BR>
-<B>desc:</B>  Aspen Systems Inc is a Digital OEM partner who
-engineers and manufactures motherboards based upon the 
-21064 and 21164 ALPHA processors.  
-Linux is supported on multiple models currently.
-<P>
-<DT><B>AVNET</B><DD><P><B>voice:</B> 1-800-426-7999 <BR>
-<B>desc:</B> AVNET sells boards and systems, both in small quantities and
-large quantities.
-<P>
-<DT><B>BTG</B><DD><P><B>voice:</B> 1-800-449-4228, (703) 714-7204 <BR>
-<B>fax:</B> (703) 714-7204 <BR>
-<B>email:</B> 
-<A HREF="mailto:jbell@btg.com">jbell@btg.com</A> <BR>
-<B>URL:</B> 
-<A HREF="http://www.btg.com">http://www.btg.com</A><BR>
-<B>desc:</B> Sells boards and systems.
-<P>
-<DT><B>Carrera Computers, Inc.</B><DD><P>23181 Verdugo Drive <BR>
-Building 101 <BR>
-Laguna Hills, CA  92653 <BR>
-<B>voice:</B> 1-800-576-RISC <BR>
-<B>URL:</B> 
-<A HREF="http://www.carrera.com">http://www.carrera.com</A><BR>
-<B>email:</B> 
-<A HREF="mailto:carrera1@delphi.com">carrera1@delphi.com</A><BR>
-<B>desc:</B> Does not sell Noname boards, but does sell Cabriolet motherboards
-and complete systems.
-<P>
-<DT><B>DCG Computers</B><DD><P>35 Otterson Rd. <BR>
-Londonderry, NH 03053 <BR>
-<B>voice:</B> (603) 421-1800 <BR>
-<B>fax:</B> (603) 421-0911 <BR>
-<B>contact:</B> Steven Gaudet <BR>
-<B>URL:</B> 
-<A HREF="http://www.dcginc.com">http://www.dcginc.com</A><BR>
-<B>email:</B> 
-<A HREF="mailto:sjg@dcginc.com">Steven Gaudet</A><BR>
-<B>desc:</B> Both motherboards and complete systems in various configurations
-are available.
-<P>
-<DT><B>Enorex Microsystems, Inc.</B><DD><P>518-7 Old Post Road Suite #301<BR>
-Edison, NJ 08817 <BR>
-<B>voice:</B> (908) 1-764-5640<BR>
-<B>fax:</B> (908) 1-764-5641<BR>
-<B>URL:</B> 
-<A HREF="http://www.enorex.com">http://www.enorex.com</A><BR>
-<B>desc:</B> The UltraPC line is reported to work with
-Linux/Alpha.  Enorex sells systems with WNT only.  If you don't want to
-go through the trouble of having to install Linux yourself, you might want
-to consider buying from a vendor that sells systems with Linux preinstalled.
-<P>
-<DT><B>International Technology Sales</B><DD><P>500 North Cary-Algonquin Road <BR>
-Cary, Illinois 60013-2083 <BR>
-<B>voice:</B> (847) 639-0775 <BR>
-<B>fax:</B> (847) 639-0710 <BR>
-<B>URL:</B> 
-<A HREF="http://www.itsinfonet.com">http://www.itsinfonet.com</A> <BR>
-<B>email:</B> 
-<A HREF="mailto:its@itsinfonet.com">its@itsinfonet.com</A><BR>
-<B>desc:</B> DEC Technical OEM and business parter.  Sells various Alpha
-boards and systems.
-<P>
-<DT><B>Lodgepole Technology, Inc.</B><DD><P>10242 189th Court NE <BR>
-Redmond, Wa. 98052 <BR>
-<B>voice:</B> (206) 868-6889 <BR>
-<B>fax:</B> (206) 868-3753 <BR>
-<B>URL:</B> 
-<A HREF="http://www.lodgepole.com/">http://www.lodgepole.com/</A> <BR>
-<B>desc:</B> Sells boards and systems.
-<P>
-<DT><B>Bushey Virtual Construction</B><DD><P>951 S. Cypress St. Suite F <BR>
-La Habra, Ca. 90631 <BR>
-<B>voice:</B> (714) 447-3587 <BR>
-<B>fax:</B> (714) 447-1812 <BR>
-<B>URL:</B> 
-<A HREF="http://www.alpha-zone.com/">http://www.alpha-zone.com/</A> <BR>
-<B>email:</B> 
-<A HREF="mailto:sales@bvc.net">sales@bvc.net</A> <BR>
-<B>desc:</B> Sells boards and systems.
-<P>
-<DT><B>Nekotech</B><DD><P>102 Tide Mill Rd Suite 6 <BR>
-Hampton, NH 03842-2705 <BR>
-<B>voice:</B> 1-800-635-6895 <BR>
-<B>fax:</B> (603) 926-0301 <BR>
-<B>URL:</B> 
-<A HREF="http://www.alphapower.com">http://www.alphapower.com</A><BR>
-<B>desc:</B> Sells boards and systems.
-<P>
-<DT><B>Puget Sound Data Systems</B><DD><P><B>voice:</B> (425) 488-0710 <BR>
-<B>fax:</B> (425) 488-6414 <BR>
-<B>URL:</B> 
-<A HREF="http://www.psds.com">http://www.psds.com</A><BR>
-<B>email:</B> 
-<A HREF="mailto:scott@psds.com">scott@psds.com</A><BR>
-<B>desc:</B> Offers Digital Equipment full line of product and custom Alpha's
-based on Digital Semiconductor PC164 Motherboards and Digital Processors.
-<P>
-</DL>
-<P>
-<P>
-<H2><A NAME="ss7.15">7.15 Taiwan (country code: 886)</A>
-</H2>
-
-<P> 
-<DL>
-<P>
-<DT><B>Lumax International Corp. Ltd.</B><DD><P>7th Fl, 52, Sec. 3 <BR>
-Nan-Kang Road <BR>
-Taipei, Taiwan <BR>
-<B>voice:</B> 886-2-7883656 x.674 <BR>
-<B>fax:</B> 886-2-7883568 <BR>
-<B>contact:</B> Felix Huang <BR>
-<B>email:</B> 
-<A HREF="mailto:departd@mailer.lumax.com.tw">departd@mailer.lumax.com.tw</A> <BR>
-<B>desc:</B> Sells boards: Noname, Cabrios, EB164, etc.  Linux is not available
-pre-installed, but this is apparently something that is being worked
-on.
-</DL>
-<P>
-<P>
-<HR>
-<A HREF="FAQ-8.html">Next</A>
-<A HREF="FAQ-6.html">Previous</A>
-<A HREF="FAQ.html#toc7">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-8.html b/english/ports/alpha/faq/FAQ-8.html
deleted file mode 100644
index 5607a45e06b..00000000000
--- a/english/ports/alpha/faq/FAQ-8.html
+++ /dev/null
@@ -1,158 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Noname (AXPpci33) and Multia (UDB) </TITLE>
- <LINK HREF="FAQ-9.html" REL=next>
- <LINK HREF="FAQ-7.html" REL=previous>
- <LINK HREF="FAQ.html#toc8" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-9.html">Next</A>
-<A HREF="FAQ-7.html">Previous</A>
-<A HREF="FAQ.html#toc8">Contents</A>
-<HR>
-<H2><A NAME="Noname (AXPpci33)"></A> <A NAME="s8">8. Noname (AXPpci33) and Multia (UDB) </A></H2>
-
-<P> This section provides some more information on the Noname motherboard.
-There are some hints and tips that you might be interested in if you're
-considering putting together a system on your own.
-<P>First off, here is what the Noname board looks like: 
-<A HREF="http://ftp.digital.com/pub/DEC/axppci/small_pci33.gif">picture of Noname board</A>.
-<P>This section also includes standard benchmark performance results,
-which might help give you an idea of how a Noname system performs.
-<P>Before going out and purchasing such a machine, please be aware that
-the Noname really is a low-end machine and as such is relatively low
-performance. The Noname <EM>can</EM> make for a nice machine (especially
-together with a TGA graphics card), but be sure to run the
-applications you care about before making a purchase decision.  Rather
-then putting together a system based on this board, it is currently
-much cheaper to get a Universal Desktop Box (
-<A HREF="http://www.annex.co.uk/systems/udb.html">UDB</A>).  That box is basically a
-Noname with lots of very nice builtin hardware. The last UDB's are now
-being sold at $ 99,-.
-<P>
-<H2><A NAME="ss8.1">8.1 What Firmware Does Linux/Alpha Require?</A>
-</H2>
-
-<P> You will need the OSF/1 PALcode to run Linux.  Digital has made
-the firmware available for ftp so you can download the SRM console
-from 
-<A HREF="ftp://ftp.digital.com/pub/DEC/axppci">Digital's ftp site</A>. There are two serious
-drawbacks with the SRM console: it eats away 2-3MB of RAM and it
-<B>cannot</B> boot from IDE drives.  Fortunately, the free 
-<A HREF="milo.html">MILO</A> replacement firmware doesn't suffer from
-these problems.  Plus with MILO, you get all the sources!
-<P>
-<P>
-<H2><A NAME="ss8.2">8.2 What Do I Need To Watch Out For?</A>
-</H2>
-
-<P>
-<UL>
-<LI> <B> Keyboard </B>
-
-<P>If you plan on running DEC Unix (formerly known as OSF/1), you have
-to get a board with a PS/2 style connector.  On the other hand, it
-seems a lot easier/cheaper to find cases and keyboards for AT-style
-connectors.  (Nekotech seems to be shipping Noname motherboards with
-the PS/2 connectors on a slot-bracket which allows you to have the
-best of both worlds: a regular (cheap) AT-case without having to tie
-up a serial port for the mouse.)
-<P>The only difference between the PS/2 and AT-style keyboard
-interface is the keyboard <B>connector</B>. The electrical interface
-is identical.  In fact, you can buy AT to PS/2 converters in any
-computer shop for a few bucks.  The advantage of PS/2-style board is
-that there is a second connector that can be used for a PS/2 mouse
-(i.e., no need to tie up a serial port with a serial mouse).  But then
-again: economy of scale currently works in the direction that serial
-mice are dirt cheap and omni-present, which can't be said about PS/2
-mice.
-<P>
-</LI>
-<LI><B>Memory</B>
-
-<P> Be careful about what kind of SIMMs you get.  In particular,
-"logical parity" SIMMs <B>do not</B> work.  What you should get is
-70ns memory with 36bits/SIMM.  These are also known as ECC SIMMs.
-Please refer to the OEM Design Guide for details.
-<P>Also notice that some of the firmware simply <EM>refuses</EM> to boot with
-anything less than 16MB of RAM installed.  Older versions of the SRM
-console used to do that and the ARC console apparently has the same
-bad habit.  MILO and any reasonably recent release of the SRM console
-should boot fine in 8MB, however.
-<P>
-</LI>
-</UL>
-<P>
-<P>
-<H2><A NAME="ss8.3">8.3 Will Normal ISA Cards Work?</A>
-</H2>
-
-<P> They should and, as far as we can tell, they really do work.
-Besides the drivers for the on-board interfaces, several other ISA
-cards are known to work already (e.g., depca and ne2000 Ethernet
-cards, sound cards, internal modems, etc.).  Notice that the SRM
-console includes a configuration command called "isacfg" that allows
-to setup the PCI/ISA bridge.  That command has an undocumented option
-<CODE>enadev</CODE> that allows to enable the ISA card.
-<P>
-<P>
-<H2><A NAME="ss8.4">8.4 What's Performance Like?</A>
-</H2>
-
-<P> Notice that the numbers below are for DEC Unix.  Linux/Alpha is
-likely to be less tuned at this point, but it gives you an idea of
-where the hardware stands.  
-<P>
-<H3>233MHz, 1MB Second-level Cache</H3>
-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
--------------------------------------------------
-DRAFT 0.02 Performance Flash    AXPpci33, 233MHz
-Digital UNIX 3.2                1MB BCache
--------------------------------------------------
-SPEC CINT92
-        SPECint92               100.2
-        SPECbase_int92           91.2
-SPEC CFP92
-        SPECfp92                112.7
-        SPECbase_fp92           107.8
-LINKPACK
-64-bit Double-Precision
-        100x100 MFLOPS           17.32
-        1000x1000 MFLOPS         93.95
-Dhrystone
-        V1.1 instructions/sec   263.012
-        v2.1 instructions/sec   250.000
-Whetstone
-        Single-precision KWIPS  249.292
-        Double-precision KWIPS  211.255
-DN and R Labs CPU2      
-        MVUPS                   274.47
-SLALOM
-        Patches                  5,686
-        MFLOPS                   40.07
-Livermore Loops
-        Geo. mean MFLOPS         21.95
-CERN    
-        CERNS units              28.99
--------------------------------------------------
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss8.5">8.5 To Probe Further</A>
-</H2>
-
-<P> A lot of useful and detailed information is available at 
-<A HREF="http://ftp.digital.com/pub/DEC/axppci/read_me.html">Digital's ftp server</A>.
-<P>
-<P>
-<HR>
-<A HREF="FAQ-9.html">Next</A>
-<A HREF="FAQ-7.html">Previous</A>
-<A HREF="FAQ.html#toc8">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ-9.html b/english/ports/alpha/faq/FAQ-9.html
deleted file mode 100644
index fcd55ad1b9a..00000000000
--- a/english/ports/alpha/faq/FAQ-9.html
+++ /dev/null
@@ -1,204 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions: Jensen (DEC 2000/DECpc 150/Highscreen AXP)</TITLE>
- <LINK HREF="FAQ-10.html" REL=next>
- <LINK HREF="FAQ-8.html" REL=previous>
- <LINK HREF="FAQ.html#toc9" REL=contents>
-</HEAD>
-<BODY>
-<A HREF="FAQ-10.html">Next</A>
-<A HREF="FAQ-8.html">Previous</A>
-<A HREF="FAQ.html#toc9">Contents</A>
-<HR>
-<H2><A NAME="s9">9. Jensen (DEC 2000/DECpc 150/Highscreen AXP)</A></H2>
-
-<P><I>This section was contributed and was maintained for many 
-years by Martin Ostermann. (Thanks, Martin !) Currently Martin doesn't own a 
-Jensen anymore: updates for this section may be sent directly 
-to 
-<A HREF="mailto:geerten@bart.nl">me</A></I>
-<P>
-<P> The Jensen was the first Alpha PC that has been available
-commercially from DEC.  Not surprisingly, there are a few oddities
-with it.  This section is an attempt to help people getting
-Linux/Alpha installed on a Jensen, and to provide additional
-information operating Linux on the Jensen.
-<P>
-<H2><A NAME="ss9.1">9.1 Installation</A>
-</H2>
-
-<P>First off, there is no MILO for the Jensen.  So it is unavoidable to
-use Jensen's builtin 
-<A HREF="http://www.azstarnet.com/~axplinux/srm.html">SRM</A> 
-console.  Unfortunately, it is severely
-handicapped with respect to boot command line option processing.
-Thanks to 
-<A HREF="mailto:michaels@stochastik.rwth-aachen.de">Michael Schwingen</A> there is now a new
-<A HREF="ftp://ftp.azstarnet.com/pub/linux/axp/aboot">aboot</A>
-loader that can work around these limitations.
-<P>Secondly, the Jensen SRM console cannot boot from a floppy. This used
-to make bootstrapping Linux a real pain, until 
-<A HREF="mailto:paradis@amt.tay1.dec.com">Jim Paradis</A> contributed a minlabel and
-writeboot programs executable from the ARC console.  An updated 
-version, which you probably want to use, includes a pre-compiled aboot 
-loader and updated installation instructions and is  available 
-<A HREF="ftp://ftp.azstarnet.com/pub/linux/axp/jensen/install">here</A>.
-<P>The original version -- <B> which is outdated and you should not use this 
-now</B> -- is available together with a the JENSEN-HOWTO describing the installation 
-process in detail from 
-<A HREF="ftp://ftp.digital.com/pub/DEC/Linux-Alpha/JENSEN_INSTALL/">ftp.digital.com</A>.
-<P>The Jensen is supported by 
-<A HREF="http://www.redhat.com">Red Hat Linux</A>, but some things still cause trouble.
-<P>
-<H2><A NAME="ss9.2">9.2 The Jensen is different</A>
-</H2>
-
-<P>The Jensen differs from other systems in several ways:
-<P>
-<UL>
-<LI> <B>No MILO.</B> It was already stated that there is no MILO for the Jensen. This is
-because the firmware implementation of the Jensen differs somewhat
-from the one on other systems. <I>PALcode</I> is the keyword to look for, if
-your interested to know more.
-</LI>
-<LI> <B>EISA-Bus.</B> The Jensen only got an EISA bus, no
-PCI. Furthermore, it uses a very special addressing scheme for the
-bus. While the kernel usually takes care of that in respect to device
-drivers, it has to be taken care of by utilities that do i/o in user
-space, like the X servers. Therefore you need special support from the
-X server, which is  available in XFree86 version 3.3 (or later) for S3
-cards, available from 
-<A HREF="http://www.xfree86.org/">www.xfree86.org</A>. 
-There is an older version for pure ECOFF systems available via ftp from 
-<A HREF="ftp://ftp.azstarnet.com/pub/linux/axp/jensen/">AZStarNet</A>. You'll also find
-other useful stuff there, ported by 
-<A HREF="http://www.informatik.rwth-aachen.de/I6/Colleagues/kanthak/Jensen/jensen_fan_page.html">Stephan Kanthak</A>,
-like a ported SVGAlib.
-
-If you're interested in details, watch for the keywords <I> SPARSE vs
-DENSE memory</I>.
-
-<P><B>Note:</B> Only S3 based cards are supported. The Compaq QVision,
-which is one of the graphic cards originally  shipped by Digital, is
-<B>not</B> currently not supported by XFree86, and support for it is
-unlikely to occur at all.
-<P>
-</LI>
-<LI> <B>RTC.</B> Somehow it was managed to locate the real time clock
-at a different place (I/O port 0x170 instead of 0x70 on all other
-machines). Thus the original clock program will fail. A patched
-version is available from 
-<A HREF="http://www.comnets.rwth-aachen.de/~ost/alpha/alpha.html">Martin Ostermann's Alpha Page</A>.
-</LI>
-<LI> <B>Firmware.</B> Since the Jensen is the oldest machine around,
-there are chances that you got a very old firmware. The date format
-changed in newer version, which will cause an offset of 20 years. You
-ought to get a 
-<A HREF="http://ftp.digital.com/pub/DEC/Linux-Alpha/JENSEN_INSTALL/jensen_firmware_procedure.html">firmware update</A>. WARNING: If you own an ELSA-Winner 1000
-graphics adapter, don't update beyond version 1.7!
-Otherwise you'll not be able to use your card in EISA mode. This is
-probably due to a bug in the EISA BIOS of the card.
-</LI>
-</UL>
-<P>
-<H2><A NAME="ss9.3">9.3 Known Problems</A>
-</H2>
-
-<P> Know Problem and workarounds:
-<UL>
-<LI> <B>Date and Time.</B> Due to the location of the real time clock
-and/or an old firmware. See above.
-</LI>
-<LI> <B>Won't boot after firmware update.</B> Aboot doesn't work with
-new firmwares. It is known to work 
-<A HREF="http://ftp.digital.com/pub/DEC/Linux-Alpha/JENSEN_INSTALL/jensen_firmware_procedure.html">with versions up to 1.7</A>.<BR>
-If you own an
-ELSA-Winner 1000  graphics adapter and upgraded beyond firmware
-version 1.7, the card won't work in EISA mode. Turn the card, so that
-it is plugged in with its ISA side. <BR>
-Maybe you want to downgrade you
-firmware again. (Windows-NT 3.51 and 4.0 seem to work fine with firmware 1.7)
-<A HREF="http://ftp.digital.com/pub/DEC/Linux-Alpha/JENSEN_INSTALL/jensen_firmware_procedure.html">This version</A>
-is now available from Digital's FTP server.
-</LI>
-<LI> <B>aboot-0.x doesn't compile on recent kernels.</B> 
-Get aboot-0.4 or above, it works with recent kernels.
-</LI>
-<LI> <B>Won't automatic reboot after correct shutdown.</B> Known
-problem, with 2.0.x kernels. Apparently this has been solved with
-recent 2.1.x kernels. I tried 2.1.88, and rebooting worked. But that
-kernel version had other problems.
-</LI>
-<LI> <B>Second serial port is unusable.</B> 
-Accessing '/dev/cua1' will freeze the system immediately. You may test 
-this by issuing 'cat /dev/cua1', but I suggest that you put your 
-file-systems in read-only mode first. In case you need more serial 
-ports, it is no problem to install an additional serial buffer 
-card. In case you need this for a modem, you ought to do that 
-anyway, because  the builtin ports are unbuffered (16450 
-compatible), not buffered onces (16550!). 
-</LI>
-</UL>
-<P>Sometimes people tend to blame the Jensen for general Alpha related
-problems. Please keep in mind that only the hardware is different, and
-that in most cases the kernel handles the hardware access. Thus for most
-programs it doesn't make a difference if they are being run on the
-Jensen or any other Digital/Alpha machine. 
-<P>
-<H2><A NAME="ss9.4">9.4 Hardware Issues</A>
-</H2>
-
-<P>You may ask yourself, how you can upgrade your system. Here are some 
-suggestions, but please note that I actually <B>did not</B> test most of this 
-stuff, I just collected information found on the internet: 
-<P>
-<UL>
-<LI><B>RAM updates.</B>
-4 MB, 8MB (dual-RAS aka doublesided), 16 MB, and 32 MB SIMMs produced 
-as late as summer of 96 have been reported to work, but I do not know 
-if a certain refresh cyclus is required. Note that you need <B> 36 
-bit true parity</B> SIMMs (but only one of the 4 paritiy bits on each 
-SIMM is actually used, as Michael Schwingen confirmed).   
-</LI>
-<LI><B>Video card.</B>
-Basically any VGA ISA or EISA card <B>may</B> work. Most actually do, if 
-you use the ARC console and Windows NT. Unfortunatly, the SRM 
-console, which you need to boot Linux, is somewhat picky about the 
-cards it supports. It uses an Intel-x86 emulation to initialize the card 
-via its VGA-BIOS, and that one seems to be buggy.<BR>
-If you want to run X, you need an S3 based card. Any S3 card (but, 
-<B>not</B> S3-Virge, etc), which has been accepted by the SRM console, 
-should work. Look at the XFree documentation for the XF86S3 driver for 
-detailed information.
-</LI>
-</UL>
-<P>
-<H2><A NAME="ss9.5">9.5 Miscellaneous Information</A>
-</H2>
-
-<P>So what is the Jensen all about? There is a some information
-available online:
-<P>
-<UL>
-<LI><B>The Evolution of the Alpha AXP PC (
-<A HREF="http://www.digital.com/.i/info/DTJD04/DTJD04SC.TXT">text</A>/
-<A HREF="http://www.digital.com/.i/info/DTJD04/DTJD04P8.PS">Postscript</A>)</B>
-by David G. Conroy, Thomas E. Kopec, and Joseph R. Falcone.
-This describes the development leading to the Jensen system. 
-</LI>
-<LI><B>Product announcement and description (
-<A HREF="http://ftp.digital.com/pub/DEC/Alpha/systems/as1000/docs/SOC/Feb94/ch-1-b.txt">text</A>/
-<A HREF="http://ftp.digital.com/pub/DEC/Alpha/systems/as1000/docs/SOC/Feb94/ch-1-b.ps.Z">Postscript</A>)</B>  by Digital. This is
-an overview of the Jensen system components and options.</LI>
-<LI><B>PB22H-KB System Module -- Hardware Reference Information (
-<A HREF="ftp://ftp.netbsd.org/pub/NetBSD/misc/dec-docs/ek-a0638-td.pdf.gz">PDF</A>)</B> by Digital. This is an in-depth description of the Jensen hardware.</LI>
-</UL>
-<P>
-<HR>
-<A HREF="FAQ-10.html">Next</A>
-<A HREF="FAQ-8.html">Previous</A>
-<A HREF="FAQ.html#toc9">Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/FAQ.html b/english/ports/alpha/faq/FAQ.html
deleted file mode 100644
index a1d1570bc89..00000000000
--- a/english/ports/alpha/faq/FAQ.html
+++ /dev/null
@@ -1,169 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.7">
- <TITLE>Linux/Alpha Frequently Asked Questions</TITLE>
- <LINK HREF="FAQ-1.html" REL=next>
-
-
-</HEAD>
-<BODY>
-<A HREF="FAQ-1.html">Next</A>
-Previous
-Contents
-<HR>
-<H1>Linux/Alpha Frequently Asked Questions</H1>
-
-<H2>
-<A HREF="mailto:geerten@bart.nl">Geerten Kuiper</A>
-, 
-<A HREF="mailto:David.Mosberger@acm.org">David Mosberger</A></H2>v1.1.5, 28 Feb 1999
-<P><HR>
-<EM>This document attempts to answer the most common Linux/Alpha related
-questions.  It also contains various pointers to other information
-sources that may help you get started in the Alpha world.  The latest
-version of this FAQ can always be found via the 
-<A HREF="http://www.alphalinux.org">Linux/Alpha home page</A>.
-It can also be downloaded, in .html or a number of other formats, from 
-<A HREF="otherformats/index.html">alphalinux.org</A>.</EM>
-<HR>
-<P>
-<H2><A NAME="toc1">1.</A> <A HREF="FAQ-1.html">What State Is Linux/Alpha In? </A></H2>
-
-<UL>
-<LI><A HREF="FAQ-1.html#ss1.1">1.1 Supported Drivers</A>
-<LI><A HREF="FAQ-1.html#ss1.2">1.2 Known Bugs And Workarounds</A>
-<LI><A HREF="FAQ-1.html#ss1.3">1.3 Porting to Alpha: the <CODE>long</CODE> and <CODE>short</CODE> of it</A>
-</UL>
-<P>
-<H2><A NAME="toc2">2.</A> <A HREF="FAQ-2.html">Are There Any Mailing Lists I Should Join?</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-2.html#ss2.1">2.1 And How About NewsGroups?</A>
-</UL>
-<P>
-<H2><A NAME="toc3">3.</A> <A HREF="FAQ-3.html">What's The Minimum Configuration To Run Linux/Alpha?</A></H2>
-
-<P>
-<H2><A NAME="toc4">4.</A> <A HREF="FAQ-4.html">How fast is the Alpha ?</A></H2>
-
-<P>
-<H2><A NAME="toc5">5.</A> <A HREF="FAQ-5.html">What Systems Does Linux/Alpha Run On?</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-5.html#ss5.1">5.1 Unsupported Systems</A>
-<LI><A HREF="FAQ-5.html#ss5.2">5.2 Table</A>
-</UL>
-<P>
-<H2><A NAME="toc6">6.</A> <A HREF="FAQ-6.html">So, what should I buy?</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-6.html#ss6.1">6.1 Boards</A>
-<LI><A HREF="FAQ-6.html#ss6.2">6.2 Systems</A>
-<LI><A HREF="FAQ-6.html#ss6.3">6.3 Brief Alpha Systems Overview</A>
-</UL>
-<P>
-<H2><A NAME="toc7">7.</A> <A HREF="FAQ-7.html">Where Do I Get Alpha Hardware?</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-7.html#ss7.1">7.1 Australia (country code: 61)</A>
-<LI><A HREF="FAQ-7.html#ss7.2">7.2 Austria (country code: 43)</A>
-<LI><A HREF="FAQ-7.html#ss7.3">7.3 Canada (country code: 1)</A>
-<LI><A HREF="FAQ-7.html#ss7.4">7.4 Finland (country code: 358)</A>
-<LI><A HREF="FAQ-7.html#ss7.5">7.5 France (country code: 33) </A>
-<LI><A HREF="FAQ-7.html#ss7.6">7.6 Germany (country code: 49) </A>
-<LI><A HREF="FAQ-7.html#ss7.7">7.7 Hong Kong (country code: 852) </A>
-<LI><A HREF="FAQ-7.html#ss7.8">7.8 Italy (country code: 39) </A>
-<LI><A HREF="FAQ-7.html#ss7.9">7.9 Japan (country code: 81) </A>
-<LI><A HREF="FAQ-7.html#ss7.10">7.10 Netherlands (country code: 31)</A>
-<LI><A HREF="FAQ-7.html#ss7.11">7.11 Sweden (country code: 46) </A>
-<LI><A HREF="FAQ-7.html#ss7.12">7.12 Switzerland (country code: 41)</A>
-<LI><A HREF="FAQ-7.html#ss7.13">7.13 U.K. (country code: 44)</A>
-<LI><A HREF="FAQ-7.html#ss7.14">7.14 U.S. (country code: 01)</A>
-<LI><A HREF="FAQ-7.html#ss7.15">7.15 Taiwan (country code: 886)</A>
-</UL>
-<P>
-<H2><A NAME="toc8">8.</A> <A HREF="FAQ-8.html">Noname (AXPpci33) and Multia (UDB) </A></H2>
-
-<UL>
-<LI><A HREF="FAQ-8.html#ss8.1">8.1 What Firmware Does Linux/Alpha Require?</A>
-<LI><A HREF="FAQ-8.html#ss8.2">8.2 What Do I Need To Watch Out For?</A>
-<LI><A HREF="FAQ-8.html#ss8.3">8.3 Will Normal ISA Cards Work?</A>
-<LI><A HREF="FAQ-8.html#ss8.4">8.4 What's Performance Like?</A>
-<LI><A HREF="FAQ-8.html#ss8.5">8.5 To Probe Further</A>
-</UL>
-<P>
-<H2><A NAME="toc9">9.</A> <A HREF="FAQ-9.html">Jensen (DEC 2000/DECpc 150/Highscreen AXP)</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-9.html#ss9.1">9.1 Installation</A>
-<LI><A HREF="FAQ-9.html#ss9.2">9.2 The Jensen is different</A>
-<LI><A HREF="FAQ-9.html#ss9.3">9.3 Known Problems</A>
-<LI><A HREF="FAQ-9.html#ss9.4">9.4 Hardware Issues</A>
-<LI><A HREF="FAQ-9.html#ss9.5">9.5 Miscellaneous Information</A>
-</UL>
-<P>
-<H2><A NAME="toc10">10.</A> <A HREF="FAQ-10.html">AlphaStation 200</A></H2>
-
-<P>
-<H2><A NAME="toc11">11.</A> <A HREF="FAQ-11.html">Samsung APC164UX (Ruffian): The Irreverent Guide </A></H2>
-
-<UL>
-<LI><A HREF="FAQ-11.html#ss11.1">11.1 Ruffian Links</A>
-<LI><A HREF="FAQ-11.html#ss11.2">11.2 Introduction</A>
-<LI><A HREF="FAQ-11.html#ss11.3">11.3 The Red Hat Release CDs and the Ruffian </A>
-<LI><A HREF="FAQ-11.html#ss11.4">11.4 Red Hat 5.1 </A>
-<LI><A HREF="FAQ-11.html#ss11.5">11.5 Red Hat 5.2 </A>
-<LI><A HREF="FAQ-11.html#ss11.6">11.6 Hardware Issues with the Ruffian </A>
-</UL>
-<P>
-<H2><A NAME="toc12">12.</A> <A HREF="FAQ-12.html">What Graphics Cards Work With Linux/Alpha?</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-12.html#ss12.1">12.1 TGA Card</A>
-<LI><A HREF="FAQ-12.html#ss12.2">12.2 VGA Cards</A>
-<LI><A HREF="FAQ-12.html#ss12.3">12.3 Cards Supported by the X Windowing System</A>
-<LI><A HREF="FAQ-12.html#ss12.4">12.4 Can Linux/Alpha Run Without Graphics Card?</A>
-</UL>
-<P>
-<H2><A NAME="toc13">13.</A> <A HREF="FAQ-13.html">Where Do I Get Linux Software?</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-13.html#ss13.1">13.1 Red Hat</A>
-<LI><A HREF="FAQ-13.html#ss13.2">13.2 DLD</A>
-<LI><A HREF="FAQ-13.html#ss13.3">13.3 Debian GNU/Linux</A>
-<LI><A HREF="FAQ-13.html#ss13.4">13.4 Stampede</A>
-<LI><A HREF="FAQ-13.html#ss13.5">13.5 Sources</A>
-<LI><A HREF="FAQ-13.html#ss13.6">13.6 Building a Kernel</A>
-</UL>
-<P>
-<H2><A NAME="toc14">14.</A> <A HREF="FAQ-14.html">Commercial Applications</A></H2>
-
-<P>
-<H2><A NAME="toc15">15.</A> <A HREF="FAQ-15.html">How To Boot Linux/Alpha?</A></H2>
-
-<P>
-<H2><A NAME="toc16">16.</A> <A HREF="FAQ-16.html">EM86: How To Run Linux/x86 Apps on Linux/Alpha</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-16.html#ss16.1">16.1 Two quotes from the README</A>
-</UL>
-<P>
-<H2><A NAME="toc17">17.</A> <A HREF="FAQ-17.html">How To Run DEC Unix Netscape on Linux/Alpha</A></H2>
-
-<UL>
-<LI><A HREF="FAQ-17.html#ss17.1">17.1 Requirements</A>
-<LI><A HREF="FAQ-17.html#ss17.2">17.2 How-To</A>
-<LI><A HREF="FAQ-17.html#ss17.3">17.3 Conclusion</A>
-<LI><A HREF="FAQ-17.html#ss17.4">17.4 Mail</A>
-<LI><A HREF="FAQ-17.html#ss17.5">17.5 Threads</A>
-</UL>
-<P>
-<H2><A NAME="toc18">18.</A> <A HREF="FAQ-18.html">Change Log</A></H2>
-
-<HR>
-<A HREF="FAQ-1.html">Next</A>
-Previous
-Contents
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/alpha-sys.html b/english/ports/alpha/faq/alpha-sys.html
deleted file mode 100644
index 88643964274..00000000000
--- a/english/ports/alpha/faq/alpha-sys.html
+++ /dev/null
@@ -1,385 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<head>
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta name="GENERATOR" content="Mozilla/4.5 [en] (X11; I; Linux 2.0.35 i586) [Netscape]">
-   <title>Alpha-Linux Howto</title>
-</head>
-<body text="#000000" bgcolor="#FFFFFF" link="#0000FF" vlink="#D00000">
-Brief Introduction to Alpha Systems and Processors Neal
-Crook, Digital Equipment (Editor: David Mosberger ) V0.11, 6 June 1997
-<p><font size=+2><a href="#What is Alpha">What is Alpha?</a></font>
-<br><font size=+2><a href="#What is DS">What is Digital Semiconductor</a></font>
-<br><font size=+2><a href="#Alpha CPU">Alpha CPUs</a></font>
-<br><font size=+2><a href="#21064 performace vs 21066 performance">21064
-performance vs 21066 performance</a></font>
-<br><font size=+2><a href="#A Few Notes On Clocking">A Few Notes on Clocking</a></font>
-<br><font size=+2><a href="#The chip-sets">The Chip-Sets</a></font>
-<br><font size=+2><a href="#The Systems">The Systems</a></font>
-<br><font size=+2><a href="#Bytes and all that stuff">Bytes And All That
-Stuff</a></font>
-<br><font size=+2><a href="#PALcode and all that stuff">PALcode and All
-That Stuff</a></font>
-<br><font size=+2><a href="#Porting">Porting</a></font>
-<br><font size=+2><a href="#More Information">More Information</a></font>
-<br><font size=+2><a href="#References">References</a></font>
-<br>
-<hr WIDTH="100%">
-<br>&nbsp;
-<p>This document is a brief overview of existing Alpha CPUs, chipsets and
-systems. It has something of a hardware bias, reflecting my own area of
-expertese. Although I am an employee of Digital Equipment Corporation,
-this is not an official statement by Digital and any opinions expressed
-are mine and not Digital's.
-<p><font size=+2>1.&nbsp;<a NAME="What is Alpha"></a>What is Alpha ?</font>
-<p>"Alpha" is the name given to Digital's 64-bit RISC architecture. The
-Alpha project in Digital began in mid-1989, with the goal of providing
-a high-performance migration path for VAX customers. This was not the first
-RISC architecture to be produced by Digital, but it was the first to reach
-the market. When Digital announced Alpha, in March 1992, it made the decision
-to enter the merchant semicondutor market by selling Alpha microprocessors.
-Alpha is also sometimes referred to as Alpha AXP, for obscure and arcane
-reasons that aren't worth persuing. Suffice it to say that they are one
-and the same.
-<p><font size=+2>2.&nbsp;<a NAME="What is DS"></a>What is Digital Semiconductor</font>
-<p>Digital Semiconductor<font size=+2> </font>(DS) is the business unit
-within Digital Equipment Corporation (Digital - we don't like the name
-DEC) that sells semiconductors on the merchant market. Digital's products
-include CPUs, support chipsets, PCI-PCI bridges and PCI peripheral chips
-for comms and multimedia.
-<p><font size=+2>3.&nbsp;<a NAME="Alpha CPU"></a>Alpha CPUs</font>
-<p>There are currently 2 generations of CPU core that implement the Alpha
-architecture:
-<p>&middot; EV4
-<br>&middot; EV5
-<p>Opinions differ as to what "EV" stands for (Editor's note: the true
-answer is of course "Electro Vlassic" ``[1]''), but the number represents
-the first generation of Digital's CMOS technology that the core was implemented
-in. So, the EV4 was originally implemented in CMOS4. As time goes by, a
-CPU tends to get a mid-life performance kick by being optically shrunk
-into the next generation of CMOS process. EV45, then, is the EV4 core implemented
-in CMOS5 process. There is a big difference between shrinking a design
-into a particular technology and implementing it from scratch in that technology
-(but I don't want to go into that now). There are a few other wildcards
-in here: there is also a CMOS4S (optical shrink in CMOS4) and a CMOS5L.
-<p>True technophiles will be interested to know that CMOS4 is a 0.75 micron
-process, CMOS5 is a 0.5 micron process and CMOS6 is a 0.35 micron process.
-<p>To map these CPU cores to chips we get:
-<p>21064-150,166
-<blockquote>EV4 (originally), EV4S (now)</blockquote>
-21064-200
-<blockquote>EV4S</blockquote>
-21064A-233,275,300
-<blockquote>EV45</blockquote>
-21066 LCA4S (EV4 core, with EV4 FPU)
-<p>21066A-233 LCA45 (EV4 core, but with EV45 FPU)
-<p>21164-233,300,333 EV5 21164A-417 EV56
-<p>21264 EV6
-<p>The EV4 core is a dual-issue (it can issue 2 instructions per CPU clock)
-superpipelined core with integer unit, floating point unit and branch prediction.
-It is fully bypassed and has 64-bit internal data paths and tightly coupled
-8Kbyte caches, one each for Instruction and Data. The caches are write-through
-(they never get dirty).
-<p>The EV45 core has a couple of tweaks to the EV4 core: it has a slightly
-improved floating point unit, and 16KB caches, one each for Instruction
-and Data (it also has cache parity). (Editor's note: Neal Crook indicated
-in a separate mail that the changes to the floating point unit (FPU) improve
-the performance of the divider. The EV4 FPU divider takes 34 cycles for
-a single-precision divide and 63 cycles for a double-precision divide (non
-data-dependent). In constrast, the EV45 divider takes typically 19 cycles
-(34 cycles max) for single- precision and typically 29 cycles (63 cycles
-max) for a double- precision division (data-dependent).)
-<p>The EV5 core is a quad-issue core, also superpipelined, fully bypassed
-etc etc. It has tightly-coupled 8Kbyte caches, one each for I and D. These
-caches are write-through. It also has a tightly-coupled 96Kbyte on-chip
-second-level cache (the Scache) which is 3-way set associative and write-back
-(it can be dirty). The EV4->EV5 performance increase is better than just
-the increase achieved by clock speed improvements. As well as the bigger
-caches and quad issue, there are microarchitectural improvements to reduce
-producer/consumer latencies in some paths.
-<p>The EV56 core is fundamentally the same microarchitecture as the EV5,
-but it adds some new instructions for 8 and 16-bit loads and stores (see
-Section ``Bytes and all that stuff''). These are primarily intended for
-use by device drivers. The EV56 core is implemented in CMOS6, which is
-a 2.0V process.
-<p>The 21064 was anounced in March 1992. It uses the EV4 core, with a 128-bit
-bus interface. The bus interface supports the 'easy' connection of an external
-second-level cache, with a block size of 256-bits (2 data beats on the
-bus). The Bcache timing is completely software configurable. The 21064
-can also be configured to use a 64-bit external bus, (but I'm not sure
-if any shipping system uses this mode). The 21064 does not impose any policy
-on the Bcache, but it is usually configured as a write-back cache. The
-21064 does contain hooks to allow external hardware to maintain cache coherence
-with the Bcache and internal caches, but this is hairy.
-<p>The 21066 uses the EV4 core and integrates a memory controller and PCI
-host bridge. To save pins, the memory controller has a 64-bit data bus
-(but the internal caches have a block size of 256 bits, just like the 21064,
-therefore a block fill takes 4 beats on the bus). The memory controller
-supports an external Bcache and external DRAMs. The timing of the Bcache
-and DRAMs is completely software configurable, and can be controlled to
-the resolution of the CPU clock period. Having a 4-beat process to fill
-a cache block isn't as bad as it sounds because the DRAM access is done
-in page mode. Unfortunately, the memory controller doesn't support any
-of the new esoteric DRAMs (SDRAM, EDO or BEDO) or synchronous cache RAMs.
-The PCI bus interface is fully rev2.0 compliant and runs at upto 33MHz.
-<p>The 21164 has a 128-bit data bus and supports split reads, with upto
-2 reads outstanding at any time (this allows 100% data bus utilisation
-under best-case dream-on conditions, i.e., you can theoretically transfer
-128-bits of data on every bus clock). The 21164 supports easy connection
-of an external 3-rd level cache (Bcache) and has all the hooks to allow
-external systems to maintain full cache coherence with all caches. Therefore,
-symmetric multiprocessor designs are 'easy'.
-<p>The 21164A was announced in October, 1995. It uses the EV56 core. It
-is nominally pin-compatible with the 21164, but requires split power rails;
-all of the power pins that were +3.3V power on the 21164 have now been
-split into two groups; one group provided 2.0V power to the CPU core, the
-other group supplies 3.3V to the I/O cells. Unlike older implementations,
-the 21164 pins are not 5V-tolerant. The end result of this change is that
-21164 systems are, in general, not upgradeable to the 21164A (though note
-that it would be relatively straightforward to design a 21164A system that
-could also accommodate a 21164). The 21164A also has a couple of new pins
-to support the new 8 and 16-bit loads and stores. It also improves the
-21164 support for using synchronus SRAMs to implement the external Bcache.
-<p><font size=+2>4.&nbsp;<a NAME="21064 performace vs 21066 performance"></a>21064
-performance vs 21066 performance</font>
-<p>The 21064 and the 21066 have the same (EV4) CPU core. If the same program
-is run on a 21064 and a 21066, at the same CPU speed, then the difference
-in performance comes only as a result of system Bcache/memory bandwidth.
-Any code thread that has a high hit-rate on the internal caches will perform
-the same. There are 2 big performance killers:
-<br>&nbsp;
-<blockquote>1. Code that is write-intensive. Even though the 21064 and
-the 21066 have write buffers to swallow some of the delays, code that is
-write-intensive will be throttled by write bandwidth at the system bus.
-This arises because the on-chip caches are write-through.
-<p>2. Code that wants to treat floats as integers. The Alpha architecture
-does not allow register-register transfers from integer registers to floating
-point registers. Such a conversion has to be done via memory (And therefore,
-because the on-chip caches are write- through, via the Bcache). (Editor's
-note: it seems that both the EV4 and EV45 can perform the conversion through
-the primary data cache (Dcache), provided that the memory is cached already.
-In such a case, the store in the conversion sequence will update the Dcache
-and the subsequent load is, under certain circumstances, able to read the
-updated d-cache value, thus avoiding a costly roundtrip to the Bcache.
-In particular, it seems best to execute the stq/ldt or stt/ldq instructions
-back-to-back, which is somewhat counter-intuitive.)
-<br>&nbsp;</blockquote>
-If you make the same comparison between a 21064A and a 21066A, there is
-an additional factor due to the different Icache and Dcache sizes between
-the two chips.
-<p>Now, the 21164 solves both these problems: it achieve much higher system
-bus bandwidths (despite having the same number of signal pins - yes, I
-know it's got about twice as many pins as a 21064, but all those extra
-ones are power and ground! (yes, really!!)) and it has write-back caches.
-The only remaining problem is the answer to the question "how much does
-it cost?"
-<p><font size=+2>5.&nbsp;<a NAME="A Few Notes On Clocking"></a>A Few Notes
-On Clocking</font>
-<p>All of the current Alpha CPUs use high-speed clocks, because their microarchitectures
-have been designed as so-called short-tick designs. None of the sytem busses
-have to run at horrendous speeds as a result though:
-<br>&nbsp;
-<blockquote>&middot; on the 21066(A), 21064(A), 21164 the off-chip cache
-(Bcache) timing is completely programmable, to the resolution of the CPU
-clock. For example, on a 275MHz CPU, the Bcache read access time can be
-controller with a resolution of 3.6ns
-<p>&middot; on the 21066(A), the DRAM timing is completely programmable,
-to the resolution of the CPU clock (not the PCI clock, the CPU clock).
-<p>&middot; on the 21064(A), 21164(A), the system bus frequency is a sub-
-multiple of the CPU clock frequency. Most of the 21064 motherboards use
-a 33MHz system bus clock.
-<p>&middot; Systems that use the 21066 can run the PCI at any frequency
-relative to the CPU. Generally, the PCI runs at 33MHz.
-<p>&middot; Systems that use the APECs chipset (see Section ``'') always
-have their CPU system bus equal to their PCI bus frequency. This means
-that both busses tends to run at either 25MHz or 33MHz (since these are
-the frequencies that scale up to match the CPU frequencies). On APECs systems,
-the DRAM controller timings are software programmable in terms of the CPU
-system bus frequency
-<br>&nbsp;</blockquote>
-Aside: someone suggested that they were getting bad performance on a 21066
-because the 21066 memory controller was only running at 33MHz. Actually,
-it's the superfast 21064A systems that have memory controllers that 'only'
-run at 33MHz.
-<p><font size=+2>6.&nbsp;<a NAME="The chip-sets"></a>The chip-sets</font>
-<p>DS sells two CPU support chipsets. The 2107x chipset (aka APECS) is
-a 21064(A) support chiset. The 2117x chipset (aka ALCOR) is a 21164 support
-chipset. There will also be 2117xA chipset (aka ALCOR 2) as a 21164A support
-chipset.
-<p>Both chipsets provide memory controllers and PCI host bridges for their
-CPU. APECS provides a 32-bit PCI host bridge, ALCOR provides a 64-bit PCI
-host bridge which (in accordance with the requirements of the PCI spec)
-can support both 32-bit and 64-bit PCI devices.
-<p>APECS consists of 6, 208-pin chips (4, 32-bit data slices (DECADE),
-1 system controller (COMANCHE), 1 PCI controller (EPIC)). It provides a
-DRAM controller (128-bit memory bus) and a PCI interface. It also does
-all the work to maintain memory coherence when a PCI device DMAs into (or
-out of) memory.
-<p>ALCOR consists of 5 chips (4, 64-bit data slices (Data Switch, DSW)
-- 208-pin PQFP and 1 control (Control, I/O Address, CIA) - a 383 pin plastic
-PGA). It provides a DRAM controller (256-bit memory bus) and a PCI interface.
-It also does all the work required to support an external Bcache and to
-maintain memory coherence when a PCI device DMAs into (or out of) memory.
-<p>There is no support chipset for the 21066, since the memory controller
-and PCI host bridge functionality are integrated onto the chip.
-<p><font size=+2>7.&nbsp;<a NAME="The Systems"></a>The Systems</font>
-<p>The applications engineering group in DS produces example designs using
-the CPUs and support chipsets. These are typically PC-AT size motherboards,
-with all the functionality that you'd typically find on a high-end Pentium
-motherboard. Originally, these example designs were intended to be used
-as starting points for third-parties to produce motherboard designs from.
-These first-generation designs were called Evaluation Boards (EBs). As
-the amount of engineering required to build a motherboard has increased
-(due to higher-speed clocks and the need to meet RF emission and susceptibility
-regulations) the emphasis has shifted towards providing motherboards that
-are suitable for volume manufacture.
-<p>Digital's system groups have produced several generations of machines
-using Alpha processors. Some of these systems use support logic that is
-designed by the systems groups, and some use commodity chipsets from DS.
-In some cases, systems use a combination of both.
-<p>Various third-parties build systems using Alpha processors. Some of
-these companies design systems from scratch, and others use DS support
-chipsets, clone/modify DS example designs or simply package systems using
-build and tested boards from DS.
-<p>The EB64: Obsolete design using 21064 with memory controller implemented
-using programmable logic. I/O provided by using programmable logic to interface
-a 486&lt;->ISA bridge chip. On-board Ethernet, SuperI/O (2S, 1P, FD), Ethernet
-and ISA. PC-AT size. Runs from standard PC power supply.
-<p>The EB64+: Uses 21064 or 21064A and APECs. Has ISA and PCI expansion
-(3 ISA, 2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
-ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI (NCR
-810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style), SuperI/O
-(2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM. PC-AT size. Runs from standard
-PC power supply.
-<p>The EB66: Uses 21066 or 21066A. I/O sub-system is identical to EB64+.
-Baby PC-AT size. Runs from standard PC power supply. The EB66 schematic
-was published as a marketing poster advertising the 21066 as "the first
-microprocessor in the world with embedded PCI" (for trivia fans: there
-are actually 2 versions of this poster - I drew the circuits and wrote
-the spiel for the first version, and some Americans mauled the spiel for
-the second version)
-<p>The EB164: Uses 21164 and ALCOR. Has ISA and PCI expansion (3 ISA slots,
-2 64-bit PCI slots (one is shared with an ISA slot) and 2 32-bit PCI slots.
-Uses plus-in Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD),
-KBD, MOUSE (PS2 style), RTC/NVRAM. Boot ROM is Flash. PC-AT-sized motherboard.
-Requires power supply with 3.3V output.
-<p>The AlphaPC64 (aka Cabriolet): derived from EB64+ but now baby-AT with
-Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA slots, 4 PCI slots
-(one pair are on a shared slot), uses plug-in Bcache SIMMs. Requires power
-supply with 3.3V output.
-<p>The AXPpci33 (aka NoName), is based on the EB66. This design is produced
-by Digital's Technical OEM (TOEM) group. It uses the 21066 processor running
-at 166MHz or 233MHz. It is a baby-AT size, and runs from a standard PC
-power supply. It has 5 ISA slots and 3 PCI slots (one pair are a shared
-slot). There are 2 versions, with either PS/2 or large DIN connectors for
-the keyboard.
-<p>Other 21066-based motherboards: most if not all other 21066-based motherboards
-on the market are also based on EB66 - there's really not many system options
-when designing a 21066 system, because all the control is done on-chip.
-<p>Multia (aka the Universal Desktop Box): This is a very compact pedestal
-desktop system based on the 21066. It includes 2 PCMCIA sockets, 21030
-(TGA) graphics, 21040 Ethernet and NCR 810 SCSI disk along with floppy,
-2 serial ports and a parallel port. It has limited expansion capability
-(one PCI slot) due to its compact size. (There is some restriction on when
-you can use the PCI slot, can't remember what) (Note that 21066A-based
-and Pentium-based Multia's are also available).
-<p>DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
-of the first-generation Alpha systems. It is only mentioned here because
-a number of these systems seem to be available on the second- hand market.
-The Jensen is a floor-standing tower system which used a 150MHz 21064 (later
-versions used faster CPUs but I'm not sure what speeds). It used programmable
-logic to interface a 486 EISA I/O bridge to the CPU.
-<p>Other 21064(A) systems: There are 3 or 4 motherboard designs around
-(I'm not including Digital systems here) and all the ones I know of are
-derived from the EB64+ design. These include:
-<blockquote>&middot; EB64+ (some vendors package the board and sell it
-unmodified); AT form-factor.
-<br>&middot; Aspen Systems motherboard: EB64+ derivative; baby-AT form-factor.
-<br>&middot; Aspen Systems server board: many PCI slots (includes PCI bridge).
-<br>&middot; AlphaPC64 (aka Cabriolet), baby AT form-factor. Other 21164(A)
-systems: The only one I'm aware of that isn't simply an EB164 clone is
-a system made by DeskStation. That system is implemented using a memory
-and I/O controller proprietary to Desk Station. I don't know what their
-attitude towards Linux is.</blockquote>
-<font size=+2>8.&nbsp;<a NAME="Bytes and all that stuff"></a>Bytes and
-all that stuff</font>
-<p>When the Alpha architecture was introduced, it was unique amongst RISC
-architectures for eschewing 8-bit and 16-bit loads and stores. It supported
-32-bit and 64-bit loads and stores (longword and quadword, in Digital's
-nomenclature). The co-architects (Dick Sites, Rich Witek) justified this
-decision by citing the advantages:
-<blockquote>1. Byte support in the cache and memory sub-system tends to
-slow down accesses for 32-bit and 64-bit quantities.
-<br>2. Byte support makes it hard to build high-speed error-correction
-circuitry into the cache/memory sub-system.</blockquote>
-Alpha compensates by providing powerful instructions for manipulating bytes
-and byte groups within 64-bit registers. Standard benchmarks for string
-operations (e.g., some of the Byte benchmarks) show that Alpha performs
-very well on byte manipulation.
-<p>The absence of byte loads and stores impacts some software semaphores
-and impacts the design of I/O sub-systems. Digital's solution to the I/O
-problem is to use some low-order address lines to specify the data size
-during I/O transfers, and to decode these as byte enables. This so-called
-Sparse Addressing wastes address space and has the consequence that I/O
-space is non-contiguous (more on the intricacies of Sparse Addressing when
-I get around to writing it). Note that I/O space, in this context, refers
-to all system resources present on the PCI and therefore includes both
-PCI memory space and PCI I/O space.
-<p>With the 21164A introduction, the Alpha archtecture was ECO'd to include
-byte addressing. Executing these new instructions on an earlier CPU will
-cause an OPCDEC PALcode exception, so that the PALcode will handle the
-access. This will have a performance impact. The ramifications of this
-are that use of these new instructions (IMO) should be restricted to device
-drivers rather than applications code.
-<p>These new byte load and stores mean that future support chipsets will
-be able to support contiguous I/O space.
-<p><font size=+2>9.&nbsp;<a NAME="PALcode and all that stuff"></a>PALcode
-and all that stuff</font>
-<p>This is a placeholder for a section explaining PALcode. I will write
-it if there is sufficient interest.
-<p><font size=+2>10.&nbsp;<a NAME="Porting"></a>Porting</font>
-<p>The ability of any Alpha-based machine to run Linux is really only limited
-by your ability to get information on the gory details of its innards.
-Since there are Linux ports for the E66, EB64+ and EB164 boards, all systems
-based on the 21066, 21064/APECS or 21164/ALCOR should run Linux with little
-or no modification. The major thing that is different between any of these
-motherboards is the way that they route interrupts. There are three sources
-of interrupts:
-<blockquote>&middot; on-board devices
-<br>&middot; PCI devices
-<br>&middot; ISA devices</blockquote>
-All the systems use an Intel System I/O bridge (SIO) to act as a bridge
-between PCI and ISA (the main I/O bus is PCI, the ISA bus is a secondary
-bus used to support slow-speed and 'legacy' I/O devices). The SIO contains
-the traditional pair of daisy-chained 8259s.
-<p>Some systems (e.g., the Noname) route all of their interrupts through
-the SIO and thence to the CPU. Some systems have a separate interrupt controller
-and route all PCI interrupts plus the SIO interrupt (8259 output) through
-that, and all ISA interrupts through the SIO.
-<p>Other differences between the systems include:
-<blockquote>&middot; how many slots they have &middot; what on-board PCI
-devices they have
-<br>&middot; whether they have Flash or EPROM</blockquote>
-<font size=+2>11.&nbsp;<a NAME="More Information"></a>More Information</font>
-<p>All of the DS evaluation boards and motherboard designs are license-
-free and the whole documentation kit for a design costs about 0. That includes
-all the schematics, programmable parts sources, data sheets for CPU and
-support chipset. The doc kits are available from Digital Semiconductor
-distributors. I'm not suggesting that many people will want to rush out
-and buy this, but I do want to point out that the information is available.
-<p>Hope that was helpful. Comments/updates/suggestions for expansion to
-Neal Crook&nbsp;<mailto:neal.crook@reo.mts.digital.com>.
-<p>12.&nbsp;<a NAME="References"></a><font size=+2>References</font>
-<p>[1]&nbsp;<http://www.research.digital.com/wrl/publications/abstracts/TN-13.html>Bill
-Hamburgen, Jeff Mogul, Brian Reid, Alan Eustace, Richard Swan, Mary Jo
-Doherty, and Joel Bartlett. Characterization of Organic Illumination Systems.
-DEC WRL, Technical Note 13, April 1989.
-<center>
-<p>
-<hr WIDTH="100%">
-<br><i><font size=-1>Adapted from the original Alpha-Linux Howto on 
-<a href="http://sunsite.unc.edu/pub/Linux/docs/howto/Alpha-HOWTO">sunsite.unc.edu</a></font></i>
-<br><i><font size=-1>October 31st 1998</font></i></center>
-
-</body>
-</html>
diff --git a/english/ports/alpha/faq/alphabios-howto.html b/english/ports/alpha/faq/alphabios-howto.html
deleted file mode 100644
index cf8a9a6fb3a..00000000000
--- a/english/ports/alpha/faq/alphabios-howto.html
+++ /dev/null
@@ -1,95 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>AlphaBIOS -HOWTO</TITLE>
-</HEAD>
-<BODY>
-Booting Linux/Alpha on an AlphaBIOS-based system
-<P>
-With the introduction of the XLT series, Digital changed the system
-console interface for its NT systems from ARC to AlphaBIOS.  AlphaBIOS
-is a screen-oriented interface which should be more familiar to PC
-users.  This change in console interface necessitates a change in
-setup procedure for those who wish to run Linux/Alpha on AlphaBIOS-based
-systems.
-<P>
-The first thing you must do is to install the latest version of AlphaBIOS
-on your system.  This can be obtained from Digital's "System Software and
-Driver Updates" Web page, <A HREF="http://www.windows.digital.com/support/sysoft.htp">www.windows.digital.com/support/sysoft.htp</A>
-Download the ZIP file, unzip it, and install it as follows:
-<P>
-
-<UL>
-	<LI> Copy the files to a FAT-formatted floppy.</LI>
-	<LI> Turn on the system and insert the floppy.  At the opening
-	  screen, press <F2> to go into setup mode</LI>
-	<LI> Select "Upgrade AlphaBIOS"</LI>
-	<LI> Follow the directions on the screen</LI>
-</UL>
-
-Once your AlphaBIOS is at the latest revision level, you can start
-bootstrapping your system as follows:
-<P>
-<UL>
-	<LI>- Create a FAT-formatted floppy with the following files:
-	<UL>
-		<LI>- linload.exe (from this directory)</LI>
-		<LI>- milo (the version appropriate to your system)</LI>
-		</UL>
-		</LI>
-
-	<LI>- Turn on the system and insert the floppy.  At the opening
-	  screen, press <F2> to go into setup mode</LI>
-	<LI>- Select "Utilities->OS Selection Setup..."</LI>
-	<LI>- Press INSERT to add a new operating system selection</LI>
-	<LI>- For "Boot Name", enter something like "Linux".  Press TAB
-	  to get over to the next field.</LI>
-	<LI>- Press down-arrow until the selection for "Boot File" is "A:".
-	  TAB over to the next field</LI>
-	<LI>- Enter "\linload.exe".  TAB *twice* (i.e. skip the OS Path
-	  load device -- it's irrelevant)</LI>
-	<LI>- Enter "\" for the OS Path load file</LI>
-	<LI>- Press ENTER to add the selection.</LI>
-	</UL>
-<P>
-
-At this point, AlphaBIOS will probably put up a big, unfriendly dialog
-box labelled "Warning: Operating System Selection not valid!".  Ignore
-this error (it's only a problem for NT) and press ENTER to continue.
-<P>
-        <UL>
-	<LI>- Press F10 to save the changes you just made; press ENTER to
-	  confirm the changes.</LI>
-	<LI>- Press ESC twice to get back to the opening screen.</LI>
-	<LI>- Use the up and down arrows to select the boot selection you
-	  just added, and press ENTER to boot it.</LI>
-	<LI>- AlphaBIOS will load linload, which will in turn load MILO.
-	  When you get to the MILO prompt, proceed as you would for a
-	  normal ARC-based system installation.</LI>
-	  </UL>
-<P>
-If you dedicated the first partition of your first disk drive to a small
-FAT partition for booting (as the installation procedure advises you to),
-then once Linux is installed you should copy linload.exe and milo to
-this partition.  Once you shut down, you can then modify the Linux menu
-selection to load MILO from this partition as follows:
-<P>
-<UL>
-	<LI>- At the opening screen, select <F2> to go into setup mode</LI>
-	<LI>- Select "Utilities->OS Selection setup"</LI>
-	<LI>- Highlight the entry for Linux, then press F6 to edit it.</LI>
-	<LI>- TAB over to the device portion of the "Boot File" line.
-	  Use the up and down arrow keys to select the hard-disk
-	  partition where linload and milo reside (typically
-	  "Disk 0 Partition 1" or "Disk 1 Partition 1").  Press
-	  ENTER to confirm the selection</LI>
-	<LI>- If you wish to auto-boot linux after MILO is loaded, then
-	  TAB over to the "OS Options" line and enter the MILO command
-	  to boot the system, e.g. "boot sda2:vmlinux.gz"
-	  Press ENTER to confirm the selection.</LI>
-	<LI>- Press F10 to save the changes.  Press ENTER to confirm.</LI>
-</UL>
-<P>
-Once you have done this, booting and running Linux on an AlphaBIOS based
-system should be very similar to doing so on an ARC system.
-
-</BODY></HTML>
-\ No newline at end of file
diff --git a/english/ports/alpha/faq/index.html b/english/ports/alpha/faq/index.html
deleted file mode 100644
index 2d5baf950d3..00000000000
--- a/english/ports/alpha/faq/index.html
+++ /dev/null
@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
- <HEAD>
-  <TITLE>Index of /faq</TITLE>
- </HEAD>
- <BODY>
-<H1>Index of /faq</H1>
-<PRE><IMG SRC="/icons/blank.gif" ALT="     "> <A HREF="?N=D">Name</A>                    <A HREF="?M=A">Last modified</A>       <A HREF="?S=A">Size</A>  <A HREF="?D=A">Description</A>
-<HR>
-<IMG SRC="/icons/back.gif" ALT="[DIR]"> <A HREF="/">Parent Directory</A>        05-Jul-1999 11:10      -  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-1.html">FAQ-1.html</A>              28-Feb-1999 18:08    21k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-10.html">FAQ-10.html</A>             28-Feb-1999 18:08     4k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-11.html">FAQ-11.html</A>             28-Feb-1999 18:08     8k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-12.html">FAQ-12.html</A>             28-Feb-1999 18:08     5k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-13.html">FAQ-13.html</A>             28-Feb-1999 18:08     5k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-14.html">FAQ-14.html</A>             28-Feb-1999 18:09     4k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-15.html">FAQ-15.html</A>             28-Feb-1999 18:09     1k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-16.html">FAQ-16.html</A>             28-Feb-1999 18:09     7k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-17.html">FAQ-17.html</A>             28-Feb-1999 18:09     7k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-18.html">FAQ-18.html</A>             28-Feb-1999 18:09     8k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-19.html">FAQ-19.html</A>             13-Jan-1999 16:52     8k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-2.html">FAQ-2.html</A>              28-Feb-1999 18:09     2k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-3.html">FAQ-3.html</A>              28-Feb-1999 18:10     2k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-4.html">FAQ-4.html</A>              28-Feb-1999 18:10     2k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-5.html">FAQ-5.html</A>              28-Feb-1999 18:10    11k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-6.html">FAQ-6.html</A>              28-Feb-1999 18:10     3k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-7.html">FAQ-7.html</A>              28-Feb-1999 18:10    18k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-8.html">FAQ-8.html</A>              28-Feb-1999 18:10     6k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ-9.html">FAQ-9.html</A>              28-Feb-1999 18:11     9k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="FAQ.html">FAQ.html</A>                28-Feb-1999 18:11     6k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="alpha-sys.html">alpha-sys.html</A>          06-Dec-1998 12:22    24k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="alphabios-howto.html">alphabios-howto.html</A>    03-Apr-1999 14:16     4k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-1.html">milo-1.html</A>             07-Nov-1998 13:05     2k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-10.html">milo-10.html</A>            07-Nov-1998 13:07     1k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-2.html">milo-2.html</A>             07-Nov-1998 13:05     5k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-3.html">milo-3.html</A>             07-Nov-1998 13:06     1k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-4.html">milo-4.html</A>             07-Nov-1998 13:06     3k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-5.html">milo-5.html</A>             07-Nov-1998 13:06    22k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-6.html">milo-6.html</A>             07-Nov-1998 13:06     8k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-7.html">milo-7.html</A>             07-Nov-1998 13:06     5k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-8.html">milo-8.html</A>             07-Nov-1998 13:06     1k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo-9.html">milo-9.html</A>             07-Nov-1998 13:07     3k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="milo.html">milo.html</A>               07-Nov-1998 12:49     3k  
-<IMG SRC="/icons/folder.gif" ALT="[DIR]"> <A HREF="otherformats/">otherformats/</A>           28-Feb-1999 18:16      -  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="srm-1.html">srm-1.html</A>              07-Nov-1998 13:07     3k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="srm-2.html">srm-2.html</A>              07-Nov-1998 13:07     3k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="srm-3.html">srm-3.html</A>              07-Nov-1998 13:08    16k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="srm-4.html">srm-4.html</A>              07-Nov-1998 13:08     7k  
-<IMG SRC="/icons/text.gif" ALT="[TXT]"> <A HREF="srm.html">srm.html</A>                07-Nov-1998 12:49     2k  
-</PRE><HR>
-<ADDRESS>Apache/1.3.6 Server at www.alphalinux.org Port 80</ADDRESS>
-</BODY></HTML>
diff --git a/english/ports/alpha/faq/milo-1.html b/english/ports/alpha/faq/milo-1.html
deleted file mode 100644
index f132012148e..00000000000
--- a/english/ports/alpha/faq/milo-1.html
+++ /dev/null
@@ -1,51 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: Introduction </TITLE>
-</HEAD>
-<BODY>
-Previous
-<A HREF="milo-2.html">Next</A>
-<A HREF="milo.html#toc1">Table of Contents</A>
-<HR>
-<H2><A NAME="intro-section"></A> <A NAME="s1">1. Introduction </A></H2>
-
-<P>This document describes the Miniloader for Linux on Alpha AXP (MILO).
-This firmware is used to initialize Alpha AXP based systems, load and
-start Linux and, finally, provide PALcode for Linux.</P>
-
-<H2><A NAME="ss1.1">1.1 Copyright</A></H2>
-
-<P>The Alpha Miniloader (MILO) HOWTO is copyright (C) 1995, 1996 David A Rusling.</P>
-
-<P><B>Copyright.</B> Like all Linux HOWTO documents, it may be reproduced and distributed
-in whole or in part, in any medium, physical or electronic, so long as
-this copyright notice is retained on all copies.
-Commercial redistribution is allowed and encouraged; however the author
-would <EM>like</EM> to be notified of such distributions.
-You may translate this HOWTO into any language whatsover provided that
-you leave this copyright statement and disclaimer intact, and that you append
-a notice stating who translated the document.</P>
-
-<P><B>Disclaimer.</B> While I have tried to include the most correct and
-up to date information available to me, I cannot guarantee that usage
-of information in this document does not result in loss of data or
-equipment.   I provide NO WARRENTY about the information in the HOWTO and
-I cannot be made liable for any consequences resulting from using the
-information in this HOWTO.</P>
-
-
-<H2><A NAME="ss1.2">1.2 New Versions of this Document</A></H2>
-
-<P> The latest version of this document can be found in
-<A HREF="ftp://gatekeeper.dec.com/pub/Digital/Linux-Alpha/Miniloader/docs">ftp://gatekeeper.dec.com/pub/Digital/Linux-Alpha/Miniloader/docs</A>
-and David Mosberger-Tang is kind enough to include the html form of it
-in his excellent Linux Alpha FAQ site
-<A HREF="http://www.azstarnet.com/~axplinux">http://www.azstarnet.com/~axplinux</A>.</P>
-
-
-<HR>
-Previous
-<A HREF="milo-2.html">Next</A>
-<A HREF="milo.html#toc1">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-10.html b/english/ports/alpha/faq/milo-10.html
deleted file mode 100644
index 8a680102970..00000000000
--- a/english/ports/alpha/faq/milo-10.html
+++ /dev/null
@@ -1,39 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: Acknowledgements.</TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-9.html">Previous</A>
-Next
-<A HREF="milo.html#toc10">Table of Contents</A>
-<HR>
-<H2><A NAME="s10">10. Acknowledgements.</A></H2>
-
-<P>I would like to thank: 
-<UL>
-<LI>Eric Rasmussen and Eilleen Samberg the authors of
-the PALcode,</LI>
-<LI>Jim Paradis for the keyboard driver and the original
-MILO interface,</LI>
-<LI>Jay Estabrook for his help and bugfixes,</LI>
-<LI>David Mosberger-Tang for the freeware BIOS emulation
-and his support and encouragement,</LI>
-<LI>Last (and <CODE>not</CODE> least) Linus Torvalds for the 
-timer code and his kernel.</LI>
-</UL>
-</P>
-
-<P>There are a number of things that still need doing to MILO,
-if you want to add something yourself, then do let me know 
-<A HREF="mailto:david.rusling@reo.mts.dec.com">david.rusling@reo.mts.dec.com</A>
-so that we do not duplicate our efforts.</P>
-
-<P>Finally, a big thank you to Digital for producing such a wonderful 
-chip (and paying me to do this).</P>
-
-<HR>
-<A HREF="milo-9.html">Previous</A>
-Next
-<A HREF="milo.html#toc10">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-2.html b/english/ports/alpha/faq/milo-2.html
deleted file mode 100644
index bc16907df30..00000000000
--- a/english/ports/alpha/faq/milo-2.html
+++ /dev/null
@@ -1,118 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: What is MILO? </TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-1.html">Previous</A>
-<A HREF="milo-3.html">Next</A>
-<A HREF="milo.html#toc2">Table of Contents</A>
-<HR>
-<H2><A NAME="what-section"></A> <A NAME="s2">2. What is MILO? </A></H2>
-
-<P>On Intel based PC systems, the BIOS firmware
-sets up the system and then loads the image to be run from the boot 
-block of a DOS file system.
-This is more or less what MILO does on an Alpha based system,
-however there are several interesting differences between BIOS firmware and
-MILO, not least of which is that MILO includes and 
-uses standard Linux device drivers unmodified.
-MILO is firmware, unlike LILO, which relies on the BIOS firmware to 
-get itself loaded.
-The main functional parts of MILO are:</P>
-<P>
-<OL>
-<LI> PALcode,</LI>
-<LI> Memory set up code (builds page tables and turns on virtual addressing),</LI>
-<LI> Video code (BIOS emulation code and TGA (21030)),</LI>
-<LI> Linux kernel code.  This includes real Linux
-kernel code (for example, the interrupt handling) and 
-ersatz or mock Linux kernel,</LI>
-<LI> Linux block device drivers (for example, the floppy driver),</LI>
-<LI> File system support (ext2, MS-DOS and ISO9660),</LI>
-<LI> User inteface code (MILO),</LI>
-<LI> Kernel interface code (sets up the HWRPB and memory map for linux),</LI>
-<LI> NVRAM code for managing environment variables.</LI>
-</OL>
-</P>
-
-<P>The following paragraphs describe these functional parts in more detail.</P>
-
-<P>PALcode can be thought of as a tiny software layer that tailors the
-chip to a particular operating system.  
-It runs in a special mode (PALmode) which has certain restrictions but it
-uses the standard Alpha instruction set with just five extra instructions.
-In this way, the Alpha chip can run such diverse operating systems as
-Windows NT, OpenVMS, Digital Unix and, of course, Linux.
-The PALcode that MILO uses (and therefore Linux itself)
-is, like the rest of MILO, freeware.
-It is derived from Digital's Evaluation Board software example Digital Unix
-PALcode..
-The differences between the different PALcodes are because of 
-differences in address mapping and interrupt handling that
-exist between the Alpha chips (21066 based systems have 
-a different I/O map to 21064+2107x systems) and different
-Alpha based systems.</P>
-
-<P>For MILO to operate properly it needs to know what memory 
-is available, where Linux will eventually be running from and it must be
-able to allocate temporary memory for the Linux device drivers.
-The code maintains a memory map that has entries for permanent and temporary
-allocated pages.
-As it boots, MILO uncompresses itself into the correct place in
-physical memory.   When it passes control to the Linux kernel,
-it reserves memory for the compressed version of itself, the PALcode
-(which the kernel needs) and some data structures.
-This leaves <CODE>most</CODE> of the memory in the system for Linux itself.</P>
-
-<P>The final act of the memory code is to set up and turn on virtual addressing
-so that the data structures that Linux expects to see are at the correct place
-in virtual memory.</P>
-
-<P>MILO contains video code that initialises and uses the video device
-for the system.   
-It will detect and use a VGA device if there is one, otherwise
-it will try to use a TGA (21030) video device.   
-Failing that, it will assume that there is no graphics device.
-The BIOS emulation that the standard, pre-built, images include is
-Digital's own BIOS emulation which supports most, if not all, of
-the standard graphics devices available.</P>
-
-<P>Linux device drivers live within the kernel and expect 
-certain services from the kernel.  Some of these services are provided directly
-by Linux kernel code, for example the interrupt handling and some is provided
-by kernel look-alike routines.</P>
-
-<P>MILO's most powerful
-feature is that you can embed unaltered Linux device drivers into it.
-This gives it the potential to support every device that Linux does.
-MILO includes all of the block devices that are configured into the
-Linux kernel that it is built against as well as a lot of the block device
-code (for example, ll_rw_blk()).</P>
-
-<P>MILO loads the Linux kernel from real file systems rather 
-than  from boot blocks and other strange places.
-It understands MSDOS, EXT2 and ISO9660 filesystems.
-Gzip'd files are supported and these are recommended, particularly if
-you are loading from floppy which is rather slow.
-MILO recognises these by their <EM>.gz</EM> suffix.</P>
-
-<P>Built into MILO is a simple keyboard driver which, together with
-an equally simple video driver allows it to have a simple user interface.
-That interface allows you to list file systems on configured devices, boot
-Linux or run flash update utilities and set environment variables that 
-control the system's booting.
-Like LILO, you can pass arguments to the Kernel.</P>
-
-<P>MILO must tell the Linux kernel what sort of system this is,
-how much memory there is and which of that memory is free.
-It does this using the HWRPB (Hardware Restart Parameter Block) data 
-structure and associated memory cluster descriptions.
-These are placed at the appropriate place in virtual memory just before
-control is passed to the Linux kernel.</P>
-
-<HR>
-<A HREF="milo-1.html">Previous</A>
-<A HREF="milo-3.html">Next</A>
-<A HREF="milo.html#toc2">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-3.html b/english/ports/alpha/faq/milo-3.html
deleted file mode 100644
index 57b1fd1aaaa..00000000000
--- a/english/ports/alpha/faq/milo-3.html
+++ /dev/null
@@ -1,39 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: Pre-Built Standard MILO Images.</TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-2.html">Previous</A>
-<A HREF="milo-4.html">Next</A>
-<A HREF="milo.html#toc3">Table of Contents</A>
-<HR>
-<H2><A NAME="s3">3. Pre-Built Standard MILO Images.</A></H2>
-
-<P>If you are planning to run Linux on a standard Alpha based system, then
-there are pre-built "standard" MILO images that you might use.
-These (along with the sources and other interesting stuff)
-can be found in 
-<A HREF="ftp://gatekeeper.dec.com/pub/Digital/Linux-Alpha/Miniloader">ftp://gatekeeper.dec.com/pub/Digital/Linux-Alpha/Miniloader</A>.</P>
-
-<P>The <CODE>images</CODE> subdirectory contains a directory per standard system
-(eg AlphaPC64) with MILO images having the following naming convention:</P>
-<P>
-<OL>
-<LI> <CODE>MILO</CODE> - Miniloader executable image, this image can be loaded in a 
-variety of ways,</LI>
-<LI> <CODE>fmu.gz</CODE> - Flash management utility,</LI>
-<LI> <CODE>MILO.dd</CODE> - Boot block floppy disk image.  
-These should be written using rawrite.exe or <CODE>dd</CODE> on Linux.</LI>
-</OL>
-</P>
-
-<P>The <CODE>test-images</CODE>, like the <CODE>images</CODE> subdirectory 
-contains a directory per standard system.   These images are somewhat
-experimental but tend to contain all the latest features.</P>
-
-<HR>
-<A HREF="milo-2.html">Previous</A>
-<A HREF="milo-4.html">Next</A>
-<A HREF="milo.html#toc3">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-4.html b/english/ports/alpha/faq/milo-4.html
deleted file mode 100644
index 433370d63d2..00000000000
--- a/english/ports/alpha/faq/milo-4.html
+++ /dev/null
@@ -1,97 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: How To Build MILO </TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-3.html">Previous</A>
-<A HREF="milo-5.html">Next</A>
-<A HREF="milo.html#toc4">Table of Contents</A>
-<HR>
-<H2><A NAME="build-section"></A> <A NAME="s4">4. How To Build MILO </A></H2>
-
-<P> You build MILO 
-seperately from the Kernel.  As MILO requires parts of the kernel
-to function (for example interrupt handling) you must first 
-configure and build the
-kernel that matches with MILO that you want to build.  Mostly this
-means building the kernel with the same version number.  
-So, MILO-2.0.25.tar.gz will build against linux-2.0.25.tar.gz.  
-MILO <CODE>may</CODE> build against a higher version of the kernel, but there 
-again it may not.
-Also, now that ELF shared libraries are fully supported, there are two
-versions of the MILO sources.
-To build under an ELF system you must first unpack the standard MILO sources
-and then patch those sources with the same version numbered ELF patch.
-In the remainder of this discussion,
-I assume that your kernel sources and object files are stored in the
-subtree at <CODE>/usr/src/linux</CODE> and that the linux kernel has been fully
-built with the command <CODE>make boot</CODE></P>
-
-
-<P>To build MILO, 
-change your working directory to the MILO source directory and
-invoke <CODE>make</CODE> with:
-<BLOCKQUOTE><CODE>
-<PRE>
-$    make KSRC=/usr/src/linux config
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Just like the Linux kernel, you will be asked a series of questions</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     Echo output to the serial port (MINI_SERIAL_ECHO) [y]
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P> It's a good idea to echo kernel printk to <CODE>/dev/ttyS0</CODE> if you can.
-If you can (and want to), then type "y", otherwise "n".  
-All of the standard, pre-built, MILO images include serial port I/O using COM1.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     Use Digital's BIOS emulation code (not free) (MINI_DIGITAL_BIOS_EMU) [y]
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P> This code is included as a library which is freely distributable
-so long as it is used on an Alpha based system.  The sources are
-not available.   If you answer <CODE>n</CODE> then the freeware 
-alternative BIOS emulation will be built.  It's sources are included
-with MILO.
-Note that you cannot right now build choose Digital's BIOS emulation code in
-an ELF system (the library is not yet ready) and so you must answer no to this
-question.</P>
-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     Build PALcode from sources (Warning this is dangerous) (MINI_BUILD_PALCODE_FROM_SOURCES) [n]     
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You should only do this if you have changed the PALcode sources, otherwise use the standard,
-pre-built PALcode included with MILO.</P>
-
-<P>You are now all set to build the MILO image itself:
-<BLOCKQUOTE><CODE>
-<PRE>
-$    make KSRC=/usr/src/linux
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>When the build has successfully completed, the MILO image is in the file called <CODE>milo</CODE>.
-There are a lot of images called <CODE>milo.*</CODE>, these should be ignored.</P>
-
-<HR>
-<A HREF="milo-3.html">Previous</A>
-<A HREF="milo-5.html">Next</A>
-<A HREF="milo.html#toc4">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-5.html b/english/ports/alpha/faq/milo-5.html
deleted file mode 100644
index 222f32cd513..00000000000
--- a/english/ports/alpha/faq/milo-5.html
+++ /dev/null
@@ -1,585 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: How To Load MILO</TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-4.html">Previous</A>
-<A HREF="milo-6.html">Next</A>
-<A HREF="milo.html#toc5">Table of Contents</A>
-<HR>
-<H2><A NAME="load-section"></A> <A NAME="s5">5. How To Load MILO</A></H2>
-
-<P>The most commonly supported method of loading MILO is from the Windows NT
-ARC firmware as most shipping systems support this.  However, there are
-a wide variety of  loading MILO.   It may be loaded from:
-<UL>
-<LI> a failsafe boot block floppy,</LI>
-<LI> the Windows NT ARC firmware, </LI>
-<LI> Digital's SRM console, </LI>
-<LI> an Alpha Evaluation Board Debug Monitor,</LI>
-<LI> flash/ROM.</LI>
-</UL>
-</P>
-
-<H2><A NAME="arc-section"></A> <A NAME="ss5.1">5.1 Loading MILO from the Windows NT ARC firmware</A></H2>
-
-<P>Most, if not all, Alpha AXP based systems include the Windows NT
-ARC firmware and this is the prefered method of booting MILO and thus
-Linux.  Once the Windows NT firmware is running and you have the correct
-MILO image for your system, this method is completely generic.</P>
-
-<P>The Windows NT ARC firmware is an environment in which programs can run
-and make callbacks into the firmware to perform actions.  The Windows NT
-OSLoader is a program that does exactly this.   Linload.exe is a 
-much simpler program which does just enough to load and execute MILO.
-It loads the appropriate image
-file into memory at 0x00000000 and then makes a swap-PAL PALcall to
-it.  
-MILO, like Linux, uses a different PALcode to Windows NT which is why the
-swap has to happen.
-MILO relocates itself to 0x200000 and continues on through the
-PALcode reset entry point as before.</P>
-
-<P>Before you add a Linux boot option, 
-you will need to copy linload.exe and the appropriate MILO that you
-wish to load to someplace that the Windows NT ARC firmware can read from.  
-In the following example, I assume that you are booting from a DOS format floppy
-disk:</P>
-<P>
-<OL>
-<LI> At the boot menu, select <CODE>"Supplementary menu..."</CODE></LI>
-<LI> At the <CODE>"Supplementary menu"</CODE>, select <CODE>"Set up the system..."</CODE></LI>
-<LI> At the <CODE>"Setup menu"</CODE>, select <CODE>"Manage boot selection menu..."</CODE></LI>
-<LI> In the <CODE>"Boot selections menu"</CODE>, choose <CODE>"Add a boot selection"</CODE></LI>
-<LI> Choose <CODE>"Floppy Disk 0"</CODE></LI>
-<LI> Enter <CODE>"linload.exe"</CODE> as the osloader directory and name</LI>
-<LI> Say "yes" to the operating system being on the same partition
-as the osloader</LI>
-<LI> Enter "\" as the operating system root directory</LI>
-<LI> I usually enter <CODE>"Linux"</CODE> as the name for this boot selection</LI>
-<LI> Say "No" you do not want to initialise the debugger at boot time</LI>
-<LI> You should now be back in the <CODE>"Boot selections menu"</CODE>, choose the
-<CODE>"Change a boot selection option"</CODE> and pick the selection you just created
-as the one to edit</LI>
-<LI> Use the down arrow to get <CODE>"OSLOADFILENAME"</CODE> up and then type in the
-name of the MILO image that you wish to use, for example <CODE>"noname.arc"</CODE>
-followed by return.</LI>
-<LI> Press ESC to get back to the <CODE>"Boot Selections menu"</CODE></LI>
-<LI> Choose <CODE>"Setup Menu"</CODE> (or hit ESC again) and choose <CODE>"Supplementary menu,
-and save changes"</CODE> option</LI>
-<LI> ESC will get you back to the <CODE>"Boot menu"</CODE> and you can attempt to boot
-MILO.  If you do not want Linux as the first boot option, then you can
-alter the order of the boot options in the <CODE>"Boot selections menu"</CODE>.</LI>
-</OL>
-</P>
-
-<P>At the end of all this, you should have a boot selection that looks something 
-like:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-LOADIDENTIFIER=Linux
-SYSTEMPARTITION=multi(0)disk(0)fdisk(0)
-OSLOADER=multi(0)disk(0)fdisk(0)\linload.exe
-OSLOADPARTITION=multi(0)disk(0)fdisk(0)
-OSLOADFILENAME=\noname.arc
-OSLOADOPTIONS=
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You can now boot MILO (and then Linux).  You can load linload.exe
-and MILO directly from a file system that Windows NT understands such as 
-NTFS or DOS on a hard disk.</P>
-
-<P>The contents <CODE>OSLOADOPTIONS</CODE> are passed to MILO which interprets
-it as a command.   So, in order to
-boot Linux directly from Windows NT without pausing in MILO, you could
-pass the following in <CODE>OSLOADOPTIONS</CODE>:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-boot sda2:vmlinux.gz root=/dev/sda2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>See 
-<A HREF="milo-6.html#MILO-if-section">MILO's User Interface</A> for more
-information on the commands available.</P>
-
-<P>Another (rather sneaky) way of loading of loading MILO via the WNT ARC firmware
-is to put MILO onto an MS-DOS floppy and call it <CODE>fwupdate.exe</CODE> and then choose
-the "Upgrade Firmware" option.</P>
-
-
-<H2><A NAME="dbm-section"></A> <A NAME="ss5.2">5.2 Loading MILO from the Evaluation Board Debug Monitor</A></H2>
-
-<P>Evaluation boards (and often designs cloned from them) include
-support for the Alpha Evaluation Board Debug Monitor.   Consult
-your system document before considering this method of booting
-MILO.   The following systems are <EM>known</EM> to include Debug Monitor
-support:
-<UL>
-<LI>AlphaPC64 (Section 
-<A HREF="#pc64-section">AlphaPC64</A>)</LI>
-<LI>EB64+ (Section 
-<A HREF="#eb64p-section">EB64+</A>)</LI>
-<LI>EB66+ (Section 
-<A HREF="#eb66p-section">EB66+</A>)</LI>
-<LI>EB164 (Section 
-<A HREF="#eb164-section">EB164</A>)</LI>
-<LI>PC164 (Section 
-<A HREF="#pc164-section">PC164</A>)</LI>
-</UL>
-</P>
-
-<P>Before you consider this method, you should note that the early
-versions of the Evaluation Board Debug Monitor did not include video
-or keyboard drivers and so you must be prepared to connect another
-system via the serial port so that you can use the Debug Monitor.
-Its interface is very simple and typing help shows a whole heap
-of commands.  The ones that are most interesting include
-the word <CODE>boot</CODE> or <CODE>load</CODE> in them.</P>
-
-<P>The Evaluation Board Debug Monitor can load an image either via the network
-(netboot) or via a floppy (flboot).  In either case, set the boot
-address to 0x200000 (<CODE>> bootadr 200000</CODE>) before booting the
-image.  </P>
-
-<P>If the image is on floppy (and note that only DOS formatted floppies
-are supported), then you will need to type the following command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     AlphaPC64&gt; flboot &lt;MILO-image-name&gt;
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="bootblock-section"></A> <A NAME="ss5.3">5.3 Loading MILO from a Failsafe Boot Block Floppy</A></H2>
-
-<P>Only the AxpPCI33 is <EM>known</EM> to include failsafe boot block
-floppy support (Section < id="noname-section" name="Noname">).</P>
-
-<P>If you do not have a standard pre-built MILO .dd image, 
-then you may need to
-build an SRM boot block floppy.  
-Once you have built MILO, you need to do the following on Digital Unix box:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     fddisk -fmt /dev/rfd0a
-     cat mboot bootm &gt; /dev/rfd0a
-     disklabel -rw rfd0a 'rx23' mboot bootm
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Or on a Linux box:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     cat mboot bootm &gt; /dev/fd0 
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P> If you have a standard MILO image available (say <CODE>MILO.dd</CODE>)
-then you would build a boot block floppy using the following command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     dd if=MILO.dd of=/dev/fd0 
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="flash_section"></A> <A NAME="ss5.4">5.4 Loading MILO from Flash</A></H2>
-
-<P>There are a number of systems where MILO can be blown into flash
-and booted directly (instead of via the Windows NT ARC firmware):
-<UL>
-<LI>AlphaPC64 (Section 
-<A HREF="#pc64-section">AlphaPC64</A>)</LI>
-<LI>Noname (Section 
-<A HREF="#noname-section">Noname</A>)</LI>
-<LI>EB66+ (Section 
-<A HREF="#eb66p-section">EB66+</A>)</LI>
-<LI>EB164 (Section 
-<A HREF="#eb164-section">EB164</A>)</LI>
-<LI>PC164 (Section 
-<A HREF="#pc164-section">PC164</A>)</LI>
-</UL>
-</P>
-
-
-<H2><A NAME="srm_section"></A> <A NAME="ss5.5">5.5 Loading MILO from the SRM Console</A></H2>
-
-<P>The SRM (short for System Reference Manual) Console knows nothing about filesystems or disk-partitions, 
-it simply expects that the secondary bootstrap loader occupies a consecutive range of
-physical disk sectors starting from a given offset.   The information describing
-the secondary bootstrap loader (its size and offset) is given in the first 512 
-byte block.   To load MILO via the SRM you must generate that structure on a 
-device which the SRM can access (such as a floppy disk).
-This is what <CODE>mboot</CODE> and <CODE>bootm</CODE>, <CODE>mboot</CODE> is the first block (or
-boot description) and <CODE>mboot</CODE> is the <CODE>MILO</CODE> image rounded up to a
-512 byte boundary.</P>
-
-<P>  To load MILO from a boot block device, either build <CODE>mboot</CODE>
-and <CODE>bootm</CODE> and push them onto the boot device
-using the following command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-        $ cat mboot bootm &gt; /dev/fd0
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Or, grab the appropriate <CODE>MILO.dd</CODE> from a web site and write it onto the
-boot device using either <CODE>RAWRITE.EXE</CODE> or <CODE>dd</CODE>.</P>
-
-<P> Once you have done that you can boot the SRM console and use one of its
-many commands to boot MILO.   For example, to boot MILO from a boot block floppy
-you would use the following command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-        &gt;&gt;&gt;boot dva0
-        (boot dva0.0.0.0.1 -flags 0)
-        block 0 of dva0.0.0.0.1 is a valid boot block
-        reading 621 blocks from dva0.0.0.0.1
-        bootstrap code read in
-        base = 112000, image_start = 0, image_bytes = 4da00
-        initializing HWRPB at 2000
-        initializing page table at 104000
-        initializing machine state
-        setting affinity to the primary CPU
-        jumping to bootstrap code
-        MILO Stub: V1.1
-        Unzipping MILO into position
-        Allocating memory for unzip
-        ####...
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>The following systems are <EM>known</EM> to have SRM Console support:
-<UL>
-<LI>Noname (Section 
-<A HREF="#noname-section">Noname</A>)</LI>
-<LI>AlphaPC64 (Section 
-<A HREF="#pc64-section">AlphaPC64</A>)</LI>
-<LI>EB164 (Section 
-<A HREF="#eb164-section">EB164</A>)</LI>
-<LI>PC164 (Section 
-<A HREF="#pc164-section">PC164</A>)</LI>
-</UL>
-</P>
-
-
-<H2><A NAME="specific-section"></A> <A NAME="ss5.6">5.6 System Specific Information</A></H2>
-
-<H3><A NAME="noname-section"></A> AxpPCI33 (Noname)</H3>
-
-<P>The Noname board can load MILO 
-from the Windows NT ARC firmware
-(Section 
-<A HREF="#arc-section">booting from Windows NT ARC firmware</A>),
-from the SRM Console
-(Section 
-<A HREF="#srm_section">Loading MILO from the SRM Console</A>).
-and from a failsafe boot block floppy
-(Section 
-<A HREF="#bootblock-section">Loading from a Failsafe Boot Block Floppy</A>).
-A flash management utility, runnable from MILO is available so that
-once MILO is running, it can be blown into flash
-(Section 
-<A HREF="milo-7.html#MILO-fmu-section">running the flash management utility</A>).
-However, be warned
-that once you have done this you will lose the previous image held there
-as there is only room for one image.</P>
-
-<P>The way that Noname boots is controlled
-by a set of jumpers on the board, J29 and J28.  These look like:
-<BLOCKQUOTE><CODE>
-<PRE>
-                    4
-        J29     2 x x x 6
-                1 x x x 5
-
-        J28     2 x x x 6
-                1 x x x 5
-                    3
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The two options that we're interested in are J28, pins 1-3 which
-boots the console/loader from flash and J29, pins 1-3 which boots the
-console/loader from a boot block floppy.  The second option is the one
-that you need to first boot MILO on the Noname board.</P>
-
-<P>Once you've selected the boot from floppy option via the jumpers,
-put the SRM boot block floppy containing MILO into the
-floppy and reboot.  In a few seconds (after the floppy light goes out)
-you should see the screen blank to white and MILO telling
-you what's going on.</P>
-
-<P>If you are really interested in technical stuff, the Noname loads
-images off of the floppy into physical address 0x104000 and images
-from flash into 0x100000.  For this reason, MILO is built
-with it's PALcode starting at 0x200000.  When it is first loaded, it
-moves itself to the correct location (see relocate.S).</P>
-
-<H3><A NAME="pc64-section"></A> AlphaPC64 (Cabriolet)</H3>
-
-<P>The AlphaPC64 includes the Windows NT ARC firmware
-(Section 
-<A HREF="#arc-section">booting from Windows NT ARC firmware</A>),
-the SRM Console (Section 
-<A HREF="#srm_section">Loading MILO from the SRM Console</A>)
-and the Evaluation Debug Monitor 
-(Section 
-<A HREF="#dbm-section">Loading from the Debug Monitor</A>).
-These images are in flash and there is room to add MILO so that
-you can boot MILO directly from flash.
-A flash management utility, runnable from MILO is available so that
-once MILO is running, it can be blown into flash
-(Section 
-<A HREF="milo-7.html#MILO-fmu-section">running the flash management utility</A>).
-This system supports MILO environment variables.</P>
-
-<P>You select between the boot options (and MILO when it is
-been put into flash) using a combination of jumpers and a boot option which
-is saved in the NVRAM of the TOY clock.</P>
-<P>The jumper is J2, SP bits 6 and 7 have the following meanings:
-<UL>
-<LI>SP bit 6 should always be out.  If this jumper is set then the
-SROM mini-debugger gets booted,</LI>
-<LI>SP bit 7 in is boot image selected by the boot option byte in 
-the TOY clock,</LI>
-<LI>SP bit 7 out is boot first image in flash.</LI>
-</UL>
-</P>
-
-<P>So, with bit 7 out, the Debug Monitor will be booted as it is <CODE>always</CODE>
-the first image in flash.  With bit 7 in, the image selected by
-the boot option in the TOY clock will be selected.  
-The Debug Monitor, the Windows NT ARC firmware and MILO all support setting
-this boot option byte but you must be very careful using it.
-In particular, you cannot set the boot option so that next time the system
-boots MILO when you are running the Windows NT ARC firmware, it only
-allows you to set Debug Monitor or Windows NT ARC as boot options.</P>
-
-<P> To get MILO into flash via the Evaluation Board Debug Monitor, 
-you will need a flashable image.
-The build proceedures make MILO.rom, 
-but you can also make a rom image using the makerom tool in the 
-Debug Monitor software that comes with the board:</P>
-<P>
-<PRE>
-    &gt; makerom -v -i7 -l200000 MILO -o mini.flash
-</PRE>
-</P>
-
-<P> (type makerom to find out what the arguments mean, but 7 is a
-flash image id used by the srom and -l200000 gives the load address
-for the image as 0x200000).</P>
-
-<P>Load that image into memory (via the Debug Monitor commands flload,
-netload, and so on) at 0x200000 and then blow the image into flash:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     AlphaPC64&gt; flash 200000 8
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P> (200000 is where the image to be blown is in memory and 8 is the segment
-number where you put the image.   There are 16 1024*64 byte segments in the
-flash and the Debug Monitor is at seg 0 and the Windows NT ARC firmware is at seg 4).</P>
-
-<P> Set up the image that the srom will boot by writing the number of
-the image into the TOY clock.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     AlphaPC64&gt; bootopt 131
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>(131 means boot the 3rd image, 129 = 1st, 130 = 2nd and so on).</P>
-
-<P> Power off, put jumper 7 on and power on and you should see the
-MILO burst into life.  If you don't then take jumper 7 back off
-and reboot the Debug Monitor.</P>
-
-<H3><A NAME="eb66p-section"></A> EB66+</H3>
-
-<P>The EB66+, like all of the Alpha Evaluation Boards built by Digital
-contains the Evaluation Board Debug Monitor and so this is available
-to load MILO
-(Section 
-<A HREF="#dbm-section">Loading from the Debug Monitor</A>).  
-Quite often (although not always) boards whose design is derived from
-these include the Debug Monitor also.
-Usually, these boards include the Windows NT ARC firmware
-(Section 
-<A HREF="#arc-section">booting from Windows NT ARC firmware</A>).
-A flash management utility, runnable from MILO is available so that
-once MILO is running, it can be blown into flash
-(Section 
-<A HREF="milo-7.html#MILO-fmu-section">running the flash management utility</A>).
-This system supports MILO environment variables.</P>
-
-<P>These systems have several boot images in flash controlled by jumpers.  
-The two jumper banks are J18 and J16 and are located at the bottom
-of the board in the middle (if the Alpha chip is at the top).
-You select between the boot options (and MILO when it is
-been put into flash) using a combination of jumpers and a boot option which
-is saved in the NVRAM of the TOY clock.</P>
-
-<P>Jumper 7-8 of J18 in means boot the image described by the
-boot option.   Jumper 7-8 of J18 out means boot the Evaluation Board
-Debug Monitor.</P>
-
-<P>Blowing an image into flash via the Evaluation Board Debug Monitor
-is exactly the same proceedure as
-for the AlphaPC64 (Section 
-<A HREF="#pc64-section">AlphaPC64</A>).</P>
-
-<H3><A NAME="eb64p-section"></A> EB64+/Aspen Alpine</H3>
-
-<P>This system is quite like the AlphaPC64 except that it does not
-contain flash which MILO can be loaded from.
-The EB64+ has two ROMs, one of which contains
-the Windows NT ARC firmware
-(Section 
-<A HREF="#arc-section">booting from Windows NT ARC firmware</A>).  
-and the other contains the Evaluation Board Debug Monitor 
-(Section 
-<A HREF="#dbm-section">Loading from the Debug Monitor</A>).  </P>
-
-<P>The Aspen Alpine is a little different in that it only has one
-ROM; this contains the Windows NT ARC firmware.</P>
-
-<H3><A NAME="multia-section"></A> Universal Desktop Box (Multia)</H3>
-
-<P>This is a very compact pre-packaged 21066 based system that 
-includes a TGA (21030) graphics device.   Although you can <EM>just</EM> fit
-a half height PCI graphics card in the box you are better off waiting
-for full TGA support in XFree86.   It includes the Windows NT ARC
-firmware and so booting from that is the prefered method
-(Section 
-<A HREF="#arc-section">Loading from Windows NT</A>).</P>
-
-<H3><A NAME="eb164-section"></A> EB164</H3>
-
-<P>The EB164, like all of the Alpha Evaluation Boards built by Digital
-contains the Evaluation Board Debug Monitor and so this is available
-to load MILO
-(Section 
-<A HREF="#dbm-section">Loading from the Debug Monitor</A>).  
-Quite often (although not always) boards whose design is derived from
-these include the Debug Monitor also.
-Usually, these boards include the Windows NT ARC firmware
-(Section 
-<A HREF="#arc-section">booting from Windows NT ARC firmware</A>).
-The SRM console is also available
-(Section 
-<A HREF="#srm_section">Loading MILO from the SRM Console</A>).
-A flash management utility, runnable from MILO is available so that
-once MILO is running, it can be blown into flash
-(Section 
-<A HREF="milo-7.html#MILO-fmu-section">running the flash management utility</A>).
-This system supports MILO environment variables.</P>
-
-<P>These systems have several boot images in flash controlled by jumpers.  
-The two jumper bank is J1 and is located at the bottom
-of the board on the left (if the Alpha chip is at the top).
-You select between the boot options (and MILO when it is
-been put into flash) using a combination of jumpers and a boot option which
-is saved in the NVRAM of the TOY clock.</P>
-
-<P>Jumper SP-11 of J1 in means boot the image described by the
-boot option.   Jumper SP-11 of J1 out means boot the Evaluation Board
-Debug Monitor.</P>
-
-<P>Blowing an image into flash via the Evaluation Board Debug
-Monitor is exactly the same proceedure as
-for the AlphaPC64 (Section 
-<A HREF="#pc64-section">AlphaPC64</A>).</P>
-
-<H3><A NAME="pc164-section"></A> PC164</H3>
-
-<P>The PC164, like all of the Alpha Evaluation Boards built by Digital
-contains the Evaluation Board Debug Monitor and so this is available
-to load MILO
-(Section 
-<A HREF="#dbm-section">Loading from the Debug Monitor</A>).  
-Quite often (although not always) boards whose design is derived from
-these include the Debug Monitor also.
-Usually, these boards include the Windows NT ARC firmware
-(Section 
-<A HREF="#arc-section">booting from Windows NT ARC firmware</A>).
-The SRM console is also available
-(Section 
-<A HREF="#srm_section">Loading MILO from the SRM Console</A>).
-A flash management utility, runnable from MILO is available so that
-once MILO is running, it can be blown into flash
-(Section 
-<A HREF="milo-7.html#MILO-fmu-section">running the flash management utility</A>).
-This system supports MILO environment variables.</P>
-
-<P>These systems have several boot images in flash controlled by jumpers.  
-The main jumper block, J30, contains the system configuration jumpers and
-jumper CF6 in means that the system will boot the Debug Monitor, the default
-is out.</P>
-
-<P>Blowing an image into flash via the Evaluation Board Debug
-Monitor is exactly the same proceedure as
-for the AlphaPC64 (Section 
-<A HREF="#pc64-section">AlphaPC64</A>).</P>
-
-<H3><A NAME="xl-section"></A> XL266</H3>
-
-<P>The XL266 is one of a family of systems that are known as Avanti.  
-It has a riser card containing the Alpha chip and cache which plugs into 
-the main board at right angles.   This board can replace the equivalent 
-Pentium board.</P>
-
-<P>Some of these systems ship with the SRM console but others, notably
-the XL266 ship with only the Windows NT ARC firmware
-(Section 
-<A HREF="#arc-section">booting from Windows NT ARC firmware</A>).</P>
-
-<P>Here is my list of compatible systems:
-<UL>
-<LI>AlphaStation 400 (Avanti),</LI>
-<LI>AlphaStation 250,</LI>
-<LI>AlphaStation 200 (Mustang),</LI>
-<LI>XL.  There are two flavours, XL266 and XL233 with the only
-difference being in processor speed and cache size.</LI>
-</UL>
-</P>
-
-<P><B>Note</B> The system that I use to develop and test MILO is
-an XL266 and so this is the only one that I can guarentee will work.
-However, technically, all of the above systems are equivalent; they
-have the same support chipsets and the same interrupt handling
-mechanisms.</P>
-
-<H3><A NAME="p2k-section"></A> Platform2000</H3>
-
-<P>This is a 233Mhz 21066 based system.</P>
-
-
-<HR>
-<A HREF="milo-4.html">Previous</A>
-<A HREF="milo-6.html">Next</A>
-<A HREF="milo.html#toc5">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-6.html b/english/ports/alpha/faq/milo-6.html
deleted file mode 100644
index f32ebca1ccd..00000000000
--- a/english/ports/alpha/faq/milo-6.html
+++ /dev/null
@@ -1,209 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: MILO's User Interface</TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-5.html">Previous</A>
-<A HREF="milo-7.html">Next</A>
-<A HREF="milo.html#toc6">Table of Contents</A>
-<HR>
-<H2><A NAME="MILO-if-section"></A> <A NAME="s6">6. MILO's User Interface</A></H2>
-
-<P>Once you have correctly installed/loaded/run MILO you will see 
-the MILO (for MIniLOader) prompt displayed on your screen.  There is a very
-simple interface that you must use in order to boot a particular Linux 
-kernel image.  Typing "help" is a good idea as it gives a useful summary
-of the commands.</P>
-
-<H2><A NAME="MILO-help-section"></A> <A NAME="ss6.1">6.1 The ''help'' Command</A></H2>
-
-<P>Probably the most useful command that MILO has:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-MILO&gt; help
-MILO command summary:
-
-ls [-t fs] [dev:[dir]] 
-                    - List files in directory on device
-boot [-t fs] [dev:file] [boot string] 
-                    - Boot Linux from the specified device and file
-run [-t fs] dev:file 
-                    - Run the standalone program dev:file
-show                - Display all known devices and file systems
-set VAR VALUE       - Set the variable VAR to the specified VALUE
-unset VAR           - Delete the specified variable
-reset               - Delete all variables
-print               - Display current variable settings
-help [var]          - Print this help text
-
-Devices are specified as: fd0, hda1, hda2, sda1...
-Use the '-t filesystem-name' option if you want to use
-  anything but the default filesystem  ('ext2').
-Use the 'show' command to show known devices and filesystems.
-Type 'help var' for a list of variables.
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P><B>Note</B> that the <CODE>bootopt</CODE> command only appears on AlphaPC64 
-(and similar) systems.  
-Refer to the board's dcoumentation to find out just what it means.</P>
-
-<P><B>Devices.</B>  Until you
-use a command that needs to make use of a device, no device
-inititalisation will take place.   The first <CODE>show</CODE>, 
-<CODE>ls</CODE>, <CODE>boot</CODE> or <CODE>run</CODE>
-commands all cause the devices within MILO to be initialised.
-Devices are named
-in the same way (exactly) that Linux itself will name them.  So, the
-first IDE disk will be called 'hda' and it's first partition will be 'hda1'.
-Use the <CODE>show</CODE> command to show what devices are available.</P>
-
-<P><B>File Systems.</B>   MILO supports three file systems, 
-MSDOS, EXT2 and ISO9660.  So long as a device is available to it, 
-MILO can <CODE>list</CODE><CODE>boot</CODE> or <CODE>run</CODE> an image stored on 
-one of these file systems.
-MILO's default file system is <CODE>EXT2</CODE> and so you have tell MILO that
-the file system is something other than that.
-All of the commands that use filenames 
-allow you to pass the file system using the <CODE>-t [filesystem]</CODE>option.
-So, if you wanted to list the contents of a SCSI CD ROM, you might type the
-following:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     MILO&gt; ls -t iso9660 scd0:
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P><B>Variables.</B>  MILO contains some settable variables that help
-the boot process.  If you are loading via the Windows NT ARC firmware, then
-MILO makes use of the boot option environment variables set up by that
-firmware.  
-For some systems, MILO (for example, the AlphaPC64) maintains
-its own set of environment variables that do not change from boot to boot.
-These variables are:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-MILO&gt; help var
-Variables that MILO cares about:
-  MEMORY_SIZE      - System memory size in megabytes
-  BOOT_DEV         - Specifies the default boot device
-  BOOT_FILE        - Specifies the default boot file
-  BOOT_STRING      - Specifies the boot string to pass to the kernel
-  SCSIn_HOSTID     - Specifies the host id of the n-th SCSI controller.
-  AUTOBOOT         - If set, MILO attempts to boot on powerup
-                     and enters command loop only on failure.
-  AUTOBOOT_TIMEOUT - Seconds to wait before auto-booting on powerup.
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="MILO-boot-section"></A> <A NAME="ss6.2">6.2 Booting Linux </A></H2>
-
-<P>The <CODE>boot</CODE> command boots a linux kernel from a device.
-You will need to have a linux kernel image on
-an EXT2 formatted disk (SCSI, IDE or floppy) or an ISO9660 formatted CD
-available to MILO.  
-The image can be gzip'd and in this case 
-MILO will recognise that it is gzip'd by the .gz suffix.</P>
-
-<P>You should note that the version of MILO does not usually have to match
-the version of the Linux kernel that you are loading.
-You boot Linux using the following command syntax:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     MILO&gt; boot [-t file-system] device-name:file-name [[boot-option] [boot-option] ...]
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Where <CODE>device-name</CODE> is the name of the device that you wish to
-use and <CODE>file-name</CODE> is the name of the file containing the Linux
-kernel.   All arguments supplied after the file name are passed directly
-to the Linux kernel. </P>
-
-<P>If you are installing Red Hat, then you will need to specify a root
-device and so on.  So you would use:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     MILO&gt; boot fd0:vmlinux.gz root=/dev/fd0 load_ramdisk=1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P> MILO will automatically contain the block devices that
-you configure into your vmlinux.  I have tested the floppy driver, the IDE
-driver and a number of SCSI drivers (for example, the NCR 810), and these work fine.  
-Also, it is important to set the host id of the SCSI controller
-to a reasonable value.  By default, MILO will initialize it to the
-highest possible value (7) which should normally work just fine.
-However, if you wish, you can explicitly set the host id of the
-<EM>n</EM>-th SCSI controller in the system by setting environment
-variable <CODE>SCSI</CODE><EM>n</EM><CODE>_HOSTID</CODE> to the appropriate
-value.  For example, to set the hostid of the first SCSI controller to
-7, you can issue the following command at the MILO prompt:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     setenv SCSI0_HOSTID 7
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="MILO-reboot-section"></A> <A NAME="ss6.3">6.3 Rebooting Linux </A></H2>
-
-<P>You may want to reboot a running Linux system using the
-<CODE>shutdown -r now</CODE> command.  In this case, the Linux kernel
-returns control to MILO (via the HALT CallPAL entrypoint).
-MILO leaves a compressed copy of itself in memory for just this
-reason and detects that the system is being rebooted from information
-held in the HWRPB (Hardware Restart Parameter Block).
-In this case it starts to reboot using exactly the same command that
-was used to boot the Linux kernel the last time.
-There is a 30 second timeout that allows you to interrupt this 
-process and boot whatever kernel you wish in whatever way you wish.</P>
-
-
-<H2><A NAME="MILO-bootopt-section"></A> <A NAME="ss6.4">6.4 The ''bootopt'' command </A></H2>
-
-<P>For flash based systems such as the AlphaPC64, EB164 and the EB66+, there
-are a number of possible boot options and these are changed using the 
-<CODE>bootopt</CODE> command.  
-This has one argument, a decimal number which is the type of the
-image to be booted the next time the system is power cycled or reset:</P>
-
-<P><B>0</B> Boot the Evaluation Board Debug Monitor,</P>
-<P><B>1</B> Boot the Windows NT ARC firmware.</P>
-
-<P>In order to tell the boot code to boot the MILO firmware from flash
-then you need a boot option that means boot the N'th image.  
-For this, you need to 128 plus N, so if MILO is the third image, you 
-would use the command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     MILO&gt; bootopt 131
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P><CODE>Note:</CODE> Be very careful with this command.   A good rule is never to
-set bootopt to 0 (the Evaluation Board Debug Monitor), but instead use the 
-system's jumpers to achieve the same thing.  </P>
-
-
-<HR>
-<A HREF="milo-5.html">Previous</A>
-<A HREF="milo-7.html">Next</A>
-<A HREF="milo.html#toc6">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-7.html b/english/ports/alpha/faq/milo-7.html
deleted file mode 100644
index 74a4b20cad4..00000000000
--- a/english/ports/alpha/faq/milo-7.html
+++ /dev/null
@@ -1,165 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: Running the Flash Management Utility </TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-6.html">Previous</A>
-<A HREF="milo-8.html">Next</A>
-<A HREF="milo.html#toc7">Table of Contents</A>
-<HR>
-<H2><A NAME="MILO-fmu-section"></A> <A NAME="s7">7. Running the Flash Management Utility </A></H2>
-
-<P>The <CODE>run</CODE> command is used to run the flash management utility.
-Before you start you will need a device available to MILO that
-contains the updateflash program.  
-This (like vmlinux) can be gzip'd.  You need to run the flash management
-utility  program from the MILO using the (<CODE>run</CODE>) command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     MILO&gt; run fd0:fmu.gz
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Once it has loaded and initialised, the flash management utility
-will tell you some information about the flash device and give you
-a command prompt.  Again the <CODE>help</CODE> command is most useful.</P>
-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Linux MILO Flash Management Utility V1.0
-
-Flash device is an Intel 28f008SA
-  16 segments, each of 0x10000 (65536) bytes
-Scanning Flash blocks for usage
-Block 12 contains the environment variables
-FMU&gt; 
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P><CODE>Note</CODE> that on systems where environment variables may be stored
-and where there is more than one flash block (for example, the AlphaPC64)
-the flash management utility will look for a block to hold MILO's 
-environment variables.  If such a block already exists, the flash management
-utility will tell you where it is.  Otherwise, you must use the <CODE>environment</CODE>
-command to set a block and initialise it.
-In the above example, flash block 12 contains MILO's environment 
-variables.</P>
-
-<H2><A NAME="ss7.1">7.1 The ''help'' command</A></H2>
-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-FMU&gt; help
-FMU command summary:
-
-list                - List the contents of flash
-program             - program an image into flash
-quit                - Quit
-environment         - Set which block should contain the environment variables
-bootopt num         - Select firmware type to use on next power up
-help                - Print this help text
-FMU&gt;           
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P><EM>Note</EM> that the <CODE>environment</CODE> and <CODE>bootopt</CODE> commands are only available on
-the EB66+, the AlphaPC64, EB164 and PC164 systems (and their clones).</P>
-
-
-<H2><A NAME="ss7.2">7.2 The ''list'' command</A></H2>
-
-<P>The ''list'' command shows the current usage of the flash memory.
-Where there is more than one flash block, the usage of each flash block
-is shown.   In the example below you can see that Windows NT ARC is using
-blocks 4:7 and block 15.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-FMU&gt; list
-Flash blocks:  0:DBM  1:DBM  2:DBM  3:WNT  4:WNT  5:WNT  6:WNT  7:WNT  8:MILO  
-        9:MILO 10:MILO 11:MILO 12:MILO 13:U 14:U 15:WNT
-Listing flash Images
-  Flash image starting at block 0:
-    Firmware Id:  0 (Alpha Evaluation Board Debug Monitor)
-    Image size is 191248 bytes (3 blocks)
-    Executing at 0x300000
-  Flash image starting at block 3:
-    Firmware Id:  1 (Windows NT ARC)
-    Image size is 277664 bytes (5 blocks)
-    Executing at 0x300000
-  Flash image starting at block 8:
-    Firmware Id:  7 (MILO/Linux)
-    Image size is 217896 bytes (4 blocks)
-    Executing at 0x200000
-FMU&gt;
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="ss7.3">7.3 The ''program'' command</A></H2>
-
-<P>The flash management utility contains a compressed copy of a flash
-image of MILO.  The ''program'' command allows you to blow this image
-into flash.
-The command allows you to back out, but before you run it you should
-use the ''list'' command to see where to put MILO.  
-If MILO is already in flash, then the flash management utility will 
-offer to overwrite it.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-FMU&gt; program
-Image is:
-    Firmware Id:  7 (MILO/Linux)
-    Image size is 217896 bytes (4 blocks)
-    Executing at 0x200000
-Found existing image at block 8
-Overwrite existing image? (N/y)? y
-Do you really want to do this (y/N)? y
-Deleting blocks ready to program: 8 9 10 11
-Programming image into flash
-Scanning Flash blocks for usage
-FMU&gt; 
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Wait until it has completed before powering off your system.</P>
-
-<P><CODE>Note:</CODE> I cannot emphasise just how careful you must be here
-not to overwrite an existing flash image that you might need or
-render your system useless.   A very good rule is never to overwrite
-the Debug Monitor.</P>
-
-
-<H2><A NAME="ss7.4">7.4 The ''environment'' command</A></H2>
-
-<P>This selects a flash block to contain MILO's environment variables.</P>
-
-
-<H2><A NAME="ss7.5">7.5 The ''bootopt'' command</A></H2>
-
-<P>This is just the same as MILO's ''bootopt'' command,
-see (Section 
-<A HREF="milo-6.html#MILO-bootopt-section">The ''bootopt'' command</A>).</P>
-
-
-<H2><A NAME="ss7.6">7.6 The ''quit'' command</A></H2>
-
-<P>This is really pretty meaningless.  The only way back to MILO (or
-anything else) once the flash management utility has run is to reboot
-the system.</P>
-
-
-<HR>
-<A HREF="milo-6.html">Previous</A>
-<A HREF="milo-8.html">Next</A>
-<A HREF="milo.html#toc7">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-8.html b/english/ports/alpha/faq/milo-8.html
deleted file mode 100644
index e6902946cbc..00000000000
--- a/english/ports/alpha/faq/milo-8.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: Restrictions.</TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-7.html">Previous</A>
-<A HREF="milo-9.html">Next</A>
-<A HREF="milo.html#toc8">Table of Contents</A>
-<HR>
-<H2><A NAME="s8">8. Restrictions.</A></H2>
-
-<P>Unfortunately this is not a perfect world and there, as always, some
-restrictions that you should be aware of.</P>
-
-<P>MILO is not meant to load operating systems other than Linux, 
-although it can load images linked to run at the same place in memory as Linux
-(which is 0xFFFFFC0000310000).
-This is how the flash management utilities can be run.</P>
-
-<P> The PALcode sources included in <CODE>miniboot/palcode/</CODE><EM>blah</EM> are
-correct, however there are problems when they are built using the
-latest <CODE>gas</CODE>.  They <EM>do</EM> build if you use the ancient a.out gas
-that's supplied in the Alpha Evaluation Board toolset (and that's how
-they were built).  I'm trying to get someone to fix the new gas.
-Meanwhile, as a workaround, I have provided pre-built PALcode for the
-supported boards and David Mosberger-Tang has a fixed gas on
-his ftp site.</P>
-
-<HR>
-<A HREF="milo-7.html">Previous</A>
-<A HREF="milo-9.html">Next</A>
-<A HREF="milo.html#toc8">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo-9.html b/english/ports/alpha/faq/milo-9.html
deleted file mode 100644
index 409d13022bf..00000000000
--- a/english/ports/alpha/faq/milo-9.html
+++ /dev/null
@@ -1,77 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto: Problem Solving.</TITLE>
-</HEAD>
-<BODY>
-<A HREF="milo-8.html">Previous</A>
-<A HREF="milo-10.html">Next</A>
-<A HREF="milo.html#toc9">Table of Contents</A>
-<HR>
-<H2><A NAME="s9">9. Problem Solving.</A></H2>
-
-<P>Here are some common problems that people have seen, together with the
-solutions.</P>
-
-<P><B>Reading MS-DOS floppies from the Evaluation Board Debug Monitor.</B>  </P>
-<P> Some of the older versions of the Evaluation Board Debug Monitor (pre-version 2.0)
-have a problem with DOS format flopies generated from Linux.
-Usually, the Debug Monitor can load the first few sectors all right, but then goes
-into an endless loop complaining about "bad sectors."  Apparently,
-there is an incompatibility between the DOS file system as expected by
-the Debug Monitor and the Linux implementation of DOSFS.  To make the
-long story short: if you run into this problem, try using DOS to write
-the floppy disk.  For example, if loading the file <CODE>MILO.cab</CODE>
-doesn't work, use a DOS machine, insert the floppy and then do:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-     copy a:MILO.cab c:
-     copy c:MILO.cab a:
-     del c:MILO.cab
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P> Then try booting from that floppy again.  This normally solves the problem.</P>
-
-<P><B>MILO displays a long sequence of <CODE>O></CODE> and does not accept input.</B></P>
-<P>This usually happens when MILO was built to use COM1 as a secondary console
-device.   In such a case, MILO echo output to COM1 and accepts input from
-there also.   This is great for debugging but not so great if you have
-a device other than a terminal connected.
-If this happens, disconnect the device or power it down until the Linux
-kernel has booted.
-Once Linux is up and running, everything will work as expected.</P>
-
-<P><B>MILO complains that the kernel image has the wrong magic number</B></P>
-<P> Older versions of MILO did not support the ELF object file format and so
-could not recognise an ELF image and this might be your problem.
-If this is reported, upgrade to the latest MILO that you can find.  All
-2.0.20 and beyond MILOs support ELF.
-On the other hand it could be that the image is indeed damaged.  You should
-also note that MILO does not yet automatically distinquish between GZIP'd
-and non-GZIP'd images; you need to add the ".gz" suffix to the file name.</P>
-
-<P><B>MILO prints "...turning on virtual addressing and jumping to the Linux Kernel" and
-nothing else happens</B></P>
-<P>One obvious problem is that the kernel image is wrongly built or is built for another
-Alpha system altogether.
-Another is that the video board is a TGA (Zlxp) device and the kernel has been built
-for a VGA device (or vice versa).
-It is worth building the kernel to echo to COM1 and then connecting a terminal to
-that serial port or retrying the kernel that came with the Linux distribution that you
-installed.</P>
-
-<P><B>MILO does not recognise the SCSI device</B></P>
-<P>The standard MILO images include as many device drivers as are known to be stable
-for Alpha (as of now that includes the NCR 810, QLOGIC ISP, Buslogic and Adaptec 2940s
-and 3940 cards).  If your card is not included, it may be that the driver is not stable
-enough on an Alpha system yet.  Again, the latest MILO images are worth trying.  You
-can tell which SCSI devices a MILO image has built into it by using the "show" command.</P>
-
-<HR>
-<A HREF="milo-8.html">Previous</A>
-<A HREF="milo-10.html">Next</A>
-<A HREF="milo.html#toc9">Table of Contents</A>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/milo.html b/english/ports/alpha/faq/milo.html
deleted file mode 100644
index f090adb4c0b..00000000000
--- a/english/ports/alpha/faq/milo.html
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<HTML>
-<HEAD>
-<TITLE>Alpha Miniloader Howto</TITLE>
-</HEAD>
-<BODY>
-Previous
-<A HREF="milo-1.html">Next</A>
-Table of Contents
-<HR>
-<H1>Alpha Miniloader Howto</H1>
-
-<H2>David A. Rusling, <CODE>david.rusling@reo.mts.dec.com</CODE></H2>v0.84, 6th December 1996
-<P><HR><EM>This document describes the Miniloader, a program for Alpha based systems that can be used to initialize the machine and load Linux.  The Alpha Linux Miniloader (to give it it's full
-name) is also known as MILO.</EM><HR></P>
-<P>
-<H2><A NAME="toc1">1.</A> <A HREF="milo-1.html">Introduction </A></H2>
-<UL>
-<LI><A HREF="milo-1.html#ss1.1">1.1 Copyright</A>
-<LI><A HREF="milo-1.html#ss1.2">1.2 New Versions of this Document</A>
-</UL>
-
-<P>
-<H2><A NAME="toc2">2.</A> <A HREF="milo-2.html">What is MILO? </A></H2>
-
-<P>
-<H2><A NAME="toc3">3.</A> <A HREF="milo-3.html">Pre-Built Standard MILO Images.</A></H2>
-
-<P>
-<H2><A NAME="toc4">4.</A> <A HREF="milo-4.html">How To Build MILO </A></H2>
-
-<P>
-<H2><A NAME="toc5">5.</A> <A HREF="milo-5.html">How To Load MILO</A></H2>
-<UL>
-<LI><A HREF="milo-5.html#ss5.1">5.1 Loading MILO from the Windows NT ARC firmware</A>
-<LI><A HREF="milo-5.html#ss5.2">5.2 Loading MILO from the Evaluation Board Debug Monitor</A>
-<LI><A HREF="milo-5.html#ss5.3">5.3 Loading MILO from a Failsafe Boot Block Floppy</A>
-<LI><A HREF="milo-5.html#ss5.4">5.4 Loading MILO from Flash</A>
-<LI><A HREF="milo-5.html#ss5.5">5.5 Loading MILO from the SRM Console</A>
-<LI><A HREF="milo-5.html#ss5.6">5.6 System Specific Information</A>
-</UL>
-
-<P>
-<H2><A NAME="toc6">6.</A> <A HREF="milo-6.html">MILO's User Interface</A></H2>
-<UL>
-<LI><A HREF="milo-6.html#ss6.1">6.1 The ''help'' Command</A>
-<LI><A HREF="milo-6.html#ss6.2">6.2 Booting Linux </A>
-<LI><A HREF="milo-6.html#ss6.3">6.3 Rebooting Linux </A>
-<LI><A HREF="milo-6.html#ss6.4">6.4 The ''bootopt'' command </A>
-</UL>
-
-<P>
-<H2><A NAME="toc7">7.</A> <A HREF="milo-7.html">Running the Flash Management Utility </A></H2>
-<UL>
-<LI><A HREF="milo-7.html#ss7.1">7.1 The ''help'' command</A>
-<LI><A HREF="milo-7.html#ss7.2">7.2 The ''list'' command</A>
-<LI><A HREF="milo-7.html#ss7.3">7.3 The ''program'' command</A>
-<LI><A HREF="milo-7.html#ss7.4">7.4 The ''environment'' command</A>
-<LI><A HREF="milo-7.html#ss7.5">7.5 The ''bootopt'' command</A>
-<LI><A HREF="milo-7.html#ss7.6">7.6 The ''quit'' command</A>
-</UL>
-
-<P>
-<H2><A NAME="toc8">8.</A> <A HREF="milo-8.html">Restrictions.</A></H2>
-
-<P>
-<H2><A NAME="toc9">9.</A> <A HREF="milo-9.html">Problem Solving.</A></H2>
-
-<P>
-<H2><A NAME="toc10">10.</A> <A HREF="milo-10.html">Acknowledgements.</A></H2>
-
-
-<HR>
-Previous
-<A HREF="milo-1.html">Next</A>
-Table of Contents
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/otherformats/FAQ.dvi.gz b/english/ports/alpha/faq/otherformats/FAQ.dvi.gz
deleted file mode 100644
index f1d2683beb3..00000000000
--- a/english/ports/alpha/faq/otherformats/FAQ.dvi.gz
+++ /dev/null
diff --git a/english/ports/alpha/faq/otherformats/FAQ.lyx.gz b/english/ports/alpha/faq/otherformats/FAQ.lyx.gz
deleted file mode 100644
index 23f83108c05..00000000000
--- a/english/ports/alpha/faq/otherformats/FAQ.lyx.gz
+++ /dev/null
diff --git a/english/ports/alpha/faq/otherformats/FAQ.ps.gz b/english/ports/alpha/faq/otherformats/FAQ.ps.gz
deleted file mode 100644
index c5221feb562..00000000000
--- a/english/ports/alpha/faq/otherformats/FAQ.ps.gz
+++ /dev/null
diff --git a/english/ports/alpha/faq/otherformats/FAQ.sgml.gz b/english/ports/alpha/faq/otherformats/FAQ.sgml.gz
deleted file mode 100644
index 8c5921c9c0a..00000000000
--- a/english/ports/alpha/faq/otherformats/FAQ.sgml.gz
+++ /dev/null
diff --git a/english/ports/alpha/faq/otherformats/FAQ.tex.gz b/english/ports/alpha/faq/otherformats/FAQ.tex.gz
deleted file mode 100644
index 78de5294615..00000000000
--- a/english/ports/alpha/faq/otherformats/FAQ.tex.gz
+++ /dev/null
diff --git a/english/ports/alpha/faq/otherformats/FAQ.tgz b/english/ports/alpha/faq/otherformats/FAQ.tgz
deleted file mode 100644
index 3a390c2a78d..00000000000
--- a/english/ports/alpha/faq/otherformats/FAQ.tgz
+++ /dev/null
diff --git a/english/ports/alpha/faq/otherformats/FAQ.txt.gz b/english/ports/alpha/faq/otherformats/FAQ.txt.gz
deleted file mode 100644
index 49d6948fe00..00000000000
--- a/english/ports/alpha/faq/otherformats/FAQ.txt.gz
+++ /dev/null
diff --git a/english/ports/alpha/faq/otherformats/index.html b/english/ports/alpha/faq/otherformats/index.html
deleted file mode 100644
index 52309d0f6d7..00000000000
--- a/english/ports/alpha/faq/otherformats/index.html
+++ /dev/null
@@ -1,13 +0,0 @@
-<HTML>
-<HEAD><TITLE>AlphaLinux FAQ in other formats</TITLE></HEAD>
-<BODY BGDOLOR="FFFFFF">
-<A HREF="FAQ.dvi.gz">FAQ.dvi.gz</A><P>
-<A HREF="FAQ.lyx.gz">FAQ.lyx.gz</A></P>
-<A HREF="FAQ.sgml.gz">FAQ.sgml.gz</A></P>
-<A HREF="FAQ.tex.gz">FAQ.tex.gz</A></P>
-<A HREF="FAQ.tgz">FAQ.tgz</A></P>
-<A HREF="FAQ.txt.gz">FAQ.txt.gz</A></P> 
-<A HREF="FAQ.ps.gz">FAQ.ps.gz</A></P>
-
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/srm-1.html b/english/ports/alpha/faq/srm-1.html
deleted file mode 100644
index ba1b0f3b812..00000000000
--- a/english/ports/alpha/faq/srm-1.html
+++ /dev/null
@@ -1,60 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>How Does SRM Boot an OS?</TITLE>
-</HEAD>
-<BODY>
-<H1>1. <A NAME="s1"></A>How Does SRM Boot an OS?</H1>
-<P>
-<A HREF="srm.html#toc1">Contents of this section</A></P>
-
-<P> All versions of SRM can boot from SCSI disks and the versions for
-recent platforms, such as the Noname or AlphaStations can boot from
-floppy disks as well.  Network booting via <CODE>bootp</CODE> is supported.
-Note that older SRM versions (notably the one for the Jensen)
-<EM>cannot</EM> boot from floppy disks.  Also, booting from IDE disk
-drives is unsupported.</P>
-<P></P>
-<P> Booting Linux with SRM is a two step process: first, SRM loads and
-transfers control to the secondary bootstrap loader.  Then the
-secondary bootstrap loader sets up the environment for Linux, reads
-the kernel image from a disk filesystem and finally transfers control
-to Linux.</P>
-<P></P>
-<P> Currently, there are two secondary bootstrap loaders for Linux:
-the <EM>raw</EM> loader that comes with the Linux kernel and <CODE>aboot</CODE>
-which is distributed separately.  These two loaders are described in
-more detail below.</P>
-<P></P>
-<P></P>
-<H2>1.1 <A NAME="ss1.1"></A> Loading The Secondary Bootstrap Loader</H2>
-
-<P> SRM knows nothing about filesystems or disk-partitions.  It simply
-expects that the secondary bootstrap loader occupies a consecutive
-range of physical disk sector, starting from a given offset.  The
-information on the size of the secondary bootstrap loader and the
-offset of its first disk sector is stored in the first 512 byte
-sector.  Specifically, the long integer at offset 480 stores the
-<EM>size</EM> of the secondary bootstrap loader (in 512-byte blocks) and
-the long at offset 488 gives the <EM>sector number</EM> at which the
-secondary bootstrap loader starts.  The first sector also stores a
-flag-word at offset 496 which is always 0 and a checksum at offset
-504.  The checksum is simply the sum of the first 63 long integers in
-the first sector.</P>
-<P></P>
-<P> If the checksum in the first sector is correct, SRM goes ahead and
-reads the <EM>size</EM> sectors starting from the sector given in the
-<EM>sector number</EM> field and places them in <EM>virtual</EM> memory at
-address <CODE>0x20000000</CODE>.  If the reading completes successfully,
-SRM performs a jump to address <CODE>0x20000000</CODE>.</P>
-<P></P>
-
-<HR>
-<P>
-<A HREF="srm-2.html">Next</A> Chapter<P>
-Table of contents of <A HREF="srm.html#toc1">this chapter</A>,
- General <A HREF="srm.html#toc">table of contents</A></P>
-<P>
-<A HREF="srm.html">Top</A> of the document,
- <A HREF="#0"> Beginning of this Chapter</A></P>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/srm-2.html b/english/ports/alpha/faq/srm-2.html
deleted file mode 100644
index 212d2c2e0dc..00000000000
--- a/english/ports/alpha/faq/srm-2.html
+++ /dev/null
@@ -1,76 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>The Raw Loader</TITLE>
-</HEAD>
-<BODY>
-<H1>2. <A NAME="s2"></A>The Raw Loader</H1>
-<P>
-<A HREF="srm.html#toc2">Contents of this section</A></P>
-
-<P> The sources for this loader can be found in directory</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-        linux/arch/alpha/boot
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>of the Linux kernel source distribution.  It loads the Linux kernel by
-reading <CODE>START_SIZE</CODE> bytes starting at disk offset
-<CODE>BOOT_SIZE+512</CODE> (also in bytes).  The constants
-<CODE>START_SIZE</CODE> and <CODE>BOOT_SIZE</CODE> are defined in
-<CODE>linux/include/asm-alpha/system.h</CODE>.  <CODE>START_SIZE</CODE>
-must be at least as big as the kernel image (i.e., the size of the
-<CODE>.text</CODE>, <CODE>.data</CODE>, and <CODE>.bss</CODE> segments).  Similarly,
-<CODE>BOOT_SIZE</CODE> must be at least as big as the image of the raw
-bootstrap loader.  Both constants should be an integer multiple of the
-sector size, which is 512 bytes.  The default values are currently
-2MB for <CODE>START_SIZE</CODE> and 16KB for <CODE>BOOT_SIZE</CODE>.
-Note that if you want to boot from a 1.44MB floppy disk, you have to
-reduce <CODE>START_SIZE</CODE> to 1400KB and make sure that the kernel
-you want to boot is no bigger than that.</P>
-<P></P>
-<P> To build a raw loader, simply type <CODE>make rawboot</CODE> in
-<CODE>/usr/src/linux</CODE>.  This should produce the following files in
-<CODE>arch/alpha/boot</CODE>:</P>
-<P>
-<DL>
-<DT><B><CODE>tools/lxboot</CODE>:</B><DD><P>The first
-sector on the disk.  It contains the offset and size of
-the next file in the format described above.</P>
-<DT><B><CODE>tools/bootlx</CODE>:</B><DD><P>The raw boot loader that
-will load the file below.</P>
-<DT><B><CODE>vmlinux.nh</CODE>:</B><DD><P>The raw kernel image consisting of
-the <CODE>.text</CODE>, <CODE>.data</CODE>, and <CODE>.bss</CODE> segments of the
-object file in <CODE>/usr/src/linux/vmlinux</CODE>.  The
-extension <CODE>.nh</CODE> indicates that this file has no object-file
-header.</P>
-</DL>
-</P>
-<P></P>
-<P> The concatenation of these three files should be written to the
-disk from which you want to boot.  For example, to boot from a floppy,
-insert an empty floppy disk in, say, <CODE>/dev/fd0</CODE> and then type:
-<BLOCKQUOTE><CODE>
-<PRE>
-cat tools/lxboot tools/bootlx vmlinux &gt;/dev/fd0
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P></P>
-<P> You can then shutdown the system and boot from the floppy by
-issueing the command <CODE>boot dva0</CODE>.</P>
-<P></P>
-<P></P>
-<HR>
-<P>
-<A HREF="srm-3.html">Next</A> Chapter,
-<A HREF="srm-1.html">Previous</A> Chapter
-<P>
-Table of contents of <A HREF="srm.html#toc2">this chapter</A>,
- General <A HREF="srm.html#toc">table of contents</A></P>
-<P>
-<A HREF="srm.html">Top</A> of the document,
- <A HREF="#0"> Beginning of this Chapter</A></P>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/srm-3.html b/english/ports/alpha/faq/srm-3.html
deleted file mode 100644
index 6e9a3eb49b9..00000000000
--- a/english/ports/alpha/faq/srm-3.html
+++ /dev/null
@@ -1,429 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>The aboot Loader</TITLE>
-</HEAD>
-<BODY>
-<A NAME="aboot"></A> <H1>3. <A NAME="s3"></A>The aboot Loader</H1>
-<P>
-<A HREF="srm.html#toc3">Contents of this section</A></P>
-
-<P> When using the SRM firmware, <CODE>aboot</CODE> is the preferred way of
-booting Linux.  It supports:</P>
-<P>
-<UL>
-<LI> direct booting from various filesystems (<CODE>ext2</CODE>, <CODE>ISO9660</CODE>, and
-<CODE>UFS</CODE>, the DEC Unix filesystem)</LI>
-<LI> booting of executable object files (both ELF and ECOFF)</LI>
-<LI> booting compressed kernels</LI>
-<LI> network booting (using bootp)</LI>
-<LI> partition tables in DEC Unix format (which is
-compatible with BSD Unix partition tables)</LI>
-<LI> interactive booting and default configurations for
-SRM consoles that cannot pass long option strings</LI>
-</UL>
-</P>
-<P></P>
-<P></P>
-<H2>3.1 <A NAME="ss3.1"></A> Getting and Building aboot</H2>
-
-<P> The latest sources for <CODE>aboot</CODE> are available in 
-<A HREF="ftp://ftp.azstarnet.com/pub/linux/axp/aboot">this ftp directory</A>
-.  The description in this manual applies to <CODE>aboot</CODE>
-version 0.5 or newer.</P>
-<P></P>
-<P> Once you downloaded and extracted the latest tar file, take a look
-at the <CODE>README</CODE> and <CODE>INSTALL</CODE> files for installation hints.  In
-particular, be sure to adjust the variables in <CODE>Makefile</CODE> and in
-<CODE>include/config.h</CODE> to match your environment.  Normally, you
-won't need to change anything when building under Linux, but it is
-always a good idea to double check.  If you're satisfied with the
-configuration, simply type <CODE>make</CODE> to build it (if you're not
-building under Linux, be advised that <CODE>aboot</CODE> requires GNU
-<CODE>make</CODE>).</P>
-<P>After running <CODE>make</CODE>, the <CODE>aboot</CODE> directory should contain the
-following files:</P>
-<P>
-<DL>
-<DT><B>aboot</B><DD><P>This is the actual <CODE>aboot</CODE> executable (either an
-ECOFF or ELF object file).</P>
-<DT><B>bootlx</B><DD><P>Same as above, but it contains only the text, data
-and bss segments---that is, this file is not an object file.</P>
-<DT><B>sdisklabel/writeboot</B><DD><P>Utility to install <CODE>aboot</CODE> on a
-hard disk.</P>
-<DT><B>tools/e2writeboot</B><DD><P>Utility to install <CODE>aboot</CODE> on an ext2
-filesystem (usually used for floppies only).</P>
-<DT><B>tools/isomarkboot</B><DD><P>Utility to install <CODE>aboot</CODE> on a iso9660
-filesystem (used by CD-ROM distributors).</P>
-<DT><B>tools/abootconf</B><DD><P>Utility to configure an installed <CODE>aboot</CODE>.</P>
-</DL>
-</P>
-<P></P>
-
-<H2>3.2 <A NAME="ss3.2"></A> Floppy Installation</H2>
-
-<P> The bootloader can be installed on a floppy using the
-<CODE>e2writeboot</CODE> command (note: this can't be done on a Jensen since
-its firmware does <EM>not</EM> support booting from floppy).  This command
-requires that the disk is not overly fragmented as it needs to find
-enough contiguous file blocks to store the entire <CODE>aboot</CODE> image
-(currently about 90KB).  If <CODE>e2writeboot</CODE> fails because of this,
-reformat the floppy and try again (e.g., with <CODE>fdformat(1)</CODE>).  For
-example, the following steps install <CODE>aboot</CODE> on floppy disk
-assuming the floppy is in drive <CODE>/dev/fd0</CODE>:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-fdformat /dev/fd0
-mke2fs /dev/fd0
-e2writeboot /dev/fd0 bootlx
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P></P>
-<P></P>
-
-<H2>3.3 <A NAME="ss3.3"></A> Harddisk Installation</H2>
-
-<P> Since the <CODE>e2writeboot</CODE> command may fail on highly fragmented
-disks and since reformatting a harddisk is not without pain, it is
-generally safer to install <CODE>aboot</CODE> on a harddisk using the
-<CODE>swriteboot</CODE> command.  <CODE>swriteboot</CODE> requires that the first few
-sectors are reserved for booting purposes.  We suggest that the disk
-be partitioned such that the first partition starts at an offset of
-2048 sectors.  This leaves 1MB of space for storing <CODE>aboot</CODE>.  On
-a properly partitioned disk, it is then possible to install <CODE>aboot</CODE>
-as follows (assuming the disk is <CODE>/dev/sda</CODE>):</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-swriteboot /dev/sda bootlx
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>On a Jensen, you will want to leave some more space, since you need to
-write a kernel to this place, too---2MB should be sufficient when
-using compressed kernels.  Use <CODE>swriteboot</CODE> as described in Section
-<A HREF="#booting">booting</A>
- to write <CODE>bootlx</CODE> together with the Linux
-kernel.</P>
-<P></P>
-
-<H2>3.4 <A NAME="ss3.4"></A> CD-ROM Installation</H2>
-
-<P> To make a CD-ROM bootable by SRM, simply build <CODE>aboot</CODE> as
-described above.  Then, make sure that the <CODE>bootlx</CODE> file is present
-on the iso9660 filesystem (e.g., copy <CODE>bootlx</CODE> to the directory
-that is the filesystem master, then run <CODE>mkisofs</CODE> on that
-directory).  After that, all that remains to be done is to mark the
-filesystem as SRM bootable.  This is achieved with a command of the
-form:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-isomarkboot filesystem bootlx
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The command above assumes that <CODE>filesystem</CODE> is a file containing
-the iso9660 filesystem and that <CODE>bootlx</CODE> has been copied into the
-root directory of that filesystem.  That's it!</P>
-<P></P>
-<P></P>
-
-<A NAME="Building Linux"></A> <H2>3.5 <A NAME="ss3.5"></A> Building the Linux Kernel</H2>
-
-<P> A bootable Linux kernel can be built with the following steps.  During
-the <CODE>make config</CODE>, be sure to answer "yes" to the question whether you
-want to boot the kernel via SRM.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd /usr/src/linux
-make config
-make dep
-make boot
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P></P>
-<P> The last command will build the file
-<CODE>arch/alpha/boot/vmlinux.gz</CODE> which can then be copied to the
-disk from which you want to boot from.  In our floppy disk example
-above, this would entail:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-mount /dev/fd0 /mnt
-cp arch/alpha/boot/vmlinux.gz /mnt
-umount /mnt
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P></P>
-<P></P>
-
-<A NAME="booting"></A> <H2>3.6 <A NAME="ss3.6"></A> Booting Linux</H2>
-
-<P> With the SRM firmware and <CODE>aboot</CODE> installed, Linux is generally
-booted with a command of the form:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<CODE>boot</CODE> <I>devicename</I> <CODE>-fi</CODE> <I>filename</I> <CODE>-fl</CODE> <I>flags</I>
-</CODE></BLOCKQUOTE>
-</P>
-<P></P>
-<P> The <I>filename</I> and <I>flags</I> arguments are optional.  If they
-are not specified, SRM uses the default values stored in environment
-variables <CODE>BOOT_OSFILE</CODE> and <CODE>BOOT_OSFLAGS</CODE>.  The
-syntax and meaning of these two arguments is described in more detail
-below.</P>
-<P></P>
-<P></P>
-<H3>Boot Filename</H3>
-
-<P> The filename argument takes the form:
-<BLOCKQUOTE>
-[<EM>n</EM>/]<EM>filename</EM>
-</BLOCKQUOTE>
-</P>
-<P><EM>n</EM> is a single digit in the range 1..8 that gives the partition
-number from which to boot from.  <EM>filename</EM> is the path of the file
-you want boot.  For example to boot from the second partition of SCSI
-device 6, you would enter:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-boot dka600 -file 2/vmlinux.gz
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Or to boot from floppy drive 0, you'd enter:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-boot dva0 -file vmlinux.gz
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P></P>
-<P> If a disk has no partition table , <CODE>aboot</CODE> pretends the disk
-contains one <CODE>ext2</CODE> partition starting at the first diskblock.
-This allows booting from floppy disks.</P>
-<P></P>
-<P> As a special case, partition number 0 is used to request booting
-from a disk that does not (yet) contain a file system.  When
-specifying "partition" number 0, <CODE>aboot</CODE> assumes that the Linux
-kernel is stored right behind the <CODE>aboot</CODE> image.  Such a layout
-can be achieved with the <CODE>swriteboot</CODE> command.  For example, to
-setup a filesystem-less boot from <CODE>/dev/sda</CODE>, one could use
-the command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-swriteboot /dev/sda bootlx vmlinux.gz
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P></P>
-<P> Booting a system in this way is not normally necessary.  The
-reason this feature exists is to make it possible to get Linux
-installed on a systems that can't boot from a floppy disk (e.g., the
-Jensen).</P>
-<P></P>
-<P></P>
-<H3>Boot Flags</H3>
-
-<P>A number of bootflags can be specified.  The syntax is:
-<BLOCKQUOTE><CODE>
-<PRE>
--flags &quot;options...&quot;
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Where "options..." is any combination the following options (separated
-by blanks).  There are many more bootoptions, depending on what
-drivers your kernel has installed.  The options listed below are
-therefore just examples to illustrate the general idea:</P>
-<P>
-<DL>
-<P></P>
-<DT><B>load_ramdisk=1</B><DD><P>Copy root file system from a (floppy) disk to the RAM disk
-before starting the system.  The RAM disk will be used in
-lieu of the root device.  This is useful to bootstrap Linux
-on a system with only one floppy drive.</P>
-<P></P>
-<DT><B>floppy=<EM>str</EM></B><DD><P>Sets floppy configuration to <EM>str</EM>.</P>
-<P></P>
-<DT><B>root=<EM>dev</EM></B><DD><P>Select device <EM>dev</EM> as the root-file
-system. The device can be specified as a major/minor hex number (e.g.,
-0x802 for /dev/sda2) or one of a few canonical names (e.g.,
-<CODE>/dev/fd0</CODE>, <CODE>/dev/sda2</CODE>).</P>
-<P></P>
-<DT><B>single</B><DD><P>Boot system in single user mode.</P>
-<P></P>
-<DT><B>kgdb</B><DD><P>Enable kernel-gdb (works only if <CODE>CONFIG_KGDB</CODE> is
-enabled; a second Alpha system needs to be connected over the serial
-port in order to make this work)</P>
-<P></P>
-</DL>
-</P>
-<P></P>
-<P> Some SRM implementations (e.g., the one for the Jensen) are
-handicapped and allow only short option strings (e.g., at most 8
-characters).  In such a case, <CODE>aboot</CODE> can be booted with the
-single-character boot flag "i".  With this flag, <CODE>aboot</CODE> will
-prompt the user to interacively enter a boot option string of up to
-256 characters.  For example:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-boot dka0 -fl i
-aboot&gt; 3/vmlinux.gz root=/dev/sda3 single
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Since booting in that manner quickly becomes tedious, <CODE>aboot</CODE>
-allows to define short-hands for frequently used commandlines.  In
-particular, a single digit option (0-9) requests that <CODE>aboot</CODE> uses
-the corresponding option string stored in file
-<CODE>/etc/aboot.conf</CODE>.  A sample <CODE>aboot.conf</CODE> is shown below:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# aboot default configurations
-#
-0:3/vmlinux.gz root=/dev/sda3
-1:3/vmlinux.gz root=/dev/sda3 single
-2:3/vmlinux.new.gz root=/dev/sda3
-3:3/vmlinux root=/dev/sda3
-8:- root=/dev/sda3            # fs-less boot of raw kernel
-9:0/vmlinux.gz root=/dev/sda3 # fs-less boot of (compressed) ECOFF kernel
--
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>With this configuration file, the command</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-boot dka0 -fl 1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>corresponds exactly to the boot command shown above.  It is quite easy
-to forget what number corresponds to what option string.  To alleviate
-this problem, boot with option "h" and <CODE>aboot</CODE> will print the
-contents of <CODE>/etc/aboot.conf</CODE> before issueing the prompt for
-the full option string.</P>
-<P>Finally, whenever <CODE>aboot</CODE> prompts for an option string, it is
-possible to enter one of the single character flags ("i", "h", or
-"0"-"9") to get the same effect as if that flag had been specified in
-the boot command line.  For example, you could boot with flag "i" and
-then type "h" (followed by return) to remind yourself of the contents of
-<CODE>/etc/aboot.conf</CODE></P>
-<P></P>
-<H3>Selecting the Partition of /etc/aboot.conf</H3>
-
-<P> When installed on a harddisk, <CODE>aboot</CODE> needs to know what
-partition to search for the <CODE>/etc/aboot.conf</CODE> file.  A newly
-compiled <CODE>aboot</CODE> will search the <EM>second</EM> partition (e.g.,
-<CODE>/dev/sda2</CODE>).  Since it would be inconvenient to have to
-recompile <CODE>aboot</CODE> just to change the partition number,
-<CODE>abootconf</CODE> allows to directly modify an installed <CODE>aboot</CODE>.
-Specifically, if you want to change <CODE>aboot</CODE> to use the <EM>third</EM>
-partition on disk <CODE>/dev/sda</CODE>, you'd use the command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-abootconf /dev/sda 3
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can verify the current setting by simply omitting the partition
-number.  That is: <CODE>abootconf /dev/sda</CODE> will print the currently
-selected partition number.  Note that <CODE>aboot</CODE> does have to be
-installed already for this command to succeed.  Also, when installing
-a new <CODE>aboot</CODE>, the partition number will fall back to the default
-(i.e., it will be necessary to rerun <CODE>abootconf</CODE>).</P>
-<P>Since <CODE>aboot</CODE> version 0.5, it is also possible to select the
-<CODE>aboot.conf</CODE> partition via the boot command line. This can be
-done with a command line of the form <I>a</I><CODE>:</CODE><I>b</I> where <I>a</I>
-is the partition that holds <CODE>/etc/aboot.conf</CODE> and <I>b</I> is a
-single-letter option as described above (<CODE>0</CODE>-<CODE>9</CODE>, <CODE>i</CODE>, or
-<CODE>h</CODE>). For example, if you type <CODE>boot -fl "3:h" dka100</CODE> the
-system boots from SCSI ID 1, loads <CODE>/etc/aboot.conf</CODE> from the
-third partition, prints its contents on the screen and waits for you
-to enter the boot options.</P>
-<P></P>
-<P></P>
-
-<A NAME="Network Booting"></A> <H2>3.7 <A NAME="ss3.7"></A> Booting Over the Network</H2>
-
-<P> Two prelimenary steps are necessary before Linux can be booted via
-a network.  First, you need to set the SRM environment variables to
-enable booting via the bootp protocol and second you need to setup
-another machine as the your boot server.  Please refer to the SRM
-documentation that came with your machine for information on how to
-enable bootp.  Setting up the boot server is obviously dependent on
-what operating system that machine is running, but typically it
-involves starting the program <CODE>bootpd</CODE> in the background after
-configuring the <CODE>/etc/bootptab</CODE> file.  The <CODE>bootptab</CODE> file
-has one entry describing each client that is allowed to boot from
-the server.  For example, if you want to boot the machine
-<CODE>myhost.cs.arizona.edu</CODE>, then an entry of the following form would
-be needed:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-myhost.cs.arizona.edu:\
-        :hd=/remote/:bf=vmlinux.bootp:\
-        :ht=ethernet:ha=08012B1C51F8:hn:vm=rfc1048:\
-        :ip=192.12.69.254:bs=auto:
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This entry assumes that the machine's Ethernet address is
-<CODE>08012B1C51F8</CODE> and that its IP address is 192.12.69.254.  The
-Ethernet address can be found with the <CODE>show device</CODE> command of the
-SRM console or, if Linux is running, with the <CODE>ifconfig</CODE> command.
-The entry also defines that if the client does not specify otherwise,
-the file that will be booted is <CODE>vmlinux.bootp</CODE> in directory
-<CODE>/remote</CODE>.  For more information on configuring <CODE>bootpd</CODE>,
-please refer to its man page.</P>
-<P>Next, build <CODE>aboot</CODE> with with the command <CODE>make netboot</CODE>.  Make
-sure the kernel that you want to boot has been built already.  By
-default, the <CODE>aboot</CODE> <CODE>Makefile</CODE> uses the kernel in
-<CODE>/usr/src/linux/arch/alpha/boot/vmlinux.gz</CODE> (edit the
-<CODE>Makefile</CODE> if you want to use a different path).  The result of
-<CODE>make netboot</CODE> is a file called <CODE>vmlinux.bootp</CODE> which contains
-<CODE>aboot</CODE> <EM>and</EM> the Linux kernel, ready for network booting.</P>
-<P>Finally, copy <CODE>vmlinux.bootp</CODE> to the bootsever's directory.  In the
-example above, you'd copy it into <CODE>/remote/vmlinux.bootp</CODE>.
-Next, power up the client machine and boot it, specifying the Ethernet
-adapter as the boot device.  Typically, SRM calls the first Ethernet
-adapter <CODE>ewa0</CODE>, so to boot from that device, you'd use the command:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-boot ewa0
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The <CODE>-fi</CODE> and <CODE>-fl</CODE> options can be used as usual.  In
-particular, you can ask <CODE>aboot</CODE> to prompt for Linux kernel
-arguments by specifying the option <CODE>-fl i</CODE>.</P>
-<P></P>
-
-<HR>
-<P>
-<A HREF="srm-4.html">Next</A> Chapter,
-<A HREF="srm-2.html">Previous</A> Chapter
-<P>
-Table of contents of <A HREF="srm.html#toc3">this chapter</A>,
- General <A HREF="srm.html#toc">table of contents</A></P>
-<P>
-<A HREF="srm.html">Top</A> of the document,
- <A HREF="#0"> Beginning of this Chapter</A></P>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/srm-4.html b/english/ports/alpha/faq/srm-4.html
deleted file mode 100644
index 3cb80974b16..00000000000
--- a/english/ports/alpha/faq/srm-4.html
+++ /dev/null
@@ -1,169 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>Sharing a Disk With DEC Unix</TITLE>
-</HEAD>
-<BODY>
-<H1>4. <A NAME="s4"></A>Sharing a Disk With DEC Unix</H1>
-<P>
-<A HREF="srm.html#toc4">Contents of this section</A></P>
-
-<P> Unfortunately, DEC Unix doesn't know anything about Linux, so
-sharing a single disk between the two OSes is not entirely trivial.
-However, it is not a difficult task if you heed the tips in this
-section.  The section assumes you are using <CODE>aboot</CODE> version 0.5 or
-newer.</P>
-<P></P>
-<H2>4.1 <A NAME="ss4.1"></A> Partitioning the disk</H2>
-
-<P> First and foremost: <EM>never</EM> use any of the Linux partitioning
-programs (<CODE>minlabel</CODE> or <CODE>fdisk</CODE>) on a disk that is also used by
-DEC Unix.  The Linux <CODE>minlabel</CODE> program uses the same partition
-table format as DEC Unix <CODE>disklabel</CODE>, but there are some
-incompatibilities in the data that <CODE>minlabel</CODE> fills in, so DEC Unix
-will simply refuse to accept a partition table generated by
-<CODE>minlabel</CODE>.  To setup a Linux <CODE>ext2</CODE> partition under DEC Unix,
-you'll have to change the disktab entry for your disk.  For the
-purpose of this discussion, let's assume that you have an rz26 disk (a
-common 1GB drive) on which you want to install Linux.  The disktab
-entry under DEC Unix v3.2 looks like this (see file
-<CODE>/etc/disktab</CODE>):</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-rz26|RZ26|DEC RZ26 Winchester:\
-        :ty=winchester:dt=SCSI:ns#57:nt#14:nc#2570:\
-        :oa#0:pa#131072:ba#8192:fa#1024:\
-        :ob#131072:pb#262144:bb#8192:fb#1024:\
-        :oc#0:pc#2050860:bc#8192:fc#1024:\
-        :od#393216:pd#552548:bd#8192:fd#1024:\
-        :oe#945764:pe#552548:be#8192:fe#1024:\
-        :of#1498312:pf#552548:bf#8192:ff#1024:\
-        :og#393216:pg#819200:bg#8192:fg#1024:\
-        :oh#1212416:ph#838444:bh#8192:fh#1024:
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The interesting fields here are <CODE>o</CODE><I>?</I>, and <CODE>p</CODE><I>?</I>, where
-<I>?</I> is a letter in the range <CODE>a</CODE>-<CODE>h</CODE> (first through 8-th
-partition).  The <CODE>o</CODE> value gives the starting offset of the
-partition (in sectors) and the <CODE>p</CODE> value gives the size of the
-partition (also in sectors).  See <CODE>disktab(4)</CODE> for more info.  Note
-that DEC Unix likes to define overlapping partitions.  For the entry
-above, the partition layout looks like this (you can verify this by
-adding up the various <CODE>o</CODE> and <CODE>p</CODE> values):</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-  a     b         d           e           f
-|---|-------|-----------|-----------|-----------|
-
-                        c
-|-----------------------------------------------|
-
-                     g                 h
-            |-----------------|-----------------|
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>DEC Unix insists that partition <CODE>a</CODE> starts at offset 0 and that
-partition <CODE>c</CODE> spans the entire disk.  Other than that, you can
-setup the partition table any way you like.</P>
-<P>Let's suppose you have DEC Unix using partition <CODE>g</CODE> and want to
-install Linux on partition <CODE>h</CODE> with partition <CODE>b</CODE> being a
-(largish) swap partition.  To get this layout without destroying the
-existing DEC Unix partition, you need to set the partition types
-explicitly.  You can do this by adding a <CODE>t</CODE> field for each
-partition.  In our case, we add the following line to the above
-disktab entry.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-        :ta=unused:tb=swap:tg=4.2BSD:th=resrvd8:
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Now why do we mark partition <CODE>h</CODE> as "reservd8" instead of "ext2"?
-Well, DEC Unix doesn't know about Linux.  It so happens that partition
-type "ext2" corresponds to a numeric value of 8, and DEC Unix uses the
-string "reservd8" for that value.  Thus, in DEC Unix speak, "reservd8"
-means "ext2".  OK, this was the hard part.  Now we just need to
-install the updated disktab entry on the disk.  Let's assume the disk
-has SCSI id 5.  In this case, we'd do:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-disklabel -rw /dev/rrz5c rz26
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can verify that everything is all right by reading back the
-disklabel with <CODE>disklabel -r /dev/rrz5c</CODE>.  At this point, you
-may want to reboot DEC Unix and make sure the existing DEC Unix
-partition is still alive and well.  If that is the case, you can shut
-down the machine and start with the Linux installation.  Be sure to
-skip the disk partitioning step during the install.  Since we already
-installed a good partition table, you should be able to proceed and
-select the 8th partition as the Linux root partition and the 2nd
-partition as the swap partition.  If the disk is, say, the second SCSI
-disk in the machine, then the device name for these partitions would
-be <CODE>/dev/sdb8</CODE> and <CODE>/dev/sdb2</CODE>, respectively (note that
-Linux uses letters to name the drives and numbers to name the
-partitions, which is exactly reversed from what DEC Unix does; the
-Linux scheme makes more sense, of course ;-).</P>
-<P></P>
-<P></P>
-
-<H2>4.2 <A NAME="ss4.2"></A> Installing <CODE>aboot</CODE></H2>
-
-<P> <EM>First big caveat</EM>: with the SRM firmware, you can boot one and
-only one operating system per disk.  For this reason, it is generally
-best to have at least two SCSI disks in a machine that you want to
-dualboot between Linux and DEC Unix.  Of course, you could also boot
-Linux from a floppy if speed doesn't matter or over the network, if
-you have a <CODE>bootp</CODE>-capable server.  But in this section we assume
-you want to boot Linux from a disk that contains one or more DEC Unix
-partitions.</P>
-<P><EM>Second big caveat</EM>: installing <CODE>aboot</CODE> on a disk shared with
-DEC Unix renders the first and third partition unusable (since those
-<EM>must</EM> have a starting offset of 0).  For this reason, we recommend
-that you change the size of partition <CODE>a</CODE> to something that is just
-big enough to hold <CODE>aboot</CODE> (1MB should be plenty).</P>
-<P>Once these two caveats are taken care of, installing <CODE>aboot</CODE> is
-almost as easy as usual: since partition <CODE>a</CODE> and <CODE>c</CODE> will
-overlap with <CODE>aboot</CODE>, we need to tell <CODE>swriteboot</CODE> that this is
-indeed OK.  We can do this under Linux with a command line of the
-following form (again, assuming we're trying to install <CODE>aboot</CODE> on
-the second SCSI disk):</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-swriteboot -f1 -f3 /dev/sdb bootlx
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The <CODE>-f1</CODE> means that we want to force writing <CODE>bootlx</CODE> even
-though it overlaps with partition 1.  The corresponding applies for
-partition 3.</P>
-<P>This is it.  You should now be able to shutdown the system and boot
-Linux from the harddisk.  In our example, the SRM command line to do
-this would be:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-boot dka5 -fi 8/vmlinux.gz -fl root=/dev/sdb8
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P></P>
-
-<HR>
-<P>
-<A HREF="srm-3.html">Previous</A> Chapter
-<P>
-Table of contents of <A HREF="srm.html#toc4">this chapter</A>,
- General <A HREF="srm.html#toc">table of contents</A></P>
-<P>
-<A HREF="srm.html">Top</A> of the document,
- <A HREF="#0"> Beginning of this Chapter</A></P>
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/faq/srm.html b/english/ports/alpha/faq/srm.html
deleted file mode 100644
index ad1fd2f4ea3..00000000000
--- a/english/ports/alpha/faq/srm.html
+++ /dev/null
@@ -1,60 +0,0 @@
-
-
-
-
-
-<HTML>
-<HEAD>
-<TITLE>SRM Firmware Howto</TITLE>
-</HEAD>
-<BODY>
-<H1>SRM Firmware Howto</H1>
-
-<H2>
-<A HREF="mailto:davidm@azstarnet.com">David Mosberger</A>
-</H2>v0.5, 17 August 1996
-<P><HR><EM>This document describes how to boot Linux/Alpha using the SRM
-firmware, which is the firmware normally used to boot DEC Unix.
-Generally, it is preferable to use MILO instead of aboot since MILO is
-perfectly adapted to the needs of Linux.  However, MILO is not always
-available for a particular system and MILO does not presently have the
-ability to boot over the network.  In either case, using the SRM
-console may be  the right solution.</EM><HR></P>
-<P> Unless you're interested in technical details, you may want to
-skip right to Section 
-<A HREF="srm-3.html#aboot">aboot</A>
-.</P>
-<P></P>
-<P>
-<H2><A NAME="toc1"></A>1. <A HREF="srm-1.html">How Does SRM Boot an OS?</A></H2>
-<UL>
-<LI><A HREF="srm-1.html#ss1.1">1.1 Loading The Secondary Bootstrap Loader</A>
-</UL>
-
-<P>
-<H2><A NAME="toc2"></A>2. <A HREF="srm-2.html">The Raw Loader</A></H2>
-<UL>
-</UL>
-
-<P>
-<H2><A NAME="toc3"></A>3. <A HREF="srm-3.html">The aboot Loader</A></H2>
-<UL>
-<LI><A HREF="srm-3.html#ss3.1">3.1 Getting and Building aboot</A>
-<LI><A HREF="srm-3.html#ss3.2">3.2 Floppy Installation</A>
-<LI><A HREF="srm-3.html#ss3.3">3.3 Harddisk Installation</A>
-<LI><A HREF="srm-3.html#ss3.4">3.4 CD-ROM Installation</A>
-<LI><A HREF="srm-3.html#ss3.5">3.5 Building the Linux Kernel</A>
-<LI><A HREF="srm-3.html#ss3.6">3.6 Booting Linux</A>
-<LI><A HREF="srm-3.html#ss3.7">3.7 Booting Over the Network</A>
-</UL>
-
-<P>
-<H2><A NAME="toc4"></A>4. <A HREF="srm-4.html">Sharing a Disk With DEC Unix</A></H2>
-<UL>
-<LI><A HREF="srm-4.html#ss4.1">4.1 Partitioning the disk</A>
-<LI><A HREF="srm-4.html#ss4.2">4.2 Installing <CODE>aboot</CODE></A>
-</UL>
-
-
-</BODY>
-</HTML>
diff --git a/english/ports/alpha/glibc21-page.wml b/english/ports/alpha/glibc21-page.wml
deleted file mode 100644
index dd378fbe3aa..00000000000
--- a/english/ports/alpha/glibc21-page.wml
+++ /dev/null
@@ -1,33 +0,0 @@
-#use wml::debian::template title="Glibc 2.1 on Alpha" NOHEADER="yes"
-#include "$(ENGLISHDIR)/ports/alpha/menu.inc"
-# $Id$
-
-<h1>Glibc 2.1 on Alpha</h1>
-
-<p>Now that the work on slink has concluded, it's time to move along
-to the new glibc 2.1.  Developers based on Alphas must be aware of
-some issues before getting involved with glibc 2.1:</p>
-
-<ul>
-<li><b>Glibc 2.1 binaries are NOT backwardly compatible with glibc 2.0</b><br>
-That's right...if you compile something on a glibc 2.1 system, you CANNOT
-run that binary on a glibc 2.0 system.  This is due to many changes in the
-internal structure of glibc 2.1 from 2.0 along with some other interface
-changes.  More to come as I find the related info in the docs.</li>
-
-<li><b>Library packages must be recompiled before use on glibc 2.1 systems</b><br>
-This is related to the above.  In addition, some soname changes occurred with
-respect to libstdc++, so all C++ software should be recompiled on glibc 2.1
-systems.</li>
-
-<li><b>New gcc is required</b><br>
-To accommodate the above, a new gcc is on the way to address many of the
-above issues more easily.  Obviously, with a new version of gcc, it is
-often best to recompile your packages with it.</li>
-</ul>
-
-<p>As I have said, I will provide further information as I come across it
-in the glibc 2.1 documentation (which is sparse at the time of this writing).
-</p>
-
-<p>&mdash; Christopher C. Chimelis &lt;chris@debian.org&gt;</p>
diff --git a/english/ports/alpha/port-status.wml b/english/ports/alpha/port-status.wml
index 25e28abfca7..1be22876c07 100644
--- a/english/ports/alpha/port-status.wml
+++ b/english/ports/alpha/port-status.wml
@@ -1,12 +1,14 @@
 #use wml::debian::template title="Alpha Port -- Status" NOHEADER="yes"
 #include "$(ENGLISHDIR)/ports/alpha/menu.inc"
+# $Id$
 
-<h1>Debian GNU/Linux on Alpha -- Status</h1>
+<h1>Debian GNU/Linux on Alpha &ndash; Status</h1>
 
 <h2>The unstable distribution ("sid")</h2>
 
-<p>Alpha port is continued to be developed. The automatic package build
-daemon for alpha is operational.</p>
+<p>Alpha port is continued to be developed. The automatic package 
+<a href="http://buildd.debian.org/">build daemons</a> for alpha are
+operational.</p>
 
 <h2>Debian GNU/Linux 3.0 "woody"</h2>
 
@@ -17,10 +19,20 @@ daemon for alpha is operational.</p>
 <p>Potato has much more software available and supports
 more types of Alphas than slink did.</p>
 
-<ul>
-<li><A HREF="glibc21-page">Glibc 2.1 Information for potato</A></li>
-</ul>
-
 <h2>Debian GNU/Linux 2.1 "slink"</h2>
 
 <p>The alpha port was initially released with this release.</p>
+
+<h1>Hardware support</h1>
+
+<p>Quite a lot of hardware is now supported on Linux/Alpha. Unfortunately,
+   the exact combination of machine, hardware and kernel version is
+   non-trivial, so if you don't find your combo in 
+   <a href="http://www.alphalinux.org/ALOHcl">this list on alphalinux.org</a>,
+   and researching the
+   <a href="links#lists">list archives for Debian and RedHat</a>-AXP-Lists
+   neither yields a result, then 
+   <a href="http://lists.debian.org/debian-alpha/">subscribe</a> to the
+   Debian-Alpha list and ask.
+   Usually someone has tried already and can provide useful
+   information.</p>
author	Frank Lichtenheld <djpig>	2004-04-15 20:28:55 +0000
committer	Frank Lichtenheld <djpig>	2004-04-15 20:28:55 +0000
commit	4dbe170de7d7931109b309063fdd09abb48569bb (patch)
tree	a411312ec0b41546a4938d72783c375059ee7348 /english/ports/alpha
parent	d24dad9691b0b2a9a6ffd25d780c919b7c418490 (diff)