~ubuntu-branches/ubuntu/raring/installation-guide/raring-proposed
» Revision
26
: po/pot/using-d-i.pot
« back to all changes in this revision
Viewing changes to po/pot/using-d-i.pot
- browse files at revision 26
- compare with another revision
- download diff
- download tarball
- view history from revision 26
- Committer: Bazaar Package Importer
- Author(s): Colin Watson
- Date: 2008-11-20 19:15:23 UTC
- Revision ID: james.westby@ubuntu.com-20081120191523-ewj4gnnj4k6skpn4
Tags: 20081113ubuntu1
* Document user-setup encrypted private directory preseeding.
* Resynchronise with Debian. Remaining changes:
- Build only English (for now, until we figure out how to avoid trashing
translations quite so badly with Ubuntu branding etc.).
- Build only Ubuntu architectures (amd64, hppa, i386, ia64, lpia,
powerpc, sparc).
- Extensive (although possibly incomplete) Ubuntu branding, adjustments
for our mirror layout, etc.
- Add "Ubuntu and Debian" and "What is Ubuntu?" section, text borrowed
from the Ubuntu web site. Disable the "What is Debian GNU/Linux?"
section.
- Direct installation reports to ubuntu-users for now.
- Adjust various memory and disk space requirements. Talk about the
default Ubuntu desktop and Ubuntu tasks rather than Debian tasks.
- Document mounting /sys in various places.
- Unset supports-floppy-boot for all our architectures.
- Add a few more supports-floppy-boot and bootable-usb conditionals.
- Document our root password and sudo arrangements.
- Document netboot-style USB images. Still mention the hd-media images,
but they're downplayed since many USB sticks are too small for a full
Ubuntu ISO image.
- Document Kickstart installations (currently only the basics, a
reference to Red Hat's documentation, and the differences from
Anaconda).
- Update keyboard preseeding documentation for console-setup.
- Update chroot-install guide for console-setup and language packs; add
a bit more advice about installing grub.
- Disable documentation of win32-loader.
- Document new simplified partman preseeding.
- Document mirror/udeb/components.
- Document apt-setup/security_path.
- Don't recommend passing http://archive.ubuntu.com/ubuntu to
debootstrap.
- Document partman/early_command.
- Document pkgsel/update-policy.
* Bump kernelversion to 2.6.27.
* Bump GNOME version to 2.26.
* Bump release version and names for Jaunty.
* Re-enable documentation of the GTK frontend.
* Resynchronise with Debian. Remaining changes:
- Build only English (for now, until we figure out how to avoid trashing
translations quite so badly with Ubuntu branding etc.).
- Build only Ubuntu architectures (amd64, hppa, i386, ia64, lpia,
powerpc, sparc).
- Extensive (although possibly incomplete) Ubuntu branding, adjustments
for our mirror layout, etc.
- Add "Ubuntu and Debian" and "What is Ubuntu?" section, text borrowed
from the Ubuntu web site. Disable the "What is Debian GNU/Linux?"
section.
- Direct installation reports to ubuntu-users for now.
- Adjust various memory and disk space requirements. Talk about the
default Ubuntu desktop and Ubuntu tasks rather than Debian tasks.
- Document mounting /sys in various places.
- Unset supports-floppy-boot for all our architectures.
- Add a few more supports-floppy-boot and bootable-usb conditionals.
- Document our root password and sudo arrangements.
- Document netboot-style USB images. Still mention the hd-media images,
but they're downplayed since many USB sticks are too small for a full
Ubuntu ISO image.
- Document Kickstart installations (currently only the basics, a
reference to Red Hat's documentation, and the differences from
Anaconda).
- Update keyboard preseeding documentation for console-setup.
- Update chroot-install guide for console-setup and language packs; add
a bit more advice about installing grub.
- Disable documentation of win32-loader.
- Document new simplified partman preseeding.
- Document mirror/udeb/components.
- Document apt-setup/security_path.
- Don't recommend passing http://archive.ubuntu.com/ubuntu to
debootstrap.
- Document partman/early_command.
- Document pkgsel/update-policy.
* Bump kernelversion to 2.6.27.
* Bump GNOME version to 2.26.
* Bump release version and names for Jaunty.
* Re-enable documentation of the GTK frontend.
- files added:
- ca/hardware/buying-hardware.xml
- files removed:
- ca/using-d-i/modules/mipsel/delo-installer.xml
- files modified:
- build/arch-options/alpha
added
removed
po/pot/using-d-i.pot
6
6
msgstr ""
7
7
"Project-Id-Version: PACKAGE VERSION\n"
8
8
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
9
"POT-Creation-Date: 2008-05-05 00:09+0000\n"
9
"POT-Creation-Date: 2008-10-26 00:10+0000\n"
10
10
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
11
11
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
12
12
"Language-Team: LANGUAGE <LL@li.org>\n"
65
65
#. Tag: para
66
66
#: using-d-i.xml:59
67
67
#, no-c-format
68
msgid "The normal installer display is character-based (as opposed to the now more familiar graphical interface). The mouse is not operational in this environment. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
69
msgstr ""
70
71
#. Tag: para
72
#: using-d-i.xml:77
68
msgid "For this architecture the &d-i; supports two different user interfaces: a character-based one and a graphical one. The character-based interface is used by default unless you selected the <quote>Graphical install</quote> option in the initial boot menu. For more information about the graphical installer, please refer to <xref linkend=\"graphical\"/>."
69
msgstr ""
70
71
#. Tag: para
72
#: using-d-i.xml:67
73
#, no-c-format
74
msgid "For this architecture the installer uses a character-based user interface. A graphical user interface is currently not available."
75
msgstr ""
76
77
#. Tag: para
78
#: using-d-i.xml:72
79
#, no-c-format
80
msgid "In the character-based environment the use of a mouse is not supported. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
81
msgstr ""
82
83
#. Tag: para
84
#: using-d-i.xml:89
73
85
#, no-c-format
74
86
msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below."
75
87
msgstr ""
76
88
77
89
#. Tag: para
78
#: using-d-i.xml:82
90
#: using-d-i.xml:94
79
91
#, no-c-format
80
92
msgid "Error messages and logs are redirected to the fourth console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F4</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
81
93
msgstr ""
82
94
83
95
#. Tag: para
84
#: using-d-i.xml:92
96
#: using-d-i.xml:104
85
97
#, no-c-format
86
98
msgid "These messages can also be found in <filename>/var/log/syslog</filename>. After installation, this log is copied to <filename>/var/log/installer/syslog</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system."
87
99
msgstr ""
88
100
89
101
#. Tag: title
90
#: using-d-i.xml:106
102
#: using-d-i.xml:118
91
103
#, no-c-format
92
104
msgid "Components Introduction"
93
105
msgstr ""
94
106
95
107
#. Tag: para
96
#: using-d-i.xml:107
108
#: using-d-i.xml:119
97
109
#, no-c-format
98
110
msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>."
99
111
msgstr ""
100
112
101
113
#. Tag: term
102
#: using-d-i.xml:118
114
#: using-d-i.xml:130
103
115
#, no-c-format
104
116
msgid "main-menu"
105
117
msgstr ""
106
118
107
119
#. Tag: para
108
#: using-d-i.xml:118
120
#: using-d-i.xml:130
109
121
#, no-c-format
110
122
msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear."
111
123
msgstr ""
112
124
113
125
#. Tag: para
114
#: using-d-i.xml:128
126
#: using-d-i.xml:140
115
127
#, no-c-format
116
128
msgid "You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly to back all the way out of the currently running component."
117
129
msgstr ""
118
130
119
131
#. Tag: term
120
#: using-d-i.xml:137
132
#: using-d-i.xml:149
121
133
#, no-c-format
122
134
msgid "localechooser"
123
135
msgstr ""
124
136
125
137
#. Tag: para
126
#: using-d-i.xml:137
138
#: using-d-i.xml:149
127
139
#, no-c-format
128
140
msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English."
129
141
msgstr ""
130
142
131
143
#. Tag: term
132
#: using-d-i.xml:149
144
#: using-d-i.xml:161
133
145
#, no-c-format
134
146
msgid "kbd-chooser"
135
147
msgstr ""
136
148
137
149
#. Tag: para
138
#: using-d-i.xml:149
150
#: using-d-i.xml:161
139
151
#, no-c-format
140
152
msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
141
153
msgstr ""
142
154
143
155
#. Tag: term
144
#: using-d-i.xml:158
156
#: using-d-i.xml:170
145
157
#, no-c-format
146
158
msgid "hw-detect"
147
159
msgstr ""
148
160
149
161
#. Tag: para
150
#: using-d-i.xml:158
162
#: using-d-i.xml:170
151
163
#, no-c-format
152
164
msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
153
165
msgstr ""
154
166
155
167
#. Tag: term
156
#: using-d-i.xml:167
168
#: using-d-i.xml:179
157
169
#, no-c-format
158
170
msgid "cdrom-detect"
159
171
msgstr ""
160
172
161
173
#. Tag: para
162
#: using-d-i.xml:167
174
#: using-d-i.xml:179
163
175
#, no-c-format
164
176
msgid "Looks for and mounts a Debian installation CD."
165
177
msgstr ""
166
178
167
179
#. Tag: term
168
#: using-d-i.xml:175
180
#: using-d-i.xml:187
169
181
#, no-c-format
170
182
msgid "netcfg"
171
183
msgstr ""
172
184
173
185
#. Tag: para
174
#: using-d-i.xml:175
186
#: using-d-i.xml:187
175
187
#, no-c-format
176
188
msgid "Configures the computer's network connections so it can communicate over the internet."
177
189
msgstr ""
178
190
179
191
#. Tag: term
180
#: using-d-i.xml:184
192
#: using-d-i.xml:196
181
193
#, no-c-format
182
194
msgid "iso-scan"
183
195
msgstr ""
184
196
185
197
#. Tag: para
186
#: using-d-i.xml:184
198
#: using-d-i.xml:196
187
199
#, no-c-format
188
msgid "Looks for ISO file systems, which may be on a CD-ROM or on the hard drive."
200
msgid "Searches for ISO images (<filename>.iso</filename> files) on hard drives."
189
201
msgstr ""
190
202
191
203
#. Tag: term
192
#: using-d-i.xml:193
204
#: using-d-i.xml:204
193
205
#, no-c-format
194
206
msgid "choose-mirror"
195
207
msgstr ""
196
208
197
209
#. Tag: para
198
#: using-d-i.xml:193
210
#: using-d-i.xml:204
199
211
#, no-c-format
200
212
msgid "Presents a list of Debian archive mirrors. The user may choose the source of his installation packages."
201
213
msgstr ""
202
214
203
215
#. Tag: term
204
#: using-d-i.xml:202
216
#: using-d-i.xml:213
205
217
#, no-c-format
206
218
msgid "cdrom-checker"
207
219
msgstr ""
208
220
209
221
#. Tag: para
210
#: using-d-i.xml:202
222
#: using-d-i.xml:213
211
223
#, no-c-format
212
224
msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted."
213
225
msgstr ""
214
226
215
227
#. Tag: term
216
#: using-d-i.xml:211
228
#: using-d-i.xml:222
217
229
#, no-c-format
218
230
msgid "lowmem"
219
231
msgstr ""
220
232
221
233
#. Tag: para
222
#: using-d-i.xml:211
234
#: using-d-i.xml:222
223
235
#, no-c-format
224
236
msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)."
225
237
msgstr ""
226
238
227
239
#. Tag: term
228
#: using-d-i.xml:221
240
#: using-d-i.xml:232
229
241
#, no-c-format
230
242
msgid "anna"
231
243
msgstr ""
232
244
233
245
#. Tag: para
234
#: using-d-i.xml:221
246
#: using-d-i.xml:232
235
247
#, no-c-format
236
248
msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
237
249
msgstr ""
238
250
239
251
#. Tag: term
240
#: using-d-i.xml:230
252
#: using-d-i.xml:241
241
253
#, no-c-format
242
254
msgid "clock-setup"
243
255
msgstr ""
244
256
245
257
#. Tag: para
246
#: using-d-i.xml:230
258
#: using-d-i.xml:241
247
259
#, no-c-format
248
260
msgid "Updates the system clock and determines whether the clock is set to UTC or not."
249
261
msgstr ""
250
262
251
263
#. Tag: term
252
#: using-d-i.xml:239
264
#: using-d-i.xml:250
253
265
#, no-c-format
254
266
msgid "tzsetup"
255
267
msgstr ""
256
268
257
269
#. Tag: para
258
#: using-d-i.xml:239
270
#: using-d-i.xml:250
259
271
#, no-c-format
260
272
msgid "Selects the time zone, based on the location selected earlier."
261
273
msgstr ""
262
274
263
275
#. Tag: term
264
#: using-d-i.xml:247
276
#: using-d-i.xml:258
265
277
#, no-c-format
266
278
msgid "partman"
267
279
msgstr ""
268
280
269
281
#. Tag: para
270
#: using-d-i.xml:247
282
#: using-d-i.xml:258
271
283
#, no-c-format
272
284
msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in Debian."
273
285
msgstr ""
274
286
275
287
#. Tag: term
276
#: using-d-i.xml:259
288
#: using-d-i.xml:270
277
289
#, no-c-format
278
290
msgid "partitioner"
279
291
msgstr ""
280
292
281
293
#. Tag: para
282
#: using-d-i.xml:259
294
#: using-d-i.xml:270
283
295
#, no-c-format
284
296
msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
285
297
msgstr ""
286
298
287
299
#. Tag: term
288
#: using-d-i.xml:269
300
#: using-d-i.xml:280
289
301
#, no-c-format
290
302
msgid "partconf"
291
303
msgstr ""
292
304
293
305
#. Tag: para
294
#: using-d-i.xml:269
306
#: using-d-i.xml:280
295
307
#, no-c-format
296
308
msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
297
309
msgstr ""
298
310
299
311
#. Tag: term
300
#: using-d-i.xml:278
312
#: using-d-i.xml:289
301
313
#, no-c-format
302
314
msgid "lvmcfg"
303
315
msgstr ""
304
316
305
317
#. Tag: para
306
#: using-d-i.xml:278
318
#: using-d-i.xml:289
307
319
#, no-c-format
308
320
msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
309
321
msgstr ""
310
322
311
323
#. Tag: term
312
#: using-d-i.xml:287
324
#: using-d-i.xml:298
313
325
#, no-c-format
314
326
msgid "mdcfg"
315
327
msgstr ""
316
328
317
329
#. Tag: para
318
#: using-d-i.xml:287
330
#: using-d-i.xml:298
319
331
#, no-c-format
320
msgid "Allows the user to setup Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
332
msgid "Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
321
333
msgstr ""
322
334
323
335
#. Tag: term
324
#: using-d-i.xml:298
336
#: using-d-i.xml:309
325
337
#, no-c-format
326
338
msgid "base-installer"
327
339
msgstr ""
328
340
329
341
#. Tag: para
330
#: using-d-i.xml:298
342
#: using-d-i.xml:309
331
343
#, no-c-format
332
344
msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted."
333
345
msgstr ""
334
346
335
347
#. Tag: term
336
#: using-d-i.xml:307
348
#: using-d-i.xml:318
337
349
#, no-c-format
338
350
msgid "user-setup"
339
351
msgstr ""
340
352
341
353
#. Tag: para
342
#: using-d-i.xml:307
354
#: using-d-i.xml:318
343
355
#, no-c-format
344
356
msgid "Sets up the root password, and adds a non-root user."
345
357
msgstr ""
346
358
347
359
#. Tag: term
348
#: using-d-i.xml:315
360
#: using-d-i.xml:326
349
361
#, no-c-format
350
362
msgid "apt-setup"
351
363
msgstr ""
352
364
353
365
#. Tag: para
354
#: using-d-i.xml:315
366
#: using-d-i.xml:326
355
367
#, no-c-format
356
368
msgid "Configures apt, mostly automatically, based on what media the installer is running from."
357
369
msgstr ""
358
370
359
371
#. Tag: term
360
#: using-d-i.xml:324
372
#: using-d-i.xml:335
361
373
#, no-c-format
362
374
msgid "pkgsel"
363
375
msgstr ""
364
376
365
377
#. Tag: para
366
#: using-d-i.xml:324
378
#: using-d-i.xml:335
367
379
#, no-c-format
368
380
msgid "Uses <classname>tasksel</classname> to select and install additional software."
369
381
msgstr ""
370
382
371
383
#. Tag: term
372
#: using-d-i.xml:332
384
#: using-d-i.xml:343
373
385
#, no-c-format
374
386
msgid "os-prober"
375
387
msgstr ""
376
388
377
389
#. Tag: para
378
#: using-d-i.xml:332
390
#: using-d-i.xml:343
379
391
#, no-c-format
380
392
msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
381
393
msgstr ""
382
394
383
395
#. Tag: term
384
#: using-d-i.xml:344
396
#: using-d-i.xml:355
385
397
#, no-c-format
386
398
msgid "bootloader-installer"
387
399
msgstr ""
388
400
389
401
#. Tag: para
390
#: using-d-i.xml:344
402
#: using-d-i.xml:355
391
403
#, no-c-format
392
404
msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using Linux without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
393
405
msgstr ""
394
406
395
407
#. Tag: term
396
#: using-d-i.xml:355
408
#: using-d-i.xml:366
397
409
#, no-c-format
398
410
msgid "shell"
399
411
msgstr ""
400
412
401
413
#. Tag: para
402
#: using-d-i.xml:355
414
#: using-d-i.xml:366
403
415
#, no-c-format
404
416
msgid "Allows the user to execute a shell from the menu, or in the second console."
405
417
msgstr ""
406
418
407
419
#. Tag: term
408
#: using-d-i.xml:364
420
#: using-d-i.xml:375
409
421
#, no-c-format
410
422
msgid "save-logs"
411
423
msgstr ""
412
424
413
425
#. Tag: para
414
#: using-d-i.xml:364
426
#: using-d-i.xml:375
415
427
#, no-c-format
416
428
msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to Debian developers later."
417
429
msgstr ""
418
430
419
431
#. Tag: title
420
#: using-d-i.xml:382
432
#: using-d-i.xml:393
421
433
#, no-c-format
422
434
msgid "Using Individual Components"
423
435
msgstr ""
424
436
425
437
#. Tag: para
426
#: using-d-i.xml:383
438
#: using-d-i.xml:394
427
439
#, no-c-format
428
440
msgid "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."
429
441
msgstr ""
430
442
431
443
#. Tag: title
432
#: using-d-i.xml:395
444
#: using-d-i.xml:406
433
445
#, no-c-format
434
446
msgid "Setting up Debian Installer and Hardware Configuration"
435
447
msgstr ""
436
448
437
449
#. Tag: para
438
#: using-d-i.xml:396
450
#: using-d-i.xml:407
439
451
#, no-c-format
440
452
msgid "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)."
441
453
msgstr ""
442
454
443
455
#. Tag: para
444
#: using-d-i.xml:409
456
#: using-d-i.xml:420
445
457
#, no-c-format
446
458
msgid "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."
447
459
msgstr ""
448
460
461
#. Tag: para
462
#: using-d-i.xml:428
463
#, no-c-format
464
msgid "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."
465
msgstr ""
466
449
467
#. Tag: title
450
#: using-d-i.xml:424
468
#: using-d-i.xml:443
451
469
#, no-c-format
452
470
msgid "Check available memory / low memory mode"
453
471
msgstr ""
454
472
455
473
#. Tag: para
456
#: using-d-i.xml:426
474
#: using-d-i.xml:445
457
475
#, no-c-format
458
476
msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian; on your system."
459
477
msgstr ""
460
478
461
479
#. Tag: para
462
#: using-d-i.xml:433
480
#: using-d-i.xml:452
463
481
#, no-c-format
464
482
msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed."
465
483
msgstr ""
466
484
467
485
#. Tag: para
468
#: using-d-i.xml:440
486
#: using-d-i.xml:459
469
487
#, no-c-format
470
488
msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
471
489
msgstr ""
472
490
473
491
#. Tag: para
474
#: using-d-i.xml:449
492
#: using-d-i.xml:468
475
493
#, no-c-format
476
494
msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64–128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity."
477
495
msgstr ""
478
496
479
497
#. Tag: para
480
#: using-d-i.xml:459
498
#: using-d-i.xml:478
481
499
#, no-c-format
482
500
msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)."
483
501
msgstr ""
484
502
485
503
#. Tag: para
486
#: using-d-i.xml:466
504
#: using-d-i.xml:485
487
505
#, no-c-format
488
506
msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation."
489
507
msgstr ""
490
508
491
509
#. Tag: para
492
#: using-d-i.xml:474
510
#: using-d-i.xml:493
493
511
#, no-c-format
494
512
msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>."
495
513
msgstr ""
496
514
497
515
#. Tag: title
498
#: using-d-i.xml:489
516
#: using-d-i.xml:508
499
517
#, no-c-format
500
518
msgid "Selecting Localization Options"
501
519
msgstr ""
502
520
503
521
#. Tag: para
504
#: using-d-i.xml:491
522
#: using-d-i.xml:510
505
523
#, no-c-format
506
524
msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, country and locales."
507
525
msgstr ""
508
526
509
527
#. Tag: para
510
#: using-d-i.xml:498
528
#: using-d-i.xml:517
511
529
#, no-c-format
512
530
msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English."
513
531
msgstr ""
514
532
515
533
#. Tag: para
516
#: using-d-i.xml:505
534
#: using-d-i.xml:524
517
535
#, no-c-format
518
536
msgid "The selected country will be used later in the installation process to pick the default timezone and a Debian mirror appropriate for your geographic location. Language and country together will be used to set the default locale for your system and to help select your keyboard."
519
537
msgstr ""
520
538
521
539
#. Tag: para
522
#: using-d-i.xml:512
523
#, no-c-format
524
msgid "You will first be asked to select your preferred language. The language names are listed in both English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
525
msgstr ""
526
527
#. Tag: para
528
#: using-d-i.xml:524
529
#, no-c-format
530
msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will next be asked to select a country. If you choose <guimenuitem>Other</guimenuitem> at the bottom of the list, you will be presented with a list of all countries, grouped by continent. If the language has only one country associated with it, that country will be selected automatically."
531
msgstr ""
532
533
#. Tag: para
534
#: using-d-i.xml:542
540
#: using-d-i.xml:531
541
#, no-c-format
542
msgid "You will first be asked to select your preferred language. The language names are listed both in English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
543
msgstr ""
544
545
#. Tag: para
546
#: using-d-i.xml:543
547
#, no-c-format
548
msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will be shown a list of only those countries. To select a country that is not in that list, choose <guimenuitem>Other</guimenuitem> (the last option). You will then be presented with a list of continents; selecting a continent will lead to a list of relevant countries on that continent."
549
msgstr ""
550
551
#. Tag: para
552
#: using-d-i.xml:561
553
#, no-c-format
554
msgid "If the language has only one country associated with it, that country will be selected automatically. In that case it is only possible to select a different country by first lowering the debconf priority to medium, followed by revisiting the language selection option in the main menu of the installer."
555
msgstr ""
556
557
#. Tag: para
558
#: using-d-i.xml:569
535
559
#, no-c-format
536
560
msgid "A default locale will be selected based on the selected language and country. If you are installing at medium or low priority, you will have the option of selecting a different default locale and of selecting additional locales to be generated for the installed system."
537
561
msgstr ""
538
562
539
563
#. Tag: title
540
#: using-d-i.xml:557
564
#: using-d-i.xml:584
541
565
#, no-c-format
542
566
msgid "Choosing a Keyboard"
543
567
msgstr ""
544
568
545
569
#. Tag: para
546
#: using-d-i.xml:559
570
#: using-d-i.xml:586
547
571
#, no-c-format
548
572
msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>kbdconfig</command> as root after you have completed the installation)."
549
573
msgstr ""
550
574
551
575
#. Tag: para
552
#: using-d-i.xml:569
576
#: using-d-i.xml:596
553
577
#, no-c-format
554
578
msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight — they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration. An 'extended' keyboard is one with <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row."
555
579
msgstr ""
556
580
557
581
#. Tag: para
558
#: using-d-i.xml:578
559
#, no-c-format
560
msgid "On DECstations there is currently no loadable keymap available, so you have to skip the keyboard selection and keep the default kernel keymap (LK201 US). This may change in the future as it depends on further Linux/MIPS kernel development."
561
msgstr ""
562
563
#. Tag: para
564
#: using-d-i.xml:585
582
#: using-d-i.xml:605
565
583
#, no-c-format
566
584
msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar."
567
585
msgstr ""
568
586
569
587
#. Tag: title
570
#: using-d-i.xml:615
588
#: using-d-i.xml:635
571
589
#, no-c-format
572
590
msgid "Looking for the Debian Installer ISO Image"
573
591
msgstr ""
574
592
575
593
#. Tag: para
576
#: using-d-i.xml:616
594
#: using-d-i.xml:636
577
595
#, no-c-format
578
596
msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the Debian Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this."
579
597
msgstr ""
580
598
581
599
#. Tag: para
582
#: using-d-i.xml:623
600
#: using-d-i.xml:643
583
601
#, no-c-format
584
602
msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid Debian iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
585
603
msgstr ""
586
604
587
605
#. Tag: para
588
#: using-d-i.xml:640
606
#: using-d-i.xml:660
589
607
#, no-c-format
590
608
msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem."
591
609
msgstr ""
592
610
593
611
#. Tag: para
594
#: using-d-i.xml:647
612
#: using-d-i.xml:667
595
613
#, no-c-format
596
614
msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console."
597
615
msgstr ""
598
616
599
617
#. Tag: title
600
#: using-d-i.xml:668
618
#: using-d-i.xml:688
601
619
#, no-c-format
602
620
msgid "Configuring the Network"
603
621
msgstr ""
604
622
605
623
#. Tag: para
606
#: using-d-i.xml:670
624
#: using-d-i.xml:690
607
625
#, no-c-format
608
626
msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page."
609
627
msgstr ""
610
628
611
629
#. Tag: para
612
#: using-d-i.xml:681
630
#: using-d-i.xml:701
613
631
#, no-c-format
614
632
msgid "By default, &d-i; tries to configure your computer's network automatically via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it may be caused by many factors ranging from unplugged network cable, to a misconfigured DHCP setup. Or maybe you don't have a DHCP server in your local network at all. For further explanation, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again."
615
633
msgstr ""
616
634
617
635
#. Tag: para
618
#: using-d-i.xml:693
636
#: using-d-i.xml:713
619
637
#, no-c-format
620
638
msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> and a <computeroutput>WEP key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
621
639
msgstr ""
622
640
623
641
#. Tag: para
624
#: using-d-i.xml:707
642
#: using-d-i.xml:727
625
643
#, no-c-format
626
644
msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. The default broadcast address is calculated as the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the offered defaults — if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
627
645
msgstr ""
628
646
629
647
#. Tag: title
630
#: using-d-i.xml:752
648
#: using-d-i.xml:772
631
649
#, no-c-format
632
650
msgid "Configuring the Clock"
633
651
msgstr ""
634
652
635
653
#. Tag: para
636
#: using-d-i.xml:754
654
#: using-d-i.xml:774
637
655
#, no-c-format
638
656
msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process."
639
657
msgstr ""
640
658
641
659
#. Tag: para
642
#: using-d-i.xml:772
660
#: using-d-i.xml:792
643
661
#, no-c-format
644
662
msgid "Depending on the location selected earlier in the installation process, you may be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone."
645
663
msgstr ""
646
664
647
665
#. Tag: para
648
#: using-d-i.xml:779
666
#: using-d-i.xml:799
649
667
#, no-c-format
650
668
msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options."
651
669
msgstr ""
652
670
653
671
#. Tag: para
654
#: using-d-i.xml:790
672
#: using-d-i.xml:810
655
673
#, no-c-format
656
674
msgid "The simplest option is to just select a different timezone after the installation has been completed and you've booted into the new system. The command to do this is:"
657
675
msgstr ""
658
676
659
677
#. Tag: screen
660
#: using-d-i.xml:796
678
#: using-d-i.xml:816
661
679
#, no-c-format
662
680
msgid "# dpkg-reconfigure tzdata"
663
681
msgstr ""
664
682
665
683
#. Tag: para
666
#: using-d-i.xml:802
684
#: using-d-i.xml:822
667
685
#, no-c-format
668
686
msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
669
687
msgstr ""
670
688
671
689
#. Tag: para
672
#: using-d-i.xml:816
690
#: using-d-i.xml:836
673
691
#, no-c-format
674
692
msgid "For automated installations the time zone can also be set using preseeding."
675
693
msgstr ""
676
694
677
695
#. Tag: title
678
#: using-d-i.xml:829
696
#: using-d-i.xml:849
679
697
#, no-c-format
680
698
msgid "Partitioning and Mount Point Selection"
681
699
msgstr ""
682
700
683
701
#. Tag: para
684
#: using-d-i.xml:830
702
#: using-d-i.xml:850
685
703
#, no-c-format
686
704
msgid "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."
687
705
msgstr ""
688
706
689
707
#. Tag: para
690
#: using-d-i.xml:851
708
#: using-d-i.xml:871
691
709
#, no-c-format
692
710
msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
693
711
msgstr ""
694
712
695
713
#. Tag: para
696
#: using-d-i.xml:857
714
#: using-d-i.xml:877
697
715
#, no-c-format
698
716
msgid ""
699
717
"If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n"
702
720
msgstr ""
703
721
704
722
#. Tag: para
705
#: using-d-i.xml:870
723
#: using-d-i.xml:890
706
724
#, no-c-format
707
725
msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
708
726
msgstr ""
709
727
710
728
#. Tag: title
711
#: using-d-i.xml:880
729
#: using-d-i.xml:900
712
730
#, no-c-format
713
731
msgid "Guided Partitioning"
714
732
msgstr ""
715
733
716
734
#. Tag: para
717
#: using-d-i.xml:881
735
#: using-d-i.xml:901
718
736
#, no-c-format
719
737
msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
720
738
msgstr ""
721
739
722
740
#. Tag: para
723
#: using-d-i.xml:896
741
#: using-d-i.xml:916
724
742
#, no-c-format
725
743
msgid "The option to use (encrypted) LVM may not be available on all architectures."
726
744
msgstr ""
727
745
728
746
#. Tag: para
729
#: using-d-i.xml:901
747
#: using-d-i.xml:921
730
748
#, no-c-format
731
749
msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
732
750
msgstr ""
733
751
734
752
#. Tag: para
735
#: using-d-i.xml:910
753
#: using-d-i.xml:930
736
754
#, no-c-format
737
755
msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
738
756
msgstr ""
739
757
740
758
#. Tag: para
741
#: using-d-i.xml:919
759
#: using-d-i.xml:939
742
760
#, no-c-format
743
761
msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
744
762
msgstr ""
745
763
746
764
#. Tag: para
747
#: using-d-i.xml:929
765
#: using-d-i.xml:949
748
766
#, no-c-format
749
767
msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
750
768
msgstr ""
751
769
752
770
#. Tag: para
753
#: using-d-i.xml:938
771
#: using-d-i.xml:958
754
772
#, no-c-format
755
773
msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible."
756
774
msgstr ""
757
775
758
776
#. Tag: para
759
#: using-d-i.xml:946
777
#: using-d-i.xml:966
760
778
#, no-c-format
761
779
msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
762
780
msgstr ""
763
781
764
782
#. Tag: entry
765
#: using-d-i.xml:962
783
#: using-d-i.xml:982
766
784
#, no-c-format
767
785
msgid "Partitioning scheme"
768
786
msgstr ""
769
787
770
788
#. Tag: entry
771
#: using-d-i.xml:963
789
#: using-d-i.xml:983
772
790
#, no-c-format
773
791
msgid "Minimum space"
774
792
msgstr ""
775
793
776
794
#. Tag: entry
777
#: using-d-i.xml:964
795
#: using-d-i.xml:984
778
796
#, no-c-format
779
797
msgid "Created partitions"
780
798
msgstr ""
781
799
782
800
#. Tag: entry
783
#: using-d-i.xml:970
801
#: using-d-i.xml:990
784
802
#, no-c-format
785
803
msgid "All files in one partition"
786
804
msgstr ""
787
805
788
806
#. Tag: entry
789
#: using-d-i.xml:971
807
#: using-d-i.xml:991
790
808
#, no-c-format
791
809
msgid "600MB"
792
810
msgstr ""
793
811
794
812
#. Tag: entry
795
#: using-d-i.xml:972
813
#: using-d-i.xml:992
796
814
#, no-c-format
797
815
msgid "<filename>/</filename>, swap"
798
816
msgstr ""
799
817
800
818
#. Tag: entry
801
#: using-d-i.xml:974
819
#: using-d-i.xml:994
802
820
#, no-c-format
803
821
msgid "Separate /home partition"
804
822
msgstr ""
805
823
806
824
#. Tag: entry
807
#: using-d-i.xml:975
825
#: using-d-i.xml:995
808
826
#, no-c-format
809
827
msgid "500MB"
810
828
msgstr ""
811
829
812
830
#. Tag: entry
813
#: using-d-i.xml:976
831
#: using-d-i.xml:996
814
832
#, no-c-format
815
833
msgid "<filename>/</filename>, <filename>/home</filename>, swap"
816
834
msgstr ""
817
835
818
836
#. Tag: entry
819
#: using-d-i.xml:980
837
#: using-d-i.xml:1000
820
838
#, no-c-format
821
839
msgid "Separate /home, /usr, /var and /tmp partitions"
822
840
msgstr ""
823
841
824
842
#. Tag: entry
825
#: using-d-i.xml:981
843
#: using-d-i.xml:1001
826
844
#, no-c-format
827
845
msgid "<entry>1GB</entry>"
828
846
msgstr ""
829
847
830
848
#. Tag: entry
831
#: using-d-i.xml:982
849
#: using-d-i.xml:1002
832
850
#, no-c-format
833
851
msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
834
852
msgstr ""
835
853
836
854
#. Tag: para
837
#: using-d-i.xml:991
855
#: using-d-i.xml:1011
838
856
#, no-c-format
839
857
msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
840
858
msgstr ""
841
859
842
860
#. Tag: para
843
#: using-d-i.xml:997
861
#: using-d-i.xml:1017
844
862
#, no-c-format
845
863
msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
846
864
msgstr ""
847
865
848
866
#. Tag: para
849
#: using-d-i.xml:1005
867
#: using-d-i.xml:1025
850
868
#, no-c-format
851
869
msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader."
852
870
msgstr ""
853
871
854
872
#. Tag: para
855
#: using-d-i.xml:1011
873
#: using-d-i.xml:1031
856
874
#, no-c-format
857
875
msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted."
858
876
msgstr ""
859
877
860
878
#. Tag: para
861
#: using-d-i.xml:1017
879
#: using-d-i.xml:1037
862
880
#, no-c-format
863
881
msgid ""
864
882
"The list of partitions might look like this: <informalexample><screen>\n"
881
899
msgstr ""
882
900
883
901
#. Tag: para
884
#: using-d-i.xml:1030
902
#: using-d-i.xml:1050
885
903
#, no-c-format
886
904
msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
887
905
msgstr ""
888
906
889
907
#. Tag: title
890
#: using-d-i.xml:1044
908
#: using-d-i.xml:1064
891
909
#, no-c-format
892
910
msgid "Manual Partitioning"
893
911
msgstr ""
894
912
895
913
#. Tag: para
896
#: using-d-i.xml:1045
914
#: using-d-i.xml:1065
897
915
#, no-c-format
898
msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually setup your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section."
916
msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually set up your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section."
899
917
msgstr ""
900
918
901
919
#. Tag: para
902
#: using-d-i.xml:1053
920
#: using-d-i.xml:1073
903
921
#, no-c-format
904
922
msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
905
923
msgstr ""
906
924
907
925
#. Tag: para
908
#: using-d-i.xml:1061
926
#: using-d-i.xml:1081
909
927
#, no-c-format
910
928
msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
911
929
msgstr ""
912
930
913
931
#. Tag: para
914
#: using-d-i.xml:1083
932
#: using-d-i.xml:1103
915
933
#, no-c-format
916
934
msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition."
917
935
msgstr ""
918
936
919
937
#. Tag: para
920
#: using-d-i.xml:1094
938
#: using-d-i.xml:1114
921
939
#, no-c-format
922
940
msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
923
941
msgstr ""
924
942
925
943
#. Tag: para
926
#: using-d-i.xml:1102
944
#: using-d-i.xml:1122
927
945
#, no-c-format
928
946
msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
929
947
msgstr ""
930
948
931
949
#. Tag: para
932
#: using-d-i.xml:1108
950
#: using-d-i.xml:1128
933
951
#, no-c-format
934
952
msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
935
953
msgstr ""
936
954
937
955
#. Tag: para
938
#: using-d-i.xml:1116
956
#: using-d-i.xml:1136
939
957
#, no-c-format
940
958
msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
941
959
msgstr ""
942
960
943
961
#. Tag: title
944
#: using-d-i.xml:1144
962
#: using-d-i.xml:1164
945
963
#, no-c-format
946
964
msgid "Configuring Multidisk Devices (Software RAID)"
947
965
msgstr ""
948
966
949
967
#. Tag: para
950
#: using-d-i.xml:1145
968
#: using-d-i.xml:1165
951
969
#, no-c-format
952
msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
970
msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. </para></footnote> in your computer, you can use <command>mdcfg</command> to set up your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
953
971
msgstr ""
954
972
955
973
#. Tag: para
956
#: using-d-i.xml:1159
974
#: using-d-i.xml:1178
957
975
#, no-c-format
958
976
msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
959
977
msgstr ""
960
978
961
979
#. Tag: para
962
#: using-d-i.xml:1167
980
#: using-d-i.xml:1186
963
981
#, no-c-format
964
msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:"
982
msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:"
965
983
msgstr ""
966
984
967
985
#. Tag: entry
968
#: using-d-i.xml:1245
986
#: using-d-i.xml:1300
969
987
#, no-c-format
970
988
msgid "Type"
971
989
msgstr ""
972
990
973
991
#. Tag: entry
974
#: using-d-i.xml:1246
992
#: using-d-i.xml:1301
975
993
#, no-c-format
976
994
msgid "Minimum Devices"
977
995
msgstr ""
978
996
979
997
#. Tag: entry
980
#: using-d-i.xml:1247
998
#: using-d-i.xml:1302
981
999
#, no-c-format
982
1000
msgid "Spare Device"
983
1001
msgstr ""
984
1002
985
1003
#. Tag: entry
986
#: using-d-i.xml:1248
1004
#: using-d-i.xml:1303
987
1005
#, no-c-format
988
1006
msgid "Survives disk failure?"
989
1007
msgstr ""
990
1008
991
1009
#. Tag: entry
992
#: using-d-i.xml:1249
1010
#: using-d-i.xml:1304
993
1011
#, no-c-format
994
1012
msgid "Available Space"
995
1013
msgstr ""
996
1014
997
1015
#. Tag: entry
998
#: using-d-i.xml:1255
1016
#: using-d-i.xml:1310
999
1017
#, no-c-format
1000
1018
msgid "RAID0"
1001
1019
msgstr ""
1002
1020
1003
1021
#. Tag: entry
1004
#: using-d-i.xml:1256 using-d-i.xml:1264
1022
#: using-d-i.xml:1311 using-d-i.xml:1319 using-d-i.xml:1349
1005
1023
#, no-c-format
1006
1024
msgid "<entry>2</entry>"
1007
1025
msgstr ""
1008
1026
1009
1027
#. Tag: entry
1010
#: using-d-i.xml:1257 using-d-i.xml:1258
1028
#: using-d-i.xml:1312 using-d-i.xml:1313
1011
1029
#, no-c-format
1012
1030
msgid "<entry>no</entry>"
1013
1031
msgstr ""
1014
1032
1015
1033
#. Tag: entry
1016
#: using-d-i.xml:1259
1034
#: using-d-i.xml:1314
1017
1035
#, no-c-format
1018
1036
msgid "Size of the smallest partition multiplied by number of devices in RAID"
1019
1037
msgstr ""
1020
1038
1021
1039
#. Tag: entry
1022
#: using-d-i.xml:1263
1040
#: using-d-i.xml:1318
1023
1041
#, no-c-format
1024
1042
msgid "RAID1"
1025
1043
msgstr ""
1026
1044
1027
1045
#. Tag: entry
1028
#: using-d-i.xml:1265 using-d-i.xml:1273
1046
#: using-d-i.xml:1320 using-d-i.xml:1328 using-d-i.xml:1339 using-d-i.xml:1350
1029
1047
#, no-c-format
1030
1048
msgid "optional"
1031
1049
msgstr ""
1032
1050
1033
1051
#. Tag: entry
1034
#: using-d-i.xml:1266 using-d-i.xml:1274
1052
#: using-d-i.xml:1321 using-d-i.xml:1329 using-d-i.xml:1340 using-d-i.xml:1351
1035
1053
#, no-c-format
1036
1054
msgid "<entry>yes</entry>"
1037
1055
msgstr ""
1038
1056
1039
1057
#. Tag: entry
1040
#: using-d-i.xml:1267
1058
#: using-d-i.xml:1322
1041
1059
#, no-c-format
1042
1060
msgid "Size of the smallest partition in RAID"
1043
1061
msgstr ""
1044
1062
1045
1063
#. Tag: entry
1046
#: using-d-i.xml:1271
1064
#: using-d-i.xml:1326
1047
1065
#, no-c-format
1048
1066
msgid "RAID5"
1049
1067
msgstr ""
1050
1068
1051
1069
#. Tag: entry
1052
#: using-d-i.xml:1272
1070
#: using-d-i.xml:1327
1053
1071
#, no-c-format
1054
1072
msgid "<entry>3</entry>"
1055
1073
msgstr ""
1056
1074
1057
1075
#. Tag: entry
1058
#: using-d-i.xml:1275
1076
#: using-d-i.xml:1330
1059
1077
#, no-c-format
1060
1078
msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
1061
1079
msgstr ""
1062
1080
1081
#. Tag: entry
1082
#: using-d-i.xml:1337
1083
#, no-c-format
1084
msgid "RAID6"
1085
msgstr ""
1086
1087
#. Tag: entry
1088
#: using-d-i.xml:1338
1089
#, no-c-format
1090
msgid "<entry>4</entry>"
1091
msgstr ""
1092
1093
#. Tag: entry
1094
#: using-d-i.xml:1341
1095
#, no-c-format
1096
msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)"
1097
msgstr ""
1098
1099
#. Tag: entry
1100
#: using-d-i.xml:1348
1101
#, no-c-format
1102
msgid "RAID10"
1103
msgstr ""
1104
1105
#. Tag: entry
1106
#: using-d-i.xml:1352
1107
#, no-c-format
1108
msgid "Total of all partitions divided by the number of chunk copies (defaults to two)"
1109
msgstr ""
1110
1063
1111
#. Tag: para
1064
#: using-d-i.xml:1283
1112
#: using-d-i.xml:1359
1065
1113
#, no-c-format
1066
1114
msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
1067
1115
msgstr ""
1068
1116
1069
1117
#. Tag: para
1070
#: using-d-i.xml:1288
1118
#: using-d-i.xml:1364
1071
1119
#, no-c-format
1072
msgid "To create a MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
1120
msgid "To create an MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
1073
1121
msgstr ""
1074
1122
1075
1123
#. Tag: para
1076
#: using-d-i.xml:1297
1124
#: using-d-i.xml:1373
1077
1125
#, no-c-format
1078
1126
msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
1079
1127
msgstr ""
1080
1128
1081
1129
#. Tag: para
1082
#: using-d-i.xml:1309
1130
#: using-d-i.xml:1385
1083
1131
#, no-c-format
1084
1132
msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
1085
1133
msgstr ""
1086
1134
1087
1135
#. Tag: para
1088
#: using-d-i.xml:1318
1136
#: using-d-i.xml:1394
1089
1137
#, no-c-format
1090
1138
msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected."
1091
1139
msgstr ""
1092
1140
1093
1141
#. Tag: para
1094
#: using-d-i.xml:1331
1142
#: using-d-i.xml:1407
1095
1143
#, no-c-format
1096
1144
msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD."
1097
1145
msgstr ""
1098
1146
1099
1147
#. Tag: para
1100
#: using-d-i.xml:1338
1101
#, no-c-format
1102
msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue."
1103
msgstr ""
1104
1105
#. Tag: para
1106
#: using-d-i.xml:1350
1107
#, no-c-format
1108
msgid "RAID5 has a similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
1109
msgstr ""
1110
1111
#. Tag: para
1112
#: using-d-i.xml:1358
1148
#: using-d-i.xml:1414
1149
#, no-c-format
1150
msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue."
1151
msgstr ""
1152
1153
#. Tag: para
1154
#: using-d-i.xml:1426
1155
#, no-c-format
1156
msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
1157
msgstr ""
1158
1159
#. Tag: para
1160
#: using-d-i.xml:1432
1161
#, no-c-format
1162
msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required."
1163
msgstr ""
1164
1165
#. Tag: para
1166
#: using-d-i.xml:1438
1167
#, no-c-format
1168
msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks."
1169
msgstr ""
1170
1171
#. Tag: para
1172
#: using-d-i.xml:1452
1113
1173
#, no-c-format
1114
1174
msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)."
1115
1175
msgstr ""
1116
1176
1117
1177
#. Tag: para
1118
#: using-d-i.xml:1367
1178
#: using-d-i.xml:1461
1119
1179
#, no-c-format
1120
msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
1180
msgid "After you set up MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
1121
1181
msgstr ""
1122
1182
1123
1183
#. Tag: title
1124
#: using-d-i.xml:1382
1184
#: using-d-i.xml:1476
1125
1185
#, no-c-format
1126
1186
msgid "Configuring the Logical Volume Manager (LVM)"
1127
1187
msgstr ""
1128
1188
1129
1189
#. Tag: para
1130
#: using-d-i.xml:1383
1190
#: using-d-i.xml:1477
1131
1191
#, no-c-format
1132
msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc."
1192
msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc."
1133
1193
msgstr ""
1134
1194
1135
1195
#. Tag: para
1136
#: using-d-i.xml:1391
1196
#: using-d-i.xml:1485
1137
1197
#, no-c-format
1138
1198
msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks."
1139
1199
msgstr ""
1140
1200
1141
1201
#. Tag: para
1142
#: using-d-i.xml:1401
1202
#: using-d-i.xml:1495
1143
1203
#, no-c-format
1144
1204
msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila — your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
1145
1205
msgstr ""
1146
1206
1147
1207
#. Tag: para
1148
#: using-d-i.xml:1412
1208
#: using-d-i.xml:1506
1149
1209
#, no-c-format
1150
1210
msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
1151
1211
msgstr ""
1152
1212
1153
1213
#. Tag: para
1154
#: using-d-i.xml:1421
1214
#: using-d-i.xml:1515
1155
1215
#, no-c-format
1156
1216
msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
1157
1217
msgstr ""
1158
1218
1159
1219
#. Tag: para
1160
#: using-d-i.xml:1432
1220
#: using-d-i.xml:1526
1161
1221
#, no-c-format
1162
1222
msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more"
1163
1223
msgstr ""
1164
1224
1165
1225
#. Tag: guimenuitem
1166
#: using-d-i.xml:1437
1226
#: using-d-i.xml:1531
1167
1227
#, no-c-format
1168
1228
msgid "Create volume group"
1169
1229
msgstr ""
1170
1230
1171
1231
#. Tag: guimenuitem
1172
#: using-d-i.xml:1440
1232
#: using-d-i.xml:1534
1173
1233
#, no-c-format
1174
1234
msgid "Create logical volume"
1175
1235
msgstr ""
1176
1236
1177
1237
#. Tag: guimenuitem
1178
#: using-d-i.xml:1443
1238
#: using-d-i.xml:1537
1179
1239
#, no-c-format
1180
1240
msgid "Delete volume group"
1181
1241
msgstr ""
1182
1242
1183
1243
#. Tag: guimenuitem
1184
#: using-d-i.xml:1446
1244
#: using-d-i.xml:1540
1185
1245
#, no-c-format
1186
1246
msgid "Delete logical volume"
1187
1247
msgstr ""
1188
1248
1189
1249
#. Tag: guimenuitem
1190
#: using-d-i.xml:1449
1250
#: using-d-i.xml:1543
1191
1251
#, no-c-format
1192
1252
msgid "Extend volume group"
1193
1253
msgstr ""
1194
1254
1195
1255
#. Tag: guimenuitem
1196
#: using-d-i.xml:1452
1256
#: using-d-i.xml:1546
1197
1257
#, no-c-format
1198
1258
msgid "Reduce volume group"
1199
1259
msgstr ""
1200
1260
1201
1261
#. Tag: para
1202
#: using-d-i.xml:1454
1262
#: using-d-i.xml:1548
1203
1263
#, no-c-format
1204
1264
msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
1205
1265
msgstr ""
1206
1266
1207
1267
#. Tag: para
1208
#: using-d-i.xml:1460
1268
#: using-d-i.xml:1554
1209
1269
#, no-c-format
1210
1270
msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
1211
1271
msgstr ""
1212
1272
1213
1273
#. Tag: para
1214
#: using-d-i.xml:1465
1274
#: using-d-i.xml:1559
1215
1275
#, no-c-format
1216
1276
msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
1217
1277
msgstr ""
1218
1278
1219
1279
#. Tag: title
1220
#: using-d-i.xml:1479
1280
#: using-d-i.xml:1573
1221
1281
#, no-c-format
1222
1282
msgid "Configuring Encrypted Volumes"
1223
1283
msgstr ""
1224
1284
1225
1285
#. Tag: para
1226
#: using-d-i.xml:1480
1286
#: using-d-i.xml:1574
1227
1287
#, no-c-format
1228
1288
msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
1229
1289
msgstr ""
1230
1290
1231
1291
#. Tag: para
1232
#: using-d-i.xml:1492
1292
#: using-d-i.xml:1586
1233
1293
#, no-c-format
1234
1294
msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
1235
1295
msgstr ""
1236
1296
1237
1297
#. Tag: para
1238
#: using-d-i.xml:1507
1298
#: using-d-i.xml:1601
1239
1299
#, no-c-format
1240
1300
msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
1241
1301
msgstr ""
1242
1302
1243
1303
#. Tag: para
1244
#: using-d-i.xml:1514
1304
#: using-d-i.xml:1608
1245
1305
#, no-c-format
1246
1306
msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
1247
1307
msgstr ""
1248
1308
1249
1309
#. Tag: para
1250
#: using-d-i.xml:1525
1310
#: using-d-i.xml:1619
1251
1311
#, no-c-format
1252
1312
msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
1253
1313
msgstr ""
1254
1314
1255
1315
#. Tag: para
1256
#: using-d-i.xml:1537
1316
#: using-d-i.xml:1631
1257
1317
#, no-c-format
1258
1318
msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
1259
1319
msgstr ""
1260
1320
1261
1321
#. Tag: term
1262
#: using-d-i.xml:1547
1322
#: using-d-i.xml:1641
1263
1323
#, no-c-format
1264
1324
msgid "Encryption: <userinput>aes</userinput>"
1265
1325
msgstr ""
1266
1326
1267
1327
#. Tag: para
1268
#: using-d-i.xml:1549
1328
#: using-d-i.xml:1643
1269
1329
#, no-c-format
1270
1330
msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
1271
1331
msgstr ""
1272
1332
1273
1333
#. Tag: term
1274
#: using-d-i.xml:1567
1334
#: using-d-i.xml:1661
1275
1335
#, no-c-format
1276
1336
msgid "Key size: <userinput>256</userinput>"
1277
1337
msgstr ""
1278
1338
1279
1339
#. Tag: para
1280
#: using-d-i.xml:1569
1340
#: using-d-i.xml:1663
1281
1341
#, no-c-format
1282
1342
msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
1283
1343
msgstr ""
1284
1344
1285
1345
#. Tag: term
1286
#: using-d-i.xml:1581
1346
#: using-d-i.xml:1675
1287
1347
#, no-c-format
1288
1348
msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>"
1289
1349
msgstr ""
1290
1350
1291
1351
#. Tag: para
1292
#: using-d-i.xml:1583
1352
#: using-d-i.xml:1677
1293
1353
#, no-c-format
1294
1354
msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
1295
1355
msgstr ""
1296
1356
1297
1357
#. Tag: para
1298
#: using-d-i.xml:1593
1358
#: using-d-i.xml:1687
1299
1359
#, no-c-format
1300
1360
msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
1301
1361
msgstr ""
1302
1362
1303
1363
#. Tag: term
1304
#: using-d-i.xml:1605
1364
#: using-d-i.xml:1699
1305
1365
#, no-c-format
1306
1366
msgid "Encryption key: <userinput>Passphrase</userinput>"
1307
1367
msgstr ""
1308
1368
1309
1369
#. Tag: para
1310
#: using-d-i.xml:1607
1370
#: using-d-i.xml:1701
1311
1371
#, no-c-format
1312
1372
msgid "Here you can choose the type of the encryption key for this partition."
1313
1373
msgstr ""
1314
1374
1315
1375
#. Tag: term
1316
#: using-d-i.xml:1613
1376
#: using-d-i.xml:1707
1317
1377
#, no-c-format
1318
1378
msgid "Passphrase"
1319
1379
msgstr ""
1320
1380
1321
1381
#. Tag: para
1322
#: using-d-i.xml:1614
1382
#: using-d-i.xml:1708
1323
1383
#, no-c-format
1324
1384
msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
1325
1385
msgstr ""
1326
1386
1327
1387
#. Tag: term
1328
#: using-d-i.xml:1629 using-d-i.xml:1722
1388
#: using-d-i.xml:1723 using-d-i.xml:1816
1329
1389
#, no-c-format
1330
1390
msgid "Random key"
1331
1391
msgstr ""
1332
1392
1333
1393
#. Tag: para
1334
#: using-d-i.xml:1630
1394
#: using-d-i.xml:1724
1335
1395
#, no-c-format
1336
1396
msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
1337
1397
msgstr ""
1338
1398
1339
1399
#. Tag: para
1340
#: using-d-i.xml:1639
1400
#: using-d-i.xml:1733
1341
1401
#, no-c-format
1342
1402
msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
1343
1403
msgstr ""
1344
1404
1345
1405
#. Tag: term
1346
#: using-d-i.xml:1658 using-d-i.xml:1735
1406
#: using-d-i.xml:1752 using-d-i.xml:1829
1347
1407
#, no-c-format
1348
1408
msgid "Erase data: <userinput>yes</userinput>"
1349
1409
msgstr ""
1350
1410
1351
1411
#. Tag: para
1352
#: using-d-i.xml:1660
1412
#: using-d-i.xml:1754
1353
1413
#, no-c-format
1354
1414
msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
1355
1415
msgstr ""
1356
1416
1357
1417
#. Tag: para
1358
#: using-d-i.xml:1680
1418
#: using-d-i.xml:1774
1359
1419
#, no-c-format
1360
1420
msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
1361
1421
msgstr ""
1362
1422
1363
1423
#. Tag: term
1364
#: using-d-i.xml:1689
1424
#: using-d-i.xml:1783
1365
1425
#, no-c-format
1366
1426
msgid "Encryption: <userinput>AES256</userinput>"
1367
1427
msgstr ""
1368
1428
1369
1429
#. Tag: para
1370
#: using-d-i.xml:1691
1430
#: using-d-i.xml:1785
1371
1431
#, no-c-format
1372
1432
msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
1373
1433
msgstr ""
1374
1434
1375
1435
#. Tag: term
1376
#: using-d-i.xml:1701
1436
#: using-d-i.xml:1795
1377
1437
#, no-c-format
1378
1438
msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>"
1379
1439
msgstr ""
1380
1440
1381
1441
#. Tag: para
1382
#: using-d-i.xml:1703
1442
#: using-d-i.xml:1797
1383
1443
#, no-c-format
1384
1444
msgid "Here you can select the type of the encryption key for this partition."
1385
1445
msgstr ""
1386
1446
1387
1447
#. Tag: term
1388
#: using-d-i.xml:1709
1448
#: using-d-i.xml:1803
1389
1449
#, no-c-format
1390
1450
msgid "Keyfile (GnuPG)"
1391
1451
msgstr ""
1392
1452
1393
1453
#. Tag: para
1394
#: using-d-i.xml:1710
1454
#: using-d-i.xml:1804
1395
1455
#, no-c-format
1396
1456
msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
1397
1457
msgstr ""
1398
1458
1399
1459
#. Tag: para
1400
#: using-d-i.xml:1723
1460
#: using-d-i.xml:1817
1401
1461
#, no-c-format
1402
1462
msgid "Please see the section on random keys above."
1403
1463
msgstr ""
1404
1464
1405
1465
#. Tag: para
1406
#: using-d-i.xml:1737
1466
#: using-d-i.xml:1831
1407
1467
#, no-c-format
1408
1468
msgid "Please see the the section on erasing data above."
1409
1469
msgstr ""
1410
1470
1411
1471
#. Tag: para
1412
#: using-d-i.xml:1746
1472
#: using-d-i.xml:1840
1413
1473
#, no-c-format
1414
1474
msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
1415
1475
msgstr ""
1416
1476
1417
1477
#. Tag: para
1418
#: using-d-i.xml:1756
1478
#: using-d-i.xml:1850
1419
1479
#, no-c-format
1420
1480
msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
1421
1481
msgstr ""
1422
1482
1423
1483
#. Tag: para
1424
#: using-d-i.xml:1765
1484
#: using-d-i.xml:1859
1425
1485
#, no-c-format
1426
1486
msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
1427
1487
msgstr ""
1428
1488
1429
1489
#. Tag: para
1430
#: using-d-i.xml:1778
1490
#: using-d-i.xml:1872
1431
1491
#, no-c-format
1432
1492
msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
1433
1493
msgstr ""
1434
1494
1435
1495
#. Tag: para
1436
#: using-d-i.xml:1794
1496
#: using-d-i.xml:1888
1437
1497
#, no-c-format
1438
1498
msgid ""
1439
1499
"After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
1446
1506
msgstr ""
1447
1507
1448
1508
#. Tag: para
1449
#: using-d-i.xml:1807
1509
#: using-d-i.xml:1901
1450
1510
#, no-c-format
1451
msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
1511
msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
1452
1512
msgstr ""
1453
1513
1454
1514
#. Tag: para
1455
#: using-d-i.xml:1817
1515
#: using-d-i.xml:1911
1456
1516
#, no-c-format
1457
1517
msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
1458
1518
msgstr ""
1459
1519
1460
1520
#. Tag: title
1461
#: using-d-i.xml:1828
1521
#: using-d-i.xml:1922
1462
1522
#, no-c-format
1463
1523
msgid "Installing the Base System"
1464
1524
msgstr ""
1465
1525
1466
1526
#. Tag: para
1467
#: using-d-i.xml:1829
1527
#: using-d-i.xml:1923
1468
1528
#, no-c-format
1469
1529
msgid "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."
1470
1530
msgstr ""
1471
1531
1472
1532
#. Tag: para
1473
#: using-d-i.xml:1842
1533
#: using-d-i.xml:1936
1474
1534
#, no-c-format
1475
1535
msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
1476
1536
msgstr ""
1477
1537
1478
1538
#. Tag: para
1479
#: using-d-i.xml:1851
1539
#: using-d-i.xml:1945
1480
1540
#, no-c-format
1481
1541
msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
1482
1542
msgstr ""
1483
1543
1484
1544
#. Tag: para
1485
#: using-d-i.xml:1857
1545
#: using-d-i.xml:1951
1486
1546
#, no-c-format
1487
1547
msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
1488
1548
msgstr ""
1489
1549
1490
1550
#. Tag: title
1491
#: using-d-i.xml:1869
1551
#: using-d-i.xml:1963
1492
1552
#, no-c-format
1493
1553
msgid "Setting Up Users And Passwords"
1494
1554
msgstr ""
1495
1555
1496
1556
#. Tag: para
1497
#: using-d-i.xml:1870
1557
#: using-d-i.xml:1964
1498
1558
#, no-c-format
1499
1559
msgid "After the base system has been installed, 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."
1500
1560
msgstr ""
1501
1561
1502
1562
#. Tag: title
1503
#: using-d-i.xml:1884
1563
#: using-d-i.xml:1978
1504
1564
#, no-c-format
1505
1565
msgid "Set the Root Password"
1506
1566
msgstr ""
1507
1567
1508
1568
#. Tag: para
1509
#: using-d-i.xml:1888
1569
#: using-d-i.xml:1982
1510
1570
#, no-c-format
1511
1571
msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
1512
1572
msgstr ""
1513
1573
1514
1574
#. Tag: para
1515
#: using-d-i.xml:1896
1575
#: using-d-i.xml:1990
1516
1576
#, no-c-format
1517
1577
msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
1518
1578
msgstr ""
1519
1579
1520
1580
#. Tag: para
1521
#: using-d-i.xml:1904
1581
#: using-d-i.xml:1998
1522
1582
#, no-c-format
1523
1583
msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
1524
1584
msgstr ""
1525
1585
1526
1586
#. Tag: title
1527
#: using-d-i.xml:1914
1587
#: using-d-i.xml:2008
1528
1588
#, no-c-format
1529
1589
msgid "Create an Ordinary User"
1530
1590
msgstr ""
1531
1591
1532
1592
#. Tag: para
1533
#: using-d-i.xml:1916
1593
#: using-d-i.xml:2010
1534
1594
#, no-c-format
1535
1595
msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
1536
1596
msgstr ""
1537
1597
1538
1598
#. Tag: para
1539
#: using-d-i.xml:1925
1599
#: using-d-i.xml:2019
1540
1600
#, no-c-format
1541
1601
msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you."
1542
1602
msgstr ""
1543
1603
1544
1604
#. Tag: para
1545
#: using-d-i.xml:1935
1605
#: using-d-i.xml:2029
1546
1606
#, no-c-format
1547
1607
msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
1548
1608
msgstr ""
1549
1609
1550
1610
#. Tag: para
1551
#: using-d-i.xml:1942
1611
#: using-d-i.xml:2036
1552
1612
#, no-c-format
1553
1613
msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
1554
1614
msgstr ""
1555
1615
1556
1616
#. Tag: title
1557
#: using-d-i.xml:1953
1617
#: using-d-i.xml:2047
1558
1618
#, no-c-format
1559
1619
msgid "Installing Additional Software"
1560
1620
msgstr ""
1561
1621
1562
1622
#. Tag: para
1563
#: using-d-i.xml:1954
1623
#: using-d-i.xml:2048
1564
1624
#, no-c-format
1565
1625
msgid "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."
1566
1626
msgstr ""
1567
1627
1568
1628
#. Tag: title
1569
#: using-d-i.xml:1969
1629
#: using-d-i.xml:2063
1570
1630
#, no-c-format
1571
1631
msgid "Configuring apt"
1572
1632
msgstr ""
1573
1633
1574
1634
#. Tag: para
1575
#: using-d-i.xml:1971
1635
#: using-d-i.xml:2065
1576
1636
#, no-c-format
1577
1637
msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
1578
1638
msgstr ""
1579
1639
1580
1640
#. Tag: para
1581
#: using-d-i.xml:1995
1641
#: using-d-i.xml:2089
1582
1642
#, no-c-format
1583
1643
msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete."
1584
1644
msgstr ""
1585
1645
1586
1646
#. Tag: para
1587
#: using-d-i.xml:2002
1647
#: using-d-i.xml:2096
1588
1648
#, no-c-format
1589
1649
msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service."
1590
1650
msgstr ""
1591
1651
1592
1652
#. Tag: para
1593
#: using-d-i.xml:2011
1653
#: using-d-i.xml:2105
1594
1654
#, no-c-format
1595
1655
msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
1596
1656
msgstr ""
1597
1657
1598
1658
#. Tag: title
1599
#: using-d-i.xml:2022
1659
#: using-d-i.xml:2116
1600
1660
#, no-c-format
1601
1661
msgid "Installing from more than one CD or DVD"
1602
1662
msgstr ""
1603
1663
1604
1664
#. Tag: para
1605
#: using-d-i.xml:2024
1665
#: using-d-i.xml:2118
1606
1666
#, no-c-format
1607
1667
msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them."
1608
1668
msgstr ""
1609
1669
1610
1670
#. Tag: para
1611
#: using-d-i.xml:2031
1671
#: using-d-i.xml:2125
1612
1672
#, no-c-format
1613
1673
msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed."
1614
1674
msgstr ""
1615
1675
1616
1676
#. Tag: para
1617
#: using-d-i.xml:2039
1677
#: using-d-i.xml:2133
1618
1678
#, no-c-format
1619
1679
msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set."
1620
1680
msgstr ""
1621
1681
1622
1682
#. Tag: para
1623
#: using-d-i.xml:2046
1683
#: using-d-i.xml:2140
1624
1684
#, no-c-format
1625
1685
msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
1626
1686
msgstr ""
1627
1687
1628
1688
#. Tag: para
1629
#: using-d-i.xml:2055
1689
#: using-d-i.xml:2149
1630
1690
#, no-c-format
1631
1691
msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments."
1632
1692
msgstr ""
1633
1693
1634
1694
#. Tag: para
1635
#: using-d-i.xml:2063
1695
#: using-d-i.xml:2157
1636
1696
#, no-c-format
1637
1697
msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes."
1638
1698
msgstr ""
1639
1699
1640
1700
#. Tag: title
1641
#: using-d-i.xml:2076
1701
#: using-d-i.xml:2170
1642
1702
#, no-c-format
1643
1703
msgid "Using a network mirror"
1644
1704
msgstr ""
1645
1705
1646
1706
#. Tag: para
1647
#: using-d-i.xml:2078
1707
#: using-d-i.xml:2172
1648
1708
#, no-c-format
1649
1709
msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
1650
1710
msgstr ""
1651
1711
1652
1712
#. Tag: para
1653
#: using-d-i.xml:2084
1713
#: using-d-i.xml:2178
1654
1714
#, no-c-format
1655
1715
msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation."
1656
1716
msgstr ""
1657
1717
1658
1718
#. Tag: para
1659
#: using-d-i.xml:2093
1719
#: using-d-i.xml:2187
1660
1720
#, no-c-format
1661
1721
msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)."
1662
1722
msgstr ""
1663
1723
1664
1724
#. Tag: para
1665
#: using-d-i.xml:2104
1725
#: using-d-i.xml:2198
1666
1726
#, no-c-format
1667
1727
msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional."
1668
1728
msgstr ""
1669
1729
1670
1730
#. Tag: para
1671
#: using-d-i.xml:2111
1731
#: using-d-i.xml:2205
1672
1732
#, no-c-format
1673
1733
msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system."
1674
1734
msgstr ""
1675
1735
1676
1736
#. Tag: para
1677
#: using-d-i.xml:2118
1737
#: using-d-i.xml:2212
1678
1738
#, no-c-format
1679
1739
msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on"
1680
1740
msgstr ""
1681
1741
1682
1742
#. Tag: para
1683
#: using-d-i.xml:2127
1743
#: using-d-i.xml:2221
1684
1744
#, no-c-format
1685
1745
msgid "the tasks you select in the next step of the installation,"
1686
1746
msgstr ""
1687
1747
1688
1748
#. Tag: para
1689
#: using-d-i.xml:2132
1749
#: using-d-i.xml:2226
1690
1750
#, no-c-format
1691
1751
msgid "which packages are needed for those tasks,"
1692
1752
msgstr ""
1693
1753
1694
1754
#. Tag: para
1695
#: using-d-i.xml:2137
1755
#: using-d-i.xml:2231
1696
1756
#, no-c-format
1697
1757
msgid "which of those packages are present on the CDs or DVDs you have scanned, and"
1698
1758
msgstr ""
1699
1759
1700
1760
#. Tag: para
1701
#: using-d-i.xml:2142
1761
#: using-d-i.xml:2236
1702
1762
#, no-c-format
1703
1763
msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)."
1704
1764
msgstr ""
1705
1765
1706
1766
#. Tag: para
1707
#: using-d-i.xml:2151
1767
#: using-d-i.xml:2245
1708
1768
#, no-c-format
1709
1769
msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
1710
1770
msgstr ""
1711
1771
1712
1772
#. Tag: title
1713
#: using-d-i.xml:2167
1773
#: using-d-i.xml:2261
1714
1774
#, no-c-format
1715
1775
msgid "Selecting and Installing Software"
1716
1776
msgstr ""
1717
1777
1718
1778
#. Tag: para
1719
#: using-d-i.xml:2169
1779
#: using-d-i.xml:2263
1720
1780
#, no-c-format
1721
1781
msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks."
1722
1782
msgstr ""
1723
1783
1724
1784
#. Tag: para
1725
#: using-d-i.xml:2178
1785
#: using-d-i.xml:2272
1726
1786
#, no-c-format
1727
1787
msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
1728
1788
msgstr ""
1729
1789
1730
1790
#. Tag: para
1731
#: using-d-i.xml:2205
1791
#: using-d-i.xml:2299
1732
1792
#, no-c-format
1733
1793
msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point."
1734
1794
msgstr ""
1735
1795
1736
1796
#. Tag: para
1737
#: using-d-i.xml:2212
1797
#: using-d-i.xml:2306
1738
1798
#, no-c-format
1739
1799
msgid "Unless you are using the special KDE or Xfce CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment."
1740
1800
msgstr ""
1741
1801
1742
1802
#. Tag: para
1743
#: using-d-i.xml:2219
1803
#: using-d-i.xml:2313
1744
1804
#, no-c-format
1745
1805
msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce desktop environment can be selected by using <literal>desktop=xfce</literal>."
1746
1806
msgstr ""
1747
1807
1748
1808
#. Tag: para
1749
#: using-d-i.xml:2229
1809
#: using-d-i.xml:2323
1750
1810
#, no-c-format
1751
1811
msgid "Note that this will only work if the packages needed for KDE or Xfce are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE or Xfce this way should work fine if you are using a DVD image or any other installation method."
1752
1812
msgstr ""
1753
1813
1754
1814
#. Tag: para
1755
#: using-d-i.xml:2237
1756
#, no-c-format
1757
msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache</classname>."
1758
msgstr ""
1759
1760
#. Tag: para
1761
#: using-d-i.xml:2249
1762
#, no-c-format
1763
msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected."
1764
msgstr ""
1765
1766
#. Tag: para
1767
#: using-d-i.xml:2256
1815
#: using-d-i.xml:2331
1816
#, no-c-format
1817
msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache2</classname>."
1818
msgstr ""
1819
1820
#. Tag: para
1821
#: using-d-i.xml:2343
1822
#, no-c-format
1823
msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process."
1824
msgstr ""
1825
1826
#. Tag: para
1827
#: using-d-i.xml:2351
1768
1828
#, no-c-format
1769
1829
msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
1770
1830
msgstr ""
1771
1831
1772
1832
#. Tag: para
1773
#: using-d-i.xml:2262
1833
#: using-d-i.xml:2357
1774
1834
#, no-c-format
1775
1835
msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
1776
1836
msgstr ""
1777
1837
1778
1838
#. Tag: para
1779
#: using-d-i.xml:2271
1839
#: using-d-i.xml:2366
1780
1840
#, no-c-format
1781
1841
msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
1782
1842
msgstr ""
1783
1843
1784
#. Tag: para
1785
#: using-d-i.xml:2280
1786
#, no-c-format
1787
msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process."
1788
msgstr ""
1789
1790
1844
#. Tag: title
1791
#: using-d-i.xml:2293
1845
#: using-d-i.xml:2381
1792
1846
#, no-c-format
1793
1847
msgid "Making Your System Bootable"
1794
1848
msgstr ""
1795
1849
1796
1850
#. Tag: para
1797
#: using-d-i.xml:2295
1851
#: using-d-i.xml:2383
1798
1852
#, no-c-format
1799
1853
msgid "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>"
1800
1854
msgstr ""
1801
1855
1802
1856
#. Tag: title
1803
#: using-d-i.xml:2310
1857
#: using-d-i.xml:2398
1804
1858
#, no-c-format
1805
1859
msgid "Detecting other operating systems"
1806
1860
msgstr ""
1807
1861
1808
1862
#. Tag: para
1809
#: using-d-i.xml:2312
1863
#: using-d-i.xml:2400
1810
1864
#, no-c-format
1811
1865
msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian."
1812
1866
msgstr ""
1813
1867
1814
1868
#. Tag: para
1815
#: using-d-i.xml:2320
1869
#: using-d-i.xml:2408
1816
1870
#, no-c-format
1817
1871
msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information."
1818
1872
msgstr ""
1819
1873
1820
1874
#. Tag: title
1821
#: using-d-i.xml:2338
1875
#: using-d-i.xml:2426
1822
1876
#, no-c-format
1823
1877
msgid "Install <command>aboot</command> on a Hard Disk"
1824
1878
msgstr ""
1825
1879
1826
1880
#. Tag: para
1827
#: using-d-i.xml:2339
1881
#: using-d-i.xml:2427
1828
1882
#, no-c-format
1829
1883
msgid "If you have booted from SRM and you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead."
1830
1884
msgstr ""
1831
1885
1832
1886
#. Tag: title
1833
#: using-d-i.xml:2359
1887
#: using-d-i.xml:2447
1834
1888
#, no-c-format
1835
1889
msgid "<command>palo</command>-installer"
1836
1890
msgstr ""
1837
1891
1838
1892
#. Tag: para
1839
#: using-d-i.xml:2360
1893
#: using-d-i.xml:2448
1840
1894
#, no-c-format
1841
1895
msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
1842
1896
msgstr ""
1843
1897
1844
1898
#. Tag: para
1845
#: using-d-i.xml:2369
1899
#: using-d-i.xml:2457
1846
1900
#, no-c-format
1847
1901
msgid "hppa FIXME ( need more info )"
1848
1902
msgstr ""
1849
1903
1850
1904
#. Tag: title
1851
#: using-d-i.xml:2381
1905
#: using-d-i.xml:2469
1852
1906
#, no-c-format
1853
1907
msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
1854
1908
msgstr ""
1855
1909
1856
1910
#. Tag: para
1857
#: using-d-i.xml:2383
1911
#: using-d-i.xml:2471
1858
1912
#, no-c-format
1859
1913
msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike."
1860
1914
msgstr ""
1861
1915
1862
1916
#. Tag: para
1863
#: using-d-i.xml:2389
1917
#: using-d-i.xml:2477
1864
1918
#, no-c-format
1865
1919
msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
1866
1920
msgstr ""
1867
1921
1868
1922
#. Tag: para
1869
#: using-d-i.xml:2395
1923
#: using-d-i.xml:2483
1870
1924
#, no-c-format
1871
1925
msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
1872
1926
msgstr ""
1873
1927
1874
1928
#. Tag: title
1875
#: using-d-i.xml:2408
1929
#: using-d-i.xml:2496
1876
1930
#, no-c-format
1877
1931
msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
1878
1932
msgstr ""
1879
1933
1880
1934
#. Tag: para
1881
#: using-d-i.xml:2410
1935
#: using-d-i.xml:2498
1882
1936
#, no-c-format
1883
1937
msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
1884
1938
msgstr ""
1885
1939
1886
1940
#. Tag: para
1887
#: using-d-i.xml:2420
1941
#: using-d-i.xml:2508
1888
1942
#, no-c-format
1889
1943
msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
1890
1944
msgstr ""
1891
1945
1892
1946
#. Tag: para
1893
#: using-d-i.xml:2428
1947
#: using-d-i.xml:2516
1894
1948
#, no-c-format
1895
1949
msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
1896
1950
msgstr ""
1897
1951
1898
1952
#. Tag: term
1899
#: using-d-i.xml:2435
1953
#: using-d-i.xml:2523
1900
1954
#, no-c-format
1901
1955
msgid "Master Boot Record (MBR)"
1902
1956
msgstr ""
1903
1957
1904
1958
#. Tag: para
1905
#: using-d-i.xml:2435
1959
#: using-d-i.xml:2523
1906
1960
#, no-c-format
1907
1961
msgid "This way the <command>LILO</command> will take complete control of the boot process."
1908
1962
msgstr ""
1909
1963
1910
1964
#. Tag: term
1911
#: using-d-i.xml:2442
1965
#: using-d-i.xml:2530
1912
1966
#, no-c-format
1913
1967
msgid "new Debian partition"
1914
1968
msgstr ""
1915
1969
1916
1970
#. Tag: para
1917
#: using-d-i.xml:2442
1971
#: using-d-i.xml:2530
1918
1972
#, no-c-format
1919
1973
msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader."
1920
1974
msgstr ""
1921
1975
1922
1976
#. Tag: term
1923
#: using-d-i.xml:2451
1977
#: using-d-i.xml:2539
1924
1978
#, no-c-format
1925
1979
msgid "Other choice"
1926
1980
msgstr ""
1927
1981
1928
1982
#. Tag: para
1929
#: using-d-i.xml:2451
1983
#: using-d-i.xml:2539
1930
1984
#, no-c-format
1931
1985
msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
1932
1986
msgstr ""
1933
1987
1934
1988
#. Tag: para
1935
#: using-d-i.xml:2461
1989
#: using-d-i.xml:2549
1936
1990
#, no-c-format
1937
1991
msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into Debian!"
1938
1992
msgstr ""
1939
1993
1940
1994
#. Tag: title
1941
#: using-d-i.xml:2477
1995
#: using-d-i.xml:2565
1942
1996
#, no-c-format
1943
1997
msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
1944
1998
msgstr ""
1945
1999
1946
2000
#. Tag: para
1947
#: using-d-i.xml:2479
2001
#: using-d-i.xml:2567
1948
2002
#, no-c-format
1949
2003
msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
1950
2004
msgstr ""
1951
2005
1952
2006
#. Tag: para
1953
#: using-d-i.xml:2495
2007
#: using-d-i.xml:2583
1954
2008
#, no-c-format
1955
2009
msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
1956
2010
msgstr ""
1957
2011
1958
2012
#. Tag: title
1959
#: using-d-i.xml:2507
2013
#: using-d-i.xml:2595
1960
2014
#, no-c-format
1961
2015
msgid "Choose the correct partition!"
1962
2016
msgstr ""
1963
2017
1964
2018
#. Tag: para
1965
#: using-d-i.xml:2509
2019
#: using-d-i.xml:2597
1966
2020
#, no-c-format
1967
2021
msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
1968
2022
msgstr ""
1969
2023
1970
2024
#. Tag: title
1971
#: using-d-i.xml:2524
2025
#: using-d-i.xml:2612
1972
2026
#, no-c-format
1973
2027
msgid "EFI Partition Contents"
1974
2028
msgstr ""
1975
2029
1976
2030
#. Tag: para
1977
#: using-d-i.xml:2526
2031
#: using-d-i.xml:2614
1978
2032
#, no-c-format
1979
2033
msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
1980
2034
msgstr ""
1981
2035
1982
2036
#. Tag: filename
1983
#: using-d-i.xml:2548
2037
#: using-d-i.xml:2636
1984
2038
#, no-c-format
1985
2039
msgid "elilo.conf"
1986
2040
msgstr ""
1987
2041
1988
2042
#. Tag: para
1989
#: using-d-i.xml:2549
2043
#: using-d-i.xml:2637
1990
2044
#, no-c-format
1991
2045
msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
1992
2046
msgstr ""
1993
2047
1994
2048
#. Tag: filename
1995
#: using-d-i.xml:2558
2049
#: using-d-i.xml:2646
1996
2050
#, no-c-format
1997
2051
msgid "elilo.efi"
1998
2052
msgstr ""
1999
2053
2000
2054
#. Tag: para
2001
#: using-d-i.xml:2559
2055
#: using-d-i.xml:2647
2002
2056
#, no-c-format
2003
2057
msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
2004
2058
msgstr ""
2005
2059
2006
2060
#. Tag: filename
2007
#: using-d-i.xml:2569
2061
#: using-d-i.xml:2657
2008
2062
#, no-c-format
2009
2063
msgid "initrd.img"
2010
2064
msgstr ""
2011
2065
2012
2066
#. Tag: para
2013
#: using-d-i.xml:2570
2067
#: using-d-i.xml:2658
2014
2068
#, no-c-format
2015
2069
msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
2016
2070
msgstr ""
2017
2071
2018
2072
#. Tag: filename
2019
#: using-d-i.xml:2582
2073
#: using-d-i.xml:2670
2020
2074
#, no-c-format
2021
2075
msgid "readme.txt"
2022
2076
msgstr ""
2023
2077
2024
2078
#. Tag: para
2025
#: using-d-i.xml:2583
2079
#: using-d-i.xml:2671
2026
2080
#, no-c-format
2027
2081
msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
2028
2082
msgstr ""
2029
2083
2030
2084
#. Tag: filename
2031
#: using-d-i.xml:2593
2085
#: using-d-i.xml:2681
2032
2086
#, no-c-format
2033
2087
msgid "vmlinuz"
2034
2088
msgstr ""
2035
2089
2036
2090
#. Tag: para
2037
#: using-d-i.xml:2594
2091
#: using-d-i.xml:2682
2038
2092
#, no-c-format
2039
2093
msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
2040
2094
msgstr ""
2041
2095
2042
2096
#. Tag: title
2043
#: using-d-i.xml:2614
2097
#: using-d-i.xml:2702
2044
2098
#, no-c-format
2045
2099
msgid "<command>arcboot</command>-installer"
2046
2100
msgstr ""
2047
2101
2048
2102
#. Tag: para
2049
#: using-d-i.xml:2615
2103
#: using-d-i.xml:2703
2050
2104
#, no-c-format
2051
2105
msgid ""
2052
2106
"The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
2059
2113
msgstr ""
2060
2114
2061
2115
#. Tag: replaceable
2062
#: using-d-i.xml:2634
2116
#: using-d-i.xml:2722
2063
2117
#, no-c-format
2064
2118
msgid "scsi"
2065
2119
msgstr ""
2066
2120
2067
2121
#. Tag: para
2068
#: using-d-i.xml:2635
2122
#: using-d-i.xml:2723
2069
2123
#, no-c-format
2070
2124
msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
2071
2125
msgstr ""
2072
2126
2073
2127
#. Tag: replaceable
2074
#: using-d-i.xml:2643
2128
#: using-d-i.xml:2731
2075
2129
#, no-c-format
2076
2130
msgid "disk"
2077
2131
msgstr ""
2078
2132
2079
2133
#. Tag: para
2080
#: using-d-i.xml:2644
2134
#: using-d-i.xml:2732
2081
2135
#, no-c-format
2082
2136
msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
2083
2137
msgstr ""
2084
2138
2085
2139
#. Tag: replaceable
2086
#: using-d-i.xml:2652 using-d-i.xml:2721
2140
#: using-d-i.xml:2740
2087
2141
#, no-c-format
2088
2142
msgid "partnr"
2089
2143
msgstr ""
2090
2144
2091
2145
#. Tag: para
2092
#: using-d-i.xml:2653
2146
#: using-d-i.xml:2741
2093
2147
#, no-c-format
2094
2148
msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
2095
2149
msgstr ""
2096
2150
2097
2151
#. Tag: replaceable
2098
#: using-d-i.xml:2661
2152
#: using-d-i.xml:2749
2099
2153
#, no-c-format
2100
2154
msgid "config"
2101
2155
msgstr ""
2102
2156
2103
2157
#. Tag: para
2104
#: using-d-i.xml:2662
2158
#: using-d-i.xml:2750
2105
2159
#, no-c-format
2106
2160
msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
2107
2161
msgstr ""
2108
2162
2109
2163
#. Tag: title
2110
#: using-d-i.xml:2683
2111
#, no-c-format
2112
msgid "<command>delo</command>-installer"
2113
msgstr ""
2114
2115
#. Tag: para
2116
#: using-d-i.xml:2684
2117
#, no-c-format
2118
msgid ""
2119
"The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n"
2120
"<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput>\n"
2121
"</screen></informalexample> on the firmware prompt."
2122
msgstr ""
2123
2124
#. Tag: replaceable
2125
#: using-d-i.xml:2703
2126
#, no-c-format
2127
msgid "<replaceable>#</replaceable>"
2128
msgstr ""
2129
2130
#. Tag: para
2131
#: using-d-i.xml:2704
2132
#, no-c-format
2133
msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers"
2134
msgstr ""
2135
2136
#. Tag: replaceable
2137
#: using-d-i.xml:2712
2138
#, no-c-format
2139
msgid "<replaceable>id</replaceable>"
2140
msgstr ""
2141
2142
#. Tag: para
2143
#: using-d-i.xml:2713
2144
#, no-c-format
2145
msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed"
2146
msgstr ""
2147
2148
#. Tag: para
2149
#: using-d-i.xml:2722
2150
#, no-c-format
2151
msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides"
2152
msgstr ""
2153
2154
#. Tag: replaceable
2155
#: using-d-i.xml:2730
2156
#, no-c-format
2157
msgid "name"
2158
msgstr ""
2159
2160
#. Tag: para
2161
#: using-d-i.xml:2731
2162
#, no-c-format
2163
msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default."
2164
msgstr ""
2165
2166
#. Tag: para
2167
#: using-d-i.xml:2741
2168
#, no-c-format
2169
msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use"
2170
msgstr ""
2171
2172
#. Tag: screen
2173
#: using-d-i.xml:2747
2174
#, no-c-format
2175
msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>"
2176
msgstr ""
2177
2178
#. Tag: title
2179
#: using-d-i.xml:2757
2164
#: using-d-i.xml:2771
2180
2165
#, no-c-format
2181
2166
msgid "Install <command>Yaboot</command> on a Hard Disk"
2182
2167
msgstr ""
2183
2168
2184
2169
#. Tag: para
2185
#: using-d-i.xml:2758
2170
#: using-d-i.xml:2772
2186
2171
#, no-c-format
2187
2172
msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;."
2188
2173
msgstr ""
2189
2174
2190
2175
#. Tag: title
2191
#: using-d-i.xml:2776
2176
#: using-d-i.xml:2790
2192
2177
#, no-c-format
2193
2178
msgid "Install <command>Quik</command> on a Hard Disk"
2194
2179
msgstr ""
2195
2180
2196
2181
#. Tag: para
2197
#: using-d-i.xml:2777
2182
#: using-d-i.xml:2791
2198
2183
#, no-c-format
2199
2184
msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
2200
2185
msgstr ""
2201
2186
2202
2187
#. Tag: title
2203
#: using-d-i.xml:2793
2188
#: using-d-i.xml:2807
2204
2189
#, no-c-format
2205
2190
msgid "<command>zipl</command>-installer"
2206
2191
msgstr ""
2207
2192
2208
2193
#. Tag: para
2209
#: using-d-i.xml:2794
2194
#: using-d-i.xml:2808
2210
2195
#, no-c-format
2211
2196
msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
2212
2197
msgstr ""
2213
2198
2214
2199
#. Tag: title
2215
#: using-d-i.xml:2811
2200
#: using-d-i.xml:2825
2216
2201
#, no-c-format
2217
2202
msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
2218
2203
msgstr ""
2219
2204
2220
2205
#. Tag: para
2221
#: using-d-i.xml:2813
2206
#: using-d-i.xml:2827
2222
2207
#, no-c-format
2223
2208
msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
2224
2209
msgstr ""
2225
2210
2226
2211
#. Tag: title
2227
#: using-d-i.xml:2838
2212
#: using-d-i.xml:2852
2228
2213
#, no-c-format
2229
2214
msgid "Continue Without Boot Loader"
2230
2215
msgstr ""
2231
2216
2232
2217
#. Tag: para
2233
#: using-d-i.xml:2840
2218
#: using-d-i.xml:2854
2234
2219
#, no-c-format
2235
2220
msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>"
2236
2221
msgstr ""
2237
2222
2238
2223
#. Tag: para
2239
#: using-d-i.xml:2849
2224
#: using-d-i.xml:2863
2240
2225
#, no-c-format
2241
2226
msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
2242
2227
msgstr ""
2243
2228
2244
2229
#. Tag: title
2245
#: using-d-i.xml:2866
2230
#: using-d-i.xml:2880
2246
2231
#, no-c-format
2247
2232
msgid "Finishing the Installation"
2248
2233
msgstr ""
2249
2234
2250
2235
#. Tag: para
2251
#: using-d-i.xml:2867
2236
#: using-d-i.xml:2881
2252
2237
#, no-c-format
2253
2238
msgid "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;."
2254
2239
msgstr ""
2255
2240
2256
2241
#. Tag: title
2257
#: using-d-i.xml:2880
2242
#: using-d-i.xml:2894
2258
2243
#, no-c-format
2259
2244
msgid "Setting the System Clock"
2260
2245
msgstr ""
2261
2246
2262
2247
#. Tag: para
2263
#: using-d-i.xml:2882
2248
#: using-d-i.xml:2896
2264
2249
#, no-c-format
2265
2250
msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
2266
2251
msgstr ""
2267
2252
2268
2253
#. Tag: para
2269
#: using-d-i.xml:2889
2254
#: using-d-i.xml:2903
2270
2255
#, no-c-format
2271
2256
msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>"
2272
2257
msgstr ""
2273
2258
2274
2259
#. Tag: para
2275
#: using-d-i.xml:2900
2260
#: using-d-i.xml:2914
2276
2261
#, no-c-format
2277
2262
msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
2278
2263
msgstr ""
2279
2264
2280
2265
#. Tag: title
2281
#: using-d-i.xml:2915
2266
#: using-d-i.xml:2929
2282
2267
#, no-c-format
2283
2268
msgid "Reboot the System"
2284
2269
msgstr ""
2285
2270
2286
2271
#. Tag: para
2287
#: using-d-i.xml:2917
2272
#: using-d-i.xml:2931
2288
2273
#, no-c-format
2289
2274
msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new Debian system."
2290
2275
msgstr ""
2291
2276
2292
2277
#. Tag: para
2293
#: using-d-i.xml:2923
2278
#: using-d-i.xml:2937
2294
2279
#, no-c-format
2295
2280
msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian; from the DASD which you selected for the root filesystem during the first steps of the installation."
2296
2281
msgstr ""
2297
2282
2298
2283
#. Tag: title
2299
#: using-d-i.xml:2936
2284
#: using-d-i.xml:2950
2300
2285
#, no-c-format
2301
2286
msgid "Miscellaneous"
2302
2287
msgstr ""
2303
2288
2304
2289
#. Tag: para
2305
#: using-d-i.xml:2937
2290
#: using-d-i.xml:2951
2306
2291
#, no-c-format
2307
2292
msgid "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."
2308
2293
msgstr ""
2309
2294
2310
2295
#. Tag: title
2311
#: using-d-i.xml:2950
2296
#: using-d-i.xml:2964
2312
2297
#, no-c-format
2313
2298
msgid "Saving the installation logs"
2314
2299
msgstr ""
2315
2300
2316
2301
#. Tag: para
2317
#: using-d-i.xml:2952
2302
#: using-d-i.xml:2966
2318
2303
#, no-c-format
2319
2304
msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system."
2320
2305
msgstr ""
2321
2306
2322
2307
#. Tag: para
2323
#: using-d-i.xml:2959
2308
#: using-d-i.xml:2973
2324
2309
#, no-c-format
2325
2310
msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
2326
2311
msgstr ""
2327
2312
2328
2313
#. Tag: title
2329
#: using-d-i.xml:2979
2314
#: using-d-i.xml:2993
2330
2315
#, no-c-format
2331
2316
msgid "Using the Shell and Viewing the Logs"
2332
2317
msgstr ""
2333
2318
2334
2319
#. Tag: para
2335
#: using-d-i.xml:2981
2320
#: using-d-i.xml:2995
2336
2321
#, no-c-format
2337
msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself."
2322
msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to the installer itself."
2338
2323
msgstr ""
2339
2324
2340
2325
#. Tag: para
2341
#: using-d-i.xml:2999
2326
#: using-d-i.xml:3013
2342
2327
#, no-c-format
2343
2328
msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>."
2344
2329
msgstr ""
2345
2330
2346
2331
#. Tag: para
2347
#: using-d-i.xml:3003
2332
#: using-d-i.xml:3017
2348
2333
#, no-c-format
2349
2334
msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
2350
2335
msgstr ""
2351
2336
2352
2337
#. Tag: para
2353
#: using-d-i.xml:3011
2338
#: using-d-i.xml:3025
2354
2339
#, no-c-format
2355
2340
msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
2356
2341
msgstr ""
2357
2342
2358
2343
#. Tag: para
2359
#: using-d-i.xml:3020
2344
#: using-d-i.xml:3034
2360
2345
#, no-c-format
2361
2346
msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
2362
2347
msgstr ""
2363
2348
2364
2349
#. Tag: para
2365
#: using-d-i.xml:3027
2350
#: using-d-i.xml:3041
2366
2351
#, no-c-format
2367
2352
msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
2368
2353
msgstr ""
2369
2354
2370
2355
#. Tag: para
2371
#: using-d-i.xml:3033
2356
#: using-d-i.xml:3047
2372
2357
#, no-c-format
2373
2358
msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
2374
2359
msgstr ""
2375
2360
2376
2361
#. Tag: title
2377
#: using-d-i.xml:3048
2362
#: using-d-i.xml:3062
2378
2363
#, no-c-format
2379
2364
msgid "Installation Over the Network"
2380
2365
msgstr ""
2381
2366
2382
2367
#. Tag: para
2383
#: using-d-i.xml:3050
2368
#: using-d-i.xml:3064
2384
2369
#, no-c-format
2385
2370
msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
2386
2371
msgstr ""
2387
2372
2388
2373
#. Tag: para
2389
#: using-d-i.xml:3060
2374
#: using-d-i.xml:3074
2390
2375
#, no-c-format
2391
2376
msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
2392
2377
msgstr ""
2393
2378
2394
2379
#. Tag: para
2395
#: using-d-i.xml:3073
2380
#: using-d-i.xml:3087
2396
2381
#, no-c-format
2397
2382
msgid "For installations on &arch-title;, this is the default method after setting up the network."
2398
2383
msgstr ""
2399
2384
2400
2385
#. Tag: para
2401
#: using-d-i.xml:3078
2386
#: using-d-i.xml:3092
2402
2387
#, no-c-format
2403
2388
msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>."
2404
2389
msgstr ""
2405
2390
2406
2391
#. Tag: para
2407
#: using-d-i.xml:3090
2392
#: using-d-i.xml:3104
2408
2393
#, no-c-format
2409
2394
msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
2410
2395
msgstr ""
2411
2396
2412
2397
#. Tag: para
2413
#: using-d-i.xml:3096
2398
#: using-d-i.xml:3110
2414
2399
#, no-c-format
2415
2400
msgid ""
2416
2401
"Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n"
2419
2404
msgstr ""
2420
2405
2421
2406
#. Tag: para
2422
#: using-d-i.xml:3113
2407
#: using-d-i.xml:3127
2423
2408
#, no-c-format
2424
2409
msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations — depending on your local network setup — the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting."
2425
2410
msgstr ""
2426
2411
2427
2412
#. Tag: para
2428
#: using-d-i.xml:3126
2413
#: using-d-i.xml:3140
2429
2414
#, no-c-format
2430
2415
msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed."
2431
2416
msgstr ""
2432
2417
2433
2418
#. Tag: para
2434
#: using-d-i.xml:3139
2419
#: using-d-i.xml:3153
2435
2420
#, no-c-format
2436
2421
msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R <<replaceable>hostname</replaceable>|<replaceable>IP address</replaceable>></command>. </para> </footnote> and try again."
2437
2422
msgstr ""
2438
2423
2439
2424
#. Tag: para
2440
#: using-d-i.xml:3155
2425
#: using-d-i.xml:3169
2441
2426
#, no-c-format
2442
2427
msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
2443
2428
msgstr ""
2444
2429
2445
2430
#. Tag: para
2446
#: using-d-i.xml:3165
2431
#: using-d-i.xml:3179
2447
2432
#, no-c-format
2448
2433
msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
2449
2434
msgstr ""
2450
2435
2451
#. Tag: para
2452
#: using-d-i.xml:3173
2453
#, no-c-format
2454
msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated."
2436
#. Tag: title
2437
#: using-d-i.xml:3199
2438
#, no-c-format
2439
msgid "Loading Missing Firmware"
2440
msgstr ""
2441
2442
#. Tag: para
2443
#: using-d-i.xml:3200
2444
#, no-c-format
2445
msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features."
2446
msgstr ""
2447
2448
#. Tag: para
2449
#: using-d-i.xml:3208
2450
#, no-c-format
2451
msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded."
2452
msgstr ""
2453
2454
#. Tag: para
2455
#: using-d-i.xml:3218
2456
#, no-c-format
2457
msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>"
2458
msgstr ""
2459
2460
#. Tag: para
2461
#: using-d-i.xml:3228
2462
#, no-c-format
2463
msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
2464
msgstr ""
2465
2466
#. Tag: para
2467
#: using-d-i.xml:3235
2468
#, no-c-format
2469
msgid "Support for loading firmware is still relatively basic and is likely to be improved in future releases of the installer. Currently &d-i; will for example not display any warning if you choose to load missing firmware, but the requested firmware is not found. Please report any issues you encounter by filing an installation report (see <xref linkend=\"submit-bug\"/>)."
2470
msgstr ""
2471
2472
#. Tag: title
2473
#: using-d-i.xml:3246
2474
#, no-c-format
2475
msgid "Preparing a medium"
2476
msgstr ""
2477
2478
#. Tag: para
2479
#: using-d-i.xml:3247
2480
#, no-c-format
2481
msgid "Although in some cases the firmware can also be loaded from a partition on a hard disk, the most common method to load firmware will be from some removable medium such as a floppy disk or a USB stick. The firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
2482
msgstr ""
2483
2484
#. Tag: para
2485
#: using-d-i.xml:3257
2486
#, no-c-format
2487
msgid "Tarballs containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball for the correct release and unpack it to the file system on the medium."
2488
msgstr ""
2489
2490
#. Tag: para
2491
#: using-d-i.xml:3271
2492
#, no-c-format
2493
msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
2494
msgstr ""
2495
2496
#. Tag: para
2497
#: using-d-i.xml:3285
2498
#, no-c-format
2499
msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
2500
msgstr ""
2501
2502
#. Tag: title
2503
#: using-d-i.xml:3294
2504
#, no-c-format
2505
msgid "Firmware and the Installed System"
2506
msgstr ""
2507
2508
#. Tag: para
2509
#: using-d-i.xml:3295
2510
#, no-c-format
2511
msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
2512
msgstr ""
2513
2514
#. Tag: para
2515
#: using-d-i.xml:3304
2516
#, no-c-format
2517
msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
2518
msgstr ""
2519
2520
#. Tag: para
2521
#: using-d-i.xml:3312
2522
#, no-c-format
2523
msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
2524
msgstr ""
2525
2526
#. Tag: para
2527
#: using-d-i.xml:3319
2528
#, no-c-format
2529
msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
2455
2530
msgstr ""
2456
2531
Loggerhead is a web-based interface for Breezy
Version: 2.0.1