Free read and write software for linux

databeans is a fully object oriented (not relational) persistence framework for Java, based on the use of the JavaBeans accessor methods to read and write data on disk instead of in the classes instance fields.
Main features:
- based on the use of the javabeans accessor methods to read/write data on disk in place of in the classes instance fields
- distributed (through RMI)
- transactional (with the 4 ANSI isolation levels supported)
- garbage collected (backed by an on-disk heap "heapspace")
- with persistent versions of the Collection classes
Installation:
Extract the archive into any appropriate directory on your hard drive. It will create a "databeans" directory with the following contents:
build.xml
api
[api documentation as generated by javadoc]
bin
databeans_admin
databeans_admin.bat
databeans_export
databeans_export.bat
databeans_import
databeans_import.bat
export.bsh
import.bsh
mkheapspace
mkheapspace.bat
mkheapspace.bsh
docs
getting_started.txt
gpl.txt
lib
databeans_admin.jar
databeans_client.jar
databeans.jar
security
databeans.policy
sample
client
build.xml
Department.java
Employee.java
policy
Sample.java
server
build.xml
DepartmentImpl.java
Department.java
EmployeeImpl.java
Employee.java
policy
src
[java source files]
The most interesting part for now is the file getting_started.txt located in the docs/ directory. It will guide you through running a sample application (which is located in the sample/ directory). That done, go on and read the manual (below) for a complete view of the products features.

FUR is a application that let the user mount a Windows CE based device on your Linux file system: it uses the brilliant FUSE (acronym of File system in UserSpacE of Miklos Szeredi) and the great librapi2 of the Synce Project, a unix implementation of the RAPI protocol (that your device use to communicate with your other operating $ystem ) which you can find here, along with other very nice tools.
You execute it with proper arguments, then (if everything goes fine) the entire file system of your (previously connected) handheld will appear automagically mounted like a regular Linux file system where you will be able to copy, move read and write data with your favorite programs.
FUR filesystem means FUSE use libRAPI.
What dose not?
- Not very stable, particulary if used concurrently by different processes (but should be usable).
- Not well tested.
- The source is horrible(Tm).
- The implementation is more involved than it should.
- Lack documentation.
- Not even remotely optimized.
- Configuration tools deficient.
- Random access I/O is anti-optimized.
- Write is bugged (maybe a problem with concurrent file access).
- The resource locking system (e.g. to prevent different processes to write on the same file) is only roughly implemented (theres a lot to be done).
- Total absence of a caching system of some sort (which i hope to implement, sooner or later).
- Some errors are to obscure (and maybe not well implemented).
- Some attributes (e.g. ctime) are not implemented (the needed function in the librapi2 library is not yet implemented).
- No UID/GID check: this is not a security issue: only the user that invoke the dccm demon can access the filesystem, but other users should be able to see some kind of error message (which i will implement soon).
- Lot of other things i have forgot now.
- The log reporting suck

Archive::Zip is a Perl module which provides an interface to ZIP archive files.

SYNOPSIS

# Create a Zip file
use Archive::Zip qw( :ERROR_CODES :CONSTANTS );
my $zip = Archive::Zip->new();

# Add a directory
my $dir_member = $zip->addDirectory( dirname/ );

# Add a file from a string with compression
my $string_member = $zip->addString( This is a test, stringMember.txt );
$string_member->desiredCompressionMethod( COMPRESSION_DEFLATED );

# Add a file from disk
my $file_member = $zip->addFile( xyz.pl, AnotherName.pl );

# Save the Zip file
unless ( $zip->writeToFileNamed(someZip.zip) == AZ_OK ) {
die write error;
}

# Read a Zip file
my $somezip = Archive::Zip->new();
unless ( $somezip->read( someZip.zip ) == AZ_OK ) {
die read error;
}

# Change the compression type for a file in the Zip
my $member = $somezip->memberNamed( stringMember.txt );
$member->desiredCompressionMethod( COMPRESSION_STORED );
unless ( $zip->writeToFileNamed( someOtherZip.zip ) == AZ_OK ) {
die write error;
}

The Archive::Zip module allows a Perl program to create, manipulate, read, and write Zip archive files.

Zip archives can be created, or you can read from existing zip files.
Once created, they can be written to files, streams, or strings. Members can be added, removed, extracted, replaced, rearranged, and enumerated. They can also be renamed or have their dates, comments, or other attributes queried or modified. Their data can be compressed or uncompressed as needed.
Members can be created from members in existing Zip files, or from existing directories, files, or strings.

This module uses the Compress::Zlib library to read and write the compressed streams inside the files.

File::Remote is a Perl module to read/write/edit remote files transparently.

SYNOPSIS

#
# Two ways to use File::Remote
#
# First, the function-based style. Here, we can use the
# special :replace tag to overload Perl builtins!
#
use File::Remote qw(:replace); # special :replace tag

# read from a remote file
open(REMOTE, "host:/remote/file") or die $!;
print while (< REMOTE >);
close(REMOTE);

# writing a local file still works!
open(LOCAL, ">>/local/file");
print LOCAL "This is a new line.n";
close(LOCAL);

mkdir("host:/remote/dir", 0755);
unlink("host:/remote/file");
unlink("/local/file"); # still works too!
symlink("host:/remote/src", "host:/remote/dest");

chown("root", "other", "host:/remote/dir/file");
chmod(0600, "host:/remote/dir/file");

#
# Next, the object-oriented style, if you dont want to
# mess with the builtins.
#
use File::Remote;
my $remote = new File::Remote;

# Standard filehandles
$remote->open(FILE, ">>host:/remote/file") or die $!;
print FILE "Heres a line thats added.n";
$remote->close(FILE);

# Create a new file and change its permissions
$remote->mkdir("host:/remote/dir");
$remote->touch("host:/remote/dir/file");

# Move files around
$remote->copy("/local/file", "host:/remote/file") or warn $!;
$remote->move("host:/remote/file", "/local/file");

# Read and write whole files
my @file = $remote->readfile("host:/remote/file");
$remote->writefile("/local/file", @file);

# Backup a file with a suffix
$remote->backup("host:/remote/oldfile", "save");

# Use secure connection methods
my $secure = new File::Remote (rsh => "/usr/local/bin/ssh",
rcp => "/usr/local/bin/scp");
$secure->unlink("/local/file");
$secure->rmdir("host:/remote/dir");

This module takes care of dealing with files regardless of whether theyre local or remote. It allows you to create and edit files without having to worry about their physical location on the network. If a file passed into a function is of the form host:/path/to/file, then File::Remote uses rsh/rcp (or ssh/scp, depending on how you configure it) to edit the file remotely. Otherwise, it assumes the file is local and passes calls directly through to Perls core functions.

The nice thing about this module is that you can use it for all your file calls, since it handles both remote and local files transparently. This means you dont have to put a whole bunch of checks for remote files in your code. Plus, if you use the function-oriented interface along with the :replace tag, you can actually redefine the Perl builtin file functions. This means that your existing Perl scripts can automatically handle remote files with no re-engineering(!).