On Mon, Jun 09, 2014 at 01:31:26PM +0300, Andrei POPESCU wrote: > Quote from the first link: > > The udev built from the systemd source tree will stay compatible > with non-systemd init systems for a long time. This change is mostly > a detail of the build scheme, rather than a change of direction or > interfaces. Accordingly, the libudev API is untouched by these build > infrastructure changes. For us, compatibility is key. >
Allow me to remind you this story: http://lkml.org/lkml/2012/10/3/484 The whole mess started once udev (systemd) upstream took the liberty to rewrite udev's firmware loader, and blamed kernel for the resulting breakage. And what was the reason of rewriting said firmware loader? Some part of systemd design. Or look at those poor people: http://forums.opensuse.org/showthread.php/493546-How-to-predict-predictable-network-interface-names https://lists.fedoraproject.org/pipermail/users/2013-February/431853.html So much for 'predictable network interface names', which is a favorite FreeDesktop toy. Regardless of initial intention of non-systemd compatibility, udev is changed, and the reason of changes lies in systemd. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140609105651.ga5...@d1696.int.rdtex.ru
