Nicolas Sebrecht posted on Thu, 11 Feb 2016 02:46:33 +0100 as excerpted: > On Mon, Feb 08, 2016 at 11:00:15AM -0500, Ian Stakenvicius wrote: > >> Oh, eudev also doesn't handle network link setup given that external >> tools already do this just fine. That's another difference, though not >> one that matters programmatically. That said, the network-link setup >> was added primarily to support systemd's use-case, and there's very >> little need or point in having it done by udevd on an rc-based system. > > Unless I'm mistaken, you're saying that eudev doesn't handle network > link but it doesn't matter because rc-based systems don't requires it. > > And at the same time, I read in this thread that eudev is in-place > replacement for udev without any harm. What will happen to the users > wanting systemd AND expect the network link setup?
This whole debate doesn't apply to systemd users at all, only those not using systemd, because... Systemd users get the systemd-integrated udev, with systemd blocking (effectively, I've not looked at where the specific blocks are) both the stand-alone udev and eudev, as systemd is its own device-manager provider. Thus, systemd users have the systemd-based network link solution if they want it, via the systemd-integrated udev. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
