|
|
|
|
|
by binarycrusader
4764 days ago
|
|
I'll clarify then: I believe Solaris has had the first part (ability to boot into a 32-bit or 64-bit kernel) since 1998. That's well before Apple even provided a 64-bit kernel or ever shipped an OS X release. Solaris has long had a single, unified architecture for 32-bit and 64-bit and until recently delivered both a 32-bit and 64-bit kernel on a single disk. That's why on Solaris you'll generally find the 32-bit libraries installed in 'usr/lib' and the 64-bit under 'usr/lib/64'. The only exception is for processor architectures (SPARC/x86) where it made less sense. But even then, Solaris 11 has multi-variant packages, so a single package provides support for both x86 and SPARC. It's true that (as far as I'm aware) Solaris never supported the 64-bit application on 32-bit kernel hack that OS X did (which comes with significant performance tradeoffs). So at most, Apple can claim that achievement, but they can't claim to be the first to provide a single install image supporting 32-bit and 64-bit. |
|
It also is true that (as far as I am aware) Solaris never had lots of 32-bit customers running applications and drivers that neither Sun nor those customers could recompile for 64-bits.
That and the fact that some of those customers desperately wanted/needed to access more than 4 GB of memory forced Apple's hands. They had to keep the kernel 32 bits to support older drivers, and had to provide a user space that supported more than 32 bits.
The world is so much simpler if you can force al your customers to recompile their applications. If you doubt that, ask Microsoft or Intel why Itanium didn't even get a chance.