Linked by Thom Holwerda on Wed 27th Jun 2007 18:59 UTC, submitted by John Nilsson
Thread beginning with comment 251061
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Also from the PDF..
The Singularity kernel is a microkernel; all device drivers, network protocols, file systems, and user replaceable services execute in SIPs outside the kernel.
As for the research project going production, I was speaking hypothetically. Sorry if I didn't make that clear.
On your second remark: this is a research project afaik and is not meant to go to production.
Who says it can't be a real product; Windows NT started off as a project, a better UNIX than UNIX - now its the basis for Windows.
To me, it looks very Plan9'ish. Lets remember guys, all operating systems suck badly. UNIX has its own issues, hence the reason why Plan9 was designed, Windows sucks, but due to inetia, its going to stay.
Singularity will probably start off most likely from the bottom and move its way up, from embedded, servers might go next, and meet in the middle - the end user desktop.
As for singularity today, its research project because it has a number of levels of development - its an entirely new concept; each level needs to achieve a certain level of functionality - each has a milestone. Once it gets to a point that it can fulfil all what current generation operating systems can do, and exceed it - no use having something that does it all, but does it terribly.







Member since:
2005-07-27
It is based somewhat on the idea of microkernels, from the article:
"The first foundational feature common to Singularity systems is the Software-Isolated Process (SIP). Like processes in many operating systems, a SIP is a holder of processing resources and provides the context for program execution. However, unlike traditional processes, SIPs take advantage of the type and memory safety of modern programming languages to dramatically reduce the cost of isolating safe code.
Figure 1 illustrates the architectural features of a SIP. SIPs share many properties with processes in other operating systems. Execution of each user program occurs within the context of a SIP. Associated with a SIP is a set of memory pages containing code and data. A SIP contains one or more threads of execution. A SIP executes with a security identity and has associated OS
security attributes. Finally, SIPs provide information hiding and failure isolation."
On your second remark: this is a research project afaik and is not meant to go to production.