Received: from mxout013.mail.hostpoint.ch (mxout013.mail.hostpoint.ch [IPv6:2a00:d70:0:e::313]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id DD9A62232BC for <~alpine/devel@lists.alpinelinux.org>; Thu, 27 Apr 2023 20:10:42 +0000 (UTC) Received: from [10.0.2.45] (helo=asmtp012.mail.hostpoint.ch) by mxout013.mail.hostpoint.ch with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.95 (FreeBSD)) (envelope-from ) id 1ps7wt-000Hqq-OK for ~alpine/devel@lists.alpinelinux.org; Thu, 27 Apr 2023 22:10:39 +0200 Received: from mail-qk1-f180.google.com ([209.85.222.180]) by asmtp012.mail.hostpoint.ch with esmtpa (Exim 4.95 (FreeBSD)) (envelope-from ) id 1ps7wt-0009XL-Jn for ~alpine/devel@lists.alpinelinux.org; Thu, 27 Apr 2023 22:10:39 +0200 Received: by mail-qk1-f180.google.com with SMTP id af79cd13be357-74de7182043so426275885a.3 for <~alpine/devel@lists.alpinelinux.org>; Thu, 27 Apr 2023 13:10:39 -0700 (PDT) X-Authenticated-Sender-Id: sven@kirmesss.myhostpoint.ch X-Gm-Message-State: AC+VfDyLjZNgLWywcFqUPkjEoe09AlmkksNLzkK7MpG0AnC5Oe23novD /aVcn1JjstFU9OSdD/+BL5MCRi6C3JcPRYyhS5E= X-Google-Smtp-Source: ACHHUZ5NLaRBIF/qm1hR+Sv91slJAC1X/jDNuyzUEPtgLEz6P/sgW5dIkKRIu7LtF0uDriZCNhHgseEjE8bumj4VnMQ= X-Received: by 2002:a05:6214:4115:b0:5e0:5935:d80e with SMTP id kc21-20020a056214411500b005e05935d80emr3961792qvb.45.1682626238341; Thu, 27 Apr 2023 13:10:38 -0700 (PDT) MIME-Version: 1.0 From: Sven Kirmess Date: Thu, 27 Apr 2023 22:10:27 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: UID for admin user created by setup-alpine To: ~alpine/devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="00000000000039ea8b05fa56f3b9" X-Vs-State: 0 --00000000000039ea8b05fa56f3b9 Content-Type: text/plain; charset="UTF-8" Is there a way to ensure the admin user created by setup-alpine has a specific uid, instead of the default (1000)? I think I found the script that setup-alpine uses to create a user, and that script doesn't have an option to ask for a UID: < https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blob/master/setup-user.in > Is that the correct script? And if yes, is there a reason why this option is not present or could that be added? --00000000000039ea8b05fa56f3b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Is there a way to ensure the admin user created by se= tup-alpine has a specific uid, instead of the default (1000)?
I think I found the script that setup-alpine uses to create a u= ser, and that script doesn't have an option to ask for a UID:
<https://gitlab.alpinelinux.org/alpine/alpine-conf/-/blo= b/master/setup-user.in>

Is that the correct= script? And if yes, is there a reason why this option is not present or co= uld that be added?
--00000000000039ea8b05fa56f3b9--