systemd/udev/eudev polishing
cover systemd/udev/eudev polishing
This patch series contains enhancements for systemd, udev and eudev, intended for next branch:
- use of proper virtual package infrastructure (suggested by Arnout).
- enable required kernel features for systemd (suggested by SamuelM).
Best regards,
ELB
Eric Le Bihan (2):
udev: update udev to new virtual package infra.
systemd: enable required kernel features.
linux/linux.mk | 6 +++++- package/eudev/Config.in | 3 +++ package/systemd/Config.in | 15 +++++++++++++-- package/udev/Config.in | 8 ++++---- package/udev/udev.mk | 11 ++--------- 5 files changed, 27 insertions(+), 16 deletions(-)
Signature · 1 line
1.7.9.5
PATCH 1/2 udev: update udev to new virtual package infra.
The udev virtual package and its current providers (eudev and systemd) have been updated to use the latest version of virtual package infrastructure.
A provider should now select BR2_PACKAGE_HAS_UDEV and well as set a value for BR2_PACKAGE_PROVIDES_UDEV.
--- package/eudev/Config.in | 3 +++ package/systemd/Config.in | 3 +++ package/udev/Config.in | 8 ++++---- package/udev/udev.mk | 11 ++--------- 4 files changed, 12 insertions(+), 13 deletions(-)
package/eudev/Config.in +3 -0
@@ -21,6 +21,9 @@ config BR2_PACKAGE_EUDEV if BR2_PACKAGE_EUDEV +config BR2_PACKAGE_PROVIDES_UDEV + default "eudev" + config BR2_PACKAGE_EUDEV_RULES_GEN bool "enable rules generator" help
package/systemd/Config.in +3 -0
@@ -40,6 +40,9 @@ config BR2_PACKAGE_SYSTEMD if BR2_PACKAGE_SYSTEMD +config BR2_PACKAGE_PROVIDES_UDEV + default "systemd" + config BR2_PACKAGE_SYSTEMD_ALL_EXTRAS bool "enable all extras" select BR2_PACKAGE_XZ
package/udev/Config.in +4 -4
@@ -1,6 +1,6 @@ config BR2_PACKAGE_HAS_UDEV bool - help - udev is now a virtual package. - Packages requiring udevd at run time or libudev/gudev at build time - should select it. + +config BR2_PACKAGE_PROVIDES_UDEV + depends on BR2_PACKAGE_HAS_UDEV + string
package/udev/udev.mk +2 -9
@@ -5,18 +5,11 @@ ################################################################################ UDEV_SOURCE = - -ifeq ($(BR2_PACKAGE_EUDEV),y) -UDEV_DEPENDENCIES += eudev -endif - -ifeq ($(BR2_PACKAGE_SYSTEMD),y) -UDEV_DEPENDENCIES += systemd -endif +UDEV_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_UDEV)) ifeq ($(UDEV_DEPENDENCIES),) define UDEV_CONFIGURE_CMDS - echo "No Udev implementation selected. Configuration error." + $(error No Udev implementation selected. Configuration error) exit 1 endef endif
Signature · 1 line
1.7.9.5
PATCH 1/2 udev: update udev to new virtual package infra.
Dear Eric Le Bihan,
Quoted 6 lines · Eric Le Bihan
package/udev/udev.mk +0
-6-ifeq ($(BR2_PACKAGE_EUDEV),y) -UDEV_DEPENDENCIES += eudev -endif - -ifeq ($(BR2_PACKAGE_SYSTEMD),y) -UDEV_DEPENDENCIES += systemd
package/udev/udev.mk line 15
Quoted 10 lines
package/udev/udev.mk +2
-2-endif +UDEV_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_UDEV)) ifeq ($(UDEV_DEPENDENCIES),) define UDEV_CONFIGURE_CMDS - echo "No Udev implementation selected. Configuration error." + $(error No Udev implementation selected. Configuration error) exit 1 endef endif
Why are we doing this check in UDEV_CONFIGURE_CMDS ? I believe we can simply do:
ifeq ($(<foo>_DEPENDENCIES),)
$(error No <foo> implementation selected)
endif
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/2 udev: update udev to new virtual package infra.
Hi!
Quoted 24 lines · Thomas Petazzoni
Dear Eric Le Bihan,
Quoted 6 lines · Eric Le Bihan
package/udev/udev.mk +0
-6-ifeq ($(BR2_PACKAGE_EUDEV),y) -UDEV_DEPENDENCIES += eudev -endif - -ifeq ($(BR2_PACKAGE_SYSTEMD),y) -UDEV_DEPENDENCIES += systemdpackage/udev/udev.mk line 15
Quoted 10 lines
package/udev/udev.mk +2
-2-endif +UDEV_DEPENDENCIES = $(call qstrip,$(BR2_PACKAGE_PROVIDES_UDEV)) ifeq ($(UDEV_DEPENDENCIES),) define UDEV_CONFIGURE_CMDS - echo "No Udev implementation selected. Configuration error." + $(error No Udev implementation selected. Configuration error) exit 1 endef endifWhy are we doing this check in
UDEV_CONFIGURE_CMDS? I believe we can simply do:
Quoted 3 lines
ifeq ($(<foo>_DEPENDENCIES),)
$(error No <foo> implementation selected)
endif
I followed the example in package/opengl/libegl/libegl.mk, but I mixed the Makefile control function $(error text...) and some Shell script without thinking...
I will revert it to the pure shell version to be coherent.
With the <foo>_CONFIGURE_CMDS method, we go through all the dummy steps, and this is very verbose:
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
udev undefined Extracting
udev undefined Patching
udev undefined Configuring
echo "No Udev implementation selected. Configuration error."
No Udev implementation selected. Configuration error.
exit 1
make: *** [/home/eric/build/elebihan/demo-systemd/arm/build/udev-undefined/.stamp_configured] Erreur 1
With the pure Makefile version, the error message is clearer:
package/udev/udev.mk:11: *** No Udev implementation selected. Configuration error. Stop.
I find it better. If it suits everyone, I can propose a patch to convert all the virtual packages to it and re-send my tutorial patch about virtual package.
Best regards,
ELB
PATCH 1/2 udev: update udev to new virtual package infra.
Dear Eric Le Bihan,
Quoted 11 lines · Eric Le Bihan
Quoted 6 lines
Why are we doing this check in
UDEV_CONFIGURE_CMDS? I believe we can simply do:ifeq ($(<foo>_DEPENDENCIES),)
$(error No <foo> implementation selected)
endifI followed the example in
package/opengl/libegl/libegl.mk, but I mixed theMakefilecontrol function $(error text...) and some Shell script without thinking...I will revert it to the pure shell version to be coherent.
I guess you mean "to the pure make version", according to what you say below, right?
Quoted 6 lines
With the <foo>_CONFIGURE_CMDS method, we go through all the dummy steps, and this is very verbose:
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
udev undefined Extracting
udev undefined Patching
udev undefined Configuring
Quoted 8 lines
echo "No Udev implementation selected. Configuration error."
No Udev implementation selected. Configuration error.
exit 1
make: *** [/home/eric/build/elebihan/demo-systemd/arm/build/udev-undefined/.stamp_configured] Erreur 1With the pure
Makefileversion, the error message is clearer:
package/udev/udev.mk:11: *** No Udev implementation selected. Configuration error. Stop.
Yes, I believe this is better. And the message is given at the very beginning of the build, not when udev starts to be built, which is also nicer.
Quoted 3 lines
I find it better. If it suits everyone, I can propose a patch to convert all the virtual packages to it and re-send my tutorial patch about virtual package.
That would be really great!
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/2 udev: update udev to new virtual package infra.
Quoted 10 lines · Thomas Petazzoni
Dear Eric Le Bihan,
Quoted 6 lines · Eric Le Bihan
Quoted 6 lines
Why are we doing this check in
UDEV_CONFIGURE_CMDS? I believe we can simply do:ifeq ($(<foo>_DEPENDENCIES),)
$(error No <foo> implementation selected)
endif
Quoted 9 lines
Quoted 5 lines
I followed the example in
package/opengl/libegl/libegl.mk, but I mixed theMakefilecontrol function $(error text...) and some Shell script without thinking...I will revert it to the pure shell version to be coherent.
I guess you mean "to the pure make version", according to what you say below, right?
No. I was thinking about keeping the shell version for this series and making the change in the new series that would update all the virtual packages, but thinking twice about it, it is better to make it now (patches could be applied in any order).
Best regards,
ELB
PATCH 1/2 udev: update udev to new virtual package infra.
In reply to Thomas PetazzoniHi!
Quoted 11 lines · Thomas Petazzoni
Quoted 11 lines
With the <foo>_CONFIGURE_CMDS method, we go through all the dummy steps, and this is very verbose:
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
udev undefined Extracting
udev undefined Patching
udev undefined Configuringecho "No Udev implementation selected. Configuration error."
No Udev implementation selected. Configuration error.
exit 1
make: *** [/home/eric/build/elebihan/demo-systemd/arm/build/udev-undefined/.stamp_configured] Erreur 1
Quoted 7 lines
Quoted 3 lines
With the pure
Makefileversion, the error message is clearer:
package/udev/udev.mk:11: *** No Udev implementation selected. Configuration error. Stop.Yes, I believe this is better. And the message is given at the very beginning of the build, not when udev starts to be built, which is also nicer.
I've made some further testing and unfortunately, the pure "make" solution does not work. The test on <foo>_DEPENDENCIES is performed when the Makefile is evaluated, whether <foo> virtual package is selected or not.
If virtual package <foo> is not selected, <foo>_DEPENDENCIES will be empty, so the test is true and the error message is displayed. That's not what we want.
Using <foo>_CONFIGURE_CMDS, the test will only be performed if the package is selected.
So, I'll stick with the current method (I'll had some '@' to silence the shell commands though).
Best regards,
ELB
PATCH 1/2 udev: update udev to new virtual package infra.
Dear Eric Le Bihan,
Quoted 9 lines · Eric Le Bihan
I've made some further testing and unfortunately, the pure "make" solution does not work. The test on <foo>_DEPENDENCIES is performed when the
Makefileis evaluated, whether <foo> virtual package is selected or not.If virtual package <foo> is not selected, <foo>_DEPENDENCIES will be empty, so the test is true and the error message is displayed. That's not what we want.
Using <foo>_CONFIGURE_CMDS, the test will only be performed if the package is selected.
Then, just improve the test so that the test against the dependencies is only made when the virtual package is selected:
ifeq ($(BR2_PACKAGE_<virtual package>),y)
ifeq ($(<virtual package>_DEPENDENCIES),)
$(error "Something wrong going on!")
endif
endif
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 2/2 systemd: enable required kernel features.
In reply to Eric Le BihanWhen systemd is chosen as init system, the required kernel features are enabled.
--- linux/linux.mk | 6 +++++- package/systemd/Config.in | 12 ++++++++++-- 2 files changed, 15 insertions(+), 3 deletions(-)
linux/linux.mk +5 -1
@@ -195,7 +195,11 @@ define LINUX_CONFIGURE_CMDS $(call KCONFIG_ENABLE_OPT,CONFIG_FUNCTION_TRACER,$(@D)/.config)) $(if $(BR2_PACKAGE_SYSTEMD), $(call KCONFIG_ENABLE_OPT,CONFIG_CGROUPS,$(@D)/.config) - $(call KCONFIG_ENABLE_OPT,CONFIG_INOTIFY_USER,$(@D)/.config)) + $(call KCONFIG_ENABLE_OPT,CONFIG_INOTIFY_USER,$(@D)/.config) + $(call KCONFIG_ENABLE_OPT,CONFIG_FHANDLE,$(@D)/.config) + $(call KCONFIG_ENABLE_OPT,CONFIG_AUTOFS4_FS,$(@D)/.config) + $(call KCONFIG_ENABLE_OPT,CONFIG_TMPFS_POSIX_ACL,$(@D)/.config) + $(call KCONFIG_ENABLE_OPT,CONFIG_TMPFS_POSIX_XATTR,$(@D)/.config)) $(if $(BR2_LINUX_KERNEL_APPENDED_DTB), $(call KCONFIG_ENABLE_OPT,CONFIG_ARM_APPENDED_DTB,$(@D)/.config)) yes '' | $(TARGET_MAKE_ENV) $(MAKE1) $(LINUX_MAKE_FLAGS) -C $(@D) oldconfig
package/systemd/Config.in +10 -2
@@ -26,8 +26,16 @@ config BR2_PACKAGE_SYSTEMD elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit. - Systemd requires a Linux kernel >= 3.0, with inotify, devtmpfs, - tmpfs vfs and tmpfs POSIX ACL enabled. + Systemd requires a Linux kernel >= 3.0. + + The following features will be enabled in the kernel: + + - CONFIG_CGROUPS + - CONFIG_INOTIFY_USER + - CONFIG_FHANDLE + - CONFIG_AUTOFS4_FS + - CONFIG_TMPFS_POSIX_ACL + - CONFIG_TMPFS_XATTR Systemd also provides udev, the userspace device daemon.
Signature · 1 line
1.7.9.5
PATCH 2/2 systemd: enable required kernel features.
Dear Eric Le Bihan,
Quoted 10 lines · Eric Le Bihan
package/systemd/Config.in +0
-2@@ -26,8 +26,16 @@ config BR2_PACKAGE_SYSTEMD elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit. - Systemd requires a Linux kernel >= 3.0, with inotify, devtmpfs, - tmpfs vfs and tmpfs POSIX ACL enabled.
package/systemd/Config.in config BR2_PACKAGE_SYSTEMD · line 38
Quoted 10 lines
package/systemd/Config.in +10
-0+ Systemd requires a Linux kernel >= 3.0. + + The following features will be enabled in the kernel: + + - CONFIG_CGROUPS + - CONFIG_INOTIFY_USER + - CONFIG_FHANDLE + - CONFIG_AUTOFS4_FS + - CONFIG_TMPFS_POSIX_ACL + - CONFIG_TMPFS_XATTR
This formulation is not correct for people who build their kernel outside of Buildroot (while the earlier formulation worked for both situations).
What about something like:
systemd requires the following options to be enabled in the kernel:
- CONFIG_<foo>
- CONFIG_<bar>
These options will be automatically enabled by Buildroot if it is responsible for building the kernel. Otherwise, if you are building your kernel outside of Buildroot, make sure these options are enabled.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 2/2 systemd: enable required kernel features.
Hi!
Quoted 34 lines · Thomas Petazzoni
Dear Eric Le Bihan,
Quoted 10 lines · Eric Le Bihan
package/systemd/Config.in +0
-2@@ -26,8 +26,16 @@ config BR2_PACKAGE_SYSTEMD elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit. - Systemd requires a Linux kernel >= 3.0, with inotify, devtmpfs, - tmpfs vfs and tmpfs POSIX ACL enabled.package/systemd/Config.in config BR2_PACKAGE_SYSTEMD · line 38
Quoted 10 lines
package/systemd/Config.in +10
-0+ Systemd requires a Linux kernel >= 3.0. + + The following features will be enabled in the kernel: + + - CONFIG_CGROUPS + - CONFIG_INOTIFY_USER + - CONFIG_FHANDLE + - CONFIG_AUTOFS4_FS + - CONFIG_TMPFS_POSIX_ACL + - CONFIG_TMPFS_XATTRThis formulation is not correct for people who build their kernel outside of Buildroot (while the earlier formulation worked for both situations).
What about something like:
systemd requires the following options to be enabled in the kernel:
Quoted 8 lines
- CONFIG_<foo>
- CONFIG_<bar>These options will be automatically enabled by Buildroot if it is responsible for building the kernel. Otherwise, if you are building your kernel outside of Buildroot, make sure these options are enabled.
Thanks for the suggestion. I'll add it (the more information, the better).
Best regards,
ELB