Here is a basic proposal for the Command API to enable future improvements to the API without rewriting commands.

The execute() method is something like this:
public void execute( CommandLine cl, InputStream stdin, OutputStream stdout, OutputStream stderr );

This works--for as long as we do not pass a new parameter to execute method.

Let's talk about an equivalent method. Let's say that a command has-a command context. And let's say that a command context has-a command line, a standard input stream, a standard output stream, a standard error stream. The execute() method becomes something like

public void execute( CommandContext ctx );

This works, too--but it is more future-oriented.

Next week, let's say that we want to pass credentials to a command, so that permissions are based upon credentials. We rework the command context interface. We add a credentials property. The execute method becomes something like

public void execute( CommandContext ctx );

But wait! That is the same signature we already have. Commands that do not interact with credentials are unchanged.

0.2.7 has been released. Where is the corresponding on-line and up-to-date JavaDoc documentation? JavaDoc helps us comprehend the API, and therefore, write Java code for the operating system. How do I contribute JavaDoc comments to improve the JavaDoc documentation?

The command API, for example, appears to have no interface for a command, and no abstract base class for a command object. It seems to be based upon the reflection API. The JavaDoc documentation should provide contact information for reporting missing or misleading JavaDoc comments, right?

Thanks,

Hi all,
I did some work for jnode a few years ago(NTFS driver, charva porting, console work,etc) and i was just thinking about looking into the new developments from JNode a bit. Can you maybe answer the following questions:

* Have you implemented "isolation api" or are you just starting the applications in different threads?

* can you boot JNode from hard drive? I know there was a FAT driver which was pretty stable and a NTFS and ext2 drivers which ware unstable..what works now better? I know that there was no formatting application which really worked back then.What about now?

* who wrote the desktop application? do you have any windowing system in mind or is it just a simple program that start other java application in separate threads?

*what happened with the original project owner? is he still contributing?

*who many active developers do you have?

that's all.. for the moment

oo... and by the way.. great job!!!

I have download it but the keyboard layout is English. How can I change it? It is difficult to enter command with a German keyboard.

Sorry if this is the wrong place to post this. I think it's a potentially great addition to JNode.

NestedVM, by Brian Alliet and Adam Megacz, was written as part of the (Java-based) Ibex platform and it translates MIPS-bytecode into Java-bytecode.

In real terms, it allows us to run C-libraries like FreeType on the JVM.

It could address a fundamental weakness of JNode by allowing Java apps that require C/C++ libraries by first compiling them to run on MIPS.

Performance is also surprisingly good.

Homepage:
http://nestedvm.ibex.org/

Quick Start Guide:
http://wiki.brianweb.net/NestedVM/QuickStartGuide