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
