Free who wants to be a millionaire winner software for linux

LINGOT is a musical instrument tuner. LINGOT is easy to use, accurate, and highly configurable. Originally conceived to tune electric guitars, its configurability gives it a more general character. (Tuning another instruments has not been tested).
It looks like an analogic tuner, with a gauge indicating the relative shift to a certain note --found automatically as the closest note to the estimated frequency--, indicating that note and its frequency.
The note will be found automatically, since the program hasnt any manual function mode (indicating the note to tune manually), for mantaining its general purpose.
We recommend using the tuner in conjunction with a sound mixer for selecting the desired recording source and the signal recording levels.
Main features:
- Accurate.
- Easy to use. Just plug in your instrument and run tuner.
- Very configurable via GUI. Its possible to change any parameter while the program is running, without editing any file.
- It works in an automatic way. It isnt necessary specify the note to tune; the program guesses it.
- Its free software. It has GPL license.
- Tuning other instruments than guitars is possible. Since this program guesses the note you are playing, it can be used to tune a piano, a bass, a violin, etc.
Enhancements:
- Files have been reorganized to a more "GNU-like" structure.
- Multi-lingual support has been added.

Script for a multi-homed firewall is an example IPTables 1.2.1 script for a dual-homed firewall.

This script has not yet been tested thoroughly on a dual-homed firewall. If you find any problems, please drop me an email.

Current versions and documentation are available at http://www.sentry.net/~obsid/IPTables/rc.scripts.dir/current/

## User-defined Chains ##

Chain KEEP_STATE
The KEEP_STATE chain holds a few rules for generic stateful packet filtering.
This chain is called from many of the INPUT/OUTPUT chains to DROP "INVALID"
and perhaps "UNCLEAN" packets and allow other packets from "RELATED" or
"ESTABLISHED" connections.

CHECK_FLAGS
The CHECK_FLAGS chain contains a few rules to filter based on TCP flags.
These rules do indeed filter mainly bogus/malicious traffic(scans, etc). It
would be a good idea to keep an eye on what these rules send to the logs.
Null scans are also logged and dropped, in the mangle table.

DENY_PORTS
The DENY_PORTS chains contains a few rules to DROP and/or LOG packets based
on the source and/or destination port number of the packet.

Packets destined to/from the following ports are dropped by default in the script. These are just some examples of some commonly used ports that certain daemons/trojans/DDoS agents may utilize.

## TCP ##
137:139 SMB
2049 NFS
6000:6063 X
20034 Netbus 2 Pro
12345:12346 Netbus
27374 SubSeven
27665,27444,31335 Trinoo
10498,12754 Mstream

## UDP ##
2049 NFS
31337 BO2k
27444,31335 Trinoo
10498 mstream

These are just examples to stare at. They guarantee no real protection against the associated trojans.

For more common port numbers check out:
http://www.sans.org/newlook/resources/IDFAQ/oddports.htm

ALLOW_PORTS
The ALLOW_PORTS chain simply ACCEPTs packets based on port number. If you have
a default FORWARD policy of DROP, then you would need to utilize a chain like
this if you are DNATing/routing connections behind the firewall or perhaps
running services on(!!!) the firewall.

ALLOW_ICMP
The ALLOW_ICMP chains simply allows packets based on ICMP type. Currently
the firewall allows the flow of the following ICMP types:
Echo Reply (pong)
Destination Unreachable
Echo Request (ping)
TTL Exceeded (traceroute)

SRC_EGRESS && DST_EGRESS
The SRC_EGRESS and DST_EGRESS chains filter packets that have a source or
destination IP address matching an array of private or reserved subnets.

TOS_OUTPUT
The TOS_OUTPUT chain exists in the mangle table and mangles the TOS(Type
of Service) field in the IP header of locally generated, outgoing packets.

TOS_PREROUTING
The TOS_PREROUTING chain exists in the mangle table and mangles the TOS(Type
of Service) field in the IP header of packets being routed through the firewall.

The following user-defined chains are pretty obvious. The firewall script is designed to have a user-defined INPUT and OUTPUT chain for every available interface. From these user-defined chains are called the user-defined chains
mentioned above, which I call "Special Chains". The chains below are then called by the built-in INPUT/OUTPUT/FORWARD chains. This isnt really the rule, of course, alot of the user-defined chains mentioned above are called directly from the built-in INPUT/OUTPUT/FORWARD chains. This is done to assure proper flow of the packets through the filters.

EXTERNAL_INPUT
INTERNAL_INPUT
DMZ_INPUT
LO_INPUT
EXTERNAL_OUTPUT
INTERNAL_OUTPUT
DMZ_OUTPUT
LO_OUTPUT

Tactical Operations: Crossfire is a tactical shooter based on Unreal Tournament 2004.

Tactical Operations: Crossfire is a fast paced first person online shooter in which two teams, terrorists and special forces, duke it out in a wide variety of environments with various objectives to accomplish. From rescuing hostages kept in a small desert town in Saudi-Arabia to preventing the bombing of an oil refinery on the Caspian sea shore. There are no less than fourteen official maps to choose from!

Each map is played for a certain amount of time and the team having won the most rounds when the time runs out is declared the winner. A round can be won either by completing the objective set for that team, such as rescueing the hostages, or by simply eliminating all players on the opposite team.

A large number of weapons is avaialable for both teams, which can be purchased by each player at the start of the round. Out of the thirty weapons currently available, theres bound to be a weapon to suit your style of playing, be it either up close and personal with the Benelli Nova tactical shotgun or sneaky sniper work with the Dragunov SVD.

Tactical Operations: Crossfire continues where the popular Tactical Ops: Assault on Terror left off, with many classic weapons returning and remakes of some of the original maps. To play TO:C, you will need Unreal Tournament 2004 installed and patched to the latest version (3369). Tactical Ops: Crossfire can be played on Windows, Linux and Mac systems.

Gapcmon is a gtk/glib desktop monitor program for the apcupsd package. Apcupsd interfaces with UPS power systems on local or networked systems. gapcmon connects to apcupsd via the NIS api to collect and displays the current operational state of the UPS.
A Gtk2/GLib2 GUI application used to monitor UPS devices controlled by the APCUPSD package. The program uses the NIS interface from apcupsd to collect event and status information for display to the end-user. Because of this great interface, this program can be executed on any OS supported machine and use the network socket interface to connect back to apcupsd. Of course apcupsd must be compiled with nis support
(i.e. ./configure --enable-nis --enable-gapcmon ...).
The general design model for gapcmon assumes the user has one or more UPSs attached to one or more tcpip/hosts with network connectivity to/from the gapcmon workstation. Gapcmon provides a Preferences panel to capture the hostname, port, and polling cycle for that UPS; along with an "enable" checkbox to indicate if the monitor for this configuration should be active. Gapcmon collects status and event information for each enabled UPS configuration and presents it to the user via a Detailed Information window.
Main features:
- FreeDesktop.org Spec for Notification Area Icons.
- Unlimited support for multiple UPSs.
- Historical Graph of five data points are charted. A total of 40 points are maintained on the graph. The data points are LINEV, BATTV, BCHARGE, LOADPCT, and TIMELEFT.
- Clicking an notification icon will cause the information window for that monitor to become visible or be hidden, if its already visible.
- Monitor tooltips are available when hovering the mouse over the icon, and contain a quick summary of the ups status.
- Icons are dynamically added or removed when enabled in preferences.
- Icon changes to reflect the operational state of the UPS.
- o where state is (online, onbattery, charging, not communicating, no cable)
- History graph supports popup tooltip for data point under the mouse pointer, showing dataseries name, color, time, and value.
- Configuration of the tcpi/ip hostname, tcp port number, and whether that monitor is currently enabled is provided via a central Preferences page.
- background thread for all network io to keep user interface responsive.

Script for a dual-homed firewall script is intended to setup a masquerading firewall based on the IPTABLES (Net)filter-machanism of Linux 2.3.15+
Syslogging matches fireparse for graphical output (see http://www.fireparse.com)
Normally this script will work out-of-the-box, but you should adapt it to your own needs (At least you should set the correct default interfaces --> see Default-Interfaces section)
Syntax to invoke script: firewall (start|stop|restart|status) EXTIF INTIF
Example: "firewall start ppp0 eth0"
Enhancements:
- Added a few comments

Volity::WinnersList is Perl class for Volity game record winners lists.

SYNOPSIS

Heres code you might see in a Volity::Game subclass implementing a game where there is one winner and a bunch of losers, the latter of whom are all effectively tied for second place (we assume that the methods called in the first two lines are defined elsewhere):

if ($self->game_has_been_won) {
my ($winner, @losers) = $self->get_winning_seat_order;
$self->winners->add_seat_to_slot($winner, 1);
$self->winners->add_seat_to_slot(@losers, 2);
$self->end;
}

And heres what you might see in a subclass defining a score-using games where each player has a discrete ordinal place, and ties and ties are not possible (again assuming the presence of some magic methods defined somewhere else in the subclass):

if ($self->game_has_been_won) {
my @ordered_seats = $self->get_winning_seat_order;
for (my $index = 0; $index winners->add_seat_to_slot($ordered_seats[$index], $place);
}
$self->end;
}

Attached to every Volity::Game-subclass object is a WinnersList object, accessible through the game objects winners method. When a game wraps up, it should use the methods listed in this document to place the tables seats in a winning order before calling the end method. The referee will then use this information when it builds the game record to send to the Volity bookkeeper.

METHODS

slots

Accessor to the raw list of winner slots. Returns an array of anonymous arrays, each representing a single slot, in winning order: the one at index [0] is the winningest slot, and the one at [-1] is the losingest. Each of these slot-arrays contains a number of Volity::Seat objects.

add_seat_to_slot ($seat, $position)

Adds the given seat to the winners list at the given position. Note that the position is expressed in game-rank, so the first-place position is 1, not 0.

If there are already seats at the current position, the given seat will share the slot with them. As a shortcut, you can add several seats at once to the same slot by passing an arrayref of seats as the first argument.

seats_at_slot ($position)

Returns the list of seats the given position in the winners list. Note that the position is expressed in game-rank, so the first-place position is 1, not 0.