Hi there everyone At 10:51 AM +0100 2/13/03, [EMAIL PROTECTED] wrote: >You will find an option called CPU_DISABLE_CMPXCHG I read that one and didn't read (my newbie fault) that it was so closely related to VMWare. >I realize you then have the problem of how to compile the new >kernel when it takes so long to do anything with the standard >GENERIC kernel. Perhaps it would go better if you booted up >in >single-user mode, and then compiled and installed the new >kernel. That's a good idea, even if I'm not sure single user would make a difference. I imagine that the same machine code is being called when doing a make depend, make, cc & stuff. My short term method has been (all day long) to reboot the guest os from time to time (when things get slow, but before things get *BLOCKED*) and relaunch the build procedure. However, this is quite difficult and cumbersome to achieve. I, for sure, would have preferred a sysctl option if I understand that it is far too low level for this. In the end, compiling a new kernel on a non-VMWare host sounds interesting but might sound "bizarre" when using the VMWare-do- not-need-new-hardware-to-try-new-OS approach. My new kernel build is not over right now and I'll probably find it blocked tomorrow morning because of no reboot :( Thanks for your help anyway, and sorry for the RTFM glitch ;-) Yvon
Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
