From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/mender: new package
Date: Fri, 4 May 2018 11:16:04 +0200 [thread overview]
Message-ID: <20180504111604.37f6f0e5@windsurf> (raw)
In-Reply-To: <CA+_SqVYNqhb6pAc6wzaf4v79D+Jn9YruJjWhaNJL9NJ-jmc05A@mail.gmail.com>
Hello,
On Fri, 4 May 2018 11:09:52 +0200, Angelo Compagnucci wrote:
> > Not a complete review by far, but I'm wondering if it makes sense to
> > include server certificates in Buildroot. I would assume that one would
> > want to generate his own certificate instead, no ?
>
> It's a test certificate just to starting up. The same file is included
> in the official yocto package so I thought it could useful to have
> here.
Ah, OK. Then perhaps it is fine to have this test certificate as well.
> > Is there anything that makes mender tied to systemd, other than the
> > fact that you provide only a systemd mender.service, and no init
> > script ?
>
> Mender depends on systemd stating to the requirements here
> https://docs.mender.io/1.4/devices/system-requirements
I'm wondering whether this is a real dependency (i.e they are linked
with systemd libraries), or whether it is just that they have only
tested their integration with systemd.
But OK, if they advertise this as a dependency, it's reasonable to have
that as well in Buildroot. It can be relaxed later on if someone is
interested in using Mender in a non-systemd system.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-04 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 21:52 [Buildroot] [PATCH v2] package/mender: new package Angelo Compagnucci
2018-05-04 7:23 ` Thomas Petazzoni
2018-05-04 9:09 ` Angelo Compagnucci
2018-05-04 9:16 ` Thomas Petazzoni [this message]
2018-05-04 9:20 ` Angelo Compagnucci
-- strict thread matches above, loose matches on Subject: below --
2018-06-04 21:37 Dan Walkes
2018-06-05 7:33 ` Thomas Petazzoni
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=20180504111604.37f6f0e5@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 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.