Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Sunday December 21 2014, @04:54PM   Printer-friendly
from the show-stopper-or-rare-event? dept.

Noted Linux expert Chris Siebenmann has described two catastrophic failures involving systemd.

One of the problems he encountered with systemd became apparent during a disastrous upgrade of a system from Fedora 20 to Fedora 21. It involved PID 1 segfaulting during the upgrade process. He isn't the only victim to suffer from this type of bad experience, either. The bug report for this problem is still showing a status of NEW, nearly a month after it was opened.

The second problem with systemd that he describes involves the journalctl utility. It displays log messages with long lines in a way that requires sideways scrolling, as well as displaying all messages since the beginning of time, in forward chronological order. Both of these behaviors contribute to making the tool much less usable, especially in critical situations where time and efficiency are of the essence.

Problems like these raise some serious questions about systemd, and its suitability for use by major Linux distros like Fedora and Debian. How can systemd be used if it can segfault in such a way, or if the tools that are provided to assist with the recovery exhibit such counter-intuitive, if not outright useless, behavior?

Editor's Comment: I am not a supporter of systemd, but if there are only 2 such reported occurrences of this fault, as noted in one of the links, then perhaps it is not a widespread fault but actually a very rare one. This would certainly explain - although not justify - why there has been so little apparent interest being shown by the maintainers. Nevertheless, the fault should still be fixed.

 
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: 3, Interesting) by novak on Sunday December 21 2014, @07:16PM

    by novak (4683) on Sunday December 21 2014, @07:16PM (#128084) Homepage

    While you're correct and they do need to put the brakes on hard, and release "when it is ready," I think it's pretty obvious that's not going to happen. Gnome3 and Pulseaudio both skated happily into the last release as defaults, and those are pretty broken, hated pieces of software. Systemd is just the formalization of their commitment to mainstream over quality.

    --
    novak
    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 3, Funny) by digitalaudiorock on Sunday December 21 2014, @07:55PM

    by digitalaudiorock (688) on Sunday December 21 2014, @07:55PM (#128100)

    While you're correct and they do need to put the brakes on hard, and release "when it is ready," I think it's pretty obvious that's not going to happen.

    ...not more than releasing "when it is needed" which would be "never"...

    • (Score: 2) by novak on Sunday December 21 2014, @08:11PM

      by novak (4683) on Sunday December 21 2014, @08:11PM (#128110) Homepage

      Yeah, by "when it is ready" I meant Debian 8, not systemd. I can agree that systemd will never be needed and probably never high quality enough to deserve to be in a real linux distro.

      My point is that Debian has acting questionably for years, and now they are clarifying that they do indeed intend to adopt whatever comes down the pike instead of slashing anything that fails to meet their standards.

      Hopefully enough people who remember the old debian will support devuan and they'll get some traction.

      --
      novak
      • (Score: 0) by Anonymous Coward on Monday December 22 2014, @11:15AM

        by Anonymous Coward on Monday December 22 2014, @11:15AM (#128281)

        The debian faggots should be beaten. They are SJW fucks who ruined something good. They infiltrated and took over.

  • (Score: 2) by sjames on Monday December 22 2014, @04:16AM

    by sjames (2882) on Monday December 22 2014, @04:16AM (#128222) Journal

    I would at least like to see them add an option to the installer to choose init systems. Currently, I can install Jessie with sysV but only by using expert mode and opening a shell to switch init packages in the target.