From 2912ce3db07a16813d77cb3dc8da12e5142c3898 Mon Sep 17 00:00:00 2001 From: Holger Wansing Date: Thu, 29 Aug 2019 16:36:18 +0200 Subject: Remove mentions of floppy --- en/install-methods/boot-drive-files.xml | 5 +- en/install-methods/create-floppy.xml | 108 ---------------------------- en/install-methods/floppy/i386.xml | 35 --------- en/install-methods/floppy/powerpc.xml | 122 -------------------------------- en/install-methods/install-methods.xml | 1 - en/install-methods/official-cdrom.xml | 4 -- en/install-methods/tftp/rarp.xml | 2 +- 7 files changed, 4 insertions(+), 273 deletions(-) delete mode 100644 en/install-methods/create-floppy.xml delete mode 100644 en/install-methods/floppy/i386.xml delete mode 100644 en/install-methods/floppy/powerpc.xml (limited to 'en/install-methods') 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, pure network 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. @@ -108,6 +107,7 @@ Copy the following directories from a &debian; CD image to c:\ + 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 @@ - - - - - Creating Floppies from Disk Images - - -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. - - - -Booting the installer from floppy disk reportedly fails on Mac USB -floppy drives. - - - -Disk images are files containing the complete contents of a floppy -disk in raw form. Disk images, such as -boot.img, cannot simply be copied to floppy -drives. A special program is used to write the image files to floppy -disk in raw mode. This is required because these -images are raw representations of the disk; it is required to do a -sector copy of the data from the file onto the -floppy. - - - -There are different techniques for creating floppies from disk images. -This section describes how to create floppies from disk images on -different platforms. - - - -Before you can create the floppies, you will first need to download them -from one of the &debian; mirrors, as explained in -. If you already -have an installation CD-ROM or DVD, the floppy images may also be included -on the CD/DVD. - - - -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. - - - - Writing Disk Images From a Linux or Unix System - - -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 - - -$ dd if=filename of=/dev/fd0 bs=1024 conv=sync ; sync - - -where filename is one of the floppy disk image -files. -/dev/fd0 is a commonly used name of the floppy -disk device, it may be different on your workstation -(on Solaris, it is /dev/fd/0). -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 (on Solaris, use -eject, see the manual page). - - - -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 raw -mode. Unfortunately, how to accomplish this will vary -based on your operating system. - -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 volcheck or -the equivalent command in the file manager). Then use a -dd command of the form given above, just replace -/dev/fd0 with -/vol/rdsk/floppy_name, -where floppy_name is the name the floppy -disk was given when it was formatted (unnamed floppies default to the -name unnamed_floppy). On other systems, ask your -system administrator. - - - - -If writing a floppy on powerpc Linux, you will need to eject it. The -eject program handles this nicely; you might need -to install it. - - - - - -&floppy-i386.xml; -&floppy-powerpc.xml; - - - 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 @@ - - - - - - - - Writing Disk Images From DOS, Windows, or OS/2 - - - -If you have access to an i386 or amd64 machine, you can use one of the -following programs to copy images to floppies. - - - -The rawrite1 and rawrite2 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 -not expected to work. - - - -The rwwrtwin 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. - - - -These tools can be found on the Official &debian; CD-ROMs under the -/tools directory. - - - 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 @@ - - - - - Writing Disk Images From MacOS - - -An AppleScript, Make &debian; Floppy, is -available for burning floppies from the provided disk image files. It -can be downloaded from -. 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. - - - -You can also use the MacOS utility Disk Copy -directly, or the freeware utility suntar. The -root.bin 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. - - - - - Writing Disk Images with <command>Disk Copy</command> - - -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 Creator-Changer steps are -only necessary if you downloaded the image files from a &debian; mirror. - - - - - -Obtain -Creator-Changer -and use it to open the root.bin file. - - - - -Change the Creator to ddsk (Disk Copy), and the -Type to DDim (binary floppy image). The case is -sensitive for these fields. - - - - -Important: In the Finder, use Get -Info to display the Finder information about the floppy -image, and X the File Locked check box so -that MacOS will be unable to remove the boot blocks if the image is -accidentally mounted. - - - - -Obtain Disk Copy; if you have a MacOS system or CD it -will very likely be there already, otherwise try -. - - - - -Run Disk Copy, and select -Utilities Make a Floppy -, then select the -locked 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. - - - - - - - - Writing Disk Images with <command>suntar</command> - - - - - -Obtain suntar from -. Start the suntar program and select -Overwrite Sectors... from the Special -menu. - - - - -Insert the floppy disk as requested, then hit &enterkey; (start at -sector 0). - - - - -Select the root.bin file in the file-opening dialog. - - - - -After the floppy has been created successfully, select -File Eject . -If there are any errors writing the floppy, simply toss that floppy and -try another. - - - - -Before using the floppy you created, set the write protect -tab! Otherwise if you accidentally mount it in MacOS, -MacOS will helpfully ruin it. - - - - 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 (only relevant on very old PC systems), but you do have a CD set, you can use an alternative strategy such as -floppy disk, - VM reader, hard disk, @@ -71,8 +69,6 @@ installer system files and place them on the VM minidisk -floppy disk or - hard disk or usb stick or 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 pick it off the initial OpenPROM boot messages, use the OpenBoot .enet-addr command, or -boot into Rescue mode (e.g., from the rescue floppy) and use the +boot into Rescue mode and use the command ip addr show dev eth0. -- cgit v1.2.3