From nobody Mon Aug 19 17:21:44 2024 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 4WnfXT0vshz5T875; Mon, 19 Aug 2024 17:21:45 +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 4WnfXT0bnYz4JZt; Mon, 19 Aug 2024 17:21:45 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724088105; 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=TeKsaMddvdd9scABpN5qtmpMyG3yaqYhasArGQr7+oo=; b=XlC0BHIgpl1TJJLtjdx5lFpOEeyoF5XJX7TiH/EjYAG4KhU1ud7i7i4kqBNBJUWRdb7+4n 1es5LowwrZwrCdHfgl3ibQb+LQcF6ud6bb8PXUpa9pUH0kylB2pYfgPL88yv+F94uqAL+h MoPx2XgbWV/U7LgER2wogoDdCqH/Pc5ZvQdg0IxdTytXVabBu7KKZXmErAL5HPjPSLiwmK J3uK05rxCd+F64S4aTqJ1ntslnXRnOXDprR+r0CeTPIMWsAB6KQK+FMcYxQdSNy7/Zxo9z 56Z9uePD7CSEUxzduzIBPLDmb7gP8RlbCGqIqNDHglnjfmNiyCbckXJb6QRvHA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724088105; a=rsa-sha256; cv=none; b=leoOdLt/Or8tHf7jRRYOWEHlViNQTui3kOxMoPE1Ivx2UPggY8OTX0/L9tIRqCAF9+Ce9Q rDzQ6aZtSLKldn/rTF0ZkPNn1aOJfbAJFHiGpW6y3HGLdLbenxDMm9gpplobEiuWSVDmDa XLLftwFieQKcz5TS0L+stAvj/0VSEpvbqlpRGV9jiWlBt1UZ6+iU1bVmNNbUUcqlJ1Od93 HeuGipShfPC+9KNRbFK3mnMjb/sIkag9AaoAa9ujSHXEwYG6jG3x2mjkvYeHk46L83VETb etuFmG0xmbMaoUdOwnsfuOJ4EwzUGZ/7BV4uCE8S/w2+dt5IKwOyHayvKkWvSA== 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=1724088105; 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=TeKsaMddvdd9scABpN5qtmpMyG3yaqYhasArGQr7+oo=; b=Ajj27nfnbTIgBLLN9wiXdD3ObYnhmcEVt9BWMJbBtItQgzFbhQOleNqyLK1BS32PG5nptJ 5OV8Y9xXLP6nusOf6r72e7vgign9VqVx6VWa0drITl0T1GN4CtJQYMMPPYVGptM27WsJbh cfFWH57oMSoWDJbducgo/u9avxF6Ka6tGxN5i69Ez28EjxKrBLNavZ19Tpd0TUJET4sFza omNZoiKteGZVOE17y2DmaqQtweBko7TOyQhS3rbd3mCEHGYdn2lfo1Y0C4pcyeumoIrGyd vOVoJbSywqprCkNthVZCAS+vhClNBNzZV/CFWu8d3E/hBkQ6fmMIWMTqC1k5Jg== Received: by freefall.freebsd.org (Postfix, from userid 1472) id E8C052EAB; Mon, 19 Aug 2024 17:21:44 +0000 (UTC) Date: Mon, 19 Aug 2024 17:21:44 +0000 From: Lorenzo Salvadore To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD Status Report - Second 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 Second Quarter 2024 Here is the second 2024 status report, with 20 entries. It has been very difficult to publish this status report within the usual schedule: indeed we are late. Unfortunately many of us have been busy with a lot of stuff, both inside and outside FreeBSD, thus some reports arrived late and report publication was slower than usual. Hopefully, this quarter was an exception and next quarter we will already be back on track, with 2024Q3 report published within October 2024. Have a nice read. Lorenzo Salvadore, on behalf of the Status Team. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2024-04-2024-06/ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection • Projects □ Audio Stack Improvements □ FreeBSD GitHub Pull Request Report • Userland □ Capsicum-rs □ Service jails — Automatic jailing of rc.d services • Kernel □ Hierarchical rate limits for OpenZFS □ A low-cost conditional execution mechanism • Architectures □ FreeBSD/riscv64 • Cloud □ FreeBSD on Microsoft HyperV and Azure □ OpenStack on FreeBSD • Documentation □ Documentation Engineering Team • Ports □ GCC on FreeBSD □ KDE on FreeBSD □ FreeBSD Erlang Ecosystem Ports update • Third Party Projects □ Containers and FreeBSD: Pot, Potluck and Potman ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. DevSummit 202405 The Core Team has presented the status update at the DevSummit 202405. Details are available at https://wiki.freebsd.org/DevSummit/202405 Passing of Mike Karels It is with a heavy heart that we have learned of Mike Karels' recent passing. We want to offer our sincere condolences to his family, friends, and the community for this loss. Mike was an inspirational fellow developer and will be sorely missed. In Memory of Mike Karels. For more details about him, please visit the FreeBSD Foundation’s page at: https://freebsdfoundation.org/mike_karels/ 2024 Core Team Election Core.12 appointed Muhammad Moinur Rahman (bofh@) and Allan Jude (allanjude@) as the managers of the 2024 Core Team election. After Allan decided to run for Core, Moin continued to handle all the election tasks independently. The result was announced on June 12th, with 8 members: • Allan Jude (allanjude@) • Dave Cottlehuber (dch@) • Gleb Smirnoff (glebius@) • Hiroki Sato (hrs@) • Li-Wen Hsu (lwhsu@) • Mathieu Arnold (mat@) • Olivier Cochard (olivier@) • Tobias C. Berner (tcberner@) Mike Karels has run for the 2024 Core Team election, and was in the top nine candidates in the result. After a discussion, core.13 came to the conclusion that the eight members will serve as the new team. Core.13 takes office on June 12th, and hold the handover meeting with core.12 on June 21st. The project thanks the outgoing core.12 members for their service in the last two years: • Baptiste Daroussin (bapt@) • Benedict Reuschling (bcr@) • Ed Maste (emaste@) • Greg Lehey (grog@) • John Baldwin (jhb@) • Emmanuel Vadot (manu@) • Mateusz Piotrowski (0mp@) Commit bits • Core approved the src commit bit for Osama Abboud (osamaabb@) • Core reactivated the src commit bit for Ryan Libby (rlibby@) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://freebsdfoundation.org/ Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://freebsdfoundation.org/journal/ Foundation Events URL: https://freebsdfoundation.org/our-work/events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD. We do this in both technical and non-technical ways. We are 100% supported by donations from individuals and corporations and those investments help us fund the: • Software development projects to implement features and functionality in FreeBSD • Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD • Purchase and support of hardware to improve and maintain FreeBSD infrastructure • Resources to improve security, quality assurance, and continuous integration efforts • Materials and staff needed to promote, educate, and advocate for FreeBSD • Collaboration between commercial vendors and FreeBSD developers • Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity Last quarter we helped FreeBSD celebrate its 31st anniversary! This community sure loves to celebrate milestones like this one. We not only saw more users sharing their stories on social media, but many commercial users stepped in to promote their use cases and love for FreeBSD. It is exciting to see the growth of this project through the improvements made to FreeBSD, as well as the increase in users and contributors. Over the past few quarters, we have built up our technology, advocacy, and partnership teams to accelerate our work in improving the operating system, increasing the adoption and visibility of FreeBSD, and increasing the number of partners who help fund our work. Below you will find updates from each team to see the work we have accomplished to support you, the community and the operating system we all love. But, first I want to share a fundraising update. Last quarter we raised $41,154 towards our goal of raising over $2,000,000. You can see our 2024 budget to understand how we are spending your donations here: https://freebsdfoundation.org/wp-content/uploads/2024/03/Budget2024-Approved-Public.pdf. Over half the budget goes directly into improving and securing FreeBSD. If there is a security vulnerability out there, we have software developers on staff who can quickly step in, evaluate the situation, and put in a change or workaround if needed. We have a full-time developer who leads the continuous integration efforts and investigates ways to improve the tools to test code, improve test coverage, and help developers be more efficient. We have also allocated more funding towards our advocacy efforts. This includes creating content to highlight FreeBSD’s strengths and differentiators, talking to commercial users and documenting their use cases, and promoting the work you are doing. Please consider funding our efforts to help keep FreeBSD innovative, secure, and stable by making a donation here: https://freebsdfoundation.org/donate/. If you are a corporate user, please consider becoming a partner! Go here to find out more information about our partnership opportunities: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/. OS Improvements During the second quarter of 2024, 204 src, 50 ports, and 11 doc tree commits identified The FreeBSD Foundation as a sponsor. The Foundation is sponsoring 13 projects. • Christos Margiolis continued to improve FreeBSD’s audio stack and provide audio developers with useful tools and frameworks to facilitate sound development on FreeBSD. Refer to the Audio Stack Improvements entry for details. • Pawel Dawidek is in the final stages of a project to add hierarchical rate limits to OpenZFS. For details, refer to the Hierarchical rate limits for OpenZFS report entry and the pull request in the OpenZFS repository. • Long-term contractor Olivier Certner was active in a few different parts of the tree: □ rtprio(2): Updating the number of queues per runqueue from 64 to 256 □ UnionFS: reviewed work from Jason A. Harmening. Jason’s work fixes many locking problems (wild accesses without locks, deadlocks, etc.), particularly in unionfs_rename() and improves locking logic. □ Vnode recycling/ZFS ARC reclaim: Reviewed a fix for bug #275594, liaised with upstream to obtain and test a backport, had an EN issued and applied as 13.3-RELEASE-p2, and started longer-term work to improve the vnode reclaiming mechanisms and have ZFS pass the right information □ ULE scheduler: Updated to work on a single runqueue instead of 3 for POSIX compliance with respect to the number of distinct SCHED_FIFO/ SCHED_RR priority levels □ Miscellaneous: Many (26) reviews, ports updates, and investigated DRM problems □ Published a EuroBSDCon 2023 conference report in the FreeBSD Journal. • Pierre Pronchery continued work on a security-focused project with the Foundation that included: □ working on a conversion tool from VuXML to OSV □ automating the generation of VuXML reports across all ports with security/osv-scanner □ running Coverity Scan reports around bhyve and assisting in rectifying the reported defects • Work continued on a joint project between Advanced Micro Devices (AMD) and The FreeBSD Foundation to develop a complete FreeBSD AMD IOMMU driver. This work will allow FreeBSD to fully support greater than 256 cores with features such as CPU mapping and will also include bhyve integration. Konstantin Belousov has been working on various parts of the project, including driver attachment, register definitions, an ACPI table parser, and utility functions. Two key components that need to be completed are context handling, which is mostly a generalization of Intel DMAR code, and page table creation. After this, the AMD driver’s enable bit can be turned on for testing. To follow all of Konstantin’s work, look for src commits tagged with Sponsored by fields for Advanced Micro Devices (AMD) and The FreeBSD Foundation. • The Vector Packet Processor (VPP) is an open-source, high-performance user space networking stack that provides fast packet processing suitable for software-defined networking and network function virtualization applications. Tom Jones is wrapping up his part on a project to port VPP to FreeBSD. The code has been shared with RG Nets, a co-sponsor of the work, for extensive testing. • Björn Zeeb continued to improve wireless networking on FreeBSD. As with last quarter, the focus was mainly on bug fixes and stability improvements. Most of Bjoern’s 30+ src commits were to LinuxKPI and net80211 code. • Philip Paeps is working on a 20-hour-per-month, six-month contract to continue modernizing the FreeBSD cluster. This work includes moving more servers to our newest cluster site at NYI in Chicago. • Moin Rahman is under two contracts. Moin is nearing completion of a Center for Internet Security (CIS) hardening guide and continues work to establish pre-commit CI. • Mina Galić continues efforts to put FreeBSD cloud-init support on par with Linux support. • Mitchell Horne presented his RISC-V work at the FreeBSD developer summit. You can read about the latest developments in the FreeBSD/riscv64 report entry. • Refer to Chih-Hsin Chang's OpenStack on FreeBSD report entry for the latest updates on the project to port OpenStack components so that OpenStack can be run on FreeBSD hosts. Other members of the Foundation’s technology team contributed to FreeBSD development efforts. For example, Mark Johnston, along with Andrew Turner, authored basic routines to build a Flattened Device Tree (FDT) for arm64 bhyve guests. The FDT describes various hardware components like CPUs, memory, UART, PCIe controller, interrupt controller, and platform timer, which the guest OS needs to know about. Ed Maste committed a variety of src contributions, including modernization of tzsetup(8) and correcting an issue with diff(1) options. Balancing their regular responsibilities, Li-Wen Hsu and Joe Mingrone contributed updates and fixes to various ports, including addressing pressing security issues. FreeBSD is participating in the 20th consecutive Google Summer of Code. The 11 projects for this summer are well underway. 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. Partnerships and Research In the Second Quarter, Greg Wallace, the Foundation Partnerships lead, attended the Open Source Summit event in Seattle. There he joined Doug Rabson who gave a talk on the work of the FreeBSD OCI Runtime Extension working Group. You can check it out here. Greg also used the event to connect with a number of key tech companies to advance major joint technology initiatives. Greg’s write up on the event is here. Work continues on other highly-requested features. RG Nets and others have been making great strides to bring CUDA and related AI stack components to FreeBSD. The Foundation is seeking ways to coordinate across users of FreeBSD to get support for a variety of AI technologies on FreeBSD. One idea is to launch a FreeBSD AI lab that would pool money from supporters to get CUDA fully supported on FreeBSD and to round out DPU driver support. Please contact us if you would like to support such an initiative. Work continues to leverage the heroic work from the FreeBSD Community to get .NET supported on FreeBSD so that downstream dependencies can in turn better support FreeBSD. More to come on this front soon. Thanks to the generous grant from Alpha-Omega, the FreeBSD Foundation has undertaken two code audits of important subsystems carried out by Synactiv. Alpha-Omega is an open source project with a mission to protect society by catalyzing sustainable security improvements to the most critical open source software projects and ecosystems. Our most recent monthly update can be found here. The code audits will conclude in July and then we will then undertake a process audit and will also run a 2FA pilot. In Q1 and Q2, Greg participated in several meetings about various government regulations. In March, he represented FreeBSD at the CISA two-day Open Source Software (OSS) Security Summit alongside other Open Policy Alliance members. Previously, Greg collaborated with OPA to submit comments to CISA’s RFC on how the US Government can support the security and sustainability of Open Source. And in June, The FreeBSD Foundation joined the Open Regulatory Compliance Working Group at the Eclipse Foundation. This group aims to accelerate the development of cohesive cybersecurity processes required for regulatory compliance while offering a neutral environment for hosting technical discussions with the open source community at large. We are thrilled to welcome Alice Sowerby as a part time, contract Partnerships Program Manager. Alice is an experienced, multi-skilled leader, currently active in a number of open source domains. She is the co-host of the CHAOSS podcast and chair of the TODO group review team for the OSPO Book. Alice is providing program and project management for partnership initiatives, like Alpha-Omega, OCI FreeBSD Runtime Extension WG, and the Enterprise Working Group. Advocacy During the second quarter of 2024, we continued growing our efforts to drive awareness, advocate for the project, highlight users, and bring educational content to the FreeBSD community. Below are some of those efforts. • Organized the May 2024 FreeBSD Developer Summit, co-located with BSDCan. Check out both the videos and write ups from Summit. • Celebrated FreeBSD’s 31st Birthday with FreeBSD Week, which included many new user stories, and an interview with Beastie! • Released the Final Report from the 2024 FreeBSD Community Survey. • Announced the winners of the first annual Digital Security by Design (DSbD) Ecosystem Beacon Awards to celebrate innovators working with and enhancing CheriBSD. The Beacon awards are sponsored by the Foundation in partnership with Innovate UK and Digital Security by Design (DSbD). • Provided an overview of FreeBSD 14.1. • Updated the FreeBSD End User page with new interviews and a number of new case studies including ones from Netflix, Metify, and RGNets. • Published numerous blogs including: □ FreeBSD Foundation Delivers V1 of FreeBSD SSDF Attestation to Support Cybersecurity Compliance □ FreeBSD: The torchbearer of the original operating system distribution □ The 2024 FreeBSD Foundation Budget Journey: Choosing Where We Invest □ Why FreeBSD Continues to Innovate and Thrive □ Innovating the Future: Arm’s Strategic Embrace of FreeBSD □ Why FreeBSD Events are Important to Furthering the Development of FreeBSD • Participated in the following contributed articles, interviews and podcasts: □ CIO Influence interview with Deb Goodkin □ SustainOSS Podcast interview with Deb Goodkin 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.1-RELEASE announcement URL: https://www.freebsd.org/releases/14.1R/announce/ FreeBSD 13.4-RELEASE schedule URL: https://www.freebsd.org/releases/13.4R/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 mourns the loss of Mike Karels, who was the Deputy Release Engineering Lead and mere days before his death agreed to take the role of Release Engineer for 13.4-RELEASE. The Team managed 14.1-RELEASE, leading to the final RELEASE build and announcement in June. During the second quarter of the year, the Team has gained new members: Ed Maste (Deputy Release Engineer Lead), Dave Cottlehuber, John Hixson, Mahdi Mokhtari, Doug Rabson, Muhammad Moinur Rahman. Planning has started for the upcoming 13.4-RELEASE cycle. 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 cluster services to Chicago. Cluster software refresh Except for the package builders and developer-facing ("dogfood") machines, the FreeBSD cluster mostly tracks stable/X branches. This quarter, we started moving the stable/13 hosts to stable/14. At the time of this writing, there are 133 physical machines in the cluster, 48 run current, and 64 have been upgraded to stable/14. The remaining machines are slated for upgrading or decommissioning in the near future. Of the 290 jails in the cluster, 206 run stable/14. 12.x: Regular 2, Jails 8 13.x: Regular 19, Jails 68 14.x: Regular 64, Jails 206 >15.x: Regular 48, Jails 8 ----------------------------- Total: Regular 133, Jails 290 Total installations: 423 Running -RELEASE|{-p*}: 0 Total geographic sites: 16 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. 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 and Netzkommune ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Continuous Integration Links: FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD CI Tinderbox view URL: https://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 second 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: • Added new hardware purchased by the FreeBSD Foundation in Chicago site to the CI cluster • Repurposed decommissioned pkg builder as build agent and added to the CI cluster • Adjusted the job dispatching mechanism based on the machine capability • bofh@ merged https://reviews.freebsd.org/D43786 as Add preliminary in-tree CI infrastructure for developers so they can replicate an environment or results similar to https://ci.FreeBSD.org • Decommission armv6 jobs for the main branch Work in progress tasks: • Merging Pre-commit CI with CIRRUS-CI • Designing and implementing pre-commit CI building and testing and pull/ merge-request based system (to support the workflow working group) • Proof of concept system is in progress. • 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 • Planning to run ztest tests • 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://ports.FreeBSD.org 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. According to INDEX, there are currently 32,471 ports in the Ports Collection. There are currently ~3,497 open ports PRs. The last quarter saw 10,525 commits by 160 committers on the main branch and 1771 commits by 107 committers on the 2024Q2 branch. Compared to last quarter, this means a large decrease in the number of commits on the main branch (down from 12,991) and backports to the quarterly branch (compared to 888). The number of ports also increased (up from 32,244). The most active committers to main were: • sunpoet 3739 • yuri 1450 • jbeich 491 • eduardo 220 • bofh 200 • diizzy 197 • rene 188 • fernape 156 • jhale 133 • arrowd 129 A lot has happened in the ports tree in the last three quarter, an excerpt of the major software upgrades is: • pkg 1.21.3 • Default version of lazarus switched to 3.4.0 • Default version of fpc switched to 3.2.3 • Default version of python switched to 3.11 • chromium updated from 123.0.6312.86 to 126.0.6478.126 • firefox updated from 124.0.1 to 127.0.2 • firefox-esr updated from 115.9.0 to 115.12.1 • rust updated from 1.77.0 to 1.79.0 • sdl2 updated from 2.6.3 to 2.8.2 • wlroots updated from 0.17.2 to 0.17.4 • wine updated from 8.0.2 to 9.0 • wine-devel updated from 9.4 to 9.11 • xorg-server updated from 21.1.11 to 21.1.13 • qt5 updated from 5.15.13 to 5.15.14 • qt6 updated from 6.6.3 to 6.7.2 • kf5 updated from 5.115.0 to 5.116.0 • kf6 updated from 6.0.0 to 6.3.0 • plasma6 updated from 6.0.2 to 6.1.1 During the last quarter, pkgmgr@ ran 24 exp-runs to test various ports upgrades, updates to default versions of ports, subpackage support and base system changes. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Projects Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. 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: • Asynchronous audio device detach is now possible. This functionality already ships with FreeBSD 14.1-RELEASE, as well as 14-STABLE. • Got rid of the "snd_clone" device cloning framework used in sound(4) and replaced it with DEVFS_CDEVPRIV(9). More info about behavior changes in the commit description. Also ships with 14.1-RELEASE and 14-STABLE. • Several sound(4) crash and bug fixes. • More out of the box support for snd_hda(4) laptop sound. • Series of commits that clean up and simplify parts of sound(4). • Several fixes regarding the OSS API, with the most notable so far being a proper implementation of the SNDCTL_AUDIOINFO and SNDCTL_ENGINEINFO IOCTLs. • Started implementing audio(3), an OSS audio and MIDI library. • Took over maintenance of virtual_oss(8). Future work includes: • Implementation of an audio(8) utility, in similar fashion to mixer(8). • Implementation of a bluetooth device management utility. • Improve mixer(3) and mixer(8). • Improve documentation and test suite where needed. • Attempt to find a better (ideally automatic) way to handle snd_hda(4) pin-patching. This is an experimental attempt and is not guaranteed to actually yield a working result. You can also follow the development process in freebsd-multimedia@, where I post regular reports. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD GitHub Pull Request Report Links: GitHub Working Group wiki page URL: https://wiki.freebsd.org/WorkingGroup/GitHub FreeBSD Base System Pull Requests URL: https://github.com/freebsd/freebsd-src/pulls Contact: Warner Losh The FreeBSD Project has been trying an experiment to accept contributions via GitHub pull requests. We have learned a lot in the last year that we’ve been doing this. We have created a number of rules relating to the pull requests. In general, pull requests should only be for things that are user-visible, add value to the project and are ready to go, modulo final review. Current status: • We are able to keep up with the pull requests doing everything by hand, but only if we do it at least weekly. • We have discovered the by-hand process is tedious and error-prone. • We can stage multiple pull requests in a testing branch so we can batch-up testing. • We can automatically land the result so merged pull requests show up as merged in GitHub infrastructure. We need help with automating the process: • Add automated testing that is context specific (for example, run igor over man pages). • Add build/install tests that test-boot the resulting image. • Automate common tasks, like man page corrections, into staging process. • Add simple smoke testing for the staging branch for tier 1 architectures. • Investigate optionally integrating Jenkins testing to scale up the size of changes we can accept. • Integrate with Bugzilla problem reports and Phabricator reviews. • Improve the submitter experience on GitHub by automating common feedback to mistakes in the pull requests. • Create checklists for submitters to reduce errors. • Create better reporting about pull requests, especially the frequent contributors of good pull requests. We are coordinating on FreeBSD’s Discord in the #github-hacking channel. Join us there to pitch in, or just chat about the project. Once things are fine-tuned, we want to publicity to steer contributors, at least the base system, to GitHub pull requests. We need more developers looking at the FreeBSD GitHub pull requests. We will also need more developers to review and land pull requests once it is automated and the automation has matured. We sincerely hope that we can improve the FreeBSD contribution experience with this, as well as gain useful fixes from the community. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Userland Changes affecting the base system and programs in it. Capsicum-rs Links: capsicum-rs on GitHub URL: https://github.com/dlrobertson/capsicum-rs capsicum-net on GitHub URL: https://github.com/asomers/capsicum-net Contact: Alan Somers Capsicum is a lightweight OS capability and sandbox framework implementing a hybrid capability system model. I have adopted the library providing Rust bindings for Capsicum, and extended it with support for libcasper(3) and cap_net(3). It is already being used by net-mgmt/nfs-exporter and by a TLS-enabled FTP server (the FTP server is closed-source, but all of the interesting bits reside in an open source library, and an example server can be found at https://github.com/bolcom/libunftp/tree/master/crates/unftp-sbe-fs/examples). Sponsor: Axcient ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Service jails — Automatic jailing of rc.d services Links: rc-article part for Service Jails URL: https://docs.freebsd.org/en/articles/rc-scripting/#rcng-service-jails Contact: Alexander Leidinger Service jails extend the rc(8) system to allow automatic jailing of rc.d services. A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, …​) by default. Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (vmm(4)). The base system infrastructure and the basesystem rc.d services are committed to 15-current, and the handbook / rc article updates are committed to the documentation. Next steps are to extend services in the ports collection to be able to make use of it. If you want to put e.g. nginx into a service jail and allow IPv4 and IPv6 access, simply change rc.conf(5) to have: nginx_svcj_options=net_basic nginx_svcj=YES While this does not have the same security benefits as a manual jail setup with a separate filesystem and IP/VNET, it is much easier to set up, while providing some of the security benefits of a jail like hiding other processes of the same user. Any testing and feedback (even as simple as "service X works in a service jail") is welcome. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. Hierarchical rate limits for OpenZFS Links: Pull request URL: https://github.com/openzfs/zfs/pull/16205 Contact: Pawel Dawidek Rate limits allow to limit bandwidth and number of metadata operations per dataset. Hierarchical rate limits allow for granular resource control especially in shared environments, eg. when a single ZFS pool serves data to multiple, independent virtual machines or jails. Because the limits are hierarchical, they are enforced like the quota property: the children datasets must obey the limits of the parent dataset. The limits can be configured using six new properties: limit_bw_read, limit_bw_write, limit_bw_total, limit_op_read, limit_op_write, limit_op_total The limit_bw_* properties limit the read, write, or combined bandwidth, respectively, that a dataset and its descendants can consume. Those limits are in bytes per second. The limit_op_* properties limit the read, write, or both metadata operations, respectively, that a dataset and its descendants can generate. Those limits are in number of operations per second. Limits are applied to file systems and ZFS volumes (and their snapshots). The initial work is done and the pull request is up for review. Sponsor: Klara Systems Sponsor: FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A low-cost conditional execution mechanism Links: FreeBSD wiki URL: https://wiki.freebsd.org/SummerOfCode2024Projects/ZeroCostConditionalExecutionMechanism Contact: Marko Vlaić Contact: Bojan Novković (mentor) < bnovkov@freebsd.org> This project aims to implement a low-cost conditional execution mechanism, similar to the static_key interface in Linux. The current working name is zcond, as in zero-cost conditional. The idea is to reduce the overhead of rarely used features in performance sensitive kernel code paths. Specifically, code blocks of the following, simple structure, are targeted: if(some_global_flag == true) { do_some_additional_task(); } A block like this can cause performance overhead in a frequently executed piece of code. The motivating use case for the mechanism is tracing (as outlined here in the wiki), but the project will identify more areas where this mechanism could be applied. The backbone of the mechanism is runtime instruction hot patching, making it highly architecture dependent. Great care has to be given to security, because kernel instructions are overwritten at runtime. More details and some implementation ideas can be found in the project proposal on the project wiki page. More documents describing the implementation and design decisions will be produced, as the project moves along. The goal of the project is to produce a working implementation of the mechanism for the x86-64 architecture. It will then be applied to an existing piece of kernel code and benchmarked. If the benchmark results come out positive, it will be ported to other architectures. This project is a part of the Google Summer of Code 2024.. The project is still in its early stages, but any feedback would be highly appreciated. Help wanted • General feedback on the mechanism, API and implementation • More use cases besides tracing are welcome • Code review • Name suggestions Sponsor: Google LLC (GSoC 2024) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Architectures Updating platform-specific features and bringing in support for new hardware platforms. FreeBSD/riscv64 Links: Wiki Homepage URL: https://wiki.freebsd.org/riscv Contact: Mitchell Horne Contact: Ruslan Bukin Contact: Jari Sihvola The FreeBSD/RISC-V project is providing support for running FreeBSD on the RISC-V Instruction Set Architecture. BSDCan Devsummit Updates Mitchell gave a presentation on the status of the FreeBSD/riscv64 platform at the June developers' summit, part of BSDCan 2024. The presentation discussed the challenges of supporting the evolving RISC-V ISA, and gave a brief overview of some available hardware targets. It is informal in nature, but available to watch on youtube. https://www.youtube.com/watch?v=O7zW7Z9U0ns StarFive JH7110 SoC / VisionFive v2 Work has been ongoing to support the JH7110 RISC-V SoC in FreeBSD. This SoC is present in several existing RISC-V SBCs. The primary support target is the VisionFive v2, but this work is likely to benefit similar hardware such as the Pine64 Star64 and the Milk-V Mars. At present, the support in CURRENT is partially complete. What is working: * UART * clk/reset drivers * MMC/SD The next target is working ethernet, which is supported with extensions to the if_eqos driver. This code is functional, but still in review. Work on this has been performed by Jari, with review, testing, and integration from Mitchell. https://wiki.freebsd.org/riscv/StarFive T-HEAD/XuanTie CPU Support As discussed in the devsummit presentation, these CPUs present several barriers to support. The problems come primarily from custom vendor extensions: non-coherent device I/O with custom cache management instructions, and a custom (spec-violating) implementation of page-based memory types. Combined, these quirks require difficult and invasive changes to pmap, busdma, and early boot code. At the same time, we are seeing an increasing amount of available hardware based on this IP, and so support becomes a repeated question and incentive. Work on page-based memory types is underway and expected to land soon in CURRENT. This feature allows individual virtual memory pages to be assigned specific properties, e.g. cacheability requirements. The riscv64 pmap has been extended to support the official RISC-V 'Svpbmt' extension, and the T-HEAD version of PBMT. These alternative encodings are incompatible, but provide similar functionality. Work on the device coherence and cache management challenges will begin next quarter. The hope is that this foundational work will (eventually) enable board support for available RISC-V hardware such as: * Allwinner D1 (Nehza) * Sipeed Lichee Pi 4A * Beagle-V Ahead * Milk-V Pioneer RISC-V Hypervisor Experimental support for the RISC-V hypervisor in bhyve/vmm(4) is under active development. Currently, single-core VMs are possible, and the guest can boot to multi-user. Note: the "H" (hypervisor) extension is not implemented by any known existing or upcoming RISC-V hardware. It is fully supported by software simulators such as Spike or QEMU. https://wiki.freebsd.org/riscv/bhyve Sponsor: The FreeBSD Foundation (mhorne’s work) Sponsor: UKRI (br’s work) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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: Li-Wen Hsu In this quarter, we have published the 14.1-RELEASE on Azure Marketplace. Souradeep Chakrabarti from Microsoft has improved the TLB flushing mechanism in Azure. Work in progress tasks: • Automating the image building and publishing process and merging to src/ release/. • Building and publishing snapshot builds to Azure community gallery. • Testing adding FreeBSD support in Azure Pipelines □ https://github.com/microsoft/azure-pipelines-agent/pull/3266 The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft. 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 integrate OpenStack cloud infrastructure with the FreeBSD operating system, utilizing FreeBSD’s unique features while maintaining compatibility with OpenStack standards. In the second quarter of 2024, we continued to advance the project significantly. One of our key activities was attending BSDCan 2024, where we presented on "Towards a Robust FreeBSD-based Cloud: Porting OpenStack Components". This presentation helped increase the project’s visibility and attracted interest from potential contributors. We expanded the current single-node proof-of-concept (POC) site to a three-node setup. This involved detailed environment setup and network planning. Additionally, we began migrating the base to FreeBSD 15.0-CURRENT to ensure our project stays aligned with the latest advancements in FreeBSD. We also started working on adapting the manual installation steps and code patches into FreeBSD ports, aiming to streamline the installation process for future users. Another major milestone was initiating work on making bare-metal provisioning function on both FreeBSD instances and service hosts for OpenStack Ironic. Looking forward to the next quarter, our focus will be on refining these advancements and further enhancing the project’s robustness and ease of use. Specifically, we aim to upgrade our OpenStack components from the Xena version to a more recent release, as Xena has entered the "unmaintained" phase and will soon reach EOL. We welcome any suggestions and contributions from the community to help us achieve our goals. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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/url Link: FreeBSD Documentation Project Primer for New Contributors URL: https://docs.freebsd.org/en/books/fdp-primer/url Link: Documentation Engineering Team URL: https://www.freebsd.org/administration/#t-docengurl 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 During this quarter multiple pieces of the documentation were updated including the removal of mentions to ports that were removed from the ports tree, typos, URL corrections, and asciidoc improvements. These are three highlighted contributions in this quarter: • Best practices related to vendor import were documented. URL: https://cgit.freebsd.org/doc/commit/?id=fe494e72df138266f6da2b9170cf0215275a6aaf • A section about service jails was added to the handbook. URL: https://cgit.freebsd.org/doc/commit/?id=8f4754a9a6ee8f2503cfb68d14afa99b17729e7f • bhyve documentation was improved. URL: https://cgit.freebsd.org/doc/commit/?id=68cbd16c4e7c199cfdfb2b54110ad1470b4d7a2e 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 Q2 2024 Status • 17 team languages • 214 registered users 9 new translators joined Weblate: • BFR (de_DE) • Elwood (de_DE) • Freebsd-Freund (de_DE) • MSantos (pt) • SINF-KEN (fr_FR, nl_NL) • aperechnev (ru) • edsonwolf • fdecunta (es_ES) • wheatfox (zh_CN, zh_HANS) Languages • Chinese (Simplified) (zh-cn) (progress: 7%) • Chinese (Traditional) (zh-tw) (progress: 3%) • Dutch (nl) (progress: 1%) • French (fr) (progress: 1%) • German (de) (progress: 1%) • Greek (el) (progress: 1%) • Indonesian (id) (progress: 1%) • Italian (it) (progress: 5%) • Korean (ko) (progress: 32%) • Norwegian (nb-no) (progress: 1%) • Persian (fa-ir) (progress: 3%) • Polish (progress: 2%) • Portuguese (progress: 0%) • Portuguese (pt-br) (progress: 22%) • Spanish (es) (progress: 36%) • Turkish (tr) (progress: 2%) We want to thank everyone that contributed, translating or reviewing documents. And please, help promote this effort on your local user group, we always need more volunteers. Packages maintained by DocEng During this quarter the following work was done in packages maintained by doceng@: • textproc/docproj-legacy: Fix build with DBLATEX • textproc/docproj-legacy: Fix poudriere warning • textproc/rubygem-asciidoctor-epub3: Add missing run dependency • www/gohugo: Update to 0.125.4 Open issues There are 3 Open PRs in bugzilla assigned to doceng@: • 279815 status reports: ERR_TOO_MANY_REDIRECTS • 276923 www/gohugo link error under poudriere • 267274 Please remove the zh-CN Handbook of the current FreeBSD website During this quarter doceng@ closed 3 PRs: • 278904 misc/freebsd-doc-en: HTML should be single page • 278732 www/gohugo: Update to v125.5 • 278504 textproc/rubygem-asciidoctor-epub3: A run-time dependency is missing for rubygem-asciidoctor-epub3 port ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. 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 Upstream has released GCC 14.1. Therefore port lang/gcc-14 has been created, as well as lang/gcc15-devel which tracks the new latest development GCC version. Previous major versions of GCC are being updated as well. Only very little work has been done on existing bugs for GCC ports this quarter, contrary to the original plan stated in the precedent report. This is due to the fact that I noticed an increasing interest in upstream to support GCC on FreeBSD, which however gets blocked by the fact that GCC sources do not build out-of-the-box on our platform, but needs instead many patches which are in our ports tree framework. It is then necessary to focus on upstreaming all of those patches, possibly at once and not one at the time as it has been done until now, and to also regularly run the tests suite, fixing all tests that fail. Then I am working on a new setup of automation that allows me to build and test all supported GCC versions as efficiently as possible, including GCC from sources but without the ports tree framework support. All of this has significantly slowed down usual GCC ports maintainership (users of the -devel ports have probably noticed that they are being updated much less frequently), but I am confident that it will eventually pay off. It should also be noted that Robert Clausecker has enabled lang/gcc11, lang/ gcc12, and lang/gcc13 for riscv64 architecture as the ports build fine on 15-CURRENT. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ KDE on FreeBSD Links: KDE/FreeBSD initiative URL: https://freebsd.kde.org/ FreeBSD — KDE Community Wiki URL: https://community.kde.org/FreeBSD Contact: Adriaan de Groot The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. The KDE team is part of desktop@, building the software stack to make FreeBSD beautiful and usable as a daily driver graphical desktop workstation. We missed a quarter, while the broader KDE community celebrated the KDE Megarelease of KDE Frameworks 6, KDE Plasma 6 and KDE Gear. The latest software is still not available on FreeBSD, pending more testing and some integration work. Infrastructure CMake was updated several times and is now version 3.29.6, the latest upstream release. CMake in the ports framework now supports setting parallel-build for tests. Qt5 is now on long-term support and updates only rarely. An update to 5.15.14 and WebEngine to 5.15.17 was landed in May. Qt6 and the Python bindings for Qt, Pyside, were updated to version 6.7.2. KDE Stack KDE Gear, Plasma and Frameworks release happen very regularly. These updates arrive in the FreeBSD ports tree only piecemeal, due to lagging work on compatibility and testing. • KDE Frameworks reached version 6.3.0 • KDE Plasma 6 Desktop was updated to version 6.0.4 • KDE Gear 6 has not yet arrived in the ports tree Related Ports The KDE ecosystem includes a wide range of ports — most maintained by kde@, all building on a shared base of Qt and KDE Frameworks. The KDE team updates them all as needed. This quarter the KDE team would like to thank Tobias C. Berner, Gleb Popov and Jason E. Hale again for keeping things up-to-date. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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. Notable changes in 2024 include: • adding OTP27, the latest Erlang runtime release, Elixir 1.17, and Gleam 1.20 • more than 57 point release updates so far in 2024 • improved inline documentation within Erlang ports • moved RabbitMQ port to the generic UNIX build, decoupling this from Elixir as a build-time dependency. This enables moving RabbitMQ to the latest supported release. Users of RabbitMQ need to update each quarter to avoid being stuck on an unsupported release of Erlang/OTP + RabbitMQ 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. During 2024Q3, the Erlang team is planning to: • migrate the base lang/erlang port to OTP26 and update related dependencies 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. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 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. 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 were no new Pot releases. Potluck images saw some updates again though. All images have been rebuilt for the new quarterly packages, a new Opensearch container has been added. Additional features, updates and fixes have been committed to containers like PostgreSQL-Patroni or Nomad-Server-TLS. In total, there are 58 container images and templates available now. As always, feedback and patches are welcome. Sponsors: Nikulipe UAB, Honeyguide Group From nobody Thu Aug 22 09:53:22 2024 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 4WqJS230pZz5SYhN for ; Thu, 22 Aug 2024 09:53:38 +0000 (UTC) (envelope-from matpockuh@gmail.com) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WqJS0662Tz4HQk for ; Thu, 22 Aug 2024 09:53:36 +0000 (UTC) (envelope-from matpockuh@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=f8DiG54y; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of matpockuh@gmail.com designates 2a00:1450:4864:20::52f as permitted sender) smtp.mailfrom=matpockuh@gmail.com Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-5becfd14353so800233a12.1 for ; Thu, 22 Aug 2024 02:53:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724320415; x=1724925215; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=y2GSgIfNlkBFu4D9HaQxh4WCk13eFUqYJ+Ic7loibDU=; b=f8DiG54yE63BlaR3CnedHY3SPaMF5Hrc6QvgMoZ9OQKruaNlon7KOyBwG5FUoJ8xsk 7+011mCDrCwiwydX4sFzrwTbnRQgvneA+75OzEdMUH+tX8T+dv5fvEn7NYf8OJZ4APSZ DdiQgyIR+hsQfa+UFY6j0pQgJXC5tBhXxnezdzS74K7ktigOOYHULvkSGazoQ4o7HYKB sAzBK6+xinTDRjU64pPESqz51VtZ04+0ZQhF/f6fbHHAK3YhXxwRL9anC/g868YH5mL9 mouKZ/Dh6kSoN+YjGmEvfT5aVmvOUJbni0iQRKmXOQ/fbPAqzZSjoMN36xN8bbs8RKe0 Gdaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724320415; x=1724925215; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=y2GSgIfNlkBFu4D9HaQxh4WCk13eFUqYJ+Ic7loibDU=; b=TH0pTklZvTSDDKsgcONw/va6FB9GOJttioPX6vM0DiDJaXS/fHHo64jr7HqibumiOw N8wmep9DPG0d9QlZQnEozsxdKeD7nxtYcnusvD9MMoS4pLuCVVnrzfcoWqpmmYkW2FAw YEkzd/xF5cJbr+nTk5CZeVKDyMQf2kvJS3hR4GikbkQ0rM77Hgm2jgSP/XPuc+8iq4xo DpaLDiZW4uEKisp4uXUJ7rlwCeUORwQDHcN7i8fUOixofhaB5bODA15JRx4VXp79S0Zh bL+8/PYDKvLRRn5NWqSaJVPu4I4fqItfNV6sWr6lm526n8a/OItyT0K12yNTQYO2/Y0y +T3Q== X-Gm-Message-State: AOJu0YzTz83uf04aolJ1lqmT8xToi7+byrlvTrtEhx7UEC9lnjwTfsFo 2EJDJZBFHERacbIuMKGO2UntAaFe1P795YZIElkQLw15dfHd81vjnZmJ7bfEAnQjhKBqqrENtqJ L+Jn6vLAOTWldRL1HmVyuTCflT9m0K0am X-Google-Smtp-Source: AGHT+IHjhRGJ+KOnPyy29Qt9/IGmoxQNxriAp0Is3ZzjcjZOQL3GiaeFUcTzBGrQ52InPwUKWZ3x4RVI6E+WDXPRqNw= X-Received: by 2002:a05:6402:5518:b0:5bf:afe:6294 with SMTP id 4fb4d7f45d1cf-5c07920a97emr731620a12.17.1724320414433; Thu, 22 Aug 2024 02:53:34 -0700 (PDT) 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 From: KOT MATPOCKuH Date: Thu, 22 Aug 2024 12:53:22 +0300 Message-ID: Subject: uart device lost after upgrading 14.1 d56a912f2 to b99852587 To: freebsd-stable List Content-Type: multipart/alternative; boundary="000000000000c80cd8062042a153" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.91 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.91)[-0.914]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52f:from] X-Rspamd-Queue-Id: 4WqJS0662Tz4HQk --000000000000c80cd8062042a153 Content-Type: text/plain; charset="UTF-8" Hello all! After upgrading FreeBSD 14.1 from d56a912f2 to b99852587 system lost uart device on my SunFire X2270 system. Entries from dmesg.boot file BEFORE update: uart0: at port 0x3f8 irq 4 flags 0x1 0 on isa0 uart0: console (9600,n,8,1) What happened? How can I return my serial console to working state? On the updated system I do not have these entries, also I have NO ttyu0 devices that were used as console. I'm using stable/14 git's branch. There were no changes in the kernel configuration file. I do not have this problem on other systems, including different Sun's servers, but this servers using different chipset. For example log entries from SunFire X4200: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ns8250: UART FCR is broken uart0: console (9600,n,8,1) -- MATPOCKuH --000000000000c80cd8062042a153 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello all!

After upgrading FreeBSD = 14.1 from d56a912f2 to b99852587 system lost uart device on my SunFire X227= 0 system.
Entries from dmesg.boot file BEFORE update:
uart0: <Non-standard ns8250 class UART with FIFOs> at port 0x3= f8 irq 4 flags 0x1
0 on isa0
uart0: console (9600,n,8,1)

What happened? How can I return my serial console to = working state?

On the updated system I do not = have these entries, also I have NO ttyu0 devices that were used as console.=
I'm using stable/14 git's branch.
There were n= o changes in the kernel configuration file.
I do not have this pr= oblem on other systems, including different Sun's servers, but this ser= vers using different chipset. For example log entries from SunFire X4200:
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flag= s 0x10 on acpi0
ns8250: UART FCR is broken
uart0: console (9600,n,8,1= )

--
MATPOCKuH
--000000000000c80cd8062042a153-- From nobody Thu Aug 22 10:14:34 2024 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 4WqJwL5Y1xz5SbZ5 for ; Thu, 22 Aug 2024 10:14:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4WqJwL1nkkz4Kqp for ; Thu, 22 Aug 2024 10:14:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.18.1/8.18.1) with ESMTP id 47MAEYLQ040919; Thu, 22 Aug 2024 13:14:37 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 47MAEYLQ040919 Received: (from kostik@localhost) by tom.home (8.18.1/8.18.1/Submit) id 47MAEYVv040918; Thu, 22 Aug 2024 13:14:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 22 Aug 2024 13:14:34 +0300 From: Konstantin Belousov To: KOT MATPOCKuH Cc: freebsd-stable List Subject: Re: uart device lost after upgrading 14.1 d56a912f2 to b99852587 Message-ID: References: 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=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on tom.home X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4WqJwL1nkkz4Kqp On Thu, Aug 22, 2024 at 12:53:22PM +0300, KOT MATPOCKuH wrote: > Hello all! > > After upgrading FreeBSD 14.1 from d56a912f2 to b99852587 system lost uart > device on my SunFire X2270 system. > Entries from dmesg.boot file BEFORE update: > uart0: at port 0x3f8 irq 4 > flags 0x1 > 0 on isa0 > uart0: console (9600,n,8,1) > > What happened? How can I return my serial console to working state? > > On the updated system I do not have these entries, also I have NO ttyu0 > devices that were used as console. > I'm using stable/14 git's branch. > There were no changes in the kernel configuration file. > I do not have this problem on other systems, including different Sun's > servers, but this servers using different chipset. For example log entries > from SunFire X4200: > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > ns8250: UART FCR is broken > uart0: console (9600,n,8,1) Compare /boot/device.hints on 14.0 vs. 14.1. I remember the isa hints for the uarts were removed. If not enumerated by acpi, as in case of X4200, the hints needs to be provided. From nobody Thu Aug 22 11:45:53 2024 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 4WqLxZ6FFsz5Slc7 for ; Thu, 22 Aug 2024 11:45:54 +0000 (UTC) (envelope-from SRS0=s+K5=PV=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4WqLxZ51kVz4Wkh for ; Thu, 22 Aug 2024 11:45:54 +0000 (UTC) (envelope-from SRS0=s+K5=PV=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Thu, 22 Aug 2024 13:45:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1724327153; 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: in-reply-to:in-reply-to; bh=q1/4ckgGENJLQrPhTosudNl3ig4PCmLCJx7r9kYpxi8=; b=CaI+6+iRjhlJQE4a52Bj+fQIAYPqibJP8jVA7mnB5NBUC+vpptoo/MZZdne2YmL/hoF+8P pS8YtBNg4SxWYc2b2XJxC9jmtUSjt70BCPnol5VLFA6wQDI5BLVelazqrkTQo7wX3WP63t 1lEInBe0IlfxXD2rDhP13g4LlkelQr8epeaVQZ8CzUmWgrvxWFPrmq+IcDTXp78lresTNP RhTGUnkyKFvq6e86D121GSs25ItYr5otJqx2n9JrpoSrHnZU5jklOEHoQYHJ5PLKZ2nt/Q aYWP4Dx+g5MeT8jVsV6Te6e3KDBy8KsFoWTlVJBySHIgfQNYQNFNH/hQk2J3qA== From: Ronald Klop To: Konstantin Belousov Cc: KOT MATPOCKuH , freebsd-stable List Message-ID: <1510003604.3724.1724327153577@localhost> In-Reply-To: Subject: Re: uart device lost after upgrading 14.1 d56a912f2 to b99852587 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: multipart/alternative; boundary="----=_Part_3723_1909895283.1724327153573" X-Mailer: Realworks (717.34) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[K5=PV=klop.ws=ronald-lists]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4WqLxZ51kVz4Wkh ------=_Part_3723_1909895283.1724327153573 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Konstantin Belousov Datum: 22 augustus 2024 12:14 Aan: KOT MATPOCKuH CC: freebsd-stable List Onderwerp: Re: uart device lost after upgrading 14.1 d56a912f2 to b99852587 > > > On Thu, Aug 22, 2024 at 12:53:22PM +0300, KOT MATPOCKuH wrote: > > Hello all! > > > > After upgrading FreeBSD 14.1 from d56a912f2 to b99852587 system lost uart > > device on my SunFire X2270 system. > > Entries from dmesg.boot file BEFORE update: > > uart0: at port 0x3f8 irq 4 > > flags 0x1 > > 0 on isa0 > > uart0: console (9600,n,8,1) > > > > What happened? How can I return my serial console to working state? > > > > On the updated system I do not have these entries, also I have NO ttyu0 > > devices that were used as console. > > I'm using stable/14 git's branch. > > There were no changes in the kernel configuration file. > > I do not have this problem on other systems, including different Sun's > > servers, but this servers using different chipset. For example log entries > > from SunFire X4200: > > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > > ns8250: UART FCR is broken > > uart0: console (9600,n,8,1) > Compare /boot/device.hints on 14.0 vs. 14.1. I remember the isa hints for > the uarts were removed. If not enumerated by acpi, as in case of X4200, > the hints needs to be provided. > > > > > See https://cgit.freebsd.org/src/commit/?h=stable/14&id=74b9fc7adcf4afb1c3039267e338c3cfdf022957 Regards, Ronald ------=_Part_3723_1909895283.1724327153573 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: Konstantin Belousov <kostikbel@gmail.com>
Datum: 22 augustus 2024 12:14
Aan: KOT MATPOCKuH <matpockuh@gmail.com>
CC: freebsd-stable List <freebsd-stable@freebsd.org>
Onderwerp: Re: uart device lost after upgrading 14.1 d56a912f2 to b99852587

On Thu, Aug 22, 2024 at 12:53:22PM +0300, KOT MATPOCKuH wrote:
> Hello all!
>
> After upgrading FreeBSD 14.1 from d56a912f2 to b99852587 system lost uart
> device on my SunFire X2270 system.
> Entries from dmesg.boot file BEFORE update:
> uart0: at port 0x3f8 irq 4
> flags 0x1
> 0 on isa0
> uart0: console (9600,n,8,1)
>
> What happened? How can I return my serial console to working state?
>
> On the updated system I do not have these entries, also I have NO ttyu0
> devices that were used as console.
> I'm using stable/14 git's branch.
> There were no changes in the kernel configuration file.
> I do not have this problem on other systems, including different Sun's
> servers, but this servers using different chipset. For example log entries
> from SunFire X4200:
> uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
> ns8250: UART FCR is broken
> uart0: console (9600,n,8,1)
Compare /boot/device.hints on 14.0 vs. 14.1.  I remember the isa hints for
the uarts were removed.  If not enumerated by acpi, as in case of X4200,
the hints needs to be provided.


See 
https://cgit.freebsd.org/src/commit/?h=stable/14&id=74b9fc7adcf4afb1c3039267e338c3cfdf022957


Regards,
Ronald
------=_Part_3723_1909895283.1724327153573-- From nobody Fri Aug 23 02:49:52 2024 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 4Wql0s0sBmz5V6kR for ; Fri, 23 Aug 2024 02:50:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wql0r40MZz54LB for ; Fri, 23 Aug 2024 02:50:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-7b8884631c4so661157a12.2 for ; Thu, 22 Aug 2024 19:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1724381403; x=1724986203; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GO7GO7A/eGaCccdh5VODheZVT7vNjF9ZLOt2JwrlCUo=; b=Y3bVmBwyJrAbkYVQFe43LwccQ8rjpWW3ns1/nIuzjRirznvGTTu3aTLfyAtQh2u/G5 4EVdz02p1lvyHHpKEOwyEb2ySCbrOqRri5O+EMItrHBtvQkj4xCnXzZgflOEnYMzcVCw 0alkkBfVEUYS5fxX+KpDPwzJDn4Lf/GaMx1IgNu1O88HC/e7v9wT1aNRxDQ0+P4bjd08 rn21N18/8nbFZ4EXt7eBg76nJZCjL1jKOBnVPwxQ8f4nsAeMkIhSSxQxV7/bmFZ+OPpN foUgO4extYR/sXxYYDx0o7MMHuJGsMm1z/MZrnaZ/df37LYgSD2NOZpatASRUOvM8mNa CdaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724381403; x=1724986203; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GO7GO7A/eGaCccdh5VODheZVT7vNjF9ZLOt2JwrlCUo=; b=u9BzdlTFya3Owr5OXaduzrq477xjS+z1TO3LvyoWGdEByd/WWehe6bb4kJhKKqaVDt Vr3VzsKtsiaGPPoLvM/d1nQhyIoyozshaO7G8aCGOZRuHqB5H7mmen+qMBFpJD8edtpj S0891PjMODtNFDwanPWW1RAbt0mLeCz69DiWbvD0qmAa55O66R6TPW1xGYP6t/Eyp5ur gzzT9rSrpt21WWFNTewg4L13KlypHYEP8m/mCLJcPFjOCK9Zd/74ch6NWL2/LcmGKb8T qxciDeW9txcoFZYlgNELxivFRoO8hKa2fc6xeMi+C2GOuEuG3C0ML/combgEJcWXrHov ddoA== X-Gm-Message-State: AOJu0Yycd1utyARRQHtkLfcWvSeYS79JLCl6RsY+TM6e07AXOHvQjpyP ooKhWEY4ts1UAAnBIFZRvvlF0bQylhCTR0TJTLJB/jf2Ak4XrEwmhEGxsdSCr/D83ExPMhO6Fdz klRsA/kbMzyL7dS1j2SaVnMvL8nfc5XKZQH/0OBj3evkoHTFU X-Google-Smtp-Source: AGHT+IGppM78YRf768E/eCE52qkBIevd/qCQuAFyqrhoyZjdq13nTuoqnOrE3ufpbN/yyo3kv7FItF9R8gQ2HGBcQKw= X-Received: by 2002:a17:90a:9314:b0:2c8:ac1:d8c3 with SMTP id 98e67ed59e1d1-2d646d4bb42mr753105a91.29.1724381403251; Thu, 22 Aug 2024 19:50:03 -0700 (PDT) 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 References: In-Reply-To: From: Warner Losh Date: Thu, 22 Aug 2024 20:49:52 -0600 Message-ID: Subject: Re: uart device lost after upgrading 14.1 d56a912f2 to b99852587 To: KOT MATPOCKuH Cc: freebsd-stable List Content-Type: multipart/alternative; boundary="000000000000ffa1ea062050d4e0" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Wql0r40MZz54LB --000000000000ffa1ea062050d4e0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 22, 2024 at 3:54=E2=80=AFAM KOT MATPOCKuH = wrote: > Hello all! > > After upgrading FreeBSD 14.1 from d56a912f2 to b99852587 system lost uart > device on my SunFire X2270 system. > Entries from dmesg.boot file BEFORE update: > uart0: at port 0x3f8 irq 4 > flags 0x1 > 0 on isa0 > uart0: console (9600,n,8,1) > > What happened? How can I return my serial console to working state? > I believe that kib@ is correct. on isa0 is a good hint that we're attaching with the old hints. I think we should add an entry about this to the release notes for the next 14.x release. > On the updated system I do not have these entries, also I have NO ttyu0 > devices that were used as console. > I'm using stable/14 git's branch. > There were no changes in the kernel configuration file. > I do not have this problem on other systems, including different Sun's > servers, but this servers using different chipset. For example log entrie= s > from SunFire X4200: > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > ns8250: UART FCR is broken > uart0: console (9600,n,8,1) > Yea, ACPI on the newer system has these uarts listed. On the other systems not so much. The X2270 was released 2009 or 2010, which is new enough I'd expect it to have ACPI and have the serial ports in its AML.... Warner --000000000000ffa1ea062050d4e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Aug 22, 2024 at 3:54=E2=80=AF= AM KOT MATPOCKuH <matpockuh@gmail= .com> wrote:
Hello all!

After upgrading Free= BSD 14.1 from d56a912f2 to b99852587 system lost uart device on my SunFire = X2270 system.
Entries from dmesg.boot file BEFORE update:
=
uart0: <Non-standard ns8250 class UART with FIFOs> at port= 0x3f8 irq 4 flags 0x1
0 on isa0
uart0: console (9600,n,8,1)

What happened? How can I return my serial console= to working state?

I beli= eve that kib@ is correct. on isa0 is a good hint that we're attaching w= ith the old hints.

I think we should add an entry = about this to the release notes for the next 14.x release.
=C2=A0=
On the updated system I do not have these entries, also I have NO t= tyu0 devices that were used as console.
I'm using stable/14 g= it's branch.
There were no changes in the kernel configuratio= n file.
I do not have this problem on other systems, including di= fferent Sun's servers, but this servers using different chipset. For ex= ample log entries from SunFire X4200:
uart0: <16550 or com= patible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
ns8250: UART FCR = is broken
uart0: console (9600,n,8,1)

Yea, ACPI on the newer system has these uarts listed. On th= e other systems not so much.

The=C2=A0X2270 was=C2= =A0released 2009 or 2010, which is new enough I'd expect it to have ACP= I and have the serial ports in its AML....

Warner<= /div>
--000000000000ffa1ea062050d4e0-- From nobody Sat Aug 24 06:29:26 2024 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 4WrRqV54bvz5VFn2; Sat, 24 Aug 2024 06:29:26 +0000 (UTC) (envelope-from cperciva@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 4WrRqV4S2tz4TgB; Sat, 24 Aug 2024 06:29:26 +0000 (UTC) (envelope-from cperciva@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724480966; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc; bh=tI3xR3gXp6WS+d7sMmVhzbNBmdcXNfUkCueHCVy5z8s=; b=kiabvaL/farcJbA2STcIjlykai+LQSyPccP7hUOKQ2hdrz9qA+GSKSviBQucKw7/UhlkGA skU3qzI8J0NgdToNl3k2CjIEuvOLs65wFILs5/YNdvleF4qYVInJX+9CA1Hi3dflTyaRrb pAGL5jZB0AOAVmOkeTvv8gnUTAXbqp//PsmlHdTLS6H79d0KNQyXVroISr6olGITzDgOcn 6VY0RKY4hcurTAIIp0703KJqsFPnyCnPshZv977Q4oSeoEhQYV8gK4p4JUJwn6nE5tA++4 PmK+l64/EbGB+H98d4OSw7Dk3TeH1bDyMQ1Yz8iYuCZLL2MTO/hcdSYHM9UPhg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724480966; a=rsa-sha256; cv=none; b=Y+mLtvYEareawDwiOKSokFohX+8COB1EMa8dtlhhHgmiG5EjNwUkpmkZdXtpE/Zg2kclL+ nELdHjjLDXM+qKJc+ctpKmT5JQEvO/SnCaDDtM6A5iccpox3/Qd7rY1ui5bs603ZeOMyYQ WcB3jSmO9bfeypSP4gtCeUyuH2s5vIw9xmxofL5ibDPvachoSVYaqcDRYhPO7jFiEgn2p9 1z6/NI41IZnZiYI2RDz6EeQ5f3ngxkCIW5NlXxvZ03lonIlH2X4v/6Yx1xb6yT3sdTYqJD MRMsopBYkXMZexLFLx969YIU6IBllF5QA9YREHhZM0hHpi4MLR80roRgZ99hwA== 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=1724480966; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc; bh=tI3xR3gXp6WS+d7sMmVhzbNBmdcXNfUkCueHCVy5z8s=; b=pWhkK98vzyNWrBG6vvsz7XrAqtQGuLAM2Vm3+3RUtzBhvI6avHjCC2PSpaxmf36zD9f6Pf irZe6QA7a5h4cwv4utHbtfHUgl5I9aKZrTXcvn0sn4XSa0ctQP3T58obMzxwU2aq114X6U q3TxGqxXPJUJDeh+VcznkZEWcDKs3hDL8+EgKercf6cVI2Or9JUq453zNXxitOdnSmT5gF W3YfAOdJRHuwOlRtqFw1ZBDgAgKO167/VKbFwkV8/l8WuRlwQrAqKKyWEuozjJ3h2QmG20 w2wVRo4iS4QU11c03hB4bYf2Pic4793FldpqUUq/g4iZ3esUXyP4oOJRen1MHg== Received: by freefall.freebsd.org (Postfix, from userid 1002) id 81FEA4EA2; Sat, 24 Aug 2024 06:29:26 +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.4-RC1 Now Available Message-Id: <20240824062926.81FEA4EA2@freefall.freebsd.org> Date: Sat, 24 Aug 2024 06:29:26 +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 RC build of the 13.4-RELEASE release cycle is now available. Installation images are available for: o 13.4-RC1 amd64 GENERIC o 13.4-RC1 i386 GENERIC o 13.4-RC1 powerpc GENERIC o 13.4-RC1 powerpc64 GENERIC64 o 13.4-RC1 powerpc64le GENERIC64LE o 13.4-RC1 powerpcspe MPC85XXSPE o 13.4-RC1 armv6 RPI-B o 13.4-RC1 armv7 GENERICSD o 13.4-RC1 aarch64 GENERIC o 13.4-RC1 aarch64 RPI o 13.4-RC1 aarch64 PINE64 o 13.4-RC1 aarch64 PINE64-LTS o 13.4-RC1 aarch64 PINEBOOK o 13.4-RC1 aarch64 ROCK64 o 13.4-RC1 aarch64 ROCKPRO64 o 13.4-RC1 riscv64 GENERIC o 13.4-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.4/ 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.4" branch. A summary of changes since BETA3 includes: o Bug fixes to ICMP handling in pf. o Fixing a crash in "tail -F". o Fixes to per-user ZFS dataset handling in adduser o DVD images have been updated to include a set of packages likely to be more useful on modern systems. A list of changes since 13.3 is available in the releng/13.4 release notes: https://www.freebsd.org/releases/13.4R/relnotes/ Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 13.4-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.4-RC1/ BASIC-CI images can be found at: https://download.freebsd.org/releases/CI-IMAGES/13.4-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.4/RC1 FreeBSD/aarch64 EC2 AMI IDs can be retrieved using the keys /aws/service/freebsd/arm64/base/ufs/13.4/RC1 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-13.4-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.4-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.4-RC1 amd64 GENERIC: SHA512 (FreeBSD-13.4-RC1-amd64-bootonly.iso) = be3a841ab8adc1d7ed67d2feeb171be569cbe4299ee72fc53031d79034a100fc650e57736d7ac07ec5b484f1da7f3a5a2bc65929e2460043503fa95ac0aee208 SHA512 (FreeBSD-13.4-RC1-amd64-bootonly.iso.xz) = 20ecb3dd6337c9de9d00a863cc3e37ef6ac21c646e45e7de1fe84366c3fc30e3eb7cd666297919609eaf332ad1a8c9653d52a04314513d530e869e4cc0b54af1 SHA512 (FreeBSD-13.4-RC1-amd64-disc1.iso) = dec8289aa551dac10c3c407aacddd1b470fb7e0cfcff9df81981e98597b714f81ec00ab0e5b75b12bb74296ee6cf2e5dfb5aefabd16d838e84a2211931e42c16 SHA512 (FreeBSD-13.4-RC1-amd64-disc1.iso.xz) = 889f02c147f16f3ada5c3a0bc5ccee1470c75ec1d95219b9b758aa5fb957f15b1bb803311afbea002b41dc7e0bee06bfbd0cff09201cb714549ca30e66571976 SHA512 (FreeBSD-13.4-RC1-amd64-dvd1.iso) = 1e3e85f28a20ea1def64cb3a814a488676ef492c64120a69c11b64136a7d11f2493fda22036452872a78a7452748905b658486f1a34adb11b8d64c878d038866 SHA512 (FreeBSD-13.4-RC1-amd64-dvd1.iso.xz) = 4c72fbf9f7f3a1e11a562ad528c391fe532a28ce4d9d2b88e68c7248b98d1440265adc7618837e0a6f5dc3d43a21e2e5103666e98fe815fb78dfd6b2ffe126f1 SHA512 (FreeBSD-13.4-RC1-amd64-memstick.img) = a10da1fb3cc0f8f2d171cb464c877e12dec77b97e69e447416eecd0265f9350bc20b8719047ae0ce7a1c7a97b799e3c8828af55d7fce3569f3af2d1540bf9d3d SHA512 (FreeBSD-13.4-RC1-amd64-memstick.img.xz) = 64d205923a113ba97f5bd8ab18cb9f0f76a7b58f691b5c504ec14c6214e4ad2bc246e9b9584e0e158b2ebb9b0b72c8d71a7fd16699e65dce1007cd0d5feac5ff SHA512 (FreeBSD-13.4-RC1-amd64-mini-memstick.img) = 3856d745b543a975c4f88fb86a13f14020f9d94b8c40fab846acba1c42d2a77379a569a95adfeffd4e483a3c3703d900103c0cf32228f858a6edc83b3e152f7b SHA512 (FreeBSD-13.4-RC1-amd64-mini-memstick.img.xz) = 3ac0ec4cf866581d421787cc284b1ce57c23d922767ae15f640f68833da3818b65081921d16ada1125098c7ff1fdaa84ac014f2cc12cfba746b846b002b22c43 SHA256 (FreeBSD-13.4-RC1-amd64-bootonly.iso) = c4b49572b99f98f4333ddaf2c4e7609ce3d91e3ff2180ac1c65852c731d23fb6 SHA256 (FreeBSD-13.4-RC1-amd64-bootonly.iso.xz) = 753336c103884fee0cce686ee4002252dd254fd6a1c4270f3a4d457695cd0560 SHA256 (FreeBSD-13.4-RC1-amd64-disc1.iso) = f45fe76cb36b4314938a2cb9b02108e3722442bf1de98d8040a5b9812f64f284 SHA256 (FreeBSD-13.4-RC1-amd64-disc1.iso.xz) = 0274710857abe56d34a4ac41098819a6516077d4acdd91066ab57ca99906b5e9 SHA256 (FreeBSD-13.4-RC1-amd64-dvd1.iso) = 6d87d2c55cec8146e0f5047e31bc50ee5e88713bca87963bda963c8e8155f12e SHA256 (FreeBSD-13.4-RC1-amd64-dvd1.iso.xz) = d193d112a05979700d5a16405ff3ccfba9b22f0683c542b2fc0575f66a584afc SHA256 (FreeBSD-13.4-RC1-amd64-memstick.img) = a8ccea24f5c5151a28b1141ffc822db27cc4c2a2aa3b0984a359db9a0363c3a2 SHA256 (FreeBSD-13.4-RC1-amd64-memstick.img.xz) = e857bdf497373f23eae6da12a178711f788558cbf5020ce44ac89e1ff41d411d SHA256 (FreeBSD-13.4-RC1-amd64-mini-memstick.img) = 6fc6016b492b6d4fea24221bbd4cc05020dd624d36ffc41b141443dbe71da8d5 SHA256 (FreeBSD-13.4-RC1-amd64-mini-memstick.img.xz) = 7ff08582d1f1630fc51f08f8a9f199273f42e53cb2e6d44b6585a4127e9770b2 o 13.4-RC1 i386 GENERIC: SHA512 (FreeBSD-13.4-RC1-i386-bootonly.iso) = b3e718563a8892f7e10b93386749f06f6a82b118387c555cd683ba5b14be6fbdf706b4836ac30edef57403eaa14a3fdb900810df01041fba8125e9d8ede4c55b SHA512 (FreeBSD-13.4-RC1-i386-bootonly.iso.xz) = e61de73a85c9dd63a58f33cbe15b0a7d2e0241bd0c2366c0395c6916cb3f8e5f781b201522397ec933c09333f6130f1834ac9e12920c40d01ff4c91274ad3008 SHA512 (FreeBSD-13.4-RC1-i386-disc1.iso) = 2aba6ded0f8dc702683ee639dab8444c51d2f2a6662680208ec1fa28eb4d6cb85df3984f2b1024f207963d9e2eeaf7bfe04bf97b4b04a8c061c957d1b0cf8078 SHA512 (FreeBSD-13.4-RC1-i386-disc1.iso.xz) = 99f2d686bc69e9494072478a81c27d348c41f79e0d264a4914e419bc855c086ad36799a759c48170dd01238464589c0e1a80440000da7e0e6d2e4df8168d8725 SHA512 (FreeBSD-13.4-RC1-i386-dvd1.iso) = 284666e7db317bb6174e21de9597e0e772d36fd0fdb84a39b89cc25e41de7c7e0ccf6b5de75251ee84a34a9f7210ef03cec533c93b169beee5127ec407cfce07 SHA512 (FreeBSD-13.4-RC1-i386-dvd1.iso.xz) = 746554b8451b59a095d29a1b0b7085dad9f9dab08897b7f0930b2f422d0ee542104a1efc05228921519ee3ef4c0c7c1151e44d7f180e8598829f65517265db4f SHA512 (FreeBSD-13.4-RC1-i386-memstick.img) = f5e1b75dd900d17d9c865c1fcc5407816140934d5579cbdd1c0dab5ddcc3a2d68498bd72b02cf302b571f9f1d0aed81c5e6002cafca479dc33fe18e8dc7ff5a4 SHA512 (FreeBSD-13.4-RC1-i386-memstick.img.xz) = 37a85fbafd25604a6ca2ce4a14a232c211d54517527153e65198a6da3a70838799b5ee05dec1e0f6b11eceb10b0d51db2f6dabf43dd86a030cbe5c15afee492c SHA512 (FreeBSD-13.4-RC1-i386-mini-memstick.img) = 8ee547ddbc4073f9bca3eef34f2dc856e2c0b6367724a3778f2b724360f8c202e158402a1d4eb9cd12cf9d663847d09940a89ee5673b0347489e0a4237981d6d SHA512 (FreeBSD-13.4-RC1-i386-mini-memstick.img.xz) = 222ddaf3f93f3219780da74a30bcfb907f0586f9e9f2850d1bcaa84da4bd207371f4d1adb9b3ed3b932fe1b66b61826f7a540894a88fd7d95a727503f0a4459c SHA256 (FreeBSD-13.4-RC1-i386-bootonly.iso) = 0f054cf393447b14408398d0bc85e601a41c7d16e264cc69f6dc309e407c1f99 SHA256 (FreeBSD-13.4-RC1-i386-bootonly.iso.xz) = 1b47922a700edd1e93fffda379346db73c6a302c1591899157db0b9437b430b7 SHA256 (FreeBSD-13.4-RC1-i386-disc1.iso) = 14d93b1065acb89c393318f05ce94342d4bacd34c3bc4a43b9ecaf15245c3432 SHA256 (FreeBSD-13.4-RC1-i386-disc1.iso.xz) = 019c663aae649fc756911a61a17764fbbb69c4f19f8254216518ff9d2a83069a SHA256 (FreeBSD-13.4-RC1-i386-dvd1.iso) = 4d008bda6362a94a1c5b7ce211bea67cdc7b551ebd12a9692725e7c53b0e8d41 SHA256 (FreeBSD-13.4-RC1-i386-dvd1.iso.xz) = a2f575b5cc75908851d910d5fdc5cc966a56f9f82d77f745743f28fdde10c4b5 SHA256 (FreeBSD-13.4-RC1-i386-memstick.img) = 3694f5c8c87efddfac89026fbe875f70c5635ae8be9d0edcb1d5337670c89e3b SHA256 (FreeBSD-13.4-RC1-i386-memstick.img.xz) = 57a878415e54ff6dfd665d3f7544d041a2c0f3c3ac11841160dc6da9c3df723f SHA256 (FreeBSD-13.4-RC1-i386-mini-memstick.img) = 488b263b1c27ff2fa93998998a0ad05c410d32efc98da8080635d34d44b9aea6 SHA256 (FreeBSD-13.4-RC1-i386-mini-memstick.img.xz) = a1d6ecd51c85962bd852264ae8819f05af1a510ee9ebb8336cf3d5dec76b76a7 o 13.4-RC1 powerpc GENERIC: SHA512 (FreeBSD-13.4-RC1-powerpc-bootonly.iso) = c9f56d1536714e9aa5e47a39ef998c7d5ed390f19c46d2b28c5eab519f410bdd5e8ea32d3ea4169435c3d8bbe9da54073c482dc559459f868d03b94c3c85da3f SHA512 (FreeBSD-13.4-RC1-powerpc-bootonly.iso.xz) = 999866a1563b294003467036a04faa056f76766938df48cb006a3db180977af7502dd0f4e94b729105f7099d46edde8e67f699b732956e80a0c8081f93a4f355 SHA512 (FreeBSD-13.4-RC1-powerpc-disc1.iso) = 5b80bd4201f44b3860a4662493493d7e99061fdc9430045e0276bd28f748451ac05f61fe07291d138f97e7466b03e141a09f30dc1245049358f35b901b2ebdcb SHA512 (FreeBSD-13.4-RC1-powerpc-disc1.iso.xz) = 35108fe6a11259fc03aa2ea9b063869d092adacbd90e631fffefb87027aa3cc8f1a09ffb4db63c4ba3a6cc91f8a42477fd66826ebe676aff1fcf423ffc8b11af SHA256 (FreeBSD-13.4-RC1-powerpc-bootonly.iso) = 656ce49d51328b9ec3e5df4328de417755a93acffe2ab62003ef8f6ff27fcc1c SHA256 (FreeBSD-13.4-RC1-powerpc-bootonly.iso.xz) = 0b37d2389a8abc7b5af6d705eba6f77e73ec9d7642e88fb22d5a0d1348fccc56 SHA256 (FreeBSD-13.4-RC1-powerpc-disc1.iso) = c4e542c198d03579faf2a4f32c70df824d86b3e17411e41b2507b0062970933c SHA256 (FreeBSD-13.4-RC1-powerpc-disc1.iso.xz) = 53dcf69b2e77bc3659f4b967c2b3ea199c905b325004ca6ac5be7c01ee5c7f31 o 13.4-RC1 powerpc64 GENERIC64: SHA512 (FreeBSD-13.4-RC1-powerpc-powerpc64-bootonly.iso) = dc672ba00bf39afda7ae21c13aa0f0edbf43780b96f36a534b97aafc188fdec6c7b7e606df52f66a776fdf355d63e20272b9382f030216726bdb5d9e6c77b558 SHA512 (FreeBSD-13.4-RC1-powerpc-powerpc64-bootonly.iso.xz) = 77cc298d658242fa8051e739565dde96d90e0425cf92996c5928c7f43893380aeb35b2bffc8faa807a7862fd8ee535c5adbfe3f1d8f34673ddccc14e99023a87 SHA512 (FreeBSD-13.4-RC1-powerpc-powerpc64-disc1.iso) = 01ada885dc328539c57682900ad248232bc489d6bd62ac725c4cb4ca6cdbbc0afd668194380c3c241c6e3454b67c6c9571b35035bd33617af94fadc763043a72 SHA512 (FreeBSD-13.4-RC1-powerpc-powerpc64-disc1.iso.xz) = 7fd0941bea901deac28322579ba4f82259935316ff7e5f7bf0106d374ca86e3f391108ab816a3f97209e1e895fc9da1ee2efb8b329647a9eb2f079a4ddd0e5b3 SHA256 (FreeBSD-13.4-RC1-powerpc-powerpc64-bootonly.iso) = 80247da17372effda229e32554b181c111a3ffa4a93053314c0187313fea9004 SHA256 (FreeBSD-13.4-RC1-powerpc-powerpc64-bootonly.iso.xz) = 93a2b3179e42358707cdd8b54e3abc032d70565c87285e3e3de2bb12a74fd1cd SHA256 (FreeBSD-13.4-RC1-powerpc-powerpc64-disc1.iso) = 34d4237fba4d60a621db49617d7d46c088621a0b6e087a051417bfb6bf759b9f SHA256 (FreeBSD-13.4-RC1-powerpc-powerpc64-disc1.iso.xz) = 6dd73fc5f1b59491732bb125f562dbd7d51e71afbd38c56dda9bcfc1275aea7a o 13.4-RC1 powerpc64le GENERIC64LE: SHA512 (FreeBSD-13.4-RC1-powerpc-powerpc64le-bootonly.iso) = dab0f7175bacb98b5a9020144401c4141a7188a32d23a8d8660ce1a43d53c5f62e5a27d97487ea1f9241ba4b4c5309079c42686b2f732af40e080b52aac7acec SHA512 (FreeBSD-13.4-RC1-powerpc-powerpc64le-bootonly.iso.xz) = e5e73eb6a5291fb821554670104270b76999c19a91f71e7ac9e1007775ca7028ca2fc45b2f5f7b0133f2e1f4e6b9c602c36d9826cf1283df742352cb395fa4ce SHA512 (FreeBSD-13.4-RC1-powerpc-powerpc64le-disc1.iso) = 679656bf52512ec8a1aeb9d580cd852cfdcff01db06cca628a35e8f432858acc8fd873862b746ebed577201badcc3e8490c9f5e397c6faa875749257650b2809 SHA512 (FreeBSD-13.4-RC1-powerpc-powerpc64le-disc1.iso.xz) = 91e602d86a7447c972be653b256d6949ae54cb5a8d547f209ad1d8b3bb2641ac110b4bb1477957d18761901ccec4b8f29e5c0c6f0b9d79c7e03efc1a9e26f888 SHA256 (FreeBSD-13.4-RC1-powerpc-powerpc64le-bootonly.iso) = 7cbb9b80da2da86785ea238d53c48f30e1c32e0b81164e8a1f6d249c1a67ac45 SHA256 (FreeBSD-13.4-RC1-powerpc-powerpc64le-bootonly.iso.xz) = 94baa88e11f7f6a9cfb44f88138fd535e5a0de06e531902c05e7c5664db0981f SHA256 (FreeBSD-13.4-RC1-powerpc-powerpc64le-disc1.iso) = c63510fca35e0ede1a1d00bea27b4e655708f41a841e0d8f958299f9a0f79514 SHA256 (FreeBSD-13.4-RC1-powerpc-powerpc64le-disc1.iso.xz) = cf29c30f1f2473a3d2d9fe930192d2a3437a464333202f84ae93ae2c139bc363 o 13.4-RC1 powerpcspe MPC85XXSPE: SHA512 (FreeBSD-13.4-RC1-powerpc-powerpcspe-bootonly.iso) = 28530d43dbaa48e21015b70b6cb80d7579545caaf6918c23e4f7bd990a4d448a169a12aaa3febbf76724ce1a265e817c048fc591e7aac62c029dac528fe51a30 SHA512 (FreeBSD-13.4-RC1-powerpc-powerpcspe-bootonly.iso.xz) = 7c5b39ce3250c8939b10fa6834f7c6f12b732d506bc47d7680570faca7d84bf17b99902895cbede3fb1264ddf5df62f987e9e451cf2c002ff1909ebd62c2c5cf SHA512 (FreeBSD-13.4-RC1-powerpc-powerpcspe-disc1.iso) = 2407f67e7d3460ebcca0360d4ffe9ed8820902b2d4b7455e90c0ece99499a6f94d304ddb742a81d89e0d5ffd4938e6c2888827afdb6cee64131084dc1cc79b78 SHA512 (FreeBSD-13.4-RC1-powerpc-powerpcspe-disc1.iso.xz) = 2c0e48fa12d34fd981579ed2bd7159373f5fd64cce1e5e6b0aaca20b83e4b310c201d6d73c3dc21a0fb8ee969ddb20584508e34a43e426572b926f4d28e8496f SHA256 (FreeBSD-13.4-RC1-powerpc-powerpcspe-bootonly.iso) = 0105ae779eaade069e23e948220ed6a299dd8edfc881232e47c2763cdd117f67 SHA256 (FreeBSD-13.4-RC1-powerpc-powerpcspe-bootonly.iso.xz) = e9a2616e1fc1fc238b5778bc1eb7116ce6b3425851d7f3371604863e4da2ddd8 SHA256 (FreeBSD-13.4-RC1-powerpc-powerpcspe-disc1.iso) = 943a1fa8c8aae9665d94b4e9ba7c6b5bf6668393c302df65c2decfa50616adfe SHA256 (FreeBSD-13.4-RC1-powerpc-powerpcspe-disc1.iso.xz) = 39136f7e8db036fbca7ce493c58a434b7daff50d88b1aec04b2a1c0114f0accd o 13.4-RC1 armv6 RPI-B: SHA512 (FreeBSD-13.4-RC1-arm-armv6-RPI-B.img.xz) = b710e4662dc5214fb83f7a078b891d3434e5d88c2e146c507deea4a8c7945eae511b12ddccfc26cc2d82b5c32fd1f9a428eb14a25d0f380ca7e40af873fec589 SHA256 (FreeBSD-13.4-RC1-arm-armv6-RPI-B.img.xz) = 4de0cff20c5c2950d91fe75e85e04371e38d21d3dbb564d054618bd85fab307b o 13.4-RC1 armv7 GENERICSD: SHA512 (FreeBSD-13.4-RC1-arm-armv7-GENERICSD.img.xz) = f045a36b8dbdf819211f39b3a6162e8c9f257370f25ec9d310875cb559999d68c9cf538f1f06b2bb2b3d914cc188d87e06489634ad80819151df124b06368438 SHA256 (FreeBSD-13.4-RC1-arm-armv7-GENERICSD.img.xz) = 40a0e276919e70982aa9737ab762c7bf83a55ce1027a7721d5c9625b1428f144 o 13.4-RC1 aarch64 GENERIC: SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-bootonly.iso) = f6af4a976b9652e30f1301fea45d35f029974610a35a911b35ef2e359e02db60f2f7d2d646ed72e26ef3967ed26335feb379ee47bf099c0d1ab32d92fe48ab66 SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-bootonly.iso.xz) = aaf1e6e3fc5d3385a3ef3431bc05594416d21395851cb34cd82215a6c90832c4bd0ffac1da9b8978411be8575b029c3fcd631be77a0db7e54fcd7b9a679f28e9 SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-disc1.iso) = 2a2a8cd598e9adcf280ed56bab73e886d6426419a043e788eef8f0135cded4604ba0d2e9ccaa57c5a759534138b77382ee0db0cafad64c5ad2c3c88e51c65d74 SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-disc1.iso.xz) = 56315cadcc91e6bec20e8bbae9a720d7fc4829b3e260ae299d104972637cfb0481266b438a19081e45dcbf023f13b75102fe3c7e9a5469582bf3cfe9bb27267b SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-dvd1.iso) = f2d0702beac03694ae5e4b4748abbcd1f281c1e72aa22631cf7f61a3b6961515d2684b90c67fba2a8aacb072e95223d0a0855421229ca23dcb030df290595b3f SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-dvd1.iso.xz) = f90ed43449910433c75e225bc4278eef8e66a66ed8520d0a3895a793bdeb66af68b8eba838fba2b1a71f1263da4b257afb9e603cb83dd45138f57c73e55653df SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-memstick.img) = c586ad158b8ef7fed6139c0ac23b7717b94f2d2ddfb4a87142bbc41306913817cdae4e0625a780602679fb09bc7ddd9edb9d6236d97f14394c9ea0196eb0beb8 SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-memstick.img.xz) = 2197697317ec01da1365eea87ed4b6bc1f653b461717a3309d0b6d791bdd028bd57c905f76c9fcd78491cac2bdff7b9d612dce749268e25861e936de57a8f267 SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-mini-memstick.img) = dfd57da1727a63478fb9d01550df6682b42a21a850345f5696c17b2706cb83f9e2a9444c869ccb08666227fe16009c623dd3e443be87907f4e9279a66170ea2d SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-mini-memstick.img.xz) = 99a285822befac75b2d3470d117ec2950de0eae76b5ca2efd13bf2ea18a96cf1e2b7abdcca86c8eb7f46d40ff22cca837ed251b09ef044744b810666d93962b6 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-bootonly.iso) = 708dd36d3fe511c8f9c57526b873bc12a2717424d0e80e6ceada6ba730f111c4 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-bootonly.iso.xz) = 1fc0ca215f4834dc1fdf802ec567b841e1596f6ec4ce55957653546e93e2ba7c SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-disc1.iso) = e762e362cd40c7d334196409ecb894b21701b7ffc4d5c77b54617c6c85bba8f0 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-disc1.iso.xz) = 8938cb517a21743f61e162e5dd49340442b22332143aa516da899a95967eca60 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-dvd1.iso) = c3fdf89b27b7bc029bc2ecd16c3f55053f1e904784611ff430caa8c306017b59 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-dvd1.iso.xz) = 8427a9ceda734b98dffb39da63005564de7fa9fb59512bc4ee5a3f7d4ea41b76 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-memstick.img) = 01c7528ec8c82d594efcd6ccbe2575df79c009db8f42fb36f7d754ad82be0a66 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-memstick.img.xz) = e1627f8d9b148a8067f1bbcc6c45b56efed1aab66b899c4ffbe1dee94d35098b SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-mini-memstick.img) = 6f1ea73b75183bf7eef5798bc5ce6f336d1ac0538d556a703abe0fdf73d1e52e SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-mini-memstick.img.xz) = 1f1eef425f87fbc7bcd1bc23b05a7cc50bfaca99c4808fab0fa80dfca9dbefd7 o 13.4-RC1 aarch64 RPI: SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-RPI.img.xz) = e52e2972cdf54ef6e6c17e01ef97ac14379abeb2c2bda5312501c98333754feb291a608d1c7b9c3e491fa1eb8fd77da8fce727e6a18ab96b21a6e31b4e57a239 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-RPI.img.xz) = 2ae82e99ef4dfe71441b34bc42d88e453442dcba3be2fc5a48afee0a5ad4a9fc o 13.4-RC1 aarch64 PINE64: SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-PINE64.img.xz) = a11850519b65476afa3cbc3beb5a2677f7a66e01dffc6e1f80d9e3d1034bcae607e889d708f60543ab32a6840e576a9eebacbfbd194313e2d20a41d17d2a2b1a SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-PINE64.img.xz) = cb10337d04e392a75b896235163fcea8a44dc66381530eb4fed9416448c23a3a o 13.4-RC1 aarch64 PINE64-LTS: SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-PINE64-LTS.img.xz) = 7b537e8eab170dda0223fd48653b7313f15798033b5cf2c9f8e1d2b4c662cc456a3f6fd0985e40ccd409eded0517f163c131b2b8afcf7f50e12764c8f3b5f10c SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-PINE64-LTS.img.xz) = 35e7acf887283cc4ef6699cee2e5e325631234be7fc19f2bea0008fd08dd3712 o 13.4-RC1 aarch64 PINEBOOK: SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-PINEBOOK.img.xz) = 2227c9707053e6d88ea7a2be5b68e7f733a7c61b647922f8fe745dc58119d62705116e4f9ebe5d2e2f89c400c80b69ae54bc5de683eabd316c9c7a42af4399f1 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-PINEBOOK.img.xz) = 3a258938851710ea63db7decbfca61eed3090300afdeb50becc7d021cf9ad359 o 13.4-RC1 aarch64 ROCK64: SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-ROCK64.img.xz) = a1de999df2e1a7e6a1d03fae8ef001c633a4b62aed26716527bc13c15344cd5f67d049effadc7c5ba1a86c1da889c257e0d0a4757125b91a4bdd651237c558f7 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-ROCK64.img.xz) = aedabfa7ab2f573b25206a3aa1ce43d868a11abfd48c988a92761eea38c806d2 o 13.4-RC1 aarch64 ROCKPRO64: SHA512 (FreeBSD-13.4-RC1-arm64-aarch64-ROCKPRO64.img.xz) = 0959a5e0ddb0b6d2fe8325842723e49d42a09962701bfa31f17efd88bea8a99b58ddc0b98a38b557bb167204b2c670033d373f653d23ceb7a80d5551b403d417 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64-ROCKPRO64.img.xz) = b3d720863a58818ebc91c1f4fb129a82fbbc571df7b26fae1d60909ba8931693 o 13.4-RC1 riscv64 GENERIC: SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-bootonly.iso) = e5c7f36e2f656bd6ffa4585ff235bd7625b4411bd31514ea26bc3f54f08db7d064147778a76a492e3051c55d847333d413203739d46505730acd40daecdca6b1 SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-bootonly.iso.xz) = 1e2b1a46eeae1bcf59d5ee5d8061e9e5a25d670f652298e2b28292c9221e56285c426611a27b381e1f98b3506214202c51df57a9a21a96f6aebd1dd54b551b54 SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-disc1.iso) = e7521ba4b8b76c546b6ad3e53a4b2371ab6f0034232954ff754d5b82f4d45598beae2093b332c64f768b3ba22fb178b814dd83c10df37901a40f1b51b07a654c SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-disc1.iso.xz) = ae276b8562b9b6e3ad10dd395af7b589a33d559a1d46df3e26cb5a5b4e674541021610742810dd677daacb63577db36e2d4fbc7d02c8e403282511f7387301e6 SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-memstick.img) = 51aa70e65d34ae65c2fdd8d12292d39acc9aa1752915bfc70cfa85bdfe8ad51d2829f26f696e6ad3249be3ddd54374368d26dd8ec5b76bf46c3fb82c2e7b10e4 SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-memstick.img.xz) = 7fea556b99c70f95e85bb27a2627e459b37ecc9c9c224cfaad25ebc23c1a0b349709831f1c3c535160b7523d6d460dba19a314c3dc72d9685af5c0a8f2664411 SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-mini-memstick.img) = 862fb0e23f3d2bf53e95ffe49af18a2debe0cc416af8c004b2a03229ce79d0e7ad533131dd427582a9e3429a7f55f2921094ee56e21018d9f628a2907483486e SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-mini-memstick.img.xz) = 07c03621bb1d8ce0200c4103ca4f3f4ebedb81f032b607a3fd1ecdc879a6a4926bdae308c13585d647b4a458497aab8780861de062b52664bbf6c9a3cd2dab7a SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-bootonly.iso) = 8b8c6e7b52df164d3ce8c3d0498f0020be596c86682cbdc30aa738be1222f8d8 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-bootonly.iso.xz) = 9c76aa49134e9491896d4aec2bd1bbdcb5482c058b2edcfad032761e073465d8 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-disc1.iso) = cd1df3bdbc510d6e49211695283c00cac83d1986d4990633c46b3ed155922842 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-disc1.iso.xz) = b819385a6b0ab3f2e3a730f4aecef42b8ab4a8d0a31fb32fbcb3b85ebfbf268a SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-memstick.img) = 68b4a39eae5edabf3c90a76a48584e5c2f097dbcd25fb171013784c2c7f244ef SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-memstick.img.xz) = 568310a7cc58da1f0a1fd1c973662ccbf1882fa53d14c8ec6c6d7e95904af8c2 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-mini-memstick.img) = 44f6ad8419def6114d1d202e11d1cb8c8a436d7dab76681795150974118ba2a8 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-mini-memstick.img.xz) = de84da3a3c84cf3dbbd5e27f75ebe5d353157a1700cfee47854b890cdf7cf61d o 13.4-RC1 riscv64 GENERICSD: SHA512 (FreeBSD-13.4-RC1-riscv-riscv64-GENERICSD.img.xz) = f7530edcaddcb785e8e796506a22616da4d70b0f94f81e7e64a95e0821a3178aa6ca96ca3780b4e16029e8414c41c0d3d1220c333f312e51a9252473d9391485 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64-GENERICSD.img.xz) = 6ae9e3f24a0d8040875dbb9498a006e6ab4ecd7b0941454514e38209d7475645 == VM IMAGE CHECKSUMS == o 13.4-RC1 amd64: SHA512 (FreeBSD-13.4-RC1-amd64.qcow2.xz) = e9ab9203376c2551dcc1a007bef3e1b9832ab4a3bfbbff346626df73249d6bb8f9cff2cd914492d3e0af3e9060b90575332d7d153cbeec7f109780b3807f1b91 SHA512 (FreeBSD-13.4-RC1-amd64.raw.xz) = 66e0dbfa2500cb79dbaefee9d89a444b395dc409fe1f08bcaa1e53a0805eee686ed636dc2dee8bf9b4695c3bc973b509afc7299d3345b4efb23711efe8047000 SHA512 (FreeBSD-13.4-RC1-amd64.vhd.xz) = 36f4e3b4f08d35fa30b4e6f1a9126fad2494403f65daffcc10697647a6cde42be87f124f17c01546a84794a7ef9fa52488f3458d6c0bfeb743b2ce337cdd778f SHA512 (FreeBSD-13.4-RC1-amd64.vmdk.xz) = 794036a192e6ea1632d2cab7272b5406dac9bdc5edd3eb2d1ed1b3257e95a460922b4050ff4861023d89ab519692dac3c41feec1759bccb90d3b2374fb32b884 SHA256 (FreeBSD-13.4-RC1-amd64.qcow2.xz) = 907357bf6ba8392066bfe5f840e74f8b51d9a92a086bf311e91d6391eadfc121 SHA256 (FreeBSD-13.4-RC1-amd64.raw.xz) = 0e6a0a11c7597d5f046b3c792ef0c6472ecb0c111452146ec1c56772339946c7 SHA256 (FreeBSD-13.4-RC1-amd64.vhd.xz) = 8b49336717891cf10a117dd49874903c7a094ee89d4da341bd3cdad5f03d36cd SHA256 (FreeBSD-13.4-RC1-amd64.vmdk.xz) = 81cbc5736bfce866f6409f85f7da9d3378deb9de01926965363852814f8e68d9 o 13.4-RC1 i386: SHA512 (FreeBSD-13.4-RC1-i386.qcow2.xz) = d72624e2756851f4e05469357b413b4e163e600d7598b112e406f08e64f91e0cf163b0bf3f41cc3bdb7610c409cc3a03e51e83283956cefb663dacbbdc6419b0 SHA512 (FreeBSD-13.4-RC1-i386.raw.xz) = f9c0d948e8365fa028172bc07d425f8b522b951150d9bf1161a1ba8a4007fe872b7fcf538f9f11e80a1c25f08f666495d66d96687642fda2a80be3d1528a3837 SHA512 (FreeBSD-13.4-RC1-i386.vhd.xz) = 856d1a56284cde9b650b297844073aa41f70c908dd69ba0dc850a760aef5480f91d71cde0459ca80f95d97a5947611db0239de9052af731e2f7c31e057becce2 SHA512 (FreeBSD-13.4-RC1-i386.vmdk.xz) = 3691c5ac851c379707e67c6c1443024e21e970a6a0374683374918c314a67343631142bf567556bfdfd6434d5ecfebedfeba49ba3fd9234c44ef55eaaeb9f201 SHA256 (FreeBSD-13.4-RC1-i386.qcow2.xz) = 6bdb4aec18316d40ed62c911d8fa410cc9f1eae42e4611cc094a7851c9c2d02d SHA256 (FreeBSD-13.4-RC1-i386.raw.xz) = 8a05bc25f5a6c3aef7eb3f89dc6b6817d26a7da59035ada37aa353c260de6d19 SHA256 (FreeBSD-13.4-RC1-i386.vhd.xz) = 742dcd2c36f0614396c8c2f58d3be72e8436f5564ed709d7050e92e3f25e6dc0 SHA256 (FreeBSD-13.4-RC1-i386.vmdk.xz) = 17d494dd98f3751ff71efd53469ec9365c3f93593f40c42b08dbf0e2b902e8c2 o 13.4-RC1 aarch64: SHA512 (FreeBSD-13.4-RC1-arm64-aarch64.qcow2.xz) = 975f0e86679b9c5c4562ae78b55fca335d34bacbfe04e9502bc75a5ed3394965a08553838932d1a4fbf023ceb9780caf31932ff2bd63215125c5791542a3f0a9 SHA512 (FreeBSD-13.4-RC1-arm64-aarch64.raw.xz) = 51dc558be5e7b10a73e6cd26ae2b1a1df93bbdde3bdba3618863e83381775205dffe0e6c95fe6691e1c9b02bbfa696d4dd7540c936fd35d34ec9279dc49d8abe SHA512 (FreeBSD-13.4-RC1-arm64-aarch64.vhd.xz) = 1dd13ed2c9d2e920e7b7f8df5d81ae915fc38629714bbb45cd2175fd387c17ad68339c7d24987fd6247b8bbb8090938e686559abd56ebe8c23702c2fc3c08c41 SHA512 (FreeBSD-13.4-RC1-arm64-aarch64.vmdk.xz) = 393c7a58665b624bf5037b45db70dad56f06a928fd591849b57b0a8f4604a848e8333334858ca7db99fa5badc90f9e221783144375718b92930f8062a70e0ab0 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64.qcow2.xz) = 0745ffa4ee475dcabe64942133a97b4da951a4cb147e954b1b509c5000457b36 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64.raw.xz) = a72b8123219d3fc0f23c86b14d38139719c9ae38d853bd596cc0cc35f0fbf6b8 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64.vhd.xz) = 9cba52311b40075a2a161fc2732dd2b62b4da462004524c2aba6fb3cfcdd94d4 SHA256 (FreeBSD-13.4-RC1-arm64-aarch64.vmdk.xz) = 4ba9252f2a60be03b4a6557f2ffd4f142109de285fa01526f000cbc4f739ae7b o 13.4-RC1 riscv64: SHA512 (FreeBSD-13.4-RC1-riscv-riscv64.qcow2.xz) = 034b32f1138322638c7a5b7949a3b184c6a4cdfd003360a496c08c56c2cc645c94fbe9cdf9d84c963af6dda6c442717cd61d7e1cecf7024bd463f6f5196c5527 SHA512 (FreeBSD-13.4-RC1-riscv-riscv64.raw.xz) = 034b32f1138322638c7a5b7949a3b184c6a4cdfd003360a496c08c56c2cc645c94fbe9cdf9d84c963af6dda6c442717cd61d7e1cecf7024bd463f6f5196c5527 SHA512 (FreeBSD-13.4-RC1-riscv-riscv64.vhd.xz) = 034b32f1138322638c7a5b7949a3b184c6a4cdfd003360a496c08c56c2cc645c94fbe9cdf9d84c963af6dda6c442717cd61d7e1cecf7024bd463f6f5196c5527 SHA512 (FreeBSD-13.4-RC1-riscv-riscv64.vmdk.xz) = 034b32f1138322638c7a5b7949a3b184c6a4cdfd003360a496c08c56c2cc645c94fbe9cdf9d84c963af6dda6c442717cd61d7e1cecf7024bd463f6f5196c5527 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64.qcow2.xz) = 0040f94d11d0039505328a90b2ff48968db873e9e7967307631bf40ef5679275 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64.raw.xz) = 0040f94d11d0039505328a90b2ff48968db873e9e7967307631bf40ef5679275 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64.vhd.xz) = 0040f94d11d0039505328a90b2ff48968db873e9e7967307631bf40ef5679275 SHA256 (FreeBSD-13.4-RC1-riscv-riscv64.vmdk.xz) = 0040f94d11d0039505328a90b2ff48968db873e9e7967307631bf40ef5679275 Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEglY7hNBiDtwN+4ZBOJfy4i5lrT8FAmbJfXIACgkQOJfy4i5l rT+7Ww//Qs7nYhvJMeFOR59nkwvXFFGFpK1qYchpG9oX0SBjwYOCdosBVrfNd+Bh +971JD/SexMxTETKn+N7SLfMPqHhVUsqPipH1aI62WAVxT5jIqAXHlw3Al7eHPEY aZEwm/hTRxEkoM2F4evdAXGwu1jynLh4e2b5Pl2t2ycy0/7zGV+a8bq7OUVr1f+1 +9Y30iTMy8ZlNInjISdfCU6UZxoxnEzDi0/CxCoyA9hh5QqL0TjlGYzEFQ0r+HCM MrLrS/Ha/UDgkmpu2k7RGMf6xB0R04HEcaCT0eX+SvaZwf03vuiNw85TbNB3aWFT SK0XLF6YXPJOcGjqjjiCtK8w3SJ0kDLj1OwafuPSym/Hf5k1/lVdsT3fURg4D6KB 6e7fkbuiUcnHlooAfwsGPsJmD6uu7Q30l/yX03Ge3gaZl7yu+WoDdrdSwoCeLC/i aAOSy/KRpkyyMDeDs64r6j5AEqFlU6dwwmRvMpfM6ha6oRbVixXni1SJgpHSPa3o wCi/m+YbG1jcKFtz3+s1CDptWOBvKWkQH0xwExBdhcZGwJNjVvhveEX3KQybExAy VNEnPngk5J03pRfPW7eI6lLjd/MZMwBl6RaqrzRf9zd+B71qQGPdm608HUZgksCe c5Q7NjNVOPQbmChnOafpOzG/dQ/tgEJ22uq922/B2yUiplX+fh8= =00Ds -----END PGP SIGNATURE----- From ml@ft-c.de Sun Aug 25 09:05:39 2024 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 4Ws7FT186Jz5Vddk for ; Sun, 25 Aug 2024 09:05:49 +0000 (UTC) (envelope-from ml@ft-c.de) Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 "mail.in-berlin.de", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws7FR6LF0z48Yd for ; Sun, 25 Aug 2024 09:05:47 +0000 (UTC) (envelope-from ml@ft-c.de) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ml@ft-c.de designates 192.109.42.8 as permitted sender) smtp.mailfrom=ml@ft-c.de X-Envelope-From: ml@ft-c.de X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id 47P95eCS1082976 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Sun, 25 Aug 2024 11:05:40 +0200 Message-ID: Subject: delete zfs and snapshots from upgrade process? From: ft Reply-To: ml@ft-c.de To: FreeBSD-STABLE Mailing List Date: Sun, 25 Aug 2024 11:05:39 +0200 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4 FreeBSD GNOME Team 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 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.28 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.99)[-0.985]; R_SPF_ALLOW(-0.20)[+ip4:192.109.42.0/24]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[192.109.42.8:from]; ONCE_RECEIVED(0.10)[]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[ft-c.de]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:29670, ipnet:192.109.42.0/24, country:DE]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; HAS_REPLYTO(0.00)[ml@ft-c.de] X-Rspamd-Queue-Id: 4Ws7FR6LF0z48Yd Hello, I have make an upgrade from 13.1 to 14.1.=20 uname -a=C2=A0 FreeBSD ftc 14.1-RELEASE-p3 FreeBSD 14.1-RELEASE-p3 GENERIC amd64 Everything works fine.=20 My question: There are some zfs and some snapshots. Can I destroy them or are they required? Here is the list: zfs: zroot/ROOT/13.1-RELEASE-p9_2023-08-27_201128 zroot/ROOT/13.1-RELEASE_2023-08-27_195317 zroot/ROOT/13.2-RELEASE-p12_2024-08-24_192252 zroot/ROOT/13.2-RELEASE-p2_2023-08-27_223329 zroot/ROOT/13.2-RELEASE-p2_2024-08-24_185205 zroot/ROOT/14.1-RELEASE-p3_2024-08-24_192543 snapshots: zroot/ROOT/default@2023-08-27-19:53:17-0 zroot/ROOT/default@2023-08-27-20:11:28-0 zroot/ROOT/default@2023-08-27-22:33:29-0 zroot/ROOT/default@2024-08-24-18:52:05-0 zroot/ROOT/default@2024-08-24-19:22:52-0 zroot/ROOT/default@2024-08-24-19:25:43-0 Franz From nobody Sun Aug 25 09:52:33 2024 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 4Ws8HV5Qlwz5VhqM for ; Sun, 25 Aug 2024 09:52:38 +0000 (UTC) (envelope-from matthew@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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws8HV4dfcz4Gp0 for ; Sun, 25 Aug 2024 09:52:38 +0000 (UTC) (envelope-from matthew@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724579558; 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:autocrypt:autocrypt; bh=V6qymwl0XwEhIc1yGb9KlIcGKs76hV5ZKuGSTBXBAc4=; b=iFevaQIIY48PbvtFrC0SztRS820LuRK2CSapNlzer0mlp84zA69V1OH4d7p95WxgotjVf+ YH3olxftc9avLsECPKeagr6x4sUBz5FqLFh7YIDpsr50/4l7ht1wGwDh0NdSvr8bd9125x l9AcVhaXvMbAMTALMcVJSQCIqGChY41Pdse7JajTqHx4v72lujTqMPSL74+BMCJ54SNzhx LuviZPV5HmVNDBahgHGwvQlBDTTM7o+78lX9ZS7DICyc0m7PFnBNKo2J09v1g4zmjHVHEY 2suvBHgDRbO+yWcaFEo2dEDmVMNl2WW5g9BaQDBQqCcrYtlFb7TOEkyPSOht0g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724579558; a=rsa-sha256; cv=none; b=CVbbqFQPEvpB0hdeJOBU++iWyh5tkGAPVPesP18tkRpr5uhbtdUQfmx9TrMgyH3RmRLk03 LGEMgVGfh6SedSOvQUyD24cvnHhaG0H5G9SNqDrYT1FWD8F3ODo/7kayOFexYMvS/7YOW5 cop4XfEGUK/48a7oRty6ShVeVMkAeShpa9hvA9qx9+A6sSeIe52cibkM2gpu4yOTY2rQui tcBucPZ9EJE9DBrsWtGWOf0b60/3GNu1kCuyi1GjE1ppZzCvTcU/GyFoh1uCY8ogtDkEUF ln5PF2eGIcYEa+ZGyn3zdbAPP2ohx7/c3BamwF0rHH8DLW3sbrNWywfW3LrEDg== ARC-Authentication-Results: i=1; smtp.infracaninophile.co.uk; dmarc=fail (p=none dis=none) header.from=FreeBSD.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724579558; 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:autocrypt:autocrypt; bh=V6qymwl0XwEhIc1yGb9KlIcGKs76hV5ZKuGSTBXBAc4=; b=Vz3hvp6hAcAwTlTwG94n3qdALcmR2N6b3UGPpQ0/MplTplx7LXN9oXiSciJXMtAiV9DkOU S4NY9p7AagFNXPnYK2+/xYy+fbo4bLWqEs1FO6ixeJ+NWFYyLa90RxrWEMVA/qfVMJGl3f TX1An2htZNsDHruvQSpc8o+dgHlK0KznYXqoa9tm2/eSJb/5xoESTVTbQIGcdhekV9vhL9 8xOzNZ0KGPUXu26r6P3o4degoth46wVPq2OwbingwF4WwNvBsLfnO0AppWQoPb7FpHMN2Y x1pjApnkvPm2BTIuBEwaeMPJQAYAuVOMgkNYbKtmHFtD2r4eONWrlG4A3IsplA== Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (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: matthew/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Ws8HV35wRzFm5 for ; Sun, 25 Aug 2024 09:52:38 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from [IPV6:2001:8b0:151:1:54fc:974d:575c:92b3] (unknown [IPv6:2001:8b0:151:1:54fc:974d:575c:92b3]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 027C41C96A for ; Sun, 25 Aug 2024 10:52:33 +0100 (BST) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=fail (p=none dis=none) header.from=FreeBSD.org Message-ID: Date: Sun, 25 Aug 2024 10:52:33 +0100 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 User-Agent: Mozilla Thunderbird Subject: Re: delete zfs and snapshots from upgrade process? To: stable@freebsd.org References: Content-Language: en-GB From: Matthew Seaman Autocrypt: addr=matthew@FreeBSD.org; keydata= xsFNBFJIL80BEADi7/VbnnErDU6pjEhI/SzEZ/HbDRkJ5g7HroAtqIRm6nj8ZwOAgZ/2ZnWn 5F+fXTuLsG0FLNtkd17FoVcuCi5e/GPliXI5cmamV7E1Yz4T8UsJ7RQolimyxVexccKd16Tc AA7B9bFlJSKkBUSD0buj7VjT07xWhRzu6Vgi5r0UjLALYJz977uZA0F1aOGOXREDEAOhdcNc kSNjynqAwDA6dCT1Elpi4key1fYjv4jyDF+GU/YXul2Y/rguA8FCkHd9vyym5eAsLQ5mG00V V9fkEHIpH5KorNVnl/ufHXnkZqmHAZVpFDcrshb7aZ/pL45PXyWgLj+e6etelgj3a2bZi0JF cVdXCnBZVP2oIyYblM11ugTbfCwodORU8a5KfPeztMdAtDr4e+32NTrPdPi5rLT+GUsYz+PL 3A3m3u8bdsFp40DlIrBtSByVjqERxcfhphrEB4J8BXHUG7OAtXkZMlW/PGKDwXJq0O6Z5Tcg YHAoEiSWbXiexHgXNJyP+sqnIlhLWhSJGeJ+C83wqI6oYlZUCW00NkPxcIHnQPV/z+5wQVci TMyaWC2YCIHz4Ljs+TnwWMz0E8PNFDfHVbQ0W4PRGV7gRAqxfL+yKufauIEGbEq8rNDbSwL3 bcUCxR4ZDlaUEUwT4J8naf7rjdgiEYHs2Ig3jeK1+ER4FPG1sQARAQABzSRNYXR0aGV3IFNl YW1hbiA8bWF0dGhld0BmcmVlYnNkLm9yZz7CwZQEEwEKAD4CGwMFCwkIBwMFFQoJCAsFFgMC AQACHgECF4AWIQRyz6whebywJLW1RZADb2ye5/OevwUCZidQVgUJFcBUAQAKCRADb2ye5/Oe v7hXD/sHeYOYYCQsv8urMfbQCjUXPgP9UzPVBDudVT4VlPjsg4kRzTJC4aCDcpV1s5kVaMc3 nDN1TOOjV8Fmo3kFCsoow8U+uqX3+41ODPG01/i7+SDtCABhDlXtRPpFPsN0O/wdwWz6URV8 Pcfb3Uvo7hqgMWhaLfzdJeSdbZoU3qU5nGYcRrW4ojYCUKYCICmnG9af3H4RDSUzhxpcvUiG Gf0eiO6j80YYFx4kAyL6g2IkRSQ+HYAJc8bX4z/unJqBP154PxcHPvyLIQjYouDHTE0EX/Kw tIk1uwFuOWeC417ZinJuI5/Fsei8COmb7+axIDeqt+63ytxZAB3fiK3V1qmQwBf+H3H3fuXe 7cd9NML8gbXRsjRBzuKDsHfJyJwNU47DlbRXhUlWALfawCndU8Ka+4FbhS5WfO7m/bd3/A0k 6gqnUhRr07V1kds25gIwyBjvUF2MdCkdk3VrzEmU5oXBI9jfBK3s0j8DXESWHKJTf5hwmGDX 6rjzyRh0Nv9ZVQYFUwypBAP4koklZLEjh8Gme7dr3qbmcl+r1pBD6M6EFYfFqDI3kr7FwH0e wsspX6FoX+OPBMsit4CmqR4T2HuTD0ayn5kMQk9lmScJNVjdoLH1yf/KDFBfKuAL+gOyaKnB lGmbEfSqsXCnBue8wfDZOxr4bxQFg+HQ88YdH6032s7BTQRSUUK4ARAA1FhWoOejtwmsnGsh oIbda2FmM+z/f97OzpagLhACHfP5Es/I18wG/0G+rdNuO2tjA9IMZ44GUMtjokDrDk63N9S+ rVKy1QEy+UN6CiIfYTpTTAPnEY7IGN1JjGksPhn7aeuBCQwUMAV1k+wklBCcOD6s8DD4kx0Z JqkH83XzWoBSVamdHvnM56C8yPVr5HHMC1tZInAWBMrF+cjl1EPfz3CqkVnG8Sxc5ydeibMS 9Q3lHLeVkVlMRAmNqzNLfgJDUWtzac7JIjFEsxYYhpiaPcsstUUuHa4zIRJ/yHDNbDttWRf1 lrlFZLpeuap4BZ2hQw0UOZVNwGoFoS4ZqaZiv8mm0lX6s9/AdQD6AVrpXWKa7JU2wDiay9sR bYh+5vVWGz9mhncK/Vfwtu5IjVp5v5WMz/WfnUxZMcNlfgTo4i1swww+qRBO2A4Yj8qKKWnT sl7aCX92itTiPgwbt6YgQPwgww72r67jPt5o8VMXDqPMPKzGicw1AyxtMjsoSlnn91FuZctw il3vPpvzGXtBmrzQSbdDmy0KT5p5/W9pD/8UtLLLM6PLs5X0jIhovQHnQKEUO7xV3yNDAW9D PICeh7f/o9W+QJfQAXngNz0brvmgScAUXRaeAFeQbAmtEG92qlSVD7gb7WOemllgfbEn0Nan rv5aEcZCWx4WjybMLHEAEQEAAcLBfAQYAQoAJgIbDBYhBHLPrCF5vLAktbVFkANvbJ7n856/ BQJmJ1DIBQkVt0GQAAoJEANvbJ7n856/SOkP/iocAFde4BUQ8D8WQuG+dXum75rwlV1NutwI dzZyzLDF6l5ItV9t1VtWVOpd7lgWqHtUBGqjm6mw6qR9YoXNMeycnokBq2YSunLuV2K/UEij NES6deNYYu1HIb4GbfeEODiK2xQ40dDPwpucSQmZ0FeHfnkO7hgIRlywbIyG8p4HHuKR01/W 07pOGGRA6F8GRoI+m38ARe+r/2W4HlrJnS/+POKm6lu67wdtcBNqeYF3rcgrvh08bqZtIaEt GoyZ54tRpoWq6aTXvI88T5oABwZKn95m5KAvUlQ15IOGF049uAN4APOExOtqVNcvQPypeRCo OTShW20C1ZM3ZaRc39alDu3bj1S24K/Ldav8Qe+kzWs744Tu+QytbWtpr+gvkrpPVXdFiFiD uCF3WQZrTdTr3Nm5ES2ePV2YW02M837VnmW8hm9id3iiBawyhdUyNtSPXXGTZSMD/TZ8urv2 R3xMkpoh2j5PIJ4cF2ZJEz/VOaWv6LN4/+MgC7icVyUldoOZeWFjLS2YBgy50ICICmCefF4e kMGcbPi9+OAd1lLYwkLd1AAhQu1JPU163KW8/Bkc/FqrzE0iJxX9N3I3Zyt3uswd1+7Lxisw WZdkvBJvTpHtp1CeiA794MDJEVQfI9o5icfRBNOoPJM8c56FTs19JmiH35KSh45LpcSbDr3t In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMjUvMDgvMjAyNCAxMDowNSwgZnQgd3JvdGU6DQoNCj4gSSBoYXZlIG1ha2UgYW4gdXBn cmFkZSBmcm9tIDEzLjEgdG8gMTQuMS4NCj4gdW5hbWUgLWENCj4gRnJlZUJTRCBmdGMgMTQu MS1SRUxFQVNFLXAzIEZyZWVCU0QgMTQuMS1SRUxFQVNFLXAzIEdFTkVSSUMgYW1kNjQNCj4g DQo+IEV2ZXJ5dGhpbmcgd29ya3MgZmluZS4NCj4gDQo+IE15IHF1ZXN0aW9uOg0KPiBUaGVy ZSBhcmUgc29tZSB6ZnMgYW5kIHNvbWUgc25hcHNob3RzLiBDYW4gSSBkZXN0cm95IHRoZW0g b3IgYXJlIHRoZXkNCj4gcmVxdWlyZWQ/DQo+IA0KPiBIZXJlIGlzIHRoZSBsaXN0Og0KPiB6 ZnM6DQo+IHpyb290L1JPT1QvMTMuMS1SRUxFQVNFLXA5XzIwMjMtMDgtMjdfMjAxMTI4DQo+ IHpyb290L1JPT1QvMTMuMS1SRUxFQVNFXzIwMjMtMDgtMjdfMTk1MzE3DQo+IHpyb290L1JP T1QvMTMuMi1SRUxFQVNFLXAxMl8yMDI0LTA4LTI0XzE5MjI1Mg0KPiB6cm9vdC9ST09ULzEz LjItUkVMRUFTRS1wMl8yMDIzLTA4LTI3XzIyMzMyOQ0KPiB6cm9vdC9ST09ULzEzLjItUkVM RUFTRS1wMl8yMDI0LTA4LTI0XzE4NTIwNQ0KPiB6cm9vdC9ST09ULzE0LjEtUkVMRUFTRS1w M18yMDI0LTA4LTI0XzE5MjU0Mw0KPiBzbmFwc2hvdHM6DQo+IHpyb290L1JPT1QvZGVmYXVs dEAyMDIzLTA4LTI3LTE5OjUzOjE3LTANCj4genJvb3QvUk9PVC9kZWZhdWx0QDIwMjMtMDgt MjctMjA6MTE6MjgtMA0KPiB6cm9vdC9ST09UL2RlZmF1bHRAMjAyMy0wOC0yNy0yMjozMzoy OS0wDQo+IHpyb290L1JPT1QvZGVmYXVsdEAyMDI0LTA4LTI0LTE4OjUyOjA1LTANCj4genJv b3QvUk9PVC9kZWZhdWx0QDIwMjQtMDgtMjQtMTk6MjI6NTItMA0KPiB6cm9vdC9ST09UL2Rl ZmF1bHRAMjAyNC0wOC0yNC0xOToyNTo0My0wDQoNCk9uY2UgeW91J3JlIGhhcHB5IHRoYXQg ZXZlcnl0aGluZyBpcyBmaW5lIHdpdGggMTQuMSBhbmQgeW91J2xsIG5ldmVyIA0Kd2FudCB0 byByZXZlcnQgdG8gYSBwcmV2aW91cyB2ZXJzaW9uLCB0aGVuIHlvdSBjYW4gZGVsZXRlIHRo ZSBvbGQgYm9vdCANCmVudmlyb25tZW50cywgYW5kIHRoZSBzbmFwc2hvdHMgdGhleSBhcmUg YmFzZWQgb24uICBJIGdlbmVyYWxseSBydW4gd2l0aCANCnR3byBib290IGVudmlyb25tZW50 cyAtLSB0aGUgY3VycnJlbnQgb25lIGFuZCBvbmUgcHJldmlvdXMganVzdCBpbiBjYXNlLCAN CmJ1dCBJIGhhdmVuJ3QgbmVlZGVkIHRvIHJldmVydCB0byBhbiBvbGRlciBCLkUuIGluIGEg dmVyeSBsb25nIHRpbWUuDQoNClVzZSBgYmVjdGwgZGVzdHJveWAgdG8gZGVsZXRlIGJvb3Qg ZW52aXJvbm1lbnRzIGFzIHRoaXMgd2lsbCBkZWxldGUgDQphc3NvY2lhdGVkIHNuYXBzaG90 cyBmb3IgeW91IGFzIHdlbGwuDQoNCglDaGVlcnMsDQoNCglNYXR0aGV3DQoNCg0K From ml@ft-c.de Sun Aug 25 19:15:03 2024 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 4WsNmX3zglz5TMSH for ; Sun, 25 Aug 2024 19:15:08 +0000 (UTC) (envelope-from ml@ft-c.de) Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 "mail.in-berlin.de", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WsNmW2vw0z4CW5 for ; Sun, 25 Aug 2024 19:15:07 +0000 (UTC) (envelope-from ml@ft-c.de) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of ml@ft-c.de designates 192.109.42.8 as permitted sender) smtp.mailfrom=ml@ft-c.de X-Envelope-From: ml@ft-c.de X-Envelope-To: Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id 47PJF48V1689783 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Sun, 25 Aug 2024 21:15:04 +0200 Message-ID: Subject: cpan module install From: ft Reply-To: ml@ft-c.de To: FreeBSD-STABLE Mailing List Date: Sun, 25 Aug 2024 21:15:03 +0200 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4 FreeBSD GNOME Team 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 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.22 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.988]; NEURAL_HAM_LONG(-0.99)[-0.986]; NEURAL_HAM_SHORT(-0.95)[-0.950]; R_SPF_ALLOW(-0.20)[+ip4:192.109.42.0/24]; RWL_MAILSPIKE_GOOD(-0.10)[192.109.42.8:from]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:29670, ipnet:192.109.42.0/24, country:DE]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[ft-c.de]; HAS_REPLYTO(0.00)[ml@ft-c.de] X-Rspamd-Queue-Id: 4WsNmW2vw0z4CW5 Hello when I install a cpan module with pkg,=C2=A0 it is stored in /usr/local/lib/per5/... When I install cpan module (as root) with command cpan, the module is stored in root directory. (~/.cpan/...) It is possible to store these module in /usr/local/lib/... too? Franz=20