1. That link is dead ("Access Denied")
2. The bug is not in Devuan, it's in something called refractainstaller, which is used for Devuan live-ISOs. If you just install Devuan that doesn't happen.
3. With a refractainstaller live-ISO, and if you chose to not define a root user, then this bug manifests.
The bug seems to have lingered for so long because despite being rather obvious (i.e. you can just become root) because nobody tried to secure a live-ISO-based system, which is something you typically use as a "rescue disk" or to diagnose hardware.
So - is this a screw-up? Yes. Does it reflect significantly on Devuan as a project? Not really.
To draw a parallel - the fact that systemd has had bugs which other init systems didn't, or had gotten over decades before, does not mean it's an undesirable project. My (and many people)'s problems with systemd regard its fundamental design philosophy, as well as its governance/behavior as a software project.
Works for me.
>2. The bug is not in Devuan, it's in something called refractainstaller, which is used for Devuan live-ISOs. If you just install Devuan that doesn't happen.
From the link:
>>When you download and install the desktop-live Devuan image, you will be prompted to create a user account at the end of the process.
... ie it seems to be talking about the normal process for installing a Linux distro - you make a live CD, boot it, and run the installer.
What's the impact of having systemd (or not) for the everyday layman like me that just uses Visual Studio Code to build flutter apps ?
A lot of people are mad about it for a lot of reasons, but if you're not a system administrator, it's probably better to stick with systemd, since it's what most of the linux community has standardized on, and thus it's much easier to find information online about using those systems.
When you add in things like Podman and it's use of systemd it's overall not a bad thing at all.
And even, probably, if you are.
Compared to initrd, after Debian upgrading to systemd, the system boots slightly faster and shuts down slightly slower (or same speed, depends really what you run)
By "unencumbered by systemd" they mostly mean "works worse". We've removed tens of thousands lines of fixes for "easy", "simple" sysv scripts when we upgraded our servers to version that runs systemd.
Basically, don't worry about it.
It's an idealogical flamewar, that in most cases is without impact.
The binary format of the log file still seems to me to be a bad idea - it introduces corruptibility and complexity to a vital service that should be simple and uncorruptible.
If a failing system starts to do weird things, plain text append only logging is preferable.
Nothing. I run Void Linux Musl with XFCE and I have no issue running Steam and other big glibc programs in Flatpak, docker, etc.