Add FreeBSD / Linux Comparison Whitepaper written by Dru Lavigne.
Additional DocBook markup could be added to this article to improve the links to the citations, etc. Reviewed by: gnn, murray
This commit is contained in:
parent
8cdc4e3af4
commit
33df755f92
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=25240
3 changed files with 568 additions and 0 deletions
en_US.ISO8859-1/articles
|
@ -23,6 +23,7 @@ SUBDIR+= hubs
|
|||
SUBDIR+= ipsec-must
|
||||
SUBDIR+= java-tomcat
|
||||
SUBDIR+= laptop
|
||||
SUBDIR+= linux-comparison
|
||||
SUBDIR+= mailing-list-faq
|
||||
SUBDIR+= mh
|
||||
SUBDIR+= multi-os
|
||||
|
|
18
en_US.ISO8859-1/articles/linux-comparison/Makefile
Normal file
18
en_US.ISO8859-1/articles/linux-comparison/Makefile
Normal file
|
@ -0,0 +1,18 @@
|
|||
# $FreeBSD$
|
||||
#
|
||||
# Article: FreeBSD and Linux Comparison Whitepaper
|
||||
|
||||
MAINTAINER= marketing@FreeBSD.org
|
||||
|
||||
DOC?= article
|
||||
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
SRCS= article.sgml
|
||||
|
||||
URL_RELPREFIX?= ../../../..
|
||||
DOC_PREFIX?= ${.CURDIR}/../../..
|
||||
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
549
en_US.ISO8859-1/articles/linux-comparison/article.sgml
Normal file
549
en_US.ISO8859-1/articles/linux-comparison/article.sgml
Normal file
|
@ -0,0 +1,549 @@
|
|||
<!--
|
||||
Copyright (c) 2005 Dru Lavigne
|
||||
|
||||
Redistribution and use in source (SGML DocBook) and 'compiled' forms
|
||||
(SGML, HTML, PDF, PostScript, RTF and so forth) with or without
|
||||
modification, are permitted provided that the following conditions
|
||||
are met:
|
||||
|
||||
1. Redistributions of source code (SGML DocBook) must retain the above
|
||||
copyright notice, this list of conditions and the following
|
||||
disclaimer as the first lines of this file unmodified.
|
||||
|
||||
2. Redistributions in compiled form (transformed to other DTDs,
|
||||
converted to PDF, PostScript, RTF and other formats) must reproduce
|
||||
the above copyright notice, this list of conditions and the
|
||||
following disclaimer in the documentation and/or other materials
|
||||
provided with the distribution.
|
||||
|
||||
THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT "AS
|
||||
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
|
||||
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
||||
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL NIK CLAYTON BE LIABLE FOR ANY
|
||||
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||||
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
||||
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
||||
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
|
||||
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
|
||||
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
<!ENTITY legalnotice SYSTEM "../../share/sgml/legalnotice.sgml">
|
||||
]>
|
||||
|
||||
<article>
|
||||
<articleinfo>
|
||||
<title>FreeBSD / Linux Comparison Whitepaper</title>
|
||||
|
||||
<author>
|
||||
<firstname>Dru</firstname>
|
||||
<surname>Lavigne</surname>
|
||||
<affiliation>
|
||||
<address><email>dru@isecom.org</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
|
||||
<copyright>
|
||||
<year>2005</year>
|
||||
<holder role="mailto:dru@isecom.org">Dru Lavigne</holder>
|
||||
</copyright>
|
||||
|
||||
<releaseinfo>$FreeBSD$</releaseinfo>
|
||||
|
||||
<legalnotice id="trademarks" role="trademarks">
|
||||
&tm-attrib.freebsd;
|
||||
&tm-attrib.linux;
|
||||
&tm-attrib.unix;
|
||||
&tm-attrib.general;
|
||||
</legalnotice>
|
||||
|
||||
&legalnotice;
|
||||
|
||||
<abstract>
|
||||
<para>The objective of this whitepaper is to explain some of the
|
||||
features and benefits provided by FreeBSD, and where
|
||||
applicable, compare those features to Linux. This paper
|
||||
provides a starting point for those interested in exploring
|
||||
Open Source alternatives to Linux.</para>
|
||||
</abstract>
|
||||
</articleinfo>
|
||||
|
||||
<sect1 id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>FreeBSD is a &unix; like operating system based on the
|
||||
Berkeley Software Distribution. While FreeBSD and Linux are
|
||||
commonly perceived as being very similar, there are differences:</para>
|
||||
|
||||
<orderedlist>
|
||||
|
||||
<listitem>
|
||||
|
||||
<para>Linux itself is a kernel. Distributions (e.g. Red Hat,
|
||||
Debian, Suse and others) provide the installer and the
|
||||
utilities available to the user. http://www.linux.org/dist
|
||||
lists well over 300 distinct distributions. While giving
|
||||
the user maximum flexibility, the existence of so many
|
||||
distributions also increases the difficulty of transferring
|
||||
one's skills from one distribution to another. Distributions
|
||||
don't just differ in ease-of install and available programs;
|
||||
they also differ in directory layout, available shells and
|
||||
window managers, and software installation and patching
|
||||
routines.</para>
|
||||
|
||||
<para>FreeBSD is a complete operating system (kernel and
|
||||
userland) with a well-respected heritage grounded in the
|
||||
roots of Unix development.[1] Since both the kernel and the
|
||||
provided utilities are under the control of the same release
|
||||
engineering team, there is less likelihood of library
|
||||
incompatibilities. Security vulnerabilities can also be
|
||||
addressed quickly by the security team. When new utilities
|
||||
or kernel features are added, the user simply needs to read
|
||||
one file, the Release Notes, which is publicly available on
|
||||
the main page of the FreeBSD website
|
||||
[http://www.freebsd.org].</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>FreeBSD has a large and well organized programming base
|
||||
which ensures changes are implemented quickly and in a
|
||||
controlled manner. There are several thousand programmers
|
||||
who contribute code on a regular basis but only about 300 of
|
||||
these have what is known as a commit bit and can actually
|
||||
commit changes to the kernel, utilities and official
|
||||
documentation. A release engineering team provides quality
|
||||
control and a security officer team is responsible for
|
||||
responding to security incidents. In addition, there is an
|
||||
elected core group of 8 senior committers who set the
|
||||
overall direction of the Project.</para>
|
||||
|
||||
<para>In contrast, changes to the Linux kernel ultimately have
|
||||
to wait until they pass through the maintainer of kernel
|
||||
source, Linus Torvalds. How changes to distributions occur
|
||||
can vary widely, depending upon the size of each particular
|
||||
distribution's programming base and organizational method.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
||||
<para>While both FreeBSD and Linux use an Open Source
|
||||
licensing model, the actual licenses used differ. The Linux
|
||||
kernel is under the GPL license
|
||||
[http://www.opensource.org/licenses/gpl-license.php] while
|
||||
FreeBSD uses the BSD license
|
||||
[http://www.opensource.org/licenses/bsd-license.php]. These,
|
||||
and other Open Source licenses, are described in more detail
|
||||
at the website of the Open Source
|
||||
Initiative. [http://www.opensource.org/licenses/]</para>
|
||||
|
||||
<para>The driving philosophy behind the GPL is to ensure that
|
||||
code remains Open Source; it does this by placing
|
||||
restrictions on the distribution of GPLd code. In contrast,
|
||||
the BSD license places no such restrictions, which gives you
|
||||
the flexibility of keeping the code Open Source or closing
|
||||
the code for a proprietary commercial product.[2] Having
|
||||
stable and reliable code under the attractive BSD license
|
||||
means that many operating systems, such as Apple OS X
|
||||
[http://developer.apple.com/darwin/projects/darwin/faq.html],
|
||||
are based on FreeBSD code. It also means that if you choose
|
||||
to use BSD licensed code in your own projects, you can do so
|
||||
without threat of future legal liability.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="freebsd-features">
|
||||
<title>FreeBSD Features</title>
|
||||
|
||||
<sect2 id="freebsd-features-platforms">
|
||||
<title>Supported Platforms</title>
|
||||
|
||||
<para>FreeBSD has gained a reputation as a secure, stable,
|
||||
operating system for the Intel (i386) platform, However,
|
||||
FreeBSD also supports the following architectures:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><simpara>alpha</simpara></listitem>
|
||||
<listitem><simpara>amd64</simpara></listitem>
|
||||
<listitem><simpara>ia64</simpara></listitem>
|
||||
<listitem><simpara>i386</simpara></listitem>
|
||||
<listitem><simpara>pc98</simpara></listitem>
|
||||
<listitem><simpara>sparc64</simpara></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>In addition, there is ongoing development to port FreeBSD
|
||||
to the following architectures:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><simpara>ARM</simpara></listitem>
|
||||
<listitem><simpara>MIPS</simpara></listitem>
|
||||
<listitem><simpara>PowerPC</simpara></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Up-to-date hardware lists are maintained for each
|
||||
architecture so you can tell at a glance if your hardware is
|
||||
supported. For servers, there is excellent hardware RAID and
|
||||
network interface support.</para>
|
||||
|
||||
<para>FreeBSD also makes a great workstation and laptop
|
||||
operating system! It supports the X Window System, the same
|
||||
one used in Linux distributions to provide a desktop user
|
||||
interface. It also supports over 13,000 easy to install
|
||||
third-party applications,[3] including KDE, Gnome, and
|
||||
OpenOffice.</para>
|
||||
|
||||
<para>Several projects are available to ease the installation of
|
||||
FreeBSD as a desktop. The most notable are:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para><ulink
|
||||
url="http://www.freesbie.org">FreeSBIE</ulink> which
|
||||
provides a LiveCD of FreeBSD.</para></listitem>
|
||||
|
||||
<listitem><para><ulink
|
||||
url="http://www.pcbsd.com">PC-BSD</ulink> which provides an
|
||||
easy-to-use GUI installer for FreeBSD aimed at the desktop
|
||||
user.</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="freebsd-features-frameworks">
|
||||
<title>Extensible Frameworks</title>
|
||||
|
||||
<para>FreeBSD provides many extensible frameworks to easily
|
||||
allow you to customize the FreeBSD environment to your
|
||||
particular needs. Some of the major frameworks are:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>Netgraph</term>
|
||||
|
||||
<listitem><para>Netgraph is a modular networking subsystem that
|
||||
can be used to supplement the existing kernel networking
|
||||
infrastructure. Hooks are provided to allow developers to
|
||||
derive their own modules. As a result, rapid prototyping and
|
||||
production deployment of enhanced network services can be
|
||||
performed far more easily and with fewer bugs. Many existing
|
||||
operational modules ship with FreeBSD and include support for:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>PPPoE</para></listitem>
|
||||
<listitem><para>ATM</para></listitem>
|
||||
<listitem><para>ISDN</para></listitem>
|
||||
<listitem><para>Bluetooth</para></listitem>
|
||||
<listitem><para>HDLC</para></listitem>
|
||||
<listitem><para>EtherChannel</para></listitem>
|
||||
<listitem><para>Frame Relay</para></listitem>
|
||||
<listitem><para>L2TP, just to name a few.</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>GEOM</term>
|
||||
|
||||
<listitem><para>GEOM is a modular disk I/O request
|
||||
transformation framework. Since it is a pluggable storage
|
||||
layer, it permits new storage services to be quickly developed
|
||||
and cleanly integrated into the FreeBSD storage
|
||||
subsystem. Some examples where this can be useful are:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Creating RAID solutions.</para></listitem>
|
||||
<listitem><para>Providing full-blown cryptographic protection of stored data.</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Newer versions of FreeBSD provide many administrative
|
||||
utilities to use the existing GEOM modules. For example, one
|
||||
can create a disk mirror using &man.gmirror.8;, a stripe
|
||||
using &man.gstripe.8;, and a shared secret device using
|
||||
&man.gshsec.8;.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>GBDE</term>
|
||||
|
||||
<listitem><para>GBDE, or GEOM Based Disk Encryption, provides
|
||||
strong cryptographic protection and can protect file systems,
|
||||
swap devices, and other uses of storage media. In addition,
|
||||
GBDE transparently encrypts entire file systems, not just
|
||||
individual files. No cleartext ever touches the hard drive's
|
||||
platter.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>MAC</term>
|
||||
|
||||
<listitem><para>MAC
|
||||
[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mac.html],
|
||||
or Mandatory Access Control, provides fine-tuned access to
|
||||
files and is meant to augment traditional operating system
|
||||
authorization provided by file permissions. Since MAC is
|
||||
implemented as a modular framework, a FreeBSD system can be
|
||||
configured for any required policy varying from HIPAA
|
||||
compliance to the needs of a military-grade system.</para>
|
||||
|
||||
<para>FreeBSD ships with modules to implement the following
|
||||
policies; however the framework allows you to develop any
|
||||
required policy:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Biba integrity model</para></listitem>
|
||||
<listitem><para>Port ACLs</para></listitem>
|
||||
<listitem><para>MLS or Multi-Level Security confidentiality policy</para></listitem>
|
||||
<listitem><para>LOMAC or Low-watermark Mandatory Access Control data integrity policy</para></listitem>
|
||||
<listitem><para>Process partition policy</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>PAM</term>
|
||||
|
||||
<listitem><para>Like Linux, FreeBSD provides support for PAM
|
||||
[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pam/],
|
||||
Pluggable Authentication Modules. This allows an administrator
|
||||
to augment the traditional Unix username/password
|
||||
authentication model. FreeBSD provides modules to integrate
|
||||
into many authentication mechanisms, including:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>Kerberos 5</para></listitem>
|
||||
<listitem><para>OPIE</para></listitem>
|
||||
<listitem><para>RADIUS</para></listitem>
|
||||
<listitem><para>TACACS+</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>It also allows the administrator to define policies to
|
||||
control authentication issues such as the quality of
|
||||
user-chosen passwords.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="freebsd-security">
|
||||
<title>Security</title>
|
||||
|
||||
<para>Security is very important to the FreeBSD Release
|
||||
Engineering Team
|
||||
[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/]. This
|
||||
manifests itself in several concrete areas:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>All security incidents and fixes pass through the
|
||||
Security Team and are issued as publicly available
|
||||
Advisories. The Security Team has a reputation for quickly
|
||||
resolving known security issues. Full information regarding
|
||||
FreeBSD's security handling procedures and where to find
|
||||
security information is available at
|
||||
<ulink url="http://www.freebsd.org/security/"></ulink>.</para></listitem>
|
||||
|
||||
<listitem><para>One of the problems associated with Open Source
|
||||
software is the sheer volume of available applications. There
|
||||
are literally 10s of 1000s of Open Source application projects
|
||||
each with varying levels of responsiveness to security
|
||||
incidents. FreeBSD has met this challenge head-on with <ulink
|
||||
url="http://www.vuxml.org/freebsd/">VuXML</ulink>. All software
|
||||
shipped with the FreeBSD operating system as well any software
|
||||
available in the <ulink
|
||||
url="http://www.FreeBSD.org/ports/">Ports Collection</ulink>
|
||||
is compared to a database of known, unresolved
|
||||
vulnerabilities. An administrator can use the portaudit
|
||||
utility to quickly determine if any software on a FreeBSD
|
||||
system is vulnerable, and if so, receive a description of the
|
||||
problem and an URL containing a more detailed vulnerability
|
||||
description.</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>FreeBSD also provides many mechanisms which allow an
|
||||
administrator to tune the operating system to meet his security
|
||||
needs:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem><para>The &man.jail.8; utility allows an administrator
|
||||
to imprison a process; this is ideal for applications which
|
||||
don't provide their own chroot environment.</para></listitem>
|
||||
|
||||
<listitem><para>The &man.chflags.1; utility augments the
|
||||
security provided by traditional Unix permissions. It can, for
|
||||
example, prevent specified files from being modified or
|
||||
deleted by even the superuser.</para></listitem>
|
||||
|
||||
<listitem><para>FreeBSD provides 3 built-in stateful, NAT-aware
|
||||
firewalls, allowing the flexibility of choosing the ruleset
|
||||
most appropriate to one's security needs.</para></listitem>
|
||||
|
||||
<listitem><para>The FreeBSD kernel is easily modified, allowing an
|
||||
administrator to strip out unneeded functionality. FreeBSD
|
||||
also supports kernel loadable modules and provides utilities
|
||||
to view, load and unload kernel modules.</para></listitem>
|
||||
|
||||
<listitem><para>The sysctl mechanism allows an administrator to view
|
||||
and change kernel state on-the-fly without requiring a
|
||||
reboot.</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="freebsd-support">
|
||||
<title>Support</title>
|
||||
|
||||
<para>Like Linux, FreeBSD offers many venues for support, both
|
||||
freely available and commercial.</para>
|
||||
|
||||
<sect2 id="freebsd-support-free">
|
||||
<title>Free Offerings</title>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem><para>FreeBSD is one of the best documented
|
||||
operating systems, and the documentation is available both
|
||||
as part of the operating system and on the Internet. Manual
|
||||
pages are clear, concise and provide working examples. The
|
||||
FreeBSD Handbook
|
||||
[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/]
|
||||
provides background information and configuration examples
|
||||
for nearly every task one would wish to complete using
|
||||
FreeBSD.</para></listitem>
|
||||
|
||||
<listitem><para>FreeBSD provides many support mailing lists
|
||||
[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL].
|
||||
where answers are archived and fully searchable. If you have
|
||||
a question that wasn't addressed by the Handbook, it most
|
||||
likely has already been answered on a mailing list. The
|
||||
Handbook and mailing lists are also available in several
|
||||
languages, all of which are easily accessible from
|
||||
http://www.freebsd.org.</para></listitem>
|
||||
|
||||
<listitem><para>There are many FreeBSD IRC channels, forums
|
||||
and user groups. See <ulink
|
||||
url="http://www.freebsd.org/support.html"></ulink> for a
|
||||
selection.</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>If you're looking for a FreeBSD administrator, developer
|
||||
or support personnel, send a job description which includes
|
||||
geographic location to freebsd-jobs@FreeBSD.org.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="freebsd-support-commercial">
|
||||
<title>Commercial Offerings</title>
|
||||
|
||||
<para>There are many vendors who provide commercial FreeBSD
|
||||
support. Resources for finding a vendor near you
|
||||
include:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>The Commercial Vendors page at the FreeBSD
|
||||
site: <ulink
|
||||
url="http://www.freebsd.org/commercial/"></ulink></para></listitem>
|
||||
|
||||
<listitem><para>FreeBSDMall has been selling support contracts
|
||||
for nearly 10 years.
|
||||
<ulink url="http://www.freebsdmall.com"></ulink></para></listitem>
|
||||
|
||||
<listitem><para>The BSDTracker Database at: <ulink
|
||||
url="http://www.nycbug.org/index.php?NAV=BSDTracker"></ulink></para></listitem>
|
||||
|
||||
</itemizedlist>
|
||||
|
||||
<para>There is also an initiative to provide certification of BSD
|
||||
system administrators. <ulink
|
||||
url="http://www.bsdcertification.org"></ulink>.</para>
|
||||
|
||||
<para>If your project requires Common Criteria certification,
|
||||
FreeBSD includes the <ulink
|
||||
url="http://www.trustedbsd.org">TrustedBSD</ulink> MAC
|
||||
framework to ease the certification process.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="freebsd-advantages">
|
||||
<title>Advantages to Choosing FreeBSD</title>
|
||||
|
||||
<para>There are many advantages to including FreeBSD solutions in
|
||||
your IT infrastructure:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>FreeBSD is well documented and follows many
|
||||
standards. This allows your existing intermediate and advanced
|
||||
system administrators to quickly transfer their existing Linux
|
||||
and Unix skillsets to FreeBSD administration.</para></listitem>
|
||||
|
||||
<listitem><para>In-house developers have full access to all
|
||||
FreeBSD code[4] for all releases going back to the original
|
||||
FreeBSD release. Included with the code are all of the log
|
||||
messages which provide context to changes and
|
||||
bugfixes. Additionally, a developer can easily replicate any
|
||||
release by simply checking out the code with the desired
|
||||
label. In contrast, Linux traditionally didn't follow this
|
||||
model, but has recently adopted a more mature development
|
||||
model. [5]</para></listitem>
|
||||
|
||||
<listitem><para>In-house developers also have full access to
|
||||
FreeBSD's <ulink
|
||||
url="http://www.gnu.org/software/gnats/">GNATS</ulink>
|
||||
bug-tracking database. They are able to query and track
|
||||
existing bugs as well as submit their own patches for approval
|
||||
and possible committal into the FreeBSD base code.
|
||||
[http://www.freebsd.org/support.html#gnats]</para></listitem>
|
||||
|
||||
<listitem><para>The BSD license allows you to freely modify the
|
||||
code to suit your business purposes. Unlike the GPL, there are
|
||||
no restrictions on how you choose to distribute the resulting
|
||||
software.</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="freebsd-conclusion">
|
||||
<title>Conclusion</title>
|
||||
|
||||
<para>FreeBSD is a mature Unix-like operating system which
|
||||
includes many of the features one would expect in a modern Unix
|
||||
system. For those wishing to incorporate an Open Source solution
|
||||
in their existing infrastructure, FreeBSD is an excellent choice
|
||||
indeed.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="freebsd-addenda">
|
||||
<title>Addenda</title>
|
||||
|
||||
<orderedlist>
|
||||
|
||||
<listitem><para>See also <ulink
|
||||
url="http://www.oreilly.com/catalog/opensources/book/kirkmck.html"></ulink>
|
||||
for a brief history.</para></listitem>
|
||||
|
||||
<listitem><para>For a fairly unbiased view of the merits of each
|
||||
license, see <ulink
|
||||
url="http://en.wikipedia.org/wiki/BSD_and_GPL_licensing"></ulink>.</para></listitem>
|
||||
|
||||
<listitem><para>Using <ulink
|
||||
url="http://www.freebsd.org/ports">FreeBSD's ports
|
||||
collection</ulink>: . Software installation is as easy as
|
||||
<command>pkg_add -r
|
||||
application_name</command>.</para></listitem>
|
||||
|
||||
<listitem><para>In addition, all code is browsable through a
|
||||
web-interface: <ulink
|
||||
url="http://www.freebsd.org/cgi/cvsweb.cgi/"></ulink>.</para></listitem>
|
||||
|
||||
<listitem><para>An interesting overview of the evolving Linux
|
||||
development model can be found at <ulink
|
||||
url="http://linuxdevices.com/articles/AT4155251624.html"></ulink>.</para></listitem>
|
||||
|
||||
</orderedlist>
|
||||
</sect1>
|
||||
</article>
|
||||
|
||||
|
||||
|
Loading…
Reference in a new issue