Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Monday November 17 2014, @11:15AM   Printer-friendly
from the more-systemd-fallout dept.

Longtime Debian contributor Tollef Fog Heen has announced his resignation from the Debian systemd maintainer team. His announcement states that "the load of the continued attacks is just becoming too much."

He has since written a detailed blog article surrounding the circumstances of his resignation. As he puts it,

I've been a DD for almost 14 years, I should be able to weather any storm, shouldn't I? It turns out that no, the mountain does get worn down by the rain. It's not a single hurtful comment here and there. There's a constant drum about this all being some sort of conspiracy and there are sometimes flares where people wish people involved in systemd would be run over by a bus or just accusations of incompetence.

This is yet another dramatic event affecting the Debian project in recent months. The adoption of systemd has been extremely controversial, even going so far as to result in calls for Debian to be forked. There have been other problems as of late, too, ranging from a serious bug breaking Wine just days before the Jessie freeze deadline, to the possibility of Debian GNU/kFreeBSD being dropped from Debian 8. And it was only just over a week ago that Joey Hess — another longtime Debian contributor — left the project, citing the "very unhealthy directions" that Debian has been led in lately.

Is the internal tension and strife caused by systemd about to tear the Debian project apart? Recent events such as the aforementioned have suggested that this is becoming more and more of a possibility. The repercussions of this drama will no doubt be felt wide and far, given Debian's own popularity, as well it forming the basis of other major Linux distros such as Ubuntu and Linux Mint.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by jmorris on Tuesday November 18 2014, @07:37AM

    by jmorris (4844) on Tuesday November 18 2014, @07:37AM (#117150)

    No. I'm typing this on a Thinkpad running F20. PulseAudio is f*ck*d. It has been f*ck*d for years and years on pretty much every platform I have had the misfortune to use it.... which because RH and the GNOMEs rammed it down everyone's throat is almost everywhere; exactly like systemd. Years have passed and I'm sick and damned tired of listening to excuses for that useless piece of crap that you can't get rid of without a week of intense effort. Just because someone might have a bluetooth headset and want to 'seamlessly' (yea, that will be the day) transition the stream between their headset and the speakers we have all had to suffer broken audio for almost a decade now.

    Drop onto the docking station, a couple of RANDOM outputs will mute themselves. Suspend and guess what happens? Undock and guess what happens. Launch the PulseAudio Graphic EQ plugin and GUESS WHAT HAPPENS! While you could attribute the dock and power management related ones to potential kernel bugs, the EQ doing exactly the same thing kinda gives the game away.

    Better, since I ditched Gnome3 for Mate there isn't even a graphical tool remaining (unsure if there is one in Gnome but there migh) that can even manipulate the actual hardware volume controls, only pulse. All I have found is alsamixer in a terminal window. (Although the GUI alsamixer would be viable too with the -c0 switch... since it has no graphical way to select the card to control and defaults to pulse.)

    No, I will never allow Pulse, Networkmanager or systemd near a production server. Never. When Debian becomes unusable I'll look for a fork. If there isn't one Slackware. Should it too fall to the forces of darkness BSD will always be there.

    Because I'm in both dissenting camps. systemd is a bad idea that isn't likely to ever work reliably and securely. Or at least not work in the twenty or so years I have left before retirement.