Mail archive

Re: [alpine-devel] udev replacement on Alpine Linux

From: Alan Pillay <>
Date: Tue, 12 Jan 2016 10:51:25 -0200

It has been half a month since we had this nice conversation. First of
all, I wish everyone a happy new year!

Due to other priorities, the udev replacement has been postponed, but
now Sören Tempel came up with this idea again. He also proposes smdev
to be shipped with next major Alpine Linux version - 3.4.0 - which is
expected to be released in about 4 months.
For this reason, I think it is good to reconsider this subject and
restart this conversation.
Natanael, do you believe smdev is mature enough to be used implemented
on Alpine Linux as the default device manager? What about the
accompanying software, nldev and nlmon? If something is missing, what
is it exactly? Would the developers of smdev, nldev and nlmon be
willing to help with the transaction from udev to their lightweight


On Tue, Jul 28, 2015 at 2:24 AM, Isaac Dunham <> wrote:
> [pruning CC: to those who are more likely to care about mdev features
> and command line]
> On Mon, Jul 27, 2015 at 10:37:37AM +0200, Natanael Copa wrote:
>> There was also a long discussion about adding netlink support to
>> busybox mdev on busybox mailing list. There was some disagreement on
>> how to do it.
>> There was even some patches that made busybox mdev read events from
>> stdin.
> A few comments regarding those patches...
> It is much simpler to debug something like "mdev -i" than a netlink reader
> spawned by a "netlink inetd", since there's less indirection in using strace
> and you can trivially create, log, and replay events. Do not underestimate
> how useful the ability to play back a series of hotplug events is.
> While I did prepare a patch for mdev -i (read events from stdin) based
> on your work, other modifications were made to mdev.
> Meanwhile, the agreement that there had been about reading events from
> stdin disappeared, Denys assumed that it was entirely about serialization
> and reimplemented nldev, and a simple rework of the patch to match the
> new code didn't work, so I never got the patch updated. (I figured that
> with a maintainer who didn't understand the feature request, it would take
> a bit more support to get it in.)
> If mdev -i is desired rather than a netlink reader, I think I could update
> the patch; but if netlink support in mdev itself is desired, I don't want
> to set up the environment that would be needed to test it.
> Thanks,
> Isaac Dunham
> ---
> Unsubscribe:
> Help:
> ---

Received on Tue Jan 12 2016 - 10:51:25 UTC