diff --git a/website/content/en/status/report-2022-07-2022-09/intro.adoc b/website/content/en/status/report-2022-07-2022-09/intro.adoc index e3ebb30c81..f8a991319d 100644 --- a/website/content/en/status/report-2022-07-2022-09/intro.adoc +++ b/website/content/en/status/report-2022-07-2022-09/intro.adoc @@ -1,11 +1,11 @@ Here is the third quarterly report for year 2022, with 24 reports included, which is slightly fewer than last quarter. I notice that in the past we had quarters with many more reports: often more than 30, sometimes even more than 40. -Thus I would like to encourage all of you to submit reports: reports are useful to share your work, to find help, to have more eyes reviewing your changes, to have more people testing your softwares, to reach a wider audience whenever you need to tell something to all of the FreeBSD community and in many other cases. +Thus I would like to encourage all of you to submit reports: reports are useful to share your work, to find help, to have more eyes reviewing your changes, to have more people testing your software, to reach a wider audience whenever you need to tell something to all of the FreeBSD community and in many other cases. Please do not be shy and do not worry if you are not a native English speaker or if you are not proficient in AsciiDoc syntax: the quarterly team will be glad to help you in whatever you need. -On the other hand, if you really do not have anything to report, then maybe you might like to join one of the interesting projects described below, or you might be insipired from one of them to do something new, thus having something to report in the future. +On the other hand, if you really do not have anything to report, then maybe you might like to join one of the interesting projects described below, or you might be inspired from one of them to do something new, thus having something to report in the future. We wish you all a pleasant read. Lorenzo Salvadore, on behalf of the status report team. diff --git a/website/content/en/status/report-2022-07-2022-09/lsof.adoc b/website/content/en/status/report-2022-07-2022-09/lsof.adoc index 6bbe24709c..136f204feb 100644 --- a/website/content/en/status/report-2022-07-2022-09/lsof.adoc +++ b/website/content/en/status/report-2022-07-2022-09/lsof.adoc @@ -1,19 +1,19 @@ === sysutils/lsof major upgrade Link: + link:https://github.com/lsof-org/lsof[lsof project repo] URL: link:https://github.com/lsof-org/lsof[https://github.com/lsof-org/lsof] Contact: + Larry Rosenman package:sysutils/lsof[] had a major upgrade to no longer look in `/dev/kmem` for data, and to use the userland API. This took a long time to hit the tree, but is finally done. It fixes man:lsof[8] to work with ZFS again for the first time since 13.0-RELEASE. This will make maintenance much easier going forward. To the kernel folks: if you make changes that break lsof, please submit a GitHub pull request to https://github.com/lsof-org/lsof. Please test any changes to the interfaces that lsof uses and make sure they still work. These all should be userland interfaces now, but please test. -My thanks to Warner Losh , Mateusz Guzik , and Ed Maste for help getting this major change landed. +My thanks to Warner Losh , Mateusz Guzik , and Ed Maste for help getting this major change landed. diff --git a/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc b/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc index ffb9fa95bc..84b680b904 100644 --- a/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc +++ b/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc @@ -1,24 +1,24 @@ === Rewrite of pjdfstest Links: + link:https://github.com/musikid/pjdfstest[Github] URL: link:https://github.com/musikid/pjdfstest[https://github.com/musikid/pjdfstest] + link:https://musikid.github.io/blog/rewrite-pjdfstest/[Blog] URL: https://musikid.github.io/blog/rewrite-pjdfstest/[https://musikid.github.io/blog/rewrite-pjdfstest/] + -Contact: Alan Somers +Contact: Alan Somers Back in 2007, Pawel Jakub Dawidek wrote pjdfstest, a POSIX file system conformance test tool. He originally wrote it to validate the port of ZFS to FreeBSD, but it has subsequently been used for other file systems and other operating systems. This year, Sayafdine Said rewrote it under Google's sponsorship. The new version has several improvements: * More configurable, for better use with other file systems. * Much faster, largely thanks to said configurability. * Better test case isolation, making failure easy to debug. * No longer requires root privileges for all test cases. * Test cases can be run in a debugger. * More maintainable, less duplication. There are still a couple of lingering PRs to complete, but we expect to wrap those up and add pjdfstest to the ports collection soon. From there, it will be used both by `/usr/tests` for ZFS and UFS, and by external developers for other file systems. Sponsor: Google Summer of Code diff --git a/website/content/en/status/report-2022-07-2022-09/portmgr.adoc b/website/content/en/status/report-2022-07-2022-09/portmgr.adoc index ff7d136d7d..62655e0d66 100644 --- a/website/content/en/status/report-2022-07-2022-09/portmgr.adoc +++ b/website/content/en/status/report-2022-07-2022-09/portmgr.adoc @@ -1,56 +1,56 @@ === Ports Collection Links: + link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[https://www.FreeBSD.org/ports/] + link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] + link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] + link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[https://www.freebsd.org/portmgr/] + link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/] Contact: René Ladan + Contact: FreeBSD Ports Management Team The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. Below is what happened in the last quarter. -Currently there are just over 30,500 ports in the Ports Tree. +Currently there are just over 30,500 ports in the Ports Tree. There are currently just under 2,800 open ports PRs of which 750 are unassigned. The last quarter saw 9,137 commits by 151 committers on the main branch and 589 commits by 61 committers on the 2022Q3 branch. Compared to two quarters ago, this means a slight increase in the number of ports, but also a slight increase in the number of (unassigned) ports PRs and a slight decrease in the number of commits made. In the last quarter, we welcomed Felix Palmen (zirias@) as a new ports committer, welcomed back Akinori MUSHA (knu@), and said goodbye to Olli Hauer (ohauer@). We also welcomed Luca Pizzamiglio (pizzamig@) as an official member of portmgr. Some large changes in the Ports Tree were made during the last quarter: * "Created by" lines have been removed from the top of each Makefile, as a lot of those were outdated. * WWW: has been moved from each pkg-descr into each Makefile as a variable; the below write-up is from Stefan Eßer (se@) who did the work: -The description of a port's functionality should end with the URL of a web page that provides further information, such as best practices for usage or configuration. -This information can be displayed with `pkg query -e` for installed packages or `pkg rquery -e` for available packages. +The description of a port's functionality should end with the URL of a web page that provides further information, such as best practices for usage or configuration. +This information can be displayed with `pkg query -e` for installed packages or `pkg rquery -e` for available packages. The URL used to be appended to the end of the ports' pkg-descr files, with the prefix "WWW: ", so that tools could extract the URL from the description. Over time, many of these URLs have become stale, since port updates generally change only the Makefile, not the pkg-descr file. -By moving the definition of these URLs into the Makefiles, maintainers are more likely to update the URL along with other port changes, and tools have easier access to them. +By moving the definition of these URLs into the Makefiles, maintainers are more likely to update the URL along with other port changes, and tools have easier access to them. The URLs are now assigned to the WWW macro in the Makefile and can be queried with `make -V WWW` in the port directory. Tools that process the description contained in the package files still work because the "WWW: " lines at the end are generated from the WWW values in the Makefiles. During EuroBSDCon, portmgr@ had a discussion about improving the situation for kernel module packages. Various possibilities have been discussed. The following happened under the hood: * one new USES, "vala", was added. * The default version of Go got bumped to 1.19 * CMake is now a meta-port * Initial support for Qt 6 was added, at version 6.3.2 * Vim no longer installs a system-wide vimrc * A number of major ports got updated: ** pkg 1.18.4 ** Chromium 106.0.5249.91 ** Firefox 105.0.1 *** Firefox ESR 102.3.0 ** KDE Applications 22.8.1 ** KDE Frameworks 5.98 ** Rust 1.63.0 ** SDL 2.24.0 ** Xorg server 21.1.4 (overhaul) diff --git a/website/content/en/status/report-2022-07-2022-09/pot.adoc b/website/content/en/status/report-2022-07-2022-09/pot.adoc index 376833e224..8d80107ccd 100644 --- a/website/content/en/status/report-2022-07-2022-09/pot.adoc +++ b/website/content/en/status/report-2022-07-2022-09/pot.adoc @@ -1,24 +1,24 @@ === Containers and FreeBSD: Pot, Potluck and Potman Links: + link:https://github.com/bsdpot[Pot organization on github] URL: link:https://github.com/bsdpot[https://github.com/bsdpot] Contact: Luca Pizzamiglio (Pot) + Contact: Stephan Lichtenauer (Potluck) + Contact: Michael Gmelin (Potman) Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad]. During the last quarter, link:https://github.com/bsdpot/pot/releases/tag/0.15.3[pot 0.15.3] was released. It contains a number of improvements like mount-out to remove or unmount a previously mount-in folder or filesystem, signal and exec commands, better jail lifecycle handling, and many bug fixes. A new version of the Nomad driver, link:https://github.com/bsdpot/nomad-pot-driver/releases/tag/v0.9.0[nomad-pot-driver 0.9.0], was also released with signal and exec support and stability fixes. Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: a repository of pot flavours and complete container images for usage with pot and in many cases Nomad. Since the last status report, link:https://github.com/bsdpot/potluck/commits/master[many changes were committed], including many fixes and improvements to core images like link:https://github.com/bsdpot/potluck/tree/master/grafana[grafana], link:https://github.com/bsdpot/potluck/tree/master/postgresql-patroni[postgresql-patroni] or link:https://github.com/bsdpot/potluck/tree/master/loki[loki]. -Additionally, all images have been rebuilt for FreeBSD 13.1 and 12.3 and to include the current quarterly versions of the packages being used. +Additionally, all images have been rebuilt for FreeBSD 13.1 and 12.3 and to include the current quarterly versions of the packages being used. Last not least, Luca held the pot implementation and ecosystem talk link:https://2022.eurobsdcon.org/program/[How far a naive FreeBSD container implementation can go] at EuroBSDCon 2022. As always, feedback and patches are welcome. diff --git a/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc b/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc index 6051e43e82..97aa9e5d1f 100644 --- a/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc +++ b/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc @@ -1,30 +1,30 @@ === Enabling Snapshots on Filesystems Using Journaled Soft Updates Links: + link:https://reviews.freebsd.org/D36491[Milestone 1 Core Changes] URL: link:https://reviews.freebsd.org/D36491[https://reviews.freebsd.org/D36491] Contact: Kirk McKusick -This project will make UFS/FFS filesystem snapshots avaiable when running with journaled soft updates. +This project will make UFS/FFS filesystem snapshots available when running with journaled soft updates. The UFS/FFS filesystem has the ability to take snapshots. Because the taking of snapshots was added after soft updates were written they were fully integrated with soft updates. When journaled soft updates were added in 2010, they were never integrated with snapshots. So snapshots cannot be used on filesystems running with journaled soft updates. Snapshots became less important with the support for ZFS on FreeBSD since ZFS can take snapshots quickly and easily. However there remain two instances where UFS snapshots are still important. The first is that they allow reliable dumps of live filesystems which avoids possibly hours of down time. The second is that they allow the running of background fsck. Similar to the need for scrub in ZFS, fsck needs to be run periodically to find undetected disk failures. Snapshots allow fsck to be run on live filesystems rather than needing to schedule down time to run it. This project has two milestones: 1. enable snapshots when running with journaled soft updates and ensure that they can be used for doing background dumps on a live filesystem. This milestone should be completed by the end of 2022. 2. extend fsck_ffs to be able to do a background check using a snapshot on a filesystem running with journaled soft updates. This milestone is expected by Q3 of 2023. Sponsored by: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-07-2022-09/wifi.adoc b/website/content/en/status/report-2022-07-2022-09/wifi.adoc index 1416f97cf1..284b81a769 100644 --- a/website/content/en/status/report-2022-07-2022-09/wifi.adoc +++ b/website/content/en/status/report-2022-07-2022-09/wifi.adoc @@ -1,31 +1,31 @@ === More wireless updates Links: + link:https://people.freebsd.org/~bz/wireless/[Bjoern's Wireless Work In Progress landing page] URL: link:https://people.freebsd.org/\~bz/wireless/[https://people.freebsd.org/~bz/wireless/] + link:https://wiki.freebsd.org/WiFi/Rtw88[Realtek rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88] + link:https://wiki.freebsd.org/WiFi/Rtw89[Realtek rtw89 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw89[https://wiki.freebsd.org/WiFi/Rtw89] + link:https://wiki.freebsd.org/WiFi/Mt76[MediaTek mt76 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Mt76[https://wiki.freebsd.org/WiFi/Mt76] + link:https://wiki.freebsd.org/WiFi/Ath11k[QCA ath11k status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Ath11k[https://wiki.freebsd.org/WiFi/Ath11k] Contact: Bjoern A. Zeeb Currently development is mostly driven by Intel's iwlwifi driver again (see other report). As the saying goes ''each one helps the other'' so has work on Realtek's rtw89 driver helped find a bug in LinuxKPI bothering iwlwifi users. For this status report the topic is mostly more drivers, which do need more LinuxKPI support. Various work in progress: * Realtek's rtw88 PCI is in-tree as-is and after a fruitful discussion with Hans Petter Selasky at EuroBSDCon work on LinuxKPI USB support for the rtw88 USB WiFi dongles will continue. - * Realtek's rtw89 driver was committed to main but is not conected to the build yet. Scanning already works but packets are not yet passing. Having the driver in-tree already eased testing for users having that chipset in order to indentify more unimplemented LinuxKPI bits (some of which will help the other drivers as well) and reduced work for me. + * Realtek's rtw89 driver was committed to main but is not connected to the build yet. Scanning already works but packets are not yet passing. Having the driver in-tree already eased testing for users having that chipset in order to indentify more unimplemented LinuxKPI bits (some of which will help the other drivers as well) and reduced work for me. * The next drivers to probably hit the tree will be based on MediaTek's mt76 driver (for 7921 and 7915) which I have compiling and started testing. * Based on requests I am also working on ath11k to support STA mode given some vendors seem to ship Laptops with those chips. While some of this clearly benefits from work sponsored by The FreeBSD Foundation for iwlwifi and newer standard support, a lot of this is just free-time work. If you are interested in any of these drivers I would greatly appreciate if some more hands would help with one or the other. This could be regularly testing updates to main, writing documentation and updating wiki pages, tracking PRs, trying out patches, helping with work on individual LinuxKPI bits with or without 802.11 work, or simply debugging problems with individual drivers and/or chipsets. If you are interested in helping with any one of the above, please drop me an email. For the latest state of the development, please follow the freebsd-wireless mailing list and check the wiki pages (as soon as they exist).