[Buildroot] What to do about systemd/udev/eudev?

[Thomas Petazzoni <thomas.petazzoni@free-electrons.com>]

Dear Stefan Fr?berg,

On Mon, 04 Mar 2013 20:25:45 +0200, Stefan Fr?berg wrote:

> >> *But* ... (and this is a big but) I have not tested how it reacts to
> >> kernel events after boot when you *plug/unplug* devices and if mdev
> >> is capable of *running programs/scripts when some event happens*.
> > mdev is capable of running programs/scripts when some event happens,
> > even after boot time. I've already used this capability to notify an
> > application when a USB input device is added/removed from the system,
> > or to trigger a system upgrade when a USB key is inserted.
> 
> It is? Oh good ! :-)

See http://git.busybox.net/busybox/tree/examples/mdev.conf#n17.

> > However, if an application relies on libudev to get notifications of
> > devices appearing/disappearing, or other services, then of course, it
> > cannot work with mdev.
> 
> Damn... That would mean that network-manager and some other stuff would
> need patchin then to
> get completely rid of udev...
> Real pity.

Things like bluez, udisks, pulseaudio, X.org, etc. depend on libudev to
get notification when devices are added/removed.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com