Upgrade Systemd to v209

[wkennington]

This is a pretty major change which brings dbus and systemd up to the most recent versions. I'm still working on this patch but I'd like to put it out there to make progress. Nixos still does not build even though systemd should.

One of the benefits to upgrading is that it would greatly reduce the complexity in our networking services as this version of systemd brings the networkd component.

Note: This looks to be broken on arm as per the release notes.
http://lists.freedesktop.org/archives/systemd-devel/2014-February/017146.html

[edolstra]

I'm not sure we want systemd-networkd. It really seems bloat to me that systemd is now doing things like DHCP, when we have packages like dhcpcd that work just fine (and probably have more features and fewer bugs).

[bluescreen303]

I agree, but I would like to experiment with it nonetheless.
I think this will become useful if we ever decide to move systemd into
initrd phases, which provides more niceties.

[ocharles]

Mathijs Kwik notifications@github.com writes:

I agree, but I would like to experiment with it nonetheless.
I think this will become useful if we ever decide to move systemd into
initrd phases, which provides more niceties.

I'm in the same situation - while it might be bloat I would like to at
least experiment with it and decide that for myself.

[offlinehacker]

We could use ncd http://code.google.com/p/badvpn/wiki/NCD for network
configuration. It clearly provides more flexibility than any other network
configuration manager.
On Feb 20, 2014 3:33 PM, "Oliver Charles" notifications@github.com wrote:

Mathijs Kwik notifications@github.com writes:

I agree, but I would like to experiment with it nonetheless.
I think this will become useful if we ever decide to move systemd into
initrd phases, which provides more niceties.

I'm in the same situation - while it might be bloat I would like to at
least experiment with it and decide that for myself.

Reply to this email directly or view it on GitHubhttps://github.com//pull/1795#issuecomment-35626533
.

[bluescreen303]

I don't want all these :)
I like what we have, but would like to experiment with systemd's method.

[vcunat]

I suppose we don't want to merge such huge update before branching off release-14.02.

This is a massive new release, it includes a lot of new code. You probably don't want to base your LTS release on this. We hope to return to a shorter release cycle now to stabilize the new code. Expect a couple of bugfix releases over the next weeks.

But it seems good to prepare for the switch, as the bug-fixes are unlikely to disrupt the preparations.

[wkennington]

@edolstra I think that the networkd component would be a great improvement over our current handling of bridges, vlans, and bonds. It sounds like it should be something handled upstream and the hotplugging support looks to be better.

@vcunat I completely agree considering this is a huge change for the systemd project, and it looks like we don't have more than 7 days before 14.02 goes out. I just wanted to propose this change as the systemd package has been stagnating even though the project seems to be moving right along.

[thoughtpolice]

It's worth noting that systemd 210 was already released yesterday, and it has some other extra improvements worth considering, like AppArmor profile support and a lot of bug fixes.

https://www.mail-archive.com/systemd-devel@lists.freedesktop.org/msg17083.html

[wkennington]

Yes, I'll be working with the latest version at all times seeing as they are moving to a faster paced bug fix cycle again. For now I'll keep this the same as the patch is not nearly ready.