splux-site · log · files · refs · tags · releases · people · languages · GitHub · file
site/docs/index.html
4170 bytes at 4c4f12c · GitHub
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Handbook - Splux Linux</title>
<meta name="description" content="Splux Linux handbook: live images, installation, and SPS.">
<link rel="icon" href="../../../../../../assets/favicon.png" type="image/png">
<link rel="stylesheet" href="../../../../../../assets/style.css">
</head>
<body>
<a class="skip" href="#main">Skip to content</a>
<div class="wrap wide">
Splux Linux
source-based Linux using SPS
<div class="handbook">
<main id="main">
<h2>Handbook</h2>
<hr class="rule">
<p>This is the Splux Linux handbook. Splux is a source-based distribution. Packages are built on the machine that installs them, from recipes in <a href="../../../../../../git/">sps-core and sps-extra</a>, using SPS. A third tree, <a href="../../../../../../docs/community/">community</a>, exists but is not enabled until you add it.</p>
<p>Live images are development snapshots, not a numbered stable release. Read the chapter that matches the ISO you booted.</p>
<h3>Start here</h3>
<table class="docs">
<thead>
<tr><th>Chapter</th><th>What it covers</th></tr>
</thead>
<tbody>
<tr>
<td><a href="../../../../../../docs/images/">Live images</a></td>
<td>tty, slim, and Plasma: what is on each disc, and which one to download.</td>
</tr>
<tr>
<td><a href="../../../../../../install/">Install</a></td>
<td>Three paths in tabs: <code>setup</code>, a full manual install from the tty ISO without <code>setup</code>, and the slim image.</td>
</tr>
<tr>
<td><a href="../../../../../../docs/sps/">SPS tools</a></td>
<td><code>src</code>, <code>sget</code>, <code>mkpkg</code>, <code>pkin</code>, and the rest of the package system.</td>
</tr>
<tr>
<td><a href="../../../../../../docs/community/">Community</a></td>
<td>Opt-in <code>sps-community</code> recipes. Not enabled by <code>setup</code>. One line in <code>repos.conf</code>.</td>
</tr>
<tr>
<td><a href="../../../../../../docs/first-boot/">After first boot</a></td>
<td>Passwords, network, services, and the next packages.</td>
</tr>
</tbody>
</table>
<h3>Install paths</h3>
<p>Use <a href="../../../../../../install/#setup">guided setup</a> on <code>sps-live-tty.iso</code> or <code>sps-live-plasma.iso</code> if you want dialog screens. Use the <a href="../../../../../../install/#manual">manual chapter</a> if you want the same work as shell commands, with only tools that exist on the tty disc. The <a href="../../../../../../install/#slim">slim chapter</a> is rescue, partitioning, and network debugging. Slim is not a source-install disc.</p>
<h3>Architecture and status</h3>
<p>Published images are x86_64 hybrid ISOs. Live PID 1 is busybox init with gettys on tty1 and ttyS0 (or systemd when the machine that built the ISO had it). The login is <code>root</code> with an empty password.</p>
<p>SPS 1.0 is usable. Official recipe trees are still being built out. A console install compiles for a long time. A Plasma install compiles Qt and KDE and takes much longer.</p>
<h3>Reference trees</h3>
<ul class="plain">
<li><a href="../../../../../../packages/">Package browser</a> (1474 packages)</li>
<li><a href="../../../../../../git/SPS/blob/README.md/">SPS README</a></li>
<li><a href="../../../../../../git/SPS/blob/DESIGN.md/">SPS 1.0 formats and behavior</a></li>
<li><a href="../../../../../../git/SPS/blob/man/setup.1/">setup(1)</a></li>
<li><a href="../../../../../../git/SPS/blob/PACKAGE-MAINTAINER.md/">Package maintainer guide</a></li>
<li><a href="../../../../../../git/sps-core/">core collection</a></li>
<li><a href="../../../../../../git/sps-extra/">extra collection</a></li>
<li><a href="../../../../../../git/sps-community/">community collection</a> (opt-in)</li>
<li><a href="../../../../../../git/">Splux Git</a></li>
<li><a href="../../../../../../source/">Source repositories</a></li>
</ul>
<h3>Fastfetch</h3>
<p>Fastfetch is a native SPS package. On a Splux install it counts SPS packages in its Packages module and still reports Flatpak, Homebrew, Nix, and other managers when they are present. The system default is gray labels and a yellow P in the SPS logo. A user config in <code>~/.config/fastfetch/</code> overrides that default. Fastfetch is not started from shell profiles.</p>
</main>
</div>
</div>
<script src="../../../../../../assets/docs.js?v=4c4f12c-20261019130111"></script>
</body>
</html>