65 lines
4.1 KiB
HTML
65 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>Network setup — Keru OS</title>
|
|
<meta name="description" content="How the Keru installer handles networking: the connectivity gate, nmtui, and the re-check loop.">
|
|
<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> / network setup</p>
|
|
<h1>Network setup</h1>
|
|
<p>Connectivity is a hard requirement. The installer makes connecting easy.</p>
|
|
</header>
|
|
|
|
<section>
|
|
<div class="wrap">
|
|
<div class="prose">
|
|
<h3>Why networking is mandatory</h3>
|
|
<p>The ISO carries <em>only</em> the installer — there's no prebuilt base image on the disk. Your entire system (toolchain, kernel, init, libc, filesystem tooling, tools) is fetched from the network and compiled during installation. So the installer treats a connection as a hard gate: no network, no install. It won't pretend otherwise.</p>
|
|
|
|
<h3>The flow, exactly</h3>
|
|
<ol>
|
|
<li><strong>Probe.</strong> The installer checks connectivity against several hosts (<code>1.1.1.1</code>, <code>github.com</code>) using <code>ping</code>, falling back to a TCP connect via <code>nc</code> if needed.</li>
|
|
<li><strong>If connected:</strong> a simple <code>[ keru ] network: connected</code> and it moves straight to crafting your system.</li>
|
|
<li><strong>If not connected:</strong> you're told, and asked — <code>Connect to the network now (runs nmtui)? [Y/n]</code>.</li>
|
|
<li><strong>Say yes:</strong> <code>nmtui</code> opens. Connect to your network, press okay.</li>
|
|
<li><strong>Saying no:</strong> the installer exits with <code>a network connection is required to install Keru</code>.</li>
|
|
<li><strong>Re-check.</strong> After <code>nmtui</code> closes, connectivity is probed again. If you're online, you continue. If not, it asks again — it never fakes success.</li>
|
|
</ol>
|
|
|
|
<div class="terminal">
|
|
<div class="tbar"><span class="dot r"></span><span class="dot y"></span><span class="dot g"></span><span class="t">keru@live:~$</span></div>
|
|
<pre>[ keru ] warning: network: not connected
|
|
Connect to the network now (runs nmtui)? [Y/n] <span class="k">y</span>
|
|
<span class="p">(nmtui opens — pick your network, connect, press ok)</span>
|
|
[ keru ] network: connected</pre>
|
|
</div>
|
|
|
|
<h3>Details that matter</h3>
|
|
<ul class="features">
|
|
<li><strong>Wired is the path of least resistance.</strong> A physical Ethernet connection with DHCP typically just works — the probe succeeds and you skip straight to choosing.</li>
|
|
<li><strong>Wireless goes through nmtui.</strong> The NetworkManager TUI handles Wi-Fi selection, WPA credentials, and the rest. The installer doesn't guess; it hands you the tool.</li>
|
|
<li><strong>Loop, don't lie.</strong> If you run <code>nmtui</code> but never connect, the installer loops back to the prompt rather than proceeding on a "trust me, it worked" basis.</li>
|
|
</ul>
|
|
|
|
<div class="callout"><strong>What if nmtui isn't available?</strong> The live ISO ships with it, so this is an edge case — but if it's missing, the installer tells you plainly and lets you bring the network up yourself before continuing.</div>
|
|
|
|
<p><a href="installer-walkthrough.html">Walkthrough</a> · <a href="installation-requirements.html">Requirements</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> |