From 5ed09c14644ec1ee64cf60ef65e988c4300eed50 Mon Sep 17 00:00:00 2001
From: Frans Pop <elendil@planet.nl>
Date: Mon, 2 Nov 2009 22:53:43 +0000
Subject: Remove m68k from nl translation

---
 nl/install-methods/create-floppy.xml     |  6 ------
 nl/install-methods/download/m68k.xml     | 23 -----------------------
 nl/install-methods/downloading-files.xml |  1 -
 nl/install-methods/floppy/m68k.xml       | 27 ---------------------------
 nl/install-methods/install-tftp.xml      | 21 ---------------------
 5 files changed, 78 deletions(-)
 delete mode 100644 nl/install-methods/download/m68k.xml
 delete mode 100644 nl/install-methods/floppy/m68k.xml

(limited to 'nl/install-methods')

diff --git a/nl/install-methods/create-floppy.xml b/nl/install-methods/create-floppy.xml
index a14602dac..714c1268b 100644
--- a/nl/install-methods/create-floppy.xml
+++ b/nl/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/nl/install-methods/download/m68k.xml b/nl/install-methods/download/m68k.xml
deleted file mode 100644
index 409e6a459..000000000
--- a/nl/install-methods/download/m68k.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 28672 untranslated -->
-
-
-   <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/nl/install-methods/downloading-files.xml b/nl/install-methods/downloading-files.xml
index 0b39acc7d..e9b8586e6 100644
--- a/nl/install-methods/downloading-files.xml
+++ b/nl/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/nl/install-methods/floppy/m68k.xml b/nl/install-methods/floppy/m68k.xml
deleted file mode 100644
index 749f39956..000000000
--- a/nl/install-methods/floppy/m68k.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 45433 untranslated -->
-
-
-  <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/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml
index 951c2aa5f..f5a182186 100644
--- a/nl/install-methods/install-tftp.xml
+++ b/nl/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.
@@ -274,24 +271,6 @@ by adding it to the end of the OpenPROM boot command, such as
 <userinput>boot net my-sparc.image</userinput>. This must still reside
 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>
 
-- 
cgit v1.2.3