public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4 0/2] image-bootfiles: new class
Date: Fri, 14 Jun 2024 22:25:19 +0200	[thread overview]
Message-ID: <ZmynL5Cl8rWu-Swg@gmail.com> (raw)
In-Reply-To: <20240530095314.407638-1-marcus.folkesson@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

Hello

On Thu, May 30, 2024 at 11:53:12AM +0200, Marcus Folkesson wrote:
> The image-bootfiles class is used to put all files listed in
> IMAGE_BOOT_FILES into the root filesystem.
> 
> IMAGE_BOOT_FILES is used by the bootimg-partition wic plugin to put the
> files into a boot partition. 
> Be able to list files as "boot files" in e.g. your .conf or image files
> instead of install those in every recipe is a good thing.
> 
> It is not always desired to have a separate boot partition for boot
> files. Sometimes it could be good to have them as a part of the root
> filesystem.
> 
> For example, if a double copy strategy is used for update the system,
> then you probably want to update both the boot files and root filesystem
> at the same time as there may be dependencies.

I have received some feedback on this, but I would appreciate it if more
people could share their thought about it.

I still think this is a feature we should add, even though the way
this (and bootimg-partition) works has some drawbacks in terms of design.

Since the codebase is now shared between image-bootfiles
and bootimg-partition, I imagine that both are redone in a potential
re-design.

Best regards,
Marcus Folkesson


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2024-06-14 20:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30  9:53 [PATCH v4 0/2] image-bootfiles: new class Marcus Folkesson
2024-05-30  9:53 ` [PATCH v4 1/2] bootimg-partition: break out code to a common library Marcus Folkesson
2024-05-30  9:53 ` [PATCH v4 2/2] image-bootfiles.bbclass: new class, copy boot files to root filesystem Marcus Folkesson
2024-05-31 12:09   ` Quentin Schulz
2024-06-16  4:26   ` Konrad Weihmann
2024-06-17  6:23     ` [OE-core] " Marcus Folkesson
2024-06-11 10:37 ` [OE-core] [PATCH v4 0/2] image-bootfiles: new class Ross Burton
2024-06-11 13:22   ` Marcus Folkesson
2024-06-11 14:44     ` Martin Hundebøll
2024-06-11 15:04       ` Marcus Folkesson
2024-07-16 11:28     ` Ross Burton
2024-07-22  7:36       ` Marcus Folkesson
2024-06-14 20:25 ` Marcus Folkesson [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=ZmynL5Cl8rWu-Swg@gmail.com \
    --to=marcus.folkesson@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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