public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Randolph Sapp <rs@ti.com>
To: Ross Burton <Ross.Burton@arm.com>, "rs@ti.com" <rs@ti.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"mathieu.dubois-briand@bootlin.com"
	<mathieu.dubois-briand@bootlin.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-core][PATCH] libx11: create tmpfile dir for x11 domain socket
Date: Mon, 6 Oct 2025 12:21:23 -0500	[thread overview]
Message-ID: <DDBEUV3YD4MO.2KQ3UC10EUWFZ@ti.com> (raw)
In-Reply-To: <CE558C16-AD4F-401B-9734-E57067101F56@arm.com>

On Mon Oct 6, 2025 at 5:38 AM CDT, Ross Burton wrote:
> On 2 Oct 2025, at 01:30, rs@ti.com wrote:
>> 
>> From: Randolph Sapp <rs@ti.com>
>> 
>> Register a volatile directory entry for the x11 domain socket when not
>> using systemd. This will make sure the directory is always created with
>> the correct permissions. Systemd already provides their own tmpfile.d
>> entry for the same behavior.
>> 
>> Currently some x11 related applications will create this directory if it
>> doesn't already exist, but this is not true for everything. In addition,
>> if the application in question isn't started as root, it's possible this
>> directory can be owned by a non-root user. This isn't an issue by
>> itself, but it can potentially lead to problems in a multi-user
>> environment.
>
> Feel like this should be in xserver (as the xserver is the one creating the sockets), not libx11.
>
> Ross

Fair enough. That got me thinking though, with potentially multiple xserver
providers, and systemd already shipping it's own version of that tmpfiles entry,
should this instead be part of sysvinit? If anything, just to be symmetric?

- Randolph


      reply	other threads:[~2025-10-06 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  0:30 [oe-core][PATCH] libx11: create tmpfile dir for x11 domain socket rs
2025-10-06 10:38 ` Ross Burton
2025-10-06 17:21   ` Randolph Sapp [this message]

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=DDBEUV3YD4MO.2KQ3UC10EUWFZ@ti.com \
    --to=rs@ti.com \
    --cc=Ross.Burton@arm.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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