diff --git a/website/content/en/status/_index.adoc b/website/content/en/status/_index.adoc --- a/website/content/en/status/_index.adoc +++ b/website/content/en/status/_index.adoc @@ -21,6 +21,10 @@ These status reports may be reproduced in whole or in part, as long as the source is clearly identified and appropriate credit given. +== 2025 + +* link:report-2025-01-2025-03/[January, 2025 - March, 2025] + == 2024 * link:report-2024-10-2024-12/[October, 2024 - December, 2024] diff --git a/website/content/en/status/report-2025-01-2025-03/_index.adoc b/website/content/en/status/report-2025-01-2025-03/_index.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/_index.adoc @@ -0,0 +1,232 @@ +--- +title: "FreeBSD Status Report First Quarter 2025" +sidenav: about +--- + += Introduction +:doctype: article +:toc: macro +:toclevels: 2 +:icons: font +:!sectnums: +:source-highlighter: rouge +:experimental: +:reports-path: content/en/status/report-2025-01-2025-03 + +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[] + +''' + +include::{reports-path}/bugmeister.adoc[] + +''' + +include::{reports-path}/srcmgr.adoc[] + +''' + +[[projects]] +== Projects + +Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. + +''' + +include::{reports-path}/foundation-infrastructure-modernization.adoc[] + +''' + +include::{reports-path}/foundation-laptop.adoc[] + +''' + +include::{reports-path}/foundation-security.adoc[] + +''' + +include::{reports-path}/foundation-security-audit.adoc[] + +''' + +include::{reports-path}/framework.adoc[] + +''' + +[[userland]] +== Userland + +{userland-desc} + +''' + +include::{reports-path}/jailmeta.adoc[] + +''' + +[[kernel]] +== Kernel + +{kernel-desc} + +''' + +include::{reports-path}/audio.adoc[] + +''' + +include::{reports-path}/drm-drivers.adoc[] + +''' + +include::{reports-path}/suspend.adoc[] + +''' + +include::{reports-path}/syzkaller.adoc[] + +''' + +include::{reports-path}/wireless-iwx.adoc[] + +''' + +[[architectures]] +== Architectures + +{architectures-desc} + +''' + +include::{reports-path}/pinephone.adoc[] + +''' + +[[cloud]] +== Cloud + +{cloud-desc} + +''' + +include::{reports-path}/buildpacks.adoc[] + +''' + +include::{reports-path}/ec2.adoc[] + +''' + +[[documentation]] +== Documentation + +{documentation-desc} + +''' + +include::{reports-path}/doceng.adoc[] + +''' + +include::{reports-path}/wiki_status_report_2025Q1.adoc[] + +''' + +[[ports]] +== Ports + +{ports-desc} + +''' + +include::{reports-path}/bhyvemgr.adoc[] + +''' + +include::{reports-path}/container-orchestration.adoc[] + +''' + +include::{reports-path}/gcc.adoc[] + +''' + +include::{reports-path}/ipv6-support-on-ng_ksocket.adoc[] + +''' + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/openbgpd-fix-fib-handling.adoc[] + +''' + +include::{reports-path}/openjdk-status-2025Q1.adoc[] + +''' + +include::{reports-path}/wazuh.adoc[] + +''' + +[[third-Party-Projects]] +== Third Party Projects + +{third-Party-Projects-desc} + +include::{reports-path}/cfc.adoc[] + +''' + +include::{reports-path}/discord.adoc[] + +''' + +include::{reports-path}/framework-kmod.adoc[] + +''' + +include::{reports-path}/ldwg.adoc[] + +''' + +include::{reports-path}/pot.adoc[] diff --git a/website/content/en/status/report-2025-01-2025-03/appjail.adoc b/website/content/en/status/report-2025-01-2025-03/appjail.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/appjail.adoc @@ -0,0 +1,16 @@ +=== Container orchestration: Overlord, Director and AppJail + +Links: + +link:https://github.com/DtxdF/AppJail[AppJail on Github] URL: link:https://github.com/DtxdF/AppJail[] + +link:https://github.com/DtxdF/Director[Director on Github] URL: link:https://github.com/DtxdF/Director[] +link:https://github.com/DtxdF/Overlord[Overlord on Github] URL: link:https://github.com/DtxdF/Overlord[] + +Contact: Jes??s Daniel Colmenares Oviedo + +**AppJail** is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. + +**Director** is a tool for running multi-jail environments on AppJail using a simple YAML specification. A Director file is used to define how one or more jails that make up your application are configured. Once you have a Director file, you can create and start your application with a single command: `appjail-director up`. + +**Overlord** is a fast, distributed orchestrator for FreeBSD jails oriented to GitOps. You define a file with the service intended to run on your cluster and deployment takes seconds to minutes. This orchestration tool uses AppJail, Director and can even create VMs with vm-bhyve, but as its philosophy is ???deploy using code??? you can create a single file once and deploy many times. Through a tree chaining system Overlord deploys jails on connected systems sharing their resources almost infinitely. See the link:https://github.com/DtxdF/Overlord/wiki[wiki] for articles that use Overlord. + +Sponsor: https://www.patreon.com/appjail diff --git a/website/content/en/status/report-2025-01-2025-03/cfc.adoc b/website/content/en/status/report-2025-01-2025-03/cfc.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/cfc.adoc @@ -0,0 +1,44 @@ +=== Chinese FreeBSD Community (CFC) + +link:https://bsdcn.org/[Chinese FreeBSD Community (CFC)] URL: link:https://bsdcn.org/[] + +Community member count: QQ group 249 members, WeChat group 175 members + +==== FreeBSD-Ask + +Links: + +link:https://github.com/FreeBSD-Ask/FreeBSD-Ask[FreeBSD-Ask on GitHub] URL: link:https://github.com/FreeBSD-Ask/FreeBSD-Ask[] + +link:https://book.bsdcn.org/[FreeBSD-Ask on Website] URL: link:https://book.bsdcn.org/[] + +Contact: ykla + +*FreeBSD-Ask* is an open-source FreeBSD introductory guide written in Simplified Chinese, initiated by ykla from the Chinese FreeBSD Community (CFC). *FreeBSD-Ask* was established on March 14, 2021 + +Updates in this quarter: + +* Added: + * Installing Budgie + * bsdconfig System Configuration Tool + * Installing Fluxbox + * Installing IceWM + * Prometheus Monitoring Deployment + * Fail2Ban (Based on IPFW, PF, IPF) + * Installing Window Maker + * Manual Dual-Boot Installation (Installing FreeBSD First) + * Installing FreeBSD - Based on Apple M1 & Parallels Desktop 20 + * Command Line Basics + * Zabbix Monitoring (Based on PostgreSQL) + * etc. + +* Rewritten: + * Pure-FTPd (Based on MySQL) + * ProFTPD (Based on MySQL) + * vsftpd + + +* Introduced several GitHub Actions, such as automatic PDF generation, dead link checking, etc. + + +As always, feedback and patches are welcome. + +Sponsors: Chinese FreeBSD Community (CFC) diff --git a/website/content/en/status/report-2025-01-2025-03/discord.adoc b/website/content/en/status/report-2025-01-2025-03/discord.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/discord.adoc @@ -0,0 +1,50 @@ +=== FreeBSD Discord Server + +Links: + +link:https://wiki.freebsd.org/Discord/DiscordServer[Discord Server] URL: link:https://wiki.freebsd.org/Discord/DiscordServer[] + +Contact: setesh.strong@gmail.com + +The FreeBSD Community Discord server has grown to over 5.3K members, with over 3K members active in the last month. To help support our community’s health and pursue growth in project contribution and engagement, the BSDlabs group developed the Helper program, more than two years ago now. +After several phases of growth, we have reached the point where the team has thrived enough that it has become necessary to divide it into three distinct functional teams. + +Our community health and culture helpers (@moderators) are led by Alexander Vereeken. +Our newcomer onboarding and training helpers (@mentors) are led by Alexander Ziaee. +Our event organizer and outreach helpers (@organizers) are led by Ahmad Abdulla. + +Since the creation of the new teams, all of our helpers have been hard at work, driving growth within the areas of their remit within the program. +We are proud to share some of the outcomes of their efforts with you, as well as several of the areas of focus and objectives we will tackle in the upcoming quarter. + +Antranig Vartanian led the development of our recurring series of Ask the Greybeards AMAs (Ask Me Anything) with the support of other veteran sysadmins and developers. +This recurring event provides an opportunity for users and those still gaining mastery of our platform to meet and learn from the depth of experience our community offers. +Special thanks to Michael Dexter and many others for their engagement and support of this event. Your expertise and skills help nurture the future of our ecosystem. + +Significant progress into onboarding new contributors has occurred through the efforts of the newcomer helper team under Alexander Ziaee’s leadership. +His work has brought newly increased activity to our docs tree. + +At the request of Warner Losh, we have created a workspace for #google-summer-of-code on the server. +his space provides a location for those engaged with GSoC to ask questions and receive feedback and assistance. +In further pursuit of our desire to bridge between silos, we are in the process of establishing a matterbridge bot. +This will serve to connect with the #freebsd-gsoc IRC channel, as well as other potential links in the future with FreeBSD’s IRC and Matrix communities. + +We are proud to welcome developers working on FreeBSD’s wifi stack to our server. +We have created the #wifi-hacking workspace to facilitate their efforts. +pecial thanks to Adrian Chadd for bringing this opportunity to us, and leading the way in the thriving activity in this workspace. + +We are currently in the process of developing our new Co-op Study Club, driven by the leadership of Jesper Schmitz Mouridsen. +This will provide members of our community with the opportunity to build their skills in side-by-side study, under the guidance of our newcomer helper team. +As a project driven study group, it will develop our members’ passions into strengths, while building comfort and familiarity with contributing to the project via porting, src development, and documentation testing and patching. +Experienced mentorship will be on hand to provide learning resources for those who join this study group, answer questions that cannot be answered by peer support, and aiding in overcoming blockers. +Our objective is to provide a roadmap and environment for achieving excellence as both developers and FreeBSD contributors. + +Thanks to the efforts of community helper Jessica Hawkwell, with the support of events team leader Ahmad Abdulla, we’ve seen the addition of a #foss-ecosystem channel. +This development marks the beginning of the process of bridging between the various silos, both within the FreeBSD community, and in the larger FOSS ecosystem. +If you want us to add a link to your segment of the community and it’s not already contained in our directory in this channel, please reach out to us. + +In addition to the existing tools afforded by Discord for our server, we are currently in the process of upgrading and expanding our infrastructure. +This effort focuses on ensuring the availability of Discord bot infrastructure and tooling, as well as restoring etherpad and dpaste functionality for collaboration. +We seek to improve support for all of the dedicated developers within the workspaces of our community. + +If you’re a member of the FreeBSD ecosystem and haven’t yet connected to our Discord presence, we invite you to do so via the invite link available on the wiki at the top of this report. +If you have experience or passion for any of the areas of our current helper teams, or a passion for Discord bot infrastructure development, we would love to have you on our teams. +We invite you to contact us via the above contact email, or by sending a DM on Discord (@setesh.strong). diff --git a/website/content/en/status/report-2025-01-2025-03/framework-kmod.adoc b/website/content/en/status/report-2025-01-2025-03/framework-kmod.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/framework-kmod.adoc @@ -0,0 +1,31 @@ +=== Framework Kernel Module + +Links: + +link:https://github.com/christian-moerz/framework-kmod[GitHub] URL: https://github.com/christian-moerz/framework-kmod[] + +link:https://bugs.freebsd.org/285448[Bugzilla] URL: https://bugs.freebsd.org/285448[] + +Contact: Chris Moerz + +The development of the `framework-kmod` kernel module originated from discussions and collaborative efforts within the link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[FreeBSD Laptop and Desktop Workgroup (LDWG)]. +This module addresses a specific need for dynamic screen dimming functionality, particularly suited for environments where full-featured desktop environments are not in use. + +The primary feature of the framework-kmod kernel module is to dynamically dim the screen when the computer is not in use and to restore brightness upon detecting user activity. +This functionality is designed to enhance power efficiency and user experience, especially in minimalistic setups. + +By default, the module dims the screen very aggressively, dimming it after approximately one second of inactivity. +This behavior ensures immediate power savings but may need adjustment based on user preferences. +The module's settings can be customized through sysctls, allowing users to tailor the behavior to their needs. +Users can set different brightness levels for the dimmed and bright states, adjust the length of time that needs to pass without any input signal before dimming the screen, and apply different settings depending on whether the laptop is running on a power outlet or battery. +Brightness levels can also be adjusted through the use of the keyboard's brightness control keys. + +The module tracks input signals through man:evdev[4]. +If no input is detected within the set timeout period, the screen brightness is reduced. +Upon detecting user input, the brightness is immediately restored to the previous level. +The module requires drm-kmod drivers to be loaded in advance, ensuring compatibility with the necessary graphics drivers. + +The framework-kmod is not a general-purpose screen dimming driver. +It is specifically designed for use with tty consoles or simple window managers like suckless' dwm or i3. +Users of full-featured desktop environments like Gnome or KDE are advised to use the built-in screen dimming functions provided by those environments. + +The development of this module was driven by the needs identified during LDWG calls, highlighting the collaborative nature of the workgroup. +A link:https://bugs.freebsd.org/285448[port of the framework-kmod] has been submitted, making it accessible for broader use and further development by the FreeBSD community. diff --git a/website/content/en/status/report-2025-01-2025-03/gcc.adoc b/website/content/en/status/report-2025-01-2025-03/gcc.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/gcc.adoc @@ -0,0 +1,20 @@ +=== GCC on FreeBSD + +Links: + +link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] + +link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[] + +link:https://gcc.gnu.org/gcc-12/[GCC 12 release series] URL: link:https://gcc.gnu.org/gcc-12/[] + +link:https://gcc.gnu.org/gcc-13/[GCC 13 release series] URL: link:https://gcc.gnu.org/gcc-13/[] + +link:https://gcc.gnu.org/gcc-14/[GCC 14 release series] URL: link:https://gcc.gnu.org/gcc-14/[] + +Contact: Lorenzo Salvadore + +The link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281091[exp-run to update GCC default version from 13 to 14] has been suspended. +Indeed it has been noticed that FreeBSD 13.4 lacks symbols that are used by GCC 14 for linking, please see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284499#c0 for a more detailed explanation. +The symbols are however already present in higher FreeBSD version. +Since FreeBSD 13.4 is expected to go out of support soon (on June 30th), it has been decided that it is preferable to suspend the exp-run until then. +I plan to put it back on track on July 1st. + +In the meantime, work is being done on bugs. +Bugs link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276070[276070] and https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284441[284441] have been fixed. +At the time this report is written, some bugs are being discussed addressing special values of the CPUTYPE variable, please see for example https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285711[285711]. diff --git a/website/content/en/status/report-2025-01-2025-03/intro.adoc b/website/content/en/status/report-2025-01-2025-03/intro.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/intro.adoc @@ -0,0 +1,12 @@ +As we step into a new year, the FreeBSD community continues its work with unwavering speed, intent, and purpose. +With BSDcan approaching in Q2, we are excited about the promising developments and news on the horizon. + +The first quarter has been remarkable, with numerous reports highlighting progress across various areas. +Engaging with the community through forums, mailing lists, and conversations has revealed to me more advancements than can ever be captured in a single quarterly report. + +We extend our heartfelt thanks to everyone who submitted reports and helped raise awareness of our activities. +Your contributions are invaluable in showcasing our collective efforts. + +Let's build on the success of 2024 and make this the best year yet for FreeBSD and our community! + +Chris Moerz, on behalf of the Status Team. diff --git a/website/content/en/status/report-2025-01-2025-03/ldwg.adoc b/website/content/en/status/report-2025-01-2025-03/ldwg.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/ldwg.adoc @@ -0,0 +1,39 @@ +=== Laptop and Desktop Work Group (LDWG) + +Links: + +link:https://lists.freebsd.org/archives/freebsd-desktop/[Desktop mailing list] URL: link:https://lists.freebsd.org/archives/freebsd-desktop/[] + +link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[Wiki Page] URL: link:https://wiki.freebsd.org/LaptopDesktopWorkingGroup[] + +link:https://www.youtube.com/watch?v=U9SdSkfqH9U&list=PLugwS7L7NMXwHlYfDKNMXwJrjFrYVA9ca[YouTube] URL: https://www.youtube.com/watch?v=U9SdSkfqH9U&list=PLugwS7L7NMXwHlYfDKNMXwJrjFrYVA9ca[] + +Contact: Chris Moerz + +The FreeBSD Laptop and Desktop Workgroup (LDWG) has continued its dedicated efforts throughout the first quarter. + +LDWG holds monthly meetings to discuss the state of FreeBSD on laptops and desktops and to review progress. These meetings are scheduled every second Monday at 5 PM UTC. The next meeting is set for Wednesday, May 14, at 10 AM PST / 1 PM EDT / 5 PM UTC. + +A survey has been initiated to explore alternative calling options that would enable participants from APAC regions to join the calls more conveniently. + +All calls are now available on YouTube, allowing broader access for interested parties to stay updated on the group's activities. + +The group's participants have made notable advancements in several areas: + +* ***Audio Improvements:*** Enhancements have been made to improve audio quality. +* ***Documentation:*** Significant improvements have been made to the documentation, making it more comprehensive and user-friendly. +* ***Wireless Speed and Stability:*** Efforts have led to better wireless speed and stability, enhancing overall connectivity. + +All activities are meticulously documented on the group's worksheet. +LDWG encourages anyone interested in contributing to add their name to the worksheet. +If there is any planned or ongoing work, participants are welcome to include it in the worksheet. + +The established LDWG's call agenda includes: + +* ***News Updates:*** Sharing news around FreeBSD on desktops and laptops, including work not otherwise covered by the workgroup. +* ***FreeBSD Foundation Laptop Project:*** The project continues to progress well, with reports highlighting the need for volunteers to support testing efforts and the formation of a UX test group. +* ***Project Reviews and Announcements:*** Reviewing and presenting progress, announcing new projects, and calling for actions. +* ***Q&A Sessions:*** Providing a platform to ask questions about ongoing projects; serving as a rallying point to organize developers, users, and stakeholders on focus areas. + +LDWG is working to improve the call's agenda in collaboration with the Enterprise Working Group. Both groups face the challenge of having more areas of interest and work streams than available resources. Therefore, a process is being developed to ensure that available time is spent on matters that have the required resources and attention. + +The group is open to anyone interested in the matter. We welcome anyone who wants to join the group and/or calls to do so. + +Hope to see you there! diff --git a/website/content/en/status/report-2025-01-2025-03/openjdk-status-2025Q1.adoc b/website/content/en/status/report-2025-01-2025-03/openjdk-status-2025Q1.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/openjdk-status-2025Q1.adoc @@ -0,0 +1,25 @@ +=== Improve OpenJDK on FreeBSD + +Links: + +link:https://freebsdfoundation.org/project/improving-openjdk-on-freebsd/[Project description] URL: https://freebsdfoundation.org/project/improving-openjdk-on-freebsd/[] + +link:https://github.com/freebsd/openjdk[Project repository] URL: https://github.com/freebsd/openjdk[] + +Contact: + +Harald Eilertsen + +FreeBSD Java mailing list + +The main goal of this project is to improve OpenJDK support on FreeBSD/amd64 and FreeBSD/arm64. + +Java is an important runtime environment for many high performance, critical enterprise systems. +Making sure Java based applications run correctly and efficiently on FreeBSD is important to ensure that FreeBSD will continue to be a viable and attractive platform for enterprises, as well as businesses and organizations of all sizes. + +We released https://cgit.freebsd.org/ports/commit/?id=aa17c509fe7c4a011e832bd1e67257cf5d0ebc81[a port for OpenJDK 23] for FreeBSD at the very end of last year, and have since then fixed an https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284503[issues with font management] and some other minor improvements. +We have also been following the development of OpenJDK 24 closely, and are just finishing a https://reviews.freebsd.org/D49354[port for it] that that should be available by the time this status update is published. + +In parallel with porting OpenJDK 24 work has been ongoing on moving the BSD port also to the mainline OpenJDK development tree, and the first patches has been accepted upstream. Currently the focus is on reviving the https://openjdk.org/projects/bsd-port/[OpenJDK BSD port project], as well as getting a separate project repository set up under it. + +A lot of the work of this quarter has gone into cleaning up the patches of the BSD port based on the development in the upstream mainline and jdk24 branches. Also a lot of time has been spent on improving the results of the built in test suites (jtreg and gtest) on FreeBSD. This has involved both changes to the tests themselves, but also various parts of the low level OpenJDK code. More work is needed to get the final few tests passing, especially on Aarch64, but compared to previous OpenJDK releases on FreeBSD the results have been improving. + +Finally, a significant amount of time has been spent on communicating and discussing how to approach the goal of integrating the BSD support in the mainline OpenJDK codebase. The OpenJDK project has been very open, welcoming and supportive of the effort, and seems more than willing to help make this happen in a good way. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2025-01-2025-03/pinephone.adoc b/website/content/en/status/report-2025-01-2025-03/pinephone.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/pinephone.adoc @@ -0,0 +1,35 @@ +=== Pinephone Pro Support + +Links: + +link:https://codeberg.org/Honeyguide/freebsd-pinephonepro[Repository on Codeberg] URL: link:https://codeberg.org/Honeyguide/freebsd-pinephonepro[] + +Contact: Toby Kurien + +The project to port FreeBSD over to the Pinephone Pro is progressing. The +aim of this project is to step by step support components of the Pinephone +Pro in FreeBSD so that the device one day might be usable as a highly +mobile FreeBSD device. + +In this quarter, console output to the screen was enabled, using EFI +framebuffer support. This requires using a specific version of U-boot that sets +up the EFI framebuffer, which FreeBSD's kernel is then able to use for output +while booting up. While this comes with limitations (like no hardware +acceleration), it is a big step forward in making FreeBSD usable on the +PinePhone Pro. To make it easier to try the current code changes out, a script +was added to the repository to create a flashable image for booting from an SD +card. This script downloads and patches a FreeBSD CURRENT mini-memstick image +with the custom device tree and kernel. The resulting image can then be copied +to an SD card using dd and booted up on the phone. See the repo for details. + +Work on enabling the USB port was started but has stalled and help is needed, +particularly from someone who understands the USB subsystem and can help move +this forward. Currently, some USB controllers are detected by FreeBSD but no +USB devices are visible, e.g. the internally connected modem. Help is also +needed to port the WiFi driver from Linux, which would be the same driver +needed for Raspberry Pi 3b+/4/5 (Broadcom 43455 wifi module connected via +SDIO). Anyone wanting to assist can contact me by e-mail. + +See the post on the FreeBSD Forum for more: +https://forums.freebsd.org/threads/porting-freebsd-to-pinephone-pro-help-needed.95948/ + +Sponsor: Honeyguide Group diff --git a/website/content/en/status/report-2025-01-2025-03/portmgr.adoc b/website/content/en/status/report-2025-01-2025-03/portmgr.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/portmgr.adoc @@ -0,0 +1,57 @@ +=== 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: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: Tobias C. Berner + +Contact: FreeBSD Ports Management Team + +The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. +Below is what happened in the last quarter. + +In the last quarter, we welcomed Austin Shafer (ashafer@) as a new ports committer, and welcomed back Eygene Ryabinkin (rea@) and Mark Linimon (linimon@). + +According to INDEX, there are currently 36,450 (up from 36,332) ports in the Ports Collection. +There are currently about 3,333 (down from 3,368) open ports PRs, of which 887 are unassigned. +The last quarter saw 10,733 (up from 10,640) commits by 158 (up from 155) committers on the main branch and 707 (down from 733) commits by 54 (down from 61) committers on the 2025Q1 branch. + +The most active committers to main were: + +* 3029 sunpoet@FreeBSD.org +* 1171 yuri@FreeBSD.org +* 358 vvd@FreeBSD.org +* 340 bofh@FreeBSD.org +* 313 rene@FreeBSD.org +* 297 jbeich@FreeBSD.org +* 288 eduardo@FreeBSD.org +* 243 pkubaj@FreeBSD.org +* 223 fuz@FreeBSD.org +* 212 diizzy@FreeBSD.org + +A lot has happened in the ports tree in the last three months, an excerpt of the major software upgrades are: + +- pkg 2.1.0 +- Default version of Lazarus switched to 3.8.0 (aarch64 at 4.99) +- Chromium 134.0.6998.165 +- Electron 31 removed, Electron 34 added +- Firefox 137.0-rc2 +- Firefox-esr 128.9.0-rc2 +- Gnome desktop 44.1 +- KDE Frameworks 6.12.0 +- KDE Plasma 6.3.3 +- KDE Gear 24.12.3 +- Qt6 6.8.3 +- Python 3.8 removed +- Ruby 3.1 removed +- Ruby 3.3.7 +- Rust 1.85.1 +- SDL 2.32.2 +- SDL 3.2.8, added to USES=sdl +- Wine 10.0 + +One `USES` was removed: qca + +During the last quarter, pkgmgr@ ran 20 exp-runs to test infrastructure changes and various ports upgrades. diff --git a/website/content/en/status/report-2025-01-2025-03/pot.adoc b/website/content/en/status/report-2025-01-2025-03/pot.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/pot.adoc @@ -0,0 +1,22 @@ +=== Containers and FreeBSD: Pot, Potluck and Potman + +Links: + +link:https://github.com/bsdpot[Pot organization on Github] URL: link:https://github.com/bsdpot[] + +Contact: Luca Pizzamiglio (Pot) + +Contact: Bretton Vine (Potluck) + +Contact: Michael Gmelin (Potman) + +Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad]. +Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad. + +During this quarter, there was a new link:https://github.com/bsdpot/pot/releases/tag/0.16.1[Pot release 0.16.1] which includes a number of minor fixes. The FreeBSD port was updated accordingly. + +Potluck got a new link:https://github.com/bsdpot/potluck/tree/master/onlyoffice-documentserver[OnlyOffice Documentserver] image that can be used together with the link:https://github.com/bsdpot/potluck/tree/master/nextcloud-nginx-nomad[Nextcloud] image. +Additionally, a large number of images have received improvements and bug fixes again, e.g. link:https://github.com/bsdpot/potluck/tree/master/nextcloud-spreed-signalling[Nextcloud Spreed], link:https://github.com/bsdpot/potluck/tree/master/grafana[Grafana], link:https://github.com/bsdpot/potluck/tree/master/vault[Vault] or link:https://github.com/bsdpot/potluck/tree/master/consul[Consul] and all images have been rebuilt for an updated base image. + +Last not least, we are in the process of moving the main repository to Codeberg with Github acting as a mirror. + +As always, feedback and patches are welcome. + +Sponsors: Nikulipe UAB, Honeyguide Group diff --git a/website/content/en/status/report-2025-01-2025-03/report.adoc b/website/content/en/status/report-2025-01-2025-03/report.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/report.adoc @@ -0,0 +1,22 @@ +=== Container orchestration: Overlord, Director and AppJail + +Links: + +link:https://github.com/DtxdF/AppJail[AppJail on Github] URL: link:https://github.com/DtxdF/AppJail[] + +link:https://github.com/DtxdF/Director[Director on Github] URL: link:https://github.com/DtxdF/Director[] + +link:https://github.com/DtxdF/Overlord[Overlord on Github] URL: link:https://github.com/DtxdF/Overlord[] + +Contact: Jesús Daniel Colmenares Oviedo + +**AppJail** is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behave like an application. + +**Director** is a tool for running multi-jail environments on AppJail using a simple YAML specification. +A Director file is used to define how one or more jails that make up your application are configured. +Once you have a Director file, you can create and start your application with a single command: `appjail-director up`. + +**Overlord** is a fast, distributed orchestrator for FreeBSD jails oriented to GitOps. +You define a file with the service intended to run on your cluster and deployment takes seconds to minutes. +This orchestration tool uses AppJail, Director and can even create VMs with vm-bhyve, but as its philosophy is "deploy using code", you can create a single file once and deploy many times. +Through a tree chaining system Overlord deploys jails on connected systems sharing their resources almost infinitely. +See the link:https://github.com/DtxdF/Overlord/wiki[wiki] for articles that use Overlord. + +Sponsor: https://www.patreon.com/appjail diff --git a/website/content/en/status/report-2025-01-2025-03/syzkaller.adoc b/website/content/en/status/report-2025-01-2025-03/syzkaller.adoc new file mode 100644 --- /dev/null +++ b/website/content/en/status/report-2025-01-2025-03/syzkaller.adoc @@ -0,0 +1,26 @@ +=== Syzkaller Improvement on FreeBSD + +Links: + +link:https://github.com/google/syzkaller[google/syzkaller] URL: link:https://github.com/google/syzkaller[] + + +Contact: Jian-Lin Li + +Contact: Li-Wen Hsu + +Syzkaller is an operating system kernel fuzzer that can look for vulnerabilities in the kernel. + +This project aims to improve the support of Syzkaller on FreeBSD. Based on the existing WiFi fuzzer designed for Linux, we drafted a WiFi fuzzer for FreeBSD. We planned to use wtap(4), a virtual wifi driver for testing, in order to support WiFi fuzzing. + +Some of the design details include: + +* Initialize wtap devices in Syzkaller before WiFi fuzzing +* Inject 802.11 frames via the existing ioctl interface provided by wtap +* Inject 802.11 frames via the Netlink interface, which is not supported by FreeBSD for now + +We haved developed a WiFi fuzzer using existing ioctl interface provided by wtap. One can check out the result in this link:https://github.com/estarriol43/syzkaller/tree/freebsd/frame-injection-v2[branch] + +I hope to introduce Netlink interface, which is adopted by the Syzkaller to inject 802.11 frames into Linux kernel, to FreeBSD to improve the compatibilities between Linux and FreeBSD. + +Sponsor: The FreeBSD Foundation + +Best Regards, +Jian-Lin \ No newline at end of file