1
<!-- retain these comments for translator revision tracking -->
2
<!-- original version: 11648 untranslated -->
4
<sect1 condition="bootable-disk" id="boot-drive-files">
5
<title>Preparing Files for Hard Disk Booting</title>
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.
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"/> unreliable floppy disks.
19
</para><para arch="x86">
21
The installer cannot boot from files on an NTFS file system.
23
</para><para arch="powerpc">
25
The installer cannot boot from files on an HFS+ file system. MacOS
26
System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all
27
use HFS+. To determine whether your existing file system is HFS+,
28
select <userinput>Get Info</userinput> for the volume in question. HFS
29
file systems appear as <userinput>Mac OS Standard</userinput>, while
30
HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must
31
have an HFS partition in order to exchange files between MacOS and
32
Linux, in particular the installation files you download.
34
</para><para arch="powerpc">
36
Different programs are used for hard disk installation system booting,
37
depending on whether the system is a ``NewWorld'' or an ``OldWorld''
42
<sect2 arch="x86" id="files-lilo">
43
<title>Hard disk installer booting using <command>LILO</command> or
44
<command>GRUB</command></title>
47
This section explains how to add to or even replace an existing linux
48
installation using either <command>LILO</command> or
49
<command>GRUB</command>.
53
At boot time, both bootloaders support loading in memory not
54
only the kernel, but also a disk image. This RAM disk can be used as
55
the root file-system by the kernel. Choose the flavor in
56
<xref linkend="kernel-choice"/> that best fits your taste, and you
57
will be (almost) done.
61
Copy the following two or three files from the Debian archives in a
62
convenient location on your hard drive, for instance in
63
<filename>/boot/newinstall/</filename>.
68
<filename>vmlinuz</filename> (kernel binary)
73
<filename>initrd.gz</filename> (ramdisk image)
78
<filename>drivers.tgz</filename> (optional kernel modules)
83
Extract recursively everything <emphasis>now</emphasis> (easier than
84
later). Remember on which physical partition
85
(e.g. <filename>/dev/hda4</filename>) are the <filename>.o</filename>
86
drivers you just extracted from <filename>drivers.tgz</filename>.
90
You can also replace <filename>vmlinuz</filename> and
91
<filename>drivers.tgz</filename> by your custom kernel and the
92
carefully chosen drivers that you will need for the installation, for
93
instance a module for your exotic and unsupported network interface.
94
Do not forget that your custom kernel must have (at least) the
95
<filename>RAMDISK</filename> and <filename>initrd</filename> features
96
<emphasis>built-in</emphasis>. See the very beginning of
97
<xref linkend="rescue-replace-kernel"/> for the list of the other
98
mandatory built-in kernel features required to boot and launch the
99
installer. The floppy-related stuff after the list of features is
104
Finally, to configure the bootloader proceed to
105
<xref linkend="boot-initrd"/>.
111
<sect2 arch="powerpc" id="files-oldworld">
112
<title>Hard Disk Installer Booting for OldWorld Macs</title>
115
The <filename>boot-floppy-hfs</filename> floppy uses
116
<application>miBoot</application> to launch Linux installation, but
117
<application>miBoot</application> cannot easily be used for hard disk
118
booting. <application>BootX</application>, launched from MacOS,
119
supports booting from files placed on the hard
120
disk. <application>BootX</application> can also be used to dual-boot
121
MacOS and Linux after your Debian installation is complete. For the
122
Performa 6360, it appears that <command>quik</command> cannot make the
123
hard disk bootable. So <application>BootX</application> is required
128
Download and unstuff the <application>BootX</application>
129
distribution, available from <ulink url="&url-powerpc-bootx;"></ulink>,
131
<filename>dists/woody/main/disks-powerpc/current/powermac</filename>
132
directory on Debian http/ftp mirrors and official Debian CDs. Use
133
<application>Stuffit Expander</application> to extract it from its
134
archive. Within the package, there is an empty folder called
135
<filename>Linux Kernels</filename>. Download
136
<filename>linux.bin</filename> and
137
<filename>ramdisk.image.gz</filename> from the
138
<filename>disks-powerpc/current/powermac</filename> folder, and place
139
them in the <filename>Linux Kernels</filename> folder. Then place the
140
<filename>Linux Kernels</filename> folder in the active System Folder.
145
<sect2 arch="powerpc" id="files-newworld">
146
<title>Hard Disk Installer Booting for NewWorld Macs</title>
149
NewWorld PowerMacs support booting from a network or an ISO9660
150
CD-ROM, as well as loading ELF binaries directly from the hard
151
disk. These machines will boot Linux directly via
152
<command>yaboot</command>, which supports loading a kernel and RAMdisk
153
directly from an ext2 partition, as well as dual-booting with
154
MacOS. Hard disk booting of the installer is particularly appropriate
155
for newer machines without floppy drives. <command>BootX</command> is
156
not supported and must not be used on NewWorld PowerMacs.
160
<emphasis>Copy</emphasis> (not move) the following four files which
161
you downloaded earlier from the Debian archives, onto the root level
162
of your hard drive (this can be accomplished by
163
<keycap>option</keycap>-dragging each file to the hard drive icon).
168
<filename>linux.bin</filename>
173
<filename>root.bin</filename> (from inside the images-1.44 folder)
178
<filename>yaboot</filename>
183
<filename>yaboot.conf</filename>
190
Make a note of the partition number of the MacOS partition where you
191
place these files. If you have the MacOS <command>pdisk</command>
192
program, you can use the L command to check for the partition
193
number. You will need this partition number for the command you type
194
at the Open Firmware prompt when you boot the installer.
198
To boot the installer, proceed to <xref linkend="boot-newworld"/>.