From 1ea73eea5ecc6a8ed901316049259aee737ee554 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 7 Oct 2005 19:51:38 +0000 Subject: move manual to top-level directory, split out of debian-installer package --- eu/install-methods/download/alpha.xml | 36 +++++++++++ eu/install-methods/download/arm.xml | 37 ++++++++++++ eu/install-methods/download/m68k.xml | 102 ++++++++++++++++++++++++++++++++ eu/install-methods/download/powerpc.xml | 26 ++++++++ 4 files changed, 201 insertions(+) create mode 100644 eu/install-methods/download/alpha.xml create mode 100644 eu/install-methods/download/arm.xml create mode 100644 eu/install-methods/download/m68k.xml create mode 100644 eu/install-methods/download/powerpc.xml (limited to 'eu/install-methods/download') 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 @@ + + + + + Alpha Installation Files + + +If you choose to boot from ARC console firmware using +MILO, you will also need to prepare a disk +containing MILO and LINLOAD.EXE +from the provided disk images. See +for more information on Alpha +firmware and boot loaders. The floppy images can be found in the +MILO directory as +milo_subarchitecture.bin. + + + +Unfortunately, these MILO 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 +MILO binary onto the floppy +(). +Note that those MILOs 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 MILO. + + + +MILO binaries are platform-specific. See + to determine the appropriate +MILO image for your Alpha platform. + + + 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 @@ + + + + + + RiscPC Installation Files + + +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 +linloader.!Boot components into place, and run +!dInstall. + + + + + + NetWinder Installation Files + + +The easiest way to boot a NetWinder is over the network, using the +supplied TFTP image &netwinder-boot-img;. + + + + + + CATS Installation Files + + +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. + + + 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 @@ + + + + + + AmigaOS Installation Files + + + + +Instead of the boot, root, and driver files above, just download +&amiga-install-tarball;. + + + + +Unpack &amiga-install-tarball; into a partition with at least 25MB +free. We recommend you unpack it into a directory named +debian. The &amiga-install-tarball; will create an +amiga subdirectory. + + + + +Write down the Linux partition name for the location where your new +debian directory is. See + for more information on Linux partition +naming. + + + + + + + Atari TOS Installation Files + + + + +Instead of the boot, root, and driver files above, just download +&atari-install-tarball;. + + + + +Unpack &atari-install-tarball; into a partition with at least 25 MB +free. We recommend you unpack it into a directory named +debian. + + + + +After unpacking, you should have an atari +subdirectory. Do not rename any files in this directory. + + + + +Write down the Linux partition name for the location where your new +debian directory is. See + for more +information on Linux partition naming. + + + + + + + 68k MacOS Installation Files + + + + +Instead of the boot, root, and driver files above, just download +&mac-install-tarball;. + + + + +Unpack &mac-install-tarball; into a partition with at least 25 MB +free. We recommend you unpack it into a directory named +debian. Use Stuffit Expander +(at least version 5.5) or MacGZip to extract it +from its archive. + + + + +After unpacking, you should have a mac subdirectory. Do +not rename any files in this directory. Do not allow your +decompression program to decompress drivers.tgz. + + + + +Write down the Linux partition name for the location where your new +debian directory is. See +for more information on Linux partition naming. + + + + 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 @@ + + + + + + NewWorld MacOS Installation Files + + +For floppy-less installation on NewWorld Macs, it may be most +convenient to obtain all the necessary files packaged into one Stuffit +archive from + (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 yaboot and +yaboot.conf files from the +new-powermac or +powermac archive folder. +However, the newest G4 PowerMacs, and those that work without MacOS 9, +need the newest version of yaboot; the one in the +archive will not work. Obtain the newest version from +. + + + + -- cgit v1.2.3