From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/dhcp: dhcp server: select systemd tmpfile support when systemd is used
Date: Mon, 26 Jun 2017 22:24:15 +0200 [thread overview]
Message-ID: <87tw32fqfk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170624232810.2728f3ab@windsurf.home> (Thomas Petazzoni's message of "Sat, 24 Jun 2017 23:28:10 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Sat, 27 May 2017 00:13:48 +0200, Romain Naour wrote:
>> tmpfile support is optional in systemd but the dhcp server install it's
>> config file in $(TARGET_DIR)/usr/lib/tmpfiles.d directory when systemd
>> is used as init system.
>>
>> So it seems that dhcp server require tmpfile support for systemd based
>> system.
>>
>> Signed-off-by: Romain Naour <romain.naour@gmail.com>
>> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>> ---
>> package/dhcp/Config.in | 1 +
>> 1 file changed, 1 insertion(+)
> I'm not a big expert in systemd stuff, but nobody else complained for
> almost a month, so I've applied your patch. Thanks!
Committed to 2017.02.x and 2017.05.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-06-26 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 22:13 [Buildroot] [PATCH 1/2] package/dhcp: create tmpfiles.d directory Romain Naour
2017-05-26 22:13 ` [Buildroot] [PATCH 2/2] package/dhcp: dhcp server: select systemd tmpfile support when systemd is used Romain Naour
2017-06-24 21:28 ` Thomas Petazzoni
2017-06-26 20:24 ` Peter Korsgaard [this message]
2017-05-27 7:45 ` [Buildroot] [PATCH 1/2] package/dhcp: create tmpfiles.d directory Bernd Kuhls
2017-05-27 15:18 ` Thomas Petazzoni
2017-06-01 14:19 ` Peter Korsgaard
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=87tw32fqfk.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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 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.