Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/8] package/mender: add BR2_PACKAGE_MENDER_DEVICE_TYPE option
Date: Wed, 15 Aug 2018 19:47:08 +0200	[thread overview]
Message-ID: <20180815194708.733bc58d@windsurf> (raw)
In-Reply-To: <CADHdJwB11mau2fiZsWCy=og6uEmSzybNDULUNXHr8T+s-CSB2Q@mail.gmail.com>

Hello,

On Wed, 15 Aug 2018 14:46:20 +0200, Mirza Krak wrote:

> >> > I am a bit confused with "Note that /data is a mount point for the
> >> > persistent data partition". If /data is a different partition than the
> >> > root filesystem one, then what is the point of
> >> > having /data/mender/device_type in the root filesystem ? It will be
> >> > hidden by whatever partition gets mounted in /data.  
> >>
> >> Understand the confusion, my intention was to convert the /data
> >> directory on target image to an ext4 image in a post build step  
> >
> > Why do you want to do this ?  
> 
> In the end I would like to create a "disk image" with _all_ the
> content, and the data part must be populated at build time, as it
> works at the moment.
> 
> Pseudo image:
> 
> image sdcard.img {
>     hdimage {
>     }
> 
>     partition u-boot {
>         partition-type = 0xC
>         bootable = "true"
>                 image = "boot.vfat"
>     }
> 
>     partition rootfsA {
>         partition-type = 0x83
>         image = "rootfs.ext4"
>         size = 512M
>     }
> 
>     partition rootfsB {
>         partition-type = 0x83
>         image = "rootfs.ext4"
>         size = 512M
>     }
> 
>     partition data {
>         partition-type = 0x83
>         image = "data.ext4"
>         size = 512M
>     }
> }

I don't think we should enforce anything like that in the Mender
package. Buildroot's policy is to not have much policy on how the
system should be structured/organized. Maybe people won't need any data
partition because the system is completely state-less ? Maybe they need
two data partitions ? Maybe having it in /data is not what they want.

So, the mender package should not make any assumption like this. And I
still don't get why the device_type file should be in this data
partition :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-15 17:47 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 23:13 [Buildroot] [PATCH 0/8] various improvements to package/mender Mirza Krak
2018-08-14 23:13 ` [Buildroot] [PATCH 1/8] package/mender: update legal info Mirza Krak
2018-08-14 23:32   ` Arnout Vandecappelle
2018-08-15  7:37     ` Mirza Krak
2018-08-16 15:36       ` Arnout Vandecappelle
2018-08-16 19:59         ` Mirza Krak
2018-08-16 20:18         ` Mirza Krak
2018-08-17  3:48           ` Baruch Siach
2018-08-17  6:53             ` Mirza Krak
2018-08-14 23:13 ` [Buildroot] [PATCH 2/8] package/mender: update install of config files Mirza Krak
2018-08-15 12:31   ` Thomas Petazzoni
2018-08-15 12:42     ` Mirza Krak
2018-08-15 17:41       ` Thomas Petazzoni
2018-08-15 18:48         ` Mirza Krak
2018-08-15 19:02           ` Thomas Petazzoni
2018-08-14 23:13 ` [Buildroot] [PATCH 3/8] package/mender: add dep on BR2_PACKAGE_UBOOT_TOOLS_FWPRINTENV Mirza Krak
2018-08-15  5:08   ` Baruch Siach
2018-08-15  7:21     ` Mirza Krak
2018-08-14 23:13 ` [Buildroot] [PATCH 4/8] package/mender: add BR2_PACKAGE_MENDER_ARTIFACT_NAME option Mirza Krak
2018-08-15  5:10   ` Baruch Siach
2018-08-15  7:23     ` Mirza Krak
2018-08-15 11:53   ` Thomas Petazzoni
2018-08-15 12:23     ` Mirza Krak
2018-08-14 23:13 ` [Buildroot] [PATCH 5/8] package/mender: add BR2_PACKAGE_MENDER_DEVICE_TYPE option Mirza Krak
2018-08-15 11:55   ` Thomas Petazzoni
2018-08-15 12:26     ` Mirza Krak
2018-08-15 12:42       ` Thomas Petazzoni
2018-08-15 12:46         ` Mirza Krak
2018-08-15 17:47           ` Thomas Petazzoni [this message]
2018-08-15 19:41             ` Mirza Krak
2018-08-14 23:13 ` [Buildroot] [PATCH 6/8] package/mender: populate the mender.conf template Mirza Krak
2018-08-15 11:56   ` Thomas Petazzoni
2018-08-15 12:27     ` Mirza Krak
2018-08-14 23:13 ` [Buildroot] [PATCH 7/8] package/mender: select BR2_PACKAGE_CA_CERTIFICATES Mirza Krak
2018-08-15 11:57   ` Thomas Petazzoni
2018-08-15 12:28     ` Mirza Krak
2018-08-14 23:13 ` [Buildroot] [PATCH 8/8] package/mender: set version in go linker Mirza Krak
2018-08-15 11:58   ` Thomas Petazzoni
2018-08-15 12:32     ` Mirza Krak
2018-08-15 12:43       ` 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=20180815194708.733bc58d@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