mkusers: create system users/groups below UID/GID 1000
PATCH 1/1 mkusers: create system users/groups below UID/GID 1000
Try not to create users/groups past UID/GID 1000, as this space is usually reserved for proper user/group accounts.
Change buildroot behaviour to be similar to distros (like Debian) where UID/GID 101-999 are used for dynamic allocation to system service accounts.
--- support/scripts/mkusers | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
support/scripts/mkusers +4 -4
@@ -4,10 +4,10 @@ myname="${0##*/}" #---------------------------------------------------------------------------- # Configurable items -MIN_UID=1000 -MAX_UID=1999 -MIN_GID=1000 -MAX_GID=1999 +MIN_UID=101 +MAX_UID=999 +MIN_GID=101 +MAX_GID=999 # No more is configurable below this point #----------------------------------------------------------------------------
Signature · 1 line
2.7.4
PATCH 1/1 mkusers: create system users/groups below UID/GID 1000
Pascal, All,
On 2017-02-09 14:43 +0100, Pascal de Bruijn spake thusly:
Quoted 18 lines
Try not to create users/groups past UID/GID 1000, as this space is usually reserved for proper user/group accounts.
Change buildroot behaviour to be similar to distros (like Debian) where UID/GID 101-999 are used for dynamic allocation to system service accounts.
Signed-off-by Pascal de Bruijn <[email protected]>--- support/scripts/mkusers | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)support/scripts/mkusers +0
-0@@ -4,10 +4,10 @@ myname="${0##*/}"
support/scripts/mkusers myname="${0##*/}" · line 10
Quoted 10 lines
support/scripts/mkusers +4
-4#---------------------------------------------------------------------------- # Configurable items -MIN_UID=1000 -MAX_UID=1999 -MIN_GID=1000 -MAX_GID=1999 +MIN_UID=101 +MAX_UID=999 +MIN_GID=101 +MAX_GID=999
Although I don't have any hard conviction for a specific range or another, I don't like the rationale.
For one, why would we need to stick to similar numbering as standard distros to begin with? as far as I know, nothing mandates any UID:GID range for anything, except that 0:0 is for root:root.
Second, this script does not create only so-called "service accounts"; it is perfectly legit to use that script to create "normal" users.
If you need to guarantee a numbering for specific users, then you should pass your own user tables with the uids and gids you care about; Buildroot will happily use the UIDs/GIDs used therein, even outside the range here.
However...
I would love to see that range being configurable in the menuconfig, instead of having to edit the file to change the range.
I believe this would be much more user-friendly and would cover your use-case as well. I believe. ;-)
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 mkusers: create system users/groups below UID/GID 1000
Quoted 5 lines · Yann E. MORIN
I would love to see that range being configurable in the menuconfig, instead of having to edit the file to change the range.
I believe this would be much more user-friendly and would cover your use-case as well. I believe. ;-)
I agree, and I've marked the patch as Changes Requested in patchwork accordingly.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF