docs/manual/makeusers-syntax.txt: add caveat for upgrading
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>
[yann.morin.1998@free.fr: slight rewording]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
(cherry picked from commit 8b51205638
)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
parent
84668397c1
commit
aa0dc66931
@ -90,3 +90,16 @@ This will create this user:
|
||||
- +shell+ is: +/bin/sh+
|
||||
- +test+ is not a member of any additional +groups+
|
||||
- +comment+ is: +Test user+
|
||||
|
||||
|
||||
=== Caveat with automatic UIDs and GIDs
|
||||
|
||||
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 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.
|
||||
|
Loading…
Reference in New Issue
Block a user