Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/openssh: Add sysusers.d snippet
Date: Tue, 18 Dec 2018 08:49:37 +0100	[thread overview]
Message-ID: <20181218084937.47142880@windsurf> (raw)
In-Reply-To: <9cf83ac8-2d39-0eb5-92cb-0469eb0a9d6e@mind.be>

Hello,

On Mon, 17 Dec 2018 23:59:04 +0100, Arnout Vandecappelle wrote:

>  Which brings me to my question to Chris: what was the purpose of this patch to
> begin with? Since OPENSSH_USERS is already set, the sshd user will already exist
> in /etc/passwd, so the sysusers.d directive will be ignored... Either that, or
> our mkusers script doesn't work correctly.

Stateless systems, where /etc and /var don't even "exist" in a
persistent fashion, and are entirely populated at boot time.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-12-18  7:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 23:22 [Buildroot] [PATCH] package/openssh: Add sysusers.d snippet Chris Lesiak
2018-02-06 15:10 ` Samuel Martin
2018-02-16 18:10 ` [Buildroot] [PATCH v2] " Chris Lesiak
2018-12-16 13:45   ` Yann E. MORIN
2018-12-17 15:07     ` Chris Lesiak
2018-12-17 18:13       ` Yann E. MORIN
2018-12-17 21:24         ` Chris Lesiak
2018-12-17 22:59         ` Arnout Vandecappelle
2018-12-18  7:49           ` Thomas Petazzoni [this message]
2018-12-18 14:14             ` Chris Lesiak
2018-12-18 14:32               ` Arnout Vandecappelle
2018-12-18 17:03                 ` Chris Lesiak
2019-02-06 13:13                   ` Arnout Vandecappelle
2018-12-18 20:01               ` Yann E. MORIN
2018-12-18 19:59           ` 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=20181218084937.47142880@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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