Free 98 rock software for linux

Rocks provides an user-level package for reliable and mobile network connections.
Rocks protect sockets-based applications from network failures, particularly failures common to mobile computing, including:
.Link failures (e.g., unexpected modem disconnection);
.IP address changes (e.g., laptop movement, DHCP lease expiry);
.Extended periods of disconnection (e.g., laptop suspension).
Rock-enabled programs continue to run after any of these events; their broken connections recover automatically, without loss of in-flight data, when connectivity returns.
Rocks work transparently with most applications, including SSH clients, X-windows applications, and network service daemons.
Main features:
- Reliable: Rocks detect connection failures within seconds and reconnect automatically when connectivity is restored. Reconnection succeeds even when one end of the connection obtains a new IP address.
- Safe: Rocks recover lost in-flight data no matter when failures occur, safely interoperate with ordinary sockets, and authenticate resumed connections.
- User level: You can install and use rocks as an ordinary user. They do not require any kernel modifications.
- Transparent: You can use rocks with existing programs without re-programming, re-compiling, or re-linking.
- Easy to use: Rocks come with simple command-line tools for enabling rocks in ordinary programs.
Enhancements:
- Bug fixes.

ROCK is a Distribution Build Kit. You can configure your personal build of ROCK and easily build your own distribution (see the screenshots). Rock Linux is software for managing operating environments. In a way it is a software development toolkit for building OS solutions.
The available config options include, but are not limited to:
Package Selection
You can select the packages you want to have in your Distribution. So packages you dont want or need are not build at all. A list of available packages can be found here.
Compiler and Optimization
You can select a compiler (by default gcc3) and optimization options for building your distribution. That enables you to highly optimize for your hardware. You can also build your entire distribution with the GCC Stack-Smashing Protector enabled for enhanced security.
Dietlibc
You can use dietlibc instead of the GNU LibC as your C library. That can be very useful e.g. for embedded systems.
And much more ...
Other options are: selection of an init-style, custom GNU configure options, cross-building, and much more. A major focus in the ROCK development always has been to make adding new features and config options as easy as possible.
Enhancements:
- Packages can be forked (gcc=gcc3, gcc=gcc4) to reduce code duplication.
- Packages can be split (gcc, gcc:doc, gcc:dev) to reduce necessary filesystem space after installation.
- Postinstall scripts can be run to setup the application after installation rather than after compilation.
- Every ROCK script now has a -help text.
- udev has replaced devfs.
- Toolchain compilation for cross-builds has been made easier.
- Cluster Builds, Pseudonative Builds, and Cross Builds have been made easier.
- Lots of other improvements were made, and practically all of the 1600 packages were updated.

Hugs 98 is a functional programming system based on Haskell 98, the de facto standard for non-strict functional programming languages. Hugs 98 provides an almost complete implementation of Haskell 98, including:
- Lazy evaluation, higher order functions, and pattern matching.
- A wide range of built-in types, from characters to bignums, and lists to functions, with comprehensive facilities for defining new datatypes and type synonyms.
- An advanced polymorphic type system with type and constructor class overloading.
- All of the features of the Haskell 98 expression and pattern syntax including lambda, case, conditional and let expressions, list comprehensions, do-notation, operator sections, and wildcard, irrefutable and `as patterns.
- An implementation of the Haskell 98 primitives for monadic I/O, with support for simple interactive programs, access to text files, handle-based I/O, and exception handling.
- An almost complete implementation of the Haskell module system. Hugs 98 also supports a number of advanced and experimental extensions including multi-parameter classes, extensible records, rank-2 polymorphism, existentials, scoped type variables, and restricted type synonyms.

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

ProQuake project is a Quake engine for advanced deathmatch play, including cheat-free mode.
ProQuake is a modification to the Quake source which is specifically intended for intense deathmatch play.
It is a rock solid set of enhancements to unmodified NetQuake, such as precise aim, and other small, simple changes that improve the quality of netplay enormously.
ProQuake is fully compatible with standard NetQuake and Clanring CRMod++ features including team scores, match timer, and client pings.
Main features:
- Eliminated cheat-free lag for modem players on 3.50 servers
- "cheatfree" command tells you if youre connected to a cheat-free server
- Connect to 3.40 servers through routers/NAT/IP Masquerading
- Four button mouse support
- Mouse wheel support
- Fullbright shaft in glpro
- r_polyblend in wqpro
- QuakePro+ bestweapon command
- Recognizes ip_address:port notation
- Remove r from console output
- Added %d for binds to say where you died
- Various minor bug-fixes and improvements
- Eliminated cheat-free lag for 3.50 modem players
- Append "(cheat-free)" to the host name for cheat-free servers
- 3.40 clients can connect through routers/NAT/IP Masquerading
- iplog supports multiple concurrent servers
- Clients without map can connect to cheatfree server
- Cheat protection
- Fixed incoming message buffer overflow (q1crash)
- Added pq_logbinds to store player binds in log file
Enhancements:
- ProQuake 3.50 eliminates the lag that modem users were experiencing on cheat-free servers.

drsbackup is for backing up systems, disk to disk. drsbackup project is not aimed at your cron job that does periodic backups. Instead, it is intended as a one-shot backup facility, for use when you, say, need to upgrade a system, in which case doing a -a followed by a -a -i can be very effective.

It has three primary modes of operation:

1. Back up all filesystems on the system, as determined by a df-local script that lists all local filesystems. If your df-local script doesnt work, dont blame drsbackup .
2. Back up all filesystems specified with -f.
3. Back up all files that have changed since initial install (requires stamp/check-stamp/elim-dirs, and a stamp snapshot to have been done at install time).

Largely orthogonal to the above modes of operation, there are these additional, independent modes of operation:

1. Copy all files, but split out
2. Copy only files that have changed (presumes split out copies)
3. Copy all files, but to a series of tar archives

You can also specify whether transfers should be compressed or not (only on the client side, so far, which is usually what one wants, but not always).

Run it with an argument of -h for usage.

YaBook is a simple but powerful guestbook running on PHP 5. YaBook project features easy installation and customization, multi-language support, an administration interface, and email notifications on new postings. YaBooks design uses a template system so it can be easy integrated into your page.
YaBook ist built on the Sourdough framework, a web application framework for PHP 5. Various database systems are currently supported, e.g. MySQL, PostgreSQL, MSSQL, SQLite.
Main features:
- Fully customizable layout and interface (skins support, template based)
- Disallow HTML Code, BBcode support
- Email notification on new entries
- URLs will be transformed into links
- Multipages. Browsable entries with previous/next bar.
- User administration interface
- multi-language support with automatic language detection
- Ability to create multiple moderator and administration users
- Moderators are able to hide/unhide, delete, or edit an entry
- Administrator approvement of new entries if required
- Anti-flood spambot protection by Captcha image verification.

ZRacer is a ncurses multiplayer racing game. It has a curses based semi-graphical interface, random track generator, editable settings and supports hotseat multiplayer.
The rules are simple - the higher on the screen, the faster you ride. Dont crash with rocks, kerbs, or your opponent and be the first on the finish line.
Main features:
- Semi-graphical ncurses driven interface.
- Hotseat multiplayer.
- Random track generator.
- Runs on both Linux and Windows, tested.
- Beautiful source code.
Instructions:
Player 1 controls his car with arrow keys, and player 2 does it with wsad. The higher the car is on the screen, the faster it moves. Game time is measured with turns, where 1 turn is the time needed to move the car when its at the top verge of the screen. The track has two kerbs and occasional rocks are generated. When a car hits a rock or a kerb, it explodes. Your goal is to get to the finish line without exploding and within shortest possible time. Have fun.