Linked by moondevil on Wed 11th Jul 2012 22:49 UTC
Permalink for comment 526526
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2008-12-10
http://ahatfullofsky.comuv.com/English/Programs/SMS/SMS.html
This ist the link to a small tool, telling you in which mode your kernel booted.
I never quite understood how it works that I have a 64bit-EFI with a 64bit-kernel, that starts up in 32bit-mode and runs 32bit and 64bit applications alongside - as this app indicatates my 2011-MBP does with Snow Leopard.
You can use this tool also to force your kernel into 64bit mode on next boot - which I never tried.
I thought this strange mixture of 64bit/32bit-kernel mode was what allowed Snow Leopard to run 32bit drivers also.
First of all - how can a piece of kernel be 64bit and 32bit at the same time, if it's not just a 2-architecture binary file and bootmode decides which of the two ressources in this fork is loaded.
And if '32bit-mode' means that kernel operates in 32bit - how can it execude 64bit applications and kernelextensions?
I really don't get it.
And what happend in Mountain Lion, if Apple really has such an elaborate way of mixing 32bit and 64bit?