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

Mounting Hard Drive

Hello. I just started using JNode 2 days ago, and I'm really liking it. When i run it on QEMU the hard drives are mounted automatically. But when I run it on my own PC, the OS doesn't even detect the drive. When I run device command It only shows sg0 which is the CD-ROM.

My hard drive is an ATA WDC WD2500BEVS-7 according to HardInfo. It also says it has a scsi0 controller. It has a ext3 partition with a Linux system installed. I would really like to know if I have to do something or my drive isn't actually supported by JNode.


WANTED: cpio command

The cpio command reads and writes archives in the cpio format. As cp means copy, cpio means copy in/out. The jRPM project at sourceforge.net happens to provide a CPIOInputStream and CPIOOutputStream.

How do you copy files from one JNode machine to another?

Other kernel loaded as process

As we have nano-kernel, so we have possibility to load other kernels (something like linux kernel) under our nano-kernel, or not?
What do you think about it?

How does the JNode gui work?

It seems that everything in the JNode GUI is implemented through the awt/swing components of the jdk. But how do the peers draw on the screen? Does JNode use a X server or the like? How does the JNode wm handle other applications, because for now it seems the defaultLookAndFeel is just applied to every program, making it a very unflexable window manager. I'm also interested how JNode implemented the taskbar+"start button".

The reason I'm asking is because I'm writing my own window manager in pure java (still very early in development). It uses the escher X11 java library to make calls to the X server and I thought perhaps I could contribute to JNode.

I plan to 'procletize' System getProperties() and getEnv()

When I first presented the 'proclet' idea for discussion, one of the problems I wanted to address was the 'global-ness' of the System properties. For example, the 'cd' command changes the current directory by calling "System.setProperty("user.dir", ...)" which actually changes the current directory for all consoles and all currently running applications. Another example is that classic Java apps often look in the System Properties for parameters set by the launch script.

So what I am planning to do is to change the System.getEnv() and System.getProperties() so that they return different objects depending on the current thread's proclet context. This is roughly analogous to the way that the System.in/out/err streams read and write to different places depending on the proclet context. In theory, the implementation should be simple, since I don't have to worry about the equivalent of System.setIn/Out/Err. But it will entail changing the some 'core' classes.

Syndicate content