From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] image.bbclass: add a method to add/delete/modify user/group settings
Date: Mon, 8 Jul 2013 12:15:40 -0500 [thread overview]
Message-ID: <51DAF3BC.60107@windriver.com> (raw)
In-Reply-To: <20130705083905.GD3259@jama>
On 7/5/13 3:39 AM, Martin Jansa wrote:
> On Fri, Jul 05, 2013 at 02:07:28PM +0800, Qi.Chen@windriver.com wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> We may want to add a user or group which does not logically belong to
>> any specific package. For example, we may want to add a user with the
>> name 'tester' to our image. Besides, we may want to delete or modify
>> user/group in our image.
>>
>> This patch adds a variable, USER_GROUP_SETTINGS, which is dedicated
>> to these tasks. The configuration format is detailed in the local.conf.
>> sample.extended file.
>>
>> This patch also adds a function, set_user_group, which happens at
>> the end of the ROOTFS_POSTPROCESS_COMMAND. It handles the settings
>> in the USER_GROUP_SETTINGS variable.
>
> Why not use extra package just with user?
>
> See "[PATCH v3 0/5] Allow xuser to shutdown (cover letter only)"
The issue is that the users don't want extra (empty) packages to just add
standard users/groups. What they want is a post image-generation
"configuration" mechanism.
Adding users/groups is one of the basic items that they want/need. This really
has to be considered to be an administrative activity vs a distribution
activity. (I.e. difference between creating a package and performing some kind
of post-image action.)
The other issue with a package based approach is it then mandates changes occur
by having to rebuild/reinstall packages. This is onerous in my experience, for
something basic like this. It's really outside of the package manager's control.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-07-08 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 6:07 [PATCH 0/1] image.bbclass: add a method for image level user/group configuration Qi.Chen
2013-07-05 6:07 ` [PATCH 1/1] image.bbclass: add a method to add/delete/modify user/group settings Qi.Chen
2013-07-05 8:39 ` Martin Jansa
2013-07-05 9:16 ` ChenQi
2013-07-08 17:15 ` Mark Hatle [this message]
2013-07-08 17:27 ` Martin Jansa
2013-07-08 18:01 ` Mark Hatle
2013-07-08 19:31 ` Martin Jansa
2013-07-08 20:10 ` Mark Hatle
2013-07-08 23:20 ` Saul Wold
2013-07-10 6:42 ` ChenQi
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=51DAF3BC.60107@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox