4 ms·

systemd (init) operates as pid1; Networkd is spawned by init similar to ubuntu's NetworkManager or a classic /etc/init.d/network restart. Pid1 /must/ be the fi

by abofh 12y ago

systemd (init) operates as pid1; Networkd is spawned by init similar to ubuntu's NetworkManager or a classic /etc/init.d/network restart. Pid1 /must/ be the first process as it's starting all the others; Shipping a network daemon w/ systemd doesn't imply the network daemon is pid1.

Symmetry 12y ago
I think he's asking if you could launch networkd from, say, a traditional init or Upstart. EDIT: Or if not, that's what I'm curious about.
- digi_owl 12y ago
  Bingo. No other init but systemd has a sprawling set of sub-daemons that duplicate existing daemons for features (but not interfaces), and insist on only working with systemd as the running init.
  - EmanueleAina 12y ago
    No, networkd relies on systemd udev integration and unit activation system. Since systemd needed a way to understand networking enough to activate units only on certain network settings (no need to fire up avahi if no real network interfaces are available) factoring out a daemon to react to devices coming and going to configure them wasn't too much work. You may thing that networkd duplicates some NetworkManager features, but it's a rather different, lower-level beast and they can work together just fine. I'm not sure which other daemons systemd duplicates, care to elaborate? timesyncd does not duplicate ntpd, it is just a client daemon (it's closer to a daemonised ntpdate), hostnamed, localed, machined do not duplicate anything, logind is the ConsoleKit successor addressing the known, unfixable issues in the latter. timesyncd, hostnamed, localed may arguably be made to work on non-systemd systems with little effort (as they already do in the systemd-shims package), logind relies on the systemd-as-pid1 due to the need to set up cgroups (in preparation to the single hierarchy change planned by kernel people) but with some more work it can be made to work without systemd (see the systemd-shims package again). I'm not sure if networkd is shipped by systemd-shims, let me know if you care enough to check.
- deleted 12y ago
  [deleted]

by abofh 12y ago

Symmetry 12y ago

I think he's asking if you could launch networkd from, say, a traditional init or Upstart. EDIT: Or if not, that's what I'm curious about.

digi_owl 12y ago
Bingo. No other init but systemd has a sprawling set of sub-daemons that duplicate existing daemons for features (but not interfaces), and insist on only working with systemd as the running init.
- EmanueleAina 12y ago
  No, networkd relies on systemd udev integration and unit activation system. Since systemd needed a way to understand networking enough to activate units only on certain network settings (no need to fire up avahi if no real network interfaces are available) factoring out a daemon to react to devices coming and going to configure them wasn't too much work. You may thing that networkd duplicates some NetworkManager features, but it's a rather different, lower-level beast and they can work together just fine. I'm not sure which other daemons systemd duplicates, care to elaborate? timesyncd does not duplicate ntpd, it is just a client daemon (it's closer to a daemonised ntpdate), hostnamed, localed, machined do not duplicate anything, logind is the ConsoleKit successor addressing the known, unfixable issues in the latter. timesyncd, hostnamed, localed may arguably be made to work on non-systemd systems with little effort (as they already do in the systemd-shims package), logind relies on the systemd-as-pid1 due to the need to set up cgroups (in preparation to the single hierarchy change planned by kernel people) but with some more work it can be made to work without systemd (see the systemd-shims package again). I'm not sure if networkd is shipped by systemd-shims, let me know if you care enough to check.
deleted 12y ago
[deleted]