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.
