-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathindex.html
executable file
·78 lines (73 loc) · 3.27 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
<!DOCTYPE html>
<!-- in vi we trust -->
<!--
-- Copyright (c) 2014, 2015 Antti Kantee
-- All Rights Reserved
-->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="keywords" content="rump kernel, component, portable, driver, TCP/IP stack, PCI, SCSI, virtio, POSIX, embedded, bare metal, hypervisor, operating systems, unikernel, unikernels">
<meta name="description" content="Rump kernels provide portable, ready-to-integrate kernel-quality operating system drivers running on a documented hypercall interface. The Rumprun unikernel uses rump kernels to provide a unikernel suitable for POSIX applications on the cloud and on bare metal.">
<meta name="robots" content="index, follow">
<link href="rumpkernel.css" type="text/css" rel="stylesheet">
<title>Rump Kernels</title>
<link rel="icon" type="image/x-icon" href="https://rumpkernel.github.io/favicon.ico">
</head>
<body>
<div id="header">
<table>
<tr><td>
<img src="logo150.png" alt="">
</td>
<td class="bigtext">Rump Kernels
<hr>
<div id="slogan">"You can make an omelette without breaking the kitchen!"</div>
</td>
<td>
<ul>
<li>Shortcuts to <a href="https://github.com/rumpkernel/wiki/wiki/">Wiki</a></li>
<li><a href="https://github.com/rumpkernel/wiki/wiki/Info:-FAQ">FAQ</a></li>
<li><a href="https://github.com/rumpkernel/wiki/wiki/Info%3A-Publications-and-Talks">Publications</a></li>
<li><a href="https://github.com/rumpkernel/wiki/wiki/Repo">Repositories</a></li>
<li><a href="https://github.com/rumpkernel/wiki/wiki/Tutorial:-Getting-started">Getting started</a></li>
</ul>
</tr>
</table>
</div>
<div id="breadtext">
<p>
Rump kernels enable you to build the software stack you need
without forcing you to reinvent the wheels. The key observation is
that a software stack needs driver-like components which are conventionally
tightly-knit into operating systems — even if you do not desire the
limitations and infrastructure overhead of a given OS, you do need drivers.
</p>
<p>
We solve the problem by providing free, reusable, componentized, kernel
quality drivers such as file systems, POSIX system calls,
PCI device drivers and TCP/IP and SCSI protocol stacks.
For examples of what you can achieve with rump kernels, see the
<a href="https://github.com/rumpkernel/wiki/wiki/Repo">repositories</a>
we provide. There is also a wiki page for
<a href="https://github.com/rumpkernel/wiki/wiki/Info%3A-Who-Uses-Rump-Kernels">3rd
party projects using rump kernels</a>.
</p>
<p>
The article <a href="http://www.fixup.fi/misc/usenix-login-2015/login_oct15_02_kantee.pdf">Rise and Fall of the Operating System</a>
provides an extended high-level motivation for rump kernels.
The book <a href="http://www.fixup.fi/misc/rumpkernel-book/">Design
and Implementation of
the Anykernel and Rump Kernels</a> gives a technical description of the
fundamental operating principles and terminology. Further
information is available on
<a href="https://github.com/rumpkernel/wiki/wiki/">the wiki</a> or interactively
via the <a href="https://github.com/rumpkernel/wiki/wiki/Info:-Community">community</a>.
</p>
</div>
<div id="footer">
<!-- use picons.me social pack png/32 -->
<a href="https://github.com/rumpkernel" title="Watch us on GitHub!"><img src="img/github.png" alt="Watch us on GitHub!"></a>
</div>
</body>
</html>