All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: adduser question
Date: Sun, 30 Nov 2008 10:27:22 +0100	[thread overview]
Message-ID: <ggtm9q$o83$1@ger.gmane.org> (raw)
In-Reply-To: <ggs1ip$38h$1@ger.gmane.org>

On 29-11-08 19:27, Koen Kooi wrote:
> On 29-11-08 19:08, Phil Blundell wrote:
>> On Sat, 2008-11-29 at 18:08 +0100, Koen Kooi wrote:
>>> adduser --system adds UIDs<100 to /etc/passwd, which 'update-passwd'
>>> will blow away, since they aren't in
>>> /usr/share/base-passwd/passwd.master
>>>
>>> Is this intended behaviour, and if not, how should it get fixed?
>>
>> Whether or not to use passwd.master and update-passwd is clearly a
>> distribution choice. Any distro which does want to use a
>> centrally-administered master password file should, presumably, also
>> configure adduser with an appropriate system UID range (for example,
>> 100-999). Depending on what implementation of adduser you are using,
>> this might just be a case of adjusting adduser.conf or it might involve
>> a recompile.
>>
>> For distros which don't desire to use passwd.master, the right solution
>> is simply to refrain from installing or running update-passwd. In this
>> case it doesn't matter what UID range adduser is set up for.
>
> Thanks for the explanation, I'll have a stab at adding a proper adduser
> since we only have the busybox one in OE. The busybox adduser doesn't
> seem to support adduser.conf nor UID ranges.

That's a no-go, the 'adduser' package is written in perl. Next stop: 
evaluate useradd from the 'passwd' package.

regards,

Koen




      reply	other threads:[~2008-11-30  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 17:08 adduser question Koen Kooi
2008-11-29 18:08 ` Phil Blundell
2008-11-29 18:27   ` Koen Kooi
2008-11-30  9:27     ` Koen Kooi [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='ggtm9q$o83$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.