From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v2 0/1] systemd: bump to v213
Date: Sun, 8 Jun 2014 15:33:02 +0200 [thread overview]
Message-ID: <20140608153302.2cc49ded@free-electrons.com> (raw)
In-Reply-To: <1401918049-10503-1-git-send-email-eric.le.bihan.dev@free.fr>
Dear Eric Le Bihan,
On Wed, 4 Jun 2014 23:40:48 +0200, Eric Le Bihan wrote:
> This patch bumps systemd to v213.
>
> This version features systemd-timesyncd, a SNTP daemon, which is useful on
> machines without a RTC, like Raspberry Pi.
Applied, thanks.
> Note that in order to have systemd and this daemon to run properly, some
> changes to /var, /run and /etc/resolv.conf in the target skeleton should be
> made. This can be done in a post-build script (see
> https://github.com/elebihan/buildroot-ext-elb/commit/557d5df324db4ec12d1b98bed7c1a899eb24bdb6
> for an example).
I think we should find a way of making this automatic. I believe it is
quite related to something we've discussed last week with Maxime: maybe
the skeleton should become a proper package, and should be freed from
everything Busybox-specific. Then, we can have additional
skeleton-busybox and skeleton-systemd packages, or some other mechanism
to introduce the specificities needed by these init systems (maybe
directly in the busybox and systemd packages).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-06-08 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 21:40 [Buildroot] [Patch v2 0/1] systemd: bump to v213 Eric Le Bihan
2014-06-04 21:40 ` [Buildroot] [Patch v2 1/1] " Eric Le Bihan
2014-06-08 13:33 ` Thomas Petazzoni [this message]
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=20140608153302.2cc49ded@free-electrons.com \
--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 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.