• 0 Posts
  • 7 Comments
Joined 6 months ago
cake
Cake day: March 15th, 2026

help-circle
  • From their wiki:

    What Makes Vostok Different? Void Linux is powerful — but it requires effort to set up. Vostok removes that barrier entirely:

    • KDE Plasma out of the box — a full, polished desktop environment ready from the first boot
    • Everything pre-configured — codecs, drivers, browser, fonts — all included
    • Vostok Repository — hundreds of additional packages not available in the official Void repos (Brave, Figma, and more)
    • Beginner-friendly, expert-approved — simple enough for newcomers, powerful enough for professionals
    • 100% free — no subscriptions, no telemetry, no corporate strings
    • One developer, one vision — transparent, independent, and built with love for the community
    • Open to everyone — developers, designers, gamers, students, sysadmins — Vostok is for all of them

    The em dashes definitely gives me LLM-vibes. Regardless, it mostly comes over as Void Linux with KDE Plasma and some onboarding. And I suppose they have their own repository. Furthermore, I think it’s a very new distro as their Github activities only go two months back.

    To OP: Why would you use this over (some) other Void derivatives? Secondly, as you state

    I can customize it myself

    Why even bother with any of these to begin with?







  • I could see it becoming the future. But only under a couple of scenarios.

    Scenario A: It becomes (strictly) better and/or easier than the alternative. Kinda like how systemd effectively replaced SysVinit within a couple of years, simply because it was a more sane alternative. But this is reliant on the read-only aspect being put in place without affecting existing workflows on traditional distros. So, as Fedora Atomic is the atomic distro I’m most familiar with, I’ll provide explicit examples from it:

    • Installing packages shouldn’t take a reboot to take effect. I can see sysexts being leveraged for this eventually.
    • Any commands that involve dnf should (somehow) continue to function. It could even be an alias (or something) that invokes something else entirely. I don’t even think most users will care for what exactly happens in the background, as long as the functional expectation is being met.
    • The previous two points shouldn’t come at a (significant) speed loss.

    Scenario B: It’s enforced on us by (some of) our Linux overlords and/or expected by (parts of) the Desktop Linux stack. Kinda like how the GNOME desktop environment currently has dependencies that are systemd-components. Thus, requiring some hacking to make it work in its absence. Currently, I can only see some RHEL(-adjacent) projects committing to this.

    But I think both of the above scenarios are at least 5 years away. While atomic/immutable distros enjoy a healthy (perhaps even generous) amount of development, AFAIK none of them are actually 100% feature-complete[1] compared to their traditional counterparts. So, fixing (most of) the remaining edge cases to make migration possible for every enthusiast that even considers switching, should probably be their priority.


    1. To be clear, it’s probably at like 95% or so. ↩︎