install-guide/po fedora-install-guide.pot,1.3,1.4
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15283/po
Modified Files:
fedora-install-guide.pot
Log Message:
- Minor amendment to example servers, for consistency.
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.3 -r 1.4 fedora-install-guide.pot
Index: fedora-install-guide.pot
===================================================================
RCS file: /cvs/docs/install-guide/po/fedora-install-guide.pot,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fedora-install-guide.pot 6 Mar 2006 02:23:03 -0000 1.3
+++ fedora-install-guide.pot 7 May 2006 14:37:38 -0000 1.4
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-05 20:19-0600\n"
+"POT-Creation-Date: 2006-05-03 22:30+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL(a)li.org>\n"
@@ -9,2779 +9,2943 @@
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+#: en_US/entities.xml:5(title) en_US/entities.xml:5(title)
+msgid "These entities are local to the Fedora Installation Guide."
+msgstr ""
+
+#: en_US/entities.xml:8(comment) en_US/entities.xml:8(comment)
+msgid "Document base name"
+msgstr ""
+
+#: en_US/entities.xml:9(text) en_US/entities.xml:9(text)
+msgid "fedora-install-guide"
+msgstr ""
+
+#: en_US/entities.xml:12(comment) en_US/entities.xml:12(comment)
+msgid "Document language"
+msgstr ""
+
+#: en_US/entities.xml:13(text) en_US/entities.xml:13(text)
+msgid "en_US"
+msgstr ""
+
+#: en_US/entities.xml:16(comment) en_US/entities.xml:16(comment)
+msgid "Document version"
+msgstr ""
+
+#: en_US/entities.xml:17(text) en_US/entities.xml:17(text)
+msgid "1.32"
+msgstr ""
+
+#: en_US/entities.xml:20(comment) en_US/entities.xml:20(comment)
+msgid "Document date"
+msgstr ""
+
+#: en_US/entities.xml:21(text) en_US/entities.xml:21(text)
+msgid "2006-30-04"
+msgstr ""
+
+#: en_US/entities.xml:24(comment) en_US/entities.xml:24(comment)
+msgid "Document ID string"
+msgstr ""
+
+#: en_US/entities.xml:25(text) en_US/entities.xml:25(text)
+msgid "<use entity=\"DOCNAME\"/>-<use entity=\"DOCLANG\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE\"/>)"
+msgstr ""
+
+#: en_US/entities.xml:31(comment) en_US/entities.xml:31(comment)
+msgid "Local version of Fedora Core"
+msgstr ""
+
+#: en_US/entities.xml:32(text) en_US/entities.xml:32(text)
+msgid "5"
+msgstr ""
+
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
-#: en/fedora-install-guide-upgrading.xml:41(None)
+#: en_US/fedora-install-guide-upgrading.xml:41(None)
msgid "@@image: './figs/upgrade.eps'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
-#: en/fedora-install-guide-upgrading.xml:44(None)
+#: en_US/fedora-install-guide-upgrading.xml:44(None)
msgid "@@image: './figs/upgrade.png'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
-#: en/fedora-install-guide-upgrading.xml:94(None)
+#: en_US/fedora-install-guide-upgrading.xml:94(None)
msgid "@@image: './figs/upgradebootloader.eps'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
-#: en/fedora-install-guide-upgrading.xml:97(None)
+#: en_US/fedora-install-guide-upgrading.xml:97(None)
msgid "@@image: './figs/upgradebootloader.png'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:16(title)
+#: en_US/fedora-install-guide-upgrading.xml:16(title)
msgid "Upgrading an Existing System"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:18(para)
-msgid "The installation system automatically detects any existing installation of &FC;. The upgrade process updates the existing system software with new versions, but does not remove any data from users' home directories. The existing partition structure on your hard drives does not change. Your system configuration changes only if a package upgrade demands it. Most package upgrades do not change system configuration, but rather install an additional configuration file for you to examine later."
+#: en_US/fedora-install-guide-upgrading.xml:18(para)
+msgid "The installation system automatically detects any existing installation of Fedora Core. The upgrade process updates the existing system software with new versions, but does not remove any data from users' home directories. The existing partition structure on your hard drives does not change. Your system configuration changes only if a package upgrade demands it. Most package upgrades do not change system configuration, but rather install an additional configuration file for you to examine later."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:30(title)
+#: en_US/fedora-install-guide-upgrading.xml:30(title)
msgid "Upgrade Examine"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:32(para)
-msgid "If your system contains a &FC; or &RHL; installation, the following screen appears:"
+#: en_US/fedora-install-guide-upgrading.xml:32(para)
+msgid "If your system contains a Fedora Core or Red Hat Linux installation, the following screen appears:"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:38(title)
+#: en_US/fedora-install-guide-upgrading.xml:38(title)
msgid "Upgrade Examine Screen"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:47(phrase)
+#: en_US/fedora-install-guide-upgrading.xml:47(phrase)
msgid "Upgrade examine screen."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:54(para)
+#: en_US/fedora-install-guide-upgrading.xml:54(para)
msgid "To perform an upgrade of an existing system, choose the appropriate installation from the drop-down list and select <guibutton>Next</guibutton>."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:61(title)
+#: en_US/fedora-install-guide-upgrading.xml:61(title)
msgid "Manually Installed Software"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:62(para)
-msgid "Software which you have installed manually on your existing &FC; or &RHL; system may behave differently after an upgrade. You may need to manually recompile this software after an upgrade to ensure it performs correctly on the updated system."
+#: en_US/fedora-install-guide-upgrading.xml:62(para)
+msgid "Software which you have installed manually on your existing Fedora Core or Red Hat Linux system may behave differently after an upgrade. You may need to manually recompile this software after an upgrade to ensure it performs correctly on the updated system."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:73(title)
+#: en_US/fedora-install-guide-upgrading.xml:73(title)
msgid "Upgrading Boot Loader Configuration"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:75(para)
-msgid "<indexterm><primary>boot loader</primary><secondary>upgrading</secondary></indexterm> Your completed &FC; installation must be registered in the <indexterm><primary>boot loader</primary><seealso>GRUB</seealso></indexterm><firstterm>boot loader</firstterm> to boot properly. A boot loader is software on your machine that locates and starts the operating system. Refer to <xref linkend=\"ch-bootloader\"/> for more information about boot loaders."
+#: en_US/fedora-install-guide-upgrading.xml:75(para)
+msgid "<indexterm><primary>boot loader</primary><secondary>upgrading</secondary></indexterm> Your completed Fedora Core installation must be registered in the <indexterm><primary>boot loader</primary><seealso>GRUB</seealso></indexterm><firstterm>boot loader</firstterm> to boot properly. A boot loader is software on your machine that locates and starts the operating system. Refer to <xref linkend=\"ch-bootloader\"/> for more information about boot loaders."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:91(title)
+#: en_US/fedora-install-guide-upgrading.xml:91(title)
msgid "Upgrade Bootloader Screen"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:100(phrase)
+#: en_US/fedora-install-guide-upgrading.xml:100(phrase)
msgid "Upgrade bootloader screen."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:107(para)
-msgid "If the existing boot loader was installed by a Linux distribution, the installation system can modify it to load the new &FC; system. To update the existing Linux boot loader, select <guilabel>Update boot loader configuration</guilabel>. This is the default behavior when you upgrade an existing &FC; or &RHL; installation."
+#: en_US/fedora-install-guide-upgrading.xml:107(para)
+msgid "If the existing boot loader was installed by a Linux distribution, the installation system can modify it to load the new Fedora Core system. To update the existing Linux boot loader, select <guilabel>Update boot loader configuration</guilabel>. This is the default behavior when you upgrade an existing Fedora Core or Red Hat Linux installation."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:115(para)
-msgid "<firstterm>GRUB</firstterm> is the standard boot loader for &FED;. If your machine uses another boot loader, such as <trademark>BootMagic</trademark>, <trademark>System Commander</trademark>, or the loader installed by Microsoft Windows, then the &FED; installation system cannot update it. In this case, select <guilabel>Skip boot loader updating</guilabel>. When the installation process completes, refer to the documentation for your product for assistance."
+#: en_US/fedora-install-guide-upgrading.xml:115(para)
+msgid "<firstterm>GRUB</firstterm> is the standard boot loader for Fedora. If your machine uses another boot loader, such as <trademark>BootMagic</trademark>, <trademark>System Commander</trademark>, or the loader installed by Microsoft Windows, then the Fedora installation system cannot update it. In this case, select <guilabel>Skip boot loader updating</guilabel>. When the installation process completes, refer to the documentation for your product for assistance."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:126(para)
+#: en_US/fedora-install-guide-upgrading.xml:126(para)
msgid "Install a new boot loader as part of an upgrade process only if you are certain you want to replace the existing boot loader. If you install a new boot loader, you may not be able to boot other operating systems on the same machine until you have configured the new boot loader. Select <guilabel>Create new boot loader configuration</guilabel> to remove the existing boot loader and install GRUB."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:136(para)
+#: en_US/fedora-install-guide-upgrading.xml:136(para)
msgid "After you make your selection, click <guibutton>Next</guibutton> to continue."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
-#: en/fedora-install-guide-timezone.xml:36(None)
+#: en_US/fedora-install-guide-timezone.xml:36(None)
msgid "@@image: './figs/timezone.eps'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
[...4610 lines suppressed...]
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1062(option)
+#: en_US/fedora-install-guide-adminoptions.xml:1066(option)
msgid "isa"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1070(title)
+#: en_US/fedora-install-guide-adminoptions.xml:1074(title)
msgid "Additional Screen"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1072(para)
+#: en_US/fedora-install-guide-adminoptions.xml:1076(para)
msgid "The <option>isa</option> option causes the system to display an additional text screen at the beginning of the installation process. Use this screen to configure the ISA devices on your computer."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1082(title)
+#: en_US/fedora-install-guide-adminoptions.xml:1086(title)
msgid "Using the Maintenance Boot Modes"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1085(title)
+#: en_US/fedora-install-guide-adminoptions.xml:1089(title)
msgid "Loading the Memory (RAM) Testing Mode"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1087(para)
-msgid "Faults in memory modules may cause your system to freeze or crash unpredictably. In some cases, memory faults may only cause errors with particular combinations of software. For this reason, you should test the memory of a computer before you install &FED; for the first time, even if it has previously run other operating systems."
+#: en_US/fedora-install-guide-adminoptions.xml:1091(para)
+msgid "Faults in memory modules may cause your system to freeze or crash unpredictably. In some cases, memory faults may only cause errors with particular combinations of software. For this reason, you should test the memory of a computer before you install Fedora for the first time, even if it has previously run other operating systems."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1096(para)
+#: en_US/fedora-install-guide-adminoptions.xml:1100(para)
msgid "To boot your computer in <indexterm><primary>memory testing mode</primary></indexterm> memory testing mode, enter <userinput>memtest86</userinput> at the <prompt>boot:</prompt> prompt. The first test starts immediately. By default, <command>memtest86</command> carries out a total of ten tests."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1108(para)
+#: en_US/fedora-install-guide-adminoptions.xml:1112(para)
msgid "To halt the tests and reboot your computer, enter <keycap>Esc</keycap> at any time."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1115(title)
+#: en_US/fedora-install-guide-adminoptions.xml:1119(title)
msgid "Booting Your Computer with the Rescue Mode"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1117(primary)
+#: en_US/fedora-install-guide-adminoptions.xml:1121(primary)
msgid "rescue mode"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1119(para)
-msgid "You may boot a command-line Linux system from either a <indexterm><primary>rescue discs</primary></indexterm> rescue disc or the first installation disc, without installing &FED; on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair systems that are already installed on your computer."
+#: en_US/fedora-install-guide-adminoptions.xml:1123(para)
+msgid "You may boot a command-line Linux system from either a <indexterm><primary>rescue discs</primary></indexterm> rescue disc or the first installation disc, without installing Fedora on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair systems that are already installed on your computer."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1130(para)
+#: en_US/fedora-install-guide-adminoptions.xml:1134(para)
msgid "The rescue disc starts the rescue mode system by default. To load the rescue system with the first installation disc, enter:"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1135(userinput)
+#: en_US/fedora-install-guide-adminoptions.xml:1139(userinput)
#, no-wrap
msgid "linux rescue"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1137(para)
+#: en_US/fedora-install-guide-adminoptions.xml:1141(para)
msgid "Specify the language, keyboard layout and network settings for the rescue system with the screens that follow. The final setup screen configures access to the existing system on your computer."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1144(para)
+#: en_US/fedora-install-guide-adminoptions.xml:1148(para)
msgid "By default, rescue mode attaches an existing operating system to the rescue system under the directory <filename>/mnt/sysimage/</filename>."
msgstr ""
-#: en/fedora-install-guide-acknowledgements.xml:16(title)
+#: en_US/fedora-install-guide-acknowledgements.xml:16(title)
msgid "Acknowledgements"
msgstr ""
-#: en/fedora-install-guide-acknowledgements.xml:17(para)
-msgid "Many useful comments and suggestions were provided by Rahul Sundaram and the Anaconda team. David Neimi and Debra Deutsch contributed additional information on boot loader and RAID configurations."
+#: en_US/fedora-install-guide-acknowledgements.xml:17(para)
+msgid "Many useful comments and suggestions were provided by Rahul Sundaram and the Anaconda team. David Neimi and Debra Deutsch contributed additional information on boot loader and RAID configurations. The sections on LVM benefited from the contributions of Bob McKay."
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
-#: en/fedora-install-guide-abouttoinstall.xml:41(None)
+#: en_US/fedora-install-guide-abouttoinstall.xml:41(None)
msgid "@@image: './figs/abouttoinstall.eps'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
-#: en/fedora-install-guide-abouttoinstall.xml:44(None)
+#: en_US/fedora-install-guide-abouttoinstall.xml:44(None)
msgid "@@image: './figs/abouttoinstall.png'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:16(title)
+#: en_US/fedora-install-guide-abouttoinstall.xml:16(title)
msgid "About to Install"
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:18(para)
-msgid "No changes are made to your computer until you click the <guilabel>Next</guilabel> button. If you abort the installation process after that point, the &FC; system will be incomplete and unusable. To return to previous screens to make different choices, select <guilabel>Back</guilabel>. To abort the installation, turn off the computer."
+#: en_US/fedora-install-guide-abouttoinstall.xml:18(para)
+msgid "No changes are made to your computer until you click the <guilabel>Next</guilabel> button. If you abort the installation process after that point, the Fedora Core system will be incomplete and unusable. To return to previous screens to make different choices, select <guilabel>Back</guilabel>. To abort the installation, turn off the computer."
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:28(title)
+#: en_US/fedora-install-guide-abouttoinstall.xml:28(title)
msgid "Aborting Installation"
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:29(para)
-msgid "In certain situations, you may be unable to return to previous screens. &FC; notifies you of this restriction and allows you to abort the installation program. You may reboot with the installation media to start over."
+#: en_US/fedora-install-guide-abouttoinstall.xml:29(para)
+msgid "In certain situations, you may be unable to return to previous screens. Fedora Core notifies you of this restriction and allows you to abort the installation program. You may reboot with the installation media to start over."
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:38(title)
+#: en_US/fedora-install-guide-abouttoinstall.xml:38(title)
msgid "About to Install Screen"
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:47(phrase)
+#: en_US/fedora-install-guide-abouttoinstall.xml:47(phrase)
msgid "About to install screen."
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:54(para)
+#: en_US/fedora-install-guide-abouttoinstall.xml:54(para)
msgid "Click <guilabel>Next</guilabel> to begin the installation."
msgstr ""
-#: en/entities.xml:5(title)
-msgid "These entities are local to the Fedora Installation Guide."
-msgstr ""
-
-#: en/entities.xml:8(comment)
-msgid "Document base name"
-msgstr ""
-
-#: en/entities.xml:9(text)
-msgid "fedora-install-guide"
-msgstr ""
-
-#: en/entities.xml:12(comment)
-msgid "Document language"
-msgstr ""
-
-#: en/entities.xml:13(text)
-msgid "en"
-msgstr ""
-
-#: en/entities.xml:16(comment)
-msgid "Document version"
-msgstr ""
-
-#: en/entities.xml:17(text)
-msgid "1.24"
-msgstr ""
-
-#: en/entities.xml:20(comment)
-msgid "Document date"
-msgstr ""
-
-#: en/entities.xml:21(text)
-msgid "2006-03-04"
-msgstr ""
-
-#: en/entities.xml:24(comment)
-msgid "Document ID string"
-msgstr ""
-
-#: en/entities.xml:25(text)
-msgid "<use entity=\"DOCNAME\"/>-<use entity=\"DOCLANG\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE\"/>)"
-msgstr ""
-
-#: en/entities.xml:31(comment)
-msgid "Local version of Fedora Core"
-msgstr ""
-
-#: en/entities.xml:32(text)
-msgid "5"
-msgstr ""
-
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: en/entities.xml:0(None)
+#: en_US/entities.xml:0(None)
msgid "translator-credits"
msgstr ""
18 years
install-guide rpm-info.xml,1.23,1.24
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15283
Modified Files:
rpm-info.xml
Log Message:
- Minor amendment to example servers, for consistency.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- rpm-info.xml 30 Apr 2006 22:15:06 -0000 1.23
+++ rpm-info.xml 7 May 2006 14:37:37 -0000 1.24
@@ -28,10 +28,15 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="Sun May 07 2006" number="1" role="rpm">
+ <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+ <details>Amended example computer names</details>
+ </revision>
<revision date="2006-04-30" number="1.32" role="doc">
<author worker="StuartEllis"/>
<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
- <details>Amended USB media instructions to use dmesg.</details>
+ <details lang="en_US">Amended USB media instructions to use dmesg.</details>
</revision>
<revision date="2006-04-30" number="1.31" role="doc">
<author worker="StuartEllis"/>
18 years
install-guide/en_US fedora-install-guide-adminoptions.xml,1.2,1.3
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15283/en_US
Modified Files:
fedora-install-guide-adminoptions.xml
Log Message:
- Minor amendment to example servers, for consistency.
Index: fedora-install-guide-adminoptions.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/fedora-install-guide-adminoptions.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-install-guide-adminoptions.xml 29 Mar 2006 21:19:18 -0000 1.2
+++ fedora-install-guide-adminoptions.xml 7 May 2006 14:37:38 -0000 1.3
@@ -209,7 +209,7 @@
</entry>
<entry>
<para>
- <option>method=<replaceable>http://server.example.com/directory/</replaceable></option>
+ <option>method=<replaceable>http://server.mydomain.com/directory/</replaceable></option>
</para>
</entry>
</row>
@@ -221,7 +221,7 @@
</entry>
<entry>
<para>
- <option>method=<replaceable>ftp://server.example.com/directory/</replaceable></option>
+ <option>method=<replaceable>ftp://server.mydomain.com/directory/</replaceable></option>
</para>
</entry>
</row>
@@ -233,7 +233,7 @@
</entry>
<entry>
<para>
- <option>method=<replaceable>nfs:server.example.com:/directory/</replaceable></option>
+ <option>method=<replaceable>nfs:server.mydomain.com:/directory/</replaceable></option>
</para>
</entry>
</row>
@@ -717,7 +717,7 @@
the Web application. Your application can use these headers to
identify the computer. This line sends a request with headers to
the application
- <wordasword>http://server.example.com/kickstart.cgi</wordasword>:
+ <wordasword>http://server.mydomain.com/kickstart.cgi</wordasword>:
</para>
<screen>
<userinput>linux ks=http://server.mydomain.com/kickstart.cgi kssendmac</userinput>
18 years
release-notes Makefile,1.37,1.38
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7464
Modified Files:
Makefile
Log Message:
Adding in other languages; make html-[lang] to test, as plain make or make html may fail.
Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- Makefile 10 Apr 2006 17:28:48 -0000 1.37
+++ Makefile 6 May 2006 22:29:43 -0000 1.38
@@ -8,7 +8,7 @@
#
DOCBASE = RELEASE-NOTES
PRI_LANG = en_US
-OTHERS = #zh_CN pt_BR it ru # pa ja_JP
+OTHERS = #de it ja_JP pa pl pt_BR ru zh_CN
########################################################################
# List each XML file of your document in the template below. Append the
18 years
release-notes/pl - New directory
by fedora-docs-commits@redhat.com
Author: mcgiwer
Update of /cvs/docs/release-notes/pl
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6183/pl
Log Message:
Directory /cvs/docs/release-notes/pl added to the repository
18 years
docs-common/common cvs-pt_BR.xml,NONE,1.1
by fedora-docs-commits@redhat.com
Author: eitch
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29386
Added Files:
cvs-pt_BR.xml
Log Message:
Finished pt_BR translation
--- NEW FILE cvs-pt_BR.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY BOILERPLATE "This header makes editing XML easier" >
<!ENTITY FC "Fedora Core" >
<!ENTITY RH "Red Hat" >
]>
-->
<chapter id="ch-cvs">
<title>CVS</title>
<para>
O Concurrent Versions System (<application>CVS</application>)
fornece uma plataforma onde ��ltiplos usu��rios podem editar os mesmos
arquivos. Imagine que se um grupo de usu��rios editam arquivos em um ��nico
diret��rio, o caos pode reinar. Entretanto, usando o
<application>CVS</application>, um grupo de pessoas pode trabalhar de forma
segura no mesmo conjunto de arquivos. O <application>CVS</application>
mant��m uma c��pia mestre dos arquivos, e grava em um reposit��rio central quem
modificou que arquivo e quando. Se conflitos surgem, o
<application>CVS</application> lhe diz. O <application>CVS</application> ��
geralmente usado por programadores que compartilham c��digos, mas tamb��m
funciona bem para documenta����o.
</para>
<indexterm>
<primary>cvs</primary>
</indexterm>
<section id="sn-cvs-overview">
<title>Como o CVS Trabalha</title>
<indexterm>
<primary>cvs</primary>
<secondary>como ele trabalha</secondary>
</indexterm>
<indexterm>
<primary>cvs</primary>
<secondary>vis��o geral</secondary>
</indexterm>
<para>
Em muitos casos, cada conjunto de arquivos que formam um pacote ou projeto
�� armazenado como um <firstterm>m��dulo</firstterm> no servidor CVS.
</para>
<para>
Quando trabalhando com arquivos no <application>CVS</application>, voc��
pode extrair (<firstterm>checkout</firstterm>) uma c��pia do m��dulo para o
seu sistema de arquivos local. Depois de modificar um ou mais arquivos,
voc�� pode envi��-los (<firstterm>commit</firstterm>) de volta para o
reposit��rio central do servidor <application>CVS</application>.
</para>
<para>
Com o <application>CVS</application> voc�� pode editar um arquivo sem
primeiro pegar permiss��o ou bloqueando o arquivo. A parte concorrente
(<wordasword>concurrent</wordasword>) do arquivo no
<application>CVS</application> tem a habilidade de permitir muitas pessoas
diferentes a editar diferentes partes do arquivo. Contanto que nenhuma das
mudan��as gerem conflito entre si, o <application>CVS</application> pode
corretamente gravar as mudan��as. Em caso de mudan��as duplicadas, elas s��o
marcadas nos arquivos e os autores podem resolver o problema entre eles.
</para>
<para>
Quando voc�� aplica as mudan��as, apenas mudan��as em arquivos que o servidor
conhece s��o aplicadas. Em outras palavras, quando voc�� cria um arquivo em
sua c��pia local do m��dulo, o novo arquivo n��o �� automaticamente atualizado
no servidor. Voc�� precisa adicionar (<firstterm>add</firstterm>) o arquivo
ao reposit��rio para depois aplic��-lo enviando (commit). Se voc�� remover o
arquivo da sua c��pia local do m��dulo, voc�� precisa especificar que voc��
deseja remov��-lo do diret��rio no servidor CVS e depois aplicar a remo����o
do arquivo.
</para>
<para>
Os comandos especificos para executar estas a����es s��o descritos em
<xref linkend="sn-cvs-cvscommands"></xref>.
</para>
<para>
Se algu��m modificou o arquivo entre a ��ltima vez que voc�� pegou o arquivo
do CVS e quando voc�� tentou aplicar as mudan��as, o
<application>CVS</application> tentar�� mesclar as mudan��as na c��pia mestre
do servidor <application>CVS</application>. Se o conte��do que voc��
modificou est�� em uma localiza����o diferente no arquivo do que as mudan��as
que outra pessoa modificou, as chances s��o de que a a����o de aplicar ter��
sucesso sem nenhum <firstterm>conflict</firstterm>. Se algu��m modificou o
mesmo conte��do que voc�� e tentar aplicar, voc�� ver�� uma mensagem de que um
conflito no arquivo ocorreu. Por isso, voc�� precisa atualizar
(<firstterm>update</firstterm>) seus arquivos freq��entemente. �� uma boa
pr��tica atualiz��-los logo antes de come��ar a modificar um arquivo. Veja na
<xref linkend="sn-cvs-cvscommands-conflicts"></xref> para instru����es em
como resolver conflitos.
</para>
</section>
<section id="sn-cvs-preparation">
<title>Preparando-se Para Usar o CVS</title>
<indexterm>
<primary>cvs</primary>
<secondary>preparando-se para usar</secondary>
</indexterm>
<para>
Antes de usar o <application>CVS</application>, voc�� precisa estabelecer
uma conta no servidor <application>CVS</application>. Depois de conseguir
uma conta, voc�� n��o precisa fazer estes passos novamente.
</para>
<section id="sn-cvs-rpm-check">
<title>O CVS Est�� Instalado em Seu Sistema?</title>
<indexterm>
<primary>cvs</primary>
<secondary>instala����o por RPM</secondary>
</indexterm>
<para>
Voc�� deve ter o pacote <abbrev>RPM</abbrev> do
<application>CVS</application> instalado. Verifique a sua presen��a
digitando o comando:
</para>
<screen><prompt>$ </prompt><command>rpm -q cvs</command></screen>
<para>
Se voc�� ver uma sa��da parecida com
<computeroutput>cvs-1.11.19-1</computeroutput>, ent��o o pacote est��
instalado. Uma mensagem parecida com <computeroutput>package cvs is not
installed</computeroutput> quer dizer que voc�� precisa instalar o pacote
<application>cvs</application> antes de continuar. Se voc�� n��o sabe como
fazer isso, consulte o seu administrador de sistemas que possa
instal��-lo para voc��.
</para>
</section>
<section id="sn-cvs-generate-keys">
<title>Gerando as Chaves SSH</title>
<indexterm>
<primary>OpenSSH</primary>
<secondary>chaves de autoriza����o</secondary>
</indexterm>
<para>
O servidor <application>CVS</application> usa chaves do Protocolo 2 do
<application>SSH</application> para autenticar usu��rios. Por isso voc��
precisar�� gerar um par de chaves antes de conseguir uma conta no
<application>CVS</application>. Se voc�� j�� tem uma chave
<abbrev>DSA</abbrev> do <application>SSH</application>, pode pular este
passo.
</para>
<tip>
<title>Dica</title>
<para>
Voc�� j�� tem uma chave <abbrev>DSA</abbrev> caso voc�� tenha o arquivo
<filename>~/.ssh/id_dsa.pub</filename> em seu sistema.
</para>
<para>
Se sua chave <abbrev>DSA</abbrev> existente n��o precisa de uma
frase-senha (<wordasword>passphrase</wordasword>), �� altamente
recomendado que voc�� gere outra que precisa de uma frase-senha.
</para>
</tip>
<para>
Use os seguintes passos para gerar uma chave <abbrev>DSA</abbrev> usada
pelo Protocolo 2 do <application>SSH</application>. Ela �� necess��ria
para uma conta <application>CVS</application> no servidor
<computeroutput>cvs.fedora.redhat.com</computeroutput>.
</para>
<orderedlist>
<indexterm>
<primary>OpenSSH</primary>
<secondary><command>ssh-keygen</command>
</secondary>
</indexterm>
<indexterm>
<primary><command>ssh-keygen</command>
</primary>
</indexterm>
<listitem>
<para>
Para gerar uma chave <acronym>DSA</acronym> que trabalhe com a
vers��o 2.0 do protoclo, digite na linha de comando:
</para>
<screen><prompt>$ </prompt><command>ssh-keygen -t dsa</command></screen>
<para>
Aceite a localiza����o de arquivo padr��o no
<filename>~/.ssh/id_dsa</filename>. �� altamente recomendado que voc��
defina e use uma frase-senha (<firstterm>passphrase</firstterm>)
para melhorar a seguran��a da sua chave. Entre com uma frase-senha
diferente da sua senha de conta e confirme digitando-a novamente.
</para>
</listitem>
<listitem>
<para>
Copie a sua nova chave para o arquivo correto digitando o seguinte
na linha de comando.
</para>
<screen><prompt>$ </prompt><command>cat ~/.ssh/id_dsa.pub>>~/.ssh/authorized_keys</command></screen>
<note>
<para>
Verifique este comando com cuidado antes de pressionar a tecla
<guibutton>ENTER</guibutton>. Se o arquivo
<filename>~/.ssh/authorized_keys</filename> j�� existir, o conte��do
do <filename>~/.ssh/id_dsa.pub</filename> ir�� ser adicionado ao
fim do arquivo <filename>~/.ssh/authorized_keys</filename>.
</para>
</note>
</listitem>
<listitem>
<para>
Mude as permiss��es do seu diret��rio <filename>~/.ssh</filename> e de
suas chaves com os comandos:
</para>
<screen><prompt>$ </prompt><command>chmod 755 ~/.ssh</command>
<prompt>$ </prompt><command>chmod 644 ~/.ssh/authorized_keys</command></screen>
</listitem>
</orderedlist>
<tip>
<title>Dica</title>
<para>
Voc�� pode fazer com que o seu sistema lembre-se de sua frase-senha
para que voc�� n��o tenha que digitar toda vez que acessar o servidor
<application>CVS</application>. Veja a documenta����o do programa
<application>ssh-add</application>.
</para>
</tip>
</section>
</section>
<section id="sn-cvs-config">
<title>Configurando Para Um Acesso CVS</title>
<indexterm>
<primary>cvs</primary>
<secondary>configurando para acesso</secondary>
</indexterm>
<indexterm>
<primary>cvs</primary>
<secondary>CVSROOT</secondary>
</indexterm>
<indexterm>
<primary>cvs</primary>
<secondary>CVS_RSH</secondary>
</indexterm>
<indexterm>
<primary>CVSROOT</primary>
</indexterm>
<indexterm>
<primary>CVS_RSH</primary>
</indexterm>
<indexterm>
<primary>cvs</primary>
<secondary><filename>.cvsrc</filename>
</secondary>
</indexterm>
<indexterm>
<primary><filename>.cvsrc</filename>
</primary>
</indexterm>
<section id="sn-cvs-config-cvsrc">
<title>Evitando Digita����es Repetitivas</title>
<indexterm>
<primary>cvs</primary>
<secondary>evitando digita����es repetitivas</secondary>
</indexterm>
<para>
Muitos comandos <application>CVS</application> precisam de certos
par��metros de linha de comando para operar consistentemente. Ao inv��s de
digit��-los toda vez que o comando �� usado, voc�� pode salvar estes
par��metros em um arquivo que o <application>CVS</application> ir�� ler
antes de executar a sua linha de comando.
</para>
<para>
Crie um arquivo chamado <filename>~/.cvsrc</filename> no seu diret��rio
home. Ele deve conter os seguintes comandos, um por linha:
<screen><computeroutput>cvs -z3
diff -uNp
rdiff -uNp
update -dP</computeroutput></screen>
</para>
</section>
<section id="sn-cvs-config-anon">
<title>Configurando para Acesso CVS Somente-Leitura</title>
<indexterm>
<primary>cvs</primary>
<secondary>configurando acesso somente-leitura</secondary>
</indexterm>
<indexterm>
<primary>cvs</primary>
<secondary>acesso an��nimo</secondary>
</indexterm>
<para>
Se o seu objetivo �� efetuar download das v��rias documenta����es do &FC; e
renderizar em seu sistema, voc�� precisar�� apenas de acesso
somente-leitura no reposit��rio <application>CVS</application>. Siga as
instru����es desta se����o e ent��o pule diretamente para a <xref
linkend="sn-cvs-cvscommands-co"/>.
</para>
<para>
Mude o diret��rio para onde voc�� quer que seus arquivos do
<application>CVS</application> estejam localizados, e ent��o execute os
seguintes comandos:
</para>
<screen><prompt>$ </prompt><command>export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs</command>
<prompt>$ </prompt><command>cvs login</command>
<prompt>$ </prompt><command>cvs checkout docs-common</command> <replaceable>module-name</replaceable>
<prompt>$ </prompt><command>cvs checkout</command> <replaceable>module-name</replaceable>
<prompt>$ </prompt><command>cd</command> <replaceable>module-name</replaceable></screen>
<para>
Uma vez que voc�� tenha obtido o m��dulo, n��o importa o que estiver em sua
vari��vel <envar>CVSROOT</envar> porque o dado �� armazenado no arquivo
<filename>CVS/Root</filename> em cada diret��rio do seu reposit��rio
local. Enquanto o seu diret��rio de trabalho atual tiver um diret��rio
<filename>CVS/</filename>, o programa <application>CVS</application> ir��
localizar automaticamente o reposit��rio &FC;.
</para>
</section>
<section id="sn-cvs-config-author">
<title>Configurando Acesso CVS Leitura/Escrita</title>
<indexterm>
<primary>cvs</primary>
<secondary>configurando acesso leitura/escrita</secondary>
</indexterm>
<indexterm>
<primary>cvs</primary>
<secondary>configurando acesso para autores</secondary>
</indexterm>
<para>
Para criar um novo documento ou modificar um j�� existente, voc�� precisa
obter acesso leitura/escrita completo ao reposit��rio CVS de
Documenta����o &FC;. Para detalhes completos sobre este processo, veja no
site <ulink
url="http://fedoraproject.org/wiki/DocsProject/NewWriters"><filename>http://fedoraproject.org/wiki/DocsProject/NewWriters</filename>.
Abaixo est�� um pequeno resumo:
</para>
<itemizedlist>
<listitem>
<para>
Inscreva-se na <ulink
url="https://listman.redhat.com/mailman/listinfo/fedora-docs-list"><filename>fedora-docs-list</filename>
</ulink>, que �� a lista principal do projeto.
</para>
</listitem>
<listitem>
<para>
Gere uma chave GNU Privacy Guard (<abbrev>GPG</abbrev>) para voc�� se
identificar no projeto.
</para>
</listitem>
<listitem>
<para>
Registre uma conta no <ulink
url="http://bugzilla.redhat.com/"><filename>Bugzilla</filename>
</ulink>, se voc�� j�� n��o tem uma. O <filename>Bugzilla</filename> ��
o m��todo que usamos para acompanhar bugs, mudan��as e projetos.
</para>
</listitem>
<listitem>
<para>
Envie uma <ulink
url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">apresenta����o
de si</ulink> na lista.
</para>
</listitem>
</itemizedlist>
<para>
Depois que sua <ulink
url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">apresenta����o
de si</ulink> for aprovada, seu acesso <application>CVS</application>
ser�� garantido.
</para>
<para>
Todo autor, e isso inclui voc�� depois da sua apresenta����o, recebe uma
vari��vel <envar>$CVSROOT</envar> ��nica para acessar o reposit��rio
<application>CVS</application>:
</para>
<screen><prompt>$ </prompt><command>export CVSROOT=:ext:</command><replaceable>seunome</replaceable><command>@cvs.fedora.redhat.com:/cvs/docs</command>
<prompt>$ </prompt><command>export CVS_RSH=/usr/bin/ssh</command></screen>
<para>
Com as vari��veis de ambiente
<envar>$CVSROOT</envar>
e
<envar>$CVS_RSH</envar>
funcionando, voc�� pode acessar o reposit��rio:
</para>
<screen><prompt>$ </prompt><command>cvs co -c</command></screen>
<para>
Voc�� ter�� que digitar sua frase-senha para a sua chave
<application>SSH</application>. Pressione
<guibutton>ENTER</guibutton>
e voc�� dever�� receber uma lista de m��dulos que j�� est��o no reposit��rio.
</para>
</section>
</section>
<section id="sn-cvs-cvscommands">
<title>Comandos B��sicos de CVS</title>
<indexterm>
<primary>cvs</primary>
<secondary>comandos</secondary>
</indexterm>
<para>
Depois de configurar seu sistema para trabalhar com CVS, extraia os
m��dulos que voc�� ir�� trabalhar.
</para>
<tip>
<title>Dica</title>
<para>
Para ver se voc�� precisa de uma vari��vel
<envar>$CVSROOT</envar>
configurada corretamente, ou um par��metro
<option>-m </option>
<replaceable>reposit��rio</replaceable>, veja se voc�� tem um subdiret��rio
chamado <filename>CVS/</filename> no diret��rio atual.
</para>
<para>
Se voc�� tem um diret��rio <filename>CVS/</filename>, o
<application>CVS</application> ignora totalmente a vari��vel
<envar>$CVSROOT</envar> ou o par��metro <option>-m</option>.
</para>
</tip>
<section id="sn-cvs-cvscommands-co">
<title>Extraindo M��dulos</title>
<indexterm>
<primary>cvs</primary>
<secondary>extraindo m��dulos</secondary>
</indexterm>
<para>
Voc�� s�� precisar extrair um m��dulo uma vez. Depois que uma c��pia local
do m��dulo estiver em seu sistema, ela estar�� em seu sistema.
</para>
<para>
Para extrair um m��dulo, use o seguinte comando:
</para>
<screen><prompt>$ </prompt><command>cvs co</command> <replaceable><nome-do-modulo></replaceable></screen>
<para>
Por exemplo, para extrair o m��dulo
<computeroutput>example-tutorial</computeroutput>, mude o seu atual
diret��rio, e execute o seguinte comando:
</para>
<screen><prompt>$ </prompt><command>cvs co example-tutorial</command></screen>
<para>
Um diret��rio chamado <filename>example-tutorial/</filename> �� criado
dentro do diret��rio atual.
</para>
<para>
Se um nome de ��rvore n��o �� especificado ao extrair um m��dulo, ele ��
referenciado com a ��rvore <firstterm>HEAD</firstterm> do m��dulo
<application>CVS</application>.
</para>
<section id="sn-cvs-cvscommands-co-branch">
<title>Extraindo ��rvores de M��dulos</title>
<indexterm>
<primary>cvs</primary>
<secondary>extrair m��dulos</secondary>
<tertiary>extraindo ��rvores</tertiary>
</indexterm>
<para>
Pense na ��rvore <application>CVS</application> como uma vers��o dos
arquivos para uma vers��o particular de um manual ou pacote.
</para>
<para>
Para extrair uma ��rvore de um m��dulo, use o seguinte comando:
</para>
<screen><prompt>$ </prompt><command>cvs co</command> <option>-d</option> <replaceable><diret��rio></replaceable> <option>-r</option> <replaceable><nome-da-��rvore></replaceable> <replaceable><nome-do-m��dulo></replaceable></screen>
<para>
Um diret��rio chamado <replaceable><diret��rio></replaceable> ��
criado, e os arquivos da ��rvore
<replaceable><nome-da-��rvore></replaceable> do m��dulo
<replaceable><nome-do-m��dulo></replaceable> s��o copiados para
este diret��rio.
</para>
<para>
Por exemplo, para extrair uma ��rvore chamada BRANCH-VERSION-1.2
do m��dulo <computeroutput>mymodule</computeroutput>, use o comando:
</para>
<screen><prompt>$ </prompt><command>cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule</command></screen>
<para>
A ��rvore BRANCH-VERSION-1.2 do m��dulo �� extra��da para o diret��rio
<filename>mymodule-1.2</filename> em seu sistema.
</para>
<para>
Para determinar que ��rvores e tags existem para um arquivo, use o
comando:
</para>
<screen><prompt>$ </prompt><command>cvs status</command> <option>-v</option> <replaceable><nomedoarquivo></replaceable></screen>
<para>
Por exemplo, o status do arquivo <filename>foo.sgml</filename> �� o
seguinte:
</para>
<screen>
<computeroutput>
===================================================================
File: foo.sgml Status: Up-to-date
Working revision: 1.47
Repository revision: 1.47 /cvs/docs/custom-guide/rhl-cg-en_US.sgml,v
Sticky Tag: (none)
Sticky Date: (none)
Sticky Options: (none)
Existing Tags:
BRANCH-VERSION-1.2 (branch: 1.25.2)
</computeroutput>
</screen>
<para>
Apenas as tags marcadas como ��rvores na segunda coluna da se����o
<computeroutput>Existing Tags</computeroutput> (Tags Existentes) podem
ser extra��das como uma ��rvore.
</para>
</section>
</section>
<section id="sn-cvs-cvscommands-up">
<title>Atualizando Arquivos</title>
<indexterm>
<primary>cvs</primary>
<secondary>atualizando arquivos</secondary>
</indexterm>
<para>
Para obter as ��ltimas vers��es dos arquivos de um m��dulo, mude para o
diret��rio que cont��m os arquivos para o m��dulo e execute o comando:
</para>
<screen><command>cvs update</command></screen>
<para>
Ser�� efetuado o download das ��ltimas vers��es de todos os arquivos no
m��dulo e colocado em sua c��pia local. Se voc�� notar algum conflito de
arquivo, veja a <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
</para>
</section>
<section id="sn-cvs-cvscommands-commit">
<title>Enviando Arquivos</title>
<indexterm>
<primary>cvs</primary>
<secondary>enviando arquivos</secondary>
</indexterm>
<para>
Depois de modificar os arquivos em sua vers��o local do m��dulo, envie-os
(commit) para salvar as mudan��as no servidor
<application>CVS</application>:
</para>
<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> "<replaceable>mensagem de log</replaceable>" <replaceable>nomedoarquivo</replaceable></screen>
<note>
<para>
Se voc�� prefere escrever as mensagens de log com seu editor de textos
preferidos, como definido nas vari��veis de mabiente $VISUAL ou
$EDITOR, apenas omita o par��metro <userinput>-m "mensagem
de log"</userinput>. O documento j�� ter�� coment��rios descrevendo
a mudan��a; voc�� n��o precisa remov��-los quando for escrever seu
pr��prio texto.
</para>
</note>
<para>
A mensagem de log deve ser o quanto mais descritiva poss��vel para que
voc�� e qualquer outra pessoa trabalhando no m��dulo entenda o que foi
mudado. Usar uma mensagem de log como por exemplo <userinput>atualizado
alguns arquivos</userinput> n��o descreve necessariamente o que foi
mudado e n��o ir�� ajud��-lo no futuro. Se voc�� est�� corrigindo um bug, use
a refer��ncia do <application>Bugzilla</application>.
</para>
<para>
O <replaceable><nomedoarquivo></replaceable> pode ser um arquivo,
uma s��rie de arquivos separados por espa��o, ou um grupo de arquivos
especificados com wildcards (coringas) como por exemplo
<filename>*.png</filename> ou <filename>foo-*.sgml</filename>.
</para>
<para>
Se nehum arquivo ou grupo de arquivos �� especificado no comando
<command>commit</command>, todas as mudan��as de todos os tipos ser��o
enviadas ao servidor. O comando �� recursivo e incluir�� tamb��m mudan��as
em subdiret��rios do m��dulo. Tenha cuidado quando usar o comando
<command>commit</command> sem especificar arquivos porque voc�� pode n��o
lembrar exatamente que arquivos foram modificados.
</para>
<para>
Se voc�� notar algum conflito de arquivo, veja a <xref
linkend="sn-cvs-cvscommands-conflicts"></xref>.
</para>
</section>
<section id="sn-cvs-cvscommands-add">
<title>Adicionando Arquivos</title>
<indexterm>
<primary>cvs</primary>
<secondary>adicionando arquivos</secondary>
</indexterm>
<para>
Para adicionar um arquivo a um m��dulo, crie o arquivo em sua c��pia local
e execute o seguinte comando:
</para>
<screen><prompt>$ </prompt><command>cvs add</command> <replaceable>arquivo-a-adicionar</replaceable></screen>
<para>
Depois de adicionar o arquivo, voc�� precisar�� aplicar
(<command>commit</command>) o comando <command>add</command> para copiar
o arquivo para o servidor:
</para>
<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> "<replaceable>mensagem de log</replaceable>" <replaceable>arquivo-a-adicionar</replaceable></screen>
</section>
<section id="sn-cvs-cvscommands-admin">
<title>Lidando com Arquivos Bin��rios</title>
<indexterm>
<primary>cvs</primary>
<secondary>arquivos bin��rios</secondary>
</indexterm>
<para>
A maioria dos arquivos mais comuns s��o arquivos de texto simples, mas
algumas vezes arquivos bin��rios tamb��m s��o arquivados. O programa
<application>cvs</application> reconhece as extens��es de arquivos mais
comuns como por exemplo <filename>.png</filename> ou
<filename>.jpg</filename>, ent��o o <application>cvs</application>
geralmente "faz a coisa certa".
</para>
<para>
Quando uma c��pia de arquivo �� extra��da do reposit��rio, o
<application>cvs</application>procura palavras-chave especiais nele como
por exemplo "<computeroutput>$id:$</computeroutput>" e
substitui a linha por um valor gerado, como o n��mero de vers��o do
arquivo.
</para>
<para>
Esta substitui����o de palavras-chave geralmente corrompe arquivos
bin��rios, ent��o ela deve ser desligada se o
<application>cvs</application> n��o reconhece seu arquivo como bin��rio.
Para marcar seu arquivo como bin��rio, deixando a substitui����o de
palavras-chave desligada, use o comando:
</para>
<screen width="60"><prompt>$ </prompt><command>cvs</command> <option>admin</option> <option>-kk</option> <replaceable>arquivo</replaceable></screen>
<para>
Note que o arquivo deve estar contido no reposit��rio
<abbrev>CVS</abbrev> antes do comando <option>admin</option> ser usado.
Isto �� certo porque a substitui����o de palavra-chave �� feia quando o
arquivo �� extra��do para o reposit��rio local, e n��o quando o arquivo ��
aplicado ao reposit��rio.
</para>
<tip>
<title>Recuperando um arquivo bin��rio</title>
<para>
Se voc�� colocar um arquivo bin��rio no reposit��rio e perceber que ele
est�� corrompido quando extra��do, n��o entre em p��nico. Simplesmente use
o comando <option>admin</option> como descrito acima, remova sua c��pia
local de arquivo, e extraia-o de novo.
</para>
</tip>
</section>
<section id="sn-cvs-cvscommands-rm">
<title>Removendo Arquivos</title>
<indexterm>
<primary>cvs</primary>
<secondary>removendo arquivos</secondary>
</indexterm>
<para>
Se um arquivo n��o �� mais preciso em um m��dulo, use o comando
<command>remove</command> para remov��-lo de sua c��pia local e ent��o
aplique <command>commit</command> a remo����o no servidor. Meso que o
arquivo seja removido da vers��o atual do m��dulo, uma c��pia arquivada
ainda �� guardada no servidor para que possa ser recolocada a qualquer
momento com o comando <command>add</command>.
</para>
<screen><prompt>$ </prompt><command>cvs rm -f</command> <replaceable>arquivo-a-remover</replaceable></screen>
<para>
Depois de remover o arquivo, voc�� precisa aplicar
(<command>commit</command>) a remo����o:
</para>
<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option>"<replaceable>mensagem de log</replaceable>" <replaceable>arquivo-a-remover</replaceable></screen>
<para>
Voc�� pode usar wildcards (coringas) no comando <command>commit</command>
para identificar os arquivos removidos. Eles devem ser especificados
com um nome de arquivo exato.
</para>
<para>
Se voc�� precisa renomear um arquivo, �� melhor voc�� renomear o arquivo no
servidor <application>CVS</application> para que o hist��rico de vers��es
do arquivo seja preservado. Quando precisar renomear um arquivo, envie
um e-mail para
<ulink url="mailto:cvsdocs-administrator@fedora.redhat.com"><filename>cvsdocs-administrator(a)fedora.redhat.com</filename>
</ulink> pedindo para o arquivo ser renomeado.
</para>
</section>
<section id="sn-cvs-cvscommands-status">
<title>Estado dos Arquivos</title>
<indexterm>
<primary>cvs</primary>
<secondary>estado dos arquivos</secondary>
</indexterm>
<para>
As vezes �� necess��rio visualizar o <firstterm>estado</firstterm> de um
arquivo em um m��dulo <application>CVS</application>. Para ver o estado
de um arquivo, use o comando:
</para>
<screen><prompt>$ </prompt><command>cvs status</command> <replaceable>arquivo</replaceable></screen>
<para>
O estado de um arquivo de reposit��rio pode ser:
</para>
<variablelist>
<varlistentry>
<term><computeroutput>Up-to-date</computeroutput> (Atualizado)</term>
<listitem>
<para>
Sua revis��o do arquivo �� id��ntica a ��ltima vers��o do servidor
<application>CVS</application>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><computeroutput>Locally Modified</computeroutput> (Localmente Modificada)</term>
<listitem>
<para>
Voc�� atualizou a ��ltima revis��o do servidor, mas voc�� modificou o
arquivo em seu sistema.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><computeroutput>Locally Added</computeroutput> (Adicionado Localmente)</term>
<listitem>
<para>
Voc�� adicionou o arquivo com o comando <command>cvs add</command>
mas n��o aplicou (commit) a adi����o do arquivo.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><computeroutput>Locally Removed</computeroutput> (Removido Localmente)</term>
<listitem>
<para>
Voc�� removeu o arquivo com o comando <command>cvs remove</command>
mas ainda n��o aplicou (commit) a remo����o.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><computeroutput>Needs Checkout</computeroutput> (Precisa de Extra����o)</term>
<listitem>
<para>
Uma novavers��o do arquivo est�� no servidor e precisa ser obtida.
Apesar do estado incluir a palavra extrair, ele na verdade
significa que voc�� precisa atualizar seus arquivos com o comando
<command>cvs update</command>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><computeroutput>Needs Patch</computeroutput> (Precisa de Patch)</term>
<listitem>
<para>
A revis��o do seu reposit��rio local precisa de um patch para a
��ltima revis��o do servidor. Use o comando <command>cvs
update</command> para resolver.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><computeroutput>Needs Merge</computeroutput> (Precisa de Mesclagem)</term>
<listitem>
<para>
Uma nova revis��o existe no servidor e sua vers��o local cont��m
modifica����es que ainda n��o foram aplicadas. Este estado geralmente
aparece quando voc�� n��o tem a ��ltima revis��o do arquivo e mesmo
assim o edita.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><computeroutput>File had conflicts on merge</computeroutput> (H�� conflitos no Arquivo durante a Mesclagem)</term>
<listitem>
<para>
Parecido com o <computeroutput>Needs Merge</computeroutput>,
exceto pelo fato de que voc�� tentou usar o comando <command>cvs
update</command>. A diferen��a n��o p��de ter sido resolvida
automaticamente. Veja a <xref
linkend="sn-cvs-cvscommands-conflicts"></xref> para mais
informa����es em como resolver conflitos.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><computeroutput>Unknown</computeroutput> (Desconhecido)</term>
<listitem>
<para>
O servidor <application>CVS</application> n��o sabe de nada sobre
este arquivo. Ele pode n��o ter sido adicionado ou removido
localmente e nunca p��de ter sido aplicado ao servidor. Este estado
geralmente ocorre para arquivos que voc�� n��o deve aplicar (commit)
ao <application>CVS</application> como por exemplo um
<filename>generated-index.sgml</filenamee> ou arquivos que voc��
pode querer adicionar ao reposit��rio mas n��o usou o comando
<command>cvs add</command>.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
<section id="sn-cvs-cvscommands-conflicts">
<title>Resolvendo Conflitos</title>
<indexterm>
<primary>cvs</primary>
<secondary>resolvendo conflitos</secondary>
</indexterm>
<para>
Se voc�� modifica um arquivo em uma mesma regi��o que foi modificada e
aplicada por outra pessoa primeiro, voc�� provavelmente ir�� ver uma
mensagem parecido com a abaixo quando aplicar o arquivo ou atualizar a
sua c��pia local do m��dulo:
</para>
<screen>
<computeroutput>
RCS file: /cvs/docs/module-name/filename.sgml,v
retrieving revision 1.12
retrieving revision 1.13
Merging differences between 1.12 and 1.13 into filename.sgml
rcsmerge: warning: conflicts during merge
cvs server: conflicts found in filename.sgml
C filename.sgml
</computeroutput>
</screen>
<para>
Para resolver o conflito, abra o arquivo, procure por
<computeroutput><<<<<<<</computeroutput>
e determine que vers��o do conte��do �� correta. Por exemplo:
</para>
<screen>
<computeroutput>
<para>
Uma senten��a.
<<<<<<< filename.sgml
A senten��a que foi mudada na c��pia em trabalho.
=======
A mesma senten��a que foi mudada diferentemente e aplicada.
>>>>>>> 1.13
</para>
</computeroutput>
</screen>
<para>
O conte��do entre
<computeroutput><<<<<<<</computeroutput>,
e <computeroutput>=======</computeroutput> �� o conte��do da sua c��pia
local. O conte��do entre o <computeroutput>=======</computeroutput> e
<computeroutput>>>>>>>></computeroutput> �� o
conte��do do servidor.
</para>
<para>
Resolva o conflito editando a sua c��pia, e aplicando (commit) o arquivo.
</para>
</section>
<section id="sn-cvs-cvscommands-summary">
<title>Sum��rio</title>
<indexterm>
<primary>cvs</primary>
<secondary>comandos</secondary>
<tertiary>sum��rio dos</tertiary>
</indexterm>
<para>
Todos os comandos assumem que voc�� esteja no diret��rio apropriado do
m��dulo <application>CVS</application>.
</para>
<table frame="all" id="tb-cvs-basic-commands">
<title>Comandos B��sicos de CVS</title>
<tgroup cols="2">
<colspec colnum="1" colname="shortcut" colwidth="30"/>
<colspec colnum="2" colname="description" colwidth="60"/>
<thead>
<row>
<entry>Comando</entry>
<entry>Descri����o</entry>
</row>
</thead>
<tbody>
<row>
<entry><command>cvs checkout
<replaceable><nome-do-m��dulo></replaceable></command>
ou <command>cvs co <replaceable><nome-do-m��dulo></replaceable></command>
</entry>
<entry>Cria um diret��rio chamado
<replaceable><nome-do-m��dulo></replaceable> com o conte��do do m��dulo no
diret��rio</entry>
</row>
<row>
<entry><command>cvs co -d
<replaceable><diret��rio></replaceable> -r <replaceable><nome-da-��rvore></replaceable><replaceable><nome-do-m��dulo></replaceable></command>
</entry>
<entry>Cria o diret��rio <replaceable><diret��rio></replaceable>
com o conte��do da ��rvore <replaceable><nome-da-��rvore></replaceable>
do m��dulo <replaceable><nome-do-m��dulo></replaceable> m��dulo.</entry>
</row>
<row>
<entry><command>cvs update</command> ou <command>cvs up</command>
</entry>
<entry>Atualiza seus arquivos com os ��ltimos arquivos do servidor
CVS.</entry>
</row>
<row>
<entry><command>cvs add <replaceable><arquivo></replaceable></command>
</entry>
<entry>Adiciona o novo arquivo "arquivo" ao servidor CVS</entry>
</row>
<row>
<entry><command>cvs commit -m "Minha mensagem"
<replaceable><arquivo></replaceable></command>
</entry>
<entry>Atualiza o arquivo
<replaceable><arquivo></replaceable> com a ��ltima c��pia de
seu computador</entry>
</row>
<row>
<entry><command>cvs log <replaceable><arquivo></replaceable></command>
</entry>
<entry>Visualiza as mensagens de commit do arquivo <replaceable><arquivo></replaceable>
</entry>
</row>
<row>
<entry><command>cvs status <replaceable><arquivo></replaceable></command>
</entry>
<entry>Visualiza o estado do arquivo, como por exemplo
<computeroutput>Localmente Modificado</computeroutput>
</entry>
</row>
<row>
<entry><command>cvs status -v <replaceable><arquivo></replaceable></command>
</entry>
<entry>Visualiza as tags e ��rvores existentes para o arquivo</entry>
</row>
<row>
<entry><command>cvs diff <replaceable><arquivo></replaceable></command>
</entry>
<entry>Mostra a diferen��a entre sua c��pia local do arquivo e a
��ltima vers��o do arquivo na ��rvore</entry>
</row>
<row>
<entry><command>cvs diff -r1.1 -r1.2 <replaceable><arquivo></replaceable></command>
</entry>
<entry>Mostra a diferen��a do arquivo da vers��o 1.1 para a 1.2</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
Para mais informa����es, leia o manual CVS dispon��vel em seu sistema em
<filename>/usr/share/doc/cvs-<replaceable><n��mero-de-vers��o></replaceable>/cvs.ps</filename>
(a vers��o do CVS pode variar) e visite a p��gina do CVS dispon��vel em
<ulink url="http://www.cvshome.org/">http://www.cvshome.org/</ulink>.
</para>
<tip>
<title>Dica</title>
<para>
Como o <application>CVS</application> est�� usando o
<application>ssh</application> para conectar-se ao servidor
<application>CVS</application>, voc�� ser�� perguntando por uma senha
antes de executar a instru����o <application>CVS</application>. Se voc��
quiser configurar o seu sistema para que voc�� n��o tenha que digitar a
senha, veja a p��gina
<ulink url="http://redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-openssh..."><citetitle>&RH;
Linux 9 Customization Guide</citetitle> </ulink> para detalhes em como
usar o <command>ssh-agent</command>.
</para>
</tip>
</section>
</section>
</chapter>
18 years
release-notes/po pa.po,1.4,1.5
by fedora-docs-commits@redhat.com
Author: apbrar
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20040
Modified Files:
pa.po
Log Message:
update translation for Punjabi (Gurmukhi) by apbrar gmail com
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.4 -r 1.5 pa.po
Index: pa.po
===================================================================
RCS file: /cvs/docs/release-notes/po/pa.po,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- pa.po 14 Mar 2006 20:42:32 -0000 1.4
+++ pa.po 1 May 2006 07:57:25 -0000 1.5
@@ -1,291 +1,324 @@
-# translation of fedora-pa2.po to Punjabi
+# translation of pa2.po to Punjabi
# Amanpreet Singh Alam <apbrar(a)gmail.com>, 2006.
# Jaswinder Singh Phulewala <jsingh(a)redhat.com>, 2006.
# A S Alam <apbrar(a)gmail.com>, 2006.
msgid ""
msgstr ""
-"Project-Id-Version: fedora-pa2\n"
-"POT-Creation-Date: 2006-03-14 08:19+0530\n"
-"PO-Revision-Date: 2006-03-15 01:38+0530\n"
+"Project-Id-Version: pa2\n"
+"POT-Creation-Date: 2006-05-01 12:30+0530\n"
+"PO-Revision-Date: 2006-05-01 13:27+0530\n"
"Last-Translator: A S Alam <apbrar(a)gmail.com>\n"
"Language-Team: Punjabi <fedora-trans-pa(a)redhat.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.11.1\n"
+"X-Generator: KBabel 1.11.2\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
"\n"
"\n"
-#: en/Xorg.xml:5(title) en/Welcome.xml:5(title) en/WebServers.xml:5(title)
-#: en/Virtualization.xml:5(title) en/SystemDaemons.xml:5(title)
-#: en/ServerTools.xml:5(title) en/SecuritySELinux.xml:5(title)
-#: en/Security.xml:5(title) en/Samba.xml:5(title)
-#: en/ProjectOverview.xml:5(title) en/Printing.xml:5(title)
-#: en/PackageNotes.xml:5(title) en/PackageChanges.xml:5(title)
-#: en/OverView.xml:5(title) en/Networking.xml:5(title)
-#: en/Multimedia.xml:5(title) en/Legacy.xml:5(title) en/Kernel.xml:5(title)
-#: en/Java.xml:5(title) en/Installer.xml:5(title) en/I18n.xml:5(title)
-#: en/FileSystems.xml:5(title) en/FileServers.xml:5(title)
-#: en/Feedback.xml:5(title) en/Entertainment.xml:5(title)
-#: en/Extras.xml:5(title) en/DevelToolsGCC.xml:5(title)
-#: en/DevelTools.xml:5(title) en/Desktop.xml:5(title)
-#: en/DatabaseServers.xml:5(title) en/Colophon.xml:5(title)
-#: en/BackwardsCompatibility.xml:5(title) en/ArchSpecificx86.xml:5(title)
-#: en/ArchSpecificx86_64.xml:5(title) en/ArchSpecificPPC.xml:5(title)
-#: en/ArchSpecific.xml:5(title)
+#: en_US/Xorg.xml:7(title) en_US/Welcome.xml:7(title)
+#: en_US/WebServers.xml:7(title) en_US/Virtualization.xml:7(title)
+#: en_US/SystemDaemons.xml:7(title) en_US/ServerTools.xml:7(title)
+#: en_US/SecuritySELinux.xml:7(title) en_US/Security.xml:7(title)
+#: en_US/Samba.xml:7(title) en_US/ProjectOverview.xml:7(title)
+#: en_US/Printing.xml:7(title) en_US/PackageNotes.xml:7(title)
+#: en_US/PackageChanges.xml:7(title) en_US/OverView.xml:7(title)
+#: en_US/Networking.xml:7(title) en_US/Multimedia.xml:7(title)
+#: en_US/Legacy.xml:7(title) en_US/Kernel.xml:7(title) en_US/Java.xml:7(title)
+#: en_US/Installer.xml:7(title) en_US/I18n.xml:7(title)
+#: en_US/FileSystems.xml:7(title) en_US/FileServers.xml:7(title)
+#: en_US/Feedback.xml:7(title) en_US/Entertainment.xml:7(title)
+#: en_US/Extras.xml:7(title) en_US/DevelToolsGCC.xml:7(title)
+#: en_US/DevelTools.xml:7(title) en_US/Desktop.xml:7(title)
+#: en_US/DatabaseServers.xml:7(title) en_US/Colophon.xml:7(title)
+#: en_US/BackwardsCompatibility.xml:7(title)
+#: en_US/ArchSpecificx86.xml:7(title) en_US/ArchSpecificx86_64.xml:7(title)
+#: en_US/ArchSpecificPPC.xml:7(title) en_US/ArchSpecific.xml:7(title)
msgid "Temp"
msgstr "���������������"
-#: en/Xorg.xml:8(title)
+#: en_US/Xorg.xml:11(title)
msgid "X Window System (Graphics)"
msgstr "X ��������������� ��������������� (���������������������)"
-#: en/Xorg.xml:9(para)
+#: en_US/Xorg.xml:13(para)
msgid ""
"This section contains information related to the X Window System "
"implementation provided with Fedora."
-msgstr "������ ��������� ������������ X ��������������� ��������������� ������������ ��������������������� ������, ������ ������ ������������������ ������������ ������������������ ������������������ ������ ������������ ���������"
+msgstr ""
+"������ ��������� ������������ X ��������������� ��������������� ������������ ��������������������� ������, ������ ������ ������������������ ������������ ������������������ ������������������ ������ "
+"������������ ���������"
-#: en/Xorg.xml:11(title)
+#: en_US/Xorg.xml:19(title)
msgid "xorg-x11"
msgstr "xorg-x11"
-#: en/Xorg.xml:12(para)
+#: en_US/Xorg.xml:21(para)
msgid ""
-"X.org X11 is an open source implementation of the X Window System. It "
-"provides the basic low-level functionality upon which full-fledged graphical "
-"user interfaces (GUIs) such as GNOME and KDE are designed. For more "
-"information about X.org, refer to <ulink url=\"http://xorg.freedesktop.org/"
-"wiki/\">http://xorg.freedesktop.org/wiki/</ulink>."
-msgstr "X.org X11 X ��������������� ��������������� ������ ��������� ��������� ������������ ������������������ ��������� ������ ������������������ ��������������� ������������ ������ ������������������������������ ������������������ ������������ ������, ��������� ��������� ������������ ��������������� ������������������ ��������������������� (GUI) ������ ��������������� ������������ ��������� KDE ������������ ������ ��������� X.org ������ ��������������� ��������������������� ������ <ulink url=\"http://xorg.freedesktop.org/wiki/\">http://xorg.freedesktop.org/wiki/</ulink> ���������������"
-
-#: en/Xorg.xml:13(para)
-msgid ""
-"You may use <emphasis>Applications > System Settings > Display</"
-"emphasis> or <emphasis role=\"strong\">system-config-display</emphasis> to "
-"configure the settings. The configuration file for X.org is located in "
-"<code>/etc/X11/xorg.conf</code>."
-msgstr "��������������� ��������������� ������������������ ��������� ������ <emphasis>������������ > ��������������� ��������������� > ���������������</emphasis> ��������� <emphasisrole=\"strong\">system-config-display</emphasis> ��������� ��������� ������������ ��������� Xorg ������ ������������������ ������������ <code>/etc/X11/xorg.conf</code> ������������ ���������"
-
-#: en/Xorg.xml:14(para)
-msgid ""
-"X.org X11R7 is the first modular release of X.org, which, among several "
-"other benefits, promotes faster updates and helps programmers rapidly "
-"develop and release specific components. More information on the current "
-"status of the X.org modularization effort in Fedora is available at <ulink "
-"url=\"http://fedoraproject.org/wiki/Xorg/Modularization\">http://"
-"fedoraproject.org/wiki/Xorg/Modularization</ulink>."
-msgstr "X.org X11R7, X.org ������ ������������������ ������������������ ��������������� ������, ������ ��������� ��������������������� ������ ���������-���������, ������������ ������������������ ������������ ������ ��������� ������������������������������ ������ ��������������� ��������������� ��������������������� ������ ������������������������������ ������ ��������� ������������ ��������� ������������������ ������������ X.org ������������������������������������ ������������������ ������ ������������������ ��������������� ������ ��������������� ��������������������� <ulink url=\"http://fedoraproject.org/wiki/Xorg/Modularization\">http://fedoraproject.org/wiki/Xorg/Modularization</ulink> ������������ ������������������ ���������"
+"X.org X11 is an open source implementation of the X Window System. "
+"It provides the basic low-level functionality upon which full-"
+"fledged graphical user interfaces (GUIs) such as GNOME and KDE are "
+"designed. For more information about X.org, refer to <ulink url="
+"\"http://xorg.freedesktop.org/wiki/\">http://xorg.freedesktop.org/"
+"wiki/</ulink>."
+msgstr ""
+"X.org X11 X ��������������� ��������������� ������ ��������� ��������� ������������ ������������������ ��������� ������ ������������������ ��������������� ������������ ������ "
+"������������������������������ ������������������ ������������ ������, ��������� ��������� ������������ ��������������� ������������������ ��������������������� (GUI) ������ ��������������� ������������ "
+"��������� KDE ������������ ������ ��������� X.org ������ ��������������� ��������������������� ������ <ulink url=\"http://xorg."
+"freedesktop.org/wiki/\">http://xorg.freedesktop.org/wiki/</ulink> ���������������"
+
+#: en_US/Xorg.xml:29(para)
+msgid ""
+"You may use <emphasis>System > Administration > Display</"
+"emphasis> or <emphasis role=\"strong\">system-config-display</"
+"emphasis> to configure the settings. The configuration file for X."
+"org is located in <code>/etc/X11/xorg.conf</code>."
+msgstr ""
+"��������������� ��������������� ������������������ ��������� ������ <emphasis>������������ > ��������������� ��������������� > ���������������</"
+"emphasis> ��������� <emphasisrole=\"strong\">system-config-display</"
+"emphasis> ��������� ��������� ������������ ��������� Xorg ������ ������������������ ������������ <code>/etc/X11/xorg.conf</"
+"code> ������������ ���������"
+
+#: en_US/Xorg.xml:36(para)
+msgid ""
+"X.org X11R7 is the first modular release of X.org, which, among "
+"several other benefits, promotes faster updates and helps "
+"programmers rapidly develop and release specific components. More "
+"information on the current status of the X.org modularization effort "
+"in Fedora is available at <ulink url=\"http://fedoraproject.org/wiki/"
+"Xorg/Modularization\">http://fedoraproject.org/wiki/Xorg/"
+"Modularization</ulink>."
+msgstr ""
+"X.org X11R7, X.org ������ ������������������ ������������������ ��������������� ������, ������ ��������� ��������������������� ������ ���������-���������, "
+"������������ ������������������ ������������ ������ ��������� ������������������������������ ������ ��������������� ��������������� ��������������������� ������ ������������������������������ ������ ��������� "
+"������������ ��������� ������������������ ������������ X.org ������������������������������������ ������������������ ������ ������������������ ��������������� ������ ��������������� "
+"��������������������� <ulink url=\"http://fedoraproject.org/wiki/Xorg/"
+"Modularization\">http://fedoraproject.org/wiki/Xorg/Modularization</"
+"ulink> ������������ ������������������ ���������"
-#: en/Xorg.xml:17(title)
+#: en_US/Xorg.xml:47(title)
msgid "X.org X11R7 End-User Notes"
msgstr "X.org X11R7 ������������-������������������ ���������������"
-#: en/Xorg.xml:19(title)
+#: en_US/Xorg.xml:50(title)
msgid "Installing Third Party Drivers"
msgstr "������������������ ������������������ ������������������ ������ ��������� ������"
-#: en/Xorg.xml:20(para)
+#: en_US/Xorg.xml:51(para)
msgid ""
-"Before you install any third party drivers from any vendor, including ATI or "
-"nVidia, please read <ulink url=\"http://fedoraproject.org/wiki/"
+"Before you install any third party drivers from any vendor, "
+"including ATI or nVidia, please read <ulink url=\"http://"
+"fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers\">http://"
+"fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers</ulink>."
+msgstr ""
+"������������ ������ ��������������������� ��������� ������������������ ��������������� ������������������, ��������������������� ������������ ATI ��������� nVidia ������, ������������������ "
+"��������� ��������� ������������������, ��������������� ������������ <ulink url=\"http://fedoraproject.org/wiki/"
"Xorg/3rdPartyVideoDrivers\">http://fedoraproject.org/wiki/"
-"Xorg/3rdPartyVideoDrivers</ulink>."
-msgstr "������������ ������ ��������������������� ��������� ������������������ ��������������� ������������������, ��������������������� ������������ ATI ��������� nVidia ������, ������������������ ��������� ��������� ������������������, ��������������� ������������ <ulink url=\"http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers\">http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers</ulink> ������������������"
+"Xorg/3rdPartyVideoDrivers</ulink> ������������������"
-#: en/Xorg.xml:25(para)
+#: en_US/Xorg.xml:58(para)
msgid ""
-"The <code>xorg-x11-server-Xorg</code> package install scripts automatically "
-"remove the <code>RgbPath</code> line from the <code>xorg.conf</code> file if "
-"it is present. You may need to reconfigure your keyboard differently from "
-"what you are used to. You are encouraged to subscribe to the upstream <ulink "
-"url=\"mailto:xorg@freedesktop.org\">xorg(a)freedesktop.org</ulink> mailing "
-"list if you do need assistance reconfiguring your keyboard."
+"The <code>xorg-x11-server-Xorg</code> package install scripts "
+"automatically remove the <code>RgbPath</code> line from the "
+"<code>xorg.conf</code> file if it is present. You may need to "
+"reconfigure your keyboard differently from what you are used to. You "
+"are encouraged to subscribe to the upstream <ulink url=\"mailto:"
[...9817 lines suppressed...]
msgid ""
-"Fedora Core Installation Disc 1 is bootable on supported hardware. In "
-"addition, a bootable CD image appears in the <code>images/</code> directory "
-"of this disc. These images will behave differently according to your system "
-"hardware:"
+"Fedora Core Installation Disc 1 is bootable on supported hardware. "
+"In addition, a bootable CD image appears in the <code>images/</code> "
+"directory of this disc. These images will behave differently "
+"according to your system hardware:"
msgstr ""
-"������������������ ��������� ������������������������������ ������������ 1 ��������������������� ������������ ������������ ��������� ��������� ��������� ��������� ������ ��������� ���������������, ��������� "
-"��������� ��������� ��������� CD ��������������������������� ������ ������������ ������ <code>images/</code> ��������������������������� ������������ ������ ��������� "
+"������������������ ��������� ������������������������������ ������������ 1 ��������������������� ������������ ������������ ��������� ��������� ��������� ��������� ������ ��������� ���������������, ��������� ��������� "
+"��������� ��������� CD ��������������������������� ������ ������������ ������ <code>images/</code> ��������������������������� ������������ ������ ��������� "
"������ ��������������������������� ������������������ ��������������� ������������ ������������������ ��������������� ��������������� ������������ ������������ ������:"
-#: en/ArchSpecificPPC.xml:48(para)
+#: en_US/ArchSpecificPPC.xml:115(para)
msgid "Apple Macintosh"
msgstr "��������� ��������������������������� (Apple Macintosh)"
-#: en/ArchSpecificPPC.xml:49(para)
+#: en_US/ArchSpecificPPC.xml:118(para)
msgid ""
-"The bootloader should automatically boot the appropriate 32-bit or 64-bit "
-"installer."
+"The bootloader should automatically boot the appropriate 32-bit or "
+"64-bit installer."
msgstr "��������� ������������ ��������� ���������-������������ ������ ��������������������� 32-������������ ��������� 64-������������ ��������������������� ��������� ������������ ������������������ ���������"
-#: en/ArchSpecificPPC.xml:50(para)
+#: en_US/ArchSpecificPPC.xml:122(para)
msgid ""
"The default <code>gnome-power-manager</code> package includes power "
-"management support, including sleep and backlight level management. Users "
-"with more complex requirements can use the <code>apmud</code> package in "
-"Fedora Extras. Following installation, you can install <code>apmud</code> "
-"with the following command:"
-msgstr ""
-"��������� <code>gnome-power-manager</code> ��������������� ������������ ������������ ��������������� ������������������, ������������������ ������, "
-"��������� ������������ ������������������ ��������� ��������������������� ��������������� ��������������� ������ ������������������ ��������� ��������� ������ ������������������������ ��������������� ������������ ������������������ "
-"������������������ ������������������ ������������������ <code>apmud</code> ��������������� ������ ��������������� ������ ������������ ��������� ������������������������������ ������ ������������ "
-"��������������� ������������ ��������������� ��������������� ��������� <code>apmud</code> ������������������ ������ ������������ ������:"
+"management support, including sleep and backlight level management. "
+"Users with more complex requirements can use the <code>apmud</code> "
+"package in Fedora Extras. Following installation, you can install "
+"<code>apmud</code> with the following command:"
+msgstr ""
+"��������� <code>gnome-power-manager</code> ��������������� ������������ ������������ ��������������� ������������������, ������������������ "
+"������, ��������� ������������ ������������������ ��������� ��������������������� ��������������� ��������������� ������ ������������������ ��������� ��������� ������ ������������������������ ��������������� ������������ "
+"������������������ ������������������ ������������������ ������������������ <code>apmud</code> ��������������� ������ ��������������� ������ ������������ ��������� "
+"������������������������������ ������ ������������ ��������������� ������������ ��������������� ��������������� ��������� <code>apmud</code> ������������������ ������ ������������ "
+"������:"
-#: en/ArchSpecificPPC.xml:51(screen)
+#: en_US/ArchSpecificPPC.xml:136(screen)
#, no-wrap
-msgid "su -c 'yum install apmud' "
-msgstr "su -c 'yum install apmud' "
+msgid "su -c 'yum install apmud'"
+msgstr "su -c 'yum install apmud'"
-#: en/ArchSpecificPPC.xml:54(para)
+#: en_US/ArchSpecificPPC.xml:141(para)
msgid "64-bit IBM eServer pSeries (POWER4/POWER5)"
msgstr "64-������������ IBM eServer pSeries (POWER4/POWER5)"
-#: en/ArchSpecificPPC.xml:55(para)
+#: en_US/ArchSpecificPPC.xml:144(para)
msgid ""
-"After using Open<emphasis role=\"strong\"/>Firmware to boot the CD, the "
-"bootloader (yaboot) should automatically boot the 64-bit installer."
+"After using Open<emphasis role=\"strong\"/>Firmware to boot the CD, "
+"the bootloader (yaboot) should automatically boot the 64-bit "
+"installer."
msgstr ""
-"������������ ������ ��������������� ������������<emphasis role=\"strong\"/>CD ��������� ��������� ��������� ������ ������������������������, ��������� ������������ "
-"(yaboot) ���������-������������ ������ 64-������������ ��������������������� ������������������������"
+"������������ ������ ��������������� ������������<emphasis role=\"strong\"/>CD ��������� ��������� ��������� ������ ������������������������, ��������� "
+"������������ (yaboot) ���������-������������ ������ 64-������������ ��������������������� ������������������������"
-#: en/ArchSpecificPPC.xml:58(para)
+#: en_US/ArchSpecificPPC.xml:151(para)
msgid "32-bit CHRP (IBM RS/6000 and others)"
msgstr "32-bit CHRP (IBM RS/6000 ��������� ���������)"
-#: en/ArchSpecificPPC.xml:59(para)
+#: en_US/ArchSpecificPPC.xml:154(para)
msgid ""
-"After using Open<emphasis role=\"strong\"/>Firmware to boot the CD, select "
-"the <code>linux32</code> boot image at the <code>boot:</code> prompt to "
-"start the 32-bit installer. Otherwise, the 64-bit installer starts, which "
-"does not work."
-msgstr ""
-"<emphasis role=\"strong\"/> ������������ ��������� ��������� ��������� ������������ ��������������������� ������, <code>boot:</code> ������������ "
-"<code>linux32</code> 32-������������ ��������������������� ��������������� ��������� ������ ��������������� ������������ ��������� 64-������������ ��������������������� ������������������, ������ ������ ��������� "
-"������������ ������������ ���������"
+"After using Open<emphasis role=\"strong\"/>Firmware to boot the CD, "
+"select the <code>linux32</code> boot image at the <code>boot:</code> "
+"prompt to start the 32-bit installer. Otherwise, the 64-bit "
+"installer starts, which does not work."
+msgstr ""
+"<emphasis role=\"strong\"/> ������������ ��������� ��������� ��������� ������������ ��������������������� ������, <code>boot:"
+"</code> ������������ <code>linux32</code> 32-������������ ��������������������� ��������������� ��������� ������ ��������������� ������������ ��������� "
+"64-������������ ��������������������� ������������������, ������ ������ ��������� ������������ ������������ ���������"
-#: en/ArchSpecificPPC.xml:62(para)
+#: en_US/ArchSpecificPPC.xml:165(para)
msgid "Genesi Pegasos II"
msgstr "Genesi Pegasos II"
-#: en/ArchSpecificPPC.xml:63(para)
+#: en_US/ArchSpecificPPC.xml:168(para)
msgid ""
-"At the time of writing, firmware with full support for ISO9660 file systems "
-"is not yet released for the Pegasos. However, you can use the network boot "
-"image. At the Open<emphasis role=\"strong\"/>Firmware prompt, enter the "
-"command:"
+"At the time of writing, firmware with full support for ISO9660 file "
+"systems is not yet released for the Pegasos. However, you can use "
+"the network boot image. At the Open<emphasis role=\"strong\"/"
+">Firmware prompt, enter the command:"
msgstr ""
-#: en/ArchSpecificPPC.xml:64(screen)
+#: en_US/ArchSpecificPPC.xml:177(screen)
#, no-wrap
-msgid "boot cd: /images/netboot/ppc32.img "
-msgstr "boot cd: /images/netboot/ppc32.img "
+msgid "boot cd: /images/netboot/ppc32.img"
+msgstr "boot cd: /images/netboot/ppc32.img"
-#: en/ArchSpecificPPC.xml:65(para)
+#: en_US/ArchSpecificPPC.xml:180(para)
msgid ""
-"You must also configure Open<emphasis role=\"strong\"/>Firmware on the "
-"Pegasos manually to make the installed Fedora Core system bootable. To do "
-"this, set the <code>boot-device</code> and <code>boot-file</code> "
-"environment variables appropriately."
+"You must also configure Open<emphasis role=\"strong\"/>Firmware on "
+"the Pegasos manually to make the installed Fedora Core system "
+"bootable. To do this, set the <code>boot-device</code> and "
+"<code>boot-file</code> environment variables appropriately."
msgstr ""
-#: en/ArchSpecificPPC.xml:68(para)
+#: en_US/ArchSpecificPPC.xml:192(para)
msgid "Network booting"
msgstr "��������������������� ��������� ������������"
-#: en/ArchSpecificPPC.xml:69(para)
+#: en_US/ArchSpecificPPC.xml:195(para)
msgid ""
-"You can find combined images containing the installer kernel and ramdisk in "
-"the <code>images/netboot/</code> directory of the installation tree. These "
-"are intended for network booting with TFTP, but can be used in many ways."
+"You can find combined images containing the installer kernel and "
+"ramdisk in the <code>images/netboot/</code> directory of the "
+"installation tree. These are intended for network booting with TFTP, "
+"but can be used in many ways."
msgstr ""
-#: en/ArchSpecificPPC.xml:70(para)
+#: en_US/ArchSpecificPPC.xml:202(para)
msgid ""
-"<code>yaboot</code> supports TFTP booting for IBM eServer pSeries and Apple "
-"Macintosh. The Fedora Project encourages the use of <code>yaboot</code> over "
-"the <code>netboot</code> images."
+"<code>yaboot</code> supports TFTP booting for IBM eServer pSeries "
+"and Apple Macintosh. The Fedora Project encourages the use of "
+"<code>yaboot</code> over the <code>netboot</code> images."
msgstr ""
-"<code>yaboot</code> IBM eServer pSeries ��������� Apple Macintosh ������ tftp ��������� ��������� ������ ��������������� ������ "
-"��������������� <code>yaboot</code> ������ ��������������� <code>netboot</code> ��������������������������� ��������������� ������������������ ������������ ������������ ������ ���������"
+"<code>yaboot</code> IBM eServer pSeries ��������� Apple Macintosh ������ tftp "
+"��������� ��������� ������ ��������������� ������ ��������������� <code>yaboot</code> ������ ��������������� <code>netboot</"
+"code> ��������������������������� ��������������� ������������������ ������������ ������������ ������ ���������"
-#: en/ArchSpecific.xml:8(title)
-msgid "Architecture Specific Notes"
-msgstr "��������������� ������������������ ���������������"
+#: en_US/ArchSpecific.xml:11(title)
+msgid "ArchSpecific"
+msgstr "ArchSpecific"
-#: en/ArchSpecific.xml:9(para)
+#: en_US/ArchSpecific.xml:13(para)
msgid ""
-"This section provides notes that are specific to the supported hardware "
-"architectures of Fedora Core."
+"This section provides notes that are specific to the supported "
+"hardware architectures of Fedora Core."
msgstr "������ ��������� ������������ ������������������ ��������� ������������ ��������������� ������������ ��������������������� ������������ ��������������������� ��������������� ������ ���������"
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: en/ArchSpecific.xml:0(None)
+#: en_US/ArchSpecific.xml:0(None)
msgid "translator-credits"
msgstr "��������������������� ������������ ��������� <aalam(a)redhat.com> 2006"
18 years
docs-common/common fedora-entities-pa.ent, NONE, 1.1 legalnotice-opl-pa.xml, NONE, 1.1
by fedora-docs-commits@redhat.com
Author: apbrar
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17519
Added Files:
fedora-entities-pa.ent legalnotice-opl-pa.xml
Log Message:
update for new pa (Punjabi) Translation files
***** Error reading new file: [Errno 2] No such file or directory: 'fedora-entities-pa.ent'
--- NEW FILE legalnotice-opl-pa.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: -->
<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
<!ENTITY % FEDORA-ENTITIES-PA SYSTEM "fedora-entities-pa.ent">
%FEDORA-ENTITIES-PA;
]>
<!--
To use the content of this legal notice in another document, simply
use the XInclude standard. Logically there are only two elements
you need to reference, as follows:
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="legalnotice-opl-en.xml"
xpointer="element(opl.permission)"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="legalnotice-opl-en.xml" xpointer="element(opl.require)"/>
You may insert these includes in any element which can contain a
<para> and an <orderedlist> element.
-->
<legalnotice id="legalnotice-opl">
<para id="opl.permission">
������ ������������������������ ��������� ��������������������������� ��������������������� (OPL), ������������ 1.0 ��������� ������������ Permission is granted to copy, distribute, and/or modify this
������ ������������ ��������� ���������, ������������, ���������/��������� ������������ ������ ������������������ ���������
OPL ������������ ������������������ ������������ ������ ��������������� ���������������:
</para>
<orderedlist numeration="upperroman" id="opl.terms">
<listitem id="opl.require">
<bridgehead>REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED
VERSIONS</bridgehead>
<para>
Open Publication works may be reproduced and distributed in
whole or in part, in any medium physical or electronic, provided
that the terms of this license are adhered to, and that this
license or an incorporation of it by reference (with any options
elected by the author(s) and/or publisher) is displayed in the
reproduction.
</para>
<para>
Proper form for an incorporation by reference is as follows:
</para>
<para>
Copyright (c) <year> by <author's name or designee>.
This material may be distributed only subject to the terms and
conditions set forth in the Open Publication License, vX.Y or
later (the latest version is presently available at <ulink
url="http://www.opencontent.org/openpub/"/>).
</para>
<para>
The reference must be immediately followed with any options
elected by the author(s) and/or publisher of the document (see
section VI). Commercial redistribution of Open
Publication-licensed material is permitted. Any publication in
standard (paper) book form shall require the citation of the
original publisher and author. The publisher and author's names
shall appear on all outer surfaces of the book. On all outer
surfaces of the book the original publisher's name shall be as
large as the title of the work and cited as possessive with
respect to the title.
</para>
</listitem>
<listitem id="opl.copyright">
<bridgehead>COPYRIGHT</bridgehead>
<para>
The copyright to each Open Publication is owned by its author(s)
or designee.
</para>
</listitem>
<listitem id="opl.scope">
<bridgehead>SCOPE OF LICENSE</bridgehead>
<para>
The following license terms apply to all Open Publication works,
unless otherwise explicitly stated in the document.
</para>
<para>
Mere aggregation of Open Publication works or a portion of an
Open Publication work with other works or programs on the same
media shall not cause this license to apply to those other
works. The aggregate work shall contain a notice specifying the
inclusion of the Open Publication material and appropriate
copyright notice.
</para>
<para>
SEVERABILITY. If any part of this license is found to be
unenforceable in any jurisdiction, the remaining portions of the
license remain in force.
</para>
<para>
NO WARRANTY. Open Publication works are licensed and provided
"as is" without warranty of any kind, express or implied,
including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose or a
warranty of non-infringement.
</para>
</listitem>
<listitem id="opl.modified.works">
<bridgehead>REQUIREMENTS ON MODIFIED WORKS</bridgehead>
<para>
All modified versions of documents covered by this license,
including translations, anthologies, compilations and partial
documents, must meet the following requirements:
</para>
<orderedlist>
<listitem>
<para>
The modified version must be labeled as such.
</para>
</listitem>
<listitem>
<para>
The person making the modifications must be identified and
the modifications dated.
</para>
</listitem>
<listitem>
<para>
Acknowledgement of the original author and publisher if
applicable must be retained according to normal academic
citation practices.
</para>
</listitem>
<listitem>
<para>
The location of the original unmodified document must be
identified.
</para>
</listitem>
<listitem>
<para>
The original author's (or authors') name(s) may not be used
to assert or imply endorsement of the resulting document
without the original author's (or authors') permission.
</para>
</listitem>
</orderedlist>
</listitem>
<listitem id="opl.good-practice">
<bridgehead>GOOD-PRACTICE RECOMMENDATIONS</bridgehead>
<para>
In addition to the requirements of this license, it is requested
from and strongly recommended of redistributors that:
</para>
<orderedlist>
<listitem>
<para>
If you are distributing Open Publication works on hardcopy
or CD-ROM, you provide email notification to the authors of
your intent to redistribute at least thirty days before your
manuscript or media freeze, to give the authors time to
provide updated documents. This notification should describe
modifications, if any, made to the document.
</para>
</listitem>
<listitem>
<para>
All substantive modifications (including deletions) be
either clearly marked up in the document or else described
in an attachment to the document.
</para>
</listitem>
<listitem>
<para>
Finally, while it is not mandatory under this license, it is
considered good form to offer a free copy of any hardcopy
and CD-ROM expression of an Open Publication-licensed work
to its author(s).
</para>
</listitem>
</orderedlist>
</listitem>
<listitem id="opl.options">
<bridgehead>LICENSE OPTIONS</bridgehead>
<para>
The author(s) and/or publisher of an Open Publication-licensed
document may elect certain options by appending language to the
reference to or copy of the license. These options are
considered part of the license instance and must be included
with the license (or its incorporation by reference) in derived
works.
</para>
<para>
A. To prohibit distribution of substantively modified versions
without the explicit permission of the author(s). "Substantive
modification" is defined as a change to the semantic content of
the document, and excludes mere changes in format or
typographical corrections.
</para>
<para>
To accomplish this, add the phrase 'Distribution of
substantively modified versions of this document is prohibited
without the explicit permission of the copyright holder.' to the
license reference or copy.
</para>
<para>
B. To prohibit any publication of this work or derivative works
in whole or in part in standard (paper) book form for commercial
purposes is prohibited unless prior permission is obtained from
the copyright holder.
</para>
<para>
To accomplish this, add the phrase 'Distribution of the work or
derivative of the work in any standard (paper) book form is
prohibited unless prior permission is obtained from the
copyright holder.' to the license reference or copy.
</para>
</listitem>
</orderedlist>
</legalnotice>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
18 years
yum-software-management Makefile,1.9,1.10
by fedora-docs-commits@redhat.com
Author: apbrar
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17386
Modified Files:
Makefile
Log Message:
new language pa is added Make file
Index: Makefile
===================================================================
RCS file: /cvs/docs/yum-software-management/Makefile,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- Makefile 13 Mar 2006 00:23:27 -0000 1.9
+++ Makefile 1 May 2006 06:40:12 -0000 1.10
@@ -17,7 +17,7 @@
#
DOCBASE = yum-software-management
PRI_LANG = en_US
-OTHERS = zh_CN
+OTHERS = pa zh_CN
DOC_ENTITIES = doc-entities
########################################################################
# List each XML file of your document in the template below. Append the
18 years
yum-software-management/po pa.po,NONE,1.1
by fedora-docs-commits@redhat.com
Author: apbrar
Update of /cvs/docs/yum-software-management/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17356
Added Files:
pa.po
Log Message:
new Translation File pa.po is added
--- NEW FILE pa.po ---
# translation of pa.po to Punjabi
# A S Alam <apbrar(a)gmail.com>, 2006.
msgid ""
msgstr ""
"Project-Id-Version: pa\n"
"POT-Creation-Date: 2006-05-01 11:38+0530\n"
"PO-Revision-Date: 2006-05-01 11:39+0530\n"
"Last-Translator: A S Alam <apbrar(a)gmail.com>\n"
"Language-Team: Punjabi <fedora-trans-pa(a)redhat.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.2\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
#: en_US/doc-entities.xml:4(title)
msgid "Local entities for Yum Tutorial"
msgstr "��������� ��������������������� ������ ������������ ���������������������"
#: en_US/doc-entities.xml:7(comment)
msgid "Document name"
msgstr "������������������������ ���������"
#: en_US/doc-entities.xml:8(text)
msgid "yum-software-management"
msgstr "yum-software-management"
#: en_US/doc-entities.xml:11(comment)
msgid "Version number"
msgstr "������������ ������������"
#: en_US/doc-entities.xml:12(text)
msgid "1.31"
msgstr "1.31"
#: en_US/doc-entities.xml:15(comment)
msgid "Date of last revision"
msgstr "������������ ��������������������� ������ ������������"
#: en_US/doc-entities.xml:16(text)
msgid "2006-04-30"
msgstr "2006-04-30"
#: en_US/doc-entities.xml:19(comment)
msgid "Document ID"
msgstr "������������������������ ID"
#: en_US/doc-entities.xml:20(text)
msgid "<use entity=\"DOCNAME\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE\"/>)"
msgstr "<use entity=\"DOCNAME\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE\"/>)"
#: en_US/doc-entities.xml:26(comment)
msgid "Local version of Fedora Core for this document"
msgstr "������ ������������������������ ������ ������������������ ��������� ������ ������������ ������������"
#: en_US/doc-entities.xml:27(text)
msgid "5"
msgstr "5"
#: en_US/yum-software-management.xml:18(title)
msgid "Introduction"
msgstr "��������� ������������"
#: en_US/yum-software-management.xml:21(title)
msgid "Purpose"
msgstr "������������"
#: en_US/yum-software-management.xml:23(para)
msgid "This document presents basic concepts of software management on Fedora systems. It outlines the major functions of <command>yum</command>, the recommended software management tool for Fedora."
msgstr ""
#: en_US/yum-software-management.xml:32(title)
msgid "Audience"
msgstr "���������������"
#: en_US/yum-software-management.xml:34(para)
msgid "This document is intended for Fedora users of all levels of experience."
msgstr "������ ������������������������ ������������ ������ ������������ ������ ��������������� ������ ������������������ ������������������������ ������ ������������ ������������ ��������� ���������"
#: en_US/yum-software-management.xml:41(title)
msgid "Using This Document"
msgstr "������ ������������������������ ������ ���������������"
#: en_US/yum-software-management.xml:43(para)
msgid "This document is a reference for using <command>yum</command>. You may wish to read some or all of the sections, depending upon your needs and level of experience. If you are a new user, read <xref linkend=\"sn-software-management-concepts\"/> before using <command>yum</command> for the first time. Experienced Linux users should start with <xref linkend=\"sn-managing-packages\"/>."
msgstr ""
#: en_US/yum-software-management.xml:55(title)
msgid "Previous Versions of Fedora Core"
msgstr "������������������ ��������� ������ ������������������ ������������"
#: en_US/yum-software-management.xml:57(para)
msgid "This document describes the configuration of <command>yum</command> on current versions of Fedora Core. You must perform the additional step noted in <xref linkend=\"sn-authorizing-package-sources\"/> to enable <command>yum</command> on Fedora Core 3."
msgstr ""
#: en_US/yum-software-management.xml:66(para)
msgid "Most of the examples in this document use the package <filename>tsclient</filename>, which is included with Fedora Core. The <filename>tsclient</filename> package provides an application for remote desktop access. If you install it successfully you may start the application by choosing <menuchoice><guimenu>Applications</guimenu><guisubmenu>Internet</guisubmenu><guimenuitem>Terminal Server Client</guimenuitem></menuchoice>. To use the examples, substitute the name of the relevant package for <filename>tsclient</filename>. The example commands for Fedora package groups use the <filename>MySQL Database</filename> group."
msgstr ""
#: en_US/yum-software-management.xml:81(title)
msgid "Avoid Logging in with the Root Account"
msgstr "��������� (root) ������������ ��������� ��������������� ��������� ��������� ���������"
#: en_US/yum-software-management.xml:83(para)
msgid "You do not need to log in with the <systemitem class=\"username\">root</systemitem> account in order to manage your Fedora system. All of the commands shown in this tutorial that require <systemitem class=\"username\">root</systemitem> access will prompt you for the <systemitem class=\"username\">root</systemitem> password. The example terminal commands use <command>su <option>-c</option></command> to provide this facility."
msgstr ""
#: en_US/yum-software-management.xml:96(para)
msgid "Fedora Core includes a <command>yum</command> configuration that is suitable for independent systems with Internet access. You may use <command>yum</command> and related software on such systems without any additional configuration."
msgstr ""
#: en_US/yum-software-management.xml:103(para)
msgid "If your system is part of a managed network, consult your network administrators for advice. You may need to configure <command>yum</command> to use a network proxy server. <xref linkend=\"sn-yum-proxy-server\"/> explains how to configure <command>yum</command> to use a proxy server. Administrators may also suggest or require that <command>yum</command> clients use specific package repositories. Refer to <xref linkend=\"sn-using-repositories\"/> for instructions on how to configure access to repositories."
msgstr ""
#: en_US/yum-software-management.xml:115(para)
msgid "To improve performance and enable disconnected operations, activate the <command>yum</command> caches on your system. Refer to <xref linkend=\"sn-yum-caching\"/> for more information on the caching option."
msgstr ""
#: en_US/yum-software-management.xml:124(title)
msgid "Additional Resources"
msgstr "��������� ������������"
#: en_US/yum-software-management.xml:126(primary) en_US/yum-software-management.xml:130(primary) en_US/yum-software-management.xml:145(primary) en_US/yum-software-management.xml:149(primary) en_US/yum-software-management.xml:605(primary) en_US/yum-software-management.xml:1101(primary) en_US/yum-software-management.xml:1864(primary) en_US/yum-software-management.xml:1908(primary) en_US/yum-software-management.xml:1946(primary)
msgid "yum"
msgstr "��������� (yum)"
#: en_US/yum-software-management.xml:127(secondary)
msgid "documentation"
msgstr "������������������������"
#: en_US/yum-software-management.xml:131(secondary)
msgid "man pages"
msgstr "man ������������"
#: en_US/yum-software-management.xml:133(para)
msgid "The <command>yum</command> utility has features and options not discussed in this document. Read the <command>man</command> pages for <command>yum(8)</command> and <filename>yum.conf(5)</filename> to learn more, using the following commands:"
msgstr ""
#: en_US/yum-software-management.xml:141(userinput)
#, no-wrap
msgid "man yum\nman yum.conf"
msgstr "man yum\nman yum.conf"
#: en_US/yum-software-management.xml:146(secondary)
msgid "Web sites"
msgstr "������������ ������������������"
#: en_US/yum-software-management.xml:150(secondary)
msgid "mailing lists"
msgstr "������������������ ������������������"
#: en_US/yum-software-management.xml:152(para)
msgid "Other useful <command>yum</command> resources on the Internet include:"
msgstr ""
#: en_US/yum-software-management.xml:159(term)
msgid "Project Web site"
msgstr "������������������������ ������������ ������������"
#: en_US/yum-software-management.xml:170(term)
msgid "Users mailing list"
msgstr "������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:181(term)
msgid "Development mailing list"
msgstr "������������ ������������������ ������������"
#: en_US/yum-software-management.xml:192(title)
msgid "Check Bugzilla First"
msgstr "������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:193(para)
msgid "If you encounter a persistent error with a specific operation, visit <ulink url=\"http://bugzilla.redhat.com\"/> and review the bug reports for the package or packages involved. An error in a package may cause all <command>yum</command> operations that rely on that package to fail. Please file bug reports for Fedora packages, including <command>yum</command>, on this Bugzilla web site."
msgstr ""
#: en_US/yum-software-management.xml:206(title)
msgid "Software Management Concepts"
msgstr "������������������������ ��������������� ������������������"
#: en_US/yum-software-management.xml:209(title)
msgid "About Packages"
msgstr "��������������������� ������������"
#: en_US/yum-software-management.xml:211(primary) en_US/yum-software-management.xml:405(primary) en_US/yum-software-management.xml:409(primary) en_US/yum-software-management.xml:947(primary) en_US/yum-software-management.xml:1292(primary) en_US/yum-software-management.xml:1766(primary)
msgid "packages"
msgstr "���������������"
#: en_US/yum-software-management.xml:212(secondary) en_US/yum-software-management.xml:250(secondary) en_US/yum-software-management.xml:327(secondary) en_US/yum-software-management.xml:378(secondary)
msgid "defined"
msgstr "������������������������"
#: en_US/yum-software-management.xml:214(para)
msgid "Fedora software and documentation is supplied in the form of files called RPM <firstterm>packages</firstterm>. Each package is a compressed archive containing product information, program files, icons, documentation and management scripts. Management applications use these files to safely locate, install, update and remove software. For example, the Fedora installation process uses the packages supplied with Fedora Core to build or upgrade a system to your requirements."
msgstr ""
#: en_US/yum-software-management.xml:225(para)
msgid "Packages also include a digital signature to prove their source. Software management utilities verify this digital signature by using a GPG <firstterm>public key</firstterm>. The <command>yum</command> and <command>rpm</command> utilities share a common <firstterm>keyring</firstterm> that stores all of the public keys for approved package sources. The system administrator configures these approved package sources."
msgstr ""
#: en_US/yum-software-management.xml:236(title)
msgid "All Fedora Packages are Open Source Software"
msgstr "������ ������������������ ��������������� ��������� ������������ ������������������������ ������"
#: en_US/yum-software-management.xml:238(para)
msgid "All of the software provided by the Fedora Project is open source software. You may download and install Fedora packages on as many systems as desired."
msgstr ""
#: en_US/yum-software-management.xml:247(title)
msgid "About Repositories"
msgstr "��������������� (���������������������������) ������������"
#: en_US/yum-software-management.xml:249(primary) en_US/yum-software-management.xml:1161(primary) en_US/yum-software-management.xml:1201(primary) en_US/yum-software-management.xml:1296(primary) en_US/yum-software-management.xml:1354(primary) en_US/yum-software-management.xml:1358(primary)
msgid "repositories"
msgstr "���������������������������"
#: en_US/yum-software-management.xml:252(para)
msgid "A <firstterm>repository</firstterm> is a prepared directory or Web site that contains software packages and index files. Software management utilities such as <command>yum</command> automatically locate and obtain the correct RPM packages from these repositories. This method frees you from having to manually find and install new applications or updates. You may use a single command to update all system software, or search for new software by specifying criteria."
msgstr ""
#: en_US/yum-software-management.xml:263(para)
msgid "A network of servers provide several repositories for each version of Fedora Core. The package management utilities in Fedora Core are already configured to use three of these repositories:"
msgstr ""
#: en_US/yum-software-management.xml:271(term)
msgid "Base"
msgstr "������������"
#: en_US/yum-software-management.xml:275(para)
msgid "The packages that make up a Fedora Core release, as it is on disc"
msgstr "���������������, ������ ������ ������������ ������������ ��������� ������������������ ��������� ������������������ ������������������ ������"
#: en_US/yum-software-management.xml:282(term)
msgid "Updates"
msgstr "������������������"
#: en_US/yum-software-management.xml:286(para)
msgid "Updated versions of packages that are provided in Base"
msgstr "��������������������� ������ ������������������ ������������ ������������, ������ ������ ������������ ������������������ ��������������������� ������"
#: en_US/yum-software-management.xml:293(term)
msgid "Extras"
msgstr "������������ (������������������)"
#: en_US/yum-software-management.xml:297(para)
msgid "Packages for a large selection of additional software"
msgstr "������������ ��������� ������ ��������� ������������������������"
#: en_US/yum-software-management.xml:305(title)
msgid "Fedora Development Repositories"
msgstr "������������������ ������������ ���������������������������������"
#: en_US/yum-software-management.xml:307(para)
msgid "Fedora Core also includes settings for several alternative repositories. These provide packages for various types of test system, and replace one or more of the standard repositories. Only enable support for one of the following repositories if you test or develop Fedora software: <filename>fedora-devel</filename> (Rawhide), <filename>fedora-extras-devel</filename>, and <filename>updates-testing</filename>."
msgstr ""
#: en_US/yum-software-management.xml:319(para)
msgid "Third-party software developers also provide repositories for their Fedora compatible packages. To learn how to configure your Fedora system to use third-party repositories, read <xref linkend=\"sn-using-repositories\"/>."
msgstr ""
#: en_US/yum-software-management.xml:326(primary)
msgid "package groups"
msgstr "��������������� ���������������"
#: en_US/yum-software-management.xml:329(para)
msgid "You may also use the <firstterm>package groups</firstterm> provided by the Fedora repositories to manage related packages as sets. Some third-party repositories add packages to these groups, or provide their packages as additional groups."
msgstr ""
#: en_US/yum-software-management.xml:338(title)
msgid "Available Package Groups"
msgstr "������������������ ��������������� ���������������"
#: en_US/yum-software-management.xml:340(para)
msgid "To view a list of all of the available package groups for your Fedora system, run the command <command>su -c 'yum grouplist'</command>."
msgstr ""
#: en_US/yum-software-management.xml:347(para)
msgid "Use repositories to ensure that you always receive current versions of software. If several versions of the same package are available, your management utility automatically selects the latest version."
msgstr ""
#: en_US/yum-software-management.xml:355(title)
msgid "Installing Software not from a Repository"
msgstr "��������������� ��������������������������� ��������� ������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:357(para)
msgid "Install software using manual methods only when you are confident there is no repository which can currently provide it. You may have to manage that software with manual methods, instead of with Fedora software management utilities."
msgstr ""
#: en_US/yum-software-management.xml:364(para)
msgid "The <command>yum</command> commands shown in this document use repositories as package sources. Refer to <xref linkend=\"sn-yum-installing-frompackage\"/> for details of using <command>yum</command> to install software from a package file."
msgstr ""
#: en_US/yum-software-management.xml:375(title)
msgid "About Dependencies"
msgstr "��������������������� ������������"
#: en_US/yum-software-management.xml:377(primary)
msgid "dependencies"
msgstr "���������������������"
#: en_US/yum-software-management.xml:380(para)
msgid "Some of the files installed on a Fedora distribution are <firstterm>libraries</firstterm> which may provide functions to multiple applications. When an application requires a specific library, the package which contains that library is a <firstterm>dependency</firstterm>. To properly install a package, Fedora must first satisfy its dependencies. The dependency information for a RPM package is stored within the RPM file."
msgstr ""
#: en_US/yum-software-management.xml:391(para)
msgid "The <command>yum</command> utility uses package dependency data to ensure that all of requirements for an application are met during installation. It automatically installs the packages for any dependencies not already present on your system. If a new application has requirements that conflict with existing software, <command>yum</command> aborts without making any changes to your system."
msgstr ""
#: en_US/yum-software-management.xml:403(title)
msgid "Understanding Package Names"
msgstr "��������������� ��������� ���������������"
#: en_US/yum-software-management.xml:406(secondary)
msgid "hardware compatibility"
msgstr "������������ ������������������������"
#: en_US/yum-software-management.xml:410(secondary)
msgid "naming"
msgstr "���������"
#: en_US/yum-software-management.xml:412(para)
msgid "Each package file has a long name that indicates several key pieces of information. For example, this is the full name of a <filename>tsclient</filename> package:"
msgstr ""
#: en_US/yum-software-management.xml:418(filename)
msgid "tsclient-0.132-6.i386.rpm"
msgstr "tsclient-0.132-6.i386.rpm"
#: en_US/yum-software-management.xml:420(para)
msgid "Management utilities commonly refer to packages with one of three formats:"
msgstr ""
#: en_US/yum-software-management.xml:427(para)
msgid "Package name: <filename>tsclient</filename>"
msgstr "��������������� ���������: <filename>tsclient</filename>"
#: en_US/yum-software-management.xml:432(para)
msgid "Package name with version and release numbers: <filename>tsclient-0.132-6</filename>"
msgstr "������������ ��������� ������������������ ������������ ��������� ���������������: <filename>tsclient-0.132-6</filename>"
#: en_US/yum-software-management.xml:441(para)
msgid "Package name with hardware architecture: <filename>tsclient.i386</filename>"
msgstr "������������ ��������������� ��������� ��������������� ���������: <filename>tsclient.i386</filename>"
#: en_US/yum-software-management.xml:448(para)
msgid "For clarity, <command>yum</command> lists packages in the format <filename>name.architecture</filename>. Repositories also commonly store packages in separate directories by architecture. In each case, the hardware architecture specified for the package is the <emphasis>minimum</emphasis> type of machine required to use the package."
msgstr ""
#: en_US/yum-software-management.xml:459(term)
msgid "i386"
msgstr "i386"
#: en_US/yum-software-management.xml:463(para)
msgid "Suitable for any current Intel-compatible computer"
msgstr "������������ ������ Intel-������������������ ��������������������� ������ ���������������������"
#: en_US/yum-software-management.xml:470(term)
msgid "noarch"
msgstr "noarch"
#: en_US/yum-software-management.xml:474(para)
msgid "Compatible with all computer architectures"
msgstr "������ ��������������������� ��������������������� ������ ������������������"
#: en_US/yum-software-management.xml:481(term)
msgid "ppc"
msgstr "ppc"
#: en_US/yum-software-management.xml:485(para)
msgid "Suitable for PowerPC systems, such as Apple Power Macintosh"
msgstr "PowerPC ���������������������, ��������������� ������ Apple Power Macintosh, ������ ���������������������"
#: en_US/yum-software-management.xml:493(term)
msgid "x86_64"
msgstr "x86_64"
#: en_US/yum-software-management.xml:497(para)
msgid "Suitable for 64-bit Intel-compatible processors, such as Opterons"
msgstr "64-������������ Intel-������������������ ���������������������������, ��������������� ������ ������������������ (Opterons) ������ ���������������������"
#: en_US/yum-software-management.xml:505(para)
msgid "Some software may be optimized for particular types of Intel-compatible machine. Separate packages may be provided for <option>i386</option>, <option>i586</option>, <option>i686</option> and <option>x86_64</option> computers. A machine with at least an Intel Pentium, VIA C3 or compatible CPU may use <option>i586</option> packages. Computers with an Intel Pentium Pro and above, or a current model of AMD chip, may use <option>i686</option> packages."
msgstr ""
#: en_US/yum-software-management.xml:516(para)
msgid "Use the short name of the package for <command>yum</command> commands. This causes <command>yum</command> to automatically select the most recent package in the repositories that matches the hardware architecture of your computer."
msgstr ""
#: en_US/yum-software-management.xml:523(para)
msgid "Specify a package with other name formats to override the default behavior and force <command>yum</command> to use the package that matches that version or architecture. Only override <command>yum</command> when you know that the default package selection has a bug or other fault that makes it unsuitable for installation."
msgstr ""
#: en_US/yum-software-management.xml:532(title)
msgid "Package Names"
msgstr "��������������� ���������"
#: en_US/yum-software-management.xml:533(para)
msgid "You may use any of the following formats to specify a package in a <command>yum</command> operation: <replaceable>name</replaceable>, <replaceable>name.architecture</replaceable>, <replaceable>name-version</replaceable>, <replaceable>name-version-release</replaceable>, <replaceable>name-version-release.architecture</replaceable>, and <replaceable>epoch:name-version-release.architecture</replaceable>."
msgstr ""
#: en_US/yum-software-management.xml:549(title)
msgid "Software Management Tools in Fedora Core"
msgstr "������������������ ��������� ������������ ������������������������ ��������������� ���������"
#: en_US/yum-software-management.xml:551(primary)
msgid "Add/Remove Software utility"
msgstr "������������������������ ��������������� ���������/��������������� ���������������"
#: en_US/yum-software-management.xml:554(primary)
msgid "Software Updater utility"
msgstr "������������������������ ��������������������� ���������������"
#: en_US/yum-software-management.xml:557(primary)
msgid "rpm utility"
msgstr "rpm ���������������"
#: en_US/yum-software-management.xml:559(para)
msgid "The <command>yum</command> utility is a complete software management system. Fedora Core also includes two graphical applications for software management that use <command>yum</command>. The <application>pup</application> utility provides an interface for updating software, and the <application>pirut</application> application enables you to add or remove software."
msgstr ""
#: en_US/yum-software-management.xml:568(para)
msgid "Both graphical tools appear in the <guimenu>Applications</guimenu> desktop menu. To update your system with <application>pup</application>, select <menuchoice><guimenu>Applications</guimenu><guisubmenu>System Tools</guisubmenu><guimenuitem>Software Updater</guimenuitem></menuchoice>. To add or remove software with <application>pirut</application>, select <menuchoice><guimenu>Applications</guimenu><guimenuitem>Add/Remove Software</guimenuitem></menuchoice>."
msgstr ""
#: en_US/yum-software-management.xml:580(para)
msgid "The <command>rpm</command> command-line utility has many functions for working with individual RPM packages. You may use it to manually install and remove packages from your system. If you install software with the <command>rpm</command> utility, you must manually check and install any dependencies. For this reason, <application>pirut</application> and <command>yum</command> are the recommended methods for installing software."
msgstr ""
#: en_US/yum-software-management.xml:591(title)
msgid "Current Package Versions"
msgstr "������������������ ��������������� ������������"
#: en_US/yum-software-management.xml:593(para)
msgid "The <application>pirut</application> and <command>yum</command> utilities ensure that you have the most recent version of software packages. Other methods do not guarantee that the packages are current."
msgstr ""
#: en_US/yum-software-management.xml:603(title)
msgid "Managing Software with <command>yum</command>"
msgstr "<command>yum</command> ��������� ������������������������ ��������������� ������������"
#: en_US/yum-software-management.xml:606(secondary)
msgid "software management"
msgstr "������������������������ ���������������"
#: en_US/yum-software-management.xml:608(para)
msgid "Use the <command>yum</command> utility to modify the software on your system in four ways:"
msgstr ""
#: en_US/yum-software-management.xml:616(para)
msgid "To install new software from package repositories"
msgstr "��������������� ��������������������������� ��������� ������������ ������������������������ ������������������ ���������"
#: en_US/yum-software-management.xml:621(para)
msgid "To install new software from an individual package file"
msgstr "��������� ��������������� ��������������� ������������ ��������� ������������ ������������������������ ������������������ ��������� ������"
#: en_US/yum-software-management.xml:626(para)
msgid "To update existing software on your system"
msgstr "������������ ��������������� ������������ ������������������ ������������������������ ��������� ������������������ ��������� ������"
#: en_US/yum-software-management.xml:631(para)
msgid "To remove unwanted software from your system"
msgstr "������������ ��������������� ��������� ������-������������������ ������������������������ ��������������� ������"
#: en_US/yum-software-management.xml:639(title)
msgid "Installing Software from a Package File"
msgstr "��������� ��������������� ������������ ��������� ������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:641(para)
msgid "The <command>yum</command> commands shown in this section use repositories as package sources. Refer to <xref linkend=\"sn-yum-installing-frompackage\"/> for details of using <command>yum</command> to install software from an individual package file."
msgstr ""
#: en_US/yum-software-management.xml:650(para)
msgid "To use <command>yum</command>, specify a function and one or more packages or package groups. Each section below gives some examples."
msgstr ""
#: en_US/yum-software-management.xml:656(para)
msgid "For each operation, <command>yum</command> downloads the latest package information from the configured repositories. If your system uses a slow network connection <command>yum</command> may require several seconds to download the repository indexes and the header files for each package."
msgstr ""
#: en_US/yum-software-management.xml:664(para)
msgid "The <command>yum</command> utility searches these data files to determine the best set of actions to produce the required result, and displays the transaction for you to approve. The transaction may include the installation, update, or removal of additional packages, in order to resolve software dependencies."
msgstr ""
#: en_US/yum-software-management.xml:673(title)
msgid "Format of <command>yum</command> Transaction Reports"
msgstr "<command>yum</command> ��������������� ������������������������ ������ ������������������"
#: en_US/yum-software-management.xml:675(para)
msgid "This is an example of the transaction for installing <filename>tsclient</filename>:"
msgstr "������ <filename>tsclient</filename> ��������� ������������������ ��������� ������ ��������������� ������ ������������������ ������:"
#: en_US/yum-software-management.xml:680(computeroutput)
#, no-wrap
msgid "=============================================================================\n Package Arch Version Repository Size\n=============================================================================\nInstalling:\n tsclient i386 0.132-6 base 247 k\nInstalling for dependencies:\n rdesktop i386 1.4.0-2 base 107 k\n\nTransaction Summary\n=============================================================================\nInstall 2 Package(s)\nUpdate 0 Package(s)\nRemove 0 Package(s)\nTotal download size: 355 k\nIs this ok [y/N]:"
msgstr "=============================================================================\n Package Arch Version Repository Size\n=============================================================================\nInstalling:\n tsclient i386 0.132-6 base 247 k\nInstalling for dependencies:\n rdesktop i386 1.4.0-2 base 107 k\n\nTransaction Summary\n=============================================================================\nInstall 2 Package(s)\nUpdate 0 Package(s)\nRemove 0 Package(s)\nTotal download size: 355 k\nIs this ok [y/N]:"
#: en_US/yum-software-management.xml:698(para)
msgid "Review the list of changes, and then press <keycap>y</keycap> to accept and begin the process. If you press <keycap>N</keycap> or <keycap>Enter</keycap>, <command>yum</command> does not download or change any packages."
msgstr ""
#: en_US/yum-software-management.xml:706(title)
msgid "Package Versions"
msgstr "��������������� ������������"
#: en_US/yum-software-management.xml:708(para)
msgid "The <command>yum</command> utility only displays and uses the newest version of each package, unless you specify an older version."
msgstr ""
#: en_US/yum-software-management.xml:715(para)
msgid "The <command>yum</command> utility also imports the repository public key if it is not already installed on the <command>rpm</command> keyring."
msgstr ""
#: en_US/yum-software-management.xml:722(title)
msgid "Format of <command>yum</command> Public Key Import"
msgstr "<command>yum</command> ��������������� ��������������� ������������ ������ ������������������"
#: en_US/yum-software-management.xml:724(para)
msgid "This is an example of the public key import:"
msgstr "������ ��������������� ��������������� ������������ ��������� ������ ������������������ ������:"
#: en_US/yum-software-management.xml:728(computeroutput)
#, no-wrap
msgid "warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2\npublic key not available for tsclient-0.132-6.i386.rpm\nRetrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora\nImporting GPG key 0x4F2A6FD2 \"Fedora Project <fedora(a)redhat.com>\"\nIs this ok [y/N]:"
msgstr "warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2\npublic key not available for tsclient-0.132-6.i386.rpm\nRetrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora\nImporting GPG key 0x4F2A6FD2 \"Fedora Project <fedora(a)redhat.com>\"\nIs this ok [y/N]:"
#: en_US/yum-software-management.xml:736(para)
msgid "Check the public key, and then press <keycap>y</keycap> to import the key and authorize the key for use. If you press <keycap>N</keycap> or <keycap>Enter</keycap>, <command>yum</command> stops without installing any packages."
msgstr "Check the public key, and then press <keycap>y</keycap> to import the key and authorize the key for use. If you press <keycap>N</keycap> or <keycap>Enter</keycap>, <command>yum</command> stops without installing any packages."
#: en_US/yum-software-management.xml:743(para)
msgid "To ensure that downloaded packages are genuine, <command>yum</command> verifies the digital signature of each package against the public key of the provider. Once all of the packages required for the transaction are successfully downloaded and verified, <command>yum</command> applies them to your system."
msgstr ""
#: en_US/yum-software-management.xml:752(title)
msgid "Transaction Log"
msgstr "��������������� ���������"
#: en_US/yum-software-management.xml:754(para)
msgid "Every completed transaction records the affected packages in the log file <indexterm><primary>log file</primary></indexterm><filename>/var/log/yum.log</filename>. You may only read this file with <systemitem class=\"username\">root</systemitem> access."
msgstr ""
#: en_US/yum-software-management.xml:766(title)
msgid "Installing New Software with <command>yum</command>"
msgstr "<command>yum</command> ��������� ������������ ������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:768(primary) en_US/yum-software-management.xml:1472(primary)
msgid "installing software"
msgstr "������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:769(see)
msgid "software, installing"
msgstr "������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:772(primary) en_US/yum-software-management.xml:823(primary) en_US/yum-software-management.xml:895(primary) en_US/yum-software-management.xml:1477(primary)
msgid "software"
msgstr "������������������������"
#: en_US/yum-software-management.xml:773(secondary) en_US/yum-software-management.xml:1633(secondary)
msgid "installing"
msgstr "������������������ ������������"
#: en_US/yum-software-management.xml:775(para)
msgid "To install the package <filename>tsclient</filename>, enter the command:"
msgstr "��������������� <filename>tsclient</filename> ������������������ ��������� ������ ��������������� ���������:"
#: en_US/yum-software-management.xml:780(replaceable) en_US/yum-software-management.xml:831(replaceable) en_US/yum-software-management.xml:910(replaceable) en_US/yum-software-management.xml:976(replaceable) en_US/yum-software-management.xml:1881(replaceable)
msgid "tsclient"
msgstr "tsclient"
#: en_US/yum-software-management.xml:780(userinput)
#, no-wrap
msgid "su -c 'yum install <placeholder-1/>'"
msgstr "su -c 'yum install <placeholder-1/>'"
#: en_US/yum-software-management.xml:782(para) en_US/yum-software-management.xml:795(para) en_US/yum-software-management.xml:833(para) en_US/yum-software-management.xml:871(para) en_US/yum-software-management.xml:912(para) en_US/yum-software-management.xml:925(para) en_US/yum-software-management.xml:978(para) en_US/yum-software-management.xml:1022(para) en_US/yum-software-management.xml:1574(para) en_US/yum-software-management.xml:1678(para) en_US/yum-software-management.xml:1692(para) en_US/yum-software-management.xml:1752(para) en_US/yum-software-management.xml:1883(para)
msgid "Enter the password for the <systemitem class=\"username\">root</systemitem> account when prompted."
msgstr "������������ ������������������ ������������ ��������� <systemitem class=\"username\">root</systemitem> ������������ ������ ������������-��������� ������������"
#: en_US/yum-software-management.xml:788(para)
msgid "To install the package group <filename>MySQL Database</filename>, enter the command:"
msgstr "<filename>MySQL Database</filename> ��������������� ��������������� ������������������ ��������� ������, ��������� ��������������� ��������������� ���������:"
#: en_US/yum-software-management.xml:793(replaceable) en_US/yum-software-management.xml:869(replaceable) en_US/yum-software-management.xml:923(replaceable)
msgid "MySQL Database"
msgstr "MySQL Database"
#: en_US/yum-software-management.xml:793(userinput)
#, no-wrap
msgid "su -c 'yum groupinstall \"<placeholder-1/>\"'"
msgstr "su -c 'yum groupinstall \"<placeholder-1/>\"'"
#: en_US/yum-software-management.xml:802(title)
msgid "New Services Require Activation"
msgstr "������������������ ��������������������� ��������� ��������������� ��������� ������ ���������"
#: en_US/yum-software-management.xml:804(para)
msgid "When you install a service, Fedora does not activate or start it. To configure a new service to run on bootup, choose <menuchoice><guimenu>Desktop</guimenu><guisubmenu>System Settings</guisubmenu><guisubmenu>Server Settings</guisubmenu><guimenuitem>Services</guimenuitem></menuchoice>, or use the <command>chkconfig</command> and <command>service</command> command-line utilities."
msgstr ""
#: en_US/yum-software-management.xml:817(title)
msgid "Updating Software with <command>yum</command>"
msgstr "<command>yum</command> ��������� ������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:819(primary) en_US/yum-software-management.xml:824(secondary) en_US/yum-software-management.xml:1097(primary)
msgid "updating"
msgstr "������������������ ������������"
#: en_US/yum-software-management.xml:820(secondary)
msgid "software packages"
msgstr "������������������������ ���������������"
#: en_US/yum-software-management.xml:826(para)
msgid "To update the <filename>tsclient</filename> package to the latest version, type:"
msgstr "<filename>tsclient</filename> ��������������� ��������� ������������ ������������ ��������� ������������������ ��������� ������ ������������:"
#: en_US/yum-software-management.xml:831(userinput)
#, no-wrap
msgid "su -c 'yum update <placeholder-1/>'"
msgstr "su -c 'yum update <placeholder-1/>'"
#: en_US/yum-software-management.xml:840(title)
msgid "New Software Versions Require Reloading"
msgstr "������������ ������������������������ ������������ ������ ���������-��������� ������������ ������������������ ������"
#: en_US/yum-software-management.xml:842(para)
msgid "If a piece of software is in use when you update it, the old version remains active until the application or service is restarted. Kernel updates take effect when you reboot the system."
msgstr ""
#: en_US/yum-software-management.xml:851(title)
msgid "Kernel Packages"
msgstr "������������ ���������������"
#: en_US/yum-software-management.xml:853(para)
msgid "Kernel packages remain on the system after they have been superseded by newer versions. This enables you to boot your system with an older kernel if an error occurs with the current kernel. To minimize maintenance, <command>yum</command> automatically removes obsolete kernel packages from your system, retaining only the current kernel and the previous version."
msgstr ""
#: en_US/yum-software-management.xml:864(para)
msgid "To update all of the packages in the package group <filename>MySQL Database</filename>, enter the command:"
msgstr ""
#: en_US/yum-software-management.xml:869(userinput)
#, no-wrap
msgid "su -c 'yum groupupdate \"<placeholder-1/>\"'"
msgstr "su -c 'yum groupupdate \"<placeholder-1/>\"'"
#: en_US/yum-software-management.xml:878(title)
msgid "Updating the Entire System"
msgstr "������������ ��������������� ������������������ ������������"
#: en_US/yum-software-management.xml:880(para)
msgid "To update all of the packages on your Fedora system, use the commands described in <xref linkend=\"sn-updating-your-system\"/>."
msgstr "������������ ������������������ ��������������� ������ ������ ��������������������� ��������� ������������������ ��������� ������, <xref linkend=\"sn-updating-your-system\"/> ������������ ��������������������� ��������������� ������������������"
#: en_US/yum-software-management.xml:890(title)
msgid "Removing Software with <command>yum</command>"
msgstr "<command>yum</command> ��������� ������������������������ ������������������"
#: en_US/yum-software-management.xml:892(primary)
msgid "removing software"
msgstr "������������������������ ������������������"
#: en_US/yum-software-management.xml:896(secondary)
msgid "removing"
msgstr "������������������"
#: en_US/yum-software-management.xml:898(para)
msgid "To remove software, <command>yum</command> examines your system for both the specified software, and any software which claims it as a dependency. The transaction to remove the software deletes both the software and the dependencies."
msgstr ""
#: en_US/yum-software-management.xml:905(para)
msgid "To remove the <filename>tsclient</filename> package from your system, use the command:"
msgstr "������������ ��������������� ��������� <filename>tsclient</filename> ��������������� ������, ��������������� ���������:"
#: en_US/yum-software-management.xml:910(userinput)
#, no-wrap
msgid "su -c 'yum remove <placeholder-1/>'"
msgstr "su -c 'yum remove <placeholder-1/>'"
#: en_US/yum-software-management.xml:918(para)
msgid "To remove all of the packages in the package group <filename>MySQL Database</filename>, enter the command:"
msgstr "��������������� ��������������� <filename>MySQL Database</filename> ������������������ ������ ��������������������� ��������� ��������������� ������, ��������������� ���������:"
#: en_US/yum-software-management.xml:923(userinput)
#, no-wrap
msgid "su -c 'yum groupremove \"<placeholder-1/>\"'"
msgstr "su -c 'yum groupremove \"<placeholder-1/>\"'"
#: en_US/yum-software-management.xml:932(title)
msgid "Data and Configuration File Retention"
msgstr "������������ ��������� ������������������ ������������ ���������-������������������"
#: en_US/yum-software-management.xml:934(para)
msgid "The removal process leaves user data in place but may remove configuration files in some cases. If a package removal does not include the configuration file, and you reinstall the package later, it may reuse the old configuration file."
msgstr ""
#: en_US/yum-software-management.xml:945(title)
msgid "Searching for Packages with <command>yum</command>"
msgstr "<command>yum</command> ��������� ��������������������� ������ ���������"
#: en_US/yum-software-management.xml:948(secondary)
msgid "locating"
msgstr "���������������"
#: en_US/yum-software-management.xml:951(primary) en_US/yum-software-management.xml:1165(primary)
msgid "searching"
msgstr "��������� ������������"
#: en_US/yum-software-management.xml:952(secondary)
msgid "for packages"
msgstr "��������������������� ������"
#: en_US/yum-software-management.xml:954(para)
msgid "Use the search features of <command>yum</command> to find software that is available from the configured repositories, or already installed on your system. Searches automatically include both installed and available packages."
msgstr ""
#: en_US/yum-software-management.xml:961(para)
msgid "The format of the results depends upon the option. If the query produces no information, there are no packages matching the criteria."
msgstr ""
#: en_US/yum-software-management.xml:968(title)
msgid "Searching by Package Name and Attributes"
msgstr "��������������� ��������� ��������� ��������������� ��������� ��������� ������������"
#: en_US/yum-software-management.xml:970(para)
msgid "To search for a specific package by name, use the <option>list</option> function. To search for the package <filename>tsclient</filename>, use the command:"
msgstr ""
#: en_US/yum-software-management.xml:976(userinput) en_US/yum-software-management.xml:991(userinput) en_US/yum-software-management.xml:1069(userinput)
#, no-wrap
msgid "su -c 'yum list <placeholder-1/>'"
msgstr "su -c 'yum list <placeholder-1/>'"
#: en_US/yum-software-management.xml:984(para)
msgid "To make your queries more precise, specify packages with a name that include other attributes, such as version or hardware architecture. To search for version 0.132 of the application, use the command:"
msgstr ""
#: en_US/yum-software-management.xml:991(replaceable)
msgid "tsclient-0.132"
msgstr "tsclient-0.132"
#: en_US/yum-software-management.xml:994(title)
msgid "Valid Package Attributes"
msgstr "��������������� ��������������� ������ ������������������"
#: en_US/yum-software-management.xml:996(para)
msgid "Refer to <xref linkend=\"sn-package-names\"/> for information on package name formats and the attributes that they include."
msgstr ""
#: en_US/yum-software-management.xml:1004(title)
msgid "Advanced Searches"
msgstr "������������������ ���������"
#: en_US/yum-software-management.xml:1006(para)
msgid "If you do not know the name of the package, use the <option>search</option> or <option>provides</option> options. Alternatively, use wild cards with any <command>yum</command> search option to broaden the search criteria."
msgstr ""
#: en_US/yum-software-management.xml:1013(para)
msgid "The <option>search</option> option checks the names, descriptions, summaries and listed package maintainers of all of the available packages to find those that match. For example, to search for all packages that relate to Palm Pilots, type:"
msgstr ""
#: en_US/yum-software-management.xml:1020(replaceable)
msgid "PalmPilot"
msgstr "PalmPilot"
#: en_US/yum-software-management.xml:1020(userinput)
#, no-wrap
msgid "su -c 'yum search <placeholder-1/>'"
msgstr "su -c 'yum search <placeholder-1/>'"
#: en_US/yum-software-management.xml:1028(para)
msgid "The <option>provides</option> function checks both the files included in the packages and the functions that the software provides. This option requires <command>yum</command> to download and read much larger index files than with the <option>search</option> option."
msgstr ""
#: en_US/yum-software-management.xml:1036(para)
msgid "To search for all packages that include files called <filename>libneon</filename>, type:"
msgstr ""
#: en_US/yum-software-management.xml:1041(replaceable)
msgid "libneon"
msgstr "libneon"
#: en_US/yum-software-management.xml:1041(userinput) en_US/yum-software-management.xml:1049(userinput)
#, no-wrap
msgid "su -c 'yum provides <placeholder-1/>'"
msgstr "su -c 'yum provides <placeholder-1/>'"
#: en_US/yum-software-management.xml:1043(para)
msgid "To search for all packages that either provide a MTA (Mail Transport Agent) service, or include files with <filename>mta</filename> in their name:"
msgstr ""
#: en_US/yum-software-management.xml:1049(replaceable)
msgid "MTA"
msgstr "MTA"
#: en_US/yum-software-management.xml:1051(para)
msgid "For each command, at the prompt enter the password for the <systemitem class=\"username\">root</systemitem> account."
msgstr ""
#: en_US/yum-software-management.xml:1056(para)
msgid "Use the standard wild-card characters to run any search option with a partial word or name: <option>?</option> to represent any one character, and <option>*</option> to mean zero or more characters. Always add the escape character (<option>\\</option>) before wild-cards."
msgstr ""
#: en_US/yum-software-management.xml:1064(para)
msgid "To <option>list</option> all packages with names that begin with <filename>tsc</filename>, type:"
msgstr ""
#: en_US/yum-software-management.xml:1069(replaceable)
msgid "tsc\\*"
msgstr "tsc\\*"
#: en_US/yum-software-management.xml:1074(title)
msgid "Understanding Matches"
msgstr "��������������� ��������� ���������������"
#: en_US/yum-software-management.xml:1076(para)
msgid "Searches with <command>yum</command> show all of the packages that match your criteria. Packages must meet the terms of the search exactly to be considered matches, unless you use wild-cards."
msgstr ""
#: en_US/yum-software-management.xml:1083(para)
msgid "For example, a search query for <filename>shadowutils</filename> or <filename>shadow-util</filename> would not produce the package <filename>shadow-utils</filename>. This package would match and be shown if the query was <filename>shadow-util\\?</filename>, or <filename>shadow\\*</filename>."
msgstr ""
#: en_US/yum-software-management.xml:1095(title)
msgid "Updating Your System with <command>yum</command>"
msgstr "������������ ��������������� ��������� <command>yum</command> ��������� ������������������ ������������"
#: en_US/yum-software-management.xml:1098(secondary)
msgid "full system"
msgstr "������������ ���������������"
#: en_US/yum-software-management.xml:1102(secondary)
msgid "updating full system"
msgstr "������������ ��������������� ������������������ ������������"
#: en_US/yum-software-management.xml:1104(para)
msgid "Use the <option>update</option> option to upgrade all of your Fedora system software to the latest version with one operation."
msgstr ""
#: en_US/yum-software-management.xml:1109(para)
msgid "To perform a full system update, type this command:"
msgstr "������������ ��������������� ��������� ������������������ ��������� ������ ������ ��������������� ���������:"
#: en_US/yum-software-management.xml:1113(userinput)
#, no-wrap
msgid "su -c 'yum update'"
msgstr "su -c 'yum update'"
#: en_US/yum-software-management.xml:1115(para) en_US/yum-software-management.xml:1272(para) en_US/yum-software-management.xml:1505(para)
msgid "At the prompt, enter the <systemitem class=\"username\">root</systemitem> password."
msgstr "��������������� ������������ <systemitem class=\"username\">root</systemitem> ������������-��������� ������������"
#: en_US/yum-software-management.xml:1122(title)
msgid "Automatically Updating Your System"
msgstr "������������ ��������������� ��������� ������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:1124(primary)
msgid "automatic updating"
msgstr "������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:1126(para)
msgid "The <filename>yum</filename> package supplied with Fedora Core includes scripts to perform full system updates every day. To activate automatic daily updates, enter this command:"
msgstr ""
#: en_US/yum-software-management.xml:1132(userinput)
#, no-wrap
msgid "su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'"
msgstr "su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'"
#: en_US/yum-software-management.xml:1134(para) en_US/yum-software-management.xml:1226(para) en_US/yum-software-management.xml:1258(para)
msgid "At the prompt, enter the password for the <systemitem class=\"username\">root</systemitem> account."
msgstr "��������������� ��������� ������������, <systemitem class=\"username\">root</systemitem> ������������ ������ ������������-��������� ������������"
#: en_US/yum-software-management.xml:1140(title)
msgid "How Daily Updates are Run"
msgstr "������������ ������������������ ��������������� ��������������� ������"
#: en_US/yum-software-management.xml:1142(para)
msgid "There is no separate <command>yum</command> service that runs on your system. The command given above enables the control script <filename>/etc/rc.d/init.d/yum</filename>. This control script activates the script <filename>/etc/cron.daily/yum.cron</filename>, which causes the <command>cron</command> service to automatically begin a system update at 4am each day."
msgstr ""
#: en_US/yum-software-management.xml:1156(title)
msgid "Configuring Access to Software Repositories"
msgstr "������������������������ ��������������������������������� ������ ��������������� ������ ������������������ ������������"
#: en_US/yum-software-management.xml:1158(primary)
msgid "Fedora Extras"
msgstr "������������������ ������������������"
#: en_US/yum-software-management.xml:1162(secondary)
msgid "finding"
msgstr "��������� ������������"
#: en_US/yum-software-management.xml:1166(secondary)
msgid "for repositories"
msgstr "��������������������������� ���������"
#: en_US/yum-software-management.xml:1168(para)
msgid "Fedora systems automatically use the Fedora Project repositories. These include Fedora Extras, the default source of packages for software that is not included with Fedora Core."
msgstr ""
#: en_US/yum-software-management.xml:1175(title)
msgid "Fedora Extras Repositories for Previous Versions of Fedora Core"
msgstr ""
#: en_US/yum-software-management.xml:1177(para)
msgid "You must manually configure Fedora Core 3 systems to use Fedora Extras, using the instructions at <ulink url=\"http://fedora.redhat.com/projects/extras/\"/>. For additional packages for Fedora Core 1 and Fedora Core 2, refer to <ulink url=\"http://www.fedora.us/\"/>."
msgstr ""
#: en_US/yum-software-management.xml:1188(para)
msgid "If the Fedora Project does not supply packages for a product, the manufacturer may provide or recommend a separate repository. Members of the community also maintain repositories to provide packages for Fedora systems. For example, <ulink url=\"http://www.jpackage.org/\"/> distributes popular Java software as packages."
msgstr ""
#: en_US/yum-software-management.xml:1199(title)
msgid "Adding a Repository as a Package Source"
msgstr "��������� ��������������������������� ��������� ��������� ��������������� ������������ ������������ ������������������ ������������"
#: en_US/yum-software-management.xml:1202(secondary)
msgid "adding to yum"
msgstr "��������� '��� ���������������"
#: en_US/yum-software-management.xml:1204(para)
msgid "To add an extra repository, place a definition file in the <filename>/etc/yum.repos.d/</filename> directory on your system. Package providers make the definition files for their repositories available on their web sites."
msgstr ""
#: en_US/yum-software-management.xml:1211(title)
msgid "Definition File Extension"
msgstr "������������ ��������������������������� ������ ������������������������"
#: en_US/yum-software-management.xml:1212(para)
msgid "The names of repository definition files end with <filename>.repo</filename>."
msgstr "��������������������������� ������������������������ ������������������ ������ ��������� ������ ��������� ������������ <filename>.repo</filename> ������������ ������������������ ���������"
#: en_US/yum-software-management.xml:1217(para)
msgid "You must have <systemitem class=\"username\">root</systemitem> access to add a file to the definitions directory. To copy the definition file <filename>example.repo</filename>, type this command:"
msgstr ""
#: en_US/yum-software-management.xml:1224(userinput)
#, no-wrap
msgid "su -c 'cp example.repo /etc/yum.repos.d/'"
msgstr "su -c 'cp example.repo /etc/yum.repos.d/'"
#: en_US/yum-software-management.xml:1231(para)
msgid "The configuration file for each repository should include a <command>gpgkey</command> setting. This setting specifies the location of a public key that verifies the packages provided by that repository. This public key is automatically imported the first time that you install software from the repository. If the configuration file provided does not include this setting, refer to <xref linkend=\"sn-authorizing-package-sources\"/>."
msgstr ""
#: en_US/yum-software-management.xml:1243(title)
msgid "Manually Authorizing Package Sources"
msgstr "������������ ��������������� ������������������ ������ ���������������������������"
#: en_US/yum-software-management.xml:1245(primary)
msgid "public keys"
msgstr "��������������� ���������������������"
#: en_US/yum-software-management.xml:1246(secondary)
msgid "adding"
msgstr "���������������"
#: en_US/yum-software-management.xml:1248(para)
msgid "To manually add a public key to your <command>rpm</command> keyring, use the <option>import</option> feature of the <command>rpm</command> utility. To import the file <filename>GPG-PUB-KEY.asc</filename>, type the following command:"
msgstr ""
#: en_US/yum-software-management.xml:1256(replaceable)
msgid "GPG-PUB-KEY.asc"
msgstr "GPG-PUB-KEY.asc"
#: en_US/yum-software-management.xml:1256(userinput) en_US/yum-software-management.xml:1270(userinput)
#, no-wrap
msgid "su -c 'rpm --import <placeholder-1/>'"
msgstr "su -c 'rpm --import <placeholder-1/>'"
#: en_US/yum-software-management.xml:1263(para)
msgid "You may also import public keys directly from a web site. For example, to import the file <filename>GPG-PUB-KEY.asc</filename> on the web site <wordasword>www.therepository.com</wordasword> use this command:"
msgstr ""
#: en_US/yum-software-management.xml:1270(replaceable)
msgid "http://www.therepository.com/GPG-PUB-KEY.asc"
msgstr "http://www.therepository.com/GPG-PUB-KEY.asc"
#: en_US/yum-software-management.xml:1279(title)
msgid "Importing the Fedora Key on Fedora Core 3"
msgstr ""
#: en_US/yum-software-management.xml:1281(para)
msgid "To add the Fedora public key to the <command>rpm</command> keyring on Fedora Core 3 systems, run the command <command>su -c 'rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora'</command>."
msgstr ""
#: en_US/yum-software-management.xml:1290(title)
msgid "Understanding Repository Compatibility"
msgstr "��������������������������� ������������������������ ��������� ���������������"
#: en_US/yum-software-management.xml:1293(secondary)
msgid "software compatibility"
msgstr "������������������������ ������������������������"
#: en_US/yum-software-management.xml:1297(secondary)
msgid "compatibility"
msgstr "������������������������"
#: en_US/yum-software-management.xml:1299(para)
msgid "The Fedora Extras repository provides packages which are built to the same standards as Fedora Core packages. Third-party packages should be compatible with these Fedora Project packages, unless the provider specifically states otherwise."
msgstr ""
#: en_US/yum-software-management.xml:1306(para)
msgid "Always read the web site of the repository for information on package compatibility before you add it as a package source. Separate repository providers may offer different and incompatible versions of the same software. Third-party repositories may also provide alternative packages for software that is included in Fedora repositories."
msgstr ""
#: en_US/yum-software-management.xml:1315(para)
msgid "Alternative packages may contain versions of the software that function differently from the version in the Fedora Project packages. Determine the benefits and potential incompatibilities before replacing Fedora Project packages with alternative versions."
msgstr ""
#: en_US/yum-software-management.xml:1323(title)
msgid "Incompatible Repositories"
msgstr "������-������������������������ ���������������������������������"
#: en_US/yum-software-management.xml:1325(para)
msgid "If you configure your system to use incompatible repositories <command>yum</command> operations may fail."
msgstr ""
#: en_US/yum-software-management.xml:1331(para)
msgid "Packages built for one version of Fedora are usually not compatible with other versions of Fedora. The web site of the provider should specifically state which versions of Fedora they support."
msgstr ""
#: en_US/yum-software-management.xml:1338(title)
msgid "Old Versions of <command>yum</command> and Current Repositories"
msgstr "<command>yum</command> ������ ������������������ ������������ ��������� ������������������ ���������������������������������"
#: en_US/yum-software-management.xml:1339(para)
msgid "The data format for repository indexes changed with version 2.1 of <command>yum</command>. This was the version supplied with Fedora Core 3. Repository providers should specify the versions of Fedora Core that they support. To confirm that an unlabeled repository is compatible with current versions of <command>yum</command>, check that it has a sub-directory called <filename>repodata/</filename>."
msgstr ""
#: en_US/yum-software-management.xml:1352(title)
msgid "Disabling or Removing Package Sources"
msgstr "��������������� ������������ ������������ ������������ ��������� ������������������"
#: en_US/yum-software-management.xml:1355(secondary)
msgid "disabling in yum"
msgstr "��������� ��������� ������������ ������������"
#: en_US/yum-software-management.xml:1359(secondary)
msgid "removing from yum"
msgstr "��������� ��������� ������������������"
#: en_US/yum-software-management.xml:1361(para)
msgid "Set <command>enable=0</command> in a definition file to prevent <command>yum</command> from using that repository. The <command>yum</command> utility ignores any definition file with this setting."
msgstr ""
#: en_US/yum-software-management.xml:1368(para)
msgid "To completely remove access to a repository:"
msgstr "��������� ��������������������������� ��������� ��������������� ��������� ������������ ������������������ ������������������:"
#: en_US/yum-software-management.xml:1373(para)
msgid "Delete the relevant file from <filename>/etc/yum.repos.d/</filename>."
msgstr "������������������������ ������������������ ��������� <filename>/etc/yum.repos.d/</filename> ������������������ ���������������"
#: en_US/yum-software-management.xml:1379(para)
msgid "Delete the cache directory from <filename>/var/cache/yum/</filename>."
msgstr "<filename>/var/cache/yum/</filename> ��������� ��������������� ��������������������������� ��������� ���������������"
#: en_US/yum-software-management.xml:1470(title)
msgid "Installing Software from an Isolated Package"
msgstr "��������� ��������������� ��������������� ��������� ������������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:1473(secondary)
msgid "from a package"
msgstr "��������� ��������������� ���������"
#: en_US/yum-software-management.xml:1474(see)
msgid "software, installing from a package"
msgstr "������������������������, ��������� ��������������� ��������� ������������������ ������������"
#: en_US/yum-software-management.xml:1478(secondary)
msgid "installing from a package"
msgstr "��������� ��������������� ��������� ������������������ ������������"
#: en_US/yum-software-management.xml:1480(para)
msgid "Use repositories and the standard <command>yum</command> commands to locate and install new software, unless the software package is not available from any repository. In these cases, use the <option>localinstall</option> function to install the software from the package file."
msgstr ""
#: en_US/yum-software-management.xml:1489(title)
msgid "Public Key is Required"
msgstr "��������������� ��������������� ������ ���������"
#: en_US/yum-software-management.xml:1491(para)
msgid "Ensure that the public key for the package source has been imported before you install a package without a repository. Refer to <xref linkend=\"sn-authorizing-package-sources\"/>."
msgstr ""
#: en_US/yum-software-management.xml:1498(para)
msgid "Enter this command to install the package <filename>tsclient-0.132-4.i386.rpm</filename>:"
msgstr "<filename>tsclient-0.132-4.i386.rpm</filename> ��������������� ������������������ ��������� ������ ������ ��������������� ���������:"
#: en_US/yum-software-management.xml:1503(replaceable)
msgid "tsclient-0.132-4.i386.rpm"
msgstr "tsclient-0.132-4.i386.rpm"
#: en_US/yum-software-management.xml:1503(userinput)
#, no-wrap
msgid "su -c 'yum localinstall <placeholder-1/>'"
msgstr "su -c 'yum localinstall <placeholder-1/>'"
#: en_US/yum-software-management.xml:1512(title)
msgid "Previously Installed Software is Updated"
msgstr "������������������ ������������������ ������������������������ ������������������ ������"
#: en_US/yum-software-management.xml:1514(para)
msgid "If the package provides a later version of software that is already installed on your system, <command>yum</command> updates the installed software."
msgstr ""
#: en_US/yum-software-management.xml:1521(para)
msgid "If the package requires software that is not installed on your system, <command>yum</command> attempts to meet the dependencies with packages from the configured repositories. You may need to manually download and install additional packages in order to satisfy all of the dependencies."
msgstr ""
#: en_US/yum-software-management.xml:1530(title)
msgid "Maintaining Manually Installed Software"
msgstr "������������ ������������������ ��������������������������� ������ ��������������� ������������"
#: en_US/yum-software-management.xml:1532(para)
msgid "If you install software that is not provided by a repository, <command>yum update</command> cannot automatically upgrade it as new versions become available. To ensure that you have the latest packages, subscribe to e-mail or RSS services that notify you when new versions are released."
msgstr ""
#: en_US/yum-software-management.xml:1543(title)
msgid "Customizing <command>yum</command>"
msgstr "<command>yum</command> ������������"
#. SE: The dictionary says "plug-in", but yum documentation uses "plugin". For consistency, I'm using "plugin" in this document.
#: en_US/yum-software-management.xml:1545(para)
msgid "To change the behavior of <command>yum</command>, you may either edit the configuration files, or install <firstterm>plugins</firstterm>. Plugins enable developers to add new features to <command>yum</command>."
msgstr ""
#: en_US/yum-software-management.xml:1553(title)
msgid "Editing the <command>yum</command> Configuration"
msgstr "<command>yum</command> ������������������ ������ ��������� ������������"
#: en_US/yum-software-management.xml:1555(primary)
msgid "configuration files"
msgstr "������������������ ������������������"
#: en_US/yum-software-management.xml:1557(para)
msgid "The file <filename>/etc/yum.conf</filename> provides the main configuration for <command>yum</command>. Settings in a repository definition file override the main configuration for those operations that use the defined repository."
msgstr ""
#: en_US/yum-software-management.xml:1564(para)
msgid "To edit <filename>/etc/yum.conf</filename>, run a text editor with <systemitem class=\"username\">root</systemitem> privileges. This command opens <filename>/etc/yum.conf</filename> with <application>gedit</application>, the default text editor for Fedora desktop systems:"
msgstr ""
#: en_US/yum-software-management.xml:1572(userinput)
#, no-wrap
msgid "su -c 'gedit /etc/yum.conf'"
msgstr "su -c 'gedit /etc/yum.conf'"
#: en_US/yum-software-management.xml:1580(para)
msgid "The main configuration file provides the settings that apply to all <command>yum</command> operations. These include caching options, and proxy server settings. The directory <filename>/etc/yum.repos.d/</filename> holds definition files for each repository that <command>yum</command> uses. Plugins use the configuration files in the directory <filename>/etc/yum/pluginconf.d/</filename>."
msgstr ""
#: en_US/yum-software-management.xml:1590(para)
msgid "The following sections in this document provide further information on configuring <command>yum</command>:"
msgstr ""
#: en_US/yum-software-management.xml:1620(title)
msgid "Further Documentation"
msgstr "��������� ������������������������"
#: en_US/yum-software-management.xml:1621(para)
msgid "Refer to the <command>man</command> page for <filename>yum.conf</filename> for a complete list of the configuration options supported by <command>yum</command>."
msgstr ""
#: en_US/yum-software-management.xml:1630(title)
msgid "Working with <command>yum</command> Plugins"
msgstr "<command>yum</command> ������������-������������ ��������� ��������� ������������"
#: en_US/yum-software-management.xml:1632(primary)
msgid "plugins"
msgstr "������������������������"
#: en_US/yum-software-management.xml:1635(para)
msgid "Each <command>yum</command> plugin is a single file, written in the Python programming language. You may download plugins from the <command>yum</command> project Web site, or from third-party providers. The <command>yum</command> project maintains a list of plugins on the page <ulink url=\"http://wiki.linux.duke.edu/YumPlugins\"/>."
msgstr ""
#: en_US/yum-software-management.xml:1644(title)
msgid "Plugin File Extension"
msgstr "������������������������ ������������ ���������������������������"
#: en_US/yum-software-management.xml:1645(para)
msgid "The names of <command>yum</command> plugin files end with <filename>.py</filename>, the standard extension for Python scripts."
msgstr ""
#: en_US/yum-software-management.xml:1651(para)
msgid "To install a plugin, copy it to the directory <filename>/usr/lib/yum-plugins/</filename>. Create a configuration file for the plugin in the directory <filename>/etc/yum/pluginconf.d/</filename>. Save the configuration file with the same name as the plugin, but with the extension <filename>.conf</filename>."
msgstr ""
#: en_US/yum-software-management.xml:1661(title)
msgid "<systemitem class=\"username\">root</systemitem> Privileges Required"
msgstr "<systemitem class=\"username\">root</systemitem> ������������������ ������������������ ������"
#: en_US/yum-software-management.xml:1663(para)
msgid "You must have <systemitem class=\"username\">root</systemitem> access to add files to the directories <filename>/usr/lib/yum-plugins/</filename> and <filename>/etc/yum/pluginconf.d/</filename>."
msgstr ""
#: en_US/yum-software-management.xml:1671(para)
msgid "For example, to copy the plugin <filename>exampleplugin.py</filename>, enter the command:"
msgstr ""
#: en_US/yum-software-management.xml:1676(userinput)
#, no-wrap
msgid "su -c 'cp exampleplugin.py /usr/lib/yum-plugins/'"
msgstr "su -c 'cp exampleplugin.py /usr/lib/yum-plugins/'"
#: en_US/yum-software-management.xml:1684(para)
msgid "You may then create a configuration file for the plugin with a text editor. This example uses <application>gedit</application>, the default text editor for Fedora desktop systems:"
msgstr ""
#: en_US/yum-software-management.xml:1690(userinput)
#, no-wrap
msgid "su -c 'gedit /etc/yum/pluginconf.d/exampleplugin.conf'"
msgstr "su -c 'gedit /etc/yum/pluginconf.d/exampleplugin.conf'"
#: en_US/yum-software-management.xml:1698(para)
msgid "Each plugin configuration file includes the <command>enabled</command> setting. Some plugins also require additional settings. To determine the correct settings, either refer to the documentation supplied with the plugin, or read the plugin file itself with any text editor."
msgstr ""
#: en_US/yum-software-management.xml:1707(title)
msgid "Example Plugin Configuration File"
msgstr "������������������ ������������������ ������������������ ������������"
#: en_US/yum-software-management.xml:1709(computeroutput)
#, no-wrap
msgid "[main]\nenabled=1\nanotheroption=0"
msgstr "[main]\nenabled=1\nanotheroption=0"
#: en_US/yum-software-management.xml:1716(title)
msgid "Plugin Installed by Default"
msgstr "��������� ��������� '��� ������������������ ������������������������"
#: en_US/yum-software-management.xml:1718(para)
msgid "<indexterm><primary>plugins</primary><secondary>installonlyn</secondary></indexterm> Fedora Core includes the <filename>installonlyn</filename> plugin. This plugin modifies <command>yum</command> to remove excess kernel packages, so that no more than a set number of kernels exist on the system. By default, <filename>installonlyn</filename> retains the two most current kernels, and automatically removes older kernel packages."
msgstr ""
#: en_US/yum-software-management.xml:1732(para)
msgid "<indexterm><primary>plugins</primary><secondary>removing</secondary></indexterm> To remove a plugin, delete both the original file and the automatically generated bytecode file from <filename>/usr/lib/yum-plugins/</filename>. The bytecode file uses the same name as the plugin, but has the extension <filename>.pyc</filename>. Remove the relevant configuration file in <filename>/etc/yum/pluginconf.d/</filename>."
msgstr ""
#: en_US/yum-software-management.xml:1745(para)
msgid "This command removes the plugin <filename>exampleplugin</filename>:"
msgstr "������ ��������������� <filename>exampleplugin</filename> ������������������ ��������� ������������������ ������:"
#: en_US/yum-software-management.xml:1750(userinput)
#, no-wrap
msgid "su -c 'rm -f /etc/yum/pluginconf.d/exampleplugin.conf; rm -f /usr/lib/yum-plugins/exampleplugin.py*'"
msgstr "su -c 'rm -f /etc/yum/pluginconf.d/exampleplugin.conf; rm -f /usr/lib/yum-plugins/exampleplugin.py*'"
#: en_US/yum-software-management.xml:1761(title)
msgid "Working with <command>yum</command> Caching"
msgstr "<command>yum</command> ��������������� ��������� ��������� ������������"
#: en_US/yum-software-management.xml:1763(primary) en_US/yum-software-management.xml:1767(secondary) en_US/yum-software-management.xml:1831(primary) en_US/yum-software-management.xml:1904(primary)
msgid "caching"
msgstr "���������������"
#: en_US/yum-software-management.xml:1769(para)
msgid "By default, current versions of <command>yum</command> delete the data files and packages that they download, after these have been successfully used for an operation. This minimizes the amount of storage space that <command>yum</command> uses. You may enable caching, so that <command>yum</command> retains the files that it downloads in cache directories."
msgstr ""
#: en_US/yum-software-management.xml:1778(para)
msgid "Caches provide three advantages:"
msgstr "��������������� ������ ������������ ��������������� ������:"
#: en_US/yum-software-management.xml:1785(para)
msgid "The performance of <command>yum</command> increases"
msgstr "<command>yum</command> ������ ������������������ ��������������� ������"
#: en_US/yum-software-management.xml:1790(para)
msgid "You may carry out <command>yum</command> operations without a network connection, by using only the caches"
msgstr "��������������� <command>yum</command> ������������������������ ��������� ��������������������� ������������������������ ��������� ���������������, ��������������� ��������������� ��������� ������ ������ ������������ ���������"
#: en_US/yum-software-management.xml:1796(para)
msgid "You may copy packages from the caches and reuse them elsewhere"
msgstr "��������������� ��������������� ��������� ��������������������� ������ ��������� ������ ������������ ������ ��������� ������������ ��������� ��������� ��������� ������������ ������"
#: en_US/yum-software-management.xml:1804(para)
msgid "By default, <command>yum</command> stores temporary files under the directory <filename>/var/cache/yum/</filename>, with one subdirectory for each configured repository. The <filename>packages/</filename> directory within each repository directory holds the cached packages. For example, the directory <filename>/var/cache/yum/development/packages/</filename> holds packages downloaded from the <filename>development</filename> repository."
msgstr ""
#: en_US/yum-software-management.xml:1815(title) en_US/yum-software-management.xml:1902(title)
msgid "Clearing the <command>yum</command> Caches"
msgstr "<command>yum</command> ��������������� ������������ ������������"
#: en_US/yum-software-management.xml:1816(para)
msgid "Cached files use disk space until removed. You may wish to periodically clear the <command>yum</command> caches to recover capacity. Refer to <xref linkend=\"sn-yum-clearance\"/> for information on clearing the caches."
msgstr ""
#: en_US/yum-software-management.xml:1823(para)
msgid "If you remove a package from the cache, you do not affect the copy of the software installed on your system."
msgstr "������������ ��������������� ��������������� ��������� ��������� ��������������� ��������� ��������������� ������ ��������� ��������������� ������������ ��������������� ������������ ������������������ ������������������������ ��������� ��������� ���������-��������� ������������ ������������ ���������"
#: en_US/yum-software-management.xml:1829(title)
msgid "Enabling the Caches"
msgstr "��������������� ��������� ������������"
#: en_US/yum-software-management.xml:1832(secondary)
msgid "enabling"
msgstr "��������� ������������"
#: en_US/yum-software-management.xml:1834(para)
msgid "To configure <command>yum</command> to retain downloaded files rather than discarding them, set the <command>keepcache</command> option in <filename>/etc/yum.conf</filename> to <userinput>1</userinput>:"
msgstr ""
#: en_US/yum-software-management.xml:1841(computeroutput)
#, no-wrap
msgid "\nkeepcache=1\n"
msgstr "\nkeepcache=1\n"
#: en_US/yum-software-management.xml:1845(para)
msgid "Refer to <xref linkend=\"sn-yum-configfiles\"/> for more information on editing the <command>yum</command> configuration file."
msgstr "<command>yum</command> ������������������ ������������ ������������ ��������� ��������� ������ <xref linkend=\"sn-yum-configfiles\"/> ��������� ���������������"
#: en_US/yum-software-management.xml:1851(para)
msgid "Once you enable caching, every <command>yum</command> operation may download package data from the configured repositories. To ensure that the caches have a set of package data, carry out an operation after you enable caching. Use a <option>list</option> or <option>search</option> query to download package data without modifying your system."
msgstr ""
#: en_US/yum-software-management.xml:1862(title)
msgid "Using <command>yum</command> in Cache-only Mode"
msgstr "���������������-��������������� ��������� ��������� ������ <command>yum</command> ������ ���������������"
#: en_US/yum-software-management.xml:1865(secondary)
msgid "cache-only mode"
msgstr "��������������� ��������������� ������ ���������"
#: en_US/yum-software-management.xml:1867(para)
msgid "To carry out a <command>yum</command> command without a network connection, add the <option>-C</option> option. This causes <command>yum</command> to proceed without checking any network repositories, and use only cached files. In this mode, <command>yum</command> may only install packages that have been downloaded and cached by a previous operation."
msgstr ""
#: en_US/yum-software-management.xml:1876(para)
msgid "To search for the package <filename>tsclient</filename> without using a network connection, enter the command:"
msgstr ""
#: en_US/yum-software-management.xml:1881(userinput)
#, no-wrap
msgid "su -c 'yum -C list <placeholder-1/>'"
msgstr "su -c 'yum -C list <placeholder-1/>'"
#: en_US/yum-software-management.xml:1890(title)
msgid "Cache-only Mode Requires Cached Data"
msgstr "���������������-��������������� ������ ��������� ������ ��������������� ������������ ������������ ������������������ ������"
#: en_US/yum-software-management.xml:1892(para)
msgid "Cache-only mode requires package data to exist in the caches. If you enable caching, every <command>yum</command> operation may update the data files, unless cache-only mode is specified for the operation."
msgstr ""
#: en_US/yum-software-management.xml:1905(secondary) en_US/yum-software-management.xml:1909(secondary)
msgid "cleaning caches"
msgstr "��������������� ������������ ������������"
#: en_US/yum-software-management.xml:1911(para)
msgid "If you configure it to do so, <command>yum</command> retains the packages and package data files that it downloads, so that they may be reused in future operations without being downloaded again. To purge the package data files, use this command:"
msgstr ""
#: en_US/yum-software-management.xml:1918(userinput)
#, no-wrap
msgid "su -c 'yum clean headers'"
msgstr "su -c 'yum clean headers'"
#: en_US/yum-software-management.xml:1920(para)
msgid "Run this command to remove all of the packages held in the caches:"
msgstr "������ ��������������� ��������������� ������������ ������ ��������������������� ��������� ��������������� ������ ���������������:"
#: en_US/yum-software-management.xml:1925(userinput)
#, no-wrap
msgid "su -c 'yum clean packages'"
msgstr "su -c 'yum clean packages'"
#: en_US/yum-software-management.xml:1927(para)
msgid "When using these commands, at the prompt, enter the password for the <systemitem class=\"username\">root</systemitem> account."
msgstr ""
#: en_US/yum-software-management.xml:1932(para)
msgid "Purging cached files causes those files to downloaded again the next time that they are required. This increases the amount of time required to complete the operation."
msgstr ""
#: en_US/yum-software-management.xml:1941(title)
msgid "Using <command>yum</command> with a Proxy Server"
msgstr "��������� ������������������ ������������ ��������� <command>yum</command> ������ ���������������"
#: en_US/yum-software-management.xml:1943(primary)
msgid "proxy server"
msgstr "������������������ ������������"
#: en_US/yum-software-management.xml:1947(secondary)
msgid "using with a proxy server"
msgstr "��������� ������������������ ������������ ���������"
#: en_US/yum-software-management.xml:1949(para)
msgid "By default, <command>yum</command> accesses network repositories with HTTP. All <command>yum</command> HTTP operations use HTTP/1.1, and are compatible with web proxy servers that support this standard. You may also access FTP repositories, and configure <command>yum</command> to use an FTP proxy server. The <filename>squid</filename> package provides a proxy service for both HTTP/1.1 and FTP connections."
msgstr ""
#: en_US/yum-software-management.xml:1959(title)
msgid "Modifying <command>yum</command> for Network Compatibility"
msgstr "��������������������� ������������������������ ������ <command>yum</command> ��������� ������������"
#: en_US/yum-software-management.xml:1960(para)
msgid "Refer to the <command>man</command> page for <filename>yum.conf</filename> for information on HTTP settings that may be modified for compatibility with nonstandard web proxy servers. Alternatively, configure <command>yum</command> to use an FTP proxy server, and access repositories that support FTP. The Fedora repositories support both HTTP and FTP."
msgstr ""
#: en_US/yum-software-management.xml:1970(title)
msgid "Configuring Proxy Server Access"
msgstr "������������������ ������������ ��������������� ������ ������������������ ������������"
#: en_US/yum-software-management.xml:1972(para)
msgid "To enable all <command>yum</command> operations to use a proxy server, specify the proxy server details in <filename>/etc/yum.conf</filename>. The <option>proxy</option> setting must specify the proxy server as a complete URL, including the TCP port number. If your proxy server requires a username and password, specify these by adding <option>proxy_username</option> and <option>proxy_password</option> settings."
msgstr ""
#: en_US/yum-software-management.xml:1983(para)
msgid "The settings below enable <command>yum</command> to use the proxy server <systemitem class=\"systemname\">mycache.mydomain.com</systemitem>, connecting to port 3128, with the username <systemitem class=\"username\">yum-user</systemitem> and the password <systemitem>qwerty</systemitem>."
msgstr ""
#: en_US/yum-software-management.xml:1995(title)
msgid "Configuration File Settings for Using A Proxy Server"
msgstr "��������� ������������������ ������������ ������ ��������������� ������������ ������������������ ������������ ���������������"
#: en_US/yum-software-management.xml:1997(computeroutput)
#, no-wrap
msgid "# The proxy server - proxy server:port number\nproxy=http://mycache.mydomain.com:3128\n# The account details for yum connections\nproxy_username=yum-user\nproxy_password=qwerty"
msgstr "# The proxy server - proxy server:port number\nproxy=http://mycache.mydomain.com:3128\n# The account details for yum connections\nproxy_username=yum-user\nproxy_password=qwerty"
#: en_US/yum-software-management.xml:2006(title)
msgid "Global Settings"
msgstr "��������������� ���������������"
#: en_US/yum-software-management.xml:2008(para)
msgid "If you define a proxy server in <filename>/etc/yum.conf</filename>, <emphasis>all</emphasis> users connect to the proxy server with those details when using <command>yum</command>."
msgstr ""
#: en_US/yum-software-management.xml:2018(title)
msgid "Configuring Proxy Server Access for a Single User"
msgstr "��������� ��������������� ������������������ ������ ������������������ ������������ ��������������� ������ ������������������ ������������"
#: en_US/yum-software-management.xml:2020(para)
msgid "To enable proxy access for a specific user, add the lines in the example box below to the user's shell profile. For the default <command>bash</command> shell, the profile is the file <filename>~/.bash_profile</filename>. The settings below enable <command>yum</command> to use the proxy server <systemitem class=\"systemname\">mycache.mydomain.com</systemitem>, connecting to port 3128."
msgstr ""
#: en_US/yum-software-management.xml:2032(title)
msgid "Profile Settings for Using a Proxy Server"
msgstr "��������� ������������������ ������������ ������ ��������������� ������������ ��������������������� ���������������"
#: en_US/yum-software-management.xml:2034(computeroutput)
#, no-wrap
msgid "# The Web proxy server used by this account\nhttp_proxy=\"http://mycache.mydomain.com:3128\"\nexport http_proxy"
msgstr "# The Web proxy server used by this account\nhttp_proxy=\"http://mycache.mydomain.com:3128\"\nexport http_proxy"
#: en_US/yum-software-management.xml:2040(para)
msgid "If the proxy server requires a username and password, add these to the URL. To include the username <systemitem class=\"username\">yum-user</systemitem> and the password <systemitem>qwerty</systemitem>, add these settings:"
msgstr ""
#: en_US/yum-software-management.xml:2048(title)
msgid "Profile Settings for a Secured Proxy Server"
msgstr "��������� ������������������������ ������������������ ������������ ������ ��������������������� ���������������"
#: en_US/yum-software-management.xml:2050(computeroutput)
#, no-wrap
msgid "# The Web proxy server, with the username and password for this account\nhttp_proxy=\"http://yum-user:qwerty@mycache.mydomain.com:3128\"\nexport http_proxy"
msgstr "# The Web proxy server, with the username and password for this account\nhttp_proxy=\"http://yum-user:qwerty@mycache.mydomain.com:3128\"\nexport http_proxy"
#: en_US/yum-software-management.xml:2057(title)
msgid "The <option>http_proxy</option> Environment Variable"
msgstr "<option>http_proxy</option> ��������������������� ������������"
#: en_US/yum-software-management.xml:2059(para)
msgid "The <command>http_proxy</command> environment variable is also used by <command>curl</command> and other utilities. Although <command>yum</command> itself may use <command>http_proxy</command> in either upper-case or lower-case, <command>curl</command> requires the name of the variable to be in lower-case."
msgstr ""
#: en_US/yum-software-management.xml:2074(title)
msgid "Acknowledgments"
msgstr "������������������ ��������������������� ������"
#: en_US/yum-software-management.xml:2076(para)
msgid "Paul Frields edited this document. Timothy Murphy reviewed the beta release."
msgstr "��������� ��������������� ������ ������ ������������������������ ��������������� ��������� ������������������ ��������������� ������ ������������ ������������������ ������ ������������ ������������ ���������"
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
#: en_US/yum-software-management.xml:0(None)
msgid "translator-credits"
msgstr ""
"��������������������� ������������ ���������\n"
"aalam(a)redhat.com"
18 years