<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>hi, it&#39;s mike</title>
    <link>https://mike.puddingtime.org/tags/kvm/</link>
    <description>Recent content on hi, it&#39;s mike</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>mike@puddingtime.org (mike)</managingEditor>
    <webMaster>mike@puddingtime.org (mike)</webMaster>
    <copyright>© 2026, mike</copyright>
    <lastBuildDate>Sat, 16 Dec 2023 14:42:04 -0800</lastBuildDate>
    <atom:link href="https://mike.puddingtime.org/tags/kvm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Daily notes for 2023-12-16</title>
      <link>https://mike.puddingtime.org/posts/2023-12-16-daily-notes/</link>
      <pubDate>Sat, 16 Dec 2023 14:42:04 -0800</pubDate><author>mike@puddingtime.org (mike)</author>
      <guid>https://mike.puddingtime.org/posts/2023-12-16-daily-notes/</guid>
      <description>A soft KVM switcher for Dell monitors and Linux. Photo housekeeping.</description>
      <content:encoded><![CDATA[<h2 id="a-little-bit-of-c-for-a-dell-kvm-switcher-in-linux">A little bit of C for a Dell KVM switcher in Linux</h2>
<p>My Dell monitor has a built-in KVM, which is great. The included Mac software allows you to bind a hotkey to flip between machines. There&rsquo;s no such thing for Linux, but I found <a href="https://www.dell.com/community/en/conversations/monitors/u2723qe-kvm-using-a-keyboard-shortcut-to-switch-in-linux/647fa06af4ccf8a8de56ccc8">this post on the Dell support forums</a> that explains how to use <code>ddcutil</code> to trigger a switch.</p>
<p>The posted C to make it a little executable was victimized by Dell&rsquo;s HTML sanitization, so here it is with the needed includes:</p>






<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-c" data-lang="c"><span class="line"><span class="cl"><span class="c1">// switch_screen.c
</span></span></span><span class="line"><span class="cl"><span class="cp">#include</span> <span class="cpf">&lt;stdio.h&gt;</span><span class="cp">
</span></span></span><span class="line"><span class="cl"><span class="cp">#include</span> <span class="cpf">&lt;stdlib.h&gt;</span><span class="cp">
</span></span></span><span class="line"><span class="cl"><span class="cp">#include</span> <span class="cpf">&lt;sys/types.h&gt;</span><span class="cp">
</span></span></span><span class="line"><span class="cl"><span class="cp">#include</span> <span class="cpf">&lt;unistd.h&gt;</span><span class="cp">
</span></span></span><span class="line"><span class="cl"><span class="kt">int</span> <span class="nf">main</span><span class="p">()</span>
</span></span><span class="line"><span class="cl"><span class="p">{</span>
</span></span><span class="line"><span class="cl">    <span class="nf">setuid</span><span class="p">(</span><span class="mi">0</span><span class="p">);</span>
</span></span><span class="line"><span class="cl">    <span class="nf">system</span><span class="p">(</span><span class="s">&#34;ddcutil setvcp 60 0x11&#34;</span><span class="p">);</span> <span class="c1">// Change this for each computer
</span></span></span><span class="line"><span class="cl">    <span class="k">return</span> <span class="mi">0</span><span class="p">;</span>
</span></span><span class="line"><span class="cl"><span class="p">}</span></span></span></code></pre></div>
<p>I compiled it and made a custom keyboard shortcut for it in GNOME (<code>Settings -&gt; Keyboard -&gt; Keyboard Shortcuts -&gt; View and Customize Keyboard Shortcuts -&gt; Custom Shortcuts</code>).</p>
<p>It works really well. More reliably, in fact, than the Dell-provided functionality does on the Mac, where the machine periodically forgets it is actually connected to the monitor.</p>
<p>There&rsquo;s some latency when you switch, too: maybe 4 seconds to switch from Linux to Mac, and upwards of 8 seconds going in the other direction. Still better than reaching around the back of the monitor to use the hardware button to open the menu and pick a machine.</p>
<h2 id="photo-housekeeping">Photo housekeeping</h2>
<p>With a decent machine under the desk I&rsquo;m going to take another run at learning Darktable, so I spent some time today making sure everything is backed up correctly. I&rsquo;ve had my photos from before 2018 backing up to Backblaze for a while, but was semi-trusting a combo of local network drives and Adobe sync to handle everything since. Today I set up backups from the Thunderbolt photo drive to the Synology, and then I&rsquo;ll set up backup jobs from the Synology to Backblaze.</p>
<p>Al and I were having a chat about my occasional impermanence jags and she wanted to know, maybe a little nervously, what the implications of that were for my pictures.</p>
<p>After dealing with double-checking the health of a bunch of automated backups today, and prepping to make detaching from the Adobe ecosystem a little easier, I&rsquo;m revisiting an idea I had a long while back of making yearly physical books. I&rsquo;ve got terabytes of photos, but when I go through and do the exercise of picking &ldquo;five star&rdquo; images from each year since ~2000, it &hellip; it doesn&rsquo;t come down to terabytes. I&rsquo;d like to do that exercise again, or at least review my choices, make a few redundant online archives, and make a few physical books: One for us, one for Ben.</p>
<p>Whenever I think about what I&rsquo;m trying to do here, I realize that I archive and keep much, much more than I want because I haven&rsquo;t taken the step of specifically preserving what seems worth preserving. So I lug around terabytes of data, zealously preserving all of it and fretting about losing any of it. Making a few physical editions and stowing a few backups of digital proofs of what matters would do a lot to make it all feel less burdensome.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
