From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 146d6a8845ccb2da73d8b5701ccde94b45ced76c
Date: Thu, 19 Nov 2026 10:15:14 +0000 (UTC) [thread overview]
Message-ID: <4jVZ8y2bpFz2xVM@people01.haj.ipfire.org> (raw)
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, master has been updated
via 146d6a8845ccb2da73d8b5701ccde94b45ced76c (commit)
from cd0a94f3daa66fa4190233af7bc83251fee08924 (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 146d6a8845ccb2da73d8b5701ccde94b45ced76c
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Thu Nov 19 10:13:09 2026 +0000
core206: Ship the kernel in the updater
The kernel has been updated since Core Update 205, but it was not part of the update. Add it to the file lists for all architectures and perform the usual sanity checks and cleanup of the old kernel in update.sh.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
.../124 => core/206}/filelists/aarch64/linux | 0
.../rootfiles/core/206/filelists/loongarch64/linux | 1 +
.../181 => core/206}/filelists/riscv64/linux | 0
.../100 => core/206}/filelists/x86_64/linux | 0
config/rootfiles/core/206/update.sh | 63 +++++++++++++++++++++-
5 files changed, 63 insertions(+), 1 deletion(-)
copy config/rootfiles/{oldcore/124 => core/206}/filelists/aarch64/linux (100%)
create mode 120000 config/rootfiles/core/206/filelists/loongarch64/linux
copy config/rootfiles/{oldcore/181 => core/206}/filelists/riscv64/linux (100%)
copy config/rootfiles/{oldcore/100 => core/206}/filelists/x86_64/linux (100%)
Difference in files:
diff --git a/config/rootfiles/core/206/filelists/aarch64/linux b/config/rootfiles/core/206/filelists/aarch64/linux
new file mode 120000
index 000000000..3a2532bc7
--- /dev/null
+++ b/config/rootfiles/core/206/filelists/aarch64/linux
@@ -0,0 +1 @@
+../../../../common/aarch64/linux
\ No newline at end of file
diff --git a/config/rootfiles/core/206/filelists/loongarch64/linux b/config/rootfiles/core/206/filelists/loongarch64/linux
new file mode 120000
index 000000000..31b2bcffe
--- /dev/null
+++ b/config/rootfiles/core/206/filelists/loongarch64/linux
@@ -0,0 +1 @@
+../../../../common/loongarch64/linux
\ No newline at end of file
diff --git a/config/rootfiles/core/206/filelists/riscv64/linux b/config/rootfiles/core/206/filelists/riscv64/linux
new file mode 120000
index 000000000..c8e8350ca
--- /dev/null
+++ b/config/rootfiles/core/206/filelists/riscv64/linux
@@ -0,0 +1 @@
+../../../../common/riscv64/linux
\ No newline at end of file
diff --git a/config/rootfiles/core/206/filelists/x86_64/linux b/config/rootfiles/core/206/filelists/x86_64/linux
new file mode 120000
index 000000000..0615b5b9a
--- /dev/null
+++ b/config/rootfiles/core/206/filelists/x86_64/linux
@@ -0,0 +1 @@
+../../../../common/x86_64/linux
\ No newline at end of file
diff --git a/config/rootfiles/core/206/update.sh b/config/rootfiles/core/206/update.sh
index 454bcf620..8a5515d44 100644
--- a/config/rootfiles/core/206/update.sh
+++ b/config/rootfiles/core/206/update.sh
@@ -26,13 +26,65 @@
core=206
+exit_with_error() {
+ # Set last succesfull installed core.
+ echo $(($core-1)) > /opt/pakfire/db/core/mine
+ # force fsck at next boot, this may fix free space on xfs
+ touch /forcefsck
+ # don't start pakfire again at error
+ killall -KILL pak_update
+ /usr/bin/logger -p syslog.emerg -t ipfire \
+ "core-update-${core}: $1"
+ exit $2
+}
+
# Remove old core updates from pakfire cache to save space...
for (( i=1; i<=$core; i++ )); do
rm -f /var/cache/pakfire/core-upgrade-*-$i.ipfire
done
+KVER="@KERNEL_RELEASE@"
+
+# Backup uEnv.txt if exist
+if [ -e /boot/uEnv.txt ]; then
+ cp -vf /boot/uEnv.txt /boot/uEnv.txt.org
+fi
+
+# Do some sanity checks prior to the kernel update
+case $(uname -r) in
+ *-ipfire*)
+ # Ok.
+ ;;
+ *)
+ exit_with_error "ERROR cannot update. No IPFire Kernel." 1
+ ;;
+esac
+
+# Check diskspace on root and size of boot
+ROOTSPACE=$( df / -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1 )
+if [ $ROOTSPACE -lt 200000 ]; then
+ exit_with_error "ERROR cannot update because not enough free space on root." 2
+fi
+BOOTSIZE=$( df /boot -Pk | sed "s| * | |g" | cut -d" " -f2 | tail -n 1 )
+if [ $BOOTSIZE -lt 100000 ]; then
+ exit_with_error "ERROR cannot update. BOOT partition is to small." 3
+fi
+
# Stop services
+# Remove the old kernel
+rm -rvf \
+ /boot/System.map-* \
+ /boot/config-* \
+ /boot/ipfirerd-* \
+ /boot/initramfs-* \
+ /boot/vmlinuz-* \
+ /boot/uImage-* \
+ /boot/zImage-* \
+ /boot/uInit-* \
+ /boot/dtb-* \
+ /lib/modules
+
# Remove files
rm -rfv \
/etc/strongswan.d/charon/gcrypt.conf \
@@ -117,7 +169,6 @@ fi
# Build initial ramdisks
dracut --regenerate-all --force
-KVER="@KERNEL_RELEASE@"
case "$(uname -m)" in
aarch64)
mkimage -A arm64 -T ramdisk -C lzma -d /boot/initramfs-${KVER}.img /boot/uInit-${KVER}
@@ -128,6 +179,16 @@ esac
# This update needs a reboot...
touch /var/run/need_reboot
+# Update kernel version in uEnv.txt
+if [ -e /boot/uEnv.txt ]; then
+ sed -i -e "s/KVER=.*/KVER=${KVER}/g" /boot/uEnv.txt
+fi
+
+# Call user update script (needed for some ARM boards)
+if [ -e /boot/pakfire-kernel-update ]; then
+ /boot/pakfire-kernel-update ${KVER}
+fi
+
# Finish
/etc/init.d/fireinfo start
sendprofile
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2026-11-19 10:15 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=4jVZ8y2bpFz2xVM@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