From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: Re: [PATCH v7 5/6] meta-isar: install expand-on-first-boot in most images and add space
Date: Fri, 23 Dec 2022 20:11:24 +0100 [thread overview]
Message-ID: <CAJGKYO6YVWRj8UPehpvjJ3U_rzjbXtg_niGtUn+gQiX4pUY71Q@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO5iU9CehYHAHfp-zqXctr+GVFGxo+bcCL89sezsmty=og@mail.gmail.com>
On Fri, 23 Dec 2022 at 16:43, Roberto A. Foglietta
<roberto.foglietta@gmail.com> wrote:
> Moreover, I saw that there are .conf files for producing vmdk and ova
> files. IMHO, a more general and flexible approach is to create these
> files directly from the .wic image, like in my project
>
> wicinst vmdk:$filename.vmdk [disk_size_in_gigabytes]
>
> wicinst ovaf:$filename.ova [disk_size_in_gigabytes]
However, some automatic test systems might prefer the .ova or .vmdk as
the ultimate output of the building without the necessity to call a
secondary script. I have not in mind anyone but I cannot exclude that
they exist. So, the two approaches can exist together as complementary
ones. Or possibly, their .conf allows a more tunable output than a
mere conversion which is easier to adopt during the development,
instead. IMHO.
> Best regards, R-
next prev parent reply other threads:[~2022-12-23 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 8:55 [PATCH v7 0/6] expand-on-first-boot btrfs and CI testing Henning Schild
2022-12-23 8:55 ` [PATCH v7 1/6] expand-on-first-boot: really only do that once, especially on failure Henning Schild
2022-12-23 8:55 ` [PATCH v7 2/6] expand-on-first-boot: support resizing a btrfs Henning Schild
2022-12-23 8:55 ` [PATCH v7 3/6] meta-isar: introduce an example to use btrfs Henning Schild
2022-12-23 8:55 ` [PATCH v7 4/6] CI: improve cibuilder readability Henning Schild
2022-12-23 8:55 ` [PATCH v7 5/6] meta-isar: install expand-on-first-boot in most images and add space Henning Schild
2022-12-23 15:43 ` Roberto A. Foglietta
2022-12-23 19:11 ` Roberto A. Foglietta [this message]
2022-12-23 8:55 ` [PATCH v7 6/6] CI: expect a message about filesystem resize vom expand script Henning Schild
2022-12-23 9:07 ` [PATCH v7 0/6] expand-on-first-boot btrfs and CI testing Henning Schild
2022-12-30 19:18 ` Anton Mikanovich
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=CAJGKYO6YVWRj8UPehpvjJ3U_rzjbXtg_niGtUn+gQiX4pUY71Q@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/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