From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ee9476348b72e666ea42c4fa72c1e88ddce7cc0b
Date: Mon, 03 Jul 2023 17:51:12 +0000 [thread overview]
Message-ID: <4Qvtl43BW6z2xnv@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via ee9476348b72e666ea42c4fa72c1e88ddce7cc0b (commit)
from 5ea686072b9c398ef886eec2c48fb0b091817bf8 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit ee9476348b72e666ea42c4fa72c1e88ddce7cc0b
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Mon Jul 3 17:50:36 2023 +0000
Core Update 177: Rebuild initial ramdisk to apply AMD microcode updates
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/177/update.sh | 10 ++++++++++
1 file changed, 10 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/177/update.sh b/config/rootfiles/core/177/update.sh
index a3a141dae..43f9a02f6 100644
--- a/config/rootfiles/core/177/update.sh
+++ b/config/rootfiles/core/177/update.sh
@@ -59,6 +59,16 @@ if [ -f /var/ipfire/proxy/enable ]; then
/etc/init.d/squid restart
fi
+# Rebuild initial ramdisk to apply microcode updates
+dracut --regenerate-all --force
+KVER="xxxKVERxxx"
+case "$(uname -m)" in
+ aarch64)
+ mkimage -A arm64 -T ramdisk -C lzma -d /boot/initramfs-${KVER}-ipfire.img /boot/uInit-${KVER}-ipfire
+ # dont remove initramfs because grub need this to boot.
+ ;;
+esac
+
# This update needs a reboot...
touch /var/run/need_reboot
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-07-03 17:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4Qvtl43BW6z2xnv@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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