Add Debian 13 (Trixie) Root on ZFS Guide

[wommy]

Closes #565

Summary

Adds a Root on ZFS installation guide for Debian 13 (Trixie), released as current
stable on August 9, 2025. This is a port of the mature Bookworm guide with
version-specific updates.

Changes

New Documentation

• docs/Getting Started/Debian/Debian Trixie Root on ZFS.rst
  • Ported from Bookworm guide (find/replace: Bookworm → Trixie)
  • Live CD URL updated: cdimage.debian.org/mirror/cdimage/release/current-live/
    → cdimage.debian.org/debian-cd/current-live/ (reflects Trixie paths)

Updated Documentation

• docs/Getting Started/Debian/Debian Bookworm Root on ZFS.rst

  • Added "Newer release available" header pointing to Trixie guide
  • Follows established pattern from Bullseye guide

• docs/Getting Started/Debian/index.rst

  • Updated backports examples to use trixie-backports

Commits

Baseline Creation (Merge Commit d1acd9d):

1. Create Trixie baseline from Bookworm guide
   • Merge commit containing two operations:
     • Rename Bookworm guide → Trixie baseline (d212b7e)
     • Restore Bookworm guide for reference (673fad4)
   • GitHub shows as expandable merge with green "renamed from" badge

Trixie-Specific Modifications (5 commits):
2. Update version strings from Bookworm to Trixie (b805e6b)
3. Standardize release navigation headers (9ceed8b)

• Added "Newer release available" to Bookworm
• Follows Bullseye→Bookworm pattern

4. Update Debian index for current stable (7a226b9)
5. Update GitHub organization references (69a464b)
   • FAQ uses relative link (avoids wiki redirect loop)
   • Issues and commits: zfsonlinux → openzfs
6. Add non-free-firmware component to backports (ee83839)

Total: 8 commits on GitHub (merge structure visible in Commits tab)

For Reviewers:

Recommended: Use GitHub's UI

• Commits tab: Shows all 8 commits with expandable merge
  • Click merge commit (d1acd9d) to see the rename + restore operations
  • Green "renamed from" badge shows Trixie's origin from Bookworm
• Files changed tab:
  • Click "Hide whitespace" for cleaner diff
  • 3 files changed (1 new: Trixie, 2 modified: Bookworm + index)
  • Use blame view to trace line history through the rename

Command-line (if preferred):

# View functional changes only (commits 2-6)
git log d1acd9d..ee83839 --oneline

# See actual diff of modifications
git diff d1acd9d..ee83839 --stat

Quality of Life Improvements in This Port

Minor improvements made during porting:

• Standardized release navigation pattern (follows Bullseye→Bookworm precedent)
• Updated GitHub organization references (zfsonlinux → openzfs)
• FAQ link uses relative reference (avoids wiki redirect)
• Updated repository examples to current stable (trixie-backports)
• Updated Live CD paths to reflect Trixie directory structure
• Added non-free-firmware component to backports repository (required for firmware packages)

These could be backported to earlier guides if desired.

Testing & Validation

Build Status:

• ✅ Documentation builds successfully with no errors
• ✅ All internal links verified
• ✅ RST syntax validated

Installation Testing:

• ⏳ Full walkthrough pending (contributor will test shortly)
• 🤝 Community testing welcome and appreciated!

Testing Note: This is a straightforward port from the well-tested Bookworm
guide. Core ZFS installation process is unchanged—only version strings and
repository references updated. The guide serves as a solid foundation for Trixie
users and a launching point for community feedback.

If you test this guide, please report your results in the comments!

---

cc @rlaager (as requested in the guide)

[gmelikov]

Thank you! I diffed it, it's really is just a bookworm->trixie rebranding (which is expected), changes are good.

Minor note - I thought that Rename Bookworm guide to Trixie baseline commit will give us strange blame on Bookworm, but somehow it didn't, so LGTM. Maybe Bookworm restore commit is somehow special?

[wommy]

yeah i havent used it since 2018 or so and i only used it 5 times then
git mv file.a file.b ; git commit
git checkout HEAD~1 -- file.a ; git commit
git merge --no-ff tmp_branch
i could have swore you needed the merge commit

EDIT: proven false
but i just double checked, i think it can be even more simple with:
git mv oldfile.txt newfile.txt ; git checkout HEAD -- oldfile.txt ; git commit

i was actually really curious as to the right way to do this
i juggled like 5 options and wasnt happy with either bc +1207 newlines
i felt like this was the most clear

ALSO EDIT: i spent 2 hours diving into it, i tested
git mv + checkout (needs -C -C flags) - what i put up above
Interactive rebase (rewrites history)
filter-branch (rewrites history)
filter-repo (corrupts repo)
jujutsu/jj (needs -C -C flags)
2 commits sequential (loses Bookworm blame)
Parallel branches + merge (only keeps one file)

you need the merge --no-ff and a minimum of 3 commits
id love to hear if someone has a smoother way to achieve this

[wommy]

btw i found quite a few inconsistencies across the docs
in docs: Update GitHub organization references in Trixie guide
this same problem plagues the docs across most distros
but i wanted to kick this off first and ask for feedback on how to approach that

another thing that sent me for a loop:
the ordering here dictates the subnav in the sidebar on the index page link
the glob search of *Root on ZFS gives an alphabetical list
and initially i was pretty confused why trixie was at the bottom of the list when its the newest
i already have a commit somewhere that manually enters them in a reversed chronological order (newest first)
i dont think glob is necessary as it literally hides information while reducing only 3 (now 4) lines of code
and its not like a huge workload to add another entry every 18months whenever the next debian drops
but then again, adding the version number to the filename
Debian Trixie Root on ZFS.rst => Debian 13 Trixie Root on ZFS.rst or Debian 13 (Trixie) Root on ZFS.rst
i think debian usually leans into the latter
could be supported with toctree :reversed:
and that could be just as easily done too

[chrisstornowski]

Debian Trixie is using:

/etc/apt/sources.list.d/debian.sources

https://wiki.debian.org/SourcesList

Types: deb deb-src
URIs: https://deb.debian.org/debian
Suites: trixie trixie-updates
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb deb-src
URIs: https://security.debian.org/debian-security
Suites: trixie-security
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

[wommy]

great! you activated my first trap card - i had a followup waiting in the wings exactly for this