summaryrefslogtreecommitdiff
path: root/po/pot
diff options
context:
space:
mode:
authorFelipe Augusto van de Wiel <faw@debian.org>2008-10-26 00:11:57 +0000
committerFelipe Augusto van de Wiel <faw@debian.org>2008-10-26 00:11:57 +0000
commit4c54eb0ad9a1532876f42bace58cf803a671f41d (patch)
tree7a48db0e1626bf463b8d76cc3e3f39dbf8670022 /po/pot
parentc44c61370e5189185f683332a52917d0a4e7f1d3 (diff)
downloadinstallation-guide-4c54eb0ad9a1532876f42bace58cf803a671f41d.zip
[SILENT_COMMIT] Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
-rw-r--r--po/pot/preseed.pot194
-rw-r--r--po/pot/using-d-i.pot242
2 files changed, 215 insertions, 221 deletions
diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot
index 2ea2d807b..113602120 100644
--- a/po/pot/preseed.pot
+++ b/po/pot/preseed.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: 2008-10-22 00:10+0000\n"
+"POT-Creation-Date: 2008-10-26 00:10+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"
@@ -27,7 +27,7 @@ msgid "This appendix explains how to preseed answers to questions in &d-i; to au
msgstr ""
#. Tag: para
-#: preseed.xml:23 preseed.xml:664
+#: preseed.xml:23 preseed.xml:663
#, no-c-format
msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;."
msgstr ""
@@ -600,47 +600,47 @@ msgstr ""
#. Tag: para
#: preseed.xml:574
#, no-c-format
-msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value. If you specify an empty value you should still put a single space or tab after the type."
+msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value."
msgstr ""
#. Tag: para
-#: preseed.xml:579
+#: preseed.xml:578
#, no-c-format
-msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Splitting a line inside the value is normally not supported, with the exception of partitioning recipes."
+msgid "A line can be split into multiple lines by appending a backslash (<quote><literal>\\</literal></quote>) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space."
msgstr ""
#. Tag: para
-#: preseed.xml:586
+#: preseed.xml:585
#, no-c-format
msgid "For debconf variables (templates) used in the installer itself, the owner should be set to <quote>d-i</quote>; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than <quote>d-i</quote> will be propagated to the debconf database for the installed system."
msgstr ""
#. Tag: para
-#: preseed.xml:594
+#: preseed.xml:593
#, no-c-format
msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in <classname>partman</classname>) where the translated values need to be used."
msgstr ""
#. Tag: para
-#: preseed.xml:600
+#: preseed.xml:599
#, no-c-format
msgid "Some questions take a code as value instead of the English text that is shown during installation."
msgstr ""
#. Tag: para
-#: preseed.xml:606
+#: preseed.xml:605
#, no-c-format
msgid "The easiest way to create a preconfiguration file is to use the example file linked in <xref linkend=\"preseed-contents\"/> as basis and work from there."
msgstr ""
#. Tag: para
-#: preseed.xml:611
+#: preseed.xml:610
#, no-c-format
msgid "An alternative method is to do a manual installation and then, after rebooting, use the <command>debconf-get-selections</command> from the <classname>debconf-utils</classname> package to dump both the debconf database and the installer's cdebconf database to a single file:"
msgstr ""
#. Tag: screen
-#: preseed.xml:618
+#: preseed.xml:617
#, no-c-format
msgid ""
"$ debconf-get-selections --installer &gt; <replaceable>file</replaceable>\n"
@@ -648,67 +648,67 @@ msgid ""
msgstr ""
#. Tag: para
-#: preseed.xml:620
+#: preseed.xml:619
#, no-c-format
msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users."
msgstr ""
#. Tag: para
-#: preseed.xml:628
+#: preseed.xml:627
#, no-c-format
msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in <filename>/var/log/installer/cdebconf</filename>. However, because the database may contain sensitive information, by default the files are only readable by root."
msgstr ""
#. Tag: para
-#: preseed.xml:636
+#: preseed.xml:635
#, no-c-format
msgid "The directory <filename>/var/log/installer</filename> and all files in it will be deleted from your system if you purge the package <classname>installation-report</classname>."
msgstr ""
#. Tag: para
-#: preseed.xml:644
+#: preseed.xml:643
#, no-c-format
msgid "To check possible values for questions, you can use <command>nano</command> to examine the files in <filename>/var/lib/cdebconf</filename> while an installation is in progress. View <filename>templates.dat</filename> for the raw templates and <filename>questions.dat</filename> for the current values and for the values assigned to variables."
msgstr ""
#. Tag: para
-#: preseed.xml:652
+#: preseed.xml:651
#, no-c-format
msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command <command>debconf-set-selections -c <replaceable>preseed.cfg</replaceable></command>."
msgstr ""
#. Tag: title
-#: preseed.xml:663
+#: preseed.xml:662
#, no-c-format
msgid "Contents of the preconfiguration file (for &releasename;)"
msgstr ""
#. Tag: para
-#: preseed.xml:669
+#: preseed.xml:668
#, no-c-format
msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture."
msgstr ""
#. Tag: title
-#: preseed.xml:680
+#: preseed.xml:679
#, no-c-format
msgid "Localization"
msgstr ""
#. Tag: para
-#: preseed.xml:681
+#: preseed.xml:680
#, no-c-format
msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked."
msgstr ""
#. Tag: para
-#: preseed.xml:687
+#: preseed.xml:686
#, no-c-format
-msgid "The locale can be used to specify both language and country. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
+msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use <userinput>locale=<replaceable>en_US</replaceable></userinput>."
msgstr ""
#. Tag: screen
-#: preseed.xml:693
+#: preseed.xml:695
#, no-c-format
msgid ""
"# Locale sets language and country.\n"
@@ -716,13 +716,13 @@ msgid ""
msgstr ""
#. Tag: para
-#: preseed.xml:695
+#: preseed.xml:697
#, no-c-format
msgid "Keyboard configuration consists of selecting a keyboard architecture and a keymap. In most cases the correct keyboard architecture is selected by default, so there's normally no need to preseed it. The keymap must be known to the &d-i; for the selected keyboard architecture."
msgstr ""
#. Tag: screen
-#: preseed.xml:702
+#: preseed.xml:704
#, no-c-format
msgid ""
"# Keyboard selection.\n"
@@ -733,55 +733,55 @@ msgid ""
msgstr ""
#. Tag: para
-#: preseed.xml:704
+#: preseed.xml:706
#, no-c-format
msgid "To skip keyboard configuration, preseed <classname>console-tools/archs</classname> with <userinput>skip-config</userinput>. This will result in the kernel keymap remaining active."
msgstr ""
#. Tag: para
-#: preseed.xml:713
+#: preseed.xml:715
#, no-c-format
msgid "The changes in the input layer for 2.6 kernels have made the keyboard architecture virtually obsolete. For 2.6 kernels normally a <quote>PC</quote> (<userinput>at</userinput>) keymap should be selected."
msgstr ""
#. Tag: title
-#: preseed.xml:723
+#: preseed.xml:725
#, no-c-format
msgid "Network configuration"
msgstr ""
#. Tag: para
-#: preseed.xml:724
+#: preseed.xml:726
#, no-c-format
msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters."
msgstr ""
#. Tag: para
-#: preseed.xml:732
+#: preseed.xml:734
#, no-c-format
msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as <userinput>interface=<replaceable>eth1</replaceable></userinput>."
msgstr ""
#. Tag: para
-#: preseed.xml:738
+#: preseed.xml:740
#, no-c-format
msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using <quote>preseed/url</quote>), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a <quote>preseed/run</quote> script containing the following commands:"
msgstr ""
#. Tag: screen
-#: preseed.xml:748
+#: preseed.xml:750
#, no-c-format
msgid "killall.sh; netcfg"
msgstr ""
#. Tag: para
-#: preseed.xml:750
+#: preseed.xml:752
#, no-c-format
msgid "The following debconf variables are relevant for network configuration."
msgstr ""
#. Tag: screen
-#: preseed.xml:756
+#: preseed.xml:758
#, no-c-format
msgid ""
"# netcfg will choose an interface that has link if possible. This makes it\n"
@@ -830,37 +830,37 @@ msgid ""
msgstr ""
#. Tag: para
-#: preseed.xml:758
+#: preseed.xml:760
#, no-c-format
msgid "Please note that <command>netcfg</command> will automatically determine the netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In this case, the variable has to be marked as <literal>seen</literal> for automatic installations. Similarly, <command>netcfg</command> will choose an appropriate address if <classname>netcfg/get_gateway</classname> is not set. As a special case, you can set <classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify that no gateway should be used."
msgstr ""
#. Tag: title
-#: preseed.xml:774
+#: preseed.xml:776
#, no-c-format
msgid "Mirror settings"
msgstr ""
#. Tag: para
-#: preseed.xml:775
+#: preseed.xml:777
#, no-c-format
msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system."
msgstr ""
#. Tag: para
-#: preseed.xml:782
+#: preseed.xml:784
#, no-c-format
msgid "The parameter <classname>mirror/suite</classname> determines the suite for the installed system."
msgstr ""
#. Tag: para
-#: preseed.xml:787
+#: preseed.xml:789
#, no-c-format
msgid "The parameter <classname>mirror/udeb/suite</classname> determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. By default the value for <classname>mirror/udeb/suite</classname> is the same as <classname>mirror/suite</classname>."
msgstr ""
#. Tag: screen
-#: preseed.xml:799
+#: preseed.xml:801
#, no-c-format
msgid ""
"# If you select ftp, the mirror/country string does not need to be set.\n"
@@ -877,13 +877,13 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:804
+#: preseed.xml:806
#, no-c-format
msgid "Clock and time zone setup"
msgstr ""
#. Tag: screen
-#: preseed.xml:806
+#: preseed.xml:808
#, no-c-format
msgid ""
"# Controls whether or not the hardware clock is set to UTC.\n"
@@ -900,25 +900,25 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:811
+#: preseed.xml:813
#, no-c-format
msgid "Partitioning"
msgstr ""
#. Tag: para
-#: preseed.xml:812
+#: preseed.xml:814
#, no-c-format
msgid "Using preseeding to partition the harddisk is very much limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file. It is currently not possible to partition multiple disks using preseeding."
msgstr ""
#. Tag: para
-#: preseed.xml:823
+#: preseed.xml:825
#, no-c-format
msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding."
msgstr ""
#. Tag: screen
-#: preseed.xml:831
+#: preseed.xml:833
#, no-c-format
msgid ""
"# If the system has free space you can choose to only partition that space.\n"
@@ -982,25 +982,25 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:836
+#: preseed.xml:838
#, no-c-format
msgid "Partitioning using RAID"
msgstr ""
#. Tag: para
-#: preseed.xml:837
+#: preseed.xml:839
#, no-c-format
msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices. If you are using RAID 1, you can preseed grub to install to all devices used in the array; see <xref linkend=\"preseed-bootloader\"/>."
msgstr ""
#. Tag: para
-#: preseed.xml:847
+#: preseed.xml:849
#, no-c-format
msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check <filename>/var/log/syslog</filename> if you run into problems."
msgstr ""
#. Tag: screen
-#: preseed.xml:857
+#: preseed.xml:859
#, no-c-format
msgid ""
"# NOTE: this option is of beta release quality and should be used carefully\n"
@@ -1050,19 +1050,19 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:862
+#: preseed.xml:864
#, no-c-format
msgid "Base system installation"
msgstr ""
#. Tag: para
-#: preseed.xml:863
+#: preseed.xml:865
#, no-c-format
msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel."
msgstr ""
#. Tag: screen
-#: preseed.xml:870
+#: preseed.xml:872
#, no-c-format
msgid ""
"# Select the initramfs generator used to generate the initrd for 2.6 kernels.\n"
@@ -1074,25 +1074,25 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:875
+#: preseed.xml:877
#, no-c-format
msgid "Account setup"
msgstr ""
#. Tag: para
-#: preseed.xml:876
+#: preseed.xml:878
#, no-c-format
msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 <emphasis>hashes</emphasis>."
msgstr ""
#. Tag: para
-#: preseed.xml:883
+#: preseed.xml:885
#, no-c-format
msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks."
msgstr ""
#. Tag: screen
-#: preseed.xml:893
+#: preseed.xml:895
#, no-c-format
msgid ""
"# Skip creation of a root account (normal user account will be able to\n"
@@ -1124,37 +1124,37 @@ msgid ""
msgstr ""
#. Tag: para
-#: preseed.xml:895
+#: preseed.xml:897
#, no-c-format
msgid "The <classname>passwd/root-password-crypted</classname> and <classname>passwd/user-password-crypted</classname> variables can also be preseeded with <quote>!</quote> as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or <command>sudo</command>)."
msgstr ""
#. Tag: para
-#: preseed.xml:905
+#: preseed.xml:907
#, no-c-format
msgid "The following command can be used to generate an MD5 hash for a password:"
msgstr ""
#. Tag: screen
-#: preseed.xml:909
+#: preseed.xml:911
#, no-c-format
msgid "$ echo \"r00tme\" | mkpasswd -s -m md5"
msgstr ""
#. Tag: title
-#: preseed.xml:915
+#: preseed.xml:917
#, no-c-format
msgid "Apt setup"
msgstr ""
#. Tag: para
-#: preseed.xml:916
+#: preseed.xml:918
#, no-c-format
msgid "Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories."
msgstr ""
#. Tag: screen
-#: preseed.xml:924
+#: preseed.xml:926
#, no-c-format
msgid ""
"# You can choose to install non-free and contrib software.\n"
@@ -1186,97 +1186,97 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:929
+#: preseed.xml:931
#, no-c-format
msgid "Package selection"
msgstr ""
#. Tag: para
-#: preseed.xml:930
+#: preseed.xml:932
#, no-c-format
msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:"
msgstr ""
#. Tag: userinput
-#: preseed.xml:939
+#: preseed.xml:941
#, no-c-format
msgid "standard"
msgstr ""
#. Tag: userinput
-#: preseed.xml:942
+#: preseed.xml:944
#, no-c-format
msgid "desktop"
msgstr ""
#. Tag: userinput
-#: preseed.xml:945
+#: preseed.xml:947
#, no-c-format
msgid "gnome-desktop"
msgstr ""
#. Tag: userinput
-#: preseed.xml:948
+#: preseed.xml:950
#, no-c-format
msgid "kde-desktop"
msgstr ""
#. Tag: userinput
-#: preseed.xml:951
+#: preseed.xml:953
#, no-c-format
msgid "web-server"
msgstr ""
#. Tag: userinput
-#: preseed.xml:954
+#: preseed.xml:956
#, no-c-format
msgid "print-server"
msgstr ""
#. Tag: userinput
-#: preseed.xml:957
+#: preseed.xml:959
#, no-c-format
msgid "dns-server"
msgstr ""
#. Tag: userinput
-#: preseed.xml:960
+#: preseed.xml:962
#, no-c-format
msgid "file-server"
msgstr ""
#. Tag: userinput
-#: preseed.xml:963
+#: preseed.xml:965
#, no-c-format
msgid "mail-server"
msgstr ""
#. Tag: userinput
-#: preseed.xml:966
+#: preseed.xml:968
#, no-c-format
msgid "sql-database"
msgstr ""
#. Tag: userinput
-#: preseed.xml:969
+#: preseed.xml:971
#, no-c-format
msgid "laptop"
msgstr ""
#. Tag: para
-#: preseed.xml:973
+#: preseed.xml:975
#, no-c-format
msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the <userinput>standard</userinput> task."
msgstr ""
#. Tag: para
-#: preseed.xml:979
+#: preseed.xml:981
#, no-c-format
msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well."
msgstr ""
#. Tag: screen
-#: preseed.xml:989
+#: preseed.xml:991
#, no-c-format
msgid ""
"#tasksel tasksel/first multiselect standard, web-server\n"
@@ -1298,13 +1298,13 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:994
+#: preseed.xml:996
#, no-c-format
msgid "Boot loader installation"
msgstr ""
#. Tag: screen
-#: preseed.xml:996
+#: preseed.xml:998
#, no-c-format
msgid ""
"# Grub is the default boot loader (for x86). If you want lilo installed\n"
@@ -1338,19 +1338,19 @@ msgid ""
msgstr ""
#. Tag: para
-#: preseed.xml:998
+#: preseed.xml:1000
#, no-c-format
msgid "An MD5 hash for a password for <classname>grub</classname> can be generated using <command>grub-md5-crypt</command>, or using the command from the example in <xref linkend=\"preseed-account\"/>."
msgstr ""
#. Tag: title
-#: preseed.xml:1008
+#: preseed.xml:1010
#, no-c-format
msgid "Finishing up the installation"
msgstr ""
#. Tag: screen
-#: preseed.xml:1010
+#: preseed.xml:1012
#, no-c-format
msgid ""
"# During installations from serial console, the regular virtual consoles\n"
@@ -1373,13 +1373,13 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:1015
+#: preseed.xml:1017
#, no-c-format
msgid "Preseeding other packages"
msgstr ""
#. Tag: screen
-#: preseed.xml:1017
+#: preseed.xml:1019
#, no-c-format
msgid ""
"# Depending on what software you choose to install, or if things go wrong\n"
@@ -1392,25 +1392,25 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:1024
+#: preseed.xml:1026
#, no-c-format
msgid "Advanced options"
msgstr ""
#. Tag: title
-#: preseed.xml:1027
+#: preseed.xml:1029
#, no-c-format
msgid "Running custom commands during the installation"
msgstr ""
#. Tag: para
-#: preseed.xml:1028
+#: preseed.xml:1030
#, no-c-format
msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation."
msgstr ""
#. Tag: screen
-#: preseed.xml:1036
+#: preseed.xml:1038
#, no-c-format
msgid ""
"# d-i preseeding is inherently not secure. Nothing in the installer checks\n"
@@ -1432,13 +1432,13 @@ msgid ""
msgstr ""
#. Tag: title
-#: preseed.xml:1041
+#: preseed.xml:1043
#, no-c-format
msgid "Using preseeding to change default values"
msgstr ""
#. Tag: para
-#: preseed.xml:1042
+#: preseed.xml:1044
#, no-c-format
msgid ""
"It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a question. <informalexample><screen>\n"
@@ -1448,25 +1448,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: preseed.xml:1056
+#: preseed.xml:1058
#, no-c-format
msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the <quote>?=</quote> operator, i.e. <userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput>. This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for <quote>internal</quote> parameters."
msgstr ""
#. Tag: title
-#: preseed.xml:1071
+#: preseed.xml:1073
#, no-c-format
msgid "Chainloading preconfiguration files"
msgstr ""
#. Tag: para
-#: preseed.xml:1072
+#: preseed.xml:1074
#, no-c-format
msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files."
msgstr ""
#. Tag: screen
-#: preseed.xml:1082
+#: preseed.xml:1084
#, no-c-format
msgid ""
"# More than one file can be listed, separated by spaces; all will be\n"
@@ -1494,7 +1494,7 @@ msgid ""
msgstr ""
#. Tag: para
-#: preseed.xml:1084
+#: preseed.xml:1086
#, no-c-format
msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up."
msgstr ""
diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot
index 5cbcb455a..87e449a62 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: 2008-10-17 00:09+0000\n"
+"POT-Creation-Date: 2008-10-26 00:10+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"
@@ -1820,293 +1820,287 @@ msgstr ""
#. Tag: para
#: using-d-i.xml:2343
#, no-c-format
-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 "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2350
+#: using-d-i.xml:2351
#, no-c-format
msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2356
+#: using-d-i.xml:2357
#, no-c-format
msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2365
+#: using-d-i.xml:2366
#, no-c-format
msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
msgstr ""
-#. Tag: para
-#: using-d-i.xml:2374
-#, no-c-format
-msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process."
-msgstr ""
-
#. Tag: title
-#: using-d-i.xml:2387
+#: using-d-i.xml:2381
#, no-c-format
msgid "Making Your System Bootable"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2389
+#: using-d-i.xml:2383
#, no-c-format
msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
msgstr ""
#. Tag: title
-#: using-d-i.xml:2404
+#: using-d-i.xml:2398
#, no-c-format
msgid "Detecting other operating systems"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2406
+#: using-d-i.xml:2400
#, no-c-format
msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2414
+#: using-d-i.xml:2408
#, no-c-format
msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2432
+#: using-d-i.xml:2426
#, no-c-format
msgid "Install <command>aboot</command> on a Hard Disk"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2433
+#: using-d-i.xml:2427
#, 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 ""
#. Tag: title
-#: using-d-i.xml:2453
+#: using-d-i.xml:2447
#, no-c-format
msgid "<command>palo</command>-installer"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2454
+#: using-d-i.xml:2448
#, no-c-format
msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2463
+#: using-d-i.xml:2457
#, no-c-format
msgid "hppa FIXME ( need more info )"
msgstr ""
#. Tag: title
-#: using-d-i.xml:2475
+#: using-d-i.xml:2469
#, no-c-format
msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2477
+#: using-d-i.xml:2471
#, no-c-format
msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2483
+#: using-d-i.xml:2477
#, no-c-format
msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2489
+#: using-d-i.xml:2483
#, no-c-format
msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2502
+#: using-d-i.xml:2496
#, no-c-format
msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2504
+#: using-d-i.xml:2498
#, no-c-format
msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2514
+#: using-d-i.xml:2508
#, no-c-format
msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2522
+#: using-d-i.xml:2516
#, no-c-format
msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
msgstr ""
#. Tag: term
-#: using-d-i.xml:2529
+#: using-d-i.xml:2523
#, no-c-format
msgid "Master Boot Record (MBR)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2529
+#: using-d-i.xml:2523
#, no-c-format
msgid "This way the <command>LILO</command> will take complete control of the boot process."
msgstr ""
#. Tag: term
-#: using-d-i.xml:2536
+#: using-d-i.xml:2530
#, no-c-format
msgid "new Debian partition"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2536
+#: using-d-i.xml:2530
#, no-c-format
msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader."
msgstr ""
#. Tag: term
-#: using-d-i.xml:2545
+#: using-d-i.xml:2539
#, no-c-format
msgid "Other choice"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2545
+#: using-d-i.xml:2539
#, 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 traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2555
+#: using-d-i.xml:2549
#, 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 ""
#. Tag: title
-#: using-d-i.xml:2571
+#: using-d-i.xml:2565
#, no-c-format
msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2573
+#: using-d-i.xml:2567
#, no-c-format
msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to do the actual work of loading and starting the Linux kernel."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2589
+#: using-d-i.xml:2583
#, no-c-format
msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2601
+#: using-d-i.xml:2595
#, no-c-format
msgid "Choose the correct partition!"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2603
+#: using-d-i.xml:2597
#, no-c-format
msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
msgstr ""
#. Tag: title
-#: using-d-i.xml:2618
+#: using-d-i.xml:2612
#, no-c-format
msgid "EFI Partition Contents"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2620
+#: using-d-i.xml:2614
#, no-c-format
msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
msgstr ""
#. Tag: filename
-#: using-d-i.xml:2642
+#: using-d-i.xml:2636
#, no-c-format
msgid "elilo.conf"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2643
+#: using-d-i.xml:2637
#, no-c-format
msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
msgstr ""
#. Tag: filename
-#: using-d-i.xml:2652
+#: using-d-i.xml:2646
#, no-c-format
msgid "elilo.efi"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2653
+#: using-d-i.xml:2647
#, no-c-format
msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
msgstr ""
#. Tag: filename
-#: using-d-i.xml:2663
+#: using-d-i.xml:2657
#, no-c-format
msgid "initrd.img"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2664
+#: using-d-i.xml:2658
#, no-c-format
msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
msgstr ""
#. Tag: filename
-#: using-d-i.xml:2676
+#: using-d-i.xml:2670
#, no-c-format
msgid "readme.txt"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2677
+#: using-d-i.xml:2671
#, no-c-format
msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
msgstr ""
#. Tag: filename
-#: using-d-i.xml:2687
+#: using-d-i.xml:2681
#, no-c-format
msgid "vmlinuz"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2688
+#: using-d-i.xml:2682
#, no-c-format
msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2708
+#: using-d-i.xml:2702
#, no-c-format
msgid "<command>arcboot</command>-installer"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2709
+#: using-d-i.xml:2703
#, 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"
@@ -2119,289 +2113,289 @@ msgid ""
msgstr ""
#. Tag: replaceable
-#: using-d-i.xml:2728
+#: using-d-i.xml:2722
#, no-c-format
msgid "scsi"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2729
+#: using-d-i.xml:2723
#, no-c-format
msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
msgstr ""
#. Tag: replaceable
-#: using-d-i.xml:2737
+#: using-d-i.xml:2731
#, no-c-format
msgid "disk"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2738
+#: using-d-i.xml:2732
#, no-c-format
msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
msgstr ""
#. Tag: replaceable
-#: using-d-i.xml:2746
+#: using-d-i.xml:2740
#, no-c-format
msgid "partnr"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2747
+#: using-d-i.xml:2741
#, no-c-format
msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
msgstr ""
#. Tag: replaceable
-#: using-d-i.xml:2755
+#: using-d-i.xml:2749
#, no-c-format
msgid "config"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2756
+#: using-d-i.xml:2750
#, no-c-format
msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2777
+#: using-d-i.xml:2771
#, no-c-format
msgid "Install <command>Yaboot</command> on a Hard Disk"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2778
+#: using-d-i.xml:2772
#, no-c-format
msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2796
+#: using-d-i.xml:2790
#, no-c-format
msgid "Install <command>Quik</command> on a Hard Disk"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2797
+#: using-d-i.xml:2791
#, no-c-format
msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2813
+#: using-d-i.xml:2807
#, no-c-format
msgid "<command>zipl</command>-installer"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2814
+#: using-d-i.xml:2808
#, no-c-format
msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2831
+#: using-d-i.xml:2825
#, no-c-format
msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2833
+#: using-d-i.xml:2827
#, no-c-format
msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2858
+#: using-d-i.xml:2852
#, no-c-format
msgid "Continue Without Boot Loader"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2860
+#: using-d-i.xml:2854
#, no-c-format
msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2869
+#: using-d-i.xml:2863
#, no-c-format
msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2886
+#: using-d-i.xml:2880
#, no-c-format
msgid "Finishing the Installation"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2887
+#: using-d-i.xml:2881
#, no-c-format
msgid "This is the last step in the Debian installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2900
+#: using-d-i.xml:2894
#, no-c-format
msgid "Setting the System Clock"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2902
+#: using-d-i.xml:2896
#, no-c-format
msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2909
+#: using-d-i.xml:2903
#, 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 UTC.</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 UTC.</phrase>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2920
+#: using-d-i.xml:2914
#, no-c-format
msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2935
+#: using-d-i.xml:2929
#, no-c-format
msgid "Reboot the System"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2937
+#: using-d-i.xml:2931
#, no-c-format
msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new Debian system."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2943
+#: using-d-i.xml:2937
#, no-c-format
msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian; from the DASD which you selected for the root filesystem during the first steps of the installation."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2956
+#: using-d-i.xml:2950
#, no-c-format
msgid "Miscellaneous"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2957
+#: using-d-i.xml:2951
#, no-c-format
msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2970
+#: using-d-i.xml:2964
#, no-c-format
msgid "Saving the installation logs"
msgstr ""
#. Tag: para
-#: using-d-i.xml:2972
+#: using-d-i.xml:2966
#, no-c-format
msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system."
msgstr ""
#. Tag: para
-#: using-d-i.xml:2979
+#: using-d-i.xml:2973
#, no-c-format
msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report."
msgstr ""
#. Tag: title
-#: using-d-i.xml:2999
+#: using-d-i.xml:2993
#, no-c-format
msgid "Using the Shell and Viewing the Logs"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3001
+#: using-d-i.xml:2995
#, no-c-format
msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap> and the <keycap>F2</keycap> function key at the same time. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to the installer itself."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3019
+#: using-d-i.xml:3013
#, no-c-format
msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3023
+#: using-d-i.xml:3017
#, no-c-format
msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3031
+#: using-d-i.xml:3025
#, no-c-format
msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3040
+#: using-d-i.xml:3034
#, no-c-format
msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3047
+#: using-d-i.xml:3041
#, no-c-format
msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3053
+#: using-d-i.xml:3047
#, 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:3068
+#: using-d-i.xml:3062
#, no-c-format
msgid "Installation Over the Network"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3070
+#: using-d-i.xml:3064
#, no-c-format
msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3080
+#: using-d-i.xml:3074
#, no-c-format
msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3093
+#: using-d-i.xml:3087
#, no-c-format
msgid "For installations on &arch-title;, this is the default method after setting up the network."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3098
+#: using-d-i.xml:3092
#, no-c-format
msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3110
+#: using-d-i.xml:3104
#, no-c-format
msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3116
+#: using-d-i.xml:3110
#, 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"
@@ -2410,127 +2404,127 @@ msgid ""
msgstr ""
#. Tag: para
-#: using-d-i.xml:3133
+#: using-d-i.xml:3127
#, no-c-format
msgid "The <command>ssh</command> server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations &mdash; depending on your local network setup &mdash; the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3146
+#: using-d-i.xml:3140
#, no-c-format
msgid "You may be able to avoid the connection being dropped by adding the option <userinput>-o&nbsp;ServerAliveInterval=<replaceable>value</replaceable></userinput> when starting the <command>ssh</command> connection, or by adding that option in your <command>ssh</command> configuration file. Note however that in some cases adding this option may also <emphasis>cause</emphasis> a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which <command>ssh</command> would otherwise have recovered), so it should only be used when needed."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3159
+#: using-d-i.xml:3153
#, no-c-format
msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename><footnote> <para> The following command will remove an existing entry for a host: <command>ssh-keygen -R &lt;<replaceable>hostname</replaceable>|<replaceable>IP&nbsp;address</replaceable>&gt;</command>. </para> </footnote> and try again."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3175
+#: using-d-i.xml:3169
#, no-c-format
msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3185
+#: using-d-i.xml:3179
#, no-c-format
msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system."
msgstr ""
#. Tag: title
-#: using-d-i.xml:3205
+#: using-d-i.xml:3199
#, no-c-format
msgid "Loading Missing Firmware"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3206
+#: using-d-i.xml:3200
#, no-c-format
msgid "As described in <xref linkend=\"hardware-firmware\"/>, some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3214
+#: using-d-i.xml:3208
#, no-c-format
msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (<filename>/lib/firmware</filename>) and the driver module will be reloaded."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3224
+#: using-d-i.xml:3218
#, no-c-format
msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. <phrase arch=\"x86\">On i386 and amd64 firmware can also be loaded from an MMC or SD card.</phrase>"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3234
+#: using-d-i.xml:3228
#, no-c-format
msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3241
+#: using-d-i.xml:3235
#, no-c-format
msgid "Support for loading firmware is still relatively basic and is likely to be improved in future releases of the installer. Currently &d-i; will for example not display any warning if you choose to load missing firmware, but the requested firmware is not found. Please report any issues you encounter by filing an installation report (see <xref linkend=\"submit-bug\"/>)."
msgstr ""
#. Tag: title
-#: using-d-i.xml:3252
+#: using-d-i.xml:3246
#, no-c-format
msgid "Preparing a medium"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3253
+#: using-d-i.xml:3247
#, no-c-format
msgid "Although in some cases the firmware can also be loaded from a partition on a hard disk, the most common method to load firmware will be from some removable medium such as a floppy disk or a USB stick. The firmware files or packages must be placed in either the root directory or a directory named <filename>/firmware</filename> of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3263
+#: using-d-i.xml:3257
#, no-c-format
msgid "Tarballs containing current packages for the most common firmware are available from: <itemizedlist> <listitem><para> <ulink url=\"&url-firmware-tarballs;\"></ulink> </para></listitem> </itemizedlist> Just download the tarball for the correct release and unpack it to the file system on the medium."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3277
+#: using-d-i.xml:3271
#, no-c-format
msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3291
+#: using-d-i.xml:3285
#, no-c-format
msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor."
msgstr ""
#. Tag: title
-#: using-d-i.xml:3300
+#: using-d-i.xml:3294
#, no-c-format
msgid "Firmware and the Installed System"
msgstr ""
#. Tag: para
-#: using-d-i.xml:3301
+#: using-d-i.xml:3295
#, no-c-format
msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3310
+#: using-d-i.xml:3304
#, no-c-format
msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's <filename>sources.list</filename>. This has the advantage that the firmware should be updated automatically if a new version becomes available."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3318
+#: using-d-i.xml:3312
#, no-c-format
msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually."
msgstr ""
#. Tag: para
-#: using-d-i.xml:3325
+#: using-d-i.xml:3319
#, no-c-format
msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will <emphasis>not</emphasis> be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed."
msgstr ""