Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "José Pekkarinen" <jose.pekkarinen@unikie.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] system: add optional rsync with preserved permissions
Date: Mon, 4 Oct 2021 17:15:12 +0200	[thread overview]
Message-ID: <20211004151512.GD1504958@scaer> (raw)
In-Reply-To: <CAJPV9MpbeTF4vGvOtP15bNGGLbt8StceDxYWs8LLebgyEr=gvg@mail.gmail.com>

José, All,

On 2021-10-04 10:08 +0300, José Pekkarinen spake thusly:
> On Mon, Oct 4, 2021 at 10:00 AM Thomas Petazzoni < [1]thomas.petazzoni@bootlin.com> wrote:
>   On Mon,  4 Oct 2021 09:41:43 +0300
>   José Pekkarinen < [2]jose.pekkarinen@unikie.com> wrote:
> 
>   > +config BR2_ROOTFS_OVERLAY_PRESERVED_PERMISSION
>   > +     string "Preserve permissions of overlay directories"
>   > +     depends on BR2_ROOTFS_OVERLAY
>   > +     default "n"
>   > +     help
>   > +       Preserve file permissions of specified overlay.
>   José: have you considered using a permission table to fixup the
>   permissions ?
> 
> Never heard of it,

It's irght there in the manual:

    9.5.1. Setting file permissions and ownership and adding custom devices nodes
    https://buildroot.org/downloads/manual/manual.html#rootfs-custom

    Chapter 25. Makedev syntax documentation
    https://buildroot.org/downloads/manual/manual.html#makedev-syntax

;-)

> but after a quick check it looks like
> it is a better answer to my problem, since I found that, for
> example, if I want to provide, an authorized_keys file owned
> by root, with 600 permissions, rsync copies the file with 644,
> which is closer, but not perfect.

Given your feedback, and Thomas' and my comments, I've then marked your
patch as rejected in Patchwork.

Thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2021-10-04 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04  6:41 [Buildroot] [PATCH] system: add optional rsync with preserved permissions José Pekkarinen
2021-10-04  7:00 ` Thomas Petazzoni
2021-10-04  7:08   ` José Pekkarinen
2021-10-04  7:30     ` Thomas Petazzoni
2021-10-04 15:15     ` Yann E. MORIN [this message]
2021-10-04 15:10   ` Yann E. MORIN

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=20211004151512.GD1504958@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=jose.pekkarinen@unikie.com \
    --cc=thomas.petazzoni@bootlin.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