diff options
| author | Holger Wansing <hwansing@mailbox.org> | 2021-01-17 23:13:12 +0100 |
|---|---|---|
| committer | Holger Wansing <hwansing@mailbox.org> | 2021-01-17 23:13:12 +0100 |
| commit | ed6969127b0443024bc139b6b370e02e86eca9f6 (patch) | |
| tree | 20390541fd1b5043afc19e83fdb21b155eea5fac /po | |
| parent | f8950f1cf38c395b6a494377d4ae41b75961d9ae (diff) | |
| download | installation-guide-ed6969127b0443024bc139b6b370e02e86eca9f6.zip | |
New translation effort announced for Kabyle. Added po files (copied from templates pot files)
Diffstat (limited to 'po')
| -rw-r--r-- | po/kab/administrivia.po | 200 | ||||
| -rw-r--r-- | po/kab/bookinfo.po | 102 | ||||
| -rw-r--r-- | po/kab/boot-installer.po | 3359 | ||||
| -rw-r--r-- | po/kab/boot-new.po | 419 | ||||
| -rw-r--r-- | po/kab/gpl.po | 668 | ||||
| -rw-r--r-- | po/kab/hardware.po | 2856 | ||||
| -rw-r--r-- | po/kab/install-methods.po | 1491 | ||||
| -rw-r--r-- | po/kab/installation-howto.po | 441 | ||||
| -rw-r--r-- | po/kab/partitioning.po | 1122 | ||||
| -rw-r--r-- | po/kab/post-install.po | 679 | ||||
| -rw-r--r-- | po/kab/preface.po | 53 | ||||
| -rw-r--r-- | po/kab/preparing.po | 2344 | ||||
| -rw-r--r-- | po/kab/preseed.po | 2341 | ||||
| -rw-r--r-- | po/kab/random-bits.po | 1613 | ||||
| -rw-r--r-- | po/kab/using-d-i.po | 4193 | ||||
| -rw-r--r-- | po/kab/welcome.po | 765 |
16 files changed, 22646 insertions, 0 deletions
diff --git a/po/kab/administrivia.po b/po/kab/administrivia.po new file mode 100644 index 000000000..34f2da50b --- /dev/null +++ b/po/kab/administrivia.po @@ -0,0 +1,200 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-administrivia 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2019-08-06 18:46+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: administrivia.xml:5 +#, no-c-format +msgid "Administrivia" +msgstr "" + +#. Tag: title +#: administrivia.xml:9 +#, no-c-format +msgid "About This Document" +msgstr "" + +#. Tag: para +#: administrivia.xml:11 +#, no-c-format +msgid "" +"This manual was created for Sarge's debian-installer, based on the Woody " +"installation manual for boot-floppies, which was based on earlier Debian " +"installation manuals, and on the Progeny distribution manual which was " +"released under GPL in 2003." +msgstr "" + +#. Tag: para +#: administrivia.xml:18 +#, no-c-format +msgid "" +"This document is written in DocBook XML. Output formats are generated by " +"various programs using information from the <classname>docbook-xml</" +"classname> and <classname>docbook-xsl</classname> packages." +msgstr "" + +#. Tag: para +#: administrivia.xml:25 +#, no-c-format +msgid "" +"In order to increase the maintainability of this document, we use a number " +"of XML features, such as entities and profiling attributes. These play a " +"role akin to variables and conditionals in programming languages. The XML " +"source to this document contains information for each different architecture " +"— profiling attributes are used to isolate certain bits of text as " +"architecture-specific." +msgstr "" + +#. Tag: para +#: administrivia.xml:34 +#, no-c-format +msgid "" +"Translators can use this paragraph to acknowledge the people responsible for " +"the translation of the manual. Translation teams are advised to just mention " +"the coordinator and maybe major contributors and thank everybody else in a " +"phrase like <quote>all translators and reviewers from the translation team " +"for {your language} at {your l10n mailinglist}</quote>. See build/lang-" +"options/README on how to enable this paragraph. Its condition is " +"<quote>about-langteam</quote>." +msgstr "" + +#. Tag: title +#: administrivia.xml:50 +#, no-c-format +msgid "Contributing to This Document" +msgstr "" + +#. Tag: para +#: administrivia.xml:52 +#, no-c-format +msgid "" +"If you have problems or suggestions regarding this document, you should " +"probably submit them as a bug report against the package " +"<classname>installation-guide</classname>. See the <classname>reportbug</" +"classname> package or read the online documentation of the <ulink url=\"&url-" +"bts;\">Debian Bug Tracking System</ulink>. It would be nice if you could " +"check the <ulink url=\"&url-bts;installation-guide\">open bugs against " +"installation-guide</ulink> to see whether your problem has already been " +"reported. If so, you can supply additional corroboration or helpful " +"information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</" +"email>, where <replaceable>XXXX</replaceable> is the number for the already-" +"reported bug." +msgstr "" + +#. Tag: para +#: administrivia.xml:68 +#, no-c-format +msgid "" +"Better yet, get a copy of the DocBook source for this document, and produce " +"patches against it. The DocBook source can be found at the <ulink url=\"&url-" +"d-i-project-salsa;\">installation-guide project on salsa</ulink>. If you're " +"not familiar with DocBook, don't worry: there is a simple cheatsheet in the " +"manuals directory that will get you started. It's like html, but oriented " +"towards the meaning of the text rather than the presentation. Patches " +"submitted to the debian-boot mailing list (see below) are welcomed. For " +"instructions on how to check out the sources via git, see <ulink url=\"&url-" +"manual-readme;\">README</ulink> from the source root directory." +msgstr "" + +#. Tag: para +#: administrivia.xml:82 +#, no-c-format +msgid "" +"Please do <emphasis>not</emphasis> contact the authors of this document " +"directly. There is also a discussion list for &d-i;, which includes " +"discussions of this manual. The mailing list is <email>debian-boot@lists." +"debian.org</email>. Instructions for subscribing to this list can be found " +"at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List " +"Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-" +"list-archives;\">Debian Mailing List Archives</ulink> online." +msgstr "" + +#. Tag: title +#: administrivia.xml:99 +#, no-c-format +msgid "Major Contributions" +msgstr "" + +#. Tag: para +#: administrivia.xml:101 +#, no-c-format +msgid "" +"This document was originally written by Bruce Perens, Sven Rudolph, Igor " +"Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the " +"Installation Howto." +msgstr "" + +#. Tag: para +#: administrivia.xml:107 +#, no-c-format +msgid "" +"Miroslav Kuře has documented a lot of the new functionality in Sarge's " +"debian-installer. Frans Pop was the main editor and release manager during " +"the Etch, Lenny and Squeeze releases." +msgstr "" + +#. Tag: para +#: administrivia.xml:113 +#, no-c-format +msgid "" +"Many, many Debian users and developers contributed to this document. " +"Particular note must be made of Michael Schmitz (m68k support), Frank " +"Neumann (original author of the <ulink url=\"&url-m68k-old-amiga-install;" +"\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/Ben Collins " +"(SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for numerous " +"edits and text. We have to thank Pascal Le Bail for useful information about " +"booting from USB memory sticks." +msgstr "" + +#. Tag: para +#: administrivia.xml:124 +#, no-c-format +msgid "" +"Extremely helpful text and information was found in Jim Mintha's HOWTO for " +"network booting (no URL available), the <ulink url=\"&url-debian-faq;" +"\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</" +"ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors " +"FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, " +"amongst others. The maintainers of these freely available and rich sources " +"of information must be recognized." +msgstr "" + +#. Tag: para +#: administrivia.xml:136 +#, no-c-format +msgid "" +"The section on chrooted installations in this manual (<xref linkend=\"linux-" +"upgrade\"/>) was derived in part from documents copyright Karsten M. Self." +msgstr "" + +#. Tag: para +#: administrivia.xml:142 +#, no-c-format +msgid "" +"The section on installations over plip in this manual (<xref linkend=\"plip" +"\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-" +"HOWTO</ulink> by Gilles Lamiral." +msgstr "" + +#. Tag: title +#: administrivia.xml:153 +#, no-c-format +msgid "Trademark Acknowledgement" +msgstr "" + +#. Tag: para +#: administrivia.xml:154 +#, no-c-format +msgid "All trademarks are property of their respective trademark owners." +msgstr "" diff --git a/po/kab/bookinfo.po b/po/kab/bookinfo.po new file mode 100644 index 000000000..916e8d0f3 --- /dev/null +++ b/po/kab/bookinfo.po @@ -0,0 +1,102 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-bookinfo 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-01-10 23: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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: bookinfo.xml:5 +#, no-c-format +msgid "&debian-gnu; Installation Guide" +msgstr "" + +#. Tag: para +#: bookinfo.xml:8 +#, no-c-format +msgid "" +"This document contains installation instructions for the &debian-gnu; " +"&release; system (codename <quote>&releasename;</quote>), for the &arch-" +"title; (<quote>&architecture;</quote>) architecture. It also contains " +"pointers to more information and information on how to make the most of your " +"new &debian; system." +msgstr "" + +#. Tag: para +#: bookinfo.xml:17 +#, no-c-format +msgid "" +"This installation guide is based on an earlier manual written for the old " +"Debian installation system (the <quote>boot-floppies</quote>), and has been " +"updated to document the new Debian installer. However, for &architecture;, " +"the manual has not been fully updated and fact checked for the new " +"installer. There may remain parts of the manual that are incomplete or " +"outdated or that still document the boot-floppies installer. A newer version " +"of this manual, possibly better documenting this architecture, may be found " +"on the Internet at the <ulink url=\"&url-d-i;\">&d-i; home page</ulink>. You " +"may also be able to find additional translations there." +msgstr "" + +#. Tag: para +#: bookinfo.xml:30 +#, no-c-format +msgid "" +"Although this installation guide for &architecture; is mostly up-to-date, we " +"plan to make some changes and reorganize parts of the manual after the " +"official release of &releasename;. A newer version of this manual may be " +"found on the Internet at the <ulink url=\"&url-d-i;\">&d-i; home page</" +"ulink>. You may also be able to find additional translations there." +msgstr "" + +#. Tag: para +#: bookinfo.xml:39 +#, no-c-format +msgid "" +"This translation of the installation guide is not up-to-date and currently " +"there is noone actively working on updating it. Keep this in mind when " +"reading it; it may contain outdated or wrong information. Read or double-" +"check the English variant, if in doubt. If you can help us with updating the " +"translation, please contact <email>debian-boot@lists.debian.org</email> or " +"the <ulink url=\"https://lists.debian.org/i18n.html\">debian-l10n-xxx " +"mailinglist</ulink> for this language. Many thanks" +msgstr "" + +#. Tag: para +#: bookinfo.xml:53 +#, no-c-format +msgid "" +"Translators can use this paragraph to provide some information about the " +"status of the translation, for example if the translation is still being " +"worked on or if review is wanted (don't forget to mention where comments " +"should be sent!). See build/lang-options/README on how to enable this " +"paragraph. Its condition is \"translation-status\"." +msgstr "" + +#. Tag: holder +#: bookinfo.xml:66 +#, no-c-format +msgid "the Debian Installer team" +msgstr "" + +#. Tag: para +#: bookinfo.xml:70 +#, no-c-format +msgid "" +"This manual is free software; you may redistribute it and/or modify it under " +"the terms of the GNU General Public License. Please refer to the license in " +"<xref linkend=\"appendix-gpl\"/>." +msgstr "" + +#. Tag: para +#: bookinfo.xml:78 +#, no-c-format +msgid "Build version of this manual: &debversion;." +msgstr "" diff --git a/po/kab/boot-installer.po b/po/kab/boot-installer.po new file mode 100644 index 000000000..45d23c03b --- /dev/null +++ b/po/kab/boot-installer.po @@ -0,0 +1,3359 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-boot-installer 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-07-26 23: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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: boot-installer.xml:4 +#, no-c-format +msgid "Booting the Installation System" +msgstr "" + +#. Tag: title +#: boot-installer.xml:9 +#, no-c-format +msgid "Booting the Installer on &arch-title;" +msgstr "" + +#. Tag: para +#: boot-installer.xml:15 +#, no-c-format +msgid "" +"If you have any other operating systems on your system that you wish to keep " +"(dual boot setup), you should make sure that they have been properly shut " +"down <emphasis>before</emphasis> you boot the installer. Installing an " +"operating system while another operating system is in hibernation (has been " +"suspended to disk) could result in loss of, or damage to the state of the " +"suspended operating system which could cause problems when it is rebooted." +msgstr "" + +#. Tag: para +#: boot-installer.xml:26 +#, no-c-format +msgid "" +"For information on how to boot the graphical installer, see <xref linkend=" +"\"graphical\"/>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:39 +#, no-c-format +msgid "Boot image formats" +msgstr "" + +#. Tag: para +#: boot-installer.xml:40 +#, no-c-format +msgid "" +"On ARM-based systems in most cases one of two formats for boot images is " +"used: a) standard Linux zImage-format kernels (<quote>vmlinuz</quote>) in " +"conjunction with standard Linux initial ramdisks (<quote>initrd.gz</quote>) " +"or b) uImage-format kernels (<quote>uImage</quote>) in conjunction with " +"corresponding initial ramdisks (<quote>uInitrd</quote>)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:48 +#, no-c-format +msgid "" +"uImage/uInitrd are image formats designed for the U-Boot firmware that is " +"used on many ARM-based systems (mostly 32-bit ones). Older U-Boot versions " +"can only boot files in uImage/uInitrd format, so these are often used on " +"older armel systems. Newer U-Boot versions can - besides booting uImages/" +"uInitrds - also boot standard Linux kernels and ramdisk images, but the " +"command syntax to do that is slightly different from that for booting " +"uImages." +msgstr "" + +#. Tag: para +#: boot-installer.xml:57 +#, no-c-format +msgid "" +"For systems using a multiplatform kernel, besides kernel and initial ramdisk " +"a so-called device-tree file (or device-tree blob, <quote>dtb</quote>) is " +"needed. It is specific to each supported system and contains a description " +"of the particular hardware. The dtb should be supplied on the device by the " +"firmware, but in practice a newer one often needs to be loaded." +msgstr "" + +#. Tag: title +#: boot-installer.xml:68 boot-installer.xml:86 +#, no-c-format +msgid "Console configuration" +msgstr "" + +#. Tag: para +#: boot-installer.xml:69 +#, no-c-format +msgid "" +"The netboot tarball (<xref linkend=\"boot-armhf-netboot.tar.gz\"/>), and the " +"installer SD-card images (<xref linkend=\"boot-installer-sd-image\"/>) use " +"the (platform-specific) default console that is defined by U-Boot in the " +"<quote>console</quote> variable. In most cases that is a serial console, so " +"on those platforms you by default need a serial console cable to use the " +"installer." +msgstr "" + +#. Tag: para +#: boot-installer.xml:78 +#, no-c-format +msgid "" +"On platforms which also support a video console, you can modify the U-Boot " +"<quote>console</quote> variable accordingly if you would like the installer " +"to start on the video console." +msgstr "" + +#. Tag: para +#: boot-installer.xml:87 +#, no-c-format +msgid "" +"The graphical installer is not enabled on the arm64 &d-i; images for stretch " +"so the serial console is used. The console device should be detected " +"automatically from the firmware, but if it is not then after you boot linux " +"from the GRUB menu you will see a <quote>Booting Linux</quote> message, then " +"nothing more." +msgstr "" + +#. Tag: para +#: boot-installer.xml:94 +#, no-c-format +msgid "" +"If you hit this issue you will need to set a specific console config on the " +"kernel command line. Hit <userinput>e</userinput> for <quote>Edit Kernel " +"command-line</quote> at the GRUB menu, and change " +"<informalexample><screen>--- quiet</screen></informalexample> to " +"<informalexample><screen>console=<device>,<speed></screen></" +"informalexample> e.g. <informalexample><screen>console=ttyAMA0,115200n8</" +"screen></informalexample>. When finished hit <keycombo><keycap>Control</" +"keycap> <keycap>x</keycap></keycombo> to continue booting with new setting." +msgstr "" + +#. Tag: title +#: boot-installer.xml:108 +#, no-c-format +msgid "Juno Installation" +msgstr "" + +#. Tag: para +#: boot-installer.xml:109 +#, no-c-format +msgid "" +"Juno has UEFI so the install is straightforward. The most practical method " +"is installing from USB stick. You need up to date firmware for USB-booting " +"to work. Builds from <ulink url=\"&url-juno-firmware;\">&url-juno-firmware;</" +"ulink> after March 2015 tested OK. Consult Juno documentation on firmware " +"updating." +msgstr "" + +#. Tag: para +#: boot-installer.xml:116 +#, no-c-format +msgid "" +"Prepare a standard arm64 CD/DVD image on a USB stick. Insert it in one of " +"the USB ports on the back. Plug a serial cable into the upper 9-pin serial " +"port on the back. If you need networking (netboot image) plug the ethernet " +"cable into the socket on the front of the machine." +msgstr "" + +#. Tag: para +#: boot-installer.xml:123 +#, no-c-format +msgid "" +"Run a serial console at 115200, 8bit no parity, and boot the Juno. It should " +"boot from the USB stick to a GRUB menu. The console config is not correctly " +"detected on Juno so just hitting &enterkey; will show no kernel output. Set " +"the console to <informalexample><screen>console=ttyAMA0,115200n8</screen></" +"informalexample> (as described in <xref linkend=\"arm64-console-setup\"/>). " +"<keycombo><keycap>Control</keycap> <keycap>x</keycap></keycombo> to boot " +"should show you the &d-i; screens, and allow you to proceed with a standard " +"installation." +msgstr "" + +#. Tag: title +#: boot-installer.xml:136 +#, no-c-format +msgid "Applied Micro Mustang Installation" +msgstr "" + +#. Tag: para +#: boot-installer.xml:137 +#, no-c-format +msgid "" +"UEFI is available for this machine but it is normally shipped with U-Boot so " +"you will need to either install UEFI firmware first then use standard boot/" +"install methods, or use U-Boot boot methods. You must use a serial console " +"to control the installation because the graphical installer is not enabled " +"on the arm64 architecture." +msgstr "" + +#. Tag: para +#: boot-installer.xml:145 +#, no-c-format +msgid "" +"The recommended install method is to copy the &d-i; kernel and initrd onto " +"the hard drive, using the openembedded system supplied with the machine, " +"then boot from that to run the installer. Alternatively use TFTP to get the " +"kernel/dtb/initrd copied over and booted (<xref linkend=\"boot-tftp-uboot\"/" +">). After installation, manual changes to boot from the installed image are " +"needed." +msgstr "" + +#. Tag: para +#: boot-installer.xml:154 +#, no-c-format +msgid "" +"Run a serial console at 115200, 8bit no parity, and boot the machine. Reboot " +"the machine and when you see <quote>Hit any key to stop autoboot:</quote> " +"hit a key to get a Mustang# prompt. Then use U-Boot commands to load and " +"boot the kernel, dtb and initrd." +msgstr "" + +#. Tag: title +#: boot-installer.xml:163 +#, no-c-format +msgid "Booting by TFTP" +msgstr "" + +#. Tag: para +#: boot-installer.xml:169 boot-installer.xml:729 boot-installer.xml:1366 +#: boot-installer.xml:1496 boot-installer.xml:1889 +#, no-c-format +msgid "" +"Booting from the network requires that you have a network connection and a " +"TFTP network boot server (and probably also a DHCP, RARP, or BOOTP server " +"for automatic network configuration)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:175 boot-installer.xml:735 boot-installer.xml:1372 +#: boot-installer.xml:1502 boot-installer.xml:1895 +#, no-c-format +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" + +#. Tag: para +#: boot-installer.xml:180 boot-installer.xml:740 boot-installer.xml:1377 +#: boot-installer.xml:1507 boot-installer.xml:1900 +#, no-c-format +msgid "" +"The server-side setup to support network booting is described in <xref " +"linkend=\"install-tftp\"/>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:189 +#, no-c-format +msgid "TFTP-booting in U-Boot" +msgstr "" + +#. Tag: para +#: boot-installer.xml:190 +#, no-c-format +msgid "" +"Network booting on systems using the U-Boot firmware consists of three " +"steps: a) configuring the network, b) loading the images (kernel/initial " +"ramdisk/dtb) into memory and c) actually executing the previosly loaded code." +msgstr "" + +#. Tag: para +#: boot-installer.xml:196 +#, no-c-format +msgid "" +"First you have to configure the network, either automatically via DHCP by " +"running <informalexample><screen>\n" +"setenv autoload no\n" +"dhcp\n" +"</screen></informalexample> or manually by setting several environment " +"variables <informalexample><screen>\n" +"setenv ipaddr <ip address of the client>\n" +"setenv netmask <netmask>\n" +"setenv serverip <ip address of the tftp server>\n" +"setenv dnsip <ip address of the nameserver>\n" +"setenv gatewayip <ip address of the default gateway>\n" +"</screen></informalexample> If you prefer, you can make these settings " +"permanent by running" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:203 +#, no-c-format +msgid "saveenv" +msgstr "" + +#. Tag: para +#: boot-installer.xml:205 +#, no-c-format +msgid "" +"Afterwards you need to load the images (kernel/initial ramdisk/dtb) into " +"memory. This is done with the tftpboot command, which has to be provided " +"with the address at which the image shall be stored in memory. Unfortunately " +"the memory map can vary from system to system, so there is no general rule " +"which addresses can be used for this." +msgstr "" + +#. Tag: para +#: boot-installer.xml:213 +#, no-c-format +msgid "" +"On some systems, U-Boot predefines a set of environment variables with " +"suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. You " +"can check whether they are defined by running <informalexample><screen>\n" +"printenv kernel_addr_r ramdisk_addr_r fdt_addr_r\n" +"</screen></informalexample> If they are not defined, you have to check your " +"system's documentation for appropriate values and set them manually. For " +"systems based on Allwinner SunXi SOCs (e.g. the Allwinner A10, architecture " +"name <quote>sun4i</quote> or the Allwinner A20, architecture name " +"<quote>sun7i</quote>), you can e.g. use the following values:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:224 +#, no-c-format +msgid "" +"setenv kernel_addr_r 0x46000000\n" +"setenv fdt_addr_r 0x47000000\n" +"setenv ramdisk_addr_r 0x48000000" +msgstr "" + +#. Tag: para +#: boot-installer.xml:226 +#, no-c-format +msgid "" +"When the load addresses are defined, you can load the images into memory " +"from the previously defined tftp server with" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:229 +#, no-c-format +msgid "" +"tftpboot ${kernel_addr_r} <filename of the kernel image>\n" +"tftpboot ${fdt_addr_r} <filename of the dtb>\n" +"tftpboot ${ramdisk_addr_r} <filename of the initial ramdisk image>" +msgstr "" + +#. Tag: para +#: boot-installer.xml:231 +#, no-c-format +msgid "" +"The third part is setting the kernel commandline and actually executing the " +"loaded code. U-Boot passes the content of the <quote>bootargs</quote> " +"environment variable as commandline to the kernel, so any parameters for the " +"kernel and the installer - such as the console device (see <xref linkend=" +"\"boot-console\"/>) or preseeding options (see <xref linkend=\"installer-args" +"\"/> and <xref linkend=\"appendix-preseed\"/>) - can be set with a command " +"like <informalexample><screen>\n" +"setenv bootargs console=ttyS0,115200 rootwait panic=10\n" +"</screen></informalexample> The exact command to execute the previously " +"loaded code depends on the image format used. With uImage/uInitrd, the " +"command is <informalexample><screen>\n" +"bootm ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}\n" +"</screen></informalexample> and with native Linux images it is" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:244 +#, no-c-format +msgid "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}" +msgstr "" + +#. Tag: para +#: boot-installer.xml:246 +#, no-c-format +msgid "" +"Note: When booting standard linux images, it is important to load the " +"initial ramdisk image after the kernel and the dtb as U-Boot sets the " +"filesize variable to the size of the last file loaded and the bootz command " +"requires the size of the ramdisk image to work correctly. In case of booting " +"a platform-specific kernel, i.e. a kernel without device-tree, simply omit " +"the ${fdt_addr_r} parameter." +msgstr "" + +#. Tag: title +#: boot-installer.xml:257 +#, no-c-format +msgid "Pre-built netboot tarball" +msgstr "" + +#. Tag: para +#: boot-installer.xml:258 +#, no-c-format +msgid "" +"&debian; provides a pre-built tarball (&armmp-netboot-tarball;) that can " +"simply be unpacked on your tftp server and contains all files necessary for " +"netbooting. It also includes a boot script that automates all steps to load " +"the installer. Modern U-Boot versions contain a tftp autoboot feature that " +"becomes active if there is no bootable local storage device (MMC/SD, USB, " +"IDE/SATA/SCSI) and then loads this boot script from the tftp server. " +"Prerequisite for using this feature is that you have a dhcp server in your " +"network which provides the client with the address of the tftp server." +msgstr "" + +#. Tag: para +#: boot-installer.xml:270 +#, no-c-format +msgid "" +"If you would like to trigger the tftp autoboot feature from the U-Boot " +"commandline, you can use the follwing command:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:273 +#, no-c-format +msgid "run bootcmd_dhcp" +msgstr "" + +#. Tag: para +#: boot-installer.xml:275 +#, no-c-format +msgid "" +"To manually load the bootscript provided by the tarball, you can " +"alternatively issue the following commands at the U-Boot prompt:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:279 +#, no-c-format +msgid "" +"setenv autoload no\n" +"dhcp\n" +"tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr\n" +"source ${scriptaddr}" +msgstr "" + +#. Tag: title +#: boot-installer.xml:287 +#, no-c-format +msgid "Booting from USB Memory Stick with UEFI" +msgstr "" + +#. Tag: para +#: boot-installer.xml:293 boot-installer.xml:555 +#, no-c-format +msgid "" +"If your computer will boot from USB, this will probably be the easiest route " +"for installation. Assuming you have prepared everything from <phrase arch=" +"\"any-x86\"><xref linkend=\"boot-dev-select-x86\"/></phrase><phrase arch=" +"\"arm64\"><xref linkend=\"boot-dev-select-arm64\"/></phrase> and <xref " +"linkend=\"boot-usb-files\"/>, just plug your USB stick into some free USB " +"connector and reboot the computer. The system should boot up, and unless you " +"have used the flexible way to build the stick and not enabled it, you should " +"be presented with a graphical boot menu (on hardware that supports it). Here " +"you can select various installer options, or just hit &enterkey;." +msgstr "" + +#. Tag: title +#: boot-installer.xml:312 +#, no-c-format +msgid "Booting from a USB stick in U-Boot" +msgstr "" + +#. Tag: para +#: boot-installer.xml:313 +#, no-c-format +msgid "" +"Many modern U-Boot versions have USB support and allow booting from USB mass " +"storage devices such as USB sticks. Unfortunately the exact steps required " +"to do that can vary quite a bit from device to device." +msgstr "" + +#. Tag: para +#: boot-installer.xml:320 +#, no-c-format +msgid "" +"U-Boot v2014.10 has introduced a common commandline handling and autoboot " +"framework. This allows building generic boot images that work on any system " +"implementing this framework. The &d-i; supports installation from a USB " +"stick on such systems, but unfortunately not all platforms have adopted this " +"new framework yet." +msgstr "" + +#. Tag: para +#: boot-installer.xml:329 +#, no-c-format +msgid "" +"To build a bootable USB stick for installing &debian;, unpack the hd-media " +"tarball (see <xref linkend=\"where-files\"/>) onto a USB stick formatted " +"with a filesystem supported by the U-Boot version on your device. For modern " +"U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / ext4 usually works. " +"Then copy the ISO image file of the first &debian; installation CD or DVD " +"onto the stick." +msgstr "" + +#. Tag: para +#: boot-installer.xml:339 +#, no-c-format +msgid "" +"The autoboot framework in modern U-Boot versions works similar to the boot " +"ordering options in a PC BIOS/UEFI, i.e. it checks a list of possible boot " +"devices for a valid boot image and starts the first one it finds. If there " +"is no operating system installed, plugging in the USB stick and powering up " +"the system should result in starting the installer. You can also initiate " +"the USB-boot process any time from the U-Boot prompt by entering the " +"<quote>run bootcmd_usb0</quote> command." +msgstr "" + +#. Tag: para +#: boot-installer.xml:349 +#, no-c-format +msgid "" +"One problem that can come up when booting from a USB stick while using a " +"serial console can be a console baudrate mismatch. If a console variable is " +"defined in U-Boot, the &d-i; boot script automatically passes it to the " +"kernel to set the primary console device and, if applicable, the console " +"baudrate. Unfortunately the handling of the console variable varies from " +"platform to platform - on some platforms, the console variable includes the " +"baudrate (as in <quote>console=ttyS0,115200</quote>), while on other " +"platforms the console variable contains only the device (as in " +"<quote>console=ttyS0</quote>). The latter case leads to a garbled console " +"output when the default baudrate differs between U-Boot and the kernel. " +"Modern U-Boot versions often use 115200 baud while the kernel still defaults " +"to the traditional 9600 baud. If this happens, you should manually set the " +"console variable to contain the correct baudrate for your system and then " +"start the installer with the <quote>run bootcmd_usb0</quote> command." +msgstr "" + +#. Tag: title +#: boot-installer.xml:370 +#, no-c-format +msgid "Using pre-built SD-card images with the installer" +msgstr "" + +#. Tag: para +#: boot-installer.xml:371 +#, no-c-format +msgid "" +"For a number of systems, Debian provides SD card images that contain both U-" +"Boot and the &d-i;. These images are provided in two variants - one for " +"downloading the software packages over the network (available at &armmp-" +"netboot-sd-img;) and one for offline installations using a Debian CD/DVD " +"(available at &armmp-hd-media-sd-img;). To save space and network bandwidth, " +"the images consist of two parts - a system-dependent part named " +"<quote>firmware.<system-type>.img.gz</quote>, and a system-independent " +"part named <quote>partition.img.gz</quote>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:382 +#, no-c-format +msgid "" +"To create a complete image from the two parts on Linux systems, you can use " +"zcat as follows: <informalexample><screen>zcat firmware.<system-type>." +"img.gz partition.img.gz > complete_image.img</screen></informalexample> " +"On Windows systems, you have to first decompress the two parts separately, " +"which can be done e.g. by using 7-Zip, and then concatenate the decompressed " +"parts together by running the command <informalexample><screen>copy /b " +"firmware.<system-type>.img + partition.img complete_image.img</" +"screen></informalexample> in a Windows CMD.exe window." +msgstr "" + +#. Tag: para +#: boot-installer.xml:396 +#, no-c-format +msgid "" +"Write the resulting image onto an SD card, e.g. by running the following " +"command on a Linux system: <informalexample><screen>cat complete_image.img " +"> /dev/SD_CARD_DEVICE</screen></informalexample> After plugging the SD " +"card into the target system and powering the system up, the installer is " +"loaded from the SD card. If you use the hd-media variant for offline " +"installations, you must provide the installer with access to the first " +"&debian; CD/DVD on a separate medium, which can e.g. be a CD/DVD ISO image " +"on a USB stick." +msgstr "" + +#. Tag: para +#: boot-installer.xml:408 +#, no-c-format +msgid "" +"When you come to the partitioning step in the installer (see <xref linkend=" +"\"di-partition\"/>), you can delete or replace any previous partitions on " +"the card. Once the installer is started, it runs completely in the system's " +"main memory and does not need to access the SD card anymore, so you can use " +"the full card for installing &debian;. The easiest way to create a proper " +"partition layout on the SD card is to let the installer automatically create " +"one for you (see <xref linkend=\"partman-auto\"/>)." +msgstr "" + +#. Tag: title +#: boot-installer.xml:549 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "" + +#. Tag: title +#: boot-installer.xml:573 +#, no-c-format +msgid "Booting from optical disc (CD/DVD)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:579 boot-installer.xml:986 boot-installer.xml:1929 +#, no-c-format +msgid "" +"If you have a set of optical discs, and your machine supports booting " +"directly off those, great! Simply <phrase arch=\"x86\"> configure your " +"system for booting off an optical disc as described in <xref linkend=\"boot-" +"dev-select-x86\"/>, </phrase> insert the disc, reboot, and proceed to the " +"next chapter." +msgstr "" + +#. Tag: para +#: boot-installer.xml:589 boot-installer.xml:996 boot-installer.xml:1939 +#, no-c-format +msgid "" +"Note that certain optical drives may require special drivers, and thus be " +"inaccessible in the early installation stages. If it turns out the standard " +"way of booting off an optical disc doesn't work for your hardware, revisit " +"this chapter and read about alternate kernels and installation methods which " +"may work for you." +msgstr "" + +#. Tag: para +#: boot-installer.xml:597 boot-installer.xml:1004 boot-installer.xml:1947 +#, no-c-format +msgid "" +"Even if you cannot boot from optical disc, you can probably install the " +"&debian; system components and any packages you want from such disc. Simply " +"boot using a different medium and when it's time to install the operating " +"system, base system, and any additional packages, point the installation " +"system at the optical drive." +msgstr "" + +#. Tag: para +#: boot-installer.xml:605 boot-installer.xml:1012 boot-installer.xml:1955 +#, no-c-format +msgid "" +"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:615 +#, no-c-format +msgid "Booting from Windows" +msgstr "" + +#. Tag: para +#: boot-installer.xml:616 +#, no-c-format +msgid "To start the installer from Windows, you can either" +msgstr "" + +#. Tag: para +#: boot-installer.xml:621 +#, no-c-format +msgid "" +"obtain installation media as described in <xref linkend=\"official-cdrom\"/" +"><phrase condition=\"bootable-usb\"> or <xref linkend=\"boot-usb-files\"/></" +"phrase> or" +msgstr "" + +#. Tag: para +#: boot-installer.xml:628 +#, no-c-format +msgid "" +"download a standalone Windows executable, which is available as <ulink url=" +"\"&win32-loader-exe;\">tools/win32-loader/stable/win32-loader.exe</ulink> on " +"the &debian; mirrors." +msgstr "" + +#. Tag: para +#: boot-installer.xml:637 +#, no-c-format +msgid "" +"If you use optical installation media, a pre-installation program should be " +"launched automatically when you insert the disc. In case Windows does not " +"start it automatically, or if you are using a USB memory stick, you can run " +"it manually by accessing the device and executing <command>setup.exe</" +"command>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:645 +#, no-c-format +msgid "" +"After the program has been started, a few preliminary questions will be " +"asked and the system will be prepared to reboot into the &debian-gnu; " +"installer." +msgstr "" + +#. Tag: title +#: boot-installer.xml:655 +#, no-c-format +msgid "Booting from DOS using loadlin" +msgstr "" + +#. Tag: para +#: boot-installer.xml:656 +#, no-c-format +msgid "" +"Boot into DOS (not Windows). To do this, you can for instance boot from a " +"recovery or diagnostic disk." +msgstr "" + +#. Tag: para +#: boot-installer.xml:661 +#, no-c-format +msgid "" +"If you can access the installation CD, change the current drive to the CD-" +"ROM drive, e.g. <informalexample><screen>\n" +"d:\n" +"</screen></informalexample> else make sure you have first prepared your hard " +"disk as explained in <xref linkend=\"files-loadlin\"/>, and change the " +"current drive to it if needed." +msgstr "" + +#. Tag: para +#: boot-installer.xml:671 +#, no-c-format +msgid "" +"Enter the subdirectory for the flavor you chose, e.g., " +"<informalexample><screen>\n" +"cd \\&x86-install-dir;\n" +"</screen></informalexample> If you prefer using the graphical installer, " +"enter the <filename>gtk</filename> sub-directory. <informalexample><screen>\n" +"cd gtk\n" +"</screen></informalexample> Next, execute <command>install.bat</command>. " +"The kernel will load and launch the installer system." +msgstr "" + +#. Tag: title +#: boot-installer.xml:689 +#, no-c-format +msgid "Booting from Linux using <command>GRUB</command>" +msgstr "" + +#. Tag: para +#: boot-installer.xml:692 +#, no-c-format +msgid "" +"To boot the installer from hard disk, you must first download and place the " +"needed files as described in <xref linkend=\"boot-drive-files\"/>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:697 +#, no-c-format +msgid "" +"For <command>GRUB2</command>, you will need to configure two essential " +"things in <filename>/boot/grub/grub.cfg</filename>:" +msgstr "" + +#. Tag: para +#: boot-installer.xml:701 +#, no-c-format +msgid "to load the <filename>initrd.gz</filename> installer at boot time;" +msgstr "" + +#. Tag: para +#: boot-installer.xml:706 +#, no-c-format +msgid "" +"have the <filename>vmlinuz</filename> kernel use a RAM disk as its root " +"partition." +msgstr "" + +#. Tag: para +#: boot-installer.xml:714 +#, no-c-format +msgid "An entry for the installer would be for example:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:718 +#, no-c-format +msgid "" +"menuentry 'New Install' {\n" +"insmod part_msdos\n" +"insmod ext2\n" +"set root='(hd0,msdos1)'\n" +"linux /boot/newinstall/vmlinuz\n" +"initrd /boot/newinstall/initrd.gz\n" +"}" +msgstr "" + +#. Tag: title +#: boot-installer.xml:723 boot-installer.xml:1348 boot-installer.xml:1490 +#: boot-installer.xml:1883 +#, no-c-format +msgid "Booting with TFTP" +msgstr "" + +#. Tag: para +#: boot-installer.xml:748 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "" + +#. Tag: title +#: boot-installer.xml:754 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "" + +#. Tag: para +#: boot-installer.xml:755 +#, no-c-format +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> " +"re-implementation of TFTP boot. If so, you may be able to configure your " +"BIOS/UEFI to boot from the network." +msgstr "" + +#. Tag: title +#: boot-installer.xml:766 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "" + +#. Tag: para +#: boot-installer.xml:767 +#, no-c-format +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "" + +#. Tag: para +#: boot-installer.xml:772 +#, no-c-format +msgid "" +"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. " +"Please refer to this document." +msgstr "" + +#. Tag: title +#: boot-installer.xml:780 +#, no-c-format +msgid "Etherboot" +msgstr "" + +#. Tag: para +#: boot-installer.xml:781 +#, no-c-format +msgid "" +"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" + +#. Tag: title +#: boot-installer.xml:791 +#, no-c-format +msgid "The Boot Screen" +msgstr "" + +#. Tag: para +#: boot-installer.xml:792 +#, no-c-format +msgid "" +"When the installer boots, you should be presented with a friendly graphical " +"screen showing the &debian; logo and a menu:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:797 +#, no-c-format +msgid "" +"&debian-gnu; installer boot menu\n" +"\n" +"Graphical install\n" +"Install\n" +"Advanced options >\n" +"Accessible dark contrast installer menu >\n" +"Help\n" +"Install with speech synthesis" +msgstr "" + +#. Tag: para +#: boot-installer.xml:801 +#, no-c-format +msgid "" +"This graphical screen will look very slightly different depending on how " +"your computer has booted (BIOS or UEFI), but the same options will be shown." +msgstr "" + +#. Tag: para +#: boot-installer.xml:809 +#, no-c-format +msgid "" +"Depending on the installation method you are using, the <quote>Graphical " +"install</quote> option may not be available. Bi-arch images additionally " +"have a 64 bit variant for each install option, right below it, thus almost " +"doubling the number of options." +msgstr "" + +#. Tag: para +#: boot-installer.xml:816 +#, no-c-format +msgid "" +"For a normal installation, select either the <quote>Graphical install</" +"quote> or the <quote>Install</quote> entry — using either the arrow " +"keys on your keyboard or by typing the first (highlighted) letter — " +"and press &enterkey; to boot the installer. The <quote>Graphical install</" +"quote> entry is already selected by default." +msgstr "" + +#. Tag: para +#: boot-installer.xml:824 +#, no-c-format +msgid "" +"The <quote>Advanced options</quote> entry gives access to a second menu that " +"allows to boot the installer in expert mode, in rescue mode and for " +"automated installs." +msgstr "" + +#. Tag: para +#: boot-installer.xml:830 +#, no-c-format +msgid "" +"If you wish or need to add any boot parameters for either the installer or " +"the kernel, press &tabkey; (BIOS boot), or &ekey; then &downkey; three times " +"then &endkey; (UEFI boot). This will bring the boot command for the selected " +"menu entry and allow you to edit it to suit your needs. Note that the " +"keyboard layout at this point is still QWERTY. The help screens (see below) " +"list some common possible options. Press &enterkey; (BIOS boot) or &f10key; " +"(UEFI boot) to boot the installer with your options; pressing &escapekey; " +"will return you to the boot menu and undo any changes you made." +msgstr "" + +#. Tag: para +#: boot-installer.xml:843 +#, no-c-format +msgid "" +"Choosing the <quote>Help</quote> entry will result in the first help screen " +"being displayed which gives an overview of all available help screens. To " +"return to the boot menu after the help screens have been displayed, type " +"<quote>menu</quote> at the boot prompt and press &enterkey;. All help " +"screens have a boot prompt at which the boot command can be typed: " +"<informalexample><screen>\n" +"Press F1 for the help index, or ENTER to boot:\n" +"</screen></informalexample> At this boot prompt you can either just press " +"&enterkey; to boot the installer with default options or enter a specific " +"boot command and, optionally, boot parameters. A number of boot parameters " +"which might be useful can be found on the various help screens. If you do " +"add any parameters to the boot command line, be sure to first 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 +#: boot-installer.xml:861 +#, no-c-format +msgid "" +"The keyboard is assumed to have a default American English layout at this " +"point. This means that if your keyboard has a different (language-specific) " +"layout, the characters that appear on the screen may be different from what " +"you'd expect when you type parameters. Wikipedia has a <ulink url=\"&url-us-" +"keymap;\">schema of the US keyboard layout</ulink> which can be used as a " +"reference to find the correct keys to use." +msgstr "" + +#. Tag: para +#: boot-installer.xml:871 +#, no-c-format +msgid "" +"If you are using a system that has the BIOS configured to use serial " +"console, you may not be able to see the initial graphical splash screen upon " +"booting the installer; you may even not see the boot menu. The same can " +"happen if you are installing the system via a remote management device that " +"provides a text interface to the VGA console. Examples of these devices " +"include the text console of Compaq's <quote>integrated Lights Out</quote> " +"(iLO) and HP's <quote>Integrated Remote Assistant</quote> (IRA)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:881 +#, no-c-format +msgid "" +"To bypass the graphical boot screen you can either blindly press &escapekey; " +"to get a text boot prompt, or (equally blindly) press <quote>H</quote> " +"followed by &enterkey; to select the <quote>Help</quote> option described " +"above. After that your keystrokes should be echoed at the prompt. To prevent " +"the installer from using the framebuffer for the rest of the installation, " +"you will also want to add <userinput>vga=normal fb=false</userinput> to the " +"boot prompt, as described in the help text." +msgstr "" + +#. Tag: title +#: boot-installer.xml:897 +#, no-c-format +msgid "The Graphical Installer" +msgstr "" + +#. Tag: para +#: boot-installer.xml:898 +#, no-c-format +msgid "" +"The graphical version of the installer is only available for a limited " +"number of architectures, including &arch-title;. The functionality of the " +"graphical installer is essentially the same as that of the text-based " +"installer as it basically uses the same programs, but with a different " +"frontend." +msgstr "" + +#. Tag: para +#: boot-installer.xml:906 +#, no-c-format +msgid "" +"Although the functionality is identical, the graphical installer still has a " +"few significant advantages. The main advantage is that it supports more " +"languages, namely those that use a character set that cannot be displayed " +"with the text-based <quote>newt</quote> frontend. It also has a few " +"usability advantages such as the option to use a mouse, and in some cases " +"several questions can be displayed on a single screen." +msgstr "" + +#. Tag: para +#: boot-installer.xml:915 +#, no-c-format +msgid "" +"The graphical installer is available with all CD/DVD images and with the hd-" +"media installation method. To boot the graphical installer simply select the " +"relevant option from the boot menu. Expert and rescue mode for the graphical " +"installer can be selected from the <quote>Advanced options</quote> menu. The " +"previously used boot methods <userinput>installgui</userinput>, " +"<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can " +"still be used from the boot prompt which is shown after selecting the " +"<quote>Help</quote> option in the boot menu." +msgstr "" + +#. Tag: para +#: boot-installer.xml:926 +#, no-c-format +msgid "" +"There is also a graphical installer image that can be netbooted. And there " +"is a special <quote>mini</quote> ISO image<footnote id=\"gtk-miniiso-x86\"> " +"<para> The mini ISO image can be downloaded from a &debian; mirror as " +"described in <xref linkend=\"downloading-files\"/>. Look for " +"<filename>netboot/gtk/mini.iso</filename>. </para> </footnote>, which is " +"mainly useful for testing." +msgstr "" + +#. Tag: para +#: boot-installer.xml:939 +#, no-c-format +msgid "" +"For &arch-title;, currently only an experimental <quote>mini</quote> ISO " +"image is available<footnote id=\"gtk-miniiso-powerpc\"> <para> The mini ISO " +"image can be downloaded from a &debian; mirror as described in <xref linkend=" +"\"downloading-files\"/>. Look for <filename>netboot/gtk/mini.iso</filename>. " +"</para> </footnote>. It should work on almost all PowerPC systems that have " +"an ATI graphical card, but is unlikely to work on other systems." +msgstr "" + +#. Tag: para +#: boot-installer.xml:953 +#, no-c-format +msgid "" +"Just as with the text-based installer it is possible to add boot parameters " +"when starting the graphical installer." +msgstr "" + +#. Tag: para +#: boot-installer.xml:959 +#, no-c-format +msgid "" +"The graphical installer requires significantly more memory to run than the " +"text-based installer: &minimum-memory-gtk;. If insufficient memory is " +"available, it will automatically fall back to the text-based <quote>newt</" +"quote> frontend." +msgstr "" + +#. Tag: para +#: boot-installer.xml:966 +#, no-c-format +msgid "" +"If the amount of memory in your system is below &minimum-memory;, the " +"graphical installer may fail to boot at all while booting the text-based " +"installer would still work. Using the text-based installer is recommended " +"for systems with little available memory." +msgstr "" + +#. Tag: title +#: boot-installer.xml:980 boot-installer.xml:1923 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "" + +#. Tag: title +#: boot-installer.xml:1020 +#, no-c-format +msgid "CD Contents" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1022 +#, no-c-format +msgid "" +"There are three basic variations of &debian; Install CDs. The " +"<emphasis>Business Card</emphasis> CD has a minimal installation that will " +"fit on the small form factor CD media. It requires a network connection in " +"order to install the rest of the base installation and make a usable system. " +"The <emphasis>Network Install</emphasis> CD has all of the packages for a " +"base install but requires a network connection to a &debian; mirror site in " +"order to install the extra packages one would want for a complete system . " +"The set of &debian; CDs can install a complete system from the wide range of " +"packages without needing access to the network." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1038 +#, no-c-format +msgid "" +"The IA-64 architecture uses the next generation Extensible Firmware " +"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows " +"little about the boot device other than the partition table and Master Boot " +"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted " +"disk partitions. This simplifies the often arcane process of starting a " +"system. The system boot loader and the EFI firmware that supports it have a " +"full filesystem to store the files necessary for booting the machine. This " +"means that the system disk on an IA-64 system has an additional disk " +"partition dedicated to EFI instead of the simple MBR or boot block on more " +"conventional systems." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1054 +#, no-c-format +msgid "" +"The &debian; Installer CD contains a small EFI partition where the " +"<command>ELILO</command> bootloader, its configuration file, the installer's " +"kernel, and initial filesystem (initrd) are located. The running system also " +"contains an EFI partition where the necessary files for booting the system " +"reside. These files are readable from the EFI Shell as described below." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1063 +#, no-c-format +msgid "" +"Most of the details of how <command>ELILO</command> actually loads and " +"starts a system are transparent to the system installer. However, the " +"installer must set up an EFI partition prior to installing the base system. " +"Otherwise, the installation of <command>ELILO</command> will fail, rendering " +"the system un-bootable. The EFI partition is allocated and formatted in the " +"partitioning step of the installation prior to loading any packages on the " +"system disk. The partitioning task also verifies that a suitable EFI " +"partition is present before allowing the installation to proceed." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1075 +#, no-c-format +msgid "" +"The EFI Boot Manager is presented as the last step of the firmware " +"initialization. It displays a menu list from which the user can select an " +"option. Depending on the model of system and what other software has been " +"loaded on the system, this menu may be different from one system to another. " +"There should be at least two menu items displayed, <command>Boot Option " +"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. " +"Using the first option is preferred, however, if that option is not " +"available or the CD for some reason does not boot with it, use the second " +"option." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1094 +#, no-c-format +msgid "IMPORTANT" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1095 +#, no-c-format +msgid "" +"The EFI Boot Manager will select a default boot action, typically the first " +"menu choice, within a pre-set number of seconds. This is indicated by a " +"countdown at the bottom of the screen. Once the timer expires and the " +"systems starts the default action, you may have to reboot the machine in " +"order to continue the installation. If the default action is the EFI Shell, " +"you can return to the Boot Manager by running <command>exit</command> at the " +"shell prompt." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1107 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1114 +#, no-c-format +msgid "" +"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " +"display the EFI Boot Manager page and menu after it completes its system " +"initialization." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1120 +#, no-c-format +msgid "" +"Select <command>Boot Maintenance Menu</command> from the menu with the arrow " +"keys and press <command>ENTER</command>. This will display a new menu." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1126 +#, no-c-format +msgid "" +"Select <command>Boot From a File</command> from the menu with the arrow keys " +"and press <command>ENTER</command>. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media " +"Boot</command>. If you examine the rest of the menu line, you will notice " +"that the device and controller information should be the same." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1137 +#, no-c-format +msgid "" +"You can choose either of the entries that refer to the CD/DVD drive. Select " +"your choice with the arrow keys and press <command>ENTER</command>. If you " +"choose <command>Removable Media Boot</command> the machine will immediately " +"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</" +"command> instead, it will display a directory listing of the bootable " +"portion of the CD, requiring you to proceed to the next (additional) step." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1148 +#, no-c-format +msgid "" +"You will only need this step if you chose <command>Debian Inst [Acpi ...</" +"command>. The directory listing will also show <command>[Treat like " +"Removable Media Boot]</command> on the next to the last line. Select this " +"line with the arrow keys and press <command>ENTER</command>. This will start " +"the boot load sequence." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1160 +#, no-c-format +msgid "" +"These steps start the &debian; boot loader which will display a menu page " +"for you to select a boot kernel and options. Proceed to selecting the boot " +"kernel and options." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1170 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1171 +#, no-c-format +msgid "" +"If, for some reason, option 1 is not successful, reboot the machine and when " +"the EFI Boot Manager screen appears there should be one option called " +"<command>EFI Shell [Built-in]</command>. Boot the &debian; Installer CD with " +"the following steps:" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1182 +#, no-c-format +msgid "" +"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " +"display the EFI Boot Manager page and menu after it completes system " +"initialization." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1188 +#, no-c-format +msgid "" +"Select <command>EFI Shell</command> from the menu with the arrow keys and " +"press <command>ENTER</command>. The EFI Shell will scan all of the bootable " +"devices and display them to the console before displaying its command " +"prompt. The recognized bootable partitions on devices will show a device " +"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other " +"recognized partitions will be named <filename>blk<replaceable>n</" +"replaceable>:</filename>. If you inserted the CD just before entering the " +"shell, this may take a few extra seconds as it initializes the CD drive." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1202 +#, no-c-format +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the <filename>fs0:</filename> device although other devices with " +"bootable partitions will also show up as <filename>fs<replaceable>n</" +"replaceable></filename>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1209 +#, no-c-format +msgid "" +"Enter <command>fs<replaceable>n</replaceable>:</command> and press " +"<command>ENTER</command> to select that device where <replaceable>n</" +"replaceable> is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1216 +#, no-c-format +msgid "" +"Enter <command>elilo</command> and press <command>ENTER</command>. This will " +"start the boot load sequence." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1223 +#, no-c-format +msgid "" +"As with option 1, these steps start the &debian; boot loader which will " +"display a menu page for you to select a boot kernel and options. You can " +"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</" +"command> command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1237 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1239 +#, no-c-format +msgid "" +"You may choose to perform an install using a monitor and keyboard or using a " +"serial connection. To use a monitor/keyboard setup, select an option " +"containing the string [VGA console]. To install over a serial connection, " +"choose an option containing the string [<replaceable>BAUD</replaceable> baud " +"serial console], where <replaceable>BAUD</replaceable> is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1250 +#, no-c-format +msgid "" +"In most circumstances, you will want the installer to use the same baud rate " +"as your connection to the EFI console. If you aren't sure what this setting " +"is, you can obtain it using the command <command>baud</command> at the EFI " +"shell." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1257 +#, no-c-format +msgid "" +"If there is not an option available that is configured for the serial device " +"or baud rate you would like to use, you may override the console setting for " +"one of the existing menu options. For example, to use a 57600 baud console " +"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into " +"the <classname>Boot:</classname> text window." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "" +"Most IA-64 boxes ship with a default console setting of 9600 baud. This " +"setting is rather slow, and the normal installation process will take a " +"significant time to draw each screen. You should consider either increasing " +"the baud rate used for performing the installation, or performing a Text " +"Mode installation. See the <classname>Params</classname> help menu for " +"instructions on starting the installer in Text Mode." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1277 +#, no-c-format +msgid "" +"If you select the wrong console type, you will be able to select the kernel " +"and enter parameters but both the display and your input will go dead as " +"soon as the kernel starts, requiring you to reboot before you can begin the " +"installation." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1286 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1288 +#, no-c-format +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a <classname>Boot:</classname> prompt. The arrow keys select an item from " +"the menu and any text typed at the keyboard will appear in the text window. " +"There are also help screens which can be displayed by pressing the " +"appropriate function key. The <classname>General</classname> help screen " +"explains the menu choices and the <classname>Params</classname> screen " +"explains the common command line options." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1300 +#, no-c-format +msgid "" +"Consult the <classname>General</classname> help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult <xref linkend=\"boot-parms\"/> below for any additional " +"parameters that you may want to set in the <classname>Boot:</classname> text " +"window. The kernel version you choose selects the kernel version that will " +"be used for both the installation process and the installed system. If you " +"encounter kernel problems with the installation, you may also have those " +"same problems with the system you install. The following two steps will " +"select and start the install:" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1318 +#, no-c-format +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1323 +#, no-c-format +msgid "" +"Enter any boot parameters by typing at the keyboard. The text will be " +"displayed directly in the text window. This is where kernel parameters (such " +"as serial console settings) are specified." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1330 +#, no-c-format +msgid "" +"Press <command>ENTER</command>. This will load and start the kernel. The " +"kernel will display its usual initialization messages followed by the first " +"screen of the &debian; Installer." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1339 boot-installer.xml:1476 +#, no-c-format +msgid "" +"Proceed to the next chapter to continue the installation where you will set " +"up the language locale, network, and disk partitions." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1350 +#, no-c-format +msgid "" +"Booting an IA-64 system from the network is similar to a CD boot. The only " +"difference is how the installation kernel is loaded. The EFI Boot Manager " +"can load and start programs from a server on the network. Once the " +"installation kernel is loaded and starts, the system install will proceed " +"through the same steps as the CD install with the exception that the " +"packages of the base install will be loaded from the network rather than the " +"CD drive." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1385 +#, no-c-format +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"<command>elilo</command>. On the client a new boot option must be defined in " +"the EFI boot manager to enable loading over a network." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1396 +#, no-c-format +msgid "Configuring the Server" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1397 +#, no-c-format +msgid "" +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: <informalexample><screen>\n" +"host mcmuffin {\n" +" hardware ethernet 00:30:6e:1e:0e:83;\n" +" fixed-address 10.0.0.21;\n" +" filename \"debian-installer/ia64/elilo.efi\";\n" +"}\n" +"</screen></informalexample> Note that the goal is to get <command>elilo.efi</" +"command> running on the client." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1407 +#, no-c-format +msgid "" +"Extract the <filename>netboot.tar.gz</filename> file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This " +"will create a <filename>debian-installer</filename> directory tree " +"containing the boot files for an IA-64 system." +msgstr "" + +#. Tag: screen +#: boot-installer.xml:1417 +#, no-c-format +msgid "" +"# cd /var/lib/tftp\n" +"# tar xvfz /home/user/netboot.tar.gz\n" +"./\n" +"./debian-installer/\n" +"./debian-installer/ia64/\n" +"[...]" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1417 +#, no-c-format +msgid "" +"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</" +"filename> file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the <filename>debian-" +"installer/ia64/</filename> directory. It is possible to have different " +"config files for different clients by naming them using the client's IP " +"address in hex with the suffix <filename>.conf</filename> instead of " +"<filename>elilo.conf</filename>. See documentation provided in the " +"<classname>elilo</classname> package for details." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1434 +#, no-c-format +msgid "Configuring the Client" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1435 +#, no-c-format +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> " +"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You " +"should see one or more lines with the text <guimenuitem>Load File " +"[Acpi()/.../Mac()]</guimenuitem>. If more than one of these entries exist, " +"choose the one containing the MAC address of the interface from which you'll " +"be booting. Use the arrow keys to highlight your choice, then press enter. </" +"para></listitem> <listitem><para> Name the entry <userinput>Netboot</" +"userinput> or something similar, save, and exit back to the boot options " +"menu. </para></listitem> </itemizedlist> You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of <filename>elilo.efi</filename> from the server." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1467 +#, no-c-format +msgid "" +"The boot loader will display its prompt after it has downloaded and " +"processed its configuration file. At this point, the installation proceeds " +"with the same steps as a CD install. Select a boot option as in above and " +"when the kernel has completed installing itself from the network, it will " +"start the &debian; Installer." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1521 +#, no-c-format +msgid "S/390 Limitations" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1522 +#, no-c-format +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1527 +#, no-c-format +msgid "" +"The booting process starts with a network setup that prompts you for several " +"network parameters. If the setup is successful, you will login to the system " +"by starting an ssh session which will launch the standard installation " +"system." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1538 +#, no-c-format +msgid "S/390 Boot Parameters" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1539 +#, no-c-format +msgid "" +"On S/390 you can append boot parameters in the parm file. This file can " +"either be in ASCII or EBCDIC format. It needs to be fixed-width with 80 " +"characters per line. A sample parm file <filename>parmfile.debian</filename> " +"is provided with the installation images. If a parameter is too long to fit " +"into the 80 characters limit it can simply be continued in the first column " +"of the next line. All the lines are concatenated without spaces when being " +"passed to the kernel." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1556 +#, no-c-format +msgid "" +"If you boot the installer in a logical partition (LPAR) or virtual machine " +"(VM) where a lot of devices are visible, you can instruct the kernel to " +"restrict the list to a fixed set of devices. This is advised for the " +"installer's boot process if a lot of disks are visible, most likely in LPAR " +"mode. The <quote>cio_ignore</quote> option supports both a blacklist (to " +"only disallow a few devices) and a whitelist (to only allow specific " +"devices): <informalexample role=\"example\"><screen>\n" +" # blacklist: just ignore the two devices 300 and 301\n" +" cio_ignore=0.0.0300-0.0.0301\n" +" # whitelist: ignore everything but 1150, FD00, FD01 and FD02\n" +" cio_ignore=all,!0.0.1150,!0.0.fd00-0.0.fd02\n" +"</screen></informalexample> Please note that all devices numbers' hex digits " +"need to be specified in lower case. Furthermore if this boot parameter is " +"used all devices need to be listed: this includes at least disks, network " +"devices and the console. To be considered during the installer's boot " +"process the above option needs to be added to <filename>parmfile.debian</" +"filename>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1841 +#, no-c-format +msgid "Booting a ppc64el machine" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1842 +#, no-c-format +msgid "How to boot a ppc64el machine:" +msgstr "" + +#. Tag: title +#: boot-installer.xml:1848 +#, no-c-format +msgid "Petitboot" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1849 +#, no-c-format +msgid "" +"Petitboot is a platform independent bootloader based on the Linux kexec. " +"Petitboot supports loading kernel, initrd and device tree files from any " +"Linux mountable filesystem, plus can load files from the network using the " +"FTP, SFTP, TFTP, NFS, HTTP and HTTPS protocols. Petitboot can boot any " +"operating system that includes kexec boot support." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1857 +#, no-c-format +msgid "" +"Petitboot looks for bootloader configuration files on mountable devices in " +"the system, and can also be configured to use boot information from a DHCP " +"server." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1908 +#, no-c-format +msgid "" +"On machines with OpenBoot, simply enter the boot monitor on the machine " +"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use " +"the command <userinput>boot net</userinput> to boot from a TFTP and RARP " +"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:" +"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. You can pass " +"extra boot parameters to &d-i; at the end of the <userinput>boot</userinput> " +"command." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1962 +#, no-c-format +msgid "" +"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command " +"which is simply an alias to boot from the SCSI device on ID 6 (or the " +"secondary master for IDE based systems)." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1971 +#, no-c-format +msgid "IDPROM Messages" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1972 +#, no-c-format +msgid "" +"If you cannot boot because you get messages about a problem with " +"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which " +"holds configuration information for you firmware, has run out. See the " +"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more " +"information." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1991 +#, no-c-format +msgid "Accessibility" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1992 +#, no-c-format +msgid "" +"Some users may need specific support because of e.g. some visual impairment. " +"<phrase arch=\"ia64;powerpc;ppc64el;x86\">USB braille displays are detected " +"automatically (not serial displays connected via a serial-to-USB converter), " +"but most other</phrase> <phrase arch=\"arm;hppa;mips;mipsel;mips64el;sparc" +"\">Most</phrase> accessibility features have to be enabled manually. <phrase " +"arch=\"x86\">On machines that support it, the boot menu emits beeps when it " +"is ready to receive keystrokes. It beeps once on BIOS systems, and beeps " +"twice on UEFI systems.</phrase> Some boot parameters can <phrase arch=" +"\"x86\">then</phrase> be appended to enable accessibility features<phrase " +"arch=\"x86\"> (see also <xref linkend=\"boot-screen\"/>)</phrase>. Note that " +"on most architectures the boot loader interprets your keyboard as a QWERTY " +"keyboard." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2012 +#, no-c-format +msgid "Installer front-end" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2013 +#, no-c-format +msgid "" +"The &debian; installer supports several front-ends for asking questions, " +"with varying convenience for accessibility: notably, <userinput>text</" +"userinput> uses plain text while <userinput>newt</userinput> uses text-based " +"dialog boxes. The choice can be made at the boot prompt, see the " +"documentation for <userinput>DEBIAN_FRONTEND</userinput> in <xref linkend=" +"\"installer-args\"/>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2025 +#, no-c-format +msgid "USB Braille Displays" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2026 +#, no-c-format +msgid "" +"USB braille displays should be automatically detected. A textual version of " +"the installer will then be automatically selected, and support for the " +"braille display will be automatically installed on the target system. You " +"can thus just press &enterkey; at the boot menu. Once <classname>brltty</" +"classname> is started, you can choose a braille table by entering the " +"preference menu. Documentation on key bindings for braille devices is " +"available on the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</" +"classname> website</ulink>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2041 +#, no-c-format +msgid "Serial Braille Displays" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2042 +#, no-c-format +msgid "" +"Serial braille displays cannot safely be automatically detected (since that " +"may damage some of them). You thus need to append the " +"<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</" +"replaceable></userinput> boot parameter to tell <classname>brltty</" +"classname> which driver and port it should use. <replaceable>driver</" +"replaceable> should be replaced by the two-letter driver code for your " +"terminal (see the <ulink url=\"&url-brltty-manual;\">BRLTTY manual</ulink>). " +"<replaceable>port</replaceable> should be replaced by the name of the serial " +"port the display is connected to, <userinput>ttyS0</userinput> is the " +"default, <userinput>ttyUSB0</userinput> can be typically used when using a " +"serial-to-USB converter. A third parameter can be provided, to choose the " +"name of the braille table to be used (see the <ulink url=\"&url-brltty-" +"manual;\">BRLTTY manual</ulink>); the English table is the default. Note " +"that the table can be changed later by entering the preference menu. A " +"fourth parameter can be provided to pass parameters to the braille driver, " +"such as <userinput>protocol=foo</userinput> which is needed for some rare " +"models. Documentation on key bindings for braille devices is available on " +"the <ulink url=\"&url-brltty-driver-help;\"><classname>brltty</classname> " +"website</ulink>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2069 boot-installer.xml:3061 +#, no-c-format +msgid "Software Speech Synthesis" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2070 +#, no-c-format +msgid "" +"Support for software speech synthesis is available on all installer images " +"which have the graphical installer, i.e. all netinst, CD and DVD images, and " +"the netboot gtk variant. It can be activated by selecting it in the boot " +"menu by typing <userinput>s</userinput> &enterkey;. The textual version of " +"the installer will then be automatically selected, and support for software " +"speech synthesis will be automatically installed on the target system." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2079 +#, no-c-format +msgid "" +"If several sound cards are detected, you will be prompted to press " +"&enterkey; when you hear speech from the desired sound card." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2084 +#, no-c-format +msgid "" +"The first question (language) is spoken in english, and the remainder of " +"installation is spoken in the selected language (if available in " +"<classname>espeak</classname>)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2090 +#, no-c-format +msgid "" +"The default speech rate is quite slow. To make it faster, press " +"<keycombo><keycap>CapsLock</keycap><keycap>6</keycap></keycombo>. To make it " +"slower, press <keycombo><keycap>CapsLock</keycap><keycap>5</keycap></" +"keycombo>. The default volume should be medium. To make it louder, press " +"<keycombo><keycap>CapsLock</keycap><keycap>2</keycap></keycombo>. To make it " +"quieter, press <keycombo><keycap>CapsLock</keycap><keycap>1</keycap></" +"keycombo>. To get more details on the browsing shortcuts, see the <ulink url=" +"\"&url-speakup-guide;\">Speakup guide</ulink>. To just accept the default " +"answer for a question, simply press <keycap>Enter</keycap> at the prompt. To " +"provide an empty answer for a question, type <userinput>!</userinput> at the " +"prompt. To get back to the previous question, type <userinput><</" +"userinput> at the prompt." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2118 +#, no-c-format +msgid "Hardware Speech Synthesis" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2119 +#, no-c-format +msgid "" +"Support for hardware speech synthesis devices is available on all installer " +"images which have the graphical installer, i.e. all netinst, CD and DVD " +"images, and the netboot gtk variant. You thus need to select a " +"<quote>Graphical install</quote> entry in the boot menu." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2126 +#, no-c-format +msgid "" +"Hardware speech synthesis devices cannot be automatically detected. You thus " +"need to append the <userinput>speakup.synth=<replaceable>driver</" +"replaceable></userinput> boot parameter to tell <classname>speakup</" +"classname> which driver it should use. <replaceable>driver</replaceable> " +"should be replaced by the driver code for your device (see <ulink url=\"&url-" +"speakup-guide;\">driver code list</ulink>). The textual version of the " +"installer will then be automatically selected, and support for the speech " +"synthesis device will be automatically installed on the target system." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2141 +#, no-c-format +msgid "Board Devices" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2142 +#, no-c-format +msgid "" +"Some accessibility devices are actual boards that are plugged inside the " +"machine and that read text directly from the video memory. To get them to " +"work framebuffer support must be disabled by using the <userinput arch=" +"\"x86\">vga=normal</userinput> <userinput>fb=false</userinput> boot " +"parameter. This will however reduce the number of available languages." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2150 +#, no-c-format +msgid "" +"If desired a textual version of the bootloader can be activated before " +"adding the boot parameter by typing <userinput>h</userinput> &enterkey;." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2158 +#, no-c-format +msgid "High-Contrast Theme" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2159 +#, no-c-format +msgid "" +"For users with low vision, the installer can use a high-contrast color theme " +"that makes it more readable. To enable it, you can use the <quote>Accessible " +"high contrast</quote> entry from the boot screen with the <userinput>d</" +"userinput> shortcut, or append the <userinput>theme=dark</userinput> boot " +"parameter." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2170 +#, no-c-format +msgid "Zoom" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2171 +#, no-c-format +msgid "" +"For users with low vision, the graphical installer has a very basic zoom " +"support: the <keycombo><keycap>Control</keycap> <keycap>+</keycap></" +"keycombo> and <keycombo><keycap>Control</keycap> <keycap>-</keycap></" +"keycombo> shortcuts increase and decrease the font size." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2181 +#, no-c-format +msgid "Expert install, rescue mode, automated install" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2182 +#, no-c-format +msgid "" +"Expert, Rescue, and Automated installation choices are also available with " +"accessibility support. To access them, one has to first enter the " +"<quote>Advanced options</quote> submenu from the boot menu by typing " +"<userinput>a</userinput>. When using a BIOS system (the boot menu will have " +"beeped only once), this has to be followed by &enterkey; ; for UEFI systems " +"(the boot menu will have beeped twice) that must not be done. Then, to " +"enable speech synthesis, <userinput>s</userinput> can optionally be pressed " +"(followed again by &enterkey; on BIOS systems but not on UEFI systems). From " +"there, various shortcuts can be used: <userinput>x</userinput> for expert " +"installation, <userinput>r</userinput> for rescue mode, or <userinput>a</" +"userinput> for automated installation. Again these need to be followed by " +"&enterkey; when using a BIOS system." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2197 +#, no-c-format +msgid "" +"The automated install choice allows to install &debian; completely " +"automatically by using preseeding, whose source can be entered after " +"accessibility features get started. Preseeding itself is documented in <xref " +"linkend=\"appendix-preseed\"/>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2207 +#, no-c-format +msgid "Accessibility of the installed system" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2208 +#, no-c-format +msgid "" +"Documentation on accessibility of the installed system is available on the " +"<ulink url=\"&url-debian-wiki-accessibility;\">Debian Accessibility wiki " +"page</ulink>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2222 +#, no-c-format +msgid "Boot Parameters" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2223 +#, no-c-format +msgid "" +"Boot parameters are Linux kernel parameters which are generally used to make " +"sure that peripherals are dealt with properly. For the most part, the kernel " +"can auto-detect information about your peripherals. However, in some cases " +"you'll have to help the kernel a bit." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2230 +#, no-c-format +msgid "" +"If this is the first time you're booting the system, try the default boot " +"parameters (i.e., don't try setting parameters) and see if it works " +"correctly. It probably will. If not, you can reboot later and look for any " +"special parameters that inform the system about your hardware." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2237 +#, no-c-format +msgid "" +"Information on many boot parameters can be found in the <ulink url=\"http://" +"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in <xref " +"linkend=\"boot-troubleshooting\"/>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2249 +#, no-c-format +msgid "Boot console" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2251 +#, no-c-format +msgid "" +"If you are booting with a serial console, generally the kernel will " +"autodetect this. If you have a videocard (framebuffer) and a keyboard also " +"attached to the computer which you wish to boot via serial console, you may " +"have to pass the <userinput>console=<replaceable>device</replaceable></" +"userinput> argument to the kernel, where <replaceable>device</replaceable> " +"is your serial device, which is usually something like <filename>ttyS0</" +"filename>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2263 +#, no-c-format +msgid "" +"You may need to specify parameters for the serial port, such as speed and " +"parity, for instance <userinput>console=ttyS0,9600n8</userinput>; other " +"typical speeds may be 57600 or 115200. Be sure to specify this option after " +"<quote>---</quote>, so that it is copied into the bootloader configuration " +"for the installed system (if supported by the installer for the bootloader)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2271 +#, no-c-format +msgid "" +"In order to ensure the terminal type used by the installer matches your " +"terminal emulator, the parameter <userinput>TERM=<replaceable>type</" +"replaceable></userinput> can be added. Note that the installer only supports " +"the following terminal types: <literal>linux</literal>, <literal>bterm</" +"literal>, <literal>ansi</literal>, <literal>vt102</literal> and " +"<literal>dumb</literal>. The default for serial console in &d-i; is " +"<userinput>vt102</userinput>. If you are using an IPMI console, or a " +"virtualization tool which does not provide conversion into such terminals " +"types itself, e.g. QEMU/KVM, you can start it inside a <command>screen</" +"command> session. That will indeed perform translation into the " +"<literal>screen</literal> terminal type, which is very close to " +"<literal>vt102</literal>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2287 +#, no-c-format +msgid "" +"For &arch-title; the serial devices are <filename>ttya</filename> or " +"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</" +"envar> and <envar>output-device</envar> OpenPROM variables to " +"<filename>ttya</filename>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2299 +#, no-c-format +msgid "&debian; Installer Parameters" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2300 +#, no-c-format +msgid "" +"The installation system recognizes a few additional boot " +"parameters<footnote> <para> With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. Also there is a limit of 255 characters for " +"the whole kernel command line, everything above this limit may be silently " +"truncated. </para> </footnote> which may be useful." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2315 +#, no-c-format +msgid "" +"A number of parameters have a <quote>short form</quote> that helps avoid the " +"limitations of the kernel command line options and makes entering the " +"parameters easier. If a parameter has a short form, it will be listed in " +"brackets behind the (normal) long form. Examples in this manual will " +"normally use the short form too." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2327 +#, no-c-format +msgid "debconf/priority (priority)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2328 +#, no-c-format +msgid "This parameter sets the lowest priority of messages to be displayed." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2332 +#, no-c-format +msgid "" +"The default installation uses <userinput>priority=high</userinput>. This " +"means that both high and critical priority messages are shown, but medium " +"and low priority messages are skipped. If problems are encountered, the " +"installer adjusts the priority as needed." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2339 +#, no-c-format +msgid "" +"If you add <userinput>priority=medium</userinput> as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When <userinput>priority=low</userinput> is used, all messages " +"are shown (this is equivalent to the <emphasis>expert</emphasis> boot " +"method). With <userinput>priority=critical</userinput>, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2353 +#, no-c-format +msgid "DEBIAN_FRONTEND" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2354 +#, no-c-format +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: <itemizedlist> " +"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></" +"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</" +"userinput></para> </listitem><listitem> " +"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </" +"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> " +"</listitem> </itemizedlist> The default frontend is " +"<userinput>DEBIAN_FRONTEND=newt</userinput>. " +"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial " +"console installs. Some specialized types of install media may only offer a " +"limited selection of frontends, but the <userinput>newt</userinput> and " +"<userinput>text</userinput> frontends are available on most default install " +"media. On architectures that support it, the graphical installer uses the " +"<userinput>gtk</userinput> frontend." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2385 +#, no-c-format +msgid "BOOT_DEBUG" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2386 +#, no-c-format +msgid "" +"Setting this boot parameter to 2 will cause the installer's boot process to " +"be verbosely logged. Setting it to 3 makes debug shells available at " +"strategic points in the boot process. (Exit the shells to continue the boot " +"process.)" +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:2395 +#, no-c-format +msgid "BOOT_DEBUG=0" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2396 +#, no-c-format +msgid "This is the default." +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:2400 +#, no-c-format +msgid "BOOT_DEBUG=1" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2401 +#, no-c-format +msgid "More verbose than usual." +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:2405 +#, no-c-format +msgid "BOOT_DEBUG=2" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2406 +#, no-c-format +msgid "Lots of debugging information." +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:2410 +#, no-c-format +msgid "BOOT_DEBUG=3" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2411 +#, no-c-format +msgid "" +"Shells are run at various points in the boot process to allow detailed " +"debugging. Exit the shell to continue the boot." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2425 +#, no-c-format +msgid "log_host" +msgstr "" + +#. Tag: term +#: boot-installer.xml:2426 +#, no-c-format +msgid "log_port" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2427 +#, no-c-format +msgid "" +"Causes the installer to send log messages to a remote syslog on the " +"specified host and port as well as to a local file. If not specified, the " +"port defaults to the standard syslog port 514." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2438 +#, no-c-format +msgid "lowmem" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2439 +#, no-c-format +msgid "" +"Can be used to force the installer to a lowmem level higher than the one the " +"installer sets by default based on available memory. Possible values are 1 " +"and 2. See also <xref linkend=\"lowmem\"/>." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2449 +#, no-c-format +msgid "noshell" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2450 +#, no-c-format +msgid "" +"Prevents the installer from offering interactive shells on tty2 and tty3. " +"Useful for unattended installations where physical security is limited." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2459 +#, no-c-format +msgid "debian-installer/framebuffer (fb)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2460 +#, no-c-format +msgid "" +"Some architectures use the kernel framebuffer to offer installation in a " +"number of languages. If framebuffer causes a problem on your system you can " +"disable the feature using the parameter <userinput arch=\"x86\">vga=normal</" +"userinput> <userinput>fb=false</userinput>. Problem symptoms are error " +"messages about bterm or bogl, a blank screen, or a freeze within a few " +"minutes after starting the install." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2469 +#, no-c-format +msgid "Such problems have been reported on hppa." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2473 +#, no-c-format +msgid "" +"Because of display problems on some systems, framebuffer support is " +"<emphasis>disabled by default</emphasis> for &arch-title;. This can result " +"in ugly display on systems that do properly support the framebuffer, like " +"those with ATI graphical cards. If you see display problems in the " +"installer, you can try booting with parameter <userinput>debian-installer/" +"framebuffer=true</userinput> or <userinput>fb=true</userinput> for short." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2487 +#, no-c-format +msgid "debian-installer/theme (theme)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2488 +#, no-c-format +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). Which themes are available may differ per frontend. Currently " +"both the newt and gtk frontend have (apart from the default look) only one " +"additional theme named <quote>dark</quote> theme, which was designed for " +"visually impaired users. Set this theme by booting with " +"<userinput>theme=<replaceable>dark</replaceable></userinput> (there is also " +"the keyboard shortcut <userinput>d</userinput> for this in the boot menu)." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2503 boot-installer.xml:2736 +#, no-c-format +msgid "netcfg/disable_autoconfig" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2504 +#, no-c-format +msgid "" +"By default, the &d-i; automatically probes for network configuration via " +"IPv6 autoconfiguration and DHCP. If the probe succeeds, you won't have a " +"chance to review and change the obtained settings. You can get to the manual " +"network setup only in case the automatic configuration fails." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2511 +#, no-c-format +msgid "" +"If you have an IPv6 router or a DHCP server on your local network, but want " +"to avoid them because e.g. they give wrong answers, you can use the " +"parameter <userinput>netcfg/disable_autoconfig=true</userinput> to prevent " +"any automatic configuration of the network (neither v4 nor v6) and to enter " +"the information manually." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2522 +#, no-c-format +msgid "hw-detect/start_pcmcia" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2523 +#, no-c-format +msgid "" +"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2533 +#, no-c-format +msgid "disk-detect/dmraid/enable (dmraid)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2534 +#, no-c-format +msgid "" +"Set to <userinput>true</userinput> to enable support for Serial ATA RAID " +"(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note " +"that this support is currently experimental. Additional information can be " +"found on the <ulink url=\"&url-d-i-wiki;\">&debian; Installer Wiki</ulink>." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2545 +#, no-c-format +msgid "preseed/url (url)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2546 +#, no-c-format +msgid "" +"Specify the url to a preconfiguration file to download and use for " +"automating the install. See <xref linkend=\"automatic-install\"/>." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2555 +#, no-c-format +msgid "preseed/file (file)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2556 +#, no-c-format +msgid "" +"Specify the path to a preconfiguration file to load for automating the " +"install. See <xref linkend=\"automatic-install\"/>." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2565 +#, no-c-format +msgid "preseed/interactive" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2566 +#, no-c-format +msgid "" +"Set to <userinput>true</userinput> to display questions even if they have " +"been preseeded. Can be useful for testing or debugging a preconfiguration " +"file. Note that this will have no effect on parameters that are passed as " +"boot parameters, but for those a special syntax can be used. See <xref " +"linkend=\"preseed-seenflag\"/> for details." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2578 +#, no-c-format +msgid "auto-install/enable (auto)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2579 +#, no-c-format +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. See <xref linkend=\"preseed-auto\"/> for " +"details about using this to automate installs." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2590 +#, no-c-format +msgid "finish-install/keep-consoles" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2591 +#, no-c-format +msgid "" +"During installations from serial or management console, the regular virtual " +"consoles (VT1 to VT6) are normally disabled in <filename>/etc/inittab</" +"filename>. Set to <userinput>true</userinput> to prevent this." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2602 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2603 +#, no-c-format +msgid "" +"By default, before rebooting, &d-i; automatically ejects the optical media " +"used during the installation. This can be unnecessary if the system does not " +"automatically boot off such media. In some cases it may even be undesirable, " +"for example if the optical drive cannot reinsert the media itself and the " +"user is not there to do it manually. Many slot loading, slim-line, and caddy " +"style drives cannot reload media automatically." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2612 +#, no-c-format +msgid "" +"Set to <userinput>false</userinput> to disable automatic ejection, and be " +"aware that you may need to ensure that the system does not automatically " +"boot from the optical drive after the initial installation." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2623 +#, no-c-format +msgid "base-installer/install-recommends (recommends)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2624 +#, no-c-format +msgid "" +"By setting this option to <userinput>false</userinput>, the package " +"management system will be configured to not automatically install " +"<quote>Recommends</quote>, both during the installation and for the " +"installed system. See also <xref linkend=\"di-install-base\"/>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2631 +#, no-c-format +msgid "" +"Note that this option allows to have a leaner system, but can also result in " +"features being missing that you might normally expect to be available. You " +"may have to manually install some of the recommended packages to obtain the " +"full functionality you want. This option should therefore only be used by " +"very experienced users." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2643 +#, no-c-format +msgid "debian-installer/allow_unauthenticated" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2644 +#, no-c-format +msgid "" +"By default the installer requires that repositories be authenticated using a " +"known gpg key. Set to <userinput>true</userinput> to disable that " +"authentication. <emphasis role=\"bold\">Warning: insecure, not recommended.</" +"emphasis>" +msgstr "" + +#. Tag: term +#: boot-installer.xml:2655 +#, no-c-format +msgid "ramdisk_size" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2656 +#, no-c-format +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:2666 +#, no-c-format +msgid "rescue/enable" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2667 +#, 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:2680 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2681 +#, 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:2693 +#, no-c-format +msgid "debian-installer/language (language)" +msgstr "" + +#. Tag: term +#: boot-installer.xml:2694 +#, no-c-format +msgid "debian-installer/country (country)" +msgstr "" + +#. Tag: term +#: boot-installer.xml:2695 +#, no-c-format +msgid "debian-installer/locale (locale)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2696 +#, no-c-format +msgid "" +"There are two ways to specify the language, country and locale to use for " +"the installation and the installed system." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2701 +#, no-c-format +msgid "" +"The first and easiest is to pass only the parameter <literal>locale</" +"literal>. Language and country will then be derived from its value. You can " +"for example use <userinput>locale=de_CH</userinput> to select German as " +"language and Switzerland as country (<literal>de_CH.UTF-8</literal> will be " +"set as default locale for the installed system). Limitation is that not all " +"possible combinations of language, country and locale can be achieved this " +"way." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2710 +#, no-c-format +msgid "" +"The second, more flexible option is to specify <literal>language</literal> " +"and <literal>country</literal> separately. In this case <literal>locale</" +"literal> can optionally be added to specify a specific default locale for " +"the installed system. Example: <userinput>language=en country=DE " +"locale=en_GB.UTF-8</userinput>." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2722 +#, no-c-format +msgid "anna/choose_modules (modules)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2723 +#, 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)<phrase arch=\"not-s390\"> and " +"<classname>ppp-udeb</classname> (see <xref linkend=\"pppoe\"/>)</phrase>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2737 +#, no-c-format +msgid "" +"Set to <userinput>true</userinput> if you want to disable IPv6 " +"autoconfiguration and DHCP and instead force static network configuration." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2746 +#, no-c-format +msgid "mirror/protocol (protocol)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2747 +#, 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:2760 +#, no-c-format +msgid "tasksel:tasksel/first (tasks)" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2761 +#, 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:2775 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2776 +#, 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:2789 +#, 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:2796 +#, no-c-format +msgid "" +"The syntax to use to set parameters for modules is: " +"<informalexample><screen>\n" +"<replaceable>module_name</replaceable>.<replaceable>parameter_name</" +"replaceable>=<replaceable>value</replaceable>\n" +"</screen></informalexample> If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:2806 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "" + +#. Tag: title +#: boot-installer.xml:2812 +#, no-c-format +msgid "Blacklisting kernel modules" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2813 +#, no-c-format +msgid "" +"Sometimes it may be necessary to blacklist a module to prevent it from being " +"loaded automatically by the kernel and udev. One reason could be that a " +"particular module causes problems with your hardware. The kernel also " +"sometimes lists two different drivers for the same device. This can cause " +"the device to not work correctly if the drivers conflict or if the wrong " +"driver is loaded first." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2822 +#, no-c-format +msgid "" +"You can blacklist a module using the following syntax: " +"<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. " +"This will cause the module to be blacklisted in <filename>/etc/modprobe.d/" +"blacklist.local</filename> both during the installation and for the " +"installed system." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2830 +#, no-c-format +msgid "" +"Note that a module may still be loaded by the installation system itself. " +"You can prevent that from happening by running the installation in expert " +"mode and unselecting the module from the list of modules displayed during " +"the hardware detection phases." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2846 +#, no-c-format +msgid "Troubleshooting the Installation Process" +msgstr "" + +#. Tag: title +#: boot-installer.xml:2851 +#, no-c-format +msgid "Reliability of optical media" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2852 +#, no-c-format +msgid "" +"Sometimes, especially with older drives, the installer may fail to boot from " +"an optical disc. The installer may also — even after booting " +"successfully from such disc — fail to recognize the disc or return " +"errors while reading from it during the installation." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2859 +#, no-c-format +msgid "" +"There are 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:2865 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2870 +#, no-c-format +msgid "" +"If the disc does not boot, check that it was inserted correctly and that it " +"is not dirty." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2876 +#, no-c-format +msgid "" +"If the installer fails to recognize the disc, try just running the option " +"<menuchoice> <guimenuitem>Detect and mount installation media</guimenuitem> " +"</menuchoice> a second time. Some DMA related issues with very old CD-ROM " +"drives are known to be resolved in this way." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2886 +#, 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 CD-ROM and DVD." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2891 +#, no-c-format +msgid "" +"If you cannot get the installation working from optical disc, try one of the " +"other installation methods that are available." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2899 +#, no-c-format +msgid "Common issues" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2902 +#, 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:2919 +#, no-c-format +msgid "" +"Some very old CD-ROM drives do not work correctly if <quote>direct memory " +"access</quote> (DMA) is enabled for them." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2930 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2931 +#, no-c-format +msgid "If the optical disc fails to boot, try the suggestions listed below." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2936 +#, no-c-format +msgid "" +"Check that your BIOS/UEFI actually supports booting from optical disc (only " +"an issue for very old systems) and that booting from such media is enabled " +"in the BIOS/UEFI." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2943 +#, 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" +"$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>\n" +"a20391b12f7ff22ef705cee4059c6b92 <replaceable>debian-testing-i386-netinst." +"iso</replaceable>\n" +"</screen></informalexample> Next, check that the md5sum of the burned disc " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the disc." +msgstr "" + +#. Tag: screen +#: boot-installer.xml:2956 +#, no-c-format +msgid "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</" +"replaceable>` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2961 +#, no-c-format +msgid "" +"If, after the installer has been booted successfully, the disc is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one optical drive, try changing the disc to the other drive. If " +"that does not work or if the disc is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"&arch-kernel; 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:2973 +#, 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:2980 +#, no-c-format +msgid "" +"Check in the output of <command>dmesg</command> if your optical drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): <informalexample><screen>\n" +"ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33\n" +"ata1.00: configured for UDMA/33\n" +"scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 ANSI: " +"5\n" +"sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray\n" +"cdrom: Uniform CD-ROM driver Revision: 3.20\n" +"</screen></informalexample> If you don't see something like that, chances " +"are the controller your drive is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the controller, " +"you can try loading it manually using <command>modprobe</command>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2994 +#, no-c-format +msgid "" +"Check that there is a device node for your optical drive under <filename>/" +"dev/</filename>. In the example above, this would be <filename>/dev/sr0</" +"filename>. There should also be a <filename>/dev/cdrom</filename>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3002 +#, no-c-format +msgid "" +"Use the <command>mount</command> command to check if the optical disc is " +"already mounted; if not, try mounting it manually: " +"<informalexample><screen>\n" +"$ mount /dev/<replaceable>hdc</replaceable> /cdrom\n" +"</screen></informalexample> Check if there are any error messages after that " +"command." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3012 +#, no-c-format +msgid "" +"Check if DMA is currently enabled: <informalexample><screen>\n" +"$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>\n" +"$ grep using_dma settings\n" +"using_dma 1 0 1 rw\n" +"</screen></informalexample> A <quote>1</quote> in the first column after " +"<literal>using_dma</literal> means it is enabled. If it is, try disabling " +"it: <informalexample><screen>\n" +"$ echo -n \"using_dma:0\" >settings\n" +"</screen></informalexample> Make sure that you are in the directory for the " +"device that corresponds to your optical drive." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3027 +#, no-c-format +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the installation media using the option near the bottom of the " +"installer's main menu. This option can also be used as a general test if the " +"disc can be read reliably." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3041 +#, no-c-format +msgid "Boot Configuration" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3043 +#, 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:3052 +#, no-c-format +msgid "" +"In some cases, malfunctions can be caused by missing device firmware (see " +"<xref linkend=\"hardware-firmware\"/> and <xref linkend=\"loading-firmware\"/" +">)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3063 +#, no-c-format +msgid "" +"If software speech synthesis does not work, there is most probably an issue " +"with your sound board, usually because either the driver for it is not " +"included in the installer, or because it has unusual mixer level names which " +"are set to muted by default. You should thus submit a bug report which " +"includes the output of the following commands, run on the same machine from " +"a Linux system which is known to have sound working (e.g., a live CD)." +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:3074 +#, no-c-format +msgid "dmesg" +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:3076 +#, no-c-format +msgid "lspci" +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:3078 +#, no-c-format +msgid "lsmod" +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:3080 +#, no-c-format +msgid "amixer" +msgstr "" + +#. Tag: title +#: boot-installer.xml:3088 boot-installer.xml:3193 +#, no-c-format +msgid "Common &arch-title; Installation Problems" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3089 +#, 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:3134 +#, 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</" +"userinput> to disable the framebuffer console. Only a reduced set of " +"languages will be available during the installation due to limited console " +"features. See <xref linkend=\"boot-parms\"/> for details." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3148 +#, no-c-format +msgid "System Freeze During the PCMCIA Configuration Phase" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3149 +#, no-c-format +msgid "" +"Some very old 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:3159 +#, 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: para +#: boot-installer.xml:3194 +#, no-c-format +msgid "There are some common installation problems that are worth mentioning." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3200 +#, no-c-format +msgid "Misdirected video output" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3201 +#, 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" +"Remapping the kernel... done\n" +"Booting Linux...\n" +"</screen></informalexample> To work around this, you can either pull out one " +"of the video cards, or disable the one not used during the OpenProm boot " +"phase using a kernel parameter. For example, to disable an ATI card, you " +"should boot the installer with <userinput>video=atyfb:off</userinput>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3215 +#, 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:3226 +#, no-c-format +msgid "Failure to Boot or Install from CD-ROM" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3227 +#, 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:3233 +#, no-c-format +msgid "We recommend to install such systems by netbooting the installer." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3242 +#, no-c-format +msgid "Interpreting the Kernel Startup Messages" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3244 +#, 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 <phrase arch=\"linux-any\">(see <xref linkend=\"kernel-" +"baking\"/>)</phrase>." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3269 +#, no-c-format +msgid "Reporting Installation Problems" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3270 +#, 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 on a storage medium, 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:3281 +#, 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:3292 +#, no-c-format +msgid "Submitting Installation Reports" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3293 +#, 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:3300 +#, 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." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3306 +#, 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>apt " +"install installation-report reportbug</command>), configure " +"<classname>reportbug</classname> as explained in <xref linkend=\"mail-" +"outgoing\"/>, and run the command <command>reportbug installation-reports</" +"command>." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3316 +#, 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" +"Package: installation-reports\n" +"\n" +"Boot method: <How did you boot the installer? CD/DVD? USB stick? Network?" +">\n" +"Image version: <Full URL to image you downloaded is best>\n" +"Date: <Date and time of the install>\n" +"\n" +"Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" +"Processor:\n" +"Memory:\n" +"Partitions: <df -Tl will do; the raw partition table is preferred>\n" +"\n" +"Output of lspci -knn (or lspci -nn):\n" +"\n" +"Base System Installation Checklist:\n" +"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" +"\n" +"Initial boot: [ ]\n" +"Detect network card: [ ]\n" +"Configure network: [ ]\n" +"Detect media: [ ]\n" +"Load installer modules: [ ]\n" +"Detect hard drives: [ ]\n" +"Partition hard drives: [ ]\n" +"Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" +"Install boot loader: [ ]\n" +"Overall install: [ ]\n" +"\n" +"Comments/Problems:\n" +"\n" +"<Description of the install, in prose, and any thoughts, comments\n" +" and ideas you had during the initial install.>\n" +"</screen></informalexample> In the bug report, describe what the problem is, " +"including the last visible kernel messages in the event of a kernel hang. " +"Describe the steps that you did which brought the system into the problem " +"state." +msgstr "" diff --git a/po/kab/boot-new.po b/po/kab/boot-new.po new file mode 100644 index 000000000..89049c99c --- /dev/null +++ b/po/kab/boot-new.po @@ -0,0 +1,419 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-boot-new 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-04-02 09:22+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: boot-new.xml:5 +#, no-c-format +msgid "Booting Into Your New &debian; System" +msgstr "" + +#. Tag: title +#: boot-new.xml:7 +#, no-c-format +msgid "The Moment of Truth" +msgstr "" + +#. Tag: para +#: boot-new.xml:8 +#, no-c-format +msgid "" +"Your system's first boot on its own power is what electrical engineers call " +"the <quote>smoke test</quote>." +msgstr "" + +#. Tag: para +#: boot-new.xml:13 +#, no-c-format +msgid "" +"If you did a default installation, the first thing you should see when you " +"boot the system is the menu of the <classname>grub</classname> bootloader. " +"The first choices in the menu will be for your new &debian; system. If you " +"had any other operating systems on your computer (like Windows) that were " +"detected by the installation system, those will be listed lower down in the " +"menu." +msgstr "" + +#. Tag: para +#: boot-new.xml:23 +#, no-c-format +msgid "" +"If the system fails to start up correctly, don't panic. If the installation " +"was successful, chances are good that there is only a relatively minor " +"problem that is preventing the system from booting &debian;. In most cases " +"such problems can be fixed without having to repeat the installation. One " +"available option to fix boot problems is to use the installer's built-in " +"rescue mode (see <xref linkend=\"rescue\"/>)." +msgstr "" + +#. Tag: para +#: boot-new.xml:32 +#, no-c-format +msgid "" +"If you are new to &debian; and &arch-kernel;, you may need some help from " +"more experienced users. <phrase arch=\"x86\">For direct on-line help you can " +"try the IRC channels #debian or #debian-boot on the OFTC network. " +"Alternatively you can contact the <ulink url=\"&url-list-subscribe;\">debian-" +"user mailing list</ulink>.</phrase> <phrase arch=\"not-x86\">For less common " +"architectures like &arch-title;, your best option is to ask on the <ulink " +"url=\"&url-list-subscribe;\">debian-&arch-listname; mailing list</ulink>.</" +"phrase> You can also file an installation report as described in <xref " +"linkend=\"submit-bug\"/>. Please make sure that you describe your problem " +"clearly and include any messages that are displayed and may help others to " +"diagnose the issue." +msgstr "" + +#. Tag: para +#: boot-new.xml:48 +#, no-c-format +msgid "" +"If you had any other operating systems on your computer that were not " +"detected or not detected correctly, please file an installation report." +msgstr "" + +#. Tag: title +#: boot-new.xml:56 +#, no-c-format +msgid "OldWorld PowerMacs" +msgstr "" + +#. Tag: para +#: boot-new.xml:57 +#, no-c-format +msgid "" +"If the machine fails to boot after completing the installation, and stops " +"with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</" +"userinput> followed by &enterkey;. (The default boot configuration in " +"<filename>quik.conf</filename> is labeled Linux). The labels defined in " +"<filename>quik.conf</filename> will be displayed if you press the " +"<keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also " +"try booting back into the installer, and editing the <filename>/target/etc/" +"quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard " +"Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are " +"available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>." +msgstr "" + +#. Tag: para +#: boot-new.xml:71 +#, no-c-format +msgid "" +"To boot back into MacOS without resetting the nvram, type <userinput>bye</" +"userinput> at the OpenFirmware prompt (assuming MacOS has not been removed " +"from the machine). To obtain an OpenFirmware prompt, hold down the " +"<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</" +"keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. " +"If you need to reset the OpenFirmware nvram changes to the MacOS default in " +"order to boot back to MacOS, hold down the <keycombo> <keycap>command</" +"keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </" +"keycombo> keys while cold booting the machine." +msgstr "" + +#. Tag: para +#: boot-new.xml:84 +#, no-c-format +msgid "" +"If you use <command>BootX</command> to boot into the installed system, just " +"select your desired kernel in the <filename>Linux Kernels</filename> folder, " +"un-choose the ramdisk option, and add a root device corresponding to your " +"installation; e.g. <userinput>/dev/sda8</userinput>." +msgstr "" + +#. Tag: title +#: boot-new.xml:96 +#, no-c-format +msgid "NewWorld PowerMacs" +msgstr "" + +#. Tag: para +#: boot-new.xml:97 +#, no-c-format +msgid "" +"On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key " +"and get a graphical screen with a button for each bootable OS, &debian-gnu; " +"will be a button with a small penguin icon." +msgstr "" + +#. Tag: para +#: boot-new.xml:104 +#, no-c-format +msgid "" +"If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-" +"device</envar> variable you should reset OpenFirmware to its default " +"configuration. To do this hold down the <keycombo> <keycap>command</keycap> " +"<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> " +"keys while cold booting the machine." +msgstr "" + +#. Tag: para +#: boot-new.xml:112 +#, no-c-format +msgid "" +"The labels defined in <filename>yaboot.conf</filename> will be displayed if " +"you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt." +msgstr "" + +#. Tag: para +#: boot-new.xml:118 +#, no-c-format +msgid "" +"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-" +"gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap " +"partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an " +"IDE disk this may not work and you will have to enter OpenFirmware and set " +"the <envar>boot-device</envar> variable, <command>ybin</command> normally " +"does this automatically." +msgstr "" + +#. Tag: para +#: boot-new.xml:127 +#, no-c-format +msgid "" +"After you boot &debian-gnu; for the first time you can add any additional " +"options you desire (such as dual boot options) to <filename>/etc/yaboot." +"conf</filename> and run <command>ybin</command> to update your boot " +"partition with the changed configuration. Please read the <ulink url=\"&url-" +"powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information." +msgstr "" + +#. Tag: title +#: boot-new.xml:145 +#, no-c-format +msgid "Mounting encrypted volumes" +msgstr "" + +#. Tag: para +#: boot-new.xml:147 +#, no-c-format +msgid "" +"If you created encrypted volumes during the installation and assigned them " +"mount points, you will be asked to enter the passphrase for each of these " +"volumes during the boot." +msgstr "" + +#. Tag: para +#: boot-new.xml:155 +#, no-c-format +msgid "" +"For partitions encrypted using dm-crypt you will be shown the following " +"prompt during the boot: <informalexample><screen>\n" +"Starting early crypto disks... <replaceable>part</" +"replaceable>_crypt(starting)\n" +"Enter LUKS passphrase:\n" +"</screen></informalexample> In the first line of the prompt, " +"<replaceable>part</replaceable> is the name of the underlying partition, e." +"g. sda2 or md0. You are now probably wondering <emphasis>for which volume</" +"emphasis> you are actually entering the passphrase. Does it relate to your " +"<filename>/home</filename>? Or to <filename>/var</filename>? Of course, if " +"you have just one encrypted volume, this is easy and you can just enter the " +"passphrase you used when setting up this volume. If you set up more than one " +"encrypted volume during the installation, the notes you wrote down as the " +"last step in <xref linkend=\"partman-crypto\"/> come in handy. If you did " +"not make a note of the mapping between <filename><replaceable>part</" +"replaceable>_crypt</filename> and the mount points before, you can still " +"find it in <filename>/etc/crypttab</filename> and <filename>/etc/fstab</" +"filename> of your new system." +msgstr "" + +#. Tag: para +#: boot-new.xml:178 +#, no-c-format +msgid "" +"The prompt may look somewhat different when an encrypted root file system is " +"mounted. This depends on which initramfs generator was used to generate the " +"initrd used to boot the system. The example below is for an initrd generated " +"using <classname>initramfs-tools</classname>:" +msgstr "" + +#. Tag: screen +#: boot-new.xml:185 +#, no-c-format +msgid "" +"Begin: Mounting <emphasis>root file system</emphasis>... ...\n" +"Begin: Running /scripts/local-top ...\n" +"Enter LUKS passphrase:" +msgstr "" + +#. Tag: para +#: boot-new.xml:187 +#, no-c-format +msgid "" +"No characters (even asterisks) will be shown while entering the passphrase. " +"If you enter the wrong passphrase, you have two more tries to correct it. " +"After the third try the boot process will skip this volume and continue to " +"mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting" +"\"/> for further information." +msgstr "" + +#. Tag: para +#: boot-new.xml:195 +#, no-c-format +msgid "After entering all passphrases the boot should continue as usual." +msgstr "" + +#. Tag: title +#: boot-new.xml:202 +#, no-c-format +msgid "Troubleshooting" +msgstr "" + +#. Tag: para +#: boot-new.xml:204 +#, no-c-format +msgid "" +"If some of the encrypted volumes could not be mounted because a wrong " +"passphrase was entered, you will have to mount them manually after the boot. " +"There are several cases." +msgstr "" + +#. Tag: para +#: boot-new.xml:213 +#, no-c-format +msgid "" +"The first case concerns the root partition. When it is not mounted " +"correctly, the boot process will halt and you will have to reboot the " +"computer to try again." +msgstr "" + +#. Tag: para +#: boot-new.xml:220 +#, no-c-format +msgid "" +"The easiest case is for encrypted volumes holding data like <filename>/home</" +"filename> or <filename>/srv</filename>. You can simply mount them manually " +"after the boot." +msgstr "" + +#. Tag: para +#: boot-new.xml:226 +#, no-c-format +msgid "" +"However for dm-crypt this is a bit tricky. First you need to register the " +"volumes with <application>device mapper</application> by running: " +"<informalexample><screen>\n" +"<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n" +"</screen></informalexample> This will scan all volumes mentioned in " +"<filename>/etc/crypttab</filename> and will create appropriate devices under " +"the <filename>/dev</filename> directory after entering the correct " +"passphrases. (Already registered volumes will be skipped, so you can repeat " +"this command several times without worrying.) After successful registration " +"you can simply mount the volumes the usual way:" +msgstr "" + +#. Tag: screen +#: boot-new.xml:241 +#, no-c-format +msgid "" +"<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></" +"userinput>" +msgstr "" + +#. Tag: para +#: boot-new.xml:244 +#, no-c-format +msgid "" +"If any volume holding noncritical system files could not be mounted " +"(<filename>/usr</filename> or <filename>/var</filename>), the system should " +"still boot and you should be able to mount the volumes manually like in the " +"previous case. However, you will also need to (re)start any services usually " +"running in your default runlevel because it is very likely that they were " +"not started. The easiest way is to just reboot the computer." +msgstr "" + +#. Tag: title +#: boot-new.xml:262 +#, no-c-format +msgid "Log In" +msgstr "" + +#. Tag: para +#: boot-new.xml:264 +#, no-c-format +msgid "" +"Once your system boots, you'll be presented with the login prompt. Log in " +"using the personal login and password you selected during the installation " +"process. Your system is now ready for use." +msgstr "" + +#. Tag: para +#: boot-new.xml:270 +#, no-c-format +msgid "" +"If you are a new user, you may want to explore the documentation which is " +"already installed on your system as you start to use it. There are currently " +"several documentation systems, work is proceeding on integrating the " +"different types of documentation. Here are a few starting points." +msgstr "" + +#. Tag: para +#: boot-new.xml:278 +#, no-c-format +msgid "" +"Documentation accompanying programs you have installed can be found in " +"<filename>/usr/share/doc/</filename>, under a subdirectory named after the " +"program (or, more precise, the &debian; package that contains the program). " +"However, more extensive documentation is often packaged separately in " +"special documentation packages that are mostly not installed by default. For " +"example, documentation about the package management tool <command>apt</" +"command> can be found in the packages <classname>apt-doc</classname> or " +"<classname>apt-howto</classname>." +msgstr "" + +#. Tag: para +#: boot-new.xml:289 +#, no-c-format +msgid "" +"In addition, there are some special folders within the <filename>/usr/share/" +"doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</" +"emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</" +"filename>. After installing <classname>dhelp</classname>, you will find a " +"browsable index of documentation in <filename>/usr/share/doc/HTML/index." +"html</filename>." +msgstr "" + +#. Tag: para +#: boot-new.xml:298 +#, no-c-format +msgid "" +"One easy way to view these documents using a text based browser is to enter " +"the following commands: <informalexample><screen>\n" +"$ cd /usr/share/doc/\n" +"$ w3m .\n" +"</screen></informalexample> The dot after the <command>w3m</command> command " +"tells it to show the contents of the current directory." +msgstr "" + +#. Tag: para +#: boot-new.xml:308 +#, no-c-format +msgid "" +"If you have a graphical desktop environment installed, you can also use its " +"web browser. Start the web browser from the application menu and enter " +"<userinput>/usr/share/doc/</userinput> in the address bar." +msgstr "" + +#. Tag: para +#: boot-new.xml:314 +#, no-c-format +msgid "" +"You can also type <userinput>info <replaceable>command</replaceable></" +"userinput> or <userinput>man <replaceable>command</replaceable></userinput> " +"to see documentation on most commands available at the command prompt. " +"Typing <userinput>help</userinput> will display help on shell commands. And " +"typing a command followed by <userinput>--help</userinput> will usually " +"display a short summary of the command's usage. If a command's results " +"scroll past the top of the screen, type <userinput>| more</userinput> " +"after the command to cause the results to pause before scrolling past the " +"top of the screen. To see a list of all commands available which begin with " +"a certain letter, type the letter and then two tabs." +msgstr "" diff --git a/po/kab/gpl.po b/po/kab/gpl.po new file mode 100644 index 000000000..5b4f3b500 --- /dev/null +++ b/po/kab/gpl.po @@ -0,0 +1,668 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-gpl 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2019-08-07 21:24+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: gpl.xml:4 +#, no-c-format +msgid "GNU General Public License" +msgstr "" + +#. Tag: para +#: gpl.xml:6 +#, no-c-format +msgid "" +"[[This note, consisting of two paragraphs, should only be included in your " +"translation if you translate the GPL in this appendix. See build/lang-" +"options/README on how to enable this paragraph and for additional " +"information. Its condition is \"gpl-unofficial\".]] [[LEAVE THIS PARAGRAPH " +"IN ENGLISH! Only replace {language} with the English name of your language. " +"Do not change the link to the GPL!]] This is an unofficial translation of " +"the GNU General Public License into {language}. It was not published by the " +"Free Software Foundation, and does not legally state the distribution terms " +"for software that uses the GNU GPL — only the original <ulink url=" +"\"&url-gnu-copyleft;\">English text</ulink> of the GNU GPL does that. " +"However, we hope that this translation will help {language} speakers to " +"better understand the GNU GPL." +msgstr "" + +#. Tag: para +#: gpl.xml:22 +#, no-c-format +msgid "" +"[[See build/lang-options/README on how to enable this paragraph and for " +"additional information. Its condition is \"gpl-unofficial\".]] [[THIS " +"PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English name of " +"your language before translating. Do not change the link to the GPL!]] This " +"is an unofficial translation of the GNU General Public License into " +"{language}. It was not published by the Free Software Foundation, and does " +"not legally state the distribution terms for software that uses the GNU GPL " +"— only the original <ulink url=\"&url-gnu-copyleft;\">English text</" +"ulink> of the GNU GPL does that. However, we hope that this translation will " +"help {language} speakers to better understand the GNU GPL." +msgstr "" + +#. Tag: para +#: gpl.xml:37 +#, no-c-format +msgid "Version 2, June 1991" +msgstr "" + +#. Tag: screen +#: gpl.xml:41 +#, no-c-format +msgid "" +"Copyright (C) 1989, 1991 Free Software Foundation, Inc.\n" +"51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n" +"\n" +"Everyone is permitted to copy and distribute verbatim copies\n" +"of this license document, but changing it is not allowed." +msgstr "" + +#. Tag: title +#: gpl.xml:45 +#, no-c-format +msgid "Preamble" +msgstr "" + +#. Tag: para +#: gpl.xml:46 +#, no-c-format +msgid "" +"The licenses for most software are designed to take away your freedom to " +"share and change it. By contrast, the gnu General Public License is intended " +"to guarantee your freedom to share and change free software — to make " +"sure the software is free for all its users. This General Public License " +"applies to most of the Free Software Foundation's software and to any other " +"program whose authors commit to using it. (Some other Free Software " +"Foundation software is covered by the gnu Library General Public License " +"instead.) You can apply it to your programs, too." +msgstr "" + +#. Tag: para +#: gpl.xml:58 +#, no-c-format +msgid "" +"When we speak of free software, we are referring to freedom, not price. Our " +"General Public Licenses are designed to make sure that you have the freedom " +"to distribute copies of free software (and charge for this service if you " +"wish), that you receive source code or can get it if you want it, that you " +"can change the software or use pieces of it in new free programs; and that " +"you know you can do these things." +msgstr "" + +#. Tag: para +#: gpl.xml:68 +#, no-c-format +msgid "" +"To protect your rights, we need to make restrictions that forbid anyone to " +"deny you these rights or to ask you to surrender the rights. These " +"restrictions translate to certain responsibilities for you if you distribute " +"copies of the software, or if you modify it." +msgstr "" + +#. Tag: para +#: gpl.xml:75 +#, no-c-format +msgid "" +"For example, if you distribute copies of such a program, whether gratis or " +"for a fee, you must give the recipients all the rights that you have. You " +"must make sure that they, too, receive or can get the source code. And you " +"must show them these terms so they know their rights." +msgstr "" + +#. Tag: para +#: gpl.xml:83 +#, no-c-format +msgid "" +"We protect your rights with two steps: (1) copyright the software, and (2) " +"offer you this license which gives you legal permission to copy, distribute " +"and/or modify the software." +msgstr "" + +#. Tag: para +#: gpl.xml:89 +#, no-c-format +msgid "" +"Also, for each author's protection and ours, we want to make certain that " +"everyone understands that there is no warranty for this free software. If " +"the software is modified by someone else and passed on, we want its " +"recipients to know that what they have is not the original, so that any " +"problems introduced by others will not reflect on the original authors' " +"reputations." +msgstr "" + +#. Tag: para +#: gpl.xml:98 +#, no-c-format +msgid "" +"Finally, any free program is threatened constantly by software patents. We " +"wish to avoid the danger that redistributors of a free program will " +"individually obtain patent licenses, in effect making the program " +"proprietary. To prevent this, we have made it clear that any patent must be " +"licensed for everyone's free use or not licensed at all." +msgstr "" + +#. Tag: para +#: gpl.xml:107 +#, no-c-format +msgid "" +"The precise terms and conditions for copying, distribution and modification " +"follow." +msgstr "" + +#. Tag: title +#: gpl.xml:115 +#, no-c-format +msgid "GNU GENERAL PUBLIC LICENSE" +msgstr "" + +#. Tag: emphasis +#: gpl.xml:118 +#, no-c-format +msgid "TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION" +msgstr "" + +#. Tag: para +#: gpl.xml:121 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">0.</emphasis> This License applies to any program or " +"other work which contains a notice placed by the copyright holder saying it " +"may be distributed under the terms of this General Public License. The " +"<quote>Program</quote>, below, refers to any such program or work, and a " +"<quote>work based on the Program</quote> means either the Program or any " +"derivative work under copyright law: that is to say, a work containing the " +"Program or a portion of it, either verbatim or with modifications and/or " +"translated into another language. (Hereinafter, translation is included " +"without limitation in the term <quote>modification</quote>.) Each licensee " +"is addressed as <quote>you</quote>." +msgstr "" + +#. Tag: para +#: gpl.xml:134 +#, no-c-format +msgid "" +"Activities other than copying, distribution and modification are not covered " +"by this License; they are outside its scope. The act of running the Program " +"is not restricted, and the output from the Program is covered only if its " +"contents constitute a work based on the Program (independent of having been " +"made by running the Program). Whether that is true depends on what the " +"Program does." +msgstr "" + +#. Tag: para +#: gpl.xml:143 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">1.</emphasis> You may copy and distribute verbatim " +"copies of the Program's source code as you receive it, in any medium, " +"provided that you conspicuously and appropriately publish on each copy an " +"appropriate copyright notice and disclaimer of warranty; keep intact all the " +"notices that refer to this License and to the absence of any warranty; and " +"give any other recipients of the Program a copy of this License along with " +"the Program." +msgstr "" + +#. Tag: para +#: gpl.xml:154 +#, no-c-format +msgid "" +"You may charge a fee for the physical act of transferring a copy, and you " +"may at your option offer warranty protection in exchange for a fee." +msgstr "" + +#. Tag: para +#: gpl.xml:160 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">2.</emphasis> You may modify your copy or copies of " +"the Program or any portion of it, thus forming a work based on the Program, " +"and copy and distribute such modifications or work under the terms of " +"Section 1 above, provided that you also meet all of these conditions:" +msgstr "" + +#. Tag: para +#: gpl.xml:169 +#, no-c-format +msgid "" +"You must cause the modified files to carry prominent notices stating that " +"you changed the files and the date of any change." +msgstr "" + +#. Tag: para +#: gpl.xml:175 +#, no-c-format +msgid "" +"You must cause any work that you distribute or publish, that in whole or in " +"part contains or is derived from the Program or any part thereof, to be " +"licensed as a whole at no charge to all third parties under the terms of " +"this License." +msgstr "" + +#. Tag: para +#: gpl.xml:183 +#, no-c-format +msgid "" +"If the modified program normally reads commands interactively when run, you " +"must cause it, when started running for such interactive use in the most " +"ordinary way, to print or display an announcement including an appropriate " +"copyright notice and a notice that there is no warranty (or else, saying " +"that you provide a warranty) and that users may redistribute the program " +"under these conditions, and telling the user how to view a copy of this " +"License. (Exception: if the Program itself is interactive but does not " +"normally print such an announcement, your work based on the Program is not " +"required to print an announcement.)" +msgstr "" + +#. Tag: para +#: gpl.xml:197 +#, no-c-format +msgid "" +"These requirements apply to the modified work as a whole. If identifiable " +"sections of that work are not derived from the Program, and can be " +"reasonably considered independent and separate works in themselves, then " +"this License, and its terms, do not apply to those sections when you " +"distribute them as separate works. But when you distribute the same sections " +"as part of a whole which is a work based on the Program, the distribution of " +"the whole must be on the terms of this License, whose permissions for other " +"licensees extend to the entire whole, and thus to each and every part " +"regardless of who wrote it." +msgstr "" + +#. Tag: para +#: gpl.xml:210 +#, no-c-format +msgid "" +"Thus, it is not the intent of this section to claim rights or contest your " +"rights to work written entirely by you; rather, the intent is to exercise " +"the right to control the distribution of derivative or collective works " +"based on the Program." +msgstr "" + +#. Tag: para +#: gpl.xml:217 +#, no-c-format +msgid "" +"In addition, mere aggregation of another work not based on the Program with " +"the Program (or with a work based on the Program) on a volume of a storage " +"or distribution medium does not bring the other work under the scope of this " +"License." +msgstr "" + +#. Tag: para +#: gpl.xml:224 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">3.</emphasis> You may copy and distribute the " +"Program (or a work based on it, under Section 2) in object code or " +"executable form under the terms of Sections 1 and 2 above provided that you " +"also do one of the following:" +msgstr "" + +#. Tag: para +#: gpl.xml:233 +#, no-c-format +msgid "" +"Accompany it with the complete corresponding machine-readable source code, " +"which must be distributed under the terms of Sections 1 and 2 above on a " +"medium customarily used for software interchange; or," +msgstr "" + +#. Tag: para +#: gpl.xml:241 +#, no-c-format +msgid "" +"Accompany it with a written offer, valid for at least three years, to give " +"any third party, for a charge no more than your cost of physically " +"performing source distribution, a complete machine-readable copy of the " +"corresponding source code, to be distributed under the terms of Sections 1 " +"and 2 above on a medium customarily used for software interchange; or," +msgstr "" + +#. Tag: para +#: gpl.xml:251 +#, no-c-format +msgid "" +"Accompany it with the information you received as to the offer to distribute " +"corresponding source code. (This alternative is allowed only for " +"noncommercial distribution and only if you received the program in object " +"code or executable form with such an offer, in accord with Subsection b " +"above.)" +msgstr "" + +#. Tag: para +#: gpl.xml:260 +#, no-c-format +msgid "" +"The source code for a work means the preferred form of the work for making " +"modifications to it. For an executable work, complete source code means all " +"the source code for all modules it contains, plus any associated interface " +"definition files, plus the scripts used to control compilation and " +"installation of the executable. However, as a special exception, the source " +"code distributed need not include anything that is normally distributed (in " +"either source or binary form) with the major components (compiler, kernel, " +"and so on) of the operating system on which the executable runs, unless that " +"component itself accompanies the executable." +msgstr "" + +#. Tag: para +#: gpl.xml:273 +#, no-c-format +msgid "" +"If distribution of executable or object code is made by offering access to " +"copy from a designated place, then offering equivalent access to copy the " +"source code from the same place counts as distribution of the source code, " +"even though third parties are not compelled to copy the source along with " +"the object code." +msgstr "" + +#. Tag: para +#: gpl.xml:281 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">4.</emphasis> You may not copy, modify, sublicense, " +"or distribute the Program except as expressly provided under this License. " +"Any attempt otherwise to copy, modify, sublicense or distribute the Program " +"is void, and will automatically terminate your rights under this License. " +"However, parties who have received copies, or rights, from you under this " +"License will not have their licenses terminated so long as such parties " +"remain in full compliance." +msgstr "" + +#. Tag: para +#: gpl.xml:292 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">5.</emphasis> You are not required to accept this " +"License, since you have not signed it. However, nothing else grants you " +"permission to modify or distribute the Program or its derivative works. " +"These actions are prohibited by law if you do not accept this License. " +"Therefore, by modifying or distributing the Program (or any work based on " +"the Program), you indicate your acceptance of this License to do so, and all " +"its terms and conditions for copying, distributing or modifying the Program " +"or works based on it." +msgstr "" + +#. Tag: para +#: gpl.xml:304 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">6.</emphasis> Each time you redistribute the Program " +"(or any work based on the Program), the recipient automatically receives a " +"license from the original licensor to copy, distribute or modify the Program " +"subject to these terms and conditions. You may not impose any further " +"restrictions on the recipients' exercise of the rights granted herein. You " +"are not responsible for enforcing compliance by third parties to this " +"License." +msgstr "" + +#. Tag: para +#: gpl.xml:315 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">7.</emphasis> If, as a consequence of a court " +"judgment or allegation of patent infringement or for any other reason (not " +"limited to patent issues), conditions are imposed on you (whether by court " +"order, agreement or otherwise) that contradict the conditions of this " +"License, they do not excuse you from the conditions of this License. If you " +"cannot distribute so as to satisfy simultaneously your obligations under " +"this License and any other pertinent obligations, then as a consequence you " +"may not distribute the Program at all. For example, if a patent license " +"would not permit royalty-free redistribution of the Program by all those who " +"receive copies directly or indirectly through you, then the only way you " +"could satisfy both it and this License would be to refrain entirely from " +"distribution of the Program." +msgstr "" + +#. Tag: para +#: gpl.xml:332 +#, no-c-format +msgid "" +"If any portion of this section is held invalid or unenforceable under any " +"particular circumstance, the balance of the section is intended to apply and " +"the section as a whole is intended to apply in other circumstances." +msgstr "" + +#. Tag: para +#: gpl.xml:339 +#, no-c-format +msgid "" +"It is not the purpose of this section to induce you to infringe any patents " +"or other property right claims or to contest validity of any such claims; " +"this section has the sole purpose of protecting the integrity of the free " +"software distribution system, which is implemented by public license " +"practices. Many people have made generous contributions to the wide range of " +"software distributed through that system in reliance on consistent " +"application of that system; it is up to the author/donor to decide if he or " +"she is willing to distribute software through any other system and a " +"licensee cannot impose that choice." +msgstr "" + +#. Tag: para +#: gpl.xml:352 +#, no-c-format +msgid "" +"This section is intended to make thoroughly clear what is believed to be a " +"consequence of the rest of this License." +msgstr "" + +#. Tag: para +#: gpl.xml:357 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">8.</emphasis> If the distribution and/or use of the " +"Program is restricted in certain countries either by patents or by " +"copyrighted interfaces, the original copyright holder who places the Program " +"under this License may add an explicit geographical distribution limitation " +"excluding those countries, so that distribution is permitted only in or " +"among countries not thus excluded. In such case, this License incorporates " +"the limitation as if written in the body of this License." +msgstr "" + +#. Tag: para +#: gpl.xml:368 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">9.</emphasis> The Free Software Foundation may " +"publish revised and/or new versions of the General Public License from time " +"to time. Such new versions will be similar in spirit to the present version, " +"but may differ in detail to address new problems or concerns. Each version " +"is given a distinguishing version number. If the Program specifies a version " +"number of this License which applies to it and <quote>any later version</" +"quote>, you have the option of following the terms and conditions either of " +"that version or of any later version published by the Free Software " +"Foundation. If the Program does not specify a version number of this " +"License, you may choose any version ever published by the Free Software " +"Foundation." +msgstr "" + +#. Tag: para +#: gpl.xml:383 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">10.</emphasis> If you wish to incorporate parts of " +"the Program into other free programs whose distribution conditions are " +"different, write to the author to ask for permission. For software which is " +"copyrighted by the Free Software Foundation, write to the Free Software " +"Foundation; we sometimes make exceptions for this. Our decision will be " +"guided by the two goals of preserving the free status of all derivatives of " +"our free software and of promoting the sharing and reuse of software " +"generally." +msgstr "" + +#. Tag: emphasis +#: gpl.xml:397 +#, no-c-format +msgid "NO WARRANTY" +msgstr "" + +#. Tag: para +#: gpl.xml:399 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">11.</emphasis> BECAUSE THE PROGRAM IS LICENSED FREE " +"OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY " +"APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT " +"HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM <quote>AS IS</quote> " +"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT " +"NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A " +"PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE " +"PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST " +"OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION." +msgstr "" + +#. Tag: para +#: gpl.xml:412 +#, no-c-format +msgid "" +"<emphasis role=\"bold\">12.</emphasis> IN NO EVENT UNLESS REQUIRED BY " +"APPLICABLE LAW OR AGREED TO IN WRITING WILL AND COPYRIGHT HOLDER, OR ANY " +"OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED " +"ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, " +"INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO " +"USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING " +"RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE " +"OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR " +"OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES." +msgstr "" + +#. Tag: emphasis +#: gpl.xml:428 +#, no-c-format +msgid "END OF TERMS AND CONDITIONS" +msgstr "" + +#. Tag: title +#: gpl.xml:433 +#, no-c-format +msgid "How to Apply These Terms to Your New Programs" +msgstr "" + +#. Tag: para +#: gpl.xml:434 +#, no-c-format +msgid "" +"If you develop a new program, and you want it to be of the greatest possible " +"use to the public, the best way to achieve this is to make it free software " +"which everyone can redistribute and change under these terms." +msgstr "" + +#. Tag: para +#: gpl.xml:441 +#, no-c-format +msgid "" +"To do so, attach the following notices to the program. It is safest to " +"attach them to the start of each source file to most effectively convey the " +"exclusion of warranty; and each file should have at least the " +"<quote>copyright</quote> line and a pointer to where the full notice is " +"found." +msgstr "" + +#. Tag: screen +#: gpl.xml:448 +#, no-c-format +msgid "" +"<replaceable>one line to give the program's name and a brief idea of what it " +"does.</replaceable>\n" +"Copyright (C) <replaceable>year name of author</replaceable>\n" +"\n" +"This program is free software; you can redistribute it and/or\n" +"modify it under the terms of the GNU General Public License\n" +"as published by the Free Software Foundation; either version 2\n" +"of the License, or (at your option) any later version.\n" +"\n" +"This program is distributed in the hope that it will be useful,\n" +"but WITHOUT ANY WARRANTY; without even the implied warranty of\n" +"MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the\n" +"GNU General Public License for more details.\n" +"\n" +"You should have received a copy of the GNU General Public License\n" +"along with this program; if not, write to the Free Software\n" +"Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, " +"USA." +msgstr "" + +#. Tag: para +#: gpl.xml:450 +#, no-c-format +msgid "" +"Also add information on how to contact you by electronic and paper mail." +msgstr "" + +#. Tag: para +#: gpl.xml:455 +#, no-c-format +msgid "" +"If the program is interactive, make it output a short notice like this when " +"it starts in an interactive mode:" +msgstr "" + +#. Tag: screen +#: gpl.xml:460 +#, no-c-format +msgid "" +"Gnomovision version 69, Copyright (C) <replaceable>year name of author</" +"replaceable>\n" +"Gnomovision comes with absolutely no warranty; for details\n" +"type <userinput>show w</userinput>. This is free software, and you are " +"welcome\n" +"to redistribute it under certain conditions; type <userinput>show c</" +"userinput>\n" +"for details." +msgstr "" + +#. Tag: para +#: gpl.xml:462 +#, no-c-format +msgid "" +"The hypothetical commands <quote>show w</quote> and <quote>show c</quote> " +"should show the appropriate parts of the General Public License. Of course, " +"the commands you use may be called something other than <quote>show w</" +"quote> and <quote>show c</quote>; they could even be mouse-clicks or menu " +"items — whatever suits your program." +msgstr "" + +#. Tag: para +#: gpl.xml:470 +#, no-c-format +msgid "" +"You should also get your employer (if you work as a programmer) or your " +"school, if any, to sign a <quote>copyright disclaimer</quote> for the " +"program, if necessary. Here is a sample; alter the names:" +msgstr "" + +#. Tag: screen +#: gpl.xml:476 +#, no-c-format +msgid "" +"Yoyodyne, Inc., hereby disclaims all copyright interest in the\n" +"program <userinput>Gnomovision</userinput> (which makes passes at compilers) " +"written\n" +"by James Hacker.\n" +"\n" +"<replaceable>signature of Ty Coon</replaceable>, 1 April 1989\n" +"Ty Coon, President of Vice" +msgstr "" + +#. Tag: para +#: gpl.xml:478 +#, no-c-format +msgid "" +"This General Public License does not permit incorporating your program into " +"proprietary programs. If your program is a subroutine library, you may " +"consider it more useful to permit linking proprietary applications with the " +"library. If this is what you want to do, use the GNU Lesser General Public " +"License instead of this License." +msgstr "" diff --git a/po/kab/hardware.po b/po/kab/hardware.po new file mode 100644 index 000000000..feda547f7 --- /dev/null +++ b/po/kab/hardware.po @@ -0,0 +1,2856 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-hardware 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-08-23 23: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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: hardware.xml:5 +#, no-c-format +msgid "System Requirements" +msgstr "" + +#. Tag: para +#: hardware.xml:7 +#, no-c-format +msgid "" +"This section contains information about what hardware you need to get " +"started with &debian;. You will also find links to further information about " +"hardware supported by GNU and &arch-kernel;." +msgstr "" + +#. Tag: title +#: hardware.xml:20 +#, no-c-format +msgid "Supported Hardware" +msgstr "" + +#. Tag: para +#: hardware.xml:21 +#, no-c-format +msgid "" +"&debian; does not impose hardware requirements beyond the requirements of " +"the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any " +"architecture or platform to which the Linux or kFreeBSD kernel, libc, " +"<command>gcc</command>, etc. have been ported, and for which a &debian; port " +"exists, can run &debian;. Please refer to the Ports pages at <ulink url=" +"\"&url-ports;\"></ulink> for more details on &arch-title; architecture " +"systems which have been tested with &debian-gnu;." +msgstr "" + +#. Tag: para +#: hardware.xml:32 +#, no-c-format +msgid "" +"Rather than attempting to describe all the different hardware configurations " +"which are supported for &arch-title;, this section contains general " +"information and pointers to where additional information can be found." +msgstr "" + +#. Tag: title +#: hardware.xml:41 +#, no-c-format +msgid "Supported Architectures" +msgstr "" + +#. Tag: para +#: hardware.xml:42 +#, no-c-format +msgid "" +"&debian; GNU/Linux &release; supports ten major architectures and several " +"variations of each architecture known as <quote>flavors</quote>." +msgstr "" + +#. Tag: entry +#: hardware.xml:53 +#, no-c-format +msgid "Architecture" +msgstr "" + +#. Tag: entry +#: hardware.xml:53 +#, no-c-format +msgid "&debian; Designation" +msgstr "" + +#. Tag: entry +#: hardware.xml:54 +#, no-c-format +msgid "Subarchitecture" +msgstr "" + +#. Tag: entry +#: hardware.xml:54 +#, no-c-format +msgid "Flavor" +msgstr "" + +#. Tag: entry +#: hardware.xml:60 +#, no-c-format +msgid "AMD64 & Intel 64" +msgstr "" + +#. Tag: entry +#: hardware.xml:61 +#, no-c-format +msgid "amd64" +msgstr "" + +#. Tag: entry +#: hardware.xml:67 +#, no-c-format +msgid "Intel x86-based" +msgstr "" + +#. Tag: entry +#: hardware.xml:68 +#, no-c-format +msgid "i386" +msgstr "" + +#. Tag: entry +#: hardware.xml:69 +#, no-c-format +msgid "default x86 machines" +msgstr "" + +#. Tag: entry +#: hardware.xml:70 +#, no-c-format +msgid "default" +msgstr "" + +#. Tag: entry +#: hardware.xml:72 +#, no-c-format +msgid "Xen PV domains only" +msgstr "" + +#. Tag: entry +#: hardware.xml:73 +#, no-c-format +msgid "<entry>xen</entry>" +msgstr "" + +#. Tag: entry +#: hardware.xml:77 +#, no-c-format +msgid "<entry>ARM</entry>" +msgstr "" + +#. Tag: entry +#: hardware.xml:78 +#, no-c-format +msgid "armel" +msgstr "" + +#. Tag: entry +#: hardware.xml:79 +#, no-c-format +msgid "Marvell Kirkwood and Orion" +msgstr "" + +#. Tag: entry +#: hardware.xml:80 +#, no-c-format +msgid "marvell" +msgstr "" + +#. Tag: entry +#: hardware.xml:84 +#, no-c-format +msgid "ARM with hardware FPU" +msgstr "" + +#. Tag: entry +#: hardware.xml:85 +#, no-c-format +msgid "armhf" +msgstr "" + +#. Tag: entry +#: hardware.xml:86 +#, no-c-format +msgid "multiplatform" +msgstr "" + +#. Tag: entry +#: hardware.xml:87 +#, no-c-format +msgid "armmp" +msgstr "" + +#. Tag: entry +#: hardware.xml:91 +#, no-c-format +msgid "64bit ARM" +msgstr "" + +#. Tag: entry +#: hardware.xml:92 +#, no-c-format +msgid "arm64" +msgstr "" + +#. Tag: entry +#: hardware.xml:98 +#, no-c-format +msgid "32bit MIPS (big-endian)" +msgstr "" + +#. Tag: entry +#: hardware.xml:99 +#, no-c-format +msgid "mips" +msgstr "" + +#. Tag: entry +#: hardware.xml:100 hardware.xml:110 hardware.xml:123 +#, no-c-format +msgid "<entry>MIPS Malta</entry>" +msgstr "" + +#. Tag: entry +#: hardware.xml:101 hardware.xml:124 +#, no-c-format +msgid "4kc-malta" +msgstr "" + +#. Tag: entry +#: hardware.xml:103 hardware.xml:113 hardware.xml:126 +#, no-c-format +msgid "<entry>Cavium Octeon</entry>" +msgstr "" + +#. Tag: entry +#: hardware.xml:104 hardware.xml:114 hardware.xml:127 +#, no-c-format +msgid "octeon" +msgstr "" + +#. Tag: entry +#: hardware.xml:108 +#, no-c-format +msgid "64bit MIPS (little-endian)" +msgstr "" + +#. Tag: entry +#: hardware.xml:109 +#, no-c-format +msgid "mips64el" +msgstr "" + +#. Tag: entry +#: hardware.xml:111 +#, no-c-format +msgid "5kc-malta" +msgstr "" + +#. Tag: entry +#: hardware.xml:116 hardware.xml:129 +#, no-c-format +msgid "<entry>Loongson 3</entry>" +msgstr "" + +#. Tag: entry +#: hardware.xml:117 hardware.xml:130 +#, no-c-format +msgid "loongson-3" +msgstr "" + +#. Tag: entry +#: hardware.xml:121 +#, no-c-format +msgid "32bit MIPS (little-endian)" +msgstr "" + +#. Tag: entry +#: hardware.xml:122 +#, no-c-format +msgid "mipsel" +msgstr "" + +#. Tag: entry +#: hardware.xml:148 +#, no-c-format +msgid "Power Systems" +msgstr "" + +#. Tag: entry +#: hardware.xml:149 +#, no-c-format +msgid "ppc64el" +msgstr "" + +#. Tag: entry +#: hardware.xml:150 +#, no-c-format +msgid "IBM POWER8 or newer machines" +msgstr "" + +#. Tag: entry +#: hardware.xml:175 +#, no-c-format +msgid "64bit IBM S/390" +msgstr "" + +#. Tag: entry +#: hardware.xml:176 +#, no-c-format +msgid "s390x" +msgstr "" + +#. Tag: entry +#: hardware.xml:177 +#, no-c-format +msgid "IPL from VM-reader and DASD" +msgstr "" + +#. Tag: entry +#: hardware.xml:178 +#, no-c-format +msgid "generic" +msgstr "" + +#. Tag: para +#: hardware.xml:185 +#, no-c-format +msgid "" +"This document covers installation for the <emphasis>&arch-title;</emphasis> " +"architecture using the <emphasis>&arch-kernel;</emphasis> kernel. If you are " +"looking for information on any of the other &debian;-supported architectures " +"take a look at the <ulink url=\"http://www.debian.org/ports/\">&debian;-" +"Ports</ulink> pages." +msgstr "" + +#. Tag: para +#: hardware.xml:195 +#, no-c-format +msgid "" +"This is the first official release of &debian-gnu; for the &arch-title; " +"architecture. We feel that it has proven itself sufficiently to be released. " +"However, because it has not had the exposure (and hence testing by users) " +"that some other architectures have had, you may encounter a few bugs. Use " +"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any " +"problems; make sure to mention the fact that the bug is on the &arch-title; " +"platform using the <emphasis>&arch-kernel;</emphasis> kernel. It can be " +"necessary to use the <ulink url=\"&url-list-subscribe;\">debian-&arch-" +"listname; mailing list</ulink> as well." +msgstr "" + +#. Tag: title +#: hardware.xml:217 +#, no-c-format +msgid "CPU Support" +msgstr "" + +#. Tag: para +#: hardware.xml:218 +#, no-c-format +msgid "Both AMD64 and Intel 64 processors are supported." +msgstr "" + +#. Tag: title +#: hardware.xml:242 +#, no-c-format +msgid "Three different ARM ports" +msgstr "" + +#. Tag: para +#: hardware.xml:244 +#, no-c-format +msgid "" +"The ARM architecture has evolved over time and modern ARM processors provide " +"features which are not available in older models. &debian; therefore " +"provides three ARM ports to give the best support for a very wide range of " +"different machines:" +msgstr "" + +#. Tag: para +#: hardware.xml:250 +#, no-c-format +msgid "" +"&debian;/armel targets older 32-bit ARM processors without support for a " +"hardware floating point unit (FPU)," +msgstr "" + +#. Tag: para +#: hardware.xml:254 +#, no-c-format +msgid "" +"&debian;/armhf works only on newer 32-bit ARM processors which implement at " +"least the ARMv7 architecture with version 3 of the ARM vector floating point " +"specification (VFPv3). It makes use of the extended features and performance " +"enhancements available on these models." +msgstr "" + +#. Tag: para +#: hardware.xml:261 +#, no-c-format +msgid "" +"&debian;/arm64 works on 64-bit ARM processors which implement at least the " +"ARMv8 architecture." +msgstr "" + +#. Tag: para +#: hardware.xml:268 +#, no-c-format +msgid "" +"Technically, all currently available ARM CPUs can be run in either endian " +"mode (big or little), but in practice the vast majority use little-endian " +"mode. All of &debian;/arm64, &debian;/armhf and &debian;/armel support only " +"little-endian systems." +msgstr "" + +#. Tag: title +#: hardware.xml:277 +#, no-c-format +msgid "Variations in ARM CPU designs and support complexity" +msgstr "" + +#. Tag: para +#: hardware.xml:279 +#, no-c-format +msgid "" +"ARM systems are much more heterogeneous than those based on the i386/amd64-" +"based PC architecture, so the support situation can be much more complicated." +msgstr "" + +#. Tag: para +#: hardware.xml:285 +#, no-c-format +msgid "" +"The ARM architecture is used mainly in so-called <quote>system-on-chip</" +"quote> (SoC) designs. These SoCs are designed by many different companies " +"with vastly varying hardware components even for the very basic " +"functionality required to bring the system up. System firmware interfaces " +"have been increasingly standardised over time, but especially on older " +"hardware firmware/boot interfaces vary a great deal, so on these systems the " +"Linux kernel has to take care of many system-specific low-level issues which " +"would be handled by the mainboard's BIOS/UEFI in the PC world." +msgstr "" + +#. Tag: para +#: hardware.xml:297 +#, no-c-format +msgid "" +"At the beginning of the ARM support in the Linux kernel, the hardware " +"variety resulted in the requirement of having a separate kernel for each ARM " +"system in contrast to the <quote>one-fits-all</quote> kernel for PC systems. " +"As this approach does not scale to a large number of different systems, work " +"was done to allow booting with a single ARM kernel that can run on different " +"ARM systems. Support for newer ARM systems is now implemented in a way that " +"allows the use of such a multiplatform kernel, but for several older systems " +"a separate specific kernel is still required. Because of this, the standard " +"&debian; distribution only supports installation on a selected number of " +"such older ARM systems, alongside the newer systems which are supported by " +"the ARM multiplatform kernels (called <quote>armmp</quote>) in &debian;/" +"armhf." +msgstr "" + +#. Tag: para +#: hardware.xml:313 +#, no-c-format +msgid "" +"The ARM architecture is used mainly in so-called <quote>system-on-chip</" +"quote> (SoC) designs. These SoCs are designed by many different companies, " +"often with vastly varying hardware components even for the very basic " +"functionality required to bring the system up. Older versions of the ARM " +"architecture have seen massive differences from one SoC to the next, but " +"ARMv8 (arm64) is much more standardised and so is easier for the Linux " +"kernel and other software to support." +msgstr "" + +#. Tag: para +#: hardware.xml:324 +#, no-c-format +msgid "" +"Server versions of ARMv8 hardware are typically configured using the Unified " +"Extensible Firmware Interface (UEFI) and Advanced Configuration and Power " +"Interface (ACPI) standards. These two provide common, device-independent " +"ways to boot and configure computer hardware. They are also common in the " +"x86 PC world." +msgstr "" + +#. Tag: title +#: hardware.xml:334 +#, no-c-format +msgid "Platforms supported by Debian/arm64" +msgstr "" + +#. Tag: para +#: hardware.xml:336 +#, no-c-format +msgid "" +"Arm64/AArch64/ARMv8 hardware became available quite late in the &debian; " +"&releasename-cap; release cycle so not many platforms had support merged in " +"the mainline kernel version by the time of this release; this is the main " +"requirement to have &d-i; working on them. The following platforms are known " +"to be supported by &debian;/arm64 in this release. There is only one kernel " +"image, which supports all the listed platforms." +msgstr "" + +#. Tag: term +#: hardware.xml:348 +#, no-c-format +msgid "Applied Micro (APM) Mustang/X-Gene" +msgstr "" + +#. Tag: para +#: hardware.xml:350 +#, no-c-format +msgid "" +"The APM Mustang was the first Linux-capable ARMv8 system available. It uses " +"the X-gene SoC, which has since also been used in other machines. It is an 8-" +"core CPU, with ethernet, USB and serial. A common form-factor looks just " +"like a desktop PC box, but many other versions are expected in the future. " +"Most of the hardware is supported in the mainline kernel, but at this point " +"USB support is lacking in the &releasename-cap; kernel." +msgstr "" + +#. Tag: term +#: hardware.xml:364 +#, no-c-format +msgid "ARM Juno Development Platform" +msgstr "" + +#. Tag: para +#: hardware.xml:366 +#, no-c-format +msgid "" +"Juno is a capable development board with a 6-core (2xA57, 4xA53) ARMv8-A " +"800Mhz CPU, Mali (T624) graphics, 8GB DDR3 RAM, Ethernet, USB, Serial. It " +"was designed for system bring-up and power testing so is neither small nor " +"cheap, but was one of the first boards available. All the on-board hardware " +"is supported in the mainline kernel and in &releasename-cap;." +msgstr "" + +#. Tag: para +#: hardware.xml:380 +#, no-c-format +msgid "" +"When using &d-i; on non-UEFI systems, you may have to manually make the " +"system bootable at the end of the installation, e.g. by running the required " +"commands in a shell started from within &d-i;. flash-kernel knows how to set " +"up an X-Gene system booting with U-Boot." +msgstr "" + +#. Tag: title +#: hardware.xml:388 +#, no-c-format +msgid "Other platforms" +msgstr "" + +#. Tag: para +#: hardware.xml:389 +#, no-c-format +msgid "" +"The multiplatform support in the arm64 Linux kernel may also allow running " +"&d-i; on arm64 systems not explicitly listed above. So long as the kernel " +"used by &d-i; has support for the target system's components, and a device-" +"tree file for that target is available, a new target system may work just " +"fine. In these cases, the installer can usually provide a working " +"installation, and so long as UEFI is in use, it should be able to make the " +"system bootable as well. If UEFI is not used you may also need to perform " +"some manual configuration steps to make the system bootable." +msgstr "" + +#. Tag: title +#: hardware.xml:405 +#, no-c-format +msgid "Platforms supported by Debian/armhf" +msgstr "" + +#. Tag: para +#: hardware.xml:407 +#, no-c-format +msgid "" +"The following systems are known to work with &debian;/armhf using the " +"multiplatform (armmp) kernel:" +msgstr "" + +#. Tag: term +#: hardware.xml:414 +#, no-c-format +msgid "Freescale MX53 Quick Start Board (MX53 LOCO Board)" +msgstr "" + +#. Tag: para +#: hardware.xml:416 +#, no-c-format +msgid "The IMX53QSB is a development board based on the i.MX53 SoC." +msgstr "" + +#. Tag: term +#: hardware.xml:423 +#, no-c-format +msgid "Versatile Express" +msgstr "" + +#. Tag: para +#: hardware.xml:425 +#, no-c-format +msgid "" +"The Versatile Express is a development board series from ARM consisting of a " +"baseboard which can be equipped with various CPU daughter boards." +msgstr "" + +#. Tag: term +#: hardware.xml:434 +#, no-c-format +msgid "Certain Allwinner sunXi-based development boards and embedded systems" +msgstr "" + +#. Tag: para +#: hardware.xml:437 +#, no-c-format +msgid "" +"The armmp kernel supports several development boards and embedded systems " +"based on the Allwinner A10 (architecture codename <quote>sun4i</quote>), " +"A10s/A13 (architecture codename <quote>sun5i</quote>), A20 (architecture " +"codename <quote>sun7i</quote>), A31/A31s (architecture codename " +"<quote>sun6i</quote>) and A23/A33 (part of the <quote>sun8i</quote> family) " +"SoCs. Full installer support (including provision of ready-made SD card " +"images with the installer) is currently available for the following sunXi-" +"based systems:" +msgstr "" + +#. Tag: para +#: hardware.xml:451 +#, no-c-format +msgid "Cubietech Cubieboard 1 + 2 / Cubietruck" +msgstr "" + +#. Tag: para +#: hardware.xml:454 +#, no-c-format +msgid "LeMaker Banana Pi and Banana Pro" +msgstr "" + +#. Tag: para +#: hardware.xml:457 +#, no-c-format +msgid "LinkSprite pcDuino and pcDuino3" +msgstr "" + +#. Tag: para +#: hardware.xml:460 +#, no-c-format +msgid "" +"Olimex A10-Olinuxino-LIME / A20-Olinuxino-LIME / A20-Olinuxino-LIME2 / A20-" +"Olinuxino Micro / A20-SOM-EVB" +msgstr "" + +#. Tag: para +#: hardware.xml:464 +#, no-c-format +msgid "Xunlong OrangePi Plus" +msgstr "" + +#. Tag: para +#: hardware.xml:470 +#, no-c-format +msgid "" +"System support for Allwinner sunXi-based devices is limited to drivers and " +"device-tree information available in the mainline Linux kernel. Vendor-" +"specific kernel trees (such as the Allwinner SDK kernels) and the android-" +"derived linux-sunxi.org kernel 3.4 series are not supported by &debian;." +msgstr "" + +#. Tag: para +#: hardware.xml:478 +#, no-c-format +msgid "" +"The mainline Linux kernel generally supports serial console, ethernet, SATA, " +"USB and MMC/SD-cards on Allwinner A10, A10s/A13, A20, A23/A33 and A31/A31s " +"SoCs. The level of support for local display (HDMI/VGA/LCD) and audio " +"hardware varies between individual systems. For most systems, the kernel " +"doesn't have native graphics drivers but instead uses the <quote>simplefb</" +"quote> infrastructure in which the bootloader initializes the display and " +"the kernel just re-uses the pre-initialized framebuffer. This generally " +"works reasonably well, although it results in certain limitations (the " +"display resolution cannot be changed on the fly and display powermanagement " +"is not possible)." +msgstr "" + +#. Tag: para +#: hardware.xml:493 +#, no-c-format +msgid "" +"Onboard flash memory intended to be used as a mass storage device generally " +"exists in two basic variants on sunXi-based systems: raw NAND flash and eMMC " +"flash. Most older sunXi-based boards with onboard flash storage use raw NAND " +"flash for which support is not generally available in the mainline kernel " +"and therefore also not in Debian. A number of newer systems use eMMC flash " +"instead of raw NAND flash. An eMMC flash chip basically appears as a fast, " +"non-removable SD card and is supported in the same way as a regular SD card." +msgstr "" + +#. Tag: para +#: hardware.xml:506 +#, no-c-format +msgid "" +"The installer includes basic support for a number of sunXi-based systems not " +"listed above, but it is largely untested on those systems as the &debian; " +"project doesn't have access to the corresponding hardware. No pre-built SD " +"card images with the installer are provided for those systems. Development " +"boards with such limited support include:" +msgstr "" + +#. Tag: para +#: hardware.xml:515 +#, no-c-format +msgid "Olimex A10s-Olinuxino Micro / A13-Olinuxino / A13-Olinuxino Micro" +msgstr "" + +#. Tag: para +#: hardware.xml:519 +#, no-c-format +msgid "Sinovoip BPI-M2 (A31s-based)" +msgstr "" + +#. Tag: para +#: hardware.xml:522 +#, no-c-format +msgid "Xunlong Orange Pi (A20-based) / Orange Pi Mini (A20-based)" +msgstr "" + +#. Tag: para +#: hardware.xml:527 +#, no-c-format +msgid "" +"In addition to the SoCs and systems listed above, the installer has very " +"limited support for the Allwinner H3 SoC and a number of boards based on it. " +"Mainline kernel support for the H3 is still largely work in progress at the " +"time of the Debian 9 release freeze, so the installer only supports serial " +"console, MMC/SD and the USB host controller on H3-based systems. There is no " +"driver for the on-board ethernet port of the H3 yet, so networking is only " +"possible with a USB ethernet adaptor or a USB wifi dongle. Systems based on " +"the H3 for which such very basic installer support is available include:" +msgstr "" + +#. Tag: para +#: hardware.xml:540 +#, no-c-format +msgid "FriendlyARM NanoPi NEO" +msgstr "" + +#. Tag: para +#: hardware.xml:543 +#, no-c-format +msgid "" +"Xunlong Orange Pi Lite / Orange Pi One / Orange Pi PC / Orange Pi PC Plus / " +"Orange Pi Plus / Orange Pi Plus 2E / Orange Pi 2" +msgstr "" + +#. Tag: term +#: hardware.xml:554 +#, no-c-format +msgid "NVIDIA Jetson TK1" +msgstr "" + +#. Tag: para +#: hardware.xml:556 +#, no-c-format +msgid "" +"The NVIDIA Jetson TK1 is a developer board based on the Tegra K1 chip (also " +"known as Tegra 124). The Tegra K1 features a quad-core 32-bit ARM Cortex-A15 " +"CPU and Kepler GPU (GK20A) with 192 CUDA cores. Other systems based on the " +"Tegra 124 may work, too." +msgstr "" + +#. Tag: term +#: hardware.xml:567 +#, no-c-format +msgid "Seagate Personal Cloud and Seagate NAS" +msgstr "" + +#. Tag: para +#: hardware.xml:569 +#, no-c-format +msgid "" +"The Seagate Personal Cloud and Seagate NAS are NAS devices based on " +"Marvell's Armada 370 platform. Debian supports the Personal Cloud (SRN21C), " +"Personal Cloud 2-Bay (SRN22C), Seagate NAS 2-Bay (SRPD20) and Seagate NAS 4-" +"Bay (SRPD40)." +msgstr "" + +#. Tag: term +#: hardware.xml:579 +#, no-c-format +msgid "SolidRun Cubox-i2eX / Cubox-i4Pro" +msgstr "" + +#. Tag: para +#: hardware.xml:581 +#, no-c-format +msgid "" +"The Cubox-i series is a set of small, cubical-shaped systems based on the " +"Freescale i.MX6 SoC family. System support for the Cubox-i series is limited " +"to drivers and device-tree information available in the mainline Linux " +"kernel; the Freescale 3.0 kernel series for the Cubox-i is not supported by " +"&debian;. Available drivers in the mainline kernel include serial console, " +"ethernet, USB, MMC/SD-card and display support over HDMI (console and X11). " +"In addition to that, the eSATA port on the Cubox-i4Pro is supported." +msgstr "" + +#. Tag: term +#: hardware.xml:596 +#, no-c-format +msgid "Wandboard" +msgstr "" + +#. Tag: para +#: hardware.xml:598 +#, no-c-format +msgid "" +"The Wandboard Quad, Dual and Solo are development boards based on the " +"Freescale i.MX6 Quad SoC. System support is limited to drivers and device-" +"tree information available in the mainline Linux kernel; the wandboard-" +"specific 3.0 and 3.10 kernel series from wandboard.org are not supported by " +"&debian;. The mainline kernel includes driver support for serial console, " +"display via HDMI (console and X11), ethernet, USB, MMC/SD, SATA (Quad only) " +"and analog audio. Support for the other audio options (S/PDIF, HDMI-Audio) " +"and for the onboard WLAN/Bluetooth module is untested or not available in " +"&debian; 9." +msgstr "" + +#. Tag: para +#: hardware.xml:616 +#, no-c-format +msgid "" +"Generally, the ARM multiplatform support in the Linux kernel allows running " +"&d-i; on armhf systems not explicitly listed above, as long as the kernel " +"used by &d-i; has support for the target system's components and a device-" +"tree file for the target is available. In these cases, the installer can " +"usually provide a working installation, but it may not be able to " +"automatically make the system bootable. Doing that in many cases requires " +"device-specific information." +msgstr "" + +#. Tag: para +#: hardware.xml:628 +#, no-c-format +msgid "" +"When using &d-i; on such systems, you may have to manually make the system " +"bootable at the end of the installation, e.g. by running the required " +"commands in a shell started from within &d-i;." +msgstr "" + +#. Tag: title +#: hardware.xml:637 +#, no-c-format +msgid "Platforms no longer supported by Debian/armhf" +msgstr "" + +#. Tag: term +#: hardware.xml:641 +#, no-c-format +msgid "EfikaMX" +msgstr "" + +#. Tag: para +#: hardware.xml:642 +#, no-c-format +msgid "" +"The EfikaMX platform (Genesi Efika Smartbook and Genesi EfikaMX nettop) was " +"supported in &debian; 7 with a platform-specific kernel, but is no longer " +"supported from &debian; 8 onwards. The code required to build the formerly " +"used platform-specific kernel has been removed from the upstream Linux " +"kernel source in 2012, so &debian; cannot provide newer builds. Using the " +"armmp multiplatform kernel on the EfikaMX platform would require device-tree " +"support for it, which is currently not available." +msgstr "" + +#. Tag: title +#: hardware.xml:660 +#, no-c-format +msgid "Platforms supported by Debian/armel" +msgstr "" + +#. Tag: para +#: hardware.xml:662 +#, no-c-format +msgid "" +"The following platforms are supported by &debian;/armel; they require " +"platform-specific kernels." +msgstr "" + +#. Tag: term +#: hardware.xml:670 +#, no-c-format +msgid "Kirkwood" +msgstr "" + +#. Tag: para +#: hardware.xml:671 +#, no-c-format +msgid "" +"Kirkwood is a system-on-chip (SoC) from Marvell that integrates an ARM CPU, " +"Ethernet, SATA, USB, and other functionality in one chip. &debian; currently " +"supports the following Kirkwood based devices:" +msgstr "" + +#. Tag: ulink +#: hardware.xml:679 +#, no-c-format +msgid "" +"Plug computers (SheevaPlug, GuruPlug, DreamPlug and Seagate FreeAgent " +"DockStar)" +msgstr "" + +#. Tag: para +#: hardware.xml:682 +#, no-c-format +msgid "" +"<ulink url=\"&url-arm-cyrius-qnap-kirkwood;\">QNAP Turbo Station</ulink> " +"(all TS-11x/TS-12x, HS-210, TS-21x/TS-22x and TS-41x/TS-42x models)" +msgstr "" + +#. Tag: para +#: hardware.xml:686 +#, no-c-format +msgid "" +"LaCie NASes (Network Space v2, Network Space Max v2, Internet Space v2, d2 " +"Network v2, 2Big Network v2 and 5Big Network v2)" +msgstr "" + +#. Tag: para +#: hardware.xml:690 +#, no-c-format +msgid "OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate)" +msgstr "" + +#. Tag: term +#: hardware.xml:699 hardware.xml:743 +#, no-c-format +msgid "Orion5x" +msgstr "" + +#. Tag: para +#: hardware.xml:700 +#, no-c-format +msgid "" +"Orion is a system-on-chip (SoC) from Marvell that integrates an ARM CPU, " +"Ethernet, SATA, USB, and other functionality in one chip. There are many " +"Network Attached Storage (NAS) devices on the market that are based on an " +"Orion chip. &debian; currently supports the following Orion based devices: " +"<ulink url=\"&url-arm-cyrius-kuroboxpro;\">Buffalo Kurobox</ulink> and " +"<ulink url=\"&url-arm-cyrius-mv2120;\">HP mv2120</ulink>." +msgstr "" + +#. Tag: term +#: hardware.xml:714 +#, no-c-format +msgid "Versatile" +msgstr "" + +#. Tag: para +#: hardware.xml:715 +#, no-c-format +msgid "" +"The Versatile platform is emulated by QEMU and is therefore a nice way to " +"test and run &debian; on ARM if you don't have real hardware." +msgstr "" + +#. Tag: title +#: hardware.xml:728 +#, no-c-format +msgid "Platforms and devices no longer supported by Debian/armel" +msgstr "" + +#. Tag: term +#: hardware.xml:732 +#, no-c-format +msgid "IXP4xx" +msgstr "" + +#. Tag: para +#: hardware.xml:733 +#, no-c-format +msgid "" +"Support for the Intel IXP4xx platform has been dropped in &debian; 9. The " +"Linksys NSLU2 device is based on IXP4xx and is therefore no longer supported." +msgstr "" + +#. Tag: para +#: hardware.xml:744 +#, no-c-format +msgid "" +"Support for the D-Link DNS-323 and Conceptronic CH3SNAS devices has been " +"dropped from the Orion5x platform in &debian; 9. The Linux kernel no longer " +"fits into the flash on these devices. Other Orion devices, such as Buffalo " +"Kurobox and HP mv2120, are still supported." +msgstr "" + +#. Tag: title +#: hardware.xml:763 hardware.xml:931 hardware.xml:1374 +#, no-c-format +msgid "CPU, Main Boards, and Video Support" +msgstr "" + +#. Tag: para +#: hardware.xml:764 +#, no-c-format +msgid "" +"Complete information concerning supported peripherals can be found at <ulink " +"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. " +"This section merely outlines the basics." +msgstr "" + +#. Tag: title +#: hardware.xml:772 hardware.xml:875 +#, no-c-format +msgid "<title>CPU</title>" +msgstr "" + +#. Tag: para +#: hardware.xml:773 +#, no-c-format +msgid "" +"Nearly all x86-based (IA-32) processors still in use in personal computers " +"are supported. 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:780 +#, no-c-format +msgid "" +"However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run " +"on 586 (Pentium) or earlier processors." +msgstr "" + +#. Tag: para +#: hardware.xml:786 +#, no-c-format +msgid "" +"If your system has a 64-bit processor from the AMD64 or Intel 64 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: title +#: hardware.xml:795 +#, no-c-format +msgid "I/O Bus" +msgstr "" + +#. Tag: para +#: hardware.xml:796 +#, no-c-format +msgid "" +"The system bus is the part of the motherboard which allows the CPU to " +"communicate with peripherals such as storage devices. Your computer must use " +"the PCI, PCIe, or PCI-X bus. Essentially all personal computers sold in " +"recent years use one of these." +msgstr "" + +#. Tag: title +#: hardware.xml:813 +#, no-c-format +msgid "Platforms supported by the &debian; &architecture; port" +msgstr "" + +#. Tag: para +#: hardware.xml:815 +#, no-c-format +msgid "&debian; on &arch-title; supports the following platforms:" +msgstr "" + +#. Tag: term +#: hardware.xml:821 +#, no-c-format +msgid "<term>Cavium Octeon</term>" +msgstr "" + +#. Tag: para +#: hardware.xml:823 +#, no-c-format +msgid "" +"Cavium designs a range of 64-bit MIPS Octeon processors which are mainly " +"used in networking devices. Devices with these processors include the " +"Ubiquiti EdgeRouter and the Rhino Labs UTM8." +msgstr "" + +#. Tag: term +#: hardware.xml:832 +#, no-c-format +msgid "<term>Loongson 3</term>" +msgstr "" + +#. Tag: para +#: hardware.xml:834 +#, no-c-format +msgid "Devices based on the Loongson 3A and 3B processors are supported." +msgstr "" + +#. Tag: term +#: hardware.xml:842 +#, no-c-format +msgid "<term>MIPS Malta</term>" +msgstr "" + +#. Tag: para +#: hardware.xml:844 +#, no-c-format +msgid "" +"This platform is emulated by QEMU and is therefore a nice way to test and " +"run &debian; on MIPS if you don't have the hardware." +msgstr "" + +#. Tag: para +#: hardware.xml:848 +#, no-c-format +msgid "" +"There are two Malta kernel flavours: 4kc-malta is built for 32-bit " +"processors, and 5kc-malta is built for 64-bit processors." +msgstr "" + +#. Tag: para +#: hardware.xml:856 +#, no-c-format +msgid "" +"In addition, other boards which contain <phrase arch=\"mips;mipsel" +"\">MIPS32r2 or</phrase> MIPS64r2 based processors should also be able to run " +"&debian;, however kernels for these processors are not built and the " +"&debian; installer does not directly support them." +msgstr "" + +#. Tag: para +#: hardware.xml:864 +#, no-c-format +msgid "" +"Complete information regarding supported mips/mipsel/mips64el machines can " +"be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</ulink>. " +"In the following, only the systems supported by the &debian; installer will " +"be covered. If you are looking for support for other subarchitectures, " +"please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-" +"listname; mailing list</ulink>." +msgstr "" + +#. Tag: para +#: hardware.xml:876 +#, no-c-format +msgid "" +"Some MIPS machines can be operated in both big and little endian mode. " +"<phrase arch=\"mips64el;mipsel\"> For little endian MIPS, please read the " +"documentation for the mipsel and mips64el architectures. </phrase> <phrase " +"arch=\"mips\"> For big endian MIPS, please read the documentation for the " +"mips architecture. </phrase>" +msgstr "" + +#. Tag: title +#: hardware.xml:891 +#, no-c-format +msgid "Platforms no longer supported by the &debian; &architecture; port" +msgstr "" + +#. Tag: para +#: hardware.xml:892 +#, no-c-format +msgid "" +"Since &debian; Stretch, support for all MIPS processors which do not " +"implement MIPS32 Release 2 have been dropped. Therefore the following " +"platforms supported in Jessie are no longer supported:" +msgstr "" + +#. Tag: term +#: hardware.xml:899 +#, no-c-format +msgid "Loongson 2E and 2F" +msgstr "" + +#. Tag: listitem +#: hardware.xml:900 +#, no-c-format +msgid "" +"These are the older Loongson processors. Devices based on them include the " +"Fuloong Mini-PC and the Lemote Yeeloong laptop." +msgstr "" + +#. Tag: term +#: hardware.xml:906 +#, no-c-format +msgid "SGI IP22" +msgstr "" + +#. Tag: listitem +#: hardware.xml:907 +#, no-c-format +msgid "This platform includes the SGI machines Indy, Indigo 2 and Challenge S." +msgstr "" + +#. Tag: term +#: hardware.xml:912 +#, no-c-format +msgid "SGI IP32" +msgstr "" + +#. Tag: listitem +#: hardware.xml:913 +#, no-c-format +msgid "This platform is generally known as SGI O2." +msgstr "" + +#. Tag: term +#: hardware.xml:916 +#, no-c-format +msgid "Broadcom BCM91250" +msgstr "" + +#. Tag: listitem +#: hardware.xml:917 +#, no-c-format +msgid "" +"Development board for Broadcom's SiByte core. Also known by its codename " +"SWARM." +msgstr "" + +#. Tag: para +#: hardware.xml:932 +#, no-c-format +msgid "" +"For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and " +"PreP subarchitectures are supported." +msgstr "" + +#. Tag: title +#: hardware.xml:953 +#, no-c-format +msgid "Kernel Flavours" +msgstr "" + +#. Tag: para +#: hardware.xml:955 +#, no-c-format +msgid "" +"There are two flavours of the powerpc kernel in &debian;, based on the CPU " +"type:" +msgstr "" + +#. Tag: term +#: hardware.xml:962 +#, no-c-format +msgid "powerpc" +msgstr "" + +#. Tag: para +#: hardware.xml:963 +#, no-c-format +msgid "" +"This kernel flavour supports the PowerPC 601, 603, 604, 740, 750, and 7400 " +"processors. All Apple PowerMac machines up to and including the one marketed " +"as G4 use one of these processors." +msgstr "" + +#. Tag: term +#: hardware.xml:973 +#, no-c-format +msgid "powerpc-smp" +msgstr "" + +#. Tag: para +#: hardware.xml:974 +#, no-c-format +msgid "All Apple PowerMac G4 SMP machines." +msgstr "" + +#. Tag: term +#: hardware.xml:982 +#, no-c-format +msgid "power64" +msgstr "" + +#. Tag: para +#: hardware.xml:983 +#, no-c-format +msgid "The power64 kernel flavour supports the following CPUs:" +msgstr "" + +#. Tag: para +#: hardware.xml:987 +#, no-c-format +msgid "" +"The POWER3 processor is used in older IBM 64-bit server systems: known " +"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, " +"and the RS/6000 7044-170, 7043-260, and 7044-270." +msgstr "" + +#. Tag: para +#: hardware.xml:993 +#, no-c-format +msgid "" +"The POWER4 processor is used in more recent IBM 64-bit server systems: known " +"models include the pSeries 615, 630, 650, 655, 670, and 690." +msgstr "" + +#. Tag: para +#: hardware.xml:998 +#, no-c-format +msgid "" +"Systems using the PPC970 processor (Apple G5, YDL PowerStation, IBM " +"Intellistation POWER 185) are also based on the POWER4 architecture, and use " +"this kernel flavour." +msgstr "" + +#. Tag: para +#: hardware.xml:1004 +#, no-c-format +msgid "Newer IBM systems using POWER5, POWER6, and POWER7 processors." +msgstr "" + +#. Tag: title +#: hardware.xml:1037 +#, no-c-format +msgid "Power Macintosh (pmac) subarchitecture" +msgstr "" + +#. Tag: para +#: hardware.xml:1039 +#, no-c-format +msgid "" +"Apple (and briefly a few other manufacturers — Power Computing, for " +"example) made a series of Macintosh computers based on the PowerPC " +"processor. For purposes of architecture support, they are categorized as " +"NuBus (not supported by &debian;), OldWorld, and NewWorld." +msgstr "" + +#. Tag: para +#: hardware.xml:1046 +#, no-c-format +msgid "" +"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI " +"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld " +"machines. Those pre-iMac PowerPC models from Apple use a four digit naming " +"scheme, except for the beige colored G3 systems, which are also OldWorld." +msgstr "" + +#. Tag: para +#: hardware.xml:1054 +#, no-c-format +msgid "" +"The so called NewWorld PowerMacs are any PowerMacs in translucent colored " +"plastic cases and later models. That includes all iMacs, iBooks, G4 systems, " +"blue colored G3 systems, and most PowerBooks manufactured in and after 1999. " +"The NewWorld PowerMacs are also known for using the <quote>ROM in RAM</" +"quote> system for MacOS, and were manufactured from mid-1998 onwards." +msgstr "" + +#. Tag: para +#: hardware.xml:1062 +#, no-c-format +msgid "" +"Specifications for Apple hardware are available at <ulink url=\"http://www." +"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older " +"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/" +"index.html\">AppleSpec Legacy</ulink>." +msgstr "" + +#. Tag: entry +#: hardware.xml:1078 hardware.xml:1213 hardware.xml:1257 hardware.xml:1290 +#, no-c-format +msgid "Model Name/Number" +msgstr "" + +#. Tag: entry +#: hardware.xml:1079 +#, no-c-format +msgid "Generation" +msgstr "" + +#. Tag: entry +#: hardware.xml:1085 +#, no-c-format +msgid "Apple" +msgstr "" + +#. Tag: entry +#: hardware.xml:1086 +#, no-c-format +msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" +msgstr "" + +#. Tag: entry +#: hardware.xml:1087 hardware.xml:1090 hardware.xml:1093 hardware.xml:1096 +#: hardware.xml:1099 hardware.xml:1102 hardware.xml:1105 hardware.xml:1108 +#: hardware.xml:1111 hardware.xml:1114 hardware.xml:1117 hardware.xml:1120 +#: hardware.xml:1123 hardware.xml:1126 hardware.xml:1129 hardware.xml:1132 +#, no-c-format +msgid "NewWorld" +msgstr "" + +#. Tag: entry +#: hardware.xml:1089 +#, no-c-format +msgid "iMac Summer 2000, Early 2001" +msgstr "" + +#. Tag: entry +#: hardware.xml:1092 +#, no-c-format +msgid "iMac G5" +msgstr "" + +#. Tag: entry +#: hardware.xml:1095 +#, no-c-format +msgid "iBook, iBook SE, iBook Dual USB" +msgstr "" + +#. Tag: entry +#: hardware.xml:1098 +#, no-c-format +msgid "iBook2" +msgstr "" + +#. Tag: entry +#: hardware.xml:1101 +#, no-c-format +msgid "iBook G4" +msgstr "" + +#. Tag: entry +#: hardware.xml:1104 +#, no-c-format +msgid "Power Macintosh Blue and White (B&W) G3" +msgstr "" + +#. Tag: entry +#: hardware.xml:1107 +#, no-c-format +msgid "Power Macintosh G4 PCI, AGP, Cube" +msgstr "" + +#. Tag: entry +#: hardware.xml:1110 +#, no-c-format +msgid "Power Macintosh G4 Gigabit Ethernet" +msgstr "" + +#. Tag: entry +#: hardware.xml:1113 +#, no-c-format +msgid "Power Macintosh G4 Digital Audio, Quicksilver" +msgstr "" + +#. Tag: entry +#: hardware.xml:1116 +#, no-c-format +msgid "Power Macintosh G5" +msgstr "" + +#. Tag: entry +#: hardware.xml:1119 +#, no-c-format +msgid "PowerBook G3 FireWire Pismo (2000)" +msgstr "" + +#. Tag: entry +#: hardware.xml:1122 +#, no-c-format +msgid "PowerBook G3 Lombard (1999)" +msgstr "" + +#. Tag: entry +#: hardware.xml:1125 +#, no-c-format +msgid "PowerBook G4 Titanium" +msgstr "" + +#. Tag: entry +#: hardware.xml:1128 +#, no-c-format +msgid "PowerBook G4 Aluminum" +msgstr "" + +#. Tag: entry +#: hardware.xml:1131 +#, no-c-format +msgid "Xserve G5" +msgstr "" + +#. Tag: entry +#: hardware.xml:1134 +#, no-c-format +msgid "Performa 4400, 54xx, 5500" +msgstr "" + +#. Tag: entry +#: hardware.xml:1135 hardware.xml:1138 hardware.xml:1141 hardware.xml:1144 +#: hardware.xml:1147 hardware.xml:1150 hardware.xml:1153 hardware.xml:1156 +#: hardware.xml:1159 hardware.xml:1162 hardware.xml:1165 hardware.xml:1168 +#: hardware.xml:1174 hardware.xml:1177 hardware.xml:1183 hardware.xml:1189 +#: hardware.xml:1195 +#, no-c-format +msgid "OldWorld" +msgstr "" + +#. Tag: entry +#: hardware.xml:1137 +#, no-c-format +msgid "Performa 6360, 6400, 6500" +msgstr "" + +#. Tag: entry +#: hardware.xml:1140 +#, no-c-format +msgid "Power Macintosh 4400, 5400" +msgstr "" + +#. Tag: entry +#: hardware.xml:1143 +#, no-c-format +msgid "Power Macintosh 7200, 7300, 7500, 7600" +msgstr "" + +#. Tag: entry +#: hardware.xml:1146 +#, no-c-format +msgid "Power Macintosh 8200, 8500, 8600" +msgstr "" + +#. Tag: entry +#: hardware.xml:1149 +#, no-c-format +msgid "Power Macintosh 9500, 9600" +msgstr "" + +#. Tag: entry +#: hardware.xml:1152 +#, no-c-format +msgid "Power Macintosh (Beige) G3 Minitower" +msgstr "" + +#. Tag: entry +#: hardware.xml:1155 +#, no-c-format +msgid "Power Macintosh (Beige) Desktop, All-in-One" +msgstr "" + +#. Tag: entry +#: hardware.xml:1158 +#, no-c-format +msgid "PowerBook 2400, 3400, 3500" +msgstr "" + +#. Tag: entry +#: hardware.xml:1161 +#, no-c-format +msgid "PowerBook G3 Wallstreet (1998)" +msgstr "" + +#. Tag: entry +#: hardware.xml:1164 +#, no-c-format +msgid "Twentieth Anniversary Macintosh" +msgstr "" + +#. Tag: entry +#: hardware.xml:1167 +#, no-c-format +msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" +msgstr "" + +#. Tag: entry +#: hardware.xml:1172 +#, no-c-format +msgid "Power Computing" +msgstr "" + +#. Tag: entry +#: hardware.xml:1173 +#, no-c-format +msgid "PowerBase, PowerTower / Pro, PowerWave" +msgstr "" + +#. Tag: entry +#: hardware.xml:1176 +#, no-c-format +msgid "PowerCenter / Pro, PowerCurve" +msgstr "" + +#. Tag: entry +#: hardware.xml:1181 +#, no-c-format +msgid "UMAX" +msgstr "" + +#. Tag: entry +#: hardware.xml:1182 +#, no-c-format +msgid "C500, C600, J700, S900" +msgstr "" + +#. Tag: entry +#: hardware.xml:1187 +#, no-c-format +msgid "<entry>APS</entry>" +msgstr "" + +#. Tag: entry +#: hardware.xml:1188 +#, no-c-format +msgid "APS Tech M*Power 604e/2000" +msgstr "" + +#. Tag: entry +#: hardware.xml:1193 hardware.xml:1219 +#, no-c-format +msgid "Motorola" +msgstr "" + +#. Tag: entry +#: hardware.xml:1194 +#, no-c-format +msgid "Starmax 3000, 4000, 5000, 5500" +msgstr "" + +#. Tag: title +#: hardware.xml:1203 +#, no-c-format +msgid "PReP subarchitecture" +msgstr "" + +#. Tag: entry +#: hardware.xml:1220 +#, no-c-format +msgid "Firepower, PowerStack Series E, PowerStack II" +msgstr "" + +#. Tag: entry +#: hardware.xml:1222 +#, no-c-format +msgid "MPC 7xx, 8xx" +msgstr "" + +#. Tag: entry +#: hardware.xml:1224 +#, no-c-format +msgid "MTX, MTX+" +msgstr "" + +#. Tag: entry +#: hardware.xml:1226 +#, no-c-format +msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" +msgstr "" + +#. Tag: entry +#: hardware.xml:1228 +#, no-c-format +msgid "MCP(N)750" +msgstr "" + +#. Tag: entry +#: hardware.xml:1232 hardware.xml:1263 +#, no-c-format +msgid "IBM RS/6000" +msgstr "" + +#. Tag: entry +#: hardware.xml:1233 +#, no-c-format +msgid "40P, 43P" +msgstr "" + +#. Tag: entry +#: hardware.xml:1235 +#, no-c-format +msgid "Power 830/850/860 (6070, 6050)" +msgstr "" + +#. Tag: entry +#: hardware.xml:1237 +#, no-c-format +msgid "6030, 7025, 7043" +msgstr "" + +#. Tag: entry +#: hardware.xml:1239 +#, no-c-format +msgid "p640" +msgstr "" + +#. Tag: title +#: hardware.xml:1247 +#, no-c-format +msgid "CHRP subarchitecture" +msgstr "" + +#. Tag: entry +#: hardware.xml:1264 +#, no-c-format +msgid "B50, 43P-150, 44P" +msgstr "" + +#. Tag: entry +#: hardware.xml:1267 +#, no-c-format +msgid "Genesi" +msgstr "" + +#. Tag: entry +#: hardware.xml:1268 +#, no-c-format +msgid "Pegasos I, Pegasos II" +msgstr "" + +#. Tag: entry +#: hardware.xml:1271 +#, no-c-format +msgid "Fixstars" +msgstr "" + +#. Tag: entry +#: hardware.xml:1272 +#, no-c-format +msgid "YDL PowerStation" +msgstr "" + +#. Tag: title +#: hardware.xml:1280 +#, no-c-format +msgid "APUS subarchitecture (unsupported)" +msgstr "" + +#. Tag: entry +#: hardware.xml:1296 +#, no-c-format +msgid "Amiga Power-UP Systems (APUS)" +msgstr "" + +#. Tag: entry +#: hardware.xml:1297 +#, no-c-format +msgid "A1200, A3000, A4000" +msgstr "" + +#. Tag: title +#: hardware.xml:1305 +#, no-c-format +msgid "Nubus PowerMac subarchitecture (unsupported)" +msgstr "" + +#. Tag: para +#: hardware.xml:1307 +#, no-c-format +msgid "" +"NuBus systems are not currently supported by &debian;/powerpc. The " +"monolithic Linux/PPC kernel architecture does not have support for these " +"machines; instead, one must use the MkLinux Mach microkernel, which &debian; " +"does not yet support. These include the following: <itemizedlist> " +"<listitem><para> Power Macintosh 6100, 7100, 8100 </para></listitem> " +"<listitem><para> Performa 5200, 6200, 6300 </para></listitem> " +"<listitem><para> Powerbook 1400, 2300, and 5300 </para></listitem> " +"<listitem><para> Workgroup Server 6150, 8150, 9150 </para></listitem> </" +"itemizedlist> A linux kernel for these machines and limited support is " +"available at <ulink url=\"http://nubus-pmac.sourceforge.net/\"></ulink>." +msgstr "" + +#. Tag: title +#: hardware.xml:1344 +#, no-c-format +msgid "Non-PowerPC Macs" +msgstr "" + +#. Tag: para +#: hardware.xml:1346 +#, no-c-format +msgid "" +"Macintosh computers using the 680x0 series of processors are <emphasis>not</" +"emphasis> in the PowerPC family but are instead m68k machines. Those models " +"start with <quote>Mac II</quote> series, go on to the <quote>LC</quote> " +"family, then the Centris series, and culminate in the Quadras and Performas. " +"These models usually have a Roman numeral or 3-digit model number such as " +"Mac IIcx, LCIII or Quadra 950." +msgstr "" + +#. Tag: para +#: hardware.xml:1355 +#, no-c-format +msgid "" +"This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, " +"IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, " +"580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra " +"(605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the " +"Performa 200-640CD." +msgstr "" + +#. Tag: para +#: hardware.xml:1363 +#, no-c-format +msgid "" +"In laptops, it started with the Mac Portable, then the PowerBook 100-190cs " +"and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, " +"please see the section above)." +msgstr "" + +#. Tag: title +#: hardware.xml:1377 +#, no-c-format +msgid "Machines" +msgstr "" + +#. Tag: para +#: hardware.xml:1380 +#, no-c-format +msgid "S822L" +msgstr "" + +#. Tag: para +#: hardware.xml:1385 +#, no-c-format +msgid "S821L" +msgstr "" + +#. Tag: para +#: hardware.xml:1390 +#, no-c-format +msgid "S822" +msgstr "" + +#. Tag: para +#: hardware.xml:1395 +#, no-c-format +msgid "S821" +msgstr "" + +#. Tag: para +#: hardware.xml:1400 +#, no-c-format +msgid "TYAN GN70-BP010" +msgstr "" + +#. Tag: title +#: hardware.xml:1415 +#, no-c-format +msgid "zSeries and System z machine types" +msgstr "" + +#. Tag: para +#: hardware.xml:1416 +#, no-c-format +msgid "" +"The minimum required z/Architecture processor type is z196. The most current " +"information about IBM's Linux support can be found at the <ulink url=" +"\"http://www.ibm.com/developerworks/linux/linux390/development_technical.html" +"\"> Linux on <trademark class=\"registered\">System z</trademark> page on " +"developerWorks</ulink>." +msgstr "" + +#. Tag: title +#: hardware.xml:1429 +#, no-c-format +msgid "PAV and HyperPAV" +msgstr "" + +#. Tag: para +#: hardware.xml:1430 +#, no-c-format +msgid "" +"PAV and HyperPAV are supported transparently, multipathing is not needed to " +"take advantage of these storage system features. Be sure to configure the " +"devices during DASD device selection. The alias devices will not be offered " +"neither for formatting, partitioning nor direct use." +msgstr "" + +#. Tag: title +#: hardware.xml:1446 +#, no-c-format +msgid "CPU and Main Boards Support" +msgstr "" + +#. Tag: para +#: hardware.xml:1447 +#, no-c-format +msgid "" +"Sparc-based hardware is divided into a number of different subarchitectures, " +"identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u " +"or sun4v. The following list describes what machines they include and what " +"level of support may be expected for each of them." +msgstr "" + +#. Tag: term +#: hardware.xml:1458 +#, no-c-format +msgid "sun4, sun4c, sun4d, sun4m" +msgstr "" + +#. Tag: para +#: hardware.xml:1460 +#, no-c-format +msgid "" +"None of these 32-bit sparc subarchitectures (sparc32) is supported. For a " +"complete list of machines belonging to these subarchitectures, please " +"consult the <ulink url=\"http://en.wikipedia.org/wiki/SPARCstation" +"\">Wikipedia SPARCstation page</ulink>." +msgstr "" + +#. Tag: para +#: hardware.xml:1467 +#, no-c-format +msgid "" +"The last &debian; release to support sparc32 was Etch, but even then only " +"for sun4m systems. Support for the other 32-bits subarchitectures had " +"already been discontinued after earlier releases." +msgstr "" + +#. Tag: term +#: hardware.xml:1477 +#, no-c-format +msgid "sun4u" +msgstr "" + +#. Tag: para +#: hardware.xml:1479 +#, no-c-format +msgid "" +"This subarchitecture includes all 64-bit machines (sparc64) based on the " +"UltraSparc processor and its clones. Most of the machines are well " +"supported, even though for some you may experience problems booting from CD " +"due to firmware or bootloader bugs (this problem may be worked around by " +"using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP " +"configurations respectively." +msgstr "" + +#. Tag: term +#: hardware.xml:1492 +#, no-c-format +msgid "sun4v" +msgstr "" + +#. Tag: para +#: hardware.xml:1494 +#, no-c-format +msgid "" +"This is the newest addition to the Sparc family, which includes machines " +"based on the Niagara multi-core CPUs. At the moment such CPUs are only " +"available in T1000 and T2000 servers by Sun, and are well supported. Use the " +"sparc64-smp kernel." +msgstr "" + +#. Tag: para +#: hardware.xml:1505 +#, no-c-format +msgid "" +"Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are " +"not supported due to lack of support in the Linux kernel." +msgstr "" + +#. Tag: title +#: hardware.xml:1514 +#, no-c-format +msgid "Laptops" +msgstr "" + +#. Tag: para +#: hardware.xml:1515 +#, no-c-format +msgid "" +"From a technical point of view, laptops are normal PCs, so all information " +"regarding PC systems applies to laptops as well. Installations on laptops " +"nowadays usually work out of the box, including things like automatically " +"suspending the system on closing the lid and laptop specfic hardware buttons " +"like those for disabling the wifi interfaces (<quote>airplane mode</quote>). " +"Nonetheless sometimes the hardware vendors use specialized or proprietary " +"hardware for some laptop-specific functions which might not be supported. To " +"see if your particular laptop works well with GNU/Linux, see for example the " +"<ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>." +msgstr "" + +#. Tag: title +#: hardware.xml:1532 hardware.xml:1552 hardware.xml:1574 hardware.xml:1597 +#, no-c-format +msgid "Multiple Processors" +msgstr "" + +#. Tag: para +#: hardware.xml:1533 +#, no-c-format +msgid "" +"Multiprocessor support — also called <quote>symmetric multiprocessing</" +"quote> or SMP — is available for this architecture. Having multiple " +"processors in a computer was originally only an issue for high-end server " +"systems but has become common in recent years nearly everywhere with the " +"introduction of so called <quote>multi-core</quote> processors. These " +"contain two or more processor units, called <quote>cores</quote>, in one " +"physical chip." +msgstr "" + +#. Tag: para +#: hardware.xml:1543 +#, no-c-format +msgid "" +"The standard &debian; &release; kernel image has been compiled with SMP " +"support. It is also usable on non-SMP systems without problems." +msgstr "" + +#. Tag: para +#: hardware.xml:1554 +#, no-c-format +msgid "" +"Multiprocessor support — also called <quote>symmetric multiprocessing</" +"quote> or SMP — is available for this architecture. The standard " +"&debian; &release; kernel image has been compiled with <firstterm>SMP-" +"alternatives</firstterm> support. This means that the kernel will detect the " +"number of processors (or processor cores) and will automatically deactivate " +"SMP on uniprocessor systems." +msgstr "" + +#. Tag: para +#: hardware.xml:1563 +#, no-c-format +msgid "" +"Having multiple processors in a computer was originally only an issue for " +"high-end server systems but has become common in recent years nearly " +"everywhere with the introduction of so called <quote>multi-core</quote> " +"processors. These contain two or more processor units, called <quote>cores</" +"quote>, in one physical chip." +msgstr "" + +#. Tag: para +#: hardware.xml:1575 +#, no-c-format +msgid "" +"Multiprocessor support — also called <quote>symmetric multiprocessing</" +"quote> or SMP — is available for this architecture. However, the " +"standard &debian; &release; kernel image does not support SMP. This should " +"not prevent installation, since the standard, non-SMP kernel should boot on " +"SMP systems; the kernel will simply use only the first CPU." +msgstr "" + +#. Tag: para +#: hardware.xml:1584 +#, no-c-format +msgid "" +"In order to take advantage of multiple processors, you'll have to replace " +"the standard &debian; kernel.<phrase arch=\"linux-any\"> You can find a " +"discussion of how to do this in <xref linkend=\"kernel-baking\"/>. At this " +"time (kernel version &kernelversion;) the way you enable SMP is to select " +"<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</" +"quote> section of the kernel config.</phrase>" +msgstr "" + +#. Tag: para +#: hardware.xml:1598 +#, no-c-format +msgid "" +"Multiprocessor support — also called <quote>symmetric multiprocessing</" +"quote> or SMP — is available for this architecture, and is supported " +"by a precompiled &debian; kernel image. Depending on your install media, " +"this SMP-capable kernel may or may not be installed by default. This should " +"not prevent installation, since the standard, non-SMP kernel should boot on " +"SMP systems; the kernel will simply use the first CPU." +msgstr "" + +#. Tag: para +#: hardware.xml:1608 +#, no-c-format +msgid "" +"In order to take advantage of multiple processors, you should check to see " +"if a kernel package that supports SMP is installed, and if not, choose an " +"appropriate kernel package." +msgstr "" + +#. Tag: para +#: hardware.xml:1614 +#, no-c-format +msgid "" +"You can also build your own customized kernel to support SMP.<phrase arch=" +"\"linux-any\"> You can find a discussion of how to do this in <xref linkend=" +"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way " +"you enable SMP is to select <quote>&smp-config-option;</quote> in the " +"<quote>&smp-config-section;</quote> section of the kernel config.</phrase>" +msgstr "" + +#. Tag: title +#: hardware.xml:1625 +#, no-c-format +msgid "Graphics Hardware Support" +msgstr "" + +#. Tag: para +#: hardware.xml:1626 +#, no-c-format +msgid "" +"&debian;'s support for graphical interfaces is determined by the underlying " +"support found in X.Org's X11 system, and the kernel. Basic framebuffer " +"graphics is provided by the kernel, whilst desktop environments use X11. " +"Whether advanced graphics card features such as 3D-hardware acceleration or " +"hardware-accelerated video are available, depends on the actual graphics " +"hardware used in the system and in some cases on the installation of " +"additional <quote>firmware</quote> images (see <xref linkend=\"hardware-" +"firmware\"/>)." +msgstr "" + +#. Tag: para +#: hardware.xml:1638 +#, no-c-format +msgid "" +"On modern PCs, having a graphical display usually works out of the box. In " +"very few cases there have been reports about hardware on which installation " +"of additional graphics card firmware was required even for basic graphics " +"support, but these have been rare exceptions. For quite a lot of hardware, " +"3D acceleration also works well out of the box, but there is still some " +"hardware that needs binary blobs to work well." +msgstr "" + +#. Tag: para +#: hardware.xml:1649 +#, no-c-format +msgid "" +"Nearly all ARM machines have the graphics hardware built-in, rather than " +"being on a plug-in card. Some machines do have expansion slots which will " +"take graphics cards, but that is a rarity. Hardware designed to be headless " +"with no graphics at all is quite common. Whilst basic framebuffer video " +"provided by the kernel should work on all devices that have graphics, fast " +"3D graphics invariably needs binary drivers to work. The situation is " +"changing quickly but at the time of the &releasename; release free drivers " +"for nouveau (Nvidia Tegra K1 SoC) and freedreno (Qualcomm Snapdragon SoCs) " +"are available in the release. Other hardware needs non-free drivers from 3rd " +"parties." +msgstr "" + +#. Tag: para +#: hardware.xml:1663 +#, no-c-format +msgid "" +"Details on supported graphics hardware and pointing devices can be found at " +"<ulink url=\"&url-xorg;\"></ulink>. &debian; &release; ships with X.Org " +"version &x11ver;." +msgstr "" + +#. Tag: para +#: hardware.xml:1668 +#, no-c-format +msgid "" +"Most graphics options commonly found on Sparc-based machines are supported. " +"X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, " +"sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), " +"PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards " +"(glint driver). To use an Elite3D card with X.org you additionally need to " +"install the <classname>afbinit</classname> package, and read the " +"documentation included with it on how to activate the card." +msgstr "" + +#. Tag: para +#: hardware.xml:1678 +#, no-c-format +msgid "" +"It is not uncommon for a Sparc machine to have two graphics cards in a " +"default configuration. In such a case there is a possibility that the Linux " +"kernel will not direct its output to the card initially used by the " +"firmware. The lack of output on the graphical console may then be mistaken " +"for a hang (usually the last message seen on console is 'Booting Linux...'). " +"One possible solution is to physically remove one of the video cards; " +"another option is to disable one of the cards using a kernel boot parameter. " +"Also, if graphical output is not required or desired, serial console may be " +"used as an alternative. On some systems use of serial console can be " +"activated automatically by disconnecting the keyboard before booting the " +"system." +msgstr "" + +#. Tag: title +#: hardware.xml:1700 +#, no-c-format +msgid "Network Connectivity Hardware" +msgstr "" + +#. Tag: para +#: hardware.xml:1701 +#, no-c-format +msgid "" +"Almost any network interface card (NIC) supported by the &arch-kernel; " +"kernel should also be supported by the installation system; drivers should " +"normally be loaded automatically. <phrase arch=\"x86\">This includes most " +"PCI/PCI-Express cards as well as PCMCIA/Express Cards on laptops.</phrase> " +"<phrase arch=\"i386\">Many older ISA cards are supported as well.</phrase>" +msgstr "" + +#. Tag: para +#: hardware.xml:1711 +#, 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:1717 +#, no-c-format +msgid "Sun LANCE" +msgstr "" + +#. Tag: para +#: hardware.xml:1722 +#, no-c-format +msgid "Sun Happy Meal" +msgstr "" + +#. Tag: para +#: hardware.xml:1727 +#, no-c-format +msgid "Sun BigMAC" +msgstr "" + +#. Tag: para +#: hardware.xml:1732 +#, no-c-format +msgid "Sun QuadEthernet" +msgstr "" + +#. Tag: para +#: hardware.xml:1737 +#, no-c-format +msgid "MyriCOM Gigabit Ethernet" +msgstr "" + +#. Tag: para +#: hardware.xml:1744 +#, no-c-format +msgid "The list of supported network devices is:" +msgstr "" + +#. Tag: para +#: hardware.xml:1749 +#, no-c-format +msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" +msgstr "" + +#. Tag: para +#: hardware.xml:1754 +#, no-c-format +msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" +msgstr "" + +#. Tag: para +#: hardware.xml:1759 +#, no-c-format +msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" +msgstr "" + +#. Tag: para +#: hardware.xml:1768 +#, no-c-format +msgid "" +"On &arch-title;, most built-in Ethernet devices are supported and modules " +"for additional PCI and USB devices are provided." +msgstr "" + +#. Tag: para +#: hardware.xml:1773 +#, no-c-format +msgid "ISDN is supported, but not during the installation." +msgstr "" + +#. Tag: title +#: hardware.xml:1780 +#, no-c-format +msgid "Wireless Network Cards" +msgstr "" + +#. Tag: para +#: hardware.xml:1781 +#, no-c-format +msgid "" +"Wireless networking is in general supported as well and a growing number of " +"wireless adapters are supported by the official &arch-kernel; kernel, " +"although many of them do require firmware to be loaded." +msgstr "" + +#. Tag: para +#: hardware.xml:1788 +#, no-c-format +msgid "" +"If firmware is needed, the installer will prompt you to load firmware. See " +"<xref linkend=\"loading-firmware\"/> for detailed information on how to load " +"firmware during the installation." +msgstr "" + +#. Tag: para +#: hardware.xml:1793 +#, no-c-format +msgid "" +"Wireless NICs that are not supported by the official &arch-kernel; kernel " +"can generally be made to work under &debian-gnu;, but are not supported " +"during the installation." +msgstr "" + +#. Tag: para +#: hardware.xml:1798 +#, no-c-format +msgid "" +"If there is a problem with wireless and there is no other NIC you can use " +"during the installation, it is still possible to install &debian-gnu; 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." +msgstr "" + +#. Tag: para +#: hardware.xml:1808 +#, 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:1822 +#, no-c-format +msgid "Known Issues for &arch-title;" +msgstr "" + +#. Tag: para +#: hardware.xml:1823 +#, no-c-format +msgid "" +"There are a couple of issues with specific network cards that are worth " +"mentioning here." +msgstr "" + +#. Tag: title +#: hardware.xml:1830 +#, no-c-format +msgid "Conflict between tulip and dfme drivers" +msgstr "" + +#. Tag: para +#: hardware.xml:1832 +#, 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:1842 +#, 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. You can prevent this issue by blacklisting the " +"wrong driver module as described in <xref linkend=\"module-blacklist\"/>." +msgstr "" + +#. Tag: para +#: hardware.xml:1850 +#, no-c-format +msgid "" +"An alternative solution during the installation 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>. Note that " +"the wrong module may then still be loaded when the system is rebooted." +msgstr "" + +#. Tag: title +#: hardware.xml:1863 +#, no-c-format +msgid "Sun B100 blade" +msgstr "" + +#. Tag: para +#: hardware.xml:1865 +#, no-c-format +msgid "" +"The <literal>cassini</literal> network driver does not work with Sun B100 " +"blade systems." +msgstr "" + +#. Tag: title +#: hardware.xml:1880 +#, no-c-format +msgid "Braille Displays" +msgstr "" + +#. Tag: para +#: hardware.xml:1881 +#, no-c-format +msgid "" +"Support for braille displays is determined by the underlying support found " +"in <classname>brltty</classname>. Most displays work under " +"<classname>brltty</classname>, connected via either a serial port, USB or " +"bluetooth. Details on supported braille devices can be found on the <ulink " +"url=\"&url-brltty;\"><classname>brltty</classname> website</ulink>. &debian-" +"gnu; &release; ships with <classname>brltty</classname> version &brlttyver;." +msgstr "" + +#. Tag: title +#: hardware.xml:1895 +#, no-c-format +msgid "Hardware Speech Synthesis" +msgstr "" + +#. Tag: para +#: hardware.xml:1896 +#, no-c-format +msgid "" +"Support for hardware speech synthesis devices is determined by the " +"underlying support found in <classname>speakup</classname>. " +"<classname>speakup</classname> only supports integrated boards and external " +"devices connected to a serial port (no USB, serial-to-USB or PCI adapters " +"are supported). Details on supported hardware speech synthesis devices can " +"be found on the <ulink url=\"&url-speakup;\"><classname>speakup</classname> " +"website</ulink>. &debian-gnu; &release; ships with <classname>speakup</" +"classname> version &speakupver;." +msgstr "" + +#. Tag: title +#: hardware.xml:1916 +#, no-c-format +msgid "Peripherals and Other Hardware" +msgstr "" + +#. Tag: para +#: hardware.xml:1917 +#, no-c-format +msgid "" +"&arch-kernel; supports a large variety of hardware devices such as mice, " +"printers, scanners, PCMCIA/CardBus/ExpressCard and USB devices. However, " +"most of these devices are not required while installing the system." +msgstr "" + +#. Tag: para +#: hardware.xml:1923 +#, no-c-format +msgid "" +"USB hardware generally works fine. On some very old PC systems some USB " +"keyboards may require additional configuration (see <xref linkend=\"hardware-" +"issues\"/>). On modern PCs, USB keyboards and mice work without requiring " +"any specific configuration." +msgstr "" + +#. Tag: para +#: hardware.xml:1932 +#, 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: title +#: hardware.xml:1945 +#, no-c-format +msgid "Devices Requiring Firmware" +msgstr "" + +#. Tag: para +#: hardware.xml:1946 +#, no-c-format +msgid "" +"Besides the availability of a device driver, some hardware also requires so-" +"called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> " +"to be loaded into the device before it can become operational. This is most " +"common for network interface cards (especially wireless NICs), but for " +"example some USB devices and even some hard disk controllers also require " +"firmware. With many graphics cards, basic functionality is available without " +"additional firmware, but the use of advanced features requires an " +"appropriate firmware file to be installed in the system." +msgstr "" + +#. Tag: para +#: hardware.xml:1957 +#, no-c-format +msgid "" +"On many older devices which require firmware to work, the firmware file was " +"permanently placed in an EEPROM/Flash chip on the device itself by the " +"manufacturer. Nowadays most new devices do not have the firmware embedded " +"this way anymore, so the firmware file must be uploaded into the device by " +"the host operating system every time the system boots." +msgstr "" + +#. Tag: para +#: hardware.xml:1965 +#, no-c-format +msgid "" +"In most cases firmware is non-free according to the criteria used by the " +"&debian-gnu; project and thus cannot be included in the main distribution or " +"in the installation system. If the device driver itself is included in the " +"distribution and if &debian-gnu; legally can distribute the firmware, it " +"will often be available as a separate package from the non-free section of " +"the archive." +msgstr "" + +#. Tag: para +#: hardware.xml:1974 +#, no-c-format +msgid "" +"However, this does not mean that such hardware cannot be used during an " +"installation. Starting with &debian-gnu; 5.0, &d-i; supports loading " +"firmware files or packages containing firmware from a removable medium, such " +"as a USB stick. See <xref linkend=\"loading-firmware\"/> for detailed " +"information on how to load firmware files or packages during the " +"installation." +msgstr "" + +#. Tag: para +#: hardware.xml:1983 +#, no-c-format +msgid "" +"If the &d-i; prompts for a firmware file and you do not have this firmware " +"file available or do not want to install a non-free firmware file on your " +"system, you can try to proceed without loading the firmware. There are " +"several cases where a driver prompts for additional firmware because it may " +"be needed under certain circumstances, but the device does work without it " +"on most systems (this e.g. happens with certain network cards using the tg3 " +"driver)." +msgstr "" + +#. Tag: title +#: hardware.xml:2000 +#, no-c-format +msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" +msgstr "" + +#. Tag: para +#: hardware.xml:2002 +#, 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:2010 +#, 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:2018 +#, no-c-format +msgid "" +"Whether or not you are purchasing a system with &arch-kernel; bundled, or " +"even a used system, it is still important to check that your hardware is " +"supported by the &arch-kernel; kernel. Check if your hardware is listed in " +"the references found above. Let your salesperson (if any) know that you're " +"shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware " +"vendors." +msgstr "" + +#. Tag: title +#: hardware.xml:2029 +#, no-c-format +msgid "Avoid Proprietary or Closed Hardware" +msgstr "" + +#. Tag: para +#: hardware.xml:2030 +#, 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 driver's " +"source code, which is one of the central elements of free software. Since we " +"haven't been granted access to usable documentation on these devices, they " +"simply won't work under &arch-kernel;." +msgstr "" + +#. Tag: para +#: hardware.xml:2040 +#, no-c-format +msgid "" +"In many cases there are standards (or at least some de-facto standards) " +"describing how an operating system and its device drivers communicate with a " +"certain class of devices. All devices which comply to such a (de-" +"facto-)standard can be used with a single generic device driver and no " +"device-specific drivers are required. With some kinds of hardware (e.g. USB " +"<quote>Human Interface Devices</quote>, i.e. keyboards, mice, etc., and USB " +"mass storage devices like USB flash disks and memory card readers) this " +"works very well and practically every device sold in the market is standards-" +"compliant." +msgstr "" + +#. Tag: para +#: hardware.xml:2052 +#, no-c-format +msgid "" +"In other fields, among them e.g. printers, this is unfortunately not the " +"case. While there are many printers which can be addressed via a small set " +"of (de-facto-)standard control languages and therefore can be made to work " +"without problems in any operating system, there are quite a few models which " +"only understand proprietary control commands for which no usable " +"documentation is available and therefore either cannot be used at all on " +"free operating systems or can only be used with a vendor-supplied closed-" +"source driver." +msgstr "" + +#. Tag: para +#: hardware.xml:2063 +#, no-c-format +msgid "" +"Even if there is a vendor-provided closed-source driver for such hardware " +"when purchasing the device, the practical lifespan of the device is limited " +"by driver availability. Nowadays product cycles have become short and it is " +"not uncommon that a short time after a consumer device has ceased " +"production, no driver updates get made available any more by the " +"manufacturer. If the old closed-source driver does not work anymore after a " +"system update, an otherwise perfectly working device becomes unusable due to " +"lacking driver support and there is nothing that can be done in this case. " +"You should therefore avoid buying closed hardware in the first place, " +"regardless of the operating system you want to use it with." +msgstr "" + +#. Tag: para +#: hardware.xml:2076 +#, no-c-format +msgid "" +"You can help improve this situation by encouraging manufacturers of closed " +"hardware to release the documentation and other resources necessary for us " +"to provide free drivers for their hardware." +msgstr "" + +#. Tag: title +#: hardware.xml:2091 +#, no-c-format +msgid "Installation Media" +msgstr "" + +#. Tag: para +#: hardware.xml:2093 +#, no-c-format +msgid "" +"This section will help you determine which different media types you can use " +"to install &debian;. There is a whole chapter devoted to media, <xref " +"linkend=\"install-methods\"/>, which lists the advantages and disadvantages " +"of each media type. You may want to refer back to this page once you reach " +"that section." +msgstr "" + +#. Tag: title +#: hardware.xml:2103 +#, no-c-format +msgid "CD-ROM/DVD-ROM/BD-ROM" +msgstr "" + +#. Tag: para +#: hardware.xml:2105 +#, no-c-format +msgid "Installation from optical disc is supported for most architectures." +msgstr "" + +#. Tag: para +#: hardware.xml:2109 +#, no-c-format +msgid "" +"On PCs SATA, IDE/ATAPI, USB and SCSI optical drives are supported, as are " +"FireWire devices that are supported by the ohci1394 and sbp2 drivers." +msgstr "" + +#. Tag: title +#: hardware.xml:2126 +#, no-c-format +msgid "USB Memory Stick" +msgstr "" + +#. Tag: para +#: hardware.xml:2128 +#, no-c-format +msgid "" +"USB flash disks a.k.a. USB memory sticks have become a commonly used and " +"cheap storage device. Most modern computer systems also allow booting the &d-" +"i; from such a stick. Many modern computer systems, in particular netbooks " +"and thin laptops, do not have an optical drive anymore at all and booting " +"from USB media is the standard way of installing a new operating system on " +"them." +msgstr "" + +#. Tag: title +#: hardware.xml:2140 +#, no-c-format +msgid "Network" +msgstr "" + +#. Tag: para +#: hardware.xml:2142 +#, no-c-format +msgid "" +"The network can be used during the installation 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 connections (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:2152 +#, no-c-format +msgid "" +"You can also <emphasis>boot</emphasis> the installation system over the " +"network without needing any local media like CDs/DVDs or USB sticks. If you " +"already have a netboot-infrastructure available (i.e. you are already " +"running DHCP and TFTP services in your network), this allows an easy and " +"fast deployment of a large number of machines. Setting up the necessary " +"infrastructure requires a certain level of technical experience, so this is " +"not recommended for novice users. <phrase arch=\"mips;mipsel;mips64el\">This " +"is the preferred installation technique for &arch-title;.</phrase>" +msgstr "" + +#. Tag: para +#: hardware.xml:2165 +#, no-c-format +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:2174 +#, no-c-format +msgid "Hard Disk" +msgstr "" + +#. Tag: para +#: hardware.xml:2176 +#, no-c-format +msgid "" +"Booting the installation system directly from a hard disk is another option " +"for many architectures. This will require some other operating system to " +"load the installer onto the hard disk. This method is only recommended for " +"special cases when no other installation method is available." +msgstr "" + +#. Tag: para +#: hardware.xml:2183 +#, no-c-format +msgid "" +"Although the &arch-title; does not allow booting from SunOS (Solaris), you " +"can install from a SunOS partition (UFS slices)." +msgstr "" + +#. Tag: title +#: hardware.xml:2192 +#, no-c-format +msgid "Un*x or GNU system" +msgstr "" + +#. Tag: para +#: hardware.xml:2194 +#, no-c-format +msgid "" +"If you are running another Unix-like system, you could use it to install " +"&debian-gnu; 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\"/>. This " +"installation method is only recommended for advanced users when no other " +"installation method is available." +msgstr "" + +#. Tag: title +#: hardware.xml:2207 +#, no-c-format +msgid "Supported Storage Systems" +msgstr "" + +#. Tag: para +#: hardware.xml:2209 +#, no-c-format +msgid "" +"The &debian; installer contains a kernel which is built to maximize the " +"number of systems it runs on." +msgstr "" + +#. Tag: para +#: hardware.xml:2213 +#, no-c-format +msgid "" +"Generally, the &debian; installation system includes support for IDE (also " +"known as PATA) drives, SATA and 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:2230 +#, 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:2275 +#, no-c-format +msgid "" +"Any storage system supported by the Linux kernel is also supported by the " +"boot system." +msgstr "" + +#. Tag: para +#: hardware.xml:2280 +#, 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:2297 +#, no-c-format +msgid "Memory and Disk Space Requirements" +msgstr "" + +#. Tag: para +#: hardware.xml:2299 +#, no-c-format +msgid "" +"You must have at least &minimum-memory; of memory and &minimum-fs-size; of " +"hard disk space to perform a normal installation. Note that these are fairly " +"minimal numbers. For more realistic figures, see <xref linkend=\"minimum-" +"hardware-reqts\"/>." +msgstr "" + +#. Tag: para +#: hardware.xml:2306 +#, no-c-format +msgid "" +"Installation on systems with less memory<footnote condition=\"gtk\"> <para> " +"Installation images that support the graphical installer require more memory " +"than images that support only the textual installer and should not be used " +"on systems with less than &minimum-memory; of memory. If there is a choice " +"between booting the text-based and the graphical installer, the former " +"should be selected on such systems. </para> </footnote> or disk space " +"available may be possible but is only advised for experienced users." +msgstr "" diff --git a/po/kab/install-methods.po b/po/kab/install-methods.po new file mode 100644 index 000000000..cfe00a269 --- /dev/null +++ b/po/kab/install-methods.po @@ -0,0 +1,1491 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-install-methods 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-12-02 23: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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: install-methods.xml:5 +#, no-c-format +msgid "Obtaining System Installation Media" +msgstr "" + +#. Tag: title +#: install-methods.xml:12 +#, no-c-format +msgid "Official &debian-gnu; installation images" +msgstr "" + +#. Tag: para +#: install-methods.xml:13 +#, no-c-format +msgid "" +"By far the easiest way to install &debian-gnu; is from a set of official " +"&debian; installation images. You can buy a set of CDs/DVDs from a vendor " +"(see the <ulink url=\"&url-debian-cd-vendors;\">CD vendors page</ulink>). " +"You may also download the installation images from a &debian; mirror and " +"make your own set, if you have a fast network connection and a CD/DVD burner " +"(see the <ulink url=\"&url-debian-cd;\">Debian CD/DVD page</ulink> and " +"<ulink url=\"&url-debian-cd-faq;\">Debian CD FAQ</ulink> for detailed " +"instructions). If you have such optical installation media, and they are " +"bootable on your machine<phrase arch=\"x86\">, which is the case on all " +"modern PCs</phrase>, you can skip right to <xref linkend=\"boot-installer\"/" +">. Much effort has been expended to ensure the most-used files are on the " +"first CD and DVD image, so that a basic desktop installation can be done " +"with only the first DVD or - to a limited extent - even with only the first " +"CD image." +msgstr "" + +#. Tag: para +#: install-methods.xml:30 +#, no-c-format +msgid "" +"As CDs have a rather limited capacity by today's standards, not all " +"graphical desktop environments are installable with only the first CD; for " +"some desktop environments a CD installation requires either network " +"connectivity during the installation to download the remaining files or " +"additional CDs." +msgstr "" + +#. Tag: para +#: install-methods.xml:38 +#, no-c-format +msgid "" +"Also, keep in mind: if the installation media you are using don't contain " +"some packages you need, you can always install those packages afterwards " +"from your running new Debian system (after the installation has finished). " +"If you need to know on which installation image to find a specific package, " +"visit <ulink url=\"https://cdimage-search.debian.org/\">https://cdimage-" +"search.debian.org/</ulink>." +msgstr "" + +#. Tag: para +#: install-methods.xml:46 +#, no-c-format +msgid "" +"If your machine doesn't support booting from optical media<phrase arch=" +"\"x86\"> (only relevant on very old PC systems)</phrase>, but you do have a " +"set of CD/DVD, you can use an alternative strategy such as <phrase arch=" +"\"s390\">VM reader,</phrase> <phrase condition=\"bootable-disk\">hard disk,</" +"phrase> <phrase condition=\"bootable-usb\">usb stick,</phrase> <phrase " +"condition=\"supports-tftp\">net boot,</phrase> or manually loading the " +"kernel from the disc to initially boot the system installer. The files you " +"need for booting by another means are also on the disc; the &debian; network " +"archive and folder organization on the disc are identical. So when archive " +"file paths are given below for particular files you need for booting, look " +"for those files in the same directories and subdirectories on your " +"installation media." +msgstr "" + +#. Tag: para +#: install-methods.xml:67 +#, no-c-format +msgid "" +"Once the installer is booted, it will be able to obtain all the other files " +"it needs from the disc." +msgstr "" + +#. Tag: para +#: install-methods.xml:72 +#, no-c-format +msgid "" +"If you don't have an installation media set, then you will need to download " +"the installer system files and place them on the <phrase arch=\"s390\">VM " +"minidisk</phrase> <phrase condition=\"bootable-disk\">hard disk or</phrase> " +"<phrase condition=\"bootable-usb\">usb stick or</phrase> <phrase condition=" +"\"supports-tftp\">a connected computer</phrase> so they can be used to boot " +"the installer." +msgstr "" + +#. Tag: title +#: install-methods.xml:96 +#, no-c-format +msgid "Downloading Files from &debian; Mirrors" +msgstr "" + +#. Tag: para +#: install-methods.xml:98 +#, no-c-format +msgid "" +"To find the nearest (and thus probably the fastest) mirror, see the <ulink " +"url=\"&url-debian-mirrors;\">list of &debian; mirrors</ulink>." +msgstr "" + +#. Tag: title +#: install-methods.xml:106 +#, no-c-format +msgid "Where to Find Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:108 +#, no-c-format +msgid "" +"Various installation files can be found on each &debian; mirror in the " +"directory <ulink url=\"&url-debian-installer;images\">debian/dists/" +"&releasename;/main/installer-&architecture;/current/images/</ulink> — " +"the <ulink url=\"&url-debian-installer;images/MANIFEST\">MANIFEST</ulink> " +"lists each image and its purpose." +msgstr "" + +#. Tag: title +#: install-methods.xml:120 +#, no-c-format +msgid "Kurobox Pro Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:121 +#, no-c-format +msgid "" +"The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the " +"disk on which you intend to install &debian;. These images can be obtained " +"from &kuroboxpro-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:131 +#, no-c-format +msgid "HP mv2120 Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:132 +#, no-c-format +msgid "" +"A firmware image is provided for the HP mv2120 which will automatically boot " +"<classname>debian-installer</classname>. This image can be installed with " +"uphpmvault on Linux and other systems and with the HP Media Vault Firmware " +"Recovery Utility on Windows. The firmware image can be obtained from &mv2120-" +"firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:144 +#, no-c-format +msgid "QNAP Turbo Station Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:145 +#, no-c-format +msgid "" +"The installation files for the QNAP Turbo Station consist of a kernel and " +"ramdisk as well as a script to write these images to flash. You can obtain " +"the installation files for QNAP TS-11x/TS-12x, HS-210, TS-21x/TS-22x and " +"TS-41x/TS-42x models from &qnap-kirkwood-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:156 +#, no-c-format +msgid "Plug Computer and OpenRD Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:157 +#, no-c-format +msgid "" +"The installation files for plug computers (SheevaPlug, GuruPlug, DreamPlug " +"etc) and OpenRD devices consist of a kernel and initrd for U-Boot. You can " +"obtain these files from &kirkwood-marvell-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:167 +#, no-c-format +msgid "LaCie NASes Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:168 +#, no-c-format +msgid "" +"The installation files for LaCie NASes (Network Space v2, Network Space Max " +"v2, Internet Space v2, d2 Network v2, 2Big Network v2 and 5Big Network v2) " +"consist of a kernel and initrd for U-Boot. You can obtain these files from " +"&lacie-kirkwood-firmware-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:179 +#, no-c-format +msgid "Armhf Multiplatform Installation Files" +msgstr "" + +#. Tag: para +#: install-methods.xml:180 +#, no-c-format +msgid "" +"The installation files for systems supported by the armhf multiplatform " +"kernel (see <xref linkend=\"armhf-armmp-supported-platforms\"/>) consist of " +"a standard Linux kernel image, a standard Linux initial ramdisk image and a " +"system-specific device-tree blob. The kernel and the initial ramdisk image " +"for tftp-booting can be obtained from &armmp-firmware-img; and the device-" +"tree blob can be obtained from &armmp-dtb-img;. The tar archive for creating " +"a bootable USB stick with the installer can be obtained from &armmp-hd-media-" +"tarball;." +msgstr "" + +#. Tag: para +#: install-methods.xml:192 +#, no-c-format +msgid "" +"U-boot images for various armhf platforms are available at &armmp-uboot-img;." +msgstr "" + +#. Tag: title +#: install-methods.xml:238 +#, no-c-format +msgid "Preparing Files for USB Memory Stick Booting" +msgstr "" + +#. Tag: para +#: install-methods.xml:240 +#, no-c-format +msgid "" +"To prepare the USB stick, we recommend to use a system where GNU/Linux is " +"already running and where USB is supported. With current GNU/Linux systems " +"the USB stick should be automatically recognized when you insert it. If it " +"is not you should check that the usb-storage kernel module is loaded. When " +"the USB stick is inserted, it will be mapped to a device named <filename>/" +"dev/sdX</filename>, where the <quote>X</quote> is a letter in the range a-z. " +"You should be able to see to which device the USB stick was mapped by " +"running the command <command>dmesg</command> after inserting it. To write to " +"your stick, you may have to turn off its write protection switch." +msgstr "" + +#. Tag: para +#: install-methods.xml:253 +#, no-c-format +msgid "" +"The procedures described in this section will destroy anything already on " +"the device! Make very sure that you use the correct device name for your USB " +"stick. If you use the wrong device the result could be that all information " +"on for example a hard disk could be lost." +msgstr "" + +#. Tag: title +#: install-methods.xml:263 +#, no-c-format +msgid "Preparing a USB stick using a hybrid CD/DVD image" +msgstr "" + +#. Tag: para +#: install-methods.xml:264 +#, no-c-format +msgid "" +"Debian installation images can now be written directly to a USB stick, which " +"is a very easy way to make a bootable USB stick. Simply choose an image " +"(such as the netinst, CD, DVD-1, or netboot) that will fit on your USB " +"stick. See <xref linkend=\"official-cdrom\"/> to get an installation image." +msgstr "" + +#. Tag: para +#: install-methods.xml:272 +#, no-c-format +msgid "" +"Alternatively, for very small USB sticks, only a few megabytes in size, you " +"can download the &netboot-mini-iso; image from the <filename>netboot</" +"filename> directory (at the location mentioned in <xref linkend=\"where-files" +"\"/>)." +msgstr "" + +#. Tag: para +#: install-methods.xml:279 +#, no-c-format +msgid "" +"The installation image you choose should be written directly to the USB " +"stick, overwriting its current contents. For example, when using an existing " +"GNU/Linux system, the image file can be written to a USB stick as follows, " +"after having made sure that the stick is unmounted: " +"<informalexample><screen>\n" +"<prompt>#</prompt> <userinput>cp <replaceable>debian.iso</replaceable> /dev/" +"<replaceable>sdX</replaceable></userinput>\n" +"<prompt>#</prompt> <userinput>sync</userinput>\n" +"</screen></informalexample> Information about how to do this on other " +"operating systems can be found in the <ulink url=\"&url-debian-cd-faq-write-" +"usb;\">Debian CD FAQ</ulink>." +msgstr "" + +#. Tag: para +#: install-methods.xml:291 +#, no-c-format +msgid "" +"The image must be written to the whole-disk device and not a partition, e." +"g. /dev/sdb and not /dev/sdb1. Do not use tools like <command>unetbootin</" +"command> which alter the image." +msgstr "" + +#. Tag: para +#: install-methods.xml:297 +#, no-c-format +msgid "" +"Simply writing the installation image to USB like this should work fine for " +"most users. The other options below are more complex, mainly for people with " +"specialised needs." +msgstr "" + +#. Tag: para +#: install-methods.xml:305 +#, no-c-format +msgid "" +"The hybrid image on the stick does not occupy all the storage space, so it " +"may be worth considering using the free space to hold firmware files or " +"packages or any other files of your choice. This could be useful if you have " +"only one stick or just want to keep everything you need on one device." +msgstr "" + +#. Tag: para +#: install-methods.xml:313 +#, no-c-format +msgid "" +"Create a second, FAT partition on the stick, mount the partition and copy or " +"unpack the firmware onto it. For example:" +msgstr "" + +#. Tag: screen +#: install-methods.xml:318 +#, no-c-format +msgid "" +"# mount /dev/<replaceable>sdX2</replaceable> /mnt\n" +"# cd /mnt\n" +"# tar zxvf <replaceable>/path/to/</replaceable>firmware.tar.gz\n" +"# cd /\n" +"# umount /mnt" +msgstr "" + +#. Tag: para +#: install-methods.xml:320 +#, no-c-format +msgid "" +"You might have written the <filename>mini.iso</filename> to the USB stick. " +"In this case the second partition doesn't have to be created as, very " +"nicely, it will already be present. Unplugging and replugging the USB stick " +"should make the two partitions visible." +msgstr "" + +#. Tag: title +#: install-methods.xml:334 +#, no-c-format +msgid "Manually copying files to the USB stick" +msgstr "" + +#. Tag: para +#: install-methods.xml:335 +#, no-c-format +msgid "" +"An alternative way to set up your USB stick is to manually copy the " +"installer files, and also an installation image to it. Note that the USB " +"stick should be at least 1 GB in size (smaller setups are possible if you " +"follow <xref linkend=\"usb-copy-flexible\"/>)." +msgstr "" + +#. Tag: para +#: install-methods.xml:342 +#, no-c-format +msgid "" +"There is an all-in-one file &hdmedia-boot-img; which contains all the " +"installer files (including the kernel) <phrase arch=\"x86\">as well as " +"<classname>syslinux</classname> and its configuration file</phrase> <phrase " +"arch=\"powerpc\">as well as <classname>yaboot</classname> and its " +"configuration file</phrase>." +msgstr "" + +#. Tag: para +#: install-methods.xml:351 +#, no-c-format +msgid "" +"Note that, although convenient, this method does have one major " +"disadvantage: the logical size of the device will be limited to 1 GB, even " +"if the capacity of the USB stick is larger. You will need to repartition the " +"USB stick and create new file systems to get its full capacity back if you " +"ever want to use it for some different purpose." +msgstr "" + +#. Tag: para +#: install-methods.xml:359 +#, no-c-format +msgid "To use this image simply extract it directly to your USB stick:" +msgstr "" + +#. Tag: screen +#: install-methods.xml:363 +#, no-c-format +msgid "# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable>" +msgstr "" + +#. Tag: para +#: install-methods.xml:365 +#, no-c-format +msgid "" +"Create a partition of type \"Apple_Bootstrap\" on your USB stick using " +"<command>mac-fdisk</command>'s <userinput>C</userinput> command and extract " +"the image directly to that:" +msgstr "" + +#. Tag: screen +#: install-methods.xml:371 +#, no-c-format +msgid "# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable>" +msgstr "" + +#. Tag: para +#: install-methods.xml:373 +#, no-c-format +msgid "" +"After that, mount the USB memory stick <phrase arch=" +"\"x86\">(<userinput>mount /dev/<replaceable>sdX</replaceable> /mnt</" +"userinput>),</phrase> <phrase arch=\"powerpc\">(<userinput>mount /dev/" +"<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> which will now " +"have <phrase arch=\"x86\">a FAT filesystem</phrase> <phrase arch=\"powerpc" +"\">an HFS filesystem</phrase> on it, and copy a &debian; ISO image (netinst " +"or full CD/DVD) to it. Unmount the stick (<userinput>umount /mnt</" +"userinput>) and you are done." +msgstr "" + +#. Tag: title +#: install-methods.xml:390 +#, no-c-format +msgid "Manually copying files to the USB stick — the flexible way" +msgstr "" + +#. Tag: para +#: install-methods.xml:391 +#, no-c-format +msgid "" +"If you like more flexibility or just want to know what's going on, you " +"should use the following method to put the files on your stick. One " +"advantage of using this method is that — if the capacity of your USB " +"stick is large enough — you have the option of copying any ISO image, " +"even a DVD image, to it." +msgstr "" + +#. Tag: title +#: install-methods.xml:406 install-methods.xml:528 +#, no-c-format +msgid "Partitioning the USB stick" +msgstr "" + +#. Tag: para +#: install-methods.xml:407 +#, no-c-format +msgid "" +"We will show how to set up the memory stick to use the first partition, " +"instead of the entire device." +msgstr "" + +#. Tag: para +#: install-methods.xml:412 +#, no-c-format +msgid "" +"Since most USB sticks come pre-configured with a single FAT16 partition, you " +"probably won't have to repartition or reformat the stick. If you have to do " +"that anyway, use <command>cfdisk</command> or any other partitioning tool to " +"create a FAT16 partition<footnote> <para> Don't forget to set the " +"<quote>bootable</quote> bootable flag. </para> </footnote>, install an MBR " +"using: <informalexample><screen>\n" +"# install-mbr /dev/<replaceable>sdX</replaceable>\n" +"</screen></informalexample> The <command>install-mbr</command> command is " +"contained in the <classname>mbr</classname> &debian; package. Then create " +"the filesystem using: <informalexample><screen>\n" +"# mkdosfs /dev/<replaceable>sdX1</replaceable>\n" +"</screen></informalexample> Take care that you use the correct device name " +"for your USB stick. The <command>mkdosfs</command> command is contained in " +"the <classname>dosfstools</classname> &debian; package." +msgstr "" + +#. Tag: para +#: install-methods.xml:436 +#, 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. Although any boot loader should work, it's " +"convenient to use <classname>syslinux</classname>, since it uses a FAT16 " +"partition and can be reconfigured by just editing a text file. Any operating " +"system which supports the FAT file system can be used to make changes to the " +"configuration of the boot loader." +msgstr "" + +#. Tag: para +#: install-methods.xml:446 +#, no-c-format +msgid "" +"To put <classname>syslinux</classname> on the FAT16 partition on your USB " +"stick, install the <classname>syslinux</classname> and <classname>mtools</" +"classname> packages on your system, and do: <informalexample><screen>\n" +"# syslinux /dev/<replaceable>sdX1</replaceable>\n" +"</screen></informalexample> Again, take care that you use the correct device " +"name. The partition must not be mounted when starting <command>syslinux</" +"command>. This procedure writes a boot sector to the partition and creates " +"the file <filename>ldlinux.sys</filename> which contains the boot loader " +"code." +msgstr "" + +#. Tag: title +#: install-methods.xml:463 install-methods.xml:575 +#, no-c-format +msgid "Adding the installer image" +msgstr "" + +#. Tag: para +#: install-methods.xml:464 +#, no-c-format +msgid "" +"Mount the partition (<userinput>mount /dev/<replaceable>sdX1</replaceable> /" +"mnt</userinput>) and copy the following installer image files to the stick: " +"<itemizedlist> <listitem><para> <filename>vmlinuz</filename> or " +"<filename>linux</filename> (kernel binary) </para></listitem> " +"<listitem><para> <filename>initrd.gz</filename> (initial ramdisk image) </" +"para></listitem> </itemizedlist> You can choose between either the text-" +"based or the graphical version of the installer. The latter can be found in " +"the <filename>gtk</filename> subdirectory. If you want to rename the files, " +"please note that <classname>syslinux</classname> can only process DOS (8.3) " +"file names." +msgstr "" + +#. Tag: para +#: install-methods.xml:488 +#, no-c-format +msgid "" +"Next you should create a <filename>syslinux.cfg</filename> configuration " +"file, which at a bare minimum should contain the following line (change the " +"name of the kernel binary to <quote><filename>linux</filename></quote> if " +"you used a <filename>netboot</filename> image): <informalexample><screen>\n" +"default vmlinuz initrd=initrd.gz\n" +"</screen></informalexample> For the graphical installer you should add " +"<userinput>vga=788</userinput> to the line. Other parameters can be appended " +"as desired." +msgstr "" + +#. Tag: para +#: install-methods.xml:500 +#, no-c-format +msgid "" +"To enable the boot prompt to permit further parameter appending, add a " +"<userinput>prompt 1</userinput> line." +msgstr "" + +#. Tag: para +#: install-methods.xml:505 +#, no-c-format +msgid "" +"If you used an <filename>hd-media</filename> image, you should now copy the " +"ISO file of a &debian; ISO image<footnote> <para> You can use either a " +"netinst or a full CD/DVD image (see <xref linkend=\"official-cdrom\"/>). Be " +"sure to select one that fits. Note that the <quote>netboot <filename>mini." +"iso</filename></quote> image is not usable for this purpose. </para> </" +"footnote> onto the stick. When you are done, unmount the USB memory stick " +"(<userinput>umount /mnt</userinput>)." +msgstr "" + +#. Tag: para +#: install-methods.xml:529 +#, 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/<replaceable>sdX</replaceable></" +"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" +"$ hformat /dev/<replaceable>sdX2</replaceable>\n" +"</screen></informalexample> Take care that you use the correct device name " +"for your USB stick. The <command>hformat</command> command is contained in " +"the <classname>hfsutils</classname> &debian; package." +msgstr "" + +#. Tag: para +#: install-methods.xml:546 +#, 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:555 +#, 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" +"$ hmount /dev/<replaceable>sdX2</replaceable>\n" +"$ hcopy -r /usr/lib/yaboot/yaboot :\n" +"$ hattrib -c UNIX -t tbxi :yaboot\n" +"$ hattrib -b :\n" +"$ humount\n" +"</screen></informalexample> Again, take care that you use the correct device " +"name. The partition must not be otherwise mounted during this procedure. " +"This procedure writes the boot loader to the partition, and uses the HFS " +"utilities to mark it in such a way that Open Firmware will boot it. Having " +"done this, the rest of the USB stick may be prepared using the normal Unix " +"utilities." +msgstr "" + +#. Tag: para +#: install-methods.xml:576 +#, no-c-format +msgid "" +"Mount the partition (<userinput>mount /dev/<replaceable>sdX2</replaceable> /" +"mnt</userinput>) and copy the following installer image files to the stick:" +msgstr "" + +#. Tag: para +#: install-methods.xml:583 +#, no-c-format +msgid "<filename>vmlinux</filename> (kernel binary)" +msgstr "" + +#. Tag: para +#: install-methods.xml:588 +#, no-c-format +msgid "<filename>initrd.gz</filename> (initial ramdisk image)" +msgstr "" + +#. Tag: para +#: install-methods.xml:593 +#, no-c-format +msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" +msgstr "" + +#. Tag: para +#: install-methods.xml:598 +#, no-c-format +msgid "<filename>boot.msg</filename> (optional boot message)" +msgstr "" + +#. Tag: para +#: install-methods.xml:605 +#, no-c-format +msgid "" +"The <filename>yaboot.conf</filename> configuration file should contain the " +"following lines: <informalexample><screen>\n" +"default=install\n" +"root=/dev/ram\n" +"\n" +"message=/boot.msg\n" +"\n" +"image=/vmlinux\n" +" label=install\n" +" initrd=/initrd.gz\n" +" initrd-size=10000\n" +" read-only\n" +"</screen></informalexample> Please note that the <userinput>initrd-size</" +"userinput> parameter may need to be increased, depending on the image you " +"are booting." +msgstr "" + +#. Tag: para +#: install-methods.xml:615 +#, no-c-format +msgid "" +"If you used an <filename>hd-media</filename> image, you should now copy the " +"ISO file of a &debian; ISO image<footnote> <para> You can use either a " +"netinst or a full CD image (see <xref linkend=\"official-cdrom\"/>). Be sure " +"to select one that fits. Note that the <quote>netboot <filename>mini.iso</" +"filename></quote> image is not usable for this purpose. </para> </footnote> " +"onto the stick. When you are done, unmount the USB memory stick " +"(<userinput>umount /mnt</userinput>)." +msgstr "" + +#. Tag: title +#: install-methods.xml:643 +#, no-c-format +msgid "Preparing Files for Hard Disk Booting" +msgstr "" + +#. Tag: para +#: install-methods.xml:644 +#, 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. On modern UEFI systems, the " +"kernel may be booted directly from the UEFI partition without the need of a " +"boot loader." +msgstr "" + +#. Tag: para +#: install-methods.xml:652 +#, 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/DVD images." +msgstr "" + +#. Tag: para +#: install-methods.xml:658 +#, 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:669 +#, 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:678 +#, no-c-format +msgid "Hard disk installer booting from Linux using <command>GRUB</command>" +msgstr "" + +#. Tag: para +#: install-methods.xml:680 +#, no-c-format +msgid "" +"This section explains how to add to or even replace an existing linux " +"installation using <command>GRUB</command>." +msgstr "" + +#. Tag: para +#: install-methods.xml:686 +#, no-c-format +msgid "" +"At boot time, <command>GRUB</command> supports loading in memory not only " +"the kernel, but also a disk image. This RAM disk can be used as the root " +"file-system by the kernel." +msgstr "" + +#. Tag: para +#: install-methods.xml:692 +#, 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:699 +#, no-c-format +msgid "<filename>vmlinuz</filename> (kernel binary)" +msgstr "" + +#. Tag: para +#: install-methods.xml:704 +#, no-c-format +msgid "<filename>initrd.gz</filename> (ramdisk image)" +msgstr "" + +#. Tag: para +#: install-methods.xml:711 +#, 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 &x86-netboot-initrd; " +"file and its corresponding kernel &x86-netboot-linux;. This will allow you " +"to repartition the hard disk from which you boot the installer, although you " +"should do so with care." +msgstr "" + +#. Tag: para +#: install-methods.xml:720 +#, no-c-format +msgid "" +"Alternatively, if you intend to keep an existing partition on the hard drive " +"unchanged during the install, you can download the &x86-hdmedia-initrd; file " +"and its kernel &x86-hdmedia-vmlinuz;, as well as copy an installation image " +"to the hard drive (make sure the file is named ending in <literal>.iso</" +"literal>). The installer can then boot from the hard drive and install from " +"the installation image, without needing the network." +msgstr "" + +#. Tag: para +#: install-methods.xml:728 +#, no-c-format +msgid "" +"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd" +"\"/>." +msgstr "" + +#. Tag: title +#: install-methods.xml:738 +#, no-c-format +msgid "Hard disk installer booting from DOS using <command>loadlin</command>" +msgstr "" + +#. Tag: para +#: install-methods.xml:739 +#, no-c-format +msgid "" +"This section explains how to prepare your hard drive for booting the " +"installer from DOS using <command>loadlin</command>." +msgstr "" + +#. Tag: para +#: install-methods.xml:744 +#, no-c-format +msgid "" +"Copy the following directories from a &debian; installation image to " +"<filename>c:\\</filename>." +msgstr "" + +#. Tag: para +#: install-methods.xml:749 +#, no-c-format +msgid "" +"<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)" +msgstr "" + +#. Tag: para +#: install-methods.xml:754 +#, no-c-format +msgid "<filename>/tools</filename> (loadlin tool)" +msgstr "" + +#. Tag: title +#: install-methods.xml:866 +#, no-c-format +msgid "Preparing Files for TFTP Net Booting" +msgstr "" + +#. Tag: para +#: install-methods.xml:867 +#, 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:875 +#, no-c-format +msgid "" +"You need to set up 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:882 +#, 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> 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:896 +#, 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:902 +#, 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:907 +#, 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:915 +#, no-c-format +msgid "" +"For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. " +"It's written by the same author as the <classname>syslinux</classname> " +"bootloader and is therefore least likely to cause issues. A good alternative " +"is <classname>atftpd</classname>." +msgstr "" + +#. Tag: title +#: install-methods.xml:931 +#, no-c-format +msgid "Setting up RARP server" +msgstr "" + +#. Tag: para +#: install-methods.xml:932 +#, 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 and use the " +"command <userinput>ip addr show dev eth0</userinput>." +msgstr "" + +#. Tag: para +#: install-methods.xml:944 +#, no-c-format +msgid "" +"On a RARP server system using a Linux 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:965 +#, no-c-format +msgid "Setting up a DHCP server" +msgstr "" + +#. Tag: para +#: install-methods.xml:966 +#, no-c-format +msgid "" +"One free software DHCP server is ISC <command>dhcpd</command>. For &debian-" +"gnu;, the <classname>isc-dhcp-server</classname> package is recommended. " +"Here is a sample configuration file for it (see <filename>/etc/dhcp/dhcpd." +"conf</filename>):" +msgstr "" + +#. Tag: screen +#: install-methods.xml:973 +#, no-c-format +msgid "" +"option domain-name \"example.com\";\n" +"option domain-name-servers ns1.example.com;\n" +"option subnet-mask 255.255.255.0;\n" +"default-lease-time 600;\n" +"max-lease-time 7200;\n" +"server-name \"servername\";\n" +"\n" +"subnet 192.168.1.0 netmask 255.255.255.0 {\n" +" range 192.168.1.200 192.168.1.253;\n" +" option routers 192.168.1.1;\n" +"}\n" +"\n" +"host clientname {\n" +" filename \"/tftpboot.img\";\n" +" server-name \"servername\";\n" +" next-server servername;\n" +" hardware ethernet 01:23:45:67:89:AB;\n" +" fixed-address 192.168.1.90;\n" +"}" +msgstr "" + +#. Tag: para +#: install-methods.xml:975 +#, 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:985 +#, no-c-format +msgid "" +"After you have edited the <command>dhcpd</command> configuration file, " +"restart it with <userinput>/etc/init.d/isc-dhcp-server restart</userinput>." +msgstr "" + +#. Tag: title +#: install-methods.xml:993 +#, no-c-format +msgid "Enabling PXE Booting in the DHCP configuration" +msgstr "" + +#. Tag: para +#: install-methods.xml:994 +#, 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" +"option domain-name \"example.com\";\n" +"\n" +"default-lease-time 600;\n" +"max-lease-time 7200;\n" +"\n" +"allow booting;\n" +"allow bootp;\n" +"\n" +"# The next paragraph needs to be modified to fit your case\n" +"subnet 192.168.1.0 netmask 255.255.255.0 {\n" +" range 192.168.1.200 192.168.1.253;\n" +" option broadcast-address 192.168.1.255;\n" +"# the gateway address which can be different\n" +"# (access to the internet for instance)\n" +" option routers 192.168.1.1;\n" +"# indicate the dns you want to use\n" +" option domain-name-servers 192.168.1.3;\n" +"}\n" +"\n" +"group {\n" +" next-server 192.168.1.3;\n" +" host tftpclient {\n" +"# tftp client hardware address\n" +" hardware ethernet 00:10:DC:27:6C:15;\n" +" filename \"pxelinux.0\";\n" +" }\n" +"}\n" +"</screen></informalexample> Note that for PXE booting, the client filename " +"<filename>pxelinux.0</filename> is a boot loader, not a kernel image (see " +"<xref linkend=\"tftp-images\"/> below)." +msgstr "" + +#. Tag: para +#: install-methods.xml:1004 +#, no-c-format +msgid "" +"If your machine uses UEFI to boot, you will have to specify a boot loader " +"appropriate for UEFI machines, for example" +msgstr "" + +#. Tag: screen +#: install-methods.xml:1008 +#, no-c-format +msgid "" +"group {\n" +" next-server 192.168.1.3;\n" +" host tftpclient {\n" +"# tftp client hardware address\n" +" hardware ethernet 00:10:DC:27:6C:15;\n" +" filename \"debian-installer/amd64/bootnetx64.efi\";\n" +" }\n" +"}" +msgstr "" + +#. Tag: title +#: install-methods.xml:1021 +#, no-c-format +msgid "Setting up a BOOTP server" +msgstr "" + +#. Tag: para +#: install-methods.xml:1022 +#, 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-gnu; these are contained in the " +"<classname>bootp</classname> and <classname>isc-dhcp-server</classname> " +"packages respectively." +msgstr "" + +#. Tag: para +#: install-methods.xml:1030 +#, 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-gnu;, 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" +"bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" +"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</" +"filename> file. This has the same sort of familiar and cryptic format as the " +"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, " +"and <filename>disktab</filename> files. See the <filename>bootptab</" +"filename> manual page for more information. For CMU <command>bootpd</" +"command>, you will need to know the hardware (MAC) address of the client. " +"Here is an example <filename>/etc/bootptab</filename>: " +"<informalexample><screen>\n" +"client:\\\n" +" hd=/tftpboot:\\\n" +" bf=tftpboot.img:\\\n" +" ip=192.168.1.90:\\\n" +" sm=255.255.255.0:\\\n" +" sa=192.168.1.1:\\\n" +" ha=0123456789AB:\n" +"</screen></informalexample> You will need to change at least the <quote>ha</" +"quote> option, which specifies the hardware address of the client. The " +"<quote>bf</quote> option specifies the file a client should retrieve via " +"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=" +"\"mips\"> On SGI machines you can just enter the command monitor and type " +"<userinput>printenv</userinput>. The value of the <userinput>eaddr</" +"userinput> variable is the machine's MAC address. </phrase>" +msgstr "" + +#. Tag: para +#: install-methods.xml:1063 +#, 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\"/>. Otherwise 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 in <filename>/etc/dhcp/dhcpd." +"conf</filename>, and restart <command>dhcpd</command> with <userinput>/etc/" +"init.d/isc-dhcp-server restart</userinput>." +msgstr "" + +#. Tag: title +#: install-methods.xml:1082 +#, no-c-format +msgid "Enabling the TFTP Server" +msgstr "" + +#. Tag: para +#: install-methods.xml:1083 +#, no-c-format +msgid "" +"To get the TFTP server ready to go, you should first make sure that " +"<command>tftpd</command> is enabled." +msgstr "" + +#. Tag: para +#: install-methods.xml:1088 +#, no-c-format +msgid "" +"In the case of <classname>tftpd-hpa</classname> there are two ways the " +"service can be run. It can be started on demand by the system's " +"<classname>inetd</classname> daemon, or it can be set up to run as an " +"independent daemon. Which of these methods is used is selected when the " +"package is installed and can be changed by reconfiguring the package." +msgstr "" + +#. Tag: para +#: install-methods.xml:1097 +#, no-c-format +msgid "" +"Historically, TFTP servers used <filename>/tftpboot</filename> as directory " +"to serve images from. However, &debian-gnu; 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>/srv/tftp</filename>. You may have to adjust the " +"configuration examples in this section accordingly." +msgstr "" + +#. Tag: para +#: install-methods.xml:1107 +#, no-c-format +msgid "" +"All <command>in.tftpd</command> alternatives available in &debian; should " +"log TFTP requests to the system logs by default. Some of them support a " +"<userinput>-v</userinput> argument to increase verbosity. It is recommended " +"to check these log messages in case of boot problems as they are a good " +"starting point for diagnosing the cause of errors." +msgstr "" + +#. Tag: para +#: install-methods.xml:1115 +#, 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" +"# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n" +"</screen></informalexample> to turn off Path MTU discovery, otherwise the " +"SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets " +"are sent from a source port no greater than 32767, or the download will " +"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in " +"the PROM, and you can avoid it by setting <informalexample><screen>\n" +"# echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n" +"</screen></informalexample> to adjust the range of source ports the Linux " +"TFTP server uses." +msgstr "" + +#. Tag: title +#: install-methods.xml:1137 +#, no-c-format +msgid "Move TFTP Images Into Place" +msgstr "" + +#. Tag: para +#: install-methods.xml:1138 +#, 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:1147 +#, 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. You will need to download the following files from the " +"<filename>netboot/</filename> directory:" +msgstr "" + +#. Tag: filename +#: install-methods.xml:1158 +#, no-c-format +msgid "vmlinux" +msgstr "" + +#. Tag: filename +#: install-methods.xml:1163 +#, no-c-format +msgid "initrd.gz" +msgstr "" + +#. Tag: filename +#: install-methods.xml:1168 +#, no-c-format +msgid "yaboot" +msgstr "" + +#. Tag: filename +#: install-methods.xml:1173 +#, no-c-format +msgid "yaboot.conf" +msgstr "" + +#. Tag: filename +#: install-methods.xml:1178 +#, no-c-format +msgid "boot.msg" +msgstr "" + +#. Tag: para +#: install-methods.xml:1183 +#, 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. For UEFI machines, you " +"will need to pass an appropriate EFI boot image name (such as <filename>/" +"debian-installer/amd64/bootnetx64.efi</filename>)." +msgstr "" + +#. Tag: para +#: install-methods.xml:1193 +#, 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:1205 +#, no-c-format +msgid "SPARC TFTP Booting" +msgstr "" + +#. Tag: para +#: install-methods.xml:1206 +#, 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" +"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n" +"</screen></informalexample> To get to the correct filename, you will need to " +"change all letters to uppercase and if necessary append the subarchitecture " +"name." +msgstr "" + +#. Tag: para +#: install-methods.xml:1222 +#, 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:1229 +#, 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:1240 +#, no-c-format +msgid "SGI TFTP Booting" +msgstr "" + +#. Tag: para +#: install-methods.xml:1241 +#, 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:1349 +#, no-c-format +msgid "Automatic Installation" +msgstr "" + +#. Tag: para +#: install-methods.xml:1350 +#, 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-" +"quickstart</classname> (which can use an install server) and the &debian; " +"Installer itself. Have a look at the <ulink url=\"http://fai-project.org" +"\">FAI home page</ulink> for detailed information." +msgstr "" + +#. Tag: title +#: install-methods.xml:1362 +#, no-c-format +msgid "Automatic Installation Using the &debian; Installer" +msgstr "" + +#. Tag: para +#: install-methods.xml:1363 +#, 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:1370 +#, no-c-format +msgid "" +"Full documentation on preseeding including a working example that you can " +"edit is in <xref linkend=\"appendix-preseed\"/>." +msgstr "" + +#. Tag: title +#: install-methods.xml:1384 +#, no-c-format +msgid "Verifying the integrity of installation files" +msgstr "" + +#. Tag: para +#: install-methods.xml:1386 +#, no-c-format +msgid "" +"You can verify the integrity of downloaded files against checksums provided " +"in <filename>SHA256SUMS</filename> or <filename>SHA512SUMS</filename> files " +"on Debian mirrors. You can find them in the same places as the installation " +"images itself. Visit the following locations:" +msgstr "" + +#. Tag: para +#: install-methods.xml:1397 +#, no-c-format +msgid "" +"<ulink url=\"https://cdimage.debian.org/debian-cd/current/&architecture;/iso-" +"cd/\">checksum files for CD images</ulink>," +msgstr "" + +#. Tag: para +#: install-methods.xml:1403 +#, no-c-format +msgid "" +"<ulink url=\"https://cdimage.debian.org/debian-cd/current/&architecture;/iso-" +"dvd/\">checksum files for DVD images</ulink>," +msgstr "" + +#. Tag: para +#: install-methods.xml:1409 +#, no-c-format +msgid "" +"<ulink url=\"https://cdimage.debian.org/debian-cd/current/&architecture;/iso-" +"bd/\">checksum files for BD images</ulink>," +msgstr "" + +#. Tag: para +#: install-methods.xml:1415 +#, no-c-format +msgid "" +"<ulink url=\"http://http.us.debian.org/debian/dists/&releasename;/main/" +"installer-&architecture;/current/images/\">checksum files for other " +"installation files</ulink>." +msgstr "" + +#. Tag: para +#: install-methods.xml:1423 +#, no-c-format +msgid "" +"To compute the checksum of a downloaded installation file, use " +"<informalexample><screen>\n" +"sha256sum filename.iso\n" +"</screen></informalexample> respective <informalexample><screen>\n" +"sha512sum filename.iso\n" +"</screen></informalexample> and then compare the shown checksum against the " +"corresponding one in the <filename>SHA256SUMS</filename> respective " +"<filename>SHA512SUMS</filename> file." +msgstr "" + +#. Tag: para +#: install-methods.xml:1436 +#, no-c-format +msgid "" +"The <ulink url=\"&url-debian-cd-faq;\">Debian CD FAQ</ulink> has <ulink url=" +"\"https://www.debian.org/CD/faq/index.en.html#verify\">more useful " +"information</ulink> on this topic (such as the script " +"<filename>check_debian_iso</filename>, to semi-automate above procedure), as " +"well as instructions, how to verify the integrity of the above checksum " +"files themselves." +msgstr "" diff --git a/po/kab/installation-howto.po b/po/kab/installation-howto.po new file mode 100644 index 000000000..9c612e8f0 --- /dev/null +++ b/po/kab/installation-howto.po @@ -0,0 +1,441 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-installation-howto 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-07-26 23: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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: installation-howto.xml:5 +#, no-c-format +msgid "Installation Howto" +msgstr "" + +#. Tag: para +#: installation-howto.xml:7 +#, no-c-format +msgid "" +"This document describes how to install &debian-gnu; &releasename; for the " +"&arch-title; (<quote>&architecture;</quote>) with the new &d-i;. It is a " +"quick walkthrough of the installation process which should contain all the " +"information you will need for most installs. When more information can be " +"useful, we will link to more detailed explanations in other parts of this " +"document." +msgstr "" + +#. Tag: title +#: installation-howto.xml:19 +#, no-c-format +msgid "Preliminaries" +msgstr "" + +#. Tag: para +#: installation-howto.xml:20 +#, no-c-format +msgid "" +"<phrase condition=\"unofficial-build\"> The debian-installer is still in a " +"beta state. </phrase> If you encounter bugs during your install, please " +"refer to <xref linkend=\"submit-bug\"/> for instructions on how to report " +"them. If you have questions which cannot be answered by this document, " +"please direct them to the debian-boot mailing list (&email-debian-boot-" +"list;) or ask on IRC (#debian-boot on the OFTC network)." +msgstr "" + +#. Tag: title +#: installation-howto.xml:36 +#, no-c-format +msgid "Booting the installer" +msgstr "" + +#. Tag: para +#: installation-howto.xml:37 +#, no-c-format +msgid "" +"<phrase condition=\"unofficial-build\"> For some quick links to installation " +"images, check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </" +"phrase> The debian-cd team provides builds of installation images using &d-" +"i; on the <ulink url=\"&url-debian-cd;\">Debian CD/DVD page</ulink>. For " +"more information on where to get installation images, see <xref linkend=" +"\"official-cdrom\"/>." +msgstr "" + +#. Tag: para +#: installation-howto.xml:47 +#, no-c-format +msgid "" +"Some installation methods require other images than those for optical media. " +"<phrase condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; " +"home page</ulink> has links to other images. </phrase> <xref linkend=\"where-" +"files\"/> explains how to find images on &debian; mirrors." +msgstr "" + +#. Tag: para +#: installation-howto.xml:57 +#, no-c-format +msgid "" +"The subsections below will give the details about which images you should " +"get for each possible means of installation." +msgstr "" + +#. Tag: title +#: installation-howto.xml:65 +#, no-c-format +msgid "Optical disc" +msgstr "" + +#. Tag: para +#: installation-howto.xml:67 +#, no-c-format +msgid "" +"The netinst CD image is a popular image which can be used to install " +"&releasename; with the &d-i;. This installation method is intended to boot " +"from the image and install additional packages over a network; hence the " +"name <quote>netinst</quote>. The image has the software components needed to " +"run the installer and the base packages to provide a minimal &releasename; " +"system. If you'd rather, you can get a full size CD/DVD image which will not " +"need the network to install. You only need the first image of such set." +msgstr "" + +#. Tag: para +#: installation-howto.xml:77 +#, no-c-format +msgid "" +"Download whichever type you prefer and burn it to an optical disc. <phrase " +"arch=\"any-x86\">To boot the disc, you may need to change your BIOS/UEFI " +"configuration, as explained in <xref linkend=\"bios-setup\"/>.</phrase> " +"<phrase arch=\"powerpc\"> To boot a PowerMac from CD, press the <keycap>c</" +"keycap> key while booting. See <xref linkend=\"boot-cd\"/> for other ways to " +"boot from CD. </phrase>" +msgstr "" + +#. Tag: title +#: installation-howto.xml:91 +#, no-c-format +msgid "USB memory stick" +msgstr "" + +#. Tag: para +#: installation-howto.xml:92 +#, no-c-format +msgid "" +"It's also possible to install from removable USB storage devices. For " +"example a USB keychain can make a handy &debian; install medium that you can " +"take with you anywhere." +msgstr "" + +#. Tag: para +#: installation-howto.xml:98 +#, no-c-format +msgid "" +"The easiest way to prepare your USB memory stick is to download any Debian " +"CD or DVD image that will fit on it, and write the image directly to the " +"memory stick. Of course this will destroy anything already on the stick. " +"This works because Debian CD/DVD images are <quote>isohybrid</quote> images " +"that can boot both from optical and USB drives." +msgstr "" + +#. Tag: para +#: installation-howto.xml:106 +#, no-c-format +msgid "" +"The easiest way to prepare your USB memory stick is to download <filename>hd-" +"media/boot.img.gz</filename>, and use gunzip to extract the 1 GB image from " +"that file. Write this image directly to your memory stick, which must be at " +"least 1 GB in size. Of course this will destroy anything already on the " +"memory stick. Then mount the memory stick, which will now have a FAT " +"filesystem on it. Next, download a &debian; netinst CD image, and copy that " +"file to the memory stick; any filename is ok as long as it ends in <literal>." +"iso</literal>." +msgstr "" + +#. Tag: para +#: installation-howto.xml:117 +#, no-c-format +msgid "" +"There are other, more flexible ways to set up a memory stick to use the " +"debian-installer, and it's possible to get it to work with smaller memory " +"sticks. For details, see <xref linkend=\"boot-usb-files\"/>." +msgstr "" + +#. Tag: para +#: installation-howto.xml:123 +#, no-c-format +msgid "" +"While booting from USB storage is quite common on UEFI systems, this is " +"somewhat different in the older BIOS world. Some BIOSes can boot USB storage " +"directly, and some cannot. You may need to configure your BIOS/UEFI to " +"enable <quote>USB legacy support</quote> or <quote>Legacy support</quote>. " +"The boot device selection menu should show <quote>removable drive</quote> or " +"<quote>USB-HDD</quote> to get it to boot from the USB device. For helpful " +"hints and details, see <xref linkend=\"usb-boot-x86\"/>." +msgstr "" + +#. Tag: para +#: installation-howto.xml:134 +#, no-c-format +msgid "" +"Booting Macintosh systems from USB storage devices involves manual use of " +"Open Firmware. For directions, see <xref linkend=\"usb-boot-powerpc\"/>." +msgstr "" + +#. Tag: title +#: installation-howto.xml:143 +#, no-c-format +msgid "Booting from network" +msgstr "" + +#. Tag: para +#: installation-howto.xml:144 +#, no-c-format +msgid "" +"It's also possible to boot &d-i; completely from the net. The various " +"methods to netboot depend on your architecture and netboot setup. The files " +"in <filename>netboot/</filename> can be used to netboot &d-i;." +msgstr "" + +#. Tag: para +#: installation-howto.xml:150 +#, no-c-format +msgid "" +"The easiest thing to set up is probably PXE netbooting. Untar the file " +"<filename>netboot/pxeboot.tar.gz</filename> into <filename>/srv/tftp</" +"filename> or wherever is appropriate for your tftp server. Set up your DHCP " +"server to pass filename <filename>pxelinux.0</filename> to clients, and with " +"luck everything will just work. For detailed instructions, see <xref linkend=" +"\"install-tftp\"/>." +msgstr "" + +#. Tag: title +#: installation-howto.xml:164 +#, no-c-format +msgid "Booting from hard disk" +msgstr "" + +#. Tag: para +#: installation-howto.xml:165 +#, no-c-format +msgid "" +"It's possible to boot the installer using no removable media, but just an " +"existing hard disk, which can have a different OS on it. Download " +"<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</" +"filename>, and a &debian; CD/DVD image to the top-level directory of the " +"hard disk. Make sure that the image has a filename ending in <literal>.iso</" +"literal>. Now it's just a matter of booting linux with the initrd. <phrase " +"arch=\"x86\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </" +"phrase>" +msgstr "" + +#. Tag: title +#: installation-howto.xml:182 +#, no-c-format +msgid "Installation" +msgstr "" + +#. Tag: para +#: installation-howto.xml:183 +#, no-c-format +msgid "" +"Once the installer starts, you will be greeted with an initial screen. Press " +"&enterkey; to boot, or read the instructions for other boot methods and " +"parameters (see <xref linkend=\"boot-parms\"/>)." +msgstr "" + +#. Tag: para +#: installation-howto.xml:189 +#, no-c-format +msgid "" +"After a while you will be asked to select your language. Use the arrow keys " +"to pick a language and press &enterkey; to continue. Next you'll be asked to " +"select your country, with the choices including countries where your " +"language is spoken. If it's not on the short list, a list of all the " +"countries in the world is available." +msgstr "" + +#. Tag: para +#: installation-howto.xml:197 +#, no-c-format +msgid "" +"You may be asked to confirm your keyboard layout. Choose the default unless " +"you know better." +msgstr "" + +#. Tag: para +#: installation-howto.xml:202 +#, no-c-format +msgid "" +"Now sit back while debian-installer detects some of your hardware, and loads " +"the rest of the installation image." +msgstr "" + +#. Tag: para +#: installation-howto.xml:207 +#, no-c-format +msgid "" +"Next the installer will try to detect your network hardware and set up " +"networking by DHCP. If you are not on a network or do not have DHCP, you " +"will be given the opportunity to configure the network manually." +msgstr "" + +#. Tag: para +#: installation-howto.xml:213 +#, no-c-format +msgid "" +"Setting up the network is followed by the creation of user accounts. By " +"default you are asked to provide a password for the <quote>root</quote> " +"(administrator) account and information necessary to create one regular user " +"account. If you do not specify a password for the <quote>root</quote> user, " +"this account will be disabled but the <command>sudo</command> package will " +"be installed later to enable administrative tasks to be carried out on the " +"new system. By default, the first user created on the system will be allowed " +"to use the <command>sudo</command> command to become root." +msgstr "" + +#. Tag: para +#: installation-howto.xml:224 +#, no-c-format +msgid "" +"The next step is setting up your clock and time zone. The installer will try " +"to contact a time server on the Internet to ensure the clock is set " +"correctly. The time zone is based on the country selected earlier and the " +"installer will only ask to select one if a country has multiple zones." +msgstr "" + +#. Tag: para +#: installation-howto.xml:231 +#, no-c-format +msgid "" +"Now it is time to partition your disks. First you will be given the " +"opportunity to automatically partition either an entire drive, or available " +"free space on a drive (see <xref linkend=\"partman-auto\"/>). This is " +"recommended for new users or anyone in a hurry. If you do not want to " +"autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." +msgstr "" + +#. Tag: para +#: installation-howto.xml:239 +#, no-c-format +msgid "" +"If you have an existing DOS or Windows partition that you want to preserve, " +"be very careful with automatic partitioning. If you choose manual " +"partitioning, you can use the installer to resize existing FAT or NTFS " +"partitions to create room for the &debian; install: simply select the " +"partition and specify its new size." +msgstr "" + +#. Tag: para +#: installation-howto.xml:246 +#, no-c-format +msgid "" +"On the next screen you will see your partition table, how the partitions " +"will be formatted, and where they will be mounted. Select a partition to " +"modify or delete it. If you did automatic partitioning, you should just be " +"able to choose <guimenuitem>Finish partitioning and write changes to disk</" +"guimenuitem> from the menu to use what it set up. Remember to assign at " +"least one partition for swap space and to mount a partition on <filename>/</" +"filename>. For more detailed information on how to use the partitioner, " +"please refer to <xref linkend=\"di-partition\"/>; the appendix <xref linkend=" +"\"partitioning\"/> has more general information about partitioning." +msgstr "" + +#. Tag: para +#: installation-howto.xml:259 +#, no-c-format +msgid "" +"Now &d-i; formats your partitions and starts to install the base system, " +"which can take a while. That is followed by installing a kernel." +msgstr "" + +#. Tag: para +#: installation-howto.xml:264 +#, no-c-format +msgid "" +"The base system that was installed earlier is a working, but very minimal " +"installation. To make the system more functional the next step allows you to " +"install additional packages by selecting tasks. Before packages can be " +"installed <classname>apt</classname> needs to be configured as that defines " +"from where the packages will be retrieved. The <quote>Standard system</" +"quote> task will be selected by default and should normally be installed. " +"Select the <quote>Desktop environment</quote> task if you would like to have " +"a graphical desktop after the installation. See <xref linkend=\"pkgsel\"/> " +"for additional information about this step." +msgstr "" + +#. Tag: para +#: installation-howto.xml:276 +#, no-c-format +msgid "" +"The last step is to install a boot loader. If the installer detects other " +"operating systems on your computer, it will add them to the boot menu and " +"let you know. <phrase arch=\"any-x86\">By default GRUB will be installed to " +"the UEFI partition/boot record of the primary drive, which is generally a " +"good choice. You'll be given the opportunity to override that choice and " +"install it elsewhere. </phrase>" +msgstr "" + +#. Tag: para +#: installation-howto.xml:286 +#, no-c-format +msgid "" +"&d-i; will now tell you that the installation has finished. Remove the cdrom " +"or other boot media and hit &enterkey; to reboot your machine. It should " +"boot up into the newly installed system and allow you to log in. This is " +"explained in <xref linkend=\"boot-new\"/>." +msgstr "" + +#. Tag: para +#: installation-howto.xml:293 +#, no-c-format +msgid "" +"If you need more information on the install process, see <xref linkend=\"d-i-" +"intro\"/>." +msgstr "" + +#. Tag: title +#: installation-howto.xml:302 +#, no-c-format +msgid "Send us an installation report" +msgstr "" + +#. Tag: para +#: installation-howto.xml:303 +#, 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 install reportbug</command>), configure " +"<classname>reportbug</classname> as explained in <xref linkend=\"mail-" +"outgoing\"/>, and run <command>reportbug installation-reports</command>." +msgstr "" + +#. Tag: para +#: installation-howto.xml:313 +#, 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:325 +#, no-c-format +msgid "And finally…" +msgstr "" + +#. Tag: para +#: installation-howto.xml:326 +#, 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/kab/partitioning.po b/po/kab/partitioning.po new file mode 100644 index 000000000..01998b4f0 --- /dev/null +++ b/po/kab/partitioning.po @@ -0,0 +1,1122 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-partitioning 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-08-12 23: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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: partitioning.xml:5 +#, no-c-format +msgid "Partitioning for &debian;" +msgstr "" + +#. Tag: title +#: partitioning.xml:13 +#, no-c-format +msgid "Deciding on &debian; Partitions and Sizes" +msgstr "" + +#. Tag: para +#: partitioning.xml:14 +#, no-c-format +msgid "" +"At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can " +"have a single partition containing the entire operating system, " +"applications, and your personal files. Most people feel that a separate swap " +"partition is also a necessity, although it's not strictly true. <quote>Swap</" +"quote> is scratch space for an operating system, which allows the system to " +"use disk storage as <quote>virtual memory</quote>. By putting swap on a " +"separate partition, &arch-kernel; can make much more efficient use of it. It " +"is possible to force &arch-kernel; to use a regular file as swap, but it is " +"not recommended." +msgstr "" + +#. Tag: para +#: partitioning.xml:26 +#, no-c-format +msgid "" +"Most people choose to give GNU/&arch-kernel; more than the minimum number of " +"partitions, however. There are two reasons you might want to break up the " +"file system into a number of smaller partitions. The first is for safety. If " +"something happens to corrupt the file system, generally only one partition " +"is affected. Thus, you only have to replace (from the backups you've been " +"carefully keeping) a portion of your system. At a bare minimum, you should " +"consider creating what is commonly called a <quote>root partition</quote>. " +"This contains the most essential components of the system. If any other " +"partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix " +"the system. This can save you the trouble of having to reinstall the system " +"from scratch." +msgstr "" + +#. Tag: para +#: partitioning.xml:40 +#, no-c-format +msgid "" +"The second reason is generally more important in a business setting, but it " +"really depends on your use of the machine. For example, a mail server " +"getting spammed with e-mail can easily fill a partition. If you made " +"<filename>/var/mail</filename> a separate partition on the mail server, most " +"of the system will remain working even if you get spammed." +msgstr "" + +#. Tag: para +#: partitioning.xml:48 +#, no-c-format +msgid "" +"The only real drawback to using more partitions is that it is often " +"difficult to know in advance what your needs will be. If you make a " +"partition too small then you will either have to reinstall the system or you " +"will be constantly moving things around to make room in the undersized " +"partition. On the other hand, if you make the partition too big, you will be " +"wasting space that could be used elsewhere. Disk space is cheap nowadays, " +"but why throw your money away?" +msgstr "" + +#. Tag: title +#: partitioning.xml:67 +#, no-c-format +msgid "The Directory Tree" +msgstr "" + +#. Tag: para +#: partitioning.xml:68 +#, no-c-format +msgid "" +"&debian-gnu; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem " +"Hierarchy Standard</ulink> for directory and file naming. This standard " +"allows users and software programs to predict the location of files and " +"directories. The root level directory is represented simply by the slash " +"<filename>/</filename>. At the root level, all &debian; systems include " +"these directories:" +msgstr "" + +#. Tag: entry +#: partitioning.xml:82 +#, no-c-format +msgid "Directory" +msgstr "" + +#. Tag: entry +#: partitioning.xml:82 +#, no-c-format +msgid "Content" +msgstr "" + +#. Tag: filename +#: partitioning.xml:88 +#, no-c-format +msgid "<filename>bin</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:89 +#, no-c-format +msgid "Essential command binaries" +msgstr "" + +#. Tag: filename +#: partitioning.xml:91 +#, no-c-format +msgid "boot" +msgstr "" + +#. Tag: entry +#: partitioning.xml:92 +#, no-c-format +msgid "Static files of the boot loader" +msgstr "" + +#. Tag: filename +#: partitioning.xml:94 +#, no-c-format +msgid "<filename>dev</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:95 +#, no-c-format +msgid "Device files" +msgstr "" + +#. Tag: filename +#: partitioning.xml:97 +#, no-c-format +msgid "<filename>etc</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:98 +#, no-c-format +msgid "Host-specific system configuration" +msgstr "" + +#. Tag: filename +#: partitioning.xml:100 +#, no-c-format +msgid "home" +msgstr "" + +#. Tag: entry +#: partitioning.xml:101 +#, no-c-format +msgid "User home directories" +msgstr "" + +#. Tag: filename +#: partitioning.xml:103 +#, no-c-format +msgid "<filename>lib</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:104 +#, no-c-format +msgid "Essential shared libraries and kernel modules" +msgstr "" + +#. Tag: filename +#: partitioning.xml:106 +#, no-c-format +msgid "media" +msgstr "" + +#. Tag: entry +#: partitioning.xml:107 +#, no-c-format +msgid "Contains mount points for replaceable media" +msgstr "" + +#. Tag: filename +#: partitioning.xml:109 +#, no-c-format +msgid "<filename>mnt</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:110 +#, no-c-format +msgid "Mount point for mounting a file system temporarily" +msgstr "" + +#. Tag: filename +#: partitioning.xml:112 +#, no-c-format +msgid "proc" +msgstr "" + +#. Tag: entry +#: partitioning.xml:113 partitioning.xml:125 +#, no-c-format +msgid "Virtual directory for system information" +msgstr "" + +#. Tag: filename +#: partitioning.xml:115 +#, no-c-format +msgid "root" +msgstr "" + +#. Tag: entry +#: partitioning.xml:116 +#, no-c-format +msgid "Home directory for the root user" +msgstr "" + +#. Tag: filename +#: partitioning.xml:118 +#, no-c-format +msgid "<filename>run</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:119 +#, no-c-format +msgid "Run-time variable data" +msgstr "" + +#. Tag: filename +#: partitioning.xml:121 +#, no-c-format +msgid "sbin" +msgstr "" + +#. Tag: entry +#: partitioning.xml:122 +#, no-c-format +msgid "Essential system binaries" +msgstr "" + +#. Tag: filename +#: partitioning.xml:124 +#, no-c-format +msgid "<filename>sys</filename>" +msgstr "" + +#. Tag: filename +#: partitioning.xml:127 +#, no-c-format +msgid "<filename>tmp</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:128 +#, no-c-format +msgid "Temporary files" +msgstr "" + +#. Tag: filename +#: partitioning.xml:130 +#, no-c-format +msgid "<filename>usr</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:131 +#, no-c-format +msgid "Secondary hierarchy" +msgstr "" + +#. Tag: filename +#: partitioning.xml:133 +#, no-c-format +msgid "<filename>var</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:134 +#, no-c-format +msgid "Variable data" +msgstr "" + +#. Tag: filename +#: partitioning.xml:136 +#, no-c-format +msgid "<filename>srv</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:137 +#, no-c-format +msgid "Data for services provided by the system" +msgstr "" + +#. Tag: filename +#: partitioning.xml:139 +#, no-c-format +msgid "<filename>opt</filename>" +msgstr "" + +#. Tag: entry +#: partitioning.xml:140 +#, no-c-format +msgid "Add-on application software packages" +msgstr "" + +#. Tag: para +#: partitioning.xml:145 +#, no-c-format +msgid "" +"The following is a list of important considerations regarding directories " +"and partitions. Note that disk usage varies widely given system " +"configuration and specific usage patterns. The recommendations here are " +"general guidelines and provide a starting point for partitioning." +msgstr "" + +#. Tag: para +#: partitioning.xml:155 +#, no-c-format +msgid "" +"The root partition <filename>/</filename> must always physically contain " +"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</" +"filename>, <filename>/lib</filename> and <filename>/dev</filename>, " +"otherwise you won't be able to boot. Typically &root-system-size-min;–" +"&root-system-size-max;MB is needed for the root partition." +msgstr "" + +#. Tag: para +#: partitioning.xml:164 +#, no-c-format +msgid "" +"<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</" +"filename>), libraries (<filename>/usr/lib</filename>), documentation " +"(<filename>/usr/share/doc</filename>), etc. This is the part of the file " +"system that generally takes up most space. You should provide at least 500MB " +"of disk space. This amount should be increased depending on the number and " +"type of packages you plan to install. A generous workstation or server " +"installation should allow 4–6GB." +msgstr "" + +#. Tag: para +#: partitioning.xml:177 +#, no-c-format +msgid "" +"It is now recommended to have <filename>/usr</filename> on the root " +"partition <filename>/</filename>, otherwise it could cause some trouble at " +"boot time. This means that you should provide at least 600–750MB of " +"disk space for the root partition including <filename>/usr</filename>, or " +"5–6GB for a workstation or a server installation." +msgstr "" + +#. Tag: para +#: partitioning.xml:187 +#, no-c-format +msgid "" +"<filename>/var</filename>: variable data like news articles, e-mails, web " +"sites, databases, the packaging system cache, etc. will be placed under this " +"directory. The size of this directory depends greatly on the usage of your " +"system, but for most people will be dictated by the package management " +"tool's overhead. If you are going to do a full installation of just about " +"everything &debian; has to offer, all in one session, setting aside 2 or 3 " +"GB of space for <filename>/var</filename> should be sufficient. If you are " +"going to install in pieces (that is to say, install services and utilities, " +"followed by text stuff, then X, ...), you can get away with 300–500 " +"MB. If hard drive space is at a premium and you don't plan on doing major " +"system updates, you can get by with as little as 30 or 40 MB." +msgstr "" + +#. Tag: para +#: partitioning.xml:203 +#, no-c-format +msgid "" +"<filename>/tmp</filename>: temporary data created by programs will most " +"likely go in this directory. 40–100MB should usually be enough. Some " +"applications — including archive manipulators, CD/DVD authoring tools, " +"and multimedia software — may use <filename>/tmp</filename> to " +"temporarily store image files. If you plan to use such applications, you " +"should adjust the space available in <filename>/tmp</filename> accordingly." +msgstr "" + +#. Tag: para +#: partitioning.xml:214 +#, no-c-format +msgid "" +"<filename>/home</filename>: every user will put his personal data into a " +"subdirectory of this directory. Its size depends on how many users will be " +"using the system and what files are to be stored in their directories. " +"Depending on your planned usage you should reserve about 100MB for each " +"user, but adapt this value to your needs. Reserve a lot more space if you " +"plan to save a lot of multimedia files (pictures, MP3, movies) in your home " +"directory." +msgstr "" + +#. Tag: title +#: partitioning.xml:235 +#, no-c-format +msgid "Recommended Partitioning Scheme" +msgstr "" + +#. Tag: para +#: partitioning.xml:236 +#, no-c-format +msgid "" +"For new users, personal &debian; boxes, home systems, and other single-user " +"setups, a single <filename>/</filename> partition (plus swap) is probably " +"the easiest, simplest way to go. The recommended partition type is ext4." +msgstr "" + +#. Tag: para +#: partitioning.xml:243 +#, no-c-format +msgid "" +"For multi-user systems or systems with lots of disk space, it's best to put " +"<filename>/var</filename>, <filename>/tmp</filename>, and <filename>/home</" +"filename> each on their own partitions separate from the <filename>/</" +"filename> partition." +msgstr "" + +#. Tag: para +#: partitioning.xml:251 +#, no-c-format +msgid "" +"You might need a separate <filename>/usr/local</filename> partition if you " +"plan to install many programs that are not part of the &debian; " +"distribution. If your machine will be a mail server, you might need to make " +"<filename>/var/mail</filename> a separate partition. If you are setting up a " +"server with lots of user accounts, it's generally good to have a separate, " +"large <filename>/home</filename> partition. In general, the partitioning " +"situation varies from computer to computer depending on its uses." +msgstr "" + +#. Tag: para +#: partitioning.xml:262 +#, no-c-format +msgid "" +"For very complex systems, you should see the <ulink url=\"&url-multidisk-" +"howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, " +"mostly of interest to ISPs and people setting up servers." +msgstr "" + +#. Tag: para +#: partitioning.xml:269 +#, no-c-format +msgid "" +"With respect to the issue of swap partition size, there are many views. One " +"rule of thumb which works well is to use as much swap as you have system " +"memory. It also shouldn't be smaller than 512MB, in most cases. Of course, " +"there are exceptions to these rules." +msgstr "" + +#. Tag: para +#: partitioning.xml:276 +#, no-c-format +msgid "" +"As an example, an older home machine might have 512MB of RAM and a 20GB SATA " +"drive on <filename>/dev/sda</filename>. There might be a 8GB partition for " +"another operating system on <filename>/dev/sda1</filename>, a 512MB swap " +"partition on <filename>/dev/sda3</filename> and about 11.4GB on <filename>/" +"dev/sda2</filename> as the Linux partition." +msgstr "" + +#. Tag: para +#: partitioning.xml:285 +#, no-c-format +msgid "" +"For an idea of the space taken by tasks you might be interested in adding " +"after your system installation is complete, check <xref linkend=\"tasksel-" +"size-list\"/>." +msgstr "" + +#. Tag: title +#: partitioning.xml:301 +#, no-c-format +msgid "Device Names in Linux" +msgstr "" + +#. Tag: para +#: partitioning.xml:302 +#, no-c-format +msgid "" +"Linux disks and partition names may be different from other operating " +"systems. You need to know the names that Linux uses when you create and " +"mount partitions. Here's the basic naming scheme:" +msgstr "" + +#. Tag: para +#: partitioning.xml:310 +#, no-c-format +msgid "The first hard disk detected is named <filename>/dev/sda</filename>." +msgstr "" + +#. Tag: para +#: partitioning.xml:315 +#, no-c-format +msgid "" +"The second hard disk detected is named <filename>/dev/sdb</filename>, and so " +"on." +msgstr "" + +#. Tag: para +#: partitioning.xml:321 +#, no-c-format +msgid "" +"The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as " +"<filename>/dev/sr0</filename>." +msgstr "" + +#. Tag: para +#: partitioning.xml:330 +#, no-c-format +msgid "The first DASD device is named <filename>/dev/dasda</filename>." +msgstr "" + +#. Tag: para +#: partitioning.xml:336 +#, no-c-format +msgid "" +"The second DASD device is named <filename>/dev/dasdb</filename>, and so on." +msgstr "" + +#. Tag: para +#: partitioning.xml:344 +#, no-c-format +msgid "" +"The partitions on each disk are represented by appending a decimal number to " +"the disk name: <filename>sda1</filename> and <filename>sda2</filename> " +"represent the first and second partitions of the first SCSI disk drive in " +"your system." +msgstr "" + +#. Tag: para +#: partitioning.xml:351 +#, no-c-format +msgid "" +"Here is a real-life example. Let's assume you have a system with 2 SCSI " +"disks, one at SCSI address 2 and the other at SCSI address 4. The first disk " +"(at address 2) is then named <filename>sda</filename>, and the second " +"<filename>sdb</filename>. If the <filename>sda</filename> drive has 3 " +"partitions on it, these will be named <filename>sda1</filename>, " +"<filename>sda2</filename>, and <filename>sda3</filename>. The same applies " +"to the <filename>sdb</filename> disk and its partitions." +msgstr "" + +#. Tag: para +#: partitioning.xml:362 +#, no-c-format +msgid "" +"Note that if you have two SCSI host bus adapters (i.e., controllers), the " +"order of the drives can get confusing. The best solution in this case is to " +"watch the boot messages, assuming you know the drive models and/or " +"capacities." +msgstr "" + +#. Tag: para +#: partitioning.xml:369 +#, no-c-format +msgid "" +"Linux represents the primary partitions as the drive name, plus the numbers " +"1 through 4. For example, the first primary partition on the first drive is " +"<filename>/dev/sda1</filename>. The logical partitions are numbered starting " +"at 5, so the first logical partition on that same drive is <filename>/dev/" +"sda5</filename>. Remember that the extended partition, that is, the primary " +"partition holding the logical partitions, is not usable by itself." +msgstr "" + +#. Tag: para +#: partitioning.xml:379 +#, no-c-format +msgid "" +"Sun disk partitions allow for 8 separate partitions (or slices). The third " +"partition is usually (and is preferred to have) the <quote>Whole Disk</" +"quote> partition. This partition references all of the sectors of the disk, " +"and is used by the boot loader (either SILO, or Sun's)." +msgstr "" + +#. Tag: para +#: partitioning.xml:386 +#, no-c-format +msgid "" +"The partitions on each disk are represented by appending a decimal number to " +"the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> " +"represent the first and second partitions of the first DASD device in your " +"system." +msgstr "" + +#. Tag: title +#: partitioning.xml:401 +#, no-c-format +msgid "&debian; Partitioning Programs" +msgstr "" + +#. Tag: para +#: partitioning.xml:402 +#, no-c-format +msgid "" +"Several varieties of partitioning programs have been adapted by &debian; " +"developers to work on various types of hard disks and computer " +"architectures. Following is a list of the program(s) applicable for your " +"architecture." +msgstr "" + +#. Tag: para +#: partitioning.xml:415 +#, no-c-format +msgid "" +"Recommended partitioning tool in &debian;. This Swiss army knife can also " +"resize partitions, create filesystems <phrase arch=\"any-x86\"> " +"(<quote>format</quote> in Windows speak)</phrase> and assign them to the " +"mountpoints." +msgstr "" + +#. Tag: para +#: partitioning.xml:427 +#, no-c-format +msgid "The original Linux disk partitioner, good for gurus." +msgstr "" + +#. Tag: para +#: partitioning.xml:431 +#, no-c-format +msgid "" +"Be careful if you have existing FreeBSD partitions on your machine. The " +"installation kernels include support for these partitions, but the way that " +"<command>fdisk</command> represents them (or not) can make the device names " +"differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</" +"ulink>." +msgstr "" + +#. Tag: para +#: partitioning.xml:444 +#, no-c-format +msgid "A simple-to-use, full-screen disk partitioner for the rest of us." +msgstr "" + +#. Tag: para +#: partitioning.xml:448 +#, no-c-format +msgid "" +"Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at " +"all, and, again, device names may differ as a result." +msgstr "" + +#. Tag: para +#: partitioning.xml:458 +#, no-c-format +msgid "Atari-aware version of <command>fdisk</command>." +msgstr "" + +#. Tag: para +#: partitioning.xml:467 +#, no-c-format +msgid "Amiga-aware version of <command>fdisk</command>." +msgstr "" + +#. Tag: para +#: partitioning.xml:476 +#, no-c-format +msgid "Mac-aware version of <command>fdisk</command>." +msgstr "" + +#. Tag: para +#: partitioning.xml:485 +#, no-c-format +msgid "" +"PowerMac-aware version of <command>fdisk</command>, also used by BVM and " +"Motorola VMEbus systems." +msgstr "" + +#. Tag: para +#: partitioning.xml:495 +#, no-c-format +msgid "" +"&arch-title; version of <command>fdisk</command>; Please read the fdasd " +"manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/" +"developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and " +"Installation Commands</ulink> for details." +msgstr "" + +#. Tag: para +#: partitioning.xml:506 +#, no-c-format +msgid "" +"One of these programs will be run by default when you select " +"<guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible " +"to use a different partitioning tool from the command line on VT2, but this " +"is not recommended." +msgstr "" + +#. Tag: para +#: partitioning.xml:513 +#, no-c-format +msgid "Remember to mark your boot partition as <quote>Bootable</quote>." +msgstr "" + +#. Tag: para +#: partitioning.xml:516 +#, no-c-format +msgid "" +"One key point when partitioning for Mac type disks is that the swap " +"partition is identified by its name; it must be named <quote>swap</quote>. " +"All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. " +"Please read the fine manual. We also suggest reading the <ulink url=\"&url-" +"mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you " +"should take if you are sharing your disk with MacOS." +msgstr "" + +#. Tag: title +#: partitioning.xml:532 partitioning.xml:556 partitioning.xml:672 +#: partitioning.xml:786 partitioning.xml:863 +#, no-c-format +msgid "Partitioning for &arch-title;" +msgstr "" + +#. Tag: para +#: partitioning.xml:533 +#, no-c-format +msgid "" +"PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> " +"somewhere in the first 2GB. This is where the boot loader and an optional " +"kernel and RAMdisk will be stored, so make it big enough for that — at " +"least 4Mb (I like 8–16MB). An additional requirement of the firmware " +"is that the Linux kernel must reside within the first 2GB of the disk. This " +"is typically achieved by making the root ext2 partition fit entirely within " +"the first 2GB of the disk. Alternatively you can create a small ext2 " +"partition near the start of the disk and mount that on <filename>/boot</" +"filename>, since that is the directory where the Linux kernel(s) will be " +"stored. <filename>/boot</filename> needs to be big enough to hold whatever " +"kernels (and backups) you might wish to load; 25–50MB is generally " +"sufficient." +msgstr "" + +#. Tag: para +#: partitioning.xml:557 +#, no-c-format +msgid "" +"If you are using a new harddisk (or want to wipe out the whole partition " +"table of your disk), a new partition table needs to be created. The " +"<quote>Guided partitioning</quote> does this automatically, but when " +"partitioning manually, move the selection on the top-level entry of the disk " +"and hit &enterkey;. That will create a new partition table on that disk. In " +"expert mode, you will then be asked for the type of the partition table. " +"Default for UEFI-based systems is <quote>gpt</quote>, while for the older " +"BIOS world the default value is <quote>msdos</quote>. In a standard priority " +"installation those defaults will be used automatically." +msgstr "" + +#. Tag: para +#: partitioning.xml:569 +#, no-c-format +msgid "" +"When a partition table with type <quote>gpt</quote> was selected (default " +"for UEFI systems), a free space of 1 MB will automatically get created at " +"the beginning of the disk. This is intended and required to embed the GRUB2 " +"bootloader." +msgstr "" + +#. Tag: para +#: partitioning.xml:576 +#, no-c-format +msgid "" +"If you have an existing other operating system such as DOS or Windows and " +"you want to preserve that operating system while installing &debian;, you " +"may need to resize its partition to free up space for the &debian; " +"installation. The installer supports resizing of both FAT and NTFS " +"filesystems; when you get to the installer's partitioning step, select the " +"option <guimenuitem>Manual</guimenuitem> and then simply select an existing " +"partition and change its size." +msgstr "" + +#. Tag: para +#: partitioning.xml:586 +#, no-c-format +msgid "" +"While modern UEFI systems don't have such limitations as listed below, the " +"old PC BIOS generally adds additional constraints for disk partitioning. " +"There is a limit to how many <quote>primary</quote> and <quote>logical</" +"quote> partitions a drive can contain. Additionally, with pre 1994–98 " +"BIOSes, there are limits to where on the drive the BIOS can boot from. More " +"information can be found in the <ulink url=\"&url-partition-howto;\">Linux " +"Partition HOWTO</ulink>, but this section will include a brief overview to " +"help you plan most situations." +msgstr "" + +#. Tag: para +#: partitioning.xml:597 +#, no-c-format +msgid "" +"<quote>Primary</quote> partitions are the original partitioning scheme for " +"PC disks. However, there can only be four of them. To get past this " +"limitation, <quote>extended</quote> and <quote>logical</quote> partitions " +"were invented. By setting one of your primary partitions as an extended " +"partition, you can subdivide all the space allocated to that partition into " +"logical partitions. You can create up to 60 logical partitions per extended " +"partition; however, you can only have one extended partition per drive." +msgstr "" + +#. Tag: para +#: partitioning.xml:608 +#, no-c-format +msgid "" +"Linux limits the partitions per drive to 255 partitions for SCSI disks (3 " +"usable primary partitions, 252 logical partitions), and 63 partitions on an " +"IDE drive (3 usable primary partitions, 60 logical partitions). However the " +"normal &debian-gnu; system provides only 20 devices for partitions, so you " +"may not install on partitions higher than 20 unless you first manually " +"create devices for those partitions." +msgstr "" + +#. Tag: para +#: partitioning.xml:618 +#, no-c-format +msgid "" +"If you have a large IDE disk, and are using neither LBA addressing, nor " +"overlay drivers (sometimes provided by hard disk manufacturers), then the " +"boot partition (the partition containing your kernel image) must be placed " +"within the first 1024 cylinders of your hard drive (usually around 524 " +"megabytes, without BIOS translation)." +msgstr "" + +#. Tag: para +#: partitioning.xml:626 +#, no-c-format +msgid "" +"This restriction doesn't apply if you have a BIOS newer than around " +"1995–98 (depending on the manufacturer) that supports the " +"<quote>Enhanced Disk Drive Support Specification</quote>. &debian;'s Lilo " +"alternative <command>mbr</command> must use the BIOS to read the kernel from " +"the disk into RAM. If the BIOS int 0x13 large disk access extensions are " +"found to be present, they will be utilized. Otherwise, the legacy disk " +"access interface is used as a fall-back, and it cannot be used to address " +"any location on the disk higher than the 1023rd cylinder. Once &arch-kernel; " +"is booted, no matter what BIOS your computer has, these restrictions no " +"longer apply, since &arch-kernel; does not use the BIOS for disk access." +msgstr "" + +#. Tag: para +#: partitioning.xml:640 +#, no-c-format +msgid "" +"If you have a large disk, you might have to use cylinder translation " +"techniques, which you can set from your BIOS setup program, such as LBA " +"(Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). " +"More information about issues with large disks can be found in the <ulink " +"url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a " +"cylinder translation scheme, and the BIOS does not support the large disk " +"access extensions, then your boot partition has to fit within the " +"<emphasis>translated</emphasis> representation of the 1024th cylinder." +msgstr "" + +#. Tag: para +#: partitioning.xml:652 +#, no-c-format +msgid "" +"The recommended way of accomplishing this is to create a small " +"(25–50MB should suffice) partition at the beginning of the disk to be " +"used as the boot partition, and then create whatever other partitions you " +"wish to have, in the remaining area. This boot partition <emphasis>must</" +"emphasis> be mounted on <filename>/boot</filename>, since that is the " +"directory where the &arch-kernel; kernel(s) will be stored. This " +"configuration will work on any system, regardless of whether LBA or large " +"disk CHS translation is used, and regardless of whether your BIOS supports " +"the large disk access extensions." +msgstr "" + +#. Tag: para +#: partitioning.xml:673 +#, no-c-format +msgid "" +"The <command>partman</command> disk partitioner is the default partitioning " +"tool for the installer. It manages the set of partitions and their mount " +"points to ensure that the disks and filesystems are properly configured for " +"a successful installation. It actually uses <command>parted</command> to do " +"the on-disk partitioning." +msgstr "" + +#. Tag: title +#: partitioning.xml:685 +#, no-c-format +msgid "EFI Recognized Formats" +msgstr "" + +#. Tag: para +#: partitioning.xml:686 +#, no-c-format +msgid "" +"The IA-64 EFI firmware supports two partition table (or disk label) formats, " +"GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer " +"recommended for IA-64 systems. Although the installer also provides " +"<command>cfdisk</command>, you should only use <ulink url=\"parted.txt\"> " +"<command>parted</command></ulink> because only it can manage both GPT and MS-" +"DOS tables correctly." +msgstr "" + +#. Tag: para +#: partitioning.xml:698 +#, no-c-format +msgid "" +"The automatic partitioning recipes for <command>partman</command> allocate " +"an EFI partition as the first partition on the disk. You can also set up the " +"partition under the <guimenuitem>Guided partitioning</guimenuitem> from the " +"main menu in a manner similar to setting up a <emphasis>swap</emphasis> " +"partition." +msgstr "" + +#. Tag: para +#: partitioning.xml:706 +#, no-c-format +msgid "" +"The <command>partman</command> partitioner will handle most disk layouts. " +"For those rare cases where it is necessary to manually set up a disk, you " +"can use the shell as described above and run the <command>parted</command> " +"utility directly using its command line interface. Assuming that you want to " +"erase your whole disk and create a GPT table and some partitions, then " +"something similar to the following command sequence could be used: " +"<informalexample><screen>\n" +" mklabel gpt\n" +" mkpartfs primary fat 0 50\n" +" mkpartfs primary linux-swap 51 1000\n" +" mkpartfs primary ext2 1001 3000\n" +" set 1 boot on\n" +" print\n" +" quit\n" +"</screen></informalexample> This creates a new partition table, and three " +"partitions to be used as an EFI boot partition, swap space, and a root file " +"system. Finally it sets the boot flag on the EFI partition. Partitions are " +"specified in Megabytes, with start and end offsets from the beginning of the " +"disk. So, for example, above we created a 1999MB ext2 file system starting " +"at offset 1001MB from the start of the disk. Note that formatting swap space " +"with <command>parted</command> can take a few minutes to complete, as it " +"scans the partition for bad blocks." +msgstr "" + +#. Tag: title +#: partitioning.xml:731 +#, no-c-format +msgid "Boot Loader Partition Requirements" +msgstr "" + +#. Tag: para +#: partitioning.xml:732 +#, no-c-format +msgid "" +"ELILO, the IA-64 boot loader, requires a partition containing a FAT file " +"system with the <userinput>boot</userinput> flag set. The partition must be " +"big enough to hold the boot loader and any kernels or RAMdisks you may wish " +"to boot. A minimum size would be about 20MB, but if you expect to run with " +"multiple kernels, then 128MB might be a better size." +msgstr "" + +#. Tag: para +#: partitioning.xml:741 +#, no-c-format +msgid "" +"The EFI Boot Manager and the EFI Shell fully support the GPT table so the " +"boot partition does not necessarily have to be the first partition or even " +"on the same disk. This is convenient if you should forget to allocate the " +"partition and only find out after you have formatted the other partitions on " +"your disk(s). The <command>partman</command> partitioner checks for an EFI " +"partition at the same time it checks for a properly set up <emphasis>root</" +"emphasis> partition. This gives you an opportunity to correct the disk " +"layout before the package install begins. The easiest way to correct this " +"omission is to shrink the last partition of the disk to make enough free " +"space for adding an EFI partition." +msgstr "" + +#. Tag: para +#: partitioning.xml:756 +#, no-c-format +msgid "" +"It is strongly recommended that you allocate the EFI boot partition on the " +"same disk as the <emphasis>root</emphasis> filesystem." +msgstr "" + +#. Tag: title +#: partitioning.xml:764 +#, no-c-format +msgid "EFI Diagnostic Partitions" +msgstr "" + +#. Tag: para +#: partitioning.xml:765 +#, no-c-format +msgid "" +"The EFI firmware is significantly more sophisticated than the usual BIOS " +"seen on most x86 PCs. Some system vendors take advantage of the ability of " +"the EFI to access files and run programs from a hard disk filesystem to " +"store diagnostics and EFI based system management utilities on the hard " +"disk. This is a separate FAT format filesystem on the system disk. Consult " +"the system documentation and accessories that come with the system for " +"details. The easiest time to set up a diagnostics partition is at the same " +"time you set up the EFI boot partition." +msgstr "" + +#. Tag: para +#: partitioning.xml:787 +#, no-c-format +msgid "" +"SGI machines require an SGI disk label in order to make the system bootable " +"from hard disk. It can be created in the fdisk expert menu. The thereby " +"created volume header (partition number 9) should be at least 3MB large. If " +"the volume header created is too small, you can simply delete partition " +"number 9 and re-add it with a different size. Note that the volume header " +"must start at sector 0." +msgstr "" + +#. Tag: title +#: partitioning.xml:804 +#, no-c-format +msgid "Partitioning Newer PowerMacs" +msgstr "" + +#. Tag: para +#: partitioning.xml:805 +#, no-c-format +msgid "" +"If you are installing onto a NewWorld PowerMac you must create a special " +"bootstrap partition to hold the boot loader. The size of this partition must " +"have at least 819200 bytes and its partition type must be " +"<emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is not " +"created with the <emphasis>Apple_Bootstrap</emphasis> type your machine " +"cannot be made bootable from the hard disk. This partition can easily be " +"created by creating a new partition in <command>partman</command> and " +"telling it to use it as a <quote>NewWorld boot partition</quote>, or in " +"<command>mac-fdisk</command> using the <userinput>b</userinput> command." +msgstr "" + +#. Tag: para +#: partitioning.xml:818 +#, no-c-format +msgid "" +"The special partition type Apple_Bootstrap is required to prevent MacOS from " +"mounting and damaging the bootstrap partition, as there are special " +"modifications made to it in order for OpenFirmware to boot it automatically." +msgstr "" + +#. Tag: para +#: partitioning.xml:825 +#, no-c-format +msgid "" +"Note that the bootstrap partition is only meant to hold 3 very small files: " +"the <command>yaboot</command> binary, its configuration <filename>yaboot." +"conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</" +"command>. It need not and must not be mounted on your file system nor have " +"kernels or anything else copied to it. The <command>ybin</command> and " +"<command>mkofboot</command> utilities are used to manipulate this partition." +msgstr "" + +#. Tag: para +#: partitioning.xml:835 +#, no-c-format +msgid "" +"In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap " +"partition should appear before other boot partitions on the disk, especially " +"MacOS boot partitions. The bootstrap partition should be the first one you " +"create. However, if you add a bootstrap partition later, you can use " +"<command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder " +"the partition map so the bootstrap partition comes right after the map " +"(which is always partition 1). It's the logical map order, not the physical " +"address order, that counts." +msgstr "" + +#. Tag: para +#: partitioning.xml:847 +#, no-c-format +msgid "" +"Apple disks normally have several small driver partitions. If you intend to " +"dual boot your machine with MacOSX, you should retain these partitions and a " +"small HFS partition (800k is the minimum size). That is because MacOSX, on " +"every boot, offers to initialize any disks which do not have active MacOS " +"partitions and driver partitions." +msgstr "" + +#. Tag: para +#: partitioning.xml:864 +#, no-c-format +msgid "" +"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. The <keycap>s</keycap> key " +"is used in <command>fdisk</command> to create Sun disk labels." +msgstr "" + +#. Tag: para +#: partitioning.xml:872 +#, no-c-format +msgid "" +"Furthermore, on &arch-title; disks, make sure your first partition on your " +"boot disk starts at cylinder 0. While this is required, it also means that " +"the first partition will contain the partition table and the boot block, " +"which are the first two sectors of the disk. You must <emphasis>not</" +"emphasis> put swap on the first partition of the boot drive, since swap " +"partitions do not preserve the first few sectors of the partition. You can " +"put Ext2 or UFS partitions there; these will leave the partition table and " +"the boot block alone." +msgstr "" + +#. Tag: para +#: partitioning.xml:883 +#, no-c-format +msgid "" +"It is also advised that the third partition should be of type <quote>Whole " +"disk</quote> (type 5), and contain the entire disk (from the first cylinder " +"to the last). This is simply a convention of Sun disk labels, and helps the " +"<command>SILO</command> boot loader keep its bearings." +msgstr "" diff --git a/po/kab/post-install.po b/po/kab/post-install.po new file mode 100644 index 000000000..a4a3d9841 --- /dev/null +++ b/po/kab/post-install.po @@ -0,0 +1,679 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-post-install 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2019-08-11 15:17+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: post-install.xml:5 +#, no-c-format +msgid "Next Steps and Where to Go From Here" +msgstr "" + +#. Tag: title +#: post-install.xml:13 +#, no-c-format +msgid "Shutting down the system" +msgstr "" + +#. Tag: para +#: post-install.xml:15 +#, no-c-format +msgid "" +"To shut down a running &debian-gnu; system, you must not reboot with the " +"reset switch on the front or back of your computer, or just turn off the " +"computer. &debian-gnu; should be shut down in a controlled manner, otherwise " +"files might get lost and/or disk damage might occur. If you run a desktop " +"environment, there is usually an option to <quote>log out</quote> available " +"from the application menu that allows you to shutdown (or reboot) the system." +msgstr "" + +#. Tag: para +#: post-install.xml:25 +#, no-c-format +msgid "" +"Alternatively you can press the key combination <keycombo> <keycap>Ctrl</" +"keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> <phrase arch=" +"\"powerpc\"> or <keycombo> <keycap>Control</keycap> <keycap>Shift</keycap> " +"<keycap>Power</keycap> </keycombo> on Macintosh systems</phrase>. If the key " +"combinations do not work, a last option is to log in as root and type the " +"necessary commands. Use <command>reboot</command> to reboot the system. Use " +"<command>halt</command> to halt the system without powering it off " +"<footnote> <para> Under the SysV init system <command>halt</command> had the " +"same effect as <command>poweroff</command>, but with systemd as init system " +"(the default since jessie) their effects are different. </para> </footnote>. " +"To power off the machine, use <command>poweroff</command> or " +"<command>shutdown -h now</command>. The systemd init system provides " +"additional commands that perform the same functions; for example " +"<command>systemctl reboot</command> or <command>systemctl poweroff</command>." +msgstr "" + +#. Tag: title +#: post-install.xml:60 +#, no-c-format +msgid "Orienting Yourself to &debian;" +msgstr "" + +#. Tag: para +#: post-install.xml:61 +#, no-c-format +msgid "" +"&debian; is a little different from other distributions. Even if you're " +"familiar with Linux in other distributions, there are things you should know " +"about &debian; to help you to keep your system in a good, clean state. This " +"chapter contains material to help you get oriented; it is not intended to be " +"a tutorial for how to use &debian;, but just a very brief glimpse of the " +"system for the very rushed." +msgstr "" + +#. Tag: title +#: post-install.xml:72 +#, no-c-format +msgid "&debian; Packaging System" +msgstr "" + +#. Tag: para +#: post-install.xml:73 +#, no-c-format +msgid "" +"The most important concept to grasp is the &debian; packaging system. In " +"essence, large parts of your system should be considered under the control " +"of the packaging system. These include: <itemizedlist> <listitem><para> " +"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </" +"para></listitem> <listitem><para> <filename>/var</filename> (you could make " +"<filename>/var/local</filename> and be safe in there) </para></listitem> " +"<listitem><para> <filename>/bin</filename> </para></listitem> " +"<listitem><para> <filename>/sbin</filename> </para></listitem> " +"<listitem><para> <filename>/lib</filename> </para></listitem> </" +"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</" +"filename>, that will work, but then if you upgrade your <classname>perl</" +"classname> package, the file you put there will be replaced. Experts can get " +"around this by putting packages on <quote>hold</quote> in <command>aptitude</" +"command>." +msgstr "" + +#. Tag: para +#: post-install.xml:114 +#, no-c-format +msgid "" +"One of the best installation methods is apt. You can use the command line " +"version of <command>apt</command> as well as tools like " +"<application>aptitude</application> or <application>synaptic</application> " +"(which are just graphical frontends for <command>apt</command>). Note that " +"apt will also let you merge main, contrib, and non-free so you can have " +"restricted packages (strictly speaking not belonging to &debian;) as well as " +"packages from &debian-gnu; at the same time." +msgstr "" + +#. Tag: title +#: post-install.xml:128 +#, no-c-format +msgid "Additional Software Available for &debian;" +msgstr "" + +#. Tag: para +#: post-install.xml:129 +#, no-c-format +msgid "" +"There are official and unofficial software repositories that are not enabled " +"in the default &debian; install. These contain software which many find " +"important and expect to have. Information on these additional repositories " +"can be found on the &debian; Wiki page titled <ulink url=\"&url-debian-wiki-" +"software;\">The Software Available for &debian;'s Stable Release</ulink>." +msgstr "" + +#. Tag: title +#: post-install.xml:141 +#, no-c-format +msgid "Application Version Management" +msgstr "" + +#. Tag: para +#: post-install.xml:142 +#, no-c-format +msgid "" +"Alternative versions of applications are managed by update-alternatives. If " +"you are maintaining multiple versions of your applications, read the update-" +"alternatives man page." +msgstr "" + +#. Tag: title +#: post-install.xml:152 +#, no-c-format +msgid "Cron Job Management" +msgstr "" + +#. Tag: para +#: post-install.xml:153 +#, no-c-format +msgid "" +"Any jobs under the purview of the system administrator should be in " +"<filename>/etc</filename>, since they are configuration files. If you have a " +"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/" +"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/" +"etc/crontab</filename>, and will run in alphabetic order, which serializes " +"them." +msgstr "" + +#. Tag: para +#: post-install.xml:162 +#, no-c-format +msgid "" +"On the other hand, if you have a cron job that (a) needs to run as a special " +"user, or (b) needs to run at a special time or frequency, you can use either " +"<filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/" +"whatever</filename>. These particular files also have an extra field that " +"allows you to stipulate the user account under which the cron job runs." +msgstr "" + +#. Tag: para +#: post-install.xml:171 +#, no-c-format +msgid "" +"In either case, you just edit the files and cron will notice them " +"automatically. There is no need to run a special command. For more " +"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/" +"README.Debian</filename>." +msgstr "" + +#. Tag: title +#: post-install.xml:186 +#, no-c-format +msgid "Further Reading and Information" +msgstr "" + +#. Tag: para +#: post-install.xml:187 +#, no-c-format +msgid "" +"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a " +"large quantity of documentation about &debian;. In particular, see the " +"<ulink url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> " +"and the <ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference" +"\">Debian Reference</ulink>. An index of more &debian; documentation is " +"available from the <ulink url=\"http://www.debian.org/doc/ddp\">Debian " +"Documentation Project</ulink>. The &debian; community is self-supporting; to " +"subscribe to one or more of the Debian mailing lists, see the <ulink url=" +"\"http://www.debian.org/MailingLists/subscribe\"> Mail List Subscription</" +"ulink> page. Last, but not least, the <ulink url=\"http://lists.debian.org/" +"\">Debian Mailing List Archives</ulink> contain a wealth of information on " +"&debian;." +msgstr "" + +#. Tag: para +#: post-install.xml:205 +#, no-c-format +msgid "" +"If you need information about a particular program, you should first try " +"<userinput>man <replaceable>program</replaceable></userinput>, or " +"<userinput>info <replaceable>program</replaceable></userinput>." +msgstr "" + +#. Tag: para +#: post-install.xml:211 +#, no-c-format +msgid "" +"There is lots of useful documentation in <filename>/usr/share/doc</filename> " +"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and " +"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting " +"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</" +"filename>. To read about &debian;-specific issues for particular programs, " +"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>." +msgstr "" + +#. Tag: para +#: post-install.xml:222 +#, no-c-format +msgid "" +"A general source of information on GNU/Linux is the <ulink url=\"http://www." +"tldp.org/\">Linux Documentation Project</ulink>. There you will find the " +"HOWTOs and pointers to other very valuable information on parts of a GNU/" +"Linux system." +msgstr "" + +#. Tag: para +#: post-install.xml:229 +#, no-c-format +msgid "" +"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux " +"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online " +"books relating to Linux." +msgstr "" + +#. Tag: para +#: post-install.xml:236 +#, no-c-format +msgid "" +"If you are new to Unix, you probably should go out and buy some books and do " +"some reading. This <ulink url=\"&url-unix-faq;\">list of Unix FAQs</ulink> " +"contains a number of UseNet documents which provide a nice historical " +"reference." +msgstr "" + +#. Tag: title +#: post-install.xml:251 +#, no-c-format +msgid "Setting Up Your System To Use E-Mail" +msgstr "" + +#. Tag: para +#: post-install.xml:252 +#, no-c-format +msgid "" +"Today, email is an important part of many people's life. As there are many " +"options as to how to set it up, and as having it set up correctly is " +"important for some &debian; utilities, we will try to cover the basics in " +"this section." +msgstr "" + +#. Tag: para +#: post-install.xml:259 +#, no-c-format +msgid "" +"There are three main functions that make up an e-mail system. First there is " +"the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user " +"actually uses to compose and read mails. Then there is the <firstterm>Mail " +"Transfer Agent</firstterm> (MTA) that takes care of transferring messages " +"from one computer to another. And last there is the <firstterm>Mail Delivery " +"Agent</firstterm> (MDA) that takes care of delivering incoming mail to the " +"user's inbox." +msgstr "" + +#. Tag: para +#: post-install.xml:269 +#, no-c-format +msgid "" +"These three functions can be performed by separate programs, but they can " +"also be combined in one or two programs. It is also possible to have " +"different programs handle these functions for different types of mail." +msgstr "" + +#. Tag: para +#: post-install.xml:275 +#, no-c-format +msgid "" +"On Linux and Unix systems <command>mutt</command> is historically a very " +"popular MUA. Like most traditional Linux programs it is text based. It is " +"often used in combination with <command>exim</command> or <command>sendmail</" +"command> as MTA and <command>procmail</command> as MDA." +msgstr "" + +#. Tag: para +#: post-install.xml:282 +#, no-c-format +msgid "" +"With the increasing popularity of graphical desktop systems, the use of " +"graphical e-mail programs like GNOME's <command>evolution</command>, KDE's " +"<command>kmail</command> or Mozilla's <command>thunderbird</command> has " +"becoming more popular. These programs combine the function of a MUA, MTA and " +"MDA, but can — and often are — also be used in combination with " +"the traditional Linux tools." +msgstr "" + +#. Tag: title +#: post-install.xml:294 +#, no-c-format +msgid "Default E-Mail Configuration" +msgstr "" + +#. Tag: para +#: post-install.xml:295 +#, no-c-format +msgid "" +"Even if you are planning to use a graphical mail program, it would be " +"useful, to have a traditional MTA/MDA installed and correctly set up on your " +"&debian-gnu; system. Reason is that various utilities running on the " +"system<footnote> <para> Examples are: <command>cron</command>, " +"<command>quota</command>, <command>logcheck</command>, <command>aide</" +"command>, … </para> </footnote> can send important notices by e-mail " +"to inform the system administrator of (potential) problems or changes." +msgstr "" + +#. Tag: para +#: post-install.xml:310 +#, no-c-format +msgid "" +"For this you can install <classname>exim4</classname> and <classname>mutt</" +"classname> with <command>apt install exim4 mutt</command>. <classname>exim4</" +"classname> is a combination MTA/MDA that is relatively small but very " +"flexible. By default it will be configured to only handle e-mail local to " +"the system itself and e-mails addressed to the system administrator (root " +"account) will be delivered to the regular user account created during the " +"installation<footnote> <para> The forwarding of mail for root to the regular " +"user account is configured in <filename>/etc/aliases</filename>. If no " +"regular user account was created, the mail will of course be delivered to " +"the root account itself. </para> </footnote>." +msgstr "" + +#. Tag: para +#: post-install.xml:328 +#, no-c-format +msgid "" +"When system e-mails are delivered they are added to a file in <filename>/var/" +"mail/<replaceable>account_name</replaceable></filename>. The e-mails can be " +"read using <command>mutt</command>." +msgstr "" + +#. Tag: title +#: post-install.xml:338 +#, no-c-format +msgid "Sending E-Mails Outside The System" +msgstr "" + +#. Tag: para +#: post-install.xml:339 +#, no-c-format +msgid "" +"As mentioned earlier, the installed &debian; system is only set up to handle " +"e-mail local to the system, not for sending mail to others nor for receiving " +"mail from others." +msgstr "" + +#. Tag: para +#: post-install.xml:345 +#, no-c-format +msgid "" +"If you would like <classname>exim4</classname> to handle external e-mail, " +"please refer to the next subsection for the basic available configuration " +"options. Make sure to test that mail can be sent and received correctly." +msgstr "" + +#. Tag: para +#: post-install.xml:351 +#, no-c-format +msgid "" +"If you intend to use a graphical mail program and use a mail server of your " +"Internet Service Provider (ISP) or your company, there is not really any " +"need to configure <classname>exim4</classname> for handling external e-mail. " +"Just configure your favorite graphical mail program to use the correct " +"servers to send and receive e-mail (how is outside the scope of this manual)." +msgstr "" + +#. Tag: para +#: post-install.xml:360 +#, no-c-format +msgid "" +"However, in that case you may need to configure individual utilities to " +"correctly send e-mails. One such utility is <command>reportbug</command>, a " +"program that facilitates submitting bug reports against &debian; packages. " +"By default it expects to be able to use <classname>exim4</classname> to " +"submit bug reports." +msgstr "" + +#. Tag: para +#: post-install.xml:368 +#, no-c-format +msgid "" +"To correctly set up <command>reportbug</command> to use an external mail " +"server, please run the command <command>reportbug --configure</command> and " +"answer <quote>no</quote> to the question if an MTA is available. You will " +"then be asked for the SMTP server to be used for submitting bug reports." +msgstr "" + +#. Tag: title +#: post-install.xml:379 +#, no-c-format +msgid "Configuring the Exim4 Mail Transport Agent" +msgstr "" + +#. Tag: para +#: post-install.xml:380 +#, no-c-format +msgid "" +"If you would like your system to also handle external e-mail, you will need " +"to reconfigure the <classname>exim4</classname> package<footnote> <para> You " +"can of course also remove <classname>exim4</classname> and replace it with " +"an alternative MTA/MDA. </para> </footnote>:" +msgstr "" + +#. Tag: screen +#: post-install.xml:392 +#, no-c-format +msgid "# dpkg-reconfigure exim4-config" +msgstr "" + +#. Tag: para +#: post-install.xml:394 +#, no-c-format +msgid "" +"After entering that command (as root), you will be asked if you want split " +"the configuration into small files. If you are unsure, select the default " +"option." +msgstr "" + +#. Tag: para +#: post-install.xml:400 +#, no-c-format +msgid "" +"Next you will be presented with several common mail scenarios. Choose the " +"one that most closely resembles your needs." +msgstr "" + +#. Tag: term +#: post-install.xml:409 +#, no-c-format +msgid "internet site" +msgstr "" + +#. Tag: para +#: post-install.xml:410 +#, no-c-format +msgid "" +"Your system is connected to a network and your mail is sent and received " +"directly using SMTP. On the following screens you will be asked a few basic " +"questions, like your machine's mail name, or a list of domains for which you " +"accept or relay mail." +msgstr "" + +#. Tag: term +#: post-install.xml:421 +#, no-c-format +msgid "mail sent by smarthost" +msgstr "" + +#. Tag: para +#: post-install.xml:422 +#, no-c-format +msgid "" +"In this scenario your outgoing mail is forwarded to another machine, called " +"a <quote>smarthost</quote>, which takes care of sending the message on to " +"its destination. The smarthost also usually stores incoming mail addressed " +"to your computer, so you don't need to be permanently online. That also " +"means you have to download your mail from the smarthost via programs like " +"fetchmail." +msgstr "" + +#. Tag: para +#: post-install.xml:432 +#, no-c-format +msgid "" +"In a lot of cases the smarthost will be your ISP's mail server, which makes " +"this option very suitable for dial-up users. It can also be a company mail " +"server, or even another system on your own network." +msgstr "" + +#. Tag: term +#: post-install.xml:442 +#, no-c-format +msgid "mail sent by smarthost; no local mail" +msgstr "" + +#. Tag: para +#: post-install.xml:443 +#, no-c-format +msgid "" +"This option is basically the same as the previous one except that the system " +"will not be set up to handle mail for a local e-mail domain. Mail on the " +"system itself (e.g. for the system administrator) will still be handled." +msgstr "" + +#. Tag: term +#: post-install.xml:454 +#, no-c-format +msgid "local delivery only" +msgstr "" + +#. Tag: para +#: post-install.xml:455 +#, no-c-format +msgid "This is the option your system is configured for by default." +msgstr "" + +#. Tag: term +#: post-install.xml:463 +#, no-c-format +msgid "no configuration at this time" +msgstr "" + +#. Tag: para +#: post-install.xml:464 +#, no-c-format +msgid "" +"Choose this if you are absolutely convinced you know what you are doing. " +"This will leave you with an unconfigured mail system — until you " +"configure it, you won't be able to send or receive any mail and you may miss " +"some important messages from your system utilities." +msgstr "" + +#. Tag: para +#: post-install.xml:475 +#, no-c-format +msgid "" +"If none of these scenarios suits your needs, or if you need a finer grained " +"setup, you will need to edit configuration files under the <filename>/etc/" +"exim4</filename> directory after the installation is complete. More " +"information about <classname>exim4</classname> may be found under <filename>/" +"usr/share/doc/exim4</filename>; the file <filename>README.Debian.gz</" +"filename> has further details about configuring <classname>exim4</classname> " +"and explains where to find additional documentation." +msgstr "" + +#. Tag: para +#: post-install.xml:486 +#, no-c-format +msgid "" +"Note that sending mail directly to the Internet when you don't have an " +"official domain name, can result in your mail being rejected because of anti-" +"spam measures on receiving servers. Using your ISP's mail server is " +"preferred. If you still do want to send out mail directly, you may want to " +"use a different e-mail address than is generated by default. If you use " +"<classname>exim4</classname> as your MTA, this is possible by adding an " +"entry in <filename>/etc/email-addresses</filename>." +msgstr "" + +#. Tag: title +#: post-install.xml:504 +#, no-c-format +msgid "Compiling a New Kernel" +msgstr "" + +#. Tag: para +#: post-install.xml:505 +#, no-c-format +msgid "" +"Why would someone want to compile a new kernel? It is most probably not " +"necessary since the default kernel shipped with &debian; handles almost all " +"configurations." +msgstr "" + +#. Tag: para +#: post-install.xml:511 +#, no-c-format +msgid "" +"If you want to compile your own kernel nevertheless, this is of course " +"possible and we recommend the use of the <quote>make deb-pkg</quote> target. " +"For more information read the <ulink url=\"&url-kernel-handbook;\">Debian " +"Linux Kernel Handbook</ulink>." +msgstr "" + +#. Tag: title +#: post-install.xml:526 +#, no-c-format +msgid "Recovering a Broken System" +msgstr "" + +#. Tag: para +#: post-install.xml:527 +#, no-c-format +msgid "" +"Sometimes, things go wrong, and the system you've carefully installed is no " +"longer bootable. Perhaps the boot loader configuration broke while trying " +"out a change, or perhaps a new kernel you installed won't boot, or perhaps " +"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</" +"filename>. Regardless of the cause, you'll need to have a system to work " +"from while you fix it, and rescue mode can be useful for this." +msgstr "" + +#. Tag: para +#: post-install.xml:537 +#, no-c-format +msgid "" +"To access rescue mode, select <userinput>rescue</userinput> from the boot " +"menu, type <userinput>rescue</userinput> at the <prompt>boot:</prompt> " +"prompt, or boot with the <userinput>rescue/enable=true</userinput> boot " +"parameter. You'll be shown the first few screens of the installer, with a " +"note in the corner of the display to indicate that this is rescue mode, not " +"a full installation. Don't worry, your system is not about to be " +"overwritten! Rescue mode simply takes advantage of the hardware detection " +"facilities available in the installer to ensure that your disks, network " +"devices, and so on are available to you while repairing your system." +msgstr "" + +#. Tag: para +#: post-install.xml:554 +#, no-c-format +msgid "" +"Instead of the partitioning tool, you should now be presented with a list of " +"the partitions on your system, and asked to select one of them. Normally, " +"you should select the partition containing the root file system that you " +"need to repair. You may select partitions on RAID and LVM devices as well as " +"those created directly on disks." +msgstr "" + +#. Tag: para +#: post-install.xml:562 +#, no-c-format +msgid "" +"If possible, the installer will now present you with a shell prompt in the " +"file system you selected, which you can use to perform any necessary " +"repairs. <phrase arch=\"any-x86\"> For example, if you need to reinstall the " +"GRUB boot loader into the master boot record of the first hard disk, you " +"could enter the command <userinput>grub-install '(hd0)'</userinput> to do " +"so. </phrase>" +msgstr "" + +#. Tag: para +#: post-install.xml:574 +#, no-c-format +msgid "" +"If the installer cannot run a usable shell in the root file system you " +"selected, perhaps because the file system is corrupt, then it will issue a " +"warning and offer to give you a shell in the installer environment instead. " +"You may not have as many tools available in this environment, but they will " +"often be enough to repair your system anyway. The root file system you " +"selected will be mounted on the <filename>/target</filename> directory." +msgstr "" + +#. Tag: para +#: post-install.xml:583 +#, no-c-format +msgid "In either case, after you exit the shell, the system will reboot." +msgstr "" + +#. Tag: para +#: post-install.xml:587 +#, no-c-format +msgid "" +"Finally, note that repairing broken systems can be difficult, and this " +"manual does not attempt to go into all the things that might have gone wrong " +"or how to fix them. If you have problems, consult an expert." +msgstr "" diff --git a/po/kab/preface.po b/po/kab/preface.po new file mode 100644 index 000000000..d0504daf9 --- /dev/null +++ b/po/kab/preface.po @@ -0,0 +1,53 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-preface 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2016-12-29 08:03+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: preface.xml:5 +#, no-c-format +msgid "Installing &debian-gnu; &release; for &architecture;" +msgstr "" + +#. Tag: para +#: preface.xml:6 +#, no-c-format +msgid "" +"We are delighted that you have decided to try &debian;, and are sure that " +"you will find that &debian;'s GNU/&arch-kernel; distribution is unique. " +"&debian-gnu; brings together high-quality free software from around the " +"world, integrating it into a coherent whole. We believe that you will find " +"that the result is truly more than the sum of the parts." +msgstr "" + +#. Tag: para +#: preface.xml:15 +#, no-c-format +msgid "" +"We understand that many of you want to install &debian; without reading this " +"manual, and the &debian; installer is designed to make this possible. If you " +"don't have time to read the whole Installation Guide right now, we recommend " +"that you read the Installation Howto, which will walk you through the basic " +"installation process, and links to the manual for more advanced topics or " +"for when things go wrong. The Installation Howto can be found in <xref " +"linkend=\"installation-howto\"/>." +msgstr "" + +#. Tag: para +#: preface.xml:25 +#, no-c-format +msgid "" +"With that said, we hope that you have the time to read most of this manual, " +"and doing so will lead to a more informed and likely more successful " +"installation experience." +msgstr "" diff --git a/po/kab/preparing.po b/po/kab/preparing.po new file mode 100644 index 000000000..09e72700f --- /dev/null +++ b/po/kab/preparing.po @@ -0,0 +1,2344 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-preparing 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-12-11 21:39+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: preparing.xml:5 +#, no-c-format +msgid "Before Installing &debian-gnu;" +msgstr "" + +#. Tag: para +#: preparing.xml:6 +#, no-c-format +msgid "" +"This chapter deals with the preparation for installing &debian; before you " +"even boot the installer. This includes backing up your data, gathering " +"information about your hardware, and locating any necessary information." +msgstr "" + +#. Tag: title +#: preparing.xml:19 +#, no-c-format +msgid "Overview of the Installation Process" +msgstr "" + +#. Tag: para +#: preparing.xml:20 +#, no-c-format +msgid "" +"First, just a note about re-installations. With &debian;, a circumstance " +"that will require a complete re-installation of your system is very rare; " +"perhaps mechanical failure of the hard disk would be the most common case." +msgstr "" + +#. Tag: para +#: preparing.xml:27 +#, no-c-format +msgid "" +"Many common operating systems may require a complete installation to be " +"performed when critical failures take place or for upgrades to new OS " +"versions. Even if a completely new installation isn't required, often the " +"programs you use must be re-installed to operate properly in the new OS." +msgstr "" + +#. Tag: para +#: preparing.xml:35 +#, no-c-format +msgid "" +"Under &debian-gnu;, it is much more likely that your OS can be repaired " +"rather than replaced if things go wrong. Upgrades never require a wholesale " +"installation; you can always upgrade in-place. And the programs are almost " +"always compatible with successive OS releases. If a new program version " +"requires newer supporting software, the &debian; packaging system ensures " +"that all the necessary software is automatically identified and installed. " +"The point is, much effort has been put into avoiding the need for re-" +"installation, so think of it as your very last option. The installer is " +"<emphasis>not</emphasis> designed to re-install over an existing system." +msgstr "" + +#. Tag: para +#: preparing.xml:48 +#, no-c-format +msgid "" +"Here's a road map for the steps you will take during the installation " +"process." +msgstr "" + +#. Tag: para +#: preparing.xml:56 +#, no-c-format +msgid "" +"Back up any existing data or documents on the hard disk where you plan to " +"install." +msgstr "" + +#. Tag: para +#: preparing.xml:62 +#, no-c-format +msgid "" +"Gather information about your computer and any needed documentation, before " +"starting the installation." +msgstr "" + +#. Tag: para +#: preparing.xml:68 +#, no-c-format +msgid "Create partitionable space for &debian; on your hard disk." +msgstr "" + +#. Tag: para +#: preparing.xml:73 +#, no-c-format +msgid "" +"Locate and/or download the installer software and any specialized driver or " +"firmware files your machine requires." +msgstr "" + +#. Tag: para +#: preparing.xml:79 +#, no-c-format +msgid "" +"Set up boot media such as CDs/DVDs/USB sticks or provide a network boot " +"infrastructure from which the installer can be booted." +msgstr "" + +#. Tag: para +#: preparing.xml:85 +#, no-c-format +msgid "Boot the installation system." +msgstr "" + +#. Tag: para +#: preparing.xml:90 +#, no-c-format +msgid "Select the installation language." +msgstr "" + +#. Tag: para +#: preparing.xml:95 +#, no-c-format +msgid "Activate the ethernet network connection, if available." +msgstr "" + +#. Tag: para +#: preparing.xml:101 +#, no-c-format +msgid "Configure one network interface." +msgstr "" + +#. Tag: para +#: preparing.xml:106 +#, no-c-format +msgid "Open an ssh connection to the new system." +msgstr "" + +#. Tag: para +#: preparing.xml:111 +#, no-c-format +msgid "Attach one or more DASDs (Direct Access Storage Device)." +msgstr "" + +#. Tag: para +#: preparing.xml:117 +#, no-c-format +msgid "" +"If necessary, resize existing partitions on your target harddisk to make " +"space for the installation." +msgstr "" + +#. Tag: para +#: preparing.xml:122 +#, no-c-format +msgid "Create and mount the partitions on which &debian; will be installed." +msgstr "" + +#. Tag: para +#: preparing.xml:127 +#, no-c-format +msgid "" +"Watch the automatic download/install/setup of the <firstterm>base system</" +"firstterm>." +msgstr "" + +#. Tag: para +#: preparing.xml:133 +#, no-c-format +msgid "Select and install <firstterm>additional software</firstterm>." +msgstr "" + +#. Tag: para +#: preparing.xml:138 +#, no-c-format +msgid "" +"Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; " +"and/or your existing system." +msgstr "" + +#. Tag: para +#: preparing.xml:144 +#, no-c-format +msgid "Load the newly installed system for the first time." +msgstr "" + +#. Tag: para +#: preparing.xml:151 +#, no-c-format +msgid "" +"For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</" +"phrase> <phrase arch=\"arm64\">an experimental</phrase> <phrase arch=" +"\"powerpc\">an experimental</phrase> graphical version of the installation " +"system. For more information about this graphical installer, see <xref " +"linkend=\"graphical\"/>." +msgstr "" + +#. Tag: para +#: preparing.xml:160 +#, no-c-format +msgid "" +"If you have problems during the installation, it helps to know which " +"packages are involved in which steps. Introducing the leading software " +"actors in this installation drama:" +msgstr "" + +#. Tag: para +#: preparing.xml:166 +#, 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, 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:178 +#, 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:184 +#, no-c-format +msgid "" +"One important option during the installation is whether or not to install a " +"graphical desktop environment, consisting of the X 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 in relation to a text-mode-only system it requires a " +"comparatively large amount of disk space and because many &debian-gnu; " +"systems are servers which don't really have any need for a graphical user " +"interface to do their job." +msgstr "" + +#. Tag: para +#: preparing.xml:197 +#, no-c-format +msgid "" +"Just be aware that the X Window System is completely separate from " +"<classname>debian-installer</classname>, and in fact is much more " +"complicated. Troubleshooting of the X Window System is not within the scope " +"of this manual." +msgstr "" + +#. Tag: title +#: preparing.xml:212 +#, no-c-format +msgid "Back Up Your Existing Data!" +msgstr "" + +#. Tag: para +#: preparing.xml:213 +#, 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 is going to " +"be installed on your computer, it is quite likely you will need to re-" +"partition your disk to make room for &debian-gnu;. 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 the installation of &debian-" +"gnu; 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:226 +#, 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. Even " +"though this is normally not necessary, there might be situations in which " +"you could be required to reinstall your operating system's boot loader to " +"make the system boot or in a worst case even have to reinstall the complete " +"operating system and restore your previously made backup." +msgstr "" + +#. Tag: title +#: preparing.xml:245 +#, no-c-format +msgid "Information You Will Need" +msgstr "" + +#. Tag: title +#: preparing.xml:248 +#, no-c-format +msgid "Documentation" +msgstr "" + +#. Tag: title +#: preparing.xml:251 +#, no-c-format +msgid "Installation Manual" +msgstr "" + +#. Tag: para +#: preparing.xml:253 +#, no-c-format +msgid "This document you are now reading, in plain ASCII, HTML or PDF format." +msgstr "" + +#. Tag: itemizedlist +#: preparing.xml:259 +#, no-c-format +msgid "&list-install-manual-files;" +msgstr "" + +#. Tag: para +#: preparing.xml:265 +#, 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:274 +#, 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-dillon-manual;\">various formats and translations</ulink>." +msgstr "" + +#. Tag: title +#: preparing.xml:286 +#, no-c-format +msgid "Hardware documentation" +msgstr "" + +#. Tag: para +#: preparing.xml:287 +#, no-c-format +msgid "" +"Often contains useful information on configuring or using your hardware." +msgstr "" + +#. Tag: ulink +#: preparing.xml:298 +#, no-c-format +msgid "The Debian Wiki hardware page" +msgstr "" + +#. Tag: ulink +#: preparing.xml:304 +#, no-c-format +msgid "Linux for SPARC Processors FAQ" +msgstr "" + +#. Tag: ulink +#: preparing.xml:310 +#, no-c-format +msgid "Linux/MIPS website" +msgstr "" + +#. Tag: title +#: preparing.xml:319 +#, no-c-format +msgid "&arch-title; Hardware References" +msgstr "" + +#. Tag: para +#: preparing.xml:320 +#, no-c-format +msgid "" +"Documentation of &arch-title;-specific boot sequence, commands and device " +"drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)" +msgstr "" + +#. Tag: ulink +#: preparing.xml:331 +#, no-c-format +msgid "Device Drivers, Features, and Commands (Linux Kernel 3.2)" +msgstr "" + +#. Tag: para +#: preparing.xml:336 +#, 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:346 +#, no-c-format +msgid "Linux for &arch-title;" +msgstr "" + +#. Tag: para +#: preparing.xml:352 +#, 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:363 +#, no-c-format +msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions" +msgstr "" + +#. Tag: title +#: preparing.xml:373 +#, no-c-format +msgid "Finding Sources of Hardware Information" +msgstr "" + +#. Tag: para +#: preparing.xml:374 +#, 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:380 +#, no-c-format +msgid "Hardware information can be gathered from:" +msgstr "" + +#. Tag: para +#: preparing.xml:387 +#, no-c-format +msgid "The manuals that come with each piece of hardware." +msgstr "" + +#. Tag: para +#: preparing.xml:392 +#, no-c-format +msgid "" +"The BIOS/UEFI 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> or the " +"<keycap>F2</keycap> key, but some manufacturers use other keys or key " +"combinations. Usually upon starting the computer there will be a message " +"stating which key to press to enter the setup screen." +msgstr "" + +#. Tag: para +#: preparing.xml:402 +#, no-c-format +msgid "The cases and boxes for each piece of hardware." +msgstr "" + +#. Tag: para +#: preparing.xml:408 +#, no-c-format +msgid "The System window in the Windows Control Panel." +msgstr "" + +#. Tag: para +#: 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: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:433 +#, no-c-format +msgid "Hardware Information Helpful for an Install" +msgstr "" + +#. Tag: entry +#: preparing.xml:437 +#, no-c-format +msgid "Hardware" +msgstr "" + +#. Tag: entry +#: preparing.xml:437 +#, no-c-format +msgid "Information You Might Need" +msgstr "" + +#. Tag: entry +#: preparing.xml:443 +#, no-c-format +msgid "Hard Drives" +msgstr "" + +#. Tag: entry +#: preparing.xml:444 +#, no-c-format +msgid "How many you have." +msgstr "" + +#. Tag: entry +#: preparing.xml:446 +#, no-c-format +msgid "Their order on the system." +msgstr "" + +#. Tag: entry +#: preparing.xml:448 +#, no-c-format +msgid "Whether IDE (also known as PATA), SATA or SCSI." +msgstr "" + +#. Tag: entry +#: preparing.xml:450 preparing.xml:499 +#, no-c-format +msgid "Available free space." +msgstr "" + +#. Tag: entry +#: preparing.xml:451 +#, no-c-format +msgid "Partitions." +msgstr "" + +#. Tag: entry +#: preparing.xml:453 +#, no-c-format +msgid "Partitions where other operating systems are installed." +msgstr "" + +#. Tag: entry +#: preparing.xml:481 +#, no-c-format +msgid "Network interfaces" +msgstr "" + +#. Tag: entry +#: preparing.xml:482 +#, no-c-format +msgid "Type/model of available network interfaces." +msgstr "" + +#. Tag: entry +#: preparing.xml:486 +#, no-c-format +msgid "Printer" +msgstr "" + +#. Tag: entry +#: preparing.xml:487 +#, no-c-format +msgid "Model and manufacturer." +msgstr "" + +#. Tag: entry +#: preparing.xml:491 +#, no-c-format +msgid "Video Card" +msgstr "" + +#. Tag: entry +#: preparing.xml:492 +#, no-c-format +msgid "Type/model and manufacturer." +msgstr "" + +#. Tag: entry +#: preparing.xml:496 +#, no-c-format +msgid "DASD" +msgstr "" + +#. Tag: entry +#: preparing.xml:497 +#, no-c-format +msgid "Device number(s)." +msgstr "" + +#. Tag: entry +#: preparing.xml:502 +#, no-c-format +msgid "Network" +msgstr "" + +#. Tag: entry +#: preparing.xml:503 +#, no-c-format +msgid "Type of adapter." +msgstr "" + +#. Tag: entry +#: preparing.xml:505 +#, no-c-format +msgid "Device numbers." +msgstr "" + +#. Tag: entry +#: preparing.xml:506 +#, no-c-format +msgid "Relative adapter number for OSA cards." +msgstr "" + +#. Tag: title +#: preparing.xml:514 +#, no-c-format +msgid "Hardware Compatibility" +msgstr "" + +#. Tag: para +#: preparing.xml:516 +#, no-c-format +msgid "" +"Many products work without trouble on &arch-kernel;. Moreover, hardware " +"support in &arch-kernel; is improving daily. However, &arch-kernel; still " +"does not run as many different types of hardware as some operating systems." +msgstr "" + +#. Tag: para +#: preparing.xml:522 +#, no-c-format +msgid "" +"Drivers in &arch-kernel; in most cases are not written for a certain " +"<quote>product</quote> or <quote>brand</quote> from a specific manufacturer, " +"but for a certain hardware/chipset. Many seemingly different products/brands " +"are based on the same hardware design; it is not uncommon that chip " +"manufacturers provide so-called <quote>reference designs</quote> for " +"products based on their chips which are then used by several different " +"device manufacturers and sold under lots of different product or brand names." +msgstr "" + +#. Tag: para +#: preparing.xml:533 +#, no-c-format +msgid "" +"This has advantages and disadvantages. An advantage is that a driver for one " +"chipset works with lots of different products from different manufacturers, " +"as long as their product is based on the same chipset. The disadvantage is " +"that it is not always easy to see which actual chipset is used in a certain " +"product/brand. Unfortunately sometimes device manufacturers change the " +"hardware base of their product without changing the product name or at least " +"the product version number, so that when having two items of the same brand/" +"product name bought at different times, they can sometimes be based on two " +"different chipsets and therefore use two different drivers or there might be " +"no driver at all for one of them." +msgstr "" + +#. Tag: para +#: preparing.xml:546 +#, no-c-format +msgid "" +"For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on " +"which chipset they are based is to look at their device IDs. All USB/PCI/PCI-" +"Express/ExpressCard devices have so called <quote>vendor</quote> and " +"<quote>product</quote> IDs, and the combination of these two is usually the " +"same for any product based on the same chipset." +msgstr "" + +#. Tag: para +#: preparing.xml:554 +#, no-c-format +msgid "" +"On Linux systems, these IDs can be read with the <command>lsusb</command> " +"command for USB devices and with the <command>lspci -nn</command> command " +"for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are " +"usually given in the form of two hexadecimal numbers, separated by a colon, " +"such as <quote>1d6b:0001</quote>." +msgstr "" + +#. Tag: para +#: preparing.xml:562 +#, no-c-format +msgid "" +"An example for the output of <command>lsusb</command>: <quote>Bus 001 Device " +"001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the " +"vendor ID and 0002 is the product ID." +msgstr "" + +#. Tag: para +#: preparing.xml:568 +#, no-c-format +msgid "" +"An example for the output of <command>lspci -nn</command> for an Ethernet " +"card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., " +"Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev " +"06)</quote>. The IDs are given inside the rightmost square brackets, i.e. " +"here 10ec is the vendor- and 8168 is the product ID." +msgstr "" + +#. Tag: para +#: preparing.xml:576 +#, no-c-format +msgid "" +"As another example, a graphics card could give the following output: " +"<quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices " +"[AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>." +msgstr "" + +#. Tag: para +#: preparing.xml:582 +#, no-c-format +msgid "" +"On Windows systems, the IDs for a device can be found in the Windows device " +"manager on the tab <quote>details</quote>, where the vendor ID is prefixed " +"with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, " +"you have to select the property <quote>Hardware IDs</quote> in the device " +"manager's details tab to actually see the IDs, as they are not displayed by " +"default." +msgstr "" + +#. Tag: para +#: preparing.xml:592 +#, no-c-format +msgid "" +"Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</" +"quote> and <quote>driver</quote> as the search terms often results in " +"information regarding the driver support status for a certain chipset. If a " +"search for the vendor/product ID does not yield usable results, a search for " +"the chip code names, which are also often provided by lsusb and lspci " +"(<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example " +"and <quote>RV710</quote> in the graphics card example), can help." +msgstr "" + +#. Tag: title +#: preparing.xml:605 +#, no-c-format +msgid "Testing hardware compatibility with a Live-System" +msgstr "" + +#. Tag: para +#: preparing.xml:607 +#, no-c-format +msgid "" +"&debian-gnu; is also available as a so-called <quote>live system</quote> for " +"certain architectures. A live system is a preconfigured ready-to-use system " +"in a compressed format that can be booted and used from a read-only medium " +"like a CD or DVD. Using it by default does not create any permanent changes " +"on your computer. You can change user settings and install additional " +"programs from within the live system, but all this only happens in the " +"computer's RAM, i.e. if you turn off the computer and boot the live system " +"again, everything is reset to its defaults. If you want to see whether your " +"hardware is supported by &debian-gnu;, the easiest way is to run a &debian; " +"live system on it and try it out." +msgstr "" + +#. Tag: para +#: preparing.xml:620 +#, no-c-format +msgid "" +"There are a few limitations in using a live system. The first is that as all " +"changes you do within the live system must be held in your computer's RAM, " +"this only works on systems with enough RAM to do that, so installing " +"additional large software packages may fail due to memory constraints. " +"Another limitation with regards to hardware compatibility testing is that " +"the official &debian-gnu; live system contains only free components, i.e. " +"there are no non-free firmware files included in it. Such non-free packages " +"can of course be installed manually within the system, but there is no " +"automatic detection of required firmware files like in the &d-i;, so " +"installation of non-free components must be done manually if needed." +msgstr "" + +#. Tag: para +#: preparing.xml:633 +#, no-c-format +msgid "" +"Information about the available variants of the &debian; live images can be " +"found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</" +"ulink>." +msgstr "" + +#. Tag: title +#: preparing.xml:647 +#, no-c-format +msgid "Network Settings" +msgstr "" + +#. Tag: para +#: preparing.xml:649 +#, no-c-format +msgid "" +"If your computer is connected to a fixed network (i.e. an Ethernet or " +"equivalent connection — not a dialup/PPP connection) which is " +"administered by somebody else, you should ask your network's system " +"administrator for this information:" +msgstr "" + +#. Tag: para +#: preparing.xml:657 +#, no-c-format +msgid "Your host name (you may be able to decide this on your own)." +msgstr "" + +#. Tag: para +#: preparing.xml:662 +#, no-c-format +msgid "Your domain name." +msgstr "" + +#. Tag: para +#: preparing.xml:667 +#, no-c-format +msgid "Your computer's IP address." +msgstr "" + +#. Tag: para +#: preparing.xml:672 +#, no-c-format +msgid "The netmask to use with your network." +msgstr "" + +#. Tag: para +#: preparing.xml:677 +#, 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:683 +#, 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:691 +#, no-c-format +msgid "" +"If the network you are connected to uses DHCP (Dynamic Host Configuration " +"Protocol) for configuring network settings, 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:698 +#, no-c-format +msgid "" +"If you have internet access via DSL or cable modem (i.e. over a cable tv " +"network) and have a router (often provided preconfigured by your phone or " +"catv provider) which handles your network connectivity, DHCP is usually " +"available by default." +msgstr "" + +#. Tag: para +#: preparing.xml:706 +#, no-c-format +msgid "" +"As a rule of thumb: if you run a Windows system in your home network and did " +"not have to manually perform any network settings there to achieve Internet " +"access, network connectivity in &debian-gnu; will also be configured " +"automatically." +msgstr "" + +#. Tag: para +#: preparing.xml:713 +#, no-c-format +msgid "If you use a WLAN/WiFi network, you should find out:" +msgstr "" + +#. Tag: para +#: preparing.xml:718 +#, no-c-format +msgid "The ESSID (<quote>network name</quote>) of your wireless network." +msgstr "" + +#. Tag: para +#: preparing.xml:723 +#, no-c-format +msgid "The WEP or WPA/WPA2 security key to access the network (if applicable)." +msgstr "" + +#. Tag: title +#: preparing.xml:740 +#, no-c-format +msgid "Meeting Minimum Hardware Requirements" +msgstr "" + +#. Tag: para +#: preparing.xml:741 +#, 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:747 +#, 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:753 +#, no-c-format +msgid "" +"A Pentium 4, 1GHz system is the minimum recommended for a desktop system." +msgstr "" + +#. Tag: para +#: preparing.xml:758 +#, no-c-format +msgid "Any OldWorld or NewWorld PowerPC can serve well as a desktop system." +msgstr "" + +#. Tag: title +#: preparing.xml:765 +#, no-c-format +msgid "Recommended Minimum System Requirements" +msgstr "" + +#. Tag: entry +#: preparing.xml:769 +#, no-c-format +msgid "Install Type" +msgstr "" + +#. Tag: entry +#: preparing.xml:770 +#, no-c-format +msgid "RAM (minimum)" +msgstr "" + +#. Tag: entry +#: preparing.xml:771 +#, no-c-format +msgid "RAM (recommended)" +msgstr "" + +#. Tag: entry +#: preparing.xml:772 +#, no-c-format +msgid "Hard Drive" +msgstr "" + +#. Tag: entry +#: preparing.xml:778 +#, no-c-format +msgid "No desktop" +msgstr "" + +#. Tag: entry +#: preparing.xml:779 +#, no-c-format +msgid "256 megabytes" +msgstr "" + +#. Tag: entry +#: preparing.xml:780 +#, no-c-format +msgid "512 megabytes" +msgstr "" + +#. Tag: entry +#: preparing.xml:781 preparing.xml:785 +#, no-c-format +msgid "2 gigabytes" +msgstr "" + +#. Tag: entry +#: preparing.xml:783 +#, no-c-format +msgid "With Desktop" +msgstr "" + +#. Tag: entry +#: preparing.xml:784 +#, no-c-format +msgid "1 gigabytes" +msgstr "" + +#. Tag: entry +#: preparing.xml:786 +#, no-c-format +msgid "10 gigabytes" +msgstr "" + +#. Tag: para +#: preparing.xml:791 +#, no-c-format +msgid "" +"The minimum values assumes that swap will be enabled and a non-liveCD image " +"is used. The <quote>No desktop</quote> value assumes that the non-graphical " +"installer is used." +msgstr "" + +#. Tag: para +#: preparing.xml:796 +#, no-c-format +msgid "" +"The actual minimum memory requirements are a lot less than the numbers " +"listed in this table. With swap enabled, it is possible to install &debian; " +"with as little as &minimum-memory-strict;. 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:806 +#, no-c-format +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 Plasma desktop " +"environments; alternatives include <classname>xfce4</classname>, " +"<classname>icewm</classname> and <classname>wmaker</classname>, but there " +"are others to choose from." +msgstr "" + +#. Tag: para +#: preparing.xml:815 +#, no-c-format +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:821 +#, 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." +msgstr "" + +#. Tag: para +#: preparing.xml:828 +#, no-c-format +msgid "" +"Disk space required for the smooth operation of the &debian-gnu; 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</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:852 +#, no-c-format +msgid "Pre-Partitioning for Multi-Boot Systems" +msgstr "" + +#. Tag: para +#: preparing.xml:853 +#, 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:860 +#, 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:866 +#, no-c-format +msgid "" +"If you already have an operating system on your system <phrase arch=\"any-" +"x86\"> (Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, " +"FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, " +"…) </phrase> which uses the whole disk and you want to stick &debian; " +"on the same disk, you will need to repartition it. &debian; requires its own " +"hard disk partitions. It cannot be installed on Windows or Mac OS X " +"partitions. It may be able to share some partitions with other Unix systems, " +"but that's not covered here. At the very least you will need a dedicated " +"partition for the &debian; root filesystem." +msgstr "" + +#. Tag: para +#: preparing.xml:885 +#, 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=\"any-" +"x86\">, such as the integrated Disk Manager in Windows or fdisk in DOS</" +"phrase><phrase arch=\"powerpc\">, such as Disk Utility, Drive Setup, HD " +"Toolkit, or MacTools</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:895 +#, 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: para +#: preparing.xml:903 +#, no-c-format +msgid "" +"Several modern operating systems offer the ability to move and resize " +"certain existing partitions without destroying their contents. This allows " +"making space for additional partitions without losing existing data. Even " +"though this works quite well in most cases, making changes to the " +"partitioning of a disk is an inherently dangerous action and should only be " +"done after having made a full backup of all data. <phrase arch=\"any-" +"x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, " +"the ability to move and resize them losslessly is provided both by &d-i; as " +"well as by the integrated Disk Manager of Windows 7. </phrase>" +msgstr "" + +#. Tag: para +#: preparing.xml:918 +#, no-c-format +msgid "" +"To losslessly resize an existing FAT or NTFS partition from within &d-i;, go " +"to the partitioning step, select the option for manual partitioning, select " +"the partition to resize, and simply specify its new size." +msgstr "" + +#. Tag: emphasis +#: preparing.xml:926 +#, no-c-format +msgid "FIXME: write about HP-UX disks?" +msgstr "" + +#. Tag: para +#: preparing.xml:928 +#, no-c-format +msgid "" +"Creating and deleting partitions can be done from within &d-i; as well as " +"from an existing operating system. As a rule of thumb, partitions should be " +"created by the system for which they are to be used, i.e. partitions to be " +"used by &debian-gnu; should be created from within &d-i; and partitions to " +"be used from another operating system should be created from there. &d-i; is " +"capable of creating non-&arch-kernel; partitions, and partitions created " +"this way usually work without problems when used in other operating systems, " +"but there are a few rare corner cases in which this could cause problems, so " +"if you want to be sure, use the native partitioning tools to create " +"partitions for use by other operating systems." +msgstr "" + +#. Tag: para +#: preparing.xml:941 +#, 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 the " +"&debian; installation. Windows and other OS installations may destroy your " +"ability to start &debian;, or encourage you to reformat non-native " +"partitions." +msgstr "" + +#. Tag: para +#: preparing.xml:949 +#, 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:954 +#, no-c-format +msgid "" +"In order for OpenFirmware to automatically boot &debian-gnu; the &arch-" +"parttype; partitions should appear before all other partitions on the disk, " +"especially Mac OS X boot partitions. This should be kept in mind when pre-" +"partitioning; you should create a &arch-parttype; 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 &debian; partition tools later during " +"the actual install, and replace it with &arch-parttype; partitions." +msgstr "" + +#. Tag: title +#: preparing.xml:1030 +#, no-c-format +msgid "Partitioning from SunOS" +msgstr "" + +#. Tag: para +#: preparing.xml:1032 +#, 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. SILO supports " +"booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or " +"iso9660 (CDROM) partitions." +msgstr "" + +#. Tag: title +#: preparing.xml:1044 +#, no-c-format +msgid "Partitioning from Linux or another OS" +msgstr "" + +#. Tag: para +#: preparing.xml:1046 +#, 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:1058 +#, 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:1073 +#, no-c-format +msgid "Mac OS X Partitioning" +msgstr "" + +#. Tag: para +#: preparing.xml:1075 +#, no-c-format +msgid "" +"The <application>Disk Utility</application> application can be found under " +"the <filename>Utilities</filename> menu in Mac OS X Installer. It will not " +"adjust existing partitions; it is limited to partitioning the entire disk at " +"once." +msgstr "" + +#. Tag: para +#: preparing.xml:1081 +#, 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-gnu; installer." +msgstr "" + +#. Tag: para +#: preparing.xml:1087 +#, no-c-format +msgid "" +"&debian; installer partition table editing tools are compatible with OS X, " +"but not with MacOS 9. If you are planning to use both MacOS 9 and OS X, it " +"is best to install OS X and &debian; on one hard drive, and put MacOS 9 on a " +"separate hard drive. 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." +msgstr "" + +#. Tag: para +#: preparing.xml:1097 +#, no-c-format +msgid "" +"GNU/Linux is unable to access information on UFS partitions, but can access " +"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 Mac OS X and GNU/Linux " +"systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT file " +"systems are supported by MacOS 9, Mac OS X and GNU/Linux." +msgstr "" + +#. Tag: title +#: preparing.xml:1117 +#, no-c-format +msgid "Pre-Installation Hardware and Operating System Setup" +msgstr "" + +#. Tag: para +#: preparing.xml:1118 +#, 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 BIOS/UEFI/system firmware settings " +"for your system. The <quote>BIOS/UEFI</quote> or <quote>system firmware</" +"quote> is the core software used by the hardware; it is most critically " +"invoked during the bootstrap process (after power-up)." +msgstr "" + +#. Tag: title +#: preparing.xml:1133 +#, no-c-format +msgid "Invoking the BIOS/UEFI Set-Up Menu" +msgstr "" + +#. Tag: para +#: preparing.xml:1135 +#, no-c-format +msgid "" +"The BIOS/UEFI provides the basic functions needed to boot your machine and " +"to allow your operating system to access your hardware. Your system provides " +"a BIOS/UEFI setup menu, which is used to configure the BIOS/UEFI. To enter " +"the BIOS/UEFI setup menu you have to press a key or key combination after " +"turning on the computer. Often it is the <keycap>Delete</keycap> or the " +"<keycap>F2</keycap> key, but some manufacturers use other keys. Usually upon " +"starting the computer there will be a message stating which key to press to " +"enter the setup screen." +msgstr "" + +#. Tag: title +#: preparing.xml:1149 preparing.xml:1493 preparing.xml:1671 +#, no-c-format +msgid "Boot Device Selection" +msgstr "" + +#. Tag: para +#: preparing.xml:1151 +#, no-c-format +msgid "" +"Within the BIOS/UEFI setup menu, you can select which devices shall be " +"checked in which sequence for a bootable operating system. Possible choices " +"usually include the internal harddisks, the CD/DVD-ROM drive and USB mass " +"storage devices such as USB sticks or external USB harddisks. On modern " +"systems there is also often a possibility to enable network booting via PXE." +msgstr "" + +#. Tag: para +#: preparing.xml:1159 +#, no-c-format +msgid "" +"Depending on the installation media (CD/DVD ROM, USB stick, network boot) " +"you have chosen you should enable the appropriate boot devices if they are " +"not already enabled." +msgstr "" + +#. Tag: para +#: preparing.xml:1165 +#, no-c-format +msgid "" +"Most BIOS/UEFI versions allow you to call up a boot menu on system startup " +"in which you select from which device the computer should start for the " +"current session. If this option is available, the BIOS/UEFI usually displays " +"a short message like <quote>press <keycap>F12</keycap> for boot menu</quote> " +"on system startup. The actual key used to select this menu varies from " +"system to system; commonly used keys are <keycap>F12</keycap>, <keycap>F11</" +"keycap> and <keycap>F8</keycap>. Choosing a device from this menu does not " +"change the default boot order of the BIOS/UEFI, i.e. you can start once from " +"a USB stick while having configured the internal harddisk as the normal " +"primary boot device." +msgstr "" + +#. Tag: para +#: preparing.xml:1179 +#, no-c-format +msgid "" +"If your BIOS/UEFI does not provide you with a boot menu to do ad-hoc choices " +"of the current boot device, you will have to change your BIOS/UEFI setup to " +"make the device from which the &d-i; shall be booted the primary boot device." +msgstr "" + +#. Tag: para +#: preparing.xml:1185 +#, no-c-format +msgid "" +"Unfortunately some computers may contain buggy BIOS/UEFI versions. Booting " +"&d-i; from a USB stick might not work even if there is an appropriate option " +"in the BIOS/UEFI setup menu and the stick is selected as the primary boot " +"device. On some of these systems using a USB stick as boot medium is " +"impossible; others can be tricked into booting from the stick by changing " +"the device type in the BIOS/UEFI setup from the default <quote>USB harddisk</" +"quote> or <quote>USB stick</quote> to <quote>USB ZIP</quote> or <quote>USB " +"CDROM</quote>. <phrase condition=\"isohybrid-supported\"> In particular if " +"you use an isohybrid installation image on a USB stick (see <xref linkend=" +"\"usb-copy-isohybrid\"/>), changing the device type to <quote>USB CDROM</" +"quote> helps on some BIOSes which will not boot from a USB stick in USB " +"harddisk mode.</phrase> You may need to configure your BIOS/UEFI to enable " +"<quote>USB legacy support</quote>." +msgstr "" + +#. Tag: para +#: preparing.xml:1201 +#, no-c-format +msgid "" +"If you cannot manipulate the BIOS/UEFI to boot directly from a USB stick you " +"still have the option of using an ISO copied to the stick. Boot &d-i; using " +"<xref linkend=\"boot-drive-files\"/> and, after scanning the hard drives for " +"an installer ISO image, select the USB device and choose an installation " +"image." +msgstr "" + +#. Tag: title +#: preparing.xml:1219 +#, no-c-format +msgid "Invoking OpenFirmware" +msgstr "" + +#. Tag: para +#: preparing.xml:1220 +#, 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:1228 +#, no-c-format +msgid "" +"On &arch-title; Macintoshes, you invoke OpenFirmware with " +"<keycombo><keycap>Command (cloverleaf/Apple)</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:1236 +#, no-c-format +msgid "" +"The OpenFirmware prompt looks like this: <informalexample><screen>\n" +"ok\n" +"0 >\n" +"</screen></informalexample> Note that on older model &arch-title; Macs, the " +"default and sometimes hardwired I/O for OpenFirmware user interaction is " +"through the serial (modem) port. If you invoke OpenFirmware on one of these " +"machines, you will just see a black screen. In that case, a terminal program " +"running on another computer, connected to the modem port, is needed to " +"interact with OpenFirmware." +msgstr "" + +#. Tag: para +#: preparing.xml:1249 +#, 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</guibutton> button to have the " +"firmware patches installed to nvram." +msgstr "" + +#. Tag: title +#: preparing.xml:1265 +#, no-c-format +msgid "How to update bare metal ppc64el firmware" +msgstr "" + +#. Tag: para +#: preparing.xml:1266 +#, no-c-format +msgid "" +"This is an excerpt from <ulink url=\"&url-ibm-powerkvm;\">IBM PowerKVM on " +"IBM POWER8</ulink>." +msgstr "" + +#. Tag: para +#: preparing.xml:1271 +#, no-c-format +msgid "" +"Open Power Abstraction Layer (OPAL) is the system firmware in the stack of " +"POWER processor-based server." +msgstr "" + +#. Tag: para +#: preparing.xml:1276 +#, no-c-format +msgid "" +"There may be instances when the user might have to upgrade the Power Systems " +"firmware to a more recent level to acquire new features or additional " +"support for devices." +msgstr "" + +#. Tag: para +#: preparing.xml:1282 +#, no-c-format +msgid "Make sure that the following requirements are met:" +msgstr "" + +#. Tag: para +#: preparing.xml:1287 +#, no-c-format +msgid "an OS to be running on the system;" +msgstr "" + +#. Tag: para +#: preparing.xml:1289 +#, no-c-format +msgid "the .img file of the OPAL level that the user needs to update to;" +msgstr "" + +#. Tag: para +#: preparing.xml:1291 +#, no-c-format +msgid "the machine isn't under HMC control." +msgstr "" + +#. Tag: para +#: preparing.xml:1295 +#, no-c-format +msgid "" +"Power Systems has two sides of flash to boot firmware from, namely permanent " +"and temporary. This provides a way to test firmware updates on the temporary " +"side of the flash before committing the tested changes to the permanent " +"side, thereby committing the new updates." +msgstr "" + +#. Tag: para +#: preparing.xml:1302 +#, no-c-format +msgid "Perform the following steps for the update:" +msgstr "" + +#. Tag: para +#: preparing.xml:1307 +#, no-c-format +msgid "" +"Save the level of the existing firmware before really updating. In ASM, in " +"the system menu, click <command>Service Aids -> Service Processor Command " +"Line</command>, and run the following command:" +msgstr "" + +#. Tag: screen +#: preparing.xml:1311 +#, no-c-format +msgid "cupdcmd -f" +msgstr "" + +#. Tag: para +#: preparing.xml:1312 +#, no-c-format +msgid "" +"Download the .img file of the level of firmware to be updated to a location " +"in the host filesystem. Refer to <ulink url=\"&url-ibm-fixcentral;\">IBM Fix " +"Central</ulink> for downloading the image file." +msgstr "" + +#. Tag: para +#: preparing.xml:1317 +#, no-c-format +msgid "" +"Verify the image downloaded by running the following command and save the " +"output." +msgstr "" + +#. Tag: screen +#: preparing.xml:1320 +#, no-c-format +msgid "$update_flash -v -f <file_name.img>" +msgstr "" + +#. Tag: para +#: preparing.xml:1322 +#, no-c-format +msgid "Update the firmware by running the following command." +msgstr "" + +#. Tag: screen +#: preparing.xml:1324 +#, no-c-format +msgid "$update_flash -f <file_name.img>" +msgstr "" + +#. Tag: para +#: preparing.xml:1330 +#, no-c-format +msgid "" +"The command reboots the system and therefore, sessions if any, would be lost." +msgstr "" + +#. Tag: para +#: preparing.xml:1333 +#, no-c-format +msgid "Do not reboot or switch off the system until it is back." +msgstr "" + +#. Tag: para +#: preparing.xml:1340 +#, no-c-format +msgid "" +"Verify the updated firmware level of the temporary side of the flash as in " +"step 1." +msgstr "" + +#. Tag: para +#: preparing.xml:1343 +#, no-c-format +msgid "" +"In case the update has to be reverted, the user can do so by running this " +"command: <informalexample><screen>\n" +" $update_flash -r\n" +"</screen></informalexample> Rejection would reject only the temporary side " +"of the flash. Therefore, the new level should be committed to the permanent " +"side only after thorough testing of the new firmware." +msgstr "" + +#. Tag: para +#: preparing.xml:1350 +#, no-c-format +msgid "" +"The new updated level can be committed to the permanent side of the flash by " +"running the following command." +msgstr "" + +#. Tag: screen +#: preparing.xml:1353 +#, no-c-format +msgid "$update_flash -c" +msgstr "" + +#. Tag: title +#: preparing.xml:1361 +#, no-c-format +msgid "Updating KVM guest firmware (SLOF)" +msgstr "" + +#. Tag: para +#: preparing.xml:1362 +#, no-c-format +msgid "" +"Slimline Open Firmware (SLOF) is an implementation of the IEEE 1275 " +"standard. It can be used as partition firmware for pSeries machines running " +"on QEMU or KVM." +msgstr "" + +#. Tag: para +#: preparing.xml:1369 +#, no-c-format +msgid "" +"The package qemu-slof is, in fact, a dependency of package qemu-system-ppc " +"(which also provides the virtual package qemu-system-ppc64), and can be " +"installed or updated via <command>apt</command> tool on Debian-based " +"distros. Like so: <informalexample><screen>\n" +"# apt install qemu-slof\n" +"</screen></informalexample> SLOF can also be installed into rpm-based " +"distribution systems, given the proper repository or rpm package. " +"Additionally, the upstream source code is available at <ulink url=\"http://" +"github.com/leilihh/SLOF\"></ulink>." +msgstr "" + +#. Tag: para +#: preparing.xml:1384 +#, no-c-format +msgid "" +"Thus, one can use a different SLOF file rather than the default, when " +"running <command>qemu-system</command>, by adding the command line argument " +"<userinput>-bios <slof_file> </userinput> when starting qemu." +msgstr "" + +#. Tag: title +#: preparing.xml:1394 +#, no-c-format +msgid "Updating PowerKVM hypervisor" +msgstr "" + +#. Tag: title +#: preparing.xml:1395 +#, no-c-format +msgid "Instructions for Netboot installation" +msgstr "" + +#. Tag: para +#: preparing.xml:1396 +#, no-c-format +msgid "" +"You will need a DHCP/TFTP (BOOTP) server, as well as a web server. After " +"downloading ibm-powerkvm-*-ppc64-service-*.iso, mount loop it and unpack it " +"into some directory within your HTTP server www root structure (say " +"wwwroot): <informalexample><screen>\n" +"# cd <directory-where-the-iso-is>\n" +"# mkdir ./iso\n" +"# sudo mount -o loop ibm-powerkvm-*-ppc64-service-*.iso ./iso\n" +"# cp -a ./iso/* <path-to-wwwroot>\n" +"</screen></informalexample> Create the petitboot.conf file in a directory " +"under your tftproot, say /tftproot/powerkvm, with the following contents: " +"<informalexample><screen>\n" +"label PowerKVM Automated Install\n" +"kernel http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/vmlinuz\n" +"initrd http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/initrd.img\n" +"append root=live:http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/LiveOS/squashfs." +"img repo=http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/packages rd.dm=0 rd.md=0 " +"console=hvc0 console=tty0\n" +"</screen></informalexample> Editing your dhcpd.conf, set this directive at " +"the beginning: <informalexample><screen>\n" +"option conf-file code 209 = text;\n" +"</screen></informalexample> Add the system directive: " +"<informalexample><screen>\n" +"host <your-system> {\n" +" hardware ethernet <system macaddr>\n" +" fixed-address <system ip>;\n" +" option host-name \"<system hostname>\";\n" +" option conf-file \"<powerkvm/petitboot.conf>\";\n" +" }\n" +"</screen></informalexample> Reboot the dhcp server." +msgstr "" + +#. Tag: para +#: preparing.xml:1420 +#, no-c-format +msgid "Boot your PowerLinux machine." +msgstr "" + +#. Tag: para +#: preparing.xml:1424 +#, no-c-format +msgid "" +"There should be the following option at petitboot (select it): " +"<informalexample><screen>\n" +"\"Power KVM Automated Install\" \n" +"</screen></informalexample> The installer menu should appear automatically." +msgstr "" + +#. Tag: title +#: preparing.xml:1435 +#, no-c-format +msgid "Instructions for DVD" +msgstr "" + +#. Tag: para +#: preparing.xml:1436 +#, no-c-format +msgid "" +"Boot the ISO ibm-powerkvm-*-ppc64-service-*.iso (either burn a DVD or make " +"it virtual if using QEMU) and simply wait for the boot." +msgstr "" + +#. Tag: para +#: preparing.xml:1439 +#, no-c-format +msgid "" +"There should be the following option at petitboot (select it): " +"<informalexample><screen>\n" +"\"POWERKVM_LIVECD\" \n" +"</screen></informalexample> The installer menu should appear automatically." +msgstr "" + +#. Tag: title +#: preparing.xml:1460 +#, no-c-format +msgid "Invoking OpenBoot" +msgstr "" + +#. Tag: para +#: preparing.xml:1462 +#, 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:1470 +#, 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:1482 +#, 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:1495 +#, 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:1505 +#, 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" +"# echo disk1:1 > /proc/openprom/options/boot-device\n" +"</screen></informalexample> and under Solaris:" +msgstr "" + +#. Tag: screen +#: preparing.xml:1549 +#, no-c-format +msgid "eeprom boot-device=disk1:1" +msgstr "" + +#. Tag: title +#: preparing.xml:1559 +#, no-c-format +msgid "BIOS Setup" +msgstr "" + +#. Tag: para +#: preparing.xml:1560 +#, no-c-format +msgid "" +"In order to install &debian-gnu; 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, and you will notice a 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:1572 +#, 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. Boot media differs depending on the runtime mode. 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:1581 +#, 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:1598 +#, no-c-format +msgid "Native and LPAR installations" +msgstr "" + +#. Tag: para +#: preparing.xml:1599 +#, 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:1613 +#, no-c-format +msgid "Installation as a VM guest" +msgstr "" + +#. Tag: para +#: preparing.xml:1615 +#, 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:1625 +#, 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 (by specifying <userinput>BINARY</userinput> " +"and <userinput>LOCSITE FIX 80</userinput> in your FTP client). " +"<filename>parmfile.debian</filename> can be in either ASCII or EBCDIC " +"format. A sample <filename>debian.exec</filename> script, which will punch " +"the files in the proper order, is included with the images." +msgstr "" + +#. Tag: title +#: preparing.xml:1642 +#, no-c-format +msgid "Setting up an installation server" +msgstr "" + +#. Tag: para +#: preparing.xml:1644 +#, 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:1652 +#, no-c-format +msgid "" +"The installation server needs to copy the exact directory structure from any " +"&debian-gnu; mirror, but only the S/390 and architecture-independent files " +"are required. You can also copy the contents of all installation images into " +"such a directory tree." +msgstr "" + +#. Tag: emphasis +#: preparing.xml:1661 +#, no-c-format +msgid "FIXME: more information needed — from a Redbook?" +msgstr "" + +#. Tag: title +#: preparing.xml:1678 +#, no-c-format +msgid "ARM firmware" +msgstr "" + +#. Tag: para +#: preparing.xml:1680 +#, no-c-format +msgid "" +"As already mentioned before, there is unfortunately no standard for system " +"firmware on ARM systems. Even the behaviour of different systems which use " +"nominally the same firmware can be quite different. This results from the " +"fact that a large part of the devices using the ARM architecture are " +"embedded systems, for which the manufacturers usually build heavily " +"customized firmware versions and include device-specific patches. " +"Unfortunately the manufacturers often do not submit their changes and " +"extensions back to the mainline firmware developers, so their changes are " +"not integrated into newer versions of the original firmware." +msgstr "" + +#. Tag: para +#: preparing.xml:1692 +#, no-c-format +msgid "" +"As a result even newly sold systems often use a firmware that is based on a " +"years-old manufacturer-modified version of a firmware whose mainline " +"codebase has evolved a lot further in the meantime and offers additional " +"features or shows different behaviour in certain aspects. In addition to " +"that, the naming of onboard devices is not consistent between different " +"manufacturer-modified versions of the same firmware, therefore it is nearly " +"impossible to provide usable product-independend instructions for ARM-based " +"systems." +msgstr "" + +#. Tag: title +#: preparing.xml:1705 +#, no-c-format +msgid "Debian-provided U-Boot (system firmware) images" +msgstr "" + +#. Tag: para +#: preparing.xml:1706 +#, no-c-format +msgid "" +"Debian provides U-Boot images for various armhf systems that can load their " +"U-Boot from an SD card at &armmp-uboot-img;. The U-Boot builds are offered " +"in two formats: raw U-Boot components and a ready-made card image that can " +"easily be written onto an SD card. The raw U-Boot components are provided " +"for advanced users; the generally recommended way is to use one of the ready-" +"made SD card images. They are named <system-type>.sdcard.img.gz and " +"can be written to a card e.g. with <informalexample><screen>zcat <system-" +"type>.sdcard.img.gz > /dev/SD_CARD_DEVICE</screen></informalexample> " +"As with all images, please be aware that writing the image to an SD card " +"wipes all previous contents of the card!" +msgstr "" + +#. Tag: para +#: preparing.xml:1721 +#, no-c-format +msgid "" +"If Debian provides a U-Boot image for your system, it is recommended that " +"you use this image instead of the vendor-provided U-Boot, as the version in " +"Debian is usually newer and has more features." +msgstr "" + +#. Tag: title +#: preparing.xml:1729 +#, no-c-format +msgid "Setting the ethernet MAC address in U-Boot" +msgstr "" + +#. Tag: para +#: preparing.xml:1730 +#, no-c-format +msgid "" +"The MAC address of every ethernet interface should normally be globally " +"unique, and it technically has to be unique within its ethernet broadcast " +"domain. To achieve this, the manufacturer usually allocates a block of MAC " +"addresses from a centrally-administered pool (for which a fee has to be " +"paid) and preconfigures one of these addresses on each item sold." +msgstr "" + +#. Tag: para +#: preparing.xml:1738 +#, no-c-format +msgid "" +"In the case of development boards, sometimes the manufacturer wants to avoid " +"paying these fees and therefore provides no globally unique addresses. In " +"these cases the users themselves have to define MAC addresses for their " +"systems. When no MAC address is defined for an ethernet interface, some " +"network drivers generate a random MAC address that can change on every boot, " +"and if this happens, network access would be possible even when the user has " +"not manually set an address, but e.g. assigning semi-static IP addresses by " +"DHCP based on the MAC address of the requesting client would obviously not " +"work reliably." +msgstr "" + +#. Tag: para +#: preparing.xml:1749 +#, no-c-format +msgid "" +"To avoid conflicts with existing officially-assigned MAC addresses, there is " +"an address pool which is reserved for so-called <quote>locally administered</" +"quote> addresses. It is defined by the value of two specific bits in the " +"first byte of the address (the article <quote>MAC address</quote> in the " +"English language Wikipedia gives a good explanation). In practice this means " +"that e.g. any address starting with hexadecimal ca (such as ca:ff:" +"ee:12:34:56) can be used as a locally administered address." +msgstr "" + +#. Tag: para +#: preparing.xml:1759 +#, no-c-format +msgid "" +"On systems using U-Boot as system firmware, the ethernet MAC address is " +"placed in the <quote>ethaddr</quote> environment variable. It can be checked " +"at the U-Boot command prompt with the command <quote>printenv ethaddr</" +"quote> and can be set with the command <quote>setenv ethaddr ca:ff:" +"ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</" +"quote> makes the assignment permanent." +msgstr "" + +#. Tag: title +#: preparing.xml:1770 +#, no-c-format +msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot" +msgstr "" + +#. Tag: para +#: preparing.xml:1771 +#, no-c-format +msgid "" +"On some systems with older U-Boot versions there can be problems with " +"properly relocating the Linux kernel, the initial ramdisk and the device-" +"tree blob in memory during the boot process. In this case, U-Boot shows the " +"message <quote>Starting kernel ...</quote>, but the system freezes " +"afterwards without further output. These issues have been solved with newer " +"U-Boot versions from v2014.07 onwards." +msgstr "" + +#. Tag: para +#: preparing.xml:1780 +#, no-c-format +msgid "" +"If the system has originally used a U-Boot version older than v2014.07 and " +"has been upgraded to a newer version later, the problem might still occur " +"even after upgrading U-Boot. Upgrading U-Boot usually does not modify the " +"existing U-Boot environment variables and the fix requires an additional " +"environment variable (bootm_size) to be set, which U-Boot does automatically " +"only on fresh installations without existing environment data. It is " +"possible to manually set bootm_size to the new U-Boot's default value by " +"running the command <quote>env default bootm_size; saveenv</quote> at the U-" +"Boot prompt." +msgstr "" + +#. Tag: para +#: preparing.xml:1791 +#, no-c-format +msgid "" +"Another possibility to circumvent relocation-related problems is to run the " +"command <quote>setenv fdt_high ffffffff; setenv initrd_high 0xffffffff; " +"saveenv</quote> at the U-Boot prompt to completely disable the relocation of " +"the initial ramdisk and the device-tree blob." +msgstr "" + +#. Tag: title +#: preparing.xml:1801 +#, no-c-format +msgid "Systems with UEFI firmware" +msgstr "" + +#. Tag: para +#: preparing.xml:1802 +#, no-c-format +msgid "" +"UEFI (<quote>Unified Extensible Firmware Interface</quote>) is a new kind of " +"system firmware that is used on many modern systems and is - among other " +"uses - intended to replace the classic PC BIOS." +msgstr "" + +#. Tag: para +#: preparing.xml:1808 +#, no-c-format +msgid "" +"Currently most PC systems that use UEFI also have a so-called " +"<quote>Compatibility Support Module</quote> (CSM) in the firmware, which " +"provides exactly the same interfaces to an operating system as a classic PC " +"BIOS, so that software written for the classic PC BIOS can be used " +"unchanged. Nonetheless UEFI is intended to one day completely replace the " +"old PC BIOS without being fully backwards-compatible and there are already a " +"lot of systems with UEFI but without CSM." +msgstr "" + +#. Tag: para +#: preparing.xml:1818 +#, no-c-format +msgid "" +"On systems with UEFI there are a few things to take into consideration when " +"installing an operating system. The way the firmware loads an operating " +"system is fundamentally different between the classic BIOS (or UEFI in CSM " +"mode) and native UEFI. One major difference is the way the harddisk " +"partitions are recorded on the harddisk. While the classic BIOS and UEFI in " +"CSM mode use a DOS partition table, native UEFI uses a different " +"partitioning scheme called <quote>GUID Partition Table</quote> (GPT). On a " +"single disk, for all practical purposes only one of the two can be used and " +"in case of a multi-boot setup with different operating systems on one disk, " +"all of them must therefore use the same type of partition table. Booting " +"from a disk with GPT is only possible in native UEFI mode, but using GPT " +"becomes more and more common as hard disk sizes grow, because the classic " +"DOS partition table cannot address disks larger than about 2 Terabytes while " +"GPT allows for far larger disks. The other major difference between BIOS (or " +"UEFI in CSM mode) and native UEFI is the location where boot code is stored " +"and in which format it has to be. This means that different bootloaders are " +"needed for each system." +msgstr "" + +#. Tag: para +#: preparing.xml:1838 +#, no-c-format +msgid "" +"The latter becomes important when booting &d-i; on a UEFI system with CSM " +"because &d-i; checks whether it was started on a BIOS- or on a native UEFI " +"system and installs the corresponding bootloader. Normally this simply works " +"but there can be a problem in multi-boot environments. On some UEFI systems " +"with CSM the default boot mode for removable devices can be different from " +"what is actually used when booting from hard disk, so when booting the " +"installer from a USB stick in a different mode from what is used when " +"booting another already installed operating system from the hard disk, the " +"wrong bootloader might be installed and the system might be unbootable after " +"finishing the installation. When choosing the boot device from a firmware " +"boot menu, some systems offer two separate choices for each device, so that " +"the user can select whether booting shall happen in CSM or in native UEFI " +"mode." +msgstr "" + +#. Tag: title +#: preparing.xml:1857 +#, no-c-format +msgid "Secure boot" +msgstr "" + +#. Tag: para +#: preparing.xml:1858 +#, no-c-format +msgid "" +"Another UEFI-related topic is the so-called <quote>secure boot</quote> " +"mechanism. Secure boot means a function of UEFI implementations that allows " +"the firmware to only load and execute code that is cryptographically signed " +"with certain keys and thereby blocking any (potentially malicious) boot code " +"that is unsigned or signed with unknown keys. In practice the only key " +"accepted by default on most UEFI systems with secure boot is a key from " +"Microsoft used for signing the Windows bootloader. As the boot code used by " +"&d-i; is not signed by Microsoft, booting the installer requires prior " +"deactivation of secure boot in case it is enabled. Secure boot is often " +"enabled by default on systems that come preinstalled with a 64-bit version " +"of Windows 8 and there is unfortunately no standard way to disable it in the " +"UEFI setup. On some systems, the option to disable secure boot is only made " +"visible when a BIOS password has been set by the user, so if you have a " +"system with secure boot enabled, but cannot find an option to disable it, " +"try setting a BIOS password, powercycle the machine and look again for an " +"appropriate option." +msgstr "" + +#. Tag: title +#: preparing.xml:1880 +#, no-c-format +msgid "" +"Disabling the Windows <quote>fast boot</quote>/<quote>fast startup</quote> " +"feature" +msgstr "" + +#. Tag: para +#: preparing.xml:1881 +#, no-c-format +msgid "" +"Windows offers a feature (called <quote>fast boot</quote> in Windows 8, " +"<quote>fast startup</quote> in Windows 10) to cut down system startup time. " +"Technically, when this feature is enabled, Windows does not do a real " +"shutdown and a real cold boot afterwards when ordered to shut down, but " +"instead does something resembling a partial suspend to disk to reduce the " +"<quote>boot</quote> time. As long as Windows is the only operating system on " +"the machine, this is unproblematic, but it can result in problems and data " +"loss, when you have a dual boot setup, in which another operating system " +"accesses the same filesystems as Windows does. In that case the real state " +"of the filesystem can be different from what Windows believes it to be after " +"the <quote>boot</quote> and this could cause filesystem corruption upon " +"further write accesses to the filesystem. Therefore in a dual boot setup, to " +"avoid filesystem corruption the <quote>fast boot</quote>/<quote>fast " +"startup</quote> feature has to be disabled within Windows." +msgstr "" + +#. Tag: para +#: preparing.xml:1898 +#, no-c-format +msgid "" +"Furthermore, the Windows Update mechanism has (sometimes) been known to " +"automatically re-enable this feature, after it has been previously disabled " +"by the user. It is suggested to re-check this setting periodically." +msgstr "" + +#. Tag: para +#: preparing.xml:1903 +#, no-c-format +msgid "" +"It may also be necessary to disable <quote>fast boot</quote> to even allow " +"access to UEFI setup to choose to boot another operating system or &d-i;. On " +"some UEFI systems, the firmware will reduce <quote>boot</quote> time by not " +"initialising the keyboard controller or USB hardware; in these cases, it is " +"necessary to boot into Windows and disable this feature to allow for a " +"change of boot order." +msgstr "" + +#. Tag: title +#: preparing.xml:1915 +#, no-c-format +msgid "Hardware Issues to Watch Out For" +msgstr "" + +#. Tag: title +#: preparing.xml:1918 +#, no-c-format +msgid "USB BIOS support and keyboards" +msgstr "" + +#. Tag: para +#: preparing.xml:1919 +#, no-c-format +msgid "" +"If you have no PS/2-style keyboard, but only a USB model, on some very old " +"PCs you may need to enable legacy keyboard emulation in your BIOS setup to " +"be able to use your keyboard in the bootloader menu, but this is not an " +"issue for modern systems. If your keyboard does not work in the bootloader " +"menu, consult your mainboard manual and look in the BIOS for <quote>Legacy " +"keyboard emulation</quote> or <quote>USB keyboard support</quote> options." +msgstr "" + +#. Tag: title +#: preparing.xml:1932 +#, no-c-format +msgid "Display-visibility on OldWorld Powermacs" +msgstr "" + +#. Tag: para +#: preparing.xml:1934 +#, 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/kab/preseed.po b/po/kab/preseed.po new file mode 100644 index 000000000..11e29cff8 --- /dev/null +++ b/po/kab/preseed.po @@ -0,0 +1,2341 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-preface 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-07-03 20:59+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: preseed.xml:16 +#, no-c-format +msgid "Automating the installation using preseeding" +msgstr "" + +#. Tag: para +#: preseed.xml:18 +#, no-c-format +msgid "" +"This appendix explains how to preseed answers to questions in &d-i; to " +"automate your installation." +msgstr "" + +#. Tag: para +#: preseed.xml:23 preseed.xml:720 +#, no-c-format +msgid "" +"The configuration fragments used in this appendix are also available as an " +"example preconfiguration file from &urlset-example-preseed;." +msgstr "" + +#. Tag: title +#: preseed.xml:31 +#, no-c-format +msgid "Introduction" +msgstr "" + +#. Tag: para +#: preseed.xml:32 +#, no-c-format +msgid "" +"Preseeding provides a way to set answers to questions asked during the " +"installation process, without having to manually enter the answers while the " +"installation is running. This makes it possible to fully automate most types " +"of installation and even offers some features not available during normal " +"installations." +msgstr "" + +#. Tag: para +#: preseed.xml:40 +#, no-c-format +msgid "" +"Preseeding is not required. If you use an empty preseed file, the installer " +"will behave just the same way as in a normal manual installation. Each " +"question you preseed will (if you got it right!) modify the installation in " +"some way from that baseline." +msgstr "" + +#. Tag: title +#: preseed.xml:50 +#, no-c-format +msgid "Preseeding methods" +msgstr "" + +#. Tag: para +#: preseed.xml:51 +#, no-c-format +msgid "" +"There are three methods that can be used for preseeding: <firstterm>initrd</" +"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. " +"Initrd preseeding will work with any installation method and supports " +"preseeding of more things, but it requires the most preparation. File and " +"network preseeding each can be used with different installation methods." +msgstr "" + +#. Tag: para +#: preseed.xml:60 +#, no-c-format +msgid "" +"The following table shows which preseeding methods can be used with which " +"installation methods." +msgstr "" + +#. Tag: entry +#: preseed.xml:69 +#, no-c-format +msgid "Installation method" +msgstr "" + +#. Tag: entry +#: preseed.xml:69 +#, no-c-format +msgid "initrd" +msgstr "" + +#. Tag: entry +#: preseed.xml:70 preseed.xml:531 +#, no-c-format +msgid "file" +msgstr "" + +#. Tag: entry +#: preseed.xml:70 +#, no-c-format +msgid "network" +msgstr "" + +#. Tag: entry +#: preseed.xml:76 +#, no-c-format +msgid "CD/DVD/USB" +msgstr "" + +#. Tag: entry +#: preseed.xml:77 preseed.xml:78 preseed.xml:79 preseed.xml:89 preseed.xml:91 +#: preseed.xml:94 preseed.xml:95 preseed.xml:99 preseed.xml:101 +#, no-c-format +msgid "<entry>yes</entry>" +msgstr "" + +#. Tag: para +#: preseed.xml:81 +#, no-c-format +msgid "" +"but only if you have network access, and set <literal>preseed/url</literal> " +"appropriately" +msgstr "" + +#. Tag: entry +#: preseed.xml:88 +#, no-c-format +msgid "netboot" +msgstr "" + +#. Tag: entry +#: preseed.xml:90 preseed.xml:100 +#, no-c-format +msgid "<entry>no</entry>" +msgstr "" + +#. Tag: entry +#: preseed.xml:93 +#, no-c-format +msgid "" +"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>" +msgstr "" + +#. Tag: entry +#: preseed.xml:96 +#, no-c-format +msgid "yes<footnoteref linkend=\"apx-ps-net\"/>" +msgstr "" + +#. Tag: entry +#: preseed.xml:98 +#, no-c-format +msgid "generic" +msgstr "" + +#. Tag: para +#: preseed.xml:107 +#, no-c-format +msgid "" +"An important difference between the preseeding methods is the point at which " +"the preconfiguration file is loaded and processed. For initrd preseeding " +"this is right at the start of the installation, before the first question is " +"even asked. Preseeding from the kernel command line happens just after. It " +"is thus possible to override configuration set in the initrd by editing the " +"kernel command line (either in the bootloader configuration or manually at " +"boot time for bootloaders that allow it). For file preseeding this is after " +"the installation image has been loaded. For network preseeding it is only " +"after the network has been configured." +msgstr "" + +#. Tag: para +#: preseed.xml:119 +#, no-c-format +msgid "" +"Obviously, any questions that have been processed before the " +"preconfiguration file is loaded cannot be preseeded (this will include " +"questions that are only displayed at medium or low priority, like the first " +"hardware detection run). A not so convenient way to avoid these questions " +"from being asked is to preseed them through the boot parameters, as " +"described in <xref linkend=\"preseed-bootparms\"/>." +msgstr "" + +#. Tag: para +#: preseed.xml:128 +#, no-c-format +msgid "" +"In order to easily avoid the questions that would normally appear before the " +"preseeding occurs, you can start the installer in <quote>auto</quote> mode. " +"This delays questions that would normally be asked too early for preseeding " +"(i.e. language, country and keyboard selection) until after the network " +"comes up, thus allowing them to be preseeded. It also runs the installation " +"at critical priority, which avoids many unimportant questions. See <xref " +"linkend=\"preseed-auto\"/> for details." +msgstr "" + +#. Tag: title +#: preseed.xml:142 +#, no-c-format +msgid "Limitations" +msgstr "" + +#. Tag: para +#: preseed.xml:143 +#, no-c-format +msgid "" +"Although most questions used by &d-i; can be preseeded using this method, " +"there are some notable exceptions. You must (re)partition an entire disk or " +"use available free space on a disk; it is not possible to use existing " +"partitions." +msgstr "" + +#. Tag: title +#: preseed.xml:217 +#, no-c-format +msgid "Using preseeding" +msgstr "" + +#. Tag: para +#: preseed.xml:218 +#, no-c-format +msgid "" +"You will first need to create a preconfiguration file and place it in the " +"location from where you want to use it. Creating the preconfiguration file " +"is covered later in this appendix. Putting it in the correct location is " +"fairly straightforward for network preseeding or if you want to read the " +"file off a usb-stick. If you want to include the file in an installation ISO " +"image, you will have to remaster the image. How to get the preconfiguration " +"file included in the initrd is outside the scope of this document; please " +"consult the developers' documentation for &d-i;." +msgstr "" + +#. Tag: para +#: preseed.xml:229 +#, no-c-format +msgid "" +"An example preconfiguration file that you can use as basis for your own " +"preconfiguration file is available from &urlset-example-preseed;. This file " +"is based on the configuration fragments included in this appendix." +msgstr "" + +#. Tag: title +#: preseed.xml:238 +#, no-c-format +msgid "Loading the preconfiguration file" +msgstr "" + +#. Tag: para +#: preseed.xml:239 +#, no-c-format +msgid "" +"If you are using initrd preseeding, you only have to make sure a file named " +"<filename>preseed.cfg</filename> is included in the root directory of the " +"initrd. The installer will automatically check if this file is present and " +"load it." +msgstr "" + +#. Tag: para +#: preseed.xml:246 +#, no-c-format +msgid "" +"For the other preseeding methods you need to tell the installer what file to " +"use when you boot it. This is normally done by passing the kernel a boot " +"parameter, either manually at boot time or by editing the bootloader " +"configuration file <phrase arch=\"linux-any\">(e.g. <filename>syslinux.cfg</" +"filename>) and adding the parameter to the end of the append line(s) for the " +"kernel.</phrase><phrase arch=\"kfreebsd-any\">(e.g. <filename>grub.cfg</" +"filename>) and adding the parameter as a new <literal>set</literal> line for " +"the kernel.</phrase><phrase arch=\"hurd-any\">(e.g. <filename>grub.cfg</" +"filename>) and adding the parameter to the end of the <filename>gnumach.gz</" +"filename> line.</phrase>" +msgstr "" + +#. Tag: para +#: preseed.xml:259 +#, no-c-format +msgid "" +"If you do specify the preconfiguration file in the bootloader configuration, " +"you might change the configuration so you don't need to hit enter to boot " +"the installer. <phrase arch=\"linux-any\">For syslinux this means setting " +"the timeout to <literal>1</literal> in <filename>syslinux.cfg</filename>.</" +"phrase><phrase arch=\"kfrebsd-any;hurd-any\">For grub this means setting the " +"timeout to <literal>0</literal> in <filename>grub.cfg</filename>.</phrase>" +msgstr "" + +#. Tag: para +#: preseed.xml:268 +#, no-c-format +msgid "" +"To make sure the installer gets the right preconfiguration file, you can " +"optionally specify a checksum for the file. Currently this needs to be a " +"md5sum, and if specified it must match the preconfiguration file or the " +"installer will refuse to use it." +msgstr "" + +#. Tag: screen +#: preseed.xml:277 +#, no-c-format +msgid "" +"Boot parameters to specify:\n" +"- if you're netbooting:\n" +" preseed/url=http://host/path/to/preseed.cfg\n" +" preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n" +"- or\n" +" preseed/url=tftp://host/path/to/preseed.cfg\n" +" preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n" +"\n" +"- if you're booting a remastered installation image:\n" +" preseed/file=/cdrom/preseed.cfg\n" +" preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n" +"\n" +"- if you're installing from USB media (put the preconfiguration file in the\n" +" toplevel directory of the USB stick):\n" +" preseed/file=/hd-media/preseed.cfg\n" +" preseed/file/checksum=5da499872becccfeda2c4872f9171c3d" +msgstr "" + +#. Tag: para +#: preseed.xml:279 +#, no-c-format +msgid "" +"Note that <filename>preseed/url</filename> can be shortened to just " +"<filename>url</filename>, <filename>preseed/file</filename> to just " +"<filename>file</filename> and <filename>preseed/file/checksum</filename> to " +"just <filename>preseed-md5</filename> when they are passed as boot " +"parameters." +msgstr "" + +#. Tag: title +#: preseed.xml:290 +#, no-c-format +msgid "Using boot parameters to preseed questions" +msgstr "" + +#. Tag: para +#: preseed.xml:291 +#, no-c-format +msgid "" +"If a preconfiguration file cannot be used to preseed some steps, the install " +"can still be fully automated, since you can pass preseed values on the " +"command line when booting the installer." +msgstr "" + +#. Tag: para +#: preseed.xml:297 +#, no-c-format +msgid "" +"Boot parameters can also be used if you do not really want to use " +"preseeding, but just want to provide an answer for a specific question. Some " +"examples where this can be useful are documented elsewhere in this manual." +msgstr "" + +#. Tag: para +#: preseed.xml:303 +#, no-c-format +msgid "" +"To set a value to be used inside &d-i;, just pass " +"<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</" +"replaceable></userinput> for any of the preseed variables listed in the " +"examples in this appendix. If a value is to be used to configure packages " +"for the target system, you will need to prepend the <firstterm>owner</" +"firstterm><footnote> <para> The owner of a debconf variable (or template) is " +"normally the name of the package that contains the corresponding debconf " +"template. For variables used in the installer itself the owner is <quote>d-" +"i</quote>. Templates and variables can have more than one owner which helps " +"to determine whether they can be removed from the debconf database if the " +"package is purged. </para> </footnote> of the variable as in " +"<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</" +"replaceable>=<replaceable>value</replaceable></userinput>. If you don't " +"specify the owner, the value for the variable will not be copied to the " +"debconf database in the target system and thus remain unused during the " +"configuration of the relevant package." +msgstr "" + +#. Tag: para +#: preseed.xml:326 +#, no-c-format +msgid "" +"Normally, preseeding a question in this way will mean that the question will " +"not be asked. To set a specific default value for a question, but still have " +"the question asked, use <quote>?=</quote> instead of <quote>=</quote> as " +"operator. See also <xref linkend=\"preseed-seenflag\"/>." +msgstr "" + +#. Tag: para +#: preseed.xml:333 +#, no-c-format +msgid "" +"Note that some variables that are frequently set at the boot prompt have a " +"shorter alias. If an alias is available, it is used in the examples in this " +"appendix instead of the full variable. The <literal>preseed/url</literal> " +"variable for example has been aliased as <literal>url</literal>. Another " +"example is the <literal>tasks</literal> alias, which translates to " +"<literal>tasksel:tasksel/first</literal>." +msgstr "" + +#. Tag: para +#: preseed.xml:342 +#, no-c-format +msgid "" +"A <quote>---</quote> in the boot options has special meaning. Kernel " +"parameters that appear after the last <quote>---</quote> may be copied into " +"the bootloader configuration for the installed system (if supported by the " +"installer for the bootloader). The installer will automatically filter out " +"any options (like preconfiguration options) that it recognizes." +msgstr "" + +#. Tag: para +#: preseed.xml:351 +#, no-c-format +msgid "" +"Current linux kernels (2.6.9 and later) accept a maximum of 32 command line " +"options and 32 environment options, including any options added by default " +"for the installer. If these numbers are exceeded, the kernel will panic " +"(crash). (For earlier kernels, these numbers were lower.)" +msgstr "" + +#. Tag: para +#: preseed.xml:359 +#, no-c-format +msgid "" +"For most installations some of the default options in your bootloader " +"configuration file, like <literal>vga=normal</literal>, may be safely " +"removed which may allow you to add more options for preseeding." +msgstr "" + +#. Tag: para +#: preseed.xml:366 +#, no-c-format +msgid "" +"It may not always be possible to specify values with spaces for boot " +"parameters, even if you delimit them with quotes." +msgstr "" + +#. Tag: title +#: preseed.xml:375 +#, no-c-format +msgid "Auto mode" +msgstr "" + +#. Tag: para +#: preseed.xml:376 +#, no-c-format +msgid "" +"There are several features of &debian; Installer that combine to allow " +"fairly simple command lines at the boot prompt to result in arbitrarily " +"complex customized automatic installs." +msgstr "" + +#. Tag: para +#: preseed.xml:382 +#, no-c-format +msgid "" +"This is enabled by using the <literal>Automated install</literal> boot " +"choice, also called <literal>auto</literal> for some architectures or boot " +"methods. In this section, <literal>auto</literal> is thus not a parameter, " +"it means selecting that boot choice, and appending the following boot " +"parameters on the boot prompt. <phrase arch=\"x86\">See <xref linkend=\"boot-" +"screen\"/> for information on how to add a boot parameter.</phrase>" +msgstr "" + +#. Tag: para +#: preseed.xml:391 +#, no-c-format +msgid "" +"To illustrate this, here are some examples that can be used at the boot " +"prompt: <informalexample><screen>\n" +"auto url=autoserver\n" +"</screen></informalexample> This relies on there being a DHCP server that " +"will get the machine to the point where <literal>autoserver</literal> can be " +"resolved by DNS, perhaps after adding the local domain if that was provided " +"by DHCP. If this was done at a site where the domain is <literal>example." +"com</literal>, and they have a reasonably sane DHCP setup, it would result " +"in the preseed file being retrieved from <literal>http://autoserver.example." +"com/d-i/&releasename;/./preseed.cfg</literal>." +msgstr "" + +#. Tag: para +#: preseed.xml:405 +#, no-c-format +msgid "" +"The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</" +"literal>) is taken from <literal>auto-install/defaultroot</literal>. By " +"default this includes the directory <literal>&releasename;</literal> to " +"allow future versions to specify their own codename and let people migrate " +"forwards in a controlled manner. The <literal>/./</literal> bit is used to " +"indicate a root, relative to which subsequent paths can be anchored (for use " +"in preseed/include and preseed/run). This allows files to be specified " +"either as full URLs, paths starting with / that are thus anchored, or even " +"paths relative to the location where the last preseed file was found. This " +"can be used to construct more portable scripts where an entire hierarchy of " +"scripts can be moved to a new location without breaking it, for example " +"copying the files onto a USB stick when they started out on a web server. In " +"this example, if the preseed file sets <literal>preseed/run</literal> to " +"<literal>/scripts/late_command.sh</literal> then the file will be fetched " +"from <literal>http://autoserver.example.com/d-i/&releasename;/./scripts/" +"late_command.sh</literal>." +msgstr "" + +#. Tag: para +#: preseed.xml:425 +#, no-c-format +msgid "" +"If there is no local DHCP or DNS infrastructure, or if you do not want to " +"use the default path to <filename>preseed.cfg</filename>, you can still use " +"an explicit url, and if you don't use the <literal>/./</literal> element it " +"will be anchored to the start of the path (i.e. the third <literal>/</" +"literal> in the URL). Here is an example that requires minimal support from " +"the local network infrastructure: <informalexample><screen>\n" +"auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</" +"replaceable>\n" +"</screen></informalexample> The way this works is that:" +msgstr "" + +#. Tag: para +#: preseed.xml:438 +#, no-c-format +msgid "if the URL is missing a protocol, http is assumed," +msgstr "" + +#. Tag: para +#: preseed.xml:441 +#, no-c-format +msgid "" +"if the hostname section contains no periods, it has the domain derived from " +"DHCP appended to it, and" +msgstr "" + +#. Tag: para +#: preseed.xml:445 +#, no-c-format +msgid "" +"if there's no <literal>/</literal>'s after the hostname, then the default " +"path is added." +msgstr "" + +#. Tag: para +#: preseed.xml:451 +#, no-c-format +msgid "" +"In addition to specifying the url, you can also specify settings that do not " +"directly affect the behavior of &d-i; itself, but can be passed through to " +"scripts specified using <literal>preseed/run</literal> in the loaded preseed " +"file. At present, the only example of this is <literal>auto-install/classes</" +"literal>, which has an alias <literal>classes</literal>. This can be used " +"thus: <informalexample><screen>\n" +"auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;" +"class_B</replaceable>\n" +"</screen></informalexample> The classes could for example denote the type of " +"system to be installed, or the localization to be used." +msgstr "" + +#. Tag: para +#: preseed.xml:465 +#, no-c-format +msgid "" +"It is of course possible to extend this concept, and if you do, it is " +"reasonable to use the auto-install namespace for this. So one might have " +"something like <literal>auto-install/style</literal> which is then used in " +"your scripts. If you feel the need to do this, please mention it on the " +"<email>debian-boot@lists.debian.org</email> mailing list so that we can " +"avoid namespace conflicts, and perhaps add an alias for the parameter for " +"you." +msgstr "" + +#. Tag: para +#: preseed.xml:475 +#, no-c-format +msgid "" +"The <literal>auto</literal> boot choice is not yet defined on all arches. " +"The same effect may be achieved by simply adding the two parameters " +"<literal>auto=true priority=critical</literal> to the kernel command line. " +"The <literal>auto</literal> kernel parameter is an alias for <literal>auto-" +"install/enable</literal> and setting it to <literal>true</literal> delays " +"the locale and keyboard questions until after there has been a chance to " +"preseed them, while <literal>priority</literal> is an alias for " +"<literal>debconf/priority</literal> and setting it to <literal>critical</" +"literal> stops any questions with a lower priority from being asked." +msgstr "" + +#. Tag: para +#: preseed.xml:489 +#, no-c-format +msgid "" +"Additional options that may be of interest while attempting to automate an " +"install while using DHCP are: <literal>interface=auto netcfg/" +"dhcp_timeout=60</literal> which makes the machine choose the first viable " +"NIC and be more patient about getting a reply to its DHCP query." +msgstr "" + +#. Tag: para +#: preseed.xml:498 +#, no-c-format +msgid "" +"An extensive example of how to use this framework, including example scripts " +"and classes, can be found on the <ulink url=\"http://hands.com/d-i/" +"\">website of its developer</ulink>. The examples available there also show " +"many other nice effects that can be achieved by creative use of " +"preconfiguration." +msgstr "" + +#. Tag: title +#: preseed.xml:509 +#, no-c-format +msgid "Aliases useful with preseeding" +msgstr "" + +#. Tag: para +#: preseed.xml:510 +#, no-c-format +msgid "" +"The following aliases can be useful when using (auto mode) preseeding. Note " +"that these are simply short aliases for question names, and you always need " +"to specify a value as well: for example, <literal>auto=true</literal> or " +"<literal>interface=eth0</literal>." +msgstr "" + +#. Tag: entry +#: preseed.xml:523 +#, no-c-format +msgid "priority" +msgstr "" + +#. Tag: entry +#: preseed.xml:523 +#, no-c-format +msgid "debconf/priority" +msgstr "" + +#. Tag: entry +#: preseed.xml:524 +#, no-c-format +msgid "<entry>fb</entry>" +msgstr "" + +#. Tag: entry +#: preseed.xml:524 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "" + +#. Tag: entry +#: preseed.xml:525 +#, no-c-format +msgid "language" +msgstr "" + +#. Tag: entry +#: preseed.xml:525 +#, no-c-format +msgid "debian-installer/language" +msgstr "" + +#. Tag: entry +#: preseed.xml:526 +#, no-c-format +msgid "country" +msgstr "" + +#. Tag: entry +#: preseed.xml:526 +#, no-c-format +msgid "debian-installer/country" +msgstr "" + +#. Tag: entry +#: preseed.xml:527 +#, no-c-format +msgid "locale" +msgstr "" + +#. Tag: entry +#: preseed.xml:527 +#, no-c-format +msgid "debian-installer/locale" +msgstr "" + +#. Tag: entry +#: preseed.xml:528 +#, no-c-format +msgid "theme" +msgstr "" + +#. Tag: entry +#: preseed.xml:528 +#, no-c-format +msgid "debian-installer/theme" +msgstr "" + +#. Tag: entry +#: preseed.xml:529 +#, no-c-format +msgid "auto" +msgstr "" + +#. Tag: entry +#: preseed.xml:529 +#, no-c-format +msgid "auto-install/enable" +msgstr "" + +#. Tag: entry +#: preseed.xml:530 +#, no-c-format +msgid "classes" +msgstr "" + +#. Tag: entry +#: preseed.xml:530 +#, no-c-format +msgid "auto-install/classes" +msgstr "" + +#. Tag: entry +#: preseed.xml:531 +#, no-c-format +msgid "preseed/file" +msgstr "" + +#. Tag: entry +#: preseed.xml:532 +#, no-c-format +msgid "<entry>url</entry>" +msgstr "" + +#. Tag: entry +#: preseed.xml:532 +#, no-c-format +msgid "preseed/url" +msgstr "" + +#. Tag: entry +#: preseed.xml:533 +#, no-c-format +msgid "domain" +msgstr "" + +#. Tag: entry +#: preseed.xml:533 +#, no-c-format +msgid "netcfg/get_domain" +msgstr "" + +#. Tag: entry +#: preseed.xml:534 +#, no-c-format +msgid "hostname " +msgstr "" + +#. Tag: entry +#: preseed.xml:534 +#, no-c-format +msgid "netcfg/get_hostname" +msgstr "" + +#. Tag: entry +#: preseed.xml:535 +#, no-c-format +msgid "interface" +msgstr "" + +#. Tag: entry +#: preseed.xml:535 +#, no-c-format +msgid "netcfg/choose_interface" +msgstr "" + +#. Tag: entry +#: preseed.xml:536 +#, no-c-format +msgid "protocol" +msgstr "" + +#. Tag: entry +#: preseed.xml:536 +#, no-c-format +msgid "mirror/protocol" +msgstr "" + +#. Tag: entry +#: preseed.xml:537 +#, no-c-format +msgid "suite" +msgstr "" + +#. Tag: entry +#: preseed.xml:537 +#, no-c-format +msgid "mirror/suite" +msgstr "" + +#. Tag: entry +#: preseed.xml:538 +#, no-c-format +msgid "modules" +msgstr "" + +#. Tag: entry +#: preseed.xml:538 +#, no-c-format +msgid "anna/choose_modules" +msgstr "" + +#. Tag: entry +#: preseed.xml:539 +#, no-c-format +msgid "recommends" +msgstr "" + +#. Tag: entry +#: preseed.xml:539 +#, no-c-format +msgid "base-installer/install-recommends" +msgstr "" + +#. Tag: entry +#: preseed.xml:540 +#, no-c-format +msgid "tasks" +msgstr "" + +#. Tag: entry +#: preseed.xml:540 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "" + +#. Tag: entry +#: preseed.xml:541 +#, no-c-format +msgid "desktop" +msgstr "" + +#. Tag: entry +#: preseed.xml:541 +#, no-c-format +msgid "tasksel:tasksel/desktop" +msgstr "" + +#. Tag: entry +#: preseed.xml:542 +#, no-c-format +msgid "dmraid" +msgstr "" + +#. Tag: entry +#: preseed.xml:542 +#, no-c-format +msgid "disk-detect/dmraid/enable" +msgstr "" + +#. Tag: entry +#: preseed.xml:543 +#, no-c-format +msgid "keymap" +msgstr "" + +#. Tag: entry +#: preseed.xml:543 +#, no-c-format +msgid "keyboard-configuration/xkb-keymap" +msgstr "" + +#. Tag: entry +#: preseed.xml:544 +#, no-c-format +msgid "preseed-md5" +msgstr "" + +#. Tag: entry +#: preseed.xml:544 +#, no-c-format +msgid "preseed/file/checksum" +msgstr "" + +#. Tag: title +#: preseed.xml:551 +#, no-c-format +msgid "Examples of boot prompt preseeding" +msgstr "" + +#. Tag: para +#: preseed.xml:552 +#, no-c-format +msgid "" +"Here are some examples of how the boot prompt might look like (you will need " +"to adapt this to your needs<phrase arch=\"x86\">; also see <xref linkend=" +"\"boot-screen\"/></phrase>)." +msgstr "" + +#. Tag: screen +#: preseed.xml:558 +#, no-c-format +msgid "" +"# To set French as language and France as country:\n" +"/install.amd/vmlinuz vga=788 initrd=/install.amd/gtk/initrd.gz language=fr " +"country=FR --- quiet\n" +"# To set English as language and Germany as country, and use a German " +"keyboard layout:\n" +"/install.amd/vmlinuz vga=788 initrd=/install.amd/gtk/initrd.gz language=en " +"country=DE locale=en_US.UTF-8 keymap=de --- quiet\n" +"# To install the MATE desktop:\n" +"/install.amd/vmlinuz vga=788 initrd=/install.amd/gtk/initrd.gz desktop=mate-" +"desktop --- quiet\n" +"# To install the web-server task:\n" +"/install.amd/vmlinuz initrd=/install.amd/initrd.gz tasksel:tasksel/first=web-" +"server ---" +msgstr "" + +#. Tag: title +#: preseed.xml:564 +#, no-c-format +msgid "Using a DHCP server to specify preconfiguration files" +msgstr "" + +#. Tag: para +#: preseed.xml:565 +#, no-c-format +msgid "" +"It's also possible to use DHCP to specify a preconfiguration file to " +"download from the network. DHCP allows specifying a filename. Normally this " +"is a file to netboot, but if it appears to be an URL then installation media " +"that support network preseeding will download the file from the URL and use " +"it as a preconfiguration file. Here is an example of how to set it up in the " +"dhcpd.conf for version 3 of the ISC DHCP server (the isc-dhcp-server " +"&debian; package)." +msgstr "" + +#. Tag: screen +#: preseed.xml:576 +#, no-c-format +msgid "" +"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" +" filename \"http://host/preseed.cfg\";\n" +"}" +msgstr "" + +#. Tag: para +#: preseed.xml:578 +#, no-c-format +msgid "" +"Note that the above example limits this filename to DHCP clients that " +"identify themselves as <quote>d-i</quote>, so it will not affect regular " +"DHCP clients, but only the installer. You can also put the text in a stanza " +"for only one particular host to avoid preseeding all installs on your " +"network." +msgstr "" + +#. Tag: para +#: preseed.xml:585 +#, no-c-format +msgid "" +"A good way to use the DHCP preseeding is to only preseed values specific to " +"your network, such as the &debian; mirror to use. This way installs on your " +"network will automatically get a good mirror selected, but the rest of the " +"installation can be performed interactively. Using DHCP preseeding to fully " +"automate &debian; installs should only be done with care." +msgstr "" + +#. Tag: title +#: preseed.xml:599 +#, no-c-format +msgid "Creating a preconfiguration file" +msgstr "" + +#. Tag: para +#: preseed.xml:600 +#, no-c-format +msgid "" +"The preconfiguration file is in the format used by the <command>debconf-set-" +"selections</command> command. The general format of a line in a " +"preconfiguration file is:" +msgstr "" + +#. Tag: screen +#: preseed.xml:606 +#, no-c-format +msgid "<owner> <question name> <question type> <value>" +msgstr "" + +#. Tag: para +#: preseed.xml:608 +#, no-c-format +msgid "The file should start with <literal>#_preseed_V1</literal>" +msgstr "" + +#. Tag: para +#: preseed.xml:620 +#, no-c-format +msgid "" +"There are a few rules to keep in mind when writing a preconfiguration file." +msgstr "" + +#. Tag: para +#: preseed.xml:627 +#, no-c-format +msgid "" +"Put only a single space or tab between type and value: any additional " +"whitespace will be interpreted as belonging to the value." +msgstr "" + +#. Tag: para +#: preseed.xml:631 +#, no-c-format +msgid "" +"A line can be split into multiple lines by appending a backslash " +"(<quote><literal>\\</literal></quote>) as the line continuation character. A " +"good place to split a line is after the question name; a bad place is " +"between type and value. Split lines will be joined into a single line with " +"all leading/trailing whitespace condensed to a single space." +msgstr "" + +#. Tag: para +#: preseed.xml:638 +#, no-c-format +msgid "" +"For debconf variables (templates) used only in the installer itself, the " +"owner should be set to <quote>d-i</quote>; to preseed variables used in the " +"installed system, the name of the package that contains the corresponding " +"debconf template should be used. Only variables that have their owner set to " +"something other than <quote>d-i</quote> will be propagated to the debconf " +"database for the installed system." +msgstr "" + +#. Tag: para +#: preseed.xml:646 +#, no-c-format +msgid "" +"Most questions need to be preseeded using the values valid in English and " +"not the translated values. However, there are some questions (for example in " +"<classname>partman</classname>) where the translated values need to be used." +msgstr "" + +#. Tag: para +#: preseed.xml:652 +#, no-c-format +msgid "" +"Some questions take a code as value instead of the English text that is " +"shown during installation." +msgstr "" + +#. Tag: para +#: preseed.xml:656 +#, no-c-format +msgid "Start with <literal>#_preseed_V1</literal>" +msgstr "" + +#. Tag: para +#: preseed.xml:662 +#, no-c-format +msgid "" +"The easiest way to create a preconfiguration file is to use the example file " +"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there." +msgstr "" + +#. Tag: para +#: preseed.xml:667 +#, no-c-format +msgid "" +"An alternative method is to do a manual installation and then, after " +"rebooting, use the <command>debconf-get-selections</command> from the " +"<classname>debconf-utils</classname> package to dump both the debconf " +"database and the installer's cdebconf database to a single file:" +msgstr "" + +#. Tag: screen +#: preseed.xml:674 +#, no-c-format +msgid "" +"$ echo \"#_preseed_V1\" > <replaceable>file</replaceable>\n" +"$ debconf-get-selections --installer >> <replaceable>file</" +"replaceable>\n" +"$ debconf-get-selections >> <replaceable>file</replaceable>" +msgstr "" + +#. Tag: para +#: preseed.xml:676 +#, no-c-format +msgid "" +"However, a file generated in this manner will have some items that should " +"not be preseeded, and the example file is a better starting place for most " +"users." +msgstr "" + +#. Tag: para +#: preseed.xml:684 +#, no-c-format +msgid "" +"This method relies on the fact that, at the end of the installation, the " +"installer's cdebconf database is saved to the installed system in <filename>/" +"var/log/installer/cdebconf</filename>. However, because the database may " +"contain sensitive information, by default the files are only readable by " +"root." +msgstr "" + +#. Tag: para +#: preseed.xml:692 +#, no-c-format +msgid "" +"The directory <filename>/var/log/installer</filename> and all files in it " +"will be deleted from your system if you purge the package " +"<classname>installation-report</classname>." +msgstr "" + +#. Tag: para +#: preseed.xml:700 +#, no-c-format +msgid "" +"To check possible values for questions, you can use <command>nano</command> " +"to examine the files in <filename>/var/lib/cdebconf</filename> while an " +"installation is in progress. View <filename>templates.dat</filename> for the " +"raw templates and <filename>questions.dat</filename> for the current values " +"and for the values assigned to variables." +msgstr "" + +#. Tag: para +#: preseed.xml:708 +#, no-c-format +msgid "" +"To check if the format of your preconfiguration file is valid before " +"performing an install, you can use the command <command>debconf-set-" +"selections -c <replaceable>preseed.cfg</replaceable></command>." +msgstr "" + +#. Tag: title +#: preseed.xml:719 +#, no-c-format +msgid "Contents of the preconfiguration file (for &releasename;)" +msgstr "" + +#. Tag: para +#: preseed.xml:725 +#, no-c-format +msgid "" +"Note that this example is based on an installation for the Intel x86 " +"architecture. If you are installing a different architecture, some of the " +"examples (like keyboard selection and bootloader installation) may not be " +"relevant and will need to be replaced by debconf settings appropriate for " +"your architecture." +msgstr "" + +#. Tag: para +#: preseed.xml:733 +#, no-c-format +msgid "" +"Details on how the different Debian Installer components actually work can " +"be found in <xref linkend=\"module-details\"/>." +msgstr "" + +#. Tag: title +#: preseed.xml:741 +#, no-c-format +msgid "Localization" +msgstr "" + +#. Tag: para +#: preseed.xml:742 +#, no-c-format +msgid "" +"During a normal install the questions about localization are asked first, so " +"these values can only be preseeded via the initrd or kernel boot parameter " +"methods. Auto mode (<xref linkend=\"preseed-auto\"/>) includes the setting " +"of <literal>auto-install/enable=true</literal> (normally via the " +"<literal>auto</literal> preseed alias). This delays the asking of the " +"localisation questions, so that they can be preseeded by any method." +msgstr "" + +#. Tag: para +#: preseed.xml:751 +#, no-c-format +msgid "" +"The locale can be used to specify both language and country and can be any " +"combination of a language supported by &d-i; and a recognized country. If " +"the combination does not form a valid locale, the installer will " +"automatically select a locale that is valid for the selected language. To " +"specify the locale as a boot parameter, use " +"<userinput>locale=<replaceable>en_US</replaceable></userinput>." +msgstr "" + +#. Tag: para +#: preseed.xml:760 +#, no-c-format +msgid "" +"Although this method is very easy to use, it does not allow preseeding of " +"all possible combinations of language, country and locale<footnote> <para> " +"Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would " +"for example result in <literal>en_US.UTF-8</literal> as default locale for " +"the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred " +"instead, the values will need to be preseeded individually. </para> </" +"footnote>. So alternatively the values can be preseeded individually. " +"Language and country can also be specified as boot parameters." +msgstr "" + +#. Tag: screen +#: preseed.xml:775 +#, no-c-format +msgid "" +"# Preseeding only locale sets language, country and locale.\n" +"d-i debian-installer/locale string en_US\n" +"\n" +"# The values can also be preseeded individually for greater flexibility.\n" +"#d-i debian-installer/language string en\n" +"#d-i debian-installer/country string NL\n" +"#d-i debian-installer/locale string en_GB.UTF-8\n" +"# Optionally specify additional locales to be generated.\n" +"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8" +msgstr "" + +#. Tag: para +#: preseed.xml:777 +#, no-c-format +msgid "" +"Keyboard configuration consists of selecting a keymap and (for non-latin " +"keymaps) a toggle key to switch between the non-latin keymap and the US " +"keymap. Only basic keymap variants are available during installation. " +"Advanced variants are available only in the installed system, through " +"<command>dpkg-reconfigure keyboard-configuration</command>." +msgstr "" + +#. Tag: screen +#: preseed.xml:785 +#, no-c-format +msgid "" +"# Keyboard selection.\n" +"d-i keyboard-configuration/xkb-keymap select us\n" +"# d-i keyboard-configuration/toggle select No toggling" +msgstr "" + +#. Tag: para +#: preseed.xml:787 +#, no-c-format +msgid "" +"To skip keyboard configuration, preseed <classname>keymap</classname> with " +"<userinput>skip-config</userinput>. This will result in the kernel keymap " +"remaining active." +msgstr "" + +#. Tag: title +#: preseed.xml:799 +#, no-c-format +msgid "Network configuration" +msgstr "" + +#. Tag: para +#: preseed.xml:800 +#, no-c-format +msgid "" +"Of course, preseeding the network configuration won't work if you're loading " +"your preconfiguration file from the network. But it's great when you're " +"booting from optical disc or USB stick. If you are loading preconfiguration " +"files from the network, you can pass network config parameters by using " +"kernel boot parameters." +msgstr "" + +#. Tag: para +#: preseed.xml:808 +#, no-c-format +msgid "" +"If you need to pick a particular interface when netbooting before loading a " +"preconfiguration file from the network, use a boot parameter such as " +"<userinput>interface=<replaceable>eth1</replaceable></userinput>." +msgstr "" + +#. Tag: para +#: preseed.xml:814 +#, no-c-format +msgid "" +"Although preseeding the network configuration is normally not possible when " +"using network preseeding (using <quote>preseed/url</quote>), you can use the " +"following hack to work around that, for example if you'd like to set a " +"static address for the network interface. The hack is to force the network " +"configuration to run again after the preconfiguration file has been loaded " +"by creating a <quote>preseed/run</quote> script containing the following " +"commands:" +msgstr "" + +#. Tag: screen +#: preseed.xml:824 +#, no-c-format +msgid "kill-all-dhcp; netcfg" +msgstr "" + +#. Tag: para +#: preseed.xml:826 +#, no-c-format +msgid "The following debconf variables are relevant for network configuration." +msgstr "" + +#. Tag: screen +#: preseed.xml:832 +#, no-c-format +msgid "" +"# Disable network configuration entirely. This is useful for cdrom\n" +"# installations on non-networked devices where the network questions,\n" +"# warning and long timeouts are a nuisance.\n" +"#d-i netcfg/enable boolean false\n" +"\n" +"# netcfg will choose an interface that has link if possible. This makes it\n" +"# skip displaying a list if there is more than one interface.\n" +"d-i netcfg/choose_interface select auto\n" +"\n" +"# To pick a particular interface instead:\n" +"#d-i netcfg/choose_interface select eth1\n" +"\n" +"# To set a different link detection timeout (default is 3 seconds).\n" +"# Values are interpreted as seconds.\n" +"#d-i netcfg/link_wait_timeout string 10\n" +"\n" +"# If you have a slow dhcp server and the installer times out waiting for\n" +"# it, this might be useful.\n" +"#d-i netcfg/dhcp_timeout string 60\n" +"#d-i netcfg/dhcpv6_timeout string 60\n" +"\n" +"# If you prefer to configure the network manually, uncomment this line and\n" +"# the static network configuration below.\n" +"#d-i netcfg/disable_autoconfig boolean true\n" +"\n" +"# If you want the preconfiguration file to work on systems both with and\n" +"# without a dhcp server, uncomment these lines and the static network\n" +"# configuration below.\n" +"#d-i netcfg/dhcp_failed note\n" +"#d-i netcfg/dhcp_options select Configure network manually\n" +"\n" +"# Static network configuration.\n" +"#\n" +"# IPv4 example\n" +"#d-i netcfg/get_ipaddress string 192.168.1.42\n" +"#d-i netcfg/get_netmask string 255.255.255.0\n" +"#d-i netcfg/get_gateway string 192.168.1.1\n" +"#d-i netcfg/get_nameservers string 192.168.1.1\n" +"#d-i netcfg/confirm_static boolean true\n" +"#\n" +"# IPv6 example\n" +"#d-i netcfg/get_ipaddress string fc00::2\n" +"#d-i netcfg/get_netmask string ffff:ffff:ffff:ffff::\n" +"#d-i netcfg/get_gateway string fc00::1\n" +"#d-i netcfg/get_nameservers string fc00::1\n" +"#d-i netcfg/confirm_static boolean true\n" +"\n" +"# Any hostname and domain names assigned from dhcp take precedence over\n" +"# values set here. However, setting the values still prevents the questions\n" +"# from being shown, even if values come from dhcp.\n" +"d-i netcfg/get_hostname string unassigned-hostname\n" +"d-i netcfg/get_domain string unassigned-domain\n" +"\n" +"# If you want to force a hostname, regardless of what either the DHCP\n" +"# server returns or what the reverse DNS entry for the IP is, uncomment\n" +"# and adjust the following line.\n" +"#d-i netcfg/hostname string somehost\n" +"\n" +"# Disable that annoying WEP key dialog.\n" +"d-i netcfg/wireless_wep string\n" +"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n" +"#d-i netcfg/dhcp_hostname string radish\n" +"\n" +"# If non-free firmware is needed for the network or other hardware, you can\n" +"# configure the installer to always try to load it, without prompting. Or\n" +"# change to false to disable asking.\n" +"#d-i hw-detect/load_firmware boolean true" +msgstr "" + +#. Tag: para +#: preseed.xml:834 +#, no-c-format +msgid "" +"Please note that <command>netcfg</command> will automatically determine the " +"netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In " +"this case, the variable has to be marked as <literal>seen</literal> for " +"automatic installations. Similarly, <command>netcfg</command> will choose an " +"appropriate address if <classname>netcfg/get_gateway</classname> is not set. " +"As a special case, you can set <classname>netcfg/get_gateway</classname> to " +"<quote>none</quote> to specify that no gateway should be used." +msgstr "" + +#. Tag: title +#: preseed.xml:850 +#, no-c-format +msgid "Network console" +msgstr "" + +#. Tag: screen +#: preseed.xml:852 +#, no-c-format +msgid "" +"# Use the following settings if you wish to make use of the network-console\n" +"# component for remote installation over SSH. This only makes sense if you\n" +"# intend to perform the remainder of the installation manually.\n" +"#d-i anna/choose_modules string network-console\n" +"#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key\n" +"#d-i network-console/password password r00tme\n" +"#d-i network-console/password-again password r00tme" +msgstr "" + +#. Tag: title +#: preseed.xml:857 +#, no-c-format +msgid "Mirror settings" +msgstr "" + +#. Tag: para +#: preseed.xml:858 +#, no-c-format +msgid "" +"Depending on the installation method you use, a mirror may be used to " +"download additional components of the installer, to install the base system, " +"and to set up the <filename>/etc/apt/sources.list</filename> for the " +"installed system." +msgstr "" + +#. Tag: para +#: preseed.xml:865 +#, no-c-format +msgid "" +"The parameter <classname>mirror/suite</classname> determines the suite for " +"the installed system." +msgstr "" + +#. Tag: para +#: preseed.xml:870 +#, no-c-format +msgid "" +"The parameter <classname>mirror/udeb/suite</classname> determines the suite " +"for additional components for the installer. It is only useful to set this " +"if components are actually downloaded over the network and should match the " +"suite that was used to build the initrd for the installation method used for " +"the installation. Normally the installer will automatically use the correct " +"value and there should be no need to set this." +msgstr "" + +#. Tag: screen +#: preseed.xml:881 +#, no-c-format +msgid "" +"# If you select ftp, the mirror/country string does not need to be set.\n" +"#d-i mirror/protocol string ftp\n" +"d-i mirror/country string manual\n" +"d-i mirror/http/hostname string &archive-mirror;\n" +"d-i mirror/http/directory string /debian\n" +"d-i mirror/http/proxy string\n" +"\n" +"# Suite to install.\n" +"#d-i mirror/suite string testing\n" +"# Suite to use for loading installer components (optional).\n" +"#d-i mirror/udeb/suite string testing" +msgstr "" + +#. Tag: title +#: preseed.xml:886 +#, no-c-format +msgid "Account setup" +msgstr "" + +#. Tag: para +#: preseed.xml:887 +#, no-c-format +msgid "" +"The password for the root account and name and password for a first regular " +"user's account can be preseeded. For the passwords you can use either clear " +"text values or crypt(3) <emphasis>hashes</emphasis>." +msgstr "" + +#. Tag: para +#: preseed.xml:894 +#, no-c-format +msgid "" +"Be aware that preseeding passwords is not completely secure as everyone with " +"access to the preconfiguration file will have the knowledge of these " +"passwords. Storing hashed passwords is considered secure unless a weak " +"hashing algorithm like DES or MD5 is used which allow for bruteforce " +"attacks. Recommended password hashing algorithms are SHA-256 and SHA512." +msgstr "" + +#. Tag: screen +#: preseed.xml:904 +#, no-c-format +msgid "" +"# Skip creation of a root account (normal user account will be able to\n" +"# use sudo).\n" +"#d-i passwd/root-login boolean false\n" +"# Alternatively, to skip creation of a normal user account.\n" +"#d-i passwd/make-user boolean false\n" +"\n" +"# Root password, either in clear text\n" +"#d-i passwd/root-password password r00tme\n" +"#d-i passwd/root-password-again password r00tme\n" +"# or encrypted using a crypt(3) hash.\n" +"#d-i passwd/root-password-crypted password [crypt(3) hash]\n" +"\n" +"# To create a normal user account.\n" +"#d-i passwd/user-fullname string Debian User\n" +"#d-i passwd/username string debian\n" +"# Normal user's password, either in clear text\n" +"#d-i passwd/user-password password insecure\n" +"#d-i passwd/user-password-again password insecure\n" +"# or encrypted using a crypt(3) hash.\n" +"#d-i passwd/user-password-crypted password [crypt(3) hash]\n" +"# Create the first user with the specified UID instead of the default.\n" +"#d-i passwd/user-uid string 1010\n" +"\n" +"# The user account will be added to some standard initial groups. To\n" +"# override that, use this.\n" +"#d-i passwd/user-default-groups string audio cdrom video" +msgstr "" + +#. Tag: para +#: preseed.xml:906 +#, no-c-format +msgid "" +"The <classname>passwd/root-password-crypted</classname> and " +"<classname>passwd/user-password-crypted</classname> variables can also be " +"preseeded with <quote>!</quote> as their value. In that case, the " +"corresponding account is disabled. This may be convenient for the root " +"account, provided of course that an alternative method is set up to allow " +"administrative activities or root login (for instance by using SSH key " +"authentication or <command>sudo</command>)." +msgstr "" + +#. Tag: para +#: preseed.xml:916 +#, no-c-format +msgid "" +"The following command (available from the <classname>whois</classname> " +"package) can be used to generate a SHA-512 based crypt(3) hash for a " +"password:" +msgstr "" + +#. Tag: screen +#: preseed.xml:921 +#, no-c-format +msgid "mkpasswd -m sha-512" +msgstr "" + +#. Tag: title +#: preseed.xml:927 +#, no-c-format +msgid "Clock and time zone setup" +msgstr "" + +#. Tag: screen +#: preseed.xml:929 +#, no-c-format +msgid "" +"# Controls whether or not the hardware clock is set to UTC.\n" +"d-i clock-setup/utc boolean true\n" +"\n" +"# You may set this to any valid setting for $TZ; see the contents of\n" +"# /usr/share/zoneinfo/ for valid values.\n" +"d-i time/zone string US/Eastern\n" +"\n" +"# Controls whether to use NTP to set the clock during the install\n" +"d-i clock-setup/ntp boolean true\n" +"# NTP server to use. The default is almost always fine here.\n" +"#d-i clock-setup/ntp-server string ntp.example.com" +msgstr "" + +#. Tag: title +#: preseed.xml:934 +#, no-c-format +msgid "Partitioning" +msgstr "" + +#. Tag: para +#: preseed.xml:935 +#, no-c-format +msgid "" +"Using preseeding to partition the harddisk is limited to what is supported " +"by <classname>partman-auto</classname>. You can choose to partition either " +"existing free space on a disk or a whole disk. The layout of the disk can be " +"determined by using a predefined recipe, a custom recipe from a recipe file " +"or a recipe included in the preconfiguration file." +msgstr "" + +#. Tag: para +#: preseed.xml:943 +#, no-c-format +msgid "" +"Preseeding of advanced partition setups using RAID, LVM and encryption is " +"supported, but not with the full flexibility possible when partitioning " +"during a non-preseeded install." +msgstr "" + +#. Tag: para +#: preseed.xml:949 +#, no-c-format +msgid "" +"The examples below only provide basic information on the use of recipes. For " +"detailed information see the files <filename>partman-auto-recipe.txt</" +"filename> and <filename>partman-auto-raid-recipe.txt</filename> included in " +"the <classname>debian-installer</classname> package. Both files are also " +"available from the <ulink url=\"&url-d-i-doc-devel;\">&d-i; source " +"repository</ulink>. Note that the supported functionality may change between " +"releases." +msgstr "" + +#. Tag: para +#: preseed.xml:963 +#, no-c-format +msgid "" +"The identification of disks is dependent on the order in which their drivers " +"are loaded. If there are multiple disks in the system, make very sure the " +"correct one will be selected before using preseeding." +msgstr "" + +#. Tag: title +#: preseed.xml:972 +#, no-c-format +msgid "Partitioning example" +msgstr "" + +#. Tag: screen +#: preseed.xml:974 +#, no-c-format +msgid "" +"# If the system has free space you can choose to only partition that space.\n" +"# This is only honoured if partman-auto/method (below) is not set.\n" +"#d-i partman-auto/init_automatically_partition select biggest_free\n" +"\n" +"# Alternatively, you may specify a disk to partition. If the system has " +"only\n" +"# one disk the installer will default to using that, but otherwise the " +"device\n" +"# name must be given in traditional, non-devfs format (so e.g. /dev/sda\n" +"# and not e.g. /dev/discs/disc0/disc).\n" +"# For example, to use the first SCSI/SATA hard disk:\n" +"#d-i partman-auto/disk string /dev/sda\n" +"# In addition, you'll need to specify the method to use.\n" +"# The presently available methods are:\n" +"# - regular: use the usual partition types for your architecture\n" +"# - lvm: use LVM to partition the disk\n" +"# - crypto: use LVM within an encrypted partition\n" +"d-i partman-auto/method string lvm\n" +"\n" +"# You can define the amount of space that will be used for the LVM volume\n" +"# group. It can either be a size with its unit (eg. 20 GB), a percentage of\n" +"# free space or the 'max' keyword.\n" +"d-i partman-auto-lvm/guided_size string max\n" +"\n" +"# If one of the disks that are going to be automatically partitioned\n" +"# contains an old LVM configuration, the user will normally receive a\n" +"# warning. This can be preseeded away...\n" +"d-i partman-lvm/device_remove_lvm boolean true\n" +"# The same applies to pre-existing software RAID array:\n" +"d-i partman-md/device_remove_md boolean true\n" +"# And the same goes for the confirmation to write the lvm partitions.\n" +"d-i partman-lvm/confirm boolean true\n" +"d-i partman-lvm/confirm_nooverwrite boolean true\n" +"\n" +"# You can choose one of the three predefined partitioning recipes:\n" +"# - atomic: all files in one partition\n" +"# - home: separate /home partition\n" +"# - multi: separate /home, /var, and /tmp partitions\n" +"d-i partman-auto/choose_recipe select atomic\n" +"\n" +"# Or provide a recipe of your own...\n" +"# If you have a way to get a recipe file into the d-i environment, you can\n" +"# just point at it.\n" +"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n" +"\n" +"# If not, you can put an entire recipe into the preconfiguration file in " +"one\n" +"# (logical) line. This example creates a small /boot partition, suitable\n" +"# swap, and uses the rest of the space for the root partition:\n" +"#d-i partman-auto/expert_recipe string \\\n" +"# boot-root :: \\\n" +"# 40 50 100 ext3 \\\n" +"# $primary{ } $bootable{ } \\\n" +"# method{ format } format{ } \\\n" +"# use_filesystem{ } filesystem{ ext3 } \\\n" +"# mountpoint{ /boot } \\\n" +"# . \\\n" +"# 500 10000 1000000000 ext3 \\\n" +"# method{ format } format{ } \\\n" +"# use_filesystem{ } filesystem{ ext3 } \\\n" +"# mountpoint{ / } \\\n" +"# . \\\n" +"# 64 512 300% linux-swap \\\n" +"# method{ swap } format{ } \\\n" +"# .\n" +"\n" +"# The full recipe format is documented in the file partman-auto-recipe.txt\n" +"# included in the 'debian-installer' package or available from D-I source\n" +"# repository. This also documents how to specify settings such as file\n" +"# system labels, volume group names and which physical devices to include\n" +"# in a volume group.\n" +"\n" +"## Partitioning for EFI\n" +"# If your system needs an EFI partition you could add something like\n" +"# this to the recipe above, as the first element in the recipe:\n" +"# 538 538 1075 free \\\n" +"# $iflabel{ gpt } \\\n" +"# $reusemethod{ } \\\n" +"# method{ efi } \\\n" +"# format{ } \\\n" +"# . \\\n" +"#\n" +"# The fragment above is for the amd64 architecture; the details may be\n" +"# different on other architectures. The 'partman-auto' package in the\n" +"# D-I source repository may have an example you can follow.\n" +"\n" +"# This makes partman automatically partition without confirmation, provided\n" +"# that you told it what to do using one of the methods above.\n" +"d-i partman-partitioning/confirm_write_new_label boolean true\n" +"d-i partman/choose_partition select finish\n" +"d-i partman/confirm boolean true\n" +"d-i partman/confirm_nooverwrite boolean true\n" +"\n" +"# Force UEFI booting ('BIOS compatibility' will be lost). Default: false.\n" +"#d-i partman-efi/non_efi_system boolean true\n" +"# Ensure the partition table is GPT - this is required for EFI\n" +"#d-i partman-partitioning/choose_label string gpt\n" +"#d-i partman-partitioning/default_label string gpt\n" +"\n" +"# When disk encryption is enabled, skip wiping the partitions beforehand.\n" +"#d-i partman-auto-crypto/erase_disks boolean false" +msgstr "" + +#. Tag: title +#: preseed.xml:978 +#, no-c-format +msgid "Partitioning using RAID" +msgstr "" + +#. Tag: para +#: preseed.xml:979 +#, no-c-format +msgid "" +"You can also use preseeding to set up partitions on software RAID arrays. " +"Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and " +"specifying spare devices." +msgstr "" + +#. Tag: para +#: preseed.xml:985 +#, no-c-format +msgid "" +"If you are using RAID 1, you can preseed grub to install to all devices used " +"in the array; see <xref linkend=\"preseed-bootloader\"/>." +msgstr "" + +#. Tag: para +#: preseed.xml:992 +#, no-c-format +msgid "" +"This type of automated partitioning is easy to get wrong. It is also " +"functionality that receives relatively little testing from the developers of " +"&d-i;. The responsibility to get the various recipes right (so they make " +"sense and don't conflict) lies with the user. Check <filename>/var/log/" +"syslog</filename> if you run into problems." +msgstr "" + +#. Tag: screen +#: preseed.xml:1002 +#, no-c-format +msgid "" +"# The method should be set to \"raid\".\n" +"#d-i partman-auto/method string raid\n" +"# Specify the disks to be partitioned. They will all get the same layout,\n" +"# so this will only work if the disks are the same size.\n" +"#d-i partman-auto/disk string /dev/sda /dev/sdb\n" +"\n" +"# Next you need to specify the physical partitions that will be used. \n" +"#d-i partman-auto/expert_recipe string \\\n" +"# multiraid :: \\\n" +"# 1000 5000 4000 raid \\\n" +"# $primary{ } method{ raid } \\\n" +"# . \\\n" +"# 64 512 300% raid \\\n" +"# method{ raid } \\\n" +"# . \\\n" +"# 500 10000 1000000000 raid \\\n" +"# method{ raid } \\\n" +"# .\n" +"\n" +"# Last you need to specify how the previously defined partitions will be\n" +"# used in the RAID setup. Remember to use the correct partition numbers\n" +"# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported;\n" +"# devices are separated using \"#\".\n" +"# Parameters are:\n" +"# <raidtype> <devcount> <sparecount> <fstype> <" +"mountpoint> \\\n" +"# <devices> <sparedevices>\n" +"\n" +"#d-i partman-auto-raid/recipe string \\\n" +"# 1 2 0 ext3 / \\\n" +"# /dev/sda1#/dev/sdb1 \\\n" +"# . \\\n" +"# 1 2 0 swap - \\\n" +"# /dev/sda5#/dev/sdb5 \\\n" +"# . \\\n" +"# 0 2 0 ext3 /home \\\n" +"# /dev/sda6#/dev/sdb6 \\\n" +"# .\n" +"\n" +"# For additional information see the file partman-auto-raid-recipe.txt\n" +"# included in the 'debian-installer' package or available from D-I source\n" +"# repository.\n" +"\n" +"# This makes partman automatically partition without confirmation.\n" +"d-i partman-md/confirm boolean true\n" +"d-i partman-partitioning/confirm_write_new_label boolean true\n" +"d-i partman/choose_partition select finish\n" +"d-i partman/confirm boolean true\n" +"d-i partman/confirm_nooverwrite boolean true" +msgstr "" + +#. Tag: title +#: preseed.xml:1007 +#, no-c-format +msgid "Controlling how partitions are mounted" +msgstr "" + +#. Tag: para +#: preseed.xml:1008 +#, no-c-format +msgid "" +"Normally, filesystems are mounted using a universally unique identifier " +"(UUID) as a key; this allows them to be mounted properly even if their " +"device name changes. UUIDs are long and difficult to read, so, if you " +"prefer, the installer can mount filesystems based on the traditional device " +"names, or based on a label you assign. If you ask the installer to mount by " +"label, any filesystems without a label will be mounted using a UUID instead." +msgstr "" + +#. Tag: para +#: preseed.xml:1017 +#, no-c-format +msgid "" +"Devices with stable names, such as LVM logical volumes, will continue to use " +"their traditional names rather than UUIDs." +msgstr "" + +#. Tag: para +#: preseed.xml:1024 +#, no-c-format +msgid "" +"Traditional device names may change based on the order in which the kernel " +"discovers devices at boot, which may cause the wrong filesystem to be " +"mounted. Similarly, labels are likely to clash if you plug in a new disk or " +"a USB drive, and if that happens your system's behaviour when started will " +"be random." +msgstr "" + +#. Tag: screen +#: preseed.xml:1034 +#, no-c-format +msgid "" +"# The default is to mount by UUID, but you can also choose \"traditional\" " +"to\n" +"# use traditional device names, or \"label\" to try filesystem labels " +"before\n" +"# falling back to UUIDs.\n" +"#d-i partman/mount_style select uuid" +msgstr "" + +#. Tag: title +#: preseed.xml:1040 +#, no-c-format +msgid "Base system installation" +msgstr "" + +#. Tag: para +#: preseed.xml:1041 +#, no-c-format +msgid "" +"There is actually not very much that can be preseeded for this stage of the " +"installation. The only questions asked concern the installation of the " +"kernel." +msgstr "" + +#. Tag: screen +#: preseed.xml:1048 +#, no-c-format +msgid "" +"# Configure APT to not install recommended packages by default. Use of this\n" +"# option can result in an incomplete system and should only be used by very\n" +"# experienced users.\n" +"#d-i base-installer/install-recommends boolean false\n" +"\n" +"# The kernel image (meta) package to be installed; \"none\" can be used if " +"no\n" +"# kernel is to be installed.\n" +"#d-i base-installer/kernel/image string &kernelpackage;-686" +msgstr "" + +#. Tag: title +#: preseed.xml:1053 +#, no-c-format +msgid "Apt setup" +msgstr "" + +#. Tag: para +#: preseed.xml:1054 +#, no-c-format +msgid "" +"Setup of the <filename>/etc/apt/sources.list</filename> and basic " +"configuration options is fully automated based on your installation method " +"and answers to earlier questions. You can optionally add other (local) " +"repositories." +msgstr "" + +#. Tag: screen +#: preseed.xml:1062 +#, no-c-format +msgid "" +"# You can choose to install non-free and contrib software.\n" +"#d-i apt-setup/non-free boolean true\n" +"#d-i apt-setup/contrib boolean true\n" +"# Uncomment this if you don't want to use a network mirror.\n" +"#d-i apt-setup/use_mirror boolean false\n" +"# Select which update services to use; define the mirrors to be used.\n" +"# Values shown below are the normal defaults.\n" +"#d-i apt-setup/services-select multiselect security, updates\n" +"#d-i apt-setup/security_host string security.debian.org\n" +"\n" +"# Additional repositories, local[0-9] available\n" +"#d-i apt-setup/local0/repository string \\\n" +"# http://local.server/debian stable main\n" +"#d-i apt-setup/local0/comment string local server\n" +"# Enable deb-src lines\n" +"#d-i apt-setup/local0/source boolean true\n" +"# URL to the public key of the local repository; you must provide a key or\n" +"# apt will complain about the unauthenticated repository and so the\n" +"# sources.list line will be left commented out.\n" +"#d-i apt-setup/local0/key string http://local.server/key\n" +"# If the provided key file ends in \".asc\" the key file needs to be an\n" +"# ASCII-armoured PGP key, if it ends in \".gpg\" it needs to use the\n" +"# \"GPG key public keyring\" format, the \"keybox database\" format is\n" +"# currently not supported.\n" +"\n" +"# By default the installer requires that repositories be authenticated\n" +"# using a known gpg key. This setting can be used to disable that\n" +"# authentication. Warning: Insecure, not recommended.\n" +"#d-i debian-installer/allow_unauthenticated boolean true\n" +"\n" +"# Uncomment this to add multiarch configuration for i386\n" +"#d-i apt-setup/multiarch string i386" +msgstr "" + +#. Tag: title +#: preseed.xml:1067 +#, no-c-format +msgid "Package selection" +msgstr "" + +#. Tag: para +#: preseed.xml:1068 +#, no-c-format +msgid "" +"You can choose to install any combination of tasks that are available. " +"Available tasks as of this writing include:" +msgstr "" + +#. Tag: para +#: preseed.xml:1076 +#, no-c-format +msgid "<userinput>standard</userinput> (standard tools)" +msgstr "" + +#. Tag: para +#: preseed.xml:1079 +#, no-c-format +msgid "<userinput>desktop</userinput> (graphical desktop)" +msgstr "" + +#. Tag: para +#: preseed.xml:1082 +#, no-c-format +msgid "<userinput>gnome-desktop</userinput> (Gnome desktop)" +msgstr "" + +#. Tag: para +#: preseed.xml:1085 +#, no-c-format +msgid "<userinput>xfce-desktop</userinput> (XFCE desktop)" +msgstr "" + +#. Tag: para +#: preseed.xml:1088 +#, no-c-format +msgid "<userinput>kde-desktop</userinput> (KDE Plasma desktop)" +msgstr "" + +#. Tag: para +#: preseed.xml:1091 +#, no-c-format +msgid "<userinput>cinnamon-desktop</userinput> (Cinnamon desktop)" +msgstr "" + +#. Tag: para +#: preseed.xml:1094 +#, no-c-format +msgid "<userinput>mate-desktop</userinput> (MATE desktop)" +msgstr "" + +#. Tag: para +#: preseed.xml:1097 +#, no-c-format +msgid "<userinput>lxde-desktop</userinput> (LXDE desktop)" +msgstr "" + +#. Tag: para +#: preseed.xml:1100 +#, no-c-format +msgid "<userinput>web-server</userinput> (web server)" +msgstr "" + +#. Tag: para +#: preseed.xml:1103 +#, no-c-format +msgid "<userinput>ssh-server</userinput> (SSH server)" +msgstr "" + +#. Tag: para +#: preseed.xml:1108 +#, no-c-format +msgid "" +"You can also choose to install no tasks, and force the installation of a set " +"of packages in some other way. We recommend always including the " +"<userinput>standard</userinput> task." +msgstr "" + +#. Tag: para +#: preseed.xml:1114 +#, no-c-format +msgid "" +"If you want to install some individual packages in addition to packages " +"installed by tasks, you can use the parameter <classname>pkgsel/include</" +"classname>. The value of this parameter can be a list of packages separated " +"by either commas or spaces, which allows it to be used easily on the kernel " +"command line as well." +msgstr "" + +#. Tag: screen +#: preseed.xml:1124 +#, no-c-format +msgid "" +"#tasksel tasksel/first multiselect standard, web-server, kde-desktop\n" +"\n" +"# Individual additional packages to install\n" +"#d-i pkgsel/include string openssh-server build-essential\n" +"# Whether to upgrade packages after debootstrap.\n" +"# Allowed values: none, safe-upgrade, full-upgrade\n" +"#d-i pkgsel/upgrade select none\n" +"\n" +"# Some versions of the installer can report back on what software you have\n" +"# installed, and what software you use. The default is not to report back,\n" +"# but sending reports helps the project determine what software is most\n" +"# popular and should be included on the first CD/DVD.\n" +"#popularity-contest popularity-contest/participate boolean false" +msgstr "" + +#. Tag: title +#: preseed.xml:1129 +#, no-c-format +msgid "Boot loader installation" +msgstr "" + +#. Tag: screen +#: preseed.xml:1131 +#, no-c-format +msgid "" +"<phrase arch=\"linux-any\"># Grub is the boot loader (for x86).</" +"phrase><phrase\n" +"arch=\"kfreebsd-any;hurd-any\"># To install no bootloader, uncomment this\n" +"#d-i grub-installer/skip boolean true</phrase>\n" +"\n" +"# This is fairly safe to set, it makes grub install automatically to the " +"UEFI\n" +"# partition/boot record if no other operating system is detected on the " +"machine.\n" +"d-i grub-installer/only_debian boolean true\n" +"\n" +"# This one makes grub-installer install to the UEFI partition/boot record, " +"if\n" +"# it also finds some other OS, which is less safe as it might not be able " +"to\n" +"# boot that other OS.\n" +"d-i grub-installer/with_other_os boolean true\n" +"\n" +"# Due notably to potential USB sticks, the location of the primary drive " +"can\n" +"# not be determined safely in general, so this needs to be specified:\n" +"#d-i grub-installer/bootdev string /dev/sda\n" +"# To install to the primary device (assuming it is not a USB stick):\n" +"#d-i grub-installer/bootdev string default\n" +"\n" +"# Alternatively, if you want to install to a location other than the UEFI\n" +"# parition/boot record, uncomment and edit these lines:\n" +"#d-i grub-installer/only_debian boolean false\n" +"#d-i grub-installer/with_other_os boolean false\n" +"#d-i grub-installer/bootdev string (hd0,1)\n" +"# To install grub to multiple disks:\n" +"#d-i grub-installer/bootdev string (hd0,1) (hd1,1) (hd2,1)\n" +"\n" +"# Optional password for grub, either in clear text\n" +"#d-i grub-installer/password password r00tme\n" +"#d-i grub-installer/password-again password r00tme\n" +"# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n" +"#d-i grub-installer/password-crypted password [MD5 hash]\n" +"\n" +"# Use the following option to add additional boot parameters for the\n" +"# installed system (if supported by the bootloader installer).\n" +"# Note: options passed to the installer will be added automatically.\n" +"#d-i debian-installer/add-kernel-opts string nousb" +msgstr "" + +#. Tag: para +#: preseed.xml:1133 +#, no-c-format +msgid "" +"An MD5 hash for a password for <classname>grub</classname> can be generated " +"using <command>grub-md5-crypt</command>, or using the command from the " +"example in <xref linkend=\"preseed-account\"/>." +msgstr "" + +#. Tag: title +#: preseed.xml:1143 +#, no-c-format +msgid "Finishing up the installation" +msgstr "" + +#. Tag: screen +#: preseed.xml:1145 +#, no-c-format +msgid "" +"# During installations from serial console, the regular virtual consoles\n" +"# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next\n" +"# line to prevent this.\n" +"#d-i finish-install/keep-consoles boolean true\n" +"\n" +"# Avoid that last message about the install being complete.\n" +"d-i finish-install/reboot_in_progress note\n" +"\n" +"# This will prevent the installer from ejecting the CD during the reboot,\n" +"# which is useful in some situations.\n" +"#d-i cdrom-detect/eject boolean false\n" +"\n" +"# This is how to make the installer shutdown when finished, but not\n" +"# reboot into the installed system.\n" +"#d-i debian-installer/exit/halt boolean true\n" +"# This will power off the machine instead of just halting it.\n" +"#d-i debian-installer/exit/poweroff boolean true" +msgstr "" + +#. Tag: title +#: preseed.xml:1150 +#, no-c-format +msgid "Preseeding other packages" +msgstr "" + +#. Tag: screen +#: preseed.xml:1152 +#, no-c-format +msgid "" +"# Depending on what software you choose to install, or if things go wrong\n" +"# during the installation process, it's possible that other questions may\n" +"# be asked. You can preseed those too, of course. To get a list of every\n" +"# possible question that could be asked during an install, do an\n" +"# installation, and then run these commands:\n" +"# debconf-get-selections --installer > file\n" +"# debconf-get-selections >> file" +msgstr "" + +#. Tag: title +#: preseed.xml:1159 +#, no-c-format +msgid "Advanced options" +msgstr "" + +#. Tag: title +#: preseed.xml:1162 +#, no-c-format +msgid "Running custom commands during the installation" +msgstr "" + +#. Tag: para +#: preseed.xml:1163 +#, no-c-format +msgid "" +"A very powerful and flexible option offered by the preconfiguration tools is " +"the ability to run commands or scripts at certain points in the installation." +msgstr "" + +#. Tag: para +#: preseed.xml:1169 +#, no-c-format +msgid "" +"When the filesystem of the target system is mounted, it is available in " +"<filename>/target</filename>. If an installation CD is used, when it is " +"mounted it is available in <filename>/cdrom</filename>." +msgstr "" + +#. Tag: screen +#: preseed.xml:1177 +#, no-c-format +msgid "" +"# d-i preseeding is inherently not secure. Nothing in the installer checks\n" +"# for attempts at buffer overflows or other exploits of the values of a\n" +"# preconfiguration file like this one. Only use preconfiguration files from\n" +"# trusted locations! To drive that home, and because it's generally useful,\n" +"# here's a way to run any shell command you'd like inside the installer,\n" +"# automatically.\n" +"\n" +"# This first command is run as early as possible, just after\n" +"# preseeding is read.\n" +"#d-i preseed/early_command string anna-install some-udeb\n" +"# This command is run immediately before the partitioner starts. It may be\n" +"# useful to apply dynamic partitioner preseeding that depends on the state\n" +"# of the disks (which may not be visible when preseed/early_command runs).\n" +"#d-i partman/early_command \\\n" +"# string debconf-set partman-auto/disk \"$(list-devices disk | head -" +"n1)\"\n" +"# This command is run just before the install finishes, but when there is\n" +"# still a usable /target directory. You can chroot to /target and use it\n" +"# directly, or use the apt-install and in-target commands to easily install\n" +"# packages and run commands in the target system.\n" +"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh" +msgstr "" + +#. Tag: title +#: preseed.xml:1182 +#, no-c-format +msgid "Using preseeding to change default values" +msgstr "" + +#. Tag: para +#: preseed.xml:1183 +#, no-c-format +msgid "" +"It is possible to use preseeding to change the default answer for a " +"question, but still have the question asked. To do this the <firstterm>seen</" +"firstterm> flag must be reset to <quote>false</quote> after setting the " +"value for a question. <informalexample><screen>\n" +"d-i foo/bar string value\n" +"d-i foo/bar seen false\n" +"</screen></informalexample> The same effect can be achieved for " +"<emphasis>all</emphasis> questions by setting the parameter " +"<classname>preseed/interactive=true</classname> at the boot prompt. This can " +"also be useful for testing or debugging your preconfiguration file." +msgstr "" + +#. Tag: para +#: preseed.xml:1197 +#, no-c-format +msgid "" +"Note that the <quote>d-i</quote> owner should only be used for variables " +"used in the installer itself. For variables belonging to packages installed " +"on the target system, you should use the name of that package instead. See " +"the footnote to <xref linkend=\"preseed-bootparms\"/>." +msgstr "" + +#. Tag: para +#: preseed.xml:1204 +#, no-c-format +msgid "" +"If you are preseeding using boot parameters, you can make the installer ask " +"the corresponding question by using the <quote>?=</quote> operator, i.e. " +"<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?" +"=<replaceable>value</replaceable></userinput> (or " +"<userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</" +"replaceable>?=<replaceable>value</replaceable></userinput>). This will of " +"course only have effect for parameters that correspond to questions that are " +"actually displayed during an installation and not for <quote>internal</" +"quote> parameters." +msgstr "" + +#. Tag: para +#: preseed.xml:1214 +#, no-c-format +msgid "" +"For more debugging information, use the boot parameter " +"<classname>DEBCONF_DEBUG=5</classname>. This will cause <classname>debconf</" +"classname> to print much more detail about the current settings of each " +"variable and about its progress through each package's installation scripts." +msgstr "" + +#. Tag: title +#: preseed.xml:1226 +#, no-c-format +msgid "Chainloading preconfiguration files" +msgstr "" + +#. Tag: para +#: preseed.xml:1227 +#, no-c-format +msgid "" +"It is possible to include other preconfiguration files from a " +"preconfiguration file. Any settings in those files will override pre-" +"existing settings from files loaded earlier. This makes it possible to put, " +"for example, general networking settings for your location in one file and " +"more specific settings for certain configurations in other files." +msgstr "" + +#. Tag: screen +#: preseed.xml:1237 +#, no-c-format +msgid "" +"# More than one file can be listed, separated by spaces; all will be\n" +"# loaded. The included files can have preseed/include directives of their\n" +"# own as well. Note that if the filenames are relative, they are taken from\n" +"# the same directory as the preconfiguration file that includes them.\n" +"#d-i preseed/include string x.cfg\n" +"\n" +"# The installer can optionally verify checksums of preconfiguration files\n" +"# before using them. Currently only md5sums are supported, list the md5sums\n" +"# in the same order as the list of files to include.\n" +"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n" +"\n" +"# More flexibly, this runs a shell command and if it outputs the names of\n" +"# preconfiguration files, includes those files. \n" +"#d-i preseed/include_command \\\n" +"# string if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi\n" +"\n" +"# Most flexibly of all, this downloads a program and runs it. The program\n" +"# can use commands such as debconf-set to manipulate the debconf database.\n" +"# More than one script can be listed, separated by spaces.\n" +"# Note that if the filenames are relative, they are taken from the same\n" +"# directory as the preconfiguration file that runs them.\n" +"#d-i preseed/run string foo.sh" +msgstr "" + +#. Tag: para +#: preseed.xml:1239 +#, no-c-format +msgid "" +"It is also possible to chainload from the initrd or file preseeding phase, " +"into network preseeding by setting preseed/url in the earlier files. This " +"will cause network preseeding to be performed when the network comes up. You " +"need to be careful when doing this, since there will be two distinct runs at " +"preseeding, meaning for example that you get another chance to run the " +"preseed/early command, the second one happening after the network comes up." +msgstr "" diff --git a/po/kab/random-bits.po b/po/kab/random-bits.po new file mode 100644 index 000000000..1866b0740 --- /dev/null +++ b/po/kab/random-bits.po @@ -0,0 +1,1613 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-random-bits 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-04-05 16:28+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: random-bits.xml:4 +#, no-c-format +msgid "Random Bits" +msgstr "" + +#. Tag: title +#: random-bits.xml:11 +#, no-c-format +msgid "Linux Devices" +msgstr "" + +#. Tag: para +#: random-bits.xml:12 +#, no-c-format +msgid "" +"In Linux various special files can be found under the directory <filename>/" +"dev</filename>. These files are called device files and behave unlike " +"ordinary files. The most common types of device files are for block devices " +"and character devices. These files are an interface to the actual driver " +"(part of the Linux kernel) which in turn accesses the hardware. Another, " +"less common, type of device file is the named <firstterm>pipe</firstterm>. " +"The most important device files are listed in the tables below." +msgstr "" + +#. Tag: filename +#: random-bits.xml:27 +#, no-c-format +msgid "<filename>sda</filename>" +msgstr "" + +#. Tag: entry +#: random-bits.xml:28 +#, no-c-format +msgid "First hard disk" +msgstr "" + +#. Tag: filename +#: random-bits.xml:30 +#, no-c-format +msgid "<filename>sdb</filename>" +msgstr "" + +#. Tag: entry +#: random-bits.xml:31 +#, no-c-format +msgid "Second hard disk" +msgstr "" + +#. Tag: filename +#: random-bits.xml:33 +#, no-c-format +msgid "sda1" +msgstr "" + +#. Tag: entry +#: random-bits.xml:34 +#, no-c-format +msgid "First partition of the first hard disk" +msgstr "" + +#. Tag: filename +#: random-bits.xml:36 +#, no-c-format +msgid "sdb7" +msgstr "" + +#. Tag: entry +#: random-bits.xml:37 +#, no-c-format +msgid "Seventh partition of the second hard disk" +msgstr "" + +#. Tag: filename +#: random-bits.xml:43 +#, no-c-format +msgid "<filename>sr0</filename>" +msgstr "" + +#. Tag: entry +#: random-bits.xml:44 +#, no-c-format +msgid "First CD-ROM" +msgstr "" + +#. Tag: filename +#: random-bits.xml:46 +#, no-c-format +msgid "<filename>sr1</filename>" +msgstr "" + +#. Tag: entry +#: random-bits.xml:47 +#, no-c-format +msgid "Second CD-ROM" +msgstr "" + +#. Tag: filename +#: random-bits.xml:53 +#, no-c-format +msgid "ttyS0" +msgstr "" + +#. Tag: entry +#: random-bits.xml:54 +#, no-c-format +msgid "Serial port 0, COM1 under MS-DOS" +msgstr "" + +#. Tag: filename +#: random-bits.xml:56 +#, no-c-format +msgid "ttyS1" +msgstr "" + +#. Tag: entry +#: random-bits.xml:57 +#, no-c-format +msgid "Serial port 1, COM2 under MS-DOS" +msgstr "" + +#. Tag: filename +#: random-bits.xml:59 +#, no-c-format +msgid "psaux" +msgstr "" + +#. Tag: entry +#: random-bits.xml:60 +#, no-c-format +msgid "PS/2 mouse device" +msgstr "" + +#. Tag: filename +#: random-bits.xml:62 +#, no-c-format +msgid "gpmdata" +msgstr "" + +#. Tag: entry +#: random-bits.xml:63 +#, no-c-format +msgid "Pseudo device, repeater data from GPM (mouse) daemon" +msgstr "" + +#. Tag: filename +#: random-bits.xml:69 +#, no-c-format +msgid "cdrom" +msgstr "" + +#. Tag: entry +#: random-bits.xml:70 +#, no-c-format +msgid "Symbolic link to the CD-ROM drive" +msgstr "" + +#. Tag: filename +#: random-bits.xml:72 +#, no-c-format +msgid "mouse" +msgstr "" + +#. Tag: entry +#: random-bits.xml:73 +#, no-c-format +msgid "Symbolic link to the mouse device file" +msgstr "" + +#. Tag: filename +#: random-bits.xml:79 +#, no-c-format +msgid "null" +msgstr "" + +#. Tag: entry +#: random-bits.xml:80 +#, no-c-format +msgid "Anything written to this device will disappear" +msgstr "" + +#. Tag: filename +#: random-bits.xml:82 +#, no-c-format +msgid "zero" +msgstr "" + +#. Tag: entry +#: random-bits.xml:83 +#, no-c-format +msgid "One can endlessly read zeros out of this device" +msgstr "" + +#. Tag: title +#: random-bits.xml:90 +#, no-c-format +msgid "Setting Up Your Mouse" +msgstr "" + +#. Tag: para +#: random-bits.xml:91 +#, no-c-format +msgid "" +"The mouse can be used in both the Linux console (with gpm) and the X window " +"environment. Normally, this is a simple matter of installing <filename>gpm</" +"filename> and the X server itself. Both should be configured to use " +"<filename>/dev/input/mice</filename> as the mouse device. The correct mouse " +"protocol is named <userinput>exps2</userinput> in gpm, and " +"<userinput>ExplorerPS/2</userinput> in X. The respective configuration files " +"are <filename>/etc/gpm.conf</filename> and <filename>/etc/X11/xorg.conf</" +"filename>." +msgstr "" + +#. Tag: para +#: random-bits.xml:102 +#, no-c-format +msgid "" +"Certain kernel modules must be loaded in order for your mouse to work. In " +"most cases the correct modules are autodetected, but not always for old-" +"style serial and bus mice<footnote> <para> Serial mice usually have a 9-hole " +"D-shaped connector; bus mice have an 8-pin round connector, not to be " +"confused with the 6-pin round connector of a PS/2 mouse or the 4-pin round " +"connector of an ADB mouse. </para> </footnote>, which are quite rare except " +"on very old computers. Summary of Linux kernel modules needed for different " +"mouse types: <informaltable><tgroup cols=\"2\"><thead> <row> <entry>Module</" +"entry> <entry>Description</entry> </row> </thead><tbody> <row> " +"<entry>psmouse</entry> <entry>PS/2 mice (should be autodetected)</entry> </" +"row> <row> <entry>usbhid</entry> <entry>USB mice (should be autodetected)</" +"entry> </row> <row> <entry>sermouse</entry> <entry>Most serial mice</entry> " +"</row> <row> <entry>logibm</entry> <entry>Bus mouse connected to Logitech " +"adapter card</entry> </row> <row> <entry>inport</entry> <entry>Bus mouse " +"connected to ATI or Microsoft InPort card</entry> </row> </tbody></tgroup></" +"informaltable> To load a mouse driver module, you can use the " +"<command>modconf</command> command (from the package with the same name) and " +"look in the category <userinput>kernel/drivers/input/mouse</userinput>." +msgstr "" + +#. Tag: para +#: random-bits.xml:149 +#, no-c-format +msgid "" +"Modern kernels give you the capability to emulate a three-button mouse when " +"your mouse only has one button. Just add the following lines to <filename>/" +"etc/sysctl.conf</filename> file." +msgstr "" + +#. Tag: screen +#: random-bits.xml:156 +#, no-c-format +msgid "" +"# 3-button mouse emulation\n" +"# turn on emulation\n" +"/dev/mac_hid/mouse_button_emulation = 1\n" +"# Send middle mouse button signal with the F11 key\n" +"/dev/mac_hid/mouse_button2_keycode = 87\n" +"# Send right mouse button signal with the F12 key\n" +"/dev/mac_hid/mouse_button3_keycode = 88\n" +"# For different keys, use showkey to tell you what the code is." +msgstr "" + +#. Tag: title +#: random-bits.xml:163 +#, no-c-format +msgid "Disk Space Needed for Tasks" +msgstr "" + +#. Tag: para +#: random-bits.xml:164 +#, no-c-format +msgid "" +"A standard installation for the amd64 architecture, including all standard " +"packages and using the default kernel, takes up &std-system-size;MB of disk " +"space. A minimal base installation, without the <quote>Standard system</" +"quote> task selected, will take &base-system-size;MB." +msgstr "" + +#. Tag: para +#: random-bits.xml:172 +#, 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:181 +#, 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:188 +#, no-c-format +msgid "" +"By default the installer will install the GNOME desktop environment, but " +"alternative desktop environments can be selected either by using one of the " +"special installation images, or by specifying the desired desktop " +"environment during installation (see <xref linkend=\"pkgsel\"/>)." +msgstr "" + +#. Tag: para +#: random-bits.xml:195 +#, no-c-format +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:209 +#, no-c-format +msgid "Task" +msgstr "" + +#. Tag: entry +#: random-bits.xml:210 +#, no-c-format +msgid "Installed size (MB)" +msgstr "" + +#. Tag: entry +#: random-bits.xml:211 +#, no-c-format +msgid "Download size (MB)" +msgstr "" + +#. Tag: entry +#: random-bits.xml:212 +#, no-c-format +msgid "Space needed to install (MB)" +msgstr "" + +#. Tag: entry +#: random-bits.xml:218 +#, no-c-format +msgid "Desktop environment" +msgstr "" + +#. Tag: entry +#: random-bits.xml:219 random-bits.xml:220 random-bits.xml:221 +#, no-c-format +msgid " " +msgstr "" + +#. Tag: entry +#: random-bits.xml:224 +#, no-c-format +msgid " • GNOME (default)" +msgstr "" + +#. Tag: entry +#: random-bits.xml:225 +#, no-c-format +msgid "&task-desktop-gnome-inst;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:226 +#, no-c-format +msgid "&task-desktop-gnome-dl;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:227 +#, no-c-format +msgid "&task-desktop-gnome-tot;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:230 +#, no-c-format +msgid " • KDE Plasma" +msgstr "" + +#. Tag: entry +#: random-bits.xml:231 +#, no-c-format +msgid "&task-desktop-kde-inst;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:232 +#, no-c-format +msgid "&task-desktop-kde-dl;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:233 +#, no-c-format +msgid "&task-desktop-kde-tot;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:236 +#, no-c-format +msgid " • Xfce" +msgstr "" + +#. Tag: entry +#: random-bits.xml:237 +#, no-c-format +msgid "&task-desktop-xfce-inst;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:238 +#, no-c-format +msgid "&task-desktop-xfce-dl;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:239 +#, no-c-format +msgid "&task-desktop-xfce-tot;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:242 +#, no-c-format +msgid " • LXDE" +msgstr "" + +#. Tag: entry +#: random-bits.xml:243 +#, no-c-format +msgid "&task-desktop-lxde-inst;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:244 +#, no-c-format +msgid "&task-desktop-lxde-dl;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:245 +#, no-c-format +msgid "&task-desktop-lxde-tot;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:248 +#, no-c-format +msgid " • MATE" +msgstr "" + +#. Tag: entry +#: random-bits.xml:249 +#, no-c-format +msgid "&task-desktop-mate-inst;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:250 +#, no-c-format +msgid "&task-desktop-mate-dl;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:251 +#, no-c-format +msgid "&task-desktop-mate-tot;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:254 +#, no-c-format +msgid " • Cinnamon" +msgstr "" + +#. Tag: entry +#: random-bits.xml:255 +#, no-c-format +msgid "&task-desktop-cinnamon-inst;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:256 +#, no-c-format +msgid "&task-desktop-cinnamon-dl;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:257 +#, no-c-format +msgid "&task-desktop-cinnamon-tot;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:261 +#, no-c-format +msgid "Web server" +msgstr "" + +#. Tag: entry +#: random-bits.xml:262 +#, no-c-format +msgid "&task-web-inst;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:263 +#, no-c-format +msgid "&task-web-dl;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:264 +#, no-c-format +msgid "&task-web-tot;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:268 +#, no-c-format +msgid "SSH server" +msgstr "" + +#. Tag: entry +#: random-bits.xml:269 +#, no-c-format +msgid "&task-ssh-inst;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:270 +#, no-c-format +msgid "&task-ssh-dl;" +msgstr "" + +#. Tag: entry +#: random-bits.xml:271 +#, no-c-format +msgid "&task-ssh-tot;" +msgstr "" + +#. Tag: para +#: random-bits.xml:277 +#, 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 350MB in total for download and installation." +msgstr "" + +#. Tag: title +#: random-bits.xml:292 +#, no-c-format +msgid "Installing &debian-gnu; from a Unix/Linux System" +msgstr "" + +#. Tag: para +#: random-bits.xml:294 +#, no-c-format +msgid "" +"This section explains how to install &debian-gnu; 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-gnu; from Red Hat, Mandriva, 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:306 +#, 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-gnu; 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: para +#: random-bits.xml:317 +#, no-c-format +msgid "" +"As this is a mostly manual procedure, you should bear in mind that you will " +"need to do a lot of basic configuration of the system yourself, which will " +"also require more knowledge of &debian; and of &arch-kernel; in general than " +"performing a regular installation. You cannot expect this procedure to " +"result in a system that is identical to a system from a regular " +"installation. You should also keep in mind that this procedure only gives " +"the basic steps to set up a system. Additional installation and/or " +"configuration steps may be needed." +msgstr "" + +#. Tag: title +#: random-bits.xml:331 +#, no-c-format +msgid "Getting Started" +msgstr "" + +#. Tag: para +#: random-bits.xml:332 +#, 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 &base-" +"system-size;MB of space available for a console only install, or about &task-" +"desktop-lxde-inst;MB if you plan to install X (more if you intend to install " +"desktop environments like GNOME or KDE Plasma)." +msgstr "" + +#. Tag: para +#: random-bits.xml:340 +#, no-c-format +msgid "" +"Next, create file systems on the partitions. For example, to create an ext3 " +"file system on partition <filename>/dev/sda6</filename> (that's our example " +"root partition): <informalexample><screen>\n" +"# mke2fs -j /dev/<replaceable>sda6</replaceable>\n" +"</screen></informalexample> To create an ext2 file system instead, omit " +"<userinput>-j</userinput>." +msgstr "" + +#. Tag: para +#: random-bits.xml:350 +#, no-c-format +msgid "" +"Initialize and activate swap (substitute the partition number for your " +"intended &debian; swap partition): <informalexample><screen>\n" +"# mkswap /dev/<replaceable>sda5</replaceable>\n" +"# sync\n" +"# swapon /dev/<replaceable>sda5</replaceable>\n" +"</screen></informalexample> Mount one partition as <filename>/mnt/debinst</" +"filename> (the installation point, to be the root (<filename>/</filename>) " +"filesystem on your new system). The mount point name is strictly arbitrary, " +"it is referenced later below." +msgstr "" + +#. Tag: screen +#: random-bits.xml:362 +#, no-c-format +msgid "" +"# mkdir /mnt/debinst\n" +"# mount /dev/<replaceable>sda6</replaceable> /mnt/debinst" +msgstr "" + +#. Tag: para +#: random-bits.xml:365 +#, 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 +#, no-c-format +msgid "Install <command>debootstrap</command>" +msgstr "" + +#. Tag: para +#: random-bits.xml:376 +#, 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 +#, 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" +"# mkdir work\n" +"# cd work\n" +"</screen></informalexample> The <command>debootstrap</command> binary is " +"located in the &debian; archive (be sure to select the proper file for your " +"architecture). Download the <command>debootstrap</command> .deb from the " +"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</" +"ulink>, copy the package to the work folder, and extract the files from it. " +"You will need to have root privileges to install the files." +msgstr "" + +#. Tag: screen +#: random-bits.xml:421 +#, no-c-format +msgid "" +"# ar -x debootstrap_0.X.X_all.deb\n" +"# cd /\n" +"# zcat /full-path-to-work/work/data.tar.gz | tar xv" +msgstr "" + +#. Tag: title +#: random-bits.xml:427 +#, no-c-format +msgid "Run <command>debootstrap</command>" +msgstr "" + +#. Tag: para +#: random-bits.xml:428 +#, 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>&archive-mirror;/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/mirror/list\"></ulink>." +msgstr "" + +#. Tag: para +#: random-bits.xml:437 +#, no-c-format +msgid "" +"If you have a &releasename; &debian-gnu; installation image 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 +#, no-c-format +msgid "" +"Substitute one of the following for <replaceable>ARCH</replaceable> in the " +"<command>debootstrap</command> command: <userinput>amd64</userinput>, " +"<userinput>arm64</userinput>, <userinput>armel</userinput>, " +"<userinput>armhf</userinput>, <userinput>i386</userinput>, <userinput>mips</" +"userinput>, <userinput>mips64el</userinput>, <userinput>mipsel</userinput>, " +"<userinput>powerpc</userinput>, <userinput>ppc64el</userinput>, or " +"<userinput>s390x</userinput>. <informalexample><screen>\n" +"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" +" /mnt/debinst http://ftp.us.debian.org/debian\n" +"</screen></informalexample> If the target architecture is different than the " +"host, you should add the <userinput>--foreign</userinput> option." +msgstr "" + +#. Tag: title +#: random-bits.xml:469 +#, no-c-format +msgid "Configure The Base System" +msgstr "" + +#. Tag: para +#: random-bits.xml:470 +#, 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" +"# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash\n" +"</screen></informalexample> If the target architecture is different from the " +"host, you will need to first copy qemu-user-static to the new host: " +"<informalexample><screen>\n" +"# cp /usr/bin/qemu-ARCH-static /mnt/debinst/usr/bin\n" +"# LANG=C.UTF-8 chroot /mnt/debinst qemu-ARCH-static /bin/bash\n" +"</screen></informalexample> After chrooting you may need to set the terminal " +"definition to be compatible with the &debian; base system, for example: " +"<informalexample><screen>\n" +"# export TERM=<replaceable>xterm-color</replaceable>\n" +"</screen></informalexample> Depending on the value of TERM, you may have to " +"install the <classname>ncurses-term</classname> package to get support for " +"it." +msgstr "" + +#. Tag: para +#: random-bits.xml:490 +#, no-c-format +msgid "" +"If the target architecture is different from the host, you need to finish " +"the multi-stage boot strap:" +msgstr "" + +#. Tag: screen +#: random-bits.xml:494 +#, no-c-format +msgid "/debootstrap/debootstrap --second-stage" +msgstr "" + +#. Tag: title +#: random-bits.xml:499 +#, no-c-format +msgid "Create device files" +msgstr "" + +#. Tag: para +#: random-bits.xml:500 +#, no-c-format +msgid "" +"At this point <filename>/dev/</filename> only contains very basic device " +"files. For the next steps of the installation additional device files may be " +"needed. There are different ways to go about this and which method you " +"should use depends on the host system you are using for the installation, on " +"whether you intend to use a modular kernel or not, and on whether you intend " +"to use dynamic (e.g. using <classname>udev</classname>) or static device " +"files for the new system." +msgstr "" + +#. Tag: para +#: random-bits.xml:510 +#, no-c-format +msgid "A few of the available options are:" +msgstr "" + +#. Tag: para +#: random-bits.xml:515 +#, no-c-format +msgid "" +"install the makedev package, and create a default set of static device files " +"using (after chrooting)" +msgstr "" + +#. Tag: screen +#: random-bits.xml:519 +#, no-c-format +msgid "" +"# apt install makedev\n" +"# mount none /proc -t proc\n" +"# cd /dev\n" +"# MAKEDEV generic" +msgstr "" + +#. Tag: para +#: random-bits.xml:522 +#, no-c-format +msgid "" +"manually create only specific device files using <command>MAKEDEV</command>" +msgstr "" + +#. Tag: para +#: random-bits.xml:527 +#, no-c-format +msgid "" +"bind mount /dev from your host system on top of /dev in the target system; " +"note that the postinst scripts of some packages may try to create device " +"files, so this option should only be used with care" +msgstr "" + +#. Tag: title +#: random-bits.xml:540 +#, no-c-format +msgid "Mount Partitions" +msgstr "" + +#. Tag: para +#: random-bits.xml:541 +#, no-c-format +msgid "" +"You need to create <filename>/etc/fstab</filename>. " +"<informalexample><screen>\n" +"# editor /etc/fstab\n" +"</screen></informalexample> Here is a sample you can modify to suit: " +"<informalexample><screen>\n" +"# /etc/fstab: static file system information.\n" +"#\n" +"# file system mount point type options dump pass\n" +"/dev/XXX / ext3 defaults 0 1\n" +"/dev/XXX /boot ext3 ro,nosuid,nodev 0 2\n" +"\n" +"/dev/XXX none swap sw 0 0\n" +"proc /proc proc defaults 0 0\n" +"\n" +"/dev/cdrom /media/cdrom iso9660 noauto,ro,user,exec 0 0\n" +"\n" +"/dev/XXX /tmp ext3 rw,nosuid,nodev 0 2\n" +"/dev/XXX /var ext3 rw,nosuid,nodev 0 2\n" +"/dev/XXX /usr ext3 rw,nodev 0 2\n" +"/dev/XXX /home ext3 rw,nosuid,nodev 0 2\n" +"</screen></informalexample> Use <userinput>mount -a</userinput> to mount all " +"the file systems you have specified in your <filename>/etc/fstab</filename>, " +"or, to mount file systems individually, use: <informalexample><screen>\n" +"# mount /path # e.g.: mount /usr\n" +"</screen></informalexample> Current &debian; systems have mountpoints for " +"removable media under <filename>/media</filename>, but keep compatibility " +"symlinks in <filename>/</filename>. Create these as as needed, for example: " +"<informalexample><screen>\n" +"# cd /media\n" +"# mkdir cdrom0\n" +"# ln -s cdrom0 cdrom\n" +"# cd /\n" +"# ln -s media/cdrom\n" +"</screen></informalexample> You can mount the proc file system multiple " +"times and to arbitrary locations, though <filename>/proc</filename> is " +"customary. If you didn't use <userinput>mount -a</userinput>, be sure to " +"mount proc before continuing:" +msgstr "" + +#. Tag: screen +#: random-bits.xml:567 +#, no-c-format +msgid "# mount -t proc proc /proc" +msgstr "" + +#. Tag: para +#: random-bits.xml:569 +#, 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:575 +#, no-c-format +msgid "# mount -t proc proc /mnt/debinst/proc" +msgstr "" + +#. Tag: title +#: random-bits.xml:581 +#, no-c-format +msgid "Setting Timezone" +msgstr "" + +#. Tag: para +#: random-bits.xml:582 +#, no-c-format +msgid "" +"Setting the third line of the file <filename>/etc/adjtime</filename> to " +"<quote>UTC</quote> or <quote>LOCAL</quote> determines whether the system " +"will interpret the hardware clock as being set to UTC respective local time. " +"The following command allows you to set that. <informalexample><screen>\n" +"# editor /etc/adjtime\n" +"</screen></informalexample> Here is a sample: <informalexample><screen>\n" +"0.0 0 0.0\n" +"0\n" +"UTC\n" +"</screen></informalexample> The following command allows you to choose your " +"timezone." +msgstr "" + +#. Tag: screen +#: random-bits.xml:596 +#, no-c-format +msgid "# dpkg-reconfigure tzdata" +msgstr "" + +#. Tag: title +#: random-bits.xml:602 +#, no-c-format +msgid "Configure Networking" +msgstr "" + +#. Tag: para +#: random-bits.xml:603 +#, 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" +"# editor /etc/network/interfaces\n" +"</screen></informalexample> Here are some simple examples from <filename>/" +"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n" +"######################################################################\n" +"# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n" +"# See the interfaces(5) manpage for information on what options are\n" +"# available.\n" +"######################################################################\n" +"\n" +"# The loopback interface isn't really required any longer, but can be used\n" +"# if needed.\n" +"#\n" +"# auto lo\n" +"# iface lo inet loopback\n" +"\n" +"# To use dhcp:\n" +"#\n" +"# auto eth0\n" +"# iface eth0 inet dhcp\n" +"\n" +"# An example static IP setup: (network, broadcast and gateway are optional)\n" +"#\n" +"# auto eth0\n" +"# iface eth0 inet static\n" +"# address 192.168.0.42\n" +"# network 192.168.0.0\n" +"# netmask 255.255.255.0\n" +"# broadcast 192.168.0.255\n" +"# gateway 192.168.0.1\n" +"</screen></informalexample> Enter your nameserver(s) and search directives " +"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n" +"# editor /etc/resolv.conf\n" +"</screen></informalexample> A simple example <filename>/etc/resolv.conf</" +"filename>: <informalexample><screen>\n" +"search example.com\n" +"nameserver 10.1.1.36\n" +"nameserver 192.168.9.100\n" +"</screen></informalexample> Enter your system's host name (2 to 63 " +"characters): <informalexample><screen>\n" +"# echo DebianHostName > /etc/hostname\n" +"</screen></informalexample> And a basic <filename>/etc/hosts</filename> with " +"IPv6 support: <informalexample><screen>\n" +"127.0.0.1 localhost\n" +"127.0.1.1 DebianHostName\n" +"\n" +"# The following lines are desirable for IPv6 capable hosts\n" +"::1 ip6-localhost ip6-loopback\n" +"fe00::0 ip6-localnet\n" +"ff00::0 ip6-mcastprefix\n" +"ff02::1 ip6-allnodes\n" +"ff02::2 ip6-allrouters\n" +"ff02::3 ip6-allhosts\n" +"</screen></informalexample> If you have multiple network cards, you should " +"arrange the names of driver modules in the <filename>/etc/modules</filename> " +"file into the desired order. Then during boot, each card will be associated " +"with the interface name (eth0, eth1, etc.) that you expect." +msgstr "" + +#. Tag: title +#: random-bits.xml:644 +#, no-c-format +msgid "Configure Apt" +msgstr "" + +#. Tag: para +#: random-bits.xml:645 +#, 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" +"deb-src http://ftp.us.debian.org/debian &releasename; main\n" +"\n" +"deb http://security.debian.org/ &releasename;-security main\n" +"deb-src http://security.debian.org/ &releasename;-security main\n" +"</screen></informalexample> Make sure to run <userinput>apt update</" +"userinput> after you have made changes to the sources list." +msgstr "" + +#. Tag: title +#: random-bits.xml:661 +#, no-c-format +msgid "Configure Locales and Keyboard" +msgstr "" + +#. Tag: para +#: random-bits.xml:662 +#, 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" +"# apt install locales\n" +"# dpkg-reconfigure locales\n" +"</screen></informalexample> To configure your keyboard (if needed):" +msgstr "" + +#. Tag: screen +#: random-bits.xml:672 +#, no-c-format +msgid "" +"# apt install console-setup\n" +"# dpkg-reconfigure keyboard-configuration" +msgstr "" + +#. Tag: para +#: random-bits.xml:674 +#, 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:684 +#, no-c-format +msgid "Install a Kernel" +msgstr "" + +#. Tag: para +#: random-bits.xml:685 +#, no-c-format +msgid "" +"If you intend to boot this system, you probably want a &arch-kernel; kernel " +"and a boot loader. Identify available pre-packaged kernels with:" +msgstr "" + +#. Tag: screen +#: random-bits.xml:690 +#, no-c-format +msgid "# apt search &kernelpackage;" +msgstr "" + +#. Tag: para +#: random-bits.xml:692 +#, no-c-format +msgid "Then install the kernel package of your choice using its package name." +msgstr "" + +#. Tag: screen +#: random-bits.xml:696 +#, no-c-format +msgid "# apt install &kernelpackage;-<replaceable>arch-etc</replaceable>" +msgstr "" + +#. Tag: title +#: random-bits.xml:702 +#, no-c-format +msgid "Set up the Boot Loader" +msgstr "" + +#. Tag: para +#: random-bits.xml:703 +#, no-c-format +msgid "" +"To make your &debian-gnu; 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, but you can " +"use <command>apt</command> inside your &debian; chroot to do so." +msgstr "" + +#. Tag: para +#: random-bits.xml:710 +#, no-c-format +msgid "" +"Check <userinput>info grub</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 grub2 <filename>grub." +"cfg</filename>." +msgstr "" + +#. Tag: para +#: random-bits.xml:718 +#, no-c-format +msgid "" +"Installing and setting up <classname>grub2</classname> is as easy as: " +"<informalexample><screen>\n" +"# apt install grub-pc\n" +"# grub-install /dev/<replaceable>sda</replaceable>\n" +"# update-grub\n" +"</screen></informalexample> The second command will install <command>grub2</" +"command> (in this case in the MBR of <literal>sda</literal>). The last " +"command will create a sane and working <filename>/boot/grub/grub.cfg</" +"filename>." +msgstr "" + +#. Tag: para +#: random-bits.xml:728 +#, no-c-format +msgid "" +"Note that this assumes that a <filename>/dev/sda</filename> device file has " +"been created. There are alternative methods to install <command>grub2</" +"command>, but those are outside the scope of this appendix." +msgstr "" + +#. Tag: para +#: random-bits.xml:734 +#, 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:744 +#, no-c-format +msgid "" +"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: " +"<informalexample><screen>\n" +"boot=/dev/sda2\n" +"device=hd:\n" +"partition=6\n" +"root=/dev/sda6\n" +"magicboot=/usr/lib/yaboot/ofboot\n" +"timeout=50\n" +"image=/vmlinux\n" +"label=Debian\n" +"</screen></informalexample> On some machines, you may need to use " +"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>." +msgstr "" + +#. Tag: title +#: random-bits.xml:757 +#, no-c-format +msgid "Remote access: Installing SSH and setting up access" +msgstr "" + +#. Tag: para +#: random-bits.xml:758 +#, no-c-format +msgid "" +"In case you can login to the system via console, you can skip this section. " +"If the system should be accessible via the network later on, you need to " +"install SSH and set up access. <informalexample><screen>\n" +"# apt install ssh\n" +"</screen></informalexample> Root login with password is disabled by default, " +"so setting up access can be done by setting a password and re-enable root " +"login with password: <informalexample><screen>\n" +"# passwd\n" +"# editor /etc/ssh/sshd_config\n" +"</screen></informalexample> This is the option to be enabled: " +"<informalexample><screen>\n" +"PermitRootLogin yes\n" +"</screen></informalexample> Access can also be set up by adding an ssh key " +"to the root account: <informalexample><screen>\n" +"# mkdir /root/.ssh\n" +"# cat << EOF > /root/.ssh/authorized_keys\n" +"ssh-rsa ....\n" +"EOF\n" +"</screen></informalexample> Lastly, access can be set up by adding a non-" +"root user and setting a password:" +msgstr "" + +#. Tag: screen +#: random-bits.xml:782 +#, no-c-format +msgid "" +"# adduser joe\n" +"# passwd joe" +msgstr "" + +#. Tag: title +#: random-bits.xml:787 +#, no-c-format +msgid "Finishing touches" +msgstr "" + +#. Tag: para +#: random-bits.xml:788 +#, 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" +"# tasksel install standard\n" +"</screen></informalexample> Of course, you can also just use <command>apt</" +"command> to install packages individually." +msgstr "" + +#. Tag: para +#: random-bits.xml:799 +#, 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:805 +#, no-c-format +msgid "# apt clean" +msgstr "" + +#. Tag: title +#: random-bits.xml:816 +#, no-c-format +msgid "Installing &debian-gnu; over Parallel Line IP (PLIP)" +msgstr "" + +#. Tag: para +#: random-bits.xml:818 +#, no-c-format +msgid "" +"This section explains how to install &debian-gnu; 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:826 +#, 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:834 +#, 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:839 +#, 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:849 +#, no-c-format +msgid "Requirements" +msgstr "" + +#. Tag: para +#: random-bits.xml:852 +#, no-c-format +msgid "" +"A target computer, called <emphasis>target</emphasis>, where &debian; will " +"be installed." +msgstr "" + +#. Tag: para +#: random-bits.xml:858 +#, no-c-format +msgid "System installation media; see <xref linkend=\"installation-media\"/>." +msgstr "" + +#. Tag: para +#: random-bits.xml:863 +#, 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:869 +#, 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:881 +#, no-c-format +msgid "Setting up source" +msgstr "" + +#. Tag: para +#: random-bits.xml:882 +#, 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:887 +#, no-c-format +msgid "" +"#!/bin/sh\n" +"\n" +"# We remove running modules from kernel to avoid conflicts and to\n" +"# reconfigure them manually.\n" +"modprobe -r lp parport_pc\n" +"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</" +"replaceable>\n" +"modprobe plip\n" +"\n" +"# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n" +"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint " +"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n" +"\n" +"# Configure gateway\n" +"modprobe iptable_nat\n" +"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j " +"MASQUERADE\n" +"echo 1 > /proc/sys/net/ipv4/ip_forward" +msgstr "" + +#. Tag: title +#: random-bits.xml:893 +#, no-c-format +msgid "Installing target" +msgstr "" + +#. Tag: para +#: random-bits.xml:894 +#, 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" +"expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc." +"irq=<replaceable>7</replaceable>\n" +"</screen></informalexample> Below are the answers that should be given " +"during various stages of the installation." +msgstr "" + +#. Tag: guimenuitem +#: random-bits.xml:913 +#, no-c-format +msgid "Load installer components from installation media" +msgstr "" + +#. Tag: para +#: random-bits.xml:915 +#, 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:923 +#, no-c-format +msgid "Detect network hardware" +msgstr "" + +#. Tag: para +#: random-bits.xml:928 +#, 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:937 +#, 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:949 +#, no-c-format +msgid "Configure the network" +msgstr "" + +#. Tag: para +#: random-bits.xml:952 +#, no-c-format +msgid "Auto-configure network with DHCP: No" +msgstr "" + +#. Tag: para +#: random-bits.xml:957 +#, no-c-format +msgid "" +"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" +msgstr "" + +#. Tag: para +#: random-bits.xml:962 +#, no-c-format +msgid "" +"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></" +"userinput>" +msgstr "" + +#. Tag: para +#: random-bits.xml:968 +#, no-c-format +msgid "" +"Name server addresses: you can enter the same addresses used on source (see " +"<filename>/etc/resolv.conf</filename>)" +msgstr "" + +#. Tag: title +#: random-bits.xml:987 +#, no-c-format +msgid "Installing &debian-gnu; using PPP over Ethernet (PPPoE)" +msgstr "" + +#. Tag: para +#: random-bits.xml:989 +#, no-c-format +msgid "" +"In some countries PPP over Ethernet (PPPoE) is a common protocol for " +"broadband (ADSL or cable) connections to an Internet Service Provider. " +"Setting up a network connection using PPPoE is not supported by default in " +"the installer, but can be made to work very simply. This section explains " +"how." +msgstr "" + +#. Tag: para +#: random-bits.xml:997 +#, no-c-format +msgid "" +"The PPPoE 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:1002 +#, no-c-format +msgid "" +"To have the option of setting up and using PPPoE during the installation, " +"you will need to install using one of the CD-ROM/DVD images that are " +"available. It is not supported for other installation methods (e.g. netboot)." +msgstr "" + +#. Tag: para +#: random-bits.xml:1009 +#, no-c-format +msgid "" +"Installing over PPPoE is mostly the same as any other installation. The " +"following steps explain the differences." +msgstr "" + +#. Tag: para +#: random-bits.xml:1017 +#, no-c-format +msgid "" +"Boot the installer with the boot parameter <userinput>modules=ppp-udeb</" +"userinput><footnote arch=\"x86\"> <para> See <xref linkend=\"boot-screen\"/> " +"for information on how to add a boot parameter. </para> </footnote>. This " +"will ensure the component responsible for the setup of PPPoE (<classname>ppp-" +"udeb</classname>) will be loaded and run automatically." +msgstr "" + +#. Tag: para +#: random-bits.xml:1032 +#, no-c-format +msgid "" +"Follow the regular initial steps of the installation (language, country and " +"keyboard selection; the loading of additional installer components<footnote> " +"<para> The <classname>ppp-udeb</classname> component is loaded as one of the " +"additional components in this step. If you want to install at medium or low " +"priority (expert mode), you can also manually select the <classname>ppp-" +"udeb</classname> instead of entering the <quote>modules</quote> parameter at " +"the boot prompt. </para> </footnote>)." +msgstr "" + +#. Tag: para +#: random-bits.xml:1051 +#, no-c-format +msgid "" +"The next step is the detection of network hardware, in order to identify any " +"Ethernet cards present in the system." +msgstr "" + +#. Tag: para +#: random-bits.xml:1057 +#, no-c-format +msgid "" +"After this the actual setup of PPPoE is started. The installer will probe " +"all the detected Ethernet interfaces in an attempt to find a PPPoE " +"concentrator (a type of server which handles PPPoE connections)." +msgstr "" + +#. Tag: para +#: random-bits.xml:1063 +#, no-c-format +msgid "" +"It is possible that the concentrator will not to be found at the first " +"attempt. This can happen occasionally on slow or loaded networks or with " +"faulty servers. In most cases a second attempt to detect the concentrator " +"will be successful; to retry, select <guimenuitem>Configure and start a " +"PPPoE connection</guimenuitem> from the main menu of the installer." +msgstr "" + +#. Tag: para +#: random-bits.xml:1072 +#, no-c-format +msgid "" +"After a concentrator is found, the user will be prompted to type the login " +"information (the PPPoE username and password)." +msgstr "" + +#. Tag: para +#: random-bits.xml:1078 +#, no-c-format +msgid "" +"At this point the installer will use the provided information to establish " +"the PPPoE connection. If the correct information was provided, the PPPoE " +"connection should be configured and the installer should be able to use it " +"to connect to the Internet and retrieve packages over it (if needed). If the " +"login information is not correct or some error appears, the installer will " +"stop, but the configuration can be attempted again by selecting the menu " +"entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>." +msgstr "" diff --git a/po/kab/using-d-i.po b/po/kab/using-d-i.po new file mode 100644 index 000000000..30c3fbba4 --- /dev/null +++ b/po/kab/using-d-i.po @@ -0,0 +1,4193 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-using-d-i 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-12-11 21:39+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: using-d-i.xml:5 +#, no-c-format +msgid "Using the &debian; Installer" +msgstr "" + +#. Tag: title +#: using-d-i.xml:7 +#, no-c-format +msgid "How the Installer Works" +msgstr "" + +#. Tag: para +#: using-d-i.xml:8 +#, no-c-format +msgid "" +"The &debian; Installer consists of a number of special-purpose components to " +"perform each installation task. Each component performs its task, asking the " +"user questions as necessary to do its job. The questions themselves are " +"given priorities, and the priority of questions to be asked is set when the " +"installer is started." +msgstr "" + +#. Tag: para +#: using-d-i.xml:16 +#, no-c-format +msgid "" +"When a default installation is performed, only essential (high priority) " +"questions will be asked. This results in a highly automated installation " +"process with little user interaction. Components are automatically run in " +"sequence; which components are run depends mainly on the installation method " +"you use and on your hardware. The installer will use default values for " +"questions that are not asked." +msgstr "" + +#. Tag: para +#: using-d-i.xml:25 +#, no-c-format +msgid "" +"If there is a problem, the user will see an error screen, and the installer " +"menu may be shown in order to select some alternative action. If there are " +"no problems, the user will never see the installer menu, but will simply " +"answer questions for each component in turn. Serious error notifications are " +"set to priority <quote>critical</quote> so the user will always be notified." +msgstr "" + +#. Tag: para +#: using-d-i.xml:34 +#, no-c-format +msgid "" +"Some of the defaults that the installer uses can be influenced by passing " +"boot arguments when &d-i; is started. If, for example, you wish to force " +"static network configuration (IPv6 autoconfiguration and DHCP are used by " +"default if available), you could add the boot parameter <userinput>netcfg/" +"disable_autoconfig=true</userinput>. See <xref linkend=\"installer-args\"/> " +"for available options." +msgstr "" + +#. Tag: para +#: using-d-i.xml:43 +#, no-c-format +msgid "" +"Power users may be more comfortable with a menu-driven interface, where each " +"step is controlled by the user rather than the installer performing each " +"step automatically in sequence. To use the installer in a manual, menu-" +"driven way, add the boot argument <userinput>priority=medium</userinput>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:51 +#, no-c-format +msgid "" +"If your hardware requires you to pass options to kernel modules as they are " +"installed, you will need to start the installer in <quote>expert</quote> " +"mode. This can be done by either using the <command>expert</command> command " +"to start the installer or by adding the boot argument " +"<userinput>priority=low</userinput>. Expert mode gives you full control over " +"&d-i;." +msgstr "" + +#. Tag: para +#: using-d-i.xml:60 +#, no-c-format +msgid "" +"For this architecture the &d-i; supports two different user interfaces: a " +"graphical one and a character-based one. The graphical interface is used by " +"default unless you select an <quote>Install</quote> option in the boot menu. " +"For more information about the graphical installer, please refer to <xref " +"linkend=\"graphical\"/>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:68 +#, no-c-format +msgid "" +"For this architecture the &d-i; supports two different user interfaces: a " +"text-based one and a graphical one. The text-based interface is used by " +"default unless you select an <quote>Graphical install</quote> option in the " +"boot menu. For more information about the graphical installer, please refer " +"to <xref linkend=\"graphical\"/>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:76 +#, no-c-format +msgid "" +"For this architecture the &d-i; supports two different user interfaces: a " +"character-based one and a graphical one. The character-based interface is " +"used by default unless you select the <quote>Graphical install</quote> " +"option on purpose. For more information about the graphical installer, " +"please refer to <xref linkend=\"graphical\"/>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:84 +#, no-c-format +msgid "" +"For this architecture the installer uses a character-based user interface. A " +"graphical user interface is currently not available." +msgstr "" + +#. Tag: para +#: using-d-i.xml:89 +#, no-c-format +msgid "" +"In the character-based environment the use of a mouse is not supported. Here " +"are the keys you can use to navigate within the various dialogs. The " +"<keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move " +"<quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> " +"<keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move " +"<quote>backward</quote> between displayed buttons and selections. The " +"<keycap>up</keycap> and <keycap>down</keycap> arrow select different items " +"within a scrollable list, and also scroll the list itself. In addition, in " +"long lists, you can type a letter to cause the list to scroll directly to " +"the section with items starting with the letter you typed and use <keycap>Pg-" +"Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The " +"<keycap>space bar</keycap> selects an item such as a checkbox. Use " +"&enterkey; to activate choices." +msgstr "" + +#. Tag: para +#: using-d-i.xml:106 +#, no-c-format +msgid "" +"Some dialogs may offer additional help information. If help is available " +"this will be indicated on the bottom line of the screen by displaying that " +"help information can be accessed by pressing the <keycap>F1</keycap> key." +msgstr "" + +#. Tag: para +#: using-d-i.xml:112 +#, no-c-format +msgid "" +"S/390 does not support virtual consoles. You may open a second and third ssh " +"session to view the logs described below." +msgstr "" + +#. Tag: para +#: using-d-i.xml:117 +#, no-c-format +msgid "" +"Error messages and logs are redirected to the fourth console. You can access " +"this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</" +"keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing " +"the <keycap>F4</keycap> function key); get back to the main installer " +"process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></" +"keycombo>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:127 +#, no-c-format +msgid "" +"These messages can also be found in <filename>/var/log/syslog</filename>. " +"After installation, this log is copied to <filename>/var/log/installer/" +"syslog</filename> on your new system. Other installation messages may be " +"found in <filename>/var/log/</filename> during the installation, and " +"<filename>/var/log/installer/</filename> after the computer has been booted " +"into the installed system." +msgstr "" + +#. Tag: title +#: using-d-i.xml:140 +#, no-c-format +msgid "Using the graphical installer" +msgstr "" + +#. Tag: para +#: using-d-i.xml:141 +#, no-c-format +msgid "" +"The graphical installer basically works the same as the text-based installer " +"and thus the rest of this manual can be used to guide you through the " +"installation process." +msgstr "" + +#. Tag: para +#: using-d-i.xml:147 +#, no-c-format +msgid "" +"If you prefer using the keyboard over the mouse, there are two things you " +"need to know. To expand a collapsed list (used for example for the selection " +"of countries within continents), you can use the <keycap>+</keycap> and " +"<keycap>-</keycap> keys. For questions where more than one item can be " +"selected (e.g. task selection), you first need to tab to the &BTN-CONT; " +"button after making your selections; hitting enter will toggle a selection, " +"not activate &BTN-CONT;." +msgstr "" + +#. Tag: para +#: using-d-i.xml:157 +#, no-c-format +msgid "" +"If a dialog offers additional help information, a <guibutton>Help</" +"guibutton> button will be displayed. The help information can be accessed " +"either by activating the button or by pressing the <keycap>F1</keycap> key." +msgstr "" + +#. Tag: para +#: using-d-i.xml:163 +#, no-c-format +msgid "" +"To switch to another console, you will also need to use the <keycap>Ctrl</" +"keycap> key, just as with the X Window System. For example, to switch to VT2 " +"(the first debug shell) you would use: <keycombo> <keycap>Ctrl</keycap> " +"<keycap>Left Alt</keycap> <keycap>F2</keycap> </keycombo>. The graphical " +"installer itself runs on VT5, so you can use <keycombo> <keycap>Left Alt</" +"keycap> <keycap>F5</keycap> </keycombo> to switch back." +msgstr "" + +#. Tag: title +#: using-d-i.xml:177 +#, no-c-format +msgid "Components Introduction" +msgstr "" + +#. Tag: para +#: using-d-i.xml:178 +#, no-c-format +msgid "" +"Here is a list of installer components with a brief description of each " +"component's purpose. Details you might need to know about using a particular " +"component are in <xref linkend=\"module-details\"/>." +msgstr "" + +#. Tag: term +#: using-d-i.xml:189 +#, no-c-format +msgid "main-menu" +msgstr "" + +#. Tag: para +#: using-d-i.xml:189 +#, no-c-format +msgid "" +"Shows the list of components to the user during installer operation, and " +"starts a component when it is selected. Main-menu's questions are set to " +"priority medium, so if your priority is set to high or critical (high is the " +"default), you will not see the menu. On the other hand, if there is an error " +"which requires your intervention, the question priority may be downgraded " +"temporarily to allow you to resolve the problem, and in that case the menu " +"may appear." +msgstr "" + +#. Tag: para +#: using-d-i.xml:199 +#, no-c-format +msgid "" +"You can get to the main menu by selecting the &BTN-GOBACK; button repeatedly " +"to back all the way out of the currently running component." +msgstr "" + +#. Tag: term +#: using-d-i.xml:208 +#, no-c-format +msgid "localechooser" +msgstr "" + +#. Tag: para +#: using-d-i.xml:208 +#, no-c-format +msgid "" +"Allows the user to select localization options for the installation and the " +"installed system: language, country and locales. The installer will display " +"messages in the selected language, unless the translation for that language " +"is not complete in which case some messages may be shown in English." +msgstr "" + +#. Tag: term +#: using-d-i.xml:220 +#, no-c-format +msgid "console-setup" +msgstr "" + +#. Tag: para +#: using-d-i.xml:220 +#, no-c-format +msgid "" +"Shows a list of keyboard (layouts), from which the user chooses the one " +"which matches his own model." +msgstr "" + +#. Tag: term +#: using-d-i.xml:229 +#, no-c-format +msgid "hw-detect" +msgstr "" + +#. Tag: para +#: using-d-i.xml:229 +#, no-c-format +msgid "" +"Automatically detects most of the system's hardware, including network " +"cards, disk drives, and PCMCIA." +msgstr "" + +#. Tag: term +#: using-d-i.xml:238 +#, no-c-format +msgid "cdrom-detect" +msgstr "" + +#. Tag: para +#: using-d-i.xml:238 +#, no-c-format +msgid "Looks for and mounts a &debian; installation media." +msgstr "" + +#. Tag: term +#: using-d-i.xml:246 +#, no-c-format +msgid "netcfg" +msgstr "" + +#. Tag: para +#: using-d-i.xml:246 +#, no-c-format +msgid "" +"Configures the computer's network connections so it can communicate over the " +"internet." +msgstr "" + +#. Tag: term +#: using-d-i.xml:255 +#, no-c-format +msgid "iso-scan" +msgstr "" + +#. Tag: para +#: using-d-i.xml:255 +#, no-c-format +msgid "" +"Searches for ISO images (<filename>.iso</filename> files) on hard drives." +msgstr "" + +#. Tag: term +#: using-d-i.xml:263 +#, no-c-format +msgid "choose-mirror" +msgstr "" + +#. Tag: para +#: using-d-i.xml:263 +#, no-c-format +msgid "" +"Presents a list of &debian; archive mirrors. The user may choose the source " +"of his installation packages." +msgstr "" + +#. Tag: term +#: using-d-i.xml:272 +#, no-c-format +msgid "cdrom-checker" +msgstr "" + +#. Tag: para +#: using-d-i.xml:272 +#, no-c-format +msgid "" +"Checks integrity of installation media. This way, the user may assure him/" +"herself that the installation image was not corrupted." +msgstr "" + +#. Tag: term +#: using-d-i.xml:281 +#, no-c-format +msgid "lowmem" +msgstr "" + +#. Tag: para +#: using-d-i.xml:281 +#, no-c-format +msgid "" +"Lowmem tries to detect systems with low memory and then does various tricks " +"to remove unnecessary parts of &d-i; from the memory (at the cost of some " +"features)." +msgstr "" + +#. Tag: term +#: using-d-i.xml:291 +#, no-c-format +msgid "anna" +msgstr "" + +#. Tag: para +#: using-d-i.xml:291 +#, no-c-format +msgid "" +"Anna's Not Nearly APT. Installs packages which have been retrieved from the " +"chosen mirror or installation media." +msgstr "" + +#. Tag: term +#: using-d-i.xml:300 +#, no-c-format +msgid "user-setup" +msgstr "" + +#. Tag: para +#: using-d-i.xml:300 +#, no-c-format +msgid "Sets up the root password, and adds a non-root user." +msgstr "" + +#. Tag: term +#: using-d-i.xml:308 +#, no-c-format +msgid "clock-setup" +msgstr "" + +#. Tag: para +#: using-d-i.xml:308 +#, no-c-format +msgid "" +"Updates the system clock and determines whether the clock is set to UTC or " +"not." +msgstr "" + +#. Tag: term +#: using-d-i.xml:317 +#, no-c-format +msgid "tzsetup" +msgstr "" + +#. Tag: para +#: using-d-i.xml:317 +#, no-c-format +msgid "Selects the time zone, based on the location selected earlier." +msgstr "" + +#. Tag: term +#: using-d-i.xml:325 +#, no-c-format +msgid "partman" +msgstr "" + +#. Tag: para +#: using-d-i.xml:325 +#, no-c-format +msgid "" +"Allows the user to partition disks attached to the system, create file " +"systems on the selected partitions, and attach them to the mountpoints. " +"Included are also interesting features like a fully automatic mode or LVM " +"support. This is the preferred partitioning tool in &debian;." +msgstr "" + +#. Tag: term +#: using-d-i.xml:337 +#, no-c-format +msgid "partitioner" +msgstr "" + +#. Tag: para +#: using-d-i.xml:337 +#, no-c-format +msgid "" +"Allows the user to partition disks attached to the system. A partitioning " +"program appropriate to your computer's architecture is chosen." +msgstr "" + +#. Tag: term +#: using-d-i.xml:347 +#, no-c-format +msgid "partconf" +msgstr "" + +#. Tag: para +#: using-d-i.xml:347 +#, no-c-format +msgid "" +"Displays a list of partitions, and creates file systems on the selected " +"partitions according to user instructions." +msgstr "" + +#. Tag: term +#: using-d-i.xml:356 +#, no-c-format +msgid "partman-lvm" +msgstr "" + +#. Tag: para +#: using-d-i.xml:356 +#, no-c-format +msgid "" +"Helps the user with the configuration of the <firstterm>LVM</firstterm> " +"(Logical Volume Manager)." +msgstr "" + +#. Tag: term +#: using-d-i.xml:365 +#, no-c-format +msgid "partman-md" +msgstr "" + +#. Tag: para +#: using-d-i.xml:365 +#, no-c-format +msgid "" +"Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant " +"Array of Inexpensive Disks). This Software RAID is usually superior to the " +"cheap IDE (pseudo hardware) RAID controllers found on newer motherboards." +msgstr "" + +#. Tag: term +#: using-d-i.xml:376 +#, no-c-format +msgid "base-installer" +msgstr "" + +#. Tag: para +#: using-d-i.xml:376 +#, no-c-format +msgid "" +"Installs the most basic set of packages which would allow the computer to " +"operate under &debian-gnu; when rebooted." +msgstr "" + +#. Tag: term +#: using-d-i.xml:385 +#, no-c-format +msgid "apt-setup" +msgstr "" + +#. Tag: para +#: using-d-i.xml:385 +#, no-c-format +msgid "" +"Configures apt, mostly automatically, based on what media the installer is " +"running from." +msgstr "" + +#. Tag: term +#: using-d-i.xml:394 +#, no-c-format +msgid "pkgsel" +msgstr "" + +#. Tag: para +#: using-d-i.xml:394 +#, no-c-format +msgid "" +"Uses <classname>tasksel</classname> to select and install additional " +"software." +msgstr "" + +#. Tag: term +#: using-d-i.xml:402 +#, no-c-format +msgid "os-prober" +msgstr "" + +#. Tag: para +#: using-d-i.xml:402 +#, no-c-format +msgid "" +"Detects currently installed operating systems on the computer and passes " +"this information to the bootloader-installer, which may offer you an ability " +"to add discovered operating systems to the bootloader's start menu. This way " +"the user could easily choose at the boot time which operating system to " +"start." +msgstr "" + +#. Tag: term +#: using-d-i.xml:414 +#, no-c-format +msgid "bootloader-installer" +msgstr "" + +#. Tag: para +#: using-d-i.xml:414 +#, no-c-format +msgid "" +"The various bootloader installers each install a boot loader program on the " +"hard disk, which is necessary for the computer to start up using &arch-" +"kernel; without using a USB stick or CD-ROM. Many boot loaders allow the " +"user to choose an alternate operating system each time the computer boots." +msgstr "" + +#. Tag: term +#: using-d-i.xml:425 +#, no-c-format +msgid "shell" +msgstr "" + +#. Tag: para +#: using-d-i.xml:425 +#, no-c-format +msgid "" +"Allows the user to execute a shell from the menu, or in the second console." +msgstr "" + +#. Tag: term +#: using-d-i.xml:434 +#, no-c-format +msgid "save-logs" +msgstr "" + +#. Tag: para +#: using-d-i.xml:434 +#, no-c-format +msgid "" +"Provides a way for the user to record information on a USB stick, network, " +"hard disk, or other media when trouble is encountered, in order to " +"accurately report installer software problems to &debian; developers later." +msgstr "" + +#. Tag: title +#: using-d-i.xml:452 +#, no-c-format +msgid "Using Individual Components" +msgstr "" + +#. Tag: para +#: using-d-i.xml:453 +#, no-c-format +msgid "" +"In this section we will describe each installer component in detail. The " +"components have been grouped into stages that should be recognizable for " +"users. They are presented in the order they appear during the install. Note " +"that not all modules will be used for every installation; which modules are " +"actually used depends on the installation method you use and on your " +"hardware." +msgstr "" + +#. Tag: title +#: using-d-i.xml:465 +#, no-c-format +msgid "Setting up &debian; Installer and Hardware Configuration" +msgstr "" + +#. Tag: para +#: using-d-i.xml:466 +#, no-c-format +msgid "" +"Let's assume the &debian; Installer has booted and you are facing its first " +"screen. At this time, the capabilities of &d-i; are still quite limited. It " +"doesn't know much about your hardware, preferred language, or even the task " +"it should perform. Don't worry. Because &d-i; is quite clever, it can " +"automatically probe your hardware, locate the rest of its components and " +"upgrade itself to a capable installation system. However, you still need to " +"help &d-i; with some information it can't determine automatically (like " +"selecting your preferred language, keyboard layout or desired network " +"mirror)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:479 +#, no-c-format +msgid "" +"You will notice that &d-i; performs <firstterm>hardware detection</" +"firstterm> several times during this stage. The first time is targeted " +"specifically at the hardware needed to load installer components (e.g. your " +"CD-ROM or network card). As not all drivers may be available during this " +"first run, hardware detection needs to be repeated later in the process." +msgstr "" + +#. Tag: para +#: using-d-i.xml:487 +#, no-c-format +msgid "" +"During hardware detection &d-i; checks if any of the drivers for the " +"hardware devices in your system require firmware to be loaded. If any " +"firmware is requested but unavailable, a dialog will be displayed that " +"allows the missing firmware to be loaded from a removable medium. See <xref " +"linkend=\"loading-firmware\"/> for further details." +msgstr "" + +#. Tag: title +#: using-d-i.xml:502 +#, no-c-format +msgid "Check available memory / low memory mode" +msgstr "" + +#. Tag: para +#: using-d-i.xml:504 +#, no-c-format +msgid "" +"One of the first things &d-i; does, is to check available memory. If the " +"available memory is limited, this component will make some changes in the " +"installation process which hopefully will allow you to install &debian-gnu; " +"on your system." +msgstr "" + +#. Tag: para +#: using-d-i.xml:511 +#, no-c-format +msgid "" +"The first measure taken to reduce memory consumption by the installer is to " +"disable translations, which means that the installation can only be done in " +"English. Of course, you can still localize the installed system after the " +"installation has completed." +msgstr "" + +#. Tag: para +#: using-d-i.xml:518 +#, no-c-format +msgid "" +"If that is not sufficient, the installer will further reduce memory " +"consumption by loading only those components essential to complete a basic " +"installation. This reduces the functionality of the installation system. You " +"will be given the opportunity to load additional components manually, but " +"you should be aware that each component you select will use additional " +"memory and thus may cause the installation to fail." +msgstr "" + +#. Tag: para +#: using-d-i.xml:527 +#, no-c-format +msgid "" +"If the installer runs in low memory mode, it is recommended to create a " +"relatively large swap partition (64–128MB). The swap partition will be " +"used as virtual memory and thus increases the amount of memory available to " +"the system. The installer will activate the swap partition as early as " +"possible in the installation process. Note that heavy use of swap will " +"reduce performance of your system and may lead to high disk activity." +msgstr "" + +#. Tag: para +#: using-d-i.xml:537 +#, no-c-format +msgid "" +"Despite these measures, it is still possible that your system freezes, that " +"unexpected errors occur or that processes are killed by the kernel because " +"the system runs out of memory (which will result in <quote>Out of memory</" +"quote> messages on VT4 and in the syslog)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:544 +#, no-c-format +msgid "" +"For example, it has been reported that creating a big ext3 file system fails " +"in low memory mode when there is insufficient swap space. If a larger swap " +"doesn't help, try creating the file system as ext2 (which is an essential " +"component of the installer) instead. It is possible to change an ext2 " +"partition to ext3 after the installation." +msgstr "" + +#. Tag: para +#: using-d-i.xml:552 +#, no-c-format +msgid "" +"It is possible to force the installer to use a higher lowmem level than the " +"one based on available memory by using the boot parameter <quote>lowmem</" +"quote> as described in <xref linkend=\"installer-args\"/>." +msgstr "" + +#. Tag: title +#: using-d-i.xml:567 +#, no-c-format +msgid "Selecting Localization Options" +msgstr "" + +#. Tag: para +#: using-d-i.xml:569 +#, no-c-format +msgid "" +"In most cases the first questions you will be asked concern the selection of " +"localization options to be used both for the installation and for the " +"installed system. The localization options consist of language, location and " +"locales." +msgstr "" + +#. Tag: para +#: using-d-i.xml:576 +#, no-c-format +msgid "" +"The language you choose will be used for the rest of the installation " +"process, provided a translation of the different dialogs is available. If no " +"valid translation is available for the selected language, the installer will " +"default to English." +msgstr "" + +#. Tag: para +#: using-d-i.xml:583 +#, no-c-format +msgid "" +"The selected geographic location (in most cases a country) will be used " +"later in the installation process to select the correct time zone and a " +"&debian; mirror appropriate for that country. Language and country together " +"will help determine the default locale for your system and select the " +"correct keyboard layout." +msgstr "" + +#. Tag: para +#: using-d-i.xml:591 +#, no-c-format +msgid "" +"You will first be asked to select your preferred language. The language " +"names are listed both in English (left side) and in the language itself " +"(right side); the names on the right side are also shown in the proper " +"script for the language. The list is sorted on the English names. At the top " +"of the list is an extra option that allows you to select the <quote>C</" +"quote> locale instead of a language. Choosing the <quote>C</quote> locale " +"will result in the installation proceding in English; the installed system " +"will have no localization support as the <classname>locales</classname> " +"package will not be installed." +msgstr "" + +#. Tag: para +#: using-d-i.xml:603 +#, no-c-format +msgid "" +"Next you will be asked to select your geographic location. If you selected a " +"language that is recognized as an official language for more than one " +"country<footnote> <para> In technical terms: where multiple locales exist " +"for that language with differing country codes. </para> </footnote>, you " +"will be shown a list of only those countries. To select a country that is " +"not in that list, choose <guimenuitem>other</guimenuitem> (the last option). " +"You will then be presented with a list of continents; selecting a continent " +"will lead to a list of relevant countries on that continent." +msgstr "" + +#. Tag: para +#: using-d-i.xml:620 +#, no-c-format +msgid "" +"If the language has only one country associated with it, a list of countries " +"will be displayed for the continent or region the country belongs to, with " +"that country selected as the default. Use the <guibutton>Go Back</guibutton> " +"option to select countries on a different continent." +msgstr "" + +#. Tag: para +#: using-d-i.xml:627 +#, no-c-format +msgid "" +"It is important to select the country where you live or where you are " +"located as it determines the time zone that will be configured for the " +"installed system." +msgstr "" + +#. Tag: para +#: using-d-i.xml:633 +#, no-c-format +msgid "" +"If you selected a combination of language and country for which no locale is " +"defined and there exist multiple locales for the language, then the " +"installer will allow you to choose which of those locales you prefer as the " +"default locale for the installed system<footnote> <para> At medium and low " +"priority you can always select your preferred locale from those available " +"for the selected language (if there's more than one). </para> </footnote>. " +"In all other cases a default locale will be selected based on the selected " +"language and country." +msgstr "" + +#. Tag: para +#: using-d-i.xml:648 +#, no-c-format +msgid "" +"Any default locale selected as described in the previous paragraph will use " +"<firstterm>UTF-8</firstterm> as character encoding." +msgstr "" + +#. Tag: para +#: using-d-i.xml:653 +#, no-c-format +msgid "" +"If you are installing at low priority, you will have the option of selecting " +"additional locales, including so-called <quote>legacy</quote> " +"locales<footnote> <para> Legacy locales are locales which do not use UTF-8, " +"but one of the older standards for character encoding such as " +"ISO 8859-1 (used by West European languages) or EUC-JP (used by " +"Japanese). </para> </footnote>, to be generated for the installed system; if " +"you do, you will be asked which of the selected locales should be the " +"default for the installed system." +msgstr "" + +#. Tag: title +#: using-d-i.xml:677 +#, no-c-format +msgid "Choosing a Keyboard" +msgstr "" + +#. Tag: para +#: using-d-i.xml:679 +#, no-c-format +msgid "" +"Keyboards are often tailored to the characters used in a language. Select a " +"layout that conforms to the keyboard you are using, or select something " +"close if the keyboard layout you want isn't represented. Once the system " +"installation is complete, you'll be able to select a keyboard layout from a " +"wider range of choices (run <command>dpkg-reconfigure keyboard-" +"configuration</command> as root after you have completed the installation)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:689 +#, no-c-format +msgid "" +"Move the highlight to the keyboard selection you desire and press " +"&enterkey;. Use the arrow keys to move the highlight — they are in the " +"same place in all national language keyboard layouts, so they are " +"independent of the keyboard configuration." +msgstr "" + +#. Tag: title +#: using-d-i.xml:716 +#, no-c-format +msgid "Looking for the &debian; Installer ISO Image" +msgstr "" + +#. Tag: para +#: using-d-i.xml:717 +#, no-c-format +msgid "" +"When installing via the <emphasis>hd-media</emphasis> method, there will be " +"a moment where you need to find and mount the &debian; Installer iso image " +"in order to get the rest of the installation files. The component " +"<command>iso-scan</command> does exactly this." +msgstr "" + +#. Tag: para +#: using-d-i.xml:724 +#, no-c-format +msgid "" +"At first, <command>iso-scan</command> automatically mounts all block devices " +"(e.g. partitions and logical volumes) which have some known filesystem on " +"them and sequentially searches for filenames ending with <filename>.iso</" +"filename> (or <filename>.ISO</filename> for that matter). Beware that the " +"first attempt scans only files in the root directory and in the first level " +"of subdirectories (i.e. it finds <filename>/<replaceable>whatever</" +"replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</" +"replaceable>.iso</filename>, but not <filename>/data/tmp/" +"<replaceable>whatever</replaceable>.iso</filename>). After an iso image has " +"been found, <command>iso-scan</command> checks its content to determine if " +"the image is a valid &debian; iso image or not. In the former case we are " +"done, in the latter <command>iso-scan</command> seeks for another image." +msgstr "" + +#. Tag: para +#: using-d-i.xml:741 +#, no-c-format +msgid "" +"In case the previous attempt to find an installer iso image fails, " +"<command>iso-scan</command> will ask you whether you would like to perform a " +"more thorough search. This pass doesn't just look into the topmost " +"directories, but really traverses whole filesystem." +msgstr "" + +#. Tag: para +#: using-d-i.xml:748 +#, no-c-format +msgid "" +"If <command>iso-scan</command> does not discover your installer iso image, " +"reboot back to your original operating system and check if the image is " +"named correctly (ending in <filename>.iso</filename>), if it is placed on a " +"filesystem recognizable by &d-i;, and if it is not corrupted (verify the " +"checksum). Experienced Unix users could do this without rebooting on the " +"second console." +msgstr "" + +#. Tag: para +#: using-d-i.xml:757 +#, no-c-format +msgid "" +"Note that the partition (or disk) hosting the ISO image can't be reused " +"during the installation process as it will be in use by the installer. To " +"work-around this, and provided that you have enough system memory, the " +"installer can copy the ISO image into RAM before mounting it. This is " +"controlled by the low priority <literal>iso-scan/copy_iso_to_ram</literal> " +"debconf question (it is only asked if the memory requirement is met)." +msgstr "" + +#. Tag: title +#: using-d-i.xml:778 +#, no-c-format +msgid "Configuring the Network" +msgstr "" + +#. Tag: para +#: using-d-i.xml:780 +#, no-c-format +msgid "" +"As you enter this step, if the system detects that you have more than one " +"network device, you'll be asked to choose which device will be your " +"<emphasis>primary</emphasis> network interface, i.e. the one which you want " +"to use for installation. The other interfaces won't be configured at this " +"time. You may configure additional interfaces after installation is " +"complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> " +"<manvolnum>5</manvolnum> </citerefentry> man page." +msgstr "" + +#. Tag: title +#: using-d-i.xml:794 +#, no-c-format +msgid "Automatic network configuration" +msgstr "" + +#. Tag: para +#: using-d-i.xml:795 +#, no-c-format +msgid "" +"By default, &d-i; tries to configure your computer's network automatically " +"as far as possible. If the automatic configuration fails, that may be caused " +"by many factors ranging from an unplugged network cable to missing " +"infrastructure for automatic configuration. For further explanation in case " +"of errors, check the error messages on the fourth console. In any case, you " +"will be asked if you want to retry, or if you want to perform a manual " +"setup. Sometimes the network services used for autoconfiguration can be slow " +"in their responses, so if you are sure everything is in place, simply start " +"the autoconfiguration attempt again. If autoconfiguration fails repeatedly, " +"you can instead choose the manual network setup." +msgstr "" + +#. Tag: title +#: using-d-i.xml:814 +#, no-c-format +msgid "Manual network configuration" +msgstr "" + +#. Tag: para +#: using-d-i.xml:815 +#, no-c-format +msgid "" +"The manual network setup in turn asks you a number of questions about your " +"network, notably <computeroutput>IP address</computeroutput>, " +"<computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</" +"computeroutput>, <computeroutput>Name server addresses</computeroutput>, and " +"a <computeroutput>Hostname</computeroutput>. Moreover, if you have a " +"wireless network interface, you will be asked to provide your " +"<computeroutput>Wireless ESSID</computeroutput> (<quote>wireless network " +"name</quote>) and a <computeroutput>WEP key</computeroutput> or " +"<computeroutput>WPA/WPA2 passphrase</computeroutput>. Fill in the answers " +"from <xref linkend=\"needed-info\"/>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:831 +#, no-c-format +msgid "" +"Some technical details you might, or might not, find handy: the program " +"assumes the network IP address is the bitwise-AND of your system's IP " +"address and your netmask. The default broadcast address is calculated as the " +"bitwise OR of your system's IP address with the bitwise negation of the " +"netmask. It will also guess your gateway. If you can't find any of these " +"answers, use the offered defaults — if necessary, you can change them " +"by editing <filename>/etc/network/interfaces</filename> once the system has " +"been installed." +msgstr "" + +#. Tag: title +#: using-d-i.xml:846 +#, no-c-format +msgid "IPv4 and IPv6" +msgstr "" + +#. Tag: para +#: using-d-i.xml:847 +#, no-c-format +msgid "" +"From &debian-gnu; 7.0 (<quote>Wheezy</quote>) onwards, &d-i; supports IPv6 " +"as well as the <quote>classic</quote> IPv4. All combinations of IPv4 and " +"IPv6 (IPv4-only, IPv6-only and dual-stack configurations) are supported." +msgstr "" + +#. Tag: para +#: using-d-i.xml:853 +#, no-c-format +msgid "" +"Autoconfiguration for IPv4 is done via DHCP (Dynamic Host Configuration " +"Protocol). Autoconfiguration for IPv6 supports stateless autoconfiguration " +"using NDP (Neighbor Discovery Protocol, including recursive DNS server " +"(RDNSS) assignment), stateful autoconfiguration via DHCPv6 and mixed " +"stateless/stateful autoconfiguration (address configuration via NDP, " +"additional parameters via DHCPv6)." +msgstr "" + +#. Tag: title +#: using-d-i.xml:897 +#, no-c-format +msgid "Setting Up Users And Passwords" +msgstr "" + +#. Tag: para +#: using-d-i.xml:898 +#, no-c-format +msgid "" +"Just before configuring the clock, the installer will allow you to set up " +"the <quote>root</quote> account and/or an account for the first user. Other " +"user accounts can be created after the installation has been completed." +msgstr "" + +#. Tag: title +#: using-d-i.xml:912 +#, no-c-format +msgid "Set the Root Password" +msgstr "" + +#. Tag: para +#: using-d-i.xml:914 +#, no-c-format +msgid "" +"The <emphasis>root</emphasis> account is also called the <emphasis>super-" +"user</emphasis>; it is a login that bypasses all security protection on your " +"system. The root account should only be used to perform system " +"administration, and only used for as short a time as possible." +msgstr "" + +#. Tag: para +#: using-d-i.xml:922 +#, no-c-format +msgid "" +"Any password you create should contain at least 6 characters, and should " +"contain both upper- and lower-case characters, as well as punctuation " +"characters. Take extra care when setting your root password, since it is " +"such a powerful account. Avoid dictionary words or use of any personal " +"information which could be guessed." +msgstr "" + +#. Tag: para +#: using-d-i.xml:930 +#, no-c-format +msgid "" +"If anyone ever tells you they need your root password, be extremely wary. " +"You should normally never give your root password out, unless you are " +"administering a machine with more than one system administrator." +msgstr "" + +#. Tag: para +#: using-d-i.xml:936 +#, no-c-format +msgid "" +"In case you do not specify a password for the <quote>root</quote> user here, " +"this account will be disabled but the <command>sudo</command> package will " +"be installed later to enable administrative tasks to be carried out on the " +"new system. By default, the first user created on the system will be allowed " +"to use the <command>sudo</command> command to become root." +msgstr "" + +#. Tag: title +#: using-d-i.xml:948 +#, no-c-format +msgid "Create an Ordinary User" +msgstr "" + +#. Tag: para +#: using-d-i.xml:950 +#, no-c-format +msgid "" +"The system will ask you whether you wish to create an ordinary user account " +"at this point. This account should be your main personal log-in. You should " +"<emphasis>not</emphasis> use the root account for daily use or as your " +"personal login." +msgstr "" + +#. Tag: para +#: using-d-i.xml:959 +#, no-c-format +msgid "" +"Why not? Well, one reason to avoid using root's privileges is that it is " +"very easy to do irreparable damage as root. Another reason is that you might " +"be tricked into running a <emphasis>Trojan-horse</emphasis> program — " +"that is a program that takes advantage of your super-user powers to " +"compromise the security of your system behind your back. Any good book on " +"Unix system administration will cover this topic in more detail — " +"consider reading one if it is new to you." +msgstr "" + +#. Tag: para +#: using-d-i.xml:969 +#, no-c-format +msgid "" +"You will first be prompted for the user's full name. Then you'll be asked " +"for a name for the user account; generally your first name or something " +"similar will suffice and indeed will be the default. Finally, you will be " +"prompted for a password for this account." +msgstr "" + +#. Tag: para +#: using-d-i.xml:976 +#, no-c-format +msgid "" +"If at any point after installation you would like to create another account, " +"use the <command>adduser</command> command." +msgstr "" + +#. Tag: title +#: using-d-i.xml:991 +#, no-c-format +msgid "Configuring the Clock and Time Zone" +msgstr "" + +#. Tag: para +#: using-d-i.xml:993 +#, no-c-format +msgid "" +"The installer will first attempt to connect to a time server on the Internet " +"(using the <firstterm>NTP</firstterm> protocol) in order to correctly set " +"the system time. If this does not succeed, the installer will assume the " +"time and date obtained from the system clock when the installation system " +"was booted are correct. It is not possible to manually set the system time " +"during the installation process." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1002 +#, no-c-format +msgid "The installer does not modify the system clock on the S/390 platform." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1015 +#, no-c-format +msgid "" +"Depending on the location selected earlier in the installation process, you " +"may be shown a list of time zones relevant for that location. If your " +"location has only one time zone and you are doing a default installation, " +"you will not be asked anything and the system will assume that time zone." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1023 +#, no-c-format +msgid "" +"In expert mode or when installing at medium priority, you will have the " +"additional option to select <quote>Coordinated Universal Time</quote> (UTC) " +"as time zone." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1029 +#, no-c-format +msgid "" +"If for some reason you wish to set a time zone for the installed system that " +"does <emphasis>not</emphasis> match the selected location, there are two " +"options." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1040 +#, no-c-format +msgid "" +"The simplest option is to just select a different time zone after the " +"installation has been completed and you've booted into the new system. The " +"command to do this is:" +msgstr "" + +#. Tag: screen +#: using-d-i.xml:1046 +#, no-c-format +msgid "# dpkg-reconfigure tzdata" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1052 +#, no-c-format +msgid "" +"Alternatively, the time zone can be set at the very start of the " +"installation by passing the parameter <userinput>time/" +"zone=<replaceable>value</replaceable></userinput> when you boot the " +"installation system. The value should of course be a valid time zone, for " +"example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1066 +#, no-c-format +msgid "" +"For automated installations the time zone can be set to any desired value " +"using preseeding." +msgstr "" + +#. Tag: title +#: using-d-i.xml:1079 +#, no-c-format +msgid "Partitioning and Mount Point Selection" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1080 +#, no-c-format +msgid "" +"At this time, after hardware detection has been executed a final time, &d-i; " +"should be at its full strength, customized for the user's needs and ready to " +"do some real work. As the title of this section indicates, the main task of " +"the next few components lies in partitioning your disks, creating " +"filesystems, assigning mountpoints and optionally configuring closely " +"related options like RAID, LVM or encrypted devices." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1101 +#, no-c-format +msgid "" +"If you are uncomfortable with partitioning, or just want to know more " +"details, see <xref linkend=\"partitioning\"/>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1107 +#, no-c-format +msgid "" +"If a hard disk has previously used under Solaris, the partitioner may not " +"detect the size of the drive correctly. Creating a new partition table does " +"not fix this issue. What does help, is to <quote>zero</quote> the first few " +"sectors of the drive: <informalexample><screen>\n" +"# dd if=/dev/zero of=/dev/sd<replaceable>X</replaceable> bs=512 count=2; " +"sync\n" +"</screen></informalexample> Note that this will make any existing data on " +"that disk inaccessible." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1120 +#, no-c-format +msgid "" +"First you will be given the opportunity to automatically partition either an " +"entire drive, or available free space on a drive. This is also called " +"<quote>guided</quote> partitioning. If you do not want to autopartition, " +"choose <guimenuitem>Manual</guimenuitem> from the menu." +msgstr "" + +#. Tag: title +#: using-d-i.xml:1130 +#, no-c-format +msgid "Supported partitioning options" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1131 +#, no-c-format +msgid "" +"The partitioner used in &d-i; is fairly versatile. It allows to create many " +"different partitioning schemes, using various partition tables, file systems " +"and advanced block devices." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1137 +#, no-c-format +msgid "" +"Exactly which options are available depends mainly on the architecture, but " +"also on other factors. For example, on systems with limited internal memory " +"some options may not be available. Defaults may vary as well. The type of " +"partition table used by default can for example be different for large " +"capacity hard disks than for smaller hard disks. Some options can only be " +"changed when installing at medium or low debconf priority; at higher " +"priorities sensible defaults will be used." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1148 +#, no-c-format +msgid "" +"The installer supports various forms of advanced partitioning and use of " +"storage devices, which in many cases can be used in combination." +msgstr "" + +#. Tag: emphasis +#: using-d-i.xml:1155 +#, no-c-format +msgid "Logical Volume Management (LVM)" +msgstr "" + +#. Tag: emphasis +#: using-d-i.xml:1158 +#, no-c-format +msgid "Software RAID" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1159 +#, no-c-format +msgid "Supported are RAID levels 0, 1, 4, 5, 6 and 10." +msgstr "" + +#. Tag: emphasis +#: using-d-i.xml:1163 +#, no-c-format +msgid "Encryption" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1165 +#, no-c-format +msgid "" +"<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1167 +#, no-c-format +msgid "" +"Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support " +"for Serial ATA RAID is currently only available if enabled when the " +"installer is booted. Further information is available on <ulink url=\"&url-d-" +"i-sataraid;\">our Wiki</ulink>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1173 +#, no-c-format +msgid "<emphasis>Multipath</emphasis> (experimental)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1175 +#, no-c-format +msgid "" +"See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. " +"Support for multipath is currently only available if enabled when the " +"installer is booted." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1182 +#, no-c-format +msgid "The following file systems are supported." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1187 +#, no-c-format +msgid "" +"<phrase arch=\"arm;mipsel;mips64el\"><emphasis>ext2r0</emphasis>,</phrase> " +"<emphasis>ext2</emphasis>, <phrase arch=\"linux-any\"><emphasis>ext3</" +"emphasis>,</phrase> <phrase arch=\"linux-any\"><emphasis>ext4</emphasis></" +"phrase>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1192 +#, no-c-format +msgid "" +"The default file system selected in most cases is ext4; for <filename>/boot</" +"filename> partitions ext2 will be selected by default when guided " +"partitioning is used." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1197 +#, no-c-format +msgid "<emphasis>jfs</emphasis> (not available on all architectures)" +msgstr "" + +#. Tag: emphasis +#: using-d-i.xml:1201 +#, no-c-format +msgid "<emphasis>ufs</emphasis>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1202 +#, no-c-format +msgid "The default file system is UFS." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1205 +#, no-c-format +msgid "<emphasis>xfs</emphasis> (not available on all architectures)" +msgstr "" + +#. Tag: emphasis +#: using-d-i.xml:1209 +#, no-c-format +msgid "<emphasis>zfs</emphasis>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1210 +#, no-c-format +msgid "" +"As ZFS support in the installer is still in development, only a basic subset " +"of ZFS features are supported. Some of them can be enabled manually after " +"the initial install, but there are some caveats:" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1215 +#, no-c-format +msgid "" +"Each ZFS pool will host only one filesystem. After install is finished, more " +"filesystems can be created on this pool by using the <quote>zfs create</" +"quote> command." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1220 +#, no-c-format +msgid "" +"Each ZFS pool will be composed of exactly one partition. After install is " +"finished, a single-device ZFS pool can be converted into a multi-device pool " +"by using the <quote>zpool add</quote> command, or into a mirrored pool by " +"using the <quote>zpool attach</quote> command. However, you shouldn't do " +"this on the pool that hosts root filesystem, as it would prevent GRUB from " +"booting your system." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1228 +#, no-c-format +msgid "" +"Compression is not currently supported. After the install is finished, " +"compression can be enabled by setting the <quote>compression</quote> " +"property via the <quote>zfs set</quote> command. However, if a compression " +"algorithm other than the default (lzjb) is used on the pool that hosts your " +"root filesystem, this may prevent GRUB from booting your system." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1237 +#, no-c-format +msgid "" +"<emphasis>reiserfs</emphasis> (optional; not available on all architectures)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1239 +#, no-c-format +msgid "" +"Support for the Reiser file system is no longer available by default. When " +"the installer is running at medium or low debconf priority it can be enabled " +"by selecting the <classname>partman-reiserfs</classname> component. Only " +"version 3 of the file system is supported." +msgstr "" + +#. Tag: emphasis +#: using-d-i.xml:1246 +#, no-c-format +msgid "jffs2" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1247 +#, no-c-format +msgid "" +"Used on some systems to read flash memory. It is not possible to create new " +"jffs2 partitions." +msgstr "" + +#. Tag: emphasis +#: using-d-i.xml:1252 +#, no-c-format +msgid "qnx4" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1253 +#, no-c-format +msgid "" +"Existing partitions will be recognized and it is possible to assign mount " +"points for them. It is not possible to create new qnx4 partitions." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1257 +#, no-c-format +msgid "<emphasis>FAT16</emphasis>, <emphasis>FAT32</emphasis>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1260 +#, no-c-format +msgid "<emphasis>NTFS</emphasis> (read-only)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1262 +#, no-c-format +msgid "" +"Existing NTFS partitions can be resized and it is possible to assign mount " +"points for them. It is not possible to create new NTFS partitions." +msgstr "" + +#. Tag: title +#: using-d-i.xml:1272 +#, no-c-format +msgid "Guided Partitioning" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1273 +#, no-c-format +msgid "" +"If you choose guided partitioning, you may have three options: to create " +"partitions directly on the hard disk (classic method), or to create them " +"using Logical Volume Management (LVM), or to create them using encrypted " +"LVM<footnote> <para> The installer will encrypt the LVM volume group using a " +"256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> " +"support. </para> </footnote>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1288 +#, no-c-format +msgid "" +"The option to use (encrypted) LVM may not be available on all architectures." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1293 +#, no-c-format +msgid "" +"When using LVM or encrypted LVM, the installer will create most partitions " +"inside one big partition; the advantage of this method is that partitions " +"inside this big partition can be resized relatively easily later. In the " +"case of encrypted LVM the big partition will not be readable without knowing " +"a special key phrase, thus providing extra security of your (personal) data." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1302 +#, no-c-format +msgid "" +"When using encrypted LVM, the installer will also automatically erase the " +"disk by writing random data to it. This further improves security (as it " +"makes it impossible to tell which parts of the disk are in use and also " +"makes sure that any traces of previous installations are erased), but may " +"take some time depending on the size of your disk." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1311 +#, no-c-format +msgid "" +"If you choose guided partitioning using LVM or encrypted LVM, some changes " +"in the partition table will need to be written to the selected disk while " +"LVM is being set up. These changes effectively erase all data that is " +"currently on the selected hard disk and you will not be able to undo them " +"later. However, the installer will ask you to confirm these changes before " +"they are written to disk." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1321 +#, no-c-format +msgid "" +"If you choose guided partitioning<phrase arch=\"linux-any\"> (either classic " +"or using (encrypted) LVM)</phrase> for a whole disk, you will first be asked " +"to select the disk you want to use. Check that all your disks are listed " +"and, if you have several disks, make sure you select the correct one. The " +"order they are listed in may differ from what you are used to. The size of " +"the disks may help to identify them." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1330 +#, no-c-format +msgid "" +"Any data on the disk you select will eventually be lost, but you will always " +"be asked to confirm any changes before they are written to the disk. <phrase " +"arch=\"linux-any\"> If you have selected the classic method of partitioning, " +"you will be able to undo any changes right until the end; when using " +"(encrypted) LVM this is not possible. </phrase>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1340 +#, no-c-format +msgid "" +"Next, you will be able to choose from the schemes listed in the table below. " +"All schemes have their pros and cons, some of which are discussed in <xref " +"linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in " +"mind that guided partitioning needs a certain minimal amount of free space " +"to operate with. If you don't give it at least about 1GB of space (depends " +"on chosen scheme), guided partitioning will fail." +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1356 +#, no-c-format +msgid "Partitioning scheme" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1357 +#, no-c-format +msgid "Minimum space" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1358 +#, no-c-format +msgid "Created partitions" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1364 +#, no-c-format +msgid "All files in one partition" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1365 +#, no-c-format +msgid "600MB" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1366 +#, no-c-format +msgid "<filename>/</filename>, swap" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1368 +#, no-c-format +msgid "Separate /home partition" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1369 +#, no-c-format +msgid "500MB" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1370 +#, no-c-format +msgid "<filename>/</filename>, <filename>/home</filename>, swap" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1374 +#, no-c-format +msgid "Separate /home, /var and /tmp partitions" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1375 +#, no-c-format +msgid "<entry>1GB</entry>" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1376 +#, no-c-format +msgid "" +"<filename>/</filename>, <filename>/home</filename>, <filename>/var</" +"filename>, <filename>/tmp</filename>, swap" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1385 +#, no-c-format +msgid "" +"If you choose guided partitioning using (encrypted) LVM, the installer will " +"also create a separate <filename>/boot</filename> partition. The other " +"partitions, including the swap partition, will be created inside the LVM " +"partition." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1391 +#, no-c-format +msgid "" +"If you have booted in EFI mode then within the guided partitioning setup " +"there will be an additional partition, formatted as a FAT32 bootable " +"filesystem, for the EFI boot loader. This partition is known as an EFI " +"System Partition (ESP). There is also an additional menu item in the " +"formatting menu to manually set up a partition as an ESP." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1399 +#, no-c-format +msgid "" +"After selecting a scheme, the next screen will show your new partition " +"table, including information on whether and how partitions will be formatted " +"and where they will be mounted." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1405 +#, no-c-format +msgid "" +"The list of partitions might look like this: <informalexample><screen>\n" +" SCSI1 (0,0,0) (sda) - 6.4 GB WDC AC36400L\n" +" #1 primary 16.4 MB B f ext2 /boot\n" +" #2 primary 551.0 MB swap swap\n" +" #3 primary 5.8 GB ntfs\n" +" pri/log 8.2 MB FREE SPACE\n" +"\n" +" SCSI2 (1,0,0) (sdb) - 80.0 GB ST380021A\n" +" #1 primary 15.9 MB ext3\n" +" #2 primary 996.0 MB fat16\n" +" #3 primary 3.9 GB xfs /home\n" +" #5 logical 6.0 GB f ext4 /\n" +" #6 logical 1.0 GB f ext3 /var\n" +" #7 logical 498.8 MB ext3\n" +"</screen></informalexample> This example shows two hard drives divided into " +"several partitions; the first disk has some free space. Each partition line " +"consists of the partition number, its type, size, optional flags, file " +"system, and mountpoint (if any). Note: this particular setup cannot be " +"created using guided partitioning but it does show possible variation that " +"can be achieved using manual partitioning." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1418 +#, no-c-format +msgid "" +"This concludes the guided partitioning. If you are satisfied with the " +"generated partition table, you can choose <guimenuitem>Finish partitioning " +"and write changes to disk</guimenuitem> from the menu to implement the new " +"partition table (as described at the end of this section). If you are not " +"happy, you can choose to <guimenuitem>Undo changes to partitions</" +"guimenuitem> and run guided partitioning again, or modify the proposed " +"changes as described below for manual partitioning." +msgstr "" + +#. Tag: title +#: using-d-i.xml:1432 +#, no-c-format +msgid "Manual Partitioning" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1433 +#, no-c-format +msgid "" +"A similar screen to the one shown just above will be displayed if you choose " +"manual partitioning except that your existing partition table will be shown " +"and without the mount points. How to manually set up your partition table " +"and the usage of partitions by your new &debian; system will be covered in " +"the remainder of this section." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1441 +#, no-c-format +msgid "" +"If you select a pristine disk which has neither partitions nor free space on " +"it, you will be asked if a new partition table should be created (this is " +"needed so you can create new partitions). After this, a new line entitled " +"<quote>FREE SPACE</quote> should appear in the table under the selected disk." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1449 +#, no-c-format +msgid "" +"If you select some free space, you will have the opportunity to create a new " +"partition. You will have to answer a quick series of questions about its " +"size, type (primary or logical), and location (beginning or end of the free " +"space). After this, you will be presented with a detailed overview of your " +"new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which " +"determines if the partition will have a file system on it, or be used for " +"swap,<phrase arch=\"linux-any\"> software RAID, LVM, an encrypted file " +"system,</phrase> or not be used at all. Other settings include mountpoint, " +"mount options, and bootable flag; which settings are shown depends on how " +"the partition is to be used. If you don't like the preselected defaults, " +"feel free to change them to your liking. E.g. by selecting the option " +"<guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem " +"for this partition, including options to use the partition for swap,<phrase " +"arch=\"linux-any\"> software RAID, LVM,</phrase> or not use it at all. When " +"you are satisfied with your new partition, select <guimenuitem>Done setting " +"up the partition</guimenuitem> and you will return to <command>partman</" +"command>'s main screen." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1470 +#, no-c-format +msgid "" +"If you decide you want to change something about your partition, simply " +"select the partition, which will bring you to the partition configuration " +"menu. This is the same screen as is used when creating a new partition, so " +"you can change the same settings. One thing that may not be very obvious at " +"a first glance is that you can resize the partition by selecting the item " +"displaying the size of the partition. Filesystems known to work are at least " +"fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a " +"partition." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1481 +#, no-c-format +msgid "" +"Be sure to create at least two partitions: one for the <emphasis>root</" +"emphasis> filesystem (which must be mounted as <filename>/</filename>) and " +"one for <emphasis>swap</emphasis>. If you forget to mount the root " +"filesystem, <command>partman</command> won't let you continue until you " +"correct this issue." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1489 +#, no-c-format +msgid "" +"If you boot in EFI mode but forget to select and format an EFI System " +"Partition, <command>partman</command> will detect this and will not let you " +"continue until you allocate one." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1495 +#, no-c-format +msgid "" +"Capabilities of <command>partman</command> can be extended with installer " +"modules, but are dependent on your system's architecture. So if you can't " +"see all promised goodies, check if you have loaded all required modules (e." +"g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or " +"<filename>partman-lvm</filename>)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1503 +#, no-c-format +msgid "" +"After you are satisfied with partitioning, select <guimenuitem>Finish " +"partitioning and write changes to disk</guimenuitem> from the partitioning " +"menu. You will be presented with a summary of changes made to the disks and " +"asked to confirm that the filesystems should be created as requested." +msgstr "" + +#. Tag: title +#: using-d-i.xml:1531 +#, no-c-format +msgid "Configuring Multidisk Devices (Software RAID)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1532 +#, no-c-format +msgid "" +"If you have more than one harddrive<footnote><para> To be honest, you can " +"construct an MD device even from partitions residing on single physical " +"drive, but that won't give any benefits. </para></footnote> in your " +"computer, you can use <command>partman-md</command> to set up your drives " +"for increased performance and/or better reliability of your data. The result " +"is called <firstterm>Multidisk Device</firstterm> (or after its most famous " +"variant <firstterm>software RAID</firstterm>)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1545 +#, no-c-format +msgid "" +"MD is basically a bunch of partitions located on different disks and " +"combined together to form a <emphasis>logical</emphasis> device. This device " +"can then be used like an ordinary partition (i.e. in <command>partman</" +"command> you can format it, assign a mountpoint, etc.)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1553 +#, no-c-format +msgid "" +"What benefits this brings depends on the type of MD device you are creating. " +"Currently supported are: <variablelist> <varlistentry> <term>RAID0</" +"term><listitem><para> Is mainly aimed at performance. RAID0 splits all " +"incoming data into <firstterm>stripes</firstterm> and distributes them " +"equally over each disk in the array. This can increase the speed of read/" +"write operations, but when one of the disks fails, you will lose " +"<emphasis>everything</emphasis> (part of the information is still on the " +"healthy disk(s), the other part <emphasis>was</emphasis> on the failed " +"disk). </para><para> The typical use for RAID0 is a partition for video " +"editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</" +"term><listitem><para> Is suitable for setups where reliability is the first " +"concern. It consists of several (usually two) equally-sized partitions where " +"every partition contains exactly the same data. This essentially means three " +"things. First, if one of your disks fails, you still have the data mirrored " +"on the remaining disks. Second, you can use only a fraction of the available " +"capacity (more precisely, it is the size of the smallest partition in the " +"RAID). Third, file-reads are load-balanced among the disks, which can " +"improve performance on a server, such as a file server, that tends to be " +"loaded with more disk reads than writes. </para><para> Optionally you can " +"have a spare disk in the array which will take the place of the failed disk " +"in the case of failure. </para></listitem> </varlistentry> <varlistentry> " +"<term>RAID5</term><listitem><para> Is a good compromise between speed, " +"reliability and data redundancy. RAID5 splits all incoming data into stripes " +"and distributes them equally on all but one disk (similar to RAID0). Unlike " +"RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which " +"gets written on the remaining disk. The parity disk is not static (that " +"would be called RAID4), but is changing periodically, so the parity " +"information is distributed equally on all disks. When one of the disks " +"fails, the missing part of information can be computed from remaining data " +"and its parity. RAID5 must consist of at least three active partitions. " +"Optionally you can have a spare disk in the array which will take the place " +"of the failed disk in the case of failure. </para><para> As you can see, " +"RAID5 has a similar degree of reliability to RAID1 while achieving less " +"redundancy. On the other hand, it might be a bit slower on write operations " +"than RAID0 due to computation of parity information. </para></listitem> </" +"varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar " +"to RAID5 except that it uses two parity devices instead of one. </" +"para><para> A RAID6 array can survive up to two disk failures. </para></" +"listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> " +"RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It " +"creates <replaceable>n</replaceable> copies of incoming data and distributes " +"them across the partitions so that none of the copies of the same data are " +"on the same device. The default value of <replaceable>n</replaceable> is 2, " +"but it can be set to something else in expert mode. The number of partitions " +"used must be at least <replaceable>n</replaceable>. RAID10 has different " +"layouts for distributing the copies. The default is near copies. Near copies " +"have all of the copies at about the same offset on all of the disks. Far " +"copies have the copies at different offsets on the disks. Offset copies copy " +"the stripe, not the individual copies. </para><para> RAID10 can be used to " +"achieve reliability and redundancy without the drawback of having to " +"calculate parity. </para></listitem> </varlistentry> </variablelist> To sum " +"it up:" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1667 +#, no-c-format +msgid "Type" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1668 +#, no-c-format +msgid "Minimum Devices" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1669 +#, no-c-format +msgid "Spare Device" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1670 +#, no-c-format +msgid "Survives disk failure?" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1671 +#, no-c-format +msgid "Available Space" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1677 +#, no-c-format +msgid "RAID0" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1678 using-d-i.xml:1686 using-d-i.xml:1716 +#, no-c-format +msgid "<entry>2</entry>" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1679 using-d-i.xml:1680 +#, no-c-format +msgid "<entry>no</entry>" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1681 +#, no-c-format +msgid "Size of the smallest partition multiplied by number of devices in RAID" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1685 +#, no-c-format +msgid "RAID1" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1687 using-d-i.xml:1695 using-d-i.xml:1706 using-d-i.xml:1717 +#, no-c-format +msgid "optional" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1688 using-d-i.xml:1696 using-d-i.xml:1707 using-d-i.xml:1718 +#, no-c-format +msgid "<entry>yes</entry>" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1689 +#, no-c-format +msgid "Size of the smallest partition in RAID" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1693 +#, no-c-format +msgid "RAID5" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1694 +#, no-c-format +msgid "<entry>3</entry>" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1697 +#, no-c-format +msgid "" +"Size of the smallest partition multiplied by (number of devices in RAID " +"minus one)" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1704 +#, no-c-format +msgid "RAID6" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1705 +#, no-c-format +msgid "<entry>4</entry>" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1708 +#, no-c-format +msgid "" +"Size of the smallest partition multiplied by (number of devices in RAID " +"minus two)" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1715 +#, no-c-format +msgid "RAID10" +msgstr "" + +#. Tag: entry +#: using-d-i.xml:1719 +#, no-c-format +msgid "" +"Total of all partitions divided by the number of chunk copies (defaults to " +"two)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1726 +#, no-c-format +msgid "" +"If you want to know more about Software RAID, have a look at <ulink url=" +"\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1731 +#, no-c-format +msgid "" +"To create an MD device, you need to have the desired partitions it should " +"consist of marked for use in a RAID. (This is done in <command>partman</" +"command> in the <guimenu>Partition settings</guimenu> menu where you should " +"select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume " +"for RAID</guimenuitem> </menuchoice>.)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1740 +#, no-c-format +msgid "" +"Make sure that the system can be booted with the partitioning scheme you are " +"planning. In general it will be necessary to create a separate file system " +"for <filename>/boot</filename> when using RAID for the root (<filename>/</" +"filename>) file system. Most boot loaders <phrase arch=\"x86\">(including " +"grub)</phrase> do support mirrored (not striped!) RAID1, so using for " +"example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</" +"filename> can be an option." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1751 +#, no-c-format +msgid "" +"Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> " +"from the main <command>partman</command> menu. (The menu will only appear " +"after you mark at least one partition for use as <guimenuitem>physical " +"volume for RAID</guimenuitem>.) On the first screen of <command>partman-md</" +"command> simply select <guimenuitem>Create MD device</guimenuitem>. You will " +"be presented with a list of supported types of MD devices, from which you " +"should choose one (e.g. RAID1). What follows depends on the type of MD you " +"selected." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1764 +#, no-c-format +msgid "" +"RAID0 is simple — you will be issued with the list of available RAID " +"partitions and your only task is to select the partitions which will form " +"the MD." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1771 +#, no-c-format +msgid "" +"RAID1 is a bit more tricky. First, you will be asked to enter the number of " +"active devices and the number of spare devices which will form the MD. Next, " +"you need to select from the list of available RAID partitions those that " +"will be active and then those that will be spare. The count of selected " +"partitions must be equal to the number provided earlier. Don't worry. If you " +"make a mistake and select a different number of partitions, &d-i; won't let " +"you continue until you correct the issue." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1783 +#, no-c-format +msgid "" +"RAID5 has a setup procedure similar to RAID1 with the exception that you " +"need to use at least <emphasis>three</emphasis> active partitions." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1789 +#, no-c-format +msgid "" +"RAID6 also has a setup procedure similar to RAID1 except that at least " +"<emphasis>four</emphasis> active partitions are required." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1795 +#, no-c-format +msgid "" +"RAID10 again has a setup procedure similar to RAID1 except in expert mode. " +"In expert mode, &d-i; will ask you for the layout. The layout has two parts. " +"The first part is the layout type. It is either <literal>n</literal> (for " +"near copies), <literal>f</literal> (for far copies), or <literal>o</literal> " +"(for offset copies). The second part is the number of copies to make of the " +"data. There must be at least that many active devices so that all of the " +"copies can be distributed onto different disks." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1809 +#, no-c-format +msgid "" +"It is perfectly possible to have several types of MD at once. For example, " +"if you have three 200 GB hard drives dedicated to MD, each containing two " +"100 GB partitions, you can combine the first partitions on all three disks " +"into the RAID0 (fast 300 GB video editing partition) and use the other three " +"partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition " +"for <filename>/home</filename>)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1818 +#, no-c-format +msgid "" +"After you set up MD devices to your liking, you can <guimenuitem>Finish</" +"guimenuitem> <command>partman-md</command> to return back to the " +"<command>partman</command> to create filesystems on your new MD devices and " +"assign them the usual attributes like mountpoints." +msgstr "" + +#. Tag: title +#: using-d-i.xml:1833 +#, no-c-format +msgid "Configuring the Logical Volume Manager (LVM)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1834 +#, no-c-format +msgid "" +"If you are working with computers at the level of system administrator or " +"<quote>advanced</quote> user, you have surely seen the situation where some " +"disk partition (usually the most important one) was short on space, while " +"some other partition was grossly underused and you had to manage this " +"situation by moving stuff around, symlinking, etc." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1842 +#, no-c-format +msgid "" +"To avoid the described situation you can use Logical Volume Manager (LVM). " +"Simply said, with LVM you can combine your partitions (<firstterm>physical " +"volumes</firstterm> in LVM lingo) to form a virtual disk (so called " +"<firstterm>volume group</firstterm>), which can then be divided into virtual " +"partitions (<firstterm>logical volumes</firstterm>). The point is that " +"logical volumes (and of course underlying volume groups) can span across " +"several physical disks." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1852 +#, no-c-format +msgid "" +"Now when you realize you need more space for your old 160GB <filename>/home</" +"filename> partition, you can simply add a new 300GB disk to the computer, " +"join it with your existing volume group and then resize the logical volume " +"which holds your <filename>/home</filename> filesystem and voila — " +"your users have some room again on their renewed 460GB partition. This " +"example is of course a bit oversimplified. If you haven't read it yet, you " +"should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1863 +#, no-c-format +msgid "" +"LVM setup in &d-i; is quite simple and completely supported inside " +"<command>partman</command>. First, you have to mark the partition(s) to be " +"used as physical volumes for LVM. This is done in the <guimenu>Partition " +"settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:" +"</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1872 +#, no-c-format +msgid "" +"Be aware: the new LVM setup will destroy all data on all partitions marked " +"with an LVM type code. So, if you already have an LVM on some of your disks, " +"and want to install Debian additionally to that machine, the old (already " +"existing) LVM will be wiped out! The same counts for partitions, which are " +"(for any reason) misleadingly marked with an LVM type code, but contain " +"something different (like an encrypted volume). You need to remove such " +"disks from the system, before performing a new LVM setup!" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1882 +#, no-c-format +msgid "" +"When you return to the main <command>partman</command> screen, you will see " +"a new option <guimenuitem>Configure the Logical Volume Manager</" +"guimenuitem>. When you select that, you will first be asked to confirm " +"pending changes to the partition table (if any) and after that the LVM " +"configuration menu will be shown. Above the menu a summary of the LVM " +"configuration is shown. The menu itself is context sensitive and only shows " +"valid actions. The possible actions are:" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1893 +#, no-c-format +msgid "" +"<guimenuitem>Display configuration details</guimenuitem>: shows LVM device " +"structure, names and sizes of logical volumes and more" +msgstr "" + +#. Tag: guimenuitem +#: using-d-i.xml:1898 +#, no-c-format +msgid "Create volume group" +msgstr "" + +#. Tag: guimenuitem +#: using-d-i.xml:1901 +#, no-c-format +msgid "Create logical volume" +msgstr "" + +#. Tag: guimenuitem +#: using-d-i.xml:1904 +#, no-c-format +msgid "Delete volume group" +msgstr "" + +#. Tag: guimenuitem +#: using-d-i.xml:1907 +#, no-c-format +msgid "Delete logical volume" +msgstr "" + +#. Tag: guimenuitem +#: using-d-i.xml:1910 +#, no-c-format +msgid "Extend volume group" +msgstr "" + +#. Tag: guimenuitem +#: using-d-i.xml:1913 +#, no-c-format +msgid "Reduce volume group" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1915 +#, no-c-format +msgid "" +"<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</" +"command> screen" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1921 +#, no-c-format +msgid "" +"Use the options in that menu to first create a volume group and then create " +"your logical volumes inside it." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1926 +#, no-c-format +msgid "" +"After you return to the main <command>partman</command> screen, any created " +"logical volumes will be displayed in the same way as ordinary partitions " +"(and you should treat them as such)." +msgstr "" + +#. Tag: title +#: using-d-i.xml:1940 +#, no-c-format +msgid "Configuring Encrypted Volumes" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1941 +#, no-c-format +msgid "" +"&d-i; allows you to set up encrypted partitions. Every file you write to " +"such a partition is immediately saved to the device in encrypted form. " +"Access to the encrypted data is granted only after entering the " +"<firstterm>passphrase</firstterm> used when the encrypted partition was " +"originally created. This feature is useful to protect sensitive data in case " +"your laptop or hard drive gets stolen. The thief might get physical access " +"to the hard drive, but without knowing the right passphrase, the data on the " +"hard drive will look like random characters." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1953 +#, no-c-format +msgid "" +"The two most important partitions to encrypt are: the home partition, where " +"your private data resides, and the swap partition, where sensitive data " +"might be stored temporarily during operation. Of course, nothing prevents " +"you from encrypting any other partitions that might be of interest. For " +"example <filename>/var</filename> where database servers, mail servers or " +"print servers store their data, or <filename>/tmp</filename> which is used " +"by various programs to store potentially interesting temporary files. Some " +"people may even want to encrypt their whole system. Generally the only " +"exception here is the <filename>/boot</filename> partition which must remain " +"unencrypted, because historically there was no way to load the kernel from " +"an encrypted partition. (GRUB is now able to do that, but &d-i; currently " +"lacks native support for encrypted <filename>/boot</filename>. The setup is " +"therefore covered in a <ulink url=\"https://cryptsetup-team.pages.debian.net/" +"cryptsetup/encrypted-boot.html\">separate document</ulink>.)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:1971 +#, no-c-format +msgid "" +"Please note that the performance of encrypted partitions will be less than " +"that of unencrypted ones because the data needs to be decrypted or encrypted " +"for every read or write. The performance impact depends on your CPU speed, " +"chosen cipher and a key length." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1978 +#, no-c-format +msgid "" +"To use encryption, you have to create a new partition by selecting some free " +"space in the main partitioning menu. Another option is to choose an existing " +"partition (e.g. a regular partition, an LVM logical volume or a RAID " +"volume). In the <guimenu>Partition settings</guimenu> menu, you need to " +"select <guimenuitem>physical volume for encryption</guimenuitem> at the " +"<menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will " +"then change to include several cryptographic options for the partition." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1989 +#, no-c-format +msgid "" +"The encryption method supported by &d-i; is <firstterm>dm-crypt</firstterm> " +"(included in newer Linux kernels, able to host LVM physical volumes)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:1998 +#, no-c-format +msgid "" +"Let's have a look at the options available when you select encryption via " +"<userinput>Device-mapper (dm-crypt)</userinput>. As always: when in doubt, " +"use the defaults, because they have been carefully chosen with security in " +"mind." +msgstr "" + +#. Tag: term +#: using-d-i.xml:2008 +#, no-c-format +msgid "Encryption: <userinput>aes</userinput>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2010 +#, no-c-format +msgid "" +"This option lets you select the encryption algorithm (<firstterm>cipher</" +"firstterm>) which will be used to encrypt the data on the partition. &d-i; " +"currently supports the following block ciphers: <firstterm>aes</firstterm>, " +"<firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and " +"<firstterm>twofish</firstterm>. It is beyond the scope of this document to " +"discuss the qualities of these different algorithms, however, it might help " +"your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by " +"the American National Institute of Standards and Technology as the standard " +"encryption algorithm for protecting sensitive information in the 21st " +"century." +msgstr "" + +#. Tag: term +#: using-d-i.xml:2028 +#, no-c-format +msgid "Key size: <userinput>256</userinput>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2030 +#, no-c-format +msgid "" +"Here you can specify the length of the encryption key. With a larger key " +"size, the strength of the encryption is generally improved. On the other " +"hand, increasing the length of the key usually has a negative impact on " +"performance. Available key sizes vary depending on the cipher." +msgstr "" + +#. Tag: term +#: using-d-i.xml:2042 +#, no-c-format +msgid "IV algorithm: <userinput>xts-plain64</userinput>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2044 +#, no-c-format +msgid "" +"The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</" +"firstterm> algorithm is used in cryptography to ensure that applying the " +"cipher on the same <firstterm>clear text</firstterm> data with the same key " +"always produces a unique <firstterm>cipher text</firstterm>. The idea is to " +"prevent the attacker from deducing information from repeated patterns in the " +"encrypted data." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2054 +#, no-c-format +msgid "" +"From the provided alternatives, the default <userinput>xts-plain64</" +"userinput> is currently the least vulnerable to known attacks. Use the other " +"alternatives only when you need to ensure compatibility with some previously " +"installed system that is not able to use newer algorithms." +msgstr "" + +#. Tag: term +#: using-d-i.xml:2066 +#, no-c-format +msgid "Encryption key: <userinput>Passphrase</userinput>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2068 +#, no-c-format +msgid "Here you can choose the type of the encryption key for this partition." +msgstr "" + +#. Tag: term +#: using-d-i.xml:2074 +#, no-c-format +msgid "Passphrase" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2075 +#, no-c-format +msgid "" +"The encryption key will be computed<footnote> <para> Using a passphrase as " +"the key currently means that the partition will be set up using <ulink url=" +"\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase " +"which you will be able to enter later in the process." +msgstr "" + +#. Tag: term +#: using-d-i.xml:2090 +#, no-c-format +msgid "Random key" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2091 +#, no-c-format +msgid "" +"A new encryption key will be generated from random data each time you try to " +"bring up the encrypted partition. In other words: on every shutdown the " +"content of the partition will be lost as the key is deleted from memory. (Of " +"course, you could try to guess the key with a brute force attack, but unless " +"there is an unknown weakness in the cipher algorithm, it is not achievable " +"in our lifetime.)" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2100 +#, no-c-format +msgid "" +"Random keys are useful for swap partitions because you do not need to bother " +"yourself with remembering the passphrase or wiping sensitive information " +"from the swap partition before shutting down your computer. However, it also " +"means that you will <emphasis>not</emphasis> be able to use the " +"<quote>suspend-to-disk</quote> functionality offered by newer Linux kernels " +"as it will be impossible (during a subsequent boot) to recover the suspended " +"data written to the swap partition." +msgstr "" + +#. Tag: term +#: using-d-i.xml:2119 +#, no-c-format +msgid "Erase data: <userinput>yes</userinput>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2121 +#, no-c-format +msgid "" +"Determines whether the content of this partition should be overwritten with " +"random data before setting up the encryption. This is recommended because it " +"might otherwise be possible for an attacker to discern which parts of the " +"partition are in use and which are not. In addition, this will make it " +"harder to recover any leftover data from previous " +"installations<footnote><para> It is believed that the guys from three-letter " +"agencies can restore the data even after several rewrites of the " +"magnetooptical media, though. </para></footnote>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2142 +#, no-c-format +msgid "" +"After you have selected the desired parameters for your encrypted " +"partitions, return back to the main partitioning menu. There should now be a " +"new menu item called <guimenu>Configure encrypted volumes</guimenu>. After " +"you select it, you will be asked to confirm the deletion of data on " +"partitions marked to be erased and possibly other actions such as writing a " +"new partition table. For large partitions this might take some time." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2152 +#, no-c-format +msgid "" +"Next you will be asked to enter a passphrase for partitions configured to " +"use one. Good passphrases should be longer than 8 characters, should be a " +"mixture of letters, numbers and other characters and should not contain " +"common dictionary words or information easily associable with you (such as " +"birthdates, hobbies, pet names, names of family members or relatives, etc.)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2161 +#, no-c-format +msgid "" +"Before you input any passphrases, you should have made sure that your " +"keyboard is configured correctly and generates the expected characters. If " +"you are unsure, you can switch to the second virtual console and type some " +"text at the prompt. This ensures that you won't be surprised later, e.g. by " +"trying to input a passphrase using a qwerty keyboard layout when you used an " +"azerty layout during the installation. This situation can have several " +"causes. Maybe you switched to another keyboard layout during the " +"installation, or the selected keyboard layout might not have been set up yet " +"when entering the passphrase for the root file system." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2174 +#, no-c-format +msgid "" +"If you selected to use methods other than a passphrase to create encryption " +"keys, they will be generated now. Because the kernel may not have gathered a " +"sufficient amount of entropy at this early stage of the installation, the " +"process may take a long time. You can help speed up the process by " +"generating entropy: e.g. by pressing random keys, or by switching to the " +"shell on the second virtual console and generating some network and disk " +"traffic (downloading some files, feeding big files into <filename>/dev/null</" +"filename>, etc.). This will be repeated for each partition to be encrypted." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2190 +#, no-c-format +msgid "" +"After returning to the main partitioning menu, you will see all encrypted " +"volumes as additional partitions which can be configured in the same way as " +"ordinary partitions. The following example shows a volume encrypted via dm-" +"crypt. <informalexample><screen>\n" +"Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux " +"device-mapper\n" +" #1 115.1 GB F ext3\n" +"</screen></informalexample> Now is the time to assign mount points to the " +"volumes and optionally change the file system types if the defaults do not " +"suit you." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2202 +#, no-c-format +msgid "" +"Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</" +"replaceable> in this case) and the mount points you assigned to each " +"encrypted volume. You will need this information later when booting the new " +"system. The differences between the ordinary boot process and the boot " +"process with encryption involved will be covered later in <xref linkend=" +"\"mount-encrypted-volumes\"/>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2212 +#, no-c-format +msgid "" +"Once you are satisfied with the partitioning scheme, continue with the " +"installation." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2223 +#, no-c-format +msgid "Installing the Base System" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2224 +#, no-c-format +msgid "" +"Although this stage is the least problematic, it consumes a significant " +"fraction of the install because it downloads, verifies and unpacks the whole " +"base system. If you have a slow computer or network connection, this could " +"take some time." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2237 +#, no-c-format +msgid "" +"During installation of the base system, package unpacking and setup messages " +"are redirected to <userinput>tty4</userinput>. You can access this terminal " +"by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></" +"keycombo>; get back to the main installer process with " +"<keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2246 +#, no-c-format +msgid "" +"The unpack/setup messages generated during this phase are also saved in " +"<filename>/var/log/syslog</filename>. You can check them there if the " +"installation is performed over a serial console." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2252 +#, no-c-format +msgid "" +"As part of the installation, a &arch-kernel; kernel will be installed. At " +"the default priority, the installer will choose one for you that best " +"matches your hardware. In lower priority modes, you will be able to choose " +"from a list of available kernels." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2259 +#, no-c-format +msgid "" +"When packages are installed using the package management system, it will by " +"default also install packages that are recommended by those packages. " +"Recommended packages are not strictly required for the core functionality of " +"the selected software, but they do enhance that software and should, in the " +"view of the package maintainers, normally be installed together with that " +"software." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2269 +#, no-c-format +msgid "" +"For technical reasons packages installed during the installation of the base " +"system are installed without their <quote>Recommends</quote>. The rule " +"described above only takes effect after this point in the installation " +"process." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2281 +#, no-c-format +msgid "Installing Additional Software" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2282 +#, no-c-format +msgid "" +"At this point you have a usable but limited system. Most users will want to " +"install additional software on the system to tune it to their needs, and the " +"installer allows you do so. This step can take even longer than installing " +"the base system if you have a slow computer or network connection." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2297 +#, no-c-format +msgid "Configuring apt" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2299 +#, no-c-format +msgid "" +"One of the tools used to install packages on a &debian-gnu; system is the " +"program <command>apt</command>, from the <classname>apt</classname> " +"package<footnote> <para> Note that the program which actually installs the " +"packages is called <command>dpkg</command>. However, this program is more of " +"a low-level tool. <command>apt</command> is a higher-level tool, which will " +"invoke <command>dpkg</command> as appropriate. It knows how to retrieve " +"packages from your installation media, the network, or wherever. It is also " +"able to automatically install other packages which are required to make the " +"package you're trying to install work correctly. </para> </footnote>. Other " +"front-ends for package management, like <command>aptitude</command> and " +"<command>synaptic</command>, are also in use. These front-ends are " +"recommended for new users, since they integrate some additional features " +"(package searching and status checks) in a nice user interface." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2322 +#, no-c-format +msgid "" +"<command>apt</command> must be configured so that it knows from where to " +"retrieve packages. The results of this configuration are written to the file " +"<filename>/etc/apt/sources.list</filename>. You can examine and edit this " +"file to your liking after the installation is complete." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2329 +#, no-c-format +msgid "" +"If you are installing at default priority, the installer will largely take " +"care of the configuration automatically, based on the installation method " +"you are using and possibly using choices made earlier in the installation. " +"In most cases the installer will automatically add a security mirror and, if " +"you are installing the stable distribution, a mirror for the <quote>stable-" +"updates</quote> service." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2338 +#, no-c-format +msgid "" +"If you are installing at a lower priority (e.g. in expert mode), you will be " +"able to make more decisions yourself. You can choose whether or not to use " +"the security and/or stable-updates services, and you can choose to add " +"packages from the <quote>contrib</quote> and <quote>non-free</quote> " +"sections of the archive." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2349 +#, no-c-format +msgid "Installing from more than one CD or DVD image" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2351 +#, no-c-format +msgid "" +"If you are installing from a CD or DVD image that is part of a larger set, " +"the installer will ask if you want to scan additional installation media. If " +"you have such additional media available, you probably want to do this so " +"the installer can use the packages included on them." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2358 +#, no-c-format +msgid "" +"If you do not have any additional media, that is no problem: using them is " +"not required. If you also do not use a network mirror (as explained in the " +"next section), it can mean that not all packages belonging to the tasks you " +"select in the next step of the installation can be installed." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2366 +#, no-c-format +msgid "" +"Packages are included on CD and DVD images in the order of their popularity. " +"This means that for most uses only the first image of a set is needed and " +"that only very few people actually use any of the packages included on the " +"last images of a set." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2373 +#, no-c-format +msgid "" +"It also means that buying or downloading and burning a full CD set is just a " +"waste of money as you'll never use most of them. In most cases you are " +"better off getting only the first 3 to 8 CDs and installing any additional " +"packages you may need from the Internet by using a mirror. The same goes for " +"DVD sets: the first DVD, or maybe the first two DVDs will cover most needs." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2383 +#, no-c-format +msgid "" +"If you do scan multiple installation media, the installer will prompt you to " +"exchange them when it needs packages from one that isn't currently in the " +"drive. Note that only discs that belong to the same set should be scanned. " +"The order in which they are scanned does not really matter, but scanning " +"them in ascending order will reduce the chance of mistakes." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2396 +#, no-c-format +msgid "Using a network mirror" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2398 +#, no-c-format +msgid "" +"One question that will be asked during most installs is whether or not to " +"use a network mirror as a source for packages. In most cases the default " +"answer should be fine, but there are some exceptions." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2404 +#, no-c-format +msgid "" +"If you are <emphasis>not</emphasis> installing from a full CD/DVD image, you " +"really should use a network mirror as otherwise you will end up with only a " +"very minimal system. However, if you have a limited Internet connection it " +"is best <emphasis>not</emphasis> to select the <literal>desktop</literal> " +"task in the next step of the installation." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2413 +#, no-c-format +msgid "" +"If you are installing from a single full CD image, using a network mirror is " +"not required, but is still strongly recommended because a single CD image " +"contains only a fairly limited number of packages. If you have a limited " +"Internet connection it may still be best to <emphasis>not</emphasis> select " +"a network mirror here, but to finish the installation using only what's " +"available on the CD image and selectively install additional packages after " +"the installation (i.e. after you have rebooted into the new system)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2424 +#, no-c-format +msgid "" +"If you are installing from DVD, any packages needed during the installation " +"should be present on the first DVD image. Use of a network mirror is " +"optional." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2430 +#, no-c-format +msgid "" +"One advantage of adding a network mirror is that updates, that have occurred " +"since the CD/DVD images were created and have been included in a point " +"release, will become available for installation, thus extending the life of " +"your CD/DVD set without compromising the security or stability of the " +"installed system." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2437 +#, no-c-format +msgid "" +"In summary: selecting a network mirror is generally a good idea, except if " +"you do not have a good Internet connection. If the current version of a " +"package is available from installation media, the installer will always use " +"that. The amount of data that will be downloaded if you do select a mirror " +"thus depends on" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2446 +#, no-c-format +msgid "the tasks you select in the next step of the installation," +msgstr "" + +#. Tag: para +#: using-d-i.xml:2451 +#, no-c-format +msgid "which packages are needed for those tasks," +msgstr "" + +#. Tag: para +#: using-d-i.xml:2456 +#, no-c-format +msgid "" +"which of those packages are present on the installation media you have " +"scanned, and" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2461 +#, no-c-format +msgid "" +"whether any updated versions of packages included on the installation media " +"are available from a mirror (either a regular package mirror, or a mirror " +"for security or stable-updates)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2470 +#, no-c-format +msgid "" +"Note that the last point means that, even if you choose not to use a network " +"mirror, some packages may still be downloaded from the Internet if there is " +"a security or stable-updates update available for them and those services " +"have been configured." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2481 +#, no-c-format +msgid "Choosing a network mirror" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2482 +#, no-c-format +msgid "" +"Unless you chose not to use a network mirror, you will be presented with a " +"list of network mirrors based upon your country selection earlier in the " +"installation process. Choosing the offered default is usually fine." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2489 +#, no-c-format +msgid "" +"The offered default is deb.debian.org, which is not a mirror itself but will " +"redirect to a mirror that should be up-to-date and fast. These mirrors " +"support TLS (https protocol) and IPv6. This service is maintained by the " +"Debian System Administration (DSA) team." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2496 +#, no-c-format +msgid "" +"A mirror can also be specified by hand by choosing <quote>enter information " +"manually</quote> . You can then specify a mirror host name and an optional " +"port number. This actually has to be a URL base, i.e. when specifying an " +"IPv6 address, one has to add square brackets around it, for instance " +"<quote>[2001:db8::1]</quote>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2504 +#, no-c-format +msgid "" +"If your computer is on an IPv6-only network (which is probably not the case " +"for the vast majority of users), using the default mirror for your country " +"might not work. All the mirrors in the list are reachable via IPv4, but only " +"some of them can be used via IPv6. As connectivity of individual mirrors can " +"change over time, this information is not available in the installer. If " +"there is no IPv6 connectivity for the default mirror for your country, you " +"can either try some of the other mirrors offered to you or choose the " +"<quote>enter information manually</quote> option. You can then specify " +"<quote>ftp.ipv6.debian.org</quote> as the mirror name, which is an alias for " +"a mirror available via IPv6, although it will probably not be the fastest " +"possible one." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2527 +#, no-c-format +msgid "Selecting and Installing Software" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2529 +#, no-c-format +msgid "" +"During the installation process, you are given the opportunity to select " +"additional software to install. Rather than picking individual software " +"packages from the &num-of-distrib-pkgs; available packages, this stage of " +"the installation process focuses on selecting and installing predefined " +"collections of software to quickly set up your computer to perform various " +"tasks." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2538 +#, no-c-format +msgid "" +"These tasks loosely represent a number of different jobs or things you want " +"to do with your computer, such as <quote>Desktop environment</quote>, " +"<quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> " +"You should know that to present this list, the installer is merely invoking " +"the <command>tasksel</command> program. It can be run at any time after " +"installation to install more packages (or remove them), or you can use a " +"more fine-grained tool such as <command>aptitude</command>. If you are " +"looking for a specific single package, after installation is complete, " +"simply run <userinput>aptitude install <replaceable>package</replaceable></" +"userinput>, where <replaceable>package</replaceable> is the name of the " +"package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-" +"size-list\"/> lists the space requirements for the available tasks." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2564 +#, 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 deselect " +"them. You can even opt to install no tasks at all at this point." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2571 +#, 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:2577 +#, no-c-format +msgid "" +"The <quote>Desktop environment</quote> task will install a graphical desktop " +"environment." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2582 +#, no-c-format +msgid "" +"By default, &d-i; installs the <phrase arch=\"x86\">Gnome</phrase> <phrase " +"arch=\"non-x86\">Xfce</phrase> desktop environment. It is possible to " +"interactively select a different desktop environment during the " +"installation. It is also possible to install multiple desktops, but some " +"combinations of desktop may not be co-installable." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2590 +#, no-c-format +msgid "" +"Note that this will only work if the packages needed for the desired desktop " +"environment are actually available. If you are installing using a single " +"full CD image, they will possibly need to be downloaded from a network " +"mirror as they might not be available on the CD image due to its limited " +"amount of space. Installing any of the available desktop environments this " +"way should work fine if you are using a DVD image or any other installation " +"method." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2600 +#, no-c-format +msgid "" +"The various server tasks will install software roughly as follows. Web " +"server: <classname>apache2</classname>; Print server: <classname>cups</" +"classname>; SSH server: <classname>openssh</classname>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2607 +#, no-c-format +msgid "" +"The <quote>Standard system</quote> task will install any package that has a " +"priority <quote>standard</quote>. This includes a lot of common utilities " +"that are normally available on any Linux or Unix system. You should leave " +"this task selected unless you know what you are doing and want a really " +"minimal system." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2615 +#, no-c-format +msgid "" +"If during language selection a default locale other than the <quote>C</" +"quote> locale was selected, <command>tasksel</command> will check if any " +"localization tasks are defined for that locale and will automatically try to " +"install relevant localization packages. This includes for example packages " +"containing word lists or special fonts for your language. If a desktop " +"environment was selected, it will also install appropriate localization " +"packages for that (if available)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2625 +#, no-c-format +msgid "" +"Once you've selected your tasks, select &BTN-CONT;. At this point, " +"<command>apt</command> will install the packages that are part of the " +"selected tasks. If a particular program needs more information from the " +"user, it will prompt you during this process." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2632 +#, 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:2641 +#, 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: title +#: using-d-i.xml:2656 +#, no-c-format +msgid "Making Your System Bootable" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2658 +#, 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:2673 +#, no-c-format +msgid "Detecting other operating systems" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2675 +#, 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:2683 +#, 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:2701 +#, no-c-format +msgid "<command>palo</command>-installer" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2702 +#, 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:2711 +#, no-c-format +msgid "hppa FIXME ( need more info )" +msgstr "" + +#. Tag: title +#: using-d-i.xml:2723 +#, no-c-format +msgid "Install the <command>Grub</command> Boot Loader on the drive" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2725 +#, no-c-format +msgid "" +"The &architecture; boot loader is called <quote>grub</quote>. Grub is a " +"flexible and robust boot loader and a good default choice for new users and " +"old hands alike." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2731 +#, no-c-format +msgid "" +"By default, grub will be installed on the UEFI partition/the Boot Record of " +"the primary drive, 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:2738 +#, no-c-format +msgid "" +"If you do not want to install grub, use the &BTN-GOBACK; button to get to " +"the main menu, and from there select whatever bootloader you would like to " +"use." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2751 +#, no-c-format +msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2753 +#, 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:2769 +#, 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:2781 +#, no-c-format +msgid "Choose the correct partition!" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2783 +#, no-c-format +msgid "" +"The criterion for selecting a partition is that it must be a 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:2798 +#, no-c-format +msgid "EFI Partition Contents" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2800 +#, 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:2822 +#, no-c-format +msgid "elilo.conf" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2823 +#, 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:2832 +#, no-c-format +msgid "elilo.efi" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2833 +#, 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:2843 +#, no-c-format +msgid "initrd.img" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2844 +#, 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:2856 +#, no-c-format +msgid "readme.txt" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2857 +#, 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:2867 +#, no-c-format +msgid "vmlinuz" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2868 +#, 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:2892 +#, no-c-format +msgid "Install <command>Yaboot</command> on a Hard Disk" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2893 +#, 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-gnu;." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2911 +#, no-c-format +msgid "Install <command>Quik</command> on a Hard Disk" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2912 +#, 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:2928 +#, no-c-format +msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2930 +#, 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 new users and " +"old hands alike." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2936 +#, no-c-format +msgid "" +"By default, Grub will be installed into the PReP partition, where it will " +"over complete control of the boot process." +msgstr "" + +#. Tag: title +#: using-d-i.xml:2949 +#, no-c-format +msgid "<command>zipl</command>-installer" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2950 +#, 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:2967 +#, no-c-format +msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2969 +#, 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:2994 +#, no-c-format +msgid "Making the system bootable with flash-kernel" +msgstr "" + +#. Tag: para +#: using-d-i.xml:2995 +#, no-c-format +msgid "" +"As there is no common firmware interface on all ARM platforms, the steps " +"required to make the system bootable on ARM devices are highly device-" +"dependent. &debian; uses a tool called <command>flash-kernel </command> to " +"take care of this. Flash-kernel contains a database which describes the " +"particular operations that are required to make the system bootable on " +"various devices. It detects whether the current device is supported, and if " +"yes, performs the necessary operations." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3006 +#, no-c-format +msgid "" +"On devices which boot from internal NOR- or NAND-flash memory, flash-kernel " +"writes the kernel and the initial ramdisk to this internal memory. This " +"method is particularly common on older armel devices. Please note that most " +"of these devices do not allow having multiple kernels and ramdisks in their " +"internal flash memory, i.e. running flash-kernel on them usually overwrites " +"the previous contents of the flash memory!" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3016 +#, no-c-format +msgid "" +"For ARM systems that use U-Boot as their system firmware and boot the kernel " +"and the initial ramdisk from external storage media (such as MMC/SD-cards, " +"USB mass storage devices or IDE/SATA harddisks), flash-kernel generates an " +"appropriate boot script to allow autobooting without user interaction." +msgstr "" + +#. Tag: title +#: using-d-i.xml:3032 +#, no-c-format +msgid "Continue Without Boot Loader" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3034 +#, 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)." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3041 +#, 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:3058 +#, no-c-format +msgid "Finishing the Installation" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3059 +#, no-c-format +msgid "" +"This is the last step in the &debian; installation process during which the " +"installer will do any last minute tasks. It mostly consists of tidying up " +"after the &d-i;." +msgstr "" + +#. Tag: title +#: using-d-i.xml:3072 +#, no-c-format +msgid "Setting the System Clock" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3074 +#, no-c-format +msgid "" +"The installer may ask you if the computer's clock is set to UTC. Normally " +"this question is avoided if possible and the installer tries to work out " +"whether the clock is set to UTC based on things like what other operating " +"systems are installed." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3081 +#, no-c-format +msgid "" +"In expert mode you will always be able to choose whether or not the clock is " +"set to UTC. <phrase arch=\"powerpc\">Macintosh hardware clocks are normally " +"set to local time. If you want to dual-boot, select local time instead of " +"UTC.</phrase> <phrase arch=\"any-x86\">Systems that (also) run Dos or " +"Windows are normally set to local time. If you want to dual-boot, select " +"local time instead of UTC.</phrase>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3092 +#, no-c-format +msgid "" +"At this point &d-i; will also attempt to save the current time to the " +"system's hardware clock. This will be done either in UTC or local time, " +"depending on the selection that was just made." +msgstr "" + +#. Tag: title +#: using-d-i.xml:3107 +#, no-c-format +msgid "Reboot the System" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3109 +#, no-c-format +msgid "" +"You will be prompted to remove the boot media (CD, USB stick, etc) that you " +"used to boot the installer. After that the system will be rebooted into your " +"new &debian; system." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3115 +#, no-c-format +msgid "" +"After a final prompt the system will be halted because rebooting is not " +"supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD " +"which you selected for the root filesystem during the first steps of the " +"installation." +msgstr "" + +#. Tag: title +#: using-d-i.xml:3128 +#, no-c-format +msgid "Troubleshooting" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3129 +#, 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:3142 +#, no-c-format +msgid "Saving the installation logs" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3144 +#, 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:3151 +#, no-c-format +msgid "" +"Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu " +"allows you to save the log files to a USB stick, 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:3171 +#, no-c-format +msgid "Using the Shell and Viewing the Logs" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3173 +#, 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 the installer itself." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3191 +#, no-c-format +msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3195 +#, 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. " +"You can get to the main menu from most dialogs by using the &BTN-GOBACK; " +"button one or more times. Type <userinput>exit</userinput> to close the " +"shell and return to the installer." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3203 +#, 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:3212 +#, 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:3219 +#, 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:3225 +#, 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:3241 +#, no-c-format +msgid "Installation Over the Network" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3243 +#, 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:3253 +#, 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 optical media, " +"you need to boot with medium priority or otherwise invoke the main " +"installation menu and choose <guimenuitem>Load installer components from " +"installation media</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:3266 +#, 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:3271 +#, 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 person who will continue the installation remotely." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3283 +#, 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:3289 +#, 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" +"<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</" +"replaceable></userinput>\n" +"</screen></informalexample> Where <replaceable>install_host</replaceable> is " +"either the name or IP address of the computer being installed. Before the " +"actual login the fingerprint of the remote system will be displayed and you " +"will have to confirm that it is correct." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3306 +#, no-c-format +msgid "" +"The <command>ssh</command> server in the installer uses a default " +"configuration that does not send keep-alive packets. In principle, a " +"connection to the system being installed should be kept open indefinitely. " +"However, in some situations — depending on your local network setup " +"— the connection may be lost after some period of inactivity. One " +"common case where this can happen is when there is some form of Network " +"Address Translation (NAT) somewhere between the client and the system being " +"installed. Depending on at which point of the installation the connection " +"was lost, you may or may not be able to resume the installation after " +"reconnecting." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3319 +#, no-c-format +msgid "" +"You may be able to avoid the connection being dropped by adding the option " +"<userinput>-o ServerAliveInterval=<replaceable>value</replaceable></" +"userinput> when starting the <command>ssh</command> connection, or by adding " +"that option in your <command>ssh</command> configuration file. Note however " +"that in some cases adding this option may also <emphasis>cause</emphasis> a " +"connection to be dropped (for example if keep-alive packets are sent during " +"a brief network outage, from which <command>ssh</command> would otherwise " +"have recovered), so it should only be used when needed." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3332 +#, 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><footnote> <para> The following command will remove an existing " +"entry for a host: <command>ssh-keygen -R <<replaceable>hostname</" +"replaceable>|<replaceable>IP address</replaceable>></command>. </" +"para> </footnote> and try again." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3348 +#, 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:3358 +#, 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: title +#: using-d-i.xml:3377 +#, no-c-format +msgid "Loading Missing Firmware" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3378 +#, no-c-format +msgid "" +"As described in <xref linkend=\"hardware-firmware\"/>, some devices require " +"firmware to be loaded. In most cases the device will not work at all if the " +"firmware is not available; sometimes basic functionality is not impaired if " +"it is missing and the firmware is only needed to enable additional features." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3386 +#, no-c-format +msgid "" +"If a device driver requests firmware that is not available, &d-i; will " +"display a dialog offering to load the missing firmware. If this option is " +"selected, &d-i; will scan available devices for either loose firmware files " +"or packages containing firmware. If found, the firmware will be copied to " +"the correct location (<filename>/lib/firmware</filename>) and the driver " +"module will be reloaded." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3396 +#, no-c-format +msgid "" +"Which devices are scanned and which file systems are supported depends on " +"the architecture, the installation method and the stage of the installation. " +"Especially during the early stages of the installation, loading the firmware " +"is most likely to succeed from a FAT-formatted USB stick. <phrase arch=" +"\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card." +"</phrase>" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3406 +#, no-c-format +msgid "" +"Note that it is possible to skip loading the firmware if you know the device " +"will also function without it, or if the device is not needed during the " +"installation." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3412 +#, no-c-format +msgid "" +"&d-i; only prompts for firmware needed by kernel modules loaded during the " +"installation. Not all drivers are included in &d-i;, in particular radeon is " +"not, so this implies that the capabilities of some devices may be no " +"different at the end of the installation from what they were at the " +"beginning. Consequently, some of your hardware may not be being used to its " +"full potential. If you suspect this is the case, or are just curious, it is " +"not a bad idea to check the output of the <command>dmesg</command> command " +"on the newly booted system and search for <quote>firmware</quote>." +msgstr "" + +#. Tag: title +#: using-d-i.xml:3426 +#, no-c-format +msgid "Preparing a medium" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3427 +#, no-c-format +msgid "" +"Official installation images do not include non-free firmware. The most " +"common method to load such firmware is from some removable medium such as a " +"USB stick. Alternatively, unofficial installation images containing non-free " +"firmware can be found at <ulink url=\"&url-firmware-cds;\"></ulink>. To " +"prepare a USB stick (or other medium like a hard drive partition), the " +"firmware files or packages must be placed in either the root directory or a " +"directory named <filename>/firmware</filename> of the file system on the " +"medium. The recommended file system to use is FAT as that is most certain to " +"be supported during the early stages of the installation." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3440 +#, no-c-format +msgid "" +"Tarballs and zip files containing current packages for the most common " +"firmware are available from: <itemizedlist> <listitem><para> <ulink url=" +"\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just " +"download the tarball or zip file for the correct release and unpack it to " +"the file system on the medium." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3454 +#, no-c-format +msgid "" +"If the firmware you need is not included in the tarball, you can also " +"download specific firmware packages from the (non-free section of the) " +"archive. The following overview should list most available firmware packages " +"but is not guaranteed to be complete and may also contain non-firmware " +"packages:" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3468 +#, no-c-format +msgid "" +"It is also possible to copy individual firmware files to the medium. Loose " +"firmware could be obtained for example from an already installed system or " +"from a hardware vendor." +msgstr "" + +#. Tag: title +#: using-d-i.xml:3477 +#, no-c-format +msgid "Firmware and the Installed System" +msgstr "" + +#. Tag: para +#: using-d-i.xml:3478 +#, no-c-format +msgid "" +"Any firmware loaded during the installation will be copied automatically to " +"the installed system. In most cases this will ensure that the device that " +"requires the firmware will also work correctly after the system is rebooted " +"into the installed system. However, if the installed system runs a different " +"kernel version from the installer there is a slight chance that the firmware " +"cannot be loaded due to version skew." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3487 +#, no-c-format +msgid "" +"If the firmware was loaded from a firmware package, &d-i; will also install " +"this package for the installed system and will automatically add the non-" +"free section of the package archive in APT's <filename>sources.list</" +"filename>. This has the advantage that the firmware should be updated " +"automatically if a new version becomes available." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3495 +#, no-c-format +msgid "" +"If loading the firmware was skipped during the installation, the relevant " +"device will probably not work with the installed system until the firmware " +"(package) is installed manually." +msgstr "" + +#. Tag: para +#: using-d-i.xml:3502 +#, no-c-format +msgid "" +"If the firmware was loaded from loose firmware files, the firmware copied to " +"the installed system will <emphasis>not</emphasis> be automatically updated " +"unless the corresponding firmware package (if available) is installed after " +"the installation is completed." +msgstr "" diff --git a/po/kab/welcome.po b/po/kab/welcome.po new file mode 100644 index 000000000..22522c5e7 --- /dev/null +++ b/po/kab/welcome.po @@ -0,0 +1,765 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-welcome 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2019-09-22 23:04+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" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: welcome.xml:4 +#, no-c-format +msgid "Welcome to &debian;" +msgstr "" + +#. Tag: para +#: welcome.xml:5 +#, no-c-format +msgid "" +"This chapter provides an overview of the &debian; Project and &debian-gnu;. " +"If you already know about the &debian; Project's history and the &debian-" +"gnu; distribution, feel free to skip to the next chapter." +msgstr "" + +#. Tag: title +#: welcome.xml:19 +#, no-c-format +msgid "What is Debian?" +msgstr "" + +#. Tag: para +#: welcome.xml:20 +#, no-c-format +msgid "" +"Debian is an all-volunteer organization dedicated to developing free " +"software and promoting the ideals of the Free Software community. The Debian " +"Project began in 1993, when Ian Murdock issued an open invitation to " +"software developers to contribute to a complete and coherent software " +"distribution based on the relatively new Linux kernel. That relatively small " +"band of dedicated enthusiasts, originally funded by the <ulink url=\"&url-" +"fsf;\">Free Software Foundation</ulink> and influenced by the <ulink url=" +"\"&url-gnu-intro;\">GNU</ulink> philosophy, has grown over the years into an " +"organization of around &num-of-debian-developers; <firstterm>Debian " +"Developers</firstterm>." +msgstr "" + +#. Tag: para +#: welcome.xml:35 +#, no-c-format +msgid "" +"Debian Developers are involved in a variety of activities, including <ulink " +"url=\"&url-debian-home;\">Web</ulink> and <ulink url=\"&url-debian-ftp;" +"\">FTP</ulink> site administration, graphic design, legal analysis of " +"software licenses, writing documentation, and, of course, maintaining " +"software packages." +msgstr "" + +#. Tag: para +#: welcome.xml:44 +#, no-c-format +msgid "" +"In the interest of communicating our philosophy and attracting developers " +"who believe in the principles that Debian stands for, the Debian Project has " +"published a number of documents that outline our values and serve as guides " +"to what it means to be a Debian Developer:" +msgstr "" + +#. Tag: para +#: welcome.xml:52 +#, no-c-format +msgid "" +"The <ulink url=\"&url-social-contract;\">Debian Social Contract</ulink> is a " +"statement of Debian's commitments to the Free Software Community. Anyone who " +"agrees to abide to the Social Contract may become a <ulink url=\"&url-new-" +"maintainer;\">maintainer</ulink>. Any maintainer can introduce new software " +"into Debian — provided that the software meets our criteria for being " +"free, and the package follows our quality standards." +msgstr "" + +#. Tag: para +#: welcome.xml:64 +#, no-c-format +msgid "" +"The <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink> are a " +"clear and concise statement of Debian's criteria for free software. The DFSG " +"is a very influential document in the Free Software Movement, and was the " +"foundation of the <ulink url=\"&url-osd;\">The Open Source Definition</" +"ulink>." +msgstr "" + +#. Tag: para +#: welcome.xml:74 +#, no-c-format +msgid "" +"The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> is an " +"extensive specification of the Debian Project's standards of quality." +msgstr "" + +#. Tag: para +#: welcome.xml:82 +#, no-c-format +msgid "" +"Debian developers are also involved in a number of other projects; some " +"specific to Debian, others involving some or all of the Linux community. " +"Some examples include:" +msgstr "" + +#. Tag: para +#: welcome.xml:89 +#, no-c-format +msgid "" +"The <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> " +"(FHS) is an effort to standardize the layout of the Linux file system. The " +"FHS will allow software developers to concentrate their efforts on designing " +"programs, without having to worry about how the package will be installed in " +"different GNU/Linux distributions." +msgstr "" + +#. Tag: para +#: welcome.xml:99 +#, no-c-format +msgid "" +"<ulink url=\"&url-debian-jr;\">Debian Jr.</ulink> is an internal project, " +"aimed at making sure Debian has something to offer to our youngest users." +msgstr "" + +#. Tag: para +#: welcome.xml:108 +#, no-c-format +msgid "" +"For more general information about Debian, see the <ulink url=\"&url-debian-" +"faq;\">Debian FAQ</ulink>." +msgstr "" + +#. Tag: title +#: welcome.xml:123 +#, no-c-format +msgid "What is GNU/Linux?" +msgstr "" + +#. Tag: para +#: welcome.xml:124 +#, no-c-format +msgid "" +"Linux is an operating system: a series of programs that let you interact " +"with your computer and run other programs." +msgstr "" + +#. Tag: para +#: welcome.xml:129 +#, no-c-format +msgid "" +"An operating system consists of various fundamental programs which are " +"needed by your computer so that it can communicate and receive instructions " +"from users; read and write data to hard disks, tapes, and printers; control " +"the use of memory; and run other software. The most important part of an " +"operating system is the kernel. In a GNU/Linux system, Linux is the kernel " +"component. The rest of the system consists of other programs, many of which " +"were written by or for the GNU Project. Because the Linux kernel alone does " +"not form a working operating system, we prefer to use the term <quote>GNU/" +"Linux</quote> to refer to systems that many people casually refer to as " +"<quote>Linux</quote>." +msgstr "" + +#. Tag: para +#: welcome.xml:143 +#, no-c-format +msgid "" +"Linux is modelled on the Unix operating system. From the start, Linux was " +"designed to be a multi-tasking, multi-user system. These facts are enough to " +"make Linux different from other well-known operating systems. However, Linux " +"is even more different than you might imagine. In contrast to other " +"operating systems, nobody owns Linux. Much of its development is done by " +"unpaid volunteers." +msgstr "" + +#. Tag: para +#: welcome.xml:152 +#, no-c-format +msgid "" +"Development of what later became GNU/Linux began in 1984, when the <ulink " +"url=\"&url-fsf;\">Free Software Foundation</ulink> began development of a " +"free Unix-like operating system called GNU." +msgstr "" + +#. Tag: para +#: welcome.xml:158 +#, no-c-format +msgid "" +"The <ulink url=\"&url-gnu;\">GNU Project</ulink> has developed a " +"comprehensive set of free software tools for use with Unix™ and Unix-" +"like operating systems such as Linux. These tools enable users to perform " +"tasks ranging from the mundane (such as copying or removing files from the " +"system) to the arcane (such as writing and compiling programs or doing " +"sophisticated editing in a variety of document formats)." +msgstr "" + +#. Tag: para +#: welcome.xml:168 +#, no-c-format +msgid "" +"While many groups and individuals have contributed to Linux, the largest " +"single contributor is still the Free Software Foundation, which created not " +"only most of the tools used in Linux, but also the philosophy and the " +"community that made Linux possible." +msgstr "" + +#. Tag: para +#: welcome.xml:175 +#, no-c-format +msgid "" +"The <ulink url=\"&url-kernel-org;\">Linux kernel</ulink> first appeared in " +"1991, when a Finnish computing science student named Linus Torvalds " +"announced an early version of a replacement kernel for Minix to the Usenet " +"newsgroup <userinput>comp.os.minix</userinput>. See Linux International's " +"<ulink url=\"&url-linux-history;\">Linux History Page</ulink>." +msgstr "" + +#. Tag: para +#: welcome.xml:184 +#, no-c-format +msgid "" +"Linus Torvalds continues to coordinate the work of several hundred " +"developers with the help of a number of subsystem maintainers. There is an " +"<ulink url=\"&url-kernel-org;\">official website</ulink> for the Linux " +"kernel. Information about the <userinput>linux-kernel</userinput> mailing " +"list can be found on the <ulink url=\"&url-linux-kernel-list-faq;\">linux-" +"kernel mailing list FAQ</ulink>." +msgstr "" + +#. Tag: para +#: welcome.xml:194 +#, no-c-format +msgid "" +"Linux users have immense freedom of choice in their software. For example, " +"Linux users can choose from a dozen different command line shells and " +"several graphical desktops. This selection is often bewildering to users of " +"other operating systems, who are not used to thinking of the command line or " +"desktop as something that they can change." +msgstr "" + +#. Tag: para +#: welcome.xml:203 +#, no-c-format +msgid "" +"Linux is also less likely to crash, better able to run more than one program " +"at the same time, and more secure than many operating systems. With these " +"advantages, Linux is the fastest growing operating system in the server " +"market. More recently, Linux has begun to be popular among home and business " +"users as well." +msgstr "" + +#. Tag: title +#: welcome.xml:221 +#, no-c-format +msgid "What is &debian; GNU/Linux?" +msgstr "" + +#. Tag: para +#: welcome.xml:222 +#, no-c-format +msgid "" +"The combination of &debian;'s philosophy and methodology and the GNU tools, " +"the Linux kernel, and other important free software, form a unique software " +"distribution called &debian; GNU/Linux. This distribution is made up of a " +"large number of software <emphasis>packages</emphasis>. Each package in the " +"distribution contains executables, scripts, documentation, and configuration " +"information, and has a <emphasis>maintainer</emphasis> who is primarily " +"responsible for keeping the package up-to-date, tracking bug reports, and " +"communicating with the upstream author(s) of the packaged software. Our " +"extremely large user base, combined with our bug tracking system ensures " +"that problems are found and fixed quickly." +msgstr "" + +#. Tag: para +#: welcome.xml:236 +#, no-c-format +msgid "" +"&debian;'s attention to detail allows us to produce a high-quality, stable, " +"and scalable distribution. Installations can be easily configured to serve " +"many roles, from stripped-down firewalls to desktop scientific workstations " +"to high-end network servers." +msgstr "" + +#. Tag: para +#: welcome.xml:243 +#, no-c-format +msgid "" +"&debian; is especially popular among advanced users because of its technical " +"excellence and its deep commitment to the needs and expectations of the " +"Linux community. &debian; also introduced many features to Linux that are " +"now commonplace." +msgstr "" + +#. Tag: para +#: welcome.xml:250 +#, no-c-format +msgid "" +"For example, &debian; was the first Linux distribution to include a package " +"management system for easy installation and removal of software. It was also " +"the first Linux distribution that could be upgraded without requiring " +"reinstallation." +msgstr "" + +#. Tag: para +#: welcome.xml:257 +#, no-c-format +msgid "" +"&debian; continues to be a leader in Linux development. Its development " +"process is an example of just how well the Open Source development model can " +"work — even for very complex tasks such as building and maintaining a " +"complete operating system." +msgstr "" + +#. Tag: para +#: welcome.xml:264 +#, no-c-format +msgid "" +"The feature that most distinguishes &debian; from other Linux distributions " +"is its package management system. These tools give the administrator of a " +"&debian; system complete control over the packages installed on that system, " +"including the ability to install a single package or automatically update " +"the entire operating system. Individual packages can also be protected from " +"being updated. You can even tell the package management system about " +"software you have compiled yourself and what dependencies it fulfills." +msgstr "" + +#. Tag: para +#: welcome.xml:275 +#, no-c-format +msgid "" +"To protect your system against <quote>Trojan horses</quote> and other " +"malevolent software, &debian;'s servers verify that uploaded packages come " +"from their registered &debian; maintainers. &debian; packagers also take " +"great care to configure their packages in a secure manner. When security " +"problems in shipped packages do appear, fixes are usually available very " +"quickly. With &debian;'s simple update options, security fixes can be " +"downloaded and installed automatically across the Internet." +msgstr "" + +#. Tag: para +#: welcome.xml:285 +#, no-c-format +msgid "" +"The primary, and best, method of getting support for your &debian; GNU/Linux " +"system and communicating with &debian; Developers is through the many " +"mailing lists maintained by the &debian; Project (there are more than &num-" +"of-debian-maillists; at this writing). The easiest way to subscribe to one " +"or more of these lists is visit <ulink url=\"&url-debian-lists-subscribe;\"> " +"Debian's mailing list subscription page</ulink> and fill out the form you'll " +"find there." +msgstr "" + +#. Tag: title +#: welcome.xml:308 +#, no-c-format +msgid "What is &debian; GNU/kFreeBSD?" +msgstr "" + +#. Tag: para +#: welcome.xml:310 +#, no-c-format +msgid "" +"&debian; GNU/kFreeBSD is a &debian; GNU system with the kFreeBSD kernel." +msgstr "" + +#. Tag: para +#: welcome.xml:314 +#, no-c-format +msgid "" +"This port of &debian; is currently only being developed for the i386 and " +"amd64 architectures, although ports to other architectures is possible." +msgstr "" + +#. Tag: para +#: welcome.xml:319 +#, no-c-format +msgid "" +"Please note that &debian; GNU/kFreeBSD is not a Linux system, and thus some " +"information on Linux system may not apply to it." +msgstr "" + +#. Tag: para +#: welcome.xml:324 +#, no-c-format +msgid "" +"For more information, see the <ulink url=\"http://www.debian.org/ports/" +"kfreebsd-gnu/\"> &debian; GNU/kFreeBSD ports page</ulink> and the " +"<email>debian-bsd@lists.debian.org</email> mailing list." +msgstr "" + +#. Tag: title +#: welcome.xml:343 +#, no-c-format +msgid "What is &debian; GNU/Hurd?" +msgstr "" + +#. Tag: para +#: welcome.xml:345 +#, no-c-format +msgid "" +"&debian; GNU/Hurd is a &debian; GNU system with the GNU Hurd — a set " +"of servers running on top of the GNU Mach microkernel." +msgstr "" + +#. Tag: para +#: welcome.xml:350 +#, no-c-format +msgid "" +"The Hurd is still unfinished, and is unsuitable for day-to-day use, but work " +"is continuing. The Hurd is currently only being developed for the i386 " +"architecture, although ports to other architectures will be made once the " +"system becomes more stable." +msgstr "" + +#. Tag: para +#: welcome.xml:358 +#, no-c-format +msgid "" +"Please note that &debian; GNU/Hurd is not a Linux system, and thus some " +"information on Linux system may not apply to it." +msgstr "" + +#. Tag: para +#: welcome.xml:363 +#, no-c-format +msgid "" +"For more information, see the <ulink url=\"http://www.debian.org/ports/hurd/" +"\"> &debian; GNU/Hurd ports page</ulink> and the <email>debian-hurd@lists." +"debian.org</email> mailing list." +msgstr "" + +#. Tag: title +#: welcome.xml:380 +#, no-c-format +msgid "What is the Debian Installer?" +msgstr "" + +#. Tag: para +#: welcome.xml:382 +#, no-c-format +msgid "" +"Debian Installer, also known as <quote>d-i</quote>, is the software system " +"to install a basic working Debian system. A wide range of hardware such as " +"embedded devices, laptops, desktops and server machines is supported and a " +"large set of free software for many purposes is offered." +msgstr "" + +#. Tag: para +#: welcome.xml:389 +#, no-c-format +msgid "" +"The installation is conducted by answering a basic set of questions. Also " +"available are an expert mode that allows to control every aspect of the " +"installation and an advanced feature to perform automated installations. The " +"installed system can be used as is or further customized. The installation " +"can be performed from a multitude of sources: USB, CD/DVD/Blu-Ray or the " +"network. The installer supports localized installations in more than 80 " +"languages." +msgstr "" + +#. Tag: para +#: welcome.xml:399 +#, no-c-format +msgid "" +"The installer has its origin in the boot-floppies project, and it was <ulink " +"url=\"http://lists.debian.org/debian-boot/2000/06/msg00279.html\">first " +"mentioned</ulink> by Joey Hess in 2000. Since then the installation system " +"has been continuously developed by volunteers improving and adding more " +"features." +msgstr "" + +#. Tag: para +#: welcome.xml:407 +#, no-c-format +msgid "" +"More information can be found on the <ulink url=\"&url-d-i;\">Debian " +"Installer page</ulink>, on the <ulink url=\"&url-d-i-wiki;\">Wiki</ulink> " +"and on the <ulink url=\"&url-debian-boot-list;\">debian-boot mailing list</" +"ulink>." +msgstr "" + +#. Tag: title +#: welcome.xml:422 +#, no-c-format +msgid "Getting &debian;" +msgstr "" + +#. Tag: para +#: welcome.xml:424 +#, no-c-format +msgid "" +"For information on how to download &debian-gnu; from the Internet or from " +"whom official &debian; installation media can be purchased, see the <ulink " +"url=\"&url-debian-distrib;\">distribution web page</ulink>. The <ulink url=" +"\"&url-debian-mirrors;\">list of &debian; mirrors</ulink> contains a full " +"set of official &debian; mirrors, so you can easily find the nearest one." +msgstr "" + +#. Tag: para +#: welcome.xml:433 +#, no-c-format +msgid "" +"&debian; can be upgraded after installation very easily. The installation " +"procedure will help set up the system so that you can make those upgrades " +"once installation is complete, if need be." +msgstr "" + +#. Tag: title +#: welcome.xml:448 +#, no-c-format +msgid "Getting the Newest Version of This Document" +msgstr "" + +#. Tag: para +#: welcome.xml:450 +#, no-c-format +msgid "" +"This document is constantly being revised. Be sure to check the <ulink url=" +"\"&url-release-area;\"> Debian &release; pages</ulink> for any last-minute " +"information about the &release; release of the &debian-gnu; system. Updated " +"versions of this installation manual are also available from the <ulink url=" +"\"&url-install-manual;\">official Install Manual pages</ulink>." +msgstr "" + +#. Tag: title +#: welcome.xml:468 +#, no-c-format +msgid "Organization of This Document" +msgstr "" + +#. Tag: para +#: welcome.xml:470 +#, no-c-format +msgid "" +"This document is meant to serve as a manual for first-time &debian; users. " +"It tries to make as few assumptions as possible about your level of " +"expertise. However, we do assume that you have a general understanding of " +"how the hardware in your computer works." +msgstr "" + +#. Tag: para +#: welcome.xml:477 +#, no-c-format +msgid "" +"Expert users may also find interesting reference information in this " +"document, including minimum installation sizes, details about the hardware " +"supported by the &debian; installation system, and so on. We encourage " +"expert users to jump around in the document." +msgstr "" + +#. Tag: para +#: welcome.xml:484 +#, no-c-format +msgid "" +"In general, this manual is arranged in a linear fashion, walking you through " +"the installation process from start to finish. Here are the steps in " +"installing &debian-gnu;, and the sections of this document which correlate " +"with each step:" +msgstr "" + +#. Tag: para +#: welcome.xml:492 +#, no-c-format +msgid "" +"Determine whether your hardware meets the requirements for using the " +"installation system, in <xref linkend=\"hardware-req\"/>." +msgstr "" + +#. Tag: para +#: welcome.xml:498 +#, no-c-format +msgid "" +"Backup your system, perform any necessary planning and hardware " +"configuration prior to installing &debian;, in <xref linkend=\"preparing\"/" +">. If you are preparing a multi-boot system, you may need to create " +"partitionable space on your hard disk for &debian; to use." +msgstr "" + +#. Tag: para +#: welcome.xml:506 +#, no-c-format +msgid "" +"In <xref linkend=\"install-methods\"/>, you will obtain the necessary " +"installation files for your method of installation." +msgstr "" + +#. Tag: para +#: welcome.xml:512 +#, no-c-format +msgid "" +"The next <xref linkend=\"boot-installer\"/> describes booting into the " +"installation system. This chapter also discusses troubleshooting procedures " +"in case you have problems with this step." +msgstr "" + +#. Tag: para +#: welcome.xml:519 +#, no-c-format +msgid "" +"Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. " +"This involves choosing your language, configuring peripheral driver modules, " +"configuring your network connection, so that remaining installation files " +"can be obtained directly from a &debian; server (if you are not installing " +"from a set of CD/DVD installation images), partitioning your hard drives and " +"installation of a base system, then selection and installation of tasks. " +"(Some background about setting up the partitions for your &debian; system is " +"explained in <xref linkend=\"partitioning\"/>.)" +msgstr "" + +#. Tag: para +#: welcome.xml:532 +#, no-c-format +msgid "" +"Boot into your newly installed base system, from <xref linkend=\"boot-new\"/" +">." +msgstr "" + +#. Tag: para +#: welcome.xml:540 +#, no-c-format +msgid "" +"Once you've got your system installed, you can read <xref linkend=\"post-" +"install\"/>. That chapter explains where to look to find more information " +"about Unix and &debian;, and how to replace your kernel." +msgstr "" + +#. Tag: para +#: welcome.xml:550 +#, no-c-format +msgid "" +"Finally, information about this document and how to contribute to it may be " +"found in <xref linkend=\"administrivia\"/>." +msgstr "" + +#. Tag: title +#: welcome.xml:560 +#, no-c-format +msgid "Your Documentation Help is Welcome" +msgstr "" + +#. Tag: para +#: welcome.xml:562 +#, no-c-format +msgid "" +"Any help, suggestions, and especially, patches, are greatly appreciated. " +"Working versions of this document can be found at <ulink url=\"&url-d-i-" +"dillon-manual;\"></ulink>. There you will find a list of all the different " +"architectures and languages for which this document is available." +msgstr "" + +#. Tag: para +#: welcome.xml:569 +#, no-c-format +msgid "" +"Source is also available publicly; look in <xref linkend=\"administrivia\"/> " +"for more information concerning how to contribute. We welcome suggestions, " +"comments, patches, and bug reports (use the package <classname>installation-" +"guide</classname> for bugs, but check first to see if the problem is already " +"reported)." +msgstr "" + +#. Tag: title +#: welcome.xml:585 +#, no-c-format +msgid "About Copyrights and Software Licenses" +msgstr "" + +#. Tag: para +#: welcome.xml:588 +#, no-c-format +msgid "" +"We're sure that you've read some of the licenses that come with most " +"commercial software — they usually say that you can only use one copy " +"of the software on a single computer. This system's license isn't like that " +"at all. We encourage you to put a copy of &debian-gnu; on every computer in " +"your school or place of business. Lend your installation media to your " +"friends and help them install it on their computers! You can even make " +"thousands of copies and <emphasis>sell</emphasis> them — albeit with a " +"few restrictions. Your freedom to install and use the system comes directly " +"from &debian; being based on <emphasis>free software</emphasis>." +msgstr "" + +#. Tag: para +#: welcome.xml:601 +#, no-c-format +msgid "" +"Calling software <emphasis>free</emphasis> doesn't mean that the software " +"isn't copyrighted, and it doesn't mean that installation media containing " +"that software must be distributed at no charge. Free software, in part, " +"means that the licenses of individual programs do not require you to pay for " +"the privilege of distributing or using those programs. Free software also " +"means that not only may anyone extend, adapt, and modify the software, but " +"that they may distribute the results of their work as well." +msgstr "" + +#. Tag: para +#: welcome.xml:612 +#, no-c-format +msgid "" +"The &debian; project, as a pragmatic concession to its users, does make some " +"packages available that do not meet our criteria for being free. These " +"packages are not part of the official distribution, however, and are only " +"available from the <userinput>contrib</userinput> or <userinput>non-free</" +"userinput> areas of &debian; mirrors or on third-party CD/DVD-ROMs; see the " +"<ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>The Debian " +"FTP archives</quote>, for more information about the layout and contents of " +"the archives." +msgstr "" + +#. Tag: para +#: welcome.xml:626 +#, no-c-format +msgid "" +"Many of the programs in the system are licensed under the <emphasis>GNU</" +"emphasis> <emphasis>General Public License</emphasis>, often simply referred " +"to as <quote>the GPL</quote>. The GPL requires you to make the " +"<emphasis>source code</emphasis> of the programs available whenever you " +"distribute a binary copy of the program; that provision of the license " +"ensures that any user will be able to modify the software. Because of this " +"provision, the source code<footnote> <para> For information on how to " +"locate, unpack, and build binaries from &debian; source packages, see the " +"<ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>Basics of " +"the Debian Package Management System</quote>. </para> </footnote> for all " +"such programs is available in the &debian; system." +msgstr "" + +#. Tag: para +#: welcome.xml:645 +#, no-c-format +msgid "" +"There are several other forms of copyright statements and software licenses " +"used on the programs in &debian;. You can find the copyrights and licenses " +"for every package installed on your system by looking in the file <filename>/" +"usr/share/doc/<replaceable>package-name</replaceable>/copyright </filename> " +"once you've installed a package on your system." +msgstr "" + +#. Tag: para +#: welcome.xml:655 +#, no-c-format +msgid "" +"For more information about licenses and how &debian; determines whether " +"software is free enough to be included in the main distribution, see the " +"<ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink>." +msgstr "" + +#. Tag: para +#: welcome.xml:661 +#, no-c-format +msgid "" +"The most important legal notice is that this software comes with " +"<emphasis>no warranties</emphasis>. The programmers who have created this " +"software have done so for the benefit of the community. No guarantee is made " +"as to the suitability of the software for any given purpose. However, since " +"the software is free, you are empowered to modify that software to suit your " +"needs — and to enjoy the benefits of the changes made by others who " +"have extended the software in this way." +msgstr "" |