release-notes/FC-6/css content.css, NONE, 1.1 docbook.css, NONE, 1.1 layout.css, NONE, 1.1 print.css, NONE, 1.1
by fedora-docs-commits＠redhat.com 28 Oct '06
by fedora-docs-commits＠redhat.com 28 Oct '06
28 Oct '06
Author: pfrields
Update of /cvs/docs/release-notes/FC-6/css
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6395/FC-6/css
Added Files:
content.css docbook.css layout.css print.css
Log Message:
Add FC-6 branch. This branch should be used for errata updates, not devel -- although syncing them is fine.
--- NEW FILE content.css ---
.name-project, .name-release, .name-version {
}
/* Front page H1 */
#page-main h1 {
font-size: 1.35em;
}
#page-main h1.center {
text-align: center;
}
h1, h2, h3, h4 {
/*
font-style: italic;
*/
font-family: luxi sans,sans-serif;
}
h1 {
font-size: 1.75em;
}
h2 {
font-size: 1.25em;
}
h3 {
font-size: 1.1em;
}
hr {
border: 0;
border-bottom: 1px solid #ccc;
}
.fedora-side-right-content {
padding: 0 5px 1.5em;
}
#fedora-side-right h1, #fedora-side-right h2, #fedora-side-right h3 {
margin: 0;
padding: 0 4pt 0;
font-size: 1em;
letter-spacing: 2pt;
border-bottom: 1px solid #bbb;
}
#fedora-side-right hr {
border-bottom: 1px solid #aaa;
margin: 0.5em 0;
}
table tr {
font-size: 0.9em;
}
#link-offsite {
}
.link-offsite-notation {
font-size: 0.9em;
color: #777;
padding-left: 1pt;
text-decoration: none !important;
}
#fedora-content .link-offsite-notation {
color: #999;
}
#link-redhat {
}
#fedora-content #link-redhat {
}
#link-internal {
}
#fedora-content li {
padding: 1pt;
}
#fedora-content h1 {
margin-top: 0;
}
#fedora-content a img {
margin: 1px;
border: 0;
}
#fedora-content a:hover img {
margin: 0;
border: 1px solid #f00;
}
#fedora-content a img.noborder {
margin: 0;
border: 0;
}
#fedora-content a:hover img .noborder {
margin: 0;
border: 0;
}
#fedora-project-maintainers p, #fedora-project-contributors p, #fedora-project-bugs p {
margin-left: 5pt;
}
#fedora-project-download dt {
font-weight: bold;
margin-top: 8pt;
margin-left: 5pt;
}
#fedora-project-download dd {
padding: 0;
margin: 10px 20px 0;
}
#fedora-project-screenshots a img {
margin: 5px;
}
#fedora-project-screenshots a:hover img {
margin: 4px;
}
#fedora-project-todo ul {
border: 1px solid #cad4e9;
margin: 0 1em;
padding: 0;
list-style: none;
border-radius: 2.5px;
-moz-border-radius: 2.5px;
}
#fedora-project-todo li {
margin: 0;
padding: 6px 8px;
}
#fedora-project-todo li.odd {
background-color: #ecf0f7;
}
#fedora-project-todo li.even {
background-color: #f7f9fc;
}
#fedora-list-packages {
border-collapse: collapse;
border: 1px solid #cad4e9;
border-radius: 2.5px;
-moz-border-radius: 2.5px;
}
#fedora-list-packages tr.odd td {
background-color: #ecf0f7;
}
#fedora-list-packages tr.even td {
background-color: #f7f9fc;
}
#fedora-list-packages th,
#fedora-list-packages td {
margin: 0;
padding: 6px 8px;
}
#fedora-list-packages td.column-2 {
text-align: center;
}
#fedora-list-packages th {
background-color: #cad4e9;
color: #000;
font-weight: bold;
text-align: center;
}
/* pre.screen is for DocBook HTML output */
code.screen, pre.screen {
font-family: monospace;
font-size: 1em;
display: block;
padding: 10px;
border: 1px solid #bbb;
background-color: #eee;
color: #000;
overflow: auto;
border-radius: 2.5px;
-moz-border-radius: 2.5px;
margin: 0.5em 2em;
}
#fedora-project code.screen {
margin: 0;
}
code.command, code.filename {
font-family: monospace;
}
code.citetitle {
font-family: sans-serif;
font-style: italic;
}
strong.application {
font-weight: bold;
}
.indent {
margin: 0 2em;
}
.fedora-docs-nav {
text-align: center;
position: relative;
padding: 1em;
margin-top: 2em;
border-top: 1px solid #ccc;
}
.fedora-docs-nav a {
padding: 0 1em;
}
.fedora-docs-nav-left {
position: absolute;
left: 0;
}
.fedora-docs-nav-right {
position: absolute;
right: 0;
}
--- NEW FILE docbook.css ---
#fedora-content li p {
margin: 0.2em;
}
#fedora-content div.table table {
width: 95%;
background-color: #DCDCDC;
color: #000000;
border-spacing: 0;
}
#fedora-content div.table table th {
border: 1px solid #A9A9A9;
background-color: #A9A9A9;
color: #000000;
}
#fedora-content div.table table td {
border: 1px solid #A9A9A9;
background-color: #DCDCDC;
color: #000000;
padding: 0.5em;
margin-bottom: 0.5em;
margin-top: 2px;
}
div.note table, div.tip table, div.important table, div.caution table, div.warning table {
width: 95%;
border: 2px solid #B0C4DE;
background-color: #F0F8FF;
color: #000000;
/* padding inside table area */
padding: 0.5em;
margin-bottom: 0.5em;
margin-top: 0.5em;
}
/* "Just the FAQs, ma'm." */
.qandaset table {
border-collapse: collapse;
}
.qandaset {
}
.qandaset tr.question {
}
.qandaset tr.question td {
font-weight: bold;
padding: 0 0.5em;
margin: 0;
}
.qandaset tr.answer td {
padding: 0 0.5em 1.5em;
margin: 0;
}
.qandaset tr.question td, .qandaset tr.answer td {
vertical-align: top;
}
.qandaset strong {
text-align: right;
}
.article .table table {
border: 0;
margin: 0 auto;
border-collapse: collapse;
}
.article .table table th {
padding: 5px;
text-align: center;
}
div.example {
padding: 10px;
border: 1px solid #bbb;
margin: 0.5em 2em;
}
--- NEW FILE layout.css ---
body {
font-size: 0.9em;
font-family: bitstream vera sans,sans-serif;
margin: 0;
padding: 0;
/* (The background color is specified elsewhere, so do a global replacement if it ever changes) */
background-color: #d9d9d9;
}
a:link {
color: #900;
}
a:visited {
color: #48468f;
}
a:hover {
color: #f20;
}
a[name] {
color: inherit;
text-decoration: inherit;
}
#fedora-header {
background-color: #fff;
height: 62px;
}
#fedora-header img {
border: 0;
vertical-align: middle;
}
#fedora-header-logo {
/* position is offset by the header padding amount */
position: absolute;
left: 26px;
top: 13px;
z-index: 3;
}
#fedora-header-logo img {
width: 110px;
height: 40;
}
#fedora-header-items {
/* position is offset by the header padding amount */
position: absolute;
right: 10px;
top: 15px;
text-align: right;
display: inline;
}
#fedora-header-items a {
color: #000;
text-decoration: none;
padding: 7pt;
font-size: 0.8em;
}
#fedora-header-items a:hover, #fedora-header-search-button:hover {
color: #f20;
cursor: pointer;
}
#fedora-header-items img {
margin-right: 1px;
width: 36px;
height: 36px;
}
#fedora-header-search {
height: 25px;
}
#fedora-header-search-entry {
vertical-align: top;
margin: 0.65em 4px 0 10px;
padding: 2px 4px;
background-color: #f5f5f5;
border: 1px solid #999;
font-size: 0.8em !important;
}
#fedora-header-search-entry:focus {
background-color: #fff;
border: 1px solid #555;
}
#fedora-header-search-button {
font-size: 0.8em !important;
vertical-align: top;
margin-top: 0.2em;
border: 0;
padding: 7px;
background: #fff url('../img/header-search.png') no-repeat left;
padding-left: 21px;
}
#fedora-header-items form {
float: right;
}
#fedora-header-items input {
font-size: 0.85em;
}
#fedora-nav {
margin: 0;
padding: 0;
background-color: #22437f;
font-size: 0;
height: 5px;
border-top: 1px solid #000;
border-bottom: 1px solid #f5f5f5;
}
#fedora-nav ul {
margin: 0;
padding: 0;
}
#fedora-nav li {
display: inline;
list-style: none;
padding: 0 5pt;
}
#fedora-nav li + li {
padding-left: 8pt;
border-left: 1px solid #99a5bf;
}
#fedora-nav a {
color: #c5ccdb;
text-decoration: none;
}
#fedora-nav a:hover {
color: #fff;
}
#fedora-side-left {
position: absolute;
z-index: 2;
width: 11em;
/* Space down for the approx line height (fonts) */
left: 12px;
}
#fedora-side-right {
position: absolute;
z-index: 1;
width: 13em;
right: 12px;
padding-top: 3px;
}
#fedora-side-left, #fedora-side-right {
top: 2px;
/* add to the top margin to compensate for the fixed sizes */
margin-top: 75px;
color: #555;
font-size: 0.9em;
}
#fedora-side-right ul {
list-style: square inside;
padding: 0;
margin: 0;
}
/* Left-side naviagation */
#fedora-side-nav-label {
display: none;
}
#fedora-side-nav {
list-style: none;
margin: 0;
padding: 0;
border: 1px solid #5976b2;
border-top: 0;
background-color: #22437f;
}
#fedora-side-nav li {
margin: 0;
padding: 0;
border-top: 1px solid #5976b2;
/* IE/Win gets upset if there is no bottom border... Go figure. */
border-bottom: 1px solid #22437f;
}
#fedora-side-nav a {
margin: 0;
color: #c5ccdb;
display: block;
text-decoration: none;
padding: 4px 6px;
}
#fedora-side-nav a:hover {
background-color: #34548f;
color: #fff;
}
#fedora-side-nav ul {
list-style: none;
margin: 0;
padding: 0;
}
#fedora-side-nav ul li {
border-top: 1px solid #34548e;
background-color: #34548e;
/* IE/Win gets upset if there is no bottom border... Go figure. */
border-bottom: 1px solid #34548e;
}
#fedora-side-nav ul li:hover {
border-bottom: 1px solid #34548f;
}
#fedora-side-nav ul li a {
padding-left: 12px;
color: #a7b2c9;
}
#fedora-side-nav ul li a:hover {
background-color: #46659e;
}
#fedora-side-nav ul ul li a {
padding-left: 18px;
}
#fedora-side-nav strong a {
font-weight: normal;
color: #fff !important;
background-color: #10203b;
}
#fedora-side-nav strong a:hover {
background-color: #172e56 !important;
}
/* content containers */
#fedora-middle-one, #fedora-middle-two, #fedora-middle-three {
font-size: 0.9em;
/* position: relative; */ /* relative to utilize z-index */
width: auto;
min-width: 120px;
margin: 10px;
z-index: 3; /* content can overlap when the browser is narrow */
}
#fedora-middle-two, #fedora-middle-three {
margin-left: 11em;
padding-left: 24px;
}
#fedora-middle-three {
margin-right: 13em;
padding-right: 24px;
}
#fedora-content {
padding: 24px;
border: 1px solid #aaa;
background-color: #fff;
}
#fedora-content > .fedora-corner-bottom { top: 0 }
.fedora-corner-tl, .fedora-corner-tr, .fedora-corner-bl, .fedora-corner-br {
background-color: #d9d9d9;
position: relative;
width: 19px;
height: 19px;
/* The following line is to render PNGs with alpha transparency within IE/Win, using DirectX */
/* Work-around for IE6/Mac borkage (Part 1) */
display: none;
}
.fedora-corner-tl, .fedora-corner-bl { float: left; left: 0px; }
.fedora-corner-tr, .fedora-corner-br { float: right; right: 0px; }
.fedora-corner-tl, .fedora-corner-tr { top: 0px; }
.fedora-corner-bl, .fedora-corner-br { bottom: 0px; margin-top: -19px; /* Opera fix (part 1) */ top: -18px;}
html>body .fedora-corner-tl { background: #d9d9d9 url("../img/corner-tl.png") no-repeat left top; }
html>body .fedora-corner-tr { background: #d9d9d9 url("../img/corner-tr.png") no-repeat right top; }
html>body .fedora-corner-bl { background: #d9d9d9 url("../img/corner-bl.png") no-repeat left bottom; }
html>body .fedora-corner-br { background: #d9d9d9 url("../img/corner-br.png") no-repeat right bottom; }
.fedora-corner-tl { filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='/img/corner-tl.png',sizingMethod='scale'); }
.fedora-corner-tr { filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='/img/corner-tr.png',sizingMethod='scale'); }
.fedora-corner-br { filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='/img/corner-br.png',sizingMethod='scale'); }
.fedora-corner-bl { filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='/img/corner-bl.png',sizingMethod='scale'); }
/* \*/
.fedora-corner-tl, .fedora-corner-tr, .fedora-corner-bl, .fedora-corner-br {
/* Restore the view for everything but IE6/Mac (part 2 of the "IE/Mac fix") */
display: block;
}
/* */
.fedora-corner-bl, .fedora-corner-br {
top: 0px;
}
.content { margin: 0 1em }
#fedora-sidelist {
position: relative;
bottom: 3px;
margin: 0;
padding: 3px !important;
border: 1px solid #bbb;
background-color: #ccc;
border-radius: 2.5px;
-moz-border-radius: 2.5px;
}
#fedora-sidelist strong a {
font-weight: normal;
background-color: #555;
color: #fff;
}
#fedora-sidelist strong a:hover {
background-color: #333;
color: #fff;
}
#fedora-sidelist li {
list-style-position: outside;
font-size: 0.9em;
list-style: none;
border: 1px solid #ccc;
border-width: 1px 0;
padding: 0;
list-style: none;
}
#fedora-sidelist li a {
text-decoration: none;
display: block;
padding: 6px 8px;
border-radius: 2.5px;
-moz-border-radius: 2.5px;
}
#fedora-sidelist li a:hover {
background-color: #999;
color: #eee;
}
#fedora-footer {
font-size: 0.75em;
text-align: center;
color: #777;
margin-bottom: 2em;
}
#fedora-printable {
text-align: center;
margin: 1em 0;
font-size: 0.85em;
}
#fedora-printable a {
text-decoration: none;
padding: 5px 0;
padding-left: 18px;
background: transparent url("../img/printable.png") no-repeat left;
}
#fedora-printable a:hover {
text-decoration: underline;
}
--- NEW FILE print.css ---
body {
background: white;
color: black;
font-size: 10pt;
font-family: sans-serif;
line-height: 1.25em;
}
div {
border: 1px solid white;
}
li {
border: 1px solid white;
margin: 0;
}
li p {
display: inline;
}
h1 {
font-size: 16pt;
}
h2 {
font-size: 12pt;
}
h3,h4,h5 {
font-size: 10pt;
}
img {
border: 1px solid white;
background-color: white;
}
hr {
border: 1px dotted gray;
border-width: 0 0 1 0;
margin: 1em;
}
table {
border-collapse: collapse;
}
td,th {
border: 1px solid gray;
padding: 8pt;
font-size: 10pt;
}
th {
font-weight: bold;
}
#fedora-header, #fedora-footer {
text-align: center;
}
#fedora-header-items, #fedora-side-left, #fedora-side-right {
display: none;
}
#fedora-project-download dt {
font-weight: bold;
margin-top: 8pt;
margin-left: 5pt;
}
#fedora-project-download dd {
padding: 0;
margin: 10px 20px 0;
}
code.screen, pre.screen {
font-family: monospace;
font-size: 1em;
display: block;
padding: 5pt;
border: 1px dashed gray;
margin: 0.5em 2em;
}
#fedora-project code.screen {
margin: 0;
}
/*
#fedora-content a:link:after, #fedora-content a:visited:after {
content: " (" attr(href) ") ";
font-size: 80%;
}
*/
.navheader table, .navheader table td {
border: 0 !important;
}
1
0
Author: pfrields
Update of /cvs/docs/release-notes/FC-6/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6395/FC-6/en_US
Added Files:
ArchSpecific.xml BackwardsCompatibility.xml Colophon.xml
DatabaseServers.xml Desktop.xml Devel.xml Entertainment.xml
Extras.xml FAQ.xml Feedback.xml FileSystems.xml I18n.xml
Installer.xml Java.xml Kernel.xml Legacy.xml Multimedia.xml
OverView.xml PackageChanges.xml PackageNotes.xml
ProjectOverview.xml README-BURNING-ISOS.xml README.xml
RELEASE-NOTES.xml Security.xml Virtualization.xml
WebServers.xml Welcome.xml Xorg.xml about-fedora.omf.in
about-fedora.xml fedora-release-notes.omf.in homepage.xml
rpm-info.xml
Log Message:
Add FC-6 branch. This branch should be used for errata updates, not devel -- although syncing them is fine.
--- NEW FILE ArchSpecific.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-ArchSpecific">
<title>Architecture Specific Notes</title>
<!--RAW HTML: <h2>Architecture Specific Notes</h2>-->
<para>
This section provides notes that are specific to the supported
hardware architectures of Fedora Core.
</para>
<section>
<title>RPM Multiarch Support on 64-bit platforms (x86_64, ppc64)</title>
<para>
<emphasis role='strong'>RPM</emphasis> supports parallel installation of
multiple architectures of the same package. A default package listing such
as <command>rpm -qa</command> might appear to include duplicate packages, since
the architecture is not displayed. Instead, use the <command>repoquery</command>
command, part of the <package>yum-utils</package> package in Fedora Extras,
which displays architecture by default. To install <package>yum-utils</package>,
run the following command:
</para>
<screen><![CDATA[su -c 'yum install yum-utils'
]]></screen>
<para>
To list all packages with their architecture using
<command>rpm</command>, run the following command:
</para>
<screen><![CDATA[rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"
]]></screen>
<para>
You can add this to <filename>/etc/rpm/macros</filename> (for a system
wide setting) or <filename>~/.rpmmacros</filename> (for a per-user
setting). It changes the default query to list the architecture:
</para>
<screen><![CDATA[%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
]]></screen>
</section>
<section>
<title>PPC Specifics for Fedora</title>
<para>
This section covers any specific information you may need to know about
Fedora Core and the PPC hardware platform.
</para>
<section>
<title>PPC Hardware Requirements</title>
<section>
<title>Processor and Memory</title>
<itemizedlist>
<listitem>
<para>
Minimum CPU: PowerPC G3 / POWER3
</para>
</listitem>
<listitem>
<para>
Fedora Core 6 supports only the "New World" generation of Apple
Power Macintosh, shipped from circa 1999 onward.
</para>
</listitem>
<listitem>
<para>
Fedora Core 6 also supports IBM pSeries, IBM iSeries,
IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband
Engine machines.
</para>
</listitem>
<listitem>
<para>
Recommended for text-mode: 233 MHz G3 or better,
128MiB RAM.
</para>
</listitem>
<listitem>
<para>
Recommended for graphical: 400 MHz G3 or better,
256MiB RAM.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Hard Disk Space Requirements</title>
<para>
The disk space requirements listed below represent the disk space
taken up by Fedora Core 6 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 <filename>/Fedora/base/stage2.img</filename> (on Installation Disc
1) plus the size of the files in <filename>/var/lib/rpm</filename> on the
installed system.
</para>
<para>
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 installation that includes nearly all the
packages. The complete installed packages can occupy over 9 GB of disk
space.
</para>
<para>
Additional space is also required for any user data, and
at least 5% free space should be maintained for proper
system operation.
</para>
</section>
</section>
<section>
<title>The Apple keyboard</title>
<para>
The <keycap function="option">Option</keycap> key on Apple systems is equivalent
to the <keycap function="alt">Alt</keycap> key on the PC. Where documentation
and the installer refer to the <keycap function="alt">Alt</keycap> key, use the
<keycap function="option">Option</keycap> key. For some key combinations you may
need to use the <keycap function="option">Option</keycap> key in conjunction with
the <keycap function="other">Fn</keycap> key, such as
<keycombo>
<keycap function="option">Option</keycap><keycap function="other">Fn</keycap><keycap>F3</keycap></keycombo> to
switch to virtual terminal tty3.
</para>
</section>
<section>
<title>PPC Installation Notes</title>
<para>
Fedora Core Installation Disc 1 is bootable on supported
hardware. In addition, a bootable CD image appears in the
<filename>images/</filename> directory of this disc. These images
behave differently according to your system hardware:
</para>
<itemizedlist>
<listitem>
<para>
Apple Macintosh The bootloader automatically boots the
appropriate 32-bit or 64-bit installer.
</para>
<para>
The default <package>gnome-power-manager</package> package includes power
management support, including sleep and backlight level management.
Users with more complex requirements can use the <package>apmud</package>
package in Fedora Extras. To install <package>apmud</package> after
installation, use the following command:
</para>
</listitem>
</itemizedlist>
<screen>su -c 'yum install apmud'
</screen>
<itemizedlist>
<listitem>
<para>
64-bit IBM pSeries (POWER4/POWER5), current iSeries
models
</para>
<para>
After using Open<emphasis role='strong'/>Firmware to
boot the CD, the bootloader, <command>yaboot</command>,
automatically boots the 64-bit installer.
</para>
</listitem>
<listitem>
<para>
IBM "Legacy" iSeries (POWER4)
</para>
<para>
So-called "Legacy" iSeries models, which do not use Open<emphasis
role='strong'/>Firmware, require use of the boot image located in
the <filename>images/iSeries</filename> directory of the installation tree.
</para>
</listitem>
<listitem>
<para>
32-bit CHRP (IBM RS/6000 and others)
</para>
<para>
After using Open<emphasis role='strong'/>Firmware to boot the CD,
select the <filename>linux32</filename> boot image at the <prompt>boot:</prompt>
prompt to start the 32-bit installer. Otherwise, the 64-bit
installer starts and fails.
</para>
</listitem>
<listitem>
<para>
Genesi Pegasos II
</para>
<para>
At the time of writing, firmware with full support for ISO9660 file
systems has not yet been released for the Pegasos. You can use the
network boot image, however. At the OpenFirmware prompt, enter the following command:
</para>
</listitem>
</itemizedlist>
<screen>boot cd: /images/netboot/ppc32.img
</screen>
<itemizedlist>
<listitem override='none'>
<para>
You must also configure OpenFirmware on the
Pegasos manually to make the installed Fedora Core system bootable.
To do this, set the <envar>boot-device</envar> and
<envar>boot-file</envar> environment variables appropriately.
</para>
</listitem>
<listitem>
<para>
Network booting
</para>
<para>
Combined images containing the installer kernel and ramdisk are
located in the <filename>images/netboot/</filename> directory of the
installation tree. They are intended for network booting with TFTP,
but can be used in many ways.
</para>
<para>
The <command>yaboot</command> loader supports TFTP booting for IBM pSeries
and Apple Macintosh. The Fedora Project encourages the use of
<command>yaboot</command> over the <command>netboot</command> images.
</para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>x86 Specifics for Fedora</title>
<para>
This section covers any specific information you may need to
know about Fedora Core and the x86 hardware platform.
</para>
<section>
<title>x86 Hardware Requirements</title>
<para>
In order to use specific features of Fedora Core 6 during or
after installation, you may need to know details of other
hardware components such as video and network cards.
</para>
<section>
<title>Processor and Memory Requirements</title>
<para>
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.
</para>
<para>
Fedora Core 6 requires an Intel Pentium or better
processor, and is optimized for Pentium 4 and later
processors.
</para>
<itemizedlist>
<listitem>
<para>
Recommended for text-mode: 200 MHz Pentium-class or
better
</para>
</listitem>
<listitem>
<para>
Recommended for graphical: 400 MHz Pentium II or
better
</para>
</listitem>
<listitem>
<para>
Minimum RAM for text-mode: 128MiB
</para>
</listitem>
<listitem>
<para>
Minimum RAM for graphical: 192MiB
</para>
</listitem>
<listitem>
<para>
Recommended RAM for graphical: 256MiB
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Hard Disk Space Requirements</title>
<para>
The disk space requirements listed below represent the
disk space taken up by Fedora Core 6 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
<filename>/Fedora/base/stage2.img</filename> on Installation Disc
1 plus the size of the files in <filename>/var/lib/rpm</filename>
on the installed system.
</para>
<para>
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 installation that includes nearly all the
packages. The complete installed packages can occupy over 9 GB of disk
space.
</para>
<para>
Additional space is also required for any user data, and
at least 5% free space should be maintained for proper
system operation.
</para>
</section>
</section>
</section>
<section>
<title>x86_64 Specifics for Fedora</title>
<para>
This section covers any specific information you may need to
know about Fedora Core and the x86_64 hardware platform.
</para>
<section>
<title>x86_64 Hardware Requirements</title>
<para>
In order to use specific features of Fedora Core 6 during or
after installation, you may need to know details of other
hardware components such as video and network cards.
</para>
<section>
<title>x86_64 Memory Requirements</title>
<itemizedlist>
<listitem>
<para>
Minimum RAM for text-mode: 128MiB
</para>
</listitem>
<listitem>
<para>
Minimum RAM for graphical: 256MiB
</para>
</listitem>
<listitem>
<para>
Recommended RAM for graphical: 512MiB
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Hard Disk Space Requirements</title>
<para>
The disk space requirements listed below represent the
disk space taken up by Fedora Core 6 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
<filename>/Fedora/base/stage2.img</filename> on Installation Disc
1 plus the size of the files in <filename>/var/lib/rpm</filename>
on the installed system.
</para>
<para>
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 installation that includes nearly all the
packages. The complete installed packages can occupy over 9 GB of disk
space.
</para>
<para>
Additional space is also required for any user data, and
at least 5% free space should be maintained for proper
system operation.
</para>
</section>
</section>
</section>
</section>
--- NEW FILE BackwardsCompatibility.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-BackwardsCompatibility">
<title>Backwards Compatibility</title>
<!--RAW HTML: <h2>Backwards Compatibility</h2>-->
<para>
Fedora Core provides legacy system libraries for compatibility with
older software. This software is part of the
<systemitem>Legacy Software Development</systemitem>
group, which is not installed by default. Users who require this
functionality may select this group either during installation, or
after the installation process is complete. To install the package
group on a Fedora system, use <menuchoice>
<guimenu>Applications</guimenu><guimenuitem>Add/Remove
Software</guimenuitem></menuchoice>, <application>Pirut</application>, or
enter the following command in a terminal window:
</para>
<screen><![CDATA[su -c 'yum groupinstall "Legacy Software Development"'
]]></screen>
<para>
Enter the password for the <systemitem
class="username">root</systemitem> account when prompted.
</para>
<section>
<title>Compiler Compatibility</title>
<para>
The <code>compat-gcc-34</code> package has been included in this
release for compatibility reasons:
</para>
<para>
<ulink url='https://www.redhat.com/archives/fedora-devel-list/2006-August/msg00409.html'/>
</para>
</section>
</section>
--- NEW FILE Colophon.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Colophon">
<title>Colophon</title>
<!--RAW HTML: <h2>Colophon</h2>-->
<para>
As we use the term, a <emphasis>colophon</emphasis>:
</para>
<itemizedlist>
<listitem>
<para>
recognizes contributors and provides accountability, and
</para>
</listitem>
<listitem>
<para>
explains tools and production methods.
</para>
</listitem>
</itemizedlist>
<section>
<title>Contributors</title>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/BobJensen'>Bob
Jensen</ulink> (editor-in-chief, beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/AndrewMartynov'>Andrew
Martynov</ulink> (translator, Russian)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/AnthonyGreen'>Anthony
Green</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/ChrisLennert'>Chris
Lennert</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DaveMalcolm'>Dave
Malcolm</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DavidEisenstein'>David
Eisenstein</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DavidWoodhouse'>David
Woodhouse</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DiegoB��rigoZacar��o'>Diego
B��rigo Zacar��o</ulink> (translator - Brazilian Portuguese)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DimitrisGlezos'>Dimitris
Glezos</ulink> (translator, tools)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DomingoBecker'>Domingo
Becker</ulink> (translator - Spanish)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/FrancescoTombolini'>Francesco
Tombolini</ulink> (translator, Italian)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/GavinHenry'>Gavin
Henry</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/HugoCisneiros'>Hugo
Cisneiros</ulink> (translator, Brazilian Portuguese)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/JensPetersen'>Jens
Petersen</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/JoeOrton'>Joe
Orton</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Jos��NunoCoelhoPires '>Jos��
Nuno Coelho Pires</ulink> (translator - Portuguese)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/JoshBressers'>Josh
Bressers</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/KarstenWade'>Karsten
Wade</ulink> (beat writer, editor, co-publisher)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/LuyaTshimbalanga'>Luya
Tshimbalanga</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/MagnusLarsson'>Magnus
Larsson</ulink>(translator - Swedish)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/NikosCharonitakis'>Nikos
Charonitakis</ulink>(translator - Greek)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/PanagiotaBilianou'>Panagiota
Bilianou</ulink>(translator - Greek)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/PatrickBarnes'>Patrick
Barnes</ulink>(beat writer, editor)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/PaulWFrields'>Paul
W. Frields</ulink> (tools, editor)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/PawelSadowski'>Pawel
Sadowski</ulink> (translator - Polish)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/RahulSundaram'>Rahul
Sundaram</ulink> (beat writer, editor)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SamFolkWilliams'>Sam
Folk-Williams</ulink> (beat writer, editor)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SekineTatsuo'>Sekine
Tatsuo</ulink> (translator, Japanese)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SimosXenitellis'>Simos
Xenitellis</ulink> (translator - Greek)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SteveDickson'>Steve
Dickson</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/ThomasCanniot'>ThomasCanniot</ulink>
(translator, French)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/ThomasGraf'>Thomas
Graf</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/TommyReynolds'>Tommy
Reynolds</ulink> (tools)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/ValnirFerreira'>Valnir
Ferreira Jr.</ulink> (translator - Brazilian Portuguese)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/YoshinariTakaoka'>Yoshinari
Takaoka</ulink> (translator, tools)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/YuanYijun'>Yuan
Yijun</ulink> (translator, Simplified Chinese)
</para>
</listitem>
<listitem>
<para>
<ulink
url='http://fedoraproject.org/wiki/ZhangYang'>Zhang Yang</ulink>
(translator - simplified Chinese)
</para>
</listitem>
</itemizedlist>
<para>
... and many more translators. Refer to the Web-updated version of these
release notes as we add translators after release:
</para>
<para>
<ulink url="http://fedora.redhat.com/docs/release-notes/"/>
</para>
</section>
<section>
<title>Production Methods</title>
<para>
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.
</para>
</section>
</section>
--- NEW FILE DatabaseServers.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-DatabaseServers">
<title>Database Servers</title>
<!--RAW HTML: <h2>Database Servers</h2>-->
<section>
<title>MySQL</title>
<para>
Fedora now provides <application>MySQL</application> 5.0.
For a list of the enhancements provided by this version, refer to
<ulink url='http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html'/>.
</para>
<para>
For more information on upgrading databases from previous releases
of <application>MySQL</application>, refer to the
<application>MySQL</application> web site at
<ulink url='http://dev.mysql.com/doc/refman/5.0/en/upgrade.html'/>.
</para>
</section>
<section>
<title>PostgreSQL</title>
<para>
This release of Fedora includes
<application>PostgreSQL</application> 8.1. For more
information on this new version, refer to
<ulink url='http://www.postgresql.org/docs/whatsnew'/>.
</para>
<important>
<title>Upgrading Databases</title>
<para>
Fedora Core 4 provided version 8.0 of
<application>PostgreSQL</application>. If you upgrade an existing Fedora
system with a <application>PostgreSQL</application> database, you must
upgrade the database to access the data. To upgrade a database from a
previous version of PostgreSQL, follow the procedure described at <ulink
url='http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html'/>
</para>
</important>
</section>
</section>
--- NEW FILE Desktop.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Desktop">
<title>Fedora Desktop</title>
<!--RAW HTML: <h2>Fedora Desktop</h2>-->
<para>
This section details changes that affect Fedora graphical desktop
users.
</para>
<section>
<title>Desktop Effects</title>
<para>
AIGLX, from the <ulink
url='http://fedoraproject.org/wiki/RenderingProject'>Fedora
Rendering Project</ulink>, is part of the upstream
<application>X.org</application> 7.1 release included in Fedora
Core 6. <application>X.org</application> compositing is enabled by
default in this release. Compositing features in
<application>Metacity</application>, the default window manager
provided in GNOME, are disabled in this release. When desktop
effects are enabled, <application>Metacity</application> is
replaced by <application>Compiz</application>, an OpenGL
compositing window manager that uses AIGLX to provide desktop
effects.
</para>
<para>
To enable the fancy desktop effects, follow these steps:
</para>
<orderedlist numeration='arabic'>
<listitem>
<para>
<menuchoice>
<guimenu>System</guimenu>
<guimenuitem>Preferences</guimenuitem>
<guimenuitem>Desktop Effects</guimenuitem>
</menuchoice>
</para>
</listitem>
<listitem>
<para>
Log out
</para>
</listitem>
<listitem>
<para>
Log back in. <command>compiz</command> should be enabled
</para>
</listitem>
</orderedlist>
<para>
If you get stuck, refer to the following thread:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://www.redhat.com/archives/fedora-devel-list/2006-September/msg00382.ht…'/>
</para>
</listitem>
<listitem>
<para>
<ulink url='http://www.redhat.com/archives/fedora-devel-list/2006-September/msg00383.ht…'/>
</para>
</listitem>
</itemizedlist>
<para>
A list of hardware that supports these effects is available at
<ulink url='http://fedoraproject.org/wiki/RenderingProject/aiglx'/>.
</para>
</section>
<section>
<title>Software Management</title>
<para>
The performance for the <command>yum</command> software management
utility has been greatly improved in Fedora Core 6. The repository
metadata parser has now been implemented in C. A new mirror
management infrastructure also ensures better mirror selection
and, in most cases, faster performance. The
<application>Pirut</application> package management tool and the
<application>Pup</application> software update utility are based
on <command>yum</command>, so their performance is likewise
improved.
</para>
</section>
<section>
<title>GNOME</title>
<para>
This release features
<ulink url='http://www.gnome.org/start/2.16/'>GNOME 2.16</ulink>.
Many of the changes in GNOME 2.16, such as
<application>Tomboy</application> and the
<application>GNOME Power Manager</application>, were added
in Fedora Core 5. Fedora Core 6 also features the
<application>Orca</application> screen reader, and the
<application>Alacarte</application> menu editor previously
available from Fedora Extras.
</para>
<para>
The <application>GNOME Power Manager</application> utility
now provides detailed, graphical information about power
consumption. To access this information, right click on the applet
and select the <guimenuitem>Information</guimenuitem> menu item.
</para>
<para>
The GNOME splash screen has been disabled upstream intentionally.
To enable it, use <command>gconf-editor</command> or the following
command:
</para>
<screen><![CDATA[gconftool-2 --set /apps/gnome-session/options/show_splash_screen --type bool true
]]></screen>
<para>
The lock screen dialog theme is not connected to the selected
screensaver in this release. To enable it, use
<command>gconf-editor</command> or the following command:
</para>
<screen><![CDATA[gconftool-2 --set --type string /apps/gnome-screensaver/lock_dialog_theme "system"
]]></screen>
</section>
<section>
<title>Web Browsers</title>
<para>
There is no longer a <firstterm>browser suite</firstterm> package
contained in Fedora Core 6. The <package>mozilla</package> package
has been removed. For equivalent functionality, use
<package>firefox</package> as a web browser and
<package>thunderbird</package> as a mail client, or use
<package>seamonkey</package>, a browser suite distributed in
Fedora Extras.
</para>
<para>
To better support certain scripts (such as Indic and some CJK scripts),
Fedora builds its <application>Firefox</application> using the
Pango system as its text renderer. Pango is used with the permission of
the Mozilla Corporation. This change may negatively impact performance on
some pages. To disable the use of Pango, set
<envar>MOZ_DISABLE_PANGO=1</envar> in your environment before launching
<application>Firefox</application>.
</para>
<screen>
export MOZ_DISABLE_PANGO=1
/usr/bin/firefox
</screen>
<para>
Gecko based browsers <application>Firefox</application>
and <application>Epiphany</application> now properly
render MathML when using the Pango text backend. Additionally,
several issues with the rendering and behavior of text when using
the Pango text backend have been resolved.
<application>Epiphany</application> now renders using
Pango by default.
</para>
</section>
<section>
<title>Mail Clients</title>
<para>
<application>Thunderbird</application> in Fedora now
enables Pango by default for all locales with permission from the
Mozilla Corporation. This change may negatively impact performance
on some pages. To disable the use of Pango, set
<envar>MOZ_DISABLE_PANGO=1</envar> in your environment before
launching <application>Thunderbird</application>.
</para>
<screen>
export MOZ_DISABLE_PANGO=1
/usr/bin/thunderbird
</screen>
</section>
</section>
--- NEW FILE Devel.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Devel">
<title>Development</title>
<!--RAW HTML: <h2>Development</h2>-->
<para>
This section covers various development tools and features.
</para>
<section>
<title>Runtime</title>
<para>
These are the new features in <package>glibc</package>:
</para>
<itemizedlist>
<listitem>
<para>
Support for priority inheriting and priority protecting
mutexes. These are two features described in the POSIX
standards.
</para>
<itemizedlist>
<listitem>
<para>
Priority inheriting mutexes automatically prevent
priority inversion caused by waiting for the
availability of mutexes. The kernel automatically boosts
the priority of the thread holding the mutex until it
unlocks the mutex.
</para>
</listitem>
<listitem>
<para>
Priority protection allows to specify a priority that
all threads that acquire the mutex will run with until
the mutex is unlocked. This feature is not available for
robust mutexes.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
The destination address sorting performed by the
<interface>getaddrinfo()</interface> interface for hostname lookup can
now be customized by rules in the <filename>/etc/gai.conf</filename>
file.
</para>
</listitem>
<listitem>
<para>
Significant speed-ups in NIS and NIS+ processing.
</para>
</listitem>
<listitem>
<para>
RFC 3542 support completed (advanced socket APIs for IPv6).
</para>
</listitem>
<listitem>
<para>
Significant speed-ups of dynamic symbol lookup.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Tools</title>
<para>
The linker includes support for the new ELF symbol hash table
format. Use the <option>--hash-style</option> option of the linker
to select the format(s).
</para>
<section>
<title>Kernel header files</title>
<para>
This release of Fedora has been built using Linux kernel
headers exported directly from the kernel, using the new
<option>headers_install</option> feature of the 2.6.18 kernel.
Thus, the <package>glibc-kernheaders</package> package has been
removed and replaced with <package>kernel-headers</package>, a
subpackage of <package>kernel</package>.
</para>
<para>
Developers may notice some changes between these new kernel
headers and what was present before, including but not limited
to the following:
</para>
<itemizedlist>
<listitem>
<para>
The <filename><linux/compiler.h></filename> header file has
been removed, since it contains nothing of use to
userspace.
</para>
</listitem>
<listitem>
<para>
The <systemitem class="macro">_syscallX()</systemitem> macros are removed. Userspace
should use <systemitem class="macro">syscall()</systemitem> from the C library
instead.
</para>
</listitem>
<listitem>
<para>
The <systemitem class="macro">PAGE_SIZE</systemitem> macro is
removed from some architectures, since the page size is variable.
Userspace should be using <systemitem
class="macro">sysconf(_SC_PAGE_SIZE)</systemitem> or <systemitem
class="macro">getpagesize()</systemitem> instead.
</para>
</listitem>
<listitem>
<para>
The <filename><asm/atomic.h></filename> and
<filename><asm/bitops.h></filename> header files have been
removed. These were not designed for use in userspace, and
would fail to compile on some architectures while silently
giving non-atomic behaviour on others. The C compiler
provides its own
<ulink url='http://gcc.gnu.org/onlinedocs/gcc-4.1.1/gcc/Atomic-Builtins.html#Atomic-Bui…'>atomic
builtin functions</ulink> that are suitable for use in
userspace programs instead.
</para>
</listitem>
<listitem>
<para>
Content that was previously protected with <code>#ifdef
__KERNEL__</code> is now elided completely with the
<command>unifdef</command> tool. Defining
<code>__KERNEL___</code> in order to see parts that
should not be visible to userspace is no longer effective.
</para>
</listitem>
</itemizedlist>
<para>
In addition, some other header files that xare not suitable
for use in userspace have been removed, and still more headers
have been edited to remove unsuitable content.
</para>
<para>
<note>
<title>Kernel header changes are not Fedora-specific</title>
<para>
These changes are inherited from the upstream kernel and
are not specific to Fedora. Any distribution using the
current officially-exported kernel headers would be the
same.
</para>
</note>
</para>
</section>
<section>
<title>GCC Compiler Collection</title>
<para>
This release of Fedora has been built with GCC 4.1, which
is included with the distribution.
</para>
<section>
<title>Caveats</title>
<itemizedlist>
<listitem>
<para>
Fedora developers have introduced changes in the ELF
<code>.hash</code> section that provides symbols for dynamic
linking. This new <code>.gnu.hash</code> section, which is
produced with the new default
<option>--hash-style=gnu</option> option for
<command>gcc</command>, serves the same purpose as
previous hash sections. It provides, however, an
approximately 50% increase in dynamic linking speed.
Binaries and libraries produced with the new hashing
function are incompatible with older
<systemitem class="library">glibc</systemitem> and dynamic linker releases. To
use the old-style hashing routines for compatibility
with older <systemitem class="library">glibc</systemitem>-based systems, pass
the <option>--hash-style=sysv</option> option instead.
</para>
</listitem>
<listitem>
<para>
You need GDB 6.1 or newer to debug binaries, unless
they are compiled using the
<option>-fno-var-tracking</option> compilation option.
</para>
</listitem>
<listitem>
<para>
The <option>-fwritable-strings</option> option is no
longer accepted.
</para>
</listitem>
<listitem>
<para>
English-language diagnostic messages now use Unicode
quotes. If you cannot read this, set your
<envar>LC_CTYPE</envar> environment variable to
<systemitem class="constant">C</systemitem> or change your terminal emulator.
</para>
</listitem>
<listitem>
<para>
The <filename>specs</filename> file is no longer installed
on most systems. Ordinary users will not notice, but
developers who need to alter the file can use the
<option>-dumpspecs</option> option to generate the file
for editing.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Code Generation</title>
<itemizedlist>
<listitem>
<para>
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.
</para>
</listitem>
<listitem>
<para>
Autovectorization is supported. This technique
achieves higher performance for repetitive loop
code, in some circumstances.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Language Extensions</title>
<itemizedlist>
<listitem>
<para>
The new sentinel attribute causes the compiler to
issue a warning if a function such as
<function>execl(char *path, const char *arg,
...)</function>, which requires a NULL list terminator,
is missing the NULL.
</para>
</listitem>
<listitem>
<para>
The <systemitem>cast-as-lvalue</systemitem>,
<systemitem>conditional-expression-as-lvalue</systemitem>, and
<systemitem>compund-expression-as-lvalue</systemitem> extensions
have been removed.
</para>
</listitem>
<listitem>
<para>
The <systemitem class="macro">#pragma pack()</systemitem>
semantics are now closer to those used by other compilers.
</para>
</listitem>
<listitem>
<para>
Taking the address of a variable declared with the register
modifier now generates an error instead of a warning.
</para>
</listitem>
<listitem>
<para>
Arrays of incomplete element types now generate an
error. This implies no forward reference to
structure definitions.
</para>
</listitem>
<listitem>
<para>
The basic compiler, without any optimization
(<option>-O0</option>), has been measured as much as 25% faster in
real-world code.
</para>
</listitem>
<listitem>
<para>
Libraries may now contain function-scope static
variables in multi-threaded programs. Embedded
developers can use the
<option>-fno-threadsafe-statics</option> to turn off
this feature, but ordinary users should never do
this.
</para>
</listitem>
</itemizedlist>
</section>
</section>
</section>
<section>
<title>Ruby</title>
<para>
The standard search path for Ruby libraries, <code>$:</code>, has
changed in accordance with
<ulink url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/Packaging/Ruby'>the
packaging guidelines</ulink>. Changes were also made to some of
the entries in <code>Config::CONFIG</code> in the
<filename>rbconfig</filename> module. The most important changes include:
</para>
<itemizedlist>
<listitem>
<para>
<filename>sitedir</filename> and related directories
(<filename>sitelibdir</filename>, <filename>sitearchdir</filename>) are now
under <filename>rubylibdir</filename>. Instead of
<filename>/usr/lib/site_ruby</filename> they are underneath
<filename>/usr/lib/ruby/site_ruby</filename>.
</para>
</listitem>
<listitem>
<para>
The directories for architecture-independent pure Ruby code
are always under <filename>/usr/lib</filename>, even on x86_64
architecture, where they used to be under
<filename>/usr/lib64</filename>. This change affects the
<code>Config::CONFIG</code> entries <filename>rubylibdir</filename>
and <filename>sitelibdir</filename>.
</para>
</listitem>
</itemizedlist>
<para>
Directories that were previously in <code>$:</code> remain there for the
time being, so that existing code, such as
<filename>/usr/lib/site_ruby</filename>, does not need to be modified.
These directories are deprecated though, and will be removed by the
release of Fedora Core 8. Build Ruby RPM packages in accordance with
<ulink
url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/Packaging/Ruby'>the
packaging guidelines</ulink>. In particular, Ruby libraries should only
be installed into <filename>sitelibdir</filename> and
<filename>sitearchdir</filename>. You should also follow this rule for
Ruby code that is not packaged as an RPM.
</para>
</section>
</section>
--- NEW FILE Entertainment.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Entertainment">
<title>Games and Entertainment</title>
<!--RAW HTML: <h2>Games and Entertainment</h2>-->
<para>
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 <package>gnome-games</package>) and KDE
(<package>kdegames</package>). Fedora Extras provides additional games
that span every major genre.
</para>
<para>
The Fedora Project website features a section dedicated to games
that details many of the available games, including overviews and
installation instructions. For more information, refer to
<ulink url='http://fedoraproject.org/wiki/Games'/>.
</para>
</section>
--- NEW FILE Extras.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Extras">
<title>Fedora Extras - Community Package Repository</title>
<!--RAW HTML: <h2>Fedora Extras - Community Package Repository</h2>-->
<itemizedlist>
<listitem override='none'>
<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
<para>
Fedora Extras is an extension of Fedora Core that provides many
additional packages for users of the Fedora distribution.
</para>
</listitem>
</itemizedlist>
<section>
<title>Using the Repository</title>
<para>
<note>
<title>Fedora Extras are Available by Default</title>
<para>
Fedora systems automatically use both the Fedora Core and
Fedora Extras repositories to install and update software.
</para>
</note>
</para>
<para>
To install software from either the Core or Extras repositories, choose
<menuchoice>
<guimenu>Applications</guimenu>
<guimenuitem>Add/Remove Software</guimenuitem></menuchoice>. Enter the
<systemitem class="username">root</systemitem> password when prompted.
Select the software you require from the list, and choose
<guilabel>Apply</guilabel>.
</para>
<para>
You may also install software with the <command>yum</command>
command-line utility. For example, this command automatically
installs the <command>abiword</command> package, and all of the
dependencies that are required:
</para>
<screen><![CDATA[su -c 'yum install abiword'
]]></screen>
<para>
Enter the <systemitem class="username">root</systemitem> password when
prompted.
</para>
</section>
<section>
<title>About Fedora Extras</title>
<para>
As of the release of Fedora Core
<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
6, 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:
</para>
<itemizedlist>
<listitem>
<para>
<package>abiword</package> - elegant word-processing application
</para>
</listitem>
<listitem>
<para>
<package>balsa</package> - lightweight e-mail reader
</para>
</listitem>
<listitem>
<para>
<package>bash-completion</package> - advanced command-line
completion for power users
</para>
</listitem>
<listitem>
<para>
<package>bluefish</package> - HTML editor
</para>
</listitem>
<listitem>
<para>
<package>clamav</package> - open source anti-virus scanner for
servers and desktops
</para>
</listitem>
<listitem>
<para>
<package>exim</package> - flexible and powerful mail transfer agent
</para>
</listitem>
<listitem>
<para>
<package>fuse</package> - tool for attaching non-standard devices
and network services as directories
</para>
</listitem>
<listitem>
<para>
<package>fwbuilder</package> - graphical utility for building Linux
and Cisco firewall rulesets
</para>
</listitem>
<listitem>
<para>
<package>gaim-guifications</package> - enhancements to the Gaim
Instant Messenger
</para>
</listitem>
<listitem>
<para>
<package>gdesklets</package> - widgets for the GNOME desktop
</para>
</listitem>
<listitem>
<para>
<package>gnumeric</package> - powerful spreadsheet application
</para>
</listitem>
<listitem>
<para>
<package>gramps</package> - genealogy application
</para>
</listitem>
<listitem>
<para>
<package>inkscape</package> - illustration and vector drawing
application
</para>
</listitem>
<listitem>
<para>
<package>koffice</package> - complete office suite for the KDE
desktop
</para>
</listitem>
<listitem>
<para>
<package>mail-notification</package> - alerts you as new mail
arrives
</para>
</listitem>
<listitem>
<para>
<package>mediawiki</package> - the Wikipedia solution for
collaborative websites
</para>
</listitem>
<listitem>
<para>
<package>nautilus-open-terminal</package> - extension to the GNOME
file manager
</para>
</listitem>
<listitem>
<para>
<package>pan</package> - the Usenet news reader
</para>
</listitem>
<listitem>
<para>
<package>revelation</package> - password management utility
</para>
</listitem>
<listitem>
<para>
<package>scribus</package> - desktop publishing (DTP) application
</para>
</listitem>
<listitem>
<para>
<package>wine</package> - a compatibility layer to run Windows(TM)
programs
</para>
</listitem>
<listitem>
<para>
<package>xfce</package> - lightweight desktop environment
</para>
</listitem>
<listitem>
<para>
<package>xmms</package> - the popular audio player
</para>
</listitem>
<listitem>
<para>
lots of Perl and Python tools and libraries
</para>
</listitem>
<listitem>
<para>
...and much more!
</para>
</listitem>
</itemizedlist>
<para>
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 the project.
</para>
<para>
To learn more about how to use Fedora Extras or how to get
involved, refer to
<ulink url='http://fedoraproject.org/wiki/Extras'/>.
</para>
</section>
<section>
<title>Package Updates</title>
<para>
This section discusses changes in Fedora Extras packages that
affect this release of Fedora Core.
</para>
<section>
<title>exim-sa</title>
<para>
The <package>exim-sa</package> package is deprecated, and is not
provided in Fedora Extras 6. It was the original implementation
of <ulink
url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/SpamAssassin'>SpamAssassin</ulink>
integration with Exim, and was functionally similar to
<package>sendmail</package> milters or
<package>postfix</package> filters. However, that functionality
is rather limited, and Exim now has far better support for
content checking, fully integrated into its general-purpose
Access Control Lists.
</para>
<para>
Since the <option>sa_exim</option> feature was not enabled in
the default configuration, the package can normally be safely
uninstalled to allow Exim to be upgraded. Users who have
modified their configuration to use <option>sa_exim</option>
features should either reconfigure to use Exim's full content
scanning abilities or rebuild the package for themselves to
include the <package>exim-sa</package> subpackage. For further
details on Exim's built-in content scanning, see the <ulink
url='http://www.exim.org/exim-html-4.62/doc/html/spec_html/ch40.html'>Exim
documentation</ulink>.
</para>
</section>
<section>
<title>mail-notification</title>
<para>
The <package>mail-notification</package> package has been split.
The <application>Evolution</application> plugin is now in a
separate package called
<package>mail-notification-evolution-plugin</package>. When you
update the <package>mail-notification</package> package, the
plugin is added automatically.
</para>
</section>
</section>
</section>
--- NEW FILE FAQ.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section>
<title>FAQ</title>
<informaltable>
<tgroup cols='1'>
<colspec colname='col_0'/>
<tbody>
<row>
<entry colsep='1' rowsep='1'></entry>
</row>
<row>
<entry colsep='1' rowsep='1'><para> <emphasis role='strong'>Frequently Asked Questions</emphasis> </para></entry>
</row>
<row>
<entry colsep='1' rowsep='1'><para> Just like any Linux distribution, we get a lot of questions. Some are asked regularly, and we try to answer some of these Frequently Asked Questions here. You might also be interested in the <ulink url='http://docbook.wikiwikiweb.de/FedoraMyths'>FedoraMyths</ulink> page, which details the facts behind a few common myths about Fedora. If this FAQ doesn't answer your question, refer to the <ulink url='#links'>Fedora Resources</ulink> listed at the bottom of the page. </para></entry>
</row>
<row>
<entry align='center' colsep='1' rowsep='1'><para> <emphasis role='strong'>Table of Contents</emphasis> </para></entry>
</row>
<row>
<entry colsep='1' rowsep='1'></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<section>
<title>Getting Started</title>
<section>
<title>Why should I be using Fedora?</title>
<para>
You should be using Fedora because it includes the best and
latest collection of robust free and open source software
available. The
<ulink url='http://docbook.wikiwikiweb.de/Overview'>Overview</ulink>
details many of Fedora's strengths:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Overview'>http://fedoraproject.org/wiki/Overview</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Where can I get Fedora? Can I redistribute Fedora or make derivatives
from it?</title>
<para>
You can download, use and redestribute Fedora and we strongly
encourage you to do so. The open source licenses (such as the
GPL) governing the source code allow you to redistribute or
modify Fedora but any use must comply with the
<ulink url='http://fedora.redhat.com/about/trademarks/guidelines/'>Fedora
Trademark Guidelines</ulink>. Details are available at
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Distribution'>http://fedoraproject.org/wiki/Distribution</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Is my hardware compatible with Fedora?</title>
<para>
Linux is able to support every class of component and
peripheral. Fedora Core includes all of the drivers provided by
the projects that are responsible for Linux hardware support.
The Fedora Core installation process automatically detects the
supported hardware on your computer.
</para>
<para>
Some specific models of hardware are not yet supported under
Linux, or require proprietary drivers from the manufacturer. If
Fedora does not automatically detect a device, you may need to
install additional drivers or firmware.
</para>
<itemizedlist>
<listitem override='none'>
<informaltable>
<tgroup cols='1'>
<colspec colname='col_0'/>
<tbody>
<row>
<entry colsep='1' rowsep='1'><para> <inlinemediaobject><imageobject><imagedata width='16' fileref='http://docbook.wikiwikiweb.de/wiki/modern/img/icon-info.png' depth='16'/></imageobject><textobject><phrase>{i}</phrase></textobject></inlinemediaobject> <emphasis role='strong'>Network Connections</emphasis> </para></entry>
</row>
<row>
<entry colsep='1' rowsep='1'><para> Modems and wireless network connections require additional configuration after the installation process completes. Refer to the question on network connections for more information. </para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</listitem>
</itemizedlist>
<para>
The following websites provide more detailed information on
Linux support for various types of hardware:
</para>
<itemizedlist>
<listitem>
<para>
Graphics adaptors -
<ulink url='http://wiki.x.org/wiki/FAQ'>http://wiki.x.org/wiki/FAQ</ulink>
</para>
</listitem>
<listitem>
<para>
Audio adaptors -
<ulink url='http://www.alsa-project.org/'>http://www.alsa-project.org/</ulink>
</para>
</listitem>
<listitem>
<para>
Printers -
<ulink url='http://www.linuxprinting.org/'>http://www.linuxprinting.org/</ulink>
</para>
</listitem>
<listitem>
<para>
Digital cameras -
<ulink url='http://www.gphoto.org/'>http://www.gphoto.org/</ulink>
</para>
</listitem>
<listitem>
<para>
Scanners and imaging devices -
<ulink url='http://www.sane-project.org/'>http://www.sane-project.org/</ulink>
</para>
</listitem>
<listitem>
<para>
Modems -
<ulink url='http://linmodems.org/'>http://linmodems.org/</ulink>
</para>
</listitem>
<listitem>
<para>
PCMCIA cards -
<ulink url='http://prism54.org/newdrivers.html'>http://prism54.org/newdrivers.html</ulink>,
<ulink url='http://rt2x00.serialmonkey.com/wiki/index.php/Hardware'>http://rt2x00.serialmonkey.com/wiki/index.php/Hardware</ulink>,
<ulink url='http://ralink.rapla.net/'>http://ralink.rapla.net/</ulink>,
<ulink url='http://zd1211.ath.cx/'>http://zd1211.ath.cx/</ulink>
</para>
</listitem>
</itemizedlist>
<para>
The Fedora Release Notes document known issues with specific
device models:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedora.redhat.com/docs/release-notes/'>http://fedora.redhat.com/docs/release-notes/</ulink>
</para>
</listitem>
</itemizedlist>
<para>
For more information on the Fedora hardware support policy,
refer to the question on hardware
<ulink url='#HWCert'>certification</ulink>.
</para>
</section>
<section>
<title>How can I install Fedora?</title>
<para>
Fedora provides a very user-friendly installation system, with
both graphical and text interfaces. Read the Fedora Installation
Guide for step by step details:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedora.redhat.com/docs/install-guide/'>http://fedora.redhat.com/docs/install-guide/</ulink>
</para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>Using Fedora</title>
<section>
<title>How do I configure network connections? How does Fedora support wireless
connections?</title>
<para>
By default, Fedora configures the network cards on your computer
to automatically obtain the correct network settings with DHCP.
If your computer connects to a wired network or DSL router, no
further configuration is required.
</para>
<para>
For other types of connection, you may wish to install
<ulink url='http://docbook.wikiwikiweb.de/Tools/NetworkManager'>Network
Manager</ulink>. This new system provides automatic networking
and wireless configuration, as well as an interface for VPN
connections. Laptops may switch seamlessly between networks with
<ulink url='http://docbook.wikiwikiweb.de/NetworkManager'>NetworkManager</ulink>.
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Tools/NetworkManager'>http://fedoraproject.org/wiki/Tools/NetworkManager</ulink>
</para>
</listitem>
</itemizedlist>
<para>
Fedora also provides the
<emphasis role='strong'>system-config-network</emphasis>
utility, which allows you to manually configure most networking
options. To run
<emphasis role='strong'>system-config-network</emphasis>, choose
<emphasis>System => Administration => Network</emphasis>.
</para>
</section>
<section>
<title>How do I install new software on Fedora? Is there anything like APT?</title>
<para>
The
<screen><![CDATA[yum]]></screen>
utility helps you manage the software on your system. The
<screen><![CDATA[yum]]></screen>
utility accesses Web sites, known as
<emphasis>repositories</emphasis>, to download and install the
latest versions of software packages. Fedora Core 5 systems also
include a graphical interface to
<screen><![CDATA[yum]]></screen>
, which appears on the Main Menu under <emphasis>Applications >
Add/Remove Software</emphasis>.
</para>
<para>
From Fedora Core 4 onwards, systems are automatically configured
to use both the Core and Extras repositories maintained by the
Fedora Project. The Core repositories includes all of the
packages on the installation discs. Fedora Extras provides over
2,000 additional software packages to supplement the Core
release. To obtain software from other sources, configure
<screen><![CDATA[yum]]></screen>
to use the relevant repositories.
</para>
<para>
Refer to this page for more information on
<screen><![CDATA[yum]]></screen>
:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Tools/yum'>http://fedoraproject.org/wiki/Tools/yum</ulink>
</para>
</listitem>
</itemizedlist>
<para>
Fedora recommends that you avoid using the older APT-RPM utility
for software management. APT-RPM is not compatible with 64-bit
systems, and is no longer under active development. See the
<ulink url='http://docbook.wikiwikiweb.de/Tools/Apt'>APT</ulink>
page for details:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Tools/Apt'>http://fedoraproject.org/wiki/Tools/Apt</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>How do I keep Fedora systems updated?</title>
<para>
To perform a system update on Fedora Core 5, select
<emphasis>Applications => System Tools => Software
Updater</emphasis>. This utility updates all of your system's
software that is provided by
<screen><![CDATA[yum]]></screen>
repositories.
</para>
<para>
To start a full system update from the command-line, enter the
following at the prompt:
</para>
<screen><![CDATA[ su -c 'yum update'
]]></screen>
<para>
Enter the
<screen><![CDATA[root]]></screen>
password when prompted.
</para>
<para>
Fedora Core 4 and previous releases include the
<screen><![CDATA[up2date]]></screen>
application and a desktop Alert Icon. The
<screen><![CDATA[up2date]]></screen>
application has been superceded by the
<emphasis role='strong'>Software Updater</emphasis> in Fedora 5.
</para>
</section>
<section>
<title>Can Fedora update itself automatically?</title>
<para>
Yes, although automatic updates may not be appropriate for all
systems. Refer to
<ulink url='http://fedoraproject.org/wiki/AutoUpdates'>http://fedoraproject.org/wiki/AutoUpdates</ulink>
for more details on whether and how to use this feature on your
Fedora system.
</para>
</section>
<section>
<title>How can I get notices of new software releases?</title>
<para>
To receive notification of new and updated software as it is
made available, you may subscribe to either the announcements
mailing list, or the RSS feeds:
</para>
<itemizedlist>
<listitem>
<para>
Fedora Project package announcements mailing list :
<ulink url='https://www.redhat.com/mailman/listinfo/fedora-package-announce-list'>https://www.redhat.com/mailman/listinfo/fedora-package-announce-list</ulink>
</para>
</listitem>
<listitem>
<para>
Fedora Project RSS feeds:
<ulink url='http://fedoraproject.org/infofeed/'>http://fedoraproject.org/infofeed/</ulink>
</para>
</listitem>
</itemizedlist>
<para>
Other major announcements can be recieved by subscribing to the
Fedora Project announcements mailing list
</para>
<itemizedlist>
<listitem>
<para>
Fedora Project announcements mailing list:
<ulink url='https://www.redhat.com/mailman/listinfo/fedora-announce-list'>https://www.redhat.com/mailman/listinfo/fedora-announce-list</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Why doesn't Fedora include support for proprietary formats like MP3 or
MPEG?</title>
<para>
The MP3 and MPEG formats are covered by patents, and the patent
owners have not released the technologies under licenses which
are compatible with Fedora's requirements.
</para>
<para>
Fedora only supports and includes free and open source software.
Technologies under stringent copyright or patent restrictions
are not included in Fedora. For more information about
multimedia support in Fedora, including more about MP3 and MPEG
support, see the Multimedia section:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Multimedia'>http://fedoraproject.org/wiki/Multimedia</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Why doesn't Fedora include DVD video playback support?</title>
<para>
The DVD video formats are covered by patents, and the patent
owners have not released the technologies under licenses which
are compatible with Fedora's requirements. Many DVD videos also
use a copy protection technology, and the code necessary to play
those videos may violate the Digital Millennium Copyright Act
(DMCA), a copyright law of the United States.
</para>
<para>
Fedora only supports and includes free and open source software.
Technologies under stringent copyright or patent restrictions
are not included in Fedora. For more information about
multimedia support in Fedora, including more about DVD video
support, see the Multimedia section:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Multimedia'>http://fedoraproject.org/wiki/Multimedia</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Why doesn't Fedora include proprietary software like Adobe's Acrobat
Reader, Adobe's Flash Player, or RealPlayer?</title>
<para>
Fedora only supports and includes free and open source software.
No proprietary programs are included in Fedora Core or Fedora
Extras. Many of these programs are available for Fedora, and you
are free to obtain them from another vendor. For more
information, see the
<ulink url='http://docbook.wikiwikiweb.de/ForbiddenItems'>ForbiddenItems</ulink>
page:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Does Fedora include Java?</title>
<para>
Fedora includes open source software to run and develop Java
applications, along with several well-known open source Java
applications. Developers are currently finalizing an open source
Web browser plugin for Java applets.
</para>
<para>
Please refer to our
<ulink url='http://docbook.wikiwikiweb.de/JavaFAQ'>JavaFAQ</ulink>
page for information regarding Java and Fedora Core:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/JavaFAQ'>http://fedoraproject.org/wiki/JavaFAQ</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>What is SELinux, and where can I read more about it?</title>
<para>
Fedora is the first mainstream operating system in the world to
provide a Mandatory Access Control (MAC) security system by
default, using the SELinux framework. The SELinux configuration
in Fedora Core 4 and above provides enhanced security by
restricting the privileges of processes running on a Fedora
system. These restrictions drastically reduce the impact of
security vulnerabilities, since services have only limited
access to the rest of the system. SELinux in Fedora Core also
has a 'strict' policy, which is useful for security-sensitive
environments. There are other security systems enabled through
the SELinux framework, such as MLS, MCS and RBAC, which are
provided in Fedora Core 5 and above.
</para>
<para>
Refer to the following document for more information on the
SELinux implementation in Fedora:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SELinux'>http://fedoraproject.org/wiki/SELinux</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>What is Xen? Where can I learn about setting up Xen?</title>
<para>
Xen enables multiple operating systems to run simultaneously on
the same machine with little reduction in overall performance.
Each operating system is allocated some of the resources of the
host computer. With Xen, administrators may also move a running
operating system between machines without disrupting or shutting
down services. Existing virtual machine and virtual server
products offer similar facilities, but lack the same level of
performance and integration that the Xen approach offers.
</para>
<para>
Fedora Core 4 includes experimental Xen support. Fedora Core 5
and above provide a more robust implementation. The
<ulink url='http://docbook.wikiwikiweb.de/Tools/Xen%20'>Xen</ulink>
page can help you get started:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Tools/Xen'>http://fedoraproject.org/wiki/Tools/Xen</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>When is the next release of Fedora? What is the release schedule?</title>
<para>
See the Fedora Project
<ulink url='http://docbook.wikiwikiweb.de/Core/Schedule%20'>schedule</ulink>
page:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Core/Schedule'>http://fedoraproject.org/wiki/Core/Schedule</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>How long is each release of Fedora maintained?</title>
<para>
Each Fedora release is updated with new software until it is
moved into <emphasis>maintenance mode</emphasis>. Once the
product a new Fedora release reaches the test2 stage, the Fedora
release two versions before it moves into maintenance mode. At
that point, the older release is transferred to Fedora Legacy,
the community maintenance project, which continues to provide
critical updates for that release. For example, Fedora 3 was
updated until Fedora Core 5 test2 was released, and is now
maintained by the Fedora Legacy project.
</para>
<para>
To use the Fedora Legacy updates, see the Fedora Legacy wiki
pages:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Legacy'>http://fedoraproject.org/wiki/Legacy</ulink>
</para>
</listitem>
</itemizedlist>
<para>
The Fedora release lifecycle is explained in more detail:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/LifeCycle'>http://fedoraproject.org/wiki/LifeCycle</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>What is the errata policy for The Fedora Project?</title>
<para>
Security updates, bugfix updates, and new feature updates will
all be available, through Red Hat and third parties. Updates may
be staged (first made available for public qualification, then
later for general consumption) when appropriate. In drastic
cases, we may remove a package from The Fedora Project if we
judge that a necessary security update is too
problematic/disruptive to the larger goals of the project.
Availability of updates should not be misconstrued as support
for anything other than continued development and innovation of
the code base.
</para>
<para>
Red Hat will not be providing an SLA (Service Level Agreement)
for resolution times for updates for The Fedora Project.
Security updates will take priority. For packages maintained by
external parties, Red Hat may respond to security holes by
deprecating packages if the external maintainers do not provide
updates in a reasonable time. Users who want support, or
maintenance according to an SLA, may purchase the appropriate
Red Hat Enterprise Linux product for their use.
</para>
</section>
<section>
<title>I have an older Fedora release. Can I upgrade my existing installation?</title>
<para>
Yes. For more information on upgrading options, refer to the
<ulink url='http://docbook.wikiwikiweb.de/DistributionUpgrades'>DistributionUpgrades</ulink>
page:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DistributionUpgrades'>http://fedoraproject.org/wiki/DistributionUpgrades</ulink>
</para>
</listitem>
</itemizedlist>
<para>
We recommend that you <emphasis>do not</emphasis> try to upgrade
a Fedora system with
<screen><![CDATA[yum]]></screen>
. If you choose to do so, however, this page provides some
information on the necessary steps to minimize the issues:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/YumUpgradeFaq'>http://fedoraproject.org/wiki/YumUpgradeFaq</ulink>
</para>
</listitem>
</itemizedlist>
<para>
The information on the page listed above is provided by the
community, without any guarantees. The Fedora Project does not
recommend upgrading systems with software management
applications.
</para>
</section>
</section>
<section>
<title>Help and Support</title>
<section>
<title>Where can I find help?</title>
<para>
You can find documentation and get help through forums, IRC, or
mailing lists from others in the Fedora community. See the
<ulink url='http://docbook.wikiwikiweb.de/Communicate'>Communicate</ulink>
page for more information:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>
</para>
</listitem>
</itemizedlist>
<para>
Please do not contact Fedora developers directly, or use the
special developer channels, for end-user support. The developers
are very busy writing and maintaining Fedora software and do not
have much spare time for these issues.
</para>
</section>
<section>
<title>I hear all of these terms that are unfamiliar, what do they mean?</title>
<para>
For definitions to many of the most common terms, refer to the
<ulink url='http://docbook.wikiwikiweb.de/FAQ/Glossary'>Glossary</ulink>.
</para>
</section>
<section>
<title>Where can I report bugs or request features for software packages
existing in Fedora?</title>
<para>
Refer to the
<ulink url='http://docbook.wikiwikiweb.de/BugsAndFeatureRequests'>BugsAndFeatureRequests</ulink>
page for guidance on this.
</para>
</section>
<section>
<title>Where I can learn more about security features and status in Fedora? How
do I report a security bug?</title>
<para>
Refer to the
<ulink url='http://docbook.wikiwikiweb.de/Security'>Security</ulink>
page for all of this information.
</para>
</section>
<section>
<title>I'm experiencing a problem, and I think it might be my hardware. Where
should I look?</title>
<para>
Check the
<ulink url='http://docbook.wikiwikiweb.de/HardwareProblems'>HardwareProblems</ulink>
page before posting bugs that might be known hardware problems.
</para>
</section>
<section>
<title>I have a question that isn't in this list. Where else can I find help?</title>
<para>
See the links for <ulink url='#links'>Fedora Resources</ulink>
at the bottom of this page.
</para>
</section>
</section>
<section>
<title>About Fedora</title>
<section>
<title>What is Fedora?</title>
<para>
<!--GetVal-macro not supported by the docbook formatter, but giving it a shot anyway-->
Fedora is a set of projects sponsored by Red Hat and guided by
the contributors. These projects are developed by a large
community of people who strive to provide and maintain the very
best in free, open source software and standards. Fedora Core,
the central Fedora project, is an operating system and platform
based on Linux which is always free for anyone to use, modify,
and distribute, now and forever.
</para>
</section>
<section>
<title>What are the objectives of Fedora?</title>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Objectives'>http://fedoraproject.org/wiki/Objectives</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Why a project instead of a product?</title>
<para>
A global steering committee at Red Hat decided that Red Hat
Linux was suffering from too many compromises as a retail
product, and that the company should redirect efforts toward
creating a community-based project. Rather than being subject to
retail product delivery schedules, Fedora Core is released on
schedules set by a decision-making process that is open, and
influenced by the community. The Fedora Project is managed by a
<ulink url='http://docbook.wikiwikiweb.de/Board'>board</ulink>
of community members and Red Hat employees, with Red Hat
providing significant funding and other services such as
bandwidth and hosting, broad direction, engineering, and
marketing.
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Projects'>http://fedoraproject.org/wiki/Projects</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Board'>http://fedoraproject.org/wiki/Board</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>What are the core benefits of this change?</title>
<para>
Changing the product to a project will:
</para>
<itemizedlist>
<listitem>
<para>
Ensure that users can get the latest bits as quickly as
possible.
</para>
</listitem>
<listitem>
<para>
Create new opportunities for developers and users to
participate in The Fedora Project development by opening up
the full development process for anyone to see and join if
they'd like.
</para>
</listitem>
<listitem>
<para>
Allow us to use The Fedora Project to develop and mature the
latest, greatest technologies.
</para>
</listitem>
<listitem>
<para>
Speed up the development process, taking better advantage of
the inherent strengths of the open source model.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Will Red Hat provide formal technical support for The Fedora Project?</title>
<para>
No, no formal Web or phone support for The Fedora Project will
be available from Red Hat. Red Hat's supported product line will
be based in part on Fedora Core, and our development will be
done externally as part of The Fedora Project as much as
possible. Each new release of our supported products will be
based in part on a recent release of Fedora Core.
</para>
</section>
<section>
<title>Will Red Hat's supported products contain all the packages found in
Fedora Core?</title>
<para>
In order to focus our efforts and limit support costs, we will
probably select a subset of packages found in Fedora Core to
include in the supported product line. One of the goals of The
Fedora Project is to encourage a pool of high-quality add-on
packages; if we're successful, there will be so many we won't be
able to support all of them.
</para>
</section>
<section>
<title>Will Fedora Core be sold in retail?</title>
<para>
Fedora Core will not be sold through the retail channel as a
shrinkwrapped box. There is no list price for Fedora Core. The
rapid development pace we expect for Fedora Core doesn't suit
retail distribution ��� it is a lot of work to get a box product
in and out of the channel, and retail isn't set up to
efficiently handle software that is updated as often as every
six months. Also, the creation of packaging and other materials
that are necessary for retail significantly slows down the time
to market, which means that users can't get the freshest bits
when they are still truly fresh. Further information on Red
Hat's retail product line is available at the Red Hat website.
</para>
</section>
<section>
<title>How will The Fedora Project be made available to the public?</title>
<para>
Fedora Core releases will be available as ISO images for both
CDs and DVDs, and will also be available through other channels
such as third-party online sales of physical media; distribution
at Linux User Groups, included in magazines and in books, and
maybe even handed out at trade shows. The bits may be actively
pushed into content sharing networks such as
<ulink url='http://docbook.wikiwikiweb.de/BitTorrent'>BitTorrent</ulink>.
(Not all mechanisms will be used for each release, except that
ISOs will be freely available for each release.)
</para>
</section>
<section>
<title>What are the core benefits of this change?</title>
<para>
Changing the product to a project will:
</para>
<itemizedlist>
<listitem>
<para>
Ensure that users can get the latest bits as quickly as
possible.
</para>
</listitem>
<listitem>
<para>
Create new opportunities for developers and users to
participate in The Fedora Project development by opening up
the full development process for anyone to see and join if
they'd like.
</para>
</listitem>
<listitem>
<para>
Allow us to use The Fedora Project to develop and mature the
latest, greatest technologies.
</para>
</listitem>
<listitem>
<para>
Speed up the development process, taking better advantage of
the inherent strengths of the open source model.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Will Red Hat provide formal technical support for The Fedora Project?</title>
<para>
No, no formal Web or phone support for The Fedora Project will
be available from Red Hat. Red Hat's supported product line will
be based in part on Fedora Core, and our development will be
done externally as part of The Fedora Project as much as
possible. Each new release of our supported products will be
based in part on a recent release of Fedora Core.
</para>
</section>
<section>
<title>Will Red Hat's supported products contain all the packages found in
Fedora Core?</title>
<para>
In order to focus our efforts and limit support costs, we will
probably select a subset of packages found in Fedora Core to
include in the supported product line. One of the goals of The
Fedora Project is to encourage a pool of high-quality add-on
packages; if we're successful, there will be so many we won't be
able to support all of them.
</para>
<para>
== Will Fedora Core be sold in retail? ===
</para>
<para>
Fedora Core will not be sold through the retail channel as a
shrinkwrapped box. There is no list price for Fedora Core. The
rapid development pace we expect for Fedora Core doesn't suit
retail distribution ��� it is a lot of work to get a box product
in and out of the channel, and retail isn't set up to
efficiently handle software that is updated as often as every
six months. Also, the creation of packaging and other materials
that are necessary for retail significantly slows down the time
to market, which means that users can't get the freshest bits
when they are still truly fresh. Further information on Red
Hat's retail product line is available at the Red Hat website.
</para>
</section>
<section>
<title>How will The Fedora Project be made available to the public?</title>
<para>
Fedora Core releases will be available as ISO images for both
CDs and DVDs, and will also be available through other channels
such as third-party online sales of physical media; distribution
at Linux User Groups, included in magazines and in books, and
maybe even handed out at trade shows. The bits may be actively
pushed into content sharing networks such as
<ulink url='http://docbook.wikiwikiweb.de/BitTorrent'>BitTorrent</ulink>.
(Not all mechanisms will be used for each release, except that
ISOs will be freely available for each release.)
</para>
</section>
<section>
<title>What is the difference between "Fedora", "The Fedora Project", and
"Fedora Core"?</title>
<para>
The <emphasis>Fedora Project</emphasis> is a collection of
sub-projects. <emphasis>Fedora Core</emphasis> is the central
project, which aims to provide a platform with the best in free
and open source software. <emphasis>Fedora</emphasis> generally
refers to the <emphasis>Fedora Project</emphasis> as a whole,
and is sometimes used to refer to <emphasis>Fedora
Core</emphasis> or a system running a collection of software
from the Fedora Project.
</para>
</section>
<section>
<title>Whom can I contact in the individual Fedora sub-projects?</title>
<para>
Try the project's mailing list first, which gives the project
leads and other community members the chance to help you. You
can find information for the various projects on the
<ulink url='http://docbook.wikiwikiweb.de/Communicate'>Communicate</ulink>
page.
</para>
<para>
Contact information for project leads is available at:
</para>
<itemizedlist>
<listitem override='none'>
<para>
<ulink url='http://fedora.redhat.com/About/contact.html'>http://fedora.redhat.com/About/contact.html</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>How is the Fedora Project organized and governed?</title>
<para>
The Fedora Project is a collection of many smaller
<ulink url='http://docbook.wikiwikiweb.de/Projects'>projects</ulink>,
working together to produce the platform and build the
supporting community. These different sub-projects are
independent of one another, but work together to achieve common
goals and coordinate efforts.
</para>
<para>
Each of the sub-projects has leads or a Steering Committee to
organize and guide that project's development. The Fedora
Project operates as a
<ulink url='http://en.wikipedia.org/wiki/Meritocracy'>meritocracy</ulink>,
where responsibility and power are granted based upon ability
and effort. The people who lead Fedora are selected because they
have proven they are willing and able to do so.
</para>
</section>
<section>
<title>What kind of project management method does each Fedora sub-project use?</title>
<para>
Each project has either leads or a Steering Committee to guide
it. Individual contributors are given a great deal of freedom to
work on whatever they choose, but they are asked to follow the
guidance from the project's committee for processes and approval
for new initiatives.
</para>
<para>
Like other responsibilities in the Fedora Project, committee
membership is based largely upon merit, but all voices are
welcome, and new ideas and opinions will be given due attention.
Innovating and leading new ideas is a great way to earn
recognition within the community.
</para>
<para>
Contributors can join committee members in regular IRC meetings.
The meetings are open, and minutes are made publicly available
and usually posted to the appropriate mailing list. Raw IRC logs
are also sometimes available.
</para>
<para>
Most sub-projects keep a schedule of tasks on this wiki. Check
the
<ulink url='http://docbook.wikiwikiweb.de/Projects'>Projects</ulink>
page for links to individual sub-project pages. From those
individual pages, you can find all of the available information
for that project.
</para>
</section>
<section>
<title>Does the Fedora Project assign tasks to contributors, or do the
contributors decide what to do?</title>
<para>
Interested volunteers are encouraged to take up the tasks they
would like to contribute towards. You can avoid redundant tasks
by posting to the relevant project list and coordinating with
other interested community members. If you're not sure where you
want to contribute, see the
<ulink url='http://docbook.wikiwikiweb.de/HelpWanted'>HelpWanted</ulink>
page for different areas that can use your help. The
<ulink url='http://docbook.wikiwikiweb.de/Mentors'>Fedora
Mentors</ulink> project can guide you if you need further help.
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Is there a partnership program between schools or non-profits and
Fedora?</title>
<para>
Not at present. If you have any ideas or suggestions to create
such a program, please bring it to the attention of
<ulink url='http://docbook.wikiwikiweb.de/Marketing'>Fedora
Marketing</ulink>. Interested schools and non-profits are
welcome to join us for discussions.
</para>
</section>
<section>
<title>Is there a partnership program between LUGs and Fedora?</title>
<para>
We attempt to work with Linux User Groups in whatever ways we
can. Our list of LUG contacts is on our
<ulink url='http://docbook.wikiwikiweb.de/LinuxUserGroups'>LinuxUserGroups</ulink>
page. If you would like to represent your LUG, please add your
LUG to that list. We also encourage our Ambassadors to engage
their local LUGs.
</para>
</section>
<section>
<title>Can schools and non-profits reference the "Fedora Project" name and
other Fedora marks if they are interacting with the Fedora
community?</title>
<para>
Yes, as long as they make it clear whether or not they are
representing the Project. If they would like to represent the
Project, they can approach and coordinate with the
<ulink url='http://docbook.wikiwikiweb.de/Marketing'>Fedora
Marketing</ulink> team. This and other uses of Fedora marks are
subject to the terms of the
<ulink url='http://docbook.wikiwikiweb.de/Legal/TrademarkGuidelines'>Trademark
Guidelines</ulink>.
</para>
</section>
<section>
<title>Is there a certification program for third-party applications running on
Fedora?</title>
<para>
No. The Fedora Project is dedicated to providing the best in
free and open source software. Fedora Core is the pinnacle of
innovative, open solutions, and is developed with a rapid
release cycle. Fedora Extras allows a vast array of additional
free and open source solutions to be contributed by the
community and maintained for Fedora Core. Beyond these projects,
the Fedora Project does not certify any third-party
applications.
</para>
<para>
Formal ISV certification is available for Red Hat Enterprise
Linux, which shares many of Fedora Core's features, but is
provided on a longer release cycle and is commercially supported
for 7 years.
</para>
</section>
<section>
<title>Is there a certification program for hardware that works with Fedora?</title>
<para>
Fedora Core runs on a large variety of hardware, and the list of
working hardware is constantly growing larger. Because Fedora
improvements occur very rapidly and consistently, including
hardware support, a
<ulink url='http://docbook.wikiwikiweb.de/HCL'>Hardware
Compatibility List</ulink> was deemed too time-consuming and not
worthwhile. Alternative methods of tracking working hardware
have been suggested, but the consensus is that manually
maintaining a complete list is unfeasible.
</para>
<para>
We are trying a new approach to collect hardware information
directly from the users, through the
<screen><![CDATA[pootypedia]]></screen>
project which was built as part of the
<ulink url='http://docbook.wikiwikiweb.de/FedoraBounties'>Fedora
Bounties</ulink> program. More information about this is
available from our infrastracture project schedule:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/Infrastructure/Schedule'>http://fedoraproject.org/wiki/Infrastructure/Schedule</ulink>
</para>
</listitem>
</itemizedlist>
<para>
We are always trying to find ways to improve Fedora's hardware
support, and welcome constructive feedback.
</para>
<para>
A compatibility list is maintained for Red Hat Enterprise Linux
at
<ulink url='http://bugzilla.redhat.com/hcl'>http://bugzilla.redhat.com/hcl</ulink>.
It will closely parallel Fedora's compatibility.
</para>
</section>
<section>
<title>Is the Fedora Project independent of Red Hat, Inc.?</title>
<para>
The Fedora Project is a community project, separate from Red
Hat, but Red Hat sponsors the Fedora Project and provides a
great deal of valuable management and resources to the Fedora
Project. Red Hat uses the material that the Fedora Project
produces to develop its enterprise platform offerings. Red Hat
has a strong interest in Fedora, and the success of the Fedora
Project has been thanks to the great contributions of Red Hat.
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://redhat.com/fedora'>http://redhat.com/fedora</ulink>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Why should I pay for Red Hat Enterprise Linux when Fedora Core is free?
What is the relationship between Fedora Core and Red Hat
Enterprise Linux?</title>
<para>
Both Fedora Core and Red Hat Enterprise Linux (RHEL) are open
source. Fedora Core is a community project and serves as the
base platform on which RHEL is built. The cost of RHEL comes
from the subscription, which provides assorted certifications
and support for additional architectures, as well as 7 years of
enterprise support. Red Hat also enhances its RHEL offerings
with additional software and with certification programs.
Misinformation and confusion notwithstanding, the base RHEL
distribution <emphasis>is</emphasis> open source, and the
complete source code can always be downloaded from
<ulink url='ftp://ftp.redhat.com/'>Red Hat's FTP
servers</ulink>.
</para>
<para>
Red Hat provides a comparison between the two options on their
website:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='https://www.redhat.com/software/rhelorfedora/'>https://www.redhat.com/software/rhelorfedora/</ulink>
</para>
</listitem>
</itemizedlist>
<para>
More information on the release history and lineage is available
from the following link:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/History'>http://fedoraproject.org/wiki/History</ulink>
</para>
</listitem>
</itemizedlist>
<para>
When you purchase RHEL, you are also helping to support Fedora.
Since Red Hat sponsors Fedora, what is good for Red Hat is
usually good for Fedora.
</para>
</section>
</section>
<section>
<title>For Fedora Contributors</title>
<section>
<title>Why should I help?</title>
<para>
<emphasis role='strong'>Your name in lights, an online CV, and
maybe a trip to a FUDCon.</emphasis>
</para>
<para>
First, contribute to Fedora and you may get your name in the
distribution. Hey, fair is fair.
</para>
<para>
Second, if you're a Fedora contributor, you don't need a fancy
resume; you can just tell potential employers to 'Google' your
name.
</para>
<para>
Third, top Fedora contributors can receive travel stipends to
attend the Fedora Users and Developers Conference nearest them.
You will have the opportunity to meet some of the giants of the
open source movement in person, as their peers and equals.
</para>
<para>
And last, you'd be playing with this stuff anyway. Spend your
time doing stuff that you will enjoy and that others will use.
What more incentive do you need? Join us.
</para>
</section>
<section>
<title>I'm interested in contributing to Fedora, where can I get started?</title>
<para>
Refer to our
<ulink url='http://docbook.wikiwikiweb.de/HelpWanted'>HelpWanted</ulink>
page to learn where help is needed and how to get going. You
might also be interested in our
<ulink url='http://docbook.wikiwikiweb.de/Mentors'>Mentors</ulink>
program.
</para>
</section>
<section>
<title>What are some interesting new project ideas that are important to
Fedora?</title>
<para>
See the
<ulink url='http://docbook.wikiwikiweb.de/FedoraBounties'>FedoraBounties</ulink>
page for project ideas important to Fedora.
</para>
</section>
<section>
<title>How can I package software for Fedora users? Where can I find
information for contributing to Fedora Extras?</title>
<para>
The
<ulink url='http://docbook.wikiwikiweb.de/Extras'>Extras</ulink>
page will point you to all kinds of help.
</para>
</section>
<section>
<title>Where can I find information for contributing to the Fedora
Documentation Project?</title>
<para>
Some good links for help can be found on the
<ulink url='http://docbook.wikiwikiweb.de/DocsProject'>DocsProject</ulink>
page.
</para>
</section>
</section>
<section>
<title>Where else can I find answers?</title>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedora.redhat.com/docs/release-notes/'>Release
Notes</ulink> - You should always read the release notes for
the versions of Fedora you use.
</para>
</listitem>
<listitem>
<para>
<ulink url='http://bugzilla.redhat.com/'>Red Hat's
Bugzilla</ulink> - Search for information about your problem
here
</para>
</listitem>
<listitem>
<para>
<ulink url='http://docbook.wikiwikiweb.de/Docs'>Fedora
Documentation</ulink> - Several helpful documents are
published here.
</para>
</listitem>
<listitem>
<para>
<ulink url='http://redhat.com/magazine'>Red Hat
Magazine</ulink> - Red Hat online magazine is a free resource
that provides various informative articles on Fedora.
</para>
</listitem>
<listitem>
<para>
See
<ulink url='http://docbook.wikiwikiweb.de/CommunityWebsites'>Fedora
Community Websites</ulink> for more Fedora Resources.
</para>
</listitem>
</itemizedlist>
<!--rule (<hr>) is not supported-->
<para>
<ulink url='http://docbook.wikiwikiweb.de/CategoryDocumentation'>CategoryDocumentation</ulink>
</para>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE Feedback.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Feedback">
<title>Feedback</title>
<!--RAW HTML: <h2>Feedback</h2>-->
<para>
Thank you for taking the time to provide your comments, suggestions,
and bug reports to the Fedora community. By doing so, you help
improve the state of Fedora, Linux, and free software worldwide.
</para>
<section>
<title>Providing Feedback on Fedora Software</title>
<para>
To provide feedback on Fedora software or other system elements,
please refer to
<ulink url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'/>.
A list of commonly reported bugs and known issues for this release
is available from
<ulink url='http://fedoraproject.org/wiki/Bugs/FC6Common'/>.
</para>
</section>
<section>
<title>Providing Feedback on Release Notes</title>
<para>
<important>
<title>Feedback for Release Notes Only</title>
<para>
This section concerns feedback on the release notes
themselves.
</para>
</important>
</para>
<para>
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:
</para>
<itemizedlist>
<listitem>
<para>
If you have a Fedora account, edit content directly at
<ulink url='http://fedoraproject.org/wiki/Docs/Beats'/>
</para>
</listitem>
<listitem>
<para>
Fill out a bug request using this template:
<ulink url='http://tinyurl.com/nej3u'/> -
<emphasis role='strong'>This link is ONLY for feedback on the
release notes themselves</emphasis>
</para>
</listitem>
<listitem>
<para>
Email
<ulink url='mailto:relnotes@fedoraproject.org'>relnotes(a)fedoraproject.org</ulink>
</para>
</listitem>
</itemizedlist>
</section>
</section>
--- NEW FILE FileSystems.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-FileSystems">
<title>File Systems</title>
<!--RAW HTML: <h2>File Systems</h2>-->
<para>
Fedora Core 6 provides basic support for encrypted swap partitions
and non-root file systems. To use it, add entries to
<filename>/etc/crypttab</filename> and reference the created devices in
<filename>/etc/fstab</filename>.
</para>
<para>
<note>
<title>Encrypted FS Support Unavailable During Install</title>
<para>
Enable file system encryption after installation. Anaconda does
not have support for creating encrypted block devices.
</para>
</note>
</para>
<para>
The following example shows an <filename>/etc/crypttab</filename> entry for a
swap partition:
</para>
<screen><![CDATA[my_swap /dev/hdb1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
]]></screen>
<para>
This creates an encrypted block device <filename
class="devicefile">/dev/mapper/my_swap</filename>, which can be
referenced in <filename>/etc/fstab</filename>. The next example
shows an entry for a filesystem volume:
</para>
<screen><![CDATA[my_volume /dev/hda5 /etc/volume_key cipher=aes-cbc-essiv:sha256
]]></screen>
<para>
The <filename>/etc/volume_key</filename> file contains a plaintext
encryption key. You can also specify <option>none</option> as the
key file name, and the system instead asks for the encryption key
during boot.
</para>
<para>
The recommended method is to use
<application>LUKS</application> for file system volumes:
</para>
<itemizedlist>
<listitem>
<para>
Create the encrypted volume using <command>cryptsetup
luksFormat</command>
</para>
</listitem>
<listitem>
<para>
Add the necessary entry to <filename>/etc/crypttab</filename>
</para>
</listitem>
<listitem>
<para>
Set up the volume manually using <command>cryptsetup
luksOpen</command> or reboot
</para>
</listitem>
<listitem>
<para>
Create a filesystem on the encrypted volume
</para>
</listitem>
<listitem>
<para>
Set up an <filename>/etc/fstab</filename> entry
</para>
</listitem>
</itemizedlist>
</section>
--- NEW FILE I18n.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-I18n">
<title>Internationalization (i18n)</title>
<!--RAW HTML: <h2>Internationalization (i18n)</h2>-->
<para>
This section includes information on language support under Fedora
Core.
</para>
<section>
<title>Input Methods</title>
<para>
The default SCIM (Simple Common Input Method) GTK Input Method
Module is now <code>scim-bridge</code>, written from scratch in C
by Ryo Dairiki. SCIM is no longer linked against <systemitem
class="library">libstdc++so7</systemitem>, and
<systemitem>scim-qtimm</systemitem> works again.
</para>
<para>
If SCIM is installed, it now runs by default for users of all
locales rather than only some Asian locales as in the previous
release. The following table lists the default trigger hotkeys for
different languages:
</para>
<informaltable>
<tgroup cols='2'>
<colspec colname='col_0'/>
<colspec colname='col_1'/>
<tbody>
<row>
<entry colsep='1' rowsep='1'><para><emphasis role='strong'>Language</emphasis></para></entry>
<entry colsep='1' rowsep='1'><para><emphasis role='strong'>Trigger hotkeys</emphasis></para></entry>
</row>
<row>
<entry colsep='1' rowsep='1'><para>all</para></entry>
<entry colsep='1' rowsep='1'><para><code>Ctrl-Space</code></para></entry>
</row>
<row>
<entry colsep='1' rowsep='1'><para>Japanese</para></entry>
<entry colsep='1' rowsep='1'><para><keycap>Zenkaku_Hankaku</keycap> or
<keycombo>
<keycap>Alt</keycap>
<keycap>`</keycap>
</keycombo></para></entry>
</row>
<row>
<entry colsep='1' rowsep='1'><para>Korean</para></entry>
<entry colsep='1' rowsep='1'><para><keycombo>
<keycap>Shift</keycap>
<keycap>Space</keycap>
</keycombo></para></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<section>
<title>Language Installation</title>
<para>
To install additional language support from the
<systemitem class="groupname">Languages</systemitem> group, use
<command>pirut</command> or <keycombo>
<keycap>Applications</keycap><keycap>Add/Remove
Software</keycap></keycombo>, or run this command:
</para>
<screen><![CDATA[su -c 'yum groupinstall <language>-support'
]]></screen>
<para>
In the command above, <replaceable><language></replaceable> is one of
<literal>assamese</literal>, <literal>bengali</literal>,
<literal>chinese</literal>, <literal>gujarati</literal>, <literal>hindi</literal>,
<literal>japanese</literal>, <literal>kannada</literal>,
<literal>korean</literal>, <literal>malayalam</literal>,
<literal>marathi</literal>, <literal>oriya</literal>, <literal>punjabi</literal>,
<literal>sinhala</literal>, <literal>tamil</literal>, <literal>thai</literal>, or
<literal>telegu</literal>.
</para>
</section>
</section>
<section>
<title>im-chooser</title>
<para>
A new user configuration tool called <command>im-chooser</command>
has been added that allows you to disable or enable the usage of
input methods on your desktop. If SCIM is installed but you do not
wish to run it on your desktop, you can disable it using
<command>im-chooser</command>.
</para>
</section>
<section>
<title>xinputrc</title>
<para>
At X startup, <command>xinput.sh</command> now sources
<filename>~/.xinputrc</filename> or
<filename>/etc/X11/xinit/xinputrc</filename> instead of searching
config files under <filename>~/.xinput.d/</filename> or
<filename>/etc/xinit/xinput.d/</filename>.
</para>
</section>
</section>
--- NEW FILE Installer.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Installer">
<title>Installation Notes</title>
<para>
<application>Anaconda</application> is the name of the
Fedora Installer. This section outlines those issues that are
related to <application>Anaconda</application> (the Fedora
Core installation program) and installing Fedora Core 6.
</para>
<para>
<note>
<title>Downloading Large Files</title>
<para>
If you intend to download the Fedora Core 6 DVD ISO image, keep
in mind that not all file downloading tools can accommodate
files larger than 2 GiB in size. <command>wget</command>
1.9.1-16 and above, <command>curl</command> and
<command>ncftpget</command> do not have this limitation, and can
successfully download files larger than 2 GiB.
<application>BitTorrent</application> is another method for
downloading large files. For information about obtaining and
using the torrent file, refer to <ulink
url="http://torrent.fedoraproject.org/"/>.
</para>
</note>
</para>
<para>
<application>Anaconda</application> 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 <userinput>linux
mediacheck</userinput> at the
<computeroutput>boot:</computeroutput> prompt presented at the start
of installation.
</para>
<para>
The <option>mediacheck</option> 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
<option>mediacheck</option>, boot with the following option:
</para>
<screen><![CDATA[linux ide=nodma
]]></screen>
<para>
After you complete the <option>mediacheck</option> function
successfully, reboot to return DMA mode to its normal state. On many
systems this results in a faster installation process from disc. You
may skip the <option>mediacheck</option> option when rebooting.
</para>
<para>
Use the <command>sha1sum</command> 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.
</para>
<para>
<important>
<title><application>BitTorrent</application> Automatically
Verifies File Integrity</title>
<para>
If you use <application>BitTorrent</application>, any files you
download are automatically validated. If your file completes
downloading, you do not need to check it. Once you burn your CD,
however, you should still use <option>mediacheck</option>.
</para>
</important>
</para>
<para>
You may perform memory testing before you install Fedora Core by
entering <userinput>memtest86</userinput> at the
<computeroutput>boot:</computeroutput> prompt. This option runs the
<application>Memtest86</application> standalone memory testing
software in place of <application>Anaconda</application>.
<application>Memtest86</application> memory testing continues until
the <keycap function="escape">Esc</keycap> key is pressed.
</para>
<para>
<note>
<title><application>Memtest86</application> Availability</title>
<para>
You must boot from Installation Disc 1 or a rescue CD in order
to use this feature.
</para>
</note>
</para>
<para>
Fedora Core 6 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
fall back to using the text-based installer automatically. If you
prefer to use the text-based installer, type <userinput>linux
text</userinput> at the <computeroutput>boot:</computeroutput>
prompt.
</para>
<section>
<title>Changes in Anaconda</title>
<itemizedlist>
<listitem>
<para>
<application>Anaconda</application> now features the ability
to install packages from Fedora Extras or any custom
<command>yum</command>-compatible software repository. Fedora
Extras is available by default on interactive installs with
network connectivity.
</para>
</listitem>
</itemizedlist>
<para>
<note>
<title>Yum Repository Support</title>
<para>
Only HTTP and FTP repositories are supported; repositories on
CDs or NFS are not currently supported.
</para>
</note>
</para>
<itemizedlist>
<listitem>
<para>
You can now use the installer to generate a Live CD for
Kadischi. Refer to
<ulink url='http://fedoraproject.org/wiki/Kadischi/'/> for
more details.
</para>
</listitem>
<listitem>
<para>
<application>Anaconda</application> uses SquashFS to compress
and store packages on images.
</para>
</listitem>
<listitem>
<para>
<application>Anaconda</application> now supports installation
using IPv6.
</para>
</listitem>
<listitem>
<para>
<application>Anaconda</application> now supports installation
from <ulink
url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/FireWire'>FireWire</ulink>
and USB storage devices.
</para>
</listitem>
<listitem>
<para>
<application>Anaconda's</application> backend,
<command>yum</command>, has been updated to 2.9.x.
</para>
</listitem>
<listitem>
<para>
The installer provides enhanced support for the ppc64
architecture.
</para>
</listitem>
<listitem>
<para>
The installer now supports Apple Macintosh systems with Intel
processors.
</para>
</listitem>
<listitem>
<para>
The installer now supports multipathing.
</para>
</listitem>
<listitem>
<para>
Vera fonts are retired and replaced by
<ulink url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/DejaVu'>DejaVu</ulink>
as default for the installer.
</para>
</listitem>
<listitem>
<para>
The installer is now translated in Greek, Kannada, Malayalam,
Marathi and Oriya.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Kickstart Changes</title>
<para>
Three new <systemitem>kickstart</systemitem> keywords have been
added.
</para>
<variablelist>
<varlistentry>
<term><code><![CDATA[repo --name=<repoid> [--baseurl=<url>|--mirrorlist=<url>]]></code></term>
<listitem>
<para>
<option>repo</option> specifies additional package
repositories to use for installation.
<option>baseurl</option> specifies the URL for the
repository, while <option>mirrorlist</option> specifies a
list of mirrors. One and only one of these options may be
specified per repository definition.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><code><![CDATA[services [--disabled=<list>] [--enabled=<list>] ]]></code></term>
<listitem>
<para>
<option>services</option> modifies the default set of
services that are started in the default runlevel.
<option>enabled</option> and <option>disabled</option> take
comma-separated lists, with <option>enabled</option>
services taking priority.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><code><![CDATA[user --name=<username> [--groups=<list>]
[--homedir=<homedir>] [--password=<password>] [--iscrypted]
[--shell=<shell>] [--uid=<uid>] ]]></code></term>
<listitem>
<para>
<option>user</option> creates a new user with the specified
parameters. <option>name</option> is required; all other
parameters are optional.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
More documentation on <systemitem>kickstart</systemitem> is
available in the <package>anaconda</package> package. To install
it, run the command <command>su -c 'yum install
anaconda'</command> and read the
<filename>/usr/share/doc/anaconda*/kickstart-docs.txt</filename>
file for more information.
</para>
</section>
<section>
<title>Installation Related Issues</title>
<section>
<title>Sony VAIO Notebooks</title>
<para>
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:
</para>
<screen><![CDATA[pci=off ide1=0x180,0x386
]]></screen>
<para>
Installation should proceed normally, and any devices not
detected are configured the first time Fedora Core is booted.
</para>
</section>
<section>
<title>IDE RAID</title>
<para>
Not all IDE RAID controllers are supported. If your RAID
controller is not yet supported by <option>dmraid</option>, you
may combine drives into RAID arrays by configuring Linux
software RAID. For supported controllers, configure the RAID
functions in the computer BIOS.
</para>
</section>
<section>
<title>Multiple NICs and PXE Installation</title>
<para>
Some servers with multiple network interfaces may not assign
<systemitem>eth0</systemitem> to the first network interface as
BIOS knows it, which can cause the installer to try using a
different network interface than was used by PXE. To change this
behavior, use the following in
<filename>pxelinux.cfg/*</filename> config files:
</para>
<screen><![CDATA[IPAPPEND 2
APPEND ksdevice=bootif
]]></screen>
<para>
The configuration options above cause the installer to use the
same network interface as BIOS and PXE use. You can also use the
following option:
</para>
<screen><![CDATA[ksdevice=link
]]></screen>
<para>
This option causes the installer to use the first network device
it finds that is linked to a network switch.
</para>
</section>
</section>
<section>
<title>Upgrade Related Issues</title>
<para>
Refer to
<ulink url='http://fedoraproject.org/wiki/DistributionUpgrades'/>
for detailed recommended procedures for upgrading Fedora.
</para>
<para>
In general, fresh installations are recommended over upgrades,
particularly for systems that include software from third-party
repositories. Third-party packages remaining from a previous
installation may not work as expected on an upgraded Fedora
system. If you decide to perform an upgrade anyway, the following
information may be helpful:
</para>
<itemizedlist>
<listitem>
<para>
Before you upgrade, back up the system completely. In
particular, preserve <filename
class="directory">/etc</filename>, <filename
class="directory">/home</filename>, and possibly <filename
class="directory">/opt</filename> and <filename
class="directory">/usr/local</filename> 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, create alternate
boot media such as a GRUB boot floppy.
</para>
</listitem>
</itemizedlist>
<para>
<important>
<title>System Configuration Backups</title>
<para>
Backups of configurations in <filename
class="directory">/etc</filename> are also useful in
reconstructing system settings after a fresh installation.
</para>
</important>
</para>
<itemizedlist>
<listitem>
<para>
After you complete the upgrade, run the following command:
</para>
</listitem>
</itemizedlist>
<screen><![CDATA[rpm -qa --last > RPMS_by_Install_Time.txt
]]></screen>
<itemizedlist>
<listitem override='none'>
<para>
Inspect the end of the output for packages that pre-date the
upgrade. Remove or upgrade those packages from third-party
repositories, or otherwise deal with them as necessary.
</para>
</listitem>
</itemizedlist>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE Java.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Java">
<title>Java and java-gcj-compat</title>
<!--RAW HTML: <h2>Java and java-gcj-compat</h2>-->
<para>
This release of Fedora Core includes a free and open source Java
environment called <systemitem>java-gcj-compat</systemitem>. The
<systemitem>java-gcj-compat</systemitem> collection includes a tool
suite and execution environment that is capable of building and
running many useful programs that are written in the Java
programming language.
</para>
<para>
<note>
<title>Fedora Core Does Not Include Java</title>
<para>
Java is a trademark of Sun Microsystems.
<systemitem>java-gcj-compat</systemitem> is an entirely free
software stack that is <emphasis>not</emphasis> Java, but may
run Java software.
</para>
</note>
</para>
<para>
The <!--GetVal-macro not supported by the docbook formatter, but
giving it a shot anyway--> <systemitem>java-gcj-compat</systemitem>
infrastructure has three key components: a <application>GNU
Java</application> runtime (<systemitem
class="library">libgcj</systemitem>), the <application>Eclipse
Java</application> compiler (<systemitem>ecj</systemitem>), and a
set of wrappers and links (<systemitem>java-gcj-compat</systemitem>)
that present the runtime and compiler to the user in a manner
similar to other Java environments.
</para>
<para>
The Java software packages in this Fedora release use the
<systemitem>java-gcj-compat</systemitem> environment. These packages
include <application>OpenOffice.org Base</application>,
<application>Eclipse</application>, and <application>Apache
Tomcat</application>. Refer to the Java FAQ at <ulink
url='http://www.fedoraproject.org/wiki/JavaFAQ'/> for more
information on the <systemitem>java-gcj-compat</systemitem> free
Java environment in Fedora.
</para>
<para>
<important>
<title>Include Location and Version Information in Bug Reports</title>
<para>
When making a bug report, be sure to include the output from
these commands:
</para>
</important>
</para>
<screen><![CDATA[which java && java -version && which javac && javac -version
]]></screen>
<section>
<title>Handling Java and Java-like Packages</title>
<para>
In addition to the <systemitem>java-gcj-compat</systemitem> free
software stack, Fedora Core lets you install multiple Java
implementations and switch between them using the
<command>alternatives</command> command line tool. However, every
Java system you install must be packaged using the JPackage
Project packaging guidelines to take advantage of
<command>alternatives</command>. Once these packages are installed
properly, the <systemitem class="username">root</systemitem> user
may switch between <systemitem>java</systemitem> and
<systemitem>javac</systemitem> implementations using the
<command>alternatives</command> command:
</para>
<screen><![CDATA[alternatives --config java
alternatives --config javac
]]></screen>
</section>
<section>
<title>64-bit JNI Libraries</title>
<para>
The 64-bit JNI libraries shipped by default on x86_64 systems in
Fedora Core and Extras do not run on 32-bit JREs. Either switch
to a 64-bit Java alternative, or install the 32-bit version of the
packages, if available. To install a 32-bit version, use the
following command:
</para>
<screen><![CDATA[yum install <package_name>.i386
]]></screen>
<para>
Likewise, the 32-bit JNI libraries shipped by default on ppc64
systems do not run with a 64-bit JRE. To install the 64-bit
version, use the following command:
</para>
<screen><![CDATA[yum install <package_name>.ppc64
]]></screen>
</section>
<section>
<title>Handling Java Applets</title>
<para>
This release of Fedora Core includes a preview release of
<systemitem>gcjwebplugin</systemitem>, a
<application>Firefox</application> plugin for Java applets.
<systemitem>gcjwebplugin</systemitem> is not enabled by default.
Although the security implementation in <application>GNU
Classpath</application> is being actively developed, it is not
mature enough to run untrusted applets safely. That said, the AWT
and Swing implementations in <application>GNU
Classpath</application> are now sufficiently mature that they
can run many applets deployed on the web. Adventurous users who
want to try <systemitem>gcjwebplugin</systemitem> can read
<filename>/usr/share/doc/libgcj-4.1.1/README.libgcjwebplugin.so</filename>,
as installed by the <package>gcc</package> rpm. The README
explains how to enable the plugin and the risks associated with
doing so.
</para>
</section>
<section>
<title>Fedora and the JPackage Java Packages</title>
<para>
Fedora Core includes many packages derived from the JPackage
Project, which provides a Java software repository. These packages
are modified in Fedora to remove proprietary software dependencies
and to make use of GCJ's ahead-of-time compilation feature. Use
the Fedora repositories to update these packages, or use the
JPackage repository for packages not provided by Fedora. Refer to
the JPackage website at <ulink url='http://jpackage.org'/> for
more information on the project and the software it provides.
</para>
<para>
<warning>
<title>Mixing Packages from Fedora and JPackage</title>
<para>
Research package compatibility before you install software
from both the Fedora and JPackage repositories on the same
system. Incompatible packages may cause complex issues.
</para>
</warning>
</para>
</section>
<section>
<title>Eclipse</title>
<para>
This release of Fedora Core includes Fedora Eclipse, which is based
on the <ulink url='http://www.eclipse.org'>Eclipse</ulink> SDK
version 3.2. The "New and Noteworthy" page for this release can be
accessed
<ulink url='http://download.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/new_…'>here</ulink>.
</para>
<para>
Released in June 2006, the SDK is known variously as "the Eclipse
Platform," "the Eclipse IDE," and "Eclipse." The Eclipse SDK is
the foundation for the combined release of ten Eclipse projects
under the
<ulink url='http://www.eclipse.org/callisto'>Callisto</ulink>
combined release umbrella. A few of these Callisto projects are
included in Fedora Core and Extras:
<ulink url='http://www.eclipse.org/cdt'>CDT</ulink>, for C/C++
development, and
<ulink url='http://www.eclipse.org/gef'>GEF</ulink>, the Graphical
Editing Framework.
</para>
<para>
We hope to augment these projects with others as this Fedora cycle
goes on. Likely candidates for inclusion include
<ulink url='http://www.eclipse.org/emf'>EMF</ulink>, the Eclipse
Modeling Framework, and
<ulink url='http://www.eclipse.org/vep'>VE</ulink>, the Visual
Editor. As of this writing, it is expected that an updated version
of <ulink url='http://pydev.sf.net'>PyDev</ulink>, the Python
development tools, is going to be available in Fedora Extras.
Assistance in getting these projects packaged and tested with GCJ
is always welcome. Contact the interested parties through
<ulink url='http://www.redhat.com/mailman/listinfo/fedora-devel-java-list/'>fedora-devel-java-list</ulink>
and/or #fedora-java on freenode.
</para>
<para>
Fedora also includes plugins and features that are particularly
useful to FOSS hackers: <ulink
url='http://fedora-test.fedoraproject.org/fedora-docs/fedora-docs/ChangeLog'>ChangeLog</ulink>
editing with <systemitem>eclipse-changelog</systemitem> and
Bugzilla interaction with
<systemitem>eclipse-bugzilla</systemitem>. Our CDT package also
includes work-in-progress support for the GNU Autotools. The
latest information regarding these projects can be found at the
<ulink url='http://sourceware.org/eclipse/'>Fedora Eclipse
Project</ulink> page.
</para>
<section>
<title>Non-packaged Plugins/Feature</title>
<para>
Fedora Eclipse contains a patch to allow non-root users to make
use of the Update Manager functionality for installing
non-packaged plugins and features. Such plugins are installed in
the user's home directory under the <filename
class="directory">.eclipse</filename> directory. Please note,
however, that these plugins do not have associated GCJ-compiled
bits and may therefore run slower than expected.
</para>
</section>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE Kernel.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Kernel">
<title>Linux Kernel</title>
<para>
This section covers changes and important information regarding the
2.6.18 based kernel in Fedora Core 6. The 2.6.18 kernel includes:
</para>
<itemizedlist>
<listitem>
<para>
Lightweight user space priority inheritance support
(<ulink url='http://lwn.net/Articles/178253/'/>)
</para>
</listitem>
<listitem>
<para>
A "lock validator" debugging tool
(<ulink url='http://lwn.net/Articles/185666/'/>)
</para>
</listitem>
<listitem>
<para>
A new power saving policy for multicore systems, SMPnice
(<ulink url='http://lwn.net/Articles/186438/'/>)
</para>
</listitem>
<listitem>
<para>
A much improved SATA layer
(<ulink url='http://lwn.net/Articles/183734/'/>)
</para>
</listitem>
<listitem>
<para>
Swapless page migration
(<ulink url='http://lwn.net/Articles/160201/'/>)
</para>
</listitem>
<listitem>
<para>
Per-zone VM counters
</para>
</listitem>
<listitem>
<para>
Per-task delay accounting
</para>
</listitem>
<listitem>
<para>
A new per-packet access control for SELinux called
<option>secmark</option> (<ulink
url='http://james-morris.livejournal.com/11010.html'/>)
</para>
</listitem>
<listitem>
<para>
Randomized i386 vDSO
</para>
</listitem>
<listitem>
<para>
New drivers and additional device support for many existing
drivers
</para>
</listitem>
<listitem>
<para>
Many bug fixes and other small improvements
</para>
</listitem>
</itemizedlist>
<section>
<title>Version</title>
<para>
Fedora Core may include additional patches to the kernel 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 <emphasis>vanilla kernel</emphasis> from the kernel.org
web site:
</para>
<para>
<ulink url='http://www.kernel.org/'/>
</para>
<para>
To obtain a list of these patches, download the source RPM package
and run the following command against it:
</para>
<screen>rpm -qpl kernel-<replaceable><version></replaceable>.src.rpm</screen>
</section>
<section>
<title>Changelog</title>
<para>
To retrieve a log of changes to the package, run the following
command:
</para>
<screen>rpm -q --changelog kernel-<replaceable><version></replaceable></screen>
<para>
If you need a user friendly version of the changelog, refer to
<ulink url='http://wiki.kernelnewbies.org/LinuxChanges'/>. A short
and full diff of the kernel is available from
<ulink url='http://kernel.org/git'/>. The Fedora version kernel is
based on the Linus tree.
</para>
<para>
Customizations made for the Fedora version are available from
<ulink url='http://cvs.fedora.redhat.com'/> .
</para>
</section>
<section>
<title>Kernel Flavors</title>
<para>
<!--Anchor-macro not supported by the docbook formatter, but giving it a shot anyway-->
<anchor id='Kernel_Flavors'/>
</para>
<para>
Fedora Core 6 includes the following kernel builds:
</para>
<itemizedlist>
<listitem>
<para>
Native kernel, for use in most systems. Configured sources are
available in the
<filename>kernel-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
package.
</para>
</listitem>
<listitem>
<para>
kernel-PAE, for use in 32-bit x86 systems with > 4GB of RAM,
or with CPUs that have a 'NX (No eXecute)' feature. This
kernel support both uniprocessor and multi-processor systems.
</para>
</listitem>
<listitem>
<para>
Virtualization kernel for use with the Xen emulator package.
Configured sources are available in the
<filename>kernel-xen-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
package.
</para>
</listitem>
<listitem>
<para>
Kdump kernel for use with
<systemitem>kexec</systemitem>/<systemitem>kdump</systemitem>
capabilities. Configured sources are available in the
<filename>kernel-kdump-devel-<replaceable><version></replaceable>.<replaceable><arch></replaceable>.rpm</filename>
package.
</para>
</listitem>
</itemizedlist>
<para>
You may install kernel headers for all kernel flavors at the same
time. The files are installed in the
<filename>/usr/src/kernels/<replaceable><version></replaceable>-[xen|kdump]-<replaceable><arch></replaceable>/</filename>
tree. Use the following command:
</para>
<screen>su -c 'yum install kernel-{PAE,xen,kdump}-devel'</screen>
<para>
Select one or more of these flavors, separated by commas and no
spaces, as appropriate. Enter the <systemitem
class="username">root</systemitem> password when prompted.
</para>
<para>
<note>
<title>Default Kernel Provides SMP</title>
<para>
There is no separate SMP kernel available for Fedora Core 6 on
i386, x86_64 and ppc64. Multiprocessor support is provided by
the native kernel.
</para>
</note>
</para>
<para>
<note>
<title>PowerPC Kernel Support</title>
<para>
There is no support for Xen or kdump for the PowerPC
architecture in Fedora Core 6 test3. 32-bit PowerPC does still
have a separate SMP kernel.
</para>
</note>
</para>
</section>
<section>
<title>Reporting Bugs</title>
<para>
Refer to
<ulink url='http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html'/>
for information on reporting bugs in the Linux kernel. You may
also use <ulink url='http://bugzilla.redhat.com'/> for reporting
bugs that are specific to Fedora.
</para>
</section>
<section>
<title>Following Generic Textbooks</title>
<para>
Many of the tutorials, examples, and textbooks about Linux kernel
development assume the kernel sources are installed under the
<filename class="directory">/usr/src/linux/</filename> 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:
</para>
<screen>su -c 'ln -s /usr/src/kernels/<replaceable><version></replaceable>.<replaceable><release></replaceable>-<replaceable><arch></replaceable> /usr/src/linux'</screen>
<para>
Enter the <systemitem class="username">root</systemitem> password
when prompted.
</para>
</section>
<section>
<title>Preparing for Kernel Development</title>
<para>
Fedora Core 6 does not include the
<filename>kernel-source</filename> package provided by older
versions since only the <filename>kernel-devel</filename> package
is required now to build external modules. Configured sources are
available, as described in this kernel flavors section.
</para>
<note>
<title>Instructions Refer to Current Kernel</title>
<para>
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
<literal><replaceable><version></replaceable></literal>
refers to the kernel version shown by the command: <command>uname
-r</command>.
</para>
</note>
<para>
Users who require access to Fedora Core original kernel sources
can find them in the kernel <filename
class="extension">.src.rpm</filename> package. To create an
exploded source tree from this file, perform the following steps:
</para>
<note>
<title>Do Not Build Packages as Super-user (root)</title>
<para>
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 <filename
class="directory">/usr/src/linux</filename> in their kernel
instructions. If you use these instructions, simply substitute
<filename class="directory">~/rpmbuild/BUILD/kernel-<replaceable><version></replaceable>/linux-<replaceable><version></replaceable>.<replaceable><arch></replaceable></filename>."]]
</para>
</note>
<procedure>
<step>
<para>
Prepare a RPM package building environment in your home
directory. Run the following commands:
</para>
<screen>su -c 'yum install rpmdevtools yum-utils' rpmdev-setuptree</screen>
</step>
<step>
<para>
Enter the <systemitem class="username">root</systemitem> password when prompted.
</para>
</step>
<step>
<para>
Download the
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
file. Enable any appropriate source repositories, such as
Core, Updates, or Testing, with the <option>-e</option>
switch:
</para>
<screen>yumdownloader -e core-source -e updates-source --source kernel</screen>
</step>
<step>
<para>
Enter the <systemitem class="username">root</systemitem>
password when prompted.
</para>
</step>
<step>
<para>
Install
<filename>kernel-<replaceable><version></replaceable>.src.rpm</filename>
using the command:
</para>
<screen>rpm -Uvh kernel-<replaceable><version></replaceable>.src.rpm</screen>
</step>
<step>
<para>
This command writes the RPM contents into <filename
class="directory">${HOME}/rpmbuild/SOURCES</filename> and
<filename class="directory">${HOME}/rpmbuild/SPECS</filename>,
where <varname>${HOME}</varname> is your home directory.
</para>
<note>
<title>Space Required</title>
<para>
The full kernel building process may require several
gigabytes of extra space on the file system containing your
home directory.
</para>
</note>
</step>
<step>
<para>
Prepare the kernel sources using the commands:
</para>
<screen><![CDATA[cd ~/rpmbuild/SPECS
rpmbuild -bp --target $(uname -m) kernel-2.6.spec]]></screen>
</step>
<step>
<para>
The kernel source tree is located in the <filename
class="directory">~/rpmbuild/BUILD/kernel-<replaceable><version></replaceable>/linux-<replaceable><version></replaceable>.<replaceable><arch></replaceable></filename>
directory.
</para>
<para>
The configurations for the specific kernels shipped in Fedora
Core 6 are in the <filename
class="directory">~/rpmbuild/BUILD/kernel-<replaceable><version></replaceable>/linux-<replaceable><version></replaceable>.<replaceable><arch></replaceable>/configs</filename>
directory. For example, the i686 configuration file is named
<filename
class="directory">~/rpmbuild/BUILD/kernel-<replaceable><version></replaceable>/linux-<replaceable><version></replaceable>.<replaceable><arch></replaceable>/configs/kernel-<replaceable><version></replaceable>-i686.config</filename>.
Issue the following command to place the desired configuration
file in the proper place for building:
</para>
<screen>cp configs/<replaceable><desired-config-file></replaceable> .config</screen>
</step>
<step>
<para>
Every kernel gets a name based on its version number. This is
the value the <command>uname -r</command> command displays.
The kernel name is defined by the first four lines of the
kernel <filename>Makefile</filename>. The
<filename>Makefile</filename> has been changed to generate a
kernel with a <emphasis>different</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
<filename>Makefile</filename>.
</para>
<para>
For example, if the <code>uname -r</code> returns the string
<code>2.6.17-1.2345_FC6</code>, change the
<code>EXTRAVERSION</code> definition from this:
</para>
<screen><![CDATA[EXTRAVERSION = -prep ]]></screen>
<para>
to this:
</para>
<screen><![CDATA[EXTRAVERSION = -1.2345_FC6]]></screen>
<para>
That is, substitute everything from the final dash onward.
</para>
</step>
<step>
<para>
Run the following command:
</para>
<screen><![CDATA[make oldconfig]]></screen>
<para>
You may then proceed as usual.
</para>
</step>
</procedure>
<note>
<title>Building Kernel Binary RPMs</title>
<para>
Normally, kernels for Fedora are built using the
<command>rpmbuild</command> utility and a specfile. Your results
may vary if you use the kernel's built-in <command>make
rpm</command> target.
</para>
</note>
</section>
<section>
<title>Building Only Kernel Modules</title>
<para>
An exploded source tree is not required to build a kernel module,
such as your own device driver, against the currently in-use
kernel. Only the <filename>kernel-devel</filename> package is
required to build external modules. If you did not select it
during installation, use <application>Pirut</application> to
install it, going to <menuchoice>
<guimenu>Applications</guimenu>
<guimenuitem>Add/Remove Software</guimenuitem></menuchoice> or
use <command>yum</command> to install it. Run the following
command to install the <filename>kernel-devel</filename> package
using <filename>yum</filename>.
</para>
<screen><![CDATA[su -c 'yum install kernel-devel'
]]></screen>
<para>
For example, to build the <filename>foo.ko</filename> module, create the
following <filename>Makefile</filename> in the directory containing the
<filename>foo.c</filename> file:
</para>
<screen><![CDATA[obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) M=$(PWD) modules
]]></screen>
<para>
Issue the <command>make</command> command to build the
<filename>foo.ko</filename> module.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE Legacy.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Legacy">
<title>Fedora Legacy - Community Maintenance Project</title>
<!--RAW HTML: <h2>Fedora Legacy - Community Maintenance Project</h2>-->
<para>
The Fedora Legacy Project is a community-supported open source project to
extend the lifecycle of select <firstterm>maintenance mode</firstterm> 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 <ulink
url='http://fedoraproject.org/wiki/Legacy'/>.
</para>
<para>
<note>
<title>Legacy Repo Included in Fedora Core 6</title>
<para>
Fedora Core 6 ships with a software repository configuration for
Fedora Legacy. This is a huge step in integrating Fedora Legacy
with the Fedora Project at large and Fedora Core specifically.
This repository is not enabled by default in this release.
</para>
</note>
</para>
<para>
Currently the Fedora Legacy Project maintains the following
distributions and releases in maintenance mode:
</para>
<itemizedlist>
<listitem>
<para>
Fedora Core 3
</para>
</listitem>
<listitem>
<para>
Fedora Core 4
</para>
</listitem>
</itemizedlist>
<para>
The Fedora Legacy Project provides updates for these releases as
long as there is community interest and participation. When interest
is not sustained further, maintenance mode ends with the second test
release for the fourth subsequent Core release. For example,
maintenance mode for Fedora Core 3, 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.
</para>
<para>
The Fedora Legacy Project always needs volunteers to perform quality
assurance testing on packages waiting to be published as updates.
Refer to
<ulink url='http://fedoraproject.org/wiki/Legacy/QATesting'/> for
more information. Also visit our issues list at
<ulink url='http://fedoraproject.org/wiki/Legacy/QATesting#issues'/>
for further information and pointers to bugs we have in the queue.
</para>
<para>
If you need help in getting started, visit the project home page on
the Wiki at <ulink url='http://fedoraproject.org/wiki/Legacy'/>, or
the Mentors page at
<ulink url='http://fedoraproject.org/wiki/Mentors'/>. If you are
looking for others ways to participate in Fedora, refer to
<ulink url='http://fedoraproject.org/wiki/HelpWanted'/>.
</para>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE Multimedia.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Multimedia">
<title>Multimedia</title>
<para>
Fedora Core includes applications for assorted multimedia functions,
including playback, recording and editing. Additional packages are
available through the Fedora Extras repository. For additional
information about multimedia in Fedora, refer to the Multimedia
section of the Fedora Project website at
<ulink url='http://fedoraproject.org/wiki/Multimedia'/>.
</para>
<section>
<title>Multimedia Players</title>
<para>
The default installation of Fedora Core includes
<application>Rhythmbox</application> and
<application>Totem</application> for media playback. The Fedora
Core and Fedora Extras repositories include many other popular
programs such as the <application>XMMS</application> player and
KDE's <application>amaroK</application>. Both GNOME and KDE have a
selection of players that can be used with a variety of formats.
Third parties may offer additional programs to handle other
formats.
</para>
<para>
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
<ulink url='http://www.alsa-project.org/'/>. Users may still
experience issues when multiple users log into the system.
Depending upon hardware and software configurations, multiple
users may not be able to use the sound hardware simultaneously.
</para>
<para>
<application>Helix Player</application> has been removed from this
release since it duplicates the functionality of
<application>Totem</application>. <application>Totem</application>
also uses the <application>GStreamer</application> media
framework, which is used by other multimedia applications in
Fedora Core. With <application>GStreamer</application>, users can
easily add support for additional codecs to all included
applications.
</para>
</section>
<section>
<title>Ogg and Xiph.Org Foundation Formats</title>
<para>
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
flexible alternatives to more popular, restricted
formats. The Fedora Project encourages the use of open 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 <ulink url='http://www.xiph.org/'/>.
</para>
</section>
<section>
<title>MP3, DVD, and Other Excluded Multimedia Formats</title>
<para>
Fedora Core and Fedora Extras software repositories cannot include
support for MP3 or DVD video playback or recording. The MP3
formats are patented, and the patent holders have not provided the
necessary patent licenses. DVD video formats are patented and
equipped with an encryption scheme. The patent holders have not
provided the necessary patent licenses, and the code needed to
decrypt CSS-encrypted discs may violate the Digital Millennium
Copyright Act, a copyright law of the United States. Fedora also
excludes other multimedia software due to patent, copyright or
license restrictions, including Adobe's Flash Player and and Real
Media's Real Player. For more on this subject, please refer to
<ulink url='http://fedoraproject.org/wiki/ForbiddenItems'/>.
</para>
<para>
While other MP3 options may be available for Fedora, Fluendo now
offers a free MP3 plugin for GStreamer that has the necessary
patent license for end users. This plugin enables MP3 support
in applications that use the GStreamer framework as a backend.
Fedora does not include this plugin since we prefer to support and
encourage the use of patent unrestricted open formats instead. For
more information about the MP3 plugin, visit Fluendo's website at
<ulink url='http://www.fluendo.com/'/>.
</para>
</section>
<section>
<title>CD and DVD Authoring and Burning</title>
<para>
Fedora Core and Fedora Extras software repositories includes 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 <filename>gnomebaker</filename> or
<filename>graveman</filename> packages from Fedora Extras, or the
older <filename>xcdroast</filename> package from Fedora Core. KDE
users can use the robust <filename>k3b</filename> package,
available in Fedora Extras, for these tasks. Console tools include
<filename>cdrecord</filename>, <filename>readcd</filename>,
<filename>mkisofs</filename>, and other popular applications.
</para>
</section>
<section>
<title>Screencasts</title>
<para>
You can use Fedora to create and play back
<firstterm>screencasts</firstterm>, which are recorded desktop
sessions, using open technologies. Fedora Extras software
repository includes <filename>istanbul</filename>, 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 <ulink
url='http://fedoraproject.org/wiki/ScreenCasting'/>.
</para>
</section>
<section>
<title>Extended Support through Plugins</title>
<para>
Most of the media players in Fedora Core and Fedora Extras
software repositories can use plugins to add support for
additional media formats and sound output systems. Some use
powerful multimedia frameworks, such as the
<filename>gstreamer</filename> package, to handle media format
support and sound output. Fedora Core and Fedora Extras software
repositories offer plugin packages for these backends and for
individual applications. Third parties may provide additional
plugins to add even greater capabilities.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE OverView.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-OverView">
<title>Release Highlights</title>
<section>
<title>Fedora Core 6 Tour</title>
<para>
You can find a tour filled with pictures and videos of this
exciting new release at
<ulink url='http://fedoraproject.org/wiki/Tours/FedoraCore6'/>.
</para>
</section>
<section>
<title>New in Fedora Core 6</title>
<para>
This release includes significant new versions of many key
components and technologies. The following sections provide a
brief overview of major changes from the last release of Fedora
Core.
</para>
<section>
<title>Desktop</title>
<itemizedlist>
<listitem>
<para>
This release has an improved look and feel for various
international languages, with a new
<ulink url='http://fedoraproject.org/wiki/Fonts/DejaVu'>DejaVu</ulink>
default font.
</para>
</listitem>
<listitem>
<para>
The <application>Compiz</application> window manager
provides better visual feedback and a variety of desktop
effects by using the AIGLX framework. More information is
available from the
<ulink url='http://fedoraproject.org/wiki/RenderingProject'>Fedora
Rendering Project</ulink>.
</para>
</listitem>
<listitem>
<para>
This release features an update applet called
<application>puplet</application> that provides user
notifications when software updates are available. For more
information, refer to <ulink
url='http://fedoraproject.org/wiki/YumApplet'/>.
</para>
</listitem>
<listitem>
<para>
This release includes a completely rewritten and enhanced
<ulink url='http://www.redhat.com/magazine/022aug06/features/fc6_print/'>system-config-printer</ulink>
that uses the latest CUPS 1.2. More technical details are
available at
<ulink url='http://fedoraproject.org/wiki/Printing/AdminToolOutline'/>
and
<ulink url='http://fedoraproject.org/wiki/Printing/AdminToolSpecifics'/>.
</para>
</listitem>
<listitem>
<para>
This release features
<ulink url='http://www.gnome.org/start/2.16/'>GNOME
2.16</ulink> and KDE 3.5.4.
</para>
</listitem>
<listitem>
<para>
Fedora Core 6 includes a refreshing new "DNA" theme, which
is part of a continuous team effort from the
<ulink url='http://fedoraproject.org/wiki/Artwork'>Fedora
Artwork Project</ulink>.
</para>
</listitem>
<listitem>
<para>
This release includes
<ulink url='http://people.redhat.com/zcerza/dogtail/'>Dogtail</ulink>
which provides a graphical test and automation framework for
the desktop.
</para>
</listitem>
<listitem>
<para>
This release features the <ulink
url='http://lists.gnucash.org/pipermail/gnucash-announce/2006-July/000069.html'>GnuCash
2.0</ulink> accounting application, which provides major new
features and interface improvements. For more information, refer to
<ulink url='http://www.gnucash.org/features.phtml'>GnuCash
Features</ulink>.
</para>
</listitem>
<listitem>
<para>
<application>Helix Player</application> has been
moved to Fedora Extras, since the included
<application>Totem</application> media player
provides similar functionality.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Performance</title>
<itemizedlist>
<listitem>
<para>
All Fedora Core applications have been rebuilt using
<ulink url='http://sources.redhat.com/ml/binutils/2006-06/msg00418.html'>`DT_GNU_HASH`</ulink>,
which provides up to a 50%
<ulink url='http://lwn.net/Articles/192624/'>performance
boost</ulink> on applications using dynamic linking.
</para>
</listitem>
<listitem>
<para>
IMAP support for the
<application>Evolution</application> personal
information manager is much improved in this release.
</para>
</listitem>
<listitem>
<para>
This release improves performance and manageability by
splitting up package dependencies in a much more granular
way. Affected packages include <package>beagle</package>,
<package>evince</package>, and
<package>NetworkManager</package>. For more information on
these and other related changes, refer to <xref
linkend="sn-PackageNotes"/>.
</para>
</listitem>
<listitem>
<para>
In this release, the performance of <command>yum</command>,
<application>Pirut</application>, and
<application>Pup</application> has been significantly
improved.
</para>
</listitem>
<listitem>
<para>
<ulink
url='http://fontconfig.org/wiki/2_2e4_20release_20notes'><application>Fontconfig
2.4</application></ulink> improves startup performance
and memory footprint significantly.
</para>
</listitem>
<listitem>
<para>
The performance of the Fedora's default ext3 filesystem has
been
<ulink url='http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h…'>boosted</ulink>
in recent versions of the Linux kernel.
</para>
</listitem>
<listitem>
<para>
A new background service caches and increases the
performance of network filesystems such as AFS and NFS. This
service is part of the ongoing
<ulink url='http://lwn.net/Articles/100321/'>CacheFS
development</ulink> by Red Hat.
</para>
</listitem>
<listitem>
<para>
CUPS printing service starts much more faster since it now
detects devices on demand.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>System Administration</title>
<itemizedlist>
<listitem>
<para>
The Fedora installer,
<application>Anaconda</application>, can now connect
to additional repositories such as Updates and Fedora
Extras, and users can install applications from these
repositories directly. Support for Fedora Extras is included
by default on network-connected interactive installs.
</para>
</listitem>
<listitem>
<para>
<emphasis role='strong'>Anaconda</emphasis> also now
supports IPv6.
</para>
</listitem>
<listitem>
<para>
This release features a new virtualization manager, <ulink
url='http://virt-manager.et.redhat.com/'><application>virt-manager</application></ulink>,
which adds a graphical management interface layer on top of
<application>Xen</application>.
</para>
</listitem>
<listitem>
<para>
This release increases usability of SELinux by providing a
<ulink
url='http://fedoraproject.org/wiki/SELinux/setroubleshoot'>graphical
troubleshooting tool</ulink> and enhancements to the
<application>Nautilus</application> file manager.
</para>
</listitem>
<listitem>
<para>
Fedora now features integrated smart card capabilities, for
secure authentication out of the box using the new
<ulink url='http://directory.fedora.redhat.com/wiki/CoolKey'>CoolKey</ulink>
system.
</para>
</listitem>
<listitem>
<para>
This release introduces a new tool,
<application>lvm2-cluster</application>, for intuitively
managing cluster volumes.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>System Level Changes</title>
<itemizedlist>
<listitem>
<para>
Fedora Core 6 features a 2.6.18 based kernel. There are no
longer separate kernels for SMP and UP processors on any
architecture. A single kernel now automatically detects your
processor configuration and enables the proper bits for it.
</para>
</listitem>
<listitem>
<para>
<application>X.org 7.1</application> now dynamically
configures monitor resolution and refresh rates to limit the
amount of required user configuration.
</para>
</listitem>
<listitem>
<para>
This release supports <ulink
url='http://fedoraproject.org/wiki/FedoraOnMactel'>Apple Macintosh
systems</ulink> running the new Intel processors.
</para>
</listitem>
<listitem>
<para>
This release includes better i18n support using the default
<application>SCIM</application> input method,
including more languages such as Sinhalase (Sri Lanka) and
Oriya, Kannada, and Malayalam (India). Fedora now provides
an easy interface to switch the input methods using
<command>im-chooser</command>.
</para>
</listitem>
<listitem>
<para>
The <application>GNOME 1.x</application> legacy stack has
been removed from Fedora Core, and added to Fedora Extras.
</para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>Road Map</title>
<para>
The proposed plans for the next release of Fedora are available at
<ulink url='http://fedoraproject.org/wiki/RoadMap'/>.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE PackageChanges.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-PackageChanges">
<title>Package Changes</title>
<!--RAW HTML: <h2>Package Changes</h2>-->
<para>
<note>
<title>This list is automatically generated</title>
<para>
This list is automatically generated. It is not a good choice
for translation.
</para>
</note>
</para>
<para>
For a list of which packages were updated since the previous
release, refer to
<ulink url='http://fedoraproject.org/wiki/Docs/Beats/PackageChanges/UpdatedPackages'/>.
You can also find a comparison of major packages between all Fedora
versions at <ulink url='http://distrowatch.com/fedora'/>.
</para>
<screen>
<![CDATA[
# 2006-09-29 -- treediff <oldtree> <newtree>
New package alacarte
Simple menu editor for GNOME
New package bouncycastle
Bouncy Castle Crypto Package for Java
New package cachefilesd
CacheFiles userspace management daemon
New package ccid
Generic USB CCID smart card reader driver
New package compat-gcc-34
Compatibility GNU Compiler Collection
New package compiz
OpenGL window and compositing manager
New package coolkey
CoolKey PKCS #11 module
New package dbus-glib
GLib bindings for D-Bus
New package dbus-python
D-Bus Python Bindings
New package dbus-sharp
C# bindings for D-Bus
New package dejavu-lgc-fonts
DejaVu LGC Fonts
New package dogtail
GUI test tool and automation framework
New package esc
Enterprise Security Client Smart Card Client
New package fedora-release-notes
Release Notes for Fedora Core 5.92
New package fonts-sinhala
Fonts for Sinhala
New package gcalctool
A desktop calculator
New package gfs2-utils
Utilities for managing the global filesystem (GFS)
New package gnome-sharp
GTK+ and GNOME bindings for Mono
New package gnome-vfs2-monikers
Monikers for the GNOME virtual file-system
New package gnu-efi
Development Libraries and headers for EFI
New package gnu-getopt
Java getopt implementation
New package gucharmap
Unicode character picker and font browser
New package hesinfo
Command-line Hesiod client.
New package ifd-egate
Axalto Egate SmartCard device driver for PCSC-lite
New package im-chooser
Desktop Input Method configuration tool
New package jakarta-oro
Full regular expressions API
New package kdnssd-avahi
KDE zeroconf implementation based on avahi
New package libdhcp
A library for network interface configuration with DHCP
New package libpfm
a performance monitoring library for Linux/ia64
New package libtirpc
Transport Independent RPC Library
New package libutempter
A privileged helper for utmp/wtmp updates
New package lvm2-cluster
Cluster extenstions for userland logical volume management tools
New package mcstrans
SELinux Translation Daemon
New package notification-daemon
Notification Daemon
New package notify-python
Python bindings for libnotify
New package openais
The openais Standards-Based Cluster Framework executive and APIs
New package openmpi
Open Message Passing Interface
New package orca
Flexible, extensible, and powerful assistive technology
New package pam_pkcs11
PKCS #11/NSS PAM login module
New package paps
Plain Text to PostScript converter
New package pcsc-lite
PC/SC Lite smart card framework and applications
New package perl-IO-Socket-INET6
Perl Object interface for AF_INET|AF_INET6 domain sockets
New package perl-IO-Socket-SSL
Perl library for transparent SSL
New package perl-Net-SSLeay
Perl extension for using OpenSSL
New package perl-Socket6
IPv6 related part of the C socket.h defines and structure manipulators
New package pfmon
a performance monitoring tool for Linux/ia64
New package postgresql-jdbc
JDBC driver for PostgreSQL
New package pygobject2
Python bindings for gobjects
New package pyspi
Python bindings for AT-SPI
New package python-xeninst
Python modules for starting Xen guest installations
New package scim-bridge
SCIM Bridge Gtk IM module
New package scim-sinhala
Sri Lankan input method for SCIM
New package setroubleshoot
Helps troubleshoot SELinux problems
New package unifdef
Unifdef tool for removing ifdef'd lines
New package virt-manager
Virtual Machine Manager
New package werken-xpath
XPath implementation using JDOM
New package wireshark
Network traffic analyzer
New package xkeyboard-config
xkeyboard-config alternative xkb data files
New package xorg-sgml-doctools
X.Org SGML documentation generation tools
New package xorg-x11-docs
X.Org X11 documentation
New package xorg-x11-drv-amd
Xorg X11 AMD Geode video driver
New package xorg-x11-drv-ast
Xorg X11 ast video driver
New package xorg-x11-drv-vmmouse
Xorg X11 vmmouse input driver
New package yum-metadata-parser
A fast metadata parser for yum
New package zenity
Display dialog boxes from shell scripts
Removed package GFS-kernel
Removed package GFS
Removed package Guppi
Removed package HelixPlayer
Removed package bg5ps
Removed package caching-nameserver
Removed package ccs
Removed package ckermit
Removed package cman-kernel
Removed package ddd
Removed package dlm
Removed package dlm-kernel
Removed package eclipse-pydev
Removed package ethereal
Removed package fence
Removed package fence
Removed package freeglut
Removed package gal
Removed package gdk-pixbuf
Removed package gkrellm
Removed package glibc-kernheaders
Removed package gnbd
Removed package gnbd-kernel
Removed package gnome-libs
Removed package gnome-print
Removed package gnopernicus
Removed package gnu.getopt
Removed package gtk+
Removed package gtk-engines
Removed package gulm
Removed package h2ps
Removed package iddev
Removed package imlib
Removed package kon2
Removed package lha
Removed package libghttp
Removed package liblbxutil
Removed package libpng10
Removed package liboldX
Removed package libsetrans
Removed package libstdc++so7
Removed package libxkbui
Removed package longrun
Removed package magma-plugins
Removed package macutils
Removed package magma
Removed package mozilla
Removed package notify-daemon
Removed package oaf
Removed package openmotif
Removed package openobex-apps
Removed package oro
Removed package rhnlib
Removed package valgrind-callgrind
Removed package utempter
Removed package werken.xpath
Removed package xorg-x11-xkbdata
Removed package xpdf
Removed package xscreensaver
]]></screen>
</section>
--- NEW FILE PackageNotes.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-PackageNotes">
<title>Package Notes</title>
<para>
The following sections contain information regarding software
packages that have undergone significant changes for Fedora Core 6.
For easier access, they are generally organized using the same
groups that are shown in the installation system.
</para>
<section>
<title>GNOME Desktop Environment</title>
<para>
The following packages have been split into several packages to
improve performance and manageability as noted:
</para>
<itemizedlist>
<listitem>
<para>
<package>gnome-utils</package>
</para>
</listitem>
<listitem>
<para>
<package>beagle</package>, which no longer depends on
<application>Evolution</application>
</para>
</listitem>
<listitem>
<para>
<package>evince</package>, which no longer depends on
<application>Nautilus</application>
</para>
</listitem>
<listitem>
<para>
<package>NetworkManager</package>, which no longer depends on
<package>bind</package> and
<package>caching-nameserver</package>
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Web Server</title>
<para>
The <package>php</package> package has been split to separate the
command line binary from the CGI executable.
</para>
</section>
<section>
<title>Ext3 File System Utilities</title>
<para>
A new version of <package>e2fsprogs</package> included in this
release has a number of bug fixes. The
<command>ext2online</command> feature has been integrated into
<command>resize2fs</command>, so the <command>ext2online</command>
program has been removed from this package.
</para>
</section>
<section>
<title>Licensing Audit</title>
<para>
The <ulink url='http://fedoraproject.org/wiki/Board'>Fedora
Project Board</ulink> initiated a <ulink
url='http://fedoraproject.org/wiki/FreeSoftwareAnalysis'>licensing
audit</ulink> to ensure all software included in Fedora Core is
compliant with the package licensing guidelines. This process is
now complete, and several changes were made as a result:
</para>
<itemizedlist>
<listitem>
<para>
The <package>openmotif</package> package has been <ulink
url='https://www.redhat.com/archives/fedora-devel-list/2006-August/msg01314.html'>dropped</ulink>
due to a non-free license. Software packages previously
dependent on the <package>openmotif</package> library have
been rebuilt to use <package>lesstif</package>.
</para>
</listitem>
<listitem>
<para>
The <package>macutils</package> package has been <ulink
url='https://www.redhat.com/archives/fedora-maintainers/2006-August/msg00021.html'>dropped</ulink>
due to a non-free license.
</para>
</listitem>
<listitem>
<para>
The <package>ckermit</package> package has been <ulink
url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.h…'>dropped</ulink>
due to a non-free license.
</para>
</listitem>
<listitem>
<para>
The <package>cleanfeed</package> package has been <ulink
url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00401.h…'>dropped</ulink>
due to a non-free license.
</para>
</listitem>
<listitem>
<para>
The <package>aspell-nl</package> package has been <ulink
url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.h…'>changed</ulink>
to include GPL licensed data.
</para>
</listitem>
<listitem>
<para>
The <package>crypto-utils</package> package has been <ulink
url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.h…'>changed</ulink>
to remove PGP licensed code in favor of new GPL licensed code.
</para>
</listitem>
<listitem>
<para>
The <package>netpbm</package> package has been <ulink
url='http://www.redhat.com/archives/fedora-advisory-board/2006-August/msg00271.h…'>changed</ulink>
to remove all unlicensed or improper files from the source
tarball.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Kernel Headers</title>
<para>
The process of generating kernel headers has been <ulink
url='http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h…'>changed</ulink>,
which provides several <ulink
url='http://lkml.org/lkml/2006/7/2/24'>benefits</ulink> included
easier maintenance and consistency.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE ProjectOverview.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-ProjectOverview">
<title>Fedora Project - Freedom to the Core</title>
<para>
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
<ulink url='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 at
<ulink url='http://fedoraproject.org/'/>.
</para>
<para>
The Fedora Project is driven by the individuals that contribute to
it. As a tester, developer, documenter, or translator, you can make
a difference. Refer to <ulink
url='http://fedoraproject.org/wiki/HelpWanted'/> for details. For
information on the channels of communication for Fedora users and
contributors, refer to <ulink
url='http://fedoraproject.org/wiki/Communicate'/>.
</para>
<para>
In addition to the website, the following mailing lists are
available:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='mailto:fedora-list@redhat.com'>fedora-list(a)redhat.com</ulink>,
for users of Fedora Core releases
</para>
</listitem>
<listitem>
<para>
<ulink url='mailto:fedora-test-list@redhat.com'>fedora-test-list(a)redhat.com</ulink>,
for testers of Fedora Core test releases
</para>
</listitem>
<listitem>
<para>
<ulink url='mailto:fedora-devel-list@redhat.com'>fedora-devel-list(a)redhat.com</ulink>,
for developers, developers, developers
</para>
</listitem>
<listitem>
<para>
<ulink url='mailto:fedora-docs-list@redhat.com'>fedora-docs-list(a)redhat.com</ulink>,
for participants of the Documentation Project
</para>
</listitem>
</itemizedlist>
<para>
To subscribe to any of these lists, send an email with the word
"subscribe" in the subject to
<email><replaceable><listname></replaceable>-request</email>,
where <replaceable><listname></replaceable> is one of the
above list names. Alternately, you can subscribe to Fedora mailing
lists through the Web interface at <ulink
url='http://www.redhat.com/mailman/listinfo/'/>.
</para>
<para>
The Fedora Project also uses several IRC (Internet Relay Chat)
channels. IRC is a real-time, text-based form of communication,
similar to Instant Messaging. With it, you may have conversations
with multiple people in an open channel, or chat with someone
privately one-on-one. To talk with other Fedora Project participants
via IRC, access the Freenode IRC network. Refer to the Freenode
website at <ulink url='http://www.freenode.net/'/> for more
information.
</para>
<para>
Fedora Project participants frequent the
<systemitem>#fedora</systemitem> channel on the Freenode network,
while Fedora Project developers may often be found on the
<systemitem>#fedora-devel</systemitem> 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 <ulink
url='http://fedoraproject.org/wiki/Communicate'/>.
</para>
<para>
In order to talk on the <systemitem>#fedora</systemitem> channel,
you need to register your nickname, or <firstterm>nick</firstterm>.
Instructions are given when you <command>/join</command> the
channel.
</para>
<para>
<note>
<title>IRC Channels</title>
<para>
The Fedora Project and Red Hat have no control over the Fedora
Project IRC channels or their content.
</para>
</note>
</para>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE README-BURNING-ISOS.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<title>Discs</title>
<section>
<title>Introduction</title>
<para>
The Fedora Core distribution is provided in the form of ISO 9660
standard filesystem images. You can copy these ISO images onto
either CDROM or DVD media to produce a bootable disc.
</para>
<para>
Before you can install Fedora Core on a computer, you must
transfer, or <firstterm>burn</firstterm>, the ISO files to blank
disc media (CD-R/RW or DVD-R/RW). This document describes the
procedure for burning these files using a few common tools. This
document assumes that you have no experience with Linux, and that
you are using Microsoft Windows for the purpose of downloading and
burning the files.
</para>
</section>
<section>
<title>Downloading</title>
<para>
The ISO files are large, and it may take a long time to download
them, especially using a dial-up modem. You may want to use a
download manager.
</para>
<section>
<title>Choosing CD or DVD</title>
<para>
Fedora Core is distributed on multiple CD-sized ISO image files,
or a single DVD-sized ISO image file. You can use the single DVD
ISO file if your computer meets the following requirements:
</para>
<itemizedlist>
<listitem>
<para>
It has a DVD-writable or DVD-rewritable drive
</para>
</listitem>
<listitem>
<para>
It has a NTFS drive with sufficient space to hold the image
file
</para>
</listitem>
</itemizedlist>
<para>
To write the DVD ISO file to a disc, your computer needs to have
a drive that will write to DVD media. If your computer has a
drive that only writes CD media and not DVD media, download the
CD-sized files instead.
</para>
<para>
Some file systems cannot store files larger than 2 GB, such as
the DVD image. The commonly-used NTFS file system does not have
this limitation, but many other non-NTFS formats do, such as
FAT32. To check the format of a drive under Windows such as
<systemitem>C:</systemitem>, select the
<guilabel>Start</guilabel> menu and then <guilabel>My
Computer</guilabel>. Right-click the drive you want to check,
and choose <guilabel>Properties</guilabel>. The resulting dialog
displays the format for that file system. If you do not have an
NTFS drive with enough free space, download the CD-sized files
instead.
</para>
<para>
Create a new directory where you can download all of these
files. You need approximately 700 MiB of free space available
for each CD-sized ISO file, or approximately 3.5 GiB for the
DVD-sized ISO file. This document assumes you have downloaded
the files to the folder <filename class="directory">C:\Documents
and Settings\Owner\My Documents\My Downloads\Fedora
Core</filename>.
</para>
</section>
<section>
<title>Choosing the ISO Files</title>
<para>
The exact files you need from the download server depend upon
your system and the version of Fedora Core you are downloading.
The files you need are named in the form of
<filename>FC-<replaceable><version></replaceable>-<replaceable><arch></replaceable>-disc<replaceable><count></replaceable>.iso</filename>,
where "<replaceable><version></replaceable>" is the
version of Fedora Core you wish to download,
"<replaceable><arch></replaceable>" is your computer's
processor architecture, and
"<replaceable><count></replaceable>" is the disc number
for each of the installation CDs.
</para>
<para>
The computer processor architecture is usually
<systemitem>i386</systemitem> for 32-bit PCs, including the
Pentium and Athlon processor families. The architecture is
usually <systemitem>x86_64</systemitem> for 64-bit PCs,
including the Athlon 64 processor family. The architecture is
usually <systemitem>ppc</systemitem> for PowerPC computers,
including most of Apple's Mac offerings. If in doubt, your
system probably requires the <systemitem>i386</systemitem>
versions.
</para>
<para>
If you are downloading Fedora Core 6 for a Pentium 4 computer,
for example, you need these files:
</para>
<itemizedlist>
<listitem>
<para>
<filename>FC-6-i386-disc1.iso</filename>
</para>
</listitem>
<listitem>
<para>
<filename>FC-6-i386-disc2.iso</filename>
</para>
</listitem>
<listitem>
<para>
<filename>FC-6-i386-disc3.iso</filename>
</para>
</listitem>
<listitem>
<para>
<filename>FC-6-i386-disc4.iso</filename>
</para>
</listitem>
<listitem>
<para>
<filename>FC-6-i386-disc5.iso</filename>
</para>
</listitem>
</itemizedlist>
<para>
Or, if you prefer to install from a single DVD, you only need
this file:
</para>
<itemizedlist>
<listitem>
<para>
<filename>FC-6-i386-DVD.iso</filename>
</para>
</listitem>
</itemizedlist>
<para>
You may also need the <code>SHA1SUM</code> file to verify that
the files you have downloaded are complete and correct.
</para>
</section>
</section>
<section>
<title>Validating the Files</title>
<para>
Errors can occur during the download, even if your download
manager reports none. Therefore it is <emphasis role='strong'>very
important</emphasis> to check that the files have not been
corrupted in any way. This is the purpose of the
<filename>SHA1SUM</filename> file. It contains one line for each
of the available ISO files with a content verification code called
a <firstterm>hash</firstterm> computed from the original ISO files.
</para>
<para>
<note>
<title>BitTorrent Automatic Error Checking</title>
<para>
BitTorrent automatically performs this error checking during
downloads. If your BitTorrent application reports all files
have been successfully downloaded, you can safely skip this
step.
</para>
</note>
</para>
<section>
<title>Validating in the Windows Graphical Environment</title>
<para>
There are a number of free (as in cost) products available for
file validation and hashing that have point and click
interfaces. Here are links to a few of them:
</para>
<itemizedlist>
<listitem>
<para>
HashCalc: <ulink url='http://www.slavasoft.com/hashcalc/'/>
</para>
</listitem>
<listitem>
<para>
eXpress CheckSum Calculator (XCSC): <ulink
url='http://www.irnis.net/soft/xcsc/'/>
</para>
</listitem>
</itemizedlist>
<para>
Follow the instructions provided to install the program. When
you run the program, use the file selection tools provided to
select your downloaded ISO image files. Then select the SHA-1
algorithm for calculation, and run the tool. The program takes
some time to complete, since it must read the entire ISO file.
</para>
<para>
Open the file <filename>SHA1SUM</filename> with a text editor,
such as <application>WordPad</application>, to display its
contents. Make sure the hash displayed by the hash tool for
<emphasis role='strong'>each</emphasis> of the downloaded ISO
files <emphasis role='strong'>exactly</emphasis> matches the
corresponding hash in the <filename>SHA1SUM</filename> file.
</para>
<para>
If all of the hashes match, you can then burn the ISO files to
media. If a file does not match, you may have to download it
again.
</para>
<para>
<important>
<title>CAVEAT EMPTOR</title>
<para>
The Fedora Project and Red Hat, Inc. have no control over
external sites such as the ones listed above, or the
programs they provide.
</para>
</important>
</para>
</section>
<section>
<title>Validating at the Windows Command Prompt</title>
<para>
To check the files using the command prompt, you need to
download the program <filename>sha1sum.exe</filename>. For
instructions and the link to download the program, refer to
<ulink
url='http://lists.gnupg.org/pipermail/gnupg-announce/2004q4/000184.html'/>.
</para>
<para>
The <filename>sha1sum.exe</filename> program computes and
displays hashes. To use it, save
<filename>sha1sum.exe</filename> to the same directory as the
ISO files. Select <guilabel>Run...</guilabel> from the Start
menu and then enter <userinput>cmd</userinput> for the name of
the program to start a <application>Command Prompt</application>
window. Then change into the download directory. Run
<command>sha1sum</command> with each ISO file like this:
</para>
<screen><![CDATA[cd "C:\Documents and Settings\Owner\My Documents\My Downloads\Fedora Core"
sha1sum.exe FC5-i386-disc1.iso]]></screen>
<para>
The program takes some time to complete, since it must read the
entire ISO file.
</para>
<para>
Open the file <filename>SHA1SUM</filename> with a text editor,
such as <application>WordPad</application>, to display its
contents. Make sure the hash displayed by
<filename>sha1sum.exe</filename> for <emphasis
role='strong'>each</emphasis> of the downloaded ISO files
<emphasis role='strong'>exactly</emphasis> matches the
corresponding hash in the <filename>SHA1SUM</filename> file.
</para>
<para>
If all of the hashes match, the ISO files can be burned to
media. If a file does not match, you may have to download it
again.
</para>
</section>
</section>
<section>
<title>Burning</title>
<para>
The process of burning a CD is not always obvious to the users of
Windows. Windows applications often let users burn data discs by
simply dragging the source files into a box and clicking the
<guilabel>Burn</guilabel> button.
</para>
<para>
In reality, though, the burning software performs two operations.
First, it creates an ISO 9660 standard image, just like the ones
used to install Fedora Core, from the source files that were
dragged into the box. Second, it transfers that ISO file onto the
blank CD. If the original source file was already an ISO image,
the resulting CD is not usable for installation purposes.
</para>
<para>
To create the Fedora installation CDs, <emphasis role='strong'>it
is vital that you only perform the second step</emphasis> with
the Fedora Core ISO files. The steps required to do this using
several popular CD burning applications are listed below.
</para>
<section>
<title>Using The ISO Recorder V2 Power Toy</title>
<para>
Obtain and install the ISO Recorder power toy from the <ulink
url='http://isorecorder.alexfeinman.com/isorecorder.htm'/> web
site.
</para>
<procedure>
<step>
<para>
In Explorer, right click on the first Fedora Code ISO file
</para>
</step>
<step>
<para>
In the context menu, select "Copy image to CD"
</para>
</step>
<step>
<para>
Follow the steps given by the "CD Recording Wizard" pop-up
</para>
</step>
<step>
<para>
Repeat for the remaining ISO files
</para>
</step>
</procedure>
</section>
<section>
<title>Using Roxio Easy Media Creator 7</title>
<procedure>
<step>
<para>
Start "Creator Classic"
</para>
</step>
<step>
<para>
Select "Other Tasks"
</para>
</step>
<step>
<para>
Select "Burn from Disc Image File"
</para>
</step>
<step>
<para>
Choose the first Fedora Core ISO file and burn it
</para>
</step>
<step>
<para>
Repeat the above steps for each of the other ISO files
</para>
</step>
</procedure>
</section>
<section>
<title>Using Nero Burning ROM 5</title>
<procedure>
<step>
<para>
Start the program
</para>
</step>
<step>
<para>
Open the "File" menu
</para>
</step>
<step>
<para>
Select "Burn Image"
</para>
</step>
<step>
<para>
Choose the first Fedora Core ISO file and burn it
</para>
</step>
<step>
<para>
Repeat the above steps for each of the other ISO files
</para>
</step>
</procedure>
</section>
<section>
<title>Using Nero Express 6</title>
<procedure>
<step>
<para>
Start the program
</para>
</step>
<step>
<para>
Select "Disc Image or Saved Project"
</para>
</step>
<step>
<para>
An Open dialog appears. Select the first Fedora Core ISO
file. Click Open.
</para>
</step>
<step>
<para>
The next screen allows you to select Writing Speed. You
should set this to 4x for DVD, or 16x for CD, for best
performance.
</para>
</step>
<step>
<para>
Click Next to Burn
</para>
</step>
<step>
<para>
Repeat the steps above for the other ISO files
</para>
</step>
</procedure>
</section>
</section>
<section>
<title>Testing Your Discs</title>
<para>
In order to be certain the CDs will work on your system, you may
wish to burn only disc 1 and then perform the following process
before burning the others:
</para>
<procedure>
<step>
<para>
Following the directions from your computer's manufacturer,
make sure your computer's BIOS is set to boot from the CD
drive.
</para>
</step>
<step>
<para>
Reboot the computer with disc 1 in the CD drive. The boot
menu for the Fedora Core installer appears.
</para>
</step>
<step>
<para>
Press <emphasis role='strong'>Enter</emphasis>.
</para>
</step>
<step>
<para>
Follow the directions on-screen until you are asked if you
would like to perform a media check.
</para>
</step>
<step>
<para>
Conduct the check against the first disc. If the check
succeeds, your disc is correct. At this point the installer
has changed nothing on your computer. Remove the Fedora Core
installation disc and restart the system so that the computer
boots into Windows.
</para>
</step>
<step>
<para>
Burn the other three ISO images. After burning the other
discs, you can repeat the media check to test them all.
</para>
</step>
</procedure>
</section>
<section>
<title>Comments and Feedback</title>
<para>
If you have suggestions for this document, send an email to
relnotes AT fedoraproject.org. We welcome directions for other
tools and platforms.
</para>
</section>
</article>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE README.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % ALPHA "IGNORE">
<!ENTITY % X86 "INCLUDE">
<!ENTITY % IA64 "IGNORE">
<!ENTITY % S390 "IGNORE">
<!ENTITY % HA "IGNORE">
<!ENTITY % X86-64 "IGNORE">
<!ENTITY RH "Red Hat"> <!-- The generic term "Red Hat" -->
<!ENTITY RHL "&RH; Linux"> <!-- The generic term "Red Hat Linux" -->
<!ENTITY FORMAL-RHI "&RH;, Inc."> <!-- Formal version -->
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
<!ENTITY PROJ "&NAME; Project"> <!-- The project's name -->
<!ENTITY DISTRO "&NAME; Core"> <!-- The software's name -->
<!ENTITY DISTROVER "6"> <!-- The software's version -->
]>
<article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final">
<articleinfo>
<title>&DISTRO; &DISTROVER; README</title>
<copyright>
<year>2006</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
<legalnotice id="legalnotice">
<para>
The contents of this CD-ROM are Copyright © 2006
&FORMAL-RHI; and others. Refer to the End User License Agreement
and individual copyright notices in each source package for
distribution terms.
</para>
<para>
&NAME;, &RH;, &RH; Network, the &RH; "Shadow Man" logo, RPM,
Maximum RPM, the RPM logo, Linux Library, PowerTools, Linux
Undercover, RHmember, RHmember More, Rough Cuts, Rawhide and all
&RH;-based trademarks and logos are trademarks or registered
trademarks of &FORMAL-RHI; in the United States and other
countries.
</para>
<para>
Linux is a registered trademark of Linus Torvalds.
</para>
<para>
Motif and UNIX are registered trademarks of The Open Group.
</para>
<para>
Intel and Pentium are registered trademarks of Intel
Corporation. Itanium and Celeron are trademarks of Intel
Corporation.
</para>
<para>
AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of
Advanced Micro Devices, Inc.
</para>
<para>
Windows is a registered trademark of Microsoft Corporation.
</para>
<para>
SSH and Secure Shell are trademarks of SSH Communications
Security, Inc.
</para>
<para>
FireWire is a trademark of Apple Computer Corporation.
</para>
<para>
All other trademarks and copyrights referred to are the property
of their respective owners.
</para>
<para>
The GPG fingerprint of the <computeroutput>"Fedora Project
<fedora(a)redhat.com>"</computeroutput> key is:
</para>
<para>
CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
</para>
</legalnotice>
</articleinfo>
<section id="dir-org">
<title>DIRECTORY ORGANIZATION</title>
<para>
&DISTRO; is delivered on multiple CD-ROMs consisting of
installation CD-ROMs and source code CD-ROMs.
</para>
<para>
The first installation CD-ROM can be directly booted into the
installation on most modern systems, and contains the following
directory structure (where <filename>/mnt/cdrom</filename> is the
mount point of the CD-ROM):
</para>
<screen arch="x86">
<!-- <remark os="test">(x86)</remark> -->
<computeroutput>
/mnt/cdrom
|----> Fedora
| |----> RPMS -- binary packages
| `----> base -- information on this release of Fedora
| Core used by the installation process
|----> images -- boot and driver disk images
|----> isolinux -- files necessary to boot from CD-ROM
|----> repodata -- repository information used by the
| installation process
|----> README -- this file
|----> RELEASE-NOTES -- the latest information about this release
| of Fedora Core
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat
</computeroutput>
</screen>
<!-- repetitive for the moment
<screen arch="x86_64">
<remark os="test">(x86_64)</remark>
<computeroutput>
/mnt/cdrom
|- - - -> Fedora
| |- - - -> RPMS - - binary packages
| `- - - -> base - - information on this release of Fedora
| Core used by the installation process
|- - - -> images - - boot disk ISO image
|- - - -> isolinux - - files necessary to boot from CD-ROM
|- - - -> README - - this file
|- - - -> RELEASE-NOTES - - the latest information about this release
| of Fedora Core
`- - - -> RPM-GPG-KEY - - GPG signature for packages from Red Hat
</computeroutput>
</screen>
-->
<para>
The remaining Installation CD-ROMs are similar to Installation
CD-ROM 1, except that only the <filename>Fedora</filename>
subdirectory is present.
</para>
<para>
The directory layout of each source code CD-ROM is as follows:
</para>
<screen>
<computeroutput>
/mnt/cdrom
|----> SRPMS -- source packages
`----> RPM-GPG-KEY -- GPG signature for packages from Red Hat
</computeroutput>
</screen>
<para>
If you are setting up an installation tree for NFS, FTP, or HTTP
installations, you need to copy the
<filename>RELEASE-NOTES</filename> files and all files from the
<filename>Fedora</filename> directory on discs 1-5. On Linux and
Unix systems, the following process will properly configure the
/target/directory on your server (repeat for each disc):
</para>
<orderedlist>
<listitem>
<para>
Insert disc
</para>
</listitem>
<listitem>
<para>
<command>mount /mnt/cdrom</command>
</para>
</listitem>
<listitem>
<para>
<command>cp -a /mnt/cdrom/Fedora /target/directory</command>
</para>
</listitem>
<listitem>
<para>
<command>cp /mnt/cdrom/RELEASE-NOTES*
/target/directory</command>
</para>
<para>
<command>cp -a /mnt/cdrom/repodata /target/directory</command>
</para>
<para>
(Do this only for disc 1)
</para>
</listitem>
<listitem>
<para>
<command>umount /mnt/cdrom</command>
</para>
</listitem>
</orderedlist>
</section>
<section id="installing">
<title>INSTALLING</title>
<para>
Many computers can now automatically boot from CD-ROMs. If you
have such a machine (and it is properly configured) you can boot
the &DISTRO; CD-ROM directly. After booting, the &DISTRO;
installation program will start, and you will be able to install
your system from the CD-ROM.
</para>
<para arch="x86;x86_64">
<!-- <remark os="test">(x86;x86_64)</remark> -->
The <filename>images/</filename> directory contains the file
<filename>boot.iso</filename>. This file is an ISO image that can
be used to boot the &DISTRO; installation program. It is a handy
way to start network-based installations without having to use
multiple diskettes. To use <filename>boot.iso</filename>, your
computer must be able to boot from its CD-ROM drive, and its BIOS
settings must be configured to do so. You must then burn
<filename>boot.iso</filename> onto a recordable/rewriteable
CD-ROM.
</para>
<para arch="x86;x86_64">
<!-- <remark os="test">(x86;x86_64)</remark> -->
Another image file contained in the <filename>images/</filename>
directory is <filename>diskboot.img</filename>. This file is
designed for use with USB pen drives (or other bootable media with
a capacity larger than a diskette drive). Use the
<command>dd</command> command to write the image.
</para>
<note arch="x86;x86_64">
<title>Note</title>
<!-- <remark os="test">(x86;x86_64)</remark> -->
<para>
The ability to use this image file with a USB pen drive depends
on the ability of your system's BIOS to boot from a USB device.
</para>
</note>
</section>
<section id="get-help">
<title>GETTING HELP</title>
<para>
For those that have web access, see
<ulink
url="http://fedora.redhat.com">http://fedora.redhat.com</ulink>.
In particular, access to &PROJ; mailing lists can be found at:
</para>
<para>
<ulink
url="https://listman.redhat.com/mailman/listinfo/">https://listman.redhat.com/mailman/listinfo/</ulink>
</para>
<para>
The complete &NAME; Installation Guide is available at
<ulink
url="http://fedora.redhat.com/docs/" />.
</para>
</section>
<section id="export-ctl">
<title>EXPORT CONTROL</title>
<para>
The communication or transfer of any information received with
this product may be subject to specific government export
approval. User shall adhere to all applicable laws, regulations
and rules relating to the export or re-export of technical data or
products to any proscribed country listed in such applicable laws,
regulations and rules unless properly authorized. The obligations
under this paragraph shall survive in perpetuity.
</para>
</section>
<section id="s1-test" os="test">
<title>README Feedback Procedure</title>
<para>
(This section will disappear when the final &DISTRO; release is
created.)
</para>
<para>
If you feel that this README could be improved in some way, submit
a bug report in &RH;'s bug reporting system:
</para>
<para>
<ulink
url="https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi">https://bugzilla.redhat.com/bugzilla/easy_enter_bug.cgi</ulink>
</para>
<para>
When posting your bug, include the following information in the
specified fields:
</para>
<itemizedlist>
<listitem>
<para>
<guilabel>Product:</guilabel> &DISTRO;
</para>
</listitem>
<listitem>
<para>
<guilabel>Version:</guilabel> "devel"
</para>
</listitem>
<listitem>
<para>
<guilabel>Component:</guilabel> fedora-release
</para>
</listitem>
<listitem>
<para>
<guilabel>Summary:</guilabel> A short description of what
could be improved. If it includes the word "README", so much
the better.
</para>
</listitem>
<listitem>
<para>
<guilabel>Description:</guilabel> A more in-depth description
of what could be improved.
</para>
</listitem>
</itemizedlist>
</section>
<!--
<ackno>(
<emphasis arch="x86">x86</emphasis>
<emphasis arch="x86_64">x86_64</emphasis>
)</ackno>
-->
</article>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
***** Error reading new file: [Errno 2] No such file or directory: 'RELEASE-NOTES.xml'
--- NEW FILE Security.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Security">
<title>Security</title>
<para>
This section highlights various security items from Fedora Core.
</para>
<section>
<title>General Information</title>
<para>
A general introduction to the many proactive security features in
Fedora, the current status, and policies is available at
<ulink url='http://fedoraproject.org/wiki/Security'/>.
</para>
</section>
<section>
<title>SELinux</title>
<para>
This release increases usability of SELinux by providing a
graphical troubleshooting tool, <ulink
url='http://fedoraproject.org/wiki/SELinux/setroubleshoot'>setroubleshoot</ulink>.
SELinux developer Dan Walsh explains the tool and its usage in his
<ulink
url='http://danwalsh.livejournal.com/7212.html'>blog</ulink>.
The <application>Nautilus</application> file manager has also been
improved in GNOME 2.16 to display SELinux contexts.
</para>
<para>
The SELinux project pages have troubleshooting tips,
explanations, and pointers to documentation and references.
Some useful links include the following:
</para>
<itemizedlist>
<listitem>
<para>
New SELinux project pages:
<ulink url='http://fedoraproject.org/wiki/SELinux'/>
</para>
</listitem>
<listitem>
<para>
Troubleshooting tips:
<ulink url='http://fedoraproject.org/wiki/SELinux/Troubleshooting'/>
</para>
</listitem>
<listitem>
<para>
Frequently Asked Questions:
<ulink url='http://fedora.redhat.com/docs/selinux-faq/'/>
</para>
</listitem>
<listitem>
<para>
Listing of SELinux commands:
<ulink url='http://fedoraproject.org/wiki/SELinux/Commands'/>
</para>
</listitem>
<listitem>
<para>
Details of confined domains:
<ulink url='http://fedoraproject.org/wiki/SELinux/Domains'/>
</para>
</listitem>
</itemizedlist>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE Virtualization.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Virtualization">
<title>Virtualization</title>
<para>
Virtualization in Fedora Core is based on Xen 3.0.2, and is
integrated within the Fedora Core 6 installer. Refer to
<ulink url='http://fedoraproject.org/wiki/Tools/Xen'/> for more
information about Xen.
</para>
<section>
<title>Types of Virtualization</title>
<para>
Under Fedora Core 6 using Xen 3.0.2, both paravirtualization and
full virtualization can be implemented. Full virtualization
requires a VT-capable processor. Paravirtualization does not
require special hardware, but does require the guest OS to be
modified. To learn more about how to configure and use Xen, refer
to
<ulink url='http://fedoraproject.org/wiki/FedoraXenQuickstartFC6'/>.
</para>
</section>
<section>
<title>Guest Operating Systems</title>
<para>
The Fedora Core 6 development team has tested Xen with Fedora Core
6 and Red Hat Enterprise Linux 5 Beta1 guests. Other guests have
not been tested. With paravirtualization, however, users can
expect reasonable success running any Linux guest OS that was
built for Xen 3.0.2. With full virtualization using VT hardware,
users can expect reasonable success with a larger variety of
operating systems, including some proprietary operating systems.
</para>
</section>
<section>
<title>Changes to the Xen Packages</title>
<para>
In Fedora Core 6 a single kernel supports both the host and the
guest operating systems. In previous versions, there was one
kernel, <package>kernel-xenU</package>, for the host or hypervisor
and a separate kernel, <package>kernel-xen0</package>, for the
guests. In Fedora Core 6 the <package>kernel-xen</package> package
is the only kernel needed.
</para>
<para>
Fedora Core 6 introduces <command>virt-manager</command>, a GUI
application for installing and managing virtual machines. Features
of <command>virt-manager</command> include:
</para>
<itemizedlist>
<listitem>
<para>
Integrated graphical framebuffer. Both the GUI installer and
the guest operating system's graphical environment can be
accessed from <application>virt-manager</application> without
the need for VNC.
</para>
</listitem>
<listitem>
<para>
An embedded serial console viewer. The console can now be
accessed from <application>virt-manager</application> without
opening a separate terminal and using <command>xm
console</command>.
</para>
</listitem>
<listitem>
<para>
CPU and memory management. The vCPUs and memory of active
guest operating systems can be adjusted on the fly.
</para>
</listitem>
<listitem>
<para>
Extended RFB protocol handler. If the guest operating system
changes screen resolution, the
<application>virt-manager</application> graphical console
adjusts its size accordingly.
</para>
</listitem>
</itemizedlist>
<para>
In Fedora Core 6 there are two methods to install a guest OS: via
the command line using the <command>xenguest-install</command>
program, or via the GUI application
<application>virt-manager</application>.
</para>
<itemizedlist>
<listitem override='none'>
<note>
<title>xenguest-install Script Renamed</title>
<para>
The <command>xenguest-install</command> script was named
<command>xenguest-install.py</command> in previous versions.
</para>
</note>
</listitem>
</itemizedlist>
<para>
Xen log messages are stored under <filename
class="directory">/var/log/xen</filename>, which separates Xen
related log messages from other system messages.
</para>
<itemizedlist>
<listitem override='none'>
<important>
<title>i386 Guest Kernels Require PAE</title>
<para>
PAE support in the CPU is required by i386 guests. Some
older computers might not have this functionality.
</para>
</important>
</listitem>
</itemizedlist>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE WebServers.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-WebServers">
<title>Web Servers</title>
<!--RAW HTML: <h2>Web Servers</h2>-->
<para>
Fedora Core 6 includes version 2.2 of the <application>Apache HTTP
Server</application>. Users upgrading from version 2.0 (included
in Fedora Core 4 and earlier) need to make changes to their
<command>httpd</command> configuration; refer to <ulink
url='http://httpd.apache.org/docs/2.2/upgrading.html'/> for more
details.
</para>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE Welcome.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Welcome">
<title>Welcome to Fedora Core</title>
<itemizedlist>
<listitem override='none'>
<para>
Fedora is a set of projects sponsored by Red Hat and guided by
the contributors. These projects are developed by a large
community of people who strive to provide and maintain the very
best in free, open source software and standards. Fedora Core,
the central Fedora project, is an operating system and platform
based on Linux which is always free for anyone to use, modify,
and distribute, now and forever.
</para>
</listitem>
</itemizedlist>
<para>
<tip>
<title>Latest Release Notes on the Web</title>
<para>
These release notes may be updated. Visit <ulink
url="http://fedora.redhat.com/docs/release-notes/"/> to view the
latest release notes for Fedora Core 6.
</para>
</tip>
</para>
<para>
You can help the Fedora Project community continue to improve Fedora
if you file bug reports and enhancement requests. Refer to
<ulink url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'/>
for more information about bugs. Thank you for your participation.
</para>
<para>
To find out more general information about Fedora, refer to the
following Web pages:
</para>
<itemizedlist>
<listitem>
<para>
Fedora Overview
(<ulink url='http://fedoraproject.org/wiki/Overview'/>)
</para>
</listitem>
<listitem>
<para>
Fedora FAQ (<ulink url='http://fedoraproject.org/wiki/FAQ'/>)
</para>
</listitem>
<listitem>
<para>
Help and Support
(<ulink url='http://fedoraproject.org/wiki/Communicate'/>)
</para>
</listitem>
<listitem>
<para>
Participate in the Fedora Project
(<ulink url='http://fedoraproject.org/wiki/HelpWanted'/>)
</para>
</listitem>
<listitem>
<para>
About the Fedora Project
(<ulink url='http://fedora.redhat.com/About/'/>)
</para>
</listitem>
</itemizedlist>
<para>
<note>
<title>Document Links</title>
<para>
If you are reading these release notes during the Fedora Core
installation process, many links may not work properly. The
release notes are also available post-installation as part of
the desktop Web browser's default home page. If you are
connected to the internet, use these links to find other helpful
information about Fedora and the community that creates and
supports it.
</para>
</note>
</para>
</section>
--- NEW FILE Xorg.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<section id="sn-Xorg">
<title>X Window System (Graphics)</title>
<!--RAW HTML: <h2>X Window System (Graphics)</h2>-->
<para>
This section contains information related to the X Window System
implementation provided with Fedora.
</para>
<section>
<title>X Configuration Changes</title>
<para>
The <application>X.org 7.1</application> X server has been
modified to automatically detect and configure most hardware,
eliminating the need for users or administrators to modify the
<filename>/etc/X11/xorg.conf</filename> configuration file. The
only hardware configured by default in the
<filename>xorg.conf</filename> file written by anaconda is:
</para>
<itemizedlist>
<listitem>
<para>
the graphics driver
</para>
</listitem>
<listitem>
<para>
the keyboard map
</para>
</listitem>
</itemizedlist>
<para>
All other hardware, such as monitors (both LCD and CRT), USB mice,
and touchpads should be detected and configured automatically.
</para>
<para>
The X server queries the attached monitor for supported
resolution ranges, and attempts to pick the highest resolution
available with the correct aspect ratio for the display. Users can
set their preferred resolution in <menuchoice>
<guimenu>System</guimenu>
<guisubmenu>Preferences</guisubmenu>
<guimenuitem>Screen Resolution</guimenuitem></menuchoice>,
and the default resolution for
the system can be changed with <menuchoice>
<guimenu>System</guimenu>
<guisubmenu>Administration</guisubmenu>
<guimenuitem>Display</guimenuitem></menuchoice>.
</para>
<para>
If the <filename>/etc/X11/xorg.conf</filename> configuration file
is not present, X also automatically detects the appropriate
driver, and assumes a 105-key US keyboard layout.
</para>
</section>
<section>
<title>Intel Driver notes</title>
<para>
Fedora Core 6 contains two drivers for Intel integrated graphics
controllers:
</para>
<itemizedlist>
<listitem>
<para>
The default <systemitem>i810</systemitem> driver, which
contains support for Intel graphics chipsets up to and
including i945 and i965
</para>
</listitem>
<listitem>
<para>
The experimental <systemitem>intel</systemitem> driver, which
contains support for Intel graphics chipsets up to and
including i945
</para>
</listitem>
</itemizedlist>
<para>
The <systemitem>i810</systemitem> driver is limited to resolutions
available in the BIOS. If you need support for non-standard
resolutions, such as those used in some widescreen displays, you
may want to switch to the <systemitem>intel</systemitem> driver.
You may switch drivers by using
<systemitem>system-config-display</systemitem>, available in the
menus under <menuchoice>
<guimenu>System</guimenu>
<guisubmenu>Administration</guisubmenu>
<guimenuitem>Display</guimenuitem></menuchoice>.
</para>
<para>
We welcome feedback on the experimental
<systemitem>intel</systemitem> driver. Please report success in
<ulink
url='http://bugzilla.redhat.com/bugzilla/'>Bugzilla</ulink>,
attaching the full output of <command>lspci -vn</command> for your
machine. Given success reports, various chipsets may be switched
to use the <systemitem>intel</systemitem> driver by default.
</para>
</section>
</section>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE about-fedora.omf.in ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE omf PUBLIC "-//OMF//DTD Scrollkeeper OMF Variant V1.0//EN"
"http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-…">
<omf>
<resource>
<creator>
fedora-docs-list(a)redhat.com (Fedora Documentation Project)
</creator>
<maintainer>
fedora-docs-list(a)redhat.com (Fedora Documentation Project)
</maintainer>
<title>
About Fedora
</title>
<date>
@DATE@
</date>
<version identifier="@RELEASE@" date="@DATE@" description="about-fedora-@RELEASE@"/>
<subject category="General|Linux|Distributions|Other"/>
<description>
Describes Fedora Core, the Fedora Project, and how you can help.
</description>
<type>
About
</type>
<format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.4//EN"/>
<identifier url="file:///usr/share/doc/fedora-release-notes-@RELEASE@/about/@LANGC@/about-fedora.xml"/>
<language code="@LANGC@"/>
<relation seriesid="7a5d3ea2-2a1e-11da-86a3-8ea47a4bb227"/>
<rights type="OPL" license="http://opencontent.org/openpub/" license.version="1.0"/>
</resource>
</omf>
--- NEW FILE about-fedora.xml ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" >
<article>
<title>About Fedora</title>
<articleinfo>
<authorgroup>
<corpauthor>The Fedora Project community</corpauthor>
<editor>
<firstname>Paul</firstname>
<othername>W.</othername>
<surname>Frields</surname>
</editor>
</authorgroup>
<copyright>
<year>2006</year>
<holder>Red Hat, Inc. and others</holder>
</copyright>
</articleinfo>
<para id="pa-about-fedora">
Fedora is an open, innovative, forward looking operating system and
platform, based on Linux, that is always free for anyone to use,
modify and distribute, now and forever. It is developed by a large
community of people who strive to provide and maintain the very best
in free, open source software and standards. Fedora Core is
part of the Fedora Project, sponsored by Red Hat, Inc.
</para>
<para>
Visit the Fedora community Wiki at <ulink
url="http://fedoraproject.org/wiki/"/>.
</para>
<section id="sn-about-extras">
<title>Fedora Extras</title>
<para>
The Fedora Extras project, sponsored by Red Hat and maintained by
the Fedora community, provides hundreds of high-quality software
packages to augment the software available in Fedora Core. Visit
our Web page at <ulink
url="http://fedoraproject.org/wiki/Extras"/>.
</para>
</section>
<section id="sn-about-docs">
<title>Fedora Documentation</title>
<para>
The Fedora Documentation Project provides 100% Free/Libre Open
Source Software (FLOSS) content, services, and tools for
documentation. We welcome volunteers and contributors of all
skill levels. Visit our Web page at <ulink
url="http://fedoraproject.org/wiki/DocsProject"/>.
</para>
</section>
<section id="sn-about-translation">
<title>Fedora Translation</title>
<para>
The goal of the Translation Project is to translate the software
and the documentation associated with the Fedora Project. Visit
our Web page at <ulink
url="http://fedoraproject.org/wiki/Translation"/>.
</para>
</section>
<section id="sn-about-legacy">
<title>Fedora Legacy</title>
<para>
The Fedora Legacy Project is a community-supported open source
project to extend the lifecycle of select 'maintenace mode' Red
Hat Linux and Fedora Core distributions. Fedora Legacy project is
a formal Fedora Project supported by the Fedora Foundation and
sponsored by Red Hat. Visit our Web page at <ulink
url="http://fedoraproject.org/wiki/Legacy"/>.
</para>
</section>
<section id="sn-about-triage">
<title>Fedora Bug Squad</title>
<para>
The primary mission of the Fedora Bug Squad is to track down and
clear bugs in <ulink
url="https://bugzilla.redhat.com/bugzilla">Bugzilla</ulink> that
are related to Fedora, and act as a bridge between users and
developers. Visit our Web page at <ulink
url="http://fedoraproject.org/wiki/BugZappers"/>.
</para>
</section>
<section id="sn-about-marketing">
<title>Fedora Marketing</title>
<para>
The Fedora Marketing Project is the Fedora Project's public voice.
Our goal is to promote Fedora and to help promote other Linux and
open source projects. Visit our Web page at <ulink
url="http://fedoraproject.org/wiki/Marketing"/>.
</para>
</section>
<section id="sn-about-ambassadors">
<title>Fedora Ambassadors</title>
<para>
Fedora Ambassadors are people who go to places where other Linux
users and potential converts gather and tell them about Fedora
— the project and the distribution. Visit our Web page at
<ulink url="http://fedoraproject.org/wiki/Ambassadors"/>.
</para>
</section>
<section id="sn-about-infrastructure">
<title>Fedora Infrastructure</title>
<para>
The Fedora Infrastructure Project is about helping all Fedora
contributors get their stuff done with minimum hassle and maximum
efficiency. Things under this umbrella include the Extras build
system, the <ulink
url="http://fedoraproject.org/wiki/Infrastructure/AccountSystem">Fedora
Account System</ulink>, the <ulink
url="http://cvs.fedora.redhat.com/">CVS repositories</ulink>,
the <ulink url="http://fedoraproject.org/wiki/Communicate">mailing
lists</ulink>, and the <ulink
url="http://fedoraproject.org/wiki/Websites">Websites</ulink>
infrastructure. Visit our Web site at <ulink
url="http://fedoraproject.org/wiki/Infrastructure"/>.
</para>
</section>
<section id="sn-about-websites">
<title>Fedora Websites</title>
<para>
The Fedora Websites initiative aims to improve Fedora's image on
the Internet. The key goals of this effort include:
</para>
<itemizedlist>
<listitem>
<para>
Trying to consolidate all the key Fedora websites onto one
uniform scheme
</para>
</listitem>
<listitem>
<para>
Maintaining the content that doesn't fall under any particular
sub-project
</para>
</listitem>
<listitem>
<para>
Generally, making the sites as fun and exciting as the project
they represent!
</para>
</listitem>
</itemizedlist>
<para>
Visit our Web page at <ulink
url="http://fedoraproject.org/wiki/Websites"/>.
</para>
</section>
<section id="sn-about-artwork">
<title>Fedora Artwork</title>
<para>
Making things look pretty is the name of the game... Icons,
desktop backgrounds, and themes are all parts of the Fedora
Artwork Project. Visit our Web page at <ulink
url="http://fedoraproject.org/wiki/Artwork"/>.
</para>
</section>
<section id="sn-about-planet">
<title>Fedora People</title>
<para>
You can read weblogs of many Fedora contributors at our official
aggregator, <ulink url="http://planet.fedoraproject.org/"/>.
</para>
</section>
</article>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE fedora-release-notes.omf.in ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE omf PUBLIC "-//OMF//DTD Scrollkeeper OMF Variant V1.0//EN"
"http://scrollkeeper.sourceforge.net/dtds/scrollkeeper-omf-1.0/scrollkeeper-…">
<omf>
<resource>
<creator>
fedora-docs-list(a)redhat.com (Fedora Documentation Project)
</creator>
<maintainer>
fedora-docs-list(a)redhat.com (Fedora Documentation Project)
</maintainer>
<title>
Fedora Core Release Notes
</title>
<date>
@DATE@
</date>
<version identifier="@RELEASE@" date="@DATE@"
description="fedora-release-notes-@RELEASE@"/>
<subject category="General|Linux|Distributions|Other"/>
<description>
Important information about this release of Fedora Core
</description>
<type>
About
</type>
<format mime="text/html"/>
<identifier url="file:///usr/share/doc/HTML/RELEASE-NOTES-@LANG@.html"/>
<language code="@LANGC@"/>
<relation seriesid="7a5d3ea2-2a1e-11da-86a3-8ea47a4bb227"/>
<rights type="OPL" license="http://opencontent.org/openpub/"
license.version="1.0"/>
</resource>
</omf>
--- NEW FILE homepage.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd" [
<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
%FDP-ENTITIES;
]>
<article id="browserSplash">
<sect1 id="welcome">
<title>Welcome to &FC; &FCVER;!</title>
<para>This page is where you can learn more about &FED; and the &FP;
in general. Use the resources listed here to get started with
this release, and to find solutions to common problems you might
encounter.</para>
<note>
<para>Documents that are not stored on your system and require a
connection to the Internet are marked with the following icon:
<ulink url=""><phrase role="external"> </phrase></ulink></para>
</note>
<para>This page is available in <ulink
url="index-pt_BR.html">Brazilian Portuguese</ulink>,
<ulink url="index-el.html">Greek</ulink>, <ulink
url="index-it.html">Italian</ulink>, <ulink
url="index-pl.html">Polish</ulink>, <ulink
url="index-pt.html">Portuguese</ulink>, <ulink
url="index-ru.html">Russian</ulink>, <ulink
url="index-zh_CN.html">Simplified Chinese</ulink>,
<ulink url="index-es.html">Spanish</ulink>, <ulink
url="index-sv.html">Swedish</ulink>, and <ulink
url="index-en_US.html">US English</ulink>.</para>
<sect2 id="fedora-docs">
<title>&FED; Documentation</title>
<sect3 id="release-notes">
<title>
<ulink url="RELEASE-NOTES-en_US.html">&FC; &FCVER; Release
Notes</ulink>
</title>
<para>The Release Notes provide a detailed overview of this
release of &FC;, including what's new, notes specific to your
computer architecture, and tips for smoother system operation.
This document is highly recommended for every installation or
upgrade of your &FED; system.</para>
<!-- We'll use the following para if we can't get the XSLT and CSS -->
<!-- working against DocBook XML. If we can figure out some XSLT to -->
<!-- apply to this after it's turned into XHTML, then we can simply have -->
<!-- this work like everything else. The CSS, though, needs to turn -->
<!-- this into two columns, and right now DocBook stylesheets have no -->
<!-- way of applying an @id or @role properly into an XHTML @CLASS -->
<!-- attribute (or something else suitable for telling one column from -->
<!-- another). If someone writes an XSLT stylesheet to apply a @CLASS -->
<!-- attribute value to the XHTML <div>s that come out of the <sect2>s -->
<!-- in this document, the CSS can be applied and we're in business. -->
<!-- If not, we'll simply uncomment this paragraph (since we'll only be -->
<!-- delivering it in en_US in that case) and list the translations that -->
<!-- have been made available through the PO. -->
<para>The Release Notes are available in <ulink
url="RELEASE-NOTES-pt_BR.html">Brazilian Portuguese</ulink>,
<ulink url="RELEASE-NOTES-el.html">Greek</ulink>, <ulink
url="RELEASE-NOTES-it.html">Italian</ulink>, <ulink
url="RELEASE-NOTES-pl.html">Polish</ulink>, <ulink
url="RELEASE-NOTES-pt.html">Portuguese</ulink>, <ulink
url="RELEASE-NOTES-ru.html">Russian</ulink>, <ulink
url="RELEASE-NOTES-zh_CN.html">Simplified Chinese</ulink>,
<ulink url="RELEASE-NOTES-es.html">Spanish</ulink>, <ulink
url="RELEASE-NOTES-sv.html">Swedish</ulink>, and <ulink
url="RELEASE-NOTES-en_US.html">US English</ulink>.</para>
</sect3>
<sect3>
<title>&IG;</title>
<para>The <ulink
url="http://fedora.redhat.com/docs/install-guide/"><phrase
role="external">&IG;</phrase></ulink> helps you install
&FC; on desktops, laptops and servers.</para>
</sect3>
<sect3 id="desktop-user-guide">
<title>&FED; Desktop User Guide</title>
<para>The Desktop User Guide explains how to accomplish specific
tasks using desktop applications. It covers activities such
as using the desktop, accessing media, communicating on the
Internet, using office productivity applications, and playing
multimedia and games.</para>
<para>The Desktop User Guide is currently available as a
<emphasis>draft</emphasis> in <ulink
url="http://fedoraproject.org/wiki/Docs/Drafts/DesktopUserGuide"><phrase
role="external">US English</phrase></ulink>.</para>
</sect3>
</sect2>
<sect2 id="other-resources">
<title>Other Resources</title>
<sect3>
<title>&FP;</title>
<para>The &FP; website contains a wealth of information. Here
are some pages of interest:</para>
<itemizedlist>
<listitem>
<para><ulink
url="http://fedoraproject.org/wiki/Overview"><phrase
role="external">Overview of &FED;</phrase></ulink>:
What &FED; is, and what makes it special</para>
</listitem>
<listitem>
<para><ulink url="http://fedoraproject.org/wiki/FAQ"><phrase
role="external">&FED; FAQ</phrase></ulink>: Frequently
asked questions about &FED; and their answers</para>
</listitem>
<listitem>
<para><ulink
url="http://fedoraproject.org/wiki/Communicate"><phrase
role="external">Communicate</phrase></ulink>: Ways to
interact with a strong, global community of users and
contributors that is ready to help you and listen to your
feedback</para>
</listitem>
<listitem>
<para><ulink
url="http://fedoraproject.org/wiki/HelpWanted"><phrase
role="external">Participate</phrase></ulink>: Ways you
can make a change by helping with &FED;</para>
</listitem>
<listitem>
<para><ulink url="http://fedoraproject.org/people/"><phrase
role="external">Planet &FED;</phrase></ulink>: Read
what &FP; contributors around the planet have to
say</para>
</listitem>
</itemizedlist>
</sect3>
<sect3>
<title>Community Websites</title>
<note>
<para>The documentation provided in these sites is provided
<emphasis>as is</emphasis>, and neither &RH; nor the &FP;
have any control over their content.</para>
</note>
<itemizedlist>
<listitem>
<para><ulink url="http://fedoranews.org"><phrase
role="external">&FED; News</phrase></ulink>: A public
community news and information site for &FED; users</para>
</listitem>
<listitem>
<para><ulink url="http://fedoraforum.org"><phrase
role="external">Fedora Forum</phrase></ulink>: The
formally endorsed forums of the &FP;</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.fedorafaq.org/"><phrase
role="external">The unofficial &FED; FAQ</phrase>
</ulink>
</para>
</listitem>
</itemizedlist>
</sect3>
</sect2>
</sect1>
</article>
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
--- NEW FILE rpm-info.xml ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE rpm-info SYSTEM "../../../docs-common/packaging/rpm-info.dtd">
<rpm-info>
<colophon>
<worker id="fdp" wholename="Fedora Documentation Project" email="fedora-docs-list(a)redhat.com" surname="Project" firstname="Fedora Documentation" initials="fdp"/>
<worker id="quaid" wholename="Karsten Wade" email="kwade(a)redhat.com" surname="Wade" firstname="Karsten" initials="quaid"/>
<worker email="Tommy.Reynolds(a)MegaCoder.com" firstname="Tommy" id="megacoder" initials="JTR" surname="Reynolds" wholename="Tommy Reynolds"/>
<worker id="PaulWFrields" wholename="Paul W. Frields" email="stickster(a)gmail.com" surname="Frields" firstname="Paul" othername="W." initials="PWF"/>
</colophon>
<author worker="fdp"/>
<license>
<rights>OPL</rights>
<version>1.0</version>
</license>
<copyright>
<year>2006</year>
<holder>Red Hat, Inc. and others</holder>
</copyright>
<title>Fedora Core Release Notes</title>
<desc>Important information about this release of Fedora Core</desc>
<changelog order="newest-first">
<revision date="2006-09-24" number="6.0.0">
<author worker="PaulWFrields"/>
<details>Push new version for final</details>
</revision>
<revision date="2006-09-05" number="5.92" role="doc">
<author worker="PaulWFrields"/>
<details>Push new version for test3</details>
</revision>
<revision date="2006-08-13" number="5.91.2" role="doc">
<author worker="PaulWFrields"/>
<details>Prepare new wiki snapshot for Web release</details>
</revision>
<revision date="2006-08-10" number="5.91.1" role="doc">
<author worker="PaulWFrields"/>
<details>Fix copyright holder information</details>
</revision>
<revision date="2006-07-13" number="5.91" role="doc">
<author worker="PaulWFrields"/>
<details>Bring version number into line with reality</details>
</revision>
<revision date="2006-07-11" number="0.5.9.1" role="doc">
<author worker="PaulWFrields"/>
<details>FC6 test2 rollout for translation</details>
</revision>
</changelog>
</rpm-info>
1
0
release-notes/FC-5/po RELEASE-NOTES.pot,1.1,1.2 pt.po,1.9,1.10
by fedora-docs-commits＠redhat.com 28 Oct '06
by fedora-docs-commits＠redhat.com 28 Oct '06
28 Oct '06
Author: pfrields
Update of /cvs/docs/release-notes/FC-5/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6395/FC-5/po
Modified Files:
RELEASE-NOTES.pot pt.po
Log Message:
Add FC-6 branch. This branch should be used for errata updates, not devel -- although syncing them is fine.
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.1 -r 1.2 RELEASE-NOTES.pot
Index: RELEASE-NOTES.pot
===================================================================
RCS file: /cvs/docs/release-notes/FC-5/po/RELEASE-NOTES.pot,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- RELEASE-NOTES.pot 27 Jun 2006 21:26:45 -0000 1.1
+++ RELEASE-NOTES.pot 28 Oct 2006 22:21:33 -0000 1.2
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-02-22 05:54-0600\n"
+"POT-Creation-Date: 2006-10-14 10:59-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL(a)li.org>\n"
@@ -9,2251 +9,3097 @@
"Content-Type: text/plain; charset=UTF-8\n"
"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/ArchSpecificx86_64.xml:5(title) en/ArchSpecificPPC.xml:5(title) en/ArchSpecific.xml:5(title)
+#: en_US/rpm-info.xml:21(rights)
+msgid "OPL"
+msgstr ""
+
+#: en_US/rpm-info.xml:22(version)
+msgid "1.0"
+msgstr ""
+
+#: en_US/rpm-info.xml:25(year)
+msgid "2006"
+msgstr ""
+
+#: en_US/rpm-info.xml:26(holder)
+msgid "Red Hat, Inc. and others"
+msgstr ""
+
+#: en_US/rpm-info.xml:30(title)
+msgid "Fedora Core 5 Release Notes"
+msgstr ""
+
+#: en_US/rpm-info.xml:31(desc)
+msgid "Important information about this release of Fedora Core"
+msgstr ""
+
+#: en_US/rpm-info.xml:35(title)
+msgid "Fedora Core 5 ������������"
+msgstr ""
+
+#: en_US/rpm-info.xml:39(title)
+msgid "Note di rilascio per Fedora Core 5"
+msgstr ""
+
+#: en_US/rpm-info.xml:43(title)
+msgid "Fedora Core 5 ������������������ �� ��������������"
+msgstr ""
+
+#: en_US/rpm-info.xml:47(title)
+msgid "Fedora Core 5 ���������������������"
+msgstr ""
+
+#: en_US/rpm-info.xml:54(details)
+msgid "Refer to IG and fix repodata instructions (#186904)"
+msgstr ""
+
+#: en_US/rpm-info.xml:59(details)
+msgid "Errata release notes for FC5 release."
+msgstr ""
+
+#: en_US/rpm-info.xml:63(details)
+msgid "Finished port of wiki for FC5 release."
+msgstr ""
+
+#: en_US/Xorg.xml:7(title) en_US/Welcome.xml:7(title) en_US/WebServers.xml:7(title) en_US/Virtualization.xml:7(title) en_US/SystemDaemons.xml:7(title) en_US/ServerTools.xml:7(title) en_US/SecuritySELinux.xml:7(title) en_US/Security.xml:7(title) en_US/Samba.xml:7(title) en_US/ProjectOverview.xml:7(title) en_US/Printing.xml:7(title) en_US/PackageNotes.xml:7(title) en_US/PackageChanges.xml:7(title) en_US/OverView.xml:7(title) en_US/Networking.xml:7(title) en_US/Multimedia.xml:7(title) en_US/Legacy.xml:7(title) en_US/Kernel.xml:7(title) en_US/Java.xml:7(title) en_US/Installer.xml:7(title) en_US/I18n.xml:7(title) en_US/FileSystems.xml:7(title) en_US/FileServers.xml:7(title) en_US/Feedback.xml:7(title) en_US/Entertainment.xml:7(title) en_US/Extras.xml:7(title) en_US/DevelToolsGCC.xml:7(title) en_US/DevelTools.xml:7(title) en_US/Desktop.xml:7(title) en_US/DatabaseServers.xml:7(title) en_US/Colophon.xml:7(title) en_US/BackwardsCompatibility.xml:7(title) en_US/ArchSpecificx86.xml:7(!
title) en_US/ArchSpecificx86_64.xml:7(title) en_US/ArchSpecificPPC.xml:7(title) en_US/ArchSpecific.xml:7(title)
msgid "Temp"
msgstr ""
-#: en/Xorg.xml:8(title)
+#: en_US/Xorg.xml:11(title)
msgid "X Window System (Graphics)"
msgstr ""
-#: en/Xorg.xml:9(para)
+#: en_US/Xorg.xml:13(para)
msgid "This section contains information related to the X Window System implementation provided with Fedora."
msgstr ""
-#: en/Xorg.xml:11(title)
+#: en_US/Xorg.xml:19(title)
msgid "xorg-x11"
msgstr ""
-#: 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."
+#: en_US/Xorg.xml:21(para)
+msgid "X.org X11 is an open source implementation of the X Window System. It provides the basic low-level functionality upon which full-fledged graphical user interfaces (GUIs) such as GNOME and KDE are designed. For more information about X.org, refer to <ulink url=\"http://xorg.freedesktop.org/wiki/\">http://xorg.freedesktop.org/wiki/</ulink>."
msgstr ""
-#: en/Xorg.xml:13(para)
-msgid "For more information about Xorg refer to <ulink url=\"http://xorg.freedesktop.org/wiki/\">http://xorg.freedesktop.org/wiki/</ulink>"
+#: en_US/Xorg.xml:29(para)
+msgid "You may use <emphasis>System > Administration > Display</emphasis> or <emphasis role=\"strong\">system-config-display</emphasis> to configure the settings. The configuration file for X.org is located in <code>/etc/X11/xorg.conf</code>."
msgstr ""
-#: 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"
+#: en_US/Xorg.xml:36(para)
+msgid "X.org X11R7 is the first modular release of X.org, which, among several other benefits, promotes faster updates and helps programmers rapidly develop and release specific components. More information on the current status of the X.org modularization effort in Fedora is available at <ulink url=\"http://fedoraproject.org/wiki/Xorg/Modularization\">http://fedoraproject.org/wiki/Xorg/Modularization</ulink>."
msgstr ""
-#: 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."
+#: en_US/Xorg.xml:47(title)
+msgid "X.org X11R7 End-User Notes"
msgstr ""
-#: en/Xorg.xml:17(para)
-msgid "More information on the current status of the Xorg modularization effort in Fedora is available from <ulink url=\"/Xorg/Modularization\">http://fedoraproject.org/wiki/Xorg/Modularization</ulink>"
+#: en_US/Xorg.xml:50(title)
+msgid "Installing Third Party Drivers"
msgstr ""
-#: en/Xorg.xml:21(title)
-msgid "Xorg X11R7.0 Developer Notes"
+#: en_US/Xorg.xml:51(para)
+msgid "Before you install any third party drivers from any vendor, including ATI or nVidia, please read <ulink url=\"http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers\">http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers</ulink>."
msgstr ""
-#: 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 X11<emphasis role=\"strong\"/>R7. 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."
+#: en_US/Xorg.xml:58(para)
+msgid "The <code>xorg-x11-server-Xorg</code> package install scripts automatically remove the <code>RgbPath</code> line from the <code>xorg.conf</code> file if it is present. You may need to reconfigure your keyboard differently from what you are used to. You are encouraged to subscribe to the upstream <ulink url=\"mailto:xorg@freedesktop.org\">xorg(a)freedesktop.org</ulink> mailing list if you do need assistance reconfiguring your keyboard."
msgstr ""
-#: en/Xorg.xml:24(title)
-msgid "The /usr/X11R6 Directory Hierarchy"
+#: en_US/Xorg.xml:70(title)
+msgid "X.org X11R7 Developer Overview"
msgstr ""
-#: en/Xorg.xml:25(para)
-msgid "X11<emphasis role=\"strong\"/>R7 install into /usr directly now, and no longer uses the /usr/X11<emphasis role=\"strong\"/>R6 hierarchy. Applications which rely on files being present at fixed paths under /usr/X11<emphasis role=\"strong\"/>R6 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."
+#: en_US/Xorg.xml:72(para)
+msgid "The following list includes some of the more visible changes for developers in X11R7:"
msgstr ""
-#: en/Xorg.xml:28(title)
+#: en_US/Xorg.xml:79(para)
+msgid "The entire buildsystem has changed from <code>imake</code> to the GNU <code>autotools</code> collection."
+msgstr ""
+
+#: en_US/Xorg.xml:85(para)
+msgid "Libraries now install <code>pkgconfig</code><code>*.pc</code> files, which should now always be used by software that depends on these libraries, instead of hard coding paths to them in <code>/usr/X11R6/lib </code> or elsewhere."
+msgstr ""
+
+#: en_US/Xorg.xml:93(para)
+msgid "Everything is now installed directly into <code>/usr</code> instead of <code>/usr/X11R6</code>. All software that hard codes paths to anything in <code>/usr/X11R6</code> must now be changed, preferably to dynamically detect the proper location of the object. Developers are <emphasis role=\"strong\">strongly</emphasis> advised against hard-coding the new X11R7 default paths."
+msgstr ""
+
+#: en_US/Xorg.xml:103(para)
+msgid "Every library has its own private source RPM package, which creates a runtime binary subpackage and a <code>-devel</code> subpackage."
+msgstr ""
+
+#: en_US/Xorg.xml:112(title)
+msgid "X.org X11R7 Developer Notes"
+msgstr ""
+
+#: en_US/Xorg.xml:114(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 ""
+
+#: en_US/Xorg.xml:120(title)
+msgid "The /usr/X11R6/ Directory Hierarchy"
+msgstr ""
+
+#: en_US/Xorg.xml:122(para)
+msgid "X11R7 files install into <code>/usr</code> directly now, and no longer use the <code>/usr/X11R6/</code> hierarchy. Applications that rely on files being present at fixed paths under <code>/usr/X11R6/</code>, either at compile time or run time, must be updated. They should now use the system <code>PATH</code>, or some other mechanism to dynamically determine where the files reside, or alternatively to hard code the new locations, possibly with fallbacks."
+msgstr ""
+
+#: en_US/Xorg.xml:134(title)
msgid "Imake"
msgstr ""
-#: 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 X11<emphasis role=\"strong\"/>R7, 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."
+#: en_US/Xorg.xml:136(para)
+msgid "The <code>imake</code> xutility is no longer used to build the X Window System, and is now officially deprecated. X11R7 includes <code>imake</code>, <code>xmkmf</code>, and other build utilities previously supplied by the X Window System. X.Org highly recommends, however, that people migrate from <code>imake</code> to use GNU <code>autotools</code> and <code>pkg-config</code>. Support for <code>imake</code> may be removed in a future X Window System release, so developers are <emphasis role=\"strong\">strongly</emphasis> encouraged to transition away from it, and not use it for any new software projects."
+msgstr ""
+
+#: en_US/Xorg.xml:151(title)
+msgid "The Systemwide app-defaults/ Directory"
+msgstr ""
+
+#: en_US/Xorg.xml:153(para)
+msgid "The system <code>app-defaults/</code> directory for X resources is now <code>%{_datadir}/X11/app-defaults</code>, which expands to <code>/usr/share/X11/app-defaults/</code> on Fedora Core and for future Red Hat Enterprise Linux systems."
+msgstr ""
+
+#: en_US/Xorg.xml:162(title)
+msgid "Correct Package Dependencies"
[...3805 lines suppressed...]
+#: en_US/ArchSpecificx86_64.xml:107(para)
+msgid "To list all packages with their architecture using <code>rpm</code>, run the following command:"
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/ArchSpecificPPC.xml:45(None)
-msgid "@@image: '/wiki/ntheme/img/alert.png'; md5=THIS FILE DOESN'T EXIST"
+#: en_US/ArchSpecificx86_64.xml:111(screen)
+#, no-wrap
+msgid "\nrpm -qa --queryformat \"%{name}-%{version}-%{release}.%{arch}\\n\"\n"
+msgstr ""
+
+#: en_US/ArchSpecificx86_64.xml:115(para)
+msgid "You can add this to <code>/etc/rpm/macros</code> (for a system wide setting) or <code>~/.rpmmacros</code> (for a per-user setting). It changes the default query to list the architecture:"
+msgstr ""
+
+#: en_US/ArchSpecificx86_64.xml:120(screen)
+#, no-wrap
+msgid "\n%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}\n"
msgstr ""
-#: en/ArchSpecificPPC.xml:8(title)
+#: en_US/ArchSpecificPPC.xml:11(title)
msgid "PPC Specifics for Fedora"
msgstr ""
-#: en/ArchSpecificPPC.xml:9(para)
+#: en_US/ArchSpecificPPC.xml:13(para)
msgid "This section covers any specific information you may need to know about Fedora Core and the PPC hardware platform."
msgstr ""
-#: en/ArchSpecificPPC.xml:11(title)
+#: en_US/ArchSpecificPPC.xml:19(title)
msgid "PPC Hardware Requirements"
msgstr ""
-#: en/ArchSpecificPPC.xml:12(para)
-msgid "This section lists the minimum PowerPC (PPC) hardware needed to install Fedora Core 4."
+#: en_US/ArchSpecificPPC.xml:22(title)
+msgid "Processor and Memory"
msgstr ""
-#: en/ArchSpecificPPC.xml:15(para)
-msgid "Minimum: PowerPC G3 / POWER4"
+#: en_US/ArchSpecificPPC.xml:26(para)
+msgid "Minimum CPU: PowerPC G3 / POWER4"
msgstr ""
-#: en/ArchSpecificPPC.xml:18(para)
-msgid "Fedora Core 5 supports only the ���New World��� generation of Apple Power Macintosh, shipped circa 1999 onwards."
+#: en_US/ArchSpecificPPC.xml:31(para)
+msgid "Fedora Core 5 supports only the ���New World��� generation of Apple Power Macintosh, shipped from circa 1999 onward."
msgstr ""
-#: 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."
+#: en_US/ArchSpecificPPC.xml:37(para)
+msgid "Fedora Core 5 also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines."
msgstr ""
-#: en/ArchSpecificPPC.xml:24(para)
-msgid "Recommended for text-mode: 233 MHz G3 or better, 64MiB RAM."
+#: en_US/ArchSpecificPPC.xml:44(para)
+msgid "Recommended for text-mode: 233 MHz G3 or better, 128MiB RAM."
msgstr ""
-#: en/ArchSpecificPPC.xml:27(para)
-msgid "Recommended for graphical: 400 MHz G3 or better, 128MiB RAM."
+#: en_US/ArchSpecificPPC.xml:50(para)
+msgid "Recommended for graphical: 400 MHz G3 or better, 256MiB RAM."
msgstr ""
-#: en/ArchSpecificPPC.xml:39(title)
-msgid "PPC Installation Notes"
+#: en_US/ArchSpecificPPC.xml:60(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 <code>/Fedora/base/stage2.img</code> (on Installtion Disc 1) plus the size of the files in <code>/var/lib/rpm</code> on the installed system."
msgstr ""
-#: en/ArchSpecificPPC.xml:48(phrase)
-msgid "/!\\"
+#: en_US/ArchSpecificPPC.xml:89(title)
+msgid "The Apple keyboard"
msgstr ""
-#: en/ArchSpecificPPC.xml:42(para)
-msgid "<inlinemediaobject><placeholder-1/><placeholder-2/></inlinemediaobject> Currently FC5 Test Release CD 1 and Rescue ISOs do not boot on Mac hardware. See below on booting using boot.iso."
+#: en_US/ArchSpecificPPC.xml:91(para)
+msgid "The <code>Option</code> key on Apple systems is equivalent to the <code>Alt</code> key on the PC. Where documentation and the installer refer to the <code>Alt</code> key, use the <code>Option</code> key. For some key combinations you may need to use the <code>Option</code> key in conjunction with the <code>Fn</code> key, such as <code>Option</code> - <code>Fn</code> - <code>F3</code> to switch to virtual terminal tty3."
msgstr ""
-#: 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:"
+#: en_US/ArchSpecificPPC.xml:103(title)
+msgid "PPC Installation Notes"
+msgstr ""
+
+#: en_US/ArchSpecificPPC.xml:105(para)
+msgid "Fedora Core Installation Disc 1 is bootable on supported hardware. In addition, a bootable CD image appears in the <code>images/</code> directory of this disc. These images will behave differently according to your system hardware:"
msgstr ""
-#: en/ArchSpecificPPC.xml:58(para)
+#: en_US/ArchSpecificPPC.xml:115(para)
msgid "Apple Macintosh"
msgstr ""
-#: 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."
+#: en_US/ArchSpecificPPC.xml:118(para)
+msgid "The bootloader should automatically boot the appropriate 32-bit or 64-bit installer."
+msgstr ""
+
+#: en_US/ArchSpecificPPC.xml:122(para)
+msgid "The default <code>gnome-power-manager</code> package includes power management support, including sleep and backlight level management. Users with more complex requirements can use the <code>apmud</code> package in Fedora Extras. Following installation, you can install <code>apmud</code> with the following command:"
+msgstr ""
+
+#: en_US/ArchSpecificPPC.xml:136(screen)
+#, no-wrap
+msgid "su -c 'yum install apmud'"
msgstr ""
-#: en/ArchSpecificPPC.xml:66(para)
+#: en_US/ArchSpecificPPC.xml:141(para)
msgid "64-bit IBM eServer pSeries (POWER4/POWER5)"
msgstr ""
-#: en/ArchSpecificPPC.xml:69(para)
+#: en_US/ArchSpecificPPC.xml:144(para)
msgid "After using Open<emphasis role=\"strong\"/>Firmware to boot the CD, the bootloader (yaboot) should automatically boot the 64-bit installer."
msgstr ""
-#: en/ArchSpecificPPC.xml:74(para)
+#: en_US/ArchSpecificPPC.xml:151(para)
msgid "32-bit CHRP (IBM RS/6000 and others)"
msgstr ""
-#: en/ArchSpecificPPC.xml:77(para)
-msgid "After using Open<emphasis role=\"strong\"/>Firmware 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_US/ArchSpecificPPC.xml:154(para)
+msgid "After using Open<emphasis role=\"strong\"/>Firmware to boot the CD, select the <code>linux32</code> boot image at the <code>boot:</code> prompt to start the 32-bit installer. Otherwise, the 64-bit installer starts, which does not work."
msgstr ""
-#: en/ArchSpecificPPC.xml:82(para)
+#: en_US/ArchSpecificPPC.xml:165(para)
msgid "Genesi Pegasos II"
msgstr ""
-#: 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 Open<emphasis role=\"strong\"/>Firmware prompt, enter the command:"
+#: en_US/ArchSpecificPPC.xml:168(para)
+msgid "At the time of writing, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, you can use the network boot image. At the Open<emphasis role=\"strong\"/>Firmware prompt, enter the command:"
msgstr ""
-#: en/ArchSpecificPPC.xml:88(screen)
+#: en_US/ArchSpecificPPC.xml:177(screen)
#, no-wrap
-msgid "boot cd: /images/netboot/ppc32.img "
+msgid "boot cd: /images/netboot/ppc32.img"
msgstr ""
-#: en/ArchSpecificPPC.xml:91(para)
-msgid "You also need to configure Open<emphasis role=\"strong\"/>Firmware 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_US/ArchSpecificPPC.xml:180(para)
+msgid "You must also configure Open<emphasis role=\"strong\"/>Firmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, set the <code>boot-device</code> and <code>boot-file</code> environment variables appropriately."
msgstr ""
-#: en/ArchSpecificPPC.xml:96(para)
+#: en_US/ArchSpecificPPC.xml:192(para)
msgid "Network booting"
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."
+#: en_US/ArchSpecificPPC.xml:195(para)
+msgid "You can find combined images containing the installer kernel and ramdisk in the <code>images/netboot/</code> directory of the installation tree. These are intended for network booting with TFTP, but can be used in many ways."
msgstr ""
-#: 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_US/ArchSpecificPPC.xml:202(para)
+msgid "<code>yaboot</code> supports TFTP booting for IBM eServer pSeries and Apple Macintosh. The Fedora Project encourages the use of <code>yaboot</code> over the <code>netboot</code> images."
msgstr ""
-#: en/ArchSpecific.xml:8(title)
-msgid "Archictecture Specific"
+#: en_US/ArchSpecific.xml:10(title)
+msgid "Architecture Specific Notes"
msgstr ""
-#: en/ArchSpecific.xml:9(para)
+#: en_US/ArchSpecific.xml:11(para)
msgid "This section provides notes that are specific to the supported hardware architectures of Fedora Core."
msgstr ""
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: en/ArchSpecific.xml:0(None)
+#: en_US/ArchSpecific.xml:0(None)
msgid "translator-credits"
msgstr ""
Index: pt.po
===================================================================
RCS file: /cvs/docs/release-notes/FC-5/po/pt.po,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- pt.po 25 Sep 2006 17:43:11 -0000 1.9
+++ pt.po 28 Oct 2006 22:21:33 -0000 1.10
@@ -2,7 +2,7 @@
msgstr ""
"Project-Id-Version: release-notes\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2006-09-07 10:47+0100\n"
+"POT-Creation-Date: 2006-10-14 10:59-0400\n"
"PO-Revision-Date: 2006-09-07 10:49+0100\n"
"Last-Translator: Jos�� Nuno Coelho Pires <jncp(a)netcabo.pt>\n"
"Language-Team: pt <kde-i18n-pt(a)kde.org>\n"
@@ -980,9 +980,8 @@
msgstr "/!\\"
#: en_US/SystemDaemons.xml:16(para) en_US/Printing.xml:16(para)
-msgid ""
-"<inlinemediaobject><placeholder-1/><placeholder-2/></inlinemediaobject> "
-"REMOVE ME Before Publishing - Beat Comment"
+#, fuzzy
+msgid "<placeholder-1/> REMOVE ME Before Publishing - Beat Comment"
msgstr ""
"<inlinemediaobject><placeholder-1/><placeholder-2/></inlinemediaobject> "
"REMOVA-ME Antes da Publica����o - Coment��rio da ��rea"
@@ -1659,7 +1658,10 @@
"In order to talk on the <code>#fedora</code> channel, you will need to "
"register your nickname, or <emphasis>nick</emphasis>. Instructions are given "
"when you <code>/join</code> the channel."
-msgstr "Para poder falar no canal <code>#fedora</code>, ter�� de registar o seu nome de utilizador ou <emphasis>alcunha</emphasis>. As instru����es ser��o dadas quando voc�� fizer <code>/join</code> (ligar) ao canal."
+msgstr ""
+"Para poder falar no canal <code>#fedora</code>, ter�� de registar o seu nome "
+"de utilizador ou <emphasis>alcunha</emphasis>. As instru����es ser��o dadas "
+"quando voc�� fizer <code>/join</code> (ligar) ao canal."
#: en_US/ProjectOverview.xml:132(title)
msgid "IRC Channels"
@@ -5467,7 +5469,10 @@
"Kdump kernel for use with kexec/kdump capabilities. Configured sources are "
"available in the <code>kernel-kdump-devel-<version>.<arch>.rpm</"
"code> package."
-msgstr "O 'kernel' do 'kdump' para usar com as capacidades do 'kexec'/'kdump'. As fontes configuradas est��o dispon��veis no pacote <code>kernel-kdump-devel-<vers��o>.<arquitectura>.rpm</code>."
+msgstr ""
+"O 'kernel' do 'kdump' para usar com as capacidades do 'kexec'/'kdump'. As "
+"fontes configuradas est��o dispon��veis no pacote <code>kernel-kdump-devel-<"
+"vers��o>.<arquitectura>.rpm</code>."
#: en_US/Kernel.xml:113(para)
msgid ""
@@ -5586,7 +5591,13 @@
"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 dos tutoriais, exemplos e manuais de texto sobre o desenvolvimento para o 'kernel' do Linux assumem que o c��digo do 'kernel' est�� instalado na pasta <code>/usr/src/linux/</code>. Se criar uma liga����o simb��lica, como aparece abaixo, poder�� usar este material de aprendizagem com os pacotes do Fedora Core. Instale o c��digo apropriado do 'kernel', como aparece acima, e depois:"
+msgstr ""
+"Muitos dos tutoriais, exemplos e manuais de texto sobre o desenvolvimento "
+"para o 'kernel' do Linux assumem que o c��digo do 'kernel' est�� instalado na "
+"pasta <code>/usr/src/linux/</code>. Se criar uma liga����o simb��lica, como "
+"aparece abaixo, poder�� usar este material de aprendizagem com os pacotes do "
+"Fedora Core. Instale o c��digo apropriado do 'kernel', como aparece acima, e "
+"depois:"
#: en_US/Kernel.xml:195(screen)
#, no-wrap
@@ -5640,7 +5651,11 @@
"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 "Os utilizadores que necessitem de acesso ao c��digo-fonte original do Fedora Core, pod��-lo-��o encontrar no pacote '.src.rpm' do 'kernel'. Para criar uma ��rvore de c��digo expandida a partir deste ficheiro, execute os seguintes passos:"
+msgstr ""
+"Os utilizadores que necessitem de acesso ao c��digo-fonte original do Fedora "
+"Core, pod��-lo-��o encontrar no pacote '.src.rpm' do 'kernel'. Para criar uma "
+"��rvore de c��digo expandida a partir deste ficheiro, execute os seguintes "
+"passos:"
#: en_US/Kernel.xml:231(title)
msgid "Do Not Build Packages as Super-user (root)"
@@ -5814,7 +5829,16 @@
"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 <code>Makefile</code>."
-msgstr "Todos os 'kernels' ficam com um nome baseado no seu n��mero de vers��o. Este �� o valor que o comando <code>uname -r</code> mostra. O nome do 'kernel' �� definido pelas primeiras quatro linhas da <code>Makefile</code> do 'kernel'. Para proteger os inocentes, a <code>Makefile</code> foi alterada para gerar um 'kernel' com um nome <emphasis>diferente</emphasis> do 'kernel' actualmente em execu����o. Antes de um m��dulo poder ser aceite no 'kernel' em execu����o, esse m��dulo precisa ser compilado para um 'kernel' com o nome correcto. Para fazer isto, precisa de editar a <code>Makefile</code> do 'kernel'."
+msgstr ""
+"Todos os 'kernels' ficam com um nome baseado no seu n��mero de vers��o. Este �� "
+"o valor que o comando <code>uname -r</code> mostra. O nome do 'kernel' �� "
+"definido pelas primeiras quatro linhas da <code>Makefile</code> do 'kernel'. "
+"Para proteger os inocentes, a <code>Makefile</code> foi alterada para gerar "
+"um 'kernel' com um nome <emphasis>diferente</emphasis> do 'kernel' "
+"actualmente em execu����o. Antes de um m��dulo poder ser aceite no 'kernel' em "
+"execu����o, esse m��dulo precisa ser compilado para um 'kernel' com o nome "
+"correcto. Para fazer isto, precisa de editar a <code>Makefile</code> do "
+"'kernel'."
#: en_US/Kernel.xml:352(para)
msgid ""
@@ -6209,7 +6233,15 @@
"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 <code>linux mediacheck</code> at the <code>boot:</code> prompt."
-msgstr "O <emphasis role=\"strong\">Anaconda</emphasis> tem a capacidade de testar a integridade dos discos de instala����o. Funciona com os m��todos de instala����o a partir do CD, DVD, ISO no disco r��gido e do ISO por NFS. O Projecto Fedora recomenda que voc�� teste todos os discos de instala����o antes de iniciar o processo de instala����o, e antes de comunicar quaisquer problemas relacionados com a instala����o (muitos dos erros comunicados s��o derivados de facto de CDs gravados de forma errada). Para usar este teste, escreva <code>linux mediacheck</code> na linha de comando <code>boot:</code>."
+msgstr ""
+"O <emphasis role=\"strong\">Anaconda</emphasis> tem a capacidade de testar a "
+"integridade dos discos de instala����o. Funciona com os m��todos de instala����o "
+"a partir do CD, DVD, ISO no disco r��gido e do ISO por NFS. O Projecto Fedora "
+"recomenda que voc�� teste todos os discos de instala����o antes de iniciar o "
+"processo de instala����o, e antes de comunicar quaisquer problemas "
+"relacionados com a instala����o (muitos dos erros comunicados s��o derivados de "
+"facto de CDs gravados de forma errada). Para usar este teste, escreva "
+"<code>linux mediacheck</code> na linha de comando <code>boot:</code>."
#: en_US/Installer.xml:54(para)
msgid ""
@@ -7118,7 +7150,12 @@
"<emphasis>Applications > Add/Remove Software</emphasis>. Enter the "
"<code>root</code> password when prompted. Select the software you require "
"from the list, and choose <emphasis>Apply</emphasis>."
-msgstr "Para instalar o 'software' tanto dos reposit��rios Core ou Extras, escolha a op����o <emphasis role=\"strong\">Aplica����es > Adicionar/Remover 'Software'</emphasis>. Indique a senha de <code>root</code> quando lhe for pedida. Seleccione as aplica����es que necessitar da lista e escolha <emphasis>Aplicar</emphasis>."
+msgstr ""
+"Para instalar o 'software' tanto dos reposit��rios Core ou Extras, escolha a "
+"op����o <emphasis role=\"strong\">Aplica����es > Adicionar/Remover "
+"'Software'</emphasis>. Indique a senha de <code>root</code> quando lhe for "
+"pedida. Seleccione as aplica����es que necessitar da lista e escolha "
+"<emphasis>Aplicar</emphasis>."
#: en_US/Extras.xml:37(para)
msgid ""
1
0
28 Oct '06
Author: pfrields
Update of /cvs/docs/release-notes/FC-6
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6395/FC-6
Added Files:
Makefile README-Accessibility README.fedora-release
about-gnome.desktop about-gnome.desktop.in about-kde.desktop
about-kde.desktop.in about-title.xsl fedora-release-notes.spec
indexhtml-foot indexhtml-head main.xsl readmes.xsl sources
Log Message:
Add FC-6 branch. This branch should be used for errata updates, not devel -- although syncing them is fine.
--- NEW FILE Makefile ---
########################################################################
# Fedora Documentation Project Per-document Makefile
# License: GPL
# Copyright 2005,2006 Tommy Reynolds, MegaCoder.com
########################################################################
#
# Document-specific definitions.
#
DOCBASE = RELEASE-NOTES
PRI_LANG = en_US
OTHERS = el es it pl pt_BR pt ru sv zh_CN
FDPDIR = ${PWD}/../..
# Special legalnotice for this document:
LEGALNOTICEBASE =legalnotice-relnotes
# Special basename for packaging:
PKGNAME =fedora-release-notes
# Special PKGRPMFLAGS to keep Rawhide happy for f13
PKGRPMFLAGS =--define "_topdir ${PWD}" --define "_specdir ${PWD}" --define "_sourcedir ${PWD}" --define "_srcrpmdir ${PWD}" --define "_rpmdir ${PWD}"
########################################################################
# 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}/ArchSpecific.xml \
${1}/BackwardsCompatibility.xml \
${1}/Colophon.xml \
${1}/DatabaseServers.xml \
${1}/Desktop.xml \
${1}/Devel.xml \
${1}/Extras.xml \
${1}/Entertainment.xml \
${1}/Feedback.xml \
${1}/FileSystems.xml \
${1}/I18n.xml \
${1}/Installer.xml \
${1}/Java.xml \
${1}/Kernel.xml \
${1}/Legacy.xml \
${1}/Multimedia.xml \
${1}/OverView.xml \
${1}/PackageChanges.xml \
${1}/PackageNotes.xml \
${1}/ProjectOverview.xml \
${1}/RELEASE-NOTES.xml \
${1}/Security.xml \
${1}/Virtualization.xml \
${1}/WebServers.xml \
${1}/Welcome.xml \
${1}/Xorg.xml \
${1}/about-fedora.xml \
${1}/README.xml \
${1}/README-BURNING-ISOS.xml \
${1}/homepage.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
# print the message "FINISHED AT LAST" after building
# the HTML document version, uncomment the following
# line:
#${DOCBASE}-en/index.html::
# echo FINISHED AT LAST
########################################################################
###########
#
# Get or build OMF.
#
# If the per-doc Makefile provides a ${OMFINFILES} list, we use those.
# If it does not, and ${BUILDOMF} is defined, make one using XSLT and
# rpm-info data.
#
# The template OMF files are expected to use @VARNAME@ notation to
# allow replacement of their content dynamically at build time. They
# should retain this notation during PO/POT conversion so that
# translators never have to worry about that content. Substitution
# only occurs during the packaging process.
#
# FIXME: There may not be a need to have the ${PRI_LANG} prefixing
# each entry in ${OMFINFILES}. Might be a good idea to take that out.
# if OMFINFILES is empty, try and get the file list.
# If it's still empty, and BUILDOMF is set, use that to populate the list.
# Otherwise it stays empty. After all, we may not want them at all.
ifeq "${OMFINFILES}" ""
OMFINFILES=$(foreach F,$(wildcard ${PRI_LANG}/*.omf.in),$(shell basename ${F}))
ifeq "${OMFINFILES}" ""
ifdef BUILDOMF
OMFINFILES=${PKGNAME}.omf.in
${PRI_LANG}/${PKGNAME}.omf.in:: ${PRI_LANG}/${RPMINFO}
${XSLTPROC} --stringparam lang ${PRI_LANG} \
--stringparam docbase ${PKGNAME} \
${FDPDIR}/docs-common/packaging/omf-in.xsl \
$< > $@
endif
endif
endif
showvars::
@echo "OMFINFILES=\"${OMFINFILES}\""
define OMFVAR_template
$(foreach F,${OMFINFILES},$(eval OMFINFILES-${1}+=${1}/${F}))
$(foreach F,${OMFINFILES},$(eval OMFFILES-${1}+=$(patsubst %.in,${1}/%,${F})))
$(foreach F,${OMFINFILES},$(eval PKGOMFFILES-${1}+=$(patsubst \
%.omf.in,$(if $(findstring ${PRI_LANG},${1}),%-C.omf,%-${1}.omf), \
${F})))
showvars-debug::
@echo "PKGOMFFILES-${1}=\"${PKGOMFFILES-${1}}\""
@echo "OMFFILES-${1}=\"${PKGOMFFILES-${1}}\""
endef
$(foreach L,${LANGUAGES},$(eval $(call OMFVAR_template,${L})))
define OMFIN_template
.PHONY: omf-in-${1}
omf-in-${1}:: ${OMFINFILES-${1}}
# Treat .omf.in files just like XML... since they are!
$(foreach F,${OMFINFILES},$(eval $(call XML_template,${1},${PRI_LANG}/${F})))
clean::
${RM} ${OMFINFILES-${1}}
help::
@printf ${TFMT} 'omf-in-${1}' 'Make OMF input file for ${1}'
endef
$(foreach L,${OTHERS},$(eval $(call OMFIN_template,${L})))
.PHONY: omf-in
omf-in:: $(foreach L,${LANGUAGES},${OMFINFILES-${L}})
help::
@printf ${TFMT} 'omf-in' 'Make all OMF input files'
# To make the real OMF, just do a quick bit of sed processing.
# The spacing in the second command is purposeful to ensure no extra
# space appears in the sed command.
#
# Note the difference between @LANG@ and @LANGC@: the former is always
# replaced by the locale name, whereas the latter is replaced by the
# locale name *unless* the locale is en_US, in which case is is replaced
# by "C", the fallback.
%.omf: %.omf.in
sed -e 's!@RELEASE@!${VERSION}!g' $< > $@
sed -i 's!@DATE@!${REVDATE}!g' $@
sed -i 's!@LANG@!$(patsubst %/$(shell basename $<),%,$<)!g' $@
sed -i 's!@LANGC@!$(if $(findstring en_US,$(patsubst \
%/$(shell basename $<),%,$<)),C,$(patsubst \
%/$(shell basename $<),%,$<))!g' $@
define OMF_template
.PHONY: omf-${1}
omf-${1}:: ${OMFFILES-${1}}
clean::
${RM} ${OMFFILES-${1}}
help::
@printf ${TFMT} 'omf-${1}' 'Make all OMF files for ${1} locale'
endef
$(foreach L,${LANGUAGES},$(eval $(call OMF_template,${L})))
.PHONY: omf
omf:: $(foreach L,${LANGUAGES},${OMFFILES-${L}})
help::
@printf ${TFMT} 'omf' 'Make all OMF files for all locales'
define HACK_HTML_template
.PHONY: homepage-${1}
$(eval HOMEPAGEDIR=homepage)
$(eval HTMLEXTRAFILES-${1}=${HOMEPAGEDIR}/index-${1}.html)
$(eval HOMEPAGE_CSS=${HOMEPAGEDIR}/homepage.css)
$(eval HOMEPAGE_XSL=${HOMEPAGEDIR}/homepage.xsl)
homepage-${1}:: ${HOMEPAGEDIR}/index-${1}.html
${HOMEPAGEDIR}/index-${1}.html:: ${1}/homepage.xml ${XMLDEPFILES-${1}}
# Can we get away with just the above? Let's see...
LANG=$(1).UTF-8 ${XMLTO} html -x $(XSLHTML) -m ${HOMEPAGE_XSL} $(1)/homepage.xml
move-if-change index.html ${HOMEPAGEDIR}/index-${1}.html
mkdir -p stylesheet-images/
cp ${FDPDIR}/docs-common/stylesheet-images/*.png stylesheet-images
clean::
rm -rf ${HOMEPAGEDIR}/index-${1}.html stylesheet-images/
endef
$(foreach L,${LANGUAGES},$(eval $(call HACK_HTML_template,${L})))
define HACK_TXT_template
.PHONY: readme-${1} readme-isoburn-${1}
$(eval TXTEXTRAFILES-${1}=README-${1}.txt README-BURNING-ISOS-${1}.txt)
readme-${1}:: README-${1}.txt
README-${1}.txt:: ${1}/README.xml
LANG=${1}.UTF-8 ${XMLLINT} ${XMLLINTOPT} ${1}/README.xml \
> ${1}/README.lint.xml
LANG=${1}.UTF-8 ${XSLTPROC} \
${FDPDIR}/docs-common/packaging/strip-for-txt.xsl \
${1}/README.lint.xml > ${1}/README.stripped.xml && \
${RM} -f ${1}/README.lint.xml
LANG=${1}.UTF-8 ${XMLTO} ${XMLTOTXTPOSTOPT} txt \
${1}/README.stripped.xml && \
move-if-change README.stripped.txt README-${1}.txt
readme-isoburn-${1}:: README-BURNING-ISOS-${1}.txt
README-BURNING-ISOS-${1}.txt:: ${1}/README-BURNING-ISOS.xml
LANG=${1}.UTF-8 ${XMLLINT} ${XMLLINTOPT} ${1}/README-BURNING-ISOS.xml \
> ${1}/README-BURNING-ISOS.lint.xml
LANG=${1}.UTF-8 ${XSLTPROC} \
${FDPDIR}/docs-common/packaging/strip-for-txt.xsl \
${1}/README-BURNING-ISOS.lint.xml > \
${1}/README-BURNING-ISOS.stripped.xml && \
${RM} -f ${1}/README-BURNING-ISOS.lint.xml
LANG=${1}.UTF-8 ${XMLTO} ${XMLTOTXTPOSTOPT} txt \
${1}/README-BURNING-ISOS.stripped.xml && \
move-if-change README-BURNING-ISOS.stripped.txt \
README-BURNING-ISOS-${1}.txt
clean::
${RM} -f ${TXTEXTRAFILES-${1}}
${RM} -f ${1}/README.stripped.xml ${1}/README-BURNING-ISOS.stripped.xml
txt-${1} text-${1}:: ${TXTEXTRAFILES-${1}}
showvars::
@echo "TXTEXTRAFILES-${1}=\"${TXTEXTRAFILES-${1}}\""
endef
$(foreach L,${LANGUAGES},$(eval $(call HACK_TXT_template,${L})))
.PHONY: readme
readme:: $(foreach L,${LANGUAGES},${TXTEXTRAFILES-${L}})
#########
#
# These rules are for use in packaging the release notes for an ISO
# spin. To do so, just run "make release-pkg" and out pops a shiny
# tarball named "${PKGNAME}-<VER>.tar.gz where <VER> is the FC
# release (5.91, 6, etc.).
#
#########
#define PKGOMFFILES_template
#ifeq "${1}" "${PRI_LANG}"
#PKGOMFFILES-${1}=$(patsubst %.omf,%-C.omf,${OMFFILES-${1}})
#else
#PKGOMFFILES-${1}=$(patsubst %.omf,%-${1}.omf,${OMFFILES-${1}})
#endif
#showvars::
# @echo "PKGOMFFILES-${1}=${PKGOMFFILES-${1}}"
#endef
$(foreach L,${LANGUAGES},$(eval $(call PKGOMFFILES_template,${L})))
define PKGOMF_DOC_template
.PHONY: pkgomf-${1}-${2}
ifeq "${2}" "${PRI_LANG}"
pkgomf-${1}-${2}:: ${PKGNAME}-${VERSION}/${1}-C.omf
${PKGNAME}-${VERSION}/${1}-C.omf:: ${2}/${1}.omf
mkdir -p ${PKGNAME}-${VERSION}
cp ${2}/${1}.omf $$@
else
pkgomf-${1}-${2}:: ${PKGNAME}-${VERSION}/${1}-${2}.omf
${PKGNAME}-${VERSION}/${1}-${2}.omf:: ${2}/${1}.omf
mkdir -p ${PKGNAME}-${VERSION}
cp ${2}/${1}.omf $$@
endif
endef
$(foreach L,${LANGUAGES}, \
$(foreach F,$(patsubst %.omf.in,%,${OMFINFILES}), \
$(eval $(call PKGOMF_DOC_template,${F},${L}))))
define PKGOMF_template
.PHONY: pkgomf-${1}
pkgomf-${1}:: $(foreach F,${PKGOMFFILES-${1}},${PKGNAME}-${VERSION}/${F})
$(eval PKGFILES-${1}+=$(foreach F,${PKGOMFFILES-${1}},${PKGNAME}-${VERSION}/${F}))
endef
$(foreach L,${LANGUAGES},$(eval $(call PKGOMF_template,${L})))
define PKGHTML_NOCHUNKS_template
.PHONY: pkghtml-nochunks-${1}
pkghtml-nochunks-${1}:: ${PKGNAME}-${VERSION}/${DOCBASE}-${1}.html
$(eval PKGFILES-${1}+=${PKGNAME}-${VERSION}/${DOCBASE}-${1}.html)
${PKGNAME}-${VERSION}/${DOCBASE}-${1}.html:: ${DOCBASE}-${1}.html
mkdir -p ${PKGNAME}-${VERSION}
cp ${DOCBASE}-${1}.html $$@
endef
$(foreach L,${LANGUAGES},$(eval $(call PKGHTML_NOCHUNKS_template,${L})))
define PKGHTML_HOMEPAGE_template
.PHONY: pkghtml-homepage-${1}
pkghtml-homepage-${1}:: ${PKGNAME}-${VERSION}/${HOMEPAGEDIR}/index-${1}.html
$(eval PKGFILES-${1}+=${PKGNAME}-${VERSION}/${HOMEPAGEDIR}/index-${1}.html)
${PKGNAME}-${VERSION}/${HOMEPAGEDIR}/index-${1}.html:: ${HOMEPAGEDIR}/index-${1}.html
mkdir -p ${PKGNAME}-${VERSION}/${HOMEPAGEDIR}
cp ${HOMEPAGEDIR}/index-${1}.html $$@
endef
$(foreach L,${LANGUAGES},$(eval $(call PKGHTML_HOMEPAGE_template,${L})))
define PKGTXT_template
.PHONY: pkgtxt-${1}
pkgtxt-${1}:: ${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt ${PKGNAME}-${VERSION}/README-${1}.txt ${PKGNAME}-${VERSION}/README-BURNING-ISOS-${1}.txt
$(eval PKGFILES-${1}+=${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt ${PKGNAME}-${VERSION}/README-${1}.txt ${PKGNAME}-${VERSION}/README-BURNING-ISOS-${1}.txt)
${PKGNAME}-${VERSION}/${DOCBASE}-${1}.txt:: ${DOCBASE}-${1}.txt
mkdir -p ${PKGNAME}-${VERSION}
cp ${DOCBASE}-${1}.txt $$@
### README is hacked in until we have more control here...
${PKGNAME}-${VERSION}/README-${1}.txt:: README-${1}.txt
mkdir -p ${PKGNAME}-${VERSION}
cp README-${1}.txt $$@
${PKGNAME}-${VERSION}/README-BURNING-ISOS-${1}.txt:: README-BURNING-ISOS-${1}.txt
mkdir -p ${PKGNAME}-${VERSION}
cp README-BURNING-ISOS-${1}.txt $$@
endef
$(foreach L,${LANGUAGES},$(eval $(call PKGTXT_template,${L})))
define PKG_template
.PHONY: release-pkg-${1}
release-pkg-${1}:: ${PKGFILES-${1}}
showvars::
@echo "PKGFILES-${1}=${PKGFILES-${1}}"
endef
$(foreach L,${LANGUAGES},$(eval $(call PKG_template,${L})))
${PKGNAME}-${VERSION}/about-gnome.desktop:: about-gnome.desktop.in \
$(foreach LN,${OTHERS},${LN}/about-fedora.xml)
$(eval NAME_L10N=Name=$(shell ${XSLTPROC} \
about-title.xsl ${PRI_LANG}/about-fedora.xml))
$(eval COMMENT_L10N=Comment=$(shell ${XSLTPROC} \
about-title.xsl ${PRI_LANG}/about-fedora.xml))
$(eval EXEC_L10N=Exec=yelp file:///usr/share/doc/${PKGNAME}-${VERSION}/about/C/about-fedora.xml)
$(foreach L,${LANGUAGES},$(eval \
NAME_L10N+=\nName[${L}]=$(shell ${XSLTPROC} \
about-title.xsl ${L}/about-fedora.xml)))
$(foreach L,${LANGUAGES},$(eval \
COMMENT_L10N+=\nComment[${L}]=$(shell ${XSLTPROC} \
about-title.xsl ${L}/about-fedora.xml)))
$(foreach L,${LANGUAGES},$(eval \
EXEC_L10N+=\nExec[${L}]=yelp file:///usr/share/doc/${PKGNAME}-${VERSION}/about/${L}/about-fedora.xml))
sed -e 's!@NAME-L10N@!${NAME_L10N}!' -e 's!@COMMENT-L10N@!${COMMENT_L10N}!' -e 's!@EXEC-L10N@!${EXEC_L10N}!' $< > $@
.PHONY: release-pkg
release-pkg:: ${PKGNAME}-${VERSION}.tar.gz
${PKGNAME}-${VERSION}.tar.gz:: $(foreach L,${LANGUAGES},${PKGFILES-${L}}) \
${PKGNAME}-${VERSION}/about-gnome.desktop
cp -a --parents css/*css fedora.css ${HOMEPAGE_CSS} img/*png stylesheet-images/*png ${PKGNAME}-${VERSION}
mkdir -p ${PKGNAME}-${VERSION}/about/C && \
cp ${PRI_LANG}/about-fedora.xml ${PKGNAME}-${VERSION}/about/C
$(foreach LN,${OTHERS},$(eval \
$(shell mkdir -p ${PKGNAME}-${VERSION}/about/${LN})))
$(foreach LN,${OTHERS},$(eval \
$(shell cp ${LN}/about-fedora.xml ${PKGNAME}-${VERSION}/about/${LN})))
cp -a README-Accessibility ${PKGNAME}-${VERSION}
tar czf ${PKGNAME}-${VERSION}.tar.gz ${PKGNAME}-${VERSION}
clean::
${RM} -rf ${PKGNAME}-${VERSION}.tar.gz
${RM} -rf ${PKGNAME}-${VERSION}
help::
@printf ${TFMT} 'release-pkg' 'Make a tarball suitable for import to Core'
.PHONY: release-srpm
release-srpm:: ${PKGNAME}-${VERSION}-${RELEASE}.src.rpm
${PKGNAME}-${VERSION}-${RELEASE}.src.rpm:: ${SPECFILE} ${PKGNAME}-${VERSION}.tar.gz
rpmbuild -bs ${PKGRPMFLAGS} ${SPECFILE}
clean::
${RM} -rf ${PKGNAME}-${VERSION}-${RELEASE}.src.rpm
help::
@printf ${TFMT} 'release-srpm' 'Make a SRPM suitable for import to Core'
--- NEW FILE README-Accessibility ---
Linux Accessibility Solutions
=============================
Copyright �� 2003 by Red Hat, Inc.
Abstract
========
There are approximately 500 million people worldwide with some kind of
visual, hearing, or mobility impairment. There are currently over 54
million people with disabilities in the US alone and that number is
significantly increasing as the baby boomer generation continues to
age. People with disabilities often find it extremely difficult to
effectively use existing and emerging technologies designed without regard
to their needs. Websites with inaccessible content can also be problematic
for screen readers and other specialized devices used by the disabled
community.
Accessible features have been voluntarily integrated into operating
systems, Web interfaces and other technologies because of marketing
potential or because it was "the right thing to do." Equal access to
educational, professional and recreational technologies is rapidly becoming
a legal requirement. Federal agencies in numerous countries are formulating
accessibility standards. Federal requirements in the United States went
into effect in June 2001.
There are specialized hardware devices, applications and utilities
available that considerably increase the usability of Linux for individuals
with special needs.
This document covers the following topics:
==========================================
* Why should people choose Fedora Core as an accessibility solution?
* The Section 508 Mandate
* The Voluntary Product Accessibility Template (VPAT)
* Available open source tools, utilities and drivers
* Using Speakup with Fedora Core
* Using Emacspeak and Festival with Fedora Core
* Reading news using Fedora Core and Emacspeak
* Sending and reading email using Fedora Core and Emacspeak
* Browsing the Web using Fedora Core and Emacspeak
* Using Emacspeak to execute Fedora Core shell commands
* Using BRLTTY with Fedora Core
* Finding more information on Linux accessibility
Why should people choose Fedora Core as an accessibility solution?
==================================================================
Linux offers an inexpensive and efficient solution for the disabled
community. Open source software costs far less compared to tools that run
on other operating systems and Linux tools are often freely downloadable.
While the Graphic User Interface (GUI) is convenient for sighted users, it
is often inhibiting to those with visual impairments because of the
difficulty speech synthesizers have interpreting graphics. Linux is a great
OS for users with visual limitations because the GUI is not required by the
kernel. Most modern tools including email, news, Web browsers, calendars,
calculators and much more can run on Linux without the GUI. The working
environment can also be customized to meet the hardware or software needs
of the user.
Fedora Core (and its predecessor Red Hat Linux) is an extremely popular
Linux distribution; most industry professionals are familiar with it,
making it relatively straightforward to find assistance if necessary.
Red Hat provides the up2date client and Red Hat Network. These services
simplify file management and make it easier to effortlessly keep their
computers secure and up to date.
The Section 508 Mandate
=======================
The Section 508 Mandate is an addendum to the Rehabilitation Act of 1998
that requires federal agencies to use accessible electronic and information
technologies so that people with special needs have the same opportunities
as everyone else.
For detailed information about the requirements of the Section 508 Mandate,
visit this link:
http://www.section508.gov/
The Voluntary Product Accessibility Template (VPAT)
===================================================
The VPAT template details how a particular product or service conforms to
Section 508 criteria. The VPAT helps federal personnel adhere to Section
508 by helping them determine whether they are buying the most accessible
IT products and services available. The VPAT template participation by
private vendors is voluntary. These templates are hosted on the individual
vendor websites. The vendors maintain their own information and the
government does not endorse this information in any way. For more
information on these templates, contact the legal department at Red Hat
Inc.
Available open source tools, utilities and drivers
==================================================
Current development is focusing on visual and mobility impairments. There
are both software and hardware based solutions available. There are also
both console and graphic solutions available, however, the graphic
solutions are limited at this time. The GNOME Accessibility Project is
making great progress bringing the Gnome desktop up to speed.
For more information about the GNOME Accessibility Project, visit:
http://developer.gnome.org/projects/gap/
The KDE Accessibility Project is simultaneously working to make sure the
KDE desktop is accessible as well.
For more information about the KDE Accessibility Project, visit:
http://accessibility.kde.org/
Hardware
==========
The biggest advantage of the hardware speech solutions is that speech is
available before the OS loads (makes it easier to install). Hardware
solutions include speech synthesizers, braille terminals, braille printers,
sip and puff systems, eye gaze pointing devices, etc. These devices are
usually very expensive and it is difficult to find drivers for
them. Drivers are being written (mostly for speech synthesizers) for Linux
but they need to be tested and integrated by the community into "upstream"
software projects before becoming part of Fedora Core.
Jim Van Zandt has also written several servers that work with
Emacspeak. These servers can be found in a package called Emacspeak-ss on
Jim Van Zandt's website or linked within the Emacspeak HOWTO
The Emacspeak HOWTO is available online at:
http://www.mv.com/ipusers/vanzandt/Emacspeak-HOWTO.html
For more information on Emacspeak, visit:
http://emacspeak.sf.net/
Software
==========
This document focuses mostly on software tools and utilities that work with
Linux. Most of these tools have been developed by the Open Source community
and many have not yet been tested by Red Hat, Inc. Speakup, Emacspeak,
Festival and BRLTTY have been tested by Red Hat. Festival and Emacspeak
ships with Red Hat Linux 7.3 and later releases (including Fedora
Core). The following list of downloadable tools provide various functions:
* Software Speech Synthesizers:
IBM ViaVoice Outloud
Festival
MBROLA
Emacspeak
* Magnification Tools:
xzoom
SVGATextMode
* Speech Recognition Software:
IBM ViaVoice
cvoicecontrol
Xvoice
* Screen Readers:
Screader
Speakup
BRLTTY
Visual Bells
Keyboard Tools
AccessX
StickyKeys
GTKeyboard
Using Speakup with Fedora Core
================================
Speakup is a GPL screen review package written by Kirk Reiser and Andy
Berdan. Speakup gives users with visual or mobility impairments the ability
to have audible console feedback using a speech synthesizer. Red Hat
recommends Speakup for blind users because it provides an audible
installation and is fully supported by the blind open source community.
William F. Acker currently maintains the Speakup packages for the Red Hat
distribution. His contributions to the open source community and to blind
Linux users have been outstanding.
Speakup works with the following hardware synthesizers:
DoubleTalk PC/LT
LiteTalk
Accent PC/SA
Speakout
Artic Transport
Audapter
Braille 'N Speak / Type 'N Speak
Dectalk External and Express
Apollo2
For instructions on using Speakup with Fedora Core, visit:
http://www.linux-speakup.org/ftp/disks/redhat/HOWTO_INSTALL.html
For more information about Speakup, or to contribute to the Speakup project
visit:
http://www.linux-speakup.org
Using Emacspeak with Fedora Core
==================================
Before using Emacspeak, you should familiarize yourself with some
documentation. Start with "A Gentle Introduction to Emacspeak" by Gary
Lawrence Murphy, which is available online at:
http://emacspeak-guide.sourceforge.net/
The Emacspeak HOWTO written by Jim Van Zandt is also a very good resource,
although the document is limited to the Slackware distribution. The
Emascspeak HOWTO is available online at:
http://www.mv.com/ipusers/vanzandt/Emacspeak-HOWTO.html
Reading news using Fedora Core and Emacspeak
===============================================
Gnus is the news reader included with Emacspeak. Gnus gets the appropriate
data from the ~/.newsrc file in the user's home directory. To post and read
news through Emacspeak, refer to http://www.gnus.org/ for manuals,
tutorials, HOWTOs, and more. To start Gnus, type the following command.
Note that "M-x" means to hold down the [Meta] key (often labeled [Alt])
while simultaneously pressing the [x] key:
M-x gnus
This command displays all the newsgroups you are subscribed to. To select a
newsgroup, highlight your selection and press the space bar. Next, specify
how many articles you would like to open. Type the number you desire and
press [Enter]. This splits the screen into two buffers. The top section is
the summary buffer, the bottom section is the article buffer. You should
now be able to read your news. For a detailed overview of this tool, visit:
http://www.mv.com/ipusers/vanzandt/Emacspeak-HOWTO.html
Sending and reading email using Fedora Core and Emacspeak
===========================================================
There are several email clients available in Emacspeak. The Gnus
utility can actually be used for both email and news. Type:
M-x gnus
to start Gnus, then type:
M
to use the mail client.
The easiest tool to use is RMAIL. To send a message using RMAIL, type the
following command. Note that "C-x" means to hold down the [Ctrl] key while
simultaneously pressing the [x] key:
C-x m
Fill in the To: and Subject: fields. Put the body of the message below the
line that reads -text follows this line-. You can send the message when you
are finished by typing:
C-c C-c
To read a message using RMAIL type:
M-x rmail
For more information on using RMAIL visit:
http://www.gnu.org/manual/emacs-20.3/html_chapter/emacs_31.html
Browsing the Web using Fedora Core and Emacspeak
==================================================
You must download William Perry's w3 browser:
ftp://people.redhat.com/jlamb/
You can install the package from the FTP site (after you log in as root)
and type:
rpm -ivh ftp://people.redhat.com/jlamb/w3-4.0pre.44-1.i386.rpm
Once the package is installed, restart Emacspeak and type the following
command:
M-x w3
This starts the browser and opens the default homepage. For more
information on w3 including a tutorial and command explanation, read
through the information on the default home page, available online at:
http://www.cs.indiana.edu/elisp/w3/docs.html
Using Emacspeak to execute Linux shell commands
===============================================
You do not have to leave Emacspeak to execute a Linux command. To
execute a command within Emacspeak, type
ESC !
and then enter the name of the command you would like to run when
Emacspeak prompts you. To exit the command output window type:
C-x 1
This functionality is extremely useful. You can even print and compile
files you are working on within Emacspeak. For more information on Linux
shell commands refer to Josh's Linux Guide or any other comparable command
resource.
Josh's Linux Guide is available online at:
http://jgo.local.net/LinuxGuide/linux-commands.html
Using BRLTTY with Fedora Core
===============================
BRLTTY provides access to the Linux command line for blind people using
refreshable braille displays. The tool provides complete screen review
functionality and minimal speech capability. BRLTTY has been tested by Red
Hat Inc. and is available in RPM format. For information and documentation
on BRLTTY, visit the following link:
http://mielke.cc/brltty/
Finding more information on Linux accessibility
===============================================
The following documents offer helpful suggestions for making Linux
more accessible:
Linux Accessibility HOWTO
http://tldp.org/HOWTO/Accessibility-HOWTO/index.html
Keyboard-and-Console-HOWTO
http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO.html
Additional links which may be helpful include:
The Speakup Homepage
http://www.braille.uwo.ca/speakup/
Trace Center
http://trace.wisc.edu/
Blinux
http://leb.net/blinux/
--- NEW FILE README.fedora-release ---
==========================================
NOTES FOR PACKAGING FEDORA-RELEASE-NOTES
==========================================
If you want to turn the current release notes into a SRPM package for
import to Core, do the following:
1. Make sure you have the release-notes/ module and the docs-common/
module -- also in Docs CVS -- in the same location.
2. Edit the fedora-release-notes.spec file and edit the "Release" tag
and make a new entry in the %changelog. There is no need to use
%{?dist} since this is a single-release package.
3. Run 'make release-srpm' to build the SRPM. The contents of the
source tarball -- the ones not already in the top-level directory --
remain in the "fedora-release-notes-<version>/" directory if you want to
review them. The tarball is there as well.
-- PWF, rev. 18 July 2006
--- NEW FILE about-gnome.desktop ---
[Desktop Entry]
Encoding=UTF-8
Name=About Fedora
Comment=Learn more about Fedora
Exec=yelp file:///usr/share/doc/fedora-release-notes-@RELEASE@/about/C/about-fedora.xml
Icon=fedora-logo-icon
Terminal=false
Type=Application
Categories=X-Fedora-About;
StartupNotify=true
OnlyShowIn=GNOME;
--- NEW FILE about-gnome.desktop.in ---
[Desktop Entry]
Encoding=UTF-8
@NAME-L10N@
@COMMENT-L10N@
@EXEC-L10N@
Icon=fedora-logo-icon
Terminal=false
Type=Application
Categories=X-Fedora-About;
StartupNotify=true
OnlyShowIn=GNOME;
--- NEW FILE about-kde.desktop ---
[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=About Fedora
GenericName=About Fedora
Comment=Learn more about Fedora
Exec=khelpcenter
Icon=
Path=
Terminal=false
Type=Application
DocPath=khelpcenter/plugins/about.html
Categories=Qt;KDE;Application;Core;
X-KDE-StartupNotify=true
OnlyShowIn=KDE;
GenericName[en_US]=About Fedora
--- NEW FILE about-kde.desktop.in ---
[Desktop Entry]
Version=1.0
Encoding=UTF-8
#Name=About Fedora
#GenericName=About Fedora
#Comment=Learn more about Fedora
#Exec=khelpcenter
@NAME-L10N@
@GENERICNAME-L10N@
@COMMENT-L10N@
@EXEC-L10N@
Icon=
Path=
Terminal=false
Type=Application
DocPath=khelpcenter/plugins/about.html
Categories=Qt;KDE;Application;Core;
X-KDE-StartupNotify=true
OnlyShowIn=KDE;
--- NEW FILE about-title.xsl ---
<?xml version="1.0" encoding="UTF-8"?>
<!-- Pull title from about-fedora.xml article -->
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output omit-xml-declaration="yes" preserve-space="no" encoding="UTF-8"
indent="no" method="text"/>
<xsl:template match="*">
<xsl:value-of select="/article/title"/>
</xsl:template>
</xsl:stylesheet>
--- NEW FILE fedora-release-notes.spec ---
Name: fedora-release-notes
Version: 6
Release: 3
Summary: Release Notes for Fedora Core %{version}
URL: http://fedoraproject.org/wiki/Docs/Beats
Group: System Environment/Base
License: Distributable
Source0: fedora-release-notes-%{version}.tar.gz
#Source1: indexhtml-head
#Source2: indexhtml-foot
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildArch: noarch
BuildRequires: desktop-file-utils
Provides: indexhtml = %{version}-%{release}
Obsoletes: indexhtml < 9-3
%description
These are the official Release Notes for Fedora Core %{version},
written and edited by the Fedora community. For more
information on the Release Notes process or how you can
contribute, refer to the Release Notes HOWTO located at
http://fedoraproject.org/wiki/Docs/Beats/HowTo.
%prep
%setup -q
%build
#cat %{SOURCE1} > index.html
#sed 's/.*<div class="article"/<div class="article"/g' \
# RELEASE-NOTES-en_US.html >> index.html
#cat %{SOURCE2} >> index.html
sed -i 's/@RELEASE@/%{version}/g' about-gnome.desktop
%install
rm -rf $RPM_BUILD_ROOT
install -m 755 -d $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
install -m 644 fedora.css $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
install -m 644 homepage/* $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
install -m 644 homepage/index-en_US.html $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/index.html
install -m 644 README-Accessibility $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
install -m 644 README-BURNING-ISOS*.txt $RPM_BUILD_ROOT%{_defaultdocdir}/HTML
for DIR in css img stylesheet-images ; do
install -m 755 -d $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/$DIR
find $DIR -type f -exec install -m 644 {} $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/$DIR \;
done
for F in RELEASE-NOTES-*.html; do
install -m 755 -D $F $RPM_BUILD_ROOT%{_defaultdocdir}/HTML/$F
done
find about/ -type f -exec install -m 644 -D {} $RPM_BUILD_ROOT%{_defaultdocdir}/fedora-release-notes-%{version}/{} \;
install -m 755 -d $RPM_BUILD_ROOT%{_datadir}/omf/fedora-release-notes
install -m 644 fedora-release-notes-*.omf $RPM_BUILD_ROOT%{_datadir}/omf/fedora-release-notes/
install -m 755 -d $RPM_BUILD_ROOT%{_datadir}/omf/about-fedora
install -m 644 about-*omf $RPM_BUILD_ROOT%{_datadir}/omf/about-fedora/
install -m 644 -D about-gnome.desktop $RPM_BUILD_ROOT%{_datadir}/applications/about-fedora.desktop
%clean
rm -rf $RPM_BUILD_ROOT
%post
if [ -x /usr/bin/scrollkeeper-update ]; then scrollkeeper-update -q -o %{_datadir}/omf/{%{name},about-fedora}; fi
if [ -x /usr/bin/update-desktop-database ]; then update-desktop-database &> /dev/null; fi
%postun
if [ -x /usr/bin/scrollkeeper-update ]; then scrollkeeper-update -q; fi
if [ -x /usr/bin/update-desktop-database ]; then update-desktop-database &> /dev/null; fi
%files
%defattr(-,root,root,-)
%{_defaultdocdir}/HTML
%{_defaultdocdir}/fedora-release-notes-%{version}/about
%{_datadir}/applications/about-fedora.desktop
%{_datadir}/omf/fedora-release-notes/
%{_datadir}/omf/about-fedora/
%changelog
* Sun Oct 15 2006 Paul W. Frields <stickster(a)gmail.com> - 6-3
- Fix IG publication URL
- Amend CSS to respect font selections and restore icons
* Sun Oct 8 2006 Paul W. Frields <stickster(a)gmail.com> - 6-2
- Localize About Fedora menu item (somewhat)
* Thu Oct 05 2006 Jesse Keating <jkeating(a)redhat.com> - 6-1
- Build for FC6, lots of new translations
* Sat Sep 30 2006 Paul W. Frields <stickster(a)gmail.com> - 5.92-7
- Include new i18n browser home page
* Mon Sep 25 2006 Jesse Keating <jkeating(a)redhat.com> - 5.92-6
- Bump for lang fixes
* Tue Sep 12 2006 Paul W. Frields <stickster(a)gmail.com> - 5.92-5
- Update scrollkeeper data for about-fedora
* Mon Sep 11 2006 Paul W. Frields <stickster(a)gmail.com> - 5.92-4
- Update about-fedora
* Wed Sep 6 2006 Paul W. Frields <stickster(a)gmail.com> - 5.92-3
- Make sure we package README-BURNING-ISOS files
* Tue Sep 5 2006 Jesse Keating <jkeating(a)redhat.com> - 5.92-1
- Bump for 5.92
* Fri Sep 1 2006 Paul W. Frields <stickster(a)gmail.com> - 5.91-8
- Handle i18n OMF files
* Sat Aug 26 2006 Paul W. Frields <stickster(a)gmail.com> - 5.91-7
- Add README-BURNING-ISOS.txt for inclusion in mirrors
- Put About document in proper directory
* Wed Aug 2 2006 Jesse Keating <jkeating(a)redhat.com> - 5.91-6
- bump
* Wed Aug 2 2006 Paul W. Frields <stickster(a)gmail.com> - 5.91-5
- Add README-Accessibility (moved from fedora-release)
* Wed Jul 26 2006 Paul W. Frields <stickster(a)gmail.com> - 5.91-4
- Process paths correctly (#200266)
- Package standalone HTML
* Sun Jul 23 2006 Jesse Keating <jkeating(a)redhat.com> - 5.91-3
- Only use tabs
- Version the indexhtml provides/obsoletes
- Cleanup post and postun scriptlets
- Don't require fedora-release, fedora-release requires us.
- Add a URL tag
* Sun Jul 16 2006 Paul W. Frields <stickster(a)gmail.com> - 5.91-1
- Initial release for Fedora Core 6 test2.
--- NEW FILE indexhtml-foot ---
</div></div>
<div class="fedora-corner-br"> </div>
<div class="fedora-corner-bl"> </div>
</div>
<!-- content END -->
<!-- footer BEGIN -->
<div id="fedora-footer">
Copyright �� 2006 Red Hat, Inc. All rights reserved.
<br>
Fedora is a trademark of Red Hat, Inc.
<br>
The Fedora Project is not a supported product of Red Hat, Inc.
<br>
Red Hat, Inc. is not responsible for the content of other sites.
</div>
<!-- footer END -->
</body></html>
--- NEW FILE indexhtml-head ---
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"><html><head><title>Fedora Project, sponsored by Red Hat</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" type="text/css" media="print" href="css/print.css">
<style type="text/css" media="screen">
@import url("css/layout.css");
@import url("css/content.css");
@import url("css/docbook.css");
</style>
<!-- <script src="offsite.js" type="text/javascript"></script> -->
<meta name="MSSmartTagsPreventParsing" content="TRUE">
<link rel="shortcut icon" href="http://fedora.redhat.com/images/favicon.ico">
<link rel="icon" href="http://fedora.redhat.com/images/favicon.ico"></head>
<body onload="OffSite();">
<!-- header BEGIN -->
<div id="fedora-header">
<div id="fedora-header-logo">
<a href="http://fedora.redhat.com/" id="link-internal"><img src="img/header-fedora_logo01.png" alt="Fedora Project"></a>
</div>
<div id="fedora-header-items">
<span class="fedora-header-icon">
<a href="http://fedora.redhat.com/Download/" id="link-internal"><img src="img/header-download.png" alt=" ">Download</a>
<a href="http://fedora.redhat.com/About/Projects/" id="link-internal"><img src="img/header-projects.png" alt=" ">Projects</a>
<a href="http://fedoraproject.org/wiki/FAQ/" id="link-internal"><img src="img/header-faq.png" alt=" ">FAQ</a></span>
</div>
</div>
<div id="fedora-nav"></div>
<!-- header END -->
<!-- leftside BEGIN -->
<div id="fedora-side-left">
<div id="fedora-side-nav-label">Site Navigation:</div> <ul id="fedora-side-nav">
<li><a href="http://fedora.redhat.com/" id="link-internal">Home</a></li>
<li><a href="http://fedora.redhat.com/Download/" id="link-internal">Download</a></li>
<li><a href="http://fedora.redhat.com/docs/" id="link-internal">Documentation</a><ul>
<li><strong><a href="http://fedora.redhat.com/docs/release-notes/" id="link-internal">Release Notes</a></strong></li>
</ul></li>
<li><a href="http://fedora.redhat.com/About/Projects/" id="link-internal">Projects</a></li>
<li><a href="http://fedora.redhat.com/Contribute/" id="link-internal">Contribute</a></li>
<li><a href="http://fedora.redhat.com/About/" id="link-internal">About</a></li>
<li><a href="http://fedoraproject.org/" id="link-internal">FedoraProject.org</a></li>
<li><a href="http://fedoraproject.org/wiki/FAQ" id="link-internal">Fedora Project FAQ</a></li>
<li><a href="http://fedoraforum.org/" id="link-internal">Fedora End-User Support Forum</a></li>
</ul>
</div>
<!-- leftside END -->
<!-- content BEGIN -->
<div id="fedora-middle-two">
<div class="fedora-corner-tr"> </div>
<div class="fedora-corner-tl"> </div>
<div id="fedora-content">
--- NEW FILE main.xsl ---
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:exsl="http://exslt.org/common"
version="1.0"
exclude-result-prefixes="exsl">
<xsl:import href="readmes.xsl"/>
<xsl:import href="/usr/share/sgml/docbook/xsl-stylesheets/html/chunk-common.xsl"/>
<xsl:include href="/usr/share/sgml/docbook/xsl-stylesheets/html/manifest.xsl"/>
<!-- Why is chunk-code now xsl:included?
Suppose you want to customize *both* the chunking algorithm used *and* the
presentation of some elements that may be chunks. In order to do that, you
must get the order of imports "just right". The answer is to make your own
copy of this file, where you replace the initial import of "docbook.xsl"
with an import of your own base.xsl (that does its own import of docbook.xsl).
Put the templates for changing the presentation of elements in your base.xsl.
Put the templates that control chunking after the include of chunk-code.xsl.
Voila! (Man I hope we can do this better in XSLT 2.0)
-->
<!-- don't show TOC for article because html viewer in anaconda doesn't support the dt and dl tags -->
<xsl:param name="generate.toc">
article nop
</xsl:param>
<xsl:include href="/usr/share/sgml/docbook/xsl-stylesheets/html/profile-docbook.xsl"/>
<xsl:param name="onechunk" select="1"/>
<xsl:output method="html" encoding="utf-8" indent="no"/>
</xsl:stylesheet>
--- NEW FILE readmes.xsl ---
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
version='1.0'>
<xsl:output method="html" encoding="UTF-8" indent="no"/>
<!-- This sets the extension for HTML files to ".html". -->
<!-- (The stylesheet's default for XHTML files is ".xhtm".) -->
<xsl:param name="html.ext" select="'.html'"/>
<!-- This sets the filename based on the ID. -->
<xsl:param name="use.id.as.filename" select="'0'"/>
<xsl:param name="suppress.navigation" select="'1'"/>
<xsl:param name="generate.toc">
article nop
</xsl:param>
<xsl:param name="chapter.autolabel" select="'0'"/>
<xsl:template match="command">
<xsl:call-template name="inline.monoseq"/>
</xsl:template>
<xsl:template match="application">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guibutton">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guiicon">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guilabel">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guimenu">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guimenuitem">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="guisubmenu">
<xsl:call-template name="inline.boldseq"/>
</xsl:template>
<xsl:template match="filename">
<xsl:call-template name="inline.monoseq"/>
</xsl:template>
</xsl:stylesheet>
--- NEW FILE sources ---
### This describes the various package repositories (repos) that up2date will
### query for packages. It currently supports apt-rpm, yum, and "dir" repos.
### Format is one repository (repo) entry per line, # starts comments, the
### first word on each line is the type of repo.
### The default RHN (using "default" as the url means use the one in the
### up2date config file).
#up2date default
### Note: when a channel label is required for the non up2date repos,
### the label is solely used as an internal identifier and is not
### based on the url or any other info from the repos.
### An apt style repo (the example is arjan's 2.6 kernel repo).
### The format is:
### type channel-label service:server path repo name
#apt arjan-2.6-kernel-i386 http://people.redhat.com ~arjanv/2.5/ kernel
### Note: for apt repos, there can be multiple repo names specified (space
### seperated).
### A yum style repo. The format is:
### type channel-label url
yum fedora-core-3 http://download.fedora.redhat.com/pub/fedora/linux/core/3/$ARCH/os/
yum updates-released-fc3 http://download.fedora.redhat.com/pub/fedora/linux/core/updates/3/$ARCH/
yum-mirror fedora-core-3 http://fedora.redhat.com/download/up2date-mirrors/fedora-core-3
yum-mirror updates-released-fc3 http://fedora.redhat.com/download/up2date-mirrors/updates-released-fc3
#yum updates-testing http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/3/$…
#yum-mirror updates-testing http://fedora.redhat.com/download/up2date-mirrors/updates-testing-fc3
#yum development http://download.fedora.redhat.com/pub/fedora/linux/core/development/$ARCH/
#yum-mirror development http://fedora.redhat.com/download/up2date-mirrors/fedora-core-rawhide
### A local directory full of packages (a "dir" repo). For example:
#dir my-favorite-rpms /var/spool/RPMS/
# Multiple versions of all repos except "up2date" can be used. Dependencies
# can be resolved "cross-repo" if need be.
1
0
Author: pfrields
Update of /cvs/docs/release-notes/FC-6/xmlbeats
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6241/xmlbeats
Log Message:
Directory /cvs/docs/release-notes/FC-6/xmlbeats added to the repository
1
0
Author: pfrields
Update of /cvs/docs/release-notes/FC-6/scripts
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6241/scripts
Log Message:
Directory /cvs/docs/release-notes/FC-6/scripts added to the repository
1
0
Author: pfrields
Update of /cvs/docs/release-notes/FC-6/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6241/po
Log Message:
Directory /cvs/docs/release-notes/FC-6/po added to the repository
1
0
Author: pfrields
Update of /cvs/docs/release-notes/FC-6/img
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6241/img
Log Message:
Directory /cvs/docs/release-notes/FC-6/img added to the repository
1
0
Author: pfrields
Update of /cvs/docs/release-notes/FC-6/figs
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6241/figs
Log Message:
Directory /cvs/docs/release-notes/FC-6/figs added to the repository
1
0
Author: pfrields
Update of /cvs/docs/release-notes/FC-6/homepage
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv6241/homepage
Log Message:
Directory /cvs/docs/release-notes/FC-6/homepage added to the repository
1
0