<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Posts on Lyndon Sanche</title>
		<link>https://lyndeno.ca/posts/</link>
		<description>Recent content in Posts on Lyndon Sanche</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 16 Jan 2026 07:30:00 -0600</lastBuildDate>
		
			<atom:link href="https://lyndeno.ca/posts/feed.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Reproducable, flashable, updateable Raspberry Pi Images with NixOS</title>
				<link>https://lyndeno.ca/posts/2026/01-jan/2026-01-16-nixos-repart-image/</link>
				<pubDate>Fri, 16 Jan 2026 07:30:00 -0600</pubDate>
				<guid>https://lyndeno.ca/posts/2026/01-jan/2026-01-16-nixos-repart-image/</guid>
				<description>&lt;p&gt;A lot of my knowledge laid out here would not be possible without the insight&#xA;from&#xA;&lt;a href=&#34;https://nixcademy.com/posts/auto-growing-nixos-appliance-images-with-systemd-repart/&#34;&gt;Nixcademy&lt;/a&gt;&#xA;and their blog series on NixOS images. Please check out the linked blog for more&#xA;information on this topic. The code in this article is heavily inspired by or&#xA;reused from that post.&lt;/p&gt;&#xA;&lt;p&gt;I hope to add a little more to this topic by showing how to achieve a UEFI-based&#xA;image for a Raspberry Pi. I also want to practice my technical writing skills&#xA;for this article.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Automating Your Resume with Github</title>
				<link>https://lyndeno.ca/posts/2021/04-apr/2021-04-24-online-presence-resume/</link>
				<pubDate>Sat, 24 Apr 2021 01:20:00 -0600</pubDate>
				<guid>https://lyndeno.ca/posts/2021/04-apr/2021-04-24-online-presence-resume/</guid>
				<description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;Making your resume easily available and up to date can be quite the task. The approach I have taken is to host my resume on Github.&#xA;Github has tools that make it easy to have links that always point to the latest version of a file, which is what we need for my approach.&lt;/p&gt;&#xA;&lt;p&gt;What this approach uses:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A repository for hosting the resume LaTeX &lt;strong&gt;code&lt;/strong&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Github actions for building the resume.&lt;/li&gt;&#xA;&lt;li&gt;Git tags to tell Github when to build and &amp;ldquo;release&amp;rdquo; the resume PDF.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The final result of this process is something that, when set up, can be operated completely from the Git command line. All you have to do is commit changes to your&#xA;resume repository, then create a tag when the resume is in a presentable state. A link can be put on your website that always points to the latest PDF.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Setting up External Monitor Brightness Controls on Arch Linux</title>
				<link>https://lyndeno.ca/posts/2020/10-oct/2020-10-29-setting-up-external-monitor-brightness/</link>
				<pubDate>Thu, 29 Oct 2020 16:30:00 -0600</pubDate>
				<guid>https://lyndeno.ca/posts/2020/10-oct/2020-10-29-setting-up-external-monitor-brightness/</guid>
				<description>&lt;p&gt;This will be the first technical post on my website. I will use this post to describe the process in setting up external brightness control in Sway on Arch Linux.&lt;/p&gt;&#xA;&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;Kernel 5.9 added improved I2C support to Navi 10 cards&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;, which include the Radeon RX 5600XT. Using I2C in combination with &lt;a href=&#34;https://www.archlinux.org/packages/community/x86_64/ddcutil/&#34;&gt;ddcutil&lt;/a&gt; can allow us to control an external monitors brightness using commands.&lt;/p&gt;&#xA;&lt;h2 id=&#34;using-ddcutil&#34;&gt;Using ddcutil&lt;/h2&gt;&#xA;&lt;h3 id=&#34;detecting-monitors&#34;&gt;Detecting Monitors&lt;/h3&gt;&#xA;&lt;p&gt;First we need to make sure that the &lt;code&gt;i2c-dev&lt;/code&gt; module is loaded into the system; In my case, it was loaded automatically. We now want to identify the monitors:&lt;/p&gt;</description>
			</item>
			<item>
				<title>New website live</title>
				<link>https://lyndeno.ca/posts/2020/09-sep/2020-09-10-new-website-launch/</link>
				<pubDate>Thu, 10 Sep 2020 13:25:00 -0600</pubDate>
				<guid>https://lyndeno.ca/posts/2020/09-sep/2020-09-10-new-website-launch/</guid>
				<description>&lt;p&gt;The new website design is now live. You should now be reading this at &lt;a href=&#34;https://lyndeno.ca&#34;&gt;lyndeno.ca&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Welcome to the new lyndeno.ca</title>
				<link>https://lyndeno.ca/posts/2020/09-sep/2020-09-08-new-website/</link>
				<pubDate>Tue, 08 Sep 2020 13:43:00 -0600</pubDate>
				<guid>https://lyndeno.ca/posts/2020/09-sep/2020-09-08-new-website/</guid>
				<description>&lt;h2 id=&#34;welcome-to-the-new-website&#34;&gt;Welcome to the new website&lt;/h2&gt;&#xA;&lt;p&gt;This website will eventually replace the old HTML/PHP based &lt;a href=&#34;https://lyndeno.ca&#34;&gt;lyndeno.ca&lt;/a&gt;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
