FreeBSD FreeBSD aims to make an operating system usable for any purpose. It is intended to run a wide variety of applications, be easy to use, contain cutting-edge features, and be highly scalable, including for network servers with very high loads. FreeBSD is free software, and the project prefers the
FreeBSD license. However, they sometimes accept
non-disclosure agreements (NDAs) and include a limited number of nonfree
hardware abstraction layer (HAL) modules for specific device drivers in their source tree, to support the hardware of companies who do not provide purely libre drivers (such as HALs to program
software-defined radios so that vendors do not share their nonfree algorithms). To maintain a high level of quality and provide good support for "production quality
commercial off-the-shelf (COTS) workstation, server, and high-end embedded systems", FreeBSD focuses on a narrow set of architectures. :*
GhostBSD – a
FreeBSD-based operating system that uses the MATE desktop environment and aims to be user-friendly. :*
MidnightBSD – a
FreeBSD-based OS with
XFCE based Desktop Environment :*
Junos OS – a
FreeBSD-based
nonfree operating system distributed with
Juniper Networks hardware. :*
NomadBSD – a persistent live system for USB flash drives, based on
FreeBSD. :*
ClonOS – virtual hosting platform/appliance based on
FreeBSD. :*
pfSense – an open source firewall/router computer software distribution based on
FreeBSD. :*
OPNsense – an open source firewall/router computer software distribution based on
FreeBSD. :*
BSDRP – BSD Router Project: Open Source Router Distribution based on
FreeBSD. :*
HardenedBSD – HardenedBSD is a security-enhanced fork of
FreeBSD. :*
StarBSD – is a Unix-like, server-oriented operating system based on FreeBSD for Mission-Critical Enterprise Environment. :*
TrueOS (previously PC-BSD) – a
FreeBSD based
server operating system, previously a
desktop operating system. The project was officially discontinued in May 2020. :*
XigmaNAS – a network-attached storage (NAS) server software with a dedicated management web interface. :*
helloSystem – a GUI-focused system with a
macOS interface. :*
CheriBSD – adapted to support CHERI-MIPS, CHERI-RISC-V, and Arm Morello ISAs.
NetBSD NetBSD aims to provide a freely redistributable operating system that professionals, hobbyists, and researchers can use in any manner they wish. The main focus is
portability, through the use of clear distinctions between machine-dependent and
machine-independent code. It runs on a wide variety of
32-bit and
64-bit CPU architectures and hardware platforms, and is intended to interoperate well with other
operating systems. NetBSD places emphasis on
correct design, well-written code, stability, and efficiency. Where practical, close compliance with
open API and
protocol standards is also emphasized. A powerful
TCP/IP stack, combined with a small
footprint, make NetBSD suited to be
embedded in
networking applications, as well as to revive
vintage hardware. In June 2008, the NetBSD Foundation moved to a
2-clause BSD license, citing changes at UCB and industry applicability. Projects spawned by NetBSD include
NPF,
Rump kernels,
busdma,
pkgsrc and NVMM.
Derivatives: •
Force10 Networks FTOS– Powerful and robust operating system that runs on Force10 TeraScale E-Series
switches and
routers. •
SEIL/SMFv2– The system management
framework used by
IIJ's SEIL/X
CPE routers, built on NetBSD. •
fdgw – fdgw is a tool kit to build a minimal NetBSD
bootable disk, with a primary focus on routers. •
g4u – NetBSD based boot floppy/CD-ROM that allows easy
cloning of PC
hard drives. •
OS108 – system with graphical
desktop environment based on NetBSD. •
polyBSD/pocketSAN – Multipurpose framework for building embedded
SAN and
VPN appliances based on NetBSD. •
smolBSD – Tiny BSD system creation tool, primarily aimed at building modern, lightweight, fast micro
VMs.
OpenBSD OpenBSD is a security-focused BSD known for its developers' insistence on extensive, ongoing
code auditing for security and correct functionality, a "secure by default" philosophy, good documentation, and adherence to strictly
open source licensing. The system incorporates
numerous security features that are absent or optional in other versions of BSD. The OpenBSD policy on openness extends to hardware documentation and drivers, since without these, there can be no trust in the correct operation of the kernel and its security, and vendor
software bugs would be hard to resolve. OpenBSD emphasizes very high standards in all areas. Security policies include disabling all non-essential services and having sane initial settings; and integrated
cryptography (originally made easier due to relaxed Canadian export laws relative to the United States),
full public disclosure of all security flaws discovered; thoroughly
auditing code for bugs and security issues; various security features, including the
W^X page protection technology and heavy use of randomization to mitigate attacks. Coding approaches include an emphasis on searching for similar issues throughout the
code base if any code issue is identified. Concerning software freedom, OpenBSD prefers the
BSD or
ISC license, with the
GPL acceptable only for existing software which is impractical to replace, such as the
GNU Compiler Collection. NDAs are never considered acceptable. In common with its parent, NetBSD, OpenBSD strives to run on a wide variety of hardware. Where licenses or code quality conflict with OpenBSD's philosophy, the OpenBSD team has re-implemented major pieces of software from scratch, which have often become the standard used within other versions of BSD. Examples include the
pf packet filter, new
privilege separation techniques used to safeguard tools such as
tcpdump and
tmux, much of the
OpenSSH codebase, and replacing GPL licensed tools such as
diff,
grep and
pkg-config with
ISC or
BSD licensed equivalents. OpenBSD prominently notes the success of its security approach on its website home page. , only two remotely exploitable vulnerabilities have ever been found in its default install (an
OpenSSH vulnerability found in 2002, and a remote network vulnerability found in 2007) in a period of almost 22 years. According to OpenBSD expert Michael W. Lucas, OpenBSD "is widely regarded as the most secure operating system available anywhere, under any licensing terms." OpenBSD has spawned numerous child projects such as
OpenSSH,
OpenNTPD,
OpenBGPD,
OpenSMTPD,
PF,
CARP, and
LibreSSL. Many of these are designed to replace restricted alternatives.
Derivatives: •
LibertyBSD – Aimed to be a 'deblobbed' version of OpenBSD. There are a number of reasons as to why blobs can be problematic, according to the project. LibertyBSD began going through the process to become
Free Software Foundation FSDG certified, but ultimately never was accepted. LibertyBSD is no longer actively developed, and the project page directs people instead to
HyperbolaBSD. •
Isotop, a French project aiming to adapt OpenBSD to desktops and laptops, using
xfce then
dwm. •
fuguita – a live system based on OpenBSD for i386, amd64, and arm64
DragonFly BSD DragonFly BSD aims to be inherently easy to understand and develop for
multi-processor infrastructures. The main goal of the project, forked from FreeBSD 4.8, is to radically change the kernel architecture, introducing
microkernel-like
message passing which will enhance
scaling and
reliability on
symmetric multiprocessing (SMP) platforms while also being applicable to
NUMA and
clustered systems. The long-term goal is to provide a transparent
single system image in clustered environments. DragonFly BSD originally supported both the
IA-32 and
x86-64 platforms, however support for IA-32 was dropped in version 4.0. Matthew Dillon, the founder of DragonFly BSD, believes supporting fewer platforms makes it easier for a project to do a proper, ground-up
symmetric multiprocessing implementation. ==Popularity==