diff --git a/en/releases/5.0R/todo.sgml b/en/releases/5.0R/todo.sgml index cfdaac9a58..202ff23be3 100644 --- a/en/releases/5.0R/todo.sgml +++ b/en/releases/5.0R/todo.sgml @@ -1,207 +1,208 @@ - + %includes; ]> &header;

Open Issues

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.

Must Resolve Issues for 5.0-DP2

IssueStatusResponsibleDescription
X instabilityUnknown?? XFree86 hangs after several hours/days of use with -CURRENT. No further details are available at this time.

Must Resolve Issues for 5.0-RELEASE

- + - - - + + +
IssueStatusResponsibleDescription
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.
devdPrototype committed. imp@FreeBSD.orgA 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.orgUser 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 frameworkFreeBSD CVS HEAD: default now switchedBelived to be OK. phk@FreeBSD.org,sam@FreeBSD.orgMove 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 i386In progressgreen@FreeBSD.org, phk@FreeBSD.orgUFS2 can be successfully booted on sparc64, but on i386 the - emulated 64-bit instructions grow boot2 beyond the 8k traditionally - allocated for that boot loader. There appear to be some combination - of books in various bits of the boot loading mechanism relating - to this (possibly including in the i386 emulated 64-bit instructions) - that must be resolved. In addition, the installation code now needs - to start leaving room for the larger boot blocks so that freshly - installed systems can be UFS2-bootable.In progress. We might want to miss on this one.phk@FreeBSD.orgUFS2 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 In progress markm@FreeBSD.org KerberosV appears not to currently work with OpenPAM.
FireWire SupportIn 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 LockingPatches available in Perforce jhb@FreeBSD.orgFurther locking cleanups relating to p_ucred.
ipfw2 on non-i386 platformsunknown luigi@FreeBSD.orgIn 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.

Desired Features for 5.0-RELEASE

IssueStatusResponsibleDescription
User documentation for ACPI. -- freebsd-doc@FreeBSD.org The new ACPI code is a very important component of FreeBSD 5.0-RELEASE, but the documentation is insufficient. The manual page does not describe how to perform the basic ACPI tasks. The Usenix paper, man pages, and mailing list archives should be used to write a substantial new section to the FreeBSD Handbook. New users read the Handbook. See PR 43528.
OpenOffice--ports@FreeBSD.org A working OpenOffice port is a strongly desired feature for 5.0
&footer;