Jump to content

Fedora Linux

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Cedars (talk | contribs) at 00:27, 11 August 2006. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Fedora Core
File:Fedoralogo.png
Fedora Core 5 running GNOME
DeveloperFedora Project
OS familyLinux
Working stateCurrent
Source modelOpen source
Latest releaseCore 5 / March 20, 2006
Update methodYum
Package managerRPM Package Manager
Platformsi386, AMD64, PowerPC
Kernel typeMonolithic kernel
Default
user interface		GNOME
LicenseVarious
Official websitefedoraproject.org

Fedora Core is an RPM-based Linux distribution, developed by the community-supported Fedora Project and sponsored by Red Hat. The name derives from Red Hat's characteristic fedora used in its "Shadowman" logo. However, the Fedora community project had existed as a volunteer group providing extra software for the Red Hat Linux distribution before Red Hat got involved as a direct sponsor.[1]

Fedora aims to be a complete, general-purpose operating system built from open source software. Fedora is designed to be easily installed and configured with a simple graphical installer and the 'system-config' suite of configuration tools. Packages and their dependencies can be easily downloaded and installed with the yum utility. New releases of Fedora come out every six to eight months.

The name Fedora Core distinguishes the main Fedora packages from those of the Fedora Extras project, which provides add-ons to Fedora Core.

Fedora was derived from the original Red Hat Linux distribution. The project envisages that conventional Linux home users will use Fedora Core, and intends that it replace the consumer distributions of Red Hat Linux. Support for Fedora comes from the greater community (although Red Hat staff work on it, Red Hat does not provide official support for Fedora).

Fedora is sometimes called Fedora Linux, though this is not actually the official name.

Features

  • Fedora Core uses GNOME as its default desktop environment. The Fedora developers' attention to usability improvements in the GNOME codebase has meant that they have on occasions backported improvements such as the no-focus-steal feature in GNOME, for Fedora Core 4 [citation needed].
  • Many of the administration tools in Fedora Core are written in Python - an object oriented scripting language.

Versions

Fedora Core 4

Stable

On March 20, 2006, Fedora Core 5 (FC5, release name Bordeaux) was released. It includes GNOME 2.14, KDE 3.5.1, Xorg 7.0, GCC 4.1, version 2.6.16 of the Linux kernel, and, for the first time, the Mono development platform. Mono has not been previously included due to the extent of Microsoft's patent claims being unclear.

Fedora Core
Version Name Date
1 Yarrow November 5 2003
2 Tettnang May 18 2004
3 Heidelberg November 8 2004
4 Stentz June 13 2005
5 Bordeaux March 20 2006

Unstable

Fedora Core 6 Test 2 is the current unstable release of Fedora Core. Fedora Core 6 Final will be the next stable release of Fedora Core, which will be released in October 2006.

The preliminary release schedule of Fedora Core 6 [2] is shown as follows:

  • 21 June, 2006 - Fedora Core 6 Test 1
  • 7 August, 2006 - Fedora Core 6 Test 2
  • 11 September, 2006 - Fedora Core 6 Test 3
  • 9 October, 2006 - Fedora Core 6 Final (this release will be stable)

Bleeding-edge

Development versions of distributions such as Red Hat are often referred to as the "bleeding edge" [3]. In Red Hat and Fedora, this refers to the repositories known as Rawhide. New packages that end up in Fedora (and later, Red Hat Enterprise Linux) are first added to Fedora Rawhide. Rawhide is in perpetual beta, and may break at any time, but some developers do use it as their main distribution.

Maintained by Fedora Legacy

The Fedora Legacy project is a community project that handles releases after Red Hat has stopped maintaining updates for those who do not wish to or cannot upgrade.

Fedora Core 4 (FC4, release name Stentz) was released on June 13, 2005 for the i386, AMD64, and PowerPC architectures. It includes GNOME 2.10 and KDE 3.4, GCC 4.0, a gcj-compiled version of the Eclipse IDE, and version 2.6.11 of the Linux kernel.

Fedora Core 3

Fedora Core 3 (FC3, release name Heidelberg) was released on November 8, 2004 for the i386 and AMD64 architectures, and was transferred to Fedora Legacy on January 16, 2006. It included GNOME 2.8 and KDE 3.3.0, X.Org Server 6.8.1, the Xen virtualizer, and version 2.6.9 of the Linux kernel.

Discontinued

Fedora Core 2 (FC2, release name Tettnang) reached release on May 18, 2004, and was transferred to Fedora Legacy on April 11, 2005. It included version 2.6 of the Linux kernel, GNOME 2.6, KDE 3.2.1, and SELinux. This version also replaced XFree86 with the X.Org Server. This release occasioned many complaints because of its problems with installation while dual-booting with Windows XP (actually caused by an issue with the 2.6 kernel's handling of partitions).

Fedora Core 1 (FC1, internal codename Cambridge, release name Yarrow) was released on November 6, 2003, and transferred to Fedora Legacy on November 20, 2004. Improvements over Red Hat Linux 9 included automated updates with yum, improved laptop support with ACPI and cpufreq, and prelinking for faster program start time. An AMD64 version appeared in March 2004.

Repositories of extra software

Fedora Core only includes a core set of packages. For downloading and installing programs or codecs not distributed with Core, there are several repositories available. Packages are generally compatible between third-party repositories, though this has not always been the case.[4] There are also occasional overlaps or packaging errors that cause one package to negatively affect packages distributed from different repositories.

Official repositories

Currently only Fedora Extras has the status of official. This repository supports the currently released version of Fedora Core 5. All the others should be compatible with it.

Fedora Extras is maintained by a group of volunteers and affiliated with the official Fedora Project. As a link to Extra is currently included in the base distribution, no extra configuration is required to enable it.

Unofficial repositories

These repositories are designed to be compatible with Fedora Core although they may not be compatible with each other. Some of the repositories have discontinued active support for earlier versions of Fedora Core but keep the repositories around for the convenience of users with previous versions.

  • Livna, a third-party repository maintained by a group of packagers, supporting Fedora Core 1 through 5.
(Must use with Extras. Not compatible with RPMForge repositories.)[5][6]
  • ATrpms, maintained by Axel Thimm and supporting Fedora Core 1 through 5.
(Updates base packages ahead of Core. Some administrators consider it a bad idea to update base packages outside of their official channel.)
  • RPMforge, containing the packages of Matthias Saou, Dag Wieers and Dries that were previously available in three different repositories, supporting Fedora Core 1 through 5.[7] RPMforge is compatible with Fedora Extras, similar to Livna.[8]
    • FreshRPMS, maintained by Matthias Saou, supporting Fedora Core 1 through 5
    • Dag, maintained by Dag Wieers, supporting Fedora Core 1 through 3
    • Dries, maintained by Dries Verachtert, supporting Fedora Core 1 through 5
    • PlanetCCRMA, maintained by Fernando Lopez-Lezcano, supporting Fedora Core 1 through 5
  • Fedora Legacy, maintained by a group of packagers that support Fedora Core 1 through 3. Is not related to the Fedora-legacy.repo that comes by default with FC5.
  • kde-redhat, Excellent source for Kde support in Fedora Core maintained by a group of packagers that support Fedora Core.Has updated KDE desktop RPMS, general KDE applications such as blue tooth support.

As the Fedora Extras project is only an arms-length away from the main Fedora project, it only maintains packages legally distributable in the United States. Other repositories may have different policies. For example, the Livna project maintains packages that may have legal issues within the United States or can be downloaded only by the end user.

Some repositories also maintain "source-only" packages that require the user to download pre-built binaries that may not be available to the public. The package script then unpacks and repacks the binaries in a format more suitable for deployment on RPM-based systems.

Software update utilities

The main tool to install software from repositories is the command yum. A graphical tool called pirut (available in the upper menu bar with the name "Add/Remove Software") is, together with the update program pup, part of the standard installation since Fedora Core 5. Yumex [9] and Synaptic are two graphical alternatives preferred by some reviewers, and availables in Extras.

Up until Fedora Core 4, maintainers of some of the extra repositories advocated the use of apt-rpm for update management - being written in C, it uses fewer CPU cycles and is therefore suitable for older computers, too. For Fedora Core 5 a new version of apt is included in extras which is capable of using native yum metadata. However apt-rpm still does not support the new multi-architecture package format, where one package for each supported architecture on the machine is installed. An example would be i386 and x86_64 for AMD and Intel 64-bit systems.

Another useful tool to work with repositories is Fedora Helper [10]. It is an automatic configurator for the "missing codecs" of Fedora Core. It uses the livna.org repository. Another tool that helps to mix repositories is Fedora Frog.[11]

Fedora Core and Red Hat Enterprise Linux

Fedora came about as a result of a new business strategy which Red Hat implemented late in 2003 - Red Hat now positions Red Hat Enterprise Linux as a business-oriented Linux distribution, and all official support is for that distribution. Red Hat Enterprise Linux (RHEL) releases are branched off Fedora Core, which has led some critics to observe that Fedora Core users are in effect beta testers for RHEL.

Trademark dispute

File:Redhat Logo.svg
Red Hat's Shadowman logo

Red Hat has been tangled in disputes with the creators of the Fedora repository management software over the name, on which Red Hat has attempted to secure trademark rights.[12]

See also

References

  1. ^ "Fedora Network Proposal". Retrieved 2006-07-28.
  2. ^ "Preliminary Fedora Core 6 schedule at fedoraproject.org". Retrieved 2006-05-27.
  3. ^ "rawhide". Retrieved 2006-07-28.
  4. ^ FreshRPMs mailing list: (non-)compatibility of repositories
  5. ^ Livna's maintainers have a policy to not work together with other 3rd party repositories or at least they had this policy when Fedora Extras was Fedora.us
  6. ^ Matthias Saou explains the compatibility issues between FreshRPMs and Livna
  7. ^ FreshRPMS, PlanetCCRMA, Dries and DAG (RPMforge.net) build their packages together from the same sources. This ensures much greater cooperation and compatibility and will eventually lead to a merger.
  8. ^ "RPMforge: Frequently Asked Questions". Retrieved 2006-07-28.
  9. ^ "Yum Extender". Retrieved 2006-07-28.
  10. ^ "Fedora Helper". Retrieved 2006-07-28.
  11. ^ "Fedora frog". Retrieved 2006-07-28.
  12. ^ "Red Hat Inc.'s Use of The Fedora Name". Retrieved 2006-07-28.

Official sites

Unofficial sites

Compatibility information sites

Retrieved from "https://en.wikipedia.org/w/index.php?title=Fedora_Linux&oldid=68924597"