os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove a few obsolete entries.

Browse source
This commit is contained in:
Scott Long 2006-04-30 06:46:09 +00:00
parent 0acd9d1959
commit 446657abaa
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=27676
1 changed files with 1 additions and 49 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
en/releases/6.1R/todo.sgml
View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.27 2006/04/25 11:43:09 hrs Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/6.1R/todo.sgml,v 1.28 2006/04/30 06:42:17 scottl Exp $">
<!ENTITY local.rel "6.1">
<!ENTITY title "FreeBSD 6.1 Open Issues">
<!ENTITY % navincludes SYSTEM "../../includes.navdownload.sgml"> %navincludes;
@ -132,19 +132,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
update the calibration code to be more precise on 2 March.</td>
</tr>
<tr>
<td>rpc.lockd interoperability problems</td>
<td>&status.unknown;</td>
<td>&a.kuriyama;</td>
<td>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.</td>
</tr>
<tr>
<td>NFS data corruption between two 7.0 machines</td>
<td>&status.wip;</td>
@ -176,13 +163,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
looks to handle this better and might be a suitable replacement.</td>
</tr>
<tr>
<td>updated hal and ath drivers</td>
<td>&status.done;</td>
<td>&a.sam;</td>
<td>ath hal has been updated to v0.9.16.16 in February 2006.</td>
</tr>
<tr>
<td>fix ntpdate(1) bogus output on amd64.</td>
<td>&status.unknown;</td>
@ -190,25 +170,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
<td></td>
</tr>
<tr>
<td>Improve performance</td>
<td>&status.unknown;</td>
<td></td>
<td>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.</td>
</tr>
<tr>
<td>/dev/kmem panic</td>
<td>&status.wip;</td>
<td>&a.ups;</td>
<td>&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.</td>
</tr>
<tr>
<td>make -jN</td>
<td>&status.new;</td>
@ -229,15 +190,6 @@ on a filesystem is negative; fsck -f is needed to correct this.</td>
sys-admins tend to do.</td>
</tr>
<tr>
<td>swapping on 6.0 is slower than on 4.x</td>
<td>&status.new;</td>
<td>&nbsp;</td>
<td>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.</td>
</tr>
<tr>
<td>i386 deadlocks with >16GB swap</td>
<td>&status.deferred;</td>