MFR50: Synchronize the content of the errata file with RELENG_5_0.

	article.sgml	1.9.2.4

At this point, the errata file on HEAD should contain the same content
as for RELENG_5_0, but be compatible with the SGML entities and other
infrastructure on HEAD.  We can now add content here and it will
appear as post-release errata.

1 files changed, 62 insertions, 4 deletions

diff --git a/release/doc/en_US.ISO8859-1/errata/article.sgml b/release/doc/en_US.ISO8859-1/errata/article.sgml
index 8d17106..2b953ab 100644
--- a/release/doc/en_US.ISO8859-1/errata/article.sgml
+++ b/release/doc/en_US.ISO8859-1/errata/article.sgml
@@ -88,11 +88,69 @@
 
   <sect1 id="security">
     <title>Security Advisories</title>
-    <para></para>
+
+    <para>No active security advisories.</para>
+
   </sect1>
 
-  <sect1 id="update">
-    <title>System Update Information</title>
-    <para></para>
+  <sect1 id="late-news">
+    <title>Late-Breaking News</title>
+
+    <para>The &man.geom.4;-based disk partitioning code in the kernel
+      will not allow an open partition to be overwritten.  This
+      usually prevents the use of <command>disklabel -B</command> to
+      update the boot blocks on a disk because the
+      <literal>a</literal> partition overlaps the space where the boot
+      blocks are stored.  A suggested workaround is to boot from an
+      alternate disk, a CDROM, or a fixit floppy.</para>
+
+    <para>When using disk media with sector sizes larger than 512
+      bytes (for instance, &man.gbde.4; encrypted disks), the
+      &man.dump.8; program fails to respect the larger sector size and
+      cannot dump the partition.  One possible workaround is to copy
+      the entire file system in raw format and dump the copy.  It is,
+      for instance, possible to dump a file system stored in a regular
+      file:</para>
+
+      <screen>&prompt.root; <userinput>dd if=/dev/ad0s1d.bde of=/junk/ad0.dd bs=1m</userinput>
+&prompt.root; <userinput>dump 0f - /junk/ad0.dd | ...</userinput></screen>
+
+    <para>A simpler workaround is to use &man.tar.1; or &man.cpio.1;
+      to make backup copies.</para>
+
+    <para>Hangs have been reported during &os; 5.0 snapshot
+      installations when installing to &man.mly.4;-supported RAID
+      arrays, in hardware configurations that appear to work fine
+      under &os; 4.7-RELEASE.</para>
+
+    <para>NETNCP and nwfs appear to be as-yet unadapted for KSE, and
+      hence not working.</para>
+
+    <para>During installation, the &man.iir.4; controller appears to
+      probe correctly, but finds no disk devices.</para>
+
+    <para>&man.truss.1; appears to contain a race condition during the
+      start-up of debugging, which can result in &man.truss.1; failing
+      to attach to the process before it exists.  The symptom is that
+      &man.truss.1; reports that it cannot open the &man.procfs.5;
+      node supporting the process being debugged.  A bug also appears
+      to exist wherein &man.truss.1; will hang if &man.execve.2;
+      returns <literal>ENOENT</literal> A further race appears to
+      exist in which &man.truss.1; will return <errorname>PIOCWAIT:
+      Input/output error</errorname> occasionally on startup.  The fix
+      for this sufficiently changes process execution handling that it
+      has been deferred until after 5.0.</para>
+
+    <para>Some bugs have been reported in &man.sysinstall.8; disk
+      partitioning.  One observed problem on the i386 is that
+      &man.sysinstall.8; cannot recalculate the free space left on a
+      disk after changing the type of an FDISK-type partition.</para>
+
+    <para>In some case, documentation (such as the FAQ or Handbook)
+      has not been updated to take into account &os; &release.current;
+      features.  Examples of areas where documentation is still
+      needed include &man.gbde.8; and the new <quote>fast
+      IPsec</quote> implementation.</para>
+
   </sect1>
 </article>