[CVS] di-docs/post-install kernel-baking.po,1.3,1.4 reactivating-win.po,1.3,1.4
Update of /cvsroot/l10n-russian/di-docs/post-install
In directory haydn:/tmp/cvs-serv22208/post-install
Modified Files:
kernel-baking.po reactivating-win.po
Log Message:
Автоматическая синхронизация шаблонов
Index: kernel-baking.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/post-install/kernel-baking.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- kernel-baking.po 10 Sep 2004 13:31:24 -0000 1.3
+++ kernel-baking.po 13 Oct 2004 00:25:51 -0000 1.4
@@ -70,7 +70,7 @@
#. Tag: para
#: kernel-baking.xml:44
#, no-c-format
-msgid "run a updated or development kernel"
+msgid "run an updated or development kernel"
msgstr ""
#. Tag: para
Index: reactivating-win.po
===================================================================
RCS file: /cvsroot/l10n-russian/di-docs/post-install/reactivating-win.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- reactivating-win.po 10 Sep 2004 13:31:24 -0000 1.3
+++ reactivating-win.po 13 Oct 2004 00:25:51 -0000 1.4
@@ -14,44 +14,81 @@
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: ENCODING\n"
+#. Tag: title
#: reactivating-win.xml:6
#, no-c-format
-#. Tag: title
msgid "Reactivating DOS and Windows"
msgstr ""
+#. Tag: para
#: reactivating-win.xml:7
#, no-c-format
-#. Tag: para
-msgid "After installing the base system and writing to the <emphasis>Master Boot Record</emphasis>, you will be able boot Linux, but probably nothing else. This depends what you have chosen during the installation. This chapter will describe how you can reactivate your old systems so that you can also boot your DOS or Windows again."
+msgid ""
+"After installing the base system and writing to the <emphasis>Master Boot "
+"Record</emphasis>, you will be able to boot Linux, but probably nothing "
+"else. This depends what you have chosen during the installation. This "
+"chapter will describe how you can reactivate your old systems so that you "
+"can also boot your DOS or Windows again."
msgstr ""
+#. Tag: para
#: reactivating-win.xml:15
#, no-c-format
-#. Tag: para
-msgid "<command>LILO</command> is a boot manager with which you can also boot other operating systems than Linux, which complies to PC conventions. The boot manager is configured via <filename>/etc/lilo.conf</filename> file. Whenever you edited this file you have to run <command>lilo</command> afterwards. The reason for this is that the changes will take place only when you call the program."
+msgid ""
+"<command>LILO</command> is a boot manager with which you can also boot other "
+"operating systems than Linux, which complies to PC conventions. The boot "
+"manager is configured via <filename>/etc/lilo.conf</filename> file. Whenever "
+"you edited this file you have to run <command>lilo</command> afterwards. The "
+"reason for this is that the changes will take place only when you call the "
+"program."
msgstr ""
+#. Tag: para
#: reactivating-win.xml:25
#, no-c-format
-#. Tag: para
-msgid "Important parts of the <filename>lilo.conf</filename> file are the lines containing the <userinput>image</userinput> and <userinput>other</userinput> keywords, as well as the lines following those. They can be used to describe a system which can be booted by <command>LILO</command>. Such a system can include a kernel (<userinput>image</userinput>), a root partition, additional kernel parameters, etc. as well as a configuration to boot another, non-Linux (<userinput>other</userinput>) operating system. These keywords can also be used more than once. The ordering of these systems within the configuration file is important because it determines which system will be booted automatically after, for instance, a timeout (<userinput>delay</userinput>) presuming <command>LILO</command> wasn't stopped by pressing the <keycap>shift</keycap> key."
+msgid ""
+"Important parts of the <filename>lilo.conf</filename> file are the lines "
+"containing the <userinput>image</userinput> and <userinput>other</userinput> "
+"keywords, as well as the lines following those. They can be used to describe "
+"a system which can be booted by <command>LILO</command>. Such a system can "
+"include a kernel (<userinput>image</userinput>), a root partition, "
+"additional kernel parameters, etc. as well as a configuration to boot "
+"another, non-Linux (<userinput>other</userinput>) operating system. These "
+"keywords can also be used more than once. The ordering of these systems "
+"within the configuration file is important because it determines which "
+"system will be booted automatically after, for instance, a timeout "
+"(<userinput>delay</userinput>) presuming <command>LILO</command> wasn't "
+"stopped by pressing the <keycap>shift</keycap> key."
msgstr ""
+#. Tag: para
#: reactivating-win.xml:41
#, no-c-format
-#. Tag: para
msgid ""
- "After a fresh install of Debian, just the current system is configured for booting with <command>LILO</command>. If you want to boot another Linux kernel, you have to edit the configuration file <filename>/etc/lilo.conf</filename> to add the following lines: <informalexample><screen>\n"
- "\n"
- "&additional-lilo-image;\n"
- "\n"
- "</screen></informalexample> For a basic setup just the first two lines are necessary. If you want to know more about the other two options please have a look at the <command>LILO</command> documentation. This can be found in <filename>/usr/share/doc/lilo/</filename>. The file which should be read is <filename>Manual.txt</filename>. To have a quicker start into the world of booting a system you can also look at the <command>LILO</command> man pages <filename>lilo.conf</filename> for an overview of configuration keywords and <filename>lilo</filename> for description of the installation of the new configuration into the boot sector."
+"After a fresh install of Debian, just the current system is configured for "
+"booting with <command>LILO</command>. If you want to boot another Linux "
+"kernel, you have to edit the configuration file <filename>/etc/lilo.conf</"
+"filename> to add the following lines: <informalexample><screen>\n"
+"\n"
+"&additional-lilo-image;\n"
+"\n"
+"</screen></informalexample> For a basic setup just the first two lines are "
+"necessary. If you want to know more about the other two options please have "
+"a look at the <command>LILO</command> documentation. This can be found in "
+"<filename>/usr/share/doc/lilo/</filename>. The file which should be read is "
+"<filename>Manual.txt</filename>. To have a quicker start into the world of "
+"booting a system you can also look at the <command>LILO</command> man pages "
+"<filename>lilo.conf</filename> for an overview of configuration keywords and "
+"<filename>lilo</filename> for description of the installation of the new "
+"configuration into the boot sector."
msgstr ""
+#. Tag: para
#: reactivating-win.xml:61
#, no-c-format
-#. Tag: para
-msgid "Notice that there are other boot loaders available in &debian;, such as GRUB (in <classname>grub</classname> package), CHOS (in <classname>chos</classname> package), Extended-IPL (in <classname>extipl</classname> package), loadlin (in <classname>loadlin</classname> package) etc."
+msgid ""
+"Notice that there are other boot loaders available in &debian;, such as GRUB "
+"(in <classname>grub</classname> package), CHOS (in <classname>chos</"
+"classname> package), Extended-IPL (in <classname>extipl</classname> "
+"package), loadlin (in <classname>loadlin</classname> package) etc."
msgstr ""
-
Reply to: