Free reaper miniatures software for linux

Reaper project is a fly around and shoot stuff 3D game.
Reaper is a graphics-intensive 3D-game where you fly a spaceship over a planet completing combat missions.
Apart from being a creature that tends to consume all free time of those involved, leaving them robbed of the chance of ever living a normal life, it is a 3D-game.
To clarify some more, it could be classified as a space combat simulator (well, you dont fly in space, you fly much closer to the ground, but you do pilot spaceships, so.
Enhancements:
- Cleanup of shadow system (could be even better)
- BUGFIX: Incorrect handling of textures larger than GL_MAX_TEXTURE_SIZE
- Removed glsdk from src/ext-directory (not used)
- Added glh (gl helper library)
- Added nvparse (nvidia parser library)
- Add extgen (gl extension definition file generator)
- Changed OpenGL extensions handling from homegrown to glh/extgen
- Dynamic environment mapping on the players ship
- The autoconf setup is a bit less hackish
- Added GL-headers in src/GL - eliminates the need to adapt to broken headers on various systems.
- Fixed a time leak in the mainloop
- Improved network-startup, better synchronization
- Compiles cleanly with gcc and -ansi -pedantic -Wall -W -Wno-sign-compare -Wno-unused
- Changed use_texture to an int (texture_level), allowing a textured hud while object textures are turned off.

Request Tracker (RT) is an enterprise-grade ticketing system which enables a group of people to intelligently and efficiently manage tasks, issues, and requests submitted by a community of users.
The RT platform has been under development since 1996, and is used by systems administrators, customer support staffs, IT managers, developers and marketing departments at thousands of sites around the world.
Written in object-oriented Perl, RT is a high-level, portable, platform independent system that eases collaboration within organizations and makes it easy for them to take care of their customers.
RT manages key tasks such as the identification, prioritization, assignment, resolution and notification required by enterprise-critical applications including project management, help desk, NOC ticketing, CRM and software development.
RT is used by Fortune 100 companies, government agencies, educational institutions, and development organizations worldwide.
Main features:
- RT is your organizations focal point for tracking tasks, issues, knowledge, and collaboration.
- Its easy to submit, assign, prioritize, search, escalate, and report on issues.
- RT keeps track of each tickets full history and metadata to help your organization better retain knowledge and analyze trends.
- RT can track multiple projects for multiple teams within a single installation.
- RT tracks critical system metadata, including time spent per action, due dates, and estimated time to completion.
- Its easy to record private comments that are not available to end-users.
- RTs web interface comes complete with an intuitive "iterative" search interface that allows end users to construct complex queries by pointing and clicking within their web browsers.
- Users can save and edit queries later, using their browsers "bookmarks" feature.
- Users dont need to do anything special -- they can just send email to RT. RT will take care of thanking them for their message, automatically routing it to the appropriate staff, and making sure all future correspondence gets to the right place.
- RT provides a simple, self-service interface that allows end users to view their own active and resolved tickets online.
- RTs web interface is designed to be easy to use from any browser. Just working in Internet Explorer and Netscape isnt enough. Your staff need to be able to get work done anytime, anywhere.
- Whether you use Windows, MacOS or Unix, your staff already have everything they need to access RT.
- RT works great from a handheld or screen-reader (for the blind.) Best Practical is working with users to ensure that a future release is fully compliant with Section 508 accessibility requirements.
- A powerful new command-line interface that allows power users to quickly and easily work with RT, even if theyre out of the office is currently available for testing by the public.
- Youve got customers around the world. RT lets you interact with them in their own language. Internally, RT converts all data to UnicodeTM, so you can respond to users in their native tongue, but work in yours.
- Youve got staff around the globe. RTs web interface has been fully internationalized. Right now, RT speaks English, German, French, Dutch, Portuguese, Russian, Czech, Japanese, Traditional Chinese, and Simplified Chinese. Adding new languages is a breeze, if you need something RT doesnt support yet. On login, RT automatically detects which language each user prefers, so staff members can collaborate even if they speak different languages.
- Unlike costly proprietary issue tracking systems, an administrator can have a basic RT system up and running in an afternoon.
- RT is built to be useful right out of the box. You dont need expensive consultants
- Theres no client software to manage or keep up to date. Your existing web browser and email clients are all you need.
- RT is written in object-oriented perl. Not only do you get the complete source code to the product with every download, but your staff can begin customizing RT to meet your needs within hours.
- RTs web interface and mail gateway are built on top of the same API we publish for you to write your own tools on top of. The interface is documented and there are numerous third party tools to use as examples and templates.
- Every organization needs to track specialized data. RT lets you define list-based and freeform custom fields to help track your tickets. Once you create custom fields, its easy to search on them, just like RTs predefined fields.
- All of RTs mailing rules are based around a powerful custom business logic system called "Scrips." Scrips make it easy for a local administrator to make RT do ANYTHING whenever a ticket is created or updated, without making it hard to upgrade.
- RTs entire web interface is built on a flexible templating system that lets you build your own web-based tools or alter RTs look and feel to better fit your organization.
- If you dont want to radically change RTs interface, you can add your own components to RTs pages. A web callback system lets you drop miniature templates into RTs web pages.
- If you need even more power, "Code overlays" let you customize RTs internal behaviour without touching RTs core libraries.
Enhancements:
- This release includes numerous small cleanups and improvements.
- It fixes the dreaded "infinite relogin" bug.

SMTP Relay Checker is a fully configurable, multithreaded open mail relay scanner. It supports scanning of IP blocks, and can print the results to a Web page.
SMTP Relay Checker is intended for Systems Administrators to check IP blocks under their control.
Compilation / Installation
To build SmtpRC please run "make" in the package directory. This will build the package and create the binary "smtprc". To install the package, please run "make install".
By Default, the binary will be installed into /usr/local/bin/, configuration files will be installed under /usr/local/etc/smtprc/ and all documentation files will be installed under /usr/local/share/doc/smtprc/. Please see below for a full list of installed files.
/usr/local/bin/smtprc
/usr/local/bin/gsmtprc
/usr/local/etc/smtprc/auto.conf
/usr/local/etc/smtprc/email.tmpl
/usr/local/etc/smtprc/rcheck.conf
/usr/local/share/doc/smtprc/README
/usr/local/share/doc/smtprc/FAQ
/usr/local/man/man1/smtprc.1
/usr/local/man/man1/gsmtprc.1
Using Smtprc
SmtpRC can be run by specifying options on the command line, or by configuring an "auto configuration" file and letting SmtpRC parse the options from there. The latter is recommended.
When SmtpRC is installed, a example "auto configuration" file is installed in "/usr/local/etc/smtprc/auto.conf". Edit this file, changing the values to suit your specific network requirements and run smtprc with the following option (a full list of options
is detailed below):
"/usr/local/bin/smtprc -j /usr/local/etc/smtprc/auto.conf"
To be sure that a mailserver relays third-party email, SmtpRC will attempt to relay mail to an address specified. It is recommended that this address is a mailbox on the local machine that is being used to run SmtpRC - pop support is a planned feature, but for now, SmtpRC only supports checking local mailboxes (mbox and Maildir). Create a new user account (smtprc), specify the email address for this account, and the local mailbox (on the command line or in the "auto configuration" file), and SmtpRC will attempt to relay emails to this address and check for recieved emails after scanning.
There is also a GUI interface to smtprc (gsmtprc) that is installed in /usr/local/bin. This requires Perl Tk to run.
Enhancements:
- Fixes a race condition between the master and reaper threads.

OpenRPG project is suite of RPG utilities for online and tabletop gaming.
More accurately described, OpenRPG is a role-playing game shell. In its basic form, OpenRPG is a peer-to-peer chat program with very advanced die rolling capabilities, a web based miniature map (think virtual table top), and a data organizer (game tree).
However, OpenRPG is highly extendable and customizable. OpenRPG is designed in a way to facilitate the development of add-ons or extension modules (called applets) that can add to its functionality.
Add-ons are created on top of the gaming shell using resources provided by the OpenRPG core. Currently, OpenRPG contains a collection of generic and system specific add-ons. OpenRPG also supports form based character sheet.
Main features:
Miniature Map: Simulate combat with a layered, web base, miniature map. Load any image off the web! Map features include: hex or square adjustable overlay grid, background images, z-order, facing, labels, free hand drawing, tape measure, and more.
Game Tree: A highly customizable data organizer that allows for the creating of custom made characters sheets and GM aids. A plug in architecture that allows for openrpg add-ons!
Chat: A full featured chat system that allows embed HTML. Embed color, tables, images, and links!
Die Engine: A full feature die engine that contains many of the common die roll options and a plug in architecture that allows for the development of game specific rollers.
Game Servers: Run your own dedicated game server.

Ghornons Hammer project is a 3D strategy adventure game.

Ghornons Hammer is a 3D strategy adventure game based on missions and adventure rather than on mass armies or leveling stats.

There is no gameplay in this version of Ghornons Hammer yet. The map you are on consits of a miniature village (windmills, trees, campfire) and some surrounding terrain. You are free to walk around the map to get an impression of what Ghornons Hammer might look like in future. In the next releases, we will be adding a user interface and character animation, so stay tuned!

Neverputt is a hot-seat multiplayer miniature golf game using the physics and graphics of Neverball.

Socks via HTTP provides a socks tunnel via HTTP.

Socks via HTTP is a program converting SOCKS requests into HTTP requests and tunnelling them through HTTP proxies if needed.

The SOCKS protocol allows programs to traverse firewalls on any port number and is used by many popular programs, like Napster, MSN Messenger, CRT(telnet client) and many others.

Many companies restrict firewall traversals only to HTTP requests, disabling SOCKS proxy.

Socks via HTTP provides a miniature SOCKS server for the SOCKS client, performing its connection through an HTTP proxy to a remote server, which establishes the real connection.

Socks via HTTP is 100% Java, and can run on any OS. It is entirely written in Java.

mysqlrowcopy is a tool that generates insert statements from result sets. It produces output similar to what might result from running mysqldump on a single SELECT query.

This project helps eliminate some of the tedium of moving data between QA and production MySQL databases.

Build:

To build mysqlrowcopy, you should run:

./configure
make

A mysqlrowcopy and mysqlrowcopy.debug file are created. They have identical functionality, the .debug version simply has debugging symbols built in (for gdb).

Since mysqlrowcopy is probably going to be I/O bound with modest CPU and RAM usage, the only reason to even build a 64-bit version is to work around potential issues in dynamic linking 32-bit binaries against 64-bit libraries.

RECIPES

1. Migrating a MySQL user account reaper from QA server to a production server.

e.g. MySQL database server qa3.example.com to prod1.example.com:

$ mysqlrowcopy -h qa3.example.com
SELECT * FROM db WHERE User = "reaper" mysql db > reaper.sql
$ mysql -h prod1.example.com mysql < reaper.sql

You could of course simply pipe the output of mysqlrowcopy into mysql and skip the intermediate file.

(Dont forget to RELOAD PRIVILEGES afterwards)

2. Keep your test environment up to date. Populate it with production data every 24 hours. You could run this sequence from cron once a day:

$ mysqlrowcopy -h finance-db.example.com
SELECT * FROM stocks WHERE modified > DATE_SUB(NOW(),INTERVAL 24 HOUR)
finance stocks > day-stocks.sql

$ cat day-stocks.sql | mysql -h finance-test.example.com finance

3. Copy data between tables on different servers that have some similar fields.

Youve got common data in table Zip on a production database:

mysql> desc Zip;
+-------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| ZIPCode | varchar(5) | | PRI | | |
| ZIPCodeType | char(1) | YES | | NULL | |
| City | varchar(32) | YES | | NULL | |
| CityType | char(1) | YES | | NULL | |
| State | varchar(32) | YES | | NULL | |
| StateCode | char(3) | YES | | NULL | |
| AreaCode | char(3) | YES | | NULL | |
| Latitude | varchar(12) | YES | | NULL | |
| Longitude | varchar(12) | YES | | NULL | |
+-------------+-------------+------+-----+---------+-------+
9 rows in set (0.00 sec)

And youve got table ZipPosition in a research database:

mysql> desc ZipPosition;
+-------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| ZIPCode | varchar(5) | | | | |
| Latitude | varchar(12) | YES | | NULL | |
| Longitude | varchar(12) | YES | | NULL | |
+-------------+-------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

You want to load data from production Zip into research ZipPosition.

$ mysqlrowcopy -h production SELECT ZIPCode,Latitude,Longitude common ZipPosition > pos.sql
$ cat pos.sql | mysql -h qa research

Note how we specify ZipPosition on the first line to tell mysqlrowcopy what the destination table is going to be.