Hi. > In SystemImager 4.1.x the hardware.lst is always re-generated at end of > imaging, so this problem should be already fixed in recent versions > (i.e. 4.1.6).
I guess, time to update to latest unstable :). > It's used by systemconfigurator to know which modules must be included > in the initrd and to create opportune kernel module aliases (see man > systemconfigurator). I don't see any issues with the new server - but perhaps I should re-image and redeploy it with the latest unstable release? > You must not hard-code kernel version in post-install script. Well, I can't erase or run mkinitrd otherwise. > CONFIGRD=YES must work, if not this means you've found a bug in > systemconfigurator, but to fix it we need the full systemconfigurator > output as I've requested in a previous email. Otherwise it's too > diffucult to understand where systemconfigurator failed. > > For this I would suggest to enable monitoring (see > http://wiki.systemimager.org/index.php/Monitoring) and copy & paste > virtual console output. I have it enabled. What exactly you like me to post? I checked but couldn't find any reference in the output to CONFIGRD=YES in the output. Thanks again, Stas. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
