From nobody Thu Feb 27 14:07:22 2025 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z3Y7z4mkZz5qF9K; Thu, 27 Feb 2025 14:07:43 +0000 (UTC) (envelope-from dch@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z3Y7z3qj3z3wrV; Thu, 27 Feb 2025 14:07:43 +0000 (UTC) (envelope-from dch@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740665263; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=h1TR4rxFFaNbiZHeTZ6hjflkG/SZSIQqRlQwRjAdTOQ=; b=mydzBLDyLMNBrECoabZKGTihDYmUtkxrLysCb3CFPDb5q48RfqwNmwIySMsozsSFs3ldL0 V94/Beo7pHT6f/j6f1CJZd079KmGJrQpA3003/GDKE3o+j9atyEux6Sl0XaOd+aZV3pN+S oR/qrJBZoc0uM+vizvIgxFj3hRAqnwntUy5XfEgywcq3LbMOJKogGDj52iyc1d/TbRCS0s y4j0KcbmxkWlhHVIo6mRi/dcOIzuLGysmatC97RFwwyUk6/qHVhSVcd3naAd3yDn+Etok3 so/oZr8lw4CJqWxLnt2jy6Z1J5nezMGiEY4oOecXmJuz8d7RiniUuSuWvZNAuA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740665263; a=rsa-sha256; cv=none; b=Y1oUiEENQNi35LhcAAjV0oT52jNhAl9g35AzqG+1yzqd0tskvN2ZYZIDMslaYziY+D/XzX tGhYinvh0IxMG5PM3Xts0nqsj++XHxW34Jha8gD3UI4EafXC4Myo1ohFq3Skn+crvSuwIF LJ1K/07QGVUz3aTU/pXJwJoA/vEv+F7MvTYnsbX6iXc0bCli2DREZAmPu/DHTM4saH4Xcp uJjLjSnnCIemz0XGcynnTlfPn43fLcYz6Iace2Mjl6Vm+niQrnqJcxAR4xQI4ZyQqoRNtP QWW6a0yiD1P7xrlHxQX4RXlkvBsTVOnDtxnwN40ctf+KULyG8gfsLl+79OIfpA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740665263; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=h1TR4rxFFaNbiZHeTZ6hjflkG/SZSIQqRlQwRjAdTOQ=; b=v7RYOdwyuH9KyWJWOneMcthK3ugWOkbAm9x2bThS61qEJWuSrKBQJXAN2Ja1W9/+/Fj17K NnArnbXEczDcBigO6LPbfwIW7IvM8Vcj6FhK4cRR+SxRBWH4KcbWi9fpWnuwhFoOenuZP9 e2Q1TgbnZVrvudtH8CKEE4ZZs/ErqtdSc8Q6DgmFxSlhl5a4Giaos+vANwcxczMIcZ19X3 WHJmqeTIp0lc/q/suMXbiBs+G6SqECMjNyhf+DIE7Rt7UVE7/Oog7WiWelAcVGDehfLD5o Ff0cfFsRFIEvt22RW8hVDaHMOBcHZhnAXliRUBoXXxn3+rO0G7XlJoJnlsBoaw== Received: from fauth-a1-smtp.messagingengine.com (fauth-a1-smtp.messagingengine.com [103.168.172.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: dch/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Z3Y7z2fwLz8mw; Thu, 27 Feb 2025 14:07:43 +0000 (UTC) (envelope-from dch@FreeBSD.org) Received: from phl-compute-10.internal (phl-compute-10.phl.internal [10.202.2.50]) by mailfauth.phl.internal (Postfix) with ESMTP id 244E11200043; Thu, 27 Feb 2025 09:07:43 -0500 (EST) Received: from phl-imap-02 ([10.202.2.81]) by phl-compute-10.internal (MEProxy); Thu, 27 Feb 2025 09:07:43 -0500 X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgdekjeeiiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefoggffhffvvefkjghfufgtgfesthejredtredt tdenucfhrhhomhepfdffrghvvgcuvehothhtlhgvhhhusggvrhdfuceouggthheshfhrvg gvuefuffdrohhrgheqnecuggftrfgrthhtvghrnhepffdukeelkeekueeludelteetvdeg ffejudelgedugfdtleehteelgeevtdefvdehnecuvehluhhsthgvrhfuihiivgeptdenuc frrghrrghmpehmrghilhhfrhhomhepuggthhdomhgvshhmthhprghuthhhphgvrhhsohhn rghlihhthidquddvgeeluddtfeeguddquddvudefuddujeejqdgutghhpeephfhrvggvue fuffdrohhrghesfhgrshhtmhgrihhlrdhfmhdpnhgspghrtghpthhtohephedpmhhouggv pehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqtghurhhrvghnthesfhhrvg gvsghsugdrohhrghdprhgtphhtthhopehfrhgvvggsshguqdhhrggtkhgvrhhssehfrhgv vggsshgurdhorhhgpdhrtghpthhtohepfhhrvggvsghsugdqshhtrggslhgvsehfrhgvvg gsshgurdhorhhgpdhrtghpthhtohepshgrlhhvrgguohhrvgesfhhrvggvsghsugdrohhr ghdprhgtphhtthhopehfrhgvvggsshgusehnhidqtggvnhhtrhgrlhdrohhrgh X-ME-Proxy: Feedback-ID: icedc46df:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id EE740B0006A; Thu, 27 Feb 2025 09:07:42 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Date: Thu, 27 Feb 2025 14:07:22 +0000 From: "Dave Cottlehuber" To: "Lorenzo Salvadore" , "FreeBSD Hackers" Cc: freebsd-current , "FreeBSD Stable" Message-Id: In-Reply-To: References: Subject: Re: FreeBSD Status Report - Fourth Quarter 2024 Content-Type: text/plain Content-Transfer-Encoding: 7bit On Thu, 27 Feb 2025, at 11:51, Lorenzo Salvadore wrote: > FreeBSD Status Report Fourth Quarter 2024 > > Here is the fourth and last 2024 status report, with 44 entries. > > It shows: 2024 has been a tremendously successful and busy year. Usually, one > would expect the final months in a year to be less busy, with people leaving > for holidays and New Years celebration. We still managed to deliver and see > great progress on so many things! > > Collecting and compiling this report took longer than planned, but it was worth > the wait. > > Thank you to the whole community for your amazing work and an especially big > thanks to those who contributed updates to this report! > > Enjoy the read! > > Chris Moerz, on behalf of the Status Team. Thanks Lorenzo, Chris, and everybody (including me ;-) who contributed a section, chased, curated, or edited the whole report as well. I am only half-way through. A+ Dave -- O for a muse of fire, that would ascend the brightest heaven of invention! From nobody Thu Feb 27 11:51:34 2025 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z3V6t5l3nz5q82s; Thu, 27 Feb 2025 11:51:34 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z3V6t4qcNz3prj; Thu, 27 Feb 2025 11:51:34 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740657094; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=AIo0flFKV+/50gUnIXtuiNm49bXt8EsgFkj6or4Gx2M=; b=Gd0cq2wSpLbE8gbh+2T/zi2qRYjWzS08jxNDO6zmuIXxvvmYqoFMYh5SgZA9U12PILA4m9 Rj2M8anWAdzUcXfcx1QHEEeUoM5zSNzSHf7IE5hf9H4cQT1gmBd/eqECXU8jIWhhYeqfBK Q0MYmtPcXfZ75oQiz5IfJMbImndE5wVcytNWcocVLXRaNVOMGsDjZYDvz2snVJgmrRna6x 8HFRJv3o495wZNT5PJzE29Wq8O+BHCJT5qk9zIJ5oOjOzmuQs3RHX8ptEVjLoSqpcxslcg eoUX9/4HVKlSqEtCj5SgbKrzQxmtZO8hwufmEGNBOdzSyu5O8hhS89r/TH5tVA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740657094; a=rsa-sha256; cv=none; b=ETUrx0v0aIlTV9xnSrO7HdDnyQDGt/OjyXpC3uZpd0xiulDKCa/KirbmOVwJ8hQg1MxV1S g0ch/obkXTWdR/Y3icHUO8CgkSnxjQJySNkXo3O1N6d7xcsrWKB5tsVVCuBpq2nf2OAbZy 9MJZEv3+HPhTjhq07oTtoEO5XlXV7dg3ESw6fOi9P2l234Hd+anNQ8MbsManLepOK72ete q5vDQmMPktLmVuSECIVv/51rQ7YvlMkhmNhtzyw/G4u/xYlertztB5pCwChzFzVIp+fj79 /Q13tyOXxq0EbSKGwqN1HXhmoB/gVDcIb2QsUXvwTZ7DKYsK0X5/xqsnsJzfvg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740657094; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=AIo0flFKV+/50gUnIXtuiNm49bXt8EsgFkj6or4Gx2M=; b=X5T727X39lbUXz+HsxJH9fX6tumbzoAMisOrwHfp1buqii6zQG53NY92ZOQFscWQ4LAXfk mLCmAaouubkvVVQIv6ru+P/vUvXvnkV8L70lCCWTl3hl6G6dGk9K0zf/EuO2b1+gwzq/is it0og/LQxph8YE/EHm9y0JxFs2xuAq22Zi18K1e7gEQ69zK62cx373/eaKyW4HHu4xgC/C yiTe4tuuyCRrp/4YETRjID8qqOt/gj/8AhLkuFtlmNTWqpfB9/uiAF//mUmjJwHxm2neaY UhbPVOMXOhIDtx/+ZSi/6I3ZpjKA4c/ikjJJ8B4894D9MbtFbC4B2xiGzoxyYQ== Received: by freefall.freebsd.org (Postfix, from userid 1472) id 8B8782065; Thu, 27 Feb 2025 11:51:34 +0000 (UTC) Date: Thu, 27 Feb 2025 11:51:34 +0000 From: Lorenzo Salvadore To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD Status Report - Fourth Quarter 2024 Message-ID: List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline; filename="report.txt" Content-Transfer-Encoding: 8bit FreeBSD Status Report Fourth Quarter 2024 Here is the fourth and last 2024 status report, with 44 entries. It shows: 2024 has been a tremendously successful and busy year. Usually, one would expect the final months in a year to be less busy, with people leaving for holidays and New Years celebration. We still managed to deliver and see great progress on so many things! Collecting and compiling this report took longer than planned, but it was worth the wait. Thank you to the whole community for your amazing work and an especially big thanks to those who contributed updates to this report! Enjoy the read! Chris Moerz, on behalf of the Status Team. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2024-10-2024-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 □ New srcmgr team • Projects □ Infrastructure Modernization □ Laptop Support and Usability Improvements Project □ Security engineering at the FreeBSD Foundation □ Security Audits □ Framework Laptop support • Userland □ PkgBase-motivated improvements to pkg □ Progress on the FreeBSD installer • Kernel □ Audio Stack Improvements □ mac_do(4), setcred(2), mdo(1) □ Suspend/Resume Improvements □ umb(4) driver for MBIM USB 4G/5G modems □ LinuxKPI 802.11 Wireless Update □ Wireless Update □ Syzkaller Improvement on FreeBSD • Architectures □ Pinephone Pro Support • Cloud □ FreeBSD on Microsoft HyperV and Azure □ OpenStack on FreeBSD □ Containers and FreeBSD: Cloud Native Buildpacks □ FreeBSD on EC2 • Documentation □ Documentation Engineering Team • Ports □ Ports Collection Accessibility - Colors Low Vision □ Containers and FreeBSD: AppJail, Director, OCI and more □ Improving Common Lisp Infrastructure in FreeBSD Ports □ FreeBSD Erlang Ecosystem Ports update □ Improve OpenJDK on FreeBSD □ Xfce on FreeBSD □ LXQt on FreeBSD □ GCC on FreeBSD □ Tor-Browser □ Greenbone Vulnerability Management Community Edition □ Wazuh on FreeBSD □ A bhyve management GUI written in Freepascal/Lazarus □ BSD-USER 4 LINUX • Third Party Projects □ Laptop and Desktop Work Group (LDWG) □ 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. Following up with the FreeBSD Foundation Core had a video conference with the FreeBSD Foundation on 2024-12-12 to follow-up on their in-person meeting held in Dublin during EuroBSDCon. Core and the Foundation continue discussing how to improve the collaboration and how to support developers and contributors: • The next round of community survey • Identifying projects where core would like help from the Foundation • Work on the technical roadmap with the Foundation Work in Progress Core is currently working on the following items: • Policy on generative AI created code and documentation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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 advancing FreeBSD through technical and non-technical support. Funded entirely by donations, the Foundation supports software development, infrastructure, security, and collaboration efforts; organizes events and developer summits; provides educational resources; and represents the FreeBSD Project in legal matters. The following report covers just some of the ways we supported FreeBSD in Q4. Deb Goodkin here. On behalf of the Foundation, I want to start out by saying thank you to this amazing community! Your financial contributions have allowed us to step up and take on some significant projects, including large, multi-phase software development work, greater security improvements, and important infrastructure improvements that will continue through 2025. We also increased our FreeBSD advocacy efforts over many different technical and social media platforms, including creating more content to promote and advocate for FreeBSD. You’ll find more information about all of this work below. For a more in-depth look at our efforts in 2024, be sure to check out the year-end blog posts and my year-end reflections in the advocacy section below. We are hiring! Check out our jobs page here for our Solutions Specialist and Technical Marketing Manager job postings. Plus, we are looking for part-time technical writers and will be opening up another position soon, so keep an eye on this page https://freebsdfoundation.org/open-positions/. We are still finalizing our 2024 fundraising numbers, but at this writing, we have raised around $1,324,000. You might be thinking, why do not we have a final tally now that it is 2025? First, we have not yet received all the checks postmarked 2024 . We are also waiting on a few payments from invoices issued last year. We will have a final report in the next quarterly status report. Thank you to the individuals and organizations that made a financial contribution in Q4! We received 325 donations from individuals totaling $120,841 and six financial contributions from organizations totaling $326,000. We also received a grant from the Silicon Valley Community Fund. I would also like to send a shoutout to the anonymous donor who wanted us to help get Framework laptops into developers' hands. Pietro Cerutti has been coordinating that effort, and we are close to finalizing the process with Framework so developers can place their orders directly with them. We also funded almost $5,000 worth of AV equipment for the BSDCon AV team to minimize the amount of equipment needed to rent at each of the two main BSD conferences. Now, back to our financials. We will be publishing 2024 financial documents and reports in Q1. Our updated Q1-Q3 2024 Financial reports will be published by the end of January and will better match the budget format. The Final 2024 financial reports will be published in early Q2. Going forward, our budget and financial reports will provide more details on how funding is allocated to the major software development projects. For example, we will include how much was spent on the laptop project each quarter. We are working with our accountant to improve our accounting systems to be more transparent on how we spend our money. We are excited about the opportunities for FreeBSD in 2025 and beyond, and are growing our team to help support the work needed to take advantage of these opportunities. However, we need your help to sustain this. Our investments will only carry on this work for a year or two at most. If your company is invested in the long-term sustainability of FreeBSD, please consider giving a financial contribution so we can ensure it stays the secure, reliable, and innovative platform you depend on. Not sure how to go about asking? Please reach out. We can help you navigate the process. Please go here to make a donation: https://freebsdfoundation.org/donate/. To find out more about our Partnership Program, go here: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/. Advocacy During the 4th quarter of 2024, we continued to raise awareness, advocate for the project, showcase users, while also providing educational content to the FreeBSD community. Here are some highlights of those efforts. • Sponsored and helped to organize the Fall 2024 FreeBSD Summit which took place November 7-8, 2024 in San Jose, CA. Check out the event recap. Videos are available on the FreeBSD YouTube channel. • Updated the community on two of the new releases: □ FreeBSD 13.4: What’s new, and how did we get here? □ FreeBSD 14.2: What’s new, and how did we get here? • Published the NYI Case Study • Shared the FreeBSD Foundation 2024 Report on the Security Audit of the Capsicum and bhyve subsystems. Learn more in the Security Audit. • Created a series of year end retrospectives on the work we did in 2024. □ Your Impact on FreeBSD: 2024 Milestones and What’s Next □ 2024: A Year of Advocacy and Growth for the FreeBSD Foundation □ Celebrating 2024’s Collaborative Achievements at the FreeBSD Foundation □ FreeBSD Foundation: A Year of Sponsored Development in 2024 □ Reflecting on a Successful 2024 • Published additional blogs including: □ Why Your Open Source Project Should Prioritize Security: Lessons from FreeBSD’s Proactive Approach □ Why FreeBSD Should Be the Foundation for Your Security Product □ Celebrating FreeBSD Day with Tara Stella: A Journey from Linux to FreeBSD □ Advancing Cloud Native Containers on FreeBSD: Podman Testing Highlights • Participated in the following contributed articles, interviews and podcasts: □ All Things Open Blog: Prioritizing Security: Lessons from FreeBSD’s Proactive Approach □ FreeBSD Foundation Releases Bhyve and Capsicum Security Audit Funded by Alpha-Omega Project □ Why We Use FreeBSD Over Linux: A CTO’s Perspective • Published the October 2024, November 2024, and December 2024 FreeBSD Foundation Newsletters. • Released the September/October 2024 issue of the FreeBSD Journal with HTML versions of the articles. OS Improvements During the fourth quarter of 2024, 382 src, 135 ports, and 17 doc tree commits identified The FreeBSD Foundation as a sponsor. The Foundation and its investment partners supported four major projects: • Konstantin Belousov continued work on an AMD IOMMU driver for FreeBSD, a project jointly funded by AMD and the Foundation. This effort aims to enhance support for large-core AMD systems and other scenarios requiring interrupt remapping. The driver was pushed to the src tree in early November and continues to undergo testing and refinement. • Alpha-Omega and the Foundation have been jointly funding a project to improve FreeBSD security. For the latest updates, refer to the Security Engineering at the FreeBSD Foundation entry for the latest updates. • A project to improve FreeBSD laptop usability began this quarter. For details, refer to the Laptop Support and Usability Improvements Project report entry. • Work commissioned by the Sovereign Tech Agency to modernize FreeBSD’s infrastructure continued this quarter. The goal of this work is to help achieve and sustain a manageable bug backlog. As part of this effort, The Foundation worked with Bitergia to analyze and assess open Bugzilla bugs. Muhammad Moinur Rahman finished porting Grimoirelab and deploying Grimoire in the FreeBSD cluster. Other projects: • Alfonso S. Siciliano provided a FreeBSD Accessibility Project update. • Aymeric Wibo began implementing suspend-to-idle and S0ix sleep support. • Bjoern A. Zeeb shared a LinuxKPI 802.11 Wireless Update. • Chih-Hsin Chang continued work to improve OpenStack on FreeBSD. • Christos Margiolis shared an update on work to improve the FreeBSD audio stack. • Harald Eilersten began working on a project to improve OpenJDK on FreeBSD. • Isaac Freund worked on PkgBase-motivated improvements to pkg. • Jian-Lin Li began a project to improve Syzkaller on FreeBSD. • Joseph Mingrone spent time on a personal project to improve Common Lisp support in the ports tree. • Olivier Certner submitted a report entry describing the work he completed with Baptiste Daroussin to allow controlled process credentials transitions using the MAC framework. • Pierre Pronchery returned to working on a umb(4) driver for MBIM USB 4G/5G modems and he shared an update on work to improve the FreeBSD Installer. • Tom Jones started porting the iwx WiFi driver from OpenBSD (via Haiku). Other members of the Foundation’s development team contributed to FreeBSD development efforts. For example: • Mitchell Horne worked with community contributor Julien Cassette to add a RISC-V Allwinner D1 clock and reset driver. • Chuck Tuffli, John Baldwin, and Pierre Pronchery fixed a few bhyve issues: □ bounds checks in hda_codec □ out-of-bounds read in NVMe log page □ infinite loop in queue processing □ buffer overflow in pci_vtcon_control_send □ robustness of TRIM handling. • In the ports tree, Muhammad Moinur Rahman converted USE_OCAML and USE_JAVA to the USES framework. • Ed Maste squashed a couple of makefs(8) bugs related to creating ISO9660 filesystems via the cd9660(4) driver: □ cd9660 filename buffer maximum length □ cd9660 duplicate directory names. Continuous Integration and Workflow Improvement As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project’s continuous integration system and test infrastructure. Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. Go to https://freebsdfoundation.org to find more about how we support FreeBSD and how we can help you! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Release Engineering Team Links: FreeBSD 14.2-RELEASE announcement URL: https://www.freebsd.org/releases/14.2R/announce/ FreeBSD 13.5-RELEASE schedule URL: https://www.freebsd.org/releases/13.5R/schedule/ FreeBSD releases URL: https://download.freebsd.org/releases/ISO-IMAGES/ FreeBSD development snapshots URL: https://download.freebsd.org/snapshots/ISO-IMAGES/ Contact: FreeBSD Release Engineering Team, The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. The Team managed 14.2-RELEASE, leading to the official RELEASE build and announcement in December. Planning has started for the upcoming 13.5-RELEASE cycle, which is expected to be the final release from the legacy stable/13 branch; as such it will include updates to "contrib" code and some bug fixes, but is not expected to have any significant new features. In addition to previously shipped release artifacts (ISO and memory stick images, VM images, cloud offerings, etc.) the Team is now also providing OCI compatible container images. The Release Engineering Team continued providing weekly development snapshot builds for the main, stable/14, and stable/13 branches. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cluster Administration Team Links: Cluster Administration Team members URL: https://www.freebsd.org/administration/#t-clusteradm Contact: Cluster Administration Team FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications. In this quarter, the team has worked on the following: • Regular support for FreeBSD.org user accounts. • Regular disk and parts support (and replacement) for all physical hosts and mirrors. • Cluster software refresh. • Moving more cluster services to Chicago. • Supporting the Grimoirelab dashboard effort. Cluster software refresh Except for the package builders and developer-facing ("dogfood") machines, the FreeBSD cluster mostly tracks stable/X branches. At the time of this writing, there are 131 physical machines in the cluster. We have 54 machines on current, 61 on stable/14 and 14 on stable/13. Work continues to upgrade the remaining stable/13 machines to stable/14. The stable/ 12 machines have been slated for decommissioning for a while; they do not run production workloads. The remaining machines are slated for upgrading or decommissioning in the near future. Of the 297 jails in the cluster, 222 are now on stable/14. 12.x: Regular 2, Jails 7 13.x: Regular 14, Jails 59 14.x: Regular 61, Jails 222 >15.x: Regular 54, Jails 9 Total: Regular 131, Jails 297 Total installations: 428 Running -RELEASE|{-p*}: 0 Total geographic sites: 15 Moving cluster services to Chicago Earlier this year, we started building up our new site in Chicago. This quarter, we began decommissioning older machines in New Jersey and moving services to the newer machines in Chicago. Our long-term goal is for Chicago to become our primary location. This work will take several more months to complete. FreeBSD Official Mirrors Overview Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America — California, Chicago, New Jersey (primary site), and Washington. Our mirror site in Taiwan is experiencing an extended outage. We hope to have it back online during the first quarter of 2025. Also during the first quarter of 2025, we expect a second mirror site in California, generously hosted by Sonic. The hardware and network connection have been generously provided by: • Cloud and SDN Laboratory at BroadBand Tower, Inc • Department of Computer Science, National Yang Ming Chiao Tung University • Equinix • Internet Association of Australia • Internet Systems Consortium • INX-ZA • KDDI Web Communications Inc • Malaysian Research & Education Network • MetaPeer • New York Internet • NIC.br • Teleservice Skåne AB • Your.Org New official mirrors are always welcome. We have noted the benefits of hosting single mirrors at Internet Exchange Points globally, as evidenced by our existing mirrors in Australia, Brazil, and South Africa. If you are affiliated with or know of any organizations willing to sponsor a single mirror server, please contact us. We are particularly interested in locations on the United States West Coast and throughout Europe. See generic mirrored layout for full mirror site specs and tiny-mirror for a single mirror site. Sponsors: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Continuous Integration Links: FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD CI Tinderbox view URL: https://tinderbox.freebsd.org FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org 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://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci dev-ci Mailing List URL: https://lists.FreeBSD.org/subscription/dev-ci Contact: Jenkins Admin Contact: Li-Wen Hsu Contact: freebsd-testing Mailing List Contact: IRC #freebsd-ci channel on EFNet In the fourth quarter of 2024, we worked with the project contributors and developers to address their testing requirements. Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. Important completed tasks: • Update main and stable/14 build environment to 14.2-RELEASE • Update stable/13 build environment to 13.4-RELEASE • Fixed an old but not revealed bug about pw(1) usage in jail setup. Work in progress tasks: • Designing and implementing pre-commit CI building and testing and pull/ merge-request based system (to support the workflow working group) □ Improving the src/tests/ci work to support running test suites ☆ Merging CI: Add full test support □ Merging Pre-commit CI with CIRRUS-CI • Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds • Simplifying CI/test environment setting up for contributors and developers • Setting up the CI stage environment and putting the experimental jobs on it • Redesigning the hardware test lab and adding more hardware for testing Open or queued tasks: • Collecting and sorting CI tasks and ideas • Setting up public network access for the VM guest running tests • Implementing use of bare-metal hardware to run test suites • Adding drm ports building tests against -CURRENT • Helping more software get FreeBSD support in its CI pipeline (Wiki pages: 3rdPartySoftwareCI, HostedCI) • Working with hosted CI providers to have better FreeBSD support Please see freebsd-testing@ related tickets for more WIP information, and do not hesitate to join the effort! Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Collection Links: About FreeBSD Ports URL:https://www.FreeBSD.org/ports/ Contributing to Ports URL: https://docs.freebsd.org/en/articles/contributing/#ports-contributing Ports Management Team URL: https://www.freebsd.org/portmgr/ Ports Tarball URL: http://ftp.freebsd.org/pub/FreeBSD/ports/ports/ Contact: Tobias C. Berner 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. In the last quarter, we welcomed Xavier Beaudouin (kiwi@) as a new ports committer. According to INDEX, there are currently 36,332 (down from 36,504) ports in the Ports Collection. There are currently about 3,368 (down from 3,379) open ports PRs, of which 809 are unassigned. The last quarter saw 10,640 commits (down from 11,594) by 155 committers (one less) on the main branch and 733 commits (down from 832) by 61 committers (down from 78) on the 2024Q4 branch. The number of ports also decreased (down from 36,504). The most active committers to main were: • 3867 sunpoet@FreeBSD.org • 1156 yuri@FreeBSD.org • 368 jbeich@FreeBSD.org • 361 bofh@FreeBSD.org • 273 fuz@FreeBSD.org • 247 fluffy@FreeBSD.org • 209 vvd@FreeBSD.org • 206 eduardo@FreeBSD.org • 201 rene@FreeBSD.org • 157 uzsolt@FreeBSD.org A lot has happened in the ports tree in the last three months, an excerpt of the major software upgrades are: • Default version of Lazarus switched to 3.6.0 • Default version of PHP switched to 8.3 • Chromium 131.0.6778.204 • Electron 33.3.0 • Firefox 134.0 • Firefox-esr 128.6.0 • KDE Frameworks 6.9.0 • KDE Plasma 6.2.4 • Qt6 6.8.1 • Python 3.9.21 • Python 3.10.16 • Python 3.11.11 • Ruby 3.2.6 • Ruby 3.3.6 • Rust 1.83.0 • SDL 2.30.10 • SDL 3.1.6 • Sway 1.10 Three new USES were introduced: • cl to provide support for Common Lisp ports. • java to provide support for Java. • sbrk to handle ports requiring sbrk() During the last quarter, pkgmgr@ ran 14 exp-runs to test various ports upgrades and changes to bsd.port.mk. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Bugmeister Team Links: FreeBSD Bugzilla URL: https://wiki.freebsd.org/Bugzilla Contact: Bugmeister In this quarter we came even closer to steady-state; we are dealing with incoming PRs more quickly these days. For reference: https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=90 The overall number of PRs came down from slightly over 11,600 to right at 11,000. This was due to work from several people to go over entire groups of PRs (see below). Mark Linimon attended several video calls with various src committers. They are doing some experimentation to learn what kind of effort is sustainable. The most recent effort was to evaluate the latest incoming src PRs; you will note that many of them from the past few weeks have been marked as requesting feedback. Bugmeister folks also did some passes through the database to clean up metadata: • reassigned bugs away from committers who had had their commit bits safekept over the last year. • cleaned up bugs for Product: Base System Status: In Progress. A number of these were not being actively worked on. The count is down to 184. □ In particular, Mark Linimon believes "assigned to mailing list" means "it is not really In Progress". Perhaps it has been discussed, but we do not really have a state for that. (We can make an argument that that itself is a bug.) □ We are now down to only a handful of the above, from "too many". The concept is to make sure In Progress has some real meaning. • evaluated PRs for mfc-stableN. In particular, any having mfc-stable12 had that flag cleared. □ The concept is to make sure these metadata have some real meaning as well: e.g. "a commit has been made and should be evaluated for MFCs". □ There are now a much smaller number of these. • closed numerous PRs as "Overcome By Events": □ (old version) + (contains the string "boot") □ (old version) + (contains the strings "alpha" or "beta") • evaluated "PR shows a commit" (possibly via Phabricator)" and "there was no trailing discussion". □ In a few cases of the above we simply assigned them and made sure that mfc-stable[13|14] was set, if it seemed appropriate. □ This does leave many that have a commit and then have trailing discussion. I think we will need more volunteers to go through those. • removed many of the 'patch' keywords from PRs. In the optimal case these should now be imputed by metadata in each attachment. In a few cases where patches are submitted inline instead of as an attachment, the keyword stays. There may be a few of these left over from the GNATS conversion. The use of inline patches should be discouraged, as automation has no way to detect them. Thanks to our triagers, especially Alexander Ziaee. There were various discussions about bug futures that came up in various video chats. One is that there is a (supported) successor to Phabricator, which itself is now no longer developed. Multiple groups will need to coordinate to evaluate it. Jan Bramkamp has volunteered to help with the task "automate harvesting PRs and evaluating whether they still apply". Mark Linimon to collaborate. Clusteradm@ helped us fend off yet another crawler site. While that was ongoing, bugzilla was nearly unusable due to timeouts, as were other services hosted on the same machine (wiki and cgit among others). We also welcomed our newest Triage member, Lexi (aka 'ivy' on Discord). Finally, glebius was added to bugmeister@ alias as core.13 liaison. See also: https://wiki.freebsd.org/Bugzilla/SearchQueries ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ New srcmgr team Contact: srcmgr A new source management team has been ratified by core@ to handle management of the FreeBSD src tree, akin to portmgr@ and doceng@ for the ports and docs trees, respectively. The initial members are Ed Maste, Mark Johnston, John Baldwin, and Warner Losh. srcmgr@ is currently focused on finding ways to make src developers more productive, and to try and manage the large numbers of bug reports and pull requests that we receive. The team meets every two weeks to discuss src-related issues and spend time triaging bug reports and pull requests. Meeting minutes are available on GitHub. The srcmgr@ team has a charter and is working on developing and documenting policies to help manage the src tree. In December, srcmgr@ ran an online bug-busting session, attended by 15 developers. We spent time going through recent bug reports, plus a list of older ones with patches. The team plans to host monthly sessions of this type, and aims to open them to a wider audience in the future. The team plans to develop a lurker program similar to portmgr@'s in the first half of 2025. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Projects Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Infrastructure Modernization Contact: Ed Maste Contact: Alice Sowerby The project started in Q3 of 2024 and was commissioned by the Sovereign Tech Agency with a budget of $745,000, to be spent over about one year. The main goals are to improve security tools for the base system, ports, and packages, update the project’s infrastructure to speed up development, enhance build security, and make it easier for new developers to get started. Q4 update • Work Package A: Technical Debt reduction. The Foundation collaborated with the Source Management team to commission and deploy a number of dashboards that characterize the bug backlog for the FreeBSD Project. These were created to the team’s specifications by our project partner, Bitergia, who used an open source tool called GrimoireLab to create the dashboards. Foundation staff have hosted the dashboards on a FreeBSD deployment and they can be seen at https://grimoire.freebsd.org/. More information about the dashboards can be found at https://github.com/freebsd/grimoire. The Source Management team has also used these dashboards to support their new, evolving approach to bug triage and it has been included as a key tool for collaborative bug-squashing events. • Work Package B: Zero Trust Builds, and Work Package C: CI/CD Automation. The Foundation collaborated with various key management and administration teams within the FreeBSD Project to co-create the details of the scope for these two projects. They are scheduled to start in January and will conclude in Q2/3. • Work Package D: Security Controls in Ports and Packages, and Work Package E: Improve Software Bill of Materials (SBOM). These have not started yet as they are scheduled for February and March starts respectively. Commissioning body: Sovereign Tech Agency ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Laptop Support and Usability Improvements Project Contact: Ed Maste Contact: Alice Sowerby The project began in Q4 of 2024 and is funded by the FreeBSD Foundation and Quantum Leap Research. It has a budget of $750,000, which will be used over one to two years. The goal is to improve key features like WiFi, audio usability, suspend and resume functions, graphics, and Bluetooth. The team will also create clear documentation and step-by-step guides to help people use the new features. Q4 Update • The Foundation initiated the project, created a public roadmap, and allocated contractors to relevant workstreams. December was the first monthly iteration of development, covering: □ Implement S0ix low power states □ Put a VM into hibernation □ Create a list of supported laptops □ Create a translation layer for Linux drivers on FreeBSD □ Create a list of supported window environments □ wireless_update,POC driver for Intel WiFi interfaces (based on OpenBSD/ Haiku) □ Resolve tech debt in pkg to enable PkgBase development □ Document how to update graphic drivers □ Implement s2idle low power state □ Bring in camera code donation from Dell • The FreeBSD project started a community group called the "Laptop and Desktop Working Group" (LDWG) to help people working on Laptop- and Desktop-related projects to connect and collaborate with others in the community working on similar efforts. The group held its first monthly meeting in December 2024. To stay updated on LDWG activities, you can join the Desktop mailing list. Sponsor: The FreeBSD Foundation Sponsor: Quantum Leap Research ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Security engineering at the FreeBSD Foundation Links: FreeBSD Foundation Releases Bhyve and Capsicum Security Audit Funded by Alpha-Omega Project URL: https://freebsdfoundation.org/news-and-events/latest-news/ freebsd-foundation-releases-bhyve-and-capsicum-security-audit-funded-by-alpha-omega-project / How FreeBSD security audits have improved our security culture URL: https://fosdem.org/2025/schedule/event/fosdem-2025-6152-how-freebsd-security-audits-have-improved-our-security-culture / Home of the ORC WG URL: https://github.com/orcwg/orcwg FreeBSD Foundation: Contact Us URL: https://freebsdfoundation.org/about-us/contact-us/ Open Source Vulnerability schema (OSV Schema) URL: https://openssf.org/projects/osv-schema/ ossf/osv-schema tools: import a conversion tool to and from VuXML (#237) URL: https://github.com/ossf/osv-schema/pull/237 Contact: Pierre Pronchery My tasks at the FreeBSD Foundation continue to revolve around Security Engineering for the FreeBSD Project. First, we keep working on the outcome of the source code audit on bhyve and Capsicum, documenting and researching how to prevent and mitigate similar issues from occurring again in the future. This includes the processes relevant for contributions to the FreeBSD Project, as well as the preparation of a joint presentation with Alpha-Omega at the BSD Devroom during the coming FOSDEM conference in 2025. At the same time, I am liaising with the Open Regulatory Compliance Working Group (ORC WG), where an FAQ is being elaborated jointly by a number of stakeholders on the European Union’s newly introduced Cyber Resilience Act (CRA). This is all related to our ongoing collaboration with OpenSSF, notably the self-assessment initiative; note that the FreeBSD Foundation can provide assistance in this regard for projects deploying FreeBSD. Finally, possibilities around the integration of OSV tooling into the FreeBSD ecosystem are under investigation as well. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Security Audits Contact: Ed Maste Contact: Alice Sowerby The project began in Q2 of 2024 and was funded by Alpha Omega with a budget of $137,500, which was used over about six months and is now complete. The focus was on conducting a code audit for key subsystems, bhyve and Capsicum, as well as performing a security audit of the development process. The funds were used to hire a specialist offensive security firm to perform the code audit, to contract developers to address issues found, and for Foundation staff’s work on both audits. Q4 update The project is complete. The Code Audit and subsequent reports were released after the related Security Advisories were published. The Process Audit is complete. It was created by FreeBSD Foundation staff who ran an outreach exercise to gather information about the current FreeBSD development process. The teams consulted were: Security Team, Source Management Team, Cluster Administrators, Release Engineering Team. Information was gathered through an online long-form survey which was structured around existing frameworks for analysing security in software development. Teams were asked to describe current development processes and appraise the current security practices, as well as to make suggestions for improvements. The responses were collated and synthesised into the report by Foundation staff. The report was reviewed for accuracy by the original respondents. The report will now be made available to the Security Team and other teams previously mentioned, as well as to the Foundation executive team. This will be a useful tool in identifying areas for investment and prioritisation going forward as more security projects are planned and funded. The report is intended primarily for FreeBSD Project and Foundation planning purposes and as such there is no plan to promote it to an external audience. Interested readers should contact the Security Team to request a copy of the report. To learn about the project, and to see historical monthly updates visit: https://github.com/ossf/alpha-omega/tree/main/alpha/engagements/2024/FreeBSD. Sponsor: Alpha Omega Project ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Framework Laptop support Links: Framework Laptop page on FreeBSD Wiki URL: https://wiki.freebsd.org/Laptops/Framework_Laptop/ Guide on installing and using FreeBSD on Framework systems URL: https://github.com/FrameworkComputer/freebsd-on-framework Tracking ticket: Framework Laptop: Feature support, bugs and improvements URL: https://bugs.freebsd.org/262152 Contact: Daniel Schaefer Contact: Li-Wen Hsu Contact: Sheng-Yi Hong For a long time, Framework Laptop Inc is friendly to the FreeBSD project in many aspects, including providing engineering samples to Foundation for testing and working on support. Since 2024 summer, there are several small hackathons in Framework’s Taipei office on testing FreeBSD on different models of Framework laptop, and the peripheral devices. Sheng-Yi is using the laptop provided by Framework Computer to add more device support, e.g. d3b05d0ea10a: Add smbus and i2c device IDs for Meteor Lake. Daniel from Framework Computer Inc started a repository under Framework Computer’s GitHub organization to keep the notes of installation and miscellaneous information. He fixed fingerprint readers (libfprint) not just for Framework, but in general on FreeBSD. And working on the support and fix to many related drivers on FreeBSD. In November, Foundation people and some FreeBSD developers visited Framework’s San Francisco office and had a meeting for checking the current FreeBSD support status and discussing the possible future collaboration plans. Foundation will continue working on improving the general laptop support and using Framework as one of the target platforms for the Laptop Support and Usability Project. Sponsor: The FreeBSD Foundation for Li-Wen’s work Sponsor: Framework Computer Inc for Daniel’s work, hardware and space support ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Userland Changes affecting the base system and programs in it. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PkgBase-motivated improvements to pkg Contact: Isaac Freund Some problems blocking progress on the PkgBase project are caused by shortcomings of pkg(8). The primary goal of my work on pkg is to unblock PkgBase progress. However, all users of pkg will benefit even if they do not use PkgBase. The scheduler for pkg’s install/upgrade/delete jobs has been rewritten, motivated by solving PR259785. The new scheduler models the scheduling problem as a directed graph and splits upgrade jobs into delete/install halves only when necessary to break a cycle in the graph. This formal model gives strong guarantees about ordering that the old scheduler was not able to provide and prevents unnecessary splitting of upgrade jobs. It also fixes longstanding bugs where the old scheduler would bail out and cause the entire upgrade to fail. The new scheduler is included in pkg version 1.21.99.3 (pkg-devel). The rest of my work this quarter has been related to pkg’s automatic tracking of shared library dependencies, which PkgBase heavily relies on. The initial motivating problem was PR265061 but it was necessary to make more fundamental changes to how pkg tracks shlibs before cleanly solving that problem became possible. When a package is created with pkg-create(8), pkg scans the included files and generates shlibs_provided/shlibs_required lists based on the executables/shared libraries found. Before my changes, pkg would use the elf hints file of the host system as an input to pkg-create in order to filter out shlibs provided by the base system from the generated shlibs_required list. An ALLOW_BASE_SHLIBS option disabled this filtering for the purpose of building PkgBase packages. After my changes, pkg-create no longer reads the elf hints file of the host system and base system shlibs are included in the generated shlibs_required list. When pkg-install(8)/pkg-upgrade(8)/etc. invoke the solver on an non-PkgBase system, pkg generates a list of shlibs provided by the base system as an input to the solver by scanning /lib and /usr/lib. On a PkgBase system, the PkgBase packages provide all base system shlibs. This allows the ALLOW_BASE_SHLIBS option to be eliminated. It also gives better integration between the ports packages and PkgBase packages as shlib dependencies of ports packages on PkgBase packages are now tracked rather than ignored. Finally, this change significantly simplifies the pkg codebase and improves portability. This change was implemented in https://github.com/freebsd/pkg/pull/2386 and is not yet included in a pkg release. With that change and other internal improvements I was able to add support for tracking lib32 and Linuxulator shlibs, which should resolve the problem that originally motivated my work on pkg’s shlib handling (PR265061). This support is implemented in https://github.com/freebsd/pkg/pull/2387 and is not yet included in a pkg release. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Progress on the FreeBSD installer Links: Improving Repair Ability of the FreeBSD Installer URL: https://wiki.freebsd.org/SummerOfCode2024Projects/ImprovingRepairAbilityOfTheFreeBSDInstaller GSoC 2024 - Improving Installer with Repair and Upgrade Ability (#1395) URL: https://github.com/freebsd/freebsd-src/pull/1395 bsdinstall: Add pkg install support in live env (#1424) URL: https://github.com/freebsd/freebsd-src/pull/1424 bsdinstall: Add repair scripts to installer menu (#1427) URL: https://github.com/freebsd/freebsd-src/pull/1427 Laptop and Desktop Working Group URL: https://wiki.freebsd.org/LaptopDesktopWorkingGroup Contact: Pierre Pronchery As part of 2024’s GSoC Project on the FreeBSD installer, I had the pleasure to mentor Chun Cheng Yeh (aka "Leaf") with his implementation of additional capabilities. The aim was to add support for repairing or updating an existing installation of FreeBSD, as well as allowing packages to be installed in the Live environment. This work has been consolidated into three distinct pull-requests, available on GitHub. While some aspects probably still require additional polishing before a possible merge, the possibility to significantly extend the installer images into a potentially life-saving tool is within reach. This is particularly relevant given the ongoing efforts to improve support for laptop and desktop use of FreeBSD. In this context, I am currently resuming work on the graphical version of the installer. The most immediate challenge includes shaping it suitably for integration into the next major release. Combining the two initiatives above should help FreeBSD close some gaps with its competition amongst other modern Operating Systems, for the enterprise as well as for laptop and desktop use. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Audio Stack Improvements Contact: Christos Margiolis The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement — from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs. This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature. Important work since last report: • sound(4) and driver bug fixes, including panics and races. Several cleanup and refactor patches. • Committed mididump(1). Ships with 14.2-RELEASE and 14-STABLE. • Implementing AFMT_FLOAT support. This fixes ports, such as emulators/wine, that require AFMT_FLOAT support from OSS. Related bug reports: PR 184380, PR 281390, PR 264973, PR 157050. Future work includes: • More bug fixes, optimizations and general improvements. • Implement a generic MIDI layer, similar to pcm/, and improve/modernize the MIDI codebase in general. • Implement a bluetooth device management utility. • virtual_oss patches and improvements. • Attempt to automate snd_hda(4) pin-patching. • Investigate SOF/DMIC support. You can also follow the development process in freebsd-multimedia@, where I post regular reports. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ mac_do(4), setcred(2), mdo(1) Contact: Olivier Certner Contact: Baptiste Daroussin This project aims at allowing controlled process credentials transitions without using setuid executables but instead leveraging our MAC framework. For an overall presentation, we refer the reader to the previous quarter’s report. As this is a progress report, we only recall the outline here. In a nutshell, this project comprises two components: • mac_do(4) is the kernel module that checks credentials transition requests and authorizes those that match rules configured by the administrator. • mdo(1) is the userland program playing the role of a mediator between processes wanting to launch other processes with changed credentials and mac_do(4), whose function is to authorize only specific such changes. setcred(2) is the new system call at the interface between them. It enables userland to request various credentials changes atomically, allowing mac_do (4) to base its decision on the transition between the initial and desired final credentials. Both prerequisite commits and changes in MAC/do proper have been reviewed and all commits have finally been pushed to FreeBSD’s main branch, including documentation in the form of a new manual page for setcred(2) and changes to the mac_do(4) one to match the new sysctl(8) knobs and rules syntax. Rules can now express finely which groups are allowed in the resulting credentials for a given UID or GID, notably making it possible to specify which target primary and supplementary groups the final credentials can, or must, or must not include. Please consult mac_do(4) for a description of the new syntax and examples. Future work, in no particular order and timeframe, may include: • For the mac_do(4) component: □ Currently, it can only grant credentials transitions for processes spawned from the /usr/bin/mdo executable. The possibility to tweak this path may be interesting for custom thin jail layouts. The ability to have several such paths is one of the missing pieces to be able to use mac_do(4) in conjunction with other credentials-granting programs such as sudo(1) and doas(1). □ mac_do(4) currently can only grant new credentials if they are requested via the new setcred(2), as it needs to see the current and desired final credentials to make a decision. However, each call to traditional and standard credentials-changing functions, such as setuid (2), seteuid(2), etc., can be considered as a (limited) full transition on its own, which mac_do(4) could decide upon. This functionality could allow to more finely control transitions to root and, combined with that of the previous point, to install and use credentials-granting programs without the "setuid" bit. However, the full power of this new mac_do(4) module version cannot be harnessed without modifying these programs to use setcred(2). • For the mdo(1) component: □ The credentials transitions that can be requested are fairly limited compared to what mac_do(4)'s rules can allow. It would be useful to make it possible to: ☆ Specify any list of target groups (primary or supplementary), possibly based on user names (with the implicit list coming from the contents of /etc/passwd and /etc/group) but allowing some tweaks (such as excluding a particular group in the final credentials). ☆ Allow changes of groups only. ☆ Request a password before calling setcred(2) in certain cases. This weakens the security paradigm of the mac_do(4)/mdo(1) combination, as it would now rely on userland for part of the gating process, but seems acceptable in many cases. ☆ Grow a mode producing the target part of rules corresponding to the contents of the password and group databases for some users. We welcome any feedback on this new version and the future-work list above. Sponsor: The FreeBSD Foundation Sponsor: Kumacom SARL ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Suspend/Resume Improvements Links: Blog URL: https://obiw.ac/s0ix/ Working Branch URL: https://github.com/obiwac/freebsd-s0ix Contact: obiwac Suspend-to-idle and support for S0ix sleep is in the process of being added to FreeBSD. This will allow modern Intel and AMD laptops (e.g. AMD and newer Intel Framework laptops), some of which do not support ACPI S3 sleep, to enter low power states to increase battery life. Ben Widawsky from Intel started working on this in 2018 but his work was never finished and is now outdated. His work has now been picked up and the first goal is to get suspend/resume working on the Framework 13 AMD Ryzen 7040 series by end of January. There are plans for presenting initial results at a talk at FOSDEM. Currently, all device power constraints on AMD can already be parsed to enter a system’s low power states. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ umb(4) driver for MBIM USB 4G/5G modems Links: UMB(4) - OpenBSD Device Drivers Manual URL: https://man.openbsd.org/umb UMB(4) - NetBSD Kernel Interfaces Manual URL: https://man.netbsd.org/umb.4 Bug 263783 - USB MBIM: Support for LTE/4G USB modems URL: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263783 Introduce the USB umb(4) network driver URL: https://reviews.freebsd.org/D48167 Contact: Pierre Pronchery The Mobile Broadband Interface Model (MBIM) is a protocol for communication with network USB devices, transmitting packet data over mobile broadband networks. Implementing this protocol adds support for a whole range of USB devices providing connectivity to mobile networks, such as 4G, 5G, and their subsequent technological evolutions. A first implementation for this protocol was performed for OpenBSD in 2016, under the name umb(4). I have ported it myself to NetBSD under the same name, back in 2019. I was then contracted to make it work with OPNSense, and authorized to publish it as Open Source in 2022. Unfortunately, by this time, some changes in FreeBSD effectively broke the driver, and it could not be merged until fixed. This quarter I have managed to offer an updated version and confirmed it working (thanks Mike and Zhenlei!). This version is now under review in Phabricator as D48167. The submission is still based on code from 2020, and behind progress made by OpenBSD since that time. As such, it is currently restricted to IPv4. However, I believe it makes sense to keep the review simple and focus on the design decisions and integration, before progressively importing the improvements made upstream since then in OpenBSD (notably IPv6 support). In its current form, the driver was modified from being out of tree and available as a plug-in for OPNSense, into a kernel module and its companion binary, umbconfig(8). This management binary effectively allows the umb(4) driver to be configured beyond the capabilities of ifconfig(8): the PIN or PUK code, APN, username/password, or roaming parameters can be setup, and the connectivity tracked as well (network provider, speed…​). Should you want to give it a spin yourself and get hardware supported by this driver, the single most important feature to look for is support for the MBIM specification. The manual page for OpenBSD provides a list of devices that should be compliant; note that some of them require preliminary configuration in order to effectively expose the MBIM interface. The exact procedure is vendor-specific, and can also depend on the model and current configuration of the device. You should refer to the documentation offered for your device for any steps necessary. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ LinuxKPI 802.11 Wireless Update Links: Categorised Wireless Problem Reports URL: https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0 Overview of drivers URL: https://people.freebsd.org/~bz/wireless/ Contact: Bjoern A. Zeeb Contact: The FreeBSD wireless mailing list With multiple wireless projects ongoing, this report focuses on the efforts using permissively licensed Linux wireless drivers mostly unmodified on FreeBSD. Drivers previously committed directly to FreeBSD src.git were retroactively imported in vendor branches and merged to main. This makes maintenance and identifying local changes a lot easier. The iwlwifi(4), rtw88(4), and rtw89(4) drivers got updated in main to match Linux 6.11. The rtw89(4) driver, which had been ported and in the tree for a while, got connected to the build. Thanks for that goes to the efforts of the community finding two bugs preventing it from working before. Wireless firmware in ports got updated and a release flavor was added. The release building framework got enhanced to install the firmware packages onto the release media. The installer grew support to run fwget(8) on the installed system to install the firmware. This all together ensures that (wireless) drivers with external firmware can be used from the installer and right away on the installed system without the need for alternate connectivity. With the framework in place for iwlwifi(4), rtw88(4), and rtw89(4) support for more drivers can easily be added in the future. These changes shipped the first time with 14.2-RELEASE. Having a lot of these requested necessities out of the way, time was spent on HT(802.11n) and VHT(802.11ac) improvements to the LinuxKPI framework synching between driver and net80211. Hardware crypto offload got sorted along with A-MPDU RX/BA offload right at the end of the year. Both were needed towards the goal to achieve higher throughput with iwlwifi(4). A half-year old bug, which stayed unnoticed preventing packets to be sent beyond scanning with rtw88(4) in main and stable/14, received a patch to fix the situation. Work for the first quarter of 2025 should include: • finishing basic HT and VHT support, and • looking at finishing the code for generic LinuxKPI 802.11 suspend/resume support Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Wireless Update Contact: Tom Jones Contact: The FreeBSD wireless mailing list With Support from the FreeBSD Foundation this quarter I started working on porting the iwx WiFi driver from OpenBSD (via Haiku). The iwx driver supports many of the chipsets supported by iwlwifi, but rather than make that driver more complex the OpenBSD developers decided to support these devices in a new driver. iwx on OpenBSD currently supports running as a station in 80211abgn and ac, it does not yet support ax rates. The goals of this project are to import a maintainable driver from OpenBSD and to gradually increase support until we have a native driver in FreeBSD with support for 80211ac (and potentially 80211ax). Currently the driver supports 80211a and 80211g and is able to saturate the practical limits of the rates these standards offers (roughly 28Mbit down and 25 Mbit up). The driver is under active development and moving quite quickly. The plan for the next quarter is to add support for high throughput rates, implement monitor mode and stabilise the driver for a public call for testing. Once the driver is stable enough a call for testing will be posted to the freebsd-current and freebsd-wireless mailing lists. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Syzkaller Improvement on FreeBSD Links: google/syzkaller URL: https://github.com/google/syzkaller Contact: Jian-Lin Li Contact: Li-Wen Hsu Syzkaller is an operating system kernel fuzzer that can look for vulnerabilities in the kernel. This project aims to improve the support of Syzkaller on FreeBSD. Based on the existing WiFi fuzzer designed for Linux, we drafted a WiFi fuzzer for FreeBSD. We planned to use wtap(4), a virtual wifi driver for testing, in order to support WiFi fuzzing. Some of the design details include: • Introduce a new netlink command to wtap in order to realize frame injection, which is essential for WiFi fuzzing. • Initialize wtap devices in Syzkaller before WiFi fuzzing. We are developing some prototypes and discussing the feasible design plan with some experts. There is not much progress yet. We hope to have more progress on this project in the next few months. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Architectures Updating platform-specific features and bringing in support for new hardware platforms. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Pinephone Pro Support Links: Repository on Codeberg URL: https://codeberg.org/Honeyguide/freebsd-pinephonepro Contact: Toby Kurien The project to port FreeBSD over to the Pinephone Pro is progressing. The aim of this project is to step by step support components of the Pinephone Pro in FreeBSD so that the device one day might be usable as a highly mobile FreeBSD device. In this quarter: • A driver for the RK818 power management IC was implemented, enabling the device regulators. • A driver for the real-time clock was also implemented, allowing the system to keep time between reboots. • A driver for the RK818 battery charger and battery monitor was written to allow the battery to be charged via USB, and to retrieve some battery information like voltage and charging status via sysctl. • The code repository has been updated with scripts and documentation on how to compile the custom kernel and device tree, and patch a FreeBSD 15-CURRENT image with them so that it boots on the Pinephone Pro. The next steps are to enable UEFI-based framebuffer support to enable output to the screen, and to enable USB on-the-go functionality, which might allow for plugging in a USB keyboard and/or Ethernet. Porting the Linux driver for WiFi will also be looked into. Any developers wanting to assist are encouraged to get in touch. Additional feedback and testers are welcome. Also see this thread on the FreeBSD Forum if you want to participate. Sponsor: Honeyguide Group ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cloud Updating cloud-specific features and bringing in support for new cloud platforms. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD on Microsoft HyperV and Azure Links: Microsoft Azure article on FreeBSD wiki URL: https://wiki.freebsd.org/MicrosoftAzure Microsoft HyperV article on FreeBSD wiki URL: https://wiki.freebsd.org/HyperV Contact: Microsoft FreeBSD Integration Services Team Contact: freebsd-cloud Mailing List Contact: The FreeBSD Azure Release Engineering Team Contact: Wei Hu , Contact: Souradeep Chakrabarti Contact: Colin Su Contact: Li-Wen Hsu In this quarter, we have published the 14.2-RELEASE on Azure Marketplace. Colin Su has presented at the FreeBSD 2024 Fall Summit about Azure DevOps Pipeline. Souradeep Chakrabarti from Microsoft has added a feature to use hypercalls for TLB shootdown on Hyper-V and Azure. Wei Hu root-caused an issue on missing CDROM device when booting FreeBSD on the latest Azure v6 VM SKU. V6 type only offers NVMe disks to guest OS. He also continues bug fixing for FreeBSD MANA NIC device. Work in progress tasks: • Automating the image publishing process and merging to src/release/. (Li-Wen Hsu) • Colin Su is testing adding FreeBSD support in Azure Pipelines □ https://github.com/microsoft/azure-pipelines-agent/pull/3266 □ Building and publishing snapshot builds to Azure community gallery. Open tasks: • Update FreeBSD-related doc at Microsoft Learn • Update sysutils/azure-agent to the latest version • Upstream local modifications of Azure agent • Port Linux Virtual Machine Extensions for Azure Sponsor: Microsoft for people in Microsoft, and for resources for the rest Sponsor: The FreeBSD Foundation for everything else ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OpenStack on FreeBSD Links: OpenStack URL: https://www.openstack.org/ OpenStack on FreeBSD URL: https://github.com/openstack-on-freebsd Contact: Chih-Hsin Chang Contact: Li-Wen Hsu The OpenStack on FreeBSD project aims to merge the capabilities of the OpenStack cloud infrastructure with the robust features of FreeBSD. Our objective is to harness FreeBSD’s unique features while ensuring compatibility with OpenStack’s operations. In the fourth quarter, our primary goal was to finalize the tasks promised under milestone 1 by establishing a new environment for a demonstrable Proof of Concept (POC) site. However, the simultaneous aim to set up another deployment based on FreeBSD Jail within the same environment led us to spend considerable time on network design and tuning. Fortunately, we successfully established external network connectivity for guest VMs by the end of this period. The remaining challenge now is to enable guest VMs to automatically acquire IP addresses through cloud-init. On another note, we attempted to obtain the domain XML of VMs from the Linux-based OpenStack to compare with the XML used for bhyve VMs. These domain XMLs are utilized by Libvirt, defining each virtual machine’s configuration and operational parameters. Comparing the differences between the two will aid in developing the "bhyve serial console over TCP" work. In the first quarter of the upcoming year, we will continue to conclude the tasks related to milestone 1 of our project. Additionally, we will persist in developing FreeBSD Ports for OpenStack components, further integrating and enhancing the system’s capabilities. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Containers and FreeBSD: Cloud Native Buildpacks Contact: Robert Gogolok Cloud Native Buildpacks (CNBs) transform application source code into container images. Those images can run on any cloud. With buildpacks, organizations can concentrate the knowledge of container build best practices within a specialized team, instead of having application developers across the organization individually maintain their own Dockerfiles. A few weeks ago, I’ve started to look into FreeBSD support for buildpacks. My goal is to have working versions of the tools lifecycle and pack in the next few months. There were previous attempts to bring support for FreeBSD to buildpacks, for example to lifecycle: • Add support for FreeBSD #1087 • Add FreeBSD Support #1271 After looking into those changes, I’ve decided to first introduce some general cleanup steps to keep the required changes for FreeBSD small. This resulted in the following changes that were successfully integrated: • Remove obsolete // +build lines #1431 • Use unix build constraint #1432 • Support FreeBSD build phase #1439 With these steps, it is now possible to compile lifecycle under FreeBSD. The next steps are: • Provide missing FreeBSD functionality to lifecycle. • Further investigate FreeBSD as a build target in lifecycle. • Investigate and get the tool pack to compile and run under FreeBSD. • Provide lifecycle and/or pack via FreeBSD ports. • Investigate the idea of FreeBSD buildpacks for some popular languages, similar to paketo buildpacks. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD on EC2 Links: EC2 Boot performance over time URL: https://www.daemonology.net/freebsd-ec2-boot-performance/ Contact: Colin Percival FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances. In the past quarter, first boot performance of ZFS AMIs has been significantly improved, e.g. from about 22 seconds to about 11 seconds for 15.0 "base" AMIs on amd64. Graphs of boot performance over time are now being generated and published automatically; typical times are around 9-12 seconds for "base" and "small" AMIs and 14-18 seconds for "cloud-init" AMIs. On Graviton systems, the EC2 "shutdown" and "reboot" operations now work as intended (starting with FreeBSD 14.2). On Graviton systems, adding new devices (e.g. EBS volumes) while the system is running now works in HEAD and support is expected to be merged in time for FreeBSD 14.3. Sponsor: Amazon Sponsor: https://www.patreon.com/cperciva ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Documentation Noteworthy changes in the documentation tree, manual pages, or new external books/documents. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Documentation Engineering Team Link: FreeBSD Documentation Project URL: https://www.freebsd.org/docproj/ Link: FreeBSD Documentation Project Primer for New Contributors URL: https://docs.freebsd.org/en/books/fdp-primer/ Link: Documentation Engineering Team URL: https://www.freebsd.org/administration/#t-doceng Contact: FreeBSD Doceng Team The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see FreeBSD Doceng Team Charter. Document changes • Handbook: □ Add warning about custom kernel configurations. □ Mention Rocky Linux 9 userland. □ Add notes to VMWare related setup guide. • Committer’s guide: Document "Discussed with" Improve "Fixes:" metadata. • Porter’s Handbook: Document new TCL_ variables. • Website: Remove Turkish links. • Documentation repository: □ Added OpenBSD 7.6 manual pages. □ Updated Debian 11/12 manpages. FreeBSD Translations on Weblate Link: Translate FreeBSD on Weblate URL: https://wiki.freebsd.org/Doc/Translation/Weblateurl Link: FreeBSD Weblate Instance URL: https://translate-dev.freebsd.org/url Q3 2024 Status • 18 team languages • 215 registered users 1 new translator joined Weblate: • Sean Markham (ES) Languages • Chinese (Simplified) (zh-cn) (progress: 14%) • Chinese (Traditional) (zh-tw) (progress: 11%) • Dutch (nl) (progress: 1%) • French (fr) (progress: 1%) • German (de) (progress: 1%) • Greek (el) (progress: 1%) • Indonesian (id) (progress: 1%) • Italian (it) (progress: 11%) • Korean (ko) (progress: 30%) • Norwegian (nb-no) (progress: 1%) • Persian (fa-ir) (progress: 6%) • Polish (progress: 2%) • Portuguese (progress: 0%) • Portuguese (pt-br) (progress: 31%) • Sinhala (progress: 1%) • Spanish (es) (progress: 39%) • Spanish (Chile) (progress: 0%) • Turkish (tr) (progress: 5%) We want to thank everyone who contributed, translating, or reviewing documents. And please, help promote this effort on your local user group; we always need more volunteers. Packages maintained by DocEng During this quarter the following work was done in packages maintained by doceng@: • www/gohugo: update to 0.140.2 • misc/freebsd-doc-ja: fix build Open issues There is 1 open PR in Bugzilla assigned to doceng@: • 276923 www/gohugo link error under poudriere ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Collection Accessibility - Colors Low Vision Link: Project wiki page URL: https://wiki.freebsd.org/portconfig Contact: FreeBSD Accessibility mailing list Contact: Alfonso Sabato Siciliano FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications. The collection provides tens of thousands of ports; port configuration is a key feature. It is possible to configure a port before the building and installation. The command "make config" uses a text user interface (TUI) to set up port options interactively. Recently low vision users (mainly with cataracts) have requested new features to easily change the colors of the TUI. Several features have been implemented to allow changing colors, for example: a new environment variable to set the UI to black and white, or the ability to set colors by reading a configuration file at runtime. All features have been described in portconfig(1) since version 0.6.2. To note, blind users can refer to PortOptsCLI - Ports Collection Accessibility, Status Report Third Quarter 2023 to use the Ports Collection. Tips and new ideas are welcome. If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Containers and FreeBSD: AppJail, Director, OCI and more Links: AppJail on GitHub URL: https://github.com/DtxdF/AppJail Director on GitHub URL: https://github.com/DtxdF/Director LittleJet on GitHub URL: https://github.com/DtxdF/LittleJet Reproduce on GitHub URL: https://github.com/DtxdF/reproduce Contact: Jesús Daniel Colmenares Oviedo AppJail is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. Director is a tool for running multi-jail environments on AppJail using a simple YAML specification. A Director file is used to define how one or more jails that make up your application are configured. Once you have a Director file, you can create and start your application with a single command: appjail-director up. LittleJet is an open source, easy-to-use orchestrator for managing, deploying, scaling and interconnecting FreeBSD jails anywhere in the world. Their goals are to simplify life for sysadmins and developers by providing a unified interface that automates the jail workflow by combining the base FreeBSD tools. AppJail and all its meta-projects extensively follow The Ephemeral Concept which helps update/upgrade jails more easily as they become disposable. I have used this extensively to deploy my jails with services since this concept was implemented in AppJail. Although there have been great people working on OCI for a long time, this month the featured topic is OCI, and the advances related to this technology in FreeBSD make it possible to implement it in AppJail. The latest release adds more useful features, improves on existing things and implements OCI. I’m continually adding more Makejails, a simple text file that automates the deployment of services in jails. There is an organization on GitHub that I call The Centralized Repository if you want to make a contribution. The last improvement was to implement BuildBot as the CI/CD of AppJail images, so any change made to a repository that is tracked by BuildBot will generate a new task to build and deploy an image to the mirrors. And if mirrors are not an option, appjail-reproduce can be used to build images using your own resources. Sponsor: https://www.patreon.com/appjail ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Improving Common Lisp Infrastructure in FreeBSD Ports Contact: Joe Mingrone Common Lisp (CL) is a general-purpose, multi-paradigm programming language first conceived in the early 1980s. Although it predates many modern programming languages, it remains a viable option for many different projects. One contemporary example is Grammarly, a widely used grammar engine reportedly implemented in CL and capable of processing over a thousand sentences per second. The FreeBSD ports tree has provided CL support for many years. The initial work was contributed by Henrik Motakef in 2003, and then enhanced and maintained by Jimmy Olgeni. The infrastructure facilitated building and installing CL libraries using ASDF so that multiple CL implementations could load compiled object code files (fasl) at run-time without conflicts. However, many issues crept in over the years. Support dwindled to only one CL implementation, SBCL, and users encountered longstanding bugs such as conflicting ASDF versions and write errors when loading libraries outside the ports tree. Also, managing dependencies was cumbersome because most infrastructure code was included as part of the devel/cl-asdf port. A long overdue update of the FreeBSD CL infrastructure was completed this quarter. The primary outcome is that users can, once again, easily and reliably work with CL on FreeBSD. For example, installing and loading the popular Alexandria library under SBCL requires only a few simple steps. % pkg install cl-alexandria-sbcl % sbcl * (asdf:load-system :alexandria) Similar steps can be used to load libraries for the other two newly supported implementations: CCL, and CLISP. Most users will likely prefer to work with the fasl ports, although there is no obligation to do so. Because ASDF is now configured to fall back to its default caching mechanism of writing fasl to a cache under ${HOME}, users can also install CL source ports without the associated fasl port or load CL sources from outside of the ports tree. Other highlights of the update include: • decoupling ASDF initialization from devel/cl-asdf by creating a dedicated port: devel/freebsd-cl-asdf-init • creating USES=cl • adding and updating various CL library ports for the three supported implementations • updating and modernizing lang/ccl and lang/clisp For details, refer to these commit logs: • 4c954c1522cbf4d05013caaf40c36458d82f1480 • f6a75a8f9bf20dbf1e9a4d5bc171d58f595c1ec1 • 1d7c75a5cde6792b3872340edeaf8f278add291a • 148251b431b8d972623bb3adaa5a71355f47ac26 • 7f68336ed19be61027dfb7b461aacd056733eba4 The tentative plan is to add support for ECL after an ASDF output translation issue is solved and to create ports for other CL libraries. Feedback, testing, and contributions are welcome. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Erlang Ecosystem Ports update Links: FreeBSD Erlang wiki URL: https://wiki.freebsd.org/Erlang Erlang/OTP language URL: https://erlang.org/ Elixir language URL: https://elixir-lang.org/ Gleam language URL: https://gleam.run/ Contact: FreeBSD Erlang mailing list The Erlang runtime system, commonly known as the BEAM, provides a runtime that is used by a number of programming languages and applications in the FreeBSD ports collection. In the final update for 2024, the Erlang ecosystem team has been busy: • Regular updates to all Erlang/OTP releases, to stay current • Elixir 1.18.1, Gleam 1.6.3, and RabbitMQ updates Users of RabbitMQ need to update each quarter to avoid being stuck on an unsupported release of Erlang/OTP + RabbitMQ, without a supported migration path. Note that as the upstream Erlang OTP team only commit to supporting the two latest major releases, more and more point updates are arriving for OTP26-27, but not for the older Erlang runtime releases, which are now unlikely to get security and bug fixes. The Erlang team will be updating the default Erlang runtime to OTP26, to lang/ erlang, along with the usual dependencies and tooling. Additional testing and community contributions are welcome; please reach out on the mailing list, especially if you are able to help testing of specific port updates. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Improve OpenJDK on FreeBSD Links: Project description URL: https://freebsdfoundation.org/project/ improving-openjdk-on-freebsd/ Contact: Harald Eilertsen The aim of this project is to improve support for Java in FreeBSD, by working with the upstream OpenJDK community, as well as the FreeBSD community in getting the changes and additions needed for fully supporting FreeBSD accepted upstream. As this is a new project, there is not much to report yet, but here’s what has been achieved so far: • The Java Test Regression harness (jtreg) now builds and runs on FreeBSD, and the process of upstreaming the changes has started. • OpenJDK 23 builds and runs on FreeBSD, and work on adding it to the ports collection has started; this is still considered experimental. https://reviews.freebsd.org/D48194 • Work on porting the next OpenJDK (version 24) has started. https://github.com/snake66/jdk/tree/jdk24-freebsd Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Xfce on FreeBSD Links: Xfce 4.20 Upstream Release Announcement URL: https://xfce.org/about/news/?post=1734220800 Xfce meta-port on FreshPorts URL: https://www.freshports.org/x11-wm/xfce4 Contact: Xfce team Contact: Guido Falsi The FreeBSD Xfce team (xfce@) works to ensure the Xfce desktop environment is maintained and fully functional on FreeBSD. This quarter the Xfce team members are pleased to welcome Xfce 4.20 to the FreeBSD ports tree! This new release adds many stability improvements and some new functionality. Upstream work for this release was focused on getting the code base ready for Wayland support. This release brings experimental Wayland support, although not all components have been migrated, so it may not work for you. For further details, refer to the Xfce 4.20 Upstream Release Announcement. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ LXQt on FreeBSD Links: LXQt Project URL: https://lxqt-project.org/ LXQt Project GitHub URL: https://github.com/lxqt Contact: LXQt Team LXQt is an advanced, easy-to-use, and fast desktop environment based on Qt technologies. It has been tailored for users who value simplicity, speed, and an intuitive interface. Unlike most desktop environments, LXQt also works fine with less powerful machines. During this quarter, the x11-wm/lxqt metaport was updated to 2.1.0. This update adds initial Wayland support to the LXQt desktop. You can read some release highlights here. Anyone interested in helping with the project is welcome. Current version: 2.1.0 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ GCC on FreeBSD Links: GCC Project URL: https://gcc.gnu.org/ GCC 11 release series URL: https://gcc.gnu.org/gcc-11/ GCC 12 release series URL: https://gcc.gnu.org/gcc-12/ GCC 13 release series URL: https://gcc.gnu.org/gcc-13/ GCC 14 release series URL: https://gcc.gnu.org/gcc-14/ Contact: Lorenzo Salvadore The exp-run to update GCC default version from 13 to 14 is getting forward. As usual, thanks to everyone involved. If you maintain any of the affected ports or want to give a hand preparing and testing some patches, you can consider trying adding -fpermissive to CFLAGS in affected ports as a temporary solution: GCC 14 has transformed some warnings into errors, which is the cause of many of the failed builds. The -fpermissive flag switches those errors back to warnings. However, it is preferable that upstream updates its code to remove those warnings completely so that -fpermissive is not necessary, possibly with FreeBSD ports maintainers support. If the code is not maintained upstream anymore, the time might have come to deprecate the port. Work has been done on some bugs too, mainly upstream: • https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210 has been fixed: a recent change in the FreeBSD headers caused a regression in the GCC 15 development version; • https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115008 has been fixed: this was an issue with posix_fallocate failing on FreeBSD on a ZFS filesystem; • an attempt to fix bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282797 specific to aarch64 for -devel ports has failed. If you are able to give a hand on this, it would be very much appreciated. Thanks to everyone who has helped with these issues. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Tor-Browser Links: Tor Project Homepage URL: https://www.torproject.org/ GitLab Repository URL: https://gitlab.torproject.org/tpo/applications/ tor-browser Contact: Martin Filla Since the last report, significant progress has been made in building and packaging Tor Browser for FreeBSD. Additionally, the Tor Browser version has been updated to 14.0.3, which is now available from the Tor Browser download page and also from our distribution directory. This update includes important security updates to Firefox, ensuring that users benefit from enhanced security and privacy features. Expanding FreeBSD compatibility remains a priority to provide seamless and native privacy solutions for the platform. What is new: Tor Browser version 14.0.3 includes: • Rebase to Firefox 128.5.0esr. • Backporting of security fixes from Firefox 133. • Platform-specific updates such as disabling Microsoft SSO on macOS and updating GeckoView for Android. • Updated Go to version 1.22.9 in the build system. Help Needed: To move forward, assistance is required in the following areas: Code Review: Ensure patches meet the required coding and security standards. Testing: Volunteers are needed to test Tor Browser 14.0.3 on FreeBSD to identify edge cases. Bug Fixing: Developers familiar with FreeBSD and Firefox’s codebase are encouraged to resolve known issues. Feedback: If you find a bug or have suggestions for improving this release, please let us know through the GitLab Repository or the provided contact email. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Greenbone Vulnerability Management Community Edition Links: Greenbone URL: https://www.greenbone.net/en/ Greenbone GitHub URL: https://github.com/greenbone/ Contact: José Alonso Cárdenas Márquez The Greenbone Community Edition (GVM) covers the actual source code of the Greenbone Vulnerability Management software stack, which is also known as OpenVAS scanner, a security feed with more than 160.000 vulnerability tests, a vulnerability management application, and much more. During this quarter, security/gvm metaport was updated to 24.1.2. This update includes the following: • databases/pg-gvm: Updated to 22.6.6 • security/gsa: Updated to 24.1.0 (Only amd64 and aarch64) • security/gsad: Updated to 24.1.0 • security/openvas: Updated to 23.14.0 • security/gvmd: Updated to 24.1.2 • security/gvm-libs: Updated to 22.15.0 • security/py-notus-scanner: Updated to 22.6.5 • security/py-greenbone-feed-sync: Updated to 24.9.0 • security/py-ospd-openvas: Bump PORTREVISION • security/py-gvm-tools: Updated to 24.12.1 • security/py-python-gvm: Updated to 24.12.0 A quick GVM jail installation to test it can be done using AppJail, makejail, or https://github.com/AppJail-makejails/greenbone-openvas. Anyone interested in helping with the project or interested in aarch64 device donation for testing is welcome. Current version: 24.1.2 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Wazuh on FreeBSD Links: Wazuh URL: https://www.wazuh.com/ Contact: José Alonso Cárdenas Márquez Wazuh is a free and open source platform used for threat prevention, detection, and response. It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments. Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data gathered by the agents. Besides, Wazuh has been fully integrated with the Elastic Stack or OpenSearch Stack, providing a search engine and data visualization tool that allows users to navigate through their security alerts. After a long break, ports has been updated to include Wazuh version 4.9.2. This version of Wazuh uses Python 3.11 instead of 3.10, and it includes some new features: • support to get ports info, • support to get processes info, • improved memory info, • FreeBSD decoder and rule files, and • FreeBSD Security Configuration Assessment files for 13.x, 14.x and 15-CURRENT. Also, FreeBSD ports include a custom version of wazuh-dashboard-plugins for a better integration with FreeBSD. Wazuh can easily be installed in a jail by following the Wazuh AppJail-Makejails tutorial. Anyone interested in helping with the project or interested in aarch64 device donation for testing/packaging is welcome. Current version: 4.9.2 TODO • Add Wazuh cluster-mode infrastructure AppJail makejails • Add vulnerability detection support to FreeBSD Wazuh agent • Add FreeBSD as officially supported platform by Wazuh Inc • Update FreeBSD SCA Policies to new FreeBSD CIS Benchmark ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A bhyve management GUI written in Freepascal/Lazarus Links: Bhyvemgr URL: https://github.com/alonsobsd/bhyvemgr/ Contact: José Alonso Cárdenas Márquez Bhyvemgr is a bhyve management GUI written in Freepascal/Lazarus on FreeBSD. It needs a bunch of tools mostly installed on base system and some installed from ports/packages. The application is being developed for desktop users to easily and quickly setup and run virtual machines on FreeBSD hosts. During this quarter, there were many bugfixes and improvements to Bhyvemgr. These are some new features that were added: • Support for Trusted Platform Module (TPM through software via swtpm) on CURRENT • Bootvars support • Bios, system, board and chassis information can be modified • Systray icon support on almost all desktop environment (tested on Plasma, Gnome, Xfce, LXQt and IceWM) Bhyvemgr supports aarch64 only on 15-CURRENT and amd64 from FreeBSD 13.x to 15-CURRENT. Also bhyvemgr can be • compiled and installed from ports, • installed as binaries through pkg with gtk2, qt5 or qt6 interface support. Anyone interested in helping or supporting the project are welcome. Current version: 1.3.1 TODO • Testing on real aarch64 hardware (aarch64 device donation for testing is welcome) • Add uart device support ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BSD-USER 4 LINUX Contact: Maksym Sobolyev Links: Project Page URL: https://github.com/sobomax/qemu-bsd-user-l4b Tooling URL: https://github.com/sobomax/qemu_l4b The bsd-user-4-linux project ports BSD user-mode emulation for QEMU to Linux. The primary goal is to enable unmodified FreeBSD binaries to run on modern Linux systems. Additionally, the project aims to provide multi-platform container images with a functional FreeBSD environment and ready-to-use GitHub Actions templates. Current Status: • The initial port successfully runs make -jN buildworld. • Most command-line tools are working as expected (sh, bash, find, grep, git, clang, etc). • A GitHub Actions pipeline builds x86_64 emulation images for: □ linux/386 □ linux/amd64 □ linux/arm/v5 □ linux/arm64/v8 Next Steps: * Implement container integration. How You Can Help: • Test with your preferred toolchain, report issues, or contribute fixes. • Build and test non-x86_64 emulation images (e.g., FreeBSD/arm64 on Linux/ x86_64). The code works on BSD but needs testing on Linux. • Support us on Patreon. Sponsor: Sippy Software, Inc. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Third Party Projects Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Laptop and Desktop Work Group (LDWG) Links: Desktop mailing list URL: https://lists.freebsd.org/archives/freebsd-desktop/ Wiki Page URL: https://wiki.freebsd.org/LaptopDesktopWorkingGroup Contact: Chris Moerz October 2024 marked the inception of the Laptop and Desktop Work Group (LDWG), affectionately known as "Ludwig". This initiative provides a collaborative platform for the community to engage in development, testing, knowledge exchange, and advocacy for FreeBSD on laptops and desktops. Everyone is welcome to join, if interested. Scope of Work: • Content Creation: Develop recordings, articles, tutorials, documentation, and system configurations for stakeholders interested in FreeBSD on laptops and desktops. • Encouraging Contributions: Invite developers, testers, and industry experts to enhance the usability of FreeBSD on laptops and desktops. • Facilitating Collaboration: Promote code contributions, testing initiatives, operational support, and hardware insights. • Supporting User Stories and Ongoing Projects: Assist in the creation, validation, prioritization, and delivery of user stories identified in the FreeBSD Foundation’s “Laptop” investment work package. On November 16, 2024, the LDWG held its inaugural virtual meeting. The strong interest in FreeBSD for laptops and desktops was evident from the diverse group of participants, including developers, contributors, Discord community moderators, users, and FreeBSD Foundation members. Meeting slides, minutes, and recordings are available on the Group’s wiki page. During the meeting, the group identified prioritized gaps and potential improvements in the following areas: • Console • Desktop Environment • Documentation • Hardware □ Graphics □ Wireless (WiFi and Bluetooth) □ USB/Thunderbolt • Installer • Performance • Software and Port Availability All activities are documented on the Group’s worksheet. The Group encourages anyone interested in contributing to add their name. If there is any planned or ongoing work, please include it in the worksheet. Alice Sowerby provided an update on the The Foundation’s Laptop project, highlighting the need for volunteers to support testing efforts. The Group is running an online survey to gather input from non-participants. The survey will remain open until the next call in January, where results will be presented and discussed. Hope to see you there! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Containers and FreeBSD: Pot, Potluck and Potman Links: Pot organization on GitHub URL: https://github.com/bsdpot Contact: Luca Pizzamiglio (Pot) Contact: Bretton Vine (Potluck) Contact: Michael Gmelin (Potman) Pot is a jail management tool that also supports orchestration through Nomad. Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad. During this quarter, there was no new Pot release. The tool is stable and used in production for quite some time already. Potluck got a new Netbox image. Additionally, various images have received improvements and bug fixes, e.g. improving their syslog-ng integration. Last not least, all images have been rebuilt several times: for FreeBSD 14.1, to include security fixes, then again for 14.2 and also for the new quarterly packages. As always, feedback and patches are welcome. Sponsors: Nikulipe UAB, Honeyguide Group From nobody Sat Mar 1 07:36:59 2025 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z4cNF1H0Lz5nwMb for ; Sat, 01 Mar 2025 07:37:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z4cND73mxz474p for ; Sat, 01 Mar 2025 07:37:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740814621; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PpnDbJ+tHMrVLoLaJPO2x+Sd0saIh5PwDF/BH/SxYGk=; b=Y/uoPki/w08N4WyTFJK7HABhhvGfNJjsuO6tX4YRoub44IexJrrHfigMLUnnC3WE6KUVbV PcuMWj9c/OoYLMxjn/jAUb1vALRG1QVE3bjr5t8RQ1/IP1EaLY73oUybAMnxvaySARjJd8 MsDq6Sk6ODmbq6nWCtl/1znihR9Q1K/8LvMadZsog6LQfJISH4jSW0qR8iAmkYnuPNZmch p/I1fFKbLjaC+CZdNSGqWlDVDbWfLKUMLovUt21mX2jsd+4QPT56pb4seLKilC2dtbJ491 mCqzRrw6QW0d5i0Z7UzU/VBSBlOksS/WAfr9ADB2qOAaZkK54F7QppRRQOcGWg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740814621; a=rsa-sha256; cv=none; b=Z9Ba//ZYDIKj3TWIJWyKEeQHp5wCwmMjBqJXkTWddrHlbTZZiGPaPCv80PHsXuuKYhfdyk R5MAHkm5wYVKFMu9r+qq9rBp0rU2ymmxacfKz06pEv6iuYXWLx/G4p7K7lc2aEtIzU1w0x MsdwGPpRh6/wt2zsDbcWpabfFSgFMXs+kPWjH2xVSyXVUAoR0HIlwOUdGGsJpaQP8RojJG be6iFpSih7fcTgyS2Q9kp4fCYz29C6VvknpUDx3dlC1DW6SIu3MzWATynEbNuGZNfsPYW2 Qmc4LiDjSOJzS2EJywAyczvgBmYlSlP8op9mudAqVOa7yN/sZgxEXaoLvJAF0A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740814621; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PpnDbJ+tHMrVLoLaJPO2x+Sd0saIh5PwDF/BH/SxYGk=; b=BHy/fQeIk/GEPsZa08tXTWjrmVa2sRIW/Zruxi3vaTuHwzvbfH7toIpSoV/ap2V3/XYSy9 IW6BOExyW+f2o6KkSUJTlTMb3DZwhB6A5oPMSQ2mqcGGXU4ooHy14VSRmvxAV1yEZFDxyq tMxQhoASs/coir/0ym48Junq1wIY3iwtfX5BdivI8LQhDBRJX6D+Kw0Dan3LGap3Rx1F0t +8Jzh6IfyL3lMtWIZno2pRUeDpLFHwFLfOUi6YRkHdI9boAqBG1oMbvOMWG+/gFhWCQIHh DCSV/gNKqWVQKb9LO4/xSYAn0nlUCefUgVvy6jShmzLjgKQ9d+snvt0VpJa43w== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z4cND6fzVz1574 for ; Sat, 01 Mar 2025 07:37:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 5217b0il070753 for ; Sat, 1 Mar 2025 07:37:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 5217b0oW070752 for stable@FreeBSD.org; Sat, 1 Mar 2025 07:37:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 278099] outdated version of zstd(1) is kept in the base Date: Sat, 01 Mar 2025 07:36:59 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: needs-patch, performance, regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: zarychtam@plan-b.pwste.edu.pl X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278099 --- Comment #9 from Marek Zarychta --- Zstandard (zstd) version 1.5.7 was released last week, introducing signific= ant performance enhancements and bug fixes[1] We have zstd 1.5.2 in the base system. It was released 3+ years ago and the= re are 1772 commits to dev since this release. 1.https://github.com/facebook/zstd/releases/tag/v1.5.7 --=20 You are receiving this mail because: You are on the CC list for the bug.= From nobody Sun Mar 2 02:01:32 2025 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z54tl4xpWz5VfKZ; Sun, 02 Mar 2025 02:01:35 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z54tl4gTsz4QhY; Sun, 02 Mar 2025 02:01:35 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740880895; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc; bh=Qu/m4Mybr82oyCoxhz4xETjodx/Eyg5n+5JK/qiA/uA=; b=ROPBkTIiqinyQOcD0XhUqLXS5Pa4kVqptrLlbP1Y3BiVt8p5Polzh+R4uSlsYAEIoU+w4G u8fBMwCQuzGCVR6fczsoFy6aTiymf/VSxDNiAE38Va7VNXchF/kg4ghiR6qLGaVGp5UzEt bHTFZyNvr4R1jW5OkQbXmXB6mtKzaNjjSN6do7CzKuHCIHKp4zBoqyr2/kGqwJ4HDyKwQm +/MO6BgAi0Wvj+CnS7aoBM1Prs0SOkBDB9AMaBFOUFyxokPTnyQ9Wkiu7CzqAXFZC7iAi9 LBjl5ws4iyoAxkmThzm+EoUPNFOAxfvJT3oTuDjuCpeMJWuzioDSv8PsblBhVg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740880895; a=rsa-sha256; cv=none; b=VgV8HpSf933KX/4CyAci5Qf9oVNtiqZckR3W8yqK/OzO1CuiUEOuESZaov1StuODdjPpQz 2/3eBNuwQCrbySTn20M0YnRQ/LLTbgphGEIAtcKNebP+KdWLQEooo2mORtBy7EQFy32DMl UVVubAzlUnWVIlhSFp9/MoZpVZ2Dt5Weygmvx/iVK9IAq6dm3BmHYhr2xJHJpIWXD/Kl1U 3ukpgXSdMvyEWS6TR1TpvEJNeGwyMnAz1HJoV9mBnC+NDy3hloEPGnHUeWCZ1jf/8JD1gG HInK3bvRgy7BTV5FPBj7HdAbq/mRYym3XeN98Mzb6UX8fskf/utl6AlQMaW/yA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740880895; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc; bh=Qu/m4Mybr82oyCoxhz4xETjodx/Eyg5n+5JK/qiA/uA=; b=GEA/GZZaPMnD7AVvQoccyLnPweOI/FuY9T+2GJ5MdqrQzm/mzqEEOXvR364TcCpcpgHTHW y/9qA1bTCLbrCA3HsIaR0JBjTuLpmnYcTm+A6YDO77C/3XT0dAoKRGc7zwpkjAV4Kq4yjM 005EdFAYCUkzB4Ya6IRnKmw/9kR4Sxi9ym5izficV/V9G84tnv+X+egoEQ7g/P1WcopryC S19ioxEumL+xH8j2wlh91+C64yZyLnEqvZj0r7wkPN7dhE2WEHvcra2PEu0+QEE4qUP2H8 ztfO/6n2KdGFXI+GeuEMqsN9v+NPPM6Kn/4j9gZ+vz/rmytIb0+KTFnPnCxLGg== Received: by freefall.freebsd.org (Postfix, from userid 1002) id 85383E446; Sun, 02 Mar 2025 02:01:32 +0000 (UTC) To: freebsd-snapshots@FreeBSD.org, freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Reply-To: FreeBSD Release Engineering Team Subject: FreeBSD 13.5-RC1 Now Available Message-Id: <20250302020135.85383E446@freefall.freebsd.org> Date: Sun, 02 Mar 2025 02:01:32 +0000 (UTC) From: Colin Percival List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 The first Release Candidate build of the 13.5-RELEASE release cycle is now available. Installation images are available for: o 13.5-RC1 amd64 GENERIC o 13.5-RC1 i386 GENERIC o 13.5-RC1 powerpc GENERIC o 13.5-RC1 powerpc64 GENERIC64 o 13.5-RC1 powerpc64le GENERIC64LE o 13.5-RC1 powerpcspe MPC85XXSPE o 13.5-RC1 armv6 RPI-B o 13.5-RC1 armv7 GENERICSD o 13.5-RC1 aarch64 GENERIC o 13.5-RC1 aarch64 RPI o 13.5-RC1 aarch64 PINE64 o 13.5-RC1 aarch64 PINE64-LTS o 13.5-RC1 aarch64 PINEBOOK o 13.5-RC1 aarch64 ROCK64 o 13.5-RC1 aarch64 ROCKPRO64 o 13.5-RC1 riscv64 GENERIC o 13.5-RC1 riscv64 GENERICSD Note regarding arm SD card images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: https://download.freebsd.org/releases/ISO-IMAGES/13.5/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use Git to do a source based update of an existing system, use the "releng/13.5" branch. A summary of changes since BETA3 includes: o Fix to blacklistd integration with sshd o Fix to (unused in FreeBSD base system) STAILQ_ASSERT_EMPTY macro A list of changes since 13.4 is available in the releng/13.5 release notes: https://www.freebsd.org/releases/13.5R/relnotes/ Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 13.5-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64, i386, aarch64, and riscv64 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD download mirrors): https://download.freebsd.org/releases/VM-IMAGES/13.5-RC1/ BASIC-CI images can be found at: https://download.freebsd.org/releases/CI-IMAGES/13.5-RC1/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 135 MB and 165 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI loader file is needed for qemu-system-aarch64 to be able to boot the virtual machine images. See this page for more information: https://wiki.freebsd.org/arm64/QEMU To boot the VM image, run: % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt \ -bios QEMU_EFI.fd -serial telnet::4444,server -nographic \ -drive if=none,file=VMDISK,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -device virtio-net-device,netdev=net0 \ -netdev user,id=net0 Be sure to replace "VMDISK" with the path to the virtual machine image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMI IDs can be retrieved from the Systems Manager Parameter Store via the AWS CLI using the command % aws --region $REGION ssm get-parameter --name $KEY where $REGION is the desired region and $KEY is one of the following keys: /aws/service/freebsd/amd64/base/ufs/13.5/RC1 FreeBSD/aarch64 EC2 AMI IDs can be retrieved using the keys /aws/service/freebsd/arm64/base/ufs/13.5/RC1 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-13.5-RC1 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64, i386, and aarch64 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade by first installing any updates for the currently running release: # freebsd-update fetch # freebsd-update install and then downloading the new release: # freebsd-update upgrade -r 13.5-RC1 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 12.x. Alternatively, the user can install misc/compat12x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 13.5-RC1 amd64 GENERIC: SHA512 (FreeBSD-13.5-RC1-amd64-bootonly.iso) = e43cb34093b61c596006ec217c11b75194f633dfef9630cdec198687930870450dffffbd2e0183c50aa62ac7d60cf947c1ace364b4173c1bc3a134cc2abc9332 SHA512 (FreeBSD-13.5-RC1-amd64-bootonly.iso.xz) = 597d1a8430d697baa61f6cf8a0f1a7affaf756cdeaa49d01b4e00c5b577df4b7396b5ef3ceb242868487f32955560ebceb88eaac76b2f511190c545a5246d17f SHA512 (FreeBSD-13.5-RC1-amd64-disc1.iso) = 4b2b2543d8099b66fe1b62e40dceaa1eedb87d19800701daaba2680fba3f4807d2c216ed837a780e6d11bd550c5554c5056da002e9b5488a323c61707dd340a1 SHA512 (FreeBSD-13.5-RC1-amd64-disc1.iso.xz) = fc68632e8700e5b5a07e4ab830651bf225066f1d9cb978ef524979bbd030936eea69868bcd4d0a3ffa4829c94cea789fecb1923067983fbc79a4ffd0a84927ea SHA512 (FreeBSD-13.5-RC1-amd64-dvd1.iso) = c9aed488d5462cc94ee77d2ff63daab81b85fa7b3b66062c0ccb9e972825bffe29201e39e87597df542b93b8cea811485ba16f8dd1e9ca83e748e43906610299 SHA512 (FreeBSD-13.5-RC1-amd64-dvd1.iso.xz) = 56ae57278d6d3701a3e21f159987a0823974eceda4ad34f2309f872adcf44b4ae9f271c1d8e0696341f43450bd6abb8f429147f6b2bca1f6e1b807d1eff49a89 SHA512 (FreeBSD-13.5-RC1-amd64-memstick.img) = 0c04cdadea99777fd498d5217eb71cf9c434604056e14ae3acde6e570bfc90d216b2e390c52e43c3ead94a7820e133da3d1ce155d8fb095d3f7a5b6460adb14e SHA512 (FreeBSD-13.5-RC1-amd64-memstick.img.xz) = 7f442dc6635f73d8c5ad167d34d82bf95172ec66a54dc62945173c24eb28f7632a20eb88688194822a03da7acefb200afc75086b0bc934c813cca13c716dcdd6 SHA512 (FreeBSD-13.5-RC1-amd64-mini-memstick.img) = b7465d78f591c1c8fa45e40a1b22c14ca25fd7b29ea29d316969c9518b74e86073f7764cbda98b57f7c1862e4196fc52821352bfcf9a56ad2f3243fdbc99877b SHA512 (FreeBSD-13.5-RC1-amd64-mini-memstick.img.xz) = 7c2dad8bef2756764b5518083bfb5478117f689a3058668f226a42e11dd6b949f3b28790d4830cf76da4316bba06022a4b8be3dbc066ff8df49f1f23809959d3 SHA256 (FreeBSD-13.5-RC1-amd64-bootonly.iso) = 67875856ae2587604e5452785e1d6d8867577661e69ae157d7fbc335cc848dfb SHA256 (FreeBSD-13.5-RC1-amd64-bootonly.iso.xz) = 29e74cdc2d120616c2ff65fce91820f9f698fb8d7f35c709705f7ef09f319f42 SHA256 (FreeBSD-13.5-RC1-amd64-disc1.iso) = 9c165c54a9cc931c240d2595fe4a860dbdc6e6c17046f0b79c94b4a0074fdd01 SHA256 (FreeBSD-13.5-RC1-amd64-disc1.iso.xz) = a273b8510693c64379f3cb3e3846d6331599a0b36da2d8ebc656754b075b2fea SHA256 (FreeBSD-13.5-RC1-amd64-dvd1.iso) = d0c6cf2d89e71d2ca8e05a18f1b9e7988646fa13a8ab2f3bea6ee2e849677127 SHA256 (FreeBSD-13.5-RC1-amd64-dvd1.iso.xz) = c88a836aa0b23a39a09336861ef3e20d457e85d0886f33c4e400b77ffa618519 SHA256 (FreeBSD-13.5-RC1-amd64-memstick.img) = e8e155b9eabc4faebdfdd33f604c495a86d2e9a4d0cca66b46485acbe07e94a1 SHA256 (FreeBSD-13.5-RC1-amd64-memstick.img.xz) = 91a1dd145f09f25b56d8b6dd0bdb7de28b4827baf4a6e7f6643550a28d0c5325 SHA256 (FreeBSD-13.5-RC1-amd64-mini-memstick.img) = aef926ffaf5e0449e3827fe31630659588292f7a05857bed61e2d5889ffd8188 SHA256 (FreeBSD-13.5-RC1-amd64-mini-memstick.img.xz) = bc1c3366ecf60617a94fe2b5ee2cb1d9a53c530acf9d3d23c5a7adaa2e3a4aa7 o 13.5-RC1 i386 GENERIC: SHA512 (FreeBSD-13.5-RC1-i386-bootonly.iso) = 5700e43597f93c7b0da4b41724e186796f6d23c0cbf82e033e49c5eea14f5df54611661158699dcd7c6bb3e6e11e56e7507d078e7eb25f6810b7b5d3445a20ec SHA512 (FreeBSD-13.5-RC1-i386-bootonly.iso.xz) = 2bd4f9e9b5a8163754601c9706f874c9f1084408dc36e8b403d0416febf3a9e9833cf77288789cc033e10158a1060bb0f0f5765f98d38715adf1bab0fe690a72 SHA512 (FreeBSD-13.5-RC1-i386-disc1.iso) = e810860f21da9d291e569f41690929fb2c6ebb7aeb43e7e40f619400ebc52adde16fc092f3481f3a244edda53e7898044704d68342726e65b6d1f9c8c23cea33 SHA512 (FreeBSD-13.5-RC1-i386-disc1.iso.xz) = b8b26708a1dca541e0d2f97fffd5eb9af7870785cf29067ffd63d96dbbcc836ee72e44859dcdd0e46fcc6536fb72cea973a715adca8ae6781a585cb5dc752e73 SHA512 (FreeBSD-13.5-RC1-i386-dvd1.iso) = 091335318861d610f4f876cf0cdc8d3471b6ae56f8b20dad4fc82dfb9b6f6b8a818baa44280f5fc8a67f7b418bec288f474b539d420ddf6ed11cd19b1dd02fdd SHA512 (FreeBSD-13.5-RC1-i386-dvd1.iso.xz) = be91e7eed3ff85b813b896d6c53bd19b82e663b8d3c824fa2d074ac80e5b17a8b434ec13d2a795d9da38e24626c3ffdb6f307991ee58ff13d5d0a1d4330809ce SHA512 (FreeBSD-13.5-RC1-i386-memstick.img) = 58892ebb1d9b6efe1c9ac38f9a22edc78710dca79ff50d90afc17b3d52ee4d1d8c00f096a088916cf0c6e09356120ea710139faae2d2b2bc6c5ad79224c0d9bd SHA512 (FreeBSD-13.5-RC1-i386-memstick.img.xz) = a5ad6337ae30b7061cf4673dcd8f672b505e08c4c09b7390c173d8ce2301a5c3ad0db52b05641c991a694314f3e7923252b8b8c7498819769d3fceffe2bce773 SHA512 (FreeBSD-13.5-RC1-i386-mini-memstick.img) = 4ab2af4f9db907b1f214b62b423c81019723a673ab0de712104aec384f855b6988ad35d777caa8666fa49cf4ef9c28e10df9d54c437c034a2d4751bb73d7b594 SHA512 (FreeBSD-13.5-RC1-i386-mini-memstick.img.xz) = c003ed622f2974ee902b45e56b61672a2a5a094fce521bf5a5e906776ae4a13961f5241b7bf004213a97be661c688afdc0e0bb7bad2af153e07da8e51da0af5d SHA256 (FreeBSD-13.5-RC1-i386-bootonly.iso) = b70b09bb33851dc7cd2fe140726eccadceea23ab9b48834660618168ab381b52 SHA256 (FreeBSD-13.5-RC1-i386-bootonly.iso.xz) = 133932d884d8fbf111c21c55bea314c05ff388059d22d3def0bab0cb223326fa SHA256 (FreeBSD-13.5-RC1-i386-disc1.iso) = 97d1a43753c8a18869bb9f86adb7f636218de313551437bd59e0d72ff66c7c08 SHA256 (FreeBSD-13.5-RC1-i386-disc1.iso.xz) = 6e170abbd26a6f561105d24f2ddb3727e14e648532c5b2cf7865b2b8236a8b95 SHA256 (FreeBSD-13.5-RC1-i386-dvd1.iso) = 0ba31695e34ff24bb1b14a8c3c1ad1da13689c259e0090f09169a6310fcaf9e1 SHA256 (FreeBSD-13.5-RC1-i386-dvd1.iso.xz) = 527f6d82edadf6d6ac7fcdb9e5dd286035b29c6317d0d97fb17218c31429cb79 SHA256 (FreeBSD-13.5-RC1-i386-memstick.img) = 855752755197ca6a4db9b177d5923a59168e0a90dd96731c0607b187673e92d5 SHA256 (FreeBSD-13.5-RC1-i386-memstick.img.xz) = c19aabe4f99c31621fbaa2cf1222c64f9b296848860d70aa8e5227354c67ea22 SHA256 (FreeBSD-13.5-RC1-i386-mini-memstick.img) = 54e604f8142265154fab0b6862f3259f3788348bdb6f3c8d29e4482d33e07aab SHA256 (FreeBSD-13.5-RC1-i386-mini-memstick.img.xz) = 96359c55fc40e0331acc728a20c742d4e8bcd83ac69691e2750a7d5b7fa1bd3e o 13.5-RC1 powerpc GENERIC: SHA512 (FreeBSD-13.5-RC1-powerpc-bootonly.iso) = 6556bbf255815f356c8d000fb9e191942905d53305f4cca254a9579d30e1894eac61de4022bc3e144ed2f1833462aa220397e6b60ed52075a2e65f6463328fbf SHA512 (FreeBSD-13.5-RC1-powerpc-bootonly.iso.xz) = 24758bfea7f79c06e99fcaaa43b18c15a606a7f2ab23e2475144997e925e8d021e41155f157e5a8ea7a14e94df409a58a8fac8ad48bad9cb2098c5097406497b SHA512 (FreeBSD-13.5-RC1-powerpc-disc1.iso) = dd2c08e95907ba269675e8c26782adbed6267b4dd1d9352db2085f1a58caef1426e2137b1512f295372177c10cf51b664c91f9a32f45bd2afae335ae73d10c61 SHA512 (FreeBSD-13.5-RC1-powerpc-disc1.iso.xz) = 66bcc3edacb47ae18440b7577ac4f8ee2bd799d6ef9017602a72a9cce29985bb8287299a34707e4f147abcd187ff45f71e2d52f7d69a95e0dd30b6f6db26b82b SHA256 (FreeBSD-13.5-RC1-powerpc-bootonly.iso) = bb763b1f32f7441b684d93b3b39b483df32889dc77289a4cc201c32067102f66 SHA256 (FreeBSD-13.5-RC1-powerpc-bootonly.iso.xz) = f3ccb455a0e13290b206261e4d1d26a688ea8eb0de8cc80b85e026de336742f7 SHA256 (FreeBSD-13.5-RC1-powerpc-disc1.iso) = 4f87336cbb659887aa978c8ed62634746e6cdd25ffef163f0950a71fdc2119b1 SHA256 (FreeBSD-13.5-RC1-powerpc-disc1.iso.xz) = 7a27a59ee74e93732ad76d39985ba3a0ee8389eae8520e67439e79a058c0f117 o 13.5-RC1 powerpc64 GENERIC64: SHA512 (FreeBSD-13.5-RC1-powerpc-powerpc64-bootonly.iso) = 5b423b3924dde6c09d906225b9abcabe6781cb5fa63fa796cf6ca977a7eb5b9ea4d83b35ad7815f77bdbd019d2a7eb1922b226b90f6414a80141138901bdcfab SHA512 (FreeBSD-13.5-RC1-powerpc-powerpc64-bootonly.iso.xz) = 02583058bfe14210ac1e01782fce8ee6b0836653652b282a11683000cfec44f2ef62a90d204acece1a677184dd4b5832ea1b8b41b4d886ad35acbf0f8623a7ae SHA512 (FreeBSD-13.5-RC1-powerpc-powerpc64-disc1.iso) = 8b5b8d69b7a2f14fb45dfebcf279cc2db45446bffea53c84a5c8cc5df92f12b8ddc8f7de8c42254684f66747535da772935a033b3d210bea3a2de2f9c0e335c5 SHA512 (FreeBSD-13.5-RC1-powerpc-powerpc64-disc1.iso.xz) = d7791a5f3188690888b0f8e18085afe06f25a6d38a4c27fff821c28e4ac8e919f5a667e241d2517d93ca0ef27b063470e2b9926caed53f5d39e999c81a648eff SHA256 (FreeBSD-13.5-RC1-powerpc-powerpc64-bootonly.iso) = ad7652c98b5db5aef05801745ba87f935f4754ed497b72dcb77dc2456273c92f SHA256 (FreeBSD-13.5-RC1-powerpc-powerpc64-bootonly.iso.xz) = d5655b762c1c0b89c14e8d5d04fa2a561fcebd2dfe610e0dd813a4ef79179199 SHA256 (FreeBSD-13.5-RC1-powerpc-powerpc64-disc1.iso) = 14bec55d57dc74ddcfee88a8a4addda88ff6f487f9eb5f68b945d0f721abad65 SHA256 (FreeBSD-13.5-RC1-powerpc-powerpc64-disc1.iso.xz) = 865dbc9012a262be75d76d76c4e147a83acbe5b5ab12a64ac17ffe40929acef1 o 13.5-RC1 powerpc64le GENERIC64LE: SHA512 (FreeBSD-13.5-RC1-powerpc-powerpc64le-bootonly.iso) = dbc90bcefdce89fbdb95c8c11d8cd0252c8a618f027c2121c9c5c74a95bd25936638409280407ba911bf0a8fdc6b1ad65db723597a8763a136279d6df092cfc2 SHA512 (FreeBSD-13.5-RC1-powerpc-powerpc64le-bootonly.iso.xz) = 376a667bfdc66c28a460656fa08cd7b7857486f88b571a46803cd6c7269445e24fe0df13cb4d9b321a55361f687a15eb04f0158c1289876612aa1e4b774dce68 SHA512 (FreeBSD-13.5-RC1-powerpc-powerpc64le-disc1.iso) = 8e60d0b6a46a7c207685e1303252035544e278210f0236d362d7be62a268ec46e001be08e399f58ad179aea13d4c04c8905977fc325a95730bcbc9df4d22c20a SHA512 (FreeBSD-13.5-RC1-powerpc-powerpc64le-disc1.iso.xz) = 88519a21a8460b41c9941b007b80a0c52616d7f9509a673d86bbf0e77f42732da1fb25219159de98c4151bb0356521d43f922375bbdc947a8b8ddabf7d2d9574 SHA256 (FreeBSD-13.5-RC1-powerpc-powerpc64le-bootonly.iso) = d3dc136246b7c6ab452ba1ed44cc2427d63497ca603ca440bb5baa0c1c280687 SHA256 (FreeBSD-13.5-RC1-powerpc-powerpc64le-bootonly.iso.xz) = 5f772cac5b07e28e0f658874c3559c6cacbe801feb82fe6139fcea0d14b1c366 SHA256 (FreeBSD-13.5-RC1-powerpc-powerpc64le-disc1.iso) = 1733d7edc08dd5d56c6c59dd7ec2d1fccd4e69cb696ceff0327dbb3c56f97322 SHA256 (FreeBSD-13.5-RC1-powerpc-powerpc64le-disc1.iso.xz) = 7a7803d0213546db2663e71b152ae41c781696cdc40248860f0d61052dadc56d o 13.5-RC1 powerpcspe MPC85XXSPE: SHA512 (FreeBSD-13.5-RC1-powerpc-powerpcspe-bootonly.iso) = 919e585c03bdc7fce155d0f840e95baa9794d475320f72229cafb9a27e9e53d3d15a5af60c08e85d2b83fae7b7195a328c9ea89cb90453fb62865a4a0d29b771 SHA512 (FreeBSD-13.5-RC1-powerpc-powerpcspe-bootonly.iso.xz) = eed96daf7dc63ad8e3a631ceb713b717cfb2e40bdc7f3628307df776b5c7e9eaba15253f900e399b2aa30b7486d5179f3ab2d1d89c8fd5d5704b07aafbe99d88 SHA512 (FreeBSD-13.5-RC1-powerpc-powerpcspe-disc1.iso) = e025f2f9823a0acf663ddcbfdd3dd9d969ac4dbf717951009dc7b96b72b1d5fadf0b3749c81c6984fbec451f15d511db0a78a1a15137786a01d325ec4dba855d SHA512 (FreeBSD-13.5-RC1-powerpc-powerpcspe-disc1.iso.xz) = 97f2cbaa6a3922fa5af1837bf83a58fe63f12a0c16163dd449e4c82fd9b897c23b22be29c056fc837de0c03cc085d19f24c163faa489eb281f61808c922d6576 SHA256 (FreeBSD-13.5-RC1-powerpc-powerpcspe-bootonly.iso) = 7e4cc6fb1e82348aaf6a330fafbd492222812ecfe4d41052bd16fdc63d0bdf0a SHA256 (FreeBSD-13.5-RC1-powerpc-powerpcspe-bootonly.iso.xz) = bef509d1560b84ea201e9be248dd7c6b3dd2ed0f5eb245b8a67609b77ce56fe6 SHA256 (FreeBSD-13.5-RC1-powerpc-powerpcspe-disc1.iso) = 5718af15ea25856ed17376cd41ad89106402a6f71076ed578bbbff0b6de59d7d SHA256 (FreeBSD-13.5-RC1-powerpc-powerpcspe-disc1.iso.xz) = 4713e83fe66db83af4971d65770aa6820518cf36468e4ea7449a36cf230a01ef o 13.5-RC1 armv6 RPI-B: SHA512 (FreeBSD-13.5-RC1-arm-armv6-RPI-B.img.xz) = babe0dfd1ae2cf3e5375bda5f12cd9ca8241aaebc477ab5367b5305d40a656bad6007dcbbeec222f65b5075bab0e6d37075994147691c2b18e4655b86dcc1554 SHA256 (FreeBSD-13.5-RC1-arm-armv6-RPI-B.img.xz) = 2160e7826ef3729f82070b1c8d66657c2afe7666cb4d1ab1924570decf95535e o 13.5-RC1 armv7 GENERICSD: SHA512 (FreeBSD-13.5-RC1-arm-armv7-GENERICSD.img.xz) = 9d74ba30c9a67f8f44ca5274dd0c77ecd594278194d330e1289458e4c7a8aaef5dc9470ee83779ca19d3610f040e7e5fe0020eba75ecf2d26c672ffecc79532d SHA256 (FreeBSD-13.5-RC1-arm-armv7-GENERICSD.img.xz) = 79a6080202ed3e5efceafabec0b37259002c2504d79837ddcf2c882e914285a3 o 13.5-RC1 aarch64 GENERIC: SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-bootonly.iso) = a564861c07e3ed62c2b2fe65ea837c92e0c0d98763af6623405e9f49ac06d31ab27c4cfbdaa8481528db193d2231526c29ac7b67935fb3ed19bfe36b3839e851 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-bootonly.iso.xz) = 963fd95980f560a6299f30a9debdb4aba3f2aee9d260785bccb0e9dab60d00e63c3350a0e34a193d971bce0c598d6331ec343cc447e59e091b9bb37270405685 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-disc1.iso) = c574f11e7112cca7fd28859255de284d7086a376b08fd4ea9d4064a0305bbaa05e0e7434fca6748a763fef9512ccfa68ffb3bd58c570d5e1f93797fd6f09f520 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-disc1.iso.xz) = d22ffbf348ebef8b3a4bc949ed574b5aac39e17124bbaa0135aeae7a87863d3938015b7de387c01a787be635ad9108e10d3c11cc386e623b84713504e9823084 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-dvd1.iso) = 8173185bf727f7da5489e1f59bbff7604375a4f24dc2db35fc6fb3a673ce1ef36192f779c0ce68dc687486f0e452e6c4d988b26de1b9f73901bf7145dfa9d69b SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-dvd1.iso.xz) = cf3571eaafc02c5308c04aa8e178f5b3b922b11ce750314d880342a1af3e2d8e68ec5b7b03139fe262bd853f5751cce4ca7d10b84d9af17e247339131c650083 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-memstick.img) = 099195c01c540092098a5f887f11a12bdbf9d17b87d4f959bd92da97f76627711c4e613c5491b15e5217a6d00052a9780eb144549f6c7879158cb65c10b4c41f SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-memstick.img.xz) = 402060d21840febc0dc2cef3efe35ee1f59d435d534add99f9d05eb2b774372141b20f2d71b46ffecba6786b0bbd2e624a69fa01aa475da14c1af0b2784f7ffe SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-mini-memstick.img) = b592c11394f8a2813117c7470a2c05108d5043167fb33299e8e6eb28cff10559cbbc42642e812a8736cc9f60420c18d913d4534a5f230ece966f75105047d7f2 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-mini-memstick.img.xz) = 02efe20ad42ee1f9ff2d7a92023b7e95010eaa3db5737e05cc2ea2ec74bc101a4d2e99736d2c7375911679686e50ab3b8678c419441aabc9f278dafa74e9676e SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-bootonly.iso) = f1f98ab64f54e32ca7da35c3172da734a381ea42290f080ff8d0d3ffb6529619 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-bootonly.iso.xz) = c478c8c9c241764f1fcf3975dac0ceeade4309473a490f838f14ec1433bfdee0 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-disc1.iso) = aa2bd7ec2522e8205dc39556ed7570f3d52c01b6e0ed90b0bb1195e6c18d225d SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-disc1.iso.xz) = 77ab69b98f46541cc51d016d920c2e2962208a8645d105bf31335af6a2efa987 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-dvd1.iso) = 4fa2fa86a374d5bdfe1fbc833ba25b0ecce767fbb67bbba06b3380ce6cf0b7d1 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-dvd1.iso.xz) = 73253d3ebc440915d80cd726e199de292f399d66ab928451c4253ffd7c8e1485 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-memstick.img) = bf0835bba41e3fccfe0f8440a5d598a3bd3282fe7adce3eeb59a1ea03ba8f534 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-memstick.img.xz) = 006750e39de6aa98e72d059a2bc0f7234e4ddb7021e9c5328566f551983b8912 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-mini-memstick.img) = dec9aadced19f1236eb71f38bb0da8565435f9ea8bcfb49202c23c23b4382174 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-mini-memstick.img.xz) = ef37fc86bf5a3986bb6ace4a4af4386cba8e173f2375d1aa3998367ee7d21346 o 13.5-RC1 aarch64 RPI: SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-RPI.img.xz) = 19f947802fd23350f400ec9ecbf68201d949a8cb9bb73d42ffed715b41f5c6dd47ac63848f99fb9abef8c2f497d1f723664e4a4e4b23ed8baad24c6d16e2dc91 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-RPI.img.xz) = b2b109618cd63ad483a4b4a236c24e3d9eb8203fd8bb3942c11faf0ff77b46b9 o 13.5-RC1 aarch64 PINE64: SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-PINE64.img.xz) = 84dc117aa76d85ea781fbc9fb8806dd58386bf4ab1b47d8394bfddafc411cd7652aac5cc37b3849ec433109d29892be6fec8b0008ffc7368767d2dc4d9b57b5d SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-PINE64.img.xz) = 9fc176f9eb2d5f21bf1b74f6d7c2af352482f1cf0c59c8a93fc1c0c9a6621b07 o 13.5-RC1 aarch64 PINE64-LTS: SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-PINE64-LTS.img.xz) = e83697646e375da516fe1bffdee61ec8545f1af5c5fbe7283de382eb02a4b93a071afe99d57e621ff62f3e1eb263163c19d10bf73926b44e252d77995c151545 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-PINE64-LTS.img.xz) = 3c978dc0a132fe63642fa7e6c82210b5b83787219273edd2088f085e1656c10e o 13.5-RC1 aarch64 PINEBOOK: SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-PINEBOOK.img.xz) = 9c3dd09be6414e3ba350e6786dce476647ba1aec3091cba4a542d5b296aa232128bbd3d6d379108b200e1892d3925a6fd10394fa115259aae8add4c4dd8d3c00 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-PINEBOOK.img.xz) = d8a21c7721b12d28eecd5d66be6d512366302cdba0215b21ebacf068a3d19352 o 13.5-RC1 aarch64 ROCK64: SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-ROCK64.img.xz) = 084f0bc23ab0e41892997b28f335f3a8261654464a04d74b66f2cb564f17360d60ea464baf37468b02c85633848bc45de9b4193fed5b74b28fdcaf224a66b324 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-ROCK64.img.xz) = a8fe16ab2c62ee4a1487ad6818155c3082c1ff5542ae96635ee7f23fabdd932b o 13.5-RC1 aarch64 ROCKPRO64: SHA512 (FreeBSD-13.5-RC1-arm64-aarch64-ROCKPRO64.img.xz) = c0cb720cc9fbfe14da3c2bbb783717154cbaa158c804dc8a1cdd9e3adc9f3f2777423427dd485ddecff6726d7ddbe1e011e8e4a28775ad450ec52424e3dd9f80 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64-ROCKPRO64.img.xz) = ebac7405d1d2b6702e83fae1434060447290a52825a323485d8c2943e77a65c1 o 13.5-RC1 riscv64 GENERIC: SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-bootonly.iso) = a315373171c38625e5b012ec92a317f8d69d212d20c765c797de77b013cded553bc401f33277dac2034f11b5faf761e4c0ac3db282aa40ea21c3b55ecef701cd SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-bootonly.iso.xz) = 8429e982845c0575ba10bb7294a4bd5c4ee5f0d81e9387c2e4662d0fd07f98b96eb5e18c283d3fcbea6b861a4cb5356a29cecf77ff875c3f170882ddce23140a SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-disc1.iso) = da309bc6033058adf43e7e22e2925055433ed850f9c38d9400bf96abd2a53a41578939cc78c2a6357c4951b17aa5817967bc017af9177aff270738a762f2642e SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-disc1.iso.xz) = 2016e83288c6ba3dc412e651cafacba572d69d30d0b890ddf3f7c0bd21b31d0cb723ac5c4618dbebc5da47aaf0ff03dd20e6f665449da734da5d3baeca48d851 SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-memstick.img) = d6eb451442658c781247781bc637eabc5b2625864a1fca729812358a3584839a7ec7b4a2cf6ab8c5dddeb2f1148bc59c506cb5a11ab2a2541fa9aead23a09468 SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-memstick.img.xz) = ea5f6ed65d2238025366d25c00f3f40a98b03e7244a904b984c71e1fcbd992f452970a8a871f0e2c9f014379d19112bb5baab9f03357c9fad31c11b1f09bab1d SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-mini-memstick.img) = 76ce560c780dc09600980603b2b6bef06c708bb1898c8a0b4bbdfc2e1a5600e81802436873f8e33268ee311b2e777d4b52e3ca37bfbad01d27580c8a9cf8250d SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-mini-memstick.img.xz) = b52a6433afca2c0740736b8922e92ee1ced3ac56fe95137b472ce198cfaad83662ed317fde198171760ef508fd20658f7e4f22b01020d040473e75bba933c5bd SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-bootonly.iso) = 33ec258863f2742f5df6a0994f1728633ea471ad490fcd4ed2cba555c66a3dee SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-bootonly.iso.xz) = 1037a726e1d382ce130abccbce66d1ff83a559f8c78929c9e9d0ce415d78935e SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-disc1.iso) = 835b3ccdcd65b1cd8d0c96e01fac34780ca32b45d5af02f4bdd8e41377b09bc8 SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-disc1.iso.xz) = db2aedd53af5d4aa708fdbd7d41447d080185b5e6a015bd4dc27122d22989226 SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-memstick.img) = 68ad39f38a66ad4087e133c694e74dc00a425b9366107882e4b6d5efe933c2b5 SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-memstick.img.xz) = 27790fffe7f689434a5ee64f51878adbef41b9f72576fa9943b9d1244449e110 SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-mini-memstick.img) = a994bc1030e9e90cc13a24472548fab329b422197129cadfa1a230be783e3b5e SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-mini-memstick.img.xz) = cfbb66fadd673c414a86632cbf25bc6470d1f388780b423d8f6b7df8f6f65921 o 13.5-RC1 riscv64 GENERICSD: SHA512 (FreeBSD-13.5-RC1-riscv-riscv64-GENERICSD.img.xz) = 34bfdb1f2e2a1bd61a04ef0493aa00b4d6f79800638fe0251c949d0a80bcced130f5ae503e67f37ae7a9e66cab87306187224baf8017d34e1b98906ee1ceeb7e SHA256 (FreeBSD-13.5-RC1-riscv-riscv64-GENERICSD.img.xz) = 8a594116baa091442271f23ed8fd50540986cd2cf12f05116b1d397e567bd28d == VM IMAGE CHECKSUMS == o 13.5-RC1 amd64: SHA512 (FreeBSD-13.5-RC1-amd64.qcow2.xz) = 1d9808c3cf08a40f7e112d6f786facd965643d3027d1bcc45348d00e2892c5b2727fb0bedaabe81a13f2a927a0137f1f974b9c475efee0e1597ee9b8420a608a SHA512 (FreeBSD-13.5-RC1-amd64.raw.xz) = 31801931ce2227087ee840df561ca64df4bfb03c22fb4055b5a36a9d0cfe44d3d363e64d0ad4cf11ebb527c39ebaf4cc510797c11480d2730c85d4eeed57cc52 SHA512 (FreeBSD-13.5-RC1-amd64.vhd.xz) = fe1aed6b1f73810bb735d2aadc0512a767ed4c0f71cddb902e7e296c36b1a1ac3d9a82d05cf50c88c41feddd04e513e6c2108254319a0e9d1fbe81529334428c SHA512 (FreeBSD-13.5-RC1-amd64.vmdk.xz) = 5d39794dc52243cc2195bf9bb448f08b3655c47e2bf141f076188bfb1af972b68c3eb359d57e949ee9bbd2a8f29b89826c8dfe6bc46dd3f93ae4bbbc18701f59 SHA256 (FreeBSD-13.5-RC1-amd64.qcow2.xz) = a146dac40877a38a73381b64d0f6c5c8c133061078147b4d499b8c3968900334 SHA256 (FreeBSD-13.5-RC1-amd64.raw.xz) = c2169c0f561ac2552b7e0d1fc11509fd24009e7fe5fa4a0e58236e7101e8e2f9 SHA256 (FreeBSD-13.5-RC1-amd64.vhd.xz) = c206ab04d2c55b0a39e9dcfb2621df1ffb00a6e802b4eb0f7611a79829b92482 SHA256 (FreeBSD-13.5-RC1-amd64.vmdk.xz) = 75fba8a7ac031c7cb80629a840301f39f2a75cc2d10063152b0075ab34b51e9f o 13.5-RC1 i386: SHA512 (FreeBSD-13.5-RC1-i386.qcow2.xz) = ba083c9b46ea8b035881034ff4e7965058de343759c92292ca9d55d21de13cf433a129da1e156a895933d108084879a1182845694f378cec9b6432552f76f684 SHA512 (FreeBSD-13.5-RC1-i386.raw.xz) = a912083f9c56bd63923f5dde1f19e4ca72dcf40b2ea46baf701de102f37a89e074bc509a6adc4d3c95000e0b2ce30bd116e101fbb4bdbb1dad2929ac32102bdb SHA512 (FreeBSD-13.5-RC1-i386.vhd.xz) = 7c9648d4fe7fcbf875645c0f9924b160d0c77ad9156ca62f9b81b457b909848db3ad3692b629b8f28add58ba4d8aa21f83418fa2b9fa79e5954c762c3fa3310f SHA512 (FreeBSD-13.5-RC1-i386.vmdk.xz) = 6bdba237f1819d7f76c02d1c48f6019973252d9caaeb75e21f981c2b56fc7dc63e2bb4f91638aa517a8ee2e14ad9355e2d50f104c715fb491fbc8216d0e9d04c SHA256 (FreeBSD-13.5-RC1-i386.qcow2.xz) = 775b00f76e11304d52a8c24312531cf1bebfbd14e1a2f10e36e1a025349cb58a SHA256 (FreeBSD-13.5-RC1-i386.raw.xz) = 0a750069f0cccd6d125673f8cf2b21ba743617e95e7ae87edc4aab2a95765579 SHA256 (FreeBSD-13.5-RC1-i386.vhd.xz) = 79411f66d6687ba9d625d66d062adbb25e93d2b2869221935eda2475700dd1e4 SHA256 (FreeBSD-13.5-RC1-i386.vmdk.xz) = e8a9cd5d9ea4cf6e43a3fbb0d12526df337cc90ee8d0a88cef1c8455219832c2 o 13.5-RC1 aarch64: SHA512 (FreeBSD-13.5-RC1-arm64-aarch64.qcow2.xz) = 8e523fdead6b5e8f44e79e12d0847ab1a0b4ab61c3c8f7f813315eefa227145c2479a6a4d3defb49a271d0de750c80315887ff5f12059dda75f5265aa811bea1 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64.raw.xz) = 9b25a6e6d871243aa3e079ab6d59cfe60f29d4139145668aedb7a4539d038c29b76309192e1945c518fc3869e5e782dfbedae3c433ed057c2bb1b4c0cae789f5 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64.vhd.xz) = 79c6d6ee924e7e4f287cd7b925f86f446ef4a0bcd59ae50b14c0c0bb531549ff24f130edaa3cddca6e807163a48e8c512221cad01dc275ac32870f420d323276 SHA512 (FreeBSD-13.5-RC1-arm64-aarch64.vmdk.xz) = f6e81251ab37dea893a78d53c4f3f5245c074764c6aae0443246ab82f3635a8cd9b78b40beb5fc97ccc431dd14a3dbd5c7ecb848820403f1396620f00c21408d SHA256 (FreeBSD-13.5-RC1-arm64-aarch64.qcow2.xz) = 6c5869bda1fc03813467fb9ec771f70f5e704224d4b20cec7488730e7c4038bb SHA256 (FreeBSD-13.5-RC1-arm64-aarch64.raw.xz) = 607259cd78a402807c64494612cf2d6b7eefd3f9f5ee121c073ed60974157bf5 SHA256 (FreeBSD-13.5-RC1-arm64-aarch64.vhd.xz) = c3d17d62368dae5a7153b54ce3c4937d16122aabf65979c2b01887dc02ca94bf SHA256 (FreeBSD-13.5-RC1-arm64-aarch64.vmdk.xz) = 88359d97e8b683b4c57d2c8d0495a43fa3f9d3eec693d089c073ff640810d539 o 13.5-RC1 riscv64: SHA512 (FreeBSD-13.5-RC1-riscv-riscv64.qcow2.xz) = 59be9b8e04862b641ed39807f0550af97a6cd5d2a14878669238167c38567562c426ed349bb961c68f57ed87d3959ee2ee2868c70758bbf39b7b87384999e34d SHA512 (FreeBSD-13.5-RC1-riscv-riscv64.raw.xz) = 88e5419f8efd59f89dee5464f9a091b6bdfa4e648801bb47b1ba28ae65681132c7b4c1be7d6b95af24f81ef8f73960602d57c201a978275aa3fbf961632601ab SHA512 (FreeBSD-13.5-RC1-riscv-riscv64.vhd.xz) = d4a3ee7cd44d90c8e1c851a8f4409246de58fa45b85d8019df3d6ae75790e04d837960be34ba600c2620491509ca9c8316c2722e78ecfdd541e012555ac99cf1 SHA512 (FreeBSD-13.5-RC1-riscv-riscv64.vmdk.xz) = 1bad64e2456eb1af0e51ab3e7fc95c34636b993e87f939d96d15fd1c7f8963f9567fd2804f012a11631e25aab0803a40e0e359de40f8c85a1b1653664146c0ae SHA256 (FreeBSD-13.5-RC1-riscv-riscv64.qcow2.xz) = 027f1a07d02e656eb4a55ce628c6d7de7ecd1ba752af13655d6e65f5cb018366 SHA256 (FreeBSD-13.5-RC1-riscv-riscv64.raw.xz) = 4f93b6b3cb867309a66034ac81a06e5c0eadeaa8e752dbbdd8c2feaab02a6fd4 SHA256 (FreeBSD-13.5-RC1-riscv-riscv64.vhd.xz) = 812c2706cb3ca2d2622638471db863692815581dedb1c26050cd7a4d02c736f7 SHA256 (FreeBSD-13.5-RC1-riscv-riscv64.vmdk.xz) = 72ffd4999978bc829f8c3160b76a13d63e857255b6f5b05e07c2571879f96e70 Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEglY7hNBiDtwN+4ZBOJfy4i5lrT8FAmfDu+YACgkQOJfy4i5l rT8tlA//ar0ZAnC+EYCcF1R2VSNlpEIGehjVcsF0EOXI5j5gkXdkEl38v+KnLmmA o/JnGeUBnRTnhrhH5mhs/XQ7BPkKAOqJQlxGTtoRxYtmTCR1O7gUIUTD+4DEF0NO OJtEBVLofvxpkoLDn4J4+0e1CEIBaoowVoVRycY2bJX/nqdz1zMDyy6xk8DScGaY Js+h8NQ6KTIw/QBaGCzlMavmq9jtSfZNjJiIsdv37gOZZ9h/q85zsP8Yt4SYjJBz cuWipnCarjgho8fkigssAzB3G4JX7nji4cPm9txHzTvwZMg03rqeTZR6zJT8DVIQ gNjNrLXp6Ete5V74ZF06UfYLPbrc49FjoIK3z8hXfcgD2tm9bWtTnQ9uGnUNs0Qx Iku+TO/xbs4xtEhY/bELVLGfk4WC0mo/UkYSVCGe4fyqoNq3Ncz/BHagmTNgToXp 1NgM52l6QhKznWczpTobE3mz8pcT8KvoKSfkgVIBnGz8T/dQCil3GkvoxFGcYaUq WD2wtGiMlPOoUgbxNjYBSCx3dyiYg35bRwMYu+3IETUxG9mAbzvKlMCWy3UCa4Wb l4606WoYT4Q3S/RqB1pdgGcDyHCvwTjPCBJkLgKbU0/SRWG2lsDUjn+DAy83OMGG 2GXHqx9oE9bcYpVgeP3r1JRBCAQOhuWO7oh/pmEV65CjC6VhIzs= =DPgG -----END PGP SIGNATURE----- From nobody Sun Mar 2 12:02:03 2025 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Z5LCd0WGxz5pC6J for ; Sun, 02 Mar 2025 12:02:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Z5LCc4cHCz3WHH for ; Sun, 02 Mar 2025 12:02:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740916924; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SgcVCvpuqDLfwVhH0oY2zW2sQPfjF6rH2mw0KLzP4Kw=; b=shZG2MFzcUAO7NZK1CEA/UwMkCeEU5r7f25TywMRwZtAzSg8GHOOZ4xeZYaPXI3cklsIwJ jBRkAWTTiIqardcXXGW98qVg2R8ckPAT1Drl2AZPjuKa1yWenBmIGwV2rrvcVIZUSuQ0uH FkTt33g8FbWyCymUEvlhjOC4WzzcmCnVA/Iy/+C1e2HnkPSrDiTnRY6iTO7xkiz/5uUP2L X+QDx0vrp2O9uL3JjbNi6/AbkbgMUHIh8RAwfMiWF0BlFdPgQL0Qou7ljy3W803MK87sPo mims+jnkWIhGI38jVBNDKE46PJT3GMqjoqMAdlgWcV2xXaWqQ1LgPZrl0qytNA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1740916924; a=rsa-sha256; cv=none; b=Sl8b4eL7Y0XpIvQu5U9A9wLcp3E86f08fqNNjgKXjknEIepZOuMlWqntzfSp2UBwxxcogy NjCInGFTMri/DraJX7qF/PvH6RXlByoubgJQmZBKGoz5AUmWgxPN6fb9N9FkgGVzVW14uL FDlXqXGa5XroGvUNnaZN9QNWeZ3kED2uMAQpeXi7lJUpTO4iDrPEORJEJ1nHduLbOjDzBk UsmcNgmqRJILhovYYJkSTNcQ4DDQrEp8wbe8PvDtDP8RTFbIHShK3eKmBS66qA6H1GC2Ok 9D8T15dkj9xbfKfJ6fnhsuCQXOMPpUH5UlJMHnh31M5rv+Vj3RbUboanfbl+rA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1740916924; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SgcVCvpuqDLfwVhH0oY2zW2sQPfjF6rH2mw0KLzP4Kw=; b=tikeJYhYJvbApozZsE4pmYArAFdhcQ/fKIrY6jGPMvqgcILsC3HfB2B03fGehVeDuuKq5A NsEfkFqzEr/jnTmMjiYIBCchcbkevcHLMyKMcUhZTa2vK11RSinoqQGe+3pyA06uW4AvFf b6/ac0otU5nqXUl7tS0eCwBN2UVgSe+2f0l4rDeW9nFS7N2BkbX56ruDJBEz+tBDFbFb6Q h2ea2Zx1HoMIUhLgCIMU1HA5vrRBUudIpNzrgfKveZrE+8Je2e3WerOi9pgNV7gdZGRPnj Nf4TnoJkcj5lj8NiPjfp9t5z4SbCi1PAI8I+mc0UhxBTWgWSw+aiSoFoMncwjQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Z5LCc3pmNz11JF for ; Sun, 02 Mar 2025 12:02:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 522C24pk091525 for ; Sun, 2 Mar 2025 12:02:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 522C24Xa091524 for stable@FreeBSD.org; Sun, 2 Mar 2025 12:02:04 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer Date: Sun, 02 Mar 2025 12:02:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.4-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: imp@FreeBSD.org X-Bugzilla-Flags: mfc-stable14? mfc-stable13? X-Bugzilla-Changed-Fields: bug_status Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246279 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress --=20 You are receiving this mail because: You are on the CC list for the bug.=