diff options
Diffstat (limited to 'en/install-methods')
-rw-r--r-- | en/install-methods/download/alpha.xml | 36 | ||||
-rw-r--r-- | en/install-methods/downloading-files.xml | 1 | ||||
-rw-r--r-- | en/install-methods/install-tftp.xml | 33 |
3 files changed, 0 insertions, 70 deletions
diff --git a/en/install-methods/download/alpha.xml b/en/install-methods/download/alpha.xml deleted file mode 100644 index 280187987..000000000 --- a/en/install-methods/download/alpha.xml +++ /dev/null @@ -1,36 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect3 arch="alpha"><title>Alpha Installation Files</title> -<para> - -If you choose to boot from ARC console firmware using -<command>MILO</command>, you will also need to prepare a disk -containing <command>MILO</command> and <command>LINLOAD.EXE</command> -from the provided disk images. See <xref linkend="alpha-firmware"/> -for more information on Alpha -firmware and boot loaders. The floppy images can be found in the -<filename>MILO</filename> directory as -<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>. - -</para><para> - -Unfortunately, these <command>MILO</command> images could not be -tested and might not work for all subarchitectures. If you find it -doesn't work for you, try copying the appropriate -<command>MILO</command> binary onto the floppy -(<ulink url="&disturlftp;main/disks-alpha/current/MILO/"></ulink>). -Note that those <command>MILO</command>s don't support ext2 <quote>sparse -superblocks</quote>, so you can't use them to load kernels from newly -generated ext2 file systems. As a workaround, you can put your kernel -onto the FAT partition next to the <command>MILO</command>. - -</para><para> - -<command>MILO</command> binaries are platform-specific. See -<xref linkend="alpha-cpus"/> to determine the appropriate -<command>MILO</command> image for your Alpha platform. - -</para> - </sect3> diff --git a/en/install-methods/downloading-files.xml b/en/install-methods/downloading-files.xml index 7be75fd04..8ec61a025 100644 --- a/en/install-methods/downloading-files.xml +++ b/en/install-methods/downloading-files.xml @@ -26,7 +26,6 @@ The installation images are located on each Debian mirror in the directory lists each image and its purpose. </para> -&download-alpha.xml; &download-arm.xml; &download-powerpc.xml; diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index eff4340da..ea56b6889 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -38,23 +38,6 @@ For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP. -</para><para arch="alpha"> - -Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM -console will <emphasis>not</emphasis> use RARP to obtain its IP -address, and therefore you must use BOOTP for net booting your -Alpha<footnote> - -<para> -Alpha systems can also be net-booted using the DECNet MOP (Maintenance -Operations Protocol), but this is not covered here. Presumably, your -local OpenVMS operator will be happy to assist you should you have -some burning need to use MOP to boot Linux on your Alpha. -</para> - -</footnote>. You can also enter the IP configuration for network -interfaces directly in the SRM console. - </para><para arch="hppa"> Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. @@ -221,22 +204,6 @@ to <command>tftpd</command> as the filename to boot. </para> - <sect3 arch="alpha"> - <title>Alpha TFTP Booting</title> -<para> -On Alpha, you must specify the filename (as a relative path to the -boot image directory) using the <userinput>-file</userinput> argument -to the SRM <userinput>boot</userinput> command, or by setting the -<userinput>BOOT_FILE</userinput> environment variable. Alternatively, -the filename can be given via BOOTP (in ISC <command>dhcpd</command>, -use the <userinput>filename</userinput> directive). Unlike Open -Firmware, there is <emphasis>no default filename</emphasis> on SRM, so -you <emphasis>must</emphasis> specify a filename by either one of -these methods. - -</para> - </sect3> - <sect3 arch="sparc"> <title>SPARC TFTP Booting</title> <para> |