On Tue, 31 Aug 1999, Raphael Hertzog wrote:
> No problem, but you could try to do something realistic and logical.
I did. I read policy, asked base-passwd maintainer for static ids and got
no response at all. Then I asked here, in the hope to get things in order,
what we do right now, by this dis
Sorry to repeat the question,
but while my call for new static ids was shot down, nobody tried to answer
the question:
What should the package do, when it uses dynamic system ids (recognized by
name, not numeric value) and encounters a system, where the designed name
is already used by someone e
On Fri, 27 Aug 1999, Andreas Jellinghaus wrote:
> it is very easy in this case: don't use static id's. use dynamic.
I'm all for it, I'll patch what's needed and send it upstream etc.
> this is easy: use useradd or adduser to create an entry in /etc/passwd.
> these programs should return an error
Am I overlooking something? Please help me clarify this:
If I use static ids 0-99, they're set, both numbers and names. I can be
sure, that on every debian system they're assigned the same (or
unassigned, in case of older systems, and via dependencies I can force
base-passwd to be updated) - sta
4 matches
Mail list logo
