Archive:FedoraDocs/ReleaseNotes/Core4Test2

Release Notes for Fedora Core 4 test2

This page currently mirrors and potentially supplements the release notes shipped with Fedora Core 4 test2. We are discussing the idea of using a Wiki within the release notes creation process, which would still need to be converted to DocBook and packaged with the release. This first usage will let us test this idea.

For details on how to edit this document, refer to FedoraDocs/RelNotes/RelNotesProcess.

If you are not a developer and see a bug in the document such as incorrect information or unclear writing, or have an enhancement request, use this pre-filled bugzilla request .

When you use this pre-filled bug, your report blocks bugzilla #151189, which is a master tracker for Fedora Core release notes work. This helps us keep track of your report so that it is not lost.

Fedora Core 4test2 Release Notes

Copyright (c) 2005 Red Hat, Inc.

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 [1] http://www.gnu.org/licenses/fdl.html.

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.

Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries.

The Fedora trademark is a trademark of Red Hat, Inc. in the United States and other countries.

Linux is a registered trademark of Linus Torvalds.

All other trademarks and copyrights referred to are the property of their respective owners.

The GPG fingerprint of the "Fedora Project <fedora@redhat.com>" key is:

CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2

---

Introduction

The Fedora Project is an openly-developed project designed by Red Hat, open for general participation, led by a meritocracy, and following a set of project objectives. The results from this project include Fedora Core, a complete, general-purpose operating system built exclusively from open source software.

NOTE: Fedora Core is not a supported product of Red Hat, Inc.

For more information, refer to the Fedora Project overview later in this document.

The following topics related to Fedora Core 4test2 are covered in this document:

• Introduction (this section)
• Hardware requirements
• Overview of this release
• Installation-related notes
• Package-specific notes
• Packages added/removed/deprecated
• An overview of the Fedora Project

Hardware Requirements

The following information represents the minimum hardware requirements necessary to successfully install Fedora Core 4test2.

Note

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.

CPU Requirements

This section lists the CPU specifications required by Fedora Core 4test2.

Note

The following CPU specifications are stated in terms of Intel processors. Other processors (notably, offerings from AMD, Cyrix, and VIA) that are compatible with and equivalent to the following Intel processors may also be used with Fedora Core.

• Minimum: Pentium-class

Fedora Core 4test2 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 Pentium-class optimizations actually result in reduced performance for non-Pentium-class processors, and Pentium 4 scheduling is sufficiently different (while making up the bulk of today's processors) to warrant this change.

• Recommended for text-mode: 200 MHz Pentium-class or better

• Recommended for graphical: 400 MHz Pentium II or better

Hard Disk Space Requirements

This section lists the disk space required to install Fedora Core 4test2.

Note

The disk space requirements listed below represent the disk space taken up by Fedora Core 4test2 after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system.

In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation.

Also, keep in mind that additional space will be required for any user data, and at least 5% free space should be maintained for proper system operation.

• Custom Installation (Minimal): 620MB
• Server: 1.1GB
• Personal Desktop: 2.3GB
• Workstation: 3.0GB
• Custom Installation (Everything): 6.9GB

Memory Requirements

This section lists the memory required to install Fedora Core 4test2.

• Minimum for text-mode: 64MB
• Minimum for graphical: 192MB
• Recommended for graphical: 256MB

Overview of This Release

The following list highlights certain new features of Fedora Core 4test2:

• GCC 4.0
• GNOME 2.10
• KDE 3.4
• Native Eclipse 3.1M5
• MySQL 4.1
• PHP 5.0

• SELinux -- New daemons have been added to the targeted policy For

more information, refer to the SELinux FAQ at http://fedora.redhat.com/docs/selinux-faq/ .

• amanda
• apache
• chkpwd
• cups
• dhcpc
• dhcpd
• dictd
• dovecot
• fingerd
• ftpd
• howl
• i18n_input
• ifconfig
• init
• initrc
• inetd
• innd
• kerberos
• ktalkd
• ldconfig
• login
• lpd
• mailman
• modutil
• mta
• mysqld
• NetworkManager
• named
• nscd
• ntpd
• portmap
• postgresql
• privoxy
• radius
• radvd
• rlogind
• rpcd
• rshd
• rsync
• samba
• slapd
• snmpd
• squid
• stunnel
• syslogd
• telnetd
• tftpd
• winbind
• ypbind
• ypserv
• zebra

Installation-Related Notes

This section outlines anything noteworthy that is related to Anaconda (the Fedora Core installation program) and installing Fedora Core 4test2 in general.

Note

If you intend to download the Fedora Core 4test2 DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2GB in size. For example, wget will exit with a File size limit exceeded error.

The curl and ncftpget file downloading tools do not have this limitation, and can successfully download files larger than 2GB.

Bittorrent is another method for downloading large files.

Anaconda Notes

• The Fedora Core installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. Red Hat recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs). To use this test, type linux mediacheck at the boot: prompt.

• Memory testing may be performed prior to installing Fedora Core by entering memtest86 at the boot: prompt. This causes the Memtest86 standalone memory testing software to run. Memtest86 memory testing continues until the Esc key is pressed.

NOTE: You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use this feature.

• Fedora Core 4test2 supports graphical FTP and HTTP installations. However, due to the necessity of containing the installer image in RAM, only systems with more than 128MB of RAM (or systems booted from CD-ROM 1, which contains the installer image) can use the graphical installer. Systems with 128MB or less will continue to use the text-based installer.

Installation-Related Issues

• Certain hardware configurations (particularly those with LCD displays) may experience problems while starting the Fedora Core installation program. In these instances, restart the installation, and add the "nofb" option to the boot command line.

NOTE: Chinese, Japanese, and Korean graphical installations started using the "nofb" option will start in English, and then switch to the appropriate language once the graphical phase of the installation process begins.

• Some Sony VAIO(R) 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:

pci=off ide1=0x180,0x386

This option allows the installation to proceed normally; any devices not detected due to the use of this option will be configured the first time Fedora Core is booted.

• Serial mice are known to be inoperative during installation. However, there are indications that serial mice work properly in X after the installation has completed. Refer to bug 119474 for more information:

[6] http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474

• There have been issues observed when upgrading Red Hat Linux 7.<x>, 8.0, 9, and Fedora Core 1 systems running Ximian GNOME. The issue is caused by version overlap between the official Red Hat Linux RPMs (or the ones from the Fedora Project) and the Ximian RPMs. This configuration is not supported. You have several choices in resolving this issue:

1) You may remove Ximian GNOME from your system prior to upgrading to Fedora Core.

2) You may upgrade your system, and then immediately reinstall Ximian GNOME.

3) You may upgrade your system, and then immediately remove all remaining Ximian RPMs, replacing them with the corresponding Fedora Core RPMs.

You must resolve the version overlap using one of the above choices. Failure to do so will result in an unstable GNOME configuration.

Package-Specific Notes

The following sections contain information regarding packages that have undergone significant changes for Fedora Core 4test2. For easier access, they are organized using the same groups used in Anaconda.

Base

This section contains information related to basic system components.

slocate database

The database needed by the locate utility is no longer created by default. Enable the database creation by setting DAILY_UPDATE to "yes" in /etc/updatedb.conf if you want to use locate.

openssh

The version of OpenSSH in Fedora Core 4test2 contains OpenSSH 3.9 includes strict permission and ownership checks for the ~/.ssh/config file. These checks mean that ssh will exit if this file does not have appropriate ownership and permissions.

Therefore, make sure that ~/.ssh/config is owned by the owner of ~/, and that its permissions are set to mode 600.

In addition, OpenSSH is no longer configured to request X11 forwarding by default when connecting to servers. To enable X11 forwarding, the -X or -Y option must be specified, or the ForwardX11 option must be enabled in the ~/.ssh/config file.

The behavior of ssh clients that are invoked with the -X flag has changed. In OpenSSH 3.8 and later, X11 forwarding is performed in a way that applications run as untrusted clients by default. Previously, X11 forwarding was performed so that applications always ran as trusted clients. Some applications may not function properly when run as untrusted clients. To forward X11 so that applications are run as trusted clients, invoke ssh with the -Y flag instead of the -X flag, or set ForwardX11Trusted in the ~/.ssh/config file.

Core

This section contains the most elemental components of Fedora Core, including the kernel.

• In order to eliminate the redundancy inherent in providing a separate package for the kernel source code when that source code already exists in the kernel's .src.rpm file, Fedora Core 4test2 no longer includes the kernel-source package. Users that require access to the kernel sources can find them in the kernel .src.rpm file. To create an exploded source tree from this file, perform the following steps (note that <version> refers to the version specification for your currently-running kernel):

1. Obtain the kernel-<version>.src.rpm file from one of the following sources:

• The SRPMS directory on the appropriate "SRPMS" CD iso image

• The FTP site where you got the kernel package

• By running the following command:

up2date --get-source kernel

2. Install kernel-<version>.src.rpm (given the default RPM configuration, the files this package contains will be written to /usr/src/redhat/)

3. Change directory to /usr/src/redhat/SPECS/, and issue the following command:

rpmbuild -bp --target=<arch> kernel.spec

(Where <arch> is the desired target architecture.)

On a default RPM configuration, the kernel tree will be located in /usr/src/redhat/BUILD/.

4. In resulting tree, the configurations for the specific kernels shipped in Fedora Core 4test2 are in the /configs/ directory. For example, the i686 SMP configuration file is named /configs/kernel-<version>-i686-smp.config. Issue the following command to place the desired configuration file in the proper place for building:

cp <desired-file> ./.config

5. Issue the following command:

make oldconfig

You can then proceed as usual.

Note

An exploded source tree is not required to build kernel modules against the currently in-use kernel.

For example, to build the foo.ko module, create the following file (named Makefile) in the directory containing the foo.c file:

obj-m  := foo.o

KDIR  := /lib/modules/$(shell uname -r)/build PWD  := $(shell pwd)

default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules

Issue the make command to build the foo.ko module.

Language Support

This section includes information related to the support of various languages under Fedora Core.

Server Configuration Tools

This section contains information related to various server configuration tools.

Sound and Video

This section contains information related to multimedia applications.

Web Server

This section contains information related to Web-related tools.

php

Version 5.0 of PHP is now included, which includes a number of changes to the language along with significant performance improvements. Please refer to the PHP documentation for more information on migrating from PHP 4.3 to PHP 5.0:

http://www.php.net/manual/en/migration5.php

The following extensions have been added:

• the "mysqli" extension, the newly MySQL interface designed

specifically for MySQL 4; included in the php-mysql

• the "soap" extension, which can be used to implement a SOAP server

or client

Windows File Server

This section contains information related to Samba, software that makes it possible to share files between Linux and Windows systems.

samba

Browsing of Windows shares (also known as SMB browsing) fails on Fedora Core 4test2 systems that have the standard firewall configured. This is most easily noticed in the failure of Nautilus to display shares. The failure is due to the firewall disrupting the broadcast mode of SMB browsing, which is Samba's default setting. There are two workarounds:

• Configure a WINS server on the network, and set the "wins server" option in smb.conf to the address of the WINS server.

• Disable the firewall

Warning

Depending on your system and network configurations, disabling the firewall can greatly increase the chance of your system being attacked and compromised. Make sure you fully understand the risks before undertaking this step.

For additional information, refer to the following bug report:

[8] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478

Macintosh File Server

This section contains information related to netatalk, software that makes it possible to share files between Linux and Macintosh systems.

netatalk

The 2.x version of netatalk uses a different method to store resource forks, and may use a different file name encoding scheme. Upgrading to Fedora Core 4 may result in data loss. Please read the documentation of the netatalk 1.x to 2.x upgrade before upgrading to Fedora Core 4.

The netatalk upgrade information is available directly from the netatalk site:

http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html

It is also included in the netatalk installation for Fedora Core 4, the files are at:

/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf - numbered page 25, document page 33.

or

/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html

X Window System

This section contains information related to the X Window System implementation provided with Fedora Core.

xorg-x11

• Users new to the X.org X11 implementation should take note of a few differences between it and the XFree86.org X11 implementation which shipped in previous Red Hat operating systems. In particular, the names of some files have changed:

X Server Binary:

• XFree86 X11: XFree86

• X.org X11: Xorg

X Server Configuration File:

• XFree86 X11: /etc/X11/XF86Config

• X.org X11: /etc/X11/xorg.conf

X Server Log File

• XFree86 X11: /var/log/XFree86.$DISPLAY.log

• X.org X11: /var/log/Xorg.$DISPLAY.log

When configuring or troubleshooting your X server configuration, be sure that you are using the correct files.

• There has been some confusion regarding font-related issues under the X Window System in recent versions of Fedora Core (and versions of Red Hat Linux before it.) At the present time, there are two font subsystems, each with different characteristics:

- The original (15+ year old) subsystem is referred to as the "core X font subsystem". Fonts rendered by this subsystem are not anti-aliased, are handled by the X server, and have names like:

-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1

The newer font subsystem is known as "fontconfig", and allows applications direct access to the font files. Fontconfig is often used along with the "Xft" library, which allows applications to render fontconfig fonts to the screen with antialiasing. Fontconfig uses more human-friendly names like:

Luxi Sans-10

• Over time, fontconfig/Xft will replace the core X font subsystem. At the present time, applications using the Qt 3 or GTK 2 toolkits (which would include KDE and GNOME applications) use the fontconfig and Xft font subsystem; almost everything else uses the core X fonts.

In the future, Fedora Core may support only fontconfig/Xft in place of the XFS font server as the default local font access method.

NOTE: An exception to the font subsystem usage outlined above is OpenOffice.org (which uses its own font rendering technology).

If you wish to add new fonts to your Fedora Core 4test2 system, you must be aware that the steps necessary depend on which font subsystem is to use the new fonts. For the core X font subsystem, you must:

1. Create the /usr/share/fonts/local/ directory (if it doesn't already exist):

mkdir /usr/share/fonts/local/

2. Copy the new font file into /usr/share/fonts/local/

3. Update the font information by issuing the following commands (note that, due to formatting restrictions, the following commands may appear on more than one line; in use, each command should be entered on a single line):

ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale

mkfontdir /usr/share/fonts/local/

4. If you had to create /usr/share/fonts/local/, you must then add it to the X font server (xfs) path:

chkfontpath --add /usr/share/fonts/local/

Adding new fonts to the fontconfig font subsystem is more straightforward; the new font file only needs to be copied into the /usr/share/fonts/ directory (individual users can modify their personal font configuration by copying the font file into the ~/.fonts/ directory).

After the new font has been copied, use fc-cache to update the font information cache:

fc-cache <directory>

(Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/ directories.)

Individual users may also install fonts graphically, by browsing fonts:/// in Nautilus, and dragging the new font files there.

NOTE: If the font filename ends with ".gz", it has been compressed with gzip, and must be decompressed (with the gunzip command) before the fontconfig font subsystem can use the font.

• Due to the transition to the new font system based on fontconfig/Xft, GTK+ 1.2 applications are not affected by any changes made via the Font Preferences dialog. For these applications, a font can be configured by adding the following lines to the file ~/.gtkrc.mine:

style "user-font" {

fontset = "<font-specification>"

}

widget_class " *" style "user-font"

(Where <font-specification> represents a font specification in the style used by traditional X applications, such as "-adobe-helvetica-medium-r-normal-- *-120- *- *- *- *- *- *".)

Miscellaneous Notes

This section contains information related to packages that do not fit in any of the proceeding categories.

Packages Added, Moved From Core, Changed, or Deprecated/Nuked

For an overview of orphaned packages, visit this list .

This section contains lists of packages that fit into the following categories:

• Packages that have been added to Fedora Core 4test2

• Packages that have been moved out of Fedora Core 4test2

• Packages that have a changed version since Fedora Core 3

• Packages that have been deprecated, and may be removed from a future

release of Fedora Core

Packages Added

The following packages have been added to Fedora Core 4test2:

• ant-1.6.2-3jpp_2fc
• antlr-2.7.4-2jpp_1fc
• aqbanking-1.0.4beta-2
• aqhbci-1.0.2beta-2
• avalon-framework-4.1.4-2jpp_5fc
• avalon-logkit-1.2-2jpp_4fc
• bcel-5.1-1jpp_4fc
• classpath-inetlib-1.0-1jpp_1fc
• classpathx-jaf-1.0-2jpp_3fc
• classpathx-mail-1.0-3jpp_1fc
• compat-gcc-296-2.96-132.fc4
• compat-gcc-32-3.2.3-47.fc4
• compat-readline43-4.3-2
• cpufreq-utils-0.2-1.1.12
• cpuspeed-1.2.1-1.19
• cryptix-3.2.0-4jpp_1fc
• cryptix-asn1-20011119-4jpp_1fc
• cryptsetup-luks-1.0-1
• dcraw-0.0.20050227-1
• device-mapper-multipath-0.4.4-0.pre8.0
• dmidecode-2.6-1.13
• eclipse-3.1.0_fc-0.M5.17
• eclipse-bugzilla-0.1.0_fc-9
• eclipse-cdt-3.0.0_fc-0.M5.3
• eclipse-changelog-2.0.1_fc-19
• eclipse-pydev-0.9.0_fc-4
• evince-0.1.9-1
• fonts-chinese-2.15-1
• fonts-indic-1.9-2
• fonts-japanese-0.20050222-2
• fonts-korean-1.0.11-2
• gjdoc-0.7.3-1
• gnome-doc-utils-0.1.3-1
• gnome-menus-2.10.1-1
• gnome-python2-extras-2.10.0-2.1
• gnu-crypto-2.0.1-1jpp_1fc
• gnu.getopt-1.0.9-4jpp_1fc
• gwenhywfar-1.7.2-2
• hardlink-1.0-1.11
• iiimf-12.1.1-11.svn2435
• ipv6calc-0.48-3
• irqbalance-1.12-1.18
• jakarta-commons-beanutils-1.7.0-1jpp_1fc
• jakarta-commons-collections-3.1-1jpp_1fc
• jakarta-commons-daemon-1.0-2jpp_1fc
• jakarta-commons-dbcp-1.2.1-3jpp_1fc
• jakarta-commons-digester-1.6-2jpp_1fc
• jakarta-commons-el-1.0-2jpp_1fc
• jakarta-commons-fileupload-1.0-3jpp_1fc
• jakarta-commons-lang-2.0-2jpp_1fc
• jakarta-commons-launcher-0.9-3jpp_1fc
• jakarta-commons-logging-1.0.4-2jpp_1fc
• jakarta-commons-modeler-1.1-3jpp_1fc
• jakarta-commons-pool-1.2-2jpp_1fc
• jakarta-commons-validator-1.1.3-1jpp_1fc
• jakarta-taglibs-standard-1.1.1-4jpp_1fc
• java_cup-0.10-0.k.1jpp_2fc
• jdepend-2.6-2jpp_3fc
• jessie-1.0.0-3
• jlex-1.2.6-1jpp_2fc
• jsch-0.1.17-2jpp_1fc
• junit-3.8.1-3jpp_4fc
• jzlib-1.0.5-2jpp_1fc
• kdeaccessibility-3.4.0-1
• ksh-20050202-1
• latex2html-2002.2.1-1
• ldapjdk-4.17-1jpp_2fc
• libdbi-drivers-0.7.1-2
• libgconf-java-2.10.0-1
• libglade-java-2.9.92-1
• libgnome-java-2.9.92-1
• libgtk-java-2.6.1.1-1
• linux-atm-2.5.0-0.20050118.2
• lksctp-tools-1.0.2-5
• log4j-1.2.8-7jpp_3fc
• longrun-0.9-1.8
• lvm2-cluster-2.00.29-1.22.FC4
• mcelog-0.4-1.8
• microcode_ctl-1.11-1.21
• mod_jk-1.2.6-3jpp_1fc
• mx4j-2.1.0-1jpp_2fc
• mysqlclient10-3.23.58-5
• openhpi-2.0.3-2
• OpenIPMI-1.4.11-5
• openssl097a-0.9.7a-2
• oro-2.0.8-1jpp_2fc
• poppler-0.1.2-1
• puretls-0.9-0.b4.1jpp_2fc
• python-docs-2.4-102
• python-elementtree-1.2.6-4
• python-numeric-23.7-2
• python-sqlite-1.1.6-1
• python-twisted-1.3.0-4
• python-urlgrabber-2.9.6-1
• readahead-1.0-1.7
• regexp-1.3-1jpp_4fc
• rng-utils-2.0-1.5
• salinfo-0.5-1.4
• servletapi5-5.0.18-1jpp_3fc
• slib-3a1-2
• smartmontools-5.33-1.5
• sqlite-3.1.2-2
• struts11-1.1-1jpp_2fc
• system-config-lvm-0.9.22-1.0
• texi2html-1.76-2
• tomcat5-5.0.30-1jpp_2fc
• x86info-1.13-1.9
• xalan-j2-2.6.0-2jpp_1fc
• xen-2-20050403
• xerces-j2-2.6.2-4jpp_1fc
• xml-commons-1.0-0.b2.6jpp_5fc
• xml-commons-resolver-1.1-1jpp_4fc

Packages Moved Out Of Core

This is a new section to the release notes. This is based on a treediff of dist-fc3 and dist-fc4 on 14-MAR-2005. The following packages have been moved out of core from Fedora Core 4test2:

• abiword-2.0.12-3
• aiksaurus-1.2.1-2
• ash-0.3.8-20
• asp2php-0.76.18-3
• aspell-ia-0.50-1
• aumix-2.8-9
• balsa-2.2.4-1.FC3.1
• bluez-bluefw-1.0-6
• bonobo-1.0.22-9
• bzflag-1.10.6-2
• cdecl-2.5-30
• cdlabelgen-3.0.0-1
• cdp-0.33-32
• compat-gcc-8-3.3.4.2
• compat-pwdb-0.62-9
• comsat-0.17-11
• cproto-4.7c-3
• cryptsetup-0.1-4
• cyrus-imapd-2.2.6-2.FC3.6
• dbh-1.0.18-5
• dbskkd-cdb-1.01-21
• ddskk-12.2.0-4
• dietlibc-0.27-4
• diskcheck-1.6-2
• dmalloc-5.3.0-3
• exim-4.43-1
• flim-1.14.7-1
• fonts-bengali-0.1-3
• fonts-ja-8.0-16
• freeciv-1.14.2-1
• FreeWnn-1.10pl020-5
• fsh-1.2-5
• ftpcopy-0.6.2-7
• gcc4-4.0.0-0.8
• ggv-2.8.0-1
• giftrans-1.12.2-20
• Glide3-20010520-33
• gnome-vfs-1.0.5-21
• gnome-vfs-extras-0.2.0-9
• gnuchess-5.07-4
• gnumeric-1.2.13-6
• gpdf-2.8.0-5
• grip-3.2.0-3
• gv-3.5.8-29
• im-sdk-12.1-4
• jed-0.99.16-6
• jisksp14-0.1-16
• jisksp16-1990-0.1-16
• kappa20-0.3-15
• kdetoys-3.3.0-1
• kernel-utils-2.4-13.1.39
• kinput2-v3.1-23
• knm_new-1.1-16
• koffice-1.3.3-1
• lapack-3.0-25
• lesstif-0.93.36-6
• libesmtp-1.0.3r1-2
• libgda-1.0.4-3
• libgnomedb-1.0.4-3
• libtool-libs13-1.3.5-10
• libxfce4mcs-4.0.6-1
• libxfce4util-4.0.6-1
• libxfcegui4-4.0.6-1
• lilo-21.4.4-26
• Maelstrom-3.0.6-6
• MagicPoint-1.11b-1
• memprof-0.5.1-5
• mew-3.3-4
• miniChinput-0.0.3-58
• nabi-0.14-3
• namazu-2.0.13-3
• nautilus-media-0.8.1-3
• ncftp-3.1.8-2
• nedit-5.4-3
• octave-2.1.57-7
• Omni-0.9.1-7
• openhbci-0.9.17-1
• openssl096b-0.9.6b-19
• ots-0.4.2-2
• pan-0.14.2-8
• pccts-1.33mr33-11
• pdksh-5.2.14-30
• qmkbootdisk-1.0.2-3
• Regina-2.3-1
• routed-0.17-18
• skkinput-2.06.4-7
• splint-3.1.1-4
• sylpheed-0.9.12-1
• system-logviewer-0.9.11-1
• system-switch-im-0.1.2-3
• THE-3.1-2
• tora-1.3.14.1-2
• ttfonts-indic-1.6-1
• ttfonts-ja-1.2-36
• ttfonts-ko-1.0.11-32.2
• ttfonts-zh_CN-2.14-10
• ttfonts-zh_TW-2.11-28
• ttfprint-0.9-13
• tuxracer-0.61-28
• w3m-el-1.4.3-2
• wl-2.10.1-4
• x3270-3.3.2.p1-6
• xboard-4.2.7-6
• xcin-2.5.3.pre3-24
• xemacs-21.4.15-9
• xemacs-sumo-20040818-2
• xfce4-iconbox-4.0.6-2
• xfce4-panel-4.0.6-1
• xfce4-systray-4.0.6-2
• xfce-mcs-manager-4.0.6-2
• xfce-mcs-plugins-4.0.6-2
• xfce-utils-4.0.6-1
• xfdesktop-4.0.6-2
• xffm-4.0.6-1
• xffm-icons-4.0.6-2
• xfprint-4.0.6-2
• xfwm4-4.0.6-1
• xfwm4-themes-4.0.6-2
• xloadimage-4.1-32
• xmms-1.2.10-9
• xosview-1.8.2-1
• xsnow-1.42-15
• ytalk-3.1.2-1

An Overview of the Fedora Project

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 will be done in a public forum. The project will produce time-based releases of Fedora Core about 2-3 times a year, with a public release schedule. The Red Hat engineering team will continue to participate in building Fedora Core 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.

For more information, refer to the Fedora Project website:

[10] http://fedora.redhat.com/

In addition to the website, the following mailing lists are available:

• fedora-list@redhat.com -- For users of Fedora Core releases
• fedora-test-list@redhat.com -- For testers of Fedora Core test releases
• fedora-devel-list@redhat.com -- For developers, developers, developers
• fedora-docs-list@redhat.com -- For participants of the docs project

To subscribe to any of these lists, send an email with the word "subscribe" in the subject to <listname>-request (where <listname> is one of the above list names.)

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.

The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC is a real-time, text-based form of communication. With it, you can have conversations with multiple people in an open channel or chat with someone privately one-on-one.

To talk with other Fedora Project participants via IRC, access freenode IRC network. Initially, you can use irc.freenode.net as the IRC server, although you may decide to select a server that is geographically closer to you. Refer to the freenode website ([11] http://www.freenode.net/) for more information. Fedora Project participants frequent the #fedora channel, while Fedora Project developers can often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well; this information can be found on the project pages.

NOTE: Red Hat has no control over the Fedora IRC channels or their content.

( x86 )

References

Visible links

1. http://www.gnu.org/licenses/fdl.html

2. http://fedora.redhat.com/docs/selinux-faq/

3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html

4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html

5. http://platan.vc.cvut.cz/ftp/pub/vmware/

6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474

7. http://i2o.shadowconnect.com/

8. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478

9. http://people.redhat.com/~harald/udev.html

10. http://fedora.redhat.com/

11. http://www.freenode.net/