Free red hat club software for linux

ical for Red Hat is an effort to provide the ical program in RPM format for users of current versions of Red Hat Linux.

Red Carpet is a software management tool for RPM-based Linux distros.

Red Carpet is a suite of applications that allows easy installation and update of software on Linux systems. Red Carpet project features both command-line and graphical GNOME interfaces.

These days Red Carpet is part of the Novell ZenWorks solution.

MKGI Chess Club is a chess playing server with a pure Web interface.
It features complete player profile management, full html email notification with embedded board display.
MKGI Chess Club also features an interface to match against chess engines such as gnuchess, phalanx, and crafty.
Enhancements:
- Fixed the notification feature which was broken since 1.6.0.
- Fixed undo availability immediately after a move.
- Implemented partial dragndrop of pieces on the chess board.

EZ Red Skin Fix is a script-fu based on a technique by lylejk of dpreview.com that can be used to improve skin that has a reddish tint.

Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....

Fedora Core is now available from Red Hat and at distinguished mirror sites near you, and is also available in the torrent.
Fedora Core has expanded in this release to four binary ISO images and four source ISO images, and is available for both x86-64 and i386 and also PPC machines.
The Fedora Project is a Red-Hat-sponsored and community-supported open source project. It is also a proving ground for new technology that may eventually make its way into Red Hat products. It is not a supported product of Red Hat, Inc.
The goal of The Fedora Project is to work with the Linux community to build a complete, general purpose operating system exclusively from free 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 the building of Fedora Core and will invite and encourage more outside participation than was possible in Red Hat Linux.
By using this more open process, we hope to provide an operating system that uses free software development practices and is more appealing to the open source community.
Main features:
- KDE 3.5.4
- GNOME 2.16
- OpenOffice 2.0.4
- Kernel 2.6.17
- Xen
- ...and many more

Current project is an open source implementation of a server to interact with the Up2date Agent shipped in Red Hat Linux.
Everything is implemented for a basic, anonymous only system. We are working to extend support for non-anonymous (fully managed) setups.
Main features:
- Production quality Up2date server for 2.7 to 4.4 clients with a Fedora Core 1, 2, 3, 4, or Red Hat Enterprise Linux 3, or 4 server.
- Full SQL database backend.
- Web Interface in the devel series.
- As easy to setup for the admin as we can make it.
Enhancements:
- This version fixes errors in the channel scan code path that was nonfunctional in 1.7.5.
- This also includes code to reconnect to MySQL databases when the connection times out.
- The database also collects a bit more meta information about each client, and that is displayed in the TG web interface.