migrate website from KeruOS web to its own repo

2026-09-01 12:06:36 +02:00
commit 4a32fab414
56 changed files with 4120 additions and 0 deletions
@@ -0,0 +1,54 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>Network tools — Keru OS</title>
+<meta name="description" content="Choose your network management with Keru: networkmanager, connman, systemd-networkd, or nmtui alone.">
+<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> / network tools</p>
+    <h1>Network tools</h1>
+    <p>How your network gets managed. Your call.</p>
+</header>
+
+<section>
+    <div class="wrap">
+        <div class="prose">
+            <p>The network stack has as many opinions attached as the init system. Keru applies the same rule: pick the manager you want, and it's built into your system — nothing wireless-by-default imposed, no "just use the standard one."</p>
+        </div>
+
+        <div class="grid grid-4" style="margin-top:30px">
+            <div class="card"><span class="h">nmtui</span><p>The default. Just NetworkManager's terminal user interface — connect wires and Wi-Fi without a full manager on your system.</p></div>
+            <div class="card"><span class="h">networkmanager</span><p>The full NetworkManager — daemon, D-Bus API, <code>nmcli</code>, handles wired, wireless, VPN, and more.</p></div>
+            <div class="card"><span class="h">connman</span><p>Intel's connection manager — light, D-Bus bus–independent, designed for embedded and minimal systems.</p></div>
+            <div class="card"><span class="h">systemd-networkd</span><p>systemd's network configuration daemon — declarative unit-based config, pairs with systemd/udev.</p></div>
+        </div>
+
+        <div class="prose" style="margin-top:34px">
+            <h3>Notes on the default</h3>
+            <p>The default is <code>nmtui</code> — the interface, not the daemon — which is the lean choice: you get the easy <code>nmtui</code> workflow during install without committing yourself to running NetworkManager's daemon afterward. If you want the full manager, it's one selection away.</p>
+
+            <h3>Coherence</h3>
+            <p>If you chose <code>systemd</code> as your init, <code>systemd-networkd</code> pairs naturally. If you're on runit or s6, a standalone manager (or just <code>nmtui</code>) fits the picture. The installer offers the pieces; you assemble them.</p>
+
+            <div class="callout">During install, network setup uses <code>nmtui</code> itself (the installer runs it when you need to connect) — independent of what you pick as your system's eventual network tool. <a href="network-setup.html">The install-time network flow.</a></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>