Free io software for linux

nio provides a network IO framework.

nio is a C++ framework for writing Internet Protocol (IP) based software.

nio may be useful for:

- writing test software, testing embedded TCP/IP stacks
- writing didactic software demonstrating the features of the TCP/IP protocol suite

nio is packet oriented and uses the object oriented constructs of C++ for having easy access to every bit on a packet without getting lost in the details.

QUICKSTART

The nio based programs must be executed as root

INSTALL

- Unpack tarball
$ ./configure options
$ make install

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.

IO::Tty is a Perl module to low-level allocate a pseudo-Tty, import constants.

SYNOPSIS

use IO::Tty qw(TIOCNOTTY);
...
# use only to import constants, see IO::Pty to create ptys.

IO::Tty is used internally by IO::Pty to create a pseudo-tty. You wouldnt want to use it directly except to import constants, use IO::Pty. For a list of importable constants, see IO::Tty::Constant.

Windows is now supported, but ONLY under the Cygwin environment, see http://sources.redhat.com/cygwin/.

Please note that pty creation is very system-dependend. From my experience, any modern POSIX system should be fine. Find below a list of systems that IO::Tty should work on. A more detailed table (which is slowly getting out-of-date) is available from the project pages document manager at SourceForge http://sourceforge.net/projects/expectperl/.

If you have problems on your system and your system is listed in the "verified" list, you probably have some non-standard setup, e.g. you compiled your Linux-kernel yourself and disabled ptys (bummer!). Please ask your friendly sysadmin for help.

If your system is not listed, unpack the latest version of IO::Tty, do a perl Makefile.PL; make; make test; uname -a and send me (RGiersig@cpan.org) the results and Ill see what I can deduce from that. There are chances that it will work right out-of-the-box...

If its working on your system, please send me a short note with details (version number, distribution, etc. uname -a and perl -V is a good start; also, the output from "perl Makefile.PL" contains a lot of interesting info, so please include that as well) so I can get an overview. Thanks!

IO-stringy is a I/O on in-core objects like strings and arrays.

SYNOPSIS

IO::
::AtomicFile adpO Write a file which is updated atomically ERYQ
::Lines bdpO I/O handle to read/write to array of lines ERYQ
::Scalar RdpO I/O handle to read/write to a string ERYQ
::ScalarArray RdpO I/O handle to read/write to array of scalars ERYQ
::Wrap RdpO Wrap old-style FHs in standard OO interface ERYQ
::WrapTie adpO Tie your handles & retain full OO interface ERYQ

This toolkit primarily provides modules for performing both traditional and object-oriented i/o) on things other than normal filehandles; in particular, IO::Scalar, IO::ScalarArray, and IO::Lines.

In the more-traditional IO::Handle front, we have IO::AtomicFile which may be used to painlessly create files which are updated atomically.

And in the "this-may-prove-useful" corner, we have IO::Wrap, whose exported wraphandle() function will clothe anything thats not a blessed object in an IO::Handle-like wrapper... so you can just use OO syntax and stop worrying about whether your functions caller handed you a string, a globref, or a FileHandle.

Iterator::IO is a Perl module with filesystem and stream iterators.

SYNOPSIS

use Iterator::IO;

# Return the names of files in a directory (except . and ..)
$iter = idir_listing ($path);

# Return all the files in a directory tree, one at a time.
# Like File::Find, in slow motion.
$iter = idir_walk ($path);

# Return the lines of a file, one at a time.
$iter = ifile ($filename, %options);

# Return the lines of a file, in reverse order
$iter = ifile_reverse ($filename, %options);

This module provides filesystem and stream iterator functions. See the Iterator module for more information about how to use iterators.

FUNCTIONS

idir_listing

$iter = idir_listing ($path);

Iterator that returns the names of the files in the $path directory. If $path is omitted, defaults to the current directory. Does not return the . and .. files (under unix).

Requires IO::Dir and Cwd.

Example:

To return only certain files, combine this with an igrep:

$iter = igrep {-s && -M < 1} idir "/some/path";

(Returns non-empty files modified less than a day ago). (igrep) is defined in the Iterator::Util module).

idir_walk

$iter = idir_walk ($path);

Returns the files in a directory tree, one by one. Its sort of like File::Find in slow motion.

Requires IO::Dir and Cwd.

ifile

$iter = ifile ($filename, %options);

Opens a file, generates an iterator to return the lines of the file.
%options is a reference to a hash of options. Currently, two options are supported:

chomp

chomp => boolean indicates whether lines should be chomped before being returned by the iterator. The default is true.

$/

$/ => value specifies what string to use as the record separator. If not specified, the current value of $/ is used.

"rs" or "input_record_separator" may be used as option names instead of "$/", if you find that to be more readable. See the English module.

Option names are case-insensitive.

ifile requires IO::File.
ifile_reverse

$iter = ifile_reverse ($filename, %options);

Exactly the same as "ifile", but reads the lines of the file backwards.
The input_record_separator option values undef (slurp whole file) and scalar references (fixed-length records) are not currently supported.

INTERFACE CHANGE

In version 0.01 of Iterator::IO, the "ifile" and ifile_reverse functions accepted their options in a different manner. This has now changed to operate via a hash reference of options. The old way will still work, but is deprecated and will be removed in a future release.

EXPORTS

This module exports all function names to the callers namespace by default.

DIAGNOSTICS

Iterator::IO uses Exception::Class objects for throwing exceptions. If youre not familiar with Exception::Class, dont worry; these exception objects work just like $@ does with die and croak, but they are easier to work with if you are trapping errors.

See the Iterator module documentation for more information on how to trap and handle these exception objects.

Parameter Errors

Class: Iterator::X::Parameter_Error

You called an Iterator::IO function with one or more bad parameters. Since this is almost certainly a coding error, there is probably not much use in handling this sort of exception.

As a string, this exception provides a human-readable message about what the problem was.

Exhausted Iterators

Class: Iterator::X::Exhausted

You called value on an iterator that is exhausted; that is, there are no more values in the sequence to return.

As a string, this exception is "Iterator is exhausted."

I/O Errors

Class: Iterator::X::IO_Error

This exception is thrown when any sort of I/O error occurs; this only happens with the filesystem iterators.

This exception has one method, os_error, which returns the original $! that was trapped by the Iterator object.

As a string, this exception provides some human-readable information along with $!.

Internal Errors

Class: Iterator::X::Internal_Error

Something happened that I thought couldnt possibly happen. I would appreciate it if you could send me an email message detailing the circumstances of the error.

bio2jack is a library that allows for simple porting of general purposed bio (blocked io) OSS/ALSA audio applications to Jack.

This library allows the person porting the code to simply replace the calls into OSS/ALSA with calls into interface functions of this library.

The library buffers a small amount of audio data and takes care of the rest of the jack implementation including the linked list of audio data buffers and the jack callback.

Bio::PopGen::IO contains input individual,marker,allele information.

SYNOPSIS

use Bio::PopGen::IO;
my $io = new Bio::PopGen::IO(-format => csv,
-file => data.csv);

# Some IO might support reading in a population at a time

my @population;
while( my $ind = $io->next_individual ) {
push @population, $ind;
}

This is a generic interface to reading in population genetic data (of which there really isnt too many standard formats). This implementation makes it easy to provide your own parser for the data. You need to only implement one function next_individual. You can also implement next_population if your data has explicit information about population memberhsip for the indidviduals.

PDL::IO::Pic is a image I/O for PDL.

Image I/O for PDL based on the netpbm package.

This package implements I/O for a number of popular image formats by exploiting the xxxtopnm and pnmtoxxx converters from the netpbm package (which is based on the original pbmplus by Jef Poskanzer).

Netpbm is available at ftp://wuarchive.wustl.edu/graphics/graphics/packages/NetPBM/ Pbmplus (on which netpbm is based) might work as well, I havent tried it. If you want to read/write JPEG images you additionally need the two converters cjpeg/djpeg which come with the libjpeg distribution (the "official" archive site for this software is ftp://ftp.uu.net/graphics/jpeg).

Image I/O for all formats is established by reading and writing only the PNM format directly while the netpbm standalone apps take care of the necessary conversions. In accordance with netpbm parlance PNM stands here for portable any map meaning any of the PBM/PGM/PPM formats.

As it appeared to be a reasonable place this package also contains the routine wmpeg to write mpeg movies from PDLs representing image stacks (the image stack is first written as a sequence of PPM images into some temporary directory). For this to work you additionally need the program mpeg_encode from the Berkeley multimedia package.

You find mpeg_encode at ftp://mm-ftp.cs.berkeley.edu/pub/multimedia/mpeg/encode (they even have binaries for a number of platforms).