Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #206207

Re: systemd error

From Default User <hunguponcontent@gmail.com>
Newsgroups linux.debian.user
Subject Re: systemd error
Date 2019-03-13 06:00 +0100
Message-ID <xB49H-77y-1@gated-at.bofh.it> (permalink)
References (10 earlier) <xAcVH-6XF-1@gated-at.bofh.it> <xAkgx-30a-1@gated-at.bofh.it> <xAnR8-5jy-3@gated-at.bofh.it> <xAsxs-8hu-5@gated-at.bofh.it> <xB49H-77y-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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