From: Andrew Davis <afd@ti.com>
To: Randolph Sapp <rs@ti.com>, Denys Dmytriyenko <denis@denix.org>,
Ryan Eatmon <reatmon@ti.com>
Cc: <meta-arago@lists.yoctoproject.org>
Subject: Re: [DISCUSSION] Weston-Init and non-root weston
Date: Mon, 17 Apr 2023 17:39:16 -0500 [thread overview]
Message-ID: <02df0607-5aad-f70d-62d2-ffdce916201b@ti.com> (raw)
In-Reply-To: <1241ddde-7f9c-d8ff-2c15-d300f5c5a24a@ti.com>
On 4/17/23 5:32 PM, Randolph Sapp wrote:
> Finally getting around to weston-init issue I highlighted a while back and there's only one real issue preventing us from reusing the base weston-init recipe -- our touchscreen auto-configuration script.
>
> That script has to have root access to setup and reload udev rules and as we know setuid won't work for shell scripts.
>
> I propose we rewrite it in something that can use setuid (perl or c or something of the sort). I'm currently looking at perl as there's already quite a few core recipes that rdepend on it.
>
> Then we just need to inject it into the runWeston script and adjust the two init scripts to point at that.
>
> Any concerns or objections?
Why not just drop out that old touchscreen script, it is a non-standard way of doing
this task and should be removed.
Andrew
next prev parent reply other threads:[~2023-04-17 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 22:32 [DISCUSSION] Weston-Init and non-root weston Randolph Sapp
2023-04-17 22:39 ` Andrew Davis [this message]
2023-04-17 22:43 ` Randolph Sapp
2023-04-17 22:52 ` Andrew Davis
2023-04-17 23:01 ` Randolph Sapp
2023-04-17 23:08 ` Andrew Davis
2023-04-17 23:16 ` Randolph Sapp
2023-04-18 22:51 ` Denys Dmytriyenko
2023-04-19 2:30 ` [EXTERNAL] " 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=02df0607-5aad-f70d-62d2-ffdce916201b@ti.com \
--to=afd@ti.com \
--cc=denis@denix.org \
--cc=meta-arago@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=rs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.