diff --git a/website/content/en/status/report-2023-01-2023-03/ci.adoc b/website/content/en/status/report-2023-01-2023-03/ci.adoc index 4a4cf3ae58..10b9d26b2e 100644 --- a/website/content/en/status/report-2023-01-2023-03/ci.adoc +++ b/website/content/en/status/report-2023-01-2023-03/ci.adoc @@ -1,52 +1,52 @@ === Continuous Integration Links: + -link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] + -link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] + -link:https://wiki.FreeBSD.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.FreeBSD.org/Jenkins[https://wiki.FreeBSD.org/Jenkins] + -link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[https://wiki.FreeBSD.org/HostedCI] + -link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[https://wiki.FreeBSD.org/3rdPartySoftwareCI] + -link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals] + -link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] + -link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[https://lists.FreeBSD.org/subscription/dev-ci] +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] + +link:https://wiki.FreeBSD.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.FreeBSD.org/Jenkins[] + +link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] + +link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] + +link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] + +link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[] Contact: Jenkins Admin + Contact: Li-Wen Hsu + Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + Contact: IRC #freebsd-ci channel on EFNet In the first quarter of 2023, we worked with the project contributors and developers to address their testing requirements. Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. Important completed tasks: * link:https://ci.FreeBSD.org/job/FreeBSD-main-aarch64-KASAN_test/[FreeBSD-main-aarch64-KASAN_test] and its supporting jobs have been added. * link:https://ci.FreeBSD.org/job/FreeBSD-stable-13-amd64-KASAN_test/[FreeBSD-stable-13-amd64-KASAN_test] and its supporting jobs have been added. * link:https://ci.FreeBSD.org/job/FreeBSD-main-amd64-gcc12_build/[FreeBSD-main-amd64-gcc12_build] now sends failing reports to the committers whose commits may be related. * Various fixes or workarounds to the tests of non-x86 architectures from trasz@ * Present Testing/CI Status Update in link:https://wiki.freebsd.org/DevSummit/202303[AsiaBSDCon 2023 Developer Summit] Work in progress tasks: * Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) * Designing and implementing use of CI cluster to build release artifacts as release engineering does * Simplifying CI/test environment setting up for contributors and developers * Setting up the CI stage environment and putting the experimental jobs on it * Organizing the scripts in freebsd-ci repository to prepare for merging to src repository * Improving the hardware test lab and adding more hardware for testing * Merge https://reviews.freebsd.org/D38815 * Merge https://reviews.freebsd.org/D36257 Open or queued tasks: * Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] * Setting up public network access for the VM guest running tests * Implementing use of bare-metal hardware to run test suites * Adding drm ports building tests against -CURRENT * Planning to run ztest tests * Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI]) * Working with hosted CI providers to have better FreeBSD support Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort! Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/doceng.adoc b/website/content/en/status/report-2023-01-2023-03/doceng.adoc index 789b75a0d7..3d565d37d7 100644 --- a/website/content/en/status/report-2023-01-2023-03/doceng.adoc +++ b/website/content/en/status/report-2023-01-2023-03/doceng.adoc @@ -1,103 +1,104 @@ //// Quarter: 1st quarter of 2023 Prepared by: fernape Reviewed by: carlavilla@ Last edit: Version: //// === Documentation Engineering Team -Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] + -Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] + -Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] +Links: + +link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[] + +link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] + +link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[] Contact: FreeBSD Doceng Team The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. During the last quarter: * The doc commit bit for Pau Amma was taken in. * Lorenzo Salvadore has been proposed as doc committer. carlavilla@ and dbaio@ will mentor him. * Ryusuke SUZUKI steps down from doceng. doceng would like to thank ryusuke@ for his service. Items pending and in the discussion: * link:https://cgit.freebsd.org/doc/commit/?id=4c50528a8678246a6d01765acac8c395434b8c7e[A new document about licensing] has been added to the documentation set. ==== Porter's Handbook: Three new `Uses` knobs have been added to the Handbook: * link:https://cgit.freebsd.org/doc/commit/?id=407dbb9254e7b6b379b8257f34f7732ed1afc71f[New Uses = ruby]. * link:https://cgit.freebsd.org/doc/commit/?id=afa1a31005978bac63874fff8a1833f69a81dae3[New Uses = ldap]. * link:https://cgit.freebsd.org/doc/commit/?id=689f1b026a02bf6d7039bdfec59353196d83ccef[New Uses = budgie]. Also: * link:https://cgit.freebsd.org/doc/commit/?id=9af61238fc24d4772b3c9e5fbd63fcaee2526699[The NVIDIA install and configure options have been fixed] * link:https://cgit.freebsd.org/doc/commit/?id=3c6d3dea4a3ee60e7f0033afc9c5bf74e9ae1d31[The Advanced Networking chapter has been improved] ==== FreeBSD Translations on Weblate Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] + Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] ===== Q4 2022 Status * 12 languages * 150 registered users ===== Languages * Chinese (Simplified) (zh-cn) (progress: 14%) * Chinese (Traditional) (zh-tw) (progress: 11%) * Dutch (nl) (progress: 1%) * French (fr) (progress: 1%) * German (de) (progress: 1%) * Indonesian (id) (progress: 1%) * Italian (it) (progress: 10%) * Korean (ko) (progress: 11%) * Norwegian (nb-no) (progress: 1%) * Persian (fa-ir) (progress: 6%) * Portuguese (pt-br) (progress: 29%) * Sinhala (si) (progress: 1%) * Spanish (es) (progress: 37%) * Turkish (tr) (progress: 5%) We want to thank everyone that contributed, translating or reviewing documents. And please, help promote this effort on your local user group, we always need more volunteers. ==== FreeBSD Handbook working group Contact: Sergio Carlavilla Chapters 1 to 6 have been updated. Chapter 7 is work in progress. ==== FreeBSD Website Revamp - WebApps working group Contact: Sergio Carlavilla Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components. FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21. The work will be divided into four phases: . Redesign of the Documentation Portal + Create a new design, responsive and with global search. (_Complete_) . Redesign of the Manual Pages on web + Scripts to generate the HTML pages using mandoc. (_Complete_) Public instance on https://man-dev.FreeBSD.org . Redesign of the Ports page on web + Ports scripts to create an applications portal. (_Work in progress_) . Redesign of the FreeBSD main website + New design, responsive and dark theme. (_Work in progress_) diff --git a/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc b/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc index 7fdac89f95..4f46a41f13 100644 --- a/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc +++ b/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc @@ -1,51 +1,51 @@ === DRM drivers (i.e. GPU drivers) Links: + -link:https://github.com/freebsd/drm-kmod[Git repository on GitHub] URL: link:https://github.com/freebsd/drm-kmod[https://github.com/freebsd/drm-kmod] + +link:https://github.com/freebsd/drm-kmod[Git repository on GitHub] URL: link:https://github.com/freebsd/drm-kmod[] + Contact: Emmanuel Vadot + Contact: Jean-Sébastien Pédron + Contact: The Graphics team GPUs are driven by DRM drivers. They are developed specifically for Linux using a permissive license. Our mission is to port those drivers to FreeBSD to make sure modern GPUs are fully supported. We didn't publish a report to share our progress for a long time. Therefore this status report entry will cover more than just the last quarter. ==== Update to Linux 5.15 LTS and Linux 5.16 As of this status report, the package:graphics/drm-kmod[] meta port still installs the DRM drivers from Linux 5.10 (released on December 13, 2020) on FreeBSD 13.1 and greater. This version of the driver lacks support for recent GPUs, in particular Intel 12th gen Alder Lake ones. In the past months, we worked to update the DRM drivers to bring support for more modern AMD and Intel GPUs. The `drm-kmod` Git repository `master` branch was first updated to Linux 5.15 (released on October 31, 2021). This is an LTS branch in Linux and we wanted to take advantage of that. Thus at that point, we followed two paths: * A `5.15-lts` branch was created to backport all bug fixes from Linux 5.15.x patch releases. This work is now available in the `drm-515-kmod` port. * The porting effort from subsequent Linux versions continued. The `master` branch is now at Linux 5.16 (release on January 9, 2022). The Intel driver from Linux 5.15 LTS supports 12th gen GPUs (Alder Lake). It looks to work on FreeBSD but we only tested it lightly so far. We still need more of that, that's why package:graphics/drm-kmod[] still installs package:graphics/drm-510-kmod[] instead of package:graphics/drm-515-kmod[]. At last, FreeBSD should run as a desktop on this GPU generation and several new AMD GPUs, though problems will surely appear through real test and use. In the process, we updated firmwares to link:https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git[linux-firmware] 20230210. ==== Linux 5.17 and future work DRM drivers from Linux 5.17 (released on March 20, 2022) were already ported but link:https://github.com/freebsd/drm-kmod/pull/236[this work still sits in its own branch]. A couple of issues block further testing and the merge into the `master` branch: * Our current integration with man:vt[4], the console/terminal driver, is quite far from the DRM drivers expectations which are based on Linux' fbdev KPI. Something changed in both the Intel and AMD drivers, meaning that man:vt[4] breaks with the 5.17 update. * The initial Linux 5.17 release does not contain the fixes backported to Linux 5.15 LTS. It seems quite unstable with the Intel 12th gen GPU mentioned earlier. To address the issue with our man:vt[4] integration layer, we started to link:https://github.com/freebsd/drm-kmod/pull/243[write a new vt backend specifically to use the fbdev callbacks exposed by the DRM drivers]. This backend will be provided with the DRM drivers, not the FreeBSD kernel, to make it easier to maintain as the drivers evolve. This is still a work in progress and locking in particular is tricky to get right. Regarding the bad support of Intel 12th gen in the 5.17 update, bug fixes backported to Linux 5.17.x patch releases will probably not be ported as part of this work. Instead we will focus on Linux 5.18 (released on May 22, 2022) and following. diff --git a/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc b/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc index 60b83e70bc..b76710cfc6 100644 --- a/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc +++ b/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc @@ -1,124 +1,124 @@ === FreeBSD Foundation Links: + -link:https://www.freebsdfoundation.org[FreeBSD Foundation] URL: link:https://www.freebsdfoundation.org[https://www.freebsdfoundation.org] + -link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://freebsdfoundation.org/blog/technology-roadmap/] + -link:https://www.freebsdfoundation.org/donate/[Donate] URL: link:https://www.freebsdfoundation.org/donate/[https://www.freebsdfoundation.org/donate/] + -link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/] + -link:https://www.freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.freebsdfoundation.org/journal/[https://www.freebsdfoundation.org/journal/] + -link:https://www.freebsdfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.freebsdfoundation.org/news-and-events/[https://www.freebsdfoundation.org/news-and-events/] +link:https://www.freebsdfoundation.org[FreeBSD Foundation] URL: link:https://www.freebsdfoundation.org[] + +link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] + +link:https://www.freebsdfoundation.org/donate/[Donate] URL: link:https://www.freebsdfoundation.org/donate/[] + +link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] + +link:https://www.freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.freebsdfoundation.org/journal/[] + +link:https://www.freebsdfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.freebsdfoundation.org/news-and-events/[] Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. ==== Fundraising Efforts We finally have our 2022 fundraising numbers in and we raised a total of $1,231,096! We were short of our goal, which forced us to pull around $74,000 from our longer term investments. Besides receiving a lot of donations from you our users and contributors, we received larger donations from Juniper, Meta, Arm, Netflix, Beckhoff, Tarsnap, Modirum, Koum Family Foundation, and Stormshield. I’d like to extend a heartfelt thank you on behalf of the Foundation to everyone, including individuals and corporations, for your financial contributions in 2022! This year our budget is around $2,230,000, which includes increased spending towards FreeBSD advocacy and software development. More than half our budget is allocated towards work directly related to improving FreeBSD and keeping it secure. To fund the 2023 budget, we increased our fundraising goal and plan on using some of our investment money. When we received our first million dollar donation, the plan was to use up to 10% of it each year to increase our work to improve FreeBSD, so this has been part of our funding plan for a few years now. The 2023 budget is in the process of being approved by the board of directors and will be published once it is approved. This quarter we received donations from Juniper, Tarsnap, Microsoft, and Stormshield. So, we are already off to a great start! But, we definitely need more to support our planned efforts for 2023. If you want to help us continue our efforts, please consider making a donation towards our 2023 fundraising campaign! -link:https://www.freebsdfoundation.org/donate/[https://www.freebsdfoundation.org/donate/] +link:https://www.freebsdfoundation.org/donate/[] We also have a Partnership Program for larger commercial donors. -You can read about it at link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/]. +You can read about it at link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[]. ==== OS Improvements During the first quarter of 2023, 226 src, 39 ports, and 12 doc tree commits identified the Foundation as a sponsor. Some of this sponsored work is described in separate report entries: * Continuous Integration * Enabling Snapshots on Filesystems Using Journaled Soft Updates * FreeBSD Release Engineering Team * Improve the kinst DTrace provider * OpenStack on FreeBSD Other Foundation-sponsored work included: * OpenSSH fixes and updates to versions 9.2p1 and 9.3p1 * a vendor import and update of libpcap to version 1.10.3 * improvements to tmpfs, msdosfs, and makefs * the addition of a new kqueue1 syscall * man page updates * dtrace and bhyve fixes * LinuxKPI work ==== Continuous Integration and Quality Assurance The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. You can read more about CI work in a dedicated report entry. A current project that is being funded by the FreeBSD Foundation is one to develop a set of scripts to help src developers conduct CI tests themselves. One of the main goals is to offer more visibility at the pre-commit stage. link:https://reviews.freebsd.org/D38815[A review for the first milestone] has been submitted. ==== FreeBSD Advocacy and Education Much of our effort is dedicated to the FreeBSD Project advocacy. This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups. We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. This all helps provide a healthy ecosystem. We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. We are back to attending events mostly in person and began planning the in person May 2023 Developer Summit, co-located with BSDCan. In addition to attending and planning events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD. Check out some of our advocacy and education work: * Hosted a stand at FOSDEM 2023, February 4-5, 2023 in Brussels, Belgium. Check out the link:https://freebsdfoundation.org/blog/fosdem-2023-conference-report/[trip report]. * Hosted a table at State of Open Con 2023, February, 7-8, 2023, in London, England. link:https://freebsdfoundation.org/blog/advocating-for-freebsd-around-the-world/[Read more] about it. * Sponsored, held a workshop and hosted a booth at SCALE 20x, in March 9-12, 2023, Pasadena, California. Check out the link:https://freebsdfoundation.org/blog/freebsd-at-scale-20x/[trip report]. * Sponsored Open Source 101, March 23 2023, in Charlotte, NC. * Sponsored and began planning the in-person link:https://wiki.freebsd.org/DevSummit/202305[May 2023 Developer Summit] taking place May 17-18, 2023 in Ottawa, Ontario * Secured our Media Partner sponsorship status and submitted a workshop for link:https://2023.allthingsopen.org/[All Things Open], October 15-17, 2023 in Raleigh, NC. * Submitted a Workshop proposal for link:https://sfconservancy.org/fossy/[FOSSY], July 13-16, 2023, in Portland, OR. * The FreeBSD Project was accepted as a link:https://summerofcode.withgoogle.com/programs/2023/organizations/the-freebsd-project[Participating Organization] for Google Summer of Code. * We held link:https://youtu.be/NpOkTR_d8os[GSoC Office Hours] to help prospective participants with questions. * Published link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-march-2023/[March Newsletter] * Additional Blog Posts ** link:https://freebsdfoundation.org/blog/under-the-hood-with-freebsd-and-ampere-altra/[Under the Hood with FreeBSD and Ampere Altra] ** link:https://freebsdfoundation.org/blog/under-the-hood-with-freebsd-and-ampere-altra/[New Open Position: FreeBSD Userland Software Developer] - Note: Posting is closed. ** link:https://freebsdfoundation.org/blog/bsdcan-2023-travel-grant-application-now-open/[BSDCan 2023 Travel Grant Application Now Open] - Note: Applications are closed * FreeBSD in the News: ** link:https://freebsdfoundation.org/news-and-events/latest-news/vmblog-state-of-open-con-qa-with-deb-goodkin/[VMBlog State of Open Con Q&A with Deb Goodkin] We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is now a free publication. -Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[https://www.FreeBSDfoundation.org/journal/]. +Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[]. -You can find out more about events we attended and upcoming events at link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDfoundation.org/news-and-events/]. +You can find out more about events we attended and upcoming events at link:https://www.FreeBSDfoundation.org/news-and-events/[]. ==== Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. -Go to link:https://www.freebsdfoundation.org[https://www.freebsdfoundation.org] to find more about how we support FreeBSD and how we can help you! +Go to link:https://www.freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2023-01-2023-03/fsx.adoc b/website/content/en/status/report-2023-01-2023-03/fsx.adoc index be4447a93b..def3b68468 100644 --- a/website/content/en/status/report-2023-01-2023-03/fsx.adoc +++ b/website/content/en/status/report-2023-01-2023-03/fsx.adoc @@ -1,18 +1,18 @@ === FSX Links: + -link:https://github.com/asomers/fsx-rs[GitHub] URL: https://github.com/asomers/fsx-rs[https://github.com/asomers/fsx-rs] + -link:https://www.freshports.org/devel/fsx/[FreshPorts] URL: https://www.freshports.org/devel/fsx/[https://www.freshports.org/devel/fsx/] +link:https://github.com/asomers/fsx-rs[GitHub] URL: https://github.com/asomers/fsx-rs[] +link:https://www.freshports.org/devel/fsx/[FreshPorts] URL: https://www.freshports.org/devel/fsx/[] Contact: Alan Somers The venerable FSX (File System eXerciser) tool, first written at Apple Computer in the nineties, has been a part of FreeBSD since 5.0. It stress tests file systems with a stream of randomly generated operations, verifying file data after every read. However, it has never been installed as part of the OS; it only exists in the source tree. That makes it difficult to use in CI pipelines. It has some other limitations, too. So this quarter I rewrote the entire tool in Rust. The rewrite is byte-for-byte compatible with the original, given identical seed values. Future versions will break backwards-compatibility, however, in order to add new features like `fspacectl` and `copy_file_range`. The new version can be found in the ports tree, and in time I'll remove the original. diff --git a/website/content/en/status/report-2023-01-2023-03/gcc.adoc b/website/content/en/status/report-2023-01-2023-03/gcc.adoc index e4a7b12242..f5936fef0f 100644 --- a/website/content/en/status/report-2023-01-2023-03/gcc.adoc +++ b/website/content/en/status/report-2023-01-2023-03/gcc.adoc @@ -1,24 +1,24 @@ === GCC on FreeBSD Links: + -link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] + -link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/] + -link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[https://gcc.gnu.org/gcc-12/] +link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[] + +link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] + +link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] Contact: Lorenzo Salvadore + Contact: Gerald Pfeifer The main news this quarter is the cleaning of old GCC versions from the ports tree: this will allow for a more efficient approach to bugs. ==== Deprecation of old GCC ports The ports tree still contains several ports related to old and unsupported GCC versions. They are usually needed as dependencies for a few old ports, that it would be better to either update to use a supported GCC release, or deprecate. link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269644[Bug reports] have been created to track the issue and work has already started towards its resolution. Thanks to all ports contributors who are helping. ==== Deprecation of USE_GCC=X+ Gerald, who maintained the GCC ports for many years until recently, still contributes to the GCC maintenance on FreeBSD by helping simplify the GCC infrastructure in the ports tree, for example by removing special cases that deal with old unsupported GCC versions. This quarter the most significant of his changes is probably link:https://cgit.freebsd.org/ports/commit/?id=9b5f5ab8482f105311d01a32260ef32bba4a2628[the removal of support for the `USE_GCC=X+` construct]: any port depending on GCC should set `USE_GCC=yes` if `GCC_DEFAULT` works; if not, it should require a specific version (e.g. `USE_GCC=11`); it cannot ask for a minimal version anymore (e.g. `USE_GCC=11+`). diff --git a/website/content/en/status/report-2023-01-2023-03/kde.adoc b/website/content/en/status/report-2023-01-2023-03/kde.adoc index db716d79da..18ef0b3a7b 100644 --- a/website/content/en/status/report-2023-01-2023-03/kde.adoc +++ b/website/content/en/status/report-2023-01-2023-03/kde.adoc @@ -1,52 +1,52 @@ === KDE on FreeBSD Links: + -link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] + -link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL:link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD] +link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[] + +link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL:link:https://community.kde.org/FreeBSD[] Contact: Adriaan de Groot The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine. The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack. ==== Infrastructure * The Qt5 ports were updated to the KDE patch collection release 5.15.8. * The Qt6 ports -- these are not used by KDE yet, but there are many ports that can use Qt6 and have Qt6 flavors -- were updated to release 6.4.2. Python bindings for the Qt6 release of WebEngine were added. * The cmake ports were updated to release 3.25.1 and the CPack generator for FreeBSD packages was repaired. * The package:graphics/poppler[] port -- used by many PDF-viewers -- was updated to release 23.01. * The package:sysutils/bsdisks[] port -- used as a shim for applications that expect Linux udisks, which means most desktop environments -- was updated to release 0.29. ==== KDE Stack KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. These (large) updates land shortly after their upstream release and are not listed separately. * KDE Frameworks updated to 5.104. * KDE Gear updated to 22.12.3. * KDE Plasma Desktop was updated to version 5.27. This was a long delayed update, due to unresolved issues in the support stack and a misplaced patch from an earlier release of KDE Plasma. Thanks to arrowd@ and Serenity Cybersecurity, LLC for sorting that out. * New port package:devel/ktextaddons[] was added to the tree. This is part of the KDE PIM suite, and slated to become a new KDE Framework in some future release. ==== Related Ports * package:audio/amarok[], one of the most popular KDE audio players of the early 2000's, has been marked deprecated in the ports tree. It is no longer maintained upstream. * package:astro/kstars[], an interactive planetarium, was updated to release 3.6.3. * package:devel/gitqlient[], a graphical user interface for git, was updated to release 1.6.1 with support for new git commands. * package:devel/okteta[], a hex viewer and editor for binary files, was updated to release 0.26.10. * package:devel/qcoro[], C++ coroutines with Qt support, was updated to release 0.8.0. * package:graphics/krita[], an application for painting and graphical work, was updated to release 5.1.5. * package:graphics/quickqanava[], a graph visualization library, got a real release and an update in the ports tree. * package:irc/kvirc[], an IRC client, was updated to the latest commit; there is no real release but there are bugfixes. * package:multimedia/haruna[], a video and audio player, was updated to release 0.10.3. * package:net-im/neochat[], one of a handful of Matrix clients, was updated to chase a new release of package:net-im/libquotient[]. There are continuing troubles with compatibility with older FreeBSD releases, leading to the KDE-FreeBSD team to declare FreeBSD 12 releases "effectively unsupported". * package:net-im/ruqola[], a Rocket Chat client, was updated to release 1.9.1. * package:security/keysmith[], a two-factor-authentication support application, was updated to release 23.01.0. diff --git a/website/content/en/status/report-2023-01-2023-03/kinst.adoc b/website/content/en/status/report-2023-01-2023-03/kinst.adoc index f1b0c2998b..94e7e72fe2 100644 --- a/website/content/en/status/report-2023-01-2023-03/kinst.adoc +++ b/website/content/en/status/report-2023-01-2023-03/kinst.adoc @@ -1,66 +1,66 @@ === Improve the kinst DTrace provider Links: + -link:https://reviews.freebsd.org/D38825[libdtrace: implement inline function tracing] URL: link:https://reviews.freebsd.org/D38825[https://reviews.freebsd.org/D38825] + -link:https://reviews.freebsd.org/D38732[dtrace(1): add -d flag to dump D script post-dt_sugar] URL: link:https://reviews.freebsd.org/D38732[https://reviews.freebsd.org/D38732] +link:https://reviews.freebsd.org/D38825[libdtrace: implement inline function tracing] URL: link:https://reviews.freebsd.org/D38825[] + +link:https://reviews.freebsd.org/D38732[dtrace(1): add -d flag to dump D script post-dt_sugar] URL: link:https://reviews.freebsd.org/D38732[] Contact: Christos Margiolis + Contact: Mark Johnston kinst is a new DTrace provider created by christos@ and markj@ that allows for arbitrary instruction tracing in a kernel function. kinst has been added to the base system in FreeBSD 14.0. link:https://www.freebsd.org/status/report-2022-07-2022-09/#_dtrace_instruction_level_dynamic_tracing[The 2022Q3 status report gives a brief introduction to kinst.] We're now working on inline function tracing (see review D38825 above) -- a much-requested DTrace feature -- by using kernel DWARF and ELF info to find the call sites of each inline copy and use that information to transform D syntax by turning kinst probes of the form: .... kinst::: // { } .... To: .... kinst:::, kinst:::, kinst::: // { } .... For example: .... # dtrace -dn 'kinst::cam_iosched_has_more_trim:entry { printf("\t%d\t%s", pid, execname); }' kinst::cam_iosched_get_trim:13, kinst::cam_iosched_next_bio:13, kinst::cam_iosched_schedule:40 { printf("\t%d\t%s", pid, execname); } dtrace: description 'kinst::cam_iosched_has_more_trim:entry ' matched 3 probes CPU ID FUNCTION:NAME 2 79315 cam_iosched_next_bio:13 0 kernel 2 79316 cam_iosched_schedule:40 0 kernel 0 79316 cam_iosched_schedule:40 12 intr 2 79315 cam_iosched_next_bio:13 0 kernel 2 79316 cam_iosched_schedule:40 0 kernel 0 79316 cam_iosched_schedule:40 12 intr ^C .... A new `-d` flag has also been added to man:dtrace[1] which dumps the D script after libdtrace has applied syntactic transformations. Further goals include: * Implement a `locals` structure in D which stores the local variables of the traced function. For example with `kinst::foo:`, we could print the local variable `bar` by doing `print(locals->bar)` inside a D script. * Port kinst to riscv and/or arm64. Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc b/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc index 38d02d7cad..d06ac09bf3 100644 --- a/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc +++ b/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc @@ -1,24 +1,24 @@ === PkgBase.live Links: + -link:https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/[Website (archive.org)] URL: link:https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/ + -link:https://codeberg.org/pkgbase/website[Website source] URL: link:https://codeberg.org/pkgbase/website[https://codeberg.org/pkgbase/website] +link:https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/[Website (archive.org)] URL: link:https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/[] + +link:https://codeberg.org/pkgbase/website[Website source] URL: link:https://codeberg.org/pkgbase/website[] Contact: Mina Galić PkgBase.live _was_ an unofficial repository for the FreeBSD link:https://wiki.freebsd.org/PkgBase[PkgBase project]. As a service, PkgBase.live was inspired by link:https://up.bsd.lv/[], which provides man:freebsd-update[8] for STABLE and CURRENT branches. Hardware for PkgBase was kindly sponsored by a member of the FreeBSD community. However, as life and projects moved on, they had to decommission the hardware, giving me three months' notice. In that time, my own life was rather turbulent after a recent move to a different country so I haven't been able to find a replacement. For the time being, PkgBase.live is dead. The website, and with it the link:https://codeberg.org/pkgbase/website/src/branch/main/howto/howdo.md[How Did She Do it?!] are still available in link:https://codeberg.org/pkgbase/website[Git]. I highly encourage copy-cats. I will also happily accept a new hardware sponsor! Please note that I _have_ contacted the FreeBSD Project, and they _are_ working on integrating PkgBase into release engineering. However, they are not yet ready, they also cannot "simply" take over PkgBase.live because it uses a completely different process. diff --git a/website/content/en/status/report-2023-01-2023-03/portmgr.adoc b/website/content/en/status/report-2023-01-2023-03/portmgr.adoc index 041036bb47..f870f49495 100644 --- a/website/content/en/status/report-2023-01-2023-03/portmgr.adoc +++ b/website/content/en/status/report-2023-01-2023-03/portmgr.adoc @@ -1,35 +1,35 @@ === 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/] +link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL: link: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[] + +link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[] + +link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link: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/[] 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 (through its subsidiary pkgmgr), and personnel matters. Below is what happened in the last quarter. Currently we have around 33,500 ports in the tree. For these ports, there are 3,021 open PRs of which 764 are unassigned. The first three months of this year saw 9,021 commits by 163 committers for the `main` branch and 701 commits by 55 committers for the `2023Q1` branch. Compared to 2022Q4, this means a slight increase in the number of ports, port PRs, ports commits, and active port committers. During the last quarter, we welcomed Robert Clausecker (fuz@), Vladimir Druzenko (vvd@), Robert Nagy (rnagy@), welcomed back Norikatsu Shigemura (nork@), and said goodbye to Marius Strobl (marius@). Portgmr added Muhammad Moinur Rahman (bofh@) as a new member after a successful lurkership. During the bi-weekly portmgr meetings, the following topics were discussed: * improving the situation of binary packages for kernel modules * ways to measure the impact of ports on its dependencies and how to maintain high-impact ports During the last quarter, 32 exp-runs were run to test port updates, updating default versions (LLVM to 15, MySQL to 8.0, Ruby to 3.1), and updating byacc in base. Furthermore, the default version of Go switched to 1.20 and that of Lazarus to 2.2.6. Four new USES were introduced: * budgie to support ports related to the Budgie Desktop * ldap to provide support for OpenLDAP, with a new default version of 26 (i.e. 2.6) * nextcloud to support Nextcloud applications * ruby to provide support for Ruby ports (formerly bsd.ruby.mk) diff --git a/website/content/en/status/report-2023-01-2023-03/pot.adoc b/website/content/en/status/report-2023-01-2023-03/pot.adoc index dd97422216..951eb14541 100644 --- a/website/content/en/status/report-2023-01-2023-03/pot.adoc +++ b/website/content/en/status/report-2023-01-2023-03/pot.adoc @@ -1,20 +1,20 @@ === 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] +link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[] Contact: Luca Pizzamiglio (Pot) + Contact: Bretton Vine (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/commits/master[pot] received a number of minor fixes but no new version has been released yet. 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. All Potluck images have been rebuilt to include the latest FreeBSD security advisories, a new link:https://github.com/bsdpot/potluck/tree/master/smokeping[Smokeping network latency monitoring image has been added], again a lot of work went into the link:https://github.com/bsdpot/potluck/tree/master/jitsi-meet[Jitsi] image, which unfortunately still seems to have some reliability issues. Also, two new blog posts are available showing how easy it is to use Potluck images, link:https://honeyguide.eu/posts/minio-beast-nextcloud/[one explaining how to set up Nextcloud with Minio as object storage and Prometheus for monitoring], link:https://honeyguide.eu/posts/openldap-matrix-blog-post/[one showing how to run your own Matrix Synapse server using OpenLDAP for access management]. As always, feedback and patches are welcome. diff --git a/website/content/en/status/report-2023-01-2023-03/releng.adoc b/website/content/en/status/report-2023-01-2023-03/releng.adoc index 9e57d2bbe1..c0ba1045cf 100644 --- a/website/content/en/status/report-2023-01-2023-03/releng.adoc +++ b/website/content/en/status/report-2023-01-2023-03/releng.adoc @@ -1,20 +1,20 @@ === FreeBSD Release Engineering Team Links: + -link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[https://www.freebsd.org/releases/13.2R/schedule/] + -link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[https://www.freebsd.org/releases/14.0R/schedule/] + -link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[https://download.freebsd.org/releases/ISO-IMAGES/] + -link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[https://download.freebsd.org/snapshots/ISO-IMAGES/] +link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[] + +link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[] + +link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] + +link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[] Contact: FreeBSD Release Engineering Team, The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. During the first quarter of 2023, the Release Engineering Team started work on the upcoming 13.2-RELEASE. As of this writing, the 13.2 cycle has followed the originally set schedule, with the addition of fourth, fifth and sixth RC builds, postponing the final release from the end of March to early April. The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/13*, and *stable/12* branches. Sponsor: Rubicon Communications, LLC ("Netgate") + Sponsor: Tarsnap + Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/timerfd.adoc b/website/content/en/status/report-2023-01-2023-03/timerfd.adoc index 9c6841d5de..b6d9ec7ee6 100644 --- a/website/content/en/status/report-2023-01-2023-03/timerfd.adoc +++ b/website/content/en/status/report-2023-01-2023-03/timerfd.adoc @@ -1,20 +1,20 @@ === Native Linux timerfd Links: + -link:https://reviews.freebsd.org/D38459[Differential revision] URL: link:https://reviews.freebsd.org/D38459[https://reviews.freebsd.org/D38459] +link:https://reviews.freebsd.org/D38459[Differential revision] URL: link:https://reviews.freebsd.org/D38459[] Contact: Jake Freeland The timerfd facility is a set of Linux-standard system calls that operate on interval timers. These timers are analogous to per-process timers but are represented by a file descriptor, rather than a process. These file descriptors may be passed to other processes, are preserved across man:fork[2], and may be monitored via man:kevent[2], man:poll[2], or man:select[2]. A timerfd implementation in FreeBSD already exists for Linux compatibility, but link:https://reviews.freebsd.org/D38459[this differential revision] makes the interface native. The goal behind this change is to ease the FreeBSD porting process for programs that include timerfd. This specific implementation avoids adding new names to the system call table. Instead, `timerfd_create()` is wrapped by the `specialfd()` system call. The `timerfd_gettime() and `timerfd_settime()` calls are wrapped `ioctl()` s. Developers that wish to support FreeBSD should avoid using timerfd. The `kqueue()` `EVFILT_TIMER` filter is preferred for establishing arbitrary timers. diff --git a/website/content/en/status/report-2023-01-2023-03/valgrind.adoc b/website/content/en/status/report-2023-01-2023-03/valgrind.adoc index 989b880182..f3aa176ee4 100644 --- a/website/content/en/status/report-2023-01-2023-03/valgrind.adoc +++ b/website/content/en/status/report-2023-01-2023-03/valgrind.adoc @@ -1,29 +1,29 @@ === Valgrind - Preparing for Valgrind 3.21 Links: + -link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[https://www.valgrind.org/] + -link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[https://www.valgrind.org/docs/manual/dist.news.html] +link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[] + +link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[] Contact: Paul Floyd The package:devel/valgrind-devel[] port had an intermediate update which was submitted on 2023-02-20. This contains most of what will be in the official release of Valgrind 3.21 which is due out shortly after this status report. There is a nice improvement to the vgdb interface. It's now much easier to see which bits of memory are initialized or not. There are a couple of fixes to the thread checks done by Helgrind. For FreeBSD specifically, the address space limit has been raised to be the same as Linux and Solaris on amd64. It was 32Gbytes and now it is 128Gbytes. The `kern.proc.pathname.PID` man:sysctl[3] has been fixed so that it returns the path of the guest exe and not that of the Valgrind host. At the same time I fixed some `_umtx_op` false positives and corrected auxv `AT_EXECPATH` in a way similar to `kern.proc.pathname.PID`. Syscall wrappers have been added for man:sctp_generic_sendmsg[2] and man:sctp_generic_recvmsg[2]. Not yet available in the ports versions of Valgrind, there is a workaround for the use of man:rfork[2]. Previously, since it is not supported, it would cause Valgrind to abort. Now it fails gracefully setting either EINVAL or ENOSYS. The main use of this system call is in man:posix_spawn[3], which will fall back to using man:vfork[2]. The man:mknodat[2] syscall wrapper was incorrectly implemented on i386 and has now been fixed. There is a reworking of all of the aligned allocation functions so that they behave less like Linux glibc and more like the Valgrind build platform.