Free separated software for linux

ipsort script sorts a STDIN of IP addresses to STDOUT. It sorts by the first octet, then by the second, the third and the fourth.

Usage: Takes Standard in or a file or list of files. So ipsort < file1 > < file2 > or cat < file > | ipsort
Its quite clever and looks for an IP address on each line, rejecting if it doesnt find one

Options:

-c or --commas Separate the list by space-separated commas, rather than one IP per line.
-u or --unique Uniquely sort the list as well, to avoid duplicate IPs.
-s or --string Use this string to separate the IPs. Eg. -s :
-m or --multiple Search for multiple IP addresses per line.
-h or --help Display this usage message.

Super Sparrow enables users to load balance traffic between geographically separated points of presence by finding the site network-wise closest to clients.
This is done by accessing BGP routing information, the information that determines the path that traffic will take on the internet. Super Sparrow forms part of VAnessa. Super Sparrow is made to work with other components of VAnessa, including Ultra Monkey.
Main features:
- Uses BGP routing information to determine which point of presence a client should connect to.
- Routing information can be obtained from a Route Server running GNU Zebra, Gated or Cisco IOS.
- Driver module, mod_supersparrow, for Dents enables Super Sparrow enhanced sites to used DNS to communicate which server a client should connect to.
- Stand-alone programme, supersparrow, enables Super Sparrow to be integrated into applications that can communicate using stdio. This can be used to tie Super Sparrow directly into The Apache HTTP Server.
- Library API to enable applications to be integrated with Super Sparrow.
- Code is Open Source.

SpectraScan is a little helper program for those unlucky persons, who dont get their spectrums in an appropriate computer readable format, but on dead tree.

This project allows to convert a variety of spectrum types into a comma separated value format, which is suitable to be loaded into Excel or a statistic program.

Another feature is the ability to scan the axes of a spectrum.

Project Dune provides an issue tracker integrated with source code control systems.
Project Dune is a Web-based issue tracker that is fully integrated with source code control systems, which enables code inspections in the browser.
The project aims to automate the full cycle of development, from estimation to release.
This allows more time for productive tasks like architecture, design and coding. Especially if you have a quality plan in place based on ISO or CMM, you will find this software useful.
It is built for Tomcat with GWT, Hibernate, Java, Dozer, using the Postgres database.
Enhancements:
- An entire new layout.
- An administration module has been added.
- The inspection m- Eodule has been separated, and binary inspections added.
- Many fixes and features have been implemented.

Expose PHP template engine is a template engine written in PHP. A template is a special kind of document that describes how a page will look like. How does this differ from writing webpages/applications using ordinary PHP files?
A template does not contain code to fetch data from a database or deal with forms. It only contains code how this data is transformed to HTML.
Some reasons to use the Expose template engine:
- Application logic and presentation is separated. It makes your code much more beautiful and manageable.
- Templates are fed only the parameters you specifiy and support only a subset of native PHP functions. This means safer code and your designers will be happier, because they dont have to inject their HTML in application code.
- Expose supports server- and client-sided caching. This will considerably cut down on server/database load and reduces bandwidth.
- Expose has built-in locale support. Translators can work with separate files and never need to touch application files or templates. Writing applications in multiple languages has become easier than ever before!
- Plugins simplify common tasks like inserting a select box or date picker in your page.
- The template script language is based on PHP, which means you dont have to learn a new language.
Enhancements:
- The Boolean "and" (&&) operator is now properly recognized.
- Several array PHP functions are now registered at default.
- The first newline after the close tag (?>) is now stripped like expected.
- The built-in display() template function now correctly passes additional parameters to the included template.

SQL::Statement::Embed can embed a SQL engine in a DBD or module.

SQL::Statement is designed to be easy to embed in other modules and to be especially easy to embed in DBI drivers. It provides a SQL Engine and the other module needs to then provide a data source and a storage mechanism. For example, the DBD::CSV module uses SQL::Statement as an embedded SQL engine by implementing a file-based data source and by using DBI as the user interface. Similarly DBD::Amazon uses SQL::Statement as its SQL engine, provides its own extensions to the supported SQL syntax, and uses on-the-fly searches of Amazon.com as its data source.

SQL::Statement is the basis for eight existing DBDs (DBI database drivers). If you have a new data source, you too can create a DBD without having to reinvent the SQL wheel. Its fun, its easy, become a DBD author today!

SQL::Statement can be also be embedded without DBI. Well explore that first since developing a DBD uses most of the same methods and techniques.

The role of SQL::Statement subclasses

SQL::Statement provides a SQL parsing and execution engine. It does not provide a data source or storage mechanism other than in-memory tables. The DBD::File module is a subclass of SQL::Statement that provides access to file-based storage mechanisms. Its quite possible to use things other than files as data souces, in which case we wouldnt use DBD::File, instead wed replace DBD::Files methods with our own. In the examples below, well use DBD::File, replacing only a few methods.

SQL::Statement provides SQL parsing and evaluation and DBD::File provides file-based storage. The only thing missing is a data source - what we actually want to store and query. As an example suppose we are going to create a subclass called Foo that will provide as a data source a simple file similar to a passwd file - one record per line, fields separated by colons, with only three fields "username, uid, gid".

Consider what needs to happen to perform a SELECT query on our Foo data:

* recieve a SQL string
* parse the SQL string into a request structure
* open the table(s) specified in the request
* define column names and postions for the table
* read rows from the table
* convert the rows from colon-separated format into perl arrays
* match the columns and rows against the requested selection criteria
* return requested rows and columns to the user

To perform operations like INSERT and DELETE, we also need to:

* convert rows from perl arrays into colon-separated format
* write rows
* delete rows

SQL::Statement takes care of all of the SQL parsing and evaluation. DBD::File takes care of file opening, reading, writing, and deleting. So the only things Foo is really responsible for are:

* define column names and postions for the table
* convert rows from colon-separated format into perl arrays
* convert rows from perl arrays into colon-separated format

In SQL::Statement subclasses these responsibilities are assigned to two objects, a ::Statement object is responsible for opening the table, defining the column names and positions, and for creating new ::Table objects. A ::Table object is responsible for reading, converting, writing, and deleting data.

Sort MP3 is a script was made to help in organizing MP3s. If you have one directory with allot of mp3s and the names are not very readable you can run this script against them. It will read the id tag of a mp3 and rename the file to the title of the song but with _ instead of spaces. It can also create a directory structure from the id tag if the -c option is used. The structure will be put in the same directory the mp3s are in. It will be something like: "/BANDNAME/CDTITLE/SONG.mp3"

Usage: sort_mp3.pl [options]
Options should be separated by a space and my be
in any order.

-c Create a directory structure from the mp3 tag.
It is made inside the directory holding the un-named mp3s.
If not set the files will just be renamed.
Example: "/BANDNAME/CDTITLE/SONG.mp3"

-d= Path to the directory where mp3s can be found.
There should be no / at the end and no spaces.
Example: "-d=/unsorted_mp3s"