[Buildroot] [PATCH 1/3] package/systemd: add option to enable SysV and utmp compatibility

Norbert Lange nolange79 at gmail.com
Sat Jul 11 11:27:52 UTC 2020


Norbert Lange <nolange79 at gmail.com> schrieb am Sa., 11. Juli 2020, 13:25:

>
>
>
> Thomas Petazzoni <thomas.petazzoni at bootlin.com> schrieb am Sa., 11. Juli
> 2020, 12:56:
>
>> On Sat, 11 Jul 2020 01:41:47 +0200
>> Norbert Lange <nolange79 at gmail.com> wrote:
>>
>> > diff --git a/package/systemd/systemd.mk b/package/systemd/systemd.mk
>> > index 05c1d1ff9a..05d8cb4934 100644
>> > --- a/package/systemd/systemd.mk
>> > +++ b/package/systemd/systemd.mk
>> > @@ -199,6 +199,18 @@ else
>> >  SYSTEMD_CONF_OPTS += -Dpcre2=false
>> >  endif
>> >
>> > +ifeq ($(BR2_PACKAGE_SYSTEMD_SYSV),y)
>> > +SYSTEMD_CONF_OPTS += -Dsysvinit-path=/etc/init.d
>> -Dsysvrcnd-path=/etc/rc.d
>>
>> We don't have any /etc/rc.d directory in Buildroot, and when systemd is
>> selected as the init system, we don't install init scripts in
>> /etc/init.d. So I'm wondering what is the use case for this option ?
>>
>
> Removing *support for unit scripts*. those scripts, as you said, don't
> exist.
> That support comes in form of several services to parse and convert those
> script, some code and daemon to allow systemd to communicate with some sysv
> tools (initctl, runlevels et all).
>
> Norbert
>
>
>> Best regards,
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
>
>
Hmm, maybe I misunderstood. There is no Boolean to enable this support, but
it is disabled when those paths are empty.

I enable these paths by setting the defaults.
If you want to argue, that we should just disabled the compatibility
without option, I won't object

Norbert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200711/c70a8667/attachment-0002.html>


More information about the buildroot mailing list