<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>sysadmin &amp;mdash; LinuxPizza</title>
    <link>https://blogs.linux.pizza/tag:sysadmin</link>
    <description>Personal notes and occasional posts - 100% human, 0% AI generated</description>
    <pubDate>Wed, 15 Apr 2026 06:26:19 +0000</pubDate>
    <item>
      <title>Stop bloating your system - use chroot</title>
      <link>https://blogs.linux.pizza/stop-bloating-your-system-use-chroot</link>
      <description>&lt;![CDATA[Have you ever installed packages from third party repositories to later realize that it was not the best idea? No? Well - I have. &#xA;But from now on, I wont do it. And instead utilize chroot!&#xA;&#xA;In this section, we&#39;ll cover how you do it on your Debian-based system aswell as on Fedora.&#xA;&#xA;Install the package &#xA;apt update; apt install debootstrap&#xA;Or if you are on Fedora:&#xA;dnf install debootstrap&#xA;&#xA;Now, create a catalogue anywhere of your choosing, for example in /srv&#xA;mkdir /srv/chroot&#xA;&#xA;Great. Now depending on what you want. Perform any of the following:&#xA;debootstrap bullseye /srv/chroot http://ftp.us.debian.org/debian&#xA;debootstrap  jammy /srv/chroot http://archive.ubuntu.com/ubuntu&#xA;&#xA;You should see it pull down all the packages needed for the distro to start, and when it is complete - you can enter the chroot:&#xA;&#xA;chroot /srv/chroot&#xA;&#xA;That&#39;s it! Now you can install, test or compile your packages as usual.&#xA;&#xA;And when you are done, you can simply remove the catalogue and start fresh - if you want.&#xA;&#xA;Here is a quick demo of the actual process:&#xA;&#xA;asciicast&#xA;&#xA;#linux #chroot #sysadmin #debian #ubuntu #fedora ]]&gt;</description>
      <content:encoded><![CDATA[<h3 id="have-you-ever-installed-packages-from-third-party-repositories-to-later-realize-that-it-was-not-the-best-idea-no-well-i-have" id="have-you-ever-installed-packages-from-third-party-repositories-to-later-realize-that-it-was-not-the-best-idea-no-well-i-have">Have you ever installed packages from third party repositories to later realize that it was not the best idea? No? Well – I have.</h3>

<h4 id="but-from-now-on-i-wont-do-it-and-instead-utilize-chroot" id="but-from-now-on-i-wont-do-it-and-instead-utilize-chroot">But from now on, I wont do it. And instead utilize chroot!</h4>

<p>In this section, we&#39;ll cover how you do it on your Debian-based system aswell as on Fedora.</p>

<p>Install the package <code>debootstrap</code></p>

<pre><code>apt update; apt install debootstrap
</code></pre>

<p>Or if you are on Fedora:</p>

<pre><code>dnf install debootstrap
</code></pre>

<p>Now, create a catalogue anywhere of your choosing, for example in /srv</p>

<pre><code>mkdir /srv/chroot
</code></pre>

<p>Great. Now depending on what you want. Perform any of the following:</p>

<pre><code>debootstrap bullseye /srv/chroot http://ftp.us.debian.org/debian
</code></pre>

<pre><code>debootstrap  jammy /srv/chroot http://archive.ubuntu.com/ubuntu
</code></pre>

<p>You should see it pull down all the packages needed for the distro to start, and when it is complete – you can enter the chroot:</p>

<pre><code>chroot /srv/chroot
</code></pre>

<p>That&#39;s it! Now you can install, test or compile your packages as usual.</p>

<p>And when you are done, you can simply remove the catalogue and start fresh – if you want.</p>

<p>Here is a quick demo of the actual process:</p>

<p><a href="https://asciinema.org/a/yfFz8qvnlQecQOZXIXjgIL593"><img src="https://asciinema.org/a/yfFz8qvnlQecQOZXIXjgIL593.svg" alt="asciicast"></a></p>

<p><a href="https://blogs.linux.pizza/tag:linux" class="hashtag"><span>#</span><span class="p-category">linux</span></a> <a href="https://blogs.linux.pizza/tag:chroot" class="hashtag"><span>#</span><span class="p-category">chroot</span></a> <a href="https://blogs.linux.pizza/tag:sysadmin" class="hashtag"><span>#</span><span class="p-category">sysadmin</span></a> <a href="https://blogs.linux.pizza/tag:debian" class="hashtag"><span>#</span><span class="p-category">debian</span></a> <a href="https://blogs.linux.pizza/tag:ubuntu" class="hashtag"><span>#</span><span class="p-category">ubuntu</span></a> <a href="https://blogs.linux.pizza/tag:fedora" class="hashtag"><span>#</span><span class="p-category">fedora</span></a></p>
]]></content:encoded>
      <guid>https://blogs.linux.pizza/stop-bloating-your-system-use-chroot</guid>
      <pubDate>Tue, 22 Nov 2022 17:51:14 +0000</pubDate>
    </item>
    <item>
      <title>Postfix - relay emails via a another mailserver with authentication and submission enabled</title>
      <link>https://blogs.linux.pizza/postfix-relay-emails-via-a-another-mailserver-with-authentication-and</link>
      <description>&lt;![CDATA[This short writeup will guide you on how to do it on Debian-based and Fedora systems.&#xA;&#xA;We begin with installing posfix and the required packages for authentication.&#xA;&#xA;First - doublecheck that your machine has a Fully Qualified Domain Name set in the hostfile, this will remove alot of headaches from you in the future.&#xA;&#xA;My machine is named &#34;T15.domain.tld&#34; - so emails will be arriving from &#34;user@T15.domain.tld&#34;.&#xA;&#xA;Debian:&#xA;apt-get install postfix mailutils libsasl2-2 libsasl2-modules&#xA;Fedora:&#xA;dnf install postfix mailx mailx cyrus-sasl cyrus-sasl-plain&#xA;Next, we will create the sasl-password file and hash it:&#xA;echo &#34;[relay.domain.tld]:587 username:password&#34;   /etc/postfix/sasl&#xA;postmap /etc/postfix/sasl&#xA;Great, now we have to tell postfix that all emails sent via it should be relayed throu the smtp-relay:&#xA;relayhost = [relay.domain.tld]:587&#xA;smtpusetls = yes&#xA;smtpsaslauthenable = yes&#xA;smtpsaslsecurityoptions =&#xA;smtpsaslpasswordmaps = hash:/etc/postfix/sasl&#xA;smtptlsCAfile = /etc/ssl/certs/ca-certificates.crt&#xA;Restart postfix and check the log, so everything looks good.&#xA;&#xA;Test your setup:&#xA;echo &#34;This is a test&#34; | mail -s &#34;Just a test&#34; destinationemail@domain.tld&#xA;You can check the status of the mailqueue with the command &#xA;And that&#39;s about it!&#xA;&#xA;#linux #postfix #smtp #sysadmin #email]]&gt;</description>
      <content:encoded><![CDATA[<h4 id="this-short-writeup-will-guide-you-on-how-to-do-it-on-debian-based-and-fedora-systems" id="this-short-writeup-will-guide-you-on-how-to-do-it-on-debian-based-and-fedora-systems">This short writeup will guide you on how to do it on Debian-based and Fedora systems.</h4>

<p>We begin with installing posfix and the required packages for authentication.</p>

<p>First – doublecheck that your machine has a Fully Qualified Domain Name set in the hostfile, this will remove alot of headaches from you in the future.</p>

<p>My machine is named “T15.domain.tld” – so emails will be arriving from “user@T15.domain.tld”.</p>

<p>Debian:</p>

<pre><code>apt-get install postfix mailutils libsasl2-2 libsasl2-modules
</code></pre>

<p>Fedora:</p>

<pre><code>dnf install postfix mailx mailx cyrus-sasl cyrus-sasl-plain
</code></pre>

<p>Next, we will create the sasl-password file and hash it:</p>

<pre><code>echo &#34;[relay.domain.tld]:587 username:password&#34; &gt; /etc/postfix/sasl
postmap /etc/postfix/sasl
</code></pre>

<p>Great, now we have to tell postfix that all emails sent via it should be relayed throu the smtp-relay:</p>

<pre><code>relayhost = [relay.domain.tld]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_sasl_password_maps = hash:/etc/postfix/sasl
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
</code></pre>

<p>Restart postfix and check the log, so everything looks good.</p>

<p>Test your setup:</p>

<pre><code>echo &#34;This is a test&#34; | mail -s &#34;Just a test&#34; destination_email@domain.tld
</code></pre>

<p>You can check the status of the mailqueue with the command <code>mailq</code>.</p>

<p>And that&#39;s about it!</p>

<p><a href="https://blogs.linux.pizza/tag:linux" class="hashtag"><span>#</span><span class="p-category">linux</span></a> <a href="https://blogs.linux.pizza/tag:postfix" class="hashtag"><span>#</span><span class="p-category">postfix</span></a> <a href="https://blogs.linux.pizza/tag:smtp" class="hashtag"><span>#</span><span class="p-category">smtp</span></a> <a href="https://blogs.linux.pizza/tag:sysadmin" class="hashtag"><span>#</span><span class="p-category">sysadmin</span></a> <a href="https://blogs.linux.pizza/tag:email" class="hashtag"><span>#</span><span class="p-category">email</span></a></p>
]]></content:encoded>
      <guid>https://blogs.linux.pizza/postfix-relay-emails-via-a-another-mailserver-with-authentication-and</guid>
      <pubDate>Sat, 10 Sep 2022 18:41:49 +0000</pubDate>
    </item>
  </channel>
</rss>