Hi Bernard,

in an OSCAR image created the conventional way the initrd is usually
generated in the %post scriptlet of the RPM. This happens on the 
master node at image creation time, inside a chroot on possibly completely
different hardware. Therefore the existing initrd can be completely bogus.
Re-generating it at install time gives the user or some API scripts the
chance to adapt /etc/systemconfig/systemconfig.conf and /etc/modprobe.conf
inside the image and get a more appropriate result.

For OSCAR I think it is better to try to fix the generation of the initrd,
i.e. work on getting modprobe.conf and /etc/sysconfig/kernel right. By using
the initrd made at RPM install time in the image you might solve some very
simple and symmetric case, but cut the path to get the complex cluster
installs with different master hardware right.

Regards,
Erich

On Friday 21 September 2007 02:40, Bernard Li wrote:
> The systemconfig.conf generated by systeminstaller for the image does
> not contain the INITRD line.
> 
> This causes systemconfigurator to re-generate the ramdisk each time it
> is run with --configrd (even though the ramdisk file already exists).
> 
> Would people normally want the ramdisk to be re-generated even though
> it exists?  I guess the only time you would want to re-generate it is
> if you make some modifications to your hardware and modify
> /etc/modprobe.conf, but to me it sounds like you should only overwrite
> it when --force is specified.
> 
> We can "fix" this in two ways:
> 
> 1) Modify systeminstaller so it outputs INITRD line in systemconfig.conf
> 2) Modify systemconfigurator so it doesn't overwrite an existing ramdisk
> 
> What are people's thoughts on this?
> 
> Cheers,
> 
> Bernard

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sisuite-devel mailing list
sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel

Reply via email to