BSD init

BSD init
Name	BSD init
Developer	University of California, Berkeley, Keith Bostic, Berkeley Software Distribution
Released	1979
Programming language	C (programming language)
Operating system	BSD variants
License	BSD license

BSD init is the traditional initialization system used by Berkeley Software Distribution-derived operating systems including FreeBSD, OpenBSD, NetBSD, DragonFly BSD and historical 4.3BSD. It provides the early-boot process, runlevel-like states, process supervision hooks and orderly shutdown semantics across releases such as NetBSD 1.0, FreeBSD 5.0, OpenBSD 3.6 and DragonFly BSD 1.0. BSD init influenced later service management designs and interacted with components like rc scripts, init(8), rc.conf and the Unix philosophy as embodied by projects at Bell Labs, University of California, Berkeley and contributors such as Marshall Kirk McKusick.

History

BSD init emerged in the context of Research Unix evolution and the CSRG work at University of California, Berkeley, evolving from the simple single-process init in Version 7 Unix and earlier Unix releases. Early development occurred alongside milestones like 4.2BSD and 4.3BSD and contributors including Bill Joy and Keith Bostic adapted init behavior to BSD’s startup and shutdown needs. The system’s conventions were codified in manuals such as Unix manual pages and informed contemporary service management efforts at projects like System V Release 4 and later alternatives exemplified by systemd and launchd.

Design and architecture

BSD init follows a minimalist, monolithic-process design rooted in Unix philosophy, implementing a parent init process that adopts orphaned processes and handles SIGCHLD semantics defined by POSIX. The architecture relies on filesystem-based configuration such as /etc/rc, /etc/rc.d directories, and variables in rc.conf influencing behavior across kernels like those from FreeBSD Foundation and OpenBSD Project. Interactions with kernel process tables and facilities from libc ensure init manages process identifiers and session leaders consistent with standards from IEEE and The Open Group.

Configuration and scripts

Configuration centers on shell-based scripts located in /etc/rc.d and global files such as /etc/rc.conf and legacy entries in /etc/rc.local, authored as POSIX-compliant shell compatible with Bourne shell and influenced by authors at AT&T Bell Laboratories. Administrators tune system-wide variables, firewall rules via pf (OpenBSD) or ipfw, and service enablement for daemons like sshd, cron, syslogd and inetd using these scripts. The convention enables distribution maintainers at organizations including The NetBSD Foundation and The FreeBSD Foundation to package startup hooks and dependency hints in a predictable file-layout model.

Boot and shutdown sequence

During boot, the BIOS or UEFI transfers control to a bootloader such as boot0, GRUB alternatives or BSD boot manager which then loads a kernel that mounts root filesystems and executes init; subsequent rc scripts initialize subsystems including mountd, devd, dhclient, ifconfig and ntpd. Shutdown invokes orderly termination of daemons via signals defined by POSIX, unmounts filesystems including UFS or ZFS, and interacts with power management subsystems like ACPI to halt or reboot hardware. The sequence is documented in system manuals used by distributions and projects such as FreeBSD Handbook and OpenBSD FAQ.

Implementations and variants

Implementations appear across FreeBSD, OpenBSD, NetBSD, DragonFly BSD and older 386BSD trees, with distribution-specific wrappers and framework changes contributed by organizations like The FreeBSD Foundation, The NetBSD Foundation, and the OpenBSD Project. Some systems augment init with process supervision tools such as daemontools-like supervisors, runit, and integration points to alternative init replacements like systemd in other ecosystems, while projects at Google and Apple Inc. pursued independent launch systems in upstart and launchd.

Security and reliability considerations

Security practices include minimizing code paths run as root in early boot, hardening init scripts against environment manipulation documented by CERT Coordination Center guidance, and validating configuration via packaging policies from organizations like FreeBSD Foundation and OpenBSD Project security advisories. Reliability depends on correct signal handling, robust handling of zombie processes per POSIX semantics, and safe ordering of services such as sshd and named to avoid privilege-escalation or denial scenarios noted in security bulletins by US-CERT and others.

Comparison with other init systems

Compared with System V init used in many AT&T-influenced distributions, BSD init emphasizes script-based, rc-style orchestration rather than numbered runlevels and rc.d symlink schemes popularized in Linux distributions. Against modern alternatives like systemd and launchd, BSD init remains simpler, smaller in scope, and more aligned with the Unix philosophy championed by figures at Bell Labs and the University of California, Berkeley, though it lacks integrated features such as socket activation, cgroup management, and complex dependency resolution found in those projects.

Category:BSD software