diff options
Diffstat (limited to 'po/pot/boot-new.pot')
| -rw-r--r-- | po/pot/boot-new.pot | 79 |
1 files changed, 24 insertions, 55 deletions
diff --git a/po/pot/boot-new.pot b/po/pot/boot-new.pot index ed8d2658a..4dd59fa11 100644 --- a/po/pot/boot-new.pot +++ b/po/pot/boot-new.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: 2014-01-29 10:50+0000\n" +"POT-Creation-Date: 2014-08-26 20:40+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" @@ -125,17 +125,11 @@ msgstr "" #. Tag: para #: boot-new.xml:147 #, no-c-format -msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot. The actual procedure differs slightly between dm-crypt and loop-AES." -msgstr "" - -#. Tag: title -#: boot-new.xml:157 -#, no-c-format -msgid "dm-crypt" +msgid "If you created encrypted volumes during the installation and assigned them mount points, you will be asked to enter the passphrase for each of these volumes during the boot." msgstr "" #. Tag: para -#: boot-new.xml:159 +#: boot-new.xml:155 #, no-c-format msgid "" "For partitions encrypted using dm-crypt you will be shown the following prompt during the boot: <informalexample><screen>\n" @@ -145,13 +139,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-new.xml:182 +#: boot-new.xml:178 #, no-c-format msgid "The prompt may look somewhat different when an encrypted root file system is mounted. This depends on which initramfs generator was used to generate the initrd used to boot the system. The example below is for an initrd generated using <classname>initramfs-tools</classname>:" msgstr "" #. Tag: screen -#: boot-new.xml:189 +#: boot-new.xml:185 #, no-c-format msgid "" "Begin: Mounting <emphasis>root file system</emphasis>... ...\n" @@ -160,119 +154,94 @@ msgid "" msgstr "" #. Tag: para -#: boot-new.xml:191 boot-new.xml:216 +#: boot-new.xml:187 #, no-c-format msgid "No characters (even asterisks) will be shown while entering the passphrase. If you enter the wrong passphrase, you have two more tries to correct it. After the third try the boot process will skip this volume and continue to mount the next filesystem. Please see <xref linkend=\"crypto-troubleshooting\"/> for further information." msgstr "" #. Tag: para -#: boot-new.xml:199 boot-new.xml:224 +#: boot-new.xml:195 #, no-c-format msgid "After entering all passphrases the boot should continue as usual." msgstr "" #. Tag: title -#: boot-new.xml:207 -#, no-c-format -msgid "loop-AES" -msgstr "" - -#. Tag: para -#: boot-new.xml:209 -#, no-c-format -msgid "For partitions encrypted using loop-AES you will be shown the following prompt during the boot:" -msgstr "" - -#. Tag: screen -#: boot-new.xml:214 -#, no-c-format -msgid "" - "Checking loop-encrypted file systems.\n" - "Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>)\n" - "Password:" -msgstr "" - -#. Tag: title -#: boot-new.xml:232 +#: boot-new.xml:202 #, no-c-format msgid "Troubleshooting" msgstr "" #. Tag: para -#: boot-new.xml:234 +#: boot-new.xml:204 #, no-c-format msgid "If some of the encrypted volumes could not be mounted because a wrong passphrase was entered, you will have to mount them manually after the boot. There are several cases." msgstr "" #. Tag: para -#: boot-new.xml:243 +#: boot-new.xml:213 #, no-c-format msgid "The first case concerns the root partition. When it is not mounted correctly, the boot process will halt and you will have to reboot the computer to try again." msgstr "" #. Tag: para -#: boot-new.xml:250 +#: boot-new.xml:220 #, no-c-format -msgid "" - "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot. For loop-AES this is a one-step operation: <informalexample><screen>\n" - "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>\n" - "<prompt>Password:</prompt>\n" - "</screen></informalexample> where <replaceable>/mount_point</replaceable> should be replaced by the particular directory (e.g. <filename>/home</filename>). The only difference from an ordinary mount is that you will be asked to enter the passphrase for this volume." +msgid "The easiest case is for encrypted volumes holding data like <filename>/home</filename> or <filename>/srv</filename>. You can simply mount them manually after the boot." msgstr "" #. Tag: para -#: boot-new.xml:264 +#: boot-new.xml:226 #, no-c-format msgid "" - "For dm-crypt this is a bit trickier. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n" + "However for dm-crypt this is a bit tricky. First you need to register the volumes with <application>device mapper</application> by running: <informalexample><screen>\n" "<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>\n" "</screen></informalexample> This will scan all volumes mentioned in <filename>/etc/crypttab</filename> and will create appropriate devices under the <filename>/dev</filename> directory after entering the correct passphrases. (Already registered volumes will be skipped, so you can repeat this command several times without worrying.) After successful registration you can simply mount the volumes the usual way:" msgstr "" #. Tag: screen -#: boot-new.xml:279 +#: boot-new.xml:241 #, no-c-format msgid "<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>" msgstr "" #. Tag: para -#: boot-new.xml:282 +#: boot-new.xml:244 #, no-c-format msgid "If any volume holding noncritical system files could not be mounted (<filename>/usr</filename> or <filename>/var</filename>), the system should still boot and you should be able to mount the volumes manually like in the previous case. However, you will also need to (re)start any services usually running in your default runlevel because it is very likely that they were not started. The easiest way is to just reboot the computer." msgstr "" #. Tag: title -#: boot-new.xml:300 +#: boot-new.xml:262 #, no-c-format msgid "Log In" msgstr "" #. Tag: para -#: boot-new.xml:302 +#: boot-new.xml:264 #, no-c-format msgid "Once your system boots, you'll be presented with the login prompt. Log in using the personal login and password you selected during the installation process. Your system is now ready for use." msgstr "" #. Tag: para -#: boot-new.xml:308 +#: boot-new.xml:270 #, no-c-format msgid "If you are a new user, you may want to explore the documentation which is already installed on your system as you start to use it. There are currently several documentation systems, work is proceeding on integrating the different types of documentation. Here are a few starting points." msgstr "" #. Tag: para -#: boot-new.xml:316 +#: boot-new.xml:278 #, no-c-format msgid "Documentation accompanying programs you have installed can be found in <filename>/usr/share/doc/</filename>, under a subdirectory named after the program (or, more precise, the &debian; package that contains the program). However, more extensive documentation is often packaged separately in special documentation packages that are mostly not installed by default. For example, documentation about the package management tool <command>apt</command> can be found in the packages <classname>apt-doc</classname> or <classname>apt-howto</classname>." msgstr "" #. Tag: para -#: boot-new.xml:327 +#: boot-new.xml:289 #, no-c-format msgid "In addition, there are some special folders within the <filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</emphasis> (compressed) format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. After installing <classname>dhelp</classname>, you will find a browsable index of documentation in <filename>/usr/share/doc/HTML/index.html</filename>." msgstr "" #. Tag: para -#: boot-new.xml:336 +#: boot-new.xml:298 #, no-c-format msgid "" "One easy way to view these documents using a text based browser is to enter the following commands: <informalexample><screen>\n" @@ -282,13 +251,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-new.xml:346 +#: boot-new.xml:308 #, no-c-format msgid "If you have a graphical desktop environment installed, you can also use its web browser. Start the web browser from the application menu and enter <userinput>/usr/share/doc/</userinput> in the address bar." msgstr "" #. Tag: para -#: boot-new.xml:352 +#: boot-new.xml:314 #, no-c-format msgid "You can also type <userinput>info <replaceable>command</replaceable></userinput> or <userinput>man <replaceable>command</replaceable></userinput> to see documentation on most commands available at the command prompt. Typing <userinput>help</userinput> will display help on shell commands. And typing a command followed by <userinput>--help</userinput> will usually display a short summary of the command's usage. If a command's results scroll past the top of the screen, type <userinput>| more</userinput> after the command to cause the results to pause before scrolling past the top of the screen. To see a list of all commands available which begin with a certain letter, type the letter and then two tabs." msgstr "" |