diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/boot-installer.pot | 200 | ||||
| -rw-r--r-- | po/pot/hardware.pot | 160 | ||||
| -rw-r--r-- | po/pot/install-methods.pot | 210 | ||||
| -rw-r--r-- | po/pot/installation-howto.pot | 12 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 622 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 292 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 224 |
7 files changed, 849 insertions, 871 deletions
diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index f305c5753..84b3abc24 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-31 19:17+0000\n" +"POT-Creation-Date: 2007-01-01 11:02+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -679,7 +679,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:856 #, no-c-format -msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/i386/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/i386/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care." +msgid "If you intend to use the hard drive only for booting and then download everything over the network, you should download the <filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its corresponding kernel <filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care." msgstr "" #. Tag: para @@ -700,9 +700,7 @@ msgstr "" msgid "" "image=/boot/newinstall/vmlinuz\n" " label=newinstall\n" - " initrd=/boot/newinstall/initrd.gz\n" - " root=/dev/ram0\n" - " append=\"ramdisk_size=12000\"" + " initrd=/boot/newinstall/initrd.gz" msgstr "" #. Tag: para @@ -717,7 +715,7 @@ msgstr "" msgid "" "The procedure for <command>GRUB</command> is quite similar. Locate your <filename>menu.lst</filename> in the <filename>/boot/grub/</filename> directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the following lines: <informalexample><screen>\n" "title New Install\n" - "kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" + "kernel (hd0,0)/boot/newinstall/vmlinuz\n" "initrd (hd0,0)/boot/newinstall/initrd.gz\n" "</screen></informalexample> and reboot." msgstr "" @@ -761,7 +759,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:955 #, no-c-format -msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>linux root=/dev/hdc</userinput> at the boot prompt." +msgid "For installing from an LS-120 drive (ATAPI version) with a set of floppies, you need to specify the virtual location for the floppy device. This is done with the <emphasis>root=</emphasis> boot argument, giving the device that the ide-floppy driver maps the device to. For example, if your LS-120 drive is connected as the first IDE device (master) on the second cable, you enter <userinput>install root=/dev/hdc</userinput> at the boot prompt." msgstr "" #. Tag: para @@ -854,7 +852,7 @@ msgstr "" #. Tag: para #: boot-installer.xml:1078 #, no-c-format -msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>linux</userinput>) and a space before the first parameter (e.g., <userinput>linux fb=false</userinput>)." +msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</keycap>. If you add any parameters to the boot command line, be sure to type the boot method (the default is <userinput>install</userinput>) and a space before the first parameter (e.g., <userinput>install fb=false</userinput>)." msgstr "" #. Tag: para @@ -2024,7 +2022,7 @@ msgid "Set to <userinput>false</userinput> to prevent probing for USB on boot, i msgstr "" #. Tag: term -#: boot-installer.xml:3007 boot-installer.xml:3171 +#: boot-installer.xml:3007 boot-installer.xml:3173 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" @@ -2116,131 +2114,131 @@ msgstr "" #. Tag: para #: boot-installer.xml:3091 #, no-c-format -msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." +msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB." msgstr "" #. Tag: term -#: boot-installer.xml:3099 +#: boot-installer.xml:3101 #, no-c-format msgid "mouse/left" msgstr "" #. Tag: para -#: boot-installer.xml:3100 +#: boot-installer.xml:3102 #, no-c-format msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to <userinput>true</userinput>." msgstr "" #. Tag: term -#: boot-installer.xml:3109 +#: boot-installer.xml:3111 #, no-c-format msgid "directfb/hw-accel" msgstr "" #. Tag: para -#: boot-installer.xml:3110 +#: boot-installer.xml:3112 #, no-c-format msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to <userinput>true</userinput> when booting the installer." msgstr "" #. Tag: term -#: boot-installer.xml:3120 +#: boot-installer.xml:3122 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:3121 +#: boot-installer.xml:3123 #, no-c-format msgid "Set to <userinput>true</userinput> to enter rescue mode rather than performing a normal installation. See <xref linkend=\"rescue\"/>." msgstr "" #. Tag: title -#: boot-installer.xml:3132 +#: boot-installer.xml:3134 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:3133 +#: boot-installer.xml:3135 #, no-c-format msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in <xref linkend=\"preseed-bootparms\"/>. Some specific examples are listed below." msgstr "" #. Tag: term -#: boot-installer.xml:3145 +#: boot-installer.xml:3147 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:3146 +#: boot-installer.xml:3148 #, no-c-format msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. For example, use <userinput>locale=de_CH</userinput> to select German as language and Switzerland as country." msgstr "" #. Tag: term -#: boot-installer.xml:3157 +#: boot-installer.xml:3159 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:3158 +#: boot-installer.xml:3160 #, no-c-format msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are <classname>openssh-client-udeb</classname> (so you can use <command>scp</command> during the installation) and <classname>ppp-udeb</classname> (which supports PPPoE configuration)." msgstr "" #. Tag: para -#: boot-installer.xml:3172 +#: boot-installer.xml:3174 #, no-c-format msgid "Set to <userinput>true</userinput> if you want to disable DHCP and instead force static network configuration." msgstr "" #. Tag: term -#: boot-installer.xml:3181 +#: boot-installer.xml:3183 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:3182 +#: boot-installer.xml:3184 #, no-c-format msgid "By default the installer will use the http protocol to download files from Debian mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to <userinput>ftp</userinput>, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually." msgstr "" #. Tag: term -#: boot-installer.xml:3195 +#: boot-installer.xml:3197 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:3196 +#: boot-installer.xml:3198 #, no-c-format msgid "Can be used to select tasks that are not available from the interactive task list, such as the <literal>kde-desktop</literal> task. See <xref linkend=\"pkgsel\"/> for additional information." msgstr "" #. Tag: title -#: boot-installer.xml:3209 +#: boot-installer.xml:3211 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:3210 +#: boot-installer.xml:3212 #, no-c-format msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:3223 +#: boot-installer.xml:3225 #, no-c-format msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." msgstr "" #. Tag: para -#: boot-installer.xml:3230 +#: boot-installer.xml:3232 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: <informalexample><screen>\n" @@ -2249,109 +2247,109 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3240 +#: boot-installer.xml:3242 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:3252 +#: boot-installer.xml:3254 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:3257 +#: boot-installer.xml:3259 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3258 +#: boot-installer.xml:3260 #, no-c-format msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." msgstr "" #. Tag: para -#: boot-installer.xml:3265 +#: boot-installer.xml:3267 #, no-c-format msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." msgstr "" #. Tag: para -#: boot-installer.xml:3271 +#: boot-installer.xml:3273 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:3276 +#: boot-installer.xml:3278 #, no-c-format msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." msgstr "" #. Tag: para -#: boot-installer.xml:3282 +#: boot-installer.xml:3284 #, no-c-format msgid "If the installer fails to recognize a CD-ROM, try just running the option <menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way." msgstr "" #. Tag: para -#: boot-installer.xml:3292 +#: boot-installer.xml:3294 #, no-c-format msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." msgstr "" #. Tag: para -#: boot-installer.xml:3298 +#: boot-installer.xml:3300 #, no-c-format msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." msgstr "" #. Tag: title -#: boot-installer.xml:3306 +#: boot-installer.xml:3308 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:3309 +#: boot-installer.xml:3311 #, no-c-format msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." msgstr "" #. Tag: para -#: boot-installer.xml:3315 +#: boot-installer.xml:3317 #, no-c-format msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." msgstr "" #. Tag: para -#: boot-installer.xml:3322 +#: boot-installer.xml:3324 #, no-c-format msgid "Some older CD-ROM drives do not work correctly if <quote>direct memory access</quote> (DMA) is enabled." msgstr "" #. Tag: title -#: boot-installer.xml:3333 +#: boot-installer.xml:3335 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:3334 +#: boot-installer.xml:3336 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:3339 +#: boot-installer.xml:3341 #, no-c-format msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." msgstr "" #. Tag: para -#: boot-installer.xml:3345 +#: boot-installer.xml:3347 #, no-c-format msgid "" "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the <filename>MD5SUMS</filename> file that should be present in the same location as where you downloaded the image from. <informalexample><screen>\n" @@ -2361,7 +2359,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:3358 +#: boot-installer.xml:3360 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -2374,19 +2372,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3363 +#: boot-installer.xml:3365 #, no-c-format msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." msgstr "" #. Tag: para -#: boot-installer.xml:3375 +#: boot-installer.xml:3377 #, no-c-format msgid "Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> (use <command>nano</command> as editor) to check for any specific error messages. After that, also check the output of <command>dmesg</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3382 +#: boot-installer.xml:3384 #, no-c-format msgid "" "Check in the output of <command>dmesg</command> if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): <informalexample><screen>\n" @@ -2399,13 +2397,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3396 +#: boot-installer.xml:3398 #, no-c-format msgid "Check that there is a device node for your CD-ROM drive under <filename>/dev/</filename>. In the example above, this would be <filename>/dev/hdc</filename>. There should also be a <filename>/dev/cdroms/cdrom0</filename>." msgstr "" #. Tag: para -#: boot-installer.xml:3404 +#: boot-installer.xml:3406 #, no-c-format msgid "" "Use the <command>mount</command> command to check if the CD-ROM is already mounted; if not, try mounting it manually: <informalexample><screen>\n" @@ -2414,7 +2412,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3414 +#: boot-installer.xml:3416 #, no-c-format msgid "" "Check if DMA is currently enabled: <informalexample><screen>\n" @@ -2427,163 +2425,157 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3429 +#: boot-installer.xml:3431 #, no-c-format msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." msgstr "" #. Tag: title -#: boot-installer.xml:3444 +#: boot-installer.xml:3446 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:3446 +#: boot-installer.xml:3448 #, no-c-format msgid "The biggest problem for people using floppy disks to install Debian seems to be floppy disk reliability." msgstr "" #. Tag: para -#: boot-installer.xml:3451 +#: boot-installer.xml:3453 #, no-c-format msgid "The boot floppy is the floppy with the worst problems, because it is read by the hardware directly, before Linux boots. Often, the hardware doesn't read as reliably as the Linux floppy disk driver, and may just stop without printing an error message if it reads incorrect data. There can also be failures in the driver floppies, most of which indicate themselves with a flood of messages about disk I/O errors." msgstr "" #. Tag: para -#: boot-installer.xml:3460 +#: boot-installer.xml:3462 #, no-c-format msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a <emphasis>different</emphasis> floppy and see if that solves the problem. Simply reformatting the old floppy may not be sufficient, even if it appears that the floppy was reformatted and written with no errors. It is sometimes useful to try writing the floppy on a different system." msgstr "" #. Tag: para -#: boot-installer.xml:3469 +#: boot-installer.xml:3471 #, no-c-format msgid "One user reports he had to write the images to floppy <emphasis>three</emphasis> times before one worked, and then everything was fine with the third floppy." msgstr "" #. Tag: para -#: boot-installer.xml:3475 +#: boot-installer.xml:3477 #, no-c-format msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." msgstr "" #. Tag: para -#: boot-installer.xml:3481 +#: boot-installer.xml:3483 #, no-c-format msgid "Other users have reported that simply rebooting a few times with the same floppy in the floppy drive can lead to a successful boot. This is all due to buggy hardware or firmware floppy drivers." msgstr "" #. Tag: title -#: boot-installer.xml:3490 +#: boot-installer.xml:3492 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:3492 +#: boot-installer.xml:3494 #, no-c-format msgid "If you have problems and the kernel hangs during the boot process, doesn't recognize peripherals you actually have, or drives are not recognized properly, the first thing to check is the boot parameters, as discussed in <xref linkend=\"boot-parms\"/>." msgstr "" #. Tag: para -#: boot-installer.xml:3499 -#, no-c-format -msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3506 +#: boot-installer.xml:3501 #, no-c-format msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. <phrase arch=\"x86\">Internal modems, sound cards, and Plug-n-Play devices can be especially problematic.</phrase>" msgstr "" #. Tag: para -#: boot-installer.xml:3512 +#: boot-installer.xml:3507 #, no-c-format msgid "If you have a large amount of memory installed in your machine, more than 512M, and the installer hangs when booting the kernel, you may need to include a boot argument to limit the amount of memory the kernel sees, such as <userinput>mem=512m</userinput>." msgstr "" #. Tag: title -#: boot-installer.xml:3523 boot-installer.xml:3608 +#: boot-installer.xml:3518 boot-installer.xml:3603 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3524 +#: boot-installer.xml:3519 #, no-c-format msgid "There are some common installation problems that can be solved or avoided by passing certain boot parameters to the installer." msgstr "" #. Tag: para -#: boot-installer.xml:3529 +#: boot-installer.xml:3524 #, no-c-format msgid "Some systems have floppies with <quote>inverted DCLs</quote>. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter <userinput>floppy=thinkpad</userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3535 +#: boot-installer.xml:3530 #, no-c-format msgid "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is recognized properly. If not, determine your drive geometry (cylinders, heads, and sectors), and use the parameter <userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>." msgstr "" #. Tag: para -#: boot-installer.xml:3544 +#: boot-installer.xml:3539 #, no-c-format msgid "If you have a very old machine, and the kernel hangs after saying <computeroutput>Checking 'hlt' instruction...</computeroutput>, then you should try the <userinput>no-hlt</userinput> boot argument, which disables this test." msgstr "" #. Tag: para -#: boot-installer.xml:3551 +#: boot-installer.xml:3546 #, no-c-format msgid "If your screen begins to show a weird picture while the kernel boots, eg. pure white, pure black or colored pixel garbage, your system may contain a problematic video card which does not switch to the framebuffer mode properly. Then you can use the boot parameter <userinput>fb=false video=vga16:off</userinput> to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See <xref linkend=\"boot-parms\"/> for details." msgstr "" #. Tag: title -#: boot-installer.xml:3565 +#: boot-installer.xml:3560 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:3566 +#: boot-installer.xml:3561 #, no-c-format msgid "Some laptop models produced by Dell are known to crash when PCMCIA device detection tries to access some hardware addresses. Other laptops may display similar problems. If you experience such a problem and you don't need PCMCIA support during the installation, you can disable PCMCIA using the <userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can then configure PCMCIA after the installation is completed and exclude the resource range causing the problems." msgstr "" #. Tag: para -#: boot-installer.xml:3576 +#: boot-installer.xml:3571 #, no-c-format msgid "Alternatively, you can boot the installer in expert mode. You will then be asked to enter the resource range options your hardware needs. For example, if you have one of the Dell laptops mentioned above, you should enter <userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list of some common resource range options in the <ulink url=\"http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the commas, if any, when you enter this value in the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3593 +#: boot-installer.xml:3588 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:3594 +#: boot-installer.xml:3589 #, no-c-format msgid "The kernel normally tries to install USB modules and the USB keyboard driver in order to support some non-standard USB keyboards. However, there are some broken USB systems where the driver hangs on loading. A possible workaround may be disabling the USB controller in your mainboard BIOS setup. Another option is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter at the boot prompt, which will prevent the modules from being loaded." msgstr "" #. Tag: para -#: boot-installer.xml:3609 +#: boot-installer.xml:3604 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:3615 +#: boot-installer.xml:3610 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3616 +#: boot-installer.xml:3611 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: <informalexample><screen>\n" @@ -2593,85 +2585,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3630 +#: boot-installer.xml:3625 #, no-c-format msgid "Note that you may also have to manually add this parameter to the silo configuration (edit <filename>/target/etc/silo.conf</filename> before rebooting) and, if you installed X11, modify the video driver in <filename>/etc/X11/xorg.conf</filename>." msgstr "" #. Tag: title -#: boot-installer.xml:3641 +#: boot-installer.xml:3636 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3642 +#: boot-installer.xml:3637 #, no-c-format msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems." msgstr "" #. Tag: para -#: boot-installer.xml:3648 +#: boot-installer.xml:3643 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3657 +#: boot-installer.xml:3652 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3659 +#: boot-installer.xml:3654 #, no-c-format -msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable> </computeroutput>, or <computeroutput> <replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable> </computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable> </computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." +msgid "During the boot sequence, you may see many messages in the form <computeroutput>can't find <replaceable>something</replaceable></computeroutput>, or <computeroutput><replaceable>something</replaceable> not present</computeroutput>, <computeroutput>can't initialize <replaceable>something</replaceable></computeroutput>, or even <computeroutput>this driver release depends on <replaceable>something</replaceable></computeroutput>. Most of these messages are harmless. You see them because the kernel for the installation system is built to run on computers with many different peripheral devices. Obviously, no one computer will have every possible peripheral device, so the operating system may emit a few complaints while it looks for peripherals you don't own. You may also see the system pause for a while. This happens when it is waiting for a device to respond, and that device is not present on your system. If you find the time it takes to boot the system unacceptably long, you can create a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." msgstr "" #. Tag: title -#: boot-installer.xml:3684 +#: boot-installer.xml:3679 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3685 +#: boot-installer.xml:3680 #, no-c-format msgid "If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. This information may provide clues as to what went wrong and how to fix it. If you are submitting a bug report you may want to attach this information to the bug report." msgstr "" #. Tag: para -#: boot-installer.xml:3696 +#: boot-installer.xml:3691 #, no-c-format msgid "Other pertinent 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." msgstr "" #. Tag: title -#: boot-installer.xml:3707 +#: boot-installer.xml:3702 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3708 +#: boot-installer.xml:3703 #, no-c-format msgid "If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations." msgstr "" #. Tag: para -#: boot-installer.xml:3715 +#: boot-installer.xml:3710 #, no-c-format -msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an E-Mail address that you do not mind being made public." +msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public." msgstr "" #. Tag: para -#: boot-installer.xml:3721 +#: boot-installer.xml:3716 #, no-c-format msgid "If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run the command <command>reportbug installation-report</command>." msgstr "" #. Tag: para -#: boot-installer.xml:3731 +#: boot-installer.xml:3726 #, no-c-format msgid "" "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the <classname>installation-reports</classname> pseudo package, by sending it to <email>submit@bugs.debian.org</email>. <informalexample><screen>\n" diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index 316855467..7801cbd83 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-31 03:15+0000\n" +"POT-Creation-Date: 2007-01-01 11:02+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -1745,19 +1745,19 @@ msgstr "" #. Tag: para #: hardware.xml:853 #, no-c-format -msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and new processors like the Athlon XP and Intel P4 Xeon." +msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para #: hardware.xml:861 #, no-c-format -msgid "If your system has a 64-bit AMD64, Intel EM64T or Intel Core 2 Duo processor, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." +msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: para #: hardware.xml:868 #, no-c-format -msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", Debian Sarge has <emphasis>dropped support</emphasis> for actual 80386 processors (and their clones), which were supported by earlier releases<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." +msgid "However, Debian GNU/Linux &releasename; will <emphasis>not</emphasis> run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian<footnote> <para> We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. </para> </footnote>. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported<footnote> <para> Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can. </para> </footnote>." msgstr "" #. Tag: title @@ -2834,431 +2834,431 @@ msgstr "" #. Tag: para #: hardware.xml:2065 #, no-c-format -msgid "You can also <emphasis>boot</emphasis> your system over the network. <phrase arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" +msgid "The network can be used during the installtion to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connection (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP." msgstr "" #. Tag: para -#: hardware.xml:2071 +#: hardware.xml:2075 #, no-c-format -msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." +msgid "You can also <emphasis>boot</emphasis> the installation system over the network. <phrase arch=\"mips\">This is the preferred installation technique for &arch-title;.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2076 +#: hardware.xml:2081 #, no-c-format -msgid "After the operating system kernel is installed, you can install the rest of your system via any sort of network connection (including PPP after installation of the base system), via FTP or HTTP." +msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: title -#: hardware.xml:2085 +#: hardware.xml:2089 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:2087 +#: hardware.xml:2091 #, no-c-format -msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of the manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." +msgid "If you are running another Unix-like system, you could use it to install &debian; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the <xref linkend=\"linux-upgrade\"/>." msgstr "" #. Tag: title -#: hardware.xml:2099 +#: hardware.xml:2103 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:2101 +#: hardware.xml:2105 #, no-c-format msgid "The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see <xref linkend=\"kernel-baking\"/> to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware." msgstr "" #. Tag: para -#: hardware.xml:2111 +#: hardware.xml:2115 #, no-c-format msgid "Generally, the Debian installation system includes support for floppies, IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:2118 +#: hardware.xml:2122 #, no-c-format msgid "Disk interfaces that emulate the <quote>AT</quote> hard disk interface — often called MFM, RLL, IDE, or ATA — are supported. Very old 8–bit hard disk controllers used in the IBM XT computer are supported only as a module. SCSI disk controllers from many different manufacturers are supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> for more details." msgstr "" #. Tag: para -#: hardware.xml:2128 +#: hardware.xml:2132 #, no-c-format msgid "Pretty much all storage systems supported by the Linux kernel are supported by the Debian installation system. Note that the current Linux kernel does not support floppies on the Macintosh at all, and the Debian installation system doesn't support floppies for Amigas. Also supported on the Atari is the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) file system. Amigas support the FAT file system, and HFS as a module." msgstr "" #. Tag: para -#: hardware.xml:2138 +#: hardware.xml:2142 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: <itemizedlist> <listitem><para> Sparc ESP </para></listitem> <listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors FAQ</ulink> for more information on SPARC hardware supported by the Linux kernel." msgstr "" #. Tag: para -#: hardware.xml:2171 +#: hardware.xml:2175 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This includes both SCSI and IDE disks. Note, however, that on many systems, the SRM console is unable to boot from IDE drives, and the Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;\"></ulink> for more information on booting the Jensen)" msgstr "" #. Tag: para -#: hardware.xml:2180 +#: hardware.xml:2184 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all." msgstr "" #. Tag: para -#: hardware.xml:2186 +#: hardware.xml:2190 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive." msgstr "" #. Tag: para -#: hardware.xml:2192 +#: hardware.xml:2196 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:2197 +#: hardware.xml:2201 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" #. Tag: title -#: hardware.xml:2214 +#: hardware.xml:2218 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:2215 +#: hardware.xml:2219 #, no-c-format msgid "Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:2221 +#: hardware.xml:2225 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see <xref linkend=\"hardware-issues\"/>)." msgstr "" #. Tag: para -#: hardware.xml:2227 +#: hardware.xml:2231 #, no-c-format msgid "Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink> to determine whether your specific hardware is supported by Linux." msgstr "" #. Tag: para -#: hardware.xml:2233 +#: hardware.xml:2237 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: hardware.xml:2239 +#: hardware.xml:2243 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots." msgstr "" #. Tag: para -#: hardware.xml:2245 +#: hardware.xml:2249 #, no-c-format msgid "The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation board features four 64 bit PCI slots. The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:2255 +#: hardware.xml:2259 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/Linux" msgstr "" #. Tag: para -#: hardware.xml:2257 +#: hardware.xml:2261 #, no-c-format msgid "There are several vendors, who ship systems with Debian or other distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</ulink>. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para -#: hardware.xml:2265 +#: hardware.xml:2269 #, no-c-format msgid "Unfortunately, it's quite rare to find any vendor shipping new &arch-title; machines at all." msgstr "" #. Tag: para -#: hardware.xml:2270 +#: hardware.xml:2274 #, no-c-format msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for <quote>windows refund</quote> may get you some useful information to help with that." msgstr "" #. Tag: para -#: hardware.xml:2278 +#: hardware.xml:2282 #, no-c-format msgid "Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors." msgstr "" #. Tag: title -#: hardware.xml:2289 +#: hardware.xml:2293 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:2290 +#: hardware.xml:2294 #, no-c-format msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code." msgstr "" #. Tag: para -#: hardware.xml:2297 +#: hardware.xml:2301 #, no-c-format msgid "Another example is the proprietary hardware in the older Macintosh line. In fact, no specifications or documentation have ever been released for any Macintosh hardware, most notably the ADB controller (used by the mouse and keyboard), the floppy controller, and all acceleration and CLUT manipulation of the video hardware (though we do now support CLUT manipulation on nearly all internal video chips). In a nutshell, this explains why the Macintosh Linux port lags behind other Linux ports." msgstr "" #. Tag: para -#: hardware.xml:2308 +#: hardware.xml:2312 #, no-c-format msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title -#: hardware.xml:2320 +#: hardware.xml:2324 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:2321 +#: hardware.xml:2325 #, no-c-format msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> or <quote>Made especially for Windows-based computers</quote>. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often <emphasis>not</emphasis> passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para -#: hardware.xml:2334 +#: hardware.xml:2338 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes its being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at <emphasis>real-time</emphasis> priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:2355 +#: hardware.xml:2359 #, no-c-format msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the <ulink url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>." msgstr "" #. Tag: title -#: hardware.xml:2372 +#: hardware.xml:2376 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:2374 +#: hardware.xml:2378 #, no-c-format -msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. For a minimal console-based system (all standard packages), 250MB is required. If you want to install a reasonable amount of software, including the X Window System, and some development programs and libraries, you'll need at least 400MB. For a more or less complete desktop system, you'll need a few gigabytes." +msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space. Note that these are really bare-minimum numbers. For more realistic figures, see <xref linkend=\"minimum-hardware-reqts\"/>." msgstr "" #. Tag: para -#: hardware.xml:2383 +#: hardware.xml:2384 #, no-c-format msgid "On the Amiga the size of FastRAM is relevant towards the total memory requirements. Also, using Zorro cards with 16-bit RAM is not supported; you'll need 32-bit RAM. The <command>amiboot</command> program can be used to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. Recent kernels should disable 16-bit RAM automatically." msgstr "" #. Tag: para -#: hardware.xml:2392 +#: hardware.xml:2393 #, no-c-format msgid "On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many users have reported problems running the kernel itself in Fast RAM, so the Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." msgstr "" #. Tag: para -#: hardware.xml:2400 +#: hardware.xml:2401 #, no-c-format msgid "On the Macintosh, care should be taken on machines with RAM-based video (RBV). The RAM segment at physical address 0 is used as screen memory, making the default load position for the kernel unavailable. The alternate RAM segment used for kernel and RAMdisk must be at least 4 MB." msgstr "" #. Tag: emphasis -#: hardware.xml:2410 +#: hardware.xml:2411 #, no-c-format msgid "FIXME: is this still true?" msgstr "" #. Tag: title -#: hardware.xml:2421 +#: hardware.xml:2422 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:2422 +#: hardware.xml:2423 #, no-c-format msgid "Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. <phrase arch=\"x86\">This includes most PCI and PCMCIA cards.</phrase> <phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase> <phrase arch=\"m68k\">Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete details.</phrase>" msgstr "" #. Tag: para -#: hardware.xml:2434 +#: hardware.xml:2435 #, no-c-format msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" msgstr "" #. Tag: para -#: hardware.xml:2440 +#: hardware.xml:2441 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:2445 +#: hardware.xml:2446 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:2450 +#: hardware.xml:2451 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:2455 +#: hardware.xml:2456 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:2460 +#: hardware.xml:2461 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:2467 +#: hardware.xml:2468 #, no-c-format msgid "Due to kernel limitations only the onboard network interfaces on DECstations are supported, TurboChannel option network cards currently do not work." msgstr "" #. Tag: para -#: hardware.xml:2473 +#: hardware.xml:2474 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:2478 +#: hardware.xml:2479 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:2483 +#: hardware.xml:2484 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:2488 +#: hardware.xml:2489 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:2497 +#: hardware.xml:2498 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the <ulink url=\"&url-slug-firmware;\">Slug-Firmware site</ulink>." msgstr "" #. Tag: para -#: hardware.xml:2507 +#: hardware.xml:2508 #, no-c-format msgid "As for ISDN, the D-channel protocol for the (old) German 1TR6 is not supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;. Using ISDN during the installation is not supported." msgstr "" #. Tag: title -#: hardware.xml:2516 +#: hardware.xml:2517 #, no-c-format msgid "Drivers Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:2517 +#: hardware.xml:2518 #, no-c-format msgid "The installation system currently does not support retrieving firmware. This means that any network cards that use a driver that requires firmware to be loaded, is not supported by default." msgstr "" #. Tag: para -#: hardware.xml:2523 +#: hardware.xml:2524 #, no-c-format msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually. Note that the firmware may be packaged separately from the driver and may not be available in the <quote>main</quote> section of the &debian; archive." msgstr "" #. Tag: para -#: hardware.xml:2534 +#: hardware.xml:2535 #, no-c-format msgid "If the driver itself <emphasis>is</emphasis> supported, you may also be able to use the NIC during installation by copying the firmware from some medium to <filename>/usr/lib/hotplug/firmware</filename>. Don't forget to also copy the firmware to that location for the installed system before the reboot at the end of the installation." msgstr "" #. Tag: title -#: hardware.xml:2546 +#: hardware.xml:2547 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:2547 +#: hardware.xml:2548 #, no-c-format msgid "Wireless NICs are in general supported as well, with one big proviso. A lot of wireless adapters require drivers that are either non-free or have not been accepted into the official Linux kernel. These NICs can generally be made to work under &debian;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:2554 +#: hardware.xml:2555 #, no-c-format msgid "If there is no other NIC you can use during the installation, it is still possible to install &debian; using a full CD-ROM or DVD image. Use the same procedure as described above for NICs that require firmware." msgstr "" #. Tag: para -#: hardware.xml:2560 +#: hardware.xml:2561 #, no-c-format msgid "In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. <phrase arch=\"x86\">If no Linux driver is available, your last resort is to use the <classname>ndiswrapper</classname> package, which allows you to use a Windows driver.</phrase>" msgstr "" #. Tag: title -#: hardware.xml:2574 +#: hardware.xml:2575 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:2575 +#: hardware.xml:2576 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:2582 +#: hardware.xml:2583 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:2584 +#: hardware.xml:2585 #, no-c-format msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the <literal>tulip</literal> driver, others with the <literal>dfme</literal> driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "" #. Tag: para -#: hardware.xml:2594 +#: hardware.xml:2595 #, no-c-format msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the <literal>tulip</literal> driver is probably the correct one. During the installation the solution is to switch to a shell and unload the wrong driver module using <userinput>modprobe -r <replaceable>module</replaceable></userinput> (or both, if they are both loaded). After that you can load the correct module using <userinput>modprobe <replaceable>module</replaceable></userinput>." msgstr "" #. Tag: title -#: hardware.xml:2609 +#: hardware.xml:2610 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:2611 +#: hardware.xml:2612 #, no-c-format msgid "The <literal>cassini</literal> network driver does not work with Sun B100 blade systems." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 49a202101..7749e32d8 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-31 03:15+0000\n" +"POT-Creation-Date: 2007-01-01 11:02+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -474,7 +474,7 @@ msgid "If you like more flexibility or just want to know what's going on, you sh msgstr "" #. Tag: title -#: install-methods.xml:662 install-methods.xml:754 +#: install-methods.xml:662 install-methods.xml:751 #, no-c-format msgid "USB stick partitioning on &arch-title;" msgstr "" @@ -518,15 +518,19 @@ msgstr "" #. Tag: para #: install-methods.xml:736 #, no-c-format +msgid "The <filename>syslinux.cfg</filename> configuration file should contain the following two lines:" +msgstr "" + +#. Tag: screen +#: install-methods.xml:741 +#, no-c-format msgid "" - "The <filename>syslinux.cfg</filename> configuration file should contain the following two lines: <informalexample><screen>\n" "default vmlinuz\n" - "append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n" - "</screen></informalexample> Please note that the <userinput>ramdisk_size</userinput> parameter may need to be increased, depending on the image you are booting." + "append initrd=initrd.gz" msgstr "" #. Tag: para -#: install-methods.xml:755 +#: install-methods.xml:752 #, no-c-format msgid "" "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run <userinput>mac-fdisk /dev/sda</userinput>, initialise a new partition map using the <userinput>i</userinput> command, and create a new partition of type Apple_Bootstrap using the <userinput>C</userinput> command. (Note that the first \"partition\" will always be the partition map itself.) Then type <informalexample><screen>\n" @@ -535,13 +539,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:771 +#: install-methods.xml:768 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The <command>yaboot</command> boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:780 +#: install-methods.xml:777 #, no-c-format msgid "" "The normal <command>ybin</command> tool that comes with <command>yaboot</command> does not yet understand USB storage devices, so you will have to install <command>yaboot</command> by hand using the <classname>hfsutils</classname> tools. Type <informalexample><screen>\n" @@ -554,43 +558,43 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:796 +#: install-methods.xml:793 #, no-c-format msgid "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy the following files from the Debian archives to the stick:" msgstr "" #. Tag: para -#: install-methods.xml:802 +#: install-methods.xml:799 #, no-c-format msgid "<filename>vmlinux</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:807 +#: install-methods.xml:804 #, no-c-format msgid "<filename>initrd.gz</filename> (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:812 +#: install-methods.xml:809 #, no-c-format msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:817 +#: install-methods.xml:814 #, no-c-format msgid "<filename>boot.msg</filename> (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:822 +#: install-methods.xml:819 #, no-c-format msgid "Optional kernel modules" msgstr "" #. Tag: para -#: install-methods.xml:829 +#: install-methods.xml:826 #, no-c-format msgid "" "The <filename>yaboot.conf</filename> configuration file should contain the following lines: <informalexample><screen>\n" @@ -608,283 +612,283 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:845 +#: install-methods.xml:842 #, no-c-format msgid "Adding an ISO image" msgstr "" #. Tag: para -#: install-methods.xml:846 +#: install-methods.xml:843 #, no-c-format msgid "The installer will look for a Debian ISO image on the stick as its source for additional data needed for the installation. So your next step is to copy a Debian ISO image (businesscard, netinst or even a full CD image) onto your stick (be sure to select one that fits). The file name of the image must end in <filename>.iso</filename>." msgstr "" #. Tag: para -#: install-methods.xml:854 +#: install-methods.xml:851 #, no-c-format msgid "If you want to install over the network, without using an ISO image, you will of course skip the previous step. Moreover you will have to use the initial ramdisk from the <filename>netboot</filename> directory instead of the one from <filename>hd-media</filename>, because <filename>hd-media/initrd.gz</filename> does not have network support." msgstr "" #. Tag: para -#: install-methods.xml:863 +#: install-methods.xml:860 #, no-c-format msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch." msgstr "" #. Tag: title -#: install-methods.xml:873 +#: install-methods.xml:870 #, no-c-format msgid "Booting the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:874 +#: install-methods.xml:871 #, no-c-format msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the <command>install-mbr</command> command from the package <classname>mbr</classname>:" msgstr "" #. Tag: screen -#: install-methods.xml:881 +#: install-methods.xml:878 #, no-c-format msgid "# install-mbr /dev/<replaceable>sda</replaceable>" msgstr "" #. Tag: title -#: install-methods.xml:892 +#: install-methods.xml:889 #, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:893 +#: install-methods.xml:890 #, no-c-format msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." msgstr "" #. Tag: para -#: install-methods.xml:899 +#: install-methods.xml:896 #, no-c-format msgid "A full, <quote>pure network</quote> installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." msgstr "" #. Tag: para -#: install-methods.xml:906 +#: install-methods.xml:903 #, no-c-format msgid "The installer cannot boot from files on an NTFS file system." msgstr "" #. Tag: para -#: install-methods.xml:910 +#: install-methods.xml:907 #, no-c-format msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select <userinput>Get Info</userinput> for the volume in question. HFS file systems appear as <userinput>Mac OS Standard</userinput>, while HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." msgstr "" #. Tag: para -#: install-methods.xml:921 +#: install-methods.xml:918 #, no-c-format msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model." msgstr "" #. Tag: title -#: install-methods.xml:930 +#: install-methods.xml:927 #, no-c-format msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>" msgstr "" #. Tag: para -#: install-methods.xml:932 +#: install-methods.xml:929 #, no-c-format msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>." msgstr "" #. Tag: para -#: install-methods.xml:938 +#: install-methods.xml:935 #, no-c-format msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." msgstr "" #. Tag: para -#: install-methods.xml:944 +#: install-methods.xml:941 #, no-c-format msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:951 +#: install-methods.xml:948 #, no-c-format msgid "<filename>vmlinuz</filename> (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:956 +#: install-methods.xml:953 #, no-c-format msgid "<filename>initrd.gz</filename> (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:963 +#: install-methods.xml:960 #, no-c-format msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>." msgstr "" #. Tag: title -#: install-methods.xml:973 +#: install-methods.xml:970 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:974 +#: install-methods.xml:971 #, no-c-format msgid "The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</application> to launch Linux installation, but <application>miBoot</application> cannot easily be used for hard disk booting. <application>BootX</application>, launched from MacOS, supports booting from files placed on the hard disk. <application>BootX</application> can also be used to dual-boot MacOS and Linux after your Debian installation is complete. For the Performa 6360, it appears that <command>quik</command> cannot make the hard disk bootable. So <application>BootX</application> is required on that model." msgstr "" #. Tag: para -#: install-methods.xml:987 +#: install-methods.xml:984 #, no-c-format msgid "Download and unstuff the <application>BootX</application> distribution, available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the <filename>dists/woody/main/disks-powerpc/current/powermac</filename> directory on Debian http/ftp mirrors and official Debian CDs. Use <application>Stuffit Expander</application> to extract it from its archive. Within the package, there is an empty folder called <filename>Linux Kernels</filename>. Download <filename>linux.bin</filename> and <filename>ramdisk.image.gz</filename> from the <filename>disks-powerpc/current/powermac</filename> folder, and place them in the <filename>Linux Kernels</filename> folder. Then place the <filename>Linux Kernels</filename> folder in the active System Folder." msgstr "" #. Tag: title -#: install-methods.xml:1007 +#: install-methods.xml:1004 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1008 +#: install-methods.xml:1005 #, no-c-format msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via <command>yaboot</command>, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. <command>BootX</command> is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para -#: install-methods.xml:1019 +#: install-methods.xml:1016 #, no-c-format msgid "<emphasis>Copy</emphasis> (not move) the following four files which you downloaded earlier from the Debian archives, onto the root level of your hard drive (this can be accomplished by <keycap>option</keycap>-dragging each file to the hard drive icon)." msgstr "" #. Tag: filename -#: install-methods.xml:1029 +#: install-methods.xml:1026 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1034 +#: install-methods.xml:1031 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1039 +#: install-methods.xml:1036 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1044 +#: install-methods.xml:1041 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1049 +#: install-methods.xml:1046 #, no-c-format msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS <command>pdisk</command> program, you can use the <command>L</command> command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." msgstr "" #. Tag: para -#: install-methods.xml:1057 +#: install-methods.xml:1054 #, no-c-format msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." msgstr "" #. Tag: title -#: install-methods.xml:1070 +#: install-methods.xml:1067 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1071 +#: install-methods.xml:1068 #, no-c-format msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." msgstr "" #. Tag: para -#: install-methods.xml:1079 +#: install-methods.xml:1076 #, no-c-format msgid "You need to setup a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:1086 +#: install-methods.xml:1083 #, no-c-format msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> <phrase arch=\"m68k\">Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" #. Tag: para -#: install-methods.xml:1103 +#: install-methods.xml:1100 #, no-c-format msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" #. Tag: para -#: install-methods.xml:1109 +#: install-methods.xml:1106 #, no-c-format msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console." msgstr "" #. Tag: para -#: install-methods.xml:1126 +#: install-methods.xml:1123 #, no-c-format msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian." msgstr "" #. Tag: para -#: install-methods.xml:1131 +#: install-methods.xml:1128 #, no-c-format msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para -#: install-methods.xml:1139 +#: install-methods.xml:1136 #, no-c-format msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>." msgstr "" #. Tag: title -#: install-methods.xml:1157 +#: install-methods.xml:1154 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1158 +#: install-methods.xml:1155 #, no-c-format msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1170 +#: install-methods.xml:1167 #, no-c-format msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title -#: install-methods.xml:1192 +#: install-methods.xml:1189 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1193 +#: install-methods.xml:1190 #, no-c-format msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1201 +#: install-methods.xml:1198 #, no-c-format msgid "" "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n" @@ -901,25 +905,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1234 +#: install-methods.xml:1231 #, no-c-format msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. In that case, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1255 +#: install-methods.xml:1252 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1256 +#: install-methods.xml:1253 #, no-c-format msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" msgstr "" #. Tag: screen -#: install-methods.xml:1263 +#: install-methods.xml:1260 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -944,25 +948,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1265 +#: install-methods.xml:1262 #, no-c-format msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1275 +#: install-methods.xml:1272 #, no-c-format msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1283 +#: install-methods.xml:1280 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1284 +#: install-methods.xml:1281 #, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -997,13 +1001,13 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1300 +#: install-methods.xml:1297 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1301 +#: install-methods.xml:1298 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n" @@ -1012,19 +1016,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1313 +#: install-methods.xml:1310 #, no-c-format msgid "Historically TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1323 +#: install-methods.xml:1320 #, no-c-format msgid "Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. </para> </footnote>; you'll need that below. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1341 +#: install-methods.xml:1338 #, no-c-format msgid "" "If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" @@ -1035,85 +1039,85 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1363 +#: install-methods.xml:1360 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1364 +#: install-methods.xml:1361 #, no-c-format msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1373 +#: install-methods.xml:1370 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory." msgstr "" #. Tag: para -#: install-methods.xml:1382 +#: install-methods.xml:1379 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1390 +#: install-methods.xml:1387 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1402 +#: install-methods.xml:1399 #, no-c-format msgid "DECstation TFTP Images" msgstr "" #. Tag: para -#: install-methods.xml:1403 +#: install-methods.xml:1400 #, no-c-format msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename>. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above." msgstr "" #. Tag: para -#: install-methods.xml:1413 +#: install-methods.xml:1410 #, no-c-format msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: install-methods.xml:1425 +#: install-methods.xml:1422 #, no-c-format msgid "boot #/tftp/filename param1=value1 param2=value2 ..." msgstr "" #. Tag: para -#: install-methods.xml:1427 +#: install-methods.xml:1424 #, no-c-format msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>." msgstr "" #. Tag: title -#: install-methods.xml:1465 +#: install-methods.xml:1462 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1466 +#: install-methods.xml:1463 #, no-c-format msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods." msgstr "" #. Tag: title -#: install-methods.xml:1481 +#: install-methods.xml:1478 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1482 +#: install-methods.xml:1479 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1122,85 +1126,85 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1498 +#: install-methods.xml:1495 #, no-c-format msgid "If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested." msgstr "" #. Tag: para -#: install-methods.xml:1505 +#: install-methods.xml:1502 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1516 +#: install-methods.xml:1513 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1517 +#: install-methods.xml:1514 #, no-c-format msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:1522 +#: install-methods.xml:1519 #, no-c-format msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information." msgstr "" #. Tag: title -#: install-methods.xml:1534 +#: install-methods.xml:1531 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1535 +#: install-methods.xml:1532 #, no-c-format msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title -#: install-methods.xml:1547 +#: install-methods.xml:1544 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1548 +#: install-methods.xml:1545 #, no-c-format msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to be loaded to CFE." msgstr "" #. Tag: title -#: install-methods.xml:1653 +#: install-methods.xml:1650 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1654 +#: install-methods.xml:1651 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." msgstr "" #. Tag: title -#: install-methods.xml:1667 +#: install-methods.xml:1664 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1668 +#: install-methods.xml:1665 #, no-c-format msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1675 +#: install-methods.xml:1672 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" diff --git a/po/pot/installation-howto.pot b/po/pot/installation-howto.pot index b3007d84d..025732bf0 100644 --- a/po/pot/installation-howto.pot +++ b/po/pot/installation-howto.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-29 14:49+0000\n" +"POT-Creation-Date: 2007-01-01 11:02+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -269,23 +269,23 @@ msgstr "" #. Tag: para #: installation-howto.xml:299 #, no-c-format -msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>apt-get install reportbug</command>), and run <command>reportbug installation-report</command>." +msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (<command>apt-get install reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend=\"mail-outgoing\"/>, and run <command>reportbug installation-report</command>." msgstr "" #. Tag: para -#: installation-howto.xml:307 +#: installation-howto.xml:309 #, no-c-format msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see <xref linkend=\"problem-report\"/>." msgstr "" #. Tag: title -#: installation-howto.xml:319 +#: installation-howto.xml:321 #, no-c-format -msgid "And finally.." +msgid "And finally…" msgstr "" #. Tag: para -#: installation-howto.xml:320 +#: installation-howto.xml:322 #, no-c-format msgid "We hope that your Debian installation is pleasant and that you find Debian useful. You might want to read <xref linkend=\"post-install\"/>." msgstr "" diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index cc5d74d91..773d9be7c 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-31 03:15+0000\n" +"POT-Creation-Date: 2007-01-01 11:02+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -155,1499 +155,1463 @@ msgstr "" #. Tag: para #: preparing.xml:147 #, no-c-format -msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, and runs <classname>debootstrap</classname> to install the base system packages. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time." +msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, runs <classname>debootstrap</classname> to install the base system packages, and runs <classname>tasksel</classname> to allow you to install certain additional software. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time." msgstr "" #. Tag: para -#: preparing.xml:157 +#: preparing.xml:159 #, no-c-format msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment." msgstr "" #. Tag: para -#: preparing.xml:163 +#: preparing.xml:165 #, no-c-format -msgid "When <classname>debian-installer</classname> finishes, before the first system load, you have only a very basic command line driven system. The graphical interface which displays windows on your monitor will not be installed unless you select it with <classname>tasksel</classname>. It's optional because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job." +msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X11 window system and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because it requires a fairly large amount of disk space, and because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job." msgstr "" #. Tag: para -#: preparing.xml:172 +#: preparing.xml:177 #, no-c-format -msgid "Just be aware that the X system is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Installation and trouble shooting of the X window installation is not within the scope of this manual." +msgid "Just be aware that the X11 window system is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Installation and trouble shooting of the X window installation is not within the scope of this manual." msgstr "" #. Tag: title -#: preparing.xml:188 +#: preparing.xml:192 #, no-c-format msgid "Back Up Your Existing Data!" msgstr "" #. Tag: para -#: preparing.xml:189 +#: preparing.xml:193 #, no-c-format -msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian;. Anytime you partition your disk, you should count on losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work." +msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work." msgstr "" #. Tag: para -#: preparing.xml:202 +#: preparing.xml:206 #, no-c-format msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Especially if you repartition your boot drive, you might find that you have to reinstall your operating system's boot loader, or in many cases the whole operating system itself and all files on the affected partitions." msgstr "" #. Tag: para -#: preparing.xml:213 +#: preparing.xml:217 #, no-c-format msgid "With the exception of the BVM and Motorola VMEbus computers, the only supported installation method for m68k systems is booting from a local disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these machines you will need the original operating system in order to boot Linux. In order to boot Linux on the BVM and Motorola VMEbus machines you will need the <quote>BVMBug</quote> or <quote>16xBug</quote> boot ROMs." msgstr "" #. Tag: title -#: preparing.xml:231 +#: preparing.xml:235 #, no-c-format msgid "Information You Will Need" msgstr "" #. Tag: title -#: preparing.xml:234 +#: preparing.xml:238 #, no-c-format msgid "Documentation" msgstr "" #. Tag: title -#: preparing.xml:237 +#: preparing.xml:241 #, no-c-format msgid "Installation Manual" msgstr "" #. Tag: para -#: preparing.xml:239 +#: preparing.xml:243 #, no-c-format msgid "This document you are now reading, in plain ASCII, HTML or PDF format." msgstr "" #. Tag: itemizedlist -#: preparing.xml:245 +#: preparing.xml:249 #, no-c-format msgid "&list-install-manual-files;" msgstr "" #. Tag: para -#: preparing.xml:251 +#: preparing.xml:255 #, no-c-format msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of Debian; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>." msgstr "" #. Tag: para -#: preparing.xml:260 +#: preparing.xml:264 #, no-c-format msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of Debian; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>." msgstr "" #. Tag: title -#: preparing.xml:272 +#: preparing.xml:276 #, no-c-format msgid "Hardware documentation" msgstr "" #. Tag: para -#: preparing.xml:273 +#: preparing.xml:277 #, no-c-format msgid "Often contains useful information on configuring or using your hardware." msgstr "" #. Tag: ulink -#: preparing.xml:284 +#: preparing.xml:288 #, no-c-format msgid "Linux Hardware Compatibility HOWTO" msgstr "" #. Tag: ulink -#: preparing.xml:290 +#: preparing.xml:294 #, no-c-format msgid "Linux/m68k FAQ" msgstr "" #. Tag: ulink -#: preparing.xml:296 +#: preparing.xml:300 #, no-c-format msgid "Linux/Alpha FAQ" msgstr "" #. Tag: ulink -#: preparing.xml:302 +#: preparing.xml:306 #, no-c-format msgid "Linux for SPARC Processors FAQ" msgstr "" #. Tag: ulink -#: preparing.xml:308 +#: preparing.xml:312 #, no-c-format msgid "Linux/Mips website" msgstr "" #. Tag: title -#: preparing.xml:317 +#: preparing.xml:321 #, no-c-format msgid "&arch-title; Hardware References" msgstr "" #. Tag: para -#: preparing.xml:318 +#: preparing.xml:322 #, no-c-format msgid "Installation instructions and device drivers (DASD, XPRAM, Console, tape, z90 crypto, chandev, network) for Linux on &arch-title; using kernel 2.4" msgstr "" #. Tag: ulink -#: preparing.xml:330 +#: preparing.xml:334 #, no-c-format msgid "Device Drivers and Installation Commands" msgstr "" #. Tag: para -#: preparing.xml:335 +#: preparing.xml:339 #, no-c-format msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware." msgstr "" #. Tag: ulink -#: preparing.xml:345 +#: preparing.xml:349 #, no-c-format msgid "Linux for &arch-title;" msgstr "" #. Tag: para -#: preparing.xml:351 +#: preparing.xml:355 #, no-c-format msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about Debian but the basic installation concepts are the same across all &arch-title; distributions." msgstr "" #. Tag: ulink -#: preparing.xml:362 +#: preparing.xml:366 #, no-c-format msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions" msgstr "" #. Tag: title -#: preparing.xml:372 +#: preparing.xml:376 #, no-c-format msgid "Finding Sources of Hardware Information" msgstr "" #. Tag: para -#: preparing.xml:373 +#: preparing.xml:377 #, no-c-format msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install." msgstr "" #. Tag: para -#: preparing.xml:379 +#: preparing.xml:383 #, no-c-format msgid "Hardware information can be gathered from:" msgstr "" #. Tag: para -#: preparing.xml:386 +#: preparing.xml:390 #, no-c-format msgid "The manuals that come with each piece of hardware." msgstr "" #. Tag: para -#: preparing.xml:391 +#: preparing.xml:395 #, no-c-format msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> key." msgstr "" #. Tag: para -#: preparing.xml:398 +#: preparing.xml:402 #, no-c-format msgid "The cases and boxes for each piece of hardware." msgstr "" #. Tag: para -#: preparing.xml:404 +#: preparing.xml:408 #, no-c-format msgid "The System window in the Windows Control Panel." msgstr "" #. Tag: para -#: preparing.xml:410 +#: preparing.xml:414 #, no-c-format msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory." msgstr "" #. Tag: para -#: preparing.xml:417 +#: preparing.xml:421 #, no-c-format msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail." msgstr "" #. Tag: title -#: preparing.xml:429 +#: preparing.xml:433 #, no-c-format msgid "Hardware Information Needed for an Install" msgstr "" #. Tag: entry -#: preparing.xml:433 +#: preparing.xml:437 #, no-c-format msgid "Hardware" msgstr "" #. Tag: entry -#: preparing.xml:433 +#: preparing.xml:437 #, no-c-format msgid "Information You Might Need" msgstr "" #. Tag: entry -#: preparing.xml:439 +#: preparing.xml:443 #, no-c-format msgid "Hard Drives" msgstr "" #. Tag: entry -#: preparing.xml:440 +#: preparing.xml:444 #, no-c-format msgid "How many you have." msgstr "" #. Tag: entry -#: preparing.xml:442 +#: preparing.xml:446 #, no-c-format msgid "Their order on the system." msgstr "" #. Tag: entry -#: preparing.xml:445 +#: preparing.xml:449 #, no-c-format msgid "Whether IDE or SCSI (most computers are IDE)." msgstr "" #. Tag: entry -#: preparing.xml:448 +#: preparing.xml:452 #, no-c-format msgid "Whether IDE or SCSI (most m68k computers are SCSI)." msgstr "" #. Tag: entry -#: preparing.xml:450 preparing.xml:502 +#: preparing.xml:454 preparing.xml:506 #, no-c-format msgid "Available free space." msgstr "" #. Tag: entry -#: preparing.xml:451 +#: preparing.xml:455 #, no-c-format msgid "Partitions." msgstr "" #. Tag: entry -#: preparing.xml:453 +#: preparing.xml:457 #, no-c-format msgid "Partitions where other operating systems are installed." msgstr "" #. Tag: entry -#: preparing.xml:457 +#: preparing.xml:461 #, no-c-format msgid "Monitor" msgstr "" #. Tag: entry -#: preparing.xml:458 preparing.xml:478 preparing.xml:484 preparing.xml:490 +#: preparing.xml:462 preparing.xml:482 preparing.xml:488 preparing.xml:494 #, no-c-format msgid "Model and manufacturer." msgstr "" #. Tag: entry -#: preparing.xml:460 +#: preparing.xml:464 #, no-c-format msgid "Resolutions supported." msgstr "" #. Tag: entry -#: preparing.xml:461 +#: preparing.xml:465 #, no-c-format msgid "Horizontal refresh rate." msgstr "" #. Tag: entry -#: preparing.xml:462 +#: preparing.xml:466 #, no-c-format msgid "Vertical refresh rate." msgstr "" #. Tag: entry -#: preparing.xml:464 +#: preparing.xml:468 #, no-c-format msgid "Color depth (number of colors) supported." msgstr "" #. Tag: entry -#: preparing.xml:466 +#: preparing.xml:470 #, no-c-format msgid "Screen size." msgstr "" #. Tag: entry -#: preparing.xml:469 +#: preparing.xml:473 #, no-c-format msgid "Mouse" msgstr "" #. Tag: entry -#: preparing.xml:470 +#: preparing.xml:474 #, no-c-format msgid "Type: serial, PS/2, or USB." msgstr "" #. Tag: entry -#: preparing.xml:472 +#: preparing.xml:476 #, no-c-format msgid "Port." msgstr "" #. Tag: entry -#: preparing.xml:473 +#: preparing.xml:477 #, no-c-format msgid "Manufacturer." msgstr "" #. Tag: entry -#: preparing.xml:474 +#: preparing.xml:478 #, no-c-format msgid "Number of buttons." msgstr "" #. Tag: entry -#: preparing.xml:477 preparing.xml:505 +#: preparing.xml:481 preparing.xml:509 #, no-c-format msgid "Network" msgstr "" #. Tag: entry -#: preparing.xml:480 preparing.xml:506 +#: preparing.xml:484 preparing.xml:510 #, no-c-format msgid "Type of adapter." msgstr "" #. Tag: entry -#: preparing.xml:483 +#: preparing.xml:487 #, no-c-format msgid "Printer" msgstr "" #. Tag: entry -#: preparing.xml:486 +#: preparing.xml:490 #, no-c-format msgid "Printing resolutions supported." msgstr "" #. Tag: entry -#: preparing.xml:489 +#: preparing.xml:493 #, no-c-format msgid "Video Card" msgstr "" #. Tag: entry -#: preparing.xml:492 +#: preparing.xml:496 #, no-c-format msgid "Video RAM available." msgstr "" #. Tag: entry -#: preparing.xml:494 +#: preparing.xml:498 #, no-c-format msgid "Resolutions and color depths supported (these should be checked against your monitor's capabilities)." msgstr "" #. Tag: entry -#: preparing.xml:499 +#: preparing.xml:503 #, no-c-format msgid "DASD" msgstr "" #. Tag: entry -#: preparing.xml:500 +#: preparing.xml:504 #, no-c-format msgid "Device number(s)." msgstr "" #. Tag: entry -#: preparing.xml:508 +#: preparing.xml:512 #, no-c-format msgid "Device numbers." msgstr "" #. Tag: entry -#: preparing.xml:509 +#: preparing.xml:513 #, no-c-format msgid "Relative adapter number for OSA cards." msgstr "" #. Tag: title -#: preparing.xml:517 +#: preparing.xml:521 #, no-c-format msgid "Hardware Compatibility" msgstr "" #. Tag: para -#: preparing.xml:519 +#: preparing.xml:523 #, no-c-format msgid "Many brand name products work without trouble on Linux. Moreover, hardware for Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems." msgstr "" #. Tag: para -#: preparing.xml:525 +#: preparing.xml:529 #, no-c-format msgid "In particular, Linux usually cannot run hardware that requires a running version of Windows to work." msgstr "" #. Tag: para -#: preparing.xml:530 +#: preparing.xml:534 #, no-c-format msgid "Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete." msgstr "" #. Tag: para -#: preparing.xml:537 +#: preparing.xml:541 #, no-c-format msgid "So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific." msgstr "" #. Tag: para -#: preparing.xml:542 +#: preparing.xml:546 #, no-c-format msgid "You can check hardware compatibility by:" msgstr "" #. Tag: para -#: preparing.xml:547 +#: preparing.xml:551 #, no-c-format msgid "Checking manufacturers' web sites for new drivers." msgstr "" #. Tag: para -#: preparing.xml:552 +#: preparing.xml:556 #, no-c-format msgid "Looking at web sites or manuals for information about emulation. Lesser known brands can sometimes use the drivers or settings for better-known ones." msgstr "" #. Tag: para -#: preparing.xml:559 +#: preparing.xml:563 #, no-c-format msgid "Checking hardware compatibility lists for Linux on web sites dedicated to your architecture." msgstr "" #. Tag: para -#: preparing.xml:565 +#: preparing.xml:569 #, no-c-format msgid "Searching the Internet for other users' experiences." msgstr "" #. Tag: title -#: preparing.xml:576 +#: preparing.xml:580 #, no-c-format msgid "Network Settings" msgstr "" #. Tag: para -#: preparing.xml:578 +#: preparing.xml:582 #, no-c-format msgid "If your computer is connected to a network 24 hours a day (i.e., an Ethernet or equivalent connection — not a PPP connection), you should ask your network's system administrator for this information." msgstr "" #. Tag: para -#: preparing.xml:585 +#: preparing.xml:589 #, no-c-format msgid "Your host name (you may be able to decide this on your own)." msgstr "" #. Tag: para -#: preparing.xml:590 +#: preparing.xml:594 #, no-c-format msgid "Your domain name." msgstr "" #. Tag: para -#: preparing.xml:595 +#: preparing.xml:599 #, no-c-format msgid "Your computer's IP address." msgstr "" #. Tag: para -#: preparing.xml:600 +#: preparing.xml:604 #, no-c-format msgid "The netmask to use with your network." msgstr "" #. Tag: para -#: preparing.xml:605 +#: preparing.xml:609 #, no-c-format msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway." msgstr "" #. Tag: para -#: preparing.xml:611 +#: preparing.xml:615 #, no-c-format msgid "The system on your network that you should use as a DNS (Domain Name Service) server." msgstr "" #. Tag: para -#: preparing.xml:619 +#: preparing.xml:623 #, no-c-format msgid "On the other hand, if your administrator tells you that a DHCP server is available and is recommended, then you don't need this information because the DHCP server will provide it directly to your computer during the installation process." msgstr "" #. Tag: para -#: preparing.xml:626 +#: preparing.xml:630 #, no-c-format msgid "If you use a wireless network, you should also find out:" msgstr "" #. Tag: para -#: preparing.xml:631 +#: preparing.xml:635 #, no-c-format msgid "ESSID of your wireless network." msgstr "" #. Tag: para -#: preparing.xml:636 +#: preparing.xml:640 #, no-c-format msgid "WEP security key (if applicable)." msgstr "" #. Tag: title -#: preparing.xml:653 +#: preparing.xml:657 #, no-c-format msgid "Meeting Minimum Hardware Requirements" msgstr "" #. Tag: para -#: preparing.xml:654 +#: preparing.xml:658 #, no-c-format msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do." msgstr "" #. Tag: para -#: preparing.xml:660 +#: preparing.xml:664 #, no-c-format msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions." msgstr "" #. Tag: para -#: preparing.xml:666 +#: preparing.xml:670 #, no-c-format -msgid "A Pentium 100 is the minimum recommended for desktop systems, and a Pentium II-300 for a Server." +msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop systems." msgstr "" #. Tag: para -#: preparing.xml:671 +#: preparing.xml:675 #, no-c-format msgid "A 68030 or better processor is recommended for m68k installs. You may get by with a little less drive space than shown." msgstr "" #. Tag: para -#: preparing.xml:676 +#: preparing.xml:680 #, no-c-format -msgid "Any OldWorld or NewWorld PowerPC can serve well as a Desktop System. For servers, a minimum 132-Mhz machine is recommended." +msgid "Any OldWorld or NewWorld PowerPC can serve well as a desktop system." msgstr "" #. Tag: title -#: preparing.xml:685 +#: preparing.xml:687 #, no-c-format msgid "Recommended Minimum System Requirements" msgstr "" #. Tag: entry -#: preparing.xml:689 +#: preparing.xml:691 #, no-c-format msgid "Install Type" msgstr "" #. Tag: entry -#: preparing.xml:689 +#: preparing.xml:692 #, no-c-format -msgid "<entry>RAM</entry>" +msgid "RAM (minimal)" msgstr "" #. Tag: entry -#: preparing.xml:689 +#: preparing.xml:693 #, no-c-format -msgid "Hard Drive" +msgid "RAM (recommended)" msgstr "" #. Tag: entry -#: preparing.xml:695 +#: preparing.xml:694 #, no-c-format -msgid "No desktop" -msgstr "" - -#. Tag: entry -#: preparing.xml:696 -#, no-c-format -msgid "24 megabytes" +msgid "Hard Drive" msgstr "" #. Tag: entry -#: preparing.xml:697 +#: preparing.xml:700 #, no-c-format -msgid "450 megabytes" +msgid "No desktop" msgstr "" #. Tag: entry -#: preparing.xml:699 +#: preparing.xml:701 preparing.xml:706 #, no-c-format -msgid "With Desktop" +msgid "64 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:700 +#: preparing.xml:702 #, no-c-format -msgid "64 megabytes" +msgid "256 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:701 +#: preparing.xml:703 #, no-c-format msgid "1 gigabyte" msgstr "" #. Tag: entry -#: preparing.xml:703 +#: preparing.xml:705 #, no-c-format -msgid "Server" +msgid "With Desktop" msgstr "" #. Tag: entry -#: preparing.xml:704 +#: preparing.xml:707 #, no-c-format -msgid "128 megabytes" +msgid "512 megabytes" msgstr "" #. Tag: entry -#: preparing.xml:705 +#: preparing.xml:708 #, no-c-format -msgid "4 gigabytes" +msgid "5 gigabyte" msgstr "" #. Tag: para -#: preparing.xml:710 -#, no-c-format -msgid "Here is a sampling of some common Debian system configurations. You can also get an idea of the disk space used by related groups of programs by referring to <xref linkend=\"tasksel-size-list\"/>." -msgstr "" - -#. Tag: term -#: preparing.xml:720 +#: preparing.xml:713 #, no-c-format -msgid "Standard Server" +msgid "The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install Debian with as little as 20MB (for s390) to 48MB (for i386 and amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see <xref linkend=\"tasksel-size-list\"/> for additional information on disk space requirements." msgstr "" #. Tag: para -#: preparing.xml:721 -#, no-c-format -msgid "This is a small server profile, useful for a stripped down server which does not have a lot of niceties for shell users. It includes an FTP server, a web server, DNS, NIS, and POP. For these 100MB of disk space would suffice, and then you would need to add space for any data you serve up." -msgstr "" - -#. Tag: term -#: preparing.xml:733 +#: preparing.xml:723 #, no-c-format -msgid "Desktop" +msgid "It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include <classname>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from." msgstr "" #. Tag: para -#: preparing.xml:734 -#, no-c-format -msgid "A standard desktop box, including the X window system, full desktop environments, sound, editors, etc. You'll need about 2GB using the standard desktop task, though it can be done in far less." -msgstr "" - -#. Tag: term -#: preparing.xml:744 +#: preparing.xml:732 #, no-c-format -msgid "Work Console" +msgid "It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for." msgstr "" #. Tag: para -#: preparing.xml:745 -#, no-c-format -msgid "A more stripped-down user machine, without the X window system or X applications. Possibly suitable for a laptop or mobile computer. The size is around 140MB." -msgstr "" - -#. Tag: term -#: preparing.xml:755 +#: preparing.xml:738 #, no-c-format -msgid "Developer" +msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data." msgstr "" #. Tag: para -#: preparing.xml:756 -#, no-c-format -msgid "A desktop setup with all the development packages, such as Perl, C, C++, etc. Size is around 475MB. Assuming you are adding X11 and some additional packages for other uses, you should plan around 800MB for this type of machine." -msgstr "" - -#. Tag: para -#: preparing.xml:766 +#: preparing.xml:745 #, no-c-format -msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 20MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 100MB for <filename>/var</filename>." +msgid "Disk space required for the smooth operation of the &debian; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment." msgstr "" #. Tag: title -#: preparing.xml:790 +#: preparing.xml:769 #, no-c-format msgid "Pre-Partitioning for Multi-Boot Systems" msgstr "" #. Tag: para -#: preparing.xml:791 +#: preparing.xml:770 #, no-c-format msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room." msgstr "" #. Tag: para -#: preparing.xml:798 +#: preparing.xml:777 #, no-c-format msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case." msgstr "" #. Tag: para -#: preparing.xml:804 +#: preparing.xml:783 #, no-c-format msgid "If you already have an operating system on your system <phrase arch=\"x86\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac OS, …) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root." msgstr "" #. Tag: para -#: preparing.xml:831 +#: preparing.xml:810 #, no-c-format msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"x86\">, such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"m68k\">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes." msgstr "" #. Tag: para -#: preparing.xml:841 +#: preparing.xml:820 #, no-c-format msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it." msgstr "" #. Tag: emphasis -#: preparing.xml:851 +#: preparing.xml:830 #, no-c-format msgid "FIXME: write about HP-UX disks?" msgstr "" #. Tag: para -#: preparing.xml:853 +#: preparing.xml:832 #, no-c-format msgid "If your computer has more than one hard disk, you may want to dedicate one of the hard disks completely to Debian. If so, you don't need to partition that disk before booting the installation system; the installer's included partitioning program can handle the job nicely." msgstr "" #. Tag: para -#: preparing.xml:860 +#: preparing.xml:839 #, no-c-format msgid "If your machine has only one hard disk, and you would like to completely replace the current operating system with &debian;, you also can wait to partition as part of the installation process (<xref linkend=\"partman\"/>), after you have booted the installation system. However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine. Consider: if you boot from files placed on the hard disk, and then partition that same hard disk within the installation system, thus erasing the boot files, you'd better hope the installation is successful the first time around. At the least in this case, you should have some alternate means of reviving your machine like the original system's installation tapes or CDs." msgstr "" #. Tag: para -#: preparing.xml:875 +#: preparing.xml:854 #, no-c-format msgid "If your machine already has multiple partitions, and enough space can be provided by deleting and replacing one or more of them, then you too can wait and use the Debian installer's partitioning program. You should still read through the material below, because there may be special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway." msgstr "" #. Tag: para -#: preparing.xml:885 +#: preparing.xml:864 #, no-c-format msgid "If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, you can wait and use Debian installer's partitioning program to resize the filesystem." msgstr "" #. Tag: para -#: preparing.xml:891 +#: preparing.xml:870 #, no-c-format msgid "If none of the above apply, you'll need to partition your hard disk before starting the installation to create partition-able space for Debian. If some of the partitions will be owned by other operating systems, you should create those partitions using native operating system partitioning programs. We recommend that you do <emphasis>not</emphasis> attempt to create partitions for &debian; using another operating system's tools. Instead, you should just create the native operating system's partitions you will want to retain." msgstr "" #. Tag: para -#: preparing.xml:903 +#: preparing.xml:882 #, no-c-format msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with Linux installation. Windows and other OS installations may destroy your ability to start Linux, or encourage you to reformat non-native partitions." msgstr "" #. Tag: para -#: preparing.xml:911 +#: preparing.xml:890 #, no-c-format msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble." msgstr "" #. Tag: para -#: preparing.xml:916 +#: preparing.xml:895 #, no-c-format msgid "In order for OpenFirmware to automatically boot &debian; the Linux partitions should appear before all other partitions on the disk, especially MacOS boot partitions. This should be kept in mind when pre-partitioning; you should create a Linux placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the Linux partition tools later during the actual install, and replace it with Linux partitions." msgstr "" #. Tag: para -#: preparing.xml:928 +#: preparing.xml:907 #, no-c-format msgid "If you currently have one hard disk with one partition (a common setup for desktop computers), and you want to multi-boot the native operating system and Debian, you will need to:" msgstr "" #. Tag: para -#: preparing.xml:935 +#: preparing.xml:914 #, no-c-format msgid "Back up everything on the computer." msgstr "" #. Tag: para -#: preparing.xml:940 +#: preparing.xml:919 #, no-c-format msgid "Boot from the native operating system installer media such as CD-ROM or tapes. <phrase arch=\"powerpc\">When booting from a MacOS CD, hold the <keycap>c</keycap> key while booting to force the CD to become the active MacOS system.</phrase>" msgstr "" #. Tag: para -#: preparing.xml:950 +#: preparing.xml:929 #, no-c-format msgid "Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for &debian;." msgstr "" #. Tag: para -#: preparing.xml:957 +#: preparing.xml:936 #, no-c-format msgid "Install the native operating system on its new partition." msgstr "" #. Tag: para -#: preparing.xml:962 +#: preparing.xml:941 #, no-c-format msgid "Boot back into the native system to verify everything's OK, and to download the Debian installer boot files." msgstr "" #. Tag: para -#: preparing.xml:968 +#: preparing.xml:947 #, no-c-format msgid "Boot the Debian installer to continue installing Debian." msgstr "" #. Tag: title -#: preparing.xml:982 +#: preparing.xml:961 #, no-c-format msgid "Partitioning in Tru64 UNIX" msgstr "" #. Tag: para -#: preparing.xml:983 +#: preparing.xml:962 #, no-c-format msgid "Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk label</quote>, which allows for up to eight partitions per disk drive. The partitions are numbered <quote>1</quote> through to <quote>8</quote> in Linux and <quote>lettered</quote> <quote>a</quote> through to <quote>h</quote> in UNIX. Linux kernels 2.2 and higher always correspond <quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote> and so on. For example, <filename>rz0e</filename> in Tru64 UNIX would most likely be called <filename>sda5</filename> in Linux." msgstr "" #. Tag: para -#: preparing.xml:995 +#: preparing.xml:974 #, no-c-format msgid "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will be used from Tru64, the <quote>c</quote> partition is required to span the entire disk (thus overlapping all other non-empty partitions). Under Linux this makes <filename>sda3</filename> identical to <filename>sda</filename> (<filename>sdb3</filename> to <filename>sdb</filename>, if present, and so on). However, the partman partitioning tool used by &d-i; cannot handle overlapping partitions at present. As a result, it is currently not recommended to share disks between Tru64 and Debian. Partitions on Tru64 disks can be mounted under Debian after installation has been completed." msgstr "" #. Tag: para -#: preparing.xml:1008 +#: preparing.xml:987 #, no-c-format msgid "Another conventional requirement is for the <quote>a</quote> partition to start from the beginning of the disk, so that it always includes the boot block with the disk label. If you intend to boot Debian from that disk, you need to size it at least 2MB to fit aboot and perhaps a kernel. Note that this partition is only required for compatibility; you must not put a file system onto it, or you'll destroy data." msgstr "" #. Tag: para -#: preparing.xml:1017 +#: preparing.xml:996 #, no-c-format msgid "It is possible, and indeed quite reasonable, to share a swap partition between UNIX and Linux. In this case it will be needed to do a <command>mkswap</command> on that partition every time the system is rebooted from UNIX into Linux, as UNIX will damage the swap signature. You may want to run <command>mkswap</command> from the Linux start-up scripts before adding swap space with <command>swapon -a</command>." msgstr "" #. Tag: para -#: preparing.xml:1026 +#: preparing.xml:1005 #, no-c-format msgid "If you want to mount UNIX partitions under Linux, note that Digital UNIX can use two different file system types, UFS and AdvFS, of which Linux only understands the former." msgstr "" #. Tag: title -#: preparing.xml:1035 +#: preparing.xml:1014 #, no-c-format msgid "Partitioning in Windows NT" msgstr "" #. Tag: para -#: preparing.xml:1037 +#: preparing.xml:1016 #, no-c-format msgid "Windows NT uses the PC-style partition table. If you are manipulating existing FAT or NTFS partitions, it is recommended that you use the native Windows NT tools (or, more conveniently, you can also repartition your disk from the AlphaBIOS setup menu). Otherwise, it is not really necessary to partition from Windows; the Linux partitioning tools will generally do a better job. Note that when you run NT, the Disk Administrator may offer to write a <quote>harmless signature</quote> on non-Windows disks if you have any. <emphasis>Never</emphasis> let it do that, as this signature will destroy the partition information." msgstr "" #. Tag: para -#: preparing.xml:1050 +#: preparing.xml:1029 #, no-c-format msgid "If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you will need a (small) FAT partition for MILO. 5 MB is quite sufficient. If Windows NT is installed, its 6 MB bootstrap partition can be employed for this purpose. Debian &releasename; does not support installing MILO. If you already have MILO installed on your system, or install MILO from other media, Debian can still be booted from ARC." msgstr "" #. Tag: title -#: preparing.xml:1067 +#: preparing.xml:1046 #, no-c-format msgid "Partitioning From DOS or Windows" msgstr "" #. Tag: para -#: preparing.xml:1068 +#: preparing.xml:1047 #, no-c-format msgid "If you are manipulating existing FAT or NTFS partitions, it is recommended that you either use the scheme below or native Windows or DOS tools. Otherwise, it is not really necessary to partition from DOS or Windows; the Linux partitioning tools will generally do a better job." msgstr "" #. Tag: para -#: preparing.xml:1076 +#: preparing.xml:1055 #, no-c-format msgid "But if you have a large IDE disk, and are not using LBA addressing, overlay drivers (sometimes provided by hard disk manufacturers), or a new (post 1998) BIOS that supports large disk access extensions, then you must locate your Debian boot partition carefully. In this case, you will have to put the boot partition into the first 1024 cylinders of your hard disk (usually around 524 megabytes, without BIOS translation). This may require that you move an existing FAT or NTFS partition." msgstr "" #. Tag: title -#: preparing.xml:1090 +#: preparing.xml:1069 #, no-c-format msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2" msgstr "" #. Tag: para -#: preparing.xml:1093 +#: preparing.xml:1072 #, no-c-format msgid "One of the most common installations is onto a system that already contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, NT, 2000, XP), or OS/2, and it is desired to put Debian onto the same disk without destroying the previous system. Note that the installer supports resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply start the installer and when you get to the partitioning step, select the option for <menuchoice> <guimenuitem>Manual</guimenuitem> </menuchoice> partitioning, select the partition to resize, and specify its new size. So in most cases you should not need to use the method described below." msgstr "" #. Tag: para -#: preparing.xml:1105 +#: preparing.xml:1084 #, no-c-format msgid "Before going any further, you should have decided how you will be dividing up the disk. The method in this section will only split a partition into two pieces. One will contain the original OS and the other will be used for Debian. During the installation of Debian, you will be given the opportunity to use the Debian portion of the disk as you see fit, i.e., as swap or as a file system." msgstr "" #. Tag: para -#: preparing.xml:1114 +#: preparing.xml:1093 #, no-c-format msgid "The idea is to move all the data on the partition to the beginning, before changing the partition information, so that nothing will be lost. It is important that you do as little as possible between the data movement and repartitioning to minimize the chance of a file being written near the end of the partition as this will decrease the amount of space you can take from the partition." msgstr "" #. Tag: para -#: preparing.xml:1123 +#: preparing.xml:1102 #, no-c-format msgid "The first thing needed is a copy of <command>fips</command> which is available in the <filename>tools/</filename> directory on your nearest Debian mirror. Unzip the archive and copy the files <filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and <filename>ERRORS.TXT</filename> to a bootable floppy. A bootable floppy can be created using the command <filename>sys a:</filename> under DOS. <command>fips</command> comes with very good documentation which you may want to read. You will definitely need to read the documentation if you use a disk compression driver or a disk manager. Create the disk and read the documentation <emphasis>before</emphasis> you defragment the disk." msgstr "" #. Tag: para -#: preparing.xml:1136 +#: preparing.xml:1115 #, no-c-format msgid "The next thing needed is to move all the data to the beginning of the partition. <command>defrag</command>, which comes standard with DOS 6.0 and later, can easily do the job. See the <command>fips</command> documentation for a list of other software that may do the trick. Note that if you have Windows 9x, you must run <command>defrag</command> from there, since DOS doesn't understand VFAT, which is used to support for long filenames, used in Windows 95 and higher." msgstr "" #. Tag: para -#: preparing.xml:1146 +#: preparing.xml:1125 #, no-c-format msgid "After running the defragmenter (which can take a while on a large disk), reboot with the <command>fips</command> disk you created in the floppy drive. Simply type <filename>a:\\fips</filename> and follow the directions." msgstr "" #. Tag: para -#: preparing.xml:1152 +#: preparing.xml:1131 #, no-c-format msgid "Note that there are many other partition managers out there, in case <command>fips</command> doesn't do the trick for you." msgstr "" #. Tag: title -#: preparing.xml:1160 +#: preparing.xml:1139 #, no-c-format msgid "Partitioning for DOS" msgstr "" #. Tag: para -#: preparing.xml:1162 +#: preparing.xml:1141 #, no-c-format msgid "If you are partitioning for DOS drives, or changing the size of DOS partitions, using Linux tools, many people experience problems working with the resulting FAT partitions. For instance, some have reported slow performance, consistent problems with <command>scandisk</command>, or other weird errors in DOS or Windows." msgstr "" #. Tag: para -#: preparing.xml:1170 +#: preparing.xml:1149 #, no-c-format msgid "Apparently, whenever you create or resize a partition for DOS use, it's a good idea to fill the first few sectors with zeros. You should do this prior to running DOS's <command>format</command> command by executing the following command from Linux:" msgstr "" #. Tag: screen -#: preparing.xml:1177 +#: preparing.xml:1156 #, no-c-format msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" msgstr "" #. Tag: title -#: preparing.xml:1188 +#: preparing.xml:1167 #, no-c-format msgid "Partitioning in AmigaOS" msgstr "" #. Tag: para -#: preparing.xml:1189 +#: preparing.xml:1168 #, no-c-format msgid "If you are running AmigaOS, you can use the <command>HDToolBox</command> program to adjust your native partitions prior to installation." msgstr "" #. Tag: title -#: preparing.xml:1197 +#: preparing.xml:1176 #, no-c-format msgid "Partitioning in Atari TOS" msgstr "" #. Tag: para -#: preparing.xml:1198 +#: preparing.xml:1177 #, no-c-format msgid "Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for data and <quote>SWP</quote> for swap partitions. If using the low memory installation method, a small Minix partition is also needed (about 2 MB), for which the partition ID is <quote>MNX</quote>. Failure to set the appropriate partition IDs not only prevents the Debian installation process from recognizing the partitions, but also results in TOS attempting to use the Linux partitions, which confuses the hard disk driver and renders the whole disk inaccessible." msgstr "" #. Tag: para -#: preparing.xml:1209 +#: preparing.xml:1188 #, no-c-format msgid "There are a multitude of third party partitioning tools available (the Atari <command>harddisk</command> utility doesn't permit changing the partition ID); this manual cannot give detailed descriptions for all of them. The following description covers <command>SCSITool</command> (from Hard+Soft GmBH)." msgstr "" #. Tag: para -#: preparing.xml:1218 +#: preparing.xml:1197 #, no-c-format msgid "Start <command>SCSITool</command> and select the disk you want to partition (<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>)." msgstr "" #. Tag: para -#: preparing.xml:1224 +#: preparing.xml:1203 #, no-c-format msgid "From the <guimenu>Partition</guimenu> menu, select either <guimenuitem>New</guimenuitem> to add new partitions or change the existing partition sizes, or <guimenuitem>Change</guimenuitem> to change one specific partition. Unless you have already created partitions with the right sizes and only want to change the partition ID, <guimenuitem>New</guimenuitem> is probably the best choice." msgstr "" #. Tag: para -#: preparing.xml:1234 +#: preparing.xml:1213 #, no-c-format msgid "For the <guimenuitem>New</guimenuitem> choice, select <guilabel>existing</guilabel> in the dialog box prompting the initial settings. The next window shows a list of existing partitions which you can adjust using the scroll buttons, or by clicking in the bar graphs. The first column in the partition list is the partition type; just click on the text field to edit it. When you are finished changing partition settings, save the changes by leaving the window with the <guibutton>OK</guibutton> button." msgstr "" #. Tag: para -#: preparing.xml:1246 +#: preparing.xml:1225 #, no-c-format msgid "For the <guimenuitem>Change</guimenuitem> option, select the partition to change in the selection list, and select <guilabel>other systems</guilabel> in the dialog box. The next window lists detailed information about the location of this partition, and lets you change the partition ID. Save changes by leaving the window with the <guibutton>OK</guibutton> button." msgstr "" #. Tag: para -#: preparing.xml:1256 +#: preparing.xml:1235 #, no-c-format msgid "Write down the Linux names for each of the partitions you created or changed for use with Linux — see <xref linkend=\"device-names\"/>." msgstr "" #. Tag: para -#: preparing.xml:1262 +#: preparing.xml:1241 #, no-c-format msgid "Quit <command>SCSITool</command> using the <guimenuitem>Quit</guimenuitem> item from the <guimenu>File</guimenu> menu. The computer will reboot to make sure the changed partition table is used by TOS. If you changed any TOS/GEM partitions, they will be invalidated and have to be reinitialized (we told you to back up everything on the disk, didn't we?)." msgstr "" #. Tag: para -#: preparing.xml:1274 +#: preparing.xml:1253 #, no-c-format msgid "There is a partitioning tool for Linux/m68k called <command>atari-fdisk</command> in the installation system, but for now we recommend you partition your disk using a TOS partition editor or some disk tool. If your partition editor doesn't have an option to edit the partition type, you can do this crucial step at a later stage (from the booted temporary install RAMdisk). <command>SCSITool</command> is only one of the partition editors we know of which supports selection of arbitrary partition types. There may be others; select the tool that suits your needs." msgstr "" #. Tag: title -#: preparing.xml:1289 +#: preparing.xml:1268 #, no-c-format msgid "Partitioning in MacOS" msgstr "" #. Tag: para -#: preparing.xml:1290 +#: preparing.xml:1269 #, no-c-format msgid "Partitioning tools for Macintosh tested include <command>pdisk</command>, <command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 (FWB), <command>SilverLining</command> (LaCie), and <command>DiskTool</command> (Tim Endres, GPL). Full versions are required for <command>HDT</command> and <command>SilverLining</command>. The Apple tool requires a patch in order to recognize third-party disks (a description on how to patch <command>HD SC Setup</command> using <command>ResEdit</command> can be found at <ulink url=\"http://www.euronet.nl/users/ernstoud/patch.html\"></ulink>)." msgstr "" #. Tag: para -#: preparing.xml:1301 +#: preparing.xml:1280 #, no-c-format msgid "For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create empty space for the Linux partitions, and complete the partitioning under Linux, or use the MacOS version of pdisk available for download from <ulink url=\"http://homepage.mac.com/alk/downloads/pdisk.sit.hqx\">Alsoft</ulink>." msgstr "" #. Tag: title -#: preparing.xml:1317 +#: preparing.xml:1296 #, no-c-format msgid "Partitioning from SunOS" msgstr "" #. Tag: para -#: preparing.xml:1319 +#: preparing.xml:1298 #, no-c-format -msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and Debian on the same machine, it is recommended that you partition using SunOS prior to installing Debian. The Linux kernel understands Sun disk labels, so there are no problems there. Just make sure you leave room for the Debian root partition within the first 1GB area of the boot disk. You can also place the kernel image on a UFS partition if that is easier than putting the root partition there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions." +msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and Debian on the same machine, it is recommended that you partition using SunOS prior to installing Debian. The Linux kernel understands Sun disk labels, so there are no problems there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions." msgstr "" #. Tag: title -#: preparing.xml:1334 +#: preparing.xml:1310 #, no-c-format msgid "Partitioning from Linux or another OS" msgstr "" #. Tag: para -#: preparing.xml:1336 +#: preparing.xml:1312 #, no-c-format msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur." msgstr "" #. Tag: para -#: preparing.xml:1348 +#: preparing.xml:1324 #, no-c-format msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>." msgstr "" #. Tag: title -#: preparing.xml:1363 +#: preparing.xml:1339 #, no-c-format msgid "MacOS/OSX Partitioning" msgstr "" #. Tag: para -#: preparing.xml:1365 +#: preparing.xml:1341 #, no-c-format msgid "The <application>Apple Drive Setup</application> application can be found in the <filename>Utilities</filename> folder on the MacOS CD. It will not adjust existing partitions; it is limited to partitioning the entire disk at once. The disk driver partitions don't show up in <application>Drive Setup</application>." msgstr "" #. Tag: para -#: preparing.xml:1372 +#: preparing.xml:1348 #, no-c-format msgid "Remember to create a placeholder partition for GNU/Linux, preferably positioned first in the disk layout. it doesn't matter what type it is, it will be deleted and replaced later inside the &debian; installer." msgstr "" #. Tag: para -#: preparing.xml:1378 +#: preparing.xml:1354 #, no-c-format msgid "If you are planning to install both MacOS 9 and OS X, it is best to create separate partitions for OS 9 and OS X. If they are installed on the same partition, <application>Startup Disk</application> (and reboot) must be used to select between the two; the choice between the two systems can't be made at boot time. With separate partitions, separate options for OS 9 and OS X will appear when holding the <keycap>option</keycap> key at boot time, and separate options can be installed in the <application>yaboot</application> boot menu as well. Also, Startup Disk will de-bless all other mountable partitions, which can affect GNU/Linux booting. Both OS 9 and OS X partitions will be accessible from either OS 9 or OS X." msgstr "" #. Tag: para -#: preparing.xml:1391 +#: preparing.xml:1367 #, no-c-format msgid "GNU/Linux is unable to access information on UFS partitions, but does support HFS+ (aka MacOS Extended) partitions. OS X requires one of these two types for its boot partition. MacOS 9 can be installed on either HFS (aka MacOS Standard) or HFS+. To share information between the MacOS and GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT partitions are supported by both MacOS and Linux." msgstr "" #. Tag: title -#: preparing.xml:1411 +#: preparing.xml:1387 #, no-c-format msgid "Pre-Installation Hardware and Operating System Setup" msgstr "" #. Tag: para -#: preparing.xml:1412 +#: preparing.xml:1388 #, no-c-format msgid "This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for your system. The <quote>firmware</quote> is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up). Known hardware issues affecting the reliability of &debian; on your system are also highlighted." msgstr "" #. Tag: title -#: preparing.xml:1434 +#: preparing.xml:1410 #, no-c-format msgid "Invoking the BIOS Set-Up Menu" msgstr "" #. Tag: para -#: preparing.xml:1436 +#: preparing.xml:1412 #, no-c-format msgid "BIOS provides the basic functions needed to boot your machine to allow your operating system to access your hardware. Your system probably provides a BIOS set-up menu, which is used to configure the BIOS. Before installing, you <emphasis>must</emphasis> ensure that your BIOS is setup correctly; not doing so can lead to intermittent crashes or an inability to install Debian." msgstr "" #. Tag: para -#: preparing.xml:1445 +#: preparing.xml:1421 #, no-c-format msgid "The rest of this section is lifted from the <ulink url=\"&url-pc-hw-faq;\"></ulink>, answering the question, <quote>How do I enter the CMOS configuration menu?</quote>. How you access the BIOS (or <quote>CMOS</quote>) configuration menu depends on who wrote your BIOS software:" msgstr "" #. Tag: term -#: preparing.xml:1459 +#: preparing.xml:1435 #, no-c-format msgid "AMI BIOS" msgstr "" #. Tag: para -#: preparing.xml:1460 +#: preparing.xml:1436 #, no-c-format msgid "<keycap>Delete</keycap> key during the POST (power on self test)" msgstr "" #. Tag: term -#: preparing.xml:1468 +#: preparing.xml:1444 #, no-c-format msgid "Award BIOS" msgstr "" #. Tag: para -#: preparing.xml:1469 +#: preparing.xml:1445 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo>, or <keycap>Delete</keycap> key during the POST" msgstr "" #. Tag: term -#: preparing.xml:1478 +#: preparing.xml:1454 #, no-c-format msgid "DTK BIOS" msgstr "" #. Tag: para -#: preparing.xml:1479 +#: preparing.xml:1455 #, no-c-format msgid "<keycap>Esc</keycap> key during the POST" msgstr "" #. Tag: term -#: preparing.xml:1486 +#: preparing.xml:1462 #, no-c-format msgid "IBM PS/2 BIOS" msgstr "" #. Tag: para -#: preparing.xml:1487 +#: preparing.xml:1463 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> </keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap> </keycombo>" msgstr "" #. Tag: term -#: preparing.xml:1501 +#: preparing.xml:1477 #, no-c-format msgid "Phoenix BIOS" msgstr "" #. Tag: para -#: preparing.xml:1502 +#: preparing.xml:1478 #, no-c-format msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo> or <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> </keycombo> or <keycap>F1</keycap>" msgstr "" #. Tag: para -#: preparing.xml:1518 +#: preparing.xml:1494 #, no-c-format msgid "Information on invoking other BIOS routines can be found in <ulink url=\"&url-invoking-bios-info;\"></ulink>." msgstr "" #. Tag: para -#: preparing.xml:1523 +#: preparing.xml:1499 #, no-c-format msgid "Some &arch-title; machines don't have a CMOS configuration menu in the BIOS. They require a software CMOS setup program. If you don't have the Installation and/or Diagnostics diskette for your machine, you can try using a shareware/freeware program. Try looking in <ulink url=\"&url-simtel;\"></ulink>." msgstr "" #. Tag: title -#: preparing.xml:1534 preparing.xml:1878 +#: preparing.xml:1510 preparing.xml:1854 #, no-c-format msgid "Boot Device Selection" msgstr "" #. Tag: para -#: preparing.xml:1536 +#: preparing.xml:1512 #, no-c-format msgid "Many BIOS set-up menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on <filename>A:</filename> (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:</filename>), and then from <filename>C:</filename> (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian." msgstr "" #. Tag: para -#: preparing.xml:1547 +#: preparing.xml:1523 #, no-c-format msgid "If you have a newer SCSI controller and you have a CD-ROM device attached to it, you are usually able to boot from the CD-ROM. All you have to do is enable booting from a CD-ROM in the SCSI-BIOS of your controller." msgstr "" #. Tag: para -#: preparing.xml:1554 +#: preparing.xml:1530 #, no-c-format msgid "Another popular option is to boot from a USB storage device (also called a USB memory stick or USB key). Some BIOSes can boot directly from a USB storage device, but some cannot. You may need to configure your BIOS to boot from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to get it to boot from the USB device." msgstr "" #. Tag: para -#: preparing.xml:1562 +#: preparing.xml:1538 #, no-c-format msgid "Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive." msgstr "" #. Tag: title -#: preparing.xml:1571 +#: preparing.xml:1547 #, no-c-format msgid "Changing the Boot Order on IDE Computers" msgstr "" #. Tag: para -#: preparing.xml:1574 +#: preparing.xml:1550 #, no-c-format msgid "As your computer starts, press the keys to enter the BIOS utility. Often, it is the <keycap>Delete</keycap> key. However, consult the hardware documentation for the exact keystrokes." msgstr "" #. Tag: para -#: preparing.xml:1581 +#: preparing.xml:1557 #, no-c-format msgid "Find the boot sequence in the setup utility. Its location depends on your BIOS, but you are looking for a field that lists drives." msgstr "" #. Tag: para -#: preparing.xml:1586 +#: preparing.xml:1562 #, no-c-format msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." msgstr "" #. Tag: para -#: preparing.xml:1591 +#: preparing.xml:1567 #, no-c-format msgid "C is the hard drive, and A is the floppy drive." msgstr "" #. Tag: para -#: preparing.xml:1597 +#: preparing.xml:1573 #, no-c-format msgid "Change the boot sequence setting so that the CD-ROM or the floppy is first. Usually, the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> keys cycle through the possible choices." msgstr "" #. Tag: para -#: preparing.xml:1605 +#: preparing.xml:1581 #, no-c-format msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer." msgstr "" #. Tag: title -#: preparing.xml:1615 +#: preparing.xml:1591 #, no-c-format msgid "Changing the Boot Order on SCSI Computers" msgstr "" #. Tag: para -#: preparing.xml:1619 +#: preparing.xml:1595 #, no-c-format msgid "As your computer starts, press the keys to enter the SCSI setup utility." msgstr "" #. Tag: para -#: preparing.xml:1624 +#: preparing.xml:1600 #, no-c-format msgid "You can start the SCSI setup utility after the memory check and the message about how to start the BIOS utility displays when you start your computer." msgstr "" #. Tag: para -#: preparing.xml:1630 +#: preparing.xml:1606 #, no-c-format msgid "The keystrokes you need depend on the utility. Often, it is <keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. However, consult your hardware documentation for the exact keystrokes." msgstr "" #. Tag: para -#: preparing.xml:1638 +#: preparing.xml:1614 #, no-c-format msgid "Find the utility for changing the boot order." msgstr "" #. Tag: para -#: preparing.xml:1643 +#: preparing.xml:1619 #, no-c-format msgid "Set the utility so that the SCSI ID of the CD drive is first on the list." msgstr "" #. Tag: para -#: preparing.xml:1649 +#: preparing.xml:1625 #, no-c-format msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer. Often, you must press <keycap>F10</keycap>." msgstr "" #. Tag: title -#: preparing.xml:1663 +#: preparing.xml:1639 #, no-c-format msgid "Miscellaneous BIOS Settings" msgstr "" #. Tag: title -#: preparing.xml:1665 +#: preparing.xml:1641 #, no-c-format msgid "CD-ROM Settings" msgstr "" #. Tag: para -#: preparing.xml:1666 +#: preparing.xml:1642 #, no-c-format msgid "Some BIOS systems (such as Award BIOS) allow you to automatically set the CD speed. You should avoid that, and instead set it to, say, the lowest speed. If you get <userinput>seek failed</userinput> error messages, this may be your problem." msgstr "" #. Tag: title -#: preparing.xml:1676 +#: preparing.xml:1652 #, no-c-format msgid "Extended vs. Expanded Memory" msgstr "" #. Tag: para -#: preparing.xml:1677 +#: preparing.xml:1653 #, no-c-format msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory." msgstr "" #. Tag: title -#: preparing.xml:1687 +#: preparing.xml:1663 #, no-c-format msgid "Virus Protection" msgstr "" #. Tag: para -#: preparing.xml:1688 +#: preparing.xml:1664 #, no-c-format msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>." msgstr "" #. Tag: title -#: preparing.xml:1709 +#: preparing.xml:1685 #, no-c-format msgid "Shadow RAM" msgstr "" #. Tag: para -#: preparing.xml:1710 +#: preparing.xml:1686 #, no-c-format msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices." msgstr "" #. Tag: title -#: preparing.xml:1727 +#: preparing.xml:1703 #, no-c-format msgid "Memory Hole" msgstr "" #. Tag: para -#: preparing.xml:1728 +#: preparing.xml:1704 #, no-c-format msgid "If your BIOS offers something like <quote>15–16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM." msgstr "" #. Tag: para -#: preparing.xml:1734 +#: preparing.xml:1710 #, no-c-format msgid "We have a report of an Intel Endeavor motherboard on which there is an option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device — it just worked with that setting and not without it." msgstr "" #. Tag: title -#: preparing.xml:1750 +#: preparing.xml:1726 #, no-c-format msgid "Advanced Power Management" msgstr "" #. Tag: para -#: preparing.xml:1751 +#: preparing.xml:1727 #, no-c-format msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS." msgstr "" #. Tag: title -#: preparing.xml:1769 +#: preparing.xml:1745 #, no-c-format msgid "Firmware Revisions and Existing OS Setup" msgstr "" #. Tag: para -#: preparing.xml:1771 +#: preparing.xml:1747 #, no-c-format msgid "&arch-title; machines are generally self-configuring and do not require firmware configuration. However, you should make sure that you have the appropriate ROM and system patches. On the Macintosh, MacOS version >= 7.1 is recommended because version 7.0.1 contains a bug in the video drivers preventing the boot loader from deactivating the video interrupts, resulting in a boot hang. On the BVM VMEbus systems you should make sure you are using BVMBug revision G or higher boot ROMs. The BVMBug boot ROMs do not come as standard on the BVM systems but are available from BVM on request free of charge." msgstr "" #. Tag: title -#: preparing.xml:1794 +#: preparing.xml:1770 #, no-c-format msgid "Invoking OpenFirmware" msgstr "" #. Tag: para -#: preparing.xml:1795 +#: preparing.xml:1771 #, no-c-format msgid "There is normally no need to set up the BIOS (called OpenFirmware) on &arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but unfortunately, the means you use to invoke it vary from manufacturer to manufacturer. You'll have to consult the hardware documentation which came with your machine." msgstr "" #. Tag: para -#: preparing.xml:1803 +#: preparing.xml:1779 #, no-c-format msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command</keycap> <keycap>option</keycap> <keycap>O</keycap> <keycap>F</keycap></keycombo> while booting. Generally it will check for these keystrokes after the chime, but the exact timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more hints." msgstr "" #. Tag: para -#: preparing.xml:1812 +#: preparing.xml:1788 #, no-c-format msgid "" "The OpenFirmware prompt looks like this: <informalexample><screen>\n" @@ -1657,43 +1621,43 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1825 +#: preparing.xml:1801 #, no-c-format msgid "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, is broken. These machines will most likely not be able to boot from the hard drive unless the firmware is patched. A firmware patch is included in the <application>System Disk 2.3.1</application> utility, available from Apple at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, and launching it, select the <guibutton>Save button</guibutton> to have the firmware patches installed to nvram." msgstr "" #. Tag: title -#: preparing.xml:1845 +#: preparing.xml:1821 #, no-c-format msgid "Invoking OpenBoot" msgstr "" #. Tag: para -#: preparing.xml:1847 +#: preparing.xml:1823 #, no-c-format msgid "OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics and simple scripts." msgstr "" #. Tag: para -#: preparing.xml:1855 +#: preparing.xml:1831 #, no-c-format msgid "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>></userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt." msgstr "" #. Tag: para -#: preparing.xml:1867 +#: preparing.xml:1843 #, no-c-format msgid "If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program." msgstr "" #. Tag: para -#: preparing.xml:1880 +#: preparing.xml:1856 #, no-c-format msgid "You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's considerably different from Linux device naming, described in <xref linkend=\"device-names\"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>." msgstr "" #. Tag: para -#: preparing.xml:1890 +#: preparing.xml:1866 #, no-c-format msgid "" "Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form: <informalexample> <screen>\n" @@ -1704,7 +1668,7 @@ msgid "" msgstr "" #. Tag: para -#: preparing.xml:1913 +#: preparing.xml:1889 #, no-c-format msgid "" "To boot from a specific device, use the command <userinput>boot <replaceable>device</replaceable></userinput>. You can set this behavior as the default using the <userinput>setenv</userinput> command. However, the name of the variable to set changed between OpenBoot revisions. In OpenBoot 1.x, use the command <userinput>setenv boot-from <replaceable>device</replaceable></userinput>. In later revisions of OpenBoot, use the command <userinput>setenv boot-device <replaceable>device</replaceable></userinput>. Note, this is also configurable using the <command>eeprom</command> command on Solaris, or modifying the appropriate files in <filename>/proc/openprom/options/</filename>, for example under Linux: <informalexample><screen>\n" @@ -1713,121 +1677,121 @@ msgid "" msgstr "" #. Tag: screen -#: preparing.xml:1932 +#: preparing.xml:1908 #, no-c-format msgid "eeprom boot-device=disk1:1" msgstr "" #. Tag: title -#: preparing.xml:1942 +#: preparing.xml:1918 #, no-c-format msgid "BIOS Setup" msgstr "" #. Tag: para -#: preparing.xml:1943 +#: preparing.xml:1919 #, no-c-format msgid "In order to install &debian; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based." msgstr "" #. Tag: para -#: preparing.xml:1955 +#: preparing.xml:1931 #, no-c-format msgid "Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. You can use a boot tape on all of those systems; you may use some other boot media, too, but those may not be generally available. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you." msgstr "" #. Tag: para -#: preparing.xml:1965 +#: preparing.xml:1941 #, no-c-format msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually to boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of Debian-specific data is needed and where to find it. Using both sources of information, you have to prepare your machine and the installation medium before you can perform a boot from it. When you see the welcome message in your client session, return to this document to go through the Debian-specific installation steps." msgstr "" #. Tag: title -#: preparing.xml:1982 +#: preparing.xml:1958 #, no-c-format msgid "Native and LPAR installations" msgstr "" #. Tag: para -#: preparing.xml:1983 +#: preparing.xml:1959 #, no-c-format msgid "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up an LPAR for Linux." msgstr "" #. Tag: title -#: preparing.xml:1997 +#: preparing.xml:1973 #, no-c-format msgid "Installation as a VM guest" msgstr "" #. Tag: para -#: preparing.xml:1999 +#: preparing.xml:1975 #, no-c-format msgid "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up a VM guest for running Linux." msgstr "" #. Tag: para -#: preparing.xml:2009 +#: preparing.xml:1985 #, no-c-format msgid "You need to copy all the files from the <filename>generic</filename> sub-directory to your CMS disk. Be sure to transfer <filename>kernel.debian</filename> and <filename>initrd.debian</filename> in binary mode with a fixed record length of 80 characters." msgstr "" #. Tag: title -#: preparing.xml:2021 +#: preparing.xml:1997 #, no-c-format msgid "Setting up an installation server" msgstr "" #. Tag: para -#: preparing.xml:2023 +#: preparing.xml:1999 #, no-c-format msgid "If you don't have a connection to the Internet (either directly or via a web proxy) you need to create a local installation server that can be accessed from your S/390. This server keeps all the packages you want to install and must make them available using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: preparing.xml:2031 +#: preparing.xml:2007 #, no-c-format msgid "The installation server needs to copy the exact directory structure from any &debian; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree." msgstr "" #. Tag: emphasis -#: preparing.xml:2040 +#: preparing.xml:2016 #, no-c-format msgid "FIXME: more information needed — from a Redbook?" msgstr "" #. Tag: title -#: preparing.xml:2047 +#: preparing.xml:2023 #, no-c-format msgid "Hardware Issues to Watch Out For" msgstr "" #. Tag: para -#: preparing.xml:2049 +#: preparing.xml:2025 #, no-c-format msgid "Atari TT RAM boards are notorious for RAM problems under Linux; if you encounter any strange problems, try running at least the kernel in ST-RAM. Amiga users may need to exclude RAM using a booter memfile. <phrase condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </emphasis></phrase>" msgstr "" #. Tag: title -#: preparing.xml:2064 +#: preparing.xml:2040 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "" #. Tag: para -#: preparing.xml:2065 +#: preparing.xml:2041 #, no-c-format msgid "If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options." msgstr "" #. Tag: title -#: preparing.xml:2079 +#: preparing.xml:2055 #, no-c-format msgid "Display-visibility on OldWorld Powermacs" msgstr "" #. Tag: para -#: preparing.xml:2081 +#: preparing.xml:2057 #, no-c-format msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver, may not reliably produce a colormap under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>." msgstr "" diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot index ba7f07748..32abb681e 100644 --- a/po/pot/random-bits.pot +++ b/po/pot/random-bits.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-31 19:17+0000\n" +"POT-Creation-Date: 2007-01-01 11:02+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -373,277 +373,295 @@ msgid "Disk Space Needed for Tasks" msgstr "" #. Tag: para -#: random-bits.xml:189 +#: random-bits.xml:194 #, no-c-format -msgid "The base installation for i386 using the default 2.6 kernel, including all standard packages, requires 585MB of disk space. A minimal base installation, without the standard task selected, will take 365MB." +msgid "A standard installation for the i386 architecture, including all standard packages and using the default 2.6 kernel, takes up 442MB of disk space. A minimal base installation, without the <quote>Standard system</quote> task selected, will take 230MB." msgstr "" #. Tag: para -#: random-bits.xml:196 +#: random-bits.xml:202 +#, no-c-format +msgid "In both cases this is the actual disk space used <emphasis>after</emphasis> the installation is finished and any temporary files deleted. It also does not take into account overhead used by the file system, for example for journal files. This means that significantly more disk space is needed both <emphasis>during</emphasis> the installation and for normal system use." +msgstr "" + +#. Tag: para +#: random-bits.xml:211 #, no-c-format msgid "The following table lists sizes reported by aptitude for the tasks listed in tasksel. Note that some tasks have overlapping constituents, so the total installed size for two tasks together may be less than the total obtained by adding up the numbers." msgstr "" #. Tag: para -#: random-bits.xml:203 +#: random-bits.xml:218 #, no-c-format -msgid "Note that you will need to add the sizes listed in the table to the size of the base installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>." +msgid "Note that you will need to add the sizes listed in the table to the size of the standard installation when determining the size of partitions. Most of the size listed as <quote>Installed size</quote> will end up in <filename>/usr</filename> and in <filename>/lib</filename>; the size listed as <quote>Download size</quote> is (temporarily) required in <filename>/var</filename>." msgstr "" #. Tag: entry -#: random-bits.xml:216 +#: random-bits.xml:232 #, no-c-format msgid "Task" msgstr "" #. Tag: entry -#: random-bits.xml:217 +#: random-bits.xml:233 #, no-c-format msgid "Installed size (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:218 +#: random-bits.xml:234 #, no-c-format msgid "Download size (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:219 +#: random-bits.xml:235 #, no-c-format msgid "Space needed to install (MB)" msgstr "" #. Tag: entry -#: random-bits.xml:225 +#: random-bits.xml:241 #, no-c-format -msgid "Desktop" +msgid "Desktop environment" msgstr "" #. Tag: entry -#: random-bits.xml:226 +#: random-bits.xml:242 #, no-c-format -msgid "1258" +msgid "1267" msgstr "" #. Tag: entry -#: random-bits.xml:227 +#: random-bits.xml:243 #, no-c-format -msgid "<entry>418</entry>" +msgid "<entry>420</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:228 +#: random-bits.xml:244 #, no-c-format -msgid "1676" +msgid "1667" msgstr "" #. Tag: entry -#: random-bits.xml:232 +#: random-bits.xml:248 #, no-c-format msgid "Laptop" msgstr "" +#. Tag: para +#: random-bits.xml:250 +#, no-c-format +msgid "There is a large overlap of the Laptop task with the Destop environment task. If you install both, the Laptop task will only require a few MB additional disk space." +msgstr "" + #. Tag: entry -#: random-bits.xml:233 random-bits.xml:242 +#: random-bits.xml:257 #, no-c-format -msgid "<entry>46</entry>" +msgid "<entry>50</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:234 +#: random-bits.xml:258 #, no-c-format -msgid "<entry>16</entry>" +msgid "<entry>17</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:235 +#: random-bits.xml:259 #, no-c-format -msgid "<entry>62</entry>" +msgid "<entry>67</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:239 +#: random-bits.xml:263 #, no-c-format msgid "Web server" msgstr "" #. Tag: entry -#: random-bits.xml:240 +#: random-bits.xml:264 #, no-c-format msgid "<entry>35</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:241 +#: random-bits.xml:265 #, no-c-format msgid "<entry>11</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:246 +#: random-bits.xml:266 +#, no-c-format +msgid "<entry>46</entry>" +msgstr "" + +#. Tag: entry +#: random-bits.xml:270 #, no-c-format msgid "Print server" msgstr "" #. Tag: entry -#: random-bits.xml:247 +#: random-bits.xml:271 #, no-c-format -msgid "<entry>326</entry>" +msgid "<entry>277</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:248 +#: random-bits.xml:272 #, no-c-format -msgid "<entry>95</entry>" +msgid "<entry>79</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:249 +#: random-bits.xml:273 #, no-c-format -msgid "<entry>421</entry>" +msgid "<entry>356</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:253 +#: random-bits.xml:277 #, no-c-format msgid "DNS server" msgstr "" #. Tag: entry -#: random-bits.xml:254 +#: random-bits.xml:278 #, no-c-format msgid "<entry>2</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:255 +#: random-bits.xml:279 #, no-c-format msgid "<entry>1</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:256 +#: random-bits.xml:280 #, no-c-format msgid "<entry>3</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:260 +#: random-bits.xml:284 #, no-c-format msgid "File server" msgstr "" #. Tag: entry -#: random-bits.xml:261 +#: random-bits.xml:285 #, no-c-format -msgid "<entry>50</entry>" +msgid "<entry>49</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:262 +#: random-bits.xml:286 #, no-c-format msgid "<entry>21</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:263 +#: random-bits.xml:287 #, no-c-format -msgid "<entry>71</entry>" +msgid "<entry>70</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:267 +#: random-bits.xml:291 #, no-c-format msgid "Mail server" msgstr "" #. Tag: entry -#: random-bits.xml:268 +#: random-bits.xml:292 #, no-c-format msgid "<entry>13</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:269 +#: random-bits.xml:293 #, no-c-format msgid "<entry>5</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:270 +#: random-bits.xml:294 #, no-c-format msgid "<entry>18</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:274 +#: random-bits.xml:298 #, no-c-format msgid "SQL database" msgstr "" #. Tag: entry -#: random-bits.xml:275 +#: random-bits.xml:299 #, no-c-format msgid "<entry>24</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:276 +#: random-bits.xml:300 #, no-c-format msgid "<entry>8</entry>" msgstr "" #. Tag: entry -#: random-bits.xml:277 +#: random-bits.xml:301 #, no-c-format msgid "<entry>32</entry>" msgstr "" #. Tag: para -#: random-bits.xml:283 +#: random-bits.xml:307 #, no-c-format msgid "The <emphasis>Desktop</emphasis> task will install the GNOME desktop environment." msgstr "" #. Tag: para -#: random-bits.xml:290 +#: random-bits.xml:314 #, no-c-format msgid "If you install in a language other than English, <command>tasksel</command> may automatically install a <firstterm>localization task</firstterm>, if one is available for your language. Space requirements differ per language; you should allow up to 200MB in total for download and installation." msgstr "" #. Tag: title -#: random-bits.xml:305 +#: random-bits.xml:329 #, no-c-format msgid "Installing &debian; from a Unix/Linux System" msgstr "" #. Tag: para -#: random-bits.xml:307 +#: random-bits.xml:331 #, no-c-format msgid "This section explains how to install &debian; from an existing Unix or Linux system, without using the menu-driven installer as explained in the rest of the manual. This <quote>cross-install</quote> HOWTO has been requested by users switching to &debian; from Red Hat, Mandrake, and SUSE. In this section some familiarity with entering *nix commands and navigating the file system is assumed. In this section, <prompt>$</prompt> symbolizes a command to be entered in the user's current system, while <prompt>#</prompt> refers to a command entered in the Debian chroot." msgstr "" #. Tag: para -#: random-bits.xml:319 +#: random-bits.xml:343 #, no-c-format msgid "Once you've got the new Debian system configured to your preference, you can migrate your existing user data (if any) to it, and keep on rolling. This is therefore a <quote>zero downtime</quote> &debian; install. It's also a clever way for dealing with hardware that otherwise doesn't play friendly with various boot or installation media." msgstr "" #. Tag: title -#: random-bits.xml:331 +#: random-bits.xml:355 #, no-c-format msgid "Getting Started" msgstr "" #. Tag: para -#: random-bits.xml:332 +#: random-bits.xml:356 #, no-c-format msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around 350MB of space available for a console only install, or about 1GB if you plan to install X (more if you intend to install destop environments like GNOME or KDE)." msgstr "" #. Tag: para -#: random-bits.xml:340 +#: random-bits.xml:364 #, no-c-format msgid "" "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n" @@ -652,7 +670,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:350 +#: random-bits.xml:374 #, no-c-format msgid "" "Initialize and activate swap (substitute the partition number for your intended Debian swap partition): <informalexample><screen>\n" @@ -663,7 +681,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:362 +#: random-bits.xml:386 #, no-c-format msgid "" "# mkdir /mnt/debinst\n" @@ -671,25 +689,25 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:365 +#: random-bits.xml:389 #, no-c-format msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage." msgstr "" #. Tag: title -#: random-bits.xml:375 +#: random-bits.xml:399 #, no-c-format msgid "Install <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:376 +#: random-bits.xml:400 #, no-c-format msgid "The utility used by the Debian installer, and recognized as the official way to install a Debian base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>." msgstr "" #. Tag: para -#: random-bits.xml:406 +#: random-bits.xml:430 #, no-c-format msgid "" "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n" @@ -699,7 +717,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:421 +#: random-bits.xml:445 #, no-c-format msgid "" "# ar -x debootstrap_0.X.X_all.deb\n" @@ -708,31 +726,31 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:427 +#: random-bits.xml:451 #, no-c-format msgid "Run <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:428 +#: random-bits.xml:452 #, no-c-format msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any Debian archive mirror for <userinput>http.us.debian.org/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/misc/README.mirrors\"></ulink>." msgstr "" #. Tag: para -#: random-bits.xml:437 +#: random-bits.xml:461 #, no-c-format msgid "If you have a &releasename; &debian; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>" msgstr "" #. Tag: para -#: random-bits.xml:443 +#: random-bits.xml:467 #, no-c-format msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>alpha</userinput>, <userinput>amd64</userinput>, <userinput>arm</userinput>, <userinput>hppa</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or <userinput>sparc</userinput>." msgstr "" #. Tag: screen -#: random-bits.xml:461 +#: random-bits.xml:485 #, no-c-format msgid "" "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" @@ -740,13 +758,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:467 +#: random-bits.xml:491 #, no-c-format msgid "Configure The Base System" msgstr "" #. Tag: para -#: random-bits.xml:468 +#: random-bits.xml:492 #, no-c-format msgid "" "Now you've got a real Debian system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n" @@ -755,19 +773,19 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:478 +#: random-bits.xml:502 #, no-c-format msgid "# export TERM=<replaceable>xterm-color</replaceable>" msgstr "" #. Tag: title -#: random-bits.xml:483 +#: random-bits.xml:507 #, no-c-format msgid "Mount Partitions" msgstr "" #. Tag: para -#: random-bits.xml:484 +#: random-bits.xml:508 #, no-c-format msgid "" "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n" @@ -801,37 +819,37 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:510 +#: random-bits.xml:534 #, no-c-format msgid "# mount -t proc proc /proc" msgstr "" #. Tag: para -#: random-bits.xml:512 +#: random-bits.xml:536 #, no-c-format msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:" msgstr "" #. Tag: screen -#: random-bits.xml:518 +#: random-bits.xml:542 #, no-c-format msgid "# mount -t proc proc /mnt/debinst/proc" msgstr "" #. Tag: title -#: random-bits.xml:524 +#: random-bits.xml:548 #, no-c-format msgid "Setting Timezone" msgstr "" #. Tag: para -#: random-bits.xml:525 +#: random-bits.xml:549 #, no-c-format msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allow you to set that and choose your timezone." msgstr "" #. Tag: screen -#: random-bits.xml:532 +#: random-bits.xml:556 #, no-c-format msgid "" "# editor /etc/default/rcS\n" @@ -839,13 +857,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:538 +#: random-bits.xml:562 #, no-c-format msgid "Configure Networking" msgstr "" #. Tag: para -#: random-bits.xml:539 +#: random-bits.xml:563 #, no-c-format msgid "" "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n" @@ -898,13 +916,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:580 +#: random-bits.xml:604 #, no-c-format msgid "Configure Apt" msgstr "" #. Tag: para -#: random-bits.xml:581 +#: random-bits.xml:605 #, no-c-format msgid "" "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n" @@ -916,13 +934,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:597 +#: random-bits.xml:621 #, no-c-format msgid "Configure Locales and Keyboard" msgstr "" #. Tag: para -#: random-bits.xml:598 +#: random-bits.xml:622 #, no-c-format msgid "" "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n" @@ -932,7 +950,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:608 +#: random-bits.xml:632 #, no-c-format msgid "" "# aptitude install console-data\n" @@ -940,37 +958,37 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:610 +#: random-bits.xml:634 #, no-c-format msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot." msgstr "" #. Tag: title -#: random-bits.xml:620 +#: random-bits.xml:644 #, no-c-format msgid "Install a Kernel" msgstr "" #. Tag: para -#: random-bits.xml:621 +#: random-bits.xml:645 #, no-c-format msgid "If you intend to boot this system, you probably want a Linux kernel and a boot loader. Identify available pre-packaged kernels with:" msgstr "" #. Tag: screen -#: random-bits.xml:626 +#: random-bits.xml:650 #, no-c-format msgid "# apt-cache search linux-image" msgstr "" #. Tag: para -#: random-bits.xml:628 +#: random-bits.xml:652 #, no-c-format msgid "If you intend to use a pre-packaged kernel, you may want to create the configuration file <filename>/etc/kernel-img.conf</filename> before you do so. Here's an example file:" msgstr "" #. Tag: screen -#: random-bits.xml:634 +#: random-bits.xml:658 #, no-c-format msgid "" "# Kernel image management overrides\n" @@ -984,13 +1002,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:636 +#: random-bits.xml:660 #, no-c-format msgid "For detailed information about this file and the various options, consult its man page which will be available after installing the <classname>kernel-package</classname> package. We recommend that you check that the values are appropriate for your system." msgstr "" #. Tag: para -#: random-bits.xml:643 +#: random-bits.xml:667 #, no-c-format msgid "" "If you intend to use <classname>grub</classname> as your bootloader, you can set the <literal>do_bootloader</literal> option to <quote>no</quote>. To automatically update your <filename>/boot/grub/menu.lst</filename> on installation or removal of Debian kernels, add the following lines: <informalexample><screen>\n" @@ -1000,7 +1018,7 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:655 +#: random-bits.xml:679 #, no-c-format msgid "" "Then install the kernel package of your choice using its package name. <informalexample><screen>\n" @@ -1009,25 +1027,25 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:669 +#: random-bits.xml:693 #, no-c-format msgid "Set up the Boot Loader" msgstr "" #. Tag: para -#: random-bits.xml:670 +#: random-bits.xml:694 #, no-c-format msgid "To make your &debian; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so." msgstr "" #. Tag: para -#: random-bits.xml:677 +#: random-bits.xml:701 #, no-c-format msgid "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename> or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)." msgstr "" #. Tag: para -#: random-bits.xml:689 +#: random-bits.xml:713 #, no-c-format msgid "" "Installing and setting up <classname>grub</classname> is as easy as: <informalexample><screen>\n" @@ -1038,13 +1056,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:699 +#: random-bits.xml:723 #, no-c-format msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:" msgstr "" #. Tag: screen -#: random-bits.xml:703 +#: random-bits.xml:727 #, no-c-format msgid "" "boot=/dev/<replaceable>hda6</replaceable>\n" @@ -1057,13 +1075,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:705 +#: random-bits.xml:729 #, no-c-format msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)." msgstr "" #. Tag: para -#: random-bits.xml:715 +#: random-bits.xml:739 #, no-c-format msgid "" "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n" @@ -1079,13 +1097,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:728 +#: random-bits.xml:752 #, no-c-format msgid "Finishing touches" msgstr "" #. Tag: para -#: random-bits.xml:729 +#: random-bits.xml:753 #, no-c-format msgid "" "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to install all packages with <quote>standard</quote> priority: <informalexample><screen>\n" @@ -1094,91 +1112,91 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:740 +#: random-bits.xml:764 #, no-c-format msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:" msgstr "" #. Tag: screen -#: random-bits.xml:746 +#: random-bits.xml:770 #, no-c-format msgid "# aptitude clean" msgstr "" #. Tag: title -#: random-bits.xml:757 +#: random-bits.xml:781 #, no-c-format msgid "Installing &debian; over Parallel Line IP (PLIP)" msgstr "" #. Tag: para -#: random-bits.xml:759 +#: random-bits.xml:783 #, no-c-format msgid "This section explains how to install &debian; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a Debian mirror on it (e.g. to the Internet)." msgstr "" #. Tag: para -#: random-bits.xml:767 +#: random-bits.xml:791 #, no-c-format msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)." msgstr "" #. Tag: para -#: random-bits.xml:775 +#: random-bits.xml:799 #, no-c-format msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)." msgstr "" #. Tag: para -#: random-bits.xml:780 +#: random-bits.xml:804 #, no-c-format msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>." msgstr "" #. Tag: title -#: random-bits.xml:790 +#: random-bits.xml:814 #, no-c-format msgid "Requirements" msgstr "" #. Tag: para -#: random-bits.xml:793 +#: random-bits.xml:817 #, no-c-format msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed." msgstr "" #. Tag: para -#: random-bits.xml:799 +#: random-bits.xml:823 #, no-c-format msgid "System installation media; see <xref linkend=\"installation-media\"/>." msgstr "" #. Tag: para -#: random-bits.xml:804 +#: random-bits.xml:828 #, no-c-format msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway." msgstr "" #. Tag: para -#: random-bits.xml:810 +#: random-bits.xml:834 #, no-c-format msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own." msgstr "" #. Tag: title -#: random-bits.xml:822 +#: random-bits.xml:846 #, no-c-format msgid "Setting up source" msgstr "" #. Tag: para -#: random-bits.xml:823 +#: random-bits.xml:847 #, no-c-format msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0." msgstr "" #. Tag: screen -#: random-bits.xml:828 +#: random-bits.xml:852 #, no-c-format msgid "" "#!/bin/sh\n" @@ -1199,13 +1217,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:834 +#: random-bits.xml:858 #, no-c-format msgid "Installing target" msgstr "" #. Tag: para -#: random-bits.xml:835 +#: random-bits.xml:859 #, no-c-format msgid "" "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n" @@ -1214,61 +1232,61 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:854 +#: random-bits.xml:878 #, no-c-format msgid "Load installer components from CD" msgstr "" #. Tag: para -#: random-bits.xml:856 +#: random-bits.xml:880 #, no-c-format msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system." msgstr "" #. Tag: guimenuitem -#: random-bits.xml:864 +#: random-bits.xml:888 #, no-c-format msgid "Detect network hardware" msgstr "" #. Tag: para -#: random-bits.xml:869 +#: random-bits.xml:893 #, no-c-format msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list." msgstr "" #. Tag: para -#: random-bits.xml:878 +#: random-bits.xml:902 #, no-c-format msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module." msgstr "" #. Tag: guimenuitem -#: random-bits.xml:890 +#: random-bits.xml:914 #, no-c-format msgid "Configure the network" msgstr "" #. Tag: para -#: random-bits.xml:893 +#: random-bits.xml:917 #, no-c-format msgid "Auto-configure network with DHCP: No" msgstr "" #. Tag: para -#: random-bits.xml:898 +#: random-bits.xml:922 #, no-c-format msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:903 +#: random-bits.xml:927 #, no-c-format msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:909 +#: random-bits.xml:933 #, no-c-format msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)" msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 1d67f2015..f72fb50da 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-31 03:15+0000\n" +"POT-Creation-Date: 2007-01-01 11:02+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -1596,319 +1596,319 @@ msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and msgstr "" #. Tag: para -#: using-d-i.xml:2014 +#: using-d-i.xml:2016 #, no-c-format 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 un-select the tasks. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2021 +#: using-d-i.xml:2023 #, no-c-format msgid "The <quote>Desktop environment</quote> task will install the GNOME desktop environment. The options offered by the installer currently do not allow to select a different desktop environment such as for example KDE." msgstr "" #. Tag: para -#: using-d-i.xml:2027 +#: using-d-i.xml:2031 #, no-c-format msgid "It is possible to get the installer to install KDE by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding <literal>tasks=\"standard, kde-desktop\"</literal> at the boot prompt when starting the installer. However, this will only work if the packages needed for KDE are actually available. If you are installing using a full CD image, they will need to be downloaded from a mirror as KDE packages are not included on the first full CD; installing KDE this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:2038 +#: using-d-i.xml:2042 #, no-c-format 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>." msgstr "" #. Tag: para -#: using-d-i.xml:2050 +#: using-d-i.xml:2054 #, no-c-format msgid "Once you've selected your tasks, select <guibutton>OK</guibutton>. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected." msgstr "" #. Tag: para -#: using-d-i.xml:2057 +#: using-d-i.xml:2061 #, no-c-format msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" #. Tag: para -#: using-d-i.xml:2063 +#: using-d-i.xml:2067 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2072 +#: using-d-i.xml:2076 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2081 +#: using-d-i.xml:2085 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2094 +#: using-d-i.xml:2098 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2096 +#: using-d-i.xml:2100 #, no-c-format 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>" msgstr "" #. Tag: title -#: using-d-i.xml:2111 +#: using-d-i.xml:2115 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2113 +#: using-d-i.xml:2117 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2121 +#: using-d-i.xml:2125 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2139 +#: using-d-i.xml:2143 #, no-c-format msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2140 +#: using-d-i.xml:2144 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2160 +#: using-d-i.xml:2164 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2161 +#: using-d-i.xml:2165 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2170 +#: using-d-i.xml:2174 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2182 +#: using-d-i.xml:2186 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2184 +#: using-d-i.xml:2188 #, no-c-format 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 newbies and old hands alike." msgstr "" #. Tag: para -#: using-d-i.xml:2190 +#: using-d-i.xml:2194 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2196 +#: using-d-i.xml:2200 #, no-c-format msgid "If you do not want to install grub at all, use the Back button to get to the main menu, and from there select whatever bootloader you would like to use." msgstr "" #. Tag: title -#: using-d-i.xml:2210 +#: using-d-i.xml:2214 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2212 +#: using-d-i.xml:2216 #, no-c-format 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>." msgstr "" #. Tag: para -#: using-d-i.xml:2222 +#: using-d-i.xml:2226 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2230 +#: using-d-i.xml:2234 #, no-c-format msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2237 +#: using-d-i.xml:2241 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2237 +#: using-d-i.xml:2241 #, no-c-format msgid "This way the <command>LILO</command> will take complete control of the boot process." msgstr "" #. Tag: term -#: using-d-i.xml:2244 +#: using-d-i.xml:2248 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2244 +#: using-d-i.xml:2248 #, no-c-format 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." msgstr "" #. Tag: term -#: using-d-i.xml:2253 +#: using-d-i.xml:2257 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2253 +#: using-d-i.xml:2257 #, no-c-format 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 devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." msgstr "" #. Tag: para -#: using-d-i.xml:2265 +#: using-d-i.xml:2269 #, no-c-format 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!" msgstr "" #. Tag: title -#: using-d-i.xml:2281 +#: using-d-i.xml:2285 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2283 +#: using-d-i.xml:2287 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2299 +#: using-d-i.xml:2303 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2311 +#: using-d-i.xml:2315 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2313 +#: using-d-i.xml:2317 #, no-c-format 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!" msgstr "" #. Tag: title -#: using-d-i.xml:2328 +#: using-d-i.xml:2332 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2330 +#: using-d-i.xml:2334 #, no-c-format 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." msgstr "" #. Tag: filename -#: using-d-i.xml:2352 +#: using-d-i.xml:2356 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2353 +#: using-d-i.xml:2357 #, no-c-format 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." msgstr "" #. Tag: filename -#: using-d-i.xml:2362 +#: using-d-i.xml:2366 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2363 +#: using-d-i.xml:2367 #, no-c-format 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." msgstr "" #. Tag: filename -#: using-d-i.xml:2373 +#: using-d-i.xml:2377 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2374 +#: using-d-i.xml:2378 #, no-c-format 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>." msgstr "" #. Tag: filename -#: using-d-i.xml:2386 +#: using-d-i.xml:2390 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2387 +#: using-d-i.xml:2391 #, no-c-format 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." msgstr "" #. Tag: filename -#: using-d-i.xml:2397 +#: using-d-i.xml:2401 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2398 +#: using-d-i.xml:2402 #, no-c-format 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>." msgstr "" #. Tag: title -#: using-d-i.xml:2418 +#: using-d-i.xml:2422 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2419 +#: using-d-i.xml:2423 #, no-c-format msgid "" "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" @@ -1921,61 +1921,61 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2438 +#: using-d-i.xml:2442 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2439 +#: using-d-i.xml:2443 #, no-c-format msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2447 +#: using-d-i.xml:2451 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2448 +#: using-d-i.xml:2452 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2456 using-d-i.xml:2525 +#: using-d-i.xml:2460 using-d-i.xml:2529 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2457 +#: using-d-i.xml:2461 #, no-c-format msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2465 +#: using-d-i.xml:2469 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2466 +#: using-d-i.xml:2470 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: title -#: using-d-i.xml:2487 +#: using-d-i.xml:2491 #, no-c-format msgid "<command>delo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2488 +#: using-d-i.xml:2492 #, no-c-format msgid "" "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" @@ -1984,265 +1984,265 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2507 +#: using-d-i.xml:2511 #, no-c-format msgid "<replaceable>#</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2508 +#: using-d-i.xml:2512 #, no-c-format msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2516 +#: using-d-i.xml:2520 #, no-c-format msgid "<replaceable>id</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2517 +#: using-d-i.xml:2521 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" #. Tag: para -#: using-d-i.xml:2526 +#: using-d-i.xml:2530 #, no-c-format msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2534 +#: using-d-i.xml:2538 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2535 +#: using-d-i.xml:2539 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: para -#: using-d-i.xml:2545 +#: using-d-i.xml:2549 #, no-c-format 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" msgstr "" #. Tag: screen -#: using-d-i.xml:2551 +#: using-d-i.xml:2555 #, no-c-format msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" #. Tag: title -#: using-d-i.xml:2561 +#: using-d-i.xml:2565 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2562 +#: using-d-i.xml:2566 #, no-c-format 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;." msgstr "" #. Tag: title -#: using-d-i.xml:2580 +#: using-d-i.xml:2584 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2581 +#: using-d-i.xml:2585 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2597 +#: using-d-i.xml:2601 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2598 +#: using-d-i.xml:2602 #, no-c-format 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>." msgstr "" #. Tag: title -#: using-d-i.xml:2615 +#: using-d-i.xml:2619 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2617 +#: using-d-i.xml:2621 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2642 +#: using-d-i.xml:2646 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2644 +#: using-d-i.xml:2648 #, no-c-format 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>" msgstr "" #. Tag: para -#: using-d-i.xml:2653 +#: using-d-i.xml:2657 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2670 +#: using-d-i.xml:2674 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2671 +#: using-d-i.xml:2675 #, no-c-format msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:2683 +#: using-d-i.xml:2687 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "" #. Tag: para -#: using-d-i.xml:2685 +#: using-d-i.xml:2689 #, no-c-format msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2692 +#: using-d-i.xml:2696 #, no-c-format msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2706 +#: using-d-i.xml:2710 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2707 +#: using-d-i.xml:2711 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2720 +#: using-d-i.xml:2724 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2722 +#: using-d-i.xml:2726 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2729 +#: using-d-i.xml:2733 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2749 +#: using-d-i.xml:2753 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2751 +#: using-d-i.xml:2755 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2769 +#: using-d-i.xml:2773 #, no-c-format 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. To get back to the installer itself, type <userinput>exit</userinput> to close the shell." msgstr "" #. Tag: para -#: using-d-i.xml:2776 +#: using-d-i.xml:2780 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2785 +#: using-d-i.xml:2789 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2792 +#: using-d-i.xml:2796 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2798 +#: using-d-i.xml:2802 #, no-c-format 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." msgstr "" #. Tag: title -#: using-d-i.xml:2813 +#: using-d-i.xml:2817 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:2815 +#: using-d-i.xml:2819 #, no-c-format 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\"/>.)" msgstr "" #. Tag: para -#: using-d-i.xml:2825 +#: using-d-i.xml:2829 #, no-c-format 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>." msgstr "" #. Tag: para -#: using-d-i.xml:2838 +#: using-d-i.xml:2842 #, no-c-format msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" #. Tag: para -#: using-d-i.xml:2843 +#: using-d-i.xml:2847 #, no-c-format 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>." msgstr "" #. Tag: para -#: using-d-i.xml:2855 +#: using-d-i.xml:2859 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2861 +#: using-d-i.xml:2865 #, no-c-format msgid "" "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" @@ -2251,25 +2251,25 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2878 +#: using-d-i.xml:2882 #, no-c-format 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> and try again." msgstr "" #. Tag: para -#: using-d-i.xml:2887 +#: using-d-i.xml:2891 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2897 +#: using-d-i.xml:2901 #, no-c-format 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." msgstr "" #. Tag: para -#: using-d-i.xml:2905 +#: using-d-i.xml:2909 #, no-c-format 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." msgstr "" |