From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] system/skeleton: add the shadow-group file
Date: Tue, 01 Jan 2013 22:08:29 +0100 [thread overview]
Message-ID: <87k3rwsjaq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <201301011636.05672.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Tue, 1 Jan 2013 16:36:05 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
>> The next question that comes up is: do we really need to support this
>> in Buildroot?
Yann> Well, I interpreted the abscence of that file as an oversight,
Yann> that's why I thought of adding it.
Yann> Right, we probably do not need the change-group feature in
Yann> buildroot. However, for the sake of consistency, I think it is
Yann> good to have gshadow.
Yann> But I can very well live without it, sure.
Well, the fact that nobody has ever asked for it in the 11 years
buildroot has existed and that Thomas (and me) didn't know about the
file, makes me think that perhaps it isn't too important to support it
in the default skeleton (you can certainly manually add it).
Yann> Anyway... Happy New Year to all! :-)
Thanks, same to you!
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-01-01 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 23:26 [Buildroot] [pull request] Pull request for branch yem-package-create-user Yann E. MORIN
2012-12-30 23:26 ` [Buildroot] [PATCH 1/3] system/skeleton: add the shadow-group file Yann E. MORIN
2012-12-31 17:18 ` Thomas Petazzoni
2012-12-31 18:18 ` Yann E. MORIN
2013-01-01 9:26 ` Thomas Petazzoni
2013-01-01 15:36 ` Yann E. MORIN
2013-01-01 21:08 ` Peter Korsgaard [this message]
2012-12-30 23:26 ` [Buildroot] [PATCH 2/3] packages: add ability for packages to create users Yann E. MORIN
2012-12-30 23:26 ` [Buildroot] [PATCH 3/3] package/tvheadend: use a non-root user to run the daemon Yann E. MORIN
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=87k3rwsjaq.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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