Index: head/en_US.ISO8859-1/htdocs/releases/12.0R/errata/errata.xml
===================================================================
--- head/en_US.ISO8859-1/htdocs/releases/12.0R/errata/errata.xml (revision 51061)
+++ head/en_US.ISO8859-1/htdocs/releases/12.0R/errata/errata.xml (revision 51062)
@@ -1,103 +1,104 @@
%release;
%sponsor;
%vendor;
]>
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ version="5.0">
- &os; &release; Errata
+ &os; &release; Errata
- The &os; Project
+
+ The &os; Project
+ $FreeBSD$
- 2015
-
- The &os; Documentation Project
+ 2017
+ The &os; Documentation
+ Project
&tm-attrib.freebsd;
&tm-attrib.intel;
&tm-attrib.sparc;
&tm-attrib.general;
This document lists errata items for &os; &release;,
- containing significant information discovered after the release
- or too late in the release cycle to be otherwise included in the
- release documentation.
- This information includes security advisories, as well as news
- relating to the software or documentation that could affect its
- operation or usability. An up-to-date version of this document
- should always be consulted before installing this version of
+ containing significant information discovered after the
+ release or too late in the release cycle to be otherwise
+ included in the release documentation. This information
+ includes security advisories, as well as news relating to the
+ software or documentation that could affect its operation or
+ usability. An up-to-date version of this document should
+ always be consulted before installing this version of
&os;.
- This errata document for &os; &release;
- will be maintained until the release of &os; &release.next;.
+ This errata document for &os; &release; will be maintained
+ until the release of &os; &release.next;.Introduction
- This errata document contains late-breaking news
- about &os; &release;
- Before installing this version, it is important to consult this
- document to learn about any post-release discoveries or problems
- that may already have been found and fixed.
+ This errata document contains late-breaking
+ news about &os; &release; Before installing this
+ version, it is important to consult this document to learn about
+ any post-release discoveries or problems that may already have
+ been found and fixed.Any version of this errata document actually distributed
with the release (for example, on a CDROM distribution) will be
out of date by definition, but other copies are kept updated on
the Internet and should be consulted as the current
- errata for this release. These other copies of the
- errata are located at
- ,
- plus any sites
- which keep up-to-date mirrors of this location.
+ errata for this release. These other copies of the
+ errata are located at , plus any
+ sites which keep up-to-date mirrors of this location.
Source and binary snapshots of &os; &release.branch; also
contain up-to-date copies of this document (as of the time of
the snapshot).For a list of all &os; CERT security advisories, see
.Security Advisories
&security;
Errata Notices
&errata;
Open IssuesNo open issues.Late-Breaking NewsNo news.
Index: head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/hardware.xml
===================================================================
--- head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/hardware.xml (revision 51061)
+++ head/en_US.ISO8859-1/htdocs/releases/12.0R/hardware/hardware.xml (revision 51062)
@@ -1,1460 +1,1479 @@
%release;
%sponsor;
%vendor;
%devauto;
]>
-
- &os; &release.current; Hardware Notes
-
+
- The &os; Documentation Project
+
+ &os; &release.current; Hardware Notes
- $FreeBSD$
+
+ The &os; Documentation Project
+
+ $FreeBSD$200020012002200320042005200620072008200920102011201220132014201520162017
- The &os; Documentation Project
+ The &os; Documentation
+ Project
&tm-attrib.freebsd;
&tm-attrib.amd;
&tm-attrib.fujitsu;
&tm-attrib.ibm;
&tm-attrib.intel;
&tm-attrib.sparc;
&tm-attrib.sun;
&tm-attrib.general;
IntroductionThis document contains the hardware compatibility notes for
&os; &release.current;. It lists the hardware platforms
supported by &os;, as well as the various types of hardware
devices (storage controllers, network interfaces, and so on),
along with known working instances of these devices.Supported Processors and System BoardsThis section provides some architecture-specific information
about the specific processors and systems that are supported by
each architecture.amd64Since mid-2003 &os;/&arch.amd64; has supported the AMD64
(Hammer) and &intel; EM64T architecture, and is
now one of the Tier-1 platforms (fully supported
architecture), which are expected to be Production Quality
with respects to all aspects of the &os; operating system,
including installation and development environments.Note that there are two names for this architecture, AMD64
(AMD) and Intel EM64T (Extended Memory 64-bit Technology).
64-bit mode of the two architectures are almost compatible
with each other, and &os;/&arch.amd64; supports them
both.As of this writing, the following processors are
supported:&amd.athlon;64 (Clawhammer).&amd.opteron; (Sledgehammer).&amd.sempron;.&amd.turion;.&amd.phenom;.All multi-core &intel; &xeon; processors except
Sossaman have EM64T support.
- The single-core &intel; &xeon;
- processors Nocona, Irwindale,
+ The single-core &intel; &xeon; processors
+ Nocona, Irwindale,
Potomac, and Cranford have
EM64T support.All &intel; &core; 2 (not &core; Duo) and later
processorsAll &intel; &core; i range of processorsAll &intel; &pentium; D processors
- All &intel; ¢rino; Duo and ¢rino; Pro platforms
+ All &intel; ¢rino; Duo and ¢rino; Pro
+ platforms&intel; &pentium; 4s and &celeron; Ds using
the Cedar Mill core have EM64T
support.
- Some &intel; &pentium; 4s and &celeron; Ds using
- the Prescott core have EM64T support. See
- the Intel
- Processor Spec Finder for the definitive answer about
- EM64T support in Intel processors.
+ Some &intel; &pentium; 4s and &celeron; Ds using the
+ Prescott core have EM64T support. See the
+ Intel
+ Processor Spec Finder for the definitive answer
+ about EM64T support in Intel processors.&intel; EM64T is an extended version of IA-32 (x86) and
different from &intel; IA-64 (Itanium) architecture. Some of
&intel;'s old documentation refers to &intel; EM64T as
64-bit extension technology or
IA-32e.Both Uniprocessor (UP) and Symmetric Multi-processor (SMP)
configurations are supported.In many respects, &os;/&arch.amd64; is similar to
&os;/&arch.i386;, in terms of drivers supported. Generally,
drivers that already function correctly on other 64-bit
platforms should work.
-
i386&os;/&arch.i386; runs on a wide variety of IBM PC
- compatible machines. Due to the wide range of
+ compatible machines. Due to the wide range of
hardware available for this architecture, it is impossible
to exhaustively list all combinations of equipment supported
by &os;. Nevertheless, some general guidelines are
presented here.Almost all &i386;-compatible processors with a floating
- point unit are supported. All &intel; processors beginning
+ point unit are supported. All &intel; processors beginning
with the 80486 are supported, including the 80486, &pentium;,
&pentium; Pro, &pentium; II, &pentium; III, &pentium; 4, and
variants thereof, such as the &xeon; and &celeron; processors.
All &i386;-compatible AMD processors are also supported,
including the &am486;, &am5x86;, K5, &amd.k6; (and variants),
&amd.athlon; (including Athlon-MP, Athlon-XP, Athlon-4, and
Athlon Thunderbird), and &amd.duron; processors. The AMD
Élan SC520 embedded processor is supported. The
Transmeta Crusoe is recognized and supported, as are
&i386;-compatible processors from Cyrix and NexGen.There is a wide variety of motherboards available for this
architecture. Motherboards using the ISA, VLB, EISA, AGP, and
PCI expansion buses are well-supported. There is some
limited support for the MCA (MicroChannel)
expansion bus used in the IBM PS/2 line of PCs.Symmetric multi-processor (SMP) systems are generally
supported by &os;, although in some cases, BIOS or motherboard
bugs may generate some problems. Perusal of the archives of
the &a.smp; may yield some clues.&os; will take advantage of SMT (Symmetric MultiThreading,
also known as HyperThreading on &intel; CPUs) on the supported
CPUs. The GENERIC kernel which is
installed by default will automatically detect the additional
logical processors. The default &os; scheduler recognizes
processor topology on the system and selects logical and
physical processors to obtain optimal performance.
The &man.smp.4; manual page has more details.&os; will take advantage of Physical Address Extensions
(PAE) support on CPUs that support this feature. A kernel
with the PAE feature enabled will detect
memory above 4 gigabytes and allow it to be used by the
system. This feature places constraints on the device drivers
and other features of &os; which may be used; consult the
&man.pae.4; manual page for more details.&os; will generally run on i386-based laptops, albeit with
varying levels of support for certain hardware features such
as sound, graphics, power management, and PCCARD expansion
slots. These features tend to vary in idiosyncratic ways
between machines, and frequently require special-case support
in &os; to work around hardware bugs or other oddities. When
in doubt, a search of the archives of the &a.mobile; may be
useful.Most modern laptops (as well as many desktops) use the
Advanced Configuration and Power Management (ACPI) standard.
&os; supports ACPI via the ACPI Component Architecture
reference implementation from &intel;, as described in the
&man.acpi.4; manual page. The use of ACPI causes
instabilities on some machines and it may be necessary to
disable the ACPI driver, which is normally loaded via a kernel
module. This may be accomplished by adding the following line
to /boot/device.hints:hint.acpi.0.disabled="1"Users debugging ACPI-related problems may find it useful
to disable portions of the ACPI functionality. The
&man.acpi.4; manual page has more information on how to do
this via loader tunables.ACPI depends on a Differentiated System Descriptor Table
(DSDT) provided by each machine's BIOS. Some machines have
bad or incomplete DSDTs, which prevents ACPI from functioning
correctly. Replacement DSDTs for some machines can be found
- at the DSDT
- section of the ACPI4Linux project
- Web site. &os; can use these DSDTs to override the DSDT
- provided by the BIOS; see the &man.acpi.4; manual page for
- more information.
+ at the DSDT
+ section of the ACPI4Linux
+ project Web site. &os; can use these DSDTs to override the
+ DSDT provided by the BIOS; see the &man.acpi.4; manual page
+ for more information.
powerpc
- All Apple PowerPC machines with built-in USB are supported,
- as well a limited selection of non-Apple machines,
+ All Apple PowerPC machines with built-in USB are
+ supported, as well a limited selection of non-Apple machines,
including KVM on POWER7SMP is supported on all systems with more than
1 processor.sparc64This section describes the systems currently known to be
- supported by &os; on the Fujitsu &sparc64; and Sun &ultrasparc;
- platforms.
+ supported by &os; on the Fujitsu &sparc64; and Sun
+ &ultrasparc; platforms.
SMP is supported on all systems with more than 1
processor.When using the GENERIC kernel,
&os;/&arch.sparc64; systems not equipped with a framebuffer
supported by the &man.creator.4; (Sun Creator, Sun Creator3D
- and Sun Elite3D) or &man.machfb.4; (Sun PGX and Sun PGX64
- as well as the ATI Mach64 chips found onboard in for example
- &sun.blade; 100, &sun.blade; 150, &sun.ultra; 5 and &sun.ultra; 10)
- driver must use the serial console.
+ and Sun Elite3D) or &man.machfb.4; (Sun PGX and Sun PGX64 as
+ well as the ATI Mach64 chips found onboard in for example
+ &sun.blade; 100, &sun.blade; 150, &sun.ultra; 5 and
+ &sun.ultra; 10) driver must use the serial console.
If you have a system that is not listed here, it may not
have been tested with &os; &release.current;. We encourage
you to try it and send a note to the &a.sparc; with your
results, including which devices work and which do not.The following systems are fully supported by &os;:Naturetech GENIALstation 777S&sun.blade; 100&sun.blade; 150&sun.enterprise; 150&sun.enterprise; 220R&sun.enterprise; 250&sun.enterprise; 420R&sun.enterprise; 450&sun.fire; B100s (support for the on-board NICs first
appeared in 8.1-RELEASE)&sun.fire; V100&sun.fire; V120Sun &netra; t1 100/105Sun &netra; T1 AC200/DC200Sun &netra; t 1100Sun &netra; t 1120Sun &netra; t 1125Sun &netra; t 1400/1405Sun &netra; 120Sun &netra; X1Sun &sparcengine; Ultra AX1105Sun &sparcengine; Ultra AXeSun &sparcengine; Ultra AXiSun &sparcengine; Ultra AXmpSun &sparcengine; CP1500&sun.ultra; 1&sun.ultra; 1E&sun.ultra; 2&sun.ultra; 5&sun.ultra; 10&sun.ultra; 30&sun.ultra; 60&sun.ultra; 80&sun.ultra; 450The following systems are partially supported by &os;. In
- particular the fiber channel controllers in SBus-based systems are not
- supported. However, it is possible to use these with a SCSI controller
- supported by the &man.esp.4; driver (Sun ESP SCSI, Sun FAS Fast-SCSI
- and Sun FAS366 Fast-Wide SCSI controllers).
+ particular the fiber channel controllers in SBus-based systems
+ are not supported. However, it is possible to use these with
+ a SCSI controller supported by the &man.esp.4; driver (Sun ESP
+ SCSI, Sun FAS Fast-SCSI and Sun FAS366 Fast-Wide SCSI
+ controllers).
&sun.enterprise; 3500&sun.enterprise; 4500
- Starting with 7.2-RELEASE, &arch.sparc64; systems based on Sun
- &ultrasparc; III and beyond are also supported by &os;, which includes
- the following known working systems:
+ Starting with 7.2-RELEASE, &arch.sparc64; systems based on
+ Sun &ultrasparc; III and beyond are also supported by &os;,
+ which includes the following known working systems:&sun.blade; 1000&sun.blade; 1500&sun.blade; 2000&sun.blade; 2500&sun.fire; 280R&sun.fire; V210
- &sun.fire; V215 (support first appeared in 7.3-RELEASE and 8.1-RELEASE)
+ &sun.fire; V215 (support first appeared in 7.3-RELEASE
+ and 8.1-RELEASE)&sun.fire; V240
- &sun.fire; V245 (support first appeared in 7.3-RELEASE and 8.1-RELEASE)
+ &sun.fire; V245 (support first appeared in 7.3-RELEASE
+ and 8.1-RELEASE)&sun.fire; V250&sun.fire; V440 (support for the on-board NICs first
appeared in 7.3-RELEASE and 8.0-RELEASE)
- &sun.fire; V480 (501-6780 and 501-6790 centerplanes only, for
- which support first appeared in 7.3-RELEASE and 8.1-RELEASE,
- other centerplanes might work beginning with 8.3-RELEASE and 9.0-RELEASE)
+ &sun.fire; V480 (501-6780 and 501-6790 centerplanes
+ only, for which support first appeared in 7.3-RELEASE and
+ 8.1-RELEASE, other centerplanes might work beginning with
+ 8.3-RELEASE and 9.0-RELEASE)&sun.fire; V880
- &sun.fire; V890 (support first appeared in 7.4-RELEASE and 8.1-RELEASE,
- non-mixed &ultrasparc; IV/IV+ CPU-configurations only)
+ &sun.fire; V890 (support first appeared in 7.4-RELEASE
+ and 8.1-RELEASE, non-mixed &ultrasparc; IV/IV+
+ CPU-configurations only)&netra; 20/&netra; T4The following Sun &ultrasparc; systems are not tested but
believed to be also supported by &os;:&sun.fire; V125
- &sun.fire; V490 (support first appeared in 7.4-RELEASE and 8.1-RELEASE,
- non-mixed &ultrasparc; IV/IV+ CPU-configurations only)
+ &sun.fire; V490 (support first appeared in 7.4-RELEASE
+ and 8.1-RELEASE, non-mixed &ultrasparc; IV/IV+
+ CPU-configurations only)
- Starting with 7.4-RELEASE and 8.1-RELEASE, &arch.sparc64; systems based on
- Fujitsu &sparc64; V are also supported by &os;, which
- includes the following known working systems:
+ Starting with 7.4-RELEASE and 8.1-RELEASE, &arch.sparc64;
+ systems based on Fujitsu &sparc64; V are also supported by
+ &os;, which includes the following known working
+ systems:Fujitsu &primepower; 250
- The following Fujitsu &primepower; systems are not tested but
- believed to be also supported by &os;:
+ The following Fujitsu &primepower; systems are not tested
+ but believed to be also supported by &os;:Fujitsu &primepower; 450Fujitsu &primepower; 650Fujitsu &primepower; 850Supported DevicesThis section describes the devices currently known to be
supported by &os;. Other configurations may also work, but
simply have not been tested yet. Feedback, updates, and
corrections to this list are encouraged.Where possible, the drivers applicable to each device or
class of devices is listed. If the driver in question has a
manual page in the &os; base distribution (most should), it is
referenced here. Information on specific models of supported
devices, controllers, etc. can be found in the manual
pages.The device lists in this document are being generated
automatically from &os; manual pages. This means that some
devices, which are supported by multiple drivers, may appear
multiple times.Disk Controllers[&arch.amd64;, &arch.i386;, &arch.sparc64;]
IDE/ATA controllers (&man.ata.4; driver)
&hwlist.aac;
&hwlist.adv;
&hwlist.adw;
&hwlist.aha;
&hwlist.ahc;
&hwlist.ahci;
&hwlist.ahd;
&hwlist.aic;
&hwlist.amr;
&hwlist.arcmsr;
&hwlist.bt;
&hwlist.ciss;
&hwlist.dpt;
[&arch.amd64;, &arch.i386;] Booting from these
- controllers is supported. EISA adapters are not
+ controllers is supported. EISA adapters are not
supported.
&hwlist.esp;
&hwlist.hpt27xx;
&hwlist.hptiop;
&hwlist.hptmv;
&hwlist.hptrr;
&hwlist.ida;
&hwlist.iir;
&hwlist.ips;
&hwlist.isci;
&hwlist.isp;
&hwlist.mfi;
&hwlist.mlx;
[&arch.amd64;, &arch.i386;] Booting from these
- controllers is supported. EISA adapters are not
+ controllers is supported. EISA adapters are not
supported.
&hwlist.mly;
&hwlist.mpr;
&hwlist.mps;
&hwlist.mpt;
&hwlist.mrsas;
&hwlist.mvs;
&hwlist.ncr;
&hwlist.ncv;
&hwlist.nsp;
&hwlist.pms;
&hwlist.pst;
&hwlist.siis;
&hwlist.stg;
&hwlist.sym;
&hwlist.trm;
&hwlist.twa;
&hwlist.twe;
&hwlist.tws;
&hwlist.vpo;
With all supported SCSI controllers, full support is
provided for SCSI-I, SCSI-II, and SCSI-III peripherals,
including hard disks, optical disks, tape drives (including
DAT, 8mm Exabyte, Mammoth, and DLT), medium changers,
processor target devices and CD-ROM drives. WORM devices that
support CD-ROM commands are supported for read-only access by
the CD-ROM drivers (such as &man.cd.4;). WORM/CD-R/CD-RW
- writing support is provided by &man.cdrecord.1;, which is a
- part of the sysutils/cdrtools port in the Ports
- Collection.
+ writing support is provided by &man.cdrecord.1;, which is
+ a part of the sysutils/cdrtools port in the
+ Ports Collection.
The following CD-ROM type systems are supported at this
time:SCSI interface (also includes ProAudio Spectrum and
SoundBlaster SCSI) (&man.cd.4;)ATAPI IDE interface (&man.acd.4;)Ethernet Interfaces
&hwlist.ae;
&hwlist.age;
&hwlist.ale;
&hwlist.aue;
&hwlist.axe;
ASIX Electronics AX88178A/AX88179 USB Gigabit Ethernet
adapters (&man.axge.4; driver)
&hwlist.bce;
[&arch.amd64;, &arch.i386;] Broadcom BCM4401 based Fast
Ethernet adapters (&man.bfe.4; driver)
&hwlist.bge;
&hwlist.bnxt;
&hwlist.bxe;
&hwlist.cas;
&hwlist.cdce;
[&arch.amd64;, &arch.i386;] Crystal Semiconductor
CS89x0-based NICs (&man.cs.4; driver)
&hwlist.cue;
&hwlist.cxgb;
&hwlist.cxgbe;
&hwlist.dc;
&hwlist.de;
&hwlist.ed;
&hwlist.em;
&hwlist.ep;
Agere ET1310 Gigabit Ethernet adapters
(&man.et.4; driver)
&hwlist.ex;
&hwlist.fe;
&hwlist.fxp;
&hwlist.gem;
&hwlist.hme;
&hwlist.ipheth;
&hwlist.ixgb;
&hwlist.ixgbe;
&hwlist.ixl;
&hwlist.jme;
&hwlist.kue;
&hwlist.lge;
&hwlist.mlx4en;
&hwlist.mlx5en;
&hwlist.msk;
&hwlist.mxge;
&hwlist.my;
&hwlist.nfe;
&hwlist.nge;
&hwlist.nxge;
&hwlist.oce;
&hwlist.pcn;
&hwlist.qlxgb;
&hwlist.qlxgbe;
&hwlist.qlxge;
&hwlist.re;
&hwlist.rl;
&hwlist.rue;
&hwlist.sf;
&hwlist.sfxge;
&hwlist.sge;
&hwlist.sis;
&hwlist.sk;
&hwlist.smsc;
&hwlist.sn;
&hwlist.ste;
&hwlist.stge;
&hwlist.ti;
&hwlist.tl;
[&arch.amd64;, &arch.i386;] SMC 83c17x
(EPIC)-based Ethernet NICs (&man.tx.4; driver)
&hwlist.txp;
&hwlist.udav;
&hwlist.urndis;
&hwlist.vge;
&hwlist.vr;
&hwlist.vte;
&hwlist.vx;
&hwlist.vxge;
&hwlist.wb;
&hwlist.xe;
&hwlist.xl;
FDDI Interfaces[&arch.i386;] DEC DEFPA PCI (&man.fpa.4; driver)[&arch.i386;] DEC DEFEA EISA (&man.fpa.4; driver)Wireless Network Interfaces[&arch.amd64;, &arch.i386;] Cisco/Aironet
802.11b wireless adapters (&man.an.4; driver)
&hwlist.ath;
&hwlist.bwi;
&hwlist.bwn;
[&arch.i386;, &arch.amd64;] Intel PRO/Wireless 2100
MiniPCI network adapter (&man.ipw.4; driver)[&arch.i386;, &arch.amd64;] Intel PRO/Wireless
2200BG/2915ABG MiniPCI and 2225BG PCI network adapters
(&man.iwi.4; driver)[&arch.i386;, &arch.amd64;] Intel Dual Band Wireless AC
3160/7260/7265 IEEE 802.11ac network adapters (&man.iwm.4;
driver)[&arch.i386;, &arch.amd64;] Intel Wireless WiFi Link
4965AGN IEEE 802.11n PCI network adapters
(&man.iwn.4; driver)
- [&arch.i386;, &arch.amd64;] Marvell Libertas IEEE 802.11b/g
- PCI network adapters (&man.malo.4; driver)
+ [&arch.i386;, &arch.amd64;] Marvell Libertas IEEE
+ 802.11b/g PCI network adapters (&man.malo.4; driver)Marvell 88W8363 IEEE 802.11n wireless network
adapters (&man.mwl.4; driver)
&hwlist.otus;
&hwlist.ral;
&hwlist.rsu;
Realtek RTL8192C, RTL8188E, RTL8812A and RTL8821A based
PCIe IEEE 802.11b/g/n wireless network adapters (&man.rtwn.4;
driver)
&hwlist.rum;
&hwlist.run;
&hwlist.uath;
&hwlist.upgt;
&hwlist.ural;
&hwlist.urtw;
[&arch.amd64;, &arch.i386;] Lucent
Technologies WaveLAN/IEEE 802.11b wireless network adapters
and workalikes using the Lucent Hermes, Intersil PRISM-II,
Intersil PRISM-2.5, Intersil Prism-3, and Symbol Spectrum24
chipsets (&man.wi.4; driver)[&arch.i386;, &arch.amd64;] Intel PRO/Wireless 3945ABG
MiniPCI network adapters (&man.wpi.4; driver)
&hwlist.zyd;
Miscellaneous Networks
&hwlist.ce;
&hwlist.cx;
&hwlist.cp;
&hwlist.ctau;
&hwlist.cm;
Serial Interfaces[&arch.amd64;, &arch.i386;] PC standard
8250, 16450, and 16550-based serial ports (&man.sio.4;
driver)
&hwlist.uart;
&hwlist.scc;
[&arch.amd64;, &arch.i386;] AST 4 port serial card using
shared IRQARNET 8 port serial card using shared IRQARNET (now Digiboard) Sync 570/i high-speed
serial[&arch.i386;] Boca multi-port serial cardsBoca BB1004 4-Port serial card (Modems
not supported)Boca IOAT66 6-Port serial card (Modems
supported)Boca BB1008 8-Port serial card (Modems
not supported)Boca BB2016 16-Port serial card (Modems
supported)[&arch.i386;] Comtrol Rocketport card (&man.rp.4;
driver)[&arch.i386;] Cyclades Cyclom-Y serial board (&man.cy.4;
driver)[&arch.i386;] STB 4 port card using shared IRQ[&arch.amd64;, &arch.i386;] PCI-Based multi-port serial
boards (&man.puc.4; driver)[&arch.amd64;, &arch.i386;] Actiontech 56K PCI
- [&arch.amd64;, &arch.i386;] Avlab Technology, PCI IO 2S
- and PCI IO 4S
+ [&arch.amd64;, &arch.i386;] Avlab Technology, PCI IO
+ 2S and PCI IO 4S
- [&arch.amd64;, &arch.i386;] Comtrol RocketPort 550
+ [&arch.amd64;, &arch.i386;] Comtrol RocketPort
+ 550[&arch.amd64;, &arch.i386;] Decision Computers PCCOM
4-port serial and dual port RS232/422/485[&arch.amd64;, &arch.i386;] Dolphin Peripherals
4025/4035/4036[&arch.amd64;, &arch.i386;] IC Book Labs Dreadnought
16x Lite and Pro[&arch.amd64;, &arch.i386;] Lava Computers
2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550[&arch.amd64;, &arch.i386;] Middle Digital, Weasle
serial port[&arch.amd64;, &arch.i386;] Moxa Industio CP-114,
Smartio C104H-PCI and C168H/PCI[&arch.amd64;, &arch.i386;] NEC PK-UG-X001 and
PK-UG-X008[&arch.amd64;, &arch.i386;] Netmos NM9835
PCI-2S-550[&arch.amd64;, &arch.i386;] Oxford Semiconductor
OX16PCI954 PCI UART[&arch.amd64;, &arch.i386;] Syba Tech SD-LAB
PCI-4S2P-550-ECP[&arch.amd64;, &arch.i386;] SIIG Cyber I/O PCI
16C550/16C650/16C850[&arch.amd64;, &arch.i386;] SIIG Cyber 2P1S PCI
16C550/16C650/16C850[&arch.amd64;, &arch.i386;] SIIG Cyber 2S1P PCI
16C550/16C650/16C850[&arch.amd64;, &arch.i386;] SIIG Cyber 4S PCI
- 16C550/16C650/16C850
+ 16C550/16C650/16C850
[&arch.amd64;, &arch.i386;] SIIG Cyber Serial (Single
and Dual) PCI 16C550/16C650/16C850[&arch.amd64;, &arch.i386;] Syba Tech
Ltd. PCI-4S2P-550-ECP[&arch.amd64;, &arch.i386;] Titan PCI-200H and
PCI-800H[&arch.amd64;, &arch.i386;] US Robotics (3Com) 3CP5609
modem[&arch.amd64;, &arch.i386;] VScom PCI-400 and
PCI-800
&hwlist.rc;
Sound Devices
&hwlist.snd.ad1816;
&hwlist.snd.als4000;
&hwlist.snd.atiixp;
&hwlist.snd.audiocs;
&hwlist.snd.cmi;
&hwlist.snd.cs4281;
&hwlist.snd.csa;
&hwlist.snd.ds1;
&hwlist.snd.emu10k1;
&hwlist.snd.emu10kx;
&hwlist.snd.envy24;
&hwlist.snd.envy24ht;
&hwlist.snd.es137x;
&hwlist.snd.ess;
&hwlist.snd.fm801;
&hwlist.snd.gusc;
&hwlist.snd.hda;
&hwlist.snd.hdspe;
&hwlist.snd.ich;
&hwlist.snd.maestro;
&hwlist.snd.maestro3;
&hwlist.snd.mss;
&hwlist.snd.neomagic;
&hwlist.snd.sbc;
&hwlist.snd.solo;
&hwlist.snd.spicds;
&hwlist.snd.t4dwave;
&hwlist.snd.via8233;
&hwlist.snd.via82c686;
&hwlist.snd.vibes;
Camera and Video Capture Devices
&hwlist.bktr;
[&arch.i386;] Connectix QuickCamUSB Devices[&arch.amd64;, &arch.i386;] A
range of USB peripherals are supported; devices known to work
are listed in this section. Owing to the generic nature of
most USB devices, with some exceptions any device of a given
class will be supported, even if not explicitly listed
here.[&arch.amd64;, &arch.i386;]
USB Ethernet adapters can be found in the section listing
Ethernet
interfaces.
- [&arch.amd64;, &arch.i386;]
- USB Bluetooth adapters can be found in Bluetooth section.
+ [&arch.amd64;, &arch.i386;] USB Bluetooth adapters can
+ be found in Bluetooth
+ section.
&hwlist.ohci;
&hwlist.uhci;
[&arch.amd64;, &arch.i386;] USB
2.0 controllers using the EHCI interface (&man.ehci.4;
driver)[&arch.amd64;, &arch.i386;] Hubs
- [&arch.amd64;, &arch.i386;] Keyboards (&man.ukbd.4; driver)
+ [&arch.amd64;, &arch.i386;] Keyboards (&man.ukbd.4;
+ driver)[&arch.amd64;, &arch.i386;] MiscellaneousAssist Computer Systems PC Camera C-M1ActiveWire I/O BoardCreative Technology Video Blaster WebCam PlusD-Link DSB-R100 USB Radio (&man.ufm.4; driver)Mirunet AlphaCam Plus
&hwlist.urio;
&hwlist.umodem;
- [&arch.amd64;, &arch.i386;] Mice (&man.ums.4; driver)
+ [&arch.amd64;, &arch.i386;] Mice (&man.ums.4;
+ driver)
&hwlist.ulpt;
&hwlist.ubsa;
&hwlist.ubser;
&hwlist.uftdi;
&hwlist.uplcom;
&hwlist.umct;
&hwlist.umass;
[&arch.amd64;, &arch.i386;] Audio Devices
(&man.uaudio.4; driver)
&hwlist.uvisor;
IEEE 1394 (Firewire) Devices
&hwlist.fwohci;
[&arch.amd64;, &arch.i386;, &arch.sparc64;] Serial Bus
Protocol 2 (SBP-2) storage devices (&man.sbp.4; driver)Bluetooth Devices
&hwlist.ng.bt3c;
&hwlist.ng.ubt;
Cryptographic Accelerators
&hwlist.hifn;
&hwlist.safe;
&hwlist.ubsec;
Miscellaneous[&arch.amd64;, &arch.i386;] FAX-Modem/PCCARDMELCO IGM-PCM56K/IGM-PCM56KHNokia Card Phone 2.0 (gsm900/dcs1800 HSCSD
terminal)[&arch.amd64;, &arch.i386;] Floppy drives
(&man.fdc.4; driver)[&arch.amd64;, &arch.i386;] VGA-compatible video cards
(&man.vga.4; driver)Information regarding specific video cards and
compatibility with Xorg can be
- found at http://www.x.org/.
+ found at http://www.x.org/.
[&arch.amd64;, &arch.i386;] Keyboards including:[&arch.i386;] AT-style keyboards (&man.atkbd.4;
driver)[&arch.amd64;, &arch.i386;] PS/2 keyboards
(&man.atkbd.4; driver)[&arch.amd64;, &arch.i386;]
USB keyboards (&man.ukbd.4; driver)[&arch.amd64;, &arch.i386;]
Pointing devices including:[&arch.amd64;, &arch.i386;] Bus mice and
compatible devices (&man.mse.4; driver)[&arch.amd64;, &arch.i386;] PS/2 mice and compatible
devices, including many laptop pointing devices
(&man.psm.4; driver)Serial mice and compatible devices[&arch.amd64;, &arch.i386;]
USB mice (&man.ums.4; driver)&man.moused.8; has more information on using pointing
devices with &os;. Information on using pointing devices
- with Xorg can be found at http://www.x.org/.
+ with Xorg can be found at http://www.x.org/.
[&arch.amd64;, &arch.i386;] PC standard
parallel ports (&man.ppc.4; driver)[&arch.i386;, &arch.amd64;] PC-compatible joysticks
(&man.joy.4; driver)[&arch.i386;] PHS Data Communication Card/PCCARDNTT DoCoMo P-in Comp@ctPanasonic KX-PH405SII MC-P200[&arch.i386;] Xilinx XC6200-based reconfigurable hardware
- cards compatible with the HOT1 from Virtual Computers (xrpu
- driver).
-
+ cards compatible with the HOT1 from Virtual Computers
+ (xrpu driver).
Index: head/en_US.ISO8859-1/htdocs/releases/12.0R/readme/readme.xml
===================================================================
--- head/en_US.ISO8859-1/htdocs/releases/12.0R/readme/readme.xml (revision 51061)
+++ head/en_US.ISO8859-1/htdocs/releases/12.0R/readme/readme.xml (revision 51062)
@@ -1,411 +1,432 @@
%release;
]>
-
-
- &os; &release.current; README
-
+
- The &os; Project
+
+ &os; &release.current; README
+
+ The &os; Project
+
+
$FreeBSD$2000200120022003200420052006200720082009201020112012201320142015
- The &os; Documentation Project
+ 2016
+ 2017
+ The &os; Documentation
+ Project
&tm-attrib.freebsd;
&tm-attrib.intel;
&tm-attrib.opengroup;
&tm-attrib.sparc;
&tm-attrib.general;
-
- This document gives a brief introduction to &os;
- &release.current;. It includes some information on how to
- obtain &os;, a listing of various ways to contact the &os;
- Project, and pointers to some other sources of
- information.
-
+
+ This document gives a brief introduction to &os;
+ &release.current;. It includes some information on how to
+ obtain &os;, a listing of various ways to contact the &os;
+ Project, and pointers to some other sources of
+ information.
+ Introduction
- This distribution is a &release.type; of &os; &release.current;, the
- latest point along the &release.branch; branch.
+ This distribution is a &release.type; of &os;
+ &release.current;, the latest point along the &release.branch;
+ branch.About &os;&os; is an operating system based on 4.4 BSD Lite for
- AMD64 and Intel EM64T based PC hardware (&arch.amd64;),
- Intel, AMD, Cyrix or NexGen x86 based PC hardware (&arch.i386;),
- and &ultrasparc; machines (&arch.sparc64;). Versions
- for the &arm; (&arch.arm;), &mips; (&arch.mips;), and
+ AMD64 and Intel EM64T based PC hardware (&arch.amd64;), Intel,
+ AMD, Cyrix or NexGen x86 based PC hardware
+ (&arch.i386;), and &ultrasparc; machines (&arch.sparc64;).
+ Versions for the &arm; (&arch.arm;), &mips; (&arch.mips;), and
&powerpc; (&arch.powerpc;) architectures are currently under
development as well. &os; works with a wide variety of
peripherals and configurations and can be used for everything
from software development to games to Internet Service
Provision.This release of &os; contains everything you need to run
such a system, including full source code for the kernel and
all utilities in the base distribution. With the source
distribution installed, you can literally recompile the entire
system from scratch with one command, making it ideal for
students, researchers, or users who simply want to see how it
all works.A large collection of third-party ported software (the
Ports Collection) is also provided to make it
- easy to obtain and install all your favorite traditional &unix;
- utilities for &os;. Each port consists of a
- set of scripts to retrieve, configure, build, and install a
- piece of software, with a single command. Over &os.numports;
- ports, from editors to programming languages to graphical
- applications, make &os; a powerful and comprehensive operating
- environment that extends far beyond what's provided by many
- commercial versions of &unix;. Most ports are also available as
- pre-compiled packages, which can be quickly
- installed from the installation program.
+ easy to obtain and install all your favorite traditional
+ &unix; utilities for &os;. Each port consists
+ of a set of scripts to retrieve, configure, build, and install
+ a piece of software, with a single command. Over
+ &os.numports; ports, from editors to programming languages to
+ graphical applications, make &os; a powerful and comprehensive
+ operating environment that extends far beyond what's provided
+ by many commercial versions of &unix;. Most ports are also
+ available as pre-compiled packages, which can
+ be quickly installed from the installation program.
Target Audience
- This &release.type; is aimed primarily at early adopters
- and various other users who want to get involved with the
- ongoing development of &os;. While the &os; development team
- tries its best to ensure that each &release.type; works as
- advertised, &release.branch; is very much a
- work-in-progress.
+ This &release.type; is aimed
+ primarily at early adopters and various other users who want
+ to get involved with the ongoing development of &os;. While
+ the &os; development team tries its best to ensure that each
+ &release.type; works as advertised, &release.branch; is very
+ much a work-in-progress.
- The basic requirements for using this &release.type; are
- technical proficiency with &os; and an understanding of the
- ongoing development process of &os; &release.branch; (as
- discussed on the &a.current;).
+ The basic requirements for using
+ this &release.type; are technical proficiency with &os; and an
+ understanding of the ongoing development process of &os;
+ &release.branch; (as discussed on the &a.current;).
- For those more interested in doing business with &os; than
- in experimenting with new &os; technology, formal releases
- (such as &release.prev.stable;) are frequently more appropriate.
- Releases undergo a period of testing and quality assurance
- checking to ensure high reliability and dependability.
+ For those more interested in doing
+ business with &os; than in experimenting with new &os;
+ technology, formal releases (such as &release.prev.stable;)
+ are frequently more appropriate. Releases undergo a period of
+ testing and quality assurance checking to ensure high
+ reliability and dependability.
- This &release.type; is aimed primarily at early adopters
- and various other users who want to get involved with the
- ongoing development of &os;. While the &os; development team
- tries its best to ensure that each &release.type; works as
- advertised, &release.branch; is very much a
- work-in-progress.
+ This &release.type; is aimed
+ primarily at early adopters and various other users who want
+ to get involved with the ongoing development of &os;. While
+ the &os; development team tries its best to ensure that each
+ &release.type; works as advertised, &release.branch; is very
+ much a work-in-progress.
- The basic requirements for using this &release.type; are
- technical proficiency with &os; and an understanding of the
- ongoing development process of &os; &release.branch; (as
- discussed on the &a.current;).
+ The basic requirements for using
+ this &release.type; are technical proficiency with &os; and an
+ understanding of the ongoing development process of &os;
+ &release.branch; (as discussed on the &a.current;).
- For those more interested in doing business with &os; than
- in experimenting with new &os; technology, formal releases
- (such as &release.prev.stable;) are frequently more appropriate.
- Releases undergo a period of testing and quality assurance
- checking to ensure high reliability and dependability.
+ For those more interested in doing
+ business with &os; than in experimenting with new &os;
+ technology, formal releases (such as &release.prev.stable;)
+ are frequently more appropriate. Releases undergo a period of
+ testing and quality assurance checking to ensure high
+ reliability and dependability.
- This &release.type; of &os; is suitable for all users. It
- has undergone a period of testing and quality assurance
- checking to ensure the highest reliability and
- dependability.
+ This &release.type; of &os; is
+ suitable for all users. It has undergone a period of testing
+ and quality assurance checking to ensure the highest
+ reliability and dependability.Obtaining &os;&os; may be obtained in a variety of ways. This section
focuses on those ways that are primarily useful for obtaining a
complete &os; distribution, rather than updating an existing
installation.CDROM and DVD&os; -RELEASE distributions may be ordered on CDROM or DVD
from several publishers. This is frequently the most
convenient way to obtain &os; for new installations, as it
provides a convenient way to quickly reinstall the system if
necessary. Some distributions include some of the optional,
precompiled packages from the &os; Ports
Collection, or other extra material.A list of the CDROM and DVD publishers known to the
- project are listed in the Obtaining
- &os; appendix to the Handbook.
+ project are listed in the Obtaining
+ &os; appendix to the Handbook.
FTPYou can use FTP to retrieve &os; and any or all of its
- optional packages from ftp://ftp.FreeBSD.org/, which is the official
- &os; release site, or any of its
+ optional packages from ftp://ftp.FreeBSD.org/,
+ which is the official &os; release site, or any of its
mirrors.Lists of locations that mirror &os; can be found in the
FTP
Sites section of the Handbook.
Finding a close (in networking terms) mirror from which to
download the distribution is highly recommended.Additional mirror sites are always welcome. Contact
freebsd-admin@FreeBSD.org for more details on
becoming an official mirror site. You can also find useful
- information for mirror sites at the Mirroring
- &os; article.
+ information for mirror sites at the Mirroring &os;
+ article.
Mirrors generally contain the ISO images generally used to
create a CDROM of a &os; release. They usually also contain
floppy disk images (for applicable platforms), as well as the
files necessary to do an installation over the network.
Finally mirrors sites usually contain a set of packages for
the most current release.Contacting the &os; ProjectEmail and Mailing ListsFor any questions or general technical support issues,
please send mail to the &a.questions;.
- If you're tracking the &release.branch; development efforts, you
- must join the &a.current;, in order to
- keep abreast of recent developments and changes that may
- affect the way you use and maintain the system.
+ If you're tracking the &release.branch; development
+ efforts, you must join the &a.current;,
+ in order to keep abreast of recent developments and changes
+ that may affect the way you use and maintain the
+ system.
- Being a largely-volunteer effort, the &os;
- Project is always happy to have extra hands willing to help—there are already far more desired enhancements than
- there is time to implement them. To contact the developers on
- technical matters, or with offers of help, please send mail to
- the &a.hackers;.
+ Being a largely-volunteer effort, the &os; Project is
+ always happy to have extra hands willing to help—there
+ are already far more desired enhancements than there is time
+ to implement them. To contact the developers on technical
+ matters, or with offers of help, please send mail to the
+ &a.hackers;.Please note that these mailing lists can experience
significant amounts of traffic. If you
have slow or expensive mail access, or are only interested in
keeping up with major &os; events, you may find it
preferable to subscribe instead to the &a.announce;.All of the mailing lists can be freely joined by anyone
- wishing to do so. Visit the
- &os; Mailman Info Page. This will give you more
- information on joining the various lists, accessing archives,
- etc. There are a number of mailing lists targeted at special
- interest groups not mentioned here; more information can be
- obtained either from the Mailman pages or the mailing
- lists section of the &os; Web site.
+ wishing to do so. Visit the &os; Mailman Info
+ Page. This will give you more information on joining
+ the various lists, accessing archives, etc. There are
+ a number of mailing lists targeted at special interest groups
+ not mentioned here; more information can be obtained either
+ from the Mailman pages or the mailing
+ lists section of the &os; Web site.
Do not send email to the lists
asking to be subscribed. Use the Mailman interface
instead.Submitting Problem ReportsSuggestions, bug reports and contributions of code are
always valued—please do not hesitate to report any
problems you may find. Bug reports with attached fixes are of
course even more welcome.The preferred method to submit bug reports from a machine
with Internet connectivity is to use the
Bugzilla bug tracker.
Problem Reports (PRs) submitted in this way
will be filed and their progress tracked; the &os; developers
will do their best to respond to all reported bugs as soon as
possible. A list of all
active PRs is available on the &os; Web site; this
list is useful to see what potential problems other users have
encountered.Note that &man.send-pr.1; is deprecated.For more information, Writing
&os; Problem Reports, available on the &os;
Web site, has a number of helpful hints on writing and
submitting effective problem reports.Further ReadingThere are many sources of information about &os;; some are
included with this distribution, while others are available
on-line or in print versions.Release DocumentationA number of other files provide more specific information
about this &release.type; distribution. These files are
provided in various formats. Most distributions will include
both ASCII text (.TXT) and HTML
(.HTM) renditions. Some distributions
- may also include other formats such as Portable Document Format
- (.PDF).
+ may also include other formats such as Portable Document
+ Format (.PDF).
-
-
- README.TXT: This file, which
- gives some general information about &os; as well as
- some cursory notes about obtaining a
- distribution.
-
+
+
+ README.TXT: This file, which
+ gives some general information about &os; as well as some
+ cursory notes about obtaining a distribution.
+
-
- RELNOTES.TXT: The release
- notes, showing what's new and different in &os;
- &release.current; compared to the previous release (&os;
- &release.prev;).
-
+
+ RELNOTES.TXT: The release notes,
+ showing what's new and different in &os; &release.current;
+ compared to the previous release (&os;
+ &release.prev;).
+
-
- HARDWARE.TXT: The hardware
- compatibility list, showing devices with which &os; has
- been tested and is known to work.
-
+
+ HARDWARE.TXT: The hardware
+ compatibility list, showing devices with which &os; has
+ been tested and is known to work.
+
-
- ERRATA.TXT: Release errata.
- Late-breaking, post-release information can be found in
- this file, which is principally applicable to releases
- (as opposed to snapshots). It is important to consult
- this file before installing a release of &os;, as it
- contains the latest information on problems which have
- been found and fixed since the release was
- created.
-
-
-
+
+ ERRATA.TXT: Release errata.
+ Late-breaking, post-release information can be found in
+ this file, which is principally applicable to releases (as
+ opposed to snapshots). It is important to consult this
+ file before installing a release of &os;, as it contains
+ the latest information on problems which have been found
+ and fixed since the release was created.
+
+ On platforms that support &man.bsdinstall.8; (currently
- &arch.amd64;, &arch.i386;, and &arch.sparc64;), these documents are generally available via the
- Documentation menu during installation. Once the system is
- installed, you can revisit this menu by re-running the
- &man.bsdinstall.8; utility.
+ &arch.amd64;, &arch.i386;, and &arch.sparc64;), these
+ documents are generally available via the Documentation menu
+ during installation. Once the system is installed, you can
+ revisit this menu by re-running the &man.bsdinstall.8;
+ utility.
It is extremely important to read the errata for any
given release before installing it, to learn about any
late-breaking news or post-release problems.
The errata file accompanying each release (most likely right
next to this file) is already out of date by definition, but
other copies are kept updated on the Internet and should be
consulted as the current errata for this
release. These other copies of the errata are located at
- &url.base;/releases/ (as
- well as any sites which keep up-to-date mirrors of this
+ &url.base;/releases/
+ (as well as any sites which keep up-to-date mirrors of this
location).Manual Pages
- As with almost all &unix; like operating systems, &os; comes
- with a set of on-line manual pages, accessed through the
- &man.man.1; command or through the hypertext manual
- pages gateway on the &os; Web site. In general, the
- manual pages provide information on the different commands and
- APIs available to the &os; user.
+ As with almost all &unix; like operating systems, &os;
+ comes with a set of on-line manual pages, accessed through the
+ &man.man.1; command or through the hypertext
+ manual pages gateway on the &os; Web site. In
+ general, the manual pages provide information on the different
+ commands and APIs available to the &os; user.In some cases, manual pages are written to give
information on particular topics. Notable examples of such
- manual pages are &man.tuning.7; (a guide to performance tuning),
- &man.security.7; (an introduction to &os; security), and
- &man.style.9; (a style guide to kernel coding).
+ manual pages are &man.tuning.7; (a guide to performance
+ tuning), &man.security.7; (an introduction to &os; security),
+ and &man.style.9; (a style guide to kernel coding).
Books and ArticlesTwo highly-useful collections of &os;-related information,
- maintained by the &os; Project,
- are the &os; Handbook and &os; FAQ (Frequently Asked
- Questions document). On-line versions of the Handbook
- and FAQ
- are always available from the &os; Documentation
- page or its mirrors. If you install the
+ maintained by the &os; Project, are the &os; Handbook and &os;
+ FAQ (Frequently Asked Questions document). On-line versions
+ of the Handbook and FAQ are always
+ available from the &os; Documentation
+ page or its mirrors. If you install the
doc distribution set, you can use a Web
browser to read the Handbook and FAQ locally. In particular,
note that the Handbook contains a step-by-step guide to
installing &os;.A number of on-line books and articles, also maintained by
- the &os; Project, cover more-specialized, &os;-related topics.
- This material spans a wide range of topics, from effective use
- of the mailing lists, to dual-booting &os; with other
- operating systems, to guidelines for new committers. Like the
- Handbook and FAQ, these documents are available from the &os;
- Documentation Page or in the doc
- distribution set.
+ the &os; Project, cover more-specialized, &os;-related topics.
+ This material spans a wide range of topics, from effective use
+ of the mailing lists, to dual-booting &os; with other
+ operating systems, to guidelines for new committers. Like the
+ Handbook and FAQ, these documents are available from the &os;
+ Documentation Page or in the doc
+ distribution set.
A listing of other books and documents about &os; can be
- found in the bibliography
- of the &os; Handbook. Because of &os;'s strong &unix; heritage,
- many other articles and books written for &unix; systems are
- applicable as well, some of which are also listed in the
- bibliography.
+ found in the bibliography
+ of the &os; Handbook. Because of &os;'s strong &unix;
+ heritage, many other articles and books written for &unix;
+ systems are applicable as well, some of which are also listed
+ in the bibliography.
Acknowledgments&os; represents the cumulative work of many hundreds, if not
thousands, of individuals from around the world who have worked
- countless hours to bring about this &release.type;. For a
- complete list of &os; developers and contributors, please see
- Contributors
- to &os; on the &os; Web site or any of its
+ countless hours to bring about this &release.type;. For
+ a complete list of &os; developers and contributors, please see
+ Contributors
+ to &os; on the &os; Web site or any of its
mirrors.Special thanks also go to the many thousands of &os; users
and testers all over the world, without whom this &release.type;
simply would not have been possible.
Index: head/en_US.ISO8859-1/htdocs/releases/12.0R/relnotes/relnotes.xml
===================================================================
--- head/en_US.ISO8859-1/htdocs/releases/12.0R/relnotes/relnotes.xml (revision 51061)
+++ head/en_US.ISO8859-1/htdocs/releases/12.0R/relnotes/relnotes.xml (revision 51062)
@@ -1,402 +1,402 @@
%release;
%sponsor;
%vendor;
]>
&os; &release.current; Release NotesThe &os; Project$FreeBSD$
- 2016
+ 2017The &os; Documentation
Project
&tm-attrib.freebsd;
&tm-attrib.ibm;
&tm-attrib.ieee;
&tm-attrib.intel;
&tm-attrib.sparc;
&tm-attrib.general;
The release notes for &os; &release.current; contain
a summary of the changes made to the &os; base system on the
&release.branch; development line. This document lists
applicable security advisories that were issued since the last
release, as well as significant changes to the &os; kernel and
userland. Some brief remarks on upgrading are also
presented.IntroductionThis document contains the release notes for &os;
&release.current;. It describes recently added, changed, or
deleted features of &os;. It also provides some notes on
upgrading from previous versions of &os;.The &release.type; distribution to
which these release notes apply represents the latest point
along the &release.branch; development branch since
&release.branch; was created. Information regarding pre-built,
binary &release.type; distributions along this branch can be
found at &release.url;.The &release.type; distribution to
which these release notes apply represents a point along the
&release.branch; development branch between &release.prev; and
the future &release.next;. Information regarding pre-built,
binary &release.type; distributions along this branch can be
found at &release.url;.This distribution of &os;
&release.current; is a &release.type; distribution. It can be
found at &release.url; or
any of its mirrors. More information on obtaining this (or
other) &release.type; distributions of &os; can be found in the
Obtaining
&os; appendix to the &os;
Handbook.All users are encouraged to consult the release errata
before installing &os;. The errata document is updated with
late-breaking information discovered late in the
release cycle or after the release. Typically, it contains
information on known bugs, security advisories, and corrections
to documentation. An up-to-date copy of the errata for &os;
&release.current; can be found on the &os; Web site.This document describes the most user-visible new or changed
features in &os; since &release.prev;. In general, changes
described here are unique to the &release.branch; branch unless
specifically marked as &merged; features.Typical release note items document recent security
advisories issued after &release.prev;, new drivers or hardware
support, new commands or options, major bug fixes, or
contributed software upgrades. They may also list changes to
major ports/packages or release engineering practices. Clearly
the release notes cannot list every single change made to &os;
between releases; this document focuses primarily on security
advisories, user-visible changes, and major architectural
improvements.Upgrading from Previous Releases of &os;Binary upgrades between RELEASE versions
(and snapshots of the various security branches) are supported
using the &man.freebsd-update.8; utility. The binary upgrade
procedure will update unmodified userland utilities, as well as
unmodified GENERIC kernels distributed as a part of an official
&os; release. The &man.freebsd-update.8; utility requires that
the host being upgraded have Internet connectivity.Source-based upgrades (those based on recompiling the &os;
base system from source code) from previous versions are
supported, according to the instructions in
/usr/src/UPDATING.Upgrading &os; should only be attempted after backing up
all data and configuration files.Security and ErrataThis section lists the various Security Advisories and
Errata Notices since &release.prev;.Security Advisories
&security;
Errata Notices
&errata;
UserlandThis section covers changes and additions to userland
applications, contributed software, and system utilities.Userland Configuration ChangesUserland Application ChangesContributed SoftwareInstallation and Configuration Tools/etc/rc.d
Scripts/etc/periodic
ScriptsRuntime Libraries and APIABI CompatibilityKernelThis section covers changes to kernel configurations, system
tuning, and system control parameters that are not otherwise
categorized.Kernel Bug FixesKernel ConfigurationSystem Tuning and ControlsDevices and DriversThis section covers changes and additions to devices and
device drivers since &release.prev;.Device DriversStorage DriversNetwork DriversHardware SupportThis section covers general hardware support for physical
machines, hypervisors, and virtualization environments, as well
as hardware changes and updates that do not otherwise fit in
other sections of this document.Hardware SupportVirtualization SupportARM SupportStorageThis section covers changes and additions to file systems
and other storage subsystems, both local and networked.General StorageNetworked StorageZFS&man.geom.4;Boot Loader ChangesThis section covers the boot loader, boot menu, and other
boot-related changes.Boot Loader ChangesBoot Menu ChangesNetworkingThis section describes changes that affect networking in
&os;.Network ProtocolsPorts Collection and Package InfrastructureThis section covers changes to the &os; Ports
Collection, package infrastructure, and package maintenance and
installation tools.Infrastructure ChangesPackaging ChangesDocumentationThis section covers changes to the &os; Documentation
Project sources and toolchain.Documentation Source ChangesDocumentation Toolchain ChangesRelease Engineering and IntegrationThis section convers changes that are specific to the
&os; Release Engineering processes.Integration Changes