<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wsl2 on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/wsl2/</link><description>Recent content in Wsl2 on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 10 Sep 2026 09:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/wsl2/index.xml" rel="self" type="application/rss+xml"/><item><title>C Drive Full but WSL Says Otherwise? The "Grow-Only" Virtual Disk Trap — Reclaiming 150 GB in One Pass</title><link>https://blog.lynxflow.co/en/posts/wsl-docker-vhdx-shrink-reclaim-disk/</link><pubDate>Thu, 10 Sep 2026 09:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/wsl-docker-vhdx-shrink-reclaim-disk/</guid><description>The numbers didn&amp;rsquo;t add up During a routine disk health check, I hit a discrepancy:
Windows showed the C drive at 949 GB with 652 GB used — in the red. But df -h / inside WSL (Ubuntu) reported only 135 GB used. That left 500+ GB unaccounted for. Common sense says deleting a file in Linux should shrink usage on the Windows side too — I&amp;rsquo;d deleted 62 GB of video output the night before, so the C drive should have loosened up considerably. It didn&amp;rsquo;t budge.</description></item><item><title>ccswitch Edited the Model, Claude Code Didn't Budge: A Three-Layer Override Root-Cause Diagnosis</title><link>https://blog.lynxflow.co/en/posts/ccswitch-model-not-applying-claude-code/</link><pubDate>Tue, 18 Aug 2026 21:36:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/ccswitch-model-not-applying-claude-code/</guid><description>&lt;img src="https://blog.lynxflow.co/images/ccswitch-model-not-applying-claude-code.png?v=090603" alt="Featured image of post ccswitch Edited the Model, Claude Code Didn't Budge: A Three-Layer Override Root-Cause Diagnosis" /&gt;Origin: Three Edits, Zero Effect I opened ccswitch (v3.19.2, the Windows-side Claude Code config switcher), clicked &amp;ldquo;edit provider,&amp;rdquo; changed the Opus-tier model, and saved. Restarted Claude Code — still running the old model. Edited, saved, restarted again — still no change.
&amp;ldquo;Doesn&amp;rsquo;t change&amp;rdquo; problems are the worst kind to guess at. Below is the process of forcing out the root cause with logs and a field-by-field database comparison. The conclusion is more tangled th</description></item><item><title>How to Install Hermes Agent on WSL2 (2026)</title><link>https://blog.lynxflow.co/en/posts/install-hermes-wsl2/</link><pubDate>Fri, 31 Jul 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/install-hermes-wsl2/</guid><description>&lt;img src="https://blog.lynxflow.co/images/install-hermes-wsl2.png?v=090500" alt="Featured image of post How to Install Hermes Agent on WSL2 (2026)" /&gt;Hermes is a self-hosted, self-improving AI agent (Python, MIT). On WSL2 it installs the same way as on Linux — the official installer lands under ~/.hermes. This guide was verified against a live WSL2 instance running Hermes v0.16.0.
1. Install (official one-liner) 1 curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash The installer handles its own dependencies: uv, Python 3.11, Node.js, ripgrep, and ffmpeg. On WSL2 it detects your existing Git and uses it (no bundled Git needed).</description></item></channel></rss>