[Buildroot] [PATCH 10/10] package/mdevd: bump version to 0.1.1.0

[Eric Le Bihan]

On 2019-10-01 10:35, Arnout Vandecappelle wrote:
>
>
> On 01/10/2019 08:50, Thomas Petazzoni wrote:
> > On Tue, 1 Oct 2019 01:14:41 +0200
> > Eric Le Bihan <eric.le.bihan.dev at free.fr> wrote:
> >
> >> 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.
>
>  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