Index: head/en_US.ISO8859-1/books/handbook/book.xml
===================================================================
--- head/en_US.ISO8859-1/books/handbook/book.xml (revision 52444)
+++ head/en_US.ISO8859-1/books/handbook/book.xml (revision 52445)
@@ -1,319 +1,319 @@
%chapters;
%txtfiles;
]>
&os; HandbookThe FreeBSD Documentation Project$FreeBSD$$FreeBSD$199519961997199819992000200120022003200420052006200720082009201020112012201320142015201620172018The FreeBSD Documentation Project
&legalnotice;
&tm-attrib.freebsd;
&tm-attrib.3com;
&tm-attrib.3ware;
&tm-attrib.arm;
&tm-attrib.adaptec;
&tm-attrib.adobe;
&tm-attrib.apple;
&tm-attrib.google;
&tm-attrib.heidelberger;
&tm-attrib.ibm;
&tm-attrib.ieee;
&tm-attrib.intel;
&tm-attrib.intuit;
&tm-attrib.linux;
&tm-attrib.lsilogic;
&tm-attrib.microsoft;
&tm-attrib.opengroup;
&tm-attrib.oracle;
&tm-attrib.realnetworks;
&tm-attrib.redhat;
&tm-attrib.sun;
&tm-attrib.themathworks;
&tm-attrib.thomson;
&tm-attrib.vmware;
&tm-attrib.wolframresearch;
&tm-attrib.xfree86;
&tm-attrib.xiph;
&tm-attrib.general;
Welcome to &os;! This handbook covers the installation
and day to day use of
- &os; &rel.current;-RELEASE, and
- &os; &rel2.current;-RELEASE. This book is
+ &os; &rel.current;-RELEASE. This book is
the result of ongoing work by many individuals. Some sections
might be outdated. Those interested in helping to update and
expand this document should send email to the &a.doc;.The latest version of this book is available from the
FreeBSD web
site. Previous versions can be obtained from https://docs.FreeBSD.org/doc/.
The book can be downloaded in a variety of formats and
compression options from the &os;
FTP server or one of the numerous
mirror sites. Printed
copies can be purchased at the
FreeBSD
Mall. Searches can be performed on the handbook and
other documents on the
search
page.
&chap.preface;
Getting StartedThis part of the handbook is for users and administrators
who are new to &os;. These chapters:Introduce &os;.Guide readers through the installation process.Teach &unix; basics and fundamentals.Show how to install the wealth of third party
applications available for &os;.Introduce X, the &unix; windowing system, and detail
how to configure a desktop environment that makes users
more productive.The number of forward references in the text have been
kept to a minimum so that this section can be read from front
to back with minimal page flipping.
&chap.introduction;
&chap.bsdinstall;
&chap.basics;
&chap.ports;
&chap.x11;
Common TasksNow that the basics have been covered, this part of the
book discusses some frequently used features of &os;. These
chapters:Introduce popular and useful desktop applications:
browsers, productivity tools, document viewers, and
more.Introduce a number of multimedia tools available for
&os;.Explain the process of building a customized &os;
kernel to enable extra functionality.Describe the print system in detail, both for desktop
and network-connected printer setups.Show how to run Linux applications on the &os;
system.Some of these chapters recommend prior reading, and this
is noted in the synopsis at the beginning of each
chapter.
&chap.desktop;
&chap.multimedia;
&chap.kernelconfig;
&chap.printing;
&chap.linuxemu;
System AdministrationThe remaining chapters cover all aspects of &os; system
administration. Each chapter starts by describing what will
be learned as a result of reading the chapter, and also
details what the reader is expected to know before tackling
the material.These chapters are designed to be read as the information
is needed. They do not need to be read in any particular
order, nor must all of them be read before beginning to use
&os;.
&chap.config;
&chap.boot;
&chap.security;
&chap.jails;
&chap.mac;
&chap.audit;
&chap.disks;
&chap.geom;
&chap.zfs;
&chap.filesystems;
&chap.virtualization;
&chap.l10n;
&chap.cutting-edge;
&chap.dtrace;
&chap.usb-device-mode;
Network Communication&os; is one of the most widely deployed operating systems
for high performance network servers. The chapters in this
part cover:Serial communicationPPP and PPP over
EthernetElectronic MailRunning Network ServersFirewallsOther Advanced Networking TopicsThese chapters are designed to be read when the
information is needed. They do not need to be read in any
particular order, nor is it necessary to read all of them
before using &os; in a network environment.
&chap.serialcomms;
&chap.ppp-and-slip;
&chap.mail;
&chap.network-servers;
&chap.firewalls;
&chap.advanced-networking;
Appendices
&chap.mirrors;
&chap.bibliography;
&chap.eresources;
&chap.pgpkeys;
&chap.freebsd-glossary;
&chap.index;
&chap.colophon;
Index: head/en_US.ISO8859-1/htdocs/index.xsl
===================================================================
--- head/en_US.ISO8859-1/htdocs/index.xsl (revision 52444)
+++ head/en_US.ISO8859-1/htdocs/index.xsl (revision 52445)
@@ -1,334 +1,334 @@
]>
&title;
The &os; Project
&os; is an
operating system used to power
modern servers, desktops, and
embedded
platforms.
A large
community
has continually developed it for
more than thirty years. Its advanced
networking, security, and storage
features have made &os; the platform
of choice for many of the
busiest web sites
and most pervasive
embedded networking and storage
devices.
FreeBSD releases are classified into Production Releases and
Legacy Releases. Production releases are best suited to users looking
for the latest new features. Legacy releases are for users wishing to
stay with a more conservative upgrade strategy.
Documentation files for each release are available for viewing in
HTML format on the Release
Documentation page.
Currently Supported Releases
Complete information about the release date
and the estimated End-Of-Life (EOL) for currently supported
releases can be found on the Supported Releases
section of the FreeBSD
Security Information page.
Complete historical information about the release date, the
classification type, and the effective End-Of-Life (EOL) for
these releases can be found on the Unsupported
Releases section of the FreeBSD Security
Information page.
This table lists the code freeze status for major
branches of the src/ subtree of the FreeBSD Subversion
repository. Commits to any branch listed as "frozen" must first
be reviewed and approved by the relevant contact party. The
status of other subtrees such as ports/ and doc/
is also provided below.
FreeBSD
Release Engineering
This document details the approach used by the FreeBSD release
engineering team to make production-quality releases of the
FreeBSD Operating System. It describes the tools available
for those interested in producing customized FreeBSD releases
for corporate rollouts or commercial
productization.
The primary release engineering team is responsible for approving
MFC
requests during code freezes, setting release schedules, and all of
the other responsibilities laid out in our charter.
Primary RE Team
(re@FreeBSD.org) :
&a.re.members; form the primary release engineering
decision-making group.
The builders release engineering team is responsible
for building and packaging FreeBSD releases on the various supported
platforms.
The third party packages in the Ports Collection are managed by the
portmgr@ team. Among many other responsibilities, the port managers
keep the ports cluster running smoothly to produce binary
packages.
FreeBSD takes security very seriously and its developers are
constantly working on making the operating system as secure as
possible. This page will provide information about what to do in
the event of a security vulnerability affecting your system
Advisories are always signed using the FreeBSD Security Officer
PGP key and are archived, along
with their associated patches, at the http://security.FreeBSD.org/
web server in the advisories
and patches
subdirectories.
The FreeBSD Security Officer provides security advisories for
-STABLE Branches and the Security Branches.
(Advisories are not issued for the -CURRENT Branch,
which is primarily oriented towards &os; developers.)
The -STABLE branch tags have names like stable/10.
The corresponding builds have names like FreeBSD
10.1-STABLE.
Each FreeBSD Release has an associated Security Branch.
The Security Branch tags have names like releng/10.1.
The corresponding builds have names like FreeBSD
10.1-RELEASE-p4.
For users that have previously installed a binary version of &os;
(e.g., &rel.current; or &rel2.current;),
commands:
# freebsd-update fetch
# freebsd-update install
If that fails, follow the other instructions in the security
advisory you care about.
Note that the above procedure is only for users who have
previously installed a binary distribution. Those who have
built from source will need to update their source tree to
upgrade.
Supported FreeBSD releases
Each release is supported by the Security Officer for a limited
time only.
The designation and expected lifetime of all currently supported
branches
and their respective releases
are given below. The Expected EoL (end-of-life)
column indicates the earliest date on which support for that
branch or release will end. Please note that these dates may be
pushed back if circumstances warrant it.
Older releases
are not supported and users are strongly
encouraged to upgrade to one of these supported releases:
Branch
Release
Type
Release Date
Expected EoL
-
stable/10
-
n/a
-
n/a
-
n/a
-
October 31, 2018
-
-
-
releng/10.4
-
10.4-RELEASE
-
Normal
-
October 3, 2017
-
October 31, 2018
-
-
stable/11
n/a
n/a
n/a
September 30, 2021
releng/11.2
11.2-RELEASE
n/a
June 28, 2018
11.3-RELEASE + 3 months
In the run-up to a release, a number of -BETA and -RC releases
may be published for testing purposes. These releases are only
supported for a few weeks, as resources permit, and will not be
listed as supported on this page. Users are strongly discouraged
from running these releases on production systems.
The FreeBSD support model
Effective &os; 11.0-RELEASE, the support model has been
changed to allow more rapid development while also providing
timely security updates for all supported releases.
Under the new support model, each major version's stable branch
is explicitly supported for 5 years, while each individual point
release is only supported for three months after the next point
release.
The details and rationale behind this change can be found in the
official
announcement sent in February 2015.
Previously, branches were designated as either Normal or
Extended. The designation was used as a guideline for
determining the lifetime of the branch as follows:
Normal
Releases which are published from a -STABLE branch were
supported by the Security Officer for a minimum of 12 months
after the release, and for sufficient additional time (if
needed) to ensure that there is a newer release for at least
3 months before the older Normal release expires.
Extended
Selected releases (normally every second release plus the last
release from each -STABLE branch) were supported by the Security
Officer for a minimum of 24 months after the release, and for
sufficient additional time (if needed) to ensure that there is
a newer Extended release for at least 3 months before the older
Extended release expires.
Most users of &os; will have hardware for either the amd64,
i386, or armv6 architectures.
Modern PCs use the amd64 architecture, including those with
Intel® branded processors. Computers with more than
3 GB of memory should use amd64. If the computer is an
older, 32-bit only model, use i386. For embedded devices and
single-board computers (SBC) such as the Raspberry Pi, Beagle
Bone Black, Panda Board, and Zed Board, use the armv6 SD card
image which supports ARMv6 and ARMv7 processors.
All other users should reference the
complete list
of supported &os; platforms.
Choosing an Image
The &os; installer can be downloaded in a number of different
formats including CD (disc1), DVD (dvd1), and Network Install
(bootonly) sized ISO
Disc Images, as well as regular and mini USB memory stick
images. Recent versions of &os; are also offered as prebuilt
expandable Virtual Machine images, and as SD Card images for embedded
platforms.
&os; Deployment Statistics
While &os; does not gather deployment statistics, having
statistical information available is essential. Please consider
installing the sysutils/bsdstats
package, which collects hardware and software statistics,
helping developers understand how to best focus their
efforts. The information collected is available at the
bsdstats.org website.
If you are interested in a purely experimental
snapshot release of &os;-CURRENT (AKA
&rel.head;-CURRENT), aimed at developers and bleeding-edge
testers only, then please see the &os; Snapshot Releases page. For
more information about past, present and future releases in
general, please visit the release information
page.
If you plan on getting &os; via HTTP or FTP, please check
the listing of mirror
sites in the Handbook to see if there is a site
closer to you.
Install &os;
There are many options for installing &os;, including
installation from CD-ROM, DVD, USB Memory Stick or even directly
using anonymous FTP, HTTP, or NFS. Please read through the &os;
installation guide before downloading the entire &os;
distribution.
For downloading past releases, please visit the FTP
archive.
&os;-derived Operating System Distributions
&os; is widely used as a building block for other commercial
and open-source operating systems. The projects below are
widely used and of particular interest to &os; users.
FreeNAS is an open
source storage platform based on &os; and supports sharing
across Windows, Apple, and UNIX-like systems.
TrueOS (formerly
PC-BSD) is a &os;
derivative with a graphical installer. The desktop option installs
The Lumina Desktop Environment,
a fully BSD Licensed desktop, with
impressive desktop tools aimed at ease of use for the casual computer
user.
pfSense is a
&os; based customized distribution tailored for
use as a firewall and router.
Applications and Utility Software
The Ports Collection
The &os; Ports Collection is a diverse collection of utility
and application software that has been ported to &os;.
For information about how you can contribute
your favorite piece of software to the Ports Collection,
have a look at The
Porter's Handbook and the article Contributing
to &os;.
