diff mbox series

docs/manuali/makeusers-syntax.txt: add caveat for upgrading

Message ID 20220205222331.3432353-1-arnout@mind.be
State Accepted
Headers show
Series docs/manuali/makeusers-syntax.txt: add caveat for upgrading | expand

Commit Message

Arnout Vandecappelle Feb. 5, 2022, 10:23 p.m. UTC
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(+)

Comments

Yann E. MORIN May 28, 2022, 9:46 p.m. UTC | #1
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
Peter Korsgaard June 6, 2022, 10:27 a.m. UTC | #2
>>>>> "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.
diff mbox series

Patch

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
+
+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
+needed to do this for UIDs that actually create persistent files, e.g.
+database.