<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Notes on WhyNotHugo</title><link>https://whynothugo.nl/tags/notes/</link><description>Recent content in Notes on WhyNotHugo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 25 Mar 2024 10:42:23 +0100</lastBuildDate><atom:link href="https://whynothugo.nl/tags/notes/posts.xml" rel="self" type="application/rss+xml"/><item><title>Notes on s6</title><link>https://whynothugo.nl/journal/2024/03/25/notes-on-s6/</link><pubDate>Mon, 25 Mar 2024 10:26:41 +0100</pubDate><guid>https://whynothugo.nl/journal/2024/03/25/notes-on-s6/</guid><description>s6 is a collection of programs that can be used for service supervision and service management. It is composed of multiple simple tools that can be used individually or together.
The s6 suite of programs can be used to supervise and manage system service, user-session service, or just ad-hoc collection of services.
The official documentation does a good job of explaining every component in great details. This is merely a high level overview.</description></item><item><title>Notes on Podman</title><link>https://whynothugo.nl/journal/2023/03/15/notes-on-podman/</link><pubDate>Wed, 15 Mar 2023 11:21:05 +0100</pubDate><guid>https://whynothugo.nl/journal/2023/03/15/notes-on-podman/</guid><description>Podman is an alternative implementation of Docker which addresses some design issues in Docker. The most obvious/notable difference is that Podman doesn&amp;rsquo;t require a daemon running permanently, which is nice, but not a huge deal. It also has other design differences, but most of them are good ideas that have little to no impact in practice.
A big feature of Podman was that it was the first to implement rootless support.</description></item><item><title>Using a Yubikey for both GPG and TOTP</title><link>https://whynothugo.nl/journal/2023/03/13/using-a-yubikey-for-both-gpg-and-totp/</link><pubDate>Mon, 13 Mar 2023 18:39:00 +0100</pubDate><guid>https://whynothugo.nl/journal/2023/03/13/using-a-yubikey-for-both-gpg-and-totp/</guid><description>I&amp;rsquo;ve written before on how I use a Yubikey for hardware-based GPG and 2FA on the web. I also use it for TOTP. That is, the Yubikey itself generates those common &amp;ldquo;authenticator codes&amp;rdquo; like many other Authenticator apps. But the secret seed is saved into hardware that does not support revealing it, instead of being handled by a regular app on a network-connected device.
A nasty issue I&amp;rsquo;ve been dealing with is that when I signed something using GPG, the key would no longer work for TOTP unless I killed the gpg-agent.</description></item><item><title>OpenWrt with KPN fibre optics</title><link>https://whynothugo.nl/journal/2023/02/11/openwrt-with-kpn-fibre-optics/</link><pubDate>Sat, 11 Feb 2023 00:00:00 +0000</pubDate><guid>https://whynothugo.nl/journal/2023/02/11/openwrt-with-kpn-fibre-optics/</guid><description>I&amp;rsquo;ve always preferred to use my own router at home when possible, and was pleasantly surprised to learn that the EU actually has rules around router freedom. That is, each user is allowed to use their own hardware at home, rather than being imposed which hardware they can use by their service provider.
Additionally, the Netherlands has local legislation to reflect this, and KPN has a dedicated page explaining that they support this too.</description></item><item><title>Setting up IRC redirects</title><link>https://whynothugo.nl/journal/2023/01/20/setting-up-irc-redirects/</link><pubDate>Fri, 20 Jan 2023 11:39:00 +0100</pubDate><guid>https://whynothugo.nl/journal/2023/01/20/setting-up-irc-redirects/</guid><description>Updated 2023-10-23: The +i mode was added. See below for details.
A few weeks ago I wanted to set up a few redirects on IRC. Mainly, I wanted to redirect #vdirsyncer, #khal and #todoman to the #pimutils channel (given that pimutils is the umbrella project for both of these).
These are the commands I had to run after authenticating:
/msg ChanServ register #todoman /msg ChanServ set #todoman mlock +if #pimutils /msg ChanServ set #todoman guard on /msg ChanServ register #vdirsyncer /msg ChanServ set #vdirsyncer mlock +if #pimutils /msg ChanServ set #vdirsyncer guard on /msg ChanServ register #khal /msg ChanServ set #khal mlock +if #pimutils /msg ChanServ set #khal guard on Reference[permalink] mlock locks the mode to the specified one guard will retain the channel even if everyone leaves.</description></item><item><title>Quick and simple VMs with qemu</title><link>https://whynothugo.nl/journal/2022/07/01/quick-and-simple-vms-with-qemu/</link><pubDate>Fri, 01 Jul 2022 00:00:00 +0000</pubDate><guid>https://whynothugo.nl/journal/2022/07/01/quick-and-simple-vms-with-qemu/</guid><description>I don&amp;rsquo;t use VMs very often, so there&amp;rsquo;s no chance I can remember all the dozens of command line flags for qemu.
I end up using virt-manager most of the time. It&amp;rsquo;s a GUI for managing QEMU (and other VM backends) and has dozens of checkboxes and buttons, which come in handy for really complex virtual hardware configurations where I&amp;rsquo;d need to know a dozen obscure command line flags to replicate the same results.</description></item></channel></rss>