Index: releng/11.1/release/doc/en_US.ISO8859-1/errata/article.xml
===================================================================
--- releng/11.1/release/doc/en_US.ISO8859-1/errata/article.xml (revision 320504)
+++ releng/11.1/release/doc/en_US.ISO8859-1/errata/article.xml (revision 320505)
@@ -1,271 +1,158 @@
%release;
%sponsor;
%vendor;
]>
&os; &release; ErrataThe &os; Project$FreeBSD$
- 2016
+ 2017The &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
&os;.This errata document for &os; &release; will be maintained
until the release of &os; &release.next;.IntroductionThis 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.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 Issues
- An issue was discovered with Amazon® EC2™
- images which would cause the virtual machine to hang during
- boot when upgrading from previous FreeBSD versions. New
- EC2™ installations are not affected, but existing
- installations running earlier releases are advised to wait
- until the issue is resolved in an Errata Notice before
- upgrading. An Errata Notice to address this is planned
- following the release.
-
-
- &os;/&arch.i386; installed on ZFS may crash during boot
when the ZFS pool mount is attempted while booting an
unmodified GENERIC kernel.A system tunable has been added as of revision
r286584 to make the
kern.kstack_pages tunable configurable
without recompiling the kernel.To mitigate system crashes with such configurations,
chose Escape to loader prompt in the boot
menu and enter the following lines from &man.loader.8;
prompt, after an OK:set kern.kstack_pages=4
bootAdd this line to
/boot/loader.conf for the change to
persist across reboots:kern.kstack_pages=4
- A bug was diagnosed in interaction of the
- pmap_activate() function and
- TLB shootdown IPI
- handler on amd64 systems which have PCID
- features but do not implement the INVPCID
- instruction. On such machines, such as SandyBridge™
- and IvyBridge™ microarchitectures, set the loader
- tunable vm.pmap.pcid_enabled=0 during
- boot:
-
- set vm.pmap.pcid_enabled=0
-boot
-
- Add this line to
- /boot/loader.conf for the change to
- persist across reboots:
-
- To check if the system is affected, check
- &man.dmesg.8; for PCID listed in the
- "Features2", and absence of
- INVPCID in the "Structured Extended
- Features". If the PCID feature is
- not present, or INVPCID is present,
- system is not affected.
-
- vm.pmap.pcid_enabled=0
-
-
-
- The Release Notes erroneously states the
- WITH_SYSTEM_COMPILER &man.src.conf.5;
- option is enabled by default, however this was disabled
- prior to the final release build.
-
-
-
- The release announcement stated "Wireless support
- for 802.11n has been added." This was intended to
- state "Wireless support for 802.11n has been added for
- additional wireless network drivers."
-
-
-
- Some release notes pertaining to the Cavium ThunderX
- platform (the &os;/&arch.arm64; reference platform) were
- omitted:
-
-
-
- Support for the Cavium Virtualized
- NIC ethernet driver has been added.
-
-
-
- Support for the GICv3 and ITS device
- drivers has been added.
-
-
-
- Support for PCI Enhanced Allocation
- support has been added.
-
-
-
-
-
- [2016-10-20] Several recent Dell
- systems fail to find a bootable disk when the system boots
- in Legacy/BIOS/CSM mode, the boot disk is partitioned with
- GPT, and the Active flag in the
- Protective MBR is not set. To work
- around this issue, either configure the system to boot in
- UEFI mode, or choose the "GPT
- + Active" scheme.
-
-
-
- [2016-10-21] Support for sha512 and
- skein checksumming has been added to the
- ZFS filesystem. This was not mentioned
- in the release notes.
-
- Systems being upgraded from earlier &os; releases with
- ZFS will see a message in zpool
- status output noting the pool is not at the
- latest version, and some features may not be enabled.
- Additional instructions on how to update
- ZFS pools to the latest version and
- update the boot blocks for all boot drives in the pool will
- also be provided in the output.
-
- This information is also documented in
- /usr/src/UPDATING, which is included if
- the src component is selected during
- installation.
-
-
-
- [2016-10-21] The size of the GPT
- enabled ZFS boot blocks
+ The size of the GPT enabled
+ ZFS boot blocks
(/boot/gptzfsboot) has increased past
- 64K. Systems upgraded from older releases may experience
+ 82K. Systems upgraded from older releases may experience
a problem where the size of the existing
"freebsd-boot" partition is too small to hold the
new gptzfsboot.Systems where the boot partition is immediately followed
by the swap partition, such as those installed via
&man.bsdinstall.8;, can resize the swap partition slightly
using the &man.gpart.8; resize command,
so space can be reclaimed to increase the size of the
freebsd-boot partition.
- [2016-10-21] Due to a bug in earlier versions of
- &man.clang.1; that is difficult to work around in the
- upgrade process, to upgrade the system from sources via
- buildworld to -CURRENT or &release;, it is necessary to
- upgrade machines running 9.x to at least revision r286035,
- or machines running 10.x to revision r286033. Source-based
- upgrades from 10.3-RELEASE are not affected. This differs
- from the historical situation where one could generally
- upgrade from anywhere on earlier stable branches, so caution
- should be exercised.
+ Due to a bug in earlier versions of &man.clang.1; that
+ is difficult to work around in the upgrade process, to
+ upgrade the system from sources via buildworld to -CURRENT
+ or &release;, it is necessary to upgrade machines running
+ 10.x to revision r286033. Source-based upgrades from
+ 10.3-RELEASE are not affected. This differs from the
+ historical situation where one could generally upgrade from
+ anywhere on earlier stable branches, so caution should be
+ exercised.Late-Breaking NewsNo news.
Index: releng/11.1/release/doc/en_US.ISO8859-1/readme/article.xml
===================================================================
--- releng/11.1/release/doc/en_US.ISO8859-1/readme/article.xml (revision 320504)
+++ releng/11.1/release/doc/en_US.ISO8859-1/readme/article.xml (revision 320505)
@@ -1,441 +1,442 @@
%release;
]>
&os; &release.current; READMEThe &os; Project$FreeBSD$200020012002200320042005200620072008200920102011201220132014201520162017The &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.IntroductionThis 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;), NEC PC-9801/9821 series PCs and
compatibles (&arch.pc98;), 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.Target AudienceThis &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;).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.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.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.HTTPS&os; releases may be downloaded via
HTTPS from https://download.FreeBSD.org/,
which is the official &os; release site.FTPYou can use FTP to retrieve &os; and any or all of its
optional packages from ftp://ftp.FreeBSD.org/,
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.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 are 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;.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.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).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;).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.On platforms that support &man.bsdinstall.8; (currently
&arch.amd64;, &arch.i386;, &arch.pc98;, 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
+ xlink:href="&url.base;/releases/">&os; &release.current;
+ page (as well as any sites which keep up-to-date
+ mirrors of this
location).Manual PagesAs 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).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
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.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.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
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: releng/11.1/release/doc/en_US.ISO8859-1/relnotes/article.xml
===================================================================
--- releng/11.1/release/doc/en_US.ISO8859-1/relnotes/article.xml (revision 320504)
+++ releng/11.1/release/doc/en_US.ISO8859-1/relnotes/article.xml (revision 320505)
@@ -1,960 +1,942 @@
%release;
%sponsor;
%vendor;
]>
&os; &release.current; Release NotesThe &os; Project$FreeBSD$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 ChangesThe &man.inetd.8; utility is now built
without libwrap support when
WITHOUT_TCP_WRAPPERS is set in
&man.src.conf.5;.The &man.libthr.3; library and related
files are now evaluated and removed by the
delete-old-libs target when upgrading the
system if WITHOUT_LIBTHR is
set in &man.src.conf.5;.The
WITH_LLD_AS_LD build knob has been added,
which installs LLD as
/usr/bin/ld if set.LLD has been enabled by default and
installed as /usr/bin/ld on
&os;/&arch.arm64;.The
WITH_RPCBIND_WARMSTART_SUPPORT
&man.src.conf.5; knob has been added, which when enabled
allows building &man.rpcbind.8; with
warmstart support.Userland Application ChangesSupport for &man.blacklistd.8; has been added
to OpenSSH.The &man.bspatch.1; utility has been
updated with &man.capsicum.4; support.The
&man.cron.8; utility has been updated to add support for
including files within /etc/cron.d and /usr/local/etc/cron.d by
default.The
&man.syslogd.8; utility has been updated to add the
include keyword which allows specifying
a directory containing configuration files to be included in
addition to &man.syslog.conf.5;. The default
&man.syslog.conf.5; has been updated to include /etc/syslog.d and /usr/local/etc/syslog.d by
default.The &man.zfsbootcfg.8; utility has been
added, providing one-time &man.boot.config.5;-style options
for &man.zfsboot.8;.The
&man.setkey.8; utility has been modified to show the runtime
NAT-T configuration. The
-g and -t flags have
been added, which list only global and virtual policies,
respectively, when used with the -D and
-P flags.The &man.getaddrinfo.1; utility has been
added, ported from NetBSD.The &man.jail.8; utility has been
updated to allow explicitly-assigned IPv4
and IPv6 addresses to be used within
a jail.The &man.daemon.8; utility has been
updated to allow redirecting &man.stdout.4; and &man.stderr.4;
output to &man.syslog.3; or to a file.The
&man.efivar.8; utility has been added, providing an interface
to manage UEFI variables.The &man.cxgbetool.8; utility has been
added, providing command-line access to features and debugging
facilities of &man.cxgbe.4; devices.The &man.primes.6; utility now
enumerates primes beyond
3825123056546413050, up to a new limit of
2^64 - 1.Contributed Software&man.readelf.1; has been updated to
report &arch.arm; program and section header types.The
ELF Tool Chain has been updated to upstream
revision r3490.&man.groff.1; has been updated to use
the changelog date rather than file modification date in
manual pages for build reproducibility.&man.groff.1; is planned to be deprecated effective &os;
12.0-RELEASE.&man.unbound.8; has been updated to
version 1.5.10.&man.strings.1; has been updated to fix
the exit status when multiple files are provided as arguments,
and an error is encountered before the last file.&man.makewhatis.1; has been updated to produce
build-reproducible output.Subversion
has been updated to version 1.9.5.&man.file.1; has been updated to version
5.29.The &man.amd.8; utility has been updated
to version 6.2.The CLDR locales have
been updated to version 30.0.3. The unicode locales have been
updated to version 9.0.0.&man.xz.1; has been updated to version
5.2.3.&man.tcpdump.1; has been updated to
version 4.9.0.&man.zlib.3; has been updated to version
1.2.11.openresolv
has been updated to version 3.9.0.The NetBSD test suite has been updated
to the 01.11.2017_23.20 snapshot.libucl has been
updated to version 20170219.&man.libarchive.3; has been updated to
version 3.3.1.&man.dma.8; has been updated to the
2017-02-10 snapshot.&man.ntpd.8; has been updated to version
4.2.8p10.ACPICA has
been updated to version 20170303.Timezone data files have been updated to
version 2017b.&man.mandoc.1; has been updated to
version 1.14.Clang has
been updated to version 4.0.0.LLVM has
been updated to version 4.0.0.LLD has
been updated to version 4.0.0.LLDB has
been updated to version 4.0.0.compiler-rt
has been updated to version 4.0.0.libc++ has
been updated to version 4.0.0.&man.tcsh.1; has been updated to version
6.20.00.&man.blacklistd.8; has been updated to the
20170503 snapshot.&man.blacklistd.8; support for
OpenSSH has been refined to adjust
notification points to catch all authentication failures
rather than only those caused by invalid login
usernames.&man.byacc.1; has been updated to
version 20170201.bmake has
been updated to version 20170510.Installation and Configuration ToolsThe installer, &man.bsdinstall.8;, has
been updated to include support for hidden wireless networks
when configuring the &man.wlan.4; interface.The
default EFI partition created by
&man.bsdinstall.8; has been increased from 800KB to
200MB./etc/rc.d
ScriptsThe jail_confwarn
&man.rc.conf.5; entry has been added, which suppresses
warnings about obsolete per-&man.jail.8;
configurations./etc/periodic
ScriptsThe default &man.periodic.conf.5; has
been updated to include the
anticongestion_sleeptime option,
consolidating random sleeps in &man.periodic.8; scripts and
replacing the daily_ntpd_avoid_congestion
option. The default value is 3600 seconds.The 410.status-mfi
&man.periodic.8; script has been added to monitor the status
of &man.mfi.4; volumes.Runtime Libraries and APIThe libmd library has
been updated to introduce functions that operate on &man.fd.4;
instead of filename.The &man.kvm.close.3; function has been
updated to return the accumulated error from previous
&man.close.2; calls.The C standard library has been updated
to make use of &man.reallocarray.3; for bounds
checking.The clock_nanosleep()
system call has been added. The
nanosleep() system call is now a wrapper
around clock_nanosleep().The system libraries have been updated
to make use of &man.reallocarray.3; for bounds
checking.ABI CompatibilityThe type max_align_t
is now defined for C11 compliance.The
sem_clockwait_np() library function has
been added, which allows the caller to specify the reference
clock and choose between absolute and relative mode.The clangnullability qualifiers have been added to
the C library headers.Uses of the GNU
__nonnull__ attribute have been replaced
with the more benign Clang
nullability attributes.Userland Debugging&man.ptrace.2; now supports events for
&man.vfork.2;, permitting reliable debugging across
&man.vfork.2; invocations.Process core dumps now include the
process ID (PID) and command line
arguments.KernelThis section covers changes to kernel configurations, system
tuning, and system control parameters that are not otherwise
categorized.General Kernel ChangesThe &man.getdtablesize.2; system call is
now permitted in capability mode.The kern.proc.nfds
&man.sysctl.8; is now permitted in capability mode.The
sys/conf/newvers.sh script has been
updated with an option to exclude build-specific metadata from
the kernel for build reproducibility.Kernel Bug FixesThe &man.ipf.4; packet filter has been
updated to prevent keep state from
incorrectly implying keep frags, matching
the behavior documented in &man.ipf.5;.Kernel ConfigurationThe
WITH_REPRODUCIBLE_BUILD &man.src.conf.5;
knob has been added, which when set, excludes build-specific
metadata from the kernel, for build reproducibility.Support for NAT-T is now
enabled by default. The IPSEC_NAT_T kernel
configuration option has been removed.The
IPSEC_FILTERTUNNEL kernel option has been
removed, which was deprecated by the
net.inet.ipsec.filtertunnel sysctl.The EARLY_AP_STARTUP
option has been enabled by default on &arch.amd64; and
&arch.i386; architectures, which when enabled releases
Application Processors (APs) earlier in the
kernel startup process.Kernel Modules&man.cloudabi.4; has been updated to
allow running 32-bit binaries within 64-bit userland
environments when the kernel configuration file has the
COMPAT_CLOUDABI32 option present.The
ipsec and tcpmd5 kernel
modules have been added.Following the addition of the tcpmd5
module, it is now necessary to have a security association
(SA) entry for both inbound and outbound
directions.The
&man.ipfw.4; packet filter has been updated to add support for
named dynamic states.The
ipfw_nptv6 kernel module has been added,
implementing Network Prefix Translation for
IPv6 as defined in RFC
6296.The
ipfw_nat64 kernel module has been added,
implementing stateless and stateful
NAT64.The
&man.cfumass.4; device has been added, providing a storage
frontend to USB
OTG-capable hardware.The
ipfw_pmod kernel module has been added,
designed for modifying packets of any protocol.At present, only TCP
MSS modification is implemented.System Tuning and ControlsThe
vfs.root_mount_always_wait tunable has been
added, which forces the kernel to wait for root mount holds
even if the root device is already present.When the system real time clock
(RTC) is adjusted, such as by
clock_settime(), sleeping threads are now
awakened and absolute sleep times are reevaluated based on the
new value of the RTC.Devices and DriversThis section covers changes and additions to devices and
device drivers since &release.prev;.Device DriversThe &man.jedec.ts.4; driver has been
added, providing support for thermal sensors on memory
modules. The driver currently supports chips that are fully
compliant with the JEDEC
JC 42.4 specification.The &man.chromebook.platform.4; driver
has been added, providing support for various Chromebook
models.The &man.bytgpio.4; driver has been
added, providing support for Intel® Bay Trail™
SoC GPIO controllers./dev/kmem no longer
supports access via mmap(). Consumers
wishing to use /dev/kmem must use
read() and
write().&man.devctl.8; now supports a "clear
driver" command as a complement to "set
driver".Storage DriversThe &man.mpr.4; driver has been updated
to support tri-mode
(SAS/SATA/PCIe)
Broadcom® storage adapters.Network DriversThe &man.cxgbe.4; driver has been updated
to provide support for Virtual Function devices
(VFs) on Chelsio T4 and T5 adapters.TCP connections using the TCP Offload
Engine (TOE) on Chelsio T4+ adapters can
now perform zero-copy sends via
aio_write().The &man.cxgbev.4; driver has been added,
providing support for Virtual Function devices
(VFs) on Chelsio T4 and T5 adapters.The &man.bnxt.4; driver has been added,
providing support for Broadcom® NetXtreme-C™ and
NetXtreme-E™ devices.The &man.cxgbe.4; driver now supports
devices using T6-based adapters which support 10, 25, 40, and
100 Gbps.The &man.cxgbe.4; driver has been updated
to provide support for Virtual Function devices
(VFs) on Chelsio T6 adapters.The &man.cxgbev.4; driver has been updated
to provide support for Virtual Function devices
(VFs) on Chelsio T6 adapters.The &man.miibus.4; driver has been updated
to support Microchip/Micrel KSZ9031 Gigabit ethernet
cards.The &man.alc.4; driver has been updated
to provide support for Atheros® Killer E2400™
Gigabit ethernet cards.The
&man.alc.4; driver has been updated to provide support for
Atheros® Killer E2500™ Gigabit ethernet
cards.The &man.etherswitch.4; driver has been
updated to support RTL8366RB and RTL8366SR cards.The
&man.if.ipsec.4; virtual tunneling interface has been added,
implementing route-based VPNs protected
with Encapsulating Security Payload
(ESP).The &man.qlnxe.4; driver has been added,
providing support for Cavium® Qlogic™ 45000 Series
adapters.The &man.qlxgbe.4; firmware has been
updated to version 5.4.64.The &man.ixl.4; driver has been updated
to version 1.7.12-k.The &man.cxgbe.4; driver has been updated
to firmware version 1.16.45.0 for T4, T5, and T6 cards.The &man.qlnxe.4; driver has been
updated to support QLE41XXX hardware.The &man.qlnxe.4; driver firmware has
been updated to version 8.30.0.0.Hardware 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 SupportThe &man.atkbdc.4; driver has been
updated to provide support for Elantech® trackpads. To
enable hardware support, add
hw.psm.elantech_support=1 to
&man.loader.conf.5;.Virtualization SupportPCI passthrough with
&man.bhyve.4; supports more dynamic configurations permitting
devices to be marked for passthrough or host use at
runtime.PCI passthrough with
&man.bhyve.4; resets functions via FLR when
a virtual machine is started and stopped.PCI passthrough support has
been enabled on &os; virtual machines running on
Microsoft® Hyper-V™.The
&man.hv.netvsc.4; driver SR-IOV
implementation has been updated to support Virtual Function
(VF) devices, such as the Mellanox®
Connect-X3™ network card.Support
for Microsoft® Hyper-V™ Generation 2 virtual
machines has been added.Support
for synthetic keyboards has been added for virtual machines
running on Microsoft® Hyper-V™.The &os; virtual machines provided on
Amazon® EC2™ now enable IPv6 by
default.ARM SupportSupport for the Allwinner A13 board has
been added.StorageThis section covers changes and additions to file systems
and other storage subsystems, both local and networked.
-
- General Storage
-
-
-
-
Networked StorageThe NFS client now
properly handles NFS4ERR_BAD_SESSION errors
received from an NFS server. Additionally,
the kernel RPC client has been updated to
prevent creating new TCP connections when
ERESTART is received from
&man.sosend.9;.The NFS client now
supports the Amazon® Elastic File System™
(EFS).ZFSThe
vfs.zfs.debug_flags &man.sysctl.8; has been
deprecated in favor of
vfs.zfs.debugflags. Additionally,
vfs.zfs.debugflags can now be configured in
&man.loader.conf.5;, whereas
vfs.zfs.debug_flags could not.
-
-
- geom(4)
-
-
- Boot Loader ChangesThis section covers the boot loader, boot menu, and other
boot-related changes.Boot Loader ChangesThe
UEFI boot loader has been updated for build
reproducibility.The
EFI loader has been updated to support
TFTPFS, providing netboot support without
requiring an NFS server.
-
-
-
- Boot Menu Changes
-
- NetworkingThis section describes changes that affect networking in
&os;.General Network ChangesThe
network stack has been updated to include
ip6_tryforward(), providing performance
benefits as result of a reduced number of checks.The network stack has been modified to fix
incorrect or invalid IP addresses if
multiple threads emit a UDP
log_in_vain message concurrently.The TCP stack has
been changed to use the estimated RTT
instead of timestamps for receive buffer auto resizing.Network ProtocolsSupport for GARP
(gratuitous ARP) retransmit has been added.
A new &man.sysctl.8;,
net.link.ether.inet.garp_rexmit_count, has
been added, which sets the maximum number of retransmissions
when set to a non-zero value.Support for the
UDP_ENCAP_ESPINUDP_NON_IKE encapsulation
type has been removed.Ports 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
Index: releng/11.1/release/doc/share/xml/release.ent
===================================================================
--- releng/11.1/release/doc/share/xml/release.ent (revision 320504)
+++ releng/11.1/release/doc/share/xml/release.ent (revision 320505)
@@ -1,82 +1,82 @@
-
+
-
+
-
+
-
+
-
+
-
-
+
+
]]>
]]>
]]>