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
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
|
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->
<sect1 id="module-details">
<title>Using Individual Components</title>
<para>
In this section we will describe each installer component in
detail. The components have been grouped into stages that should
be recognizable for users. They are presented in the order they
appear during the install. Note that not all modules will be used
for every installation; which modules are actually used depends on
the installation method you use and on your hardware.
</para>
<sect2 id="di-setup">
<title>Setting up &debian; Installer and Hardware Configuration</title>
<para>
Let's assume the &debian; Installer has booted and you are facing its
first screen. At this time, the capabilities of &d-i; are still quite
limited. It doesn't know much about your hardware, preferred language,
or even the task it should perform. Don't worry. Because &d-i; is quite
clever, it can automatically probe your hardware, locate the rest
of its components and upgrade itself to a capable installation system.
However, you still need to help &d-i; with some information it can't
determine automatically (like selecting your preferred language, keyboard
layout or desired network mirror).
</para><para>
You will notice that &d-i; performs <firstterm>hardware detection</firstterm>
several times during this stage. The first time is targeted specifically
at the hardware needed to load installer components (e.g. your CD-ROM or
network card). As not all drivers may be available during this first run,
hardware detection needs to be repeated later in the process.
</para><para arch="not-s390">
During hardware detection &d-i; checks if any of the drivers for the
hardware devices in your system require firmware to be loaded. If any
firmware is requested but unavailable, a dialog will be displayed that
allows the missing firmware to be loaded from a removable medium.
See <xref linkend="loading-firmware"/> for further details.
</para>
&module-lowmem.xml;
&module-localechooser.xml;
&module-kbd-chooser.xml;
&module-s390-netdevice.xml;
&module-ddetect.xml;
&module-cdrom-detect.xml;
&module-iso-scan.xml;
&module-anna.xml;
&module-netcfg.xml;
&module-choose-mirror.xml;
</sect2>
<sect2 id="di-user-setup">
<title>Setting Up Users And Passwords</title>
<para>
Just before configuring the clock, the installer will allow you
to set up the <quote>root</quote> account and/or an account for the first
user. Other user accounts can be created after the installation has been
completed.
</para>
&module-user-setup.xml;
</sect2>
&module-clock-setup.xml;
<!-- tzsetup is included in clock-setup -->
<sect2 id="di-partition">
<title>Partitioning and Mount Point Selection</title>
<para>
At this time, after hardware detection has been executed a final time,
&d-i; should be at its full strength, customized for the user's needs
and ready to do some real work.
As the title of this section indicates, the main task of the next few
components lies in partitioning your disks, creating filesystems,
assigning mountpoints and optionally configuring closely related options
like RAID, LVM or encrypted devices.
</para>
&module-s390-dasd.xml;
&module-partman.xml;
&module-autopartkit.xml;
&module-partitioner.xml;
&module-partconf.xml;
&module-partman-md.xml;
&module-partman-lvm.xml;
&module-partman-crypto.xml;
</sect2>
<sect2 id="di-install-base">
<title>Installing the Base System</title>
<para>
Although this stage is the least problematic, it consumes a significant
fraction of the install because it downloads, verifies and unpacks the whole
base system. If you have a slow computer or network connection, this could
take some time.
</para>
&module-base-installer.xml;
</sect2>
<sect2 id="di-install-software">
<title>Installing Additional Software</title>
<para>
At this point you have a usable but limited system.
Most users will want to install additional software on the system to tune it to
their needs, and the installer allows you do so. This step can take even
longer than installing the base system if you have a slow computer or
network connection.
</para>
&module-apt-setup.xml;
&module-pkgsel.xml;
</sect2>
<sect2 id="di-make-bootable">
<title>Making Your System Bootable</title>
<para condition="supports-nfsroot">
If you are installing a diskless workstation, obviously, booting off
the local disk isn't a meaningful option, and this step will be
skipped. <phrase arch="sparc">You may wish to set OpenBoot to boot
from the network by default; see <xref
linkend="boot-dev-select-sun"/>.</phrase>
</para>
&module-os-prober.xml;
&module-hppa-palo-installer.xml;
&module-x86-grub-installer.xml;
&module-ia64-elilo-installer.xml;
&module-mipsel-colo-installer.xml;
&module-powerpc-yaboot-installer.xml;
&module-powerpc-quik-installer.xml;
&module-powerpc-grub-installer.xml;
&module-s390-zipl-installer.xml;
&module-sparc-silo-installer.xml;
&module-arm-flash-kernel-installer.xml;
&module-nobootloader.xml;
</sect2>
<sect2 id="di-finish">
<title>Finishing the Installation</title>
<para>
This is the last step in the &debian; installation process during which the
installer will do any last minute tasks.
It mostly consists of tidying up after the &d-i;.
</para>
&module-clock-setup-finish.xml;
&module-finish-install.xml;
</sect2>
<sect2 id="di-miscellaneous">
<title>Troubleshooting</title>
<para>
The components listed in this section are usually not involved in the
installation process, but are waiting in the background to help the
user in case something goes wrong.
</para>
&module-save-logs.xml;
&module-cdrom-checker.xml;
&module-shell.xml;
</sect2>
&module-network-console.xml;
</sect1>
|
