SoylentNews is people
SoylentNews
Almost a year and a half in the making, Devuan no longer is an Alpha-stage Linux distribution. A major site overhaul salutes the rollout of the first Beta release:
https://beta.devuan.org/
Here is an excerpt from an article from The Register on the release:
The effort to create a systemd-free Debian fork has borne fruit, with a beta of "Devuan Jessie" appearing in the wild.
Devuan came into being after a rebellion by a self-described "Veteran Unix Admin collective" argued that Debian had betrayed its roots and was becoming too desktop-oriented. The item to which they objected most vigorously was the inclusion of the systemd bootloader. The rebels therefore decided to fork Debian and "preserve Init freedom". The group renamed itself and its distribution "Devuan" and got [to] work, promising a fork that looked, felt, and quacked like Debian in all regards other than imposing systemd as the default Init option.
[...] Kudos, though, to the group for getting it out there! Now to see if there's really a groundswell of support for the cause of "Init freedom", as the greybeards name their cause.
The inclusion of systemd appears not to be holding rival Linux distros back: our review of Ubuntu 16.04 suggests it will be a speed bump for most users. Our Debian Jessie review said it slices a few seconds off boot times but is removable with little fuss for those who would prefer to go their own way at startup time. ®
How many people have been using this distro out of their worry over systemd's voracious appetite of everything standing between the kernel and the user? What are others using who share similar worries but have turned to other distros?
(Score: 2) by mmcmonster on Friday April 29 2016, @05:25PM
I'm certainly not a big time Linux administrator. Just my own home boxes.
What I've noticed is that when I do a system upgrade which involves switching to SystemD, thing behave funny/badly. Maybe the boot doesn't happen cleanly or samba or another service doesn't get started every time the system boots.
...But, if I do a clean install of the OS and SystemD is installed, everything works entirely fine.
Now, I know I should be more upset that the system upgrade should work smoothly, and if not I should be able to troubleshoot the issues. But frankly, who's got time for that? It's generally faster for me to just nuke the partition and reinstall everything.
I keep copies notes of all the modifications I do on a system anyway, so after a clean install I just read my notes on how to get everything the way I like it.
(Score: 2) by frojack on Friday April 29 2016, @09:11PM
What I've noticed is that when I do a system upgrade which involves switching to SystemD, thing behave funny/badly. Maybe the boot doesn't happen cleanly or samba or another service doesn't get started every time the system boots.
...But, if I do a clean install of the OS and SystemD is installed, everything works entirely fine.
But how much of that is actually systemd related?
Upgrading often gets you totally new software (samba has had massive changes of late) that doesn't always work with your old config files. But I bet you retained you old config files when upgrading (cuz that's why people upgrade after all).
I've had the same struggle for 10 years when updating in place, well before the advent of systemd. Fresh installs are just about always better.
No, you are mistaken. I've always had this sig.