BSD: OpenBSD, ZFS, and More
-
Ted Unangst ☛ you don't link all of libc
On OpenBSD, there is a rule that you link with libc to interface with the kernel, because that’s where the syscall stubs live. This causes a great deal of consternation for partisans of other languages, because they don’t want to link “all of libc”. But when does anything link all of libc?
-
Klara ☛ Isolating Containers with ZFS and Linux Namespaces - Klara Systems
The first building block of our multi-tenant or multi-workload configuration is OpenZFS. ZFS provides pooled storage to combine the capacity and performance of multiple storage devices while adding additional reliability. It then allows the administrator or framework to create multiple virtual filesystems on top of that pool, sharing the available free space and resources subject to configured constraints.
Each ZFS virtual file system (dataset) has a set of inherited properties that control various aspects, such as transparent compression, encryption, block/record size, quotas, reservations, and the directory where the contents are mounted. Compared to traditional file systems, this already offers more flexibility and control, but it is the ability to delegate a dataset entirely to a container that truly makes ZFS the best choice for containers.
ZFS has supported containers since its early days at Sun Microsystems through its integration with Solaris Zones. When ZFS was ported to FreeBSD, this concept was adapted to work with Jails, where it has been widely used for over a decade. Support for Linux containers arrived more recently as part of the OpenZFS 2.2 release through patches written and upstreamed by Klara for a customer.