[2 WEEKS LEFT REMINDER] Call for 2024Q3 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is September, 30th 2024 for work done since the last round of quarterly reports: July 2024 - September 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-07-2024-09/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2024-07-2024-09/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2024Q3 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Call for 2024Q3 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is September, 30th 2024 for work done since the last round of quarterly reports: July 2024 - September 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-07-2024-09/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2024-07-2024-09/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2024Q3 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
FreeBSD Status Report - Second Quarter 2024
FreeBSD Status Report Second Quarter 2024 Here is the second 2024 status report, with 20 entries. It has been very difficult to publish this status report within the usual schedule: indeed we are late. Unfortunately many of us have been busy with a lot of stuff, both inside and outside FreeBSD, thus some reports arrived late and report publication was slower than usual. Hopefully, this quarter was an exception and next quarter we will already be back on track, with 2024Q3 report published within October 2024. Have a nice read. Lorenzo Salvadore, on behalf of the Status Team. ━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2024-04-2024-06/ ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection • Projects □ Audio Stack Improvements □ FreeBSD GitHub Pull Request Report • Userland □ Capsicum-rs □ Service jails — Automatic jailing of rc.d services • Kernel □ Hierarchical rate limits for OpenZFS □ A low-cost conditional execution mechanism • Architectures □ FreeBSD/riscv64 • Cloud □ FreeBSD on Microsoft HyperV and Azure □ OpenStack on FreeBSD • Documentation □ Documentation Engineering Team • Ports □ GCC on FreeBSD □ KDE on FreeBSD □ FreeBSD Erlang Ecosystem Ports update • Third Party Projects □ Containers and FreeBSD: Pot, Potluck and Potman ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. DevSummit 202405 The Core Team has presented the status update at the DevSummit 202405. Details are available at https://wiki.freebsd.org/DevSummit/202405 Passing of Mike Karels It is with a heavy heart that we have learned of Mike Karels' recent passing. We want to offer our sincere condolences to his family, friends, and the community for this loss. Mike was an inspirational fellow developer and will be sorely missed. In Memory of Mike Karels. For more details about him, please visit the FreeBSD Foundation’s page at: https://freebsdfoundation.org/mike_karels/ 2024 Core Team Election Core.12 appointed Muhammad Moinur Rahman (bofh@) and Allan Jude (allanjude@) as the managers of the 2024 Core Team election. After Allan decided to run for Core, Moin continued to handle all the election tasks independently. The result was announced on June 12th, with 8 members: • Allan Jude (allanjude@) • Dave Cottlehuber (dch@) • Gleb Smirnoff (glebius@) • Hiroki Sato (hrs@) • Li-Wen Hsu (lwhsu@) • Mathieu Arnold (mat@) • Olivier Cochard (olivier@) • Tobias C. Berner (tcberner@) Mike Karels has run for the 2024 Core Team election, and was in the top nine candidates in the result. After a discussion, core.13 came to the conclusion that the eight members will serve as the new team. Core.13 takes office on June 12th, and hold the handover meeting with core.12 on June 21st. The project thanks the outgoing core.12 members for their service in the last two years: • Baptiste Daroussin (bapt@) • Benedict Reuschling (bcr@) • Ed Maste (emaste@) • Greg Lehey (grog@) • John Baldwin (jhb@) • Emmanuel Vadot (manu@) • Mateusz Piotrowski (0mp@) Commit bits • Core approved the src commit bit for Osama Abboud (osamaabb@) • Core reactivated the src commit bit for Ryan Libby (rlibby@) ━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://freebsdfoundation.org/ Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://freebsdfoundation.org/journal/ Foundation Events URL: https://freebsdfoundation.org/our-work/events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD. We do this in both technical and non-technical ways. We are 100% supported by donations from individuals and corporations and those investments help us fund the: • Software development projects to implement features and functionality in FreeBSD • Sponsor and organize conferences and developer summits to provide collabor
[LAST OFFICIAL REMINDER] Call for 2024Q2 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2024 for work done since the last round of quarterly reports: April 2024 - June 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-04-2024-06/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2024-04-2024-06/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2024Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
[2 WEEKS LEFT REMINDER] Call for 2024Q2 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2024 for work done since the last round of quarterly reports: April 2024 - June 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-04-2024-06/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2024-04-2024-06/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2024Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Call for 2024Q2 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2024 for work done since the last round of quarterly reports: April 2024 - June 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-04-2024-06/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2024-04-2024-06/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2024Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Re: gcc behavior of init priority of .ctors and .dtors section
On Thursday, May 16th, 2024 at 20:26, Konstantin Belousov wrote: > > gcc13 from ports > > `# gcc ctors.c && ./a.out init 1 init 2 init 5 init 4 init 3 main fini 3 > > fini 4 fini 5 fini 2 fini 1` > > > > The above order is not expected. I think clang's one is correct. > > > > Further hacking with readelf shows that clang produces the right order of > > section .rela.ctors but gcc does not. > > > > ``` > > # clang -fno-use-init-array -c ctors.c && readelf -r ctors.o | grep > > 'Relocation section with addend (.rela.ctors)' -A5 > clang.txt > > # gcc -c ctors.c && readelf -r ctors.o | grep 'Relocation section with > > addend (.rela.ctors)' -A5 > gcc.txt > > # diff clang.txt gcc.txt > > 3,5c3,5 > > < 00080001 R_X86_64_64 0060 init_65535_2 + 0 > > < 0008 00070001 R_X86_64_64 0040 init + 0 > > < 0010 00060001 R_X86_64_64 0020 init_65535 + 0 > > --- > > > > > 00060001 R_X86_64_64 0011 init_65535 + 0 > > > 0008 00070001 R_X86_64_64 0022 init + 0 > > > 0010 00080001 R_X86_64_64 0033 init_65535_2 + 0 > > > ``` > > > > The above show clearly gcc produces the wrong order of section > > `.rela.ctors`. > > > > Is that expected behavior ? > > > > I have not tried Linux version of gcc. > > Note that init array vs. init function behavior is encoded by a note added > by crt1.o. I suspect that the problem is that gcc port is built without > --enable-initfini-array configure option. Indeed, support for .init_array and .fini_array has been added to the GCC ports but is present in the *-devel ports only for now. I will soon proceed to enable it for the GCC standard ports too. lang/gcc14 is soon to be added to the ports tree and will have it since the beginning. If this is indeed the issue, switching to a -devel GCC port should fix it. Cheers, Lorenzo Salvadore
FreeBSD Status Report - First Quarter 2024
FreeBSD Status Report First Quarter 2024 Here is the first 2024 status report, with 21 entries. The New Year brings us many new interesting projects, such as the new libsys that separates system calls from libc and libpthread or work on a graphical installer for FreeBSD, which will help making our OS more user-friendly. Of course, the usual projects keep going on, such as the work on cloud-init, OpenStack, or the GCC ports. As usual our main teams share their progress with us. Have a nice read. Lorenzo Salvadore, on behalf of the Status Team. ━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2024-01-2024-03/ ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection • Projects □ Audio Stack Improvements □ Bhyve Improvements □ Graphical Installer for FreeBSD • Userland □ libsys □ PackageKit backend for FreeBSD pkg • Kernel □ iwlwifi(4) and wireless for 13.3-RELEASE • Architectures □ Ten64, WHLE-LS1, and HoneyComb • Cloud □ FreeBSD on Microsoft HyperV and Azure □ FreeBSD as a Tier 1 cloud-init Platform □ OpenStack on FreeBSD • Documentation □ Documentation Engineering Team • Ports □ FreshPorts: Notification of new packages □ GCC on FreeBSD □ Valgrind: port to arm64 on its way • Third Party Projects □ Containers and FreeBSD: Pot, Potluck and Potman ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. 13.3-RELEASE FreeBSD 13.3 was released on March 5th, 2024. The release announcement is at: https://www.freebsd.org/releases/13.3R/announce/ Along the release engineering team, the project dedicates the 13.3-RELEASE to Glen Barber, with thanks for his many years of contributions as Release Engineer. Future of 32-bit platform support Core announced Future of 32-bit platform support in FreeBSD for deprecating 32-bit platforms over the next couple of major releases. Commit bits • Core approved the src commit bit for Bojan Novković • Core reactivated the src commit bits for Mark Peek, Mark Murray, and Lawrence Stewart ━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://freebsdfoundation.org/ Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/ freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://freebsdfoundation.org/journal/ Foundation Events URL: https://freebsdfoundation.org/our-work/events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD. We do this in both technical and non-technical ways. We are 100% supported by donations from individuals and corporations and those investments help us fund the: • Software development projects to implement features and functionality in FreeBSD • Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD • Purchase and support of hardware to improve and maintain FreeBSD infrastructure • Resources to improve security, quality assurance, and continuous integration efforts • Materials and staff needed to promote, educate, and advocate for FreeBSD • Collaboration between commercial vendors and FreeBSD developers • Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity Operations We kicked off the new year with ambitious goals to help move the FreeBSD Project forward by identifying features and functionality to support in the operating system and increasing our advocacy efforts to increase and expand the visibility of FreeBSD. Stay tuned for a blog post that will provide more information on our 2024 goals and plans. We also published the 2024 Budget. In order to provide greater transparency about the budgeting process, we wrote a blog post that provides more details on how funding is allocated, new breakouts of some of the project expense categories, and more details on where the funding is going. OS Improvements During the first
[LAST OFFICIAL REMINDER] Call for 2024Q1 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2024 for work done since the last round of quarterly reports: January 2024 - March 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-01-2024-03/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2024-01-2024-03/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2024Q1 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
[2 WEEKS LEFT REMINDER] Call for 2024Q1 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2024 for work done since the last round of quarterly reports: January 2024 - March 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-01-2024-03/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2024-01-2024-03/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2024Q1 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Call for 2024Q1 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2024 for work done since the last round of quarterly reports: January 2024 - March 2024. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2024-01-2024-03/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2024-01-2024-03/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2024Q1 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
FreeBSD Status Report - Fourth Quater 2023
FreeBSD Status Report Fourth Quarter 2023 Here is the fourth 2023 status report, with 18 entries. This is the last 2023 quarter. As you have probably noticed, this status report comes later than usual and with fewer reports than the preceding quarter. Indeed, please keep in mind that the last quarter of every year is for many members of our community the quarter of the celebrations for Christmas and for the New Year, which implies that those members will spend more time with their families and will have less time for their favorite voluntary software projects. Thus there is less to report and reports tend to arrive later. But finally, here they are. Have a nice read. Lorenzo Salvadore, on behalf of the Status Team. ━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2023-10-2023-12/ ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection □ Bugmeister Team and Bugzilla • Userland □ Service jails — Automatic jailing of rc.d services • Kernel □ Packrat - NFS client caching on non-volatile storage • Architectures □ armv7 Ports Quality Assurance □ SIMD enhancements for amd64 • Cloud □ OpenStack on FreeBSD □ FreeBSD on Microsoft HyperV and Azure □ FreeBSD on EC2 • Documentation □ Documentation Engineering Team □ FreeBSD Online Editor and Man Page Editor □ FreeBSD Wiki • Ports □ KDE on FreeBSD □ State of GNOME 44 □ GCC on FreeBSD • Third Party Projects □ Containers and FreeBSD: Pot, Potluck and Potman ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. ━━━ FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. Along the release engineering team, the project dedicates the 14.0-RELEASE to the memory of Hans Petter Selasky. 14.0-RELEASE FreeBSD 14.0 was released at the end of 2023Q4. The release notes can be found at https://www.freebsd.org/releases/14.0R/relnotes/ New Release Engineering Team After years of serving as the release engineer gjb@ stepped down. cperciva@ took over as the new release engineer. karels@ is serving as the new deputy release engineer. Core would like to thank gjb@ for his long tenure and the many timely releases he created. FreeBSD 2024 Community Survey In the end of 2023, Core Team works with the Foundation to do the 2024 community survey. ━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://freebsdfoundation.org/ Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/ freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://freebsdfoundation.org/journal/ Foundation Events URL: https://freebsdfoundation.org/our-work/events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD. We do this in both technical and non-technical ways. We are 100% supported by donations from individuals and corporations and those investments help us fund the: • Software development projects to implement features and functionality in FreeBSD • Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD • Purchase and support of hardware to improve and maintain FreeBSD infrastructure, • Resources to improve security, quality assurance, and continuous integration efforts. • Materials and staff needed to promote, educate, and advocate for FreeBSD, • Collaboration between commercial vendors and FreeBSD developers, • Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. We supported FreeBSD in the following ways during the last quarter of 2023: OS Improvements During the fourth quarter of 2023, 236 src, 47 ports, and 33 doc tree commits identified The FreeBSD Foundation as a sponsor. Some of this Foundation-sponsored work is described in separate report entries: • OpenStack on FreeBSD • SIMD enhancements for amd64. Three new contractors started. Cheng Cui
[LAST OFFICIAL REMINDER] Call for 2023Q4 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is December, 31st 2023 for work done since the last round of quarterly reports: October 2023 - December 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q4 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
[LAST OFFICIAL REMINDER] Call for 2023Q4 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is December, 31st 2023 for work done since the last round of quarterly reports: October 2023 - December 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q4 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
[2 WEEKS LEFT REMINDER] Call for 2023Q4 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is December, 31st 2023 for work done since the last round of quarterly reports: October 2023 - December 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q4 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Call for 2023Q4 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is December, 31st 2023 for work done since the last round of quarterly reports: October 2023 - December 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-10-2023-12/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q4 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Re: Updating motherboard BIOS without MS Windows
On Saturday, November 11th, 2023 at 11:56, Nuno Teixeira wrote: > Hello all, > > Maybe not the best mailing to ask it but... > > How do you update BIOS without Windows since most brands only have bios > software to windows? > > I'm about to buy a new pc without windows license and I'm looking for brands > that have bios-cli that work in FreeBSD. > > Thanks, > Hello, I did such a thing about a year ago. I do not remember the details, but I think I had downloaded a windows exe file, then I extracted the firmware from it (I do not remember which software I used, maybe binwalk), I put it on a usb key and finally I installed it using the utility in the motherboard, available when powering the computer, before booting windows. Cheers, Lorenzo Salvadore
FreeBSD Status Report - Third Quarter 2023
FreeBSD Status Report Third Quarter 2023 Here is the third 2023 status report, with 32 entries. This is the summer quarter and thus it includes many interesting news from Google Summer of Code. Of course, we also have our usual team reports and many projects share with us their latest news. Much important work has been done for the first release of FreeBSD 14. Have a nice read. Lorenzo Salvadore, on behalf of the Status Team. ━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2023-07-2023-09/ ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Continuous Integration □ Ports Collection • Projects □ Filling gaps in the FreeBSD desktop experience □ LLDB Kernel Module Improvement • Userland □ OpenSSL 3 in base — Improved □ Login Classes Fixes and Improvements □ Process Visibility Security Policies □ Linux compatibility layer update • Kernel □ Enabling Snapshots on Filesystems Using Journaled Soft Updates □ SquashFS driver for FreeBSD kernel • Architectures □ NXP DPAA2 support □ SIMD enhancements for amd64 □ Integrate mfsBSD into the Release Building Tools • Cloud □ OpenStack on FreeBSD □ FreeBSD on Microsoft HyperV and Azure □ FreeBSD on EC2 • Documentation □ Documentation Engineering Team □ FreeBSD Online Editor and Man Page Editor □ FreeBSD Expert System • Ports □ KDE on FreeBSD □ Pantheon desktop on FreeBSD □ FreeBSD Office Team □ Wifibox: Use Linux to Drive your Wireless Card on FreeBSD □ GCC on FreeBSD □ Valgrind: valgrind-devel updated for FreeBSD 15 □ GitLab 16.3 Available □ PortOptsCLI — Ports Collection Accessibility • Third Party Projects □ Introducing the BSD Cafe project □ Containers and FreeBSD: Pot, Potluck and Potman ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. ━━━ FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. Demise of Hans Petter Selasky The FreeBSD Core Team would like to thank Hans Petter Selasky for his years of service. We were saddened by his death and joined the community in mourning. In Memoriam. Meetings with The FreeBSD Foundation The Core Team and The FreeBSD Foundation continue to meet to discuss the next steps to take for the management, development, and future of FreeBSD. The Core Team had two meetings with the Board of Directors, and employees of, the Foundation. They discussed how the Foundation can help the Core Team and the Project in general. Portmgr termlimits The Core Team discussed with the Ports Management Team the introduction of a time limit in which a developer can belong to the team. The proposal was approved by the Ports Management Team and will take effect at the beginning of 2024, with regular lurker programs to have a steady stream of new Ports Management Team members. Deprecation of 32-bit platforms for FreeBSD 15 Work is underway to mark support for 32-bit platforms as "deprecated" for FreeBSD 15. Matrix IM The testing of the Matrix instance and the Element-web client is still in progress. The beta is planned to be released after EuroBSDCon in September. Improve Commit Bit Expiration Policy The Core Team will clarify how to update the PGP key once a developer has become Alumni. EuroBSDCon Core Team members met with the FreeBSD Foundation in Coimbra during EuroBSDcon to discuss the direction of the Project. ━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://freebsdfoundation.org/ Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/ freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://freebsdfoundation.org/journal/ Foundation Events URL: https://freebsdfoundation.org/our-work/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 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 re
Re: compiling lang/gcc10 produces messages about signal 11 kills in /var/log/messages
Sent from Proton Mail mobile Messaggio originale Il 19 Ott 2023, 09:08, Matthias Apitz < g...@unixarea.de> ha scritto: El día miércoles, octubre 18, 2023 a las 08:45:16p. m. +0200, Matthias Apitz escribió: > > Hello salvad...@freebsd.org, > > I'm writing to you as MAINTAINER of the port lang/gcc10. > > When compiling the port lang/gcc10 with poudriere on a recent > 14.0-CURRENT system and very recent ports from git, I encounter > in /var/log/messages lines like these: > > Oct 18 17:44:45 jet kernel: pid 21011 (cc1plus), jid 169, uid 65534: exited on signal 11 (core dumped) > Oct 18 17:45:17 jet kernel: pid 30102 (cc1plus), jid 169, uid 65534: exited on signal 11 (core dumped) > ... I'm recompiling lang/gcc10 again with poudriere and while this is writing the log file .../latest-per-pkg/gcc10-10.4.0_1.log I attached another shell cmd which reads this log with tail -f and writes each line again to another file with a timestamp in front; looks like this: 08:21:31: ===> Installing existing package /packages/All/mpc-1.3.1_1.pkg 08:21:31: [140-CURRENT-ports20231014-job-01] Installing mpc-1.3.1_1... 08:21:31: [140-CURRENT-ports20231014-job-01] Extracting mpc-1.3.1_1: .. done 08:21:31: ===> gcc10-10.4.0_1 depends on shared library: libmpc.so - found (/usr/local/lib/libmpc.so) 08:21:31: ===> Returning to build of gcc10-10.4.0_1 08:21:31: === 08:21:31: === 08:21:31: = env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 08:21:31: ===> Configuring for gcc10-10.4.0_1 ... (still running). So at the end we can match the signal 11 lines from /var/log/messages exactly with what the make engine was doing at that time. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub Hello, I have reproduced your issue both on 13.2 and 14.0: https://cirrus-ci.com/build/5307810582364160 Please let me know what are the results of your tests. Then we will see if the issue needs more research or not. It might be that some test is being made and is expected to fail. In case we need to work on this, I suggest to file a bug report in bugzilla. Cheers, Lorenzo Salvadore
[LAST OFFICIAL REMINDER] Call for 2023Q3 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is September, 30th 2023 for work done since the last round of quarterly reports: July 2023 - September 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-07-2023-09/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-07-2023-09/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q3 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
[2 WEEKS LEFT REMINDER] Call for 2023Q3 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is September, 30th 2023 for work done since the last round of quarterly reports: July 2023 - September 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-07-2023-09/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-07-2023-09/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q3 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Re: sed in CURRENT fails in textproc/jq
--- Original Message ---
On Sunday, September 10th, 2023 at 13:51, Warner Losh wrote:
>
>
> On Sat, Sep 9, 2023, 10:51 PM Robert Clausecker wrote:
>
> > Greetings,
> >
> > I apologise for the inconvenience. The issue seems to boil down to
> > various places calling
> >
> > memchr(buf, c, SIZE_MAX);
> >
> > which causes an overflow when my newly written memchr() computes buf +
> > len to find the end of the buffer. A patch to alleviate this issue can
> > be found here:
> >
> > http://fuz.su/~fuz/freebsd/0001-lib-libc-amd64-string-memchr.S-fix-behaviour-with-ov.patch
> >
> > Please check if it does the trick for you. If yes, I'll go ahead and
> > push it tomorrow-ish.
>
>
>
> There are half a dozen or do kyua tests that are likely failing because of
> this or other reasons related to strings. When you push this fix you'll get
> the list. They are hidden among about 80 or so networking tests that fail. I
> plan on disabling those tests soon If no one fixes them.
>
> Warner
>
> >
> > Yours,
> > Robert Clausecker
> >
> > Am Sat, Sep 09, 2023 at 07:12:29PM +0200 schrieb Dag-Erling Smørgrav:
> > > Antoine Brodin writes:
> > > > Yuri writes:
> > > > > Either something has changed in sed(1) in CURRENT, or sed just fails
> > > > > during the configure stage of textproc/jq:
> > > > >
> > > > > sed: No error: 0
> > > > > checking for sys/cygwin.h... eval: ${+...}: Bad substitution
> > > > This seems to be a recent issue (less than 5 days).
> > > > Hundreds of configure scripts now fail to run on 15-current due to
> > > > this sed failure: [...]
> > >
> > > Try adding ARCHLEVEL=scalar to CONFIGURE_ENV on one of these. If that
> > > helps, yell at fuz@ :)
> > >
> > > DES
> > > --
> > > Dag-Erling Smørgrav - d...@freebsd.org
> > >
> >
> > --
> > () ascii ribbon campaign - for an 8-bit clean world
> > /\ - against html email - against proprietary attachments
> >
The issue seems to also affect lang/gcc14-devel:
https://pkg-status.freebsd.org/beefy18/data/main-amd64-default/pe88937b01dd4_s3482f57f0f/logs/gcc14-devel-14.0.0.s20230903.log
Cheers,
Lorenzo Salvadore
Call for 2023Q3 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is September, 30th 2023 for work done since the last round of quarterly reports: July 2023 - September 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-07-2023-09/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-07-2023-09/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q3 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Re: lang/gcc12 will not build on a host w/ 8 CPU and 16G mem
Hello, I am the port maintainer. It is a well known issue unfortunately. Just disable the LTO_BOOTSTRAP option and the build will succeed. Cheers, Lorenzo Salvadore Sent from Proton Mail mobile Messaggio originale Il 12 Ago 2023, 15:33, Matthias Apitz ha scritto: > I'm building on 14-CURRENT with poudriere. The server in question is a Dell > R210 with 8x 3.30GHz CPU and 15.8 GB memory: Aug 11 19:03:21 jet kernel: CPU: > Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz (3292.74-MHz K8-class CPU) Aug 11 > 19:03:21 jet kernel: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs Aug > 11 19:03:21 jet kernel: avail memory = 16582250496 (15814 MB) I have set swap > to 4GB + 10GB + 10GB: # swapctl -lh Device: Bytes Used: /dev/da0p3 4.0G 1.5G > /dev/md9 10G 1.5G /dev/md10 10G 1.5G and poudriere does use ZFS. Despite of > this relatively good equipped machine, lang/gcc12 can't be build. In > /var/log/messages after some 3 hours of compiling as a single(!) job in > poudriere: Aug 12 14:59:47 jet kernel: pid 57837 (lto1), jid 111, uid 65534, > was killed: a thread waited too long to allocate a page and the job fails in > poudriere with: ... xg++: fatal error: Killed signal terminated program lto1 > compilation terminated. lto-wrapper: fatal error: > /wrkdirs/usr/ports/lang/gcc12/work/.build/./prev-gcc/xg++ returned 1 exit > status compilation terminated. /usr/local/bin/ld: error: lto-wrapper failed > collect2: error: ld returned 1 exit status gmake[4]: *** > [/wrkdirs/usr/ports/lang/gcc12/work/gcc-12.2.0/gcc/cp/Make-lang.in:136: > cc1plus] Error 1 gmake[4]: *** Waiting for unfinished jobs What could I > do? matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ > +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
[LAST OFFICIAL REMINDER] Call for 2023Q2 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2023 for work done since the last round of quarterly reports: April 2023 - June 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-04-2023-06/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-04-2023-06/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
[2 WEEKS LEFT REMINDER] Call for 2023Q2 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2023 for work done since the last round of quarterly reports: April 2023 - June 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-04-2023-06/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-04-2023-06/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Re: OpenSSL 3.0 in the base system update
Thanks for the work and the update. May I suggest to submit the update to 2023Q2 status reports too? https://docs.freebsd.org/en/articles/freebsd-status-report-process/#_submit_your_report Cheers, Lorenzo Salvadore Inviato da Proton Mail mobile Messaggio originale Il 8 Giu 2023, 19:13, Ed Maste ha scritto: > As previously mentioned[1] FreeBSD 14.0 will include OpenSSL 3.0. We expect > to merge the update to main in the near future (within the next week or two) > and are ready for wider testing. Supported by the FreeBSD Foundation, Pierre > Pronchery has been working on the update in the src tree, with assistance > from Enji Cooper (ngie@), and me (emaste@). Thanks to Antoine Brodin > (antoine@) and Muhammad Moinur Rahman (bofh@) for ports exp-runs and > fixes/workarounds and to Dag-Erling (des@) for updating ldns in the base > system. ## Base system compatibility status Most of the base system is ready > for a seamless switch to OpenSSL 3.0. For several components we've added > `-DOPENSSL_API_COMPAT=0x1010L` to CFLAGS to specify the API version, > which avoids deprecation warnings from OpenSSL 3.0. Changes have also been > made to avoid OpenSSL APIs already deprecated in OpenSSL 1.1. We can continue > the process of updating to contemporary APIs after OpenSSL 3.0 is in the > tree. Additional changes are still required for libarchive and seven > Kerberos-related libraries or tools. Workarounds are ready to go along with > the OpenSSL 3 import, and proper fixes are in progress in the upstream > projects. A segfault from `openssl x509` in the i386 ports exp-run is under > investigation and needs to be addressed prior to the merge. ## Ports > compatibility With bofh@'s recent www/node18 and www/node20 patches the ports > tree is in reasonable shape for OpenSSL 3.0 in the base system. The exp-run > (link below) has a list of the failing ports, and I've emailed all of the > maintainers as a heads-up. None of the remaining failures are responsible for > a large number of skipped ports (i.e., the failures are either leaf ports or > are responsible for only a small number of skipped ports). I expect that some > or many of these will need to be addressed after the change lands in the src > tree. ## Call for testing We welcome feedback from anyone willing to test the > work in progress. Pierre's update can be obtained from the pull request[2] or > by fetching the branch[3]. If desired I will provide a large diff against > main. ## Links - Base system OpenSSL 3.0 update tracking PR: > https://bugs.freebsd.org/271615 - Ports exp-run with OpenSSL 3.0 in the base > system: https://bugs.freebsd.org/271656 [1] > https://lists.freebsd.org/archives/freebsd-current/2023-May/003609.html [2] > https://github.com/freebsd/freebsd-src/pull/760 [3] > https://github.com/khorben/freebsd-src/tree/khorben/openssl-3.0.9
Call for 2023Q2 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is June, 30th 2023 for work done since the last round of quarterly reports: April 2023 - June 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-04-2023-06/ (create it if it is missing); * submit a pull request at <https://github.com/freebsd/freebsd-doc>. You should put your reports in the directory doc/website/content/en/status/report-2023-04-2023-06/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoc template is available at <https://www.FreeBSD.org/status/report-sample.adoc>. We look forward to seeing your 2023Q2 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Re: FreeBSD Status Report - First Quarter 2023
--- Original Message --- On Wednesday, April 19th, 2023 at 4:26 PM, Lorenzo Salvadore wrote: > Last modified on: April 19, 2023 by Lorenzo Salvadore > > Legal Notices | © 1995-2023 The FreeBSD Project All rights reserved. The mark > FreeBSD is a registered trademark of The FreeBSD Foundation and is used by The > FreeBSD Project with the permission of The FreeBSD Foundation. Contact I am sorry for the footer: this should not have been included in the mail version of the status report, indeed it is the footer of the web page where the report is rendered: https://www.freebsd.org/status/report-2023-01-2023-03/ . Lorenzo Salvadore
FreeBSD Status Report - First Quarter 2023
FreeBSD Status Report First Quarter 2023 Here is the first status report of 2023, including 25 reports: we have our usual team reports, some news about cloud projects, progress in the src, ports and doc trees and more. We also provide some information about 13.2-RELEASE, which was postponed to the beginning of 2023Q2; but since this report is being published after the new version release, it is already available for installation. Users of RELEASE versions can now take advantage of many improvements such as better support for iwlwifi(4) driver or the new rtw88(4) driver, topics that have been covered in past status reports. Have a nice read. Lorenzo Salvadore, on behalf of the status team. ━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2023-01-2023-03/ ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection □ Status Team • Userland □ daemon(8) improvements • Kernel □ Enabling Snapshots on Filesystems Using Journaled Soft Updates in 13.2 □ Improve the kinst DTrace provider □ Native Linux timerfd • Architectures □ Kernel Address Sanitizer on AArch64 □ bsd-user: Upstreaming and Status Report • Cloud □ FreeBSD as a Tier 1 cloud-init Platform □ OpenStack on FreeBSD • Documentation □ Documentation Engineering Team □ The FreeBSD Russian Documentation Project • Ports □ Freshports: SQL Injection Attack and Help Request □ DRM drivers (i.e. GPU drivers) □ KDE on FreeBSD □ FSX □ GCC on FreeBSD □ Valgrind - Preparing for Valgrind 3.21 • Third Party Projects □ PkgBase.live □ Containers and FreeBSD: Pot, Potluck and Potman ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. Items Core Team Charter: Draft At the first Core Team meeting of 2023, Team delegates from the December 2022 meeting in Boulder, US presented the delegation’s conclusions to the entire Team. The Team will continue to discuss the issues and work together with the FreeBSD Foundation. FreeBSD annual developers survey The Core Team together with the FreeBSD Foundation have decided that the FreeBSD Foundation will be in charge of conducting the annual developers survey. Matrix IM solution The Core Team continues to evaluate Matrix as an IM solution for FreeBSD developers. An instance has already been prepared and tests are underway. Commit bits • Core approved the src commit bit for Cheng Cui (cc@) • Core approved the restore of the src commit bit for Joseph Koshy (jkoshy@). ━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://www.freebsdfoundation.org Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://www.freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/ freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://www.freebsdfoundation.org/journal/ Foundation News and Events URL: 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
[LAST OFFICIAL REMINDER] Call for 2023Q1 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2023 for work done since the last round of quarterly reports: January 2023 - March 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earlier you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-01-2023-03/ (create it if it is missing); * submit a pull request at https://github.com/freebsd/freebsd-doc . You should put your reports in the directory doc/website/content/en/status/report-2023-01-2023-03/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoctor template is available at https://www.FreeBSD.org/status/report-sample.adoc . We look forward to seeing your 2023Q1 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
[2 WEEKS LEFT REMINDER] Call for 2023Q1 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2023 for work done since the last round of quarterly reports: January 2023 - March 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earliest you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-01-2023-03/ (create it if it is missing); * submit a pull request at https://github.com/freebsd/freebsd-doc . You should put your reports in the directory doc/website/content/en/status/report-2023-01-2023-03/ (create it if it is missing); * send an email to status-submissi...@freebsd.org including your report. An AsciiDoctor template is available at https://www.FreeBSD.org/status/report-sample.adoc . We look forward to seeing your 2023Q1 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
Call for 2023Q1 status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Status Report update is March, 31st 2023 for work done since the last round of quarterly reports: January 2023 - March 2023. I would like to remind you that reports are published on a quarterly basis and are usually collected during the last month of each quarter, You are also welcome to submit them even earlier if you want, and the earliest you submit them, the more time we have for reviewing. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The following methods are available to submit your reports: * submit a review on Phabricator and add the group "status" to the reviewers list. You should put your reports in the directory doc/website/content/en/status/report-2023-01-2023-03/ ; * submit a pull request at https://github.com/freebsd/freebsd-doc . You should put your reports in the directory doc/website/content/en/status/report-2023-01-2023-03/ ; * send an email to status-submissi...@freebsd.org including your report. An AsciiDoctor template is available at https://www.FreeBSD.org/status/report-sample.adoc . We look forward to seeing your 2023Q1 reports! Thanks, Lorenzo Salvadore (on behalf of status@)
FreeBSD Status Report - Fourth Quarter 2022
FreeBSD Status Report Fourth Quarter 2022 The New Year has started and here is the last status report of 2022, including 34 reports. You will also notice that for the first time a new category has been introduced: the Cloud category. As FreeBSD keeps up to date with the latest technologies in IT, projects dealing with the cloud make steady improvements, and thus it has been judged that they deserve their own category in the status reports. The new category is not the only change about status reports. Indeed, the status team is revisiting its own workflow to become more efficient. If you are a report submitter, please ensure to read carefully the report authored by the status team as well as the next Call for Reports emails to keep up with the most recent changes. Have a nice read. Lorenzo Salvadore, on behalf of the status team. ━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2022-10-2022-12/ ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection □ Status reports: New workflow • Projects □ Console screen reader infrastructure □ Vessel - Integrated Application Containers for FreeBSD □ Enable the NFS server to run in a vnet prison □ Pytest support for the FreeBSD testing framework • Userland □ Base System OpenSSH Update • Kernel □ Enabling Snapshots on Filesystems Using Journaled Soft Updates □ Wireless updates □ Netlink on FreeBSD □ Adding basic CTF support to ddb • Architectures □ CheriBSD 22.12 release □ FreeBSD/riscv64 Improvements □ go on FreeBSD riscv64 □ FreeBSD/ARM64 on Xen • Cloud □ FreeBSD on Microsoft HyperV and Azure □ FreeBSD as a Tier 1 cloud-init Platform □ OpenStack on FreeBSD • Documentation □ Documentation Engineering Team □ FreeBSD Presentations and Papers • Ports □ FreshPorts - help wanted □ PortsDB: Program that imports the ports tree into an SQLite database □ KDE on FreeBSD □ Xfce on FreeBSD □ Pantheon desktop on FreeBSD □ Budgie desktop on FreeBSD □ GCC on FreeBSD □ Another milestone for biology ports • Third Party Projects □ Containers and FreeBSD: Pot, Potluck and Potman ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. Items Core Team Charter A delegation of the current core team is working together with some members of the previous Core Team to draft a core team charter. There was a face-to-face meeting in the US on December 3 - 4 to discuss the new charter. The delegation will present to the rest of the core team and discuss the details in the first quarter of 2023. The same delegation also had a meeting with the FreeBSD Foundation board on December 5th to discuss the collaboration details. Experimental Matrix IM solution The core team is working on evaluating Matrix as an instant messaging tool for the project. This will make the project’s communication channels less dependant on third parties. The service will be made available to the FreeBSD community to test and evaluate its validity at a later date. Committer’s Guide Deprecate BSD-2-Clause-FreeBSD and use BSD-2-Clause. For more information please refer to the commit. Commit bits • Core approved the src commit bit for Zhenlei Huang (zlei@) • Core approved the src commit bit for Corvin Köhne (corvink@) • Core approved the src commit bit for Sumit Saxon (ssaxena@) • Core approved the restore of the source commit bit for Paweł Jakub Dawidek (pjd@). ━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://www.freebsdfoundation.org Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://www.freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://www.freebsdfoundation.org/journal/ Foundation News and Events URL: 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
[LAST OFFICIAL REMINDER] Call for 2022Q4 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is December, 31st 2022 for work done since the last round of Quarterly Reports: October 2022 - December 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q4 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
[2 WEEKS LEFT REMINDER] Call for 2022Q4 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is December, 31st 2022 for work done since the last round of Quarterly Reports: October 2022 - December 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q4 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
Call for 2022Q4 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is December, 31st 2023 for work done since the last round of Quarterly Reports: October 2022 - December 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q4 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
[LAST OFFICIAL REMINDER] Call for 2022Q3 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is September, 30th 2022 for work done since the last round of Quarterly Reports: July 2022 - September 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q3 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
[2 WEEKS LEFT REMINDER] Call for 2022Q3 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is September, 30th 2022 for work done since the last round of Quarterly Reports: July 2022 - September 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q3 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
Call for 2022Q3 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is September, 30th 2022 for work done since the last round of Quarterly Reports: July 2022 - September 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q3 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
Re: Lots of port failures today?
--- Original Message --- On Thursday, August 18th, 2022 at 21:45, Larry Rosenman wrote: > > > https://home.lerctr.org:/build.html?mastername=live-host_ports&build=2022-08-18_13h12m51s > > circa 97ecdc00ac5 on main > Ideas? I don't know, but I can tell that I received two pkg-fallout mails today: one for gcc12 and the other one for gcc13-devel and none of them has been updated recently. So I guess something changed in one of their dependencies, which might have affected some other ports. Cheers, Lorenzo Salvadore
FreeBSD Quarterly Status Report - Second Quarter 2022
FreeBSD Quarterly Status Report Second Quarter 2022 Here is the second quarterly report of 2022, with 26 reports included. This quarter the quarterly team managed to publish the report much faster and, hopefully, with much fewer mistakes. If however you notice some errors, please report them so that we can correct them and also add some automatic checks in our tools to prevent them in the future and stay as efficient as possible in the pubblication process. We would also like to remind you that if for any reason you need more time to submit a quarterly report, the team will wait for you, but please warn us so that we are aware that some report is still missing. Many thanks to all those that have chosen to share their work with the FreeBSD community through the quarterly reports. Lorenzo Salvadore, on behalf of the status report team. ━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2022-04-2022-06/ ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection • Projects □ Linux compatibility layer update □ go on FreeBSD riscv64 □ FreeBSD on Microsoft HyperV and Azure • Userland □ Ongoing work on LLDB multiprocess debugging support □ ZFS support in makefs(8) □ Base System OpenSSH Update □ pf status update • Kernel □ ENA FreeBSD Driver Update □ New Bluetooth® configuration daemon: blued □ OpenVPN DCO □ Wireless updates □ Shared page address randomization • Architectures □ NXP DPAA2 support □ Medium-sized superpages on arm64 and beyond • Documentation □ Documentation Engineering Team • Ports □ KDE on FreeBSD □ Elsewhere □ GCC: updating GCC_DEFAULT and other improvements □ Valgrind - Numerous bugfixes and updates for 13.1 / 14.0 □ Pantheon desktop on FreeBSD □ Feature Complete Port of Intel’s igt-gpu-tools ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. The twelfth FreeBSD Core Team was elected by active developers. The core.12 members are: • Baptiste Daroussin (bapt, incumbent) • Benedict Reuschling (bcr) • Ed Maste (emaste, incumbent) • Greg Lehey (grog) • John Baldwin (jhb) • Li-Wen Hsu (lwhsu) • Emmanuel Vadot (manu) • Tobias C. Berner (tcberner) • Mateusz Piotrowski (0mp) On June 10th the outgoing core.11 and incoming core.12 teams held a handover meeting, and the new Core Team was announced on Jun 18. The current Core Team secretary, Muhammad Moinur Rahman (bofh), will step down after the appointment of a new Core Team secretary and handover tasks completes. In this quarter, src commit bits of Kornel Dulęba (kd) and Dmitry Salychev (dsl) have been approved. ━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://www.FreeBSDFoundation.org Technology Roadmap URL: https://FreeBSDFoundation.org/blog/technology-roadmap/ Donate URL: https://www.FreeBSDFoundation.org/donate/ Foundation Partnership Program URL: https://www.FreeBSDFoundation.org/ FreeBSD-foundation-partnership-program FreeBSD Journal URL: https://www.FreeBSDFoundation.org/journal/ Foundation News and Events URL: 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 First, I’d like to send a big thank you to everyone who gave a financial contribution to our efforts. We are 100% funded by your donations, so every contribution helps us continue to support FreeBSD in many ways, including some of the work funded and
[LAST OFFICIAL REMINDER] Call for 2022Q2 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is June, 30th 2022 for work done since the last round of Quarterly Reports: April 2022 - June 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q2 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
[2 WEEKS LEFT REMINDER] Call for 2022Q2 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is June, 30th 2022 for work done since the last round of Quarterly Reports: April 2022 - June 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q2 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
Re: FreeBSD Quarterly Status Report First Quarter 2022
--- Original Message --- On Saturday, June 11th, 2022 at 21:37, Lorenzo Salvadore wrote: > > > --- Original Message --- > On Saturday, June 11th, 2022 at 21:04, Dmitry Salychev d...@mcusim.org wrote: > > > > > Hi, > > > > So, you didn't like initial DPAA2 support :( > > > Of course we like it, but unfortunately, this quarter has been very difficult > for > the quarterly team and we had many errors. In that case, I made a typo in > the new automatic tools and the Architectures section disappeared. I counted > reports, but another typo in another report made me count it twice so I did > not > notice that yours was missing. > > I am fixing the issue and your report will soon appear on the website. > > I am very sorry. Your report is now online: https://www.freebsd.org/status/report-2022-01-2022-03/#_nxp_dpaa2_support Sorry again for the mistake, Lorenzo Salvadore
Re: FreeBSD Quarterly Status Report First Quarter 2022
--- Original Message --- On Saturday, June 11th, 2022 at 21:04, Dmitry Salychev wrote: > > > Hi, > > So, you didn't like initial DPAA2 support :( > Of course we like it, but unfortunately, this quarter has been very difficult for the quarterly team and we had many errors. In that case, I made a typo in the new automatic tools and the Architectures section disappeared. I counted reports, but another typo in another report made me count it twice so I did not notice that yours was missing. I am fixing the issue and your report will soon appear on the website. I am very sorry. Lorenzo Salvadore
FreeBSD Quarterly Status Report First Quarter 2022
FreeBSD Quarterly Status Report First Quarter 2022 As things are yet again settling into a new normal, it’s once again time for a status report for the FreeBSD Project. You may have noticed that this report is also a little on the late side, and it’s with regret that it’s taken this long to get to it - however, thanks to a few kind souls who’ve stepped up to the plate, in addition to the folks on the team who do things quietly in the background, future reports should hopefully be more on time. So let’s get some introductions in order, as yours truly is delighted to accept a hand from Pau Amma who already has been helping with reviews for a while, Lorenzo Salvadore who is stepping up to get some tooling in place to make it less of a chore to make the reports, as well as Sergio Carlavilla who is stepping up to help with all the work that can’t be easily automated. This report covers a very diverse set of topics including but not limited to accessibility, system boot speed-up, an implementation of GEOM union, changes to the WiFi situation, and many other things. We hope you’ll enjoy reading it! Daniel Ebdrup Jensen, on behalf of the status report team. ━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2022-01-2022-03/ ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection • Projects □ FreeBSD Accessibility □ Boot Performance Improvements • Kernel □ ENA FreeBSD Driver Update □ A New GEOM Facility, gunion □ Realtek Wireless driver support □ Intel Wireless driver support and LinuxKPI 802.11 compatibility layer □ Kernel Crypto changes to support WireGuard • Documentation □ Documentation Engineering Team • Ports □ KDE on FreeBSD □ Elsewhere □ FreeBSD Office Team □ lang/gcc* ports need some love and attention □ PortConfig □ Wifibox: Use Linux to drive your wireless card on FreeBSD • Third Party Projects □ helloSystem □ Containers and FreeBSD: Pot, Potluck and Potman □ Fpart and fpsync ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Foundation Links: FreeBSD Foundation URL: https://www.FreeBSDFoundation.org Technology Roadmap URL: https://FreeBSDFoundation.org/blog/technology-roadmap/ Donate URL: https://www.FreeBSDFoundation.org/donate/ Foundation Partnership Program URL: https://www.FreeBSDFoundation.org/ FreeBSD-foundation-partnership-program FreeBSD Journal URL: https://www.FreeBSDFoundation.org/journal/ Foundation News and Events URL: 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. Here are some highlights from the Foundation for the first quarter of 2022. Fundraising Efforts As promised, we updated our fundraising meter for 2022. So far, we’ve raised over $84,000 towards our 2022 goal of $1,400,000. We’d like to thank our individual and corporate donors for supporting our efforts this year. We’d also like to give a big shout out to our Gold Sponsor, Facebook, Silver Sponsors, VMware and Tarsnap, and the companies that provide free hosting for the Project: Bytemark, 365 Data Centers, NYI, NextArray, Sentex Data Communications, and the Computer Science Department at NCTU. You can find out how we spent your donations by reading about what we supported in Q1, in this report, and our Spring Newsletter. If you haven’t made a donation this year, please consider making a donation now at https://freebsdfoundation.org/donate/. We also have a Partnership Program for larger commercial donors. You can find out more at https://freebsdfoundation.org/our-donors/ freebsd-foundation-partnership-program/ OS Improvements During the first quarter of 2022
Call for 2022Q2 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is June, 30th 2022 for work done since the last round of Quarterly Reports: April 2022 - June 2022. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the AsciiDoctor template, fill it in, and email it to quarterly-submissi...@freebsd.org. The new AsciiDoctor template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.adoc We look forward to seeing your 2022Q2 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@)
[2 WEEKS LEFT REMINDER] Call for 2020Q2 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July, 1st 2020 for work done since the last round of Quarterly Reports: April 2020 - June 2020. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the Markdown template, fill it in, and email it to quarterly-submissi...@freebsd.org. The template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.md We look forward to seeing your 2020Q2 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@) ___ freebsd-quarterly-ca...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-quarterly-calls To unsubscribe, send any mail to "freebsd-quarterly-calls-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[FreeBSD-Quarterly-Calls] Call for 2020Q2 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July, 1st 2020 for work done since the last round of Quarterly Reports: April 2020 - June 2020. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the Markdown template, fill it in, and email it to quarterly-submissi...@freebsd.org. The template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.md We look forward to seeing your 2020Q2 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@) ___ freebsd-quarterly-ca...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-quarterly-calls To unsubscribe, send any mail to "freebsd-quarterly-calls-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD Quarterly Status Report - First Quarter 2020
I weekly report URL: https://hackmd.io/@FreeBSD-CI FreeBSD Jenkins wiki URL: https://wiki.freebsd.org/Jenkins Hosted CI wiki URL: https://wiki.freebsd.org/HostedCI 3rd Party Software CI URL: https://wiki.freebsd.org/3rdPartySoftwareCI Tickets related to freebsd-testing@ URL: https://preview.tinyurl.com/y9maauwg FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci Contact: Jenkins Admin Contact: Li-Wen Hsu Contact: freebsd-testing Mailing List Contact: IRC #freebsd-ci channel on EFNet The FreeBSD CI team maintains the continuous integration system and related tasks for the FreeBSD project. The CI system regularly checks the committed changes can be successfully built, then performs various tests and analysis of the results. The artifacts from the build jobs are archived in the artifact server for further testing and debugging needs. The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the codes or adjust test infrastructure. The details of these efforts are available in the weekly CI reports. During the first quarter of 2020, we continue working with the contributors and developers in the project for their testing needs and also keep working with external projects and companies to improve their support of FreeBSD. Important changes: * All the -head jobs are using clang/lld toolchain * All the -head test are using kyua in the base * RISC-V jobs now generate full disk image and run tests in QEMU with OpenSBI * freebsd-doc job also checks building of www.freebsd.org New jobs added: * https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/ * https://ci.freebsd.org/job/FreeBSD-head-powerpc64-images/ * https://ci.freebsd.org/job/FreeBSD-head-powerpc64-testvm/ Work in progress: * Collecting and sorting CI tasks and ideas here * Setup the CI stage environment and put the experimental jobs on it * Implementing automatic tests on bare metal hardware * Adding drm ports building test against -CURRENT * Testing and merging pull requests in the FreeBSD-ci repo * Planning for running ztest and network stack tests * Helping more 3rd software get CI on FreeBSD through a hosted CI solution * Adding non-x86 test jobs. * Adding external toolchain related jobs. * Adding more hardware to the hardware lab Please see freebsd-testing@ related tickets for more WIP information, and join the efforts Sponsor: The FreeBSD Foundation __ Ports Collection Links About FreeBSD Ports URL: https://www.FreeBSD.org/ports/ Contributing to Ports URL: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html FreeBSD Ports Monitoring URL: http://portsmon.freebsd.org/index.html Ports Management Team URL: https://www.freebsd.org/portmgr/index.html 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. During the last quarter the number of ports settled in at 39,000. There are currently just over 2,400 open PRs of which 640 are unassigned. The last quarter saw 8146 commits by 173 committers to the HEAD branch and 357 commits by 52 committers to the 2020Q1 branch. This means the number of PRs grew although the committer activity remained more or less constant. As always, people come and go. This time we welcomed Loïc Bartoletti (lbartoletti@), Mikael Urankar (mikael@), Kyle Evans (kevans@, who is already a src committer), and Lorenzo Salvadore (salvadore@, who we already know for compiling these reports you are reading right now). We said goodbye to dbn@ and theraven@, who we hope to see back in the future. On the infrastructure side, USES=qca was added and USES=zope was removed. The latter was also due to it was incompatible with Python 3, and portmgr is in the process of removing Python 2.7 from the Ports Tree. This means that all ports that currently rely on Python 2.7 need to be updated to work with Python 3 or be removed. After a long period of work by multiple people, Xorg got updated from the 1.18 to the 1.20 release series. Also, the web browsers were updated: Firefox to version 75.0, Firefox ESR to 68.7.0, and Chromium to 80.0.3987.149. The package manager itself got updated to version 1.13.2. antoine@ ran 29 exp-runs during the last quarter for various updates to KDE, poppler, pkg and build tools; and test compatibility with src changes: removing procfs-based debugging, fixing TLS alig
[LAST OFFICIAL REMINDER] Call for 2020Q1 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 1, 2020, for work done since the last round of Quarterly Reports: January, 2020 - March, 2020. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the Markdown template, fill it in, and email it to quarte...@freebsd.org. The template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.md We look forward to seeing your 2020Q1 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[2 WEEKS LEFT REMINDER] Call for 2020Q1 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 1, 2020, for work done since the last round of Quarterly Reports: January, 2020 - March, 2020. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the Markdown template, fill it in, and email it to quarte...@freebsd.org. The template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.md We look forward to seeing your 2020Q1 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Call for 2020Q1 quarterly status reports
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is April 1, 2020, for work done since the last round of Quarterly Reports: January, 2020 - March, 2020. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the Markdown template, fill it in, and email it to quarte...@freebsd.org. The template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.md We look forward to seeing your 2020Q1 reports! Thanks, Lorenzo Salvadore (on behalf of quarterly@) ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD Quarterly Status Report - Fourth Quarter 2019
FreeBSD Project Quarterly Status Report - Fourth Quarter 2019 Here is the last quarterly status report for 2019. As you might remember from last report, we changed our timeline: now we collect reports the last month of each quarter and we edit and publish the full document the next month. Thus, we cover here the period October 2019 - December 2019. If you thought that the FreeBSD community was less active in the Christmas' quarter you will be glad to be proven wrong: a quick glance at the summary will be sufficient to see that much work has been done in the last months. Have a nice read! -- Lorenzo Salvadore __ FreeBSD Team Reports * FreeBSD Core Team * FreeBSD Foundation * FreeBSD Release Engineering Team * Cluster Administration Team * Continuous Integration Projects * IPSec Extended Sequence Number (ESN) support * NFS Version 4.2 implementation * DTS Update * RockChip Support * Creating virtual FreeBSD appliances from RE VMDK images Kernel * SoC audio framework and RK3399 audio drivers * FreeBSD on Microsoft HyperV and Azure * FreeBSD on EC2 ARM64 * ENA FreeBSD Driver Update Architectures * PowerPC on Clang * NXP ARM64 SoC support Userland Programs * Linux compatibility layer update Ports * Ports Collection * KDE on FreeBSD * Java on FreeBSD * Electron and VSCode * Bastille * Universal Packaging Tool (upt) * Wine on FreeBSD Third-Party Projects * sysctlbyname-improved * pot and the nomad pot driver * 7 Days Challenge * NomadBSD __ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. * Julie Saravanos, the sister of Bruce D. Evans (bde), mailed core with the sad news that Bruce passed away on 2019-12-18 at the age of 68 years. Bruce was a deeply respected member of the community, served on the Core team, and made over 5,000 commits. Bruce's impact on our culture was so profound that new terminology was spawned. This is an excerpt of a message from Poul-Henning Kamp to Julie. I don't know precisely when I first communicated with Bruce, it was in the late 1980'ies via "UseNET", but I can say with certainty that few people have inspired me more, or improved my programming more, than Bruce he did over the next half of my life. All large projects invent its own vocabulary and in FreeBSD two of the neologisms are "Brucification", and "Brucified". A "brucification" meant receiving a short, courteous note pointing out a sometimes subtle deficiency, or an overlooked detail in a source code change. Not necessarily a serious problem, possibly not even a problem to anybody at all, but nonetheless something which was wrong and ought to be fixed. It was not uncommon for the critique to be considerably longer than the change in question. If one ignored brucifications one ran the risk of being "brucified", which meant receiving a long and painstakingly detailed list of every single one of the errors, mistakes, typos, shortcomings, bad decisions, questionable choices, style transgressions and general sloppiness of thinking, often expressed with deadpan humor sharpened to a near-fatal point. The most frustrating thing was that Bruce would be perfectly justified and correct. I can only recall one or two cases where I were able to respond "Sorry Bruce, but you're wrong there..." - and I confess that on those rare days I felt like I should cut a notch in my keyboard. The last email we received from Bruce is a good example of the depth of knowledge and insight he provided for the project: https://docs.freebsd.org/cgi/getmsg.cgi?fetch=1163414+0+archive/2019/svn-src-all/20191027.svn-src-all * The 12.1 release was dedicated to another FreeBSD developer who passed away in the fourth quarter of 2019, Kurt Lidl. The FreeBSD Foundation has a memorial page to Kurt. https://www.freebsdfoundation.org/blog/in-memory-of-kurt-lidl/ We send our condolences to both the families of Bruce and Kurt. * Core has documented The Project's policy on support tiers. https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/archs.html * Core approved a source commit bit for James Clarke. Brooks Davis (brooks) will mentor James and John Baldwin (jhb) will co-mentor. * The Project's first Season o
