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 --- da/install-methods/download/alpha.xml | 36 ++++++++++++++++++++++++++++++++ da/install-methods/download/arm.xml | 37 +++++++++++++++++++++++++++++++++ da/install-methods/download/m68k.xml | 22 ++++++++++++++++++++ da/install-methods/download/powerpc.xml | 28 +++++++++++++++++++++++++ 4 files changed, 123 insertions(+) create mode 100644 da/install-methods/download/alpha.xml create mode 100644 da/install-methods/download/arm.xml create mode 100644 da/install-methods/download/m68k.xml create mode 100644 da/install-methods/download/powerpc.xml (limited to 'da/install-methods/download') diff --git a/da/install-methods/download/alpha.xml b/da/install-methods/download/alpha.xml new file mode 100644 index 000000000..6aec375c3 --- /dev/null +++ b/da/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/da/install-methods/download/arm.xml b/da/install-methods/download/arm.xml new file mode 100644 index 000000000..f0bc838b0 --- /dev/null +++ b/da/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/da/install-methods/download/m68k.xml b/da/install-methods/download/m68k.xml new file mode 100644 index 000000000..a0dfd011c --- /dev/null +++ b/da/install-methods/download/m68k.xml @@ -0,0 +1,22 @@ + + + + + + Choosing a Kernel + + + +Some m68k subarchs have a choice of kernels to install. In general we +recommend trying the most recent version first. If your subarch or +machine needs to use a 2.2.x kernel, make sure you choose one of the +images that supports 2.2.x kernels (see the MANIFEST). + + + + +All of the m68k images for use with 2.2.x kernels, require the kernel +parameter &ramdisksize;. + + + diff --git a/da/install-methods/download/powerpc.xml b/da/install-methods/download/powerpc.xml new file mode 100644 index 000000000..f8902926d --- /dev/null +++ b/da/install-methods/download/powerpc.xml @@ -0,0 +1,28 @@ + + + + -- cgit v1.2.3