--- name: solnix-user description: > Use Solnix as a command-line user: find and install software from the signed binary cache, run it, understand why a familiar Linux/BSD command behaves differently, and recover after a boot-environment rollback. Use when someone asks to install a package, what a command does on Solnix, or why their system looks different after a rollback. For running services, storage and zones use solnix-sysadmin; for building or porting software use solnix-porter. license: CC0-1.0 metadata: author: solnix version: "0.1.0" persona: user status: migrated from site/skills SOLNIX-USER (phase 1); full rewrite planned in phase 4 --- # Solnix: user Solnix is illumos built and managed with Nix. You install software the Nix way from a signed binary cache; the system underneath is illumos (SMF, ZFS, zones), not Linux. ## Tools this uses `search_packages`, `package_status`, `translate_command`, `search_manpages`, `list_systems` (this server); `nix`, `beadm`, `zfs` (standard commands). ## Install a package 1. **Find the attribute; don't guess it.** Call `search_packages {query}`. Done when you have an attr such as `pkgs.solnix.ripgrep` and its `system` is the machine's (`list_systems` names them). 2. **Check it is served.** Call `package_status {pname}`. Done when a `served_recipes` row for the system has `narinfo_served: true`. If none does, say there is no signed binary for it yet and stop; `queue` shows whether a build is pending. 3. **Install.** ```sh nix profile install nixpkgs#ripgrep # handbook: learning Nix (Reference below) ``` Done when `nix profile list` shows the package. If the install says the attribute does not exist, the Solnix flake does not export that name yet (handbook: search, "only names the Solnix flake exports resolve"); say so. 4. **Mention open advisories.** If `package_status` listed `cve_advisories`, tell the user the CVE ids and the `fixed_in` versions. On another Nix host (not Solnix), configure the cache first (see `steering/trust-and-signing.md`, repo root) and install from `git+https://git.solnix.io/solnix.git?ref=unstable#` ([handbook: search](https://solnix.io/docs/handbook/search); without `?ref=` you get the default branch, 26.11: [handoff 20261102-rows-served-2611-default](https://codeberg.org/solnix/solnix-infra/src/commit/c2ecf4535e0fc32261bbfb2414bc7961a73fa6ca/docs/handoff/20261102-rows-served-2611-default-e1-hosted-answers.md)). On OpenIndiana this is `pkg install`; Solnix has no `pkg` (`../rules/users-and-updates-solnix-way.md`). ## "This command behaves differently" 1. Call `translate_command {command, from: "linux"}` (or freebsd/openbsd/netbsd). Done when you have the Solnix command and its compare page URL. 2. If there is no match, call `search_manpages {query: ""}` and read the Solnix page. On a default Solnix system `/usr/bin/grep`, `sed`, `date` and `ls` are the illumos ones (`../rules/shell-xpg4-vs-gnu.md`; packages added to the system can replace them); the compare page says which variant runs (`/usr/bin`, `/usr/xpg4/bin`, a GNU package). Done when you can cite the man page section that explains the difference. ## After a rollback A Solnix generation is a ZFS boot environment `solnix-N`; rolling back boots an older one. On a system set up by solnix-install, `/home` (the installer's user) is a dataset shared by every boot environment and survives; on a disk image, and for a declared user's default `/export/home/` ([users.nix](https://codeberg.org/solnix/solnix/src/commit/5a8e5ce75a33086d7be4410149847bdf7501b8fc/modules/config/users.nix); install-be makes `export/home` in the BE), the home may be inside the BE, so an older BE has the older files (see `../rules/zfs-datasets-and-properties.md`; ask `zfs list -o name,mountpoint` where yours is). Software installed into the system configuration follows the generation. Run `beadm list` to see which BE is active (`N` now, `R` on reboot). To roll back, or to go forward again afterwards, follow `../rules/be-generations-and-rollback.md`: it has the commands, what to confirm with the user first, and how this differs from an OpenIndiana BE made by `pkg update`. Reference: [handbook: boot environments](https://solnix.io/docs/handbook/boot-environments). ## Reference (load on demand) - `../rules/be-generations-and-rollback.md`, `../rules/users-and-updates-solnix-way.md` - `../rules/shell-xpg4-vs-gnu.md` - [handbook: for Linux users](https://solnix.io/docs/handbook/for-linux-users) - [handbook: learning Nix](https://solnix.io/docs/handbook/learning-nix#pkg--nix-command-by-command), `nix profile install nixpkgs#X`, `nix profile list` **Status:** the install image is preview-grade ([handbook: getting started](https://solnix.io/docs/handbook/getting-started)); no graphical installer has shipped ([graphics-claims-audit.md](https://codeberg.org/solnix/solnix/src/commit/5a8e5ce75a33086d7be4410149847bdf7501b8fc/docs/graphics-claims-audit.md), row 7).