Free openfoam rocks software for linux

Openfire is a leading Open Source, cross-platform IM server based on the XMPP (Jabber) protocol.

Openfire server has great performance, is easy to setup and use, and delivers an innovative feature set.

Openfire is an enterprise instant messaging (EIM) server dual-licensed under the Open Source GPL and commercially. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber).

Openfire is incredibly easy to setup and adminster, but offers rock-solid security and performance.

Use Openfire in your organization as a more secure and feature-rich alternative to the consumer IM networks. Or, replace your existing EIM server with a more open, easier to use, and much less expensive solution.

Enterprise Grade

Openfire supports SSL/TLS encrypted connections out of the box as well as packet auditing to meet compliance requirements. Optionally tie Openfire into your organizations existing authentication system such as LDAP and then handle thousands of concurrent users on a single server.

Open Source and Open Protocol

Openfire is available under the Open Source GPL or a commercial license. It supports the open XMPP (Jabber) IM protocol and popular extensions. XMPP is supported by dozens of IM clients and allows for easy federation between IM servers. Openfire is among the most compliant XMPP servers available.

Cross-Platform

As a 100% Java application, Openfire supports Windows, Unix/Linux, and Mac OSX. The server can be deployed as a standalone application or service, or deployed in any J2EE compliant application server (Tomcat, Resin, etc) as a WAR (Web Application Archive).

Easy to Use

Get Openfire up and running within ten minutes. Then, administer the server using the web-based admin console.

Plugins

The server is easily extensible with a full plugin architecture. Visit the plugin library for a full list of available plugins.

Spark IM Client

Openfire works great with the cross-platform, feature-rich Spark IM client. Use the Spark Manager server plugin to manage the Spark clients on your server.

Server-Managed Contact Lists

Define groups of users in the server and then use the shared-group feature to automatically push those groups into users contact lists. This makes it very easy for people to start using the system and find the people they work with.

Darwin is the core of Mac OS X. The Darwin kernel is based on FreeBSD and Mach 3.0 technologies and provides protected memory and pre-emptive multitasking. Darwin runs on PowerPC-based Macintosh computers and a version is also available for x86-compatible computers.
Apples open source projects allow developers to customize and enhance key Apple software. Through the open source model, Apple engineers and the open source community collaborate to create better, faster and more reliable products for our users.
Beneath the appealing, easy-to-use interface of Mac OS X is a rock-solid foundation that is engineered for stability, reliability, and performance. This foundation is a core operating system commonly known as Darwin.
Darwin integrates a number of technologies, most importantly Mach 3.0, operating-system services based on 4.4BSD (Berkeley Software Distribution), high-performance networking facilities, and support for multiple integrated file systems.
Since it was first released in March 1999, Darwin has been the open-source OS technology underlying Apples Mac OS X operating system, with all development being managed and hosted by Apple at http://developer.apple.com/darwin/.
Since Apples Mac OS X releases are based directly on the live Darwin CVS repository, it has been necessary to have a fairly comprehensive procedural framework in place for registering and managing Darwin developers to ensure a good level of quality control. While this system has served its intended purpose quite well, it is desirable to further increase the collaboration between Apple and the open source community beyond the current model.
OpenDarwin.org, jointly founded in April 2002 by Internet Systems Consortium, Inc. (ISC) and Apple, is an attempt to take cooperative Darwin development to the next level. Membership in the OpenDarwin project and access to its works are open to everyone.
The project is also fully independent, with control over its own web site, project news, bug tracking information and CVS repository, as well as any other services that the community owners may wish to provide. Neither Apple nor ISC take any responsibility for, or exercise any editorial control over, the OpenDarwin project.
Many OpenDarwin members are either Apple employees or Darwin Committers, who have an active interest in merging technologies from OpenDarwin.org into Darwin and Mac OS X releases. With OpenDarwin, project members have greater latitude in producing incremental updates or interim releases of Darwin.
The mission of the OpenDarwin project is to innovate and explore new technologies while still remaining relevant, through its informal connection to www.opensource.apple.com, to the mainstream computing environments that Apple provides. It complements Apples infrastructure by allowing increased participation by the community.
Enhancements:
- Install script has been enhanced to allow user creating, setting root password
- AuthenticAMD cpus are now properly detected
- cvs from upstream feature releases
- locate from NetBSD
- at/atrun synced with FreeBSD-5
- various unix software has been updated.
- ODTulipDriver, a driver for tulip-based ethernet controllers, has been added.
- ncutil, a network configuration tool for Darwin, has been updated to version 2.1

MP3::Info is a Perl module that can manipulate / fetch info from MP3 audio files.

SYNOPSIS

#!perl -w
use MP3::Info;
my $file = Pearls_Before_Swine.mp3;
set_mp3tag($file, Pearls Before Swine, q"77s",
Sticks and Stones, 1990,
q"(c) 1990 77s LTD.", rock & roll);

my $tag = get_mp3tag($file) or die "No TAG info";
$tag->{GENRE} = rock;
set_mp3tag($file, $tag);

my $info = get_mp3info($file);
printf "$file length is %d:%dn", $info->{MM}, $info->{SS};
my $mp3 = new MP3::Info $file;
$mp3->title(Perls Before Swine);
printf "$file length is %s, title is %sn",
$mp3->time, $mp3->title;

$mp3 = MP3::Info->new(FILE)

OOP interface to the rest of the module. The same keys available via get_mp3info and get_mp3tag are available via the returned object (using upper case or lower case; but note that all-caps "VERSION" will return the module version, not the MP3 version).

Passing a value to one of the methods will set the value for that tag in the MP3 file, if applicable.

use_mp3_utf8([STATUS])

Tells MP3::Info to (or not) return TAG info in UTF-8. TRUE is 1, FALSE is 0. Default is TRUE, if available.

Will only be able to turn it on if Encode is available. ID3v2 tags will be converted to UTF-8 according to the encoding specified in each tag; ID3v1 tags will be assumed Latin-1 and converted to UTF-8.

Function returns status (TRUE/FALSE). If no argument is supplied, or an unaccepted argument is supplied, function merely returns status.

This function is not exported by default, but may be exported with the :utf8 or :all export tag.

use_winamp_genres()

Puts WinAmp genres into @mp3_genres and %mp3_genres (adds 68 additional genres to the default list of 80). This is a separate function because these are non-standard genres, but they are included because they are widely used.

You can import the data structures with one of:
use MP3::Info qw(:genres);
use MP3::Info qw(:DEFAULT :genres);
use MP3::Info qw(:all);

remove_mp3tag (FILE [, VERSION, BUFFER])

Can remove ID3v1 or ID3v2 tags. VERSION should be 1 for ID3v1 (the default), 2 for ID3v2, and ALL for both.

For ID3v1, removes last 128 bytes from file if those last 128 bytes begin with the text TAG. File will be 128 bytes shorter.

For ID3v2, removes ID3v2 tag. Because an ID3v2 tag is at the beginning of the file, we rewrite the file after removing the tag data. The buffer for rewriting the file is 4MB. BUFFER (in bytes) ca change the buffer size.

Returns the number of bytes removed, or -1 if no tag removed, or undef if there is an error.

set_mp3tag (FILE, TITLE, ARTIST, ALBUM, YEAR, COMMENT, GENRE [, TRACKNUM])

set_mp3tag (FILE, $HASHREF)

Adds/changes tag information in an MP3 audio file. Will clobber any existing information in file.

Fields are TITLE, ARTIST, ALBUM, YEAR, COMMENT, GENRE. All fields have a 30-byte limit, except for YEAR, which has a four-byte limit, and GENRE, which is one byte in the file. The GENRE passed in the function is a case-insensitive text string representing a genre found in @mp3_genres.

Will accept either a list of values, or a hashref of the type returned by get_mp3tag.
If TRACKNUM is present (for ID3v1.1), then the COMMENT field can only be 28 bytes.

ID3v2 support may come eventually. Note that if you set a tag on a file with ID3v2, the set tag will be for ID3v1[.1] only, and if you call get_mp3tag on the file, it will show you the (unchanged) ID3v2 tags, unless you specify ID3v1.

get_mp3tag (FILE [, VERSION, RAW_V2])

Returns hash reference containing tag information in MP3 file. The keys returned are the same as those supplied for set_mp3tag, except in the case of RAW_V2 being set.
If VERSION is 1, the information is taken from the ID3v1 tag (if present). If VERSION is 2, the information is taken from the ID3v2 tag (if present). If VERSION is not supplied, or is false, the ID3v1 tag is read if present, and then, if present, the ID3v2 tag information will override any existing ID3v1 tag info.

If RAW_V2 is 1, the raw ID3v2 tag data is returned, without any manipulation of text encoding. The key name is the same as the frame ID (ID to name mappings are in the global %v2_tag_names).

If RAW_V2 is 2, the ID3v2 tag data is returned, manipulating for Unicode if necessary, etc. It also takes multiple values for a given key (such as comments) and puts them in an arrayref.

If the ID3v2 version is older than ID3v2.2.0 or newer than ID3v2.4.0, it will not be read.

Strings returned will be in Latin-1, unless UTF-8 is specified (use_mp3_utf8), (unless RAW_V2 is 1).

Also returns a TAGVERSION key, containing the ID3 version used for the returned data (if TAGVERSION argument is 0, may contain two versions).
get_mp3info (FILE)

Returns hash reference containing file information for MP3 file. This data cannot be changed. Returned data:

VERSION MPEG audio version (1, 2, 2.5)
LAYER MPEG layer description (1, 2, 3)
STEREO boolean for audio is in stereo

VBR boolean for variable bitrate
BITRATE bitrate in kbps (average for VBR files)
FREQUENCY frequency in kHz
SIZE bytes in audio stream
OFFSET bytes offset that stream begins

SECS total seconds
MM minutes
SS leftover seconds
MS leftover milliseconds
TIME time in MM:SS

COPYRIGHT boolean for audio is copyrighted
PADDING boolean for MP3 frames are padded
MODE channel mode (0 = stereo, 1 = joint stereo,
2 = dual channel, 3 = single channel)
FRAMES approximate number of frames
FRAME_LENGTH approximate length of a frame
VBR_SCALE VBR scale from VBR header
On error, returns nothing and sets $@.

Bomberman for Java is an original 2D "5 player on one computer" (2 keyboard, 1 mouse, and 2 joystick players) Bomberman game.
Features include a level editor, dynamic key configuration, bomb kicker, bomb stopper, remote bombs, bomb stripper, revenge bombs, portals, rolling floor, flame mirrors, farting items, 10 diseases, adjustable items and disease probabilities, player names, an advanced scoring scheme, adjustable lifetime durations, etc.
Main features:
- fast: your player runs incredible fast
- slow: your player walks very slow
- reverse controls: you go right when you press left, ...
- invisibility: you are invisible, though not invinsible
- auto bomb putting: you put your bombs automatically
- immediate bomb explosion: your bombs explode within a second
- fart: like the item
- autoblock putting: you leave a trail of rocks behind yourself
- invisible bombs: your bombs are invisible, can be very handy
- bomb constipation: you cant lay bombs
- level editor, random level chooser, specific level chooser
- small and medium levels
- adjustable
- screen size, sound on or off, player names
- bonus lifetime, bomb explode time, amount of bonusses, remote lifetime
- fire lifetime, nr of blocks, block reappearance speed
- adjustable bonus and disease probabilities
- full dynamic control setup
- joystick support for two players
- mouse support for one player
- two players on one keyboard: four is possible, but your keyboard will not be able to handle all the pressed buttons.
- keeping track of the wins of every player, resetable via the options menu
- when a player dies, some items are created around his position.
- different background colors
- removed background music and sound effects, added other sound effects
- bomb stop item
- portals
- bomb stripper
- mirrors: reflects fire

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

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.

Asteroids is a simulation game where you have to shoot in some asteroids. Asteroids is a clone of asteroids game.
Control your spaceship with the mouse, shoot rocks until they vaporize completely.
Installation:
I have tried to compile this programs on : Linux and Solaris.
On Linux and Solaris, simply type gmake (On Solaris, typing make will call Suns own make program, that is incompatible with the makefile).
Once the program has compiled, type ./game
Enhancements:
- Sound was added, proving that there is sound in the vacuum of space.