NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
1175f46044
kumquat-buildroot/package/openrc/openrc.mk

97 lines
2.9 KiB
Makefile
Raw Normal View History

package/openrc: new package This adds openrc init system package. This performs default openrc installation with openrc-init that acts as pid1. MKPKGCONFIG=no: openrc does not use pkg-config per se, if MKPKGCONFIG is enabled, it will just install *.pc files on rootfs for other programs to find librc and libeinfo. These libs expose C api to control openrc (al rc-* functions use it). From the looks of it, these libs would be usefull if user wanted to write his own programs to manage services, and vast majority of people using openrc won't need it. Also, that's the reason why there is not INSTALL_STAGING=yes. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-12 21:55:38 +02:00
################################################################################
#
# openrc
#
################################################################################
package/openrc: bump to version 0.42.1 Add a patch to prevent starting agetty on tty[1-6]. Buildroot starts a single getty, according to the system configuration. Also tty[1-6] may not even exist (e.g. embedded devices with serial consoles only). Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Carlos Santos <unixmania@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-03-01 16:17:45 +01:00
OPENRC_VERSION = 0.42.1
package/openrc: new package This adds openrc init system package. This performs default openrc installation with openrc-init that acts as pid1. MKPKGCONFIG=no: openrc does not use pkg-config per se, if MKPKGCONFIG is enabled, it will just install *.pc files on rootfs for other programs to find librc and libeinfo. These libs expose C api to control openrc (al rc-* functions use it). From the looks of it, these libs would be usefull if user wanted to write his own programs to manage services, and vast majority of people using openrc won't need it. Also, that's the reason why there is not INSTALL_STAGING=yes. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-12 21:55:38 +02:00
OPENRC_SITE = $(call github,OpenRC,openrc,$(OPENRC_VERSION))
OPENRC_LICENSE = BSD-2-Clause
OPENRC_LICENSE_FILES = LICENSE
package: drop _CPE_ID_VALID, use _CPE_ID_VENDOR FOO_CPE_ID_VALID really ought to be an internal implementaion detail. Packages that really want to trigger their CPE defintitions really should set one of the actual variables to a meaningful value. There are two CPE-related variables that we could chose to set to replace FOO_CPE_ID_VALID: FOO_CPE_ID_VENDOR and FOO_CPE_ID_PRODUCT. Between those two, _VENDOR more often diverges from the default than _PRODUCT does, so that's what we use. ---8<------8<------8<------8<------8<--- #!/bin/bash # Replace FOO_CPE_ID_VALID = YES with FOO_CPE_ID_VENDOR = foo_project for i in $(git grep -l -E '[^)]_CPE_ID_VALID = YES' package support); do pkg="$(basename "${i%/*}")" sed -r -i -e "s/_CPE_ID_VALID = YES/_CPE_ID_VENDOR = ${pkg}_project/" "${i}" done ---8<------8<------8<------8<------8<--- Reported-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Matthew Weber <matthew.weber@rockwellcollins.com> Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com> [Peter: update cpe-test comment to reflect pkg3 change] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-03-05 23:27:44 +01:00
OPENRC_CPE_ID_VENDOR = openrc_project
package/openrc: new package This adds openrc init system package. This performs default openrc installation with openrc-init that acts as pid1. MKPKGCONFIG=no: openrc does not use pkg-config per se, if MKPKGCONFIG is enabled, it will just install *.pc files on rootfs for other programs to find librc and libeinfo. These libs expose C api to control openrc (al rc-* functions use it). From the looks of it, these libs would be usefull if user wanted to write his own programs to manage services, and vast majority of people using openrc won't need it. Also, that's the reason why there is not INSTALL_STAGING=yes. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-12 21:55:38 +02:00
package/openrc: add upstream security fix for CVE-2018-21269 Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-11-23 20:17:29 +01:00
# 0007-checkpath-fix-CVE-2018-21269.patch
OPENRC_IGNORE_CVES += CVE-2018-21269
package/openrc: new package This adds openrc init system package. This performs default openrc installation with openrc-init that acts as pid1. MKPKGCONFIG=no: openrc does not use pkg-config per se, if MKPKGCONFIG is enabled, it will just install *.pc files on rootfs for other programs to find librc and libeinfo. These libs expose C api to control openrc (al rc-* functions use it). From the looks of it, these libs would be usefull if user wanted to write his own programs to manage services, and vast majority of people using openrc won't need it. Also, that's the reason why there is not INSTALL_STAGING=yes. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-12 21:55:38 +02:00
OPENRC_DEPENDENCIES = ncurses
# set LIBNAME so openrc puts files in proper directories and sets proper
# paths in installed files. Since in buildroot /lib64 and /lib32 always
# points to /lib, it's safe to hardcode it to "lib"
OPENRC_MAKE_OPTS = \
LIBNAME=lib \
LIBEXECDIR=/usr/libexec/rc \
MKPKGCONFIG=no \
MKSYSVINIT=yes \
BRANDING="Buildroot $(BR2_VERSION_FULL)" \
CC=$(TARGET_CC)
ifeq ($(BR2_SHARED_LIBS),y)
OPENRC_MAKE_OPTS += MKSTATICLIBS=no
else
OPENRC_MAKE_OPTS += MKSTATICLIBS=yes
endif
package/openrc: enable selinux support when libselinux is enabled OpenRC suports SELinux, so there is no reason to forcibly disable it. Notice this only allows OpenRC to perform the initial policy load and set the enforcing mode. In order really use SELinux it's also necessary to select refpolicy, which provides a policy, and policycoreutils, which provides restorecon and other SELinux utilities. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Carlos Santos <unixmania@gmail.com> Tested-by: Carlos Santos <unixmania@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-04-16 05:21:37 +02:00
ifeq ($(BR2_PACKAGE_LIBSELINUX),y)
OPENRC_MAKE_OPTS += MKSELINUX=yes
OPENRC_DEPENDENCIES += libselinux
else
OPENRC_MAKE_OPTS += MKSELINUX=no
endif
package/openrc: new package This adds openrc init system package. This performs default openrc installation with openrc-init that acts as pid1. MKPKGCONFIG=no: openrc does not use pkg-config per se, if MKPKGCONFIG is enabled, it will just install *.pc files on rootfs for other programs to find librc and libeinfo. These libs expose C api to control openrc (al rc-* functions use it). From the looks of it, these libs would be usefull if user wanted to write his own programs to manage services, and vast majority of people using openrc won't need it. Also, that's the reason why there is not INSTALL_STAGING=yes. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-12 21:55:38 +02:00
define OPENRC_BUILD_CMDS
$(MAKE) $(OPENRC_MAKE_OPTS) -C $(@D)
endef
define OPENRC_INSTALL_TARGET_CMDS
$(MAKE) $(OPENRC_MAKE_OPTS) DESTDIR=$(TARGET_DIR) -C $(@D) install
package/openrc: install sysv-rcs file package/openrc has the file sysv-rcs which starts sysvinit services not written for openrc. However, currently it is not installed to the target. Install this file to $(TARGET_DIR)/etc/init.d during the target_install step. Signed-off-by: Adam Duskett <aduskett@greenlots.com> [yann.morin.1998@free.fr: use full-path for destination, not just dir] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2019-12-19 20:01:35 +01:00
$(INSTALL) -D -m 0755 $(OPENRC_PKGDIR)/sysv-rcs \
$(TARGET_DIR)/etc/init.d/sysv-rcs
package/openrc: new package This adds openrc init system package. This performs default openrc installation with openrc-init that acts as pid1. MKPKGCONFIG=no: openrc does not use pkg-config per se, if MKPKGCONFIG is enabled, it will just install *.pc files on rootfs for other programs to find librc and libeinfo. These libs expose C api to control openrc (al rc-* functions use it). From the looks of it, these libs would be usefull if user wanted to write his own programs to manage services, and vast majority of people using openrc won't need it. Also, that's the reason why there is not INSTALL_STAGING=yes. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-12 21:55:38 +02:00
endef
package/openrc: remove keymaps units if kbd package is not selected keymaps and save-keymaps require kbd_mode and dumpkeys, respectively, so remove them if the kbd package is not selected (e.g. devices with serial console, only). Signed-off-by: Carlos Santos <unixmania@gmail.com> Tested-by: Adam Duskett <aduskett@gmail.com> [yann.morin.1998@free.fr: - expand to three commands to match the existing hook ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-29 19:26:21 +01:00
ifeq ($(BR2_PACKAGE_KBD),)
# keymaps and save-keymaps require kbd_mode and dumpkeys, respectively, so
# remove them if the kbd package is not selected (e.g. devices with serial
# console, only).
define OPENRC_NO_KBD
$(RM) $(TARGET_DIR)/etc/runlevels/boot/{keymaps,save-keymaps}
$(RM) $(TARGET_DIR)/etc/init.d/{keymaps,save-keymaps}
$(RM) $(TARGET_DIR)/etc/conf.d/keymaps
endef
OPENRC_POST_INSTALL_TARGET_HOOKS += OPENRC_NO_KBD
endif
package/netifrc: new package netifrc entirely replaces openrc's basic network management. As such, it conflicts with the network services installed by openrc, so we remove them from openrc when netifrc is enabled. Currently, we only catter tfor the loopback interface, but we prepare for also handling the DHCP interface, to come in a latter patch. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> [yann.morin.1998@free.fr: - remove openrc files within the openrc package itself - as it's a generic-package, no need to use post-install hooks - use description from the homepage in the help text - check-package fixes - rename package ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> [Thomas: - pass UDEVDIR to install udev rules at the correct location] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-04 14:14:18 +02:00
ifeq ($(BR2_PACKAGE_NETIFRC),y)
# netifrc replaces network, staticroute and loopback services which are
# installed by openrc
define OPENRC_NO_NET
$(RM) $(TARGET_DIR)/etc/runlevels/boot/{network,staticroute,loopback}
$(RM) $(TARGET_DIR)/etc/init.d/{network,staticroute,loopback}
$(RM) $(TARGET_DIR)/etc/conf.d/{network,staticroute,loopback}
endef
package/openrc: fix post-install-target addition OPENRC_POST_TARGET_INSTALL_HOOKS -> OPENRC_POST_INSTALL_TARGET_HOOKS Signed-off-by: Carlos Santos <unixmania@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-29 19:18:07 +01:00
OPENRC_POST_INSTALL_TARGET_HOOKS += OPENRC_NO_NET
package/netifrc: new package netifrc entirely replaces openrc's basic network management. As such, it conflicts with the network services installed by openrc, so we remove them from openrc when netifrc is enabled. Currently, we only catter tfor the loopback interface, but we prepare for also handling the DHCP interface, to come in a latter patch. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> [yann.morin.1998@free.fr: - remove openrc files within the openrc package itself - as it's a generic-package, no need to use post-install hooks - use description from the homepage in the help text - check-package fixes - rename package ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> [Thomas: - pass UDEVDIR to install udev rules at the correct location] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-04 14:14:18 +02:00
endif
package/openrc: new package This adds openrc init system package. This performs default openrc installation with openrc-init that acts as pid1. MKPKGCONFIG=no: openrc does not use pkg-config per se, if MKPKGCONFIG is enabled, it will just install *.pc files on rootfs for other programs to find librc and libeinfo. These libs expose C api to control openrc (al rc-* functions use it). From the looks of it, these libs would be usefull if user wanted to write his own programs to manage services, and vast majority of people using openrc won't need it. Also, that's the reason why there is not INSTALL_STAGING=yes. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-12 21:55:38 +02:00
define OPENRC_REMOVE_UNNEEDED
$(RM) -r $(TARGET_DIR)/usr/share/openrc
endef
OPENRC_TARGET_FINALIZE_HOOKS += OPENRC_REMOVE_UNNEEDED
package/openrc: add support for spawning getty We install a template getty service, and we 'instantiate' it in the default runlevel, using the configured tty. Ideally, packages that provide a getty program would be responsible for installing the corresponding service file. However, to keep consistency with the existing init systems (busybox, systemd, and sysv), so we do provide it from the openrc package itself. OpenRC only acts on the files in a runlevel sub-directory, but the documentation [0] actually suggests that the instance symlink be done in init.d, and then again symlinked into the actual runlevel sub-directory. So, we abide by the rules. Also, to be noted, the getty service file is installed without ensuring that a getty command is available. This again is not unlike other init systems, sysvinit and busybox, which behave the same. [0] https://wiki.gentoo.org/wiki/OpenRC Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> [yann.morin.1998@free.fr: - move getty template to openrc package (Thomas) - fix namespace of the vaiables (Thomas) - simplify creation of the defaults file - rewrite commit log ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-04 14:14:17 +02:00
ifeq ($(BR2_TARGET_GENERIC_GETTY),y)
package/openrc: drop custom getty service In Buildroot getty is provided by BusyBox or util-linux (agetty). Both create a /sbin/getty symlink pointing to the actual program, so make the agetty service use that path instead of /sbin/agetty. Also start agetty after all other services, to prevent mixing startup messages with the getty prompt on devices with a single serial console, as the custom unit we're dopping was doing already. This allows us to drop the custom getty service, which causes an error message from openrc 0.42.1 (in a forthcoming patch): Error: getty is the name of a real and virtual service. The patches are required because it's not possible to override the command or startup order by means of a configuration file. Anyway it's still better to patch something maintained upstream than depending on a custom piece that may easily become obsolete. Signed-off-by: Carlos Santos <unixmania@gmail.com> [yann.morin.1998@free.fr: - expand commit log to explain why we ve 'after *' in the same patch ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-03-01 16:17:44 +01:00
OPENRC_GETTY_SVCNAME = agetty.$(SYSTEM_GETTY_PORT)
package/openrc: add support for spawning getty We install a template getty service, and we 'instantiate' it in the default runlevel, using the configured tty. Ideally, packages that provide a getty program would be responsible for installing the corresponding service file. However, to keep consistency with the existing init systems (busybox, systemd, and sysv), so we do provide it from the openrc package itself. OpenRC only acts on the files in a runlevel sub-directory, but the documentation [0] actually suggests that the instance symlink be done in init.d, and then again symlinked into the actual runlevel sub-directory. So, we abide by the rules. Also, to be noted, the getty service file is installed without ensuring that a getty command is available. This again is not unlike other init systems, sysvinit and busybox, which behave the same. [0] https://wiki.gentoo.org/wiki/OpenRC Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> [yann.morin.1998@free.fr: - move getty template to openrc package (Thomas) - fix namespace of the vaiables (Thomas) - simplify creation of the defaults file - rewrite commit log ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-04 14:14:17 +02:00
OPENRC_GETTY_CONF_D = $(TARGET_DIR)/etc/conf.d/$(OPENRC_GETTY_SVCNAME)
define OPENRC_SET_GETTY
{ \
echo "baud=\"$(SYSTEM_GETTY_BAUDRATE)\""; \
echo "term_type=\"$(SYSTEM_GETTY_TERM)\"" ; \
package/openrc: drop custom getty service In Buildroot getty is provided by BusyBox or util-linux (agetty). Both create a /sbin/getty symlink pointing to the actual program, so make the agetty service use that path instead of /sbin/agetty. Also start agetty after all other services, to prevent mixing startup messages with the getty prompt on devices with a single serial console, as the custom unit we're dopping was doing already. This allows us to drop the custom getty service, which causes an error message from openrc 0.42.1 (in a forthcoming patch): Error: getty is the name of a real and virtual service. The patches are required because it's not possible to override the command or startup order by means of a configuration file. Anyway it's still better to patch something maintained upstream than depending on a custom piece that may easily become obsolete. Signed-off-by: Carlos Santos <unixmania@gmail.com> [yann.morin.1998@free.fr: - expand commit log to explain why we ve 'after *' in the same patch ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-03-01 16:17:44 +01:00
echo "agetty_options=\"-L $(SYSTEM_GETTY_OPTIONS)\""; \
package/openrc: add support for spawning getty We install a template getty service, and we 'instantiate' it in the default runlevel, using the configured tty. Ideally, packages that provide a getty program would be responsible for installing the corresponding service file. However, to keep consistency with the existing init systems (busybox, systemd, and sysv), so we do provide it from the openrc package itself. OpenRC only acts on the files in a runlevel sub-directory, but the documentation [0] actually suggests that the instance symlink be done in init.d, and then again symlinked into the actual runlevel sub-directory. So, we abide by the rules. Also, to be noted, the getty service file is installed without ensuring that a getty command is available. This again is not unlike other init systems, sysvinit and busybox, which behave the same. [0] https://wiki.gentoo.org/wiki/OpenRC Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> [yann.morin.1998@free.fr: - move getty template to openrc package (Thomas) - fix namespace of the vaiables (Thomas) - simplify creation of the defaults file - rewrite commit log ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-04 14:14:17 +02:00
} > $(OPENRC_GETTY_CONF_D)
package/openrc: drop custom getty service In Buildroot getty is provided by BusyBox or util-linux (agetty). Both create a /sbin/getty symlink pointing to the actual program, so make the agetty service use that path instead of /sbin/agetty. Also start agetty after all other services, to prevent mixing startup messages with the getty prompt on devices with a single serial console, as the custom unit we're dopping was doing already. This allows us to drop the custom getty service, which causes an error message from openrc 0.42.1 (in a forthcoming patch): Error: getty is the name of a real and virtual service. The patches are required because it's not possible to override the command or startup order by means of a configuration file. Anyway it's still better to patch something maintained upstream than depending on a custom piece that may easily become obsolete. Signed-off-by: Carlos Santos <unixmania@gmail.com> [yann.morin.1998@free.fr: - expand commit log to explain why we ve 'after *' in the same patch ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-03-01 16:17:44 +01:00
ln -sf agetty $(TARGET_DIR)/etc/init.d/$(OPENRC_GETTY_SVCNAME)
package/openrc: add support for spawning getty We install a template getty service, and we 'instantiate' it in the default runlevel, using the configured tty. Ideally, packages that provide a getty program would be responsible for installing the corresponding service file. However, to keep consistency with the existing init systems (busybox, systemd, and sysv), so we do provide it from the openrc package itself. OpenRC only acts on the files in a runlevel sub-directory, but the documentation [0] actually suggests that the instance symlink be done in init.d, and then again symlinked into the actual runlevel sub-directory. So, we abide by the rules. Also, to be noted, the getty service file is installed without ensuring that a getty command is available. This again is not unlike other init systems, sysvinit and busybox, which behave the same. [0] https://wiki.gentoo.org/wiki/OpenRC Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> [yann.morin.1998@free.fr: - move getty template to openrc package (Thomas) - fix namespace of the vaiables (Thomas) - simplify creation of the defaults file - rewrite commit log ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-04 14:14:17 +02:00
ln -sf /etc/init.d/$(OPENRC_GETTY_SVCNAME) \
$(TARGET_DIR)/etc/runlevels/default/$(OPENRC_GETTY_SVCNAME)
endef
OPENRC_TARGET_FINALIZE_HOOKS += OPENRC_SET_GETTY
endif # BR2_TARGET_GENERIC_GETTY
package/openrc: new package This adds openrc init system package. This performs default openrc installation with openrc-init that acts as pid1. MKPKGCONFIG=no: openrc does not use pkg-config per se, if MKPKGCONFIG is enabled, it will just install *.pc files on rootfs for other programs to find librc and libeinfo. These libs expose C api to control openrc (al rc-* functions use it). From the looks of it, these libs would be usefull if user wanted to write his own programs to manage services, and vast majority of people using openrc won't need it. Also, that's the reason why there is not INSTALL_STAGING=yes. Signed-off-by: Michał Łyszczek <michal.lyszczek@bofc.pl> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-12 21:55:38 +02:00
$(eval $(generic-package))
Reference in New Issue Copy Permalink