From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [[PATCH v2 03/14] package/mender: create directory structures required by the Mender client
Date: Mon, 20 Aug 2018 15:15:31 +0200 [thread overview]
Message-ID: <20180820151531.095a087d@windsurf> (raw)
In-Reply-To: <20180820130914.22377-4-mirza.krak@northern.tech>
Hello,
On Mon, 20 Aug 2018 15:09:03 +0200, Mirza Krak wrote:
> /uboot is a mount point for vfat boot partition.
> /data is a mount point for the persistent data partition.
>
> Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
> ---
> package/mender/mender.mk | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/package/mender/mender.mk b/package/mender/mender.mk
> index deab0cb039..71f92ce048 100644
> --- a/package/mender/mender.mk
> +++ b/package/mender/mender.mk
> @@ -8,6 +8,10 @@ MENDER_VERSION = 1.4.0
> MENDER_SITE = $(call github,mendersoftware,mender,$(MENDER_VERSION))
>
> define MENDER_INSTALL_CONFIG_FILES
> + $(INSTALL) -d -m 755 $(TARGET_DIR)/data/mender
> + $(INSTALL) -d -m 755 $(TARGET_DIR)/data/uboot
> + $(INSTALL) -d -m 755 $(TARGET_DIR)/uboot
I am sorry, but despite the explanations, I still don't understand why
these *must* be /data and /uboot. Is Mender *enforcing* those locations
exactly ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-20 13:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 13:09 [Buildroot] [[PATCH v2 00/14] various improvements to package/mender Mirza Krak
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 01/14] package/mender: fix install path for identity and inventory scripts Mirza Krak
2018-08-20 14:51 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 02/14] package/mender: provide sane values in mender.conf Mirza Krak
2018-08-20 14:51 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 03/14] package/mender: create directory structures required by the Mender client Mirza Krak
2018-08-20 13:15 ` Thomas Petazzoni [this message]
2018-08-20 13:35 ` Mirza Krak
2018-08-20 13:43 ` Mirza Krak
2018-08-20 14:31 ` Mirza Krak
2018-10-21 14:27 ` Arnout Vandecappelle
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 04/14] package/mender: create directory containing Mender state script Mirza Krak
2018-08-20 14:51 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 05/14] package/mender: symlink /var/lib/mender -> /data/mender Mirza Krak
2018-08-20 18:36 ` Mirza Krak
2018-08-20 20:04 ` Thomas Petazzoni
2018-08-20 20:33 ` Mirza Krak
2018-10-21 14:36 ` Arnout Vandecappelle
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 06/14] package/mender: select BR2_PACKAGE_UBOOT_TOOLS_FWPRINTENV Mirza Krak
2018-08-20 14:52 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 07/14] package/mender: select BR2_PACKAGE_CA_CERTIFICATES Mirza Krak
2018-08-20 14:54 ` Thomas Petazzoni
2018-08-20 18:33 ` Mirza Krak
2018-10-21 14:37 ` Arnout Vandecappelle
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 08/14] package/mender: remove tenant.conf Mirza Krak
2018-08-20 15:15 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 09/14] package/mender: use inventory and identity script from upstream source Mirza Krak
2018-08-20 15:15 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 10/14] package/mender: update legal info Mirza Krak
2018-08-20 15:15 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 11/14] package/mender: set version in go linker Mirza Krak
2018-08-20 15:15 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 12/14] package/mender: use MENDER_PKGDIR to access local files Mirza Krak
2018-10-21 14:09 ` Thomas Petazzoni
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 13/14] package/mender: add BR2_PACKAGE_MENDER_ARTIFACT_NAME option Mirza Krak
2018-10-21 14:40 ` Arnout Vandecappelle
2018-08-20 13:09 ` [Buildroot] [[PATCH v2 14/14] package/mender: add BR2_PACKAGE_MENDER_DEVICE_TYPE option Mirza Krak
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=20180820151531.095a087d@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