There's not going to be a major difference between the two. Or do you think that "it has to be faster because it has more bits!"?
Read post #214.
I don't think memory-randomization is dependant on the bitness of the system....
Google Charlie Miller
There's not going to be a major difference between the two. Or do you think that "it has to be faster because it has more bits!"?
I don't think memory-randomization is dependant on the bitness of the system....
You're right. I believe 32-bit Vista has a decent memory randomization implementation. Leopard's implementation wasn't so good since I think only a few libraries were made compatible (random) and not the whole kernel. I'm guessing the 32-bit kernel in Snow Leopard will now have memory randomization fully implemented. Still, a 64-bit kernel with memory randomization should be more effective because of the much larger address space to stick things. Admittedly, it's more of a theoretical advantage at this point, but being security, if it does become a practical advantage, it'll be a big problem. Which of course could be avoided but giving all 64-bit capable Macs access to the 64-bit kernel by writing the necessary drivers and EFI firmware. I guess it's a matter of whether safe enough for now is a compelling argument.I don't think memory-randomization is dependant on the bitness of the system....
I really wonder why everyone is so quick to be an Apple apologist. It's always the same excuse "end users wont notice" "it's not a big deal".
People pay a huge premium on the MacPro. You know how hard it is to justify a 3k desktop PC? and they can't even put enough effort to support 64bit?
On my macpro1,1 I have ran XP64, vista64, FreeBSD/amd64, Solaris (SXCE & OpenSolaris) in 64bit mode, -ALL- of these work. Yet the company I gave such a large premium to can't be bothered to support me a couple years later and you guys want to defend that? Somehow buying a 3k workstation with the expectation of a very basic level of support is "entitlement"? Come on... I'm not really that insulted at Apple because this is what I expect from them, but it's really annoying to listen to you apologists. There's really no excuse.
Can we drop the 64 bit issues for a couple of pages and at least get some first hand impressions?
geez
That's how Apple make money, they sell you the computer and two years later you are out of support, what they tell you to do? buy the latest computer hardware so the latest OS X can be supported. That's their business model.
On my macpro1,1 I have ran XP64, vista64, FreeBSD/amd64, Solaris (SXCE & OpenSolaris) in 64bit mode, -ALL- of these work.
The only think I'd like to know is, wether it really is the GM now. Because I won't install a beta on my main drive...
lol its kinda annoying people asking the same question "oh i want to be able to do an erase & install & i want a clean install". of course you will, its going to work like it has done for every OS X upgrade disk
stages
1. Pop in the install DVD & press C
2. wait for it to load up
3. Once loaded the disk will scan for a Leopard install, once it has found it on the hard disk you will be able to continue
4. After that you can either chose an upgrade, archive or erase and install,
not hard really is it LOL
Looks like the version which has been leeked on torrent sites is fake..
Check out the release notes (10.6_snow_leopard_client_10a432_seed_note.rtf):
I've been using the beta build as my main OS since 10A380. It's probably more stable than Leopard at the current build it's at, seeing as it's being released in less than 1 month.
As for OpenCL, as I'm sure you are aware Leopard supports up to 2.1 and quite a few of the OpenCL 3.x features, though it doesn't give full support. However, Linux and Microsoft offer that 3.x support for free, so I'd expect that too from Apple.
Another Example:
Mac OSX 10.5 doesn't support NUMA: http://en.wikipedia.org/wiki/Non-Uniform_Memory_Access
Hope 10.6 does, because Nehalm looses till 25% of performance in 10.5 (there are benches in c't who compared it with other operating systems).
Somebody should start a 64-bit compatibility thread for the pissed off people .. Not me, I'm lazy. But somebody should ..
It's not on the dev site, its on the ADC site.
Agreed... this whole 64bit is going out of hand.