Citi has an OpenBSD NFSv4 client implementation. Is anyone working on porting that to FreeBSD? From a cursory glance it appears to rely heavily on the existing NFS infrastructure, how far have FreeBSD and OpenBSD developed away from the 4.4 implementation?
http://www.citi.umich.edu/projects/nfsv4/openbsd/ -Kip On Mon, 30 Dec 2002, Robert Watson wrote: > > On Fri, 27 Dec 2002, joe mcguckin wrote: > > > Are there any strange interactions between NFS and filesystems that are > > not UFS? E.g. UFS2? Does NFS support new features that these fs's may > > implement? > > NFS can represent many but not all of the services found in UFS1 and UFS2. > Among things it doesn't support are the retrieval and manipulation of BSD > file user flags, system flags, extended attributes, and access control > lists (ACLs). However, NFSv3 does correctly handle enforcement with these > features because clients rely on the server to evaluate protections on > file system objects using an ACCESS RPC. NFS2 evaluates protections on > the client (if I recall correctly) so may not behave properly. There are > RPC extensions to NFSv3 to retrieve and manipulate ACLs on Solaris, IRIX, > et al, but we don't currently implement those extensions. Likewise, NFSv4 > supports ACL management, but we don't yet implement NFSv4. It shouldn't > be too hard to dig up information on the NFSv3 ACL RPC extensions and > implement them on FreeBSD 5, since the semantics of our ACLs are highly > compatible with Solaris and IRIX. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > [EMAIL PROTECTED] Network Associates Laboratories > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
