From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH v2] Core Update 169: Delete unused initrd on 32-bit ARM to save space in /boot
Date: Thu, 07 Jul 2022 13:58:05 +0000 [thread overview]
Message-ID: <20220707135805.1597569-1-peter.mueller@ipfire.org> (raw)
In-Reply-To: <AAA16072-DA1E-4841-A31E-B560CE7BFB12@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On 64-bit ARM, this is still needed for booting. Since the initrds were
already shipped with the updater, there is no need to regenerate them
locally again.
https://community.ipfire.org/t/again-with-the-file-system-full-core-169/8186
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
config/rootfiles/core/169/update.sh | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/config/rootfiles/core/169/update.sh b/config/rootfiles/core/169/update.sh
index 3902e2d45..dc7a2a18a 100644
--- a/config/rootfiles/core/169/update.sh
+++ b/config/rootfiles/core/169/update.sh
@@ -150,6 +150,13 @@ ldconfig
# Apply sysctl changes
/etc/init.d/sysctl start
+# Delete unused initrd on 32-bit ARM to save space in /boot
+case "$(uname -m)" in
+ armv*)
+ rm /boot/initramfs-${KVER}-ipfire.img
+ ;;
+esac
+
# Start services
telinit u
/etc/init.d/firewall restart
--
2.30.2
next prev parent reply other threads:[~2022-07-07 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 5:46 [PATCH] Core Update 169: Regenerate initrds and save space on ARM Peter Müller
2022-07-07 5:48 ` Peter Müller
2022-07-07 13:19 ` Michael Tremer
2022-07-07 13:30 ` Peter Müller
2022-07-07 13:43 ` Michael Tremer
2022-07-07 13:49 ` Peter Müller
2022-07-07 13:53 ` Michael Tremer
2022-07-07 13:54 ` Peter Müller
2022-07-07 13:54 ` Michael Tremer
2022-07-07 13:58 ` Peter Müller [this message]
2022-07-07 14:02 ` [PATCH v2] Core Update 169: Delete unused initrd on 32-bit ARM to save space in /boot Michael Tremer
2022-07-07 14:05 ` Peter Müller
2022-07-07 14:11 ` Michael Tremer
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=20220707135805.1597569-1-peter.mueller@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@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