migrate website from KeruOS web to its own repo
Deploy website to GitHub Pages / deploy (push) Failing after 3s
Deploy website to GitHub Pages / deploy (push) Failing after 3s
This commit is contained in:
@@ -0,0 +1,49 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<title>mkfs-root — Keru OS docs</title>
|
||||
<meta name="description" content="The mkfs-root.sh reference: formatting and assembling the target root as your chosen filesystem.">
|
||||
<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="docs.html">docs</a> / build-pipeline / mkfs-root</p>
|
||||
<h1>mkfs-root.sh</h1>
|
||||
<p>Finalizing the root as the filesystem you chose.</p>
|
||||
</header>
|
||||
|
||||
<section>
|
||||
<div class="wrap">
|
||||
<div class="prose">
|
||||
<p><code>scripts/mkfs-root.sh</code> is the final stage of the build pipeline. Given your chosen <code>TARGET_FS</code>, it formats and assembles <code>$ROOT</code> so the disk reflects exactly the filesystem you selected at install.</p>
|
||||
|
||||
<h3>What it does</h3>
|
||||
<ul class="features">
|
||||
<li><strong>Formats.</strong> Creates the filesystem image with the matching mkfs tool (ext4, btrfs, xfs, zfs, f2fs, jfs, reiserfs, swap, or the ext2/ext3 lineage).</li>
|
||||
<li><strong>Populates.</strong> Copies the built rootfs into the formatted volume.</li>
|
||||
<li><strong>Wiring.</strong> Ensures fstab and boot records match your selections.</li>
|
||||
</ul>
|
||||
|
||||
<h3>Honest flags</h3>
|
||||
<p>The filesystem tooling is built in stage 2 from your choice — if you picked zfs, you get ZFS tools; if reiserfs, you get its (unmaintained) tooling, after a stability warning. Whatever you choose, the tooling and the format match.</p>
|
||||
|
||||
<div class="callout">The result of <code>stage 3</code> is a rootfs that will boot — with the exact filesystem, kernel, init, and tools you picked. That's the whole pipeline in one line.</div>
|
||||
|
||||
<p><a href="build-pipeline.html">← Build pipeline</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