<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Writing on Kevin Raaijmakers</title>
		<link>https://kevinraaijmakers.nl/en/writing/</link>
		<description>Recent content in Writing on Kevin Raaijmakers</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://kevinraaijmakers.nl/en/writing/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Fixing WSL interoperability</title>
				<link>https://kevinraaijmakers.nl/en/writing/wsl-interoperabiliteit-repareren/</link>
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
				<guid>https://kevinraaijmakers.nl/en/writing/wsl-interoperabiliteit-repareren/</guid>
				<description>&lt;h2 id=&#34;the-problem&#34;&gt;The problem&lt;a class=&#34;anchor&#34; href=&#34;#the-problem&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;When interoperability with Windows executables in WSL is broken, launching&#xA;programs like &lt;code&gt;explorer.exe&lt;/code&gt;, &lt;code&gt;code&lt;/code&gt;, or &lt;code&gt;clip.exe&lt;/code&gt; fails. The system reports&#xA;something like:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Enabling the QEMU guest agent in pfSense</title>
				<link>https://kevinraaijmakers.nl/en/writing/qemu-guest-agent-pfsense/</link>
				<pubDate>Tue, 24 Mar 2026 00:00:00 +0000</pubDate>
				<guid>https://kevinraaijmakers.nl/en/writing/qemu-guest-agent-pfsense/</guid>
				<description>&lt;p&gt;If you run pfSense as a virtual machine on Proxmox VE, the QEMU guest agent lets&#xA;Proxmox communicate with the VM properly. Proxmox can then shut down pfSense&#xA;cleanly instead of hard-powering it off, and read the VM&amp;rsquo;s IP addresses directly&#xA;in the Proxmox UI.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Fan control for the Alienware Aurora R12 on Linux</title>
				<link>https://kevinraaijmakers.nl/en/writing/alienware-aurora-r12-fan-control/</link>
				<pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate>
				<guid>https://kevinraaijmakers.nl/en/writing/alienware-aurora-r12-fan-control/</guid>
				<description>&lt;p&gt;I run my Alienware Aurora R12 desktop on Arch Linux. Out of the box, Linux gives&#xA;you no nice GUI to switch between quiet, balanced, and performance fan/thermal&#xA;modes, the way Alienware Command Center (not that it&amp;rsquo;s great) does on Windows.&#xA;The good news: the kernel&amp;rsquo;s &lt;code&gt;alienware-wmi&lt;/code&gt; driver exposes a &lt;code&gt;platform-profile&lt;/code&gt;&#xA;sysfs interface you can write to, and &lt;code&gt;tuned&lt;/code&gt; can automate this based on the&#xA;active power profile.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Syncing Let&#39;s Encrypt certificates to AdGuard Home on Synology</title>
				<link>https://kevinraaijmakers.nl/en/writing/lets-encrypt-adguard-synology/</link>
				<pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate>
				<guid>https://kevinraaijmakers.nl/en/writing/lets-encrypt-adguard-synology/</guid>
				<description>&lt;p&gt;Synology DSM 7 can automatically request and renew Let&amp;rsquo;s Encrypt certificates —&#xA;very convenient. The problem is that other services on the NAS, such as AdGuard&#xA;Home in Docker, don&amp;rsquo;t have access to those certificates. Without anything extra,&#xA;you&amp;rsquo;d have to copy them manually after every renewal.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Bitwarden as an SSH agent in WSL2</title>
				<link>https://kevinraaijmakers.nl/en/writing/bitwarden-ssh-agent-wsl2/</link>
				<pubDate>Mon, 16 Feb 2026 00:00:00 +0000</pubDate>
				<guid>https://kevinraaijmakers.nl/en/writing/bitwarden-ssh-agent-wsl2/</guid>
				<description>&lt;p&gt;I use Bitwarden to manage my SSH keys. The Bitwarden Desktop app on Windows 11&#xA;works fine as an SSH agent, but WSL2 runs in its own lightweight virtual machine&#xA;without direct access to the Windows SSH agent. The fix: forward Windows named&#xA;pipes to a Unix socket in WSL2, using &lt;code&gt;npiperelay&lt;/code&gt; and &lt;code&gt;socat&lt;/code&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Bitwarden native messaging for Vivaldi on Arch</title>
				<link>https://kevinraaijmakers.nl/en/writing/vivaldi-bitwarden-arch/</link>
				<pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate>
				<guid>https://kevinraaijmakers.nl/en/writing/vivaldi-bitwarden-arch/</guid>
				<description>&lt;p&gt;On Windows 11, the integration between the Bitwarden browser extension and the&#xA;Bitwarden Desktop app works automatically. On Arch Linux you have to configure&#xA;that yourself, via a native messaging host.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
