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. "

Comments

Finally

[thegarbz]

Now can we please stop the flaming and can all those systemd haters just go use a distro for them and leave the rest of the internet alone please?

This was the whole point of open source. If something is wanted then it is usually developed. If it doesn't work for some reason, support the guys who are trying to make it work rather than bitching that someone moved your cheese.

Re:Finally

[thegarbz]

You can't use tab completion

No YOU can't use tab completion. The rest of us have no problems with it under systemd. Better still tab completion in systemd is context sensitive to what command precedes it rather than a stupid list of files in a director.

Plus, it's confusing that Poettering decided to call the system systemd while the command name is systemctl.

Please tell me you don't administer a SAMBA server, or that you didn't attempt to previously start and stop programs by typing sysvinit. You do realise there's a shitload of programs out there that have more than one executable command and aren't actually called the name of the program right? What's more intuitive calling systemd everytime you want to do something? Or calling it something that has context, systemctl and journalctl. Yeah I'm sure that it was really damn intuitive to enable a sysvinit script to run at boot time by calling a program call chkconfig.

Re:Systemd!

[thegarbz]

because they do not think users have the right to do their own simple init-scripts

If you think that then you've never used systemd and not read the manual either. Systemd provides you the choice of scripting your own start and stop of your service. It even has full backwards compatibility traditional sysvinit scripts.

But hey I expected nothing less from another clueless product of the diseased echo chamber that is the anti-systemd crowd.