Remove mentions of floppy

7 files changed, 4 insertions, 273 deletions

diff --git a/en/install-methods/boot-drive-files.xml b/en/install-methods/boot-drive-files.xml
index 8c5cd16e0..820dd659c 100644
--- a/en/install-methods/boot-drive-files.xml
+++ b/en/install-methods/boot-drive-files.xml
@@ -13,8 +13,7 @@ system or by invoking a boot loader directly from the BIOS.
 
 A full, <quote>pure network</quote> installation can be achieved using this
 technique. This avoids all hassles of removable media, like finding
-and burning CD images or struggling with too numerous and
-unreliable floppy disks.
+and burning CD images.
 
 </para><para arch="powerpc">
 
@@ -108,6 +107,7 @@ Copy the following directories from a &debian; CD image to <filename>c:\</filena
   </sect2>
 
 
+<!--
   <sect2 arch="powerpc" id="files-oldworld">
   <title>Hard Disk Installer Booting for OldWorld Macs</title>
 <para>
@@ -199,4 +199,5 @@ To boot the installer, proceed to <xref linkend="boot-newworld"/>.
 
 </para>
   </sect2>
+-->
  </sect1>
diff --git a/en/install-methods/create-floppy.xml b/en/install-methods/create-floppy.xml
deleted file mode 100644
index 2610c834f..000000000
--- a/en/install-methods/create-floppy.xml
+++ /dev/null
@@ -1,108 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
- <sect1 condition="supports-floppy-boot" id="create-floppy">
- <title>Creating Floppies from Disk Images</title>
-<para>
-
-Bootable floppy disks are generally used as a last resort to boot the
-installer on hardware that cannot boot from CD or by other means.
-
-</para><para arch="powerpc">
-
-Booting the installer from floppy disk reportedly fails on Mac USB
-floppy drives.
-
-</para><para>
-
-Disk images are files containing the complete contents of a floppy
-disk in <emphasis>raw</emphasis> form.  Disk images, such as
-<filename>boot.img</filename>, cannot simply be copied to floppy
-drives.  A special program is used to write the image files to floppy
-disk in <emphasis>raw</emphasis> mode.  This is required because these
-images are raw representations of the disk; it is required to do a
-<emphasis>sector copy</emphasis> of the data from the file onto the
-floppy.
-
-</para><para>
-
-There are different techniques for creating floppies from disk images.
-This section describes how to create floppies from disk images on
-different platforms.
-
-</para><para>
-
-Before you can create the floppies, you will first need to download them
-from one of the &debian; mirrors, as explained in
-<xref linkend="downloading-files"/>. <phrase arch="i386">If you already
-have an installation CD-ROM or DVD, the floppy images may also be included
-on the CD/DVD.</phrase>
-
-</para><para>
-
-No matter which method you use to create your floppies, you should
-remember to flip the write-protect tab on the floppies once you have
-written them, to ensure they are not damaged unintentionally.
-
-</para>
-
-  <sect2><title>Writing Disk Images From a Linux or Unix System</title>
-<para>
-
-To write the floppy disk image files to the floppy disks, you will
-probably need root access to the system.  Place a good, blank floppy
-in the floppy drive.  Next, use the command
-
-<informalexample><screen>
-$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync
-</screen></informalexample>
-
-where <replaceable>filename</replaceable> is one of the floppy disk image
-files.
-<filename>/dev/fd0</filename> is a commonly used name of the floppy
-disk device, it may be different on your workstation<phrase arch="sparc">
-(on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>.
-The command may return to the
-prompt before Unix has finished writing the floppy disk, so look for
-the disk-in-use light on the floppy drive and be sure that the light
-is out and the disk has stopped revolving before you remove it from
-the drive. On some systems, you'll have to run a command to eject the
-floppy from the drive <phrase arch="sparc"> (on Solaris, use
-<command>eject</command>, see the manual page)</phrase>.
-
-</para><para>
-
-Some systems attempt to automatically mount a floppy disk when you
-place it in the drive. You might have to disable this feature before
-the workstation will allow you to write a floppy in <emphasis>raw
-mode</emphasis>.  Unfortunately, how to accomplish this will vary
-based on your operating system.
-<phrase arch="sparc">
-On Solaris, you can work around
-volume management to get raw access to the floppy.  First, make sure
-that the floppy is auto-mounted (using <command>volcheck</command> or
-the equivalent command in the file manager). Then use a
-<command>dd</command> command of the form given above, just replace
-<filename>/dev/fd0</filename> with
-<filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>,
-where <replaceable>floppy_name</replaceable> is the name the floppy
-disk was given when it was formatted (unnamed floppies default to the
-name <filename>unnamed_floppy</filename>).  On other systems, ask your
-system administrator.
-</phrase>
-
-</para><para arch="powerpc">
-
-If writing a floppy on powerpc Linux, you will need to eject it. The
-<command>eject</command> program handles this nicely; you might need
-to install it.
-
-</para>
-
-  </sect2>
-
-&floppy-i386.xml; <!-- can be used for other arches -->
-&floppy-powerpc.xml;
-
- </sect1>
-
diff --git a/en/install-methods/floppy/i386.xml b/en/install-methods/floppy/i386.xml
deleted file mode 100644
index 158057aa4..000000000
--- a/en/install-methods/floppy/i386.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-
-<!--  This is not set off for i386 only, because many people will have -->
-<!--  access to a PC in order to make a floppy for other arches. -->
-
-  <sect2><title>Writing Disk Images From DOS, Windows, or OS/2</title>
-
-<para>
-
-If you have access to an i386 or amd64 machine, you can use one of the
-following programs to copy images to floppies.
-
-</para><para>
-
-The <command>rawrite1</command> and <command>rawrite2</command> programs
-can be used under MS-DOS. To use these programs, first make sure that you
-are booted into DOS. Trying to use these programs from within a DOS box in
-Windows, or double-clicking on these programs from the Windows Explorer is
-<emphasis>not</emphasis> expected to work.
-
-</para><para>
-
-The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000,
-ME, XP and probably later versions. To use it you will need to unpack
-diskio.dll in the same directory.
-
-</para><para>
-
-These tools can be found on the Official &debian; CD-ROMs under the
-<filename>/tools</filename> directory.
-
-</para>
-  </sect2>
diff --git a/en/install-methods/floppy/powerpc.xml b/en/install-methods/floppy/powerpc.xml
deleted file mode 100644
index 1a29c1043..000000000
--- a/en/install-methods/floppy/powerpc.xml
+++ /dev/null
@@ -1,122 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- $Id$ -->
-
-
-  <sect2 arch="powerpc"><title>Writing Disk Images From MacOS</title>
-<para>
-
-An AppleScript, <application>Make &debian; Floppy</application>, is
-available for burning floppies from the provided disk image files. It
-can be downloaded from
-<ulink url="ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit"></ulink>. To
-use it, just unstuff it on your desktop, and then drag any floppy
-image file to it. You must have Applescript installed and enabled in
-your extensions manager. Disk Copy will ask you to confirm that you
-wish to erase the floppy and proceed to write the file image to it.
-
-</para><para>
-
-You can also use the MacOS utility <command>Disk Copy</command>
-directly, or the freeware utility <command>suntar</command>. The
-<filename>root.bin</filename> file is an example of a floppy
-image. Use one of the following methods to create a floppy from the
-floppy image with these utilities.
-
-</para>
-
-   <sect3>
-   <title>Writing Disk Images with <command>Disk Copy</command></title>
-<para>
-
-If you are creating the floppy image from files which were originally
-on the official &debian-gnu; CD, then the Type and Creator are already set
-correctly. The following <command>Creator-Changer</command> steps are
-only necessary if you downloaded the image files from a &debian; mirror.
-
-</para>
-<orderedlist>
-<listitem><para>
-
-Obtain
-<ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink>
-and use it to open the <filename>root.bin</filename> file.
-
-</para></listitem>
-<listitem><para>
-
-Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the
-Type to <userinput>DDim</userinput> (binary floppy image). The case is
-sensitive for these fields.
-
-</para></listitem>
-<listitem><para>
-
-<emphasis>Important:</emphasis> In the Finder, use <userinput>Get
-Info</userinput> to display the Finder information about the floppy
-image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so
-that MacOS will be unable to remove the boot blocks if the image is
-accidentally mounted.
-
-</para></listitem>
-    <listitem><para>
-
-Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it
-will very likely be there already, otherwise try
-<ulink url="&url-powerpc-diskcopy;"></ulink>.
-
-</para></listitem>
-<listitem><para>
-
-Run <command>Disk Copy</command>, and select <menuchoice>
-<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem>
-</menuchoice>, then select the
-<emphasis>locked</emphasis> image file from the resulting dialog. It
-will ask you to insert a floppy, then ask if you really want to erase
-it. When done it should eject the floppy.
-
-</para></listitem>
-</orderedlist>
-
-   </sect3>
-
-   <sect3>
-   <title>Writing Disk Images with <command>suntar</command></title>
-<para>
-
-<orderedlist>
-<listitem><para>
-
-Obtain <command>suntar</command> from <ulink url="&url-powerpc-suntar;">
-</ulink>. Start the <command>suntar</command> program and select
-<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput>
-menu.
-
-</para></listitem>
-<listitem><para>
-
-Insert the floppy disk as requested, then hit &enterkey; (start at
-sector 0).
-
-</para></listitem>
-<listitem><para>
-
-Select the <filename>root.bin</filename> file in the file-opening dialog.
-
-</para></listitem>
-<listitem><para>
-
-After the floppy has been created successfully, select <menuchoice>
-<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>.
-If there are any errors writing the floppy, simply toss that floppy and
-try another.
-
-</para></listitem>
-</orderedlist>
-
-Before using the floppy you created, <emphasis>set the write protect
-tab</emphasis>!  Otherwise if you accidentally mount it in MacOS,
-MacOS will helpfully ruin it.
-
-</para>
-   </sect3>
-  </sect2>
diff --git a/en/install-methods/install-methods.xml b/en/install-methods/install-methods.xml
index 3042e1190..5b4710eac 100644
--- a/en/install-methods/install-methods.xml
+++ b/en/install-methods/install-methods.xml
@@ -6,7 +6,6 @@
 
 &official-cdrom.xml;
 &downloading-files.xml;
-&create-floppy.xml;
 &boot-usb-files.xml;
 &boot-drive-files.xml;
 &install-tftp.xml;
diff --git a/en/install-methods/official-cdrom.xml b/en/install-methods/official-cdrom.xml
index ec3b76cf8..4d9414823 100644
--- a/en/install-methods/official-cdrom.xml
+++ b/en/install-methods/official-cdrom.xml
@@ -42,8 +42,6 @@ If your machine doesn't support CD booting<phrase arch="x86"> (only relevant
 on very old PC systems)</phrase>, but you do have a CD set,
 you can use an alternative strategy such as
 
-<phrase condition="supports-floppy-boot">floppy disk,</phrase>
-
 <phrase arch="s390">VM reader,</phrase>
 
 <phrase condition="bootable-disk">hard disk,</phrase>
@@ -71,8 +69,6 @@ installer system files and place them on the
 
 <phrase arch="s390">VM minidisk</phrase>
 
-<phrase condition="supports-floppy-boot">floppy disk or</phrase>
-
 <phrase condition="bootable-disk">hard disk or</phrase>
 
 <phrase condition="bootable-usb">usb stick or</phrase>
diff --git a/en/install-methods/tftp/rarp.xml b/en/install-methods/tftp/rarp.xml
index ae539c6f3..289d3a5c0 100644
--- a/en/install-methods/tftp/rarp.xml
+++ b/en/install-methods/tftp/rarp.xml
@@ -12,7 +12,7 @@ If you don't know this information, you can
 <phrase arch="sparc"> pick it off the initial OpenPROM boot messages, use the
 OpenBoot <userinput>.enet-addr</userinput> command, or </phrase>
 
-boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the
+boot into <quote>Rescue</quote> mode and use the
 command <userinput>ip addr show dev eth0</userinput>.
 
 </para><para>