<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>app03</fireside:hostname>
    <fireside:genDate>Thu, 25 Jun 2026 19:25:24 +0000</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>BSD Now - Episodes Tagged with “Sparc64”</title>
    <link>https://www.bsdnow.tv/tags/sparc64</link>
    <pubDate>Thu, 03 Sep 2020 06:00:00 -0400</pubDate>
    <description>Created by three guys who love BSD, we cover the latest news and have an extensive series of tutorials, as well as interviews with various people from all areas of the BSD community. It also serves as a platform for support and questions. We love and advocate FreeBSD, OpenBSD, NetBSD, DragonFlyBSD and TrueOS. Our show aims to be helpful and informative for new users that want to learn about them, but still be entertaining for the people who are already pros. The show airs on Wednesdays at 2:00PM (US Eastern time) and the edited version is usually up the following day.</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>A weekly podcast and the place to B...SD</itunes:subtitle>
    <itunes:author>JT Pennington</itunes:author>
    <itunes:summary>Created by three guys who love BSD, we cover the latest news and have an extensive series of tutorials, as well as interviews with various people from all areas of the BSD community. It also serves as a platform for support and questions. We love and advocate FreeBSD, OpenBSD, NetBSD, DragonFlyBSD and TrueOS. Our show aims to be helpful and informative for new users that want to learn about them, but still be entertaining for the people who are already pros. The show airs on Wednesdays at 2:00PM (US Eastern time) and the edited version is usually up the following day.</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c91b88f1-e824-4815-bcb8-5227818d6010/cover.jpg?v=4"/>
    <itunes:explicit>no</itunes:explicit>
    <itunes:keywords>berkeley,freebsd,openbsd,netbsd,dragonflybsd,trueos,trident,hardenedbsd,tutorial,howto,guide,bsd,interview</itunes:keywords>
    <itunes:owner>
      <itunes:name>JT Pennington</itunes:name>
      <itunes:email>feedback@bsdnow.tv</itunes:email>
    </itunes:owner>
<itunes:category text="News">
  <itunes:category text="Tech News"/>
</itunes:category>
<itunes:category text="Education">
  <itunes:category text="How To"/>
</itunes:category>
<item>
  <title>366: Bootloader zpool checkpoints</title>
  <link>https://www.bsdnow.tv/366</link>
  <guid isPermaLink="false">ac66cef0-02a8-44b9-b915-813b8e26c643</guid>
  <pubDate>Thu, 03 Sep 2020 06:00:00 -0400</pubDate>
  <author>JT Pennington</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/c91b88f1-e824-4815-bcb8-5227818d6010/ac66cef0-02a8-44b9-b915-813b8e26c643.mp3" length="54891512" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>JT Pennington</itunes:author>
  <itunes:subtitle>OpenZFS with ZSTD lands in FreeBSD 13, LibreSSL doc status update, FreeBSD on SPARC64 (is dead), Bringing zpool checkpoints to a FreeBSD bootloader, and more</itunes:subtitle>
  <itunes:duration>53:02</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c91b88f1-e824-4815-bcb8-5227818d6010/cover.jpg?v=4"/>
  <description>&lt;p&gt;OpenZFS with ZSTD lands in FreeBSD 13, LibreSSL doc status update, FreeBSD on SPARC64 (is dead), Bringing zpool checkpoints to a FreeBSD bootloader, and more&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;NOTES&lt;/em&gt;&lt;/strong&gt;&lt;br&gt;
This episode of BSDNow is brought to you by &lt;a href="https://www.tarsnap.com/" rel="nofollow noopener"&gt;Tarsnap&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;Headlines&lt;/h2&gt;

&lt;h3&gt;&lt;a href="https://svnweb.freebsd.org/base?view=revision&amp;amp;revision=364746" rel="nofollow noopener"&gt;OpenZFS with ZSTD land in FreeBSD 13&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/openzfs/zfs/commit/10b3c7f5e424f54b3ba82dbf1600d866e64ec0a0" rel="nofollow noopener"&gt;ZStandard Compression for OpenZFS&lt;/a&gt;
&amp;gt; The primary benefit is maintaining a completely shared code base with the community allowing FreeBSD to receive new features sooner and with less effort.
&amp;gt; I would advise against doing 'zpool upgrade' or creating indispensable pools using new features until this change has had a month+ to soak.&lt;/li&gt;
&lt;li&gt;Rebasing FreeBSD’s OpenZFS on the new upstream was sponsored by iXsystems&lt;/li&gt;
&lt;li&gt;The competition of ZSTD support for OpenZFS was sponsored by the FreeBSD Foundation
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="https://undeadly.org/cgi?action=article;sid=20200817063735" rel="nofollow noopener"&gt;LibreSSL documentation status update&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;More than six years ago, LibreSSL was forked from OpenSSL, and almost two years ago, i explained the status of LibreSSL documentation during EuroBSDCon 2018 in Bucuresti. So it seems providing an update might be in order.&lt;br&gt;
Note that this is not an update regarding LibreSSL status in general because i'm not the right person to talk about the big picture of working on the LibreSSL code, my work has been quite focussed on documentation. All the same, it is fair to say that even though the number of developers working on it is somewhat limited, the LibreSSL project is quite alive, typically having a release every few months. Progress continues being made with respect to porting and adding new functionality (for example regarding TLSv1.3, CMS, RSA-PSS, RSA-OAEP, GOST, SM3, SM4, XChaCha20 during the last two years), OpenSSL compatibility improvements (including providing additional OpenSSL-1.1 APIs), and lots of bug fixes and code cleanup.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h3&gt;&lt;a href="https://eerielinux.wordpress.com/2020/02/15/freebsd-on-sparc64-is-dead/" rel="nofollow noopener"&gt;FreeBSD on SPARC64 (is dead)&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;’m coming pretty late to the party, because SPARC64 support in FreeBSD is apparently doomed: After the POWER platform made the switch to a LLVM/Clang-based toolchain, SPARC64 is one of the last ones that still uses the ancient GCC 4.2-based toolchain that the project wants to finally get rid off (it has already happened as I was writing this – looks like the firm plan was not so firm after all, since they killed it off early). And compared to the other platforms it has seen not too much love in recent times… SPARC64 being a great platform, I’d be quite sad to see it go. But before that happens let’s see what the current status is and what would need to be done if it were to survive, shall we?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h2&gt;News Roundup&lt;/h2&gt;

&lt;h3&gt;&lt;a href="https://www.oshogbo.vexillium.org/blog/79/" rel="nofollow noopener"&gt;Bringing zpool checkpoints to a FreeBSD bootloader&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;Almost two years ago I wrote a blog post about checkpoints in ZFS. I didn’t hide that I was a big fan of them. That said, after those two years, I still feel that there are underappreciated features in the ZFS world, so I decided to do something about that.&lt;br&gt;
Currently, one of the best practices for upgrading your operating system is to use boot environments. They are a great feature for managing multiple kernels and userlands. They are based on juggling which ZFS datasets are mounted. Each dataset has its own version of the system. Unfortunately, boot environments have their limitations. If we, for example, upgrade our ZFS pool, we may not be able to use older versions of the system anymore. &lt;br&gt;
The big advantage of boot environments is that they have very good tools. Two main tools are beadm (which was created by vermaden) and bectl (which currently is in the FreeBSD base system). These tools allow us to create and manage boot environments.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h2&gt;Beastie Bits&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://documents.uow.edu.au/content/groups/public/@web/@inf/@scsse/documents/doc/uow103747.pdf" rel="nofollow noopener"&gt;The First Unix Port&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://mwl.io/archives/7346" rel="nofollow noopener"&gt;TLS Mastery updates, August 2020&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=ww60o940kEk" rel="nofollow noopener"&gt;What is the Oldest BSD Distribution still around today&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;hr&gt;

&lt;h3&gt;Tarsnap&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Feedback/Questions&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/ben%20-%20zfs%20send%20questions.md" rel="nofollow noopener"&gt;ben - zfs send questions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/lars%20-%20zfs%20pool%20question.md" rel="nofollow noopener"&gt;lars - zfs pool question&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/neutron%20-%20bectl%20vs%20beadm.md" rel="nofollow noopener"&gt;neutron - bectl vs beadm&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;hr&gt;

&lt;ul&gt;
&lt;li&gt;Send questions, comments, show ideas/topics, or stories you want mentioned on the show to &lt;a href="mailto:feedback@bsdnow.tv" rel="nofollow noopener"&gt;feedback@bsdnow.tv&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;hr&gt;
</description>
  <itunes:keywords>freebsd, openbsd, netbsd, dragonflybsd, trueos, trident, hardenedbsd, tutorial, howto, guide, bsd, operating system, os, berkeley, software, distribution, zfs, interview, libressl, ssl, documentation, doc, status, status update, sparc64, zpool, checkpoint, bootloader</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>OpenZFS with ZSTD lands in FreeBSD 13, LibreSSL doc status update, FreeBSD on SPARC64 (is dead), Bringing zpool checkpoints to a FreeBSD bootloader, and more</p>

<p><strong><em>NOTES</em></strong><br>
This episode of BSDNow is brought to you by <a href="https://www.tarsnap.com/" rel="nofollow noopener">Tarsnap</a></p>

<h2>Headlines</h2>

<h3><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=364746" rel="nofollow noopener">OpenZFS with ZSTD land in FreeBSD 13</a></h3>

<ul>
<li><a href="https://github.com/openzfs/zfs/commit/10b3c7f5e424f54b3ba82dbf1600d866e64ec0a0" rel="nofollow noopener">ZStandard Compression for OpenZFS</a>
&gt; The primary benefit is maintaining a completely shared code base with the community allowing FreeBSD to receive new features sooner and with less effort.
&gt; I would advise against doing 'zpool upgrade' or creating indispensable pools using new features until this change has had a month+ to soak.</li>
<li>Rebasing FreeBSD’s OpenZFS on the new upstream was sponsored by iXsystems</li>
<li>The competition of ZSTD support for OpenZFS was sponsored by the FreeBSD Foundation
***</li>
</ul>

<h3><a href="https://undeadly.org/cgi?action=article;sid=20200817063735" rel="nofollow noopener">LibreSSL documentation status update</a></h3>

<blockquote>
<p>More than six years ago, LibreSSL was forked from OpenSSL, and almost two years ago, i explained the status of LibreSSL documentation during EuroBSDCon 2018 in Bucuresti. So it seems providing an update might be in order.<br>
Note that this is not an update regarding LibreSSL status in general because i'm not the right person to talk about the big picture of working on the LibreSSL code, my work has been quite focussed on documentation. All the same, it is fair to say that even though the number of developers working on it is somewhat limited, the LibreSSL project is quite alive, typically having a release every few months. Progress continues being made with respect to porting and adding new functionality (for example regarding TLSv1.3, CMS, RSA-PSS, RSA-OAEP, GOST, SM3, SM4, XChaCha20 during the last two years), OpenSSL compatibility improvements (including providing additional OpenSSL-1.1 APIs), and lots of bug fixes and code cleanup.</p>
</blockquote>

<hr>

<h3><a href="https://eerielinux.wordpress.com/2020/02/15/freebsd-on-sparc64-is-dead/" rel="nofollow noopener">FreeBSD on SPARC64 (is dead)</a></h3>

<blockquote>
<p>’m coming pretty late to the party, because SPARC64 support in FreeBSD is apparently doomed: After the POWER platform made the switch to a LLVM/Clang-based toolchain, SPARC64 is one of the last ones that still uses the ancient GCC 4.2-based toolchain that the project wants to finally get rid off (it has already happened as I was writing this – looks like the firm plan was not so firm after all, since they killed it off early). And compared to the other platforms it has seen not too much love in recent times… SPARC64 being a great platform, I’d be quite sad to see it go. But before that happens let’s see what the current status is and what would need to be done if it were to survive, shall we?</p>
</blockquote>

<hr>

<h2>News Roundup</h2>

<h3><a href="https://www.oshogbo.vexillium.org/blog/79/" rel="nofollow noopener">Bringing zpool checkpoints to a FreeBSD bootloader</a></h3>

<blockquote>
<p>Almost two years ago I wrote a blog post about checkpoints in ZFS. I didn’t hide that I was a big fan of them. That said, after those two years, I still feel that there are underappreciated features in the ZFS world, so I decided to do something about that.<br>
Currently, one of the best practices for upgrading your operating system is to use boot environments. They are a great feature for managing multiple kernels and userlands. They are based on juggling which ZFS datasets are mounted. Each dataset has its own version of the system. Unfortunately, boot environments have their limitations. If we, for example, upgrade our ZFS pool, we may not be able to use older versions of the system anymore. <br>
The big advantage of boot environments is that they have very good tools. Two main tools are beadm (which was created by vermaden) and bectl (which currently is in the FreeBSD base system). These tools allow us to create and manage boot environments.</p>
</blockquote>

<hr>

<h2>Beastie Bits</h2>

<ul>
<li><a href="https://documents.uow.edu.au/content/groups/public/@web/@inf/@scsse/documents/doc/uow103747.pdf" rel="nofollow noopener">The First Unix Port</a></li>
<li><a href="https://mwl.io/archives/7346" rel="nofollow noopener">TLS Mastery updates, August 2020</a></li>
<li><a href="https://www.youtube.com/watch?v=ww60o940kEk" rel="nofollow noopener">What is the Oldest BSD Distribution still around today</a></li>
</ul>

<hr>

<h3>Tarsnap</h3>

<ul>
<li>This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups.</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/ben%20-%20zfs%20send%20questions.md" rel="nofollow noopener">ben - zfs send questions</a></li>
<li><a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/lars%20-%20zfs%20pool%20question.md" rel="nofollow noopener">lars - zfs pool question</a></li>
<li><a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/neutron%20-%20bectl%20vs%20beadm.md" rel="nofollow noopener">neutron - bectl vs beadm</a></li>
</ul>

<hr>

<ul>
<li>Send questions, comments, show ideas/topics, or stories you want mentioned on the show to <a href="mailto:feedback@bsdnow.tv" rel="nofollow noopener">feedback@bsdnow.tv</a></li>
</ul>

<hr>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>OpenZFS with ZSTD lands in FreeBSD 13, LibreSSL doc status update, FreeBSD on SPARC64 (is dead), Bringing zpool checkpoints to a FreeBSD bootloader, and more</p>

<p><strong><em>NOTES</em></strong><br>
This episode of BSDNow is brought to you by <a href="https://www.tarsnap.com/" rel="nofollow noopener">Tarsnap</a></p>

<h2>Headlines</h2>

<h3><a href="https://svnweb.freebsd.org/base?view=revision&amp;revision=364746" rel="nofollow noopener">OpenZFS with ZSTD land in FreeBSD 13</a></h3>

<ul>
<li><a href="https://github.com/openzfs/zfs/commit/10b3c7f5e424f54b3ba82dbf1600d866e64ec0a0" rel="nofollow noopener">ZStandard Compression for OpenZFS</a>
&gt; The primary benefit is maintaining a completely shared code base with the community allowing FreeBSD to receive new features sooner and with less effort.
&gt; I would advise against doing 'zpool upgrade' or creating indispensable pools using new features until this change has had a month+ to soak.</li>
<li>Rebasing FreeBSD’s OpenZFS on the new upstream was sponsored by iXsystems</li>
<li>The competition of ZSTD support for OpenZFS was sponsored by the FreeBSD Foundation
***</li>
</ul>

<h3><a href="https://undeadly.org/cgi?action=article;sid=20200817063735" rel="nofollow noopener">LibreSSL documentation status update</a></h3>

<blockquote>
<p>More than six years ago, LibreSSL was forked from OpenSSL, and almost two years ago, i explained the status of LibreSSL documentation during EuroBSDCon 2018 in Bucuresti. So it seems providing an update might be in order.<br>
Note that this is not an update regarding LibreSSL status in general because i'm not the right person to talk about the big picture of working on the LibreSSL code, my work has been quite focussed on documentation. All the same, it is fair to say that even though the number of developers working on it is somewhat limited, the LibreSSL project is quite alive, typically having a release every few months. Progress continues being made with respect to porting and adding new functionality (for example regarding TLSv1.3, CMS, RSA-PSS, RSA-OAEP, GOST, SM3, SM4, XChaCha20 during the last two years), OpenSSL compatibility improvements (including providing additional OpenSSL-1.1 APIs), and lots of bug fixes and code cleanup.</p>
</blockquote>

<hr>

<h3><a href="https://eerielinux.wordpress.com/2020/02/15/freebsd-on-sparc64-is-dead/" rel="nofollow noopener">FreeBSD on SPARC64 (is dead)</a></h3>

<blockquote>
<p>’m coming pretty late to the party, because SPARC64 support in FreeBSD is apparently doomed: After the POWER platform made the switch to a LLVM/Clang-based toolchain, SPARC64 is one of the last ones that still uses the ancient GCC 4.2-based toolchain that the project wants to finally get rid off (it has already happened as I was writing this – looks like the firm plan was not so firm after all, since they killed it off early). And compared to the other platforms it has seen not too much love in recent times… SPARC64 being a great platform, I’d be quite sad to see it go. But before that happens let’s see what the current status is and what would need to be done if it were to survive, shall we?</p>
</blockquote>

<hr>

<h2>News Roundup</h2>

<h3><a href="https://www.oshogbo.vexillium.org/blog/79/" rel="nofollow noopener">Bringing zpool checkpoints to a FreeBSD bootloader</a></h3>

<blockquote>
<p>Almost two years ago I wrote a blog post about checkpoints in ZFS. I didn’t hide that I was a big fan of them. That said, after those two years, I still feel that there are underappreciated features in the ZFS world, so I decided to do something about that.<br>
Currently, one of the best practices for upgrading your operating system is to use boot environments. They are a great feature for managing multiple kernels and userlands. They are based on juggling which ZFS datasets are mounted. Each dataset has its own version of the system. Unfortunately, boot environments have their limitations. If we, for example, upgrade our ZFS pool, we may not be able to use older versions of the system anymore. <br>
The big advantage of boot environments is that they have very good tools. Two main tools are beadm (which was created by vermaden) and bectl (which currently is in the FreeBSD base system). These tools allow us to create and manage boot environments.</p>
</blockquote>

<hr>

<h2>Beastie Bits</h2>

<ul>
<li><a href="https://documents.uow.edu.au/content/groups/public/@web/@inf/@scsse/documents/doc/uow103747.pdf" rel="nofollow noopener">The First Unix Port</a></li>
<li><a href="https://mwl.io/archives/7346" rel="nofollow noopener">TLS Mastery updates, August 2020</a></li>
<li><a href="https://www.youtube.com/watch?v=ww60o940kEk" rel="nofollow noopener">What is the Oldest BSD Distribution still around today</a></li>
</ul>

<hr>

<h3>Tarsnap</h3>

<ul>
<li>This weeks episode of BSDNow was sponsored by our friends at Tarsnap, the only secure online backup you can trust your data to. Even paranoids need backups.</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/ben%20-%20zfs%20send%20questions.md" rel="nofollow noopener">ben - zfs send questions</a></li>
<li><a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/lars%20-%20zfs%20pool%20question.md" rel="nofollow noopener">lars - zfs pool question</a></li>
<li><a href="https://github.com/BSDNow/bsdnow.tv/blob/master/episodes/366/feedback/neutron%20-%20bectl%20vs%20beadm.md" rel="nofollow noopener">neutron - bectl vs beadm</a></li>
</ul>

<hr>

<ul>
<li>Send questions, comments, show ideas/topics, or stories you want mentioned on the show to <a href="mailto:feedback@bsdnow.tv" rel="nofollow noopener">feedback@bsdnow.tv</a></li>
</ul>

<hr>]]>
  </itunes:summary>
</item>
<item>
  <title>327: ZFS Rename Repo</title>
  <link>https://www.bsdnow.tv/327</link>
  <guid isPermaLink="false">18bee756-2b2e-45ed-bcf1-403549bf6a32</guid>
  <pubDate>Thu, 05 Dec 2019 07:00:00 -0500</pubDate>
  <author>JT Pennington</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/c91b88f1-e824-4815-bcb8-5227818d6010/18bee756-2b2e-45ed-bcf1-403549bf6a32.mp3" length="60093881" type="audio/mp3"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>JT Pennington</itunes:author>
  <itunes:subtitle>We read FreeBSD’s third quarterly status report, OpenBSD on Sparc64, ZoL repo move to OpenZFS, GEOM NOP, keeping NetBSD up-to-date, and more.</itunes:subtitle>
  <itunes:duration>1:23:27</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c91b88f1-e824-4815-bcb8-5227818d6010/cover.jpg?v=4"/>
  <description>&lt;p&gt;We read FreeBSD’s third quarterly status report, OpenBSD on Sparc64, ZoL repo move to OpenZFS, GEOM NOP, keeping NetBSD up-to-date, and more.&lt;/p&gt;

&lt;h2&gt;Headlines&lt;/h2&gt;

&lt;h3&gt;&lt;a href="https://www.freebsd.org/news/status/report-2019-07-2019-09.html" rel="nofollow noopener"&gt;FreeBSD third quarterly status report for 2019&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;This quarter the reports team has been more active than usual thanks to a better organization: calls for reports and reminders have been sent regularly, reports have been reviewed and merged quickly (I would like to thank debdrup@ in particular for his reviewing work).&lt;/p&gt;

&lt;p&gt;Efficiency could still be improved with the help of our community. In particular, the quarterly team has found that many reports have arrived in the last days before the deadline or even after. I would like to invite the community to follow the guidelines below that can help us sending out the reports sooner.&lt;/p&gt;

&lt;p&gt;Starting from next quarter, all quarterly status reports will be prepared the last month of the quarter itself, instead of the first month after the quarter's end. This means that deadlines for submitting reports will be the 1st of January, April, July and October.&lt;/p&gt;

&lt;p&gt;Next quarter will then be a short one, covering the months of November and December only and the report will probably be out in mid January.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h3&gt;&lt;a href="https://eerielinux.wordpress.com/2019/10/10/openbsd-on-sparc64-6-0-to-6-5/" rel="nofollow noopener"&gt;OpenBSD on Sparc64&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;OpenBSD, huh? Yes, I usually write about FreeBSD and that’s in fact what I tried installing on the machine first. But I ran into problems with it very early on (never even reached single user mode) and put it aside for later. Since I powered up the SunFire again last month, I needed an OS now and chose OpenBSD for the simple reason that I have it available.&lt;/p&gt;

&lt;p&gt;First I wanted to call this article simply “OpenBSD on SPARC” – but that would have been misleading since OpenBSD used to support 32-bit SPARC processors, too. The platform was just put to rest after the 5.9 release.&lt;/p&gt;

&lt;p&gt;Version 6.0 was the last release of OpenBSD that came on CD-ROM. When I bought it, I thought that I’d never use the SPARC CD. But here was the chance! While it is an obsolete release, it comes with the cryptographic signatures to verify the next release. So the plan is to start at 6.0 as I can trust the original CDs and then update to the latest release. This will also be an opportunity to recap on some of the things that changed over the various versions.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h2&gt;News Roundup&lt;/h2&gt;

&lt;h3&gt;&lt;a href="https://zfsonlinux.topicbox.com/groups/zfs-discuss/T13eedc32607dab41/zol-repo-move-to-openzfs" rel="nofollow noopener"&gt;ZoL repo move to OpenZFS&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;Because it will contain the ZFS source code for both Linux and FreeBSD, we will rename the "ZFSonLinux" code repository to "OpenZFS".  Specifically, the repo at &lt;a href="http://github.com/ZFSonLinux/zfs" rel="nofollow noopener"&gt;http://github.com/ZFSonLinux/zfs&lt;/a&gt; will be moved to the OpenZFS organization, at &lt;a href="http://github.com/OpenZFS/zfs" rel="nofollow noopener"&gt;http://github.com/OpenZFS/zfs&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The next major release of ZFS for Linux and FreeBSD will be "OpenZFS 2.0", and is expected to ship in 2020.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h3&gt;&lt;a href="https://twitter.com/mcclure111/status/1196557401710837762" rel="nofollow noopener"&gt;Mcclure111 Sun Thread&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;A long time ago— like 15 years ago— I worked at Sun Microsystems. The company was nearly dead at the time (it died a couple years later) because they didn't make anything that anyone wanted to buy anymore. So they had a lot of strange ideas about how they'd make their comeback.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h3&gt;&lt;a href="https://oshogbo.vexillium.org/blog/71/" rel="nofollow noopener"&gt;GEOM NOP&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;Sometimes while testing file systems or applications you want to simulate some errors on the disk level. The first time I heard about this need was from Baptiste Daroussin during his presentation at AsiaBSDCon 2016. He mentioned how they had built a test lab with it. The same need was recently discussed during the PGCon 2019, to test a PostgreSQL instance. If you are FreeBSD user, I have great news for you: there is a GEOM provider which allows you to simulate a failing device.&lt;/p&gt;

&lt;p&gt;GNOP allows us to configure transparent providers from existing ones. The first interesting option of it is that we can slice the device into smaller pieces, thanks to the ‘offset option’ and ‘stripsesize’. This allows us to observe how the data on the disk is changing. Let’s assume that we want to observe the changes in the GPT table when the GPT flags are added or removed (for example the bootme flags which are described here). We can use dd every time and analyze it using absolute values from the disks.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h3&gt;&lt;a href="https://jmmv.dev/2017/02/pkg_comp-2.0-tutorial-netbsd.html" rel="nofollow noopener"&gt;Keeping NetBSD up-to-date with pkg_comp 2.0&lt;/a&gt;&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;This is a tutorial to guide you through the shiny new pkg_comp 2.0 on NetBSD.&lt;/p&gt;

&lt;p&gt;Goals: to use pkg_comp 2.0 to build a binary repository of all the packages you are interested in; to keep the repository fresh on a daily basis; and to use that repository with pkgin to maintain your NetBSD system up-to-date and secure.&lt;/p&gt;

&lt;p&gt;This tutorial is specifically targeted at NetBSD but should work on other platforms with some small changes. Expect, at the very least, a macOS-specific tutorial as soon as I create a pkg_comp standalone installer for that platform.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;hr&gt;

&lt;h2&gt;Beastie Bits&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="http://lists.dragonflybsd.org/pipermail/commits/2019-November/720070.html" rel="nofollow noopener"&gt;DragonFly - Radeon Improvements&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=7DglP7SbnlA&amp;amp;feature=share" rel="nofollow noopener"&gt;NomadBSD review&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://files.yukiisbo.red/openbsd_claim.png" rel="nofollow noopener"&gt;Spongebob OpenBSD Security Comic&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://colorforth.github.io/HOPL.html" rel="nofollow noopener"&gt;Forth : The Early Years&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.youtube.com/watch?v=pvaPaWyiuLA" rel="nofollow noopener"&gt;LCM+L PDP-7 booting and running UNIX Version 0&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;hr&gt;

&lt;h2&gt;Feedback/Questions&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Chris - &lt;a href="http://dpaste.com/284E5BV" rel="nofollow noopener"&gt;Ctrl-T&lt;/a&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://asciinema.org/a/xfSpvPT61Cnd9iRgbfIjT6kYj" rel="nofollow noopener"&gt;Improved Ctrl+t that shows kernel backtrace&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;Brian - &lt;a href="http://dpaste.com/05GDK8H#wrap" rel="nofollow noopener"&gt;Migrating NexentaStore to FreeBSD/FreeNAS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Avery - &lt;a href="http://dpaste.com/26KW801#wrap" rel="nofollow noopener"&gt;How to get involved&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;hr&gt;

&lt;ul&gt;
&lt;li&gt;Send questions, comments, show ideas/topics, or stories you want mentioned on the show to &lt;a href="mailto:feedback@bsdnow.tv" rel="nofollow noopener"&gt;feedback@bsdnow.tv&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;hr&gt;


    &lt;source src="http://201406.jb-dl.cdn.scaleengine.net/bsdnow/2019/bsd-0327.mp4" type="video/mp4"&gt;
    Your browser does not support the HTML5 video tag.
 
</description>
  <itunes:keywords>freebsd, openbsd, netbsd, dragonflybsd, trueos, trident, hardenedbsd, tutorial, howto, guide, bsd, interview, quarterly status, status report, report, sparc64, sun, geom, nop, gnop, uo-to-date, pkg_comp</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>We read FreeBSD’s third quarterly status report, OpenBSD on Sparc64, ZoL repo move to OpenZFS, GEOM NOP, keeping NetBSD up-to-date, and more.</p>

<h2>Headlines</h2>

<h3><a href="https://www.freebsd.org/news/status/report-2019-07-2019-09.html" rel="nofollow noopener">FreeBSD third quarterly status report for 2019</a></h3>

<blockquote>
<p>This quarter the reports team has been more active than usual thanks to a better organization: calls for reports and reminders have been sent regularly, reports have been reviewed and merged quickly (I would like to thank debdrup@ in particular for his reviewing work).</p>

<p>Efficiency could still be improved with the help of our community. In particular, the quarterly team has found that many reports have arrived in the last days before the deadline or even after. I would like to invite the community to follow the guidelines below that can help us sending out the reports sooner.</p>

<p>Starting from next quarter, all quarterly status reports will be prepared the last month of the quarter itself, instead of the first month after the quarter's end. This means that deadlines for submitting reports will be the 1st of January, April, July and October.</p>

<p>Next quarter will then be a short one, covering the months of November and December only and the report will probably be out in mid January.</p>
</blockquote>

<hr>

<h3><a href="https://eerielinux.wordpress.com/2019/10/10/openbsd-on-sparc64-6-0-to-6-5/" rel="nofollow noopener">OpenBSD on Sparc64</a></h3>

<blockquote>
<p>OpenBSD, huh? Yes, I usually write about FreeBSD and that’s in fact what I tried installing on the machine first. But I ran into problems with it very early on (never even reached single user mode) and put it aside for later. Since I powered up the SunFire again last month, I needed an OS now and chose OpenBSD for the simple reason that I have it available.</p>

<p>First I wanted to call this article simply “OpenBSD on SPARC” – but that would have been misleading since OpenBSD used to support 32-bit SPARC processors, too. The platform was just put to rest after the 5.9 release.</p>

<p>Version 6.0 was the last release of OpenBSD that came on CD-ROM. When I bought it, I thought that I’d never use the SPARC CD. But here was the chance! While it is an obsolete release, it comes with the cryptographic signatures to verify the next release. So the plan is to start at 6.0 as I can trust the original CDs and then update to the latest release. This will also be an opportunity to recap on some of the things that changed over the various versions.</p>
</blockquote>

<hr>

<h2>News Roundup</h2>

<h3><a href="https://zfsonlinux.topicbox.com/groups/zfs-discuss/T13eedc32607dab41/zol-repo-move-to-openzfs" rel="nofollow noopener">ZoL repo move to OpenZFS</a></h3>

<blockquote>
<p>Because it will contain the ZFS source code for both Linux and FreeBSD, we will rename the "ZFSonLinux" code repository to "OpenZFS".  Specifically, the repo at <a href="http://github.com/ZFSonLinux/zfs" rel="nofollow noopener">http://github.com/ZFSonLinux/zfs</a> will be moved to the OpenZFS organization, at <a href="http://github.com/OpenZFS/zfs" rel="nofollow noopener">http://github.com/OpenZFS/zfs</a>.</p>

<p>The next major release of ZFS for Linux and FreeBSD will be "OpenZFS 2.0", and is expected to ship in 2020.</p>
</blockquote>

<hr>

<h3><a href="https://twitter.com/mcclure111/status/1196557401710837762" rel="nofollow noopener">Mcclure111 Sun Thread</a></h3>

<blockquote>
<p>A long time ago— like 15 years ago— I worked at Sun Microsystems. The company was nearly dead at the time (it died a couple years later) because they didn't make anything that anyone wanted to buy anymore. So they had a lot of strange ideas about how they'd make their comeback.</p>
</blockquote>

<hr>

<h3><a href="https://oshogbo.vexillium.org/blog/71/" rel="nofollow noopener">GEOM NOP</a></h3>

<blockquote>
<p>Sometimes while testing file systems or applications you want to simulate some errors on the disk level. The first time I heard about this need was from Baptiste Daroussin during his presentation at AsiaBSDCon 2016. He mentioned how they had built a test lab with it. The same need was recently discussed during the PGCon 2019, to test a PostgreSQL instance. If you are FreeBSD user, I have great news for you: there is a GEOM provider which allows you to simulate a failing device.</p>

<p>GNOP allows us to configure transparent providers from existing ones. The first interesting option of it is that we can slice the device into smaller pieces, thanks to the ‘offset option’ and ‘stripsesize’. This allows us to observe how the data on the disk is changing. Let’s assume that we want to observe the changes in the GPT table when the GPT flags are added or removed (for example the bootme flags which are described here). We can use dd every time and analyze it using absolute values from the disks.</p>
</blockquote>

<hr>

<h3><a href="https://jmmv.dev/2017/02/pkg_comp-2.0-tutorial-netbsd.html" rel="nofollow noopener">Keeping NetBSD up-to-date with pkg_comp 2.0</a></h3>

<blockquote>
<p>This is a tutorial to guide you through the shiny new pkg_comp 2.0 on NetBSD.</p>

<p>Goals: to use pkg_comp 2.0 to build a binary repository of all the packages you are interested in; to keep the repository fresh on a daily basis; and to use that repository with pkgin to maintain your NetBSD system up-to-date and secure.</p>

<p>This tutorial is specifically targeted at NetBSD but should work on other platforms with some small changes. Expect, at the very least, a macOS-specific tutorial as soon as I create a pkg_comp standalone installer for that platform.</p>
</blockquote>

<hr>

<h2>Beastie Bits</h2>

<ul>
<li><a href="http://lists.dragonflybsd.org/pipermail/commits/2019-November/720070.html" rel="nofollow noopener">DragonFly - Radeon Improvements</a></li>
<li><a href="https://www.youtube.com/watch?v=7DglP7SbnlA&amp;feature=share" rel="nofollow noopener">NomadBSD review</a></li>
<li><a href="https://files.yukiisbo.red/openbsd_claim.png" rel="nofollow noopener">Spongebob OpenBSD Security Comic</a></li>
<li><a href="https://colorforth.github.io/HOPL.html" rel="nofollow noopener">Forth : The Early Years</a></li>
<li><a href="https://www.youtube.com/watch?v=pvaPaWyiuLA" rel="nofollow noopener">LCM+L PDP-7 booting and running UNIX Version 0</a></li>
</ul>

<hr>

<h2>Feedback/Questions</h2>

<ul>
<li>Chris - <a href="http://dpaste.com/284E5BV" rel="nofollow noopener">Ctrl-T</a>

<ul>
<li><a href="https://asciinema.org/a/xfSpvPT61Cnd9iRgbfIjT6kYj" rel="nofollow noopener">Improved Ctrl+t that shows kernel backtrace</a></li>
</ul></li>
<li>Brian - <a href="http://dpaste.com/05GDK8H#wrap" rel="nofollow noopener">Migrating NexentaStore to FreeBSD/FreeNAS</a></li>
<li>Avery - <a href="http://dpaste.com/26KW801#wrap" rel="nofollow noopener">How to get involved</a></li>
</ul>

<hr>

<ul>
<li>Send questions, comments, show ideas/topics, or stories you want mentioned on the show to <a href="mailto:feedback@bsdnow.tv" rel="nofollow noopener">feedback@bsdnow.tv</a></li>
</ul>

<hr>


    <source src="http://201406.jb-dl.cdn.scaleengine.net/bsdnow/2019/bsd-0327.mp4" type="video/mp4">
    Your browser does not support the HTML5 video tag.
]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>We read FreeBSD’s third quarterly status report, OpenBSD on Sparc64, ZoL repo move to OpenZFS, GEOM NOP, keeping NetBSD up-to-date, and more.</p>

<h2>Headlines</h2>

<h3><a href="https://www.freebsd.org/news/status/report-2019-07-2019-09.html" rel="nofollow noopener">FreeBSD third quarterly status report for 2019</a></h3>

<blockquote>
<p>This quarter the reports team has been more active than usual thanks to a better organization: calls for reports and reminders have been sent regularly, reports have been reviewed and merged quickly (I would like to thank debdrup@ in particular for his reviewing work).</p>

<p>Efficiency could still be improved with the help of our community. In particular, the quarterly team has found that many reports have arrived in the last days before the deadline or even after. I would like to invite the community to follow the guidelines below that can help us sending out the reports sooner.</p>

<p>Starting from next quarter, all quarterly status reports will be prepared the last month of the quarter itself, instead of the first month after the quarter's end. This means that deadlines for submitting reports will be the 1st of January, April, July and October.</p>

<p>Next quarter will then be a short one, covering the months of November and December only and the report will probably be out in mid January.</p>
</blockquote>

<hr>

<h3><a href="https://eerielinux.wordpress.com/2019/10/10/openbsd-on-sparc64-6-0-to-6-5/" rel="nofollow noopener">OpenBSD on Sparc64</a></h3>

<blockquote>
<p>OpenBSD, huh? Yes, I usually write about FreeBSD and that’s in fact what I tried installing on the machine first. But I ran into problems with it very early on (never even reached single user mode) and put it aside for later. Since I powered up the SunFire again last month, I needed an OS now and chose OpenBSD for the simple reason that I have it available.</p>

<p>First I wanted to call this article simply “OpenBSD on SPARC” – but that would have been misleading since OpenBSD used to support 32-bit SPARC processors, too. The platform was just put to rest after the 5.9 release.</p>

<p>Version 6.0 was the last release of OpenBSD that came on CD-ROM. When I bought it, I thought that I’d never use the SPARC CD. But here was the chance! While it is an obsolete release, it comes with the cryptographic signatures to verify the next release. So the plan is to start at 6.0 as I can trust the original CDs and then update to the latest release. This will also be an opportunity to recap on some of the things that changed over the various versions.</p>
</blockquote>

<hr>

<h2>News Roundup</h2>

<h3><a href="https://zfsonlinux.topicbox.com/groups/zfs-discuss/T13eedc32607dab41/zol-repo-move-to-openzfs" rel="nofollow noopener">ZoL repo move to OpenZFS</a></h3>

<blockquote>
<p>Because it will contain the ZFS source code for both Linux and FreeBSD, we will rename the "ZFSonLinux" code repository to "OpenZFS".  Specifically, the repo at <a href="http://github.com/ZFSonLinux/zfs" rel="nofollow noopener">http://github.com/ZFSonLinux/zfs</a> will be moved to the OpenZFS organization, at <a href="http://github.com/OpenZFS/zfs" rel="nofollow noopener">http://github.com/OpenZFS/zfs</a>.</p>

<p>The next major release of ZFS for Linux and FreeBSD will be "OpenZFS 2.0", and is expected to ship in 2020.</p>
</blockquote>

<hr>

<h3><a href="https://twitter.com/mcclure111/status/1196557401710837762" rel="nofollow noopener">Mcclure111 Sun Thread</a></h3>

<blockquote>
<p>A long time ago— like 15 years ago— I worked at Sun Microsystems. The company was nearly dead at the time (it died a couple years later) because they didn't make anything that anyone wanted to buy anymore. So they had a lot of strange ideas about how they'd make their comeback.</p>
</blockquote>

<hr>

<h3><a href="https://oshogbo.vexillium.org/blog/71/" rel="nofollow noopener">GEOM NOP</a></h3>

<blockquote>
<p>Sometimes while testing file systems or applications you want to simulate some errors on the disk level. The first time I heard about this need was from Baptiste Daroussin during his presentation at AsiaBSDCon 2016. He mentioned how they had built a test lab with it. The same need was recently discussed during the PGCon 2019, to test a PostgreSQL instance. If you are FreeBSD user, I have great news for you: there is a GEOM provider which allows you to simulate a failing device.</p>

<p>GNOP allows us to configure transparent providers from existing ones. The first interesting option of it is that we can slice the device into smaller pieces, thanks to the ‘offset option’ and ‘stripsesize’. This allows us to observe how the data on the disk is changing. Let’s assume that we want to observe the changes in the GPT table when the GPT flags are added or removed (for example the bootme flags which are described here). We can use dd every time and analyze it using absolute values from the disks.</p>
</blockquote>

<hr>

<h3><a href="https://jmmv.dev/2017/02/pkg_comp-2.0-tutorial-netbsd.html" rel="nofollow noopener">Keeping NetBSD up-to-date with pkg_comp 2.0</a></h3>

<blockquote>
<p>This is a tutorial to guide you through the shiny new pkg_comp 2.0 on NetBSD.</p>

<p>Goals: to use pkg_comp 2.0 to build a binary repository of all the packages you are interested in; to keep the repository fresh on a daily basis; and to use that repository with pkgin to maintain your NetBSD system up-to-date and secure.</p>

<p>This tutorial is specifically targeted at NetBSD but should work on other platforms with some small changes. Expect, at the very least, a macOS-specific tutorial as soon as I create a pkg_comp standalone installer for that platform.</p>
</blockquote>

<hr>

<h2>Beastie Bits</h2>

<ul>
<li><a href="http://lists.dragonflybsd.org/pipermail/commits/2019-November/720070.html" rel="nofollow noopener">DragonFly - Radeon Improvements</a></li>
<li><a href="https://www.youtube.com/watch?v=7DglP7SbnlA&amp;feature=share" rel="nofollow noopener">NomadBSD review</a></li>
<li><a href="https://files.yukiisbo.red/openbsd_claim.png" rel="nofollow noopener">Spongebob OpenBSD Security Comic</a></li>
<li><a href="https://colorforth.github.io/HOPL.html" rel="nofollow noopener">Forth : The Early Years</a></li>
<li><a href="https://www.youtube.com/watch?v=pvaPaWyiuLA" rel="nofollow noopener">LCM+L PDP-7 booting and running UNIX Version 0</a></li>
</ul>

<hr>

<h2>Feedback/Questions</h2>

<ul>
<li>Chris - <a href="http://dpaste.com/284E5BV" rel="nofollow noopener">Ctrl-T</a>

<ul>
<li><a href="https://asciinema.org/a/xfSpvPT61Cnd9iRgbfIjT6kYj" rel="nofollow noopener">Improved Ctrl+t that shows kernel backtrace</a></li>
</ul></li>
<li>Brian - <a href="http://dpaste.com/05GDK8H#wrap" rel="nofollow noopener">Migrating NexentaStore to FreeBSD/FreeNAS</a></li>
<li>Avery - <a href="http://dpaste.com/26KW801#wrap" rel="nofollow noopener">How to get involved</a></li>
</ul>

<hr>

<ul>
<li>Send questions, comments, show ideas/topics, or stories you want mentioned on the show to <a href="mailto:feedback@bsdnow.tv" rel="nofollow noopener">feedback@bsdnow.tv</a></li>
</ul>

<hr>


    <source src="http://201406.jb-dl.cdn.scaleengine.net/bsdnow/2019/bsd-0327.mp4" type="video/mp4">
    Your browser does not support the HTML5 video tag.
]]>
  </itunes:summary>
</item>
  </channel>
</rss>
