Here's the official web page for that announcement at Devuan.org.
https://devuan.org/os/debian-fork/stable-candidate-announce-...
Devuan Jessie 1.0.0 stable release candidate
11–20 of 75 posts
Re: Devuan Jessie 1.0.0 stable release candidate
#12I never understand when OSS projects give themselves names that will never go mainstream. If the goal is semi-popularity at least, then "Devuan" will not work.
In this particular case I don't think it'll matter. All the big distros have (thankfully[1]) standardized on systemd. At least we now have something to point the systemd haters towards, I guess. [1] I doesn't even matter too much to me _which_ solution we have as long as it's reasonable (e.g. upstart wasn't) and a reasonably complete daemon supervision solution which can actually capture the output of the daemon's it…
> standardized on systemd
I sort of understand the reason for using systemd on desktop computers, where things may be rather volatile, but in a stable environment such as a server or a mainframe, the value that this complex piece of software brings to the table is not obvious to me; besides, others have mentioned that it is a sysadmin's nightmare, so...
Re: Devuan Jessie 1.0.0 stable release candidate
#13Re: Devuan Jessie 1.0.0 stable release candidate
#14"Devuan can be adopted as a flawless upgrade path from both Debian Wheezy and Jessie." That is nice, to have a supported path of simply add sources, signing keys and apt-get dist-upgrade. Impressive work. I'm personally not convinced there's a viable near future for Linux without systemd (not counting the mess that is android (as a potential workstation / server distro) - I think Debian/kFreeBSD is a better path. But…
> I think Debian/kFreeBSD is a better path.
Is there an assumption that once Debian decided to go with systemd and an increasing amount of Debian standard software depended on it, the kFreeBSD port will have to be given up at some point?
Re: Devuan Jessie 1.0.0 stable release candidate
#15I never understand when OSS projects give themselves names that will never go mainstream. If the goal is semi-popularity at least, then "Devuan" will not work.
how do you know if a name will go mainstream ?
Re: Devuan Jessie 1.0.0 stable release candidate
#16I never understand when OSS projects give themselves names that will never go mainstream. If the goal is semi-popularity at least, then "Devuan" will not work.
I've heard it referred to as Dev1, which doesn't sound as bad.
Re: Devuan Jessie 1.0.0 stable release candidate
#17I never understand when OSS projects give themselves names that will never go mainstream. If the goal is semi-popularity at least, then "Devuan" will not work.
To be fair, yahoo! and Google are pretty poor names too?
Why are they poor names? Both Yahoo! and Google are easy to pronounce and easy to remember.
Re: Devuan Jessie 1.0.0 stable release candidate
#18Earlier quoted context omitted.
In this particular case I don't think it'll matter. All the big distros have (thankfully[1]) standardized on systemd. At least we now have something to point the systemd haters towards, I guess. [1] I doesn't even matter too much to me _which_ solution we have as long as it's reasonable (e.g. upstart wasn't) and a reasonably complete daemon supervision solution which can actually capture the output of the daemon's it…
> standardized on systemd I sort of understand the reason for using systemd on desktop computers, where things may be rather volatile, but in a stable environment such as a server or a mainframe, the value that this complex piece of software brings to the table is not obvious to me; besides, others have mentioned that it is a sysadmin's nightmare, so...
>"others have mentioned that it is a sysadmin's nightmare"
Any examples? If anything I'd expect systemd to make things easier for sysadmins, would be interested in finding out what challenges sysadmins face because of systemd.
Re: Devuan Jessie 1.0.0 stable release candidate
#19I never understand when OSS projects give themselves names that will never go mainstream. If the goal is semi-popularity at least, then "Devuan" will not work.
I don't like it either. I think it's just that "vaun" is a rarely used sound in English. No real words end in vaun.
Re: Devuan Jessie 1.0.0 stable release candidate
#20Earlier quoted context omitted.
In this particular case I don't think it'll matter. All the big distros have (thankfully[1]) standardized on systemd. At least we now have something to point the systemd haters towards, I guess. [1] I doesn't even matter too much to me _which_ solution we have as long as it's reasonable (e.g. upstart wasn't) and a reasonably complete daemon supervision solution which can actually capture the output of the daemon's it…
> standardized on systemd I sort of understand the reason for using systemd on desktop computers, where things may be rather volatile, but in a stable environment such as a server or a mainframe, the value that this complex piece of software brings to the table is not obvious to me; besides, others have mentioned that it is a sysadmin's nightmare, so...
I'm not super interested in rehashing the flamewar, so this is anecdata: from the perspective of sysadmin of thousands of physical machines, systemd has been a godsend. It gives me a standard way to supervise, gather log output from, and restart long-running-processes with dependencies on other processes. It's replaced a number of "sleep 10"s and "sleep 60"s that our infrastructure has grown over the years in shell scripts at various points in init. Starting services in a consistent environment (not inheriting anything from the sysadmin's own session / environment) has also been useful in an environment with lots of sysadmins.
It's certainly not the best solution out there for any single thing it does, but the standardization - i.e., that it is integrated with my distro and also every other distro - is extremely useful. Most existing things I want to run tend to have systemd support, and most homegrown things are very easy to write systemd units for.
Also, there are a lot of reasons to want fast reboots for servers, and systemd provides this. (Again, so do other approaches, but the standardization means this actually happens.)
It's worth noting that there are sort of two debates: systemd vs. other similar systems (upstart, SMF, launchd, whatever) or systemd/similar systems vs. sysvinit. From experienced, large-scale UNIX admins, I think the wide consensus is that the answer to the second question is "definitely anything other than sysvinit". See, for instance, that the Debian tech committee debate was about systemd vs. upstart vs. insserv or something else, and nobody voted for sysvinit.