Free what is the ides of march software for linux

The Life of a Geek is very silly console game in which you (a geek) must keep a computer running until you graduate college.
Surf around on the Internet, battling hackers to gain money and better security for your box. Drink lots of caffeine to keep yourself awake, since if you go to sleep, you risk an attack on your computer.
The Life of a Geek is a simple console game.
Save up money to take a month-long college course and improve your education, but remember that paying attention to schoolwork also leaves your computer open to attack.
Find a quick job for a month at places like fast-food restaurants and grocery stores, but remember again that time away from your computer leaves it open to attack. Viruses may also appear on your computer, weakening your computers health points regularly until cleaned.
Enhancements:
- Improved randomness, a fix for a bug where more energy drinks could be bought than the available money allowed, and support for compiling using Visual C++.

The Eye Of Horus is a monitoring and alerting tool for computers. Its mainly useful for monitoring network services (eg, HTTP or SMTP servers) and the internal status of Unix servers (eg, load, disk usage, process counts).

In that respect, its a lot like Nagios, but in my opinion its better. It lacks a few features Nagios has, but it is a very simple architecture to which they can easily be added.

Its a flexible thing made from independent modules with well-defined interfaces, making it easy to customise and extend, but out of the box itll monitor your servers and produce a nice HTML summary of their status - OK, the looks need a bit of work, but that will come soon, and it can optionally integrate with the excellent (and I mean excellent) RRDTool to store logs of statistics (response times, number of packages with known security holes, etc) - and link from the status page to nice graphs of the historical behaviour of these statistics.

HOW IT WORKS

The core of the system is horus-check.py, a Python script which reads a configuration file (specified on the command line). The configuration file specifies a list of services - either network services, in which case the host to run the check from and the host to run the check at are specified, or local services, in which case only the host to run the check from need be specified. In either case, if the host to run the check from is not specified, then it defaults to the local host.

The service types reference definitions in a file which is referenced from the configuration file. In the service definitions file, a shell command to check the service is given; this command must output service status in a defined format, as a single-line YAML list. The list must contain, at least, a single-word status (OK, WARNING, FAILURE, or UNKNOWN), then optionally numeric statistics, then optionally a status message. For example:

[OK]
[UNKNOWN]
[OK, { load: 0.5, users: 3 }]
[WARNING, { load: 3, users: 30 }]
[FAILURE, { load: 95, users: 300 }]
[UNKNOWN, { }, Could not find AWK executable]

When a check is to be performed from a remote host, Horus opens an ssh connection to that host. It is assumed that the user horus is run as will have an ssh key set up to enable it to ssh to all such hosts without requiring a password.

Having performed the checks, horus-check.py then:

Reads in the status database named in the configuration file
Updates the status database with the new status of hosts
Computes an overall system status (the worst non-unknown status of any checked service)
Examines the service dependencies, and marks any service whose state is no worse than might be expected (eg, no worse than the worst state of a service it depends upon) are automatically marked as quiet
Computes a list of differences between the old and new status (services added, services removed, services whose status has improved, services whose status has worsened)
If there are any differences, invokes a notification script (named in the configuration file) with them, along with the overall status
Invokes a logging script (named in the configuration file) with the new value of every statistic reported by the service checks; I will soon provide a sample logging script that uses RRDTool to generate nice graphs.

The status database (which is written in YAML, so easily accessible to user scripts) can then be used to generate HTML status report (see status.cgi).

Heart of The Alien Redux project is a complete rewrite of game Heart of The Alien.

This game was rewritten modern computers and consoles.

Heart of The Alien is the sequel for the undoubtably the best adventure of all times, Another World. Developed back in 1994 by Interplay exclusively for the Sega CD console.

This is an open-source project which aims to bring this highly-addictive game to all modern consoles and computer platforms.

The Ace of Penguins is a set of Unix/X solitaire games based on the ones available for Windows(tm) but with a number of enhancements that my wife says make my versions better.

The latest version includes clones of freecell, golf, mastermind, merlin, minesweeper, pegged, solitaire, taipei (with editor!), and thornq (by Martin Thornquist).

Installation:

To install the binaries tar, do this as user root (other platforms are similar):

cd /usr/bin/X11
tar xvfz /tmp/ace-1.2.linux.tar.gz
tar cf - libcards.so* | (cd /usr/local/lib ; tar xf -)
rm libcards.so*

You will need to run ldconfig to notice the new shared libraries.

Then you can open a new shell window and type the name of the program you want at the command line to run it.

The Library of Assorted Spiffy Things was originally designed as a companion library to Eterm.
However, it contains many features that other projects may find useful, so it has been broken out into its own library.
Features include thorough debugging and memory tracking engines, various string manipulation functions, and a flexible config file parsing engine.
Enhancements:
- The string class is now both an interface and an implementation, so parallel implementations (e.g., a glib string wrapper) can be created.
- Detection of Imlib2 support and a pixmap leak when it was disabled have been fixed.
- Fixes have been made for gcc4/newer autotools.
- This release also contains a fix for CVE-2006-0224, a buffer overflow which could lead to privilege escalation in setuid/setgid apps using LibASTs configuration engine.

Luck of the Draw is a little application to perform draws.
Luck of the Draw allows to add entries for a draw, and have one or more entries drawn at random. Draws have a number of options so they can be customized to fit your needs, and they can be saved into a file.
I created this little application for the Mac user group in Quebec City, where we have prizes for a few lucky winners at the end of every monthly meeting.
Main features:
- Two levels of randomness.
- Support for registered or non-registered entry draws.
- Localized in french and english.

GNOME Word of the Day is a GNOME applet that displays a new vocabulary word each day.

No one likes to be lost in a sea of unknown words. With GNOME Word of the Day Applet, your vocabulary will evince perennial growth. Its a must when preparing for the SAT or GRE tests and for improving both reading comprehension and writing precision.

GNOME word of the day sits in your notification area as a whole word or as a small icon. You can retrieve words from a selection of online sources.

Ant-Eclipse is a task for the Java build tool Ant generating Eclipse projects to be just imported and used easily. Ant build scripts are used as a central place for the configuration of sources and libraries which the generated projects are based on.
The most usual way to develop a software is to write, run and debug the source code in an IDE. However, as long as the first source files are compilable the software finds its way into a package and it must be possible to compile it, run it and test it in other environments where the IDE is not available. Build tools used for this job usually cannot read the project files where IDEs store information about packages and sometimes there are more IDEs used by developers. It seems obvious that the build tool needs its own description of the package.
Keeping the package configuration on two places is more error-prone and looking for errors caused by diffrerences in these configurations can cost much time when the error occur first during the run-time of an application.
It is allways the better to keep the configuration on a single place and not to maintain its copies on more places. If there are more tools used for the development one of them should be chosen as the owner and provider of the package configuration. The others have to base ther configuration on this central one either by using it directly or by refreshing their one if the central one changes.
Which tool is the best one for keeping the package configuration? It depends on the package and the development process. The most important tool is usually the one which automates compiling packaging and running tests because it produces the final package to be delivered to end-users. This automated production usually runs unattendedly reporting results from processing the current source code base. The configuration of this tool can be taken as the source for all the others.
Ant is the most favourite build tool for projects written in the Java language. Eclipse with JDT is a state-of-the-art IDE for Java developers. Unfortunately, Eclipse cannot use Ant build scripts to base configuration of its projects on them. Ant can be run from the Eclipse IDE but the configuration is kept separately.
Ant-Eclipse automates the task of creating an Eclipse project making the developer to write an automated build script as the first thing and to generate an Eclipse project from it whenever it changes. It keeps the Eclipse project always up-to-date with the last changes in the build script. This project refreshing is usually automated when more developers are working on a software project. They have to synchronize regularly their workspace with a central source code repository to integrate changes made by the others. This usually involves:
Synchronizing the source code with a central repository.
Updating the binary dependencies (libraries) from a central depot.
Generating resources (files) dependent on the environment (time and place where it runs) like build numbers, package manifests and so on.
The regeneration of Eclipse projects fits exactly to the last phase of such sychronizing process. This is the recommended usage of the Ant-Eclipse task.
A formerly existing Eclipse project will be overwritten if a new one is to be generated. Files for an Eclipse project are not generated if they exist and they are not older than the Ant build script (the Ant build script has not been changed). This update can be forced, however.
Enhancements:
- The tool has been used for over a year, and is considered a stable version.