4 ms·

Lennart Poettering

• LEARAX 6y ago
  Perhaps as a counterpart to Nintendo's Wario, complete with maniacal laughing.
• Shared404 6y ago
  One in ten times you try to cross the finish line you get [ * ]A stop job is running for ... [ *]A stop job is running for ... [* ]A stop job is running for ... and can't cross the line. Side note: While I joke about this, I respect Poetterings determination and engineering skill, even if I disagree with him.
  • chungy 6y ago
    You just made me laugh hard. Good job :D
    • nitrogen 6y ago
      Wait, it's not just my PC that does that? Why is this error message so vague and self contradictory?
      • Shared404 6y ago
        My understanding is that it usually occurs whenever a daemon is unable to shut down correctly, so it locks up the entire process of shutting down. The networking daemons were what used to cause it when I had Fedora installed, iirc. I would start looking there. As for why it's so vague and self contradictory, I couldn't say.
        • smichel17 6y ago
          Yes, the bad part of this message is not that it hapoens, but that it's so hard to find out what is actually causing it.
          • Shared404 6y ago
            Definitely agree there.
    • Shared404 6y ago
      Glad to hear I could make your day a little better :)
  • einpoklum 6y ago
    > Mr. Poettering's engineering skill I also highly respect the engineering skill of the designers of the Vasa: https://en.wikipedia.org/wiki/Vasa_(ship) https://en.wikipedia.org/wiki/Vasa_(ship)
    • Shared404 6y ago
      SystemD has issues. I don't particularly like it, and I only have a couple machines that use it. I much prefer OpenRC, which is what I use while provisioning new systems. That being said, Poettering created software that A) Is much better than I could make. B) Is used by many, many, many, people in production, without showstopper issues. I will not deny that he deserves at least some amount of respect for what he has accomplished, including from an engineering perspective.
      • einpoklum 6y ago
        I don't know what kind of software you make, but SystemD's issues are not merely bugs and misfeatures (there are those) - the fundamental design is technically and community/society-wise wrong. It is not the right path to draw more and more system functionality into a single codebase (and partially into a single process). That's not exactly the same as the Vasa, but there too - fundamental principles were ignored while other aspects of the design were impressive.
        • Shared404 6y ago
          > I don't know what kind of software you make Mostly hacky stuff that does what I need, and not much more. Definitely nothing professional,at least that's relevant to this. I agree with what you are saying. I am by no means an expert, but I have read/studied enough to know that I disagree with almost all of the philosophy behind SystemD, and have used it enough that I know it does not work properly all the time. Everything above also applies to Windows. That doesn't change the fact that both are impressive, though flawed (more flawed than most software I use, imho) pieces of software. Despite all of it's flaws, SystemD has been proven through use. I don't like it, but I have to acknowledge it's capabilities.