Re: richacl(7) man page review comments

On Tue, Feb 23, 2016 at 11:16 AM, Michael Kerrisk (man-pages) wrote: > On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: >> On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) >> wrote: >>> I've once more pulled from the latest git;

Re: richacl(7) man page review comments

On Tue, Feb 23, 2016 at 11:16 AM, Michael Kerrisk (man-pages) wrote: > On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: >> On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) >> wrote: >>> I've once more pulled from the latest git; here's some more comments. >> >> thanks again. I've

Re: richacl(7) man page review comments

On Tue, Feb 23, 2016 at 4:09 PM, Andreas Gruenbacher wrote: > Hi Michael, > > On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) > wrote: >> On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: >>> On Sun, Feb 21, 2016 at 10:40 PM, Michael

Re: richacl(7) man page review comments

On Tue, Feb 23, 2016 at 4:09 PM, Andreas Gruenbacher wrote: > Hi Michael, > > On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) > wrote: >> On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: >>> On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) >>> wrote: I've once

Re: richacl(7) man page review comments

Hi Michael, On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) wrote: > On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: >> On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) >> wrote: >>> I've once more pulled from the

Re: richacl(7) man page review comments

Hi Michael, On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) wrote: > On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: >> On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) >> wrote: >>> I've once more pulled from the latest git; here's some more comments. >> >>

Re: richacl(7) man page review comments

On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) wrote: > So, in terms of actually testing this stuff, is it just a matter of > applying your patch series to the kernel, building the kernel, pulling > the RichACL user-space tools from Git, and mount(8)ing a

Re: richacl(7) man page review comments

On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) wrote: > So, in terms of actually testing this stuff, is it just a matter of > applying your patch series to the kernel, building the kernel, pulling > the RichACL user-space tools from Git, and mount(8)ing a filesystem with > the

Re: richacl(7) man page review comments

Hi Andreas, On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: > Hi Michael, > > On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) > wrote: >> I've once more pulled from the latest git; here's some more comments. > > thanks again. I've updated the repo with

Re: richacl(7) man page review comments

Hi Andreas, On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: > Hi Michael, > > On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) > wrote: >> I've once more pulled from the latest git; here's some more comments. > > thanks again. I've updated the repo with your changes. Next

Re: richacl(7) man page review comments

On Tue, Feb 23, 2016 at 11:16 AM, Michael Kerrisk (man-pages) wrote: > On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: >> On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) >> wrote: >>> Could we start with just a few simple examples

Re: richacl(7) man page review comments

On Tue, Feb 23, 2016 at 11:16 AM, Michael Kerrisk (man-pages) wrote: > On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: >> On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) >> wrote: >>> Could we start with just a few simple examples already, and build up >>> over future

Re: richacl(7) man page review comments

Hi Andreas, On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: > Hi Michael, > > On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) > wrote: >> I've once more pulled from the latest git; here's some more comments. > > thanks again. I've updated the repo with

Re: richacl(7) man page review comments

Hi Andreas, On 02/22/2016 03:46 PM, Andreas Gruenbacher wrote: > Hi Michael, > > On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) > wrote: >> I've once more pulled from the latest git; here's some more comments. > > thanks again. I've updated the repo with your changes. Thanks!

Re: richacl(7) man page review comments

Hi Michael, On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) wrote: > I've once more pulled from the latest git; here's some more comments. thanks again. I've updated the repo with your changes. >> .\" >> .\" RichACL Manual Pages >> .\" >> .\" Copyright (C)

Re: richacl(7) man page review comments

Hi Michael, On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) wrote: > I've once more pulled from the latest git; here's some more comments. thanks again. I've updated the repo with your changes. >> .\" >> .\" RichACL Manual Pages >> .\" >> .\" Copyright (C) 2015,2016 Red Hat,

Re: richacl(7) man page review comments

Hello Andreas, On 02/20/2016 05:37 PM, Andreas Gruenbacher wrote: > Hi Michael, > > thanks again for all the feedback. I've followed all your suggestions; > again, please see the github repo for the latest version: > > https://github.com/andreas-gruenbacher/richacl I've once more pulled from

Re: richacl(7) man page review comments

Hello Andreas, On 02/20/2016 05:37 PM, Andreas Gruenbacher wrote: > Hi Michael, > > thanks again for all the feedback. I've followed all your suggestions; > again, please see the github repo for the latest version: > > https://github.com/andreas-gruenbacher/richacl I've once more pulled from

Re: richacl(7) man page review comments

On 02/20/2016 05:37 PM, Andreas Gruenbacher wrote: > Hi Michael, > > thanks again for all the feedback. I've followed all your suggestions; > again, please see the github repo for the latest version: > > https://github.com/andreas-gruenbacher/richacl > > On Sun, Feb 14, 2016 at 10:31 PM,

Re: richacl(7) man page review comments

On 02/20/2016 05:37 PM, Andreas Gruenbacher wrote: > Hi Michael, > > thanks again for all the feedback. I've followed all your suggestions; > again, please see the github repo for the latest version: > > https://github.com/andreas-gruenbacher/richacl > > On Sun, Feb 14, 2016 at 10:31 PM,

Re: richacl(7) man page review comments

Hi Michael, thanks again for all the feedback. I've followed all your suggestions; again, please see the github repo for the latest version: https://github.com/andreas-gruenbacher/richacl On Sun, Feb 14, 2016 at 10:31 PM, Michael Kerrisk (man-pages) wrote: > Hi

Re: richacl(7) man page review comments

Hi Michael, thanks again for all the feedback. I've followed all your suggestions; again, please see the github repo for the latest version: https://github.com/andreas-gruenbacher/richacl On Sun, Feb 14, 2016 at 10:31 PM, Michael Kerrisk (man-pages) wrote: > Hi Andreas, > > Here's a few more

Re: richacl(7) man page review comments

On 15 February 2016 at 12:35, Andreas Gruenbacher wrote: > On Mon, Feb 15, 2016 at 11:25 AM, Michael Kerrisk (man-pages) > wrote: >> You're right. I was confusing with xattr(7). So, I think it might >> make some sense to eventually move both of these

Re: richacl(7) man page review comments

On 15 February 2016 at 12:35, Andreas Gruenbacher wrote: > On Mon, Feb 15, 2016 at 11:25 AM, Michael Kerrisk (man-pages) > wrote: >> You're right. I was confusing with xattr(7). So, I think it might >> make some sense to eventually move both of these into man-pages (for >> richacl(7), at least,

Re: richacl(7) man page review comments

On Mon, Feb 15, 2016 at 11:25 AM, Michael Kerrisk (man-pages) wrote: > You're right. I was confusing with xattr(7). So, I think it might > make some sense to eventually move both of these into man-pages (for > richacl(7), at least, it's probably worth delaying this for a

Re: richacl(7) man page review comments

On Mon, Feb 15, 2016 at 11:25 AM, Michael Kerrisk (man-pages) wrote: > You're right. I was confusing with xattr(7). So, I think it might > make some sense to eventually move both of these into man-pages (for > richacl(7), at least, it's probably worth delaying this for a bit), > since they're

Re: richacl(7) man page review comments

Hi Andreas, On 02/15/2016 12:12 AM, Andreas Gruenbacher wrote: > On Sun, Feb 14, 2016 at 10:27 PM, Michael Kerrisk (man-pages) > wrote: >> On 02/12/2016 11:25 PM, Andreas Gruenbacher wrote: >>> We could sure move acl(5) and richacl(7) there. >> >> We already have acl(5)

Re: richacl(7) man page review comments

Hi Andreas, On 02/15/2016 12:12 AM, Andreas Gruenbacher wrote: > On Sun, Feb 14, 2016 at 10:27 PM, Michael Kerrisk (man-pages) > wrote: >> On 02/12/2016 11:25 PM, Andreas Gruenbacher wrote: >>> We could sure move acl(5) and richacl(7) there. >> >> We already have acl(5) (now "acl(7)" in man

Re: richacl(7) man page review comments

On Sun, Feb 14, 2016 at 10:27 PM, Michael Kerrisk (man-pages) wrote: > On 02/12/2016 11:25 PM, Andreas Gruenbacher wrote: >> We could sure move acl(5) and richacl(7) there. > > We already have acl(5) (now "acl(7)" in man pages) ;-). Hmm, I can't find that page either in

Re: richacl(7) man page review comments

Hi Andreas, Here's a few more comments on the current richacl(7) page that I fetched from the git repo. > .\" > .\" RichACL Manual Pages > .\" > .\" Copyright (C) 2015,2016 Red Hat, Inc. > .\" Written by Andreas Gruenbacher > .\" This is free documentation; you can redistribute it and/or > .\"

Re: richacl(7) man page review comments

On 02/12/2016 11:25 PM, Andreas Gruenbacher wrote: > Hi Michael, > > On Sun, Feb 7, 2016 at 5:35 PM, Michael Kerrisk (man-pages) > wrote: >> Hi Andreas, >> >> I'll probably have quite a few more comments on this page as I get to >> understand RichACLs better. Here's some comments from an initial

Re: richacl(7) man page review comments

On 02/12/2016 11:25 PM, Andreas Gruenbacher wrote: > Hi Michael, > > On Sun, Feb 7, 2016 at 5:35 PM, Michael Kerrisk (man-pages) > wrote: >> Hi Andreas, >> >> I'll probably have quite a few more comments on this page as I get to >> understand RichACLs better. Here's some

Re: richacl(7) man page review comments

Hi Andreas, Here's a few more comments on the current richacl(7) page that I fetched from the git repo. > .\" > .\" RichACL Manual Pages > .\" > .\" Copyright (C) 2015,2016 Red Hat, Inc. > .\" Written by Andreas Gruenbacher > .\" This is free documentation; you can

Re: richacl(7) man page review comments

On Sun, Feb 14, 2016 at 10:27 PM, Michael Kerrisk (man-pages) wrote: > On 02/12/2016 11:25 PM, Andreas Gruenbacher wrote: >> We could sure move acl(5) and richacl(7) there. > > We already have acl(5) (now "acl(7)" in man pages) ;-). Hmm, I can't find that page either in

Re: richacl(7) man page review comments

Hi Michael, On Sun, Feb 7, 2016 at 5:35 PM, Michael Kerrisk (man-pages) wrote: > Hi Andreas, > > I'll probably have quite a few more comments on this page as I get to > understand RichACLs better. Here's some comments from an initial > reading. thanks a lot for all the feedback to the

Re: richacl(7) man page review comments

Hi Michael, On Sun, Feb 7, 2016 at 5:35 PM, Michael Kerrisk (man-pages) wrote: > Hi Andreas, > > I'll probably have quite a few more comments on this page as I get to > understand RichACLs better. Here's some comments from an initial > reading. thanks a lot for all the

Re: richacl(7) man page review comments

On Sun, Feb 07, 2016 at 05:35:46PM +0100, Michael Kerrisk (man-pages) wrote: > > This permission is always implicitly granted. > > .HP > > .B write_attributes > > .RB ( A ): > > Change the times associated with a file or directory to an arbitrary value. > > This permission is always implicitly

Re: richacl(7) man page review comments

On Sun, Feb 07, 2016 at 05:35:46PM +0100, Michael Kerrisk (man-pages) wrote: > > This permission is always implicitly granted. > > .HP > > .B write_attributes > > .RB ( A ): > > Change the times associated with a file or directory to an arbitrary value. > > This permission is always implicitly

richacl(7) man page review comments

Hi Andreas, I'll probably have quite a few more comments on this page as I get to understand RichACLs better. Here's some comments from an initial reading. So, an initial comment. It seems to me to that this page (but not setrichacl(1) and getrichacl(1)) should ultimately land in man-pages (just

richacl(7) man page review comments

Hi Andreas, I'll probably have quite a few more comments on this page as I get to understand RichACLs better. Here's some comments from an initial reading. So, an initial comment. It seems to me to that this page (but not setrichacl(1) and getrichacl(1)) should ultimately land in man-pages (just