Documentation

Everything you need to install and run JaypixOS. If something here doesn't match what you're seeing, the ISO you have is probably older than this page — check for a newer build.

Installing

Boot the ISO, log in as root (automatic, no password), and run:

jinstall

You'll get a choice between two paths:

Mode	What it asks	Good for
`jinstall --fast`	Disk, hostname, username, password. Everything else defaulted.	Most people, most of the time.
`jinstall --custom`	The full menu — locale, mirrors, disk layout, profile, network, bootloader, users, packages.	Dual-boot setups, non-default filesystems, anyone who wants full control.

A terminal (Konsole) is always installed regardless of which path you take or what you pick along the way — you're never left without one after first boot.

Fast install

jinstall --fast picks a disk automatically if there's only one, uses Btrfs with the standard subvolume layout, installs KDE Plasma, and wires up Cloudflare DNS/NTP — all without asking. You only answer:

Which disk, if there's more than one
Hostname (defaults to jaypixos)
Username (defaults to jaypix)
Password

That's it — the rest runs unattended.

Custom install

jinstall --custom opens the full guided menu. Every section shows its current state on the right as you move through it, and nothing is locked in until you choose Install at the bottom. The menu order roughly follows: locale → mirrors → disk → swap → bootloader → hostname → authentication → profile (desktop environment) → network → additional packages → timezone.

Partitioning

Under Disk configuration, Use a best-effort default partition layout is the recommended, pre-selected option: a 1 GiB boot partition (FAT32) plus a Btrfs root using the rest of the disk, with the standard subvolumes:

Subvolume	Mounted at
`@`	`/`
`@home`	`/home`
`@log`	`/var/log`
`@pkg`	`/var/cache/pacman/pkg`

If your chosen disk is under 20 GiB, both install paths will warn you and ask for confirmation before continuing — KDE Plasma needs more room than that, and installing anyway is very likely to run out of space partway through.

jpkg

jpkg is JaypixOS's package manager — a friendlier layer over pacman and the AUR, not a replacement for either. It checks core and extra first, then JPN (JaypixOS's own repo), then falls back to the AUR.

jpkg install <package>
jpkg search <term>
jpkg update

Command reference

Command	Alias	Does
`update`	`up`	Full sync + upgrade (`pacman -Syu`)
`install`	`i`	Install a package — checks core/extra, then JPN, then AUR
`remove`	`rm`	Remove a package
`purge`	—	Remove a package, its now-unneeded deps, and its configs
`search`	`s`	Search core/extra + JPN + AUR in one call
`info`	—	Show package info
`list`	—	List installed packages
`orphans`	—	List orphaned packages
`clean-orphans`	—	Remove all orphaned packages
`rollback`	—	Undo the last transaction — full filesystem snapshot on Btrfs, package-db-level otherwise
`build`	—	Build and install an AUR package (git clone + makepkg -si)
`edit`	—	Open a package's PKGBUILD in `$EDITOR` before building
`merge-configs`	—	Review `.pacnew` files left after a transaction

Pass -y / --yes to skip confirmation prompts, same as pacman's --noconfirm.

Network & DNS

Ethernet, Wi-Fi, and mobile broadband should all come up automatically via DHCP, both in the live environment and after install (NetworkManager is enabled by default even if you skip network configuration entirely during a custom install). DNS and NTP are pointed at Cloudflare out of the box:

DNS: 1.1.1.1 / 1.0.0.1, opportunistic DNS-over-TLS
NTP: time.cloudflare.com, falling back to pool.ntp.org

For Wi-Fi specifically, use iwctl to authenticate; for mobile broadband modems, mmcli.

The terminal

Konsole is installed unconditionally — you'll always have a terminal available after login, regardless of which desktop packages you picked during install.

FAQ

Is this still Arch?

Yes. Full core/extra compatibility, standard pacman package format, nothing about dependency resolution reinvented. JaypixOS adds an installer, a package manager, and some defaults — it doesn't fork the package ecosystem.

Can I use archinstall instead?

No — it's not on the system. jinstall replaces it entirely, including the underlying menu system for the custom path.

What desktop environments are supported?

KDE Plasma is the maintained, default target. Other desktop environments are selectable in the custom install menu (it's still the same profile system Arch's own installer uses under the hood) but aren't the focus of testing.

Troubleshooting

Install seems stuck during package downloads

We're actively tracking a download stall that can occur during package retrieval on some setups. If you hit it, check back here — this section will be updated as soon as it's root-caused. In the meantime, a fresh attempt with a different network path (e.g. a different Wi-Fi network, or wired instead of Wi-Fi) is worth trying.

"Could not commit transaction" partway through install

This almost always means the target disk is too small for the packages being installed (KDE Plasma needs meaningfully more than the bare minimum). Both install paths warn you up front if your disk is under 20 GiB — if you skipped past that warning, try again with more space.

Something else went wrong

Run jinstall --custom share-log to upload the install log and get a shareable URL.