Slashdot Mirror


Systemd-Free Devuan Announces Its First Stable Release Candidate 'Jessie' 1.0.0 (devuan.org)

Long-time reader jaromil writes: Devuan 1.0.0-RC is announced, following its beta 2 release last year. The Debian fork that spawned over systemd controversy is reaching stability and plans long-term support. Devuan deploys an innovative continuous integration setup: with fallback on Debian packages, it overlays its own modifications and then uses the merged source repository to ship images for 11 ARM targets, a desktop and minimal live, vagrant and qemu virtual machines and the classic installer isos. The release announcement contains several links to projects that have already adopted this distribution as a base OS.
"Dear Init Freedom Lovers," begins the announcement, "Once again the Veteran Unix Admins salute you!" It points out that Devuan "can be adopted as a flawless upgrade path from both Debian Wheezy and Jessie. This is a main goal for the Devuan Jessie stable release and has proven to be a very stable operation every time it has been performed. "

8 of 372 comments (clear)

  1. systemd by Anonymous Coward · · Score: 1, Informative

    is for D lovers

    thankfully Ubuntu lets you easily switch back to Upstart, permanently

    apt-get install upstart-sysv; update-initramfs -u

    1. Re:systemd by Anonymous Coward · · Score: 2, Informative

      apt-get install upstart-sysv; update-initramfs -u

      upstart-sys is not available anymore (*buntu 17.04)

  2. Re:Finally by whoever57 · · Score: 5, Informative

    Personally, I am still trying to figure out what real problem it solves.

    Every claim for systemd seems to be that it solves things that are simply not real issues.

    Anyone?

    The one real problem it seems to solve is: how does RedHat become the company that controls the architecture of all Linux distros.

    --
    The real "Libtards" are the Libertarians!
  3. Re:Finally by Cyberax · · Score: 4, Informative

    Yes, there were multiple votes. Debian's technical committee voted for systemd, OpenSuSE committee voted for systemd, Fedora (that was independent from RedHat at that time) adopted systemd before RHEL.

    Oh, and had there ever been a vote for sysv-init?

  4. Re:Finally by Parker+Lewis · · Score: 1, Informative

    Debian voted to leave SysV and to pick systemd instead of Upstart. No RedHat influence.

  5. Re:Finally by thegarbz · · Score: 5, Informative

    Debian voted to leave SysV and to pick systemd instead of Upstart. No RedHat influence.

    It wasn't a free choice. The fact that Gnome3 requires systemd was a significant influence.

    The choice was made long before any mention of the fictitious Gnome dependency on systemd. It IS ficticious by the way. Gnome has a dependency on one thing: something that provides a DBUS API. systemd-logind is now shipping on many systems so it made sense for Gnome to use it. Notice however Gnome is still available for all non-systemd systems, and BSD, and simply reverts to using gnome-session instead of systemd-logind. The whole dependency thing was just another out of control rage induced verbal vomit out of the echo chamber.

  6. Re:Systemd! by vovin · · Score: 3, Informative

    Yes ... but systemd is a 'happy path' only.
    When something goes wrong then the thing just shits all over itself. Just like everything else pottering has ever touched,
    Just went through the shit this weekend .. CD drive died (no big, wasn't being used for anything) but systemd managed to fubar the whole f'ing system. Fallback to upstart worked fine.

    Other stuff that is a major PITA with systemd: OpenVPN. Whenever I change my .conf file I have to update systemd with some whacky config because it 'caches' my config file in it's own little world. WTF is that about? Dunno but it's enough of a pain that I'll be jumping to the debian boxen to devuan and tossing the ubuntu for the same reason.

    Let CentOS / RHEL 7 deal with all the SystemD crap .. when it's actually decent (after pottering gets bored and real developer fixes all his shit) then maybe it will be the init system that it is being touted as.

  7. Re:Finally by thegarbz · · Score: 1, Informative

    Many of those issues did not require something so intrusive as systemd to solve.

    I only gave you one example. systemd is intrusive due to the very large scope of it's functionality and what it provides. This is also why it won technical challenges when various distributions adopted it.

    Yes, the init.d files are long, but so what? Most users never look at these files

    Users? It wasn't the users crying. Except for when it didn't work and you had to pour through 100 lines trying to figure out why you can run Apache on the command line but it fails to start by script (about the typical problem users experience). No what systemd provides is a far simpler interface for developers and distribution maintainers. None of this go to the developer's website and chose one of 5 100+ line long scripts which may or may not work depending if they are using the same version of your distro. Just a 5 line configuration file for systemd.

    Most of the int.d scripts on my Gentoo system are less than 100 lines, with a lot of them 20-30 lines.

    Congratulation. Maybe that's why Gentoo is still using OpenRC. On distributions that are popular and used by a far wider community than Gentoo, scripts can easily run into the 200+ lines.