From: "Brian Dolbec" <brian.dolbec@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:3.0 commit in: targets/support/
Date: Wed, 19 Feb 2014 17:47:48 +0000 (UTC) [thread overview]
Message-ID: <1392831122.59e71a64d4e3a75e00e10e477b251b6cbd831d81.dol-sen@gentoo> (raw)
commit: 59e71a64d4e3a75e00e10e477b251b6cbd831d81
Author: Guy Martin <gmsoft <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 5 10:40:00 2014 +0000
Commit: Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Wed Feb 19 17:32:02 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=59e71a64
Rename System.map in a way that it won't be matched if multiple kernel are used.
The System.map-version file gets renamed to System.map-${kname}.
This causes some trouble when you have more than one kernel as the file from
the previous kernel will be matched as well. To prevent that, I change
the naming slightly.
---
targets/support/functions.sh | 4 ++--
targets/support/netboot2-final.sh | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/targets/support/functions.sh b/targets/support/functions.sh
index 224833f..7face15 100755
--- a/targets/support/functions.sh
+++ b/targets/support/functions.sh
@@ -106,9 +106,9 @@ extract_kernels() {
mv ${1}/initramfs-* ${1}/${x}.igz
fi
- if [ -e ${1}/System.map-* ];
+ if [ -e ${1}/System.map-* ]
then
- mv ${1}/System.map-* ${1}/System.map-${x}
+ mv ${1}/System.map-* ${1}/System-${x}.map
fi
done
}
diff --git a/targets/support/netboot2-final.sh b/targets/support/netboot2-final.sh
index 55835d2..732a1f1 100755
--- a/targets/support/netboot2-final.sh
+++ b/targets/support/netboot2-final.sh
@@ -14,7 +14,7 @@ mkdir ${clst_target_path}kernels/misc
for x in ${clst_boot_kernel}; do
mv ${clst_target_path}boot/${x} ${clst_target_path}kernels
mv ${clst_target_path}boot/${x}.igz ${clst_target_path}kernels/misc
- mv ${clst_target_path}boot/System.map* ${clst_target_path}kernels/misc/System.map-${x}
+ mv ${clst_target_path}boot/System-${x}.map ${clst_target_path}kernels/misc
done
rmdir ${clst_target_path}boot
next reply other threads:[~2014-02-19 17:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 17:47 Brian Dolbec [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-28 11:41 [gentoo-commits] proj/catalyst:3.0 commit in: targets/support/ Raúl Porcel
2014-10-26 12:27 Raúl Porcel
2014-04-20 13:41 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-04-18 16:52 Brian Dolbec
2014-03-03 16:07 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2014-02-19 17:47 Brian Dolbec
2013-11-21 9:06 Brian Dolbec
2013-11-21 9:06 Brian Dolbec
2013-11-21 9:06 Brian Dolbec
2013-11-21 9:06 Brian Dolbec
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=1392831122.59e71a64d4e3a75e00e10e477b251b6cbd831d81.dol-sen@gentoo \
--to=brian.dolbec@gmail.com \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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