From Wikipedia, the free encyclopedia
Jump to: navigation, search
Freebsd logo.svg
Screenshot of FreeBSD 6.2 showing its Welcome screen
Company / developer The FreeBSD Project
OS family Unix-like (BSD)
Working state Active
Source model Open source
Initial release 1.0 (November 1, 1993; 20 years ago (1993-11-01))
Latest release 10.0 (20 January 2014; 7 months ago (2014-01-20)) [±][1]
Latest preview 10.0-RC5 (9 January 2014; 7 months ago (2014-01-09)) [±][2]
Platforms IA-32, x86-64, SPARC64, IA-64, PowerPC, ARM, MIPS
Kernel type Monolithic with dynamically loadable modules
Userland BSD
Default user interface Command-line interface
License FreeBSD License, FreeBSD Documentation License
Official website

FreeBSD is a free Unix-like operating system descended from Research Unix via BSD. Although for legal reasons FreeBSD cannot use the Unix trademark, it is a direct descendant of BSD, which was historically also called "BSD Unix" or "Berkeley Unix."[3][4] Due to its permissive licensing terms, much of FreeBSD's code base has become an integral part of other operating systems such as Juniper JUNOS and Apple's OS X.[5] FreeBSD is the most widely used open-source BSD distribution, accounting for more than three-quarters of all installed systems running open-source BSD derivatives.[6]

FreeBSD is a complete operating system – the kernel, device drivers, and all of the userland utilities, such as the shell, are held in the same source code revision tracking tree. (This is in contrast to Linux distributions, for which the kernel, userland utilities, and applications are developed separately, and then packaged together in various ways by others.)[7] Third-party application software may be installed using various software installation systems, the two most common being source installation and package installation, both of which use the FreeBSD Ports system.


FreeBSD development began in 1993 with a quickly growing, unofficial patchkit maintained by users of the 386BSD operating system. This patchkit forked from 386BSD and grew into an operating system taken from U.C. Berkeley's 4.3BSD-Lite (Net/2) tape with many 386BSD components and code from the Free Software Foundation. After two public beta releases via FTP (1.0-GAMMA on 2 September 1993, and 1.0-EPSILON on 3 October 1993), the first official release was FreeBSD 1.0, available via FTP on 1 November 1993 and on CDROM on 30 December 1993. This official release was coordinated by Jordan Hubbard, Nate Williams, Rodney W. Grimes and named by David Greenman. Walnut Creek CDROM agreed to distribute FreeBSD on CD and gave the project a machine to work on along with a fast Internet connection, which Hubbard later said helped stir FreeBSD's rapid growth. A "highly successful" FreeBSD 1.1 release followed in May 1994.[8]

However, there were legal concerns about the BSD Net/2 release source code used in 386BSD. After a lawsuit between then Unix copyright owner Unix System Laboratories, and the University of California, Berkeley, the FreeBSD project re-engineered most of the system using the 4.4BSD-Lite release from Berkeley, which, owing to the lawsuit, had none of the AT&T source code earlier BSD versions contained, making it an unbootable operating system. Following much work, the unencumbered outcome was released as FreeBSD 2.0 in January 1995.[8]

FreeBSD 2.0 featured a revamp of the original Carnegie Mellon University Mach virtual memory system, optimized for performance under high loads. This release introduced the FreeBSD Ports system, which made downloading, building and installing third party software very easy. By 1996, FreeBSD had become popular among commercial and ISP users, powering sites like Walnut Creek CD-ROM, Yahoo! and Hotmail. The last release along the 2-STABLE branch was 2.2.8 in November 1998.[8] FreeBSD 3.0 brought many more changes, including the switch to the ELF binary format. Support for SMP systems and the 64-bit Alpha platform were added. The 3-STABLE branch ended with 3.5.1 in June 2000.[8]

From the early days of the project's inception, a company named Walnut Creek CDROM, upon the suggestion of the two FreeBSD developers, agreed to release the operating system on CD-ROM. In addition to that, the company employed Jordan Hubbard and David Greenman, ran FreeBSD on its servers, sponsored FreeBSD conferences and published FreeBSD-related books, including The Complete FreeBSD by Greg Lehey. By 1997, FreeBSD was Walnut Creek's "most successful product". The company itself later renamed to The FreeBSD Mall.[8][9][10]

In 2005, FreeBSD was characterized as the "unknown giant among free operating systems."[5]


FreeBSD 10 bootloader with ASCII art logo
FreeBSD 9.1 startup with console login prompt
FreeBSD 9.1-RC3 running KDE SC, the Dolphin file manager, the Konsole terminal emulator, and the Mozilla Firefox Web browser from the FreeBSD Ports Collection


FreeBSD's TCP/IP stack is based on the 4.2BSD implementation of TCP/IP which greatly contributed to the widespread adoption of these protocols.[11] FreeBSD also supports IPv6,[12] SCTP, IPSec, and wireless networking (Wi-Fi).[13] The IPv6 and IPSec stacks were taken from the KAME project.[14] Also, FreeBSD supports IPX and AppleTalk protocols, but they are considered old and it is planned to drop support of them as of FreeBSD 11.0.[15]

As of FreeBSD 5.4, support for the Common Address Redundancy Protocol (CARP) was imported from the OpenBSD project. CARP allows multiple nodes to share a set of IP addresses. So if one of the nodes goes down, other nodes still can serve the requests.[16]


FreeBSD has several unique features related to storage. Soft updates can protect the consistency of the UFS filesystem (widely used on the BSDs) in the event of a system crash.[17] Filesystem snapshots allow an image of a UFS filesystem at an instant in time to be efficiently created.[18] Snapshots allow reliable backup of a live filesystem. GEOM is a modular framework that provides RAID (levels 0, 1, 3 currently), full disk encryption, journaling, concatenation, caching, and access to network-backed storage. GEOM allows building of complex storage solutions combining ("chaining") these mechanisms.[19] From 7.0 onward, FreeBSD supports the ZFS filesystem. ZFS was previously an open source filesystem that was first developed by Sun microsystems, but when Oracle acquired Sun, ZFS became a proprietary product. However, the FreeBSD project is still developing and improving its ZFS implemention.[20]

FreeBSD provides two framework for data encryption: GBDE and Geli. Both GBDE and Geli operates at the disk level. GBDE was written by Poul-Henning Kamp and is distributed under the two-clause BSD license. Geli is an alternative to GBDE that was writen by Pawel Jakub Dawidek and first appeared in FreeBSD 6.0.[21][22]


FreeBSD provides several security-related features including access control lists (ACLs), security event auditing, extended file system attributes, fine-grained capabilities and mandatory access controls (MAC). These security enhancements were developed by the TrustedBSD project. The project was founded by Robert Watson with the goal of implementing concepts from the Common Criteria for Information Technology Security Evaluation and the Orange Book. This project is ongoing and many of its extensions have been integrated into FreeBSD. The project is supported by a variety of organizations, including the DARPA, NSA, Network Associates Laboratories, Safeport Network Services, the University of Pennsylvania, Yahoo!, McAfee Research, SPARTA, Apple Computer, nCircle Network Security, Google, the University of Cambridge Computer Laboratory, and others.[23]

The project has also ported the NSA's FLASK/TE implementation from SELinux to FreeBSD. Other work includes the development of OpenBSM, an open source implementation of Sun's Basic Security Module (BSM) API and audit log file format, which supports an extensive security audit system. This was shipped as part of FreeBSD 6.2. Other infrastructure work in FreeBSD performed as part of the TrustedBSD Project has included SYN cookies, GEOM and OpenPAM.

While most components of the TrustedBSD project are eventually folded into the main sources for FreeBSD, many features, once fully matured, find their way into other operating systems. For example, OpenPAM and UFS2 have been adopted by NetBSD. Moreover, the TrustedBSD MAC Framework has been adopted by Apple for OS X.

Much of this work was sponsored by DARPA under DARPA/SPAWAR contract N66001-01-C-8035 ("CBOSS").

FreeBSD ships with three different firewall packages: IPFW, pf and IPFilter. IPFW is FreeBSD's native firewall. pf was taken from OpenBSD and IPFilter was ported to FreeBSD by Darren Reed.[24] Taken from OpenBSD, the OpenSSH program was included in default install. OpenSSH is a Free implementation of SSH protocol and is a replacement for telnet. Unlike telnet, OpenSSH encrypts all information (including username and password).[25]


FreeBSD has been ported to a variety of processor architectures. The FreeBSD project organizes architectures into tiers that characterize the level of support provided. Tier 1 architectures are mature and fully supported. Tier 2 architectures are undergoing major development. Tier 3 architectures are experimental or are no longer under active development and tier 4 architectures have no support at all.

As of March 2014, FreeBSD has been ported to the following architectures:[26]

Architecture Support Level[27] Notes
x86 (IA-32) Tier 1 referred to as "i386"
x86-64 Tier 1 referred to as "amd64"
NEC PC-9801 Tier 2 referred to as "pc98"
Sun SPARC Tier 2 Only support 64-bit (V9) architecture
Itanium (IA-64) Tier 2
PowerPC and PowerPC/64 Tier 2
ARM Tier 2
MIPS Tier 3
IBM ESA/390 Tier 3 referred to as "S/390"
Microsoft's Xbox Tier 4
DEC Alpha Tier 4 Support discontinued from FreeBSD 7.0 on

In addition, initial work has been done to port FreeBSD to run on Raspberry Pi single board computers with ARM11 SoC hardware.[28][29]

Third-party software[edit]

For more details on this topic, see FreeBSD Ports.
FreeBSD running GIMP, Firefox, and GNOME installed from the ports collection.

FreeBSD has a repository of over 24,000 applications that are developed by third parties outside of the project itself. (Examples include windowing systems, Internet browsers, email programs, office suites, and so forth.) In general, the project itself does not develop this software, only the framework to allow these programs to be installed (termed the Ports Collection). Applications may be installed either from source, if its licensing terms allow such redistribution (these are called ports), or as compiled binaries if allowed (these are called packages). The Ports Collection supports the latest release on the -CURRENT and -STABLE branches. Older releases are not supported and may or may not work correctly with an up-to-date ports collection.[30]

Ports and Packages[edit]

Main article: FreeBSD Ports

Each application in the Ports Collection is installed from source. Each port's Makefile automatically fetches the application source code, either from a local disk, CD-ROM or via ftp, unpacks it on the system, applies the patches, and compiles.[7][31] This method can be very time consuming as compiling large packages can take hours, but the user is able to install a customized program. For most ports, precompiled binary packages also exist. This method is very quick as the whole compilation process is avoided, but the user is not able to install a program with customized compile time options.[32]

In FreeBSD 10.0, a new package manager, called pkgng, was introduced. pkgng is a replacement for traditional pkg_add, pkg_create, pkg_delete, pkg_info, pkg_updating, and pkg_version commands.[33] It has functionality similar to apt and yum. It includes installation and upgrades from both source (ports) and with pre-built binary packages. PackageKit also supports the FreeBSD Ports collection as an accepted repository.


Main article: FreeBSD jail

First introduced in 4.x, a FreeBSD jail is a security mechanism and an implementation of operating system-level virtualization that enables the user to run multiple instances of a guest operating system (FreeBSD) on top of a FreeBSD host. Jails are enhanced version of traditional chroot mechanism. A process that runs in a jail, is unable to access the resources outside of that jail. Every jail has its own hostname and IP address. It is possible to run multiple jail at the same time. The kernel is shared among all of them, therefore only FreeBSD-built softwares can be run inside a jail.[34]


Main article: bhyve

bhyve, a new virtualization solution was introduced in FreeBSD 10.0. bhyve allows a user to run a number of guest operating systems (FreeBSD, OpenBSD and Linux) simultaneously. Other operating systems such as Microsoft Windows and Illumos are planned. bhyve was written by Neel Nato and Peter Grehan and was announced in the 2011 BSDCan conference for the first time. The main difference between bhyve and FreeBSD jails is that jails are an operating system-level virtualization and therefore limited to only FreeBSD guests; but bhyve is a type 2 hypervisor and is not limited to only FreeBSD guests.[35][36][37] For comparison, bhyve is a similar technology to KVM whereas jails are closer to LXC containers or Zones.

Compatibility layer with other operating systems[edit]

Most software that runs on Linux can run on FreeBSD using an optional built-in compatibility layer. Hence, most Linux binaries can be run on FreeBSD, including some proprietary applications distributed only in binary form. Additionally, FreeBSD provides compatibility layers for several other Unix-like operating systems, in addition to Linux, such as BSD/OS[38] and SVR4.[39] In addition to that, FreeBSD is able to run NetBSD and OpenBSD's binaries, but people usually don't do that and instead, compile those programs directly on FreeBSD.[38] No noticeable performance penalty over native FreeBSD programs has been noted when running Linux binaries, and, in some cases, these may even perform more smoothly than on Linux.[40][41] However, the layer is not altogether seamless, and some Linux binaries are unusable or only partially usable on FreeBSD. There is support for system calls up to version 2.6.16, available since FreeBSD 7.0. However, there is currently no support for running 64-bit Linux binaries.[41] As of 2013, there are plans for supporting them in FreeBSD 10.[42] This compatibility layer is not an emulation, Linux's ABIs are implemented in the FreeBSD's kernel and hence, Linux binaries are treated same as FreeBSD's native binaries.[39]

FreeBSD has implemented a number of Microsoft windows' native APIs, with the help of these APIs, FreeBSD is able to run windows-only network drivers.[43]


FreeBSD's kernel provides support for some essential tasks such as managing processes, communication, booting and filesystems. FreeBSD has a monolithic kernel,[44] with modular design. Different parts of the kernel such as drivers, are designed as modules. The user can load and unload this modules at any time.[45] ULE is the default scheduler in FreeBSD since version 7.1, it supports SMP and SMT.[46] The FreeBSD kernel has also a scalable event notification interface, named kqueue. It has been ported to other BSD-derivatives such as OpenBSD, NetBSD.[47] Originally, FreeBSD used a M:N threading model. This model is the best threading model in the theory, but it is hard to implement and few operating systems supports it. Although FreeBSD's implementation of this model worked, it did not perform well, so FreeBSD started using a 1:1 threading model, called libthr.[48]

Documentations and support[edit]

FreeBSD's official documentation consists of its handbooks, manual pages, mailing list archives, FAQs and a variety of articles, mainly maintained by The FreeBSD Documentation Project; they are available at FreeBSD's homepage. Official documentations are translated into several languages.[49] All official documentations are released under the FreeBSD Documentation License, "a permissive non-copyleft free documentation license that is compatible with the GNU FDL".[50] FreeBSD's documentations are described as "high-quality".[51][52]

The FreeBSD project maintains a variety of mailing lists. Among the most popular mailing list, are FreeBSD-question (general questions), FreeBSD-newbies (for newcomers) and FreeBSD-hackers (a place for ask more technically questions).[53]


FreeBSD is developed by a volunteer team located around the world. The developers use the Internet for all communication and many have not met each other in person. In addition to local user groups sponsored and attended by users, an annual conference, called BSDcon, is held by USENIX. BSDcon is not FreeBSD-specific so it deals with the technical aspects of all BSD operating systems, including OpenBSD and NetBSD.[54] In addition to BSDcon, two other annually-held conferences, EuroBSDCon and AsiaBSDCon take place in Europe and Japan respectively.[55][56]

Governance structure[edit]

Main article: FreeBSD Core Team

The FreeBSD Project is run by FreeBSD committers, or developers who have SVN commit access. There are several kinds of committers, including source committers (base operating system), doc committers (documentation and web site authors) and ports (third party application porting and infrastructure). Every two years the FreeBSD committers select a 9-member FreeBSD Core Team who are responsible for overall project direction, setting and enforcing project rules and approving new "commit bits", or the granting of SVN commit access. A number of responsibilities are officially assigned to other development teams by the FreeBSD Core Team, including responsibility for security advisories (the Security Officer Team), release engineering (the Release Engineering Team) and managing the ports collection (the Port Manager team). Developers may give up their commit rights to retire or for "safe-keeping" after a period of a year or more of inactivity, although commit rights will generally be restored on request. Under rare circumstances commit rights may be removed by Core Team vote as a result of repeated violation of project rules and standards. The FreeBSD Project is unusual among open source projects in having developers who have worked with its source base for over 10 years before its release in 1993, owing to the involvement of a number of past University of California developers who worked on BSD at the Computer Systems Research Group.[57]


FreeBSD developers maintain at least two branches of simultaneous development. The -CURRENT branch always represents the "bleeding edge" of FreeBSD development. A -STABLE branch of FreeBSD is created for each major version number, from which -RELEASE are cut about once every 4–6 months. If a feature is sufficiently stable and mature it will likely be backported (MFC or Merge from CURRENT in FreeBSD developer slang) to the -STABLE branch.[58][7] FreeBSD's development model is further described in an article by Niklas Saers.[59]


Main article: FreeBSD Foundation

FreeBSD development is supported in part by the FreeBSD Foundation. The foundation is a non-profit organization that accepts donations to fund FreeBSD development. Such funding has been used to sponsor developers for specific activities, purchase hardware and network infrastructure, provide travel grants to developer summits, and provide legal support to the FreeBSD project.[60]


FreeBSD is released under a variety of open source licenses. The kernel code and most newly created code is released under the two-clause BSD license which allows everyone to use and redistribute FreeBSD as they wish. This license was approved by Free Software Foundation[61] and Open Source Initiative[62] as a Free Software and Open Source license respectively. Free Software Foundation described this license as "a lax, permissive non-copyleft free software license, compatible with the GNU GPL". There are parts released under three- and four-clause BSD licenses, as well as Beerware license. Some device drivers include a binary blob,[63] such as the Atheros HAL of FreeBSD versions before 7.2.[64] Some of the code contributed by other projects is licensed under GPL, LGPL, CDDL[65] and ISC. All the code licensed under GPL and CDDL is clearly separated from the code under liberal licenses, to make it easy for users such as embedded device manufacturers to use only permissive free software licenses. ClangBSD aims to replace some GPL dependencies in the FreeBSD base system by replacing the GNU compiler collection with the BSD-licenced LLVM/Clang compiler. ClangBSD became self-hosting on 16 April 2010,[66] an important landmark for further independent development.


FreeBSD's mascot is the generic BSD Daemon, also known as Beastie

For many years FreeBSD's logo was the generic BSD daemon, also called Beastie, a distorted pronunciation of BSD. First appearing in 1976 on Unix T-shirts purchased by Bell Labs, the more popular versions of the BSD daemon were drawn by animation director John Lasseter beginning in 1984.[67][68] Several FreeBSD-specific versions were later drawn by Tatsumi Hosokawa.[69] Through the years Beastie became both beloved and criticized as perhaps inappropriate for corporate and mass market exposure. Moreover it was not unique to FreeBSD. In lithographic terms, the Lasseter graphic is not line art and often requires a screened, four color photo offset printing process for faithful reproduction on physical surfaces such as paper. Moreover, the BSD daemon was thought to be too graphically detailed for smooth size scaling and aesthetically over dependent upon multiple color gradations, making it hard to reliably reproduce as a simple, standardized logo in only two or three colors, much less in monochrome. Because of these worries, a competition was held and a new logo designed by Anton K. Gural, still echoing the BSD daemon, was released on 8 October 2005.[70][71][72] Meanwhile Lasseter's much known take on the BSD daemon carries forth as the official mascot of the FreeBSD Project.

The name "FreeBSD" was coined by David Greenman on 19 June 1993, other suggested names were "BSDFree86" and "Free86BSD".[73] FreeBSD's slogan is "The Power to serve" which is a registered trademark for The FreeBSD Foundation.[74]


There are a number of software distributions based on FreeBSD including:

All these distributions have no or only minor changes when compared with the original FreeBSD base system. The main difference to the original FreeBSD is that they come with pre-installed and pre-configured software for specific use cases. This can be compared with Linux distributions, which are all binary compatible because they use the same kernel and also use the same basic tools, compilers and libraries, while coming with different applications, configurations and branding.

Besides these distributions there is DragonFly BSD, a fork from FreeBSD 4.8 aiming for a different multiprocessor synchronization strategy than the one chosen for FreeBSD 5 and development of some microkernel features.[75] It does not aim to stay compatible with FreeBSD and has huge differences in the kernel and basic userland.

A wide variety of products are directly or indirectly based on FreeBSD.

Some subscription services that are directly based on FreeBSD are:

Embedded devices and embedded device operating systems based on FreeBSD include:

FreeBSD contributions to other operating systems[edit]



For a long time, FreeBSD used the sysinstall program as its main installer. It uses a text user interface, and is divided into a number of menus and screens that can be used to configure and control the installation process. It can also be used to install Ports and Packages as an alternative to the command-line interface.[91] As of FreeBSD 9, sysinstall has been replaced by bsdinstall. It was written in C by Jordan Hubbard, is curses based and first appeared in FreeBSD 2.0. The utility is now considered deprecated.


The bsdinstall utility is "a lightweight replacement for sysinstall", which replaced the sysinstall utility in FreeBSD 9.0. It was written in sh is and is more extendable than FreeBSD's old installer (sysinstall). According to OSNews, "It has lost some features while gaining others, but it is a much more flexible design, and will ultimately be significant improvement".[34][92]

pc-bsd installer[edit]

The pc-bsd installer aims to create a user-friendly graphical installer for FreeBSD & FreeBSD-derived systems.

Unauthorized access to FreeBSD's servers[edit]

On November 2012, The FreeBSD Security Team announced that hackers gained unauthorized access on two of the project's servers. These servers were turned off immediately. More research demonstrated that the first unauthorized access by hackers was occurred on 19 September. Apparently hackers gained access to these servers by Stealing SSH keys from FreeBSD's developers, not by exploiting a bug in the operating system itself. These two hacked servers were part of the infrastructure used to build third-party software packages. The FreeBSD Security Team checked the integrity of the binary packages and announced that no unauthorized change was made to the binary packages, but they stated that they can't guarantee the integrity of packages that was downloaded between 19 September and 11 November.[93][94][95]

Version history[edit]

Main article: History of FreeBSD

Legend: Old version Older version, still supported Current version Latest preview version Future release
Version Release date Supported until Significant changes
Old version, no longer supported: 1.0 November 1993
  • The first official release.
  • The Ports Collection
Old version, no longer supported: 1.1 May 1994
Old version, no longer supported: 2.0 22 November 1994
  • replace code base with BSD-Lite 4.4 (to satisfy terms of the USL v. BSDi lawsuit settlement)
  • new installer and new boot manager
  • loadable filesystems support for more filesystems (MS-DOS, unionfs, kernfs)
  • imported loadable kernel modules from NetBSD
Old version, no longer supported: 2.2 March 1997
Old version, no longer supported: 2.2.8 29 November 1998
Old version, no longer supported: 3.0 October 1998
Old version, no longer supported: 3.1 15 February 1999
Old version, no longer supported: 3.4 20 December 1999
Old version, no longer supported: 4.0 14 March 2000
  • IPv6 support and IPsec with KAME (applications were also updated to support IPv6)
  • OpenSSH integrated into the base system
  • emulator for SVR4 binary files
Old version, no longer supported: 4.1 27 July 2000
Old version, no longer supported: 4.8 3 April 2003 31 March 2004
Old version, no longer supported: 4.10 27 May 2004 May 2006
Old version, no longer supported: 5.0 14 January 2003 30 June 2003
Old version, no longer supported: 5.1 9 June 2003 February 2004
  • experimental support for AMD64
  • experimental 1:1 and M:N thread libraries for multithreaded processing
  • experimental ULE scheduler
Old version, no longer supported: 5.3 6 November 2004 31 October 2006
  • ALTQ
  • addition of new debugging framework KDB
  • import pf from OpenBSD
  • binary compatibility interface for native execution of NDIS drivers
  • replace XFree86 with 6.7
  • cryptography enabled by default in base
Old version, no longer supported: 5.4 9 May 2005 31 October 2006 import Common Address Redundancy Protocol from OpenBSD
Old version, no longer supported: 6.2 15 January 2007 31 May 2008
  • support for Xbox architecture
  • OpenBSM
  • freebsd-update (binary updates for security fixes and errata patches)
Old version, no longer supported: 7.0 27 February 2008 30 April 2009
Old version, no longer supported: 7.1 4 January 2009 28 February 2011
Old version, no longer supported: 8.1 23 July 2010 31 July 2012
  • High Availability Storage
Old version, no longer supported: 9.0 12 January 2012 31 March 2013
  • substitute GCC with Clang and LLVM for base system
  • USB 3.0 support
  • UFS SoftUpdates+Journal
  • update ZFS to version 28
  • replaced sysinstall with bsdinstall
Current stable version: 10.0 20 January 2014 31 January 2015
  • Virtualization improvements (bhyve, virtio)
  • use clang and LLVM by default
  • capsicum (sandbox) enabled by default in the kernel
  • pkgng
  • BIND replaced with LDNS and Unbound in base system
  • add support for Raspberry Pi
  • ZFS on Root File system
Version Release date Supported until Significant changes

See also[edit]


  1. ^ "[FreeBSD-Announce] FreeBSD 10.0-RELEASE Now Available". 20 January 2014. Retrieved 20 January 2014. 
  2. ^ Barber, Glen (9 Jan 2014). "FreeBSD 10.0-RC5 Now Available". FreeBSD mailing list. Retrieved 9 Jan 2014. 
  3. ^ Lehey 2003, p. 4.
  4. ^ Garfinkel, Simson. Spafford, Gene. Schwartz, Alan. Practical UNIX and Internet Security. 2003. pp. 15-20
  5. ^ a b Pohlmann, Frank (19 July 2005). "Why FreeBSD". IBM DeveloperWorks. Archived from the original on 11 September 2013. 
  6. ^ BSD Usage Survey Report (PDF). The BSD Certification Group. 31 October 2005. Retrieved 5 December 2010. 
  7. ^ a b c Chisnall, David (20 January 2006). "BSD: The Other Free UNIX Family". Retrieved 13 December 2013. 
  8. ^ a b c d e "A Brief History of FreeBSD". Retrieved 31 January 2009. 
  9. ^ Bruce, Bob. "Company History". FreeBSD Mall. Retrieved 6 August 2014. 
  10. ^ Johnson, Dwight. "Report from Comdex--Walnut Creek CDROM, FreeBSD and Slackware". Linux Today. Retrieved 6 August 2014. 
  11. ^ McKusick, Marshall (2005). "Section 2.13". The Design and Implementation of the FreeBSD Operating System. ISBN 0-201-70245-2. 
  12. ^ Farrokhi, Babak. "Network Configuration—IPv6 with FreeBSD". Packt. Archived from the original on 26 December 2013. Retrieved 26 December 2013. 
  13. ^ Sam Leffler. "FreeBSD Wireless Netwokring Support". BSDCan. Archived from the original on 26 December 2013. Retrieved 26 December 2013. 
  14. ^ "Overview of the KAME Project". KAME project. Retrieved 11 August 2014. 
  15. ^ Smirnoff, Gleb (28 October 2013). "[heads up axing AppleTalk and IPX/SPX"]. freebsd-stable mailing list. Retrieved 12 August 2014.
  16. ^ "CARP(4)". The FreeBSD documentation Project. Retrieved 25 October 2013. 
  17. ^ McKusick, Marshall; V. Neville-Neil, George (2005). "8.6. Soft Updates". The Design and Implementation of the FreeBSD Operating System. ISBN 0-201-70245-2. 
  18. ^ Lucas 2007, p. 220.
  19. ^ Lucas 2007, 18. DISK TRICKS WITH GEOM.
  20. ^ Sean Michael Kerner (25 February 2011). "FreeBSD 8.2 Expands ZFS Support -- Without Oracle". Datamation. Archived from the original on 15 December 2013. Retrieved 15 December 2013. 
  21. ^ "geli(8)". The FreeBSD Project. Retrieved 12 August 2014. 
  22. ^ Kamp, Poul-Henning. "GBDE—GEOM Based Disk Encryption". USENIX. Archived from the original on 15 Dec 2013. Retrieved 12 August 2014. 
  23. ^ "TrustedBSD Project". TrustedBSD Project. Retrieved 9 August 2014. 
  24. ^ Lucas 2007, p. 273.
  25. ^ Lucas 2007, p. 440.
  26. ^ "FreeBSD/Supported Platforms". Retrieved 26 March 2014. 
  27. ^ "Committer's Guide". The FreeBSD Documentation Project. 
  28. ^ "FreeBSD – Raspberry Pi". , see also Raspbian#Software build
  29. ^ "Raspberry Pi Software Is Rapidly Maturing". OSNews. 
  30. ^ "Chapter 4 Installing Applications: Packages and Ports". Retrieved 30 January 2009. 
  31. ^ Asami, Satoshi. "The FreeBSD Ports Collection". USENIX. Retrieved 13 December 2013. 
  32. ^ "4.4 Using the Packages System". Retrieved 30 January 2009. 
  33. ^ Larabel, Michael. "FreeBSD Still Working On Next-Gen Package Manager". Phoronix. Retrieved 9 August 2014. 
  34. ^ a b "The BSD family, pt. 1: FreeBSD 9.1". OSNews. Retrieved 9 August 2014. 
  35. ^ Schenkeveld, Paul. "The BSD Hypervisor". FOSDEM. Retrieved 9 August 2014. 
  36. ^ Larabel, Michael. "The State Of FreeBSD's Bhyve Virtualization". Phoronix. Retrieved 9 August 2014. 
  37. ^ Grehan, Peter. "Introduction to bhyve". Retrieved 9 August 2014. 
  38. ^ a b Lehey 2003, p. 162.
  39. ^ a b McEwen, Gordon. "Setting up Linux compatibility on FreeBSD 6". Archived from the original on 14 November 2006. Retrieved 15 December 2013. 
  40. ^ Tiemann, Brian (2006). "How FreeBSD Compares to Other Operating Systems". FreeBSD 6 Unleashed. ISBN 0-672-32875-5. 
  41. ^ a b Michael, Larabel. "FreeBSD: A Faster Platform For Linux Gaming Than Linux?". Phoronix. Retrieved 5 August 2014. 
  42. ^ "FreeBSD10 - FreeBSD Wiki". Retrieved 3 August 2013. 
  43. ^ Chisnall, David (15 July 2005). "Project Evil: Windows network drivers on FreeBSD". Ping Wales. Archived from the original on 4 November 2005. Retrieved 23 October 2013. 
  44. ^ McKusick & Neville-Neil 2004, Chapter 2. Design Overview of FreeBSD.
  45. ^ Michael Lucas 2007, p. 118.
  46. ^ Roberson, Jeff. "ULE: A Modern Scheduler for FreeBSD". USENIX. Retrieved 5 August 2014. 
  47. ^ Lemon, Jonathan. "KQueue–A Generic and Scalable Event Notification Facility". USENIX. Retrieved 5 August 2014. 
  48. ^ Lucas 2007, p. 359.
  49. ^ Lucas 2007, p. 25.
  50. ^ "Various Licenses and Comments about Them". Gnu Project. Retrieved 12 August 2014. 
  51. ^ Lehey 2003, p. 16.
  52. ^ "BSD: The Other Free UNIX Family". InformIT. Retrieved 12 August 2014. 
  53. ^ Lehey 2003, p. 17.
  54. ^ Lehey 2003, p. 20.
  55. ^ "EuroBSDcon 2014". EuroBSDcon. Retrieved 9 August 2014. 
  56. ^ "AsiaBSDCon 2014". AsiaBSDCon. Retrieved 9 August 2014. 
  57. ^ "FreeBSD Project Administration and Management". Retrieved 30 January 2009. 
  58. ^ Lucas 2007, pp. 372-375.
  59. ^ Saers, Niklas (2002). "A project model for the FreeBSD Project". Retrieved 3 March 2007. 
  60. ^ "About the FreeBSD Foundation". The FreeBSD Foundation. Retrieved 6 September 2009. 
  61. ^ "Various Licenses and Comments about Them". The GNU Project. Retrieved 9 August 2014. 
  62. ^ "The BSD 2-Clause License". Open Source Initiative. Retrieved 9 August 2014. 
  63. ^ Watson, Robert (Sun 22 October, 12:34:20 UTC 2006). "binary blobs in freebsd". freebsd-questions mailing list. Retrieved 20 October 2013.
  64. ^ "Contents of /stable/9/cddl/contrib/opensolaris/OPENSOLARIS.LICENSE". The FreeBSD Project. Retrieved 28 August 2014. 
  65. ^ "ClangBSD Is Selfhosting, We Need Testers Now". 17 April 2010. Retrieved 23 April 2013. 
  66. ^ "Usenix". Retrieved 15 December 2007. 
  67. ^ "Saving UNIX from /dev/null". Retrieved 15 December 2007. 
  68. ^ "The BSD Daemon". Retrieved 15 December 2007. 
  69. ^ "FreeBSD logo design competition". OSNews. Retrieved 1 November 2013. 
  70. ^ Kuriyama, Jun (22 February 2005). "FreeBSD logo design competition". FreeBSD-Announce mailing list. Retrieved 1 November 2013.
  71. ^ "Final result for the FreeBSD logo design competition". 2005. Archived from the original on 16 October 2012. Retrieved 1 March 2007. 
  72. ^ Greenman, David. "FreeBSD Archives". The FreeBSD Project. Retrieved 6 August 2014. 
  73. ^ "FreeBSD Logo". The FreeBSD Project. Retrieved 6 August 2014. 
  74. ^ Dillon, Matthew (16 July 2003), "Announcing DragonFly BSD!", freebsd-current mailing list, retrieved 26 July 2007 
  75. ^ a b "1 million is so 2011". WhatsApp Blog. Retrieved 27 August 2014. 
  76. ^ Netflix (29 May 2012). "Open Connect Appliance Deployment Guide". 
  77. ^ Long, Scott (5 June 2012). "Netflix's New Peering Appliance Uses FreeBSD". freebsd-stable mailing list. Retrieved 5 June 2012.
  78. ^ "Licenses of software used on PlayStation®3 console". Retrieved 11 August 2010. 
  79. ^ Michael Larabel (23 June 2013). "Sony's PlayStation 4 Is Running Modified FreeBSD 9". Phoronix. Retrieved 17 August 2013. 
  80. ^ Matthew Humphries (24 June 2013). "PS4 runs modified version of the FreeBSD 9.0 operating system". Retrieved 19 October 2013. 
  81. ^ Clark, Jack. "Sony's new PlayStation 4 and open source FreeBSD: The TRUTH". Retrieved 16 November 2013. 
  82. ^ Maste, Ed. "FreeBSD at Sandvine". BSDCan 2011. 
  83. ^ "Sophos Email Appliance: overview". Retrieved 23 April 2013. 
  84. ^ "iPrism v6.2xx" (PDF). Retrieved 23 April 2013. 
  85. ^ Sean Michael Kerner (21 August 2009). "FreeBSD 8 Getting New Routing Architecture". Retrieved 19 December 2010. 
  86. ^ "Using FreeBSD to Render Realtime Localized Audio and Video". Retrieved 29 December 2012. 
  87. ^ "Debian GNU/kFreeBSD". Retrieved 11 August 2010. 
  88. ^ "Kernel Programming Guide: BSD Overview". Apple Inc. 
  89. ^ "Porting UNIX/Linux Applications to OS X: Overview of OS X". Apple Inc. 
  90. ^ "2.5 Introducing Sysinstall". Retrieved 30 January 2009. 
  91. ^ "2012: a BSD year in retrospective". OSNews. Retrieved 9 August 2014. 
  92. ^ "Hackers obtained access to FreeBSD servers". H-Online. Retrieved 9 August 2014. 
  93. ^ "Hackers break into two FreeBSD Project servers using stolen SSH keys". Computer World. Retrieved 9 August 2014. 
  94. ^ "FreeBSD servers hacked". Techeye. Retrieved 9 August 2014. 


External links[edit]