All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Use useradd and update-rc.d classes in the OpenSSH recipe
Date: Mon, 26 Sep 2011 20:51:52 -0400	[thread overview]
Message-ID: <4E811E28.1020106@windriver.com> (raw)
In-Reply-To: <CAKZ=5EUPf9GrTjP=odYcxRYqkONZnqzoDd0kBWn-UdqOO5efFw@mail.gmail.com>

On 9/26/11 8:47 PM, Julian Pidancet wrote:
> On Tue, Sep 27, 2011 at 12:59 AM, Julian Pidancet
> <julian.pidancet@gmail.com> wrote:
>> On Tue, Sep 27, 2011 at 12:38 AM, Saul Wold <sgw@linux.intel.com> wrote:
>>>
>>> Is there a reason you did not include the group and --disable-password here?
>>>
>>> I think it would be good to leave thelong name options in also.
>>>
>>> Sau!
>>>
>>
>> The -U option creates a group with the same name. The
>> --disable-password option only exists with adduser and is default with
>> useradd -r.
>> I'd just like to point out that adduser is originally a perl script
>> from debian and reimplemented in busybox. The options it takes are not
>> compatible with the more standard useradd from the shadow package.
>>
>> For some reason, some long options like --system (which is supposed to
>> be supported in useradd) did not work during my first
>> experimentations, but I will investigate and respin a patch with long
>> options if possible.
>>
>> Also, I discovered that the following recipes still depends on adduser:
>> ppp-dialin, avahi, distcc, xserver-nodm-init, pulseaudio, hal, dbus
>>
>> It would be good to use the useradd class with all of them.
>>
> 
> In the shadow-sysroot package that we build to be able to use the
> useradd class, we apply the add_root_cmd_options.patch to add the
> --root option to useradd.
> 
> The --root option allows useradd to chroot somewhere so it can modify
> /etc/passwd, but at the same time, it disables all the other long
> options in the program.
> 
> It looks like it is impossible to use long options with the useradd
> class. I don't know how straighforward it would be to modify this
> patch to get the long options back. But is it worth the pain ?
> 

If the long options got disabled due to the path, it's a bug.

(File a bug on bugzilla.yoctoproject.org and someone will look at it.. or submit
a patch...)

--Mark



  reply	other threads:[~2011-09-27  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-25 12:55 [PATCH] Use useradd and update-rc.d classes in the OpenSSH recipe Julian Pidancet
2011-09-26 23:38 ` Saul Wold
2011-09-26 23:59   ` Julian Pidancet
2011-09-27  0:47     ` Julian Pidancet
2011-09-27  0:51       ` Mark Hatle [this message]
2011-09-27 20:44       ` Scott Garman

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=4E811E28.1020106@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.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.