Free standalone farm software for linux

Nosefart is a player for NES Sound Format (NSF) files (which consist of audio data ripped from Nintendo Entertainment System games).
It runs as a standalone player in Linux, with both command line and GTK interfaces, as well has having plugins for Winamp, XMMS, and CL-amp.
Enhancements:
- The file selection dialog now remembers what directory you used in the last session.
- If esd (or something else) is blocking the sound card, it now pops up an error rather than just hanging.

colorname is both a plugin for The Gimp as well as a standalone tool that tries to assign a name to a color, using external color definitions and linear algebra.

For this it calculates the euclidean distance between the currently selected color and all predefined colors, either in the RGB or HSV color space.

This project is licensed under the GPLv3.

Usage:

Standalone

Just start colorname.py

Gimp plugin

Once installed you can find colorname in the GIMP under: ”< Toolbox >/Xtns/Colorname”

Decade is a tool for simulating rigid body dynamics. Decade can work as a standalone program.

Decade can also also work from the analysis of a SolidWorks assembly or a CATIA V5 product. Results are availables as text, graphs, and animation in SW and CATIA V5.

AMPLE is short for "A MP3 LEnder". I wrote AMPLE one summer when I was coding for a company and got fed up with having to FTP over all my MP3 files from my home server to the computer at work just to listen to them. And through the other "MP3 servers" I could find didnt fit my needs for one of the following reasons:
Depended on libfoo, libbar, python, perl, php3, Apache, libssl, etc, etc, etc...I just wanted to listen to the files
Had a lot of features for "DJ:ing" etc that I really didnt need. Well....it was fun to write too.
So whats good with AMPLE?
Small, standalone (written in C using no external libraries)
Portable (I think), I often try to compile it on the SourceForge compile farms
Allows you to listen to your own MP3s away from home, nothing more, nothing less
This is beginning to sound like marketing cr*p so Ill just stop right there, check out the links on the left for more info.
Enhancements:
- There are only two fixes in this release. One is a compilation fix for Solaris and the other one is a security fix. Turns out a buffer used for local communication didnt have sufficient checks. User data isnt written without checks though so the worst that can happen is that huge amounts of memory is allocated. The socket was also bound to the loopback device so it should only be locally abuseable.

plugmon is a basic system monitoring utility with minimal configuration requirements.

Filesystems, kernel messages, and daemons are monitored from a standalone binary that only requires an email address as configuration.

plugmon project can be started from an init script or a cronjob. No central service is needed. It aims to give a minimum of false alarms.

Usage:

Install plugmon program.
Call "plugmon --mailto my.mail@address" from an rc script.
Or call it from a cronjob. Plugmon will check if its already running.

bcr steps is a step sequencer and arpeggiator made for the Behringer BCR2000 controller. The project can also be used on its own, or with almost any other MIDI controller.

If you like, you can try out the applet version, though it wont give you the full MIDI capabilities of the standalone application.

Instructions:

Download and run with java -jar bcr-steps.jar

RenderDotC project is a world class photorealistic renderer designed to meet the demands of special effects for film. The primary reason people give for choosing RenderDotC is its favorable price per performance ratio. Moreover, RenderDotC scores high marks on everything that matters for a production renderer:
Main features:
Image Quality
- Images produced with RenderDotC possess that indescribable yet beautiful quality that some people refer to as "the RenderMan look". All phenomena that are prone to aliasing artifacts are effectively anti-aliased and noise is kept to a minimum.
Speed
- RenderDotC was designed in the 1990s to take advantage of the current hardware and software technologies. Its CPU and memory performance is unsurpassed by all renderers in its class.
Robustness
- There are hundreds of details to get right when developing a renderer and that only comes with maturity. RenderDotC has been shipping since 1996 and has proven itself on complex scenes from feature films from The Matrix to Orange County.
Features
- The RenderMan standard prescribes a rich set of geometric primitives and features. RenderDotC provides all of these plus some exclusive features such as NURB curves, DSO shadeops that can call built-in functions, and complete support for extended headroom rendering.
Flexibility
- Being RenderMan-compliant, RenderDotC supports user-programmable shading. It also has other plug-in interfaces including DSO shadeops, procedural primitives, and display drivers. Since shading is decoupled from hiding, one can easily tune the speed/quality tradeoffs of each.
Price
- RenderDotC is priced competitively for both the film and broadcast markets. When considering price, its important to take into account speed. A faster renderer means that the same number of frames can be produced per hour with a smaller render farm. Fewer computers to purchase and maintain further reduces the bottom line.
Support
- As a company, Dot C Software has been around since 1992. Our customers needs come first and we have the agility to respond to requests quickly. The people who wrote RenderDotC are the same ones that provide customer support. At Dot C we make software, period. We do not compete with our customers in the arena of computer graphics production.
Enhancements:
- Improved statistical output.
- Optional non raster-oriented dicing.
- The ability to specify motion factor as a dicing attribute, and user-defined placement of output on X.
- The Windows installer now sets up the environment.

Distributed Multi-User Compilation System is a system that allows a group of users to share a compilation farm. Each compilation request from each user will be sent to the fastest available machine, every time.
Main features:
- Supports multiple users compiling simultaneously, and scales well to handle the new loads.
- Supports multiple operating systems in the compilation farm.
- Uses all processors of a multi-processor compilation host.
- Makes best use of compilation hosts with widely differing CPU speeds.
- Guarantees that a compilation host will not be overloaded by compilations.
- Takes into account the load on a host caused by non-compilation tasks.
- Supports the dynamic addition and removal of hosts to the compilation farm.
- Works with distcc, which need not be altered in any way.
DMUCS consists of these (main) programs:
- dmucs: the "host-server". This application reads a configuration file indicating the number of CPUs and the "power" of each potential host in the compilation farm. It then receives over the network:
- load average information from each compilation host.
- host requests from compile tasks that need remote hosts on which to run.
- information requests from monitoring applications.
- status requests from an administrator.
- dmucs maintains the database of hosts in the compilation farm, and assigns hosts to compilation tasks, giving out the best host/cpu available when the compilation task asks.
- gethost: a compilation task uses gethost get a host/cpu from the dmucs server. In general, a makefile will perform a compilation this way:
- gethost distcc gcc ...
- gethost contacts the server to get a host, which it puts into the environment variable DISTCC_HOSTS. gethost then calls the program given to it. After that program ends, gethost releases the assigned host back to the dmucs server.
- loadavg: the administrator of the compilation farm must start this application on each compilation host. loadavg sends the load average of the compilation host to the dmucs server periodically. The dmucs server will "downgrade" a compilation host if the hosts load averages goes too high.
- monitor: the administrator (or anyone) may use this program to monitor the busy-ness of the compilation farm. It displays which hosts/cpus are available in the compilation farm, which hosts/cpus have compilation tasks assigned to them, which hosts have been made administratively unavailable, and which hosts are "silent" - i.e., the dmucs server has not received a load average message from the compilation host for a while.