OSKit

From OSDev Wiki
Jump to navigation Jump to search

Proposed for deletion This page or section is proposed for deletion! You can help the wiki by talking about it on its talk page.

HistoricalCuriosity.png

The content of this article or section is considered a historical curiosity and should not be considered for new designs.


Utah's OsKit

The OSKit is a framework and a set of 34 component libraries oriented to operating systems, together with extensive documentation. By providing in a modular way not only most of the infrastructure "grunge" needed by an OS, but also many higher-level components, the OSKit's goal is to lower the barrier to entry to OS R&D and to lower its costs. The OSKit makes it vastly easier to create a new OS, port an existing OS to the x86 (or in the future, to other architectures supported by the OSkit), or enhance an OS to support a wider range of devices, file system formats, executable formats, or network services. The OSKit also works well for constructing OS-related programs, such as boot loaders or OS-level servers atop a microkernel.

For language researchers and enthusiasts, the OSKit lets them concentrate on the real issues raised by using advanced languages inside operating systems, such as Java, Lisp, Scheme, or ML--- instead of spending six months or years groveling inside ugly code and hardware. With the recent addition of extensive multithreading and sophisticated scheduling support, the OSKit also provides a modular platform for embedded applications, as well as a novel component-based approach to constructing entire operating systems.

http://www.cs.utah.edu/flux/oskit/

Note that OSKit expects that you'll be happy to work with COM interfaces. -- PypeClicker

Also note that the OSKit homepage has not been updated since June 27, 2002, so development has seemed to cease. -- Alboin