Bump skarnet packages to 2019.09 release
cover Bump skarnet packages to 2019.09 release
This patch series bumps the skarnet.org packages to 2019.09 release [1] and introduces mdevd, a udev replacement for s6-based systems.
[1] http://www.mail-archive.com/skaware at list.skarnet.org/msg01342.html
Eric Le Bihan (10):
package/skalibs: bump version to 2.9.0.0 package/execline: bump version to 2.5.2.0 package/s6-portable-utils: bump version to 2.2.2.0 package/s6-linux-utils: bump version to 2.5.1.0 package/s6-dns: bump version to 2.3.1.0 package/s6-networking: bump version to 2.3.1.0 package/s6: bump version to 2.9.0.0 package/s6-rc: bump version to 0.5.1.0 package/s6-linux-init: bump version to 1.0.3.0 package/mdevd: bump version to 0.1.1.0
DEVELOPERS | 1 +
package/Config.in | 1 +
package/execline/execline.hash | 2 +-
package/execline/execline.mk | 2 +-
package/mdevd/Config.in | 9 ++
package/mdevd/mdevd.hash | 3 +
package/mdevd/mdevd.mk | 39 ++++++
package/s6-dns/s6-dns.hash | 2 +-
package/s6-dns/s6-dns.mk | 2 +-
package/s6-linux-init/s6-linux-init.hash | 2 +-
package/s6-linux-init/s6-linux-init.mk | 2 +-
package/s6-linux-utils/s6-linux-utils.hash | 2 +-
package/s6-linux-utils/s6-linux-utils.mk | 2 +-
package/s6-networking/s6-networking.hash | 2 +-
package/s6-networking/s6-networking.mk | 2 +-
.../s6-portable-utils/s6-portable-utils.hash | 2 +-
.../s6-portable-utils/s6-portable-utils.mk | 2 +-
package/s6-rc/s6-rc.hash | 2 +-
package/s6-rc/s6-rc.mk | 2 +-
package/s6/s6.hash | 2 +-
package/s6/s6.mk | 2 +-
...er-use-dummy-file-when-testing-libs.patch} | 10 +-
...0001-No-runtime-tests-for-endianness.patch | 96 ---------------
...0002-No-runtime-tests-for-type-sizes.patch | 115 ------------------
package/skalibs/skalibs.hash | 2 +-
package/skalibs/skalibs.mk | 3 +-
26 files changed, 77 insertions(+), 234 deletions(-)
create mode 100644 package/mdevd/Config.in
create mode 100644 package/mdevd/mdevd.hash
create mode 100644 package/mdevd/mdevd.mk
rename package/skalibs/{0003-Make-linker-use-dummy-file-when-testing-libs.patch => 0001-Make-linker-use-dummy-file-when-testing-libs.patch} (89%)
delete mode 100644 package/skalibs/0001-No-runtime-tests-for-endianness.patch
delete mode 100644 package/skalibs/0002-No-runtime-tests-for-type-sizes.patch--
2.21.0
PATCH 1/10 package/skalibs: bump version to 2.9.0.0
Bump version to 2.9.0.0 and drop runtime test patches, as cross-compilation detection has been revamped.
---
...er-use-dummy-file-when-testing-libs.patch} | 10 +-
...0001-No-runtime-tests-for-endianness.patch | 96 ---------------
...0002-No-runtime-tests-for-type-sizes.patch | 115 ------------------
package/skalibs/skalibs.hash | 2 +-
package/skalibs/skalibs.mk | 3 +-
5 files changed, 8 insertions(+), 218 deletions(-)
rename package/skalibs/{0003-Make-linker-use-dummy-file-when-testing-libs.patch => 0001-Make-linker-use-dummy-file-when-testing-libs.patch} (89%)
delete mode 100644 package/skalibs/0001-No-runtime-tests-for-endianness.patch
delete mode 100644 package/skalibs/0002-No-runtime-tests-for-type-sizes.patchpackage/skalibs/0001-Make-linker-use-dummy-file-when-testing-libs.patch renamed from package/skalibs/0003-Make-linker-use-dummy-file-when-testing-libs.patch +5 -5
@@ -1,4 +1,4 @@ -From 02ef4599179ead87cc6d154a32acaa6627cbfca2 Mon Sep 17 00:00:00 2001 +From ca69c0d48e65acadccfe65e3adf16c34a744627b Mon Sep 17 00:00:00 2001 From: Eric Le Bihan <[email protected]> Date: Tue, 10 Oct 2017 19:51:34 +0200 Subject: [PATCH] Make linker use dummy file when testing libs
@@ -18,10 +18,10 @@ Signed-off-by: Eric Le Bihan <[email protected]> 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure b/configure -index 8348b1f..62e5981 100755 +index 54d755b..64a061a 100755 --- a/configure +++ b/configure -@@ -227,7 +227,7 @@ trylibs () { +@@ -230,7 +230,7 @@ trylibs () { echo "Checking whether system has $2..." >&3 shift 2 if $CC_AUTO $CPPFLAGS_AUTO $CPPFLAGS $CPPFLAGS_POST $CFLAGS_AUTO $CFLAGS $CFLAGS_POST -c -o try$name.o src/sysdeps/try$name.c 2>/dev/null ; then
@@ -30,7 +30,7 @@ index 8348b1f..62e5981 100755 if test -z "$*" ; then rm -f try$name.o echo -@@ -243,7 +243,7 @@ trylibs () { +@@ -246,7 +246,7 @@ trylibs () { else echo " ... yes, with$args" >&3 fi
@@ -40,5 +40,5 @@ index 8348b1f..62e5981 100755 else echo -- -2.13.6 +2.17.2
package/skalibs/0001-No-runtime-tests-for-endianness.patch deleted +0 -96
96 lines not on this page · raw message
package/skalibs/0002-No-runtime-tests-for-type-sizes.patch deleted +0 -115
115 lines not on this page · raw message
package/skalibs/skalibs.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 30ac73f1e8da6387fcfa19cfe1e326a143b4d811aaf532988b280daefa56dcc7 skalibs-2.6.4.0.tar.gz +sha256 f5604f9e5ebb436d3a8efa16a2c4133f7bd424d9f22aa88fe7a372f0153396fb skalibs-2.9.0.0.tar.gz sha256 3eadcf980c40da0f257b8292d805ff41e5e5a908c1942315d9a627732e1aa012 COPYING
package/skalibs/skalibs.mk +2 -1
@@ -4,7 +4,7 @@ # ################################################################################ -SKALIBS_VERSION = 2.6.4.0 +SKALIBS_VERSION = 2.9.0.0 SKALIBS_SITE = http://skarnet.org/software/skalibs SKALIBS_LICENSE = ISC SKALIBS_LICENSE_FILES = COPYING
@@ -13,6 +13,7 @@ SKALIBS_INSTALL_STAGING = YES SKALIBS_CONF_OPTS = \ --prefix=/usr \ --with-default-path=/sbin:/usr/sbin:/bin:/usr/bin \ + --with-sysdep-devurandom=yes \ $(SHARED_STATIC_LIBS_OPTS) define SKALIBS_CONFIGURE_CMDS
Signature · 1 line
2.21.0
PATCH 2/10 package/execline: bump version to 2.5.2.0
In reply to Eric Le Bihan--- package/execline/execline.hash | 2 +- package/execline/execline.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/execline/execline.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 f6993094766652041c21fde9c07ef53a3cd4b93a64123d9578fb4997a2cefca1 execline-2.5.0.0.tar.gz +sha256 280bb633cbe96088193225729ad32d80493d68380a127e6bc1789aac64375e29 execline-2.5.2.0.tar.gz sha256 3eadcf980c40da0f257b8292d805ff41e5e5a908c1942315d9a627732e1aa012 COPYING
package/execline/execline.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -EXECLINE_VERSION = 2.5.0.0 +EXECLINE_VERSION = 2.5.2.0 EXECLINE_SITE = http://skarnet.org/software/execline EXECLINE_LICENSE = ISC EXECLINE_LICENSE_FILES = COPYING
Signature · 1 line
2.21.0
PATCH 3/10 package/s6-portable-utils: bump version to 2.2.2.0
In reply to Eric Le Bihan--- package/s6-portable-utils/s6-portable-utils.hash | 2 +- package/s6-portable-utils/s6-portable-utils.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/s6-portable-utils/s6-portable-utils.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 6ae239d2c458a81c92b5d616129e443874f925bf3da02589913a1a3b708c4531 s6-portable-utils-2.2.1.1.tar.gz +sha256 0503841a2aee1cd79122c9ecf49dbefad5c5d21be7114e83e71c210e106abf0a s6-portable-utils-2.2.2.0.tar.gz sha256 6ee77e7199d69b707ab864ea7a838f9562717aaa41c89413bdb2cf835f95052f COPYING
package/s6-portable-utils/s6-portable-utils.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -S6_PORTABLE_UTILS_VERSION = 2.2.1.1 +S6_PORTABLE_UTILS_VERSION = 2.2.2.0 S6_PORTABLE_UTILS_SITE = http://skarnet.org/software/s6-portable-utils S6_PORTABLE_UTILS_LICENSE = ISC S6_PORTABLE_UTILS_LICENSE_FILES = COPYING
Signature · 1 line
2.21.0
PATCH 4/10 package/s6-linux-utils: bump version to 2.5.1.0
In reply to Eric Le Bihan--- package/s6-linux-utils/s6-linux-utils.hash | 2 +- package/s6-linux-utils/s6-linux-utils.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/s6-linux-utils/s6-linux-utils.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 78571574464c76fc623ef50dc14800138b4fd98c5fa877af6850fdd9c2f90213 s6-linux-utils-2.5.0.0.tar.gz +sha256 58d6cbbaabf5c03739716e208f1690f7e7241480583cc9f5396093b428941bba s6-linux-utils-2.5.1.0.tar.gz sha256 3eadcf980c40da0f257b8292d805ff41e5e5a908c1942315d9a627732e1aa012 COPYING
package/s6-linux-utils/s6-linux-utils.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -S6_LINUX_UTILS_VERSION = 2.5.0.0 +S6_LINUX_UTILS_VERSION = 2.5.1.0 S6_LINUX_UTILS_SITE = http://skarnet.org/software/s6-linux-utils S6_LINUX_UTILS_LICENSE = ISC S6_LINUX_UTILS_LICENSE_FILES = COPYING
Signature · 1 line
2.21.0
PATCH 5/10 package/s6-dns: bump version to 2.3.1.0
In reply to Eric Le Bihan--- package/s6-dns/s6-dns.hash | 2 +- package/s6-dns/s6-dns.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/s6-dns/s6-dns.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 a828583e48741927c88de3822283c317c792ffc15d5e9043f29625b87ba38740 s6-dns-2.3.0.0.tar.gz +sha256 b11ce255668b683d785a1ef8ba89551a9586481b8888bc1a66d4b997e68892ca s6-dns-2.3.1.0.tar.gz sha256 6ee77e7199d69b707ab864ea7a838f9562717aaa41c89413bdb2cf835f95052f COPYING
package/s6-dns/s6-dns.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -S6_DNS_VERSION = 2.3.0.0 +S6_DNS_VERSION = 2.3.1.0 S6_DNS_SITE = http://skarnet.org/software/s6-dns S6_DNS_LICENSE = ISC S6_DNS_LICENSE_FILES = COPYING
Signature · 1 line
2.21.0
PATCH 6/10 package/s6-networking: bump version to 2.3.1.0
In reply to Eric Le Bihan--- package/s6-networking/s6-networking.hash | 2 +- package/s6-networking/s6-networking.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/s6-networking/s6-networking.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 d81968756abbcecde6a872c89d82f643cd621a0c295c2c57650705dbe875481a s6-networking-2.3.0.2.tar.gz +sha256 814fa3b70718d2423c742e920d31f64088272f7987c2cf7bebc86a63a75596b8 s6-networking-2.3.1.0.tar.gz sha256 6ee77e7199d69b707ab864ea7a838f9562717aaa41c89413bdb2cf835f95052f COPYING
package/s6-networking/s6-networking.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -S6_NETWORKING_VERSION = 2.3.0.2 +S6_NETWORKING_VERSION = 2.3.1.0 S6_NETWORKING_SITE = http://skarnet.org/software/s6-networking S6_NETWORKING_LICENSE = ISC S6_NETWORKING_LICENSE_FILES = COPYING
Signature · 1 line
2.21.0
PATCH 7/10 package/s6: bump version to 2.9.0.0
In reply to Eric Le Bihan--- package/s6/s6.hash | 2 +- package/s6/s6.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/s6/s6.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 f37547f2890eb50bcb4cd46ffa38bad5ec9e6fd6bc7b73a8df0bdf0cf11f01a9 s6-2.7.1.1.tar.gz +sha256 1cac59bf9ff7c011b189ae2def3c76b147c2c431b0a901029fcaf957a6d9a343 s6-2.9.0.0.tar.gz sha256 3eadcf980c40da0f257b8292d805ff41e5e5a908c1942315d9a627732e1aa012 COPYING
package/s6/s6.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -S6_VERSION = 2.7.1.1 +S6_VERSION = 2.9.0.0 S6_SITE = http://skarnet.org/software/s6 S6_LICENSE = ISC S6_LICENSE_FILES = COPYING
Signature · 1 line
2.21.0
PATCH 8/10 package/s6-rc: bump version to 0.5.1.0
In reply to Eric Le Bihan--- package/s6-rc/s6-rc.hash | 2 +- package/s6-rc/s6-rc.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/s6-rc/s6-rc.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 4b4b6205e31e85be583a165a994552d0f30ebcdabbdd919f9f469815d7679e5c s6-rc-0.4.0.1.tar.gz +sha256 93c02d0b505c036c332e13769154d82c9e31e4dd99f3ba80aa97d377ca9ac11c s6-rc-0.5.1.0.tar.gz sha256 1377d3b18a31de11e8bb06f0f46888a23bc16cbc57285035793bf7e7943bbcb3 COPYING
package/s6-rc/s6-rc.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -S6_RC_VERSION = 0.4.0.1 +S6_RC_VERSION = 0.5.1.0 S6_RC_SITE = http://skarnet.org/software/s6-rc S6_RC_LICENSE = ISC S6_RC_LICENSE_FILES = COPYING
Signature · 1 line
2.21.0
PATCH 9/10 package/s6-linux-init: bump version to 1.0.3.0
In reply to Eric Le Bihan--- package/s6-linux-init/s6-linux-init.hash | 2 +- package/s6-linux-init/s6-linux-init.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/s6-linux-init/s6-linux-init.hash +1 -1
@@ -1,3 +1,3 @@ # Locally generated -sha256 d4ac9b8bde3e678353c85dad1a2a25066a40f843c53840c4210839068635ed7e s6-linux-init-0.4.0.0.tar.gz +sha256 a48dd2fb78a719d586f3f174b1a06fdf1c125839cee52e6a47d83cdb251529be s6-linux-init-1.0.3.0.tar.gz sha256 1377d3b18a31de11e8bb06f0f46888a23bc16cbc57285035793bf7e7943bbcb3 COPYING
package/s6-linux-init/s6-linux-init.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -S6_LINUX_INIT_VERSION = 0.4.0.0 +S6_LINUX_INIT_VERSION = 1.0.3.0 S6_LINUX_INIT_SITE = http://skarnet.org/software/s6-linux-init S6_LINUX_INIT_LICENSE = ISC S6_LINUX_INIT_LICENSE_FILES = COPYING
Signature · 1 line
2.21.0
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
In reply to Eric Le BihanThis new package provides mdevd, a small daemon managing kernel hotplug events similar to udevd.
--- DEVELOPERS | 1 + package/Config.in | 1 + package/mdevd/Config.in | 9 +++++++++ package/mdevd/mdevd.hash | 3 +++ package/mdevd/mdevd.mk | 39 +++++++++++++++++++++++++++++++++++++++ 5 files changed, 53 insertions(+) create mode 100644 package/mdevd/Config.in create mode 100644 package/mdevd/mdevd.hash create mode 100644 package/mdevd/mdevd.mk
DEVELOPERS +1 -0
@@ -683,6 +683,7 @@ F: package/eudev/ F: package/execline/ F: package/hicolor-icon-theme/ F: package/jemalloc/ +F: package/mdevd/ F: package/meson/ F: package/ninja/ F: package/pkg-meson.mk
package/Config.in +1 -0
@@ -478,6 +478,7 @@ endmenu source "package/lvm2/Config.in" source "package/mali-t76x/Config.in" source "package/mdadm/Config.in" + source "package/mdevd/Config.in" source "package/memtest86/Config.in" source "package/memtester/Config.in" source "package/memtool/Config.in"
package/mdevd/Config.in new file +9 -0
@@ -0,0 +1,9 @@ +config BR2_PACKAGE_MDEVD + bool "mdevd" + depends on BR2_USE_MMU # skalibs + select BR2_PACKAGE_SKALIBS + help + mdevd is a small daemon managing kernel hotplug events, + similarly to udevd. + + http://skarnet.org/software/mdevd/
package/mdevd/mdevd.hash new file +3 -0
@@ -0,0 +1,3 @@ +# Locally generated +sha256 302819dceb2400f299ef8f04828a4fe9156d7334e41ce34d61db37fbc2aa7e8f mdevd-0.1.1.0.tar.gz +sha256 e5319cb67bd1d896f3b2fa1136034b1b155a6e278ab1c2578a394f758f0034c1 COPYING
package/mdevd/mdevd.mk new file +39 -0
@@ -0,0 +1,39 @@ +################################################################################ +# +# mdevd +# +################################################################################ + +MDEVD_VERSION = 0.1.1.0 +MDEVD_SITE = http://skarnet.org/software/mdevd +MDEVD_LICENSE = ISC +MDEVD_LICENSE_FILES = COPYING +MDEVD_INSTALL_STAGING = YES +MDEVD_DEPENDENCIES = skalibs + +MDEVD_CONF_OPTS = \ + --prefix=/usr \ + --with-sysdeps=$(STAGING_DIR)/usr/lib/skalibs/sysdeps \ + --with-include=$(STAGING_DIR)/usr/include \ + --with-dynlib=$(STAGING_DIR)/usr/lib \ + --with-lib=$(STAGING_DIR)/usr/lib/skalibs \ + $(if $(BR2_STATIC_LIBS),,--disable-allstatic) \ + $(SHARED_STATIC_LIBS_OPTS) + +define MDEVD_CONFIGURE_CMDS + (cd $(@D); $(TARGET_CONFIGURE_OPTS) ./configure $(MDEVD_CONF_OPTS)) +endef + +define MDEVD_BUILD_CMDS + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) +endef + +define MDEVD_INSTALL_TARGET_CMDS + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) DESTDIR=$(TARGET_DIR) install +endef + +define MDEVD_INSTALL_STAGING_CMDS + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) DESTDIR=$(STAGING_DIR) install +endef + +$(eval $(generic-package))
Signature · 1 line
2.21.0
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
Quoted 4 lines · On Sun, 29 Sep 2019 19:10:17 +0200 Eric Le Bihan <[email protected]>…
This new package provides mdevd, a small daemon managing kernel hotplug events similar to udevd.
Signed-off-by Eric Le Bihan <[email protected]>
We have a choice between static /dev, devtmpfs, devtmpfs + Busybox mdev, devtmpfs + eudev, should we add a choice of devtmpfs + mdevd ?
What happens if we have both Busybox mdev *and* mdevd in the same configuration ?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Quoted 3 lines · On Sun, 29 Sep 2019 19:10:17 +0200 Eric Le Bihan <[email protected]>…
This new package provides mdevd, a small daemon managing kernel hotplug events similar to udevd.
Quoted 7 lines
Quoted 1 line
Signed-off-by Eric Le Bihan <[email protected]>We have a choice between static /dev, devtmpfs, devtmpfs + Busybox mdev, devtmpfs + eudev, should we add a choice of devtmpfs + mdevd ?
What happens if we have both Busybox mdev *and* mdevd in the same configuration ?
What is the advantage of mdevd over mdev now that we use the daemon mode of mdev?
Signature · 1 line
Bye, Peter Korsgaard
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
Hi!
Quoted 10 lines · Peter Korsgaard
Quoted 9 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Quoted 4 lines · On Sun, 29 Sep 2019 19:10:17 +0200 Eric Le Bihan <[email protected]>…
This new package provides mdevd, a small daemon managing kernel hotplug events similar to udevd.
Signed-off-by Eric Le Bihan <[email protected]>
Quoted 8 lines
Quoted 5 lines
We have a choice between static /dev, devtmpfs, devtmpfs + Busybox mdev, devtmpfs + eudev, should we add a choice of devtmpfs + mdevd ?
What happens if we have both Busybox mdev *and* mdevd in the same configuration ?
What is the advantage of mdevd over mdev now that we use the daemon mode of mdev?
I did not know about the daemon mode of mdev, but mdevd was created to overcome the mdev forking issue [1] and predates the daemon option [2].
So in the end, they provide the same features, with mdevd also complying with s6 notification mechanism [3], making it more tightly coupled with this init system.
Given that there is no option in menuconfig to use a s6-based init system [4], I see no reason to add a "devtmpfs+mdevd" option ATM.
Users should select the mdevd package when implementing their own custom s6-based init.
[1] https://skarnet.org/software/mdevd/mdevd.html
[2] https://git.skarnet.org/cgi-bin/cgit.cgi/mdevd/tag/?h=v0.0.1.0
[3] https://skarnet.org/software/s6/notifywhenup.html
[4] http://buildroot-busybox.2317881.n4.nabble.com/RFC-0-3-init-Add-s6-as-init-system-tp213980p216232.html
Regards,
--
ELB
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
Quoted 9 lines · On Tue, 1 Oct 2019 01:14:41 +0200 Eric Le Bihan <[email protected]>…
I did not know about the daemon mode of mdev, but mdevd was created to overcome the mdev forking issue [1] and predates the daemon option [2].
So in the end, they provide the same features, with mdevd also complying with s6 notification mechanism [3], making it more tightly coupled with this init system.
Given that there is no option in menuconfig to use a s6-based init system [4], I see no reason to add a "devtmpfs+mdevd" option ATM.
But then there is nothing that prevents them from enabling devtmpfs+eudev as the /dev management system, and separately enable mdevd. That wouldn't work very well.
On the other hand, if a user enables both openssh and dropbear, in their default configuration, both will try to listen on TCP port 22, which won't work as well. So perhaps we can live with having mdevd as a standalone package, with no specific handling in the /dev management choice. I'm just a bit worried about users who will enable this mdevd package, while they are looking for Busybox mdev.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
Quoted 17 lines · Thomas Petazzoni
Quoted 9 lines · On Tue, 1 Oct 2019 01:14:41 +0200 Eric Le Bihan <[email protected]>…
I did not know about the daemon mode of mdev, but mdevd was created to overcome the mdev forking issue [1] and predates the daemon option [2].
So in the end, they provide the same features, with mdevd also complying with s6 notification mechanism [3], making it more tightly coupled with this init system.
Given that there is no option in menuconfig to use a s6-based init system [4], I see no reason to add a "devtmpfs+mdevd" option ATM.
But then there is nothing that prevents them from enabling devtmpfs+eudev as the /dev management system, and separately enable mdevd. That wouldn't work very well.
Quoted 6 lines
On the other hand, if a user enables both openssh and dropbear, in their default configuration, both will try to listen on TCP port 22, which won't work as well. So perhaps we can live with having mdevd as a standalone package, with no specific handling in the /dev management choice. I'm just a bit worried about users who will enable this mdevd package, while they are looking for Busybox mdev.
AFAIU, the s6 tools are really an ecosystem. So I think it would make sense to
move all of them into a "s6 system management" menu under System tools. That should make it sufficiently clear that this is not related to busybox mdev.
Regards,
Arnout
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
Arnout, All,
On 2019-10-01 10:35 +0200, Arnout Vandecappelle spake thusly:
Quoted 25 lines · Thomas Petazzoni
Quoted 17 lines
Quoted 9 lines · On Tue, 1 Oct 2019 01:14:41 +0200 Eric Le Bihan <[email protected]>…
I did not know about the daemon mode of mdev, but mdevd was created to overcome the mdev forking issue [1] and predates the daemon option [2].
So in the end, they provide the same features, with mdevd also complying with s6 notification mechanism [3], making it more tightly coupled with this init system.
Given that there is no option in menuconfig to use a s6-based init system [4], I see no reason to add a "devtmpfs+mdevd" option ATM.
But then there is nothing that prevents them from enabling devtmpfs+eudev as the /dev management system, and separately enable mdevd. That wouldn't work very well.
Quoted 6 lines
On the other hand, if a user enables both openssh and dropbear, in their default configuration, both will try to listen on TCP port 22, which won't work as well. So perhaps we can live with having mdevd as a standalone package, with no specific handling in the /dev management choice. I'm just a bit worried about users who will enable this mdevd package, while they are looking for Busybox mdev.
Quoted 3 lines
AFAIU, the s6 tools are really an ecosystem. So I think it would make sense to
move all of them into a "s6 system management" menu under System tools. That should make it sufficiently clear that this is not related to busybox mdev.
Doesn't s6 also come with an init system of its own, too? In which case, it would be more akin to the systemd situation.
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
Quoted 28 lines · Yann E. MORIN
Arnout, All,
On 2019-10-01 10:35 +0200, Arnout Vandecappelle spake thusly:
Quoted 25 lines · Thomas Petazzoni
Quoted 23 lines
Quoted 9 lines · On Tue, 1 Oct 2019 01:14:41 +0200 Eric Le Bihan <[email protected]>…
I did not know about the daemon mode of mdev, but mdevd was created to overcome the mdev forking issue [1] and predates the daemon option [2].
So in the end, they provide the same features, with mdevd also complying with s6 notification mechanism [3], making it more tightly coupled with this init system.
Given that there is no option in menuconfig to use a s6-based init system [4], I see no reason to add a "devtmpfs+mdevd" option ATM.
But then there is nothing that prevents them from enabling devtmpfs+eudev as the /dev management system, and separately enable mdevd. That wouldn't work very well.
On the other hand, if a user enables both openssh and dropbear, in their default configuration, both will try to listen on TCP port 22, which won't work as well. So perhaps we can live with having mdevd as a standalone package, with no specific handling in the /dev management choice. I'm just a bit worried about users who will enable this mdevd package, while they are looking for Busybox mdev.
Quoted 6 lines
Quoted 3 lines
AFAIU, the s6 tools are really an ecosystem. So I think it would make sense to
move all of them into a "s6 system management" menu under System tools. That should make it sufficiently clear that this is not related to busybox mdev.Doesn't s6 also come with an init system of its own, too? In which case, it would be more akin to the systemd situation.
In a way, the s6 ecosystem is more a kit to build an init system than a full init system stack like systemd. The author emphasizes that it provides a mechanism and not policies. For example, some users mix the services supervision part (s6) and OpenRC [1].
The mdevd program can be used without s6, unlike udev which is now part of systemd (this situation lead to the creation of eudev).
[1] https://github.com/OpenRC/openrc/blob/master/s6-guide.md
Regards,
--
ELB
PATCH 10/10 package/mdevd: bump version to 0.1.1.0
In reply to Arnout VandecappelleQuoted 27 lines · Arnout Vandecappelle
Quoted 17 lines · Thomas Petazzoni
Quoted 9 lines · On Tue, 1 Oct 2019 01:14:41 +0200 Eric Le Bihan <[email protected]>…
I did not know about the daemon mode of mdev, but mdevd was created to overcome the mdev forking issue [1] and predates the daemon option [2].
So in the end, they provide the same features, with mdevd also complying with s6 notification mechanism [3], making it more tightly coupled with this init system.
Given that there is no option in menuconfig to use a s6-based init system [4], I see no reason to add a "devtmpfs+mdevd" option ATM.
But then there is nothing that prevents them from enabling devtmpfs+eudev as the /dev management system, and separately enable mdevd. That wouldn't work very well.
Quoted 6 lines
On the other hand, if a user enables both openssh and dropbear, in their default configuration, both will try to listen on TCP port 22, which won't work as well. So perhaps we can live with having mdevd as a standalone package, with no specific handling in the /dev management choice. I'm just a bit worried about users who will enable this mdevd package, while they are looking for Busybox mdev.
Quoted 3 lines
AFAIU, the s6 tools are really an ecosystem. So I think it would make sense to
move all of them into a "s6 system management" menu under System tools. That should make it sufficiently clear that this is not related to busybox mdev.
Currently, the following packages are listed individually in the "System tools" section: s6, s6-linux-init, s6-linux-utils, s6-portable-utils, s6-rc.
The packages s6, s6-linux-init, s6-rc are the ones to use for building a real s6-based init system. s6-linux-utils and s6-portable-utils provide alternatives to busybox/coreutils and a few niceties (e.g. s6-fillurandompool). They can be used with any init systems.
It looks sensible to move them to a submenu named "s6 system management" and add mdevd to it to avoid confusion. But IMHO other skarnet packages like the execline scripting language should be kept out of it as it not s6-related, though used most of the time when building a s6-based init system.
Regards,
--
ELB
Arnout Vandecappelle
AppliedPATCH 10/10 package/mdevd: bump version to 0.1.1.0
In reply to Eric Le BihanQuoted 4 lines · Eric Le Bihan
This new package provides mdevd, a small daemon managing kernel hotplug events similar to udevd.
Signed-off-by Eric Le Bihan <[email protected]>
Applied to master, thanks.
Regards,
Arnout
cover Bump skarnet packages to 2019.09 release
In reply to Eric Le BihanHello Eric,
Quoted 10 lines · On Sun, 29 Sep 2019 19:10:07 +0200 Eric Le Bihan <[email protected]>…
Eric Le Bihan (10):
package/skalibs: bump version to 2.9.0.0 package/execline: bump version to 2.5.2.0 package/s6-portable-utils: bump version to 2.2.2.0 package/s6-linux-utils: bump version to 2.5.1.0 package/s6-dns: bump version to 2.3.1.0 package/s6-networking: bump version to 2.3.1.0 package/s6: bump version to 2.9.0.0 package/s6-rc: bump version to 0.5.1.0 package/s6-linux-init: bump version to 1.0.3.0
I have applied those first 9 patches, but I had to fix each of them:
you forgot to update the hash of the COPYING file, and to explain so in the commit log. Could you make sure to test with "make legal-info" your next version bumps ?
Quoted 1 line
package/mdevd: bump version to 0.1.1.0
I'll reply to this one specifically.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
cover Bump skarnet packages to 2019.09 release
Hi!
Quoted 16 lines · Thomas Petazzoni
Hello Eric,
Quoted 10 lines · On Sun, 29 Sep 2019 19:10:07 +0200 Eric Le Bihan <[email protected]>…
Eric Le Bihan (10):
package/skalibs: bump version to 2.9.0.0 package/execline: bump version to 2.5.2.0 package/s6-portable-utils: bump version to 2.2.2.0 package/s6-linux-utils: bump version to 2.5.1.0 package/s6-dns: bump version to 2.3.1.0 package/s6-networking: bump version to 2.3.1.0 package/s6: bump version to 2.9.0.0 package/s6-rc: bump version to 0.5.1.0 package/s6-linux-init: bump version to 1.0.3.0
Quoted 4 lines
I have applied those first 9 patches, but I had to fix each of them:
you forgot to update the hash of the COPYING file, and to explain so in the commit log. Could you make sure to test with "make legal-info" your next version bumps ?
Of course! I wrongly assumed the COPYING files would never change. Thanks for the fix.
Regards,
--
ELB