blogs

Jnode Development

When will the new release of Jnode be released. Like 0.29/0.30. I hope this project is not dead. Tell me about development status. This site has gotten quiet. Still like the idea of an OS on VM. This is the year of the virtual machine. Keep work up. Great OS. I could test the OS with Core 2 Duo 2.26Ghz, 250GB HD,2GB RAM. Keep the work up!

I got a few ideas here. Qt Jambi support, Scala support, include popular Java apps like Lobo and Open Office.org. Printer support, 3D support via lg3d ( now dead, but good idea ), support for running Java ME apps to attract mobile developers.

Keep the work up because Java 7's coming soon and you next major version should support it. Oh and make it more DB friendly for Oracle, like the storage via Java DB idea.

Keep up the GOOD WORK!

GUI

Hi
I can't use JNode GUI.
when i use the gc and then startawt commands
blank my display and my system hang.
What is my problem?

Web Server

Submitted by spgerber on Sun, 08/02/2009 - 12:25.

service

Was wondering if jnode has some sort of web container.

I have a developed a java web server (some time ago)...

Comments? or suggestions?

Removing dependencies

Internal Dependencies

ClassLib has been split out of the trunk and seems to really help the build process. I'd like to see a few more splits like that. I think these 4 groups would be ideal...

1) ClassLib - contains all generic Java API
Some JNode specific parts may exist, but ideally as little as possible or with a clean and defined JNode <-> Java API to reduce porting issues.

2) Kernel - contains all boot, and VM; also contains JNode API
This is required to build/run JNode and would be akin to the Linux kernel; the difference between this section and the next section is security, drivers exist here to be compiled into the kernel such as input and video (not sound, network, etc).

3) Drivers/Support - contains all JNode specific code, drivers and apps
This is extra drivers and support to be loaded at run time (sound, network, etc) and JNode only commands like fdisk, mount as they have little or no use outside JNode. All this would be compiled with but not in the kernel image.

4) Distro - contains (pure java) all non-JNode code
This should follow "write once, run anywhere" ideals and extra JNode projects or 3rd party code, (Sun JDK, JNAsm, tomcat, derby, netbeans, etc)

Kernel and Drivers/Support are very close and the idea behind splitting them is to help maintain the API and security (kernel space/user space). I know those are far off goals but stating them now helps us plan to reach them. Chosing to combine them may be a better idea, I'm not sure myself.

I don't like the Forums and Issue Tracker

I have a lot of ideas and things to say, and some of it should never be said.

Many people have lots of good ideas, and I have one or two as well. But what becomes a great idea often starts as a very bad one, and only after lots of thought and review does it become a great idea.

The Forums and Issue Tracker are full of what could be great ideas that have not been given much thought. To help reduce the clutter, I'd like to propose my ideas here and let people talk them over in IRC or email. Once they have become descent and people agree it's a good direction, then post it officially for review.