MacOS floppy creation
> Chris, if you can please send a corrected patch (as a mime attachment)
> to this list, I can apply it to the potato version.
See attached 2 files, I hope they are mime, I'm using emacs mail.
> Chris, I would prefer that this stuff just be sent as a mail to this
> list rather than as a bug report.
#-) Oops.
===File ~/urls.ent.dif======================================
Index: urls.ent
===================================================================
RCS file: /cvs/debian-boot/boot-floppies/documentation/urls.ent,v
retrieving revision 1.63.2.1
diff -u -r1.63.2.1 urls.ent
--- urls.ent 2001/05/12 20:17:36 1.63.2.1
+++ urls.ent 2001/05/25 06:32:17
@@ -424,7 +424,17 @@
<!entity url-netbsd-powerpc-faq "http://www.netbsd.org/Ports/macppc/faq.html";>
-<!entity url-powerpc-of "http://prdownloads.sourceforge.net/debian-imac/debian-imac.sit";>
+<!entity url-powerpc-of
+ "http://prdownloads.sourceforge.net/debian-imac/debian-imac.sit";>
+
+<!entity url-powerpc-suntar
+ "http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/cmp/suntar-223.hqx";>
+
+<!entity url-powerpc-resedit
+ "http://www.resexcellence.com/resedit.shtml";>
+
+<!entity url-powerpc-diskcopy
+ "http://asu.info.apple.com/swupdates.nsf/artnum/n11162";>
<!entity url-powerpc-ppcbug "no URL">
============================================================
===File ~/inst-methods.sgml.dif=============================
Index: en/inst-methods.sgml
===================================================================
RCS file: /cvs/debian-boot/boot-floppies/documentation/en/inst-methods.sgml,v
retrieving revision 1.55
diff -u -r1.55 inst-methods.sgml
--- en/inst-methods.sgml 2001/02/17 18:46:25 1.55
+++ en/inst-methods.sgml 2001/05/25 06:33:03
@@ -246,6 +246,16 @@
single file. Perform your initial boot, and then point the
installation program at the files you have downloaded when it asks for
the appropriate source.
+
+<![ %powerpc [
+ <p>
+Currently, Linux cannot access files on an HFS+
+filesystem (MacOS System 8.0 and above may use HFS+
+filesystems). To determine whether your existing filesystem is
+HFS+, select <tt>Get Info</tt> for the volume in question. HFS filesystems
+appear as <tt>Mac OS Standard</tt>, while HFS+ filesystems say
+<tt>Mac OS Extended</tt>.
+ ]]>
<p>
These are only suggestions. You should choose whatever sources are
most convenient for you. Floppies are neither convenient nor
@@ -794,27 +804,26 @@
]]>
-<![ %i386 [
-<!-- This should be revised by some native speaker -->
- <sect1 id="set-lang">
+<![ %i386 [
+ <sect1 id="set-lang">
<heading>
Modifying the &RESCUE-FLOPPY; to Support National Language
</heading>
-<p>
-You may see the messages shown by the &RESCUE-FLOPPY; (before loading
-Linux kernel) in your mother tongue. If you are not an English
-speaker, you have to copy the provided messages files and a font to
-the floppy after writing the image file, to achieve this. For MS-DOS
-and Windows users there is a batch file <file>setlang.bat</file> in
-<file>dosutils</file> directory, that does exactly this. Simply enter
-this directory (e.g. <tt>cd c:\debian\dosutils</tt>) and run
+ <p>
+The messages shown by the &RESCUE-FLOPPY; (before loading the Linux
+kernel) can be shown in your mother tongue. To achieve this if you are
+not an English speaker, after writing the image file, you must copy
+the provided message files and a font to the floppy. For MS-DOS and
+Windows users there is a batch file <file>setlang.bat</file> in the
+<file>dosutils</file> directory, which copies the correct
+files. Simply enter this directory (e.g. <tt>cd
+c:\debian\dosutils</tt>) within a command prompt window, and run
<tt>setlang <var>lang</var></tt>, where <var>lang</var> is a
two-letter code of your language in lower case, for example
-<tt>setlang pl</tt> to set the language to Polish.
-
-]]>
+<tt>setlang pl</tt> to set the language to Polish. Currently these
+language codes are available: <tt>cs de eo es fi fr hr hu it ja pl pt
+ru sk sv tr</tt> ]]>
-
<![ %m68k [
<sect2>Writing Disk Images on Atari Systems
<p>
@@ -864,6 +873,75 @@
]]>
+<![ %powerpc [
+ <sect2>Writing Disk Images From MacOS
+ <p>
+To create boot floppies from the distribution floppy images on a MacOS
+system, you can use the MacOS utility <prgn>Disk Copy</prgn> or the
+independent utility <prgn>suntar</prgn>. The <file>root.bin</file>
+file is an example of a floppy image. First, copy
+<file>root.bin</file> from the offical &debian; CD, or download it
+from your favorite Debian mirror in <em>binary</em> mode. Do not allow
+any automatic extraction of the file after downloading. The `.bin'
+extension does not stand for Macbinary, but rather just `binary'
+floppy image files. Then use one of the following methods to create a
+floppy from the floppy image.
+
+ <sect3>Writing Disk Images with <prgn>Disk Copy</prgn>
+ <p>
+ <enumlist>
+ <item>
+If you are creating the floppy image from files which were originally
+on the official &debian; CD, then the Type and Creator are already set
+correctly. These <prgn>ResEdit</prgn> steps are only necessary if you
+downloaded the image files.
+ <enumlist>
+ <item>
+Obtain <url id="&url-powerpc-resedit;" name="ResEdit">. Use it to
+open the <file>root.bin</file> file (a resource fork will be added to
+the file).
+ <item>
+Select <tt>Get Info for root.bin...</tt> under the <tt>File</tt> menu. In
+the Type field, replace whatever is there with <tt>DDim</tt>. In the Creator
+field, type <tt>ddsk</tt>. The case is sensitive for these fields.
+ <item>
+<em>Important:</em> Place a check in the <tt>File Locked</tt> checkbox
+so that MacOS will be unable to remove the boot blocks if the image is
+mounted accidentally. If the image is mounted, MacOS will helpfully
+remove the boot blocks, rendering the floppy image unusable.
+ </enumlist>
+ <item>
+Obtain <prgn>Disk Copy</prgn>; if you have a MacOS system or CD it
+will very likely be there already, otherwise try
+<url id="&url-powerpc-diskcopy;">.
+ <item>
+Run <prgn>Disk Copy</prgn>, and select `Make a Floppy' from the
+Utilities menu, then select the <em>locked</em> 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.
+ <item>
+When the floppy is ejected <em>set the write protect tab</em>!
+Otherwise if you accidently mount it in MacOS, MacOS will helpfully
+ruin it.
+ </enumlist>
+ <sect3>Writing Disk Images with <prgn>suntar</prgn>
+ <enumlist>
+ <item>
+Obtain <prgn>suntar</prgn> from <url id="&url-powerpc-suntar;">.
+ <item>
+Start the <prgn>suntar</prgn> program and select `Overwrite
+Sectors...' from the <tt>Special</tt> menu.
+ <item>
+Insert the floppy disk as requested, then hit return (start at sector
+0).
+ <item>
+Select the <file>root.bin</file> file in the file-opening dialog.
+ <item>
+After the floppy has been created successfully, select `Eject' from
+the <tt>File</tt> menu. If there are any errors writing the floppy,
+simply toss that floppy and try another.
+ </enumlist>
+ ]]>
<sect>CD-ROM
<![ %supports-bootable-cd [
============================================================
Reply to: