From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core122, updated. c645bac12b753d9b8d95d61cff9b828ccbe3d391
Date: Sun, 08 Jul 2018 18:05:14 +0100 [thread overview]
Message-ID: <20180708170515.25AD21081BD8@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1638 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, core122 has been updated
via c645bac12b753d9b8d95d61cff9b828ccbe3d391 (commit)
from 3694296e56ad3e3698f3c0a68d36226eb917794a (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 c645bac12b753d9b8d95d61cff9b828ccbe3d391
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Jul 8 18:11:58 2018 +0200
core121: add diskspace check for /boot
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/121/update.sh | 7 +++++++
1 file changed, 7 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/121/update.sh b/config/rootfiles/core/121/update.sh
index 18019c1d7..bee8fd24f 100644
--- a/config/rootfiles/core/121/update.sh
+++ b/config/rootfiles/core/121/update.sh
@@ -59,6 +59,13 @@ if [ $ROOTSPACE -lt 220000 ]; then
exit 2
fi
+BOOTSPACE=`df /boot -Pk | sed "s| * | |g" | cut -d" " -f4 | tail -n 1`
+
+if [ $BOOTSPACE -lt 22000 ]; then
+ exit_with_error "ERROR cannot update because not enough free space on /boot." 3
+ exit 3
+fi
+
# Stop services
# Extract files
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-07-08 17:05 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=20180708170515.25AD21081BD8@git01.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