<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Init-Systems on Linux Café</title>
    <link>https://mrtomlinux.org/tags/init-systems/</link>
    <description>Recent content in Init-Systems on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 12 May 2026 11:53:13 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/init-systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Replacing Ubuntu&#39;s systemd with runit on my home server: what I learned</title>
      <link>https://mrtomlinux.org/post/2026-05-12-replacing-ubuntus-systemd-with-runit-on-my-ho/</link>
      <pubDate>Tue, 12 May 2026 11:53:13 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-12-replacing-ubuntus-systemd-with-runit-on-my-ho/</guid>
      <description>&lt;h2 id=&#34;introduction-to-replacing-systemd-with-runit&#34;&gt;Introduction to Replacing systemd with runit&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve always been drawn to exploring alternative init systems, and in 2025, I decided to ditch Ubuntu&amp;rsquo;s default systemd for runit on my home server. My goal was to simplify the boot process and gain more control over the services running on my server. In this article, I&amp;rsquo;ll walk you through my experience with replacing systemd with runit, including the challenges I faced and the lessons I learned.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
