Hello Every-one

I am presently trying to set up system Imager for  IBM blade servers. In the
beginning I got the error, cant find your kernel.I tried to use the patch
given in the link below which seems like a similar problem

http://www.mail-archive.com/sisuite-users@lists.sourceforge.net/msg04858.html

sudo patch UseYourOwnKernel.pm UseYourOwnKernel.pm.patch
However the patch doesnt seem to "stick"

patching file UseYourOwnKernel.pm
Hunk #1 FAILED at 460.
Hunk #2 FAILED at 469.
2 out of 2 hunks FAILED -- saving rejects to file UseYourOwnKernel.pm.rej

If I specify the the kernel from  /boot as shown below.
 si_prepareclient --server SERVER_IP --kernel
/boot/vmlinuz-2.6.27.7-9-default

It gives me the message
WARNING: unable to detect kernel release of
"/boot/vmlinuz-2.6.27.7-9-default"!
WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by
systemconfigurator)

If I try to retrieve this incomplete image, it complains:
rsync: failed to connect to 129.10.121.230: Connection timed out (110)
rsync error: error in socket IO (code 10) at clientserver.c(122)
[receiver=3.0.4]

I am new to System Imager, any help will be really appreciated in the
patching process. I am not sure if this is related to the sync or to the
kernel not being seen. I am using SystemImager 4.0.2-1

Thank You Very Much.

-- 
Perhaad Mistry
Graduate Student,
ECE Dept, NEU, Boston-MA
email: pmis...@ece.neu.edu
847-828-5475
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to