Free file systems software for linux

All System Info is a system info SuperKaramba theme. Simple english version...
It shows:
- System Info
- CPU usage
- Network Usage
- Memory Load
- HDD usage

FileSystem Investigator is a platform independent file system viewer and data extraction tool. It allows the user to:

* View the contents of the target file system in a forensicly safe manner, bypassing the normal operating system mechanisms.
* Extract files and whole directory trees of files from the source filesystem.

Since it is written in platform-neutral Java, it can be used to examine filesystems outside their native environment. For example, it can be used to view a Linux filesystem while running under Windows.

FileSystem Investigator directly accesses the source disk and processes the data using it own built in filesystem drivers. This ensures that it is safe to use FileSystem Investigator for forensic investigations.

FileSystem Investigator will never write to the source media thus important timestamps are preserved. FileSystem Investigator can also read disk-image files such as those created by dd.

Files and whole directory structures can be extracted easily from the source drive and stored for further use or analysis. Due to limitations imposed by Java, special files such as device nodes, pipes, sockets and links, cannot be extracted.

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.

GFS (Global File System) is a cluster file system. It allows a cluster of computers to simultaneously use a block device that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads and writes to the block device like a local filesystem, but also uses a lock module to allow the computers coordinate their I/O so filesystem consistency is maintained. One of the nifty features of GFS is perfect consistency -- changes made to the filesystem on one machine show up immediately on all other machines in the cluster.

GFS consists of a set of kernel patches and userspace programs.
The GFS lock module lock_dlm depends on CMAN and DLM.
The GFS lock module lock_gulm depends on GULM.
The GFS lock module lock_nolock depends on nothing.
Some GFS tools depend on the iddev library.

Building and Installing

1. build and install from cluster tree
cd cluster
./configure --kernel_src=/path/to/kernel
make; make install

- This builds and installs kernel modules, libraries and user programs.

- Kernel modules can also be built within the original kernel source tree by applying the kernel patches from cman-kernel/patches, dlm-kernel/patches and gfs-kernel/patches.

2. build device mapper user space
cd device-mapper
./configure
make; make install

3. build lvm2/clvm
cd LVM2
./configure --with-clvmd --with-cluster=shared
make; make install
LVM2/scripts/clvmd_fix_conf.sh /usr/lib

Load kernel modules

depmod -a
modprobe dm-mod
modprobe gfs
modprobe lock_dlm

Modules that should be loaded: lock_dlm, dlm, cman, gfs, lock_harness and dm-mod if device-mapper was built as a module.

Startup procedure

Run these commands on each cluster node:

> ccsd - Starts the CCS daemon
> cman_tool join - Joins the cluster
> fence_tool join - Joins the fence domain (starts fenced)
> clvmd - Starts the CLVM daemon
> vgchange -aly - Activates LVM volumes (locally)
> mount -t gfs /dev/vg/lvol /mnt - Mounts a GFS file system

Shutdown procedure

Run these commands on each cluster node:

> umount /mnt - Unmounts a GFS file system
> vgchange -aln - Deactivates LVM volumes (locally)
> killall clvmd - Stops the CLVM daemon
> fence_tool leave - Leaves the fence domain (stops fenced)
> cman_tool leave - Leaves the cluster
> killall ccsd - Stops the CCS daemon

Self-certifying File System provides a secure, global network file system with decentralized control.

SFS is a secure, global network file system with completely decentralized control. SFS lets you access your files from anywhere and share them with anyone, anywhere.

Anyone can set up an SFS server, and any user can access any server from any client.

At the same time, SFS uses strong cryptography to provide security over untrusted networks.

Thus, you can safely share files across administrative realms without involving administrators or certification authorities.

The goal of the Parallel Virtual File System (PVFS) Project is to explore the design, implementation, and uses of parallel I/O. PVFS serves as both a platform for parallel I/O research as well as a production file system for the cluster computing community. PVFS is currently targeted at clusters of workstations, or Beowulfs.
The PVFS project is conducted jointly between The Parallel Architecture Research Laboratory at Clemson University and The Mathematics and Computer Science Division at Argonne National Laboratory.
Additional funding for the PVFS project comes from NASA Goddard Space Flight Center Code 930 and The National Computational Science Alliance through the National Science Foundations Partnerships for Advanced Computational Infrastructure.
Main features:
- Compatibility with existing binaries
- Ease of installation
- User-controlled striping of files across nodes
- Multiple interfaces, including a MPI-IO interface via ROMIO
- Utilizes commodity network and storage hardware
PVFS supports the UNIX I/O interface and allows existing UNIX I/O programs to use PVFS files without recompiling. The familiar UNIX file tools (ls, cp, rm, etc.) will all operate on PVFS files and directories as well. This is accomplished via a Linux kernel module which is provided as a separate package.
PVFS is easy to install. The Quick Start page describes how to set up a simple installation. Scripts and test applications are included to help with configuration, testing for correct operation, and performance evaluation.
PVFS stripes file data across multiple disks in different nodes in a cluster. By spreading out file data in this manner, larger files can be created, potential bandwidth is increased, and network bottlenecks are minimized. A 64-bit interface is implemented as well, allowing large (more than 2GB) files to be created and accessed.
Enhancements:
- fixes to build under redhat 2.4.20-20.9 kernel
- checks for missing headers on ancient 2.4 kernels
- removal of unused fields from metadata and control messages
- updated pvfsd rc file
- handle various combinations of redhat kernel patches
- fixes to kpvfsd that had previously been fixed in user space
- fix for sftp directory reading problems
- fix to avoid oopses on clients when bad errno values returned
- adjustments to deal wiht gcc 3.4.0 issues
- fixes to work with redhat 9
- fixes to compile kernel code for xx86_64
- updated logging intrastructure
- fixes to error reporting
- update of makefile in pvfs core
- fix to bug in pvfs_open.c where pcount < 0 caused errors
- removed duplicated code in mgr
- fix for problem with bvrecv() optimization
- more unused code removal
- adjustments to keep portland group compiler happy
- removed sd_path from metadata
- new iod.rc and mgr.rc files
- fixes to chmod
- fixes to get correct fs_ino back to clients
- multiple mtime fixes
- streamlined pvfs file detection
- shared library building
- fixed closing socket bug in iod
- reordered messaging in mgr to iods to improve concurrency
- rename fix
- improved metadata file checking
- do_access permission fixes
- fix for "iod out of space" client hang
- cleaner dead socket handling, including special handling of case where mgr would close fds that clients were using
- noninteractive mkmgrconf

Open Journal Systems (OJS) is a journal management and publishing system that has been developed by the Public Knowledge Project through its federally funded efforts to expand and improve access to research.
Main features:
- OJS is installed locally and locally controlled.
- Editors configure requirements, sections, review process, etc.
- Online submission and management of all content.
- Subscription module with delayed open access options.
- Comprehensive indexing of content part of global system.
- Reading Tools for content, based on field and editors choice.
- Email notification and commenting ability for readers.
- Complete context-sensitive online Help support.
OJS assists with every stage of the refereed publishing process, from submissions through to online publication and indexing. Through its management systems, its finely grained indexing of research, and the context it provides for research, OJS seeks to improve both the scholarly and public quality of referred research.
OJS is open source software made freely available to journals worldwide for the purpose of making open access publishing a viable option for more journals, as open access can increase a journals readership as well as its contribution to the public good on a global scale (see PKP Publications).