On 4/27/21 8:33 PM, Khem Raj wrote:
On Tue, Apr 27, 2021 at 3:34 PM Konstantin Aladyshev
<email@example.com <mailto:firstname.lastname@example.org>> wrote:
I've added `IMAGE_INSTALL += "findutils"` to my `conf/local.conf`
file, and it seems like it was enough. There weren't any build
Should the AppArmor recipe be upgraded in some way to indicate that it
needs a full-featured findutils package instead of a busybox one?
I think it will be useful to dig a bit further and find out what
option does it need from findutils package sometimes this could be
solved by using compatible options etc
If we find out that it has hard dependency on findutils then it should
be added to apparmor recipe RDEPENDS
You are using systemd.
There is a comment regarding coreutils and findutils
|# Add coreutils and findutils only if sysvinit scripts are in use
On Mon, Apr 26, 2021 at 5:08 PM Quentin Schulz
> Hi Konstantin,
> On Mon, Apr 26, 2021 at 01:45:30PM +0300, Konstantin Aladyshev
> > I'm using the OpenBMC system
> > I've tried to enable AppArmor functionality from the
> > layer.
> > To achieve this I've added these strings to my local.conf file:
> > DISTRO_FEATURES_append = " apparmor"
> > IMAGE_INSTALL += "apparmor"
> > The AppArmor functionality was installed to my image, but
> > unfortunately I've come to this issue:
> > kernel: AppArmor: AppArmor initialized
> > kernel: AppArmor: AppArmor Filesystem Enabled
> > kernel: AppArmor: AppArmor sha1 policy hashing enabled
> > systemd: systemd 247.3+ running in system mode. (+PAM -AUDIT
> > -SELINUX -IMA -APPARMOR -SMACK +SYSVINIT -UTMP -LIBCRYPTSETUP
> > -GNUTLS -ACL +XZ -LZ4 -ZSTD -SECCOMP +BLKID -ELFUTILS +KMOD
> > -PCRE2 default-hierarchy=hybrid)
> > systemd: Starting AppArmor initialization...
> > apparmor: Starting AppArmor profiles
> > apparmor: xargs: invalid option -- 'd'
> Busybox implementation of xargs does not support specifying a
> I suggest you to install the full-featured xargs which is
> the findutils recipe.
> You probably need to disable xargs Busybox implementation otherwise
> there'll be a conflict (you'll know, Yocto won't create the image).