From: Steve Litt <firstname.lastname@example.org>
Subject: Re: s6 xinit replacement?
Date: Thu, 26 May 2022 22:04:06 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
yianiris said on Mon, 23 May 2022 13:05:51 +0300
>Unbelievable, on this particular list, someone suggesting that dbus or
>systemd (elogind is the most invasive of all parts of systemd) is
>needed to run X, or wayland for that matter.
>If you have compiled X to require those, then it is your fault, and yes
>such trashy messaging should be recorded somewhere, maybe by journald.
>I apologize for the harshness of my reaction,
Compiling X isn't like compiling fetchmail: It's a real slog.
Compiling the right X version to fit with your existing stuff takes
some trial and error. Having to recognize every time your distro
updates X and recompile is a time sink, even if you have a shellscript
do the whole thing.
>Again, sorry Guillermo, this is not personal, it is "political".
Suggestion: Next time lead off with the preceding sentence. I think
we all have a pretty good idea of motivations surrounding systemd, and
those motivations are every bit as ugly as those of proprietary
software. If it had been framed as "this sucks, but you need to compile
X yourself to get out of this mess", I think it would have been more
And I'd like to congratulate you for running a dbus-less system. I know
it's not easy --- I only succeeded in doing it once
). If you're the type of person who likes giving presentations, it
would be wonderful if you could present at one of our monthly GoLUG
online Jitsi meetings.
March 2022 featured book: Making Mental Models: Advanced Edition
next prev parent reply other threads:[~2022-05-27 2:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 3:36 dallinjdahl
2022-05-14 3:47 ` Guillermo
2022-05-14 23:45 ` dallinjdahl
2022-05-15 1:52 ` Laurent Bercot
2022-05-15 15:02 ` Guillermo
2022-05-17 4:10 ` Rio Liu
2022-05-15 2:44 ` Samuel Holland
2022-05-22 15:07 ` Guillermo
2022-05-22 16:33 ` Samuel Holland
2022-05-23 10:05 ` yianiris
2022-05-23 23:40 ` Guillermo
2022-05-27 2:04 ` Steve Litt [this message]
2022-05-28 4:07 ` Dallin Dahl
2022-05-28 17:15 ` Dallin Dahl
2022-05-28 19:43 ` Samuel Holland
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).