From: "Yann E. MORIN" <yann.morin.1998@free.fr>
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: Sat, 28 May 2022 23:46:13 +0200 [thread overview]
Message-ID: <20220528214613.GN301044@scaer> (raw)
In-Reply-To: <20220205222331.3432353-1-arnout@mind.be>
Arnout, All,
Title: s/manuali/manual/
On 2022-02-05 23:23 +0100, Arnout Vandecappelle (Essensium/Mind) spake thusly:
> 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>
> ---
> docs/manual/makeusers-syntax.txt | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/docs/manual/makeusers-syntax.txt b/docs/manual/makeusers-syntax.txt
> index 3d1013f447..cebc6240ae 100644
> --- a/docs/manual/makeusers-syntax.txt
> +++ b/docs/manual/makeusers-syntax.txt
> @@ -90,3 +90,17 @@ This will create this user:
> - +shell+ is: +/bin/sh+
> - +test+ is not a member of any additional +groups+
> - +comment+ is: +Test user+
> +
> +
> +=== Caveat when updating Buildroot
I changed that to: Caveat with automatic UIDs and GIDs
(because that's the real cause).
> +
> +When updating buildroot or when packages are added or removed to/from
> +the configuration, it is possible that the automatic UIDs and GIDs are
> +changed. This can be a problem if persistent files were created with
> +that user or group: after upgrade, they will suddenly have a different
> +owner.
> +
> +Therefore, it is advisable to perpetuate the automatic IDs. This can be
> +done either by adding a users table with the generated IDs. It is only
'either' is spurious here, I think, so I dropped it.
Applied to master, thanks.
Regards,
Yann E. MORIN.
> +needed to do this for UIDs that actually create persistent files, e.g.
> +database.
> --
> 2.34.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| 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
next prev parent reply other threads:[~2022-05-28 21:46 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 [this message]
2022-06-06 10:27 ` Peter Korsgaard
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=20220528214613.GN301044@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox