Files
keru/swappables.html
Astral 4a32fab414
Deploy website to GitHub Pages / deploy (push) Failing after 3s
migrate website from KeruOS web to its own repo
2026-09-01 12:06:36 +02:00

54 lines
3.6 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Swappables — Keru OS</title>
<meta name="description" content="The Keru differentiator: every major component — init, libc, filesystem, kernel, privilege elevation, networking — is chosen by you at install time.">
<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> / swappables</p>
<h1>The Swappables</h1>
<p>Every foundational component, yours to choose at install time.</p>
</header>
<section>
<div class="wrap">
<div class="prose">
<p>Keru's differentiator is one sentence: <strong>nothing is fixed, nothing you didn't ask for is forced on you.</strong> The installer presents each foundational component as a flat, open choice, and the system that boots is assembled from exactly the ones you picked.</p>
<p>This is what distro arguments get settled with, resolved ahead of time by you instead of argued forever by maintainers. Runit vs systemd, glibc vs musl, ext4 vs btrfs, vanilla vs hardened kernel — all of it becomes <em>your</em> decision, made once, at install.</p>
</div>
<div class="grid grid-2" style="margin-top:34px">
<a class="card" href="inits.html"><span class="num">init</span><span class="h">Init system</span><p>Who brings your system up at boot. runit, s6, openrc, systemd, busybox-init, sysvinit, dinit, shepherd.</p></a>
<a class="card" href="libcs.html"><span class="num">libc</span><span class="h">C library</span><p>The foundation under everything that runs. glibc, musl, uclibc-ng.</p></a>
<a class="card" href="filesystems.html"><span class="num">fs</span><span class="h">Filesystem</span><p>The shape of your disk. ext4, btrfs, xfs, zfs, f2fs, jfs, reiserfs, swap.</p></a>
<a class="card" href="kernels.html"><span class="num">kernel</span><span class="h">Kernel</span><p>The spine of the machine. linux, linux-lts, linux-hardened, linux-cachyos, linux-zen.</p></a>
<a class="card" href="privilege-elevation.html"><span class="num">priv</span><span class="h">Privilege elevation</span><p>How you elevate. doas, sudo, opendoas, su.</p></a>
<a class="card" href="network-tools.html"><span class="num">net</span><span class="h">Network tools</span><p>How the network is managed. networkmanager, connman, systemd-networkd, nmtui alone.</p></a>
</div>
<div class="prose" style="margin-top:40px">
<h3>Beyond the big six</h3>
<p>Kernel parameters, locale, clock, and keymap are all configurable too — surfaced through <code>make.conf</code>, the profile that your choices produce. The swappables aren't a fixed list; they're a stance. <a href="make-conf.html">Read the make.conf reference.</a></p>
<h3>Stability is scoped to these</h3>
<p>Because choice multiplies the surface, Keru is stable on the combinations it offers, and warns (never blocks) beyond that. <a href="stability.html">How that works.</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>