From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 4 Mar 2013 19:30:24 +0100 Subject: [Buildroot] What to do about systemd/udev/eudev? In-Reply-To: <5134E729.8070708@petroprogram.com> References: <1362312574-17701-1-git-send-email-olivier.schonken@gmail.com> <20130303195436.49654719@skate> <948441.33302.bm@smtp138.mail.ir2.yahoo.com> <5134E40D.6@petroprogram.com> <20130304192156.7bfe23bf@skate> <5134E729.8070708@petroprogram.com> Message-ID: <20130304193024.0c2d0490@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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