MirBSD originated as a patch set against OpenBSD-current, an ultra secure operating system and NetBSD derivate, and has since also incorporated changes from NetBSD, a 4.4BSD-derived ultra portable operating system. It features bugfixes, code removal for the sake of simplicity, and feature enhancements over stock OpenBSD as well as a much more up-to-date GNU toolchain, careful integration of patches from other projects (such as KAME), and many improvements. It works on the Intel Pentium and some 80486 machines with more than 32 MiB RAM and the SPARC, and a port to the PowerPC Macintosh is in preparation.
The Dazuko project provides a virtual device driver allowing (userland) applications to execute online file access control. It was originally developed by Avira GmbH (formerly known as H+BEDV Datentechnik GmbH) to allow on-access virus scanning. Other uses include a file-access monitor/logger or external security tools. Dazuko operates by intercepting file access calls and passing the file information to a userland application. The application then has the opportunity to tell the virtual device driver to allow or deny the file access. The application also receives information about the file access event, such as accessed file name, type of access, process id, and user id.
HelenOS is a microkernel-based multiserver operating system designed from scratch. By decomposing the operating system functionality into tens of isolated but intensively communicating userspace servers, it provides a computing environment that has several virtues such as flexibility, increased robustness, well defined explicit interfaces, and smaller complexity of individual components. HelenOS does not aim to be another clone of Unix or some other legacy system and is not POSIX-compliant (even though it may seem POSIX-similar at times). Instead, the goal has been to design it according to what is the most elegant and right thing to do. What makes HelenOS unique among the other multiserver operating systems is its multiplatform and multiprocessor microkernel. It will run on seven different processor architectures ranging from a 32-bit uniprocessor little-endian ARMv4 to a 64-bit multicore big-endian UltraSPARC T1.
DragonFly belongs to the same class of operating systems as other BSD-derived systems and Linux. It is based on the same Unix ideals and APIs and shares ancestor code with other BSD operating systems. DragonFly is differentiated from other operating systems in its class by, among others, the HAMMER file system, Virtual Kernels, swapcache, and the pervasive use of soft token locks. DragonFly provides an opportunity for the BSD base to grow in an entirely different direction from the ones taken in the FreeBSD, NetBSD, and OpenBSD series.
flashboot for OpenBSD is a set of makefiles, scripts, and support tools to build an OpenBSD image suitable for booting from read-only media, such as flash memory. The default image (smaller than 5Mb) is an image for a firewall/router with support for IPsec, SSH, IPv4 and IPv6 packet filtering, DHCP (client and server), and PPPoE. This image may be further trimmed or extended by editing the packing list files included in the distribution.
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.
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.