From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: wic/wks boot using labels instead of partitions
Date: Fri, 16 Sep 2022 16:41:48 -0500 [thread overview]
Message-ID: <28322394-c2dd-fc69-be32-466d0cf14906@kernel.crashing.org> (raw)
Is there a way to tell the _generated_ fstab to use labels to boot and not hard
coded partitions?
If I remove the --ondisk <device> attribute from the wks file it defaults to
/dev/sda.
What I tried was:
part /boot --source bootimg-partition --fstype=vfat --label boot --active
--align 4 size 16
part / --source rootfs --fstype=ext4 --label root --align 4
If I manually add --no-fstab-update to the wks entries and add the following to
the system default fstab:
LABEL=boot /boot vfat default 0 2
This works. But I'd like to automate it within the wks.
(Alternatively I could use uuid instead of label booting, but either case, I
need to only boot with the uuid or label -- not the partition as the location of
the disk can change.)
--Mark
next reply other threads:[~2022-09-16 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 21:41 Mark Hatle [this message]
2022-09-17 6:20 ` [OE-core] wic/wks boot using labels instead of partitions Markus Volk
2022-09-17 14:35 ` Mark Hatle
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=28322394-c2dd-fc69-be32-466d0cf14906@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--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