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

compilation errors, or me being stupid

Hi all

I just downloaded the JNode source, as i wanted to build the OS, and potentially contribute if it is within my abilities.

I am having a bit of a battle though, and not being familiar with the project, i don't know if its something i am doing incorrectly or not.

I read through the readme.txt and tried to compile the first sub project (Jnode-Core) and
I'm getting a massive amount of compilation errors

Most of them along the long of the below statement. Does that mean there is something invalid inside my build.xml file..?

/home/tim/NetBeansProjects/JNode-Sources/jnodesources-0.2.6/core/src/openjdk/vm/java/io/JNodeFileSystem.java:3: package gnu.classpath does not exist

FindBugs

Hi!

Has anyone tried to run FindBugs over the JNode sourcecode?

http://findbugs.sourceforge.net/

JNode needs a style guide

I've seen quite a bit of the JNode code base, and one thing that I find irritating is the inconsistent and occasionally bad coding style. I see:

  • inconsistent indentation,
  • inconsistent use of whitespace around operators, before and after braces, parentheses, etc
  • inconsistent spacing between lines,
  • files containing TAB characters,
  • minimal useful in-line comments
  • useless or non-existing Javadoc comments on key methods, or entire APIs.

I've also come across some basic coding errors that would have been picked up by a cursory code review. I've seen command classes that catch java.lang.Exception, command classes (with 'execute' methods) that write to System.out / System.err rather than the command's out/err, code that repeatedly looks up the same system service in loops. I've seen left-over trace prints, and Unsafe.debug calls. I've seen code that is so hacked around that it is unintelligible. And some of codebase's the lack of concern for multi-threaded access is truly frightening!

The new command line syntax mechanism

It is very good to see progress in the shell part of JNode. However I have a question. Why are the arguments converted to an array of strings before it is given to the shell command? It seems to me that information is "lost" in this conversion.

Kind regards
Jacob Kofod

MagicPermission not granted for type: org.jnode.driver.system.acpi.AcpiTable

I get the following message during boot:

MagicPermission not granted for type: org.jnode.driver.system.acpi.AcpiTable

What does that mean? is it a bug?

Syndicate content