From 446657abaa4e07faa85210c8a5116128d11d4f3f Mon Sep 17 00:00:00 2001 From: Scott Long Date: Sun, 30 Apr 2006 06:46:09 +0000 Subject: [PATCH] Remove a few obsolete entries. --- en/releases/6.1R/todo.sgml | 50 +------------------------------------- 1 file changed, 1 insertion(+), 49 deletions(-) diff --git a/en/releases/6.1R/todo.sgml b/en/releases/6.1R/todo.sgml index d1823c8850..9b9d856160 100644 --- a/en/releases/6.1R/todo.sgml +++ b/en/releases/6.1R/todo.sgml @@ -1,7 +1,7 @@ - + %navincludes; @@ -132,19 +132,6 @@ on a filesystem is negative; fsck -f is needed to correct this. update the calibration code to be more precise on 2 March. - - rpc.lockd interoperability problems - &status.unknown; - &a.kuriyama; - rpc.lockd seems to have interoperability problems that date back a - number of months but have not been reliably identified. - This may be the cause of the many "rpc.lockd no longer interoperates" - bug reports seen on -stable. Unfortunately, rpc.lockd also contains a - number of severe architectural issues that make it unsuitable for a - production environment. Fixing these is beyond the scope of the - 6.1 release. - - NFS data corruption between two 7.0 machines &status.wip; @@ -176,13 +163,6 @@ on a filesystem is negative; fsck -f is needed to correct this. looks to handle this better and might be a suitable replacement. - - updated hal and ath drivers - &status.done; - &a.sam; - ath hal has been updated to v0.9.16.16 in February 2006. - - fix ntpdate(1) bogus output on amd64. &status.unknown; @@ -190,25 +170,6 @@ on a filesystem is negative; fsck -f is needed to correct this. - - Improve performance - &status.unknown; - - What seem to be 4BSD scheduler bugs in 6.0 that - cause performance to be anomalously low in certain situations. - &a.davidxu; has expressed some interest in this problem. - - - - /dev/kmem panic - &status.wip; - &a.ups; - &a.kris; has noticed panics on SMP machines when there was ABI - breakage of libkvm and world was not rebuilt and utilities like - fstat were used. This suggests panics can be caused by incorrect - accesses to /dev/kmem. &a.ups; committed a fix for i386. - - make -jN &status.new; @@ -229,15 +190,6 @@ on a filesystem is negative; fsck -f is needed to correct this. sys-admins tend to do. - - swapping on 6.0 is slower than on 4.x - &status.new; -   - Performance on swap handling is much slower than 4.x and - this can make a system essentially unusable when moderate - paging activity is going on. - - i386 deadlocks with >16GB swap &status.deferred;