supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: yianiris <yianiris@disroot.org>
To: supervision@list.skarnet.org
Subject: Re: s6 xinit replacement?
Date: Mon, 23 May 2022 13:05:51 +0300	[thread overview]
Message-ID: <cc0d7f3f-348e-4478-7380-d832b1402abf@disroot.org> (raw)
In-Reply-To: <CADQ2Nw-qDv1neoYSpREEVvZVQXC7OquVfhqL1OQ=9u0LUthg4g@mail.gmail.com>

reply Guillermo:
> Hello, Samuel.
> 
> I had a look at your s6-rc service definitions, and it seems that you
> don't have one for the system-wide message bus (D-Bus) and elogind.
> That, in addition to having the tmpfs whose path is stored in
> XDG_RUNTIME_DIR mounted by a "user-setup@<your user>" system service,
> makes me think that you are not running those.

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.

> On the other hand, IIUC
> the Xorg process is part of a supervision tree that runs with your
> (unprivileged) user and is launched by service "user-services@<your
> user>", and I suppose that Xorg is not a suid binary, so unless you do
> something else, your Xorg*.log file should contain something like:

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, but for years I've run
(and thousands of others) without a trace of logind or dbus.  My system
is loosely based on Arch-testing (bleeding edge from 20000 upstream
sources) and I have done the same in void as well.  This implication
that to run X,Y,Z logind/dbus is needed is dangerous and confusing as
IBM propaganda, and we NEED to extinguish propaganda because we are
where we are due to power of misinformation by the evil BlueChip.

Just because it is easy and convenient for some distro developers to
adopt the blackmail methods of IBM, this doesn't mean it is necessary.
Having no direct evidence I could speculate that those the lead the
decisions to adopt them have financial interests, but I can not
speculate that far.  You can, I can't.

xorg 21.1.3
xorg-xinit 1.4.1
xorg-xwayland 22.1.1-1
wayland 1.20.0
s6 2.11.1.0
66 0.6.2.0

no logind no dbus 0 logind/dbus warning/error messages.

Again, sorry Guillermo, this is not personal, it is "political".


  parent reply	other threads:[~2022-05-23 10:07 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 [this message]
2022-05-23 23:40         ` Guillermo
2022-05-27  2:04         ` Steve Litt
2022-05-28  4:07     ` Dallin Dahl
2022-05-28 17:15     ` Dallin Dahl
2022-05-28 19:43       ` Samuel Holland

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=cc0d7f3f-348e-4478-7380-d832b1402abf@disroot.org \
    --to=yianiris@disroot.org \
    --cc=supervision@list.skarnet.org \
    /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;
as well as URLs for NNTP newsgroup(s).