From: Tim Orling <ticotimo@gmail.com>
To: ticotimo@gmail.com
Cc: ruom9900@gmail.com, poky@lists.yoctoproject.org
Subject: Re: [poky] Changing permission for udev file devices in poky
Date: Fri, 3 May 2024 15:05:14 -0700 [thread overview]
Message-ID: <CANx9H-BgMauQu6pOPpfgE3VhFoQ0yrznOe982dWBpFiKmmi2Og@mail.gmail.com> (raw)
In-Reply-To: <17CC16D04DD31A27.11769@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]
On Fri, May 3, 2024 at 2:10 PM Tim Orling via lists.yoctoproject.org
<ticotimo=gmail.com@lists.yoctoproject.org> wrote:
>
>
> On Fri, May 3, 2024 at 2:09 PM Tim Orling via lists.yoctoproject.org
> <ticotimo=gmail.com@lists.yoctoproject.org> wrote:
>
>>
>>
>> On Fri, May 3, 2024 at 1:51 PM ruom9900 via lists.yoctoproject.org
>> <ruom9900=gmail.com@lists.yoctoproject.org> wrote:
>>
>>> Hello,
>>> I'm trying to change the file ownership rules for i2c devices by
>>> specifying the group to be a custom group. Im creating the custom group in
>>> my local.conf file with EXTRA_USER_PARAMS , is there a way to modify the
>>> file permissions from the local.conf file instead of the devfs-udev.rules
>>> file ?
>>
>>
>> You probably want to do a bbappend and modify the do_install with chmod
>> command.
>>
> or chown might be more appropriate for your custom group use case.
>
On further thought, I think you should add your custom group/user to the
existing udev group. Do not reinvent the wheel.
Perhaps you could share some more details about what you are trying to
achieve and why you are asking these questions. It is possible you are
going down the less-optimal path and we might be able to help you more with
more information.
>
>>
>>>
>>>
>>>
>>
>>
>>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#13345):
> https://lists.yoctoproject.org/g/poky/message/13345
> Mute This Topic: https://lists.yoctoproject.org/mt/105896480/924729
> Group Owner: poky+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [
> ticotimo@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 3826 bytes --]
prev parent reply other threads:[~2024-05-03 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 20:51 Changing permission for udev file devices in poky ruom9900
2024-05-03 21:09 ` [poky] " Tim Orling
[not found] ` <17CC16C45BFE63A1.24380@lists.yoctoproject.org>
2024-05-03 21:10 ` Tim Orling
[not found] ` <17CC16D04DD31A27.11769@lists.yoctoproject.org>
2024-05-03 22:05 ` Tim Orling [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=CANx9H-BgMauQu6pOPpfgE3VhFoQ0yrznOe982dWBpFiKmmi2Og@mail.gmail.com \
--to=ticotimo@gmail.com \
--cc=poky@lists.yoctoproject.org \
--cc=ruom9900@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).