| 1 |
Mike Frysinger posted on Fri, 25 Jan 2013 18:51:44 -0500 as excerpted: |
| 2 |
|
| 3 |
> else |
| 4 |
> local fstype=$(stat -f -c %T "${file}") |
| 5 |
> ewarn "Could not set caps on '${file}' due to missing filesystem support." |
| 6 |
> ewarn "Make sure you enable XATTR support for '${fstype}' in your kernel." |
| 7 |
> fi |
| 8 |
|
| 9 |
This needs a bit more information, please. |
| 10 |
I had XATTR support enabled, but it wasn't enough. |
| 11 |
|
| 12 |
For at least reiserfs, and presumably for ext4, since it has |
| 13 |
similar kconfig options, *_FS_XATTR isn't enough, |
| 14 |
*_FS_SECURITY must be enabled as well. |
| 15 |
|
| 16 |
(*_FSPOSIX_ACL did NOT need to be enabled, however.) |
| 17 |
|
| 18 |
So: |
| 19 |
|
| 20 |
ewarn "Make sure you enable XATTR and SECURITY attribute |
| 21 |
support for ${fstype} in your kernel." |
| 22 |
|
| 23 |
Unfortunately, kernel-help for *_FS_SECURITY implies that it only needs |
| 24 |
to be enabled for SELinux or the like, recommending that it be disabled |
| 25 |
if you're not running such modules. Is it worth filing an upstream |
| 26 |
mainline kernel bug on that as well, suggesting that it mention file-caps |
| 27 |
as well? |
| 28 |
|
| 29 |
-- |
| 30 |
Duncan - List replies preferred. No HTML msgs. |
| 31 |
"Every nonfree program has a lord, a master -- |
| 32 |
and if you use the program, he is your master." Richard Stallman |
Archives