Sun Microsystems Inc is canning the proprietary kernel underlying its JavaOS network computer operating system and will migrate the services to run atop the ClassiX embedded microkernel from its Chorus Systemes SA acquisition. As we previously indicated (CI No 3,242), all of Sun’s embedded software products are going to be implemented on ClassiX over time, […]
Sun Microsystems Inc is canning the proprietary kernel underlying its JavaOS network computer operating system and will migrate the services to run atop the ClassiX embedded microkernel from its Chorus Systemes SA acquisition. As we previously indicated (CI No 3,242), all of Sun’s embedded software products are going to be implemented on ClassiX over time, including its Embedded Java and Personal Java subsets of the language, indicating just how important the Paris-based concern is to the company’s attempt to foster a market for Java-based devices. Sun yesterday unveiled version 1.1 of its JavaOS for network computers, a piece of software long overdue just like the company’s ‘Krups’ JavaStation NCs on which it is supposed to run. SunSoft’s embedded systems group, which inherited the mangled JavaOS project from JavaSoft, says version 1.1 now includes everything required to support production environment NCs from multiple vendors, including JDK 1.1, JavaBeans, internationalization, serial port, PPP and dialer interfaces, JIT compiler, SSL and the ability to choose a different startup location for their NC. It’s up on Sparc and Intel with StrongARM and PowerPC support due. IBM Corp has been helping Sun develop JavaOS; Bob Dies, general manager of its NC division told us yesterday he thought it will be at least six months before JavaOS is robust and stable enough to be deployed at IBM production sites which have many more support requirements. Sun says JavaOS will be migrated to ClassiX in two releases over the next 12 months. Support for JDK 1.2 and the HotSpot JIT compiler will be added plus a JDI Java developer API for writing device drivers to. Chorus’ microkernel is already supported on Intel, Motorola 680×0, PowerPC, Sparc, microSparc II and ARM processors. It’s expected to go up on Sun’s forthcoming Java silicon technologies including microJava and ultraJava.
Sun, which admits there’s likely to be some confusion as it transitions to the Chorus technologies, will market Chorus’ Java- based offering, Chorus/Jazz, as JavaOS for Appliances, such as web phones, set-tops and handhelds which have user interfaces. Sun will implement the Personal Java subset of the JDK on Chorus/Jazz next year, which includes support for HotJava and JavaViews interface technologies. JavaOS for Network Computers and Appliances looks set to share the same kernel going forward as Chorus/Jazz is an implementation of JavaOS 1.0 implemented on top of ClassiX connecting Java and Chorus threads in such a way that Java applets can utilize Chorus’ real-time and embedded system services. It also includes Chorus’ Cool object request broker. The next two versions of Chorus/Jazz have already been codenamed BeBop and Triple Z. Next year Sun will also offer an implementation of the smallest Java footprint, Embedded Java, up on ClassiX as JavaOS for Embedded and designed for controllers for the automotive, manufacturing and avionics industries. Sun says it will continue to evolve the native ClassiX as ChorusOS, which counts Lucent Technologies Inc amongst its customers. Sun’s Diba appliance design unit will provide applications that can be layered on top of the JavaOS products.