* community/gsoc/project_ideas/nfs.mdwn: add a link to libnfs, which
one could use for a client NFS.  Also mention that Sergey has a
somewhat working 9P port for the Hurd.
---
 community/gsoc/project_ideas/nfs.mdwn | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/community/gsoc/project_ideas/nfs.mdwn 
b/community/gsoc/project_ideas/nfs.mdwn
index d4980279..52043cf2 100644
--- a/community/gsoc/project_ideas/nfs.mdwn
+++ b/community/gsoc/project_ideas/nfs.mdwn
@@ -16,15 +16,15 @@ very well: File locking doesn't work properly (at least in 
conjunction with a
 GNU/Linux server), and performance is extremely poor. Part of the problems
 could be owed to the fact that only NFSv2 is supported so far.
 
-(Note though that locking on the Hurd is problematic in general, not only in
-conjunction with NFS -- see the [[file_locking]] task.)
-
-This project encompasses implementing NFSv3 support, fixing bugs and
+This project encompasses implementing NFSv4 support, fixing bugs and
 performance problems -- the goal is to have good NFS support. The work done in
 a previous unfinished GSoC project can serve as a starting point.
 
 Both client and server parts need work, though the client is probably much more
-important for now, and shall be the major focus of this project.
+important for now, and shall be the major focus of this project.  One
+could probably use [[open_issues/libnfs]] for the client portion.  You
+should probably talk to Sergey, who has an indevelopment
+9P port to the Hurd.
 
 Some [discussion of NFS
 improvements](http://lists.gnu.org/archive/html/bug-hurd/2008-04/msg00035.html)
-- 
2.45.2


Reply via email to