Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1340553
| From | Andreas Gruenbacher <agruenba@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: richacl(7) man page review comments |
| Date | 2016-02-23 12:20 +0100 |
| Message-ID | <r5jay-4vR-3@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <r2cyC-8oe-15@gated-at.bofh.it> <r4iJz-8kt-5@gated-at.bofh.it> <r4K38-3NN-11@gated-at.bofh.it> <r4ZYe-7bh-11@gated-at.bofh.it> <r5iRe-45N-45@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Feb 23, 2016 at 11:58 AM, Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> 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 right option? You'd create a test filesystem with the appropriate feature flag set (mkfs.ext4 -O richacl2 / mkfs.xfs -m richacl=1), RichACLs are not enabled by mount options anymore. This will obviously require versions of e2fsprogs / xfsprogs that understand the feature. If you want coreutils support which isn't strictly necessary, you'll need the patched version too. Other than that, it's really simple. Andreas
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: richacl(7) man page review comments "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> - 2016-02-23 12:00 +0100
Re: richacl(7) man page review comments Andreas Gruenbacher <agruenba@redhat.com> - 2016-02-23 12:20 +0100
Re: richacl(7) man page review comments Andreas Gruenbacher <agruenba@redhat.com> - 2016-02-23 16:10 +0100
Re: richacl(7) man page review comments Andreas Gruenbacher <agruenba@redhat.com> - 2016-02-23 20:10 +0100
csiph-web