From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Antonin Godard <antonin.godard@bootlin.com>, docs@lists.yoctoproject.org
Cc: michael.opdenacker@rootcommit.com
Subject: Re: [docs] [PATCH 3/3] dev-manual/bmaptool.rst: simplify and fix instructions
Date: Wed, 04 Dec 2024 09:33:36 +0000 (UTC) [thread overview]
Message-ID: <1bf657ac-1392-4ac0-b279-9689a8de8d09@rootcommit.com> (raw)
In-Reply-To: <7fa75108-fb1b-4d62-babc-054888a076d3@rootcommit.com>
On 12/4/24 10:26, Michael Opdenacker wrote:
> Hi AntoninI know this was already instructed before, but maybe `chmod
> o+w` is a better
>> practice and advice to give. What do you think?
>
>
> I wondered too. Let's do it, I agree.
Actually "chmod a+w". On my Ubuntu system, "o+w" would have worked, but
there may be other systems on which the user either owns the device file
or belongs to its group.
Michael.
--
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com/
next prev parent reply other threads:[~2024-12-04 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 17:38 [PATCH 1/3] dev-manual: fix styling of references to bmaptool michael.opdenacker
2024-12-01 17:38 ` [PATCH 2/3] dev-manual/bmaptool.rst: add missing command for bmaptool-native michael.opdenacker
2024-12-02 9:02 ` [docs] " Antonin Godard
2024-12-04 10:31 ` Michael Opdenacker
2024-12-01 17:38 ` [PATCH 3/3] dev-manual/bmaptool.rst: simplify and fix instructions michael.opdenacker
2024-12-01 19:26 ` [docs] " Ulrich Ölmann
2024-12-04 9:19 ` Michael Opdenacker
2024-12-02 9:02 ` Antonin Godard
2024-12-04 9:26 ` Michael Opdenacker
2024-12-04 9:33 ` Michael Opdenacker [this message]
2024-12-04 10:17 ` Antonin Godard
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=1bf657ac-1392-4ac0-b279-9689a8de8d09@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.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