NextBSD

Last updated
NextBSD
NextBSD logo.png
Developer Jordan Hubbard, Kip Macy
Written in C
OS family Unix
Working stateAbandoned as of 2019, no visible changes since 2016.
Source modelOpen source
Initial release2015;10 years ago (2015)
Latest release Beta / 2015;10 years ago (2015)
Repository https://github.com/NextBSD/NextBSD
Available inEnglish
Platforms Intel 80386
Kernel type Monolithic
Userland NextBSD
Default
user interface
Command-line interface
License BSD licenses
Official website web.archive.org/web/20161215232355/http://nextbsd.org/

NextBSD is a fork of the FreeBSD operating system. As of 2019 the website seems defunct, and the later commits on GitHub date from October 2019. The Wayback Machine captures of the website after 2016-12-15 are domain squatter pages and as of 2021-03-17 the site is redirecting to a fake "Apple Support" page.

Contents

Features

The basic features of launchd , notifyd, asld, and libdispatch work.

These can be installed by cloning the NextBSD repository from GitHub, building GENERIC or MACHTEST kernels, installing a new world on an existing 10.x or CURRENT system, and then following the instructions in the README.

Launchd will start the initial jobs that are part of the repo now.

Planned Features

The project refers to an installer as the first planned milestone on their website.

Future plans include convert to rc and tying notifyd in to potential consumers.

History

NeXTBSD was announced by Jordan Hubbard and Kip Macy in August 2015 at the Bay Area FreeBSD Users Group (BAFUG).

Relationship to FreeBSD

NeXTBSD is based on the FreeBSD-CURRENT kernel while adding in Mach IPC, Libdispatch, notifyd, asld, launchd, and other components derived from Darwin, Apple's open-source code for macOS.

Technology

Basic Architecture

Mach Kernel Abstractions

Tasks

The units of resource ownership; each task consists of a virtual address space, a port right namespace, and one or more threads. (Implemented as an extension to a process.)

Threads

The units of CPU execution within a task. Simple extension to kthreads.

Address space

In conjunction with memory managers, Mach implements the notion of a sparse virtual address space and shared memory. (No modifications)

Memory objects

The internal units of memory management. Memory objects include named entries and regions; they are representations of potentially persistent data that may be mapped into address spaces. (Unsupported)

Ports

Secure, simplex communication channels, accessible only via send and receive capabilities (known as port rights).

IPC

Message queues, remote procedure calls, notifications, semaphores, and lock sets. (Mach semaphores and lock sets are not supported).

Time

Clocks, timers, and waiting - (rudimentary shims).

Standards adherence

Current BSD operating system variants support many of the common IEEE, ANSI, ISO, and POSIX standards, while retaining most of the traditional BSD behavior. Like AT&T Unix, the BSD kernel is monolithic, meaning that device drivers in the kernel run in privileged mode, as part of the core of the operating system.

A selection of significant Unix versions and Unix-like operating systems that descend from BSD includes:

See also

References

Bibliography