All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] docs/manuali/makeusers-syntax.txt: add caveat for upgrading
Date: Mon, 06 Jun 2022 12:27:28 +0200	[thread overview]
Message-ID: <87pmjmxf1r.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220205222331.3432353-1-arnout@mind.be> (Arnout Vandecappelle's message of "Sat, 5 Feb 2022 23:23:31 +0100")

>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:

 > With the change of the range of UIDs that is generated from the
 > automatic ID (-1), it became apparent that there is a potential problem
 > with these automatic IDs when upgrading: they may have changed, which
 > means that persistent files that exist outside of the rootfs suddenly
 > have a different owner.

 > Add a caveat section to the manual, as well as an explanation of how to
 > work around the problem.

 > Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

Committed to 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-06-06 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 22:23 [Buildroot] [PATCH] docs/manuali/makeusers-syntax.txt: add caveat for upgrading Arnout Vandecappelle (Essensium/Mind)
2022-05-28 21:46 ` Yann E. MORIN
2022-06-06 10:27 ` Peter Korsgaard [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=87pmjmxf1r.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.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 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.