diff --git a/website/content/en/status/report-2023-04-2023-06/_index.adoc b/website/content/en/status/report-2023-04-2023-06/_index.adoc index 55391f1912..70a11b6038 100644 --- a/website/content/en/status/report-2023-04-2023-06/_index.adoc +++ b/website/content/en/status/report-2023-04-2023-06/_index.adoc @@ -1,220 +1,234 @@ --- title: "FreeBSD Status Report Second Quarter 2023" sidenav: about --- = Introduction :doctype: article :toc: macro :toclevels: 2 :icons: font :!sectnums: :source-highlighter: rouge :experimental: :reports-path: content/en/status/report-2023-04-2023-06 include::content/en/status/categories-desc.adoc[] include::{reports-path}/intro.adoc[] ''' toc::[] ''' [[FreeBSD-Team-Reports]] == FreeBSD Team Reports {FreeBSD-Team-Reports-desc} +''' + include::{reports-path}/core.adoc[] ''' include::{reports-path}/freebsd-foundation.adoc[] ''' include::{reports-path}/releng.adoc[] ''' include::{reports-path}/clusteradm.adoc[] ''' include::{reports-path}/ci.adoc[] ''' include::{reports-path}/portmgr.adoc[] ''' [[projects]] == Projects {projects-desc} ''' include::{reports-path}/cirrus.adoc[] ''' include::{reports-path}/batman.adoc[] ''' include::{reports-path}/kboot.adoc[] ''' include::{reports-path}/lldb-kmod.adoc[] ''' [[userland]] == Userland {userland-desc} ''' include::{reports-path}/openssl3.adoc[] ''' include::{reports-path}/linuxulator.adoc[] ''' include::{reports-path}/service-jails.adoc[] ''' include::{reports-path}/capsicum-ktracing.adoc[] ''' include::{reports-path}/nvmf.adoc[] ''' [[kernel]] == Kernel {kernel-desc} +''' + include::{reports-path}/boot-performance.adoc[] ''' include::{reports-path}/ci-bootloader.adoc[] ''' include::{reports-path}/compaction.adoc[] ''' include::{reports-path}/maxcpu.adoc[] ''' include::{reports-path}/squashfs.adoc[] ''' include::{reports-path}/pf.adoc[] ''' include::{reports-path}/ifapi.adoc[] ''' include::{reports-path}/epoch-netgraph.adoc[] ''' [[architectures]] == Architectures {architectures-desc} +''' + include::{reports-path}/simd.adoc[] ''' include::{reports-path}/mfsbsd.adoc[] ''' [[cloud]] == Cloud {cloud-desc} +''' + include::{reports-path}/cloud-init.adoc[] ''' include::{reports-path}/openstack.adoc[] ''' include::{reports-path}/azure.adoc[] ''' include::{reports-path}/ec2.adoc[] ''' [[documentation]] == Documentation {documentation-desc} +''' + include::{reports-path}/doceng.adoc[] ''' [[ports]] == Ports {ports-desc} +''' + include::{reports-path}/kde.adoc[] ''' include::{reports-path}/gcc.adoc[] ''' include::{reports-path}/puppet.adoc[] ''' include::{reports-path}/caldera.adoc[] ''' include::{reports-path}/wazuh.adoc[] ''' [[third-Party-Projects]] == Third Party Projects {third-Party-Projects-desc} +''' + include::{reports-path}/pkgbase.live.adoc[] ''' include::{reports-path}/pot.adoc[] diff --git a/website/content/en/status/report-2023-04-2023-06/azure.adoc b/website/content/en/status/report-2023-04-2023-06/azure.adoc index 39a41c5d3b..2458fbb414 100644 --- a/website/content/en/status/report-2023-04-2023-06/azure.adoc +++ b/website/content/en/status/report-2023-04-2023-06/azure.adoc @@ -1,49 +1,51 @@ === FreeBSD on Microsoft HyperV and Azure Links: + link:https://wiki.freebsd.org/MicrosoftAzure[Microsoft Azure article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/MicrosoftAzure[] + link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[] Contact: Microsoft FreeBSD Integration Services Team + Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[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 worked mainly on ARM64 architecture support and building and publishing images to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery]. There are some testing images available in the project's testing public gallery, named `FreeBSDCGTest-d8a43fa5-745a-4910-9f71-0c9da2ac22bf`: ++ * FreeBSD-CURRENT-testing * FreeBSD-CURRENT-gen2-testing * FreeBSD-CURRENT-arm64-testing To use them, when creating a virtual machine: ++ . In `Select an Image` step, choose `Community Images (PREVIEW)` in `Other items` . Search `FreeBSD` Work in progress tasks: * Automating the image building and publishing process and merge to src/release/. * Building and publishing ZFS-based images to Azure Marketplace ** All the required codes are merged to main branch, and can create ZFS-based images by specifying `VMFS=zfs`. ** Need to make the build process more automatic and collaborating with release engineering to start generating snapshots. * Building and publishing Hyper-V gen2 VM images to Azure Marketplace * Building and publishing snapshot builds to Azure community gallery The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft. Wei Hu and Souradeep Chakrabarti in Microsoft are working on several tasks sponsored by Microsoft: * Porting Hyper-V guest support to aarch64 ** https://bugs.freebsd.org/267654 ** https://bugs.freebsd.org/272461 Open tasks: * Update FreeBSD related doc at link:https://learn.microsoft.com[Microsoft Learn] * Support FreeBSD in link:https://azure.microsoft.com/products/devops/pipelines/[Azure Pipelines] * Update link:https://www.freshports.org/sysutils/azure-agent[Azure agent port] to the latest version * Upstream link:https://github.com/Azure/WALinuxAgent/pull/1892[local modifications of Azure agent] Sponsor: Microsoft for people in Microsoft, and for resources for the rest + Sponsor: The FreeBSD Foundation for everything else diff --git a/website/content/en/status/report-2023-04-2023-06/ci-bootloader.adoc b/website/content/en/status/report-2023-04-2023-06/ci-bootloader.adoc index fa51068139..d38c25afb3 100644 --- a/website/content/en/status/report-2023-04-2023-06/ci-bootloader.adoc +++ b/website/content/en/status/report-2023-04-2023-06/ci-bootloader.adoc @@ -1,21 +1,21 @@ === CI Test Harness For Bootloader Links: + -link:https://wiki.freebsd.org/SummerOfCode2023Projects/CITestHarnessForBootloader[FreeBSD Wiki GSoC Page] + -link:https://github.com/mightyjoe781/freebsd-src/tree/bootloader-smk/tools/boot/bootloader_test[Github Project Link] +link:https://wiki.freebsd.org/SummerOfCode2023Projects/CITestHarnessForBootloader[FreeBSD Wiki GSoC Page] URL: https://wiki.freebsd.org/SummerOfCode2023Projects/CITestHarnessForBootloader[] + +link:https://github.com/mightyjoe781/freebsd-src/tree/bootloader-smk/tools/boot/bootloader_test[GitHub Project Link] URL: https://github.com/mightyjoe781/freebsd-src/tree/bootloader-smk/tools/boot/bootloader_test[] Contact: Sudhanshu Mohan Kashyap FreeBSD supports multiple architectures, file systems, and disk-partitioning schemes. I am trying to write a Lua script which would allow for testing boot loader of all the architecture combinations supported in the first and second-tier support, and provide a report on any broken combinations and expected functionality. -If time permits, further exploration could be done to integrate the script into the existing build infrastructure (either Jenkins or Github Actions) to generate a comprehensive summary of the test results. +If time permits, further exploration could be done to integrate the script into the existing build infrastructure (either Jenkins or GitHub Actions) to generate a comprehensive summary of the test results. Currently any changes made by developer might inhibit the ability of the operating system to boot in some specific environment. These scripts provide assurance that changes do not cause regressions for the tested environments. The scripts are designed to be efficient and much less expensive than a full make universe required today. These attributes allow developers to routinely use the script, and allow integration into the CI pipelines without undue cost. Currently script related work seems to be on track, but certainly ahead I will need to find all different kinds of QEMU recipes to test different environments. If anyone has any kind of working QEMU recipe for currently released versions of FreeBSD, feel free to send to me via mail at smk@FreeBSD.org . Sponsor: The Google Summer of Code '23 program diff --git a/website/content/en/status/report-2023-04-2023-06/cirrus.adoc b/website/content/en/status/report-2023-04-2023-06/cirrus.adoc index 268bcba264..b0a91ec5ff 100644 --- a/website/content/en/status/report-2023-04-2023-06/cirrus.adoc +++ b/website/content/en/status/report-2023-04-2023-06/cirrus.adoc @@ -1,24 +1,24 @@ === Cirrus-CI Links: + -link:https://cirrus-ci.com/github/freebsd/[FreeBSD Cirrus-CI Repositories] URL: link:https://cirrus-ci.com/github/freebsd/[] -link:https://cirrus-ci.com/github/freebsd/freebsd-src[FreeBSD src CI] URL: link:https://cirrus-ci.com/github/freebsd/freebsd-src[] +link:https://cirrus-ci.com/github/freebsd/[FreeBSD Cirrus-CI Repositories] URL: link:https://cirrus-ci.com/github/freebsd/[] + +link:https://cirrus-ci.com/github/freebsd/freebsd-src[FreeBSD src CI] URL: link:https://cirrus-ci.com/github/freebsd/freebsd-src[] + link:https://cirrus-ci.com/github/freebsd/freebsd-doc[FreeBSD doc CI] URL: link:https://cirrus-ci.com/github/freebsd/freebsd-doc[] -Contact: Brooks Davis -Contact: Ed Maste +Contact: Brooks Davis + +Contact: Ed Maste + Contact: Li-Wen Hsu Cirrus-CI is a hosted continuous integration service that supports open source projects with CI services on Linux, Windows, macOS, and FreeBSD. It complements our own Jenkins CI infrastructure by supporting other use cases, including testing GitHub pull requests and FreeBSD forks. We added Cirrus-CI configuration to the FreeBSD src tree in 2019 and to doc in 2020. A number of additional FreeBSD projects hosted on GitHub (such as drm-kmod, kyua, pkg, and poudriere) also make use of Cirrus-CI. -Over the last quarter Cirrus-CI configs received ongoing maintenance updates (moving to the most recent FreeBSD release images). +Cirrus-CI configs received ongoing maintenance updates (moving to the most recent FreeBSD release images). In the src tree we have added some additional checks. These ensure that generated files are updated when needed (`make sysent` and `make makeman`) and check for missing directories. We have added jobs that build using the Clang/LLVM 16 toolchain package, mirroring the Clang version now in the base system. The GCC job is now run on the GitHub mirror by default, for all commits. -Sponsor: DARPA +Sponsor: DARPA + Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-04-2023-06/doceng.adoc b/website/content/en/status/report-2023-04-2023-06/doceng.adoc index fd015916b4..2cae11159f 100644 --- a/website/content/en/status/report-2023-04-2023-06/doceng.adoc +++ b/website/content/en/status/report-2023-04-2023-06/doceng.adoc @@ -1,102 +1,104 @@ //// Quarter: 2nd quarter of 2023 Prepared by: fernape Reviewed by: dbaio, carlavilla Last edit: $Date: 2023-06-25 15:11:08 +0200 (Sun, 25 Jun 2023) $ Version: $Id: doceng-2023-2nd-quarter-status-report.adoc 415 2023-06-25 13:11:08Z carlavilla $ //// === Documentation Engineering Team -Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj[] + -Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] + -Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[] +Links: + +link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj[] + +link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] URL: link:https://docs.freebsd.org/en/books/fdp-primer/[] + +link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] URL: link:https://www.freebsd.org/administration/#t-doceng[] Contact: FreeBSD Doceng Team The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see the link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. During this quarter: * fernape@ has been appointed as a new Doceng team member. * The package:www/gohugo[] port maintainership has been transferred to doceng@ since it is a critical part of our documentation infrastructure. This was agreed with the former maintainer. * Improvements to the translation workflow (described in the following sections). ==== Porter's Handbook link:https://cgit.freebsd.org/doc/commit/?id=634a34b7bb37650e4f8fcbea9fd7428b3f5b911a[`USES=nextcloud`] has been documented. ==== FDP Primer A new chapter focusing on Weblate has been added to the link:https://docs.freebsd.org/en/books/fdp-primer/weblate/[FreeBSD Documentation Project Primer for New Contributors]. This comprehensive chapter provides step-by-step guidance on joining the FreeBSD translators team, both for translating online on Weblate and offline. It offers valuable insights and practical suggestions for efficient translation, proofreading, and testing processes. Furthermore, this chapter equips contributors with the necessary knowledge to formally submit their translations to the documentation repository, ensuring a seamless integration of their work. ==== FreeBSD Translations on Weblate -Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblate[] + -Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/[] +Links: + +link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] URL: link:https://wiki.freebsd.org/Doc/Translation/Weblate[] + +link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/[] ===== Q2 2023 Status * 15 languages * 183 registered users * link:https://lists.freebsd.org/archives/freebsd-translators/2023-April/000111.html[New Weblate server] The FreeBSD Weblate instance now operates on a dedicated server, significantly improving its speed and enhancing the efficiency of translation work. Our heartfelt appreciation goes to ebrandi@ for providing this hardware upgrade. ===== 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%) * Indonesian (id) (progress: 1%) * Italian (it) (progress: 5%) * Korean (ko) (progress: 32%) * Norwegian (nb-no) (progress: 1%) * Persian (fa-ir) (progress: 3%) * Polish (progress: 1%) * Portuguese (pt-br) (progress: 22%) * Sinhala (si) (progress: 1%) * Spanish (es) (progress: 33%) * 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. ==== FreeBSD Handbook working group Contact: Sergio Carlavilla link:https://reviews.freebsd.org/D40546[The Network chapter is being reworked]. ==== FreeBSD Website Revamp - WebApps working group Contact: Sergio Carlavilla Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components. FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21. The work is divided into four phases: . Redesign of the Documentation Portal + Create a new design, responsive and with global search. (_Complete_) . Redesign of the Manual Pages on web + Scripts to generate the HTML pages using mandoc. (_Complete_) Public instance on https://man-dev.FreeBSD.org . Redesign of the Ports page on web + Ports scripts to create an applications portal. (_Work in progress_) . Redesign of the FreeBSD main website + New design, responsive and dark theme. (_Work in progress_) diff --git a/website/content/en/status/report-2023-04-2023-06/ifapi.adoc b/website/content/en/status/report-2023-04-2023-06/ifapi.adoc index 4c2f62233a..8a9b22a242 100644 --- a/website/content/en/status/report-2023-04-2023-06/ifapi.adoc +++ b/website/content/en/status/report-2023-04-2023-06/ifapi.adoc @@ -1,17 +1,17 @@ === Network Interface API (IfAPI) -Links: + -link:https://wiki.freebsd.org/projects/ifnet[Original project page] URL: link:https://wiki.freebsd.org/projects/ifnet +Link: + +link:https://wiki.freebsd.org/projects/ifnet[Original project page] URL: link:https://wiki.freebsd.org/projects/ifnet[] Contact: Justin Hibbits Started back in 2014, the IfAPI (formerly DrvAPI) goal is to hide the man:ifnet[9] structure from network drivers. Instead, all accesses to members will go through accessor functions. This allows the network stack to be changed without recompiling drivers, as well as potentially allowing a single driver to support multiple versions of FreeBSD. As of now this goal has been achieved in the base system, but several ports need to be updated to use the IfAPI. There is a tool to automate most of the conversion, in [.filename]#tools/ifnet/convert_ifapi.sh#. Documentation is also forthcoming, but could use help on that. man:ifnet[9] needs a lot of cleanup, as even some information in it currently is out of date. Sponsor: Juniper Networks, Inc. diff --git a/website/content/en/status/report-2023-04-2023-06/kboot.adoc b/website/content/en/status/report-2023-04-2023-06/kboot.adoc index 37d0f524c1..c24745351d 100644 --- a/website/content/en/status/report-2023-04-2023-06/kboot.adoc +++ b/website/content/en/status/report-2023-04-2023-06/kboot.adoc @@ -1,56 +1,56 @@ === FreeBSD support on LinuxBoot Contact: Warner Losh Links: + -link:https://www.linuxboot.org/[LinuxBoot Project] URL: link:https://www.linuxboot.org/[]+ +link:https://www.linuxboot.org/[LinuxBoot Project] URL: link:https://www.linuxboot.org/[] + link:https://docs.google.com/presentation/d/1N5Jp6XzYWv9Z9RhhETC-e6tFkqRHvp-ldRDW_9h2JCw/edit?usp=sharing[BSDCan 2023 kboot talk slides] URL: link:https://docs.google.com/presentation/d/1N5Jp6XzYWv9Z9RhhETC-e6tFkqRHvp-ldRDW_9h2JCw/edit?usp=sharing[] LinuxBoot is an effort to create a clean, robust, auditable and repeatable boot firmware. What originally started as a specific project at Google has grown to encompass any boot environment that uses Linux to launch the final operating system. Many platforms now support this environment, and in some cases it is the only available boot environment. In addition, some embedded boxes have a LinuxBoot environment hard-coded that is quite hard to change, and being able to reboot into FreeBSD is desirable. The old Sony PlayStation 3 port used a boot loader called 'kboot' to boot the FreeBSD port from its Linux kernel (all predating the LinuxBoot project). That code has been greatly expanded, made generic with easily replaceable per-architecture plug ins. The normal FreeBSD [.filename]#/boot/loader# is built as a Linux binary that reads in the FreeBSD kernel, modules and tunables. It places them into memory as if it were running in a pre-boot environment, then loads that image into the Linux kernel with man:kexec_load[2] and does a special reboot to that image. For UEFI-enabled systems, it passes the UEFI memory table and pointer to UEFI runtime services to the new kernel. It supports loading files from the host's filesystem, from any man:loader[8]-supported filesystem on the host's block devices (including pools that span multiple devices), from ram disk images and from files downloaded over the network. Any mix of these is available. So, for example, configuration overrides can be loaded from the host's filesystem whilst the kernel loads from dedicated storage (say NVME) or a ram disk image. It supports a host console running over stdin/stdout. It supports explicit locations such as `/dev/nvme0ns1:/boot/loader/gerbil.conf` for where to load filesystems from. It supports ZFS boot environments, including the boot-once feature. Additional details about kboot, what it supports and some general background can be found in Warner's BSDcan talk (slides linked above). FreeBSD/aarch64 now can boot from Linux in a LinuxBoot environment, with support and functionality comparable to man:loader.efi[8]. Memory layout passed in for GICv3 workarounds. Need patch for aarch64 kernel for the GICv3 workaround (link:https://reviews.freebsd.org/D40902[]). FreeBSD/amd64 support is in progress and is maybe 80% done. The amd64 boot environment places more requirements on the boot loader to provide data for the kernel than aarch64, due to amd64 being an older port. All sources for data in the BIOS environment had to be provided by the boot loader since the kernel had no access to them from long mode. While UEFI and ACPI provide ways for the kernel to get this data, much of the data must still be provided by the boot loader. The kernel panics during initialization since all these prerequisites have not been discovered and implemented. PowerPC builds, but nothing more of its state is known. Attempts to acquire a suitable Playstation 3 proved to be too time consuming for the author. ==== Help Needed 1. man:loader.kboot[8] needs to be written. It should document how to use [.filename]#loader.kboot#, how to create images, and the use cases that work today. -1. Finish amd64 support. -1. The current elf arch-specific metadata code is copied from efi. +2. Finish amd64 support. +3. The current elf arch-specific metadata code is copied from efi. Unifying the kboot and efi copies is needed. While they are mostly the same, sharing is complicated by remaining compile-time differences. In addition, the build infrastructure makes sharing awkward. -1. It would be nice to add riscv64 support. -1. PowerPC testing (it has been untested since the refactoring started). -1. Creating a script to repackage EDK-II image (say, from QEMU) as a linux-boot image with a Linux kernel built on FreeBSD for CI testing. -1. Testing it from the coreboot LinuxBoot. +4. It would be nice to add riscv64 support. +5. PowerPC testing (it has been untested since the refactoring started). +6. Creating a script to repackage EDK-II image (say, from QEMU) as a linux-boot image with a Linux kernel built on FreeBSD for CI testing. +7. Testing it from the coreboot LinuxBoot. Sponsored by: Netflix, Inc diff --git a/website/content/en/status/report-2023-04-2023-06/linuxulator.adoc b/website/content/en/status/report-2023-04-2023-06/linuxulator.adoc index d11716626b..a359e0d1da 100644 --- a/website/content/en/status/report-2023-04-2023-06/linuxulator.adoc +++ b/website/content/en/status/report-2023-04-2023-06/linuxulator.adoc @@ -1,19 +1,19 @@ === Linux compatibility layer update Links: + link:https://wiki.freebsd.org/Linuxulator[Linuxulator status Wiki page] URL: link:https://wiki.freebsd.org/Linuxulator[] + link:https://wiki.freebsd.org/LinuxApps[Linux app status Wiki page] URL: link:https://wiki.freebsd.org/LinuxApps[] Contact: Dmitry Chagin The goal of this project is to improve FreeBSD's ability to execute unmodified man:linux[4] binaries. As of gitref:cbbac5609115[repository=src], preserving an fpu xsave state across signal delivery on amd64 is implemented. That makes it possible to run modern golang with preemptive scheduler on. -The new facility to specify an alternate ABI root path was added to the man:namei[9]. +The new facility to specify an alternate ABI root path was added to man:namei[9]. Previously, to dynamically reroot lookups, every man:linux[4] syscall where path names translation is needed required a bit of ugly code and used `kern_alternate_path()` which does not properly resolve symlinks with leading `/` in the target. For now a non-native ABI (i.e., man:linux[4]) uses one call to `pwd_altroot()` during exec-time into that ABI to specify its root directory (e.g., [.filename]#/compat/ubuntu#) and forget about path names translation. That makes possible chroot into the Ubuntu compat without having to fix such symlinks by hand. In total, over 10 bugs were fixed; glibc-2.37 tests suite reports less than 70 failed tests. diff --git a/website/content/en/status/report-2023-04-2023-06/pf.adoc b/website/content/en/status/report-2023-04-2023-06/pf.adoc index a0fb75257f..0e572983cf 100644 --- a/website/content/en/status/report-2023-04-2023-06/pf.adoc +++ b/website/content/en/status/report-2023-04-2023-06/pf.adoc @@ -1,45 +1,45 @@ === Pf Improvements Links: + link:https://reviews.freebsd.org/D40911[D40911] URL: link:https://reviews.freebsd.org/D40911[] + link:https://reviews.freebsd.org/D40861[D40861] URL: link:https://reviews.freebsd.org/D40861[] + link:https://reviews.freebsd.org/D40862[D40862] URL: link:https://reviews.freebsd.org/D40862[] + link:https://reviews.freebsd.org/D40863[D40863] URL: link:https://reviews.freebsd.org/D40863[] + link:https://reviews.freebsd.org/D40864[D40864] URL: link:https://reviews.freebsd.org/D40864[] + link:https://reviews.freebsd.org/D40865[D40865] URL: link:https://reviews.freebsd.org/D40865[] + link:https://reviews.freebsd.org/D40866[D40866] URL: link:https://reviews.freebsd.org/D40866[] + link:https://reviews.freebsd.org/D40867[D40867] URL: link:https://reviews.freebsd.org/D40867[] + link:https://reviews.freebsd.org/D40868[D40868] URL: link:https://reviews.freebsd.org/D40868[] + link:https://reviews.freebsd.org/D40869[D40869] URL: link:https://reviews.freebsd.org/D40869[] + link:https://reviews.freebsd.org/D40870[D40870] URL: link:https://reviews.freebsd.org/D40870[] Contact: Kajetan Staszkiewicz + Contact: Naman Sood + Contact: Kristof Provost man:pf[4] is one of the firewalls included in FreeBSD, and is probably the most popular. pf was created by the OpenBSD project and subsequently ported to FreeBSD. ==== Backport OpenBSD Syntax Kajetan introduced the OpenBSD syntax of "scrub" operations in "match" and "pass" rules. Existing rules remain supported, but now OpenBSD style "scrub" configuration is also supported. ==== pfsync Protocol Versioning The man:pfsync[4] protocol version can now be configured, allowing for protocol changes while still supporting state synchronisation between disparate kernel versions. The primary benefit is to allow protocol changes enabling new functionality. ==== pfsync: Transport over IPv6 pfsync traffic can now be carried over IPv6 as well. Naman finished the work started by Luiz Amaral. ==== SCTP There is work in progress to support SCTP in pf. That support includes filtering on port numbers, state tracking, pfsync failover and returning ABORT chunks for rejected connections. -Sponsor: InnoGames GmbH -Sponsor: Orange Business Services +Sponsor: InnoGames GmbH + +Sponsor: Orange Business Services + Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-04-2023-06/portmgr.adoc b/website/content/en/status/report-2023-04-2023-06/portmgr.adoc index 1b1961b9b0..8e420d374d 100644 --- a/website/content/en/status/report-2023-04-2023-06/portmgr.adoc +++ b/website/content/en/status/report-2023-04-2023-06/portmgr.adoc @@ -1,29 +1,29 @@ === Ports Collection Links: + link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[] + link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] + link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[] + link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] + link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[] Contact: René Ladan + Contact: FreeBSD Ports Management Team The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. -Below is what happened in the last quarter. +elow is what happened in this quarter. Currently there are just over 34,400 ports in the Ports Tree. There are currently 3,019 open ports PRs of which 746 are unassigned. -The last quarter saw 10,439 commits on the `main` branch by 151 committers and 745 commits on the `2023Q2` branch by 55 committers. +This quarter saw 10,439 commits on the `main` branch by 151 committers and 745 commits on the `2023Q2` branch by 55 committers. Compared to the previous quarter, this means a slight increase in the number of ports, a tiny decrease in the number of open PRs, and a fair increase in the number of ports commits. During this quarter, we welcomed back Tom Judge (tj@) and said goodbye to Steve Wills (swills@). Steve was also on portmgr. As part of the portmgr lurker program, we welcomed Ronald Klop (ronald@), Renato Botelho (garga@), and Matthias Andree (mandree@). -Portmgr has resumed work on introducing sub-packages into the Tree, but various things still needs to be fleshed out. +Portmgr has resumed work on introducing sub-packages into the Tree, but various things still need to be fleshed out. On the software side, pkg was updated to 1.19.2, Firefox to 114.0.2, Chromium to 114.0.5735.198, and KDE Gear to 23.04.2. -During the last quarter, antoine@ ran 23 exp-runs to test package updates, bump CPU_MAXSIZE to 1024, fix armv7 failures for devel/cmake-core and add --auto-features=enabled to USES=meson +During this quarter, antoine@ ran 23 exp-runs to test package updates, bump CPU_MAXSIZE to 1024, fix armv7 failures for devel/cmake-core and add --auto-features=enabled to USES=meson Lastly, the Ports Tree was updated to support LLVM 16 and OpenSSL 3 in FreeBSD-CURRENT. diff --git a/website/content/en/status/report-2023-04-2023-06/simd.adoc b/website/content/en/status/report-2023-04-2023-06/simd.adoc index 84aa1269a3..682724a37a 100644 --- a/website/content/en/status/report-2023-04-2023-06/simd.adoc +++ b/website/content/en/status/report-2023-04-2023-06/simd.adoc @@ -1,23 +1,23 @@ === SIMD enhancements for amd64 Links: + link:https://reviews.freebsd.org/D40693[SIMD dispatch framework draft] URL: link:https://reviews.freebsd.org/D40693[] + -link:http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt[Project proposal] URL: link:http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt +link:http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt[Project proposal] URL: link:http://fuz.su/~fuz/freebsd/2023-04-05_libc-proposal.txt[] Contact: Robert Clausecker SIMD instruction set extensions such as SSE, AVX, and NEON are ubiquitous on modern computers and offer performance advantages for many applications. The goal of this project is to provide SIMD-enhanced versions of common libc functions (mostly those described in man:string[3]), speeding up most C programs. For each function optimised, up to four implementations will be provided: * a *scalar* implementation optimised for amd64, but without any SIMD usage, * a *baseline* implementation using SSE and SSE2 or alternatively an *x86-64-v2* implementation using all SSE extensions up to SSE4.2, * an *x86-64-v3* implementation using AVX and AVX2, and * an *x86-64-v4* implementation using AVX-512F/BW/CD/DQ. Users will be able to select which level of SIMD enhancements to use by setting the `AMD64_ARCHLEVEL` environment variable. While the current project only concerns amd64, the work may be expanded to other architectures like arm64 in the future. Sponsor: The FreeBSD Foundation