I went ahead and built under rh9. Will test today or tomorrow and upload if all goes well. However, I have several questions, and I really, really need an answer to the first question.
Q: In a past thread Brian said: "Last night I discovered why I've been unable to boot and test on my uni-processor test machine for the past few weeks -- CONFIG_SMP=y got into the linux.i386.config somehow." SMP is still turned on in the current 3.2.2 tarball's linux.i386.config. Should I turn it off? Q: If the answer above is yes... Does that mean we need to go to 3.2.3? Q: The current spec file has a bunch of 'migration' code in the pre/post scripts. I'd like to rip that out and put it into the documentation instead. The reason is that Fedora has a stated policy against RPMs that do terminal I/O. I'd like to conform to that. I'd also like to tweak it to respect any relocation information in systemimager.conf. Objections? Q: The current spec file builds a package named systemimager-i386boot-standard. The kernel in that package, however, is compiled for i486 (i586 in 3.2.0). We've had at least one bug report related to that. Should I tweak the spec file to change the name to reflect the kernel architecture rather than the build machine's architecture? I'm thinking we may need this RSN for native 64-bit support. Is that worthy of a minor revision increment? Q: Do we care about i386 any more? Q: Do we want to have more than one kernel arch boot image (e.g. 486,586,686)? This would probably require tweaks to the make rules. ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
