Welcome to JNode.org, the website of the Java New Operating System Design Effort.

JNode is a simple to use & install Java operating system for personal use.
It runs on modern devices.

Any java application will run on it, fast & secure!

JNode is open source and uses the LGPL license.

Latest release:
JNode 0.2.8
Hardware requirements:
Pentium class CPU
512M RAM

see details


I just ran across the PJA Toolkit on eTeks,


Looks like they may have implemented some graphics stuff that JNode needs, bresenham, fonts, etc. They say 100% pure java and GPL.

Sam Reid

A rumanian company is using JNode :-)

The company ubiCORE, a rumanian company, is using JNode for their Java MultiThreading Processor. So, it is a processor dedicated to JAVA and that is probably optimised for such usage.

They are using a technology called JavaHMT Technology. JNode is running pure JAVA applications without any other underlying OS. ubiCORE pushed that idea not only in the software but further, until the core of the processor itself !

We hope they will succeed and open the road to other companies that will be confident in JNode Smiling

ClassCast at boot solved

I finally found the problem that caused the ClassCastException during boottime (while mounting the initial ramdisk).

The problem was caused by a bug in the native code compilation of instanceof. This has been solved now.


JNode and Mauve project

I am now also working for the Mauve project.

Mauve is a project aiming at testing the core Java libraries implementations, like GNU Classpath (that JNode is using).

Mauve not only tests the core classes but also the VM. By working on that, we help reporting bugs in Classpath but also in JNode VM... all that in order to be compatible with JLS (Java Language Specifications).

In the near future, I hope to be able to run them under JNode.

Enable JNode's dynamically configurability with OSGi


Why not enable the dynamically configurability of JNode with OSGi just like Eclipse 3.0 did?

It seem natrual that we follow Eclipse 3.0's way since JNode adopted Eclipse's component model.
Currently, I'm working on it, and found the Eclipse's OSGi is rather modular: If you want OSGi and the extension registry, just take an Eclipse drop and use only the org.eclipse.osgi and org.eclipse.core.runtime bundles.

Basically Eclipse is completely OSGi and you should just take the
bundles/plugins you want. Note also that Eclipse guys have a 3.2 plan item to make this even better.

Syndicate content