Remove smbfs task: we believe it's now operating as well on 5.x as it

was on 4.x-STABLE, which is to say "not perfectly", but adequately
for the purposes of the TODO item.  Thanks to Tim Robbins for grabbing
this one by the horns.

Any long-term fixes for smbfs stability issues relating to forceable
unmount and dropped connections also welcome.
This commit is contained in:
Robert Watson 2002-12-01 22:08:26 +00:00
parent fa8754b6ae
commit 7e4355599e
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=15110

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/5.0R/todo.sgml,v 1.58 2002/11/27 18:58:34 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.59 2002/11/27 21:36:27 rwatson Exp $">
<!ENTITY title "FreeBSD 5.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
@ -229,20 +229,6 @@
<td>awk(1) should be fixed to respect locale</td>
</tr>
<tr>
<td>smbfs may be broken</td>
<td>patches being circulated</td>
<td>tjr</td>
<td>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.</td>
</tr>
<tr>
<td>No console (term) if smbus is enable in the kernel</td>
<td>--</td>