From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] systemd 216: add system user factory files to CONFFILES
Date: Tue, 30 Sep 2014 09:51:47 +0100 [thread overview]
Message-ID: <1412067107.6893.33.camel@ted> (raw)
In-Reply-To: <18401A03-E69C-43BB-9956-13955179B13A@dominion.thruhere.net>
On Tue, 2014-09-30 at 09:39 +0200, Koen Kooi wrote:
> Op 29 sep. 2014, om 22:59 heeft Colin Walters <walters@verbum.org> het volgende geschreven:
>
> >
> >
> > On Sat, Sep 27, 2014, at 03:22 AM, Koen Kooi wrote:
> >
> >> + ${libdir}/sysusers.d/systemd.conf \
> >> + ${libdir}/sysusers.d/basic.conf \
> >
> > Admins aren't expected to edit these - instead you override in /etc. Or
> > change /etc/passwd after the user has been created, and your changes
> > will be respected.
>
> The real question is: do we want to keep changes to these files on package upgrade or wipe them out?
or should we encourage users to edit the files that are supposed to be
edited?
You could argue this for every file on the system, binaries and all :/.
Cheers,
Richard
next prev parent reply other threads:[~2014-09-30 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 7:22 [PATCH 1/2] systemd 216: add postinsts for hostname and machine nss modules Koen Kooi
2014-09-27 7:22 ` [PATCH 2/2] systemd 216: add system user factory files to CONFFILES Koen Kooi
2014-09-29 20:59 ` Colin Walters
2014-09-30 7:39 ` Koen Kooi
2014-09-30 8:51 ` Richard Purdie [this message]
2014-09-30 9:36 ` Burton, Ross
2014-09-30 13:26 ` Colin Walters
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=1412067107.6893.33.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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