diff --git a/en/releases/5.0R/todo.sgml b/en/releases/5.0R/todo.sgml
index 26a93b5430..3f6975b185 100644
--- a/en/releases/5.0R/todo.sgml
+++ b/en/releases/5.0R/todo.sgml
@@ -1,212 +1,201 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
 <!ENTITY base CDATA "../..">
 <!ENTITY email 'freebsd-qa'>
-<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.128 2003/01/07 17:16:33 scottl Exp $">
+<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.129 2003/01/10 00:25:16 scottl Exp $">
 <!ENTITY title "FreeBSD 5.0 Open Issues">
 <!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
 <!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
 ]>
 
 <html>
 &header;
 
 <h1>Open Issues</h1>
 
 <p>This is a list of open issues that need to be resolved for FreeBSD
   5.0.  If you have any updates for this list, please e-mail
   re@FreeBSD.org.</p>
 
 
 <h3>Must Resolve Issues for 5.0-RC3</h3>
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
   <tr>
   <td>Many reported problems with disklabel -e</td>
   <td>--</td>
   <td>&a.phk;, &a.jhb;</td>
   <td>Changes in the disk label format have resulted in substantial
     numbers of bug reports; these must be resolved by RC1.  The problem
     involving a cache coherency issue relating to partition resizes
     has now been resolved.  Problems relating to disklabel -r and
     the change appear to continue.</td>
   </tr>
 
-  <tr>
-  <td>Audit of devfs device permissions</td>
-  <td>In progress</td>
-  <td>&a.kris;,&a.rwatson;</td>
-  <td>With the move to devfs, the permissions specified in kernel device
-    creation lines using make_dev() are now used as the default permissions
-    for /dev entries.  Some of these entries are more lax than is desired,
-    or than the MAKEDEV defaults in 4.x.  These need to be carefully
-    reviewed and fixed.</td>
-  </tr>
-
   <tr>
   <td>mly driver hangs during install</td>
   <td>--</td>
   <td>&a.scottl;, &a.jeff;</td>
   <td>Hangs have been reported during the 5.0 snapshot install when
     installing to mly supported RAID arrays.  The same array appears
     to work fine with 4.7-RELEASE.  The card in question is a Mylex
     AcceleRAID 170, 32 Mb RAM, Firmware revision 7.01-00.  This is
     believed to be the same problem as described in PR 45383.</td>
   </tr>
 
   <tr>
     <td>Investigate sysinstall problem reports</td>
     <td>--</td>
     <td>--</td>
     <td>There are reported problems with sysinstall on i386 not working when
       the user specifies something other that slice 1 during labeling.  More
       details are forthcoming.</td>
   </tr>
 
 </table>
 
 <h3>Must Resolve Issues for 5.0-RELEASE</h3>
 
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
   <tr>
   <td>TrustedBSD MAC Framework documentation</td>
     <td>FreeBSD documentation CVS HEAD: in progress</td>
     <td>&a.chris;</td><td>User and developer documentation of
       the new extensible security framework.  Includes guides for live
       deployment, development of policy modules, and implementation
       information.</td>
   </tr>
 
 </table>
 
 <h3>Desired Features for 5.0-RELEASE</h3>
 
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
   <tr>
   <td>a.out toolchain port</td>
   <td>--</td>
   <td>--</td>
   <td>A.out support in the base system was reduced; the removed build
     chain components should be made into a port.</td>
   </tr>
 
   <tr>
   <td>NETNCP and nwfs broken</td>
   <td>--</td>
   <td>--</td>
   <td>NETNCP and nwfs appear to be as-yet unadapted for KSE, and hence
     not working.  The build needs fixing (probably not all that hard)
     and then it needs to be tested (harder: few people appear to have
     Netware servers).</td>
   </tr>
 
   <tr>
   <td>No docs for FAST IPSEC</td>
   <td>--</td>
   <td>--</td>
   <td>The new "fast ipsec" implementation has insufficient documentation
     (man pages, release notes), and this would be highly desirable to
     have before 5.0-RELEASE.</td>
   </tr>
 
   <tr>
   <td>Race conditions in truss</td>
   <td>Errata candidate</td>
   <td>&a.robert;</td>
   <td>Truss appears to contain a race condition during the start-up of
     debugging, which can result in truss failing to attach to the process
     before it exits.  The symptom is that truss reports that it cannot
     open the procfs node supporting the process being debugged.  A bug
     also appears to exist where in truss will hang if execve() returns
     ENOENT.  A further race appears to exist in which truss will return
     "PIOCWAIT: Input/output error" occasionally on startup.  The fix
     for this sufficiently changes process execution handling that we
     will defer the fix to post-5.0 and consider this errata.</td>
   </tr>
 
   <tr>
   <td>Documentation rottage: S/Key</td>
   <td>--</td>
   <td>--</td>
   <td>We now use OPIE instead of S/Key.  The handbook doesn't know
     that yet.</td>
   </tr>
 
   <tr>
   <td>Documentation wanted: gdbe</td>
   <td>--</td>
   <td>&a.chris;</td>
   <td>5.0 includes GDBE, supporting encryption of swap and storage.
     It would be nice if that was documented in the handbook.</td>
   </tr>
 
   <tr>
   <td>iir driver fails to probe disks</td>
   <td>--</td>
   <td>--</td>
   <td>During the install, the iir controller appears to correctly
     probe, but finds no disk devices.  The card in question is an
     Intel srcu32 RAID controller with 32Mb RAM, Firmware revision
     2.33.01.  Direct access to real iir hardware for SCSI
     developers would be very helpful in resolving this problem.</td>
   </tr>
 
 </table>
 
 <h3>Areas requiring immediate testing due to 5.0 changes</h3>
 
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
   <tr>
   <td>if_ie, if_le, if_wl network device drivers</td>
   <td>--</td>
   <td>&a.sam;</td>
   <td>Changes made to the ethernet driver interfaces required sweeping
     API changes across all ethernet device drivers.  While these
     changes are largely mechanical, they were not tested for three less
     frequently used interface drivers: if_ie, if_le, and if_wl.  They
     each require testing (and probably fixing) prior to 5.0-RELEASE.
     If you have access to devices that use these drivers, please perform
     local testing and provide feedback to Sam Leffler.</td>
   </tr>
 
   <tr>
     <td>No console (term) if smbus is enable in the kernel</td>
     <td>--</td>
     <td>--</td>
     <td>There are reports that kernels build with smbus, viapm, and smb
       devices may not properly probe and support the system console
       following boot.</td>
   </tr>
 
 </table>
 
 <h3>Known Issues with 5.0R-RC1 / i386</h3>
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
   <tr>
     <td>KDE does not install from ISO</td>
     <td>In Progress</td>
     <td>&a.murray;</td>
     <td>The kde meta-package is not included on the ISO, but many of
       the component kde packages are, so sysinstall gets confused and
       installs kde-icontheme instead (more correct behavior would be to
       fall back to kdebase if kde package is not present).</td>
   </tr>
 
 </table>
     &footer;
 
   </body>
 </html>

Issue	Status	Responsible	Description
Many reported problems with disklabel -e	--	&a.phk;, &a.jhb;	Changes in the disk label format have resulted in substantial numbers of bug reports; these must be resolved by RC1. The problem involving a cache coherency issue relating to partition resizes has now been resolved. Problems relating to disklabel -r and the change appear to continue.
Audit of devfs device permissions	In progress	&a.kris;,&a.rwatson;	With the move to devfs, the permissions specified in kernel device - creation lines using make_dev() are now used as the default permissions - for /dev entries. Some of these entries are more lax than is desired, - or than the MAKEDEV defaults in 4.x. These need to be carefully - reviewed and fixed.
mly driver hangs during install	--	&a.scottl;, &a.jeff;	Hangs have been reported during the 5.0 snapshot install when installing to mly supported RAID arrays. The same array appears to work fine with 4.7-RELEASE. The card in question is a Mylex AcceleRAID 170, 32 Mb RAM, Firmware revision 7.01-00. This is believed to be the same problem as described in PR 45383.
Investigate sysinstall problem reports	--	--	There are reported problems with sysinstall on i386 not working when the user specifies something other that slice 1 during labeling. More details are forthcoming.
Issue	Status	Responsible	Description
a.out toolchain port	--	--	A.out support in the base system was reduced; the removed build chain components should be made into a port.
NETNCP and nwfs broken	--	--	NETNCP and nwfs appear to be as-yet unadapted for KSE, and hence not working. The build needs fixing (probably not all that hard) and then it needs to be tested (harder: few people appear to have Netware servers).
No docs for FAST IPSEC	--	--	The new "fast ipsec" implementation has insufficient documentation (man pages, release notes), and this would be highly desirable to have before 5.0-RELEASE.
Race conditions in truss	Errata candidate	&a.robert;	Truss appears to contain a race condition during the start-up of debugging, which can result in truss failing to attach to the process before it exits. The symptom is that truss reports that it cannot open the procfs node supporting the process being debugged. A bug also appears to exist where in truss will hang if execve() returns ENOENT. A further race appears to exist in which truss will return "PIOCWAIT: Input/output error" occasionally on startup. The fix for this sufficiently changes process execution handling that we will defer the fix to post-5.0 and consider this errata.
Documentation rottage: S/Key	--	--	We now use OPIE instead of S/Key. The handbook doesn't know that yet.
Documentation wanted: gdbe	--	&a.chris;	5.0 includes GDBE, supporting encryption of swap and storage. It would be nice if that was documented in the handbook.
iir driver fails to probe disks	--	--	During the install, the iir controller appears to correctly probe, but finds no disk devices. The card in question is an Intel srcu32 RAID controller with 32Mb RAM, Firmware revision 2.33.01. Direct access to real iir hardware for SCSI developers would be very helpful in resolving this problem.
Issue	Status	Responsible	Description
if_ie, if_le, if_wl network device drivers	--	&a.sam;	Changes made to the ethernet driver interfaces required sweeping API changes across all ethernet device drivers. While these changes are largely mechanical, they were not tested for three less frequently used interface drivers: if_ie, if_le, and if_wl. They each require testing (and probably fixing) prior to 5.0-RELEASE. If you have access to devices that use these drivers, please perform local testing and provide feedback to Sam Leffler.
No console (term) if smbus is enable in the kernel	--	--	There are reports that kernels build with smbus, viapm, and smb devices may not properly probe and support the system console following boot.