On Fri, 2014-02-21 at 19:06 +0100, Reindl Harald wrote:
> It's taken, what, 7-8 Fedora cycles, 3-4 years, and one
entire RHEL
> cycle for NetworkManager to be in a state where RH considers it
> acceptable as a default for RHEL 7.
fine - and that is why RHEL is irrelevant in the context
I don't see how that follows.
> Why are we assuming systemd-networkd shows up and will be good
enough
> for us overnight?
why not?
Er................are you serious?
I don't tend to deploy software on my servers because I'm just guessing
it'll work.
* nobody is porting "network.service" to a systemd-unit
* NM is a no-go for most people on servers i know (except Simon)
I'd run it on mine if I was deploying them today. It's a lot better than
it used to be for server use. Which makes sense, because its initial
design focus was desktop use, and once that was in good shape, server
side was worked on.
> Has anyone who's saying it's The Future and we should
> switch to it immediately even run it yet?
dow w ehave a systemd-209 somewhere
http://koji.fedoraproject.org/koji/buildinfo?buildID=499417 - build
failed on ARM. But if you haven't even built it locally and tried it
yet...
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net