New to the stream? Start here.

T2 Linux — properly T2 SDE, a source-based 'meta-distribution' and distribution build kit he's developed for ~25 years. Day to day on stream he's fixing package build recipes, bumping versions, and rebuilding everything across dozens of CPU architectures ahead of a release.

T1 was ROCK Linux — 'try one.' When ROCK was wound down, the next attempt became 'try two' → T2 (also jokingly 'technology level two'). It started as a placeholder name and just… stuck. He half-jokes about renaming it to something starting with 'A' for better alphabetical listings.

Over 6,000 packages across 25+ architectures, and somewhere around 20,000 commits a year (counting his automation bot, 'data', and a small team). Repology independently ranks it the most up-to-date distribution — over 95% of packages at the newest version. 'Just a tiny little hobby project.'

Real standards work: he's a PDF Association member and project lead of an ISO PDF/raster standard (ISO 23504), and he's been pushing to get JPEG XL into PDF for years. There's serious engineering behind the goofball energy.

Low-level, close-to-the-metal systems work: OS internals, device drivers, toolchains (compilers, linkers, libc), and cross-architecture porting — getting an entire Linux distribution, kernel included, to build and boot on hardware from a modern Ryzen desktop down to a 20-year-old POWER8 or SPARC64 box. It's mostly C and assembly, glued together with Makefiles and shell — not a framework in sight.

Most familiar dev work sits on top of a stable, documented platform — a browser, a runtime, a game engine — that hides the hardware from you. René's work is that hidden layer: there's no framework to fall back on and no 'works in Chrome, ship it.' A bug can mean the machine simply doesn't boot, instead of a stack trace in a log. The 'user' of the code is often the OS itself, running correctly on chips with wildly different quirks, not someone clicking a button in a UI.

René wrote a beginner's guide for exactly this jump — going from application-level code to OS and driver development, close to the metal.Close to the Metal: A Beginner's Guide into OS/Driver Development

His main build box is a Ryzen 9950X3D (PBO/curve-optimized and undervolted). But T2 is a portability lab, so he also builds and streams from an 80-thread IBM POWER8 (128 GB RAM), an SGI Octane, an ARM Snapdragon, DEC Alpha, SPARC64, RISC-V boards — and a Steam Deck he bought purely as a cheap thin client to 'vote with his wallet for Linux.'

He runs his own infrastructure: an nginx-RTMP server in a T2 container in his own data center, and streams into it from whichever machine is the day's victim. Simultaneously to YouTube and Twitch.

vim, inside tmux — he's used tmux (and screen before it) for about 25 years. If you see a wall of green panes, that's it.

Frequently asked. His keyboard is a NuFi Field 75. If you catch additional specifics about his setup on a stream, send them in and we'll add them here.

Help us confirm this from a stream.

His Instagram is the best source — he regularly posts photos of his desk, the current build box, and the growing pile of exotic hardware.@renerebe on Instagram

From a T2 system: t2 install <package> — it fetches, builds from source, and resolves dependencies for you. Wildcards like KDE/* already work, and broader patterns are on the wishlist.

Today, yes-ish: T2 is a source-based rolling release, so you update with t2 up && t2 upgrade and it rebuilds what changed (your toolchain/libc are held back as 'vital' until you choose). Binary updates are explicitly on René's roadmap — in his words, 'soon use binary updates… you should not rebuild packages we ship as binary.'

KDE Plasma is the flagship (Wayland), with GNOME, Cosmic and Trinity also available. Firefox runs where Rust/LLVM are available; on the most exotic architectures you'll find lighter browsers like Arctic Fox, dillo or links.

He insists yes — 'a browser has worked in T2 for 25 years; even my parents and my six-year-old can launch one.' It's a real daily-driver desktop, not just a build kit.

Patches welcome — package anything useful that's missing. There's also a bounty program with cash for specific features and fixes. 'We just need a few more devs.'

For a normal 64-bit PC, yes — that's the standard desktop image. Reading the name: x86-64 = your CPU (a regular Intel/AMD machine), desktop = a ready-to-use KDE Plasma system, glibc-gcc = the safe default toolchain, nocona = built for broad compatibility, and the 26.x number is just year.month — grab the newest. Our Get started guide decodes every part of the name.Get started guide

The current desktop ISO boots into a live KDE Plasma desktop you can try first, then you run T2's guided installer ('stone') — it can auto-partition the disk and prompts you to create your user. It's clear and menu-driven rather than a glossy one-click wizard (a friendlier flow is being built). The Get started page walks it in plain English.

Yes — a quick guided Q&A that asks about your machine (reviving a laptop, a retro box, a Raspberry Pi, Apple hardware, exotic gear) and points you to the right build. No account, no email, runs entirely in your browser.Find your build

Go step by step with a guided expert flow to put together a custom, lean system with only the packages you actually need — still no account required.Build a custom system

Both are legitimate, widely-used open-source tools and the community's go-to — just download them from their official sites (rufus.ie, etcher.balena.io). Antivirus sometimes false-positives on USB-writing tools, because writing a whole disk looks 'suspicious' to it; it isn't a virus. To prove your ISO itself is genuine, match its SHA-256 checksum to the one listed on the T2 download page.

The t2 command. 't2 install firefox' fetches, builds and installs from source with all dependencies; 't2 up && t2 upgrade' updates everything. T2 ships 6,000+ packages — the full searchable list is the official package index, linked in the site footer and the Get started guide.

On Debian's stability: 'Yeah — after 10,000 developers fixed all the shit, it works on Debian.' He won't recommend Ubuntu; if pressed, Fedora is the only other distro he'd name. Otherwise, 'asking me which distro to use is like asking Steve Jobs which OS to recommend.'

'Way too convoluted, complex and slow.' His kernel builds in ~10 minutes where a Nix user reported over an hour. His verdict: 'the only thing better about Nix is their website.'

'I value my life too much to touch Rust.' He'd rather build an off-grid cabin or open a beach café than write Rust — and muses about doing his own language instead.

Spicy: he calls them 'advanced T9 text prediction,' not real AI, and is unimpressed with the quality. Make of that what you will (you're reading a site largely built with the very thing).

Long live-coding marathons (often several hours, sometimes 8–16 CEST) on YouTube and Twitch, opening with 'Did you know most open source code is written for free during the weekend?' Expect package debugging, sharp industry rants, and relentless, self-aware self-promotion.

Surprisingly, yes — mostly because he talks the whole time instead of coding silently. If you don't already know Linux and packaging you won't follow every step, but you'll absorb a lot by osmosis. Treat the confusing bits as a challenge, not a wall.

Subscribe on YouTube/Twitch, join on Patreon, and — his actual ask — use T2 and send patches. 'Support the dream.'