Skip to content

v0.3.0 — LazyOS

Choose a tag to compare

@Brunux Brunux released this 22 Oct 00:36
· 311 commits to main since this release

v0.3.0 — LazyOS

The distribution has a name, a mark and a wallpaper, and everything that said
Nureb now says LazyOS: the prose, the identifiers, the directories, the desktop
entries, the icon theme, the manual's path and the idle screen's wordmark. The
boot chain, the kernel and the session are the ones v0.2.0 validated; the
identity changed as a clean break, and the session gained auxiliary swap (a card
becomes extra memory without editing a partitioning tool by hand).

Coming from Nureb

This release does not read the old names, and that is deliberate: a
half-renamed card installs a half-renamed eMMC, and the two names then live in
the tree at once. If the card you are holding was written before this release,
write a new one (or scripts/install-emmc.sh from a v0.3.0 card, which clones
the running system) instead of upgrading it in place.

Three things a person can still notice on an old card:

  • ~/.config/mimeapps.list keeps the old default applications. GIO merges
    a user file over /etc/xdg/mimeapps.list, so a double click keeps opening
    the old viewer until the file is removed. The new card does not carry one.
  • The swap label is lazyos_swap. resume=LABEL=lazyos_swap is the
    hibernate wiring; a partition labelled nureb_swap stays usable as swap but
    cannot be resumed from. sway-hibernate says so instead of failing quietly.
  • The agents' accounts moved with the data directories
    (~/.local/share/lazyos/agents), so an account directory keeps working only
    after the tree is copied; the menu creates a new one in one row.

What changed

  • The mark is an arcade button: a cyan bezel, an orange dome, a base03
    crescent for depth and a base1 highlight, drawn in the session's own four
    colours. brand/lazyos.svg is the source and
    scripts/make-brand.sh renders everything from it, so the launcher, the
    wallpaper and the About card cannot disagree about the picture.
  • The icon theme is LazyOS and carries lazyos.png next to the 219
    Font Awesome names (220 files in 48x48/apps and in scalable/apps, the
    latter with the SVG for GTK at larger sizes).
  • The wallpaper is the brand, at the panel's real mode (1366x912): the mark,
    lazy by design in cyan and » press any key to continue « underneath it. The
    lock screen keeps the mountain photograph on purpose: the desktop is the
    surface the brand owns, and the photograph is what is up when nobody is
    looking.
  • The distribution says its own name: /etc/os-release is a regular file
    with ID=lazyos, PRETTY_NAME="LazyOS <version>" and ID_LIKE=debian, the
    greeter greets with LazyOS · lazy by design, /etc/issue says the same to a
    virtual terminal, and the default hostname is lazyos.
  • The version has one source: the committed
    VERSION file. build-rootfs.sh reads it, forwards it
    through sudo into the chroot and records it as version in
    /etc/debian-aarch64-revision, so /etc/os-release, the build record and the
    tag cannot disagree.
  • The identifiers: org.lazyos.* desktop entries, lazyos-view,
    lazyos-find and lazyos-thumbnail, /usr/share/doc/lazyos/ for the manual,
    ~/Dev/LazyOS for the repository snapshot, lazyos-busy/lazyos-tablet/
    lazyos-capture in $XDG_RUNTIME_DIR, ~/.config/lazyos and
    ~/.local/share/lazyos for state, LAZYOS as the format label and
    lazyos_swap as the swap label. The swayfx packaging revision is
    1lazyos1, so installing over an old .deb is an upgrade.
  • The root menu grows an ai group, with Agents and Dictation together
    instead of scattered between the openers and the session actions.
  • Auxiliary swap turns a card into memory: rofi-swap (Places, and the root
    menu's system section) picks a disk and a size, then creates a
    lazyos_swap partition and the /etc/fstab block that activates it now and on
    every boot (nofail, a 15 s device timeout, priority 10 - below zram's 100, so
    compressed RAM is used first). The candidate list is the same ui_disks
    function Format a disk uses, so neither menu offers the eMMC, the card the
    system is running from, the SPI flash (mtd*) or the eMMC's hardware boot
    partitions. The status row turns it off again. resume=LABEL=lazyos_swap is
    still the hibernate wiring, and adding it is a kernel command line change and a
    rebuilt kpart.
  • About LazyOS is a new launcher entry: the mark as its icon, and a
    fastfetch card whose wordmark, colours and module order are the branded
    ones — the machine's facts, with the distribution's name on the left.
  • check-system.sh grows "The brand", and it is the release's witness: it
    FAILs when /etc/os-release is Debian's again, when the wallpaper or the mark
    is missing, and when an org.nureb.* entry survived the rename; it WARNs when
    the greeter, /etc/issue, the fastfetch files or the lock's decision lose the
    brand, because those are a hand edit away.

Validation

The rename was swept with git grep: outside the release notes (which describe
the rename on purpose), reports/ and the plan that documents it, the old name
does not appear. The brand was exercised on the build host — scripts/make-brand.sh
renders the three files, the icon reads at 48 px, the wallpaper composes at the
panel's mode, and the fastfetch card was run against the shipped configuration.

The hardware run that signs this release off is the one in
reports/, with
docs/test-checklist.md § The brand as the list: the
desktop wallpaper, the lock keeping the photograph, the About row and its card,
/etc/os-release, the greeter's greeting, the console banner and hostname.

Assets

asset what it is
google-asurada.img.xz the disk image: the three ChromeOS GPT partitions (kernel, /boot, root), ready for dd
google-asurada-rootfs.tar.zst the same root filesystem as a tarball (with /boot inside), for writing your own card with scripts/write-sd.sh
google-asurada.vmlinuz.kpart the signed FIT kernel partition of that image; it embeds the image's root=UUID, so it belongs to this image and no other
SHA256SUMS SHA-256 of the three assets
sha256sum -c SHA256SUMS
xz -dc google-asurada.img.xz | sudo dd of=/dev/mmcblk1 bs=4M conv=fsync

On the Chromebook: developer mode, crossystem dev_boot_usb=1 dev_boot_signed_only=0, insert the
card and pick external disk in the firmware menu. It comes up to a greetd prompt — user
brunux, password debian, passwordless sudo. Change the password before using it for
anything real.
scripts/install-emmc.sh installs it to internal storage.

What it does not carry

The artifact is sanitized and asserted clean by scripts/lib-dist.sh:
no Wi-Fi profiles (a released image knows no network and asks for one), no SSH host keys and no
machine-id (both generated on first boot, so every installation has its own identity), and no
personal files beyond the session configuration this repository ships.

Known limitations

  • An old card keeps the old names until it is rewritten; see Coming from Nureb.
  • The image size is fixed by the build, and a larger card keeps the space after p3 unused. Write
    the tarball with scripts/write-sd.sh to size p3 to the whole card.
  • Artifacts are not byte-reproducible yet (FIT timestamp, filesystem UUIDs).
  • The battery gauge's chemistry and time-to-empty properties are upstream failures; waybar reads
    the capacity directly, which works.
  • There is no hardware video decoder, and Vulkan is not usable (PanVK answers Mali-G57 not
    supported
    ); the session renders through EGL and Panfrost, and video is CPU work.

Upstream

Vendored from pmaports commit 0e458a2417d6f5ed61c7b70621d5632e30136091 (2026-10-15), mainline
Linux 7.2.7, swayfx 0.6 on scenefx 0.5.