move manual to top-level directory, split out of debian-installer package

4 files changed, 201 insertions, 0 deletions

diff --git a/eu/install-methods/download/alpha.xml b/eu/install-methods/download/alpha.xml
new file mode 100644
index 000000000..6aec375c3
--- /dev/null
+++ b/eu/install-methods/download/alpha.xml
@@ -0,0 +1,36 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+
+   <sect3 arch="alpha"><title>Alpha Installation Files</title>
+<para>
+
+If you choose to boot from ARC console firmware using
+<command>MILO</command>, you will also need to prepare a disk
+containing <command>MILO</command> and <command>LINLOAD.EXE</command>
+from the provided disk images. See <xref linkend="alpha-firmware"/>
+for more information on Alpha
+firmware and boot loaders. The floppy images can be found in the
+<filename>MILO</filename> directory as
+<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>.
+
+</para><para>
+
+Unfortunately, these <command>MILO</command> images could not be
+tested and might not work for all subarchitectures. If you find it
+doesn't work for you, try copying the appropriate
+<command>MILO</command> binary onto the floppy 
+(<ulink url="&disturlftp;main/disks-alpha/current/MILO/"></ulink>).  
+Note that those <command>MILO</command>s don't support ext2 ``sparse
+superblocks'', so you can't use them to load kernels from newly
+generated ext2 file systems. As a workaround, you can put your kernel
+onto the FAT partition next to the <command>MILO</command>.
+
+</para><para>
+
+<command>MILO</command> binaries are platform-specific.  See 
+<xref linkend="alpha-cpus"/> to determine the appropriate
+<command>MILO</command> image for your Alpha platform.  
+
+</para>
+   </sect3>
diff --git a/eu/install-methods/download/arm.xml b/eu/install-methods/download/arm.xml
new file mode 100644
index 000000000..f0bc838b0
--- /dev/null
+++ b/eu/install-methods/download/arm.xml
@@ -0,0 +1,37 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+
+   <sect3 arch="arm" id="riscpc-install-files">
+   <title>RiscPC Installation Files</title>
+<para>
+
+The RiscPC installer is booted initially from RISC OS.  All the
+necessary files are provided in one Zip archive, &rpc-install-kit;.
+Download this file onto the RISC OS machine, copy the
+<filename>linloader.!Boot</filename> components into place, and run
+<filename>!dInstall</filename>. 
+
+</para>
+   </sect3>
+
+   <sect3 arch="arm" id="netwinder-install-files">
+   <title>NetWinder Installation Files</title>
+<para>
+
+The easiest way to boot a NetWinder is over the network, using the
+supplied TFTP image &netwinder-boot-img;.
+
+</para> 
+   </sect3>
+
+   <sect3 arch="arm" id="cats-install-files">
+   <title>CATS Installation Files</title>
+<para>
+
+The only supported boot method for CATS is to use the combined image
+&cats-boot-img;.  This can be loaded from any device accessible to the
+Cyclone bootloader.
+
+</para>
+   </sect3>
diff --git a/eu/install-methods/download/m68k.xml b/eu/install-methods/download/m68k.xml
new file mode 100644
index 000000000..471d64273
--- /dev/null
+++ b/eu/install-methods/download/m68k.xml
@@ -0,0 +1,102 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+
+   <sect3 arch="m68k" id="amiga-install-files">
+   <title>AmigaOS Installation Files</title>
+
+<orderedlist>
+<listitem><para>
+
+Instead of the boot, root, and driver files above, just download
+&amiga-install-tarball;.
+
+</para></listitem>
+<listitem><para>
+
+Unpack &amiga-install-tarball; into a partition with at least 25MB
+free.  We recommend you unpack it into a directory named
+<filename>debian</filename>.  The &amiga-install-tarball; will create an
+<filename>amiga</filename> subdirectory.
+
+</para></listitem>
+<listitem><para>
+
+Write down the Linux partition name for the location where your new
+<filename>debian</filename> directory is.  See 
+<xref linkend="device-names"/> for more information on Linux partition
+naming.
+
+</para></listitem>
+</orderedlist>
+   </sect3>
+
+   <sect3 arch="m68k" id="atari-install-files">
+   <title>Atari TOS Installation Files </title>
+
+<orderedlist>
+<listitem><para>
+
+Instead of the boot, root, and driver files above, just download
+&atari-install-tarball;.
+
+</para></listitem>
+<listitem><para>
+
+Unpack &atari-install-tarball; into a partition with at least 25 MB
+free. We recommend you unpack it into a directory named
+<filename>debian</filename>.
+
+</para></listitem>
+<listitem><para>
+
+After unpacking, you should have an <filename>atari</filename>
+subdirectory. Do not rename any files in this directory.
+
+</para></listitem>
+<listitem><para>
+
+Write down the Linux partition name for the location where your new
+<filename>debian</filename> directory is. See 
+<xref linkend="device-names"/> for more
+information on Linux partition naming.
+
+</para></listitem>
+</orderedlist>
+   </sect3>
+
+   <sect3 arch="m68k" id="mac-install-files">
+   <title>68k MacOS Installation Files</title>
+
+<orderedlist>
+<listitem><para>
+
+Instead of the boot, root, and driver files above, just download
+&mac-install-tarball;.
+
+</para></listitem>
+<listitem><para>
+
+Unpack &mac-install-tarball; into a partition with at least 25 MB
+free. We recommend you unpack it into a directory named
+<filename>debian</filename>. Use <application>Stuffit Expander</application>
+(at least version 5.5) or <command>MacGZip</command> to extract it
+from its archive.
+
+</para></listitem>
+<listitem><para>
+
+After unpacking, you should have a <filename>mac</filename> subdirectory. Do
+not rename any files in this directory. Do not allow your
+decompression program to decompress drivers.tgz.
+
+</para></listitem>
+<listitem><para>
+
+Write down the Linux partition name for the location where your new
+<filename>debian</filename> directory is. See <xref linkend="device-names"/>
+for more information on Linux partition naming.
+
+</para></listitem>
+</orderedlist>
+   </sect3>
diff --git a/eu/install-methods/download/powerpc.xml b/eu/install-methods/download/powerpc.xml
new file mode 100644
index 000000000..8797b27fa
--- /dev/null
+++ b/eu/install-methods/download/powerpc.xml
@@ -0,0 +1,26 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 11648 untranslated -->
+
+
+   <sect3 arch="powerpc" id="newworld-install-files">
+   <title>NewWorld MacOS Installation Files </title>
+<para>
+
+For floppy-less installation on NewWorld Macs, it may be most
+convenient to obtain all the necessary files packaged into one Stuffit
+archive from 
+<ulink url="&url-powerpc-of;"></ulink> (separate instructions are
+included in the archive). Otherwise, obtain the normal installation
+files listed above. Retrieve the files to an HFS (not HFS+) partition
+on your system.  You will also need the <filename>yaboot</filename> and
+<filename>yaboot.conf</filename> files from the 
+<ulink url="&downloadable-file;new-powermac/">new-powermac</ulink> or 
+<ulink url="&downloadable-file;powermac/">powermac</ulink> archive folder.
+However, the newest G4 PowerMacs, and those that work without MacOS 9,
+need the newest version of <command>yaboot</command>; the one in the
+archive will not work. Obtain the newest version from 
+<ulink url="http://penguinppc.org/projects/yaboot/"></ulink>.
+
+</para>
+   </sect3>
+