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

On Mon, 4 Oct 2021 10:08:09 +0300
José Pekkarinen <jose.pekkarinen@unikie.com> wrote:

> Never heard of it, 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.

Yes, with a permission table, you can adjust not just the permissions,
but also the ownership of files.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-10-04  7:30 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 [this message]
2021-10-04 15:15     ` Yann E. MORIN
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=20211004093020.191b907d@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=jose.pekkarinen@unikie.com \
    --cc=yann.morin.1998@free.fr \
    /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