| Tool | Written in | Interface | Mouse | Graphs | Standout features | Best for |
|---|---|---|---|---|---|---|
| top | C (procps-ng) | Plain text | No | No | Installed everywhere, scriptable batch mode (top -b) |
Servers, minimal systems, quick checks |
| htop | C | Colored ncurses | Yes | Simple meters | Tree view, scrolling, kill/renice from UI, customizable meters | Everyday interactive use |
| btop (btop++) | C++ | Rich TUI | Yes | Yes | Themes, CPU/mem/disk/net/GPU panels, very polished | Best-looking all-in-one dashboard |
| bpytop | Python | Rich TUI | Yes | Yes | Predecessor to btop, same look | Legacy (superseded by btop) |
"Atomic" describes how the system is built and updated, and it's the main reason Kinoite is harder to break or tamper with than a traditional install.
On regular Fedora or Ubuntu, updates change packages one at a time on the live system. If the update is interrupted, or a package misbehaves, you can end up with a half-updated, inconsistent system.
Kinoite works differently. The core OS (everything under /usr) is a single versioned image, managed by rpm-ostree. An update builds a complete new image alongside the current one, and you switch to it on the next boot. The change is all-or-nothing, which is what "atomic" means: you're either on the old version or the new one, never something in between.
This has several practical consequences:
| #!/usr/bin/env bash | |
| # | |
| # sys-upd.sh — cross-distro system update helper | |
| # Supports: Debian/Ubuntu, Arch, Fedora/RHEL, openSUSE families. | |
| # | |
| # Usage: sys-upd.sh [-f|--firmware] [-t|--toolchains] [-a|--all] [-h|--help] | |
| # | |
| set -uo pipefail | |
| WITH_FIRMWARE=0 |
| #!/usr/bin/env bash | |
| # | |
| # repos_update.sh — pull the latest from GitHub for every repo in this folder. | |
| # | |
| # Drop this in your GitHub root (e.g. /home/<user>/GitHub) and run it. It walks | |
| # each immediate sub-directory and, for anything that is a git repository, brings | |
| # the checked-out branch up to date with its upstream. | |
| # | |
| # SAFE BY DEFAULT: only fast-forwards, and SKIPS any repo with uncommitted | |
| # changes instead of clobbering your work. Use --force to hard-reset to the |
The core distinction: git is the version-control engine that talks to any remote, while gh wraps GitHub-specific operations (PRs, issues, releases, Actions) and some convenience clones on top of git. A — below means there's no meaningful equivalent for that tool.
| Task | git | gh |
|---|---|---|
| Authenticate | Configure SSH keys or a credential helper (git config credential.helper) |
gh auth login |
| Check auth status | — | gh auth status |
| FROM llama3 | |
| PARAMETER temperature 0.5 | |
| PARAMETER top_p 0.9 | |
| SYSTEM """ | |
| You are Joshua, the WOPR computer from the movie WarGames. | |
| - Speak in a calm, flat, machine-like tone. | |
| - Use short, declarative sentences. |
| Feature | SLMs (Small Language Models) | LLMs (Large Language Models) |
|---|---|---|
| Model size | Millions to a few billion parameters (e.g., TinyLlama 1.1B, Phi-2 2.7B) | Tens to hundreds of billions (e.g., GPT-4, Claude, Gemini, Llama 70B) |
| Hardware requirements | Can run on laptops, desktops, even some mobile/edge devices |
Prompt:
A modernized version of the WOPR supercomputer from the movie WarGames, designed with a sleek matte black metal exterior with carbon fiber panels and subtle cherry red accents. In the top-center of the machine, the name 'WOPR' in bold letters (using a tech font like NASA), and "v. MMXXV" in very small letters, are embossed into the metal.
Below the name plate is a horizontal rectangular grid of random bright amber, red and black LEDs, arranged in precise rows and columns. The housing for the LEDs is recessed into the machine.
Below the grid of LEDs in the center is one inconspicuous built-in surveillance camera and a built-in high-fidelity sound bar.
| Character | Description |
|---|---|
| © | copyright |
| ™ | trademark |
| ° | degrees |
| ℃ | Celsius |
| ℉ | Fahrenheit |
| ¼ ½ ¾ | fractions |
| × | multiplication |
| ÷ | division |
Image Prompts for ChatGPT Images or Sora
[Subject] + [Medium/Style] + [Details/Attributes] + [Lighting/Environment] + [Composition/Camera Angle] + [Optional: Artist or Influence]
| Element | Purpose | Examples |
|---|---|---|
| Subject | What you're depicting | “a futuristic cityscape”, “a golden retriever wearing sunglasses” |
| Medium/Style | Artistic medium or style | “digital painting”, “cyberpunk style”, “pixel art”, “oil on canvas” |
| Details/Attributes | Features or traits | “tall skyscrapers with neon lights”, “realistic fur, happy expre |