From: ChenQi <Qi.Chen@windriver.com>
To: Arno Steffens <star@gmx.li>,
"pokyyoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Give others users than "root" access to GPIO (or commands)
Date: Wed, 30 May 2018 14:03:06 +0800 [thread overview]
Message-ID: <54cf3e3f-42e8-bbb9-ff6a-6ab76ff4e497@windriver.com> (raw)
In-Reply-To: <trinity-f65d3236-5771-46ac-b0bf-c6d5bbacdd40-1527590486561@3c-app-gmx-bs25>
On 05/29/2018 06:41 PM, Arno Steffens wrote:
> I have to add a user other than root to start a program which operates with i2c, spi, gpio.
> For this I added an init-script /etc/rc5.d to make it /dev/* r/w for "others".
> That works for i2c and spi but not for GPIO. As most of the files the user has to access will only created after the exporting the GPIOs (more or less doing echo xxx > /sys/class/gpio/export).
> But this new created /sys/class/gpio/xxx is not writable by user.
>
> Maybe I am doing it completely wrong, but how can I achieve this to become possible?
> I checked the mega-manual, but there is not much mentioned about groups (27.36. extrausers.bbclass).
> Best regards
> Arno
>
> Maybe I also have to give this user the permission to reboot, which is right now only possible for root
Not sure about your environment. But if you want normal user to do some
operation requiring root privilege, consider using a SETUID program.
1) Create a progrem to do the actual work that require root privilege.
2) If your only want your program to be run by some specific user, do
the user checking in the program.
3) Install your program to be SETUID. `chmod +s xxx'
You can check dbus-daemon-launch-helper in dbus for a reference.
Best Regards,
Chen Qi
next prev parent reply other threads:[~2018-05-30 6:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 10:41 Give others users than "root" access to GPIO (or commands) Arno Steffens
2018-05-30 6:03 ` ChenQi [this message]
2018-05-30 10:01 ` Arno Steffens
2018-05-30 10:18 ` Richard Purdie
2018-06-01 11:18 ` Arno Steffens
2018-05-30 10:36 ` star
2018-05-30 7:21 ` Richard Purdie
2018-05-30 10:20 ` Arno Steffens
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=54cf3e3f-42e8-bbb9-ff6a-6ab76ff4e497@windriver.com \
--to=qi.chen@windriver.com \
--cc=poky@yoctoproject.org \
--cc=star@gmx.li \
/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.