Linked by Hadrien Grasland on Sun 20th Feb 2011 13:20 UTC
OSNews, Generic OSes Now that you have an idea of where your OS project is heading as a whole, it's time to go into specifics. The first component of your OS which you'll have to design, if you're building it from the ground up, is its kernel, so this article aims at being a quick guide to kernel design, describing the major areas which you'll have to think about and guiding you to places where you can find more information on the subject.
Thread beginning with comment 463377
To read all comments associated with this story, please click here.
by antonone on Sun 20th Feb 2011 17:56 UTC
Member since:

Thanks for this article, but it appears that the JNode system got missed from the sample OS'es based on VM approach. It even has a GUI so it might be interesting thing to watch, if anyone's interested.

Reply Score: 1

RE: jnode
by Neolander on Sun 20th Feb 2011 18:36 in reply to "jnode"
Neolander Member since:

Indeed. I'll correct this along with some English mistakes once I get access to some real internet connection (EDGE with locked ports is the new 56K).

When looking for examples, I've been highly displeased to discover that most operating systems which were said to be VM-based (like Inferno or JavaOS) were in fact nothing but a java virtual machine running on top of a regular C/C++ kernel, and have given up a bit too quickly apparently.

SharpOS was also an interesting project, but apparently development has ended.

Edited 2011-02-20 18:45 UTC

Reply Parent Score: 1

RE[2]: jnode
by moondevil on Sun 20th Feb 2011 22:33 in reply to "RE: jnode"
moondevil Member since:

That is because in the area VM operating systems the author is either not old enough, or did not research enough the subject.

Pascal MicroEngine in 1976, which used to process P-Code as instruction set.

The Lisp machines the early 80s.

The original Smalltalk environment at Xerox in

Forth is a VM, compiler and operating system, all in one, in the early 70s.

Modula-2 based system for the Lilith architecture.

Some versions of Oberon operating system, use the modules in bytecode form and compile them on load.

Granted this systems still do use some assembly at the core of their implementations, but so do C based OSs.

Reply Parent Score: 3