diff --git a/en/releases/5.0R/todo.sgml b/en/releases/5.0R/todo.sgml
index 202ff23be3..c2c23b069e 100644
--- a/en/releases/5.0R/todo.sgml
+++ b/en/releases/5.0R/todo.sgml
@@ -1,208 +1,202 @@
-
+
%includes;
]>
&header;
This is a list of open issues that need to be resolved for FreeBSD
5.0. If you think something should be listed here, please email
re@FreeBSD.org. This issue was discussed in detail at the Developer Summit
at Usenix.
-
Issue | Status | Responsible | Description |
5.0 Documentation | -- | freebsd-doc |
As a minimum, we need to cover the areas where 5.x and 4.x
differ in the FAQ and Handbook. This entails marking some areas
with "This procedure is specific to 4.X. For more information for
5.x, please see foo(n)" or similar. This needs to happen quickly,
to give adequate time for the translation teams to catch up. |
+
+ Disable performance penalizing debug options |
+ Pending RC1
+ | re@ |
+ A number of performance-penalizing debug options are turned on
+ by default in 5.0-CURRENT. These include user malloc debugging
+ flags, WITNESS, INVARIANTS, and others. These must be turned off
+ as we approach the release. |
+
+
devd | Prototype committed. |
imp@FreeBSD.org | A devd prototype has been committed;
will mature as we approach the 5.0 release, including adopting
a mature configuration format. |
-
- TrustedBSD MAC Framework system call interface |
- Perforce trustedbsd_mac: preparing for merge to main tree |
- rwatson@FreeBSD.org |
- Revised system call interface supporting extensible label access
- from userland. This replaces the current temporary API which
- supports only a subset of the available policies and is not
- extensible at run-time. |
-
-
TrustedBSD MAC Framework userland applications |
Perforce trustedbsd_mac: preparing for merge to main tree |
rwatson@FreeBSD.org |
Simple labeling applications including {get,set}[fp]mac(8),
as well as labeling during the login process. |
TrustedBSD MAC Framework documentation |
FreeBSD documentation CVS HEAD: in progress |
chris@FreeBSD.org | User and developer documentation of
the new extensible security framework. Includes guides for live
deployment, development of policy modules, and implementation
information. |
Port of LOMAC to TrustedBSD MAC Framework |
Perforce trustedbsd_mac: in progress |
green@FreeBSD.org |
Re-implementation of LOMAC to plug in via the MAC framework,
making it easier to deploy and support, as well as removing
code duplication in the LOMAC tree to improve maintenance cost. |
-
- Switch to GEOM as default storage management framework |
- Belived to be OK. |
- phk@FreeBSD.org,sam@FreeBSD.org | Move to using GEOM in the
- GENERIC kernel as the default storage management framework,
- supporting out-of-the-box use of new partiton types, data transforms
- (such as cryptographic swap protection), etc. Currently waiting on
- bugs in sysinstall to be resolved relating to libdisk; many
- nits have already been resolved (SCSI deadlocks, etc). |
-
-
gdb for sparc64 |
-- |
tmm@FreeBSD.org |
gdb 5.3 now works with sparc64; gdb import required. |
Sysinstall for sparc64 |
-- |
phk@FreeBSD.org |
Sysinstall currently doesn't understand disk labeling sufficiently
to correctly install on sparc64. Various approaches might be
taken, including adopting libwhisk as an extendable labeling
mechanism, but the work hasn't yet been done. For sparc64 to be
a Tier 1 supported platform, it needs sysinstall to work out
of the box. |
UFS2 bootable on i386 |
In progress. We might want to miss on this one. |
phk@FreeBSD.org |
UFS2 can be successfully booted on sparc64, but on i386
boot2 cannot fit in the space reserved in front of a UFS1 filesystem.
disklabel, libdisk, sysinstall and newfs needs to learn about this
wrinkle, and we need some makefile magic to build both UFS1 and
UFS1/2 boot2 boot files.
The potential for foot-shooting is very large, and phk@ currently
leans towards defaulting to UFS1 for root and boot, and UFS2 for
all other filesystems.
|
ACPI support for multiple host-pci bridge adapters |
patches being circulated |
jhb@FreeBSD.org |
There appear to be problems with BIOS's incorrectly identifying
host-pci bridge adpaters. These must be resolved before 5.0. |
- KerberosV and PAM |
+ KerberosV, OpenSSH, and PAM |
In progress |
- markm@FreeBSD.org |
- KerberosV appears not to currently work with OpenPAM. |
+ markm@FreeBSD.org, nectar@FreeBSD.org |
+ KerberosV appears not to currently work with OpenSSH using PAM. |
FireWire Support | In progress | ?? |
Firewire kernel support has been committed. Userland support is
pending. Large quantities of debugging output are reported;
may require an "experimental feature tag" for the release notes? |
Proc Locking | Patches available in Perforce |
jhb@FreeBSD.org | Further locking cleanups relating to
p_ucred. |
ipfw2 on non-i386 platforms | unknown |
luigi@FreeBSD.org | In order for IPFW2 to be the default
firewall package in FreeBSD 5.0-RELEASE, it needs to work properly
on non-i386 platforms. Currently it crashes on Alpha and sparc64
due to alignment problems. |