Warewulf is an operating system management toolkit designed to facilitate large scale deployments of homogeneous and heterogeneous systems on physical, virtual and cloud based infrastructures. Originally, the Warewulf project pioneered the concept of stateless computing in HPC, setting the standard for large-scale cluster provisioning. It provided two functions, provisioning and monitoring but the two functions did not communicate within Warewulf itself, nor was it possible to hook other functions directly into Warewulf itself. Today, Warewulf is more than just a basic provisioning and monitoring solution as it now implements an abstract, object-oriented data store and a modular interface that facilitates a highly extensible, customizable feature set. Current and planned modules include monitoring (operating system, services, filesystems, etc.), provisioning, power management, user management, configuration management, event/trigger handling and notification, scheduler integration, cloud services (both local and remote), etc.
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.
Contiki is an open source, highly portable, networked, multi-tasking operating system for the Internet of Things. Contiki includes a multitasking kernel, a TCP/IP stack and a set of application programs, and a low-power radio communication stack. It is written in C and designed to be very small: it runs comfortably in a few kilobytes of RAM.
The stmpclean utility removes old files (and old empty directories) from the specified directory. It is meant to be used to clean directories such as "/tmp" where old files tend to accumulate. stmpclean never removes files or directories owned by root, which is a feature, not a bug. Great care is taken while descending into the directory, and the operation is secure. Anything that's not a directory, regular file, or symbolic link is also left alone (because programs like screen(1) create sockets and FIFOs under /tmp and expect them to be long-lived). Unlike other programs that do the same task, stmpclean never forks and consumes limited amount of memory. If stmpclean determines a race condition it will log the situation and exit with a failure.
Rocks is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters. Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users). Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
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.
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.
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.