| 1 |
toff |
3275 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
barbier |
4435 |
<!-- $Id: create-floppy.xml,v 1.6 2003/09/30 21:50:09 barbier Exp $ -->
|
| 3 |
toff |
3275 |
|
| 4 |
toff |
4119 |
<sect1 condition="supports-floppy-boot" id="create-floppy">
|
| 5 |
toff |
3275 |
<title>Creating Floppies from Disk Images</title>
|
| 6 |
|
|
<para>
|
| 7 |
|
|
|
| 8 |
|
|
Bootable floppy disks are commonly used to boot the installer system
|
| 9 |
|
|
for machines with a floppy drive. Floppies can also be used for
|
| 10 |
|
|
installation of the kernel and modules on most systems.
|
| 11 |
|
|
|
| 12 |
toff |
4099 |
</para><para arch="powerpc">
|
| 13 |
toff |
3275 |
|
| 14 |
toff |
4099 |
Floppy disk booting reportedly fails on Mac USB floppy drives.
|
| 15 |
toff |
3275 |
|
| 16 |
toff |
4099 |
</para><para arch="m68k">
|
| 17 |
|
|
|
| 18 |
|
|
Floppy disk booting is not supported on Amigas or
|
| 19 |
|
|
68k Macs.
|
| 20 |
|
|
|
| 21 |
toff |
3275 |
</para><para>
|
| 22 |
|
|
|
| 23 |
|
|
Disk images are files containing the complete contents of a floppy
|
| 24 |
|
|
disk in <emphasis>raw</emphasis> form. Disk images, such as
|
| 25 |
|
|
<filename>rescue.bin</filename>, cannot simply be copied to floppy
|
| 26 |
|
|
drives. A special program is used to write the image files to floppy
|
| 27 |
|
|
disk in <emphasis>raw</emphasis> mode. This is required because these
|
| 28 |
|
|
images are raw representations of the disk; it is required to do a
|
| 29 |
|
|
<emphasis>sector copy</emphasis> of the data from the file onto the
|
| 30 |
|
|
floppy.
|
| 31 |
|
|
|
| 32 |
|
|
</para><para>
|
| 33 |
|
|
|
| 34 |
|
|
There are different techniques for creating floppies from disk images,
|
| 35 |
|
|
which depend on your platform. This section describes how to create
|
| 36 |
|
|
floppies from disk images on different platforms.
|
| 37 |
|
|
|
| 38 |
|
|
</para><para>
|
| 39 |
|
|
|
| 40 |
|
|
No matter which method you use to create your floppies, you should
|
| 41 |
|
|
remember to flip the tab on the floppies once you have written them,
|
| 42 |
|
|
to ensure they are not damaged unintentionally.
|
| 43 |
|
|
|
| 44 |
|
|
</para>
|
| 45 |
|
|
|
| 46 |
|
|
<sect2><title>Writing Disk Images From a Linux or Unix System</title>
|
| 47 |
|
|
<para>
|
| 48 |
|
|
|
| 49 |
|
|
To write the floppy disk image files to the floppy disks, you will
|
| 50 |
|
|
probably need root access to the system. Place a good, blank floppy
|
| 51 |
|
|
in the floppy drive. Next, use the command
|
| 52 |
|
|
|
| 53 |
|
|
<informalexample><screen>
|
| 54 |
|
|
dd if=<replaceable>file</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync
|
| 55 |
|
|
</screen></informalexample>
|
| 56 |
|
|
|
| 57 |
|
|
where <replaceable>file</replaceable> is one of the floppy disk image
|
| 58 |
barbier |
4435 |
files (see <xref linkend="downloading-files"/> for what
|
| 59 |
toff |
3275 |
<replaceable>file</replaceable> should be).
|
| 60 |
|
|
<filename>/dev/fd0</filename> is a commonly used name of the floppy
|
| 61 |
|
|
disk device, it may be different on your workstation (on Solaris, it
|
| 62 |
|
|
is <filename>/dev/fd/0</filename>). The command may return to the
|
| 63 |
|
|
prompt before Unix has finished writing the floppy disk, so look for
|
| 64 |
|
|
the disk-in-use light on the floppy drive and be sure that the light
|
| 65 |
|
|
is out and the disk has stopped revolving before you remove it from
|
| 66 |
|
|
the drive. On some systems, you'll have to run a command to eject the
|
| 67 |
|
|
floppy from the drive (on Solaris, use <command>eject</command>, see
|
| 68 |
|
|
the manual page).
|
| 69 |
|
|
|
| 70 |
|
|
</para><para>
|
| 71 |
|
|
|
| 72 |
|
|
Some systems attempt to automatically mount a floppy disk when you
|
| 73 |
|
|
place it in the drive. You might have to disable this feature before
|
| 74 |
|
|
the workstation will allow you to write a floppy in <emphasis>raw
|
| 75 |
|
|
mode</emphasis>. Unfortunately, how to accomplish this will vary
|
| 76 |
|
|
based on your operating system. On Solaris, you can work around
|
| 77 |
|
|
volume management to get raw access to the floppy. First, make sure
|
| 78 |
|
|
that the floppy is auto-mounted (using <command>volcheck</command> or
|
| 79 |
|
|
the equivalent command in the file manager). Then use a
|
| 80 |
|
|
<command>dd</command> command of the form given above, just replace
|
| 81 |
|
|
<filename>/dev/fd0</filename> with
|
| 82 |
|
|
<filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>,
|
| 83 |
|
|
where <replaceable>floppy_name</replaceable> is the name the floppy
|
| 84 |
|
|
disk was given when it was formatted (unnamed floppies default to the
|
| 85 |
|
|
name <filename>unnamed_floppy</filename>). On other systems, ask your
|
| 86 |
|
|
system administrator.
|
| 87 |
|
|
|
| 88 |
toff |
4099 |
</para><para arch="powerpc">
|
| 89 |
toff |
3275 |
|
| 90 |
|
|
If writing a floppy on powerpc Linux, you will need to eject it. The
|
| 91 |
|
|
<command>eject</command> program handles this nicely; you might need
|
| 92 |
|
|
to install it.
|
| 93 |
|
|
|
| 94 |
|
|
</para>
|
| 95 |
toff |
4099 |
|
| 96 |
toff |
3275 |
</sect2>
|
| 97 |
|
|
|
| 98 |
toff |
3320 |
&floppy-i386.xml; <!-- can be used for other arches -->
|
| 99 |
toff |
4099 |
&floppy-m68k.xml;
|
| 100 |
|
|
&floppy-powerpc.xml;
|
| 101 |
toff |
3275 |
|
| 102 |
|
|
</sect1>
|
| 103 |
|
|
|
Parent Directory
| 
Revision Log