Home > Articles > Operating Systems, Server > Linux/UNIX/Open Source

BSD: The Other Free UNIX Family

There are a lot of options in the Free UNIX market at the moment. Everyone's favorite buzzword is Linux, and Sun is in the process of releasing Solaris under a Free Software license. One family, however, receives less attention than it is due. Berkeley Software Distribution (BSD) has grown into almost a complete replacement for UNIX, with numerous enhancements. David Chisnall explains why the BSD family has found its way into a large number of systems and what these systems can do for you.
Like this article? We recommend

There are a lot of options in the Free UNIX market at the moment. Everyone’s favorite buzzword is Linux, and Sun is in the process of releasing Solaris under a Free Software license. One family, however, receives less attention than it is due.

On March 9, 1978, the University of California at Berkeley released a set of patches to the Sixth Edition of the UNIX Timesharing System. These patches were licensed very permissively—you could do pretty much anything with them, but you had to state that a product that used them did so. The advertising clause was later dropped, and any distribution in source or binary form was allowed, providing the copyright notice was retained.

The name of this patch set was the Berkeley Software Distribution—BSD for short—and it gradually grew into almost a complete replacement for UNIX, with numerous enhancements.

A few years later, the owners of the UNIX original copyright decided to try to cash in on their system’s success, and sued UCB. The upshot was a small number of files containing original UNIX code were rewritten, and a completely unencumbered version of BSD—UNIX being dropped from the name for trademark reasons.

In the early ’90s, Intel released a microprocessor that was capable of running a real operating system. The Intel 386 included features such as support for paged virtual memory, so it became a potential target for running BSD. In 1991, Bill Jolitz released 386 BSD and then neglected the project. A group of people, frustrated by the difficulty of getting patches accepted to 386 BSD, began distributing a patch set and then a complete system known as FreeBSD.

At about the same time, BSD Networking Release/2 (one of the last releases by UCB) was adopted by a group known as NetBSD. While the FreeBSD team focused on supporting the Intel 386, the NetBSD team was keen to retain the portable nature of the original BSD code.

In 1995, a clash of personalities lead to one of the NetBSD core developers, Theo De Raadt, forking the project and creating OpenBSD. OpenBSD, being based in Canada, was not subject to the stringent export laws that the USA placed on cryptography at the time, and so became a popular operating system among the security-conscious. This lead to a thorough code review, which found a large number of bugs and security holes in the code imported from NetBSD. This code review is an ongoing part of the OpenBSD development process and allows them to boast an excellent security record.

Over the years, BSD code has found its way into a large number of systems. Many commercial UNIX variants began as forks of BSD code, and a BSD TCP/IP stack was used in earlier versions of Windows. BSD was also very popular in academia. One project, the Mach Microkernel at CMU, used a modified version of BSD to run UNIX programs. The Mach project was used by a company called NeXT as the foundation for their operating system. When NeXT was bought by Apple, a lot of the old BSD code was replaced with code from the NetBSD and FreeBSD projects. Mac OS X can be thought of as a close cousin to the BSD family: Although it uses Mach as an abstraction layer, much of the kernel is BSD-derived.

It is worth noting that the BSDs are complete systems. Linux is just a kernel, and to be useful it is usually combined with the GNU userland. The BSDs include their own userland—although some parts, such as the compiler, are imported from the GNU project. A BSD system can be installed with no third-party applications—and work. It is more common, however, to add additional packages such as X.org and a desktop environment (the same applications traditionally run atop Linux).

The FreeBSD project underwent some radical changes between versions 4 and 5. Much of the kernel was redesigned to better support multiprocessor systems. One developer, Matt Dillon, was unhappy with the direction it was going, so he set up Dragonfly BSD, a fork of FreeBSD 4. While FreeBSD 5 and later use a system of shared resources and locks, Dragonfly BSD uses message passing between concurrent threads—a process common on microkernel operating systems including Amiga OS (where Matt Dillon first made a name for himself).

Dragonfly BSD is designed as a cluster operating system, and should be able to be installed on a cluster of machines, presenting the appearance of a single large multiprocessor machine to end users.

FreeBSD

FreeBSD is the most popular of the BSD family. It is traditionally known for stability and performance. Many web servers are still around running versions of FreeBSD from years ago without a reboot. FreeBSD is developed in three branches: -CURRENT, -STABLE, and -RELEASE. Anything new is added to -CURRENT, which may or may not work at any given time. Once a new feature has undergone testing by the development team, it is added to -STABLE. Periodically, a release is created. These releases have a version number and their own branch in the CVS tree. Only bug fixes are allowed to be introduced into -RELEASE branches—no new features. This makes tracking a -RELEASE branch the thing to do if you want a completely stable system.

FreeBSD development underwent something of a hiccup around version 5. The release schedule was feature-based, and a large number of new features were planned. Gradually, the release date for FreeBSD 5 slipped farther and farther back. During this time, the project moved to the same six-month release schedule as NetBSD and OpenBSD.

The current release version is 6.0, which is the system used on the laptop on which this article is being written. The 5.x series was highly ambitious and the lack of immediate success gave it a reputation for being unstable and slow—the lack of speed coming from the large quantities of debugging code found in releases.

The 6.x series is intended to avoid the stigma associated with the 5.x series. One of the most noticeable improvements is the new scheduler, known as ULE. ULE is not enabled by default because it does not achieve quite as good throughput as the traditional 4BSD scheduler, making it worse for server roles. For desktop (or laptop) use, it is much better. ULE prioritizes processes that spend most of their time waiting: interactive processes. On this somewhat aging laptop, it is possible to do a large compile in the background without any loss of responsiveness in X applications.

Installation of third-party software is done using the ports system. Each port is a Makefile, containing the files that must be downloaded to build the program and a set of patches to make it run on FreeBSD. The ports system will automatically resolve dependencies when installing programs.

Every port can be compiled into a binary package, and there are copies available from the FreeBSD FTP mirrors (although they often lag behind the port version by several days).

For the few closed-source programs that require Linux, FreeBSD includes a Linux ABI compatibility layer, which translates system call vectors into their equivalent on FreeBSD. It also includes a Linux-style /proc file system for programs that depend on it. Shared libraries used by Linux programs can also be installed—the ports tree contains copies of the basic packages found in several popular Linux distributions.

FreeBSD has a couple of features that make it attractive for home users. First, nVidia release graphics drivers for it, giving it the same level of 3D acceleration available to Linux on nVidia hardware. Second, it includes Project Evil, a reimplementation of the NDIS driver API used by wireless networking cards on Windows, allowing many WiFi cards to be used without direct hardware support.

Project Evil is also being ported to NetBSD, which also has Linux ABI support. Note that ABI support is not full emulation. All UNIX systems have a set of system calls—functions handled by the kernel—which are all assigned numbers. These numbers and the system call arguments vary depending on the kernel. The ABI compatibility layer simply remaps the arguments and changes the number, giving almost no performance penalty—in some cases, even faster performance than native due to a better kernel implementation. Linux is not the only non-native ABI supported by these systems—NetBSD even includes a rudimentary Darwin ABI that allows some OS X applications to run.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020