From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] RFC: move kernels out of /boot
Date: Mon, 01 Jan 2024 23:46:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48024@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
New issue by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/48024
Description:
Some distributions have started to move the kernels out of the boot directory by default and let the install hooks etc handle copying them over.
The kernel hooks would then copy the kernels into `/boot`, users could then change the hooks to i.e. allow to create unified kernel image (UKI) executable without the extra duplication between the UKI file and the package dropped kernel binary.
Seems like the "standard" location for kernel files would be `/usr/lib/modules/${VERSION}/vmlinuz`.
Advantages:
- kernels can be copied to /boot and modified for i.e. signing.
- kernels don't have to be copied to /boot for UKIs.
- kernel.d post install moves kernels after the initramfs hook, the stupid grub mkconfig wouldn't put up kernels for which initramfs generation failed. (https://github.com/void-linux/void-packages/issues/46006)
- Maybe good for raspberrypi kernels too, let install hooks move them to the weird kernel8.img names?
next reply other threads:[~2024-01-01 22:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 22:46 Duncaen [this message]
2024-01-02 11:22 ` dkwo
2024-01-09 16:10 ` mbsmith
2024-01-09 16:12 ` classabbyamp
2024-01-09 16:13 ` classabbyamp
2024-01-09 16:13 ` classabbyamp
2024-01-09 16:27 ` mbsmith
2024-01-18 15:13 ` Jipok
2024-01-18 15:27 ` Johnnynator
2024-02-12 14:44 ` CtrlC-Root
2024-05-13 1:47 ` github-actions
2024-05-13 1:48 ` CtrlC-Root
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48024@inbox.vuxu.org \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).