Another Linux Distro Project From Ikey Doherty

Summary of technological concepts, product features, and analysis

1) Barney: a tool/project aimed at distro/OS build theory (not a new distro release)

• The video claims Barney (named after Ikey Doherty’s son) is not itself a distro, but a tool to build distributions and explore OS/distro design theory.
• A design document exists, but the speaker notes little is publicly known about Barney’s long-term roadmap.

2) Core design problem: package management complexity + distro bootstrap weakness

The described “basic problem” is that:

• Package managers handle composition and dependencies for pre-built artifacts by fitting solutions to the local system using repository candidates.
• As more virtual/alternative candidates exist, dependency resolution grows from simple graphs to complex constraint systems.
• Handling version dependencies, conflicts, and priorities becomes a way to solve composition problems locally.
• “Any binary distro ultimately suffers” from a key flaw: lack of bootstrap support (i.e., difficulty ensuring the system can fully rebuild its own toolchain coherently from sources).

3) Barney’s approach (from the design doc): source-first, validation, caching, rebuild-on-miss

Planned/claimed approach includes:

• Source-first design.
• Full chain validation (implying each build step can be validated end-to-end).
• A caching system for reuse of artifacts.
• A package “output” model where “some kind of package” exists as a hash-keyed build of a specific package.
• If an artifact is missing:
  • it will be rebuilt
  • and the build queue will force recomputation.

4) Multi-stage bootstrap + dependency-graph consistency + circular-dependency breaking

Key features highlighted:

• Explicit goal: multi-stage bootstrap automated so the toolchain can be fully re-bootstrapped.
• During that process, the reverse dependency graph should remain consistent.
• A mechanism intended to break circular dependencies, specifically mentioning the U2 Linux ↔ systemd circular dependency issue.

5) “Stateless” / hermetic direction

• The speaker connects Barney to prior concepts from the Clear Linux team and mentions stateless Linux distribution ideas.
• It’s described as aiming for hermetic-style behavior (i.e., builds/distribution outputs are reproducible and self-contained rather than relying on mutable host state).

6) “Immutable throughput”: containerized builds + cached artifacts + content-addressing

Build execution model:

• Every build happens in specially-produced containers.
• Uses cached artifacts and an “immutable throughput” concept.
• Cached builds include unique files from the install tree in a random-access friendly format.
• A local content address is referenced to generate artifacts/images on demand for routes/installs/build paths.

7) “Why this exists” framing (analysis of motivation, not technical)

The video asserts Barney exists largely because Ikey wanted to “make a point” about industry funding and attention. The speaker frames it as:

• not aiming to create a general-purpose OS,
• but demonstrating how distros are built without needing major funding (compared to a cited “$13 million” claim),
• while sharing code and a YouTube series teaching the architecture and usage.

8) Trailer/content plan (tutorial-style promise)

The speaker mentions:

• an intro video
• and an additional YouTube series about production of the tooling:
  • how it works,
  • how to use it,
  • and open sharing of code/architecture.
• There’s also mention of Ko-fi for behind-the-scenes content.

---

Main speakers / sources (as identifiable from the subtitles)

• The narrator/speaker of the video (not named in subtitles)
• Ikey Doherty (primary subject; founder/creator referenced repeatedly)
• Nomadic Core (AerynOS community member/source quoted with a statement)
• Ermo (AerynOS project member; mentioned in communications/welfare-check context)
• Joshua Strobel (Budgie desktop leader, referenced historically)
• Josh (Joshua Strobl) (named in the open-letter excerpt)