<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Heads Up! &#8211; DragonFly BSD Digest</title>
	<atom:link href="https://www.dragonflydigest.com/category/heads-up/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Wed, 11 Nov 2026 02:56:15 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://www.dragonflydigest.com/wp-content/uploads/2016/12/FullLogoSquare-150x150.gif</url>
	<title>Heads Up! &#8211; DragonFly BSD Digest</title>
	<link>https://www.dragonflydigest.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Major package upgrade for DragonFly</title>
		<link>https://www.dragonflydigest.com/2026/11/10/major-package-upgrade-for-dragonfly/</link>
					<comments>https://www.dragonflydigest.com/2026/11/10/major-package-upgrade-for-dragonfly/#respond</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 02:56:15 +0000</pubDate>
				<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=30169</guid>

					<description><![CDATA[There&#8217;s a set of port/package updates out for both DragonFly 6.4 and DragonFly-current.  It pulls from ports as of 2026Q4, so it&#8217;s a significant update even without the PHP upgrade you may be waiting for. I was able to update this server without problems.  The only manual step I had was reinitializing Postgres because the &#8230; <p class="link-more"><a href="https://www.dragonflydigest.com/2026/11/10/major-package-upgrade-for-dragonfly/" class="more-link">Continue reading<span class="screen-reader-text"> "Major package upgrade for DragonFly"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>There&#8217;s a set of port/package updates out for both DragonFly 6.4 and DragonFly-current.  It pulls from ports as of 2026Q4, so it&#8217;s a significant update even without the PHP upgrade you may be waiting for.</p>
<p>I was able to update this server without problems.  The only manual step I had was reinitializing Postgres because the major version changed.  <a href="https://lists.dragonflybsd.org/pipermail/users/2026-November/452649.html">The announcement has the details</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2026/11/10/major-package-upgrade-for-dragonfly/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>PHP and DragonFly</title>
		<link>https://www.dragonflydigest.com/2026/11/03/php-and-dragonfly/</link>
					<comments>https://www.dragonflydigest.com/2026/11/03/php-and-dragonfly/#respond</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Tue, 03 Nov 2026 21:39:25 +0000</pubDate>
				<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Goings-on]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=30143</guid>

					<description><![CDATA[Are you running PHP on DragonFly and waiting for an update to avoid PHP2Shell?  A new package build is on the way.  A side effect is that it means a 6.6 release soon after that, too. The other side effect of all this is that I think I need more tools that don&#8217;t use PHP.]]></description>
										<content:encoded><![CDATA[<p>Are you running PHP on DragonFly and waiting for an update to avoid PHP2Shell?  <a href="https://lists.dragonflybsd.org/pipermail/users/2026-November/452648.html">A new package build is on the way</a>.  A side effect is that it means a 6.6 release soon after that, too.</p>
<p>The other side effect of all this is that I think I need more tools that <em>don&#8217;t</em> use PHP.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2026/11/03/php-and-dragonfly/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>dm_target_crypt change in DragonFly</title>
		<link>https://www.dragonflydigest.com/2025/08/07/dm_target_crypt-change-in-dragonfly/</link>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Fri, 08 Aug 2025 00:22:44 +0000</pubDate>
				<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Goings-on]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=29309</guid>

					<description><![CDATA[Are you encrypting your disk in DragonFly?  If you are using dm_target_crypt, the &#8216;ng&#8217; version is now the default.  You may want to change your loader.conf.]]></description>
										<content:encoded><![CDATA[<p>Are you encrypting your disk in DragonFly?  If you are using dm_target_crypt, <a href="https://lists.dragonflybsd.org/pipermail/commits/2025-July/923582.html">the &#8216;ng&#8217; version is now the default</a>.  You may want to change your loader.conf.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>DragonFly 6.4.1 released</title>
		<link>https://www.dragonflydigest.com/2025/04/30/dragonfly-6-4-1-released/</link>
					<comments>https://www.dragonflydigest.com/2025/04/30/dragonfly-6-4-1-released/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Wed, 30 Apr 2025 14:14:25 +0000</pubDate>
				<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Goings-on]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=29097</guid>

					<description><![CDATA[6.4.1, a bugfix upgrade to 6.4, is ready to download.  The commit log from 6.4.0 to 6.4.1 is available if you want the details.]]></description>
										<content:encoded><![CDATA[<p>6.4.1, a bugfix upgrade to 6.4, is <a href="https://www.dragonflybsd.org/release64/">ready to download</a>.  The <a href="https://gitweb.dragonflybsd.org/dragonfly.git/log/refs/tags/v6.4.1">commit log from 6.4.0 to 6.4.1 is available</a> if you want the details.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2025/04/30/dragonfly-6-4-1-released/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Behavior change for skip in pf</title>
		<link>https://www.dragonflydigest.com/2022/05/25/behavior-change-for-skip-in-pf/</link>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Wed, 25 May 2022 15:41:27 +0000</pubDate>
				<category><![CDATA[Committed Code]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<category><![CDATA[pf]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=26991</guid>

					<description><![CDATA[If you are using &#8216;set skip on &#8230;&#8217; in your pf config, it used to match any interface that matched the specified type.  It now only matches members of that named group.  That may change behavior of your pf rules; check the commit to see what to look for.]]></description>
										<content:encoded><![CDATA[<p>If you are using &#8216;set skip on &#8230;&#8217; in your pf config, it used to match any interface that matched the specified type.  It now only matches members of that named group.  That may change behavior of your pf rules; <a href="https://lists.dragonflybsd.org/pipermail/commits/2022-April/820913.html">check the commit</a> to see what to look for.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>New 2021Q4 binary packages</title>
		<link>https://www.dragonflydigest.com/2021/12/03/new-2021q4-binary-packages/</link>
					<comments>https://www.dragonflydigest.com/2021/12/03/new-2021q4-binary-packages/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Fri, 03 Dec 2021 15:53:56 +0000</pubDate>
				<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=26426</guid>

					<description><![CDATA[There&#8217;s a new build of binary packages for DragonFly, based off the 2021Q4 quarterly ports release.  This will require an upgrade of most if not all packages cause of a switch from LibreSSL to OpenSSL as the default SSL library.]]></description>
										<content:encoded><![CDATA[<p>There&#8217;s <a href="https://lists.dragonflybsd.org/pipermail/users/2021-December/404872.html">a new build of binary packages for DragonFly</a>, based off the 2021Q4 quarterly ports release.  This will require an upgrade of most if not all packages cause of a switch from LibreSSL to OpenSSL as the default SSL library.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2021/12/03/new-2021q4-binary-packages/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Let&#8217;s Encrypt cert problem fixed</title>
		<link>https://www.dragonflydigest.com/2021/10/05/lets-encrypt-cert-problem-fixed/</link>
					<comments>https://www.dragonflydigest.com/2021/10/05/lets-encrypt-cert-problem-fixed/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Tue, 05 Oct 2021 22:50:17 +0000</pubDate>
				<category><![CDATA[Committed Code]]></category>
		<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=26236</guid>

					<description><![CDATA[If you have encountered that problem with Let&#8217;s Encrypt and dports, the fix is committed and a make world is needed.]]></description>
										<content:encoded><![CDATA[<p>If you have encountered that problem with Let&#8217;s Encrypt and dports, the fix is committed and <a href="https://lists.dragonflybsd.org/pipermail/users/2021-October/404826.html">a make world is needed</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2021/10/05/lets-encrypt-cert-problem-fixed/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Let&#8217;s Encrypt certs and pkg</title>
		<link>https://www.dragonflydigest.com/2021/09/30/lets-encrypt-certs-and-pkg/</link>
					<comments>https://www.dragonflydigest.com/2021/09/30/lets-encrypt-certs-and-pkg/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Fri, 01 Oct 2021 01:42:00 +0000</pubDate>
				<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=26229</guid>

					<description><![CDATA[You may get some errors because of an expiring base Let&#8217;s Encrypt certificate when using pkg.  It&#8217;s being worked on.]]></description>
										<content:encoded><![CDATA[<p>You may get some errors because of an expiring base Let&#8217;s Encrypt certificate when using pkg.  <a href="https://lists.dragonflybsd.org/pipermail/users/2021-September/404825.html">It&#8217;s being worked on</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2021/09/30/lets-encrypt-certs-and-pkg/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>tmux port redo</title>
		<link>https://www.dragonflydigest.com/2021/09/02/tmux-port-redo/</link>
					<comments>https://www.dragonflydigest.com/2021/09/02/tmux-port-redo/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Thu, 02 Sep 2021 12:48:42 +0000</pubDate>
				<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=26141</guid>

					<description><![CDATA[If you&#8217;re upgrading to the latest dports, and you use tmux &#8211; don&#8217;t update that particular port yet.]]></description>
										<content:encoded><![CDATA[<p>If you&#8217;re upgrading to the latest dports, and you use tmux &#8211; <a href="https://lists.dragonflybsd.org/pipermail/users/2021-September/404815.html">don&#8217;t update that particular port yet</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2021/09/02/tmux-port-redo/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>DragonFly and 6.x packages</title>
		<link>https://www.dragonflydigest.com/2021/04/23/dragonfly-and-6-x-packages/</link>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Sat, 24 Apr 2021 02:09:56 +0000</pubDate>
				<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=25674</guid>

					<description><![CDATA[Since DragonFly 6.x is a major number change, there&#8217;s no prebuilt packages that match that release number.  As of this writing, the mirror master site shows 5.10 packages, which would work&#8230; if that was the next release.  That&#8217;s where the number change trips it up.  There should be new 6.x packages in the next few &#8230; <p class="link-more"><a href="https://www.dragonflydigest.com/2021/04/23/dragonfly-and-6-x-packages/" class="more-link">Continue reading<span class="screen-reader-text"> "DragonFly and 6.x packages"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>Since DragonFly 6.x is a major number change, there&#8217;s no prebuilt packages that match that release number.  As of this writing, the mirror master site shows 5.10 packages, which would work&#8230; if that was the next release.  That&#8217;s where the number change trips it up.  There should be new 6.x packages in the next few days.  (Thanks to Jan Peter Vogt for the reminder)</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>One more building fix</title>
		<link>https://www.dragonflydigest.com/2021/02/19/one-more-building-fix/</link>
					<comments>https://www.dragonflydigest.com/2021/02/19/one-more-building-fix/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Fri, 19 Feb 2021 18:05:02 +0000</pubDate>
				<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Goings-on]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=25460</guid>

					<description><![CDATA[Because there&#8217;s a newer version of sh(1) in DragonFly, you may need to update your 5.8 system to continue building ports from source.  Binary installation through pkg still works as expected so this may not affect you.]]></description>
										<content:encoded><![CDATA[<p>Because there&#8217;s <a href="http://lists.dragonflybsd.org/pipermail/commits/2021-February/770230.html">a newer version of sh(1) in DragonFly</a>, you may need to <a href="http://lists.dragonflybsd.org/pipermail/users/2021-February/381558.html">update your 5.8 system</a> to continue building ports from source.  Binary installation through pkg still works as expected so this may not affect you.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2021/02/19/one-more-building-fix/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
			</item>
		<item>
		<title>Signal safety in DragonFly</title>
		<link>https://www.dragonflydigest.com/2019/11/19/signal-safety-in-dragonfly/</link>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Tue, 19 Nov 2019 16:08:42 +0000</pubDate>
				<category><![CDATA[Committed Code]]></category>
		<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=23786</guid>

					<description><![CDATA[Some of the larger application sets on DragonFly have had trouble building, and inconsistent problems with that build.  i.e. rust would fail, but in different parts of the build process, every time.  It looks to be a problem with signal interaction, and there&#8217;s now much safer ways to do that on DragonFly. That is going &#8230; <p class="link-more"><a href="https://www.dragonflydigest.com/2019/11/19/signal-safety-in-dragonfly/" class="more-link">Continue reading<span class="screen-reader-text"> "Signal safety in DragonFly"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>Some of the larger application sets on DragonFly have had trouble building, and inconsistent problems with that build.  i.e. rust would fail, but in different parts of the build process, every time.  It looks to be a problem with signal interaction, and there&#8217;s now <a href="http://lists.dragonflybsd.org/pipermail/users/2019-November/358305.html">much safer ways to do that on DragonFly</a>.</p>
<p>That is going to <a href="http://lists.dragonflybsd.org/pipermail/users/2019-November/358306.html">require a full buildworld/buildkernel</a> if you are on DragonFly-master, 5.7.  Release/5.6 users are unaffected.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Keep rebuilding</title>
		<link>https://www.dragonflydigest.com/2019/09/13/keep-rebuilding/</link>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Fri, 13 Sep 2019 17:04:56 +0000</pubDate>
				<category><![CDATA[Committed Code]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=23485</guid>

					<description><![CDATA[ABI breakage continues, so continue the full buildworld/buildkernel cycle, if you are on DragonFly-current, and continue to ignore it, if you are on 5.6. Update: yeah aim for next week.]]></description>
										<content:encoded><![CDATA[<p><a href="http://lists.dragonflybsd.org/pipermail/commits/2019-September/719531.html">ABI breakage continues</a>, so continue <a href="https://www.dragonflydigest.com/2019/09/11/23477.html">the full buildworld/buildkernel cycle</a>, if you are on DragonFly-current, and continue to ignore it, if you are on 5.6.</p>
<p>Update: <a href="http://lists.dragonflybsd.org/pipermail/users/2019-September/358281.html">yeah aim for next week</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>ABI breakage in DragonFly master</title>
		<link>https://www.dragonflydigest.com/2019/09/11/abi-breakage-in-dragonfly-master/</link>
					<comments>https://www.dragonflydigest.com/2019/09/11/abi-breakage-in-dragonfly-master/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Wed, 11 Sep 2019 22:45:36 +0000</pubDate>
				<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Goings-on]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=23477</guid>

					<description><![CDATA[There&#8217;s commits being made in DragonFly that will break binary compatibility.  If you are running DragonFly-master, that means you will need to do a full buildworld/buildkernel when updating, and you will either have to rebuild packages or wait some days until a new set are built. If you are running the 5.6 release, you are &#8230; <p class="link-more"><a href="https://www.dragonflydigest.com/2019/09/11/abi-breakage-in-dragonfly-master/" class="more-link">Continue reading<span class="screen-reader-text"> "ABI breakage in DragonFly master"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>There&#8217;s <a href="http://lists.dragonflybsd.org/pipermail/users/2019-September/358280.html">commits being made in DragonFly that will break binary compatibility</a>.  If you are running DragonFly-master, that means you will need to do a full buildworld/buildkernel when updating, and you will either have to rebuild packages or wait some days until a new set are built.</p>
<p>If you are running the 5.6 release, you are unaffected.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2019/09/11/abi-breakage-in-dragonfly-master/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>tcp keepalive and dports on DragonFly</title>
		<link>https://www.dragonflydigest.com/2019/07/15/tcp-keepalive-and-dports-on-dragonfly/</link>
					<comments>https://www.dragonflydigest.com/2019/07/15/tcp-keepalive-and-dports-on-dragonfly/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Mon, 15 Jul 2019 19:52:48 +0000</pubDate>
				<category><![CDATA[Committed Code]]></category>
		<category><![CDATA[DPorts]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=23199</guid>

					<description><![CDATA[DragonFly&#8217;s tcp keepalive was changed from milliseconds to seconds.  This happened in both DragonFly-current and in the 5.6 release, and it changes the networking API, which means a dports rebuild is needed&#8230; or a pkg upgrade, for which happily all packages have been rebuilt.  So, on your next update of the system, be sure to &#8230; <p class="link-more"><a href="https://www.dragonflydigest.com/2019/07/15/tcp-keepalive-and-dports-on-dragonfly/" class="more-link">Continue reading<span class="screen-reader-text"> "tcp keepalive and dports on DragonFly"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>DragonFly&#8217;s tcp keepalive <a href="http://lists.dragonflybsd.org/pipermail/commits/2019-July/719125.html">was</a> <a href="http://lists.dragonflybsd.org/pipermail/commits/2019-July/719126.html">changed</a> from milliseconds to seconds.  This happened in both DragonFly-current and in the 5.6 release, and it changes the networking API, which means a dports rebuild is needed&#8230; or a pkg upgrade, for which happily all packages <a href="http://lists.dragonflybsd.org/pipermail/users/2019-July/358225.html">have been rebuilt</a>.  So, on your next update of the system, be sure to update packages too.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2019/07/15/tcp-keepalive-and-dports-on-dragonfly/feed/</wfw:commentRss>
			<slash:comments>6</slash:comments>
		
		
			</item>
		<item>
		<title>TCP keepalive change in DragonFly kernel</title>
		<link>https://www.dragonflydigest.com/2019/06/26/tcp-keepalive-change-in-dragonfly-kernel/</link>
					<comments>https://www.dragonflydigest.com/2019/06/26/tcp-keepalive-change-in-dragonfly-kernel/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Wed, 26 Jun 2019 20:23:38 +0000</pubDate>
				<category><![CDATA[Committed Code]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=23120</guid>

					<description><![CDATA[Matthew Dillon&#8217;s made a change to the DragonFly kernel that could be disruptive, but will help make sure chromium runs.  If you update after this point, make sure to update your dports, too, just to be sure everything is in sync.  This applies to 5.6 and 5.7.]]></description>
										<content:encoded><![CDATA[<p>Matthew Dillon&#8217;s <a href="http://lists.dragonflybsd.org/pipermail/users/2019-June/358214.html">made a change to the DragonFly kernel</a> that<a href="http://lists.dragonflybsd.org/pipermail/commits/2019-June/719082.html"> could be disruptive</a>, but will help make sure chromium runs.  If you update after this point, make sure to update your dports, too, just to be sure everything is in sync.  This applies to 5.6 and 5.7.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2019/06/26/tcp-keepalive-change-in-dragonfly-kernel/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>5.6.1 on the way</title>
		<link>https://www.dragonflydigest.com/2019/06/18/5-6-1-on-the-way/</link>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Tue, 18 Jun 2019 16:26:20 +0000</pubDate>
				<category><![CDATA[Committed Code]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=23083</guid>

					<description><![CDATA[A last-minute drm change in DragonFly 5.6 turned out to cause a reproducible lockup, so there&#8217;s changes in place for it.  This means 5.6.1 will need to be rolled, which I will do in a day or two.  If you want to update now, the normal buildworld/buildkernel process will get you this change.]]></description>
										<content:encoded><![CDATA[<p>A last-minute drm change in DragonFly 5.6 <a href="http://lists.dragonflybsd.org/pipermail/users/2019-June/358201.html">turned out to cause a reproducible lockup</a>, so there&#8217;s <a href="http://lists.dragonflybsd.org/pipermail/commits/2019-June/719045.html">changes in place for it</a>.  This means 5.6.1 will need to be rolled, which I will do in a day or two.  If you want to update now, the normal buildworld/buildkernel process will get you this change.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>OPIE removal in DragonFly-master</title>
		<link>https://www.dragonflydigest.com/2019/06/18/opie-removal-in-dragonfly-master/</link>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Tue, 18 Jun 2019 13:04:48 +0000</pubDate>
				<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Goings-on]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=23079</guid>

					<description><![CDATA[OPIE was disabled recently in DragonFly.  Now that the 5.6 release is out, it has been removed.  This may require manual intervention if you are on DragonFly-master (i.e. 5.5. or 5.7) and update in the next day or two.  This need to fiddle with it will go away soon with changes to &#8216;make upgrade&#8217;; I &#8230; <p class="link-more"><a href="https://www.dragonflydigest.com/2019/06/18/opie-removal-in-dragonfly-master/" class="more-link">Continue reading<span class="screen-reader-text"> "OPIE removal in DragonFly-master"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>OPIE was <a href="https://www.dragonflydigest.com/2019/05/31/23008.html">disabled recently in DragonFly</a>.  Now that the 5.6 release is out, <a href="http://lists.dragonflybsd.org/pipermail/commits/2019-June/719035.html">it has been removed</a>.  This may <a href="http://lists.dragonflybsd.org/pipermail/users/2019-June/358197.html">require manual intervention</a> if you are on DragonFly-master (i.e. 5.5. or 5.7) and update in the next day or two.  This need to fiddle with it will <a href="http://lists.dragonflybsd.org/pipermail/users/2019-June/358198.html">go away soon</a> with changes to &#8216;make upgrade&#8217;; I will mention it when I see it.</p>
<p>This won&#8217;t affect anyone running 5.4 or 5.6.  It&#8217;s only in development.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>HAMMER2 corruption bug and fix</title>
		<link>https://www.dragonflydigest.com/2019/04/12/hammer2-corruption-bug-and-fix/</link>
					<comments>https://www.dragonflydigest.com/2019/04/12/hammer2-corruption-bug-and-fix/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Fri, 12 Apr 2019 16:32:10 +0000</pubDate>
				<category><![CDATA[Committed Code]]></category>
		<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Hammer]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=22772</guid>

					<description><![CDATA[It&#8217;s possible to have data corrupted on a HAMMER2 volume during a specific combination of a bulkfree operation and a lot of writing to disk.  Matthew Dillon has a potential fix already.  As he announced, it&#8217;s scheduled to go into 5.4 this weekend.  It&#8217;s a rare bug, but if you want to check for it, &#8230; <p class="link-more"><a href="https://www.dragonflydigest.com/2019/04/12/hammer2-corruption-bug-and-fix/" class="more-link">Continue reading<span class="screen-reader-text"> "HAMMER2 corruption bug and fix"</span></a></p>]]></description>
										<content:encoded><![CDATA[<p>It&#8217;s possible to have data corrupted on a HAMMER2 volume during a specific combination of a bulkfree operation and a lot of writing to disk.  Matthew Dillon has a <a href="http://lists.dragonflybsd.org/pipermail/commits/2019-April/718665.html">potential fix already</a>.  As he <a href="http://lists.dragonflybsd.org/pipermail/users/2019-April/358150.html">announced</a>, it&#8217;s scheduled to go into 5.4 this weekend.  It&#8217;s a rare bug, but if you want to check for it, look for CHECK FAIL entries in /var/log/messages.</p>
<p>And because every cloud has a silver lining: some <a href="http://lists.dragonflybsd.org/pipermail/commits/2019-April/718667.html">not-yet-quantified performance improvements</a>.</p>
<p>&nbsp;</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2019/04/12/hammer2-corruption-bug-and-fix/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>DragonFly 5.2 released</title>
		<link>https://www.dragonflydigest.com/2018/04/10/dragonfly-5-2-released/</link>
					<comments>https://www.dragonflydigest.com/2018/04/10/dragonfly-5-2-released/#comments</comments>
		
		<dc:creator><![CDATA[Justin Sherrill]]></dc:creator>
		<pubDate>Tue, 10 Apr 2018 18:28:09 +0000</pubDate>
				<category><![CDATA[DragonFly]]></category>
		<category><![CDATA[Goings-on]]></category>
		<category><![CDATA[Heads Up!]]></category>
		<guid isPermaLink="false">https://www.dragonflydigest.com/?p=21102</guid>

					<description><![CDATA[DragonFly 5.2.0 has been released.  Spectre/Meltdown mitigations are in there, along with improvements for HAMMER2, accelerated video, and ipfw.  My users@ post has the details on upgrading, as does the release notes.]]></description>
										<content:encoded><![CDATA[<p>DragonFly 5.2.0 <a href="https://www.dragonflybsd.org/release52/">has been released</a>.  Spectre/Meltdown mitigations are in there, along with improvements for HAMMER2, accelerated video, and ipfw.  My <a href="http://lists.dragonflybsd.org/pipermail/users/2018-April/335721.html">users@ post</a> has the details on upgrading, as does the release notes.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.dragonflydigest.com/2018/04/10/dragonfly-5-2-released/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
			</item>
	</channel>
</rss>
