ngacl is an effort to give Linux and its filesystems a full blown ACL system, similar to that used by NFSv4 and Windows. With this software, you have 13 different access rights, dynamic inheritance, and audit ACLs. The implementation is filesystem-independent because the kernel parts are an LSM module. In addition, there is a Samba-VFS module that enables you to alter ACLs with the Windows ACL editor.
nntpfs is a FUSE module for mounting the data offered by NNTP servers. Read-only access to the servers is provided. The Network News Transfer Protocol or NNTP is an Internet application protocol for the distribution of news and occasionally binary files. Usenet represents the most common usage of the NNTP protocol. The Filesystem in Userspace (FUSE) interface allows user application code to create its own filesystems and publish them using kernel support.
Noca is a shared library that prevents the page cache from filling with data that we know we only need once. It hooks read, lseek, and close. If some conditions are met, they trigger an fadvise call so that the memory is freed. An example of its use could be to limit the page cache of a "tar zxvf" operation to a specified size, no matter how big the archive is.
openMosix is a a set of extensions to the standard Linux kernel allowing you to build a cluster of out of off-the-shelf PC hardware. openMosix scales perfectly up to thousands of nodes. You do not need to modify your applications to benefit from your cluster (unlike PVM, MPI, Linda, etc.). Processes in openMosix migrate transparently between nodes and the cluster will always auto-balance.
palmfs is a PalmOS filesystem access software for Linux, based on FUSE. It consists of two parts, a client and a server. The client is a FUSE-based application running on the Linux system. The server part is a PalmOS application that actually executes commands sent by the client. It is intented to support various communication ports and to access the PalmOS internal filesystem as well as expansion cards.
petardfs is a FUSE filesystem designed to hoist your applications with errors. With no configuration, petardfs takes a base filesystem and exposes it through FUSE. An XML configuration file is used to tell petardfs which files to report errors for and what error code to use. For example, foo.txt can have an EIO error at bytes 34 to 37. There is explicit support for errors such as EAGAIN and EINTR, where petardfs will only report such transient errors a nominated number of times. This is handy for testing applications that support such I/O conditions gracefully.