/[d-i]/trunk/manual/po/pot/using-d-i.pot

Diff of /trunk/manual/po/pot/using-d-i.pot

Parent Directory | Revision Log | View Patch Patch

-revision 38789 by fjp,
Sun Jul  9 14:09:41 2006 UTC
+revision 48723 by faw,
Thu Jul 26 04:05:43 2007 UTC
 Line 1
  # SOME DESCRIPTIVE TITLE.
- # Copyright (C) YEAR Free Software Foundation, Inc.
  # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
  #
  #, fuzzy
  msgid ""
  msgstr ""
  "Project-Id-Version: PACKAGE VERSION\n"
- "POT-Creation-Date: 2006-07-09 14:07+0000\n"
+ "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
+ "POT-Creation-Date: 2007-07-26 04:01+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: application/x-xml2pot; charset=UTF-8\n"
- "Content-Transfer-Encoding: ENCODING\n"
+ "Content-Transfer-Encoding: 8bit\n"
+ #. Tag: title
  #: using-d-i.xml:5
  #, no-c-format
- #. Tag: title
  msgid "Using the Debian Installer"
  msgstr ""
+ #. Tag: title
  #: using-d-i.xml:7
  #, no-c-format
- #. Tag: title
  msgid "How the Installer Works"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:8
  #, no-c-format
- #. Tag: para
  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
- #. Tag: para
  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
- #. Tag: para
  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
- #. Tag: para
  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 (DHCP is used by default if available), you could add the boot parameter <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend=\"installer-args\"/> for available options."
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:42
  #, no-c-format
- #. Tag: para
  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:50
  #, no-c-format
- #. Tag: para
  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:59
  #, no-c-format
- #. Tag: para
  msgid "The normal installer display is character-based (as opposed to the now more familiar graphical interface). The mouse is not operational in this environment. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:77
  #, no-c-format
- #. Tag: para
  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:82
  #, no-c-format
- #. Tag: para
  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:92
  #, no-c-format
- #. Tag: para
  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:106
  #, no-c-format
- #. Tag: title
  msgid "Components Introduction"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:107
  #, no-c-format
- #. Tag: para
  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:118
  #, no-c-format
- #. Tag: term
  msgid "main-menu"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:118
  #, no-c-format
- #. Tag: para
  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:128
  #, no-c-format
- #. Tag: para
+ 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."
- msgid "You can get to the main menu by selecting the <quote>Back</quote> button repeatedly to back all the way out of the currently running component."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:137
  #, no-c-format
- #. Tag: term
  msgid "localechooser"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:137
  #, no-c-format
- #. Tag: para
  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:149
  #, no-c-format
- #. Tag: term
  msgid "kbd-chooser"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:149
  #, no-c-format
- #. Tag: para
  msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:158
  #, no-c-format
- #. Tag: term
  msgid "hw-detect"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:158
  #, no-c-format
- #. Tag: para
  msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:167
  #, no-c-format
- #. Tag: term
  msgid "cdrom-detect"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:167
  #, no-c-format
- #. Tag: para
  msgid "Looks for and mounts a Debian installation CD."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:175
  #, no-c-format
- #. Tag: term
  msgid "netcfg"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:175
  #, no-c-format
- #. Tag: para
  msgid "Configures the computer's network connections so it can communicate over the internet."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:184
  #, no-c-format
- #. Tag: term
  msgid "iso-scan"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:184
  #, no-c-format
- #. Tag: para
  msgid "Looks for ISO file systems, which may be on a CD-ROM or on the hard drive."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:193
  #, no-c-format
- #. Tag: term
  msgid "choose-mirror"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:193
  #, no-c-format
- #. Tag: para
  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:202
  #, no-c-format
- #. Tag: term
  msgid "cdrom-checker"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:202
  #, no-c-format
- #. Tag: para
+ msgid "Checks integrity of a CD-ROM. This way, the user may assure him/herself that the installation CD-ROM was not corrupted."
- msgid "Checks integrity of a CD-ROM. This way the user may assure him/herself that the installation CD-ROM was not corrupted."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:211
  #, no-c-format
- #. Tag: term
  msgid "lowmem"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:211
  #, no-c-format
- #. Tag: para
  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:221
  #, no-c-format
- #. Tag: term
  msgid "anna"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:221
  #, no-c-format
- #. Tag: para
  msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:230
  #, no-c-format
- #. Tag: term
  msgid "partman"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:230
  #, no-c-format
- #. Tag: para
  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:242
  #, no-c-format
- #. Tag: term
  msgid "autopartkit"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:242
  #, no-c-format
- #. Tag: para
  msgid "Automatically partitions an entire disk according to preset user preferences."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:251
  #, no-c-format
- #. Tag: term
  msgid "partitioner"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:251
  #, no-c-format
- #. Tag: para
  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:261
  #, no-c-format
- #. Tag: term
  msgid "partconf"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:261
  #, no-c-format
- #. Tag: para
  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:270
  #, no-c-format
- #. Tag: term
  msgid "lvmcfg"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:270
  #, no-c-format
- #. Tag: para
  msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:279
  #, no-c-format
- #. Tag: term
  msgid "mdcfg"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:279
  #, no-c-format
- #. Tag: para
  msgid "Allows the user to setup Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:290
  #, no-c-format
- #. Tag: term
  msgid "tzsetup"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:290
  #, no-c-format
- #. Tag: para
  msgid "Selects the time zone, based on the location selected earlier."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:298
  #, no-c-format
- #. Tag: term
  msgid "clock-setup"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:298
  #, no-c-format
- #. Tag: para
  msgid "Determines whether the clock is set to UTC or not."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:306
  #, no-c-format
- #. Tag: term
  msgid "user-setup"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:306
  #, no-c-format
- #. Tag: para
  msgid "Sets up the root password, and adds a non-root user."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:314
  #, no-c-format
- #. Tag: term
  msgid "base-installer"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:314
  #, no-c-format
- #. Tag: para
  msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:323
  #, no-c-format
- #. Tag: term
  msgid "apt-setup"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:323
  #, no-c-format
- #. Tag: para
  msgid "Configures apt, mostly automatically, based on what media the installer is running from."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:332
  #, no-c-format
- #. Tag: term
  msgid "pkgsel"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:332
  #, no-c-format
- #. Tag: para
  msgid "Uses <classname>tasksel</classname> to select and install additional software."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:340
  #, no-c-format
- #. Tag: term
  msgid "os-prober"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:340
  #, no-c-format
- #. Tag: para
  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:352
  #, no-c-format
- #. Tag: term
  msgid "bootloader-installer"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:352
  #, no-c-format
- #. Tag: para
  msgid "The various bootloader installers each install a boot loader program on the hard disk, which is necessary for the computer to start up using Linux without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:363
  #, no-c-format
- #. Tag: term
  msgid "shell"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:363
  #, no-c-format
- #. Tag: para
  msgid "Allows the user to execute a shell from the menu, or in the second console."
  msgstr ""
+ #. Tag: term
  #: using-d-i.xml:372
  #, no-c-format
- #. Tag: term
  msgid "save-logs"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:372
  #, no-c-format
- #. Tag: para
  msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to Debian developers later."
  msgstr ""
+ #. Tag: title
  #: using-d-i.xml:390
  #, no-c-format
- #. Tag: title
  msgid "Using Individual Components"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:391
  #, no-c-format
- #. Tag: para
  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:403
  #, no-c-format
- #. Tag: title
  msgid "Setting up Debian Installer and Hardware Configuration"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:404
  #, no-c-format
- #. Tag: para
  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:417
  #, no-c-format
- #. Tag: para
  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: title
  #: using-d-i.xml:432
  #, no-c-format
- #. Tag: title
+ msgid "Check available memory / low memory mode"
- msgid "Check available memory"
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:434
  #, no-c-format
- #. Tag: para
  msgid "One of the first things &d-i; does, is to check available memory. If the available memory is limited, this component will make some changes in the installation process which hopefully will allow you to install &debian; on your system."
  msgstr ""
+ #. Tag: para
  #: using-d-i.xml:441
  #, 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:448
+ #, 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:457
+ #, no-c-format
+ msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64&ndash;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:467
+ #, 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
- msgid "During a low memory install, not all components will be available. One of the limitations is that you won't be able to choose a language for the installation."
+ #: using-d-i.xml:474
+ #, 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 ""
- #: using-d-i.xml:456
+ #. Tag: para
+ #: using-d-i.xml:482
  #, 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:497
+ #, no-c-format
  msgid "Selecting Localization Options"
  msgstr ""
- #: using-d-i.xml:458
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:499
+ #, 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, country and locales."
  msgstr ""
- #: using-d-i.xml:465
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:506
+ #, 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 ""
- #: using-d-i.xml:472
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:513
+ #, no-c-format
  msgid "The selected country will be used later in the installation process to pick the default timezone and a Debian mirror appropriate for your geographic location. Language and country together will be used to set the default locale for your system and to help select your keyboard."
  msgstr ""
- #: using-d-i.xml:479
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:520
+ #, no-c-format
  msgid "You will first be asked to select your preferred language. The language names are listed in both English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
  msgstr ""
- #: using-d-i.xml:491
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:532
+ #, no-c-format
  msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will next be asked to select a country. If you choose <guimenuitem>Other</guimenuitem> at the bottom of the list, you will be presented with a list of all countries, grouped by continent. If the language has only one country associated with it, that country will be selected automatically."
  msgstr ""
- #: using-d-i.xml:509
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:550
+ #, no-c-format
  msgid "A default locale will be selected based on the selected language and country. If you are installing at medium or low priority, you will have the option of selecting a different default locale and of selecting additional locales to be generated for the installed system."
  msgstr ""
- #: using-d-i.xml:524
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:565
+ #, no-c-format
  msgid "Choosing a Keyboard"
  msgstr ""
- #: using-d-i.xml:526
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:567
+ #, 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>kbdconfig</command> as root after you have completed the installation)."
  msgstr ""
- #: using-d-i.xml:536
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:577
+ #, no-c-format
  msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight &mdash; they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration. An 'extended' keyboard is one with <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row."
  msgstr ""
- #: using-d-i.xml:545
- #, no-c-format
  #. Tag: para
- msgid "On DECstations there is currently no loadable keymap available, so you have to skip the keyboard selection and keep the default kernel keymap (LK201 US). This may change in the future as it depends on further Linux/MIPS kernel development."
+ #: using-d-i.xml:586
- msgstr ""
- #: using-d-i.xml:552
  #, no-c-format
- #. Tag: para
+ msgid "On DECstations there is currently no loadable keymap available, so you have to skip the keyboard selection and keep the default kernel keymap (LK201 US). This may change in the future as it depends on further Linux/MIPS kernel development."
- msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar."
  msgstr ""
- #: using-d-i.xml:564
- #, no-c-format
  #. Tag: para
- msgid "If you are installing on a system that has a Sun USB keyboard and have booted the installer with the default 2.4 kernel, the keyboard will not be identified correctly by the installation system. The installer will show you a list of Sun type keymaps to choose from, but selecting one of these will result in a non-working keyboard. If you are installing with the 2.6 kernel, there is no problem."
+ #: using-d-i.xml:593
- msgstr ""
- #: using-d-i.xml:573
  #, no-c-format
- #. Tag: para
+ msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar."
- msgid "To get a working keyboard, you should boot the installer with parameter <userinput>priority=medium</userinput>. When you get to keyboard selection<footnote> <para> If you are installing at default priority you should use the <userinput>Go Back</userinput> button to return to the installer menu when you are shown the list of Sun type keymaps. </para> </footnote>, choose <quote>No keyboard to configure</quote> if you have a keyboard with an American (US) layout, or choose <quote>USB keyboard</quote> if you have a keyboard with a localized layout. Selecting <quote>No keyboard to configure</quote> will leave the kernel keymap in place, which is correct for US keyboards."
  msgstr ""
- #: using-d-i.xml:611
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:623
+ #, no-c-format
  msgid "Looking for the Debian Installer ISO Image"
  msgstr ""
- #: using-d-i.xml:612
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:624
+ #, 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 ""
- #: using-d-i.xml:619
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:631
+ #, no-c-format
  msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid Debian iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
  msgstr ""
- #: using-d-i.xml:636
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:648
+ #, 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 ""
- #: using-d-i.xml:643
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:655
+ #, 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 ""
- #: using-d-i.xml:664
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:676
+ #, no-c-format
  msgid "Configuring Network"
  msgstr ""
- #: using-d-i.xml:666
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:678
+ #, 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 ""
- #: using-d-i.xml:677
- #, no-c-format
  #. Tag: para
- msgid "By default, &d-i; tries to configure your computer's network automatically via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it may be caused by many factors ranging from unplugged network cable, to a misconfigured DHCP setup. Or maybe you don't have a DHCP server in your local network at all. For further explanation check the error messages on the third console. In any case, you will be asked if you want to retry, or if you want to perform manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again."
- msgstr ""
  #: using-d-i.xml:689
  #, no-c-format
+ msgid "By default, &d-i; tries to configure your computer's network automatically via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it may be caused by many factors ranging from unplugged network cable, to a misconfigured DHCP setup. Or maybe you don't have a DHCP server in your local network at all. For further explanation, check the error messages on the fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again."
+ msgstr ""
  #. Tag: para
+ #: using-d-i.xml:701
+ #, 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> and a <computeroutput>WEP key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
  msgstr ""
- #: using-d-i.xml:703
- #, no-c-format
  #. Tag: para
- 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. It will guess the broadcast address is 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 system's guesses &mdash; you can change them once the system has been installed, if necessary, by editing <filename>/etc/network/interfaces</filename>. Alternatively, you can install <classname>etherconf</classname>, which will step you through your network setup."
+ #: using-d-i.xml:715
+ #, 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 &mdash; if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
  msgstr ""
- #: using-d-i.xml:742
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:758
+ #, no-c-format
  msgid "Partitioning and Mount Point Selection"
  msgstr ""
- #: using-d-i.xml:743
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:759
+ #, 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 issues like LVM or RAID devices."
  msgstr ""
- #: using-d-i.xml:765
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:781
+ #, no-c-format
  msgid "Partitioning Your Disks"
  msgstr ""
- #: using-d-i.xml:767
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:783
+ #, no-c-format
  msgid "Now it is time to partition your disks. If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
  msgstr ""
- #: using-d-i.xml:773
- #, no-c-format
  #. Tag: para
- msgid "First you will be given the opportunity to automatically partition either an entire drive, or free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manually edit partition table</guimenuitem> from the menu."
+ #: using-d-i.xml:790
+ #, 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/hd<replaceable>X</replaceable> bs=512 count=2; sync\n"
+       "</screen></informalexample> Note that this will make any existing data on that disk inaccessible."
  msgstr ""
- #: using-d-i.xml:781
- #, no-c-format
  #. Tag: para
- msgid "If you choose guided partitioning, you may have two options: to create partitions directly on the hard disk (classic method) or to use Logical Volume Management (LVM). In the second case, 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. Note: the option to use LVM may not be available on all architectures."
+ #: using-d-i.xml:803
+ #, 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 ""
- #: using-d-i.xml:790
- #, no-c-format
  #. Tag: para
- msgid "After you choose guided partitioning (either classic or using LVM), 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."
+ #: using-d-i.xml:810
+ #, 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 ""
- #: using-d-i.xml:807
+ #. Tag: para
+ #: using-d-i.xml:825
  #, no-c-format
- #. Tag: entry
+ msgid "The option to use (encrypted) LVM may not be available on all architectures."
- msgid "Partitioning scheme"
  msgstr ""
- #: using-d-i.xml:808
+ #. Tag: para
+ #: using-d-i.xml:830
  #, no-c-format
- #. Tag: entry
+ 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."
- msgid "Minimum space"
  msgstr ""
- #: using-d-i.xml:809
+ #. Tag: para
+ #: using-d-i.xml:839
  #, no-c-format
- #. Tag: entry
+ 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."
- msgid "Created partitions"
  msgstr ""
- #: using-d-i.xml:815
+ #. Tag: para
+ #: using-d-i.xml:848
  #, no-c-format
- #. Tag: entry
+ 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."
- msgid "All files in one partition"
  msgstr ""
- #: using-d-i.xml:816
+ #. Tag: para
+ #: using-d-i.xml:858
  #, no-c-format
+ msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
+ msgstr ""
+ #. Tag: para
+ #: using-d-i.xml:867
+ #, 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. 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."
+ msgstr ""
+ #. Tag: para
+ #: using-d-i.xml:875
+ #, 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
- msgid "600MB"
+ #: using-d-i.xml:891
+ #, no-c-format
+ msgid "Partitioning scheme"
  msgstr ""
- #: using-d-i.xml:817
+ #. Tag: entry
+ #: using-d-i.xml:892
  #, no-c-format
+ msgid "Minimum space"
+ msgstr ""
  #. Tag: entry
- msgid "<filename>/</filename>, swap"
+ #: using-d-i.xml:893
+ #, no-c-format
+ msgid "Created partitions"
  msgstr ""
- #: using-d-i.xml:819
+ #. Tag: entry
+ #: using-d-i.xml:899
  #, no-c-format
+ msgid "All files in one partition"
+ msgstr ""
  #. Tag: entry
- msgid "Separate /home partition"
+ #: using-d-i.xml:900
+ #, no-c-format
+ msgid "600MB"
  msgstr ""
- #: using-d-i.xml:820
+ #. Tag: entry
+ #: using-d-i.xml:901
  #, no-c-format
+ msgid "<filename>/</filename>, swap"
+ msgstr ""
  #. Tag: entry
- msgid "500MB"
+ #: using-d-i.xml:903
+ #, no-c-format
+ msgid "Separate /home partition"
  msgstr ""
- #: using-d-i.xml:821
+ #. Tag: entry
+ #: using-d-i.xml:904
  #, no-c-format
+ msgid "500MB"
+ msgstr ""
  #. Tag: entry
+ #: using-d-i.xml:905
+ #, no-c-format
  msgid "<filename>/</filename>, <filename>/home</filename>, swap"
  msgstr ""
- #: using-d-i.xml:825
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:909
+ #, no-c-format
  msgid "Separate /home, /usr, /var and /tmp partitions"
  msgstr ""
- #: using-d-i.xml:826
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:910
+ #, no-c-format
  msgid "<entry>1GB</entry>"
  msgstr ""
- #: using-d-i.xml:827
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:911
+ #, no-c-format
  msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
  msgstr ""
- #: using-d-i.xml:836
- #, no-c-format
  #. Tag: para
- msgid "If you choose guided partitioning using LVM, the installer will also create a separate /boot partition. The other partitions, except for the swap partition, will be created inside the LVM partition."
+ #: using-d-i.xml:920
+ #, 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 ""
- #: using-d-i.xml:842
- #, no-c-format
  #. Tag: para
- msgid "If you choose guided partitioning for your IA64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
+ #: using-d-i.xml:926
+ #, no-c-format
+ msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition."
  msgstr ""
- #: using-d-i.xml:850
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:934
+ #, no-c-format
  msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader."
  msgstr ""
- #: using-d-i.xml:856
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:940
+ #, 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 ""
- #: using-d-i.xml:862
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:946
+ #, no-c-format
  msgid ""
        "The list of partitions might look like this: <informalexample><screen>\n"
        "  IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
-Line 778 
 msgid ""
+Line 841 
 msgid ""
        "        #7 logical  498.8 MB      ext3\n"
        "        #8 logical  551.5 MB      swap       swap\n"
        "        #9 logical   65.8 GB      ext2\n"
-       "</screen></informalexample> This example shows two IDE harddrives 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)."
+       "</screen></informalexample> This example shows two IDE harddrives 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 ""
- #: using-d-i.xml:875
- #, no-c-format
  #. Tag: para
- 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><footnote> <para> If you selected guided partitioning using LVM, you will not be able to undo all changes made as some changes will already have been committed to the hard disk. The installer will warn you before that happens though. </para> </footnote> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
+ #: using-d-i.xml:959
+ #, 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 ""
- #: using-d-i.xml:895
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:969
+ #, 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 setup your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section."
  msgstr ""
- #: using-d-i.xml:903
- #, no-c-format
  #. Tag: para
- msgid "If you select a pristine disk which doesn't have neither partitions nor free space on it, you will be offered to create a new partition table (this is needed so you can create new partitions). After this a new line entitled <quote>FREE SPACE</quote> should appear under the selected disk."
+ #: using-d-i.xml:977
- msgstr ""
- #: using-d-i.xml:911
  #, no-c-format
- #. Tag: para
+ 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."
- msgid "If you select some free space, you will be offered to create 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 detailed overview of your new partition. There are options like mountpoint, mount options, bootable flag, or way of usage. 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 different filesystem for this partition including the possibility to use the partition for swap, software RAID, LVM, or not use it at all. Other nice feature is the possibility to copy data from existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will be thrown back to <command>partman</command>'s main screen."
  msgstr ""
- #: using-d-i.xml:929
- #, no-c-format
  #. Tag: para
- 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. Because this is the same screen like when creating a new partition, you can change the same set of options. One thing which might 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."
+ #: using-d-i.xml:985
- msgstr ""
- #: using-d-i.xml:940
  #, no-c-format
- #. Tag: para
+ msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
- 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 ""
- #: using-d-i.xml:948
- #, no-c-format
  #. Tag: para
- msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
+ #: using-d-i.xml:1007
- msgstr ""
- #: using-d-i.xml:954
  #, no-c-format
- #. Tag: para
+ 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."
- 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 ""
- #: using-d-i.xml:962
- #, no-c-format
  #. Tag: para
- 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."
+ #: using-d-i.xml:1018
- msgstr ""
- #: using-d-i.xml:990
  #, no-c-format
- #. Tag: title
+ 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."
- msgid "Configuring Logical Volume Manager (LVM)"
  msgstr ""
- #: using-d-i.xml:991
- #, no-c-format
  #. Tag: para
- msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc."
+ #: using-d-i.xml:1026
- msgstr ""
- #: using-d-i.xml:999
  #, no-c-format
- #. Tag: para
+ msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one."
- 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 disc (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 discs."
  msgstr ""
- #: using-d-i.xml:1009
- #, no-c-format
  #. Tag: para
- msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disc 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 &mdash; 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>."
+ #: using-d-i.xml:1032
- msgstr ""
- #: using-d-i.xml:1020
  #, no-c-format
- #. Tag: para
+ 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>)."
- msgid "LVM setup in &d-i; is quite simple. At first, you have to mark your partitions to be used as physical volumes for LVM. (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 LVM</guimenuitem> </menuchoice>.) Then start the <command>lvmcfg</command> module (either directly from <command>partman</command> or from the &d-i;'s main menu) and combine physical volumes to volume group(s) under the <guimenuitem>Modify volume groups (VG)</guimenuitem> menu. After that, you should create logical volumes on the top of volume groups from the menu <guimenuitem>Modify logical volumes (LV)</guimenuitem>."
  msgstr ""
- #: using-d-i.xml:1035
- #, no-c-format
  #. Tag: para
- msgid "After returning from <command>lvmcfg</command> back to <command>partman</command>, you will see any created logical volumes in the same way as ordinary partitions (and you should treat them like that)."
+ #: using-d-i.xml:1040
+ #, 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 ""
- #: using-d-i.xml:1050
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:1068
+ #, no-c-format
  msgid "Configuring Multidisk Device (Software RAID)"
  msgstr ""
- #: using-d-i.xml:1051
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1069
+ #, no-c-format
  msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
  msgstr ""
- #: using-d-i.xml:1065
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1083
+ #, 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 ""
- #: using-d-i.xml:1073
- #, no-c-format
  #. Tag: para
- msgid "The benefit you gain depends on a type of a 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 loose <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 incomming data into stripes and distributes them equally on all but one disks (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 similar degree of reliability like RAID1 while achieving less redundancy. On the other hand it might be a bit slower on write operation than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:"
+ #: using-d-i.xml:1091
+ #, 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> </variablelist> To sum it up:"
  msgstr ""
- #: using-d-i.xml:1151
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1169
+ #, no-c-format
  msgid "Type"
  msgstr ""
- #: using-d-i.xml:1152
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1170
+ #, no-c-format
  msgid "Minimum Devices"
  msgstr ""
- #: using-d-i.xml:1153
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1171
+ #, no-c-format
  msgid "Spare Device"
  msgstr ""
- #: using-d-i.xml:1154
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1172
+ #, no-c-format
  msgid "Survives disk failure?"
  msgstr ""
- #: using-d-i.xml:1155
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1173
+ #, no-c-format
  msgid "Available Space"
  msgstr ""
- #: using-d-i.xml:1161
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1179
+ #, no-c-format
  msgid "RAID0"
  msgstr ""
- #: using-d-i.xml:1162 using-d-i.xml:1170
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1180 using-d-i.xml:1188
+ #, no-c-format
  msgid "<entry>2</entry>"
  msgstr ""
- #: using-d-i.xml:1163 using-d-i.xml:1164
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1181 using-d-i.xml:1182
+ #, no-c-format
  msgid "<entry>no</entry>"
  msgstr ""
- #: using-d-i.xml:1165
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1183
+ #, no-c-format
  msgid "Size of the smallest partition multiplied by number of devices in RAID"
  msgstr ""
- #: using-d-i.xml:1169
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1187
+ #, no-c-format
  msgid "RAID1"
  msgstr ""
- #: using-d-i.xml:1171 using-d-i.xml:1179
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1189 using-d-i.xml:1197
+ #, no-c-format
  msgid "optional"
  msgstr ""
- #: using-d-i.xml:1172 using-d-i.xml:1180
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1190 using-d-i.xml:1198
+ #, no-c-format
  msgid "<entry>yes</entry>"
  msgstr ""
- #: using-d-i.xml:1173
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1191
+ #, no-c-format
  msgid "Size of the smallest partition in RAID"
  msgstr ""
- #: using-d-i.xml:1177
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1195
+ #, no-c-format
  msgid "RAID5"
  msgstr ""
- #: using-d-i.xml:1178
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1196
+ #, no-c-format
  msgid "<entry>3</entry>"
  msgstr ""
- #: using-d-i.xml:1181
- #, no-c-format
  #. Tag: entry
+ #: using-d-i.xml:1199
+ #, no-c-format
  msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
  msgstr ""
- #: using-d-i.xml:1189
- #, no-c-format
  #. Tag: para
- msgid "If you want to know the whole truth about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
+ #: using-d-i.xml:1207
+ #, 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 ""
- #: using-d-i.xml:1194
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1212
+ #, no-c-format
  msgid "To create a MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
  msgstr ""
- #: using-d-i.xml:1203
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1221
+ #, no-c-format
  msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) filesystem. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
  msgstr ""
- #: using-d-i.xml:1212
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1230
+ #, 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>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected."
  msgstr ""
- #: using-d-i.xml:1225
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1243
+ #, no-c-format
  msgid "RAID0 is simple &mdash; 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 ""
- #: using-d-i.xml:1232
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1250
+ #, 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 few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue."
  msgstr ""
- #: using-d-i.xml:1244
+ #. Tag: para
+ #: using-d-i.xml:1262
  #, no-c-format
+ msgid "RAID5 has a similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
+ msgstr ""
  #. Tag: para
- msgid "RAID5 has similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
+ #: using-d-i.xml:1270
+ #, 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:1279
+ #, no-c-format
+ msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
  msgstr ""
- #: using-d-i.xml:1252
+ #. Tag: title
+ #: using-d-i.xml:1294
  #, no-c-format
+ msgid "Configuring the Logical Volume Manager (LVM)"
+ msgstr ""
  #. Tag: para
- 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 first partitions on all three disk 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>)."
+ #: using-d-i.xml:1295
+ #, 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 with moving stuff around, symlinking, etc."
  msgstr ""
- #: using-d-i.xml:1261
+ #. Tag: para
+ #: using-d-i.xml:1303
  #, 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
- msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
+ #: using-d-i.xml:1313
+ #, 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 &mdash; 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 ""
- #: using-d-i.xml:1276
+ #. Tag: para
+ #: using-d-i.xml:1324
  #, no-c-format
- #. Tag: title
+ 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>."
- msgid "Configuring Encrypted Volumes"
  msgstr ""
- #: using-d-i.xml:1277
+ #. Tag: para
+ #: using-d-i.xml:1333
  #, 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
- 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."
+ #: using-d-i.xml:1344
+ #, 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:1349
+ #, no-c-format
+ msgid "Create volume group"
+ msgstr ""
+ #. Tag: guimenuitem
+ #: using-d-i.xml:1352
+ #, no-c-format
+ msgid "Create logical volume"
+ msgstr ""
+ #. Tag: guimenuitem
+ #: using-d-i.xml:1355
+ #, no-c-format
+ msgid "Delete volume group"
+ msgstr ""
+ #. Tag: guimenuitem
+ #: using-d-i.xml:1358
+ #, no-c-format
+ msgid "Delete logical volume"
  msgstr ""
- #: using-d-i.xml:1289
+ #. Tag: guimenuitem
+ #: using-d-i.xml:1361
  #, no-c-format
+ msgid "Extend volume group"
+ msgstr ""
+ #. Tag: guimenuitem
+ #: using-d-i.xml:1364
+ #, no-c-format
+ msgid "Reduce volume group"
+ msgstr ""
  #. Tag: para
- msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
+ #: using-d-i.xml:1366
+ #, no-c-format
+ msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
  msgstr ""
- #: using-d-i.xml:1304
+ #. Tag: para
+ #: using-d-i.xml:1372
  #, 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
- 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."
+ #: using-d-i.xml:1377
+ #, 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 ""
- #: using-d-i.xml:1311
+ #. Tag: title
+ #: using-d-i.xml:1391
  #, no-c-format
+ msgid "Configuring Encrypted Volumes"
+ msgstr ""
  #. Tag: para
- 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 setting</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."
+ #: using-d-i.xml:1392
+ #, 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 ""
- #: using-d-i.xml:1322
+ #. Tag: para
+ #: using-d-i.xml:1404
  #, 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. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
+ msgstr ""
  #. Tag: para
- msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
+ #: using-d-i.xml:1419
+ #, 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 ""
- #: using-d-i.xml:1334
+ #. Tag: para
+ #: using-d-i.xml:1426
  #, 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
- msgid "First, let's have a look at available options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
+ #: using-d-i.xml:1437
+ #, no-c-format
+ msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
  msgstr ""
- #: using-d-i.xml:1344
+ #. Tag: para
+ #: using-d-i.xml:1449
  #, no-c-format
+ msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
+ msgstr ""
  #. Tag: term
+ #: using-d-i.xml:1459
+ #, no-c-format
  msgid "Encryption: <userinput>aes</userinput>"
  msgstr ""
- #: using-d-i.xml:1346
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1461
+ #, 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 ""
- #: using-d-i.xml:1364
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1479
+ #, no-c-format
  msgid "Key size: <userinput>256</userinput>"
  msgstr ""
- #: using-d-i.xml:1366
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1481
+ #, 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 ""
- #: using-d-i.xml:1378
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1493
+ #, no-c-format
  msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>"
  msgstr ""
- #: using-d-i.xml:1380
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1495
+ #, 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 ""
- #: using-d-i.xml:1390
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1505
+ #, no-c-format
  msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
  msgstr ""
- #: using-d-i.xml:1402
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1517
+ #, no-c-format
  msgid "Encryption key: <userinput>Passphrase</userinput>"
  msgstr ""
- #: using-d-i.xml:1404
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1519
+ #, no-c-format
  msgid "Here you can choose the type of the encryption key for this partition."
  msgstr ""
- #: using-d-i.xml:1410
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1525
+ #, no-c-format
  msgid "Passphrase"
  msgstr ""
- #: using-d-i.xml:1411
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1526
+ #, 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 ""
- #: using-d-i.xml:1426 using-d-i.xml:1519
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1541 using-d-i.xml:1634
+ #, no-c-format
  msgid "Random key"
  msgstr ""
- #: using-d-i.xml:1427
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1542
+ #, 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 ""
- #: using-d-i.xml:1436
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1551
+ #, 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 ""
- #: using-d-i.xml:1455 using-d-i.xml:1532
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1570 using-d-i.xml:1647
+ #, no-c-format
  msgid "Erase data: <userinput>yes</userinput>"
  msgstr ""
- #: using-d-i.xml:1457
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1572
+ #, 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 ""
- #: using-d-i.xml:1477
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1592
+ #, no-c-format
  msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
  msgstr ""
- #: using-d-i.xml:1486
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1601
+ #, no-c-format
  msgid "Encryption: <userinput>AES256</userinput>"
  msgstr ""
- #: using-d-i.xml:1488
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1603
+ #, no-c-format
  msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
  msgstr ""
- #: using-d-i.xml:1498
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1613
+ #, no-c-format
  msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>"
  msgstr ""
- #: using-d-i.xml:1500
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1615
+ #, no-c-format
  msgid "Here you can select the type of the encryption key for this partition."
  msgstr ""
- #: using-d-i.xml:1506
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:1621
+ #, no-c-format
  msgid "Keyfile (GnuPG)"
  msgstr ""
- #: using-d-i.xml:1507
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1622
+ #, no-c-format
  msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
  msgstr ""
- #: using-d-i.xml:1520
- #, no-c-format
  #. Tag: para
- msgid "Please see the the section on random keys above."
+ #: using-d-i.xml:1635
+ #, no-c-format
+ msgid "Please see the section on random keys above."
  msgstr ""
- #: using-d-i.xml:1534
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1649
+ #, no-c-format
  msgid "Please see the the section on erasing data above."
  msgstr ""
- #: using-d-i.xml:1543
- #, no-c-format
  #. Tag: para
- msgid "Please note that the <emphasis>graphical</emphasis> version of the installer still has some limitations when compared to the textual one. For cryptography it means you can set up only volumes using <emphasis>passphrases</emphasis> as the encryption keys."
+ #: using-d-i.xml:1659
+ #, no-c-format
+ msgid "Please note that the <emphasis>graphical</emphasis> version of the installer still has some limitations when compared to the textual one. For cryptography it means you can set up only volumes using a <emphasis>passphrase</emphasis> as the encryption key."
  msgstr ""
- #: using-d-i.xml:1550
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1667
+ #, 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 ""
- #: using-d-i.xml:1561
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1677
+ #, 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 ""
- #: using-d-i.xml:1570
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1686
+ #, 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 ""
- #: using-d-i.xml:1583
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1699
+ #, 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 ""
- #: using-d-i.xml:1599
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1715
+ #, 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 two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
-       "Encrypted volume (<replaceable>crypt0</replaceable>) - 115.1 GB Linux device-mapper\n"
+       "Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper\n"
        "     #1 115.1 GB  F ext3\n"
        "\n"
        "Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile\n"
-Line 1280 
 msgid ""
+Line 1403 
 msgid ""
        "</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 ""
- #: using-d-i.xml:1612
- #, no-c-format
  #. Tag: para
- msgid "One thing to note here are the identifiers in parentheses (<replaceable>crypt0</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
+ #: using-d-i.xml:1728
+ #, no-c-format
+ msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
  msgstr ""
- #: using-d-i.xml:1622
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1738
+ #, no-c-format
  msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
  msgstr ""
- #: using-d-i.xml:1633
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:1749
+ #, no-c-format
  msgid "Setting up the System"
  msgstr ""
- #: using-d-i.xml:1634
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1750
+ #, no-c-format
  msgid "After partitioning the installer asks a few more questions that will be used to set up the system it is about to install."
  msgstr ""
- #: using-d-i.xml:1646
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:1762
+ #, no-c-format
  msgid "Configuring Your Time Zone"
  msgstr ""
- #: using-d-i.xml:1648
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1764
+ #, no-c-format
  msgid "Depending on the location selected at the beginning of the installation process, you might be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone."
  msgstr ""
- #: using-d-i.xml:1664
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:1780
+ #, no-c-format
  msgid "Configuring the Clock"
  msgstr ""
- #: using-d-i.xml:1666
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1782
+ #, no-c-format
  msgid "The installer might 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 ""
- #: using-d-i.xml:1673
- #, no-c-format
  #. Tag: para
- msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> <phrase arch=\"i386\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase>"
+ #: using-d-i.xml:1789
+ #, 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=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase>"
  msgstr ""
- #: using-d-i.xml:1684
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1800
+ #, no-c-format
  msgid "Note that the installer does not currently allow you to actually set the time in the computer's clock. You can set the clock to the current time after you have installed, if it is incorrect or if it was previously not set to UTC."
  msgstr ""
- #: using-d-i.xml:1700
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:1816
+ #, no-c-format
  msgid "Setting Up Users And Passwords"
  msgstr ""
- #: using-d-i.xml:1703
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:1819
+ #, no-c-format
  msgid "Set the Root Password"
  msgstr ""
- #: using-d-i.xml:1705
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1823
+ #, 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 ""
- #: using-d-i.xml:1713
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1831
+ #, 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 ""
- #: using-d-i.xml:1721
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1839
+ #, 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 ""
- #: using-d-i.xml:1731
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:1849
+ #, no-c-format
  msgid "Create an Ordinary User"
  msgstr ""
- #: using-d-i.xml:1733
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1851
+ #, 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 ""
- #: using-d-i.xml:1740
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1860
+ #, 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 &mdash; 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 &mdash; consider reading one if it is new to you."
  msgstr ""
- #: using-d-i.xml:1750
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1870
+ #, 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 ""
- #: using-d-i.xml:1757
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1877
+ #, no-c-format
  msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
  msgstr ""
- #: using-d-i.xml:1769
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:1889
+ #, no-c-format
  msgid "Installing the Base System"
  msgstr ""
- #: using-d-i.xml:1770
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1890
+ #, 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 ""
- #: using-d-i.xml:1784
+ #. Tag: para
+ #: using-d-i.xml:1903
  #, no-c-format
- #. Tag: title
+ 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>."
- msgid "Base System Installation"
  msgstr ""
- #: using-d-i.xml:1786
- #, no-c-format
  #. Tag: para
- msgid "During the Base installation, 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>."
+ #: using-d-i.xml:1912
- msgstr ""
- #: using-d-i.xml:1796
  #, no-c-format
- #. Tag: para
+ 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."
- msgid "The unpack/setup messages generated by the base installation are saved in <filename>/var/log/syslog</filename> when the installation is performed over a serial console."
  msgstr ""
- #: using-d-i.xml:1802
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:1918
+ #, no-c-format
  msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
  msgstr ""
- #: using-d-i.xml:1815
- #, no-c-format
  #. Tag: title
- msgid "Installing Additional Software"
+ #: using-d-i.xml:1930
- msgstr ""
- #: using-d-i.xml:1816
- #, no-c-format
- #. Tag: para
- msgid "After the base system is installed, you have a usable but limited system. Most users will want to add additional software to the system to tune it to their needs, and the installer lets you do so. This step can take even longer than installing the base system if you have a slow computer or network."
- msgstr ""
- #: using-d-i.xml:1830
  #, no-c-format
- #. Tag: title
+ msgid "Installing Additional Software"
- msgid "Configuring apt"
  msgstr ""
- #: using-d-i.xml:1832
- #, no-c-format
  #. Tag: para
- msgid "The main means that people use to install packages on their system is via a program called <command>apt-get</command>, from the <classname>apt</classname> package.<footnote> <para> Note that the actual program that installs packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool as it will invoke <command>dpkg</command> as appropriate and also because it knows to install other packages which are required for the package you're trying to install, as well as how to retrieve the package from your CD, the network, or wherever. </para> </footnote> Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command> are also in use and depend on <command>apt-get</command>. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface."
+ #: using-d-i.xml:1931
- msgstr ""
- #: using-d-i.xml:1856
  #, no-c-format
- #. Tag: para
+ msgid "After the base system is installed, 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."
- msgid "<command>apt</command> must be configured so that it knows where to retrieve packages from. The installer largely takes care of this automatically based on what it knows about your installation medium. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>, and you can examine and edit it to your liking after the install is complete."
  msgstr ""
- #: using-d-i.xml:1872
- #, no-c-format
  #. Tag: title
- msgid "Selecting and Installing Software"
+ #: using-d-i.xml:1945
- msgstr ""
- #: using-d-i.xml:1874
- #, no-c-format
- #. Tag: para
- 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 ""
- #: using-d-i.xml:1883
- #, no-c-format
- #. Tag: para
- msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install (or remove) more packages, 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 ""
- #: using-d-i.xml:1908
  #, no-c-format
- #. Tag: para
+ msgid "Configuring apt"
- msgid "Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this point, <command>aptitude</command> will install the packages you've selected."
  msgstr ""
- #: using-d-i.xml:1915
- #, no-c-format
  #. Tag: para
- msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
+ #: using-d-i.xml:1947
- msgstr ""
- #: using-d-i.xml:1922
  #, no-c-format
- #. Tag: para
+ msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
- msgid "Note that some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can un-select the tasks. You can even opt to install no tasks at all at this point."
  msgstr ""
- #: using-d-i.xml:1930
- #, no-c-format
  #. Tag: para
- msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process."
+ #: using-d-i.xml:1973
- msgstr ""
- #: using-d-i.xml:1939
  #, no-c-format
- #. Tag: title
+ msgid "<command>apt</command> must be configured so that it knows where to retrieve packages from. The installer largely takes care of this automatically based on what it knows about your installation medium. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>, and you can examine and edit it to your liking after the install is complete."
- msgid "Configuring Your Mail Transport Agent"
  msgstr ""
- #: using-d-i.xml:1941
+ #. Tag: title
+ #: using-d-i.xml:1989
  #, no-c-format
- #. Tag: para
+ msgid "Selecting and Installing Software"
- msgid "Today, email is a very important part of many people's life, so it's no surprise Debian lets you configure your mail system right as a part of the installation process. The standard mail transport agent in Debian is <command>exim4</command>, which is relatively small, flexible, and easy to learn."
  msgstr ""
- #: using-d-i.xml:1949
- #, no-c-format
  #. Tag: para
- msgid "You may ask if this is needed even if your computer is not connected to any network. The short answer is: Yes. The longer explanation: Some system utilities (like <command>cron</command>, <command>quota</command>, <command>aide</command>, &hellip;) may send you important notices via email."
+ #: using-d-i.xml:1991
+ #, 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 ""
- #: using-d-i.xml:1957
- #, no-c-format
  #. Tag: para
- msgid "So on the first screen you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs:"
+ #: using-d-i.xml:2000
+ #, no-c-format
+ msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
  msgstr ""
- #: using-d-i.xml:1966
+ #. Tag: para
+ #: using-d-i.xml:2027
  #, no-c-format
- #. Tag: term
+ msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can un-select the tasks. You can even opt to install no tasks at all at this point."
- msgid "internet site"
  msgstr ""
- #: using-d-i.xml:1967
- #, no-c-format
  #. Tag: para
- 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."
+ #: using-d-i.xml:2034
+ #, no-c-format
+ msgid "The <quote>Desktop environment</quote> task will install the GNOME desktop environment. The options offered by the installer currently do not allow to select a different desktop environment such as for example KDE."
  msgstr ""
- #: using-d-i.xml:1978
+ #. Tag: para
+ #: using-d-i.xml:2042
  #, no-c-format
- #. Tag: term
+ msgid "It is possible to get the installer to install KDE by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding <literal>tasks=\"standard, kde-desktop\"</literal> at the boot prompt when starting the installer<footnote> <para> A more lightweight Xfce desktop environment can be selected by using <literal>xfce-desktop</literal> instead of <literal>kde-desktop</literal>. If you are installing on a laptop, you could also add <literal>laptop</literal> to the tasks to be installed. </para> </footnote>. However, this will only work if the packages needed for KDE are actually available. If you are installing using a full CD image, they will need to be downloaded from a mirror as KDE packages are not included on the first full CD; installing KDE this way should work fine if you are using a DVD image or any other installation method."
- msgid "mail sent by smarthost"
  msgstr ""
- #: using-d-i.xml:1979
- #, no-c-format
  #. Tag: para
- msgid "In this scenario is your outgoing mail forwarded to another machine, called a <quote>smarthost</quote>, which does the actual job for you. 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. This option is suitable for dial-up users."
+ #: using-d-i.xml:2062
+ #, no-c-format
+ msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache</classname>."
  msgstr ""
- #: using-d-i.xml:1992
+ #. Tag: para
+ #: using-d-i.xml:2074
  #, no-c-format
- #. Tag: term
+ msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected."
- msgid "local delivery only"
  msgstr ""
- #: using-d-i.xml:1993
- #, no-c-format
  #. Tag: para
- msgid "Your system is not on a network and mail is sent or received only between local users. Even if you don't plan to send any messages, this option is highly recommended, because some system utilities may send you various alerts from time to time (e.g. beloved <quote>Disk quota exceeded</quote>). This option is also convenient for new users, because it doesn't ask any further questions."
+ #: using-d-i.xml:2081
+ #, 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 ""
- #: using-d-i.xml:2006
+ #. Tag: para
+ #: using-d-i.xml:2087
  #, no-c-format
- #. Tag: term
+ 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."
- msgid "no configuration at this time"
  msgstr ""
- #: using-d-i.xml:2007
- #, no-c-format
  #. Tag: para
- msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system &mdash; 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."
+ #: using-d-i.xml:2096
+ #, 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 ""
- #: using-d-i.xml:2018
- #, no-c-format
  #. Tag: para
- msgid "If none of these scenarios suits your needs, or if you need a finer setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <command>exim4</command> may be found under <filename>/usr/share/doc/exim4</filename>."
+ #: using-d-i.xml:2105
+ #, no-c-format
+ msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process."
  msgstr ""
- #: using-d-i.xml:2033
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2118
+ #, no-c-format
  msgid "Making Your System Bootable"
  msgstr ""
- #: using-d-i.xml:2035
- #, no-c-format
  #. Tag: para
- 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 the OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
+ #: using-d-i.xml:2120
- msgstr ""
- #: using-d-i.xml:2043
  #, no-c-format
- #. Tag: para
+ 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>"
- msgid "Note that multiple operating systems booting on a single machine is still something of a black art. This document does not even attempt to document the various boot managers, which vary by architecture and even by subarchitecture. You should see your boot manager's documentation for more information."
  msgstr ""
- #: using-d-i.xml:2058
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2135
+ #, no-c-format
  msgid "Detecting other operating systems"
  msgstr ""
- #: using-d-i.xml:2060
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2137
+ #, 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 ""
- #: using-d-i.xml:2068
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2145
+ #, 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 ""
- #: using-d-i.xml:2086
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2163
+ #, no-c-format
  msgid "Install <command>aboot</command> on a Hard Disk"
  msgstr ""
- #: using-d-i.xml:2087
- #, no-c-format
  #. Tag: para
- msgid "If you have booted from SRM, if you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful &mdash; it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead."
+ #: using-d-i.xml:2164
+ #, no-c-format
+ msgid "If you have booted from SRM and you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful &mdash; it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead."
  msgstr ""
- #: using-d-i.xml:2107
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2184
+ #, no-c-format
  msgid "<command>palo</command>-installer"
  msgstr ""
- #: using-d-i.xml:2108
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2185
+ #, 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 ""
- #: using-d-i.xml:2117
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2194
+ #, no-c-format
  msgid "hppa FIXME ( need more info )"
  msgstr ""
- #: using-d-i.xml:2129
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2206
+ #, no-c-format
  msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
  msgstr ""
- #: using-d-i.xml:2131
- #, no-c-format
  #. Tag: para
- msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for newbies and old hands alike."
+ #: using-d-i.xml:2208
+ #, 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 ""
- #: using-d-i.xml:2137
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2214
+ #, no-c-format
  msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
  msgstr ""
- #: using-d-i.xml:2143
- #, no-c-format
  #. Tag: para
- msgid "If you do not want to install grub at all, use the Back button to get to the main menu, and from there select whatever bootloader you would like to use."
+ #: using-d-i.xml:2220
+ #, 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 ""
- #: using-d-i.xml:2157
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2233
+ #, no-c-format
  msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
  msgstr ""
- #: using-d-i.xml:2159
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2235
+ #, no-c-format
  msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
  msgstr ""
- #: using-d-i.xml:2169
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2245
+ #, no-c-format
  msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
  msgstr ""
- #: using-d-i.xml:2177
- #, no-c-format
  #. Tag: para
- msgid "&d-i; presents you three choices where to install the <command>LILO</command> boot loader:"
+ #: using-d-i.xml:2253
+ #, no-c-format
+ msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
  msgstr ""
- #: using-d-i.xml:2184
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:2260
+ #, no-c-format
  msgid "Master Boot Record (MBR)"
  msgstr ""
- #: using-d-i.xml:2184
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2260
+ #, no-c-format
  msgid "This way the <command>LILO</command> will take complete control of the boot process."
  msgstr ""
- #: using-d-i.xml:2191
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:2267
+ #, no-c-format
  msgid "new Debian partition"
  msgstr ""
- #: using-d-i.xml:2191
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2267
+ #, no-c-format
  msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader."
  msgstr ""
- #: using-d-i.xml:2200
- #, no-c-format
  #. Tag: term
+ #: using-d-i.xml:2276
+ #, no-c-format
  msgid "Other choice"
  msgstr ""
- #: using-d-i.xml:2200
- #, no-c-format
  #. Tag: para
- msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
+ #: using-d-i.xml:2276
+ #, no-c-format
+ msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use <phrase condition=\"etch\">devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names,</phrase> <phrase condition=\"lenny\">traditional device names</phrase> such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
  msgstr ""
- #: using-d-i.xml:2212
- #, no-c-format
  #. Tag: para
- msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into Debian! For more information on this please read <xref linkend=\"reactivating-win\"/>."
+ #: using-d-i.xml:2290
+ #, no-c-format
+ msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record &mdash; however, this means that you'll need to use some other way to get back into Debian!"
  msgstr ""
- #: using-d-i.xml:2229
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2306
+ #, no-c-format
  msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
  msgstr ""
- #: using-d-i.xml:2231
- #, no-c-format
  #. Tag: para
- 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 file 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 actually do the work of loading and starting the Linux kernel."
+ #: using-d-i.xml:2308
+ #, 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 ""
- #: using-d-i.xml:2247
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2324
+ #, 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 ""
- #: using-d-i.xml:2259
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2336
+ #, no-c-format
  msgid "Choose the correct partition!"
  msgstr ""
- #: using-d-i.xml:2261
- #, no-c-format
  #. Tag: para
- msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, the <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
+ #: using-d-i.xml:2338
+ #, no-c-format
+ msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
  msgstr ""
- #: using-d-i.xml:2276
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2353
+ #, no-c-format
  msgid "EFI Partition Contents"
  msgstr ""
- #: using-d-i.xml:2278
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2355
+ #, 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 ""
- #: using-d-i.xml:2300
- #, no-c-format
  #. Tag: filename
+ #: using-d-i.xml:2377
+ #, no-c-format
  msgid "elilo.conf"
  msgstr ""
- #: using-d-i.xml:2301
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2378
+ #, 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 ""
- #: using-d-i.xml:2310
- #, no-c-format
  #. Tag: filename
+ #: using-d-i.xml:2387
+ #, no-c-format
  msgid "elilo.efi"
  msgstr ""
- #: using-d-i.xml:2311
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2388
+ #, 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 ""
- #: using-d-i.xml:2321
- #, no-c-format
  #. Tag: filename
+ #: using-d-i.xml:2398
+ #, no-c-format
  msgid "initrd.img"
  msgstr ""
- #: using-d-i.xml:2322
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2399
+ #, 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 ""
- #: using-d-i.xml:2334
- #, no-c-format
  #. Tag: filename
+ #: using-d-i.xml:2411
+ #, no-c-format
  msgid "readme.txt"
  msgstr ""
- #: using-d-i.xml:2335
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2412
+ #, 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 ""
- #: using-d-i.xml:2345
- #, no-c-format
  #. Tag: filename
+ #: using-d-i.xml:2422
+ #, no-c-format
  msgid "vmlinuz"
  msgstr ""
- #: using-d-i.xml:2346
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2423
+ #, 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 ""
- #: using-d-i.xml:2366
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2443
+ #, no-c-format
  msgid "<command>arcboot</command>-installer"
  msgstr ""
- #: using-d-i.xml:2367
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2444
+ #, no-c-format
  msgid ""
        "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
        "<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
-Line 1863 
 msgid ""
+Line 1926 
 msgid ""
        "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>."
  msgstr ""
- #: using-d-i.xml:2386
- #, no-c-format
  #. Tag: replaceable
+ #: using-d-i.xml:2463
+ #, no-c-format
  msgid "scsi"
  msgstr ""
- #: using-d-i.xml:2387
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2464
+ #, no-c-format
  msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
  msgstr ""
- #: using-d-i.xml:2395
- #, no-c-format
  #. Tag: replaceable
+ #: using-d-i.xml:2472
+ #, no-c-format
  msgid "disk"
  msgstr ""
- #: using-d-i.xml:2396
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2473
+ #, no-c-format
  msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
  msgstr ""
- #: using-d-i.xml:2404 using-d-i.xml:2473
- #, no-c-format
  #. Tag: replaceable
+ #: using-d-i.xml:2481 using-d-i.xml:2550
+ #, no-c-format
  msgid "partnr"
  msgstr ""
- #: using-d-i.xml:2405
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2482
+ #, no-c-format
  msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
  msgstr ""
- #: using-d-i.xml:2413
- #, no-c-format
  #. Tag: replaceable
+ #: using-d-i.xml:2490
+ #, no-c-format
  msgid "config"
  msgstr ""
- #: using-d-i.xml:2414
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2491
+ #, no-c-format
  msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
  msgstr ""
- #: using-d-i.xml:2435
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2512
+ #, no-c-format
  msgid "<command>delo</command>-installer"
  msgstr ""
- #: using-d-i.xml:2436
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2513
+ #, no-c-format
  msgid ""
        "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n"
        "<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput>\n"
        "</screen></informalexample> on the firmware prompt."
  msgstr ""
- #: using-d-i.xml:2455
- #, no-c-format
  #. Tag: replaceable
+ #: using-d-i.xml:2532
+ #, no-c-format
  msgid "<replaceable>#</replaceable>"
  msgstr ""
- #: using-d-i.xml:2456
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2533
+ #, no-c-format
  msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers"
  msgstr ""
- #: using-d-i.xml:2464
- #, no-c-format
  #. Tag: replaceable
+ #: using-d-i.xml:2541
+ #, no-c-format
  msgid "<replaceable>id</replaceable>"
  msgstr ""
- #: using-d-i.xml:2465
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2542
+ #, no-c-format
  msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed"
  msgstr ""
- #: using-d-i.xml:2474
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2551
+ #, no-c-format
  msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides"
  msgstr ""
- #: using-d-i.xml:2482
- #, no-c-format
  #. Tag: replaceable
+ #: using-d-i.xml:2559
+ #, no-c-format
  msgid "name"
  msgstr ""
- #: using-d-i.xml:2483
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2560
+ #, no-c-format
  msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default."
  msgstr ""
- #: using-d-i.xml:2493
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2570
+ #, no-c-format
  msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use"
  msgstr ""
- #: using-d-i.xml:2499
- #, no-c-format
  #. Tag: screen
+ #: using-d-i.xml:2576
+ #, no-c-format
  msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>"
  msgstr ""
- #: using-d-i.xml:2509
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2586
+ #, no-c-format
  msgid "Install <command>Yaboot</command> on a Hard Disk"
  msgstr ""
- #: using-d-i.xml:2510
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2587
+ #, no-c-format
  msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;."
  msgstr ""
- #: using-d-i.xml:2528
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2605
+ #, no-c-format
  msgid "Install <command>Quik</command> on a Hard Disk"
  msgstr ""
- #: using-d-i.xml:2529
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2606
+ #, 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 ""
- #: using-d-i.xml:2545
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2622
+ #, no-c-format
  msgid "<command>zipl</command>-installer"
  msgstr ""
- #: using-d-i.xml:2546
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2623
+ #, 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 ""
- #: using-d-i.xml:2563
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2640
+ #, no-c-format
  msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
  msgstr ""
- #: using-d-i.xml:2565
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2642
+ #, 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 ""
- #: using-d-i.xml:2590
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2667
+ #, no-c-format
  msgid "Continue Without Boot Loader"
  msgstr ""
- #: using-d-i.xml:2592
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2669
+ #, no-c-format
  msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>"
  msgstr ""
- #: using-d-i.xml:2601
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2678
+ #, 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 ""
- #: using-d-i.xml:2618
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2695
+ #, no-c-format
  msgid "Finishing the Installation"
  msgstr ""
- #: using-d-i.xml:2619
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2696
+ #, no-c-format
  msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;."
  msgstr ""
- #: using-d-i.xml:2631
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2708
+ #, no-c-format
  msgid "Finish the Installation and Reboot"
  msgstr ""
- #: using-d-i.xml:2633
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2710
+ #, no-c-format
  msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system."
  msgstr ""
- #: using-d-i.xml:2640
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2717
+ #, no-c-format
  msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation."
  msgstr ""
- #: using-d-i.xml:2654
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2731
+ #, no-c-format
  msgid "Miscellaneous"
  msgstr ""
- #: using-d-i.xml:2655
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2732
+ #, 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 ""
- #: using-d-i.xml:2668
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2745
+ #, no-c-format
  msgid "Saving the installation logs"
  msgstr ""
- #: using-d-i.xml:2670
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2747
+ #, 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 ""
- #: using-d-i.xml:2677
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2754
+ #, no-c-format
  msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
  msgstr ""
- #: using-d-i.xml:2697
- #, no-c-format
  #. Tag: title
+ #: using-d-i.xml:2774
+ #, no-c-format
  msgid "Using the Shell and Viewing the Logs"
  msgstr ""
- #: using-d-i.xml:2700
- #, no-c-format
  #. Tag: para
- msgid "There is an <guimenuitem>Execute a Shell</guimenuitem> item on the menu. If the menu is not available when you need to use the shell, press <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap> </keycombo>) to switch to the second <emphasis>virtual console</emphasis>. That's 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. This is a separate window running a Bourne shell clone called <command>ash</command>."
+ #: using-d-i.xml:2776
+ #, no-c-format
+ msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself."
  msgstr ""
- #: using-d-i.xml:2712
+ #. Tag: para
+ #: using-d-i.xml:2794
  #, 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
- 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 text editor is <command>nano</command>. The shell has some nice features like autocompletion and history."
+ #: using-d-i.xml:2802
+ #, 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 ""
- #: using-d-i.xml:2721
+ #. Tag: para
+ #: using-d-i.xml:2811
  #, 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
- msgid "Use the menus to perform any task that they are able to do &mdash; the shell and commands are only there in case something goes wrong. In particular, you should always use the menus, not the shell, to activate your swap partition, because the menu software can't detect that you've done this from the shell. Press <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to get back to menus, or type <command>exit</command> if you used a menu item to open the shell."
+ #: using-d-i.xml:2818
+ #, 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 ""
- #: using-d-i.xml:2740
+ #. Tag: para
+ #: using-d-i.xml:2824
  #, 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:2839
+ #, no-c-format
  msgid "Installation Over the Network"
  msgstr ""
- #: using-d-i.xml:2742
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2841
+ #, 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 ""
- #: using-d-i.xml:2752
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2851
+ #, no-c-format
  msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
  msgstr ""
- #: using-d-i.xml:2765
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2864
+ #, no-c-format
  msgid "For installations on &arch-title;, this is the default method after setting up the network."
  msgstr ""
- #: using-d-i.xml:2770
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2869
+ #, no-c-format
  msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>."
  msgstr ""
- #: using-d-i.xml:2782
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2881
+ #, 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 ""
- #: using-d-i.xml:2788
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2887
+ #, 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 ""
- #: using-d-i.xml:2805
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2904
+ #, no-c-format
  msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename> and try again."
  msgstr ""
- #: using-d-i.xml:2814
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2913
+ #, 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 ""
- #: using-d-i.xml:2824
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2923
+ #, 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 ""
- #: using-d-i.xml:2832
- #, no-c-format
  #. Tag: para
+ #: using-d-i.xml:2931
+ #, no-c-format
  msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated."
  msgstr ""

 Legend:



Removed from v.38789
 


changed lines


 
Added in v.48723
 Legend:



Removed from v.38789
 


changed lines


 
Added in v.48723
-Removed from v.38789
+Added in v.48723

	ViewVC Help
Powered by ViewVC 1.1.5