From: "NoTo CTTE" <usspookslovesystmd@muchomail.com>
To: <yaro@marupa.net>
Cc: <scott.ferguson.debian.user@gmail.com>,
<debian-devel@lists.debian.org>, <debian-ctte@lists.debian.org>,
<debian-vote@lists.debian.org>, <debian-project@lists.debian.org>,
<linux-kernel@vger.kernel.org>, <pascal@plouf.fr.eu.org>,
<yaro@marupa.net>, <cbannister@slingshot.co.nz>,
<andreimpopescu@gmail.com>, <ghaverla@materialisations.com>,
<debian-mirrors@lists.debian.org>,
<debian-security@lists.debian.org>,
<debian-user@lists.debian.org>, <debian-ctte@lists.debian.org>
Subject: Re: Four people decided the fate of debian with systemd. Bad faith likely - SysV is fine
Date: Sun, 2 Mar 2014 14:23:52 -0800 [thread overview]
Message-ID: <20140302142352.52A6A3E3@m0005309.ppops.net> (raw)
You say nothing because there is nothing that you can say.
Simplicity is beautiful, and it works.
Systemd is a nightmare, but you are using politics and psyops to push it on
every single linux user, every distro, everywhere.
I showed you code that does your vaunted concurrent boot systemddeeeee in a few
lines of shell.
That simplicity was the way unix and linux was, before the windows programmers
and the govt funded companies sunk their teeth into linux.
You know what & does.
I guess not, you're too new to gnu.
--- yaro@marupa.net wrote:
From: yaro@marupa.net
To: usspookslovesystmd@muchomail.com
Subject: Re: Four people decided the fate of debian with systemd. Bad faith likely - SysV is fine
Date: Sun, 02 Mar 2014 16:15:41 -0600
On Sunday, March 02, 2014 02:12:48 PM NoTo CTTE wrote:
> System V is NOT hard to "maintain"
> The scripts were written YEARS ago. They're fine. They do NOT need to be
> changed. Debian SysV has concurrent boot aswell.
>
> Systemd is a poison apple. 200k lines of unaudited root privlege code. A
> consulting service to go along with this new _operating system_
>
> Here's an under 100 line init with concurrent boot:
>
> #include <signal.h>
> #include <unistd.h>
>
> int main()
> {
> sigset_t set;
> int status;
>
> if (getpid() != 1) return 1;
>
> sigfillset(&set);
> sigprocmask(SIG_BLOCK, &set, 0);
>
> if (fork()) for (;;) wait(&status);
>
> sigprocmask(SIG_UNBLOCK, &set, 0);
>
> setsid();
> setpgid(0, 0);
> return execve("/etc/rc", (char *[]){ "rc", 0 }, (char *[]){ 0 });
> }
>
> >/etc/rc is a shell script
> >syslogd && getty ; udev ; network-config ; sshd & cron & nginx
>
> see how much bullsht systemd is.
>
>
> _____________________________________________________________
> The Free Email with so much more!
> =====> http://www.MuchoMail.com <=====
It'd be almost too easy to mock a laughable post like this, but I'll let
someone else do it. It's just not fun anymore.
Conrad
_____________________________________________________________
The Free Email with so much more!
=====> http://www.MuchoMail.com <=====
next reply other threads:[~2014-03-02 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-02 22:23 NoTo CTTE [this message]
2014-03-02 22:39 ` yaro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140302142352.52A6A3E3@m0005309.ppops.net \
--to=usspookslovesystmd@muchomail.com \
--cc=andreimpopescu@gmail.com \
--cc=cbannister@slingshot.co.nz \
--cc=debian-ctte@lists.debian.org \
--cc=debian-devel@lists.debian.org \
--cc=debian-mirrors@lists.debian.org \
--cc=debian-project@lists.debian.org \
--cc=debian-security@lists.debian.org \
--cc=debian-user@lists.debian.org \
--cc=debian-vote@lists.debian.org \
--cc=ghaverla@materialisations.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pascal@plouf.fr.eu.org \
--cc=scott.ferguson.debian.user@gmail.com \
--cc=yaro@marupa.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®