add website and GitHub Pages deployment
This commit is contained in:
@@ -0,0 +1,61 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<title>Installation requirements — Keru OS</title>
|
||||
<meta name="description" content="What you need to install Keru: a network connection, a machine to run it on, and a willingness to make choices.">
|
||||
<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="install.html">install</a> / requirements</p>
|
||||
<h1>Installation requirements</h1>
|
||||
<p>Honest about what installing Keru demands.</p>
|
||||
</header>
|
||||
|
||||
<section>
|
||||
<div class="wrap">
|
||||
<div class="prose">
|
||||
<h3>Hard requirements</h3>
|
||||
<table>
|
||||
<tr><th>Requirement</th><th>Why</th></tr>
|
||||
<tr><td><strong>Working network</strong></td><td>The ISO carries only the installer. Everything else — toolchain, kernel, init, libc, tools — is fetched and compiled during install. No network, no install.</td></tr>
|
||||
<tr><td><strong>A machine that runs Linux</strong></td><td>Keru is a Linux distribution. The installer boots on x86 (and other archs as they're proven).</td></tr>
|
||||
<tr><td><strong>A target disk/filesystem</strong></td><td>The system is written to the filesystem you choose during install.</td></tr>
|
||||
<tr><td><strong>Some patience</strong></td><td>Everything is built from source on your machine. A from-scratch toolchain + system takes time. The compiler, not the package manager, is the bottleneck.</td></tr>
|
||||
<tr><td><strong>A willingness to choose</strong></td><td>Keru's only ask is that you form an opinion about init, libc, filesystem, kernel, and tooling. Defaults exist; the decisions are still yours.</td></tr>
|
||||
</table>
|
||||
|
||||
<h3>Not requirements</h3>
|
||||
<ul class="features">
|
||||
<li><strong>No pre-existing Linux.</strong> You don't need an OS to install from — the ISO + installer handles everything.</li>
|
||||
<li><strong>No manual source builds.</strong> The installer drives the whole from-scratch build for you.</li>
|
||||
<li><strong>No binary packages.</strong> Nothing precompiled to download. You build what you run.</li>
|
||||
<li><strong>No telemetry or accounts.</strong> Nothing phone-home, nothing to sign up for to install.</li>
|
||||
</ul>
|
||||
|
||||
<h3>The network, concretely</h3>
|
||||
<p>At the first installable release (0.1), the network path is straightforward: wired Ethernet via DHCP, or wireless via <code>nmtui</code>, both handled from inside the installer. <a href="network-setup.html">See the network setup flow.</a></p>
|
||||
|
||||
<h3>What "from the network" means</h3>
|
||||
<p>The installer reaches source tarballs (via a mirror such as <code>mirror.keru.org</code>, with upstream as fallback), pulls recipes from the <a href="kama-repos.html">recipe repository</a>, and builds. The heavy lifting is the compiler on your CPU — which is exactly the point of a source-only, from-scratch distribution.</p>
|
||||
|
||||
<div class="callout">If you want fast and prebaked, a binary distro is right there. If you want <em>your</em> machine — built from source to your exact selection — Keru is the one.</div>
|
||||
|
||||
<p><a href="install.html">← Back to install overview</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>
|
||||
Reference in New Issue
Block a user