| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- $Id: boot-drive-files.xml -->
|
| 3 |
|
| 4 |
<sect1 id="boot-drive-files">
|
| 5 |
<title>Preparing Files for Hard Disk Booting</title>
|
| 6 |
<para>
|
| 7 |
|
| 8 |
The installer may be booted using boot files placed on an
|
| 9 |
existing hard drive partition, either launched from another operating
|
| 10 |
system or by invoking a boot loader directly from the BIOS.
|
| 11 |
|
| 12 |
</para><para>
|
| 13 |
|
| 14 |
A full, "pure network" installation can be achieved using this
|
| 15 |
technique. This avoids all hassles of removable media, like finding
|
| 16 |
and burning CD images or struggling with too numerous and
|
| 17 |
<xref linkend="unreliable-floppies"></xref> unreliable floppy disks.
|
| 18 |
|
| 19 |
</para>
|
| 20 |
|
| 21 |
<![ %i386; [
|
| 22 |
<para>
|
| 23 |
|
| 24 |
The installer cannot boot from files on an NTFS file system.
|
| 25 |
|
| 26 |
</para>
|
| 27 |
|
| 28 |
<![ %powerpc; [
|
| 29 |
<para>
|
| 30 |
|
| 31 |
The installer cannot boot from files on an HFS+ file system. MacOS
|
| 32 |
System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all
|
| 33 |
use HFS+. To determine whether your existing file system is HFS+,
|
| 34 |
select <userinput>Get Info</userinput> for the volume in question. HFS
|
| 35 |
file systems appear as <userinput>Mac OS Standard</userinput>, while
|
| 36 |
HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must
|
| 37 |
have an HFS partition in order to exchange files between MacOS and
|
| 38 |
Linux, in particular the installation files you download.
|
| 39 |
|
| 40 |
</para><para>
|
| 41 |
|
| 42 |
Different programs are used for hard disk installation system booting,
|
| 43 |
depending on whether the system is a ``NewWorld'' or an ``OldWorld''
|
| 44 |
model.
|
| 45 |
|
| 46 |
</para>
|
| 47 |
]]>
|
| 48 |
|
| 49 |
|
| 50 |
<sect2 id="files-lilo">
|
| 51 |
<title>Hard disk installer booting using <command>LILO</command></title>
|
| 52 |
<para>
|
| 53 |
|
| 54 |
This section explains how to add to or even replace an existing linux
|
| 55 |
installation using <command>LILO</command>.
|
| 56 |
|
| 57 |
</para><para>
|
| 58 |
|
| 59 |
At boot time, <command>LILO</command> supports loading in memory not
|
| 60 |
only the kernel, but also a disk image. This RAM disk can be used as
|
| 61 |
the root file-system by the kernel. Choose the flavor in
|
| 62 |
<xref linkend="kernel-choice"></xref> that best fits your taste, and you
|
| 63 |
will be (almost) done.
|
| 64 |
|
| 65 |
</para><para>
|
| 66 |
|
| 67 |
Copy the following two or three files from the Debian archives in a
|
| 68 |
convenient location on your hard drive, for instance in
|
| 69 |
<filename>/boot/newinstall/</filename>.
|
| 70 |
|
| 71 |
<itemizedlist>
|
| 72 |
<listitem><para>
|
| 73 |
|
| 74 |
<filename>linux.bin (kernel binary)</filename>
|
| 75 |
|
| 76 |
</para></listitem>
|
| 77 |
<listitem><para>
|
| 78 |
|
| 79 |
<filename>root.bin</filename> (root image)
|
| 80 |
|
| 81 |
</para></listitem>
|
| 82 |
<listitem><para>
|
| 83 |
|
| 84 |
<filename>drivers.tgz</filename> (optional kernel modules)
|
| 85 |
|
| 86 |
</para></listitem>
|
| 87 |
</itemizedlist>
|
| 88 |
|
| 89 |
Extract recursively everything <emphasis>now</emphasis> (easier than
|
| 90 |
later). Remember on which physical partition
|
| 91 |
(e.g. <filename>/dev/hda4</filename>) are the <filename>.o</filename>
|
| 92 |
drivers you just extracted from <filename>drivers.tgz</filename>.
|
| 93 |
|
| 94 |
</para><para>
|
| 95 |
|
| 96 |
You can also replace <filename>linux.bin</filename> and
|
| 97 |
<filename>drivers.tgz</filename> by your custom kernel and the
|
| 98 |
carefully chosen drivers that you will need for the installation, for
|
| 99 |
instance a module for your exotic and unsupported network interface.
|
| 100 |
Do not forget that your custom kernel must have (at least) the
|
| 101 |
<filename>RAMDISK</filename> and <filename>initrd</filename> features
|
| 102 |
<emphasis>built-in</emphasis>. See the very beginning of
|
| 103 |
<xref linkend="rescue-replace-kernel"></xref> for the list of the other
|
| 104 |
mandatory built-in kernel features required to boot and launch the
|
| 105 |
installer. The floppy-related stuff after the list of features is
|
| 106 |
irrelevant to you.
|
| 107 |
|
| 108 |
</para><para>
|
| 109 |
|
| 110 |
Finally, to configure <command>LILO</command> proceed to
|
| 111 |
<xref linkend="boot-initrd"></xref>.
|
| 112 |
|
| 113 |
</para>
|
| 114 |
|
| 115 |
</sect2>
|
| 116 |
<!-- end %i386; --> ]]>
|
| 117 |
|
| 118 |
<![ %powerpc [
|
| 119 |
<sect2 id="files-oldworld">
|
| 120 |
<title>Hard Disk Installer Booting for OldWorld Macs</title>
|
| 121 |
<para>
|
| 122 |
|
| 123 |
The <filename>boot-floppy-hfs</filename> floppy uses
|
| 124 |
<application>miBoot</application> to launch Linux installation, but
|
| 125 |
<application>miBoot</application> cannot easily be used for hard disk
|
| 126 |
booting. <application>BootX</application>, launched from MacOS,
|
| 127 |
supports booting from files placed on the hard
|
| 128 |
disk. <application>BootX</application> can also be used to dual-boot
|
| 129 |
MacOS and Linux after your Debian installation is complete. For the
|
| 130 |
Performa 6360, it appears that <command>quik</command> cannot make the
|
| 131 |
hard disk bootable. So <application>BootX</application> is required
|
| 132 |
on that model.
|
| 133 |
|
| 134 |
</para><para>
|
| 135 |
|
| 136 |
Download and unstuff the <application>BootX</application>
|
| 137 |
distribution, available from <ulink url="&url-powerpc-bootx;"></ulink>,
|
| 138 |
or in the
|
| 139 |
<filename>dists/woody/main/disks-powerpc/current/powermac</filename>
|
| 140 |
directory on Debian http/ftp mirrors and official Debian CDs. Use
|
| 141 |
<application>Stuffit Expander</application> to extract it from its
|
| 142 |
archive. Within the package, there is an empty folder called
|
| 143 |
<filename>Linux Kernels</filename>. Download
|
| 144 |
<filename>linux.bin</filename> and
|
| 145 |
<filename>ramdisk.image.gz</filename> from the
|
| 146 |
<filename>disks-powerpc/current/powermac</filename> folder, and place
|
| 147 |
them in the <filename>Linux Kernels</filename> folder. Then place the
|
| 148 |
<filename>Linux Kernels</filename> folder in the active System Folder.
|
| 149 |
|
| 150 |
</para>
|
| 151 |
</sect2>
|
| 152 |
|
| 153 |
<sect2 id="files-newworld">
|
| 154 |
<title>Hard Disk Installer Booting for NewWorld Macs</title>
|
| 155 |
<para>
|
| 156 |
|
| 157 |
NewWorld PowerMacs support booting from a network or an ISO9660
|
| 158 |
CD-ROM, as well as loading ELF binaries directly from the hard
|
| 159 |
disk. These machines will boot Linux directly via
|
| 160 |
<command>yaboot</command>, which supports loading a kernel and RAMdisk
|
| 161 |
directly from an ext2 partition, as well as dual-booting with
|
| 162 |
MacOS. Hard disk booting of the installer is particularly appropriate
|
| 163 |
for newer machines without floppy drives. <command>BootX</command> is
|
| 164 |
not supported and must not be used on NewWorld PowerMacs.
|
| 165 |
|
| 166 |
</para><para>
|
| 167 |
|
| 168 |
<emphasis>Copy</emphasis> (not move) the following four files which
|
| 169 |
you downloaded earlier from the Debian archives, onto the root level
|
| 170 |
of your hard drive (this can be accomplished by option-dragging each
|
| 171 |
file to the hard drive icon).
|
| 172 |
|
| 173 |
<itemizedlist>
|
| 174 |
<listitem><para>
|
| 175 |
|
| 176 |
<filename>linux.bin</filename>
|
| 177 |
|
| 178 |
</para></listitem>
|
| 179 |
<listitem><para>
|
| 180 |
|
| 181 |
<filename>root.bin</filename> (from inside the images-1.44 folder)
|
| 182 |
|
| 183 |
</para></listitem>
|
| 184 |
<listitem><para>
|
| 185 |
|
| 186 |
<filename>yaboot</filename>
|
| 187 |
|
| 188 |
</para></listitem>
|
| 189 |
<listitem><para>
|
| 190 |
|
| 191 |
<filename>yaboot.conf</filename>
|
| 192 |
|
| 193 |
</para></listitem>
|
| 194 |
</itemizedlist>
|
| 195 |
|
| 196 |
</para><para>
|
| 197 |
|
| 198 |
Make a note of the partition number of the MacOS partition where you
|
| 199 |
place these files. If you have the MacOS <command>pdisk</command>
|
| 200 |
program, you can use the L command to check for the partition
|
| 201 |
number. You will need this partition number for the command you type
|
| 202 |
at the Open Firmware prompt when you boot the installer.
|
| 203 |
|
| 204 |
</para><para>
|
| 205 |
|
| 206 |
To boot the installer, proceed to <xref linkend="boot-newworld"></xref>.
|
| 207 |
|
| 208 |
</para>
|
| 209 |
</sect2>
|
| 210 |
<!-- end %powerpc; --> ]]>
|
| 211 |
|
| 212 |
</sect1>
|
Parent Directory
| 
Revision Log