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: 2) by HiThere on Monday November 17 2014, @07:52PM

    by HiThere (866) Subscriber Badge on Monday November 17 2014, @07:52PM (#116916) Journal

    No. *MOST* of the criticisms are unverifiable. *SOME* of the criticisms appear valid. Some also appear dubious.

    The real point, though, is that there has been essentially nothing posted that seems to me a valid reason to choose it. I don't really have an iron in this fire, as I've chosen to revert to Debian stable while waiting for the dust to settle. My bias is such that I have ensured (via update parameters) that I won't install systemd by accident. It's also true, however, that I ran an install of Ubuntu 14.04 on this system after Debian testing crashed with the install of systemd, and it worked without problems....and I saw no advantages. (But would I? I'm not much of a sysadmin, I only run my own system and that of my wife.)

    For me the problem is that it's harder to understand what systemd is doing. I spent a lot of time over the years picking up managing sysv-init...I don't want to need to repeat that. (OTOH, this argument is often used by people who are using clunky systems when a sleek automated replacement comes out. I sure wouldn't want to go back to a hand cranked starter, even though it was easier to repair when it broke.)

    So. I'm biased against systemd, but not strongly. I just haven't heard or experienced anything that would make me think it's a good decision.

    --
    Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Monday November 17 2014, @11:23PM

    by Anonymous Coward on Monday November 17 2014, @11:23PM (#116992)

    Cut the crap, son. This isn't reddit. We aren't fucking morons here.

    The criticism against systemd is valid, and you know it.

    • (Score: 0) by Anonymous Coward on Tuesday November 18 2014, @03:54AM

      by Anonymous Coward on Tuesday November 18 2014, @03:54AM (#117094)

      Exactly, this is why we can't have nice things. That sort of name-calling has no place in a technical discussion, and it raises the question of if you are a mean kid, or part of an astroturfing FUD campaign.

      • (Score: 0) by Anonymous Coward on Tuesday November 18 2014, @04:15AM

        by Anonymous Coward on Tuesday November 18 2014, @04:15AM (#117101)

        There's nothing to discuss here. Systemd is full of technical flaws. Cry "conspiracy theory!!@!@!" all you want. None of that will change the fact that systemd is broken software that has no place in Debian, or any other serious Linux distro.

    • (Score: 2) by janrinok on Tuesday November 18 2014, @09:52AM

      by janrinok (52) Subscriber Badge on Tuesday November 18 2014, @09:52AM (#117174) Journal

      So please enlighten us all and explain what all the 'valid criticisms' are. I don't just want bald statements that cannot be substantiated, but an intelligent and technical discourse on the problems as you perceive them. I'm using it and it works - I don't see a reason to change to it, but that is simply a personal view and not 'valid criticism'.

      • (Score: 0) by Anonymous Coward on Tuesday November 18 2014, @12:42PM

        by Anonymous Coward on Tuesday November 18 2014, @12:42PM (#117197)

        If you're discussing this matter, then you should already be aware of the criticism of systemd. If you aren't, then you should probably not participate in this discussion until you've done some research.

        Since finding basic information like this is apparently a severe challenge for you, you can start here: http://boycottsystemd.org/ [boycottsystemd.org]

        • (Score: 2) by janrinok on Tuesday November 18 2014, @06:44PM

          by janrinok (52) Subscriber Badge on Tuesday November 18 2014, @06:44PM (#117348) Journal

          Thank you AC, you have made my point perfectly.

          I didn't ask what other people dislike about it - I asked what the previous poster didn't like, why he didn't like it, and what he felt it stopped him from doing. I'm using it and I have no problems whatsoever with it. It works, I do not think that I will convert my other system over to it because I cannot see any advantages, but the binary logs are not a problem, the all-encompassing dependencies are not a problem. In fact, I haven't got any problems with it. Others may have - I haven't - and I asked for the previous poster's views. Not some regurgitated information about why someone else doesn't like it.

  • (Score: 2) by Arik on Saturday November 29 2014, @02:25PM

    by Arik (4543) on Saturday November 29 2014, @02:25PM (#121107) Journal
    " I sure wouldn't want to go back to a hand cranked starter, even though it was easier to repair when it broke."

    Even that really depends on the application. An electric starter is very convenient in my car, which carries it's own battery and charges said battery whenever I drive. It's true if the car sits for a very long time it might cause a problem, but that's remote, unlikely, and already 'covered' in the sense of having a battery charger handy as well. And it's true it's more complicated to fix when it breaks - but there are several stores nearby or online that will replace the whole unit for a reasonable price, so again that's covered in a sense ahead of time.

    On the other hand an electric starter for the generator at the hunting cabin would be a very bad idea. There, I will stick to my hand crank, thank you very much, and I don't much care if hipsters mistake me for a luddite as a result.
    --
    If laughter is the best medicine, who are the best doctors?