Burn.awk is a character-mode, dialog-based frontend to the cdrtools burning software. It is only designed to burn data CD-R or CD-RW, but does it well. Despite its small size it is quite versatile. It supports SCSI writers (and IDE too, through Linux ide-scsi gateway), SCSI or IDE CDROMs, limited auto-detection, ISO image extraction, mastering and burning, direct burning of a directory, direct CD-to-CD copy, tray ejection and closing, CD-RW blanking, configuration dialogs, and saving.
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.
The Heirloom Toolchest is a collection of standard Unix utilities. It was derived from original Unix material released as open source by Caldera and Sun, and contains multiple versions of each utility corresponding to SVID3/SVR4, SVID4/SVR4.2MP, POSIX.2-1992/SUSV2, POSIX.1-2001/SUSV3, and 4BSD (SVR4 /usr/ucb). It processes lines of arbitrary length and in many cases binary input data, supports characters in UTF-8 and many East Asian encodings, and contains more than 100 individual utilities including bc, cpio, diff, ed, file, find, grep, man, nawk, oawk, pax, ps, sed, sort, spell, and tar. Extensive documentation is included.
INL Splitter allows developers to keep a class implementation and interface in a single .inl file, basically inlining all class member functions. This simple script will split the .inl file, placing the function bodies in a .cc file, and the class definition and prototypes in the .h file.
LMDBG is a collection of small tools for collecting and analyzing the logs of malloc/realloc/memalign/free function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks and double frees. However, unlike others, LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze an application on a per-module basis.