Linked by Thom Holwerda on Thu 19th May 2011 18:59 UTC, submitted by fran
Thread beginning with comment 473819
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Please correct if wrong...
by jessesmith on Thu 19th May 2011 21:28
in reply to "RE: Please correct if wrong..."
I think the above comment has it pretty much spot on. This isn't just saying, "Screw other operating systems", it's also saying, "Screw Linux distributions that don't use systemd." That could be a problem for Debian/Ubuntu/Slackware (I think) and other distros that use other init systems.
Not only that, but the developer has stated firmly that he won't accept patches into upstream that would improve portability. Which means if someone wants to put in the work to ports things over to another distro or operating system those fixes won't get applied upstream, making it a moving target. That's going to be a huge pain for outside porters/developers.
RE[3]: Please correct if wrong...
by Soulbender on Thu 19th May 2011 22:41
in reply to "RE[2]: Please correct if wrong..."
RE[3]: Please correct if wrong...
by Delgarde on Fri 20th May 2011 01:50
in reply to "RE[2]: Please correct if wrong..."
Not only that, but the developer has stated firmly that he won't accept patches into upstream that would improve portability. Which means if someone wants to put in the work to ports things over to another distro or operating system those fixes won't get applied upstream, making it a moving target. That's going to be a huge pain for outside porters/developers.
Be fair - systemd is a *very* low level project, just one step removed from the kernel, and very heavily tied to kernel interfaces. Trying to make the *code* portable just isn't feasible, which is why Lennart instead recommends writing API-compatible equivalents for BSD or Solaris.





Member since:
2008-07-15
What if people want to use sysvinit, initng, upstart, runit, or eINIT...?
I doubt most users care which init system they're running. The real question is what if most distros don't want to switch to using systemd, as it provides no real benefits over some of the other init systems out there and would require all packages' init scripts to be rewritten?
GNOME should go linux-only, imho, but it should not depend on systemd. Not everyone wants to reinvent the wheel like Poettering seems to enjoy doing. If he wants to integrate systemd support into GNOME, great. If the Ubuntu devs wish to integrate upstart support into GNOME, that's awesome. If Debian wants to integrate sysvinit support, more power to them. Forcing a hard dependency of systemd is probably one of the worst ideas I've heard... but, then again, most of GNOME 3 seems to be one huge bad idea. To those who think forcing systemd on everyone is a good idea, remember what happened when GNOME started depending on Pulseaudio and just how well that's turned out?