site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Mar 1, 2007, at 12:05 PM, darwin-dev-request@lists.apple.com wrote: I have to ask, why bother posting here in that case? = Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Well, I took a different road. I don't want to rely on system_profiler for additional reasons (one of them is the fact that the -xml SPHardwareDataType does not work on Mac OS X 10.2, another one could be not to use a tank (slow and too much information) to kill an ant). For PowerPC, I still use the old code if the OS is too old. For i386, I use sysctl with the machdep.cpu branch and another one to get the family and to know whether it's a multi-core or mono-core CPUs. So in the name of supporting 10.2, you took a path which will not work on future versions of the OS instead, despite advice from several Apple folks? As for killing things with a tank; I fear your sense of proportion is a bit mis-calibrated. Executing a tool and capturing its output for a one-off operation is a relatively cheap thing to do; the system expects (even encourages) tools to be used in this fashion. This email sent to site_archiver@lists.apple.com