From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, core56, updated. 2d57443beb7b153af4335c2b6dd5f91b3edcfd95
Date: Sat, 28 Jan 2012 00:39:39 +0100 [thread overview]
Message-ID: <20120127233939.49F3320164@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1520 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, core56 has been updated
via 2d57443beb7b153af4335c2b6dd5f91b3edcfd95 (commit)
from 5db3741f3721d32fe4eacac0c0bacf981fbfedc8 (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 2d57443beb7b153af4335c2b6dd5f91b3edcfd95
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Jan 27 09:22:15 2012 +0100
fs-resize: answer yes at fsck to continue at last mount in future.
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/init.d/fsresize | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Difference in files:
diff --git a/src/initscripts/init.d/fsresize b/src/initscripts/init.d/fsresize
index 0afe779..8913eb9 100644
--- a/src/initscripts/init.d/fsresize
+++ b/src/initscripts/init.d/fsresize
@@ -26,7 +26,7 @@ case "${1}" in
ROOT=`mount | grep -m1 " / " | cut -d" " -f1`;
DRV=${ROOT::`expr length $ROOT`-1}
boot_mesg " * check filesystem on ${DRV}4 before resize ..."
- fsck -f ${DRV}4
+ fsck -f -y ${DRV}4
boot_mesg " * resize ${DRV}4 ..."
resize2fs -p ${DRV}4
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-01-27 23:39 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=20120127233939.49F3320164@argus.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