hallo
guys,
In the Shell in the currently that in Jnode,i feel a problem of that.That taking input Runtime from the User at the promt.
During testing some small useful commands once i want to take a Input from the user during executing the command at runtime.But,i seen Only the Black screen retain after the Input writting.
I think its a unimplemented props in JNode shell.
tango

hai,
guys
The Device Drivers are the main,crucial part of any Operating System.So,for making the drivers for the Specific HW we need a huge learing session for the Hardware's Operations.
But,unfortunately the HW developers are not the supporter of the OPEN SOURCE .So, though i have a HW i cannot take any ideas that what is going on in the HW.hence, then we need another treatment technique for that.... i.e. REVERSE ENGINEERING....but this is not a good way for the development ;-((

though it is a light of hope we seeing now that the HW vendors littlely now coming supporting the OPEN SOURCE TECHNIQUES....for example

JNode summer of code is starting ))

Take your project here, here or whereever you want on JNode site or even from your own ideas and let's go for JNode summer of code.

I have choosen my own JNode summer of code project : writing a vmware disk reader/writer and after I will write a partionning tool. great projects, aren't they ?

hallo,
To interact with the different current working FrameWorks we need more different File System drivers,to enhance the JNODE----------------->

1)EXT2 and EXT3
2)NTFS write support
3)BeFS reading support

will add more soon.....

everyone is requested to set more targets for the FS developers.

I've found an interesting forum that may help to improve JNode community, especially the subcategories 'Growing an Online Community' & 'Search Engine Optimization'