On 19 Oct 99, at 7:58, Gilbert Carl Herschberger II wrote: > The mission of the JOSystem is to put distance between the > platform-dependent implementation of a JOSBox and the platform-independent > JVM. Actually, as I understand it JOSystem is the "OS layer" of abstraction which presents a common JOS interface to applications. So every implementation of the JOSystem will look identical to applications using it. So it includes a JVM and supporting libraries (java standard and jos standard) so that any JOS program will execute on top of that layer without modifications. So its not a layer between the JOSBox and the JVM. It's actually whatever combination of JOSBox, JVM, and libraries needed to create a JOSystem environment. Theoretically, if you had a native java cpu, JOSystem would just be the libraries and boot code (and any task switching and memory management not automatically handled by the java chip). The JOSBox becomes almost purely hardware. On more traditional cpu's, its a microkernel, the jvm, and the libraries. Of course, I could be wrong so I'd like to hear others opinions. -iain _______________________________________________ Kernel maillist - [EMAIL PROTECTED] http://jos.org/mailman/listinfo/kernel
