diff --git a/website/content/en/status/report-2024-01-2024-03/bhyve.adoc b/website/content/en/status/report-2024-01-2024-03/bhyve.adoc index 44b96ae426..2de6c27dfe 100644 --- a/website/content/en/status/report-2024-01-2024-03/bhyve.adoc +++ b/website/content/en/status/report-2024-01-2024-03/bhyve.adoc @@ -1,72 +1,72 @@ === Bhyve Improvements Links: + link:https://callfortesting.org/[bhyve production users calls] URL: link:https://callfortesting.org[] link:https://wiki.freebsd.org/EnterpriseWorkingGroup[FreeBSD Wiki - Enterprise Working Group] URL: link:https://wiki.freebsd.org/EnterpriseWorkingGroup[] + link:https://wiki.freebsd.org/ChrisMoerz/bhyve_management[FreeBSD Wiki - EWG - bhyve and jails management tooling] URL: link:https://wiki.freebsd.org/ChrisMoerz/bhyve_management[] + link:http://static.bultmann.eu/s6-talk/#(1)[Jan Bramkamp's work on s6rc] URL:http://static.bultmann.eu/s6-talk/#(1)[] + -link:https://github.com/christian-moerz/vmstated[vmstated on Github] URL: link:https://github.com/christian-moerz/vmstated[] + +link:https://github.com/christian-moerz/vmstated[vmstated on GitHub] URL: link:https://github.com/christian-moerz/vmstated[] + link:https://www.youtube.com/watch?v=f60NCrunXyw[YouTube - vmstated explained] URL: link:https://www.youtube.com/watch?v=f60NCrunXyw[] Contact: Chris Moerz ==== Bhyve I/O Performance Measurements Participants of the weekly bhyve production users calls recently discussed bhyve's I/O performance. Various ways of measuring and comparing were brought up, however it was quickly clear that there is currently no formal analysis and report on this. So, we started this effort in the hopes of better understanding the various impacts of configuration options for a guest on its I/O performance. We created a set of shell scripts that harness a FreeBSD guest for running package:benchmarks/fio[] I/O performance measurements under various configurations. This allows us to compare multiple criteria like bandwidth, latency, IOPS, and more. So far, we are testing for * different storage backends (i.e. ahci-hd, nvme, virtio-blk) * different memory settings * different CPU pinning options * different block sizes for the backing storage * different block sizes for accessing virtual disks We are also pitting results for different CPU manufacturers against each other and contrasting guest vs host performance to better understand the performance impact of virtualization. We plan to continue discussing our results during Michael Dexter's weekly bhyve production users call - come join us if you are interested. We also hope to be able to present the results at EuroBSDCon in Q3. ==== Bhyve Virtual Machine Tooling Last year, Greg Wallace at the FreeBSD Foundation founded the Enterprise Working Group with the specific goal of addressing pain points of Enterprise users of FreeBSD. One of the work groups that emerged clustered around bhyve and jails management tooling. After collecting a set of desired features and functionality, one overarching key point for bhyve emerged: the desire to have configuration concepts and tooling for bhyve like the ones available for jails. While other desirable features were identified as well, i.e. TPM software emulation and snapshot/restore/host-migration, the conceptual tooling question won over those due to the lower degree of complexity and its clarity on goal and the path on how to take steps towards it. Technically, this means working out existing gaps around process supervision and virtual machine state management. First steps were taken by experimenting with existing frameworks (i.e. s6rc work by Jan Bramkamp) and eventually -- through discussions in the weekly bhyve production user's calls (organized by Michael Dexter) -- this led to a proof-of-concept implementation of "vmstated". Started as an experiment to better understand the problem space of process supervision and virtual machine state handling, vmstated is constructed of a daemon and vmstatedctl management utility. It is built with base-only tooling and libraries and leverages FreeBSD specific constructs like kqueue to minimize its resource impact. vmstated is configured via a UCL configuration file (similar to [.filename]#jails.conf#) and -- in combination with a man:bhyve_config|5] configuration file -- already provides highest flexibility in configuring virtual machines. vmstatedctl provides a jail-like command set to start, stop, and retrieve status information about guests. State transitions can easily be hooked via shell scripts and allow running additional commands for network or storage set up and tear down when relevant state changes occur. An initial release is already in ports as package:sysutils/vmstated[] and updates are pending commit; however, the newest version can be found on GitHub. We are considering expanding the work; we would also like to invite anyone interested to join us in this work! Patches, suggestions, feedback, etc. are all very much welcome! If you want to know more about our work, come join us at one of Michael Dexter's weekly bhyve production users calls or reach me mailto:freebsd@ny-central.org[by email]. ==== Documentation === We managed to update a few parts of the Handbook and Porter's Handbook (thanks to mailto:emaste@FreeBSD.org[Ed Maste], mailto:jrm@FreeBSD.org[Joseph Mingrone], mailto:pauamma@gundo.com[Pau Amma], and mailto:rgrimes@FreeBSD.org[Rodney W. Grimes]): * several improvements and expansions to the virtualization chapter in the FreeBSD Handbook ** using a man:bhyve_config|5] configuration file ** jailing bhyve ** experimental snapshot and restore feature ** setting up a Windows guest * we also have a review (link:https://reviews.freebsd.org/D43940[D43940]) up for an initial step to improving the bhyve man page ** this was intentionally started with a structural update first to separate the many `-s` flag options ** once this lands, we can move to a more widespread update to the overall content Feedback is obviously very welcome -- on the existing content as well as any additional content we should be looking into! diff --git a/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc b/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc index 87cf09e0a1..6fbd95e971 100644 --- a/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc +++ b/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc @@ -1,146 +1,146 @@ === FreeBSD Foundation Links: + link:https://freebsdfoundation.org/[FreeBSD Foundation] URL: link:https://freebsdfoundation.org/[] + link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] + link:https://freebsdfoundation.org/donate/[Donate] URL: link:https://freebsdfoundation.org/donate/[] + link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[] + link:https://freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://freebsdfoundation.org/journal/[] + link:https://freebsdfoundation.org/our-work/events/[Foundation Events] URL: link:https://freebsdfoundation.org/our-work/events/[] Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD. We do this in both technical and non-technical ways. We are 100% supported by donations from individuals and corporations and those investments help us fund the: * Software development projects to implement features and functionality in FreeBSD * Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD * Purchase and support of hardware to improve and maintain FreeBSD infrastructure * Resources to improve security, quality assurance, and continuous integration efforts * Materials and staff needed to promote, educate, and advocate for FreeBSD * Collaboration between commercial vendors and FreeBSD developers * Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity ==== Operations We kicked off the new year with ambitious goals to help move the FreeBSD Project forward by identifying features and functionality to support in the operating system and increasing our advocacy efforts to increase and expand the visibility of FreeBSD. Stay tuned for a blog post that will provide more information on our 2024 goals and plans. We also published the 2024 Budget. In order to provide greater transparency about the budgeting process, we wrote a link:https://freebsdfoundation.org/blog/on-starting-the-2024-freebsd-foundation-budget-journey/[blog post] that provides more details on how funding is allocated, new breakouts of some of the project expense categories, and more details on where the funding is going. ==== OS Improvements During the first quarter of 2024, 180 src, 65 ports, and 18 doc tree commits identified The FreeBSD Foundation as a sponsor. Three new projects began this quarter. * Work began to improve FreeBSD's audio stack and provide audio developers with useful tools and frameworks to make sound development on FreeBSD easier. Read more in mailto:christos@FreeBSD.org[Christos Margiolis] <<_audio_stack_improvements,Audio Stack Improvements>> report entry. * mailto:olce@FreeBSD.org[Olivier Certner] began his second contract with the Foundation, and this time around, the main goal is to make unionfs stable and useful on FreeBSD. Other work may include revamping VFS lookups, improving out-of-memory handling, implementing a notification system for en-masse detection of filesystem changes such as inotify, and improving console usability. * This quarter, a new project to add hierarchical rate limits to the OpenZFS file system began. mailto:pjd@FreeBSD.org[Pawel Dawidek] will add support for limits that will be configurable, similar to quotas, but would limit the number of read/write operations and read/write bandwidth. Six projects continued this quarter. * You can read about the continued work to port OpenStack components to FreeBSD in Chih-Hsin Chang's <<_openstack_on_freebsd,OpenStack on FreeBSD>> report entry. * Work continued to improve cloud-init support for FreeBSD. You can read about Mina Galić's work in her <<_freeBSD_as_a_tier_1_cloud-init_platform,FreeBSD as a Tier 1 cloud-init Platform>> report entry. * A new joint project began 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. For those interested in the technical details, follow mailto:kib@FreeBSD.org[Konstantin Belousov] commits tagged with Sponsored by fields for Advanced Micro Devices (AMD) and The FreeBSD Foundation. * Refer to Pierre Pronchery's <<_graphical_installer_for_freebsd,Graphical Installer for FreeBSD>> report entry to read about the status of FreeBSD's new graphical installer. * Work continues to port the Vector Packet Processor (VPP) to FreeBSD. 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. Look for a pending article from the developer working on the project, mailto:thj@FreeBSD.org[Tom Jones], that details the experience of porting VPP to FreeBSD. * mailto:bz@FreeBSD.org[Björn Zeeb] and mailto:cc@FreeBSDd.org[Cheng Cui] continue their wireless work. This quarter was mostly focused on bug fixes and stability improvements to LinuxKPI 802.11 and net80211. Much of this work made it into the 13.3 release. Here is a sampling of other Foundation-sponsored development completed over the first quarter of 2024: * FreeBSD was accepted in Google Summer of Code 2024 after receiving 22 contributor proposals; on May 1, we will learn how many projects we will be awarded * OpenSSH: update to 9.6p1 then 9.7p1 * Deprecate bsdlabel * Import the kernel parts of bhyve/arm64 * Various RISC-V improvements ==== FreeBSD Infrastructure A contract was completed to set up a new cluster site at NYI Chicago. You can read about the details of that project on the link:https://freebsdfoundation.org/blog/powering-up-the-future-the-new-freebsd-cluster-in-chicago/[Foundation's blog]. ==== 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 the test infrastructure. The full update can be found within the quarterly status report. ==== Partnerships and Research A focus of Partnerships this Quarter has been to educate the industry about the innovations in the FreeBSD community and the impact that FreeBSD continues to have as a cornerstone to our digital society. This is an ongoing priority, and one we invite (encourage) everyone using and working on FreeBSD to join us in. Greg Wallace, the Foundation Partnerships lead, is grateful for the opportunities he has had to meet with open source and industry leaders at Microsoft, Google, AWS, OpenSSF, Alpha-Omega, CISA, Eclipse Foundation, Open Source Initiative, Apache Software Foundation, Rust Foundation, Red Hat, Linux Foundation and many others to ensure they have visibility into the key role FreeBSD plays in the global digital infrastructure. This is a role FreeBSD has earned through its technical excellence, security by design, high availability, simplicity of operations, commitment to open source collaboration, and cohesiveness. One sees these characteristics of FreeBSD in the important ongoing funded development work such as porting VPP to FreeBSD, sponsored by RG Nets. Ensuring industry visibility to the excellence and impact of FreeBSD is vital to ensuring tier one support for FreeBSD across all key hardware and software platforms. As a community, every conversation we have with people outside the BSD communities, and every piece of content we publish, that attest to how FreeBSD powers our individual and corporate success, brings us one step closer. To this end, the Foundation is working on a FreeBSD Impact Report that will aggregate the core and often mission critical role FreeBSD plays in society, from embedded systems powered by QNX, to payments and check processing, to digital entertainment, internet and cybersecurity infrastructure. Our community is stepping up in innumerable ways, including to make sure FreeBSD supports industry-standard containerized workloads -- check out the link:https://github.com/opencontainers/wg-freebsd-runtime[Open Container Initiative FreeBSD runtime extension working group]. -The recently-opened hardware vendor support survey will feed into a hardware support guide that reflects the collective experience of all respondents that is intended to help everyone identify hardware vendors that prioritize FreeBSD; it will also help focus Partnerships' outreach on the priority vendors. +The recently opened hardware vendor support survey will feed into a hardware support guide that reflects the collective experience of all respondents that is intended to help everyone identify hardware vendors that prioritize FreeBSD; it will also help focus Partnerships' outreach on the priority vendors. To close, please *TELL THE WORLD YOU USE FREEBSD AND WHY. There is no wrong way to do this* -- put it on your blog, on your favorite social media channel, list FreeBSD on your company’s Open Source page, contact the Foundation about a Case Study, etc. link:https://www.stormshield.com/news/a-short-history-of-open-source/[Stormshield, a leading cybersecurity company based in Europe, provides a great example of how vendors that use FreeBSD can do this]. The footer of their blogs says: "A strong supporter of Open Source, Stormshield is an active member (and sponsor) of the FreeBSD community...Whenever we modify Open Source software, make patches or add features, we offer them to the community for inclusion." ==== Advocacy The first quarter of 2024 marked the beginning of a link:https://freebsdfoundation.org/blog/march-2024-advocacy-update/[new era] for the Foundation Advocacy team. We welcomed link:https://freebsdfoundation.org/blog/kim-mcmahon-to-join-freebsd-foundation-as-senior-director-of-advocacy-and-community/[Kim McMahon] in the role of Senior Director of Advocacy and Community and also brought on two new technical writers to help increase the frequency and depth of the FreeBSD-related content we produce. Just some of our expanded Q1 efforts to support FreeBSD are below. * Began work planning the on the link:https://freebsdfoundation.org/news-and-events/event-calendar/may-2024-freebsd-developer-summit/[May 2024 FreeBSD Developer Summit], co-located with BSDCan, taking place May 29-30, 2024 in Ottawa, Canada * Introduced FreeBSD to new and returning folks at link:https://stateofopencon.com/soocon-2024/[State of Open Con 24] in London, UK, February 6-7, 2024 * Held an Introduction to FreeBSD half-day workshop and staffed a booth at link:https://www.socallinuxexpo.org/scale/21x[SCaLE21x], which took place March 14-17, 2024 in Pasadena, CA. Thanks to Gordon Tetlow for his help with the workshop * The Foundation team also worked on a common message on the improvement and benefits of FreeBSD to ensure consistency between the FreeBSD Foundation and Core Team * Members of the Foundation team served as Administrators for the 2024 Google Summer of Code. This year marks the 20th anniversary of Google Summer of Code and the 20th year that the link:https://freebsdfoundation.org/blog/the-freebsd-project-participating-in-google-summer-of-code-2024-2/[FreeBSD Project was accepted as a mentoring organization]. The Project received 23 applications from prospective interns * Provided an link:https://freebsdfoundation.org/blog/freebsd-13-3-whats-new-and-how-did-we-get-here/[overview of FreeBSD 13.x] including the 13.3 release * Worked on the final report of the 2024 FreeBSD Community Survey. Be on the lookout for the report at the end of April * In partnership with Innovate UK and Digital Security by Design (DSbD), the Foundation held the first annual link:https://www.globenewswire.com/news-release/2024/04/03/2856691/0/en/FreeBSD-Foundation-and-Digital-Security-by-Design-DSbD-Announce-Beacon-Award-Winners-for-Innovations-and-Improvements-to-CheriBSD.html[Digital Security by Design (DSbD) Ecosystem Beacon Awards] to celebrate innovators working with and enhancing CheriBSD * Published numerous blogs including: ** link:https://freebsdfoundation.org/blog/what-makes-the-freebsd-governance-model-successful/[What Makes the FreeBSD Governance Model Successful] ** link:https://freebsdfoundation.org/blog/guiding-the-future-of-freebsd-releases-colin-percival-the-new-release-engineering-team-lead/[Guiding the future of FreeBSD releases: Colin Percival, the new Release Engineering Team Lead] * Authored or participated in a number of Thought Leadership and News articles including: ** link:https://freebsdfoundation.org/news-and-events/latest-news/the-cybersecurity-battle-has-come-to-hardware/[The Cybersecurity Battle Has Come to Hardware] ** link:https://freebsdfoundation.org/news-and-events/latest-news/ampere-in-the-wild-how-freebsd-employs-ampere-arm64-servers-in-the-data-center/[Ampere in the Wild: How FreeBSD Employs Ampere Arm64 Servers in the Data Center] ** link:https://freebsdfoundation.org/news-and-events/latest-news/isas-and-the-dawning-hardware-security-revolution/[ISAs and the Dawning Hardware Security Revolution] ** Published the link:https://freebsdfoundation.org/news-and-events/newsletter/march-2024-foundation-update/[March 2024 FreeBSD Update] with a new look ** Released the link:https://freebsdfoundation.org/past-issues/freebsd-14-0/[November/December 2023] and link:https://freebsdfoundation.org/past-issues/networking-10th-anniversary/[January/February 2024] issues of the FreeBSD Journal now with HTML versions of the articles ==== Fundraising Thank you to everyone who gave us a financial contribution last quarter to help fund our work to support the Project. 2024 started strong with a total of $250,855 raised this quarter. We are grateful for your investment in FreeBSD! Please consider supporting our efforts in 2024 by making a donation here: link:https://freebsdfoundation.org/donate/[]. Or, check out our Partnership opportunities here: link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[]. ==== 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 link:https://freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2024-01-2024-03/freshports.adoc b/website/content/en/status/report-2024-01-2024-03/freshports.adoc index 5abd4feebc..088670806e 100644 --- a/website/content/en/status/report-2024-01-2024-03/freshports.adoc +++ b/website/content/en/status/report-2024-01-2024-03/freshports.adoc @@ -1,50 +1,50 @@ === FreshPorts: Notification of new packages Links: + link:https://freshports.org/[FreshPorts] URL: link:https://freshports.org/[] + link:https://news.freshports.org/[FreshPorts blog] URL: link:https://news.freshports.org/[] Contact: Dan Langille FreshPorts and FreshSource have reported upon FreeBSD commits for 20 years. They cover all commits, not just ports. FreshPorts tracks the commits and extracts data from the port Makefiles to create a database of information useful to both port maintainers and port users. For example, link:https://www.freshports.org/security/acme.sh/#history[] shows the history of the package:security/acme.sh[] port, back to its creation in May 2017. Also available are dependencies, flavors, configuration options, and available packages. All of this is useful for both users and developers of ports. ==== Notification: New Package Available One of the original features of FreshPorts is notification of ports updates. You can create a list of ports and receive notifications about those ports. This new feature can also notify when a new package is available for that port. -The use case: a known security vuln has been patched. +The use case: a known security vulnerability has been patched. FreshPorts will tell you the port has been patched, and then you wait for the package. This new feature will tell you when that package is available. Details at: * link:https://github.com/FreshPorts/freshports/issues/542[] ==== Help Needed It has been over 23 years since FreshPorts started. Others must take over eventually. I have started that process recently. There are several aspects to FreshPorts: * FreeBSD admin (updating the OS and packages) * front end code (website - mostly PHP) * back end code (commit processing - Perl, Python, shell) * database design (PostgreSQL). The database does not change very often and requires little maintenance compared to the applications and OS. The website pretty much runs itself. From time to time, a change to the FreeBSD ports infrastructure breaks something or requires a modification, but there is rarely any urgency to fix that. This is not a huge time commitment. There is a lot of learning. While not a complex application, FreshPorts is also not trivial. To contribute, please join the link:https://lists.freshports.org/mailman/listinfo/freshports-coders[] mailing list and let us know what you would like to help with. diff --git a/website/content/en/status/report-2024-01-2024-03/libsys.adoc b/website/content/en/status/report-2024-01-2024-03/libsys.adoc index 46275eb7aa..791aed0974 100644 --- a/website/content/en/status/report-2024-01-2024-03/libsys.adoc +++ b/website/content/en/status/report-2024-01-2024-03/libsys.adoc @@ -1,41 +1,42 @@ === libsys Contact: Brooks Davis The libsys project removes direct system calls from [.filename]#libc.so# and [.filename]#libpthread.so# (aka [.filename]#libthr.so#) to a separate [.filename]#libsys.so#. This will: * Isolate language runtimes from the details of system call implementations. * Better support logging and replay frameworks for systems calls. * Support elimination of the ability to make system calls outside trusted code in the runtime linker and `libsys`. This work was initially inspired by a compartmentalization prototype in CheriBSD in 2016. Ali Mashtizadeh and Tal Garfinkel picked that work up and attempted to upstream it (link:https://reviews.freebsd.org/D14609[D14609]). Unfortunately we could not figure out how to review and land the massive reorganization required through a phabricator review so it languished. Last year the CHERI project once again found a need for system call separation in a new library-based compartmentalization framework in CheriBSD so I rebuilt the patch from scratch, committing dozens of `libc` cleanups along the way. I landed the first batch of changes on February 5th. Since then I have made a number of refinements to the way we link `libsys` as well as which symbols are provided in which library. Thanks to mailto:kib@FreeBSD.org[Konstantin Belousov] for many rounds of review and feedback as well as runtime linker fixes. -Thanks to mailto:markj@FreeBSD.org[Mark Johnston] for runtime linker debugging and mailto:dim@FreeBSD.org[Dimitry Andric] for sanitizer fixes. +Thanks to mailto:markj@FreeBSD.org[Mark Johnston] for runtime linker debugging and mailto:dim@FreeBSD.org[Dimitry Andric] for sanitizer fixes. Thanks also to everyone who reported bugs and helped debug issues. ==== Known issues (as of the end of the reporting period) * The `libsys` ABI is not yet considered stable (it is safe to assume `__sys_foo()` will be supported so language runtimes can use it now). * Programs using the address sanitizer must be linked with `-lsys` (resolved in base at publication time). ==== TODO * Add a [.filename]#libsys.h#. (See link:https://reviews.freebsd.org/D44387[D44387] and other reviews in the stack.) * Update man:intro[2] for `libsys`. * Finalize the ABI. I am likely to reduce the set of `_` (underscore) prefixed symbols we expose. - * MFC the existence of `libsys`? It is not clear this is practical, but it might be possible to MFC something useful for language runtimes. + * MFC the existence of `libsys`? + It is not clear this is practical, but it might be possible to MFC something useful for language runtimes. ==== Help wanted * Port language runtimes that do not use `libc` to use `libsys` for system calls rather than rolling their own interfaces. * Explore limitations on where system calls can be made similar to OpenBSD's link:https://man.openbsd.org/OpenBSD-7.3/msyscall[msyscall(2)] (now obsolete) and link:https://man.openbsd.org/pinsyscalls[pinsyscalls(2)] (not an obvious match to our `libsys`). Sponsor: AFRL, DARPA diff --git a/website/content/en/status/report-2024-01-2024-03/pot.adoc b/website/content/en/status/report-2024-01-2024-03/pot.adoc index dc41c68822..1bb3823a5a 100644 --- a/website/content/en/status/report-2024-01-2024-03/pot.adoc +++ b/website/content/en/status/report-2024-01-2024-03/pot.adoc @@ -1,23 +1,23 @@ === 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 were no new link:https://github.com/bsdpot/pot[Pot] releases. Potluck saw quite some activity though. Not only have the images been rebuilt for FreeBSD 14, but also the new link:https://github.com/bsdpot/potluck/tree/master/adminer[Adminer] container has been submitted by first-time contributor link:https://github.com/Sidicer[Sidicer]. -Additionally a large number of additional features, updates and fixes have been committed to containers like link:https://github.com/bsdpot/potluck/tree/master/haproxy-consul[HAProxy-Consul], link:https://github.com/bsdpot/potluck/tree/master/grafana[Grafana], link:https://github.com/bsdpot/potluck/tree/master/postgresql-patroni[PostgreSQL-Patroni], or link:https://github.com/bsdpot/potluck/tree/master/prometheus[Prometheus]. +Additionally a large number of additional features, updates and fixes have been committed to containers like link:https://github.com/bsdpot/potluck/tree/master/haproxy-consul[HAProxy-Consul], link:https://github.com/bsdpot/potluck/tree/master/grafana[Grafana], link:https://github.com/bsdpot/potluck/tree/master/postgresql-patroni[PostgreSQL-Patroni], or link:https://github.com/bsdpot/potluck/tree/master/prometheus[Prometheus]. For the link:https://github.com/bsdpot/potluck/tree/master/mastodon-s3[Mastodon container], a link:https://honeyguide.eu/posts/run-your-own-mastodon-server/[blog post] has been published explaining how to use it to run your own instance. As always, feedback and patches are welcome. Sponsors: Nikulipe UAB, Honeyguide Group diff --git a/website/content/en/status/report-2024-01-2024-03/wireless.adoc b/website/content/en/status/report-2024-01-2024-03/wireless.adoc index 0f77129009..43c585d683 100644 --- a/website/content/en/status/report-2024-01-2024-03/wireless.adoc +++ b/website/content/en/status/report-2024-01-2024-03/wireless.adoc @@ -1,21 +1,21 @@ === iwlwifi(4) and wireless for 13.3-RELEASE Links: + link:https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0[Categorised Wireless Problem Reports] URL: link:https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=277512&hide_resolved=0[] Contact: Bjoern A. Zeeb + Contact: The FreeBSD wireless mailing list In the first weeks of 2024 focus was on stability for 13.3-RELEASE to finally make man:iwlwifi[4] usable. The upcoming 14.1-RELEASE will benefit from this work too. The response has since generally been positive and man:iwlwifi[4] supporting chipsets up to BE200 seems mostly stable, yet still slow. A lot of testing was provided by the FreeBSD Foundation and by many users. Massive thanks to everyone who tested, reported back, updated PRs and helped other users. I have also slowly started to "categorise" more (old) wireless problem reports and will try to continue with some spring cleaning throughout the year. -If you have questions or feedback please use the link:freebsd-wireless mailing list[https://lists.freebsd.org/subscription/freebsd-wireless]. +If you have questions or feedback please use the link:https://lists.freebsd.org/subscription/freebsd-wireless[freebsd-wireless mailing list]. That way everyone will see, be able to join in, and the answers will be publicly archived. Sponsor: minipci.biz (BE200 hardware)