On Sat, Feb 07, 2009 at 04:26:06PM +0100, Raoul Bhatia [IPAX] wrote:
> it is better to use "adduser --system ... libuid ..." instead of the
> complicated parsing of $ADDUSERCONF because adduser has the --system
> option so parsing /etc/adduser.conf is not necessary.

This is why we can't use adduser: 

commit 46e770b2e23c18d27c351207601c0222484d6681
Author: Theodore Ts'o <ty...@mit.edu>
Date:   Mon Dec 31 22:22:46 2007 -0500

    debian: Use useradd and groupadd in favor of adduser
    
    The adduser package is 'important', and while it is often installed,
    we can't guarantee that it will always be there.  A required package,
    or a package which is dragged in by a required package, such as
    libuuid1, shouldn't depend on an 'important' package since that would
    implicitly make it be required, which shouldn't be done unless
    absolutely necesary.
    
    So we replace the call to adduser with the lower-level useradd and
    groupadd programs.  They are part of the passwd package, which is
    required to be on all Debian systems.
    
    Signed-off-by: "Theodore Ts'o" <ty...@mit.edu>

> as far as i have observed, there seems to be one difference thou:
> adduser seems to increment the uid step-by-step increment to find the
> next free one (thus filling gaps/holes) while useradd seems to search
> for the highest uid and increment this one.

I have trouble considering this a major problem.... or even a minor
problem, for that matter.

I'll accept a patch which checks for the presence for adduser, and
uses if it is present, and falls back to useradd if adduser is not
present, but I don't care enough to try to implement and test it.
Patches, however, will be gratefully accepted.  :-) Please make sure
you test it on systems that don't have adduser to make sure the right
thing happens in both cases.

                                                - Ted




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to