From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. be6cb8eab784474cfb0dcf737aac3ba2d3e59775
Date: Sun, 27 Jan 2013 11:35:27 +0100 [thread overview]
Message-ID: <20130127103528.043F920131@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1458 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 be6cb8eab784474cfb0dcf737aac3ba2d3e59775 (commit)
from eb915ddd55640ae2856458f86f9013fc8a95fe4c (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 be6cb8eab784474cfb0dcf737aac3ba2d3e59775
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date: Sun Jan 27 11:33:50 2013 +0100
core66: create device.map before grub install.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/66/update.sh | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/66/update.sh b/config/rootfiles/core/66/update.sh
index c76f3c7..ac4e3ac 100644
--- a/config/rootfiles/core/66/update.sh
+++ b/config/rootfiles/core/66/update.sh
@@ -287,6 +287,7 @@ case $(uname -m) in
#
# ReInstall grub
#
+ echo "(hd0) ${ROOT::`expr length $ROOT`-1}" > /boot/grub/device.map
grub-install --no-floppy ${ROOT::`expr length $ROOT`-1}
;;
esac
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-01-27 10:35 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=20130127103528.043F920131@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