From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] skeleton: add systemd network.service unit
Date: Fri, 3 Jan 2014 20:13:33 +0100 [thread overview]
Message-ID: <20140103201333.7f4edd47@skate> (raw)
In-Reply-To: <1388713112-4686-1-git-send-email-vsergeev@kumunetworks.com>
Dear Ivan Sergeev,
On Thu, 2 Jan 2014 17:38:32 -0800, Ivan Sergeev wrote:
> Add and enable a systemd unit file to bring up / down network with ifup /
> ifdown, analogous to the skeleton/etc/init.d/S40network init script.
>
> Signed-off-by: Ivan Sergeev <vsergeev@kumunetworks.com>
> ---
> .../system/multi-user.target.wants/network.service | 1 +
> system/skeleton/etc/systemd/system/network.service | 21 +++++++++++++++++++++
> 2 files changed, 22 insertions(+)
> create mode 120000 system/skeleton/etc/systemd/system/multi-user.target.wants/network.service
> create mode 100644 system/skeleton/etc/systemd/system/network.service
We probably want to make that conditional on the type of init system
that is used, no?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-03 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 1:38 [Buildroot] [PATCH 1/1] skeleton: add systemd network.service unit Ivan Sergeev
2014-01-03 19:13 ` Thomas Petazzoni [this message]
2014-01-03 19:41 ` Ivan Sergeev
2014-01-28 1:54 ` [Buildroot] [PATCH 1/1] systemd: add network unit file Ivan Sergeev
2014-06-11 20:34 ` Thomas Petazzoni
2014-06-13 15:42 ` Eric Le Bihan
2014-06-13 15:44 ` Thomas Petazzoni
2014-01-28 7:13 ` [Buildroot] [PATCH 1/1] skeleton: add systemd network.service unit Arnout Vandecappelle
2014-01-28 8:25 ` Maxime Hadjinlian
2014-01-28 8:38 ` Arnout Vandecappelle
2014-01-28 13:20 ` Maxime Ripard
2014-01-28 17:20 ` Arnout Vandecappelle
2014-01-29 8:26 ` Maxime Ripard
2014-01-29 9:07 ` Maxime Hadjinlian
2014-01-29 9:09 ` 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=20140103201333.7f4edd47@skate \
--to=thomas.petazzoni@free-electrons.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