Free large file transfer software for linux

VFU is console (text mode) file manager for UNIX/Linux.

During the years I tried to make short attractive list of features which VFU has. Attractive as Advertising above :) and it does not seem to work... at least it didnt for me and I never liked it.

I made all possible to make VFU cover all file managing needs and offer large set of behaviour options. If I succeeded or not, you can decide for yourself but without trying I believe noone can say for sure.

Installation:

1. how to compile vfu

run `make from vfu base directory

this should compile everything

to compile each part of vfu manually do this:

-- go to `vslib directory
-- run `make
-- go to `vfu directory
-- run `make

if something goes wrong, check these:

-- if your `curses.h file locations is not `/usr/include/ncurses
you have to change this in the Makefile.

-- if vslib library is not in the `../vslib directory you also
have to change this in the Makefile.

2. how to install vfu

run `install script from vfu base directory

install script checks if all required files are available/built and then does this:

cp vfu/vfu rx/rx_* /usr/local/bin
cp vfu.1 /usr/local/man/man1
cp vfu.conf /usr/local/etc

3. how to install vfu manually

-- you have to copy `vfu in the `/usr/local/bin or
`/usr/bin directory and set mode to 755 `rwxr-xr-x
the owner is not significant ( root is also possible ).

-- there is preliminary man page ( vfu.1 ) which could be
copied to /usr/man/man1.

-- copy all `rx/rx_* tools to /usr/local/bin
-- install Net::FTP perl module if needed.
(this is used for FTP support)

WARNING: make sure to remove all old personal cache files!

Apple Disk Transfer ProDOS (or ADTPro for short) transfers diskettes and logical disk images between Apple ][-era computers and the modern world. If youre familiar with the original ADT, ADTPro extends ADTs reach by working with more logical disk formats, drive types, communications devices, and host operating systems.
Main features:
- Compatibility with any device ProDOS can read
- Compatibility with any Apple ][ (or clone) computer with 64k memory
- Compatibility with many logical disk image formats: .DSK, .PO, .NIB, 2IMG
- Server compatibility with original ADT client program
- Server compatibility with Windows, Mac OSX, Linux, and probably Solaris
- Ability to bootstrap an Apple ][ from bare metal over serial or cassette ports
- Ability to send floppies in "batch" mode without having to name each one
Server
The server program runs on a computer capable of running Java. Depending on how you want to connect to your Apple, you might also need a serial port and cables, an Uthernet card for your apple, or a couple of audio patch cables. The server offers a compact user interface that shows what communications are taking place between the host and the Apple ][.
The servers primary role is to send and receive disk images as requested from the client. But if you have recently acquired an Apple and a disk drive, and you have no software for it - youre in a bit of a tricky situation if you want to move software from the Internet all the way to your shiny new Apple. ADTPros server can help get you get bootstrapped.
Client
The client side runs on the Apple ][. It handles most of the user interaction. When choosing disks/volumes to transfer, anything that ProDOS can see is fair game. Transferring data occurs with a 20k buffer on the Apple, so all transfers are broken up into 20k chunks. A progress indicator shows how far it is into the current chunk, as well as a running count of the total progress.
Enhancements:
- This release has been enhanced with Jean-Marc Boutillon (Deckard)s FASTDSK fast Disk II reading routines.
- This results in a speed boost of 25%-33% for Disk II to host transfers.
- Bootstrapping operations have been reduced, as there is no longer a dependency on ProDOS BASIC.

Audio Transcriber records large audio samples, like a tape or radio broadcast, to your hard drive and splits it into tracks to be burned onto CD-R media.

The goal of Audio Transcriber is to make it easy to transfer audio tapes, LPs, or radio broadcasts to tracks on CD-R/CD-RW.

Fast Secure File System exports existing directories securely over the network, letting users store and retrieve encrypted data in a scalable and transparent way. FSFS is written in C and works on GNU/Linux systems on x86 and PPC architectures, with help from FUSE and OpenSSL.
File systems are easily the most evident, from the point of view of users, component of an operating system. Through file systems it is possible to organize data in a wide variety of ways, and access resources through a common interface.
Users can nowadays not only store and retrieve documents, but also find information on running processes and system settings (through ProcFS), access and manipulate e-mail (for example with GmailFS), or perform several other operations.
In several circumstances and scenarios it is desirable to protect stored files and directories from manipulation by unknown or malicious users: financial or health-related data, confidential documents, or any kind of personal or sensitive data may need to be stored securely, in such a way that it can not be examined or modified freely by third parties.
Most file systems do not take action in this sense, and external cryptographic utilities are sometimes employed to secure data before storage. While this can be a perfectly secure solution, it is not transparent to users.
Distributed file systems propose efficient ways of accessing data remotely as if it resided on the local machine; when it comes to dealing with securely stored data as in the examples above, care must be taken to preserve confidentiality and integrity also during network transfer.
Not all distributed file systems accomplish this task, weakening the overall security of the system, or do so inefficiently, making it inconvenient for users.
FSFS is a secure, distributed file system in users space, written in C with much help from FUSE and OpenSSL. It lets users store and retrieve data securely and transparently, knowing that it is protected both on permanent storage devices and while in transit over the network.
It is also concerned with scalability, therefore separates data cryptography from the server, leaving it to the clients; this approach is similar to the one used in CFS, and opposite to those taken on by other secure file system solutions (like NFS on top of IPsec).
FSFS is written as a pair of user space daemons that act as client and server. Because of this, it needs no kernel support (unlike NFS over IPsec), save the FUSE loadable kernel module on clients, included in Linux since 2.6.14; servers dont use FUSE and depend only on user space OpenSSL libraries.
Servers export an existing file system (of virtually any kind) to clients over the network through two separate channels: a TLS connection set up with OpenSSL, and a clear channel. Requests from the clients to the servers are sent via the TLS socket, thus they are encrypted and authenticated, according to TLS v1 specifications, by the channel itself and decrypted on receipt, as they are usually very short and the relevant cryptography does not constitute a great overhead; simple server replies undergo the same process.
Cryptography in this case happens at both ends of the transmission.
In a distributed file system, large amounts of data may be transferred between clients and servers, thus encrypting and decrypting everything may become too cumbersome for both parties, and as more clients are added to the system the server may severely lose performance; moreover, file data should be stored encrypted anyway, so the cryptography could be moved to the clients, in such a way that each encrypts data before a write operation sends it over the network to the server, and decrypts it after a read retrieves it.
This way servers only deal with TLS details and can concentrate on serving client requests by doing the relevant I/O on the underlying, "physical" file system. As the data is already encrypted, it does not need to go through the TLS channel and the corresponding overhead, but can be sent via the clear channel, provided the messages are authenticated.
Enhancements:
- This release fixes two bugs. One bug related to socket creation and would cause problems on some systems (namely OpenSUSE 10.2). The other bug related to server configuration creation when using the Python configuration utilities. Users dont need to upgrade to this release if theyre not experiencing problems or are not using the Python configuration utilities.

libptp2 is a library used to communicate with PTP devices like still imaging cameras or MP3 players (KODAK mc3).
You can download files or tweak camera properties using ptpcam program boundled with libptp2.
Supported Cameras
The list of cameras implementing PTP is constantly growing. Most (if not all) USB still cameras designed after 2002 are supporting PTP. Below is the list of vendors implementing PTP in their cameras:
- Kodak
- HP
- Nikon
- Canon
- Panasonic
- Olympus
- Konica
- Minolta
- Fuji
- Ricoh
- Sony
More are comming...
Please note that if your camera is supporting PTP it does not mean that it is capable of performing all PTP operations (like trigerring capture, uploading files or tweaking properties). Sony cameras are good example of poor PTP implementation where the only thing you can do is downloading files. Sony even breaks the USB specification assigning all its cameras the same product/vendor IDs so dont buy Sony if you want to stay out of problems.
Currently most PTP features are supported. Uploading/downloading files, taking pictures and setting camera properties is supported as long as your camera supports it. However there are many Vendor Extensions that are not supported.
For example Canon uses some proprietary extension operations to take pictures (entering capture mode, extending lens and so on), Nikon introduces proprietary PTP properties.
Unfortunately I have access to couple of Kodak cameras only so to help support extension features you may send me a patch or donate/lend the camera.
Enhancements:
- A number of bugs were fixed, including leaving the camera in an unpredictable state when an I/O error occurs.
- The projects own reimplementation of the old libusb interface (IOCTL_USB_BULK) is used instead of the new URB interface, which is 20% to 50% slower and sometime leads to I/O errors.
- File time preservation across download was added.
- Better capture support was added.
- A bug that caused files over 2MB to be corrupted while downloading was fixed.
- The --loop-capture feature was added.
- Configure errors and parralel build with make -j were fixed.

FileSystemStorage is a project that provides FileSystem storage for Archetypes.

FileSystemStorage is an Archetype storage for storing data on FileSystem This storage is used to avoid ZODB to grow quickly when using a lot of large files.