InfoQ

News

Microsoft Research Releases Singularity RDK

Posted by Steven Robbins on Apr 03, 2008 07:11 AM

Community
Architecture
Topics
Research,
Operating Systems,
Open Source,
Programming
Tags
Reference Architectures,
Announcements,
Microsoft
On March 4th, the Singularity Research Development Kit (RDK) was released as an open source project on CodePlex. The RDK is based on the Singularity Project from Microsoft Research by Galen Hunt, Jim Larus and others. The Project web site said that Singularity itself is primarily about "the construction of dependable systems through innovation in the areas of systems, languages, and tools."

The Singularity RDK includes "source code, build tools, test suites, design notes, and other background materials" that can be used to get started investigating and running Singularity. The resources include a 17 page document called "Building and Running Singularity" that walks through the processes of getting Singularity and the RDK setup. The download has more than 50 individual applications and projects that can be built and deployed, including a full test suite and a set of benchmarks.

The RDK also comes with several dozen Singularity Design Notes (SDN) that describe how certain features of Singularity or one of the projects are designed and expected to work. For example, "SDN 0: Singularity Design Motivation" includes talks about so-called Centers of Gravity
Four design points combine to produce an OS that is agile to future research and innovates in system reliability. These design points are: a type safe abstract instruction set as the system binary interface, a unified extension mechanism for applications and the OS, a strong process isolation architecture, and a ubiquitous metadata infrastructure describing code and data.
The Microsoft Research site and the RDK site had this overview of the Singularity project itself:
Advances in languages, compilers, and tools open the possibility of significantly improving software. For example, Singularity uses type-safe languages and an abstract instruction set to enable what we call Software Isolated Processes (SIPs). SIPs provide the strong isolation guarantees of OS processes (isolated object space, separate GCs, separate runtimes) without the overhead of hardware-enforced protection domains. In the current Singularity prototype SIPs are extremely cheap; they run in ring 0 in the kernel’s address space.

Singularity uses these advances to build more reliable systems and applications. For example, because SIPs are so cheap to create and enforce, Singularity runs each program, device driver, or system extension in its own SIP. SIPs are not allowed to share memory or modify their own code. As a result, we can make strong reliability guarantees about the code running in a SIP. We can verify much broader properties about a SIP at compile or install time than can be done for code running in traditional OS processes. Broader application of static verification is critical to predicting system behavior and providing users with strong guarantees about reliability.
The Singularity project site has several articles, interviews, and MSDN links related to Singularity and the RDK. Some of the most useful for getting started include "Singularity: Rethinking the Software Stack" [pdf] by Galen Hunt and James Larus and a PDF version of a Singularity RDK tutorial [pdf].

The RDK site has a very active discussion list where many community members post questions, solutions, and ideas about using Singularity and the RDK.

The Singularity RDK is currently only for academic non-commercial use.

1 comment

Reply

open source... by o f Posted Apr 8, 2008 3:08 PM
  1. Back to top

    open source...

    Apr 8, 2008 3:08 PM by o f

    hejdig.

    AFAIK Singularity nor the Singularity RDK are open source. They are both some other type of license.

    /OF

Exclusive Content

VMware Infrastructure 3 Book Excerpt and Author Interview

VMware Infrastructure 3: Advanced Technical Design Guide and Advanced Operations Guide provides a wealth of practical insights into setting up virtualization in todays corporate environments.

Architectures of extraordinarily large, self-sustaining systems

Can a system that is so large it cannot be comprehended be "designed" in a conventional sense? The foundations of computing are about to change. In this talk, Richard P. Gabriel explores why and how.

Using Ruby Fibers for Async I/O: NeverBlock and Revactor

Ruby 1.9's Fibers and non-blocking I/O are getting more attention - we talked to Mohammad A. Ali of the NeverBlock project and Tony Arcieri of the Revactor project.

Agile and Beyond - The Power of Aspirational Teams

Tim Mackinnon talks about the aspirations behind the Agile principles and practices, the desire to become efficient, to write quality code which does not end up being thrown away.

Concurrency: Past and Present

Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.

ActionScript 3 for Java Programmers

Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.

Neal Ford On Programming Languages and Platforms

Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.

Future Directions for Agile

David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.