To do
From Linux NFS
(Difference between revisions)
(add error reporting) |
|||
| Line 9: | Line 9: | ||
* [[client ACL tools]]: The client ACL utilities need some work | * [[client ACL tools]]: The client ACL utilities need some work | ||
* [[wireshark improvements]]: Wireshark (previously known as ethereal) is useful for debugging NFSv4 problems. But it could be more useful. | * [[wireshark improvements]]: Wireshark (previously known as ethereal) is useful for debugging NFSv4 problems. But it could be more useful. | ||
| + | * [[error reporting]]: It's easier for people to set up nfsv4 and krb5 if we give people informative error messages when something is wrong. | ||
Revision as of 21:34, 28 May 2007
See also:
Some specific projects; follow links for more details on design requirements and implementation plans. If you intend to work on any of these, please keep in close contact with other developers, using nfsv4@linux-nfs.org.
- pseudofilesystem improvements: The NFSv4 server currently patches together export paths in a way that is inconsistent with NFSv2 and NFSv3 and causes severe problems for automount users.
- gss callbacks: We currently don't support rpcsec_gss security on the callback channel, which means that if you mount with krb5 then you don't get the benefit of delegations.
- client ACL tools: The client ACL utilities need some work
- wireshark improvements: Wireshark (previously known as ethereal) is useful for debugging NFSv4 problems. But it could be more useful.
- error reporting: It's easier for people to set up nfsv4 and krb5 if we give people informative error messages when something is wrong.
