<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>macos on Notes</title><link>https://packetslave.github.io/experiments/blog/tags/macos/</link><description>Recent content in macos on Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 16 Aug 2026 20:32:46 +0000</lastBuildDate><atom:link href="https://packetslave.github.io/experiments/blog/tags/macos/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Claude Desktop connectors are reusable MCP servers</title><link>https://packetslave.github.io/experiments/blog/posts/claude-desktop-connectors-mcp/</link><pubDate>Sun, 16 Aug 2026 20:32:46 +0000</pubDate><guid>https://packetslave.github.io/experiments/blog/posts/claude-desktop-connectors-mcp/</guid><description>&lt;p>It turns out Claude Desktop connectors are just plain MCP servers sitting on
disk, and Claude Code can run the same server from its own config. Install
once and both clients get the integration. I had Fantastical, my calendar
app, talking to Claude Code in about 10 minutes.&lt;/p>
&lt;h2 id="where-the-servers-live">Where the servers live&lt;/h2>
&lt;p>I already had the Fantastical connector installed in Claude Desktop, which
raised the obvious question: where does Desktop keep the server it actually
runs? The answer is that each installed connector lives here:&lt;/p></description></item><item><title>How symbolic and hard links work on Unix</title><link>https://packetslave.github.io/experiments/blog/posts/symbolic-and-hard-links/</link><pubDate>Thu, 13 Aug 2026 00:38:00 +0000</pubDate><guid>https://packetslave.github.io/experiments/blog/posts/symbolic-and-hard-links/</guid><description>&lt;p>Unix file systems support 2 kinds of link: hard links and symbolic links.
Both come from the same command, &lt;code>ln&lt;/code>, but they work in very different ways.
This post explains how each kind works. It then covers where Linux and the
BSDs, including macOS, disagree.&lt;/p>
&lt;h2 id="inodes-first">Inodes first&lt;/h2>
&lt;p>A file on disk is not really a name. It is an inode: a numbered record that
holds the file&amp;rsquo;s metadata and points to its data blocks. The inode stores the
owner, the permissions, the timestamps, and the size. It does not store the
file name.&lt;/p></description></item></channel></rss>