From fedora-docs-commits at redhat.com Wed Mar 1 00:04:04 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 28 Feb 2006 19:04:04 -0500
Subject: release-notes/en Extras.xml,1.5,1.6 ProjectOverview.xml,1.4,1.5
Message-ID: <200603010004.k210447j012466@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/release-notes/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12426
Modified Files:
Extras.xml ProjectOverview.xml
Log Message:
Normalized titles for Fedora Foo sections at the end, went with Patrick's (n-man) cool suggestion ... Fedora Project - Freedom to the Core.
Index: Extras.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Extras.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Extras.xml 28 Feb 2006 22:38:45 -0000 1.5
+++ Extras.xml 1 Mar 2006 00:03:40 -0000 1.6
@@ -5,7 +5,7 @@
Temp
- Fedora Extras
+ Fedora Extras - Community Package RepositoryUsing the RepositoryFedora Extras provides a repository of packages that complement Fedora Core. This volunteer-based community effort is part of the larger Fedora Project.
Index: ProjectOverview.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ProjectOverview.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- ProjectOverview.xml 28 Feb 2006 21:45:48 -0000 1.4
+++ ProjectOverview.xml 1 Mar 2006 00:03:40 -0000 1.5
@@ -5,7 +5,7 @@
Temp
- An Overview of the Fedora Project
+ Fedora Project - Freedom to the CoreThe goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from open source software. Development is done in a public forum. The project produces time-based releases of Fedora Core approximately 2-3 times a year, with a public release schedule available at http://fedora.redhat.com/About/schedule/. The Red Hat engineering team continues to participate in building Fedora Core and invites and encourages more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community. For more information, refer to the Fedora Project website:
From fedora-docs-commits at redhat.com Wed Mar 1 00:11:19 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 28 Feb 2006 19:11:19 -0500
Subject: docs-common Makefile.common,1.79,1.80
Message-ID: <200603010011.k210BJoZ012707@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12688
Modified Files:
Makefile.common
Log Message:
Set proper locale before validating XML. Do a more thourough job
of cleaning up after ourselves.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- Makefile.common 28 Feb 2006 21:52:01 -0000 1.79
+++ Makefile.common 1 Mar 2006 00:11:09 -0000 1.80
@@ -256,6 +256,7 @@
.PHONY: html-nochunks-${1}
html-nochunks-$(1):: ${DOCBASE}-$(1).html
+
${DOCBASE}-$(1).html:: ${XMLFILES-${1}} $(1)/fdp-info.xml set-locale-${1}
LANG=${1}.UTF-8 ${XMLTO} html-nochunks -x $(XSLHTMLNOCHUNKS) $(1)/$(DOCBASE).xml
mv $(DOCBASE).html $(DOCBASE)-$(1).html
@@ -315,8 +316,10 @@
.PHONY: pdf-${1}
pdf-$(1):: ${DOCBASE}-$(1).pdf
+
${DOCBASE}-$(1).pdf:: ${XMLFILES-${1}} ${1}/fdp-info.xml set-locale-${1}
- LANG=${1}.UTF-8 ${XMLTO} pdf -x $(XSLPDF) $(1)/$(DOCBASE)-$(1).xml
+ LANG=${1}.UTF-8 ${XMLTO} pdf -x $(XSLPDF) $(1)/$(DOCBASE).xml
+ mv -f ${DOCBASE}.pdf ${DOCBASE}-${1}.pdf
distclean::
${RM} ${DOCBASE}-${1}.pdf
@@ -338,6 +341,7 @@
.PHONY: txt-${1} text-${1}
txt-$(1) text-$(1):: ${DOCBASE}-$(1).txt
+
${DOCBASE}-$(1).txt:: ${XMLFILES-${1}} ${1}/fdp-info.xml set-locale-${1}
${XMLLINT} ${XMLLINTOPT} $(1)/$(DOCBASE).xml > $(1)/$(DOCBASE).lint.xml
${XSLTPROC} $(FDPDIR)/docs-common/packaging/strip-for-txt.xsl \
@@ -347,6 +351,9 @@
mv $(DOCBASE).stripped.txt $(DOCBASE)-$(1).txt
rm $(1)/$(DOCBASE).stripped.xml
+clean::
+ ${RM} ${1}/${DOCBASE}.stripped.xml
+
distclean::
${RM} ${DOCBASE}-${1}.txt
@@ -465,6 +472,9 @@
@printf ${TFMT} 'po-${1}' 'Creates or updates locale ${1} .PO file'
@printf ${TFMT} 'po/${1}.po' 'Creates or updates locale ${1} .PO file'
+clean::
+ ${RM} .xml2po.mo
+
endef
$(foreach L,${OTHERS},$(eval $(call PO_template,${L})))
@@ -754,6 +764,7 @@
LOCALE_ENTITIES='locale-entities.xml'
define LOCALE_template
.PHONY: set-locale-${1}
+
set-locale-${1}::
${LN} -f -s ${FDPDIR}/docs-common/common/entities/entities-${1}.ent \
${LOCALE_ENTITIES}
@@ -774,9 +785,10 @@
# 'VALIDATE_template' emits rules and targets to validate the XML for the
# specified ${LANG}
define VALIDATE_template
+
.PHONY: validate-xml-${1}
-validate-xml-${1}: ${XMLFILES-${1}} ${1}/fdp-info.xml
+validate-xml-${1}:: ${XMLFILES-${1}} ${1}/fdp-info.xml set-locale-${1}
${XMLLINT} --noout --xinclude --postvalid ${1}/${DOCBASE}.xml
help::
From fedora-docs-commits at redhat.com Wed Mar 1 00:33:44 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 28 Feb 2006 19:33:44 -0500
Subject: release-notes/en OverView.xml,1.5,1.6
Message-ID: <200603010033.k210XirO013156@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/release-notes/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13132
Modified Files:
OverView.xml
Log Message:
Capturing some worthwhile language changes at the last minute from Dave Jones.
Index: OverView.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/OverView.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- OverView.xml 28 Feb 2006 21:45:48 -0000 1.5
+++ OverView.xml 1 Mar 2006 00:33:21 -0000 1.6
@@ -30,7 +30,7 @@
The new GNOME User Share facility provides simple and efficient file sharing.
- Software suspend (hibernate) capability is now provided for a wide variety of hardware.
+ Suspend to RAM support has also been improved due to infrastructure work done by the hibernate support. The previous graphical software management utilities have been replaced with the first versions of a new generation of tools. This release includes Pup, a simple interface for system updates, and Pirut, a new package manager that replaces system-config-packages. These build on the yum utility, to provide consistent software installation and update facilities throughout the system.
@@ -54,7 +54,7 @@
A large number of GTK and GNOME programs take advantage of the Cairo 2D graphics library (http://cairographics.org/), included in this release, to provide streamlined attractive graphical interfaces.
- There are new drivers that provide support for the widely-used Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/).
+ There are new experimental drivers that provide support for the widely-used Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/). This release includes libnotify, a library that features simple and attractive notifications for the desktop.
From fedora-docs-commits at redhat.com Wed Mar 1 00:41:04 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 28 Feb 2006 19:41:04 -0500
Subject: release-notes rpm-info.xml,1.7,1.8
Message-ID: <200603010041.k210f4QI013466@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13448
Modified Files:
rpm-info.xml
Log Message:
Copyright holder now matches the legal notice.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/release-notes/rpm-info.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- rpm-info.xml 28 Feb 2006 23:32:20 -0000 1.7
+++ rpm-info.xml 1 Mar 2006 00:40:57 -0000 1.8
@@ -18,7 +18,7 @@
2006
- Red Hat, Inc.
+ Fedora Foundation and others.
From fedora-docs-commits at redhat.com Wed Mar 1 00:48:53 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 28 Feb 2006 19:48:53 -0500
Subject: release-notes rpm-info.xml,1.8,1.9
Message-ID: <200603010048.k210mrV8013790@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13772
Modified Files:
rpm-info.xml
Log Message:
Extraneous periods == evil
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/release-notes/rpm-info.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- rpm-info.xml 1 Mar 2006 00:40:57 -0000 1.8
+++ rpm-info.xml 1 Mar 2006 00:48:46 -0000 1.9
@@ -18,7 +18,7 @@
2006
- Fedora Foundation and others.
+ Fedora Foundation and others
From fedora-docs-commits at redhat.com Wed Mar 1 01:14:08 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 28 Feb 2006 20:14:08 -0500
Subject: docs-common/common/entities entities-en.ent, 1.2,
1.3 entities-en.xml, 1.6, 1.7 entities-it.ent, 1.8,
1.9 entities-it.xml, 1.7, 1.8 entities-pt_BR.ent, 1.2,
1.3 entities-pt_BR.xml, 1.1, 1.2 entities-ru.ent, 1.2,
1.3 entities-ru.xml, 1.1, 1.2 entities-zh_CN.ent, 1.2,
1.3 entities-zh_CN.xml, 1.1, 1.2 it.po, 1.7, 1.8 pt_BR.po, 1.1,
1.2 ru.po, 1.1, 1.2 zh_CN.po, 1.1, 1.2
Message-ID: <200603010114.k211E832016417@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/common/entities
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16383
Modified Files:
entities-en.ent entities-en.xml entities-it.ent
entities-it.xml entities-pt_BR.ent entities-pt_BR.xml
entities-ru.ent entities-ru.xml entities-zh_CN.ent
entities-zh_CN.xml it.po pt_BR.po ru.po zh_CN.po
Log Message:
Fix a typo and add a missing FP-URL entity
Index: entities-en.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-en.ent,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities-en.ent 28 Feb 2006 04:21:26 -0000 1.2
+++ entities-en.ent 1 Mar 2006 01:14:00 -0000 1.3
@@ -20,7 +20,8 @@
" >
- " >
+ " >
+ " >
" >
Index: entities-en.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-en.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- entities-en.xml 28 Feb 2006 02:06:58 -0000 1.6
+++ entities-en.xml 1 Mar 2006 01:14:00 -0000 1.7
@@ -54,7 +54,11 @@
Fedora Docs Project URL
-
+
+ Fedora Project URL
+
+
+ Fedora Documentation (repository) URL
Index: entities-it.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-it.ent,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- entities-it.ent 28 Feb 2006 04:21:26 -0000 1.8
+++ entities-it.ent 1 Mar 2006 01:14:00 -0000 1.9
@@ -15,7 +15,8 @@
" >
- " >
+ " >
+ " >
" >
Index: entities-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-it.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- entities-it.xml 28 Feb 2006 04:11:39 -0000 1.7
+++ entities-it.xml 1 Mar 2006 01:14:00 -0000 1.8
@@ -47,7 +47,11 @@
Fedora Docs Project URL
-
+
+ Fedora Project URL
+
+
+ Fedora Documentation (repository) URL
Index: entities-pt_BR.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-pt_BR.ent,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities-pt_BR.ent 28 Feb 2006 04:21:26 -0000 1.2
+++ entities-pt_BR.ent 1 Mar 2006 01:14:00 -0000 1.3
@@ -15,7 +15,8 @@
" >
- " >
+ " >
+ " >
" >
Index: entities-pt_BR.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-pt_BR.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entities-pt_BR.xml 28 Feb 2006 04:11:40 -0000 1.1
+++ entities-pt_BR.xml 1 Mar 2006 01:14:00 -0000 1.2
@@ -47,7 +47,11 @@
Fedora Docs Project URL
-
+
+ Fedora Project URL
+
+
+ Fedora Documentation (repository) URL
Index: entities-ru.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-ru.ent,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities-ru.ent 28 Feb 2006 04:21:26 -0000 1.2
+++ entities-ru.ent 1 Mar 2006 01:14:00 -0000 1.3
@@ -15,7 +15,8 @@
" >
- " >
+ " >
+ " >
" >
Index: entities-ru.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-ru.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entities-ru.xml 28 Feb 2006 04:11:40 -0000 1.1
+++ entities-ru.xml 1 Mar 2006 01:14:00 -0000 1.2
@@ -47,7 +47,11 @@
Fedora Docs Project URL
-
+
+ Fedora Project URL
+
+
+ Fedora Documentation (repository) URL
Index: entities-zh_CN.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-zh_CN.ent,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities-zh_CN.ent 28 Feb 2006 04:21:26 -0000 1.2
+++ entities-zh_CN.ent 1 Mar 2006 01:14:00 -0000 1.3
@@ -15,7 +15,8 @@
" >
- " >
+ " >
+ " >
" >
Index: entities-zh_CN.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-zh_CN.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entities-zh_CN.xml 28 Feb 2006 04:11:40 -0000 1.1
+++ entities-zh_CN.xml 1 Mar 2006 01:14:00 -0000 1.2
@@ -47,7 +47,11 @@
Fedora Docs Project URL
-
+
+ Fedora Project URL
+
+
+ Fedora Documentation (repository) URL
Index: it.po
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/it.po,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- it.po 28 Feb 2006 04:11:40 -0000 1.7
+++ it.po 1 Mar 2006 01:14:00 -0000 1.8
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-02-27 22:09-0600\n"
+"POT-Creation-Date: 2006-02-28 20:10-0500\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
@@ -9,220 +9,226 @@
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: entities-en.xml:6(title)
-msgid "These common entities are useful shorthand terms and names, which may be subject to change at anytime. This is an important value the the entity provides: a single location to update terms and common names."
+#: entities-en.xml:6(title)
+msgid ""
+"These common entities are useful shorthand terms and names, which may be "
+"subject to change at anytime. This is an important value the the entity "
+"provides: a single location to update terms and common names."
msgstr ""
-#: entities-en.xml:14(comment) entities-en.xml:18(comment)
+#: entities-en.xml:14(comment) entities-en.xml:18(comment)
msgid "Generic root term"
msgstr ""
-#: entities-en.xml:15(text)
+#: entities-en.xml:15(text)
msgid "Fedora"
msgstr ""
-#: entities-en.xml:19(text)
+#: entities-en.xml:19(text)
msgid "Core"
msgstr ""
-#: entities-en.xml:22(comment)
+#: entities-en.xml:22(comment)
msgid "Generic main project name"
msgstr ""
-#: entities-en.xml:26(comment)
+#: entities-en.xml:26(comment)
msgid "Legacy Entity"
msgstr ""
-#: entities-en.xml:30(comment)
+#: entities-en.xml:30(comment)
msgid "Short project name"
msgstr ""
-#: entities-en.xml:31(text)
+#: entities-en.xml:31(text)
msgid "FC"
msgstr ""
-#: entities-en.xml:34(comment)
+#: entities-en.xml:34(comment)
msgid "Generic overall project name"
msgstr ""
-#: entities-en.xml:35(text)
+#: entities-en.xml:35(text)
msgid "
+
+
+ Virtualization (Xen)
+
+
+ This option provides the services and utilities to simultaneously run multiple operating systems on your computer.
+
+
+
+
Select Customize now to specify the software
@@ -114,17 +129,22 @@
printing through CUPS (Common UNIX Printing System)
+
+
+ remote desktop access through VNC (Virtual Network Computing)
+
+
Some automated processes on your Fedora system use the email
service to send reports and messages to the system administrator.
By default, the email, logging, and printing services do not
- accept connections from other systems. Although Fedora connects to
- NFS services on other systems, the NFS sharing component is
- disabled by default. You may configure your Fedora system after
- installation to offer email, logging, NFS, or print services. The
- SSH service is enabled by default.
+ accept connections from other systems. &FED; installs the NFS sharing and VNC components without enabling those services.
+
+
+
+ You may configure your Fedora system after installation to offer email, file sharing, logging, printing and remote desktop access services. The SSH service is enabled by default. You may use NFS to access files on other systems without enabling the NFS sharing service.
Index: fedora-install-guide-rootpassword.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-rootpassword.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-rootpassword.xml 24 Feb 2006 14:22:16 -0000 1.4
+++ fedora-install-guide-rootpassword.xml 1 Mar 2006 01:43:14 -0000 1.5
@@ -1,6 +1,11 @@
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+
+%FEDORA-ENTITIES;
+
+]>
Index: fedora-install-guide-techref.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-techref.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-techref.xml 24 Feb 2006 14:22:16 -0000 1.4
+++ fedora-install-guide-techref.xml 1 Mar 2006 01:43:14 -0000 1.5
@@ -1,11 +1,16 @@
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+
+%FEDORA-ENTITIES;
+
+]>
- Technical References
+ Other Technical Documentation
This document provides a reference for using the &FC; installation
software, known as anaconda. To learn more about
@@ -49,6 +54,21 @@
+ Storage Management
+
+
+
+ LVM
+ documentation
+
+Logical Volume Management (LVM) provides administrators with a range of facilities to manage storage. By default, the &FED; installation process formats drives as LVM volumes. Refer
+ to for more
+ information.
+
+
+
+
+ Audio Support
@@ -192,6 +212,21 @@
+
+
+ Virtualization
+
+
+
+ Xen
+ documentation
+
+ Xen provides the capability to simultaneously run multiple operating systems on the same computer. &FC; also includes tools to install and manage the secondary systems on a &FED; host. You may select Xen support during the installation process, or at any time thereafter. Refer to
+ for more
+ information.
+
+
+
Index: fedora-install-guide-timezone.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-timezone.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-timezone.xml 24 Feb 2006 14:22:16 -0000 1.4
+++ fedora-install-guide-timezone.xml 1 Mar 2006 01:43:14 -0000 1.5
@@ -1,6 +1,11 @@
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+
+%FEDORA-ENTITIES;
+
+]>
Index: fedora-install-guide-upgrading.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-upgrading.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide-upgrading.xml 24 Feb 2006 14:22:16 -0000 1.4
+++ fedora-install-guide-upgrading.xml 1 Mar 2006 01:43:14 -0000 1.5
@@ -1,6 +1,11 @@
+ "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+
+
+%FEDORA-ENTITIES;
+
+]>
Index: fedora-install-guide.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fedora-install-guide.xml 24 Feb 2006 14:22:16 -0000 1.4
+++ fedora-install-guide.xml 1 Mar 2006 01:43:14 -0000 1.5
@@ -1,20 +1,21 @@
-
-%FEDORA-ENTITIES-EN;
+
+%FEDORA-ENTITIES;
-
-
+
+
-
+
]>
From fedora-docs-commits at redhat.com Wed Mar 1 01:43:15 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Tue, 28 Feb 2006 20:43:15 -0500
Subject: install-guide rpm-info.xml,1.10,1.11
Message-ID: <200603010143.k211hk0b017295@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17221
Modified Files:
rpm-info.xml
Log Message:
- Updated files with entity declarations to work with XIncludes.
- Added Xen material for test3.
- Added LVM reference.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- rpm-info.xml 17 Feb 2006 19:07:00 -0000 1.10
+++ rpm-info.xml 1 Mar 2006 01:43:08 -0000 1.11
@@ -12,7 +12,7 @@
- GNU FDL
+ OPL1.0
@@ -28,10 +28,15 @@
+
+
+
+ Added Xen material.
+
- Updated First Boot.
+ Updated First Boot.
From fedora-docs-commits at redhat.com Wed Mar 1 12:03:11 2006
From: fedora-docs-commits at redhat.com (Amanpreet Singh Brar (apbrar))
Date: Wed, 1 Mar 2006 07:03:11 -0500
Subject: release-notes/po pa.po,1.1,1.2
Message-ID: <200603011203.k21C3BtS011306@cvs-int.fedora.redhat.com>
Author: apbrar
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11288
Modified Files:
pa.po
Log Message:
update for Punjabi file
Index: pa.po
===================================================================
RCS file: /cvs/docs/release-notes/po/pa.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pa.po 28 Feb 2006 14:18:36 -0000 1.1
+++ pa.po 1 Mar 2006 12:03:01 -0000 1.2
@@ -1,10 +1,10 @@
-# translation of RELEASE-NOTES.po to Punjabi
+# translation of pa.po to Punjabi
# Amanpreet Singh Alam , 2006.
msgid ""
msgstr ""
-"Project-Id-Version: RELEASE-NOTES\n"
+"Project-Id-Version: pa\n"
"POT-Creation-Date: 2006-02-22 05:54-0600\n"
-"PO-Revision-Date: 2006-02-28 19:10+0530\n"
+"PO-Revision-Date: 2006-03-01 17:30+0530\n"
"Last-Translator: Amanpreet Singh Alam \n"
"Language-Team: Punjabi \n"
"MIME-Version: 1.0\n"
@@ -427,7 +427,7 @@
#: en/SecuritySELinux.xml:63(title)
msgid "Multi Category Security (MCS)"
-msgstr ""
+msgstr "?????????-????????? ????????????????????? (MCS)"
#: en/SecuritySELinux.xml:64(para)
msgid "General use implementation of the more stringent Multilevel Security (MLS). MCS is an enhancement to SELinux to allow users to label files with categories. For example, Company_Confidential, CEO_EYES_ONLY, or Sysadmin_Passwords."
@@ -443,7 +443,7 @@
#: en/SecuritySELinux.xml:70(title)
msgid "Multilevel Security (MLS)"
-msgstr ""
+msgstr "?????????-??????????????? ????????????????????? (MLS)"
#: en/SecuritySELinux.xml:71(para)
msgid "A specific Mandatory Access Control (MAC) scheme that labels processes and objects with special security levels. For example, an object (a document file) can have the security level of { Secret, ProjectMeta }, where Secret is the sensitivity level, and the ProjectMeta is the category."
@@ -463,7 +463,7 @@
#: en/Security.xml:9(para)
msgid "This section highlights various security items from Fedora Core."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????????????????? ????????? ????????? ????????????????????? ?????????????????? ???????????? ????????????????????? ?????????"
#: en/Security.xml:11(title)
msgid "General Information"
@@ -483,11 +483,11 @@
#: en/Security.xml:20(title)
msgid "PAM Module Deprecation"
-msgstr ""
+msgstr "PAM ?????????????????? ??????????????????"
#: en/Security.xml:21(para)
msgid "Pam_stack is deprecated in this release."
-msgstr ""
+msgstr "?????? ???????????? ???????????? Pam_stack ????????? ?????????????????? ?????? ??????????????? ????????? ?????????"
#: en/Security.xml:23(para)
msgid "Linux-PAM 0.78 and later contains the include directive which obsoletes the pam_stack module. pam_stack module usage is logged with a deprecation warning. It might be removed in a future release. It must not be used in individual service configurations anymore. All packages in Fedora Core using PAM were modified so they do not use it."
@@ -582,11 +582,11 @@
#: en/ProjectOverview.xml:27(para)
msgid "fedora-devel-list at redhat.com - For developers, developers, developers"
-msgstr ""
+msgstr "fedora-devel-list at redhat.com - ?????????????????? ??????, ????????????"
#: en/ProjectOverview.xml:31(para)
msgid "fedora-docs-list at redhat.com - For participants of the Documentation Project"
-msgstr ""
+msgstr "fedora-docs-list at redhat.com - ???????????????????????? ???????????????????????? ???????????? ????????? ????????? ??????"
#: en/ProjectOverview.xml:35(para)
msgid "To subscribe to any of these lists, send an email with the word \"subscribe\" in the subject to <listname>-request (where <listname> is one of the above list names.)"
@@ -618,7 +618,7 @@
#: en/ProjectOverview.xml:45(para)
msgid "Red Hat has no control over the Fedora Project IRC channels or their content."
-msgstr ""
+msgstr "?????????????????? ???????????????????????? IRC ?????????????????? ????????? ??????????????? ?????? ????????????????????? ???????????? Red Hat ?????? ?????????????????? ???????????? ?????????"
#: en/Printing.xml:8(title)
msgid "Printing"
@@ -671,11 +671,11 @@
#: en/PackageNotesJava.xml:26(title)
msgid "Include Complete Information in Bug Reports"
-msgstr ""
+msgstr "????????? ???????????????????????? ???????????? ???????????? ????????????????????? ?????????"
#: en/PackageNotesJava.xml:27(para)
msgid "When making a bug report, be sure to include the output from these commands:"
-msgstr ""
+msgstr "???????????? ?????? ????????? ????????????????????? ??????????????? ???????????? ????????? ??????????????? ????????????????????? ?????? ????????????????????? ??????????????? ????????????:"
#: en/PackageNotesJava.xml:32(computeroutput)
#, no-wrap
@@ -696,7 +696,7 @@
#: en/PackageNotes.xml:12(para)
msgid "This section contains information related to basic system components."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????????????????? ??????????????? ??????????????? ???????????? ????????????????????? ??????????????? ?????? ?????????"
#: en/PackageNotes.xml:14(title)
msgid "Mouse Configuration Utility Removed"
@@ -712,7 +712,7 @@
#: en/PackageNotes.xml:19(para)
msgid "Screensavers not installed by default anymore? Explain why and provide commands to install them."
-msgstr ""
+msgstr "???????????????-???????????? ????????? ????????? ???????????? ????????? ?????????????????? ???????????? ???????????????? ????????????????????? ????????? ?????????????????? ????????? ???????????? ????????????????????? ?????????"
#: en/PackageNotes.xml:22(title)
msgid "NetworkManager"
@@ -720,11 +720,11 @@
#: en/PackageNotes.xml:23(para)
msgid "Because it is not possible to test NetworkManager in all configurations, it is not enabled by default in Fedora Core ."
-msgstr ""
+msgstr "?????????????????? NetworkManager ????????? ?????? ??????????????????????????? ????????? ?????????????????? ???????????? ???????????? ??????, ?????? ???????????? ?????? ????????? ????????? ????????? ???????????? ?????????????????? ????????? ???????????? ????????? ???????????? ???????????? ????????? ?????????"
#: en/PackageNotes.xml:24(para)
msgid "Refer to this page for information about enabling this application:"
-msgstr ""
+msgstr "?????? ???????????? ????????? ????????? ????????? ???????????? ????????????????????? ???????????? ?????? ?????? ???????????? ????????????:"
#: en/PackageNotes.xml:26(ulink)
msgid "http://fedoraproject.org/wiki/Tools/NetworkManager"
@@ -744,7 +744,7 @@
#: en/PackageChanges.xml:10(title)
msgid "LinuxThreads library is no longer available"
-msgstr ""
+msgstr "LinuxThreads ???????????????????????? ????????? ?????????????????? ???????????? ??????"
#: en/PackageChanges.xml:11(para)
msgid "LinuxThreads was been deprecated in Fedora Core 4 and is no longer available in this release. NPTL, which has been the default threading library since Red Hat Linux 9, has replaced this completely."
@@ -756,7 +756,7 @@
#: en/OverView.xml:9(para)
msgid "Welcome to Fedora. In this new exciting new release, we present you a sneak preview of Fedora Core 5 filled with pictures and videos available at http://fedoraproject.org/wiki/Tours/FedoraCore5."
-msgstr ""
+msgstr "?????????????????? ???????????? ?????? ???????????? ???????????? ?????? ?????????-????????????????????? ???????????? ???????????? ???????????? ???????????? ????????????????????? ?????????????????? ????????? 5 ???????????? ????????????????????? ????????? ??????????????? http://fedoraproject.org/wiki/Tours/FedoraCore5 ???????????? ?????????????????? ???????????? ????????? ????????????"
#: en/OverView.xml:11(title)
msgid "What Has Changed Since Fedora Core 4"
@@ -784,15 +784,15 @@
#: en/OverView.xml:27(para)
msgid "GNOME Power Manager and GNOME Screensaver are available as a technology preview within this release."
-msgstr ""
+msgstr "???????????? ???????????? ?????????????????? ????????? ???????????? ???????????????-???????????? ????????? ?????? ???????????? ???????????? ???????????? ???????????????????????? ????????? ???????????? ?????????????????? ?????????"
#: en/OverView.xml:30(para)
msgid "OpenOffice.org 2.0 (http://www.openoffice.org/product/index.html/) release is included. OpenOffice.org now uses system versions for many of the libraries leading to increased performance and efficiency."
-msgstr ""
+msgstr "OpenOffice.org 2.0 (http://www.openoffice.org/product/index.html/) ?????? ???????????? ????????? ?????????????????? ???????????? ????????? ????????? OpenOffice.org ???????????? ?????? ?????????????????????????????? ?????? ??????????????? ?????????????????? ???????????? ??????, ????????? ????????? ?????????????????? ???????????? ???????????? ??????????????? ???????????? ?????????"
#: en/OverView.xml:33(para)
msgid "Firefox 1.5(http://www.mozilla.com/firefox/releases/1.5.html) web browser with many new features is included in this release"
-msgstr ""
+msgstr "???????????????????????? 1.5(http://www.mozilla.com/firefox/releases/1.5.html) ???????????? ?????????????????? ???????????? ?????? ???????????? ??????????????? ?????? ???????????? ???????????? ???????????? ?????? ?????????"
#: en/OverView.xml:36(para)
msgid "Pup, the package updater has been joined by Pirut, which is the replacement for system-config-packages providing comprehensive software package management using yum as a backend."
@@ -808,7 +808,7 @@
#: en/OverView.xml:45(para)
msgid "I18N support has drastically improved through the use of SCIM language input framework which has replaced IIMF in this release"
-msgstr ""
+msgstr "I18N ??????????????? ????????? ?????? ???????????? ???????????? IIIMF ?????? ???????????? SCIM ??????????????? ?????????????????? ????????????????????? ??????????????? ????????? ?????? ???????????? ???????????? ???????????? ????????????????????? ????????? ??????"
#: en/OverView.xml:48(para)
msgid "Gstreamer media framework 0.10 which brings major improvements in robustness and features has been included in this release. Totem uses this new version of Gstreamer now. Other media applications that use gstreamer is expected to be updated within the subsequent releases."
@@ -848,7 +848,7 @@
#: en/OverView.xml:82(title)
msgid "Road Map"
-msgstr ""
+msgstr "????????????"
#: en/OverView.xml:83(para)
msgid "The proposed plans for Fedora in this version are available from http://fedoraproject.org/wiki/RoadMap."
@@ -856,15 +856,15 @@
#: en/Networking.xml:8(title)
msgid "Networking"
-msgstr ""
+msgstr "?????????????????????????????????"
#: en/Networking.xml:10(title)
msgid "Major Kernel Changes 2.6.11 - 2.6.14"
-msgstr ""
+msgstr "???????????? ???????????? ???????????????????????? 2.6.11 - 2.6.14"
#: en/Networking.xml:12(title)
msgid "IPv4 Address Promotion"
-msgstr ""
+msgstr "IPv4 ???????????????????????? ???????????????"
#: en/Networking.xml:13(para)
msgid "Starting with version 2.6.12 of the kernel a new feature has been added called named address promotion. It allows secondary IPv4 addresses to be promoted to primary addresses. Usually when the primary address is deleted, all secondary addresses are deleted as well. By enabling the new sysctl net.ipv4.conf.all.promote_secondaries (or one of the interface specific variants) this behaviour can be changed to promote one of the secondary addresses to be the new primary address."
@@ -872,7 +872,7 @@
#: en/Networking.xml:16(title)
msgid "Configurable Source Address for ICMP Errors"
-msgstr ""
+msgstr "ICMP ?????????????????? ?????? ??????????????????????????? ???????????? ????????????????????????"
#: en/Networking.xml:17(para)
msgid "The current behaviour when selecting the source address for ICMP error messages is to use the address of the interface the ICMP error is going to be sent out. Kernel version 2.6.12 introduces a new sysctl net.ipv4.icmp_errors_use_inbound_ifaddr that allows changing this behaviour to use the address of the interface that received the original error-causing packet."
@@ -896,7 +896,7 @@
#: en/Networking.xml:26(title)
msgid "Pluggable Congestion Control Algorithm Infrastructure"
-msgstr ""
+msgstr "????????????-???-??????"
#: en/Networking.xml:27(para)
msgid "TCP congestion control algorithms are now pluggable and thus modular. The legacy NewReno algorithm stays default and acts as the fallback algorithm. The following new congestion control algorithms have been added:"
@@ -912,11 +912,11 @@
#: en/Networking.xml:36(para)
msgid "H-TCP congestion control."
-msgstr ""
+msgstr "H-TCP ???????????????????????? ?????????????????? ?????????"
#: en/Networking.xml:39(para)
msgid "Scalable TCP congestion control."
-msgstr ""
+msgstr "????????????????????? TCP ???????????????????????? ?????????????????? ?????????"
#: en/Networking.xml:42(para)
msgid "All existing congestion control modules have been converted to this new infrastructure and the BIC congestion control has received enhancements from BICTCP 1.1 to handle low latency links."
@@ -924,7 +924,7 @@
#: en/Networking.xml:44(title)
msgid "Affecting the Congestion Control Algorithm"
-msgstr ""
+msgstr "???????????????????????? ?????????????????? ???????????????????????? ?????? ???????????????"
#: en/Networking.xml:46(para)
msgid "An interesting addition for developers is that the congestion control algorithm is socket specific and can be changed via the socket option TCP_CONGESTION."
@@ -940,7 +940,7 @@
#: en/Networking.xml:54(title)
msgid "DCCP Protocol Support"
-msgstr ""
+msgstr "DCCP ???????????????????????? ??????????????????"
#: en/Networking.xml:55(para)
msgid "Kernel version 2.6.14-rc1 was the first version to receive support for the DCCP protocol. The implementation is still experimental but known to work. Work has begun to make userspace applications aware of this new protocol."
@@ -948,7 +948,7 @@
#: en/Networking.xml:58(title)
msgid "Wireless"
-msgstr ""
+msgstr "???????????????"
#: en/Networking.xml:59(para)
msgid "A new driver named HostAP has been added to 2.6.14-rc1 allowing the emulation of a wireless access point in software. Currently this driver only works for Intersil Prism2-based cards (PC Card/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been added."
@@ -956,7 +956,7 @@
#: en/Networking.xml:62(title)
msgid "Miscellaneous"
-msgstr ""
+msgstr "???????????????"
#: en/Networking.xml:65(para)
msgid "A lot of TCP Segmentation Offloading (TSO) related fixes have been included."
@@ -980,7 +980,7 @@
#: en/Networking.xml:83(title)
msgid "Userspace Tools"
-msgstr ""
+msgstr "????????????-???????????? ?????????"
#: en/Networking.xml:84(para)
msgid "The IPv4 address deletion algorithm did not take the prefix length into account up to kernel version 2.6.12. Since this has changed, the iproute2 tool now issues a warning if no prefix length is provided to warn about possible unintended deletions:"
@@ -989,17 +989,17 @@
#: en/Networking.xml:86(userinput)
#, no-wrap
msgid "ip addr list dev eth0"
-msgstr ""
+msgstr "ip addr list dev eth0"
#: en/Networking.xml:87(computeroutput)
#, no-wrap
msgid "4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000\ninet 10.0.0.3/24 scope global eth0"
-msgstr ""
+msgstr "4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000\ninet 10.0.0.3/24 scope global eth0"
#: en/Networking.xml:89(userinput)
#, no-wrap
msgid "su -c 'ip addr del 10.0.0.3 dev eth0'"
-msgstr ""
+msgstr "su -c 'ip addr del 10.0.0.3 dev eth0'"
#: en/Networking.xml:90(computeroutput)
#, no-wrap
@@ -1008,12 +1008,12 @@
#: en/Networking.xml:95(para)
msgid "The correct method of deleting the address and thus avoiding the warning is:"
-msgstr ""
+msgstr "???????????????????????? ??????????????? ?????? ????????? ????????? ?????? ????????? ????????? ?????? ????????????????????? ????????? ????????? ??????:"
#: en/Networking.xml:96(screen)
#, no-wrap
msgid "su -c 'ip addr del 10.0.0.3/24 dev eth0'"
-msgstr ""
+msgstr "su -c 'ip addr del 10.0.0.3/24 dev eth0'"
#: en/Networking.xml:97(para)
msgid "Previously, it has not been possible to tell if an interface is down administratively or because no carrier can be found (cable unplugged). The flag NO-CARRIER has been introduced that shows up as a link flag if the link is administratively up but no carrier can be found."
@@ -1025,7 +1025,7 @@
#: en/Multimedia.xml:8(title)
msgid "Multimedia"
-msgstr ""
+msgstr "??????????????????"
#: en/Multimedia.xml:9(para)
msgid "Fedora Core includes applications for assorted multimedia functions, including playback, recording and editing. Additional packages are available through the Fedora Extras repository."
@@ -1033,7 +1033,7 @@
#: en/Multimedia.xml:11(title)
msgid "Multimedia Players"
-msgstr ""
+msgstr "?????????-????????? ???????????????"
#: en/Multimedia.xml:12(para)
msgid "By default, Fedora Core installs with Rhythm Box, Totem, and Helix Player for media playback. In addition, many other programs are available in the Fedora Core and Fedora Extras repositories, including the popular XMMS package. Both GNOME and KDE also have specific sets of programs that can be used with a variety of formats. Other popular programs, such as Adobe/Macromedia's Flash Player, Real Player, VLC, MPlayer, and Xine, can also be installed, but are excluded from the Fedora repositories since they are not compatible with Fedora's licensing or are usually distributed with support for restricted formats. For more on this, refer to: the !
//fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software:Excluded Multimedia Software section."
@@ -1045,23 +1045,23 @@
#: en/Multimedia.xml:17(title)
msgid "Ogg and Xiph.Org Foundation Formats"
-msgstr ""
+msgstr "Ogg ????????? Xiph.Org ??????????????????????????? ??????????????????"
#: en/Multimedia.xml:18(para)
msgid "Fedora includes complete support for the Ogg media container format, the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. More information on these formats and how to use them can be found at the Xiph.Org Foundation's web site at http://www.xiph.org/."
-msgstr ""
+msgstr "?????????????????? ???????????? Ogg ??????????????? ????????????????????? ??????????????????, ??????????????? ????????????, ???????????? ???????????????, ??????????????? ???????????? ????????? FLAC ????????????????????? ???????????? ?????????????????? ?????? ?????????????????? ?????????????????? ???????????? ????????? ????????? ??????????????? ???????????????????????? ?????? ??????????????? ????????? ???????????? ????????????????????? Xiph.Org ??????????????????????????? ?????? ???????????????????????? http://www.xiph.org/ ???????????? ??????????????? ?????? ???????????? ?????????"
#: en/Multimedia.xml:22(title)
msgid "MP3 & DVD Support"
-msgstr ""
+msgstr "MP3 & DVD ??????????????????"
#: en/Multimedia.xml:23(para)
msgid "Fedora Core and Fedora Extras cannot include support for MP3 or DVD playback or recording, because the MP3 and MPEG (DVD) formats are patented, and the patent owners have not provided the necessary licenses. For more information, refer to http://fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software."
-msgstr ""
+msgstr "?????????????????? ????????? ????????? ?????????????????? ?????????????????? ???????????? MP3 ????????? DVD ??????????????? ????????? ???????????? ?????? ?????????????????? ?????????????????? ???????????? ???????????? ????????? ??????, ?????????????????? MP3 ????????? MPEG (DVD) ?????????????????? ?????????????????? ?????? ????????? ?????????????????? ????????????????????? ???????????? ??????????????? ????????? ????????? ????????????????????? ??????, http://fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software ???????????????"
#: en/Multimedia.xml:27(title)
msgid "Excluded Multimedia Software"
-msgstr ""
+msgstr "???????????? ???????????? ?????? ?????????????????? ????????????????????????"
#: en/Multimedia.xml:31(para)
msgid "Several programs are excluded from Fedora Core and Fedora Extras due to patent or license restrictions. These include programs which provide MP3 and DVD support, Flash Player, and Real Player. For more on this subject, please see http://fedoraproject.org/wiki/ForbiddenItems."
@@ -1069,7 +1069,7 @@
#: en/Multimedia.xml:35(title)
msgid "CD and DVD Authoring and Burning"
-msgstr ""
+msgstr "CD ?????? DVD ??????????????????????????? ????????? ???????????????"
#: en/Multimedia.xml:36(para)
msgid "Tools are included in Fedora Core and Fedora Extras for easily mastering and burning CDs and DVDs. Tools that can be used from the console include cdrecord, readcd, mkisofs, and other typical Linux applications. For GNOME users, the xcdroast package from Fedora Core and the graveman package from Fedora Extras allows for easy preparation of audio and data discs. For KDE users, the k3b package provides a very robust tool for these tasks."
@@ -1077,27 +1077,27 @@
#: en/Legacy.xml:8(title)
msgid "Legacy Information"
-msgstr ""
+msgstr "?????????????????? ?????????????????????"
#: en/Legacy.xml:10(title)
msgid "Systemwide Search Changes"
-msgstr ""
+msgstr "???????????????-??????????????? ????????? ????????????????????????"
#: en/Legacy.xml:12(title)
msgid "Slocate Replaced with mlocate"
-msgstr ""
+msgstr "Slocate ????????? mlocate ????????? ??????????????? ????????? ??????"
#: en/Legacy.xml:13(para)
msgid "The /usr/bin/{locate,updatedb} implementation slocate was replaced by mlocate."
-msgstr ""
+msgstr "/usr/bin/{locate,updatedb} ??????????????? ???????????? slocate ????????? mlocate ????????? ????????? ??????????????? ????????? ?????????"
#: en/Legacy.xml:16(para)
msgid "The locate command should be completely compatible"
-msgstr ""
+msgstr "locate ??????????????? ???????????? ?????????????????? ?????????????????? ???????????? ?????????????????? ??????"
#: en/Legacy.xml:19(para)
msgid "/etc/updatedb.conf is compatible for correct configuration files"
-msgstr ""
+msgstr "/etc/updatedb.conf ????????? ?????????????????? ?????????????????? ?????? ?????????????????? ??????"
#: en/Legacy.xml:23(para)
msgid "Syntax errors that slocate would not detect are now reported"
@@ -1105,7 +1105,7 @@
#: en/Legacy.xml:26(para)
msgid "The DAILY_UPDATE variable is not supported"
-msgstr ""
+msgstr "DAILY_UPDATE ???????????? ??????????????? ???????????? ??????"
#: en/Legacy.xml:29(para)
msgid "The updatedb command is not compatible, custom scripts using updatedb might have to be changed."
@@ -1113,7 +1113,7 @@
#: en/Legacy.xml:35(title)
msgid "LinuxThreads No Longer Available"
-msgstr ""
+msgstr "LinuxThreads ????????? ?????????????????? ???????????? ??????"
#: en/Legacy.xml:36(para)
msgid "The LinuxThreads library, which was deprecated in Fedora Core 4, is no longer available in this release. NPTL has been the default threading library since Red Hat Linux 9."
@@ -1121,7 +1121,7 @@
#: en/Legacy.xml:39(title)
msgid "Legacy Compatability Libraries"
-msgstr ""
+msgstr "?????????????????? ???????????????????????? ??????????????????????????????"
#: en/Legacy.xml:40(para)
msgid "Fedora Core includes legacy system libraries for compatibility with older software. This software is part of the Legacy Software Development group that is not installed by default. Users who require this functionality can select this group during installation or run the following command post-installation."
@@ -1130,11 +1130,11 @@
#: en/Legacy.xml:41(screen) en/BackwardsCompatibility.xml:10(screen)
#, no-wrap
msgid "yum groupinstall \"Legacy Software Development\""
-msgstr ""
+msgstr "yum groupinstall \"Legacy Software Development\""
#: en/Kernel.xml:8(title)
msgid "Linux Kernel"
-msgstr ""
+msgstr "??????????????? ????????????"
#: en/Kernel.xml:9(para)
msgid "This section is for content related to the kernel. If you have a contribution for this release notes beat for Fedora Core, add it to this page or create a sub-page. If you have any questions about what content might be appropriate for this page or if a sub-page is needed, please contact SamFolkWilliams or email the Fedora Documentation Project at fedora-docs-list at redhat.com."
@@ -1142,7 +1142,7 @@
#: en/Kernel.xml:11(title)
msgid "Version"
-msgstr ""
+msgstr "????????????"
#: en/Kernel.xml:12(para)
msgid "This distribution is based on the 2.6 series of the Linux kernel. Fedora Core may include additional patches for improvements, bug fixes, or additional features. For this reason, the Fedora Core kernel may not be line-for-line equivalent to the so-called vanilla kernel from the kernel.org web site:"
@@ -1150,29 +1150,29 @@
#: en/Kernel.xml:14(ulink)
msgid "http://www.kernel.org/"
-msgstr ""
+msgstr "http://www.kernel.org/"
#: en/Kernel.xml:16(para)
msgid "You may obtain a list of any such patches by using the command on the Fedora Core package:"
-msgstr ""
+msgstr "??????????????? ?????????????????? ????????? ??????????????? ?????? ????????? ??????????????? ??????????????? ????????????????????? ?????? ??????????????? ?????????????????? ?????? ???????????? ??????:"
#: en/Kernel.xml:17(screen)
#, no-wrap
msgid "rpm -qpl kernel-<version>.src.rpm"
-msgstr ""
+msgstr "rpm -qpl kernel-<version>.src.rpm"
#: en/Kernel.xml:20(title)
msgid "Changelog"
-msgstr ""
+msgstr "Changelog"
#: en/Kernel.xml:21(para)
msgid "The package changelog can be retrieved using the following command"
-msgstr ""
+msgstr "??????????????? ????????????????????? ????????? ????????? ??????????????? ??????????????? ????????? ?????????????????? ?????? ???????????? ??????"
#: en/Kernel.xml:22(screen)
#, no-wrap
msgid "rpm -q --changelog <kernel-version>"
-msgstr ""
+msgstr "rpm -q --changelog <kernel-version>"
#: en/Kernel.xml:23(para)
msgid "If you need a user friendly version of the changelog, refer to http://wiki.kernelnewbies.org/LinuxChanges. A short and full diff of the kernel is available from http://kernel.org/git. The Fedora version is based on the Linus tree."
@@ -1184,11 +1184,11 @@
#: en/Kernel.xml:27(title)
msgid "Kernel Flavors"
-msgstr ""
+msgstr "???????????? ?????????"
#: en/Kernel.xml:31(para)
msgid "Fedora Core includes the following kernel builds:"
-msgstr ""
+msgstr "?????????????????? ????????? ???????????? ????????? ??????????????? ???????????? ???????????? ?????? ??????:"
#: en/Kernel.xml:34(para)
msgid "Native kernel, in both uni-processor and SMP (Symmetric Multi-Processor) varieties. SMP kernels provide support for multiple CPU's or processors. Configured sources are available in the kernel-[smp-]devel-<version>.<arch>.rpm package."
@@ -1213,7 +1213,7 @@
#: en/Kernel.xml:50(screen)
#, no-wrap
msgid "rpm -Uvh kernel-[xen-hypervisor/xen-guest/kdump]-devel-<version>.<arch>.rpm"
-msgstr ""
+msgstr "rpm -Uvh kernel-[xen-hypervisor/xen-guest/kdump]-devel-<version>.<arch>.rpm"
#: en/Kernel.xml:52(title)
msgid "Default Kernels in x86_64 Architecture Provide SMP Capability"
@@ -1225,7 +1225,7 @@
#: en/Kernel.xml:57(title)
msgid "Following Generic Textbooks"
-msgstr ""
+msgstr "????????? ????????????????????? ?????? ????????????????????? ??????"
#: en/Kernel.xml:58(para)
msgid "Many of the tutorials, examples, and textbooks about Linux kernel development assume the kernel sources are installed under the /usr/src/linux/ directory. If you make a symbolic link, as shown below, you should be able to use those learning materials with the Fedora Core packages. Install the appropriate kernel sources, as shown earlier, and then:"
@@ -1234,11 +1234,11 @@
#: en/Kernel.xml:59(screen)
#, no-wrap
msgid "ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux"
-msgstr ""
+msgstr "ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux"
#: en/Kernel.xml:62(title)
msgid "Preparing for Kernel Development"
-msgstr ""
+msgstr "???????????? ??????????????? ?????? ???????????????"
#: en/Kernel.xml:63(para)
msgid "Fedora Core does not include the kernel-source package provided by older versions. Instead, configured sources are available, as described in this kernel flavors section."
@@ -1246,7 +1246,7 @@
#: en/Kernel.xml:64(para)
msgid "Users that require access to Fedora Core original kernel sources can find them in the kernel .src.rpm package."
-msgstr ""
+msgstr "??????????????????, ?????? ?????? ?????????????????? ????????? ???????????? ???????????? ???????????? ????????? ??????????????? ????????????????????? ??????, ?????? kernel.src.rpm ??????????????? ???????????? ????????? ???????????? ?????????"
#: en/Kernel.xml:65(para)
msgid "To create an exploded source tree from this file, perform the following steps:"
@@ -1254,7 +1254,7 @@
#: en/Kernel.xml:67(title)
msgid "These Instructions Refer to the Currently-running Kernel"
-msgstr ""
+msgstr "?????????????????? ????????? ????????? ???????????? ???????????? ????????? ????????????????????? ????????????????????? ????????????"
#: en/Kernel.xml:68(para)
msgid "To simplify the following directions, we have assumed that you want to configure the kernel sources to match your currently-running kernel. In the steps below, you must understand that the phrase <version> refers to the kernel version shown by the command: uname -r."
@@ -1262,7 +1262,7 @@
#: en/Kernel.xml:70(para)
msgid "1. Obtain the kernel-<version>.src.rpm file from one of the following sources:"
-msgstr ""
+msgstr "1. ????????? ??????????????? ?????????????????? ????????? kernel-<version>.src.rpm ???????????? ?????????:"
#: en/Kernel.xml:73(para)
msgid "The SRPMS directory on the appropriate SRPMS CD iso image."
@@ -1270,38 +1270,38 @@
#: en/Kernel.xml:76(para)
msgid "The FTP site where you got the kernel package."
-msgstr ""
+msgstr "FTP ????????????, ??????????????? ?????? ??????????????? ???????????? ??????????????? ????????? ?????????"
#: en/Kernel.xml:79(para)
msgid "By running the following command:"
-msgstr ""
+msgstr "????????? ??????????????? ??????????????? ?????? ??????????????? ????????????:"
#: en/Kernel.xml:80(screen)
#, no-wrap
msgid "yum install yum-utilsyumdownloader --source kernel"
-msgstr ""
+msgstr "yum install yum-utilsyumdownloader --source kernel"
#: en/Kernel.xml:83(para)
msgid "2. Install kernel-<version>.src.rpm using the command:"
-msgstr ""
+msgstr "2. kernel-<version>.src.rpm ?????????????????? ????????? ?????? ??????????????? ?????????:"
#: en/Kernel.xml:84(screen)
#, no-wrap
msgid "rpm -Uvh kernel-<version>.src.rpm`"
-msgstr ""
+msgstr "rpm -Uvh kernel-<version>.src.rpm`"
#: en/Kernel.xml:85(para)
msgid "This writes the RPM contents into /usr/src/redhat/SOURCES and /usr/src/redhat/SPECS."
-msgstr ""
+msgstr "?????? RPM ??????????????? ????????? /usr/src/redhat/SOURCES ????????? /usr/src/redhat/SPECS ???????????? ??????????????? ?????????"
#: en/Kernel.xml:86(para)
msgid "3. Prepare the kernel sources using the commands:"
-msgstr ""
+msgstr "3. ??????????????? ????????? ???????????? ???????????? ???????????? ?????????:"
#: en/Kernel.xml:87(screen)
#, no-wrap
msgid "cd /usr/src/redhat/SPECSrpmbuild -bp --target $(arch) kernel-2.6.spec"
-msgstr ""
+msgstr "cd /usr/src/redhat/SPECSrpmbuild -bp --target $(arch) kernel-2.6.spec"
#: en/Kernel.xml:88(para)
msgid "The kernel source tree is then located in the /usr/src/redhat/BUILD/kernel-<version>/ directory. It is common practice to move the resulting linux-<version> directory to the /usr/src/ tree; while not strictly necessary, do this to match the generally-available documentation."
@@ -1309,7 +1309,7 @@
#: en/Kernel.xml:90(command)
msgid "cd /usr/src/redhat/BUILD/kernel-<version> mv linux-<version> /usr/src/ cd /usr/src ln -s ./linux-<version> linux cd /usr/src/linux"
-msgstr ""
+msgstr "cd /usr/src/redhat/BUILD/kernel-<version> mv linux-<version> /usr/src/ cd /usr/src ln -s ./linux-<version> linux cd /usr/src/linux"
#: en/Kernel.xml:96(para)
msgid "4. The configurations for the specific kernels shipped in Fedora Core are in the configs/ directory. For example, the i686 SMP configuration file is named configs/kernel-<version>-i686-smp.config. Issue the following command to place the desired configuration file in the proper place for building:"
@@ -1318,7 +1318,7 @@
#: en/Kernel.xml:97(screen)
#, no-wrap
msgid "cp configs/<desired-config-file> .config"
-msgstr ""
+msgstr "cp configs/<desired-config-file> .config"
#: en/Kernel.xml:98(para)
msgid "You can also find the .config file that matches your current kernel configuration in the /lib/modules/<version>/build/.config file."
@@ -1335,16 +1335,16 @@
#: en/Kernel.xml:101(screen)
#, no-wrap
msgid "EXTRAVERSION = -prep"
-msgstr ""
+msgstr "EXTRAVERSION = -prep"
#: en/Kernel.xml:102(para)
msgid "to this:"
-msgstr ""
+msgstr "?????? ????????? ??????:"
#: en/Kernel.xml:103(screen)
#, no-wrap
msgid "EXTRAVERSION = -1.234_FC4"
-msgstr ""
+msgstr "EXTRAVERSION = -1.234_FC4"
#: en/Kernel.xml:104(para)
msgid "that is, substitute everything from the final dash onward."
@@ -1352,20 +1352,20 @@
#: en/Kernel.xml:105(para)
msgid "6. Issue the following command:"
-msgstr ""
+msgstr "6. ????????? ??????????????? ??????????????? ?????????:"
#: en/Kernel.xml:106(screen)
#, no-wrap
msgid "make oldconfig"
-msgstr ""
+msgstr "make oldconfig"
#: en/Kernel.xml:107(para)
msgid "You can then proceed as usual."
-msgstr ""
+msgstr "??????????????? ?????? ?????? ?????????????????? ???????????? ????????? ???????????? ?????????"
#: en/Kernel.xml:110(title)
msgid "Building Only Kernel Modules"
-msgstr ""
+msgstr "??????????????? ???????????? ?????????????????? ??????????????????"
#: en/Kernel.xml:111(para)
msgid "An exploded source tree is not required to build a kernel module, such as your own device driver, against the currently in-use kernel. For example, to build the foo.ko module, create the following Makefile in the directory containing the foo.c file:"
@@ -1374,15 +1374,15 @@
#: en/Kernel.xml:113(computeroutput)
#, no-wrap
msgid "obj-m := foo.o\nKDIR := /lib/modules/$(shell uname -r)/build\nPWD := $(shell pwd)\ndefault:$(MAKE) -C $(KDIR) M=$(PWD) modules"
-msgstr ""
+msgstr "obj-m := foo.o\nKDIR := /lib/modules/$(shell uname -r)/build\nPWD := $(shell pwd)\ndefault:$(MAKE) -C $(KDIR) M=$(PWD) modules"
#: en/Kernel.xml:118(para)
msgid "Issue the make command to build the foo.ko module."
-msgstr ""
+msgstr "make ??????????????? foo.ko ?????????????????? ??????????????? ?????? ????????????"
#: en/Kernel.xml:121(title)
msgid "User Space Dependencies on the Kernel"
-msgstr ""
+msgstr "???????????? ???????????? ???????????? ???????????? ?????????????????????"
#: en/Kernel.xml:122(para)
msgid "Fedora Core release has support for clustered storage through the Global File System (GFS). This requires a special kernel that works in conjunction with some user-space utilities, such as management daemons. Consequently, to remove such a kernel, perhaps after an update, you cannot simply use the rpm -e kernel-<version> command as in earlier distributions because these user space packages depend on the kernel package. You may either list both the kernel package and all of its user space dependent packages on the rpm -e command, or you can use the yum remove kernel-<version> command instead. The yum command automatically removes dependent packages, if necessary."
@@ -1390,7 +1390,7 @@
#: en/Java.xml:8(title)
msgid "Java"
-msgstr ""
+msgstr "????????????"
#: en/Java.xml:9(para)
msgid "A free and open source Java environment is available within this Fedora Core release."
@@ -1406,7 +1406,7 @@
#: en/Java.xml:12(para)
msgid "For more information see the FAQ at http://www.fedoraproject.org/wiki/JavaFAQ."
-msgstr ""
+msgstr "???????????? ???????????? ?????? http://www.fedoraproject.org/wiki/JavaFAQ ???????????????"
#: en/Java.xml:15(para)
msgid "Refer to the Docs/Beats/PackageNotes/Java page for information about Java packages."
@@ -1414,11 +1414,11 @@
#: en/Installer.xml:8(title)
msgid "Installation-Related Notes"
-msgstr ""
+msgstr "?????????????????????????????? ????????? ??????????????? ???????????????"
#: en/Installer.xml:9(para)
msgid "This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core in general."
-msgstr ""
+msgstr "?????? ????????? ???????????? ??????????????? ????????????????????? ???????????? ???????????? ???????????? ?????? ??????, ?????? ?????? ???????????????????????? (?????????????????? ????????? ?????????????????????????????? ?????????????????????) ????????? ?????? ?????????????????? ????????? ?????????????????????????????? ????????? ?????????????????? ?????????"
#: en/Installer.xml:10(para)
msgid "If you intend to download the Fedora Core 5 Test 2 DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2GB in size. For example, wget before version 1.9.1-16 in Fedora will exit with a File size limit exceeded error."
@@ -1434,11 +1434,11 @@
#: en/Installer.xml:14(ulink)
msgid "http://torrent.fedoraproject.org/"
-msgstr ""
+msgstr "http://torrent.fedoraproject.org/"
#: en/Installer.xml:17(title)
msgid "Installer Notes"
-msgstr ""
+msgstr "????????????????????? ???????????????"
#: en/Installer.xml:20(para)
msgid "The Fedora Core installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. Fedora Project recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs). To use this test, type linux mediacheck at the boot: prompt."
@@ -1451,7 +1451,7 @@
#: en/Installer.xml:22(screen)
#, no-wrap
msgid "linux ide=nodma "
-msgstr ""
+msgstr "linux ide=nodma "
#: en/Installer.xml:23(para)
msgid "Use the sha1sum utility to verify discs before carrying out an installation. This test accurately identifies discs that are not valid or identical to the ISO image files."
@@ -1463,11 +1463,11 @@
#: en/Installer.xml:28(title)
msgid "Boot From Installation CD 1"
-msgstr ""
+msgstr "?????????????????????????????? CD 1 ????????? ????????? ?????????"
#: en/Installer.xml:29(para)
msgid "You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use this feature."
-msgstr ""
+msgstr "????????????????????? ?????? ???????????? ?????? ??????????????? ????????? ?????? CD-ROM 1 ????????? (??????????????????????????? CD-ROM) ????????? ????????? ???????????? ??????????????????"
#: en/Installer.xml:33(para)
msgid "Fedora Core supports graphical FTP and HTTP installations. However, due to the necessity of containing the installer image in RAM, only systems with more than 128MB of RAM (or systems booted from CD-ROM 1, which contains the installer image) can use the graphical installer. Systems with 128MB or less will continue to use the text-based installer."
@@ -1475,11 +1475,11 @@
#: en/Installer.xml:37(title)
msgid "Changes In The Installer"
-msgstr ""
+msgstr "????????????????????? ???????????? ?????????????????? ????????????????????????"
#: en/Installer.xml:40(para)
msgid "Support of yum for dependancy solver backend has been added and additional repositories are expected to be supported during installation in a future release."
-msgstr ""
+msgstr "?????????????????? ????????????????????? ???????????? ????????? ?????? ?????? ?????? ?????????????????? ????????? ??????????????? ????????? ?????? ????????? ????????? ????????????????????????????????? ???????????? ?????? ????????? ???????????? ??????, ?????? ?????? ??????????????? ?????? ???????????? ???????????? ?????????????????? ?????? ???????????? ?????????"
#: en/Installer.xml:43(para)
msgid "The installer checks the hardware capability and installs either the uniprocessor or SMP (Symmetric Multi Processor) kernel as appropriate in this release. Previous releases installed both the variants and used the appropriate one as default."
@@ -1487,19 +1487,19 @@
#: en/Installer.xml:46(para)
msgid "Partition setting has been reworked to be more user friendly"
-msgstr ""
+msgstr "????????? ??????????????? ????????? ????????? ?????????????????? ??????????????? ??????????????? ?????? ????????????????????? ????????? ?????????"
#: en/Installer.xml:49(para)
msgid "Remote logging via syslog is supported in this release. pass syslog=host:port (port is optional) at the boot prompt."
-msgstr ""
+msgstr "?????? ???????????? ???????????? syslog ?????? ??????????????? ???????????? ??????????????? ?????????-?????? ???????????? ???????????? ????????? ????????? ??????????????? ???????????? syslog=host:port (???????????? ?????????????????? ??????) ????????????"
#: en/Installer.xml:52(para)
msgid "Firewall/SELinux configuration has been moved to the final installation phase called 'firstboot'."
-msgstr ""
+msgstr "?????????????????????/SELinux ?????????????????? ????????? ????????? ?????????????????????????????? ?????? ???????????? ?????????, ????????? ????????? 'firstboot' ?????????????????? ??????, ???????????? ????????? ??????????????? ????????? ?????????"
#: en/Installer.xml:55(para)
msgid "Rendering of html pages is now done using the gtkhtml widget for better capability."
-msgstr ""
+msgstr "html ?????????????????? ???????????? ????????? ???????????????????????? gtkhtml ?????????????????? ????????? ???????????? ???????????????????????? ???????????? ??????????????? ?????????"
#: en/Installer.xml:58(para)
msgid "Kickstart has been refactored into its own package - pykickstart - containing parser and writers. As a result of this change validation and extending kickstart is now much easier."
@@ -1516,15 +1516,15 @@
#: en/Installer.xml:65(screen)
#, no-wrap
msgid "dmraid "
-msgstr ""
+msgstr "dmraid "
#: en/Installer.xml:66(para)
msgid "For more information, check the DmraidStatus page."
-msgstr ""
+msgstr "????????? ????????????????????? ?????? DmraidStatus ???????????? ???????????????"
#: en/Installer.xml:71(title)
msgid "Installation Related Issues"
-msgstr ""
+msgstr "?????????????????????????????? ????????? ?????????????????? ???????????????"
#: en/Installer.xml:74(para)
msgid "Certain hardware configurations (particularly those with LCD displays) may experience problems while starting the Fedora Core installation program. In these instances, restart the installation, and add the \"nofb\" option to the boot command line."
@@ -1532,7 +1532,7 @@
#: en/Installer.xml:76(title)
msgid "CJK Language Support"
-msgstr ""
+msgstr "CJK ??????????????? ??????????????????"
#: en/Installer.xml:77(para)
msgid "Chinese, Japanese, and Korean graphical installations started using the \"nofb\" option will start in English, and then switch to the appropriate language once the graphical phase of the installation process begins."
@@ -1545,7 +1545,7 @@
#: en/Installer.xml:82(screen)
#, no-wrap
msgid "pci=off ide1=0x180,0x386 "
-msgstr ""
+msgstr "pci=off ide1=0x180,0x386 "
#: en/Installer.xml:83(para)
msgid "This option allows the installation to proceed normally; any devices not detected due to the use of this option are configured the first time Fedora Core is booted."
@@ -1553,11 +1553,11 @@
#: en/Installer.xml:89(title)
msgid "Upgrading Related Issues"
-msgstr ""
+msgstr "????????????????????? ????????? ??????????????? ???????????????"
#: en/Installer.xml:90(para)
msgid "Refer to http://fedoraproject.org/wiki/DistributionUpgrades page for detailedrecommended procedures for upgradation of Fedora."
-msgstr ""
+msgstr "http://fedoraproject.org/wiki/DistributionUpgrades ???????????? ????????? ?????????????????? ????????????????????? ????????? ?????? ???????????????????????? ??????????????? ???????????? ???????????? ?????? ???????????????"
#: en/Installer.xml:91(para)
msgid "In general, fresh installations are to be recommended over upgrades, particularly for systems with software from add-on repositories installed. If third party packages are installed on the system, they might not work as expected. If an upgrade is attempted, the following may be helpful."
@@ -1569,20 +1569,20 @@
#: en/Installer.xml:96(title)
msgid "Make Backups!"
-msgstr ""
+msgstr "?????????????????? ????????????!"
#: en/Installer.xml:97(para)
msgid "Backups of configurations in /etc are also very useful in reconstructing system settings after a fresh install."
-msgstr ""
+msgstr "/etc ??????????????? ?????????????????? ?????? ?????????????????? ????????? ????????? ?????????????????????????????? ?????? ???????????? ??????????????? ?????????????????? ?????????-?????????????????? ????????? ?????? ??????????????? ?????????"
#: en/Installer.xml:101(para)
msgid "After completing the upgrade, run the command:"
-msgstr ""
+msgstr "????????????????????? ????????? ????????????, ??????????????? ????????????:"
#: en/Installer.xml:102(screen)
#, no-wrap
msgid "rpm -qa --last > RPMS_by_Install_Time.txt "
-msgstr ""
+msgstr "rpm -qa --last > RPMS_by_Install_Time.txt "
#: en/Installer.xml:105(para)
msgid "Inspect the end of the output for packages that pre-date the upgrade and remove/upgrade those from 3rd party repos, or otherwise deal with them as necessary."
@@ -1590,19 +1590,19 @@
#: en/I18n.xml:8(title)
msgid "Internationalization (i18n)"
-msgstr ""
+msgstr "?????????????????????????????????????????? (i18n)"
#: en/I18n.xml:9(para)
msgid "SCIM has replaced IIIMF as the language input framework in Fedora Core in this release."
-msgstr ""
+msgstr "SCIM ?????? IIIMF ?????????????????? ????????? ?????? ?????? ???????????? ???????????? ??????????????? ?????????????????? ????????????????????? ????????? ??????????????? ?????? ??????????????? ?????????"
#: en/FileSystems.xml:8(title)
msgid "File Systems"
-msgstr ""
+msgstr "???????????? ???????????????"
#: en/FileServers.xml:8(title)
msgid "File Servers"
-msgstr ""
+msgstr "???????????? ????????????"
#: en/FileServers.xml:9(para)
msgid "This section refers to file transfer and sharing servers. Please refer to the Web Servers and Samba sections for information on HTTP (Web) file transfer and Samba (Windows) file sharing."
@@ -1610,7 +1610,7 @@
#: en/FileServers.xml:11(title)
msgid "Netatalk (Macintosh Compatibility)"
-msgstr ""
+msgstr "Netatalk (Macintosh ????????????????????????)"
#: en/FileServers.xml:12(para)
msgid "This section contains information related to Netatalk, a suite of software that enables Linux to interact with Macintosh systems using the AppleTalk network protocols."
@@ -1626,7 +1626,7 @@
#: en/FileServers.xml:18(para)
msgid "Upgrade information is available directly from the Netatalk site at http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html."
-msgstr ""
+msgstr "Netatalk ???????????? http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html ????????? ??????????????? ????????????????????? ????????????????????? ???????????????"
#: en/FileServers.xml:20(para)
msgid "The documentation is also included in the netatalk package. Refer to either /usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html, or /usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf (numbered page 25, document page 33)."
@@ -1634,15 +1634,15 @@
#: en/Feedback.xml:8(title)
msgid "Feedback"
-msgstr ""
+msgstr "???????????????"
#: en/Feedback.xml:9(para)
msgid "Thanks for your interest in helping us with the release notes by providing feedback. This section explains how you can give that feedback."
-msgstr ""
+msgstr "???????????? ??????????????? ???????????? ??????????????? ????????? ?????? ?????????????????? ?????????????????? ???????????? ?????????????????? ????????? ?????? ????????? ???????????? ??????????????? ????????? ?????? ?????? ??????????????? ??????????????? ?????????????????? ?????? ???????????? ?????????"
#: en/Feedback.xml:11(title)
msgid "Release Notes Feedback Procedure"
-msgstr ""
+msgstr "???????????? ??????????????? ??????????????? ?????????"
#: en/Feedback.xml:12(para)
msgid "If you feel that these release notes could be improved in some way, you can provide feedback directly to the beat writers. Here are several ways, in order of preference:"
@@ -1650,27 +1650,27 @@
#: en/Feedback.xml:15(para)
msgid "Edit content directly at Docs/Beats"
-msgstr ""
+msgstr "Docs/Beats ???????????? ??????????????? ????????? ?????????"
#: en/Feedback.xml:19(para)
msgid "Email relnotes at fedoraproject.org"
-msgstr ""
+msgstr "???-????????? relnotes at fedoraproject.org"
#: en/Feedback.xml:23(para)
msgid "Fill out this pre-filled bug request template"
-msgstr ""
+msgstr "??????????????????-???????????? ????????? ????????? ??????????????? ????????????"
#: en/Feedback.xml:27(para)
msgid "A release note beat is an area of the release notes that is the responsibility of one or more content contributors to oversee."
-msgstr ""
+msgstr "?????????????????? ??????????????? ????????? ???????????? ??????????????? ?????? ???????????? ??????, ?????? ?????? ????????? ????????? ????????? ??????????????????????????? ?????? ??????????????????????????? ?????????"
#: en/Feedback.xml:28(para)
msgid "Thank you (in advance) for your feedback!"
-msgstr ""
+msgstr "?????????????????? ????????????????????? ?????? (?????????????????? ??????) ??????????????????!"
#: en/Entertainment.xml:8(title)
msgid "Games and Entertainment"
-msgstr ""
+msgstr "??????????????? ????????? ?????????????????????"
#: en/Entertainment.xml:9(para)
msgid "Fedora Core and Fedora Extras provide a selection of games that cover a variety of genres. By default, Fedora Core includes a small package of games for GNOME (called gnome-games). For a list of other games that are available for installation through yum, open a terminal and enter the following command:"
@@ -1679,19 +1679,19 @@
#: en/Entertainment.xml:10(screen)
#, no-wrap
msgid "yum groupinfo \"Games and Entertainment\""
-msgstr ""
+msgstr "yum groupinfo \"Games and Entertainment\""
#: en/Entertainment.xml:11(para)
msgid "For help using yum to install the assorted game packages, refer to the guide available at:"
-msgstr ""
+msgstr "yum ?????? ??????????????? ???????????? ?????????????????? ??????????????? ???????????? ??????????????? ?????????????????? ????????? ??????, ??????????????? ???????????? ????????????:"
#: en/Entertainment.xml:13(ulink)
msgid "http://fedora.redhat.com/docs/yum/"
-msgstr ""
+msgstr "http://fedora.redhat.com/docs/yum/"
#: en/Extras.xml:8(title)
msgid "Fedora Extras Repository"
-msgstr ""
+msgstr "?????????????????? ?????????????????? ???????????????????????????"
#: en/Extras.xml:9(para)
msgid "Fedora Extras is part of the larger Fedora Project and is a volunteer-based community effort to create a repository of packages that compliment Fedora Core. The Fedora Extras repository is enabled by default."
@@ -1699,40 +1699,40 @@
#: en/Extras.xml:10(para)
msgid "You can lean more about Fedora Extras from http://fedoraproject.org/wiki/Extras."
-msgstr ""
+msgstr "??????????????? ?????????????????? ?????????????????? ???????????? ????????? ????????????????????? http://fedoraproject.org/wiki/Extras ???????????? ????????? ???????????? ?????????"
#: en/Extras.xml:13(para)
msgid "If you would like to install any software available from Fedora extras you can use yum."
-msgstr ""
+msgstr "???????????? ??????????????? ????????? ?????? ??????????????? ?????????????????? ???????????? ????????????????????? ?????? ????????? ??????????????? ?????? (yum) ?????? ??????????????? ???????????? ?????????????????? ?????????????????? ????????? ?????? ???????????? ?????????"
#: en/Extras.xml:14(screen)
#, no-wrap
msgid "yum install <packagename>"
-msgstr ""
+msgstr "yum install <packagename>"
#: en/Extras.xml:15(para)
msgid "Where <packagename> is the name of the package you want to install. For example, if you wanted to install the abiword package, the command yum install abiword automatically installs the package and all dependencies."
-msgstr ""
+msgstr "??????????????? ?????? <packagename> ?????? ??????????????? ?????? ????????? ??????, ????????? ????????? ??????????????? ?????????????????? ???????????? ????????????????????? ????????? ?????????????????? ??????, ??????????????? abiword ??????????????? ?????????????????? ???????????? ????????????????????? ??????, ????????? yum install abiword ??????????????? ??????????????? ????????? ?????? ????????????????????? ????????? ?????????-???????????? ?????? ???????????? ?????? ?????????????????????"
#: en/DevelToolsGCC.xml:8(title)
msgid "GCC Compiler Collection"
-msgstr ""
+msgstr "GCC ????????????????????? ???????????????"
#: en/DevelToolsGCC.xml:9(para)
msgid "This release of Fedora has been built using GCC 4.1, which is included with the distribution."
-msgstr ""
+msgstr "?????????????????? ????????? GCC 4.1 ?????? ??????????????? ???????????? ??????????????? ????????? ??????, ?????? ?????? ?????? ???????????????????????????????????? ???????????? ?????????????????? ???????????? ????????? ?????????"
#: en/DevelToolsGCC.xml:11(title)
msgid "Caveats"
-msgstr ""
+msgstr "Caveats"
#: en/DevelToolsGCC.xml:14(para)
msgid "GDB 6.1 or newer is needed to debug binaries unless compiled using the -fno-var-tracking compilation option."
-msgstr ""
+msgstr "GDB 6.1 ????????? ???????????? ?????? ????????? ?????????????????? ????????? ?????? ?????????????????? ??????, ???????????? ????????? ?????? -fno-var-tracking ?????????????????????????????? ????????? ????????? ?????????????????? ???????????? ???????????????"
#: en/DevelToolsGCC.xml:17(para)
msgid "The -fwritable-strings option is no longer accepted."
-msgstr ""
+msgstr "-fwritable-strings ????????? ????????? ?????????????????? ???????????? ???????????? ??????????????? ?????????"
#: en/DevelToolsGCC.xml:20(para)
msgid "English-language diagnostic messages now use Unicode quotes; if you cannot read this, set your LC_CTYPE environment variable to C or change your terminal emulator."
@@ -1744,7 +1744,7 @@
#: en/DevelToolsGCC.xml:27(title)
msgid "Code Generation"
-msgstr ""
+msgstr "????????? ???????????????"
#: en/DevelToolsGCC.xml:30(para)
msgid "The SSA code optimizer is now included and brings with it better constant propagation, partial redundancy elimination, load and store code motion, strength reduction, dead storage elimination, better detection of unreachable code, and tail recursion by accumulation."
@@ -1756,7 +1756,7 @@
#: en/DevelToolsGCC.xml:38(title)
msgid "Language Extensions"
-msgstr ""
+msgstr "??????????????? ??????????????????"
#: en/DevelToolsGCC.xml:41(para)
msgid "A sentinel attribute has been added so that the compiler will now issue a warning if a function such as execl(char *path, const char *arg, ...), which requires a NULL list terminator is missing the NULL."
@@ -1788,15 +1788,15 @@
#: en/DevelTools.xml:8(title)
msgid "Developer Tools"
-msgstr ""
+msgstr "???????????? ?????????"
#: en/DevelTools.xml:9(para)
msgid "This section covers various developer tools."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????? ???????????? ??????????????? ???????????? ????????????????????? ??????????????? ?????? ?????????"
#: en/DevelTools.xml:13(title)
msgid "FORTRAN"
-msgstr ""
+msgstr "FORTRAN"
#: en/DevelTools.xml:16(para)
msgid "The GNU FORTRAN 77 front end has been replaced by a new FORTRAN 90/95 recognizer."
@@ -1804,15 +1804,15 @@
#: en/DevelTools.xml:21(title)
msgid "Eclipse Development Environment"
-msgstr ""
+msgstr "??????????????? ???????????? ?????????????????????"
#: en/DevelTools.xml:24(para)
msgid "Eclipse 3.1M6 has been compiled as a native application."
-msgstr ""
+msgstr "Eclipse 3.1M6 ????????? ????????? ???????????? ?????? ????????? ???????????? ?????????????????? ???????????? ????????? ?????????"
#: en/DevelTools.xml:27(para)
msgid "The C Development Tool (CDT) has been included."
-msgstr ""
+msgstr "C Development Tool (CDT) ?????? ?????????????????? ???????????? ????????? ?????????"
#: en/Desktop.xml:9(para)
msgid "GNOME 2.13.2 and KDE 3.5 Release Candidate 2 has been included in Fedora Core 5 test 2. GNOME 2.14 (or a release candidate) is scheduled to be available as part of Fedora Core 5."
@@ -1828,7 +1828,7 @@
#: en/Desktop.xml:16(para)
msgid "gnome-screensaver: Provides a integrated user interface to screensavers and the lock screen dialog."
-msgstr ""
+msgstr "gnome-screensaver: ???????????????-???????????? ?????? ???????????? ?????????????????? ????????????????????? ????????? ????????????????????? ??????????????? ???????????????????????? ??????????????? ?????????"
#: en/Desktop.xml:19(para)
msgid "memory optimizations in the fontconfig and shared-mime-info packages. These now use shared memory-mapped caches for this data."
@@ -1841,7 +1841,7 @@
#: en/Desktop.xml:23(screen)
#, no-wrap
msgid "yum install nautilus-open-terminal"
-msgstr ""
+msgstr "yum install nautilus-open-terminal"
#: en/Desktop.xml:24(para)
msgid "Screensavers except the one providing a blank screen are not installed by default from Fedora Core 4 onwards. Many of the screensavers are found to be offensive or known to abruptly terminate the graphical interface, in particular some of the OpenGL animated ones provided within xscreensaver-gl-extras package. Some of them also provide a unexpected suprise to users. Users who need it can install it using the following command."
@@ -1850,11 +1850,11 @@
#: en/Desktop.xml:25(screen)
#, no-wrap
msgid "yum install xscreensaver-extras xscreensaver-gl-extras"
-msgstr ""
+msgstr "yum install xscreensaver-extras xscreensaver-gl-extras"
#: en/Desktop.xml:27(title)
msgid "system-config-mouse Removed"
-msgstr ""
+msgstr "system-config-mouse ???????????????"
#: en/Desktop.xml:28(para)
msgid "system-config-mouse configuration utility has been dropped from this release since synaptic and 3 button mouse configuration is being done automatically during installation and serial mice are not formally supported in Fedora Core anymore."
@@ -1862,135 +1862,135 @@
#: en/DatabaseServers.xml:8(title)
msgid "Database Servers"
-msgstr ""
+msgstr "????????????????????? ????????????"
#: en/DatabaseServers.xml:14(emphasis)
msgid "No changes of note."
-msgstr ""
+msgstr "??????????????? ?????? ????????? ?????????????????? ???????????? ?????????"
#: en/Colophon.xml:8(title)
msgid "Colophon"
-msgstr ""
+msgstr "?????????"
#: en/Colophon.xml:10(title)
msgid "Draft"
-msgstr ""
+msgstr "???????????????"
#: en/Colophon.xml:11(para)
msgid "This is a draft, so it is incomplete and imperfect."
-msgstr ""
+msgstr "?????? ??????????????? ??????, ?????????????????? ??????????????? ????????? ??????-?????????????????? ?????????"
#: en/Colophon.xml:16(title)
msgid "About the Colophon"
-msgstr ""
+msgstr "????????? ????????????"
#: en/Colophon.xml:17(para)
msgid "As we use the term, colophon means:"
-msgstr ""
+msgstr "??????????????? ?????? ???????????? ??????????????? ?????????, ????????? ?????? ???????????? ??????:"
#: en/Colophon.xml:20(para)
msgid "A way to recognize contributors, while providing accountability."
-msgstr ""
+msgstr "?????????????????? ?????? ???????????? ???????????????, ???????????? ?????? ?????????????????? ??????????????? ??????????????? ?????????"
#: en/Colophon.xml:23(para)
msgid "Explain tools and production methods."
-msgstr ""
+msgstr "????????? ????????? ?????????????????? ????????? ??????????????? ?????????"
#: en/Colophon.xml:28(title)
msgid "Contributors"
-msgstr ""
+msgstr "??????????????????"
#: en/Colophon.xml:31(para)
msgid "Andrew Martynov (translator, Russian)"
-msgstr ""
+msgstr "Andrew Martynov (????????????????????? ????????????)"
#: en/Colophon.xml:35(para)
msgid "Anthony Green (beat writer)"
-msgstr ""
+msgstr "Anthony Green (????????? ????????????)"
#: en/Colophon.xml:39(para)
msgid "Bob Jensen (beat writer)"
-msgstr ""
+msgstr "Bob Jensen (????????? ????????????)"
#: en/Colophon.xml:43(para)
msgid "Dave Malcolm (beat writer)"
-msgstr ""
+msgstr "Dave Malcolm (????????? ????????????)"
#: en/Colophon.xml:47(para)
msgid "David Woodhouse (beat writer)"
-msgstr ""
+msgstr "David Woodhouse (????????? ????????????)"
#: en/Colophon.xml:51(para)
msgid "Francesco Tombolini (translator, Italian)"
-msgstr ""
+msgstr "Francesco Tombolini (?????????????????????, ??????????????????)"
#: en/Colophon.xml:56(para)
msgid "Gavin Henry (beat writer)"
-msgstr ""
+msgstr "Gavin Henry (????????? ????????????)"
#: en/Colophon.xml:60(para)
msgid "Jens Petersen (beat writer)"
-msgstr ""
+msgstr "Jens Petersen (????????? ????????????)"
#: en/Colophon.xml:64(para)
msgid "Joe Orton (beat writer)"
-msgstr ""
+msgstr "Joe Orton (????????? ????????????)"
#: en/Colophon.xml:68(para)
msgid "Josh Bressers (beat writer)"
-msgstr ""
+msgstr "Josh Bressers (????????? ????????????)"
#: en/Colophon.xml:72(para)
msgid "Karsten Wade (beat writer, editor, publisher)"
-msgstr ""
+msgstr "Karsten Wade (????????? ????????????, ??????????????????, ?????????????????????)"
#: en/Colophon.xml:76(para)
msgid "Luya Tshimbalanga (beat writer)"
-msgstr ""
+msgstr "Luya Tshimbalanga (????????? ????????????)"
#: en/Colophon.xml:80(para)
msgid "Patrick Barnes (beat writer, editor)"
-msgstr ""
+msgstr "Patrick Barnes (????????? ????????????, ??????????????????)"
#: en/Colophon.xml:84(para)
msgid "Paul W. Frields (tools, editor)"
-msgstr ""
+msgstr "Paul W. Frields (?????????, ??????????????????)"
#: en/Colophon.xml:88(para)
msgid "RahulSundaram (beat writer, editor)"
-msgstr ""
+msgstr "RahulSundaram (????????? ????????????, ??????????????????)"
#: en/Colophon.xml:92(para)
msgid "SekineTatsuo (translator, Japanese)"
-msgstr ""
+msgstr "SekineTatsuo (?????????????????????, ??????????????????)"
#: en/Colophon.xml:96(para)
msgid "SteveDickson (beat writer)"
-msgstr ""
+msgstr "SteveDickson (????????? ????????????)"
#: en/Colophon.xml:100(para)
msgid "StuartElliss (editor)"
-msgstr ""
+msgstr "StuartElliss (??????????????????)"
#: en/Colophon.xml:104(para)
msgid "ThomasGraf (beat writer)"
-msgstr ""
+msgstr "ThomasGraf (????????? ????????????)"
#: en/Colophon.xml:108(para)
msgid "TommyReynolds (tools)"
-msgstr ""
+msgstr "TommyReynolds (?????????)"
#: en/Colophon.xml:112(para)
msgid "YoshinariTakaoka (translator, tools)"
-msgstr ""
+msgstr "YoshinariTakaoka (?????????????????????, ?????????)"
#: en/Colophon.xml:116(para)
msgid "YuanYijun (translator, Simplified Chinese)"
-msgstr ""
+msgstr "YuanYijun (?????????????????????, ??????????????? ????????????)"
#: en/BackwardsCompatibility.xml:5(title) en/BackwardsCompatibility.xml:8(title)
msgid "Backwards Compatibility"
-msgstr ""
+msgstr "?????????-????????? ????????????????????????"
#: en/BackwardsCompatibility.xml:9(para)
msgid "Fedora includes several system libraries and software for compatibility with older software. These software are part of the \"Legacy Software Development\" group which are not installed by default. Users who require this functionality can select this group during installation or run the following the command post-installation."
@@ -1998,7 +1998,7 @@
#: en/ArchSpecificx86.xml:8(title)
msgid "x86 Specifics for Fedora"
-msgstr ""
+msgstr "?????????????????? ?????? x86 ?????????????????????"
#: en/ArchSpecificx86.xml:9(para)
msgid "This section covers any specific information you may need to know about Fedora Core and the x86 hardware platform."
@@ -2006,7 +2006,7 @@
#: en/ArchSpecificx86.xml:11(title)
msgid "x86 Hardware Requirements"
-msgstr ""
+msgstr "x86 ???????????? ???????????????"
#: en/ArchSpecificx86.xml:12(para) en/ArchSpecificx86_64.xml:12(para)
msgid "The following information represents the minimum hardware requirements necessary to successfully install Fedora Core ."
@@ -2018,11 +2018,11 @@
#: en/ArchSpecificx86.xml:15(title)
msgid "CPU Requirements"
-msgstr ""
+msgstr "CPU ?????????"
#: en/ArchSpecificx86.xml:16(para)
msgid "This section lists the CPU specifications required by Fedora Core ."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????????????????? ????????? ?????? CPU ????????????????????? ?????????"
#: en/ArchSpecificx86.xml:17(para)
msgid "The following CPU specifications are stated in terms of Intel processors. Other processors (notably, offerings from AMD, Cyrix, and VIA) that are compatible with and equivalent to the following Intel processors may also be used with Fedora Core."
@@ -2034,27 +2034,27 @@
#: en/ArchSpecificx86.xml:23(para)
msgid "Recommended for text-mode: 200 MHz Pentium-class or better"
-msgstr ""
+msgstr "????????? ????????? ?????? ????????????????????????: 200 ??????????????????????????? Pentium ????????? ????????? ????????????"
#: en/ArchSpecificx86.xml:26(para)
msgid "Recommended for graphical: 400 MHz Pentium II or better"
-msgstr ""
+msgstr "????????????????????? ?????? ????????????????????????: 400 ??????????????????????????? Pentium II ????????? ????????????"
#: en/ArchSpecificx86.xml:29(para)
msgid "AMD64 processors (both Athlon64 and Opteron)"
-msgstr ""
+msgstr "AMD64 ????????????????????? (Athlon64 ????????? Opteron ???????????????)"
#: en/ArchSpecificx86.xml:32(para)
msgid "Intel processors with Intel?? Extended Memory 64 Technology (Intel?? EM64T)"
-msgstr ""
+msgstr "Intel?? Extended Memory 64 Technology (Intel?? EM64T) ????????? Intel ?????????????????????"
#: en/ArchSpecificx86.xml:36(title) en/ArchSpecificx86_64.xml:15(title) en/ArchSpecificPPC.xml:31(title)
msgid "Hard Disk Space Requirements"
-msgstr ""
+msgstr "???????????? ???????????? ???????????? ????????? ?????????"
#: en/ArchSpecificx86.xml:37(para) en/ArchSpecificx86_64.xml:16(para) en/ArchSpecificPPC.xml:32(para)
msgid "This section lists the disk space required to install Fedora Core ."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????????????????? ????????? ?????????????????? ????????? ?????? ?????????????????? ???????????? ????????? ???????????? ????????????????????? ?????????"
#: en/ArchSpecificx86.xml:38(para) en/ArchSpecificx86_64.xml:17(para) en/ArchSpecificPPC.xml:33(para)
msgid "The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system."
@@ -2070,31 +2070,31 @@
#: en/ArchSpecificx86.xml:43(title) en/ArchSpecificx86_64.xml:21(title)
msgid "Memory Requirements"
-msgstr ""
+msgstr "?????????????????? ?????????"
#: en/ArchSpecificx86.xml:44(para) en/ArchSpecificx86_64.xml:22(para)
msgid "This section lists the memory required to install Fedora Core ."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????????????????? ????????? ?????????????????? ????????? ?????? ?????????????????? ?????????????????? ???????????? ?????????"
#: en/ArchSpecificx86.xml:45(para)
msgid "This list is for 32-bit x86 systems:"
-msgstr ""
+msgstr "?????? ???????????? 32-???????????? x86 ????????????????????? ?????? ??????:"
#: en/ArchSpecificx86.xml:48(para)
msgid "Minimum for text-mode: 64MB"
-msgstr ""
+msgstr "????????? ????????? ?????? ????????????-?????????: 64????????????"
#: en/ArchSpecificx86.xml:51(para)
msgid "Minimum for graphical: 192MB"
-msgstr ""
+msgstr "????????????????????? ?????? ????????????-?????????: 192????????????"
#: en/ArchSpecificx86.xml:54(para)
msgid "Recommended for graphical: 256MB"
-msgstr ""
+msgstr "????????????????????? ?????? ????????????????????????: 256????????????"
#: en/ArchSpecificx86.xml:61(title)
msgid "x86 Installation Notes"
-msgstr ""
+msgstr "x86 ?????????????????????????????? ???????????????"
#: en/ArchSpecificx86.xml:62(para)
msgid "Installer package screen selection interface is being redesigned in the Fedora development version. Fedora Core does not provide an option to select the installation type such as Personal Desktop, Workstation, Server and custom."
@@ -2102,93 +2102,93 @@
#: en/ArchSpecificx86_64.xml:8(title)
msgid "x86_64 Specifics for Fedora"
-msgstr ""
+msgstr "?????????????????? ?????? x86_64 ?????????????????????"
#: en/ArchSpecificx86_64.xml:9(para)
msgid "This section covers any specific information you may need to know about Fedora Core and the x86_64 hardware platform."
-msgstr ""
+msgstr "?????? ????????? ???????????? ????????? ????????? ????????????????????? ??????, ?????? ?????? ?????????????????? ????????? ????????? x86_64 ???????????? ???????????????????????? ?????? ?????????????????? ?????????????????? ?????? ???????????? ?????????"
#: en/ArchSpecificx86_64.xml:11(title)
msgid "x86_64 Hardware Requirements"
-msgstr ""
+msgstr "x86_64 ???????????? ???????????????"
#: en/ArchSpecificx86_64.xml:23(para)
msgid "This list is for 64-bit x86_64 systems:"
-msgstr ""
+msgstr "64-bit x86_64 ??????????????? ?????? ?????? ???????????? ??????:"
#: en/ArchSpecificx86_64.xml:26(para)
msgid "Minimum for text-mode: 128MB"
-msgstr ""
+msgstr "?????????-????????? ?????? ????????????-?????????: 128????????????"
#: en/ArchSpecificx86_64.xml:29(para)
msgid "Minimum for graphical: 256MB"
-msgstr ""
+msgstr "????????????????????? ?????? ????????????-?????????: 256????????????"
#: en/ArchSpecificx86_64.xml:32(para)
msgid "Recommended for graphical: 512MB"
-msgstr ""
+msgstr "????????????????????? ?????? ????????????????????????: 512????????????"
#: en/ArchSpecificx86_64.xml:39(title)
msgid "x86_64 Installation Notes"
-msgstr ""
+msgstr "x86_64 ?????????????????????????????? ???????????????"
#: en/ArchSpecificx86_64.xml:40(para)
msgid "No differences installing for x86_64."
-msgstr ""
+msgstr "x86_64 ?????????????????? ????????? ?????? ????????? ???????????? ???????????? ?????????"
#. 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/ArchSpecificPPC.xml:45(None)
msgid "@@image: '/wiki/ntheme/img/alert.png'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
+msgstr "@@image: '/wiki/ntheme/img/alert.png'; md5=THIS FILE DOESN'T EXIST"
#: en/ArchSpecificPPC.xml:8(title)
msgid "PPC Specifics for Fedora"
-msgstr ""
+msgstr "?????????????????? ?????? PPC ?????????????????????"
#: en/ArchSpecificPPC.xml:9(para)
msgid "This section covers any specific information you may need to know about Fedora Core and the PPC hardware platform."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????? ????????????????????? ??????, ?????? ?????? ????????????????????? ?????????????????? ????????? ????????? PPC ???????????? ???????????????????????? ???????????? ???????????? ?????? ???????????????????????? ?????? ???????????? ?????????"
#: en/ArchSpecificPPC.xml:11(title)
msgid "PPC Hardware Requirements"
-msgstr ""
+msgstr "PPC ???????????? ???????????????"
#: en/ArchSpecificPPC.xml:12(para)
msgid "This section lists the minimum PowerPC (PPC) hardware needed to install Fedora Core 4."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????????????????? ????????? 4 ?????????????????? ????????? ?????? ????????????-????????? ???????????????????????? (PPC) ????????? ???????????? ????????????????????? ?????????"
#: en/ArchSpecificPPC.xml:15(para)
msgid "Minimum: PowerPC G3 / POWER4"
-msgstr ""
+msgstr "????????????-?????????: PowerPC G3 / POWER4"
#: en/ArchSpecificPPC.xml:18(para)
msgid "Fedora Core 5 supports only the ???New World??? generation of Apple Power Macintosh, shipped circa 1999 onwards."
-msgstr ""
+msgstr "?????????????????? ????????? 5 ??????????????? Apple Power Macintosh ?????? ???New World??? ??????????????????, ?????? ?????? circa 1999 ????????? ???????????? ??????????????? ????????? ??????, ?????? ??????????????? ?????????"
#: en/ArchSpecificPPC.xml:21(para)
msgid "Fedora Core also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines."
-msgstr ""
+msgstr "?????????????????? ????????? IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, ????????? IBM Cell ??????????????????????????? ???????????? ????????????????????? ?????? ?????? ??????????????? ?????????"
#: en/ArchSpecificPPC.xml:24(para)
msgid "Recommended for text-mode: 233 MHz G3 or better, 64MiB RAM."
-msgstr ""
+msgstr "????????? ????????? ??????: 233 MHz G3 ????????? ????????????, 64MiB ?????????"
#: en/ArchSpecificPPC.xml:27(para)
msgid "Recommended for graphical: 400 MHz G3 or better, 128MiB RAM."
-msgstr ""
+msgstr "????????????????????? ??????: 400 MHz G3 ????????? ????????????, 128MiB ?????????"
#: en/ArchSpecificPPC.xml:39(title)
msgid "PPC Installation Notes"
-msgstr ""
+msgstr "PPC ?????????????????????????????? ???????????????"
#: en/ArchSpecificPPC.xml:48(phrase)
msgid "/!\\"
-msgstr ""
+msgstr "/!\\"
#: en/ArchSpecificPPC.xml:42(para)
msgid " Currently FC5 Test Release CD 1 and Rescue ISOs do not boot on Mac hardware. See below on booting using boot.iso."
-msgstr ""
+msgstr " ?????????????????? FC5 ???????????? ?????????????????? CD 1 ????????? ??????????????????????????? ISO ????????? ?????????????????? ???????????? ??????????????? ???????????? ????????? boot.iso ?????? ??????????????? ???????????? ????????? ????????? ?????? ????????? ???????????????"
#: en/ArchSpecificPPC.xml:55(para)
msgid "The DVD or first CD of the installation set of Fedora Core is set to be bootable on supported hardware. In addition, a bootable CD images can be found in the images/ directory of the DVD or first CD. These will behave differently according to the hardware:"
@@ -2196,7 +2196,7 @@
#: en/ArchSpecificPPC.xml:58(para)
msgid "Apple Macintosh"
-msgstr ""
+msgstr "????????? ??????????????????????????? (Apple Macintosh)"
#: en/ArchSpecificPPC.xml:61(para)
msgid "The bootloader should automatically boot the appropriate 32-bit or 64-bit installer. Power management support, including sleep and backlight level management, is present in the apmud package, which is in Fedora Extras. Fedora Extras for Fedora Core is configured by default for yum. Following installation, apmud can be installed by running yum install apmud."
@@ -2204,23 +2204,23 @@
#: en/ArchSpecificPPC.xml:66(para)
msgid "64-bit IBM eServer pSeries (POWER4/POWER5)"
-msgstr ""
+msgstr "64-???????????? IBM eServer pSeries (POWER4/POWER5)"
#: en/ArchSpecificPPC.xml:69(para)
msgid "After using OpenFirmware to boot the CD, the bootloader (yaboot) should automatically boot the 64-bit installer."
-msgstr ""
+msgstr "???????????? ?????? ??????????????? ????????????CD ????????? ????????? ????????? ?????? ????????????????????????, ????????? ???????????? (yaboot) ?????????-???????????? ?????? 64-???????????? ????????????????????? ????????????????????????"
#: en/ArchSpecificPPC.xml:74(para)
msgid "32-bit CHRP (IBM RS/6000 and others)"
-msgstr ""
+msgstr "32-bit CHRP (IBM RS/6000 ????????? ?????????)"
#: en/ArchSpecificPPC.xml:77(para)
msgid "After using OpenFirmware to boot the CD, select the 'linux32' boot image at the 'boot:' prompt to start the 32-bit installer. Otherwise, the 64-bit installer is started, which does not work."
-msgstr ""
+msgstr "???????????? ????????? ????????? ????????? ???????????? ???????????????????????? ??????, 'boot:' ???????????? 'linux32' 32-???????????? ????????????????????? ??????????????? ????????? ?????? ??????????????? ???????????? ????????? 64-???????????? ????????????????????? ??????????????????, ?????? ?????? ????????? ???????????? ???????????? ?????????"
#: en/ArchSpecificPPC.xml:82(para)
msgid "Genesi Pegasos II"
-msgstr ""
+msgstr "Genesi Pegasos II"
#: en/ArchSpecificPPC.xml:85(para)
msgid "At the time of writing, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, the network boot image can be used. At the OpenFirmware prompt, enter the command:"
@@ -2229,7 +2229,7 @@
#: en/ArchSpecificPPC.xml:88(screen)
#, no-wrap
msgid "boot cd: /images/netboot/ppc32.img "
-msgstr ""
+msgstr "boot cd: /images/netboot/ppc32.img "
#: en/ArchSpecificPPC.xml:91(para)
msgid "You also need to configure OpenFirmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, you need to set the boot-device and boot-file environment variables appropriately."
@@ -2237,7 +2237,7 @@
#: en/ArchSpecificPPC.xml:96(para)
msgid "Network booting"
-msgstr ""
+msgstr "????????????????????? ????????? ????????????"
#: en/ArchSpecificPPC.xml:99(para)
msgid "There are combined images containing the installer kernel and ramdisk in the images/netboot/ directory of the install tree. These are intended for network booting with TFTP, but can be used in many ways."
@@ -2245,18 +2245,18 @@
#: en/ArchSpecificPPC.xml:100(para)
msgid "yaboot supports tftp booting for IBM eServer pSeries and Apple Macintosh, the use of yaboot is encouraged over the netboot images."
-msgstr ""
+msgstr "yaboot IBM eServer pSeries ????????? Apple Macintosh ?????? tftp ????????? ????????? ?????? ??????????????? ?????? ??????????????? (yaboot) ?????? ??????????????? netboot ??????????????????????????? ??????????????? ?????????????????? ???????????? ???????????? ?????? ?????????"
#: en/ArchSpecific.xml:8(title)
msgid "Archictecture Specific"
-msgstr ""
+msgstr "??????????????? ?????????"
#: en/ArchSpecific.xml:9(para)
msgid "This section provides notes that are specific to the supported hardware architectures of Fedora Core."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????????????????? ????????? ???????????? ??????????????? ???????????? ????????????????????? ???????????? ????????????????????? ??????????????? ?????? ?????????"
#. Put one translator per line, in the form of NAME , YEAR1, YEAR2.
#: en/ArchSpecific.xml:0(None)
msgid "translator-credits"
-msgstr ""
+msgstr "????????????????????? ???????????? ????????? 2006"
From fedora-docs-commits at redhat.com Wed Mar 1 12:53:04 2006
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Wed, 1 Mar 2006 07:53:04 -0500
Subject: install-guide/en fedora-install-guide-beginninginstallation.xml, 1.5,
1.6 fedora-install-guide-diskpartitioning.xml, 1.5,
1.6 fedora-install-guide-intro.xml, 1.5,
1.6 fedora-install-guide.xml, 1.5, 1.6
Message-ID: <200603011253.k21Cr4kx011579@cvs-int.fedora.redhat.com>
Author: bbbush
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11555
Modified Files:
fedora-install-guide-beginninginstallation.xml
fedora-install-guide-diskpartitioning.xml
fedora-install-guide-intro.xml fedora-install-guide.xml
Log Message:
edit some place in order to build
Index: fedora-install-guide-beginninginstallation.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-beginninginstallation.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-beginninginstallation.xml 1 Mar 2006 01:43:14 -0000 1.5
+++ fedora-install-guide-beginninginstallation.xml 1 Mar 2006 12:52:56 -0000 1.6
@@ -8,6 +8,7 @@
]>
+Beginning the Installation
@@ -158,6 +159,7 @@
first stage of the installation program starts.
+ Testing CD and DVD Media
@@ -268,10 +270,6 @@
installing from bad discs on that chance. - PWF.
-->
-
-
-
-
After you test your discs and select
Continue, or if you choose to skip testing,
@@ -369,8 +367,8 @@
-
+
- &BUG-REPORTING;
Background
Index: fedora-install-guide.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide.xml 1 Mar 2006 01:43:14 -0000 1.5
+++ fedora-install-guide.xml 1 Mar 2006 12:52:56 -0000 1.6
@@ -1,6 +1,6 @@
-
@@ -24,7 +24,7 @@
xmlns:xi="http://www.w3.org/2001/XInclude"/>
-
From fedora-docs-commits at redhat.com Wed Mar 1 12:53:21 2006
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Wed, 1 Mar 2006 07:53:21 -0500
Subject: install-guide/po zh_CN.po,1.3,1.4 fedora-install-guide.pot,1.1,1.2
Message-ID: <200603011253.k21CrL7P011600@cvs-int.fedora.redhat.com>
Author: bbbush
Update of /cvs/docs/install-guide/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11553
Modified Files:
zh_CN.po fedora-install-guide.pot
Log Message:
update translation from Xiaofan.Yang
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.3 -r 1.4 zh_CN.po
Index: zh_CN.po
===================================================================
RCS file: /cvs/docs/install-guide/po/zh_CN.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- zh_CN.po 24 Feb 2006 14:22:21 -0000 1.3
+++ zh_CN.po 1 Mar 2006 12:53:13 -0000 1.4
@@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: fedora-install-guide\n"
-"POT-Creation-Date: 2006-02-23 05:10+0800\n"
-"PO-Revision-Date: 2006-02-24 21:14+0800\n"
+"POT-Creation-Date: 2006-02-28 02:49+0800\n"
+"PO-Revision-Date: 2006-02-28 03:44+0800\n"
"Last-Translator: Xiaofan Yang \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
@@ -14,108 +14,95 @@
#. 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:33(None)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:38(None)
msgid "@@image: './figs/upgrade.eps'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-"@@image: './figs/ftp-setup-further.eps'; md5=2163e5cdb427067f3333741f5fbb97ff"
+msgstr "@@image: './figs/upgrade.eps'; md5=THIS FILE DOESN'T EXIST"
#. 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:36(None)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:41(None)
msgid "@@image: './figs/upgrade.png'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-"@@image: './figs/ftp-setup-further.png'; md5=cecd390cce13ac2814a68b9d250d8fbe"
+msgstr "@@image: './figs/upgrade.png'; md5=THIS FILE DOESN'T EXIST"
#. 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:86(None)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:91(None)
msgid "@@image: './figs/upgradebootloader.eps'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-"@@image: 'figs/bootloader-others.eps'; md5=d49e5226f089428eec009a1203853fc0"
+msgstr "@@image: './figs/upgradebootloader.eps'; md5=THIS FILE DOESN'T EXIST"
#. 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:89(None)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:94(None)
msgid "@@image: './figs/upgradebootloader.png'; md5=THIS FILE DOESN'T EXIST"
-msgstr ""
-"@@image: 'figs/bootloader-others.png'; md5=dd2e597c33ba93a3bcf5f70964289fc3"
+msgstr "@@image: './figs/upgradebootloader.png'; md5=THIS FILE DOESN'T EXIST"
-#: en/fedora-install-guide-upgrading.xml:8(title)
+#: en/fedora-install-guide-upgrading.xml:13(title)
msgid "Upgrading an Existing System"
msgstr "?????????????????????"
-#: en/fedora-install-guide-upgrading.xml:10(para)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:15(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 "
+"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 ""
-"?????????????????????????????? &FC; ?????????????????????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"???????????????????????????"
+"?????????????????????????????? &FC; ???????????????????????????????????????????????????????????????????????????"
+"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"?????????????????????"
-#: en/fedora-install-guide-upgrading.xml:22(title)
+#: en/fedora-install-guide-upgrading.xml:27(title)
msgid "Upgrade Examine"
msgstr "????????????"
-#: en/fedora-install-guide-upgrading.xml:24(para)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:29(para)
msgid ""
-"If your system contains a &FC; or &RHL; installation, the following screen "
-"appears:"
-msgstr ""
-"???????????????????????????????????? &FC; ?????? &RHL; ????????????????????????????????????"
+"If your system contains a Fedora Core or Red Hat Linux installation, the "
+"following screen appears:"
+msgstr "???????????????????????????????????? &FC; ?????? &RHL; ????????????????????????????????????"
-#: en/fedora-install-guide-upgrading.xml:30(title)
+#: en/fedora-install-guide-upgrading.xml:35(title)
msgid "Upgrade Examine Screen"
msgstr "??????????????????"
-#: en/fedora-install-guide-upgrading.xml:39(phrase)
+#: en/fedora-install-guide-upgrading.xml:44(phrase)
msgid "Upgrade examine screen."
msgstr "?????????????????????"
-#: en/fedora-install-guide-upgrading.xml:46(para)
+#: en/fedora-install-guide-upgrading.xml:51(para)
msgid ""
"To perform an upgrade of an existing system, choose the appropriate "
"installation from the drop-down list and select Next."
msgstr ""
"?????????????????????????????????????????????????????????????????????????????????????????? "
-"Next???"
+"Next(?????????)???"
-#: en/fedora-install-guide-upgrading.xml:53(title)
+#: en/fedora-install-guide-upgrading.xml:58(title)
msgid "Manually Installed Software"
msgstr "?????????????????????"
-#: en/fedora-install-guide-upgrading.xml:54(para)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:59(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."
+"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 ""
-"??????????????????????????????????????? &FC; ??? &RHL; ??????????????????????????????????????????"
-"?????????????????????????????????????????????????????????????????????????????????????????????"
+"??????????????????????????????????????? &FC; ??? &RHL; ???????????????????????????????????????????????????"
+"????????????????????????????????????????????????????????????????????????????????????"
-#: en/fedora-install-guide-upgrading.xml:65(title)
+#: en/fedora-install-guide-upgrading.xml:70(title)
msgid "Upgrading Boot Loader Configuration"
msgstr "????????????????????????"
-#: en/fedora-install-guide-upgrading.xml:67(para)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:72(para)
msgid ""
"boot loaderupgrading Your completed &FC; installation must be registered in the "
+"indexterm> Your completed Fedora Core installation must be registered in the "
"boot loaderGRUBboot loader to boot properly. A boot loader "
"is software on your machine that locates and starts the operating system. "
@@ -123,52 +110,50 @@
"loaders."
msgstr ""
"boot loaderupgrading ?????? &FC; ??????????????????????????????????????? boot "
+"indexterm> ?????? &FC; ??????????????????????????????????????? boot "
"loaderGRUBboot loader ???????????????????????????????????????????????????????????????????????????????????????????????????"
-"?????????????????????????????????????????? ??????????????????"
-"??????"
+"?????????????????????????????????????????? ??????????????????"
+"???????????????????????????"
-#: en/fedora-install-guide-upgrading.xml:83(title)
+#: en/fedora-install-guide-upgrading.xml:88(title)
msgid "Upgrade Bootloader Screen"
msgstr "??????????????????????????????"
-#: en/fedora-install-guide-upgrading.xml:92(phrase)
+#: en/fedora-install-guide-upgrading.xml:97(phrase)
msgid "Upgrade bootloader screen."
msgstr "?????????????????????????????????"
-#: en/fedora-install-guide-upgrading.xml:99(para)
-#, fuzzy
+#: en/fedora-install-guide-upgrading.xml:104(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 Update boot loader "
+"installation system can modify it to load the new Fedora Core system. To "
+"update the existing Linux boot loader, select Update boot loader "
"configuration. This is the default behavior when you upgrade an "
-"existing &FC; or &RHL; installation."
+"existing Fedora Core or Red Hat Linux installation."
msgstr ""
[...8215 lines suppressed...]
#~ msgid "2005"
#~ msgstr "2005"
-#~ msgid "&FORMAL-RHI;"
-#~ msgstr "&FORMAL-RHI;"
+#~ msgid "&FORMAL-RHI;"
+#~ msgstr "&FORMAL-RHI;"
#~ msgid "Stuart Ellis"
#~ msgstr "Stuart Ellis"
@@ -7138,7 +6885,7 @@
#~ " &LEGALNOTICE; "
+#~ "> &LEGALNOTICE; "
#~ " &LEGALNOTICE; "
+#~ "> &LEGALNOTICE; "
#~ " ????????????????????????"
#~ msgid ""
-#~ "To install &FC; from discs, you need five installation CDs, or the "
+#~ "To install &FC; from discs, you need five installation CDs, or the "
#~ "installation DVD. There are separate disc sets for each supported "
-#~ "architecture. Currently, &FC; supports the "
+#~ "architecture. Currently, &FC; supports the "
#~ "i386, ppc, and "
#~ "x86_64 architectures. These architectures are "
#~ "described below:"
#~ msgstr ""
-#~ "?????????????????? &FC;????????????????????????????????????????????? DVD ???????????????????????????"
-#~ "??? architecture(??????)??????????????????????????????????????????"
-#~ "&FC; ?????? i386, ppc, ??? "
+#~ "?????????????????? &FC;????????????????????????????????????????????? DVD ?????????????????????????????? "
+#~ "architecture(??????)??????????????????????????????????????????&FC; "
+#~ "?????? i386, ppc, ??? "
#~ "x86_64 ???????????????????????????????????????"
#~ msgid ""
-#~ "To begin installation of &FC;, boot the computer from the boot media. "
-#~ "You may install from CD or DVD discs, USB pen drives, hard drives, or "
-#~ "network servers."
+#~ "To begin installation of &FC;, boot the computer from the boot media. You "
+#~ "may install from CD or DVD discs, USB pen drives, hard drives, or network "
+#~ "servers."
#~ msgstr ""
-#~ "??????????????? &FC;?????????????????????????????????????????????????????? CD ??? DVD ?????????"
-#~ "USB ?????????????????????????????????????????????????????????"
+#~ "??????????????? &FC;?????????????????????????????????????????????????????? CD ??? DVD ?????????USB ???"
+#~ "??????????????????????????????????????????????????????"
#~ msgid "Booting from Disc"
#~ msgstr "???????????????"
@@ -7293,14 +7040,14 @@
#~ msgid ""
#~ "To boot from the disc, but install from another device or a network "
#~ "server, use the linux askmethod command at the "
-#~ "boot: prompt. &FC; also includes a boot-only CD for "
-#~ "this purpose, which is stored on the first &FC; installation disc as "
-#~ "an ISO file, images/boot.iso."
+#~ "boot: prompt. &FC; also includes a boot-only CD for this "
+#~ "purpose, which is stored on the first &FC; installation disc as an ISO "
+#~ "file, images/boot.iso."
#~ msgstr ""
#~ "???????????????????????????????????????????????????????????????????????? boot: ???"
-#~ "??????????????? linux askmethod???&FC; ?????????????????????"
-#~ "????????????????????? CD????????????????????? ISO ???????????????????????? &FC; ??????????????????"
-#~ "?????????????????? images/boot.iso???"
+#~ "??????????????? linux askmethod???&FC; ???????????????????????????"
+#~ "??????????????? CD????????????????????? ISO ???????????????????????? &FC; ??????????????????????????????"
+#~ "?????? images/boot.iso???"
#~ msgid "Using Other Removable Media"
#~ msgstr "???????????????????????????"
@@ -7401,8 +7148,8 @@
#~ msgstr "???????????????????????????????????????????????????"
#~ msgid ""
-#~ "Uses only the unpartitioned space on the hard disk(s) to install &FC;"
-#~ msgstr "????????????????????? ??????????????? ????????? &FC;"
+#~ "Uses only the unpartitioned space on the hard disk(s) to install &FC;"
+#~ msgstr "????????????????????? ??????????????? ????????? &FC;"
#~ msgid "Select the desired option."
#~ msgstr "????????????????????????"
@@ -7477,13 +7224,13 @@
#~ msgstr "????????????"
#~ msgid ""
-#~ "The default security configuration for &FC; protects your system "
-#~ "without restricting any of the functions of a desktop or laptop computer. "
-#~ "If you are installing a server, you may need to alter these settings so "
-#~ "others can access the system."
+#~ "The default security configuration for &FC; protects your system without "
+#~ "restricting any of the functions of a desktop or laptop computer. If you "
+#~ "are installing a server, you may need to alter these settings so others "
+#~ "can access the system."
#~ msgstr ""
-#~ "&FC; ?????????????????????????????????????????????????????????????????????????????????????????????"
-#~ "?????????????????????????????????????????????????????????????????????????????????????????????"
+#~ "&FC; ??????????????????????????????????????????????????????????????????????????????????????????????????????"
+#~ "????????????????????????????????????????????????????????????????????????????????????"
#~ msgid "Security configuration screen."
#~ msgstr "?????????????????????"
@@ -7517,22 +7264,22 @@
#~ msgid ""
#~ "This screen allows you to load prepared discs for installing third-party "
#~ "software. However, you cannot use it to install additional packages from "
-#~ "the &FC; discs."
+#~ "the &FC; discs."
#~ msgstr ""
#~ "???????????????????????????????????????????????????????????????????????????????????????????????????????????? "
-#~ "&FC; ??????????????????????????????"
+#~ "&FC; ??????????????????????????????"
#~ msgid "Adding Software"
#~ msgstr "????????????"
#~ msgid ""
-#~ "To add software packages from the &FC; discs, use the "
+#~ "To add software packages from the &FC; discs, use the "
#~ "Package Manager utility after you log in. From "
#~ "the main menu, select DesktopSystem SettingsAdd/Remove "
#~ "Applications."
#~ msgstr ""
-#~ "????????? &FC; ???????????????????????????????????????????????? Package "
+#~ "????????? &FC; ???????????????????????????????????????????????? Package "
#~ "Manager ??????????????????????????????????????? "
#~ "DesktopSystem SettingsAdd/Remove Applicationsinstallation typeinstallation type is a label that "
-#~ "roughly describes how you will use your &FED; system. Several "
-#~ "installation types are already defined in the &FC; installation "
-#~ "program. Choose the appropriate installation type to streamline the "
-#~ "installation process if you are a beginner. The installation program "
-#~ "makes some choices for you based on the type you select. These choices "
-#~ "include partitioning of your hard disks, and software packages to be "
-#~ "installed. All installation types allow you to customize these selections."
+#~ "roughly describes how you will use your &FED; system. Several "
+#~ "installation types are already defined in the &FC; installation program. "
+#~ "Choose the appropriate installation type to streamline the installation "
+#~ "process if you are a beginner. The installation program makes some "
+#~ "choices for you based on the type you select. These choices include "
+#~ "partitioning of your hard disks, and software packages to be installed. "
+#~ "All installation types allow you to customize these selections."
#~ msgstr ""
#~ "installation typeinstallation type ?????????????????????????????????"
-#~ "????????????????????????????????? &FED; ????????????????????????????????????????????????????????????"
-#~ "???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-#~ "???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-#~ "????????????"
+#~ "????????????????????????????????? &FED; ??????????????????????????????????????????????????????????????????"
+#~ "???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+#~ "???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+#~ "??????"
#~ msgid "Choosing an Installation Type"
#~ msgstr "????????????????????????"
@@ -7685,19 +7432,19 @@
#~ msgid "You should also have the following documents:"
#~ msgstr "?????????????????????????????????"
-#~ msgid "a copy of this &IG;"
-#~ msgstr "?????? &IG; ???????????????"
+#~ msgid "a copy of this &IG;"
+#~ msgstr "?????? &IG; ???????????????"
#~ msgid ""
-#~ "&FC; includes software for a complete range of network services. To "
+#~ "&FC; includes software for a complete range of network services. To "
#~ "install a system with the most common network services, select the "
#~ "Server installation type during the installation. "
#~ "Refer to for more information. You "
#~ "may also select individual software packages during installation, or "
#~ "install them later."
#~ msgstr ""
-#~ "&FC; ????????????????????????????????????????????????????????????????????????????????????????????????"
-#~ "???????????????????????????????????? Server ????????????????????? Server ????????????????????? ??????????????????????????????????????????????????????????????????"
#~ "??????????????????????????????????????????"
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.1 -r 1.2 fedora-install-guide.pot
Index: fedora-install-guide.pot
===================================================================
RCS file: /cvs/docs/install-guide/po/fedora-install-guide.pot,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fedora-install-guide.pot 28 Feb 2006 12:42:02 -0000 1.1
+++ fedora-install-guide.pot 1 Mar 2006 12:53:14 -0000 1.2
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-02-28 06:40-0600\n"
+"POT-Creation-Date: 2006-02-28 02:49+0800\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
@@ -11,3539 +11,3593 @@
#. 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:33(None)
+#: en/fedora-install-guide-upgrading.xml:38(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:36(None)
+#: en/fedora-install-guide-upgrading.xml:41(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:86(None)
+#: en/fedora-install-guide-upgrading.xml:91(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:89(None)
+#: en/fedora-install-guide-upgrading.xml:94(None)
msgid "@@image: './figs/upgradebootloader.png'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:8(title)
+#: en/fedora-install-guide-upgrading.xml:13(title)
msgid "Upgrading an Existing System"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:10(para)
-msgid "The installation system automatically detects any existing installation of . 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/fedora-install-guide-upgrading.xml:15(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:22(title)
+#: en/fedora-install-guide-upgrading.xml:27(title)
msgid "Upgrade Examine"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:24(para)
-msgid "If your system contains a or installation, the following screen appears:"
+#: en/fedora-install-guide-upgrading.xml:29(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:30(title)
+#: en/fedora-install-guide-upgrading.xml:35(title)
msgid "Upgrade Examine Screen"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:39(phrase)
+#: en/fedora-install-guide-upgrading.xml:44(phrase)
msgid "Upgrade examine screen."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:46(para)
+#: en/fedora-install-guide-upgrading.xml:51(para)
msgid "To perform an upgrade of an existing system, choose the appropriate installation from the drop-down list and select Next."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:53(title)
+#: en/fedora-install-guide-upgrading.xml:58(title)
msgid "Manually Installed Software"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:54(para)
-msgid "Software which you have installed manually on your existing or 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/fedora-install-guide-upgrading.xml:59(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:65(title)
+#: en/fedora-install-guide-upgrading.xml:70(title)
msgid "Upgrading Boot Loader Configuration"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:67(para)
-msgid "boot loaderupgrading Your completed installation must be registered in the boot loaderGRUBboot loader to boot properly. A boot loader is software on your machine that locates and starts the operating system. Refer to for more information about boot loaders."
+#: en/fedora-install-guide-upgrading.xml:72(para)
+msgid "boot loaderupgrading Your completed Fedora Core installation must be registered in the boot loaderGRUBboot loader to boot properly. A boot loader is software on your machine that locates and starts the operating system. Refer to for more information about boot loaders."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:83(title)
+#: en/fedora-install-guide-upgrading.xml:88(title)
msgid "Upgrade Bootloader Screen"
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:92(phrase)
+#: en/fedora-install-guide-upgrading.xml:97(phrase)
msgid "Upgrade bootloader screen."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:99(para)
-msgid "If the existing boot loader was installed by a Linux distribution, the installation system can modify it to load the new system. To update the existing Linux boot loader, select Update boot loader configuration. This is the default behavior when you upgrade an existing or installation."
+#: en/fedora-install-guide-upgrading.xml:104(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 Update boot loader configuration. This is the default behavior when you upgrade an existing Fedora Core or Red Hat Linux installation."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:107(para)
-msgid "GRUB is the standard boot loader for . If your machine uses another boot loader, such as BootMagic, System Commander, or the loader installed by Microsoft Windows, then the installation system cannot update it. In this case, select Skip boot loader updating. When the installation process completes, refer to the documentation for your product for assistance."
+#: en/fedora-install-guide-upgrading.xml:112(para)
+msgid "GRUB is the standard boot loader for Fedora. If your machine uses another boot loader, such as BootMagic, System Commander, or the loader installed by Microsoft Windows, then the Fedora installation system cannot update it. In this case, select Skip boot loader updating. When the installation process completes, refer to the documentation for your product for assistance."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:118(para)
+#: en/fedora-install-guide-upgrading.xml:123(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 Create new boot loader configuration to remove the existing boot loader and install GRUB."
msgstr ""
-#: en/fedora-install-guide-upgrading.xml:128(para)
+#: en/fedora-install-guide-upgrading.xml:133(para)
msgid "After you make your selection, click Next 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:28(None)
+#: en/fedora-install-guide-timezone.xml:33(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.
#. It doesn't matter what you translate it to: it's not used at all.
-#: en/fedora-install-guide-timezone.xml:31(None)
+#: en/fedora-install-guide-timezone.xml:36(None)
msgid "@@image: './figs/timezone.png'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
-#: en/fedora-install-guide-timezone.xml:8(title)
+#: en/fedora-install-guide-timezone.xml:13(title)
msgid "Time Zone Selection"
msgstr ""
-#: en/fedora-install-guide-timezone.xml:9(para)
+#: en/fedora-install-guide-timezone.xml:14(para)
msgid "This screen allows you to specify the correct time zone for the location of your computer. Specify a time zone even if you plan to use NTP (Network Time Protocol) NTP (Network Time Protocol) to maintain the accuracy of the system clock."
msgstr ""
-#: en/fedora-install-guide-timezone.xml:18(title)
+#: en/fedora-install-guide-timezone.xml:23(title)
msgid "Selecting a Time Zone"
msgstr ""
-#: en/fedora-install-guide-timezone.xml:20(para)
-msgid "displays on the screen two methods for selecting the time zone."
+#: en/fedora-install-guide-timezone.xml:25(para)
+msgid "Fedora displays on the screen two methods for selecting the time zone."
msgstr ""
-#: en/fedora-install-guide-timezone.xml:25(title)
+#: en/fedora-install-guide-timezone.xml:30(title)
msgid "Time Zone Selection Screen"
msgstr ""
-#: en/fedora-install-guide-timezone.xml:34(phrase)
+#: en/fedora-install-guide-timezone.xml:39(phrase)
msgid "Time zone selection screen."
msgstr ""
-#: en/fedora-install-guide-timezone.xml:40(para)
+#: en/fedora-install-guide-timezone.xml:45(para)
msgid "To select a time zone using the map, first place your mouse pointer over your region on the map. Click once to magnify that region on the map. Next, select the yellow dot that represents the city nearest to your location. Once you select a dot, it becomes a red X to indicate your selection."
msgstr ""
-#: en/fedora-install-guide-timezone.xml:48(para)
+#: en/fedora-install-guide-timezone.xml:53(para)
msgid "To select a time zone using the list, select the name of the city nearest to your location. The cities are listed in alphabetical order."
msgstr ""
-#: en/fedora-install-guide-timezone.xml:55(title)
+#: en/fedora-install-guide-timezone.xml:60(title)
msgid "Universal Co-ordinated Time (UTC)"
msgstr ""
-#: en/fedora-install-guide-timezone.xml:57(para)
+#: en/fedora-install-guide-timezone.xml:62(para)
[...4221 lines suppressed...]
-#: en/fedora-install-guide-adminoptions.xml:955(option)
+#: en/fedora-install-guide-adminoptions.xml:960(option)
msgid "nodmraid"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:961(para)
+#: en/fedora-install-guide-adminoptions.xml:966(para)
msgid "Disable Firewire device detection"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:967(option)
+#: en/fedora-install-guide-adminoptions.xml:972(option)
msgid "nofirewire"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:973(para)
+#: en/fedora-install-guide-adminoptions.xml:978(para)
msgid "Disable parallel port detection"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:979(option)
+#: en/fedora-install-guide-adminoptions.xml:984(option)
msgid "noparport"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:985(para)
+#: en/fedora-install-guide-adminoptions.xml:990(para)
msgid "Disable PC Card (PCMCIA) device detection"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:991(option)
+#: en/fedora-install-guide-adminoptions.xml:996(option)
msgid "nopcmcia"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:997(para)
+#: en/fedora-install-guide-adminoptions.xml:1002(para)
msgid "Disable USB storage device detection"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1003(option)
+#: en/fedora-install-guide-adminoptions.xml:1008(option)
msgid "nousbstorage"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1009(para)
+#: en/fedora-install-guide-adminoptions.xml:1014(para)
msgid "Disable all USB device detection"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1015(option)
+#: en/fedora-install-guide-adminoptions.xml:1020(option)
msgid "nousb"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1021(para)
+#: en/fedora-install-guide-adminoptions.xml:1026(para)
msgid "Force Firewire device detection"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1027(option)
+#: en/fedora-install-guide-adminoptions.xml:1032(option)
msgid "firewire"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1033(para)
+#: en/fedora-install-guide-adminoptions.xml:1038(para)
msgid "Prompt user for ISA device configuration"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1039(option)
+#: en/fedora-install-guide-adminoptions.xml:1044(option)
msgid "isa"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1049(title)
+#: en/fedora-install-guide-adminoptions.xml:1054(title)
msgid "Using the Maintenance Boot Modes"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1052(title)
+#: en/fedora-install-guide-adminoptions.xml:1057(title)
msgid "Loading the Memory (RAM) Testing Mode"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1054(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 for the first time, even if it has previously run other operating systems."
+#: en/fedora-install-guide-adminoptions.xml:1059(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:1063(para)
+#: en/fedora-install-guide-adminoptions.xml:1068(para)
msgid "To boot your computer in memory testing mode memory testing mode, enter memtest86 at the boot: prompt. The first test starts immediately. By default, memtest86 carries out a total of ten tests."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1075(para)
+#: en/fedora-install-guide-adminoptions.xml:1080(para)
msgid "To halt the tests and reboot your computer, enter Esc at any time."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1082(title)
+#: en/fedora-install-guide-adminoptions.xml:1087(title)
msgid "Booting Your Computer with the Rescue Mode"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1084(primary)
+#: en/fedora-install-guide-adminoptions.xml:1089(primary)
msgid "rescue mode"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1086(para)
-msgid "You may boot a command-line Linux system from either a rescue discs rescue disc or the first installation disc, without installing on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair an installed system."
+#: en/fedora-install-guide-adminoptions.xml:1091(para)
+msgid "You may boot a command-line Linux system from either a rescue discs 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 an installed system."
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1097(para)
+#: en/fedora-install-guide-adminoptions.xml:1102(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:1102(userinput)
+#: en/fedora-install-guide-adminoptions.xml:1107(userinput)
#, no-wrap
msgid "linux rescue"
msgstr ""
-#: en/fedora-install-guide-adminoptions.xml:1104(para)
+#: en/fedora-install-guide-adminoptions.xml:1109(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:1111(para)
+#: en/fedora-install-guide-adminoptions.xml:1116(para)
msgid "By default, rescue mode attaches an existing operating system to the rescue system under the directory /mnt/sysimage/."
msgstr ""
-#: en/fedora-install-guide-acknowledgements.xml:8(title)
+#: en/fedora-install-guide-acknowledgements.xml:13(title)
msgid "Acknowledgements"
msgstr ""
-#: en/fedora-install-guide-acknowledgements.xml:9(para)
+#: en/fedora-install-guide-acknowledgements.xml:14(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."
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:33(None)
+#: en/fedora-install-guide-abouttoinstall.xml:38(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:36(None)
+#: en/fedora-install-guide-abouttoinstall.xml:41(None)
msgid "@@image: './figs/abouttoinstall.png'; md5=THIS FILE DOESN'T EXIST"
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:8(title)
+#: en/fedora-install-guide-abouttoinstall.xml:13(title)
msgid "About to Install"
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:10(para)
-msgid "No changes are made to your computer until you click the Next button. If you abort the installation process after that point, the system will be incomplete and unusable. To return to previous screens to make different choices, select Back. To abort the installation, turn off the computer."
+#: en/fedora-install-guide-abouttoinstall.xml:15(para)
+msgid "No changes are made to your computer until you click the Next 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 Back. To abort the installation, turn off the computer."
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:20(title)
+#: en/fedora-install-guide-abouttoinstall.xml:25(title)
msgid "Aborting Installation"
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:21(para)
-msgid "In certain situations, you may be unable to return to previous screens. notifies you of this restriction and allows you to abort the installation program. You may reboot with the installation media to start over."
+#: en/fedora-install-guide-abouttoinstall.xml:26(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:30(title)
+#: en/fedora-install-guide-abouttoinstall.xml:35(title)
msgid "About to Install Screen"
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:39(phrase)
+#: en/fedora-install-guide-abouttoinstall.xml:44(phrase)
msgid "About to install screen."
msgstr ""
-#: en/fedora-install-guide-abouttoinstall.xml:46(para)
+#: en/fedora-install-guide-abouttoinstall.xml:51(para)
msgid "Click Next to begin the installation."
msgstr ""
From fedora-docs-commits at redhat.com Wed Mar 1 13:03:35 2006
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Wed, 1 Mar 2006 08:03:35 -0500
Subject: install-guide/po zh_CN.po,1.4,1.5
Message-ID: <200603011303.k21D3ZrW013564@cvs-int.fedora.redhat.com>
Author: bbbush
Update of /cvs/docs/install-guide/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13541
Modified Files:
zh_CN.po
Log Message:
fix build
Index: zh_CN.po
===================================================================
RCS file: /cvs/docs/install-guide/po/zh_CN.po,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- zh_CN.po 1 Mar 2006 12:53:13 -0000 1.4
+++ zh_CN.po 1 Mar 2006 13:03:22 -0000 1.5
@@ -3401,8 +3401,8 @@
"ext3file systemfile systemext3ext3 ????????????????????? LVM ???????????????????????????????????????????????????"
+"secondary>ext3"
+" ????????????????????? LVM ???????????????????????????????????????????????????"
"??????????????????????????????"
#: en/fedora-install-guide-diskpartitioning.xml:289(title)
@@ -3439,7 +3439,7 @@
"????????????????????????????????? LVMvolume "
"groupvolume group ???????????????"
"??????????????????????????????????????????????????????????????? LVMlogical volumelogical "
+"primary>logical volumelogical "
"volumes ????????????????????????????????????????????????????????????????????????????????????"
"????????????????????? ext3??????????????????"
"?????????"
@@ -3692,8 +3692,8 @@
"vfatfile systemfile systemvfatvfat (FAT16 "
+"secondary>vfat"
+"(FAT16 "
"??? FAT32) ???????????????????????????"
"??????"
From fedora-docs-commits at redhat.com Wed Mar 1 13:07:19 2006
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Wed, 1 Mar 2006 08:07:19 -0500
Subject: install-guide/en fedora-install-guide-intro.xml,1.6,1.7
Message-ID: <200603011307.k21D7J0R013609@cvs-int.fedora.redhat.com>
Author: bbbush
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13581
Modified Files:
fedora-install-guide-intro.xml
Log Message:
revert and copy&paste local entities
Index: fedora-install-guide-intro.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-intro.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-intro.xml 1 Mar 2006 12:52:56 -0000 1.6
+++ fedora-install-guide-intro.xml 1 Mar 2006 13:07:10 -0000 1.7
@@ -5,7 +5,17 @@
%FEDORA-ENTITIES;
+
+
+
+
+
+
+
+
+
+
]>
@@ -43,6 +53,7 @@
they exist, do not reference them. - PWF.] -->
+ &BUG-REPORTING;
Background
From fedora-docs-commits at redhat.com Wed Mar 1 13:47:49 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Wed, 1 Mar 2006 08:47:49 -0500
Subject: docs-common/common/entities it.po,1.8,1.9
Message-ID: <200603011347.k21DlnLp013912@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/docs-common/common/entities
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13869/docs-common/common/entities
Modified Files:
it.po
Log Message:
completed translation of entities/it.po and updated some common/*.-it.xml
Index: it.po
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/it.po,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- it.po 1 Mar 2006 01:14:00 -0000 1.8
+++ it.po 1 Mar 2006 13:47:41 -0000 1.9
@@ -1,234 +1,239 @@
+# translation of it.po to Italiano
+# Francesco Tombolini , 2006.
msgid ""
msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
+"Project-Id-Version: it\n"
"POT-Creation-Date: 2006-02-28 20:10-0500\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME \n"
-"Language-Team: LANGUAGE \n"
+"PO-Revision-Date: 2006-03-01 14:45+0100\n"
+"Last-Translator: Francesco Tombolini \n"
+"Language-Team: Italiano \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"
+"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: entities-en.xml:6(title)
msgid ""
"These common entities are useful shorthand terms and names, which may be "
"subject to change at anytime. This is an important value the the entity "
"provides: a single location to update terms and common names."
-msgstr ""
+msgstr "Queste entit?? comuni sono utili abbreviazioni di termini e nomi, che potrebbero essere soggette a cambiamento in qualsiasi momento. Questo ?? il valore importante che le entit?? forniscono: Una singola locazione per aggiornare termini e nomi comuni."
#: entities-en.xml:14(comment) entities-en.xml:18(comment)
msgid "Generic root term"
-msgstr ""
+msgstr "Tremine generico root"
#: entities-en.xml:15(text)
msgid "Fedora"
-msgstr ""
+msgstr "Fedora"
#: entities-en.xml:19(text)
msgid "Core"
-msgstr ""
+msgstr "Core"
#: entities-en.xml:22(comment)
msgid "Generic main project name"
-msgstr ""
+msgstr "Nome generico del progetto principale"
#: entities-en.xml:26(comment)
msgid "Legacy Entity"
-msgstr ""
+msgstr "Entit?? obsolete"
#: entities-en.xml:30(comment)
msgid "Short project name"
-msgstr ""
+msgstr "Nome breve del progetto"
#: entities-en.xml:31(text)
msgid "FC"
-msgstr ""
+msgstr "FC"
#: entities-en.xml:34(comment)
msgid "Generic overall project name"
-msgstr ""
+msgstr "Nome generico del progetto complessivo"
#: entities-en.xml:35(text)
msgid "
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 an
- installed system.
+ functions of a running Linux system to modify or repair systems that are already installed on your computer.
Index: fedora-install-guide-diskpartitioning.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-diskpartitioning.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-diskpartitioning.xml 1 Mar 2006 12:52:56 -0000 1.6
+++ fedora-install-guide-diskpartitioning.xml 2 Mar 2006 01:24:58 -0000 1.7
@@ -29,7 +29,7 @@
RAID facilities enable a group, or array,
of drives to act as a single device. Configure any RAID functions
provided by your mainboard, or attached controller cards, before
- you install &FC;. Active RAID arrays appear as one drive.
+ you install &FC;. Each active RAID array appears as one drive.
@@ -134,7 +134,7 @@
customize the partition layout. If you choose to either
Create custom layout, or Review and
modify partitioning layout, proceed to
- .
+ .
Index: fedora-install-guide-firstboot.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-firstboot.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-firstboot.xml 1 Mar 2006 01:43:14 -0000 1.5
+++ fedora-install-guide-firstboot.xml 2 Mar 2006 01:24:58 -0000 1.6
@@ -129,6 +129,13 @@
check box next to the service name.
+
+ SSH Provides Immediate Remote Access
+
+ By default, &FED; installs and runs the SSH service. If you enable SSH access on this screen the user and root accounts may be used to access the system remotely.
+
+
+
To enable access to other services, enter the required ports in
the Other ports: field. For each port, you
Index: fedora-install-guide-locale.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-locale.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-locale.xml 1 Mar 2006 01:43:14 -0000 1.5
+++ fedora-install-guide-locale.xml 2 Mar 2006 01:24:58 -0000 1.6
@@ -20,6 +20,7 @@
+ Network Installations
Network installations with HTTP and FTP always use text screens on
systems with less than 128Mb of memory.
Index: fedora-install-guide-other-instmethods.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-other-instmethods.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-other-instmethods.xml 1 Mar 2006 01:43:14 -0000 1.5
+++ fedora-install-guide-other-instmethods.xml 2 Mar 2006 01:24:58 -0000 1.6
@@ -156,6 +156,15 @@
+
+
+ Large Download
+
+
+ Network installations download the main installation program from the server that you specify. The graphical installation program is over 60 Mb in size. Computers with a slow network connection may take several minutes to download this file.
+
+
+
Index: fedora-install-guide-packageselection.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-packageselection.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fedora-install-guide-packageselection.xml 1 Mar 2006 01:43:14 -0000 1.5
+++ fedora-install-guide-packageselection.xml 2 Mar 2006 01:24:58 -0000 1.6
@@ -117,6 +117,11 @@
remote access through SSH (Secure SHell)
+
+
+ resource advertising through mDNS (multicast DNS)
+
+
From fedora-docs-commits at redhat.com Thu Mar 2 01:25:00 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Wed, 1 Mar 2006 20:25:00 -0500
Subject: install-guide Makefile,1.20,1.21
Message-ID: <200603020125.k221PUH8011755@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11525
Modified Files:
Makefile
Log Message:
- Fixed admonition title in Locale section.
- Added note that the second stage installer may take a while to download from network servers (this file is now 67 Mb !).
- Added mDNS to the list of mandatory services installed with Core.
- Added admonition that opening the SSH port provides immediate remote access, since the service is automatically live.
- Added admonition to explain "isa" boot option.
Index: Makefile
===================================================================
RCS file: /cvs/docs/install-guide/Makefile,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- Makefile 24 Feb 2006 14:22:10 -0000 1.20
+++ Makefile 2 Mar 2006 01:24:50 -0000 1.21
@@ -28,7 +28,8 @@
define XMLFILES_template
-XMLFILES-$(1)= $(1)/${DOCBASE}.xml \
+XMLFILES-$(1)= $(1)/entities.xml \
+ $(1)/${DOCBASE}.xml \
$(1)/${DOCBASE}-abouttoinstall.xml \
$(1)/${DOCBASE}-acknowledgements.xml \
$(1)/${DOCBASE}-adminoptions.xml \
From fedora-docs-commits at redhat.com Thu Mar 2 01:50:13 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 1 Mar 2006 20:50:13 -0500
Subject: docs-common Makefile.common,1.84,1.85
Message-ID: <200603020150.k221oDKn012126@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12081/docs-common
Modified Files:
Makefile.common
Log Message:
Fixed depandancies so that ${LANG}/fdp-info.xml and
${LANG}/${DOC_ENTITIES}.ent both get built
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -r1.84 -r1.85
--- Makefile.common 1 Mar 2006 23:41:43 -0000 1.84
+++ Makefile.common 2 Mar 2006 01:50:06 -0000 1.85
@@ -165,6 +165,7 @@
# Append per-document entities file if any
ifneq "${DOC_ENTITIES}" ""
$(foreach L, ${LANGUAGES}, $(eval XMLFILES-${L}+=${L}/${DOC_ENTITIES}.xml))
+$(foreach L, ${LANGUAGES}, $(eval XMLDEPFILES-${L}+=${L}/${DOC_ENTITIES}.ent))
endif
$(foreach L, ${LANGUAGES},$(eval $(call XMLFILENAME_template,${L})))
@@ -172,6 +173,12 @@
#########################################################################
#########################################################################
+# Define ${XMLDEPFILES-${LANG}} to be the list of non-archived dependant
+# files needed in addition to ${XMLFILES-${LANG}}.
+$(foreach L, ${LANGUAGES}, $(eval XMLDEPFILES-${L}+=${L}/fdp-info.xml))
+#########################################################################
+
+#########################################################################
TFMT="%-31s -- %s\n"
#########################################################################
@@ -237,7 +244,7 @@
define HTML_template
.PHONY: html-${1}
html-$(1):: ${DOCBASE}-$(1)/index.html
-${DOCBASE}-$(1)/index.html:: ${XMLFILES-${1}} $(1)/fdp-info.xml set-locale-${1}
+${DOCBASE}-$(1)/index.html:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
LANG=$(1).UTF-8 ${XMLTO} html -x $(XSLHTML) -o $(DOCBASE)-$(1) $(1)/$(DOCBASE).xml
mkdir -p $(DOCBASE)-$(1)/stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png $(DOCBASE)-$(1)/stylesheet-images
@@ -272,7 +279,7 @@
html-nochunks-$(1):: ${DOCBASE}-$(1).html
-${DOCBASE}-$(1).html:: ${XMLFILES-${1}} $(1)/fdp-info.xml set-locale-${1}
+${DOCBASE}-$(1).html:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
LANG=${1}.UTF-8 ${XMLTO} html-nochunks -x $(XSLHTMLNOCHUNKS) $(1)/$(DOCBASE).xml
mv $(DOCBASE).html $(DOCBASE)-$(1).html
mkdir -p stylesheet-images/
@@ -332,7 +339,7 @@
pdf-$(1):: ${DOCBASE}-$(1).pdf
-${DOCBASE}-$(1).pdf:: ${XMLFILES-${1}} ${1}/fdp-info.xml set-locale-${1}
+${DOCBASE}-$(1).pdf:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
LANG=${1}.UTF-8 ${XMLTO} pdf -x $(XSLPDF) $(1)/$(DOCBASE).xml
mv -f ${DOCBASE}.pdf ${DOCBASE}-${1}.pdf
@@ -357,7 +364,7 @@
txt-$(1) text-$(1):: ${DOCBASE}-$(1).txt
-${DOCBASE}-$(1).txt:: ${XMLFILES-${1}} ${1}/fdp-info.xml set-locale-${1}
+${DOCBASE}-$(1).txt:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
${XMLLINT} ${XMLLINTOPT} $(1)/$(DOCBASE).xml > $(1)/$(DOCBASE).lint.xml
${XSLTPROC} $(FDPDIR)/docs-common/packaging/strip-for-txt.xsl \
$(1)/$(DOCBASE).lint.xml > $(1)/$(DOCBASE).stripped.xml
From fedora-docs-commits at redhat.com Thu Mar 2 01:50:08 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 1 Mar 2006 20:50:08 -0500
Subject: example-tutorial/en example-tutorial.xml,1.5,1.6
Message-ID: <200603020150.k221ocPF012134@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12081/example-tutorial/en
Modified Files:
example-tutorial.xml
Log Message:
Fixed depandancies so that ${LANG}/fdp-info.xml and
${LANG}/${DOC_ENTITIES}.ent both get built
Index: example-tutorial.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/en/example-tutorial.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- example-tutorial.xml 1 Mar 2006 23:40:06 -0000 1.5
+++ example-tutorial.xml 2 Mar 2006 01:50:00 -0000 1.6
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOCUMENT-ENTITIES;
From fedora-docs-commits at redhat.com Thu Mar 2 02:20:06 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 1 Mar 2006 21:20:06 -0500
Subject: example-tutorial/po de.po,1.3,1.4 example-tutorial.pot,1.3,1.4
Message-ID: <200603020220.k222K6iR014278@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14162/po
Modified Files:
de.po example-tutorial.pot
Log Message:
Added per-document entities example files.
Index: de.po
===================================================================
RCS file: /cvs/docs/example-tutorial/po/de.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- de.po 1 Mar 2006 23:40:12 -0000 1.3
+++ de.po 2 Mar 2006 02:19:58 -0000 1.4
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-01 17:33-0600\n"
+"POT-Creation-Date: 2006-03-01 20:16-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
@@ -14,11 +14,11 @@
msgstr ""
#: en/entities.xml:10(comment)
-msgid "Name of our document"
+msgid "A per-document entity"
msgstr ""
-#: en/entities.xml:11(text)
-msgid "Pharphrompsober"
+#: en/entities.xml:11(wordasword)
+msgid "Per-document Entity"
msgstr ""
#: en/para.xml:10(para)
@@ -31,64 +31,68 @@
msgid "WHERE IS MY FDP-INFO, DUDE"
msgstr ""
-#: en/example-tutorial.xml:26(title)
+#: en/example-tutorial.xml:24(para)
+msgid "This phrase uses the local entity Per-document Entity."
+msgstr ""
+
+#: en/example-tutorial.xml:30(title)
msgid "Some Section"
msgstr ""
-#: en/example-tutorial.xml:28(primary)
+#: en/example-tutorial.xml:32(primary)
msgid "Index term"
msgstr ""
-#: en/example-tutorial.xml:30(para)
+#: en/example-tutorial.xml:34(para)
msgid ""
"This is an example section. You should not use sect1, sect2, etc., since "
"those tags will make sections less modular, i.e., harder to relocate without "
"changing a lot of other markup."
msgstr ""
-#: en/example-tutorial.xml:37(para)
+#: en/example-tutorial.xml:41(para)
msgid "Could not find the para-en.xml file"
msgstr ""
-#: en/example-tutorial.xml:42(para)
+#: en/example-tutorial.xml:46(para)
msgid ""
"Keep text within the title tags on the same line as the "
"tags. Nesting the title on a separate line from the enclosing tags results "
"in extra spaces in HTML rendering."
msgstr ""
-#: en/example-tutorial.xml:49(title)
+#: en/example-tutorial.xml:53(title)
msgid "Warning"
msgstr ""
-#: en/example-tutorial.xml:51(para)
+#: en/example-tutorial.xml:55(para)
msgid "Example of an admonition."
msgstr ""
-#: en/example-tutorial.xml:56(para)
+#: en/example-tutorial.xml:60(para)
msgid ""
"This paragraph illustrates the use of command syntax to accomplish a task. "
"Note that specific filenames denoting versions should be avoided. To install "
"any RPM package, use the following syntax:"
msgstr ""
-#: en/example-tutorial.xml:62(replaceable)
+#: en/example-tutorial.xml:66(replaceable)
msgid "pkgname"
msgstr ""
-#: en/example-tutorial.xml:62(replaceable)
+#: en/example-tutorial.xml:66(replaceable)
msgid "version"
msgstr ""
-#: en/example-tutorial.xml:62(replaceable)
+#: en/example-tutorial.xml:66(replaceable)
msgid "arch"
msgstr ""
-#: en/example-tutorial.xml:62(command)
+#: en/example-tutorial.xml:66(command)
msgid "rpm -ivh -..rpm"
msgstr ""
-#: en/example-tutorial.xml:65(para)
+#: en/example-tutorial.xml:69(para)
msgid ""
"Notice that the screen section is entirely left-justified "
"with no preceding indent. This is necessary to ensure proper rendering in "
@@ -98,38 +102,38 @@
"command> tags, as in the following sample."
msgstr ""
-#: en/example-tutorial.xml:76(command)
+#: en/example-tutorial.xml:80(command)
msgid "grep snmptrap /etc/services"
msgstr ""
-#: en/example-tutorial.xml:78(computeroutput)
+#: en/example-tutorial.xml:82(computeroutput)
#, no-wrap
msgid "snmptrap 162/udp snmp-trap # Traps for SNMP"
msgstr ""
-#: en/example-tutorial.xml:80(para)
+#: en/example-tutorial.xml:84(para)
msgid ""
"Lines should be broken exactly as they are on-screen. "
"Also, note that spaces inside screen tags are "
"automatically treated as non-breaking."
msgstr ""
-#: en/example-tutorial.xml:86(title)
+#: en/example-tutorial.xml:90(title)
msgid "Fill modes and screen tags"
msgstr ""
-#: en/example-tutorial.xml:87(para)
+#: en/example-tutorial.xml:91(para)
msgid ""
"Using automatic or manual fill commands in Emacs/PSGML will sometimes mangle "
"screen sections. Use care when performing fill "
"operations, and check the results."
msgstr ""
-#: en/example-tutorial.xml:96(title)
+#: en/example-tutorial.xml:100(title)
msgid "Callout Example"
msgstr ""
-#: en/example-tutorial.xml:97(programlisting)
+#: en/example-tutorial.xml:101(programlisting)
#, no-wrap
msgid ""
"\n"
@@ -139,59 +143,59 @@
"Line 4 \n"
msgstr ""
-#: en/example-tutorial.xml:105(para)
+#: en/example-tutorial.xml:109(para)
msgid "Here is a callout."
msgstr ""
-#: en/example-tutorial.xml:110(para)
+#: en/example-tutorial.xml:114(para)
msgid "The second callout."
msgstr ""
-#: en/example-tutorial.xml:118(title)
+#: en/example-tutorial.xml:122(title)
msgid "Deeply nested sections"
msgstr ""
-#: en/example-tutorial.xml:120(para)
+#: en/example-tutorial.xml:124(para)
msgid "Early to bed, early to rise"
msgstr ""
-#: en/example-tutorial.xml:125(title)
+#: en/example-tutorial.xml:129(title)
msgid "Second Level"
msgstr ""
-#: en/example-tutorial.xml:127(para)
+#: en/example-tutorial.xml:131(para)
msgid "Is the curse of the working class"
msgstr ""
-#: en/example-tutorial.xml:132(title)
+#: en/example-tutorial.xml:136(title)
msgid "Third Level"
msgstr ""
-#: en/example-tutorial.xml:134(para)
+#: en/example-tutorial.xml:138(para)
msgid "He who can, does"
msgstr ""
-#: en/example-tutorial.xml:139(title)
+#: en/example-tutorial.xml:143(title)
msgid "Fourth Level"
msgstr ""
-#: en/example-tutorial.xml:141(para)
+#: en/example-tutorial.xml:145(para)
msgid "He who cannot, manages."
msgstr ""
-#: en/example-tutorial.xml:150(title)
+#: en/example-tutorial.xml:154(title)
msgid "Procedure Test"
msgstr ""
-#: en/example-tutorial.xml:153(para)
+#: en/example-tutorial.xml:157(para)
msgid "First step"
msgstr ""
-#: en/example-tutorial.xml:158(para)
+#: en/example-tutorial.xml:162(para)
msgid "Second step"
msgstr ""
-#: en/example-tutorial.xml:163(para)
+#: en/example-tutorial.xml:167(para)
msgid "Third step"
msgstr ""
Index: example-tutorial.pot
===================================================================
RCS file: /cvs/docs/example-tutorial/po/example-tutorial.pot,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- example-tutorial.pot 1 Mar 2006 23:40:12 -0000 1.3
+++ example-tutorial.pot 2 Mar 2006 02:19:58 -0000 1.4
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-01 17:33-0600\n"
+"POT-Creation-Date: 2006-03-01 20:16-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
@@ -14,11 +14,11 @@
msgstr ""
#: en/entities.xml:10(comment)
-msgid "Name of our document"
+msgid "A per-document entity"
msgstr ""
-#: en/entities.xml:11(text)
-msgid "Pharphrompsober"
+#: en/entities.xml:11(wordasword)
+msgid "Per-document Entity"
msgstr ""
#: en/para.xml:10(para)
@@ -29,141 +29,145 @@
msgid "WHERE IS MY FDP-INFO, DUDE"
msgstr ""
-#: en/example-tutorial.xml:26(title)
+#: en/example-tutorial.xml:24(para)
+msgid "This phrase uses the local entity Per-document Entity."
+msgstr ""
+
+#: en/example-tutorial.xml:30(title)
msgid "Some Section"
msgstr ""
-#: en/example-tutorial.xml:28(primary)
+#: en/example-tutorial.xml:32(primary)
msgid "Index term"
msgstr ""
-#: en/example-tutorial.xml:30(para)
+#: en/example-tutorial.xml:34(para)
msgid "This is an example section. You should not use sect1, sect2, etc., since those tags will make sections less modular, i.e., harder to relocate without changing a lot of other markup."
msgstr ""
-#: en/example-tutorial.xml:37(para)
+#: en/example-tutorial.xml:41(para)
msgid "Could not find the para-en.xml file"
msgstr ""
-#: en/example-tutorial.xml:42(para)
+#: en/example-tutorial.xml:46(para)
msgid "Keep text within the title tags on the same line as the tags. Nesting the title on a separate line from the enclosing tags results in extra spaces in HTML rendering."
msgstr ""
-#: en/example-tutorial.xml:49(title)
+#: en/example-tutorial.xml:53(title)
msgid "Warning"
msgstr ""
-#: en/example-tutorial.xml:51(para)
+#: en/example-tutorial.xml:55(para)
msgid "Example of an admonition."
msgstr ""
-#: en/example-tutorial.xml:56(para)
+#: en/example-tutorial.xml:60(para)
msgid "This paragraph illustrates the use of command syntax to accomplish a task. Note that specific filenames denoting versions should be avoided. To install any RPM package, use the following syntax:"
msgstr ""
-#: en/example-tutorial.xml:62(replaceable)
+#: en/example-tutorial.xml:66(replaceable)
msgid "pkgname"
msgstr ""
-#: en/example-tutorial.xml:62(replaceable)
+#: en/example-tutorial.xml:66(replaceable)
msgid "version"
msgstr ""
-#: en/example-tutorial.xml:62(replaceable)
+#: en/example-tutorial.xml:66(replaceable)
msgid "arch"
msgstr ""
-#: en/example-tutorial.xml:62(command)
+#: en/example-tutorial.xml:66(command)
msgid "rpm -ivh -..rpm"
msgstr ""
-#: en/example-tutorial.xml:65(para)
+#: en/example-tutorial.xml:69(para)
msgid "Notice that the screen section is entirely left-justified with no preceding indent. This is necessary to ensure proper rendering in PDFs. Also notice that the entire command has been surrounded by userinput since the user types this command. Computer output would be enclosed in computeroutput tags, as in the following sample."
msgstr ""
-#: en/example-tutorial.xml:76(command)
+#: en/example-tutorial.xml:80(command)
msgid "grep snmptrap /etc/services"
msgstr ""
-#: en/example-tutorial.xml:78(computeroutput)
+#: en/example-tutorial.xml:82(computeroutput)
#, no-wrap
msgid "snmptrap 162/udp snmp-trap # Traps for SNMP"
msgstr ""
-#: en/example-tutorial.xml:80(para)
+#: en/example-tutorial.xml:84(para)
msgid "Lines should be broken exactly as they are on-screen. Also, note that spaces inside screen tags are automatically treated as non-breaking."
msgstr ""
-#: en/example-tutorial.xml:86(title)
+#: en/example-tutorial.xml:90(title)
msgid "Fill modes and screen tags"
msgstr ""
-#: en/example-tutorial.xml:87(para)
+#: en/example-tutorial.xml:91(para)
msgid "Using automatic or manual fill commands in Emacs/PSGML will sometimes mangle screen sections. Use care when performing fill operations, and check the results."
msgstr ""
-#: en/example-tutorial.xml:96(title)
+#: en/example-tutorial.xml:100(title)
msgid "Callout Example"
msgstr ""
-#: en/example-tutorial.xml:97(programlisting)
+#: en/example-tutorial.xml:101(programlisting)
#, no-wrap
msgid "\nLine 1 \nLine 2\nLine 3\nLine 4 \n"
msgstr ""
-#: en/example-tutorial.xml:105(para)
+#: en/example-tutorial.xml:109(para)
msgid "Here is a callout."
msgstr ""
-#: en/example-tutorial.xml:110(para)
+#: en/example-tutorial.xml:114(para)
msgid "The second callout."
msgstr ""
-#: en/example-tutorial.xml:118(title)
+#: en/example-tutorial.xml:122(title)
msgid "Deeply nested sections"
msgstr ""
-#: en/example-tutorial.xml:120(para)
+#: en/example-tutorial.xml:124(para)
msgid "Early to bed, early to rise"
msgstr ""
-#: en/example-tutorial.xml:125(title)
+#: en/example-tutorial.xml:129(title)
msgid "Second Level"
msgstr ""
-#: en/example-tutorial.xml:127(para)
+#: en/example-tutorial.xml:131(para)
msgid "Is the curse of the working class"
msgstr ""
-#: en/example-tutorial.xml:132(title)
+#: en/example-tutorial.xml:136(title)
msgid "Third Level"
msgstr ""
-#: en/example-tutorial.xml:134(para)
+#: en/example-tutorial.xml:138(para)
msgid "He who can, does"
msgstr ""
-#: en/example-tutorial.xml:139(title)
+#: en/example-tutorial.xml:143(title)
msgid "Fourth Level"
msgstr ""
-#: en/example-tutorial.xml:141(para)
+#: en/example-tutorial.xml:145(para)
msgid "He who cannot, manages."
msgstr ""
-#: en/example-tutorial.xml:150(title)
+#: en/example-tutorial.xml:154(title)
msgid "Procedure Test"
msgstr ""
-#: en/example-tutorial.xml:153(para)
+#: en/example-tutorial.xml:157(para)
msgid "First step"
msgstr ""
-#: en/example-tutorial.xml:158(para)
+#: en/example-tutorial.xml:162(para)
msgid "Second step"
msgstr ""
-#: en/example-tutorial.xml:163(para)
+#: en/example-tutorial.xml:167(para)
msgid "Third step"
msgstr ""
From fedora-docs-commits at redhat.com Thu Mar 2 02:20:00 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 1 Mar 2006 21:20:00 -0500
Subject: example-tutorial/en entities.ent, NONE, 1.1 entities.xml, NONE,
1.1 example-tutorial.xml, 1.6, 1.7
Message-ID: <200603020220.k222KV8E014285@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14162/en
Modified Files:
example-tutorial.xml
Added Files:
entities.ent entities.xml
Log Message:
Added per-document entities example files.
--- NEW FILE entities.ent ---
--- NEW FILE entities.xml ---
These entities are absolutely essential in this document.
A per-document entityPer-document Entity
Index: example-tutorial.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/en/example-tutorial.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- example-tutorial.xml 2 Mar 2006 01:50:00 -0000 1.6
+++ example-tutorial.xml 2 Mar 2006 02:19:53 -0000 1.7
@@ -21,6 +21,10 @@
WHERE IS MY FDP-INFO, DUDE
+
+ This phrase uses the local entity &LOCAL-ENT;.
+
+
Some Section
From fedora-docs-commits at redhat.com Thu Mar 2 05:06:27 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 2 Mar 2006 00:06:27 -0500
Subject: docs-common/bin tidy-bowl,1.6,1.7
Message-ID: <200603020506.k2256RAN020841@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/bin
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20791/docs-common/bin
Modified Files:
tidy-bowl
Log Message:
Since we now use .POT and .PO files to hold the translated text,
non-primary language XML should no longer be committed to CVS.
Commonly, our ${PRI_LANG} is a Romance language so we can just
prettyprint *every* XML file we see.
Index: tidy-bowl
===================================================================
RCS file: /cvs/docs/docs-common/bin/tidy-bowl,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- tidy-bowl 3 Feb 2006 17:48:55 -0000 1.6
+++ tidy-bowl 2 Mar 2006 05:05:58 -0000 1.7
@@ -45,7 +45,7 @@
for fn in $@
do
case "${fn}" in
- *-de.xml | *-en.xml | *-fr-xml | *-it.xml )
+ *.xml )
# Make sure we can find the input file
# /bin/echo "$0: XML file ${fn} prettyprinted."
if [ ! -f "${fn}" ]; then
@@ -61,10 +61,6 @@
exit 1
fi
;;
- *.xml )
- # A non-Romance XML file. What to do, what to do?
- # /bin/echo "$0: Non-Romance XML file ${fn} left unchanged."
- ;;
* )
# Some other kind of file. DO NOTHING!!!
# /bin/echo "$0: file ${fn} left unchanged."
From fedora-docs-commits at redhat.com Thu Mar 2 13:04:17 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 2 Mar 2006 08:04:17 -0500
Subject: example-tutorial rpm-info.xml,1.19,1.20
Message-ID: <200603021304.k22D4lIU007940@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7878
Modified Files:
rpm-info.xml
Log Message:
0.14.2 - move per-doc entities, license as OPL, and include system entity (snippet)
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/rpm-info.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- rpm-info.xml 13 Feb 2006 16:40:15 -0000 1.19
+++ rpm-info.xml 2 Mar 2006 13:04:09 -0000 1.20
@@ -12,7 +12,7 @@
- GNU FDL
+ OPL1.0
@@ -31,6 +31,10 @@
+
+
+ Moved per-doc entities, added offboard snippet to test entity inclusion across the board, and moved license to OPL.
+ A shameless bump to test prettyprinting
From fedora-docs-commits at redhat.com Thu Mar 2 13:04:49 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 2 Mar 2006 08:04:49 -0500
Subject: example-tutorial/po de.po,1.4,1.5 example-tutorial.pot,1.4,1.5
Message-ID: <200603021304.k22D4nf2007947@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/example-tutorial/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7878/po
Modified Files:
de.po example-tutorial.pot
Log Message:
0.14.2 - move per-doc entities, license as OPL, and include system entity (snippet)
Index: de.po
===================================================================
RCS file: /cvs/docs/example-tutorial/po/de.po,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- de.po 2 Mar 2006 02:19:58 -0000 1.4
+++ de.po 2 Mar 2006 13:04:39 -0000 1.5
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-01 20:16-0600\n"
+"POT-Creation-Date: 2006-03-02 07:30-0500\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
@@ -21,78 +21,122 @@
msgid "Per-document Entity"
msgstr ""
+#: en/entities.xml:14(comment)
+msgid "Should match the name of this module"
+msgstr ""
+
+#: en/entities.xml:15(text)
+msgid "example-tutorial"
+msgstr ""
+
+#: en/entities.xml:18(comment)
+msgid "Last revision number, bump when you change the doc"
+msgstr ""
+
+#: en/entities.xml:19(text)
+msgid "0.14.2"
+msgstr ""
+
+#: en/entities.xml:22(comment)
+msgid "Last revision date, format YYYY-MM-DD"
+msgstr ""
+
+#: en/entities.xml:23(text)
+msgid "2006-03-02"
+msgstr ""
+
+#: en/entities.xml:26(comment)
+msgid "Same for every document"
+msgstr ""
+
+#: en/entities.xml:27(text)
+msgid ""
+"
-
+ &BUG-REPORTING;
This paragraph illustrates the use of command syntax to accomplish
a task. Note that specific filenames denoting versions should be
avoided. To install any RPM package, use the following syntax:
-
+rpm -ivh pkgname-version.arch.rpm
@@ -76,7 +70,7 @@
computeroutput tags, as in the following
sample.
-
+grep snmptrap /etc/servicessnmptrap 162/udp snmp-trap # Traps for SNMP
@@ -98,7 +92,7 @@
Callout Example
-
+
Line 1
Line 2
Line 3
From fedora-docs-commits at redhat.com Thu Mar 2 18:15:33 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 2 Mar 2006 13:15:33 -0500
Subject: docs-common/common/entities de.po, NONE, 1.1 entities-de.ent, NONE,
1.1 entities-de.xml, NONE, 1.1
Message-ID: <200603021815.k22IFXg5026859@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/docs-common/common/entities
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26835
Added Files:
de.po entities-de.ent entities-de.xml
Log Message:
Add de entity files to make example-tutorial happy... these can be translated for real at some point
--- NEW FILE de.po ---
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2006-03-01 16:48-0500\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: entities-en.xml:6(title)
msgid "These common entities are useful shorthand terms and names, which may be subject to change at anytime. This is an important value the the entity provides: a single location to update terms and common names."
msgstr ""
#: entities-en.xml:14(comment) entities-en.xml:18(comment)
msgid "Generic root term"
msgstr ""
#: entities-en.xml:15(text)
msgid "Fedora"
msgstr ""
#: entities-en.xml:19(text)
msgid "Core"
msgstr ""
#: entities-en.xml:22(comment)
msgid "Generic main project name"
msgstr ""
#: entities-en.xml:26(comment)
msgid "Legacy Entity"
msgstr ""
#: entities-en.xml:30(comment)
msgid "Short project name"
msgstr ""
#: entities-en.xml:31(text)
msgid "FC"
msgstr ""
#: entities-en.xml:34(comment)
msgid "Generic overall project name"
msgstr ""
#: entities-en.xml:35(text)
msgid "
-
+ Enabling Remote Access to the Installation System
-
+
You may access either graphical or text interfaces for the
installation system from any other system. Access to a text mode
@@ -316,39 +319,42 @@
running in listening mode.
-
-
- VNC (Virtual Network Computing)
- enabling
-
- To enable remote graphical access to the installation system,
- enter two options at the prompt:
-
+
+ Enabling Remote Access with VNC
+
+
+
+ VNC (Virtual Network Computing)
+ enabling
+
+ To enable remote graphical access to the installation system,
+ enter two options at the prompt:
+ linux vnc vncpassword=qwerty
-
- The option enables the VNC service. The
- option sets a password for remote
- access. The example shown above sets the password as
- qwerty.
-
+
+ The option enables the VNC service. The
+ option sets a password for remote
+ access. The example shown above sets the password as
+ qwerty.
+
-
- VNC Passwords
+
+ VNC Passwords
+
+
+ The VNC password must be at least six characters long.
+
+
- The VNC password must be at least six characters long.
+ Specify the language, keyboard layout and network settings for
+ the installation system with the screens that follow. You may
+ then access the graphical interface through a VNC client. The
+ installation system displays the correct connection setting for
+ the VNC client:
-
-
-
- Specify the language, keyboard layout and network settings for the
- installation system with the screens that follow. You may then
- access the graphical interface through a VNC client. The
- installation system displays the correct connection setting for
- the VNC client:
- for a shell]]>
-
- You may then login to the installation system with a VNC client.
- To run the vncviewer client on &FED;,
- choose Applications
- AccessoriesVNC
- Viewer, or type the command
- vncviewer in a terminal window. Enter
- the server and display number in the VNC
- Server dialog. For the example above, the VNC
- Server is
- computer.mydomain.com:1.
-
+
+ You may then login to the installation system with a VNC client.
+ To run the vncviewer client on &FED;,
+ choose Applications
+ AccessoriesVNC
+ Viewer, or type the command
+ vncviewer in a terminal window. Enter
+ the server and display number in the VNC
+ Server dialog. For the example above, the
+ VNC Server is
+ computer.mydomain.com:1.
+
+
-
- To have the installation system automatically connect to a VNC
- client, first start the client in
-
- VNC (Virtual Network Computing)
- listening mode
-
- listening mode. On &FED; systems, use the
- option to run vncviewer as a listener.
- In a terminal window, enter the command:
-
+
+ Connecting the Installation System to a VNC Listener
+
+
+ To have the installation system automatically connect to a VNC
+ client, first start the client in
+
+ VNC (Virtual Network Computing)
+ listening mode
+
+ listening mode. On &FED; systems, use the
+ option to run
+ vncviewer as a listener. In a
+ terminal window, enter the command:
+ vncviewer -listen
-
- Firewall Reconfiguration Required
+
+ Firewall Reconfiguration Required
+
+
+ By default, the vncviewer utility
+ listens on TCP port 5500. To update the &FED; firewall
+ configuration to permit connections to this port from other
+ systems, choose System
+ AdministrationSecurity
+ Level and Firewall, enter
+ 5500:tcp in the Other
+ ports: field, and select OK.
+
+
- By default, the vncviewer utility
- listens on TCP port 5500. To update the
- &FED; firewall configuration to permit connections to this port
- from other systems, choose
- System
- AdministrationSecurity
- Level and Firewall, enter
- 5500:tcp in the Other
- ports: field, and select OK.
+ Once the listening client is active, start the installation
+ system and set the VNC options at the
+ boot:
+ prompt. In addition to and
+ options, use the
+ option to specify the name or IP
+ address of the system that has the listening client. To specify
+ the TCP port for the listener, add a colon and the port number
+ to the name of the system.
-
-
- Once the listening client is active, start the installation system
- and set the VNC options at the
- boot:
- prompt. In addition to and
- options, use the
- option to specify the name or IP
- address of the system that has the listening client. To specify
- the TCP port for the listener, add a colon and the port number to
- the name of the system.
-
-
-
- For example, to connect to a VNC client on the system
-
+ For example, to connect to a VNC client on the system
+ desktop.mydomain.com
- on the port 5500, enter the following at
- the
- boot:
- prompt:
-
+ on the port 5500, enter the following at the
+ boot:
+ prompt:
+
linux vnc vncpassword=qwerty vncconnect=desktop.mydomain.com:5500
-
- To enable remote access to a text mode installation, use the
-
- Telnet
-
- option at the
- boot:
- prompt:
-
+
+
+
+ Enabling Remote Access with Telnet
+
+
+ To enable remote access to a text mode installation, use the
+
+ Telnet
+
+ option at the
+ boot:
+ prompt:
+ linux text telnet
-
- You may then connect to the installation system with the
- telnet utility. The telnet
- command requires the name or IP address of the installation
- system:
-
+
+ You may then connect to the installation system with the
+ telnet utility. The telnet
+ command requires the name or IP address of the installation
+ system:
+ telnet computer.mydomain.com
-
- Telnet Access Requires No Password
+
+ Telnet Access Requires No Password
-
- To ensure the security of the installation process, only use the
- option to install systems on networks
- with restricted access.
-
-
-
+
+ To ensure the security of the installation process, only use
+ the option to install systems on
+ networks with restricted access.
+
+
+ Logging to a Remote System During the Installation
@@ -473,8 +487,7 @@
To configure remote logging, add the
option. Specify the IP address of the logging system, and the UDP
port number of the log service on that system. By default, syslog
- services that accept remote messages listen on UDP port
- 514.
+ services that accept remote messages listen on UDP port 514.
@@ -488,64 +501,67 @@
linux syslog=192.168.1.20:514
-
- &FED; uses syslogd to provide a syslog service.
- The default configuration of syslogd rejects
- messages from remote systems.
-
-
-
- Only Enable Remote Syslog Access on Secured Networks
+
+ Configuring a Log Server
- The syslogd service includes no security
- measures. Crackers may slow or crash systems that permit access
- to the logging service, by sending large quantities of false log
- messages. In addition, hostile users may intercept or falsify
- messages sent to the logging service over the network.
+ &FED; uses syslogd to provide a syslog
+ service. The default configuration of syslogd
+ rejects messages from remote systems.
-
-
- To configure a &FED; system to accept log messages from other
- systems on the network, edit the file
- /etc/sysconfig/syslog. You must use
- root privileges to edit
- the file /etc/sysconfig/syslog. Add the
- option to the
- SYSLOGD_OPTIONS:
-
+
+ Only Enable Remote Syslog Access on Secured Networks
+
+
+ The syslogd service includes no security
+ measures. Crackers may slow or crash systems that permit
+ access to the logging service, by sending large quantities of
+ false log messages. In addition, hostile users may intercept
+ or falsify messages sent to the logging service over the
+ network.
+
+
+
+ To configure a &FED; system to accept log messages from other
+ systems on the network, edit the file
+ /etc/sysconfig/syslog. You must use
+ root privileges to
+ edit the file /etc/sysconfig/syslog. Add
+ the option to the
+ SYSLOGD_OPTIONS:
+ SYSLOGD_OPTIONS="-m 0 -r"
-
-
- Restart the syslogd service to apply the
- change:
-
+
+ Restart the syslogd service to apply the
+ change:
+ su -c '/sbin/service syslog restart'
-
- Enter the root password
- when prompted.
-
-
-
- Firewall Reconfiguration Required
-
- By default, the syslog service listens on UDP port
- 514. To update the &FED; firewall
- configuration to permit connections to this port from other
- systems, choose System
- AdministrationSecurity
- Level and Firewall, enter
- 514:udp in the Other
- ports: field, and select OK.
+ Enter the root
+ password when prompted.
-
+
+
+ Firewall Reconfiguration Required
+
+
+ By default, the syslog service listens on UDP port 514. To
+ update the &FED; firewall configuration to permit connections
+ to this port from other systems, choose
+ System
+ AdministrationSecurity
+ Level and Firewall, enter
+ 514:udp in the Other
+ ports: field, and select OK.
+
+
+ Automating the Installation with Kickstart
@@ -557,8 +573,8 @@
Kickstart file specifies settings for an
installation. Once the installation system boots, it can read a
- Kickstart file and carry out the installation process without
- any further input from a user.
+ Kickstart file and carry out the installation process without any
+ further input from a user.
Every Installation Produces a Kickstart File
@@ -572,19 +588,18 @@
- &FED; includes a graphical application to create
- and modify Kickstart files by selecting the options you
- require. Use the package
- system-config-kickstart to install this
- utility. To load the &FED; Kickstart editor, choose
- ApplicationsSystem
+ &FED; includes a graphical application to create and modify
+ Kickstart files by selecting the options you require. Use the
+ package system-config-kickstart to install
+ this utility. To load the &FED; Kickstart editor, choose
+ ApplicationsSystem
ToolsKickstart.
Kickstart files list installation settings in plain text, with one
- option per line. This format lets you modify your Kickstart
- files with any text editor, and write scripts or applications that
+ option per line. This format lets you modify your Kickstart files
+ with any text editor, and write scripts or applications that
generate custom Kickstart files for your systems.
@@ -1051,14 +1066,16 @@
+
+ Additional Screen
-
-Additional Screen
-
- The 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.
-
-
-
+
+ The 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.
+
+
@@ -1106,7 +1123,8 @@
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.
+ functions of a running Linux system to modify or repair systems
+ that are already installed on your computer.
Index: fedora-install-guide-diskpartitioning.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-diskpartitioning.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-diskpartitioning.xml 2 Mar 2006 22:57:14 -0000 1.8
+++ fedora-install-guide-diskpartitioning.xml 3 Mar 2006 02:43:40 -0000 1.9
@@ -1,4 +1,5 @@
+
RAID facilities enable a group, or array,
of drives to act as a single device. Configure any RAID functions
- provided by your mainboard, or attached controller cards, before
- you install &FC;. Each active RAID array appears as one drive.
+ provided by the mainboard of your computer, or attached controller
+ cards, before you begin the installation process. Each active RAID
+ array appears as one drive within &FED;.
@@ -168,7 +170,8 @@
Many systems have more partitions than the minimum listed above.
Choose partitions based on your particular system needs. If you
- are not sure what to choose, accept the default partition layout.
+ are not sure how best to configure the partitions for your
+ computer, accept the default partition layout.
@@ -249,7 +252,14 @@
Edit option
for more information.
-
+
+ Leave Excess Capacity Unallocated
+
+ Only assign storage capacity to partitions that you require
+ immediately. You may allocate free space at any time, to meet
+ needs as they arise.
+
+ Partition Types
@@ -330,6 +340,14 @@
across the storage devices.
+
+ You may lose data if you shrink a logical volume to a smaller
+ capacity than the data on the volume requires. For this reason,
+ create logical volumes to meet your current needs, and leave
+ excess storage capacity unallocated. You may safely grow logical
+ volumes to use unallocated space, as your needs dictate.
+
+
LVM and the Default Partition Layout
@@ -344,8 +362,8 @@
Creating a <filename>/home</filename> Partition
- If you expect that you or other users will store data on
- the system, create a separate partition for the
+ If you expect that you or other users will store data on the
+ system, create a separate partition for the
/home directory within an LVM volume. With
a separate /home partition, you may upgrade
or reinstall &FC; without erasing user data files. LVM provides
@@ -723,9 +741,9 @@
You may not remove a physical volume from a volume group if
doing so would leave insufficient space for that group's
- logical volumes. Take for example a volume group made up
- of two 5 GB LVM physical volume partitions, which contains
- an 8 GB logical volume. The installer would not allow you to
+ logical volumes. Take for example a volume group made up of
+ two 5 GB LVM physical volume partitions, which contains an 8
+ GB logical volume. The installer would not allow you to
remove either of the component physical volumes, since that
would leave only 5 GB in the group for an 8 GB logical
volume. If you reduce the total size of any logical volumes
Index: fedora-install-guide-intro.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-intro.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-intro.xml 2 Mar 2006 22:57:14 -0000 1.9
+++ fedora-install-guide-intro.xml 3 Mar 2006 02:43:40 -0000 1.10
@@ -1,4 +1,5 @@
+
This document does not detail all of the features of the
installation system.
-
&BUG-REPORTING;
@@ -51,17 +48,21 @@
The &FP;, which produces and maintains &FC;, is a collaboration
- between &FORMAL-RHI; and the
- free software
- FOSS
-
- open source
- FOSS
-
- FOSS (free and open source software)
- free and open source software
- (FOSS) community. The &FP; also provides &FEX;, additional
- software packaged for installation on a &FC; system.
+ between &FORMAL-RHI; and the
+
+ free software
+ FOSS
+
+
+ open source
+ FOSS
+
+
+ FOSS (free and open source software)
+
+ free and open source software (FOSS)
+ community. The &FP; also provides &FEX;, additional software
+ packaged for installation on a &FC; system.
@@ -165,18 +166,37 @@
Release Notes are available at &FDPDOCS-URL;.
+
+ Storage
+
+
+ A &FED; system requires a minimum of 700Mb storage for a
+ command-line system. Assign at least 3Gb for a desktop system
+ with the default applications. You may install multiple copies
+ of &FED; on the same computer.
+
+
+
+ Configure any RAID functions provided by the mainboard of your
+ computer, or attached controller cards, before you begin the
+ installation process. &FED; may automatically detect configured
+ RAID devices and use the storage that they provide.
+
+
+
Networking
By default, &FC; systems attempt to discover correct connection
- settings for the attached network using
- DHCP (Dynamic Host Configuration Protocol)
- DHCP (Dynamic Host Control
- Protocol). Your network may include a DHCP provider which
- delivers settings to other systems on demand. The DHCP provider
- may be a router or wireless access point for the network, or a
- server.
+ settings for the attached network using
+
+ DHCP (Dynamic Host Configuration Protocol)
+
+ DHCP (Dynamic Host Control Protocol).
+ Your network may include a DHCP provider which delivers settings
+ to other systems on demand. The DHCP provider may be a router or
+ wireless access point for the network, or a server.
@@ -199,34 +219,13 @@
-
- Installing from a Server or Website
+ Installing from a Server or Web Site
You may install &FC; using a mirror, a
- website or network server that provide a copy of the necessary
+ Web site or network server that provide a copy of the necessary
files. To use a mirror, you need to know:
@@ -356,9 +355,10 @@
- For instructions to download and prepare this CD or DVD installation media, refer
- to . If you
- already have the full set of &FC; installation media, skip to
+ For instructions to download and prepare this CD or DVD
+ installation media, refer to
+ . If you already
+ have the full set of &FC; installation media, skip to
.
@@ -367,18 +367,18 @@
Architecture-Specific Distributions
- To install &FC;, you must use the boot and installation media that is
- particular to your architecture.
+ To install &FC;, you must use the boot and installation media
+ that is particular to your architecture.
You may use the first CD or DVD installation disc from the
- complete &FC; distribution to boot your computer. The &FC; distribution also includes image
- files for boot-only CD or DVD media and USB media.
- These files can be converted into bootable media using standard
- Linux utilities or third-party programs on other operating
- systems.
+ complete &FC; distribution to boot your computer. The &FC;
+ distribution also includes image files for
+ boot-only CD or DVD media and USB media. These files can be
+ converted into bootable media using standard Linux utilities or
+ third-party programs on other operating systems.
Index: fedora-install-guide-locale.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-locale.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-locale.xml 2 Mar 2006 22:57:14 -0000 1.7
+++ fedora-install-guide-locale.xml 3 Mar 2006 02:43:40 -0000 1.8
@@ -1,4 +1,5 @@
+
+
Identifying Your Locale
-
If the installation system fails to identify the display hardware on
your computer, it displays text screens rather than the default
- graphical interface. The text screens provide the same functions as
- the standard screens. Later in the installation process you can
+ graphical interface. The text screens provide the same functions as
+ the standard screens. Later in the installation process you can
manually specify your display hardware.
-
- Network Installations
+ Network Installations
+
Network installations with HTTP and FTP always use text screens on
systems with less than 128Mb of memory.
-
Language Selection
@@ -37,41 +37,37 @@
The installation program displays a list of languages supported by
&FED;.
-
Language Selection Screen
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
Language selection screen.
-
+
-
Highlight the correct language on the list and select
Next.
- Installing Support For Additional Languages
+ Installing Support For Additional Languages
+
- To select support for additional languages, customize the
- installation at the package selection stage. For more
- information, refer to .
+ To select support for additional languages, customize the
+ installation at the package selection stage. For more
+ information, refer to .
-
-
-
Keyboard Configuration
@@ -79,31 +75,27 @@
The installation program display a list of the keyboard layouts
supported by &FED;:
-
Keyboard Configuration Screen
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
Keyboard configuration screen.
-
+
-
Highlight the correct layout on the list, and select
Next.
-
-
+ Boot options broken out into clearer subsections.
+
- Added Xen material.
+ Added Xen material.
From fedora-docs-commits at redhat.com Fri Mar 3 03:25:50 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 2 Mar 2006 22:25:50 -0500
Subject: install-guide/en fedora-install-guide-intro.xml,1.10,1.11
Message-ID: <200603030325.k233PoJQ018048@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18030
Modified Files:
fedora-install-guide-intro.xml
Log Message:
Minor style corrections
Index: fedora-install-guide-intro.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-intro.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- fedora-install-guide-intro.xml 3 Mar 2006 02:43:40 -0000 1.10
+++ fedora-install-guide-intro.xml 3 Mar 2006 03:25:42 -0000 1.11
@@ -170,17 +170,17 @@
Storage
- A &FED; system requires a minimum of 700Mb storage for a
- command-line system. Assign at least 3Gb for a desktop system
- with the default applications. You may install multiple copies
- of &FED; on the same computer.
+ A &FED; system requires a minimum of 700 MB storage for a
+ command-line system. A desktop system with the default
+ applications requires at least 3 GB of storage. You may install
+ multiple copies of &FED; on the same computer.
Configure any RAID functions provided by the mainboard of your
computer, or attached controller cards, before you begin the
- installation process. &FED; may automatically detect configured
- RAID devices and use the storage that they provide.
+ installation process. &FED; can automatically detect many RAID
+ devices and use any storage they provide.
@@ -262,7 +262,7 @@
- To determine the complete the directory path for the
+ To determine the complete directory path for the
installation files, add
/&FCLOCALVER;/architecture/os/
to the path shown on the webpage.
@@ -395,13 +395,13 @@
- Hard drive, either attached by USB, or internal to the
+ hard drive, either attached by USB, or internal to the
computer
- Network installation server, using either HTTP, FTP, or NFS
+ network installation server, using either HTTP, FTP, or NFS
@@ -431,7 +431,7 @@
- Network interface (via PXE)
+ network interface (via PXE)
@@ -537,7 +537,6 @@
From fedora-docs-commits at redhat.com Fri Mar 3 14:07:49 2006
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Fri, 3 Mar 2006 09:07:49 -0500
Subject: release-notes/po zh_CN.po,1.3,1.4
Message-ID: <200603031407.k23E7n66011405@cvs-int.fedora.redhat.com>
Author: bbbush
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv11377
Modified Files:
zh_CN.po
Log Message:
far from ready, though
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.3 -r 1.4 zh_CN.po
Index: zh_CN.po
===================================================================
RCS file: /cvs/docs/release-notes/po/zh_CN.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- zh_CN.po 23 Feb 2006 14:42:00 -0000 1.3
+++ zh_CN.po 3 Mar 2006 14:07:40 -0000 1.4
@@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: RELEASE-NOTES\n"
-"POT-Creation-Date: 2006-02-20 22:10+0800\n"
-"PO-Revision-Date: 2006-02-22 05:34+0800\n"
+"POT-Creation-Date: 2006-02-27 20:01+0800\n"
+"PO-Revision-Date: 2006-03-02 04:58+0800\n"
"Last-Translator: Yuan Yijun \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
@@ -10,19 +10,20 @@
"Content-Transfer-Encoding: 8bit\n"
#: en/Xorg.xml:5(title) en/Welcome.xml:5(title) en/WebServers.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/PackageNotesJava.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/ArchSpecificx86.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)
msgid "Temp"
@@ -45,83 +46,128 @@
#: en/Xorg.xml:12(para)
msgid ""
"X.org X11 is an open source implementation of the X Window System. It "
-"provides the basic low level functionality which full fledged graphical user "
-"interfaces (GUIs) such as GNOME and KDE are designed upon."
-msgstr ""
-"X.org X11 ??? X ?????????????????????????????????????????????????????????????????????????????????????????????"
-"??? (GUI) ?????? GNOME ??? KDE ???????????????"
+"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 http://xorg.freedesktop.org/wiki/."
+msgstr "X.org X11 ??? X ???????????????????????????????????????????????????????????????????????????????????????????????? (GUI) ?????? GNOME ??? KDE ???????????????????????? "
#: en/Xorg.xml:13(para)
msgid ""
-"For more information about Xorg refer to http://xorg.freedesktop.org/wiki/"
-msgstr ""
-"???????????? Xorg ?????????????????? http://xorg.freedesktop.org/wiki/"
+"You may use Applications > System Settings > Display or system-config-display to "
+"configure the settings. The configuration file for X.org is located in "
+"/etc/X11/xorg.conf."
+msgstr "???????????? Applications > System Settings > Display ????????? system-config-display ????????????Xorg ?????????????????? /etc/X11/xorg.conf???"
+
+#: 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 http://"
+"fedoraproject.org/wiki/Xorg/Modularization."
+msgstr "X.org X11R7 ??? X.org ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????Fedora ??? X.org ????????????????????????????????? http://fedoraproject.org/wiki/Xorg/Modularization???"
+
+#: en/Xorg.xml:17(title)
+msgid "X.org X11R7 End-User Notes"
+msgstr "X.org X11R7 ????????????"
+
+#: en/Xorg.xml:19(title)
+msgid "Installing Third Party Drivers"
+msgstr "?????????????????????"
+
+#: en/Xorg.xml:20(para)
+msgid ""
+"Before you install any third party drivers from any vendor, including ATI or "
+"nVidia, please read http://fedoraproject.org/wiki/"
+"Xorg/3rdPartyVideoDrivers."
+msgstr "?????????????????????(?????? ATI ??? nVidia)????????????????????????????????????????????? http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers???"
-#: en/Xorg.xml:15(para)
+#: en/Xorg.xml:25(para)
msgid ""
-"You can use Applications => System Settings => Display or system-"
-"config-display to configure the settings. The configuration file for Xorg is "
-"located in /etc/X11/xorg.conf"
-msgstr "???????????? Applications => System Settings = > Display ????????? system-config-display ????????????Xorg ?????????????????? /etc/X11/xorg.conf???"
+"The xorg-x11-server-Xorg package install scripts automatically "
+"remove the RgbPath line from the xorg.conf 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 xorg at freedesktop.org mailing "
+"list if you do need assistance reconfiguring your keyboard."
+msgstr "xorg-x11-server-Xorg ????????????????????????????????? xorg.conf ?????? RgbPath ???????????????????????????????????????????????????????????????????????????????????????????????????????????? xorg at freedesktop.org ???????????????"
-#: en/Xorg.xml:16(para)
-#, fuzzy
+#: en/Xorg.xml:28(title)
+msgid "X.org X11R7 Developer Overview"
+msgstr "X.org X11R7 ???????????????"
+
+#: en/Xorg.xml:29(para)
msgid ""
-"Modular X.Org X11R7 RC2 was released into Fedora development (rawhide) on "
-"November 16, 2005. This is the first modular release of Xorg which among "
-"several other benefits, enable users to receive updates in a faster pace and "
-"helps developers to develop and release specific components in a rapid "
-"fashion."
+"The following list includes some of the more visible changes for developers "
+"in X11R7:"
+msgstr "?????????????????? X11R7 ???????????????????????????????????????"
+
+#: en/Xorg.xml:32(para)
+msgid ""
+"The entire buildsystem has changed from imake to the GNU "
+"autotools collection."
+msgstr "????????????????????? imake ?????? GNU autotools ????????????"
+
+#: en/Xorg.xml:35(para)
+msgid ""
+"Libraries now install pkgconfig*.pc files, which "
+"should now always be used by software that depends on these libraries, "
+"instead of hard coding paths to them in /usr/X11R6/lib or elsewhere."
msgstr ""
-"Modular (????????????) X.Org X11R7 RC2 ??? 2005 ??? 11 ??? 16 ????????? &FED; ??????"
-"?????? (rawhide)????????? Xorg ??????????????????????????????????????????"
-"???????????????????????????????????? Xorg ?????????????????????????????????????????????????????????????????????"
-"???????????????????????????????????????"
+"??????????????????????????? pkgconfig*.pc ???"
+"???????????????????????????????????????????????????????????????????????? /usr/X11R6/lib ????????????????????????"
-#: en/Xorg.xml:17(para)
+#: en/Xorg.xml:40(para)
#, fuzzy
msgid ""
-"More information on the current status of the Xorg modularization effort in "
-"Fedora is available from http://"
-"fedoraproject.org/wiki/Xorg/Modularization"
+"Everything is now installed directly into /usr instead of "
+"/usr/X11R6. All software that hard codes paths to "
+"anything in /usr/X11R6 must now be changed, "
+"preferably to dynamically detect the proper location of the object. "
+"Developers are strongly advised against "
+"hard-coding the new X11R7 default paths."
msgstr ""
-"?????? Xorg ????????????????????????????????? http://"
-"fedoraproject.org/wiki/Xorg/Modularization"
+"?????????????????????????????? /usr ??????????????? /usr/"
+"X11R6???????????????????????? /usr/X11R6 ??????????????????"
+"??????????????????????????????????????????????????????????????? X11R7 ??????????????????????????????????????????"
+"??????????????????????????????????????????????????????"
-#: en/Xorg.xml:21(title)
-#, fuzzy
-msgid "Xorg X11R7.0 Developer Notes"
-msgstr "Xorg X11R7 ???????????????"
+#: en/Xorg.xml:45(para)
+msgid ""
+"Every library has its own private source RPM package, which creates a "
+"runtime binary subpackage and a -devel subpackage."
+msgstr "??????????????????????????????????????? RPM??????????????????????????????????????????????????????????????? -devel ???????????????"
-#: en/Xorg.xml:22(para)
+#: en/Xorg.xml:50(title)
#, fuzzy
+msgid "X.org X11R7 Developer Notes"
+msgstr "Xorg X11R7.0 ???????????????"
+
+#: en/Xorg.xml:51(para)
msgid ""
-"X11R7.0 is included in this release and there are a number of things that "
[...9439 lines suppressed...]
+
+#, fuzzy
+#~ msgid ""
+#~ "SCIM has replaced IIIMF as the language input framework in Fedora Core in "
+#~ "this release."
+#~ msgstr ""
+#~ " ???"
+#~ "??? Fedora Core ???????????? SCIM ????????? IIIMF ?????????????????????????????????"
+
+#, fuzzy
+#~ msgid ""
+#~ "Version 2 of Netatalk uses a different method to store file resource "
+#~ "forks from the previous version, and may require a different file name "
+#~ "encoding scheme. Please read the documentation and plan your migration "
+#~ "before upgrading."
+#~ msgstr ""
+#~ "Netatalk ????????????????????????????????????????????????????????????????????????????????????????????????"
+#~ "???????????????????????????????????????????????????????????????"
+
+#~ msgid "Feedback"
+#~ msgstr "??????"
+
+#~ msgid ""
+#~ "Thanks for your interest in helping us with the release notes by "
+#~ "providing feedback. This section explains how you can give that feedback."
+#~ msgstr "?????????????????????????????????????????????????????????????????????????????????????????????"
+
+#~ msgid "Release Notes Feedback Procedure"
+#~ msgstr "????????????????????????"
+
+#~ msgid ""
+#~ "Edit content directly at Docs/Beats"
+#~ msgstr "???????????? Docs/Beats ?????????"
+
+#~ msgid ""
+#~ "A release note beat is an area of the release notes that is the responsibility of one "
+#~ "or more content contributors to oversee."
+#~ msgstr ""
+#~ "?????????????????? beat "
+#~ "??????????????????????????????????????????????????????????????????????????????"
+
+#~ msgid "yum groupinfo \"Games and Entertainment\""
+#~ msgstr "yum groupinfo \"Games and Entertainment\""
+
+#~ msgid ""
+#~ "For help using yum to install the assorted game "
+#~ "packages, refer to the guide available at:"
+#~ msgstr ""
+#~ "???????????? yum ???????????????????????????????????????????????????????????????"
+#~ "??????"
+
+#~ msgid "http://fedora.redhat.com/docs/yum/"
+#~ msgstr "http://fedora.redhat.com/docs/yum/"
+
+#~ msgid ""
+#~ "Fedora Extras is part of the larger Fedora Project and is a volunteer-"
+#~ "based community effort to create a repository of packages that compliment "
+#~ "Fedora Core. The Fedora Extras repository is enabled by default."
+#~ msgstr ""
+#~ "Fedora Extras ??? Fedora Project ???????????????????????????????????????????????????????????????"
+#~ "?????? Fedora Core ????????????????????????Fedora Extras ????????????????????????"
+
+#~ msgid ""
+#~ "If you would like to install any software available from Fedora extras "
+#~ "you can use yum."
+#~ msgstr "?????????????????? Fedora Extras ??????????????????????????? yum???"
+
+#~ msgid "yum install <packagename>"
+#~ msgstr "yum install <packagename>"
+
+#~ msgid ""
+#~ "Where <packagename> is the name of the package you want to install. "
+#~ "For example, if you wanted to install the abiword package, the command "
+#~ "yum install abiword automatically installs the package and "
+#~ "all dependencies."
+#~ msgstr ""
+#~ "?????? <packagename> ???????????????????????????????????????????????????????????? abiword "
+#~ "?????????????????? yum install abiword ???????????????????????????????????????"
+#~ "??????"
+
+#, fuzzy
+#~ msgid ""
+#~ "GNOME 2.13.2 and KDE 3.5 Release Candidate 2 has been included in Fedora "
+#~ "Core 5 test 2. GNOME 2.14 (or a release candidate) is scheduled to be "
+#~ "available as part of Fedora Core 5."
+#~ msgstr ""
+#~ "GNOME 2.13.2 ??? KDE 3.5 ???????????? 2 ???????????? &FC; &LOCALVER; ??????"
+#~ "GNOME 2.14 (???????????????) ??????????????? &FC; 5 ???????????????"
+
+#, fuzzy
+#~ msgid ""
+#~ "The current test release has GNOME 2.12.1, together with some previews of "
+#~ "technology from the forthcoming GNOME 2.14. Feedback on these packages is "
+#~ "especially appreciated."
+#~ msgstr ""
+#~ "???????????????????????? GNOME 2.12.1???????????????????????? GNOME 2.14 ?????????????????????"
+#~ "?????????????????????????????????????????????????????????"
+
+#, fuzzy
+#~ msgid "system-config-mouse Removed"
+#~ msgstr "system-config-securitylevel"
+
+#, fuzzy
+#~ msgid ""
+#~ "system-config-mouse configuration utility has been dropped from this "
+#~ "release since synaptic and 3 button mouse configuration is being done "
+#~ "automatically during installation and serial mice are not formally "
+#~ "supported in Fedora Core anymore."
+#~ msgstr ""
+#~ "system-config-monitor ????????????????????????????????????"
+#~ "???????????????????????????????????????????????????????????????????????????????????? &FC; ????????????"
+
+#~ msgid "No changes of note."
+#~ msgstr "?????????"
+
+#~ msgid "Draft"
+#~ msgstr "??????"
+
+#~ msgid "This is a draft, so it is incomplete and imperfect."
+#~ msgstr "??????????????????????????????????????????"
+
+#, fuzzy
+#~ msgid ""
+#~ "Fedora includes several system libraries and software for compatibility "
+#~ "with older software. These software are part of the \"Legacy Software "
+#~ "Development\" group which are not installed by default. Users who require "
+#~ "this functionality can select this group during installation or run the "
+#~ "following the command post-installation."
+#~ msgstr ""
+#~ "&FC; ???????????????????????????????????????????????????????????????\"Legacy Software "
+#~ "Development\"??????????????????????????????????????????????????????????????????????????????????????????"
+#~ "??????????????????????????????"
+
+#, fuzzy
+#~ msgid ""
+#~ "The following information represents the minimum hardware requirements "
+#~ "necessary to successfully install Fedora Core ."
+#~ msgstr ""
+#~ "?????????????????????????????? &DISTRO; &DISTROVER; test1 ???????????????????????????"
+#~ "??????"
+
+#~ msgid ""
+#~ "The compatibility/availability of other hardware components (such as "
+#~ "video and network cards) may be required for specific installation modes "
+#~ "and/or post-installation usage."
+#~ msgstr ""
+#~ "??????????????????????????????/????????????????????????????????????????????????????????? (??????????????????"
+#~ "???) ???????????????"
+
+#~ msgid "CPU Requirements"
+#~ msgstr "CPU ??????"
+
+#, fuzzy
+#~ msgid "This section lists the disk space required to install Fedora Core ."
+#~ msgstr "???????????????????????? &DISTRO; &DISTROVER; test1 ???????????????"
+
+#, fuzzy
+#~ msgid "This section lists the memory required to install Fedora Core ."
+#~ msgstr "???????????????????????? &DISTRO; &DISTROVER; test1 ???????????????"
+
+#~ msgid "This list is for 32-bit x86 systems:"
+#~ msgstr "??????????????? 32 ??? x86 ?????????"
+
+#~ msgid "Minimum for text-mode: 64MB"
+#~ msgstr "????????????????????????64MiB"
+
+#, fuzzy
+#~ msgid ""
+#~ "Installer package screen selection interface is being redesigned in the "
+#~ "Fedora development version. Fedora Core does not provide an option to "
+#~ "select the installation type such as Personal Desktop, Workstation, "
+#~ "Server and custom."
+#~ msgstr "?????????????????????????????????&FC; &LOCALVER; ??????????????????????????????"
+
+#~ msgid "x86_64 Installation Notes"
+#~ msgstr "x86_64 ????????????"
+
+#~ msgid "No differences installing for x86_64."
+#~ msgstr "X86_64 ?????????????????????"
+
+#~ msgid ""
+#~ "This section lists the minimum PowerPC (PPC) hardware needed to install "
+#~ "Fedora Core 4."
+#~ msgstr ""
+#~ "????????????????????? PowerPC (PPC) ????????? &FC; &LOCALVER; ??????????????????"
+#~ "??????"
+
+#~ msgid ""
+#~ "The bootloader should automatically boot the appropriate 32-bit or 64-bit "
+#~ "installer. Power management support, including sleep and backlight level "
+#~ "management, is present in the apmud package, which is in Fedora Extras. "
+#~ "Fedora Extras for Fedora Core is configured by default for yum. Following "
+#~ "installation, apmud can be installed by running yum install apmud."
+#~ msgstr ""
+#~ "????????????????????????????????? 32 ?????? 64 ????????????????????????????????????????????????????????????"
+#~ "???????????????????????? apmud ???????????????????????? &FEX; ??????"
+#~ "????????? &FC; ????????? &FEX; ???????????? yum ?????????"
+#~ "???????????????????????????????????????????????? yum install apmud ??????"
+#~ "??? apmud???"
From fedora-docs-commits at redhat.com Fri Mar 3 19:40:23 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 14:40:23 -0500
Subject: docs-common/common/entities Makefile,1.12,1.13
Message-ID: <200603031940.k23JeN3h024720@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/common/entities
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24526
Modified Files:
Makefile
Log Message:
Fixed template typo that wrote new .ENT files into a file called '@'.
You should now delete the '@' file in your copy of this directory.
Index: Makefile
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/Makefile,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- Makefile 3 Mar 2006 00:13:18 -0000 1.12
+++ Makefile 3 Mar 2006 19:40:16 -0000 1.13
@@ -175,7 +175,7 @@
#######################################################################
define ENT_template
entities-${1}.ent:: entities-${1}.xml entities.pot
- xsltproc -o @$@ --stringparam FDPCOMMONDIR "${FDPCOMMONDIR}" \
+ xsltproc -o $$@ --stringparam FDPCOMMONDIR "${FDPCOMMONDIR}" \
entities.xsl entities-${1}.xml
endef
$(foreach L,${PRI_LANG} ${OTHERS},$(eval $(call ENT_template,${L})))
From fedora-docs-commits at redhat.com Fri Mar 3 19:55:48 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 14:55:48 -0500
Subject: docs-common Makefile.common,1.88,1.89
Message-ID: <200603031955.k23Jtmh7024776@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24758
Modified Files:
Makefile.common
Log Message:
Added "-k" switch to ${XML2PO} usages to try and keep entity references
intact. This doesn't fix the whole problem, but it's a start.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.88
retrieving revision 1.89
diff -u -r1.88 -r1.89
--- Makefile.common 2 Mar 2006 22:01:34 -0000 1.88
+++ Makefile.common 3 Mar 2006 19:55:40 -0000 1.89
@@ -46,6 +46,12 @@
#########################################################################
#########################################################################
+# Strange though it may seem, some shells do not provide a ${PWD}
+# environment variable for us.
+PWD :=$(shell /bin/pwd)
+#########################################################################
+
+#########################################################################
# Supply default values for the boilerplate files _unless_ the user has
# provided their own values.
ifeq "${FDPDIR}" ""
@@ -90,12 +96,6 @@
#########################################################################
#########################################################################
-# Strange though it may seem, some shells do not provide a ${PWD}
-# environment variable for us.
-PWD :=$(shell /bin/pwd)
-#########################################################################
-
-#########################################################################
# Use macros to locate our commonly-used programs
XMLTO =xmlto
XSLTPROC=xsltproc
@@ -112,7 +112,7 @@
# from the gnome-doc-utils RPM.
.SUFFIXES: .po .pot .ent .xml
%.po: %.xml
- ${XML2PO} $< >$@
+ ${XML2PO} -k $< >$@
%.ent: %.xml
${XSLTPROC} -o $@ --stringparam FDPCOMMONDIR "NONE" \
@@ -394,7 +394,7 @@
#########################################################################
po/${DOCBASE}.pot:: ${XMLFILES-${PRI_LANG}}
[ -d po ] || (echo ADD po/ TO CVS >&2; exit 1)
- ${XML2PO} -o $@ $^
+ ${XML2PO} -k -o $@ $^
help::
@printf ${TFMT} 'po' 'Writes one ${PRI_LANG} PO file for all XML'
@@ -426,7 +426,7 @@
# original ${PRI_LANG} file and an updated po/${LANG}.po file.
define XML_template
$(patsubst ${PRI_LANG}/%,${1}/%,${2}):: ${2} po/${1}.po ${1}
- ${XML2PO} -p po/${1}.po ${2} >$$@
+ ${XML2PO} -k -p po/${1}.po ${2} >$$@
endef
$(foreach L,${OTHERS}, \
@@ -471,12 +471,10 @@
.PRECIOUS: po/${1}.po
-po/${1}.po:: ${XMLFILES-${PRI_LANG}} po/${DOCBASE}.pot
+po/${1}.po:: po/${DOCBASE}.pot
[ -d po ] || (echo ADD po/ TO CVS >&2; exit 1)
if [ ! -f $$@ ]; then \
cp po/${DOCBASE}.pot $$@; \
- else \
- ${MSGMERGE} -U --backup=simple $$@ po/${DOCBASE}.pot; \
fi
.PHONY: po-${1}
From fedora-docs-commits at redhat.com Fri Mar 3 20:39:28 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 15:39:28 -0500
Subject: docs-common Makefile.common,1.89,1.90
Message-ID: <200603032039.k23KdSuF026960@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26933
Modified Files:
Makefile.common
Log Message:
Deleted the 'DIR_template' foolishness and removed the "${LANG}" dummy
target, too. Replaced the explicit "mkdir -p ${LANG}" in the rule to
derive the non-${PRI_LANG} XML. This cuts down on the unnecessary
XML regeneration and speeds things up a good bit.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- Makefile.common 3 Mar 2006 19:55:40 -0000 1.89
+++ Makefile.common 3 Mar 2006 20:39:19 -0000 1.90
@@ -406,26 +406,11 @@
#########################################################################
#########################################################################
-define DIR_template
-${1}::
- mkdir -p ${1}
-
-distclean::
- ${RM} -r ${1}
-
-help::
- @printf ${TFMT} '${1}' 'Creates translated XML working directory'
-
-endef
-
-$(foreach L,${OTHERS},$(eval $(call DIR_template,${L})))
-#########################################################################
-
-#########################################################################
# Define a template to generate the locale-specific XML files given the
# original ${PRI_LANG} file and an updated po/${LANG}.po file.
define XML_template
-$(patsubst ${PRI_LANG}/%,${1}/%,${2}):: ${2} po/${1}.po ${1}
+$(patsubst ${PRI_LANG}/%,${1}/%,${2}):: ${2} po/${1}.po
+ mkdir -p ${1}
${XML2PO} -k -p po/${1}.po ${2} >$$@
endef
From fedora-docs-commits at redhat.com Fri Mar 3 20:46:37 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 15:46:37 -0500
Subject: docs-common Makefile.common,1.90,1.91
Message-ID: <200603032046.k23Kkb1m027010@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26989
Modified Files:
Makefile.common
Log Message:
Replaced ${MSGMERGE} processing to update .PO file when the .XML and
thus the .POT file changes.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -r1.90 -r1.91
--- Makefile.common 3 Mar 2006 20:39:19 -0000 1.90
+++ Makefile.common 3 Mar 2006 20:46:27 -0000 1.91
@@ -460,6 +460,8 @@
[ -d po ] || (echo ADD po/ TO CVS >&2; exit 1)
if [ ! -f $$@ ]; then \
cp po/${DOCBASE}.pot $$@; \
+ else \
+ ${MSGMERGE} -U -q $$@ $$<; \
fi
.PHONY: po-${1}
From fedora-docs-commits at redhat.com Fri Mar 3 20:49:54 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 15:49:54 -0500
Subject: docs-common/common/entities entities.pot,1.2,1.3
Message-ID: <200603032049.k23Kns3L027064@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/common/entities
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27026/common/entities
Modified Files:
entities.pot
Log Message:
When validating XML, be sure to include the dependent files such as
${1}/fdp-info.xml and ${1}/${DOC_ENTITIES}.ent so there is actually a
hope of the XML validating.
Index: entities.pot
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities.pot,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities.pot 3 Mar 2006 00:13:18 -0000 1.2
+++ entities.pot 3 Mar 2006 20:49:45 -0000 1.3
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-02 18:04-0600\n"
+"POT-Creation-Date: 2006-03-03 10:22-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
From fedora-docs-commits at redhat.com Fri Mar 3 20:49:47 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 15:49:47 -0500
Subject: docs-common Makefile.common,1.91,1.92
Message-ID: <200603032050.k23KoKFt027067@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27026
Modified Files:
Makefile.common
Log Message:
When validating XML, be sure to include the dependent files such as
${1}/fdp-info.xml and ${1}/${DOC_ENTITIES}.ent so there is actually a
hope of the XML validating.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -r1.91 -r1.92
--- Makefile.common 3 Mar 2006 20:46:27 -0000 1.91
+++ Makefile.common 3 Mar 2006 20:49:35 -0000 1.92
@@ -807,7 +807,7 @@
.PHONY: validate-xml-${1}
-validate-xml-${1}:: ${XMLFILES-${1}} ${1}/fdp-info.xml set-locale-${1}
+validate-xml-${1}:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
${XMLLINT} --noout --xinclude --postvalid ${1}/${DOCBASE}.xml
help::
From fedora-docs-commits at redhat.com Fri Mar 3 23:20:46 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 18:20:46 -0500
Subject: docs-common/common/entities Makefile, 1.13, 1.14 entities-de.ent,
1.1, 1.2 entities-en.ent, 1.4, 1.5 entities-en_US.ent, 1.1,
1.2 entities-it.ent, 1.10, 1.11 entities-pt_BR.ent, 1.4,
1.5 entities-ru.ent, 1.3, 1.4 entities-zh_CN.ent, 1.3,
1.4 entities.pot, 1.3, 1.4
Message-ID: <200603032320.k23NKkxP001530@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/common/entities
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1486/common/entities
Modified Files:
Makefile entities-de.ent entities-en.ent entities-en_US.ent
entities-it.ent entities-pt_BR.ent entities-ru.ent
entities-zh_CN.ent entities.pot
Log Message:
Place the per-document entities file in the ${LANG}/ directory, where
it belonged all along. Using relative paths from within the local
entities should work the same as relative paths elsewhere. With
using the symbolic link "../doc-entities.ent" previously, relative
paths within the per-document entities had to be relative to the
parent directory unlike all other relative paths in the document.
Index: Makefile
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/Makefile,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- Makefile 3 Mar 2006 19:40:16 -0000 1.13
+++ Makefile 3 Mar 2006 23:20:38 -0000 1.14
@@ -32,7 +32,7 @@
#######################################################################
# FDPCOMMONDIR:=$(shell cd .. && /bin/pwd)
-FDPCOMMONDIR:=../docs-common/common
+FDPCOMMONDIR:=../../docs-common/common
#######################################################################
#######################################################################
Index: entities-de.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-de.ent,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entities-de.ent 2 Mar 2006 18:15:12 -0000 1.1
+++ entities-de.ent 3 Mar 2006 23:20:38 -0000 1.2
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-en.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-en.ent,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- entities-en.ent 2 Mar 2006 22:52:15 -0000 1.4
+++ entities-en.ent 3 Mar 2006 23:20:38 -0000 1.5
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-en_US.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-en_US.ent,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entities-en_US.ent 2 Mar 2006 22:52:15 -0000 1.1
+++ entities-en_US.ent 3 Mar 2006 23:20:38 -0000 1.2
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-it.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-it.ent,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- entities-it.ent 1 Mar 2006 19:51:00 -0000 1.10
+++ entities-it.ent 3 Mar 2006 23:20:38 -0000 1.11
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-pt_BR.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-pt_BR.ent,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- entities-pt_BR.ent 1 Mar 2006 18:56:05 -0000 1.4
+++ entities-pt_BR.ent 3 Mar 2006 23:20:38 -0000 1.5
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-ru.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-ru.ent,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- entities-ru.ent 1 Mar 2006 01:14:00 -0000 1.3
+++ entities-ru.ent 3 Mar 2006 23:20:38 -0000 1.4
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-zh_CN.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-zh_CN.ent,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- entities-zh_CN.ent 1 Mar 2006 01:14:00 -0000 1.3
+++ entities-zh_CN.ent 3 Mar 2006 23:20:38 -0000 1.4
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities.pot
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities.pot,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- entities.pot 3 Mar 2006 20:49:45 -0000 1.3
+++ entities.pot 3 Mar 2006 23:20:38 -0000 1.4
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-03 10:22-0600\n"
+"POT-Creation-Date: 2006-03-03 15:18-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
From fedora-docs-commits at redhat.com Fri Mar 3 23:20:40 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 18:20:40 -0500
Subject: docs-common Makefile.common,1.92,1.93
Message-ID: <200603032321.k23NLBPC001539@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1486
Modified Files:
Makefile.common
Log Message:
Place the per-document entities file in the ${LANG}/ directory, where
it belonged all along. Using relative paths from within the local
entities should work the same as relative paths elsewhere. With
using the symbolic link "../doc-entities.ent" previously, relative
paths within the per-document entities had to be relative to the
parent directory unlike all other relative paths in the document.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -r1.92 -r1.93
--- Makefile.common 3 Mar 2006 20:49:35 -0000 1.92
+++ Makefile.common 3 Mar 2006 23:20:32 -0000 1.93
@@ -781,14 +781,11 @@
set-locale-${1}::
${LN} -f -s ${FDPDIR}/docs-common/common/entities/entities-${1}.ent \
${FDP_ENTITIES}
-ifneq "${DOC_ENTITIES}" ""
- ${LN} -f -s ${1}/${DOC_ENTITIES}.ent .
-endif
clean::
${RM} ${FDP_ENTITIES}
ifneq "${DOC_ENTITIES}" ""
- ${RM} ${DOC_ENTITIES}.ent
+ ${RM} ${1}/${DOC_ENTITIES}.ent
endif
help::
From fedora-docs-commits at redhat.com Fri Mar 3 23:25:07 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 18:25:07 -0500
Subject: docs-common/common/entities Makefile, 1.14, 1.15 entities-de.ent,
1.2, 1.3 entities-en.ent, 1.5, 1.6 entities-en_US.ent, 1.2,
1.3 entities-it.ent, 1.11, 1.12 entities-pt_BR.ent, 1.5,
1.6 entities-ru.ent, 1.4, 1.5 entities-zh_CN.ent, 1.4,
1.5 entities.pot, 1.4, 1.5
Message-ID: <200603032325.k23NP7Ia001584@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/common/entities
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1555
Modified Files:
Makefile entities-de.ent entities-en.ent entities-en_US.ent
entities-it.ent entities-pt_BR.ent entities-ru.ent
entities-zh_CN.ent entities.pot
Log Message:
Corrected the default relative path. Yes, this is back to the
original value. Live and learn.
Index: Makefile
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/Makefile,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- Makefile 3 Mar 2006 23:20:38 -0000 1.14
+++ Makefile 3 Mar 2006 23:24:59 -0000 1.15
@@ -32,7 +32,7 @@
#######################################################################
# FDPCOMMONDIR:=$(shell cd .. && /bin/pwd)
-FDPCOMMONDIR:=../../docs-common/common
+FDPCOMMONDIR:=../docs-common/common
#######################################################################
#######################################################################
Index: entities-de.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-de.ent,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities-de.ent 3 Mar 2006 23:20:38 -0000 1.2
+++ entities-de.ent 3 Mar 2006 23:24:59 -0000 1.3
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-en.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-en.ent,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- entities-en.ent 3 Mar 2006 23:20:38 -0000 1.5
+++ entities-en.ent 3 Mar 2006 23:24:59 -0000 1.6
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-en_US.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-en_US.ent,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities-en_US.ent 3 Mar 2006 23:20:38 -0000 1.2
+++ entities-en_US.ent 3 Mar 2006 23:24:59 -0000 1.3
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-it.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-it.ent,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- entities-it.ent 3 Mar 2006 23:20:38 -0000 1.11
+++ entities-it.ent 3 Mar 2006 23:24:59 -0000 1.12
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-pt_BR.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-pt_BR.ent,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- entities-pt_BR.ent 3 Mar 2006 23:20:38 -0000 1.5
+++ entities-pt_BR.ent 3 Mar 2006 23:24:59 -0000 1.6
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-ru.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-ru.ent,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- entities-ru.ent 3 Mar 2006 23:20:38 -0000 1.4
+++ entities-ru.ent 3 Mar 2006 23:24:59 -0000 1.5
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-zh_CN.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-zh_CN.ent,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- entities-zh_CN.ent 3 Mar 2006 23:20:38 -0000 1.4
+++ entities-zh_CN.ent 3 Mar 2006 23:24:59 -0000 1.5
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities.pot
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities.pot,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- entities.pot 3 Mar 2006 23:20:38 -0000 1.4
+++ entities.pot 3 Mar 2006 23:24:59 -0000 1.5
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-03 15:18-0600\n"
+"POT-Creation-Date: 2006-03-03 17:24-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
From fedora-docs-commits at redhat.com Sat Mar 4 01:28:57 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 3 Mar 2006 20:28:57 -0500
Subject: docs-common Makefile.common,1.93,1.94
Message-ID: <200603040128.k241SvZ7005939@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5916
Modified Files:
Makefile.common
Log Message:
${PO2XML} is back!! You need the "kdesdk" RPM after all!! Sorry!!
Evidently, the XML merge mode of xml2po(1) is broken; at least I
could never get it to work reliably. The worst bug is that it
doesn't handle "&FOO;"-style entities reliably: sometimes they get
substituted, even if the "-k" switch is used and often times they are
simply dropped from the output XML. Boo!
Using po2xml(1) doesn't fix everything, but it's a step.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -r1.93 -r1.94
--- Makefile.common 3 Mar 2006 23:20:32 -0000 1.93
+++ Makefile.common 4 Mar 2006 01:28:47 -0000 1.94
@@ -104,6 +104,7 @@
XMLLINT =xmllint
XML2PO =xml2po
MSGMERGE=msgmerge
+PO2XML =po2xml
LN =ln
#########################################################################
@@ -411,9 +412,10 @@
define XML_template
$(patsubst ${PRI_LANG}/%,${1}/%,${2}):: ${2} po/${1}.po
mkdir -p ${1}
- ${XML2PO} -k -p po/${1}.po ${2} >$$@
-endef
-
+# ${XML2PO} -k -p po/${1}.po ${2} >$$@
+ ${PO2XML} ${2} po/${1}.po >$$@
+ endef
+
$(foreach L,${OTHERS}, \
$(foreach F,${XMLFILES-${PRI_LANG}}, \
$(eval $(call XML_template,${L},${F}))))
From fedora-docs-commits at redhat.com Sat Mar 4 06:21:58 2006
From: fedora-docs-commits at redhat.com (Hugo Cisneiros (eitch))
Date: Sat, 4 Mar 2006 01:21:58 -0500
Subject: release-notes Makefile,1.28,1.29
Message-ID: <200603040621.k246Lwar016117@cvs-int.fedora.redhat.com>
Author: eitch
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16097
Modified Files:
Makefile
Log Message:
added pt_BR target
Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- Makefile 1 Mar 2006 22:18:00 -0000 1.28
+++ Makefile 4 Mar 2006 06:21:50 -0000 1.29
@@ -8,7 +8,7 @@
#
DOCBASE = RELEASE-NOTES
PRI_LANG = en
-OTHERS = zh_CN #it pa ru
+OTHERS = zh_CN pt_BR #it pa ru
########################################################################
# List each XML file of your document in the template below. Append the
From fedora-docs-commits at redhat.com Sat Mar 4 06:24:16 2006
From: fedora-docs-commits at redhat.com (Hugo Cisneiros (eitch))
Date: Sat, 4 Mar 2006 01:24:16 -0500
Subject: release-notes/po pt_BR.po,NONE,1.1
Message-ID: <200603040624.k246OGMA016162@cvs-int.fedora.redhat.com>
Author: eitch
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16144
Added Files:
pt_BR.po
Log Message:
finished pt_BR translation, now doing final revision
--- NEW FILE pt_BR.po ---
# translation of pt_BR.po to Brazilian Portuguese
# Hugo Cisneiros , 2006.
msgid ""
msgstr ""
"Project-Id-Version: pt_BR\n"
"POT-Creation-Date: 2006-03-01 17:42-0300\n"
"PO-Revision-Date: 2006-03-04 02:59-0300\n"
"Last-Translator: Hugo Cisneiros \n"
"Language-Team: Brazilian Portuguese \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"
#: en/Xorg.xml:5(title) en/Welcome.xml:5(title) en/WebServers.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)
msgid "Temp"
msgstr "Tempor??rio"
#: en/Xorg.xml:8(title)
msgid "X Window System (Graphics)"
msgstr "X Window System (Gr??fico)"
#: en/Xorg.xml:9(para)
msgid "This section contains information related to the X Window System implementation provided with Fedora."
msgstr "Esta se????o cont??m informa????es relacionadas a implementa????o do X Window System (Sistema de Janelas X), fornecido com o Fedora."
#: en/Xorg.xml:11(title)
msgid "xorg-x11"
msgstr "xorg-x11"
#: en/Xorg.xml:12(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 http://xorg.freedesktop.org/wiki/."
msgstr "O X.org X11 ?? uma implementa????o de c??digo aberto do X Window System (Sistema de Janelas X). Ele fornece as funcionalidades de baixo n??vel b??sicas para que as completas interfaces gr??ficas de usu??rios (GUI) como por exemplo o GNOME e KDE sejam feitas. Para mais informa????es sobre o X.org, veja em http://xorg.freedesktop.org/wiki/."
#: en/Xorg.xml:13(para)
msgid "You may use Applications > System Settings > Display or system-config-display to configure the settings. The configuration file for X.org is located in /etc/X11/xorg.conf."
msgstr "Para configurar as op????es, voc?? pode entrar em Aplica????es > Configura????es de Sistema > Tela ou use o comando system-config-display. O arquivo de configura????o do X.org est?? localizado em /etc/X11/xorg.conf."
#: 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 http://fedoraproject.org/wiki/Xorg/Modularization."
msgstr "O X.org X11R7 ?? a primeira vers??o modular do X.org, que al??m de muitos outros benef??cios, promove atualiza????es mais r??pidas e ajuda os programadores a desenvolver mais r??pido e lan??ar componentes espec??ficos. Mais informa????es sobre a situa????o atual do esfor??o de modulariza????o do X.org no Fedora est??o dispon??veis em http://fedoraproject.org/wiki/Xorg/Modularization."
#: en/Xorg.xml:17(title)
msgid "X.org X11R7 End-User Notes"
msgstr "Notas de Usu??rio do X.org X11R7"
#: en/Xorg.xml:19(title)
msgid "Installing Third Party Drivers"
msgstr "Instalando Drivers de Terceiros"
#: en/Xorg.xml:20(para)
msgid "Before you install any third party drivers from any vendor, including ATI or nVidia, please read http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers."
msgstr "Antes de voc?? instalar qualquer driver de terceiros, incluindo os da ATI e nVidia, por favor leia a p??gina http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers."
#: en/Xorg.xml:25(para)
msgid "The xorg-x11-server-Xorg package install scripts automatically remove the RgbPath line from the xorg.conf 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 xorg at freedesktop.org mailing list if you do need assistance reconfiguring your keyboard."
msgstr "Os scripts de instala????o do pacote xorg-x11-server-Xorg automaticamente removem a linha RgbPath do arquivo xorg.conf caso esteja presente. Voc?? pode precisar reconfigurar seu teclado diferentemente do que est?? acostumado. ?? sugerido que voc?? se inscreva na lista de discuss??o xorg at freedesktop.org caso voc?? precise de assist??ncia na reconfigura????o do seu teclado."
#: en/Xorg.xml:28(title)
msgid "X.org X11R7 Developer Overview"
msgstr "Vis??o Geral de Desenvolvedor do X.org X11R7"
#: en/Xorg.xml:29(para)
msgid "The following list includes some of the more visible changes for developers in X11R7:"
msgstr "A seguinte lista inclui algumas das mudan??as vis??veis para os desenvolvedores no X11R7:"
#: en/Xorg.xml:32(para)
msgid "The entire buildsystem has changed from imake to the GNU autotools collection."
msgstr "Todo o sistema de compila????o foi mudado da ferramenta imake para a cole????o GNU autotools."
#: en/Xorg.xml:35(para)
msgid "Libraries now install pkgconfig*.pc files, which should now always be used by software that depends on these libraries, instead of hard coding paths to them in /usr/X11R6/lib or elsewhere."
msgstr "Agora as bibliotecas instalam arquivos *.pc do pkgconfig, que agora devem ser sempre usados por programas que dependem dessas bibliotecas, ao inv??s de escrever os caminhos diretamente no c??digo como /usr/X11R6/lib ou algo parecido."
#: en/Xorg.xml:40(para)
msgid "Everything is now installed directly into /usr instead of /usr/X11R6. All software that hard codes paths to anything in /usr/X11R6 must now be changed, preferably to dynamically detect the proper location of the object. Developers are strongly advised against hard-coding the new X11R7 default paths."
msgstr "Agora tudo ?? instalado diretamente em /usr ao inv??s de /usr/X11R6. Todos os programas que escrevem caminhos diretamente no c??digo para /usr/X11R6 devem ser mudados, de prefer??ncia para detectar din??micamente a localiza????o correta do objeto. Desenvolvedores s??o fortemente recomendados a n??o escrever os caminhos diretamente no c??digo para os novo padr??es do X11R7."
#: en/Xorg.xml:45(para)
msgid "Every library has its own private source RPM package, which creates a runtime binary subpackage and a -devel subpackage."
msgstr "Cada biblioteca tem seu pr??prio pacote-fonte RPM privado, ao qual cria sub-pacotes com bin??rios de execu????o e sub-pacotes -devel."
#: en/Xorg.xml:50(title)
msgid "X.org X11R7 Developer Notes"
msgstr "Notas de Desenvolvedor do X.org X11R7"
#: en/Xorg.xml:51(para)
msgid "This section includes a summary of issues of note for developers and packagers, and suggestions on how to fix them where possible."
msgstr "Esta se????o inclui um sum??rio de notas de problemas para os desenvolvedores e empacotadores, com sugest??es de como corrigir quando poss??vel."
#: en/Xorg.xml:53(title)
msgid "The /usr/X11R6/ Directory Hierarchy"
msgstr "A Hierarquia de Diret??rio /usr/X11R6/"
#: en/Xorg.xml:54(para)
msgid "X11R7 files install into /usr directly now, and no longer use the /usr/X11R6/ hierarchy. Applications that rely on files being present at fixed paths under /usr/X11R6/, either at compile time or run time, must be updated. They should now use the system PATH, or some other mechanism to dynamically determine where the files reside, or alternatively to hard code the new locations, possibly with fallbacks."
msgstr "Os arquivos do X11R7 agora s??o instalados diretamente no /usr e n??o usam mais a hierarquia /usr/X11R6/. As aplica????es que dependem de arquivos presentes em caminhos fixos dentro do /usr/X11R6/ devem ser atualizados ou no tempo de compila????o, ou no tempo de execu????o. Elas agora devem usar o PATH, ou algum outro mecanismo que determina din??micamente onde os arquivos residem, ou alternativamente escrever as novas localiza????es direto no c??digo possivelmente gerando recuos futuros."
#: en/Xorg.xml:59(title)
msgid "Imake"
msgstr "Imake"
#: en/Xorg.xml:60(para)
msgid "The imake utility is no longer used to build the X Window System, and is now officially deprecated. X11R7 includes imake, xmkmf, and other build utilities previously supplied by the X Window System. X.Org highly recommends, however, that people migrate from imake to use GNU autotools and pkg-config. Support for imake may be removed in a future X Window System release, so developers are strongly encouraged to transition away from it, and not use it for any new software projects."
msgstr "O utilit??rio imake n??o ?? mais usado na constru????o do X Window System, e agora est?? oficialmente fora-de-uso. O X11R7 inclui o imake, xmkmf, e outros utilit??rios de compila????o pr??viamente fornecidos pelo X Window System. Entretanto, o X.org recomenda altamente que as pessoas migrem do imake para usar as ferramentas GNU autotools e pkg-config. O suporte ao imake pode ser removido em uma futura vers??o do X Window System, ent??o os desenvolvedores s??o fortemente encorajados a mudar e n??o us??-lo em nenhum outro novo projeto de programa."
#: en/Xorg.xml:63(title)
msgid "The Systemwide app-defaults/ Directory"
msgstr "O Diret??rio Global app-defaults/"
#: en/Xorg.xml:64(para)
msgid "The system app-defaults/ directory for X resources is now %{_datadir}/X11/app-defaults, which expands to /usr/share/X11/app-defaults/ on Fedora Core 5 and for future Red Hat Enterprise Linux systems."
msgstr "O diret??rio de sistema para recursos do X app-defaults/ agora fica em %{_datadir}/X11/app-defaults, que expande para /usr/share/X11/app-defaults/ no Fedora Core 5 e para sistemas futuros do Red Hat Enterprise Linux."
#: en/Xorg.xml:67(title)
msgid "Correct Package Dependencies"
msgstr "Corretas Depend??ncias de Pacotes"
#: en/Xorg.xml:68(para)
msgid "Any software package that previously used BuildRequires: (XFree86-devel|xorg-x11-devel) to satisfy build dependencies must now individually list each library dependency. The preferred and recommended method is to use virtual build dependencies instead of hard coding the library package names of the xorg implementation. This means you should use BuildRequires: libXft-devel instead of BuildRequires: xorg-x11-Xft-devel. If your software truly does depend on the X.Org X11 implementation of a specific library, and there is no other clean or safe way to state the dependency, then use the xorg-x11-devel form. If you use the virtual provides/requires mechanism, you will avoid inconvenience if the libraries move to another location in the future."
msgstr "Qualquer programa que anteriormente usou BuildRequires: (XFree86-devel|xorg-x11-devel) para satisfazer as depend??ncias de compila????o agora devem listar cada depend??ncia de biblioteca individualmente. O m??todo preferido e recomendado ?? o uso de depend??ncias de compila????o virtuais ao inv??s de escrever os nomes de pacotes de bibliotecas da implementa????o xorg diretamente no c??digo. Isso significa que voc?? deve usar BuildRequires: libXft-devel ao inv??s de BuildRequires: xorg-x11-Xft-devel. Se o seu programa depende muito de uma implementa????o X.Org X11 de uma biblioteca espec??fica, e n??o h?? outros meios limpos e seguros de satisfazer a depend??ncia, ent??o use a forma xorg-x11-devel. Se voc?? usar mecanismos virtuais, voc?? ir?? evitar incoveni??ncias futuras caso as bibliotecas mudem de localiza????o."
#: en/Xorg.xml:74(title)
msgid "xft-config"
msgstr "xft-config"
#: en/Xorg.xml:75(para)
msgid "Modular X now uses GNU autotools and pkg-config for its buildsystem configuration and execution. The xft-config utility has been deprecated for some time, and pkgconfig*.pc files have been provided for most of this time. Applications that previously used xft-config to obtain the Cflags or libs build options must now be updated to use pkg-config."
msgstr "O X modular agora usa as ferramentas GNU autotools e pkg-config para configura????o e execu????o do seu sistema de compila????o. O utilit??rio xft-config est?? sem uso h?? algum tempo, e os arquivos *.pc do pkgconfig est??o sendo fornecidos por um bom tempo. Aplica????es que antes usavam o xft-config para obter as op????es de constru????o Cflags ou libs agora devem ser atualizadas para usar o pkg-config."
#: en/Welcome.xml:8(title)
msgid "Welcome to Fedora Core"
msgstr "Bem vindo ao Fedora Core"
#: en/Welcome.xml:10(title)
msgid "Latest Release Notes on the Web"
msgstr "??ltimas Notas de Vers??o na Web"
#: en/Welcome.xml:11(para)
msgid "These release notes may be updated. Visit http://fedora.redhat.com/docs/release-notes/ to view the latest release notes for Fedora Core 5."
msgstr "Estas notas de vers??o podem ser atualizadas. Visite http://fedora.redhat.com/docs/release-notes/ para ver as ??ltimas notas de vers??o para o Fedora Core 5."
#: en/Welcome.xml:15(para)
msgid "You can help the Fedora Project community continue to improve Fedora if you file bug reports and enhancement requests. Refer to http://fedoraproject.org/wiki/BugsAndFeatureRequests for more information about bugs. Thank you for your participation."
msgstr "Voc?? pode ajudar a comunidade do Projeto Fedora a continuar aperfei??oando o Fedora se voc?? relatar bugs ou pedir por aprimoramentos. Veja em http://fedoraproject.org/wiki/BugsAndFeatureRequests para mais informa????es sobre bugs. Obrigado por sua participa????o."
#: en/Welcome.xml:16(para)
msgid "To find out more general information about Fedora, refer to the following Web pages:"
msgstr "Para encontrar mais informa????es gerais sobre o Fedora, veja as seguintes p??ginas Web:"
#: en/Welcome.xml:19(para)
msgid "Fedora Overview (http://fedoraproject.org/wiki/Overview)"
msgstr "Vis??o Geral do Fedora (http://fedoraproject.org/wiki/Overview)"
#: en/Welcome.xml:22(para)
msgid "Fedora FAQ (http://fedoraproject.org/wiki/FAQ)"
msgstr "FAQ do Fedora (http://fedoraproject.org/wiki/FAQ)"
#: en/Welcome.xml:25(para)
msgid "Help and Support (http://fedoraproject.org/wiki/Communicate)"
msgstr "Ajuda e Suporte (http://fedoraproject.org/wiki/Communicate)"
#: en/Welcome.xml:28(para)
msgid "Participate in the Fedora Project (http://fedoraproject.org/wiki/HelpWanted)"
msgstr "Participe no Projeto Fedora (http://fedoraproject.org/wiki/HelpWanted)"
#: en/Welcome.xml:31(para)
msgid "About the Fedora Project (http://fedora.redhat.com/About/)"
msgstr "Sobre o Projeto Fedora (http://fedora.redhat.com/About/)"
#: en/WebServers.xml:8(title)
msgid "Web Servers"
msgstr "Servidores Web"
#: en/WebServers.xml:9(para)
msgid "This section contains information on Web-related applications."
msgstr "Esta se????o cont??m informa????es sobre aplica????es relacionadas a Web."
#: en/WebServers.xml:11(title)
msgid "httpd"
msgstr "httpd"
#: en/WebServers.xml:12(para)
msgid "Fedora Core now includes version 2.2 of the Apache HTTP Server. This release brings a number of improvements over the 2.0 series, including:"
msgstr "O Fedora Core agora inclui a vers??o 2.2 do Servidor HTTP Apache. Esta vers??o traz alguns aprimoramentos em rela????o a s??rie 2.0, incluindo:"
#: en/WebServers.xml:15(para)
msgid "greatly improved caching modules (mod_cache, mod_disk_cache, mod_mem_cache)"
msgstr "m??dulos de caching bastante aprimorados (mod_cache, mod_disk_cache, mod_mem_cache)"
#: en/WebServers.xml:18(para)
msgid "a new structure for authentication and authorization support, replacing the security modules provided in previous versions"
msgstr "uma nova estrutura de suporte a autentica????o e autoriza????o, substituindo os m??dulos de seguran??a fornecidos em vers??es passadas"
#: en/WebServers.xml:21(para)
msgid "support for proxy load balancing (mod_proxy_balance)"
msgstr "suporte a balanceamento de carga de proxy (mod_proxy_balance)"
#: en/WebServers.xml:24(para)
[...2299 lines suppressed...]
msgid "Recommended for graphical: 256MiB"
msgstr "Recomendado para a interface gr??fica: 256MiB"
#: en/ArchSpecificx86.xml:44(title) en/ArchSpecificx86_64.xml:29(title) en/ArchSpecificPPC.xml:33(title)
msgid "Hard Disk Space Requirements"
msgstr "Exig??ncias de Espaco no Disco R??gido"
#: en/ArchSpecificx86.xml:45(para) en/ArchSpecificx86_64.xml:30(para)
msgid "The disk space requirements listed below represent the disk space taken up by Fedora Core 5 after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img on Installation Disc 1 plus the size of the files in /var/lib/rpm on the installed system."
msgstr "As exig??ncias de espa??o em disco listadas abaixo representam o espa??o em disco usado pelo Fedora Core 5 depois que uma instala????o ?? completada. Entretando, espa??o em disco adicional ?? necess??rio durante a instala????o para suportar o ambiente do instalador. Este espa??o em disco adicional corresponde ao tamanho do arquivo /Fedora/base/stage2.img no Disco de Instala????o 1, mais o tamanho dos arquivos do diret??rio /var/lib/rpm no sistema instalado."
#: en/ArchSpecificx86.xml:46(para) en/ArchSpecificx86_64.xml:31(para) en/ArchSpecificPPC.xml:35(para)
msgid "In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an \"everything\" installation. The complete packages can occupy over 9 GB of disk space."
msgstr "Em termos pr??ticos, as exig??ncias de espa??o adicional podem ir de 90 MiB para uma instala????o m??nima, at?? 175 MiB para uma instala????o de \"tudo\". Os pacotes completos podem ocupar mais de 9 GB de espa??o em disco."
#: en/ArchSpecificx86.xml:47(para) en/ArchSpecificx86_64.xml:32(para) en/ArchSpecificPPC.xml:36(para)
msgid "Additional space is also required for any user data, and at least 5% free space should be maintained for proper system operation."
msgstr "Espa??o adicional tamb??m pode ser necess??rio para dados do usu??rio, e ao menos 5% de espa??o livre deve ser mantido para uma opera????o apropriada do sistema."
#: en/ArchSpecificx86_64.xml:8(title)
msgid "x86_64 Specifics for Fedora"
msgstr "Casos espec??ficos para x86_64 no Fedora"
#: en/ArchSpecificx86_64.xml:9(para)
msgid "This section covers any specific information you may need to know about Fedora Core and the x86_64 hardware platform."
msgstr "Esta se????o cobre qualquer informa????o espec??fica que voc?? possa precisar saber sobre o Fedora Core e a plataforma de hardware x86_64."
#: en/ArchSpecificx86_64.xml:11(title)
msgid "x86_64 Hardware Requirements"
msgstr "Exig??ncias para Hardwares x86_64"
#: en/ArchSpecificx86_64.xml:14(title)
msgid "Memory Requirements"
msgstr "Exig??ncias de Mem??ria"
#: en/ArchSpecificx86_64.xml:15(para)
msgid "This list is for 64-bit x86_64 systems:"
msgstr "Esta lista ?? para sistemas x86_64 de 64-bits:"
#: en/ArchSpecificx86_64.xml:21(para)
msgid "Minimum RAM for graphical: 256MiB"
msgstr "Mem??ria RAM m??nima para a interface gr??fica: 256MiB"
#: en/ArchSpecificx86_64.xml:24(para)
msgid "Recommended RAM for graphical: 512MiB"
msgstr "Mem??ria RAM recomendada para a interface gr??fica: 512MiB"
#: en/ArchSpecificx86_64.xml:36(title)
msgid "RPM Multiarch Support on x86_64"
msgstr "Suporte a Multiarquitetura RPM em x86_64"
#: en/ArchSpecificx86_64.xml:37(para)
msgid "RPM supports parallel installation of multiple architectures of the same package. A default package listing such as rpm -qa might appear to include duplicate packages, since the architecture is not displayed. Instead, use the repoquery command, part of the yum-utils package in Fedora Extras, which displays architecture by default. To install yum-utils, run the following command:"
msgstr "O RPM suporte a instala????o paralela de m??ltiplas arquiteturas de um mesmo pacote. Um pacote padr??o listado com rpm -qa pode aparecer com pacotes duplicados, j?? que a arquitetura n??o ?? mostrada. Ao inv??s disso, use o comando repoquery, parte do pacote yum-utils no Fedora Extras, o qual mostra a arquitetura por padr??o. Para instalar o yum-utils, execute o seguinte comando:"
#: en/ArchSpecificx86_64.xml:39(screen)
#, no-wrap
msgid "su -c 'yum install yum-utils' "
msgstr "su -c 'yum install yum-utils' "
#: en/ArchSpecificx86_64.xml:40(para)
msgid "To list all packages with their architecture using rpm, run the following command:"
msgstr "Para listar todos os pacotes com suas arquiteturas utilizando o rpm, execute o seguinte comando:"
#: en/ArchSpecificx86_64.xml:41(screen)
#, no-wrap
msgid "rpm -qa --queryformat \"%{name}-%{version}-%{release}.%{arch}\\n\" "
msgstr "rpm -qa --queryformat \"%{name}-%{version}-%{release}.%{arch}\\n\" "
#: en/ArchSpecificPPC.xml:8(title)
msgid "PPC Specifics for Fedora"
msgstr "Casos espec??ficos para PPC no Fedora"
#: en/ArchSpecificPPC.xml:9(para)
msgid "This section covers any specific information you may need to know about Fedora Core and the PPC hardware platform."
msgstr "Esta se????o cobre qualquer informa????o espec??fica que voc?? possa precisar saber sobre o Fedora e a plataforma de hardware PPC."
#: en/ArchSpecificPPC.xml:11(title)
msgid "PPC Hardware Requirements"
msgstr "Exig??ncias para Hardwares PPC"
#: en/ArchSpecificPPC.xml:13(title)
msgid "Processor and Memory"
msgstr "Processador e Mem??ria"
#: en/ArchSpecificPPC.xml:16(para)
msgid "Minimum CPU: PowerPC G3 / POWER4"
msgstr "Processador M??nimo: PowerPC G3 / POWER4"
#: en/ArchSpecificPPC.xml:19(para)
msgid "Fedora Core 5 supports only the ???New World??? generation of Apple Power Macintosh, shipped from circa 1999 onward."
msgstr "O Fedora Core 5 suporta paenas a gera????o ???Novo Mundo??? do Apple Power Macintosh, distribu??do a partir do circa de 1999 em diante."
#: en/ArchSpecificPPC.xml:22(para)
msgid "Fedora Core 5 also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines."
msgstr "O Fedora Core 5 tamb??m suporta m??quinas IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, e IBM Cell Broadband Engine."
#: en/ArchSpecificPPC.xml:25(para)
msgid "Recommended for text-mode: 233 MHz G3 or better, 128MiB RAM."
msgstr "Recomendado para modo texto: G3 de 233MHz ou superior, 128MiB de RAM."
#: en/ArchSpecificPPC.xml:28(para)
msgid "Recommended for graphical: 400 MHz G3 or better, 256MiB RAM."
msgstr "Recomendado para a interface gr??fica: G3 de 400MHz ou superior, 256MiB de RAM."
#: en/ArchSpecificPPC.xml:34(para)
msgid "The disk space requirements listed below represent the disk space taken up by Fedora Core 5 after installation is complete. However, additional disk space is required during installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on Installtion Disc 1) plus the size of the files in /var/lib/rpm on the installed system."
msgstr "As exig??ncias de espa??o em disco listadas abaixo representam o espa??o em disco usado pelo Fedora Core 5 depois que uma instala????o ?? completada. Entretando, espa??o em disco adicional ?? necess??rio durante a instala????o para suportar o ambiente do instalador. Este espa??o em disco adicional corresponde ao tamanho do arquivo /Fedora/base/stage2.img no Disco de Instala????o 1, mais o tamanho dos arquivos do diret??rio /var/lib/rpm no sistema instalado."
#: en/ArchSpecificPPC.xml:40(title)
msgid "The Apple keyboard"
msgstr "O teclado Apple"
#: en/ArchSpecificPPC.xml:41(para)
msgid "The Option key on Apple systems is equivalent to the Alt key on the PC. Where documentation and the installer refer to the Alt key, use the Option key. For some key combinations you may need to use the Option key in conjunction with the Fn key, such as Option-Fn-F3 to switch to virtual terminal tty3."
msgstr "A tecla Op????o em sistemas Apple ?? equivalente ?? tecla Alt no PC. Quando a documenta????o e o instalador se referirem a tecla Alt, use a tecla Option. Para algumas combina????es de teclas, voc?? pode precisar usar a tecla Option em conjunto com a tecla Fn, como por exemplo Option-Fn-F3 para mudar para o terminal virtual tty3."
#: en/ArchSpecificPPC.xml:44(title)
msgid "PPC Installation Notes"
msgstr "Notas de Instala????o em PPC"
#: en/ArchSpecificPPC.xml:45(para)
msgid "Fedora Core Installation Disc 1 is bootable on supported hardware. In addition, a bootable CD image appears in the images/ directory of this disc. These images will behave differently according to your system hardware:"
msgstr "O Disco de Instala????o 1 do Fedora Core ?? boot??vel em hardwares que o suportam. Al??m disso, a imagem boot??vel do CD est?? no diret??rio images do disco. Estas imagens podem se comportar diferentemente de acordo com o seu hardware:"
#: en/ArchSpecificPPC.xml:48(para)
msgid "Apple Macintosh"
msgstr "Apple Macintosh"
#: en/ArchSpecificPPC.xml:49(para)
msgid "The bootloader should automatically boot the appropriate 32-bit or 64-bit installer."
msgstr "O carregador de boot deve fazer o boot automaticamente para o instalador apropriado (de 32-bits ou 64-bits)."
#: en/ArchSpecificPPC.xml:50(para)
msgid "The default gnome-power-manager package includes power management support, including sleep and backlight level management. Users with more complex requirements can use the apmud package in Fedora Extras. Following installation, you can install apmud with the following command:"
msgstr "O pacote padr??o gnome-power-manager inclui suporte ao gerenciamento de energia, incluindo gerenciamento de n??veis das fun????es sleep e backlight. Usu??rios com necessidades mais complexas podem usar o pacote apmud no Fedora Extras. Depois da instala????o, voc?? pode instalar o apmud com o seguinte comando:"
#: en/ArchSpecificPPC.xml:51(screen)
#, no-wrap
msgid "su -c 'yum install apmud' "
msgstr "su -c 'yum install apmud' "
#: en/ArchSpecificPPC.xml:54(para)
msgid "64-bit IBM eServer pSeries (POWER4/POWER5)"
msgstr "IBM eServer pSeries de 64-bits (POWER4/POWER5)"
#: en/ArchSpecificPPC.xml:55(para)
msgid "After using OpenFirmware to boot the CD, the bootloader (yaboot) should automatically boot the 64-bit installer."
msgstr "Depois de usar o OpenFirmware para dar boot pelo CD, o carregador de boot (yaboot) deve automaticamente iniciar o instalador de 64-bits."
#: en/ArchSpecificPPC.xml:58(para)
msgid "32-bit CHRP (IBM RS/6000 and others)"
msgstr "CHRP de 32-bits (IBM RS/6000 e outros)"
#: en/ArchSpecificPPC.xml:59(para)
msgid "After using OpenFirmware to boot the CD, select the linux32 boot image at the boot: prompt to start the 32-bit installer. Otherwise, the 64-bit installer starts, which does not work."
msgstr "Depois de usar o OpenFirmware para dar boot pelo CD, selecione a imagem de boot linux32 no prompt boot: para iniciar o instalador de 32-bits. Caso contr??rio, o instalador de 64-bits inicia, e n??o funciona."
#: en/ArchSpecificPPC.xml:62(para)
msgid "Genesi Pegasos II"
msgstr "Genesi Pegasos II"
#: en/ArchSpecificPPC.xml:63(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 OpenFirmware prompt, enter the command:"
msgstr "Nesta ??poca, firmware com suporte total para sistemas de arquivos ISO9660 ainda n??o foi lan??ado para o Pegasos. Entretanto, voc?? pode usar uma imagem de boot pela rede. No prompt do OpenFirmware, digite o comando:"
#: en/ArchSpecificPPC.xml:64(screen)
#, no-wrap
msgid "boot cd: /images/netboot/ppc32.img "
msgstr "boot cd: /images/netboot/ppc32.img "
#: en/ArchSpecificPPC.xml:65(para)
msgid "You must also configure OpenFirmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, set the boot-device and boot-file environment variables appropriately."
msgstr "Voc?? tamb??m pode configurar o OpenFirmware no Pegasos para tornar o sistema do Fedora Core boot??vel manualmente. Para fazer isto, use as vari??veis de ambiente boot-device e boot-file apropriadamente."
#: en/ArchSpecificPPC.xml:68(para)
msgid "Network booting"
msgstr "Boot pela Rede"
#: en/ArchSpecificPPC.xml:69(para)
msgid "You can find combined images containing the installer kernel and ramdisk in the images/netboot/ directory of the installation tree. These are intended for network booting with TFTP, but can be used in many ways."
msgstr "Voc?? pode encontrar imagens combinadas contendo o kernel do instalador e o ramdisk no diret??rio images/netboot/ da ??rvore de instala????o. Estes t??m como objetivo o boot pela rede via TFTP, mas podem ser usados de muitas maneiras."
#: en/ArchSpecificPPC.xml:70(para)
msgid "yaboot supports TFTP booting for IBM eServer pSeries and Apple Macintosh. The Fedora Project encourages the use of yaboot over the netboot images."
msgstr "O yaboot suporte boot via TFTP para IBM eServer pSeries e Apple Macintosh. O Projeto Fedora encoraja o uso do yaboot ao inv??s das imagens netboot."
#: en/ArchSpecific.xml:8(title)
msgid "Architecture Specific Notes"
msgstr "Notas Espec??ficas de Arquitetura"
#: en/ArchSpecific.xml:9(para)
msgid "This section provides notes that are specific to the supported hardware architectures of Fedora Core."
msgstr "Esta se????o fornece notas espec??ficas para as arquiteturas de hardware suportadas no Fedora Core."
#. Put one translator per line, in the form of NAME , YEAR1, YEAR2.
#: en/ArchSpecific.xml:0(None)
msgid "translator-credits"
msgstr "Hugo Cisneiros , 2006"
From fedora-docs-commits at redhat.com Sat Mar 4 06:31:42 2006
From: fedora-docs-commits at redhat.com (Hugo Cisneiros (eitch))
Date: Sat, 4 Mar 2006 01:31:42 -0500
Subject: release-notes/po pt_BR.po,1.1,1.2
Message-ID: <200603040631.k246VgXi016215@cvs-int.fedora.redhat.com>
Author: eitch
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16195
Modified Files:
pt_BR.po
Log Message:
updated the first xml defs line to include Virtualization
Index: pt_BR.po
===================================================================
RCS file: /cvs/docs/release-notes/po/pt_BR.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pt_BR.po 4 Mar 2006 06:24:09 -0000 1.1
+++ pt_BR.po 4 Mar 2006 06:31:35 -0000 1.2
@@ -12,7 +12,7 @@
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.1\n"
-#: en/Xorg.xml:5(title) en/Welcome.xml:5(title) en/WebServers.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/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(tit!
le)
msgid "Temp"
msgstr "Tempor??rio"
From fedora-docs-commits at redhat.com Sat Mar 4 08:02:42 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 4 Mar 2006 03:02:42 -0500
Subject: release-notes/po it.po,1.1,1.2
Message-ID: <200603040802.k2482hj8020205@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20176/release-notes/po
Modified Files:
it.po
Log Message:
translated it.po
based on the release-notes-FC-5-ISO-trans-freeze snapshot
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.1 -r 1.2 it.po
Index: it.po
===================================================================
RCS file: /cvs/docs/release-notes/po/it.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- it.po 26 Feb 2006 23:08:45 -0000 1.1
+++ it.po 4 Mar 2006 08:02:25 -0000 1.2
@@ -1,10 +1,11 @@
# translation of it.po to Italiano
# Francesco Tombolini , 2006.
+# translation of it.po to
msgid ""
msgstr ""
"Project-Id-Version: it\n"
-"POT-Creation-Date: 2006-02-26 22:43+0100\n"
-"PO-Revision-Date: 2006-02-27 00:05+0100\n"
+"POT-Creation-Date: 2006-03-01 18:52+0100\n"
+"PO-Revision-Date: 2006-03-04 08:00+0100\n"
"Last-Translator: Francesco Tombolini \n"
"Language-Team: Italiano \n"
"MIME-Version: 1.0\n"
@@ -13,7 +14,22 @@
"X-Generator: KBabel 1.11.1\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-#: en/Xorg.xml:5(title) en/Welcome.xml:5(title) en/WebServers.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/PackageNotesJava.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/ArchSpecificx86.xml:5(title) en/ArchSpecificx86_64.xml:5(title) en/ArchSpecificPPC.xml:5(title) en/ArchSpecific.xml:5(title)
+#: en/Xorg.xml:5(title) en/Welcome.xml:5(title) en/WebServers.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)
msgid "Temp"
msgstr "Temporaneo"
@@ -22,156 +38,309 @@
msgstr "X Window System (Grafica)"
#: en/Xorg.xml:9(para)
-msgid "This section contains information related to the X Window System implementation provided with Fedora."
-msgstr "Questa sezione contiene le informazioni relative all'implementazione del sistema X Window distribuito con Fedora."
+msgid ""
+"This section contains information related to the X Window System "
+"implementation provided with Fedora."
+msgstr ""
+"Questa sezione contiene le informazioni relative all'implementazione del "
+"sistema X Window distribuito con Fedora."
#: en/Xorg.xml:11(title)
msgid "xorg-x11"
msgstr "xorg-x11"
#: en/Xorg.xml:12(para)
-msgid "X.org X11 is an open source implementation of the X Window System. It provides the basic low level functionality which full fledged graphical user interfaces (GUIs) such as GNOME and KDE are designed upon."
-msgstr "X.org X11 ?? un implementazione open source del sistema X Window. Fornisce quelle elementari funzionalit?? di basso livello sulle quali sbandierate interfacce grafiche (GUIs) come GNOME e KDE sono disegnate."
+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 http://xorg.freedesktop.org/wiki/."
+msgstr ""
+"X.org X11 ?? un implementazione open source del sistema X Window. Fornisce "
+"quelle elementari funzionalit?? di basso livello sulle quali sbandierate "
+"interfacce grafiche (GUIs) come GNOME e KDE sono disegnate. Per maggiori "
+"informazioni su X.org, fa riferimento a http://xorg.freedesktop.org/wiki/."
#: en/Xorg.xml:13(para)
-msgid "For more information about Xorg refer to http://xorg.freedesktop.org/wiki/"
-msgstr "Per maggiori informazioni su Xorg fa riferimento a http://xorg.freedesktop.org/wiki/"
+msgid ""
+"You may use Applications > System Settings > Display or system-config-display to "
+"configure the settings. The configuration file for X.org is located in "
+"/etc/X11/xorg.conf."
+msgstr ""
+"Puoi usare Applicazioni => Impostazioni di sistema => "
+"Schermo o eseguire system-config-"
+"display per configurare le impostazioni. Il file di configurazione per Xorg "
+"?? collocato in /etc/X11/xorg.conf."
-#: en/Xorg.xml:15(para)
-msgid "You can use Applications => System Settings => Display or system-config-display to configure the settings. The configuration file for Xorg is located in /etc/X11/xorg.conf"
-msgstr "Puoi usare Applicazioni => Impostazioni di sistema => Schermo o eseguire system-config-display per configurare le impostazioni. Il file di configurazione per Xorg ?? collocato in /etc/X11/xorg.conf."
-
-#: en/Xorg.xml:16(para)
-msgid "Modular X.Org X11R7 RC2 was released into Fedora development (rawhide) on November 16, 2005. This is the first modular release of Xorg which among several other benefits, enable users to receive updates in a faster pace and helps developers to develop and release specific components in a rapid fashion."
-msgstr "Il modulare X.Org X11R7 RC2 ?? stato distribuito con Fedora development (rawhide) il 16 Novembre, 2005. Questa ?? la prima release modulare di Xorg che fra gli altri benefici, da la possibilit?? agli utenti di ricevere gli aggiornamenti con un passo pi?? veloce, mentre aiuta gli sviluppatori a programmare e rilasciare componenti specifiche in modo pi?? rapido."
-
-#: en/Xorg.xml:17(para)
-msgid "More information on the current status of the Xorg modularization effort in Fedora is available from http://fedoraproject.org/wiki/Xorg/Modularization"
-msgstr "Maggiori informazioni sullo status attuale dello sforzo di modularizzazione di Xorg in Fedora ?? disponibile su http://fedoraproject.org/wiki/Xorg/Modularization"
-
-#: en/Xorg.xml:21(title)
-msgid "Xorg X11R7.0 Developer Notes"
-msgstr "Note per lo sviluppatore di Xorg X11R7.0"
-
-#: en/Xorg.xml:22(para)
-msgid "X11R7.0 is included in this release and there are a number of things that software developers, and packagers in Fedora repositories need to be aware of in order to ensure that their software or software packages properly compile and work with X11R7. Some are simple changes, while others may be more involved. Here is a summary of issues that may arise and where possible, suggestions on how to fix them."
-msgstr "X11R7.0 ?? incluso in questa release e ci sono un certo numero di cose di cui gli sviluppatori ed i creatori dei pacchetti nei repositori Fedora, devono essere informati, per potersi assicurare che i loro software o pacchetti software si compilino in modo appropriato e funzionino con X11R7. Alcuni sono cambiamenti superficiali, mentre altri possono essere pi?? coinvolgenti. Qui c'?? un sommario delle cose che possono insorgere e quando possibile, suggerimenti su come risolverle."
+#: 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 http://"
+"fedoraproject.org/wiki/Xorg/Modularization."
+msgstr ""
+"X.org X11R7 ?? la prima versione modulare di X.org, che, oltre a diversi altri benefici , consente aggiornamenti pi?? veloci ed aiuta i programmatori a sviluppare e rilasciare componenti specifici rapidamente. Maggiori informazioni sullo status attuale dello sforzo di modularizzazione "
+"di Xorg in Fedora ?? disponibile su http://"
+"fedoraproject.org/wiki/Xorg/Modularization."
+
+#: en/Xorg.xml:17(title)
+msgid "X.org X11R7 End-User Notes"
+msgstr "Note su Xorg X11R7 per l'utente finale"
+
+#: en/Xorg.xml:19(title)
+msgid "Installing Third Party Drivers"
+msgstr "Installare drivers di terze parti"
-#: en/Xorg.xml:24(title)
-msgid "The /usr/X11R6 Directory Hierarchy"
-msgstr "La gerarchia della directory /usr/X11R6"
+#: en/Xorg.xml:20(para)
+msgid ""
+"Before you install any third party drivers from any vendor, including ATI or "
+"nVidia, please read http://fedoraproject.org/wiki/"
+"Xorg/3rdPartyVideoDrivers."
+msgstr ""
+"Prima di installare qualsiasi drivers di terze parti da qualunque venditore, incluso ATI o "
+"nVidia, sei pregato di leggere http://fedoraproject.org/wiki/"
+"Xorg/3rdPartyVideoDrivers."
#: en/Xorg.xml:25(para)
-msgid "X11R7 install into /usr directly now, and no longer uses the /usr/X11R6 hierarchy. Applications which rely on files being present at fixed paths under /usr/X11R6 at compile time or at run time, must be updated to use the system PATH, or some other mechanism to dynamically determine where the files reside, or alternatively to hard code the new locations, possibly with fallbacks."
-msgstr "X11R7 si installa direttamente in /usr ora, e non usa pi?? la gerarchia /usr/X11R6. Le applicazioni che contano che i files siano presenti nel percorso fisso sotto /usr/X11R6 durante la compilazione o l'esecuzione, devono essere aggiornati o usare il system PATH, o alcuni altri meccanismi, per determinare dinamicamente dove risiedono i files, o alternativamente inglobare nel codice i nuovi percorsi, possibilmente con fallback."
+msgid ""
+"The xorg-x11-server-Xorg package install scripts automatically "
+"remove the RgbPath line from the xorg.conf 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 xorg at freedesktop.org mailing "
+"list if you do need assistance reconfiguring your keyboard."
+msgstr ""
+"Gli scripts d'installazione del pacchetto xorg-x11-server-Xorg rimuovono automaticamente la linea RgbPath dal file xorg.conf se presente. Potresti avere la necessit?? di riconfigurare la tua tastiera differentemente da quella che usi. Sei incoraggiato a sottoscriverti alla mailing list xorg at freedesktop.org se hai bisogno di assistenza nel riconfigurare la tua tastiera."
#: en/Xorg.xml:28(title)
-msgid "Imake"
-msgstr "Imake"
+msgid "X.org X11R7 Developer Overview"
+msgstr "Xorg X11R7 anteprima per lo sviluppatore"
#: en/Xorg.xml:29(para)
-msgid "Imake is no longer used to build the X Window System, and as such is now officially deprecated. Imake, xmkmf and other utilities previously supplied by the X Window System, are still supplied in X11R7, however X.Org highly recommends that people migrate from Imake to using GNU autotools and pkg-config. imake support may vanish in a future X Window System release, so developers are strongly encouraged to transition away from it, and not use it for any new software projects."
-msgstr "Imake non ?? pi?? utilizzato per compilare il sistema X Window, e cos?? ?? ora ufficialmente deprecato. Imake, xmkmf ed altre utilities distribuite in precedenza con il sistema X Window, sono ancora fornite con X11R7, comunque X.Org raccomanda caldamente a tutti di migrare da Imake per utilizzare GNU autotools e pkg-config. Il supporto per imake potrebbe scomparire in una futura versione del sistema X Window, cos?? gli sviluppatori sono fortemente incoraggiati a starne alla larga, e non usarlo per nessun nuovo progetto software."
+msgid ""
+"The following list includes some of the more visible changes for developers "
+"in X11R7:"
+msgstr "L'elenco seguente include alcuni fra i pi?? evidenti cambiamenti per gli sviluppatori in X11R7:"
-#: en/Xorg.xml:32(title)
-msgid "The Systemwide app-defaults Directory"
-msgstr "La directory app-defaults di sistema"
-
-#: en/Xorg.xml:33(para)
-msgid "The system app-defaults directory for X resources, is now \"%{_datadir}/X11/app-defaults\", which expands to /usr/share/X11/app-defaults on Fedora Core 5 and for future Red Hat Enterprise Linux systems."
-msgstr "La directory di sistema app-defaults per le risorse X, ?? ora \"%{_datadir}/X11/app-defaults\", che espande la /usr/share/X11/app-defaults su Fedora Core 5 e per i futuri sistemi Red Hat Enterprise Linux."
-
-#: en/Xorg.xml:36(title)
-msgid "xft-config Can't Be Found"
-msgstr "xft-config non pu?? essere trovato"
-
-#: en/Xorg.xml:37(para)
-msgid "Modular X now uses GNU autotools, and pkg-config for its buildsystem configuration, etc. xft-config has been deprecated for 2-3 years now, and pkgconfig *.pc files have been provided for most of this time. Applications which previously used xft-config to obtain the Cflags or libs options for building with, must now be updated to use pkg-config."
-msgstr "X modulare usa ora GNU autotools, e pkg-config per il suo sistema di compilazione configurazione, etc. xft-config ?? stato deprecato per 2-3 anni, ed i files pkgconfig *.pc sono stati distribuiti per la maggior parte di questo tempo. Le applicazioni che precedentemente usavano xft-config per ottenere le opzioni Cflags or libs per essere compilate, devono ora essere aggiornate per l'uso di pkg-config."
+#: en/Xorg.xml:32(para)
+msgid ""
+"The entire buildsystem has changed from imake to the GNU "
+"autotools collection."
+msgstr ""
+"L'intero sistema di compilazione ?? cambiato da imake alla collezione GNU "
+"autotools."
[...7218 lines suppressed...]
+"Fedora/base/stage2.img (on Installtion Disc 1) plus the size of the "
+"files in /var/lib/rpm on the installed system."
+msgstr ""
+"I requisiti di spazio su disco sottoelencati rappresentano lo spazio occupato da Fedora Core 5 dopo aver completato l'installazione. Comunque, altro spazio su disco ?? necessario durante l'installazione per il supporto dell'ambiente d'installazione. Questo spazio aggiuntivo corrisponde alla grandezza di /Fedora/base/stage2.img (sul Disco d'installazione 1) pi?? la "
+"grandezza dei files in /var/lib/rpm sul sistema installato."
+
+#: en/ArchSpecificPPC.xml:40(title)
+msgid "The Apple keyboard"
+msgstr "La tastiera Apple"
-#: en/ArchSpecificPPC.xml:27(para)
-msgid "Recommended for graphical: 400 MHz G3 or better, 128MiB RAM."
+#: en/ArchSpecificPPC.xml:41(para)
+msgid ""
+"The Option key on Apple systems is equivalent to the Alt key on the PC. Where documentation and the installer refer to the "
+"Alt key, use the Option key. For some key "
+"combinations you may need to use the Option key in conjunction "
+"with the Fn key, such as Option-Fn-"
+"F3 to switch to virtual terminal tty3."
msgstr ""
+"Il tasto Option sui sistemi Apple ?? equivalente al tasto Alt sul PC. Dove la documentazione o il software d'installazione si riferiscono al tasto Alt, usa il tasto Option. Per alcune combinazioni di tasti potresti aver bisogno d'usare il tasto Option insieme al tasto Fn, tipo Option-Fn-"
+"F3 per cambiare al terminale virtuale tty3."
-#: en/ArchSpecificPPC.xml:39(title)
+#: en/ArchSpecificPPC.xml:44(title)
msgid "PPC Installation Notes"
-msgstr ""
+msgstr "Note di installazione PPC"
-#: en/ArchSpecificPPC.xml:48(phrase)
-msgid "/!\\"
-msgstr ""
+#: en/ArchSpecificPPC.xml:45(para)
+msgid ""
+"Fedora Core Installation Disc 1 is bootable on supported hardware. In "
+"addition, a bootable CD image appears in the images/ directory "
+"of this disc. These images will behave differently according to your system "
+"hardware:"
+msgstr "Il disco 1 d'installazione di Fedora Core ?? avviabile sull'hardware supportato. In pi??, un immagine di CD bootabile si pu?? trovare nella directory images/ di questo disco. Queste immagini si comporteranno differentemente a seconda dell'hardware:"
-#: en/ArchSpecificPPC.xml:42(para)
-msgid " Currently FC5 Test Release CD 1 and Rescue ISOs do not boot on Mac hardware. See below on booting using boot.iso."
-msgstr ""
+#: en/ArchSpecificPPC.xml:48(para)
+msgid "Apple Macintosh"
+msgstr "Apple Macintosh"
-#: en/ArchSpecificPPC.xml:55(para)
-msgid "The DVD or first CD of the installation set of Fedora Core is set to be bootable on supported hardware. In addition, a bootable CD images can be found in the images/ directory of the DVD or first CD. These will behave differently according to the hardware:"
-msgstr ""
+#: en/ArchSpecificPPC.xml:49(para)
+msgid ""
+"The bootloader should automatically boot the appropriate 32-bit or 64-bit "
+"installer."
+msgstr "Il bootloader avvier?? automaticamente l'appropriato installer a 32-bit o 64-bit."
-#: en/ArchSpecificPPC.xml:58(para)
-msgid "Apple Macintosh"
-msgstr ""
+#: en/ArchSpecificPPC.xml:50(para)
+msgid ""
+"The default gnome-power-manager package includes power "
+"management support, including sleep and backlight level management. Users "
+"with more complex requirements can use the apmud package in "
+"Fedora Extras. Following installation, you can install apmud "
+"with the following command:"
+msgstr "Il pacchetto predefinito gnome-power-manager include il supporto al power management, incluso lo sleep e la gestione del livello di retroilluminazione. Gli utenti con requisiti pi?? complessi possono usare il pacchetto apmud in Fedora Extras. Seguendo l'installazione, puoi installare apmud con il seguente comando:"
-#: en/ArchSpecificPPC.xml:61(para)
-msgid "The bootloader should automatically boot the appropriate 32-bit or 64-bit installer. Power management support, including sleep and backlight level management, is present in the apmud package, which is in Fedora Extras. Fedora Extras for Fedora Core is configured by default for yum. Following installation, apmud can be installed by running yum install apmud."
-msgstr ""
+#: en/ArchSpecificPPC.xml:51(screen)
+#, no-wrap
+msgid "su -c 'yum install apmud' "
+msgstr "su -c 'yum install apmud' "
-#: en/ArchSpecificPPC.xml:66(para)
+#: en/ArchSpecificPPC.xml:54(para)
msgid "64-bit IBM eServer pSeries (POWER4/POWER5)"
-msgstr ""
+msgstr "64-bit IBM eServer pSeries (POWER4/POWER5)"
-#: en/ArchSpecificPPC.xml:69(para)
-msgid "After using OpenFirmware to boot the CD, the bootloader (yaboot) should automatically boot the 64-bit installer."
+#: en/ArchSpecificPPC.xml:55(para)
+msgid ""
+"After using OpenFirmware to boot the CD, the "
+"bootloader (yaboot) should automatically boot the 64-bit installer."
msgstr ""
+"Dopo aver usato OpenFirmware per avviare il CD, "
+"il bootloader (yaboot) avvier?? automaticamente l'installer a 64-bit."
-#: en/ArchSpecificPPC.xml:74(para)
+#: en/ArchSpecificPPC.xml:58(para)
msgid "32-bit CHRP (IBM RS/6000 and others)"
-msgstr ""
+msgstr "32-bit CHRP (IBM RS/6000 ed altri)"
-#: en/ArchSpecificPPC.xml:77(para)
-msgid "After using OpenFirmware to boot the CD, select the 'linux32' boot image at the 'boot:' prompt to start the 32-bit installer. Otherwise, the 64-bit installer is started, which does not work."
+#: en/ArchSpecificPPC.xml:59(para)
+msgid ""
+"After using OpenFirmware to boot the CD, select "
+"the linux32 boot image at the boot: prompt to "
+"start the 32-bit installer. Otherwise, the 64-bit installer starts, which "
+"does not work."
msgstr ""
+"Dopo aver usato OpenFirmware per avviare il CD, seleziona l'immagine boot linux32 al boot: prompt per avviare l'installer "
+"a 32-bit. Altrimenti, verr?? avviato l'installer a 64-bit, che non funzioner??."
-#: en/ArchSpecificPPC.xml:82(para)
+#: en/ArchSpecificPPC.xml:62(para)
msgid "Genesi Pegasos II"
-msgstr ""
+msgstr "Genesi Pegasos II"
-#: en/ArchSpecificPPC.xml:85(para)
-msgid "At the time of writing, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, the network boot image can be used. At the OpenFirmware prompt, enter the command:"
-msgstr ""
+#: en/ArchSpecificPPC.xml:63(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 OpenFirmware prompt, enter the "
+"command:"
+msgstr ""
+"Quando questo documento ?? stato scritto, firmware con pieno supporto per i "
+"file systems ISO9660 per Pegasos non sono ancora stati rilasciati. Comunque, "
+"potr?? essere usata l'immagine di avvio network boot. All'OpenFirmware prompt, inserisci il comando:"
-#: en/ArchSpecificPPC.xml:88(screen)
+#: en/ArchSpecificPPC.xml:64(screen)
#, no-wrap
-msgid "boot cd: /images/netboot/ppc32.img "
-msgstr ""
+msgid "boot cd: /images/netboot/ppc32.img "
+msgstr "boot cd: /images/netboot/ppc32.img "
-#: en/ArchSpecificPPC.xml:91(para)
-msgid "You also need to configure OpenFirmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, you need to set the boot-device and boot-file environment variables appropriately."
+#: en/ArchSpecificPPC.xml:65(para)
+msgid ""
+"You must also configure OpenFirmware on the "
+"Pegasos manually to make the installed Fedora Core system bootable. To do "
+"this, set the boot-device and boot-file "
+"environment variables appropriately."
msgstr ""
+"Avrai anche bisogno di configurare manualmente OpenFirmware sul Pegasos per rendere il sistema Fedora Core installato "
+"avviabile. Per farlo, dovrai impostare le variabili ambiente boot-device e boot-file appropriatamente."
-#: en/ArchSpecificPPC.xml:96(para)
+#: en/ArchSpecificPPC.xml:68(para)
msgid "Network booting"
-msgstr ""
+msgstr "Avvio dalla rete"
-#: en/ArchSpecificPPC.xml:99(para)
-msgid "There are combined images containing the installer kernel and ramdisk in the images/netboot/ directory of the install tree. These are intended for network booting with TFTP, but can be used in many ways."
-msgstr ""
+#: en/ArchSpecificPPC.xml:69(para)
+msgid ""
+"You can find combined images containing the installer kernel and ramdisk in "
+"the images/netboot/ directory of the installation tree. These "
+"are intended for network booting with TFTP, but can be used in many ways."
+msgstr "Ci sono immagini combinate contenenti il kernel d'installazione ed il ramdisk nella directory images/netboot/ del albero d'installazione. Queste sono intese per l'avvio via network con TFTP, ma possono essere usate in molti modi."
-#: en/ArchSpecificPPC.xml:100(para)
-msgid "yaboot supports tftp booting for IBM eServer pSeries and Apple Macintosh, the use of yaboot is encouraged over the netboot images."
+#: en/ArchSpecificPPC.xml:70(para)
+msgid ""
+"yaboot supports TFTP booting for IBM eServer pSeries and Apple "
+"Macintosh. The Fedora Project encourages the use of yaboot over "
+"the netboot images."
msgstr ""
+"yaboot supporta il TFTP booting per gli IBM eServer pSeries e Apple "
+"Macintosh. Il progetto Fedora Incoraggia l'uso di yaboot rispetto alle immagini netboot."
#: en/ArchSpecific.xml:8(title)
-msgid "Archictecture Specific"
-msgstr ""
+msgid "Architecture Specific Notes"
+msgstr "Note specifiche sull'architettura"
#: en/ArchSpecific.xml:9(para)
-msgid "This section provides notes that are specific to the supported hardware architectures of Fedora Core."
+msgid ""
+"This section provides notes that are specific to the supported hardware "
+"architectures of Fedora Core."
msgstr ""
+"Questa sezione fornisce note che sono specifiche all'architettura hardware "
+"supportata da Fedora Core."
#. Put one translator per line, in the form of NAME , YEAR1, YEAR2.
#: en/ArchSpecific.xml:0(None)
msgid "translator-credits"
-msgstr ""
+msgstr "riconoscimenti ai traduttori"
From fedora-docs-commits at redhat.com Sat Mar 4 10:30:13 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 4 Mar 2006 05:30:13 -0500
Subject: docs-common/common legalnotice-content-p1-it.xml, NONE,
1.1 legalnotice-content-p2-it.xml, NONE,
1.1 legalnotice-content-p3-it.xml, NONE,
1.1 legalnotice-content-p4-it.xml, NONE,
1.1 legalnotice-content-p5-it.xml, NONE,
1.1 legalnotice-content-p6-it.xml, NONE, 1.1
Message-ID: <200603041030.k24AUDU8025156@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25134
Added Files:
legalnotice-content-p1-it.xml legalnotice-content-p2-it.xml
legalnotice-content-p3-it.xml legalnotice-content-p4-it.xml
legalnotice-content-p5-it.xml legalnotice-content-p6-it.xml
Log Message:
it translation (no licence content was translated)
--- NEW FILE legalnotice-content-p1-it.xml ---
%FEDORA-ENTITIES-IT;
]>
Copyright (c) 2006 da Fedora Foundation ed altri. Questo materiale pu?? essere
distribuito solo soggetto ai termini e condizioni fissati nella Open
Publication License, v1.0, disponibile su .
--- NEW FILE legalnotice-content-p2-it.xml ---
%FEDORA-ENTITIES-IT;
]>
Garrett LeSage ha creato le grafiche di ammonizione (note, tip, important, caution,
and warning). Tommy Reynolds Tommy.Reynolds at MegaCoder.com
ha creato la grafica di callout. Queste possono essere liberamente redistribuite con
la documentazione prodotta per il Fedora Project.
--- NEW FILE legalnotice-content-p3-it.xml ---
%FEDORA-ENTITIES-IT;
]>
FEDORA, FEDORA PROJECT, ed il Fedora Logo sono marchi di Red Hat, Inc.,
sono registrati od in attesa di registrazione negli U.S. ed in altri paesi, e
sono usati qui sotto licenza alla Fedora Foundation.
--- NEW FILE legalnotice-content-p4-it.xml ---
%FEDORA-ENTITIES-IT;
]>
&RH; ed il logo &RH; "Shadow Man" sono marchi registrati di &FORMAL-RHI;
negli Stati Uniti ed in altri paesi.
--- NEW FILE legalnotice-content-p5-it.xml ---
%FEDORA-ENTITIES-IT;
]>
Tutti gli altri marchi e copyrights a cui si fa riferimento sono propriet??
dei rispettivi proprietari.
--- NEW FILE legalnotice-content-p6-it.xml ---
%FEDORA-ENTITIES-IT;
]>
La documentazione,come il software in se, pu?? essere soggetto a controllo sull'esportazione.
Leggi sul controllo sull'esportazione per il Fedora Project su http://fedoraproject.org/wiki/Legal/Export.
From fedora-docs-commits at redhat.com Sat Mar 4 10:31:19 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sat, 4 Mar 2006 05:31:19 -0500
Subject: docs-common/common legalnotice-it.xml, 1.1,
1.2 legalnotice-opl-it.xml, 1.1,
1.2 legalnotice-section-it.xml, 1.2, 1.3
Message-ID: <200603041031.k24AVJie025193@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25172
Modified Files:
legalnotice-it.xml legalnotice-opl-it.xml
legalnotice-section-it.xml
Log Message:
updated content
Index: legalnotice-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-it.xml 19 Nov 2005 20:24:22 -0000 1.1
+++ legalnotice-it.xml 4 Mar 2006 10:31:11 -0000 1.2
@@ -1,12 +1,22 @@
+
-
+
-&LEGALNOTICE-CONTENT;
-
+
+
+
+
+
+
\ No newline at end of file
Index: legalnotice-opl-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-opl-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-opl-it.xml 2 Feb 2006 15:15:09 -0000 1.1
+++ legalnotice-opl-it.xml 4 Mar 2006 10:31:11 -0000 1.2
@@ -1,12 +1,240 @@
+
-
+
+
-&LEGALNOTICE-OPL-CONTENT;
+
+ Permission is granted to copy, distribute, and/or modify this
+ document under the terms of the Open Publication Licence, Version
+ 1.0, or any later version. The terms of the OPL are set out below.
+
+
+
+ REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED
+ VERSIONS
+
+ 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.
+
+
+
+ Proper form for an incorporation by reference is as follows:
+
+
+
+ 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 ).
+
+
+
+ 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.
+
+
+
+ COPYRIGHT
+
+ The copyright to each Open Publication is owned by its author(s)
+ or designee.
+
+
+
+ SCOPE OF LICENSE
+
+
+ The following license terms apply to all Open Publication works,
+ unless otherwise explicitly stated in the document.
+
+
+
+ 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.
+
+
+
+ SEVERABILITY. If any part of this license is found to be
+ unenforceable in any jurisdiction, the remaining portions of the
+ license remain in force.
+
+
+
+ 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.
+
+
+
+ REQUIREMENTS ON MODIFIED WORKS
+
+
+ All modified versions of documents covered by this license,
+ including translations, anthologies, compilations and partial
+ documents, must meet the following requirements:
+
+
+
+
+
+ The modified version must be labeled as such.
+
+
+
+
+ The person making the modifications must be identified and
+ the modifications dated.
+
+
+
+
+ Acknowledgement of the original author and publisher if
+ applicable must be retained according to normal academic
+ citation practices.
+
+
+
+
+ The location of the original unmodified document must be
+ identified.
+
+
+
+
+ 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.
+
+
+
+
+
+ GOOD-PRACTICE RECOMMENDATIONS
+
+
+ In addition to the requirements of this license, it is requested
+ from and strongly recommended of redistributors that:
+
+
+
+
+
+ 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.
+
+
+
+
+ All substantive modifications (including deletions) be
+ either clearly marked up in the document or else described
+ in an attachment to the document.
+
+
+
+
+ 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).
+
+
+
+
+
+
+ LICENSE OPTIONS
+
+
+ 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.
+
+
+
+ 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.
+
+
+
+ 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.
+
+
+
+ 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.
+
+
+
+ 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.
+
+
+
+
+
Index: legalnotice-section-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-section-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- legalnotice-section-it.xml 1 Mar 2006 13:47:35 -0000 1.2
+++ legalnotice-section-it.xml 4 Mar 2006 10:31:11 -0000 1.3
@@ -4,8 +4,8 @@
"http://www.docbook.org/xml/4.4/docbookx.dtd" [
-
- %FEDORA-ENTITIES-EN;
+
+ %FEDORA-ENTITIES-IT;
]>
" >
- " >
+ " >
" >
- " >
+ " >
@@ -41,9 +41,9 @@
-
+
-
+
@@ -68,7 +68,7 @@
-
+
Index: entities-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-it.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- entities-it.xml 1 Mar 2006 19:51:00 -0000 1.9
+++ entities-it.xml 4 Mar 2006 10:33:59 -0000 1.10
@@ -48,7 +48,7 @@
- URL del progetto Fedora
+ Fedora Project URL
@@ -60,7 +60,7 @@
Bugzilla
- URL di Bugzilla
+ URL di bugzilla
@@ -113,7 +113,7 @@
- legalnotice-en.xml
+ legalnotice-it.xml
@@ -121,7 +121,7 @@
- legalnotice-opl-en.xml
+ legalnotice-opl-it.xml
@@ -171,7 +171,7 @@
- draftnotice-it.xml
+ draftnotice-it.xm
Index: it.po
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/it.po,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- it.po 2 Mar 2006 22:52:15 -0000 1.11
+++ it.po 4 Mar 2006 10:33:59 -0000 1.12
@@ -3,8 +3,8 @@
msgid ""
msgstr ""
"Project-Id-Version: it\n"
-"POT-Creation-Date: 2006-03-02 16:46-0600\n"
-"PO-Revision-Date: 2006-03-01 17:26+0100\n"
+"POT-Creation-Date: 2006-02-27 22:09-0600\n"
+"PO-Revision-Date: 2006-03-04 11:08+0100\n"
"Last-Translator: Francesco Tombolini \n"
"Language-Team: Italiano \n"
"MIME-Version: 1.0\n"
@@ -13,230 +13,220 @@
"X-Generator: KBabel 1.11.1\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-#: entities-en_US.xml:4(title)
-msgid ""
-"These common entities are useful shorthand terms and names, which may be "
-"subject to change at anytime. This is an important value the the entity "
-"provides: a single location to update terms and common names."
-msgstr ""
-"Queste entit?? comuni sono utili abbreviazioni di termini e nomi, che "
-"potrebbero essere soggette a cambiamento in qualsiasi momento. Questo ?? il "
-"valore importante che le entit?? forniscono: Una singola locazione per "
-"aggiornare termini e nomi comuni."
+#: entities-en.xml:6(title)
+msgid "These common entities are useful shorthand terms and names, which may be subject to change at anytime. This is an important value the the entity provides: a single location to update terms and common names."
+msgstr "Queste entit?? comuni sono utili abbreviazioni di termini e nomi, che potrebbero essere soggette a cambiamento in qualsiasi momento. Questo ?? il valore importante che le entit?? forniscono: Una singola locazione per aggiornare termini e nomi comuni."
-#: entities-en_US.xml:7(comment) entities-en_US.xml:11(comment)
+#: entities-en.xml:14(comment) entities-en.xml:18(comment)
msgid "Generic root term"
msgstr "Termine generico principale"
-#: entities-en_US.xml:8(text)
+#: entities-en.xml:15(text)
msgid "Fedora"
msgstr "Fedora"
-#: entities-en_US.xml:12(text)
+#: entities-en.xml:19(text)
msgid "Core"
msgstr "Core"
-#: entities-en_US.xml:15(comment)
+#: entities-en.xml:22(comment)
msgid "Generic main project name"
msgstr "Nome generico del progetto principale"
-#: entities-en_US.xml:19(comment)
+#: entities-en.xml:26(comment)
msgid "Legacy Entity"
msgstr "Entit?? obsolete"
-#: entities-en_US.xml:23(comment)
+#: entities-en.xml:30(comment)
msgid "Short project name"
msgstr "Nome breve del progetto"
-#: entities-en_US.xml:24(text)
+#: entities-en.xml:31(text)
msgid "FC"
msgstr "FC"
-#: entities-en_US.xml:27(comment)
+#: entities-en.xml:34(comment)
msgid "Generic overall project name"
msgstr "Nome generico del progetto complessivo"
-#: entities-en_US.xml:28(text)
+#: entities-en.xml:35(text)
msgid ", puoi ora specificare gruppi di porte. Per esempio, specificando 6881-6999:tcp si otterr?? l'aggiunta della seguente linea in /etc/sysconfig/iptables:"
#: en/ServerTools.xml:32(screen)
#, no-wrap
@@ -815,7 +815,7 @@
".rpmnew files. Such service configurations must be fixed so the "
"pam_stack module is not used. Refer to the .rpmnew "
"files for the actual changes needed."
-msgstr "Quando un sistema viene aggiornato da una precedente release di Fedora Core e l'amministratore del sistema ha precedentemente modificato alcune configurazioni dei servizi, questi files di configurazione modificati not sono sostituiti quando un nuovo pacchetto viene installato. Invece, i nuovi files di configurazione vengono creati come .rpmnew. Le configurazioni di questi servizi debbono essere fissate affinch?? il modulo pam_stack non venga utilizzato. Fa riferimento ai files .rpmnew per le modifiche necessarie."
+msgstr "Quando un sistema viene aggiornato da una precedente release di Fedora Core e l'amministratore del sistema ha precedentemente modificato alcune configurazioni dei servizi, questi files di configurazione modificati non sono sostituiti quando un nuovo pacchetto viene installato. Invece, i nuovi files di configurazione vengono creati come .rpmnew. Le configurazioni di questi servizi debbono essere fissate affinch?? il modulo pam_stack non venga utilizzato. Fa riferimento ai files .rpmnew per le modifiche necessarie."
#: en/Security.xml:28(screen)
#, no-wrap
@@ -926,7 +926,7 @@
"program. The canary value is random each time the application is started, "
"making remote exploitation very difficult. The fstack-protector "
"feature does not protect against heap-based buffer overflows."
-msgstr "Tutto il software nei repositori Fedora Core e Fedora Extras per questa versione sono compilati usando una caratteristica di sicurezza chiamata fstack-protector. L'fstack-protector pone un canary value sullo stack di funzioni contenenti un array di caratteri locale. Prima di ritornare da una funzione protetta, il canary value ?? verificato. Se c'?? stato un buffer overflow, il canary non coincider?? pi?? con il valore aspettato, abortendo il programma. Il canary value ?? randomico per ogni volta che l'applicazione ?? avviata, rendendo l'exploit remoto molto difficile. La caratteristica fstack-protector non protegge contro i buffer overflows heap based."
+msgstr "Tutto il software nei repositori Fedora Core e Fedora Extras per questa versione sono compilati usando una caratteristica di sicurezza chiamata fstack-protector. L'fstack-protector pone un canary value sullo stack di funzioni contenenti un array di caratteri locale. Prima di ritornare da una funzione protetta, il canary value viene verificato. Se c'?? stato un buffer overflow, il canary non coincider?? pi?? con il valore aspettato, abortendo il programma. Il canary value ?? randomico per ogni volta che l'applicazione ?? avviata, rendendo l'exploit remoto molto difficile. La caratteristica fstack-protector non protegge contro i buffer overflows heap based."
#: en/Security.xml:70(para)
msgid ""
@@ -964,7 +964,7 @@
"code> kernel module to the 2.6.14 kernel, and corresponding enhancements to "
"system-config-securitylevel, the "
"firewall now properly handles SMB broadcasts and permits network browsing."
-msgstr "Fedora pu?? ora esplorare le condivisioni Windows, una caratteristica conosciuta come esplorazione SMB. Nelle releases precedenti a Fedora Core 5, il firewall preveniva l'appropriata funzionalit?? dell'esplorazione SMB. Con l'aggiunta del modulo kernel ip_conntrack_netbios_ns al kernel 2.6.14 kernel, ed i corrispondenti sviluppi di system-config-securitylevel, il firewall ora amministra propriamente gli SMB broadcasts e permette l'esplorazione della rete."
+msgstr "Fedora pu?? ora esplorare le condivisioni Windows, una caratteristica conosciuta come esplorazione SMB. Nelle releases precedenti a Fedora Core 5, il firewall preveniva l'appropriata funzionalit?? dell'esplorazione SMB. Con l'aggiunta del modulo kernel ip_conntrack_netbios_ns al kernel 2.6.14, ed i corrispondenti sviluppi di system-config-securitylevel, il firewall ora gestisce propriamente gli SMB broadcasts e permette l'esplorazione della rete."
#: en/ProjectOverview.xml:8(title)
msgid "Fedora Project - Freedom to the Core"
@@ -1016,8 +1016,8 @@
"http://"
"fedoraproject.org/wiki/Communicate."
msgstr ""
-"http://"
-"fedoraproject.org/wiki/Communicate."
+"http://"
+"fedoraproject.org/wiki/it_IT/Communicate."
#: en/ProjectOverview.xml:18(para)
msgid "In addition to the website, the following mailing lists are available:"
@@ -1134,7 +1134,7 @@
"have undergone significant changes for Fedora Core 5. For easier access, "
"they are generally organized using the same groups that are shown in the "
"installation system."
-msgstr "Le seguenti sezioni contengono informazioni riguardanti i pacchetti che hanno avuto significativi cambiamenti per Fedora Core 5. Per un accesso facilitato, sono in linea generale organizzati usando gli stessi gruppi mostrati nel sistema d'installazione."
+msgstr "Le seguenti sezioni contengono informazioni riguardanti i pacchetti che hanno avuto significativi cambiamenti per Fedora Core 5. Per un accesso facilitato, sono organizzati in linea generale usando gli stessi gruppi mostrati nel sistema d'installazione."
#: en/PackageNotes.xml:11(title)
msgid "Kernel device, module loading, and hotplug changes"
@@ -1164,18 +1164,18 @@
#: en/PackageNotes.xml:18(title)
msgid "mlocate Has Replaced slocate"
-msgstr "mlocate Ha sostituito slocate"
+msgstr "mlocate ha sostituito slocate"
#: en/PackageNotes.xml:19(para)
msgid ""
"The new mlocate package provides the implementations of /"
"usr/bin/locate and /usr/bin/updatedb. Previous Fedora "
"releases included the slocate versions of these programs."
-msgstr "Il nuovo pacchetto mlocate fornisce l'implementazione di /usr/bin/locate e /usr/bin/updatedb. Le precedenti versioni di Fedora includevano le versioni slocate di questi programmi."
+msgstr "Il nuovo pacchetto mlocate fornisce le implementazioni di /usr/bin/locate e /usr/bin/updatedb. Le precedenti versioni di Fedora includevano le versioni slocate di questi programmi."
#: en/PackageNotes.xml:23(para)
msgid "The locate command should be completely compatible."
-msgstr "Il comando locate sar?? completamente compatibile."
+msgstr "Il comando locate ?? completamente compatibile."
#: en/PackageNotes.xml:26(para)
msgid "The configuration file /etc/updatedb.conf is compatible."
@@ -1183,7 +1183,7 @@
#: en/PackageNotes.xml:29(para)
msgid "Syntax errors that slocate would not detect are now reported."
-msgstr "Gli errori di sisntassi che slocate non rilever?? saranno ora riportati."
+msgstr "Gli errori di sisntassi che slocate non rilevava saranno ora segnalati."
#: en/PackageNotes.xml:32(para)
msgid "The DAILY_UPDATE variable is not supported."
@@ -1240,7 +1240,7 @@
"release. Refer to http://wiki.dovecot.org/UpgradingDovecot for more information on "
"the changes."
-msgstr "Fedora Core 5 include una nuova versione del software server IMAP dovecot, che ha molti cambiamenti nel suo file di configurazione. Questi cambiamenti sono di particolare importanza per gli utenti che eseguono l'aggiornamento da una versione precedente. Fa riferimento a http://wiki.dovecot.org/UpgradingDovecot per maggiori informazioni sui cambiamenti."
+msgstr "Fedora Core 5 include una nuova versione del software server IMAP dovecot, che presenta molti cambiamenti nel suo file di configurazione. Questi cambiamenti sono di particolare importanza per gli utenti che eseguono l'aggiornamento da una versione precedente. Fa riferimento a http://wiki.dovecot.org/UpgradingDovecot per maggiori informazioni sui cambiamenti."
#: en/PackageNotes.xml:56(title)
msgid "Kudzu"
@@ -1268,7 +1268,7 @@
"inserted media are no longer automatically added to the /etc/fstab file. Command-line users may migrate to gnome-mount, "
"which provides similar functionality."
-msgstr "Lo strumento fstab-sync ?? stato rimosso. In Fedora Core , il programma fstab-sync ?? stato rimosso in favore di soluzioni specifiche desktop per il montaggio dei media rimovibili. Linee di configurazione per le periferiche hotplug o media inseriti non sono pi?? automaticamente aggiunte al file /etc/fstab. Gli utenti della linea di comando, dovranno migrare a gnome-mount, che fornisce funzionalit?? similari."
+msgstr "Lo strumento fstab-sync ?? stato rimosso. In Fedora Core , il programma fstab-sync ?? stato rimosso in favore di soluzioni specifiche desktop per il montaggio dei media rimovibili. Nessuna linea di configurazione per le periferiche hotplug o media inseriti saranno pi?? automaticamente aggiunte al file /etc/fstab. Gli utenti della linea di comando, dovranno migrare a gnome-mount, che fornisce funzionalit?? similari."
#: en/PackageNotes.xml:64(title)
msgid "GnuCash"
@@ -1294,7 +1294,7 @@
"deprecated. It is shipped in Fedora Core 5 and applications can expect to "
"build against mozilla-devel, however it will be removed in a "
"future release of Fedora Core."
-msgstr "La suite di applicazioni Mozilla ?? deprecata. E' distribuita con Fedora Core 5 e ci si pu?? aspettare che le applicazioni possano compilarsi su mozilla-devel, comunque verr?? rimossa in una versione futura di Fedora Core."
+msgstr "La suite di applicazioni Mozilla ?? deprecata. E' distribuita con Fedora Core 5 e le applicazioni possono aspettare di compilarsi su mozilla-devel, comunque verr?? rimossa in una versione futura di Fedora Core."
#: en/PackageNotes.xml:72(title)
msgid "libstc++ preview"
@@ -3116,19 +3116,19 @@
"role=\"strong\">GNOME Screensaver(http://live.gnome.org/GnomeScreensaver/) "
"provide new and integrated power management capabilities."
-msgstr "Le ultime versioni di GNOME Power Manager (http://www.gnome.org/projects/gnome-power-manager/) e GNOME Screensaver(http://live.gnome.org/GnomeScreensaver/) forniscono nuove ed integrate capacit?? di power management."
+msgstr "Le ultime versioni di GNOME Power Manager (http://www.gnome.org/projects/gnome-power-manager/) e GNOME Screensaver (http://live.gnome.org/GnomeScreensaver/) forniscono nuove ed integrate capacit?? di power management."
#: en/OverView.xml:30(para)
msgid ""
"The new GNOME User Share facility "
"provides simple and efficient file sharing."
-msgstr "La nuova facility GNOME User Share fornisce una condivisione dei files semplice ed efficiente."
+msgstr "La nuova utilit?? GNOME User Share fornisce una condivisione dei files semplice ed efficiente."
#: en/OverView.xml:33(para)
msgid ""
"Suspend to RAM support has also been improved due to infrastructure work "
"done by the hibernate support."
-msgstr "Il supporto della sospensione in RAM ?? stato migliorato dovuto al lavoro fatto all'infrastruttura dal supporto hibernate."
+msgstr "Il supporto della sospensione in RAM ?? stato migliorato greazie al lavoro fatto all'infrastruttura dal supporto hibernate."
#: en/OverView.xml:36(para)
msgid ""
@@ -3209,7 +3209,7 @@
msgid ""
"This release includes libnotify, a library that features simple "
"and attractive notifications for the desktop."
-msgstr "Questa versione include libnotify, una libreria che presenta semplici ed attrattive notifiche per il desktop."
+msgstr "Questa versione include libnotify, una libreria che presenta semplici ed attraenti notifiche per il desktop."
#: en/OverView.xml:63(para)
msgid ""
@@ -3265,8 +3265,8 @@
"including both MySQL 5.0 and PostgreSQL 8.1."
msgstr ""
-"I pacchetti per l'ultima generazione di database servers sono stati preparati per questa versione, "
-"inclusi MySQL 5.0 e MySQL 5.0 e PostgreSQL 8.1."
#: en/OverView.xml:87(para)
@@ -3276,7 +3276,7 @@
"and the Apache Jakarta Project, in "
"addition to the Java programs and development capabilities in the previous "
"releases."
-msgstr "Diversi programmi Java nativi adesso sono disponibili compilati con GCJ, come il server J2EE Geronimo ed l'Apache Jakarta Project, oltre ai programmi Java ed alle possibilit?? di programmazione delle precedenti versioni."
+msgstr "Diversi programmi Java nativi adesso sono disponibili compilati con GCJ, come il server J2EE Geronimo ed il progetto Apache Jakarta, questo, in aggiunta ai programmi Java ed alle possibilit?? di programmazione delle versioni precedenti."
#: en/OverView.xml:90(para)
msgid ""
@@ -3292,7 +3292,7 @@
"Ci sono nuovi strumenti per il monitoraggio del sistema e l'analisi delle prestazioni. Questa release include SystemTap (http://fedoraproject.org/wiki/SystemTap), un sistema di strumentazione per il debugging e l'analisi dei colli di bottiglia prestazionali, e Frysk (http://fedoraproject.org/wiki/Frysk), una tecnologia di analisi dell'esecuzione per monitorizzare i processi o i threads in esecuzione."
+"fedoraproject.org/wiki/Frysk\">http://fedoraproject.org/wiki/Frysk), una tecnologia di analisi dell'esecuzione, per monitorizzare i processi o i threads in esecuzione."
#: en/OverView.xml:94(para)
msgid ""
@@ -3316,7 +3316,7 @@
msgid ""
"This release includes iscsi-initiator-utils, iSCSI daemon and "
"utility programs that provide support for hardware using the iSCSI interface."
-msgstr "Questa versione include iscsi-initiator-utils, il demone iSCSI ed i programmi di utilit?? che forniscono supporto per l'hardware usando l'interfaccia iSCSI."
+msgstr "Questa versione include iscsi-initiator-utils, il demone iSCSI ed i programmi di utilit?? che forniscono supporto per l'hardware che usa l'interfaccia iSCSI."
#: en/OverView.xml:105(title)
msgid "System Level Changes"
@@ -3372,8 +3372,8 @@
"Refer to the section on SELinux in these release notes for other details and "
"links to SELinux resources on the Fedora Project pages."
msgstr ""
-"L'implementazione di SELinux ha subito un cambiamento significativo con il cambiamento alla reference policy (http://serefpolicy.sourceforge.net/). La SELinux reference policy pu?? supportare moduli di policy binari. Ora ?? possibile muovere le policy SELinux in pacchetti individuali per poter consentire agli utenti di rilasciare customizzazioni pi?? peculiari per i sistemi quando richiesto. Questa versione aggiunge anche il supporto di Multi Category Security (MCS) abilitato per impostazione predefinita. e Multi Level Security (MLS). SELinux continua ad offrire supporto per il TE (Type Enforcement) abilitato per impostazione predefinita e RBAC (Role Based Access Control). Fa riferimento alla sezione su SELinux in queste notes di rilascio per altri dettagli e links a risorse SELinux sulle pagine del Progetto Fedora."
+"L'implementazione di SELinux ha subito un cambiamento significativo con il passaggio alla reference policy (http://serefpolicy.sourceforge.net/). La SELinux reference policy pu?? supportare moduli di policy binari. Ora ?? possibile spostare le policy SELinux in pacchetti individuali per poter consentire agli utenti di rilasciare personalizzazioni pi?? peculiari per i sistemi quando richiesto. Questa versione aggiunge anche il supporto di Multi Category Security (MCS), abilitato per impostazione predefinita e Multi Level Security (MLS). SELinux continua ad offrire supporto per il TE (Type Enforcement), abilitato per impostazione predefinita e RBAC (Role Based Access Control). Fa riferimento alla sezione su SELinux in queste notes di rilascio per altri dettagli e links a risorse SELinux sulle pagine del Progetto Fedora."
#: en/OverView.xml:126(title)
msgid "Road Map"
@@ -3386,7 +3386,7 @@
"RoadMap."
msgstr ""
"I piani proposti per la prossima versione di Fedora sono disponibili su http://fedoraproject.org/wiki/"
+"url=\"http://fedoraproject.org/wiki/it_IT/RoadMap\">http://fedoraproject.org/wiki/it_IT/"
"RoadMap."
#: en/Networking.xml:8(title)
@@ -3506,7 +3506,7 @@
#: en/Networking.xml:49(title)
msgid "Queue Avoidance upon Carrier Loss"
-msgstr "Impedimento di accodamento per perdita di linea"
+msgstr "Evitare l'accodamento per la perdita di linea"
#: en/Networking.xml:50(para)
msgid ""
@@ -3529,7 +3529,7 @@
"DCCP protocol. The implementation is still experimental, but is known to "
"work. Developers have begun work to make userspace applications aware of "
"this new protocol."
-msgstr "Il Kernel versione 2.6.14-rc1 fu la prima versione a ricevere supporto per il protocollo DCCP. L'implementazione ?? ancora sperimentale ma ?? risaputo che funziona. Gli sviluppatori hanno cominciato a creare applicazioni in userspace che sappiano di questo nuovo protocollo."
+msgstr "Il Kernel versione 2.6.14-rc1 fu la prima versione a ricevere supporto per il protocollo DCCP. L'implementazione ?? ancora sperimentale ma ?? risaputo che funziona. Gli sviluppatori hanno cominciato a creare applicazioni in userspace che sono a conoscenza di questo nuovo protocollo."
#: en/Networking.xml:57(title)
msgid "Wireless"
@@ -3620,7 +3620,7 @@
"administratively or because no carrier was found, such as if a cable were "
"unplugged. The new flag NO-CARRIER now appears as a link flag "
"if the link is administratively up but no carrier can be found."
-msgstr "In precedenza, non era possibile stabilire se un interfaccia fosse down amministrativamente o perche senza linea, come se il cavo fosse stato staccato. Il nuovo flag NO-CARRIER appare ora come link flag se il link ?? amministrativamente su ma non viene trovata linea."
+msgstr "In precedenza, non era possibile stabilire se un interfaccia fosse down amministrativamente o perch?? senza linea, come se il cavo fosse stato staccato. Il nuovo flag NO-CARRIER appare ora come link flag se il link ?? amministrativamente su ma non viene trovata linea."
#: en/Networking.xml:99(para)
msgid ""
@@ -3669,7 +3669,7 @@
"website at http://www.alsa-"
"project.org/."
msgstr ""
-"Fedora Core prende anche pieno vantaggio dal sistema sonoro Advanced Linux Sound Architecture (ALSA). Molti programmi possono suonare simultaneamente, una volta era difficile farlo con sui sistemi Linux. Quando tutti i software multimediali sono configurati per usare ALSA per il supporto sonoro, questa limitazione scompare. Per maggiori informazioni su ALSA, visita il sito web del progetto su http://www.alsa-"
+"Fedora Core prende anche pieno vantaggio dal sistema sonoro Advanced Linux Sound Architecture (ALSA). Molti programmi possono suonare simultaneamente, che una volta era difficile con i sistemi Linux. Quando tutti i software multimediali sono configurati per usare ALSA, per il supporto sonoro, questa limitazione scompare. Per maggiori informazioni su ALSA, visita il sito web del progetto su http://www.alsa-"
"project.org/."
#: en/Multimedia.xml:16(title)
@@ -3735,7 +3735,7 @@
"comprehensive how-to, refer to http://fedoraproject.org/wiki/ScreenCasting."
msgstr ""
-"Puoi usare Fedora per creare ed eseguire screencasts, che sono sessioni desktop registrate, utilizzando tecnologie libere. Fedora Extras 5 include istanbul, che crea screencasts usando il formato video Theora. Questi video possono essere visualizzati usando uno odei diversi lettori inclusi in Fedora Core. Questo ?? il modo preferibile di inviare screencasts al progetto Fedora sia per gli sviluppatori che per gli utenti finali. Per un pi?? comprensibile how-to, fa riferimento a screencasts, che sono sessioni desktop registrate, utilizzando tecnologie libere. Fedora Extras 5 include istanbul, che crea screencasts usando il formato video Theora. Questi video possono essere visualizzati usando uno dei diversi lettori inclusi in Fedora Core. Questo ?? il modo preferibile di inviare screencasts al progetto Fedora sia per gli sviluppatori che per gli utenti finali. Per un pi?? comprensibile how-to, fa riferimento a http://fedoraproject.org/wiki/ScreenCasting."
#: en/Multimedia.xml:32(title)
@@ -3768,7 +3768,7 @@
"Fedora Legacy Project, refer to http://fedoraproject.org/wiki/Legacy."
msgstr ""
-"Il Fedora Legacy Project ?? un progetto open source supportato dalla comunit?? per estendere il ciclo vitale di selezionate distribuzioni Red Hat Linux e Fedora Core in \"modalit?? mantenimento\". Il progetto Fedora Legacy lavora con la comunit?? Linux per fornire pacchetti di sicurezza e bug fix errata critici. Questo lavoro estende l'effettivo ciclo vitale delle vecchie distribuzioni in ambienti dove i frequenti aggiornamenti non sono possibili o desiderabili. Per maggiori informazioni sul Fedora Legacy Project, fa riferimento a http://fedoraproject.org/wiki/Legacy."
#: en/Legacy.xml:10(para)
@@ -3795,8 +3795,8 @@
"This provides an effective supported lifetime (Fedora Core plus Fedora "
"Legacy Support) of about 18 months."
msgstr ""
-"Il Fedora Legacy Project fornir?? aggiornamenti per queste versioni fin quando vi sar?? interesse della comunit??. Quando l'interesse non sar?? pi?? sostenuto, la modalit?? mantenimento finir??"
-"con la seconda versione test per la terza successiva versione Core. Per esempio, la modalit?? mantenimento per Fedora Core 4, se non sostenuta dalla comunit??, finir?? con il rilascio di Fedora Core 7 test2. Questo fornisce un effettivo supporto del ciclo vitale (Fedora Core pi?? supporto Fedora Legacy ) di circa 18 mesi."
+"Il Fedora Legacy Project fornir?? aggiornamenti per queste versioni fin quando vi sar?? interesse per la comunit??. Quando l'interesse non sar?? pi?? sostenuto, la modalit?? mantenimento finir?? "
+"con la seconda versione test per la terza successiva versione Core. Per esempio, la modalit?? mantenimento per Fedora Core 4, se non sostenuta dalla comunit??, finir?? con il rilascio di Fedora Core 7 test2. Questo risulta in un effettivo supporto del ciclo vitale (Fedora Core pi?? supporto Fedora Legacy ) di circa 18 mesi."
#: en/Legacy.xml:20(para)
msgid ""
@@ -3866,7 +3866,7 @@
msgid ""
"To obtain a list of these patches, download the source RPM package and run "
"the following command against it:"
-msgstr "Per ottenere una lista di queste patches, scarica il pacchetto RPM sogrgente ed esegui il seguente comando su di esso:"
+msgstr "Per ottenere una lista di queste patches, scarica il pacchetto RPM sorgente ed esegui il seguente comando su di esso:"
#: en/Kernel.xml:17(screen)
#, no-wrap
@@ -3896,7 +3896,7 @@
msgstr ""
"Se hai bisogno di una versione pi?? amichevole di changelog fa rifermento a http://wiki.kernelnewbies.org/"
-"LinuxChanges. Un breve e completo diff del kernel ?? disponibile su http://kernel.org/git. La versione Fedora ?? basata sul albero di Linus."
+"LinuxChanges. Un breve e completo diff del kernel ?? disponibile su http://kernel.org/git. La versione Fedora ?? basata sull'albero di Linus."
#: en/Kernel.xml:24(para)
msgid ""
@@ -4002,7 +4002,7 @@
"reporting bugs which are specific to Fedora."
msgstr ""
"Fa riferimento a http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html per informazioni sulla segnalazione di errori nel kernel di Linux kernel. Potrai inoltre usare http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html per informazioni sulla segnalazione di errori nel kernel di Linux. Potrai inoltre usare http://bugzilla.redhat.com per inviare quelle segnalazioni d'errore che sono specifiche per Fedora."
#: en/Kernel.xml:63(title)
@@ -4027,7 +4027,7 @@
#: en/Kernel.xml:66(para) en/Kernel.xml:85(para) en/Kernel.xml:100(para)
#: en/Extras.xml:20(para)
msgid "Enter the root password when prompted."
-msgstr "Immetti la password di root quando richiesto."
+msgstr "Immetti la password di root quando richiesta."
#: en/Kernel.xml:69(title)
msgid "Preparing for Kernel Development"
@@ -4072,14 +4072,14 @@
"instructions, simply substitute ~/rpmbuild/BUILD/kernel-<"
"version>/linux-<version>."
msgstr ""
-"La compilazione dei pacchetti come superuser ?? pericolosa e non ?? necessaria, anche per il kernel. Queste istruzioni ti permettono di installare i sorgenti del kernel come utente normale. Molte siti di informazione generali fanno riferimento a /usr/src/linux nelle loro istruzioni del kernel. Se usi queste istruzioni, sostituisci semplicemente ~/rpmbuild/BUILD/kernel-<"
+"La compilazione dei pacchetti come superuser ?? pericolosa e non ?? necessaria, anche per il kernel. Queste istruzioni ti permettono di installare i sorgenti del kernel come utente normale. Molti siti di informazione generali fanno riferimento a /usr/src/linux nelle loro istruzioni sul kernel. Se usi queste istruzioni, sostituisci semplicemente ~/rpmbuild/BUILD/kernel-<"
"version>/linux-<version>."
#: en/Kernel.xml:82(para)
msgid ""
"Prepare a RPM package building environment in your home directory. Run the "
"following commands:"
-msgstr "Prepara un ambiente di compilazione di pacchetti RPM package nella tua home directory. Esegui i seguenti comandi:"
+msgstr "Prepara un ambiente di compilazione di pacchetti RPM nella tua home directory. Esegui i seguenti comandi:"
#: en/Kernel.xml:83(screen)
#, no-wrap
@@ -4185,7 +4185,7 @@
"You can also find the .config file that matches your current "
"kernel configuration in the /lib/modules/<version>/build/."
"config file."
-msgstr "Puoi trovare inoltre il file .config che combacia la tua configurazione attuale del kernel nel file /lib/modules/<version>/build/.config."
+msgstr "Puoi trovare inoltre il file .config che combacia con la tua configurazione attuale del kernel nel file /lib/modules/<version>/build/.config."
#: en/Kernel.xml:125(para)
msgid ""
@@ -4196,7 +4196,7 @@
"emphasis> name from that of the running kernel. To be accepted by the "
"running kernel, a module must be compiled for a kernel with the correct "
"name. To do this, you must edit the kernel Makefile."
-msgstr "Ogni kernel prende il nome basandosi sul numero della sua versione. Questo ?? il valore mostrato dal comando uname -r. Il nome del kernel ?? definito dalle prime quattro linee del kernel Makefile. Il Makefile ?? stato cambiato per generare un kernel con un nome different da quello in esecuzione. Per essere accettato dal kernel in esecuzione, un modulo deve essere compilato per il kernel con il nome corretto. Per fare questo, devi editare il kernel Makefile."
+msgstr "Ogni kernel prende il nome basandosi sul numero della sua versione. Questo ?? il valore mostrato dal comando uname -r. Il nome del kernel ?? definito dalle prime quattro linee del kernel Makefile. Il Makefile ?? stato cambiato per generare un kernel con un nome differente da quello in esecuzione. Per essere accettato dal kernel in esecuzione, un modulo deve essere compilato per il kernel con il nome corretto. Per fare questo, devi editare il kernel Makefile. "
#: en/Kernel.xml:126(para)
msgid ""
@@ -4278,7 +4278,7 @@
#: en/Kernel.xml:154(title)
msgid "User Space Dependencies on the Kernel"
-msgstr "Dipendenze User Space sul Kernel"
+msgstr "Dipendenze User Space nel Kernel"
#: en/Kernel.xml:155(para)
msgid ""
@@ -4329,7 +4329,7 @@
msgstr ""
"Java ?? un marchio di Sun Microsystems. java-gcj-compat "
"?? uno stack di software interamente libero che non?? Java, ma pu?? eseguire software Java."
+"emphasis> ?? Java, ma pu?? eseguire software Java."
#: en/Java.xml:15(para)
msgid ""
@@ -4439,7 +4439,7 @@
"Research package compatibility before you install software from both the "
"Fedora and JPackage repositories on the same system. Incompatible packages "
"may cause complex issues."
-msgstr "Ricerca la compatibilit?? dei pacchetti prima di installare software da entrambe i repositori Fedora e JPackage sullo stesso sistema. Pacchetti incompatibili possono causare problemi complessi."
+msgstr "Verifica la compatibilit?? dei pacchetti prima di installare software da entrambe i repositori Fedora e JPackage sullo stesso sistema. Pacchetti incompatibili possono causare problemi complessi."
#: en/Installer.xml:8(title)
msgid "Installation-Related Notes"
@@ -4469,7 +4469,7 @@
"about obtaining and using the torrent file, refer to http://torrent.fedoraproject.org/."
msgstr ""
-"Se intendi scaricare l'immagine ISO DVD di Fedora Core 5, tieni a mente che non tutti gli strumenti di download file possono scaricare files pi?? grandi di 2GB. wget 1.9.1-16 o superiore, curl e ncftpget non hanno questa limitazione, e possono scaricare con successo files pi?? grandi di 2GB. BitTorrent ?? un altro metodo per scaricare grandi files. Per informazioni su come ottenere ed usare il file torrent fate riferimento a wget 1.9.1-16 o superiore, curl e ncftpget non hanno questa limitazione, e possono scaricare con successo files pi?? grandi di 2GB. BitTorrent ?? un altro metodo per scaricare grandi files. Per le informazioni su come ottenere ed usare il file torrent fa riferimento a http://torrent.fedoraproject.org/."
#: en/Installer.xml:25(title)
@@ -4804,23 +4804,23 @@
#: en/I18n.xml:20(para)
msgid "Japanese: scim-anthy"
-msgstr "Giapponese: scim-anthy"
+msgstr "Giapponese: scim-anthy "
#: en/I18n.xml:22(para)
msgid "Korean: scim-hangul"
-msgstr "Koreano: scim-hangul"
+msgstr "Koreano: scim-hangul "
#: en/I18n.xml:24(para)
msgid "Simplified Chinese: scim-pinyin scim-tables-chinese"
-msgstr "Cinese semplificato: scim-pinyin scim-tables-chinese"
+msgstr "Cinese semplificato: scim-pinyin scim-tables-chinese "
#: en/I18n.xml:26(para)
msgid "Traditional Chinese: scim-chewing scim-tables-chinese"
-msgstr "Cinese tradizionale: scim-chewing scim-tables-chinese"
+msgstr "Cinese tradizionale: scim-chewing scim-tables-chinese "
#: en/I18n.xml:28(para)
msgid "Indian and other languages: scim-m17n m17n-db-<language>"
-msgstr "Indiano ed altri linguaggi: scim-m17n m17n-db-<language>"
+msgstr "Indiano ed altri linguaggi: scim-m17n m17n-db-<language> "
#: en/I18n.xml:32(para)
msgid ""
@@ -5026,7 +5026,7 @@
"upgrade.html\">http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html."
msgstr ""
-"La versione 2 di Netatalk usa un metodo differente per immagazzinare i file resource forks dalle precedenti versioni, e potrebbe richiedere un differente schema di codifica dei nomi dei file. Sei pregato di leggere la documentazione e pianificare la tua migrazione prima di eseguire l'aggiornamento. Fa riferimento alle informazioni sull'aggiornamento disponibili direttamente dal sito Netatalk su http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html."
@@ -5067,7 +5067,7 @@
"feel these release notes could be improved in any way, you can provide your "
"feedback directly to the beat writers. Here are several ways to do so, in "
"order of preference:"
-msgstr "Grazie per l'interesse nel fornirci suggerimenti per queste note di rilascio. Se pensi che queste note possano essere migliorate in qualche modo, puoi inviare il tuo suggerimento direttamente all'autore del pezzo. Ci sono diversi modi per farlo, in ordine di preferenza:"
+msgstr "Ti ringraziamo per l'interesse nel fornirci suggerimenti per queste note di rilascio. Se pensi che queste note possano essere migliorate in qualche modo, puoi inviare il tuo suggerimento direttamente all'autore del pezzo. Ci sono diversi modi per farlo, in ordine di preferenza:"
#: en/Feedback.xml:20(para)
msgid ""
@@ -5101,7 +5101,7 @@
"DocsProject/ReleaseNotes/Beats\">http://fedoraproject.org/wiki/DocsProject/"
"ReleaseNotes/Beats."
msgstr ""
-"Un pezzo di nota di rilascio ?? un area delle note di rilascio la cui sorveglianza ?? responsabilit?? di uno o pi?? contributori di contenuti. Per maggiori informazioni sui pezzi, fa riferimento a http://fedoraproject.org/wiki/DocsProject/"
"ReleaseNotes/Beats."
@@ -5157,7 +5157,7 @@
"Applications > Add/Remove Software. Enter the "
"root password when prompted. Select the software you require "
"from the list, and choose Apply."
-msgstr "Per installare software dal repositorio Core o Extras, scegli Applicazioni > Aggiungi/Rimuovi Software. Immetti la password di root quando richiesto. Seleziona il software di cui hai bisogno dall'elenco e scegli Applica."
+msgstr "Per installare software dal repositorio Core o Extras, scegli Applicazioni > Aggiungi/Rimuovi Software. Immetti la password di root quando richiesta. Seleziona il software di cui hai bisogno dall'elenco e scegli Applica."
#: en/Extras.xml:18(para)
msgid ""
@@ -5303,7 +5303,7 @@
msgid ""
"This release of Fedora has been built with GCC 4.1 as the system compiler, "
"which is included with the distribution."
-msgstr "Questa versione di Fedora ?? stato compilata usando GCC 4.1, che ?? incluso nella distribuzione."
+msgstr "Questa versione di Fedora ?? stata compilata usando GCC 4.1, che ?? incluso nella distribuzione."
#: en/DevelToolsGCC.xml:11(title)
msgid "Caveats"
@@ -5464,7 +5464,7 @@
"GNOME 2.14 (or a release candidate) and KDE 3.5.1 are included in Fedora "
"Core 5. The following list includes notable changes to the desktop interface "
"in this release."
-msgstr "GNOME 2.14 (o una release candidate) e KDE 3.5.1 sono inclusi in Fedora Core 5. I seguenti elenchi includono i cambiamenti notevoli all'interfaccia desktop in questa versione."
+msgstr "GNOME 2.14 (o una release candidate) e KDE 3.5.1 sono inclusi in Fedora Core 5. Il seguente elenco include i cambiamenti pi?? evidenti dell'interfaccia desktop in questa versione."
#: en/Desktop.xml:13(emphasis)
msgid "gnome-power-manager"
@@ -5492,7 +5492,7 @@
msgid ""
"The GNOME Screensaver provides an "
"integrated user interface to screensavers and the lock screen dialog."
-msgstr "Gli GNOME Screensaver fornisce un'interfaccia utente integrata agli screensavers ad alla finestra di dialogo di blocco dello schermo."
+msgstr "Gli GNOME Screensaver forniscono un'interfaccia utente integrata agli screensavers ad alla finestra di dialogo di blocco dello schermo."
#: en/Desktop.xml:32(para)
msgid ""
@@ -5507,7 +5507,7 @@
"Fedora Extras provides a enhanced replacement for those who require it. You "
"can install it with the following command."
msgstr ""
-"A cominciare da GNOME 2.12 l'opzione terminale ?? stat rimossa dal men?? di contesto del desktop. Il pacchetto nautilus-open-terminal nel repositorio Fedora Extras fornisce un sostituto avanzato per coloro che ne hanno bisogno. Puoi installarlo "
+"A cominciare da GNOME 2.12 l'opzione terminale ?? stata rimossa dal men?? contestuale del desktop. Il pacchetto nautilus-open-terminal nel repositorio Fedora Extras fornisce un sostituto avanzato per coloro che ne hanno bisogno. Puoi installarlo "
"usando il seguente comando."
#: en/Desktop.xml:36(screen)
@@ -5525,7 +5525,7 @@
"video hardware. To install these extra screensavers, run the following "
"command:"
msgstr ""
-"In Fedora Core 5, solo un piccolo assortimento degli screensavers sono installati per impostazione predefinita. Alcuni utenti giudicano questi screensavers sgradevoli mentre altri potrebbero terminare brutalmente l'interfaccia grafica. Ci?? tende a succedere pi?? di frequente con certi screensavers animati OpenGL forniti nel pacchetto xscreensaver-gl-extras, quando usati con hardware scarsamente supportato. "
+"In Fedora Core 5, solo un piccolo assortimento di screensavers ?? installato per impostazione predefinita. Alcuni utenti giudicano questi screensavers sgradevoli mentre altri potrebbero terminare brutalmente l'interfaccia grafica. Ci?? tende a succedere pi?? di frequente con certi screensavers animati OpenGL forniti nel pacchetto xscreensaver-gl-extras, quando usati con hardware scarsamente supportato. "
"Per installare questi screensaver extra, esegui il seguente comando:"
#: en/Desktop.xml:40(screen)
@@ -5854,7 +5854,7 @@
#: en/BackwardsCompatibility.xml:11(para)
msgid "Enter the password for the root account when prompted."
-msgstr "Immetti la password di root quando richiesto."
+msgstr "Immetti la password di root quando richiesta."
#: en/ArchSpecificx86.xml:8(title)
msgid "x86 Specifics for Fedora"
@@ -5866,7 +5866,7 @@
"Fedora Core and the x86 hardware platform."
msgstr ""
"Questa sezione copre ogni informazione specifica che potresti aver bisogno "
-"di conoscere su Fedora Core e la piattaforma hardware x86."
+"di conoscere, su Fedora Core e la piattaforma hardware x86."
#: en/ArchSpecificx86.xml:11(title)
msgid "x86 Hardware Requirements"
@@ -5903,7 +5903,7 @@
msgstr ""
"Minimo: Pentium-class ??? Fedora Core 5 ?? ottimizzata per le CPU Pentium 4, ma "
"supporta anche CPU precedenti come il Pentium, Pentium Pro, Pentium II, "
-"Pentium III ed i processori AMD e VIA. Fedora tiene questo approccio poich?? "
+"Pentium III ed i processori AMD e VIA. Fedora prende questo approccio poich?? "
"le ottimizzazioni Pentium-class attualmente danno prestazioni ridotte per "
"processori di classe non-Pentium. In pi?? lo scheduling del Pentium4, con cui "
"sono fatti i processori di oggi, ?? sufficientemente differente per garantire "
@@ -5935,7 +5935,7 @@
#: en/ArchSpecificx86.xml:39(para)
msgid "Recommended for graphical: 256MiB"
-msgstr "Raccomandata per la modalit?? grafica: 256MiB"
+msgstr "RAM raccomandata per la modalit?? grafica: 256MiB"
#: en/ArchSpecificx86.xml:44(title) en/ArchSpecificx86_64.xml:29(title)
#: en/ArchSpecificPPC.xml:33(title)
@@ -5980,7 +5980,7 @@
"Fedora Core and the x86_64 hardware platform."
msgstr ""
"Questa sezione copre ogni informazione specifica che potresti aver bisogno "
-"di conoscere su Fedora Core e la piattaforma hardware x86_64."
+"di conoscere, su Fedora Core e la piattaforma hardware x86_64."
#: en/ArchSpecificx86_64.xml:11(title)
msgid "x86_64 Hardware Requirements"
@@ -6015,7 +6015,7 @@
"command, part of the yum-utils package in Fedora Extras, which "
"displays architecture by default. To install yum-utils, run the "
"following command:"
-msgstr "RPM supporta l'installazione parallela di molteplici architetture dello stesso pacchetto. Un elenco dei pacchetti predefinito come rpm -qa potrebbe sembrare non includere i pacchetti duplicati, poich?? l'architettura non ?? visualizzata. Invece usa il comando repoquery, parte del pacchetto yum-utils in Fedora Extras, che mostra l'architettura per impostazione predefinita. Per installare yum-utils, esegui il seguente comando:"
+msgstr "RPM supporta l'installazione parallela dello stesso pacchetto per molteplici architetture. Un normale elenco dei pacchetti come rpm -qa potrebbe sembrare includere pacchetti duplicati, poich?? l'architettura non ?? visualizzata. Usa invece il comando repoquery, che ?? parte del pacchetto yum-utils in Fedora Extras, che, per impostazione predefinita, mostra l'architettura. Per installare yum-utils, esegui il seguente comando:"
#: en/ArchSpecificx86_64.xml:39(screen)
#, no-wrap
@@ -6043,7 +6043,7 @@
"Fedora Core and the PPC hardware platform."
msgstr ""
"Questa sezione copre ogni informazione specifica che potresti aver bisogno "
-"di conoscere su Fedora Core e la piattaforma hardware PPC."
+"di conoscere, su Fedora Core e la piattaforma hardware PPC."
#: en/ArchSpecificPPC.xml:11(title)
msgid "PPC Hardware Requirements"
@@ -6102,7 +6102,7 @@
"with the Fn key, such as Option-Fn-"
"F3 to switch to virtual terminal tty3."
msgstr ""
-"Il tasto Option sui sistemi Apple ?? equivalente al tasto Alt sul PC. Dove la documentazione o il software d'installazione si riferiscono al tasto Alt, usa il tasto Option. Per alcune combinazioni di tasti potresti aver bisogno d'usare il tasto Option insieme al tasto Fn, tipo Option-Fn-"
+"Il tasto Option sui sistemi Apple ?? equivalente al tasto Alt sul PC. Dove la documentazione o il software d'installazione si riferiscono al tasto Alt, usa il tasto Option. Per alcune combinazioni di tasti potresti aver bisogno di usare il tasto Option insieme al tasto Fn, tipo Option-Fn-"
"F3 per cambiare al terminale virtuale tty3."
#: en/ArchSpecificPPC.xml:44(title)
@@ -6119,13 +6119,13 @@
#: en/ArchSpecificPPC.xml:48(para)
msgid "Apple Macintosh"
-msgstr "Apple Macintosh"
+msgstr "Apple Macintosh "
#: en/ArchSpecificPPC.xml:49(para)
msgid ""
"The bootloader should automatically boot the appropriate 32-bit or 64-bit "
"installer."
-msgstr "Il bootloader avvier?? automaticamente l'appropriato installer a 32-bit o 64-bit."
+msgstr "Il bootloader avvier?? automaticamente l'appropriato installer a 32-bit o 64-bit. "
#: en/ArchSpecificPPC.xml:50(para)
msgid ""
@@ -6143,7 +6143,7 @@
#: en/ArchSpecificPPC.xml:54(para)
msgid "64-bit IBM eServer pSeries (POWER4/POWER5)"
-msgstr "64-bit IBM eServer pSeries (POWER4/POWER5)"
+msgstr "64-bit IBM eServer pSeries (POWER4/POWER5) "
#: en/ArchSpecificPPC.xml:55(para)
msgid ""
@@ -6155,7 +6155,7 @@
#: en/ArchSpecificPPC.xml:58(para)
msgid "32-bit CHRP (IBM RS/6000 and others)"
-msgstr "32-bit CHRP (IBM RS/6000 ed altri)"
+msgstr "32-bit CHRP (IBM RS/6000 ed altri) "
#: en/ArchSpecificPPC.xml:59(para)
msgid ""
@@ -6169,7 +6169,7 @@
#: en/ArchSpecificPPC.xml:62(para)
msgid "Genesi Pegasos II"
-msgstr "Genesi Pegasos II"
+msgstr "Genesi Pegasos II "
#: en/ArchSpecificPPC.xml:63(para)
msgid ""
@@ -6200,14 +6200,14 @@
#: en/ArchSpecificPPC.xml:68(para)
msgid "Network booting"
-msgstr "Avvio dalla rete"
+msgstr "Avvio dalla rete "
#: en/ArchSpecificPPC.xml:69(para)
msgid ""
"You can find combined images containing the installer kernel and ramdisk in "
"the images/netboot/ directory of the installation tree. These "
"are intended for network booting with TFTP, but can be used in many ways."
-msgstr "Ci sono immagini combinate contenenti il kernel d'installazione ed il ramdisk nella directory images/netboot/ del albero d'installazione. Queste sono intese per l'avvio via network con TFTP, ma possono essere usate in molti modi."
+msgstr "Ci sono immagini combinate contenenti il kernel d'installazione ed il ramdisk nella directory images/netboot/ del albero d'installazione. Queste sono intese per l'avvio via network con TFTP, ma possono essere usate in molti modi. "
#: en/ArchSpecificPPC.xml:70(para)
msgid ""
From fedora-docs-commits at redhat.com Sat Mar 4 20:57:36 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 4 Mar 2006 15:57:36 -0500
Subject: mirror-tutorial/en_US - New directory
Message-ID: <200603042057.k24KvaCW015956@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/mirror-tutorial/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15941/en_US
Log Message:
Directory /cvs/docs/mirror-tutorial/en_US added to the repository
From fedora-docs-commits at redhat.com Sat Mar 4 20:58:36 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 4 Mar 2006 15:58:36 -0500
Subject: mirror-tutorial/en mirror-tutorial.xml,1.1,NONE
Message-ID: <200603042058.k24KwauW016009@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/mirror-tutorial/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15972/en
Removed Files:
mirror-tutorial.xml
Log Message:
Move to proper en_US locale
--- mirror-tutorial.xml DELETED ---
From fedora-docs-commits at redhat.com Sat Mar 4 20:58:42 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 4 Mar 2006 15:58:42 -0500
Subject: mirror-tutorial/en_US mirror-tutorial.xml,NONE,1.1
Message-ID: <200603042058.k24KwgRH016022@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/mirror-tutorial/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15972/en_US
Added Files:
mirror-tutorial.xml
Log Message:
Move to proper en_US locale
--- NEW FILE mirror-tutorial.xml ---
%FEDORA-ENTITIES-EN;
]>
IntroductionPurpose
This tutorial presents a number of related topics that allow an
administrator to seamlessly integrate mirroring and update
services for &FC;. Use these services to provision a classroom,
laboratory, or office. These service provisions also increase
ease of use and enhance user experience. They also add to the
perceived value of non-proprietary operating systems and
software.
&BUG-REPORTING;
Audience
You will find this tutorial more useful if you are a system
administrator, or a &FC; "power user" familiar with the
following topics:
&FC; system installation and administration
Basic Internet protocols (HTTP/Web)
Using a command line interface
About Mirrors
A mirrormirror is a server
that provides a copy of one or more collections of files.
Mirroring a site reduces traffic to the original source site,
thus spreading the stress and bandwidth costs of many users
across many sites. Side benefits of running a local mirror
include very fast access through the local network, providing
custom services to local users, and increasing your skills in
managing Internet services.
The site from which you retrieve files to build your mirror is
called an upstream mirrormirrorupstream. If possible, choose an upstream mirror that is
located close to you geographically. This reduces unnecessary
traffic across transcontinental sections of the Internet, where
bandwidth is limited and expensive. Use only upstream mirrors
that are intended for public access, unless you have permission
from the upstream mirror site administrator.
Additional Resources
For more information on installing &FC; see the &FC; &IG; at
&IG-URL;. For more information on basic Internet protocols, see
http://library.albany.edu/internet/internet.html,
or search Google at http://www.google.com/.
For more general information about mirrors, see http://en.wikipedia.org/wiki/Mirror_(computing).
Acknowledgements
Karsten Wade provided editorial services and kept the style
crisp and consistent. Stuart Ellis provided some additional
security-related information.
Planning and SetupThe Distribution Structure
The &FED; distributiondistribution, which is the collection of all &FED;-related
files, uses the directory tree in . It may include multiple
versions of &FC;. The tree design makes it easier to "trim"
unnecessary or undesired files. When you set up a mirror,
duplicate this tree exactly, or as closely as possible. If you
duplicate the tree, it will be easier to automate nightly
updates.
Fedora directory treefedora
+-- linux
+-- core
|-- 1
| ...
+-- &FCVER;
| +-- SRPMS
| +-- i386
| | +-- debug
| | +-- iso
| | +-- os
| | +-- Fedora
| | +-- SRPMS
| | +-- images
| | +-- isolinux
| +-- x86_64
+-- development
| ...
+-- test
| ...
+-- updates
+-- 1
| ...
+-- &FCVER;
| +-- SRPMS
| +-- i386
| +-- x86_64
+-- testing
+-- 1
| ...
+-- &FCVER;
+-- SRPMS
+-- i386
+-- x86_64Naming conventions
Throughout the rest of the document,
/var/www/mirror represents the folder
where all your mirrored files are stored. You may substitute a
different location. This location simplifies sharing your
mirror, due to the shipping configuration of &FC;. See for more information. The site
name mirror.example.com
represents the upstream mirror.
The
fedora/linux/core/&FCVER;/arch/os
directory contains a copy of all the original distribution files
for &FC; &FCVER;. They are the same files found on the DVD and
CD-ROM version of the distribution. The
&FED; subfolder contains all the files that
are necessary for installation, including the entire collection
of &FC; RPM packages. The images folder
contains copies of any floppy diskette or CD-ROM images that
boot a system into installation or rescue modes. The
fedora/linux/core/&FCVER;/arch/iso
folder contains images of the CD-ROM version of the
distribution.
RPM packagesRPMRPM, originally the Red Hat Package Manager and now
the RPM Package Manager, is not just a file format. RPM is
also a system that tracks and interconnects software and
version information. The RPM system is quite popular, and many
other Linux distributions use RPM as well. Read more
information on RPM at http://www.rpm.org/.
The SRPMS folders under
architecture-specific branches are links that point to the main
SRPMS folder for that distribution. For
example, fedora/linux/core/2/i386/os/SRPMS
is a link that points to
fedora/linux/core/2/SRPMS.
A &FED; mirror consists of at least the original ISO images
or the distribution files. If possible,
include both, provided you have sufficient disk space and/or
bandwidth.
Copying the Original Distribution
If you already have reliable CD-ROM installation discs of a
distribution, reduce your initial bandwidth and time spent
mirroring by copying the files from the discs to your server.
Copy all files from Installation Disc 1 into the
fedora/linux/core/&FCVER;/arch/os
folder. Then copy all files from the &FED;
folder of each of the remaining Installation discs into the
fedora/linux/core/&FCVER;/arch/os/&FED;
folder on the server.
Copy all the files from the SRPMS folder on
each of the "Sources" discs to the
fedora/linux/core/&FCVER;/SRPMS folder on
the server. Make a link in the os folder
that occurs under each architecture. Follow this example:
cd /var/www/mirror/fedora/linux/core/&FCVER;/i386/os/Fedora
ln ../../SRPMS SRPMS
The documentation for anacondaanaconda, the &FC; installation program, calls this directory
structure an exploded treeexploded tree. This is because the package data on each CD is extracted,
or exploded, to a large directory tree with a predetermined structure.
The anaconda installer expects this structure
to some extent.
If you only include CD images, create a mirror
suitable for installation services by mounting each CD image under the
arch/os/ directory. Make
a directory for each disc, naming them disc1,
disc2, and so on. Mount each disc on the
appropriate folder, and add entries to /etc/fstab
to perform this mount automatically in case of a reboot. Each entry
looks like this:
/path/i386/iso/FC&FCVER;-i386-disc1.iso /path/i386/os/disc1 iso9660 defaults 0 0
The anaconda installer application
automatically detects these folders and uses them properly. In
addition, system configuration tools such as
system-config-packages also continue
to work properly when pointed at the parent of the ISO image
mount points.
There are drawbacks to using CD ISO images in this fashion. For
instance, no one directory contains the entire distribution of RPM
packages. Soft links circumvent this problem, but your server security
policies may not permit them. &FC; also comes in a ISO format DVD image,
which alleviates this problem. Users who do not have DVD burning
hardware, however, cannot use this image to make discs for their own
use.
You only need a single line in /etc/fstab
for mounting the &FC; DVD ISO image. The entry looks like this:
/path/i386/iso/FC&FCVER;-i386-DVD.iso /path/i386/os iso9660 defaults 0 0Trimming Branches
You may omit almost any branch of the tree that you do not plan to use.
Consider carefully the impact of excluding that folder. Branches you
might trim from your mirror include:
Older versions of &FC; (any numbered directory).
Before you exclude an old version, ensure
this does not adversely affect any of your users. These adverse
affects can come in many forms. For example, the level of support
for certain hardware sometimes changes between releases of &FC;.
Users who cannot install a previous version may not be able to use
&FC;. Your users might need to perform software-related tasks such
as building packages for different &FC; releases. Always remain
aware of the needs of your users during the planning stage.
Folders for architectures your site does not support.
If you do not have any x86-64 hosts to support, trimming these
folders eliminates several gigabytes of extra files. If you
support x86-64 hosts later, though, you must restore mirroring of
these branches.
The development folder (formerly
"Rawhide").
This folder contains all the latest "bleeding-edge"
packages from the &FP;. If you participate in active &FED;
development, you should not trim this branch. &FED;
development moves at a rapid pace and requires frequent
updates to the latest development package
versions. However, the frequent updates cause your mirror
to download significant amounts of material during the
regular update cycle.
The testing folders.
These branches contain updates that are being subjected to
quality assurance through public testing, as well as the
test or "pre-release" versions of the &FC;
distribution. The testing folder
under the main core tree is where
test versions of the distribution, such as &FC;
&FCTESTVER;, are kept. (Users of &FC; test distributions
are often directed to use the
development branch to update
packages.) The testing folder, under
updates, contains package updates
that have not yet passed the public testing phase.
The debug folders.
These folders contain packages that enable developers and
skilled users to interpret data created when a program
crashes or encounters a bug. If you participate actively
in &FED; development, you should not trim these
folders. If you trim this branch, you may still download
individual packages as needed from a nearby public mirror
site.
The SRPMS folders (and links
thereto).
These folders contain the original source for all the
binary RPM packages in the distribution. You may download
these packages individually as needed to save space on
your local mirror.
Unless your site closely manages workstation configuration, you
should probably not trim any of the updates
branches for the distributions you support. These locations
contain packages with bug fixes, security patches, and errata
updates that your users probably want.
Downloading the Files
Locate a public mirror site for &FC; by referring to the main
project site's mirror page, &FDP-URL;. Once you have selected a
nearby mirror site, note what services it offers (FTP, HTTP,
and/or rsync). A mirror is usually servicing a large number of
users. Choose off-peak hours, when possible, to download a large
set of files. Be aware of any timezone differences when
estimating off-peak hours.
Download Using HTTP or FTP
To download via HTTP or FTP, use either the
wget or lftp
command. The wget command recurses
subdirectories automatically and pulls down entire trees of
data with a single command. If you are not careful, however,
it is possible to pull down much more data than you
intended. The following commands mirror the entire current
&FC; distribution:
cd /var/www/mirror
wget --mirror -np -nH --cut-dirs=2 http://mirror.example.com/pub/mirror/fedora/linux/core/&FCVER;/
Note the options used above:
--mirror turns on recursion (descends
into all subdirectories), and duplicates file timestamps;
-np prevents wget
from ascending into the parent directory;
-nH prevents wget
from writing a directory named after the host (in this
case,
mirror.example.com);
--cut-dirs=n
truncates the first n
directories in the path. In the example above,
--cut-dirs=2 prevents
wget from writing the
/pub/mirror
portion of the path into your mirror.
The same syntax works for both HTTP and FTP upstream
mirrors. It is possible that you may download some extraneous
files if the HTTP site formats its pages for browser
viewing. These files can be safely deleted, but return each
time the mirror updates unless you exclude them using special
options. See the wget man pages for more
information.
The lftp command works like the
wget command, and mirrors the content of a
HTTP or FTP server. The wget command,
however, does not delete old files locally. This feature is
important for update repository mirrors to stay synchronized
to upstream mirrors. New files are created and old files are
automatically removed from the upstream mirrors on a frequent
basis.
The lftp command synchronizes files and
directories from a remote host like rsync,
but uses HTTP or FTP protocols. Use the following command to
mirror the entire &FC; distribution with
lftp:
cd /var/www/mirror && \
lftp -c "open http://mirror.example.com/pub/mirror/linux/core/&FCVER;/i386/ && \
mirror --delete --verbose"
The parameter executes a set of commands
in a lftp process. Commands are separated
with && to prevent the
lftp command from executing if the
cd command fails. The commands in the
lftp command set work the same way. The
command syntax A && B is often
shorthand for "if A returns success, run B." An explanation
of the lftp commands follows:
open connects to the site and changes
directory automatically.
mirror fetches all files and
directories recursively in the current directory. The
--delete option excludes all local
files that are not in the remote directory. The
--verbose option prints some
information in the screen and is optional.
The lftp command above mantains an exact
copy of the directory for you. It downloads only new or
changed files, and deletes only those that no longer exist on
the upstream mirror.
As with wget, it is possible you may
download some unwanted files. The lftp
command supports regular expressions for excluding files
within a mirror command. The command below
shows how to mirror an current &FC; distribution updates
repository, excluding debug and
repodata directories:
cd /var/www/mirror && \
lftp -c "set mirror:exclude-regex 'debug\/|repodata\/' && \
open http://mirror.example.com/pub/mirror/linux/core/updates/&FCVER;/i386/ && \
mirror --delete --verbose"Consult the lftp man pages for more
details and usage options.Using Proxy for HTTP or FTP retrieval
If you are behind a proxy or firewall, you may need to use a
HTTP proxy to mirror files. To do this, export the
environment variables http_proxy and
ftp_proxy before you run the
wget or lftp commands:
export http_proxy=http://username:password@host:port
export ftp_proxy=http://username:password@host:portThe <command>rsync</command> Command
Use the rsync command to synchronize a set
of files and/or directories with a remote host. It operates in
much the same way as rcp, but it is usually
faster. One reason for the speed is that
rsync has a special protocol that evaluates
and skips files (or portions of files) that are already
downloaded.
Begin by identifying the modules available on the upstream
mirror site you have chosen. Note that the double colon "::"
is always used after the host name to separate it from the
rest of the rsync path. The following
command generates a list of "modules" on the upstream mirror.
rsync mirror.example.org::
These modules are roughly equivalent to top-level directories,
and they follow the same rules. To list any subdirectory of
the upstream mirror, add the directory path to the command
above. For example, on many mirrors, the
fedora-linux-core module is equivalent to
the fedora/linux/core path found at the
&FP; main download server. To list the contents of the &FC;
&FCVER; distribution folder on the upstream server, issue the
following command. Do not forget the trailing slash "/".
Without it, you only receive a listing of a folder name that
matches the last component of the remote path.
rsync mirror.example.org::fedora-linux-core/&FCVER;/Downloading Using <command>rsync</command>
To download via rsync, add a destination
path on your system to the end of the command line. The
resulting tree of files from the listing you perform are
downloaded to the local path you specify. Remember, if you
leave off the trailing slash on the remote path, then the last
component of that path is created as a folder, and its
contents are copied.
rsync filehouse.example.org::files/misc/ /var/www/misc/
When downloading using rsync for mirror purposes,
use some of the command line switches to improve performance and
feedback. The switches -PHav enable the following
rsync features:
-P
recover partially-downloaded files, and show a progress
meter
-H
preserve hard links
-a
recurse all directories, and preserve as much file
information as possible, including timestamps,
ownership, permissions, device files (if you are running
as root), and soft links
-v
give verbose feedback to the screen
Remove the -v switch if you run this mirroring
process as part of a script, or have no need to monitor progress. The
following example mirrors all available versions of &FC; from an
upstream site.
Example command downloads many gigabytes of files
This command downloads many gigabytes of files, and is intended for
use as an example only. Do not run this command if you do not
understand the consequences.
rsync -PHav mirror.example.org::fedora-linux-core/&FCVER;/ /var/www/mirror/fedora/linux/core/&FCVER;
The -n switch performs a "dry run" using
the other given parameters. Use this switch to test any
rsync command if you are unsure what files
you will receive. See also .
The -z switch enables compression during the
rsync process. The server compresses data before
transmission, and the client decompresses the data before writing it
to disk.
Compression using <command>rsync</command>
The vast majority of the &FC; distribution consists of RPM files,
which are already compressed data. Therefore, additional compression
does not save time, and instead induces an unnecessary load on the
upstream mirror CPU. As a courtesy, do not use the
-z switch for this purpose.
The next section features some additional switches that can be used to
automatically trim branches from the tree of downloaded folders. With
proper usage, they result in a mirror that is exactly as organized and
full-featured as any high-volume public upstream site.
Possible data loss
If you are not exceedingly careful in using these switches, it is
possible to delete large portions of your mirrored data. Fixing this
problem might require performing the copying steps outlined
in above. On the
other hand, if you are also careless about your destination path,
and you are running as root, you could put your entire system at
risk. Know your environment before using these switches:
What is your current working directory? Use
pwd to find out, if you are unsure.
Are you logged in as root? If you are using SELinux extensions,
what is your current security context?
Have you tested this command using the -n
switch (see )?
Use the --exclude switch, along with a simple
pattern, to disallow download of certain files and/or folders. For
instance, --exclude "*.iso" excludes the download
of any file whose name ends with the string ".iso".
Use the --delete switch, again with a pattern, to
remove any file from the local system which does not have a match on
the upstream mirror. This switch prevents unwanted file
debris from cropping up in your mirror. You can also use
it to retroactively trim branches of the tree which you no longer wish
to maintain or download.
Wildcards are permitted with rsync commands,
including the asterisk *, question
mark ?, and brackets
[ ]. The question mark and brackets
work as in the shell; the former matches any single character, while
the brackets define a set of characters to be matched. Asterisks are
especially powerful when combined with a portion of a file name. The
double asterisk ** pattern matches
any character, including slashes; a single
asterisk * matches any character, but
stops at a slash. Therefore, be judicious about using either. The
double asterisk is very useful for mirroring a tree that includes
multiple instances of directories and files that contain a pattern. A
good example is mirroring several versions of &FC;, where certain
folder names appear in every version.
Pattern matching wildcards
Use double asterisks to trim out directories that repeat throughout
a mirrored tree. For example, when mirroring for a site that
only uses i386 architecture machines, you may trim all files and
folders marked for x86_64 architecture, using the switch
--exclude "**x86_64**". This matches not only
folders marked x86_64, but also files such as
ISO images for x86_64, which are indicated by file names such as
FC&FCVER;-x86_64-disc1.iso.
Process a long list of exclusions and deletions with the
--exclude-from and --delete-from
options. Follow each tag with a file name that includes a list of
patterns, one per line, to be matched by the appropriate option.
These syntax hints only scratch the surface of
rsync, but suffice to make your first mirror. Once
you have selected your site and formulated your excludes and deletes,
run your rsync command with the
-n option. Redirect output to a file so you can
examine the resulting list of files in the editor or pager of your
choice.
The following example mirrors the entire &FC; &FCVER; distribution,
with --exclude options that avoid downloading:
Any information for x86_64 architecture;
Any yum headers (see );
Any debuginfo packages; and,
CD or DVD images.
The -n switch is included for testing purposes.
Backslashes at the ends of lines indicate this example is a single
command line.
rsync -Pan --delete --exclude "**x86_64**" --exclude "**headers**" \
--exclude "**debug**" --exclude "**iso**" \
mirror.example.com::fedora-linux-core/&FCVER;/ \
/var/www/mirror/fedora/core/&FCVER;Maintaining Your Mirror
&FED; mirrors are even more useful when they are more than just a
snapshot of the distribution at release time. Most mirror administrators
also choose to carry updates and errata packages. Repositories of
updates or development trees change daily, and your mirror should
reflect these changes.
<command>rsync</command> etiquette
If you plan to do regular updates of your mirror that include large
amounts of data, you should ask permission from the administrator of
the upstream mirror. Downloading nightly package updates for the
official releases of &FC; &FCVER; should not require notification, as
they are rarely more than a few megabytes. However, the
development tree routinely turns over several
hundred megabytes nightly. Take these factors into consideration
before putting any maintenance scripts into effect.
Once your rsync command is working as desire, you may
want to place it in a nightly cron script. The
cron system allows you to schedule
regularly-occurring jobs on your system. The intervals are highly
configurable, but a nightly run keeps your mirror synchronized with
updates and errata. Make sure your nightly cron job
follows some simple guidelines:
If your upstream mirror only synchronizes once or twice daily, run
your job after the upstream mirror completes
its update. This insures your mirror not only gets the freshest
material, but also does not interfere with the upstream server's
bandwidth while it runs its job. If you do not know this time, it is
usually safe to plan your downloads for pre-dawn hours.
Be sure you have sufficient disk space for additional packages. The
updates tree in particular grows over time as
more errata packages are released.
Always test your script thoroughly before allowing it to run
automatically. Use a -n or -v
switch in the rsync command line for testing, and
then remove it once you have completed testing. Remember that the
results are e-mailed to your account on your system unless you
specify differently. Read the crontab(5) man
pages for additional information, with the command man 5
crontab.
Server Configuration
This section describes how to set up a HTTP (Web) server to
support &FED; installation and software management applications.
Installing The Apache Web Server
&FC; provides the Apache server in the
httpd package. The
httpd package is included on &FED; systems
installed with the Server installation
type. You may have installed it later in order to run websites
or Web applications. &FEX; also offers alternative HTTP servers,
which are beyond the scope of this document.
To install the httpd package, if you have
not already done so, use the following command:
su -c 'yum install httpd'
Enter the password for the
root account when
prompted.
To start the service, use the following command:
su -c '/sbin/service httpd start'
Enter the password for the
root account when
prompted.
To enable this service to load automatically at boot time, use
the following command:
su -c '/sbin/chkconfig --level 345 httpd on'
Enter the password for the
root account when
prompted.
The default firewall configuration for &FED; blocks access from
remote systems. To enable other systems to connect to your HTTP
service, use the
system-config-securitylevel utility:
Choose DesktopSystem SettingsSecurity Level.
Enter the password for the
root account when
prompted.
Select WWW (HTTP) from the list of
services.
When prompted, select Yes to update the
firewall configuration.
Configuring The Apache Web Server
To enable HTTP access to the files in your mirror directory,
create the configuration file
/etc/httpd/conf.d/mirror.conf. The
following listing is an example:
Apache 2.x configuration file for &FED; mirror
AllowOverride None
Order Deny,Allow
Deny from all
Allow from 127.0.0.1 192.168.1
Options Indexes
]]>
You must use root privileges to create or copy files in the
directory /etc/httpd/conf.d/.
To update an active httpd service with a new
configuration, use the following command:
su -c '/sbin/service httpd reload'
Enter the password for the
root account when
prompted.
Your clients may now visit any area of your mirror by using the
URL
http://server.mydomain.org/mirror/path.
Apache and &SEL;
The default &SEL; configuration for &FED; permits Apache to
use files in the /var/www/ directory. If
you build your mirror in another directory, you may need to
modify the &SEL; policy.
Solving Dependencies
Every RPM package has a RPMheaderheader that contains all
the vital information about that package. This information
includes name, version and release, contents, the capabilities
provided by the package, and any prerequisites. These
prerequisites may include
dependenciesRPMdependencies. A dependency is a requirement for one or more
additional packages.
Packages installed without satisfying their dependencies may not
work correctly. Dependencies may create a problem for users who
are trying to install a single package. Manually determining and
resolving dependencies is difficult. &FC; provides the
yum utility for solving these dependencies
automatically, providing an improved user experience.
The Yellow Dog Updater Modified, or
yumyum, is a Python-based system for computing and solving
RPM dependencies. A yum client retrieves a
cache of headers from its repository server, as well as a list
of available RPM packages and their exact locations on the
server. It can do this via HTTP or FTP, as well as using
standard file system calls (either local or remote via NFS). The
client computes solutions to any package dependencies using the
downloaded header information, and requests all necessary
RPM packages once it has finished. The yum
command relies on rpm functions to perform
many of the computations involved in the process.
A drawback to yum is that the first time it
is run, it must download a header for every package installed on
the system in order to determine available updates. However,
running a local mirror nullifies this drawback. The
yum command can download many megabytes of
headers almost instantly on a standard Ethernet LAN. The
yum utility is the most popular update method
for &FC;.
For more information about using yum, refer
to .
Configuring Repositories
A yumrepositoryrepository is a collection of packages on a server which
supports yum clients. Repositories can serve
both types of clients if desired.
To set up a yum repository, you must write a
directory that contains information which the clients require to
resolve RPM dependencies. The directory's name depends on the
version of yum it supports. It is permissible
to have both kinds of repository information in a single
repository.
To support older yum clients, use the
yum-arch command. To support current
yum clients, use the
createrepo command.
Supporting &FC; 3 and beyond
&FC; 3 ships with a newer version of yum.
To support &FC; 3 yum clients, you
must use createrepo on
your server's repositories.
<command>yum-arch</command>
The yum-arch command creates a directory
named headers/ which supports older
versions of yum (before 2.2). The
yum-arch program searches recursively
through a target directory and any subdirectories for RPM
packages, and includes them in the header data. The
yum-arch command always creates the
headers/ directory in the current working
directory. Therefore you should change your working directory
to the directory where you want headers/
to appear.
cd /var/www/mirror/fedora/linux/core/&FCVER;/i386/os
su -c 'yum-arch -ls .'
Enter the root password at the prompt. The
-l switch follows symbolic links. The
-s switch includes SRPMS (source RPM
packages) in the header list. The command above creates the
yum header cache in the directory
/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/headers/.
<command>createrepo</command>
The createrepo command creates repository
information to support newer versions of
yum (and possibly other repository client
programs). The createrepo command stores
this data in a folder named repodata.
Run createrepo against the directory
under which you want the
repodata directory to appear. The
createrepo program also searches
recursively for RPM packages to include in the repository
data.
The following command creates the repository data in the
directory
/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/repodata.
su -c 'createrepo /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'
To create repository data for package groups in addition to
the package files, use the createrepo -g
command. The option requires a parameter
which points to the group file, relative
to the given location of the package data. The following
command creates the package group data corresponding to the
repository directly above. Note the relative location of the
group file
/var/www/mirror/fedora/linux/core/&FCVER;i386/os/Fedora/base/comps.xml.
su -c 'createrepo -g Fedora/base/comps.xml /var/www/mirror/fedora/linux/core/&FCVER;/i386/os'
You may have certain clients who update their version of
yum in a non-prescribed way. To minimize
problems for your clients, create both kinds of repository
data for any repositories. The extra repository information
is relatively small and will not affect your mirror's proper
function.
Repository Locations
Typically you will run yum-arch or
createrepo against at least the following
locations:
The stock distribution; for example,
/var/www/mirror/fedora/linux/core/&FCVER;/i386/os/.
For yum-arch, use the
-l and -s options to
follow the linked directory SRPMS and
include the source packages therein.
Official updates to the distribution; for example,
/var/www/mirror/fedora/linux/core/updates/&FCVER;/.
Once again, for yum-arch use
-l and/or -s if
appropriate.
Client Configuration
Client systems that use yum to contact your
mirror also require configuration. The yum
repository configuration files are located in
/etc/yum.repos.d and end with the suffix
.repo. Below is an example configuration
file.
Example
<filename>/etc/yum.repos.d/fedora-mirror.repo</filename>[mirror]
name=Fedora Core $releasever - $basearch - Base
baseurl=http://server.mydomain.net/mirror/fedora/linux/core/$releasever/$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
Client systems should use a repository configuration file for each
&FED; branch your mirror provides. The base distribution and
released updates, for example, each require a separate
configuration file.
If you want clients to use your mirror in place of the official
repositories, disable the existing repositories. To do this, edit
the client's file for the official repository to include the
directive enabled=0. You will need
root access to edit
these files.
Many repositories provide their own installable RPM packages
containing these configuration files. When a user installs the
RPM, the new files in /etc/yum.repos.d/
reference that repository. These packages simplify the addition
of new repositories for end users. Whether you use such a package
yourself will depend on the number and skill set of clients your
repository serves.
From fedora-docs-commits at redhat.com Sat Mar 4 20:58:31 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 4 Mar 2006 15:58:31 -0500
Subject: mirror-tutorial Makefile,1.7,1.8
Message-ID: <200603042059.k24Kx1Q7016025@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15972
Modified Files:
Makefile
Log Message:
Move to proper en_US locale
Index: Makefile
===================================================================
RCS file: /cvs/docs/mirror-tutorial/Makefile,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- Makefile 17 Feb 2006 23:32:38 -0000 1.7
+++ Makefile 4 Mar 2006 20:58:23 -0000 1.8
@@ -7,7 +7,7 @@
# Document-specific definitions.
#
DOCBASE = mirror-tutorial
-PRI_LANG = en
+PRI_LANG = en_US
OTHERS =
########################################################################
# List each XML file of your document in the template below. Append the
From fedora-docs-commits at redhat.com Sat Mar 4 21:37:16 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 4 Mar 2006 16:37:16 -0500
Subject: docs-common/images watermark-en.png, 1.3, 1.4 watermark-en.svg, 1.2,
1.3
Message-ID: <200603042137.k24LbGcH018267@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/images
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18241
Modified Files:
watermark-en.png watermark-en.svg
Log Message:
Centered text better; made "depreciated" message stronger.
Index: watermark-en.svg
===================================================================
RCS file: /cvs/docs/docs-common/images/watermark-en.svg,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- watermark-en.svg 2 Mar 2006 21:54:17 -0000 1.2
+++ watermark-en.svg 4 Mar 2006 21:37:08 -0000 1.3
@@ -8,10 +8,10 @@
Fedora Doc Project WatermarkThe word DRAFT rendered in grey at 45 degrees
-
+ DRAFT
- NOT FOR REFERENCE
- LOCALE "EN" DEPRECATED
+ NOT FOR REFERENCE
+ LOCALE "en_US", NOT "en"
From fedora-docs-commits at redhat.com Sat Mar 4 21:42:41 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 4 Mar 2006 16:42:41 -0500
Subject: docs-common Makefile.common,1.94,1.95
Message-ID: <200603042142.k24Lgft8018295@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18273
Modified Files:
Makefile.common
Log Message:
OK, OK, OK! We'll leave the default to XML2PO, but I'm keeping the
PO2XML line (commented out, though) until XML2PO works for me. It
may be a matter of one's robustness in handling the XML formatting
style rather than something obviously broken, but I'm not convinced.
Anyway, using XML2PO works for the release-notes and for right now,
"that's good enough"(tm).
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -r1.94 -r1.95
--- Makefile.common 4 Mar 2006 01:28:47 -0000 1.94
+++ Makefile.common 4 Mar 2006 21:42:33 -0000 1.95
@@ -412,8 +412,8 @@
define XML_template
$(patsubst ${PRI_LANG}/%,${1}/%,${2}):: ${2} po/${1}.po
mkdir -p ${1}
-# ${XML2PO} -k -p po/${1}.po ${2} >$$@
- ${PO2XML} ${2} po/${1}.po >$$@
+ ${XML2PO} -k -p po/${1}.po ${2} >$$@
+# ${PO2XML} ${2} po/${1}.po >$$@
endef
$(foreach L,${OTHERS}, \
From fedora-docs-commits at redhat.com Sat Mar 4 22:07:21 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 4 Mar 2006 17:07:21 -0500
Subject: docs-common Makefile.common,1.95,1.96
Message-ID: <200603042207.k24M7LVR020255@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20231
Modified Files:
Makefile.common
Log Message:
Added secret "make mrproper" target ;-)
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -r1.95 -r1.96
--- Makefile.common 4 Mar 2006 21:42:33 -0000 1.95
+++ Makefile.common 4 Mar 2006 22:07:00 -0000 1.96
@@ -824,6 +824,27 @@
#
#########################################################################
+
+#########################################################################
+# I'm going to bury this target deep at the bottom of the Makefile so
+# that maybe you won't see it ;-) This is a *VERY DANGEROUS* target
+# what will destroy *ALL* of your work, that of all the translators,
+# and probably cause dental cavities as well. You *DO NOT* want to
+# use this target, ever. The purpose of this target is to erase the
+# oh-so-carefully hand-crafted .POT and .PO translation files in addition
+# to all of the other generated product files. THIS IS THE ONLY TARGET
+# THAT WILL ERASE A .PO FILE! Unless you are working on the I18N part
+# of the FDP toolchain itself, you MUST NOT EVER use this target! It
+# voids all warranties! It will never show up on a "make help" list!
+mrproper: distclean
+ ${RM} po/*.*
+# OK, you tried it anyway didn't you? To recover you must:
+# 1) NOT DO A CVS COMMIT; and
+# 2) Immediately do a "cvs update po" to repair the damage; and
+# 3) Send $25.00USD to the charity of your choice; or
+# 4) Just pretend you didn't use this target in the first place.
+#########################################################################
+
#########################################################################
# End of Makefile.common
#########################################################################
From fedora-docs-commits at redhat.com Sat Mar 4 23:56:18 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sat, 4 Mar 2006 18:56:18 -0500
Subject: install-guide/en entities.xml, 1.2,
1.3 fedora-install-guide-firstboot.xml, 1.7, 1.8
Message-ID: <200603042356.k24NuIGI023198@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23090/en
Modified Files:
entities.xml fedora-install-guide-firstboot.xml
Log Message:
WARNING: This is broken, due to entities issue.
- Updated First Boot section to match Rawhide. Note that screenshots for this section will have to be redone prior to release.
Index: entities.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/entities.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- entities.xml 1 Mar 2006 21:45:41 -0000 1.2
+++ entities.xml 4 Mar 2006 23:56:10 -0000 1.3
@@ -14,11 +14,11 @@
Document version
- 1.22
+ 1.24Document date
- 2006-03-01
+ 2006-03-04Document ID string
Index: fedora-install-guide-firstboot.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-firstboot.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-firstboot.xml 2 Mar 2006 22:57:14 -0000 1.7
+++ fedora-install-guide-firstboot.xml 4 Mar 2006 23:56:10 -0000 1.8
@@ -1,4 +1,5 @@
+
To proceed, select Yes, I agree to the License
- Agreement and then select Next.
+ Agreement and then select
+ Forward.
@@ -107,7 +109,12 @@
By default the firewall is enabled, with a simple set of rules
that allow connections to be made from your system to others, but
- block incoming connections from other systems. You may make
+ permit only
+
+ SSH (Secure SHell)
+ firewall configuration
+
+ SSH (Secure SHell) connections from other systems. You may make
changes on this screen to allow access to specific network
services on your &FED; system.
@@ -134,24 +141,38 @@
SSH Provides Immediate Remote Access
-
- By default, &FED; installs and runs the SSH service. If you enable SSH access on this screen the user and root accounts may be used to access the system remotely.
-
+
+
+ All &FED; systems automatically run the SSH remote access
+ service. The default firewall configuration allows connections
+ to this service, to ensure that administrators have immediate
+ remote access to new systems through the user and
+ root accounts.
+
- To enable access to other services, enter the required ports in
- the Other ports: field. For each port, you
- must specify the port as TCP or UDP, in addition to the port
- number. Use the format
- portnumber:type.
- The majority of services use TCP ports.
+ To enable access to other services, select Other
+ ports, and Add the details. Use
+ the Port(s) field to specify either the port
+ number, or the registered name of the service. Select the relevant
+ Protocol from the drop-down. The majority of
+ services use the TCP protocol.
-
+
+ The Services List
+
+ The services file on every system lists the
+ port numbers and names of services that are registered with IANA
+ (Internet Assigned Names Authority). &FED; systems hold this
+ file in the directory /etc.
+
+
- For example, enter 143:tcp, 993:tcp to
- allow users to access mail from other systems with the IMAP
- protocol, which may use both TCP port 143 and TCP port 993.
+ If a service uses more than one port number, enter each port. For
+ example, to allow users on the system to access their mail with
+ the IMAP protocol, add TCP port 143 (imap), and TCP port 993
+ (imaps).
@@ -253,9 +274,10 @@
To adjust &SEL;, choose Modify SELinux
Policy. To exempt a key service from &SEL;
restrictions, select the service from the list, and choose the
- Remove SELinux protection option. The
+ Disable SELinux protection option. The
SELinux Service Protection item on the list
- includes options for additional services.
+ includes options to disable &SEL; restrictions on additional
+ services.
Changing the &SEL; policy
@@ -352,12 +374,10 @@
- To use an additional time server, either select it from the
- Server drop-down box, or type the DNS name in
- the box, and select Add. To remove a server
- or server pool from the list, select the name and click
- Delete. The drop-down box already has two
- listings as examples, which are servers provided by &RH;.
+ To use an additional time server, select Add,
+ and type the DNS name of the server into the box. To remove a
+ server or server pool from the list, select the name and click
+ Delete.
@@ -494,26 +514,72 @@
After you configure login services, select
- Next to proceed to the final screen.
+ Forward to proceed.
+
+
+
+ Sound Card
+
+
+ The Setup Agent automatically attempts
+ to identify the sound card in your computer.
-
- Finish Setup Screen
+
+ Sound Card Screen
-
+
-
+
- Finish setup screen.
-
+ Sound card screen.
+
- Click Next to proceed to the login screen.
+ Click the play button to check the sound card configuration. If
+ the configuration is correct, &FED; plays a sound sequence. You
+ may adjust the volume with the slidebar. The
+ Repeat option causes the sound to play until
+ the option is unselected, to assist you in tuning your system.
+
+
+
+ If your sound card is identified, but you do not hear the sound,
+ check your speakers and try again. In some cases, you may need to
+ alter the additional settings to obtain the best sound quality.
+
+
+
+ A sound card may provide multiple audio input and output devices.
+ To change the Default PCM device, select a
+ new option from the drop-down list. By default, audio applications
+ connect to a software mixer that manages the PCM devices. To
+ enable applications to bypass the software mixer, select the
+ option to Disable software mixing.
+
+
+
+ You may manually configure a &FC; system to use unsupported sound
+ cards after the installation process is complete. Manual sound
+ hardware configuration is beyond the scope of this document.
+
+
+ Changing the Sound Card
+
+ &FED; automatically attempts to detect a new sound card if you
+ add one to your system. If you need to launch the detection
+ process manually, choose System
+ AdministrationSoundcard
+ Detection.
+
+
+
+ Click Forward to proceed to the login screen.
Your &FC; system is now ready for use.
From fedora-docs-commits at redhat.com Sat Mar 4 23:56:12 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sat, 4 Mar 2006 18:56:12 -0500
Subject: install-guide rpm-info.xml,1.12,1.13
Message-ID: <200603042356.k24NuhsL023201@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23090
Modified Files:
rpm-info.xml
Log Message:
WARNING: This is broken, due to entities issue.
- Updated First Boot section to match Rawhide. Note that screenshots for this section will have to be redone prior to release.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- rpm-info.xml 3 Mar 2006 02:43:35 -0000 1.12
+++ rpm-info.xml 4 Mar 2006 23:56:05 -0000 1.13
@@ -28,10 +28,15 @@
+
+
+
+ Updated First Boot section.
+
- Boot options broken out into clearer subsections.
+ Boot options broken out into clearer subsections.
From fedora-docs-commits at redhat.com Sun Mar 5 03:02:25 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sat, 4 Mar 2006 22:02:25 -0500
Subject: install-guide/en fedora-install-guide-abouttoinstall.xml, 1.6,
1.7 fedora-install-guide-acknowledgements.xml, 1.6,
1.7 fedora-install-guide-adminoptions.xml, 1.8,
1.9 fedora-install-guide-beginninginstallation.xml, 1.7,
1.8 fedora-install-guide-bootloader.xml, 1.6,
1.7 fedora-install-guide-diskpartitioning.xml, 1.9,
1.10 fedora-install-guide-firstboot.xml, 1.8,
1.9 fedora-install-guide-installingpackages.xml, 1.6,
1.7 fedora-install-guide-intro.xml, 1.11,
1.12 fedora-install-guide-locale.xml, 1.8,
1.9 fedora-install-guide-networkconfig.xml, 1.6,
1.7 fedora-install-guide-nextsteps.xml, 1.7,
1.8 fedora-install-guide-other-instmethods.xml, 1.8,
1.9 fedora-install-guide-packageselection.xml, 1.8,
1.9 fedora-install-guide-rootpassword.xml, 1.6,
1.7 fedora-install-guide-techref.xml, 1.7,
1.8 fedora-install-guide-timezone.xml, 1.6,
1.7 fedora-install-guide-upgrading.xml, 1.6,
1.7 fedora-install-guide.xml, 1.8, 1.9
Message-ID: <200603050302.k2532PYp031278@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31226
Modified Files:
fedora-install-guide-abouttoinstall.xml
fedora-install-guide-acknowledgements.xml
fedora-install-guide-adminoptions.xml
fedora-install-guide-beginninginstallation.xml
fedora-install-guide-bootloader.xml
fedora-install-guide-diskpartitioning.xml
fedora-install-guide-firstboot.xml
fedora-install-guide-installingpackages.xml
fedora-install-guide-intro.xml fedora-install-guide-locale.xml
fedora-install-guide-networkconfig.xml
fedora-install-guide-nextsteps.xml
fedora-install-guide-other-instmethods.xml
fedora-install-guide-packageselection.xml
fedora-install-guide-rootpassword.xml
fedora-install-guide-techref.xml
fedora-install-guide-timezone.xml
fedora-install-guide-upgrading.xml fedora-install-guide.xml
Log Message:
Corrected paths to entities. Everywhere.
Index: fedora-install-guide-abouttoinstall.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-abouttoinstall.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-abouttoinstall.xml 2 Mar 2006 22:57:14 -0000 1.6
+++ fedora-install-guide-abouttoinstall.xml 5 Mar 2006 03:02:05 -0000 1.7
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-acknowledgements.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-acknowledgements.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-acknowledgements.xml 2 Mar 2006 22:57:14 -0000 1.6
+++ fedora-install-guide-acknowledgements.xml 5 Mar 2006 03:02:05 -0000 1.7
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-adminoptions.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-adminoptions.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-adminoptions.xml 3 Mar 2006 02:43:40 -0000 1.8
+++ fedora-install-guide-adminoptions.xml 5 Mar 2006 03:02:05 -0000 1.9
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-beginninginstallation.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-beginninginstallation.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-beginninginstallation.xml 2 Mar 2006 22:57:14 -0000 1.7
+++ fedora-install-guide-beginninginstallation.xml 5 Mar 2006 03:02:05 -0000 1.8
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-bootloader.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-bootloader.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-bootloader.xml 2 Mar 2006 22:57:14 -0000 1.6
+++ fedora-install-guide-bootloader.xml 5 Mar 2006 03:02:05 -0000 1.7
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-diskpartitioning.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-diskpartitioning.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-diskpartitioning.xml 3 Mar 2006 02:43:40 -0000 1.9
+++ fedora-install-guide-diskpartitioning.xml 5 Mar 2006 03:02:05 -0000 1.10
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-firstboot.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-firstboot.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-firstboot.xml 4 Mar 2006 23:56:10 -0000 1.8
+++ fedora-install-guide-firstboot.xml 5 Mar 2006 03:02:05 -0000 1.9
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-installingpackages.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-installingpackages.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-installingpackages.xml 2 Mar 2006 22:57:14 -0000 1.6
+++ fedora-install-guide-installingpackages.xml 5 Mar 2006 03:02:05 -0000 1.7
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-intro.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-intro.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- fedora-install-guide-intro.xml 3 Mar 2006 03:25:42 -0000 1.11
+++ fedora-install-guide-intro.xml 5 Mar 2006 03:02:05 -0000 1.12
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-locale.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-locale.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-locale.xml 3 Mar 2006 02:43:40 -0000 1.8
+++ fedora-install-guide-locale.xml 5 Mar 2006 03:02:05 -0000 1.9
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-networkconfig.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-networkconfig.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-networkconfig.xml 2 Mar 2006 22:57:14 -0000 1.6
+++ fedora-install-guide-networkconfig.xml 5 Mar 2006 03:02:05 -0000 1.7
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-nextsteps.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-nextsteps.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-nextsteps.xml 3 Mar 2006 02:43:40 -0000 1.7
+++ fedora-install-guide-nextsteps.xml 5 Mar 2006 03:02:05 -0000 1.8
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-other-instmethods.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-other-instmethods.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-other-instmethods.xml 3 Mar 2006 02:43:40 -0000 1.8
+++ fedora-install-guide-other-instmethods.xml 5 Mar 2006 03:02:05 -0000 1.9
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-packageselection.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-packageselection.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide-packageselection.xml 3 Mar 2006 02:43:40 -0000 1.8
+++ fedora-install-guide-packageselection.xml 5 Mar 2006 03:02:05 -0000 1.9
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-rootpassword.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-rootpassword.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-rootpassword.xml 2 Mar 2006 22:57:14 -0000 1.6
+++ fedora-install-guide-rootpassword.xml 5 Mar 2006 03:02:05 -0000 1.7
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-techref.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-techref.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- fedora-install-guide-techref.xml 3 Mar 2006 02:43:40 -0000 1.7
+++ fedora-install-guide-techref.xml 5 Mar 2006 03:02:05 -0000 1.8
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-timezone.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-timezone.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-timezone.xml 2 Mar 2006 22:57:14 -0000 1.6
+++ fedora-install-guide-timezone.xml 5 Mar 2006 03:02:05 -0000 1.7
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide-upgrading.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-upgrading.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fedora-install-guide-upgrading.xml 2 Mar 2006 22:57:14 -0000 1.6
+++ fedora-install-guide-upgrading.xml 5 Mar 2006 03:02:05 -0000 1.7
@@ -5,7 +5,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
Index: fedora-install-guide.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fedora-install-guide.xml 2 Mar 2006 22:57:14 -0000 1.8
+++ fedora-install-guide.xml 5 Mar 2006 03:02:05 -0000 1.9
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOC-ENTITIES;
]>
From fedora-docs-commits at redhat.com Sun Mar 5 05:52:01 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun, 5 Mar 2006 00:52:01 -0500
Subject: example-tutorial/en_US example-tutorial.xml,1.1,1.2
Message-ID: <200603050552.k255q1uC002863@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/example-tutorial/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2841/en_US
Modified Files:
example-tutorial.xml
Log Message:
Use locale-independant filename "para.xml" instead of "para-en.xml".
Index: example-tutorial.xml
===================================================================
RCS file: /cvs/docs/example-tutorial/en_US/example-tutorial.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- example-tutorial.xml 2 Mar 2006 22:33:35 -0000 1.1
+++ example-tutorial.xml 5 Mar 2006 05:51:52 -0000 1.2
@@ -6,7 +6,7 @@
%FEDORA-ENTITIES;
-
+
%DOCUMENT-ENTITIES;
]>
@@ -33,7 +33,8 @@
- Could not find the para-en.xml file
+ Could not find the para.xml file for this
+ locale.
From fedora-docs-commits at redhat.com Sun Mar 5 07:10:17 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun, 5 Mar 2006 02:10:17 -0500
Subject: release-notes Makefile,1.29,1.30
Message-ID: <200603050710.k257AHZu006693@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6675
Modified Files:
Makefile
Log Message:
added it to others
Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- Makefile 4 Mar 2006 06:21:50 -0000 1.29
+++ Makefile 5 Mar 2006 07:09:51 -0000 1.30
@@ -8,7 +8,7 @@
#
DOCBASE = RELEASE-NOTES
PRI_LANG = en
-OTHERS = zh_CN pt_BR #it pa ru
+OTHERS = zh_CN pt_BR it# pa ru
########################################################################
# List each XML file of your document in the template below. Append the
From fedora-docs-commits at redhat.com Sun Mar 5 08:29:08 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun, 5 Mar 2006 03:29:08 -0500
Subject: release-notes/po it.po,1.3,1.4
Message-ID: <200603050829.k258T8iV008806@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8788
Modified Files:
it.po
Log Message:
updated with Xen translation :)
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.3 -r 1.4 it.po
Index: it.po
===================================================================
RCS file: /cvs/docs/release-notes/po/it.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- it.po 4 Mar 2006 18:16:47 -0000 1.3
+++ it.po 5 Mar 2006 08:28:59 -0000 1.4
@@ -4,8 +4,8 @@
msgid ""
msgstr ""
"Project-Id-Version: it\n"
-"POT-Creation-Date: 2006-03-01 18:52+0100\n"
-"PO-Revision-Date: 2006-03-04 18:43+0100\n"
+"POT-Creation-Date: 2006-03-05 09:23+0100\n"
+"PO-Revision-Date: 2006-03-05 09:27+0100\n"
"Last-Translator: Francesco Tombolini \n"
"Language-Team: Italiano \n"
"MIME-Version: 1.0\n"
@@ -15,21 +15,22 @@
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: en/Xorg.xml:5(title) en/Welcome.xml:5(title) en/WebServers.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/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)
msgid "Temp"
msgstr "Temporaneo"
@@ -72,8 +73,8 @@
msgstr ""
"Puoi usare Applicazioni => Impostazioni di sistema => "
"Schermo o eseguire system-config-"
-"display per configurare le impostazioni. Il file di configurazione per Xorg "
-"?? collocato in /etc/X11/xorg.conf."
+"display per configurare le impostazioni. Il file di "
+"configurazione per Xorg ?? collocato in /etc/X11/xorg.conf."
#: en/Xorg.xml:14(para)
msgid ""
@@ -84,10 +85,12 @@
"url=\"http://fedoraproject.org/wiki/Xorg/Modularization\">http://"
"fedoraproject.org/wiki/Xorg/Modularization."
msgstr ""
-"X.org X11R7 ?? la prima versione modulare di X.org, che, oltre a diversi altri benefici , consente aggiornamenti pi?? veloci ed aiuta i programmatori a sviluppare e rilasciare componenti specifici rapidamente. Maggiori informazioni sullo status attuale dello sforzo di modularizzazione "
-"di Xorg in Fedora ?? disponibile su http://"
-"fedoraproject.org/wiki/Xorg/Modularization."
+"X.org X11R7 ?? la prima versione modulare di X.org, che, oltre a diversi "
+"altri benefici , consente aggiornamenti pi?? veloci ed aiuta i programmatori "
+"a sviluppare e rilasciare componenti specifici rapidamente. Maggiori "
+"informazioni sullo status attuale dello sforzo di modularizzazione di Xorg "
+"in Fedora ?? disponibile su http://fedoraproject.org/wiki/Xorg/Modularization."
#: en/Xorg.xml:17(title)
msgid "X.org X11R7 End-User Notes"
@@ -104,10 +107,10 @@
"Xorg/3rdPartyVideoDrivers\">http://fedoraproject.org/wiki/"
"Xorg/3rdPartyVideoDrivers."
msgstr ""
-"Prima di installare qualsiasi drivers di terze parti da qualunque venditore, incluso ATI o "
-"nVidia, sei pregato di leggere http://fedoraproject.org/wiki/"
-"Xorg/3rdPartyVideoDrivers."
+"Prima di installare qualsiasi drivers di terze parti da qualunque venditore, "
+"incluso ATI o nVidia, sei pregato di leggere http://fedoraproject.org/"
+"wiki/Xorg/3rdPartyVideoDrivers."
#: en/Xorg.xml:25(para)
msgid ""
@@ -118,8 +121,13 @@
"url=\"mailto:xorg at freedesktop.org\">xorg at freedesktop.org mailing "
"list if you do need assistance reconfiguring your keyboard."
msgstr ""
-"Gli scripts d'installazione del pacchetto xorg-x11-server-Xorg rimuovono automaticamente la linea RgbPath dal file xorg.conf se presente. Potresti avere la necessit?? di riconfigurare la tua tastiera differentemente da quella che usi. Sei incoraggiato a sottoscriverti alla mailing list xorg at freedesktop.org se hai bisogno di assistenza nel riconfigurare la tua tastiera."
+"Gli scripts d'installazione del pacchetto xorg-x11-server-Xorg "
+"rimuovono automaticamente la linea RgbPath dal file xorg."
+"conf se presente. Potresti avere la necessit?? di riconfigurare la tua "
+"tastiera differentemente da quella che usi. Sei incoraggiato a "
+"sottoscriverti alla mailing list xorg at freedesktop.org se hai bisogno di assistenza nel "
+"riconfigurare la tua tastiera."
#: en/Xorg.xml:28(title)
msgid "X.org X11R7 Developer Overview"
@@ -129,15 +137,17 @@
msgid ""
"The following list includes some of the more visible changes for developers "
"in X11R7:"
-msgstr "L'elenco seguente include alcuni fra i pi?? evidenti cambiamenti per gli sviluppatori in X11R7:"
+msgstr ""
+"L'elenco seguente include alcuni fra i pi?? evidenti cambiamenti per gli "
+"sviluppatori in X11R7:"
#: en/Xorg.xml:32(para)
msgid ""
"The entire buildsystem has changed from imake to the GNU "
"autotools collection."
msgstr ""
-"L'intero sistema di compilazione ?? cambiato da imake alla collezione GNU "
-"autotools."
+"L'intero sistema di compilazione ?? cambiato da imake alla "
+"collezione GNU autotools."
#: en/Xorg.xml:35(para)
msgid ""
@@ -146,9 +156,10 @@
"instead of hard coding paths to them in /usr/X11R6/lib or elsewhere."
msgstr ""
-"Tutte le librerie ora installano file pkgconfig*.pc, che ora dovrebbero essere sempre usate dal software che dipende da queste librerie, invece di "
-"inglobare nel codice i percorsi a queste in /usr/X11R6/lib o altrove."
+"Tutte le librerie ora installano file pkgconfig*.pc, che ora dovrebbero essere sempre usate dal software che dipende da "
+"queste librerie, invece di inglobare nel codice i percorsi a queste in "
+"/usr/X11R6/lib o altrove."
#: en/Xorg.xml:40(para)
msgid ""
@@ -158,13 +169,22 @@
"preferably to dynamically detect the proper location of the object. "
"Developers are strongly advised against "
"hard-coding the new X11R7 default paths."
-msgstr "Ogni cosa ?? ora installata direttamente in /usr invece di /usr/X11R6. Tutto il software i cui percorsi sono compilati all'interno del codice in /usr/X11R6, devono ora essere cambiati preferibilmente per determinare dinamicamente l'appropriata posizione dell'oggetto. Gli sviluppatori sono fortemente sconsigliati di inglobare nel codice i percorsi predefiniti del nuovo X11R7."
+msgstr ""
+"Ogni cosa ?? ora installata direttamente in /usr invece di "
+"/usr/X11R6. Tutto il software i cui percorsi sono "
+"compilati all'interno del codice in /usr/X11R6, "
+"devono ora essere cambiati preferibilmente per determinare dinamicamente "
+"l'appropriata posizione dell'oggetto. Gli sviluppatori sono fortemente sconsigliati di inglobare nel codice i "
+"percorsi predefiniti del nuovo X11R7."
#: en/Xorg.xml:45(para)
msgid ""
"Every library has its own private source RPM package, which creates a "
"runtime binary subpackage and a -devel subpackage."
-msgstr "Ogni libreria possiede il suo pacchetto sorgente RPM privato, che crea un sottopacchetto di binari eseguibili ed un sottopacchetto -devel."
+msgstr ""
+"Ogni libreria possiede il suo pacchetto sorgente RPM privato, che crea un "
+"sottopacchetto di binari eseguibili ed un sottopacchetto -devel."
#: en/Xorg.xml:50(title)
msgid "X.org X11R7 Developer Notes"
@@ -174,7 +194,10 @@
msgid ""
"This section includes a summary of issues of note for developers and "
"packagers, and suggestions on how to fix them where possible."
-msgstr "Questa sezione include un sommario di problematiche di note per gli sviluppatori ed i creatori di pacchetti, e suggerimenti su come fissarli quando possibile."
+msgstr ""
+"Questa sezione include un sommario di problematiche di note per gli "
+"sviluppatori ed i creatori di pacchetti, e suggerimenti su come fissarli "
+"quando possibile."
#: en/Xorg.xml:53(title)
msgid "The /usr/X11R6/ Directory Hierarchy"
@@ -190,8 +213,14 @@
"determine where the files reside, or alternatively to hard code the new "
"locations, possibly with fallbacks."
msgstr ""
-"X11R7 si installa direttamente in /usr ora, e non usa pi?? la gerarchia /usr/X11R6. Le applicazioni che contano che i files siano presenti nel percorso fisso sotto /usr/X11R6/ durante la compilazione o l'esecuzione, devono essere aggiornate. Esse debbono usare ora il system PATH, o alcuni altri meccanismi, per determinare dinamicamente dove risiedono i files, o alternativamente "
-"inglobare nel codice i nuovi percorsi, possibilmente con fallback."
+"X11R7 si installa direttamente in /usr ora, e non usa pi?? la "
+"gerarchia /usr/X11R6. Le applicazioni che contano "
+"che i files siano presenti nel percorso fisso sotto /usr/X11R6/ durante la compilazione o l'esecuzione, devono essere "
+"aggiornate. Esse debbono usare ora il system PATH, o alcuni "
+"altri meccanismi, per determinare dinamicamente dove risiedono i files, o "
[...3584 lines suppressed...]
+"occupato da Fedora Core 5 dopo aver completato l'installazione. Comunque, "
+"altro spazio su disco ?? necessario durante l'installazione per il supporto "
+"dell'ambiente d'installazione. Questo spazio aggiuntivo corrisponde alla "
+"grandezza di /Fedora/base/stage2.img sul Disco d'installazione "
+"1 pi?? la grandezza dei files in /var/lib/rpm sul sistema "
+"installato."
#: en/ArchSpecificx86.xml:46(para) en/ArchSpecificx86_64.xml:31(para)
#: en/ArchSpecificPPC.xml:35(para)
@@ -5961,14 +6942,20 @@
"as 90 MiB for a minimal installation to as much as an additional 175 MiB for "
"an \"everything\" installation. The complete packages can occupy over 9 GB "
"of disk space."
-msgstr "In termini pratici, vuol dire che i requisiti di spazio su disco possono variare da un minimo di 90MiB per un installazione minima ad un massimo di 175MiB per un installazione \"totale\". I pacchetti completi possono occupare pi?? di 9 GB di spazio su disco."
+msgstr ""
+"In termini pratici, vuol dire che i requisiti di spazio su disco possono "
+"variare da un minimo di 90MiB per un installazione minima ad un massimo di "
+"175MiB per un installazione \"totale\". I pacchetti completi possono "
+"occupare pi?? di 9 GB di spazio su disco."
#: en/ArchSpecificx86.xml:47(para) en/ArchSpecificx86_64.xml:32(para)
#: en/ArchSpecificPPC.xml:36(para)
msgid ""
"Additional space is also required for any user data, and at least 5% free "
"space should be maintained for proper system operation."
-msgstr "Ulteriore spazio ?? richiesto per ogni dato utente, ed almeno il 5% di spazio libero dovr?? essere mantenuto affinch?? il sistema funzioni correttamente."
+msgstr ""
+"Ulteriore spazio ?? richiesto per ogni dato utente, ed almeno il 5% di spazio "
+"libero dovr?? essere mantenuto affinch?? il sistema funzioni correttamente."
#: en/ArchSpecificx86_64.xml:8(title)
msgid "x86_64 Specifics for Fedora"
@@ -6015,7 +7002,14 @@
"command, part of the yum-utils package in Fedora Extras, which "
"displays architecture by default. To install yum-utils, run the "
"following command:"
-msgstr "RPM supporta l'installazione parallela dello stesso pacchetto per molteplici architetture. Un normale elenco dei pacchetti come rpm -qa potrebbe sembrare includere pacchetti duplicati, poich?? l'architettura non ?? visualizzata. Usa invece il comando repoquery, che ?? parte del pacchetto yum-utils in Fedora Extras, che, per impostazione predefinita, mostra l'architettura. Per installare yum-utils, esegui il seguente comando:"
+msgstr ""
+"RPM supporta l'installazione parallela "
+"dello stesso pacchetto per molteplici architetture. Un normale elenco dei "
+"pacchetti come rpm -qa potrebbe sembrare includere pacchetti "
+"duplicati, poich?? l'architettura non ?? visualizzata. Usa invece il comando "
+"repoquery, che ?? parte del pacchetto yum-utils in "
+"Fedora Extras, che, per impostazione predefinita, mostra l'architettura. Per "
+"installare yum-utils, esegui il seguente comando:"
#: en/ArchSpecificx86_64.xml:39(screen)
#, no-wrap
@@ -6026,7 +7020,9 @@
msgid ""
"To list all packages with their architecture using rpm, run the "
"following command:"
-msgstr "Per elencare tutti i pacchetti con le loro architetture usa rpm, eseguendo il seguente comando:"
+msgstr ""
+"Per elencare tutti i pacchetti con le loro architetture usa rpm, eseguendo il seguente comando:"
#: en/ArchSpecificx86_64.xml:41(screen)
#, no-wrap
@@ -6061,13 +7057,17 @@
msgid ""
"Fedora Core 5 supports only the ???New World??? generation of Apple Power "
"Macintosh, shipped from circa 1999 onward."
-msgstr "Fedora Core 5 supporta solo la generazione ???New World??? degli Apple Power Macintosh, venduti circa dal 1999 in poi."
+msgstr ""
+"Fedora Core 5 supporta solo la generazione ???New World??? degli Apple Power "
+"Macintosh, venduti circa dal 1999 in poi."
#: en/ArchSpecificPPC.xml:22(para)
msgid ""
"Fedora Core 5 also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos "
"II, and IBM Cell Broadband Engine machines."
-msgstr "Fedora Core supporta anche gli IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, e le macchine IBM Cell Broadband Engine."
+msgstr ""
+"Fedora Core supporta anche gli IBM eServer pSeries, IBM RS/6000, Genesi "
+"Pegasos II, e le macchine IBM Cell Broadband Engine."
#: en/ArchSpecificPPC.xml:25(para)
msgid "Recommended for text-mode: 233 MHz G3 or better, 128MiB RAM."
@@ -6086,8 +7086,13 @@
"Fedora/base/stage2.img (on Installtion Disc 1) plus the size of the "
"files in /var/lib/rpm on the installed system."
msgstr ""
-"I requisiti di spazio su disco sottoelencati rappresentano lo spazio occupato da Fedora Core 5 dopo aver completato l'installazione. Comunque, altro spazio su disco ?? necessario durante l'installazione per il supporto dell'ambiente d'installazione. Questo spazio aggiuntivo corrisponde alla grandezza di /Fedora/base/stage2.img (sul Disco d'installazione 1) pi?? la "
-"grandezza dei files in /var/lib/rpm sul sistema installato."
+"I requisiti di spazio su disco sottoelencati rappresentano lo spazio "
+"occupato da Fedora Core 5 dopo aver completato l'installazione. Comunque, "
+"altro spazio su disco ?? necessario durante l'installazione per il supporto "
+"dell'ambiente d'installazione. Questo spazio aggiuntivo corrisponde alla "
+"grandezza di /Fedora/base/stage2.img (sul Disco d'installazione "
+"1) pi?? la grandezza dei files in /var/lib/rpm sul sistema "
+"installato."
#: en/ArchSpecificPPC.xml:40(title)
msgid "The Apple keyboard"
@@ -6102,8 +7107,13 @@
"with the Fn key, such as Option-Fn-"
"F3 to switch to virtual terminal tty3."
msgstr ""
-"Il tasto Option sui sistemi Apple ?? equivalente al tasto Alt sul PC. Dove la documentazione o il software d'installazione si riferiscono al tasto Alt, usa il tasto Option. Per alcune combinazioni di tasti potresti aver bisogno di usare il tasto Option insieme al tasto Fn, tipo Option-Fn-"
-"F3 per cambiare al terminale virtuale tty3."
+"Il tasto Option sui sistemi Apple ?? equivalente al tasto "
+"Alt sul PC. Dove la documentazione o il software "
+"d'installazione si riferiscono al tasto Alt, usa il tasto "
+"Option. Per alcune combinazioni di tasti potresti aver bisogno "
+"di usare il tasto Option insieme al tasto Fn, tipo "
+"Option-Fn-F3 per cambiare al "
+"terminale virtuale tty3."
#: en/ArchSpecificPPC.xml:44(title)
msgid "PPC Installation Notes"
@@ -6115,7 +7125,11 @@
"addition, a bootable CD image appears in the images/ directory "
"of this disc. These images will behave differently according to your system "
"hardware:"
-msgstr "Il disco 1 d'installazione di Fedora Core ?? avviabile sull'hardware supportato. In pi??, un immagine di CD bootabile si pu?? trovare nella directory images/ di questo disco. Queste immagini si comporteranno differentemente a seconda dell'hardware:"
+msgstr ""
+"Il disco 1 d'installazione di Fedora Core ?? avviabile sull'hardware "
+"supportato. In pi??, un immagine di CD bootabile si pu?? trovare nella "
+"directory images/ di questo disco. Queste immagini si "
+"comporteranno differentemente a seconda dell'hardware:"
#: en/ArchSpecificPPC.xml:48(para)
msgid "Apple Macintosh"
@@ -6125,7 +7139,9 @@
msgid ""
"The bootloader should automatically boot the appropriate 32-bit or 64-bit "
"installer."
-msgstr "Il bootloader avvier?? automaticamente l'appropriato installer a 32-bit o 64-bit. "
+msgstr ""
+"Il bootloader avvier?? automaticamente l'appropriato installer a 32-bit o 64-"
+"bit. "
#: en/ArchSpecificPPC.xml:50(para)
msgid ""
@@ -6134,7 +7150,12 @@
"with more complex requirements can use the apmud package in "
"Fedora Extras. Following installation, you can install apmud "
"with the following command:"
-msgstr "Il pacchetto predefinito gnome-power-manager include il supporto al power management, incluso lo sleep e la gestione del livello di retroilluminazione. Gli utenti con requisiti pi?? complessi possono usare il pacchetto apmud in Fedora Extras. Seguendo l'installazione, puoi installare apmud con il seguente comando:"
+msgstr ""
+"Il pacchetto predefinito gnome-power-manager include il "
+"supporto al power management, incluso lo sleep e la gestione del livello di "
+"retroilluminazione. Gli utenti con requisiti pi?? complessi possono usare il "
+"pacchetto apmud in Fedora Extras. Seguendo l'installazione, "
+"puoi installare apmud con il seguente comando:"
#: en/ArchSpecificPPC.xml:51(screen)
#, no-wrap
@@ -6164,8 +7185,10 @@
"start the 32-bit installer. Otherwise, the 64-bit installer starts, which "
"does not work."
msgstr ""
-"Dopo aver usato OpenFirmware per avviare il CD, seleziona l'immagine boot linux32 al boot: prompt per avviare l'installer "
-"a 32-bit. Altrimenti, verr?? avviato l'installer a 64-bit, che non funzioner??."
+"Dopo aver usato OpenFirmware per avviare il CD, "
+"seleziona l'immagine boot linux32 al boot: prompt "
+"per avviare l'installer a 32-bit. Altrimenti, verr?? avviato l'installer a 64-"
+"bit, che non funzioner??."
#: en/ArchSpecificPPC.xml:62(para)
msgid "Genesi Pegasos II"
@@ -6195,8 +7218,10 @@
"this, set the boot-device and boot-file "
"environment variables appropriately."
msgstr ""
-"Avrai anche bisogno di configurare manualmente OpenFirmware sul Pegasos per rendere il sistema Fedora Core installato "
-"avviabile. Per farlo, dovrai impostare le variabili ambiente boot-device e boot-file appropriatamente."
+"Avrai anche bisogno di configurare manualmente OpenFirmware sul Pegasos per rendere il sistema Fedora Core installato "
+"avviabile. Per farlo, dovrai impostare le variabili ambiente boot-"
+"device e boot-file appropriatamente."
#: en/ArchSpecificPPC.xml:68(para)
msgid "Network booting"
@@ -6207,7 +7232,11 @@
"You can find combined images containing the installer kernel and ramdisk in "
"the images/netboot/ directory of the installation tree. These "
"are intended for network booting with TFTP, but can be used in many ways."
-msgstr "Ci sono immagini combinate contenenti il kernel d'installazione ed il ramdisk nella directory images/netboot/ del albero d'installazione. Queste sono intese per l'avvio via network con TFTP, ma possono essere usate in molti modi. "
+msgstr ""
+"Ci sono immagini combinate contenenti il kernel d'installazione ed il "
+"ramdisk nella directory images/netboot/ del albero "
+"d'installazione. Queste sono intese per l'avvio via network con TFTP, ma "
+"possono essere usate in molti modi. "
#: en/ArchSpecificPPC.xml:70(para)
msgid ""
@@ -6215,8 +7244,9 @@
"Macintosh. The Fedora Project encourages the use of yaboot over "
"the netboot images."
msgstr ""
-"yaboot supporta il TFTP booting per gli IBM eServer pSeries e Apple "
-"Macintosh. Il progetto Fedora Incoraggia l'uso di yaboot rispetto alle immagini netboot."
+"yaboot supporta il TFTP booting per gli IBM eServer pSeries e "
+"Apple Macintosh. Il progetto Fedora Incoraggia l'uso di yaboot "
+"rispetto alle immagini netboot."
#: en/ArchSpecific.xml:8(title)
msgid "Architecture Specific Notes"
From fedora-docs-commits at redhat.com Sun Mar 5 10:20:03 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 5 Mar 2006 05:20:03 -0500
Subject: install-guide/en fedora-install-guide-firstboot.xml,1.9,1.10
Message-ID: <200603051020.k25AK3Gt017210@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17192/en
Modified Files:
fedora-install-guide-firstboot.xml
Log Message:
- Trivial content fixes.
Index: fedora-install-guide-firstboot.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-firstboot.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-firstboot.xml 5 Mar 2006 03:02:05 -0000 1.9
+++ fedora-install-guide-firstboot.xml 5 Mar 2006 10:19:54 -0000 1.10
@@ -42,8 +42,8 @@
- Select Next to start the Setup
- Agent.
+ Select Forward to start the
+ Setup Agent.
Graphical Interface Required
@@ -163,16 +163,18 @@
The Services List
The services file on every system lists the
- port numbers and names of services that are registered with IANA
- (Internet Assigned Names Authority). &FED; systems hold this
- file in the directory /etc.
+ port numbers and names of services that are registered with the
+ Internet Assigned Names Authority (IANA). &FED; systems hold
+ this file in the directory /etc.
If a service uses more than one port number, enter each port. For
- example, to allow users on the system to access their mail with
- the IMAP protocol, add TCP port 143 (imap), and TCP port 993
- (imaps).
+ example, to allow users on the system to access their mail with an
+ IMAP service, add imap or port number
+ 143, and imaps, or
+ port number 993 for IMAP with SSL
+ encryption. Both IMAP ports use the TCP protocol.
From fedora-docs-commits at redhat.com Sun Mar 5 11:20:30 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 5 Mar 2006 06:20:30 -0500
Subject: install-guide/en fedora-install-guide-firstboot.xml, 1.10,
1.11 fedora-install-guide-packageselection.xml, 1.9, 1.10
Message-ID: <200603051120.k25BKUUF019574@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19554/en
Modified Files:
fedora-install-guide-firstboot.xml
fedora-install-guide-packageselection.xml
Log Message:
- Trivial content fixes.
Index: fedora-install-guide-firstboot.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-firstboot.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- fedora-install-guide-firstboot.xml 5 Mar 2006 10:19:54 -0000 1.10
+++ fedora-install-guide-firstboot.xml 5 Mar 2006 11:20:22 -0000 1.11
@@ -109,7 +109,7 @@
By default the firewall is enabled, with a simple set of rules
that allow connections to be made from your system to others, but
- permit only
+ permit only network browsing and
SSH (Secure SHell)firewall configuration
Index: fedora-install-guide-packageselection.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-packageselection.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-packageselection.xml 5 Mar 2006 03:02:05 -0000 1.9
+++ fedora-install-guide-packageselection.xml 5 Mar 2006 11:20:22 -0000 1.10
@@ -89,7 +89,7 @@
Core Network Services
- All Fedora Core installations run the following network services:
+ All Fedora Core installation include the following network services:
@@ -121,12 +121,17 @@
- The default installation also includes:
+ The default installation also provides:
+ network file transfer through HTTP (HyperText Transfer Protocol)
+
+
+
+
printing through CUPS (Common UNIX Printing System)
@@ -142,7 +147,7 @@
service to send reports and messages to the system administrator.
By default, the email, logging, and printing services do not
accept connections from other systems. &FED; installs the NFS
- sharing and VNC components without enabling those services.
+ sharing, HTTP, and VNC components without enabling those services.
From fedora-docs-commits at redhat.com Sun Mar 5 21:15:47 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 5 Mar 2006 16:15:47 -0500
Subject: install-guide/en fedora-install-guide-adminoptions.xml, 1.9,
1.10 fedora-install-guide-firstboot.xml, 1.11, 1.12
Message-ID: <200603052115.k25LFlB7017493@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17471/en
Modified Files:
fedora-install-guide-adminoptions.xml
fedora-install-guide-firstboot.xml
Log Message:
- A couple more small amendments.
Index: fedora-install-guide-adminoptions.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-adminoptions.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fedora-install-guide-adminoptions.xml 5 Mar 2006 03:02:05 -0000 1.9
+++ fedora-install-guide-adminoptions.xml 5 Mar 2006 21:15:31 -0000 1.10
@@ -398,14 +398,17 @@
Firewall Reconfiguration Required
- By default, the vncviewer utility
- listens on TCP port 5500. To update the &FED; firewall
- configuration to permit connections to this port from other
- systems, choose System
+ By default, vncviewer uses TCP port
+ 5500 when in listening mode. To permit connections to this
+ port from other systems, choose
+ SystemAdministrationSecurity
- Level and Firewall, enter
- 5500:tcp in the Other
- ports: field, and select OK.
+ Level and Firewall . Select
+ Other ports, and
+ Add. Enter 5500
+ in the Port(s) field, and specify
+ tcp as the
+ Protocol.
@@ -552,13 +555,15 @@
By default, the syslog service listens on UDP port 514. To
- update the &FED; firewall configuration to permit connections
- to this port from other systems, choose
- System
+ permit connections to this port from other systems, choose
+ SystemAdministrationSecurity
- Level and Firewall, enter
- 514:udp in the Other
- ports: field, and select OK.
+ Level and Firewall . Select
+ Other ports, and
+ Add. Enter 514
+ in the Port(s) field, and specify
+ udp as the
+ Protocol.
Index: fedora-install-guide-firstboot.xml
===================================================================
RCS file: /cvs/docs/install-guide/en/fedora-install-guide-firstboot.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- fedora-install-guide-firstboot.xml 5 Mar 2006 11:20:22 -0000 1.11
+++ fedora-install-guide-firstboot.xml 5 Mar 2006 21:15:31 -0000 1.12
@@ -109,7 +109,7 @@
By default the firewall is enabled, with a simple set of rules
that allow connections to be made from your system to others, but
- permit only network browsing and
+ permit only network browsing and
SSH (Secure SHell)firewall configuration
@@ -170,11 +170,13 @@
If a service uses more than one port number, enter each port. For
- example, to allow users on the system to access their mail with an
- IMAP service, add imap or port number
- 143, and imaps, or
- port number 993 for IMAP with SSL
- encryption. Both IMAP ports use the TCP protocol.
+ example, an IMAP service enables users to access their e-mail from
+ another system with either a standard connection to TCP port 143,
+ or with an encrypted connection to TCP port 993. To permit IMAP
+ connections to your system, add imap or
+ port number 143, and
+ imaps, or port number
+ 993, for IMAP with SSL encryption.
From fedora-docs-commits at redhat.com Sun Mar 5 22:05:47 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 5 Mar 2006 17:05:47 -0500
Subject: mirror-tutorial/en_US mirror-tutorial.xml,1.1,1.2
Message-ID: <200603052205.k25M5lmW019481@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/mirror-tutorial/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19463/en_US
Modified Files:
mirror-tutorial.xml
Log Message:
Update to en_US and use proper entity calls
Index: mirror-tutorial.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/en_US/mirror-tutorial.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mirror-tutorial.xml 4 Mar 2006 20:58:34 -0000 1.1
+++ mirror-tutorial.xml 5 Mar 2006 22:05:36 -0000 1.2
@@ -2,18 +2,14 @@
-%FEDORA-ENTITIES-EN;
+
+%FDP-ENTITIES;
+
+%DOC-ENTITIES;
-
-
-
-
-
-
]>
-
+
From fedora-docs-commits at redhat.com Sun Mar 5 22:08:12 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 5 Mar 2006 17:08:12 -0500
Subject: mirror-tutorial/en_US doc-entities.xml,NONE,1.1
Message-ID: <200603052208.k25M8C6M019551@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/mirror-tutorial/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19517/en_US
Added Files:
doc-entities.xml
Log Message:
Finish committal to en_US standard
--- NEW FILE doc-entities.xml ---
Local entities for Mirror TutorialDocument namemirror-tutorialVersion number1.0Date of last revision2006-02-06Document ID- ()Local version of Fedora Core for this document4
From fedora-docs-commits at redhat.com Sun Mar 5 22:08:05 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sun, 5 Mar 2006 17:08:05 -0500
Subject: mirror-tutorial Makefile,1.8,1.9 rpm-info.xml,1.2,1.3
Message-ID: <200603052208.k25M8Z3e019555@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/mirror-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19517
Modified Files:
Makefile rpm-info.xml
Log Message:
Finish committal to en_US standard
Index: Makefile
===================================================================
RCS file: /cvs/docs/mirror-tutorial/Makefile,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Makefile 4 Mar 2006 20:58:23 -0000 1.8
+++ Makefile 5 Mar 2006 22:07:37 -0000 1.9
@@ -9,6 +9,7 @@
DOCBASE = mirror-tutorial
PRI_LANG = en_US
OTHERS =
+DOC_ENTITIES = doc-entities
########################################################################
# List each XML file of your document in the template below. Append the
# path to each file to the "XMLFILES-${1}" string. Use a backslash if you
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/mirror-tutorial/rpm-info.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-info.xml 18 Feb 2006 18:12:09 -0000 1.2
+++ rpm-info.xml 5 Mar 2006 22:07:37 -0000 1.3
@@ -17,7 +17,7 @@
Paul W. Frields
-
+ Mirror TutorialInstalling and maintaining a local Fedora mirror
From fedora-docs-commits at redhat.com Sun Mar 5 22:52:35 2006
From: fedora-docs-commits at redhat.com (Hugo Cisneiros (eitch))
Date: Sun, 5 Mar 2006 17:52:35 -0500
Subject: release-notes/po pt_BR.po,1.2,1.3
Message-ID: <200603052252.k25MqZ4J019715@cvs-int.fedora.redhat.com>
Author: eitch
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19692
Modified Files:
pt_BR.po
Log Message:
revision done. final version.
Index: pt_BR.po
===================================================================
RCS file: /cvs/docs/release-notes/po/pt_BR.po,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- pt_BR.po 4 Mar 2006 06:31:35 -0000 1.2
+++ pt_BR.po 5 Mar 2006 22:52:27 -0000 1.3
@@ -4,7 +4,7 @@
msgstr ""
"Project-Id-Version: pt_BR\n"
"POT-Creation-Date: 2006-03-01 17:42-0300\n"
-"PO-Revision-Date: 2006-03-04 02:59-0300\n"
+"PO-Revision-Date: 2006-03-05 19:38-0300\n"
"Last-Translator: Hugo Cisneiros \n"
"Language-Team: Brazilian Portuguese \n"
"MIME-Version: 1.0\n"
@@ -22,7 +22,7 @@
#: en/Xorg.xml:9(para)
msgid "This section contains information related to the X Window System implementation provided with Fedora."
-msgstr "Esta se????o cont??m informa????es relacionadas a implementa????o do X Window System (Sistema de Janelas X), fornecido com o Fedora."
+msgstr "Esta se????o cont??m informa????es relacionadas ?? implementa????o do X Window System (Sistema de Janelas X), fornecido com o Fedora."
#: en/Xorg.xml:11(title)
msgid "xorg-x11"
@@ -30,11 +30,11 @@
#: en/Xorg.xml:12(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 http://xorg.freedesktop.org/wiki/."
-msgstr "O X.org X11 ?? uma implementa????o de c??digo aberto do X Window System (Sistema de Janelas X). Ele fornece as funcionalidades de baixo n??vel b??sicas para que as completas interfaces gr??ficas de usu??rios (GUI) como por exemplo o GNOME e KDE sejam feitas. Para mais informa????es sobre o X.org, veja em http://xorg.freedesktop.org/wiki/."
+msgstr "O X.org X11 ?? uma implementa????o de c??digo aberto do X Window System (Sistema de Janelas X). Ele fornece as funcionalidades de baixo n??vel b??sicas para que as interfaces gr??ficas de usu??rios (GUI) completas como por exemplo o GNOME e KDE sejam feitas. Para mais informa????es sobre o X.org, visite http://xorg.freedesktop.org/wiki/."
#: en/Xorg.xml:13(para)
msgid "You may use Applications > System Settings > Display or system-config-display to configure the settings. The configuration file for X.org is located in /etc/X11/xorg.conf."
-msgstr "Para configurar as op????es, voc?? pode entrar em Aplica????es > Configura????es de Sistema > Tela ou use o comando system-config-display. O arquivo de configura????o do X.org est?? localizado em /etc/X11/xorg.conf."
+msgstr "Para configurar as op????es, voc?? pode entrar em Aplica????es > Configura????es de Sistema > Tela ou usar o comando system-config-display. O arquivo de configura????o do X.org est?? localizado em /etc/X11/xorg.conf."
#: 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 http://fedoraproject.org/wiki/Xorg/Modularization."
@@ -74,7 +74,7 @@
#: en/Xorg.xml:40(para)
msgid "Everything is now installed directly into /usr instead of /usr/X11R6. All software that hard codes paths to anything in /usr/X11R6 must now be changed, preferably to dynamically detect the proper location of the object. Developers are strongly advised against hard-coding the new X11R7 default paths."
-msgstr "Agora tudo ?? instalado diretamente em /usr ao inv??s de /usr/X11R6. Todos os programas que escrevem caminhos diretamente no c??digo para /usr/X11R6 devem ser mudados, de prefer??ncia para detectar din??micamente a localiza????o correta do objeto. Desenvolvedores s??o fortemente recomendados a n??o escrever os caminhos diretamente no c??digo para os novo padr??es do X11R7."
+msgstr "Agora tudo ?? instalado diretamente em /usr ao inv??s de /usr/X11R6. Todos os programas que escrevem caminhos diretamente no c??digo para /usr/X11R6 devem ser mudados, de prefer??ncia para detectar dinamicamente a localiza????o correta do objeto. Desenvolvedores s??o fortemente recomendados a n??o escrever os caminhos diretamente no c??digo para os novo padr??es do X11R7."
#: en/Xorg.xml:45(para)
msgid "Every library has its own private source RPM package, which creates a runtime binary subpackage and a -devel subpackage."
@@ -102,7 +102,7 @@
#: en/Xorg.xml:60(para)
msgid "The imake utility is no longer used to build the X Window System, and is now officially deprecated. X11R7 includes imake, xmkmf, and other build utilities previously supplied by the X Window System. X.Org highly recommends, however, that people migrate from imake to use GNU autotools and pkg-config. Support for imake may be removed in a future X Window System release, so developers are strongly encouraged to transition away from it, and not use it for any new software projects."
-msgstr "O utilit??rio imake n??o ?? mais usado na constru????o do X Window System, e agora est?? oficialmente fora-de-uso. O X11R7 inclui o imake, xmkmf, e outros utilit??rios de compila????o pr??viamente fornecidos pelo X Window System. Entretanto, o X.org recomenda altamente que as pessoas migrem do imake para usar as ferramentas GNU autotools e pkg-config. O suporte ao imake pode ser removido em uma futura vers??o do X Window System, ent??o os desenvolvedores s??o fortemente encorajados a mudar e n??o us??-lo em nenhum outro novo projeto de programa."
+msgstr "O utilit??rio imake n??o ?? mais usado na constru????o do X Window System e agora est?? oficialmente fora-de-uso. O X11R7 inclui o imake, xmkmf e outros utilit??rios de compila????o previamente fornecidos pelo X Window System. Entretanto, o X.org recomenda altamente que as pessoas migrem do imake para usar as ferramentas GNU autotools e pkg-config. O suporte ao imake pode ser removido em uma futura vers??o do X Window System, ent??o os desenvolvedores s??o fortemente encorajados a mudar e n??o us??-lo em nenhum outro novo projeto de programa."
#: en/Xorg.xml:63(title)
msgid "The Systemwide app-defaults/ Directory"
@@ -114,11 +114,11 @@
#: en/Xorg.xml:67(title)
msgid "Correct Package Dependencies"
-msgstr "Corretas Depend??ncias de Pacotes"
+msgstr "Depend??ncias de Pacotes Corretas"
#: en/Xorg.xml:68(para)
msgid "Any software package that previously used BuildRequires: (XFree86-devel|xorg-x11-devel) to satisfy build dependencies must now individually list each library dependency. The preferred and recommended method is to use virtual build dependencies instead of hard coding the library package names of the xorg implementation. This means you should use BuildRequires: libXft-devel instead of BuildRequires: xorg-x11-Xft-devel. If your software truly does depend on the X.Org X11 implementation of a specific library, and there is no other clean or safe way to state the dependency, then use the xorg-x11-devel form. If you use the virtual provides/requires mechanism, you will avoid inconvenience if the libraries move to another location in the future."
-msgstr "Qualquer programa que anteriormente usou BuildRequires: (XFree86-devel|xorg-x11-devel) para satisfazer as depend??ncias de compila????o agora devem listar cada depend??ncia de biblioteca individualmente. O m??todo preferido e recomendado ?? o uso de depend??ncias de compila????o virtuais ao inv??s de escrever os nomes de pacotes de bibliotecas da implementa????o xorg diretamente no c??digo. Isso significa que voc?? deve usar BuildRequires: libXft-devel ao inv??s de BuildRequires: xorg-x11-Xft-devel. Se o seu programa depende muito de uma implementa????o X.Org X11 de uma biblioteca espec??fica, e n??o h?? outros meios limpos e seguros de satisfazer a depend??ncia, ent??o use a forma xorg-x11-devel. Se voc?? usar mecanismos virtuais, voc?? ir?? evitar incoveni??ncias futuras caso as bibliotecas mudem de localiza????o."
+msgstr "Qualquer programa que anteriormente usou BuildRequires: (XFree86-devel|xorg-x11-devel) para satisfazer as depend??ncias de compila????o agora devem listar cada depend??ncia de biblioteca individualmente. O m??todo preferido e recomendado ?? o uso de depend??ncias de compila????o virtuais ao inv??s de escrever os nomes de pacotes de bibliotecas da implementa????o xorg diretamente no c??digo. Isso significa que voc?? deve usar BuildRequires: libXft-devel ao inv??s de BuildRequires: xorg-x11-Xft-devel. Se o seu programa depende muito de uma implementa????o X.Org X11 de uma biblioteca espec??fica e n??o h?? outros meios limpos e seguros de satisfazer a depend??ncia, ent??o use a forma xorg-x11-devel. Se voc?? usar mecanismos virtuais, voc?? ir?? evitar incoveni??ncias futuras caso as bibliotecas mudem de localiza????o."
#: en/Xorg.xml:74(title)
msgid "xft-config"
@@ -126,7 +126,7 @@
#: en/Xorg.xml:75(para)
msgid "Modular X now uses GNU autotools and pkg-config for its buildsystem configuration and execution. The xft-config utility has been deprecated for some time, and pkgconfig*.pc files have been provided for most of this time. Applications that previously used xft-config to obtain the Cflags or libs build options must now be updated to use pkg-config."
-msgstr "O X modular agora usa as ferramentas GNU autotools e pkg-config para configura????o e execu????o do seu sistema de compila????o. O utilit??rio xft-config est?? sem uso h?? algum tempo, e os arquivos *.pc do pkgconfig est??o sendo fornecidos por um bom tempo. Aplica????es que antes usavam o xft-config para obter as op????es de constru????o Cflags ou libs agora devem ser atualizadas para usar o pkg-config."
+msgstr "O X modular agora usa as ferramentas GNU autotools e pkg-config para configura????o e execu????o do seu sistema de compila????o. O utilit??rio xft-config est?? sem uso h?? algum tempo e os arquivos *.pc do pkgconfig est??o sendo fornecidos por um bom tempo. Aplica????es que antes usavam o xft-config para obter as op????es de constru????o Cflags ou libs agora devem ser atualizadas para usar o pkg-config."
#: en/Welcome.xml:8(title)
msgid "Welcome to Fedora Core"
@@ -142,7 +142,7 @@
#: en/Welcome.xml:15(para)
msgid "You can help the Fedora Project community continue to improve Fedora if you file bug reports and enhancement requests. Refer to http://fedoraproject.org/wiki/BugsAndFeatureRequests for more information about bugs. Thank you for your participation."
-msgstr "Voc?? pode ajudar a comunidade do Projeto Fedora a continuar aperfei??oando o Fedora se voc?? relatar bugs ou pedir por aprimoramentos. Veja em http://fedoraproject.org/wiki/BugsAndFeatureRequests para mais informa????es sobre bugs. Obrigado por sua participa????o."
+msgstr "Voc?? pode ajudar a comunidade do Projeto Fedora a continuar aperfei??oando o Fedora ao relatar bugs ou pedir por aprimoramentos. Visite http://fedoraproject.org/wiki/BugsAndFeatureRequests para mais informa????es sobre bugs. Obrigado por sua participa????o. "
#: en/Welcome.xml:16(para)
msgid "To find out more general information about Fedora, refer to the following Web pages:"
@@ -174,7 +174,7 @@
#: en/WebServers.xml:9(para)
msgid "This section contains information on Web-related applications."
-msgstr "Esta se????o cont??m informa????es sobre aplica????es relacionadas a Web."
+msgstr "Esta se????o cont??m informa????es sobre aplica????es relacionadas ?? Web."
#: en/WebServers.xml:11(title)
msgid "httpd"
@@ -258,7 +258,7 @@
#: en/WebServers.xml:67(para)
msgid "date, hash, and Reflection (built-in with the php package)"
-msgstr "date, hash, e Reflection (acoplados ao pacote php)"
+msgstr "date, hash e Reflection (acoplados ao pacote php)"
#: en/WebServers.xml:71(para)
msgid "pdo and pdo_psqlite (in the php-pdo package)"
@@ -326,7 +326,7 @@
#: en/Virtualization.xml:9(para)
msgid "Virtualization in Fedora Core is based on Xen. Xen 3.0 is integrated within Fedora Core 5 in the installer. Refer to http://fedoraproject.org/wiki/Tools/Xen for more information about Xen."
-msgstr "A Virtualiza????o no Fedora Core ?? baseada no Xen. O Xen 3.0 est?? integrado ao instalador do Fedora Core 5. Veja em http://fedoraproject.org/wiki/Tools/Xen para mais informa????es sobre o Xen."
+msgstr "A Virtualiza????o no Fedora Core ?? baseada no Xen. O Xen 3.0 est?? integrado ao instalador do Fedora Core 5. Visite http://fedoraproject.org/wiki/Tools/Xen para mais informa????es sobre o Xen."
#: en/Virtualization.xml:12(title)
msgid "No PowerPC Support"
@@ -392,7 +392,7 @@
#: en/ServerTools.xml:18(para)
msgid "The system-config-printer application supports Kerberos authentication when adding a new SMB printer. To add the printer, the user must possess a valid Kerberos ticket and launch the printer configuration tool. Select System>Administration>Printing from the main menu, or use the following command:"
-msgstr "A aplica????o system-config-printer suporta autentica????o Kerberos na adi????o de uma nova impressora SMB. Para adicionar a impressora, o usu??rio precisa possuir um ticket Kerberos v??lido e ent??o executar a ferramenta de configura????o de impressoras. Selecione Sistema>Administra????o>kImpress??o a partir do menu principal, ou use o seguinte comando:"
+msgstr "A aplica????o system-config-printer suporta autentica????o Kerberos na adi????o de uma nova impressora SMB. Para adicionar a impressora, o usu??rio precisa possuir um ticket Kerberos v??lido e ent??o executar a ferramenta de configura????o de impressoras. Selecione Sistema>Administra????o>Impress??o a partir do menu principal, ou use o seguinte comando:"
#: en/ServerTools.xml:19(screen)
#, no-wrap
@@ -470,11 +470,11 @@
#: en/SecuritySELinux.xml:38(para)
msgid "MLS is a specific Mandatory Access Control (MAC) scheme that labels processes and objects with special security levels. For example, an object such as a document file can have the security level of { Secret, ProjectMeta }, where Secret is the sensitivity level, and ProjectMeta is the category. For more information about MLS, refer to http://james-morris.livejournal.com/5020.html."
-msgstr "O MLS ?? um esquema de Controle de Acesso Obrigat??rio (Mandatory Access Control - MAC) que rotula processos e objetos com n??veis de seguran??a especiais. Por exemplo, um objeto como um arquivo de documento pode ter um n??vel de seguran??a chamado { Secret, ProjectMeta }, onde Secret ?? o n??vel de sensibilidade. e ProjectMeta ?? a categoria. Para mais informa????es sobre o MLS, veja em http://james-morris.livejournal.com/5020.html."
+msgstr "O MLS ?? um esquema de Controle de Acesso Obrigat??rio (Mandatory Access Control - MAC) que rotula processos e objetos com n??veis de seguran??a especiais. Por exemplo, um objeto como um arquivo de documento pode ter um n??vel de seguran??a chamado { Secret, ProjectMeta }, onde Secret ?? o n??vel de sensibilidade. e ProjectMeta ?? a categoria. Para mais informa????es sobre o MLS, visite http://james-morris.livejournal.com/5020.html."
#: en/SecuritySELinux.xml:40(ulink)
msgid "CategorySecurity"
-msgstr "Seguran??a por Categoria"
+msgstr "CategorySecurity"
#: en/Security.xml:8(title)
msgid "Security"
@@ -498,7 +498,7 @@
#: en/Security.xml:15(para)
msgid "Pam_stack is deprecated in this release. Linux-PAM 0.78 and later contains the include directive which obsoletes the pam_stack module. pam_stack module usage is logged with a deprecation warning. It might be removed in a future release. It must not be used in individual service configurations anymore. All packages in Fedora Core using PAM were modified so they do not use it."
-msgstr "O Pam_stack est?? fora de uso nesta vers??o. A vers??o 0.78 do Linux-PAM em diante cont??m a diretiva include que torna obsoleto o m??dulo pam_stack. O uso do m??dulo pam_stack ?? logado com um aviso. Ele pode ser removido em uma futura vers??o. N??o ?? mais para ser usado em configura????es de servi??os individuais. Todos os pacotes no Fedora Core utilizando o PAM foram modificados para que n??o usem."
+msgstr "O Pam_stack est?? fora de uso nesta vers??o. A vers??o 0.78 do Linux-PAM em diante cont??m a diretiva include que torna obsoleto o m??dulo pam_stack. O uso do m??dulo pam_stack ?? logado com um aviso. Ele pode ser removido em uma futura vers??o. N??o ?? mais para ser usado em configura????es de servi??os individuais. Todos os pacotes que utilizam o PAM no Fedora Core foram modificados para evitar seu uso."
#: en/Security.xml:18(title)
msgid "Upgrading and PAM Stacks"
@@ -515,7 +515,7 @@
#: en/Security.xml:29(para)
msgid "The following example shows the /etc/pam.d/login configuration file in its original form using pam_stack, and then revised with the include directive."
-msgstr "O seguinte exemplo mostra o arquivo de configura????o /etc/pam.d/login em sua forma original usando o pam_stack, e ent??o a vers??o revisada com a diretiva include."
+msgstr "O seguinte exemplo mostra o arquivo de configura????o /etc/pam.d/login em sua forma original usando o pam_stack e ent??o a vers??o revisada com a diretiva include."
#: en/Security.xml:30(screen)
#, no-wrap
@@ -533,15 +533,15 @@
#: en/Security.xml:69(para)
msgid "All of the software in Fedora Core and Extras software repository for this release is compiled using a security feature called fstack-protector. fstack-protector places a canary value on the stack of functions containing a local character array. Before returning from a protected function, the canary value is verified. If there was a buffer overflow, the canary will no longer match the expected value, aborting the program. The canary value is random each time the application is started, making remote exploitation very difficult. The fstack-protector feature does not protect against heap-based buffer overflows."
-msgstr "Todos os programas dos reposit??rios do Fedora Core e Extras nesta vers??o s??o compiladas com uma funcionalidade de seguran??a chamada fstack-protector. O fstack-protector coloca um valor canary na pilha de fun????es contendo uma array de caracteres locais. Antes de retornar de uma fun????o protegida, o valor canary ?? verificado. Se houver um buffer overflow, o valor canary n??o corresponder?? ao valor esperado, e ent??o o programa ?? cancelado. O valor canary ?? aleat??ro toda vez que uma aplica????o ?? iniciada, tornando a explora????o remote muito dif??cil. A funcionalidade fstack-protector n??o protege contra buffer overflows baseados em heap (??rea especial da mem??ria)."
+msgstr "Todos os programas dos reposit??rios do Fedora Core e Extras nesta vers??o s??o compiladas com uma funcionalidade de seguran??a chamada fstack-protector. O fstack-protector coloca um valor canary na pilha de fun????es contendo uma array de caracteres locais. Antes de retornar de uma fun????o protegida, o valor canary ?? verificado. Se houver um buffer overflow, o valor canary n??o corresponder?? ao valor esperado e ent??o o programa ?? cancelado. O valor canary ?? aleat??ro toda vez que uma aplica????o ?? iniciada, tornando a explora????o remota muito dif??cil. A funcionalidade fstack-protector n??o protege contra buffer overflows baseados em heap (??rea especial da mem??ria)."
#: en/Security.xml:70(para)
msgid "This is a security feature written by Red Hat developers, implementing the IBM ProPolice/SSP feature. For more information about ProPolice/SSP, refer to http://www.research.ibm.com/trl/projects/security/ssp/. This feature is available as part of the GCC 4.1 compiler used in Fedora Core 5."
-msgstr "Esta ?? uma funcionalidade de seguran??a escrita pelos desenvolvedores da Red Hat, implementando a funcionalidade IBM-ProPolice/SSP. Para mais informa????es sobre ProPolice/SSP, veja em http://www.research.ibm.com/trl/projects/security/ssp/. Essa funcionalidade est?? dispon??vel como parte do compilador GCC 4.1 usado no Fedora Core 5."
+msgstr "Esta ?? uma funcionalidade de seguran??a escrita pelos desenvolvedores da Red Hat, implementando a funcionalidade IBM-ProPolice/SSP. Para mais informa????es sobre ProPolice/SSP, visite http://www.research.ibm.com/trl/projects/security/ssp/. Essa funcionalidade est?? dispon??vel como parte do compilador GCC 4.1 usado no Fedora Core 5."
#: en/Security.xml:71(para)
msgid "The FORTIFY_SOURCE security feature for gcc and glibc introduced in Fedora Core 4 remains available. For more information about security features in Fedora, refer to http://fedoraproject.org/wiki/Security/Features."
-msgstr "A funcionalidade de seguran??a FORTIFY_SOURCE para o gcc e glibc introduzida no Fedora Core 4 continua dispon??vel. Para mais informa????es sobre as funcionalidades de seguran??a no Fedora, veja em http://fedoraproject.org/wiki/Security/Features."
+msgstr "A funcionalidade de seguran??a FORTIFY_SOURCE para o gcc e glibc introduzida no Fedora Core 4 continua dispon??vel. Para mais informa????es sobre as funcionalidades de seguran??a no Fedora, visite http://fedoraproject.org/wiki/Security/Features."
#: en/Samba.xml:8(title)
msgid "Samba (Windows Compatibility)"
@@ -549,7 +549,7 @@
#: en/Samba.xml:9(para)
msgid "Fedora can now browse Windows shares, a feature known as SMB browsing. In releases prior to Fedora Core 5, the firewall prevented the proper function of SMB browsing. With the addition of the ip_conntrack_netbios_ns kernel module to the 2.6.14 kernel, and corresponding enhancements to system-config-securitylevel, the firewall now properly handles SMB broadcasts and permits network browsing."
-msgstr "O Fedora agora pode navegar em compartilhamentos Windows, uma funcionalidade conhecida como Navega????o SMB. Em vers??es anteriores ?? Fedora Core 5, o firewall impedia o funcionamento da navega????o SMB. Com a adi????o do m??dulo de kernel ip_conntrack_netbios_ns na vers??o 2.6.14 do kernel, e com o aprimoramento correspondente no system-config-securitylevel, o firewall agora permite broadcasts SMB e navega????o na rede."
+msgstr "O Fedora agora pode navegar em compartilhamentos Windows, uma funcionalidade conhecida como Navega????o SMB. Em vers??es anteriores ?? Fedora Core 5, o firewall impedia o funcionamento da navega????o SMB. Com a adi????o do m??dulo de kernel ip_conntrack_netbios_ns na vers??o 2.6.14 do kernel e com o aprimoramento correspondente no system-config-securitylevel, o firewall agora permite broadcasts SMB e navega????o na rede."
#: en/ProjectOverview.xml:8(title)
msgid "Fedora Project - Freedom to the Core"
@@ -557,7 +557,7 @@
#: en/ProjectOverview.xml:9(para)
msgid "The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from open source software. Development is done in a public forum. The project produces time-based releases of Fedora Core approximately 2-3 times a year, with a public release schedule available at http://fedora.redhat.com/About/schedule/. The Red Hat engineering team continues to participate in building Fedora Core and invites and encourages more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community."
-msgstr "O objetivo do Projeto Fedora ?? trabalhar com a comunidade Linux para construir um sistema operacional completo e para uso geral exclusivamente com softwares de c??digo aberto. O desenvolvimento ?? feito em um f??rum p??blico. O projeto produz vers??es em tempos fixos de aproximadamente duas a tr??s vezes por ano, com um calend??rio de lan??amentos p??blico dispon??vel em http://fedora.redhat.com/About/schedule/. O time de engenheiros Red Hat continua a participar na constru????o do Fedora Core, convida e encoraja mais participantes de fora a participar tamb??m, mais do que era poss??vel no passado. Usando este processo mais aberto, esperamos fornecer um sistema operacional mais em linha com os ideais do software livre, e mais apegado a comunidade do c??digo aberto."
+msgstr "O objetivo do Projeto Fedora ?? trabalhar com a comunidade Linux para construir um sistema operacional completo e para uso geral exclusivamente com softwares de c??digo aberto. O desenvolvimento ?? feito em um f??rum p??blico. O projeto produz vers??es em tempos fixos de aproximadamente duas a tr??s vezes por ano, com um calend??rio de lan??amentos p??blico dispon??vel em http://fedora.redhat.com/About/schedule/. O time de engenheiros Red Hat continua a participar na constru????o do Fedora Core, convida e encoraja mais participantes de fora a participar tamb??m, mais do que era poss??vel no passado. Usando este processo mais aberto, esperamos fornecer um sistema operacional mais em linha com os ideais do software livre e mais apegado a comunidade do c??digo aberto."
#: en/ProjectOverview.xml:10(para)
msgid "For more information, refer to the Fedora Project website:"
@@ -569,7 +569,7 @@
#: en/ProjectOverview.xml:14(para)
msgid "The Fedora Project is driven by the individuals that contribute to it. As a tester, developer, documenter or translator, you can make a difference. See http://fedoraproject.org/wiki/HelpWanted for details."
-msgstr "O Projeto Fedora ?? dirigido por individuais que contribuem para ele. Como algu??m que faz testes, como um desenvolvedor, documentador, ou tradutor, voc?? pode fazer a diferen??a. Veja em http://fedoraproject.org/wiki/HelpWanted para detalhes sobre isso."
+msgstr "O Projeto Fedora ?? dirigido por indiv??duos que contribuem para ele. Como algu??m que faz testes, como um desenvolvedor, documentador, ou tradutor, voc?? pode fazer a diferen??a. Visite http://fedoraproject.org/wiki/HelpWanted para detalhes sobre isso."
#: en/ProjectOverview.xml:15(para)
msgid "This page explains the channels of communication for Fedora users and contributors:"
@@ -621,7 +621,7 @@
#: en/ProjectOverview.xml:44(para)
msgid "Fedora Project participants frequent the #fedora channel on the Freenode network, whilst Fedora Project developers may often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well; this information may be found on the webpage for the project, and at http://fedoraproject.org/wiki/Communicate."
-msgstr "Os participantes do Projeto Fedora freq??entam o canal #fedora na rede Freenode, enquanto os desenvolvedores se encontram no canal #fedora-devel. Alguns dos projetos maiores tamb??m podem ter seus pr??prios canais, e esta informa????o pode ser encontrada na p??gina de cada projeto, ou em http://fedoraproject.org/wiki/Communicate."
+msgstr "Os participantes do Projeto Fedora freq??entam o canal #fedora na rede Freenode, enquanto os desenvolvedores se encontram no canal #fedora-devel. Alguns dos projetos maiores tamb??m podem ter seus pr??prios canais e esta informa????o pode ser encontrada na p??gina de cada projeto, ou em http://fedoraproject.org/wiki/Communicate."
#: en/ProjectOverview.xml:45(para)
msgid "In order to talk on the #fedora channel, you will need to register your nickname, or nick. Instructions are given when you /join the channel."
@@ -653,11 +653,11 @@
#: en/PackageNotes.xml:12(para)
msgid "The hotplug and device handling subsystem has undergone significant changes in Fedora Core 5. The udev method now handles all module loading, both on system boot and for hotplugged devices. The hotplug package has been removed, as it is no longer needed."
-msgstr "O subsistema que cuida dos dispositivos e do hotplug sofreu mudan??as significativas no Fedora Core 5. O m??todo do udev agora cuida de todo o carregamento de m??dulos, tanto no boot do sistema, como nos dispositivos do hotplug. O pacote hotplug foi removido, pois n??o ?? mais preciso."
+msgstr "O subsistema que cuida dos dispositivos e do hotplug sofreu mudan??as significativas no Fedora Core 5. O m??todo do udev agora cuida de todo o carregamento de m??dulos, tanto na inicializa????o do sistema, como nos dispositivos do hotplug. O pacote hotplug foi removido, pois n??o ?? mais necess??rio."
#: en/PackageNotes.xml:13(para)
msgid "Support for hotplug helpers via the /etc/hotplug, /etc/hotplug.d, and /etc/dev.d directories is deprecated, and may be removed in a future Fedora Core release. These helpers should be converted to udev rules. Please see http://www.reactivated.net/writing_udev_rules.html for examples."
-msgstr "O suporte para os auxiliares do hotplug nos diret??rios /etc/hotplug, /etc/hotplug.d e /etc/dev.d agora est??o fora de uso e podem ser removidos em uma futura vers??o do Fedora Core. Estes auxiliares devem ser convertidos para regras do udev. Por favor veja em http://www.reactivated.net/writing_udev_rules.html para alguns exemplos."
+msgstr "O suporte para os auxiliares do hotplug nos diret??rios /etc/hotplug, /etc/hotplug.d e /etc/dev.d agora est??o fora de uso e podem ser removidos em uma futura vers??o do Fedora Core. Estes auxiliares devem ser convertidos para regras do udev. Por favor visite http://www.reactivated.net/writing_udev_rules.html para alguns exemplos."
#: en/PackageNotes.xml:16(title)
msgid "Systemwide Search Changes"
@@ -689,7 +689,7 @@
#: en/PackageNotes.xml:35(para)
msgid "The updatedb command is not compatible, and custom scripts that use updatedb may have to be updated."
-msgstr "O comando updatedbn??o ?? compat??vel, e scripts personalizados que usam o updatedb podem precisar ser atualizados."
+msgstr "O comando updatedbn??o ?? compat??vel e scripts personalizados que usam o updatedb podem precisar de atualiza????o."
#: en/PackageNotes.xml:40(title)
msgid "Mouse Configuration Utility Removed"
@@ -709,7 +709,7 @@
#: en/PackageNotes.xml:48(para)
msgid "Refer to http://fedoraproject.org/wiki/Tools/NetworkManager for more information on how to install and enable NetworkManager."
-msgstr "Veja em http://fedoraproject.org/wiki/Tools/NetworkManager para mais informa????es em como instalar e habilitar o NetworkManager."
+msgstr "Visite http://fedoraproject.org/wiki/Tools/NetworkManager para mais informa????es em como instalar e habilitar o NetworkManager."
#: en/PackageNotes.xml:52(title)
msgid "Dovecot"
@@ -717,7 +717,7 @@
#: en/PackageNotes.xml:53(para)
msgid "Fedora Core 5 includes a new version of the dovecot IMAP server software, which has has many changes in its configuration file. These changes are of particular importance to users upgrading from a previous release. Refer to http://wiki.dovecot.org/UpgradingDovecot for more information on the changes."
-msgstr "O Fedora Core 5 inclui a nova vers??o do programa de servidor IMAP dovecot, que traz muitas mudan??as em seu arquivo de configura????o. Estas mudan??as s??o de import??ncia para usu??rios atualizando de uma vers??o anterior. Veja em http://wiki.dovecot.org/UpgradingDovecot para mais informa????es sobre as mudan??as."
+msgstr "O Fedora Core 5 inclui a nova vers??o do programa de servidor IMAP dovecot, que traz muitas mudan??as em seu arquivo de configura????o. Estas mudan??as s??o importantes para usu??rios atualizando de uma vers??o anterior. Visite http://wiki.dovecot.org/UpgradingDovecot para mais informa????es sobre as mudan??as."
#: en/PackageNotes.xml:56(title)
msgid "Kudzu"
@@ -725,7 +725,7 @@
#: en/PackageNotes.xml:57(para)
msgid "The kudzu utility, libkudzu library, and /etc/sysconfig/hwconf hardware listing are all deprecated, and will be removed in a future release of Fedora Core. Applications which need to probe for available hardware should be ported to use the HAL library. More information on HAL is available at http://freedesktop.org/wiki/Software/hal."
-msgstr "O utlit??rio kudzu, a biblioteca libkudzu e a listagem de hardware /etc/sysconfig/hwconf agora est??o todos fora de uso, e ser??o removidos em uma vers??o futura do Fedora Core. Aplica????es que precisem identificar hardwares dispon??veis devem ser portados para utilizar a biblioteca HAL. Mais informa????es sobre o HAL est??o dispon??veis em http://freedesktop.org/wiki/Software/hal."
+msgstr "O utlit??rio kudzu, a biblioteca libkudzu e a listagem de hardware /etc/sysconfig/hwconf agora est??o todos fora de uso e ser??o removidos em uma vers??o futura do Fedora Core. Aplica????es que precisem identificar hardwares dispon??veis devem ser portadas para utilizar a biblioteca HAL. Mais informa????es sobre o HAL est??o dispon??veis em http://freedesktop.org/wiki/Software/hal."
#: en/PackageNotes.xml:60(title)
msgid "No automatic fstab editing for removable media"
@@ -733,7 +733,7 @@
#: en/PackageNotes.xml:61(para)
msgid "The fstab-sync facility has been removed. In Fedora Core , the fstab-sync program is removed in favor of desktop specific solutions for mounting removable media. Entries for hotplug devices or inserted media are no longer automatically added to the /etc/fstab file. Command-line users may migrate to gnome-mount, which provides similar functionality."
-msgstr "O utlit??rio fstab-sync foi removido. No Fedora Core, o programa fstab-sync foi removido em favor das solu????es espec??ficas dos ambientes desktop para montagem de m??dias remov??veis. Entradas para dispositivos hotplug ou m??dia inserida n??o s??o mais adicionadas automaticamente no arquivo /etc/fstab. Os usu??rios d elinha de comando podem migrar para o gnome-mount, que fornece uma funcionalidade semelhante."
+msgstr "O utlit??rio fstab-sync foi removido. No Fedora Core, o programa fstab-sync foi removido em favor das solu????es espec??ficas dos ambientes desktop para montagem de m??dias remov??veis. Entradas para dispositivos hotplug ou m??dia inserida n??o s??o mais adicionadas automaticamente no arquivo /etc/fstab. Os usu??rios de linha de comando podem migrar para o gnome-mount, que fornece uma funcionalidade semelhante."
#: en/PackageNotes.xml:64(title)
msgid "GnuCash"
@@ -741,7 +741,7 @@
#: en/PackageNotes.xml:65(para)
msgid "The PostgreSQL backend for GnuCash has been removed, as it is unmaintained upstream, does not support the full set of GnuCash features, and can lead to crashes. Users who use the PostgreSQL backend should load their data and save it as an XML file before upgrading GnuCash."
-msgstr "O backend de PostgreSQL para o GnuCash foi removido, pois ele n??o ?? mais mantido no projeto principal, e n??o suporta todas as funcionalidades do GnuCash, podendo levar o programa a travamentos. Usu??rios que usam o backend de PostgreSQL devem carregar e salvar seus dados em um arquivo XML antes de atualizar o GnuCash."
+msgstr "O backend de PostgreSQL para o GnuCash foi removido, pois ele n??o ?? mais mantido no projeto principal e n??o suporta todas as funcionalidades do GnuCash, podendo levar o programa a travamentos. Usu??rios que usam o backend de PostgreSQL devem carregar e salvar seus dados em um arquivo XML antes de atualizar o GnuCash."
#: en/PackageNotes.xml:68(title)
msgid "Mozilla"
@@ -810,7 +810,7 @@
#: en/OverView.xml:12(para)
msgid "This release is the culmination of nine months of development, and includes significant new versions of many key products and technologies. The following sections provide a brief overview of major changes from the last release of Fedora Core."
-msgstr "Esta vers??o ?? o resultado de nove meses de desenvolvimento, e inclui novas vers??es de muitos produtos-chave e tecnologias. As seguintes se????es fornecem uma vis??l geral das maiores mudan??as na ??ltima vers??o do Fedora Core."
+msgstr "Esta vers??o ?? o resultado de nove meses de desenvolvimento e inclui novas vers??es de muitos produtos-chave e tecnologias. As seguintes se????es fornecem uma vis??o geral das maiores mudan??as na ??ltima vers??o do Fedora Core."
#: en/OverView.xml:14(title)
msgid "Desktop"
@@ -830,7 +830,7 @@
#: en/OverView.xml:24(para)
msgid "Popular desktop environments GNOME and KDE have innovative new versions included in this release. The GNOME desktop is based on the 2.14 release (http://www.gnome.org/~davyd/gnome-2-14/), and the KDE 3.5 desktop is the general 3.5 release (http://kde.org/announcements/announce-3.5.php)."
-msgstr "Os ambientes desktop populares GNOME e KDE t??m novas vers??es inclusas nesta vers??o. O ambiente GNOME ?? baseado em sua vers??o 2.14 (http://www.gnome.org/~davyd/gnome-2-14/), e o ambiente KDE ?? beaseado na vers??o geral 3.5 (http://kde.org/announcements/announce-3.5.php)."
+msgstr "Os ambientes desktop populares GNOME e KDE t??m novas vers??es inclusas nesta vers??o. O ambiente GNOME ?? baseado em sua vers??o 2.14 (http://www.gnome.org/~davyd/gnome-2-14/) e o ambiente KDE ?? beaseado na vers??o geral 3.5 (http://kde.org/announcements/announce-3.5.php)."
#: en/OverView.xml:27(para)
msgid "The latest versions of GNOME Power Manager (http://www.gnome.org/projects/gnome-power-manager/) and GNOME Screensaver(http://live.gnome.org/GnomeScreensaver/) provide new and integrated power management capabilities."
@@ -842,19 +842,19 @@
#: en/OverView.xml:33(para)
msgid "Suspend to RAM support has also been improved due to infrastructure work done by the hibernate support."
-msgstr "Suporte para suspender para a RAM tamb??m foi aprimorada devido ao trabalho de infraestrutura feito pelo suporte ?? hiberna????o."
+msgstr "O suporte para suspender para a RAM tamb??m foi aprimorado devido ao trabalho de infraestrutura feito pelo suporte ?? hiberna????o."
#: en/OverView.xml:36(para)
msgid "The previous graphical software management utilities have been replaced with the first versions of a new generation of tools. This release includes Pup, a simple interface for system updates, and Pirut, a new package manager that replaces system-config-packages. These build on the yum utility, to provide consistent software installation and update facilities throughout the system."
-msgstr "Os utilit??rios gr??ficos de gerenciamento de programas anteriores foram substitu??dos pelas primeiras vers??es de uma nova gera????o de ferramentas. Esta vers??o inclui o Pup, uma interface simples para atualiza????es do sistema, e o Pirut, um novo gerenciador de pacotes que substitui o system-config-packages. Estes s??o feitos tendo como base o utilit??rio yum, fornecendo instala????es consistentes de programas, e facilidades na atualiza????o do sistema."
+msgstr "Os utilit??rios gr??ficos de gerenciamento de programas anteriores foram substitu??dos pelas primeiras vers??es de uma nova gera????o de ferramentas. Esta vers??o inclui o Pup, uma interface simples para atualiza????es do sistema e o Pirut, um novo gerenciador de pacotes que substitui o system-config-packages. Estes s??o feitos tendo como base o utilit??rio yum, fornecendo instala????es consistentes de programas e facilidades na atualiza????o do sistema."
#: en/OverView.xml:39(para)
msgid "This release of Fedora includes Mono support for the first time, and Mono applications such as Beagle, a desktop search interface; F-Spot, a photo management utility; and Tomboy, a note-taking application."
-msgstr "Esta vers??o do Fedora inclui suporte ao Mono pela primeira vez, e inclui aplica????es Mono, como por exemplo: Beagle, uma interface de busca desktop; F-Spot, um utilit??rio para manuseio de fotos; e Tomboy, uma aplica????o para a tomada de notas."
+msgstr "Esta vers??o do Fedora inclui suporte ao Mono pela primeira vez e inclui aplica????es Mono, como por exemplo: Beagle, uma interface de busca desktop; F-Spot, um utilit??rio para manuseio de fotos; e Tomboy, uma aplica????o para a tomada de notas."
#: en/OverView.xml:42(para)
msgid "You can now enjoy enhanced multimedia support with version 0.10 of the Gstreamer media framework. This milestone release brings major improvements in robustness, compatibility, and features, over previous versions of Gstreamer. The Totem movie player and other media software in this release have been updated to use the new framework."
-msgstr "Voc?? agora pode aproveitar do suporte multim??dia melhorado com a vers??o 0.10 do framework multim??dia Gstreamer. Esta vers??o traz grandes melhorias em termos de robustez, compatibilidade e funcionalidades, em rela????o a antigas vers??es do Gstreamer. Nesta nova vers??o, o tocador de v??deos Toteme outros programas multim??dia foram atualizados para usar o novo framework."
+msgstr "Voc?? agora pode aproveitar do suporte multim??dia melhorado com a vers??o 0.10 do framework multim??dia Gstreamer. Esta vers??o traz grandes melhorias em termos de robustez, compatibilidade e funcionalidades, em rela????o a antigas vers??es do Gstreamer. Nesta nova vers??o, o tocador de v??deos Totem e outros programas multim??dia foram atualizados para usar o novo framework."
#: en/OverView.xml:45(para)
msgid "There is dramatically improved internationalization support with SCIM in Fedora Core 5. The SCIM language input framework provides an easy to use interface for inputting many different non-English languages. SCIM replaces the IIIMF system used in previous Fedora releases."
@@ -874,7 +874,7 @@
#: en/OverView.xml:57(para)
msgid "There are new experimental drivers that provide support for the widely-used Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/)."
-msgstr "H?? novos drivers experimentais que fornecem suporte aos bastante usados chipsets Broadcom 43xx para de placas wireless (http://bcm43xx.berlios.de/)."
+msgstr "H?? novos drivers experimentais que fornecem suporte aos bastante usados chipsets Broadcom 43xx de placas wireless (http://bcm43xx.berlios.de/)."
#: en/OverView.xml:60(para)
msgid "This release includes libnotify, a library that features simple and attractive notifications for the desktop."
@@ -882,11 +882,11 @@
#: en/OverView.xml:63(para)
msgid "Fedora Core 5 now uses gnome-mount, a more efficient mechanism that replaces fstab-sync, and uses HAL to handle mounting."
-msgstr "O Fedora Core 5 agora usa o gnome-mount, um mecanismo mais eficiente que substitui o fstab-sync, e usa HAL para manusear montagens de dispositivos."
+msgstr "O Fedora Core 5 agora usa o gnome-mount, um mecanismo mais eficiente que substitui o fstab-sync e usa HAL para manusear montagens de dispositivos."
#: en/OverView.xml:66(para)
msgid "Printing support is improved in this release with the inclusion of the hplip utility, which replaces hpijs."
-msgstr "O suporte ?? impress??o foi melhorada nesta vers??o com a inclus??o do utilit??rio hplip, que substitui o hpijs."
+msgstr "O suporte ?? impress??o foi melhorado nesta vers??o com a inclus??o do utilit??rio hplip, que substitui o hpijs."
#: en/OverView.xml:71(title)
msgid "System Administration"
@@ -898,7 +898,7 @@
#: en/OverView.xml:75(para)
msgid "The Xen virtualization system has enhanced support. The tools to configure Xen virtual machines on your Fedora Core 5 system now use the standard graphical installation process, run as a window on your desktop. Fedora developers have also created gnome-applet-vm, which provides a simple virtual domains monitor applet, and libvirt (http://libvirt.org/), a library providing an API to use Xen virtualization capabilities."
-msgstr "O suporte ao sistema de virtualiza????o Xen foi aprimorado. As ferramentas para configurar m??quinas virtuais Xen em seu sistema Fedora Core 5 agora usam o processo padr??o de instala????o gr??fica, executado como uma janela em sua ??rea de trabalho. Os desenvolvedores Fedora tamb??m criaram o gnome-applet-vm que fornece um applet de monitora????o de dom??nios virtuais simples, e a libvirt (http://libvirt.org/), uma biblioteca que fornece uma API para alguns usos de virtualiza????o Xen."
+msgstr "O suporte ao sistema de virtualiza????o Xen foi aprimorado. As ferramentas para configurar m??quinas virtuais Xen em seu sistema Fedora Core 5 agora usam o processo padr??o de instala????o gr??fica, executado como uma janela em sua ??rea de trabalho. Os desenvolvedores Fedora tamb??m criaram o gnome-applet-vm que fornece um applet de monitora????o de dom??nios virtuais simples e a libvirt (http://libvirt.org/), uma biblioteca que fornece uma API para alguns usos de virtualiza????o Xen."
#: en/OverView.xml:78(para)
msgid "The industry-leading anaconda installation system continues to evolve. New features for this release include remote logging and improved support for tracebacks. Package management in the installation system is now provided by yum. This enhancement is the first step in enabling access to Fedora Extras from within the installation process."
@@ -906,19 +906,19 @@
#: en/OverView.xml:81(para)
msgid "Version 2.2 of the Apache HTTP server is now included. This release provides enhancements to authentication, database support, proxy facilities, and content filtering."
-msgstr "A vers??o 2.2 do servidor HTTP Apache agora ?? inclu??da. Esta vers??o fornece aprimoramentos na autentica????o, suporte a banco de dados, facilidades de proxy, e filtros de conte??do."
+msgstr "A vers??o 2.2 do servidor HTTP Apache agora ?? inclu??da. Esta vers??o fornece aprimoramentos na autentica????o, suporte a banco de dados, facilidades de proxy e filtros de conte??do."
#: en/OverView.xml:84(para)
msgid "The latest generation of database servers are packaged in this release, including both MySQL 5.0 and PostgreSQL 8.1."
-msgstr "A ??ltima gera????o de servidores de bancos de dados est??o empacotados nesta vers??o, incluindo tanto o MySQL 5.0, quanto o PostgreSQL 8.1."
+msgstr "A ??ltima gera????o de servidores de bancos de dados est?? empacotados nesta vers??o, incluindo tanto o MySQL 5.0, quanto o PostgreSQL 8.1."
#: en/OverView.xml:87(para)
msgid "Several native Java programs are now available compiled with GCJ, such as the Geronimo J2EE server and the Apache Jakarta Project, in addition to the Java programs and development capabilities in the previous releases."
-msgstr "Muitos programas Java nativos compilados com o GCJ agora est??o agora dispon??veis, como por exemplo o servidor J2EE Geronimo e o projeto Apache Jakarta, adicionando ao leque de programas Java e capacidades de desenvolvimento das vers??es anteriores."
+msgstr "Muitos programas Java nativos compilados com o GCJ est??o agora dispon??veis, como por exemplo o servidor J2EE Geronimo e o projeto Apache Jakarta, adicionandos ao leque de programas Java e capacidades de desenvolvimento das vers??es anteriores."
#: en/OverView.xml:90(para)
msgid "There are new tools for system monitoring and performance analysis. This release includes SystemTap (http://fedoraproject.org/wiki/SystemTap), an instrumentation system for debugging and analyzing performance bottle necks, and Frysk (http://fedoraproject.org/wiki/Frysk), an execution analysis technology for monitoring running processes or threads."
-msgstr "H?? novas ferramentas para monitora????o de sistema e an??lise de desempenho. Esta vers??o inclui o SystemTap (http://fedoraproject.org/wiki/SystemTap), um sistema de instrumenta????o para depurar e analisar gargalos de desempenho, e o Frysk (http://fedoraproject.org/wiki/Frysk), uma tecnologia de an??lise de executa????o para monitorar processos ou threads sendo executados."
+msgstr "H?? novas ferramentas para monitora????o de sistema e an??lise de desempenho. Esta vers??o inclui o SystemTap (http://fedoraproject.org/wiki/SystemTap), um sistema de instrumenta????o para depurar e analisar gargalos de desempenho e o Frysk (http://fedoraproject.org/wiki/Frysk), uma tecnologia de an??lise de execu????o para monitorar processos ou threads sendo executados."
#: en/OverView.xml:94(para)
msgid "This release includes system-config-cluster, a utility that allows you to manage cluster configuration in a graphical setting."
@@ -926,7 +926,7 @@
#: en/OverView.xml:97(para)
msgid "The combination of Kexec and Kdump utilities provides modern crash dumping facilities and potential for faster bootup, bypassing the firmware on reboots. Kexec loads a new kernel from a running kernel, and Kdump can provide a memory dump of the previous kernel for debugging."
-msgstr "A combina????o dos utilit??rios Kexec e Kdump fornecem modernas mensagens de depura????o e inicializa????es de sistema mais r??pidas, sobrepujando o firmware no rein??cio. O Kexec carrega um novo kernel a partir do kernel sendo executado, e o Kdump fornece as mensagens de depura????o do kernel anterior para an??lise."
+msgstr "A combina????o dos utilit??rios Kexec e Kdump fornecem mensagens modernas de depura????o e inicializa????es de sistema mais r??pidas, sobrepujando o firmware no rein??cio. O Kexec carrega um novo kernel a partir do kernel sendo executado e o Kdump fornece as mensagens de depura????o do kernel anterior para an??lise."
#: en/OverView.xml:100(para)
msgid "This release includes iscsi-initiator-utils, iSCSI daemon and utility programs that provide support for hardware using the iSCSI interface."
@@ -942,7 +942,7 @@
#: en/OverView.xml:111(para)
msgid "The GCC 4.1 compiler is included, and the entire set of Fedora packages is built with this technology. This provides security and performance enhancements throughout the system."
-msgstr "O compilador GCC 4.1 est?? inclu??do, e todos os pacotes do Fedora s??o feitos com esta tecnologia. Ela fornece melhorias na seguran??a e desempenho atrav??s do sistema."
+msgstr "O compilador GCC 4.1 est?? inclu??do e todos os pacotes do Fedora s??o feitos com esta tecnologia. Ela fornece melhorias na seguran??a e desempenho atrav??s do sistema."
#: en/OverView.xml:114(para)
msgid "The kernels for this release are based on Linux 2.6.16. Refer to the section on the kernel in these release notes for other details."
@@ -950,11 +950,11 @@
#: en/OverView.xml:117(para)
msgid "The PCMCIA framework used by laptop and mobile devices has changed. The older pcmcia-cs package using the cardmgr/pcmcia service has been replaced with a new pcmciautils package. With pcmciautils, PCMCIA devices are handled directly and dynamically by the hotplug and udev subsystems. This update increases both efficiency and performance of the system. For more information about these changes, refer to http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html."
-msgstr "O framework PCMCIA, usado em laptops e outros dispositivos m??veis mudou. O antigo pacote pcmcia-cs que usava o servi??o cardmgr/pcmcia foi substitu??do pelo novo pacote pcmciautils. Com o pcmciautils, dispositivos PCMCIA s??o manuseados diretamente e din??micamente pelos subsistemas hotplug e udev. Esta atualiza????o aumenta tanto a efici??ncia quanto o desempenho do sistema. Para mais informa????es sobre estas mudan??as, veja em http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html."
+msgstr "O framework PCMCIA, usado em laptops e outros dispositivos m??veis, mudou. O antigo pacote pcmcia-cs que usava o servi??o cardmgr/pcmcia foi substitu??do pelo novo pacote pcmciautils. Com o pcmciautils, dispositivos PCMCIA s??o manuseados diretamente e din??micamente pelos subsistemas hotplug e udev. Esta atualiza????o aumenta tanto a efici??ncia quanto o desempenho do sistema. Para mais informa????es sobre estas mudan??as, visite http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html."
#: en/OverView.xml:120(para)
msgid "SELinux implementation has undergone a major change, with a switch to the SELinux reference policy (http://serefpolicy.sourceforge.net/). The SELinux reference policy can support binary policy modules. It is now possible to move SELinux policies into individual packages, making it easier for users to ship site-specific policy customizations when required. This version also adds support for Multi-Category Security (MCS), enabled by default, and Multi-Level Security (MCS). SELinux continues to offer support for TE (Type Enforcement), enabled by default, and RBAC (Role-Based Access Control). Refer to the section on SELinux in these release notes for other details and links to SELinux resources on the Fedora Project pages."
-msgstr "A implementa????o do SELinux passou por grandes mudan??as, com uma troca de pol??ticas para o SELinux reference policy (Refer??ncia de Pol??ticas SELinux - http://serefpolicy.sourceforge.net/). As refer??ncias de pol??ticas SELinux podem suportar m??dulos bin??rios de pol??ticas. Agora ?? poss??vel incluir pol??ticas SELinux em pacotes individuais, tornando mais f??cil para os usu??rios distribuir pol??ticas personalizadas mais espec??ficas quando preciso. Esta vers??o tamb??m adiciona suporte a Multi-Category Security (Seguran??a Multi Camadas - MCS), habilitado por padr??o, e Multi-Level Security (Seguran??a em Multi-N??veis - MCS). O SELinux continua a oferecer suporte a TE (Type Enforcement - Obrigatoriedade por Tipo), habilitado por padr??o, e RBAC (Role-Based Access Control - Controle de Acesso Baseado em Fun????o). Veja a se????o do SELinux nestas notas de vers??o para outros detalhes e links para mat!
eriais sobre SELinux nas p??ginas do Projeto Fedora."
+msgstr "A implementa????o do SELinux passou por grandes mudan??as, com uma troca de pol??ticas para o SELinux reference policy (Refer??ncia de Pol??ticas SELinux - http://serefpolicy.sourceforge.net/). As refer??ncias de pol??ticas SELinux podem suportar m??dulos bin??rios de pol??ticas. Agora ?? poss??vel incluir pol??ticas SELinux em pacotes individuais, tornando mais f??cil para os usu??rios distribuir pol??ticas personalizadas mais espec??ficas quando preciso. Esta vers??o tamb??m adiciona suporte a Multi-Category Security (Seguran??a Multi Camadas - MCS), habilitado por padr??o e Multi-Level Security (Seguran??a em Multi-N??veis - MCS). O SELinux continua a oferecer suporte a TE (Type Enforcement - Obrigatoriedade por Tipo), habilitado por padr??o e RBAC (Role-Based Access Control - Controle de Acesso Baseado em Fun????o). Veja a se????o do SELinux nestas notas de vers??o para outros detalhes e links para mater!
iais sobre SELinux nas p??ginas do Projeto Fedora."
#: en/OverView.xml:126(title)
msgid "Road Map"
@@ -974,7 +974,7 @@
#: en/Networking.xml:11(para)
msgid "Refer to http://wiki.kernelnewbies.org/LinuxChanges for a list of major changes. Some of them are highlighted below."
-msgstr "Veja em http://wiki.kernelnewbies.org/LinuxChanges para uma lista das maiores mudan??as. Algumas delas est??o descritas abaixo:"
+msgstr "Visite http://wiki.kernelnewbies.org/LinuxChanges para uma lista das maiores mudan??as. Algumas delas est??o descritas abaixo:"
#: en/Networking.xml:13(title)
msgid "IPv4 Address Promotion"
@@ -994,7 +994,7 @@
#: en/Networking.xml:19(para)
msgid "Suppose the kernel receives a packet on interface eth0 which generates an ICMP error, and the routing table causes the error message to be generated on interface eth1. If the new sysctl option is enabled, the ICMP error message indicates the source address as interface eth0, instead of the default eth1. This feature may ease network debugging in asynchronous routing setups."
-msgstr "Suponha que o kernel receba um pacote na interface eth0, gerando um erro ICMP, e a tabela de rotas faz com que a mensagem de erro seja gerada na interface eth1. Se a nova op????o do sysctl estiver habilitada, a mensagem de erro ICMP indicar?? como endere??o fonte a interface eth0eth1. Esta funcionalidade pode facilitar a depura????o nas configura????es de rotas ass??ncronas de redes."
+msgstr "Suponha que o kernel receba um pacote na interface eth0, gerando um erro ICMP e a tabela de rotas faz com que a mensagem de erro seja gerada na interface eth1. Se a nova op????o do sysctl estiver habilitada, a mensagem de erro ICMP indicar?? como endere??o fonte a interface eth0, ao inv??s do padr??o que seria eth1. Esta funcionalidade pode facilitar a depura????o nas configura????es de rotas ass??ncronas de redes."
#: en/Networking.xml:22(title)
msgid "LC-Trie Based Routing Lookup Algorithm"
@@ -1002,7 +1002,7 @@
#: en/Networking.xml:23(para)
msgid "A new routing lookup algorithm called trie has been added. It is intended for large routing tables and shows a clear performance improvement over the original hash implementation, at the cost of increased memory consumption and complexity."
-msgstr "Um novo algoritmo de procura de rotas chamado trie foi adicionado. Ele ?? feito para grandes tabelas de rotas e e mostrar uma melhoria de desempenho clara em rela????o a implementa????o hash original, ao custo de um maior consumo de mem??ria e complexidade."
+msgstr "Um novo algoritmo de procura de rotas chamado trie foi adicionado. Ele ?? feito para grandes tabelas de rotas e mostra uma melhoria de desempenho clara em rela????o ?? implementa????o hash original, ao custo de um maior consumo de mem??ria e complexidade."
#: en/Networking.xml:26(title)
msgid "Pluggable Congestion Control Algorithm Infrastructure"
@@ -1010,7 +1010,7 @@
#: en/Networking.xml:27(para)
msgid "TCP congestion control algorithms are now pluggable and thus modular. The legacy NewReno algorithm remains the default, and acts as the fallback algorithm. The following new congestion control algorithms have been added:"
-msgstr "Os algoritmos de controle de congestionamento TCP agora s??o plug??veis e por isso modulares. O algoritmo legado NewReno continua sendo o padr??o, e atua como o algoritmo reserva. Os seguintes algoritmos de controle de congestionamento foram adicionados:"
+msgstr "Os algoritmos de controle de congestionamento TCP agora s??o plug??veis e por isso modulares. O algoritmo legado NewReno continua sendo o padr??o e atua como o algoritmo reserva. Os seguintes algoritmos de controle de congestionamento foram adicionados:"
#: en/Networking.xml:30(para)
msgid "High Speed TCP congestion control"
@@ -1030,7 +1030,7 @@
#: en/Networking.xml:42(para)
msgid "All existing congestion control modules have been converted to this new infrastructure, and the BIC congestion control has received enhancements from BICTCP 1.1 to handle low latency links."
-msgstr "Todos os m??dulos de controle de congestionamento existentes devem ser convertidos para esta nova estrutura, e o controle de congestionamento BIC recebeu melhorias do BICTCP 1.1 para manusear links de baixa lat??ncia."
+msgstr "Todos os m??dulos de controle de congestionamento existentes devem ser convertidos para esta nova estrutura e o controle de congestionamento BIC recebeu melhorias do BICTCP 1.1 para manusear links de baixa lat??ncia."
#: en/Networking.xml:44(title)
msgid "Affecting the Congestion Control Algorithm"
@@ -1038,7 +1038,7 @@
#: en/Networking.xml:45(para)
msgid "The congestion control algorithm is socket specific, and may be changed via the socket option TCP_CONGESTION."
-msgstr "O algoritmo de controle de congestionamento ?? espec??fico a soquete, e pode ser mudava com a op????o de soquete TCP_CONGESTION."
+msgstr "O algoritmo de controle de congestionamento ?? espec??fico a soquete e pode ser mudado com a op????o de soquete TCP_CONGESTION."
#: en/Networking.xml:49(title)
msgid "Queue Avoidance upon Carrier Loss"
@@ -1046,7 +1046,7 @@
#: en/Networking.xml:50(para)
msgid "When a network driver notices a carrier loss, such as when the cable is pulled out, the driver stops the queue in front of the driver. In the past, this stoppage caused the packets to be queued at the queueing discipline layer for an unbound period of time causing unexpected effects. In order to prevent this effect, the core networking stack now refuses to queue any packets for a device that is operationally down, that is, has its queue disabled."
-msgstr "Quando um driver de rede percebe uma perda de carga, como quando o cabo ?? desconectado, o driver p??ra a fila na frente do driver. No passado, esta pausa fazia com que os pacotes entrassem numa camada de fila disciplinar por um per??odo indeterminado, causando assim efeitos inesperados. Afim de evitar isso, a pilha de n??cleo de rede agora n??o aceita enfileirar nenhum pacote de dispositivo que esteja operacionalmente fora do ar."
+msgstr "Quando um driver de rede percebe uma perda de carga, como quando o cabo ?? desconectado, o driver p??ra a fila na frente do driver. No passado, esta pausa fazia com que os pacotes entrassem numa camada de fila disciplinar por um per??odo indeterminado, causando assim efeitos inesperados. A fim de evitar isso, a pilha de n??cleo de rede agora n??o aceita enfileirar nenhum pacote de dispositivo que esteja operacionalmente fora do ar."
#: en/Networking.xml:53(title)
msgid "DCCP Protocol Support"
@@ -1054,7 +1054,7 @@
#: en/Networking.xml:54(para)
msgid "Kernel version 2.6.14-rc1 was the first version to receive support for the DCCP protocol. The implementation is still experimental, but is known to work. Developers have begun work to make userspace applications aware of this new protocol."
-msgstr "A vers??o 2.6.14-rc1 do kernel foi a primeira vers??o a receber suporte ao protocolo DCCP. A implementa????o ainda ?? experimental, mas se sabe que funciona. Os desenvolveres j?? come??aram a trabalhar para que aplica????es estejam cientes deste novo protocolo."
+msgstr "A vers??o 2.6.14-rc1 do kernel foi a primeira vers??o a receber suporte ao protocolo DCCP. A implementa????o ainda ?? experimental, mas se sabe que funciona. Os desenvolvedores j?? come??aram a trabalhar para que aplica????es estejam cientes deste novo protocolo.Ele ?? feito para grandes tabelas"
#: en/Networking.xml:57(title)
msgid "Wireless"
@@ -1062,7 +1062,7 @@
#: en/Networking.xml:58(para)
msgid "A new HostAP driver appears in the kernel starting in 2.6.14-rc1, which allows the emulation of a wireless access point through software. Currently this driver only works for Intersil Prism2-based cards (PC Card/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been added."
-msgstr "Um novo driver HostAP ?? inclu??do no kernel a partir da vers??o 2.6.14-rc1, e permite a emula????o de um access point wireless atrav??s de software. Atualmente este driver s?? funciona com placas baseadas em Intersil Prism2 (PC Card/PCI/PLX). Suporte para placas de rede sem fio Intel(R) PRO/Wireless 2100 e 2200 foram adicionadas."
+msgstr "Um novo driver HostAP ?? inclu??do no kernel a partir da vers??o 2.6.14-rc1 e permite a emula????o de um access point wireless atrav??s de software. Atualmente este driver s?? funciona com placas baseadas em Intersil Prism2 (PC Card/PCI/PLX). Suporte para placas de rede sem fio Intel(R) PRO/Wireless 2100 e 2200 foram adicionadas."
#: en/Networking.xml:61(title)
msgid "Miscellaneous"
@@ -1074,7 +1074,7 @@
#: en/Networking.xml:67(para)
msgid "A new textsearch infrastructure has been added, and is usable with corresponding iptables and extended match."
-msgstr "Uma nova infraestrutura de busca de texto foi adicionada, e est?? us??vel utilizando a extens??o do iptables correspondente."
+msgstr "Uma nova infraestrutura de busca de texto foi adicionada e pode ser usada utilizando a extens??o do iptables correspondente."
#: en/Networking.xml:70(para)
msgid "Both the IPv4 and IPv6 multicast joining interface visible by userspace have been reworked and brought up to the latest standards."
@@ -1132,7 +1132,7 @@
#: en/Multimedia.xml:12(para)
msgid "The default installation of Fedora Core includes Rhythmbox, Totem, and Helix Player for media playback. Many other programs are available in the Fedora Core and Fedora Extras repositories, including the popular XMMS package. Both GNOME and KDE have a selection of players that can be used with a variety of formats. Additional programs are available from third parties to handle other formats."
-msgstr "A instala????o padr??o do Fedora Core inclui o Rhythmbox, Totem, e Helix Player para tocar m??dias. Muitos outros programas est??o dispon??veis nos reposit??rios do Fedora Core e Fedora Extras, incluindo o popular pacote XMMS. Ambos GNOME e KDE t??m uma sele????o de tocadores que podem ser usados com uma variedade de formatos. Programas adicionais est??o dispon??veis de terceiros para suportar outros formatos."
+msgstr "A instala????o padr??o do Fedora Core inclui o Rhythmbox, Totem e Helix Player para tocar m??dias. Muitos outros programas est??o dispon??veis nos reposit??rios do Fedora Core e Fedora Extras, incluindo o popular pacote XMMS. Ambos GNOME e KDE t??m uma sele????o de tocadores que podem ser usados com uma variedade de formatos. Programas adicionais est??o dispon??veis de terceiros para suportar outros formatos."
#: en/Multimedia.xml:13(para)
msgid "Fedora Core also takes full advantage of the Advanced Linux Sound Architecture (ALSA) sound system. Many programs can play sound simultaneously, which was once difficult on Linux systems. When all multimedia software is configured to use ALSA for sound support, this limitation disappears. For more information about ALSA, visit the project website at http://www.alsa-project.org/."
@@ -1144,7 +1144,7 @@
#: en/Multimedia.xml:17(para)
msgid "Fedora includes complete support for the Ogg media container format, and the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. These freely-distributable formats are not encumbered by patent or license restrictions. They provide powerful and flexible alternatives to more popular, restricted formats. The Fedora Project encourages the use of open source formats in place of restricted ones. For more information on these formats and how to use them, refer to the Xiph.Org Foundation's web site at http://www.xiph.org/."
-msgstr "O Fedora inclui suporte completo para o formato de encapsulamento de m??dia Ogg, formato de ??udio Vorbis, de v??deo Theora, de ??udio Speex, e ??udio do tipo lossless (sem perda) FLAC. Estes formatos de livre distribui????o n??o s??o restritos por patentes ou licen??as. Eles fornecem alternativas poderosas e flex??veis para os formatos mais populares e restritos. O Projeto Fedora encoraja o uso de formatos de c??digo aberto ao inv??s dos restritos. Para mais informa????es sobre estes formatos e como us??-los, veja o site da Funda????o Xiph.Org em http://www.xiph.org/."
+msgstr "O Fedora inclui suporte completo para o formato de encapsulamento de m??dia Ogg, formato de ??udio Vorbis, de v??deo Theora, de ??udio Speex e ??udio do tipo lossless (sem perda) FLAC. Estes formatos de livre distribui????o n??o s??o restritos por patentes ou licen??as. Eles fornecem alternativas poderosas e flex??veis para os formatos mais populares e restritos. O Projeto Fedora encoraja o uso de formatos de c??digo aberto ao inv??s dos restritos. Para mais informa????es sobre estes formatos e como us??-los, veja o site da Funda????o Xiph.Org em http://www.xiph.org/."
#: en/Multimedia.xml:20(title)
msgid "MP3, DVD and Other Excluded Multimedia"
@@ -1152,7 +1152,7 @@
#: en/Multimedia.xml:21(para)
msgid "Fedora Core and Fedora Extras cannot include support for MP3 or DVD playback or recording, because the MP3 and MPEG (DVD) formats are patented, and the patent owners have not provided the necessary licenses. Fedora also excludes several multimedia application programs due to patent or license restrictions, such as Flash Player and Real Player. For more on this subject, please refer to http://fedoraproject.org/wiki/ForbiddenItems."
-msgstr "O Feora Core e Fedora Extras n??o podem incluir suporte para tocar ou gravar MP3 e DVD pelo fato de que os formatos de MP3 e MPEG (DVD) s??o patenteados, e os donos das patentes n??o forneceram as licen??as apropriadas. O Fedora tamb??m n??o inclui muitos programas multim??dia devido ?? restri????es de licen??a ou de patentes, como por exemplo o Flash Player ou Real Player. Para mais sobre este assunto, por favor veja em http://fedoraproject.org/wiki/ForbiddenItems."
+msgstr "O Fedora Core e Fedora Extras n??o podem incluir suporte para tocar ou gravar MP3 e DVD pelo fato de que os formatos de MP3 e MPEG (DVD) s??o patenteados e os donos das patentes n??o forneceram as licen??as apropriadas. O Fedora tamb??m n??o inclui muitos programas multim??dia devido ?? restri????es de licen??a ou de patentes, como por exemplo o Flash Player ou Real Player. Para mais sobre este assunto, por favor visite http://fedoraproject.org/wiki/ForbiddenItems."
#: en/Multimedia.xml:24(title)
msgid "CD and DVD Authoring and Burning"
@@ -1160,7 +1160,7 @@
#: en/Multimedia.xml:25(para)
msgid "Fedora Core and Extras include a variety of tools for easily mastering and burning CDs and DVDs. GNOME users can burn directly from the Nautilus file manager, or choose the gnomebaker or graveman packages from Fedora Extras, or the older xcdroast package from Fedora Core. KDE users can use the robust k3b package for these tasks. Console tools include cdrecord, readcd, mkisofs, and other typical Linux applications."
-msgstr "O Fedora Core e Extras inclui uma variedade de ferramentas que tornam a tarefa de masterizar e gravar CDs e DVDs f??cil. Usu??rios GNOME podem gravar diretamente do gerenciador de arquivos Nautilus, ou escolher entre os pacotes gnomebaker e graveman do Fedora Extras, ou o antigo pacote xcdroast do Fedora Core. Usu??rios KDE podem usar o robusto pacote k3b para essas tarefas. Como ferramentas de console, tem-se o cdrecord, readcd, mkisofs, e outras aplica????es t??picas do Linux."
+msgstr "O Fedora Core e Extras inclui uma variedade de ferramentas que tornam a tarefa de masterizar e gravar CDs e DVDs f??cil. Usu??rios GNOME podem gravar diretamente do gerenciador de arquivos Nautilus, ou escolher entre os pacotes gnomebaker e graveman do Fedora Extras, ou o antigo pacote xcdroast do Fedora Core. Usu??rios KDE podem usar o robusto pacote k3b para essas tarefas. Como ferramentas de console, tem-se o cdrecord, readcd, mkisofs e outras aplica????es t??picas do Linux."
#: en/Multimedia.xml:28(title)
msgid "Screencasts"
@@ -1168,7 +1168,7 @@
#: en/Multimedia.xml:29(para)
msgid "You can use Fedora to create and play back screencasts, which are recorded desktop sessions, using open technologies. Fedora Extras 5 includes istanbul, which creates screencasts using the Theora video format. These videos can be played back using one of several players included in Fedora Core. This is the preferred way to submit screencasts to the Fedora Project for either developer or end-user use. For a more comprehensive how-to, refer to http://fedoraproject.org/wiki/ScreenCasting."
-msgstr "Agora voc?? pode usar o Fedora para criar e tocar capturas de telas, que s??o sess??es da ??rea de trabalho gravadas, usando tecnologias livres. O Fedora Extras 5 inclui o istanbul, que cria capturas de tela usando o formato de v??deo Theora. Estes v??deos podem ser tocados usando um dos muitos tocadores inclu??dos no fedora Core. Este ?? o m??todo recomendado para enviar capturas de tela ao Projeto Fedora para uso tanto dos desenvolvedores quanto dos usu??rios. Para um como-fazer mais compreens??vel, veja em http://fedoraproject.org/wiki/ScreenCasting."
+msgstr "Agora voc?? pode usar o Fedora para criar e tocar capturas de telas, que s??o sess??es da ??rea de trabalho gravadas, usando tecnologias livres. O Fedora Extras 5 inclui o istanbul, que cria capturas de tela usando o formato de v??deo Theora. Estes v??deos podem ser tocados usando um dos muitos tocadores inclu??dos no fedora Core. Este ?? o m??todo recomendado para enviar capturas de tela ao Projeto Fedora para uso tanto dos desenvolvedores quanto dos usu??rios. Para um como-fazer mais compreens??vel, visite http://fedoraproject.org/wiki/ScreenCasting."
#: en/Multimedia.xml:32(title)
msgid "Extended Support through Plugins"
@@ -1176,7 +1176,7 @@
#: en/Multimedia.xml:33(para)
msgid "Most of the media players in Fedora Core and Fedora Extras support the use of plugins to add support for additional media formats and sound output systems. Some use powerful backends, like gstreamer, to handle media format support and sound output. Plugin packages for these backends and for individual applications are available in Fedora Core and Fedora Extras, and additional plugins may be available from third parties to add even greater capabilities."
-msgstr "Muitos dos tocadores de m??dia no Fedora Core e Fedora Extras suportam o uso de plugins para incluir suporte a formatos adicionais de m??dia e sistemas de sa??da de som. Alguns usam poderosos backends, como o gstreamer, para manusear suporte a formatos de m??dia e sa??da de som. Pacotes de plugins para estes backends e para aplica????es individuais est??o dispon??veis no Fedora Core e Fedora Extras, e plugins adicionais podem estar dispon??veis a partir de terceiros para adicionar ainda mais capacidade."
+msgstr "Muitos dos tocadores de m??dia no Fedora Core e Fedora Extras suportam o uso de plugins para incluir suporte a formatos adicionais de m??dia e sistemas de sa??da de som. Alguns usam poderosos backends, como o gstreamer, para manusear suporte a formatos de m??dia e sa??da de som. Pacotes de plugins para estes backends e para aplica????es individuais est??o dispon??veis no Fedora Core e Fedora Extras e plugins adicionais podem estar dispon??veis a partir de terceiros para adicionar ainda mais capacidade."
#: en/Legacy.xml:8(title)
msgid "Fedora Legacy - Community Maintenance Project"
@@ -1184,7 +1184,7 @@
#: en/Legacy.xml:9(para)
msgid "The Fedora Legacy Project is a community-supported open source project to extend the lifecycle of select \"maintenance mode\" Red Hat Linux and Fedora Core distributions. The Fedora Legacy Project works with the Linux community to provide security and critical bug fix errata packages. This work extends the effective lifetime of older distributions in environments where frequent upgrades are not possible or desirable. For more information about the Fedora Legacy Project, refer to http://fedoraproject.org/wiki/Legacy."
-msgstr "O Projeto Fedora Legacy (Legado Fedora) ?? um projeto de c??digo aberto feito pela comunidade com o objetivo de extender o ciclo de vida das distribui????es Red Hat Linux e Fedora Core em status de manuten????o. O Projeto Fedora Legacy trabalha junto com a comunidade Linux para fornecer pacotes com corre????es de erros para bugs cr??ticos e de seguran??a. Este trabalho extende o tempo de vida efetivo das distribui????es mais antigas em ambientes onde atualiza????es freq??entes n??o s??o poss??veis ou desejadas. Para mais informa????es sobre o Projeto Fedora Legacy, veja em http://fedoraproject.org/wiki/Legacy."
+msgstr "O Projeto Fedora Legacy (Legado Fedora) ?? um projeto de c??digo aberto feito pela comunidade com o objetivo de extender o ciclo de vida das distribui????es Red Hat Linux e Fedora Core em status de manuten????o. O Projeto Fedora Legacy trabalha junto com a comunidade Linux para fornecer pacotes com corre????es de erros para bugs cr??ticos e de seguran??a. Este trabalho extende o tempo de vida efetivo das distribui????es mais antigas em ambientes onde atualiza????es freq??entes n??o s??o poss??veis ou desejadas. Para mais informa????es sobre o Projeto Fedora Legacy, visite http://fedoraproject.org/wiki/Legacy."
#: en/Legacy.xml:10(para)
msgid "Currently the Fedora Legacy Project maintains the following distributions and releases in maintenance mode:"
@@ -1196,7 +1196,7 @@
#: en/Legacy.xml:16(para)
msgid "Fedora Core 1, 2, and 3"
-msgstr "Fedora Core 1, 2, e 3"
+msgstr "Fedora Core 1, 2 e 3"
#: en/Legacy.xml:19(para)
msgid "The Fedora Legacy Project will provide updates for these releases as long as there is community interest. When interest is not sustained further, maintenance mode ends with the second test release for the third subsequent Core release. For example, maintenance mode for Fedora Core 4, if not sustained by the community, ends with the release of Fedora Core 7 test2. This provides an effective supported lifetime (Fedora Core plus Fedora Legacy Support) of about 18 months."
@@ -1204,11 +1204,11 @@
#: en/Legacy.xml:20(para)
msgid "The Fedora Legacy Project always needs volunteers to perform quality assurance testing on packages waiting to be published as updates. Refer to http://fedoraproject.org/wiki/Legacy/QATesting for more information. Also visit our issues list at http://www.redhat.com/archives/fedora-legacy-list/2005-August/msg00079.html for further information and pointers to bugs we have in the queue."
-msgstr "O Projeto Fedora Legacy est?? sempre precisando de volunt??rios para fazer testes de qualidade em pacotes esperando para serem publicados como atualiza????es. Veja em http://fedoraproject.org/wiki/Legacy/QATesting para mais informa????es. Visite tamb??m nossa lista de problemas em http://www.redhat.com/archives/fedora-legacy-list/2005-August/msg00079.html para mais informa????es e indica????es de bugs que temos na fila."
+msgstr "O Projeto Fedora Legacy est?? sempre precisando de volunt??rios para fazer testes de qualidade em pacotes esperando para serem publicados como atualiza????es. Visite http://fedoraproject.org/wiki/Legacy/QATesting para mais informa????es. Visite tamb??m nossa lista de problemas em http://www.redhat.com/archives/fedora-legacy-list/2005-August/msg00079.html para mais informa????es e indica????es de bugs que temos na fila."
#: en/Legacy.xml:21(para)
msgid "If you need help in getting started, visit the project home page on the Wiki at http://fedoraproject.org/wiki/Legacy, or the Mentors page at http://fedoraproject.org/wiki/Mentors. If you are looking for others ways to participate in Fedora, refer to http://fedoraproject.org/wiki/HelpWanted."
-msgstr "Se voc?? precisa de ajuda para come??ar visite a p??gina do projeto no Wiki em http://fedoraproject.org/wiki/Legacy, ou a p??gina de Mentores em http://fedoraproject.org/wiki/Mentors. Se voc?? estiver procurando por outros meios de participar no Fedora, veja em http://fedoraproject.org/wiki/HelpWanted."
+msgstr "Se voc?? precisa de ajuda para come??ar visite a p??gina do projeto no Wiki em http://fedoraproject.org/wiki/Legacy, ou a p??gina de Mentores em http://fedoraproject.org/wiki/Mentors. Se voc?? estiver procurando por outros meios de participar no Fedora, visite http://fedoraproject.org/wiki/HelpWanted."
#: en/Legacy.xml:23(ulink)
msgid "CategoryLegacy"
@@ -1228,7 +1228,7 @@
#: en/Kernel.xml:12(para)
msgid "This distribution is based on the 2.6 series of the Linux kernel. Fedora Core may include additional patches for improvements, bug fixes, or additional features. For this reason, the Fedora Core kernel may not be line-for-line equivalent to the so-called vanilla kernel from the kernel.org web site:"
-msgstr "Esta distribui????o ?? baseada na s??rie 2.6 do kernel do Linux. O Fedora Core pode incluir patches adicionais para melhorias, corre????es de bugs, e funcionalidades adicionais. Por esta raz??o, o kernel do Fedora Core pode n??o estar em sincronia total com o chamado vanilla kernel do site kernel.org:"
+msgstr "Esta distribui????o ?? baseada na s??rie 2.6 do kernel do Linux. O Fedora Core pode incluir patches adicionais para melhorias, corre????es de bugs e funcionalidades adicionais. Por esta raz??o, o kernel do Fedora Core pode n??o estar em sincronia total com o chamado vanilla kernel do site kernel.org:"
#: en/Kernel.xml:14(ulink)
msgid "http://www.kernel.org/"
@@ -1236,7 +1236,7 @@
#: en/Kernel.xml:16(para)
msgid "To obtain a list of these patches, download the source RPM package and run the following command against it:"
-msgstr "Para obter uma lista destes patches, efetua download do pacote fonte RPM e execute o seguinte comando nele:"
+msgstr "Para obter uma lista destes patches, efetue download do pacote fonte RPM e execute o seguinte comando nele:"
#: en/Kernel.xml:17(screen)
#, no-wrap
@@ -1258,7 +1258,7 @@
#: en/Kernel.xml:23(para)
msgid "If you need a user friendly version of the changelog, refer to http://wiki.kernelnewbies.org/LinuxChanges. A short and full diff of the kernel is available from http://kernel.org/git. The Fedora version kernel is based on the Linus tree."
-msgstr "Se voc?? precisar de uma vers??o amig??vel para o log de mudan??as, veja em http://wiki.kernelnewbies.org/LinuxChanges. Um arquivo de diferen??as curto e completo est?? dispon??vel em http://kernel.org/git. A vers??o do kernel do Fedora ?? baseada na ??rvore do Linus."
+msgstr "Se voc?? precisar de uma vers??o amig??vel para o log de mudan??as, visite http://wiki.kernelnewbies.org/LinuxChanges. Um arquivo de diferen??as curto e completo est?? dispon??vel em http://kernel.org/git. A vers??o do kernel do Fedora ?? baseada na ??rvore do Linus."
#: en/Kernel.xml:24(para)
msgid "Customizations made for the Fedora version are available from http://cvs.fedora.redhat.com ."
@@ -1290,7 +1290,7 @@
#: en/Kernel.xml:46(para)
msgid "You may install sources for all kernel flavors at the same time. The files are installed in the /usr/src/kernels/<version>-[xen-hypervisor|xen-guest|kdump]-<arch>/ tree. Use the following command:"
-msgstr "Voc?? pode instalar os fontes de todos os tipos de kernel ao mesmo tempo. Os arquivos s??o instalados na ??rvore de diret??rio /usr/src/kernels/<vers??o>-[xen-hypervisor|xen-guest|kdump]-<arch>/. Use o seguinte comando:"
+msgstr "Voc?? pode instalar os c??digos-fonte de todos os tipos de kernel ao mesmo tempo. Os arquivos s??o instalados na ??rvore de diret??rio /usr/src/kernels/<vers??o>-[xen-hypervisor|xen-guest|kdump]-<arch>/. Use o seguinte comando:"
#: en/Kernel.xml:47(screen)
#, no-wrap
@@ -1299,7 +1299,7 @@
#: en/Kernel.xml:48(para)
msgid "Select one or more of these flavors, separated by commas and no spaces, as appropriate. Enter the root password when prompted."
-msgstr "Selecione um ou mais destes tipos, separados por v??rgula e sem espa??os, como apropriado. Digite a senha de root quando pedido."
+msgstr "Selecione um ou mais destes tipos, separados por v??rgula e sem espa??os, como apropriado. Digite a senha de root quando solicitada."
#: en/Kernel.xml:50(title)
msgid "x86_64 Default Kernel Provides SMP"
@@ -1323,7 +1323,7 @@
#: en/Kernel.xml:60(para)
msgid "Refer to http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html for information on reporting bugs in the Linux kernel. You may also use http://bugzilla.redhat.com for reporting bugs which are specific to Fedora."
-msgstr "Veja em http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html para informa????es em como relatar bugs no kernel do Linux. Voc?? tamb??m pode usar o http://bugzilla.redhat.com para relatar bugs que s??o espec??ficos para o Fedora."
+msgstr "Visite http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html para informa????es em como relatar bugs no kernel do Linux. Voc?? tamb??m pode usar o http://bugzilla.redhat.com para relatar bugs que s??o espec??ficos para o Fedora."
#: en/Kernel.xml:63(title)
msgid "Following Generic Textbooks"
@@ -1331,7 +1331,7 @@
#: en/Kernel.xml:64(para)
msgid "Many of the tutorials, examples, and textbooks about Linux kernel development assume the kernel sources are installed under the /usr/src/linux/ directory. If you make a symbolic link, as shown below, you should be able to use those learning materials with the Fedora Core packages. Install the appropriate kernel sources, as shown earlier, and then run the following command:"
-msgstr "Muitos tutoriais, exemplos, e textos sobre desenvolvimento do kernel Linux assumem que os c??digos-fonte do kernel s??o instalados no diret??rio /usr/src/linux/. Se voc?? fizer um link simb??lico, como mostrado abaixo, voc?? poder?? usar estes materiais de aprendizado com os pacotes do Fedora Core. Instale os fontes apropriados do kernel, como mostrado anteriormente, e ent??o execute o seguinte comando:"
+msgstr "Muitos tutoriais, exemplos e textos sobre desenvolvimento do kernel Linux assumem que os c??digos-fonte do kernel s??o instalados no diret??rio /usr/src/linux/. Se voc?? fizer um link simb??lico, como mostrado abaixo, voc?? poder?? usar estes materiais de aprendizado com os pacotes do Fedora Core. Instale os c??digos-fonte apropriados do kernel, como mostrado anteriormente e ent??o execute o seguinte comando:"
#: en/Kernel.xml:65(screen)
#, no-wrap
@@ -1340,7 +1340,7 @@
#: en/Kernel.xml:66(para) en/Kernel.xml:85(para) en/Kernel.xml:100(para) en/Extras.xml:20(para)
msgid "Enter the root password when prompted."
-msgstr "Digite a senha de root quando pedido."
+msgstr "Digite a senha de root quando solicitada."
#: en/Kernel.xml:69(title)
msgid "Preparing for Kernel Development"
@@ -1356,11 +1356,11 @@
#: en/Kernel.xml:73(para)
msgid "To simplify the following directions, we have assumed that you want to configure the kernel sources to match your currently-running kernel. In the steps below, the expression <version> refers to the kernel version shown by the command: uname -r."
-msgstr "Para simplificar o caminho, assumimos que voc?? quer configurar os fontes do kernel combinar com o seu kernel atual. Nos passos abaixo, a express??o <vers??o> se refere a vers??o do kernel mostrada pelo comando: uname -r"
+msgstr "Para simplificar o caminho, assumimos que voc?? quer configurar os c??digos-fonte do kernel para combinar com o seu kernel atual. Nos passos abaixo, a express??o <vers??o> se refere ?? vers??o do kernel mostrada pelo comando: uname -r"
#: en/Kernel.xml:75(para)
msgid "Users who require access to Fedora Core original kernel sources can find them in the kernel .src.rpm package. To create an exploded source tree from this file, perform the following steps:"
-msgstr "Usu??rios que necessitam acessar os fontes originais do kernel do Fedora Core podem ach??-los no pacote do kernel com extens??o .src.rpm. Para criar e extrair o c??digo deste arquivo, siga os seguintes passos:"
+msgstr "Usu??rios que necessitam acessar os c??digos-fonte originais do kernel do Fedora Core podem ach??-los no pacote do kernel com extens??o .src.rpm. Para criar e extrair o c??digo deste arquivo, siga os seguintes passos:"
#: en/Kernel.xml:77(title)
msgid "Do Not Build Packages as Super-user"
@@ -1368,7 +1368,7 @@
#: en/Kernel.xml:78(para)
msgid "Building packages as the superuser is inherently dangerous and is not required, even for the kernel. These instructions allow you to install the kernel source as a normal user. Many general information sites refer to /usr/src/linux in their kernel instructions. If you use these instructions, simply substitute ~/rpmbuild/BUILD/kernel-<version>/linux-<version>."
-msgstr "Construir pacotes como super-usu??rio pode ser perigoso e n??o ?? necess??rio, mesmo para o kernel. Estas instru????es permitem voc?? instalar o c??digo-fonte do kernel como um usu??rio normal. Muitos sites de informa????es gerais referenciam o diret??rio /usr/src/linux em suas instru????es de kernel. Se voc?? usa estas instru????es, simplesmente substitua por ~/rpmbuild/BUILD/kernel-<vers??o>/linux-<vers??o>."
+msgstr "Construir pacotes como super-usu??rio pode ser perigoso e n??o ?? necess??rio, mesmo para o kernel. Estas instru????es permitem voc?? instalar o c??digo-fonte do kernel como um usu??rio normal. Muitos sites de informa????es gerais referenciam o diret??rio /usr/src/linux em suas instru????es de kernel. Se voc?? usa estas instru????es, simplesmente substitua por ~/rpmbuild/BUILD/kernel-<vers??o>/linux-<vers??o>."
#: en/Kernel.xml:82(para)
msgid "Prepare a RPM package building environment in your home directory. Run the following commands:"
@@ -1423,7 +1423,7 @@
#: en/Kernel.xml:114(para)
msgid "Prepare the kernel sources using the commands:"
-msgstr "Prepare os fontes do kernel usando os comandos:"
+msgstr "Prepare os c??digos-fonte do kernel usando os comandos:"
#: en/Kernel.xml:115(screen)
#, no-wrap
@@ -1432,7 +1432,7 @@
#: en/Kernel.xml:117(para)
msgid "The kernel source tree is located in the ${HOME}/rpmbuild/BUILD/kernel-<version>/ directory."
-msgstr "A ??rvore dos fontes do kernel est?? localizada no diret??rio ${HOME}/rpmbuild/BUILD/kernel-<vers??o>/ "
+msgstr "A ??rvore dos c??digos-fonte do kernel est?? localizada no diret??rio ${HOME}/rpmbuild/BUILD/kernel-<vers??o>/ "
#: en/Kernel.xml:120(para)
msgid "The configurations for the specific kernels shipped in Fedora Core 5 are in the configs/ directory. For example, the i686 SMP configuration file is named configs/kernel-<version>-i686-smp.config. Issue the following command to place the desired configuration file in the proper place for building:"
@@ -1471,7 +1471,7 @@
#: en/Kernel.xml:130(para)
msgid "That is, substitute everything from the final dash onward."
-msgstr "Ou seja, substitua tudo ap??s do h??fen."
+msgstr "Ou seja, substitua tudo depois do h??fen."
#: en/Kernel.xml:133(para)
msgid "Run the following command:"
@@ -1537,11 +1537,11 @@
#: en/Java.xml:15(para)
msgid "The java-gcj-compat infrastructure has three key components: a GNU Java runtime (libgcj), the Eclipse Java compiler (ecj), and a set of wrappers and links (java-gcj-compat) that present the runtime and compiler to the user in a manner similar to other Java environments."
-msgstr "A infraestrutura do java-gcj-compat tem tr??s componentes chave: uma biblioteca de execu????o GNU Java (libgcj), o compilador Java Eclipse (ecj), e uma s??rie de wrappers e links (java-gcj-compat) que fornecem a biblioteca de execu????o e o compilador para o usu??rio de uma forma semelhante aos ambientes Java."
+msgstr "A infraestrutura do java-gcj-compat tem tr??s componentes chave: uma biblioteca de execu????o GNU Java (libgcj), o compilador Java Eclipse (ecj) e uma s??rie de wrappers e links (java-gcj-compat) que fornecem a biblioteca de execu????o e o compilador para o usu??rio de uma forma semelhante aos ambientes Java."
#: en/Java.xml:16(para)
msgid "The Java software packages included in this Fedora release use the new, integrated java-gcj-compat environment. These packages include OpenOffice.org Base, Eclipse, and Apache Tomcat."
-msgstr "Os pacotes de programas Java inclu??dos nesta vers??o do Fedora usam o novo ambiente integrado java-gcj-compat. Nestes pacotes est??o inclusos o OpenOffice.org Base, Eclipse, e Apache Tomcat."
+msgstr "Os pacotes de programas Java inclu??dos nesta vers??o do Fedora usam o novo ambiente integrado java-gcj-compat. Nestes pacotes est??o inclusos o OpenOffice.org Base, Eclipse e Apache Tomcat."
#: en/Java.xml:18(para)
msgid "Refer to the Java FAQ at http://www.fedoraproject.org/wiki/JavaFAQ for more information on the free Java environment in Fedora."
@@ -1565,7 +1565,7 @@
#: en/Java.xml:29(para)
msgid "In addition to the java-gcj-compat free software stack, Fedora Core is designed to let you install multiple Java implementations and switch between them using the alternatives command line tool. However, every Java system you install must be packaged using the JPackage Project packaging guidelines to take advantage of alternatives."
-msgstr "Em adi????o a pilha de programas livre java-gcj-compat, o Fedora Core ?? desenvolvido para que voc?? possa instalar m??ltiplas implementa????es Java e trocar entre elas usando a ferramenta de linha de comando alternatives. Entretanto, todo sistema Java que voc?? instalar precisa ser empacotado usando as regras de empacotamento do Projeto JPackage para obter proveito do alternatives."
+msgstr "Em adi????o ?? pilha de programas livre java-gcj-compat, o Fedora Core ?? desenvolvido para que voc?? possa instalar m??ltiplas implementa????es Java e trocar entre elas usando a ferramenta de linha de comando alternatives. Entretanto, todo sistema Java que voc?? instalar precisa ser empacotado usando as regras de empacotamento do Projeto JPackage para obter proveito do alternatives."
#: en/Java.xml:30(para)
msgid "Once installed properly, the root user should be able to switch between java and javac implementations using the alternatives command:"
@@ -1598,11 +1598,11 @@
#: en/Installer.xml:8(title)
msgid "Installation-Related Notes"
-msgstr "Notas Relacionadas a Instala????o"
+msgstr "Notas Relacionadas ?? Instala????o"
#: en/Installer.xml:9(para)
msgid "This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core 5 in general."
-msgstr "Esta se????o fala sobre notas relacionadas ao Anaconda (o programa de instala????o do Fedora Core), e sobre a instala????o do Fedora Core 5 em geral."
+msgstr "Esta se????o fala sobre notas relacionadas ao Anaconda (o programa de instala????o do Fedora Core) e sobre a instala????o do Fedora Core 5 em geral."
#: en/Installer.xml:11(title)
msgid "Downloading Large Files"
@@ -1610,7 +1610,7 @@
#: en/Installer.xml:12(para)
msgid "If you intend to download the Fedora Core 5 DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2GB in size. wget 1.9.1-16 and above, curl and ncftpget do not have this limitation, and can successfully download files larger than 2GB. BitTorrent is another method for downloading large files. For information about obtaining and using the torrent file, refer to http://torrent.fedoraproject.org/."
-msgstr "Se voc?? pretende efetuar download da imagem ISO do DVD Fedora Core 5, lembre-se que nem todas as ferramentas de download podem suportar arquivos maiores que 2GB. O wget 1.9.1-16 e mais atuais, o curl e o ncftpget n??o possuem esta limita????o, e podem efetuar download com sucesso de arquivos maiores que 2GB. O BitTorrent ?? um outro m??todo para efetuar download de arquivos grandes. Para informa????es sobre como obter e usar o arquivo torrent, veja em http://torrent.fedoraproject.org/."
+msgstr "Se voc?? pretende efetuar download da imagem ISO do DVD Fedora Core 5, lembre-se que nem todas as ferramentas de download podem suportar arquivos maiores que 2GB. O wget 1.9.1-16 e mais atuais, o curl e o ncftpget n??o possuem esta limita????o e podem efetuar com sucesso download de arquivos maiores que 2GB. O BitTorrent ?? um outro m??todo para efetuar download de arquivos grandes. Para informa????es sobre como obter e usar o arquivo torrent, visite http://torrent.fedoraproject.org/."
#: en/Installer.xml:25(title)
msgid "Anaconda Notes"
@@ -1618,11 +1618,11 @@
#: en/Installer.xml:28(para)
msgid "Anaconda tests the integrity of installation media by default. This function works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. The Fedora Project recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs. Many of the bugs reported are actually due to improperly-burned CDs. To use this test, type linux mediacheck at the boot: prompt."
-msgstr "O Anaconda testa a integridade da m??dia de instala????o por padr??o. Esta fun????o funciona com os m??todos de instala????o por CD, DVD, ISO no disco r??gido, e ISO por NFS. O Projeto Fedora recomenda que voc?? teste toda a sua m??dia de instala????o antes de come??ar o processo de instala????o, antes de relatar qualquer bug relacionado a instala????o. Muitos dos bugs relatados s??o causados por CDs gravados inapropriadamente. Para executar este teste, digite linux mediacheck no prompt boot:."
+msgstr "O Anaconda testa a integridade da m??dia de instala????o por padr??o. Esta fun????o funciona com os m??todos de instala????o por CD, DVD, ISO no disco r??gido e ISO por NFS. O Projeto Fedora recomenda que voc?? teste toda a sua m??dia de instala????o antes de come??ar o processo de instala????o, antes de relatar qualquer bug relacionado a instala????o. Muitos dos bugs relatados s??o causados por CDs gravados inapropriadamente. Para executar este teste, digite linux mediacheck no prompt boot:."
#: en/Installer.xml:30(para)
msgid "The mediacheck function is highly sensitive, and may report some usable discs as faulty. This result is often caused by disc writing software that does not include padding when creating discs from ISO files. For best results with mediacheck, boot with the following option:"
-msgstr "A fun????o mediacheck ?? extremamente sens??vel, e pode indicar alguns discos us??veis como falhos. Este resultado geralmente ?? causado por programas de grava????o de CD que n??o inclui alinhamento quando gravam discos a partir de arquivos ISO. Para melhores resultados com o mediacheck, inicie com a seguinte op????o:"
+msgstr "A fun????o mediacheck ?? extremamente sens??vel e pode indicar alguns discos us??veis como falhos. Este resultado geralmente ?? causado por programas de grava????o de CD que n??o inclui alinhamento quando gravam discos a partir de arquivos ISO. Para melhores resultados com o mediacheck, inicie com a seguinte op????o:"
#: en/Installer.xml:31(screen)
#, no-wrap
@@ -1651,7 +1651,7 @@
#: en/Installer.xml:49(para)
msgid "You must boot from Installation Disc 1 or a rescue CD in order to use this feature."
-msgstr "Voc?? precisa dar boot do Disco 1 de Instala????o ou de um CD de recupera????o (Rescue CD) para utilizar essa funcionalidade."
+msgstr "Voc?? precisa inicializar do Disco 1 de Instala????o ou de um CD de recupera????o (Rescue CD) para utilizar essa funcionalidade."
#: en/Installer.xml:54(para)
msgid "Fedora Core 5 supports graphical FTP and HTTP installations. However, the installer image must either fit in RAM or appear on local storage such as Installation Disc 1. Therefore, only systems with more than 192MiB of RAM, or which boot from Installation Disc 1, can use the graphical installer. Systems with 192MiB RAM or less will fall back to using the text-based installer automatically. If you prefer to use the text-based installer, type linux text at the boot: prompt."
@@ -1663,11 +1663,11 @@
#: en/Installer.xml:61(para)
msgid "The installer checks hardware capability and installs either the uniprocessor or SMP (Symmetric Multi Processor) kernel as appropriate in this release. Previous releases installed both variants and used the appropriate one as default."
-msgstr "Nesta vers??o, o instalador verifica a capacidade do hardware, e de acordo com a verifica????o, instala o kernel para um ??nico processador ou para m??ltiplos (SMP - Symmetric Multi Processor). Vers??es anteriores instalavam ambas variantes e usavam o apropriado como padr??o."
+msgstr "Nesta vers??o, o instalador verifica a capacidade do hardware e de acordo com a verifica????o, instala o kernel para um ??nico processador ou para m??ltiplos (SMP - Symmetric Multi Processor). Vers??es anteriores instalavam ambas variantes e usavam o apropriado como padr??o."
#: en/Installer.xml:64(para)
msgid "Anaconda now supports installation on several IDE software RAID chipsets using dmraid. To disable this feature, add the nodmraid option at the boot: prompt. For more information, refer to http://fedoraproject.org/wiki/DmraidStatus ."
-msgstr "O Anaconda agora suporta instala????es em muitos chipsets de RAID IDE por software, utilizando o dmraid. Para desabilitar esta funcionalidade, adicione a op????o nodmraid no prompt boot:. Para mais informa????es, veja em http://fedoraproject.org/wiki/DmraidStatus ."
+msgstr "O Anaconda agora suporta instala????es em muitos chipsets de RAID IDE por software, utilizando o dmraid. Para desabilitar esta funcionalidade, adicione a op????o nodmraid no prompt boot:. Para mais informa????es, visite http://fedoraproject.org/wiki/DmraidStatus ."
#: en/Installer.xml:67(title)
msgid "Do not boot only half of a dmraid RAID1 (mirror)"
@@ -1675,7 +1675,7 @@
#: en/Installer.xml:68(para)
msgid "Various situations may occur that cause dmraid to break the mirror, and if you boot in read/write mode into only one of the mirrored disks, it causes the disks to fall out of sync. No symptoms arise, since the primary disk is reading and writing to itself. But if you attempt to re-establish the mirror without first synchronizing the disks, you could corrupt the data and have to reinstall from scratch without a chance for recovery."
-msgstr "V??rias situa????es podem acontecer, causando a quebra do espelho pelo dmraid, e se voc?? iniciar em modo leitura/escrita em apenas um dos discos espelhados, isto pode fazer com que os discos saiam de sincronia. Nenhum sintoma aparece, pois o disco prim??rio est?? lendo e escrevendo de si mesmo. Mas se voc?? tentar estabelecer um espelho sem primeiro sincronizar os discos, voc?? pode corromper seus dados e ter de reinstalar tudo do zero sem chance de recupera????o."
+msgstr "V??rias situa????es podem acontecer, causando a quebra do espelho pelo dmraid e se voc?? iniciar em modo leitura/escrita em apenas um dos discos espelhados, isto pode fazer com que os discos saiam de sincronia. Nenhum sintoma aparece, pois o disco prim??rio est?? lendo e escrevendo de si mesmo. Mas se voc?? tentar estabelecer um espelho sem primeiro sincronizar os discos, voc?? pode corromper seus dados e ter de reinstalar tudo do zero sem chance de recupera????o."
#: en/Installer.xml:69(para)
msgid "If the mirror is broken, you should be able to resync from within the RAID chipset BIOS or by using the dd command. Reinstallation is always an option."
@@ -1691,7 +1691,7 @@
#: en/Installer.xml:79(para)
msgid "The package selection screen has been revamped. The new, simplified screen only displays the optional groups Office and Productivity (enabled by default), Software Development, Web Server, and Virtualization (Xen). However, you may still fully customize your package selection. Refer to http://fedoraproject.org/wiki/Anaconda/PackageSelection for more details."
-msgstr "A tela de sele????o de pacotes foi refeita. A nova e simplificada tela mostra apenas os grupos opcionais Escrit??rio e Produtividade (habilitado por padr??o), Desenvolvimento de Software, Servidor Web, e Virtualiza????o (Xen). Entretando, voc?? ainda pode personalizar sua sele????o de pacotes. Veja em http://fedoraproject.org/wiki/Anaconda/PackageSelection para mais detalhes."
+msgstr "A tela de sele????o de pacotes foi refeita. A nova e simplificada tela mostra apenas os grupos opcionais Escrit??rio e Produtividade (habilitado por padr??o), Desenvolvimento de Software, Servidor Web e Virtualiza????o (Xen). Entretando, voc?? ainda pode personalizar sua sele????o de pacotes. Visite http://fedoraproject.org/wiki/Anaconda/PackageSelection para mais detalhes."
#: en/Installer.xml:82(para)
msgid "Firewall and SELinux configuration has been moved to the Setup Agent (firstboot), the final phase of the graphical installation process."
@@ -1703,7 +1703,7 @@
#: en/Installer.xml:88(para)
msgid "This release supports remote logging via syslog. To use this feature, add the option syslog=host:port at the boot prompt. The :port specifier is optional."
-msgstr "Esta vers??o suporta log remoto atrav??s do syslog. Para usar essa funcionalidade, adicione a op????o syslog=host:port no prompt de boot. O especificador :port ?? opcional."
+msgstr "Esta vers??o suporta log remoto atrav??s do syslog. Para usar essa funcionalidade, adicione a op????o syslog=host:port no prompt de inicializa????o. O especificador :port ?? opcional."
#: en/Installer.xml:91(para)
msgid "Anaconda now renders release notes with the gtkhtml widget for better capability."
@@ -1711,7 +1711,7 @@
#: en/Installer.xml:95(para)
msgid "Kickstart has been refactored into its own package, pykickstart, and contains a parser and writers. As a result of this change, validation and extension is now much easier."
-msgstr "O KIckstart foi reconstru??do em um pacote pr??prio, o pykickstart, e cont??m as fun????es de an??lise e escrita. Como resultado desta mudan??a valida????o e extens??o agora s??o muito mais f??ceis."
+msgstr "O KIckstart foi reconstru??do em um pacote pr??prio, o pykickstart e cont??m as fun????es de an??lise e escrita. Como resultado desta mudan??a valida????o e extens??o agora s??o muito mais f??ceis."
#: en/Installer.xml:98(para)
msgid "Anaconda now uses yum as the backend for solving package dependencies. Additional repositories such as Fedora Extras are expected to be supported during installation in a future release."
@@ -1723,7 +1723,7 @@
#: en/Installer.xml:107(para)
msgid "Some Sony VAIO notebook systems may experience problems installing Fedora Core from CD-ROM. If this happens, restart the installation process and add the following option to the boot command line:"
-msgstr "Alguns sistemas em notebooks Sony VAIO poder??o experimentar problemas ao instalar o Fedora Core a partir de um CD-ROM. Se isso acontecer, reinicie o processo de instala????o e adicione a seguinte op????o na linha de comando de boot:"
+msgstr "Alguns sistemas em notebooks Sony VAIO poder??o experimentar problemas ao instalar o Fedora Core a partir de um CD-ROM. Se isso acontecer, reinicie o processo de instala????o e adicione a seguinte op????o na linha de comando de inicializa????o:"
#: en/Installer.xml:110(screen)
#, no-wrap
@@ -1732,7 +1732,7 @@
#: en/Installer.xml:113(para)
msgid "Installation should proceed normally, and any devices not detected are configured the first time Fedora Core is booted."
-msgstr "A instala????o deve prosseguir normalmente, e quaisquer dispositivos n??o detectados s??o configurados na primeira vez que o Fedora Core ?? iniciado."
+msgstr "A instala????o deve prosseguir normalmente e quaisquer dispositivos n??o detectados s??o configurados na primeira vez que o Fedora Core ?? iniciado."
#: en/Installer.xml:116(para)
msgid "Not all IDE RAID controllers are supported. If your RAID controller is not yet supported by dmraid, you may combine drives into RAID arrays by configuring Linux software RAID. For supported controllers, configure the RAID functions in the computer BIOS."
@@ -1752,7 +1752,7 @@
#: en/Installer.xml:126(para)
msgid "Before you upgrade, back up the system completely. In particular, preserve /etc, /home, and possibly /opt and /usr/local if customized packages are installed there. You may wish to use a multi-boot approach with a \"clone\" of the old installation on alternate partition(s) as a fallback. In that case, creating alternate boot media such as GRUB boot floppy."
-msgstr "Antes de atualizar, fa??a um backup completo do seu sistema. Em particular, preserve os diret??rios /etc, /home, e possivelmente o /opt e /usr/local caso pacotes personalizados estejam instalados neles. Voc?? pode querer criar um esquema multi-boot com um \"clone\" da instala????o anterior em uma parti????o separada como reserva. Neste caso, criando uma m??dia alternativa de boot como por exemplo um disquete de boot do GRUB."
+msgstr "Antes de atualizar, fa??a um backup completo do seu sistema. Em particular, preserve os diret??rios /etc, /home e possivelmente o /opt e /usr/local caso pacotes personalizados estejam instalados neles. Voc?? pode querer criar um esquema multi-boot com um \"clone\" da instala????o anterior em uma parti????o separada como reserva. Neste caso, criando uma m??dia alternativa de inicializa????o como por exemplo um disquete de inicializa????o do GRUB."
#: en/Installer.xml:128(title)
msgid "System Configuration Backups"
@@ -1789,7 +1789,7 @@
#: en/I18n.xml:12(para)
msgid "SCIM (Simple Common Input Method) has replaced IIIMF as the input method system for Asian and other languages in Fedora Core in this release. SCIM uses Ctrl-Space as the default trigger key to toggle on and off the input method, though it is easy to change the hotkey or add hotkeys with the SCIM setup configuration tool. When scim-anthy is active Japanese users can now use the Zenkaku_Hankaku key to toggle between Japanese and ASCII input."
-msgstr "O SCIM (Simple Common Input Method) substituiu o IIIMF como sistema de m??todo de entrada para idiomas asi??ticos (e outros) nesta vers??o do Fedora Core. O SCIM usa Ctrl+Space como teclas padr??es para ativar e desativar o m??todo de entrada, e ?? f??cil mudar ou adicionar as teclas de atalho atrav??s da ferramenta de configura????o do SCIM. Quando o scim-anthy est?? ativo, usu??rios Japoneses podem agora usar a tecla Zenkaku_Hankaku para mudar entre os m??todos de entrada Japon??s e ASCII."
+msgstr "O SCIM (Simple Common Input Method) substituiu o IIIMF como sistema de m??todo de entrada para idiomas asi??ticos (e outros) nesta vers??o do Fedora Core. O SCIM usa Ctrl+Space como teclas padr??es para ativar e desativar o m??todo de entrada e ?? f??cil mudar ou adicionar as teclas de atalho atrav??s da ferramenta de configura????o do SCIM. Quando o scim-anthy est?? ativo, usu??rios Japoneses podem agora usar a tecla Zenkaku_Hankaku para mudar entre os m??todos de entrada Japon??s e ASCII."
#: en/I18n.xml:14(title)
msgid "Installation"
@@ -1834,7 +1834,7 @@
#: en/I18n.xml:33(para)
msgid "If your desktop is not running in an Asian locale, to activate it in your user account, run these commands, then logout and login again to your desktop."
-msgstr "Se o seu desktop n??o estiver executando de uma localidade asi??tica, para atvar em sua conta de usu??rio, execute estes comandos, deslogue-se e logue-se novamente em sua ??rea de trabalho."
+msgstr "Se o seu desktop n??o estiver executando de uma localidade asi??tica, para ativar em sua conta de usu??rio, execute estes comandos, deslogue-se e logue-se novamente em sua ??rea de trabalho."
#: en/I18n.xml:34(screen)
#, no-wrap
@@ -1847,11 +1847,11 @@
#: en/I18n.xml:39(para)
msgid "When SCIM is running, an applet icon appears in the notification area of the desktop panel. The icon is a grey keyboard icon when SCIM is inactive, and an Input Method Engine (IME) icon when it is active. When SCIM is active, by default the SCIM input method toolbar with status information also appears."
-msgstr "Quando o SCIM estiver rodando, um ??cone de applet aparece na ??rea de notifica????o do pain??l de sua ??rea de trabalho. O ??cone ?? um teclado cinza quando o SCIM est?? desativado, e um ??cone do Input Method Engine (Mecanismo de M??todo de Entrada - IME) quando ativado. Quando o SCIM est?? ativado, por padr??o a barra de ferramentas do m??todo de entrada com informa????es de status tamb??m aparece."
+msgstr "Quando o SCIM estiver rodando, um ??cone de applet aparece na ??rea de notifica????o do painel de sua ??rea de trabalho. O ??cone ?? um teclado cinza quando o SCIM est?? desativado e um ??cone do Input Method Engine (Mecanismo de M??todo de Entrada - IME) quando ativado. Quando o SCIM est?? ativado, por padr??o a barra de ferramentas do m??todo de entrada com informa????es de status tamb??m aparece."
#: en/I18n.xml:40(para)
msgid "Clicking the left mouse button on the applet activates a SCIM language switching menu for changing the current Input Method Engine. The menu only appears when an application using the Input Method has focus. Clicking the right mouse button on the applet or SCIM toolbar activates the setup menu."
-msgstr "Clicando com o bot??o esquerdo do mouse no applet ativa o menu de mudan??a de idioma SCIM, para que se possa mudar o Mecanismo de M??todo de Entrada atual. O menu s?? aparece quando uma aplica????o que esteja usando o M??todo de Entrada esteja com foco. Clicando com o bot??o direito do mouse no applet ou na barra de ferramentas SCIM faz com que o menu de configura????o seja ativado."
+msgstr "Clicar com o bot??o esquerdo do mouse no applet ativa o menu de mudan??a de idioma SCIM, para que se possa mudar o Mecanismo de M??todo de Entrada atual. O menu s?? aparece quando uma aplica????o que esteja usando o M??todo de Entrada esteja com foco. Clicando com o bot??o direito do mouse no applet ou na barra de ferramentas SCIM faz com que o menu de configura????o seja ativado."
#: en/I18n.xml:43(title)
msgid "SCIM configuration"
@@ -1867,7 +1867,7 @@
#: en/I18n.xml:48(para)
msgid "anthy, a new Japanese conversion engine replaces the old Canna server system, and libchewing, a new Traditional Chinese conversion engine, has been added."
-msgstr "O anthy, um novo mecanismo de convers??o de Japon??s substitui o antigo sistema Canna, e o libchewing, um novo mecanismo de convers??o de Chin??s Tradicional, foi adicionado."
+msgstr "O anthy, um novo mecanismo de convers??o de Japon??s substitui o antigo sistema Canna e o libchewing, um novo mecanismo de convers??o de Chin??s Tradicional, foi adicionado."
#: en/I18n.xml:53(title)
msgid "Fonts"
@@ -1879,7 +1879,7 @@
#: en/I18n.xml:55(para)
msgid "New fonts for Chinese have been added: AR PL ShanHeiSun Uni (uming.ttf) and AR PL ZenKai Uni (ukai.ttf). The default font is AR PL ShanHeiSun Uni, which contains embedded bitmaps. If you prefer outline glyphs you can put the following section in your ~/.font.conf file:"
-msgstr "Novas fontes para o Chin??s foram adicionadas: AR PL ShanHeiSun Uni (uming.ttf) e AR PL ZenKai Uni (ukai.ttf). A fonte padr??o ?? a AR PL ShanHeiSun Uni, e cont??m bitmaps integrados. Se voc?? prefere s??mbolos em linha voc?? colocar a seguinte se????o em seu arquivo ~/.font.conf:"
+msgstr "Novas fontes para o Chin??s foram adicionadas: AR PL ShanHeiSun Uni (uming.ttf) e AR PL ZenKai Uni (ukai.ttf). A fonte padr??o ?? a AR PL ShanHeiSun Uni e cont??m bitmaps integrados. Se voc?? prefere s??mbolos em linha voc?? colocar a seguinte se????o em seu arquivo ~/.font.conf:"
#: en/I18n.xml:56(screen)
#, no-wrap
@@ -1913,7 +1913,7 @@
#: en/FileServers.xml:11(para)
msgid "This section refers to file transfer and sharing servers. Refer to http://fedoraproject.org/wiki/Docs/Beats/WebServers and http://fedoraproject.org/wiki/Docs/Beats/Samba for information on HTTP (Web) file transfer and Samba (Windows) file sharing services."
-msgstr "Esta se????o se refere aos servidores de transfer??ncia de arquivos e compartilhamento. Veja em http://fedoraproject.org/wiki/Docs/Beats/WebServers e http://fedoraproject.org/wiki/Docs/Beats/Samba para mais informa????es sobre trasfer??ncias de arquivos via HTTP (Web) e compartilhamentos Samba (Windows)."
+msgstr "Esta se????o refere-se aos servidores de transfer??ncia de arquivos e compartilhamento. Visite http://fedoraproject.org/wiki/Docs/Beats/WebServers e http://fedoraproject.org/wiki/Docs/Beats/Samba para mais informa????es sobre trasfer??ncias de arquivos via HTTP (Web) e compartilhamentos Samba (Windows)."
#: en/FileServers.xml:14(title)
msgid "Netatalk (Macintosh Compatibility)"
@@ -1929,11 +1929,11 @@
#: en/FileServers.xml:18(para)
msgid "You may experience data loss when upgrading from Netatalk version 1 to version 2."
-msgstr "Voc?? pode experimentar perda de dados quando atualizando da vers??o 1 do Netatalk para a vers??o 2."
+msgstr "Voc?? pode experimentar perda de dados ao atualizar da vers??o 1 do Netatalk para a vers??o 2."
#: en/FileServers.xml:21(para)
msgid "Version 2 of Netatalk stores file resource forks using a different method from the previous version, and may require a different file name encoding scheme. Please read the documentation and plan your migration before upgrading. Refer to the upgrade information available directly from the Netatalk site at http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html."
-msgstr "A vers??o 2 do Netatalk armazena os recursos de arquivos em um m??todo diferente que vers??es anteriores, e podem necessitar de um esquema de codifica????o de nomes de arquivos diferente. Por favor leia a documenta????o e planeje sua migra????o antes de atualizar. Veja as informa????es de atualiza????o dispon??veis no site do Netatalk, localizado em http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html."
+msgstr "A vers??o 2 do Netatalk armazena os recursos de arquivos com um m??todo diferente das vers??es anteriores e podem necessitar de um esquema de codifica????o de nomes de arquivos diferente. Por favor leia a documenta????o e planeje sua migra????o antes de atualizar. Veja as informa????es de atualiza????o dispon??veis no site do Netatalk, localizado em http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html."
#: en/FileServers.xml:22(para)
msgid "The documentation is also included in the netatalk package. Refer to either /usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html or /usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf (numbered page 25, document page 33)."
@@ -1949,11 +1949,11 @@
#: en/Feedback.xml:11(para)
msgid "This section concerns feedback on the release notes themselves. To provide feedback on Fedora software or other system elements, please refer to http://fedoraproject.org/wiki/BugsAndFeatureRequests."
-msgstr "Esta se????o ?? sobre o feedback das notas de vers??o. O feedback ?? o retorno dos usu??rios em rela????o a uma certa coisa, sugest??es, indica????es de erros, cr??ticas, entre outros. Para fornecer feedback sobre programas no Fedora ou outros elementos do sistema, por favor veja em http://fedoraproject.org/wiki/BugsAndFeatureRequests."
+msgstr "Esta se????o ?? sobre o feedback das notas de vers??o. O feedback ?? o retorno dos usu??rios em rela????o a uma certa coisa, sugest??es, indica????es de erros, cr??ticas, entre outros. Para fornecer feedback sobre programas no Fedora ou outros elementos do sistema, por favor visite http://fedoraproject.org/wiki/BugsAndFeatureRequests."
#: en/Feedback.xml:17(para)
msgid "Thanks for your interest in giving feedback for these release notes. If you feel these release notes could be improved in any way, you can provide your feedback directly to the beat writers. Here are several ways to do so, in order of preference:"
-msgstr "Obrigado pelo seu interesse em fornece feedback para estas notas de vers??o. Se voc?? achar que estas notas de vers??o podem ser melhoradas de alguma forma, voc?? pode fornecer seu feedback diretamente para os Escritores Beats. Aqui est??o v??rios meios de faz??-lo, na ordem de prefer??ncia:"
+msgstr "Obrigado pelo seu interesse em fornecer feedback para estas notas de vers??o. Se voc?? achar que estas notas de vers??o podem ser melhoradas de alguma forma, voc?? pode fornecer seu feedback diretamente para os Escritores Beats. Aqui est??o v??rios meios de faz??-lo, na ordem de prefer??ncia:"
#: en/Feedback.xml:20(para)
msgid "Edit content directly at http://fedoraproject.org/wiki/Docs/Beats"
@@ -1969,7 +1969,7 @@
#: en/Feedback.xml:32(para)
msgid "A release note beat is an area of the release notes that is the responsibility of one or more content contributors to oversee. For more ifnormation about beats, refer to http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats."
-msgstr "Um nota de vers??o beat ?? uma ??rea das notas de vers??o que ?? de responsabilidade para que um ou mais contribuidores de conte??do mantenham. Para mais informa????es sobre os beats, veja em http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats."
+msgstr "Uma nota de vers??o beat ?? uma ??rea das notas de vers??o mantida por um ou mais contribuidores de conte??do, sob suas responsabilidades. Para mais informa????es sobre os beats, visite http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats."
#: en/Feedback.xml:33(para)
msgid "Thank you (in advance) for your feedback!"
@@ -2005,11 +2005,11 @@
#: en/Extras.xml:17(para)
msgid "To install software from either the Core or Extras repositories, choose Applications > Add/Remove Software. Enter the root password when prompted. Select the software you require from the list, and choose Apply."
-msgstr "Para instalar porgramas a partir dos reposit??rios Core e Extras, v?? em Aplica????es > Adicionar/Remover Programas. Digite a senha de root quando pedido. Selecione da lista o programa que voc?? necessita, e escolha Aplicar."
+msgstr "Para instalar porgramas a partir dos reposit??rios Core e Extras, v?? em Aplica????es > Adicionar/Remover Programas. Digite a senha de root quando solicitada. Selecione da lista o programa que voc?? necessita e escolha Aplicar."
#: en/Extras.xml:18(para)
msgid "Alternatively, you may install software with the yum command-line utility. For example, this command automatically installs the abiword package, and all of the dependencies that are required:"
-msgstr "Alternativamente, voc?? pode instalar programas com o utilit??rio de linha de comando yum. Por exemplo, este comando instala automaticamente o pacote abiword, e todas as suas depend??ncias:"
+msgstr "Alternativamente, voc?? pode instalar programas com o utilit??rio de linha de comando yum. Por exemplo, este comando instala automaticamente o pacote abiword e todas as suas depend??ncias:"
#: en/Extras.xml:19(screen)
#, no-wrap
@@ -2022,7 +2022,7 @@
#: en/Extras.xml:24(para)
msgid "As of the release of Fedora Core 5, there are approximately 2,000 packages in Fedora Extras, built from 1,350 source packages. The following list includes some popular and well-known applications that are maintained by community members in Fedora Extras:"
-msgstr "No tempo da vers??o Fedora Core 5, existem aproximadamente 2.000 pacotes no Fedora Extras, constru??dos a partir de 1.350 pacotes fonte. A seguinte lista inclui alguns das aplica????es mais populares que s??o mantidas no Fedora Extras por membros da comunidade:"
+msgstr "No tempo da vers??o Fedora Core 5, existem aproximadamente 2.000 pacotes no Fedora Extras, constru??dos a partir de 1.350 pacotes fonte. A seguinte lista inclui algumas das aplica????es mais populares que s??o mantidas no Fedora Extras por membros da comunidade:"
#: en/Extras.xml:27(para)
msgid "abiword - elegant word-processing application"
@@ -2046,7 +2046,7 @@
#: en/Extras.xml:47(para)
msgid "fuse - tool for attaching non-standard devices and network services as directories"
-msgstr "fuse - ferramenta para anexar dispositivos n??o-padr??es e servi??os de rede como se fossem diret??rios"
+msgstr "fuse - ferramenta para anexar dispositivos n??o-padr??o e servi??os de rede como se fossem diret??rios"
#: en/Extras.xml:51(para)
msgid "fwbuilder - graphical utility for building Linux and Cisco firewall rulesets"
@@ -2114,11 +2114,11 @@
#: en/Extras.xml:113(para)
msgid "Is your favorite open source application missing from Fedora Extras? Package the application as an RPM, and submit it for review to Fedora Extras. After a successful review, import it to Extras and you can maintain it there. If you don't know how to create RPM packages, there are many other ways to get involved in Fedora Extras and help drive it forward."
-msgstr "Sua aplica????o de c??digo aberto favorita est?? faltando no Fedora Extras? Empacote a aplica????o como RPM, e mande para revis??o ao Fedora Extras. Depois de uma revis??o bem sucedida, importe no Extras e voc?? poder?? mant??-lo por l??. Se voc?? n??o sabe como criar pacotes RPM, h?? muitas outras maneiras de se involver com o Fedora Extras e ajudar a incluir."
+msgstr "Sua aplica????o de c??digo aberto favorita est?? faltando no Fedora Extras? Empacote a aplica????o como RPM e mande para revis??o ao Fedora Extras. Depois de uma revis??o bem sucedida, importe no Extras e voc?? poder?? mant??-lo por l??. Se voc?? n??o sabe como criar pacotes RPM, h?? muitas outras maneiras de se envolver com o Fedora Extras e ajudar a incluir."
#: en/Extras.xml:114(para)
msgid "To learn more about how to use Fedora Extras or how to get involved, refer to http://fedoraproject.org/wiki/Extras."
-msgstr "Para aprender mais sobre o uso do Fedora Extras ou como se envolver, veja em http://fedoraproject.org/wiki/Extras."
+msgstr "Para aprender mais sobre o uso do Fedora Extras ou como se envolver, visite http://fedoraproject.org/wiki/Extras."
#: en/DevelToolsGCC.xml:8(title)
msgid "GCC Compiler Collection"
@@ -2142,7 +2142,7 @@
#: en/DevelToolsGCC.xml:20(para)
msgid "English-language diagnostic messages now use Unicode quotes. If you cannot read this, set your LC_CTYPE environment variable to C or change your terminal emulator."
-msgstr "Mensagens de diagn??stico em ingl??s agora usam Unicod. Se voc?? n??o pode l??-las, configure sua vari??vel de ambiente LC_CTYPE para C ou mude no seu emulador de terminal."
+msgstr "Mensagens de diagn??stico em ingl??s agora usam Unicod. Se voc?? n??o puder l??-las, configure sua vari??vel de ambiente LC_CTYPE para C ou mude no seu emulador de terminal."
#: en/DevelToolsGCC.xml:23(para)
msgid "The specs file is no longer installed on most systems. Ordinary users will not notice, but developers who need to alter the file can use the -dumpspecs option to generate the file for editing."
@@ -2154,7 +2154,7 @@
#: en/DevelToolsGCC.xml:31(para)
msgid "The SSA code optimizer is now included and brings with it better constant propagation, partial redundancy elimination, load and store code motion, strength reduction, dead storage elimination, better detection of unreachable code, and tail recursion by accumulation."
-msgstr "O otimizador de c??digo SSA agora ?? inclu??do e traz consigo uma melhor propaga????o constante (constant propagation), elimina????o de redund??ncia parcial (partial redundancy elimination), carrega e armazena code motion (load and store code motion), redu????o de for??a (strength reduction), elimina????o de armazenamento morto (dead storage elimination), melhor detec????o de c??digo inalcan??avel (detection of unreachable code), e recurs??o por acumula????o (tail recursion by accumulation)."
+msgstr "O otimizador de c??digo SSA agora ?? inclu??do e traz consigo uma melhor propaga????o constante (constant propagation), elimina????o de redund??ncia parcial (partial redundancy elimination), carrega e armazena code motion (load and store code motion), redu????o de for??a (strength reduction), elimina????o de armazenamento morto (dead storage elimination), melhor detec????o de c??digo inalcan??avel (detection of unreachable code) e recurs??o por acumula????o (tail recursion by accumulation)."
#: en/DevelToolsGCC.xml:34(para)
msgid "Autovectorization is supported. This technique achieves higher performance for repetitive loop code, in some circumstances."
@@ -2166,19 +2166,19 @@
#: en/DevelToolsGCC.xml:42(para)
msgid "The new sentinel attribute causes the compiler to issue a warning if a function such as execl(char *path, const char *arg, ...), which requires a NULL list terminator, is missing the NULL."
-msgstr "A nova atribui????o sentinela (sentinel) faz com que o compilador gere um aviso se uma fun????o como a execl(char *path, const char *arg, ...), que requer um terminador de lista nulo (NULL), esteja faltando o NULL."
+msgstr "A nova atribui????o sentinela (sentinel) faz com que o compilador gere um aviso se uma fun????o como a execl(char *path, const char *arg, ...), que requer um terminador de lista nulo (NULL), caso esteja faltando o NULL."
#: en/DevelToolsGCC.xml:45(para)
msgid "The cast-as-lvalue, conditional-expression-as-lvalue, and compund-expression-as-lvalue extensions have been removed."
-msgstr "As extens??es cast-as-lvalue, conditional-expression-as-lvalue, e compund-expression-as-lvalue foram removidas."
+msgstr "As extens??es cast-as-lvalue, conditional-expression-as-lvalue e compund-expression-as-lvalue foram removidas."
#: en/DevelToolsGCC.xml:48(para)
msgid "The #pragma pack() semantics are now closer to those used by other compilers."
-msgstr "A sem??ntica #pragma pack() agora est?? mais semelhante ?? usadas por outros compiladores."
+msgstr "A sem??ntica #pragma pack() agora est?? mais semelhante ??s usadas por outros compiladores."
#: en/DevelToolsGCC.xml:51(para)
msgid "Taking the address of a variable declared with the register modifier now generates an error instead of a warning."
-msgstr "Tomando o endere??o de uma vari??vel declarada no modificador de registro agora gera um erro ao inv??s de um aviso."
+msgstr "Tomar o endere??o de uma vari??vel declarada no modificador de registro agora gera um erro ao inv??s de um aviso."
#: en/DevelToolsGCC.xml:54(para)
msgid "Arrays of incomplete element types now generate an error. This implies no forward reference to structure definitions."
@@ -2259,7 +2259,7 @@
#: en/Desktop.xml:39(para)
msgid "In Fedora Core 5, only a small assortment of screensavers is installed by default. Some users find certain screensavers unpleasant, and other screensavers may abruptly terminate the graphical interface. This tends to happen more often with OpenGL animated screensavers provided within the xscreensaver-gl-extras package, when used with poorly-supported video hardware. To install these extra screensavers, run the following command:"
-msgstr "No Fedora Core 5, apenas um pequeno n??mero de protetores de tela s??o instalados por padr??o. Alguns usu??rios acham certos protetores de tela chatos, e outros protetores de tela podem terminar com a interface gr??fica de uma hora para outra. Isto geralmente tende a acontecer mais com protetores de tela animados em OpenGL fornecidos no pacote xscreensaver-gl-extras, quando usados em hardwares de v??deo com pouco suporte. Para reinstalar estes protetores de tela adicionais, execute o seguinte comando:"
+msgstr "No Fedora Core 5, apenas um pequeno n??mero de protetores de tela s??o instalados por padr??o. Alguns usu??rios acham certos protetores de tela chatos e outros protetores de tela podem terminar com a interface gr??fica de uma hora para outra. Isto geralmente tende a acontecer mais com protetores de tela animados em OpenGL fornecidos no pacote xscreensaver-gl-extras, quando usados em hardwares de v??deo com pouco suporte. Para reinstalar estes protetores de tela adicionais, execute o seguinte comando:"
#: en/Desktop.xml:40(screen)
#, no-wrap
@@ -2276,7 +2276,7 @@
#: en/DatabaseServers.xml:11(para)
msgid "Fedora now provides MySQL 5.0. For a list of the enhancements provided by this version, refer to http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html."
-msgstr "O Fedora agora fornece o MySQL 5.0.Para uma lista de aprimoramentos fornecidos por esta vers??o, veja em http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html."
+msgstr "O Fedora agora fornece o MySQL 5.0. Para uma lista de aprimoramentos fornecidos por esta vers??o, visite http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html."
#: en/DatabaseServers.xml:12(para)
msgid "For more information on upgrading databases from previous releases of MySQL, refer to the MySQL web site at http://dev.mysql.com/doc/refman/5.0/en/upgrade.html."
@@ -2288,7 +2288,7 @@
#: en/DatabaseServers.xml:16(para)
msgid "This release of Fedora includes PostgreSQL 8.1. For more information on this new version, refer to http://www.postgresql.org/docs/whatsnew/."
-msgstr "Esta vers??o do Fedora inclui o PostgreSQL 8.1. Para mais informa????es sobre esta nova vers??o, veja em http://www.postgresql.org/docs/whatsnew/."
+msgstr "Esta vers??o do Fedora inclui o PostgreSQL 8.1. Para mais informa????es sobre esta nova vers??o, visite http://www.postgresql.org/docs/whatsnew/."
#: en/DatabaseServers.xml:18(title)
msgid "Database Upgrade Across Fedora Core Versions"
@@ -2316,7 +2316,7 @@
#: en/Colophon.xml:14(para)
msgid "recognizes contributors and provides accountability, and"
-msgstr "reconhece contribuidores e fornecem seus pap??is, e"
+msgstr "reconhece contribuidores e fornece seus pap??is e"
#: en/Colophon.xml:17(para)
msgid "explains tools and production methods."
@@ -2424,7 +2424,7 @@
#: en/Colophon.xml:123(para)
msgid "Beat writers produce the release notes directly on the Fedora Project Wiki. They collaborate with other subject matter experts during the test release phase of Fedora Core to explain important changes and enhancements. The editorial team ensures consistency and quality of the finished beats, and ports the Wiki material to DocBook XML in a revision control repository. At this point, the team of translators produces other language versions of the release notes, and then they become available to the general public as part of Fedora Core. The publication team also makes them, and subsequent errata, available via the Web."
-msgstr "Os escritores de beats produzem as notas de vers??o diretamente no Wiki do Projeto Fedora. Eles colaboram com outros especialistas nos assuntos durante a fase da vers??o de testes do Fedora Core para explicar importantes mudan??as e aprimoramentos. O time editorial mant??m consist??ncia e qualidade nos beats finalizados, e porta o material Wiki para DocBook XML em um reposit??rio de controle de revis??o. Neste ponto, o time de tradutores produzem vers??es das notas de vers??o em outros idiomas, tornando-as dispon??veis para o p??blico em geral como parte do Fedora Core. O time de publica????o tamb??m produz erratas (corre????es de erros) subseq??entes, dispon??veis pela Web."
+msgstr "Os escritores de beats produzem as notas de vers??o diretamente no Wiki do Projeto Fedora. Eles colaboram com outros especialistas nos assuntos durante a fase da vers??o de testes do Fedora Core para explicar importantes mudan??as e aprimoramentos. O time editorial mant??m consist??ncia e qualidade nos beats finalizados e porta o material Wiki para DocBook XML em um reposit??rio de controle de revis??o. Neste ponto, o time de tradutores produz vers??es das notas de vers??o em outros idiomas, tornando-as dispon??veis para o p??blico em geral como parte do Fedora Core. O time de publica????o tamb??m produz erratas (corre????es de erros) subseq??entes, dispon??veis pela Web."
#: en/BackwardsCompatibility.xml:8(title)
msgid "Backwards Compatibility"
@@ -2441,7 +2441,7 @@
#: en/BackwardsCompatibility.xml:11(para)
msgid "Enter the password for the root account when prompted."
-msgstr "Digite a senha da conta de root quando pedido."
+msgstr "Digite a senha da conta de root quando solicitada."
#: en/ArchSpecificx86.xml:8(title)
msgid "x86 Specifics for Fedora"
@@ -2465,11 +2465,11 @@
#: en/ArchSpecificx86.xml:15(para)
msgid "The following CPU specifications are stated in terms of Intel processors. Other processors, such as those from AMD, Cyrix, and VIA that are compatible with and equivalent to the following Intel processors, may also be used with Fedora Core."
-msgstr "As seguintes especifica????es de CPU s??o informadas em termos de processadores Intel. Outros processadores, como os da AMD, Cyrix, e VIA que s??o compat??veis e equivalentes aos seguintes processadores Intel, tamb??m podem ser usados com o Fedora Core."
+msgstr "As seguintes especifica????es de CPU s??o informadas em termos de processadores Intel. Outros processadores, como os da AMD, Cyrix e VIA que s??o compat??veis e equivalentes aos seguintes processadores Intel, tamb??m podem ser usados com o Fedora Core."
#: en/ArchSpecificx86.xml:18(para)
msgid "Minimum: Pentium-class ??? Fedora Core 5 is optimized for Pentium 4 CPUs, but also supports earlier CPUs such as Pentium, Pentium Pro, Pentium II, Pentium III, and compatible AMD and VIA processors. Fedora takes this approach because Pentium-class optimizations actually result in reduced performance for non-Pentium class processors. In addition, scheduling for Pentium 4 processors, which make up the bulk of today's processors, is sufficiently different to warrant this change."
-msgstr "M??nimo: Classe Pentium ??? O Fedora Core 5 ?? otimizado para Processadores Pentium 4, mas tamb??m suporta processadores mais velhos como Pentium, Pentium Pro, Pentium II, Pentium III, e processadores compat??veis da AMD e VIA. O Fedora usa este esquema por as otimiza????es para a classe Pentium resultam em desempenho reduzido para processadores que n??o s??o da classe Pentium. Al??m de tudo, se programar para processadores Pentium 4, que s??o os processadores mais atuais, ?? o suficiente para garantir esta mudan??a."
+msgstr "M??nimo: Classe Pentium ??? O Fedora Core 5 ?? otimizado para Processadores Pentium 4, mas tamb??m suporta processadores mais velhos como Pentium, Pentium Pro, Pentium II, Pentium III e processadores compat??veis da AMD e VIA. O Fedora usa este esquema porque as otimiza????es para a classe Pentium resultam em desempenho reduzido para processadores que n??o s??o da classe Pentium. Al??m de tudo, se programar para processadores Pentium 4, que s??o os processadores mais atuais, ?? o suficiente para garantir esta mudan??a."
#: en/ArchSpecificx86.xml:21(para)
msgid "Recommended for text-mode: 200 MHz Pentium-class or better"
@@ -2513,7 +2513,7 @@
#: en/ArchSpecificx86.xml:47(para) en/ArchSpecificx86_64.xml:32(para) en/ArchSpecificPPC.xml:36(para)
msgid "Additional space is also required for any user data, and at least 5% free space should be maintained for proper system operation."
-msgstr "Espa??o adicional tamb??m pode ser necess??rio para dados do usu??rio, e ao menos 5% de espa??o livre deve ser mantido para uma opera????o apropriada do sistema."
+msgstr "Espa??o adicional tamb??m pode ser necess??rio para dados do usu??rio e ao menos 5% de espa??o livre deve ser mantido para uma opera????o apropriada do sistema."
#: en/ArchSpecificx86_64.xml:8(title)
msgid "x86_64 Specifics for Fedora"
@@ -2549,7 +2549,7 @@
#: en/ArchSpecificx86_64.xml:37(para)
msgid "RPM supports parallel installation of multiple architectures of the same package. A default package listing such as rpm -qa might appear to include duplicate packages, since the architecture is not displayed. Instead, use the repoquery command, part of the yum-utils package in Fedora Extras, which displays architecture by default. To install yum-utils, run the following command:"
-msgstr "O RPM suporte a instala????o paralela de m??ltiplas arquiteturas de um mesmo pacote. Um pacote padr??o listado com rpm -qa pode aparecer com pacotes duplicados, j?? que a arquitetura n??o ?? mostrada. Ao inv??s disso, use o comando repoquery, parte do pacote yum-utils no Fedora Extras, o qual mostra a arquitetura por padr??o. Para instalar o yum-utils, execute o seguinte comando:"
+msgstr "O RPM suporta a instala????o paralela de m??ltiplas arquiteturas de um mesmo pacote. Um pacote padr??o listado com rpm -qa pode aparecer com pacotes duplicados, j?? que a arquitetura n??o ?? mostrada. Ao inv??s disso, use o comando repoquery, parte do pacote yum-utils no Fedora Extras, o qual mostra a arquitetura por padr??o. Para instalar o yum-utils, execute o seguinte comando:"
#: en/ArchSpecificx86_64.xml:39(screen)
#, no-wrap
@@ -2587,11 +2587,11 @@
#: en/ArchSpecificPPC.xml:19(para)
msgid "Fedora Core 5 supports only the ???New World??? generation of Apple Power Macintosh, shipped from circa 1999 onward."
-msgstr "O Fedora Core 5 suporta paenas a gera????o ???Novo Mundo??? do Apple Power Macintosh, distribu??do a partir do circa de 1999 em diante."
+msgstr "O Fedora Core 5 suporta apenas a gera????o ???Novo Mundo??? do Apple Power Macintosh, distribu??do a partir do circa de 1999 em diante."
#: en/ArchSpecificPPC.xml:22(para)
msgid "Fedora Core 5 also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines."
-msgstr "O Fedora Core 5 tamb??m suporta m??quinas IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, e IBM Cell Broadband Engine."
+msgstr "O Fedora Core 5 tamb??m suporta m??quinas IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II e IBM Cell Broadband Engine."
#: en/ArchSpecificPPC.xml:25(para)
msgid "Recommended for text-mode: 233 MHz G3 or better, 128MiB RAM."
@@ -2611,7 +2611,7 @@
#: en/ArchSpecificPPC.xml:41(para)
msgid "The Option key on Apple systems is equivalent to the Alt key on the PC. Where documentation and the installer refer to the Alt key, use the Option key. For some key combinations you may need to use the Option key in conjunction with the Fn key, such as Option-Fn-F3 to switch to virtual terminal tty3."
-msgstr "A tecla Op????o em sistemas Apple ?? equivalente ?? tecla Alt no PC. Quando a documenta????o e o instalador se referirem a tecla Alt, use a tecla Option. Para algumas combina????es de teclas, voc?? pode precisar usar a tecla Option em conjunto com a tecla Fn, como por exemplo Option-Fn-F3 para mudar para o terminal virtual tty3."
+msgstr "A tecla Op????o em sistemas Apple ?? equivalente ?? tecla Alt no PC. Quando a documenta????o e o instalador se referirem ?? tecla Alt, use a tecla Option. Para algumas combina????es de teclas, voc?? pode precisar usar a tecla Option em conjunto com a tecla Fn, como por exemplo Option-Fn-F3 para mudar para o terminal virtual tty3."
#: en/ArchSpecificPPC.xml:44(title)
msgid "PPC Installation Notes"
@@ -2619,7 +2619,7 @@
#: en/ArchSpecificPPC.xml:45(para)
msgid "Fedora Core Installation Disc 1 is bootable on supported hardware. In addition, a bootable CD image appears in the images/ directory of this disc. These images will behave differently according to your system hardware:"
-msgstr "O Disco de Instala????o 1 do Fedora Core ?? boot??vel em hardwares que o suportam. Al??m disso, a imagem boot??vel do CD est?? no diret??rio images do disco. Estas imagens podem se comportar diferentemente de acordo com o seu hardware:"
+msgstr "O Disco de Instala????o 1 do Fedora Core ?? inicializ??vel em hardwares que o suportam. Al??m disso, a imagem inicializ??vel do CD est?? no diret??rio images do disco. Estas imagens podem se comportar diferentemente de acordo com o seu hardware:"
#: en/ArchSpecificPPC.xml:48(para)
msgid "Apple Macintosh"
@@ -2627,7 +2627,7 @@
#: en/ArchSpecificPPC.xml:49(para)
msgid "The bootloader should automatically boot the appropriate 32-bit or 64-bit installer."
-msgstr "O carregador de boot deve fazer o boot automaticamente para o instalador apropriado (de 32-bits ou 64-bits)."
+msgstr "O carregador de inicializa????o deve fazer a inicializa????o automaticamente para o instalador apropriado (de 32-bits ou 64-bits)."
#: en/ArchSpecificPPC.xml:50(para)
msgid "The default gnome-power-manager package includes power management support, including sleep and backlight level management. Users with more complex requirements can use the apmud package in Fedora Extras. Following installation, you can install apmud with the following command:"
@@ -2640,27 +2640,27 @@
#: en/ArchSpecificPPC.xml:54(para)
msgid "64-bit IBM eServer pSeries (POWER4/POWER5)"
-msgstr "IBM eServer pSeries de 64-bits (POWER4/POWER5)"
+msgstr "IBM eServer pSeries de 64-bits (POWER4/POWER5)."
#: en/ArchSpecificPPC.xml:55(para)
msgid "After using OpenFirmware to boot the CD, the bootloader (yaboot) should automatically boot the 64-bit installer."
-msgstr "Depois de usar o OpenFirmware para dar boot pelo CD, o carregador de boot (yaboot) deve automaticamente iniciar o instalador de 64-bits."
+msgstr "Depois de usar o OpenFirmware para inicializar pelo CD, o carregador de inicializa????o (yaboot) deve automaticamente iniciar o instalador de 64-bits."
#: en/ArchSpecificPPC.xml:58(para)
msgid "32-bit CHRP (IBM RS/6000 and others)"
-msgstr "CHRP de 32-bits (IBM RS/6000 e outros)"
+msgstr "CHRP de 32-bits (IBM RS/6000 e outros). "
#: en/ArchSpecificPPC.xml:59(para)
msgid "After using OpenFirmware to boot the CD, select the linux32 boot image at the boot: prompt to start the 32-bit installer. Otherwise, the 64-bit installer starts, which does not work."
-msgstr "Depois de usar o OpenFirmware para dar boot pelo CD, selecione a imagem de boot linux32 no prompt boot: para iniciar o instalador de 32-bits. Caso contr??rio, o instalador de 64-bits inicia, e n??o funciona."
+msgstr "Depois de usar o OpenFirmware para inicializar pelo CD, selecione a imagem de inicializa????o linux32 no prompt boot: para iniciar o instalador de 32-bits. Caso contr??rio, o instalador de 64-bits inicia e n??o funciona."
#: en/ArchSpecificPPC.xml:62(para)
msgid "Genesi Pegasos II"
-msgstr "Genesi Pegasos II"
+msgstr "Genesi Pegasos II. "
#: en/ArchSpecificPPC.xml:63(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 OpenFirmware prompt, enter the command:"
-msgstr "Nesta ??poca, firmware com suporte total para sistemas de arquivos ISO9660 ainda n??o foi lan??ado para o Pegasos. Entretanto, voc?? pode usar uma imagem de boot pela rede. No prompt do OpenFirmware, digite o comando:"
+msgstr "Nesta ??poca, firmware com suporte total para sistemas de arquivos ISO9660 ainda n??o foi lan??ado para o Pegasos. Entretanto, voc?? pode usar uma imagem de inicializa????o pela rede. No prompt do OpenFirmware, digite o comando:"
#: en/ArchSpecificPPC.xml:64(screen)
#, no-wrap
@@ -2669,19 +2669,19 @@
#: en/ArchSpecificPPC.xml:65(para)
msgid "You must also configure OpenFirmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, set the boot-device and boot-file environment variables appropriately."
-msgstr "Voc?? tamb??m pode configurar o OpenFirmware no Pegasos para tornar o sistema do Fedora Core boot??vel manualmente. Para fazer isto, use as vari??veis de ambiente boot-device e boot-file apropriadamente."
+msgstr "Voc?? tamb??m pode configurar o OpenFirmware no Pegasos para tornar o sistema do Fedora Core inicializ??vel manualmente. Para fazer isto, use as vari??veis de ambiente boot-device e boot-file apropriadamente."
#: en/ArchSpecificPPC.xml:68(para)
msgid "Network booting"
-msgstr "Boot pela Rede"
+msgstr "Inicializa????o pela Rede. "
#: en/ArchSpecificPPC.xml:69(para)
msgid "You can find combined images containing the installer kernel and ramdisk in the images/netboot/ directory of the installation tree. These are intended for network booting with TFTP, but can be used in many ways."
-msgstr "Voc?? pode encontrar imagens combinadas contendo o kernel do instalador e o ramdisk no diret??rio images/netboot/ da ??rvore de instala????o. Estes t??m como objetivo o boot pela rede via TFTP, mas podem ser usados de muitas maneiras."
+msgstr "Voc?? pode encontrar imagens combinadas contendo o kernel do instalador e o ramdisk no diret??rio images/netboot/ da ??rvore de instala????o. Estes t??m como objetivo a inicializa????o pela rede via TFTP, mas podem ser usados de muitas maneiras."
#: en/ArchSpecificPPC.xml:70(para)
msgid "yaboot supports TFTP booting for IBM eServer pSeries and Apple Macintosh. The Fedora Project encourages the use of yaboot over the netboot images."
-msgstr "O yaboot suporte boot via TFTP para IBM eServer pSeries e Apple Macintosh. O Projeto Fedora encoraja o uso do yaboot ao inv??s das imagens netboot."
+msgstr "O yaboot suporta inicializa????o via TFTP para IBM eServer pSeries e Apple Macintosh. O Projeto Fedora encoraja o uso do yaboot ao inv??s das imagens netboot."
#: en/ArchSpecific.xml:8(title)
msgid "Architecture Specific Notes"
From fedora-docs-commits at redhat.com Mon Mar 6 02:14:32 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun, 5 Mar 2006 21:14:32 -0500
Subject: docs-common/common/entities Makefile, 1.15, 1.16 entities-de.ent,
1.3, 1.4 entities-en.ent, 1.6, 1.7 entities-en_US.ent, 1.3,
1.4 entities-it.ent, 1.13, 1.14 entities-pt_BR.ent, 1.6,
1.7 entities-ru.ent, 1.5, 1.6 entities-zh_CN.ent, 1.5,
1.6 entities.pot, 1.5, 1.6 it.po, 1.12, 1.13
Message-ID: <200603060214.k262EXBX028563@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/common/entities
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28496/docs-common/common/entities
Modified Files:
Makefile entities-de.ent entities-en.ent entities-en_US.ent
entities-it.ent entities-pt_BR.ent entities-ru.ent
entities-zh_CN.ent entities.pot it.po
Log Message:
Translatable entities: a reality!
Index: Makefile
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/Makefile,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- Makefile 3 Mar 2006 23:24:59 -0000 1.15
+++ Makefile 6 Mar 2006 02:14:22 -0000 1.16
@@ -32,7 +32,7 @@
#######################################################################
# FDPCOMMONDIR:=$(shell cd .. && /bin/pwd)
-FDPCOMMONDIR:=../docs-common/common
+FDPCOMMONDIR:=../../docs-common/common
#######################################################################
#######################################################################
Index: entities-de.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-de.ent,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- entities-de.ent 3 Mar 2006 23:24:59 -0000 1.3
+++ entities-de.ent 6 Mar 2006 02:14:22 -0000 1.4
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-en.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-en.ent,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- entities-en.ent 3 Mar 2006 23:24:59 -0000 1.6
+++ entities-en.ent 6 Mar 2006 02:14:22 -0000 1.7
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-en_US.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-en_US.ent,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- entities-en_US.ent 3 Mar 2006 23:24:59 -0000 1.3
+++ entities-en_US.ent 6 Mar 2006 02:14:22 -0000 1.4
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-it.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-it.ent,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- entities-it.ent 4 Mar 2006 10:33:59 -0000 1.13
+++ entities-it.ent 6 Mar 2006 02:14:22 -0000 1.14
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-pt_BR.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-pt_BR.ent,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- entities-pt_BR.ent 3 Mar 2006 23:24:59 -0000 1.6
+++ entities-pt_BR.ent 6 Mar 2006 02:14:22 -0000 1.7
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-ru.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-ru.ent,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- entities-ru.ent 3 Mar 2006 23:24:59 -0000 1.5
+++ entities-ru.ent 6 Mar 2006 02:14:22 -0000 1.6
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities-zh_CN.ent
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities-zh_CN.ent,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- entities-zh_CN.ent 3 Mar 2006 23:24:59 -0000 1.5
+++ entities-zh_CN.ent 6 Mar 2006 02:14:22 -0000 1.6
@@ -1,5 +1,5 @@
-
+
@@ -41,13 +41,13 @@
-
-
-
-
-
-
-
+
+
+
+
+
+
+
Index: entities.pot
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/entities.pot,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- entities.pot 3 Mar 2006 23:24:59 -0000 1.5
+++ entities.pot 6 Mar 2006 02:14:22 -0000 1.6
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-03-03 17:24-0600\n"
+"POT-Creation-Date: 2006-03-05 18:07-0600\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
Index: it.po
===================================================================
RCS file: /cvs/docs/docs-common/common/entities/it.po,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- it.po 4 Mar 2006 10:33:59 -0000 1.12
+++ it.po 6 Mar 2006 02:14:22 -0000 1.13
@@ -3,7 +3,7 @@
msgid ""
msgstr ""
"Project-Id-Version: it\n"
-"POT-Creation-Date: 2006-02-27 22:09-0600\n"
+"POT-Creation-Date: 2006-03-05 18:07-0600\n"
"PO-Revision-Date: 2006-03-04 11:08+0100\n"
"Last-Translator: Francesco Tombolini \n"
"Language-Team: Italiano \n"
@@ -13,220 +13,231 @@
"X-Generator: KBabel 1.11.1\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
-#: entities-en.xml:6(title)
-msgid "These common entities are useful shorthand terms and names, which may be subject to change at anytime. This is an important value the the entity provides: a single location to update terms and common names."
-msgstr "Queste entit?? comuni sono utili abbreviazioni di termini e nomi, che potrebbero essere soggette a cambiamento in qualsiasi momento. Questo ?? il valore importante che le entit?? forniscono: Una singola locazione per aggiornare termini e nomi comuni."
+#: entities-en_US.xml:4(title)
+msgid ""
+"These common entities are useful shorthand terms and names, which may be "
+"subject to change at anytime. This is an important value the the entity "
+"provides: a single location to update terms and common names."
+msgstr ""
+"Queste entit?? comuni sono utili abbreviazioni di termini e nomi, che "
+"potrebbero essere soggette a cambiamento in qualsiasi momento. Questo ?? il "
+"valore importante che le entit?? forniscono: Una singola locazione per "
+"aggiornare termini e nomi comuni."
-#: entities-en.xml:14(comment) entities-en.xml:18(comment)
+#: entities-en_US.xml:7(comment) entities-en_US.xml:11(comment)
msgid "Generic root term"
msgstr "Termine generico principale"
-#: entities-en.xml:15(text)
+#: entities-en_US.xml:8(text)
msgid "Fedora"
msgstr "Fedora"
-#: entities-en.xml:19(text)
+#: entities-en_US.xml:12(text)
msgid "Core"
msgstr "Core"
-#: entities-en.xml:22(comment)
+#: entities-en_US.xml:15(comment)
msgid "Generic main project name"
msgstr "Nome generico del progetto principale"
-#: entities-en.xml:26(comment)
+#: entities-en_US.xml:19(comment)
msgid "Legacy Entity"
msgstr "Entit?? obsolete"
-#: entities-en.xml:30(comment)
+#: entities-en_US.xml:23(comment)
msgid "Short project name"
msgstr "Nome breve del progetto"
-#: entities-en.xml:31(text)
+#: entities-en_US.xml:24(text)
msgid "FC"
msgstr "FC"
-#: entities-en.xml:34(comment)
+#: entities-en_US.xml:27(comment)
msgid "Generic overall project name"
msgstr "Nome generico del progetto complessivo"
-#: entities-en.xml:35(text)
+#: entities-en_US.xml:28(text)
msgid "
-
- Click Forward to proceed to the login screen.
- Your &FC; system is now ready for use.
-
-
-
- Update Your System
-
- To ensure the security of your system, run a package update
- after the installation completes.
- explains how to update your
- &FED; system.
-
-
+
+-->
+ Updated to match Rawhide.
+
- Updated First Boot section.
+ Updated First Boot section.
From fedora-docs-commits at redhat.com Sun Mar 12 19:55:00 2006
From: fedora-docs-commits at redhat.com (Amanpreet Singh Brar (apbrar))
Date: Sun, 12 Mar 2006 14:55:00 -0500
Subject: release-notes/po pa.po,1.2,1.3
Message-ID: <200603121955.k2CJt0Y9020311@cvs-int.fedora.redhat.com>
Author: apbrar
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20293
Modified Files:
pa.po
Log Message:
update for Punjabi
Index: pa.po
===================================================================
RCS file: /cvs/docs/release-notes/po/pa.po,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- pa.po 1 Mar 2006 12:03:01 -0000 1.2
+++ pa.po 12 Mar 2006 19:54:53 -0000 1.3
@@ -1,16 +1,19 @@
+# translation of fedora-pa.po to Punjabi
# translation of pa.po to Punjabi
# Amanpreet Singh Alam , 2006.
+# Jaswinder Singh Phulewala , 2006.
msgid ""
msgstr ""
-"Project-Id-Version: pa\n"
+"Project-Id-Version: fedora-pa\n"
"POT-Creation-Date: 2006-02-22 05:54-0600\n"
-"PO-Revision-Date: 2006-03-01 17:30+0530\n"
-"Last-Translator: Amanpreet Singh Alam \n"
+"PO-Revision-Date: 2006-03-13 01:12+0530\n"
+"Last-Translator: Jaswinder Singh Phulewala \n"
"Language-Team: Punjabi \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.9.1\n"
+"Plural-Forms: Plural-Forms: nplurals=2; plural=(n != 1);\n\n"
#: en/Xorg.xml:5(title) en/Welcome.xml:5(title) en/WebServers.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/PackageNotesJava.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/ArchSpecificx86.xml:5(title) en/ArchSpecificx86_64.xml:5(title) en/ArchSpecificPPC.xml:5(title) en/ArchSpecific.xml:5(title)
msgid "Temp"
@@ -30,7 +33,7 @@
#: en/Xorg.xml:12(para)
msgid "X.org X11 is an open source implementation of the X Window System. It provides the basic low level functionality which full fledged graphical user interfaces (GUIs) such as GNOME and KDE are designed upon."
-msgstr ""
+msgstr "X.org X11 X ??????????????? ??????????????? ?????? ????????? ????????? ???????????? ?????????????????? ????????? ?????? ??????????????? ??????????????? ???????????? ?????? ?????????????????????????????? ?????????????????? ???????????? ?????? ?????? ???????????? ???????????? ???????????? ????????????????????? ?????????????????? ????????????????????? (GUIs) ?????? ??????????????? ???????????? ????????? ?????? ?????? ??? ???????????? ?????? ?????????"
#: en/Xorg.xml:13(para)
msgid "For more information about Xorg refer to http://xorg.freedesktop.org/wiki/"
@@ -38,7 +41,7 @@
#: en/Xorg.xml:15(para)
msgid "You can use Applications => System Settings => Display or system-config-display to configure the settings. The configuration file for Xorg is located in /etc/X11/xorg.conf"
-msgstr ""
+msgstr "??????????????? ??????????????????????????? ?????????????????? ????????? ?????? ???????????? => ??????????????? ?????????????????? => ???????????? ????????? system-config-display ????????? ???????????? ????????? Xorg ?????? ?????????????????? ???????????? /etc/X11/xorg.conf ???????????? ?????????"
#: en/Xorg.xml:16(para)
msgid "Modular X.Org X11R7 RC2 was released into Fedora development (rawhide) on November 16, 2005. This is the first modular release of Xorg which among several other benefits, enable users to receive updates in a faster pace and helps developers to develop and release specific components in a rapid fashion."
@@ -46,7 +49,7 @@
#: en/Xorg.xml:17(para)
msgid "More information on the current status of the Xorg modularization effort in Fedora is available from http://fedoraproject.org/wiki/Xorg/Modularization"
-msgstr ""
+msgstr "?????????????????? ???????????? Xorg ???????????????????????????????????? ?????????????????? ?????? ?????????????????? ??????????????? ?????? ??????????????? ????????????????????? http://fedoraproject.org/wiki/Xorg/Modularization ?????? ?????????????????? ?????????"
#: en/Xorg.xml:21(title)
msgid "Xorg X11R7.0 Developer Notes"
@@ -78,7 +81,7 @@
#: en/Xorg.xml:33(para)
msgid "The system app-defaults directory for X resources, is now \"%{_datadir}/X11/app-defaults\", which expands to /usr/share/X11/app-defaults on Fedora Core 5 and for future Red Hat Enterprise Linux systems."
-msgstr ""
+msgstr "X ?????????????????? ?????? ??????????????? app-defaults ???????????????????????????, ????????? \"%{_datadir}/X11/app-defaults\" ??????, ?????? ?????????????????? ????????? 5 ????????? ????????? ???????????? ???????????? ????????? ??????????????????????????? ??????????????? ???????????? /usr/share/X11/app-defaults ?????? ?????? ?????????"
#: en/Xorg.xml:36(title)
msgid "xft-config Can't Be Found"
@@ -86,7 +89,7 @@
#: en/Xorg.xml:37(para)
msgid "Modular X now uses GNU autotools, and pkg-config for its buildsystem configuration, etc. xft-config has been deprecated for 2-3 years now, and pkgconfig *.pc files have been provided for most of this time. Applications which previously used xft-config to obtain the Cflags or libs options for building with, must now be updated to use pkg-config."
-msgstr ""
+msgstr "?????????????????? X ????????? ???????????? ??????????????????????????? ?????????????????? ????????? ?????? GNU ?????????-????????????, ????????? pkg-config ??????????????? ????????? xft-config ????????? 2-3 ??????????????? ?????? ??????-???????????? ???????????? ??????, ????????? pkgconfig *.pc ?????????????????? ?????? ???????????? ?????????????????? ?????????????????? ???????????? ????????? ???????????? ?????? ???????????? ????????? ?????? ?????????????????? Cflags ????????? libs xft-config ??????????????? ??????, ?????? pkg-config ????????? ???????????? ?????? ???????????????????????? ???????????? ??????????????? ?????????"
#: en/Xorg.xml:41(title)
msgid "Xorg X11R7 Developer Overview"
@@ -94,15 +97,15 @@
#: en/Xorg.xml:42(para)
msgid "Here is a short list of some of the more developer/package visible changes that are present in X11R7:"
-msgstr ""
+msgstr "???????????? ??????????????? ???????????????????????????/????????????????????? ????????????????????? ???????????????????????? ?????? ???????????? ???????????? ?????? ?????? X11R7 ???????????? ???????????? ??????:"
#: en/Xorg.xml:45(para)
msgid "The entire buildsystem has changed from \"Imake\" to the GNU autotools collection."
-msgstr ""
+msgstr "???????????? ??????????????? ??????????????? \"Imake\" ????????? ?????? ?????? GNU ?????????-???????????? ????????????????????? ????????? ??????????????? ???????????? ?????????"
#: en/Xorg.xml:48(para)
msgid "All of the libraries now install pkgconfig *.pc files, which should now always be used by software that depends on these libraries, instead of hard coding paths to them in /usr/X11R6/lib or elsewhere."
-msgstr ""
+msgstr "????????? ?????? ?????????????????????????????? pkgconfig *.pc ?????????????????? ?????????????????? ?????????????????? ??????, ?????? ??????????????? ?????? ?????????????????????????????? ?????? ???????????? ?????????????????????????????? ?????? ??????????????? ??????, ??????????????? ??????????????? ???????????? ?????????????????? ????????????????????????, ???????????? ??????????????? ????????? /usr/X11R6/lib ???????????? ????????? ???????????? ????????? ???????????? ?????????????????? ???????????? ???????????? ?????????"
#: en/Xorg.xml:51(para)
msgid "Everything is now installed directly into /usr instead of /usr/X11R6. All software which hard codes paths to anything in /usr/X11R6, must now be changed preferably to dynamically detect the proper location of the object, or to hard code the new paths that X11R7 uses by default. It is strongly advised to use autodetection methods than to hard code paths."
@@ -122,7 +125,7 @@
#: en/Welcome.xml:11(para)
msgid "This is a test release and is provided for developers and testers to participate and provide feedback. It is not meant for end users."
-msgstr ""
+msgstr "?????? ???????????? ??????????????? ?????? ????????? ????????????????????????????????? ????????? ??????????????????????????? ?????? ?????????????????? ?????? ?????????????????? ????????? ?????? ?????????????????? ???????????? ????????? ?????? ??????????????? ???????????????????????? ?????? ???????????? ?????????"
#: en/Welcome.xml:14(title)
msgid "Join the Community for More Information"
@@ -142,7 +145,7 @@
#: en/Welcome.xml:21(para)
msgid "These release notes may be updated. Visit http://fedora.redhat.com/docs/release-notes/ to view the latest release notes for Fedora Core ."
-msgstr ""
+msgstr "?????? ??????????????? ??????????????? ?????????????????? ???????????? ?????? ???????????? ????????? ?????????????????? ????????? ?????? ???????????? ??????????????? ??????????????? ???????????? ?????? http://fedora.redhat.com/docs/release-notes/ ???????????????"
#: en/Welcome.xml:23(para)
msgid "Refer to these webpages to find out more information about Fedora:"
@@ -186,47 +189,47 @@
#: en/WebServers.xml:12(para)
msgid "Version 2.2 of the Apache HTTP Server is now included in Fedora Core. This release brings a number of improvements since the 2.0 series, including:"
-msgstr ""
+msgstr "??????????????? HTTP ???????????? ?????? ???????????? 2.2 ????????? ?????????????????? ????????? ???????????? ???????????? ????????? ?????? ??????????????? ???????????? 2.0 ????????? ????????? ?????? ?????? ???????????? ?????????????????? ??????????????? ???????????? ??????:"
#: en/WebServers.xml:15(para)
msgid "greatly improved caching modules (mod_cache, mod_disk_cache, mod_mem_cache)"
-msgstr ""
+msgstr "??????????????? ????????? ???????????? ?????????????????? ?????????????????? (mod_cache, mod_disk_cache, mod_mem_cache)"
#: en/WebServers.xml:18(para)
msgid "refactored authentication and authorization support"
-msgstr ""
+msgstr "?????????-??????????????? ?????????????????????????????? ????????? ?????????????????? ??????????????????"
#: en/WebServers.xml:21(para)
msgid "support for proxy load balancing (mod_proxy_balance)"
-msgstr ""
+msgstr "?????????????????? ????????? ?????????????????? ?????? ?????????????????? (mod_proxy_balance)"
#: en/WebServers.xml:24(para)
msgid "large file support for 32-bit platforms (including support for >2Gb request bodies)"
-msgstr ""
+msgstr "32-???????????? ?????????????????????????????? ?????? ???????????? ???????????? ??????????????? ?????????????????? (>2Gb ??????????????? ????????? ?????????????????? ?????? ?????????????????? ????????????)"
#: en/WebServers.xml:27(para)
msgid "new modules mod_dbd and mod_filter bring SQL database support and enhanced filtering"
-msgstr ""
+msgstr "???????????? ?????????????????? mod_dbd ????????? mod_filter SQL ????????????????????? ?????????????????? ????????? ?????????????????? ???????????????????????? ???????????? ??????"
#: en/WebServers.xml:30(para)
msgid "The following changes have been made to the default httpd configuration:"
-msgstr ""
+msgstr "????????????????????? ???????????????????????? ????????? ?????????????????? ?????? httpd ??????????????????:"
#: en/WebServers.xml:33(para)
msgid "the mod_cern_meta and mod_asis modules are no longer loaded by default"
-msgstr ""
+msgstr "mod_cern_meta ????????? mod_asis ?????????????????? ????????? ????????? ????????? ???????????? ??????????????? ???????????? ????????? ???????????? ???????????????"
#: en/WebServers.xml:36(para)
msgid "the mod_ext_filter module is now loaded by default"
-msgstr ""
+msgstr "mod_ext_filter ?????????????????? ????????? ????????? ???????????? ????????? ???????????? ??????"
#: en/WebServers.xml:39(para)
msgid "Any third-party modules compiled for httpd 2.0 must be rebuilt for httpd 2.2."
-msgstr ""
+msgstr "????????? ???????????? ??????????????? ?????????????????? ?????? httpd 2.0 ?????? ?????????????????? ???????????? ??????, ????????? httpd 2.2 ?????? ????????? ??????????????? ?????? ???????????? ?????????"
#: en/WebServers.xml:40(para)
msgid "Any existing configuration files might need adapting for 2.2. For more information, refer to http://httpd.apache.org/docs/2.2/upgrading.html."
-msgstr ""
+msgstr "????????? ?????????????????? ?????????????????? ???????????? ?????? 2.2 ????????? ?????????????????? ????????? ?????? ????????? ?????? ???????????? ????????? ??????????????? ????????????????????? ??????, http://httpd.apache.org/docs/2.2/upgrading.html???????????????"
#: en/WebServers.xml:46(title)
msgid "php"
@@ -234,7 +237,7 @@
#: en/WebServers.xml:47(para)
msgid "Version 5.1 of PHP is now included in Fedora Core. This release brings a number of improvements since PHP 5.0, including:"
-msgstr ""
+msgstr "PHP ?????? ???????????? 5.1 ????????? ?????????????????? ????????? ???????????? ???????????? ????????? ?????? ??????????????? ???????????? PHP 5.0 ????????? ?????? ?????? ?????? ?????????????????? ??????????????? ???????????? ??????, ???????????????:"
#: en/WebServers.xml:50(para)
msgid "improved performance"
@@ -242,27 +245,27 @@
#: en/WebServers.xml:53(para)
msgid "addition of the PDO database abstraction module"
-msgstr ""
+msgstr "PDO ????????????????????? ??????????????????????????? ?????????????????? ?????? ?????????????????????"
#: en/WebServers.xml:56(para)
msgid "The following extension modules have been added:"
-msgstr ""
+msgstr "??????????????? ???????????????????????? ?????????????????? ???????????? ???????????? ?????? ??????:"
#: en/WebServers.xml:59(para)
msgid "date, hash, and Reflection (built-in with the php package)"
-msgstr ""
+msgstr "date, hash, ????????? Reflection (php ??????????????? ??????????????? ????????????)"
#: en/WebServers.xml:63(para)
msgid "pdo and pdo_psqlite (in the php-pdo package)"
-msgstr ""
+msgstr "pdo ????????? pdo_psqlite (php-pdo ??????????????? ????????????)"
#: en/WebServers.xml:67(para)
msgid "pdo_mysql (in the php-mysql package)"
-msgstr ""
+msgstr "pdo_mysql (php-mysql ??????????????? ????????????)"
#: en/WebServers.xml:71(para)
msgid "pdo_pgsql (in the php-pgsql package)"
-msgstr ""
+msgstr "pdo_pgsql (php-pgsql ??????????????? ????????????)"
#: en/WebServers.xml:75(para)
msgid "pdo_odbc (in the php-odbc package)"
@@ -270,7 +273,7 @@
#: en/WebServers.xml:79(para)
msgid "xmlreader and xmlwriter (in the php-xml package)"
-msgstr ""
+msgstr "xmlreader ????????? xmlwriter (php-xml ??????????????? ????????????)"
#: en/WebServers.xml:83(para)
msgid "The following extension modules are no longer built:"
@@ -294,7 +297,7 @@
#: en/WebServers.xml:103(para)
msgid "The PEAR framework is now packaged in the php-pear package; only the following PEAR components are included in Fedora Core:"
-msgstr ""
+msgstr "PEAR ????????????????????? ????????? php-pear ??????????????? ???????????? ???????????? ???????????? ??????; ???????????? ??????????????? PEAR ??????????????? ?????????????????? ????????? ???????????? ???????????? ???????????? ??????:"
#: en/WebServers.xml:107(command)
msgid "Archive_Tar"
@@ -330,7 +333,7 @@
#: en/ServerTools.xml:9(para)
msgid "This section highlights changes and additions to the various GUI server and system configuration tools in Fedora Core."
-msgstr ""
+msgstr "?????? ????????? ???????????? ?????????????????? ????????? ??????????????? ?????????-????????? GUI ???????????? ????????? ??????????????? ????????????????????? ?????????????????? ?????? ???????????????????????? ????????? ??????????????? ??????????????? ????????????????????? ???????????? ?????????"
#: en/ServerTools.xml:11(title)
msgid "system-config-printer"
@@ -338,19 +341,19 @@
#: en/ServerTools.xml:13(title)
msgid "SMB Browsing Outside Local Network"
-msgstr ""
+msgstr "SMB ???????????? ????????????????????? ?????? ?????????????????? ????????? ???????????? ??????"
#: en/ServerTools.xml:14(para)
msgid "Browsing for Samba print shares across subnets is now possible. In addition, if at least one WINS server has been specified in /etc/samba/smb.conf, the first address specified is used when browsing."
-msgstr ""
+msgstr "??????-???????????? ??????????????? ??????????????? ??????????????? ???????????? ?????? ????????? ????????? ???????????? ????????? ????????? ??????, ?????? ????????????-????????? ????????? WINS ???????????? /etc/samba/smb.conf ???????????? ?????????????????? ??????, ????????? ?????????????????? ????????? ??????????????? ???????????????????????? ????????? ???????????? ??????????????? ??????????????? ?????????"
#: en/ServerTools.xml:17(title)
msgid "Kerberos Support for SMB Printers"
-msgstr ""
+msgstr "SMB ???????????????????????? ?????? ?????????????????? ??????????????????"
#: en/ServerTools.xml:18(para)
msgid "The system-config-printer application supports Kerberos authentication when adding a new SMB printer. To add the printer, the user must possess a valid Kerberos ticket and /usr/sbin/printconf-gui must be launched via sudo. No username and password is stored in /etc/cups/printers.conf. Printing is still possible if the SMB print queue permits anonymous printing."
-msgstr ""
+msgstr "system-config-printer ???????????? ???????????? SMB ?????????????????? ???????????? ????????? ???????????? ?????????????????? ??????????????????????????? ????????? ?????????????????? ??????????????? ????????? ?????????????????? ???????????? ????????? ??????, ?????????????????? ????????? ????????? ?????????????????? ???????????? ???????????? ??????????????? ?????? ????????? /usr/sbin/printconf-gui ????????? sudo ??????????????? ?????????????????? ??????????????? ????????? ????????? ?????????????????? ????????? ????????? ????????????-????????? /etc/cups/printers.conf ???????????? ????????????????????? ???????????? ??????????????? ????????? ???????????????????????? ???????????? ?????? ???????????? ?????? ?????? SMB ??????????????? ???????????? ??????????????? ???????????????????????? ?????? ?????????????????? ??????????????? ?????????"
#: en/ServerTools.xml:22(title)
msgid "system-config-securitylevel"
@@ -358,11 +361,11 @@
#: en/ServerTools.xml:24(title)
msgid "Trusted Service Additions"
-msgstr ""
+msgstr "????????????????????? ???????????? ?????????????????????"
#: en/ServerTools.xml:25(para)
msgid "Samba is now listed in the \"Trusted services\" list and can thus be enabled to permit the firewall to pass SMB traffic."
-msgstr ""
+msgstr "??????????????? ????????? \"????????????????????? ?????????????????????\" ???????????? ???????????? ?????????????????? ?????? ????????? ????????????????????? ??????????????? SMB ???????????? ???????????? ?????? ?????????????????? ?????? ????????? ???????????? ?????? ???????????? ?????????"
#: en/ServerTools.xml:28(title)
msgid "Port Ranges"
@@ -370,7 +373,7 @@
#: en/ServerTools.xml:29(para)
msgid "When defining \"Other Ports\" in the system-config-securitylevel tool, port ranges can now be specified. For example, specifying \"6881-6999:tcp\" results in the addition of the following line to /etc/sysconfig/iptables:"
-msgstr ""
+msgstr "system-config-securitylevel ???????????? ???????????? \"????????? ????????????\" ???????????????????????? ????????? ????????????, ???????????? ???????????? ????????? ??????????????? ?????? ???????????? ????????? ?????????????????? ????????????, \"6881-6999:tcp\" ?????????????????? ????????? ??????????????? ????????? /etc/sysconfig/iptables ???????????? ???????????? ?????? ??????????????????:"
#: en/ServerTools.xml:30(screen)
#, no-wrap
@@ -383,11 +386,11 @@
#: en/SecuritySELinux.xml:9(para)
msgid "The new SELinux project pages have troubleshooting tips, explanations, and pointers to documentation and references:"
-msgstr ""
+msgstr "???????????? SELinux ????????????????????? ????????? ???????????? ?????????????????? ????????????????????? ????????????????????????, ??????????????????, ????????? ??????????????????????????? ????????? ????????????????????? ?????? ??????????????? ???????????? ??????:"
#: en/SecuritySELinux.xml:12(para)
msgid "New SELinux project pages:"
-msgstr ""
+msgstr "???????????? SELinux ????????????????????? ?????????:"
#: en/SecuritySELinux.xml:16(ulink)
msgid "http://fedoraproject.org/wiki/SELinux"
@@ -411,7 +414,7 @@
#: en/SecuritySELinux.xml:42(para)
msgid "Looking for a list of SELinux commands?"
-msgstr ""
+msgstr "SELinux ?????????????????? ?????? ???????????? ?????? ????????? ???????????? ???????"
#: en/SecuritySELinux.xml:46(ulink)
msgid "http://fedoraproject.org/wiki/SELinux/Commands"
@@ -419,7 +422,7 @@
#: en/SecuritySELinux.xml:52(para)
msgid "Want to know which domains are confined?"
-msgstr ""
+msgstr "??????????????? ????????????????????? ?????? ?????? ??????????????? ??????????????? ????????????????????? ???????"
#: en/SecuritySELinux.xml:56(ulink)
msgid "http://fedoraproject.org/wiki/SELinux/Domains"
@@ -431,11 +434,11 @@
#: en/SecuritySELinux.xml:64(para)
msgid "General use implementation of the more stringent Multilevel Security (MLS). MCS is an enhancement to SELinux to allow users to label files with categories. For example, Company_Confidential, CEO_EYES_ONLY, or Sysadmin_Passwords."
-msgstr ""
+msgstr "??????????????? ????????? ????????????-???????????? ????????????????????? (MLS) ?????? ?????? ??????????????? ?????? ????????????????????? MCS SELinux ?????? ????????? ????????? ?????? ?????? ???????????????????????? ????????? ?????????????????? ?????? ????????? ????????? ???????????? ???????????? ?????? ?????????????????? ??????????????? ????????? ?????????????????? ??????, Company_Confidential, CEO_EYES_ONLY, ????????? Sysadmin_Passwords???"
#: en/SecuritySELinux.xml:65(para)
msgid "For more information, you can read this article from the creator of MCS:"
-msgstr ""
+msgstr "??????????????? ????????????????????? ??????, ??????????????? ?????? ????????? MCS ?????? ????????????????????? ????????? ?????? ???????????? ??????:"
#: en/SecuritySELinux.xml:67(ulink)
msgid "http://james-morris.livejournal.com/5583.html"
@@ -447,7 +450,7 @@
#: en/SecuritySELinux.xml:71(para)
msgid "A specific Mandatory Access Control (MAC) scheme that labels processes and objects with special security levels. For example, an object (a document file) can have the security level of { Secret, ProjectMeta }, where Secret is the sensitivity level, and the ProjectMeta is the category."
-msgstr ""
+msgstr "????????? ????????? ????????????????????? ?????????????????? ?????????????????? (MAC) ???????????? ?????? ?????????????????? ????????? ???????????????????????? ?????? ????????? ????????????????????? ?????????????????? ????????? ???????????? ?????????????????? ????????? ?????????????????? ????????????, ????????? ?????????????????? (????????? ????????????????????? ????????????) ?????? { Secret, ProjectMeta } ?????? ????????????????????? ???????????? ?????? ???????????? ??????, ??????????????? Secret ??????????????????????????? ???????????? ??????, ????????? ProjectMeta ????????? ?????????"
#: en/SecuritySELinux.xml:72(para)
msgid "Refer to this technical article for more information:"
@@ -471,7 +474,7 @@
#: en/Security.xml:12(para)
msgid "General introduction to the many proactive security features in Fedora, current status and policies is available from this page:"
-msgstr ""
+msgstr "?????????????????? ????????? ????????????????????? ??????????????????-???????????? ????????????????????? ?????????????????????????????? ?????? ?????? ?????????????????????, ?????????????????? ??????????????? ????????? ?????????????????? ?????? ????????? ?????? ?????????????????? ??????:"
#: en/Security.xml:14(ulink)
msgid "http://fedoraproject.org/wiki/Security"
@@ -495,7 +498,7 @@
#: en/Security.xml:25(title)
msgid "Upgraded installations using older PAM stacks need manual intervention"
-msgstr ""
+msgstr "PAM ???????????? ????????? ?????? ?????????????????????????????? ??????????????????????????? ????????? ????????????????????? ?????? ????????? ??????"
#: en/Security.xml:26(para)
msgid "When a system is upgraded from previous Fedora Core releases and the system admininstrator previously modified some service configurations, those modified configuration files are not replaced when new packages are installed. Instead, the new configuration fiels are created as .rpmnew files. Such service configurations must be fixed so the pam_stack module is not used. Refer to the .rpmnew files for the actual changes needed."
@@ -522,7 +525,7 @@
#: en/Security.xml:70(title)
msgid "Buffer Overflow detection and variable reordering"
-msgstr ""
+msgstr "????????? ???????????? ??????????????? ????????? ????????????????????? ????????? ?????????????????????"
#: en/Security.xml:71(para)
msgid "All of the software in Fedora Core and Extras software repository for this release is compiled using a security feature called fstack-protecter. fstack-protector puts a canary value on the stack of key functions, just before the return address and just before returning from that value. Then the canary value is verified, and if there was a buffer overflow, the canary will no longer match and the program aborts. The canary value is random for each time the application is started and makes it impossible to guess remotely. This is a security feature written by Red Hat developers as a rewritten implementation of the IBM ProPolice/SSP feature and available as part of GCC 4.1 compiler used in Fedora Core ."
@@ -530,7 +533,7 @@
#: en/Security.xml:72(para)
msgid "This is in addition to using FORTIFY_SOURCE from Fedora Core 4 onwards."
-msgstr ""
+msgstr "?????? FORTIFY_SOURCE ????????? ?????????????????? ????????? 4 ????????? ???????????? ???????????? ?????? ??????????????? ???????????? ?????????"
#: en/Samba.xml:8(title)
msgid "Samba"
@@ -538,7 +541,7 @@
#: en/Samba.xml:10(title)
msgid "Content temporarily removed"
-msgstr ""
+msgstr "??????????????? ???????????? ????????? ?????? ???????????? ??????"
#: en/Samba.xml:11(para)
msgid "This section has been removed for the Fedora Core 5 test3 publication of these release notes that is happening under the Opencontent Public License (OPL), as specified in the . We were not able to obtain permission from the contributor of this content in time for publication. This or similar content is going to return for the Fedora Core 5 final release."
@@ -590,7 +593,7 @@
#: en/ProjectOverview.xml:35(para)
msgid "To subscribe to any of these lists, send an email with the word \"subscribe\" in the subject to <listname>-request (where <listname> is one of the above list names.)"
-msgstr ""
+msgstr "??????????????? ?????????????????? ???????????? ???????????? ???????????? ???????????? ????????? ??????, ????????? ???-????????? ???????????? ???????????? \"????????????\" ????????? ????????? <listname>-request ????????? ???????????? (??????????????? <listname> ????????? ?????????????????? ?????????)"
#: en/ProjectOverview.xml:36(para)
msgid "Alternately, you can subscribe through the Web interface:"
@@ -602,7 +605,7 @@
#: en/ProjectOverview.xml:40(para)
msgid "The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC is a real-time, text-based form of communication. With it, you can have conversations with multiple people in an open channel or chat with someone privately one-on-one."
-msgstr ""
+msgstr "?????????????????? ????????????????????? ???????????? IRC (???????????????????????? ???????????? ?????????) ???????????? ?????? ???????????? ????????? IRC ??????????????? ?????? ????????? ????????????-????????????, ?????????-?????????????????? ????????? ????????? ?????? ?????????, ??????????????? ??????????????? ??????????????? ????????? ??????????????? ???????????? ?????? ????????? ??????????????? ????????? ?????? ???????????????-??????????????? ???????????? ????????? ????????? ?????????????????? ?????? ???????????? ?????????"
#: en/ProjectOverview.xml:41(para)
msgid "To talk with other Fedora Project participants via IRC, access freenode IRC network. Refer to the freenode website (http://www.freenode.net/) for more information. Fedora Project participants frequent the #fedora channel, while Fedora Project developers can often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well; this information can be found on the project pages and at http://fedoraproject.org/wiki/Communicate."
@@ -610,7 +613,7 @@
#: en/ProjectOverview.xml:42(para)
msgid "In order to talk on the #fedora channel, you will need to register your nickname (nick). Instructions are given when you /join the channel."
-msgstr ""
+msgstr "#fedora ???????????? ?????? ????????? ????????? ??????, ????????????????????? ???????????? ??????-????????? (?????????) ????????? ?????????????????? ???????????? ?????????????????? ????????????????????? ????????????????????? ????????????????????? ???????????? ??????????????? ???????????? /join ???????????????"
#: en/ProjectOverview.xml:44(title)
msgid "IRC Content is Uncontrolled"
@@ -626,11 +629,11 @@
#: en/PackageNotesJava.xml:8(title)
msgid "Handling Java and Java-like Packages"
-msgstr ""
+msgstr "???????????? ????????? ???????????? ???????????? ????????????????????? ?????? ?????????????????? ?????? ???????????? ??????"
#: en/PackageNotesJava.xml:9(para)
msgid "Fedore Core includes a tool suite and execution environment based on free software technologies that is capable of building and running many useful programs written in the Java programming language, including the Eclipse IDE, Tomcat, and OpenOffice.org."
-msgstr ""
+msgstr "?????????????????? ????????? ???????????? ????????? ???????????????????????? ???????????????????????? ?????? ?????????????????? ???????????? ????????? ????????? ???????????? ???????????? ????????????????????? ???????????? ?????? ?????? ???????????? ???????????? ???????????? ????????? ????????????????????? ?????? ???????????? ?????????????????????????????? ???????????? ???????????? ???????????? ?????? ????????? ????????? ????????? ????????? ???????????? ??????, ??????????????? Eclipse IDE, Tomcat, ????????? OpenOffice.org???"
#: en/PackageNotesJava.xml:10(para)
msgid "In addition to the free software stack, Fedora Core is designed to let you install multiple Java implementations and switch between them using the alternatives command line tool. However, every Java system you install must be packaged using the JPackage Project's packaging guidelines to take advantage of alternatives."
@@ -638,7 +641,7 @@
#: en/PackageNotesJava.xml:11(para)
msgid "Once installed properly, the root user should be able to switch between java and javac implementations using the alternatives command:"
-msgstr ""
+msgstr "????????? ????????? ???????????? ???????????? ?????????????????? ????????? ?????????, ????????? ?????????????????? java ????????? javac ???????????? alternatives ??????????????? ????????? ?????? ?????????-????????? ????????? ?????? ????????? ???????????? ?????????????????? ??????:"
#: en/PackageNotesJava.xml:12(screen)
#, no-wrap
@@ -647,15 +650,15 @@
#: en/PackageNotesJava.xml:14(title)
msgid "Proprietary Sun Microsystems Java is not included"
-msgstr ""
+msgstr "????????????????????? ????????? ????????????????????????????????? ???????????? ???????????? ???????????? ????????????"
#: en/PackageNotesJava.xml:15(para)
msgid "Java is a trademark of Sun Microsystems. This entirely free software stack is not Java but can run many programs written in Java. For more information, refer to the Java FAQ at http://fedoraproject.org/wiki/JavaFAQ."
-msgstr ""
+msgstr "???????????? ????????? ????????????????????????????????? ?????? ???????????????????????? ????????? ?????? ???????????? ???????????? ???????????? ???????????????????????? ???????????? ???????????? ???????????? ?????? ???????????? ???????????? ???????????? ??????????????? ????????????????????? ????????? ???????????? ????????? ??????????????? ????????????????????? ??????, ???????????? ?????? ??????????????? ???????????? http://fedoraproject.org/wiki/JavaFAQ???????????? ???????????????"
#: en/PackageNotesJava.xml:18(title)
msgid "When to use the JPackage Project RPM repository"
-msgstr ""
+msgstr "JPackage ????????????????????? RPM ?????????????????? ???????????? ????????????"
#: en/PackageNotesJava.xml:19(para)
msgid "Fedora Core includes many packages derived from the excellent JPackage Project, which provides a Java software repository. Refer to http://jpackage.org for more information on the Jpackage Project.These packages have been modified in Fedora to remove proprietary software dependencies and to make use of GCJ's ahead-of-time compilation feature. Fedora users should use the Fedora repositories for updates to these packages, and may use the JPackage repository for packages not provided by Fedora."
@@ -663,11 +666,11 @@
#: en/PackageNotesJava.xml:22(title)
msgid "Do not simply add the JPackage repo to your yum configuration"
-msgstr ""
+msgstr "???????????? yum ?????????????????? ???????????? JPackage repo ???????????? ?????? ?????????"
#: en/PackageNotesJava.xml:23(para)
msgid "Understand better what you are doing if you plan on mixing packages from the Fedora and JPackage repos. Doing so may leave your system in a state that cannot be easily fixed. Be careful, and do research before you proceed."
-msgstr ""
+msgstr "???????????? ????????? ????????? ???????????? ?????? ??????????????? ?????? ?????? ????????? ?????? ?????? ?????????????????? ????????? JPackage repos ????????? ??????????????? ???????????? ????????? ?????? ????????? ????????? ??????????????? ????????? ????????? ?????????????????? ??????????????? ????????? ???????????? ???????????? ?????? ???????????? ?????? ?????? ??????????????? ????????? ????????? ???????????? ???????????? ?????? ??????????????? ??????????????????, ????????? ???????????? ????????? ????????? ?????????????????? ????????? ?????????|"
#: en/PackageNotesJava.xml:26(title)
msgid "Include Complete Information in Bug Reports"
@@ -680,7 +683,7 @@
#: en/PackageNotesJava.xml:32(computeroutput)
#, no-wrap
msgid "\nwhich java && java -version && which javac && javac -version\n"
-msgstr ""
+msgstr "\n??????????????? java && java -version && ??????????????? javac && javac -version\n"
#: en/PackageNotes.xml:5(title) en/PackageNotes.xml:8(title)
msgid "Package Notes"
@@ -688,7 +691,7 @@
#: en/PackageNotes.xml:9(para)
msgid "The following sections contain information regarding packages that have undergone significant changes for Fedora Core . For easier access, they are generally organized using the same groups used in Anaconda."
-msgstr ""
+msgstr "??????????????? ??????????????? ???????????? ????????????????????? ????????? ????????????????????? ????????????????????? ?????? ????????? ???????????? ?????????????????? ????????? ?????? ??????????????? ???????????????????????? ???????????? ????????? ???????????? ??????????????? ??????, ?????? ?????? ????????? ?????? ???????????????????????? ???????????? ???????????? ???????????? ?????? ???????????? ??????????????? ?????????????????? ???????????? ?????????"
#: en/PackageNotes.xml:11(title)
msgid "Basic Components"
@@ -704,7 +707,7 @@
#: en/PackageNotes.xml:15(para)
msgid "The system-config-mouse configuration utility has been dropped in this release because synaptic and 3 button mouse configuration is being done automatically. Serial mice are no longer supported."
-msgstr ""
+msgstr "system-config-mouse ?????????????????? ??????????????? ?????? ??????????????? ???????????? ???????????? ?????? ?????? ?????????????????? ??????????????????????????? ????????? 3 ????????? ???????????? ?????????????????? ????????? ?????? ???????????? ????????? ????????? ?????????????????? ?????????????????? ????????? ?????????????????? ???????????? ?????????"
#: en/PackageNotes.xml:18(title)
msgid "Screensavers Not Installed by Default"
@@ -736,7 +739,7 @@
#: en/PackageNotes.xml:31(para)
msgid "This release of Fedora Core has a new version of the Dovecot IMAP server software which has has many changes in its configuration file. These changes are of importance especially to users upgrading from a previous release. Refer to http://wiki.dovecot.org/UpgradingDovecot for more information on the changes."
-msgstr ""
+msgstr "?????????????????? ?????? ?????? ???????????? ??????????????? ???????????? Dovecot IMAP ???????????? ???????????????????????? ?????? ???????????? ???????????? ???????????? ?????? ????????? ???????????? ?????? ?????? ?????????????????? ???????????? ???????????? ?????? ???????????????????????? ?????????????????? ???????????? ????????? ?????? ???????????????????????? ????????? ???????????? ???????????????????????? ?????? ?????? ??????????????? ??????????????? ????????? ????????????????????? ?????? ?????? ?????? ?????? ?????? ??????????????? ????????? ???????????????????????? ?????? ??????????????? ????????????????????? ?????? http://wiki.dovecot.org/UpgradingDovecot ???????????????"
#: en/PackageChanges.xml:8(title)
msgid "Package Changes"
@@ -748,7 +751,7 @@
#: en/PackageChanges.xml:11(para)
msgid "LinuxThreads was been deprecated in Fedora Core 4 and is no longer available in this release. NPTL, which has been the default threading library since Red Hat Linux 9, has replaced this completely."
-msgstr ""
+msgstr "LinuxThreads ????????? ?????????????????? ????????? 4 ???????????? ??????-????????? ???????????? ?????? ????????? ?????? ??????????????? ???????????? ?????????????????? ???????????? ????????? NPTL, ?????? ???????????? ????????? 9 ????????? ?????? ?????? ????????? ????????????????????? ???????????????????????? ?????? ?????? ?????? ????????? ???????????? ???????????? ????????? ??????????????????"
#: en/OverView.xml:8(title)
msgid "Fedora Core 5 Tour"
@@ -804,7 +807,7 @@
#: en/OverView.xml:42(para)
msgid "Support for Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/) has been included in the kernel."
-msgstr ""
+msgstr "????????????????????? 43xx ???????????????????????? ???????????????????????? ?????? ?????????????????? (http://bcm43xx.berlios.de/) ???????????? ???????????? ???????????? ???????????? ?????????|"
#: en/OverView.xml:45(para)
msgid "I18N support has drastically improved through the use of SCIM language input framework which has replaced IIMF in this release"
@@ -812,7 +815,7 @@
#: en/OverView.xml:48(para)
msgid "Gstreamer media framework 0.10 which brings major improvements in robustness and features has been included in this release. Totem uses this new version of Gstreamer now. Other media applications that use gstreamer is expected to be updated within the subsequent releases."
-msgstr ""
+msgstr "??????-?????????????????? ??????????????? ????????????????????? 0.10 ?????? ?????????????????? ???????????? ???????????? ??????????????? ??????????????? ?????? ????????? ?????????????????????????????? ?????? ??????????????? ???????????? ???????????? ????????? ???????????? ????????? ?????? ??????-?????????????????? ?????? ???????????? ???????????? ????????? ??????????????? ????????? ????????? ??????????????? ???????????? ?????? ??????-?????????????????? ??????????????? ?????? ?????? ???????????????????????? ???????????? ???????????? ??????????????? ???????????? ?????????????????????"
#: en/OverView.xml:53(title)
msgid "System Administration"
@@ -852,7 +855,7 @@
#: en/OverView.xml:83(para)
msgid "The proposed plans for Fedora in this version are available from http://fedoraproject.org/wiki/RoadMap."
-msgstr ""
+msgstr "?????? ???????????? ???????????? ?????????????????? ?????? ?????????????????? ???????????? ???????????? http://fedoraproject.org/wiki/RoadMap ????????? ?????????????????? ?????????"
#: en/Networking.xml:8(title)
msgid "Networking"
From fedora-docs-commits at redhat.com Sun Mar 12 20:44:08 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 12 Mar 2006 15:44:08 -0500
Subject: yum-software-management/en_US - New directory
Message-ID: <200603122044.k2CKi8oS022602@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22587/en_US
Log Message:
Directory /cvs/docs/yum-software-management/en_US added to the repository
From fedora-docs-commits at redhat.com Sun Mar 12 20:47:24 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 12 Mar 2006 15:47:24 -0500
Subject: yum-software-management/en_US yum-software-management.xml,NONE,1.1
Message-ID: <200603122047.k2CKlOIk022637@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22620
Added Files:
yum-software-management.xml
Log Message:
- Moved main file to en_US/ directory.
--- NEW FILE yum-software-management.xml ---
%FEDORA-ENTITIES-EN;
]>
WHERE IS MY FDP-INFO, DUDEIntroductionPurpose
This document presents basic concepts of software management on
&FED; systems. It outlines the major functions of
yum, the recommended software management tool
for &FED;.
Audience
This document is intended for &FED; users of all levels of
experience.
Using This Document
This document is a reference for using yum.
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
the
before using yum for the first time.
Experienced Linux users should start with
.
Previous Versions of &FC;
This document describes the configuration of
yum on &FC; &FCLOCALVER; systems. You must
perform the additional step noted in
to enable
yum on &FC; 3.
Most of the examples in this document use the package
tsclient, which is included with &FC;. The
tsclient package provides an application
for remote desktop access. If you install it successfully you
may start the application by choosing
ApplicationsInternetTerminal
Server Client. To use the examples,
substitute the name of the relevant package for
tsclient. The example commands for &FED;
package groups use the MySQL Database
group.
Avoid Logging in with the Root Account
You do not need to log in with the
root account in
order to manage your &FED; system. All of the commands shown
in this tutorial that require
root access will
prompt you for the
root password. The
example terminal commands use su
to provide this facility.
Additional Resourcesyumdocumentationyumman pages
The yum utility has features and options not
discussed in this document. Read the man
pages for yum(8) and
yum.conf(5) to learn more, using the
following commands:
man yum
man yum.confyumweb sitesyummailing lists
Other useful yum resources on the Internet
include:
Project web site
Users mailing list
Development mailing list
Check &BZ; First
If you encounter a persistent error with a specific operation,
visit &BZ-URL; and review the bug reports for the package or
packages involved. An error in a package may cause all
yum operations that rely on that package to
fail. Please file bug reports for &FED; packages, including
yum, on this &BZ; web site.
Software Management ConceptsAbout Packagespackagesdefined
&FED; software and documentation is supplied in the form of
files called RPM packages. 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 &FED; installation process
uses the packages supplied with &FC; to build or upgrade a
system to your requirements.
Packages also include a digital signature to prove their source.
Software management utilities verify this digital signature by
using a GPG public key. The
yum and rpm utilities
share a common keyring that stores all of
the public keys for approved package sources. The system
administrator configures these approved package sources.
All &FED; Packages are Open Source Software
All of the software provided by the &FP; is open source
software. You may download and install &FED; packages on as
many systems as desired.
About Repositoriesrepositoriesdefined
A repository is a prepared directory or
web site that contains software packages and index files.
Software management utilities such as yum
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.
A network of servers provide several repositories for each
version of &FC;. The package management utilities in &FC; are
already configured to use three of these repositories:
Base
The packages that make up a &FC; release, as it is on disc
Updates
Updated versions of packages that are provided in Base
&EX;
Packages for a large selection of additional software
Previous Versions of &FC;
&FC; &FCLOCALVER; automatically supports the three
repositories listed above. You must manually configure &FC; 3
systems to use &FEX;, as noted in
.
&FED; Development Repositories
&FC; 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 &FED; software:
fedora-devel (Rawhide),
fedora-extras-devel, and
updates-testing.
Third-party software developers also provide repositories for
their &FED; compatible packages. To learn how to configure your
&FED; system to use third-party repositories, read
.
package groupsdefined
You may also use the package groups
provided by the &FED; repositories to manage related packages as
sets. Some third-party repositories add packages to these
groups, or provide their packages as additional groups.
Available Package Groups
To view a list of all of the available package groups for your
&FED; system, run the command su -c 'yum
grouplist'.
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.
Installing Software not from a Repository
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 &FED; software management utilities.
The yum commands shown in this document use
repositories as package sources. Refer to
for details of
using yum to install software from a
package file.
About Dependenciesdependenciesdefined
Some of the files installed on a &FED; distribution are
libraries which may provide functions to
multiple applications. When an application requires a specific
library, the package which contains that library is a
dependency. To properly install a
package, &FED; must first satisfy its dependencies. The
dependency information for a RPM package is stored within the
RPM file.
The yum 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, yum aborts without making any
changes to your system.
Understanding Package Namespackageshardware compatibilitypackagesnaming
Each package file has a long name that indicates several key
pieces of information. For example, this is the full name of a
tsclient package:
tsclient-0.132-6.i386.rpm
Management utilities commonly refer to packages with one of
three formats:
Package name: tsclient
Package name with version and release numbers:
tsclient-0.132-6
Package name with hardware architecture:
tsclient.i386
For clarity, yum lists packages in the format
name.architecture. Repositories also
commonly store packages in separate directories by architecture.
In each case, the hardware architecture specified for the
package is the minimum type of machine
required to use the package.
i386
Suitable for any current Intel-compatible computer
noarch
Compatible with all computer architectures
ppc
Suitable for PowerPC systems, such as Apple Power
Macintosh
x86_64
Suitable for 64-bit Intel-compatible processors, such as
Opterons
Some software may be optimized for particular types of
Intel-compatible machine. Separate packages may be provided for
, ,
and computers. A
machine with at least an Intel Pentium, VIA C3 or compatible CPU
may use packages. Computers with an Intel
Pentium Pro and above, or a current model of AMD chip, may use
packages.
Use the short name of the package for yum
commands. This causes yum to automatically
select the most recent package in the repositories that matches
the hardware architecture of your computer.
Specify a package with other name formats to override the
default behavior and force yum to use the
package that matches that version or architecture. Only override
yum when you know that the default package
selection has a bug or other fault that makes it unsuitable for
installation.
Package Names
You may use any of the following formats to specify a package
in a yum operation:
name,
name.architecture,
name-version,
name-version-release,
name-version-release.architecture,
and
epoch:name-version-release.architecture.
Software Management Tools in &FC;Add/Remove Applications utilityAlert Iconup2date
The yum utility is a complete software
management system. &FC; also includes several other applications
that can supplement yum.
On your desktop is an Alert Icon that
keeps you informed about package updates. Until your system is
updated the icon appears as a red circle with a flashing
exclamation mark. The Alert Icon is part of the
up2date application, which enables you
to easily install system updates.
&FC; also includes
system-config-packages. To run this
application from the graphical interface, select DesktopSystem
SettingsAdd/Remove
Applications. Unlike
up2date and yum,
system-config-packages installs
software packages from your &FC; installation discs only, and does
not use repositories. This application is used on systems that do
not have a network connection.
The rpm 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 rpm utility, you must
manually check and install any dependencies. For this reason,
yum is the recommended method for installing
software.
Current Package Versions
The up2date and
yum utilities ensure that you have the most
recent version of software packages. Other methods do not
guarantee that the packages are current.
Managing Software with <command>yum</command>yumsoftware management
Use the yum utility to modify the software on
your system in four ways:
To install new software from package repositories
To install new software from an individual package file
To update existing software on your system
To remove unwanted software from your system
Installing Software from a Package File
The yum commands shown in this section use
repositories as package sources. Refer to
for details of
using yum to install software from an
individual package file.
To use yum, specify a function and one or more
packages or package groups. Each section below gives some
examples.
For each operation, yum downloads the latest
package information from the configured repositories. If your
system uses a slow network connection yum may
require several seconds to download the repository indexes and the
header files for each package.
The yum 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.
Format of <command>yum</command> Transaction Reports
This is an example of the transaction for installing
tsclient:
=============================================================================
Package Arch Version Repository Size
=============================================================================
Installing:
tsclient i386 0.132-6 base 247 k
Installing for dependencies:
rdesktop i386 1.4.0-2 base 107 k
Transaction Summary
=============================================================================
Install 2 Package(s)
Update 0 Package(s)
Remove 0 Package(s)
Total download size: 355 k
Is this ok [y/N]:
Review the list of changes, and then press y to
accept and begin the process. If you press N or
Enter, yum does not download
or change any packages.
Package Versions
The yum utility only displays and uses the
newest version of each package, unless you specify an older
version.
The yum utility also imports the repository
public key if it is not already installed on the
rpm keyring.
Format of <command>yum</command> Public Key Import
This is an example of the public key import:
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
public key not available for tsclient-0.132-6.i386.rpm
Retrieving GPG key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora at redhat.com>"
Is this ok [y/N]:
Check the public key, and then press y to import
the key and authorize the key for use. If you press
N or Enter,
yum stops without installing any packages.
To ensure that downloaded packages are genuine,
yum 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, yum applies them to your system.
Every completed transaction records the affected packages in the
log file /var/log/yum.log. You may only read
this file with root
access.
Downloads are Cached
The yum utility keeps downloaded data files
and packages for reuse. You may copy packages from the
repository cache directories under
/var/cache/yum/, and use them elsewhere if
you wish. If you remove a package from the cache, you do not
affect the copy of the software installed on your system.
Installing New Software with <command>yum</command>installing softwaresoftware, installingsoftwareinstalling
To install the package tsclient, enter the
command:
su -c 'yum install tsclient'
Enter the password for the
root account when
prompted.
To install the package group MySQL
Database, enter the command:
su -c 'yum groupinstall "MySQL Database"'
Enter the password for the
root account when
prompted.
New Services Require Activation
When you install a service, &FED; does not activate or start
it. To configure a new service to run on bootup, choose
DesktopSystem
SettingsServer SettingsServices, or use the
chkconfig and service
command-line utilities.
Updating Software with <command>yum</command>updatingsoftware packagessoftwareupdating
To update the tsclient package to the
latest version, type:
su -c 'yum update tsclient'
Enter the password for the
root account when
prompted.
New Software Versions Require Reloading
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.
To update all of the packages in the package group
MySQL Database, enter the command:
su -c 'yum groupupdate "MySQL Database"'
Enter the password for the
root account when
prompted.
Updating the Entire System
To update all of the packages on your &FED; system, use the
commands described in
.
Removing Software with <command>yum</command>removing softwaresoftwareremoving
To remove software, yum 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.
To remove the tsclient package from your
system, use the command:
su -c 'yum remove tsclient'
Enter the password for the
root account when
prompted.
To remove all of the packages in the package group
MySQL Database, enter the command:
su -c 'yum groupremove "MySQL Database"'
Enter the password for the
root account when
prompted.
Data and Configuration File Retention
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.
Searching for Packages with <command>yum</command>packageslocatingsearchingfor packages
Use the search features of yum to find software
that is available from the configured repositories, or already
installed on your system. Searches automatically include both
installed and available packages.
The format of the results depends upon the option. If the query
produces no information, there are no packages matching the
criteria.
Searching by Package Name and Attributes
To search for a specific package by name, use the
function. To search for the package
tsclient, use the command:
su -c 'yum list tsclient'
Enter the password for the
root account when
prompted.
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:
su -c 'yum list tsclient-0.132'Valid Package Attributes
Refer to for information
on package name formats and the attributes that they include.
Advanced Searches
If you do not know the name of the package, use the
or options.
Alternatively, use wild cards or regular expressions with any
yum search option to broaden the search
critieria.
The 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 PalmPilots, type:
su -c 'yum search PalmPilot'
Enter the password for the
root account when
prompted.
The function checks both the files
included in the packages and the functions that the software
provides. This option requires yum to
download and read much larger index files than with the
option.
To search for all packages that include files called
libneon, type:
su -c 'yum provides libneon'
To search for all packages that either provide a MTA (Mail
Transport Agent) service, or include files with
mta in their name:
su -c 'yum provides MTA'
For each command, at the prompt enter the password for the
root account.
Use the standard wildcard characters to run any search option
with a partial word or name: to represent any
one character, and to mean zero or more
characters. Always add the escape character ()
before wildcards.
To all packages with names that begin with
tsc, type:
su -c 'yum list tsc\*'Regular Expressions
Use Perl or Python regular expressions to carry out more
complex queries.
Understanding Matches
Searches with yum 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
wildcards or a regular expression.
For example, a search query for shadowutils
or shadow-util would not produce the
package shadow-utils. This package would
match and be shown if the query was
shadow-util\?, or
shadow\*.
Updating Your System with <command>yum</command>updatingfull systemyumupdating full system
Use the option to upgrade all of your
&FED; system software to the latest version with one operation.
To perform a full system update, type this command:
su -c 'yum update'
At the prompt, enter the
root password.
Automatically Updating Your Systemautomatic updating
The yum package supplied with &FC; includes
scripts to perform full system updates every day. To activate
automatic daily updates, enter this command:
su -c '/sbin/chkconfig --level 345 yum on; /sbin/service yum start'
At the prompt, enter the password for the
root account.
How Daily Updates are Run
There is no separate yum service that runs
on your system. The command given above enables the control
script /etc/rc.d/init.d/yum. This control
script activates the script
/etc/cron.daily/yum.cron, which causes
the cron service to perform the system
update automatically at 4am each day.
Using Other Software Repositories&FEX;repositoriesfindingsearchingfor repositories
&FED; systems automatically use the &FP; repositories. These
include &FEX;, the default source of packages for software that is
not included with &FC;.
&FEX; Repositories for Previous Versions of &FC;
You must manually configure &FC; 3 systems to use &FEX;, using
the instructions at
. For
additional packages for &FC; 1 and &FC; 2, refer to
.
If the &FP; 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 &FED; systems. For example,
distributes popular Java
software as packages.
Adding a Repository as a Package Sourcerepositoriesadding to yum
To add an extra repository, place a definition file in the
/etc/yum.repos.d/ directory on your system.
Package providers make the definition files for their
repositories available on their web sites.
Definition File Extension
The names of repository definition files end with
.repo.
You must have root
access to add a file to the definitions directory. To copy the
definition file example.repo, type this
command:
su -c 'cp example.repo /etc/yum.repos.d/'
At the prompt, enter the password for the
root account.
The configuration file for each repository should include a
gpgkey 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 .
Repositories and <application>up2date</application> Channels
Starting with &FC; 4, yum repositories are
automatically used as up2date
channels. On &FC; 3 and earlier systems, you must manually
configure up2date to use these
channels. To do so, edit the
/etc/sysconfig/rhn/sources file.
Manually Authorizing Package Sourcespublic keysadding
To manually add a public key to your rpm
keyring, use the feature of the
rpm utility. To import the file
GPG-PUB-KEY.asc, type the following
command:
su -c 'rpm --import GPG-PUB-KEY.asc'
At the prompt, enter the password for the
root account.
You may also import public keys directly from a web site. For
example, to import the file GPG-PUB-KEY.asc
on the web site www.therepository.com
use this command:
su -c 'rpm --import http://www.therepository.com/GPG-PUB-KEY.asc'
At the prompt, enter the
root password.
Importing the &FED; Key on &FC; 3
To add the &FED; public key to the rpm
keyring on &FC; 3 systems, run the command su -c 'rpm
--import /usr/share/rhn/RPM-GPG-KEY-fedora'.
Understanding Repository Compatibilitypackagessoftware compatibilityrepositoriescompatibility
The &FEX; repository provides packages which are built to the
same standards as &FC; packages. Third-party packages should be
compatible with these &FP; packages, unless the provider
specifically states otherwise.
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 &FED; repositories.
Alternative packages may contain versions of the software that
function differently from the version in the &FP; packages.
Determine the benefits and potential incompatibilities before
replacing &FP; packages with alternative versions.
Incompatible Repositories
If you configure your system to use incompatible repositories
yum operations may fail.
Packages built for one version of &FED; are usually not
compatible with other versions of &FED;. The web site of the
provider should specifically state which versions of &FED; they
support.
Old Versions of <command>yum</command> and Current Repositories
The data format for repository indexes changed with version
2.1 of yum. This was the version supplied
with &FC; 3. Repository providers should specify the versions
of &FC; that they support. To confirm that an unlabeled
repository is compatible with current versions of
yum, check that it has a sub-directory
called repodata/.
Installing Software from an Isolated Packageinstalling softwarefrom a packagesoftware, installing from a packagesoftwareinstalling from a package
Use repositories and the standard yum commands
to locate and install new software, unless the software package is
not available from any repository. In these cases, use the
function to install the software
from the package file.
Public Key is Required
Ensure that the public key for the package source has been
imported before you install a package without a repository.
Refer to .
Enter this command to install the package
tsclient-0.132-4.i386.rpm:
su -c 'yum localinstall tsclient-0.132-4.i386.rpm'
At the prompt, enter the
root password.
Previously Installed Software is Updated
If the package provides a later version of software that is
already installed on your system, yum updates
the installed software.
If the package requires software that is not installed on your
system, yum 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.
Maintaining Manually Installed Software
If you install software that is not provided by a repository,
yum update 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.
Maintaining <command>yum</command>
The yum system does not require any routine
maintenance. To ensure that yum operations are
carried out at optimal speed, disable or remove repository
definitions which you no longer require. You may also clear the
files from the yum caches in order to recover
disk space.
Disabling or Removing Package Sourcesrepositoriesdisabling in yumrepositoriesremoving from yum
Set enable=0 in a definition file to prevent
yum from using that repository. The
yum utility ignores any definition file with
this setting.
To completely remove access to a repository:
Delete the relevant file from
/etc/yum.repos.d/.
Delete the cache directory from
/var/cache/yum/.
Clearing the <command>yum</command> Cachesyumcleaning caches
By default, yum 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:
su -c 'yum clean headers'
Run this command to remove all of the packages held in the
caches:
su -c 'yum clean packages'
When using these commands, at the prompt, enter the password for
the root account.
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.
Using <command>yum</command> with a Proxy Serverproxy serveryumusing with a proxy server
By default, yum accesses network repositories
with HTTP. All yum 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
yum to use an FTP proxy server. The
squid package provides a proxy service for
both HTTP/1.1 and FTP connections.
Modifying <command>yum</command> for Network Compatibility
Refer to the man page for
yum.conf for information on HTTP settings
that may be modified for compatibility with nonstandard web
proxy servers. Alternatively, configure yum
to use an FTP proxy server, and access repositories that support
FTP. The &FED; repositories support both HTTP and FTP.
Configuring Proxy Server Access
To enable all yum operations to use a proxy
server, specify the proxy server details in
/etc/yum.conf. The
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
and
settings.
The settings below enable yum to use the
proxy server
mycache.mydomain.com,
connecting to port 3128, with the username
yum-user and the
password qwerty.
Configuration File Settings for Using A Proxy Server# The proxy server - proxy server:port number
proxy=http://mycache.mydomain.com:3128
# The account details for yum connections
proxy_username=yum-user
proxy_password=qwertyGlobal Settings
If you define a proxy server in
/etc/yum.conf, all
users connect to the proxy server with those details when
using yum.
Configuring Proxy Server Access for a Single User
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
bash shell, the profile is the file
~/.bash_profile. The settings below enable
yum to use the proxy server
mycache.mydomain.com,
connecting to port 3128.
Profile Settings for Using a Proxy Server# The Web proxy server used by this account
http_proxy="http://mycache.mydomain.com:3128"
export http_proxy
If the proxy server requires a username and password, add these
to the URL. To include the username
yum-user and the
password qwerty, add these settings:
Profile Settings for a Secured Proxy Server# The Web proxy server, with the username and password for this account
http_proxy="http://yum-user:qwerty at mycache.mydomain.com:3128"
export http_proxyThe <option>http_proxy</option> Environment Variable
The http_proxy environment variable is also
used by curl and other utilities. Although
yum itself may use
http_proxy in either upper-case or
lower-case, curl requires the name of the
variable to be in lower-case.
Acknowledgements
Paul Frields edited this document. Timothy Murphy reviewed the
beta release.
From fedora-docs-commits at redhat.com Sun Mar 12 20:52:10 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 12 Mar 2006 15:52:10 -0500
Subject: yum-software-management/en yum-software-management.xml,1.2,NONE
Message-ID: <200603122052.k2CKqABG022685@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22665/en
Removed Files:
yum-software-management.xml
Log Message:
- Removed copy of main file in en/ directory.
--- yum-software-management.xml DELETED ---
From fedora-docs-commits at redhat.com Sun Mar 12 23:04:04 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun, 12 Mar 2006 18:04:04 -0500
Subject: release-notes/po it.po,1.5,1.6
Message-ID: <200603122304.k2CN441n028935@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28917
Modified Files:
it.po
Log Message:
corrected 2 typos
Index: it.po
===================================================================
RCS file: /cvs/docs/release-notes/po/it.po,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- it.po 8 Mar 2006 05:32:54 -0000 1.5
+++ it.po 12 Mar 2006 23:03:36 -0000 1.6
@@ -5,7 +5,7 @@
msgstr ""
"Project-Id-Version: it\n"
"POT-Creation-Date: 2006-03-08 06:25+0100\n"
-"PO-Revision-Date: 2006-03-08 06:32+0100\n"
+"PO-Revision-Date: 2006-03-12 22:47+0100\n"
"Last-Translator: Francesco Tombolini \n"
"Language-Team: Italiano \n"
"MIME-Version: 1.0\n"
@@ -3390,8 +3390,8 @@
"release of Fedora Core."
msgstr ""
"Questa versione ?? il culmine di nove mesi di sviluppo, ed include nuove "
-"significative versioni di molti prodotti chiave e tecnologie. La seguente "
-"sezione fornisce una breve panoramica dei principali cambiamenti dall'ultima "
+"significative versioni di molti prodotti chiave e tecnologie. Le seguenti "
+"sezioni forniscono una breve panoramica dei principali cambiamenti dall'ultima "
"versione di Fedora Core."
#: en/OverView.xml:14(title)
@@ -3469,7 +3469,7 @@
"Suspend to RAM support has also been improved due to infrastructure work "
"done by the hibernate support."
msgstr ""
-"Il supporto della sospensione in RAM ?? stato migliorato greazie al lavoro "
+"Il supporto della sospensione in RAM ?? stato migliorato grazie al lavoro "
"fatto all'infrastruttura dal supporto hibernate."
#: en/OverView.xml:36(para)
@@ -3501,8 +3501,8 @@
msgstr ""
"Questa versione di Fedora include, per la prima volta, il supporto per Mono, "
"e le applicazioni Mono, tipo Beagle, un "
-"interfaccia di ricerca per il desktop; F-Spot, un utilit?? di amministrazione per le fotografie; e F-Spot, un utilit?? di amministrazione per le fotografie e Tomboy, un applicazione per prendere appunti."
#: en/OverView.xml:42(para)
@@ -5077,7 +5077,7 @@
#: en/Java.xml:28(title)
msgid "Handling Java and Java-like Packages"
-msgstr "Gestire i paccheti Java e Java-like"
+msgstr "Gestire i pacchetti Java e Java-like"
#: en/Java.xml:29(para)
msgid ""
From fedora-docs-commits at redhat.com Mon Mar 13 00:23:41 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 12 Mar 2006 19:23:41 -0500
Subject: yum-software-management/en_US yum-software-management.xml,1.1,1.2
Message-ID: <200603130023.k2D0Nfxd031244@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31193/en_US
Modified Files:
yum-software-management.xml
Log Message:
- First pass at updating text for Fedora 5.
- Now uses en_US locale.
- Switched to OPL.
Index: yum-software-management.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/yum-software-management.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- yum-software-management.xml 12 Mar 2006 20:47:17 -0000 1.1
+++ yum-software-management.xml 13 Mar 2006 00:23:33 -0000 1.2
@@ -1,24 +1,18 @@
+
+
-%FEDORA-ENTITIES-EN;
-
-
-
-
-
-
-
+
+%FDP-ENTITIES;
+
+%DOC-ENTITIES;
-
]>
-
-
-
- WHERE IS MY FDP-INFO, DUDE
-
+
+ Introduction
@@ -62,7 +56,7 @@
This document describes the configuration of
- yum on &FC; &FCLOCALVER; systems. You must
+ yum on current versions of &FC;. You must
perform the additional step noted in
to enable
yum on &FC; 3.
@@ -281,17 +275,6 @@
-
- Previous Versions of &FC;
-
-
- &FC; &FCLOCALVER; automatically supports the three
- repositories listed above. You must manually configure &FC; 3
- systems to use &FEX;, as noted in
- .
-
-
-
&FED; Development Repositories
@@ -539,41 +522,33 @@
Software Management Tools in &FC;
- Add/Remove Applications utility
+ Add/Remove Software utility
- Alert Icon
+ Software Updater utility
- up2date
+ rpm utility
The yum utility is a complete software
- management system. &FC; also includes several other applications
- that can supplement yum.
-
-
-
- On your desktop is an Alert Icon that
- keeps you informed about package updates. Until your system is
- updated the icon appears as a red circle with a flashing
- exclamation mark. The Alert Icon is part of the
- up2date application, which enables you
- to easily install system updates.
+ management system. &FC; also includes two graphical applications
+ for software management that use yum. The
+ pup utility provides an interface for
+ updating software, and the pirut
+ application enables you to add or remove software.
- &FC; also includes
- system-config-packages. To run this
- application from the graphical interface, select
- DesktopSystem
- SettingsAdd/Remove
- Applications. Unlike
- up2date and yum,
- system-config-packages installs
- software packages from your &FC; installation discs only, and does
- not use repositories. This application is used on systems that do
- not have a network connection.
+ Both graphical tools appear in the Applications
+ desktop menu. To update your system with
+ pup, select
+ ApplicationsSystem
+ ToolsSoftware Updater
+ . To add or remove software with
+ pirut, select
+ ApplicationsAdd/Remove
+ Software.
@@ -590,7 +565,7 @@
Current Package Versions
- The up2date and
+ The Add/Remove Software and
yum utilities ensure that you have the most
recent version of software packages. Other methods do not
guarantee that the packages are current.
@@ -749,21 +724,14 @@
Every completed transaction records the affected packages in the
- log file /var/log/yum.log. You may only read
- this file with root
- access.
+ log file
+
+ log file
+
+ /var/log/yum.log. You may only read this file
+ with root access.
-
- Downloads are Cached
-
- The yum utility keeps downloaded data files
- and packages for reuse. You may copy packages from the
- repository cache directories under
- /var/cache/yum/, and use them elsewhere if
- you wish. If you remove a package from the cache, you do not
- affect the copy of the software installed on your system.
-
-
+
Installing New Software with <command>yum</command>
@@ -1233,19 +1201,6 @@
configuration file provided does not include this setting, refer
to .
-
-
- Repositories and <application>up2date</application> Channels
-
-
- Starting with &FC; 4, yum repositories are
- automatically used as up2date
- channels. On &FC; 3 and earlier systems, you must manually
- configure up2date to use these
- channels. To do so, edit the
- /etc/sysconfig/rhn/sources file.
-
-
@@ -1567,10 +1522,10 @@
cleaning caches
- By default, yum 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:
+ If you configure it to do so, yum 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:
su -c 'yum clean headers'
From fedora-docs-commits at redhat.com Mon Mar 13 00:23:35 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 12 Mar 2006 19:23:35 -0500
Subject: yum-software-management Makefile,1.8,1.9 rpm-info.xml,1.2,1.3
Message-ID: <200603130024.k2D0O5Y4031248@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31193
Modified Files:
Makefile rpm-info.xml
Log Message:
- First pass at updating text for Fedora 5.
- Now uses en_US locale.
- Switched to OPL.
Index: Makefile
===================================================================
RCS file: /cvs/docs/yum-software-management/Makefile,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Makefile 18 Feb 2006 11:04:40 -0000 1.8
+++ Makefile 13 Mar 2006 00:23:27 -0000 1.9
@@ -16,8 +16,9 @@
# Document-specific definitions.
#
DOCBASE = yum-software-management
-PRI_LANG = en
+PRI_LANG = en_US
OTHERS = zh_CN
+DOC_ENTITIES = doc-entities
########################################################################
# List each XML file of your document in the template below. Append the
# path to each file to the "XMLFILES-${1}" string. Use a backslash if you
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/rpm-info.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- rpm-info.xml 18 Feb 2006 12:53:39 -0000 1.2
+++ rpm-info.xml 13 Mar 2006 00:23:27 -0000 1.3
@@ -9,9 +9,8 @@
-
- GNU FDL
+ OPL1.0
@@ -19,54 +18,55 @@
Stuart Ellis
-
+ Managing Software with yum
-
-Documentation for the yum software management system.
-
+ Documentation for the yum software management system.?????? <command>yum</command> ????????????
-
- ?????????????????? yum ????????????
-
+ ?????????????????? yum ????????????
-
+
-
+
+
+
+ Updated for Fedora 5.
+
+ Fixed some uses of "Fedora" to read "Fedora Core" where appropriate.
-
+ Updated section on proxy servers. Fixed #166122.
-
+ Fix wording (#170584).
-
+ Fix localinstall information.
-
+ Added information on installing without repository and manually adding
keys.
-
+ Publish to official project page.
-
+ Edited for style and usage; BETA publication.
-
+ Updated for Fedora Core 4.
-
+ Initial import into CVS.
From fedora-docs-commits at redhat.com Mon Mar 13 03:08:39 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun, 12 Mar 2006 22:08:39 -0500
Subject: docs-common/xsl main-pdf.xsl,1.3,1.4
Message-ID: <200603130308.k2D38dpQ005171@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common/xsl
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5135/xsl
Modified Files:
main-pdf.xsl
Log Message:
Compute, pass, and use the absolute path to the callout images.
Index: main-pdf.xsl
===================================================================
RCS file: /cvs/docs/docs-common/xsl/main-pdf.xsl,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- main-pdf.xsl 18 Oct 2005 20:09:42 -0000 1.3
+++ main-pdf.xsl 13 Mar 2006 03:08:20 -0000 1.4
@@ -1,24 +1,23 @@
-
-
-
-
-
+
-
-
-article toc
-
+article toc3
-./stylesheet-images/
+..
+
+
+
+
+
From fedora-docs-commits at redhat.com Mon Mar 13 03:08:22 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Sun, 12 Mar 2006 22:08:22 -0500
Subject: docs-common Makefile.common,1.104,1.105
Message-ID: <200603130308.k2D38q1T005176@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/docs-common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5135
Modified Files:
Makefile.common
Log Message:
Compute, pass, and use the absolute path to the callout images.
Index: Makefile.common
===================================================================
RCS file: /cvs/docs/docs-common/Makefile.common,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -r1.104 -r1.105
--- Makefile.common 12 Mar 2006 17:48:11 -0000 1.104
+++ Makefile.common 13 Mar 2006 03:08:12 -0000 1.105
@@ -474,8 +474,9 @@
.PHONY: fo-${1}
fo-${1}:: ${1}/${DOCBASE}.fo
${1}/${DOCBASE}.fo:: ${XMLFILES-${1}} ${XMLDEPFILES-${1}} set-locale-${1}
- LANG=${1}.UTF-8 xsltproc --xinclude ${XSLPDF} \
- ${1}/${DOCBASE}.xml | ${XMLLINT} --format -o $$@ -
+ LANG=${1}.UTF-8 xsltproc --xinclude \
+ --stringparam FDPDIR ${FDPDIR} \
+ ${XSLPDF} ${1}/${DOCBASE}.xml | ${XMLLINT} --format -o $$@ -
clean::
${RM} ${1}/${DOCBASE}.fo
help::
From fedora-docs-commits at redhat.com Mon Mar 13 12:39:36 2006
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Mon, 13 Mar 2006 07:39:36 -0500
Subject: install-guide/po zh_CN.po,1.8,1.9
Message-ID: <200603131239.k2DCdaf9027516@cvs-int.fedora.redhat.com>
Author: bbbush
Update of /cvs/docs/install-guide/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27498/po
Modified Files:
zh_CN.po
Log Message:
updated translation by Xiaofan.Yang
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.8 -r 1.9 zh_CN.po
Index: zh_CN.po
===================================================================
RCS file: /cvs/docs/install-guide/po/zh_CN.po,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- zh_CN.po 6 Mar 2006 05:15:17 -0000 1.8
+++ zh_CN.po 13 Mar 2006 12:39:28 -0000 1.9
@@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: fedora-install-guide\n"
-"POT-Creation-Date: 2006-03-04 19:58+0800\n"
-"PO-Revision-Date: 2006-02-28 03:44+0800\n"
+"POT-Creation-Date: 2006-03-12 03:24+0800\n"
+"PO-Revision-Date: 2006-03-12 03:30+0800\n"
"Last-Translator: Xiaofan Yang \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
@@ -11,6 +11,7 @@
"X-Poedit-Language: Chinese\n"
"X-Poedit-Country: CHINA\n"
"X-Poedit-SourceCharset: utf-8\n"
+"X-Poedit-Bookmarks: 472,-1,-1,-1,-1,-1,-1,-1,-1,-1\n"
#. 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.
@@ -41,7 +42,6 @@
msgstr "?????????????????????"
#: en/fedora-install-guide-upgrading.xml:18(para)
-#, fuzzy
msgid ""
"The installation system automatically detects any existing installation of "
"&FC;. The upgrade process updates the existing system software with new "
@@ -51,9 +51,9 @@
"package upgrades do not change system configuration, but rather install an "
"additional configuration file for you to examine later."
msgstr ""
-"?????????????????????????????? &FC; ???????????????????????????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"????????????????????????????????????????????? &FC; ????????????????????????????????????????????????????????????"
+"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"?????????????????????"
#: en/fedora-install-guide-upgrading.xml:30(title)
@@ -61,11 +61,10 @@
msgstr "????????????"
#: en/fedora-install-guide-upgrading.xml:32(para)
-#, fuzzy
msgid ""
"If your system contains a &FC; or &RHL; installation, the following screen "
"appears:"
-msgstr "???????????????????????????????????? &FC; ?????? &RHL; ????????????????????????????????????"
+msgstr "????????????????????????????????? &FC; ?????? &RHL; ????????????????????????????????????"
#: en/fedora-install-guide-upgrading.xml:38(title)
msgid "Upgrade Examine Screen"
@@ -80,15 +79,14 @@
"To perform an upgrade of an existing system, choose the appropriate "
"installation from the drop-down list and select Next."
msgstr ""
-"?????????????????????????????????????????????????????????????????????????????????????????? "
-"Next(?????????)???"
+"?????????????????????????????????????????????????????????????????????????????????????????? ??????"
+"??????"
#: en/fedora-install-guide-upgrading.xml:61(title)
msgid "Manually Installed Software"
msgstr "?????????????????????"
#: en/fedora-install-guide-upgrading.xml:62(para)
-#, fuzzy
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 "
@@ -96,14 +94,13 @@
"the updated system."
msgstr ""
"??????????????????????????????????????? &FC; ??? &RHL; ???????????????????????????????????????????????????"
-"????????????????????????????????????????????????????????????????????????????????????"
+"???????????????????????????????????????????????????????????????????????????????????????"
#: en/fedora-install-guide-upgrading.xml:73(title)
msgid "Upgrading Boot Loader Configuration"
msgstr "????????????????????????"
#: en/fedora-install-guide-upgrading.xml:75(para)
-#, fuzzy
msgid ""
"boot loaderupgrading Your completed &FC; installation must be registered in the "
@@ -116,9 +113,9 @@
"boot loaderupgrading ?????? &FC; ??????????????????????????????????????? boot "
"loaderGRUBboot loader ???????????????????????????????????????????????????????????????????????????????????????????????????"
-"?????????????????????????????????????????? ??????????????????"
-"???????????????????????????"
+"firstterm> ???????????????????????????????????????????????????????????????????????????????????????????????????"
+"???????????????????????? ???????????????????????????????????????"
+"??????"
#: en/fedora-install-guide-upgrading.xml:91(title)
msgid "Upgrade Bootloader Screen"
@@ -129,7 +126,6 @@
msgstr "?????????????????????????????????"
#: en/fedora-install-guide-upgrading.xml:107(para)
-#, fuzzy
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 "
@@ -139,11 +135,10 @@
msgstr ""
"????????????????????????????????????????????? Linux ????????????????????????????????????????????????????????????"
"??? &FC; ??????????????????????????? Linux ??????????????????????????? Update boot "
-"loader configuration(??????????????????????????????)???????????????????????? &FC; "
-"??? &RHL; ??????????????????????????????????????????"
+"loader configuration(??????????????????????????????)???????????????????????? &FC; "
+"??? &RHL; ??????????????????????????????????????????"
#: en/fedora-install-guide-upgrading.xml:115(para)
-#, fuzzy
msgid ""
"GRUB is the standard boot loader for &FED;. If your "
"machine uses another boot loader, such as BootMagic, "
@@ -153,7 +148,7 @@
"installation process completes, refer to the documentation for your product "
"for assistance."
msgstr ""
-"GRUB ??? &FED; ????????????????????????????????????????????????????????????"
+"GRUB ??? &FED; ????????????????????????????????????????????????????????????"
"????????????????????????????????? BootMagic???System "
"Commander ?????? Microsoft Windows ?????????????????????????????? &FED; ??????"
"??????????????????????????????????????? Skip boot loader updating(???"
@@ -177,7 +172,7 @@
#: en/fedora-install-guide-upgrading.xml:136(para)
msgid ""
"After you make your selection, click Next to continue."
-msgstr "??????????????????????????? Next(?????????) ????????????"
+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.
@@ -211,7 +206,6 @@
msgstr "??????????????????"
#: en/fedora-install-guide-timezone.xml:28(para)
-#, fuzzy
msgid "&FED; displays on the screen two methods for selecting the time zone."
msgstr "&FED; ????????????????????????????????????????????????"
@@ -258,7 +252,6 @@
"Time)UTC ????????????????????? (GMT)???"
#: en/fedora-install-guide-timezone.xml:75(para)
-#, fuzzy
msgid ""
"If &FC; is the only operating system on your computer, select "
"System clock uses UTC. The system clock is a piece of "
@@ -268,7 +261,7 @@
msgstr ""
"?????? &FC; ????????????????????????????????????????????? System clock uses UTC(?????????????????? UTC)????????????????????????????????????????????????????????????&FC; ??????"
-"?????????????????????????????????????????? UTC ?????????????????????????????? ???UNIX ????????????????????????"
+"?????????????????????????????????????????? UTC ????????????????????????????????? ???UNIX ?????????????????????"
"???????????????"
#: en/fedora-install-guide-timezone.xml:85(title)
@@ -276,7 +269,6 @@
msgstr "Windows ???????????????"
#: en/fedora-install-guide-timezone.xml:87(para)
-#, fuzzy
msgid ""
"Do not enable the System clock uses UTC option if your "
"machine also runs Microsoft Windows. Microsoft operating systems change the "
@@ -285,18 +277,17 @@
msgstr ""
"????????????????????????????????? Microsoft Windows??????????????? System clock "
"uses UTC(?????????????????? UTC) ?????????Microsoft ????????????????????? BIOS ???"
-"?????????????????????????????? UTC????????? &FC; ??????????????????????????????????????????"
+"?????????????????????????????? UTC????????? &FC; ????????????????????????????????????"
#: en/fedora-install-guide-timezone.xml:95(para)
msgid "Select Next to proceed."
-msgstr "?????? Next(?????????) ??????????????????"
+msgstr "?????? ????????? ????????????"
#: en/fedora-install-guide-techref.xml:17(title)
msgid "Other Technical Documentation"
msgstr "??????????????????"
#: en/fedora-install-guide-techref.xml:18(para)
-#, fuzzy
msgid ""
[...3357 lines suppressed...]
#: en/fedora-install-guide-abouttoinstall.xml:18(para)
-#, fuzzy
msgid ""
"No changes are made to your computer until you click the Next button. If you abort the installation process after that point, "
@@ -6342,23 +6079,22 @@
"abort the installation, turn off the computer."
msgstr ""
"????????? Next(?????????) ??????????????????????????????????????????????????????"
-"??????????????????????????????????????????&FC; ??????????????????????????????????????????????????????????????????"
-"????????????????????? Back(??????)??????????????????????????????????????????"
-"??????"
+"????????????????????????????????????????????????&FC; ?????????????????????????????????????????????????????????"
+"????????????????????????????????? Back(??????)?????????????????????????????????"
+"???????????????"
#: en/fedora-install-guide-abouttoinstall.xml:28(title)
msgid "Aborting Installation"
msgstr "??????????????????"
#: en/fedora-install-guide-abouttoinstall.xml:29(para)
-#, fuzzy
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."
msgstr ""
"?????????????????????????????????????????????????????????&FC; ???????????????????????????????????????????????????"
-"???????????????????????????????????????????????????????????????"
+"?????????????????????????????????????????????????????????????????????"
#: en/fedora-install-guide-abouttoinstall.xml:38(title)
msgid "About to Install Screen"
@@ -6374,68 +6110,148 @@
#: en/entities.xml:5(title)
msgid "These entities are local to the Fedora Installation Guide."
-msgstr ""
+msgstr "?????????????????? Fedora ???????????????????????????"
#: en/entities.xml:8(comment)
msgid "Document base name"
-msgstr ""
+msgstr "??????????????????"
#: en/entities.xml:9(text)
msgid "fedora-install-guide"
-msgstr ""
+msgstr "fedora ????????????"
#: en/entities.xml:12(comment)
-#, fuzzy
msgid "Document language"
-msgstr "??????"
+msgstr "????????????"
#: en/entities.xml:13(text)
msgid "en"
-msgstr ""
+msgstr "en"
#: en/entities.xml:16(comment)
msgid "Document version"
-msgstr ""
+msgstr "????????????"
#: en/entities.xml:17(text)
-#, fuzzy
-msgid "1.24"
-msgstr "1.0.4"
+msgid "1.25"
+msgstr "1.25"
#: en/entities.xml:20(comment)
msgid "Document date"
-msgstr ""
+msgstr "????????????"
#: en/entities.xml:21(text)
-#, fuzzy
-msgid "2006-03-04"
-msgstr "2005-12-04"
+msgid "2006-03-12"
+msgstr "2006-03-12"
#: en/entities.xml:24(comment)
msgid "Document ID string"
-msgstr ""
+msgstr "?????? ID ???"
#: en/entities.xml:25(text)
msgid ""
"
-
- Language Selection
-
-
- Select every language that you need for
- your system. Adding support for a language after installation is
- difficult, and not recommended.
-
-
-
After you choose the desired packages, select
Next to proceed. &FC; checks your selection,
From fedora-docs-commits at redhat.com Tue Mar 14 22:34:26 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Tue, 14 Mar 2006 17:34:26 -0500
Subject: install-guide rpm-info.xml,1.14,1.15
Message-ID: <200603142234.k2EMYunk015702@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15658
Modified Files:
rpm-info.xml
Log Message:
- Removed obsolete warning about language support.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- rpm-info.xml 12 Mar 2006 18:16:34 -0000 1.14
+++ rpm-info.xml 14 Mar 2006 22:34:19 -0000 1.15
@@ -28,10 +28,15 @@
+
+
+
+ Removed obsolete admonition.
+
- Updated to match Rawhide.
+ Updated to match Rawhide.
From fedora-docs-commits at redhat.com Tue Mar 14 22:37:38 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 14 Mar 2006 17:37:38 -0500
Subject: release-notes Makefile,1.35,1.36
Message-ID: <200603142237.k2EMbc5B015731@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15713
Modified Files:
Makefile
Log Message:
Removing Punjabi build for ISO, will try this again for Web
Index: Makefile
===================================================================
RCS file: /cvs/docs/release-notes/Makefile,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- Makefile 14 Mar 2006 20:59:41 -0000 1.35
+++ Makefile 14 Mar 2006 22:37:30 -0000 1.36
@@ -8,7 +8,7 @@
#
DOCBASE = RELEASE-NOTES
PRI_LANG = en
-OTHERS = zh_CN pt_BR it ru pa # ja_JP
+OTHERS = zh_CN pt_BR it ru # pa ja_JP
########################################################################
# List each XML file of your document in the template below. Append the
From fedora-docs-commits at redhat.com Tue Mar 14 23:05:02 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 14 Mar 2006 18:05:02 -0500
Subject: press-release Makefile,1.3,1.4
Message-ID: <200603142305.k2EN52ww018025@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18007
Modified Files:
Makefile
Log Message:
Replace usage of "xml2pot" with "xml2o" to match FDP toolchain
expectations.
Much cleanup.
Index: Makefile
===================================================================
RCS file: /cvs/docs/press-release/Makefile,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Makefile 11 Mar 2006 17:22:43 -0000 1.3
+++ Makefile 14 Mar 2006 23:04:52 -0000 1.4
@@ -2,9 +2,9 @@
# The ${DOC_BASE} symbol provides the basic name for this document.
DOC_BASE=fdp-pr
########################################################################
-# The ${LANG} symbol gives the locale for the original language for
+# The ${PRI_LANG} symbol gives the locale for the original language for
# the document.
-LANG=en_US
+PRI_LANG=en_US
########################################################################
# The ${OTHERS} symbol is a list of additional locales into which the
# document is to be translated.
@@ -24,6 +24,8 @@
MSGMERGE=msgmerge
MSGMERGEFLAGS=
########################################################################
+LANGUAGES=${PRI_LANG} ${OTHERS}
+########################################################################
# Define our own set of suffixes to streamline the process
.SUFFIXES:
.SUFFIXES: .txt .pdf .po .pot .xml .xsl .dtd .in
@@ -31,31 +33,38 @@
# Mark the proper virtual targets so that a "make -t all" does not create
# an empty file called "all".
.PHONY: all clean distclean clobber pot
-.PHONY: $(foreach LOCALE,${OTHERS},xml-${LOCALE})
-.PHONY: $(foreach LOCALE,${OTHERS},po-${LOCALE})
########################################################################
# The default target "all"
all:: ${DOC_BASE}.pot
-all:: $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.xml)
-all:: $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.pdf)
-all:: $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.txt)
+all:: $(foreach LOCALE,${LANGUAGES},${DOC_BASE}-${LOCALE}.pdf)
+all:: $(foreach LOCALE,${LANGUAGES},${DOC_BASE}-${LOCALE}.txt)
########################################################################
# Compute the rules to transform our XML documents into both PDF and TXT
# forms
define OUTPUT_template
+
${DOC_BASE}-$(1).pdf:: ${DOC_BASE}-$(1).xml params.xsl.in
LC_ALL=${1}.UTF-8 ${SED} -e "s|DATE|$$(date +'%x %X')|" \
params.xsl.in >params.xsl
LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} pdf \
${DOC_BASE}-$(1).xml
+ ${RM} params.xsl
+
+distclean::
+ ${RM} ${DOC_BASE}-${1}.pdf
+
${DOC_BASE}-$(1).txt:: ${DOC_BASE}-$(1).xml params.xsl.in
LC_ALL=${1}.UTF-8 ${SED} -e "s|DATE|$$(date +'%x %X')|" \
params.xsl.in >params.xsl
LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} txt \
${DOC_BASE}-$(1).xml
+ ${RM} params.xsl
+
+distclean::
+ ${RM} ${DOC_BASE}-${1}.txt
endef
-$(foreach LOCALE,${LANG} ${OTHERS},$(eval $(call OUTPUT_template,${LOCALE})))
+$(foreach LOCALE,${LANGUAGES},$(eval $(call OUTPUT_template,${LOCALE})))
########################################################################
# Always generate the current date.
params.xsl: params.xsl.in
@@ -63,15 +72,19 @@
########################################################################
# The ${DOC_BASE}.pot target produces a new .POT file everytime the
# original XML file is updated.
-${DOC_BASE}.pot: ${DOC_BASE}-${LANG}.xml
- xml2pot $< >$@
+${DOC_BASE}.pot: ${DOC_BASE}-${PRI_LANG}.xml
+ xml2po -o $@ $<
########################################################################
# Compute the rules to create or update a language-specific .po file
# any time the ${DOC_BASE}.pot file is updated. We try to avoid losing
# current .PO translations by calling msgmerge if a .po file already
# exists.
define PO_template
-po-${1} ${1}.po:: ${DOC_BASE}.pot
+.PHONY: po-${1}
+po-${1}:: ${1}.po
+
+.PRECIOUS: ${1}.po
+${1}.po:: ${DOC_BASE}.pot
@if [ ! -f ${1}.po ]; then \
echo Creating pristine ${1}.po; \
cp ${DOC_BASE}.pot ${1}.po; \
@@ -87,20 +100,25 @@
# Compute the rules and targets to generate the translated XML files
# given an updated .PO file and the source XML file.
define NEWLANG_template
-xml-${1} ${DOC_BASE}-${1}.xml:: ${DOC_BASE}-${LANG}.xml ${1}.po
- ${PO2XML} ${DOC_BASE}-${LANG}.xml ${1}.po >${DOC_BASE}-${1}.xml
+.PHONY: xml-${1}
+xml-${1}:: ${DOC_BASE}-${1}.xml
+
+${DOC_BASE}-${1}.xml:: ${DOC_BASE}-${PRI_LANG}.xml ${1}.po
+ ${PO2XML} ${DOC_BASE}-${PRI_LANG}.xml ${1}.po >${DOC_BASE}-${1}.xml
+
+clean::
+ ${RM} ${DOC_BASE}-${1}.xml
endef
$(foreach LOCALE,${OTHERS},$(eval $(call NEWLANG_template,${LOCALE})))
########################################################################
-# Neatness counts
-clean:
- ${RM} $(foreach LOCALE,${OTHERS},${DOC_BASE}-${LOCALE}.xml)
- ${RM} params.xsl
-
-distclean clobber: clean
- ${RM} $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.pdf)
- ${RM} $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.txt)
+clean::
+ ${RM} params.xml
+distclean clobber:: clean
+########################################################################
+.PHONY: mrproper
+mrproper:: distclean
+ ${RM} *.po
########################################################################
# End of Makefile
########################################################################
From fedora-docs-commits at redhat.com Tue Mar 14 23:07:49 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Tue, 14 Mar 2006 18:07:49 -0500
Subject: press-release README,1.9,1.10
Message-ID: <200603142307.k2EN7nQd018116@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18088
Modified Files:
README
Log Message:
Doesn't work so well with the standard XMLTO that uses passivetex.
Index: README
===================================================================
RCS file: /cvs/docs/press-release/README,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- README 9 Mar 2006 00:50:05 -0000 1.9
+++ README 14 Mar 2006 23:07:35 -0000 1.10
@@ -24,4 +24,7 @@
This version of XMLTO has not yet been approved by the upstream
developers, either.
+Caution: using this with the standard xmlto RPM doesn't wrap lines
+in the .txt file, and doesn't separate paragraphs in the PDF version.
+
END OF README
From fedora-docs-commits at redhat.com Wed Mar 15 04:10:09 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 14 Mar 2006 23:10:09 -0500
Subject: jargon-buster/en jargon-buster.xml,1.1,1.2
Message-ID: <200603150410.k2F4A97x029012@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/jargon-buster/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28970/en
Modified Files:
jargon-buster.xml
Log Message:
Removed or revised remaining content not eligible for relicensing; now document is OPL
Index: jargon-buster.xml
===================================================================
RCS file: /cvs/docs/jargon-buster/en/jargon-buster.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- jargon-buster.xml 17 Feb 2006 22:59:39 -0000 1.1
+++ jargon-buster.xml 15 Mar 2006 04:09:46 -0000 1.2
@@ -1,12 +1,12 @@
-%FEDORA-ENTITIES-EN;
+
+%FDP-ENTITIES;
-
-
+
+
]>
@@ -24,7 +24,8 @@
bug reporting information below to notify the maintainers.
- &BUG-REPORTING;
+ Glossary
@@ -48,10 +49,11 @@
ALSA
- The Advanced Linux Sound Architecture (ALSA) provides audio
- and MIDI functionality to the Linux operating system. Refer
- to for more
- information.
+ The Advanced Linux Sound Architecture (ALSA) is a technology
+ that gives &FED; the ability to mix and output multiple
+ audio sources. ALSA supports many consumer and professional
+ level hardware devices. Refer to for more information.
@@ -59,20 +61,15 @@
Anaconda
- Anaconda is the installation
- program for &FC;. During installation,
- Anaconda identifies and
- configures the system's hardware, and creates appropriate
- file systems. Anaconda also
- allows the user to install the operating system software on
- the system. Optionally, it upgrades existing &RHL; or &FED;
- installations. Anaconda runs in a
- fully interactive text or graphical mode, or in a
- kickstart mode, which allows the
- owner or administrator to automate installation for
- unattended operation. Refer to
- for more information.
+ Anaconda is the &FC; installation
+ system. Anaconda identifies and
+ configures the system's hardware, creates appropriate file
+ systems, and installs or upgrades software packages.
+ Anaconda runs in a fully
+ interactive text or graphical mode, or in an automated mode. Refer to for more
+ information.
@@ -96,16 +93,9 @@
ATrpms
- ATrpms a third party RPM repository for &FED;
- distributions. The original focus for ATrpms was software
- used in natural sciences, especially in the field of high
- energy physics. The repository included tools for use in
- numerical programming and scientific publications. But since
- then this repository has included many non-scientific
- software titles, like system tools or multimedia packages,
- resulting in a far more generic repository. Refer to for more
- information.
+ ATrpms a third party RPM repository for &FED; software.
+ Refer to
+ for more information about ATrpms.
@@ -226,10 +216,10 @@
The Common UNIX Printing System, or CUPS,
- is a cross-platform printing solution for all UNIX-type
+ is a cross-platform, modularized printing system for UNIX-type
environments, including Linux and Macintosh OS X. It is
based on the Internet Printing Protocol and provides
- complete printing services to most printers. CUPS drivers
+ facilities for managing print jobs and queues. CUPS drivers
are available at
which allow Windows systems to use printers shared from
Linux systems. Refer to
@@ -285,9 +275,9 @@
The ethtool utility is a Linux network
driver diagnostic and tuning tool for a Linux 2.4 or later
. The
- ethtool utility obtains information and
- diagnostics related to media, link status, driver version,
- bus location, and more.
+ ethtool utility is used for querying and
+ changing settings of an
+ device.
@@ -324,9 +314,7 @@
The GNU Free Documentation License (FDL)
- is a means of ensuring freedom for program documentation.
- The &FDP; uses the FDL for its official documentation. In
- fact, this document is licensed through the FDL. As is the
+ is a means of licensing program documentation. As is the
case with all freedoms, the FDL carries both rights and
responsibilities. You have the right to modify and
redistribute FDL materials, or create other works based on
@@ -342,12 +330,11 @@
The File Hierarchy Standard, or FHS, is a
- collaborative document that defines the names and locations
- of many files and directories on a Linux system. The FHS
- also sets standards for the types of files that should
- inhabit specific system directories. Refer to for more information
- about the FHS.
+ specification for the naming and organization of directories
+ on a Linux system. The FHS sets standards for the types of
+ files that should inhabit specific system directories.
+ Refer to for
+ more information about the FHS.
@@ -367,33 +354,10 @@
The fsck utility is a command line tool
- used to check and repair file systems. It is normally used
- with Linux file systems such as , but also has the ability to make
- repairs on some Windows file systems.
-
-
-
-
- fsh
-
-
- Remote command execution via a cryptographically strong
- method such as lsh or
- ssh is often slow, especially if either
- of the involved computers is slow. The process is slow
- because the client and the server must perform a series of
- complex calculations during connection establishment.
-
-
- The fsh utility uses
- lsh or ssh to
- establish a secure tunnel to the remote system. This process
- takes as long as a normal connection establishment. Once
- the tunnel is established, however, fsh
- reuses it to start new sessions on the remote system almost
- instantaneously. With this process, fsh
- combines the security of ssh and the speed of rsh.
+ used to test file systems for consistency and repair errors.
+ It is normally used with Linux file systems such as , but also has the ability to make
+ repairs on other types of file systems.
@@ -416,10 +380,11 @@
glibc
- The GNU C library, or glibc, is
- used as the C library in &FED;. Most software programs for
- your &FED; system rely on glibc for
- basic common functions. Refer to glibc, is a
+ free and open source library of C functions. Most software
+ programs for your &FED; system rely on
+ glibc for basic common functions.
+ Refer to for more
information about glibc.
@@ -430,14 +395,14 @@
GNOME is the short name for the GNOME
- Desktop, a product of the GNOME Project. GNOME is a
- complete, free and easy-to-use desktop environment for
- UNIX-like operating systems such as &FED;. It is also a
- powerful application development framework for software
- developers. GNOME provides a complete set of human
- interface guidelines, which means that GNOME strives to have
- a consistent look and feel for all its applications. Read
- more about GNOME at .
+ Desktop, a product of the GNOME Project. GNOME is at once a
+ free desktop environment for UNIX-like operating systems
+ such as &FED;, and a framework for software developers to
+ develop graphical utilities and interfaces. GNOME provides
+ a complete set of human interface guidelines, which means
+ that GNOME strives to have a consistent look and feel for
+ all its applications. Read more about GNOME at .
@@ -500,9 +465,11 @@
The GRand Unified Boot Loader,
- or GRUB, is a program which enables the
- user to select an operating system or kernel to boot. It
- also allows the user to pass arguments to the kernel. Refer
+ or GRUB, is a program which controls the
+ boot process after basic system tests occur. It presents a
+ menu that allows the user to select an operating system or
+ kernel to boot. Its features include passing parameters and
+ options to the kernel, and a minimal functional shell. Refer
to for more
information about GRUB.
@@ -532,9 +499,8 @@
Celeron, AMD Athlon and Duron, and VIA C3 s, are commonly referred to as
i386. The
- i386 term is often used as
- shorthand for the distribution set of files meant for this
- line of computers or processors.
+ i386 term is often used to refer a
+ set of software packages that run on these processors.
@@ -598,11 +564,12 @@
Internet Relay Chat, or IRC, is a
- real-time, text-based form of communication. You can use
- IRC to have conversations with individuals or groups. IRC
- is very similar to , and offers
- many of the same capabilities, but predates IM by many
- years.
+ communication protocol that allows users to type text
+ messages to each other in approximately real time. You can
+ use IRC to have conversations with individuals or groups.
+ IRC is very similar to , and
+ offers many of the same capabilities, but predates IM by
+ many years.
@@ -652,13 +619,14 @@
kickstart
- Many system administrators prefer to use an automated
- installation method to install &FED; on their machines. With
- kickstart, a system administrator can create a single file
- containing answers to all the questions asked during a &FED;
- installation. Refer to to complete the installation
+ process. Refer to for more
- information about kickstart.
+ information about Kickstart.
@@ -710,11 +678,9 @@
LILO
- The LInux LOader, or LILO, is a basic
- system program which boots your Linux system. LILO loads the
- Linux kernel from a floppy or a hard drive, boots the kernel
- and passes control of the system to the kernel. LILO can
- also boot other operating systems. LILO has been superseded
+ The LInux LOader, or LILO, is a small
+ program used on older Linux systems to boot the Linux kernel
+ or some other operating systems. LILO has been superseded
by in &FED;.
@@ -835,10 +801,7 @@
graphical display of your system and personal files.
Nautilus also allows you to configure your desktop and
&FED;, browse your photo collection, access your network
- resources, and more, all from an integrated interface. In
- essence, Nautilus becomes a shell for your entire desktop
- experience. Insert link to Nautilus
- resource here.
+ resources, and more, all from an integrated interface.
@@ -888,12 +851,11 @@
RHEL
- Red Hat Enterprise Linux, or &RHEL;, is
- the premiere operating system for open source computing.
- &RHEL; runs on many system architectures, is certified by
- top enterprise software and hardware vendors, and is backed
- by a &RHN; subscription and up to 24x7 support with one-hour
- response. Refer to &RHEL;, is a
+ fully-supported enterprise-class operating system for open
+ source computing. &RHEL; runs on many system architectures,
+ is certified by top enterprise software and hardware
+ vendors, and is based on &FED; technology. Refer to for more
information about &RHEL;.
@@ -950,9 +912,10 @@
rsync
- The rsync provides fast incremental file
- transfers. Administrators frequently use
- rsync to create a rsync utility is used to perform
+ incremental file transfers, meaning it can transfer only
+ sections of data that have changed. Administrators
+ frequently use rsync to create a of an online resource. Refer to
for more
information about rsync.
@@ -1032,9 +995,9 @@
A source , or
SRPM, contains the source code for a
- package. If you want to read or
- modify a program's source, use its SRPM. You do not need any
- SRPMs to install or use software.
+ package. To read or modify a
+ program's source, install its SRPM. You do not need SRPM
+ packages to use the software itself.
@@ -1058,11 +1021,10 @@
The up2date application is a
- complete system for managing and updating software on &RHEL;
- and &FED; systems. It has both command line and gui
- modes. The up2date application is
- no longer recommended for software management, since it has
- been superseded by yum. Refer to up2date
+ application has been superseded by
+ yum-based utilities. Refer to for more
information on managing software on your &FED; system.
@@ -1073,7 +1035,8 @@
The vino utility is a variant of used in &FC; 4 and beyond.
+ linkend="gl-jb-vnc"/> used in &FC; 4 and beyond for remote
+ assistance and control.
@@ -1081,11 +1044,14 @@
VNC
- VNC stands for Virtual Network
- Computing. It is remote control software which allows you to
- view and interact with another computer over the network.
- Refer to for more
- information about VNC.
+ Virtual Network Computing, or
+ VNC, is communication software
+ that allows you to view and interact with another computer
+ over the network. &FED; includes VNC server and client
+ software, as well as the customized package. Refer to for more information about
+ VNC.
@@ -1093,10 +1059,8 @@
XFS
- XFS is a journalling filesystem developed by SGI and used in
- SGI's IRIX operating system. It is also available for &FED;
- systems.. It is extremely scalable and has a journalling
- capability to protect against corruption. Refer to
for more information about XFS.
From fedora-docs-commits at redhat.com Wed Mar 15 04:09:48 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 14 Mar 2006 23:09:48 -0500
Subject: jargon-buster rpm-info.xml,1.3,1.4
Message-ID: <200603150410.k2F4AI3I029015@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/jargon-buster
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28970
Modified Files:
rpm-info.xml
Log Message:
Removed or revised remaining content not eligible for relicensing; now document is OPL
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/jargon-buster/rpm-info.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-info.xml 17 Feb 2006 22:59:34 -0000 1.3
+++ rpm-info.xml 15 Mar 2006 04:09:37 -0000 1.4
@@ -7,24 +7,17 @@
-
+
-
- GNU FDL
+ OPL1.0
- 2003
- 2004
- Dave Pawson
-
-
- 200320042005Red Hat, Inc.
@@ -43,6 +36,10 @@
+
+
+ Removed or revised all legacy information to allow relicensing
+
From fedora-docs-commits at redhat.com Wed Mar 15 04:13:12 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Tue, 14 Mar 2006 23:13:12 -0500
Subject: jargon-buster/en jargon-buster.xml,1.2,1.3
Message-ID: <200603150413.k2F4DDT3029073@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/jargon-buster/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv29051/en
Modified Files:
jargon-buster.xml
Log Message:
Correct stupid tag error
Index: jargon-buster.xml
===================================================================
RCS file: /cvs/docs/jargon-buster/en/jargon-buster.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- jargon-buster.xml 15 Mar 2006 04:09:46 -0000 1.2
+++ jargon-buster.xml 15 Mar 2006 04:13:04 -0000 1.3
@@ -12,48 +12,49 @@
]>
-
This document clarifies some of the terms used on various lists, web
pages, and IRC, when talking about &FED;. Many thanks to the people
- on the fedora-list and at &RH; for their input. If you cannot find
- a term in this document that you think should appear here, use the
- bug reporting information below to notify the maintainers.
+ on the fedora-list and at &RH; for their input. If you cannot find a
+ term in this document that you think should appear here, use the bug
+ reporting information below to notify the maintainers.
-
+
GlossaryJargon Buster
- a11y
-
-
- An abbreviation for "accessibility," frequently used in
- programming to avoid unnecessary typing and misspelling.
- Accessibility is the provision of services for impaired
- users, such as text-to-speech translation for the visually
- impaired. The 11 derives from the eleven
- letters between the beginning a and the
- ending y.
-
-
+ a11y
+
+
+ An abbreviation for "accessibility," frequently used in
+ programming to avoid unnecessary typing and misspelling.
+ Accessibility is the provision of services for impaired
+ users, such as text-to-speech translation for the visually
+ impaired. The 11 derives from the eleven
+ letters between the beginning a and the
+ ending y.
+
+ ALSA
The Advanced Linux Sound Architecture (ALSA) is a technology
- that gives &FED; the ability to mix and output multiple
- audio sources. ALSA supports many consumer and professional
- level hardware devices. Refer to for more information.
+ that gives &FED; the ability to mix and output multiple
+ audio sources. ALSA supports many consumer and professional
+ level hardware devices. Refer to
+ for more
+ information.
@@ -62,14 +63,16 @@
Anaconda is the &FC; installation
- system. Anaconda identifies and
- configures the system's hardware, creates appropriate file
- systems, and installs or upgrades software packages.
- Anaconda runs in a fully
- interactive text or graphical mode, or in an automated mode. Refer to for more
- information.
+ system. Anaconda identifies and
+ configures the system's hardware, creates appropriate file
+ systems, and installs or upgrades software packages.
+ Anaconda runs in a fully
+ interactive text or graphical mode, or in an automated
+ mode. Refer to
+
+ for more information.
@@ -77,14 +80,15 @@
apt
- The apt (Advanced Package Tool) utility
- is a dependency tool developed for use with Debian Linux
- dpkg packages. The
- apt-rpm utility extends
- apt for use with RPM packages. Since
- apt has specific problems with
- multilib, however, it is not
- recommended for use with &FED; systems. Use apt (Advanced Package Tool) utility
+ is a dependency tool developed for use with Debian Linux
+ dpkg packages. The
+ apt-rpm utility extends
+ apt for use with RPM packages. Since
+ apt has specific problems with
+ multilib, however, it is not
+ recommended for use with &FED; systems. Use
+ instead.
@@ -94,8 +98,8 @@
ATrpms a third party RPM repository for &FED; software.
- Refer to
- for more information about ATrpms.
+ Refer to
+ for more information about ATrpms.
@@ -103,18 +107,21 @@
BitTorrent
- BitTorrent is a peer-to-peer
- file sharing which downloads from multiple channels at
- once. Refer to for more
- information.
+ BitTorrent is a peer-to-peer file
+ sharing which downloads from multiple channels at once.
+ Refer to
+
+ for more information.
-
+
Use BitTorrent to download &FC;
- by downloading and opening a torrent file. The official
- &FC; torrent tracker is located at . Download a
- torrent file there to begin downloading a release of &FC;.
+ by downloading and opening a torrent file. The official &FC;
+ torrent tracker is located at
+ .
+ Download a torrent file there to begin downloading a release
+ of &FC;.
@@ -123,11 +130,11 @@
Bluecurve is a theme which unifies
- the look and feel of the &FED; desktop. Bluecurve was
+ the look and feel of the &FED; desktop. Bluecurve was
introduced in &RHL; 9 and was used as the default for &FC;
- through release 3. Bluecurve was replaced in &FC; 4 by
- . Bluecurve included
- icons and settings for the menu and layout of the desktop.
+ through release 3. Bluecurve was replaced in &FC; 4 by
+ . Bluecurve included icons
+ and settings for the menu and layout of the desktop.
@@ -137,77 +144,79 @@
&BZ; is an online database for recording flaws, or
bugs, in &FED; software,
- documentation, and other projects. &BZ; also tracks bugs in
- &RH; software. When you encounter a problem with &FED;, you
+ documentation, and other projects. &BZ; also tracks bugs in
+ &RH; software. When you encounter a problem with &FED;, you
can help the community fix the problem by making a record in
- &BZ;. This procedure is called "entering a bug." For more
+ &BZ;. This procedure is called "entering a bug." For more
information about &BZ;, refer to &BZ-URL;.
- CJK
-
-
- An abbreviation for "Chinese, Japanese and Korean," East
- Asian languages which require the use of an platform due to the large number
- of possible typographic characters.
-
-
-
+ CJK
+
+
+ An abbreviation for "Chinese, Japanese and Korean," East
+ Asian languages which require the use of an
+ platform due to
+ the large number of possible typographic characters.
+
+
+
- Clearlooks
-
-
- Clearlooks is the default theme for a GNOME desktop
- environment in &FC; 4. The Clearlooks design is based on
- the original .
-
-
+ Clearlooks
+
+
+ Clearlooks is the default theme for a GNOME desktop
+ environment in &FC; 4. The Clearlooks design is based on the
+ original .
+
+ Core
- Core is a numbered release of a subset of &FED; software,
- and is usually called "&FC;." Core packages are maintained
- mainly by employees of &RH;, and are made up of free and
- open source software produced by the Linux community.
-
-
- Although the software in &FC; is updated regularly, the
- original release of &FC; does not change. For this reason,
- when users discuss the state of their &FED; system software,
- they might refer to "&FC; plus updates." When you request
- help from the community, this terminology is the most
- accurate. However, many users simply call the updated
- system "&FC;."
+ Core is a numbered release of a subset of &FED; software,
+ and is usually called "&FC;." Core packages are maintained
+ mainly by employees of &RH;, and are made up of free and
+ open source software produced by the Linux community.
+
+
+ Although the software in &FC; is updated regularly, the
+ original release of &FC; does not change. For this reason,
+ when users discuss the state of their &FED; system software,
+ they might refer to "&FC; plus updates." When you request
+ help from the community, this terminology is the most
+ accurate. However, many users simply call the updated system
+ "&FC;."
- CPU
-
-
- The Central Processing Unit, or CPU, is
- the "brain" of a computer. The rest of the computer is
- organized around the CPU, so people often refer to computer
- systems by the type of processor inside. Examples of CPUs
- include Pentium-4, Athlon64, and PowerPC.
-
-
+ CPU
+
+
+ The Central Processing Unit, or
+ CPU
+ , is the "brain" of a computer. The rest of the computer is
+ organized around the CPU, so people often refer to computer
+ systems by the type of processor inside. Examples of CPUs
+ include Pentium-4, Athlon64, and PowerPC.
+
+ cron
The cron system executes automatic jobs
- on behalf of the system or an individual user on a schedule.
- An example of a system cron job might
- include running nightly to update
- the system.
+ on behalf of the system or an individual user on a schedule.
+ An example of a system cron job might
+ include running nightly to
+ update the system.
@@ -215,15 +224,16 @@
CUPS
- The Common UNIX Printing System, or CUPS,
- is a cross-platform, modularized printing system for UNIX-type
- environments, including Linux and Macintosh OS X. It is
- based on the Internet Printing Protocol and provides
- facilities for managing print jobs and queues. CUPS drivers
- are available at
- which allow Windows systems to use printers shared from
- Linux systems. Refer to
- for more information about CUPS.
+ The Common UNIX Printing System, or
+ CUPS
+ , is a cross-platform, modularized printing system for
+ UNIX-type environments, including Linux and Macintosh OS X.
+ It is based on the Internet Printing Protocol and provides
+ facilities for managing print jobs and queues. CUPS drivers
+ are available at
+ which allow Windows systems to use printers shared from
+ Linux systems. Refer to
+ for more information about CUPS.
@@ -232,32 +242,35 @@
The Desktop Switcher tool allows
- a user to convert the &FED; desktop between and . To
- run the Desktop Switcher tool
- from the Main Menu, select
- DesktopPreferencesMore
- PreferencesDesktop
- Switcher. If you do not see this
- item in your menu, you may not have the
- switchdesk-gui package installed. Refer
- to &FDPDOCS-URL; to learn how to use to install software packages.
-
+ a user to convert the &FED; desktop between
+ and
+ . To run the Desktop
+ Switcher tool from the Main Menu, select
+ DesktopPreferencesMore
+ PreferencesDesktop
+ Switcher. If you do not see this
+ item in your menu, you may not have the
+ switchdesk-gui package installed. Refer
+ to &FDPDOCS-URL; to learn how to use
+ to install software
+ packages.
+
- eth0
-
-
- The eth0 name represents the first
- discovered interface in a
- &FED; system. If your &FED; system has more than one such
- interface, the others will be numbered
- eth1,
- eth2, and so on.
-
-
+ eth0
+
+
+ The eth0 name represents the first
+ discovered interface in a
+ &FED; system. If your &FED; system has more than one such
+ interface, the others will be numbered
+ eth1,
+ eth2, and so on.
+
+ Ethernet
@@ -274,7 +287,7 @@
The ethtool utility is a Linux network
driver diagnostic and tuning tool for a Linux 2.4 or later
- . The
+ . The
ethtool utility is used for querying and
changing settings of an
device.
@@ -282,30 +295,34 @@
- ext3
-
-
- The ext3 file system is a method of
- organizing data on storage devices. It is based on the
- older but still vital ext2 Linux
- file system. Most users do not need to understand file
- system internals because Linux translates this system into
- understandable concepts such as files and folders. Refer to
- , however,
- for more information on ext2 and
- ext3.
-
-
+ ext3
+
+
+ The ext3 file system is a method of
+ organizing data on storage devices. It is based on the older
+ but still vital ext2 Linux file
+ system. Most users do not need to understand file system
+ internals because Linux translates this system into
+ understandable concepts such as files and folders. Refer to
+ , however,
+ for more information on ext2 and
+ ext3.
+
+ FAQ
- A FAQ is a list of Frequently Asked
- Questions. Refer to for a FAQ about
- the &FP;. Refer to for a FAQ about using &FED;.
+ A
+ FAQ
+ is a list of Frequently Asked Questions. Refer to
+
+ for a FAQ about the &FP;. Refer to
+ for a FAQ
+ about using &FED;.
@@ -313,15 +330,16 @@
FDL
- The GNU Free Documentation License (FDL)
- is a means of licensing program documentation. As is the
- case with all freedoms, the FDL carries both rights and
- responsibilities. You have the right to modify and
- redistribute FDL materials, or create other works based on
- them. You then have the responsibility of licensing any
- such material under the FDL as well. In this fashion the
- FDL guarantees that documentation cannot be made less free
- by a recipient.
+ The GNU Free Documentation License (
+ FDL
+ ) is a means of licensing program documentation. As is the
+ case with all freedoms, the FDL carries both rights and
+ responsibilities. You have the right to modify and
+ redistribute FDL materials, or create other works based on
+ them. You then have the responsibility of licensing any such
+ material under the FDL as well. In this fashion the FDL
+ guarantees that documentation cannot be made less free by a
+ recipient.
@@ -329,12 +347,14 @@
FHS
- The File Hierarchy Standard, or FHS, is a
- specification for the naming and organization of directories
- on a Linux system. The FHS sets standards for the types of
- files that should inhabit specific system directories.
- Refer to for
- more information about the FHS.
+ The File Hierarchy Standard, or
+ FHS
+ , is a specification for the naming and organization of
+ directories on a Linux system. The FHS sets standards for
+ the types of files that should inhabit specific system
+ directories. Refer to
+ for more
+ information about the FHS.
@@ -343,9 +363,11 @@
A third-party repository of
- software packages. FreshRPMS is soon to be subsumed into
- the larger RPMForge repository. Refer to for more information.
+ software packages. FreshRPMS is soon to be subsumed into the
+ larger RPMForge repository. Refer to
+ for
+ more information.
@@ -354,10 +376,11 @@
The fsck utility is a command line tool
- used to test file systems for consistency and repair errors.
- It is normally used with Linux file systems such as , but also has the ability to make
- repairs on other types of file systems.
+ used to test file systems for consistency and repair errors.
+ It is normally used with Linux file systems such as
+ , but also has the ability
+ to make repairs on other types of file systems.
@@ -366,13 +389,13 @@
The GIMP is the GNU Image Manipulation Program. The GIMP is
- graphics software suitable for such tasks as photo
- retouching, image composition and image authoring. The GIMP
- will read and write graphics files in a variety of formats,
- including JPG, PNG, BMP, GIF. It will also import some
- proprietary image formats from other graphics programs.
- Refer to for more
- information about the GIMP.
+ graphics software suitable for such tasks as photo
+ retouching, image composition and image authoring. The GIMP
+ will read and write graphics files in a variety of formats,
+ including JPG, PNG, BMP, GIF. It will also import some
+ proprietary image formats from other graphics programs.
+ Refer to for more
+ information about the GIMP.
@@ -381,12 +404,13 @@
The GNU C library, or glibc, is a
- free and open source library of C functions. Most software
+ free and open source library of C functions. Most software
programs for your &FED; system rely on
glibc for basic common functions.
- Refer to for more
- information about glibc.
+ Refer to
+
+ for more information about glibc.
@@ -394,46 +418,52 @@
GNOME
- GNOME is the short name for the GNOME
- Desktop, a product of the GNOME Project. GNOME is at once a
- free desktop environment for UNIX-like operating systems
- such as &FED;, and a framework for software developers to
- develop graphical utilities and interfaces. GNOME provides
- a complete set of human interface guidelines, which means
- that GNOME strives to have a consistent look and feel for
- all its applications. Read more about GNOME at GNOME
+ is the short name for the GNOME Desktop, a product of the
+ GNOME Project. GNOME is at once a free desktop environment
+ for UNIX-like operating systems such as &FED;, and a
+ framework for software developers to develop graphical
+ utilities and interfaces. GNOME provides a complete set of
+ human interface guidelines, which means that GNOME strives
+ to have a consistent look and feel for all its applications.
+ Read more about GNOME at
+ .
- GNU
-
-
- GNU is an acronym that stands for "GNU's
- Not UNIX," and is pronounced "guh-NOO." GNU was originally
- intended to be a complete UNIX-like operating system. It
- has become a broader term describing free software licensed
- under the . Because the and much of the other software in a
- Linux system are licensed under the , many people call that system
- GNU/Linux.
-
-
+ GNU
+
+
+ GNU
+ is an acronym that stands for "GNU's Not UNIX," and is
+ pronounced "guh-NOO." GNU was originally intended to be a
+ complete UNIX-like operating system. It has become a broader
+ term describing free software licensed under the
+ . Because the
+ and much of the other
+ software in a Linux system are licensed under the
+ , many people call that
+ system GNU/Linux.
+
+ GnuPG (GPG)
GnuPG, the GNU Privacy Guard, is a complete and free
- replacement for PGP, Pretty Good Privacy. GnuPG software
+ replacement for PGP, Pretty Good Privacy. GnuPG software
allows you to digitally sign or encrypt data using public
- key encryption methods. GnuPG is OpenPGP compliant, so data
+ key encryption methods. GnuPG is OpenPGP compliant, so data
signed or encrypted by GnuPG can be exchanged with almost
- any computer user. Refer to for more information about
- GPG.
+ any computer user. Refer to
+ for more
+ information about GPG.
@@ -441,21 +471,26 @@
GPL
- The GNU General Public Licence, or GPL,
- is a software license designed to preserve users' rights to
- share and modify software. The GPL does this by restricting
- anyone from denying you those rights. Use of software is
- usually subject to the terms under which it is licensed.
- Many software licenses restrict you from copying, sharing,
- or even examining the software they cover. The terms of the
- GPL, however, allow you very broad rights to share, modify,
- and redistribute software. In return the GPL requires you
- to give others those rights if you share the results. The
- GPL encourages software programmers to learn and contribute
- to each other's work. Refer to for
- more information about the GPL. For a about the GPL, refer to GPL
+ , is a software license designed to preserve users' rights
+ to share and modify software. The GPL does this by
+ restricting anyone from denying you those rights. Use of
+ software is usually subject to the terms under which it is
+ licensed. Many software licenses restrict you from copying,
+ sharing, or even examining the software they cover. The
+ terms of the GPL, however, allow you very broad rights to
+ share, modify, and redistribute software. In return the GPL
+ requires you to give others those rights if you share the
+ results. The GPL encourages software programmers to learn
+ and contribute to each other's work. Refer to
+
+ for more information about the GPL. For a
+ about the GPL, refer
+ to
+ .
@@ -465,30 +500,32 @@
The GRand Unified Boot Loader,
- or GRUB, is a program which controls the
- boot process after basic system tests occur. It presents a
- menu that allows the user to select an operating system or
- kernel to boot. Its features include passing parameters and
- options to the kernel, and a minimal functional shell. Refer
- to for more
- information about GRUB.
+ or
+ GRUB
+ , is a program which controls the boot process after basic
+ system tests occur. It presents a menu that allows the user
+ to select an operating system or kernel to boot. Its
+ features include passing parameters and options to the
+ kernel, and a minimal functional shell. Refer to
+ for more
+ information about GRUB.
- i18n
-
-
- An abbreviation for "internationalization," frequently used
- in programming to avoid unnecessary typing and misspellings.
- Internationalization is the provision of multiple
- translations for messages that applications produce. The
- 18 derives from the eighteen (18) letters
- between the beginning i and the ending
- n.
-
-
-
+ i18n
+
+
+ An abbreviation for "internationalization," frequently used
+ in programming to avoid unnecessary typing and misspellings.
+ Internationalization is the provision of multiple
+ translations for messages that applications produce. The
+ 18 derives from the eighteen (18) letters
+ between the beginning i and the ending
+ n.
+
+
+ i386
@@ -496,80 +533,84 @@
The entire set of computer processors that are compatible
with the Intel x86 platform, including Intel Pentium and
- Celeron, AMD Athlon and Duron, and VIA C3 s, are commonly referred to as
- i386. The
+ Celeron, AMD Athlon and Duron, and VIA C3
+ s, are commonly
+ referred to as i386. The
i386 term is often used to refer a
set of software packages that run on these processors.
- IIIMF
-
-
- The Intranet/Internet Input Method Framework, or
- IIIMF, is an framework for handling languages
- such as , which will not map readily
- to a standard keyboard device. IIIMF works by loading
- language engines dynamically at runtime as they are
- requested by clients.
-
-
+ IIIMF
+
+
+ The Intranet/Internet Input Method Framework, or
+ IIIMF
+ , is an framework
+ for handling languages such as ,
+ which will not map readily to a standard keyboard device.
+ IIIMF works by loading language engines dynamically at
+ runtime as they are requested by clients.
+
+
- IM
-
-
- Instant messaging, or IM, is a real-time,
- text-based form of communication. You can use IM to have
- conversations with individuals or groups. America Online, an
- Internet service provider, popularized IM in the 1990's, but
- many other providers such as Yahoo and Google offer similar
- services. &FED; has programs such as
- gaim that allow you to use IM to
- communicate with other Internet users.
-
-
+ IM
+
+
+ Instant messaging, or
+ IM
+ , is a real-time, text-based form of communication. You can
+ use IM to have conversations with individuals or groups.
+ America Online, an Internet service provider, popularized IM
+ in the 1990's, but many other providers such as Yahoo and
+ Google offer similar services. &FED; has programs such as
+ gaim that allow you to use IM to
+ communicate with other Internet users.
+
+
- Inkscape
-
-
- Inkscape is a vector graphics illustration program. It uses
- SVG as the default file format. For more information about
- Inkscape, refer to .
-
-
-
+ Inkscape
+
+
+ Inkscape is a vector graphics illustration program. It uses
+ SVG as the default file format. For more information about
+ Inkscape, refer to .
+
+
+
- Input method
-
-
- A method used to enter text other than selecting each
- character directly on a keyboard or other input
- hardware. Input methods are widely used for entering
- ideographs and other characters phonetically or by
- component, such as in Esat Asian languages. &FC; uses the
- platform by default, but also
- offers other platforms such as .
-
-
-
+ Input method
+
+
+ A method used to enter text other than selecting each
+ character directly on a keyboard or other input hardware.
+ Input methods are widely used for entering ideographs and
+ other characters phonetically or by component, such as in
+ Esat Asian languages. &FC; uses the
+ platform by default, but also
+ offers other platforms such as .
+
+
+ IRC
- Internet Relay Chat, or IRC, is a
- communication protocol that allows users to type text
- messages to each other in approximately real time. You can
- use IRC to have conversations with individuals or groups.
- IRC is very similar to , and
- offers many of the same capabilities, but predates IM by
- many years.
+ Internet Relay Chat, or
+ IRC
+ , is a communication protocol that allows users to type text
+ messages to each other in approximately real time. You can
+ use IRC to have conversations with individuals or groups.
+ IRC is very similar to , and
+ offers many of the same capabilities, but predates IM by
+ many years.
@@ -577,15 +618,15 @@
ISO
- ISO is an acronym that stands for
- International Standards Organization. It is also used as an
- abbreviation for the ISO-9660 format of a standard data
- CD-ROM. &FED; offers installation CDs for &FC; as
- downloadable files on the Internet, in the form of CD image
- files sometimes called ISO files. These files can be burned
- directly to CD media using a CD-Recordable drive, and the
- resulting CD will contain all the files on the original &FC;
- media.
+ ISO
+ is an acronym that stands for International Standards
+ Organization. It is also used as an abbreviation for the
+ ISO-9660 format of a standard data CD-ROM. &FED; offers
+ installation CDs for &FC; as downloadable files on the
+ Internet, in the form of CD image files sometimes called ISO
+ files. These files can be burned directly to CD media using
+ a CD-Recordable drive, and the resulting CD will contain all
+ the files on the original &FC; media.
@@ -594,11 +635,12 @@
KDE is a free and open desktop environment for UNIX-like
- operating systems such as &FED;. KDE also offers a complete
+ operating systems such as &FED;. KDE also offers a complete
development framework for writing graphical applications, as
- well as an office application suite. Refer to for more information
- about KDE.
+ well as an office application suite. Refer to
+ for
+ more information about KDE.
@@ -607,9 +649,9 @@
A kernel is the core of an operating system, responsible for
- managing memory and conducting hardware operations. The
+ managing memory and conducting hardware operations. The
Linux kernel used in &FED; is free and open source software,
- originally written by Linus Torvalds. Many computer
+ originally written by Linus Torvalds. Many computer
scientists and programmers from around the world now
contribute to its development.
@@ -620,13 +662,15 @@
Kickstart is a facility that allows system administrators to
- automate the installation of &FED;. To use Kickstart, the
- administrator creates a configuration file which contains
- all the information needed by to complete the installation
- process. Refer to for more
- information about Kickstart.
+ automate the installation of &FED;. To use Kickstart, the
+ administrator creates a configuration file which contains
+ all the information needed by
+ to complete the
+ installation process. Refer to
+
+ for more information about Kickstart.
@@ -635,42 +679,44 @@
The kudzu utility usually runs at boot
- time. The kudzu utility detects changes
- in the system's hardware configuration, and configures the
- devices for use with &FED; software. Refer to kudzu utility detects changes
+ in the system's hardware configuration, and configures the
+ devices for use with &FED; software. Refer to
+
- for more information about kudzu.
+ for more information about kudzu.
- l10n
-
-
- An abbreviation for "localization," frequently used in
- programming to avoid unnecessary typing and misspelling.
- Localization is the provision of nation-specific settings
- for the representation of numbers, dates, currency, and
- other customary symbols. The 10 derives
- from the ten letters between the beginning
- l and the ending n.
-
-
-
+ l10n
+
+
+ An abbreviation for "localization," frequently used in
+ programming to avoid unnecessary typing and misspelling.
+ Localization is the provision of nation-specific settings
+ for the representation of numbers, dates, currency, and
+ other customary symbols. The 10 derives
+ from the ten letters between the beginning
+ l and the ending n.
+
+
+ LDAP
The Lightweight Directory Access Protocol, or
- LDAP, is a standard for hierarchically
- organizing and accessing collections of information. This
- information may be practically anything, but LDAP is most
- often used to collect information about organizations,
- including personnel and resource information. &FED;
- includes support for OpenLDAP, which is a free and open
- source implementation of LDAP. For more information about
- OpenLDAP, refer to .
+ LDAP
+ , is a standard for hierarchically organizing and accessing
+ collections of information. This information may be
+ practically anything, but LDAP is most often used to collect
+ information about organizations, including personnel and
+ resource information. &FED; includes support for OpenLDAP,
+ which is a free and open source implementation of LDAP. For
+ more information about OpenLDAP, refer to
+ .
@@ -678,10 +724,11 @@
LILO
- The LInux LOader, or LILO, is a small
- program used on older Linux systems to boot the Linux kernel
- or some other operating systems. LILO has been superseded
- by in &FED;.
+ The LInux LOader, or
+ LILO
+ , is a small program used on older Linux systems to boot the
+ Linux kernel or some other operating systems. LILO has been
+ superseded by in &FED;.
@@ -689,10 +736,12 @@
LSB
- The Linux Standard Base, or LSB, is a
- project that develops and promotes a set of standards to
- increase compatibility among Linux distributions. For more
- information about LSB, refer to LSB
+ , is a project that develops and promotes a set of standards
+ to increase compatibility among Linux distributions. For
+ more information about LSB, refer to
+ .
@@ -703,7 +752,7 @@
The lspci utility displays information
about all PCI buses in the system and all devices connected
- to them. It is frequently used to diagnose problems with
+ to them. It is frequently used to diagnose problems with
hardware recognition or driver compatibility.
@@ -713,14 +762,15 @@
The md5sum utility computes a 128-bit
- message digest hash value for any specified files. A hash
+ message digest hash value for any specified files. A hash
value is a "fingerprint" for a given file, created by a
computation that makes it very unlikely that any two files
will create the same hash value.
-
+
- To download an MD5 hash program for Windows operating
- systems, refer to .
@@ -730,53 +780,56 @@
The &FC; Installation CD 1 includes a memory testing utility
- called memtest86. To perform memory
+ called memtest86. To perform memory
testing before you install Fedora Core, or to diagnose a RAM
problem, enter memtest86 at the
- boot: prompt. The tests continue until you
- press the Esc key.
+ boot:
+ prompt. The tests continue until you press the
+ Esc key.
- mirror
-
-
- A mirror is a complete copy of an online resource. System
- administrators of computers connected to the Internet often
- create and provide mirrors for public use. If a resource
- has one or more mirrors, many more users can access its
- content without overloading the original resource.
-
-
+ mirror
+
+
+ A mirror is a complete copy of an online resource. System
+ administrators of computers connected to the Internet often
+ create and provide mirrors for public use. If a resource has
+ one or more mirrors, many more users can access its content
+ without overloading the original resource.
+
+ mount
To use a disk device such as a CD, USB drive, or floppy
- diskette, you must first mount it. &FED;
+ diskette, you must first mount it. &FED;
uses a single unified file system for all attached devices.
Windows systems, on the other hand, use a "drive letter" for
each disk device, such as A: or
- C:. When you
+ C:. When you
mount a disk device, its file system
- becomes part of the unified file system on &FED;. The
- device is mounted on a mount point,
- which is a directory that points to that device, such as
- /media/floppy. You must also unmount
+ becomes part of the unified file system on &FED;. The device
+ is mounted on a mount point, which is
+ a directory that points to that device, such as
+ /media/floppy. You must also unmount
the file system before you eject or remove the disk, to
insure all file information is safely written to the device.
-
- Since these functions are often handled through
- user-friendly helpers, you may perform all mounting,
- unmounting, and file browsing through the graphical desktop
- interface. For instance, if you use the Desktop, the file management utility makes it
- easy to perform these tasks.
-
+
+ Since these functions are often handled through
+ user-friendly helpers, you may perform all mounting,
+ unmounting, and file browsing through the graphical desktop
+ interface. For instance, if you use the
+ Desktop, the
+ file management
+ utility makes it easy to perform these tasks.
+
@@ -787,7 +840,8 @@
as the Firefox web browser and the Thunderbird email client.
These programs are designed for standards compliance,
performance and portability. For more information about
- Mozilla software, refer to .
@@ -797,11 +851,11 @@
The desktop environment
- includes a file manager called Nautilus which provides a
- graphical display of your system and personal files.
- Nautilus also allows you to configure your desktop and
- &FED;, browse your photo collection, access your network
- resources, and more, all from an integrated interface.
+ includes a file manager called Nautilus which provides a
+ graphical display of your system and personal files.
+ Nautilus also allows you to configure your desktop and
+ &FED;, browse your photo collection, access your network
+ resources, and more, all from an integrated interface.
@@ -811,19 +865,21 @@
Users often refer to a file as a
package.
-
-
+
+ Pine
- Pine, short for a Program for Internet
- News and Email, is a tool for reading, sending, and managing
- electronic messages. Refer to for more information
- about Pine.
+ Pine
+ , short for a Program for Internet News and Email, is a tool
+ for reading, sending, and managing electronic messages.
+ Refer to
+
+ for more information about Pine.
@@ -832,18 +888,18 @@
Rawhide is a package repository which contains the latest
- development versions of packages which will eventually be
- included in &FED;. These latest versions are sometimes
- called "bleeding edge" , since they often
- include new and untested technology. You should consider
- the Rawhide repository "unstable," since any Rawhide package
- might be badly broken if the
- programmers are trying to add, change, or test features. If
- you want to develop programs for &FED;, you may want to
- install a system from Rawhide. If you only want to use a
- stable &FED; system, you should use the standard &FC;
- distribution instead.
+ development versions of packages which will eventually be
+ included in &FED;. These latest versions are sometimes
+ called "bleeding edge" ,
+ since they often include new and untested technology. You
+ should consider the Rawhide repository "unstable," since any
+ Rawhide package might be badly broken
+ if the programmers are trying to add, change, or test
+ features. If you want to develop programs for &FED;, you may
+ want to install a system from Rawhide. If you only want to
+ use a stable &FED; system, you should use the standard &FC;
+ distribution instead.
@@ -851,13 +907,15 @@
RHEL
- Red Hat Enterprise Linux, or &RHEL;, is a
- fully-supported enterprise-class operating system for open
- source computing. &RHEL; runs on many system architectures,
- is certified by top enterprise software and hardware
- vendors, and is based on &FED; technology. Refer to for more
- information about &RHEL;.
+ Red Hat Enterprise Linux, or
+ &RHEL;
+ , is a fully-supported enterprise-class operating system for
+ open source computing. &RHEL; runs on many system
+ architectures, is certified by top enterprise software and
+ hardware vendors, and is based on &FED; technology. Refer to
+
+ for more information about &RHEL;.
@@ -865,15 +923,15 @@
rhgb
- &RH; Graphical Boot, or
- rhgb, is an
- optional component of the boot process. The
- rhgb application produces a boot
- screen with a progress bar and fewer technical messages.
- The rhgb application allows you
- to click a link to see the technical boot messages if
- desired. Systems that have been upgraded from &RHL; to &FC;
- are not configured to include
+ &RH; Graphical Boot, or
+ rhgb
+ , is an optional component of the boot
+ process. The rhgb application
+ produces a boot screen with a progress bar and fewer
+ technical messages. The rhgb
+ application allows you to click a link to see the technical
+ boot messages if desired. Systems that have been upgraded
+ from &RHL; to &FC; are not configured to include
rhgb.
@@ -885,10 +943,12 @@
The rhn-applet utility was
originally designed for use with &RHEL; and Red Hat Network.
It provides a notification and user interface for system
- updates using . It allows
- the user to retrieve and install system updates, but this
- usage is no longer recommended. Users should use for system updates instead.
+ updates using . It allows the
+ user to retrieve and install system updates, but this usage
+ is no longer recommended. Users should use
+ for system updates
+ instead.
@@ -896,15 +956,16 @@
RPM
- RPM stands for RPM Package Manager. RPM
- is a robust database system for maintaining software on
- &FED; systems. Software packaged for &FED; is distributed
- in special package files called RPM files, or RPMs. System
- owners use the rpm utility to query the
- RPM database for information about installed software.
- Although some administrators use rpm to
- install, update, and remove software, it is recommended that
- you use yum for these purposes.
+ RPM
+ stands for RPM Package Manager. RPM is a robust database
+ system for maintaining software on &FED; systems. Software
+ packaged for &FED; is distributed in special package files
+ called RPM files, or RPMs. System owners use the
+ rpm utility to query the RPM database for
+ information about installed software. Although some
+ administrators use rpm to install,
+ update, and remove software, it is recommended that you use
+ yum for these purposes.
@@ -914,39 +975,46 @@
The rsync utility is used to perform
incremental file transfers, meaning it can transfer only
- sections of data that have changed. Administrators
- frequently use rsync to create a of an online resource. Refer to
+ sections of data that have changed. Administrators
+ frequently use rsync to create a
+ of an online
+ resource. Refer to
for more
information about rsync.
- SCIM
-
-
- The Smart Common Input Method platform, or
- SCIM, is a C++ library that abstracts
- input method interface into simple, independent classes.
- It provides a higher level and simpler interface than some
- other input method platforms.
-
-
-
+ SCIM
+
+
+ The Smart Common Input Method platform, or
+ SCIM
+ , is a C++ library that abstracts input method interface
+ into simple, independent classes. It provides a higher level
+ and simpler interface than some other input method
+ platforms.
+
+
+ SELinux
- SELinux is a set of extensions to the Linux that provide extremely strong
- security. SELinux is based on role definitions, and allows
- very granular control over access to system resources based
- on those roles. These security measures limit the risk
- associated with computer intrusions by unauthorized persons.
- For more information about SELinux, refer to and that provide
+ extremely strong security. SELinux is based on role
+ definitions, and allows very granular control over access to
+ system resources based on those roles. These security
+ measures limit the risk associated with computer intrusions
+ by unauthorized persons. For more information about SELinux,
+ refer to
+ and
+ .
@@ -956,23 +1024,24 @@
The sha1sum utility computes a 160-bit
- message digest hash value for any specified files. A hash
+ message digest hash value for any specified files. A hash
value is a "fingerprint" for a given file, created by a
computation that makes it very unlikely that any two files
will create the same hash value.
-
-
+
+
Download mirrors for &FC; image
- files also include a related SHA1SUMS file which contains the
- hash values for the files. Run
- sha1sum against the downloaded files to
- verify the hash value. If a file's hash value does not
- match, you should not use that file to burn a CD. Try
+ files also include a related SHA1SUMS file which contains
+ the hash values for the files.
+ Run sha1sum against the downloaded files
+ to verify the hash value. If a file's hash value does not
+ match, you should not use that file to burn a CD. Try
downloading the file again.
- To download an SHA-1 hash program for Windows operating
- systems, refer to .
@@ -982,11 +1051,12 @@
Sodipodi is a vector graphics illustration application. It
- uses W3C SVG as its default format. Refer to for more
- information.
+ uses W3C SVG as its default format. Refer to
+
+ for more information.
-
+
@@ -994,10 +1064,11 @@
A source , or
- SRPM, contains the source code for a
- package. To read or modify a
- program's source, install its SRPM. You do not need SRPM
- packages to use the software itself.
+ SRPM
+ , contains the source code for a
+ package. To read or modify a program's source, install its
+ SRPM. You do not need SRPM packages to use the software
+ itself.
@@ -1008,11 +1079,13 @@
The system-config-packages
utility is a package installation for new &FC; systems which
- have no software updates installed yet. Since most
+ have no software updates installed yet. Since most
administrators and users update their system software
regularly, system-config-packages
- is not often used. Users should instead use the utility to install new software.
+ is not often used. Users should instead use the
+ utility to install
+ new software.
@@ -1022,23 +1095,26 @@
The up2date application is a
utility for managing and updating software on &RHEL; and
- &FED; systems. The up2date
+ &FED; systems. The up2date
application has been superseded by
- yum-based utilities. Refer to for more
- information on managing software on your &FED; system.
+ yum-based utilities. Refer to
+
+ for more information on managing software on your &FED;
+ system.
- vino
-
-
- The vino utility is a variant of used in &FC; 4 and beyond for remote
- assistance and control.
-
-
+ vino
+
+
+ The vino utility is a variant of
+ used in &FC; 4 and beyond
+ for remote assistance and control.
+
+ VNC
@@ -1047,11 +1123,13 @@
Virtual Network Computing, or
VNC, is communication software
that allows you to view and interact with another computer
- over the network. &FED; includes VNC server and client
- software, as well as the customized package. Refer to for more information about
- VNC.
+ over the network. &FED; includes VNC server and client
+ software, as well as the customized
+ package. Refer to
+ for more
+ information about VNC.
@@ -1060,7 +1138,8 @@
XFS is a scalable journaling filesystem developed by SGI and
- available for &FED; systems. Refer to
for more information about XFS.
@@ -1072,8 +1151,8 @@
The X Window System, or simply "X," is the underlying
technology for GNOME, KDE, and other graphical environments
- used in &FED;. X is a network-based system for displaying
- and communicating graphical input and output. It is very
+ used in &FED;. X is a network-based system for displaying
+ and communicating graphical input and output. It is very
flexible and is suitable for a wide variety of
configurations such as remote desktops and thin-client
applications.
@@ -1081,33 +1160,35 @@
- Xen
-
-
- Xen is an open source virtual machine monitor for Intel x86
- machines which supports concurrent execution of multiple
- guest operating systems. Using Xen, an administrator can
- set up many virtual machines running on a single physical
- computer. Any single virtual machine, while executing,
- performs nearly as well as the physical system without Xen.
- Xen may be used for testing software, providing large-scale
- web hosting on limited hardware, any many other
- applications.
-
-
+ Xen
+
+
+ Xen is an open source virtual machine monitor for Intel x86
+ machines which supports concurrent execution of multiple
+ guest operating systems. Using Xen, an administrator can set
+ up many virtual machines running on a single physical
+ computer. Any single virtual machine, while executing,
+ performs nearly as well as the physical system without Xen.
+ Xen may be used for testing software, providing large-scale
+ web hosting on limited hardware, any many other
+ applications.
+
+ yum
- The Yellow Dog Updater, or yum, is a
- complete software management utility for RPM-based systems
- such as &FED;. It automatically determines software
+ The Yellow Dog Updater, or
+ yum
+ , is a complete software management utility for RPM-based
+ systems such as &FED;. It automatically determines software
requirements, or dependencies, and
- uses this data to install, update, or remove packages.
- Refer to for more
- information about yum.
+ uses this data to install, update, or remove packages. Refer
+ to
+
+ for more information about yum.
From fedora-docs-commits at redhat.com Wed Mar 15 06:21:05 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 15 Mar 2006 01:21:05 -0500
Subject: press-release Makefile,1.4,1.5 fdp-pr.xsl,1.5,1.6
Message-ID: <200603150621.k2F6L5CF002622@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2602
Modified Files:
Makefile fdp-pr.xsl
Log Message:
Make PDF output look reasonable using the default xmlto RPM.
Text output is still mangled because it's getting rendered into HTML first;
don't ask me why.
Index: Makefile
===================================================================
RCS file: /cvs/docs/press-release/Makefile,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Makefile 14 Mar 2006 23:04:52 -0000 1.4
+++ Makefile 15 Mar 2006 06:20:58 -0000 1.5
@@ -43,7 +43,7 @@
# forms
define OUTPUT_template
-${DOC_BASE}-$(1).pdf:: ${DOC_BASE}-$(1).xml params.xsl.in
+${DOC_BASE}-$(1).pdf:: ${DOC_BASE}-$(1).xml params.xsl.in ${XSL}
LC_ALL=${1}.UTF-8 ${SED} -e "s|DATE|$$(date +'%x %X')|" \
params.xsl.in >params.xsl
LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} pdf \
@@ -53,11 +53,13 @@
distclean::
${RM} ${DOC_BASE}-${1}.pdf
-${DOC_BASE}-$(1).txt:: ${DOC_BASE}-$(1).xml params.xsl.in
+XMLPOSTFLAGS=-p '-cols 72'
+
+${DOC_BASE}-$(1).txt:: ${DOC_BASE}-$(1).xml params.xsl.in ${XSL}
LC_ALL=${1}.UTF-8 ${SED} -e "s|DATE|$$(date +'%x %X')|" \
params.xsl.in >params.xsl
- LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} txt \
- ${DOC_BASE}-$(1).xml
+ LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} $${XMLPOSTFLAGS} \
+ txt ${DOC_BASE}-$(1).xml
${RM} params.xsl
distclean::
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.xsl,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fdp-pr.xsl 11 Mar 2006 17:22:43 -0000 1.5
+++ fdp-pr.xsl 15 Mar 2006 06:20:58 -0000 1.6
@@ -42,7 +42,7 @@
-
+
@@ -74,7 +74,7 @@
-
+
@@ -82,12 +82,12 @@
-
+
-
+
@@ -118,9 +118,9 @@
-
+
-
+
From fedora-docs-commits at redhat.com Wed Mar 15 06:59:02 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 15 Mar 2006 01:59:02 -0500
Subject: press-release Makefile, 1.5, 1.6 fdp-pr.xsl, 1.6, 1.7 params.xsl.in,
1.2, 1.3
Message-ID: <200603150659.k2F6x2R8002777@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2753
Modified Files:
Makefile fdp-pr.xsl params.xsl.in
Log Message:
Try to get the automatic date generation a little more localized.
Index: Makefile
===================================================================
RCS file: /cvs/docs/press-release/Makefile,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Makefile 15 Mar 2006 06:20:58 -0000 1.5
+++ Makefile 15 Mar 2006 06:58:54 -0000 1.6
@@ -42,9 +42,14 @@
# Compute the rules to transform our XML documents into both PDF and TXT
# forms
define OUTPUT_template
+.PHONY: pdf-${1}
+
+pdf-${1}:: ${DOC_BASE}-${1}.pdf
${DOC_BASE}-$(1).pdf:: ${DOC_BASE}-$(1).xml params.xsl.in ${XSL}
- LC_ALL=${1}.UTF-8 ${SED} -e "s|DATE|$$(date +'%x %X')|" \
+ LC_ALL=${1}.UTF-8 ${SED} \
+ -e "s|DATE|$$(shell LC_ALL=${1} date +'%x %X')|" \
+ -e "s|LANG|${1}|" \
params.xsl.in >params.xsl
LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} pdf \
${DOC_BASE}-$(1).xml
@@ -53,10 +58,16 @@
distclean::
${RM} ${DOC_BASE}-${1}.pdf
+# This assumes w3m(1) is installed.
XMLPOSTFLAGS=-p '-cols 72'
+.PHONY: txt-${1}
+
+txt-${1}:: ${DOC_BASE}-${1}.txt
+
${DOC_BASE}-$(1).txt:: ${DOC_BASE}-$(1).xml params.xsl.in ${XSL}
- LC_ALL=${1}.UTF-8 ${SED} -e "s|DATE|$$(date +'%x %X')|" \
+ LC_ALL=${1}.UTF-8 ${SED} \
+ -e "s|DATE|$$(shell LC_ALL=${1} date +'%x %X')|" \
params.xsl.in >params.xsl
LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} $${XMLPOSTFLAGS} \
txt ${DOC_BASE}-$(1).xml
@@ -69,8 +80,10 @@
$(foreach LOCALE,${LANGUAGES},$(eval $(call OUTPUT_template,${LOCALE})))
########################################################################
# Always generate the current date.
-params.xsl: params.xsl.in
- ${SED} -e "s|DATE|$$(date +'%x %X')|" $< >$@.tmp && move-if-change $@.tmp $@
+params.xsl: params.xsl.in Makefile
+ ${SED} -e "s|DATE|$$(date +'%x %X')|" \
+ -e "s|LANG|${PRI_LANG}|" \
+ $< >$@.tmp && move-if-change $@.tmp $@
########################################################################
# The ${DOC_BASE}.pot target produces a new .POT file everytime the
# original XML file is updated.
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.xsl,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- fdp-pr.xsl 15 Mar 2006 06:20:58 -0000 1.6
+++ fdp-pr.xsl 15 Mar 2006 06:58:54 -0000 1.7
@@ -8,6 +8,7 @@
>
+ en_US2006-02-06Verdana12pt
@@ -15,7 +16,7 @@
12pt
-
+
@@ -42,7 +43,7 @@
-
+
@@ -58,8 +59,9 @@
+ Page
- /
+ of
Index: params.xsl.in
===================================================================
RCS file: /cvs/docs/press-release/params.xsl.in,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- params.xsl.in 7 Feb 2006 17:30:59 -0000 1.2
+++ params.xsl.in 15 Mar 2006 06:58:54 -0000 1.3
@@ -5,6 +5,7 @@
The 'today' value is provided by the Makefile, so please do not edit this definition yourself!
-->
DATE
+ LANG
From fedora-docs-commits at redhat.com Wed Mar 15 12:46:57 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Wed, 15 Mar 2006 07:46:57 -0500
Subject: jargon-buster Makefile,1.6,1.7 rpm-info.xml,1.4,1.5
Message-ID: <200603151247.k2FClRGR017774@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/jargon-buster
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17708
Modified Files:
Makefile rpm-info.xml
Log Message:
Update to proper locale and adjust supporting rpm-info and Makefile accordingly
Index: Makefile
===================================================================
RCS file: /cvs/docs/jargon-buster/Makefile,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- Makefile 17 Feb 2006 23:35:36 -0000 1.6
+++ Makefile 15 Mar 2006 12:46:50 -0000 1.7
@@ -7,7 +7,7 @@
# Document-specific definitions.
#
DOCBASE = jargon-buster
-PRI_LANG = en
+PRI_LANG = en_US
OTHERS =
########################################################################
# List each XML file of your document in the template below. Append the
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/jargon-buster/rpm-info.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-info.xml 15 Mar 2006 04:09:37 -0000 1.4
+++ rpm-info.xml 15 Mar 2006 12:46:50 -0000 1.5
@@ -29,7 +29,7 @@
Paul W. Frields
-
+ Fedora Jargon BusterA glossary that demystifies some of the terms used in Fedora and Linux
@@ -48,102 +48,102 @@
- Convert to DocBook XML V4.4 and use XInclude
+ Convert to DocBook XML V4.4 and use XInclude
- Initial RPM package
+ Initial RPM package
- Add title to glossary to ensure readability in yelp. Apparently every
+ Add title to glossary to ensure readability in yelp. Apparently every
major section needs to have a title for this reason.
- Version 1.9.5.1
+ Version 1.9.5.1
- Fix labels to uniformity.
+ Fix labels to uniformity.
- Add additional entries for input methods, programming features, and Xen
+ Add additional entries for input methods, programming features, and Xen
(#177103).
- Additional cross referencing.
- Delineate copyright information, partly for clarity and partly for
+ Additional cross referencing.
+ Delineate copyright information, partly for clarity and partly for
properly exercising build tools.
- Spelling correction (#171596).
+ Spelling correction (#171596).
- Some term fixes (#160265).
+ Some term fixes (#160265).
- Style editing.
+ Style editing.
- Additional term editing.
+ Additional term editing.
- Began new round of editing.
+ Began new round of editing.
- Added Tettnang.
+ Added Tettnang.
- Added request for input statement, added KDE and VMware terms (DaveP);
+ Added request for input statement, added KDE and VMware terms (DaveP);
added trademark tags around relevant words in new entries and
modified para on contributing (TammyFox)
- Modified to build in fedora-docs module, Red Hat is 2 words, other edits
+ Modified to build in fedora-docs module, Red Hat is 2 words, other edits
and corrections
- Update
+ Update
- More additions from list and A-Z toc. Needs art.xsl
+ More additions from list and A-Z toc. Needs art.xsl
- More additions from list.
+ More additions from list.
- Added LegalNotice and std ents.
+ Added LegalNotice and std ents.
- More added from various places (e.g. DV).
+ More added from various places (e.g. DV).
- More added from Fedora list.
+ More added from Fedora list.
- More added from Fedora list.
+ More added from Fedora list.
- Initial Release
+ Initial Release
From fedora-docs-commits at redhat.com Wed Mar 15 15:12:14 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 15 Mar 2006 10:12:14 -0500
Subject: press-release Makefile,1.6,1.7
Message-ID: <200603151512.k2FFCELd024472@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24450
Modified Files:
Makefile
Log Message:
DROPPED support for text output, for now we only support PDF output.
Added copious "make help" documentation.
Index: Makefile
===================================================================
RCS file: /cvs/docs/press-release/Makefile,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- Makefile 15 Mar 2006 06:58:54 -0000 1.6
+++ Makefile 15 Mar 2006 15:11:49 -0000 1.7
@@ -18,9 +18,7 @@
XMLTOFLAGS=-m params.xsl
XSL =fdp-pr.xsl
SED =/bin/sed
-XML2POT =xml2pot
XML2PO =xml2po
-PO2XML =po2xml
MSGMERGE=msgmerge
MSGMERGEFLAGS=
########################################################################
@@ -32,20 +30,31 @@
########################################################################
# Mark the proper virtual targets so that a "make -t all" does not create
# an empty file called "all".
-.PHONY: all clean distclean clobber pot
+.PHONY: all clean distclean clobber pot help
########################################################################
# The default target "all"
all:: ${DOC_BASE}.pot
all:: $(foreach LOCALE,${LANGUAGES},${DOC_BASE}-${LOCALE}.pdf)
-all:: $(foreach LOCALE,${LANGUAGES},${DOC_BASE}-${LOCALE}.txt)
+# FIXME all:: $(foreach LOCALE,${LANGUAGES},${DOC_BASE}-${LOCALE}.txt)
+########################################################################
+HFMT =%-31s\t%s\n
+help::
+ @printf "${HFMT}" "all" "Default target; generate PDF's"
+ @printf "${HFMT}" "clean" "Delete temporary files"
+ @printf "${HFMT}" "distclean" "Delete output and temporary files"
+ @printf "${HFMT}" "clobber" "Delete output and temporary files"
+ @printf "${HFMT}" "help" "This message; use 'make help|sort'"
########################################################################
# Compute the rules to transform our XML documents into both PDF and TXT
# forms
-define OUTPUT_template
+define PDF_template
.PHONY: pdf-${1}
pdf-${1}:: ${DOC_BASE}-${1}.pdf
+help::
+ @printf "${HFMT}" "pdf-${1}" "Generate PDF for locale '${1}'"
+
${DOC_BASE}-$(1).pdf:: ${DOC_BASE}-$(1).xml params.xsl.in ${XSL}
LC_ALL=${1}.UTF-8 ${SED} \
-e "s|DATE|$$(shell LC_ALL=${1} date +'%x %X')|" \
@@ -53,42 +62,67 @@
params.xsl.in >params.xsl
LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} pdf \
${DOC_BASE}-$(1).xml
- ${RM} params.xsl
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}-${1}.pdf" "Render PDF for locale '${1}'"
distclean::
${RM} ${DOC_BASE}-${1}.pdf
+endef
+
+$(foreach LOCALE,${LANGUAGES},$(eval $(call PDF_template,${LOCALE})))
+########################################################################
-# This assumes w3m(1) is installed.
+########################################################################
+define TXT_template
+# This assumes w3m(1) is installed. The stock xmlto RPM uses it.
XMLPOSTFLAGS=-p '-cols 72'
.PHONY: txt-${1}
txt-${1}:: ${DOC_BASE}-${1}.txt
+help::
+ @printf "${HFMT}" "txt-${1}" "Generate text version for locale '${1}'"
+
${DOC_BASE}-$(1).txt:: ${DOC_BASE}-$(1).xml params.xsl.in ${XSL}
LC_ALL=${1}.UTF-8 ${SED} \
-e "s|DATE|$$(shell LC_ALL=${1} date +'%x %X')|" \
params.xsl.in >params.xsl
LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} $${XMLPOSTFLAGS} \
txt ${DOC_BASE}-$(1).xml
- ${RM} params.xsl
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}-${1}.txt" "Render locale '${1}' text"
distclean::
${RM} ${DOC_BASE}-${1}.txt
endef
-
-$(foreach LOCALE,${LANGUAGES},$(eval $(call OUTPUT_template,${LOCALE})))
+# FIXME $(foreach LOCALE,${LANGUAGES},$(eval $(call TXT_template,${LOCALE})))
########################################################################
# Always generate the current date.
params.xsl: params.xsl.in Makefile
- ${SED} -e "s|DATE|$$(date +'%x %X')|" \
+ ${SED} -e "s|DATE|$$(LC_ALL=${PRI_LANG} date +'%x %X')|" \
-e "s|LANG|${PRI_LANG}|" \
$< >$@.tmp && move-if-change $@.tmp $@
+
+help::
+ @printf "${HFMT}" "params.xsl" "Generate dynamic parameters"
########################################################################
# The ${DOC_BASE}.pot target produces a new .POT file everytime the
# original XML file is updated.
-${DOC_BASE}.pot: ${DOC_BASE}-${PRI_LANG}.xml
+.PHONY: pot
+
+pot:: ${DOC_BASE}.pot
+
+help::
+ @printf "${HFMT}" "pot" "Generate .POT file for translation"
+
+${DOC_BASE}.pot:: ${DOC_BASE}-${PRI_LANG}.xml
xml2po -o $@ $<
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}.pot" "Generate .POT file for translation"
########################################################################
# Compute the rules to create or update a language-specific .po file
# any time the ${DOC_BASE}.pot file is updated. We try to avoid losing
@@ -98,6 +132,9 @@
.PHONY: po-${1}
po-${1}:: ${1}.po
+help::
+ @printf "${HFMT}" "po-${1}" "Update translations for locale '${1}'"
+
.PRECIOUS: ${1}.po
${1}.po:: ${DOC_BASE}.pot
@if [ ! -f ${1}.po ]; then \
@@ -108,6 +145,9 @@
${MSGMERGE} ${MSGMERGEFLAGS} \
${1}.po $${DOC_BASE}.pot >${1}.po; \
fi
+
+help::
+ @printf "${HFMT}" "${1}.po" "Update translations for locale '${1}'"
endef
$(foreach LOCALE,${OTHERS},$(eval $(call PO_template,${LOCALE})))
@@ -118,14 +158,27 @@
.PHONY: xml-${1}
xml-${1}:: ${DOC_BASE}-${1}.xml
+help::
+ @printf "${HFMT}" "xml-${1}" "Translate XML for locale '${1}'"
+
${DOC_BASE}-${1}.xml:: ${DOC_BASE}-${PRI_LANG}.xml ${1}.po
- ${PO2XML} ${DOC_BASE}-${PRI_LANG}.xml ${1}.po >${DOC_BASE}-${1}.xml
+ ${XML2PO} -p ${1}.po ${DOC_BASE}-${PRI_LANG}.xml >${DOC_BASE}-${1}.xml
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}-${1}.xml" "Create XML for locale '${1}'"
clean::
${RM} ${DOC_BASE}-${1}.xml
endef
$(foreach LOCALE,${OTHERS},$(eval $(call NEWLANG_template,${LOCALE})))
+
+.PHONY: xml-${PRI_LANG}
+
+xml-${PRI_LANG}:: ${DOC_BASE}-${PRI_LANG}.xml
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}-${PRI_LANG}.xml" "Primary XML"
########################################################################
clean::
${RM} params.xml
@@ -134,6 +187,8 @@
.PHONY: mrproper
mrproper:: distclean
${RM} *.po
+ ${RM} *.pdf
+ ${RM} *.txt
########################################################################
# End of Makefile
########################################################################
From fedora-docs-commits at redhat.com Wed Mar 15 15:17:40 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 15 Mar 2006 10:17:40 -0500
Subject: press-release fdp-pr.xsl,1.8,1.9
Message-ID: <200603151517.k2FFHeH8024635@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24524
Modified Files:
fdp-pr.xsl
Log Message:
Use "font-family" instead of "font" attributes to allow recovery if
the rendering machine doesn't have some fonts we'd expect. Hmmm,
I'll need to think about font selection more for non-Romance
languages.
Removed all non-translatable English text from the .XSL template.
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.xsl,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- fdp-pr.xsl 15 Mar 2006 07:09:43 -0000 1.8
+++ fdp-pr.xsl 15 Mar 2006 15:17:17 -0000 1.9
@@ -10,7 +10,7 @@
en_US2006-02-06
- Verdana
+ Verdana, Courier, Helvetica, Sans, Serif12pt12pt12pt
@@ -34,10 +34,10 @@
-
+
-
-
+
+
@@ -45,11 +45,10 @@
-
+
-
-
+
@@ -57,21 +56,20 @@
-
+
-
-
+
+
- Page
- of
+ /
-
+
@@ -80,7 +78,7 @@
-
+
@@ -89,6 +87,9 @@
+
+
+
From fedora-docs-commits at redhat.com Wed Mar 15 18:11:51 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Wed, 15 Mar 2006 13:11:51 -0500
Subject: press-release Makefile,1.7,1.8
Message-ID: <200603151811.k2FIBpqs031906@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31888
Modified Files:
Makefile
Log Message:
Oops, cleaned a file that was never generated!
Index: Makefile
===================================================================
RCS file: /cvs/docs/press-release/Makefile,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- Makefile 15 Mar 2006 15:11:49 -0000 1.7
+++ Makefile 15 Mar 2006 18:11:40 -0000 1.8
@@ -181,7 +181,7 @@
@printf "${HFMT}" "${DOC_BASE}-${PRI_LANG}.xml" "Primary XML"
########################################################################
clean::
- ${RM} params.xml
+ ${RM} params.xsl
distclean clobber:: clean
########################################################################
.PHONY: mrproper
From fedora-docs-commits at redhat.com Thu Mar 16 00:08:19 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 15 Mar 2006 19:08:19 -0500
Subject: marketing-content/FC-5-press-release fc5-press-release-en_US.xml,
1.1.1.1, 1.2
Message-ID: <200603160008.k2G08JEk015136@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15118
Modified Files:
fc5-press-release-en_US.xml
Log Message:
Converted from Wiki, no changes made yet to actual content.
Index: fc5-press-release-en_US.xml
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/fc5-press-release-en_US.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- fc5-press-release-en_US.xml 14 Mar 2006 20:46:34 -0000 1.1.1.1
+++ fc5-press-release-en_US.xml 16 Mar 2006 00:07:47 -0000 1.2
@@ -2,123 +2,400 @@
- Red Hat, Inc.
+ Fedora Project
- A Section
+ Presenting Fedora Core 5
- Veniam ut wisi tation et delenit
- .
+ The Fedora Project is pleased to announce the release of Fedora Core 5. New
+ desktop applications, advances in security, better localization tools,
+ improved software installation and management facilities and strong Java
+ integration help to make Fedora Core 5 the most innovative Linux
+ distribution ever.
-
-
- Lorem ipsum sit ut et, odio.
-
-
- Suscipit laoreet dolore consequat autem ad.
-
-
- Tation praesent autem aliquip consectetuer illum hendrerit vero vulputate.
-
-
- Iriure delenit sit vulputate suscipit, dolore veniam eros adipiscing.
-
-
- Sed in blandit, et ullamcorper consequat nonummy, amet eros veniam.
-
-
- Odio aliquip dolore tincidunt aliquip.
-
-
-
- Red Hat (NASDAQ: RHAT - News),
- Lorem ipsum suscipit ut et, molestie.
- Lobortis, duis zzril dolore nisl ad.
- Dignissim dolore consequat, minim facilisis commodo enim nostrud at vel.
- Ut delenit, autem vero et sed Ut esse.
- Nonummy magna dolor blandit, facilisi dignissim commodo consequat et et.
-
-
- Lorem ipsum, facilisi ad dignissim nisl luptatum nulla dolore commodo.
- Te consequat eu et blandit hendrerit hendrerit.
-
-
- Lorem ipsum praesent diam duis facilisi.
- Autem vulputate ullamcorper molestie ex commodo at.
- Euismod vel ex nisl hendrerit et tincidunt.
- Vulputate in at praesent nonummy vel.
- Adipiscing amet duis dolore velit.
- Lobortis facilisis nulla, commodo commodo hendrerit duis illum ut sit.
- Ut illum nulla aliquip eros nulla, iusto.
-
-
- Lorem ipsum vel velit quis.
- Eum delenit enim, aliquip vulputate ad et commodo.
- Iriure illum blandit vel nibh nisl.
- Exerci hendrerit in delenit dolore ut in.
-
-
- Lorem ipsum commodo augue commodo.
- Quis duis zzril vel consequat et lobortis ad lobortis.
- Nulla vulputate, tation esse minim in wisi dolore, aliquip.
- Volutpat dolore, dolore sit velit.
- Illum eum vel hendrerit commodo aliquam, nisl velit praesent, duis.
- Lobortis praesent et lobortis in.
-
-
- Lorem ipsum, aliquip, accumsan wisi commodo.
- Praesent eum feugait feugiat adipiscing, nonummy praesent erat zzril facilisis.
- Suscipit facilisis duis veniam veniam iusto, sit.
- Volutpat tation ex eros minim ad eum amet blandit esse.
- Enim ex duis aliquip molestie.
- Consequat feugiat ullamcorper in eu velit dolore tincidunt.
- Minim, nonummy vel in esse aliquam ad, luptatum in.
- Et euismod dolore praesent ea consequat.
-
-
- Lorem ipsum nulla enim in, eros, ullamcorper iriure et.
- Veniam ut wisi tation et delenit
- .
-
-
- Lorem ipsum facilisis, lorem dolore enim iusto luptatum in duis.
- Duis in, odio minim augue, dolore dignissim commodo ut vulputate.
- Ea luptatum nulla aliquip dignissim dolor duis consequat, Ut.
- Minim magna duis dolor ut.
- Tincidunt iriure tation consequat augue odio magna tincidunt.
- Vulputate lobortis praesent molestie nisl iusto, wisi.
-
-
- Lorem ipsum, elit feugiat eros in delenit wisi.
- Nostrud iusto nonummy eu veniam augue nonummy in.
- Ullamcorper, augue elit elit ullamcorper minim augue luptatum.
- Ut molestie, minim qui vel blandit.
- Eros, ut delenit luptatum vel dignissim.
- Tation feugait exerci aliquam nibh sit blandit ipsum.
- Et vulputate nonummy sit ut.
- Sed zzril dolore, ex vero feugait volutpat at, tation.
- Learn more:
-
-
- Lorem ipsum luptatum feugiat ea magna vulputate accumsan euismod.
- Facilisis vel nostrud tation qui ut.
- Qui suscipit delenit qui odio te.
- Hendrerit illum euismod veniam et feugait feugiat.
- Vero molestie duis velit diam, delenit praesent.
- Iriure molestie aliquip dolor at.
- Commodo et ut erat feugiat molestie vulputate in esse.
-
-
- Lorem ipsum wisi vero nulla suscipit ea dolor nisl.
- Zzril, lorem, ullamcorper amet, eu nulla eum iusto zzril.
- Vero molestie consequat, facilisi, enim praesent tincidunt et dignissim zzril.
- At feugait nostrud accumsan suscipit.
- Diam molestie zzril wisi veniam.
- Nisl nibh in praesent velit at hendrerit dignissim autem.
- Lobortis, vel feugait feugait aliquip.
- Vulputate consectetuer, minim duis hendrerit wisi consectetuer nostrud.
- Ut illum sed et nulla, velit zzril ad veniam.
- Duis minim commodo vel vulputate ullamcorper esse dolore.
- Nulla dolor at hendrerit feugait.
- Dignissim qui esse dolore ut.
+ Getting Fedora Core 5
+ Download ISO Images
+
+ Users can download the ISO images of the installation DVD or CD-ROMs now
+ from the Fedora web site.
+
+
+ http://fedoraproject.org/wiki/Distribution/Download
+
+ Online Vendors
+
+ We recognize that many people do not have sufficient bandwidth to download
+ an entire operating system. This is one of the reasons that the Trademark
+ Guidelines are written to allow third parties to sell physical media
+ containing Fedora Core, as long as they comply with the guidelines.
+
+
+ http://fedoraproject.org/wiki/Distribution/OnlineVendors
+
+
+ http://fedoraproject.org/wiki/Legal/TrademarkGuidelines
+
+ Fedora Community Free Media
+
+ Fedora Community Free Media, a volunteer initiative under the Fedora
+ Ambassadors Program, aims to distribute Fedora Core media (DVDs) for free to
+ individuals. Local Fedora Ambassadors or Contributors are invited to
+ participate.
+
+
+ http://fedoraproject.org/wiki/FreeMedia
+
+
+ http://fedoraproject.org/wiki/Ambassadors
+
+ What's New In Fedora Core 5
+
+ See Fedora Core 5 Now
+
+ Fedora Core 5 has an exciting new look and feel. The menus and user
+ interface have been carefully crafted by the interaction designers and
+ desktop team. Take a tour at:
+
+
+ http://fedoraproject.org/wiki/Tours/FedoraCore5
+
+
+ Desktop
+
+ Fedora Core 5 features some great new desktop applications powered by Mono.
+
+
+ Tomboy is a note-taking tool; simple and handy, it has already changed the
+ way that some Fedora users and developers work.
+
+
+ http://www.beatniksoftware.com/tomboy/
+
+
+ Thanks to F-Spot, managing digital photographs is easier than ever.
+
+
+ http://f-spot.org/Main_Page
+
+
+ If you are looking for something in a chat log, an email, or a web page you
+ visited days ago, Beagle helps you find it.
+
+
+ http://beaglewiki.org/Main_Page
+
+
+ We are also pleased to introduce Accelerated Indirect GLX (AIGLX) support in
+ Fedora Core 5. Developed in partnership with the upstream Xorg community,
+ AIGLX provides the foundation for GLX-accelerated effects on a standard
+ desktop. While this can mean eye-catching effects, it also provides a
+ platform for creating a high-performance, efficient, and elegant desktop.
+
+
+ http://fedoraproject.org/wiki/RenderingProject
+
+
+ Power management has been improved thanks to GNOME Power Manager, included
+ in this release. The GNOME screensaver package is included, with a new
+ Fedora screensaver to accompany it.
+
+
+ http://www.gnome.org/projects/gnome-power-manager/
+
+
+ http://live.gnome.org/GnomeScreensaver/
+
+
+ Integration, testing, and development was done to verify that suspend and
+ hibernation features work with the largest number of hardware combinations
+ that the Fedora community could get its hands on.
+
+
+ We didn't forget our Apple hardware users and included support for the
+ widely-used Broadcom 43xx wireless chipsets in the Fedora Core 5 kernel,
+ which is based on the 2.6.16 kernel release.
+
+
+ http://bcm43xx.berlios.de/
+
+
+ http://wiki.kernelnewbies.org/LinuxChanges
+
+
+ Fedora Core 5 also features updated versions of old favorites. The latest
+ in the Firefox 1.5 series offers improvements in speed, stability, security,
+ and accessibility. The latest OpenOffice.org 2.0.2 introduces OpenDocument
+ support, a new enhanced database frontend, a mail merge wizard, and better
+ PDF export capability. The latest versions of both GNOME 2.14 and KDE 3.5
+ bring a many new features and improvements to the Fedora desktop.
+
+
+ http://www.mozilla.com/firefox/releases/1.5.html
+
+
+ http://www.openoffice.org/product/index.html
+
+
+ http://www.gnome.org/start/2.14/notes/C/
+
+
+ http://kde.org/announcements/announce-3.5.php
+
+
+ Finally, the Fedora Core 5 desktop features new advances in multimedia
+ applications built around the free Xiph.org codecs. Fedora is proud to say
+ that Chris Montgomery, the founder of Xiph.org and the genius behind the Ogg
+ family of codecs, is now a member of the Fedora Core team. We hope that
+ Fedora and Xiph.org form a strong and lasting partnership to further the
+ development of free media formats.
+
+
+ http://www.xiph.org
+
+
+ Software Installation and Management
+
+ Anaconda, the Fedora Core installer, has been completely rewritten to
+ present a more streamlined interface that matches the new look and feel of
+ Fedora Core 5.
+
+
+ Fedora Core 5 also brings major advancements in software management with the
+ introduction of Pirut, a graphical interface to replace
+ system-config-packages. Pirut helps manage the large number of software
+ packages available in Fedora Core and Extras repositories. The software
+ package updater, Pup, helps users keep pace with Fedora's rapid
+ improvements.
+
+
+ For the first time, all of Fedora Core's tools for software installation and
+ management share the same strong foundation: the package management utility
+ Yum. This tight integration will lead to dramatic improvements in software
+ management in future Fedora releases.
+
+
+ Xen Virtualization
+
+ Xen, the leading open source virtualization project, is included in Fedora
+ Core 5. Our version of Xen is based on the latest Xen 3.0 development
+ branch, with support for both 32-bit and 64-bit x86 hardware. Also included
+ is the Xen guest install script from Fedora developers, which allows users
+ to set up virtual machines.
+
+
+ Xen's advances in Fedora Core 5 represent a critical next step in the future
+ of virtualization on Linux. Fedora has expanded our virtualization team
+ with Chris Wright, one of the maintainers of the stable branch of 2.6 kernel
+ releases, and Juan Quintela, as virtualization wizards. They are part of a
+ large Red Hat team, headed by Brian Stein, responsible for making
+ virtualization ubiquitous and seamless in Fedora.
+
+
+ http://fedoraproject.org/wiki/Tools/Xen
+
+
+ Security
+
+ You can always expect interesting and exciting advancements in security from
+ Fedora Core, and this release does not disappoint. Security Enhanced Linux
+ (SELinux) is now using the reference policy, which makes it easier to create
+ and maintain modular security policies. The introduction of a stack
+ protector to GCC 4.1 makes it harder than ever for hackers to exploit buffer
+ overflows, one of the most common security vulnerabilities.
+
+
+ http://fedoraproject.org/wiki/Security/Features?highlight=%28fstack%29
+
+
+ Fedora has switched to using the reference policy for the SELinux security
+ framework. This supports binary modules, allowing SELinux policies to move
+ into individual packages. Developers can use this to ship site-specific
+ policy customizations. Fedora Core also supports the Multi Category
+ Security (MCS) SELinux policy by default, in addition to Type Enforcement
+ (TE), Muti Level Security (MLS), and Role Base Access Control (RBAC)
+ security policies. These gains in security continue to make Fedora Core one
+ of the most secure general-use operating systems in the world. Find more
+ facts at:
+
+
+ http://fedoraproject.org/wiki/Security
+
+
+ http://serefpolicy.sourceforge.net/
+
+
+ Linux Unified Key Support (LUKS) provides hard disk encryption support in
+ Fedora Core 5; David Zeuthen of Red Hat, the HAL developer and maintainer,
+ worked on the LUKS integration with HAL and GNOME, finishing just in time
+ for the new Fedora Core release. Hard disk encryption provides one of the
+ best physical security solutions -- protection of your data if your hard
+ disk falls into the wrong hands.
+
+
+ http://fedoraproject.org/wiki/Software/LUKS
+
+
+ Internationalization and Localization
+
+ Fedora contributors speak many different languages besides C, C++, Python,
+ Java, and so on. We are also humans who speak the world's many different
+ languages, and we all want Fedora to support as many as possible.
+
+
+ In Fedora Core 5, we have come closer to that goal by adopting SCIM, in
+ place of IIIMF, as the input method of choice for internationalization. This
+ and other advances allow Fedora to communicate with its many users better
+ than ever before.
+
+
+ http://www.scim-im.org/
+
+
+ Java
+
+ This release of Fedora Core represents another big step down the free Java
+ path.
+
+
+ Through the introduction of the completely free software stack
+ java-gcj-compat that runs native and bytecode Java, Fedora can now compile
+ and run software written in Java without relying upon proprietary and closed
+ Java machine implementations.
+
+
+ The excellent Fedora Java development team of Red Hat and community hackers
+ have built many popular Java-based or Java-using packages utilizing
+ java-gcj-compat for this release. These packages, which include
+ OpenOffice.org, Eclipse, Apache Tomcat, and Jakarta, are now compiled and
+ run on a 100% free and open software stack.
+
+
+ We included a complete set of packages and development goodies in Fedora
+ Core 5 for Java technologies. Fedora Extras also has many Java
+ applications: the popular BitTorrent utility Azureus, RSSowl, and others,
+ all powered by gcj-java-compat.
+
+
+ http://fedoraproject.org/wiki/Java
+
+
+ http://www.gnu.org/philosophy/java-trap.html
+
+
+ Under the Hood
+
+ The software repositories for the Fedora Legacy community maintenance
+ project are available in this release. Disabled by default, these
+ repositories can easily be re-enabled so that users can keep up with
+ community patches after Fedora Core 5 leaves its official maintenance
+ window.
+
+
+ Fedora Core 5 includes the latest releases of Apache HTTP Web Server 2.2,
+ MySQL 5.0, and PostgreSQL 8.1 with various enhancements.
+
+
+ http://httpd.apache.org/docs/2.2/new_features_2_2.html
+
+
+ http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html
+
+
+ http://www.postgresql.org/docs/whatsnew
+
+
+ X.Org has been completely modularized and Fedora Core includes the latest
+ X.Org X11R7.0 in this release. The new modular architecture of R7.0 enables
+ easier driver upgrades and simplifies development, opening the way for rapid
+ improvement in Linux graphics.
+
+
+ Gstreamer, the free desktop multimedia framework, has seen major
+ improvements with the 0.10 release, and we made sure that applications such
+ as Totem take full advantage of it.
+
+
+ http://gstreamer.freedesktop.org/
+
+
+ We have the latest version of the GNU Compiler Collection, GCC 4.1, which
+ provides security and performance improvements. We used GCC 4.1 to compile
+ over 6,000 packages in the Fedora Core and Fedora Extras software
+ repositories. GCJ, a critical part of our free Java environment, is
+ included. There is also an implementation of the OpenMP parallel
+ programming standard (http://www.openmp.org/) for C, C++
+ and Fortran. Use the compiler switch -fopenmp to enable it.
+
+
+ Other improvements are listed at:
+
+
+ http://gcc.gnu.org/gcc-4.1/changes.html.
+
+
+ Fedora Core 5 also offers technology previews for SystemTap and Frysk,
+ cutting edge execution analysis tools that will allow developers to
+ troubleshoot performance issues to a degree never before possible.
+
+
+ http://fedoraproject.org/wiki/SystemTap
+
+
+ http://fedoraproject.org/wiki/Frysk
+
+
+ The Future of Fedora
+
+ Fedora contributors are already working toward the next release of Fedora
+ Core, which will feature advancements in Xen, and new integration work from
+ the Fedora Rendering and One Laptop Per Child (a.k.a. $100 laptop) projects.
+ Stateless Linux work is also progressing steadily. We are working on the
+ ability to support Fedora Extras and other custom software repositories
+ during installation. As usual, work continues on new releases of the best
+ and most robust free and open source software. See our roadmap at:
+
+
+ http://fedoraproject.org/wiki/RoadMap
+
+
+ http://fedoraproject.org/wiki/OLPC
+
+
+ http://fedoraproject.org/wiki/StatelessLinux
From fedora-docs-commits at redhat.com Thu Mar 16 00:11:57 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 15 Mar 2006 19:11:57 -0500
Subject: marketing-content/FC-5-press-release Makefile,1.1.1.1,1.2
Message-ID: <200603160011.k2G0Bvel015186@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15171
Modified Files:
Makefile
Log Message:
Updating Makefile to canonical from press-release module (rev. 1.8).
Index: Makefile
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/Makefile,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- Makefile 14 Mar 2006 20:46:35 -0000 1.1.1.1
+++ Makefile 16 Mar 2006 00:11:38 -0000 1.2
@@ -1,10 +1,10 @@
########################################################################
# The ${DOC_BASE} symbol provides the basic name for this document.
-DOC_BASE=fc5-press-release
+DOC_BASE=fdp-pr
########################################################################
# The ${LANG} symbol gives the locale for the original language for
# the document.
-LANG=en_US
+LANG=en
########################################################################
# The ${OTHERS} symbol is a list of additional locales into which the
# document is to be translated.
From fedora-docs-commits at redhat.com Thu Mar 16 00:14:33 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 15 Mar 2006 19:14:33 -0500
Subject: marketing-content/FC-5-press-release Makefile,1.2,1.3
Message-ID: <200603160014.k2G0EXBO015215@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15200
Modified Files:
Makefile
Log Message:
This is the real Makefile based on the real rev. 1.8.
Index: Makefile
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/Makefile,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Makefile 16 Mar 2006 00:11:38 -0000 1.2
+++ Makefile 16 Mar 2006 00:14:13 -0000 1.3
@@ -1,10 +1,10 @@
########################################################################
# The ${DOC_BASE} symbol provides the basic name for this document.
-DOC_BASE=fdp-pr
+DOC_BASE=fc5-press-release
########################################################################
-# The ${LANG} symbol gives the locale for the original language for
+# The ${PRI_LANG} symbol gives the locale for the original language for
# the document.
-LANG=en
+PRI_LANG=en_US
########################################################################
# The ${OTHERS} symbol is a list of additional locales into which the
# document is to be translated.
@@ -18,60 +18,125 @@
XMLTOFLAGS=-m params.xsl
XSL =fdp-pr.xsl
SED =/bin/sed
-XML2POT =xml2pot
XML2PO =xml2po
-PO2XML =po2xml
MSGMERGE=msgmerge
MSGMERGEFLAGS=
########################################################################
+LANGUAGES=${PRI_LANG} ${OTHERS}
+########################################################################
# Define our own set of suffixes to streamline the process
.SUFFIXES:
.SUFFIXES: .txt .pdf .po .pot .xml .xsl .dtd .in
########################################################################
# Mark the proper virtual targets so that a "make -t all" does not create
# an empty file called "all".
-.PHONY: all clean distclean clobber pot
-.PHONY: $(foreach LOCALE,${OTHERS},xml-${LOCALE})
-.PHONY: $(foreach LOCALE,${OTHERS},po-${LOCALE})
+.PHONY: all clean distclean clobber pot help
########################################################################
# The default target "all"
all:: ${DOC_BASE}.pot
-all:: $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.xml)
-all:: $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.pdf)
-all:: $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.txt)
+all:: $(foreach LOCALE,${LANGUAGES},${DOC_BASE}-${LOCALE}.pdf)
+# FIXME all:: $(foreach LOCALE,${LANGUAGES},${DOC_BASE}-${LOCALE}.txt)
+########################################################################
+HFMT =%-31s\t%s\n
+help::
+ @printf "${HFMT}" "all" "Default target; generate PDF's"
+ @printf "${HFMT}" "clean" "Delete temporary files"
+ @printf "${HFMT}" "distclean" "Delete output and temporary files"
+ @printf "${HFMT}" "clobber" "Delete output and temporary files"
+ @printf "${HFMT}" "help" "This message; use 'make help|sort'"
########################################################################
# Compute the rules to transform our XML documents into both PDF and TXT
# forms
-define OUTPUT_template
-${DOC_BASE}-$(1).pdf:: ${DOC_BASE}-$(1).xml params.xsl.in
- LC_ALL=${1}.UTF-8 ${SED} -e "s|DATE|$$(date +'%x %X')|" \
+define PDF_template
+.PHONY: pdf-${1}
+
+pdf-${1}:: ${DOC_BASE}-${1}.pdf
+
+help::
+ @printf "${HFMT}" "pdf-${1}" "Generate PDF for locale '${1}'"
+
+${DOC_BASE}-$(1).pdf:: ${DOC_BASE}-$(1).xml params.xsl.in ${XSL}
+ LC_ALL=${1}.UTF-8 ${SED} \
+ -e "s|DATE|$$(shell LC_ALL=${1} date +'%x %X')|" \
+ -e "s|LANG|${1}|" \
params.xsl.in >params.xsl
LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} pdf \
${DOC_BASE}-$(1).xml
-${DOC_BASE}-$(1).txt:: ${DOC_BASE}-$(1).xml params.xsl.in
- LC_ALL=${1}.UTF-8 ${SED} -e "s|DATE|$$(date +'%x %X')|" \
- params.xsl.in >params.xsl
- LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} txt \
- ${DOC_BASE}-$(1).xml
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}-${1}.pdf" "Render PDF for locale '${1}'"
+
+distclean::
+ ${RM} ${DOC_BASE}-${1}.pdf
endef
-$(foreach LOCALE,${LANG} ${OTHERS},$(eval $(call OUTPUT_template,${LOCALE})))
+$(foreach LOCALE,${LANGUAGES},$(eval $(call PDF_template,${LOCALE})))
+########################################################################
+
+########################################################################
+define TXT_template
+# This assumes w3m(1) is installed. The stock xmlto RPM uses it.
+XMLPOSTFLAGS=-p '-cols 72'
+
+.PHONY: txt-${1}
+
+txt-${1}:: ${DOC_BASE}-${1}.txt
+
+help::
+ @printf "${HFMT}" "txt-${1}" "Generate text version for locale '${1}'"
+
+${DOC_BASE}-$(1).txt:: ${DOC_BASE}-$(1).xml params.xsl.in ${XSL}
+ LC_ALL=${1}.UTF-8 ${SED} \
+ -e "s|DATE|$$(shell LC_ALL=${1} date +'%x %X')|" \
+ params.xsl.in >params.xsl
+ LC_ALL=${1}.UTF-8 ${XMLTO} -x ${XSL} ${XMLTOFLAGS} $${XMLPOSTFLAGS} \
+ txt ${DOC_BASE}-$(1).xml
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}-${1}.txt" "Render locale '${1}' text"
+
+distclean::
+ ${RM} ${DOC_BASE}-${1}.txt
+endef
+# FIXME $(foreach LOCALE,${LANGUAGES},$(eval $(call TXT_template,${LOCALE})))
########################################################################
# Always generate the current date.
-params.xsl: params.xsl.in
- ${SED} -e "s|DATE|$$(date +'%x %X')|" $< >$@.tmp && move-if-change $@.tmp $@
+params.xsl: params.xsl.in Makefile
+ ${SED} -e "s|DATE|$$(LC_ALL=${PRI_LANG} date +'%x %X')|" \
+ -e "s|LANG|${PRI_LANG}|" \
+ $< >$@.tmp && move-if-change $@.tmp $@
+
+help::
+ @printf "${HFMT}" "params.xsl" "Generate dynamic parameters"
########################################################################
# The ${DOC_BASE}.pot target produces a new .POT file everytime the
# original XML file is updated.
-${DOC_BASE}.pot: ${DOC_BASE}-${LANG}.xml
- xml2pot $< >$@
+.PHONY: pot
+
+pot:: ${DOC_BASE}.pot
+
+help::
+ @printf "${HFMT}" "pot" "Generate .POT file for translation"
+
+${DOC_BASE}.pot:: ${DOC_BASE}-${PRI_LANG}.xml
+ xml2po -o $@ $<
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}.pot" "Generate .POT file for translation"
########################################################################
# Compute the rules to create or update a language-specific .po file
# any time the ${DOC_BASE}.pot file is updated. We try to avoid losing
# current .PO translations by calling msgmerge if a .po file already
# exists.
define PO_template
-po-${1} ${1}.po:: ${DOC_BASE}.pot
+.PHONY: po-${1}
+po-${1}:: ${1}.po
+
+help::
+ @printf "${HFMT}" "po-${1}" "Update translations for locale '${1}'"
+
+.PRECIOUS: ${1}.po
+${1}.po:: ${DOC_BASE}.pot
@if [ ! -f ${1}.po ]; then \
echo Creating pristine ${1}.po; \
cp ${DOC_BASE}.pot ${1}.po; \
@@ -80,6 +145,9 @@
${MSGMERGE} ${MSGMERGEFLAGS} \
${1}.po $${DOC_BASE}.pot >${1}.po; \
fi
+
+help::
+ @printf "${HFMT}" "${1}.po" "Update translations for locale '${1}'"
endef
$(foreach LOCALE,${OTHERS},$(eval $(call PO_template,${LOCALE})))
@@ -87,20 +155,40 @@
# Compute the rules and targets to generate the translated XML files
# given an updated .PO file and the source XML file.
define NEWLANG_template
-xml-${1} ${DOC_BASE}-${1}.xml:: ${DOC_BASE}-${LANG}.xml ${1}.po
- ${PO2XML} ${DOC_BASE}-${LANG}.xml ${1}.po >${DOC_BASE}-${1}.xml
+.PHONY: xml-${1}
+xml-${1}:: ${DOC_BASE}-${1}.xml
+
+help::
+ @printf "${HFMT}" "xml-${1}" "Translate XML for locale '${1}'"
+
+${DOC_BASE}-${1}.xml:: ${DOC_BASE}-${PRI_LANG}.xml ${1}.po
+ ${XML2PO} -p ${1}.po ${DOC_BASE}-${PRI_LANG}.xml >${DOC_BASE}-${1}.xml
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}-${1}.xml" "Create XML for locale '${1}'"
+
+clean::
+ ${RM} ${DOC_BASE}-${1}.xml
endef
$(foreach LOCALE,${OTHERS},$(eval $(call NEWLANG_template,${LOCALE})))
+
+.PHONY: xml-${PRI_LANG}
+
+xml-${PRI_LANG}:: ${DOC_BASE}-${PRI_LANG}.xml
+
+help::
+ @printf "${HFMT}" "${DOC_BASE}-${PRI_LANG}.xml" "Primary XML"
########################################################################
-# Neatness counts
-clean:
- ${RM} $(foreach LOCALE,${OTHERS},${DOC_BASE}-${LOCALE}.xml)
+clean::
${RM} params.xsl
-
-distclean clobber: clean
- ${RM} $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.pdf)
- ${RM} $(foreach LOCALE,${LANG} ${OTHERS},${DOC_BASE}-${LOCALE}.txt)
+distclean clobber:: clean
+########################################################################
+.PHONY: mrproper
+mrproper:: distclean
+ ${RM} *.po
+ ${RM} *.pdf
+ ${RM} *.txt
########################################################################
# End of Makefile
########################################################################
From fedora-docs-commits at redhat.com Thu Mar 16 00:33:55 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 15 Mar 2006 19:33:55 -0500
Subject: marketing-content/FC-5-press-release fdp-pr.dtd,1.1.1.1,1.2
Message-ID: <200603160033.k2G0XtkW015323@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15305
Modified Files:
fdp-pr.dtd
Log Message:
Making the ulink work, this does as expected, spits out the content of the link.
Index: fdp-pr.dtd
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/fdp-pr.dtd,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- fdp-pr.dtd 14 Mar 2006 20:46:34 -0000 1.1.1.1
+++ fdp-pr.dtd 16 Mar 2006 00:33:45 -0000 1.2
@@ -14,5 +14,5 @@
-
+
\ No newline at end of file
From fedora-docs-commits at redhat.com Thu Mar 16 00:47:43 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Wed, 15 Mar 2006 19:47:43 -0500
Subject: marketing-content/FC-5-press-release fc5-press-release-en_US.xml,
1.2, 1.3
Message-ID: <200603160047.k2G0lh0l015406@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15386
Modified Files:
fc5-press-release-en_US.xml
Log Message:
Final edit, minor grammar and brevity clean ups, link to relnotes top center.
Index: fc5-press-release-en_US.xml
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/fc5-press-release-en_US.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fc5-press-release-en_US.xml 16 Mar 2006 00:07:47 -0000 1.2
+++ fc5-press-release-en_US.xml 16 Mar 2006 00:47:35 -0000 1.3
@@ -8,18 +8,26 @@
The Fedora Project is pleased to announce the release of Fedora Core 5. New
desktop applications, advances in security, better localization tools,
- improved software installation and management facilities and strong Java
+ improved software installation and management facilities, and strong Java
integration help to make Fedora Core 5 the most innovative Linux
distribution ever.
+
+ For a more complete list of changes and interesting information for users,
+ administrators, and developers, refer to the latest release notes:
+
+
+
+
+
Getting Fedora Core 5Download ISO Images
Users can download the ISO images of the installation DVD or CD-ROMs now
- from the Fedora web site.
+ from the Fedora Website.
- http://fedoraproject.org/wiki/Distribution/DownloadOnline Vendors
@@ -260,8 +268,8 @@
Internationalization and Localization
Fedora contributors speak many different languages besides C, C++, Python,
- Java, and so on. We are also humans who speak the world's many different
- languages, and we all want Fedora to support as many as possible.
+ Java, and so on. We are also humans who speak the world's languages, and we
+ want Fedora to support as many as possible.
In Fedora Core 5, we have come closer to that goal by adopting SCIM, in
@@ -364,8 +372,8 @@
Fedora Core 5 also offers technology previews for SystemTap and Frysk,
- cutting edge execution analysis tools that will allow developers to
- troubleshoot performance issues to a degree never before possible.
+ cutting edge execution analysis tools that allow developers to troubleshoot
+ performance issues to a degree never before possible.
The Future of Fedora
Fedora contributors are already working toward the next release of Fedora
- Core, which will feature advancements in Xen, and new integration work from
+ Core, which features advancements in Xen, and new integration work from
the Fedora Rendering and One Laptop Per Child (a.k.a. $100 laptop) projects.
- Stateless Linux work is also progressing steadily. We are working on the
+ Stateless Linux work is also progressing steadily. We are working on the
ability to support Fedora Extras and other custom software repositories
during installation. As usual, work continues on new releases of the best
and most robust free and open source software. See our roadmap at:
From fedora-docs-commits at redhat.com Thu Mar 16 18:39:02 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 16 Mar 2006 13:39:02 -0500
Subject: selinux-faq/en_US - New directory
Message-ID: <200603161839.k2GId2eW023433@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23418/en_US
Log Message:
Directory /cvs/docs/selinux-faq/en_US added to the repository
From fedora-docs-commits at redhat.com Thu Mar 16 19:43:08 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 16 Mar 2006 14:43:08 -0500
Subject: selinux-faq/en rpm-info-en.xml, 1.6, NONE selinux-faq-en.xml, 1.4,
NONE
Message-ID: <200603161943.k2GJh8Gc026401@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/selinux-faq/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26362/en
Removed Files:
rpm-info-en.xml selinux-faq-en.xml
Log Message:
This should modify the module to meet modern standards; unless I forgot to add something. Build requires FC4 or later, as it needs DocBook XML 4.4.
--- rpm-info-en.xml DELETED ---
--- selinux-faq-en.xml DELETED ---
From fedora-docs-commits at redhat.com Thu Mar 16 19:43:14 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 16 Mar 2006 14:43:14 -0500
Subject: selinux-faq/en_US doc-entities.xml, NONE, 1.1 selinux-faq.xml, NONE,
1.1
Message-ID: <200603161943.k2GJhE3E026414@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26362/en_US
Added Files:
doc-entities.xml selinux-faq.xml
Log Message:
This should modify the module to meet modern standards; unless I forgot to add something. Build requires FC4 or later, as it needs DocBook XML 4.4.
--- NEW FILE doc-entities.xml ---
These entities are absolutely essential in this document.A per-document entityPer-document EntityShould match the name of this moduleselinux-faqLast revision number, bump when you change the doc1.5.2Last revision date, format YYYY-MM-DD2006-02-10Same for every document
- ()Useful pre-filled bug report; note the changes of the
ampersand and percentage characters to their entity equivalent.
https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Documentation&op_sys=Linux&target_milestone=---&bug_status=NEW&version=devel&component=selinux-faq&rep_platform=All&priority=normal&bug_severity=normal&assigned_to=kwade%40redhat.com&cc=&estimated_time_presets=0.0&estimated_time=0.0&bug_file_loc=http%3A%2F%2Ffedora.redhat.com%2Fdocs%2Fselinux-faq%2F&short_desc=CHANGE%20TO%20A%20REAL%20SUMMARY&comment=%5B%5B%20Description%20of%20change%2FFAQ%20addition.%20%20If%20a%20change%2C%20include%20the%20original%0D%0Atext&!
;percnt;20first%2C%20then%20the%20changed%20text%3A%20%5D%5D%0D%0A%0D%0A%0D%0A%5B%5B%20Version-Release%20of%20FAQ%20%0D%0A%28found%20on%0D%0Ahttp%3A%2F%2Ffedora.redhat.com%2Fdocs%2Fselinux-faq-fc5%2Fln-legalnotice.html%29%3A%0D%0A%0D%0A%20for%20example%3A%20%20selinux-faq-1.5.2%20%282006-03-20%29&status_whiteboard=&keywords=&issuetrackers=&dependson=&blocked=&ext_bz_id=0&ext_bz_bug_id=&data=&desc!
ription=&contenttypemethod=list&contenttypesel!
ection
xt%2Fplain&contenttypeentry=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bugLocally useful.Apache HTTPSet value to your choice, usefule for when guide
version is out of sync with FC release, use instead of FEDVER or
FEDTESTVER5
--- NEW FILE selinux-faq.xml ---
%FEDORA-ENTITIES-EN;
%DOCUMENT-ENTITIES;
]>
WHERE IS MY FDP-INFO, DUDE&SEL; Notes and FAQ
The information in this FAQ is valuable for those who are new to &SEL;. It
is also valuable if you are new to the latest &SEL; implementation in
&FC;, since some of the behavior may be different than you have
experienced.
This FAQ is specific to &FC; &LOCALVER;
If you are looking for the FAQ for other versions of &FC;, refer to
.
For more information about how &SEL; works, how to use &SEL; for general
and specific Linux distributions, and how to write policy, these resources
are useful:
External Link List
NSA &SEL; main website —
NSA &SEL; FAQ —
&SEL; community page —
UnOfficial FAQ —
Writing traditional SE Linux policy HOWTO —
Reference Policy (the new policy found in &FC; 5) —
SELinux policy development training courses — and
Getting Started with SE Linux HOWTO: the new SE Linux (Debian) —
List of SELinux object classes and permissions —
On IRC — irc.freenode.net, #fedora-selinux
&FED; mailing list — ;
read the archives or subscribe at Making changes/additions to the &FED; &SEL; FAQ
This FAQ is available at http://fedora.redhat.com/docs/selinux-faq-fc5/.
For changes or additions to the &FED; &SEL; FAQ, use this bugzilla template, which pre-fills most of the
bug report. Patches should be a diff -u against the
XML, which is available from CVS (refer to for details on
obtaining the fedora-docs/selinux-faq module from anonymous CVS; you can
get just the fedora-docs/selinux-faq module if you
don't want the entire fedora-dcs tree.) Otherwise,
plain text showing before and after is sufficient.
For a list of all bug reports filed against this FAQ, refer to https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=118757.
Understanding &SEL;
What is &SEL;?
&SEL; (Security-Enhanced Linux) in &FC; is
an implementation of mandatory access
control in the Linux kernel using the
Linux Security Modules
(LSM) framework. Standard Linux security is a
discretionary access control model.
Discretionary access control (DAC)
DAC is standard Linux security, and it provides no
protection from broken software or malware running as a
normal user or root. Users can grant risky levels of access
to files they own.
Mandatory access control (MAC)
MAC provides full control over all interactions of
software. Administratively defined policy closely controls
user and process interactions with the system, and can
provide protection from broken software or malware running
as any user.
In a DAC model, file and resource decisions are based solely on
user identity and ownership of the objects. Each user and program
run by that user has complete discretion over the user's objects.
Malicious or flawed software can do anything with the files and
resources it controls through the user that started the process.
If the user is the super-user or the application is
setuid or setgid to root,
the process can have root level control over the entire file
system.
A MAC system does not suffer from these problems. First, you can
administratively define a security policy over all processes and
objects. Second, you control all processes and objects, in the
case of &SEL; through the kernel. Third, decisions are based on
all the security relevant information available, and not just
authenticated user identity.
MAC under &SEL; allows you to provide granular permissions for all
subjects (users, programs, processes) and
objects (files, devices). In practice,
think of subjects as processes, and objects as the target of a
process operation. You can safely grant a process only the
permissions it needs to perform its function, and no more.
The &SEL; implementation uses role-based access
control (RBAC), which provides
abstracted user-level control based on roles, and
Type
Enforcement (TE). TE
uses a table, or matrix to handle access
controls, enforcing policy rules based on the types of processes
and objects. Process types are called
domains, and a cross-reference on the
matrix of the process's domain and the object's type defines their
interaction. This system provides extremely granular control for
actors in a Linux system.
What is &SEL; policy?
The &SEL; policy describes the access permissions for all subjects
and objects, that is, the entire system of users, programs, and
processes and the files and devices they act upon. &FC; policy is
delivered in a package, with an associated source package. Current
shipping policy packages are:
selinux-policy-<version>.noarch.rpm
This package is common to all types of policy and contains
config files/man pages.
selinux-policy-devel-<version>.noarch.rpm
This is the development environment. This replaces the
-sources package from the past. This package contains the
interface files used in reference policy along with a
Makefile and a small tool used to generate a policy template
file. The interface files reside in
/usr/share/selinux/refpolicy/headers directory.
selinux-policy-strict-<version>.noarch.rpmselinux-policy-targeted-<version>.noarch.rpmselinux-policy-mls-<version>.noarch.rpm
Binary policy files are in /etc/selinux/policyname. The
policy for the types and domains is configured separately
from security context for the subjects and objects.
What is the &SEL; targeted policy?
When &SEL; was initially introduced in &FC;, it enforced the NSA
strict policy. For testing purposes, this effectively exposed
hundreds of problems in the strict policy. In addition, it
demonstrated that applying a single strict policy to the many
environments of &FED; users was not feasible. To manage a single
strict policy for anything other than default installation would
require local expertise.
At this point, the &SEL; developers reviewed their choices, and
decided to try a different strategy. They decided to create a
targeted policy that locks down specific
daemons, especially those vulnerable to attack or which could
devastate a system if broken or compromised. The rest of the
system runs exactly as it would under standard Linux DAC security.
Under the targeted policy, most processes run in the
unconfined_t domain. As the name
implies, these processes are mostly unconfined by the &SEL;
policy. They are still governed by standard Linux DAC security,
however.
Those network daemons which are addressed in the targeted policy
make a transition to the targeted policy when the application
starts. For example, at system boot, init runs
under the unconfined_t policy.
When named starts, it makes a transition to the
named_t domain and is locked down
by the appropriate policy.
For more information on enabling or disabling targeted policy on
each of the specific daemons, refer to .
What daemons are protected by the targeted policy?
Currently, the list of daemons is:
dhcpdhttpd
(apache.te)namednscdntpdportmapsnmpdsquidsyslogd
The policy files for these daemons are found in
/etc/selinux/targeted/src/policy/domains/program.
In the future, more daemons will be added to the targeted policy
protection.
Which daemons will you add to the targeted policy? How about
Sendmail, Postfix, MySQL, or PostgreSQL?
&SEL; developers would like to add ftp and mail agents to targeted
policy eventually. For example, vsftpd could
work similar to login: after log-in, a new
process would be executed under the user's context (real user or
an anonymous context).
Mail agents can be problematic because they often need to
manipulate files in user home directories. One objective of the
targeted policy is to avoid labeling problems in the user home
directories. &SEL; developers continue to work on this problem.
What about the strict policy? Does it even work?
The strict policy does work on &FC;. It is
challenged by the unique environments of different users. To use
the strict policy in your environment, you may need to fine-tune
both the policy and your systems.
To make the strict policy easier to use, &SEL; developers have
tried to make the change from one policy to the other easier.
For example, system-config-securitylevel builds
a relabel into the startup scripts.
What is the mls policy? Who is it for?
The mls policy is similar to the strict policy, but adds an
additional field to security contexts for separating levels. &SEL;
can use these levels to separate data in an environment that calls
for strict hierarchical separation. A typical example is a
military setting, where data is classified at a certain level.
This policy is geared toward this sort of environment, and is
probably not useful to you unless you fall into this category.
What is the Reference Policy?
The Reference Policy
is a new project designed to rewrite the entire SELinux policy in a
way that is easier to use and understand. To do this, it uses
the concepts of modularity, abstraction, and well-defined interfaces.
Refer to
for more information on the Reference Policy.
Fedora policies at version 1.x are based on the traditional example
policy. Version 2.x policies (as used in &FC; &LOCALVER;) are based
on the Reference Policy.
What are file contexts?
File contexts are used by the
setfiles command to generate persistent labels
which describe the security context for a file or directory.
&FC; ships with the fixfiles script, which
supports three options: ,
, and . This
script allows users to relabel the file system without having the
selinux-policy-targeted-sources package
installed. The command line usage is more friendly than the
standard setfiles command.
How do I view the security context of a file, user, or process?
The new option is the short method for
displaying the context of a subject or object:
ls -alZ file.foo
id -Z
ps -eZ
What is the difference between a domain and
a type?
There is no difference between a domain and a type, although
domain is sometimes used to refer to the type of a process. The
use of domain in this way stems from Domain and Type Enforcement
(DTE) models, where domains and types are separate.
Controlling &SEL;
How do I install/not install &SEL;?
The installer follows the choice you make in the
Firewall Configuration screen. The default
running policy is the targeted policy, and it is on by default.
How do I switch the policy I am currently using?
Use caution when switching policy
Other than trying out a new policy on a test machine for
research purposes, you should seriously consider your situation
before switching to a different policy on a production system.
The act of switching is straightforward. This method is fairly
safe, but you should try it first on a test system.
To use the automated method, run the Security Level
Configuration tool. From the GUI Main Menu,
select DesktopSystem SettingsSecurity level, or from a terminal, run
system-config-securitylevel. Change the
policy as desired and ensure that the Relabel on next
reboot option is enaled.
You can also perform these steps manually with the following
procedure:
Edit /etc/selinux/config and change the
type and the mode of policy:
SELINUXTYPE=policyname
SELINUX=permissive
This step ensures you will not be locked out after rebooting.
&SEL; will run under the correct policy, but will allow you to
login if there is a problem such as incorrect file context
labeling.
Set the system to relabel the file system on reboot:
touch /.autorelabel
Reboot the system. A clean restart under the new policy
allows all system processes to be started in the proper
context, and reveals any problems in the policy change.
Confirm your changes took effect with the following command:
sestatus -v
With the new system running in
permissive mode, check
/var/log/messages for
avc: denied messages. These
may indicate a problem that needs to be solved for the system
to run without trouble under the new policy.
When you are satisfied that the system runs stable under the
new policy, enable enforcing by changing
SELINUX=enforcing. You can
either reboot or run setenforce 1 to turn
enforcing on in real time.
How can I back up files from an &SEL; file system?
Use the star utility, which supports the
extended attributes that store the security context labels.
Specify the and
options when creating archives.
ls -Z /var/log/maillog
-rw------- root root system_u:object_r:var_log_t /var/log/maillog
cd /var/log
star -xattr -H=exustar -c -f maillog.star ./maillog*Absolute paths can overwrite existing data
If you use an absolute path, such as
/var/log/maillog, when you unpack the
archive with star -c
-f, the files will be restored on the same path they
were archived with. The maillog file will
attempt to write to /var/log/maillog. You
should received a warning from star if the
files about to be overwritten have a later date, but you cannot
rely on this behavior.
Consider carefully how you construct your archiving argument.
How can I install the strict policy by default with kickstart?
Under the %packages section,
add selinux-policy-strict.
Under the %post section,
add the following:
lokkit -q --selinuxtype=strict
touch /.autorelabel
How do I enable/disable &SEL; protection on specific daemons under
the targeted policy?
Use system-config-securitylevel, also known as
the Security Level Configuration
graphical tool, to control the
Boolean values of specific daemons. For example, if you need to
disable &SEL; for Apache to run correctly in your environment, you
can disable the value in
system-config-securitylevel. This change
disables the transition to the policy defined in
apache.te, allowing httpd
to remain under regular Linux DAC security.
How do I make a user public_html directory
work under &SEL;?
This process presumes that you have enabled user public HTML
directories in your Apache configuration file,
/etc/httpd/conf/httpd.conf. This process
only covers serving static Web content. For more information
about &APACHE; and &SEL;, refer to .
If you do not already have a
~/public_html directory, create it and
populate it with the files and folders to be served.
cd ~
mkdir public_html
cp /path/to/content ~/public_html
At this point, httpd is configured to serve
the contents, but you will still receive a 403
forbidden error. This is because
httpd is not allowed to read the security
type for the directory and files as they are created in the
user's home directory. Change the security context of the
folder and its contents recursively using the
option:
ls -Z -d public_html/drwxrwxr-x auser auser user_u:object_r:user_home_t public_htmlchcon -R -t httpd_user_content_t public_html/
ls -Z -d public_html/drwxrwxr-x auser auser user_u:object_r:httpd_user_content_t public_html/ls -Z public_html/-rw-rw-r-- auser auser user_u:object_r:httpd_user_content_t bar.html
-rw-rw-r-- auser auser user_u:object_r:httpd_user_content_t baz.html
-rw-rw-r-- auser auser user_u:object_r:httpd_user_content_t foo.html
You may notice at a later date that the user field, set here
to user_u, is changed to
system_u. This does not
affect how the targeted policy works. The field that matters
is the type field.
Your static webpages should now be served correctly. If you
continue to have errors, ensure that the Boolean which enables
user home directories is enabled. You can set it using
system-config-securitylevel. Select
the &SEL; tab, and then select the
Modify &SEL; Policy area. Select
Allow HTTPD to read home
directories. The changes take effect
immediately.
How do I turn &SEL; off at boot?
Set SELINUX=disabled in
/etc/selinux/config.
Alternatively, you can add to your
kernel boot parameters. However, this option is not recommended.
Be careful when disabling &SEL;
If you boot with , any files you
create while &SEL; is disabled will not have &SEL; context
information. The file system will be marked for relabeling at
the next boot. If an unforeseen problem prevents you from
rebooting normally, you may need to boot in single-user mode for
recovery. Add the option to your
kernel boot parameters.
How do I turn enforcing on/off at boot?
You can specify the &SEL; mode using the configuration file
/etc/sysconfig/selinux.
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=enforcing# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted
Setting the value to enforcing is
the same as adding to the kernel boot
parameters. Setting the value to
permissive is the same as adding
to the kernel boot parameters.
However, setting the value to
disabled is not the same as the
kernel boot parameter. Rather than
fully disabling &SEL; in the kernel, the
disabled setting instead turns
enforcing off and skips loading a policy.
&SEL; Configuration Precedence
The command line kernel parameter overrides the configuration
file.
How do I temporarily turn off enforcing mode without having to
reboot?
Occasionally you may need to perform an action that is normally
prevented by policy. Run the command setenforce
0 to turn off enforcing mode in real time. When you
are finished, run setenforce 1 to turn
enforcing back on.
<computeroutput>sysadm_r</computeroutput> Role
Required
You must issue the setenforce command with
the sysadm_r role. Use the
newrole command to assume this role.
Alternately, if you switch to root using su
-, you assume the
sysadm_r role automatically.
How do I turn system call auditing on/off at boot?
Add to your kernel command line to turn
system call auditing on. Add to your
kernel command line to turn system call auditing off.
System-call auditing is on by default. When
on, it provides information about the system call that was
executing when SELinux generated a
denied message. The error
message is helpful when debugging policy.
How do I temporarily turn off system-call auditing without having
to reboot?
Run auditctl -e 0. Note that this command
will not affect auditing of SELinux AVC denials.
How do I get status info about my &SEL; installation?
As root, execute the command /usr/sbin/sestatus
-v. For more information, refer to the
sestatus(8) manual page.
Resolving Problems
My application isn't working as expected and I am seeing
avc: denied messages. How do I
fix this?
This message means that the current SELinux policy is not allowing
the application to do something. There are a number of reasons
this could happen.
First, one of the files the application is trying to access could
be mislabeled. If the AVC message refers to a specific file,
inspect its current label with ls -alZ
/path/to/file. If it seems
wrong, use the command restorecon -v
/path/to/file to restore
the file's default context. If you have a large number of denials
related to files, you may want to use fixfiles
relabel, or run restorecon -R
/path to recursively
relabel a directory path.
Denials are sometimes due to a configuration change in the program
that triggered the denial message. For example, if you change
Apache to also listen on port 8800, you must also change the
security policy, apache.te. Refer to
for more information about
writing policy.
If you are having trouble getting a specific application like
Apache to work, refer to
for information on disabling enforcement just for that
application.
I installed &FC; on a system with an existing
/home partition, and now I can't log in.
Your /home partition is not labeled
correctly. You can easily fix this two different ways.
If you just want to relabel /home
recursively:
/sbin/restorecon -v -R /home
If you want to be sure there are no other files incorrectly
labeled, you can relabel the entire file system:
/sbin/fixfiles relabel
You must have the policycoreutils package
installed to use fixfiles.
After relabeling my /home using
setfiles or fixfiles, will I
still be able to read /home with a
non-&SEL;-enabled system?
You can read the files from a non-&SEL; distribution, or one with
&SEL; disabled. However, files created by a system not using &SEL;
systems will not have a security context, nor will any files you
remove and recreate. This could be a challenge with files such as
~/.bashrc. You may have to relabel
/home when you reboot the &SEL; enabled &FC;
system.
How do I share directories using NFS between &FC; and non-&SEL;
systems?
Just as NFS transparently supports many file system types, it can
be used to share directories between &SEL; and non-&SEL; systems.
When you mount a non-&SEL; file system via NFS, by default &SEL;
will treat all the files in the share as having a context of
nfs_t. You can override the
default context by setting it manually, using the
option. The following command makes
the files in the NFS mounted directory appear to have a context of
system_u:object_r:tmp_t to &SEL;:
mount -t nfs -o context=system_u:object_r:tmp_t server:/shared/foo /mnt/foo
When &SEL; exports a file system via NFS, newly created files have
the context of the directory they were created in. In other
words, the presence of &SEL; on the remote mounting system has no
effect on the local security contexts.
How can I create a new Linux user account with the user's home
directory having the proper context?
You can create your new user with the standard
useradd command. First you must become
root. Under the strict
policy you will need to change role to
sysadm_r with the following
command:
newrole -r sysadm_r
For the targeted policy you will not need
to switch roles, staying in
unconfined_t:
su - root
id -Zroot:system_r:unconfined_tuseradd auser
ls -Z /homedrwx------ auser auser root:object_r:user_home_dir_t /home/auser
The initial context for a new user directory has an identity of
root. Subsequent relabeling of
the file system will change the identity to
system_u. These are functionally
the same since the role and type are identical
(object_r:user_home_dir_t.)
I'm having troubles with avc errors filling my
logs for a particular program. How do I choose not to audit the
access for it?
If you wanted to not audit dmesg, for example,
you would put this in your
/etc/selinux/targeted/src/policy/dmesg.te
file:
dontaudit dmesg_t userdomain:fd { use };
This eliminates the error output to the terminal for all
user domains, including user,
staff and sysadm.
Even running in permissive mode, I'm getting a large number of
avc denied messages.
In a non-enforcing mode, you should actually receive
more messages than in enforcing mode. The
kernel logs each access denial as if you were in an enforcing
mode. Since you are not restricted by policy enforcement, you can
perform more actions, which results in more denials being logged.
If an application running under an enforcing mode is denied
access to read a number of files in a directory, it is
stopped once at the beginning of the action. In a non-enforcing
mode, the application is not stopped from traversing the directory
tree, and generates a denial message for each file read in the
directory.
Why do I not see the output when I run certain daemons in debug or
interactive mode?
&SEL; intentionally disables access to the tty devices to stop
daemons from communicating back with the controlling terminal.
This communication is a potential security hole because such
daemons could insert commands into the controlling terminal. A
broken or compromised program could use this hole to cause serious
problems.
There are a few ways you can capture standard output from
daemons. One method is to pipe the output to the cat command.
snmpd -v | cat
When debugging a daemon, you may want to turn off the transition
of the daemon to its specific domain. You can do this using
system-config-securitylevel or
setsebool on the command line.
A final option is to turn off enforcing mode while debugging.
Issue the command setenforce 0 to turn off
enforcing mode, and use the command setenforce
1 to re-enable &SEL; when you are finished debugging.
When I do an upgrade of the policy package (for example, using
yum), what happens with the policy? Is it
updated automatically?
Policy reloads itself when the package is updated. This behavior
replaces the manual make load.
In certain situations, you may need to relabel the file system.
This might occur as part of an &SEL; bug fix where file contexts
become invalid, or when the policy update makes changes to the
file
/etc/selinux/targeted/contexts/files/file_contexts.
After the file system is relabeled, a reboot is
not required, but is useful in ensuring every process and program
is running in the proper domain. This is highly dependent on the
changes in the updated policy.
To relabel, you have several options. You may use the
fixfiles command:
fixfiles relabel
reboot
Alternately, use the /.autorelabel mechanism:
touch /.autorelabel
reboot
If the policy shipping with an application package changes in a
way that requires relabeling, will RPM handle relabeling the files
owned by the package?
Yes. The security contexts for the files owned by the package are
stored in the header data for the package. The file contexts are
set directly after the cpio copy, as the
package files are being put on the disk.
Why do binary policies distributed with Fedora, such as
/etc/selinux/<policyname>/policy/policy.<version>,
and those I compile myself have different sizes and MD5 checksums?
When you install a policy package, pre-compiled binary policy
files are put directly into /etc/selinux.
The different build environments will make target files that have
different sizes and MD5 checksums.
Will new policy packages disable my system?
There is a possibility that changes in the policy package or in
the policy shipping with an application package can cause errors,
more denials, or other unknown behaviors. You can
discover which package caused the breakage by reverting policy and
application packages one at a time. If you don't want to return
to the previous package, the older version of the configuration
files will be saved with the extension .rpmsave. Use the
mailing lists, bugzilla, and IRC to help you work through your
problem. If you are able, write or fix policy to resolve your
problem.
How can I help write policy?
Your help is definitely appreciated.
You can start by joining the &FED; &SEL; mailing list. You can
subscribe and read the archives at .
The Unofficial FAQ has some generic policy writing HOWTO
information. Refer to
for more information.
Another new resource is the Writing SE Linux policy HOWTO,
located online at .
Also, since the &FC; &LOCALVER; policy is based on the , you should look at the
documentation on its project page. Another excellent source of
information is the policy files in
/usr/share/doc/selinux-policy->version<
which shows examples of policy.
If you want to write a new policy domain, you should install the
selinux-policy-devel package. This will place
reference policy interface files into the
/usr/share/selinux/refpolicy directory.
There are also tools available to help you generate new policy.
The following procedure is an example:
Use the policygentool command to generate
your own te, fc and
if files. The
policygentool command takes two parameters:
the name of the policy module and the full path to the
executable. The following command gives a usage example:
policygentool mydaemon /usr/sbin/mydaemon
This command creates three files:
mydaemon.te,
mydaemon.fc and
mydaemon.if.
After you generate the policy files, use the supplied
Makefile,
/usr/share/selinux/refpolicy/Makefile, to
build a policy package:
make -f /usr/share/selinux/refpolicy/Makefile
Now you can load the policy module, using
semodule, and relabel the executable using
restorecon:
semodule -i mydaemon.pprestorecon -v /usr/sbin/mydaemon
Since you have very limited policy for your executeable,
SELinux will prevent it from doing much. Turn on permissive
mode and then use the init script to start your daemon:
setenforce 1service mydaemon restart
Now you can collect avc messages. You can use
audit2allow to translate the avc messages to
allow rules and begin updating you
mydaemon.te file. You should search for
interface macros in the
/etc/selinux/refpolicy/include directory and
use these instead of using the allow rules directly, whenever
possible. If you want more examples of polcy, you could always
install the selinux-policy src rpm, which contains all of the
policy te files for the reference policy.
My console is being flooded with messages. How do I turn them
off?
To regain useful control, turn off kernel messages to the console
with this command:
dmesg -n 1
Can I test the default policy without installing the policy
source?
You can test &SEL; default policy by installing just the
selinux-policy-policyname
and policycoreutils packages. Without the
policy source installed, the fixfiles command
automates the file system relabeling.
The command fixfiles relabel is the equivalent
of make relabel. During the relabeling, it
will delete all of the files in /tmp,
cleaning up files which may have old file context labels.
Other commands are fixfiles check, which checks
for mislabeled files, and fixfiles restore,
which fixes the mislabeled files but does not delete the files in
/tmp. The fixfiles
command does not take a list of directories as an argument,
because it relabels the entire file system. If you need to
relabel a specific directory path, use
restorecon.
Why are some of my KDE applications having trouble under &SEL;?
KDE executables always appear as kdeinit, which
limits what can be done with &SEL; policy. This is because every
KDE application runs in the domain for kdeinit.
Problems often arise when installing &SEL; because it is not
possible to relabel /tmp and
/var/tmp. There is no good method of
determining which file should have which context.
The solution is to fully log out of KDE and remove all KDE
temporary files:
rm -rf /var/tmp/kdecache-<username>
rm -rf /var/tmp/<other_kde_files>
At your next login, your problem should be fixed.
Why does not work for me?
Be careful of white space in the file
/etc/sysconfig/selinux. The code is very
sensitive to white space, even trailing space.
Deploying &SEL;
What file systems can I use for &SEL;?
The file system must support
xattr labels in the right
security.* namespace. In addition to
ext2/ext3, XFS has recently added support for the necessary
labels.
Note that XFS SELinux support is broken in upstream kernel
2.6.14 and 2.6.15, but fixed (worked around)
in 2.6.16. Your kernel must include this fix if
you choose to use XFS with &SEL;.
How does &SEL; impact system performance?
This is a variable that is hard to measure, and is heavily
dependent on the tuning and usage of the system running &SEL;.
When performance was last measured, the impact was around 7% for
completely untuned code. Subsequent changes in system components
such as networking are likely to have made that worse in some
cases. &SEL; performance tuning continues to be a priority of the
development team.
What types of deployments, applications, and systems should I
leverage &SEL; in?
Initially, &SEL; has been used on Internet facing servers that are
performing a few specialized functions, where it is critical to
keep extremely tight security. Administrators typically strip
such a box of all extra software and services, and run a very
small, focused set of services. A Web server or mail server is a
good example.
In these edge servers, you can lock down the policy very tightly.
The smaller number of interactions with other components makes
such a lockdown easier. A dedicated system running a specialized
third-party application would also be a good candidate.
In the future, &SEL; will be targeted at all environments. In
order to achieve this goal, the community and
independent software vendors
(ISVs) must work with the &SEL; developers to
produce the necessary policy. So far, a very restrictive
strict policy has been written, as well as
a targeted policy that focuses on specific,
vulnerable daemons.
For more information about these policies, refer to and .
How does &SEL; affect third-party applications?
One goal of implementing a targeted &SEL; policy in &FC; is to
allow third-party applications to work without modification. The
targeted policy is transparent to those unaddressed applications,
and it falls back on standard Linux DAC security. These
applications, however, will not be running in an extra-secure
manner. You or another provider must write policy to protect these
applications with MAC security.
It is impossible to predict how every third-party application
might behave with &SEL;, even running the targeted policy. You
may be able to fix issues that arise by changing the policy. You
may find that &SEL; exposes previously unknown security issues
with your application. You may have to modify the application to
work under &SEL;.
One important value that &FC; testers and users bring to the
community is extensive testing of third-party applications. With
that in mind, please bring your experiences to the appropriate
mailing list, such as the fedora-selinux.list, for discussion. For
more information about that list, refer to .
From fedora-docs-commits at redhat.com Thu Mar 16 19:43:03 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 16 Mar 2006 14:43:03 -0500
Subject: selinux-faq rpm-info.xml,1.3,1.4 Makefile,1.5,1.6
Message-ID: <200603161943.k2GJhXRA026418@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26362
Modified Files:
Makefile
Added Files:
rpm-info.xml
Log Message:
This should modify the module to meet modern standards; unless I forgot to add something. Build requires FC4 or later, as it needs DocBook XML 4.4.
Index: rpm-info.xml
===================================================================
RCS file: rpm-info.xml
diff -N rpm-info.xml
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ rpm-info.xml 16 Mar 2006 19:42:55 -0000 1.4
@@ -0,0 +1,55 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ GNU FDL
+ 1.0
+
+
+ 2004
+ 2005
+ Red Hat, Inc.
+ Karsten Wade
+
+
+ 2006
+ Chad Sellers
+ Paul W. Frields
+
+
+
+ Fedora Core 5 SELinux FAQ
+ Frequently asked questions about SELinux in Fedora Core 5
+
+
+ Fedora Core 5 SELinux FAQ
+
+
+
+
+
+
+ Make admonition more easily maintainable
+
+
+
+ Style and readability editing; some element clarifications
+
+
+
+ First round of editing.
+ Primo round di editing.
+
+
+
Index: Makefile
===================================================================
RCS file: /cvs/docs/selinux-faq/Makefile,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- Makefile 7 Dec 2005 17:21:12 -0000 1.5
+++ Makefile 16 Mar 2006 19:42:55 -0000 1.6
@@ -1,22 +1,43 @@
-###############################################################################
-# Makefile for RHLP docs project
-# Created by: Tammy Fox
-# Last edited by: Tommy Reynolds
-# WARNING: need passivetex 1.24 for pdf generation to work
-# License: GPL
-# Copyright 2003 Tammy Fox, Red Hat, Inc.
-# Copyright 2005 Tommy Reynolds, MegaCoder.com
-###############################################################################
+########################################################################
+# NOTICE
+#-----------------------------------------------------------------------
+# There is actually no "de" translation. All the '*de*" files are just
+# fodder to check the internationalization (i18n) workings for the FTP.
+# No discourtesy to any German speaker is intended. -- Tommy Reynolds
+# Actual translations welcome.
+########################################################################
-LANGUAGES = en it
-DOCBASE = selinux-faq
-XMLEXTRAFILES-en =
-XMLEXTRAFILES-it =
+########################################################################
+# Fedora Documentation Project Per-document Makefile
+# License: GPL
+# Copyright 2005,2006 Tommy Reynolds, MegaCoder.com
+########################################################################
+#
+# Document-specific definitions.
+#
+DOCBASE = selinux-faq
+PRI_LANG = en_US
+# OTHERS =
+# If ${DOC_ENTITIES} is defined, ${PRI_LANG}/${DOC_ENTITIES}.xml
+# must contain a complete XML file conforming to the DTD located
+# in the "docs-common/common/entities/entities.dtd" file. Do NOT
+# reference this file in the XMLFILES_template below.
+DOC_ENTITIES = doc-entities
+########################################################################
+# List each XML file of your document in the template below. Append the
+# path to each file to the "XMLFILES-${1}" string. Use a backslash if you
+# need additional lines. Here, we have one extra file "en/para.xml"; that
+# gets written as "${1}/para.xml" because later, make(1) will need to compute
+# the necesssary filenames. Oh, do NOT include "fdp-info.xml" because that's
+# a generated file and we already know about that one...
-######################################################
+define XMLFILES_template
+XMLFILES-${1}=${1}/${DOCBASE}.xml
+endef
+#
+########################################################################
include ../docs-common/Makefile.common
-######################################################
-
+########################################################################
# If you want to add additional steps to any of the
# targets defined in "Makefile.common", be sure to use
# a double-colon in your rule here. For example, to
@@ -25,3 +46,4 @@
# line:
#${DOCNAME}/index.html::
# echo FINISHED AT LAST
+########################################################################
From fedora-docs-commits at redhat.com Thu Mar 16 20:09:19 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 16 Mar 2006 15:09:19 -0500
Subject: marketing-content/FC-5-press-release fdp-pr.xsl,1.1.1.1,1.2
Message-ID: <200603162009.k2GK9JmH031407@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31252
Modified Files:
fdp-pr.xsl
Log Message:
Trying out this new XSL to make prettier PDFs, still with a few minor formatting details, such as the header, to be fixed. We'll submit this back for press-release as the new stylesheet after we work out the kinks.
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/fdp-pr.xsl,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- fdp-pr.xsl 14 Mar 2006 20:46:35 -0000 1.1.1.1
+++ fdp-pr.xsl 16 Mar 2006 20:09:11 -0000 1.2
@@ -36,10 +36,10 @@
-
+
-
+
@@ -79,17 +79,17 @@
-
+
-
+
-
+
From fedora-docs-commits at redhat.com Thu Mar 16 20:50:29 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 16 Mar 2006 15:50:29 -0500
Subject: marketing-content/FC-5-press-release fdp-pr.xsl, 1.2, 1.3 fdp-pr.dtd,
1.2, 1.3
Message-ID: <200603162050.k2GKoTo3008946@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8718
Modified Files:
fdp-pr.xsl fdp-pr.dtd
Log Message:
Changes to DTD and XSL to make thinks look better, sound better.
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/fdp-pr.xsl,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fdp-pr.xsl 16 Mar 2006 20:09:11 -0000 1.2
+++ fdp-pr.xsl 16 Mar 2006 20:50:20 -0000 1.3
@@ -26,8 +26,8 @@
-
-
+
+
@@ -36,10 +36,9 @@
-
+
-
-
+
Index: fdp-pr.dtd
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/fdp-pr.dtd,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fdp-pr.dtd 16 Mar 2006 00:33:45 -0000 1.2
+++ fdp-pr.dtd 16 Mar 2006 20:50:20 -0000 1.3
@@ -1,18 +1,22 @@
-
-
+
-
-
-
-
-
+
+
+
+
+
+
+
+
-
-
+
+
+
-
-
-
+
+
-
-
\ No newline at end of file
+
+
+
+
From fedora-docs-commits at redhat.com Thu Mar 16 20:51:00 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 16 Mar 2006 15:51:00 -0500
Subject: marketing-content/FC-5-press-release fc5-press-release-en_US.xml,
1.3, 1.4
Message-ID: <200603162051.k2GKp0lK009653@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9462
Modified Files:
fc5-press-release-en_US.xml
Log Message:
Fixing ULINK style, to match DTD requirements.
Index: fc5-press-release-en_US.xml
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/fc5-press-release-en_US.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- fc5-press-release-en_US.xml 16 Mar 2006 00:47:35 -0000 1.3
+++ fc5-press-release-en_US.xml 16 Mar 2006 20:50:52 -0000 1.4
@@ -2,7 +2,9 @@
- Fedora Project
+
Presenting Fedora Core 5
@@ -27,8 +29,7 @@
from the Fedora Website.
- http://fedoraproject.org/wiki/Distribution/Download
+ Online Vendors
@@ -38,12 +39,10 @@
containing Fedora Core, as long as they comply with the guidelines.
- http://fedoraproject.org/wiki/Distribution/OnlineVendors
+
- http://fedoraproject.org/wiki/Legal/TrademarkGuidelines
+ Fedora Community Free Media
@@ -53,12 +52,10 @@
participate.
- http://fedoraproject.org/wiki/FreeMedia
+
- http://fedoraproject.org/wiki/Ambassadors
+ What's New In Fedora Core 5
@@ -69,8 +66,7 @@
desktop team. Take a tour at:
- http://fedoraproject.org/wiki/Tours/FedoraCore5
+ Desktop
@@ -82,23 +78,20 @@
way that some Fedora users and developers work.
- http://www.beatniksoftware.com/tomboy/
+
Thanks to F-Spot, managing digital photographs is easier than ever.
- http://f-spot.org/Main_Page
+
If you are looking for something in a chat log, an email, or a web page you
visited days ago, Beagle helps you find it.
- http://beaglewiki.org/Main_Page
+
We are also pleased to introduce Accelerated Indirect GLX (AIGLX) support in
@@ -108,8 +101,7 @@
platform for creating a high-performance, efficient, and elegant desktop.
- http://fedoraproject.org/wiki/RenderingProject
+
Power management has been improved thanks to GNOME Power Manager, included
@@ -117,12 +109,10 @@
Fedora screensaver to accompany it.
- http://www.gnome.org/projects/gnome-power-manager/
+
- http://live.gnome.org/GnomeScreensaver/
+
Integration, testing, and development was done to verify that suspend and
@@ -135,12 +125,10 @@
which is based on the 2.6.16 kernel release.
- http://bcm43xx.berlios.de/
+
- http://wiki.kernelnewbies.org/LinuxChanges
+
Fedora Core 5 also features updated versions of old favorites. The latest
@@ -151,20 +139,17 @@
bring a many new features and improvements to the Fedora desktop.
- http://www.mozilla.com/firefox/releases/1.5.html
+
- http://www.openoffice.org/product/index.html
+
- http://www.gnome.org/start/2.14/notes/C/
+ http://kde.org/announcements/announce-3.5.php
+ url='http://kde.org/announcements/announce-3.5.php'/>
Finally, the Fedora Core 5 desktop features new advances in multimedia
@@ -175,7 +160,7 @@
development of free media formats.
- http://www.xiph.org
+ Software Installation and Management
@@ -216,8 +201,7 @@
virtualization ubiquitous and seamless in Fedora.
- http://fedoraproject.org/wiki/Tools/Xen
+ Security
@@ -231,7 +215,7 @@
http://fedoraproject.org/wiki/Security/Features?highlight=%28fstack%29
+ url='http://fedoraproject.org/wiki/Security/Features?highlight=%28fstack%29'/>
Fedora has switched to using the reference policy for the SELinux security
@@ -246,11 +230,10 @@
http://fedoraproject.org/wiki/Security
+ url='http://fedoraproject.org/wiki/Security'/>
- http://serefpolicy.sourceforge.net/
+
Linux Unified Key Support (LUKS) provides hard disk encryption support in
@@ -262,7 +245,7 @@
http://fedoraproject.org/wiki/Software/LUKS
+ url='http://fedoraproject.org/wiki/Software/LUKS'/>
Internationalization and Localization
@@ -278,7 +261,7 @@
than ever before.
- http://www.scim-im.org/
+ Java
@@ -307,11 +290,11 @@
http://fedoraproject.org/wiki/Java
+ url='http://fedoraproject.org/wiki/Java'/>
http://www.gnu.org/philosophy/java-trap.html
+ url='http://www.gnu.org/philosophy/java-trap.html'/>
Under the Hood
@@ -328,15 +311,15 @@
http://httpd.apache.org/docs/2.2/new_features_2_2.html
+ url='http://httpd.apache.org/docs/2.2/new_features_2_2.html'/>
http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html
+ url='http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html'/>
http://www.postgresql.org/docs/whatsnew
+ url='http://www.postgresql.org/docs/whatsnew'/>
X.Org has been completely modularized and Fedora Core includes the latest
@@ -351,7 +334,7 @@
http://gstreamer.freedesktop.org/
+ url='http://gstreamer.freedesktop.org/'/>
We have the latest version of the GNU Compiler Collection, GCC 4.1, which
@@ -360,7 +343,7 @@
repositories. GCJ, a critical part of our free Java environment, is
included. There is also an implementation of the OpenMP parallel
programming standard (http://www.openmp.org/) for C, C++
+ url='http://www.openmp.org/'/>) for C, C++
and Fortran. Use the compiler switch -fopenmp to enable it.
@@ -368,7 +351,7 @@
http://gcc.gnu.org/gcc-4.1/changes.html.
+ url='http://gcc.gnu.org/gcc-4.1/changes.html'/>
Fedora Core 5 also offers technology previews for SystemTap and Frysk,
@@ -377,11 +360,11 @@
http://fedoraproject.org/wiki/SystemTap
+ url='http://fedoraproject.org/wiki/SystemTap'/>
http://fedoraproject.org/wiki/Frysk
+ url='http://fedoraproject.org/wiki/Frysk'/>
The Future of Fedora
@@ -396,14 +379,14 @@
http://fedoraproject.org/wiki/RoadMap
+ url='http://fedoraproject.org/wiki/RoadMap'/>
http://fedoraproject.org/wiki/OLPC
+ url='http://fedoraproject.org/wiki/OLPC'/>
http://fedoraproject.org/wiki/StatelessLinux
+ url='http://fedoraproject.org/wiki/StatelessLinux'/>
From fedora-docs-commits at redhat.com Thu Mar 16 20:53:23 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 16 Mar 2006 15:53:23 -0500
Subject: press-release fdp-pr.dtd,1.4,1.5 fdp-pr.xsl,1.9,1.10
Message-ID: <200603162053.k2GKrNrv012811@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv12607
Modified Files:
fdp-pr.dtd fdp-pr.xsl
Log Message:
Checkpoint
Index: fdp-pr.dtd
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.dtd,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fdp-pr.dtd 11 Mar 2006 16:46:23 -0000 1.4
+++ fdp-pr.dtd 16 Mar 2006 20:53:15 -0000 1.5
@@ -2,7 +2,7 @@
-
+
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.xsl,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- fdp-pr.xsl 15 Mar 2006 15:17:17 -0000 1.9
+++ fdp-pr.xsl 16 Mar 2006 20:53:15 -0000 1.10
@@ -4,8 +4,7 @@
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:date="http://exslt.org/dates-and-times"
- extension-element-prefixes="date"
->
+ extension-element-prefixes="date">
en_US
@@ -45,11 +44,11 @@
-
+
-
-
-
+
+
+
@@ -88,8 +87,7 @@
-
-
+
From fedora-docs-commits at redhat.com Thu Mar 16 21:50:45 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Thu, 16 Mar 2006 16:50:45 -0500
Subject: marketing-content/FC-5-press-release fc5-press-release-it_IT.xml,
NONE, 1.1
Message-ID: <200603162150.k2GLojuO031477@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv31190/FC-5-press-release
Added Files:
fc5-press-release-it_IT.xml
Log Message:
Translation of press-release-en_US by Francesco Ugolini
--- NEW FILE fc5-press-release-it_IT.xml ---
Fedora Project
Presentazione di Fedora Core 5
Il Progetto Fedora ?? lieto di annunciare il rilascio di Fedora Core 5. Nuove applicazioni desktop, sicurezza avanzata, strumenti di localizzazione migliorati, sviluppata l'installazione e la gestione del software ed una forte integrazione con Java fa si che Fedora Core 5 sia la pi?? innovativa distribuzione di Linux di sempre.
Per una lista pi?? dettagliata dei cambiamenti e informazioni interessanti per gli utenti, amministrator e sviluppatori, riferirsi alle ultime note di rilascio:
Ottenere Fedora Core 5Scaricare l'immagine ISO.
Ora gli utenti possono scaricare le immagini ISO dei DVD o dei CD-ROM dell'installazione dal sito di Fedora.
http://fedoraproject.org/wiki/Distribution/DownloadVenditori Online
Noi sappiamo che molte persone non hanno una sufficiente banda per scaricare un sistema operativo intero. Questa ?? una delle ragioni per ci le Trademark Guideline sono state scritte per permettere a terzi di vendere supporti fisici che contengano Fedora core, fermo restando che essi aderiscono alle Trademark Guideline.
http://fedoraproject.org/wiki/Distribution/OnlineVendorshttp://fedoraproject.org/wiki/Legal/TrademarkGuidelinesFedora Community Free Media
La Fedora Community Free Media, un'iniziativa volontaria sotto il programma degli ambasciatori di Fedora, mira a sistribuire i supporti (DVD) di Fedora Core gratuitamente agli individui. Gli ambasciatori o i contributori locali di Fedora sono invitati a partecipare.
http://fedoraproject.org/wiki/FreeMediahttp://fedoraproject.org/wiki/AmbassadorsCosa c'?? di nuovo in Fedora Core 5Guarda Fedora Core 5 ora
Fedora Core 5 ha un nuovo look ed un approccio emozionanti. I menu e l'interfaccia utente sono stati elaborati con attenzione dai progettisti di interazione e dalla squadra desktop. Fai un giro su:
http://fedoraproject.org/wiki/Tours/FedoraCore5Desktop
Fedora Core 5 possiede alcune nuove grandi applicazioni desktop potenziate da Mono.
Tomboy ?? uno strumento per prendere note, semplice e pratico, che ha gi?? cambiato il modo di lavorare di molti utenti fedora e sviluppatori.
http://www.beatniksoftware.com/tomboy/
Grazie a F-Spot ?? possibile gestire fotografie digitali nel pi?? semplice modo di sempre.
http://f-spot.org/Main_Page
Se state cercando qualcosa nei log delle vostre chat, nelle vostre email o in una pagina web che avete visitato giorni fa, Beagle ti aiuta a cercare questi.
http://beaglewiki.org/Main_Page
Inoltre siamo soddisfatti di introdurre il supporto di Accellerated GLX (AIGLX) in Fedora Core 5. Sviluppata in collaborazione con la comunit?? Upstream Xorg, AIGLX fornisce le base per GLX-accelerated su un desktop standard. Questo significa effetti eye-catching; inoltre fornisce una piattaforma per creare un desktop con alte performance, efficente e elegante.
http://fedoraproject.org/wiki/RenderingProject
La gestione energia ?? stata sviluppata grazie a GNOME Power Manager, inclusa in questa release. Il pacchetto degli screensaver Gnome ?? incluso con un nuovo screensaver di Fedora in accompagnamento.
http://www.gnome.org/projects/gnome-power-manager/http://live.gnome.org/GnomeScreensaver/
L'integrazione, il testing e lo sviluppo sono stati fatti per verificare che le modalit?? di sospensione e ibernazione lavorino con il maggior numero di combinazione hardware che la counit?? Fedora potrebbe utilizzare.
Non dimentichiamo i nostri utenti Apple e abbiamo incluso il supporto alla pi?? vasta scheda wirless Boardcom 43xx nel kernel Fedora Core 5, che ?? basato sul kernel 2.6.16.
http://bcm43xx.berlios.de/http://wiki.kernelnewbies.org/LinuxChanges
Fedora Core 5, inoltre, contiene nuove versioni aggiornate dei vecchi favoriti. L'ultima versione della serie Firefox 1.5, che offre una velocit?? migliorata, stabilit?? , sicurezza, supporto, un nuovo database frontend, un wizard di configurazione email ed una migliore capacit?? di esportare i file PDF. Le ultime versione di GNOME 2.14 e KDE 3.5 offrono molte nuove caratteristiche e miglioramenti al desktop Fedora.
http://www.mozilla.com/firefox/releases/1.5.htmlhttp://www.openoffice.org/product/index.htmlhttp://www.gnome.org/start/2.14/notes/C/http://kde.org/announcements/announce-3.5.php
In conclusione, le caratteristiche desktop di Fedora Core 5 offrono nuovi svuluppi nelle applicazioni multimediali, contruite intorno al codec gratuito Xiph.org ed il genio dietro alla famiglia dei code Ogg ?? ora un membro del team Fedora Core. Noi speriamo che Fedora e Xiph.org formino un' associazione forte e durevole per un ulteriore sviluppo nei formati free media.
http://www.xiph.orgSoftware Installation and Management
Anaconda, l' installer di Fedora Core, ?? stato completamente riscritto per presentare un'interfaccia pi?? efficente che abbini il nuovo look e aspetto di Fedora Core 5.
Fedora Core 5 inoltre ha importanti sviluppi nella gestione del software con l' introduzione di Pirut, un' interfaccia grafica che sostituisce il system-config-packages- Pirut aiuto a gestire un largo numero di pacchetti software disponibili in Fedora Core e nei repository Extra. Il software di aggiornamento pacchetti, Pup, aiuto gli utenti a stare al passo con i rapidi miglioramenti di Fedora.
Per la prima volta, tutto gli strumenti di Fedora Core per l' instalazione software e la gestione condividono la stessa slida base: il programma di utilit?? Yum per la gestione dei pacchetti. Questa integrazione stretta condurr?? a miglioramenti drastici nella gestione software nelle versioni successive di Fedora.
Xen Virtualization
Xen, il progetto open source principale di virtualizzazione, ?? incluso in Fedora Core 5. La nostra versione di Xen ?? basata sull' ultimo ramo di sviluppo di Xen 3,0 , con supporto per l'hardware X86 a 32 e 64 bit. Inoltre ?? stato incluso dagli sviluppatori di Fedora lo script di installazione Xen guest, che permette agli utenti di installare meacchine virtuali.
Gli sviluppi di Xen in Fedora Core 5 rappresentano un fondamentale passo per il futuro della virtualizzazione di Linux. Fedora ha allargato il nostra team di virtualizzazione con Chris Wright, uno dei nostri manutentori del ramo stabile del kernel 2.6 e Juan Quintela per il wizard della virtualizzazione. Essi fanno pare del grande team di Red Hat, guidato da Brian Stein, responsabile di rendere la virtualizazione ubiquista e senza limiti.
http://fedoraproject.org/wiki/Tools/XenSicurezza
Potete sempre asspertarvi interessanti e eccitanti sviluppi nella sicurezza da Fedora Core e questa versione non vi deluder??. Security Enhanced Linux
(SELinux) ora sta usando la reference policy, che rende pi?? facile creare e mantenere le politiche di sicurezza modulari. L' introduzione di una protezione stak per GCC 4.1 fa si che sia defficile agli ache di fare un exploit buffer overflows, una delle pi?? comuni vulnerabilit?? della sicurezza.
http://fedoraproject.org/wiki/Security/Features?highlight=%28fstack%29
Fedora ha cambiato usando una reference policy per il framework SELinux security. Questo supporta moduli binari, abilitando le politiche di SELinux a muoverso attraverso pacchetti individuali. Gli sviluppatori possono usare questa per spedire gli adattamenti site-specific delle politiche. Fedora Core inoltre supporta il Multi Category Security (MCS) politica di SELinux di default, oltre che applicazioni del tipo (TE), Multi Level Security (MLS) e le politiche per il Role Base Access Control (RBAC). Questi sviluppi nella sicurezza continuano a fare di Fedora Core uno dei sistemi operativi general-use pi?? sicuri del mondo. Cerca altri fatti su:
http://fedoraproject.org/wiki/Securityhttp://serefpolicy.sourceforge.net/
Il Linux Unified Key Support (LUKS) fornisce il supporto di crittografia del disco rigifo di Fedora Core 5; David Zeuthen di Red Hat, lo svilupparote e manutentore di HAL, ha lavorato sul integrazione di LUKS con HAL e GNOME, finenfo appena in tempo per il nuovo rilascio di Fedora Core. La crittografia del disco rigido fornisce una delle souzione fisiche migliori e la protezione dei vostri dati se il vostro disco rgido cade nelle mani errate.
http://fedoraproject.org/wiki/Software/LUKSInternazionalizzazione e localizzazione
Coloro che contribuiscono a fedora usano differenti linguaggi oltre a C, C++, Python, Java e cos?? via. Siamo inoltre esseri umani che parlano le lingue del mondo e desideriamo sostenere Fedora quanto pi?? c'?? possibile.
In Fedora Core 5 siamo venuti pi?? vicino a questo obiettivo adottando SCIM, al posto di IIIMF, come metodo di input della scelta per l'internazionalizzazione. Questo e altri sviluppi permettono che Fedora comunichi in modo migliore di prima con i suoi numerosi utenti.
http://www.scim-im.org/Java
This release of Fedora Core represents another big step down the free Java
path.
Attraverso l'introduzione dello stack completamente libero java-gcj-compat, che da dunzionare il nativo e bytecode Java, Fedora pu?? ora compliare e far funzionare il software scritto in Java senza avere bisogno delle esecuzioni riservare e chiuse della Java machine.
L'eccellente team di sviluppo di Fedora Java di Red Hat e la comunit?? di hacker hanno costruito molto pacchetti Java-based o Java-using utilizzando java-gcj-compat. Questi pacchetti, che includono OpenOffice.org, Eclipse, Apache Tomcat e Jakarta ora sono complilati e lavorano al 100% su stack di software gratuiti e aperti.
Abbiamo incluso un set completo di pacchetti e di utlit?? di sviluppo in Fedora Core 5 per le tecnologie Java. Fedora Extras, inoltre, ha molte applicazioni Java: il popolare software di utilit?? BitTorrent Azureus, RSSowl e altri, tutti alimentati da gcj-Java-compat.
http://fedoraproject.org/wiki/Javahttp://www.gnu.org/philosophy/java-trap.htmlSotto il cappuccio
Le reposity software per il progetto Fedora Legacy del progetto di mantenimento sono disponibili per questa versione. Disabilitati per default, questa repository pu?? essere riabilitata cos?? che gli utenti possano continuare con le patch della comunit?? dopo che Fedora Core 5 lascer?? la sua finestra ufficiale di manutenzione.
Fedora Core 5 include l' utimo rilascio di Apache HTTP WebServer 2.2, MySQL 5.0 e PostgreSQL 8.1 coon varie implementazioni.
http://httpd.apache.org/docs/2.2/new_features_2_2.htmlhttp://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.htmlhttp://www.postgresql.org/docs/whatsnew
X.Org ?? stato completamente modularizzato e Fedora Core include, in questo rilascio, l' ultime versione X.Org X11R7.0. La nuova architettura modulare de R7.0 abilita un facile aggiornamento dei driver e un semplificato sviluppo, aprendo la strada per un rapido sviluppo nella grafica Linux.
Gstreamer, il framework multimediale del desktop gratuito, ha visto maggiori sviluppi con la versione 0.10 e noi abbiamo assicuarto che le applicazioni come Totem possano usufruire tutti i vantaggi di questo.
http://gstreamer.freedesktop.org/
Noi abbiamo inserito l'ultima versione di GNU Complier Collection, GCC 4.1, che offre miglioramenti della sicurezza e delle performance. Noi abbiamo usato GCC 4.1 per complilare oltre 6,000 pacchetti nei repository di Fedora Core e Fedora Extras . GCJ, una parte critica del nostro sviluppo gratuito di Java, ?? incluso. C'??, inoltre, un' implementazione del OpenMP parallel programming standard (http://www.openmp.org/) per C, C++ e Fortran. Usa l'interruttore del compilatore -fopenmp per permetterlo.
Altri miglioramenti sono descritti su:
http://gcc.gnu.org/gcc-4.1/changes.html.
Fedora Core 5, inoltre, offre anteprime per il SystemTap e Frysk, tagliando gli stumenti di analisi di esecuzione edge che abilitano gli sviluppatori a risovere i problemi di performance ad un livello mai possibile prima di ora.
http://fedoraproject.org/wiki/SystemTaphttp://fedoraproject.org/wiki/FryskIl futuro di Fedora
Coloro che contribuiscono al progetto Fedora stanno gi?? lavorando per la nuova versione di Fedora Core, che avr?? sviluppi in Xen e una nuova integrazione dal progetto Fedora Rendering al progetto "Un computer per bambino" (ovvero laptop da 100 dollari). Il lavoro cosmopolita di Linux, inoltre, sta progredendo costantemente. Stiamo lavorando sulla possibilit?? di supportare i Fedora Extras e altri repository personalizzati di software durante l'installazione. Come di consueto, il lavoro continua su nuovi rilasci dei migliori e pi?? robusti software gratuiti e open source. Guarda la nostra roadmap:
http://fedoraproject.org/wiki/RoadMaphttp://fedoraproject.org/wiki/OLPChttp://fedoraproject.org/wiki/StatelessLinux
From fedora-docs-commits at redhat.com Fri Mar 17 00:45:14 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 16 Mar 2006 19:45:14 -0500
Subject: press-release fdp-pr.xsl,1.10,1.11
Message-ID: <200603170045.k2H0jEiR014055@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14027
Modified Files:
fdp-pr.xsl
Log Message:
Solved: text overlap problem in header (FEDORA PROJECT / PRESS RELEASE)
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.xsl,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- fdp-pr.xsl 16 Mar 2006 20:53:15 -0000 1.10
+++ fdp-pr.xsl 17 Mar 2006 00:45:06 -0000 1.11
@@ -35,21 +35,35 @@
-
-
+
+
-
+
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
From fedora-docs-commits at redhat.com Fri Mar 17 01:19:01 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Thu, 16 Mar 2006 20:19:01 -0500
Subject: marketing-content/FC-5-press-release fc5-press-release-it_IT.xml,
1.1, NONE
Message-ID: <200603170119.k2H1J1RB016323@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16302
Removed Files:
fc5-press-release-it_IT.xml
Log Message:
removed unnecessary xml file
--- fc5-press-release-it_IT.xml DELETED ---
From fedora-docs-commits at redhat.com Fri Mar 17 01:21:44 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Thu, 16 Mar 2006 20:21:44 -0500
Subject: marketing-content/FC-5-press-release it.po,NONE,1.1
Message-ID: <200603170121.k2H1LiPH016410@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv16390
Added Files:
it.po
Log Message:
it.po derived from xml file translated by Francesco Ugolini, and revised by me
--- NEW FILE it.po ---
# translation of it.po to Italiano
# Francesco Tombolini , 2006.
msgid ""
msgstr ""
"Project-Id-Version: it\n"
"POT-Creation-Date: 2006-03-16 22:54+0100\n"
"PO-Revision-Date: 2006-03-17 02:08+0100\n"
"Last-Translator: Francesco Tombolini \n"
"Language-Team: Italiano \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"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: fc5-press-release-en_US.xml:9(header)
msgid "Presenting Fedora Core 5"
msgstr "Presentazione di Fedora Core 5"
#: fc5-press-release-en_US.xml:10(para)
msgid "The Fedora Project is pleased to announce the release of Fedora Core 5. New desktop applications, advances in security, better localization tools, improved software installation and management facilities, and strong Java integration help to make Fedora Core 5 the most innovative Linux distribution ever."
msgstr "Il Progetto Fedora ?? lieto di annunciare il rilascio di Fedora Core 5. Nuove applicazioni desktop, sicurezza avanzata, strumenti di localizzazione migliorati, sviluppata l'installazione e la gestione del software ed una forte integrazione con Java fa si che Fedora Core 5 sia la pi?? innovativa distribuzione di Linux di sempre."
#: fc5-press-release-en_US.xml:17(para)
msgid "For a more complete list of changes and interesting information for users, administrators, and developers, refer to the latest release notes:"
msgstr "Per una lista pi?? dettagliata dei cambiamenti e informazioni interessanti per gli utenti, amministrator e sviluppatori, riferirsi alle ultime note di rilascio:"
#: fc5-press-release-en_US.xml:25(header)
msgid "Getting Fedora Core 5"
msgstr "Ottenere Fedora Core 5"
#: fc5-press-release-en_US.xml:26(header)
msgid "Download ISO Images"
msgstr "Scaricare le immagini ISO"
#: fc5-press-release-en_US.xml:27(para)
msgid "Users can download the ISO images of the installation DVD or CD-ROMs now from the Fedora Website."
msgstr "Ora gli utenti possono scaricare le immagini ISO dei DVD o dei CD-ROM dell'installazione dal sito di Fedora."
#: fc5-press-release-en_US.xml:34(header)
msgid "Online Vendors"
msgstr "Venditori Online"
#: fc5-press-release-en_US.xml:35(para)
msgid "We recognize that many people do not have sufficient bandwidth to download an entire operating system. This is one of the reasons that the Trademark Guidelines are written to allow third parties to sell physical media containing Fedora Core, as long as they comply with the guidelines."
msgstr "Noi sappiamo che molte persone non hanno una sufficiente banda per scaricare un sistema operativo intero. Questa ?? una delle ragioni per cui le Trademark Guideline sono state scritte per permettere a terzi di vendere supporti fisici che contengano Fedora core, fermo restando che essi aderiscono alle Trademark Guideline."
#: fc5-press-release-en_US.xml:47(header)
msgid "Fedora Community Free Media"
msgstr "Fedora Community Free Media"
#: fc5-press-release-en_US.xml:48(para)
msgid "Fedora Community Free Media, a volunteer initiative under the Fedora Ambassadors Program, aims to distribute Fedora Core media (DVDs) for free to individuals. Local Fedora Ambassadors or Contributors are invited to participate."
msgstr "La Fedora Community Free Media, un'iniziativa volontaria sotto il programma degli ambasciatori di Fedora, mira a distribuire i supporti (DVD) di Fedora Core gratuitamente agli individui. Gli ambasciatori o i contributori locali di Fedora sono invitati a partecipare."
#: fc5-press-release-en_US.xml:60(header)
msgid "What's New In Fedora Core 5"
msgstr "Cosa c'?? di nuovo in Fedora Core 5"
#: fc5-press-release-en_US.xml:62(header)
msgid "See Fedora Core 5 Now"
msgstr "Guarda Fedora Core 5 ora"
#: fc5-press-release-en_US.xml:63(para)
msgid "Fedora Core 5 has an exciting new look and feel. The menus and user interface have been carefully crafted by the interaction designers and desktop team. Take a tour at:"
msgstr "Fedora Core 5 ha un nuovo look ed un approccio emozionanti. I menu e l'interfaccia utente sono stati elaborati con attenzione dai progettisti di interazione e dalla squadra desktop. Fai un giro su:"
#: fc5-press-release-en_US.xml:72(header)
msgid "Desktop"
msgstr "Desktop"
#: fc5-press-release-en_US.xml:73(para)
msgid "Fedora Core 5 features some great new desktop applications powered by Mono."
msgstr "Fedora Core 5 possiede alcune nuove grandi applicazioni desktop potenziate da Mono."
#: fc5-press-release-en_US.xml:76(para)
msgid "Tomboy is a note-taking tool; simple and handy, it has already changed the way that some Fedora users and developers work."
msgstr "Tomboy ?? uno strumento per prendere note, semplice e pratico, che ha gi?? cambiato il modo di lavorare di molti utenti fedora e sviluppatori."
#: fc5-press-release-en_US.xml:83(para)
msgid "Thanks to F-Spot, managing digital photographs is easier than ever."
msgstr "Grazie a F-Spot ?? possibile gestire fotografie digitali nel pi?? semplice modo di sempre."
#: fc5-press-release-en_US.xml:89(para)
msgid "If you are looking for something in a chat log, an email, or a web page you visited days ago, Beagle helps you find it."
msgstr "Se state cercando qualcosa nei log delle vostre chat, nelle vostre email o in una pagina web che avete visitato giorni fa, Beagle ti aiuta a cercarlo."
#: fc5-press-release-en_US.xml:96(para)
msgid "We are also pleased to introduce Accelerated Indirect GLX (AIGLX) support in Fedora Core 5. Developed in partnership with the upstream Xorg community, AIGLX provides the foundation for GLX-accelerated effects on a standard desktop. While this can mean eye-catching effects, it also provides a platform for creating a high-performance, efficient, and elegant desktop."
msgstr "Inoltre siamo lieti di presentare il supporto di Accellerated Indirect GLX (AIGLX) in Fedora Core 5. Sviluppata in collaborazione con la principale comunit?? Xorg, AIGLX fornisce il fondamento per effetti accelerati GLX su un comune desktop. Mentre questo significa effetti visivi accattivanti questo fornisce anche una piattaforma per creare un desktop ad alte prestazioni, efficente ed elegante."
#: fc5-press-release-en_US.xml:106(para)
msgid "Power management has been improved thanks to GNOME Power Manager, included in this release. The GNOME screensaver package is included, with a new Fedora screensaver to accompany it."
msgstr "La gestione dell'energia ?? stata migliorata grazie a GNOME Power Manager, inclusa in questa release. Il pacchetto GNOME screensaver ?? incluso con un nuovo screensaver di Fedora in accompagnamento."
#: fc5-press-release-en_US.xml:117(para)
msgid "Integration, testing, and development was done to verify that suspend and hibernation features work with the largest number of hardware combinations that the Fedora community could get its hands on."
msgstr "L'integrazione, il testing e lo sviluppo sono stati fatti per verificare che le modalit?? di sospensione e ibernazione funzionino con il maggior numero di combinazioni hardware che la counit?? Fedora possa utilizzare."
#: fc5-press-release-en_US.xml:122(para)
msgid "We didn't forget our Apple hardware users and included support for the widely-used Broadcom 43xx wireless chipsets in the Fedora Core 5 kernel, which is based on the 2.6.16 kernel release."
msgstr "Non dimentichiamo i nostri utenti di hardware Apple e l'inclusione del supporto per i largamente usati chipsets wireless Broadcom 43xx nel kernel di Fedora Core 5, che ?? basato sulla versione del kernel 2.6.16."
#: fc5-press-release-en_US.xml:133(para)
msgid "Fedora Core 5 also features updated versions of old favorites. The latest in the Firefox 1.5 series offers improvements in speed, stability, security, and accessibility. The latest OpenOffice.org 2.0.2 introduces OpenDocument support, a new enhanced database frontend, a mail merge wizard, and better PDF export capability. The latest versions of both GNOME 2.14 and KDE 3.5 bring a many new features and improvements to the Fedora desktop."
msgstr "Fedora Core 5, inoltre, contiene nuove versioni aggiornate di vecchi favoriti. L'ultima versione nella serie Firefox 1.5 offre miglioramenti in velocit??, stabilit??, sicurezza, ed accessibilit??. L'ultimo OpenOffice.org 2.0.2 introduce il supporto dell'OpenDocument, un nuovo avanzato database frontend, un wizard per il mail merge ed una migliore capacit?? di esportare i file PDF. Le ultime versioni di GNOME 2.14 e KDE 3.5 portano molte nuove caratteristiche e miglioramenti al desktop Fedora."
#: fc5-press-release-en_US.xml:154(para)
msgid "Finally, the Fedora Core 5 desktop features new advances in multimedia applications built around the free Xiph.org codecs. Fedora is proud to say that Chris Montgomery, the founder of Xiph.org and the genius behind the Ogg family of codecs, is now a member of the Fedora Core team. We hope that Fedora and Xiph.org form a strong and lasting partnership to further the development of free media formats."
msgstr "In fine, le caratteristiche desktop di Fedora Core 5 offrono nuovi sviluppi nelle applicazioni multimediali, costruite intorno ai codecs gratuiti Xiph.org. Fedora ?? lieta di comunicarvi che Chris Montgomery, il fondatore di Xiph.org ed il genio dietro alla famiglia dei codec Ogg, ?? ora un membro del team Fedora Core. Speriamo che Fedora e Xiph.org formino un'associazione forte e durevole per un ulteriore sviluppo dei formati multimediali liberi."
#: fc5-press-release-en_US.xml:166(header)
msgid "Software Installation and Management"
msgstr "Installazione e gestione del software"
#: fc5-press-release-en_US.xml:167(para)
msgid "Anaconda, the Fedora Core installer, has been completely rewritten to present a more streamlined interface that matches the new look and feel of Fedora Core 5."
msgstr "Anaconda, l'installer di Fedora Core, ?? stato completamente riscritto per presentare un'interfaccia pi?? efficente che abbini il nuovo look and feel di Fedora Core 5."
#: fc5-press-release-en_US.xml:172(para)
msgid "Fedora Core 5 also brings major advancements in software management with the introduction of Pirut, a graphical interface to replace system-config-packages. Pirut helps manage the large number of software packages available in Fedora Core and Extras repositories. The software package updater, Pup, helps users keep pace with Fedora's rapid improvements."
msgstr "Fedora Core 5 porta anche importanti sviluppi nella gestione del software con l'introduzione di Pirut, un' interfaccia grafica che sostituisce system-config-packages. Pirut aiuta a gestire il gran numero di pacchetti software disponibili nei repositori Fedora Core ed Extras. Il software di aggiornamento pacchetti Pup, aiuta gli utenti a stare al passo con i rapidi miglioramenti di Fedora."
#: fc5-press-release-en_US.xml:180(para)
msgid "For the first time, all of Fedora Core's tools for software installation and management share the same strong foundation: the package management utility Yum. This tight integration will lead to dramatic improvements in software management in future Fedora releases."
msgstr "Per la prima volta, tutti gli strumenti di Fedora Core per la gestione e l'installazione del software condividono la stessa solida base: l'utilit?? di gestione pacchetti Yum. Questa stretta integrazione condurr?? a miglioramenti drastici nella gestione software nelle future versioni di Fedora."
#: fc5-press-release-en_US.xml:187(header)
msgid "Xen Virtualization"
msgstr "Virtualizzazione Xen"
#: fc5-press-release-en_US.xml:188(para)
msgid "Xen, the leading open source virtualization project, is included in Fedora Core 5. Our version of Xen is based on the latest Xen 3.0 development branch, with support for both 32-bit and 64-bit x86 hardware. Also included is the Xen guest install script from Fedora developers, which allows users to set up virtual machines."
msgstr "Xen, il principale progetto open source di virtualizzazione, ?? incluso in Fedora Core 5. La nostra versione di Xen ?? basata sull'ultimo ramo di sviluppo di Xen 3.0, con supporto per l'hardware X86 sia a 32-bit che a 64-bit. Inoltre ?? stato incluso dagli sviluppatori di Fedora, lo script di installazione Xen guest, che permette agli utenti di installare macchine virtuali."
#: fc5-press-release-en_US.xml:195(para)
msgid "Xen's advances in Fedora Core 5 represent a critical next step in the future of virtualization on Linux. Fedora has expanded our virtualization team with Chris Wright, one of the maintainers of the stable branch of 2.6 kernel releases, and Juan Quintela, as virtualization wizards. They are part of a large Red Hat team, headed by Brian Stein, responsible for making virtualization ubiquitous and seamless in Fedora."
msgstr "Gli sviluppi di Xen in Fedora Core 5 rappresentano un fondamentale passo per il futuro della virtualizzazione di Linux. Fedora ha allargato il nostro team di virtualizzazione con Chris Wright, uno dei manutentori del ramo stabile del kernel 2.6 e Juan Quintela per il wizard della virtualizzazione. Essi fanno pare del grande team di Red Hat, guidato da Brian Stein, responsabile di rendere la virtualizazione ubiquista e senza soluzione di continuit?? in Fedora."
#: fc5-press-release-en_US.xml:207(header)
msgid "Security"
msgstr "Sicurezza"
#: fc5-press-release-en_US.xml:208(para)
msgid "You can always expect interesting and exciting advancements in security from Fedora Core, and this release does not disappoint. Security Enhanced Linux (SELinux) is now using the reference policy, which makes it easier to create and maintain modular security policies. The introduction of a stack protector to GCC 4.1 makes it harder than ever for hackers to exploit buffer overflows, one of the most common security vulnerabilities."
msgstr "Potete sempre aspettarvi interessanti ed eccitanti sviluppi nella sicurezza da Fedora Core e questa versione non vi deluder??. Security Enhanced Linux (SELinux) sta ora usando la reference policy, che rende pi?? facile creare e mantenere politiche di sicurezza modulari. L'introduzione di una protezione stack per GCC 4.1 fa si che sia difficile pi?? che mai per gli hackers fare exploit buffer overflows, una delle pi?? comuni vulnerabilit?? di sicurezza."
#: fc5-press-release-en_US.xml:220(para)
msgid "Fedora has switched to using the reference policy for the SELinux security framework. This supports binary modules, allowing SELinux policies to move into individual packages. Developers can use this to ship site-specific policy customizations. Fedora Core also supports the Multi Category Security (MCS) SELinux policy by default, in addition to Type Enforcement (TE), Muti Level Security (MLS), and Role Base Access Control (RBAC) security policies. These gains in security continue to make Fedora Core one of the most secure general-use operating systems in the world. Find more facts at:"
msgstr "Fedora ?? passata all'uso della reference policy per il framework di sicurezza SELinux. Questa supporta moduli binari, permettendo alle policy di SELinux di muoversi verso pacchetti individuali. Gli sviluppatori possono usarla per distribuire adattamenti delle policy specifiche per il sito. Fedora Core inoltre supporta la policy di SELinux Multi Category Security (MCS) per impostazione predefinita, oltre alle Type Enforcemen (TE), Multi Level Security (MLS) e le policy di sicurezza Role Base Access Control (RBAC). Questi sviluppi nella sicurezza continuano a fare di Fedora Core uno dei sistemi operativi d'uso generale pi?? sicuri del mondo. Cerca altri fatti su:"
#: fc5-press-release-en_US.xml:238(para)
msgid "Linux Unified Key Support (LUKS) provides hard disk encryption support in Fedora Core 5; David Zeuthen of Red Hat, the HAL developer and maintainer, worked on the LUKS integration with HAL and GNOME, finishing just in time for the new Fedora Core release. Hard disk encryption provides one of the best physical security solutions -- protection of your data if your hard disk falls into the wrong hands."
msgstr "Il Linux Unified Key Support (LUKS) fornisce il supporto di crittografia del disco rigido di Fedora Core 5; David Zeuthen di Red Hat, lo svilupparote e manutentore di HAL, ha lavorato sul integrazione di LUKS con HAL e GNOME, finendolo appena in tempo per il nuovo rilascio di Fedora Core. La crittografia del disco rigido fornisce una delle migliori soluzioni -- protezioni dei vostri dati se il vostro disco rigido cade nelle mani sbagliate."
#: fc5-press-release-en_US.xml:251(header)
msgid "Internationalization and Localization"
msgstr "Internazionalizzazione e localizzazione"
#: fc5-press-release-en_US.xml:252(para)
msgid "Fedora contributors speak many different languages besides C, C++, Python, Java, and so on. We are also humans who speak the world's languages, and we want Fedora to support as many as possible."
msgstr "Coloro che contribuiscono a Fedora usano differenti linguaggi oltre a C, C++, Python, Java e cos?? via. Siamo anche esseri umani che parlano le lingue del mondo e vogliamo che Fedora ne supporti quante pi?? possibile."
#: fc5-press-release-en_US.xml:257(para)
msgid "In Fedora Core 5, we have come closer to that goal by adopting SCIM, in place of IIIMF, as the input method of choice for internationalization. This and other advances allow Fedora to communicate with its many users better than ever before."
msgstr "In Fedora Core 5, siamo arrivati pi?? vicino a questo obiettivo adottando SCIM, al posto di IIIMF, come metodo di input della scelta per l'internazionalizzazione. Questo ed altri sviluppi permettono a Fedora di comunicare meglio di prima, con i suoi numerosi utenti."
#: fc5-press-release-en_US.xml:267(header)
msgid "Java"
msgstr "Java"
#: fc5-press-release-en_US.xml:268(para)
msgid "This release of Fedora Core represents another big step down the free Java path."
msgstr "Questa versione di Fedora Core rappresenta un altro grande passo nel percorso di liberalizzazione di Java."
#: fc5-press-release-en_US.xml:272(para)
msgid "Through the introduction of the completely free software stack java-gcj-compat that runs native and bytecode Java, Fedora can now compile and run software written in Java without relying upon proprietary and closed Java machine implementations."
msgstr "Attraverso l'introduzione dello stack software completamente libero java-gcj-compat, che esegue Java nativo e bytecode, Fedora pu?? ora compilare ed eseguire il software scritto in Java senza avere bisogno di implementazioni di macchine Java chiuse e proprietarie."
#: fc5-press-release-en_US.xml:278(para)
msgid "The excellent Fedora Java development team of Red Hat and community hackers have built many popular Java-based or Java-using packages utilizing java-gcj-compat for this release. These packages, which include OpenOffice.org, Eclipse, Apache Tomcat, and Jakarta, are now compiled and run on a 100% free and open software stack."
msgstr "L'eccellente team di sviluppo di Fedora Java di Red Hat e gli hackers della comunit?? hanno costruito molti pacchetti basati su Java o che usano Java utilizzando java-gcj-compat per questa versione. Questi pacchetti, che includono OpenOffice.org, Eclipse, Apache Tomcat e Jakarta ora sono complilati ed eseguiti su uno stack software gratuito ed aperto al 100%."
#: fc5-press-release-en_US.xml:285(para)
msgid "We included a complete set of packages and development goodies in Fedora Core 5 for Java technologies. Fedora Extras also has many Java applications: the popular BitTorrent utility Azureus, RSSowl, and others, all powered by gcj-java-compat."
msgstr "Abbiamo incluso un set completo di pacchetti ed utlit?? di sviluppo in Fedora Core 5 per le tecnologie Java. Fedora Extras inoltre, ha molte applicazioni Java: il popolare software di utilit?? BitTorrent Azureus, RSSowl ed altri, spinti da gcj-Java-compat."
#: fc5-press-release-en_US.xml:300(header)
msgid "Under the Hood"
msgstr "Sotto il cappuccio"
#: fc5-press-release-en_US.xml:301(para)
msgid "The software repositories for the Fedora Legacy community maintenance project are available in this release. Disabled by default, these repositories can easily be re-enabled so that users can keep up with community patches after Fedora Core 5 leaves its official maintenance window."
msgstr "I repositori software per il progetto di mantenimento della comunit?? Fedora Legacy sono disponibili per questa versione. Disabilitati per impostazione predefinita, questi repositori possono essere facilmente riabilitati affinch?? gli utenti possano continuare con le patch della comunit?? dopo che Fedora Core 5 terminer?? il suo quadro di manutezione ufficiale."
#: fc5-press-release-en_US.xml:308(para)
msgid "Fedora Core 5 includes the latest releases of Apache HTTP Web Server 2.2, MySQL 5.0, and PostgreSQL 8.1 with various enhancements."
msgstr "Fedora Core 5 include l'ultima versione di Apache HTTP WebServer 2.2, MySQL 5.0 e PostgreSQL 8.1 con varie implementazioni."
#: fc5-press-release-en_US.xml:324(para)
msgid "X.Org has been completely modularized and Fedora Core includes the latest X.Org X11R7.0 in this release. The new modular architecture of R7.0 enables easier driver upgrades and simplifies development, opening the way for rapid improvement in Linux graphics."
msgstr "X.Org ?? stato completamente modularizzato e Fedora Core include in questo rilascio, l'ultima versione di X.Org X11R7.0. La nuova architettura modulare di R7.0 abilita un facile aggiornamento dei driver e semplifica lo sviluppo, aprendo la strada a rapidi miglioramenti nella grafica Linux."
#: fc5-press-release-en_US.xml:330(para)
msgid "Gstreamer, the free desktop multimedia framework, has seen major improvements with the 0.10 release, and we made sure that applications such as Totem take full advantage of it."
msgstr "Gstreamer, il framework multimediale gratuito per il desktop, ha visto i maggiori sviluppi con la versione 0.10 e noi abbiamo assicurato che le applicazioni come Totem possano ottenerne pieno vantaggio."
#: fc5-press-release-en_US.xml:339(para)
msgid "We have the latest version of the GNU Compiler Collection, GCC 4.1, which provides security and performance improvements. We used GCC 4.1 to compile over 6,000 packages in the Fedora Core and Fedora Extras software repositories. GCJ, a critical part of our free Java environment, is included. There is also an implementation of the OpenMP parallel programming standard () for C, C++ and Fortran. Use the compiler switch -fopenmp to enable it."
msgstr "Abbiamo l'ultima versione della GNU Complier Collection, GCC 4.1, che offre miglioramenti della sicurezza e delle prestazioni. Abbiamo usato GCC 4.1 per compilare oltre 6,000 pacchetti nei repositori di Fedora Core e Fedora Extras. GCJ, una parte critica del nostro ambiente Java gratuito, ?? incluso. C'??, inoltre, un' implementazione dell'OpenMP parallel programming standard () per C, C++ e Fortran. Usa lo switch del compilatore -fopenmp per abilitarlo."
#: fc5-press-release-en_US.xml:349(para)
msgid "Other improvements are listed at:"
msgstr "Altri miglioramenti sono descritti su:"
#: fc5-press-release-en_US.xml:356(para)
msgid "Fedora Core 5 also offers technology previews for SystemTap and Frysk, cutting edge execution analysis tools that allow developers to troubleshoot performance issues to a degree never before possible."
msgstr "Fedora Core 5, inoltre, offre le anteprime tecnologiche SystemTap e Frysk, gli ultimi strumenti di analisi dell'esecuzione che permettono agli sviluppatori di risovere problemi di prestazioni ad un livello impossibile prima d'ora."
#: fc5-press-release-en_US.xml:370(header)
msgid "The Future of Fedora"
msgstr "Il futuro di Fedora"
#: fc5-press-release-en_US.xml:371(para)
msgid "Fedora contributors are already working toward the next release of Fedora Core, which features advancements in Xen, and new integration work from the Fedora Rendering and One Laptop Per Child (a.k.a. $100 laptop) projects. Stateless Linux work is also progressing steadily. We are working on the ability to support Fedora Extras and other custom software repositories during installation. As usual, work continues on new releases of the best and most robust free and open source software. See our roadmap at:"
msgstr "Coloro che contribuiscono al progetto Fedora stanno gi?? lavorando alla nuova versione di Fedora Core, che avr?? sviluppi in Xen e una nuova integrazione dai progetti Fedora Rendering e Fedora Rendering and One Laptop Per Child (a.k.a. $100 laptop). Anche il lavoro su Stateless Linux sta progredendo costantemente. Stiamo lavorando sulla possibilit?? di supportare i Fedora Extras e altri repositori personalizzati di software durante l'installazione. Come di consueto, il lavoro continua su nuovi rilasci dei migliori e pi?? robusti software gratuiti e open source. Guarda la nostra roadmap:"
#. Put one translator per line, in the form of NAME , YEAR1, YEAR2.
#: fc5-press-release-en_US.xml:0(None)
msgid "translator-credits"
msgstr ""
"Francesco Ugolini "
"Francesco Tombolini "
From fedora-docs-commits at redhat.com Fri Mar 17 02:44:13 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Thu, 16 Mar 2006 21:44:13 -0500
Subject: selinux-faq rpm-info.xml,1.4,1.5
Message-ID: <200603170244.k2H2iDOU018649@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv18631
Modified Files:
rpm-info.xml
Log Message:
Fix rpm-info locales to en_US
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/rpm-info.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-info.xml 16 Mar 2006 19:42:55 -0000 1.4
+++ rpm-info.xml 17 Mar 2006 02:44:05 -0000 1.5
@@ -28,7 +28,7 @@
Paul W. Frields
-
+ Fedora Core 5 SELinux FAQFrequently asked questions about SELinux in Fedora Core 5
@@ -40,15 +40,15 @@
- Make admonition more easily maintainable
+ Make admonition more easily maintainable
- Style and readability editing; some element clarifications
+ Style and readability editing; some element clarifications
- First round of editing.
+ First round of editing.Primo round di editing.
From fedora-docs-commits at redhat.com Fri Mar 17 04:50:31 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Thu, 16 Mar 2006 23:50:31 -0500
Subject: press-release fdp-pr.xsl,1.11,1.12
Message-ID: <200603170450.k2H4oW0s022804@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22786
Modified Files:
fdp-pr.xsl
Log Message:
Simplified header table, but passivetex still cannot parse it.
Indented list items just a little.
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.xsl,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- fdp-pr.xsl 17 Mar 2006 00:45:06 -0000 1.11
+++ fdp-pr.xsl 17 Mar 2006 04:50:23 -0000 1.12
@@ -13,6 +13,8 @@
12pt12pt12pt
+ 0em
+ 2em
@@ -39,24 +41,24 @@
-
+
-
-
+
+
-
+
-
+
@@ -78,7 +80,7 @@
- /
+ /
@@ -108,7 +110,7 @@
-
+
@@ -139,7 +141,7 @@
-
+
From fedora-docs-commits at redhat.com Fri Mar 17 09:15:08 2006
From: fedora-docs-commits at redhat.com (Tommy Reynolds (jtr))
Date: Fri, 17 Mar 2006 04:15:08 -0500
Subject: press-release fdp-pr.dtd,1.5,1.6 fdp-pr.xsl,1.12,1.13
Message-ID: <200603170915.k2H9F8xk002001@cvs-int.fedora.redhat.com>
Author: jtr
Update of /cvs/docs/press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv1814
Modified Files:
fdp-pr.dtd fdp-pr.xsl
Log Message:
Simple, elegant solution that works for everybody, including the
stock xmlto RPM: expand the original header table into a second row.
Put the previously-overlapped text into the rightmost cell of the
second row. This was so simple it work me up about 3:00AM to fix
itself.
Also added new "spare" attribute to the element that is
copied verbatim into the leftmost cell of the second header line. I
called it "spare" because I can't think of what should go there in
the final cut. Ideas accepted.
Index: fdp-pr.dtd
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.dtd,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- fdp-pr.dtd 16 Mar 2006 20:53:15 -0000 1.5
+++ fdp-pr.dtd 17 Mar 2006 09:14:39 -0000 1.6
@@ -4,6 +4,7 @@
+
Index: fdp-pr.xsl
===================================================================
RCS file: /cvs/docs/press-release/fdp-pr.xsl,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- fdp-pr.xsl 17 Mar 2006 04:50:23 -0000 1.12
+++ fdp-pr.xsl 17 Mar 2006 09:14:39 -0000 1.13
@@ -40,6 +40,7 @@
+
@@ -47,25 +48,22 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
From fedora-docs-commits at redhat.com Fri Mar 17 19:33:30 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Fri, 17 Mar 2006 14:33:30 -0500
Subject: install-guide/en_US - New directory
Message-ID: <200603171933.k2HJXUAK030272@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30257/en_US
Log Message:
Directory /cvs/docs/install-guide/en_US added to the repository
From fedora-docs-commits at redhat.com Fri Mar 17 19:40:27 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Fri, 17 Mar 2006 14:40:27 -0500
Subject: install-guide/en_US entities.xml, NONE,
1.1 fedora-install-guide-abouttoinstall.xml, NONE,
1.1 fedora-install-guide-acknowledgements.xml, NONE,
1.1 fedora-install-guide-adminoptions.xml, NONE,
1.1 fedora-install-guide-beginninginstallation.xml, NONE,
1.1 fedora-install-guide-bootloader.xml, NONE,
1.1 fedora-install-guide-diskpartitioning.xml, NONE,
1.1 fedora-install-guide-firstboot.xml, NONE,
1.1 fedora-install-guide-installingpackages.xml, NONE,
1.1 fedora-install-guide-intro.xml, NONE,
1.1 fedora-install-guide-locale.xml, NONE,
1.1 fedora-install-guide-networkconfig.xml, NONE,
1.1 fedora-install-guide-nextsteps.xml, NONE,
1.1 fedora-install-guide-other-instmethods.xml, NONE,
1.1 fedora-install-guide-packageselection.xml, NONE,
1.1 fedora-install-guide-rootpassword.xml, NONE,
1.1 fedora-install-guide-techref.xml, NONE,
1.1 fedora-install-guide-timezone.xml, NONE,
1.1 fedora-install-guide-upgrading.xml, NONE,
1.1 fedora-install-guide.xml, NONE, 1.1
Message-ID: <200603171940.k2HJeRYO030379@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30316/en_US
Added Files:
entities.xml fedora-install-guide-abouttoinstall.xml
fedora-install-guide-acknowledgements.xml
fedora-install-guide-adminoptions.xml
fedora-install-guide-beginninginstallation.xml
fedora-install-guide-bootloader.xml
fedora-install-guide-diskpartitioning.xml
fedora-install-guide-firstboot.xml
fedora-install-guide-installingpackages.xml
fedora-install-guide-intro.xml fedora-install-guide-locale.xml
fedora-install-guide-networkconfig.xml
fedora-install-guide-nextsteps.xml
fedora-install-guide-other-instmethods.xml
fedora-install-guide-packageselection.xml
fedora-install-guide-rootpassword.xml
fedora-install-guide-techref.xml
fedora-install-guide-timezone.xml
fedora-install-guide-upgrading.xml fedora-install-guide.xml
Log Message:
- Migrated to en_US.
--- NEW FILE entities.xml ---
These entities are local to the Fedora Installation Guide.Document base namefedora-install-guideDocument languageenDocument version1.26Document date2006-03-14Document ID string-- ()Local version of Fedora Core5
--- NEW FILE fedora-install-guide-abouttoinstall.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
About to Install
No changes are made to your computer until you click the
Next 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 Back. To abort the installation, turn
off the computer.
Aborting Installation
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.
About to Install Screen
About to install screen.
Click Next to begin the installation.
--- NEW FILE fedora-install-guide-acknowledgements.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Acknowledgements
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.
--- NEW FILE fedora-install-guide-adminoptions.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Boot Options
The &FED; installation system includes a range of functions and
options for administrators. To use boot options, enter
linux option at
the
boot:
prompt.
If you specify more than one option, separate each of the options by
a single space. For example:
linux option1option2option3Rescue Mode
The &FED; installation and rescue discs may
either boot with rescue mode, or load the
installation system. For more information on rescue discs and
rescue mode, refer to .
Configuring the Installation System at the
<prompt>boot:</prompt>
Prompt
You can use the
boot:
prompt to specify a number of settings for the installation
system, including:
language
display resolution
interface type
Installation method
network settings
Specifying the Language
To set the language for both the installation process and the
final system, specify the ISO code for that language with the
option. Use the
option to configure the correct keyboard layout.
For example, the ISO codes el_GR and
gr identify the Greek language and the
Greek keyboard layout:
linux lang=el_GR keymap=grConfiguring the Interface
You may force the installation system to use the lowest possible
screen resolution (640x480) with the
option. To use a specific display resolution, enter
as a boot option. For example, to set the display resolution to
1024x768, enter:
linux resolution=1024x768
To run the installation process in
text interface
mode, enter:
linux text
To enable support for a
serial console
serial console, enter as an additional
option.
Configuring the Installed System
The installed system runs the Setup Agent the first time that
it boots. Use the Setup Agent to configure the display
settings for the new system. Refer to
for more information on
configuring the display with the Setup Agent.
Specifying the Installation Method
Use the option to display additional
menus that enable you to specify the installation method and
network settings. You may also configure the installation method
and network settings at the
boot:
prompt itself.
To specify the installation method from the
boot:
prompt, use the option. Refer to
for the supported
installation methods.
Installation MethodsInstallation MethodOption Format
CD or DVD drive
Hard Drive
HTTP Server
FTP Server
NFS Server
Manually Configuring the Network Settings
By default, the installation system uses DHCP to automatically
obtain the correct network settings. To manually configure the
network settings yourself, either enter them in the
Configure TCP/IP screen, or at the
boot:
prompt. You may specify the address,
, , and
server settings for the installation system
at the prompt. If you specify the network configuration at the
boot:
prompt, these settings are used for the installation process,
and the Configure TCP/IP screen does not
appear.
This example configures the network settings for an installation
system that uses the IP address
192.168.1.10:
linux ip=192.168.1.10 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.2,192.168.1.3Configuring the Installed System
Use the Network Configuration screen to specify the network
settings for the new system. Refer to
for more information on
configuring the network settings for the installed system.
Enabling Remote Access to the Installation System
You may access either graphical or text interfaces for the
installation system from any other system. Access to a text mode
display requires telnet, which is installed by
default on &FED; systems. To remotely access the graphical display
of an installation system, use client software that supports the
VNC (Virtual Network Computing)
VNC (Virtual Network Computing) display protocol. A number of
providers offer VNC clients for Microsoft Windows and Mac OS, as
well as UNIX-based systems.
Installing a VNC Client on &FED;VNC (Virtual Network Computing)installing client
&FED; includes vncviewer, the client
provided by the developers of VNC. To obtain
vncviewer, install the
vnc package.
The installation system supports two methods of establishing a VNC
connection. You may start the installation, and manually login to
the graphical display with a VNC client on another system.
Alternatively, you may configure the installation system to
automatically connect to a VNC client on the network that is
running in listening mode.
Enabling Remote Access with VNCVNC (Virtual Network Computing)enabling
To enable remote graphical access to the installation system,
enter two options at the prompt:
linux vnc vncpassword=qwerty
The option enables the VNC service. The
option sets a password for remote
access. The example shown above sets the password as
qwerty.
VNC Passwords
The VNC password must be at least six characters long.
Specify the language, keyboard layout and network settings for
the installation system with the screens that follow. You may
then access the graphical interface through a VNC client. The
installation system displays the correct connection setting for
the VNC client:
for a shell]]>
You may then login to the installation system with a VNC client.
To run the vncviewer client on &FED;,
choose ApplicationsAccessoriesVNC
Viewer, or type the command
vncviewer in a terminal window. Enter
the server and display number in the VNC
Server dialog. For the example above, the
VNC Server is
computer.mydomain.com:1.
Connecting the Installation System to a VNC Listener
To have the installation system automatically connect to a VNC
client, first start the client in
VNC (Virtual Network Computing)listening mode
listening mode. On &FED; systems, use the
option to run
vncviewer as a listener. In a
terminal window, enter the command:
vncviewer -listenFirewall Reconfiguration Required
By default, vncviewer uses TCP port
5500 when in listening mode. To permit connections to this
port from other systems, choose SystemAdministrationSecurity
Level and Firewall. Select
Other ports, and
Add. Enter 5500
in the Port(s) field, and specify
tcp as the
Protocol.
Once the listening client is active, start the installation
system and set the VNC options at the
boot:
prompt. In addition to and
options, use the
option to specify the name or IP
address of the system that has the listening client. To specify
the TCP port for the listener, add a colon and the port number
to the name of the system.
For example, to connect to a VNC client on the system
desktop.mydomain.com
on the port 5500, enter the following at the
boot:
prompt:
linux vnc vncpassword=qwerty vncconnect=desktop.mydomain.com:5500Enabling Remote Access with Telnet
To enable remote access to a text mode installation, use the
Telnet
option at the
boot:
prompt:
linux text telnet
You may then connect to the installation system with the
telnet utility. The telnet
command requires the name or IP address of the installation
system:
telnet computer.mydomain.comTelnet Access Requires No Password
To ensure the security of the installation process, only use
the option to install systems on
networks with restricted access.
Logging to a Remote System During the Installation
By default, the installation process sends log messages to the
console as they are generated. You may specify that these messages
go to a remote system that runs a
syslogsyslog service.
To configure remote logging, add the
option. Specify the IP address of the logging system, and the UDP
port number of the log service on that system. By default, syslog
services that accept remote messages listen on UDP port 514.
For example, to connect to a syslog service on the system
192.168.1.20, enter
the following at the
boot:
prompt:
linux syslog=192.168.1.20:514Configuring a Log Server
&FED; uses syslogd to provide a syslog
service. The default configuration of syslogd
rejects messages from remote systems.
Only Enable Remote Syslog Access on Secured Networks
The syslogd service includes no security
measures. Crackers may slow or crash systems that permit
access to the logging service, by sending large quantities of
false log messages. In addition, hostile users may intercept
or falsify messages sent to the logging service over the
network.
To configure a &FED; system to accept log messages from other
systems on the network, edit the file
/etc/sysconfig/syslog. You must use
root privileges to
edit the file /etc/sysconfig/syslog. Add
the option to the
SYSLOGD_OPTIONS:
SYSLOGD_OPTIONS="-m 0 -r"
Restart the syslogd service to apply the
change:
su -c '/sbin/service syslog restart'
Enter the root
password when prompted.
Firewall Reconfiguration Required
By default, the syslog service listens on UDP port 514. To
permit connections to this port from other systems, choose
SystemAdministrationSecurity
Level and Firewall. Select
Other ports, and
Add. Enter 514
in the Port(s) field, and specify
udp as the
Protocol.
Automating the Installation with Kickstart
A
KickstartKickstart file specifies settings for an
installation. Once the installation system boots, it can read a
Kickstart file and carry out the installation process without any
further input from a user.
Every Installation Produces a Kickstart File
The &FED; installation process automatically writes a Kickstart
file that contains the settings for the installed system. This
file is always saved as
/root/anaconda-ks.cfg. You may use this
file to repeat the installation with identical settings, or
modify copies to specify settings for other systems.
&FED; includes a graphical application to create and modify
Kickstart files by selecting the options you require. Use the
package system-config-kickstart to install
this utility. To load the &FED; Kickstart editor, choose
ApplicationsSystem
ToolsKickstart.
Kickstart files list installation settings in plain text, with one
option per line. This format lets you modify your Kickstart files
with any text editor, and write scripts or applications that
generate custom Kickstart files for your systems.
To automate the installation process with a Kickstart file, use
the option to specify the name and location of
the file:
linux ks=location/kickstart-file.cfg
You may use Kickstart files that are held on either removable
storage, a hard drive, or a network server. Refer to
for the supported Kickstart
sources.
Kickstart SourcesKickstart SourceOption Format
CD or DVD drive
Hard Drive
Other Device
HTTP Server
FTP Server
NFS Server
To obtain a Kickstart file from a script or application on a Web
server, specify the URL of the application with the
option. If you add the option
, the request also sends HTTP headers to
the Web application. Your application can use these headers to
identify the computer. This line sends a request with headers to
the application
http://server.example.com/kickstart.cgi:
linux ks=http://server.mydomain.com/kickstart.cgi kssendmacEnhancing Hardware Support
By default, &FED; attempts to automatically detect and configure
support for all of the components of your computer. &FED; supports
the majority of hardware in common use with the software
drivers that are included with the
operating system. To support other devices you may supply
additional drivers during the installation process, or at a later
time.
Adding Hardware Support with Driver Disks
The installation system can load drivers from disks, pen drives,
or network servers to configure support for new devices. After
the installation is complete, remove any driver disks and store
them for later use.
Hardware manufacturers may supply
driver disks
driver disks for &FED; with the device, or provide image files
to prepare the disks. To obtain the latest drivers, download the
correct file from the website of the manufacturer.
Driver Disks Supplied as Zipped Files
Driver disk images may be distributed as compressed archives,
or zip files. For identification, the names of zip files
include the extensions .zip, or
.tar.gz. To extract the contents of a
zipped file with a &FED; system, choose ApplicationsSystem
ToolsArchive
Manager.
To format a disk or pen drive with an image file, use the
dd utility. For example, to prepare a
diskette with the image file drivers.img,
enter this command in a terminal window:
dd if=drivers.img of=/dev/fd0
To use a driver disk in the installation process, specify the
option at the
boot:
prompt:
linux dd
When prompted, select Yes to provide a
driver disk. Choose the drive that holds the driver disk from
the list on the Driver Disk Source text
screen.
The installation system can also read drivers from disk images
that are held on network servers. Refer to
for the supported sources of
driver disk image files.
Driver Disk Image SourcesImage SourceOption Format
Select a drive or device
HTTP Server
FTP Server
NFS Server
Overriding Automatic Hardware Detection
For some models of device automatic hardware configuration may
fail, or cause instability. In these cases, you may need to
disable automatic configuration for that type of device, and
take additional steps to manually configure the device after the
installation process is complete.
Check the Release Notes
Refer to the Release Notes for information on known issues
with specific devices.
To override the automatic hardware detection, use one or more of
the following options:
Hardware OptionsCompatibility SettingOption
Disable all hardware detection
Disable graphics, keyboard, and mouse detection
Disable automatic monitor detection (DDC)
Disable mainboard APIC
Disable power management (ACPI)
Disable Direct Memory Access (DMA) for IDE drives
Disable BIOS-assisted RAID
Disable Firewire device detection
Disable parallel port detection
Disable PC Card (PCMCIA) device detection
Disable USB storage device detection
Disable all USB device detection
Force Firewire device detection
Prompt user for ISA device configuration
Additional Screen
The 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.
Using the Maintenance Boot ModesLoading the Memory (RAM) Testing Mode
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.
To boot your computer in
memory testing mode
memory testing mode, enter memtest86 at
the
boot:
prompt. The first test starts immediately. By default,
memtest86 carries out a total of ten tests.
To halt the tests and reboot your computer, enter
Esc at any time.
Booting Your Computer with the Rescue Moderescue mode
You may boot a command-line Linux system from either a
rescue discs
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.
The rescue disc starts the rescue mode system by default. To
load the rescue system with the first installation disc, enter:
linux rescue
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.
By default, rescue mode attaches an existing operating system to
the rescue system under the directory
/mnt/sysimage/.
--- NEW FILE fedora-install-guide-beginninginstallation.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Beginning the Installation
To begin installation of &FC;, boot the computer from the bootable
media. The bootable media provides the necessary programs and files
to start the installation program. Once you start the installation
program, you may be able to install from a completely different
piece of media.
If you boot from the first installation disc of the &FC;
distribution, you may choose a different source for installation.
The default source is the CDs themselves. To change this behavior,
enter linux askmethod at the
boot: prompt. If you boot from
other media, the installation program always
asks you to choose the installation source.
The BIOS (Basic Input/Output System)BIOS (Basic Input/Output System)
on your computer must support the type of boot media you select. The
BIOS controls access to some hardware devices during boot time. Any
computer that meets the minimum recommended specification for &FC;
can boot from a CD or DVD drive with the first disc. USB drives and
flash media are newer technologies, but many computers can use them
as boot media. Some network cards and chipsets include support for
network booting with
PXE (Pre-boot eXecution Environment)PXE. PXE (pronounced "pixie")
allows a computer to load boot files from a network server instead
of directly-connected hardware.
If you are not sure what capabilities your computer has, or how to
configure the BIOS, consult the documentation provided by the
manufacturer. Detailed information on hardware specifications and
configuration is beyond the scope of this document.
Aborting the Installation
To abort the installation process at any time before the
Installing Packages screen, either press
CtrlAltDel
or power off the computer with the power switch. &FED; makes no
changes to your computer until package installation begins.
Booting from CD, DVD, or USB Media
To boot your computer:
Switch on the computer.Insert the first disc into the CD or DVD drive, or attach
the USB media.A boot screen appears, with a boot:
prompt at the bottom.BIOS Boot Order
The BIOS contains settings that control the order of boot
devices. If your PC boots from a device other than the &FC;
boot media, check the BIOS boot configuration.
Boot Screen
&FC; boot screen.
If you hit Enter, the installation runs in
default mode. In the default mode, the installation uses a
graphical interface if possible. If the installation program runs
from the &FC; installation CD or DVD media, in default mode it
uses these media as the installation source. To change the
installation mode, at the boot: prompt, type
linux followed by one or more of the
following options:
To install from a hard drive or network server, add the
directive askmethod.
To use a text interface, add the directive
text.
To retry installation because the installation aborted at an
early stage, add the directive
acpi=off. ACPI is responsible for many
kinds of installation errors. If you turn ACPI off, you may
be able to overcome some of these errors.
Refer to the Release Notes for additional options that may help if
you encounter problems with the installation program. A current
copy of the Release Notes is always available at &FDPDOCS-URL;.
When you issue a command at the boot: prompt, the
first stage of the installation program starts.
Testing CD and DVD MediaMedia Test Screen
Media test screen.
Select OK to test the disc, or select
Skip to proceed with the installation
without testing the disc.
Testing Discs
Test any discs which you have not previously tested. A disc
error during the installation process may force you to restart
the entire procedure.
After you test the first disc, another screen appears and shows
the result:
Media Check Result
Media check result.
Select OK. The following screen appears:
Next Disc Screen
Next disc or continue.
Select Test to test the next disc in the
set, or Continue to proceed with the
installation.
After you test your discs and select
Continue, or if you choose to skip testing,
the main graphical installation program loads.
BIOS Boot Order
The BIOS contains settings that control the order of boot
devices. If your PC boots from a device other than the &FC;
boot media, check the BIOS boot configuration.
Booting from the Network using PXE
To boot with PXE (Pre-boot eXecution Environment) PXE, you need a properly configured server, and a
network interface in your computer that supports PXE.
Configure the computer to boot from the network interface. This
option is in the BIOS, and may be labeled or . Once you
properly configure PXE booting, the computer can boot the &FED;
installation system without any other media.
To boot a computer from a PXE server:
Ensure that the network cable is attached. The link indicator
light on the network socket should be lit, even if the
computer is not switched on.
Switch on the computer.
A menu screen appears. Press the number key that corresponds
to the desired option.
Welcome to Red Hat Network Installer
Red Hat Network Installer screen.
Choose a network installation option to continue.
PXE Troubleshooting
If your PC does not boot from the netboot server, ensure that
the BIOS is configured to boot first from the correct network
interface. Some BIOS systems specify the network interface as a
possible boot device, but do not support the PXE standard.
Refer to your hardware documentation for more information.
--- NEW FILE fedora-install-guide-bootloader.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Boot Loader
A boot loader is a small program that reads
and launches the operating system. &FC; uses the
GRUBconfiguringboot loaderGRUB boot loader by default. If you have
multiple operating systems, the boot loader determines which one to
boot, usually by offering a menu.
You may have a boot loader installed on your system already. An
operating system may install its own preferred boot loader, or you
may have installed a third-party boot loader.If your boot loader
does not recognize Linux partitions, you may not be able to boot
&FC;. Use GRUB as your boot loader to
boot Linux and most other operating systems. Follow the directions
in this chapter to install GRUB.
Installing GRUB
If you install GRUB, it may overwrite your existing boot loader.
The following screen displays boot loader configuration options.
Boot Loader Configuration ScreenBoot loader configuration screenKeeping Your Existing Boot Loader Settings
By default, the installation program installs GRUB in the
master boot record,
master boot record
or MBR, of the device for the root file system.
To change or decline installation of a new boot loader, select the
Change boot loader button. The dialog shown
in allows you to avoid
installing or changing your existing boot loader settings.
Change Boot LoaderChange boot loader dialogBoot Loader Required
Your computer must have GRUB or
another boot loader installed in order to start, unless you
create a separate startup disk to boot from.
You may need to customize the GRUB installation to correctly
support some hardware or system configurations. To specify
compatibility settings, select Configure advanced boot
loader options. This causes a second screen of options
to appear when you choose Next.
explains the features of
the additional screen.
Booting Additional Operating Systems
If you have other operating systems already installed, &FC;
attempts to automatically detect and configure
GRUB to boot them. You may manually
configure any additional operating systems if
GRUB does not detect them. To add,
remove, or change the detected operating system settings, use the
options provided.
Add
Press the Add button to include an
additional operating system in GRUB. &FC; displays the
dialog shown in
.
Select the disk partition which contains the bootable
operating system from the drop-down list and give the entry
a label. GRUB displays this label
in its boot menu.
Edit
To change an entry in the GRUB boot menu, select the entry
and then select Edit.
Delete
To remove an entry from the GRUB boot menu, select the entry
and then select Delete.
Adding Operating Systems to the Boot MenuAdding entries to the GRUB boot menu.Setting a Boot Loader PasswordGRUB reads many file systems without
the help of an operating system. An operator can interrupt the
booting sequence to choose a different operating system to boot,
change boot options, or recover from a system error. However,
these functions may introduce serious security risks in some
environments. You can add a password to
GRUB so that the operator must enter
the password to interrupt the normal boot sequence.
GRUB Passwords Not Required
You may not require a GRUB password
if your system only has trusted operators, or is physically
secured with controlled console access. However, if an untrusted
person can get physical access to your computer's keyboard and
monitor, that person can reboot the system and access
GRUB. A password is helpful in this
case.
To set a boot password, select the Use a boot loader
password check box. The Change
password button will become active. Select
Change password to display the dialog
below. Type the desired password, and then confirm it by typing it
again in the spaces provided.
Entering A Boot PasswordEntering and confirming a boot passwordChoose a Good Password
Choose a password that is easy for you to remember but hard for
others to guess.
Forgotten <application>GRUB</application> PasswordsGRUB stores the password in encrypted
form, so it cannot be read or recovered. If
you forget the boot password, boot the system normally and then
change the password entry in the
/boot/grub/grub.conf file. If you cannot
boot, you may be able to use the "rescue" mode on the first &FC;
installation disc to reset the GRUB password.
If you do need to change the GRUB
password, use the grub-md5-crypt utility. For
information on using this utility, use the command man
grub-md5-crypt in a terminal window to read the manual
pages.
Advanced Boot loader Options
The default boot options are adequate for most situations. The
installation program writes the GRUB
boot loader in the
master boot record
master boot record (MBR), overwriting any
existing boot loader.
You may keep your current boot loader in the MBR
and install GRUB as a secondary boot loader. If you choose this
option, the installer program will write GRUB to the first sector
of the Linux /boot partition.
GRUB as a Secondary Boot Loader
If you install GRUB as a secondary boot loader, you must
reconfigure your primary boot loader whenever you install and
boot from a new kernel. The kernel of an operating system such
as Microsoft Windows does not boot in the same fashion. Most
users therefore use GRUB as the primary boot loader on dual-boot
systems.
You may also need the advanced options if your
BIOS enumerates your drives or RAID arrays
differently than &FC; expects. If necessary, use the
Change Drive Order dialog to set the order
of the devices in &FC; to match your BIOS.
On a few systems, &FC; may not configure the disk drive geometry
for large disks correctly because of limitations within the
BIOS. To work around this problem, mark the
Force LBA32 check box.
The Linux kernel usually auto-detects its environment correctly,
and no additional kernel parameters are needed. However, you may
provide any needed kernel parameter using the advanced boot loader
options.
Kernel Parameters
For a partial list of the kernel command line parameters, type
the following command in a terminal window: man
bootparam. For a comprehensive and authoritative
list, refer to the documentation provided in the kernel sources.
To alter any of these settings, mark the Configure
advanced boot loader options check box. Select
Next and the menu shown in
appears.
Optional Menu
&FC; displays the following advanced boot options menu
only if the advanced configuration check box
described above has been selected.
Advanced Boot OptionsAdvanced boot settings menu
--- NEW FILE fedora-install-guide-diskpartitioning.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Disk Partitioning
&FC; creates and uses several partitions on
the available hard drives. You may customize both the partitions,
and how the drives on your system are managed.
explains drive partitions
in more detail.
Configuring RAID DevicesRAIDhardwareRAID facilities enable a group, or array,
of drives to act as a single device. Configure any RAID functions
provided by the mainboard of your computer, or attached controller
cards, before you begin the installation process. Each active RAID
array appears as one drive within &FED;.
On systems with more than one hard drive you may configure &FC; to
operate several of the drives as a Linux RAID array without
requiring any additional hardware. Linux software RAID arrays are
explained in .
Changing Your Mind
The installation process makes no changes to your system until
package installation begins. You may use
Back to return to previous screens and
change your selections at any time.
Partitioning Options Screenpartitioning options screen
The box on the screen lists the available drives. By default, the
installation process may affect all of the drives on your computer.
To ensure that specific drives are not repartitioned, clear the
check box next to those drives on this list.
The installation process erases any existing Linux partitions on the
selected drives, and replaces them with the default set of
partitions for &FC;. All other types of partitions remain unchanged.
For example, partitions used by Microsoft Windows, and system
recovery partitions created by the computer manufacturer, are both
left intact. You may choose an alternative from the drop-down list:
Remove all partitions on selected drives and create default layout
Avoid this option, unless you wish to erase all of the
existing operating systems and data on the selected drives.
Use free space on selected drives and create default layout
If the selected drives have capacity that has not been
assigned to a partition, this option installs &FC; into the
free space. This ensures that no existing partition is
modified by the installation process.
Create custom layout
You manually specify the partitioning on the selected drives.
The next screen enables you to configure the drives and
partitions for your computer. If you choose this option, &FC;
creates no partitions by default.
Select Review and modify partitioning layout to
customize the set of partitions that &FC; creates, to configure your
system to use drives in RAID arrays, or to modify the boot options
for your computer. If you choose one of the alternative partitioning
options, this is automatically selected.
Choose a partitioning option, and select Next
to proceed.
The Next Screen
The next screen is Network Devices, explained
, unless you select an option to
customize the partition layout. If you choose to either
Create custom layout, or Review and
modify partitioning layout, proceed to
.
General Information on Partitions
A &FC; system has at least three partitions:
A data partition mounted at /boot
A data partition mounted at /
A swap partition
Many systems have more partitions than the minimum listed above.
Choose partitions based on your particular system needs. If you
are not sure how best to configure the partitions for your
computer, accept the default partition layout.
Data partitions have a
mount pointmount point. The mount point indicates the
directory whose contents reside on that partition. A partition
with no mount point is not accessible by users. Data not located
on any other partition resides in the / (or
partitionrootroot) partition.
Root and <filename>/root</filename>
The / (or
partitionroot
root) partition is the top of the directory structure. The
partition/root/root (sometimes pronounced "slash-root")
directory is the home directory of the user account for system
administration.
In the minimum configuration shown above:
All data under the /boot/ directory
resides on the /boot partition. For
example, the file /boot/grub/grub.conf
resides on the /boot partition.
Any file outside of the /boot partition,
such as /etc/passwd, resides on the
/ partition.
Subdirectories may be assigned to partitions as well. Some
administrators create both /usr and
/usr/local partitions. In that case, files
under /usr/local, such as
/usr/local/bin/foo, are on the
/usr/local partition. Any other files in
/usr/, such as
/usr/bin/foo, are in the
/usr partition.
If you create many partitions instead of one large
/ partition, upgrades become easier. Refer to
the description of Disk Druid's
Edit option
for more information.
Leave Excess Capacity Unallocated
Only assign storage capacity to partitions that you require
immediately. You may allocate free space at any time, to meet
needs as they arise.
Partition Types
Every partition has a
partitiontypefile systempartition type, to indicate the format of
the
file systemfile system on that partition. The file
system enables Linux to organize, search, and retrieve files
stored on that partition. Use the
ext3file systemfile systemext3ext3
file system for data partitions that are not part of LVM, unless
you have specific needs that require another type of file
system.
Understanding LVMLVMunderstanding
LVM (Logical Volume Management) partitions provide a number of
advantages over standard partitions. LVM partitions are
formatted as
LVMphysical volumephysical volumes. One or more physical
volumes are combined to form a
LVMvolume groupvolume group. Each volume group's total
storage is then divided into one or more
LVMlogical volumelogical volumes. The logical volumes
function much like standard data partitions. They have a file
system type, such as
ext3, and a mount
point.
An administrator may grow or shrink logical volumes without
destroying data, unlike standard disk partitions. If the
physical volumes in a volume group are on separate drives or
RAID arrays then administrators may also spread a logical volume
across the storage devices.
You may lose data if you shrink a logical volume to a smaller
capacity than the data on the volume requires. For this reason,
create logical volumes to meet your current needs, and leave
excess storage capacity unallocated. You may safely grow logical
volumes to use unallocated space, as your needs dictate.
LVM and the Default Partition Layout
By default, the installation process creates partitions within
LVM volumes.
Creating a <filename>/home</filename> Partition
If you expect that you or other users will store data on the
system, create a separate partition for the
/home directory within an LVM volume. With
a separate /home partition, you may upgrade
or reinstall &FC; without erasing user data files. LVM provides
you with the ability to add more storage capacity for the user
data at a later time.
Disk DruidDisk DruidDisk Druid is an
interactive program for editing disk partitions. Users run it only
within the &FC; installation system. Disk Druid enables you to
configure
RAIDLinux software
Linux software RAID and
LVMLVM to provide more extensible and reliable
data storage.
Disk Setup Screendisk setup screenDisk Druid displays the following
actions in the installation program:
New
Select this option to add a partition
partitionadding
or LVM physical volume to the disk. In the Add
partition dialog, choose a mount point and a
partition type. If you have more than one disk on the
system, choose which disks the partition may inhabit.
Indicate a size in megabytes for the partition.
Illegal Partitionspartitionillegal
The /bin/,
/dev/, /etc/,
/lib/, /proc/,
/root/, and
/sbin/ directories may not be used
for separate partitions in Disk
Druid. These directories reside on the
partitionroot/ (root) partition.
The /boot partition may not reside on
an LVM volume group. Create the /boot
partition before configuring any volume groups.
You may also choose from three options for sizing your
partition:
Fixed size
Use a fixed size as close to your entry as possible.
Fill all space up to
Grow the partition to a maximum size of your choice.
Fill to maximum allowable
size
Grow the partition until it fills the remainder of the
selected disks.
Partition Sizes
The actual partition on the disk may be slightly smaller
or larger than your choice. Disk geometry issues cause
this effect, not an error or bug.
After you enter the details for your partition, select
OK to continue.
Edit
Select this option to edit an existing partition,
partitionediting
LVM volume group, or an LVM physical volume that is not yet
part of a volume group. To change the size of a LVM physical
volume partition, first remove it from any volume groups.
Removing LVM Physical Volumes
If you remove an LVM physical volume from a volume group,
you erase any logical volumes it contains.
Edit a partition to change its size, mount point, or file
system type. Use this function to:
correct a mistake in setting up your partitions
migrate Linux partitions if you are upgrading or
reinstalling &FC;
provide a mount point for non-Linux partitions such as
those used on some Windows operating systems
Windows Partitions
You may not label Windows partitions that use the
NTFSfile systemfile systemNTFSNTFS file
system with a mount point in the &FC; installer. You may
label
vfatfile systemfile systemvfatvfat
(FAT16 or
FAT32)
partitions with a mount point.
If you need to make drastic changes to
your partition configuration, you may want to delete
partitions and start again. If your disk contains data that
you need to keep, back it up before you edit any partitions.
If you edit the size of a partition, you may lose all data
on it.
If your system contains many separate partitions for system
and user data, it is easier to upgrade your system. The
installation program allows you to erase or retain data on
specific partitions. If your user data is on a separate
partition/home/home partition, you can retain that
data while erasing system partitions such as
/boot.
Delete
Select this option to erase an existing partition
partitiondeleting
or LVM physical volume. To delete an LVM physical volume,
first delete any volume groups of which that physical volume
is a member.
If you make a mistake, use the Reset
option to abandon all the changes you have made.
Reset
Select this option to force Disk
Druid to abandon all changes made to disk
partitions.
RAID
Select this button to set up software RAID
RAID
on your &FED; system.
Create a software RAID
partition
Choose this option to add a partition for software
RAID. This option is the only choice available if your
disk contains no software RAID partitions.
Create a RAID device
Choose this option to construct a RAID device from two
or more existing software RAID partitions. This option
is available if two or more software RAID partitions
have been configured.
Clone a drive to create a RAID
device
Choose this option to set up a RAID
mirror of an existing disk.
This option is available if two or more disks are
attached to the system.
LVM
Select this button to set up LVM
LVM
on your &FED; system. First create at least one partition or
software RAID device as an LVM physical volume, using the
New dialog.
To assign one or more physical volumes to a volume group,
first name the volume group. Then select the physical
volumes to be used in the volume group. Finally, configure
logical volumes on any volume groups using the
Add, Edit and
Delete options.
You may not remove a physical volume from a volume group if
doing so would leave insufficient space for that group's
logical volumes. Take for example a volume group made up of
two 5 GB LVM physical volume partitions, which contains an 8
GB logical volume. The installer would not allow you to
remove either of the component physical volumes, since that
would leave only 5 GB in the group for an 8 GB logical
volume. If you reduce the total size of any logical volumes
appropriately, you may then remove a physical volume from
the volume group. In the example, reducing the size of the
logical volume to 4 GB would allow you to remove one of the
5 GB physical volumes.
After you finish setting up and reviewing your partition
configuration, select Next to continue the
installation process.
--- NEW FILE fedora-install-guide-firstboot.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
First Boot
The
Setup AgentSetup Agent launches the first time that
you start a new &FC; system. Use Setup
Agent to configure the system for use before you log
in.
Welcome Screen
Welcome screen.
Select Forward to start the
Setup Agent.
Graphical Interface RequiredSetup Agent requires a graphical
interface. If none is available, configure these options manually
after you log in.
License Agreement
This screen displays the overall licensing terms for &FC;. Each
software package in &FC; is covered by its own license which has
been approved by the
OSI (Open Source Initiative)
Open Source Initiative (OSI). For more information about the OSI,
refer to
http://www.opensource.org/.
License Agreement Screen
License agreement screen.
To proceed, select Yes, I agree to the License
Agreement and then select
Forward.
Firewall
The
firewallconfiguringfirewall built into &FC; checks every
incoming and outgoing network connection on your machine against a
set of rules. These rules specify which types of connections are
permitted and which are denied.
By default the firewall is enabled, with a simple set of rules
that allow connections to be made from your system to others, but
permit only network browsing and
SSH (Secure SHell)firewall configuration
SSH (Secure SHell) connections from other systems. You may make
changes on this screen to allow access to specific network
services on your &FED; system.
Firewall Screen
Firewall screen.
To enable access to the services listed on this screen, click the
check box next to the service name.
SSH Provides Immediate Remote Access
All &FED; systems automatically run the SSH remote access
service. The default firewall configuration allows connections
to this service, to ensure that administrators have immediate
remote access to new systems through the user and
root accounts.
To enable access to other services, select Other
ports, and Add the details. Use
the Port(s) field to specify either the port
number, or the registered name of the service. Select the relevant
Protocol from the drop-down. The majority of
services use the TCP protocol.
The Services List
The services file on every system lists the
port numbers and names of services that are registered with the
Internet Assigned Names Authority (IANA). &FED; systems hold
this file in the directory /etc.
If a service uses more than one port number, enter each port. For
example, an IMAP service enables users to access their e-mail from
another system with either a standard connection to TCP port 143,
or with an encrypted connection to TCP port 993. To permit IMAP
connections to your system, add imap or
port number 143, and
imaps, or port number
993, for IMAP with SSL encryption.
Avoid disabling the firewall. If you believe that it is necessary
to do so, select No firewall.
Changing the Firewall Settings
To change these settings later, choose SystemAdministrationSecurity
Level and Firewall.
&SEL;&SEL; Screen
&SEL; screen.
The
&SEL;configuring&SEL; (Security Enhanced Linux) framework
is part of &FC;. &SEL; limits the actions of both users and
programs by enforcing security policies throughout the operating
system. Without &SEL;, software bugs or configuration changes may
render a system more vulnerable. The restrictions imposed by &SEL;
policies provide extra security against unauthorized access.
Inflexible &SEL; policies might inhibit many normal activities on
a &FED; system. For this reason, &FC; uses targeted policies,
which only affect specific network services. These services cannot
perform actions that are not part of their normal functions. The
targeted policies reduce or eliminate any inconvenience &SEL;
might cause users. Set the &SEL; mode to one of the following:
Enforcing
Select this mode to use the targeted &SEL; policy on your
&FED; system. This is the default mode for &FED;
installations.
Permissive
In this mode, the system is configured with &SEL;, but a
breach of security policies only causes an error message to
appear. No activities are actually prohibited when &SEL; is
installed in this mode. You may change the &SEL; mode to
Enforcing at any time after booting.
Disabled
If you choose this mode for &SEL;, &FED; does not configure
the access control system at all. To make &SEL; active
later, select SystemAdministrationSecurity Level and Firewall.
To adjust &SEL;, choose Modify SELinux
Policy. To exempt a key service from &SEL;
restrictions, select the service from the list, and choose the
Disable SELinux protection option. The
SELinux Service Protection item on the list
includes options to disable &SEL; restrictions on additional
services.
Changing the &SEL; policy
&SEL; is unique in that it cannot be bypassed, even by the
system administrators. To change the behavior of &SEL; after
installation, choose SystemAdministrationSecurity
Level and Firewall.
For more information about &SEL;, refer to the &SEL; FAQ at
.
Date and Time
If your system does not have Internet access or a network time
server, manually set the date and time for your system on this
screen. Otherwise, use
NTP (Network Time Protocol)NTP (Network Time Protocol) servers to
maintain the accuracy of the clock. NTP provides time
synchronization service to computers on the same network. The
Internet contains many computers that offer public NTP services.
The initial display enables you to set the date and time of your
system manually.
Date and Time Screen
Date and time screen.
Select the Network Time Protocol tab to
configure your system to use NTP servers instead.
Setting the Clock
To change these settings later, choose SystemAdministrationDate &
Time.
To configure your system to use network time servers, select the
Enable Network Time Protocol option. This
option disables the settings on the Date and
Time tab and enables the other settings on this screen.
Date and Time Screen
Date and time screen.
By default, &FC; is configured to use three separate groups, or
pools, of time servers. Time server pools
create redundancy, so if one time server is unavailable, your
system synchronizes with another server.
To use an additional time server, select Add,
and type the DNS name of the server into the box. To remove a
server or server pool from the list, select the name and click
Delete.
If the hardware clock in your computer is highly inaccurate, you
may turn off your local time source entirely. To turn off the
local time source, select Show advanced
options and then deselect the Use Local Time
Source option. If you turn off your local time source,
the NTP servers take priority over the internal clock.
If you enable the Enable NTP Broadcast
advanced option, &FC; attempts to automatically locate time
servers on the network.
Display
The Setup Agent automatically attempts
to identify the graphics card and monitor for your computer. It
uses this information to calculate the correct
Resolution and Color
Depth settings.
Display Screen
Display screen.
If you need to change the monitor, select
Configure to display a list of manufacturers.
Select the manufacturer of your monitor on the list, and hit the
+ key or select the triangle next to the name to
view supported models. Choose the correct model from the list and
select OK. If none of the listed models
match your monitor, select the closest match from either the
Generic CRT Display list or the
Generic LCD Display list.
Monitor Dialog
Monitor dialog.
To change a display setting, select
Resolution or Color
Depth, and select a new value from the drop-down list.
The Setup Agent only shows the settings
that are valid for your hardware.
Resetting the display
To reconfigure your system after the installation has completed,
choose SystemAdministrationDisplay.
System User
Create a user account for yourself with this screen. Always use
this account to log in to your &FC; system, rather than using the
root account.
System User Screen
System user screen.
Enter a user name and your full name, and then enter your chosen
password. Type your password once more in the Confirm
Password box to ensure that it is correct. Refer to
for guidelines on selecting a
secure password.
Creating extra user accounts
To add additional user accounts to your system after the
installation is complete, choose SystemAdministrationUsers &
Groups.
To configure &FC; to use network services for authentication or
user information, select Use Network
Login....
After you configure login services, select
Finish to proceed to the login screen.
Your &FC; system is now ready for use.
Update Your System
To ensure the security of your system, run a package update
after the installation completes.
explains how to update your
&FED; system.
--- NEW FILE fedora-install-guide-installingpackages.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Installing Packages
&FC; reports the installation progress on the screen as it writes
the selected packages to your system. Network and DVD installations
require no further action. If you are using CDs to install, &FC;
prompts you to change discs periodically. After you insert a disc,
select OK to resume the installation.
Installing Packages Screen
Installing packages screen.
After installation completes, select Reboot
to restart your computer. &FC; ejects any loaded discs before the
computer reboots.
--- NEW FILE fedora-install-guide-intro.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Introduction
&FC; is a complete desktop and server operating system created
entirely with open source software.
&FC; Lifecycle
&FC; is a rapidly evolving system which follows the latest
technical developments. &FC; may not be appropriate for use in
critical applications in your organization.
This manual helps you to install &FC; on desktops, laptops and
servers. The installation system is flexible enough to use even if
you have no previous knowledge of Linux or computer networks. If you
select default options, &FC; provides a complete desktop operating
system, including productivity applications, Internet utilities, and
desktop tools.
This document does not detail all of the features of the
installation system.
&BUG-REPORTING;
Background
The &FP;, which produces and maintains &FC;, is a collaboration
between &FORMAL-RHI; and the
free softwareFOSSopen sourceFOSSFOSS (free and open source software)free and open source software (FOSS)
community. The &FP; also provides &FEX;, additional software
packaged for installation on a &FC; system.
For more information about the &FP;, please visit
&FP-URL;. Refer to
http://www.opensource.org/
and
http://www.gnu.org/philosophy/free-sw.html
for more information about open source software.
Understanding i386 and Other Computer Architectures
The &FP; provides versions of &FC; for PCs, and also for a range
of other machines that are based on different technologies. Each
version of &FC; is built for computers that are based on a
specific architecture. All 32-bit PCs are
based on the i386 architecture. You may
also install versions of &FC; on computers that are based on
x86_64 or ppc
technology. The architectures are explained below:
i386
Intel x86-compatible processors, including Intel Pentium and
Pentium-MMX, Pentium Pro, Pentium-II, Pentium-III, Celeron,
Pentium 4, and Xeon; VIA C3/C3-m and Eden/Eden-N; and AMD
Athlon, AthlonXP, Duron, AthlonMP, and Sempron
ppc
PowerPC processors, such as those found in Apple Power
Macintosh, G3, G4, and G5, and IBM pSeries systems
x86_64
64-bit AMD processors such as Athlon64, Turion64, Opteron;
and Intel 64-bit processors such as EM64T
Before You Begin
Before you install &FC;, you need access to:
boot or installation media (refer to
for more information)
information about your network configuration
a copy of this &IG; and the Release Notes for this version of
&FC;
The Release Notes specify the hardware requirements for the
version of &FC; which you are about to install. They also provide
advice on any known problems with particular hardware and software
configurations.
The Release Notes are available on the first disc in HTML and
plain text format. The latest versions of this &IG; and the
Release Notes are available at &FDPDOCS-URL;.
Storage
A &FED; system requires a minimum of 700 MB storage for a
command-line system. A desktop system with the default
applications requires at least 3 GB of storage. You may install
multiple copies of &FED; on the same computer.
Configure any RAID functions provided by the mainboard of your
computer, or attached controller cards, before you begin the
installation process. &FED; can automatically detect many RAID
devices and use any storage they provide.
Networking
By default, &FC; systems attempt to discover correct connection
settings for the attached network using
DHCP (Dynamic Host Configuration Protocol)DHCP (Dynamic Host Control Protocol).
Your network may include a DHCP provider which delivers settings
to other systems on demand. The DHCP provider may be a router or
wireless access point for the network, or a server.
In some circumstances you may need to provide information about
your network during the installation process. Refer to
and
for more
information.
Modem Configuration
The installation system for &FC; does not configure modems. If
your computer has a modem, configure the dialing settings
after you complete the installation and reboot.
Installing from a Server or Web Site
You may install &FC; using a mirror, a
Web site or network server that provide a copy of the necessary
files. To use a mirror, you need to know:
the name of the server
the network protocol used for installation (FTP, HTTP, or
NFS)
the path to the installation files on the server
You may install &FC; from your own private mirror, or use one of
the public mirrors maintained by members of the community. To
ensure that the connection is as fast and reliable as possible,
use a server that is close to your own geographical location.
The &FP; maintains a list of HTTP and FTP public mirrors, sorted
by region:
To determine the complete directory path for the
installation files, add
/&FCLOCALVER;/architecture/os/
to the path shown on the webpage.
Building Your Own Mirror
Refer to
for information on how to create your own &FED; mirror for
either public or private use.
To use a mirror, boot your computer with a &FED; disc, and
follow the instructions in
. Refer to
for more information on
creating the boot media.
Using the Installation Discs
If you boot your computer with either an installation DVD, or
the first installation CD, enter linux
askmethod at the
boot:
prompt to access the server installation options.
If your network includes a server, you may also use
PXE (Pre-boot eXecution Environment) to
boot your computer. PXE (also referred to as
netboot) is a standard that enables PCs
to use files on a server as a boot device. &FC; includes
utilities that allow it to function as a PXE server for other
computers. You can use this option to install &FC; on a
PXE-enabled computer entirely over the network connection, using
no physical media at all.
Installing &FC; on a Managed Network
Some corporate networks include a directory
service that manages user accounts for the
organization. &FC; systems can join a Kerberos, NIS, Hesiod, or
MicrosoftWindows domain as
part of the installation process. &FC; can also use LDAP
directories.
Consult Network Administrators
If you are installing outside of your home, always consult the
administrators before installing a &FC; system on an existing
network. They can provide correct network and authentication
settings, and guidance on specific organizational policies and
requirements.
Preparing Media
To install &FC; from discs, you need five installation CDs, or the
installation DVD. There are separate disc sets for each supported
architecture.
For instructions to download and prepare this CD or DVD
installation media, refer to
. If you already
have the full set of &FC; installation media, skip to
.
Architecture-Specific Distributions
To install &FC;, you must use the boot and installation media
that is particular to your architecture.
You may use the first CD or DVD installation disc from the
complete &FC; distribution to boot your computer. The &FC;
distribution also includes image files for
boot-only CD or DVD media and USB media. These files can be
converted into bootable media using standard Linux utilities or
third-party programs on other operating systems.
You may boot your computer with boot-only media, and load the
installation system from another source to continue the process.
The types of installation source for &FED; include:
CD or DVD media installation discs
hard drive, either attached by USB, or internal to the
computer
network installation server, using either HTTP, FTP, or NFS
You can use this facility to install &FC; on machines without
using installation discs. For example, you may install &FC; on a
laptop with no CD or DVD drive by booting the machine with a USB
pen drive, and then using a hard drive as an installation source.
The supported boot media for &FED; include:
CD or DVD media (either installation disc #1 or a special
boot-only disc)
USB media
network interface (via PXE)
Installation from Diskettes
There is no option to either boot or install &FC; from
diskettes.
Preparing CD or DVD Media
The images/boot.iso file on the first &FC;
installation disc is a boot image designed for CD and DVD media.
This file also appears on FTP and Web sites providing &FC;. You
can also find this file on mirror sites in the &FC; distribution
directory for your particular architecture.
To convert an ISO file into a physical CD, use the option in
your CD-writing program that burns a CD image file to a CD. If
you copy the file itself to a CD instead, the disc will not boot
or work correctly. Refer to your CD writing program
documentation for instructions. If you are using Linux, use the
following command to burn a CD image file to a blank recordable
CD:
cdrecord --device=cdwriter-device -tao -eject image-file.isoPreparing USB Boot MediaData LossThis procedure destroys data on the
media. Back up any important information before you
begin. Some models of USB media use additional partitions or
software to provide functions such as encryption. This
procedure may make it difficult or impossible to access these
special areas on your boot media.
The images/diskboot.img file on the first
&FC; installation disc is a boot image designed for USB media.
This file also appears on FTP and Web sites providing &FC;.
Several software utilities are available for Windows and Linux
that can write image files to a device. Linux includes the
dd command for this purpose. To write an
image file to boot media with dd on a current
version of &FC;:
Locate the image file.
Attach or insert the media.
Your system may automatically detect and open the media. If
that happens, close or unmount the media before continuing.
Open a terminal window.
In the terminal window, type the following command:
dd if=diskboot.img of=/dev/sda
--- NEW FILE fedora-install-guide-locale.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Identifying Your Locale
If the installation system fails to identify the display hardware on
your computer, it displays text screens rather than the default
graphical interface. The text screens provide the same functions as
the standard screens. Later in the installation process you can
manually specify your display hardware.
Network Installations
Network installations with HTTP and FTP always use text screens on
systems with less than 128Mb of memory.
Language Selection
The installation program displays a list of languages supported by
&FED;.
Language Selection Screen
Language selection screen.
Highlight the correct language on the list and select
Next.
Installing Support For Additional Languages
To select support for additional languages, customize the
installation at the package selection stage. For more
information, refer to .
Keyboard Configuration
The installation program display a list of the keyboard layouts
supported by &FED;:
Keyboard Configuration Screen
Keyboard configuration screen.
Highlight the correct layout on the list, and select
Next.
--- NEW FILE fedora-install-guide-networkconfig.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Network Configuration
Use this screen to customize the network settings of your &FED;
system.
Manual network configuration of a &FED; system is often not
required. Many networks have a DHCP (Dynamic Host Configuration Protocol)DHCP (Dynamic Host Configuration
Protocol) service that automatically supplies connected systems with
configuration data. By default, &FC; activates all network
interfaces on your computer and configures them to use DHCP.
Network Configuration Screen
Network configuration screen.
Network Devices
&FED; displays a list of network interfaces detected on your
computer. Each interface must have a unique IP
addressIP address on the network to which it is attached. The interface
may receive this address from the network DHCP (Dynamic Host Configuration Protocol) DHCP service.
To manually assign an IP address, highlight the interface on the
Network Device list and select
Edit. &FED; then displays a network
configuration dialog. Deselect the
Configure using DHCP check box, so that it is
empty. Enter the IP Address and the
appropriate Netmask for the interface. Then
select OK.
If your computer will be a server, do not use DHCP. Manually
configure networking instead. Manual network configuration allows
your server to join the local network even if the DHCP provider is
down.
Specify whether an interface should be automatically activated at
boot time with the Active on Boot check box
for that device. You may manually activate a network interface at
any time after the system has booted.
Modem Configuration
The Network Configuration screen does not
list modem modems. Configure these devices after installation
with either the Internet Configuration
Wizard or Network
Cnfiguration utility. The settings for your
modem are specific to your particular Internet Service Provider
(ISP).
Computer Hostname
On some networks, the DHCP provider also provides the name of the
computer, or hostnamehostname. To specify the
hostname, select Manual and type the complete
name in the box. The complete hostname includes both the name of
the machine and the name of the domain of which it is a member,
such as machine1.example.com. The
machine name (or "short hostname") is
machine1, and the domain name domain name is
example.com.
Valid Hostnames
You may give your system any name provided that the full
hostname is unique. The hostname may include letters, numbers
and hyphens.
Miscellaneous Settings
To manually configure a network interface, you may also provide
other network settings for your computer. All of these settings
are the IP addresses of other systems on the network.
A gatewaygateway is the device that provides access to other networks.
Gateways are also referred to as routergatewayrouters. If your system
connects to other networks through a gateway, enter its IP address
in the Gateway box.
Most software relies on the DNS (Domain Name Service)DNS (Domain Name Service)
provider to locate machines and services on the network. DNS
converts hostnames to IP addresses and vice versa. A &FC; system
may use more than one DNS server. If the primary DNS server does
not respond, the computer sends any query to the secondary DNS
server, and so on. To assign DNS servers, type their IP addresses
into the Primary,
Secondary, or Tertiary DNS
Server boxes.
Click Next once you are satisfied with the
network settings for your system.
--- NEW FILE fedora-install-guide-nextsteps.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Your Next Steps
&FED; provides you with a complete operating system with a vast
range of capabilities, supported by a large community.
Updating Your System
The &FP; releases updated software packages for &FC; throughout
the support period of each version. Updated packages add new
features, improve reliability, resolve bugs, or remove security
vulnerabilities. To ensure the security of your system, carry out
an update when the installation process completes. You should then
update regularly, and as soon as possible after a security
announcement is issued. Refer to
for information on the
&FED; announcements services.
To update your system with the latest packages, use the
Package UpdaterPackage Updater:
Choose ApplicationsSystem ToolsPackage
Updater.
When prompted, enter the
root password.
Review the list of updated packages. The package list displays
a double arrow next to any updates that require a system
reboot to take effect.
Click Apply Updates to begin the update
process.
If one or more updates require a system reboot, the update
process displays a dialog with the option to Reboot
Now. Either select this option to reboot the
system immediately, or Cancel it and
reboot the system at a more convenient time.
To update packages from the command-line, use the
yumyum utility. Type this command to begin a full
update of your system with yum:
su -c 'yum update'
Enter the root password
when prompted.
Refer to for
more information on yum.
Automating Updates
If your &FED; system has a permanent network connection, you may
choose to enable daily system updates. To enable automatic
updates, follow the instructions on the webpage
.
Subscribing to &FED; Announcements and News
To receive information about package updates, subscribe to either
the announcements mailing list, or the RSS feeds.
&FP; announcements mailing list
&FP; RSS feeds
The announcements mailing list also provides you with news on the
&FP;, and the &FED; community.
Security Announcements
Announcements with the keyword
[SECURITY] in the title identify
package updates that resolve security vulnerabilities.
Finding Documentation and Support
Members of the &FED; community provides support through mailing
lists, Web forums and Linux User Groups (LUGs) across the world.
The Web site for the official forums is
.
The following resources provide information on many aspects of
&FED;:
The FAQ on the &FP; website
The documents available from the &FDP; Web site
The Linux Documentation Project (LDP)
The &RHEL; documentation, much of which also applies to
&FED;
Many other organizations and individuals also provide tutorials
and HOWTOs for &FED; on their Web sites. You can locate
information on any topic by using Google's Linux search site,
located at .
Joining The &FED; Community
The &FP; is driven by the individuals that contribute to it.
Community members provide support and documentation to other
users, help to improve the software included in &FC; by testing,
and develop new software alongside the programmers employed by
&RH;. The results of this work are available to all.
To make a difference, start here:
--- NEW FILE fedora-install-guide-other-instmethods.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Alternative Installation Methods
The installation method screen below appears if one of the following
is true:
You booted with PXE, USB media, or boot-only CD or DVD media.
You entered the option at the
boot:
prompt.
Installation Method Screen
Installation method screen.
Highlight the appropriate installation method on the list, and
select OK.
CD/DVD Activity
If the first &FC; distribution installation disc is in your
computer's CD or DVD drive, the installation program loads its
next stage from that disc. The installation program still
downloads package data from the source you
choose.
Installation from a Network Server
You may install &FC; from a network server using FTP, HTTP, or
NFS (Network File System)install from
NFS protocols. Refer to
for
information on installation servers.
TCP/IP Configuration
By default, the installation program uses DHCP to automatically
provide the network settings. If your network has no DHCP
server, clear the check box labeled Use dynamic IP
configuration and enter the settings manually.
Select OK to continue.
Configure TCP/IP Dialog
TCP/IP configuration dialog.
These settings apply only during the installation process. The
installation program allows you to configure the final network
configuration later.
Network Service Setup
The FTP, HTTP, and NFS service setup dialogs are very similar.
Each requires the name or IP address of the server, and a
directory where the installation files reside. To use a public
server, or mirror website, refer to
for
information on valid server names and directory paths.
FTP Setup Dialog
FTP setup dialog.
The FTP service setup dialog also has an option for
non-anonymous FTP. If your FTP server does
not provide anonymous access, select this check box, and provide
an account name and password in the following dialog. Select
OK to continue.
Non-anonymous FTP Account Dialog
Non-anonymous FTP account dialog.
Large Download
Network installations download the main installation program
from the server that you specify. The graphical installation
program is over 60 Mb in size. Computers with a slow network
connection may take several minutes to download this file.
Installation from a Hard Drive
Once you have booted your computer, you may use ISO image files of
the &FED; discs to continue the installation process. The ISO
files must be located on a hard drive that is either internal to
the computer, or attached to the machine by USB. You can use this
option to install &FC; on computers that have neither a network
connection nor CD or DVD drives.
The partition on the hard drive holding the ISO files must be
formatted with the
ext2file systemsfile systemsext2ext2,
ext3file systemsfile systemsext3ext3 or
vfatfile systemsfile systemsvfatvfat file system. In &FED;,
vfat includes a range
of file systems, such as FAT-16 and FAT-32, found on most
removable media. External hard drives usually contain
vfat (FAT-32) file
systems. Some Microsoft Windows systems also use
vfat file systems on
internal hard disk partitions.
FAT-16, FAT-32, and <systemitem
class="filesystem">vfat</systemitem>
Before you begin installation from a hard drive, check the
partition type to ensure that &FED; can read it. To check a
partition's file system under Windows, use the Disk
Management tool. To check a partition's file
system under Linux, use the fdisk utility.
You cannot use ISO files on partitions controlled by LVM (Logical
Volume Management). Refer to
for more information
about file systems.
If you choose this option, the following screen appears:
Select Partition Screen
Select partition screen.
Select the partition containing the ISO files from the list of
available partitions. Internal IDE drive device names begin with
/dev/hd. SCSI or USB drive device names begin
with /dev/sd. Each individual drive has its
own letter, for example /dev/hda. Each
partition on a drive is numbered, for example
/dev/sda1.
Also specify the Directory holding images.
Enter the full directory path from the drive that contains the ISO
image files.
Select OK to continue.
--- NEW FILE fedora-install-guide-packageselection.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Software Selection
By default, the &FED; installation process loads a selection of
software that is suitable for a desktop system.
Task Selection Screen
Task selection screen.
To include or remove software for common tasks, select the relevant
items from the list:
Office and Productivity
This option provides the OpenOffice.org productivity suite,
the Planner project management application, graphical tools
such as the GIMP, and multimedia applications.
Software Development
This option provides the necessary tools to compile software
on your &FED; system.
Web server
This option provides the Apache Web server.
Select Customize now to specify the software
packages for your final system in more detail. This option causes
the installation process to display an additional customization
screen when you select Next.
Installing Support for Additional Languages
Select Customize now to install support for
additional languages. Refer to
for more information on configuring language support.
Core Network Services
All Fedora Core installation include the following network services:
centralized logging through syslog
email through SMTP (Simple Mail Transfer Protocol)
network file sharing through NFS (Network File System)
remote access through SSH (Secure SHell)
resource advertising through mDNS (multicast DNS)
The default installation also provides:
network file transfer through HTTP (HyperText Transfer Protocol)
printing through CUPS (Common UNIX Printing System)
remote desktop access through VNC (Virtual Network Computing)
Some automated processes on your Fedora system use the email
service to send reports and messages to the system administrator.
By default, the email, logging, and printing services do not
accept connections from other systems. &FED; installs the NFS
sharing, HTTP, and VNC components without enabling those services.
You may configure your Fedora system after installation to offer
email, file sharing, logging, printing and remote desktop access
services. The SSH service is enabled by default. You may use NFS
to access files on other systems without enabling the NFS sharing
service.
Customizing the Software Selection
&FED; divides the included software into
package groupspackage groups. For ease of use, the
package selection screen displays these groups as six categories:
Package Group Selection Screen
Package group selection screen.
To view the package groups for a category, select the category
from the list on the left. The list on the right displays the
package groups for the currently selected category.
To specify a package group for installation, select the check box
next to the group. The box at the bottom of the screen displays
the details of the package group that is currently highlighted.
None of the packages from a group will be
installed unless the check box for that group is selected.
If you select a package group, &FED; automatically installs the
base and mandatory packages for that group. To change which
optional packages within a selected group will be installed,
select the Optional Packages button under
the description of the group. Then use the check box next to an
individual package name to change its selection.
Package Group Details Dialog
Package group details dialog.
Changing Your Mind
The packages that you select are not permanent. After you boot
your system, use the pirut tool to
make different software selections for your system. To run this
tool, from the main menu, select ApplicationsAdd/Remove
Software.
Additional Language Support
Your &FC; system automatically supports the language that you
selected at the start of the installation process. To include
support for additional languages, select the package group for
those languages from the Languages category.
After you choose the desired packages, select
Next to proceed. &FC; checks your selection,
and automatically adds any extra packages required to use the
software you select.
--- NEW FILE fedora-install-guide-rootpassword.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Set the Root Password
&FED; uses a special account named root accountroot for system
administration. The root
account on a Linux system is not subject to most normal account
restrictions. As the system owner or administrator, you may
sometimes require special privileges to configure or modify the
system. In those cases, use the root account.
Using the <systemitem class="username">root</systemitem>
Account
Avoid logging in to &FC; as root when possible. Any
administration tools which require root privileges will prompt you
for the password.
The &FED; installation program requires the root password to be at least six characters
long. Because the root
account may potentially control any part of the system, use the
following guidelines to create a good password:
Use a combination of uppercase letters, lowercase letters,
numbers, punctuation and other characters.
Do not use a word or name. Obscuring the word or name with
substitute characters is not effective.
Do not use the same password for more than one system.
The following are examples of good passwords:
f9*@1Ls99AHL8$391%%rbIwtb,10^th
Enter the root password
into the Root Password field. &FED; displays
the characters as asterisks for security. Type the same password
into the Confirm field to ensure it is set
correctly.
Set Root Password Screen
Set root password screen.
After you set the root password, select Next
to proceed.
--- NEW FILE fedora-install-guide-techref.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Other Technical Documentation
This document provides a reference for using the &FC; installation
software, known as anaconda. To learn more about
Anacondaanaconda, visit the project Web page:
.
Both anaconda and &FC; systems use a common set
of software components. For detailed information on key
technologies, refer to the Web sites listed below:
Boot Loader
&FC; uses the
GRUBdocumentationGRUB boot loader. Refer to
for more
information.
Disk Partitioning
&FC; uses parted to partition disks. Refer
to for more
information.
Storage ManagementLVMdocumentation
Logical Volume Management (LVM) provides administrators with a
range of facilities to manage storage. By default, the &FED;
installation process formats drives as LVM volumes. Refer to
for more
information.
Audio Support
The Linux kernel used by &FC; incorporates
ALSA (Advanced
Linux Sound Architecture)
ALSA (Advanced Linux Sound Architecture). For more information
about ALSA, refer to the project Web site:
.
Graphics System
Both the installation system and &FC; use the
XorgXorg suite to provide graphical
capabilities. Components of Xorg manage the
display, keyboard and mouse for the desktop environments that
users interact with. Refer to
for more information.
Remote Displays
&FC; and anaconda include
VNC (Virtual Network Computing)documentation
VNC (Virtual Network Computing) software to enable remote
access to graphical displays. For more information about VNC,
refer to the documentation on the RealVNC Web site:
.
Command-line Interface
By default, &FC; uses the GNU bash shell to
provide a command-line interface. The GNU Core Utilities
complete the command-line environment. Refer to
for
more information on bash. To learn more
about the GNU Core Utilities, refer to
.
Remote System Access
&FC; incorporates the
OpenSSHSSH
OpenSSH suite to provide remote access to the system. The SSH
SSH (Secure SHell)documentation
service enables a number of functions, which include access to
the command-line from other systems, remote command execution,
and network file transfers. During the installation process
anaconda may use the scpscpSSH
feature of OpenSSH to transfer crash reports to remote
systems. Refer to the OpenSSH Web site for more information:
.
Access Control&SEL;documentation
&SEL; provides Mandatory Access Control (MAC) capabilities
that supplement the standard Linux security features. Refer to
the &SEL; FAQ for more information:
.
Firewall
The Linux kernel used by &FC; incorporates the
netfilter framework to provide
firewalldocumentation
firewall features. The Netfilter project website provides
documentation for both netfilter, and the
iptables administration facilities:
.
Software Installation
&FC; uses
yumdocumentationyum to manage the RPM packages that make up
the system. Refer to
for more
information.
VirtualizationXendocumentation
Xen provides the capability to simultaneously run multiple
operating systems on the same computer. &FC; also includes
tools to install and manage the secondary systems on a &FED;
host. You may select Xen support during the installation
process, or at any time thereafter. Refer to
for
more information.
--- NEW FILE fedora-install-guide-timezone.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Time Zone Selection
This screen allows you to specify the correct time zone for the
location of your computer. Specify a time zone even if you plan to
use NTP (Network Time Protocol) NTP (Network Time Protocol) to maintain the accuracy of
the system clock.
Selecting a Time Zone
&FED; displays on the screen two methods for selecting the time
zone.
Time Zone Selection Screen
Time zone selection screen.
To select a time zone using the map, first place your mouse
pointer over your region on the map. Click once to magnify that
region on the map. Next, select the yellow dot that represents the
city nearest to your location. Once you select a dot, it becomes a
red X to indicate your selection.
To select a time zone using the list, select the name of the city
nearest to your location. The cities are listed in alphabetical
order.
Universal Co-ordinated Time (UTC)UTC (Universal Co-ordinated time) Universal Co-ordinated Time is also known as
GMT (Greenwich Mean Time)UTC Greenwich Mean Time (GMT).
If &FC; is the only operating system on your computer, select
System clock uses UTC. The system clock is a
piece of hardware on your computer system. &FC; uses the timezone
setting to determine the offset between the local time and UTC on
the system clock. This behavior is standard for UNIX-like
operating systems.
Windows and the System Clock
Do not enable the System clock uses UTC
option if your machine also runs Microsoft Windows. Microsoft
operating systems change the BIOS clock to match local time
rather than UTC. This may cause unexpected behavior under &FC;.
Select Next to proceed.
--- NEW FILE fedora-install-guide-upgrading.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
Upgrading an Existing System
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.
Upgrade Examine
If your system contains a &FC; or &RHL; installation, the
following screen appears:
Upgrade Examine Screen
Upgrade examine screen.
To perform an upgrade of an existing system, choose the
appropriate installation from the drop-down list and select
Next.
Manually Installed Software
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.
Upgrading Boot Loader Configurationboot loaderupgrading Your completed &FC; installation must be registered
in the boot loaderGRUBboot loader to boot properly.
A boot loader is software on your machine that locates and starts
the operating system. Refer to
for more information about boot loaders.
Upgrade Bootloader Screen
Upgrade bootloader screen.
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 Update
boot loader configuration. This is the default
behavior when you upgrade an existing &FC; or &RHL; installation.
GRUB is the standard boot loader for &FED;.
If your machine uses another boot loader, such as
BootMagic, System
Commander, or the loader installed by Microsoft
Windows, then the &FED; installation system cannot update it.
In this case, select Skip boot loader
updating. When the installation process completes,
refer to the documentation for your product for assistance.
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 Create new boot loader
configuration to remove the existing boot loader and
install GRUB.
After you make your selection, click Next
to continue.
--- NEW FILE fedora-install-guide.xml ---
%FEDORA-ENTITIES;
%DOC-ENTITIES;
]>
From fedora-docs-commits at redhat.com Fri Mar 17 19:40:22 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Fri, 17 Mar 2006 14:40:22 -0500
Subject: install-guide Makefile,1.22,1.23 rpm-info.xml,1.15,1.16
Message-ID: <200603171940.k2HJeqm9030387@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30316
Modified Files:
Makefile rpm-info.xml
Log Message:
- Migrated to en_US.
Index: Makefile
===================================================================
RCS file: /cvs/docs/install-guide/Makefile,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- Makefile 2 Mar 2006 22:57:09 -0000 1.22
+++ Makefile 17 Mar 2006 19:40:14 -0000 1.23
@@ -16,7 +16,7 @@
# Document-specific definitions.
#
DOCBASE = fedora-install-guide
-PRI_LANG = en
+PRI_LANG = en_US
OTHERS = zh_CN
# If ${DOC_ENTITIES} is defined, ${PRI_LANG}/${DOC_ENTITIES}.xml
# must contain a complete XML file conforming to the DTD located
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/rpm-info.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- rpm-info.xml 14 Mar 2006 22:34:19 -0000 1.15
+++ rpm-info.xml 17 Mar 2006 19:40:14 -0000 1.16
@@ -22,7 +22,7 @@
Paul W. Frields
-
+ Fedora Core 5 Installation Guide - BETAProvides documentation for the installation process.
From fedora-docs-commits at redhat.com Fri Mar 17 19:47:15 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Fri, 17 Mar 2006 14:47:15 -0500
Subject: install-guide/en entities.xml, 1.5,
NONE fedora-install-guide-abouttoinstall.xml, 1.8,
NONE fedora-install-guide-acknowledgements.xml, 1.8,
NONE fedora-install-guide-adminoptions.xml, 1.11,
NONE fedora-install-guide-beginninginstallation.xml, 1.9,
NONE fedora-install-guide-bootloader.xml, 1.8,
NONE fedora-install-guide-diskpartitioning.xml, 1.11,
NONE fedora-install-guide-firstboot.xml, 1.14,
NONE fedora-install-guide-installingpackages.xml, 1.8,
NONE fedora-install-guide-intro.xml, 1.13,
NONE fedora-install-guide-locale.xml, 1.10,
NONE fedora-install-guide-networkconfig.xml, 1.8,
NONE fedora-install-guide-nextsteps.xml, 1.9,
NONE fedora-install-guide-other-instmethods.xml, 1.10,
NONE fedora-install-guide-packageselection.xml, 1.12,
NONE fedora-install-guide-rootpassword.xml, 1.8,
NONE fedora-install-guide-techref.xml, 1.9,
NONE fedora-install-guide-timezone.xml, 1.8,
NONE fedora-install-guide-upgrading.xml, 1.8,
NONE fedora-install-guide.xml, 1.10, NONE
Message-ID: <200603171947.k2HJlF50030530@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/install-guide/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30513
Removed Files:
entities.xml fedora-install-guide-abouttoinstall.xml
fedora-install-guide-acknowledgements.xml
fedora-install-guide-adminoptions.xml
fedora-install-guide-beginninginstallation.xml
fedora-install-guide-bootloader.xml
fedora-install-guide-diskpartitioning.xml
fedora-install-guide-firstboot.xml
fedora-install-guide-installingpackages.xml
fedora-install-guide-intro.xml fedora-install-guide-locale.xml
fedora-install-guide-networkconfig.xml
fedora-install-guide-nextsteps.xml
fedora-install-guide-other-instmethods.xml
fedora-install-guide-packageselection.xml
fedora-install-guide-rootpassword.xml
fedora-install-guide-techref.xml
fedora-install-guide-timezone.xml
fedora-install-guide-upgrading.xml fedora-install-guide.xml
Log Message:
- Remove files from obsolete en/ directory.
--- entities.xml DELETED ---
--- fedora-install-guide-abouttoinstall.xml DELETED ---
--- fedora-install-guide-acknowledgements.xml DELETED ---
--- fedora-install-guide-adminoptions.xml DELETED ---
--- fedora-install-guide-beginninginstallation.xml DELETED ---
--- fedora-install-guide-bootloader.xml DELETED ---
--- fedora-install-guide-diskpartitioning.xml DELETED ---
--- fedora-install-guide-firstboot.xml DELETED ---
--- fedora-install-guide-installingpackages.xml DELETED ---
--- fedora-install-guide-intro.xml DELETED ---
--- fedora-install-guide-locale.xml DELETED ---
--- fedora-install-guide-networkconfig.xml DELETED ---
--- fedora-install-guide-nextsteps.xml DELETED ---
--- fedora-install-guide-other-instmethods.xml DELETED ---
--- fedora-install-guide-packageselection.xml DELETED ---
--- fedora-install-guide-rootpassword.xml DELETED ---
--- fedora-install-guide-techref.xml DELETED ---
--- fedora-install-guide-timezone.xml DELETED ---
--- fedora-install-guide-upgrading.xml DELETED ---
--- fedora-install-guide.xml DELETED ---
From fedora-docs-commits at redhat.com Sun Mar 19 11:44:58 2006
From: fedora-docs-commits at redhat.com (Yuan Yijun (bbbush))
Date: Sun, 19 Mar 2006 06:44:58 -0500
Subject: marketing-content/FC-5-press-release zh_CN.po,NONE,1.1
Message-ID: <200603191144.k2JBiwnR032249@cvs-int.fedora.redhat.com>
Author: bbbush
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32232
Added Files:
zh_CN.po
Log Message:
54t
--- NEW FILE zh_CN.po ---
msgid ""
msgstr ""
"Project-Id-Version: Fedora Core 5 Release Summary\n"
"POT-Creation-Date: 2006-03-18 00:26+0800\n"
"PO-Revision-Date: 2006-03-18 02:21+0800\n"
"Last-Translator: Yuan Yijun \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: fc5-press-release-en_US.xml:9(header)
msgid "Presenting Fedora Core 5"
msgstr "Fedora Core 5 ??????"
#: fc5-press-release-en_US.xml:10(para)
msgid "The Fedora Project is pleased to announce the release of Fedora Core 5. New desktop applications, advances in security, better localization tools, improved software installation and management facilities, and strong Java integration help to make Fedora Core 5 the most innovative Linux distribution ever."
msgstr "Fedora ????????????????????? Fedora Core 5 ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Java ??????????????? Fedora Core 5 ????????????????????????????????? Linux ????????????"
#: fc5-press-release-en_US.xml:17(para)
msgid "For a more complete list of changes and interesting information for users, administrators, and developers, refer to the latest release notes:"
msgstr "?????????????????????????????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:25(header)
msgid "Getting Fedora Core 5"
msgstr "?????? Fedora Core 5"
#: fc5-press-release-en_US.xml:26(header)
msgid "Download ISO Images"
msgstr "?????? ISO ????????????"
#: fc5-press-release-en_US.xml:27(para)
msgid "Users can download the ISO images of the installation DVD or CD-ROMs now from the Fedora Website."
msgstr "??????????????? Fedora ????????????????????????(DVD ??? CD-ROM)??? ISO ???????????????"
#: fc5-press-release-en_US.xml:34(header)
msgid "Online Vendors"
msgstr "???????????????"
#: fc5-press-release-en_US.xml:35(para)
msgid "We recognize that many people do not have sufficient bandwidth to download an entire operating system. This is one of the reasons that the Trademark Guidelines are written to allow third parties to sell physical media containing Fedora Core, as long as they comply with the guidelines."
msgstr "?????????????????????????????????????????????????????????????????????????????? Trademark Guidelines(??????????????????)????????????????????????????????? Fedora Core ?????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:47(header)
msgid "Fedora Community Free Media"
msgstr "Fedora ??????????????????"
#: fc5-press-release-en_US.xml:48(para)
msgid "Fedora Community Free Media, a volunteer initiative under the Fedora Ambassadors Program, aims to distribute Fedora Core media (DVDs) for free to individuals. Local Fedora Ambassadors or Contributors are invited to participate."
msgstr "Fedora ????????????????????? Fedora ?????????????????????????????????????????????????????????????????????????????????????????? Fedora Core ??????(DVD ???)???????????? Fedora ??????????????????????????????"
#: fc5-press-release-en_US.xml:60(header)
msgid "What's New In Fedora Core 5"
msgstr "Fedora Core 5 ???????????????"
#: fc5-press-release-en_US.xml:62(header)
msgid "See Fedora Core 5 Now"
msgstr "Fedora Core 5 ???????????????"
#: fc5-press-release-en_US.xml:63(para)
msgid "Fedora Core 5 has an exciting new look and feel. The menus and user interface have been carefully crafted by the interaction designers and desktop team. Take a tour at:"
msgstr "Fedora Core 5 ??????????????????????????????????????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:72(header)
msgid "Desktop"
msgstr "??????"
#: fc5-press-release-en_US.xml:73(para)
msgid "Fedora Core 5 features some great new desktop applications powered by Mono."
msgstr "Fedora Core 5 ???????????????????????????????????????????????????????????? Mono ?????????"
#: fc5-press-release-en_US.xml:76(para)
msgid "Tomboy is a note-taking tool; simple and handy, it has already changed the way that some Fedora users and developers work."
msgstr "Tomboy ??????????????????????????????????????????????????? Fedora ????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:83(para)
msgid "Thanks to F-Spot, managing digital photographs is easier than ever."
msgstr "F-Spot???????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:89(para)
msgid "If you are looking for something in a chat log, an email, or a web page you visited days ago, Beagle helps you find it."
msgstr "Beagle??????????????????????????????????????????????????????????????????????????????????????????????????????Beagle ????????????????????????"
#: fc5-press-release-en_US.xml:96(para)
msgid "We are also pleased to introduce Accelerated Indirect GLX (AIGLX) support in Fedora Core 5. Developed in partnership with the upstream Xorg community, AIGLX provides the foundation for GLX-accelerated effects on a standard desktop. While this can mean eye-catching effects, it also provides a platform for creating a high-performance, efficient, and elegant desktop."
msgstr "??????????????????????????? Fedora Core 5 ?????? Accelerated Indirect GLX (AIGLX) ???????????????????????? Xorg ?????????????????????AIGLX ??????????????????????????? GLX ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:106(para)
msgid "Power management has been improved thanks to GNOME Power Manager, included in this release. The GNOME screensaver package is included, with a new Fedora screensaver to accompany it."
msgstr "????????????????????????????????? GNOME Power Manager ???????????????GNOME Screensaver ????????????????????????????????? Fedora ???????????????????????????"
#: fc5-press-release-en_US.xml:117(para)
msgid "Integration, testing, and development was done to verify that suspend and hibernation features work with the largest number of hardware combinations that the Fedora community could get its hands on."
msgstr "?????????????????????????????????????????????????????????Fedora ???????????????????????????????????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:122(para)
msgid "We didn't forget our Apple hardware users and included support for the widely-used Broadcom 43xx wireless chipsets in the Fedora Core 5 kernel, which is based on the 2.6.16 kernel release."
msgstr "?????????????????? Apple ???????????????????????? Fedora Core 5 ????????????????????????????????? Broadcom 43xx ?????????????????????????????????????????? 2.6.16 ????????????"
#: fc5-press-release-en_US.xml:133(para)
msgid "Fedora Core 5 also features updated versions of old favorites. The latest in the Firefox 1.5 series offers improvements in speed, stability, security, and accessibility. The latest OpenOffice.org 2.0.2 introduces OpenDocument support, a new enhanced database frontend, a mail merge wizard, and better PDF export capability. The latest versions of both GNOME 2.14 and KDE 3.5 bring a many new features and improvements to the Fedora desktop."
msgstr "Fedora Core 5 ????????????\"????????????\"??????????????????Firefox 1.5 ???????????????????????????????????????????????????????????????????????????OpenOffice.org 2.0.2 ????????????????????? OpenDocument ?????????????????????????????????????????????????????????????????????????????? PDF ???????????????GNOME 2.14 ??? KDE 3.5 ??????????????? Fedora ????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:154(para)
msgid "Finally, the Fedora Core 5 desktop features new advances in multimedia applications built around the free Xiph.org codecs. Fedora is proud to say that Chris Montgomery, the founder of Xiph.org and the genius behind the Ogg family of codecs, is now a member of the Fedora Core team. We hope that Fedora and Xiph.org form a strong and lasting partnership to further the development of free media formats."
msgstr "?????????Fedora Core 5 ?????????????????? Xiph.org codecs ???????????????????????????????????????????????????Fedora ??????????????????Xiph.org ???????????? Chris Montgomery??????????????? Ogg ????????? codecs ????????????????????????????????? Fedora Core ????????????????????????????????????Fedora ??? Xiph.org ?????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:166(header)
msgid "Software Installation and Management"
msgstr "?????????????????????"
#: fc5-press-release-en_US.xml:167(para)
msgid "Anaconda, the Fedora Core installer, has been completely rewritten to present a more streamlined interface that matches the new look and feel of Fedora Core 5."
msgstr "Fedora Core ???????????? Anaconda ??????????????????????????????????????????????????? Fedora Core 5 ?????????????????????"
#: fc5-press-release-en_US.xml:172(para)
msgid "Fedora Core 5 also brings major advancements in software management with the introduction of Pirut, a graphical interface to replace system-config-packages. Pirut helps manage the large number of software packages available in Fedora Core and Extras repositories. The software package updater, Pup, helps users keep pace with Fedora's rapid improvements."
msgstr "Fedora Core 5 ????????? Pirut??????????????????????????????????????? system-config-packages?????????????????????????????????Pirut ????????????????????? Fedora Core ??? Extras ?????????????????????????????????Pup?????????????????????????????????????????? Fedora ????????????????????????"
#: fc5-press-release-en_US.xml:180(para)
msgid "For the first time, all of Fedora Core's tools for software installation and management share the same strong foundation: the package management utility Yum. This tight integration will lead to dramatic improvements in software management in future Fedora releases."
msgstr "Fedora ???????????????????????????????????????????????????????????????????????????????????????????????????????????? Yum???????????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:187(header)
msgid "Xen Virtualization"
msgstr "Xen ?????????"
#: fc5-press-release-en_US.xml:188(para)
msgid "Xen, the leading open source virtualization project, is included in Fedora Core 5. Our version of Xen is based on the latest Xen 3.0 development branch, with support for both 32-bit and 64-bit x86 hardware. Also included is the Xen guest install script from Fedora developers, which allows users to set up virtual machines."
msgstr "Xen??????????????????????????????????????????????????? Fedora Core 5 ??????????????? Xen ???????????????????????? Xen 3.0 ????????????????????? 32 ?????? 64 ????????????????????????????????? Fedora ?????????????????? Xen ????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:195(para)
msgid "Xen's advances in Fedora Core 5 represent a critical next step in the future of virtualization on Linux. Fedora has expanded our virtualization team with Chris Wright, one of the maintainers of the stable branch of 2.6 kernel releases, and Juan Quintela, as virtualization wizards. They are part of a large Red Hat team, headed by Brian Stein, responsible for making virtualization ubiquitous and seamless in Fedora."
msgstr "Fedora Core 5 ??? Xen ?????????????????? Linux ????????????????????????????????????Fedora ??????????????????????????? Chris Wright???2.6 ????????????????????????????????????????????? Juan Quintela??????????????????????????????????????? Red Hat ???????????????????????? Brian Stein ????????????????????????????????? Fedora ?????????????????????????????????"
#: fc5-press-release-en_US.xml:207(header)
msgid "Security"
msgstr "??????"
#: fc5-press-release-en_US.xml:208(para)
msgid "You can always expect interesting and exciting advancements in security from Fedora Core, and this release does not disappoint. Security Enhanced Linux (SELinux) is now using the reference policy, which makes it easier to create and maintain modular security policies. The introduction of a stack protector to GCC 4.1 makes it harder than ever for hackers to exploit buffer overflows, one of the most common security vulnerabilities."
msgstr "??????????????? Fedora Core ????????????????????????????????????????????????????????????????????????????????????Security Enhanced Linux (SELinux) ?????????????????????????????????????????????????????????????????????????????????GCC 4.1 ??????????????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:220(para)
msgid "Fedora has switched to using the reference policy for the SELinux security framework. This supports binary modules, allowing SELinux policies to move into individual packages. Developers can use this to ship site-specific policy customizations. Fedora Core also supports the Multi Category Security (MCS) SELinux policy by default, in addition to Type Enforcement (TE), Muti Level Security (MLS), and Role Base Access Control (RBAC) security policies. These gains in security continue to make Fedora Core one of the most secure general-use operating systems in the world. Find more facts at:"
msgstr "Fedora ???????????? SELinux ?????????????????????????????????????????????????????????????????? SELinux ?????????????????????????????????????????????????????????????????????????????????????????????Fedora Core ????????? Multi Category Security (MCS) SELinux???????????????????????? Type Enforcement (TE) ????????????Muti Level Security (MLS), ?????? Role Base Access Control (RBAC) ????????????????????????????????????????????? Fedora Core ???????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:238(para)
msgid "Linux Unified Key Support (LUKS) provides hard disk encryption support in Fedora Core 5; David Zeuthen of Red Hat, the HAL developer and maintainer, worked on the LUKS integration with HAL and GNOME, finishing just in time for the new Fedora Core release. Hard disk encryption provides one of the best physical security solutions -- protection of your data if your hard disk falls into the wrong hands."
msgstr "Linux Unified Key Support (LUKS) ??? Fedora Core 5 ??????????????????????????????Red Hat ??? David Zeuthen???HAL ???????????????????????????????????? LUKS ??? HAL ??? GNOME ???????????? Fedora Core ??????????????????????????????????????????????????????????????????????????????????????? -- ??????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:251(header)
msgid "Internationalization and Localization"
msgstr "?????????????????????"
#: fc5-press-release-en_US.xml:252(para)
msgid "Fedora contributors speak many different languages besides C, C++, Python, Java, and so on. We are also humans who speak the world's languages, and we want Fedora to support as many as possible."
msgstr "Fedora ???????????? C, C++, Python, Java ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Fedora ??????????????????????????????"
#: fc5-press-release-en_US.xml:257(para)
msgid "In Fedora Core 5, we have come closer to that goal by adopting SCIM, in place of IIIMF, as the input method of choice for internationalization. This and other advances allow Fedora to communicate with its many users better than ever before."
msgstr "??? Fedora Core 5 ?????????????????? SCIM????????????????????????????????????SCIM ????????? IIIMF??????????????????????????????????????????????????????????????????????????? Fedora ????????????????????????????????????"
#: fc5-press-release-en_US.xml:267(header)
msgid "Java"
msgstr "Java"
#: fc5-press-release-en_US.xml:268(para)
msgid "This release of Fedora Core represents another big step down the free Java path."
msgstr "???????????? Fedora Core ????????? Java ??????????????????????????????"
#: fc5-press-release-en_US.xml:272(para)
msgid "Through the introduction of the completely free software stack java-gcj-compat that runs native and bytecode Java, Fedora can now compile and run software written in Java without relying upon proprietary and closed Java machine implementations."
msgstr "???????????????????????????????????? java-gcj-compat?????????????????????????????????????????? Java ?????????Fedora ??????????????????????????? Java ??????????????????????????????????????? Java ?????????????????????"
#: fc5-press-release-en_US.xml:278(para)
msgid "The excellent Fedora Java development team of Red Hat and community hackers have built many popular Java-based or Java-using packages utilizing java-gcj-compat for this release. These packages, which include OpenOffice.org, Eclipse, Apache Tomcat, and Jakarta, are now compiled and run on a 100% free and open software stack."
msgstr "Red Hat ??????????????????????????????????????? Fedora Java ???????????????????????????????????????????????????????????? Java ????????? Java ???????????????????????? java-gcj-compat????????????????????? OpenOffice.org, Eclipse, Apache Tomcat ?????? Jakarta????????? 100% ?????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:285(para)
msgid "We included a complete set of packages and development goodies in Fedora Core 5 for Java technologies. Fedora Extras also has many Java applications: the popular BitTorrent utility Azureus, RSSowl, and others, all powered by gcj-java-compat."
msgstr "??? Fedora Core 5 ?????? Java ???????????????????????????????????????????????????Fedora Extras ??????????????? Java ?????????????????? BitTorrent ?????? Azureus, RSSowl ??????????????????????????? gcj-java-compat???"
#: fc5-press-release-en_US.xml:300(header)
msgid "Under the Hood"
msgstr "????????????"
#: fc5-press-release-en_US.xml:301(para)
msgid "The software repositories for the Fedora Legacy community maintenance project are available in this release. Disabled by default, these repositories can easily be re-enabled so that users can keep up with community patches after Fedora Core 5 leaves its official maintenance window."
msgstr "Fedora Legacy ???????????????????????????????????????????????????????????????????????????????????? Fedora Core 5 ?????????????????????????????????????????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:308(para)
msgid "Fedora Core 5 includes the latest releases of Apache HTTP Web Server 2.2, MySQL 5.0, and PostgreSQL 8.1 with various enhancements."
msgstr "Fedora Core 5 ????????????????????? Apache HTTP Web Server 2.2, MySQL 5.0, ??? PostgreSQL 8.1????????????????????????"
#: fc5-press-release-en_US.xml:324(para)
msgid "X.Org has been completely modularized and Fedora Core includes the latest X.Org X11R7.0 in this release. The new modular architecture of R7.0 enables easier driver upgrades and simplifies development, opening the way for rapid improvement in Linux graphics."
msgstr "X.Org ?????????????????????Fedora Core ?????????????????????????????? X.Org X11R7.0???R7.0 ???????????????????????????????????????????????????????????? Linux ??????????????????????????????????????????"
#: fc5-press-release-en_US.xml:330(para)
msgid "Gstreamer, the free desktop multimedia framework, has seen major improvements with the 0.10 release, and we made sure that applications such as Totem take full advantage of it."
msgstr "Gstreamer??????????????????????????????????????? 0.10 ????????????????????????????????? Totem ??????????????????????????????????????????"
#: fc5-press-release-en_US.xml:339(para)
msgid "We have the latest version of the GNU Compiler Collection, GCC 4.1, which provides security and performance improvements. We used GCC 4.1 to compile over 6,000 packages in the Fedora Core and Fedora Extras software repositories. GCJ, a critical part of our free Java environment, is included. There is also an implementation of the OpenMP parallel programming standard () for C, C++ and Fortran. Use the compiler switch -fopenmp to enable it."
msgstr "?????????????????????????????? GNU Compiler Collection, GCC 4.1?????????????????????????????????????????????????????? GCC 4.1 ????????? Fedora Core ??? Fedora Extras ????????????????????? 6,000 ???????????????GCJ????????? Java ?????????????????????????????????????????????????????????C, C++ ??? Fortran ??? OpenMP ????????????????????????()???????????????????????????????????????????????? -fopenmp ???????????????"
#: fc5-press-release-en_US.xml:349(para)
msgid "Other improvements are listed at:"
msgstr "????????????????????????"
#: fc5-press-release-en_US.xml:356(para)
msgid "Fedora Core 5 also offers technology previews for SystemTap and Frysk, cutting edge execution analysis tools that allow developers to troubleshoot performance issues to a degree never before possible."
msgstr "Fedora Core 5 ????????? SystemTap ??? Frysk ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
#: fc5-press-release-en_US.xml:370(header)
msgid "The Future of Fedora"
msgstr "Fedora ?????????"
#: fc5-press-release-en_US.xml:371(para)
msgid "Fedora contributors are already working toward the next release of Fedora Core, which features advancements in Xen, and new integration work from the Fedora Rendering and One Laptop Per Child (a.k.a. $100 laptop) projects. Stateless Linux work is also progressing steadily. We are working on the ability to support Fedora Extras and other custom software repositories during installation. As usual, work continues on new releases of the best and most robust free and open source software. See our roadmap at:"
msgstr "Fedora ?????????????????? Fedora Core ??????????????????????????????????????? Xen ?????????????????? Fedora Rendering ???????????? One Laptop Per Child(??? 100 ???????????????)????????????????????????Stateless Linux ????????????????????????????????????????????????????????? Fedora Extras ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
#. Put one translator per line, in the form of NAME , YEAR1, YEAR2.
#: fc5-press-release-en_US.xml:0(None)
msgid "translator-credits"
msgstr "Yuan Yijun 2006"
From fedora-docs-commits at redhat.com Sun Mar 19 15:47:44 2006
From: fedora-docs-commits at redhat.com (Tatsuo Sekine (tsekine))
Date: Sun, 19 Mar 2006 10:47:44 -0500
Subject: release-notes/po ja_JP.po,1.2,1.3
Message-ID: <200603191547.k2JFli6p009347@cvs-int.fedora.redhat.com>
Author: tsekine
Update of /cvs/docs/release-notes/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9329
Modified Files:
ja_JP.po
Log Message:
- All entities were expanded by hand.
- Catch up to the HEAD branch.
Index: ja_JP.po
===================================================================
RCS file: /cvs/docs/release-notes/po/ja_JP.po,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ja_JP.po 7 Mar 2006 21:41:33 -0000 1.2
+++ ja_JP.po 19 Mar 2006 15:47:36 -0000 1.3
@@ -1,8 +1,11 @@
+# translation of release notes to Japanese
+# Tatsuo "tatz" Sekine , 2005, 2006
+#
msgid ""
msgstr ""
"Project-Id-Version: ja_JP\n"
-"POT-Creation-Date: 2006-03-07 13:59-0500\n"
-"PO-Revision-Date: 2006-03-08 02:46+0900\n"
+"POT-Creation-Date: 2006-03-08 21:18+0900\n"
+"PO-Revision-Date: 2006-03-20 00:29+0900\n"
"Last-Translator: Tatsuo \"tatz\" Sekine \n"
"Language-Team: Japnese \n"
"MIME-Version: 1.0\n"
@@ -38,7 +41,7 @@
"This section contains information related to the X Window System "
"implementation provided with Fedora."
msgstr ""
-"??????????????????&FED; ???????????????????????? X Window System ???????????????????????????????????????"
+"??????????????????Fedora ???????????????????????? X Window System ???????????????????????????????????????"
#: en/Xorg.xml:11(title)
msgid "xorg-x11"
@@ -80,7 +83,7 @@
msgstr ""
"X.org X11R7 ?????????????????????????????? X.org ?????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"?????????????????????&FED; ???????????????Xorg ???????????????????????????????????????????????????????????????"
+"?????????????????????Fedora ???????????????Xorg ???????????????????????????????????????????????????????????????"
"???????????????????????? http://fedoraproject.org/wiki/Xorg/Modularization ???"
"?????????????????????"
@@ -248,8 +251,8 @@
"Linux systems."
msgstr ""
"X ???????????????????????????????????? app-defaults/ ????????????????????? "
-"%{_datadir}/X11/app-defaults/ ????????????&FC; &LOCALVER; ???"
-"????????? &RHEL; ?????????????????? /usr/share/X11/app-defaults "
+"%{_datadir}/X11/app-defaults/ ????????????Fedora Core 5 ???"
+"????????? Red Hat Enterprise Linux ?????????????????? /usr/share/X11/app-defaults "
"????????????????????????"
#: en/Xorg.xml:67(title)
@@ -319,7 +322,7 @@
"com/docs/release-notes/\">http://fedora.redhat.com/docs/release-notes/ to view the latest release notes for Fedora Core 5."
msgstr ""
-"???????????????????????????????????????????????????????????????????????????&FC; &LOCALVER; ???????????????"
+"???????????????????????????????????????????????????????????????????????????Fedora Core 5 ???????????????"
"????????????????????????????????? http://fedora.redhat.com/docs/release-notes/ ?????????????????????"
"?????????"
@@ -343,7 +346,7 @@
"To find out more general information about Fedora, refer to the following "
"Web pages:"
msgstr ""
-"&FED; ??????????????????????????????????????????????????????????????? web ?????????????????????????????????"
+"Fedora ??????????????????????????????????????????????????????????????? web ?????????????????????????????????"
"??????"
#: en/Welcome.xml:19(para)
@@ -375,7 +378,7 @@
"Participate in the Fedora Project (http://fedoraproject.org/wiki/HelpWanted)"
msgstr ""
-"&FED; ?????????????????????????????? (http://fedoraproject.org/wiki/HelpWanted)"
#: en/Welcome.xml:31(para)
@@ -383,7 +386,7 @@
"About the Fedora Project (http://fedora.redhat.com/About/)"
msgstr ""
-"&FED; ?????????????????????????????? (http://fedora.redhat.com/About/)"
#: en/WebServers.xml:8(title)
@@ -403,7 +406,7 @@
"Fedora Core now includes version 2.2 of the Apache HTTP Server. This release "
"brings a number of improvements over the 2.0 series, including:"
msgstr ""
-"Apache HTTP ??????????????????????????? 2.2 ??? &FC; ???????????????????????????????????????????????????"
+"Apache HTTP ??????????????????????????? 2.2 ??? Fedora Core ???????????????????????????????????????????????????"
"???????????????????????????2.0 ??????????????????????????????????????????????????????????????????"
#: en/WebServers.xml:15(para)
@@ -427,13 +430,10 @@
msgstr "??????????????????????????????????????????(mod_proxy_balance)"
#: en/WebServers.xml:24(para)
-#, fuzzy
msgid ""
"large file support for 32-bit platforms (including support for serving files "
"larger than 2GB)"
-msgstr ""
-"32 ?????????????????????????????????????????????????????????????????????????????? (2Gb ????????????????????????"
-"??????????????????)"
+msgstr "32 ?????????????????????????????????????????????????????????????????????????????? (2GB ??????????????????????????????????????????)"
#: en/WebServers.xml:27(para)
msgid ""
@@ -510,7 +510,7 @@
"Version 5.1 of PHP is now included in Fedora Core. This release brings a "
"number of improvements since PHP 5.0, including:"
msgstr ""
-"PHP ?????????????????? 5.1 ??? &FC; ?????????????????????????????????????????? PHP 5.0 ???????????????"
+"PHP ?????????????????? 5.1 ??? Fedora Core ?????????????????????????????????????????? PHP 5.0 ???????????????"
"????????????????????????????????????????????????"
#: en/WebServers.xml:58(para)
@@ -609,9 +609,8 @@
msgstr "????????????????????????????????? Fedora Extras ??????????????????????????????????????????"
#: en/Virtualization.xml:8(title)
-#, fuzzy
msgid "Virtualization"
-msgstr "??????????????????"
+msgstr "?????????"
#: en/Virtualization.xml:9(para)
msgid ""
@@ -619,21 +618,17 @@
"emphasis>. Xen 3.0 is integrated within Fedora Core 5 in the installer. "
"Refer to http://"
"fedoraproject.org/wiki/Tools/Xen for more information about Xen."
-msgstr ""
+msgstr "Fedora Core ?????????????????? Xen ??????????????????????????????Xen 3.0 ??? Fedora Core 5 ??????????????????????????????????????????????????????Xen ???????????????????????? http://fedoraproject.org/wiki/Tools/Xen ??????????????????????????????"
#: en/Virtualization.xml:12(title)
-#, fuzzy
msgid "No PowerPC Support"
-msgstr "PowerPC ???????????????????????????"
+msgstr "PowerPC ?????????????????????????????????"
#: en/Virtualization.xml:13(para)
-#, fuzzy
msgid ""
"Xen is not supported on the PowerPC "
"architecture in Fedora Core 5."
-msgstr ""
-"&FC; &LOCALVER; ??? PowerPC ??????????????????????????????Xen ??? kdump ????????????????????????"
-"?????????????????????"
+msgstr "Fedora Core 5 ??? PowerPC ??????????????????????????????Xen ?????????????????????????????????"
#. 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.
@@ -697,7 +692,7 @@
"This section highlights changes and additions to the various GUI server and "
"system configuration tools in Fedora Core."
msgstr ""
-"??????????????????&FC; ??????????????? ???????????????????????????????????? GUI ??????????????????????????????"
+"??????????????????Fedora Core ??????????????? ???????????????????????????????????? GUI ??????????????????????????????"
"????????????????????????"
#: en/ServerTools.xml:11(title)
@@ -901,7 +896,7 @@
#: en/Security.xml:9(para)
msgid "This section highlights various security items from Fedora Core."
-msgstr "???????????? &FC; ???????????????????????????????????????????????????????????????"
+msgstr "???????????? Fedora Core ???????????????????????????????????????????????????????????????"
#: en/Security.xml:10(para)
msgid ""
@@ -910,7 +905,7 @@
"fedoraproject.org/wiki/Security\">http://fedoraproject.org/wiki/Security."
msgstr ""
-"&FED; ?????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"Fedora ?????????????????????????????????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????? http://fedoraproject.org/wiki/Security ????????????????????????"
@@ -936,7 +931,7 @@
"pam_stack ????????????????????????????????????????????????"
"pam_stack ?????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"????????????????????????????????????????????????&FC; ??? PAM ???????????????????????????????????? "
+"????????????????????????????????????????????????Fedora Core ??? PAM ???????????????????????????????????? "
"pam_stack ????????????????????????????????????????????????"
#: en/Security.xml:18(title)
@@ -953,7 +948,7 @@
"pam_stack module is not used. Refer to the .rpmnew "
"files for the actual changes needed."
msgstr ""
-"???????????????????????? &FC; ?????????????????????????????????????????????????????????????????????????????????"
+"???????????????????????? Fedora Core ?????????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????????????????????????????????????????????????????"
"????????????????????? .rpmnew ??????????????????????????????"
"??????????????????????????????????????????pam_stack ???????????????????????????"
@@ -1073,7 +1068,7 @@
"making remote exploitation very difficult. The fstack-protector "
"feature does not protect against heap-based buffer overflows."
msgstr ""
-"???????????????????????????&FC; ??? Extras ?????????????????????????????????????????????????????? "
+"???????????????????????????Fedora Core ??? Extras ?????????????????????????????????????????????????????? "
"fstack-protecter ?????????????????????????????????????????????????????????????????????"
"??????????????????fstack-protector ???????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
@@ -1091,10 +1086,10 @@
"\">http://www.research.ibm.com/trl/projects/security/ssp/. This "
"feature is available as part of the GCC 4.1 compiler used in Fedora Core 5."
msgstr ""
-"??????????????? IBM ProPolice/SSP ?????????????????? &RH; ???????????????????????????????????????"
+"??????????????? IBM ProPolice/SSP ?????????????????? Red Hat ???????????????????????????????????????"
"ProPolice/SSP ???????????????????????? http://www.research.ibm.com/trl/projects/security/"
-"ssp/ ????????????????????????????????????????????? &FC; &LOCALVER; ????????????????????? "
+"ssp/ ????????????????????????????????????????????? Fedora Core 5 ????????????????????? "
"GCC 4.1 ?????????????????????????????????????????????????????????"
#: en/Security.xml:71(para)
@@ -1134,7 +1129,7 @@
#: en/ProjectOverview.xml:8(title)
msgid "Fedora Project - Freedom to the Core"
-msgstr "Fedora Project - Core ??????????????????"
+msgstr "Fedora ?????????????????? - Core ??????????????????"
#: en/ProjectOverview.xml:9(para)
msgid ""
@@ -1150,12 +1145,12 @@
"system more in line with the ideals of free software and more appealing to "
"the open source community."
msgstr ""
-"Fedora Project ???????????????Linux ??????????????????????????????????????????????????????????????????"
+"Fedora ?????????????????????????????????Linux ??????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"?????????????????????????????????????????????????????????????????????????????????????????? &FC; ???????????????"
+"?????????????????????????????????????????????????????????????????????????????????????????? Fedora Core ???????????????"
"???????????????????????????????????????(http://fedora.redhat.com/About/schedule/ ??????????????????)???"
-"???????????????????????????????????????????????????Red Hat ???????????????????????????????????? &FC; ??????"
+"???????????????????????????????????????????????????Red Hat ???????????????????????????????????? Fedora Core ??????"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
@@ -1163,7 +1158,7 @@
#: en/ProjectOverview.xml:10(para)
msgid "For more information, refer to the Fedora Project website:"
-msgstr "?????????????????????Fedora Project ??? Web ???????????????????????????????????????"
+msgstr "?????????????????????Fedora ????????????????????? Web ???????????????????????????????????????"
#: en/ProjectOverview.xml:12(ulink)
msgid "http://fedora.redhat.com/"
@@ -1208,7 +1203,7 @@
"??? For users of Fedora Core releases"
msgstr ""
"fedora-list at redhat.com "
-"— &FC; ?????????????????????????????????"
+"— Fedora Core ?????????????????????????????????"
#: en/ProjectOverview.xml:25(para)
msgid ""
@@ -1216,7 +1211,7 @@
"com ??? For testers of Fedora Core test releases"
msgstr ""
"fedora-test-list at redhat."
-"com — &FC; ??????????????????????????????????????????"
+"com — Fedora Core ??????????????????????????????????????????"
#: en/ProjectOverview.xml:29(para)
msgid ""
@@ -1265,7 +1260,7 @@
"Messaging. With it, you may have conversations with multiple people in an "
"open channel, or chat with someone privately one-on-one."
msgstr ""
-"Fedora Project ?????????IRC (Internet Relay Chat) ?????????????????????????????????IRC ??????"
+"Fedora ???????????????????????????IRC (Internet Relay Chat) ?????????????????????????????????IRC ??????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"?????????????????????????????????????????????"
@@ -1276,7 +1271,7 @@
"IRC network. Refer to the Freenode website (http://www.freenode.net/) for more information."
msgstr ""
-"IRC ?????????????????? &FP; ?????????????????????????????????freenode IRC ??????????????????????????????"
+"IRC ?????????????????? Fedora ???????????????????????????????????????????????????freenode IRC ??????????????????????????????"
"????????????????????????????????????????????? freenode ?????????????????? (http://www.freenode.net/) ??????????????????????????????"
@@ -1289,8 +1284,8 @@
"the project, and at http://fedoraproject.org/wiki/Communicate."
msgstr ""
-"Fedora Project ???????????? #fedora ???????????????????????? Fedora Project "
-"???????????? #fedora-devel ????????????????????????????????????????????????????????????"
+"Fedora ????????????????????????????????? #fedora ???????????????????????? Fedora ??????????????????"
+"??????????????? #fedora-devel ????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"???????????????????????? http://fedoraproject.org/wiki/Communicate ????????????????????????"
@@ -1314,7 +1309,7 @@
"Fedora Foundation or Red Hat has no control over the Fedora Project IRC "
"channels or their content."
msgstr ""
-"Fedora Foundation ??? Red Hat ??? Fedora Project ??? IRC ?????????????????????????????????"
+"Fedora Foundation ??? Red Hat ??? Fedora ????????????????????? IRC ?????????????????????????????????"
"?????????????????????????????????????????????"
#: en/Printing.xml:8(title)
@@ -1362,7 +1357,7 @@
msgstr ""
"/etc/hotplug, /etc/hotplug.d, "
"/etc/dev.d ??????????????????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????????"
+"??????????????????????????????????????????????????? Fedora Core ??????????????????????????????????????????????????????"
"??????????????????????????????????????? udev ????????????????????????????????????"
"?????????????????????????????? http://www.reactivated.net/writing_udev_rules."
@@ -1473,7 +1468,7 @@
"\">http://wiki.dovecot.org/UpgradingDovecot for more information on "
"the changes."
msgstr ""
-"&FC; ??????????????????????????????????????????????????? dovecot IMAP ???????????????"
+"Fedora Core ??????????????????????????????????????????????????? dovecot IMAP ???????????????"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????? http://wiki.dovecot.org/"
@@ -1494,7 +1489,7 @@
msgstr ""
"kudzu ????????????????????????libkudzu ??????????????????????????? "
"/etc/sysconfig/hwconf ???????????????????????????????????????????????????????????? "
-"&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"Fedora Core ????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"?????????????????????????????????????????? HAL ??????????????????????????????????????????????????????????????????"
"???????????????HAK ???????????????????????? http://freedesktop.org/wiki/Software/hal ??????????????????"
@@ -1514,7 +1509,7 @@
"which provides similar functionality."
msgstr ""
"fstab-sync ??????????????????????????????????????????????????????????????????????????????"
-"??????????????????&FC; ?????????????????????????????????????????????????????????????????????fstab-"
+"??????????????????Fedora Core ?????????????????????????????????????????????????????????????????????fstab-"
"sync ?????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????? /etc/fstab ???????????????"
"?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? "
@@ -1552,9 +1547,9 @@
"build against mozilla-devel, however it will be removed in a "
"future release of Fedora Core."
msgstr ""
-"Mozilla ????????????????????????????????????????????????&FC; 5 ???"
+"Mozilla ????????????????????????????????????????????????Fedora Core 5 ???"
"??????????????????????????????????????? mozilla-devel ?????????????????????????????????"
-"??????????????????????????????????????????????????? &FC; ??????????????????????????????????????????????????????"
+"??????????????????????????????????????????????????? Fedora Core ??????????????????????????????????????????????????????"
"??????"
#: en/PackageNotes.xml:72(title)
@@ -3359,7 +3354,7 @@
"release of Fedora Core."
msgstr ""
"?????????????????????9?????????????????????????????????????????????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????????????????? &FC; ??????????????????????????????????????????"
+"??????????????????????????????????????????????????????????????? Fedora Core ??????????????????????????????????????????"
"????????????????????????????????????"
#: en/OverView.xml:14(title)
@@ -3565,7 +3560,7 @@
"Fedora Core 5 now uses gnome-mount, a more efficient mechanism "
"that replaces fstab-sync, and uses HAL to handle mounting."
msgstr ""
-"&FC; &LOCALVER; ????????? fstab-sync ?????????????????????????????????????????????"
+"Fedora Core 5 ????????? fstab-sync ?????????????????????????????????????????????"
"??? gnome-mount ????????????????????????????????????????????? HAL ??????????????????"
#: en/OverView.xml:66(para)
@@ -3596,8 +3591,8 @@
"API to use Xen virtualization capabilities."
msgstr ""
"Xen ??????????????????????????????????????????????????????????????????"
-"&FC; ?????? Xen ??????????????????????????????????????????????????????"
-"???????????????????????????????????????????????????????????????????????????????????????????????????&FED; ??????"
+"Fedora Core ?????? Xen ??????????????????????????????????????????????????????"
+"???????????????????????????????????????????????????????????????????????????????????????????????????Fedora ??????"
"???????????????????????????????????????????????????????????????????????? gnome-applet-vm ??????Xen ????????????????????????????????? API ?????????????????????????????? "
"libvirt (http://libvirt.org/"
@@ -3790,7 +3785,7 @@
"url=\"http://fedoraproject.org/wiki/RoadMap\">http://fedoraproject.org/wiki/"
"RoadMap."
msgstr ""
-" &FED; ????????????????????????????????????????????? http://fedoraproject.org/wiki/RoadMap ?????????????????????"
"??????"
@@ -4109,7 +4104,7 @@
"including playback, recording and editing. Additional packages are available "
"through the Fedora Extras repository."
msgstr ""
-"&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"Fedora Core ????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"????????????????????????????????????????????? Fedora Extras ??????????????????????????????????????????"
#: en/Multimedia.xml:11(title)
@@ -4127,10 +4122,10 @@
"formats. Additional programs are available from third parties to handle "
"other formats."
msgstr ""
-"&FC; ???????????????????????? Rhythm Box, "
+"Fedora Core ???????????????????????? Rhythm Box, "
"Totem, Helix Player ???"
"?????????????????????????????????????????????????????????????????????????????????????????? "
-"XMMS ????????????????????????????????????????????????????????? &FC; "
+"XMMS ????????????????????????????????????????????????????????? Fedora Core "
"????????? Fedora Extras ??????????????????????????????????????????GNOME???KDE ?????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"?????????????????????????????????????????????????????????????????????"
@@ -4145,7 +4140,7 @@
"website at http://www.alsa-"
"project.org/."
msgstr ""
-"?????? &FC; ??? Advanced Linux Sound Architecture (ALSA) ??????????????????????????????"
+"?????? Fedora Core ??? Advanced Linux Sound Architecture (ALSA) ??????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????? Linux ??????????????????????????????????????????"
"????????????????????????????????????????????????????????? ALSA ????????????????????????????????????????????????"
@@ -4168,7 +4163,7 @@
"formats and how to use them, refer to the Xiph.Org Foundation's web site at "
"http://www.xiph.org/."
msgstr ""
-"&FED; ??? Ogg ?????????????????????????????????????????????Vorbis ??????????????????Theora ????????????"
+"Fedora ??? Ogg ?????????????????????????????????????????????Vorbis ??????????????????Theora ????????????"
"Speex ??????????????????FLAC ?????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
@@ -4191,7 +4186,7 @@
"ForbiddenItems\">http://fedoraproject.org/wiki/ForbiddenItems."
msgstr ""
"MP3 ????????? MPEG (DVD) ?????????????????????????????????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????????&FC; ????????? Fedora Extras ?????? MP3 ??? "
+"??????????????????????????????????????????????????????Fedora Core ????????? Fedora Extras ?????? MP3 ??? "
"DVD ?????????????????????????????????????????????????????????????????????????????????Flash "
"Player ??? Real Player ?????????????????????"
"????????????????????????????????????????????????????????????????????????????????????????????????????????? "
@@ -4213,10 +4208,10 @@
"tasks. Console tools include cdrecord, readcd, "
"mkisofs, and other typical Linux applications."
msgstr ""
-"&FC; ??? Fedora Extras ?????? CD ??? DVD ????????????????????????????????????????????????????????????"
+"Fedora Core ??? Fedora Extras ?????? CD ??? DVD ????????????????????????????????????????????????????????????"
"GNOME ???????????? Nautilus ???????????????????????????????????????"
"?????????????????????????????????Fedora Extras ?????? gnomebaker ???????????? "
-"graveman ???????????????&FC; ???????????? xcdroast ????????????"
+"graveman ???????????????Fedora Core ???????????? xcdroast ????????????"
"??????KDE ??????????????????????????????????????????????????????????????????????????????????????? "
"k3b ????????????????????????????????????????????????????????????????????? "
"cdrecord, readcd, mkisofs, ???????????????"
@@ -4260,12 +4255,12 @@
"Extras, and additional plugins may be available from third parties to add "
"even greater capabilities."
msgstr ""
-"&FC; ??? Fedora Extras ??????????????????????????????????????????????????????????????????????????????"
+"Fedora Core ??? Fedora Extras ??????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????????????????????????????????????????????????????"
"gstreamer ?????????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????? "
-"&FC; ??? Fedora Extras ?????????????????????????????????????????????????????????????????????????????????"
+"Fedora Core ??? Fedora Extras ?????????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????????????????????????????"
#: en/Legacy.xml:8(title)
@@ -4303,7 +4298,7 @@
#: en/Legacy.xml:13(para)
msgid "Red Hat Linux 7.3 and 9"
-msgstr "Red Hat Linux 7.3 and 9"
+msgstr "Red Hat Linux 7.3, 9"
#: en/Legacy.xml:16(para)
msgid "Fedora Core 1, 2, and 3"
@@ -4322,7 +4317,7 @@
"Fedora Legacy ?????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"???????????? 3 ????????? Core ?????????????????? 2 ?????????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????? &FC; 4 ???????????????????????????????????????????????????"
+"??????????????????????????????????????????????????? Fedora Core 4 ???????????????????????????????????????????????????"
"??????????????? Fedora Core 7 test2 ??????????????????????????????????????????????????????(Fedora "
"Core ????????? Fedora Legacy ????????????????????????)??? 18 ??????????????????????????????????????????"
"????????????"
@@ -4378,7 +4373,7 @@
"This section covers changes and important information regarding the kernel "
"in Fedora Core 5."
msgstr ""
-"??????????????????&FC; &LOCALVER; ????????????????????????????????????????????????????????????????????????"
+"??????????????????Fedora Core 5 ????????????????????????????????????????????????????????????????????????"
"?????????????????????"
#: en/Kernel.xml:11(title)
@@ -4393,9 +4388,9 @@
"for-line equivalent to the so-called vanilla kernel "
"from the kernel.org web site:"
msgstr ""
-"?????????????????????????????????????????? 2.6 ??????????????????????????????????????????????????????&FC; ???"
+"?????????????????????????????????????????? 2.6 ??????????????????????????????????????????????????????Fedora Core ???"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"??????&FC; ?????????????????? kernel.org ?????????????????????????????????"
+"??????Fedora Core ?????????????????? kernel.org ?????????????????????????????????"
"??????????????????????????????"
#: en/Kernel.xml:14(ulink)
@@ -4439,7 +4434,7 @@
"????????????????????????????????????????????????????????????????????? http://wiki.kernelnewbies.org/LinuxChanges ???????????????????????????????????????????????????/?????????????????? http://kernel.org/git ???????????????????????????&FED; ??????"
+"kernel.org/git\">http://kernel.org/git ???????????????????????????Fedora ??????"
"???????????? Linus ??????????????????????????????????????????"
#: en/Kernel.xml:24(para)
@@ -4447,7 +4442,7 @@
"Customizations made for the Fedora version are available from http://cvs.fedora.redhat.com ."
msgstr ""
-"&FED; ??????????????????????????????????????????????????? http://cvs.fedora.redhat.com ???????????????????????????"
#: en/Kernel.xml:27(title)
@@ -4456,7 +4451,7 @@
#: en/Kernel.xml:31(para)
msgid "Fedora Core 5 includes the following kernel builds:"
-msgstr "&FC; &LOCALVER; ????????????????????????????????????????????????"
+msgstr "Fedora Core 5 ????????????????????????????????????????????????"
#: en/Kernel.xml:34(para)
msgid ""
@@ -4474,24 +4469,16 @@
#: en/Kernel.xml:37(para)
msgid ""
"Virtual kernel hypervisor for use with the Xen emulator package. Configured "
-"sources are available in the kernel-xen-hypervisor-devel-<"
-"version>.<arch>.rpm package."
-msgstr ""
-"Xen ????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"??? kernel-xen-hypervisor-devel-???????????????.?????????????????????.rpm ??????"
-"????????????????????????????????????"
+"sources are available in the kernel-xen0-devel-<version>.<"
+"arch>.rpm package."
+msgstr "Xen ??????????????????????????????????????????????????????????????????????????????????????????????????????????????? kernel-xen0-devel-???????????????.?????????????????????.rpm ??????????????????????????????????????????"
#: en/Kernel.xml:40(para)
msgid ""
"Virtual kernel guest for use with the Xen emulator package. Configured "
-"sources are available in the kernel-xen-guest-devel-<version>."
-"<arch>.rpm package."
-msgstr ""
-"Xen ??????????????????????????????????????????????????????????????????????????????????????????????????? "
-"kernel-xen-guest-devel-???????????????."
-"?????????????????????.rpm ??????????????????????????????"
-"????????????"
+"sources are available in the kernel-xenU-devel-<version>.<"
+"arch>.rpm package."
+msgstr "Xen ??????????????????????????????????????????????????????????????????????????????????????????????????? kernel-xenU-devel-???????????????.?????????????????????.rpm ??????????????????????????????????????????"
#: en/Kernel.xml:43(para)
msgid ""
@@ -4507,18 +4494,14 @@
#: en/Kernel.xml:46(para)
msgid ""
"You may install sources for all kernel flavors at the same time. The files "
-"are installed in the /usr/src/kernels/<version>-[xen-hypervisor|"
-"xen-guest|kdump]-<arch>/ tree. Use the following command:"
-msgstr ""
-"??????????????????????????????????????????????????????????????????????????????????????????????????? "
-"/usr/src/kernels/???????????????-[xen-"
-"hypervisor/xen-guest/kdump]-?????????????????????/ ????????????????????????????????????????????????????????????????????????????????????????????????"
+"are installed in the /usr/src/kernels/<version>-[xen0|xenU|"
+"kdump]-<arch>/ tree. Use the following command:"
+msgstr "??????????????????????????????????????????????????????????????????????????????????????????????????? /usr/src/kernels/???????????????-[xen0/xenU/kdump]-?????????????????????/ ????????????????????????????????????????????????????????????????????????????????????????????????"
#: en/Kernel.xml:47(screen)
#, no-wrap
-msgid "su -c 'yum install kernel-{xen,hypervisor,xen-guest,kdump}-devel'"
-msgstr "su -c 'yum install kernel-{xen,hypervisor,xen-guest,kdump}-devel'"
+msgid "su -c 'yum install kernel-{xen0,xenU,kdump}-devel'"
+msgstr "su -c 'yum install kernel-{xen0,xenU,kdump}-devel'"
#: en/Kernel.xml:48(para)
msgid ""
@@ -4537,7 +4520,7 @@
"There is no separate SMP kernel available for the x86_64 architecture in "
"Fedora Core 5."
msgstr ""
-"&FC; &LOCALVER; ??? x86_64 ??????????????????????????????SMP ???????????????????????????????????????"
+"Fedora Core 5 ??? x86_64 ??????????????????????????????SMP ???????????????????????????????????????"
"???????????????"
#: en/Kernel.xml:54(title)
@@ -4549,7 +4532,7 @@
"There is no support for Xen or kdump for the PowerPC architecture in Fedora "
"Core 5."
msgstr ""
-"&FC; &LOCALVER; ??? PowerPC ??????????????????????????????Xen ??? kdump ????????????????????????"
+"Fedora Core 5 ??? PowerPC ??????????????????????????????Xen ??? kdump ????????????????????????"
"?????????????????????"
#: en/Kernel.xml:59(title)
@@ -4585,7 +4568,7 @@
msgstr ""
"Linux ?????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????/usr/src/linux/ ??????????????????????????????????????????????????????"
-"??????????????????????????????????????????????????????????????????????????????????????????????????????&FC; ???"
+"??????????????????????????????????????????????????????????????????????????????????????????????????????Fedora Core ???"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"?????????????????????????????????????????????????????????????????????????????????"
@@ -4609,7 +4592,7 @@
"versions. Instead, configured sources are available, as described in this "
"kernel flavors section."
msgstr ""
-"&FC; &LOCALVER; ?????????????????????????????????????????????????????? kernel-"
+"Fedora Core 5 ?????????????????????????????????????????????????????? kernel-"
"source ???????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????"
@@ -4635,7 +4618,7 @@
"them in the kernel .src.rpm package. To create an exploded source tree from "
"this file, perform the following steps:"
msgstr ""
-"&FC; ????????????????????????kernel.src.rpm ??????"
+"Fedora Core ????????????????????????kernel.src.rpm ??????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????????????????"
@@ -4767,7 +4750,7 @@
"Issue the following command to place the desired configuration file in the "
"proper place for building:"
msgstr ""
-"&FC; &LOCALVER; ??????????????????????????????????????????????????? configs/configs/ ?????????????????????????????????????????????????????????i686 SMP ??????????????????????????? "
"configs/kernel-<version>-i686-smp.config ????????????"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
@@ -4904,7 +4887,7 @@
"version>' command instead. The yum command "
"automatically removes dependent packages, if necessary."
msgstr ""
-"&FC; &LOCALVER; ??????Global File System (GFS) ????????????????????????????????????????????????"
+"Fedora Core 5 ??????Global File System (GFS) ????????????????????????????????????????????????"
"???????????????????????????GFS ?????????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"????????????????????????????????????????????????????????? su -c 'yum remove kernel-<"
@@ -4920,7 +4903,7 @@
"The GFS kernel modules are not built for the PowerPC architecture in Fedora "
"Core 5."
msgstr ""
-"&FC; &LOCALVER; ?????? PowerPC ??????????????????????????????GFS ????????????????????????????????????"
+"Fedora Core 5 ?????? PowerPC ??????????????????????????????GFS ????????????????????????????????????"
"?????????????????????"
#: en/Java.xml:8(title)
@@ -4935,7 +4918,7 @@
"capable of building and running many useful programs that are written in the "
"Java programming language."
msgstr ""
-"?????? &FC; ?????????????????????java-gcj-compat ????????????????????????"
+"?????? Fedora Core ?????????????????????java-gcj-compat ????????????????????????"
"??????????????? Java ???????????????????????????java-gcj-compat ????????????"
"??????????????????Java ??????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????"
@@ -4978,7 +4961,7 @@
"role=\"strong\">Eclipse, and Apache "
"Tomcat."
msgstr ""
-"?????? &FED; ??????????????????????????? Java ???????????????????????????????????????????????? "
+"?????? Fedora ??????????????????????????? Java ???????????????????????????????????????????????? "
"java-gcj-compat ???????????????????????????????????????????????????????????? "
"OpenOffice.org Base, Eclipse, Apache Tomcat ??????????????????"
@@ -5101,7 +5084,7 @@
"\"strong\">Anaconda (the Fedora Core installation program) and "
"installing Fedora Core 5 in general."
msgstr ""
-"??????????????????Anaconda???&FC; ?????????????????????????????????????????? &FC; &LOCALVER; ??????"
+"??????????????????Anaconda???Fedora Core ?????????????????????????????????????????? Fedora Core 5 ??????"
"??????????????????????????????????????????????????????????????????????????????"
#: en/Installer.xml:11(title)
@@ -5119,7 +5102,7 @@
"about obtaining and using the torrent file, refer to http://torrent.fedoraproject.org/."
msgstr ""
-"?????? &FC; &LOCALVER; ??? DVD ISO ??????????????????????????????????????????????????????????????????"
+"?????? Fedora Core 5 ??? DVD ISO ??????????????????????????????????????????????????????????????????"
"???????????????????????????????????? 2GB ????????????????????????????????????????????????????????????????????????"
"????????????????????????????????????wget ?????????????????? 1.9.1-16 ?????????"
"curl???????????? ncftpget ????????????????????????"
@@ -5147,7 +5130,7 @@
"??????????????????????????????????????????CD???DVD??????????????????????????? ISO ???????????????NFS ??? "
"ISO ????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"???????????? Fedora Project ??????????????????????????????????????????????????????????????????????????????"
+"???????????? Fedora ????????????????????????????????????????????????????????????????????????????????????????????????"
"?????? CD ????????????????????????????????????????????????????????????boot: ?????????"
"????????? linux mediacheck ??????????????????????????????"
@@ -5205,7 +5188,7 @@
"Memtest86 memory testing continues "
"until the Esc key is pressed."
msgstr ""
-"&FC; ????????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"Fedora Core ????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"????????? boot: ?????????????????? memtest86 ???????????????"
"????????????????????????Memtest86????????????????????????????????????"
"?????????????????????????????? Anaconda ??????????????????????????????"
@@ -5234,7 +5217,7 @@
"installer automatically. If you prefer to use the text-based installer, type "
"linux text at the boot: prompt."
msgstr ""
-"&FC; &LOCALVER; ???????????????????????? FTP???HTTP ???????????????????????????????????????????????????"
+"Fedora Core 5 ???????????????????????? FTP???HTTP ???????????????????????????????????????????????????"
"??????????????????????????????????????? RAM ???????????????????????????????????????????????? 1 ????????????"
"?????????????????????????????????????????????????????????????????????????????????192MiB ????????? RAM ??????"
"????????????????????????????????????????????????????????? 1 ???????????????????????????????????????????????????"
@@ -5310,7 +5293,7 @@
"Serial mice are no longer formally supported in Anaconda or Fedora Core."
msgstr ""
-"&FC; ????????? Anaconda?????????????????????????????????????????????"
+"Fedora Core ????????? Anaconda?????????????????????????????????????????????"
"???????????????????????????????????????"
#: en/Installer.xml:76(para)
@@ -5406,7 +5389,7 @@
"Core from CD-ROM. If this happens, restart the installation process and add "
"the following option to the boot command line:"
msgstr ""
-"Sony VAIO ?????????????????????????????????????????????&FC; ??? CD-ROM ?????????????????????????????????"
+"Sony VAIO ?????????????????????????????????????????????Fedora Core ??? CD-ROM ?????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"?????????????????????????????????????????????????????????????????????????????????"
@@ -5421,7 +5404,7 @@
"configured the first time Fedora Core is booted."
msgstr ""
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
-"???????????????????????????????????????&FC; ??????????????????????????????????????????"
+"???????????????????????????????????????Fedora Core ??????????????????????????????????????????"
#: en/Installer.xml:116(para)
msgid ""
@@ -5521,7 +5504,7 @@
"This section includes information related to the support of various "
"languages under Fedora Core."
msgstr ""
-"??????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????????"
+"??????????????????Fedora Core ??????????????????????????????????????????????????????????????????????????????????????????"
#: en/I18n.xml:11(title)
msgid "Input Methods"
@@ -5928,9 +5911,9 @@
"emphasis>>Add/Remove Software from the main desktop "
"menu."
msgstr ""
-"&FC; ??? Fedora Extras ?????????????????????????????????????????????????????????????????????????????????"
-"&FC; ??? GNOME ?????? (gnome-games ???????????????)??????????????????????????????"
-"????????????&FC; ??? Fedora Extras ?????????????????????????????????????????????????????????????????????"
+"Fedora Core ??? Fedora Extras ?????????????????????????????????????????????????????????????????????????????????"
+"Fedora Core ??? GNOME ?????? (gnome-games ???????????????)??????????????????????????????"
+"????????????Fedora Core ??? Fedora Extras ?????????????????????????????????????????????????????????????????????"
"????????????????????????????????????????????? ????????????????????????>"
"???????????????????????????????????? ??????????????????????????????"
@@ -5947,7 +5930,7 @@
"Fedora Extras provides a repository of packages that complement Fedora Core. "
"This volunteer-based community effort is part of the larger Fedora Project."
msgstr ""
-"Fedora Extras ??? &FC; ?????????????????????????????????????????????????????????????????????????????????"
+"Fedora Extras ??? Fedora Core ?????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????? Fedora ????????????????????????????????????"
#: en/Extras.xml:13(title)
@@ -5959,7 +5942,7 @@
"Fedora systems automatically use both the Fedora Core and Fedora Extras "
"repositories to install and update software."
msgstr ""
-"Fedora ??????????????????????????????????????????????????????????????????????????????&FC; ??? Fedora "
+"Fedora ??????????????????????????????????????????????????????????????????????????????Fedora Core ??? Fedora "
"Extras ????????????????????????????????????????????????????????????"
#: en/Extras.xml:17(para)
@@ -6001,7 +5984,7 @@
"includes some popular and well-known applications that are maintained by "
"community members in Fedora Extras:"
msgstr ""
-"&FC; &LOCALVER; ???????????????????????????Fedora Extras ?????? 1,350 ???????????????????????????"
+"Fedora Core 5 ???????????????????????????Fedora Extras ?????? 1,350 ???????????????????????????"
"???????????????????????? 2,000 ??????????????????????????????????????????????????? Fedora Extras ??????"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"????????????????????????????????????"
@@ -6343,7 +6326,7 @@
"GNOME Power Manager ??? GNOME ??????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"???????????????????????? HAL (???????????????????????????????????????????????????) ??? DBUS (???????????????"
-"????????????????????????) ????????????????????????&FC; ?????????????????????????????????????????????????????????"
+"????????????????????????) ????????????????????????Fedora Core ?????????????????????????????????????????????????????????"
"??????????????????"
#: en/Desktop.xml:23(emphasis)
@@ -6394,7 +6377,7 @@
"video hardware. To install these extra screensavers, run the following "
"command:"
msgstr ""
-"&FC; &LOCALVER; ??????????????????????????????????????????????????????????????????????????????????????????"
+"Fedora Core 5 ??????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"?????? xscreensaver-gl-extras ????????????????????? OpenGL ?????????"
@@ -6465,7 +6448,7 @@
"Fedora system with a PostgreSQL database, you must upgrade the database to "
"access the data."
msgstr ""
-"&FC; 4 ??? PostgreSQL ?????????????????? 8.0 ??????????????????"
+"Fedora Core 4 ??? PostgreSQL ?????????????????? 8.0 ??????????????????"
"????????????PostgreSQL ???????????? Fedora ?????????????????????"
"???????????????????????????????????????????????????????????????????????????????????????????????????????????????"
@@ -6692,7 +6675,7 @@
#: en/Colophon.xml:122(title)
msgid "Production Methods"
-msgstr "Production Methods"
+msgstr "????????????"
#: en/Colophon.xml:123(para)
msgid ""
@@ -6729,7 +6712,7 @@
"Software, Pirut or enter the "
"following command in a terminal window:"
msgstr ""
-"&FC; ?????????????????????????????????????????????????????????????????????????????????????????????????????????"
+"Fedora Core ?????????????????????????????????????????????????????????????????????????????????????????????????????????"
"????????????????????????????????? Legacy Software "
"Development ?????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
@@ -6749,14 +6732,14 @@
#: en/ArchSpecificx86.xml:8(title)
msgid "x86 Specifics for Fedora"
-msgstr "&FED; ?????? x86 ???????????????"
+msgstr "Fedora ?????? x86 ???????????????"
#: en/ArchSpecificx86.xml:9(para)
msgid ""
"This section covers any specific information you may need to know about "
"Fedora Core and the x86 hardware platform."
msgstr ""
-"??????????????????&FC; ??? x86 ??????????????????????????????????????????????????????????????????????????????"
+"??????????????????Fedora Core ??? x86 ??????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????"
#: en/ArchSpecificx86.xml:11(title)
@@ -6786,7 +6769,7 @@
msgstr ""
"????????? CPU ????????????Intel ???????????????????????????????????????????????????????????????????????????"
"????????????AMD???Cyrix???VIA ??????????????????????????????????????????????????? Intel ??????????????????"
-"?????????????????????????????????????????????????????? &FC; ?????????????????????????????????"
+"?????????????????????????????????????????????????????? Fedora Core ?????????????????????????????????"
#: en/ArchSpecificx86.xml:18(para)
msgid ""
@@ -6798,7 +6781,7 @@
"processors, which make up the bulk of today's processors, is sufficiently "
"different to warrant this change."
msgstr ""
-"?????????: Pentium ????????? — &FC; &LOCALVER; ??????Pentium 4????????????????????????"
+"?????????: Pentium ????????? — Fedora Core 5 ??????Pentium 4????????????????????????"
"CPU ???????????????????????????????????????????????????????????? CPU???????????? Pentium, Pentium "
"Pro, Pentium II, Pentium III ??? AMD ??? VIA ???????????????????????????????????????????????????"
"?????????Pentium ???????????????????????????????????????????????? Pentium ??????????????????????????????"
@@ -6852,7 +6835,7 @@
"Fedora/base/stage2.img on Installation Disc 1 plus the size of the "
"files in /var/lib/rpm on the installed system."
msgstr ""
-"?????????????????????????????????????????????????????????????????????????????? &FC; &LOCALVER; ????????????"
+"?????????????????????????????????????????????????????????????????????????????? Fedora Core 5 ????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????(CD-ROM "
"1 ?????????) /Fedora/base/stage2.img ?????????????????????????????????"
@@ -6882,14 +6865,14 @@
#: en/ArchSpecificx86_64.xml:8(title)
msgid "x86_64 Specifics for Fedora"
-msgstr "&FED; ?????? x86_64 ???????????????"
+msgstr "Fedora ?????? x86_64 ???????????????"
#: en/ArchSpecificx86_64.xml:9(para)
msgid ""
"This section covers any specific information you may need to know about "
"Fedora Core and the x86_64 hardware platform."
msgstr ""
-"??????????????????&FC; ??? x86_64 ???????????????????????????????????????????????????????????????????????????"
+"??????????????????Fedora Core ??? x86_64 ???????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????"
#: en/ArchSpecificx86_64.xml:11(title)
@@ -6954,14 +6937,14 @@
#: en/ArchSpecificPPC.xml:8(title)
msgid "PPC Specifics for Fedora"
-msgstr "&FED; ?????? PPC ???????????????"
+msgstr "Fedora ?????? PPC ???????????????"
#: en/ArchSpecificPPC.xml:9(para)
msgid ""
"This section covers any specific information you may need to know about "
"Fedora Core and the PPC hardware platform."
msgstr ""
-"??????????????????&FC; ??? PPC ??????????????????????????????????????????????????????????????????????????????"
+"??????????????????Fedora Core ??? PPC ??????????????????????????????????????????????????????????????????????????????"
"???????????????????????????????????????????????????"
#: en/ArchSpecificPPC.xml:11(title)
@@ -6981,7 +6964,7 @@
"Fedora Core 5 supports only the ???New World??? generation of Apple Power "
"Macintosh, shipped from circa 1999 onward."
msgstr ""
-"&FC; &LOCALVER; ??? \"New World\" ??????????????? 1999 ?????????????????????????????? Apple "
+"Fedora Core 5 ??? \"New World\" ??????????????? 1999 ?????????????????????????????? Apple "
"Power Macintosh ?????????????????????????????????"
#: en/ArchSpecificPPC.xml:22(para)
@@ -6989,7 +6972,7 @@
"Fedora Core 5 also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos "
"II, and IBM Cell Broadband Engine machines."
msgstr ""
-"&FC; ??? IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, IBM Cell "
+"Fedora Core ??? IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, IBM Cell "
"Broadband Engin ???????????????????????????????????????"
#: en/ArchSpecificPPC.xml:25(para)
@@ -7009,7 +6992,7 @@
"Fedora/base/stage2.img (on Installtion Disc 1) plus the size of the "
"files in /var/lib/rpm on the installed system."
msgstr ""
-"?????????????????????????????????????????????????????????????????????????????? &FC; &LOCALVER; ????????????"
+"?????????????????????????????????????????????????????????????????????????????? Fedora Core 5 ????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"??????????????????????????????????????????????????????????????????????????????????????????????????????(CD-ROM "
"1 ?????????) /Fedora/base/stage2.img ?????????????????????????????????"
@@ -7047,7 +7030,7 @@
"of this disc. These images will behave differently according to your system "
"hardware:"
msgstr ""
-"&FC; ????????????????????????????????? 1 ?????????????????????????????????????????????????????????????????????"
+"Fedora Core ????????????????????????????????? 1 ?????????????????????????????????????????????????????????????????????"
"????????????????????????????????? CD ??????????????????????????? images/ "
"??????????????????????????????????????????????????????????????????????????????????????????????????????????????????"
"????????????????????????"
@@ -7138,7 +7121,7 @@
"this, set the boot-device and boot-file "
"environment variables appropriately."
msgstr ""
-"????????????????????????????????? &FC; ????????????????????????????????? Pegasos ?????? OpenFirmware "
+"????????????????????????????????? Fedora Core ????????????????????????????????? Pegasos ?????? OpenFirmware "
"??????????????????????????????????????????????????????????????????????????????????????? boot-"
"device ??? boot-file ????????????????????????????????????????????????"
@@ -7176,7 +7159,7 @@
"This section provides notes that are specific to the supported hardware "
"architectures of Fedora Core."
msgstr ""
-"??????????????????&FC; ??????????????????????????????????????????????????????????????????????????????????????????"
+"??????????????????Fedora Core ??????????????????????????????????????????????????????????????????????????????????????????"
"??????"
#. Put one translator per line, in the form of NAME , YEAR1, YEAR2.
From fedora-docs-commits at redhat.com Sun Mar 19 21:34:36 2006
From: fedora-docs-commits at redhat.com (Francesco Tombolini (tombo))
Date: Sun, 19 Mar 2006 16:34:36 -0500
Subject: marketing-content/FC-5-press-release it.po,1.1,1.2
Message-ID: <200603192134.k2JLYanc023704@cvs-int.fedora.redhat.com>
Author: tombo
Update of /cvs/docs/marketing-content/FC-5-press-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23686
Modified Files:
it.po
Log Message:
corrected 2 typos
Index: it.po
===================================================================
RCS file: /cvs/docs/marketing-content/FC-5-press-release/it.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- it.po 17 Mar 2006 01:21:36 -0000 1.1
+++ it.po 19 Mar 2006 21:34:28 -0000 1.2
@@ -19,11 +19,11 @@
#: fc5-press-release-en_US.xml:10(para)
msgid "The Fedora Project is pleased to announce the release of Fedora Core 5. New desktop applications, advances in security, better localization tools, improved software installation and management facilities, and strong Java integration help to make Fedora Core 5 the most innovative Linux distribution ever."
-msgstr "Il Progetto Fedora ?? lieto di annunciare il rilascio di Fedora Core 5. Nuove applicazioni desktop, sicurezza avanzata, strumenti di localizzazione migliorati, sviluppata l'installazione e la gestione del software ed una forte integrazione con Java fa si che Fedora Core 5 sia la pi?? innovativa distribuzione di Linux di sempre."
+msgstr "Il Progetto Fedora ?? lieto di annunciare il rilascio di Fedora Core 5. Nuove applicazioni desktop, sicurezza avanzata, strumenti di localizzazione migliorati, sviluppata l'installazione e la gestione del software ed una forte integrazione con Java fanno si che Fedora Core 5 sia la pi?? innovativa distribuzione di Linux di sempre."
#: fc5-press-release-en_US.xml:17(para)
msgid "For a more complete list of changes and interesting information for users, administrators, and developers, refer to the latest release notes:"
-msgstr "Per una lista pi?? dettagliata dei cambiamenti e informazioni interessanti per gli utenti, amministrator e sviluppatori, riferirsi alle ultime note di rilascio:"
+msgstr "Per una lista pi?? dettagliata dei cambiamenti e informazioni interessanti per gli utenti, amministratori e sviluppatori, riferirsi alle ultime note di rilascio:"
#: fc5-press-release-en_US.xml:25(header)
msgid "Getting Fedora Core 5"
From fedora-docs-commits at redhat.com Sun Mar 19 21:39:15 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 19 Mar 2006 16:39:15 -0500
Subject: yum-software-management/en_US yum-software-management.xml,1.2,1.3
Message-ID: <200603192139.k2JLdFuH023747@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23713/en_US
Modified Files:
yum-software-management.xml
Log Message:
- Added section on customizing yum, and plugins.
- Added section on caching.
Index: yum-software-management.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/yum-software-management.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- yum-software-management.xml 13 Mar 2006 00:23:33 -0000 1.2
+++ yum-software-management.xml 19 Mar 2006 21:39:08 -0000 1.3
@@ -44,10 +44,10 @@
This document is a reference for using yum.
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
- the
- before using yum for the first time.
- Experienced Linux users should start with
+ before
+ using yum for the first time. Experienced
+ Linux users should start with
.
@@ -225,7 +225,7 @@
A repository is a prepared directory or
- web site that contains software packages and index files.
+ Web site that contains software packages and index files.
Software management utilities such as yum
automatically locate and obtain the correct RPM packages from
these repositories. This method frees you from having to
@@ -557,18 +557,18 @@
manually install and remove packages from your system. If you
install software with the rpm utility, you must
manually check and install any dependencies. For this reason,
- yum is the recommended method for installing
- software.
+ pirut and yum are
+ the recommended methods for installing software.
Current Package Versions
- The Add/Remove Software and
- yum utilities ensure that you have the most
- recent version of software packages. Other methods do not
- guarantee that the packages are current.
+ The pirut and yum
+ utilities ensure that you have the most recent version of
+ software packages. Other methods do not guarantee that the
+ packages are current.
@@ -722,15 +722,19 @@
and verified, yum applies them to your system.
-
- Every completed transaction records the affected packages in the
- log file
-
- log file
-
- /var/log/yum.log. You may only read this file
- with root access.
-
+
+ Transaction Log
+
+
+ Every completed transaction records the affected packages in the
+ log file
+
+ log file
+
+ /var/log/yum.log. You may only read this
+ file with root access.
+
+ Installing New Software with <command>yum</command>
@@ -817,6 +821,20 @@
+
+ Kernel Packages
+
+
+ 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,
+ yum automatically removes obsolete kernel
+ packages from your system, retaining only the current kernel
+ and the previous version.
+
+
+
To update all of the packages in the package group
MySQL Database, enter the command:
@@ -964,14 +982,14 @@
or options.
Alternatively, use wild cards or regular expressions with any
yum search option to broaden the search
- critieria.
+ criteria.
The 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 PalmPilots, type:
+ search for all packages that relate to Palm Pilots, type:
su -c 'yum search PalmPilot'
@@ -1011,11 +1029,11 @@
- Use the standard wildcard characters to run any search option
+ Use the standard wild-card characters to run any search option
with a partial word or name: to represent any
one character, and to mean zero or more
characters. Always add the escape character ()
- before wildcards.
+ before wild-cards.
@@ -1041,7 +1059,7 @@
Searches with yum 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
- wildcards or a regular expression.
+ wild-cards or a regular expression.
@@ -1109,8 +1127,8 @@
script /etc/rc.d/init.d/yum. This control
script activates the script
/etc/cron.daily/yum.cron, which causes
- the cron service to perform the system
- update automatically at 4am each day.
+ the cron service to automatically begin a
+ system update at 4am each day.
@@ -1386,125 +1404,155 @@
-
- Maintaining <command>yum</command>
-
+
+ Customizing <command>yum</command>
+
- The yum system does not require any routine
- maintenance. To ensure that yum operations are
- carried out at optimal speed, disable or remove repository
- definitions which you no longer require. You may also clear the
- files from the yum caches in order to recover
- disk space.
+ To change the behavior of yum, you may either
+ edit the configuration files, or install
+ plugins. Plugins enable developers to add
+ new features to yum.
-
- Disabling or Removing Package Sources
+
+ Editing the <command>yum</command> Configuration
- repositories
- disabling in yum
-
-
- repositories
- removing from yum
+ configuration files
- Set enable=0 in a definition file to prevent
- yum from using that repository. The
- yum utility ignores any definition file with
- this setting.
+ The file /etc/yum.conf provides the main
+ configuration for yum. Settings in a
+ repository definition file override the main configuration for
+ those operations that use the defined repository.
- To completely remove access to a repository:
+ To edit /etc/yum.conf, run a text editor
+ with root privileges.
+ This command opens /etc/yum.conf with
+ gedit, the default text editor for
+ &FED; desktop systems:
+
+
+su -c 'gedit /etc/yum.conf'
+
+
+ Enter the password for the
+ root account when
+ prompted.
-
-
-
- Delete the relevant file from
- /etc/yum.repos.d/.
-
-
-
-
- Delete the cache directory from
- /var/cache/yum/.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Clearing the <command>yum</command> Caches
-
- yum
- cleaning caches
-
- If you configure it to do so, yum 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:
+ Each plugin configuration file includes the
+ enabled 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.
-
-su -c 'yum clean headers'
+
+
+ Example Plugin Configuration File
+
+[main]
+enabled=1
+anotheroption=0
+
+
+
+ Plugin Installed by Default
+
+
+
+ plugins
+ installonlyn
+
+ &FC; includes the installonlyn plugin.
+ This plugin modifies yum to remove excess
+ kernel packages, so that no more than a set number of kernels
+ exist on the system. By default,
+ installonlyn retains the two most current
+ kernels, and automatically removes older kernel packages.
+
+
+
- Run this command to remove all of the packages held in the
- caches:
+
+ plugins
+ removing
+
+ To remove a plugin, delete both the original file and the
+ automatically generated bytecode file from
+ /usr/lib/yum-plugins/. The bytecode file
+ uses the same name as the plugin, but has the extension
+ .pyc. Remove the relevant configuration
+ file in /etc/yum/pluginconf.d/.
+
+
+
+ This command removes the plugin
+ exampleplugin:
-su -c 'yum clean packages'
+su -c 'rm -f /etc/yum/pluginconf.d/exampleplugin.conf; rm -f /usr/lib/yum-plugins/exampleplugin.p*'
- When using these commands, at the prompt, enter the password for
- the root account.
+ Enter the password for the
+ root account when
+ prompted.
+
+
+
+
+ Enabling the Caches
+
+ caching
+
+
+ packages
+ caching
+
+
+ By default, current versions of yum 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 yum uses. To configure
+ yum to retain downloaded files rather than
+ discarding them, set the keepcache option in
+ /etc/yum.conf to 1:
+
+
+
+keepcache=1
+
+
+
+ Enabling this option provides three advantages:
+
+
+
+
+
+
+ Performance increases, as cached files may be reused, rather
+ than being downloaded for each operation that requires them
+
+
+
+
+ You may carry out yum operations without
+ a network connection, by using only the caches
+
+
+
+
+ You may copy packages from the caches and reuse them
+ elsewhere
+
+
+
+
+
+
+ To carry out a yum command without a network
+ connection, add the option. This causes
+ yum to proceed without checking any network
+ repositories, and use only cached files. In this mode,
+ yum may only install packages that have been
+ downloaded and cached by a previous operation.
+
+
+
+ To search for the package tsclient without
+ using a network connection, enter the command:
+
+
+su -c 'yum -C list tsclient'
+
+
+ Enter the password for the
+ root account when
+ prompted.
+
+
+ By default, yum stores temporary files under
+ the directory /var/cache/yum/, with one
+ subdirectory for each configured repository. The
+ packages/ directory within each repository
+ directory holds the cached packages. For example, the directory
+ /var/cache/yum/development/packages/ holds
+ packages downloaded from the development
+ repository.
+
+
+ Clearing the <command>yum</command> Caches
- 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.
+ Cached files use disk space until removed. You may wish to
+ periodically clear the yum caches to recover
+ capacity. Refer to for
+ information on clearing the caches.
-
+
+
+ If you remove a package from the cache, you do not affect the copy
+ of the software installed on your system.
+
@@ -1681,10 +1850,174 @@
+
+ Maintaining <command>yum</command>
+
+
+ The yum system does not require any routine
+ maintenance. To ensure that yum operations are
+ carried out at optimal speed, disable or remove repository
+ definitions which you no longer require. You may also clear the
+ files from the yum caches in order to recover
+ disk space.
+
+
+
+ Disabling or Removing Package Sources
+
+ repositories
+ disabling in yum
+
+
+ repositories
+ removing from yum
+
+
+ Set enable=0 in a definition file to prevent
+ yum from using that repository. The
+ yum utility ignores any definition file with
+ this setting.
+
+
+
+ To completely remove access to a repository:
+
+
+
+
+ Delete the relevant file from
+ /etc/yum.repos.d/.
+
+
+
+
+ Delete the cache directory from
+ /var/cache/yum/.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Clearing the <command>yum</command> Caches
+
+ yum
+ cleaning caches
+
+
+ If you configure it to do so, yum 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:
+
+
+su -c 'yum clean headers'
+
+
+ Run this command to remove all of the packages held in the
+ caches:
+
+
+su -c 'yum clean packages'
+
+
+ When using these commands, at the prompt, enter the password for
+ the root account.
+
+
+
+ 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.
+
+
+
+
-
- Acknowledgements
+
+ Acknowledgments
Paul Frields edited this document. Timothy Murphy reviewed the
From fedora-docs-commits at redhat.com Sun Mar 19 21:39:10 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 19 Mar 2006 16:39:10 -0500
Subject: yum-software-management rpm-info.xml,1.3,1.4
Message-ID: <200603192139.k2JLdeLs023750@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23713
Modified Files:
rpm-info.xml
Log Message:
- Added section on customizing yum, and plugins.
- Added section on caching.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/rpm-info.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- rpm-info.xml 13 Mar 2006 00:23:27 -0000 1.3
+++ rpm-info.xml 19 Mar 2006 21:39:02 -0000 1.4
@@ -14,7 +14,7 @@
1.0
- 2005
+ 2006Stuart Ellis
@@ -28,10 +28,15 @@
+
+
+
+ Added sections on caching and plugins.
+
- Updated for Fedora 5.
+ Updated for Fedora 5.
From fedora-docs-commits at redhat.com Sun Mar 19 22:01:46 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Sun, 19 Mar 2006 17:01:46 -0500
Subject: yum-software-management/en_US yum-software-management.xml,1.3,1.4
Message-ID: <200603192201.k2JM1kvL026018@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24103/en_US
Modified Files:
yum-software-management.xml
Log Message:
- Fix typo.
Index: yum-software-management.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/yum-software-management.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- yum-software-management.xml 19 Mar 2006 21:39:08 -0000 1.3
+++ yum-software-management.xml 19 Mar 2006 22:01:30 -0000 1.4
@@ -1508,8 +1508,8 @@
Plugin File Extension
- The names of yum plugin files end with
- .py, the standard file extension for
+ The names of yum plugins end with
+ .py, the standard extension for
Python files.
@@ -1538,7 +1538,7 @@
exampleplugin.py, enter the command:
-su -c 'cp example-lugin.py /usr/lib/yum-plugins/'
+su -c 'cp exampleplugin.py /usr/lib/yum-plugins/'
Enter the password for the
From fedora-docs-commits at redhat.com Mon Mar 20 13:34:18 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Mon, 20 Mar 2006 08:34:18 -0500
Subject: install-guide/en_US entities.xml,1.1,1.2
Message-ID: <200603201334.k2KDYIKo028216@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28198
Modified Files:
entities.xml
Log Message:
Fix locale in local entities
Index: entities.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/entities.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entities.xml 17 Mar 2006 19:40:20 -0000 1.1
+++ entities.xml 20 Mar 2006 13:34:10 -0000 1.2
@@ -10,7 +10,7 @@
Document language
- en
+ en_USDocument version
From fedora-docs-commits at redhat.com Tue Mar 21 06:04:09 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 21 Mar 2006 01:04:09 -0500
Subject: docs-common/common legalnotice-content-en_US.xml, 1.1,
1.2 legalnotice-content-en.xml, 1.13,
1.14 legalnotice-content-it.xml, 1.4,
1.5 legalnotice-content-p1-en_US.xml, 1.1,
1.2 legalnotice-content-p1-en.xml, 1.4,
1.5 legalnotice-content-p1-it.xml, 1.1,
1.2 legalnotice-content-p3-en_US.xml, 1.1,
1.2 legalnotice-content-p3-en.xml, 1.2,
1.3 legalnotice-content-p3-it.xml, 1.1, 1.2
Message-ID: <200603210604.k2L6492X004891@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4857
Modified Files:
legalnotice-content-en_US.xml legalnotice-content-en.xml
legalnotice-content-it.xml legalnotice-content-p1-en_US.xml
legalnotice-content-p1-en.xml legalnotice-content-p1-it.xml
legalnotice-content-p3-en_US.xml legalnotice-content-p3-en.xml
legalnotice-content-p3-it.xml
Log Message:
Sorry, I perpetrated this mistake that carried on through translation; 'and others' covers every individual contributor, aiui.
Index: legalnotice-content-en_US.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-en_US.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-en_US.xml 2 Mar 2006 23:06:38 -0000 1.1
+++ legalnotice-content-en_US.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -13,7 +13,7 @@
Legal Notice -->
- Copyright (c) 2006 by Fedora Foundation and others. This material may be
+ Copyright (c) 2006 by Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at .
@@ -40,7 +40,7 @@
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc.,
are registered or pending registration in the U.S. and other countries, and
- are used here under license to the Fedora Foundation.
+ are used here under license to the Fedora Project.
Index: legalnotice-content-en.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-en.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- legalnotice-content-en.xml 28 Feb 2006 23:18:42 -0000 1.13
+++ legalnotice-content-en.xml 21 Mar 2006 06:03:43 -0000 1.14
@@ -13,7 +13,7 @@
Legal Notice -->
- Copyright (c) 2006 by Fedora Foundation and others. This material may be
+ Copyright (c) 2006 by Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at .
@@ -40,7 +40,7 @@
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc.,
are registered or pending registration in the U.S. and other countries, and
- are used here under license to the Fedora Foundation.
+ are used here under license to the Fedora Project.
Index: legalnotice-content-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-it.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- legalnotice-content-it.xml 1 Mar 2006 13:47:35 -0000 1.4
+++ legalnotice-content-it.xml 21 Mar 2006 06:03:43 -0000 1.5
@@ -13,7 +13,7 @@
Legal Notice -->
- Copyright (c) 2006 by Fedora Foundation ed altri. Questo materiale potrebbe essere
+ Copyright (c) 2006 by Red Hat, Inc. ed altri. Questo materiale potrebbe essere
distribuito solo soggetto ai termini e condizioni precedentemente fissati nella Open
Publication License, v1.0, disponibile su .
@@ -40,7 +40,7 @@
FEDORA, FEDORA PROJECT, ed il Fedora Logo sono marchi di Red Hat, Inc.,
sono registrati o in attesa di registrazione negli U.S. ed in altri paesi, e
- sono usati qui sotto licenza della Fedora Foundation.
+ sono usati qui sotto licenza della Fedora Project.
Index: legalnotice-content-p1-en_US.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p1-en_US.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-p1-en_US.xml 2 Mar 2006 23:06:38 -0000 1.1
+++ legalnotice-content-p1-en_US.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -9,7 +9,7 @@
]>
- Copyright (c) 2006 by Fedora Foundation and others. This material may be
+ Copyright (c) 2006 by Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at .
Index: legalnotice-content-p1-en.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p1-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- legalnotice-content-p1-en.xml 28 Feb 2006 18:07:11 -0000 1.4
+++ legalnotice-content-p1-en.xml 21 Mar 2006 06:03:43 -0000 1.5
@@ -9,7 +9,7 @@
]>
- Copyright (c) 2006 by Fedora Foundation and others. This material may be
+ Copyright (c) 2006 by Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at .
Index: legalnotice-content-p1-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p1-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-p1-it.xml 4 Mar 2006 10:30:04 -0000 1.1
+++ legalnotice-content-p1-it.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -9,7 +9,7 @@
]>
- Copyright (c) 2006 da Fedora Foundation ed altri. Questo materiale pu?? essere
+ Copyright (c) 2006 da Red Hat, Inc. ed altri. Questo materiale pu?? essere
distribuito solo soggetto ai termini e condizioni fissati nella Open
Publication License, v1.0, disponibile su .
Index: legalnotice-content-p3-en_US.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p3-en_US.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-p3-en_US.xml 2 Mar 2006 23:06:38 -0000 1.1
+++ legalnotice-content-p3-en_US.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -11,5 +11,5 @@
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc.,
are registered or pending registration in the U.S. and other countries, and
- are used here under license to the Fedora Foundation.
+ are used here under license to the Fedora Project.
Index: legalnotice-content-p3-en.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p3-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- legalnotice-content-p3-en.xml 20 Feb 2006 21:13:23 -0000 1.2
+++ legalnotice-content-p3-en.xml 21 Mar 2006 06:03:43 -0000 1.3
@@ -11,5 +11,5 @@
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc.,
are registered or pending registration in the U.S. and other countries, and
- are used here under license to the Fedora Foundation.
+ are used here under license to the Fedora Project.
Index: legalnotice-content-p3-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p3-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-p3-it.xml 4 Mar 2006 10:30:04 -0000 1.1
+++ legalnotice-content-p3-it.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -11,5 +11,5 @@
FEDORA, FEDORA PROJECT, ed il Fedora Logo sono marchi di Red Hat, Inc.,
sono registrati od in attesa di registrazione negli U.S. ed in altri paesi, e
- sono usati qui sotto licenza alla Fedora Foundation.
+ sono usati qui sotto licenza alla Fedora Project.
From fedora-docs-commits at redhat.com Tue Mar 21 07:04:51 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Tue, 21 Mar 2006 02:04:51 -0500
Subject: release-notes rpm-info.xml,1.9,1.10
Message-ID: <200603210704.k2L74poc007566@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7548
Modified Files:
rpm-info.xml
Log Message:
Last copyright correction.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/release-notes/rpm-info.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- rpm-info.xml 1 Mar 2006 00:48:46 -0000 1.9
+++ rpm-info.xml 21 Mar 2006 07:04:40 -0000 1.10
@@ -18,7 +18,7 @@
2006
- Fedora Foundation and others
+ Red Hat, Inc. and others
From fedora-docs-commits at redhat.com Wed Mar 22 03:05:13 2006
From: fedora-docs-commits at redhat.com (Chad Sellers (csellers))
Date: Tue, 21 Mar 2006 22:05:13 -0500
Subject: selinux-faq/en_US selinux-faq.xml,1.1,1.2
Message-ID: <200603220305.k2M35DMb025662@cvs-int.fedora.redhat.com>
Author: csellers
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25627/en_US
Modified Files:
selinux-faq.xml
Log Message:
Numerous updates for FC5 release
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- selinux-faq.xml 16 Mar 2006 19:43:06 -0000 1.1
+++ selinux-faq.xml 22 Mar 2006 03:04:53 -0000 1.2
@@ -243,20 +243,16 @@
This package is common to all types of policy and contains
- config files/man pages.
-
-
-
-
- selinux-policy-devel-<version>.noarch.rpm
-
-
- This is the development environment. This replaces the
- -sources package from the past. This package contains the
- interface files used in reference policy along with a
- Makefile and a small tool used to generate a policy template
- file. The interface files reside in
- /usr/share/selinux/refpolicy/headers directory.
+ config files/man pages. This includes the interface files
+ for the development environment. This replaces the -sources
+ package from the past. This package contains the interface
+ files used in Reference Policy along with a Makefile and a
+ small tool called policygentool used to
+ generate a policy template file. The interface files reside
+ in /usr/share/selinux/devel/headers
+ directory. If you want to see all of the policy files used
+ to build the Reference Policy you need to install the
+ src.rpm.
@@ -266,13 +262,20 @@
selinux-policy-mls-<version>.noarch.rpm
- Binary policy files are in /etc/selinux/policyname. The
- policy for the types and domains is configured separately
- from security context for the subjects and objects.
+ Binary policy files are in
+ /etc/selinux/policyname/.
+ The policy for the types and domains is configured
+ separately from security context for the subjects and
+ objects.
+
+ More information on the different policies available in SELinux
+ can be found at
+ .
+ .
+
+ More information on the different policies available in SELinux
+ can be found at
+ .
+
+
-
What daemons are protected by the targeted policy?
@@ -398,6 +405,7 @@
+-->
@@ -417,6 +425,11 @@
For example, system-config-securitylevel builds
a relabel into the startup scripts.
+
+ More information on the different policies available in SELinux
+ can be found at
+ .
+
@@ -435,6 +448,11 @@
This policy is geared toward this sort of environment, and is
probably not useful to you unless you fall into this category.
+
+ More information on the different policies available in SELinux
+ can be found at
+ .
+
@@ -446,14 +464,24 @@
The Reference Policy
- is a new project designed to rewrite the entire SELinux policy in a
- way that is easier to use and understand. To do this, it uses
- the concepts of modularity, abstraction, and well-defined interfaces.
+ is a new project maintained by Tresys Technology
+ () designed to rewrite
+ the entire SELinux policy in a way that is easier to use and
+ understand. To do this, it uses the concepts of modularity,
+ abstraction, and well-defined interfaces.
Refer to
for more information on the Reference Policy.
+ Note that Reference Policy is not a new type of policy, like
+ targeted or strict. Rather, it is a new base that policies can be
+ built from. Targeted, strict, and mls policies can all be built
+ from Reference Policy. In fact, one of the design goals of Reference
+ Policy is to have a single unified source tree for the different
+ policy variants.
+
+
Fedora policies at version 1.x are based on the traditional example
policy. Version 2.x policies (as used in &FC; &LOCALVER;) are based
on the Reference Policy.
@@ -517,6 +545,71 @@
+
+
+
+ What are policy modules?
+
+
+
+
+ Prior to &FC; 5, SELinux policies were monolithic, meaning that
+ they were compiled into a single policy binary. To make changes
+ or additions to that policy, an administrator had to change out
+ the entire policy. With &FC; 5, the policy is now modular. This
+ means that third party developers can ship policy modules with
+ their applications, and then they can be added to the policy
+ without having to switch out the entire policy in much the
+ same way that kernel modules can add funcationality to the kernel
+ without having to reboot the entire system.
+
+
+ This actually works by separating out compile and link steps
+ in the policy build procedure. Policy modules are compiled from
+ source, and linked when installed into the module store (see
+ ). This linked
+ policy is then loaded into the kernel for enforcement.
+
+
+ The primary command for dealing with modules is
+ semodule, which will let you perform basic
+ functions such as installing, upgrading, or removing modules.
+ Modules are usually stored as policy package file (.pp
+ extension) in
+ /usr/share/selinux/policyname/.
+ There you should at least
+ find the base.pp, which is the base module.
+
+
+
+
+
+
+ What is managed policy?
+
+
+
+
+ Prior to &FC; 5, SELinux policies were handled as user-editable
+ config files in etc. Unfortunately, this made it difficult to
+ address many of the usability issues arising with SELinux. So, a
+ new libraray, libsemanage, was added to
+ provide userspace tools an interface to making policy management
+ easier. All policy management should use this library to access
+ the policy store. The policy store holds all the policy
+ information, and is found at
+ /etc/selinux/policyname/.
+
+
+ You should never have to edit the store directly. Instead, you
+ should use tools that link against libsemanage. One example tool
+ is semanage, which is a command line tool for
+ managing much of the policy such as SELinux user mappings,
+ SELinux port mappings, and file contexts entries. Other graphical
+ tools are currently being developed as well.
+
+
+ Controlling &SEL;
@@ -882,14 +975,13 @@
<computeroutput>sysadm_r</computeroutput> Role
- Required
+ Required for strict policy
You must issue the setenforce command with
- the sysadm_r role. Use the
+ the sysadm_r role if you are
+ using strict policy. If you are using the standard targeted
+ policy, then this is not necessary. Use the
newrole command to assume this role.
- Alternately, if you switch to root using su
- -, you assume the
- sysadm_r role automatically.
@@ -943,6 +1035,160 @@
+
+
+
+ How do I write policy to allow a domain to use pam_unix.so?
+
+
+
+
+ Very few domains in the SELinux world are allowed to read the
+ /etc/shadow file. There are constraint rules
+ that prevent policy writers from writing code like
+
+
+allow mydomain_t shadow_t:file read;
+
+
+ In RHEL4 you can setup your domain to use the
+ unix_chkpwd command. The easiest way is to use
+ the unix_chkpwd attribute. So if you were
+ writing policy for an ftpd daemon you would write something like
+
+
+daemon_domain(vsftpd, `auth_chkpwd')
+
+
+ This would create a context where
+ vsftpd_t -> chkpwd_exec_t -> system_chkpwd_t which can read
+ /etc/shadow, while vsftpd_t is not able to
+ read it.
+
+
+ In &FC; &LOCALVER;/RHEL5, add the rule
+
+
+auth_domtrans_chk_passwd(vsftpd_t)
+
+
+
+
+
+
+ In the past I have written local.te file in policy sources for my
+ own local customization to policy, how do I do this with
+ Reference Policy?
+
+
+
+
+ If you have specific AVC messages you can use
+ audit2allow to
+ generate a Type Enforcement file that is ready to load as a policy
+ module.
+
+
+audit2allow -M local < /tmp/avcs
+
+
+ This will create a local.pp which you can
+ then load into the kernel using
+ semodule -i local.pp.
+ You can also edit the local.te to make
+ additional customizations.
+
+
+audit2allow -M local -l -i /var/log/audit/audit.log
+Generating type enforcment file: local.te
+Compiling policy
+checkmodule -M -m -o local.mod local.te
+semodule_package -o local.pp -m local.mod
+
+******************** IMPORTANT ***********************
+
+In order to load this newly created policy package into the kernel,
+you are required to execute
+
+semodule -i local.pp
+
+
+ This will generate a local.te file, that
+ looks something like the following:
+
+
+module local 1.0;
+
+require {
+ class file { append execute execute_no_trans getattr ioctl read write };
+ type httpd_t;
+ type httpd_w3c_script_exec_t;
+ };
+
+
+allow httpd_t httpd_w3c_script_exec_t:file { execute execute_no_trans getattr ioctl read };
+
+
+ You can hand edit this file and then recompile and reload it
+ using
+
+
+
+
+ checkmodule to compile the te file
+
+
+
+
+ semodule_package to create a policy package
+
+
+
+
+ semodule to add it to the current machines running policy
+
+
+
+
+ Important
+
+ In order to load this newly created policy package into the
+ kernel, you are required to execute
+ semodule -i local.pp
+
+
+
+
+
+
+
+ I created a new Policy Package where do I put it to make sure that
+ it gets loaded into the kernel?
+
+
+
+
+ All you need to do execute the
+ semodule -i myapp.pp
+ command. This modifies the policy that is stored on the machine.
+ Everytime for now on your policy module will get loaded with the
+ rest of the policy. You can even remove the pp file from the
+ system.
+
+
+ semodule -l will list the currently loaded
+ modules.
+
+
+#semodule -i
+myapp 1.2.1
+
+
+ If you later would like to remove the policy package, you can
+ execute semodule -r myapp.
+
+
+ Resolving Problems
@@ -1186,7 +1432,7 @@
If you wanted to not audit dmesg, for example,
you would put this in your
- /etc/selinux/targeted/src/policy/dmesg.te
+ dmesg.te
file:
@@ -1224,8 +1470,6 @@
-
+semodule -b /usr/share/selinux/targeted/base.pp
+
--->
@@ -1559,11 +1798,10 @@
which shows examples of policy.
- If you want to write a new policy domain, you should install the
- selinux-policy-devel package. This will place
- reference policy interface files into the
- /usr/share/selinux/refpolicy directory.
- There are also tools available to help you generate new policy.
+ If you want to create a new policy domain, you can look at the
+ interface files in the
+ /usr/share/selinux/devel sub-directories.
+ There is also a tool there to help you get started.
The following procedure is an example:
@@ -1580,7 +1818,8 @@
policygentool mydaemon /usr/sbin/mydaemon
- This command creates three files:
+ It will prompt you for a few common domain characteristics,
+ and will create three files:
mydaemon.te,
mydaemon.fc and
mydaemon.if.
@@ -1590,8 +1829,9 @@
After you generate the policy files, use the supplied
Makefile,
- /usr/share/selinux/refpolicy/Makefile, to
- build a policy package:
+ /usr/share/selinux/devel/Makefile, to
+ build a policy package
+ (mydaemon.pp):
make -f /usr/share/selinux/refpolicy/Makefile
@@ -1615,7 +1855,7 @@
mode and then use the init script to start your daemon:
-setenforce 1
+setenforce 0service mydaemon restart
@@ -1623,12 +1863,14 @@
Now you can collect avc messages. You can use
audit2allow to translate the avc messages to
- allow rules and begin updating you
+ allow rules and begin updating your
mydaemon.te file. You should search for
interface macros in the
- /etc/selinux/refpolicy/include directory and
+ /usr/share/selinux/devel/include directory and
use these instead of using the allow rules directly, whenever
- possible. If you want more examples of polcy, you could always
+ possible. audit2allow -R will attempt to find
+ interfaces that match the allow rule.
+ If you want more examples of polcy, you could always
install the selinux-policy src rpm, which contains all of the
policy te files for the reference policy.
@@ -1729,6 +1971,278 @@
+
+
+
+ I have a process running as
+ unconfined_t, and &SEL; is
+ still preventing my application from running.
+
+
+
+
+ We have begun to confine the
+ unconfined_t domain somewhat.
+ SELinux restricts certain memory protection operation. Following
+ is a list of those denials, as well as possible reasons and
+ solutions for those denials.
+ For more information on these restrictions, see .
+
+
+
+ execmod
+
+
+ This is usually based on a library label. You can change
+ the context on the library with the
+ chcon -t testrel_shlib_t
+ LIBRARY. Now your
+ application can run. Please report this as a bugzilla.
+
+
+
+
+ execstack
+
+
+ Attempt to execstack -c
+ LIBRARY. Now try your
+ application again. If the application now works, the
+ library was mistakenly marked as requiring
+ execstack. Please report
+ this as a bugzilla.
+
+
+
+
+ execmem, execheap
+
+
+ A boolean for each one of these memory check errors have been
+ provided. So if you need to run an application requiring
+ either of these permissions, you can set the boolean
+ allow_exec* to fix the problem. For instance if you try to run
+ an application and you get an AVC message containing an
+ execstack failure. You can
+ set the boolean with
+
+
+setsebool -P allow_execstack=1
+
+
+
+
+
+
+
+
+
+ What do these rpm errors mean?
+
+
+
+
+genhomedircon: Warning! No support yet for expanding ROLE macros in the /etc/selinux/mls/contexts/files/homedir_template file when using libsemanage.
+genhomedircon: You must manually update file_contexts.homedirs for any non-user_r users (including root).
+
+
+ Some of the interfaces are not complete yet for selinux. Most
+ users should not care about this warning. It will only affect you
+ if you are running the policy package that is reporting the
+ problem and have non standard SELinux role/user combinations.
+ IE You are using some custom policy.
+
+
+restorecon reset /etc/modprobe.conf context system_u:object_r:etc_runtime_t->system_u:object_r:modules_conf_t
+restorecon reset /etc/cups/ppd/homehp.ppd context user_u:object_r:cupsd_etc_t->system_u:object_r:cupsd_rw_etc_t
+
+
+ During the update process, the selinux package runs restorecon on
+ the difference between the previously install policy file_context
+ and the newly install policy context. This maintains the correct
+ file context on disk.
+
+
+libsepol.sepol_genbools_array: boolean hidd_disable_trans no longer in policy
+
+
+ This indicates that the updated policy has removed the boolean
+ from policy.
+
+
+
+
+
+
+ I want to run a daemon on a non standard port but &SEL; will not
+ allow me. How do get this to work?
+
+
+
+
+ You can use the semanage command to define
+ additional ports. So say you want httpd to be able to listen on
+ port 8082. You could enter the command.
+
+
+semanage port -a -p tcp -t http_port_t 8082
+
+
+
+
+
+
+ How do I add additional translations to my MCS/MLS system?
+
+
+
+
+ Translations are handled through libsemanage. Use
+ semanage translation -l to list all current
+ translations.
+
+
+# semanage translation -l
+Level Translation
+
+s0
+s0-s0:c0.c255 SystemLow-SystemHigh
+s0:c0.c255 SystemHigh
+
+
+ Now pick an unused category. Say you wanted to add
+ Payroll as a translation, and s0:c6 is unused.
+
+
+# semanage translation -a -T Payroll s0:c6
+# semanage translation -l
+Level Translation
+
+s0
+s0-s0:c0.c255 SystemLow-SystemHigh
+s0:c0.c255 SystemHigh
+s0:c6 Payroll
+
+
+
+
+
+
+ I have setup my MCS/MLS translations, now I want to designate
+ which users can read a given category?
+
+
+
+
+ You can modify the range of categories a user can login with
+ by using semanage, as seen in this example.
+
+
+# semanage login -a -r s0-Payroll csellers
+# semanage login -l
+
+Login Name SELinux User MLS/MCS Range
+
+__default__ user_u s0
+csellers user_u s0-Payroll
+root root SystemLow-SystemHigh
+
+
+ In the above example, the user csellers was given access to the
+ Payroll category with the first
+ command, as indicated in the listing output from the second
+ command.
+
+
+
+
+
+
+ I am writing an php script that needs to create temporary files in
+ /tmp and then execute them, SELinux policy is
+ preventing this. What should I do?
+
+
+
+
+ You should avoid having system applications writing to the
+ /tmp directory, since users tend to use the
+ /tmp directory also. It would be better to
+ create a directory elsewhere which could be owned by the apache
+ process and allow your script to write to it. You should label the
+ directory httpd_sys_script_rw_t.
+
+
+
+
+
+
+ I am setting up swapping to a file, but I am seeing AVC messages
+ in my log files?
+
+
+
+
+ You need to identify the swapfile to SELinux by setting its file
+ context to swapfile_t.
+
+
+chcon -t swapfile_t SWAPFILE
+
+
+
+
+
+
+ Please explain the
+ relabelto/relabelfrom
+ permissions?
+
+
+
+
+ For files, relabelfrom means "Can
+ domain D relabel a file from (i.e. currently in) type T1?" and
+ relabelto means "Can domain D
+ relabel a file to type T2?", so both checks are applied upon a
+ file relabeling, where T1 is the original type of the type and T2
+ is the new type specified by the program.
+
+
+ Useful documents to look at:
+
+
+
+
+ Object class and permission summary by Tresys
+
+
+
+
+ Implementing SELinux as an LSM technical report (describes
+ permission checks on a per-hook basis) .
+ This is also available in the selinux-doc package
+ (and more up-to-date there).
+
+
+
+
+ Integrating Flexible Support for Security Policies into the
+ Linux Operating System - technical report (describes original
+ design and implementation, including summary tables of
+ classes, permissions, and what permission checks are applied
+ to what system calls. It is not entirely up-to-date with
+ current implementation, but a good resource nonetheless).
+
+
+
+
+
+ Deploying &SEL;
@@ -1835,15 +2349,23 @@
work under &SEL;.
+ Note that with the addition of , it is now possible
+ for third-party developers to include policy modules with their
+ application. If you are a third-party developer or a
+ package-maintainer, please consider including a policy module
+ in your package. This will allow you to secure the behavior
+ of your application with the power of &SEL; for any user
+ insalling your package.
+
+
One important value that &FC; testers and users bring to the
community is extensive testing of third-party applications. With
that in mind, please bring your experiences to the appropriate
- mailing list, such as the fedora-selinux.list, for discussion. For
+ mailing list, such as the fedora-selinux list, for discussion. For
more information about that list, refer to .
-
-
From fedora-docs-commits at redhat.com Wed Mar 22 03:04:56 2006
From: fedora-docs-commits at redhat.com (Chad Sellers (csellers))
Date: Tue, 21 Mar 2006 22:04:56 -0500
Subject: selinux-faq rpm-info.xml,1.5,1.6
Message-ID: <200603220305.k2M35Qmq025672@cvs-int.fedora.redhat.com>
Author: csellers
Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25627
Modified Files:
rpm-info.xml
Log Message:
Numerous updates for FC5 release
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/rpm-info.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- rpm-info.xml 17 Mar 2006 02:44:05 -0000 1.5
+++ rpm-info.xml 22 Mar 2006 03:04:45 -0000 1.6
@@ -38,6 +38,10 @@
+
+
+ Numerous content updates for FC5 release
+ Make admonition more easily maintainable
From fedora-docs-commits at redhat.com Fri Mar 24 17:56:41 2006
From: fedora-docs-commits at redhat.com (Chad Sellers (csellers))
Date: Fri, 24 Mar 2006 12:56:41 -0500
Subject: selinux-faq/en_US selinux-faq.xml,1.2,1.3
Message-ID: <200603241756.k2OHufOV015684@cvs-int.fedora.redhat.com>
Author: csellers
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15666
Modified Files:
selinux-faq.xml
Log Message:
updated log file location for FC5 release, added targeted domains FAQ
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- selinux-faq.xml 22 Mar 2006 03:04:53 -0000 1.2
+++ selinux-faq.xml 24 Mar 2006 17:56:33 -0000 1.3
@@ -333,55 +333,103 @@
-
+
+
+
+
+
+
+
+
+
@@ -1414,7 +1557,7 @@
new features to yum.
-
+ Editing the <command>yum</command> Configurationconfiguration files
@@ -1508,9 +1651,9 @@
Plugin File Extension
- The names of yum plugins end with
- .py, the standard extension for
- Python files.
+ The names of yum plugin files end with
+ .py, the standard extension for Python
+ scripts.
@@ -1612,7 +1755,7 @@
exampleplugin:
-su -c 'rm -f /etc/yum/pluginconf.d/exampleplugin.conf; rm -f /usr/lib/yum-plugins/exampleplugin.p*'
+su -c 'rm -f /etc/yum/pluginconf.d/exampleplugin.conf; rm -f /usr/lib/yum-plugins/exampleplugin.py*'
Enter the password for the
@@ -1622,8 +1765,8 @@
-
- Enabling the Caches
+
+ Working with <command>yum</command> Cachingcaching
@@ -1635,26 +1778,20 @@
By default, current versions of yum 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 yum uses. To configure
- yum to retain downloaded files rather than
- discarding them, set the keepcache option in
- /etc/yum.conf to 1:
+ storage space that yum uses. You may enable
+ caching, so that yum retains the files that it
+ downloads in cache directories.
-
-
-keepcache=1
-
-
+
- Enabling this option provides three advantages:
+ Caches provide three advantages:
- Performance increases, as cached files may be reused, rather
- than being downloaded for each operation that requires them
+ The performance of yum increases
@@ -1673,28 +1810,6 @@
- To carry out a yum command without a network
- connection, add the option. This causes
- yum to proceed without checking any network
- repositories, and use only cached files. In this mode,
- yum may only install packages that have been
- downloaded and cached by a previous operation.
-
-
-
- To search for the package tsclient without
- using a network connection, enter the command:
-
-
-su -c 'yum -C list tsclient'
-
-
- Enter the password for the
- root account when
- prompted.
-
-
-
By default, yum stores temporary files under
the directory /var/cache/yum/, with one
subdirectory for each configured repository. The
@@ -1717,6 +1832,117 @@
If you remove a package from the cache, you do not affect the copy
of the software installed on your system.
+
+
+ Enabling the Caches
+
+ caching
+ enabling
+
+
+ To configure yum to retain downloaded files
+ rather than discarding them, set the
+ keepcache option in
+ /etc/yum.conf to 1:
+
+
+
+keepcache=1
+
+
+
+ Refer to for more
+ information on editing the yum configuration
+ file.
+
+
+
+ Once you enable caching, every yum 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
+ or query to download package data
+ without modifying your system.
+
+
+
+
+ Using <command>yum</command> in Cache-only Mode
+
+ yum
+ cache-only mode
+
+
+ To carry out a yum command without a network
+ connection, add the option. This causes
+ yum to proceed without checking any network
+ repositories, and use only cached files. In this mode,
+ yum may only install packages that have been
+ downloaded and cached by a previous operation.
+
+
+
+ To search for the package tsclient without
+ using a network connection, enter the command:
+
+
+su -c 'yum -C list tsclient'
+
+
+ Enter the password for the
+ root account when
+ prompted.
+
+
+
+ Cache-only Mode Requires Cached Data
+
+
+ Cache-only mode requires package data to exist in the caches.
+ If you enable caching, every yum operation
+ may update the data files, unless cache-only mode is specified
+ for the operation.
+
+
+
+
+
+ Clearing the <command>yum</command> Caches
+
+ caching
+ cleaning caches
+
+
+ yum
+ cleaning caches
+
+
+ If you configure it to do so, yum 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:
+
+
+su -c 'yum clean headers'
+
+
+ Run this command to remove all of the packages held in the
+ caches:
+
+
+su -c 'yum clean packages'
+
+
+ When using these commands, at the prompt, enter the password for
+ the root account.
+
+
+
+ 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.
+
+
@@ -1850,170 +2076,6 @@
-
- Maintaining <command>yum</command>
-
-
- The yum system does not require any routine
- maintenance. To ensure that yum operations are
- carried out at optimal speed, disable or remove repository
- definitions which you no longer require. You may also clear the
- files from the yum caches in order to recover
- disk space.
-
-
-
- Disabling or Removing Package Sources
-
- repositories
- disabling in yum
-
-
- repositories
- removing from yum
-
-
- Set enable=0 in a definition file to prevent
- yum from using that repository. The
- yum utility ignores any definition file with
- this setting.
-
-
-
- To completely remove access to a repository:
-
-
-
-
- Delete the relevant file from
- /etc/yum.repos.d/.
-
-
-
-
- Delete the cache directory from
- /var/cache/yum/.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Clearing the <command>yum</command> Caches
-
- yum
- cleaning caches
-
-
- If you configure it to do so, yum 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:
-
-
-su -c 'yum clean headers'
-
-
- Run this command to remove all of the packages held in the
- caches:
-
-
-su -c 'yum clean packages'
-
-
- When using these commands, at the prompt, enter the password for
- the root account.
-
-
-
- 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.
-
-
-
-
From fedora-docs-commits at redhat.com Fri Mar 24 20:37:30 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Fri, 24 Mar 2006 15:37:30 -0500
Subject: yum-software-management rpm-info.xml,1.4,1.5
Message-ID: <200603242038.k2OKc0oq022738@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22636
Modified Files:
rpm-info.xml
Log Message:
- Removed "Maintaining Yum" section, and migrated content to other sections.
- Minor polishing.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/rpm-info.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-info.xml 19 Mar 2006 21:39:02 -0000 1.4
+++ rpm-info.xml 24 Mar 2006 20:37:13 -0000 1.5
@@ -28,10 +28,15 @@
+
+
+
+ Minor restructuring of sections.
+
- Added sections on caching and plugins.
+ Added sections on caching and plugins.
From fedora-docs-commits at redhat.com Sat Mar 25 12:09:17 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 25 Mar 2006 07:09:17 -0500
Subject: selinux-faq/po - New directory
Message-ID: <200603251209.k2PC9H9l006636@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/selinux-faq/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6621/po
Log Message:
Directory /cvs/docs/selinux-faq/po added to the repository
From fedora-docs-commits at redhat.com Sat Mar 25 12:12:26 2006
From: fedora-docs-commits at redhat.com (Paul W. Frields (pfrields))
Date: Sat, 25 Mar 2006 07:12:26 -0500
Subject: selinux-faq/po doc-entities.pot,NONE,1.1 selinux-faq.pot,NONE,1.1
Message-ID: <200603251212.k2PCCSIw006671@cvs-int.fedora.redhat.com>
Author: pfrields
Update of /cvs/docs/selinux-faq/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6653/po
Added Files:
doc-entities.pot selinux-faq.pot
Log Message:
Add POT files for translator usage
--- NEW FILE doc-entities.pot ---
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2006-03-25 07:10-0500\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: en_US/doc-entities.xml:6(title)
msgid "These entities are absolutely essential in this document."
msgstr ""
#: en_US/doc-entities.xml:9(comment)
msgid "A per-document entity"
msgstr ""
#: en_US/doc-entities.xml:10(wordasword)
msgid "Per-document Entity"
msgstr ""
#: en_US/doc-entities.xml:14(comment)
msgid "Should match the name of this module"
msgstr ""
#: en_US/doc-entities.xml:15(text)
msgid "selinux-faq"
msgstr ""
#: en_US/doc-entities.xml:18(comment)
msgid "Last revision number, bump when you change the doc"
msgstr ""
#: en_US/doc-entities.xml:19(text)
msgid "1.5.2"
msgstr ""
#: en_US/doc-entities.xml:22(comment)
msgid "Last revision date, format YYYY-MM-DD"
msgstr ""
#: en_US/doc-entities.xml:23(text)
msgid "2006-03-24"
msgstr ""
#: en_US/doc-entities.xml:26(comment)
msgid "Same for every document"
msgstr ""
#: en_US/doc-entities.xml:27(text)
msgid "
-
-
+
+ To ensure the security of your system, run a package update
+ after the installation completes.
+ explains how to update your
+ &FED; system.
+
+
+
+ Reenabled Sound Card section.
+
- Removed obsolete admonition.
+ Removed obsolete admonition.
From fedora-docs-commits at redhat.com Wed Mar 29 23:49:47 2006
From: fedora-docs-commits at redhat.com (Stuart Ellis (elliss))
Date: Wed, 29 Mar 2006 16:49:47 -0700
Subject: yum-software-management/en_US doc-entities.xml,NONE,1.1
Message-ID: <200603292349.k2TNnlva030784@cvs-int.fedora.redhat.com>
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30755/en_US
Added Files:
doc-entities.xml
Log Message:
- Added entities file, which seems to have got lost.
--- NEW FILE doc-entities.xml ---
Local entities for Yum TutorialDocument nameyum-software-managementVersion number1.3Date of last revision2006-03-24Document ID- ()Local version of Fedora Core for this document5
From fedora-docs-commits at redhat.com Thu Mar 30 19:51:58 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 30 Mar 2006 12:51:58 -0700
Subject: selinux-faq/en_US selinux-faq.xml,1.3,1.4
Message-ID: <200603301951.k2UJpwbo022943@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22925
Modified Files:
selinux-faq.xml
Log Message:
Fixing some spelling mistakes, closing bz #187199.
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- selinux-faq.xml 24 Mar 2006 17:56:33 -0000 1.3
+++ selinux-faq.xml 30 Mar 2006 19:51:56 -0000 1.4
@@ -127,7 +127,7 @@
url="http://fedora.redhat.com/projects/docs/" /> for details on
obtaining the fedora-docs/selinux-faq module from anonymous CVS; you can
get just the fedora-docs/selinux-faq module if you
- don't want the entire fedora-dcs tree.) Otherwise,
+ don't want the entire fedora-docs tree.) Otherwise,
plain text showing before and after is sufficient.
@@ -608,7 +608,7 @@
means that third party developers can ship policy modules with
their applications, and then they can be added to the policy
without having to switch out the entire policy in much the
- same way that kernel modules can add funcationality to the kernel
+ same way that kernel modules can add functionality to the kernel
without having to reboot the entire system.
@@ -641,7 +641,7 @@
Prior to &FC; 5, SELinux policies were handled as user-editable
config files in etc. Unfortunately, this made it difficult to
address many of the usability issues arising with SELinux. So, a
- new libraray, libsemanage, was added to
+ new library, libsemanage, was added to
provide userspace tools an interface to making policy management
easier. All policy management should use this library to access
the policy store. The policy store holds all the policy
@@ -702,7 +702,7 @@
, or from a terminal, run
system-config-securitylevel. Change the
policy as desired and ensure that the Relabel on next
- reboot option is enaled.
+ reboot option is enabled.
You can also perform these steps manually with the following
@@ -1148,7 +1148,7 @@
audit2allow -M local -l -i /var/log/messages
-Generating type enforcment file: local.te
+Generating type enforcement file: local.te
Compiling policy
checkmodule -M -m -o local.mod local.te
semodule_package -o local.pp -m local.mod
@@ -1223,7 +1223,7 @@
All you need to do execute the
semodule -i myapp.pp
command. This modifies the policy that is stored on the machine.
- Everytime for now on your policy module will get loaded with the
+ Every time for now on your policy module will get loaded with the
rest of the policy. You can even remove the pp file from the
system.
@@ -1567,7 +1567,7 @@
Once you have found your problem you can reset to the default
- mode by executin
+ mode by executing
semodule -b /usr/share/selinux/targeted/base.pp
@@ -1904,7 +1904,7 @@
- Since you have very limited policy for your executeable,
+ Since you have very limited policy for your executable,
SELinux will prevent it from doing much. Turn on permissive
mode and then use the init script to start your daemon:
@@ -1924,7 +1924,7 @@
use these instead of using the allow rules directly, whenever
possible. audit2allow -R will attempt to find
interfaces that match the allow rule.
- If you want more examples of polcy, you could always
+ If you want more examples of policy, you could always
install the selinux-policy src rpm, which contains all of the
policy te files for the reference policy.
@@ -2380,7 +2380,7 @@
In these edge servers, you can lock down the policy very tightly.
The smaller number of interactions with other components makes
- such a lockdown easier. A dedicated system running a specialized
+ such a lock down easier. A dedicated system running a specialized
third-party application would also be a good candidate.
@@ -2431,7 +2431,7 @@
package-maintainer, please consider including a policy module
in your package. This will allow you to secure the behavior
of your application with the power of &SEL; for any user
- insalling your package.
+ installing your package.
One important value that &FC; testers and users bring to the
From fedora-docs-commits at redhat.com Thu Mar 30 19:58:18 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 30 Mar 2006 12:58:18 -0700
Subject: selinux-faq/en_US selinux-faq.xml,1.4,1.5
Message-ID: <200603301958.k2UJwI7K023518@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23500
Modified Files:
selinux-faq.xml
Log Message:
Fixing passive -> active voice, mainly by searching for 'will' and fixing all instances; this is a habit we all have, in fact some of these may be left over from my previous writing.
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- selinux-faq.xml 30 Mar 2006 19:51:56 -0000 1.4
+++ selinux-faq.xml 30 Mar 2006 19:58:15 -0000 1.5
@@ -620,7 +620,7 @@
The primary command for dealing with modules is
- semodule, which will let you perform basic
+ semodule, which lets you perform basic
functions such as installing, upgrading, or removing modules.
Modules are usually stored as policy package file (.pp
extension) in
@@ -719,8 +719,8 @@
SELINUX=permissive
- This step ensures you will not be locked out after rebooting.
- &SEL; will run under the correct policy, but will allow you to
+ This step ensures are not locked out after rebooting.
+ &SEL; runs under the correct policy, but does allow you to
login if there is a problem such as incorrect file context
labeling.
@@ -793,9 +793,9 @@
If you use an absolute path, such as
/var/log/maillog, when you unpack the
archive with star -c
- -f, the files will be restored on the same path they
- were archived with. The maillog file will
- attempt to write to /var/log/maillog. You
+ -f, the files are restored on the same path they
+ were archived with. The maillog file
+ attempts to write to /var/log/maillog. You
should received a warning from star if the
files about to be overwritten have a later date, but you cannot
rely on this behavior.
@@ -887,7 +887,7 @@
At this point, httpd is configured to serve
- the contents, but you will still receive a 403
+ the contents, but you still receive a 403
forbidden error. This is because
httpd is not allowed to read the security
type for the directory and files as they are created in the
@@ -949,8 +949,8 @@
Be careful when disabling &SEL;
If you boot with , any files you
- create while &SEL; is disabled will not have &SEL; context
- information. The file system will be marked for relabeling at
+ create while &SEL; is disabled do not have &SEL; context
+ information. The file system is marked for relabeling at
the next boot. If an unforeseen problem prevents you from
rebooting normally, you may need to boot in single-user mode for
recovery. Add the option to your
@@ -1065,7 +1065,7 @@
Run auditctl -e 0. Note that this command
- will not affect auditing of SELinux AVC denials.
+ does not affect auditing of SELinux AVC denials.
@@ -1140,7 +1140,7 @@
audit2allow -M local < /tmp/avcs
- This will create a local.pp which you can
+ This creates a local.pp which you can
then load into the kernel using
semodule -i local.pp.
You can also edit the local.te to make
@@ -1165,8 +1165,8 @@
If you were using the audit daemon, then you should use
/var/log/audit/audit.log instead of
/var/log/messages as your log file.
- This will generate a local.te file, that
- looks something like the following:
+ This generates a local.te file, that
+ looks similar to the following:
module local 1.0;
@@ -1214,21 +1214,19 @@
- I created a new Policy Package where do I put it to make sure that
+ I created a new Policy Package, where do I put it to make sure that
it gets loaded into the kernel?
- All you need to do execute the
- semodule -i myapp.pp
- command. This modifies the policy that is stored on the machine.
- Every time for now on your policy module will get loaded with the
- rest of the policy. You can even remove the pp file from the
- system.
+ You need to execute the command semodule -i
+ myapp.pp. This modifies the policy that is stored on the
+ machine. Your policy module now is loaded with the rest of the
+ policy. You can even remove the pp file from the system.
- semodule -l will list the currently loaded
+ semodule -l lists the currently loaded
modules.
@@ -1345,7 +1343,7 @@
After relabeling my /home using
- setfiles or fixfiles, will I
+ setfiles or fixfiles, am I
still be able to read /home with a
non-&SEL;-enabled system?
@@ -1354,7 +1352,7 @@
You can read the files from a non-&SEL; distribution, or one with
&SEL; disabled. However, files created by a system not using &SEL;
- systems will not have a security context, nor will any files you
+ systems do not have a security context, nor do any files you
remove and recreate. This could be a challenge with files such as
~/.bashrc. You may have to relabel
/home when you reboot the &SEL; enabled &FC;
@@ -1376,7 +1374,7 @@
When you mount a non-&SEL; file system via NFS, by default &SEL;
- will treat all the files in the share as having a context of
+ treats all the files in the share as having a context of
nfs_t. You can override the
default context by setting it manually, using the
option. The following command makes
@@ -1413,7 +1411,7 @@
You can create your new user with the standard
useradd command. First you must become
root. Under the strict
- policy you will need to change role to
+ policy you need to change role to
sysadm_r with the following
command:
@@ -1421,7 +1419,7 @@
newrole -r sysadm_r
- For the targeted policy you will not need
+ For the targeted policy you do not need
to switch roles, staying in
unconfined_t:
@@ -1436,7 +1434,7 @@
The initial context for a new user directory has an identity of
root. Subsequent relabeling of
- the file system will change the identity to
+ the file system changes the identity to
system_u. These are functionally
the same since the role and type are identical
(object_r:user_home_dir_t.)
@@ -1542,7 +1540,7 @@
way when a benign denial is filling the audit logs.
- To look for your particular denial, you will need to enable
+ To look for your particular denial, enable
auditing of all dontaudit rules:
@@ -1553,14 +1551,14 @@
is verbose
Enabling auditing of all
- dontaudit rules will likely
+ dontaudit rules likely
produce a large amount of audit information, most of which is
irrelevant to your denial.
Use this technique only if you are specifically looking for an
audit message for a denial that seems to occur silently. You
- will likely want to re-enable
+ want to re-enable
dontaudit rules as soon as
possible.
From fedora-docs-commits at redhat.com Thu Mar 30 21:53:07 2006
From: fedora-docs-commits at redhat.com (Karsten Wade (kwade))
Date: Thu, 30 Mar 2006 14:53:07 -0700
Subject: selinux-faq/en_US selinux-faq.xml,1.5,1.6
Message-ID: <200603302153.k2ULr7aE030053@cvs-int.fedora.redhat.com>
Author: kwade
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv30032
Modified Files:
selinux-faq.xml
Log Message:
Took up this typo from someone who dropped by #fedora-websites, figured it was better to just fix it since the reporter was resisting the Proper Method Using Bugzilla. :)
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- selinux-faq.xml 30 Mar 2006 19:58:15 -0000 1.5
+++ selinux-faq.xml 30 Mar 2006 21:53:04 -0000 1.6
@@ -2048,7 +2048,7 @@
This is usually based on a library label. You can change
the context on the library with the
- chcon -t testrel_shlib_t
+ chcon -t textrel_shlib_t
LIBRARY. Now your
application can run. Please report this as a bugzilla.