From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] group ids
Date: Fri, 26 Jul 2013 15:26:31 +0200 [thread overview]
Message-ID: <201307261526.31631.jbe@pengutronix.de> (raw)
In-Reply-To: <51F25D60.5060807@erwinrol.com>
Hi Erwin,
On Friday 26 July 2013 13:28:32 Erwin Rol wrote:
> how is the group id management in ptxdist suppose to work? The *.make
> files all seem to use numeric values.
Marc has changed this behaviour longer time ago to also support names instead
of numeric values only.
> Is there any mechanism to see which GID's (and UID's) are used for what?
> And how to decide which ID's to use for new users/groups?
AFAIR PTXdist uses the provided /etc/passwd and /etc/group to map the UID/GID
names from the rules files to numerical values (but I'm not sure).
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-07-26 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 11:28 Erwin Rol
2013-07-26 13:15 ` Robert Schwebel
2013-07-26 13:26 ` Jürgen Beisert [this message]
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=201307261526.31631.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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