[X] systemd is a disease [_] LENNART POETTERING! [X] Debian betrayed us [_] UNIX philosophy [_] monolithic == bad!!!
Well, we're getting somewhere, I guess. Time to post my "pro"-systemd questions for the day:
> I don't want to use systemd for technical reasons
Reasonable enough.
> I can't switch back to sysvinit
Wait, why?
> Even though SysVinit is still supported by many distros, I can't use it because many things depend on systemd
First, which things? and second, that's a problem with the devs of those other things, not systemd. Please stop shifting blame and dehumanizing systemd.
> Gnome depends on systemd
Why are you running Gnome on a server? I suppose you could be an anti-systemd desktop user, but then the technical reasons argument weakens considerably; desktop users shouldn't need to care about the init system, thanks to DEs, and most rational "anti"-systemd proponents are only arguing for loss of control on servers, recognizing systemd's benefits for desktop use.
> Systemd is being forced onto us
Is Lennart making the rounds and installing systemd on everyone's machines? No? Then keep running your SysVinit installation. Yes you miss out on long term support, but that was provided by the goodwill of the community and you really have no right to demand the community to support your whims and preferences.
-- Join the SDF Public Access UNIX System today!
Starting Score:
1
point
Karma-Bonus Modifier
+1
Total Score:
2
(Score: 2) by CRCulver on Saturday November 08 2014, @05:37PM
I was unaware of this, but even so, this is clearly a Debian problem and not an issue with systemd. Last I checked, for example, Arch is fairly easy to switch over to, e.g., OpenRC.
(Score: 2) by darkfeline on Saturday November 08 2014, @05:33PM
[X] systemd is a disease
[_] LENNART POETTERING!
[X] Debian betrayed us
[_] UNIX philosophy
[_] monolithic == bad!!!
Well, we're getting somewhere, I guess. Time to post my "pro"-systemd questions for the day:
> I don't want to use systemd for technical reasons
Reasonable enough.
> I can't switch back to sysvinit
Wait, why?
> Even though SysVinit is still supported by many distros, I can't use it because many things depend on systemd
First, which things? and second, that's a problem with the devs of those other things, not systemd. Please stop shifting blame and dehumanizing systemd.
> Gnome depends on systemd
Why are you running Gnome on a server? I suppose you could be an anti-systemd desktop user, but then the technical reasons argument weakens considerably; desktop users shouldn't need to care about the init system, thanks to DEs, and most rational "anti"-systemd proponents are only arguing for loss of control on servers, recognizing systemd's benefits for desktop use.
> Systemd is being forced onto us
Is Lennart making the rounds and installing systemd on everyone's machines? No? Then keep running your SysVinit installation. Yes you miss out on long term support, but that was provided by the goodwill of the community and you really have no right to demand the community to support your whims and preferences.
Join the SDF Public Access UNIX System today!
(Score: 2) by CRCulver on Saturday November 08 2014, @05:37PM
Here's why. [debian.org] Months have gone by and that bug is still there. Once systemd is on a Debian system, you're stuck with it.
(Score: 2) by darkfeline on Saturday November 08 2014, @10:03PM
I was unaware of this, but even so, this is clearly a Debian problem and not an issue with systemd. Last I checked, for example, Arch is fairly easy to switch over to, e.g., OpenRC.
Join the SDF Public Access UNIX System today!
(Score: 0) by Anonymous Coward on Sunday November 09 2014, @10:25AM
Why are you running Gnome on a server?
This is a stupid assumption amigo...