Free exclusively software for linux

xmmspipe is a plugin for XMMS that enables it to be controlled by sending strings to a named pipe (FIFO). When you enable the plugin, XMMS can be commanded by sending strings to $HOME/.xmms/inpipe, for example,
echo play_pause > ~/.xmms/inpipe
will cause XMMS to pause or play.
Since version 0.5.0, it is possible to setup an output pipe, and query XMMS for information. For example, sending "report title" to the input pipe will cause the current songs title to be printed on the output pipe.
Included is a demo program called "fade", that shows how to use the plugin to fade the current song and advance to the next one. It requires the output pipe to be be enabled (via the Config window).
The Infopipe plugin does output pipes a little differently.
When I first wrote this plugin, I didnt know about other programs that I couldve used to control XMMS with shell scripts, such as xmmsctrl or xmms-shell. However, Ive kept xmmspipe alive because pipes may be preferable in some situations:
The pipe automatically inherits the security features of the underlying filesystem (e.g. you could change its permissions so that only users of a particular group can control XMMS).
In many programming languages, writing to a pipe is easier than executing programs, making it easier to build programs to control XMMS.
The plugin can call internal XMMS functions which means it can have more functionality than programs relying on the xmms_remote_* functions alone. For example, XMMSPipe can load/save playlists.
Sometimes I think XMMS itself should just be an MP3-playing daemon that interfaces with the outside world exclusively through pipes (one for input, at least one for output). This would allow a lot more flexibility, e.g. the GUI could be arbitrary and playlists could be managed by an external program. (It would work in the same way gkrellm works with files in /proc.) Also, the code would be simpler because it only has to worry about reading various audio formats and playing them. It wouldnt have to deal with window managers, X, etc.
Enhancements:
- Added playlist_move command due to Graeme Yeo

Libface is a special library exclusively for face recognition and it is built over Intels OpenCV Library. The project has got a complete collection of functions that are essential for building a face recognition system.

Considering the need for plotting functionality, Ive included N. Devillards C interface to gnuplot in this project. Special thanks to N.Devillard.

In the example section you will find some interesting examples using the Library.

Documentation for the library is not complete, but Ive tried my best to make it usable (Parallely I am also coming up with a new documentation).

The Fedora Project is an openly-developed project designed by Red Hat, open for general participation, led by a meritocracy, following a set of project objectives.
The goal of The Fedora Project is to work with the Linux community to build a complete, general purpose operating system exclusively from open source 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 building Fedora Core and will invite and encourage more outside participation than in past releases.
By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community.
Main features:
- Support for the PowerPC (PPC) architecture.
- GCC 4.0
- GNOME 2.10
- KDE 3.4 includes new accessibility features. You can manage these new features in KDS Control CenterRegional & AccessibilityAccessibility.
- Native Eclipse 3.1M6 (part of a free Java stack)
- MySQL 4.1
- PHP 5.0
- Xen 2 (virtualization to run multiple versions of an OS)
- GFS 6.1-0.pre22 (cluster file system)
- Evince 0.2.1 (universal document viewer)
- GDM 2.6 - Includes early login capability
- SELinux This release includes coverage for 80 new daemons by the targeted policy. There are changes to the handling of Booleans. The targeted policy is enabled by default.

Fedora Linux brings you a powerful Linux operating system which is built from open source software. The Fedora Project is an openly-developed project designed by Red Hat, open for general participation, led by a meritocracy, following a set of project objectives.

The goal of The Fedora Project is to work with the Linux community to build a complete, general purpose operating system exclusively from open source 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 building Fedora Core and will invite and encourage more outside participation than in past releases. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community.

Major Features:

1. Support for the PowerPC (PPC) architecture.
2. GCC 4.0
3. GNOME 2.10
4. KDE 3.4 includes new accessibility features. You can manage these new features in KDS Control CenterRegional & AccessibilityAccessibility.
5. Native Eclipse 3.1M6 (part of a free Java stack)
6. MySQL 4.1
7. PHP 5.0
8. Xen 2 (virtualization to run multiple versions of an OS)
9. GFS 6.1-0.pre22 (cluster file system)
10. Evince 0.2.1 (universal document viewer)
11. GDM 2.6 Includes early login capability
12. SELinux This release includes coverage for 80 new daemons by the targeted policy. There are changes to the handling of Booleans. The targeted policy is enabled by default.

XShipWars is a massively multi-player game, ultra graphical, space-oriented gaming system designed exclusively for network play. You create your own universes, build your own vessels and form your own empires.

Devel::FindGlobals is a Perl module to find global variables and their size.

SYNOPSIS

use Devel::FindGlobals;
print print_globals_sizes();

This module just runs around and over the symbol table, finds global variables, gets their sizes with Devel::Size, and then prints them out.

find_globals() just finds the globals (and returns a hashref), and find_globals_sizes() returns the globals and the sizes in a hashref. print_globals_sizes() prints out that data in a pretty table.

find_globals() hashref is of the form $hash->{TYPE}{NAME}, where TYPE is SCALAR, ARRAY, HASH (types stored in @Devel::FindGlobals::TYPES).

find_globals_sizes() hashref is the same, except that the value of the record is not 1 but an arrayref of size and total_size (size is the size of the variable itself, and total_size counts up all the other members of the variable, for arrayrefs and hashrefs).

print_globals_sizes() accepts an OPTIONS hash. Currently recognized options are:

ignore_files

Ignore file globals (like $main::_
ignore_undef_scalars

Ignore scalars that exist, but are not defined. Default value is true.

exclude_match

An arrayref of strings to match; e.g., [^VERSION$, ^Debug]. Will not print variables matching any of the expressions.

include_match

Same as exclude_match, except for variables to exclusively include, instead of strings to exclude.

lexicals

A hashref of name = reference> for lexical variables to include in the report.

DM1 Thread Library is part of the DM1 project. This library was born out of my need to have a portable C++ Thread library that would be simple to use, and would provide all the necessary Threads functionality I required for the DM1 project.
Initially, this library was in C, but when I decided to re-write DM1 in C++, I ported the library to C++. During the port, I enhanced the functionality of the Threads library.
The DM1 Threads library aims to be small. It does not try to provide a comprehensive set of functionality, but only what is absolutely essential for a project like DM1. I had the simplicity of the Java Threads package in mind when creating this library.
The constructs provided by the DM1 Thread library are:
- Thread objects that represent Operating System threads.
- A Mutex is provided as a mechanism for Mutual Exclusion . Mutexes are used to ensure that a piece of code is executed by only one thread at any point in time.
- Events are provided as low-level mechanisms for thread synchronisation. Events can be waited for, and signalled to.
- A higher level object, that combines the functionality of an Event and a Mutex, is provided. This is the Monitor object. A Monitor can be locked exclusively, just like a Mutex, but it can also be made the object of a Wait operation. The signalling mechanism supports notification of one or more waiting threads.
- To enable more efficient locking when both shared and exclusive access to data is required, Latches are provided.
- Apart from the Thread synchronisation primitives described above, the library also provides a ThreadPool for the situation when it is inefficient to create a thread exclusively for a particular task, and it is desirable to share a pool of threads for executing multiple tasks.
Design Principles
The DM1 Threads library was designed with the following principles in mind:
1. Implement the bare minimum that is required. This Threads library does not aim to be a comprehensive threads package.
2. Avoid complex algorithms. If a particular construct is hard to implement correctly on all platforms, avoid it.
3. Document the library.
4. Avoid low level code, such as assembler code to implement Spin locks. Rely on the libraries provided by the Operating System.
5. Avoid holding Mutexes beyond function calls. A DM1 Thread library function will not hold any Mutex locks when it returns.
6. Avoid using clever C++ techniques wherever possible. (Unfortunately, some cleverness is required to implement the Thread class correctly).
7. Avoid dependency on external libraries. The DM1 library only requires the standard C library, apart from native Threads functionality.
8. Always report an error as soon as it is discovered.
9. Insert debug messages that can be switched on at run-time.
10. Do not throw exceptions from destructors because these might be executing as a result of an uncaught exception.
11. Never let an error go unreported.