text
stringlengths 0
7.06k
|
|---|
FreeBSD 's TCP / IP stack is based on the <unk> implementation of TCP / IP which greatly contributed to the widespread adoption of these protocols . FreeBSD also supports IPv6 , <unk> , <unk> , and wireless networking ( Wi @-@ Fi ) . The IPv6 and <unk> stacks were taken from the <unk> project . Also , FreeBSD supports IPX and AppleTalk protocols , but they are considered old and it is planned to drop support of them in the upcoming FreeBSD 11 @.@ 0 .
|
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 .
|
= = = Storage = = =
|
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 . <unk> snapshots allow an image of a UFS filesystem at an instant in time to be efficiently created . 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 . FreeBSD provides two frameworks for data encryption : GBDE and Geli . Both GBDE and Geli operate 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 written by Pawel Jakub <unk> and first appeared in FreeBSD 6 @.@ 0 .
|
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 <unk> via the <unk> project .
|
= = = Security = = =
|
FreeBSD provides several security @-@ related features including access control lists ( <unk> ) , security event auditing , extended file system attributes , mandatory access controls ( MAC ) and fine @-@ grained capabilities . 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 , <unk> Network Services , the University of Pennsylvania , Yahoo ! , McAfee Research , <unk> , Apple Computer , <unk> Network Security , Google , the University of Cambridge Computer Laboratory , and others .
|
The project has also ported the NSA 's <unk> / TE implementation from <unk> to FreeBSD . Other work includes the development of <unk> , an open source implementation of Sun 's Basic Security Module ( <unk> ) 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 GEOM and <unk> .
|
Most components of the TrustedBSD project are eventually folded into the main sources for FreeBSD . In addition , many features , once fully matured , find their way into other operating systems . For example , <unk> has been adopted by NetBSD . Moreover , the TrustedBSD MAC Framework has been adopted by Apple for OS X.
|
FreeBSD ships with three different firewall packages : IPFW , pf and IPFilter . IPFW is FreeBSD 's native <unk> pf was taken from OpenBSD and IPFilter was ported to FreeBSD by Darren Reed .
|
Taken from OpenBSD , the OpenSSH program was included in default install . OpenSSH is a Free implementation of the SSH protocol and is a replacement for <unk> . Unlike <unk> , OpenSSH <unk> all information ( including username and password ) .
|
In 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 occurred on 19 September . Apparently hackers gained access to these servers by stealing SSH keys from one of the 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 were downloaded between 19 September and 11 November .
|
= = = Portability = = =
|
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 2016 , FreeBSD has been ported to the following architectures :
|
The ARM and MIPS support is mostly aimed at embedded systems , however FreeBSD / ARM runs on a number of single @-@ board computers , including the <unk> Black , Raspberry Pi and <unk> .
|
= = = Third @-@ party software = = =
|
FreeBSD has a repository of over 24 @,@ 000 applications that are developed by third parties . Examples include : windowing systems , web browsers , email clients , 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 , which is known as the Ports collection . Applications may either be compiled from source ( " ports " ) , provided their licensing terms allow this , or downloaded as pre @-@ compiled binaries ( " packages " ) . The Ports collection supports the current and stable branches of FreeBSD . Older releases are not supported and may or may not work correctly with an up @-@ to @-@ date Ports collection .
|
Ports use <unk> to automatically fetch the desired application 's source code , either from a local or remote repository , unpack it on the system , apply patches to it and compile it . Depending on the size of the source code , compiling can take a long time , but it gives the user more control over the process and its result . Most ports also have package counterparts ( i.e. pre @-@ compiled binaries ) , giving the user a choice . Although this method is faster , the user has fewer customisation options .
|
FreeBSD version 10 @.@ 0 introduced the package manager pkg as a replacement for the previously used package tools . It is functionally similar to apt and yum in Linux distributions . It allows for installation , upgrading and removal of both ports and packages . In addition to pkg , <unk> can also be used to access the Ports collection .
|
= = = Jails = = =
|
First introduced in FreeBSD version 4 , jails 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 on top of a FreeBSD host . It is an enhanced version of the traditional <unk> mechanism . A process that runs within such a jail is unable to access the resources outside of it . Every jail has its own <unk> and IP address . It is possible to run multiple jails at the same time , but the kernel is shared among all of them . Hence only software supported by the FreeBSD kernel can be run within a jail .
|
= = = <unk> = = =
|
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 , Linux , and Microsoft Windows ) simultaneously . Other operating systems such as <unk> are <unk> bhyve was written by Neel Nato and Peter <unk> and was announced in the 2011 <unk> 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 . For comparison , bhyve is a similar technology to KVM whereas jails are closer to <unk> containers or Solaris Zones .
|
= = = OS compatibility layers = = =
|
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 . This compatibility layer is not an emulation ; Linux 's system call interface is implemented in the FreeBSD 's kernel and hence , Linux executable images and shared libraries are treated the same as FreeBSD 's native executable images and shared libraries . Additionally , FreeBSD provides compatibility layers for several other Unix @-@ like operating systems , in addition to Linux , such as BSD / OS and <unk> , however , it is more common for users to compile those programs directly on FreeBSD .
|
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 . 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 @.@ 18 , available since FreeBSD 7 @.@ 0 . As of release 10 @.@ 3 , FreeBSD can run 64 @-@ bit Linux binaries .
|
FreeBSD has implemented a number of Microsoft Windows native <unk> kernel interfaces to allow FreeBSD to run Windows @-@ only network drivers .
|
= = = Kernel = = =
|
FreeBSD 's kernel provides support for some essential tasks such as managing processes , communication , booting and filesystems . FreeBSD has a monolithic kernel , with modular design . Different parts of the kernel such as drivers , are designed as modules . The user can load and unload these modules at any time . <unk> is the default scheduler in FreeBSD since version 7 @.@ 1 , it supports SMP and SMT . The FreeBSD kernel has also a scalable event notification interface , named <unk> . It has been ported to other BSD @-@ derivatives such as OpenBSD , NetBSD . Kernel threading was introduced in FreeBSD 5 @.@ 0 , using an M : N threading model . This model works well in theory , but it is hard to implement and few operating systems support it . Although FreeBSD 's implementation of this model worked , it did not perform well , so from version 7 @.@ 0 onward , FreeBSD started using a 1 : 1 threading model , called <unk> .
|
= = = Documentation and support = = =
|
FreeBSD 's documentation consists of its handbooks , manual pages , mailing list archives , <unk> and a variety of articles , mainly maintained by The FreeBSD Documentation Project . FreeBSD 's documentation is translated into several languages . All official documentation is released under the FreeBSD Documentation License , " a permissive non @-@ copyleft free documentation license that is compatible with the GNU FDL " . FreeBSD 's documentation is described as " high @-@ quality " .
|
The FreeBSD project maintains a variety of mailing lists . Among the most popular mailing lists are FreeBSD @-@ questions ( general questions ) and FreeBSD @-@ hackers ( a place for asking more technical questions ) .
|
Since 2004 , the New York City BSD Users Group database provides <unk> information from a collection of computers ( laptops , workstations , single @-@ board computers , embedded systems , virtual machines , etc . ) running FreeBSD .
|
= = = <unk> = = =
|
From version 2 @.@ 0 to 9 @.@ 0 , FreeBSD used the sysinstall program as its main installer . It was written in C by Jordan Hubbard . 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 .
|
The sysinstall utility is now considered deprecated in favor of <unk> , a new installer which was introduced in FreeBSD 9 @.@ 0 @.@ <unk> is " a lightweight replacement for sysinstall " that was written in sh . According to <unk> , " It has lost some features while gaining others , but it is a much more flexible design , and will ultimately be significant improvement " .
|
= = Development = =
|
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 . In addition to BSDcon , three other annual conferences , <unk> , <unk> and <unk> take place in Europe , Japan and Canada respectively .
|
= = = Governance structure = = =
|
The FreeBSD Project is run by around 500 committers , or developers who have commit access to the master source code repositories and can develop , debug or enhance any part of the system . Most of the developers are volunteers and few developers are paid by some companies . 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 <unk> , or the granting of <unk> commit access . A number of responsibilities are officially assigned to other development teams by the FreeBSD Core Team , for example , responsibility for managing the ports collection is delegated to the Ports Management Team .
|
In addition to developers , FreeBSD has thousands of " contributors " . Contributors are also volunteers outside of the FreeBSD project who submit patches for consideration by committers , as they don 't have direct access to FreeBSD 's source code repository . <unk> then evaluate contributors submissions and decide what to accept and what to reject . A contributor who submits high @-@ quality patches is often asked to become a <unk> .
|
= = = Branches = = =
|
FreeBSD developers maintain at least two branches of simultaneous development . The <unk> branch always represents the " bleeding edge " of FreeBSD development . A <unk> branch of FreeBSD is created for each major version number , from which <unk> are cut about once every 4 – 6 months . If a feature is sufficiently stable and mature it will likely be <unk> ( MFC or Merge from <unk> in FreeBSD developer slang ) to the <unk> branch .
|
= = = 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 .
|
In November 2014 , the FreeBSD Foundation received 1 million USD donation from Jan <unk> , Co @-@ Founder and CEO of WhatsApp , - the largest single donation to the Foundation since its inception . Jan <unk> himself is a FreeBSD user since the late 1990s and WhatsApp uses FreeBSD on its servers .
|
= = License = =
|
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 and Open Source Initiative 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 <unk> license . Some device drivers include a binary blob , such as the <unk> HAL of FreeBSD versions before 7 @.@ 2 . Some of the code contributed by other projects is licensed under GPL , <unk> , <unk> and ISC . All the code licensed under GPL and <unk> 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 . <unk> aims to replace some GPL dependencies in the FreeBSD base system by replacing the GNU compiler collection with the BSD @-@ licensed <unk> / <unk> compiler . <unk> became self @-@ hosting on 16 April 2010 .
|
= = Logo = =
|
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 . Several FreeBSD @-@ specific versions were later drawn by Tatsumi Hosokawa .
|
However , Beastie 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 . Also , the BSD daemon was thought to be too graphically detailed for smooth size scaling and aesthetically over @-@ dependent on 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. <unk> , still echoing the BSD daemon , was released on 8 October 2005 . However , it was announced by Robert Watson that , the FreeBSD project is " seeking a new logo , but not a new mascot " and that the FreeBSD project will continue to use Beastie as its mascot .
|
The name " FreeBSD " was coined by David Greenman on 19 June 1993 , other suggested names were " <unk> " and " <unk> " . FreeBSD 's slogan , " The Power to serve " , is a trademark of The FreeBSD Foundation .
|
= = Derivatives = =
|
There are a number of software distributions based on FreeBSD including :
|
<unk> 10 ( server )
|
PC @-@ BSD ( aimed at home users and workstations )
|
<unk> ( desktop @-@ oriented operating system , originally based on KDE )
|
<unk> ( <unk> @-@ based distribution , which also offers other desktop environments )
|
<unk> ( live CD )
|
Frenzy ( live CD )
|
<unk> ( exploit mitigation and hardening development )
|
<unk> ( firewall )
|
<unk> ( firewall )
|
<unk> ( for Network @-@ attached storage devices )
|
<unk> ( for Network @-@ attached storage devices )
|
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.