[oe] [meta-oe][RFC 00/27] systemd / initmanager rework

Otavio Salvador otavio at ossystems.com.br
Wed Feb 8 10:57:19 UTC 2012


On Tue, Feb 7, 2012 at 22:39, Joshua Lock <josh at linux.intel.com> wrote:
>
>  * The init system ought to be a DISTRO_FEATURE (as sysvinit ought to be
>> too
>> IMO)
>>
>
> I know there's some disagreement with the suggestion that the init system
> ought to be a DISTRO_FEATURE but my (admittedly uninformed) opinion is that
> I can't see how we can avoid it.
>
> It looks like systemd provides various interfaces and API's that packages
> may or may not use and as more packages adopt these we're going to need to
> be able to enable/disable more than just some unit files/scripts for init
> support.


After looking more closely to the polkit issue it seems it is not easy to
avoid, indeed.


>  * I'd like to see sysvinit packages splitted onto ${PN}-sysvinit as well
>>
>
> Agreed. Do we need to think about the case where a systemd based system
> might *need* an initscript (no units available) vs. when the -sysvinit and
> -systemd packages both provide similar functionality?
>
> Would it be desirable for the rootfs generation logic to be able to fall
> back to an alternative "initscript" provider?


Yes for both. sysvinit, for now, ought to be the fallback and in case we
have any sysvinit we need compat-units too.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



More information about the Openembedded-devel mailing list