Fedora Core 3 released

Posted by dave on Nov 9, 2004 4:28 AM EDT
Fedora project
Mail this story
Print this story

Fedora Core 3 has been released.

Fedora Core 3 has been released and is available for download from these mirror sites or via BitTorrent.

Release notes:

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 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


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.


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 3 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 3.


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 3.


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 3 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 3.


The disk space requirements listed below represent the disk space taken up by Fedora Core 3 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 3.

  • Minimum for text-mode: 64MB

  • Minimum for graphical: 192MB

  • Recommended for graphical: 256MB

Overview of This Release

The following list includes brief summaries of some of the more significant aspects of Fedora Core 3:

Installation-Related Notes

This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core 3 in general.


If you intend to download the Fedora Core 3 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


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

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 3 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® 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:


  • 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 3. For easier access, they are organized using the same groups used in Anaconda.


This section contains information related to basic system components.


Fedora Core 3 contains OpenSSH 3.9, which 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.


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


The ext2online utility has been added for online growing of existing ext3 file systems.


It is important to keep in mind that ext2online does not grow the underlying block device itself — there must be sufficient unused space already present on the device. The easiest way to ensure this is to use LVM volumes and to run lvresize or lvextend to extend the device.

In addition, file systems must be specially prepared in order to be resized past a certain point. The preparation involves reserving a small amount of space into which on-disk tables can grow. For newly-created file systems, mke2fs reserves such space automatically; the space reserved is sufficient to grow the file system by a factor of 1000. The creation of this reserved space can be disabled by the following command:

mke2fs -O ^resize_inode

Future releases of Fedora Core will allow the creation of this reserved space on existing file systems.


  • The version of glibc provided with Fedora Core 3 performs additional internal sanity checks to prevent and detect data corruption as early as possible. By default, should corruption be detected, a message similar to the following will be displayed on standard error (or logged via syslog if stderr is not open):

    *** glibc detected *** double free or corruption: 0x0937d008 ***

    By default, the program that generated this error will also be killed; however, this (and whether or not an error message is generated) can be controlled via the MALLOC_CHECK_

    environment variable. The following settings are supported:

    • 0 — Do not generate an error message, and do not kill the program

    • 1 — Generate an error message, but do not kill the program

    • 2 — Do not generate an error message, but kill the program

    • 3 — Generate an error message and kill the program


    If MALLOC_CHECK_ is explicitly set a value other than 0, this causes glibc to perform more tests that are more extensive than the default, and may impact performance.

    Should you have a program from a third party ISV that triggers these corruption checks and displays a message, you should file a defect report with the application's vendor, since this indicates a serious bug.


The location where hotplug expects firmware to be loaded into (for example, firmware for Cardbus cards) has changed from /usr/lib/hotplug/firmware to /lib/firmware. Existing firmware files must be moved into the new directory.


  • In the past, the process of updating the kernel did not change the default kernel in the system's boot loader configuration.

    Fedora Core 3 changes this behavior to set newly-installed kernels as the default. This behavior applies to all installation methods (including rpm -i).

    This behavior is controlled by two lines in the /etc/sysconfig/kernel file:

    • UPGRADEDEFAULT — Controls whether new kernels will be booted by default (default value: yes)

    • DEFAULTKERNEL — kernel RPMs whose names match this value will be booted by default (default value: depends on hardware configuration)

  • 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 3 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 3 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>


    5. Issue the following command:

      make oldconfig

    You can then proceed as usual.


    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.


  • The default Input Method (IM) for Chinese (Simplified and Traditional), Japanese, and Korean has been changed to IIIMF — the Internet/Intranet Input Method Framework. IIIMF is supported as a native GTK2 IM module, and also through XIM using the httx client. IIIMF supports the use of multiple Language Engines (LEs) at the same time; using the GNOME Input Method Language Engine Tool (GIMLET — an applet) it is possible to switch between LEs of different languages inside GTK2 applications.

    IIIMF currently defaults to using Ctrl-Space

    or Shift-Space for toggling the input method on and off (Emacs users can use Ctrl-@ instead of Ctrl-Space

    to set the mark.)

    Depending on your selection at the language support screen during installation, one or more IIIMF language engines may be installed. The IIIMF server package (iiimf-server) will also be installed if a language engine has been selected. The language to language engine (LE) package mappings are as follows:

    • ja_JP — iiimf-le-canna

    • zh_CN — iiimf-le-chinput

    • zh_TW — iiimf-le-xcin

    • ko_KR — iiimf-le-hangul

    • {bn,gu,pa,ta,hi}_IN — iiimf-le-unit

    Accordingly, input via IIIMF will be enabled if you have chosen one of the following as your default locale:

    • ja_JP

    • zh_CN

    • zh_TW

    • ko_KR

    • {bn,gu,pa,ta,hi}_IN

    To aid your use of IIIMF, if you have selected one of the above locales and you are using the GNOME Desktop, when you first login the GIMLET utility (part of the iiimf-gnome-im-switcher package) will automatically be added to your panel.

    GIMLET is a utility for switching between the different LEs that are installed on your system. Using a different language engine allows you to enter text in different languages. Alternatively you may add GIMLET manually to your panel by right clicking on the panel and selecting:

    Add to Panel ->


    Should you wish to switch between IIIMF or the legacy input method framework XIM, you can use the system-switch-im application. After changing the input method framework your changes will be reflected when you next start the X Window System.

Mail Server

This section contains information related to the mail transport agents included with Fedora Core.


Earlier mailman RPMs installed all files under the /var/mailman/ directory. Unfortunately, this did not conform to the Filesystem Hierarchy Standard (FHS) and also created security violations when SELinux was enabled.

If you previously had mailman installed and had edited files in /var/mailman/ (such as mm_cfg.py) you must move those changes to their new location, as documented in the following file:



  • By default, the Sendmail mail transport agent (MTA) does not accept network connections from any host other than the local computer. If you want to configure Sendmail as a server for other clients, you must edit /etc/mail/sendmail.mc

    and change the DAEMON_OPTIONS line to also listen on network devices (or comment out this option entirely using the dnl comment delimiter). You must then regenerate /etc/mail/sendmail.cf by running the following command (as root):

    make -C /etc/mail

    Note that you must have the sendmail-cf package installed for this to work.

Server Configuration Tools

This section contains information related to various server configuration tools.


The firewall constructed by the system-config-securitylevel configuration tool now allows CUPS and Multicast DNS (mDNS) browsing. Note that, at the present time, these services cannot be disabled by system-config-securitylevel.

Sound and Video

This section contains information related to multimedia applications.


Past users of the CD/DVD burning application k3b may notice that the program k3bsetup is missing. This is because k3bsetup is not necessary under Fedora Core 3.

Web Server

This section contains information related to Web-related tools.


The certwatch(1) tool has been added to the crypto-utils package. This tool is used to send warning mail to root when any configured SSL certificates have expired or are approaching the expiration date. By default, the tool checks any certificates that are enabled in the mod_ssl



By default, the httpd daemon is now started using the C locale, rather than using the configured system locale setting. This behavior can be changed by setting the HTTPD_LANG variable in the /etc/sysconfig/httpd file.


The gd, mbstring, and ncurses extensions have been moved to the php-gd, php-mbstring, and php-ncurses packages, respectively. Note that you will need to install these packages manually (if required) when upgrading from an earlier release.

Windows File Server

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


Browsing of Windows shares (also known as SMB browsing) fails on Fedora Core 3 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


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:


X Window System

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


  • 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:


    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; most 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 3 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/


    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.


C++ and TCL bindings are no longer contained in the compat-db package. Applications requiring these bindings must be ported to the currently-shipping DB library.


The nscd name service cache daemon may now maintain a persistent cache across restarts or system reboots. Each database (user, group, and host, respectively) can be made selected to be persistent by setting the appropriate line in /etc/nscd.conf to "yes". Entries are not removed from the cache until they are proven to be no longer of interest. All entries whose time-to-live expires but are otherwise interesting are automatically reloaded, which helps in situations where the directory and name services become temporarily unavailable.

The nscd name service daemon is also able to communicate faster with client programs. This feature must be enabled explicitly by setting the "shared" entry for the appropriate database in /etc/nscd.conf to "yes".


Fedora Core 3 has switched from a static /dev/ directory to one that is dynamically managed via udev. This allows device nodes to be created on demand as drivers are loaded.

For more information on udev, refer to the udev(8) man page and the following link:


Additional rules for udev should be placed in a separate file in the /etc/udev/rules.d/


Additional permission rules for udev should be placed in a separate file in the /etc/udev/permissions.d/ directory.

Systems upgraded to Fedora Core 3 using Anaconda will automatically be reconfigured to use udev. However (although NOT recommended) it is possible to perform a "live" upgrade to udev using the following steps:

  1. Ensure that you are running a 2.6 kernel

  2. Ensure that /sys/ is mounted

  3. Install the initscripts RPM supplied with Fedora Core 3

  4. Install the new udev RPM supplied with Fedora Core 3

  5. Execute /sbin/start_udev

  6. Install the new mkinitrd RPM supplied with Fedora Core 3

  7. Perform one of the following steps:

    · Install the new kernel RPM supplied with Fedora Core 3


    · Re-run mkinitrd for your existing kernel(s)


Improperly performing these steps can result in a system configuration that will not boot properly.

Packages Added/Removed/Deprecated

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

  • Packages that have been added to Fedora Core 3

  • Packages that have been removed from Fedora Core 3

  • Packages that have been deprecated, and may be removed from a future release of Fedora Core


To reduce the length of the following lists,source packages, and not binary packages are listed.

Packages Added

The following packages have been added to Fedora Core 3:

  • *** Still being developed ***

Packages Removed

The following packages have been removed from Fedora Core 3:

  • *** Still being developed ***

Packages Deprecated

The following packages have been deprecated, and may be removed from a future release of Fedora Core:

  • ac-archive — No longer part of Fedora Core profile

  • dbskkd-cdb — Only used by deprecated package skkinput

  • devlabel — udev is the recommended solution

  • FAM — Gamin (which is API/ABI compatible with FAM) is the recommended solution

  • FreeWnn — Only used by deprecated package kinput2-canna-wnn6

  • kinput2-canna-wnn6 — IIIMF is the recommended input method

  • licq — Equivalent functionality present in other applications (gaim, for example)

  • lilo — GRUB is the recommended bootloader

  • miniChinput — IIIMF is the recommended input method

  • nabi — IIIMF is the recommended input method

  • ncpfs — No longer part of Fedora Core profile

  • skkinput — IIIMF is the recommended input method

  • Wnn6-SDK — Only used by deprecated package kinput2-canna-wnn6

  • xcin — IIIMF is the recommended input method

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:


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 (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


» Read more about: Story Type: Announcements; Groups: Fedora

« Return to the newswire homepage

This topic does not have any threads posted yet!

You cannot post until you login.