add website and GitHub Pages deployment

2026-09-01 11:23:34 +02:00
parent cb1da62339
commit da28f784a8
48 changed files with 3392 additions and 0 deletions
@@ -0,0 +1,55 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>Init systems — Keru OS</title>
+<meta name="description" content="The init system is yours to choose with Keru: runit, s6, openrc, systemd, busybox-init, sysvinit, dinit, shepherd.">
+<link rel="stylesheet" href="assets/css/style.css">
+<link rel="icon" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'><text y='.9em' font-size='90'>ける</text></svg>">
+</head>
+<body>
+
+<nav class="top" data-nav></nav>
+
+<header class="pagehead">
+    <p class="crumbs"><a href="index.html">home</a> / <a href="swappables.html">swappables</a> / inits</p>
+    <h1>Init systems</h1>
+    <p>Who brings your machine up. Your call.</p>
+</header>
+
+<section>
+    <div class="wrap">
+        <div class="prose">
+            <p>The init system is the first thing that runs after the kernel — it boots the rest of your system and usually supervises services. It's also one of the most fought-over pieces of modern Linux. Keru's answer to the fight is simple: <strong>pick one yourself.</strong></p>
+        </div>
+
+        <div class="grid grid-3" style="margin-top:30px">
+            <div class="card"><span class="h">runit</span><p>Small, fast, BSD-style. Default in Keru — fast boot, simple service supervision, based on the runit process supervisor.</p></div>
+            <div class="card"><span class="h">s6</span><p>The skarnet suite's init and service manager. Dependency-free, designed-for-service supervision, very small.</p></div>
+            <div class="card"><span class="h">openrc</span><p>The classic Gentoo-style init. Compatible with sysvinit-style init.d, predictable "exclusive" service tree.</p></div>
+            <div class="card"><span class="h">systemd</span><p>The dominant init — service manager, logind, udev, resolved, timedate, all in one. If you want it, it's a choice, not an assumption.</p></div>
+            <div class="card"><span class="h">busybox-init</span><p>The bare init from busybox. Minimalist, tiny static binaries, closest to "nothing but a process supervisor."</p></div>
+            <div class="card"><span class="h">sysvinit</span><p>The classic System V init. Simple runlevels, init.d scripts, historically the baseline Linux init.</p></div>
+            <div class="card"><span class="h">dinit</span><p>A modern, fast, dependency-oriented init and service manager. Parallel boot, small footprint.</p></div>
+            <div class="card"><span class="h">shepherd</span><p>GNU's service manager (init). Guile-based, declarative services, part of the GNU project.</p></div>
+        </div>
+
+        <div class="prose" style="margin-top:34px">
+            <h3>Notes on pairing</h3>
+            <p>Some combinations are easier than others. The stability check in the installer flags pairs that aren't yet proven (for example, <code>musl + systemd</code>), but never blocks them — <a href="stability.html">the warn-not-block stance</a>.</p>
+
+            <div class="callout">The init you pick is baked in at first boot. It's a choice you make once, deliberately, at install — not inherited from a default you never saw.</div>
+
+            <p><a href="swappables.html">← All swappables</a></p>
+        </div>
+    </div>
+</section>
+
+<footer data-footer></footer>
+
+<noscript><div style="text-align:center;padding:16px">See the <a href="sitemap.html">sitemap</a> for all pages.</div></noscript>
+
+<script src="assets/js/include.js" data-base="."></script>
+</body>
+</html>