Update po and pot files after changings in en

1 files changed, 2 insertions, 32 deletions

diff --git a/po/ru/boot-new.po b/po/ru/boot-new.po
index d8469a6c6..4b72f39ba 100644
--- a/po/ru/boot-new.po
+++ b/po/ru/boot-new.po
@@ -276,11 +276,6 @@ 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."
 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 "
@@ -417,25 +412,13 @@ msgid ""
 "filename> or <filename>/srv</filename>. You can simply mount them manually "
 "after the boot."
 msgstr ""
-"Самый простой случай — шифрованные тома с данными <filename>/home</"
-"filename> или <filename>/srv</filename>. Вы можете просто смонтировать их "
-"вручную "
+"Самый простой случай — шифрованные тома с данными <filename>/home</filename> "
+"или <filename>/srv</filename>. Вы можете просто смонтировать их вручную "
 "после загрузки машины."
 
 #. Tag: para
 #: 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"
-#| "<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:"
 msgid ""
 "However for dm-crypt this is a bit tricky. First you need to register the "
 "volumes with <application>device mapper</application> by running: "
@@ -472,19 +455,6 @@ msgstr ""
 #. Tag: para
 #: boot-new.xml:244
 #, no-c-format
-#| msgid ""
-#| "If any volume holding noncritical system files could not be mounted "
-#| "(<filename>/usr</filename> or <filename>/var</filename>), the system "
-#| "should still boot and you should be able to mount the volumes manually "
-#| "like in the previous case. However, you will also need to (re)start any "
-#| "services usually running in your default runlevel because it is very "
-#| "likely that they were not started. The easiest way to achieve this is by "
-#| "switching to the first runlevel and back by entering "
-#| "<informalexample><screen>\n"
-#| "<prompt>#</prompt> <userinput>init 1</userinput>\n"
-#| "</screen></informalexample> at the shell prompt and pressing <keycombo> "
-#| "<keycap>Control</keycap> <keycap>D</keycap> </keycombo> when asked for "
-#| "the root password."
 msgid ""
 "If any volume holding noncritical system files could not be mounted "
 "(<filename>/usr</filename> or <filename>/var</filename>), the system should "