Bugs item #511575, was opened at 2002-01-31 23:36 Message generated for change (Comment added) made by brechin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=511575&group_id=9368
Category: Documentation Group: Future >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Thomas Naughton (naughtont) Assigned to: Thomas Naughton (naughtont) Summary: UP/SMP kernel boot problem workaround Initial Comment: Discussion seems to have settled that we'll use kernel-SMP by default to get 90+% of the UP/SMP machines. For those UP machines that have problems booting with the kernel-SMP add the related verbage and a suitable fix/workaround. (see also: BUG#510522) ---------------------------------------------------------------------- >Comment By: Jason Brechin (brechin) Date: 2003-07-16 09:56 Message: Logged In: YES user_id=274641 Well... we still default to the SMP kernel. However, with kernel_picker, I think this issue is pretty well resolved. ---------------------------------------------------------------------- Comment By: Sean Dague (sdague) Date: 2002-07-09 17:04 Message: Logged In: YES user_id=21949 Jason et al. I agree that we should do much better here. The issue is that defaulting to the server is often as wrong as defaulting to SMP. Many people use much beefer servers than clients (which we found when people had issues with i686 images being built on their servers for i486 clients.) The problem is that you can't detect if an machine is SMP or not without running an SMP kernel on it. (If you run a UP kernel you will ALWAYS see only 1 processor.) It was assumed up to this point that the Red Hat SMP kernel worked on UP machines, which is becoming less and less true. The right solution to this is probably to add SMP capability to the SIS install kernel. Then we could know during installation what was the right thing to do. We are beyond the timeframe to fix this for 1.3 in code. We should revisit for 1.4. ---------------------------------------------------------------------- Comment By: Jason Brechin (brechin) Date: 2002-07-09 16:39 Message: Logged In: YES user_id=274641 The solution is documented, but I think we need to handle the issue more intelligently than "screw the people with UP machines, if the SMP kernel doesn't work then make them do the work". We should do some sort of intelligent default to whatever the server runs, or make it a selection, or make another rpmlist, or detect the actual processor count on the clients at some point (before the SMP kernel is installed). Too many people have had problems with this to ignore it. ---------------------------------------------------------------------- Comment By: Jeff Squyres (jsquyres) Date: 2002-04-06 13:17 Message: Logged In: YES user_id=11722 I believe that this issue has been resolved... right? Can we close this bug? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109368&aid=511575&group_id=9368 ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
