Date: Fri, 14 Jun 2019 00:30:52 +0000 (UTC) From: Glen Barber <gjb@FreeBSD.org> To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-releng@freebsd.org Subject: svn commit: r349028 - in releng/11.3/release/doc: en_US.ISO8859-1/errata en_US.ISO8859-1/hardware en_US.ISO8859-1/installation en_US.ISO8859-1/readme share/xml Message-ID: <201906140030.x5E0UquG059342@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: gjb Date: Fri Jun 14 00:30:52 2019 New Revision: 349028 URL: https://svnweb.freebsd.org/changeset/base/349028 Log: Post-branch updates to release-related documentation: - Bump copyright years. - Note in parenthesis 11.3 may be the last 11.x release. - Prune stale errata items from 11.2-RELEASE. - Fix mailing list in the readme page. - Bump version numbers accordingly. This has no effect or impact on the in-progress 11.3-RC1 build. Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Modified: releng/11.3/release/doc/en_US.ISO8859-1/errata/article.xml releng/11.3/release/doc/en_US.ISO8859-1/hardware/article.xml releng/11.3/release/doc/en_US.ISO8859-1/installation/article.xml releng/11.3/release/doc/en_US.ISO8859-1/readme/article.xml releng/11.3/release/doc/share/xml/release.ent Modified: releng/11.3/release/doc/en_US.ISO8859-1/errata/article.xml ============================================================================== --- releng/11.3/release/doc/en_US.ISO8859-1/errata/article.xml Fri Jun 14 00:09:12 2019 (r349027) +++ releng/11.3/release/doc/en_US.ISO8859-1/errata/article.xml Fri Jun 14 00:30:52 2019 (r349028) @@ -24,7 +24,7 @@ <pubdate>$FreeBSD$</pubdate> <copyright> - <year>2018</year> + <year>2019</year> <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder> @@ -49,7 +49,8 @@ &os;.</para> <para>This errata document for &os; &release; will be maintained - until the release of &os; &release.next;.</para> + until the release of &os; &release.next; (if + applicable).</para> </abstract> </info> @@ -96,157 +97,7 @@ <itemizedlist> <listitem> - <para>&os;/&arch.i386; installed on ZFS may crash during boot - when the ZFS pool mount is attempted while booting an - unmodified <literal>GENERIC</literal> kernel.</para> - - <para>A system tunable has been added as of revision - <literal>r286584</literal> to make the - <literal>kern.kstack_pages</literal> tunable configurable - without recompiling the kernel.</para> - - <para>To mitigate system crashes with such configurations, - choose <literal>Escape to loader prompt</literal> in the - boot menu and enter the following lines from &man.loader.8; - prompt, after an <literal>OK</literal>:</para> - - <screen>set kern.kstack_pages=4 -boot</screen> - - <para>Add this line to - <filename>/boot/loader.conf</filename> for the change to - persist across reboots:</para> - - <programlisting>kern.kstack_pages=4</programlisting> - </listitem> - - <listitem> - <para>[2017-07-25] &os;/&arch.arm64; currently lacks - <acronym>EFI</acronym> real-time clock - (<acronym>RTC</acronym>) support, which may cause the system - to boot with the wrong time set.</para> - - <para>As a workaround, either enable &man.ntpdate.8; or - include <literal>ntpd_sync_on_start="YES"</literal> in - &man.rc.conf.5;.</para> - </listitem> - - <listitem> - <para>[2017-07-25] A late issue was discovered with - &os;/&arch.arm64; and "root on - <acronym>ZFS</acronym>" installations where the root - <acronym>ZFS</acronym> pool would fail to be located.</para> - - <para>There currently is no workaround.</para> - </listitem> - - <listitem> - <para>[2017-11-06] An issue with &os; virtual machines with - <application>vagrant</application> was discovered that - affects the <application>VirtualBox</application> where the - virtual machine will not start on the initial boot invoked - with <literal>vagrant up</literal>.</para> - - <para>The issue is due to the virtual machine - <acronym>MAC</acronym> being unset, as &os; does not provide - a default <filename>Vagrantfile</filename>.</para> - - <para>It has been observed, however, that a subsequent - invocation of <literal>vagrant up</literal> will allow the - virtual machine to successfully boot, allowing access via - <literal>vagrant ssh</literal>.</para> - </listitem> - - <listitem> - <para>[2018-06-21] An issue had been discovered late in the - release cycle where removing <acronym>ZFS</acronym> vdevs - from a pool under certain conditions would cause a system - crash when &man.zfsd.8; is enabled in - &man.rc.conf.5;.</para> - - <para>At present, it is believed to be limited to removal of - a <literal>mirror</literal> vdev from a pool consisting of - multiple <literal>mirror</literal> vdevs.</para> - - <para>See <acronym>PR</acronym> <link - xlink:href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228750">228750</link>; - for more information and updates as the issue is - investigated.</para> - </listitem> - - <listitem> - <para>[2018-06-26] An issue had been discovered late in the - release cycle where a system crash could occur after - installing <filename - role="package">emulators/virtualbox-ose-kmod</filename> - from upstream package mirrors via &man.pkg.8;.</para> - - <para>Building <filename - role="package">emulators/virtualbox-ose-kmod</filename> - from the &man.ports.7; collection has been observed to work - around the crash.</para> - - <para>See <acronym>PR</acronym> <link - xlink:href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535">228535</link>; - for more information.</para> - </listitem> - - <listitem> - <para>[2018-06-26] It was discovered after the <filename - class="directory">releng/11.2</filename> branch was tagged - for &os; 11.2-RELEASE that a few device drivers were - missing from the <link - xlink:href="https://www.FreeBSD.org/releases/11.2R/hardware.html">hardware</link>; - page. The missing drivers, &man.alc.4;, &man.cxgbev.4;, - &man.liquidio.4;, and &man.mos.4; were added to the - 11-STABLE <link - xlink:href="https://www.FreeBSD.org/relnotes/11-STABLE/hardware/support.html">hardware - page</link>.</para> - </listitem> - - <listitem> - <para>[2018-06-26] The <acronym>URL</acronym> to the - instructions for source-based upgrades in - <filename>UPDATING</filename> incorrectly points to a page - that no longer exists. The correct URL is <link - xlink:href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html" />.</para> - </listitem> - - <listitem> - <para>[2018-06-27] The announcement email for &os; 11.2 - incorrectly states the <literal>ocs_fw(4)</literal> driver - had been added; this should have stated - &man.ocs.fc.4;.</para> - </listitem> - - <listitem> - <para>[2018-06-28] An issue had been reported after the - release of &os; 11.2 with <filename - role="package">x11/nvidia-driver</filename> installed from - the upstream package mirrors via &man.pkg.8;.</para> - - <para>Building <filename - role="package">x11/nvidia-driver</filename> from - the &man.ports.7; collection has been reported to resolve - the issue.</para> - - <para>See <acronym>PR</acronym> <link - xlink:href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536">228536</link>; - for more information.</para> - </listitem> - - <listitem> - <para>[2018-10-18] A &os; system with a custom kernel - configuration excluding <acronym>NFS</acronym> on 10.x did - not explicitly require the <literal>krpc</literal> option to - be included when booting via <acronym>ZFS</acronym>-on-root - and, for example, setting - <literal>MODULES_OVERRIDE="zfs opensolaris"</literal> in the - kernel configuration.</para> - - <para>In 11.x, however, <literal>krpc</literal> is explicitly - required if the kernel configuration excludes - <literal>NFS</literal>.</para> + <para>No open issues at this time.</para> </listitem> </itemizedlist> </sect1> Modified: releng/11.3/release/doc/en_US.ISO8859-1/hardware/article.xml ============================================================================== --- releng/11.3/release/doc/en_US.ISO8859-1/hardware/article.xml Fri Jun 14 00:09:12 2019 (r349027) +++ releng/11.3/release/doc/en_US.ISO8859-1/hardware/article.xml Fri Jun 14 00:30:52 2019 (r349028) @@ -40,6 +40,7 @@ <year>2016</year> <year>2017</year> <year>2018</year> + <year>2019</year> <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder> </copyright> Modified: releng/11.3/release/doc/en_US.ISO8859-1/installation/article.xml ============================================================================== --- releng/11.3/release/doc/en_US.ISO8859-1/installation/article.xml Fri Jun 14 00:09:12 2019 (r349027) +++ releng/11.3/release/doc/en_US.ISO8859-1/installation/article.xml Fri Jun 14 00:30:52 2019 (r349028) @@ -22,7 +22,7 @@ <pubdate>$FreeBSD$</pubdate> <copyright> - <year>2018</year> + <year>2019</year> <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder> </copyright> Modified: releng/11.3/release/doc/en_US.ISO8859-1/readme/article.xml ============================================================================== --- releng/11.3/release/doc/en_US.ISO8859-1/readme/article.xml Fri Jun 14 00:09:12 2019 (r349027) +++ releng/11.3/release/doc/en_US.ISO8859-1/readme/article.xml Fri Jun 14 00:30:52 2019 (r349028) @@ -44,6 +44,7 @@ <year>2016</year> <year>2017</year> <year>2018</year> + <year>2019</year> <holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder> </copyright> @@ -231,7 +232,7 @@ please send mail to the &a.questions;.</para> <para>If you are tracking the &release.branch; development - efforts, you <emphasis>must</emphasis> join the &a.current;, + efforts, you <emphasis>must</emphasis> join the &a.stable;, in order to keep abreast of recent developments and changes that may affect the way you use and maintain the system.</para> Modified: releng/11.3/release/doc/share/xml/release.ent ============================================================================== --- releng/11.3/release/doc/share/xml/release.ent Fri Jun 14 00:09:12 2019 (r349027) +++ releng/11.3/release/doc/share/xml/release.ent Fri Jun 14 00:30:52 2019 (r349028) @@ -6,7 +6,7 @@ <!-- Version of the OS we're describing. This needs to be updated with each new release. --> -<!ENTITY release.current "11.2-STABLE"> +<!ENTITY release.current "11.3-RELEASE"> <!-- The previous version used for comparison in the "What's New" section. For -CURRENT, we might point back to the last @@ -16,16 +16,16 @@ <!-- The previous stable release, useful for pointing user's at the release they SHOULD be running if they don't want the bleeding edge. --> -<!ENTITY release.prev.stable "10.4-RELEASE"> +<!ENTITY release.prev.stable "11.2-RELEASE"> <!-- The next version to be released, usually used for snapshots. --> -<!ENTITY release.next "11.3-RELEASE"> +<!ENTITY release.next "11.4-RELEASE"> <!-- The name of this branch. --> -<!ENTITY release.branch "11.2-STABLE"> +<!ENTITY release.branch "11.3-STABLE"> <!-- The URL for obtaining this version of FreeBSD. --> -<!ENTITY release.url "https://www.FreeBSD.org/snapshots/">; +<!ENTITY release.url "https://www.FreeBSD.org/releases/">; <!-- The URL for Security Advisories and Errata Notices. --> <!ENTITY security.url "https://www.FreeBSD.org/security/advisories">; @@ -37,10 +37,10 @@ or "release" --> <!-- WARNING: Do not forget to also change the release type in doc.relnotes.mk when updating this --> -<!ENTITY release.type "snapshot"> +<!ENTITY release.type "release"> <!ENTITY % release.type.current "IGNORE"> -<!ENTITY % release.type.snapshot "INCLUDE"> -<!ENTITY % release.type.release "IGNORE"> +<!ENTITY % release.type.snapshot "IGNORE"> +<!ENTITY % release.type.release "INCLUDE"> <![%release.type.current;[ <!ENTITY release '&release.current;'>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201906140030.x5E0UquG059342>