From: henning.schild@siemens.com
To: isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH v5 3/6] meta-isar: introduce an example to use btrfs
Date: Thu, 15 Dec 2022 15:27:56 +0100 [thread overview]
Message-ID: <20221215142759.26327-4-henning.schild@siemens.com> (raw)
In-Reply-To: <20221215142759.26327-1-henning.schild@siemens.com>
From: Henning Schild <henning.schild@siemens.com>
Switch debian bullseye over to btrfs rootfs and also to btrfs in last
partition to have a target where we test expand-on-first-boot for btrfs.
Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
meta-isar/conf/machine/qemuamd64.conf | 5 +++++
.../scripts/lib/wic/canned-wks/sdimage-efi-btrfs.wks | 9 +++++++++
2 files changed, 14 insertions(+)
create mode 100644 meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-btrfs.wks
diff --git a/meta-isar/conf/machine/qemuamd64.conf b/meta-isar/conf/machine/qemuamd64.conf
index eca2628c4ae5..6b40cb50702e 100644
--- a/meta-isar/conf/machine/qemuamd64.conf
+++ b/meta-isar/conf/machine/qemuamd64.conf
@@ -13,6 +13,11 @@ IMAGER_INSTALL += "${GRUB_BOOTLOADER_INSTALL}"
WKS_FILE_ubuntu-focal ?= "sdimage-efi-sd"
IMAGER_INSTALL_remove_ubuntu-focal = "${GRUB_BOOTLOADER_INSTALL}"
+WKS_FILE_debian-bullseye ?= "sdimage-efi-btrfs"
+IMAGER_INSTALL_remove_debian-bullseye = "${GRUB_BOOTLOADER_INSTALL}"
+IMAGER_INSTALL_append_debian-bullseye = " ${SYSTEMD_BOOTLOADER_INSTALL} btrfs-progs"
+IMAGE_PREINSTALL_append_debian-bullseye = " btrfs-progs"
+
IMAGE_INSTALL += "sshd-regen-keys"
QEMU_ARCH ?= "x86_64"
diff --git a/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-btrfs.wks b/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-btrfs.wks
new file mode 100644
index 000000000000..014ecca61f0c
--- /dev/null
+++ b/meta-isar/scripts/lib/wic/canned-wks/sdimage-efi-btrfs.wks
@@ -0,0 +1,9 @@
+# short-description: Create an EFI disk image without any swap and btrfs
+# long-description: Creates a partitioned EFI disk image without any swap that
+# the user can directly dd to boot media, where the last partition is btrfs.
+
+part /boot --source bootimg-efi-isar --sourceparams "loader=systemd-boot" --ondisk sda --label efi --part-type EF00 --align 1024
+
+part / --source rootfs --ondisk sda --fstype btrfs --label platform --align 1024 --use-uuid --exclude-path boot/
+
+bootloader --ptable gpt --timeout 3 --append "rootwait console=ttyS0,115200 console=tty0"
--
2.37.4
next prev parent reply other threads:[~2022-12-15 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 14:27 [PATCH v5 0/6] expand-on-first-boot btrfs and CI testing henning.schild
2022-12-15 14:27 ` [PATCH v5 1/6] expand-on-first-boot: really only do that once, especially on failure henning.schild
2022-12-15 15:32 ` Roberto A. Foglietta
2022-12-15 14:27 ` [PATCH v5 2/6] expand-on-first-boot: support resizing a btrfs henning.schild
2022-12-15 17:48 ` Roberto A. Foglietta
2022-12-15 14:27 ` henning.schild [this message]
2022-12-15 14:27 ` [PATCH v5 4/6] CI: improve cibuilder readability henning.schild
2022-12-15 14:27 ` [PATCH v5 5/6] meta-isar: install expand-on-first-boot in most images and add space henning.schild
2022-12-15 14:27 ` [PATCH v5 6/6] CI: expect a message about filesystem resize vom expand script henning.schild
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=20221215142759.26327-4-henning.schild@siemens.com \
--to=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