summaryrefslogtreecommitdiff
path: root/po/pot/using-d-i.pot
diff options
context:
space:
mode:
authorChristian Perrier <bubulle@debian.org>2010-10-29 06:05:21 +0000
committerChristian Perrier <bubulle@debian.org>2010-10-29 06:05:21 +0000
commitdf76c209fd8f85bf9b2d00b55e742be5cdad603e (patch)
treecb5f52c1854ed1cffd100d898bcc56ea75082b87 /po/pot/using-d-i.pot
parentb71615366c0acd03111448f435d334504b25a49f (diff)
downloadinstallation-guide-df76c209fd8f85bf9b2d00b55e742be5cdad603e.zip
Refresh PO(T) files
Diffstat (limited to 'po/pot/using-d-i.pot')
-rw-r--r--po/pot/using-d-i.pot518
1 files changed, 259 insertions, 259 deletions
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index 9d52eaed2..031d2a9c3 100644
--- a/po/pot/using-d-i.pot
+++ b/po/pot/using-d-i.pot
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2010-10-10 12:35+0000\n"
+"POT-Creation-Date: 2010-10-29 05:56+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"
@@ -257,112 +257,112 @@ msgstr ""
#. Tag: term
#: using-d-i.xml:247
#, no-c-format
-msgid "clock-setup"
+msgid "user-setup"
msgstr ""
#. Tag: para
#: using-d-i.xml:247
#, no-c-format
+msgid "Sets up the root password, and adds a non-root user."
+msgstr ""
+
+#. Tag: term
+#: using-d-i.xml:255
+#, no-c-format
+msgid "clock-setup"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:255
+#, no-c-format
msgid "Updates the system clock and determines whether the clock is set to UTC or not."
msgstr ""
#. Tag: term
-#: using-d-i.xml:256
+#: using-d-i.xml:264
#, no-c-format
msgid "tzsetup"
msgstr ""
#. Tag: para
-#: using-d-i.xml:256
+#: using-d-i.xml:264
#, no-c-format
msgid "Selects the time zone, based on the location selected earlier."
msgstr ""
#. Tag: term
-#: using-d-i.xml:264
+#: using-d-i.xml:272
#, no-c-format
msgid "partman"
msgstr ""
#. Tag: para
-#: using-d-i.xml:264
+#: using-d-i.xml:272
#, no-c-format
msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in &debian;."
msgstr ""
#. Tag: term
-#: using-d-i.xml:276
+#: using-d-i.xml:284
#, no-c-format
msgid "partitioner"
msgstr ""
#. Tag: para
-#: using-d-i.xml:276
+#: using-d-i.xml:284
#, no-c-format
msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
msgstr ""
#. Tag: term
-#: using-d-i.xml:286
+#: using-d-i.xml:294
#, no-c-format
msgid "partconf"
msgstr ""
#. Tag: para
-#: using-d-i.xml:286
+#: using-d-i.xml:294
#, no-c-format
msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
msgstr ""
#. Tag: term
-#: using-d-i.xml:295
+#: using-d-i.xml:303
#, no-c-format
msgid "lvmcfg"
msgstr ""
#. Tag: para
-#: using-d-i.xml:295
+#: using-d-i.xml:303
#, no-c-format
msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
msgstr ""
#. Tag: term
-#: using-d-i.xml:304
+#: using-d-i.xml:312
#, no-c-format
msgid "mdcfg"
msgstr ""
#. Tag: para
-#: using-d-i.xml:304
+#: using-d-i.xml:312
#, no-c-format
msgid "Allows the user to set up Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
msgstr ""
#. Tag: term
-#: using-d-i.xml:315
+#: using-d-i.xml:323
#, no-c-format
msgid "base-installer"
msgstr ""
#. Tag: para
-#: using-d-i.xml:315
+#: using-d-i.xml:323
#, no-c-format
msgid "Installs the most basic set of packages which would allow the computer to operate under &debian-gnu; when rebooted."
msgstr ""
#. Tag: term
-#: using-d-i.xml:324
-#, no-c-format
-msgid "user-setup"
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:324
-#, no-c-format
-msgid "Sets up the root password, and adds a non-root user."
-msgstr ""
-
-#. Tag: term
#: using-d-i.xml:332
#, no-c-format
msgid "apt-setup"
@@ -731,23 +731,89 @@ msgstr ""
#. Tag: title
#: using-d-i.xml:901
#, no-c-format
-msgid "Partitioning and Mount Point Selection"
+msgid "Setting Up Users And Passwords"
msgstr ""
#. Tag: para
#: using-d-i.xml:902
#, no-c-format
+msgid "Just before configuring the clock, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
+msgstr ""
+
+#. Tag: title
+#: using-d-i.xml:916
+#, no-c-format
+msgid "Set the Root Password"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:920
+#, no-c-format
+msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:928
+#, no-c-format
+msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:936
+#, no-c-format
+msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
+msgstr ""
+
+#. Tag: title
+#: using-d-i.xml:946
+#, no-c-format
+msgid "Create an Ordinary User"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:948
+#, no-c-format
+msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:957
+#, 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 ""
+
+#. Tag: para
+#: using-d-i.xml:967
+#, no-c-format
+msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:974
+#, no-c-format
+msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
+msgstr ""
+
+#. Tag: title
+#: using-d-i.xml:985
+#, no-c-format
+msgid "Partitioning and Mount Point Selection"
+msgstr ""
+
+#. Tag: para
+#: using-d-i.xml:986
+#, no-c-format
msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices."
msgstr ""
#. Tag: para
-#: using-d-i.xml:923
+#: using-d-i.xml:1007
#, no-c-format
msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:929
+#: using-d-i.xml:1013
#, 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"
@@ -756,313 +822,313 @@ msgid ""
msgstr ""
#. Tag: para
-#: using-d-i.xml:942
+#: using-d-i.xml:1026
#, no-c-format
msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
msgstr ""
#. Tag: title
-#: using-d-i.xml:952
+#: using-d-i.xml:1036
#, no-c-format
msgid "Supported partitioning options"
msgstr ""
#. Tag: para
-#: using-d-i.xml:953
+#: using-d-i.xml:1037
#, no-c-format
msgid "The partitioner used in &d-i; is fairly versatile. It allows to create many different partitioning schemes, using various partition tables, file systems and advanced block devices."
msgstr ""
#. Tag: para
-#: using-d-i.xml:959
+#: using-d-i.xml:1043
#, no-c-format
msgid "Exactly which options are available depends mainly on the architecture, but also on other factors. For example, on systems with limited internal memory some options may not be available. Defaults may vary as well. The type of partition table used by default can for example be different for large capacity hard disks than for smaller hard disks. Some options can only be changed when installing at medium or low debconf priority; at higher priorities sensible defaults will be used."
msgstr ""
#. Tag: para
-#: using-d-i.xml:970
+#: using-d-i.xml:1054
#, no-c-format
msgid "The installer supports various forms of advanced partitioning and use of storage devices, which in many cases can be used in combination."
msgstr ""
#. Tag: emphasis
-#: using-d-i.xml:977
+#: using-d-i.xml:1061
#, no-c-format
msgid "Logical Volume Management (LVM)"
msgstr ""
#. Tag: emphasis
-#: using-d-i.xml:980
+#: using-d-i.xml:1064
#, no-c-format
msgid "Software RAID"
msgstr ""
#. Tag: para
-#: using-d-i.xml:981
+#: using-d-i.xml:1065
#, no-c-format
msgid "Supported are RAID levels 0, 1, 4, 5, 6 and 10."
msgstr ""
#. Tag: emphasis
-#: using-d-i.xml:985
+#: using-d-i.xml:1069
#, no-c-format
msgid "Encryption"
msgstr ""
#. Tag: para
-#: using-d-i.xml:987
+#: using-d-i.xml:1071
#, no-c-format
msgid "<emphasis>Serial ATA RAID</emphasis> (using <classname>dmraid</classname>)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:989
+#: using-d-i.xml:1073
#, no-c-format
msgid "Also called <quote>fake RAID</quote> or <quote>BIOS RAID</quote>. Support for Serial ATA RAID is currently only available if enabled when the installer is booted. Further information is available on <ulink url=\"&url-d-i-sataraid;\">our Wiki</ulink>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:995
+#: using-d-i.xml:1079
#, no-c-format
msgid "<emphasis>Multipath</emphasis> (experimental)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:997
+#: using-d-i.xml:1081
#, no-c-format
msgid "See <ulink url=\"&url-d-i-multipath;\">our Wiki</ulink> for information. Support for multipath is currently only available if enabled when the installer is booted."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1004
+#: using-d-i.xml:1088
#, no-c-format
msgid "The following file systems are supported."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1009
+#: using-d-i.xml:1093
#, no-c-format
msgid "<phrase arch=\"arm;mipsel\"><emphasis>ext2r0</emphasis>,</phrase> <emphasis>ext2</emphasis>, <emphasis>ext3</emphasis>, <emphasis>ext4</emphasis>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1014
+#: using-d-i.xml:1098
#, no-c-format
msgid "The default file system selected in most cases is ext3; for <filename>/boot</filename> partitions ext2 will be selected by default when guided partitioning is used."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1019
+#: using-d-i.xml:1103
#, no-c-format
msgid "<emphasis>jfs</emphasis> (not available on all architectures)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1022
+#: using-d-i.xml:1106
#, no-c-format
msgid "<emphasis>xfs</emphasis> (not available on all architectures)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1025
+#: using-d-i.xml:1109
#, no-c-format
msgid "<emphasis>reiserfs</emphasis> (optional; not available on all architectures)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1027
+#: using-d-i.xml:1111
#, no-c-format
msgid "Support for the Reiser file system is no longer available by default. When the installer is running at medium or low debconf priority it can be enabled by selecting the <classname>partman-reiserfs</classname> component. Only version 3 of the file system is supported."
msgstr ""
#. Tag: emphasis
-#: using-d-i.xml:1034
+#: using-d-i.xml:1118
#, no-c-format
msgid "jffs2"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1035
+#: using-d-i.xml:1119
#, no-c-format
msgid "Used on some systems to read flash memory. It is not possible to create new jffs2 partitions."
msgstr ""
#. Tag: emphasis
-#: using-d-i.xml:1040
+#: using-d-i.xml:1124
#, no-c-format
msgid "qnx4"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1041
+#: using-d-i.xml:1125
#, no-c-format
msgid "Existing partitions will be recognized and it is possible to assign mount points for them. It is not possible to create new qnx4 partitions."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1045
+#: using-d-i.xml:1129
#, no-c-format
msgid "<emphasis>FAT16</emphasis>, <emphasis>FAT32</emphasis>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1048
+#: using-d-i.xml:1132
#, no-c-format
msgid "<emphasis>NTFS</emphasis> (read-only)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1050
+#: using-d-i.xml:1134
#, no-c-format
msgid "Existing NTFS partitions can be resized and it is possible to assign mount points for them. It is not possible to create new NTFS partitions."
msgstr ""
#. Tag: title
-#: using-d-i.xml:1060
+#: using-d-i.xml:1144
#, no-c-format
msgid "Guided Partitioning"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1061
+#: using-d-i.xml:1145
#, no-c-format
msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1076
+#: using-d-i.xml:1160
#, no-c-format
msgid "The option to use (encrypted) LVM may not be available on all architectures."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1081
+#: using-d-i.xml:1165
#, no-c-format
msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1090
+#: using-d-i.xml:1174
#, no-c-format
msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1099
+#: using-d-i.xml:1183
#, no-c-format
msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1109
+#: using-d-i.xml:1193
#, 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:1118
+#: using-d-i.xml:1202
#, 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:1126
+#: using-d-i.xml:1210
#, no-c-format
msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1142
+#: using-d-i.xml:1226
#, no-c-format
msgid "Partitioning scheme"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1143
+#: using-d-i.xml:1227
#, no-c-format
msgid "Minimum space"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1144
+#: using-d-i.xml:1228
#, no-c-format
msgid "Created partitions"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1150
+#: using-d-i.xml:1234
#, no-c-format
msgid "All files in one partition"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1151
+#: using-d-i.xml:1235
#, no-c-format
msgid "600MB"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1152
+#: using-d-i.xml:1236
#, no-c-format
msgid "<filename>/</filename>, swap"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1154
+#: using-d-i.xml:1238
#, no-c-format
msgid "Separate /home partition"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1155
+#: using-d-i.xml:1239
#, no-c-format
msgid "500MB"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1156
+#: using-d-i.xml:1240
#, no-c-format
msgid "<filename>/</filename>, <filename>/home</filename>, swap"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1160
+#: using-d-i.xml:1244
#, no-c-format
msgid "Separate /home, /usr, /var and /tmp partitions"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1161
+#: using-d-i.xml:1245
#, no-c-format
msgid "<entry>1GB</entry>"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1162
+#: using-d-i.xml:1246
#, no-c-format
msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1171
+#: using-d-i.xml:1255
#, no-c-format
msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1177
+#: using-d-i.xml:1261
#, 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 ""
#. Tag: para
-#: using-d-i.xml:1185
+#: using-d-i.xml:1269
#, no-c-format
msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1191
+#: using-d-i.xml:1275
#, no-c-format
msgid ""
"The list of partitions might look like this: <informalexample><screen>\n"
@@ -1085,601 +1151,601 @@ msgid ""
msgstr ""
#. Tag: para
-#: using-d-i.xml:1204
+#: using-d-i.xml:1288
#, no-c-format
msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
msgstr ""
#. Tag: title
-#: using-d-i.xml:1218
+#: using-d-i.xml:1302
#, no-c-format
msgid "Manual Partitioning"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1219
+#: using-d-i.xml:1303
#, no-c-format
msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually set up your partition table and the usage of partitions by your new &debian; system will be covered in the remainder of this section."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1227
+#: using-d-i.xml:1311
#, no-c-format
msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1235
+#: using-d-i.xml:1319
#, no-c-format
msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, 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."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1257
+#: using-d-i.xml:1341
#, no-c-format
msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1268
+#: using-d-i.xml:1352
#, no-c-format
msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1276
+#: using-d-i.xml:1360
#, no-c-format
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."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1282
+#: using-d-i.xml:1366
#, no-c-format
msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1290
+#: using-d-i.xml:1374
#, no-c-format
msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
msgstr ""
#. Tag: title
-#: using-d-i.xml:1318
+#: using-d-i.xml:1402
#, no-c-format
msgid "Configuring Multidisk Devices (Software RAID)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1319
+#: using-d-i.xml:1403
#, no-c-format
msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. </para></footnote> in your computer, you can use <command>mdcfg</command> to set up your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1332
+#: using-d-i.xml:1416
#, no-c-format
msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1340
+#: using-d-i.xml:1424
#, no-c-format
msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> <varlistentry> <term>RAID6</term><listitem><para> Is similar to RAID5 except that it uses two parity devices instead of one. </para><para> A RAID6 array can survive up to two disk failures. </para></listitem> </varlistentry> <varlistentry> <term>RAID10</term><listitem><para> RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates <replaceable>n</replaceable> copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of <replaceable>n</replaceable> is 2, but it can be set to something else in expert mode. The number of partitions used must be at least <replaceable>n</replaceable>. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. </para><para> RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. </para></listitem> </varlistentry> </variablelist> To sum it up:"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1454
+#: using-d-i.xml:1538
#, no-c-format
msgid "Type"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1455
+#: using-d-i.xml:1539
#, no-c-format
msgid "Minimum Devices"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1456
+#: using-d-i.xml:1540
#, no-c-format
msgid "Spare Device"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1457
+#: using-d-i.xml:1541
#, no-c-format
msgid "Survives disk failure?"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1458
+#: using-d-i.xml:1542
#, no-c-format
msgid "Available Space"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1464
+#: using-d-i.xml:1548
#, no-c-format
msgid "RAID0"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1465 using-d-i.xml:1473 using-d-i.xml:1503
+#: using-d-i.xml:1549 using-d-i.xml:1557 using-d-i.xml:1587
#, no-c-format
msgid "<entry>2</entry>"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1466 using-d-i.xml:1467
+#: using-d-i.xml:1550 using-d-i.xml:1551
#, no-c-format
msgid "<entry>no</entry>"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1468
+#: using-d-i.xml:1552
#, no-c-format
msgid "Size of the smallest partition multiplied by number of devices in RAID"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1472
+#: using-d-i.xml:1556
#, no-c-format
msgid "RAID1"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1474 using-d-i.xml:1482 using-d-i.xml:1493 using-d-i.xml:1504
+#: using-d-i.xml:1558 using-d-i.xml:1566 using-d-i.xml:1577 using-d-i.xml:1588
#, no-c-format
msgid "optional"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1475 using-d-i.xml:1483 using-d-i.xml:1494 using-d-i.xml:1505
+#: using-d-i.xml:1559 using-d-i.xml:1567 using-d-i.xml:1578 using-d-i.xml:1589
#, no-c-format
msgid "<entry>yes</entry>"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1476
+#: using-d-i.xml:1560
#, no-c-format
msgid "Size of the smallest partition in RAID"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1480
+#: using-d-i.xml:1564
#, no-c-format
msgid "RAID5"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1481
+#: using-d-i.xml:1565
#, no-c-format
msgid "<entry>3</entry>"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1484
+#: using-d-i.xml:1568
#, no-c-format
msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1491
+#: using-d-i.xml:1575
#, no-c-format
msgid "RAID6"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1492
+#: using-d-i.xml:1576
#, no-c-format
msgid "<entry>4</entry>"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1495
+#: using-d-i.xml:1579
#, no-c-format
msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1502
+#: using-d-i.xml:1586
#, no-c-format
msgid "RAID10"
msgstr ""
#. Tag: entry
-#: using-d-i.xml:1506
+#: using-d-i.xml:1590
#, no-c-format
msgid "Total of all partitions divided by the number of chunk copies (defaults to two)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1513
+#: using-d-i.xml:1597
#, no-c-format
msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1518
+#: using-d-i.xml:1602
#, no-c-format
msgid "To create an MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1527
+#: using-d-i.xml:1611
#, no-c-format
msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1539
+#: using-d-i.xml:1623
#, 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>) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1548
+#: using-d-i.xml:1632
#, 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 ""
#. Tag: para
-#: using-d-i.xml:1561
+#: using-d-i.xml:1645
#, 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 ""
#. Tag: para
-#: using-d-i.xml:1568
+#: using-d-i.xml:1652
#, no-c-format
msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1580
+#: using-d-i.xml:1664
#, no-c-format
msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1586
+#: using-d-i.xml:1670
#, no-c-format
msgid "RAID6 also has a setup procedure similar to RAID1 except that at least <emphasis>four</emphasis> active partitions are required."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1592
+#: using-d-i.xml:1676
#, no-c-format
msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either <literal>n</literal> (for near copies), <literal>f</literal> (for far copies), or <literal>o</literal> (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1606
+#: using-d-i.xml:1690
#, 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:1615
+#: using-d-i.xml:1699
#, no-c-format
msgid "After you set up MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
msgstr ""
#. Tag: title
-#: using-d-i.xml:1630
+#: using-d-i.xml:1714
#, no-c-format
msgid "Configuring the Logical Volume Manager (LVM)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1631
+#: using-d-i.xml:1715
#, no-c-format
msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1639
+#: using-d-i.xml:1723
#, no-c-format
msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disk (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1649
+#: using-d-i.xml:1733
#, 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 ""
#. Tag: para
-#: using-d-i.xml:1660
+#: using-d-i.xml:1744
#, no-c-format
msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1669
+#: using-d-i.xml:1753
#, no-c-format
msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1680
+#: using-d-i.xml:1764
#, 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:1685
+#: using-d-i.xml:1769
#, no-c-format
msgid "Create volume group"
msgstr ""
#. Tag: guimenuitem
-#: using-d-i.xml:1688
+#: using-d-i.xml:1772
#, no-c-format
msgid "Create logical volume"
msgstr ""
#. Tag: guimenuitem
-#: using-d-i.xml:1691
+#: using-d-i.xml:1775
#, no-c-format
msgid "Delete volume group"
msgstr ""
#. Tag: guimenuitem
-#: using-d-i.xml:1694
+#: using-d-i.xml:1778
#, no-c-format
msgid "Delete logical volume"
msgstr ""
#. Tag: guimenuitem
-#: using-d-i.xml:1697
+#: using-d-i.xml:1781
#, no-c-format
msgid "Extend volume group"
msgstr ""
#. Tag: guimenuitem
-#: using-d-i.xml:1700
+#: using-d-i.xml:1784
#, no-c-format
msgid "Reduce volume group"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1702
+#: using-d-i.xml:1786
#, no-c-format
msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1708
+#: using-d-i.xml:1792
#, no-c-format
msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1713
+#: using-d-i.xml:1797
#, no-c-format
msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
msgstr ""
#. Tag: title
-#: using-d-i.xml:1727
+#: using-d-i.xml:1811
#, no-c-format
msgid "Configuring Encrypted Volumes"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1728
+#: using-d-i.xml:1812
#, no-c-format
msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1740
+#: using-d-i.xml:1824
#, 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
-#: using-d-i.xml:1755
+#: using-d-i.xml:1839
#, no-c-format
msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1762
+#: using-d-i.xml:1846
#, no-c-format
msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1773
+#: using-d-i.xml:1857
#, 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 ""
#. Tag: para
-#: using-d-i.xml:1785
+#: using-d-i.xml:1869
#, 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:1795
+#: using-d-i.xml:1879
#, no-c-format
msgid "Encryption: <userinput>aes</userinput>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1797
+#: using-d-i.xml:1881
#, no-c-format
msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
msgstr ""
#. Tag: term
-#: using-d-i.xml:1815
+#: using-d-i.xml:1899
#, no-c-format
msgid "Key size: <userinput>256</userinput>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1817
+#: using-d-i.xml:1901
#, no-c-format
msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
msgstr ""
#. Tag: term
-#: using-d-i.xml:1829
+#: using-d-i.xml:1913
#, no-c-format
msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1831
+#: using-d-i.xml:1915
#, no-c-format
msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1841
+#: using-d-i.xml:1925
#, 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 ""
#. Tag: term
-#: using-d-i.xml:1853
+#: using-d-i.xml:1937
#, no-c-format
msgid "Encryption key: <userinput>Passphrase</userinput>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1855
+#: using-d-i.xml:1939
#, no-c-format
msgid "Here you can choose the type of the encryption key for this partition."
msgstr ""
#. Tag: term
-#: using-d-i.xml:1861
+#: using-d-i.xml:1945
#, no-c-format
msgid "Passphrase"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1862
+#: using-d-i.xml:1946
#, no-c-format
msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
msgstr ""
#. Tag: term
-#: using-d-i.xml:1877 using-d-i.xml:1970
+#: using-d-i.xml:1961 using-d-i.xml:2054
#, no-c-format
msgid "Random key"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1878
+#: using-d-i.xml:1962
#, no-c-format
msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1887
+#: using-d-i.xml:1971
#, no-c-format
msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
msgstr ""
#. Tag: term
-#: using-d-i.xml:1906 using-d-i.xml:1983
+#: using-d-i.xml:1990 using-d-i.xml:2067
#, no-c-format
msgid "Erase data: <userinput>yes</userinput>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1908
+#: using-d-i.xml:1992
#, no-c-format
msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1928
+#: using-d-i.xml:2012
#, 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 ""
#. Tag: term
-#: using-d-i.xml:1937
+#: using-d-i.xml:2021
#, no-c-format
msgid "Encryption: <userinput>AES256</userinput>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1939
+#: using-d-i.xml:2023
#, 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 ""
#. Tag: term
-#: using-d-i.xml:1949
+#: using-d-i.xml:2033
#, no-c-format
msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1951
+#: using-d-i.xml:2035
#, no-c-format
msgid "Here you can select the type of the encryption key for this partition."
msgstr ""
#. Tag: term
-#: using-d-i.xml:1957
+#: using-d-i.xml:2041
#, no-c-format
msgid "Keyfile (GnuPG)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:1958
+#: using-d-i.xml:2042
#, 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 ""
#. Tag: para
-#: using-d-i.xml:1971
+#: using-d-i.xml:2055
#, no-c-format
msgid "Please see the section on random keys above."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1985
+#: using-d-i.xml:2069
#, no-c-format
msgid "Please see the the section on erasing data above."
msgstr ""
#. Tag: para
-#: using-d-i.xml:1994
+#: using-d-i.xml:2078
#, no-c-format
msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2004
+#: using-d-i.xml:2088
#, no-c-format
msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2013
+#: using-d-i.xml:2097
#, no-c-format
msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2026
+#: using-d-i.xml:2110
#, no-c-format
msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2042
+#: using-d-i.xml:2126
#, 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"
@@ -1692,126 +1758,60 @@ msgid ""
msgstr ""
#. Tag: para
-#: using-d-i.xml:2055
+#: using-d-i.xml:2139
#, no-c-format
msgid "Pay attention to the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2065
+#: using-d-i.xml:2149
#, no-c-format
msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2076
+#: using-d-i.xml:2160
#, no-c-format
msgid "Installing the Base System"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2077
+#: using-d-i.xml:2161
#, no-c-format
msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2090
+#: using-d-i.xml:2174
#, no-c-format
msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2099
+#: using-d-i.xml:2183
#, no-c-format
msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2105
+#: using-d-i.xml:2189
#, no-c-format
msgid "As part of the installation, a &arch-kernel; kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2112
+#: using-d-i.xml:2196
#, no-c-format
msgid "When packages are installed using the package management system, it will by default also install packages that are recommended by those packages. Recommended packages are not strictly required for the core functionality of the selected software, but they do enhance that software and should, in the view of the package maintainers, normally be installed together with that software."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2122
+#: using-d-i.xml:2206
#, no-c-format
msgid "For technical reasons packages installed during the installation of the base system are installed without their <quote>Recommends</quote>. The rule described above only takes effect after this point in the installation process."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2134
-#, no-c-format
-msgid "Setting Up Users And Passwords"
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2135
-#, no-c-format
-msgid "After the base system has been installed, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
-msgstr ""
-
-#. Tag: title
-#: using-d-i.xml:2149
-#, no-c-format
-msgid "Set the Root Password"
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2153
-#, no-c-format
-msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2161
-#, no-c-format
-msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2169
-#, no-c-format
-msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
-msgstr ""
-
-#. Tag: title
-#: using-d-i.xml:2179
-#, no-c-format
-msgid "Create an Ordinary User"
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2181
-#, no-c-format
-msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2190
-#, 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 ""
-
-#. Tag: para
-#: using-d-i.xml:2200
-#, no-c-format
-msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
-msgstr ""
-
-#. Tag: para
-#: using-d-i.xml:2207
-#, no-c-format
-msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
-msgstr ""
-
-#. Tag: title
#: using-d-i.xml:2218
#, no-c-format
msgid "Installing Additional Software"
@@ -2222,7 +2222,7 @@ msgstr ""
#. Tag: para
#: using-d-i.xml:2771
#, 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!"
+msgid "The criterion for selecting a partition is that it must be a FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
msgstr ""
#. Tag: title