Free o software for linux

G.O.SQL is a Web-based data management tool for Oracle. Currently, the project supports 7 schemas objects: table, view, index, sequence, function, procedure, and synonym.

fio is an I/O tool meant to be used both for benchmark and stress/hardware verification.
fio project has support for 4 different types of I/O engines (sync, mmap, libaio, posixaio), I/O priorities (for newer Linux kernels), rate I/O, forked or threaded jobs, and much more. It can work on block devices as well as files.
fio accepts job descriptions in a simple-to-understand text format. Several example job files are included. fio displays all sorts of I/O performance information, such as completion and submission latencies (avg/mean/deviation), bandwidth stats, cpu and disk utilization, and more.
Options:
$ fio
-s IO is sequential
-b block size in KiB for each io
-t < sec > Runtime in seconds
-r For random io, sequence must be repeatable
-R < on > If one thread fails to meet rate, quit all
-o < on > Use direct IO is 1, buffered if 0
-l Generate per-job latency logs
-w Generate per-job bandwidth logs
-f < file > Read < file > for job descriptions
Examples using a job file:
A sample job file doing the same as above would look like this:
[read_file]
rw=0
bs=4096
[write_file]
rw=1
bs=16384
And fio would be invoked as:
$ fio -o1 -s -f file_with_above
The second example would look like this:
[rf1]
rw=0
prio=6
[rf2]
rw=0
prio=3
[rf3]
rw=0
prio=0
direct=1
And fio would be invoked as:
$ fio -o0 -s -b4096 -f file_with_above
global is a reserved keyword. When used as the filename, it sets the default options for the threads following that section. It is possible to have more than one global section in the file, as it only affects subsequent jobs.
Enhancements:
- Support for replaying blktrace logs, full splice support (network and normal), adaptive latency histograms, many data verification improvements and additions, and many bugfixes and improvements.

PoWeb aims at providing a Web PO file editor. PO files are used by the standard GNU gettext libraries. The development was started to meet the needs of the Sympa project.

Installation:

PoWeb uses the Locale::PO CPAN module to parse PO files. You should install Locale::PO module first (available on http://search.cpan.org)

PoWeb runs as a CGI ; you should add the apropriate scriptAlias directive to your Apache config. Example : ScriptAlias /poweb /usr/local/poweb/poweb.cgi

You then need to customize variables in poweb.cgi :

o $po_dir : the directory containing the PO files
o $session_dir : the directory where user session data are stored

Carrera So-o is a simple yet challenging racing game to make time go by in boring moments.

Carrera So-o counts with 2 tracks to choose (grass and snow) with a simple objective... be the first to get to the finish line in order to win the game.

DORM4J (Dynamic Object-Relational Mapping for Java) is an O/R mapping library for Java.

DORM4J library uses annotations in JDK 1.5 and dynamic features of the Java language to implement O/R mapping functions without additional XML config files.

The development of DORM4J was inspired from the research of O/R mapping tool in Rails. O/R mapping tool of Rails is very simple and easy to use.

But it is coded by Ruby, So DORM4J was written with java language to make object-relational mapping simplicity.

DORM4J doesnt use xml config files to represent the relationship between object and table . Instead, it uses annotations to do it.

Further more, DORM4J doesnt define fields to mapping columns of table in class file. The field and its value are assigned at runtime.

Conn is a small C library used to easily build any kind of IPV4/IPV6 daemons or clients.
It allows a dynamic number of connections (limited by number or by RAM) and dynamic buffer allocation (for I/O).
Enhancements:
- This release fixes two important bugs discovered with Valgrind.

G.u.e.s.s.o is a simple guess-the-number game.
I was playing this game since years , and I liked its simplicity, it was on my electronic translater (Atlas) device, but I couldnt find any PC version of it, so I decided to code it.
And it is also a project to help me learn programming with Qt.
If you like it please just drop me an email saying so.
Installation:
First you need to compile guesso, you must have qt3-devel 3.3 or later in order to compile it, open the console and type the following commands:
./make-guesso
if everything went successfuly , you can run it with the following command:
./src/guesso
and finaly if you want to install it just copy it to any folder in your $PATH variable like /use/bin :
su
cp ./src/guesso /usr/bin/guesso
Enhancements:
- made Guesso translatable (as requested :)
- added arabic translation
- added better install/uninstall scripts
- code clean up
- other minor changes

The Faq-O-Matic is a CGI-based system that automates the process of maintaining a FAQ list. It allows visitors to your FAQ to take part in keeping it up-to-date. A permission system also makes it useful as a help-desk application, bug-tracking database, or documentation system. Jon wrote an article about the FAQ-O-Matic that appeared in the USENIX ;login: newsletter: http://www.usenix.org/publications/login/1998-6/faq.html.

This documentation itself is, naturally, maintained with Faq-O-Matic. Hence the weird title. If you see anything that can use updating, please do fix it! If you just want to play around, check out the (Xref) Playground.

A mailing list is very good because it gets together people who have questions with people who have answers.

A mailing list archive is even better, because it lets thoughtful people with Frequently Asked Questions search for an immediate answer, and avoid bothering the people who have answers. Unfortunately, the answers in a mailing list archive become stale over time, are disorganized, and are hard to sift from the conversational noise of the mailing list.

A Frequently Asked Questions list (FAQ) is even better, because the people with questions can be a little lazier and still find their answer right away. Unfortunately, maintaining a FAQ list requires effort; if the people with the answers become lazy, the FAQ list becomes stale.

I wrote the FAQ-O-Matic when I found myself frequently answering a certain question on a mailing list. The FAQ for the list had become stale (its creators interest had succumbed to laziness), and I knew I was far too lazy to take over maintaining my own FAQ.

So, in a triumph of laziness, I wrote the FAQ-O-Matic. The idea is this:

- People with answers can submit them to the FAQ, but
nobody is responsible for knowing all the answers.

- People with corrections can make them to answers, but
nobody is responsible for coordinating corrections.

This worked pretty well, but the first FAQ-O-Matic tended to become disorganized, since no-one was responsible for its structure. So I added commands to move answers and categories around, plus a Moderator feature that lets one person keep track of changes to the FAQ by e-mail:

- A person can keep a subset of the FAQ organized, but he
or she doesnt have to know all the answers or organize
the whole FAQ.

So a FAQ-O-Matic is something that lets the members of a community share the tasks of entering, correcting, and organizing frequently-asked questions and answers. Many folks have found other uses for FAQ-O-Matic, treating it as a general collaborative editing tool.