68 lines
4.1 KiB
HTML
68 lines
4.1 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<title>FAQ — Keru OS</title>
|
|
<meta name="description" content="Frequently asked questions about Keru OS: what it is, how it differs from Gentoo/Bedrock, what it means for you.">
|
|
<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="community.html">community</a> / faq</p>
|
|
<h1>FAQ</h1>
|
|
<p>Straight answers.</p>
|
|
</header>
|
|
|
|
<section>
|
|
<div class="wrap">
|
|
<div class="prose">
|
|
|
|
<h3>What is a "meta-distribution"?</h3>
|
|
<p>In the GNU/Linux world it names the Gentoo/Nix/Bedrock family: distributions organized around <em>choice and composition of components</em> rather than a fixed opinionated stack. Keru is the anti-opinionated member — its meta is choosing <em>not to choose for you</em>. <a href="anti-opinionated.html">Details.</a></p>
|
|
|
|
<h3>Is Keru a "meta-OS" that runs any kernel?</h3>
|
|
<p>No. Keru is a Linux distribution. Its freedom lives above the kernel — init, libc, filesystem, and Linux kernel variants. It won't boot a BSD or illumos kernel; that's not the claim and not on the roadmap.</p>
|
|
|
|
<h3>How is this different from Gentoo?</h3>
|
|
<p>Gentoo is source-based and highly configurable, but it still picks most of your stack and calls it defaults. Keru extends the same impulse to its logical end: no default init, no default libc, no default filesystem. And its manager, Kama, is a ~225-line shell script — no resolver, no database.</p>
|
|
|
|
<h3>How is this different from Bedrock?</h3>
|
|
<p>Bedrock stitches multiple <em>distributions</em> together (apt + pacman + xbps side by side). Keru doesn't compose distros — it composes <em>components</em>, one init/libc/fs/kernel/tool at a time, built from source.</p>
|
|
|
|
<h3>Why is network required to install?</h3>
|
|
<p>The ISO carries only the installer. Your entire system is fetched and compiled during install, so a connection is a hard gate. It's the price of "power to choose anything" — nothing is prebuilt. <a href="installation-requirements.html">More.</a></p>
|
|
|
|
<h3>Will my system be stable?</h3>
|
|
<p>Stable on the combinations Keru offers you — that's the promise. If you pick something past the proven edge, the installer warns and lets you proceed. You're never blocked. <a href="stability.html">The full stance.</a></p>
|
|
|
|
<h3>Is this a joke or a real project?</h3>
|
|
<p>Real. The repos are live, AGPL-3.0, and the road to 0.1 is documented. It's at the "design is public, nothing has booted hardware yet" stage — which is exactly what 0.1 is for.</p>
|
|
|
|
<h3>What's with the Japanese?</h3>
|
|
<p><strong>ける</strong> (Keru) and <strong>ける・けいとうてき</strong> (keru keitō-teki) — "craft your system." Kama (窯) means "kiln." The naming is deliberate atmosphere, not branding gimmick. <a href="ethos.html">More.</a></p>
|
|
|
|
<h3>Why is the package manager in shell?</h3>
|
|
<p>Because a package manager should be legible, and shell is the most legible thing that can run a build recipe. The real cost of your build is the compiler, not the manager — so the manager gets to be simple.</p>
|
|
|
|
<h3>When can I install it?</h3>
|
|
<p>The first release, 0.1, ships as a bootable ISO. <a href="news/roadmap-0.1.html">Follow the road to 0.1</a>.</p>
|
|
|
|
<h3>Where do I ask something this page doesn't cover?</h3>
|
|
<p><a href="contact.html">Contact channels</a> — issues first, then the mailing list.</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> |