380: Early ZFS-mas
BSD Now - Podcast autorstwa JT Pennington - Czwartki
Kategorie:
We read FreeBSD’s 3rd quarter status report, OpenZFS 2.0, adding check-hash checks in UFS filesystem, OpenSSL 3.0 /dev/crypto issues on FreeBSD, and more. NOTES This episode of BSDNow is brought to you by Tarsnap Headlines 3rd Quarter FreeBSD Report The call for submissions for the 4th Quarter is out OpenZFS 2.0 This Monday, ZFS on Linux lead developer Brian Behlendorf published the OpenZFS 2.0.0 release to GitHub. Along with quite a lot of new features, the announcement brings an end to the former distinction between "ZFS on Linux" and ZFS elsewhere (for example, on FreeBSD). This move has been a long time coming—the FreeBSD community laid out its side of the roadmap two years ago—but this is the release that makes it official. News Roundup Revision 367034 Various new check-hash checks have been added to the UFS filesystem over various major releases. Superblock check hashes were added for the 12 release and cylinder-group and inode check hashes will appear in the 13 release. OpenSSL 3.0 /dev/crypto issues on FreeBSD So, just learned that the OpenSSL devs decided to break /dev/crypto on FreeBSD. OS108-9.1 XFCE amd64 released OS108 is a fast, open and Secure Desktop Operating System built on top of NetBSD. > Installing OS108 to your hard drive is done by using the sysinst utility, the process is basically the same as installing NetBSD itself. Please refer to the NetBSD guide for installation details, http://www.netbsd.org/docs/guide/en/part-install.html Installation Video *** Beastie Bits OpenBGPD 6.8p1 portable: released Nov 5th, 2020 IRC Awk Bot Docker on FreeBSD using bhyve and sshfs The UNIX Command Language (1976) *** Tarsnap 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. Feedback/Questions santi - openrc trond - python2 and mailman Send questions, comments, show ideas/topics, or stories you want mentioned on the show to [email protected] ***