Date: Thu, 14 Nov 2013 11:15:19 +0000 From: "Robert N. M. Watson" <rwatson@FreeBSD.org> To: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r258041 - head/lib/libc/posix1e Message-ID: <8E1D58E8-7625-4D4A-AB77-D8C48EA3BB1E@FreeBSD.org> In-Reply-To: <3C657070-0470-4107-81D8-73C6138F612C@FreeBSD.org> References: <201311121044.rACAigGi093973@svn.freebsd.org> <alpine.BSF.2.00.1311140807000.10113@fledge.watson.org> <3C657070-0470-4107-81D8-73C6138F612C@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On 14 Nov 2013, at 11:06, Edward Tomasz Napierała <trasz@FreeBSD.org> wrote: > Wiadomość napisana przez Robert Watson w dniu 14 lis 2013, o godz. 09:07: >> On Tue, 12 Nov 2013, Edward Tomasz Napierala wrote: >> >>> Mention acl_get_brand_np(3). >>> >>> MFC after: 2 weeks >>> Sponsored by: The FreeBSD Foundation >> >> Doing some writing recently, I did wonder if acl(3) and some of the other ACL API man pages might need a bit more updating to be clear about support for NFSv4 ACLs. The user-facing man pages (getfacl(1), setfacl(1)) appear fully updated, but not much mention of NFSv4 in the programmer documentation. > > Hm, it should be already documented - from updated list of constants > in acl_add_perm(3) or acl_set_tag_type(3), to new functions, such as > acl_add_flag_np(3) or acl_set_entry_type_np(3). Less a question of missing documentation than missing advertising. For example, acl(5) makes it really obvious that POSIX.1e semantics are supported, and the first mention of NFSv4 is in a long list of other unsupported types. We might want to begin simply by saying ".Fx supports POSIX.1e and NFSv4 ACLs" and expand a bit on the differences. Roberthelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8E1D58E8-7625-4D4A-AB77-D8C48EA3BB1E>