Stories
Slash Boxes
Comments

SoylentNews is people

posted by n1 on Sunday September 28 2014, @06:27AM   Printer-friendly
from the yet-another-systemd-story dept.

Controversy is nothing new when it comes to systemd. Many people find this new Linux init system to be inherently flawed in most ways, yet it is still gaining traction with major distros like Arch Linux, openSUSE, Fedora, and soon both Ubuntu and Debian GNU/Linux. The adoption of systemd for Debian 8 "Jessie" has been particularly fraught with strife and animosity.

Some have described the systemd adoption process as having been a "coup", while others are vowing to stick with Debian 7 as long as possible before moving to another distro. Others are so upset by what they see as a complete betrayal of the Debian and open source communities that there is serious discussion about forking Debian. Regardless of one's stance toward systemd, it cannot be argued that it has become one of the most divisive and disruptive changes in the long history of the Debian project, threatening to destroy both the project and the community that has built up around it.

 
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: 0) by Anonymous Coward on Monday September 29 2014, @03:50AM

    by Anonymous Coward on Monday September 29 2014, @03:50AM (#99448)

    I was just able to completely purge systemd from Debian installation in Sid and use sysvinit-core instead.

    init
      --\ PreDepends (1)
            --\ systemd-sysv | sysvinit-core | upstart
    id systemd-sysv 215-4 -73.7 kB
    pd systemd-sysv 215-5
    p sysvinit-core 2.88dsf-53.2
    p sysvinit-core 2.88dsf-53.4
    pi sysvinit-core 2.88dsf-55.3 +254 kB
    p upstart 1.11-4

    Where is this "systemd is everywhere"? Don't use it. Don't use GNOME, I don't. I'm using fluxbox and starting X with startx from console. Now, if you want some notifications about volume mounting and stuff like that, then yes, you probably need systemd for it. And the reason is no one cares enough to provide an alternative with similar functionality.

    So, there are 3 choices,

    1. Use systemd and have functionality you like
    2. Don't use systemd and don't have functionality (because you don't care about it anyway)
    3. Cry on forums because world doesn't listen to you

    Anyway, here's the entire removal of systemd in Debian,

    --\ Packages to be installed (1)
    ci sysvinit-core +254 kB 2.88dsf-55.3
    --\ Packages to be removed (11)
    idA colord -879 kB 1.2.1-1 1.2.1-1
    idA gvfs -565 kB 1.22.0-1 1.22.0-1
    id gvfs-daemons -682 kB 1.22.0-1 1.22.0-1
    id libpam-systemd -304 kB 215-4 215-5
    id policykit-1 -337 kB 0.105-6.1 0.105-7
    id policykit-1-gnome -820 kB 0.105-2 0.105-2
    id systemd -12.0 MB 215-4 215-5
    id systemd-shim -47.1 kB 8-2 8-2
    id systemd-sysv -73.7 kB 215-4 215-5
    id systemd-ui -222 kB 3-2 3-2
    id udisks2 -1,525 kB 2.1.3-3 2.1.3-3

    In the end, I'm keeping Systemd for now, but I removed some of the cruft here that I don't use anyway (like udisk2, gvfs, colord, etc.)