News for hackers. Stuff that matters.
Re:Introduction to networkd, network managment from systemd by rwmj on Tuesday February 25, 2014 @04:34AM (#7296544)
My question is why this daemon needs to be included in systemd.git. It appears to be a separate service which could easily live in its own project, to live or die on its own merits.
Re:Introduction to networkd, network managment from systemd by tomegun on Tuesday February 25, 2014 @07:23AM (#7297132)
We (the systemd developers) want systemd to provide the basic building blocks from which you can build an operating system. Networking is definitely one of these, so we want to include it by default.

However, you are of course free to use an alternative network management solution, and at least in the beginning we expect most people to stick with what they have. Distributions could easily ship networkd as a separate package, if they so chose.

[deleted]
Re:Introduction to networkd, network managment from systemd by viraptor on Tuesday February 25, 2014 @05:37AM (#7296774)
A prediction I'll write down to check in two years:

My guess is that at some point Arch and Fedora will "officially" become Systemd/GNU/Linux (Systemd will become the required and system-equivalent component) while Ubuntu will start working hard on creating a sane, modular equivalent.

Basically with init, dbus (now migrating into the kernel), logging, authorization, resource control, networking, etc. the only big thing left to control is software installation. I expect Systemd-package to pop up soon. It's going to be convenient, technically good enough to adopt and integrated enough that some projects will become pretty much not installable on other systems without hacking the build (think replacing makefiles or something similar). It may be even a slightly-incompatible systemd-rpm.

The place where systemd will be annoying the most is servers - currently most of what they do concentrates on desktops. Specialised VMs will suffer from bloat of unneeded functionality (journal, dynamic networking, dbus, cgroups integration (people that need it will do it manually anyway), user sessions, ...) and this is the first place where replacements will start.

(deleted parent was wondering what will happen first: people freaking out that systemd becomes too integrated, or systemd becoming too integrated to create a linux system without it)

Re:Introduction to networkd, network managment from systemd by fmoralesc on Tuesday February 25, 2014 @06:22AM (#7296945)
Ubuntu is following Debian on using systemd, "as soon as it offers a credible quality of service to match the existing init" (which might happen pretty fast): http://www.markshuttleworth.com/archives/1316

I don't see software installation unification happening any time soon. There are layers like packagekit that sit above package managers, though (but mostly under-developed because, well, what is the point?).

AFAIK, systemd makes sense in servers (possibly even more than in desktops), because of its support for container setups. Not sure, though.

Re:Introduction to networkd, network managment from systemd by viraptor on Tuesday February 25, 2014 @07:03AM (#7297065)
> Ubuntu is following Debian on using systemd

Yes, they were also happy to adopt Gnome shell some time ago... until they came up with own solution. And they worked on another display server... until they came up with own solution. I expect them to go the same route again.

Re:Introduction to networkd, network managment from systemd by teho on Tuesday February 25, 2014 @09:31AM (#7297756)
Upstart was started before sytemd unlike Mir and Unity (in comparison to Wayland and Gnome 3) and it's creator having come in support of systemd[1], Ubuntu's upstream, Debian, going with it and on top of that Shuttleworth already admitting defeat. I have to seriously doub that.

[1] https://plus.google.com/111820116102071851808/posts/4eHMc2tv...