|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Tweak List: Blue BoxThe Blue Box is Apple's current mechanism for ensuring backwards compatibility with the current MacOS on MacOS X Server. It is a much different animal than the YellowBox! When you turn your Mac on, the MacOS starts to load, and eventually controls all hardware, software, and low-level functions that are required for the system to properly function. The OS itself interfaces directly with the hardware. However, the Blue Box functions much differently. As opposed to interfacing directly with the hardware, the Blue Box interfaces with the Mach kernel. Because the abstraction from hardware is transparent, the Blue Box has no reason to believe that it is not running directly on the hardware and functions as if it were. Another way to think about it is to say that the Blue Box is a MacOS virtual machine in quite the same vein as a Java VM, or Virtual PC. The only difference in that analogy is that the Blue Box does not need to emulate the processor, since both MacOS X Server and the MacOS run on PowerPC hardware. Current reports show that almost all MacOS applications will run unfettered in the Blue Box. The only applications which will have trouble are ones which require direct interfaces with the hardware, such as video drivers and ADB dongles. Such issues are currently being worked out by engineers at Apple. MacOS X Server 1.0 will ship with a Blue Box using MacOS 8.5.1. In time, the Blue Box will function much differently. Possible changes are the ability to directly interface with hardware, and a transparent Blue Box. |
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
All content - ©1998-2009 - Mark J. Hershenson |
|
|
||
|
|
|
|
|
The MacOS Xclave is hosted by green-ant.com.
