From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Stephen Ecker <stephenecker240@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: initramfs:/etc/fstab empty (efibootguard)
Date: Sat, 21 Dec 2024 00:19:38 +0100 [thread overview]
Message-ID: <342b0bc4-1bf9-44a6-9702-596a4c54e5b8@web.de> (raw)
In-Reply-To: <8426e43a-f5c4-4341-83a7-b16468df061en@googlegroups.com>
On 20.12.24 22:41, Stephen Ecker wrote:
> Hello. I am using efibootguard and it is generating an empty fstab in
> the initramfs. In an attempt to understand why, I wanted to just try
> and rebuilding the initramfs myself, then create the kernel again using
> bg_gen_unified_kernel, but I cannot even build the initramfs from the
> image because there is no /boot/config-* files.
>
> can someone help me understand where and how the initramfs and unified
> kernel is created in these recipes?
>
The related recipes are part of isar-cip-core which is discussed on
cip-dev@lists.cip-project.org. Please describe over there which steps
you exactly took and which layer versions and configurations you used.
To learn more about the UKI generation, you could already study
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/blob/master/scripts/lib/wic/plugins/source/efibootguard-boot.py?ref_type=heads
Jan
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/342b0bc4-1bf9-44a6-9702-596a4c54e5b8%40web.de.
prev parent reply other threads:[~2024-12-20 23:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 21:41 Stephen Ecker
2024-12-20 23:19 ` 'Jan Kiszka' via isar-users [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=342b0bc4-1bf9-44a6-9702-596a4c54e5b8@web.de \
--to=isar-users@googlegroups.com \
--cc=jan.kiszka@web.de \
--cc=stephenecker240@gmail.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