Free filesystems software for linux

TSKmount-Fuse is the filesystem of deleted files.

TSKmount, is a free Fuse filesystem written in perl and based on The Sleuth Kit tools. It is intended to provide an easy way to recover deleted files over ext2, fat and ntfs filesystems.

Short HowTo:

Mounting device /dev/hda5 on /tmp/fuse empty directory:

tskmount /dev/hda5 /tmp/fuse
### wait the "Ready" message before going to /tmp/fuse ###


Unmounting filesystem:

fusermount -u /tmp/fuse

See common options:

tskmount --help

All I wanted is a simple way to format DVD-RAM, create UDF filesystems, set or remove the write protection and informations about the DVD-RAM.

KDVD-RAM Tools are a combination with service menu, shell script and kdialog.

cryptmount project is a utility for GNU/Linux operating systems which allows an ordinary user to mount an encrypted filesystem.
cryptmount was written to address differences between the capabilities of the loopback device and the newer, preferred, device-mapper mechanisms of the 2.6 kernel series, which make it more difficult for a non-root user to configure the devices necessary for access to an encrypted filesystem.
After the initial configuration of the encrypted filesystem, an ordinary user can mount and unmount the filesystem on demand, solely by providing the decryption password.
Enhancements:
- A new interactive tool to assist with initial setup of encrypted filesystems, support for reading/writing OpenSSL key files via libgcrypt, facilities for translating between key files stored in different formats, and support for improved dismantling of loopback filesystems during system shutdown.

oyepa project is a tagging file system (a fake but working one); a way to organize (and locate) your documents through the use of tags.
Main features:
- works with documents of any type: text, spreadsheets, images, multimedia files, source code trees, etc
- automatically prompts you to tag any document you create (but only if that doc is being created in one of the dirs you specified)
- lets you store directory trees as single documents (think of, e.g., a source code tree, or a set of pictures taken at the same occasion: you just tag the directory itself, not all the files it contains)
- tag information is stored in the filename, which ensures portability (as long as you dont move your files to filesystems which only support very short filenames) and low risk of losing your documents metadata (since filesystems dont corrupt/accidentally delete the name of a file that often)

anyfs-tools is a unix-way toolset for recovering and converting filesystems.
SYNOPSIS
build_it [-qvV] directory inode_table
anysurrect [-b blocksize] [-i input_inode_table] [-p path_prefix] [-u file_umask] [-U dir_umask] [-qvV] device inode_table
reblock [-nqvV] inode_table device blocksize
build_e2fs [ -c|-l filename ] [-b blocksize] [-f fragment-size] [-g blocks-per-group] [-i bytes-per-inode] [-j] [-J journal-options] [-N number-of-inodes] [-n] [-m reserved-blocks-percentage] [-o creator-os] [-O feature[,...]] [-q] [-r fs-revision-level] [-R raid-options] [-v] [-F] [-L volume-label] [-M last-mounted-directory] [-S] [-T filesystem-type] [-V] inode_table device [blocks-count]
mount -t any -o inodetable=file.it[,other_mount_options] device dir
build_it reads from directory recursively information about all filesystem inodes using filesystem driver (read-only maybe) for Linux OS and saves it to external inode table.
anysurrect search on device files proceeds from knowing different file types structure. Information about founded files also saves to external inode table.
reblock change filesystem block size. reblock using information from inode table change each files fragments placing so, that it was align by blocks bounds with new size.
build_e2fs proceeds from external inode table information for building ext2fs filesystems on device.
anyfs filesystem driver for Linux allows to mount device using inode table information. At mounted filesystem will be allow so file operations as deleting, moving files; making symbolic and hard links, special files; changing file access permissions. All this changes saves on unmounting to the same external inode table file and doesnt affect the device.
Usage:
Convert filesystems
anyfs-tools allows to convert filesystems. The only one requirement for source filesystem exist: there is must be FIBMAP system call ioctl(2) support in the filesystem driver (maybe read-only) for Linux OS.
Destination filesystem at that moment maybe only ext2fs. But its quite possible, that in future there are will other filesystem building support. At the first it must be interest for filesystem maintainers so as existing of convenient tool for converting of other filesystems to their one, not requesting much free space for saving of all user data, certainty will increase of the filesystem users.
In general, an applying anyfs-tools order for filesystem converting must be next:
1) build_it for reading all informaton about files placing and access permissions and saving it to external inode table file.;
2) anyfs driver for checking existence of all needed files and maybe searching of files requiring of separately saving (e.g, files eith size less than 4 Kb for ReiserFS);
3) maybe reblock for changing filesystem blocksize in occurence when destination filesystem dont support the same blocksize for this device, that source one;
4) at last ext2fs filesystem builds by build_e2fs.
Recovering damaged filesystem
For recovering files from filesystem at first intended anysurrect. After it using possible applying of anyfs filesystem drive for founded files viewing and maybe reading and saving it to another filesystem. Driver also may allow to sort files into directories so as user need in it, rename files as it necessary. At last also possible to build new filesystem with help of build_e2fs.
Recovering files from not damaged filesystem
For file recovering an aplying anyfs-tools tools order is the same that for recovering damaged filesystem excepting that at the begining you must execute build_it for reading about present filesystem file placing.
Enhancements:
- Fix anyfs building with kernel version >=2.6.19
- Some other building fix
- Fix new (from v0.84.10) i/o buffer bug in anysurrect.
- Extremally optimize anysurrect.
- Add -s option to build_it.
- Add support of converting from ntfs-3g by anyconvertfs.

HardInfo is a benchmark tool and system information for Linux systems.
Main features:
Get information about your computer:
- The Processor
- Operating System
- Languages
- Sensors
- Filesystems
- Shared Directories
- Display
- Network Interfaces
Its devices (and what controls them):
- Kernel Modules
- PCI Devices
- USB Devices
- Printers
- Input Devices
- Storage
Benchmark:
- ZLib
- MD5 and SHA1
- And generate nicely-formatted HTML reports!
Enhancements:
- Maintenance version.
- Mostly bugfixes, plugged memory leaks.
- Minor feature enhancements.

live-initramfs is a fork from Casper by Canonical. The project is used to build an initramfs suited to boot live systems.

live-initramfs is a hook for the initramfs-tools, used to generate a initramfs capable to boot live systems, such as those created by live-helper(7). This includes the Debian Live isos, netboot tarballs, and usb stick images.

At boot time it will look for a (read-only) media containing a "/live" directory where a root filesystems (often a compressed filesystem image like squashfs) is stored. If found, it will create a writable environ‐ ment, using unionfs, for Debian like systems to boot from.

To modify the code you can follow the below process:

Checkout or install live-initramfs

svn co svn://svn.debian.org/debian-live/dists/trunk/live-initramfs/

Then build to match your target platform (i.e. if target is lenny then build with lenny) with debuilder inside the live-initramfs (debuilder is part of devscripts package):

debuild -us -uc -b

Then copy the .deb generated to config/chroot_local-packages.