summaryrefslogtreecommitdiff
path: root/po/hu/boot-new.po
blob: 2a714d00dfe77da98851f0e428cba2d22b3acfc2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
# Hungarian translation of Debian Installation Guide boot-new
# SZERVÁC Attila <sas@321.hu>, 2006.
#
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
"POT-Creation-Date: 2006-09-15 18:50+0000\n"
"PO-Revision-Date: 2006-09-13 00:00+0100\n"
"Last-Translator: SZERVÁC Attila <sas@321.hu>\n"
"Language-Team: Hungarian <debian-l10n-hungarian@lists.debian>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Poedit-Language: Hungarian\n"
"X-Poedit-Country: HUNGARY\n"

#. Tag: title
#: boot-new.xml:5
#, no-c-format
msgid "Booting Into Your New Debian System"
msgstr "Az új Debian rendszer indítása"

#. Tag: title
#: boot-new.xml:7
#, no-c-format
msgid "The Moment of Truth"
msgstr "Az igazság pillanata"

#. Tag: para
#: boot-new.xml:8
#, no-c-format
msgid ""
"Your system's first boot on its own power is what electrical engineers call "
"the <quote>smoke test</quote>."
msgstr ""
"A rendszer 1. önálló indítása olyasmi, amit a mérnökök úgy hívnak: "
"<quote>tűzpróba</quote>."

#. Tag: para
#: boot-new.xml:13
#, no-c-format
msgid ""
"If you are booting directly into Debian, and the system doesn't start up, "
"either use your original installation boot media, or insert the custom boot "
"floppy if you have one, and reset your system. This way, you will probably "
"need to add some boot arguments like <userinput>root=<replaceable>root</"
"replaceable></userinput>, where <replaceable>root</replaceable> is your root "
"partition, such as <filename>/dev/sda1</filename>. Alternatively, see <xref "
"linkend=\"rescue\"/> for instructions on using the installer's built-in "
"rescue mode."
msgstr ""
"Ha kiválasztottad a Debian indítását, és a rendszer mégsem indul, "
"használhatod a telepítő médiát vagy flopit. Ekkor valószínűleg meg kell "
"adnod 1-2 indítási argumentumot, leginkább egy ilyet: "
"<userinput>root=<replaceable>gyökér</replaceable></userinput>, where "
"<replaceable>gyökér</replaceable> a telepített rendszer gyökér-partíciója, "
"például <filename>/dev/sda1</filename>. Módfelett ajánljuk, olvasd el a "
"<xref linkend=\"rescue\"/> részt a telepítő beépített mentő módja "
"lehetőségeinek ismertetéséért."

#. Tag: title
#: boot-new.xml:27
#, no-c-format
msgid "BVME 6000 Booting"
msgstr ""

#. Tag: para
#: boot-new.xml:28
#, no-c-format
msgid ""
"If you have just performed a diskless install on a BVM or Motorola VMEbus "
"machine: once the system has loaded the <command>tftplilo</command> program "
"from the TFTP server, from the <prompt>LILO Boot:</prompt> prompt enter one "
"of:"
msgstr ""

#. Tag: para
#: boot-new.xml:36
#, no-c-format
msgid ""
"<userinput>b6000</userinput> followed by &enterkey; to boot a BVME 4000/6000"
msgstr ""

#. Tag: para
#: boot-new.xml:41
#, no-c-format
msgid "<userinput>b162</userinput> followed by &enterkey; to boot an MVME162"
msgstr ""

#. Tag: para
#: boot-new.xml:46
#, no-c-format
msgid ""
"<userinput>b167</userinput> followed by &enterkey; to boot an MVME166/167"
msgstr ""

#. Tag: title
#: boot-new.xml:58
#, no-c-format
msgid "Macintosh Booting"
msgstr ""

#. Tag: para
#: boot-new.xml:60
#, no-c-format
msgid ""
"Go to the directory containing the installation files and start up the "
"<command>Penguin</command> booter, holding down the <keycap>command</keycap> "
"key. Go to the <userinput>Settings</userinput> dialogue (<keycombo> "
"<keycap>command</keycap> <keycap>T</keycap> </keycombo>), and locate the "
"kernel options line which should look like <userinput>root=/dev/ram "
"video=font:VGA8x16</userinput> or similar."
msgstr ""

#. Tag: para
#: boot-new.xml:70
#, no-c-format
msgid ""
"You need to change the entry to <userinput>root=/dev/<replaceable>yyyy</"
"replaceable></userinput>. Replace the <replaceable>yyyy</replaceable> with "
"the Linux name of the partition onto which you installed the system (e.g. "
"<filename>/dev/sda1</filename>); you wrote this down earlier. The "
"<userinput>video=font:VGA8x8</userinput> is recommended especially for users "
"with tiny screens. The kernel would pick a prettier (6x11) font but the "
"console driver for this font can hang the machine, so using 8x16 or 8x8 is "
"safer at this stage. You can change this at any time."
msgstr ""

#. Tag: para
#: boot-new.xml:83
#, no-c-format
msgid ""
"If you don't want to start GNU/Linux immediately each time you start, "
"uncheck the <userinput>Auto Boot</userinput> option. Save your settings in "
"the <filename>Prefs</filename> file using the <userinput>Save Settings As "
"Default</userinput> option."
msgstr ""

#. Tag: para
#: boot-new.xml:90
#, no-c-format
msgid ""
"Now select <userinput>Boot Now</userinput> (<keycombo> <keycap>command</"
"keycap> <keycap>B</keycap> </keycombo>) to start your freshly installed GNU/"
"Linux instead of the RAMdisk installer system."
msgstr ""

#. Tag: para
#: boot-new.xml:96
#, no-c-format
msgid ""
"Debian should boot, and you should see the same messages as when you first "
"booted the installation system, followed by some new messages."
msgstr ""

#. Tag: title
#: boot-new.xml:106
#, no-c-format
msgid "OldWorld PowerMacs"
msgstr ""

#. Tag: para
#: boot-new.xml:107
#, no-c-format
msgid ""
"If the machine fails to boot after completing the installation, and stops "
"with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</"
"userinput> followed by &enterkey;. (The default boot configuration in "
"<filename>quik.conf</filename> is labeled Linux). The labels defined in "
"<filename>quik.conf</filename> will be displayed if you press the "
"<keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also "
"try booting back into the installer, and editing the <filename>/target/etc/"
"quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard "
"Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are "
"available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>."
msgstr ""

#. Tag: para
#: boot-new.xml:121
#, no-c-format
msgid ""
"To boot back into MacOS without resetting the nvram, type <userinput>bye</"
"userinput> at the OpenFirmware prompt (assuming MacOS has not been removed "
"from the machine). To obtain an OpenFirmware prompt, hold down the "
"<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</"
"keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. "
"If you need to reset the OpenFirmware nvram changes to the MacOS default in "
"order to boot back to MacOS, hold down the <keycombo> <keycap>command</"
"keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </"
"keycombo> keys while cold booting the machine."
msgstr ""

#. Tag: para
#: boot-new.xml:134
#, no-c-format
msgid ""
"If you use <command>BootX</command> to boot into the installed system, just "
"select your desired kernel in the <filename>Linux Kernels</filename> folder, "
"un-choose the ramdisk option, and add a root device corresponding to your "
"installation; e.g. <userinput>/dev/hda8</userinput>."
msgstr ""

#. Tag: title
#: boot-new.xml:146
#, no-c-format
msgid "NewWorld PowerMacs"
msgstr ""

#. Tag: para
#: boot-new.xml:147
#, no-c-format
msgid ""
"On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key "
"and get a graphical screen with a button for each bootable OS, &debian; will "
"be a button with a small penguin icon."
msgstr ""

#. Tag: para
#: boot-new.xml:154
#, no-c-format
msgid ""
"If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-"
"device</envar> variable you should reset OpenFirmware to its default "
"configuration. To do this hold down the <keycombo> <keycap>command</keycap> "
"<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> "
"keys while cold booting the machine."
msgstr ""

#. Tag: para
#: boot-new.xml:162
#, no-c-format
msgid ""
"The labels defined in <filename>yaboot.conf</filename> will be displayed if "
"you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt."
msgstr ""

#. Tag: para
#: boot-new.xml:168
#, no-c-format
msgid ""
"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian; "
"by default (if you correctly partitioned and placed the Apple_Bootstrap "
"partition first). If you have &debian; on a SCSI disk and MacOS on an IDE "
"disk this may not work and you will have to enter OpenFirmware and set the "
"<envar>boot-device</envar> variable, <command>ybin</command> normally does "
"this automatically."
msgstr ""

#. Tag: para
#: boot-new.xml:177
#, no-c-format
msgid ""
"After you boot &debian; for the first time you can add any additional "
"options you desire (such as dual boot options) to <filename>/etc/yaboot."
"conf</filename> and run <command>ybin</command> to update your boot "
"partition with the changed configuration. Please read the <ulink url=\"&url-"
"powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information."
msgstr ""

#. Tag: title
#: boot-new.xml:195
#, no-c-format
msgid "Mounting encrypted volumes"
msgstr ""

#. Tag: para
#: boot-new.xml:197
#, no-c-format
msgid ""
"If you created encrypted volumes during the installation and assigned them "
"mount points, you will be asked to enter the passphrase for each of these "
"volumes during the boot. The actual procedure differs slightly between dm-"
"crypt and loop-AES."
msgstr ""

#. Tag: title
#: boot-new.xml:207
#, no-c-format
msgid "dm-crypt"
msgstr ""

#. Tag: para
#: boot-new.xml:209
#, no-c-format
msgid ""
"For partitions encrypted using dm-crypt you will be shown the following "
"prompt during the boot: <informalexample><screen>\n"
"Starting early crypto disks... crypt<replaceable>X</replaceable>(starting)\n"
"Enter LUKS passphrase:\n"
"</screen></informalexample> In the first line of the prompt, <replaceable>X</"
"replaceable> is the number of the loop device. You are now probably "
"wondering <emphasis>for which volume</emphasis> you are actually entering "
"the passphrase. Does it relate to your <filename>/home</filename>? Or to "
"<filename>/var</filename>? Of course, if you have just one encrypted volume, "
"this is easy and you can just enter the passphrase you used when setting up "
"this volume. If you set up more than one encrypted volume during the "
"installation, the notes you wrote down as the last step in <xref linkend="
"\"partman-crypto\"/> come in handy. If you did not make a note of the "
"mapping between <filename>crypt<replaceable>X</replaceable></filename> and "
"the mount points before, you can still find it in <filename>/etc/crypttab</"
"filename> and <filename>/etc/fstab</filename> of your new system."
msgstr ""

#. Tag: para
#: boot-new.xml:231
#, no-c-format
msgid ""
"The prompt may look somewhat different when an encrypted root file system is "
"mounted. This depends on which initramfs generator was used to generate the "
"initrd used to boot the system. The example below is for an initrd generated "
"using <classname>initramfs-tools</classname>:"
msgstr ""

#. Tag: screen
#: boot-new.xml:238
#, no-c-format
msgid ""
"Begin: Mounting <emphasis>root file system</emphasis>... ...\n"
"Begin: Running /scripts/local-top ...\n"
"Enter LUKS passphrase:"
msgstr ""

#. Tag: para
#: boot-new.xml:240 boot-new.xml:265
#, no-c-format
msgid ""
"No characters (even asterisks) will be shown while entering the passphrase. "
"If you enter the wrong passphrase, you have two more tries to correct it. "
"After the third try the boot process will skip this volume and continue to "
"mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting"
"\"/> for further information."
msgstr ""

#. Tag: para
#: boot-new.xml:248 boot-new.xml:273
#, no-c-format
msgid "After entering all passphrases the boot should continue as usual."
msgstr ""

#. Tag: title
#: boot-new.xml:256
#, no-c-format
msgid "loop-AES"
msgstr ""

#. Tag: para
#: boot-new.xml:258
#, no-c-format
msgid ""
"For partitions encrypted using loop-AES you will be shown the following "
"prompt during the boot:"
msgstr ""

#. Tag: screen
#: boot-new.xml:263
#, no-c-format
msgid ""
"Checking loop-encrypted file systems.\n"
"Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</"
"replaceable>)\n"
"Password:"
msgstr ""

#. Tag: title
#: boot-new.xml:281
#, no-c-format
msgid "Troubleshooting"
msgstr ""

#. Tag: para
#: boot-new.xml:283
#, no-c-format
msgid ""
"If some of the encrypted volumes could not be mounted because a wrong "
"passphrase was entered, you will have to mount them manually after the boot. "
"There are several cases."
msgstr ""

#. Tag: para
#: boot-new.xml:292
#, no-c-format
msgid ""
"The first case concerns the root partition. When it is not mounted "
"correctly, the boot process will halt and you will have to reboot the "
"computer to try again."
msgstr ""

#. Tag: para
#: boot-new.xml:299
#, no-c-format
msgid ""
"The easiest case is for encrypted volumes holding data like <filename>/home</"
"filename> or <filename>/srv</filename>. You can simply mount them manually "
"after the boot. For loop-AES this is one-step operation: "
"<informalexample><screen>\n"
"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
"userinput>\n"
"<prompt>Password:</prompt>\n"
"</screen></informalexample> where <replaceable>/mount_point</replaceable> "
"should be replaced by the particular directory (e.g. <filename>/home</"
"filename>). The only difference from an ordinary mount is that you will be "
"asked to enter the passphrase for this volume."
msgstr ""

#. Tag: para
#: boot-new.xml:313
#, no-c-format
msgid ""
"For dm-crypt this is a bit trickier. First you need to register the volumes "
"with <application>device mapper</application> by running: "
"<informalexample><screen>\n"
"<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n"
"</screen></informalexample> This will scan all volumes mentioned in "
"<filename>/etc/crypttab</filename> and will create appropriate devices under "
"the <filename>/dev</filename> directory after entering the correct "
"passphrases. (Already registered volumes will be skipped, so you can repeat "
"this command several times without worrying.) After successful registration "
"you can simply mount the volumes the usual way:"
msgstr ""

#. Tag: screen
#: boot-new.xml:328
#, no-c-format
msgid ""
"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></"
"userinput>"
msgstr ""

#. Tag: para
#: boot-new.xml:331
#, no-c-format
msgid ""
"If any volume holding noncritical system files could not be mounted "
"(<filename>/usr</filename> or <filename>/var</filename>), the system should "
"still boot and you should be able to mount the volumes manually like in the "
"previous case. However, you will also need to (re)start any services usually "
"running in your default runlevel because it is very likely that they were "
"not started. The easiest way to achieve this is by switching to the first "
"runlevel and back by entering <informalexample><screen>\n"
"<prompt>#</prompt> <userinput>init 1</userinput>\n"
"</screen></informalexample> at the shell prompt and pressing <keycombo> "
"<keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for the "
"root password."
msgstr ""

#. Tag: title
#: boot-new.xml:354
#, no-c-format
msgid "Log In"
msgstr ""

#. Tag: para
#: boot-new.xml:356
#, no-c-format
msgid ""
"Once your system boots, you'll be presented with the login prompt. Log in "
"using the personal login and password you selected during the installation "
"process. Your system is now ready to use."
msgstr ""

#. Tag: para
#: boot-new.xml:362
#, no-c-format
msgid ""
"If you are a new user, you may want to explore the documentation which is "
"already installed on your system as you start to use it. There are currently "
"several documentation systems, work is proceeding on integrating the "
"different types of documentation. Here are a few starting points."
msgstr ""

#. Tag: para
#: boot-new.xml:370
#, no-c-format
msgid ""
"Documentation accompanying programs you have installed is in <filename>/usr/"
"share/doc/</filename>, under a subdirectory named after the program. For "
"example, the APT User's Guide for using <command>apt</command> to install "
"other programs on your system, is located in <filename>/usr/share/doc/apt/"
"guide.html/index.html</filename>."
msgstr ""

#. Tag: para
#: boot-new.xml:379
#, no-c-format
msgid ""
"In addition, there are some special folders within the <filename>/usr/share/"
"doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</"
"emphasis> format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. "
"After installing <command>dhelp</command> you will find a browse-able index "
"of documentation in <filename>/usr/share/doc/HTML/index.html</filename>."
msgstr ""

#. Tag: para
#: boot-new.xml:389
#, no-c-format
msgid ""
"One easy way to view these documents is to <userinput>cd /usr/share/doc/</"
"userinput>, and type <userinput>lynx</userinput> followed by a space and a "
"dot (the dot stands for the current directory)."
msgstr ""

#. Tag: para
#: boot-new.xml:396
#, no-c-format
msgid ""
"You can also type <userinput>info <replaceable>command</replaceable></"
"userinput> or <userinput>man <replaceable>command</replaceable></userinput> "
"to see documentation on most commands available at the command prompt. "
"Typing <userinput>help</userinput> will display help on shell commands. And "
"typing a command followed by <userinput>--help</userinput> will usually "
"display a short summary of the command's usage. If a command's results "
"scroll past the top of the screen, type <userinput>| more</userinput> after "
"the command to cause the results to pause before scrolling past the top of "
"the screen. To see a list of all commands available which begin with a "
"certain letter, type the letter and then two tabs."
msgstr ""

#. Tag: para
#: boot-new.xml:411
#, no-c-format
msgid ""
"For a more complete introduction to Debian and GNU/Linux, see <filename>/usr/"
"share/doc/debian-guide/html/noframes/index.html</filename>."
msgstr ""