Debian decides on systemd—for now

Posted Feb 13, 2014 23:49 UTC (Thu) by xtifr (guest, #143)
In reply to: Debian decides on systemd—for now by cesarb
Parent article: Debian decides on systemd—for now

And since Ubuntu is now alone in its use of Upstart, upstream projects are free to say "we don't support single-distro solutions", and depend directly on systemd features without fallback.

That's true only for Linux-specific projects! I mean, can you seriously imagine Apache or Sendmail or OpenSSH telling people "you must use one of the major Linux platforms to run our system"? :)

Since I try to avoid using platform-specific software wherever possible (I may not have any immediate plans to switch to BSD, but I'd really like to retain the option, and I always try to support BSD at least in whatever I might write), such a statement would probably result in that software being purged from my system, even though I run Debian.

Debian decides on systemd—for now

Posted Feb 14, 2014 8:37 UTC (Fri) by ebirdie (guest, #512) [Link]

+1 expressing my support to the parent commentor and madscientist, you are both right on spot I can't bring anything to but just backup up with my experience from systems maintenance. Just a familiar term to describe my fears - and very deep irritation - with the vision in systemd: dependency hell.

I'm ready for systemd and I support that Debian makes a decision here and now to systemd than prolong the process. I fully trust both the decision-makers and the process they came to conclusions. The future will tell whether the old dogs fall in love with systemd and be quiet or feel the pain and rejoice at reinvented bone, init.

Just my cents to the discussion.

Debian decides on systemd—for now

Posted Feb 21, 2014 15:49 UTC (Fri) by Kluge (subscriber, #2881) [Link]

> I mean, can you seriously imagine Apache or Sendmail or OpenSSH telling people "you must use
> one of the major Linux platforms to run our system"? :)

As I understand it, this is precisely the POV of the OpenSSH project: core development is done solely for OpenBSD. Portability is handled by a separate group.

From http://www.openssh.com/history.html:
"From the start of our own efforts, we have felt that even the original ssh code was too complicated, it simply had too many operating system dependencies to deal with. Our approach to writing completely secure and rock solid code avoids dealing with excessive differences like that. Thus, to make the entire development process easier on us all, we decided to split our core development efforts from portability developments."