<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Armhf on tech.notes</title>
    <link>https://newblog.utzer.de/tags/armhf/</link>
    <description>Recent content in Armhf on tech.notes</description>
    <generator>Hugo</generator>
    <language>de</language>
    <lastBuildDate>Thu, 11 May 2023 13:07:58 +0000</lastBuildDate>
    <atom:link href="https://newblog.utzer.de/tags/armhf/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Upgrade Raspberry Pi OS from Buster to Bullseye</title>
      <link>https://newblog.utzer.de/2023/05/11/upgrade-raspberry-pi-raspbian-from-buster-to-bullseye/</link>
      <pubDate>Thu, 11 May 2023 13:07:58 +0000</pubDate>
       <guid isPermaLink="false">https://tech.utzer.de/?p=131</guid> 
      <description>&lt;p&gt;So to upgrade Raspbian, as it was previously called, from Buster to Bullseye went smooth an easy, I tried this with some Pi2B (armhf 32Bit) and with a Pi4. These two are headless systems, so I don&amp;rsquo;t know if this works well for any systems with window managers.&lt;/p&gt;
&lt;p&gt;Better run these commands in screen, so when the SSH connection is interrupted you can reconnect and resume your work.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Edit: For the update there is a culprit, it will cause a problem with dhcpd, so before the reboot 13. (was point 12. before I added the remark below) please &lt;a href=&#34;https://newblog.utzer.de/?p=141&#34;&gt;check this post&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
