diff --git a/en/releases/5.0R/todo.sgml b/en/releases/5.0R/todo.sgml index 6dee830e4d..a358d98a4e 100644 --- a/en/releases/5.0R/todo.sgml +++ b/en/releases/5.0R/todo.sgml @@ -1,413 +1,413 @@ - + %includes; ]> &header;

Open Issues

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.

Must Resolve Issues for 5.0-RC2

- +
IssueStatusResponsibleDescription
Many reported problems with disklabel -e -- phk@, 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 progresskris@kris@,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 -- scottl@, 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.
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
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, DEBUG=-g, and others. These must be turned off as we approach the release.
TrustedBSD MAC Framework userland applications Mostly merged, some minor updates pending rwatson@ Most MAC support for user applications and daemons has been merged. Minor updates to support correct labeling in inetd, optional labeling of ttys, and a few other bits and pieces are pending.
Port of LOMAC to TrustedBSD MAC Framework Merge in progress green@,rwatson@ New mac_lomac implementation almost completely merged: currently missing are the default policy file (commit request under review by re@) and documentation.
devdPrototype committed. imp@A devd prototype has been committed; will mature as we approach the 5.0 release, including adopting a mature configuration format.
Convert base system utilities that rely on Perl -- markm With perl removed from the base system in 5.0, any existing dependencies on perl must also be converted to a native shell scripting language, C, or be made into packages or ports. Remaining base system tools include mmroff, afmtodit.
KerberosV, OpenSSH, and PAM In progress markm@, des@, nectar@ KerberosV appears not to currently work with OpenSSH using PAM. Bugs relating to pam_kerberosV have in large part been fixed.
Update Handbook for 5.0 installation -- -- The handbook largely decsribes a 4.x installation, and doesn't mention the driver floppy or other recent events. Likewise, it probably hasn't been updated for label editor changes. It also probably talks about the in-kernel ISA configuration editor, which is no longer present. It should talk about ACPI more. Also, the recommended minimum / size should be increased to 128Mb. The handbook should be updated once sysinstall has stabilized, which it should have after RC1.
Handbook update: swapfile instructions -- -- The handbook instructions for swapfiles use vnconfig, which is apropriate only for 4.x, not 5.0. We need an updated section on configuring it for 5.0.
device.hints documentation -- scottl@ INSTALL.TXT requires updating for device.hints, and the device.hints text in the handbook requires examples. With a number of more obscure ISA drivers disabled using hints by default, this information will be necessary to get FreeBSD 5 up and running.

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.
Disable verbose debug options Pending RC2 re@ By default, ACPI generates verbose bus dumps during initial boot even if verbose it turned off. Libdisk also includes the DEBUG define by default, resulting in additional output. This output needs to be turned down following RC2.
TrustedBSD MAC Framework documentation FreeBSD documentation CVS HEAD: in progress chris@User and developer documentation of the new extensible security framework. Includes guides for live deployment, development of policy modules, and implementation information.
UFS2 bootable on i386 In progress. We might want to miss on this one. phk@ 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.
FireWire Support In progress simokawa@ 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@Further locking cleanups relating to p_ucred.
awk(1) locale support Pending import of new one-true-awk obrien@ awk(1) should be fixed to respect locale
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.
inpcb panic involving IP stack sleep -- -- Report of a panic in the TCP syncache thread under load, due to another thread sleeping while holding an inpcb mutex, when not running with WITNESS (WITNESS would have caught the sleep earlier).

Desired Features for 5.0-RELEASE

IssueStatusResponsibleDescription
User documentation for ACPI. -- freebsd-doc@ 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.
a.out toolchain port -- -- A.out support in the base system was reduced; the removed build chain components should be made into a port.
Rename of local -> unix in rpc socket names -- mbr@ mbr has requested that we change from using "local" to "unix" for tirpc unix domain socket transport naming, to sync to NetBSD.
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.
gdb for sparc64 -- tmm@ gdb 5.3 now works with sparc64; gdb import desired.
live file system boot0cfg -- -- boot0cfg -s on a live file system now no longer functions. It would be highly desirable for this, and related functionality, to work.
SMP documentation update -- -- smp(4) and other bits of system documentation relating to SMP are dated since to introduction of SMPng, MP support on sparc64, alpha, and ia64. These documents should be updated. In addition, the SMPng draft architecture should be updated and committed.
Race conditions in truss Debugging and fixing in progress 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.
gcc 3.3 ABI hack -- obrien@ Hack the C++ ABI in our in-tree version of g++ to match what will be used for gcc 3.3. This would permit us forward ABI compatibility, avoiding future breakage when we want to import the new gcc 3.3 during 5.x lifetime.
Documentation rottage: S/Key -- -- We now use OPIE instead of S/Key. The handbook doesn't know that yet.
Documentation rottage: MFS/vnconfig/mdmfs/... In progress blackend@ 5.0 uses md-backed UFS file systems, which are created using mdconfig and newfs, or with mdmfs. Much documentation still believes firmly in options MFS and vnconfig, and should be fixed. This includes a number of sections of the handbook.
Documentation wanted: gdbe -- -- 5.0 includes GDBE, supporting encryption of swap and storage. It would be nice if that was documented in the handbook.

Areas requiring immediate testing due to 5.0 changes

IssueStatusResponsibleDescription
if_ie, if_le, if_wl network device drivers -- 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.
vlan testing -- sam@ Changes to the network device driver interfaces and introduction of m_tags has changed the way in which vlans are implemented in 5.0. These changes require additional testing. If you make use if the vlan behavior in local configurations, please test them with recent 5.0 snapshots and provide feedback to Sam Leffler.
&footer;