Free 0.9.6 software for linux

HTun is a tool to allow you to create a fully bidirectional IP VPN over an HTTP proxy or just over port 80, allowing you to bypass restrictive firewalls and use any service you desire.
HTun creates an point-to-point virtual IP network over HTTP by encapsulating IP traffic into valid HTTP requests. The HTun server runs on a host with an unrestricted Internet connection. It listens on a common webserver port (80 or 443) and accepts HTun client connections. The HTun client daemon runs from within a restrictive network environment, communicating with the HTun server over an HTTP proxy.
HTun uses the Unversal TUN/TAP module (tun.o) available in the Linux kernel. Therefore, you must enable the option in the kernel configuration under "Network Device Support" --> "Universal TUN/TAP device driver support". It is recommended that you compile it as a kernel module rather than statically.
You must also create the TUN device file. You may call it whatever you want, but for this example, we will assume you are creating it as /dev/net/tun. Use the mknod command as follows to create the device with major number 10 and minor number 200:
mknod /dev/net/tun c 10 200
Additionally, to cause the device driver to be automatically loaded on request, you must place the following line into your /etc/modules.conf:
alias char-major-10-200 tun
Once you have made that modification, run depmod -a to reconfigure the module dependencies.
Enhancements:
- Maximum length for proxy auth username length increased.
- Now allow / in proxy auth username for authentication again SMB.
- New config directives to control client retries and timings.
- Client now behaves better when the server responds with an error code.

PHREL is a per host rate limiter. PHREL will track the rate of incoming traffic to a server and insert a rule into IPTables when a configured threshold is crossed.

The inserted chain may either rate limit or block the offending host for a period of time.

jctld is a job/process control system for clusters of machines. The project appeared due to the need for a semi-capable job control system, with the the sorts of features that we need/want on our cluster (the TUNA pi-cluster), and thats free software.
Main features:
- TCP, UDP or UNIX-socket operation
- Fairly lightweight in terms of CPU and memory
- See what jobs are running on machines
- Be able to start/kill/suspend/resume/renice jobs on machines
- Basic node monitoring (e.g. uptime/load)
- Security (trust by private-public key pairs)
- Anything else that we might want to add later on..

cmdftp is a command line FTP client for Unix.
Features include passive mode for all data transfers, shell like transparent syntax for local and remote modes, multiple and recursive file transfers using wildcards, recursive copy and move commands, remote and local text file viewing and editing, network errors detection and resuming of currently executing command, partial download resuming (if server accepts REST command), tab completion for both local and remote names, autologin using classic ~/.netrc approach, large file support.
cmdftp is aimed at being small and simple.
Installation:
To build the executable (cmdftp) extract the source code from the file (cmdftp-version.tar.gz) first. A new directory cmdftp-version is included in the tarball.
Then build using:
./configure
make
make install
There is more information in README file contained in the cmdftp release so refer to that file for other information on cmdftp configuration and installation.
Enhancements:
- The main focus of this release is the move to the GPLv3.

The Castor project has been developed out of need: the need to get stuff done and the need to write useful code.
It has been designed and coded over many cups of Dunkin Donuts Hazlenut coffee, Starbucks Latte, and tall no-whip White Mochas, as proof that coffee beans do come in handy.
Castor includes software, such as Xerces, Jakarta ORO, and Jakarta Regexp, developed by the Apache Software Foundation. Castor also includes JUnit testing framework
Main features:
- Castor XML: Java object model to and from XML (XML databinding)
- Generate source code from an XML Schema
- Default introspection or mapping file for existing object models
- Castor JDO: Java object persistence to RDBMS Castor JDO is not the same-as or compatible with Suns JDO. We have a different approach to handling data object to RDBMS mappings.
- XML-based mapping file to specify bindings for existing object models
- Support for schema-less Java to XML binding
- In memory caching and write-at-commit reduces JDBC operations
- Two phase commit transactions, object rollback and deadlock detection
- OQL query mapping to SQL queries
- EJB container managed persistence provider for OpenEJB
- Ability to create base mapping from existing Java classes
- Ability to create an XML Schema from an XML input document
Enhancements:
- Fixed problem with TransactionContext.getObjectEntry(Object) that was introduced as a result of adding support for lazy loading 1:1 relations.
- Added F.A.Q. entry describing compatibility problems between various releases of mySQL 4.1.x and its JDBC drivers.
- Reverted various DOCTYPE definitions in src/tests/jdo to use DTDs.
- Fixed issue with GeneralizedFieldHandler not able to handle collections. Collections are now automatically iterated over during getValue() calls and each item in the collection is passed into the convertUponGet method. To retain the old behavior simply add a call to #setCollectionIteration with a value of false in the constructor of your GeneralizedFieldHandler. The behavior for setter methods is not changed since only one item at a time is passed into the setter already.
- Fixed whitespace processing bug, where a was actually getting appended to the end of a string value if the parser was calling the #characters method again with only whitespace following a previous call to #characters method where valid content existed.
- Fixed recent issue where ElementDecl#getType() method was always returning null for element references.

vgrabbj project is made to take input, process it and output it. I know that sounds familiar...
It takes a v4l (not v4l2!) device as input to put it into an jpeg, pnm, or png file. You can add a timestamp into the image. You can also make it automagically upload it to your website via ftp.
Some of the options are made solely for users. I dont have any testing facilities to see if it works.
Enhancements:
- Added all missing options to the manuals, corrected misspelled options. Certain clarifications.
- vgrabbj.c: Added option -X to let daemon mode run in foreground (e.g. not detaching from current terminal)

libtour is a generic tournament processing library. The rules, participants, schedule, and results of a sporting tournament can be defined in the Scheme programming language and given to the library as input.
A CLI application is provided as a reference client implementation. See http://freshmeat.net/projects/qtour/ for a Qt-based client.
ach sporting tournament consists of a number of stages, examples of stages are Preliminary Stage, Quater Finals, Finals.
Each stage includes one or more group; for instance a Preliminary Stage may contain groups A, B, C, and D; Finals may contain a single group of two teams that compete for the winners title.
Each group has two or more teams. Before the tournament starts, only groups of the first stage know their teams. By the completion of the first stage it is usually possible to programmatically determine teams that advance to the following stage, based on their results, and so on for all stages.
Given rules of the tournament (points allocated to a team in a game, as well as sorting criteria for table of standings), initial teams and game schedule it is possible to interpret its results inside a computer program.
Main features:
- simple protocol to communicate with the library through request/reply objects
- queries of data coming from the Scheme definitions (game, team and team result fields, date format etc)
- queries of interpreted data (table of standings, game schedule with results, teams etc)
- notion of the "local team ID" that allows definitions of future stages without knowing real teams
- ability to query the information for stages whose teams hasnt been determined yet
- support for different group formulas (round robin, game count, playoffs)
- support for excessive games (those in the schedule but not necessary to play, like in a playoff stage)
- support for carry-forward game results, and incidentally, predefined games results
- game schedule verification
- support for dynamic creation of (parts of) the game schedule
- support for sorting conflicts within a group (when the rules fail to determine exact team positioning) and providing manual resolution for such conflicts (updated in ver. 0.9.2)
- summary groups (one per stage) provided by the library
- support for creating custom groups on the fly using team and/or game filtering procedures defined in Scheme; information on the interface of available filters (since ver. 0.9.0)
- loading and interpreting more than one tournament at a time
- saving and restoring tournament state
- comprehensive (?) documentation
Version restrictions:
- currently only two-player (not multi-player) games are supported

ECNCheck is a set of programs used for testing IPv4 and IPv6 hosts for ECN (Explicit Congestion Notification) support and RFC-violating refusal.

The programs also provide detailed traceroute information that can be useful in debugging ECN-related problems.