Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Tuesday December 10 2019, @02:06PM   Printer-friendly

Debian Developers Take To Voting Over Init System Diversity

It's been five years already since the vote to transition to systemd in Debian over Upstart while now there is the new vote that has just commenced for judging the interest in "init system diversity" and just how much Debian developers care (or not) in supporting alternatives to systemd.

Due to Debian developers having differing opinions on handling non-systemd bugs in 2019 and the interest/commitment to supporting systemd alternatives in the scope of Debian packaging and various related friction points, they've taken to a new general resolution over weighing init system diversity.

The ballot is available on-line. The choices are:

Choice 1: F: Focus on systemd
Choice 2: B: Systemd but we support exploring alternatives
Choice 3: A: Support for multiple init systems is Important
Choice 4: D: Support non-systemd systems, without blocking progress
Choice 5: H: Support portability, without blocking progress
Choice 6: E: Support for multiple init systems is Required
Choice 7: G: Support portability and multiple implementations
Choice 8: Further Discussion

[Ed. note: I'm not sure what the letters after the choice numbers indicate, nor do I know where "C" disappeared to.]


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: 4, Informative) by Bot on Tuesday December 10 2019, @07:55PM (3 children)

    by Bot (3902) on Tuesday December 10 2019, @07:55PM (#930736) Journal

    You are the user, there is written "support". So your objection as a dev might be I don't want to support many init systems.

    Debian, before systemd and COCs, was adding support for different KERNELS. Why? because it is called the universal operating system. So multiple init support, especially in terms of removing BAKED IN dependence on systemd, should be one of the main goals of debian. That they have trouble achieving it for lack of dev power (everybody occupied with making their systemd work I guess?) is another matter.

    --
    Account abandoned.
    Starting Score:    1  point
    Moderation   +2  
       Interesting=1, Informative=1, Total=2
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 2) by RS3 on Tuesday December 10 2019, @10:08PM (2 children)

    by RS3 (6367) on Tuesday December 10 2019, @10:08PM (#930811)

    It's amazing how confusing language can be. Let me try this: to me, the wording "support for multiple init systems" means "one installed OS can have multiple init systems installed at once." Does that make more sense? And maybe that could exist, and a boot menu would allow choosing which init system to use for that boot.

    I'd rather the wording be: at installation, choose one init system from many available.

    • (Score: 3, Informative) by Bot on Tuesday December 10 2019, @11:03PM (1 child)

      by Bot (3902) on Tuesday December 10 2019, @11:03PM (#930838) Journal

      Mxlinux in fact has sysvinit and systemd as boot options.

      --
      Account abandoned.
      • (Score: 2) by RS3 on Wednesday December 11 2019, @03:52PM

        by RS3 (6367) on Wednesday December 11 2019, @03:52PM (#931082)

        Thank you so much, I'll try it. I had tried "mepis" 8 or so years ago, before systemd became malignant. Recently when I saw systemd listed as part of Mxlinux I moved on, not knowing it was optional. Generally when a distro starts including systemd, my inclination is to steer clear because they're wasting valuable time and resources on a tumor. My fear with Mxlinux is that systemd will become defacto, but I'll try it...