Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Randolph Sapp <rs@ti.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>, <rs@ti.com>,
	<mathieu.dubois-briand@bootlin.com>, <alex@linutronix.de>,
	<otavio@ossystems.com.br>, <kexin.hao@windriver.com>
Cc: <afd@ti.com>, <detheridge@ti.com>, <denis@denix.org>,
	<reatmon@ti.com>, <openembedded-core@lists.openembedded.org>,
	<vijayp@ti.com>
Subject: Re: [oe-core][PATCHv10 7/7] xuser-account: merge with xserver-nodm-init
Date: Tue, 23 Sep 2025 18:38:17 -0500	[thread overview]
Message-ID: <DD0KQD1AFT03.1FP6NSP775W2P@ti.com> (raw)
In-Reply-To: <2868d1ad803cb9d135c09104470c0614a7cd2f17.camel@linuxfoundation.org>

On Tue Sep 23, 2025 at 5:57 PM CDT, Richard Purdie wrote:
> On Tue, 2025-09-23 at 17:51 -0500, rs@ti.com wrote:
>> From: Randolph Sapp <rs@ti.com>
>> 
>> Merge the xuser-account recipe with xserver-nodm-init, since:
>> 
>>  - This is the only recipe dependent on it
>
> This is not a good reason to merge them. The reason they were kept
> separate was so that people could replace the user with their own user
> setup whilst reusing the xserver init code (or vice versa).

Sure, but now this is all encompassed by the virtual-emptty-conf providers, as
the conf dictates what user is to be automatically logged in. This conf needs to
be kept in sync with whatever user is submitted.

If people want to forgo managing the conf and just manage their own users then
they can just set the preferred rprovider for virtual-emptty-conf to emptty-conf
and add their own users in their own recipes. This will give them the desktop
like experience where they are greeted with a console login prompt and session
picker on tty7.

I guess this also means that the x-session-manager recipes should be updated to
provide their desktop files for their sessions instead of us doing that in
xserver-nodm-init though. I may need to address that in another revision.

>>  - This matches the current behavior in weston-init
>>  - Running x11 as root is no longer a supported path in
>>    xserver-nodm-init
>
> Does rootless X work everywhere now? 
>
> Cheers,
>
> Richard

Uh, that's a good question. I didn't think there were any particular usecases
left that were limited by rootless X. It's been a desktop thing for so long now
the only issues I remember were specifically around the way the handoff to the
user account occurred.

Gentoo cites the difference between using a login manager / display manager vs
the old suid scheme as being problematic for remote start depending on how seat
management is handled. We didn't seem to be relying on that behavior so I want
to say it's fine.

- Randolph


  reply	other threads:[~2025-09-23 23:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 22:51 [oe-core][PATCHv10 0/7] Display manager proposal for x11 and wayland rs
2025-09-23 22:51 ` [oe-core][PATCHv10 1/7] libx11: create tmpfile dir for x11 domain socket rs
2025-09-23 22:51 ` [oe-core][PATCHv10 2/7] go: fix sigaction usage on i386 platforms rs
2025-09-23 22:51 ` [oe-core][PATCHv10 3/7] emptty: add version 0.14.0 rs
2025-09-23 22:51 ` [oe-core][PATCHv10 4/7] weston-init: convert to virtual-emptty-conf rs
2025-09-23 23:03   ` Patchtest results for " patchtest
2025-09-23 22:51 ` [oe-core][PATCHv10 5/7] weston: remove deprecated weston-start scripts rs
2025-09-23 22:51 ` [oe-core][PATCHv10 6/7] xserver-nodm-init: convert to virtual-emptty-conf rs
2025-09-23 22:51 ` [oe-core][PATCHv10 7/7] xuser-account: merge with xserver-nodm-init rs
2025-09-23 22:57   ` Richard Purdie
2025-09-23 23:38     ` Randolph Sapp [this message]
     [not found]     ` <18680DB08C963B21.19236@lists.openembedded.org>
2025-09-25 22:29       ` Randolph Sapp
2025-09-23 23:03   ` Patchtest results for " patchtest
     [not found] ` <18680B2C26D3ACFF.17085@lists.openembedded.org>
2025-09-24  0:13   ` [oe-core][PATCHv10 6/7] xserver-nodm-init: convert to virtual-emptty-conf Randolph Sapp
     [not found]   ` <18680FA2E4B5FED3.1251@lists.openembedded.org>
2025-09-24 22:47     ` Randolph Sapp

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=DD0KQD1AFT03.1FP6NSP775W2P@ti.com \
    --to=rs@ti.com \
    --cc=afd@ti.com \
    --cc=alex@linutronix.de \
    --cc=denis@denix.org \
    --cc=detheridge@ti.com \
    --cc=kexin.hao@windriver.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=reatmon@ti.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=vijayp@ti.com \
    /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