summaryrefslogtreecommitdiff
path: root/en/install-methods/boot-drive-files.xml
blob: 59741e5a67a89c5bbcb57568c2bd1d4794b13e62 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->

 <sect1 condition="bootable-disk" id="boot-drive-files">
 <title>Preparing Files for Hard Disk Booting</title>
<para>

The installer may be booted using boot files placed on an
existing hard drive partition, either launched from another operating
system or by invoking a boot loader directly from the BIOS.
On modern UEFI systems, the kernel may be booted directly from the UEFI
partition without the need of a boot loader.

</para><para>

A full, <quote>pure network</quote> installation can be achieved using this
technique. This avoids all hassles of removable media, like finding
and burning CD/DVD images.

</para>

<!--
<para arch="powerpc">

The installer cannot boot from files on an HFS+ file system.  MacOS
System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all
use HFS+. To determine whether your existing file system is HFS+,
select <userinput>Get Info</userinput> for the volume in question. HFS
file systems appear as <userinput>Mac OS Standard</userinput>, while
HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must
have an HFS partition in order to exchange files between MacOS and
Linux, in particular the installation files you download.

</para><para arch="powerpc">

Different programs are used for hard disk installation system booting,
depending on whether the system is a <quote>NewWorld</quote> or an
<quote>OldWorld</quote> model.

</para>
-->

  <sect2 arch="x86" id="files-grub">
  <title>Hard disk installer booting from Linux using
  <command>GRUB</command></title>
<para>

This section explains how to add to or even replace an existing linux
installation using
<command>GRUB</command>.

</para><para>

At boot time, <command>GRUB</command> supports loading in memory not
only the kernel, but also a disk image. This RAM disk can be used as
the root file-system by the kernel.

</para><para>

Copy the following files from the &debian; archives to a
convenient location on your hard drive, for instance to
<filename>/boot/newinstall/</filename>.

<itemizedlist>
<listitem><para>

<filename>vmlinuz</filename> (kernel binary)

</para></listitem>
<listitem><para>

<filename>initrd.gz</filename> (ramdisk image)

</para></listitem>
</itemizedlist>

</para><para>
If you intend to use the hard drive only for booting and then
download everything over the network, you should download the
&x86-netboot-initrd; file and its
corresponding kernel &x86-netboot-linux;. This will allow you
to repartition the hard disk from which you boot the installer, although you
should do so with care.
</para>

<para>
Alternatively, if you intend to keep an existing partition on the hard
drive unchanged during the install, you can download the
&x86-hdmedia-initrd; file and its kernel
&x86-hdmedia-vmlinuz;, as well as
copy an installation image to the hard drive (make sure the file is named ending in
<literal>.iso</literal>). The installer can then boot from the hard drive
and install from the installation image, without needing the network.
</para><para>

Finally, to configure the bootloader proceed to
<xref linkend="boot-initrd"/>.

</para>
  </sect2>


  <sect2 arch="x86" id="files-loadlin">
  <title>Hard disk installer booting from DOS using <command>loadlin</command></title>
<para>

This section explains how to prepare your hard drive for booting the installer
from DOS using <command>loadlin</command>.

</para><para>

Copy the following directories from a &debian; installation image to <filename>c:\</filename>.

<itemizedlist>
<listitem><para>

<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)

</para></listitem>
<listitem><para>

<filename>/tools</filename> (loadlin tool)

</para></listitem>

</itemizedlist>

</para>
  </sect2>

 </sect1>