<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Logs on Erethon&#39;s Corner</title>
    <link>https://blog.erethon.com/log/</link>
    <description>Recent content in Logs on Erethon&#39;s Corner</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 31 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.erethon.com/log/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>This Week in NixOS, Week 35 2025</title>
      <link>https://blog.erethon.com/log/twin-35-2025/</link>
      <pubDate>Sun, 31 Aug 2025 00:00:00 +0000</pubDate>
      
      <guid>https://blog.erethon.com/log/twin-35-2025/</guid>
      <description>&lt;p&gt;
Keeping the streak up, here&amp;#39;s the fourth week of This Week In NixOS.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>This Week in NixOS, Week 34 2025</title>
      <link>https://blog.erethon.com/log/twin-34-2025/</link>
      <pubDate>Sun, 24 Aug 2025 00:00:00 +0000</pubDate>
      
      <guid>https://blog.erethon.com/log/twin-34-2025/</guid>
      <description>&lt;p&gt;
Lots of interesting things happened this week in the NixOS ecosystem. Here are
my highlights.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>This Week in NixOS, Week 33 2025</title>
      <link>https://blog.erethon.com/log/twin-33-2025/</link>
      <pubDate>Sun, 17 Aug 2025 00:00:00 +0000</pubDate>
      
      <guid>https://blog.erethon.com/log/twin-33-2025/</guid>
      <description>&lt;p&gt;
Second week of my NixOS notes on what happened in the community or that I
learned that I found interesting.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>This Week in NixOS, Week 32 2025</title>
      <link>https://blog.erethon.com/log/twin-32-2025/</link>
      <pubDate>Sun, 10 Aug 2025 00:00:00 +0000</pubDate>
      
      <guid>https://blog.erethon.com/log/twin-32-2025/</guid>
      <description>&lt;p&gt;
I often send to friends links about the NixOS ecosystem that I find interesting.
I figured it&amp;#39;s better if I write about it so I have an easily accessible archive
of these links. Keep in mind, these links are based on my personal preferences
and my observations.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Zero Hydra Failures filtering</title>
      <link>https://blog.erethon.com/log/2025-05-17-zhfail-ublock-origin-hack/</link>
      <pubDate>Fri, 16 May 2025 00:00:00 +0000</pubDate>
      
      <guid>https://blog.erethon.com/log/2025-05-17-zhfail-ublock-origin-hack/</guid>
      <description>I&amp;#39;ve been participating in the NixOS 25.05 Zero Hydra Failures event where people are encouraged to fix build failures in Nixpkgs. The website for the event is zh.fail (clever use of the fail tld!) and here&amp;#39;s the current list of all failing packages and tests.
I looked around in the website but I didn&amp;#39;t find any way to filter failures only for Linux or architecture (x86_64/aarch64). This feature was requested when the zh.</description>
    </item>
    
    <item>
      <title>TIL: Hugo&#39;s GitInfo</title>
      <link>https://blog.erethon.com/log/2025-03-03-hugo-git-info/</link>
      <pubDate>Mon, 03 Mar 2025 00:00:00 +0000</pubDate>
      
      <guid>https://blog.erethon.com/log/2025-03-03-hugo-git-info/</guid>
      <description>&lt;p&gt;
While catching up with my &lt;a href=&#34;https://github.com/Erethon/dotfiles/blob/main/.newsboat/urls&#34;&gt;RSS feed&lt;/a&gt;, I ran into this &lt;a href=&#34;https://fzakaria.com/2025/02/28/jekyll-git-commit&#34;&gt;post by Farid Zakaria&lt;/a&gt; which
describes how they automatically add the latest git commit hash to their
statically generated blog. This gave me the idea to do something similar on my
Hugo theme and blog, as I frequently look for a source link when reading other
people&amp;#39;s blogs.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>TIL: Zizmor and GitHub Actions security</title>
      <link>https://blog.erethon.com/log/2024-12-08-gha-security/</link>
      <pubDate>Fri, 13 Dec 2024 00:00:00 +0000</pubDate>
      
      <guid>https://blog.erethon.com/log/2024-12-08-gha-security/</guid>
      <description>I was reading up on the recent Ultralytics GitHub Action compromise and I stumbled upon this great analysis of the situation. In it, zizmor is introduced, which is a static analysis tool for GitHub Actions.
I experimented with it a bit and I have to say it&amp;#39;s working great. It correctly identified misconfigured GitHub Actions on some repositories I was working on. It&amp;#39;s another tool that&amp;#39;s worth having as part of your CI.</description>
    </item>
    
    <item>
      <title>/tmp is not a tmpfs on NixOS</title>
      <link>https://blog.erethon.com/log/2024-12-02-nixos-tmp/</link>
      <pubDate>Mon, 02 Dec 2024 00:00:00 +0000</pubDate>
      
      <guid>https://blog.erethon.com/log/2024-12-02-nixos-tmp/</guid>
      <description>The other day I realized that /tmp/ on my NixOS installations is not a tmpfs as I&amp;#39;m used to from other distros. Instead, NixOS relies on this systemd timer that cleans up old files from /tmp/. This is not NixOS specific, other systemd based distros also run this timer.
Looking at the NixOS boot.tmp related options, we see there&amp;#39;s an option (cleanOnBoot) that clears files on boot and is disabled by default.</description>
    </item>
    
  </channel>
</rss>
