<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dzu's Blog (Einträge über systemd)</title><link>https://blog.lazy-evaluation.net/</link><description></description><atom:link href="https://blog.lazy-evaluation.net/de/categories/systemd.xml" rel="self" type="application/rss+xml"></atom:link><language>de</language><copyright>Contents © 2025 &lt;a href="mailto:dzu@member.fsf.org"&gt;Detlev Zundel&lt;/a&gt; </copyright><lastBuildDate>Sat, 08 Mar 2025 11:07:56 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Switching to maildir in Debian Bullseye</title><link>https://blog.lazy-evaluation.net/de/posts/linux/debian-maildir.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="org21f3d6e"&gt;

&lt;div id="org3c25c04" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/maildir.png" alt="maildir.png" title="GnuPG logo" align="middle" width="150"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;
Although e-mail has lost some of its importance by the advent of
secure messaging platforms like &lt;a href="https://www.signal.org/de/"&gt;Signal&lt;/a&gt;, from time to time I still get
the itch to improve my existing setup.  Recently I wondered why I am
still using a single file &lt;a href="https://en.wikipedia.org/wiki/Mbox"&gt;mbox&lt;/a&gt; instead of the more Unixy &lt;a href="https://de.wikipedia.org/wiki/Maildir"&gt;maildir&lt;/a&gt;
format on my Debian desktop and how difficult it would to be
switch. As we will see, the transition is pretty straight forward.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/debian-maildir.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (3 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/debian-maildir.html</guid><pubDate>Fri, 22 Oct 2021 21:23:27 GMT</pubDate></item><item><title>Wake-on-lan</title><link>https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;After upgrading my main desktop machine from Debian Jessie to Stretch,
I wondered if my current solution to enable wake-on-lan on that
machine could be replaced with something prepared in one of the
upstream packages.&lt;/p&gt;
&lt;img alt="Wake-On-Lan" class="align-center" src="https://blog.lazy-evaluation.net/images/wol.png" style="width: 200px;"&gt;
&lt;p&gt;The old (but in my opinion still very elegant) solution consisted of a
systemd template contained in &lt;code class="docutils literal"&gt;&lt;span class="pre"&gt;/etc/systemd/system/wol@.service&lt;/span&gt;&lt;/code&gt;:&lt;/p&gt;
&lt;div class="code"&gt;&lt;pre class="code ini"&gt;&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-1" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-1" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-1"&gt;&lt;/a&gt;&lt;span class="k"&gt;[Unit]&lt;/span&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-2" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-2" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-2"&gt;&lt;/a&gt;&lt;span class="na"&gt;Description&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;Wake-on-LAN for %i&lt;/span&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-3" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-3" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-3"&gt;&lt;/a&gt;&lt;span class="na"&gt;Requires&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;network.target&lt;/span&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-4" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-4" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-4"&gt;&lt;/a&gt;&lt;span class="na"&gt;After&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;network.target&lt;/span&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-5" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-5" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-5"&gt;&lt;/a&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-6" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-6" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-6"&gt;&lt;/a&gt;&lt;span class="k"&gt;[Service]&lt;/span&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-7" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-7" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-7"&gt;&lt;/a&gt;&lt;span class="na"&gt;ExecStart&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;/sbin/ethtool -s %i wol g&lt;/span&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-8" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-8" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-8"&gt;&lt;/a&gt;&lt;span class="na"&gt;Type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;oneshot&lt;/span&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-9" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-9" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-9"&gt;&lt;/a&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-10" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-10" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-10"&gt;&lt;/a&gt;&lt;span class="k"&gt;[Install]&lt;/span&gt;
&lt;a id="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-11" name="rest_code_21bc8cf877a045388ce5f8eddb5c02bc-11" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_21bc8cf877a045388ce5f8eddb5c02bc-11"&gt;&lt;/a&gt;&lt;span class="na"&gt;WantedBy&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;multi-user.target&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;With this in place, all that is needed to enable wake-on-lan for eth0
is a simple:&lt;/p&gt;
&lt;div class="code"&gt;&lt;pre class="code console"&gt;&lt;a id="rest_code_a66d051a5ff1405aa83d6bd7e5b97eb8-1" name="rest_code_a66d051a5ff1405aa83d6bd7e5b97eb8-1" href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html#rest_code_a66d051a5ff1405aa83d6bd7e5b97eb8-1"&gt;&lt;/a&gt;&lt;span class="gp"&gt;root@deepthought:~# &lt;/span&gt;systemctl&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nb"&gt;enable&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;wol@eth0.service
&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (2 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/wake-on-lan.html</guid><pubDate>Fri, 28 Apr 2017 20:24:18 GMT</pubDate></item><item><title>Entering Recovery Mode in Ubuntu 16.04 LTS</title><link>https://blog.lazy-evaluation.net/de/posts/linux/ubuntu-16-04-entering-recovery.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;As described in my post &lt;a class="reference external" href="https://blog.lazy-evaluation.net/posts/linux/ubuntu-16-04-broken-recovery.html"&gt;Broken Recovery Mode in Ubuntu 16.04 LTS&lt;/a&gt;, it is
currently not possible to use the rescue mode provided by Ubuntu in
the 16.04 LTS version.  Although the bug was confirmed, there is no
visible activity to fix the problem.  Should you still need to use
rescue mode, it is straightforward to enter it manually by way of
providing the correct systemd parameter on the Linux command line.&lt;/p&gt;
&lt;img alt="Preparing for Recovery Mode" class="align-center" src="https://blog.lazy-evaluation.net/images/ubuntu-16-04-manual-recovery.png" style="width: 400px;"&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/ubuntu-16-04-entering-recovery.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (1 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/ubuntu-16-04-entering-recovery.html</guid><pubDate>Mon, 13 Feb 2017 08:16:00 GMT</pubDate></item><item><title>Broken Recovery Mode in Ubuntu 16.04 LTS</title><link>https://blog.lazy-evaluation.net/de/posts/linux/ubuntu-16-04-broken-recovery.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;Ubuntu 16.04 LTS is the first long term Ubuntu version using systemd
as the init process.  Unfortunately the switch from upstart to systemd
broke the recovery mode that comes in handy in a number of situations.&lt;/p&gt;
&lt;img alt="Recovery Mode" class="align-center" src="https://blog.lazy-evaluation.net/images/ubuntu-16-04-recovery.png" style="width: 400px;"&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/ubuntu-16-04-broken-recovery.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (3 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/ubuntu-16-04-broken-recovery.html</guid><pubDate>Mon, 06 Feb 2017 17:51:00 GMT</pubDate></item></channel></rss>