Fedora Core Repositories
In 2003, Red Hat announced that it would cease development of
Red Hat Linux with Red Hat Linux 9 and future commercial
versions of Red Hat products would be available by
subscription only under its
Red Hat Enterprise Linux
product line. At the same time, Red Hat announced that
it would be merging its open source development with
the
Fedora Linux
project, an open source effort to provide extra packages to
the Red Hat Linux distributions.
The resulting collaboration is an open source community effort guided by Red Hat with the goal of creating an operating system distribution completely from open source software. While Red Hat Enterprise Linux guarantees stability and new versions are only released at roughly 18 month intervals, new Fedora releases are generated 2-3 times per year and older versions become unsupported. Therefore, Fedora is affectionately referred to as bleeding edge software. Red Hat has since announced that Fedora will serve as the experimental proving ground for future developments of Red Hat Enterprise Linux.
Initially two trees of packages were developed for Fedora users. Fedora Core was the base collection of packages released on the ISOs of a given distribution. These packages made up the core of the distribution as determined by a specific set of criteria set by the community. Other packages built as add-ons to Fedora Core, were referred to as Fedora Extras and are maintained in separate repositories with their own stable, testing and development versions. In 2007, with the release of Fedora 7, these two package trees were merged into one and given the name Fedora.
There are other collections of packages, maintained by groups outside the Fedora Project, that also hold software that can be installed on your Fedora system. One such repository, developed by the RPMForge group is commonly referred to as the Dag Wieers repository.
The Red Hat Enterprise Linux group is providing a mirror of all these packages that is updated each morning after midnight CDT.
All Fedora RPMs are signed with Fedora
GPG public keys
specific to each repository. To use the keys, you will
need to download them and import them into your key
ring. For Fedora prior to version 7, the keys for both
Fedora Core and Fedora Extras can be found in the
os directory of your particular architecture
under the core tree.
All the keys are installed in the following way
| test (Fedora 9) | i386 | x86_64 | ppc |
| Fedora 8 | i386 | x86_64 | ppc |
| Fedora 7 | i386 | x86_64 | ppc |
| Fedora Core 6 (no longer supported) | i386 | x86_64 | ppc |
| FC5 (no longer supported) | i386 | x86_64 | ppc |
| FC4 (no longer supported) | i386 | x86_64 | ppc |
| FC3 (no longer supported) | i386 | x86_64 | |
| FC2 (no longer supported) | i386 | x86_64 | |
| FC1 (no longer supported) | i386 | x86_64 |
The Fedora Extras packages are subject to the same
requirements as those that are included in Fedora Core. The
packages are collected under a tree similar to that used by
Fedora Core, by
version and architecture.
Test versions for Fedora Extras packages for Fedora Core6 are stored under a debug tree for your particular architecture.
You could do-it-yourself, applying updates and installing packages by hand using RPMs. You'd quickly find that many packages have dependencies on other packages and you'd have to hunt those down and install them as well. Or, you could use a package management tool to handle these dependencies for you.
The Fedora Core and Extras repositories on this mirror have been layed out as a yum repository system. This allows an easy and integrated way for you to update your systems using the yum tools. yum handles dependencies for you, installing other packages required by the package you wish to install.
It is assumed that you have experience with yum. If not, the link in the previous paragraph is a good place to start and you may also wish to consult the Fedora yum documentation. Here we provide you with the information on what you need to include in your configuration files to use this mirror server.
For Fedora, your repo file should look like
name=Fedora $releasever - $basearch
baseurl=http://rh-mirror.linux.iastate.edu/fedora/releases/$releasever/Everything/$basearch/os/
enabled=1
[updates]
name=Fedora $releasever - $basearch - Updates
baseurl=http://rh-mirror.linux.iastate.edu/fedora/updates/$releasever/$basearch/
enabled=1
For Fedora Core, it will include something
similar to the following:
name=Fedora Core $releasever - $basearch - Base
baseurl=http://rh-mirror.linux.iastate.edu/fedora/core/$releasever/$basearch/os/
enabled=1
[updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
baseurl=http://rh-mirror.linux.iastate.edu/fedora/core/updates/$releasever/$basearch/
enabled=1
[updates-testing]
name=Fedora Core $releasever - $basearch - Test Updates
baseurl=http://rh-mirror.linux.iastate.edu/fedora/core/updates/testing/$releasever/$basearch/
enabled=0
[development]
name=Fedora Core $releasever - Development Tree
baseurl=http://rh-mirror.linux.iastate.edu/fedora/core/development/$basearch/
enabled=0
[fedora-extras]
name=Fedora Extras $releasever - $basearch - Extra Packages
baseurl=http://rh-mirror.linux.iastate.edu/fedora/extras/$releasever/$basearch/
enabled=1
[extras-debug] name=Fedora Extras - $releasever - $basearch - Debugging packages
baseurl=http://rh-mirror.linux.iastate.edu/fedora/extras/$releasever/$basearch/debug/
enabled=0
enable=0in their respective repo files.
Consult the
yum.conf
man page if you wish to delve deeper into the details
of these settings.
http://fedoraproject.org/
You are especially encouraged to consult the Fedora Installation Guide and subscribe to any of the mailing lists to receive announcements about updates as they are made available.
You may also
contact the people
who maintain this mirror.


