Re: [sisuite-users] RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support

[Bas v. d. V. <ba...@sa...>]

On 17 dec. 2012, at 10:16, LAHAYE Olivier <oli...@ce...>
 wrote:

> 
> This means that your disk is not recognized.
> 
> Did you use my install scripts (especially the pre-install).
> http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2
> 
> It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem).
> 
> if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided  default kernel), then you'll need to use your own kernel for the moment.
> 
> I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel.
> This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old).
> 
> In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)).
> 

Oliver,

 That is why SALI is around.  It is only a kernel/initrd with up to date utilities that does a better job in detecting which hardware. The only problem is that we do not have an up to date systemconfigurator of other tools that generate the auto install scripts, Brian also posted http://download.systemimager.org/pub/ssm/README. 


Jing could replace the default system imager kernel/initrd with the SALI one.

regards

-- 
Bas van der Vlies           
mail: ba...@sa...     
SARA - Academic Computing Services , Amsterdam, The Netherlands