After Getting Started seriously
Well after all the encouragement from Stephen, Fabien, Isantha, Peter and all others, I have finally set up a sandbox from the latest svn head.
But, i thought before i dive into building the ISO and then tinkering with the source code and bombarding all of you with questions which will make u tear ur hair apart, .... i decided that i will use the latest nightly-build ISO for some more testing ....
I used the 18 July ISO and made the following observations which may/maynot be helpful ....
My approach towards Jnode is more from a user point of view ... the user a beginner java developer must be able to do something with it, that is write and compile Java code using the OS written in JAVA. My VISION is that a person wanting to learn java must do it so on the Operating system written in JAVA.
So in my previous post titled Getting Started seriously i was able to learn how to set classpath and compile a simple text java program. All the errors in setting classpath mentioned in my previous post were solved after i used the latest 18 July ISO. So those bugs seem to be fixed.
This build however sometimes mounted my windows partitions and sometimes did not mount them at all.
I use the windows partitions for copying my sample java programs to /jnode/home directory
for eg. cp /devices/hda2/HelloWorld.java /jnode/home
cd /jnode/home
javac HelloWorld.java
java HelloWorld
So if jnode does not mount my windows partitions i have to reboot again ...
- Login to post comments
... in addition to mounting partitions
I saw a message during boot time saying
Software reset failed. IDE pri still busy.
Hope this will help ...
This won't help but ...
... I also occasionally see JNode getting stuck during boot for no apparent reason. I suspect that the root cause is synchronization / race condition bugs. Unfortunately, we don't have any tools that will help us to diagnose JNode kernel deadlocks, etc.
I'm not sure if the "Software reset failed. IDE pri still busy." message is related. I recall seeing it when JNode successfully boots. (This is not to say that this is not relevant to your example though ...)
My suggestion is to put up with the problem for now. By all means create an issue, but I suspect that it will be a long time before we are able to fix it.
Jnode Stuck at boot ... NO
Stephen, Jnode has not stuck at boot for me even once since i first started with it ....
only that it does not always mount the NTFS partitions on my laptop ....
On a desktop machine in my office it mounted everytime i booted Jnode.
By the way i always boot from the CD and not VMWARE due to the fact that i do not have processor support for VMWARE so its very very ................slow.
CD boot is much faster ....
Secondly, I know that very few of you there to look into the engineering and code of Jnode ....
But, I am taking a different approach to help speed up the process ... i will be unveiled on the fly ...
I can add to the numbers by starting with development myself, but time is little and I dont think I am too good at this stage to delve into the code and requesting you for a commit right ....
But, i will try to use skills that i feel i have a little better to contribute to Jnode ...
Also, tried running Derby ... gave me some PermissionException (* READ WRITE) ...
On the face of it i feel that it is because maybe derby tries to create some log files in the directory from where the java command is run and i guess that directory does not have write permission ... i guess only /jnode directory has a write permission ....
OR
Probably jvm security manager needs permission for the derby.jar and derbyclient.jar files to be set .....
Let me know if there is a chmod command or equiv. or how to set permissions for the security managaer ....
I was trying to say that ...
... JNode problems of the nature of "XYZ sometimes happens during boot" are particularly hard to track down. My "hangs during boot" problem is just an example. I'm suggesting that you might just have to put up with having to rebooting more than once to get NTFS up and working on your laptop. (Obviously, we do need to track down your problem and fix it, but don't hold your breath ...)
Derby most likely needs a change to the relevant plugin descriptor to add the required permissions. Take a look at some of the other plugin descriptors (e.g. in the "distr" or "cli" trees) for examples.
RE
Hey Stephen,
No issues to put up with constant reboot ...
anything for Jnode even @ of one reboot every minute ...
my point was that it did not happen in 50 time i booted jnode from my desktop ... but did happen when i booted from my laptop once in 3 boots ... so might be a driver or hardware specific problem ....
Tell me should i keep posting experiences observations in forums ... i feel this is beter than posting in issues and then waste ur precious time in u trying to figure out if it really is and issue ... i mean in a forum discussion if its concluded that its an issue then someone can put it in the issue tracker ....
JavaDB/Derby i tried to run it not using a plugin architecture but using simple command java ....
thats because i am still using the prebuilt ISO rathen than creating my own ISO though i have a eclipse sandbox ready .. it will take quite some time for me to get all configuration right and successfully compile jnode and build the ISO.
Plugins vs Java
I don't know how to "grant" permissions for an application run using "java", or even if it is currently possible. Fabien D has written a plugin builder application that might allow you to create a plugin on JNode, but I don't know how to use it. Can you help us out Fabien?
there is only global permission ...
... for the java command. I don't think there is currently support for permission for each program that could be run with java command.
The documentation of Application Packager is here : it give all permissions by default.
Fabien
my blog : en français, in english or both
Re your laptop problem ...
my point was that it did not happen in 50 time i booted jnode from my desktop ... but did happen when i booted from my laptop once in 3 boots ... so might be a driver or hardware specific problem ....
It is certainly related to something to do with your hardware, but it is not possible to say what. It might be in the disc drivers, in the FS driver, in the code that tries to automount file systems, or the code that "schedules" what happens in the bootstrap sequence. Looking at the code might give some insights, but it is also possible that finding the problem will involve some serious kernel debugging ... on a machine that experiences the problem.
I think issues are appropriate
It is up to you, but I think raising an issue is appropriate if you think something is broken. Especially if you can provide sufficient information to allow the problem to be tracked down.
Indeed, I've no problems with people raising "support request" issues when they need help with a problem. After all, that's what the issue type was created for.
The advantage with using issues is that we can track / manage them via the issue tracker. And when they are "closed" they drop out of view. By contrast, problems reported in forum postings tend to get lost / overlooked.
some answers ...
i do not have processor support for VMWARE
That's the first I hear that vmware need processor support. As far as I know, it's always software emulation but i might be wrong ... Anyway, if you say it's slow ...
Have you tried something else like VirtualBox or kvm (for the latter I guess you won't have processor support) ?
But, i will try to use skills that i feel i have a little better to contribute to Jnode ...
Yes, you should start with simple things and with the ones you feel better : that's the better way to start and get success. Then, you can continue with harder things if you want.
About Derby, you should contact hagar and lsantha because they tried to use derby in jnode. They might have more informations to help you.
Fabien
my blog : en français, in english or both
RE some answers
Hey fabien,
if there is processor support like virtualizations extensions then running jnode on vmware is no problem ....
else software emulation takes a lot of time ....
sample this it takes at least 20 minutes for the jnode gui to come up on a core duo laptop with 2 gb RAM ... i guess its quite a lot of time .. i use the vmx files provided ....
if thats not right then suggest me some configurations so that it could be a little fast ....
virtual box is very very slow ... kvm or qemu is slower than VMWARE ... at least on windows XP prof. os .... for all the virtual machines i am allocating 1024 MB of ram ...
did post a forum topic Native database but no response from both ...
but m working myself on figuring out ... read my earlier post to stephens response in After getting started topic thread and suggest something if u can ...