Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #206238
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: systemd error |
| Date | 2019-03-13 21:30 +0100 |
| Message-ID | <xBiFI-81W-15@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <xAnR8-5jy-3@gated-at.bofh.it> <xAsxs-8hu-5@gated-at.bofh.it> <xB49H-77y-3@gated-at.bofh.it> <xB49H-77y-1@gated-at.bofh.it> <xBdG1-4XR-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Dan Ritter wrote: > Default User wrote: >> On Tue, Mar 12, 2019, 04:49 Ivan Ivanov <qmastery16@gmail.com> wrote: >> >> > Well, I know a good solution that will work 100%: switch from Debian >> > to Devuan to avoid this SystemD. sadly Debian does not provide the >> > init system freedom, but if you'd switch to its' brother distribution >> > (Devuan) it still provides all the benefits of Debian + the freedom >> > from SystemD. >> > >> >> >> >> Thanks for the suggestion, Ivan. >> >> Actually, I had high hopes for Devuan. But I am afraid that it's just too >> little, too late. >> >> The cancer of systemd has metastasized too far and the GNU/Linux patent >> is terminally ill. >> >> How sad that once again, the bad guys won because good men did nothing. > > In point of fact: > > - I run several hundred Debian stretch systems without systemd > running as init, or doing very much otherwise. > > "apt install sysvinit-core" was all that is needed. > > - Those are almost all servers, but also includes some desktops. > > - The debian-init-diversity mail archives are here: > http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/2019-March/thread.html > and you can see that good work is being done on sysvinit, > startpar, insserv and elogind. > > I don't know why this doesn't get more publicity. > > If you are having problems with systemd and they feel intractable, > it's perfectly reasonable to go back to sysvinit, and it's only a little > work to move to openrc and a moderate amount to use completely different > init systems. > > -dsr- Who seeks, he finds and I have actually installed: ii sysv-rc 2.88dsf-59.9 all System-V-like runlevel change mechanism ii sysvinit-core 2.88dsf-59.9 amd64 System-V-like init utilities ii sysvinit-utils 2.88dsf-59.9 amd64 System-V-like utilities and it works great. My problem with systemd is not that it is bad, but that it was pushed too early to the public like KDE4 - many things not working or not working properly and this upsets one like me that is used to stability. I do not have the time or the will to deal with problems suddenly popping up out of nowhere. Looking at the background of systemd it makes sense especially for desktop/notebook system or interdependant services. In fact my Sailfish phone works great with systemd. So the debian-init-diversity decision was the best and my respect goes to the people behind it. It is great to have freedom of choice! However I do not find my way through the link. I prefer https://wiki.debian.org/Debate/initsystem/systemd and the parent https://wiki.debian.org/Debate/initsystem
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
systemd error Default User <hunguponcontent@gmail.com> - 2019-03-08 22:20 +0100
Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-09 08:50 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 03:50 +0100
Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 08:40 +0100
Re: systemd error Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2019-03-10 12:10 +0100
Re: systemd error Curt <curty@free.fr> - 2019-03-10 14:30 +0100
Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 16:30 +0100
Re: systemd error Curt <curty@free.fr> - 2019-03-10 17:50 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 17:50 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 20:50 +0100
Re: systemd error Reco <recoverym4n@enotuniq.net> - 2019-03-10 21:10 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-11 05:00 +0100
Re: systemd error Sven Hartge <sven@svenhartge.de> - 2019-03-11 08:50 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-11 13:50 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 06:00 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 06:10 +0100
Re: systemd error <tomas@tuxteam.de> - 2019-03-13 09:50 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 14:30 +0100
Re: systemd error Dan Ritter <dsr@randomstring.org> - 2019-03-13 16:10 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-13 19:20 +0100
Re: systemd error deloptes <deloptes@gmail.com> - 2019-03-13 21:30 +0100
Re: systemd error <tomas@tuxteam.de> - 2019-03-13 22:00 +0100
Re: systemd error Curt <curty@free.fr> - 2019-03-09 10:30 +0100
Re: systemd error Default User <hunguponcontent@gmail.com> - 2019-03-10 03:40 +0100
Re: systemd error Curt <curty@free.fr> - 2019-03-10 10:40 +0100
Re: systemd error Cindy-Sue Causey <butterflybytes@gmail.com> - 2019-03-10 15:10 +0100
csiph-web