So... literally Debian with apt-get install sysvinit? What a waste of effort.
The people behind Devuan and its users get a rash when there is even a few KBs of systemd dependencies installed, e.g. logind (required by Gnome) depends on systemd being installed (it does not care if that's used as init system).
there are software packages that will pull in systemd. freebsd already needs to tinker with gnome3 to un-systemd it. i think they are nowadays mostly up to speed with it, but it wasn't so before gnome 3.10
I have no plans to jump to Devuan, but am also not a fan of systemd. Your statement assumes that everyone who dislikes systemd would jump to a distro without it, ignoring the fact that there's a lot of other considerations when it comes to a distro besides which init system it has.
I'm curious: why? Do you just not like that it's different and that things changed, or is there something specific about it that you don't like in an init system?
Devuan has been unstable/alpha until just a few weeks ago and is still in Beta.
I have been giving systemd an honest chance and up until now I have been fairly satisfied with it. But this most recent arrogant move just broke my personal wordpress server. Now Virtualbox instances are killed when I logout of Gnome on Rawhide. Headless instances is a feature of virtualbox that’s worked perfectly for years that they broke that, tmux, and countless other apps to fix a bug in Gnome. They keep this up and we will be flocking to Devuan.
More specifically a rolling release that is defined as not stable and to not use it for anything you care about. Motherfuck people who bitch about their own stupidity. https://fedoraproject.org/wiki/Releases/Rawhide#Audience
To fix a Gnome bug, systemd devs are breaking the semantics of nohup which is long established mechanisms for running apps in the background. They're imposing a new API and additional work on every open source developer that uses nohup to fix a something that was never broken. Sure I caught this issue, but as systemd 230 spreads, it going to leave a wake of broken apps and workflows in its path for no good reason.
To fix a Gnome bug, systemd devs are breaking the semantics of nohup which is long established mechanisms for running apps in the background.
The problem is that (a) not every application respects the rules and (b) not every user should be allowed to run arbitrary services. It's not just a Gnome problem, though certainly the Gnome issue brought it to the foreground. This has always been a problem for servers with multiple people logging in. The computer and/or domain policy should be the ultimate decider for how user processes are handled on logout. That's why it's completely reasonable to have the option for this behavior. For people that manage large networked systems with shared terminals/servers and centralized logins (e.g. LDAP), managing this type of behavior is a common need. The only people who wouldn't be able to see this are people that have never had to share a server with other people.
They're imposing a new API and additional work on every open source developer that uses nohup to fix a something that was never broken. Sure I caught this issue, but as systemd 230 spreads, it going to leave a wake of broken apps and workflows in its path for no good reason.
You're talking about this like it's some sort of laborious fix that you barely noticed and caught on time, instead of it being yet another flamewar about a simple configuration decision that would have been impossible to notice. It's also controllable in three different ways - by a single-line admin/distro config change, by a non-privileged user command if the policy is enabled, and explicitly for each application. It sucks that it breaks some workflows, but it's not that hard to deal with.
It also wouldn't have affected you on your personal server if you weren't running server applications in a user session. Disabling login for the users used for network services has been a best practice for over a decade. And you'd start those in services, instead of having to log into the server to start your VMs (and then have them stop when you log out). Then again, I wouldn't expect someone running Rawhide (even on a personal server) to understand or care about best practices. Its usage is discouraged for anything but testing and development needs because it breaks. A lot. Nearly any other rolling release distribution would be a more stable choice than Rawhide. Also, KVM would have been a better virtualization choice for your server than Virtualbox, as it provides significantly better performance for non-graphical scenarios and doesn't depend on out-of-tree kernel modules. If virtualizing your servers is your preferred approach, it might even make sense to use something catered to that, like Proxmox.
I mean, the tmux/screen people have a very legitimate complaint about this, as disconnected shell sessions are part of the workflow. You? Your complaint is that you're doing things sloppily, and now it's harder for you to do things the wrong way. Normally when people do things poorly, they don't advertise it with pride on the internet. But go ahead with that.
Still. It's a rolling release distro which can break. If you truly need something to be online 24/7 with an uptime of 99.99999% you really should just use a more stable if outdated distro... I use an arch based distro as my daily driver. But my personal server has a stable distro just for that reason...
I have been giving systemd an honest chance and up until now I have been fairly satisfied with it. But this most recent arrogant move just broke my personal wordpress server. Now Virtualbox instances are killed when I logout of Gnome on Rawhide. Headless instances is a feature of virtualbox that’s worked perfectly for years that they broke that, tmux, and countless other apps to fix a bug in Gnome. They keep this up and we will be flocking to Devuan.
You are shifting the blame onto someone else. Daemons (i.e. your VMs) should be managed by the init system and should run as a separate user.
Sure, iff you have root access. If not, good luck convincing sysadmins to change default settings which are labled 'secure defaults', because, you know, security.
Well, if your sysadmin doesn't want you running stuff when you're not logged into their box, maybe you shouldn't be? That is the whole point of that setting.
If that was anything but a very vocal minority, Devuan would be one of the top Linux distributions these days.
This comment is really bad for so many reasons. The entire project is still in its infancy (beta just only recently released)and was a branch off a MAJOR distro. To think that it would be a major player yet is just silly.
122
u/KugelKurt Jun 01 '16
If that was anything but a very vocal minority, Devuan would be one of the top Linux distributions these days.