diff options
Diffstat (limited to 'en/install-methods')
-rw-r--r-- | en/install-methods/create-floppy.xml | 6 | ||||
-rw-r--r-- | en/install-methods/download/m68k.xml | 23 | ||||
-rw-r--r-- | en/install-methods/downloading-files.xml | 1 | ||||
-rw-r--r-- | en/install-methods/floppy/m68k.xml | 27 | ||||
-rw-r--r-- | en/install-methods/install-tftp.xml | 21 |
5 files changed, 0 insertions, 78 deletions
diff --git a/en/install-methods/create-floppy.xml b/en/install-methods/create-floppy.xml index fb384b4ab..8489678ac 100644 --- a/en/install-methods/create-floppy.xml +++ b/en/install-methods/create-floppy.xml @@ -13,11 +13,6 @@ installer on hardware that cannot boot from CD or by other means. Booting the installer from floppy disk reportedly fails on Mac USB floppy drives. -</para><para arch="m68k"> - -Booting the installer from floppy disk is not supported on Amigas or -68k Macs. - </para><para> Disk images are files containing the complete contents of a floppy @@ -107,7 +102,6 @@ to install it. </sect2> &floppy-i386.xml; <!-- can be used for other arches --> -&floppy-m68k.xml; &floppy-powerpc.xml; </sect1> diff --git a/en/install-methods/download/m68k.xml b/en/install-methods/download/m68k.xml deleted file mode 100644 index a89b62076..000000000 --- a/en/install-methods/download/m68k.xml +++ /dev/null @@ -1,23 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect3 arch="m68k" id="kernel-22"> - <title>Choosing a Kernel</title> - -<para> - -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 <ulink -url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>). - -</para> -<para> - -All of the m68k images for use with 2.2.x kernels, require the kernel -parameter &ramdisksize;. - -</para> - </sect3> diff --git a/en/install-methods/downloading-files.xml b/en/install-methods/downloading-files.xml index 662986267..7be75fd04 100644 --- a/en/install-methods/downloading-files.xml +++ b/en/install-methods/downloading-files.xml @@ -29,7 +29,6 @@ lists each image and its purpose. &download-alpha.xml; &download-arm.xml; &download-powerpc.xml; -&download-m68k.xml; </sect2> diff --git a/en/install-methods/floppy/m68k.xml b/en/install-methods/floppy/m68k.xml deleted file mode 100644 index 776bfd0bc..000000000 --- a/en/install-methods/floppy/m68k.xml +++ /dev/null @@ -1,27 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- $Id$ --> - - - <sect2 arch="m68k"><title>Writing Disk Images on Atari Systems</title> -<para> - -You'll find the &rawwrite.ttp; program in the same directory as the -floppy disk images. Start the program by double clicking on the -program icon, and type in the name of the floppy image file you want -written to the floppy at the TOS program command line dialog box. - -</para> - - </sect2> - - <sect2 arch="m68k"><title>Writing Disk Images on Macintosh Systems</title> -<para> - -Since the current release does not yet support booting from floppies to -start the installation, there would be no point in doing this on -Macintosh Systems. However, these files are needed for the installation -of the operating system and modules, later in the process. - -</para> - - </sect2> diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index efd69e631..eff4340da 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -28,9 +28,6 @@ way is to use the BOOTP protocol.</phrase> informs a computer of its IP address and where on the network to obtain a boot image.</phrase> -<phrase arch="m68k">Yet another alternative exists on VMEbus -systems: the IP address can be manually configured in boot ROM.</phrase> - The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. @@ -277,24 +274,6 @@ in the directory that the TFTP server looks in. </para> </sect3> - <sect3 arch="m68k"> - <title>BVM/Motorola TFTP Booting</title> -<para> - -For BVM and Motorola VMEbus systems copy the files -&bvme6000-tftp-files; to <filename>/tftpboot/</filename>. - -</para><para> - -Next, configure your boot ROMs or BOOTP server to initially load the -<filename>tftplilo.bvme</filename> or -<filename>tftplilo.mvme</filename> files from the TFTP server. Refer -to the <filename>tftplilo.txt</filename> file for your subarchitecture -for additional system-specific configuration information. - -</para> - </sect3> - <sect3 arch="mips"> <title>SGI TFTP Booting</title> <para> |