You are not logged in.
As Debian 11 moves closer to Devuan (init diversity). Is there any reason to stay on Devuan?
Hi everybody!
Seems like Devuan was sucessful and Debian 11 (Bullseye) will be released with runit and SysV, probably even with OpenRC. Together with a few shim-packages to avoid the installation of systemd dependencies. Debian 11 is now in testing and can be used without systemd or its libraries.
I was wondering if there is any reason to stick with Devuan when Debian 11 is released. Did i miss something? Is there still a reason to use Devuan instead of Debian 11?
Background info: We had a pretty interesting conversation on reddit about this topic. see here:
Reddit Debian Sub
I wanted to hear your opinions on this.
Offline
Now I know why I don't hang out on reddit.
Trust is a fragile thing and not easy to repair.
If you hang around here for a while maybe you will understand why Devuan is so special . . . or maybe not. It's about more than code . . .
Online
You may also need to install orphan-sysvinit-scripts for some compatibility.
YMMD!
I used Debian since its earliest days even before it had toy story names.
My relation with Debian now:
Breaking trust can be done in a blink.
Regaining it takes years.
Last edited by yeti (2021-02-24 10:16:21)
*𝚛𝚒𝚋𝚋𝚒𝚝!*
Offline
Now I know why I don't hang out on reddit.
Trust is a fragile thing and not easy to repair.
If you hang around here for a while maybe you will understand why Devuan is so special . . . or maybe not. It's about more than code . . .
yes sadly the reddit community was/is always heavily biased towards a pro-systemd view. As Debian opens the door to other init systems these opinions will hopefully change. Thanks to you Devuan community. I appreciate that.
I also dont think the debian votings regarding systemd were fair and many users got mistreated for their opinion in the linux communites. It always felt like a political thing to me. Like a powergrab.
But from a technical standpoint alone: Is there still any technical advantage over debian 11? What are the reasons to keep Devuan when Debian has the same features? Just trying to get some infos to make my decision.
Offline
You may also need to install orphan-sysvinit-scripts for some compatibility.
YMMD!
I used Debian since its earliest days even before it had toy story names.
My relation with Debian now:
Breaking trust can be done in a blink.
Regaining it takes years.
So its "only" for personal reasons now? There is no technical reason left?
I know we have been hurt a lot in the linux communities the last 5-10 years. And it gets personal very fast. But it seems like we have won for now. Building up the trust again will take a while.
Offline
yeti wrote:You may also need to install orphan-sysvinit-scripts for some compatibility.
YMMD!
I used Debian since its earliest days even before it had toy story names.
My relation with Debian now:
Breaking trust can be done in a blink.
Regaining it takes years.So its "only" for personal reasons now? There is no technical reason left?
I know we have been hurt a lot in the linux communities the last 5-10 years. And it gets personal very fast. But it seems like we have won for now. Building up the trust again will take a while.
" But it seems like we have won for now."
The two operative phrases in this sentence are 'it seems' and 'for now'. TBH, I don't believe there's been any change of heart at Debian, and if an 'official' sysvinit version of Debian is released, I'll bet it turns out to be half-assed - rough edges, need for fiddling and workarounds, some things just not working, etc.
So for me, it's NOT 'only' for personal reasons - though those reasons remain important. I simply do not trust Debian to do as technically good a job as Devuan. It will be a sloppy afterthought, grudgingly offered.
Offline
I can see how Debian might choose some level of sanity by providing support for sysvinit again, but the heavy lifting of making that possible would have been done in a separate environment (i.e., Devuan). It's clear that such maintenance and support wouldn't happen within the Debian world directly.
This space intentionally left blank.
Offline
I believe the biggest difference between devuan and debian as it stands now is that devuan does not depend on systemd shims? These other inits that debian may be supporting still rely on systemd shims afaik?
Offline
Debian 11 (Bullseye) will be released with runit and SysV, probably even with OpenRC. Together with a few shim-packages to avoid the installation of systemd dependencies.
The runit-init package has been removed from the dependency list for the init metapackage in Debian bullseye so technically only systemd and sysvinit are supported. It is possible to use runit-init or openrc-init as PID1 though.
AFAIK there are no "shim-packages to avoid the installation of systemd dependencies", not sure where you're getting that from. Perhaps provide a citation?
These other inits that debian may be supporting still rely on systemd shims afaik?
No.
Brianna Ghey — Rest In Power
Offline
I believe the biggest difference between devuan and debian as it stands now is that devuan does not depend on systemd shims? These other inits that debian may be supporting still rely on systemd shims afaik?
afaik devuan also uses stubs/shims to resolve unmet systemd dependencies (see This Thread from a Devuan-user). I am not very knowledgeable on this topic. Maybe somebody here can give us some insights how big the differences are between devuan and deb 11?
Last edited by Morty (2021-02-24 16:12:05)
Offline
Morty wrote:Debian 11 (Bullseye) will be released with runit and SysV, probably even with OpenRC. Together with a few shim-packages to avoid the installation of systemd dependencies.
The runit-init package has been removed from the dependency list for the init metapackage in Debian bullseye so technically only systemd and sysvinit are supported. It is possible to use runit-init or openrc-init as PID1 though.
AFAIK there are no "shim-packages to avoid the installation of systemd dependencies", not sure where you're getting that from. Perhaps provide a citation?
dice wrote:These other inits that debian may be supporting still rely on systemd shims afaik?
No.
HoaS, do you know if sysv be will be offered as an option in the bullseye installer?
Offline
I know it's an option for live-build but I don't think it will be in the installer.
Try the alpha3 ISO image for bullseye and report back, that should be pretty close to the release version.
Brianna Ghey — Rest In Power
Offline
I know it's an option for live-build but I don't think it will be in the installer.
Try the alpha3 ISO image for bullseye and report back, that should be pretty close to the release version.
I'm pretty shocked that a bunch of redditors got it all wrong. Shocked I tell you.
Offline
I know it's an option for live-build but I don't think it will be in the installer.
Try the alpha3 ISO image for bullseye and report back, that should be pretty close to the release version.
I will do that.
Offline
Beginning of February I downloaded a current Bullseye netinstall image and installed it in VBox. Can't remember that I got an init choice like in Devuan.
rolfie
Offline
AFAIK there are no "shim-packages to avoid the installation of systemd dependencies", not sure where you're getting that from. Perhaps provide a citation?
i got it from these reddit users
https://old.reddit.com/r/debian/comment … t/gnjulzf/
https://old.reddit.com/r/debian/comment … t/gnmpgxy/
https://old.reddit.com/r/debian/comment … t/gnmp75t/
His detailed answer with instructions (seems like its based on the "libsystemd0" shim-package): https://old.reddit.com/r/debian/comment … d/ewdsjrq/
there is also this mysterious package called "orphan-sysvinit-scripts" which seems like a substitute for some sysd packages. Not sure on that one. https://packages.debian.org/bullseye/or … it-scripts
Last edited by Morty (2021-02-24 16:52:58)
Offline
There used to be a systemd-shim package for the pre-buster versions: https://packages.debian.org/stretch/systemd-shim
That has now been dropped but it isn't needed to run sysvinit, runit-init or openrc-init as PID1 in Debian. MX Linux is using a version of it to allow for co-installation of both systemd and sysvinit-core.
I suppose elogind could be described as a "shim" package, that allows for non-systemd inits to be used in systems that require logind compliance (ie, most desktop environments). The elogind package is only available in Debian thanks to the efforts of the Devuan developers.
Brianna Ghey — Rest In Power
Offline
Sadly, the alpha 3 iso does not have an option for selecting the init system.
Offline
Hello:
Is there any reason to stay on Devuan?
Yes, there are many reasons.
The first: trust
The second: basic common sense
All the other reasons follow these first two.
And like golinux wrote: It's about more than code.
But the question (if there has to be one at all) should be:
Is there any reason not to stay on Devuan?
And the answer is: none whatsoever.
As always, YMMV.
It's just my $0.02
A.
Last edited by Altoid (2021-02-24 18:31:47)
Offline
yes sadly the reddit community was/is always heavily biased towards a pro-systemd view. As Debian opens the door to other init systems these opinions will hopefully change. Thanks to you Devuan community. I appreciate that.
My negative response to that thread was not about the pro-systemd bias. That kind of useless yammering is not an environment in which I want to swim. A complete waste of time.
I also dont think the debian votings regarding systemd were fair and many users got mistreated for their opinion in the linux communites. It always felt like a political thing to me. Like a powergrab.
That is an understatement. I think you might not have been around when all that went down so please educate yourself: Combatting Revisionist History
But from a technical standpoint alone: Is there still any technical advantage over debian 11? What are the reasons to keep Devuan when Debian has the same features? Just trying to get some infos to make my decision.
Yes. We have an amazing team that actually collaborates and solves problems collaboratively with egos left at the door.
Online
That is an understatement. I think you might not have been around when all that went down so please educate yourself: Combatting Revisionist History
oh i am using debian stable and derivatives for over 10 years now and was around when the first "debates" started. My Linux journey started with Ubuntu around 2006. One couldnt overhear these endless dispute pro and contra init-freedom. Just writing about init-alternatives would get us pushed out of linux-communities or downvoted to hell. There is so much bitterness until today that i just dont care anymore.
I can see where these trust issues come from. But i also see that there is some positive progression in this regard. Things are slowly moving in the right direction.
Offline
Morty . . . did you actually read daseins post? A lucid analysis of the first GR vote.
Online
Now I know why I don't hang out on reddit.
Trust is a fragile thing and not easy to repair.
If you hang around here for a while maybe you will understand why Devuan is so special . . . or maybe not. It's about more than code . . .
Yeah, reddit has quite a bit of systemd loving trolls and people who like new technologies regardless of how insecure or freedom restricting they really are.
Even in the linux community there...
And yes, Devuan has standards that make sense. Debian is moving away from that.
If I added Arch to this mix, I would say they are not K.I.S.S friendly anymore.
Systemd goes against keep it simple stupid logic and stability as well. So, Debian and Arch both have some hypocrites in charge eh...
Freedom is never more than one generation away from extinction. Feelings are not facts
If you wish to be humbled, try to exalt yourself long term If you wish to be exalted, try to humble yourself long term
Favourite operating systems: Hyperbola Devuan OpenBSD
Peace Be With us All!
Offline
Morty wrote:Debian 11 (Bullseye) will be released with runit and SysV, probably even with OpenRC. Together with a few shim-packages to avoid the installation of systemd dependencies.
The runit-init package has been removed from the dependency list for the init metapackage in Debian bullseye so technically only systemd and sysvinit are supported. It is possible to use runit-init or openrc-init as PID1 though.
AFAIK there are no "shim-packages to avoid the installation of systemd dependencies", not sure where you're getting that from. Perhaps provide a citation?
dice wrote:These other inits that debian may be supporting still rely on systemd shims afaik?
No.
Okay maybe i should have said transitional packages like runit-systemd, not really a shim just a dummy package?
Edit: thats wrong, seem like runit-systemd is only used to start runit supervision via systemd
how does one use runit-init on debian, like get the services run scripts to work when absent of systemd and sysvinit.
Void linux is easy as
# ln -s /etc/sv/NetworkManager /var/service/
With debian i cant seem to find the service files for networkmanager (and yes i have a debian testing system working with runit-init but network manager not up).
Is it still too early for this under debian and maybe i would need to create the init script myself?
Edit: managed to get network manager going with the help of this page here: https://kchard.github.io/runit-quickstart/
I still dont understand what is going on with debians runit as i get the below output to check dbus and lightdm sv status ?
$ sudo sv status dbus
fail: dbus: unable to change to service directory: file does not exist
sudo sv status lightdm
fail: lightdm: unable to change to service directory: file does not exist
pstree =
~$ pstree
runit─┬─ModemManager───2*[{ModemManager}]
├─NetworkManager───2*[{NetworkManager}]
├─at-spi-bus-laun─┬─dbus-daemon
│ └─3*[{at-spi-bus-laun}]
├─at-spi-bus-laun───3*[{at-spi-bus-laun}]
├─at-spi2-registr───2*[{at-spi2-registr}]
├─avahi-daemon───avahi-daemon
├─colord───2*[{colord}]
├─cron
├─3*[dbus-daemon]
├─2*[dbus-launch]
├─dconf-service───2*[{dconf-service}]
├─elogind-daemon
├─gnome-keyring-d───3*[{gnome-keyring-d}]
├─gnome-keyring-d───2*[{gnome-keyring-d}]
├─gpg-agent
├─gvfs-udisks2-vo───3*[{gvfs-udisks2-vo}]
├─gvfsd─┬─gvfsd-trash───2*[{gvfsd-trash}]
│ └─2*[{gvfsd}]
├─gvfsd-metadata───2*[{gvfsd-metadata}]
├─lightdm─┬─Xorg───9*[{Xorg}]
│ ├─lightdm─┬─xfce4-session─┬─Thunar───2*[{Thunar}]
│ │ │ ├─applet.py
│ │ │ ├─light-locker───3*[{light-locker}]
│ │ │ ├─nm-applet───3*[{nm-applet}]
│ │ │ ├─polkit-gnome-au───2*[{polkit-gnome-au}]
│ │ │ ├─ssh-agent
│ │ │ ├─xfce4-notifyd───2*[{xfce4-notifyd}]
│ │ │ ├─xfce4-panel─┬─panel-10-notifi───2*[{panel-10-notifi}]
│ │ │ │ ├─panel-14-action───2*[{panel-14-action}]
│ │ │ │ ├─panel-6-systray───2*[{panel-6-systray}]
│ │ │ │ ├─panel-8-pulseau───2*[{panel-8-pulseau}]
│ │ │ │ ├─panel-9-power-m───2*[{panel-9-power-m}]
│ │ │ │ └─2*[{xfce4-panel}]
│ │ │ ├─xfce4-power-man───2*[{xfce4-power-man}]
│ │ │ ├─xfdesktop───2*[{xfdesktop}]
│ │ │ ├─xfsettingsd───2*[{xfsettingsd}]
│ │ │ ├─xfwm4───6*[{xfwm4}]
│ │ │ ├─xiccd───2*[{xiccd}]
│ │ │ └─2*[{xfce4-session}]
│ │ └─2*[{lightdm}]
│ └─2*[{lightdm}]
├─packagekitd───2*[{packagekitd}]
├─polkitd───2*[{polkitd}]
├─pulseaudio───2*[{pulseaudio}]
├─rsyslogd───3*[{rsyslogd}]
├─rtkit-daemon───2*[{rtkit-daemon}]
├─runsvdir─┬─6*[runsv───fgetty]
│ └─runsv───NetworkManager
├─saned───saned
├─systemd-udevd
├─udisksd───4*[{udisksd}]
├─upowerd───2*[{upowerd}]
├─wpa_supplicant
├─x-www-browser─┬─Privileged Cont───24*[{Privileged Cont}]
│ ├─2*[Web Content───24*[{Web Content}]]
│ ├─Web Content───17*[{Web Content}]
│ ├─WebExtensions───22*[{WebExtensions}]
│ └─63*[{x-www-browser}]
├─xfce4-terminal─┬─bash───pstree
│ └─2*[{xfce4-terminal}]
└─xfconfd───2*[{xfconfd}]
Last edited by dice (2021-02-25 04:28:52)
Offline
Even so, no reason for me to stop using Devuan. You can't always trust Debian today with their upstream decisions, because you know they're going to fuck something up tomorrow. They're still too heavily influenced by Red Hat, Canonical, and GNOME garbage, and direct pushers of Wayland. Just because you can change your init this time around doesn't mean they're not corrupt anymore. It's a deception.
Devuan is more than just another "Systemd protest" distro. It actually aims for KISS philosophy as much as possible without the pretentious "minimalism" crap. It's everything that Debian should have been for the longest time. The fact that a fork had this much influence says a lot.
Offline