Been using SI since 3.2......been very happy with it. Gotten a bit creative
with the master scripts for helping to automate and do some custom changes
to the golden client image when the hardware has change but the golden client
image is still usable.
Starting to build systems running 64-bit..specifically SLES 11 SP1 64-bit
si_prepareclient files to run properly becasuse systemconfigurator is unable to
determine the kernel.
I checked the mailing list and I found something that had written a patch for
the UseYourOwnKernel.pm that I applied. Still doesn't work.
What information do I need to provide to help build against SLES 11 SP1 64-bit??
Here are the RPM's that are installed on the golden-client:
systemconfigurator-2.2.11-1
systemimager-common-4.1.6-1
systemimager-i386initrd_template-4.1.6-1
systemimager-x86_64initrd_template-4.1.6-1
systemimager-client-4.1.6-1
uname -a returns the following:
Linux newserverbuild 2.6.32.36-0.5-default #1 SMP 2011-04-14 10:12:31 +0200
x86_64 x86_64 x86_64 GNU/Linux
Here is the patch that I found on the message board and tried to use:
*** /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm.orig Mon Mar
24 07:11:44 2008
--- /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm.new Fri May
13 10:28:15 2011
***************
*** 365,370 ****
--- 365,376 ----
#
# eliminate message
if( $filename =~ m/^message/ ) { return undef; }
+ #
+ # eliminate symbol files
+ if( $filename =~ m/^sym/ ) { return undef; }
+ #
+ # eliminate backup_mbr
+ if( $filename =~ m/^backup_mbr/ ) { return undef; }
#
# Get output from "file" for elimination by identification tests
***************
*** 460,478 ****
# 2.4.19-mantis-2002.11.20 (root@mantis) #6 Tue Nov 19
15:15:43 CST 2002
# 2.6.7-1-686 ([email protected]) #1 Thu
Jul 8 05:36:53 EDT 2004
# 2.6.22.5-31-default (geeko@buildhost) #1 SMP
2007/09/21 22:29:00 UTC
#
my $regex =
# | kernel version + build machine
# `---------------------------------------
! '(2\.[46]\.\d[^\/]*?) \(.*@.*\) [#]\d+.*' .
#
# | build date
# `---------------------------------------
! '(\w{3} \w{3} \d{1,2}|\d{4}\/\d{2}\/\d{2}) '.
#
# | build time
# `---------------------------------------
! '\d{2}:\d{2}:\d{2} \w{3,4}( \d{4})?';
while(<IN>) {
# extract the `uname -r` string from the kernel file
if(m/$regex/o) {
--- 466,485 ----
# 2.4.19-mantis-2002.11.20 (root@mantis) #6 Tue Nov 19
15:15:43 CST 2002
# 2.6.7-1-686 ([email protected]) #1 Thu
Jul 8 05:36:53 EDT 2004
# 2.6.22.5-31-default (geeko@buildhost) #1 SMP
2007/09/21 22:29:00 UTC
+ # 2.6.27.29-0.1-default (geeko@buildhost) #1 SMP
2009-08-15 17:53:59 +0200
#
my $regex =
# | kernel version + build machine
# `---------------------------------------
! '(2[.][46][.][[:digit:]][^\/]*?) [(]...@.*[)]
[#][[:digit:]]+.*' .
#
# | build date
# `---------------------------------------
! '(\w{3} \w{3}
[[:digit:]]{1,2}|[[:digit:]]{4}[/-][[:digit:]]{2}[/-][[:digit:]]{2}) '.
#
# | build time
# `---------------------------------------
! '[[:digit:]]{2}:[[:digit:]]{2}:[[:digit:]]{2}
(\w{3,4}|[+-][[:digit:]]{4})?( [[:digit:]]{4})?';
while(<IN>) {
# extract the `uname -r` string from the kernel file
if(m/$regex/o) {
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
