Re: [gentoo-user] XATTR missing from ext4?

2017-07-01 Thread Mick
On Saturday 01 Jul 2017 12:18:05 Rasmus Thomsen wrote:
> Hello,
> 
> > * Could not set caps on "/bin/ping6" due to missing filesystem support:*
> > * enable XATTR support for "ext2/ext3" in your kernel (if configurable)*
> > * mount the fs with the user_xattr option (if not the default)
> > * enable the relevant FS_SECURITY option (if configurable)
> 
> do as Portage advises you and enable CONFIG_EXT4_FS_SECURITY. You don't need
> any additional configs in your fstab, xattr are both enabled by default
> ( if compiled into the kernel ). Regards,
> Rasmus

Oops!  I thought I had missed something and it was right in front of my eyes!  
Thank you for point this out.  :-)
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] XATTR missing from ext4?

2017-07-01 Thread Rasmus Thomsen
Hello,
> * Could not set caps on "/bin/ping6" due to missing filesystem support:*
> * enable XATTR support for "ext2/ext3" in your kernel (if configurable)*
> * mount the fs with the user_xattr option (if not the default)
> * enable the relevant FS_SECURITY option (if configurable)
do as Portage advises you and enable CONFIG_EXT4_FS_SECURITY. You don't need 
any additional configs in your fstab, xattr are both enabled by default ( 
if compiled into the kernel ).
Regards,
Rasmus

Re: [gentoo-user] XATTR missing from ext4?

2017-07-01 Thread Mick
On Saturday 01 Jul 2017 14:10:04 David W Noon wrote:
> On Sat, 01 Jul 2017 12:49:54 +0100, Mick (michaelkintz...@gmail.com)
> wrote about "[gentoo-user] XATTR missing from ext4?" (in
> <10201199.nOKg2Blue2@dell_xps>):
> 
> [snip]
> 
> > and mounted like so:
> > 
> > /dev/sda3 on / type ext4 (rw,noatime,data=ordered)
> 
> For full extended attribute support the mount options should include
> both acl and user_xattr, as these enable the security namespace and user
> namespace respectively.

Hmm ... I set up in fstab:

/dev/sda3  /ext4  noatime,acl,user_xattr   0 1

rebooted, same problem.  What am I missing?
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] XATTR missing from ext4?

2017-07-01 Thread David W Noon
On Sat, 01 Jul 2017 12:49:54 +0100, Mick (michaelkintz...@gmail.com)
wrote about "[gentoo-user] XATTR missing from ext4?" (in
<10201199.nOKg2Blue2@dell_xps>):

[snip]
> and mounted like so:
> 
> /dev/sda3 on / type ext4 (rw,noatime,data=ordered)

For full extended attribute support the mount options should include
both acl and user_xattr, as these enable the security namespace and user
namespace respectively.
-- 
Regards,

Dave  [RLU #314465]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
dwn...@ntlworld.com (David W Noon)
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

 




signature.asc
Description: OpenPGP digital signature


[gentoo-user] XATTR missing from ext4?

2017-07-01 Thread Mick
I updated an old PC which has / on ext4 and noticed this when ping was 
installed:

--- replaced obj /bin/ping
--- replaced dir /bin
>>> Regenerating /etc/ld.so.cache...
>>> Original instance of package unmerged safely.
 * Could not set caps on '/bin/ping' due to missing filesystem support:
 * * enable XATTR support for 'ext2/ext3' in your kernel (if configurable)
 * * mount the fs with the user_xattr option (if not the default)
 * * enable the relevant FS_SECURITY option (if configurable)
 * Could not set caps on '/bin/ping6' due to missing filesystem support:
 * * enable XATTR support for 'ext2/ext3' in your kernel (if configurable)
 * * mount the fs with the user_xattr option (if not the default)
 * * enable the relevant FS_SECURITY option (if configurable)
 * Could not set caps on '/bin/arping' due to missing filesystem support:
 * * enable XATTR support for 'ext2/ext3' in your kernel (if configurable)
 * * mount the fs with the user_xattr option (if not the default)
 * * enable the relevant FS_SECURITY option (if configurable)
>>> net-misc/iputils-20151218 merged.

The ext filesystems are configured in the kernel like so:

# egrep EXT[[:digit:]] /usr/src/linux/.config
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_POSIX_ACL=y
# CONFIG_EXT4_FS_SECURITY is not set
CONFIG_EXT4_ENCRYPTION=y
CONFIG_EXT4_FS_ENCRYPTION=y
# CONFIG_EXT4_DEBUG is not set

and mounted like so:

/dev/sda3 on / type ext4 (rw,noatime,data=ordered)

Should this be different so the ewarning does not happen?
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.