diff --git a/en_US.ISO8859-1/htdocs/releases/11.1R/errata.html b/en_US.ISO8859-1/htdocs/releases/11.1R/errata.html index cebda52a5a..7460fd159c 100644 --- a/en_US.ISO8859-1/htdocs/releases/11.1R/errata.html +++ b/en_US.ISO8859-1/htdocs/releases/11.1R/errata.html @@ -1,5 +1,5 @@ -
Copyright © 2017 The FreeBSD Documentation +
Copyright © 2017 The FreeBSD Documentation Project
FreeBSD is a registered trademark of the FreeBSD Foundation.
Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered @@ -13,7 +13,7 @@ as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the - “®” symbol.
This document lists errata items for FreeBSD 11.1-RELEASE, + “®” symbol.
This document lists errata items for FreeBSD 11.1-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 @@ -80,7 +80,16 @@ boot
Add this line to ruptime(1), rwho(1), and rwhod(8) utilities have been marked "deprecated", however this change was reversed in 12.0-CURRENT.
The other utilities mentioned in the entry in the - release notes, however, are unchanged.
This file, and other release-related documents, + release notes, however, are unchanged.
[2017-11-06] An issue with FreeBSD virtual machines with
+ vagrant was discovered that
+ affects the VirtualBox where the
+ virtual machine will not start on the initial boot invoked
+ with vagrant up
.
The issue is due to the virtual machine
+ MAC being unset, as FreeBSD does not provide
+ a default Vagrantfile
.
It has been observed, however, that a subsequent
+ invocation of vagrant up
will allow the
+ virtual machine to successfully boot, allowing access via
+ vagrant ssh
.
This file, and other release-related documents, can be downloaded from https://www.FreeBSD.org/snapshots/.
For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.
All users of FreeBSD 11.1-STABLE should