Ross Burton <[email protected]>
writes:
> If binfmt_misc was compiled as a module but isn't installed then
> systemd-binfmt
> will put an automounter on /proc/sys/fs/binfmt_misc and when it attempts to
> automount (e.g. when df is called) it can't find support for the filesystem,
> and
> throws an error.
>
> As binfmt_misc isn't commonly used, split this helper into it's own package,
> add
> a dependency on kernel-module-binfmt-misc, and ensure the service gets started
> when it's installed.
> ...
> + Conflicts=shutdown.target
> ...
> +SYSTEMD_SERVICE_${PN}-binfmt = "systemd-binfmt.service"
This seems to trigger some strange behavior in the systemd.bbclass which
adds 'Conflicts' (and 'Also') to the FILES list. E.g. after this, the
'shutdown.target' file is moved into the 'systemd-binfmt' package. This
in turn causes 'systemd-binfmt' becoming a rdependency of 'systemd' due
to dead symlinks.
I would avoid the 'inherit systemd' in the systemd recipe and package
the files and .target.wants/ symlinks as-is in ${systemd_unitdir}.
Enrico
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
