DAPL (Direct Access Provider Library) is a transport-independent, platform-independent, high-performance API for using the remote direct memory access (RDMA) capabilities of modern interconnect technologies such as InfiniBand, the Virtual Interface Architecture, and iWARP. This is the reference implementation of that specification by the DAT Collaborative who maintain the DAPL API.
leJOS is a Java-based replacement firmware (OS) for LEGO Mindstorms programmable bricks, including RCX and NXT. It supports threads, exceptions, synchronization, floating point arithmetic, strings, and so on, but there is no garbage collection yet. It is also designed to be portable to other small devices.
Squashfs is a highly compressed read-only filesystem for Linux. It uses zlib to compress files, inodes, and directories. All blocks are packed to minimize the data overhead, and block sizes of between 4K and 1M are supported. It is intended to be used for archival use, for live CDs, and for embedded systems where low overhead is needed.
QP is a family of lightweight software frameworks for building responsive and modular real-time embedded applications as systems of cooperating, event-driven active objects (actors). The QP family consists of QP/C, QP/C++, and QP-nano frameworks, which are all strictly quality controlled, superbly documented, and commercially licensable. The behavior of active objects is specified in QP by means of hierarchical state machines (UML statecharts). The frameworks support manual coding of UML state machines in C or C++ as well as automatic code generation by means of the free QM modeling tool. All QP frameworks can run on bare-metal MCUs, completely replacing a traditional RTOS. Ports and ready-to-use examples are provided for all major CPUs, such as ARM Cortex-M, ARM7/9, MSP430, C28x, C55x, RX, R8C, AVR32, AVRMega, PIC24/dsPIC, as well as Arduino and mbed. QP/C and QP/C++ can also work with a traditional OS/RTOS, such as: POSIX (Linux, QNX), Windows, VxWorks, ThreadX, and uC/OS.
Plash is a sandbox for running GNU/Linux programs with minimum privileges. It is suitable for running both command line and GUI programs. It can dynamically grant Gtk-based GUI applications access rights to individual files that you want to open or edit. This happens transparently through the Open/Save file chooser dialog box, by replacing GtkFileChooserDialog. Plash virtualizes the file namespace and provides per-process/per-sandbox namespaces. It can grant processes read-only or read-write access to specific files and directories, mapped at any point in the filesystem namespace. It does not require modifications to the Linux kernel.
JTMOS stands for "Jari Tuominen's Minimal Operating System". The JTMOS operating system project aims to create a fully functional multitasking x86 operating system. It primarily targets low-end systems with small hard disks, preferably i586 family or newer. Currently focus in the project is on communication, TCP/IP stack, and building up FAT file system support. JTMOS mimics some features from Linux-style operating systems like the root directory system. JTMOS can already boot up from DOS, or independently from hard disk or floppy disk with its own custom bootloader.
LUFS is a hybrid userspace filesystem framework supporting many "exotic" filesystems (localfs, sshfs, ftpfs, httpfs, socketfs, freenetfs, and nutellafs) transparently for any application. It can be regarded as doing the same job as the VFS (virtual filesystem switch) in the kernel: it is a switch, distributing the filesystem calls to its supported filesystems. However, LUFS filesystems are implemented in userspace. This would be a drawback for local filesystems where the access speed is important, but proves to be a huge advantage for networked filesystems where the userland flexibility is most important.
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.