From: prez <prez@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: systemd-boot-efistub-253
Date: Sun, 02 Apr 2023 21:48:34 +0200 [thread overview]
Message-ID: <20230402194834.YaxVzfxE14NZFdhiydHwIMAqCwGOLL-XfCKAsBgppeo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42667@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
New comment by prez on void-packages repository
https://github.com/void-linux/void-packages/pull/42667#issuecomment-1493424924
Comment:
I've been testing this on my system (x86_64 glibc) - systemd-boot works well.
The hook could use some logic to check whether the configured kernel is newer than the current default one (always replacing the default with a potentially older kernel isn't expected behaviour, I think).
And here's a suggestion for a post-remove hook:
```sh
#!/bin/sh
#
# Kernel post-remove hook for systemd-boot.
#
# Arguments passed to this script: $1 pkgname, $2 version.
#
PKGNAME="$1"
VERSION="$2"
. "$ROOTDIR/etc/default/systemd-boot"
if [ "$SYSTEMD_BOOT_DISABLE" ]; then
exit 0
fi
boot="$ROOTDIR/boot"
entries="$boot/loader/entries"
name="void-$VERSION"
entry="$entries/$name.conf"
loader="$boot/loader/loader.conf"
[ -r "$loader" ] || exit 0
rm -f "$entry"
if grep -q "^default ${name}" "$loader" 2>/dev/null; then
# Replace removed default entry with another
alternative="$(ls -r "$entries" | head -n 1)"
[ -n "$alternative" ] || exit 0
sed -i "s/default.*/default ${alternative%.conf}/" "$loader"
fi
```
next prev parent reply other threads:[~2023-04-02 19:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 0:25 [PR PATCH] " classabbyamp
2023-03-09 0:28 ` [PR PATCH] [Updated] " classabbyamp
2023-03-09 0:29 ` classabbyamp
2023-03-09 0:40 ` classabbyamp
2023-03-09 0:46 ` classabbyamp
2023-03-09 0:58 ` classabbyamp
2023-03-11 8:38 ` classabbyamp
2023-03-11 19:26 ` classabbyamp
2023-03-11 19:38 ` classabbyamp
2023-03-11 20:14 ` classabbyamp
2023-03-13 1:48 ` prez
2023-03-13 2:12 ` classabbyamp
2023-03-13 6:44 ` sonnysighedup
2023-03-13 6:45 ` sonnysighedup
2023-03-13 11:24 ` NymanMatthias
2023-03-14 22:18 ` prez
2023-03-14 22:23 ` prez
2023-03-15 4:32 ` 0x5c
2023-03-15 4:41 ` classabbyamp
2023-03-15 12:04 ` prez
2023-03-17 1:07 ` [PR PATCH] [Updated] " classabbyamp
2023-03-17 1:43 ` 0x5c
2023-03-30 12:31 ` [PR REVIEW] " prez
2023-03-30 12:31 ` prez
2023-04-02 19:48 ` prez [this message]
2023-04-02 20:00 ` classabbyamp
2023-04-25 11:57 ` junkmanner
2023-04-25 14:04 ` classabbyamp
2023-04-25 14:04 ` classabbyamp
2023-04-25 14:04 ` classabbyamp
2023-07-25 2:01 ` github-actions
2023-09-08 8:03 ` [PR PATCH] [Updated] " classabbyamp
2023-09-08 8:04 ` classabbyamp
2023-09-08 8:06 ` New package: systemd-boot-254.2 classabbyamp
2023-09-08 8:27 ` [PR PATCH] [Updated] " classabbyamp
2023-09-08 8:29 ` classabbyamp
2023-10-05 11:31 ` MeganerdNL
2023-10-05 11:32 ` MeganerdNL
2023-10-05 11:42 ` MeganerdNL
2023-10-05 12:18 ` classabbyamp
2023-10-05 12:43 ` MeganerdNL
2024-01-04 1:46 ` github-actions
2024-02-01 20:53 ` dkwo
2024-02-01 20:53 ` dkwo
2024-02-01 21:26 ` dkwo
2024-02-02 18:56 ` [PR PATCH] [Updated] " classabbyamp
2024-02-02 22:34 ` [PR PATCH] [Updated] New package: systemd-boot-efistub-255.3 classabbyamp
2024-02-02 22:50 ` [PR PATCH] [Merged]: " classabbyamp
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=20230402194834.YaxVzfxE14NZFdhiydHwIMAqCwGOLL-XfCKAsBgppeo@z \
--to=prez@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).