diff --git a/en/releases/5.0R/todo.sgml b/en/releases/5.0R/todo.sgml index d38092b49f..0d5442bec7 100644 --- a/en/releases/5.0R/todo.sgml +++ b/en/releases/5.0R/todo.sgml @@ -1,338 +1,335 @@ - + %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.

- + 5.0. If you have any updates for this list, please e-mail + re@FreeBSD.org.

Must Resolve Issues for 5.0-RC1

IssueStatusResponsibleDescription
Audit of devfs device permissions In progress kris@FreeBSD.org 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.
Race conditions in truss Debugging and fixing in progress robert@FreeBSD.org 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.
Many reported problems with disklabel -e -- phk@FreeBSD.org, jhb@FreeBSD.org 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.
Reported problems with fdisk disk editor -- -- Reported problems deleting NTFS slices using the sysinstall fdisk editor.
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).
mly driver hangs during install -- scottl@FreeBSD.org, jeff@FreeBSD.org 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
Need to disable rare ISA drivers via hints -- jhb@FreeBSD.org ISA driver probes for rare drivers can be disruptive, and should be disabled.
doscmd results in a lock panic Patch submitted mux@FreeBSD.org Running doscmd results in a locking panic.

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 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.
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.
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 userland applications Mostly merged, some minor updates pending rwatson@FreeBSD.org Most MAC support for user applications and daemons has been merged. Minor updates to support recursive file labeling, correct labeling in inetd, and a few other bits and pieces is pending.
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.
gdb for sparc64 -- tmm@FreeBSD.org gdb 5.3 now works with sparc64; gdb import required.
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, OpenSSH, and PAM In progress markm@FreeBSD.org, nectar@FreeBSD.org KerberosV appears not to currently work with OpenSSH using PAM. Bugs relating to pam_kerberosV have in large part been fixed.
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.
awk(1) locale support patches being circulated ru@FreeBSD.org awk(1) should be fixed to respect locale
smbfs may be broken -- -- There are reports that smbfs may not be working with recent 5.0-CURRENT snapshots. The symptoms appear to be that smbfs will mount, but reads return an error, and writes result in 0-byte files. Testing of smbfs is encouraged, and claiming of this trouble item if problems are found is likewise encouraged. Note: this problem may be limited to Win2K or WinNT servers, as some local testing demonstrates that smbfs with Samba is not having this problem.
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.

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.
freebsd-games -- markm@FreeBSD.org A number of games were stripped from the base system: they should be made into a port.
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@FreeBSD.org mbr has requested that we change from using "local" to "unix" for tirpc unix domain socket transport naming, to sync to NetBSD.
OpenSSH reports lastlog warning -- des@FreeBSD.org OpenSSH appears to invoke the PAM session code in the wrong process when running with privsep, resulting in warnings of the form "Nov 20 18:08:55 u60 sshd[2002]: /var/log/lastlog: Permission denied". This may be a bug that requires reworking OpenSSH to work properly with PAM, but should be resolved in some form for the release.
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).
&footer;