release-notes/FC4 GPL, NONE, 1.1 README-Accessibility, NONE, 1.1 README-master-en.xml, NONE, 1.1 RELEASE-NOTES-master-en.xml, NONE, 1.1 RPM-GPG-KEY, NONE, 1.1 RPM-GPG-KEY-beta, NONE, 1.1 RPM-GPG-KEY-fedora, NONE, 1.1 RPM-GPG-KEY-fedora-rawhide, NONE, 1.1 RPM-GPG-KEY-fedora-test, NONE, 1.1 RPM-GPG-KEY-rawhide, NONE, 1.1 autorun-template, NONE, 1.1 eula.py, NONE, 1.1 eula.txt, NONE, 1.1 fedora-devel.repo, NONE, 1.1 fedora-release.spec, NONE, 1.1 fedora-updates-testing.repo, NONE, 1.1 fedora-updates.repo, NONE, 1.1 fedora.repo, NONE, 1.1 indexhtml-foot, NONE, 1.1 indexhtml-head, NONE, 1.1 main.xsl, NONE, 1.1 readmes.xsl, NONE, 1.1 sources, NONE, 1.1
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Fri May 20 21:55:13 UTC 2005
- Previous message (by thread): release-notes/FC4/css - New directory
- Next message (by thread): release-notes/FC4/img corner-bl.png, NONE, 1.1 corner-br.png, NONE, 1.1 corner-tl.png, NONE, 1.1 corner-tr.png, NONE, 1.1 header-download.png, NONE, 1.1 header-faq.png, NONE, 1.1 header-fedora_logo.png, NONE, 1.1 header-projects.png, NONE, 1.1
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: kwade
Update of /cvs/docs/release-notes/FC4
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13595
Added Files:
GPL README-Accessibility README-master-en.xml
RELEASE-NOTES-master-en.xml RPM-GPG-KEY RPM-GPG-KEY-beta
RPM-GPG-KEY-fedora RPM-GPG-KEY-fedora-rawhide
RPM-GPG-KEY-fedora-test RPM-GPG-KEY-rawhide autorun-template
eula.py eula.txt fedora-devel.repo fedora-release.spec
fedora-updates-testing.repo fedora-updates.repo fedora.repo
indexhtml-foot indexhtml-head main.xsl readmes.xsl sources
Log Message:
Following previous practice of making a new directory in the module for each release. No idea yet if this is the best idea, so choosing to stay close to existing practice to simplify.
--- NEW FILE GPL ---
*****************************************************************************
The following copyright applies to the Red Hat Linux compilation and any
portions of Red Hat Linux it does not conflict with. Whenever this
policy does conflict with the copyright of any individual portion of Red Hat
Linux, it does not apply.
*****************************************************************************
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
--- 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 (see
http://www.linux-speakup.org/ftp/disks/fedora/).
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-master-en.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//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 "@VERSION@"> <!-- The software's version -->
]>
<article id="index" lang="en" arch="x86;x86_64" os="test;final">
<articleinfo>
<title>&DISTRO; &DISTROVER; README</title>
<copyright>
<year>2004</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
<legalnotice id="legalnotice">
<para>The contents of this CD-ROM are Copyright © 2004 &PROJ; 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 at 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>
<sect1 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
|----> 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>
<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-3. 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>
(Do this only for disc 1)</para>
</listitem>
<listitem>
<para><command>umount /mnt/cdrom</command></para>
</listitem>
</orderedlist>
</sect1>
<sect1 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">
<remark os="test">(x86;x86_64)</remark>
<title>Note</title>
<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>
</sect1>
<sect1 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>
</sect1>
<sect1 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>
</sect1>
<sect1 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> Not really important (I'm using
"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>
<listitem>
<para><guilabel>Blocks:</guilabel> 114406 (The README blocker bug
number)</para>
</listitem>
</itemizedlist>
<para>A quick way of seeing what sorts of bugs have been posted against the
README is to look at the bugs listed in the <guilabel>Bug 114406 depends
on:</guilabel> field of the &DISTRO; release notes blocker bug:</para>
<para><ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114406">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114406</ulink></para>
<para>If you are interested in following the discussion of any of these
bugs, feel free to add yourself to the bug's CC list. That way, you'll
get email whenever there are any changes to the bug.</para>
<para>As bugs are posted for the various parts of the README file,
subsequent test versions of these release notes will contain links similar
to this one:</para>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114408">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114408</ulink>
%%%</remark>
<para>These links point to Bugzilla entries for the information preceding
the link. This makes it easier for people to contribute — just
point your browser at the link, add your comments to the bug, and commit
your changes.</para>
</sect1>
<ackno>(
<emphasis arch="x86">x86</emphasis>
<emphasis arch="x86_64">x86_64</emphasis>
)</ackno>
</article>
--- NEW FILE RELEASE-NOTES-master-en.xml ---
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.1//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!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 "@VERSION@"> <!-- The software's version -->
<!-- *************** Local entities for SELinux sect *************** -->
<!ENTITY SEL "SELinux"> <!-- -->
]>
<article id="index" lang="en" arch="x86;x86_64" os="test;final">
<articleinfo>
<title>&DISTRO; &DISTROVER; Release Notes</title>
<copyright>
<year>2004</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
<legalnotice id="legalnotice">
<para>Permission is granted to copy, distribute, and/or modify this
document under the terms of the GNU Free Documentation License, Version
1.2 or any later version published by the Free Software Foundation; with
no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is available at <ulink
url="http://www.gnu.org/licenses/fdl.html">http://www.gnu.org/licenses/fdl.html</ulink>.</para>
<para>This document may be copied and distributed in any medium, either
commercially or non-commercially, provided that the GNU Free
Documentation License (FDL), the copyright notices, and the license
notice saying the GNU FDL applies to the document are reproduced in all
copies, and that you add no other conditions whatsoever to those of the
GNU FDL.</para>
<para>&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>The Fedora trademark is a trademark of &FORMAL-RHI; in the United
States and other countries.</para>
<para>Linux is a registered trademark of Linus Torvalds.</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 at 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>
<sect1 id="s1-test" os="test">
<title>Release Notes Feedback Procedure</title>
<para>(This section will disappear when the final &DISTRO; release is
created.)</para>
<para>If you feel that these release notes could be improved in some way,
you can provide feedback directly to the author. If you see a URL in the
release notes that looks like this:</para>
<para>%%% https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=<replaceable><bug-number></replaceable> %%% </para>
<para>You can click on the URL and submit feedback on that particular
section of the release notes. Your feedback will be added as a comment to
an existing bug report.</para>
<para>If the section of the release notes that you have feedback for does
not have one of these URLs (or you are submitting a request for entirely
new content), you can click on the following link (this only works for the
HTML version, of course — the URL is much too long to include in the
text):</para>
<para><ulink
url="https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core&op_sys=Linux&version=devel&component=fedora-release&component_text=&rep_platform=All&priority=normal&bug_severity=normal&bug_status=NEW&assigned_to=&cc=&estimated_time=0.0&bug_file_loc=http%3A%2F%2F&short_desc=FC3%20release%20notes%20--%20&comment=Please%20add%20a%20descriptive%20phrase%20to%20the%20summary%2C%20and%20more%20in-depth%0D%0Adescription%20here%20%28be%20sure%20to%20note%20any%20arch-specific%20issues%29%3A%0D%0A%0D%0A&keywords=&dependson=&blocked=114398&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug">Click
here to submit new release notes feedback</ulink></para>
<para>If you would like to review the changes that have been already
submitted for this document, use the following link:</para>
<para><ulink
url="http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398">http://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=114398</ulink></para>
<para>As bugs are posted for the various parts of the release notes,
subsequent test versions of these release notes will contain links similar
to the one described earlier.</para>
<para>Thank you (in advance) for your feedback!</para>
</sect1>
<sect1 id="s1-intro">
<title>Introduction</title>
<para>The &PROJ; is an openly-developed project designed by &RH;, open for
general participation, led by a meritocracy, and following a set of
project objectives. The results from this project include &DISTRO;, a
complete, general-purpose operating system built exclusively from open
source software.</para>
<note>
<title>Note</title>
<para>&DISTRO; is not a supported product of &FORMAL-RHI;</para>
</note>
<para>For more information, refer to the &PROJ; overview later in this
document.</para>
<para>The following topics related to &DISTRO; &DISTROVER; are covered in
this document:</para>
<itemizedlist>
<listitem os="test">
<para>Release notes feedback procedure</para>
</listitem>
<listitem>
<para>Introduction (this section)</para>
</listitem>
<listitem>
<para>Hardware requirements</para>
</listitem>
<listitem>
<para>Overview of this release</para>
</listitem>
<listitem>
<para>Installation-related notes</para>
</listitem>
<listitem>
<para>Package-specific notes</para>
</listitem>
<listitem>
<para>Packages added/removed/deprecated</para>
</listitem>
<listitem>
<para>An overview of the &PROJ;</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="s1-hardware-reqs">
<title>Hardware Requirements</title>
<para>The following information represents the minimum hardware requirements
necessary to successfully install &DISTRO; &DISTROVER;.</para>
<note>
<title>Note</title>
<para>The compatibility/availability of other hardware components (such as
video and network cards) may be required for specific installation modes
and/or post-installation usage.</para>
</note>
<sect2>
<title>CPU Requirements</title>
<para>This section lists the CPU specifications required by &DISTRO;
&DISTROVER;.</para>
<note arch="x86">
<title><remark os="test">(x86)</remark> Note</title>
<para><remark os="test">(x86)</remark> The following CPU specifications
are stated in terms of Intel processors. Other processors (notably,
offerings from AMD, Cyrix, and VIA) that are compatible with and
equivalent to the following Intel processors may also be used with
&DISTRO;.</para>
</note>
<itemizedlist arch="x86">
<listitem>
<para><remark os="test">(x86)</remark> Minimum: Pentium-class</para>
<remark os="test">%%% <ulink
url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254</ulink>
%%%</remark>
<para><remark os="test">(x86)</remark> &DISTRO; &DISTROVER; is
optimized for Pentium 4 CPUs, but also supports earlier CPUs (such
as Pentium, Pentium Pro, Pentium II, Pentium III, and including AMD
and VIA variants). This approach has been taken because
[...3867 lines suppressed...]
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xerces-j</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xerces-j-devel</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xffm-icons</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-14-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-14-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-15-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-15-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-2-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-2-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-9-100dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-ISO8859-9-75dpi-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-base-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-cyrillic-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-libs-data</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-syriac-fonts</para>
</listitem>
<listitem arch="x86;x86_64">
<para><remark os="test">(x86;x86_64)</remark> xorg-x11-truetype-fonts</para>
</listitem>
</itemizedlist>
</sect2>
<sect2>
<title>Packages Deprecated</title>
<para>The following packages have been deprecated, and may be removed from
a future release of &DISTRO;:</para>
<itemizedlist>
<listitem>
<para>dbskkd-cdb — Only used by deprecated package
skkinput</para>
</listitem>
<listitem>
<para>FreeWnn — Only used by deprecated package
kinput2-canna-wnn6</para>
</listitem>
<listitem arch="x86">
<para><remark os="test">(x86)</remark> lilo — GRUB is the
recommended bootloader</para>
</listitem>
<listitem>
<para>miniChinput — IIIMF is the recommended input method</para>
</listitem>
<listitem>
<para>nabi — IIIMF is the recommended input method</para>
</listitem>
<listitem>
<para>ncpfs — No longer part of &DISTRO; profile</para>
</listitem>
<listitem>
<para>skkinput — IIIMF is the recommended input method</para>
</listitem>
<listitem>
<para>xcin — IIIMF is the recommended input method</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="s1-whatitis">
<title>An Overview of the &PROJ;</title>
<para>The goal of the &PROJ; is to work with the Linux community to build a
complete, general-purpose operating system exclusively from open source
software. Development will be done in a public forum. The project will
produce time-based releases of &DISTRO; about 2-3 times a year, with a
public release schedule. The &RH; engineering team will continue to
participate in building &DISTRO; and will invite and encourage 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.</para>
<para>For more information, refer to the &PROJ; website:</para>
<para><ulink
url="http://fedora.redhat.com/">http://fedora.redhat.com/</ulink></para>
<para>In addition to the website, the following mailing lists are
available:</para>
<itemizedlist>
<listitem>
<para>fedora-list at redhat.com — For users of &DISTRO;
releases</para>
</listitem>
<listitem>
<para>fedora-test-list at redhat.com — For testers of &DISTRO; test
releases</para>
</listitem>
<listitem>
<para>fedora-devel-list at redhat.com — For developers, developers,
developers</para>
</listitem>
<listitem>
<para>fedora-docs-list at redhat.com — For participants of the docs
project</para>
</listitem>
</itemizedlist>
<para>To subscribe to any of these lists, send an email with the word
"subscribe" in the subject to
<computeroutput><replaceable><listname></replaceable>-request</computeroutput>
(where
<computeroutput><replaceable><listname></replaceable></computeroutput>
is one of the above list names.)</para>
<para>NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list,
rhl-devel-list, or rhl-docs-list, your subscriptions have been
retained.</para>
<para>The &PROJ; also includes an IRC (Internet Relay Chat) channel. IRC is
a real-time, text-based form of communication. With it, you can have
conversations with multiple people in an open channel or chat with someone
privately one-on-one.</para>
<para>To talk with other &PROJ; participants via IRC, access freenode IRC
network. Initially, you can use <filename>irc.freenode.net</filename> as
the IRC server, although you may decide to select a server that is
geographically closer to you. Refer to the freenode website (<ulink
url="http://www.freenode.net/">http://www.freenode.net/</ulink>) for more
information. &PROJ; participants frequent the
<filename>#fedora</filename> channel, while &PROJ; developers can often be
found on the <filename>#fedora-devel</filename> channel. Some of the
larger projects may have their own channels as well; this information can
be found on the project pages.</para>
<para>NOTE: &RH; has no control over the Fedora IRC channels or their
content.</para>
</sect1>
<ackno>(
<emphasis arch="x86">x86</emphasis>
<emphasis arch="x86_64">x86_64</emphasis>
)</ackno>
</article>
--- NEW FILE RPM-GPG-KEY ---
The following public key can be used to verify RPM packages built and
signed by Red Hat, Inc. using `rpm -K' using the GNU GPG package.
Questions about this key should be sent to security at redhat.com.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
mQGiBDfqVDgRBADBKr3Bl6PO8BQ0H8sJoD6p9U7Yyl7pjtZqioviPwXP+DCWd4u8
HQzcxAZ57m8ssA1LK1Fx93coJhDzM130+p5BG9mYSWShLabR3N1KXdXQYYcowTOM
GxdwYRGr1Spw8QydLhjVfU1VSl4xt6bupPbWJbyjkg5Z3P7BlUOUJmrx3wCgobNV
EDGaWYJcch5z5B1of/41G8kEAKii6q7Gu/vhXXnLS6m15oNnPVybyngiw/23dKjS
ZVG7rKANEK2mxg1VB+vc/uUc4k49UxJJfCZg1gu1sPFV3GSa+Y/7jsiLktQvCiLP
lncQt1dV+ENmHR5BdIDPWDzKBVbgWnSDnqQ6KrZ7T6AlZ74VMpjGxxkWU6vV2xsW
XCLPA/9P/vtImA8CZN3jxGgtK5GGtDNJ/cMhhuv5tnfwFg4b/VGo2Jr8mhLUqoIb
E6zeGAmZbUpdckDco8D5fiFmqTf5+++pCEpJLJkkzel/32N2w4qzPrcRMCiBURES
PjCLd4Y5rPoU8E4kOHc/4BuHN903tiCsCPloCrWsQZ7UdxfQ5LQiUmVkIEhhdCwg
SW5jIDxzZWN1cml0eUByZWRoYXQuY29tPohVBBMRAgAVBQI36lQ4AwsKAwMVAwID
FgIBAheAAAoJECGRgM3bQqYOsBQAnRVtg7B25Hm11PHcpa8FpeddKiq2AJ9aO8sB
XmLDmPOEFI75mpTrKYHF6rkCDQQ36lRyEAgAokgI2xJ+3bZsk8jRA8ORIX8DH05U
lMH27qFYzLbT6npXwXYIOtVn0K2/iMDj+oEB1Aa2au4OnddYaLWp06v3d+XyS0t+
5ab2ZfIQzdh7wCwxqRkzR+/H5TLYbMG+hvtTdylfqIX0WEfoOXMtWEGSVwyUsnM3
Jy3LOi48rQQSCKtCAUdV20FoIGWhwnb/gHU1BnmES6UdQujFBE6EANqPhp0coYoI
hHJ2oIO8ujQItvvNaU88j/s/izQv5e7MXOgVSjKe/WX3s2JtB/tW7utpy12wh1J+
JsFdbLV/t8CozUTpJgx5mVA3RKlxjTA+On+1IEUWioB+iVfT7Ov/0kcAzwADBQf9
E4SKCWRand8K0XloMYgmipxMhJNnWDMLkokvbMNTUoNpSfRoQJ9EheXDxwMpTPwK
ti/PYrrL2J11P2ed0x7zm8v3gLrY0cue1iSba+8glY+p31ZPOr5ogaJw7ZARgoS8
BwjyRymXQp+8Dete0TELKOL2/itDOPGHW07SsVWOR6cmX4VlRRcWB5KejaNvdrE5
4XFtOd04NMgWI63uqZc4zkRa+kwEZtmbz3tHSdRCCE+Y7YVP6IUf/w6YPQFQriWY
FiA6fD10eB+BlIUqIw80VgjsBKmCwvKkn4jg8kibXgj4/TzQSx77uYokw1EqQ2wk
OZoaEtcubsNMquuLCMWijYhGBBgRAgAGBQI36lRyAAoJECGRgM3bQqYOhyYAnj7h
VDY/FJAGqmtZpwVp9IlitW5tAJ4xQApr/jNFZCTksnI+4O1765F7tA==
=3AHZ
-----END PGP PUBLIC KEY BLOCK-----
--- NEW FILE RPM-GPG-KEY-beta ---
The following public key can be used to verify RPM packages built and
signed by Red Hat, Inc. for this beta using `rpm -K' using the GNU GPG
package. Questions about this key should be sent to security at redhat.com.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
mQGiBDySTqsRBACzc7xuCIp10oj5B2PAV4XzDeVxprv/WTMreSNSK+iC0bEz0IBp
Vnn++qtyiXfH+bGIE9jqZgIEnpttWhUOaU5LhcLFzy+m8NWfngIFP9QfGmGAe9Gd
LFeAdhj4RmSG/vgr7vDd83Hz22dv403Ar/sliWO4vDOrMmZBG57WGYTWtwCgkMsi
UUQuJ6slbzKn82w+bYxOlL0EAIylWJGaTkKOTL5DqVR3ik9aT0Dt3FNVYiuhcKBe
II4E3KOIVA9kO8in1IZjx2gs6K2UV+GsoAVANdfKL7l9O+k+J8OxhE74oycvYJxW
QzCgXMZkNcvW5wyXwEMcr6TVd/5BGztcMw8oT3/l2MtAEG/vn1XaWToRSO1XDMDz
+AjUA/4m0mTkN8S4wjzJG8lqN7+quW3UOaiCe8J3SFrrrhE0XbY9cTJI/9nuXHU1
VjqOSmXQYH2Db7UOroFTBiWhlAedA4O4yuK52AJnvSsHbnJSEmn9rpo5z1Q8F+qI
mDlzriJdrIrVLeDiUeTlpH3kpG38D7007GhXBV72k1gpMoMcpbQ3UmVkIEhhdCwg
SW5jLiAoQmV0YSBUZXN0IFNvZnR3YXJlKSA8cmF3aGlkZUByZWRoYXQuY29tPohX
BBMRAgAXBQI8l5p/BQsHCgMEAxUDAgMWAgECF4AACgkQ/TcmiYl9oHqdeQCfZjw4
F9sir3XfRAjVe9kYNcQ8hnIAn0WgyT7H5RriWYTOCfauOmd+cAW4iEYEEBECAAYF
AjyXmqQACgkQIZGAzdtCpg5nDQCfepuRUyuVJvhuQkPWySETYvRw+WoAnjAWhx6q
0npMx4OE1JGFi8ymKXktuQENBDySTq4QBADKL/mK7S8E3synxISlu7R6fUvu07Oc
RoX96n0Di6T+BS99hC44XzHjMDhUX2ZzVvYS88EZXoUDDkB/8g7SwZrOJ/QE1zrI
JmSVciNhSYWwqeT40Evs88ajZUfDiNbS/cSC6oui98iS4vxd7sE7IPY+FSx9vuAR
xOa9vBnJY/dx0wADBQQAosm+Iltt2uigC6LJzxNOoIdB5r0GqTC1o5sHCeNqXJhU
ExAG8m74uzMlYVLOpGZi4y4NwwAWvCWC0MWWnnu+LGFy1wKiJKRjhv5F+WkFutY5
WHV5L44vp9jSIlBCRG+84jheTh8xqhndM9wOfPwWdYYu1vxrB8Tn6kA17PcYfHSI
RgQYEQIABgUCPJJergAKCRD9NyaJiX2geiCPAJ4nEM4NtI9Uj8lONDk6FU86PmoL
yACfb68fBd2pWEzLKsOk9imIobHHpzE=
=gpIn
-----END PGP PUBLIC KEY BLOCK-----
--- NEW FILE RPM-GPG-KEY-fedora ---
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)
mQGiBD+dnTsRBACwnlz4AhctOLlVBAsq+RaU82nb5P3bD1YJJpsAce1Ckd2sBUOJ
D11NUCqH8c7EctOquOZ5zTcWxHiWWbLyKQwUw2SUvnWa5SSbi8kI8q9MTPsPvhwt
gMrQMLenMO+nsrxrSaG6XcD+ssfJNxC7NQVCQAj3pvvg9rKi3ygsM7CXHwCghgsq
X6TOr55HE90DbEsoq3b/jjsD/i8aIZ6urUgrpAkQslcakXdJLKgSdwjRUgVZgvYZ
b7kAx1iPq0t/AhB3NJw3zW4AAKJohGg3xj5K4V8PJEZrSIpoRYlF43Kqlfu2p5gh
WT89SP4YAlWPeTqf0+dTYUYz3b144k2ZFOdRuXIRxunoYNAUr9oMrxBXbJ/eY+0U
QX3pBACYzKizyY4JJgd0zFJmNkcdK9nzcm+btYFnYQo33w5GSE686UNr+9yiXt9t
mPRvNEbj3u+xoAX8B/5k3aZ5NbUhV64/VcKlUdRIxNlFCG7I9KgxeHWAYwi7yqOG
XM3T/v6o7GLdQEB0ChFqS7kUlqmwLV+C3QhlrFe/Cuk26i+Q6rQiRmVkb3JhIFBy
b2plY3QgPGZlZG9yYUByZWRoYXQuY29tPohbBBMRAgAbBQI/nZ07BgsJCAcDAgMV
AgMDFgIBAh4BAheAAAoJELRCadBPKm/S2PAAnRTlhorITphab+oxAHtbxZF9BVyD
AJ9WOVaZUG53IWWIAXOGv3j/cmr3lohGBBMRAgAGBQI/nZ22AAoJECGRgM3bQqYO
R5QAoIp1G+omVktq/snxpmz5UeHjlSYjAKCRr/ea/L7S7ZTxB18cf1TYfad1x4hG
BBARAgAGBQI/ntjgAAoJECnVuiSN9W0FUSUAoJnrone4J0o1HMkRz+6g9KVuO2Fy
AJ0XyebOzVmI9U5OyOfnNmYV0wnQcrkBDQQ/nZ08EAQAugOfLWJbKwMA9vg2mJU5
94TZU0HRJkx/fqYhx0YxWWRpzplrEyvcDXuYcWi1Hwh0tD86T4fR5GV6joWiWClz
D+Hwhhb6gcSdeSGlGLlZAvWYtFSHWiv+3LaI9w8Vtczl99Bh2WiMDNDDGw0RQg6Z
aftldLSe4j1pffpFGQ8SuisAAwUEAKVxqLT7fC5xQ6oclcZ+PhoDlePQ1BiTS7tu
GM07bFF4nNvY91LL7S31pooz3XbGSWP8jxzSv1Fw35YhSmWGOBOEXluqMbVQGJJ5
m8fqJOjC0imbfeWgr/T7zLrJeiljDxvX+6TyawyWQngF6v1Hq6FRV0O0bOp9Npt5
zqCbDGs/iEYEGBECAAYFAj+dnTwACgkQtEJp0E8qb9L//gCcDVYnDegNCOxDn1se
dDwxw+0h8OcAn1CZHof15QqxnTwEnvwF2QeOI5dn
=mJAx
-----END PGP PUBLIC KEY BLOCK-----
--- NEW FILE RPM-GPG-KEY-fedora-rawhide ---
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)
mQGiBD+doUwRBADudl/P8RqkzaHstvwbT93MByo7yX+xHcr0FaVAoG9Qfn+2O0qy
nbNIz9BoieCx9zfgruBBaYjcT1p7QjdyfvF3wLq6ak84ne+QW91rctzqG8JqPhSB
e34L7T0JnsUdiLfnfq895Hy67SYTOcJ6sN1Eg/eKYPP0CHKL9BY9atGRZwCg14Kh
va6OSfIDyV6DNnfYF+cUSwsEALARvclTS8lLL+4sgZthg4D4Od4mYayr0QpKpoBI
0RxOj26v038unOGqEjjqX/F36PwQv6wt6DmaGd9atQ/VUqW4cnKmNfaxJVAqznqW
q80FKzTPH/JC/20v/5xx0FoxEVSCoKs2YPdXEQfEUAzNG9JC4GHNCxt2Gtnt4o5l
sn15BADepds5sa/ptu//hJcYhrvcgzUJQR/JQdDbtK+Rzrvi2oZQFZUHzCVVxxfE
0AULmX5bEC08nAGtp418ceeo1PdqlcVE+kaxuFpPgto/Sd1FvJW4P2B1a7rcUjGc
BarOMVY8QpFZs5iIlkzZdPns1BCijWlhltOiyrdxyNrM49hjlrRGRmVkb3JhIFBy
b2plY3QgYXV0b21hdGVkIGJ1aWxkIHNpZ25pbmcga2V5ICgyMDAzKSA8cmF3aGlk
ZUByZWRoYXQuY29tPohbBBMRAgAbBQI/naFMBgsJCAcDAgMVAgMDFgIBAh4BAheA
AAoJEOE4XU4c3byppW8An385Vt7LXSAIHqdH85QTCH512cr+AJ9vB4inXB6lxOoq
sbnKY0HG4Sr1IIhGBBMRAgAGBQI/naOPAAoJELRCadBPKm/SFMgAn2/FfBhf2Yov
j3gH8Z1t+bbsHRkLAJ94tjdweTZmfZsQZ7YaDXpeJ2iY+4hGBBARAgAGBQI/ntkG
AAoJECnVuiSN9W0Fi5gAn3wSpemY+8rq8aFfRLEumrSksfUoAJ95YyaGdRXv+fWt
KfPJSNTqsqhiKA==
=umuG
-----END PGP PUBLIC KEY BLOCK-----
--- NEW FILE RPM-GPG-KEY-fedora-test ---
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)
mQGiBD+do/cRBACAF7Gv91v32uUrT4nZe+qKgLl59HmtvmaOzT4lInrF95Sget7p
2TpnIqh5H0x0VGpdoeNfHvlXCw+aP50mTJv91BYmLfelkTzokqpEU5YpqGOqa5BV
jelnoK1VKOcXMB28d79Gz9tn7friZN4SnyWbcSIA4C3dHNhsjifIYf0rywCg3y19
3N6jODa0VSGeeEb4whE2xccD/i/rqk0MQmW6td2Dz2jTBaHxyf7FIcH18YDtwraD
otBRxqGkTVyFGc1q7ZTrRsbzdjIfxbp2C6GT2VJ5kHuRm9jf7JdW5fOhun+oLimR
erTlrPmgz8qQRcqUm6fkmUsYufL1u7DdyfxX7jI2ngkbAR+CsZ8Cj5JhBMeAXc/D
WWhPA/4mzZ70hn1OrGLokzxNr4O7u1+n0thsxGN0qfuTNGIc09UKCoAN42he7Qjs
kIqiE7gLtLzx8elxVOK19tNcaAiLoqmtxlLQqB03pLy4V0tMP9QcWQETbc67qTd1
zASiefGjf364j4lQd+X9AqdyhUrnax3UgPD5IxilBp92Cw7Qi7QzRmVkb3JhIFBy
b2plY3QgKFRlc3QgU29mdHdhcmUpIDxyYXdoaWRlQHJlZGhhdC5jb20+iFsEExEC
ABsFAj+do/cGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQ2oTL1DDJ7Pgh8QCgqNNs
b7xdW+UhzyZw+DEAQF6e+q4AmwVus4u9REyd/aigK2RvrdtcsNy0iEYEExECAAYF
Aj+dpBoACgkQtEJp0E8qb9Ji4QCfanY0CXnRwtBnm8GEMRNqgfGgcc0AnRunlejp
JRxGPaRsmY/11stYll32iEYEEBECAAYFAj+e2SIACgkQKdW6JI31bQWWNQCfTKcX
/7lerpwIVHcAILDduz9qxssAn1t46ERJ9EqsxJxSFlN7oBPyNkt6
=R9He
-----END PGP PUBLIC KEY BLOCK-----
--- NEW FILE RPM-GPG-KEY-rawhide ---
By using `rpm -K' and the GNU GPG package, the following public key can be
used to verify RPM packages built and signed by Red Hat, Inc. for rawhide
and testing. Questions about this key should be sent to
security at redhat.com.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.7 (GNU/Linux)
mQGiBD9DmVMRBACW9LRPUtKnUTNeSQN5huiPA0+d0hGLTEG1kkUj47zWC3RXZ1Xh
c/6yzWOrPk85Q7ys/dGoLLqsfekkxDVipUE0iS+47VMYgm531x4cd2oKnQb3Z/2R
3A6kjDkc2KyTmfOsZ8DTdL76u81Rnv6MCQjXTJCFOQzv3yxmn6ZDhOoSkwCg24J2
Qh0zuvvtyfNMsj+S8ksase8D/1qQgcURZDYZkaxrQSsdyZWsqb4NT51snXG5wE4L
Yh1VGH26YU/kY7YxU5TPo8kbQTztkqaoFHk/O6zx+Q/iS8Izv2ByTsZv0F/Weym7
Fyf+x+PTA7oDvV9hN/aJy/UPF+t4GRrsEV2mH8Ee3hIZGKSWwTwZZh+JyfIcqkyU
zwY9BACLOZ8xZjHzU4MjZw2qgWemr96Zyr2foGl0+2G1STnluWf24//nNWBiLFuA
txucItsppnUM0qB5RZ69N4c9MOmCZkBoahP3Q30qAsaAN4RaaE6AG7Yms0wtPW3m
qzzhcuCtRAumXqA/oQWYqmHaEwUPenJaxut5rasApm2r5QxaQbRFUmVkIEhhdCwg
SW5jLiBhdXRvbWF0ZWQgYnVpbGQgc2lnbmluZyBrZXkgKDIwMDMpIDxyYXdoaWRl
QHJlZGhhdC5jb20+iFsEExECABsFAj9DmVMGCwkIBwMCAxUCAwMWAgECHgECF4AA
CgkQlM1XQuQY46oixwCfUKmLRHSIBd1FbGTaR5ARBfSsK+MAn1BfxKyahkQ0ScN7
9RNaYei9kxGIiEYEExECAAYFAj9DvtMACgkQIZGAzdtCpg5exACeJlj9DExab5AK
C0eQHr8td+WRJ0QAnRNDGXQCBENRgFNgcecDMAr7P6se
=LmwA
-----END PGP PUBLIC KEY BLOCK-----
--- NEW FILE autorun-template ---
#!/bin/sh
#
# Autorun script for Red Hat Linux
# Copyright (c) 1999-2002 Red Hat, Inc.
dir=$(echo $0 |sed 's/autorun//')
cd $dir
tree=$(pwd)
# Change directories so we can unmount the CD-ROM Drive
cd /
exec /usr/bin/system-cdinstall-helper $tree
--- NEW FILE eula.py ---
from gtk import *
import string
import gtk
import gobject
import sys
import functions
import rhpl.iconv
import os
##
## I18N
##
import gettext
gettext.bindtextdomain ("firstboot", "/usr/share/locale")
gettext.textdomain ("firstboot")
_=gettext.gettext
class childWindow:
#You must specify a runPriority for the order in which you wish your module to run
runPriority = 15
moduleName = (_("License Agreement"))
def launch(self, doDebug = None):
self.doDebug = doDebug
if self.doDebug:
print "initializing eula module"
self.vbox = gtk.VBox()
self.vbox.set_size_request(400, 200)
msg = (_("License Agreement"))
title_pix = functions.imageFromFile("workstation.png")
internalVBox = gtk.VBox()
internalVBox.set_border_width(10)
internalVBox.set_spacing(5)
textBuffer = gtk.TextBuffer()
textView = gtk.TextView()
textView.set_editable(gtk.FALSE)
textSW = gtk.ScrolledWindow()
textSW.set_shadow_type(gtk.SHADOW_IN)
textSW.set_policy(gtk.POLICY_AUTOMATIC, gtk.POLICY_AUTOMATIC)
textSW.add(textView)
lang = os.environ["LANG"]
if len(string.split(lang, ".")) > 1:
lang = string.split(lang, ".")[0]
path = "/usr/share/eula/eula.%s" % lang
if not os.access(path, os.R_OK):
#Try to open the translated eula
lines = open("/usr/share/eula/eula.en_US").readlines()
else:
#If we don't have a translation for this locale, just open the English one
lines = open(path).readlines()
iter = textBuffer.get_iter_at_offset(0)
for line in lines:
textBuffer.insert(iter, line)
textView.set_buffer(textBuffer)
self.okButton = gtk.RadioButton(None, (_("_Yes, I agree to the License Agreement")))
self.noButton = gtk.RadioButton(self.okButton, (_("N_o, I do not agree")))
self.noButton.set_active(gtk.TRUE)
internalVBox.pack_start(textSW, gtk.TRUE)
internalVBox.pack_start(self.okButton, gtk.FALSE)
internalVBox.pack_start(self.noButton, gtk.FALSE)
self.vbox.pack_start(internalVBox, gtk.TRUE, 5)
return self.vbox, title_pix, msg
def apply(self, notebook):
if self.okButton.get_active() == gtk.TRUE:
return 0
else:
dlg = gtk.MessageDialog(None, 0, gtk.MESSAGE_QUESTION, gtk.BUTTONS_NONE,
(_("Do you want to reread or reconsider the Licence Agreement? "
"If not, please shut down the computer and remove this "
"product from your system. ")))
dlg.set_position(gtk.WIN_POS_CENTER)
dlg.set_modal(gtk.TRUE)
continueButton = dlg.add_button(_("_Reread license"), 0)
shutdownButton = dlg.add_button(_("_Shut down"), 1)
continueButton.grab_focus()
rc = dlg.run()
dlg.destroy()
if rc == 0:
return None
elif rc == 1:
if self.doDebug:
print "shut down system"
os.system("/sbin/halt")
return None
--- NEW FILE eula.txt ---
LICENSE AGREEMENT
FEDORA(TM) CORE 3
This agreement governs the download, installation or use of the
Software (as defined below) and any updates to the Software,
regardless of the delivery mechanism. The Software is a collective
work under U.S. Copyright Law. Subject to the following terms, Fedora
Project grants to the user ("User") a license to this collective work
pursuant to the GNU General Public License. By downloading,
installing or using the Software, User agrees to the terms of this
agreement.
1. THE SOFTWARE. Fedora Core (the "Software") is a modular Linux
operating system consisting of hundreds of software components.
The end user license agreement for each component is located in
the component's source code. With the exception of certain image
files containing the Fedora trademark identified in Section 2
below, the license terms for the components permit User to copy,
modify, and redistribute the component, in both source code and
binary code forms. This agreement does not limit User's rights
under, or grant User rights that supersede, the license terms of
any particular component.
2. INTELLECTUAL PROPERTY RIGHTS. The Software and each of its
components, including the source code, documentation, appearance,
structure and organization are copyrighted by Fedora Project and
others and are protected under copyright and other laws. Title to
the Software and any component, or to any copy, modification, or
merged portion shall remain with the aforementioned, subject to
the applicable license. The "Fedora" trademark is a trademark of
Red Hat, Inc. ("Red Hat") in the U.S. and other countries and is
used by permission. This agreement permits User to distribute
unmodified copies of Software using the Fedora trademark on the
condition that User follows Red Hat's trademark guidelines located
at http://fedora.redhat.com/legal. User must abide by these
trademark guidelines when distributing the Software, regardless of
whether the Software has been modified. If User modifies the
Software, then User must replace all images containing the
"Fedora" trademark. Those images are found in the anaconda-images
and the fedora-logos packages. Merely deleting these files may
corrupt the Software.
3. LIMITED WARRANTY. Except as specifically stated in this agreement
or a license for a particular component, TO THE MAXIMUM EXTENT
PERMITTED UNDER APPLICABLE LAW, THE SOFTWARE AND THE COMPONENTS
ARE PROVIDED AND LICENSED "AS IS" WITHOUT WARRANTY OF ANY KIND,
EXPRESSED OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF
MERCHANTABILITY, NON-INFRINGEMENT OR FITNESS FOR A PARTICULAR
PURPOSE. Neither the Fedora Project nor Red Hat warrants that the
functions contained in the Software will meet User's requirements
or that the operation of the Software will be entirely error free
or appear precisely as described in the accompanying
documentation. USE OF THE SOFTWARE IS AT USER'S OWN RISK.
4. LIMITATION OF REMEDIES AND LIABILITY. TO THE MAXIMUM EXTENT
PERMITTED BY APPLICABLE LAW, FEDORA PROJECT AND RED HAT WILL NOT
BE LIABLE TO USER FOR ANY DAMAGES, INCLUDING INCIDENTAL OR
CONSEQUENTIAL DAMAGES, LOST PROFITS OR LOST SAVINGS ARISING OUT OF
THE USE OR INABILITY TO USE THE SOFTWARE, EVEN IF FEDORA PROJECT
OR RED HAT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
5. EXPORT CONTROL. As required by U.S. law, User represents and
warrants that it: (a) understands that the Software is subject to
export controls under the U.S. Commerce Department's Export
Administration Regulations ("EAR"); (b) is not located in a
prohibited destination country under the EAR or U.S. sanctions
regulations (currently Cuba, Iran, Iraq, Libya, North Korea, Sudan
and Syria); (c) will not export, re-export, or transfer the
Software to any prohibited destination, entity, or individual
without the necessary export license(s) or authorizations(s) from
the U.S. Government; (d) will not use or transfer the Software for
use in any sensitive nuclear, chemical or biological weapons, or
missile technology end-uses unless authorized by the
U.S. Government by regulation or specific license; (e) understands
and agrees that if it is in the United States and exports or
transfers the Software to eligible end users, it will, as required
by EAR Section 741.17(e), submit semi-annual reports to the
Commerce Department's Bureau of Industry & Security (BIS), which
include the name and address (including country) of each
transferee; and (f) understands that countries other than the
United States may restrict the import, use, or export of
encryption products and that it shall be solely responsible for
compliance with any such import, use, or export restrictions.
6. GENERAL. If any provision of this agreement is held to be
unenforceable, that shall not affect the enforceability of the
remaining provisions. This agreement shall be governed by the
laws of the State of North Carolina and of the United States,
without regard to any conflict of laws provisions, except that the
United Nations Convention on the International Sale of Goods shall
not apply.
Copyright (C) 2003, 2004 Fedora Project. All rights reserved. "Red Hat"
and "Fedora" are trademarks of Red Hat, Inc. "Linux" is a registered
trademark of Linus Torvalds. All other trademarks are the property of
their respective owners.
--- NEW FILE fedora-devel.repo ---
[development]
name=Fedora Core $releasever - Development Tree
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-rawhide
enabled=0
--- NEW FILE fedora-release.spec ---
%define builtin_release_version @VERSION@
%define builtin_release_name @RELNAME@
%define real_release_version %{?release_version}%{!?release_version:%{builtin_release_version}}
%define real_release_name %{?release_name}%{!?release_name:%{builtin_release_name}}
Summary: Fedora Core release file
Name: fedora-release
Version: %{real_release_version}
Release: 9
Copyright: GFDL
Group: System Environment/Base
Source: fedora-release-%{builtin_release_version}- at RELARCH@.tar.gz
Obsoletes: rawhide-release
Obsoletes: redhat-release
Obsoletes: indexhtml
Provides: redhat-release
Provides: indexhtml
BuildRoot: %{_tmppath}/fedora-release-root
ExclusiveArch: @RELARCH@
%description
Fedora Core release file
%prep
%setup -q -n fedora-release- at VERSION@- at RELARCH@
%build
python -c "import py_compile; py_compile.compile('eula.py')"
%install
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT/etc
echo "Fedora Core release %{real_release_version} (%{real_release_name})" > $RPM_BUILD_ROOT/etc/fedora-release
cp $RPM_BUILD_ROOT/etc/fedora-release $RPM_BUILD_ROOT/etc/issue
echo "Kernel \r on an \m" >> $RPM_BUILD_ROOT/etc/issue
cp $RPM_BUILD_ROOT/etc/issue $RPM_BUILD_ROOT/etc/issue.net
echo >> $RPM_BUILD_ROOT/etc/issue
ln -s fedora-release $RPM_BUILD_ROOT/etc/redhat-release
mkdir -p $RPM_BUILD_ROOT/usr/share/eula $RPM_BUILD_ROOT/usr/share/firstboot/modules
cp -f eula.txt $RPM_BUILD_ROOT/usr/share/eula/eula.en_US
cp -f eula.py $RPM_BUILD_ROOT/usr/share/firstboot/modules/eula.py
mkdir -p -m 755 $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML
cp -ap img css \
$RPM_BUILD_ROOT/%{_defaultdocdir}/HTML
for file in indexhtml-*.html ; do
newname=`echo $file | sed 's|indexhtml-\(.*\)-\(.*\).html|index-\2.html|g'`
install -m 644 $file $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/$newname || :
done
mv -f $RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/index-en.html \
$RPM_BUILD_ROOT/%{_defaultdocdir}/HTML/index.html || :
mkdir -p -m 755 $RPM_BUILD_ROOT/etc/sysconfig/rhn
mkdir -p -m 755 $RPM_BUILD_ROOT/etc/yum.repos.d
install -m 644 sources $RPM_BUILD_ROOT/etc/sysconfig/rhn/sources
for file in fedora*repo ; do
install -m 644 $file $RPM_BUILD_ROOT/etc/yum.repos.d
done
%clean
rm -rf $RPM_BUILD_ROOT
# If this is the first time a package containing /etc/issue
# is installed, we want the new files there. Otherwise, we
# want %config(noreplace) to take precedence.
%triggerpostun -- redhat-release < 7.1.93-1
for I in issue issue.net; do
if [ -f /etc/$I.rpmnew ] ; then
mv -f /etc/$I /etc/$I.rpmsave
mv -f /etc/$I.rpmnew /etc/$I
fi
done
%files
%defattr(-,root,root)
%attr(0644,root,root) /etc/fedora-release
/etc/redhat-release
%dir /etc/sysconfig/rhn
%dir /etc/yum.repos.d
%config(noreplace) /etc/sysconfig/rhn/sources
%config(noreplace) /etc/yum.repos.d/*
%doc R*
%doc eula.txt GPL autorun-template
%config %attr(0644,root,root) /etc/issue
%config %attr(0644,root,root) /etc/issue.net
/usr/share/firstboot/modules/eula.py
/usr/share/eula/eula.en_US
%{_defaultdocdir}/HTML
--- NEW FILE fedora-updates-testing.repo ---
[updates-testing]
name=Fedora Core $releasever - $basearch - Test Updates
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/$releasever/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/updates-testing-fc$releasever
enabled=0
gpgcheck=1
--- NEW FILE fedora-updates.repo ---
[updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/updates-released-fc$releasever
enabled=1
gpgcheck=1
--- NEW FILE fedora.repo ---
[base]
name=Fedora Core $releasever - $basearch - Base
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-$releasever
enabled=1
gpgcheck=1
--- 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 © 2004 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_logo.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/projects/" id="link-internal"><img src="img/header-projects.png" alt=" ">Projects</a>
<a href="http://fedora.redhat.com/about/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">Docs</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/projects/" id="link-internal">Projects</a></li>
<li><a href="http://fedora.redhat.com/participate/" id="link-internal">Participate</a></li>
<li><a href="http://fedora.redhat.com/about/" id="link-internal">About</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/$ARCH/
#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.
- Previous message (by thread): release-notes/FC4/css - New directory
- Next message (by thread): release-notes/FC4/img corner-bl.png, NONE, 1.1 corner-br.png, NONE, 1.1 corner-tl.png, NONE, 1.1 corner-tr.png, NONE, 1.1 header-download.png, NONE, 1.1 header-faq.png, NONE, 1.1 header-fedora_logo.png, NONE, 1.1 header-projects.png, NONE, 1.1
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Fedora-docs-commits
mailing list