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

Norbert Lange nolange79 at gmail.com
Sun Jul 12 22:41:35 UTC 2020


Am Sa., 11. Juli 2020 um 15:14 Uhr schrieb Thomas Petazzoni
<thomas.petazzoni at bootlin.com>:
>
> On Sat, 11 Jul 2020 13:25:08 +0200
> Norbert Lange <nolange79 at gmail.com> wrote:
>
> > > > +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.
>
> Yes, but your patch also keeps support for init scripts enabled when
> BR2_PACKAGE_SYSTEMD_SYSV=y, and I don't understand what is the use case.
>
> When systemd is enabled, there will be nothing in /etc/init.d, because
> Buildroot only executes the <pkg>_INIT_SYSV commands (that install init
> scripts) when the init system is Busybox or SysVinit.
>
> Or do you want to support use cases where some users may install their
> own init scripts in /etc/init.d, but are using systemd ?

I accounted for such usecases, because I thought that's expected with buildroot.
No trouble removing the option from my side.
This goes for utmp aswell (not sure Id want logged in users exposed in
a file amyway)

Norbert



More information about the buildroot mailing list