Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Monday January 21 2019, @07:14AM   Printer-friendly
from the their-way-or-the-highway dept.

Michael Biebl, long-time maintainer of systemd for Debian (2010 or earlier, based on changelog.Debian.gz), is taking undetermined holidays from packaging it. The e-mail was short:

Will stop maintaining systemd in debian for a while.

What's going on is just too stupid/crazy.

This takes place after he discussed a bug in which he expected systemd to respect local settings, and not rename network devices:

@yuwata a default policy like /lib/systemd/network/99-default.link should never trump explicit user configuration.

Later he seems surprised about how things roll there:

I'm amazed that I have to point this out....

The issue is locked currently, and also archived just in case, so everyone can read the initial report and the replies he got.

Opinion: It seems distribution developers are starting to get the stick too, not just users with their "errors" (taken from a reply). Will distributions finally wake up or is that they don't still grok the attitude of projects like this? [Or is it something else? --Ed.]


Original Submission

 
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: 5, Insightful) by MadTinfoilHatter on Monday January 21 2019, @09:37AM (5 children)

    by MadTinfoilHatter (4635) on Monday January 21 2019, @09:37AM (#789490)

    A major Linux distribution mandating packages support a choice of inits would be welcome.

    Easier said than done. Making a Linux distro that allows you to choose between different kinds of normal init systems, e.g. sysv, runit, epoch, et.c. isn't that hard, because those init systems are just init systems. Systemd, on the other hand extends it's slimy tentacles to who-knows-where, which means that the only kind of distro that can offer this kind of choice is something like Gentoo, where the users himself builds all the binaries. Gentoo in fact does just this - you can choose systemd if you want to, even though it's not the default. (Funtoo could do the same, but their stance is that systemd is a turd that they're not going to waste any time supporting.)

    Because of all the systemd bindings to packages that have nothing to do with init (which BTW is the single biggest architectural flaw of systemd), regular binary package distros pretty much have to make a choice, whether to support systemd while making everybody else 2nd class citizens where things may or may not work, or whether to support normal UNIXy init systems, and give systemd the middle finger. In my opinion more distros need to do the latter, and evict the cuckoo from the nest before it destroys everything else in it.

    Starting Score:    1  point
    Moderation   +3  
       Insightful=2, Informative=1, Total=3
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   5  
  • (Score: 2, Funny) by Anonymous Coward on Monday January 21 2019, @01:28PM (2 children)

    by Anonymous Coward on Monday January 21 2019, @01:28PM (#789558)

    systemD totally needs a bit-torrent subsystem : ]

    • (Score: 0) by Anonymous Coward on Tuesday January 22 2019, @03:30AM (1 child)

      by Anonymous Coward on Tuesday January 22 2019, @03:30AM (#789949)

      Just run KodiD, fully loadeD, on your RaspDberryDPiD. Use a HDMID 2.2D cable to connect it to your SmartD TVD and you're good to go.

      • (Score: 0) by Anonymous Coward on Friday January 25 2019, @09:51PM

        by Anonymous Coward on Friday January 25 2019, @09:51PM (#792039)

        Hate smart tvs.

  • (Score: 4, Interesting) by digitalaudiorock on Monday January 21 2019, @02:22PM (1 child)

    by digitalaudiorock (688) on Monday January 21 2019, @02:22PM (#789582) Journal

    Because of all the systemd bindings to packages that have nothing to do with init (which BTW is the single biggest architectural flaw of systemd), regular binary package distros pretty much have to make a choice, whether to support systemd while making everybody else 2nd class citizens where things may or may not work, or whether to support normal UNIXy init systems, and give systemd the middle finger. In my opinion more distros need to do the latter, and evict the cuckoo from the nest before it destroys everything else in it.

    Absolutely. What's more they need to do the same for any software projects that decide to require systemd. The fact that the open source community didn't dump Gnome on the trash heap of software history when they did so has always astonished me.

    • (Score: 0) by Anonymous Coward on Monday January 21 2019, @07:04PM

      by Anonymous Coward on Monday January 21 2019, @07:04PM (#789699)

      The fact that the open source community didn't dump Gnome on the trash heap of software history when they did so has always astonished me.

      Some of us did. You'll never get 100% - the maintainers at least are unlikely to dump their own stuff - and it sounds like I'm not alone, but I don't know where the general consensus on gnome ended up.