From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 23122 invoked from network); 23 May 2022 10:07:12 -0000 Received: from alyss.skarnet.org (95.142.172.232) by inbox.vuxu.org with ESMTPUTF8; 23 May 2022 10:07:12 -0000 Received: (qmail 32601 invoked by uid 89); 23 May 2022 10:07:37 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 32594 invoked from network); 23 May 2022 10:07:37 -0000 X-Virus-Scanned: SPAM Filter at disroot.org Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1653300354; bh=i+o7pcwL3ZzkPuQn9oQoGpWYcJlCXviRQgp+RwdadvA=; h=Date:Subject:To:References:From:In-Reply-To; b=EVoNhG377mwPAb31WkF0xFbNSjn2LvTAJmix83HAIGSJuWR9EGyyrlCv36D5qsu6/ iTWy+jExxqpqhUi//W+dVuDiFjKtyFIK0QBEZK2NrkfLzut2MIMM6iB+JJBo+Qdrts 3V+b/QXirz1MWRX2N/gl1MhQFczDtLDIzAn4BncWfhHAsw0c3gJm682b/NglD/ZUfW cKVKKnwWbmFCN7OGXTPeHQnn2Jj9rpdAGVM9feNPNOZHNba0ZBt0gGdBWgmj9Z8NU3 9Z5vhiQTenAY6QP0DQktvXjVVwnTEt1f4dtpRMti5NHdY6zgstyKNJMesi2GovR3Rf +ph+kLNl3cZDw== Date: Mon, 23 May 2022 13:05:51 +0300 Mime-Version: 1.0 Subject: Re: s6 xinit replacement? Content-Language: en-US To: supervision@list.skarnet.org References: <3VJC4G8PXTKVS.3RQFDLXYQABMW@oak.localdomain> <727c2c8b-2b5e-24b4-f9e5-17e651217cc9@sholland.org> From: yianiris In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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@" 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@ 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".