diff options
Diffstat (limited to 'website/content/en/status')
364 files changed, 12713 insertions, 658 deletions
diff --git a/website/content/en/status/README b/website/content/en/status/README deleted file mode 100644 index 70484c96f9..0000000000 --- a/website/content/en/status/README +++ /dev/null @@ -1,151 +0,0 @@ -ompiling status reports - best practices - -Quarterly status reports git repository: -https://github.com/freebsd/freebsd-quarterly - -E-mail address for report submissions: -quarterly-submissions@FreeBSD.org - -0) Timeline - - The months of January, April, July and October are dedicated to - putting together the reports submitted during the precedent month. - This can include waiting for late submissions. - - portmgr@ entries default to the extended headline, because of the - overlap between quarterly reports and quarterly ports branches. - - All entries can have the deadline extended by emailing - quarterly-submissions@ up until the extended deadline. - - Quarterly status report publication is done during the same months - as soon as the report is ready. - - - First Quarter: - - First call for reports: March 1st - - 2 weeks left reminder: March 15th - - Last reminder: March 24th - - Standard deadline: March 31st - - Extended deadline: April 8th - - - Second Quarter: - - First call for reports: June 1st - - 2 weeks left reminder: June 15th - - Last reminder: June 24th - - Standard deadline: June 30th - - Extended deadline: July 8th - - - Third Quarter: - - First call for reports: September 1st - - 2 weeks left reminder: September 15th - - Last reminder: September 24th - - Standard deadline: September 30th - - Extended deadline: October 8th - - - Fourth Quarter: - - First call for reports: December 1st - - 2 weeks left reminder: December 15th - - Last reminder: December 24th - - Standard deadline: December 31st - - Extended deadline: January 8th - -1) Call for reports - - Send calls to the freebsd-quarterly-calls@ mailing list, to all - submitters of last quarterly status reports (they may have updates - or further improvements), and, depending on the season: - - Various conference organizers: - - AsiaBSDCon (secretary@asiabsdcon.org) March (First Quarter); - - BSDCan (info@bsdcan.org) May (Second Quarter); - - EuroBSDcon September - October (Third-Fourth Quarter). - EuroBSDcon as an organization is not interested in writing - reports for FreeBSD (at least it was not in October 2019: - its reason is that the conference is not FreeBSD specific), - so reports about this event should be asked of members of the - FreeBSD community that attended it; - - Google Summer of Code students and their mentors: soc-students@ - and soc-mentors@ (Second and Third Quarter). - - The easiest way to send calls for quarterly status reports is to use - the sendcalls perl script in the tools directory of the git - repository. It can also be used through a cron job, for example: - - 0 0 1,15,24 3,6,9,12 * cd ~/freebsd-quarterly/tools && ./sendcalls -s 'Daniel Ebdrup Jensen' - - If you are indeed using a cron job, please run it on freefall and - sign it with your name so that it is possible to infer who has - configured the cronjob, in case something goes wrong. - The script automatically sends calls to freebsd-quarterly-calls@, last - quarter submitters and other recipients depending on the season. - - It may also be worth making a call for reports on the forums as was - done here: - https://forums.freebsd.org/threads/call-for-freebsd-2014q4-october-december-status-reports.49812/ - - The AsciiDoctor template is at: - https://www.freebsd.org/news/status/report-sample.adoc - - Reporting howto is at: https://www.freebsd.org/news/status/howto.html. - It contains a great deal of useful hints for the submitters on how - to write good reports. It also helps to forward all the completed - reports to developers for reference, and point to the latest report - in the CFR. - -2) Building the report: - - Review and merge pull requests as well as those submitted via email, - as they come in. - - For each newly merged report, add its filename to the local Makefile: - put it in the variable corresponding to the section where you want - the report to appear. Sort the variables content as you want to sort - the reports in the corresponding section. - - While the reports are being updated, other doc-committers (wblock, - pluknet, and bjk, for example) may review the individual entries and - propose fixes. - - Write an introduction in the _index.adoc file. - It should be usually the last step in the process; a good introduction - can be only written once all the reports have been collected. - - theraven may be poked for composing a nice introduction for the - reports. - wblock suggests that we ask different people to write introductions to - add variety. Different people will bring different viewpoints and - help keep it fresh. - - Once all the reports have come in, make any final adjustsments and copy - the contents of the directory to - doc/website/content/en/status/report-yyyy-mm-yyyy-mm/ - -3) Committing it: - - - Files to edit and commit: - - The quarterly report itself, found in: - doc/website/content/en/status/report-yyyy-mm-yyyy-mm/ - - Update the next due date on the status report page and - add a link to the new report below that: - doc/website/content/en/status/_index.adoc - - The news entry for the main website page: - doc/website/data/en/news/news.toml - - Sample for the news entry (may need to add month): - [[news]] - date = "2021-01-16" - title = "October-December 2020 Status Report" - description = "The <a href=\"https://www.FreeBSD.org/status/report-2020-10-2020-12.html\">October to December 2020 Status Report</a> is now available with 42 entries." - - - After the html version of the report has been built and is online, - use w3m to dump the website as plain-text, something like the following: - w3m -cols 80 -dump https://www.freebsd.org/status/report-2021-01-2021-03/ > /tmp/report-2021-01-2021-03.txt - - w3m has full proper unicode support, and as w3m(1) explains, -dump simply - outputs text rendering of the html that can then have a few elements - snipped, while -cols ensures that everything is wrapped to 80 columns. - - - Send out - To: announce@ - Subject: FreeBSD Quarterly Status Report - <First> Quarter <year> - - This one must be approved, so find someone (mail postmaster) who can - do that before starting. - - Send a separate mail: - - To: hackers - CC: current, stable - BCC: developers - - Note: Remember to toggle disposition (attachment or inlining), as well as - recoding in the MUA. - -4) Repeat. diff --git a/website/content/en/status/_index.adoc b/website/content/en/status/_index.adoc index ee3bf1f92f..cd8acfb412 100644 --- a/website/content/en/status/_index.adoc +++ b/website/content/en/status/_index.adoc @@ -3,26 +3,41 @@ title: "FreeBSD Status Reports" sidenav: about --- +include::shared/en/urls.adoc[] + = FreeBSD Status Reports -== Next Quarterly Status Report submissions (October - December) due: December 30th, 2021 +== Next Quarterly Status Report submissions (January - March) due: March 31st, 2024 -Submit your entries as Pull Requests from your fork of link:https://github.com/freebsd/freebsd-quarterly[FreeBSD Status Report GitHub repo] or submit them via e-mail to quarterly-submissions@FreeBSD.org, using the link:https://github.com/freebsd/freebsd-quarterly/blob/master/report-sample.adoc[report-sample.adoc template]. +If you are interested in submitting status reports or you are curious about how the publication process works, please see our link:{freebsd-status-report-process}[status report process description]. ''''' One of the benefits of the FreeBSD development model is a focus on centralized design and implementation, in which the operating system is maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all the work going on in the tree. -The FreeBSD Development Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information. - -For more exact guidelines on how to write good status reports, please consult link:howto/[our recommendations]. +The FreeBSD Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information. Periodically, special status reports are prepared and published. One of those are the developer summit reports. Developer summits are places where developers meet in person to discuss issues related to the project. They are definitely worth attending if one is interested in making significant contributions to the Project and they are open to anybody! These status reports may be reproduced in whole or in part, as long as the source is clearly identified and appropriate credit given. +== 2023 + +* link:report-2023-10-2023-12/[October, 2023 - December, 2023] +* link:report-2023-07-2023-09/[July, 2023 - September, 2023] +* link:report-2023-04-2023-06/[April, 2023 - June, 2023] +* link:report-2023-01-2023-03/[January, 2023 - March, 2023] + +== 2022 + +* link:report-2022-10-2022-12/[October, 2022 - December, 2022] +* link:report-2022-07-2022-09/[July, 2022 - September, 2022] +* link:report-2022-04-2022-06/[April, 2022 - June, 2022] +* link:report-2022-01-2022-03/[January, 2022 - March, 2022] + == 2021 +* link:report-2021-10-2021-12/[October, 2021 - December, 2021] * link:report-2021-07-2021-09/[July, 2021 - September, 2021] * link:report-2021-04-2021-06/[April, 2021 - June, 2021] * link:report-2021-01-2021-03/[January, 2021 - March, 2021] diff --git a/website/content/en/status/categories-desc.adoc b/website/content/en/status/categories-desc.adoc new file mode 100644 index 0000000000..35edaa8343 --- /dev/null +++ b/website/content/en/status/categories-desc.adoc @@ -0,0 +1,19 @@ +:FreeBSD-Team-Reports-desc: Entries from the various official and semi-official teams, as found in the link:../../administration/[Administration Page]. + +:projects-desc: Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. + +:userland-desc: Changes affecting the base system and programs in it. + +:kernel-desc: Updates to kernel subsystems/features, driver support, filesystems, and more. + +:architectures-desc: Updating platform-specific features and bringing in support for new hardware platforms. + +:cloud-desc: Updating cloud-specific features and bringing in support for new cloud platforms. + +:documentation-desc: Noteworthy changes in the documentation tree, manual pages, or new external books/documents. + +:ports-desc: Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. + +:third-Party-Projects-desc: Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. + +:miscellaneous-desc: Objects that defy categorization. diff --git a/website/content/en/status/howto.adoc b/website/content/en/status/howto.adoc deleted file mode 100644 index 33c6364f14..0000000000 --- a/website/content/en/status/howto.adoc +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: "How to Write FreeBSD Status Reports" -sidenav: about ---- - -= How to Write FreeBSD Status Reports - -FreeBSD status reports are published quarterly and provide the general public with a view of what is going on in the Project, and they are often augmented by special reports from Developer Summits. As they are one of our most visible forms of communication, they are very important. This page will provide some advice on writing status report entries from mailto:theraven@FreeBSD.org[David Chisnall], experienced in technical writing. - -_Do not worry if you are not a native English speaker. The team handling status reports, `quarterly@FreeBSD.org`, will check your entries for spelling and grammar, and fix it for you._ - -== Introduce Your Work - -_Do not assume that the person reading the report knows about your project._ - -The status reports have a wide distribution. They are often one of the top news items on the FreeBSD web site and are one of the first things that people will read if they want to know a bit about what FreeBSD is. Consider this example: - -.... -abc(4) support was added, including frobnicator compatibility. -.... - -Someone reading this, if they are familiar with UNIX man pages, will know that `abc(4)` is some kind of device. But why should the reader care? What kind of device is it? Compare with this version: - -.... -A new driver, abc(4), was added to the tree, bringing support for -Yoyodyne's range Frobnicator of network interfaces. -.... - -Now the reader knows that abc is a network interface driver. Even if they do not use any Yoyodyne products, you have communicated that FreeBSD's support for network devices is improving. - -== Show the Importance of Your Work - -_Status reports are not just about telling everyone that things were done, they also need to explain why they were done._ - -Carry on with the previous example. Why is it interesting that we now support Yoyodyne Frobnicator cards? Are they widespread? Are they used in a specific popular device? Are they used in a particular niche where FreeBSD has (or would like to have) a presence? Are they the fastest network cards on the planet? Status reports often say things like this: - -.... -We imported Cyberdyne Systems T800 into the tree. -.... - -And then they stop. Maybe the reader is an avid Cyberdyne fan and knows what exciting new features the T800 brings. This is unlikely. It is far more likely that they have vaguely heard of whatever you have imported (especially into the ports tree: remember that there are over 20,000 other things there too...). List some of the new features, or bug fixes. Tell them why it is a good thing that we have the new version. - -== Tell Us Something New - -_Do not recycle the same status report items._ - -Bear in mind that status reports are not just reports on the status of the project, they are reports on the change of status of the project. If there is an ongoing project, spend a couple of sentences introducing it, but then spend the rest of the report talking about the new work. What progress have been made since the last report? What is left to do? When is it likely to be finished (or, if "finished" does not really apply, when is it likely to be ready for wider use, for testing, for deployment in production, and so on)? - -== Sponsorship - -_Do not forget about your sponsors._ - -If you or your project has received sponsorship, a scholarship from somebody or you have been already working as a contractor or an employee for a company, please include it. Sponsors always certainly appreciate if you thank them for their funding, but it is also beneficial for them to show that they are actively supporting the Project this way. Last, but not least, this helps FreeBSD to learn more about its important consumers. - -== Open Items - -_If help is needed, make this explicit!_ - -Is there any help needed with something? Are there tasks other people can do? There are two ways in which you can use the open items part of the status report: to solicit help, or to give a quick overview of the amount of work left. If there is already enough people working on the project, or it is in a state where adding more people would not speed it up, then the latter is better. Give some big work items that are in progress, and maybe indicate who is focussing on each one. - -List tasks, with enough detail that people know if they are likely to be able to do them, and invite people to get in contact. - -link:../[Back to the main page] diff --git a/website/content/en/status/report-2001-06.html b/website/content/en/status/report-2001-06.html index 960b506f7f..4a9eb7ec91 100644 --- a/website/content/en/status/report-2001-06.html +++ b/website/content/en/status/report-2001-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2001-07.html b/website/content/en/status/report-2001-07.html index 5e053d7d78..311f61e7ce 100644 --- a/website/content/en/status/report-2001-07.html +++ b/website/content/en/status/report-2001-07.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2001-08.html b/website/content/en/status/report-2001-08.html index 6b0c7b80e0..98baad6152 100644 --- a/website/content/en/status/report-2001-08.html +++ b/website/content/en/status/report-2001-08.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2001-09.html b/website/content/en/status/report-2001-09.html index 0ceb55d3c3..32e917d9bd 100644 --- a/website/content/en/status/report-2001-09.html +++ b/website/content/en/status/report-2001-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2001-11.html b/website/content/en/status/report-2001-11.html index 0955899638..edef40f247 100644 --- a/website/content/en/status/report-2001-11.html +++ b/website/content/en/status/report-2001-11.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2001-12-2002-01.html b/website/content/en/status/report-2001-12-2002-01.html index 51d4d4f2c6..ba14528ac4 100644 --- a/website/content/en/status/report-2001-12-2002-01.html +++ b/website/content/en/status/report-2001-12-2002-01.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2002-02-2002-04.html b/website/content/en/status/report-2002-02-2002-04.html index 1c9601e388..bd0229ebd7 100644 --- a/website/content/en/status/report-2002-02-2002-04.html +++ b/website/content/en/status/report-2002-02-2002-04.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2002-05-2002-06.html b/website/content/en/status/report-2002-05-2002-06.html index 8d5cbef8f8..366218d4aa 100644 --- a/website/content/en/status/report-2002-05-2002-06.html +++ b/website/content/en/status/report-2002-05-2002-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2002-07-2002-08.html b/website/content/en/status/report-2002-07-2002-08.html index 9edd07dd62..28f27b3f14 100644 --- a/website/content/en/status/report-2002-07-2002-08.html +++ b/website/content/en/status/report-2002-07-2002-08.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2002-09-2002-10.html b/website/content/en/status/report-2002-09-2002-10.html index 8cc5e7fbae..eb56a8c4da 100644 --- a/website/content/en/status/report-2002-09-2002-10.html +++ b/website/content/en/status/report-2002-09-2002-10.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2002-11-2002-12.html b/website/content/en/status/report-2002-11-2002-12.html index 1608e801ae..b6bf25e059 100644 --- a/website/content/en/status/report-2002-11-2002-12.html +++ b/website/content/en/status/report-2002-11-2002-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2003-01-2003-02.html b/website/content/en/status/report-2003-01-2003-02.html index cf65a31797..f293905f82 100644 --- a/website/content/en/status/report-2003-01-2003-02.html +++ b/website/content/en/status/report-2003-01-2003-02.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2003-03-2003-09.html b/website/content/en/status/report-2003-03-2003-09.html index e992235ff8..b0ca2cf57c 100644 --- a/website/content/en/status/report-2003-03-2003-09.html +++ b/website/content/en/status/report-2003-03-2003-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2003-10-2003-12.html b/website/content/en/status/report-2003-10-2003-12.html index 20db6ae1eb..85dd18e901 100644 --- a/website/content/en/status/report-2003-10-2003-12.html +++ b/website/content/en/status/report-2003-10-2003-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2004-01-2004-02.html b/website/content/en/status/report-2004-01-2004-02.html index 2feb6f4139..1d4f827494 100644 --- a/website/content/en/status/report-2004-01-2004-02.html +++ b/website/content/en/status/report-2004-01-2004-02.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2004-03-2004-04.html b/website/content/en/status/report-2004-03-2004-04.html index 4cef807032..eb97522524 100644 --- a/website/content/en/status/report-2004-03-2004-04.html +++ b/website/content/en/status/report-2004-03-2004-04.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2004-05-2004-06.html b/website/content/en/status/report-2004-05-2004-06.html index 1d2b8f041f..705c9a9585 100644 --- a/website/content/en/status/report-2004-05-2004-06.html +++ b/website/content/en/status/report-2004-05-2004-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2004-07-2004-12.html b/website/content/en/status/report-2004-07-2004-12.html index f855dc9377..fecbe0464c 100644 --- a/website/content/en/status/report-2004-07-2004-12.html +++ b/website/content/en/status/report-2004-07-2004-12.html @@ -6,7 +6,6 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" src="../../layout/js/google.js"></script> </head> <body> <div id="containerwrap"> @@ -281,7 +280,7 @@ the reports being divided up into topics for easier browsing. Many thanks to both for their help!</p><hr /><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Common-Address-Redundancy-Protocol---CARP">Common Address Redundancy Protocol - CARP</a></li><li><a href="#Dingo-Monthly-Report">Dingo Monthly Report</a></li><li><a href="#FreeBSD-profile.sh">FreeBSD profile.sh</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#FreeSBIE-Status-Report">FreeSBIE Status Report</a></li><li><a href="#Funded-FreeBSD-kernel-development">Funded FreeBSD kernel development</a></li><li><a href="#Improved-Multibyte/Wide-Character-Support">Improved Multibyte/Wide Character Support</a></li><li><a href="#Project-Frenzy-(FreeBSD-based-Live-CD)">Project Frenzy (FreeBSD-based Live-CD)</a></li><li><a href="#Secure-Updating">Secure Updating</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Hardware-Notes">Hardware Notes</a></li><li><a href="#The-FreeBSD-Dutch-Documentation-Team">The FreeBSD Dutch Documentation Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ATA-Driver-Status-Report">ATA Driver Status Report</a></li><li><a href="#CPU-Cache-Prefetching">CPU Cache Prefetching</a></li><li><a href="#i386-Interrupt-Code-&-PCI-Interrupt-Routing">i386 Interrupt Code & PCI Interrupt Routing</a></li><li><a href="#kgi4BSD">kgi4BSD</a></li><li><a href="#Layer-2-PFIL_HOOKS">Layer 2 PFIL_HOOKS</a></li><li><a href="#Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></li><li><a href="#Move-ARP-out-of-routing-table">Move ARP out of routing table</a></li><li><a href="#Network-Stack-Locking">Network Stack Locking</a></li><li><a href="#New-Modular-Input-Device-Layer">New Modular Input Device Layer</a></li><li><a href="#SMPng-Status-Report">SMPng Status Report</a></li><li><a href="#Sync-Protocols-(SPPP-and-NETGRAPH)">Sync Protocols (SPPP and NETGRAPH)</a></li><li><a href="#TCP-Cleanup-and-Optimizations">TCP Cleanup and Optimizations</a></li><li><a href="#TCP-Reassembly-Rewrite-and-Optimization">TCP Reassembly Rewrite and Optimization</a></li><li><a href="#TTCPv2:-Transactional-TCP-version-2">TTCPv2: Transactional TCP version 2</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Xen">FreeBSD on Xen</a></li><li><a href="#FreeBSD/arm-status-report">FreeBSD/arm status report</a></li><li><a href="#PowerPC-Port">PowerPC Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-GNOME-Project-Status-Report">FreeBSD GNOME Project Status Report</a></li><li><a href="#OpenOffice.org-port-status">OpenOffice.org port status</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#Update-of-the-Linux-userland-infrastructure">Update of the Linux userland infrastructure</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#ALTQ">ALTQ</a></li><li><a href="#Cronyx-Adapters-Drivers">Cronyx Adapters Drivers</a></li><li><a href="#OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#EuroBSDCon-2004-submitted-papers-are-online">EuroBSDCon 2004 submitted papers are online</a></li><li><a href="#EuroBSDCon-2005---Basel-/-Switzerland">EuroBSDCon 2005 - Basel / Switzerland</a></li><li><a href="#FreeBSD-Security-Officer-and-Security-Team">FreeBSD Security Officer and Security Team</a></li><li><a href="#FreeBSD-Source-Repository-Mirror-for-svn/svk">FreeBSD Source Repository Mirror for svn/svk</a></li><li><a href="#Wiki-with-new-software">Wiki with new software</a></li></ul><ul><li><a href="#Atheros-Wireless-Support">Atheros Wireless Support</a></li><li><a href="#ifconfig-Overhaul">ifconfig Overhaul</a></li><li><a href="#New-DHCP-Client">New DHCP Client</a></li><li><a href="#Wireless-Networking-Support">Wireless Networking Support</a></li></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Common-Address-Redundancy-Protocol---CARP" href="#Common-Address-Redundancy-Protocol---CARP" id="Common-Address-Redundancy-Protocol---CARP">Common Address Redundancy Protocol - CARP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~mlaier/CARP/" title="http://people.freebsd.org/~mlaier/CARP/"></a></td><td> URL: <a href="http://people.freebsd.org/~mlaier/CARP/" title="">http://people.freebsd.org/~mlaier/CARP/</a></td></tr></table><p> - Contact: + Contact: Max Laier @@ -305,7 +304,7 @@ import goes.</p> <h3>Open tasks:</h3><ol><li>Please test and send feedback!</li><li>Write documentation.</li><li>Import newest OpenBSD changes.</li></ol><hr /><h2><a name="Dingo-Monthly-Report" href="#Dingo-Monthly-Report" id="Dingo-Monthly-Report">Dingo Monthly Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/projects/dingo/index.html" title="http://www.freebsd.org/projects/dingo/index.html">Network Stack Cleanup Project.</a></td><td> URL: <a href="http://www.freebsd.org/projects/dingo/index.html" title="Network Stack Cleanup Project.">http://www.freebsd.org/projects/dingo/index.html</a></td></tr></table><p> - Contact: + Contact: George Neville-Neil @@ -316,7 +315,7 @@ outside of CVS.</p> <hr /><h2><a name="FreeBSD-profile.sh" href="#FreeBSD-profile.sh" id="FreeBSD-profile.sh">FreeBSD profile.sh</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://projects.fsck.ch/profile" title="https://projects.fsck.ch/profile">FreeBSD profile.sh site</a></td><td> URL: <a href="https://projects.fsck.ch/profile" title="FreeBSD profile.sh site">https://projects.fsck.ch/profile</a></td></tr></table><p> - Contact: + Contact: Tobias Roth @@ -335,7 +334,7 @@ configurations is needed.</p> <hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng" title="http://www.FreeBSD.org/releng"></a></td><td> URL: <a href="http://www.FreeBSD.org/releng" title="">http://www.FreeBSD.org/releng</a></td></tr></table><p> - Contact: + Contact: Scott Long @@ -392,7 +391,7 @@ <hr /><h2><a name="FreeSBIE-Status-Report" href="#FreeSBIE-Status-Report" id="FreeSBIE-Status-Report">FreeSBIE Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeSBIE.org" title="http://www.FreeSBIE.org">FreeSBIE Website</a></td><td> URL: <a href="http://www.FreeSBIE.org" title="FreeSBIE Website">http://www.FreeSBIE.org</a></td></tr><tr><td><a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="http://liste.gufi.org/mailman/listinfo/freesbie">FreeSBIE Mailing List</a></td><td> URL: <a href="http://liste.gufi.org/mailman/listinfo/freesbie" title="FreeSBIE Mailing List">http://liste.gufi.org/mailman/listinfo/freesbie</a></td></tr></table><p> - Contact: + Contact: FreeSBIE Staff @@ -422,7 +421,7 @@ implementation and use.</p> <h3>Open tasks:</h3><ol><li>Translating website and documentation</li></ol><hr /><h2><a name="Funded-FreeBSD-kernel-development" href="#Funded-FreeBSD-kernel-development" id="Funded-FreeBSD-kernel-development">Funded FreeBSD kernel development</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html" title="http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html">Long winded status report.</a></td><td> URL: <a href="http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html" title="Long winded status report.">http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/000971.html</a></td></tr></table><p> - Contact: + Contact: Poul-Henning Kamp @@ -432,7 +431,7 @@ was posted on announce, rather than repeat it here, you can find it at the link provided.</p> <hr /><h2><a name="Improved-Multibyte/Wide-Character-Support" href="#Improved-Multibyte/Wide-Character-Support" id="Improved-Multibyte/Wide-Character-Support">Improved Multibyte/Wide Character Support</a></h2><p> - Contact: + Contact: Tim Robbins @@ -457,7 +456,7 @@ <hr /><h2><a name="Project-Frenzy-(FreeBSD-based-Live-CD)" href="#Project-Frenzy-(FreeBSD-based-Live-CD)" id="Project-Frenzy-(FreeBSD-based-Live-CD)">Project Frenzy (FreeBSD-based Live-CD)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://frenzy.osdn.org.ua/" title="http://frenzy.osdn.org.ua/">Official web site</a></td><td> URL: <a href="http://frenzy.osdn.org.ua/" title="Official web site">http://frenzy.osdn.org.ua/</a></td></tr><tr><td><a href="http://frenzy.osdn.org.ua/eng/" title="http://frenzy.osdn.org.ua/eng/">English version</a></td><td> URL: <a href="http://frenzy.osdn.org.ua/eng/" title="English version">http://frenzy.osdn.org.ua/eng/</a></td></tr></table><p> - Contact: + Contact: Sergei Mozhaisky @@ -474,7 +473,7 @@ <hr /><h2><a name="Secure-Updating" href="#Secure-Updating" id="Secure-Updating">Secure Updating</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/portsnap/" title="http://www.daemonology.net/portsnap/">Portsnap</a></td><td> URL: <a href="http://www.daemonology.net/portsnap/" title="Portsnap">http://www.daemonology.net/portsnap/</a></td></tr><tr><td><a href="http://www.daemonology.net/freebsd-update/" title="http://www.daemonology.net/freebsd-update/">FreeBSD Update</a></td><td> URL: <a href="http://www.daemonology.net/freebsd-update/" title="FreeBSD Update">http://www.daemonology.net/freebsd-update/</a></td></tr></table><p> - Contact: + Contact: Colin Percival @@ -501,13 +500,13 @@ <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="Hardware-Notes" href="#Hardware-Notes" id="Hardware-Notes">Hardware Notes</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releases/5.3R/hardware-i386.html" title="http://www.FreeBSD.org/releases/5.3R/hardware-i386.html">FreeBSD/i386 5.3-RELEASE Hardware Notes</a></td><td> URL: <a href="http://www.FreeBSD.org/releases/5.3R/hardware-i386.html" title="FreeBSD/i386 5.3-RELEASE Hardware Notes">http://www.FreeBSD.org/releases/5.3R/hardware-i386.html</a></td></tr><tr><td><a href="http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html" title="http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html">FreeBSD/i386 6.0-CURRENT Hardware Notes</a></td><td> URL: <a href="http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html" title="FreeBSD/i386 6.0-CURRENT Hardware Notes">http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html</a></td></tr></table><p> - Contact: + Contact: Simon L. Nielsen <<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>> <br /> - Contact: + Contact: Christian Brueffer @@ -522,7 +521,7 @@ URL: <a href="http://www.evilcoder.org/content/section/6/39/" title="The project's webpage.">http://www.evilcoder.org/content/section/6/39/</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/nl/books/handbook/" title="http://www.FreeBSD.org/doc/nl/books/handbook/">The officially released documentation.</a></td><td> URL: <a href="http://www.FreeBSD.org/doc/nl/books/handbook/" title="The officially released documentation.">http://www.FreeBSD.org/doc/nl/books/handbook/</a></td></tr><tr><td><a href="http://www.evilcoder.org/freebsd_html/" title="http://www.evilcoder.org/freebsd_html/">Preview of the documentation.</a></td><td> URL: <a href="http://www.evilcoder.org/freebsd_html/" title="Preview of the documentation.">http://www.evilcoder.org/freebsd_html/</a></td></tr></table><p> - Contact: + Contact: Remko Lodder @@ -535,7 +534,7 @@ have a 'complete' translation ready. So if you are willing to help out, please checkout our website and/or contact me.</p> <h3>Open tasks:</h3><ol><li>Translating the Handbook</li><li>Checking the grammar of the Dutch Handbook</li><li>Translate the rest of the documentation</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="ATA-Driver-Status-Report" href="#ATA-Driver-Status-Report" id="ATA-Driver-Status-Report">ATA Driver Status Report</a></h2><p> - Contact: + Contact: Sren Schmidt @@ -563,7 +562,7 @@ fixed during this journey</p> <hr /><h2><a name="CPU-Cache-Prefetching" href="#CPU-Cache-Prefetching" id="CPU-Cache-Prefetching">CPU Cache Prefetching</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch" title="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch"></a></td><td> URL: <a href="http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch" title="">http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch</a></td></tr></table><p> - Contact: + Contact: Andre Oppermann @@ -597,7 +596,7 @@ evaluate and assess the use of CPU cache prefetch instructions in the kernel.</p> <hr /><h2><a name="i386-Interrupt-Code-&-PCI-Interrupt-Routing" href="#i386-Interrupt-Code-&-PCI-Interrupt-Routing" id="i386-Interrupt-Code-&-PCI-Interrupt-Routing">i386 Interrupt Code & PCI Interrupt Routing</a></h2><p> - Contact: + Contact: John Baldwin @@ -620,7 +619,7 @@ <hr /><h2><a name="kgi4BSD" href="#kgi4BSD" id="kgi4BSD">kgi4BSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/~nsouch/kgi4BSD" title="http://www.freebsd.org/~nsouch/kgi4BSD">Homepage</a></td><td> URL: <a href="http://www.freebsd.org/~nsouch/kgi4BSD" title="Homepage">http://www.freebsd.org/~nsouch/kgi4BSD</a></td></tr><tr><td><a href="http://wiki.daemon.li/moin.cgi/KGI" title="http://wiki.daemon.li/moin.cgi/KGI"></a></td><td> URL: <a href="http://wiki.daemon.li/moin.cgi/KGI" title="">http://wiki.daemon.li/moin.cgi/KGI</a></td></tr></table><p> - Contact: + Contact: Nicholas Souchu @@ -634,7 +633,7 @@ .</p> <h3>Open tasks:</h3><ol><li>Help improving the documentation</li></ol><hr /><h2><a name="Layer-2-PFIL_HOOKS" href="#Layer-2-PFIL_HOOKS" id="Layer-2-PFIL_HOOKS">Layer 2 PFIL_HOOKS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html" title="http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html"></a></td><td> URL: <a href="http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html" title="">http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html</a></td></tr></table><p> - Contact: + Contact: Andre Oppermann @@ -651,7 +650,7 @@ IPFW2 but also PF and others for Layer 2 filtering.</p> <hr /><h2><a name="Low-overhead-performance-monitoring-for-FreeBSD" href="#Low-overhead-performance-monitoring-for-FreeBSD" id="Low-overhead-performance-monitoring-for-FreeBSD">Low-overhead performance monitoring for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="http://people.freebsd.org/~jkoshy/projects/perf-measurement/">A best-in-class performance monitoring system for FreeBSD built over the hardware performance monitoring facilities of modern CPUs.</a></td><td> URL: <a href="http://people.freebsd.org/~jkoshy/projects/perf-measurement/" title="A best-in-class performance monitoring system for FreeBSD built over the hardware performance monitoring facilities of modern CPUs.">http://people.freebsd.org/~jkoshy/projects/perf-measurement/</a></td></tr></table><p> - Contact: + Contact: Joseph Koshy @@ -665,13 +664,13 @@ improving the project's documentation.</p> <hr /><h2><a name="Move-ARP-out-of-routing-table" href="#Move-ARP-out-of-routing-table" id="Move-ARP-out-of-routing-table">Move ARP out of routing table</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html" title="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html"></a></td><td> URL: <a href="http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html" title="">http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.html</a></td></tr></table><p> - Contact: + Contact: Andre Oppermann <<a href="mailto:andre@FreeBSD.org">andre@FreeBSD.org</a>> <br /> - Contact: + Contact: Qing Li @@ -692,7 +691,7 @@ <hr /><h2><a name="Network-Stack-Locking" href="#Network-Stack-Locking" id="Network-Stack-Locking">Network Stack Locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/projects/netperf/" title="http://www.freebsd.org/projects/netperf/">FreeBSD Project Netperf project web page.</a></td><td> URL: <a href="http://www.freebsd.org/projects/netperf/" title="FreeBSD Project Netperf project web page.">http://www.freebsd.org/projects/netperf/</a></td></tr><tr><td><a href="http://www.watson.org/~robert/freebsd/netperf/" title="http://www.watson.org/~robert/freebsd/netperf/">Robert Watson's personal Netperf web page.</a></td><td> URL: <a href="http://www.watson.org/~robert/freebsd/netperf/" title="Robert Watson's personal Netperf web page.">http://www.watson.org/~robert/freebsd/netperf/</a></td></tr></table><p> - Contact: + Contact: Robert Watson @@ -869,7 +868,7 @@ locking; a broad range of optimizations.</p> <hr /><h2><a name="New-Modular-Input-Device-Layer" href="#New-Modular-Input-Device-Layer" id="New-Modular-Input-Device-Layer">New Modular Input Device Layer</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html" title="http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html"></a></td><td> URL: <a href="http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html" title="">http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html</a></td></tr></table><p> - Contact: + Contact: Philip Paeps @@ -903,7 +902,7 @@ expected that the first visible changes will be committed to -CURRENT around late February or early March.</p> <hr /><h2><a name="SMPng-Status-Report" href="#SMPng-Status-Report" id="SMPng-Status-Report">SMPng Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p> - Contact: + Contact: John Baldwin @@ -953,7 +952,7 @@ and make the system call wrappers MPSAFE.</p> <hr /><h2><a name="Sync-Protocols-(SPPP-and-NETGRAPH)" href="#Sync-Protocols-(SPPP-and-NETGRAPH)" id="Sync-Protocols-(SPPP-and-NETGRAPH)">Sync Protocols (SPPP and NETGRAPH)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/~rik" title="http://www.freebsd.org/~rik">My FreeBSD home page. You could find here some results of my work. Unfortunately I do not update this page often.</a></td><td> URL: <a href="http://www.freebsd.org/~rik" title="My FreeBSD home page. You could find here some results of my work. Unfortunately I do not update this page often.">http://www.freebsd.org/~rik</a></td></tr></table><p> - Contact: + Contact: Roman Kurakin @@ -971,7 +970,7 @@ close a PR 21771, from 2000/10/05</p> <hr /><h2><a name="TCP-Cleanup-and-Optimizations" href="#TCP-Cleanup-and-Optimizations" id="TCP-Cleanup-and-Optimizations">TCP Cleanup and Optimizations</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~andre/tcpcleanup.html" title="http://people.freebsd.org/~andre/tcpcleanup.html"></a></td><td> URL: <a href="http://people.freebsd.org/~andre/tcpcleanup.html" title="">http://people.freebsd.org/~andre/tcpcleanup.html</a></td></tr></table><p> - Contact: + Contact: Andre Oppermann @@ -1006,7 +1005,7 @@ me in advance already now.</li></ol><hr /><h2><a name="TCP-Reassembly-Rewrite-and-Optimization" href="#TCP-Reassembly-Rewrite-and-Optimization" id="TCP-Reassembly-Rewrite-and-Optimization">TCP Reassembly Rewrite and Optimization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch" title="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch"></a></td><td> URL: <a href="http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch" title="">http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html" title="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html"></a></td><td> URL: <a href="http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html" title="">http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.html</a></td></tr></table><p> - Contact: + Contact: Andre Oppermann @@ -1037,7 +1036,7 @@ link.</p> <hr /><h2><a name="TTCPv2:-Transactional-TCP-version-2" href="#TTCPv2:-Transactional-TCP-version-2" id="TTCPv2:-Transactional-TCP-version-2">TTCPv2: Transactional TCP version 2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html" title="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html"></a></td><td> URL: <a href="http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html" title="">http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html</a></td></tr></table><p> - Contact: + Contact: Andre Oppermann @@ -1070,7 +1069,7 @@ <hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-on-Xen" href="#FreeBSD-on-Xen" id="FreeBSD-on-Xen">FreeBSD on Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.fsmware.com/xenofreebsd/" title="http://www.fsmware.com/xenofreebsd/">binaries + source + slightly out of date HOWTO</a></td><td> URL: <a href="http://www.fsmware.com/xenofreebsd/" title="binaries + source + slightly out of date HOWTO">http://www.fsmware.com/xenofreebsd/</a></td></tr><tr><td><a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/" title="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/">Xen project page</a></td><td> URL: <a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/" title="Xen project page">http://www.cl.cam.ac.uk/Research/SRG/netos/xen/</a></td></tr></table><p> - Contact: + Contact: Kip Macy @@ -1081,7 +1080,7 @@ couple of bugs need to be tracked down.</p> <h3>Open tasks:</h3><ol><li>FreeBSD support for running in Domain 0 (host)</li><li>FreeBSD support for VM checkpoint and migration</li></ol><hr /><h2><a name="FreeBSD/arm-status-report" href="#FreeBSD/arm-status-report" id="FreeBSD/arm-status-report">FreeBSD/arm status report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/platforms/arm" title="http://www.freebsd.org/platforms/arm">FreeBSD/arm project page.</a></td><td> URL: <a href="http://www.freebsd.org/platforms/arm" title="FreeBSD/arm project page.">http://www.freebsd.org/platforms/arm</a></td></tr></table><p> - Contact: + Contact: Olivier Houchard @@ -1095,7 +1094,7 @@ <hr /><h2><a name="PowerPC-Port" href="#PowerPC-Port" id="PowerPC-Port">PowerPC Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/~grehan/miniinst.iso" title="http://www.freebsd.org/~grehan/miniinst.iso">Miniinst ISO.</a></td><td> URL: <a href="http://www.freebsd.org/~grehan/miniinst.iso" title="Miniinst ISO.">http://www.freebsd.org/~grehan/miniinst.iso</a></td></tr><tr><td><a href="http://www.freebsd.org/~grehan/miniinst.txt" title="http://www.freebsd.org/~grehan/miniinst.txt">Miniinst relnotes.</a></td><td> URL: <a href="http://www.freebsd.org/~grehan/miniinst.txt" title="Miniinst relnotes.">http://www.freebsd.org/~grehan/miniinst.txt</a></td></tr></table><p> - Contact: + Contact: Peter Grehan @@ -1109,7 +1108,7 @@ those who want to delve deeply into FreeBSD kernel internals.</p> <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-GNOME-Project-Status-Report" href="#FreeBSD-GNOME-Project-Status-Report" id="FreeBSD-GNOME-Project-Status-Report">FreeBSD GNOME Project Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/">FreeBSD GNOME Project</a></td><td> URL: <a href="http://www.FreeBSD.org/gnome/" title="FreeBSD GNOME Project">http://www.FreeBSD.org/gnome/</a></td></tr></table><p> - Contact: + Contact: Joe Marcus @@ -1170,7 +1169,7 @@ URL: <a href="http://porting.openoffice.org/freebsd/" title="FreeBSD OpenOffice.org porting status page">http://porting.openoffice.org/freebsd/</a></td></tr><tr><td><a href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/" title="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/">Stable OOo Packages for FreeBSD</a></td><td> URL: <a href="http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/" title="Stable OOo Packages for FreeBSD">http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/FreeBSD/</a></td></tr><tr><td><a href="http://sourceforge.jp/projects/waooo/files/" title="http://sourceforge.jp/projects/waooo/files/">Some volatile WIP status of packages</a></td><td> URL: <a href="http://sourceforge.jp/projects/waooo/files/" title="Some volatile WIP status of packages">http://sourceforge.jp/projects/waooo/files/</a></td></tr></table><p> - Contact: + Contact: Maho Nakata @@ -1281,13 +1280,13 @@ <hr /><h2><a name="Ports-Collection" href="#Ports-Collection" id="Ports-Collection">Ports Collection</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/">The FreeBSD ports collection</a></td><td> URL: <a href="http://www.FreeBSD.org/ports/" title="The FreeBSD ports collection">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://portsmon.firepipe.net/index.html" title="http://portsmon.firepipe.net/index.html">FreeBSD ports monitoring system</a></td><td> URL: <a href="http://portsmon.firepipe.net/index.html" title="FreeBSD ports monitoring system">http://portsmon.firepipe.net/index.html</a></td></tr></table><p> - Contact: + Contact: Mark Linimon <<a href="mailto:linimon_at_FreeBSD_dot_org">linimon_at_FreeBSD_dot_org</a>> <br /> - Contact: + Contact: Erwin Lansing @@ -1406,7 +1405,7 @@ <a href="http://pointyhat.FreeBSD.org/errorlogs/" shape="rect">pointyhat</a> ) and this will remain a focus area.</li></ol><hr /><h2><a name="Update-of-the-Linux-userland-infrastructure" href="#Update-of-the-Linux-userland-infrastructure" id="Update-of-the-Linux-userland-infrastructure">Update of the Linux userland infrastructure</a></h2><p> - Contact: + Contact: Alexander Leidinger @@ -1426,7 +1425,7 @@ <hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="ALTQ" href="#ALTQ" id="ALTQ">ALTQ</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~mlaier/ALTQ_driver/" title="http://people.freebsd.org/~mlaier/ALTQ_driver/"></a></td><td> URL: <a href="http://people.freebsd.org/~mlaier/ALTQ_driver/" title="">http://people.freebsd.org/~mlaier/ALTQ_driver/</a></td></tr><tr><td><a href="http://www.freebsd.org/cgi/man.cgi?query=altq&manpath=FreeBSD+6.0-current&format=html" title="http://www.freebsd.org/cgi/man.cgi?query=altq&manpath=FreeBSD+6.0-current&format=html">ALTQ(4) man-page.</a></td><td> URL: <a href="http://www.freebsd.org/cgi/man.cgi?query=altq&manpath=FreeBSD+6.0-current&format=html" title="ALTQ(4) man-page.">http://www.freebsd.org/cgi/man.cgi?query=altq&manpath=FreeBSD+6.0-current&format=html</a></td></tr></table><p> - Contact: + Contact: Max Laier @@ -1439,7 +1438,7 @@ ALTQ. For details see the ALTQ(4) man-page.</p> <h3>Open tasks:</h3><ol><li>Convert/test more NIC drivers.</li><li>Write documentation.</li></ol><hr /><h2><a name="Cronyx-Adapters-Drivers" href="#Cronyx-Adapters-Drivers" id="Cronyx-Adapters-Drivers">Cronyx Adapters Drivers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cronyx.ru/software" title="http://www.cronyx.ru/software">Cronyx Software download page.</a></td><td> URL: <a href="http://www.cronyx.ru/software" title="Cronyx Software download page.">http://www.cronyx.ru/software</a></td></tr></table><p> - Contact: + Contact: Roman Kurakin @@ -1457,13 +1456,13 @@ runtime. For now you should recompile module/kernel to change mode.</li></ol><hr /><h2><a name="OpenBSD-packet-filter---pf" href="#OpenBSD-packet-filter---pf" id="OpenBSD-packet-filter---pf">OpenBSD packet filter - pf</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://pf4freebsd.love2party.net/" title="http://pf4freebsd.love2party.net/">PF4FreeBSD Homepage</a></td><td> URL: <a href="http://pf4freebsd.love2party.net/" title="PF4FreeBSD Homepage">http://pf4freebsd.love2party.net/</a></td></tr></table><p> - Contact: + Contact: Max Laier <<a href="mailto:mlaier@FreeBSD.org">mlaier@FreeBSD.org</a>> <br /> - Contact: + Contact: Daniel Hartmeier @@ -1492,7 +1491,7 @@ alternative to IPFW and IPF.</p> <h3>Open tasks:</h3><ol><li>Write more documentation/articles.</li><li>Write an IPFilter to PF migration guide/tool.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="EuroBSDCon-2004-submitted-papers-are-online" href="#EuroBSDCon-2004-submitted-papers-are-online" id="EuroBSDCon-2004-submitted-papers-are-online">EuroBSDCon 2004 submitted papers are online</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon2004.de/papers.html" title="http://www.eurobsdcon2004.de/papers.html">Papers/Presentations Download Page</a></td><td> URL: <a href="http://www.eurobsdcon2004.de/papers.html" title="Papers/Presentations Download Page">http://www.eurobsdcon2004.de/papers.html</a></td></tr></table><p> - Contact: + Contact: Patrick M. Hausen @@ -1503,7 +1502,7 @@ helped make EuroBSDCon 2004 a success.</p> <hr /><h2><a name="EuroBSDCon-2005---Basel-/-Switzerland" href="#EuroBSDCon-2005---Basel-/-Switzerland" id="EuroBSDCon-2005---Basel-/-Switzerland">EuroBSDCon 2005 - Basel / Switzerland</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.eurobsdcon.org/" title="http://www.eurobsdcon.org/">EuroBSDCon Homepage</a></td><td> URL: <a href="http://www.eurobsdcon.org/" title="EuroBSDCon Homepage">http://www.eurobsdcon.org/</a></td></tr></table><p> - Contact: + Contact: Max Laier @@ -1519,17 +1518,17 @@ URL: <a href="http://www.freebsd.org/administration.html#t-secteam" title="FreeBSD Security Team members">http://www.freebsd.org/administration.html#t-secteam</a></td></tr><tr><td><a href="http://vuxml.freebsd.org/" title="http://vuxml.freebsd.org/">FreeBSD VuXML web site</a></td><td> URL: <a href="http://vuxml.freebsd.org/" title="FreeBSD VuXML web site">http://vuxml.freebsd.org/</a></td></tr><tr><td><a href="http://cvsweb.freebsd.org/ports/security/portaudit/" title="http://cvsweb.freebsd.org/ports/security/portaudit/">portaudit</a></td><td> URL: <a href="http://cvsweb.freebsd.org/ports/security/portaudit/" title="portaudit">http://cvsweb.freebsd.org/ports/security/portaudit/</a></td></tr></table><p> - Contact: + Contact: Jacques Vidrine <<a href="mailto:nectar@FreeBSD.org">nectar@FreeBSD.org</a>> <br /> - Contact: + Contact: Security Officer <<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>> <br /> - Contact: + Contact: Security Team <<a href="mailto:security-team@FreeBSD.org">security-team@FreeBSD.org</a>> </p> @@ -1590,7 +1589,7 @@ URL: <a href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/" title="RSS for RELENG_5 commits.">http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/</a></td></tr><tr><td><a href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/" title="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/">RSS for CURRENT commits.</a></td><td> URL: <a href="http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/" title="RSS for CURRENT commits.">http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/</a></td></tr><tr><td><a href="http://svk.elixus.org/" title="http://svk.elixus.org/">svk homepage.</a></td><td> URL: <a href="http://svk.elixus.org/" title="svk homepage.">http://svk.elixus.org/</a></td></tr></table><p> - Contact: + Contact: Kao Chia-liang @@ -1606,7 +1605,7 @@ track upstream changes while their patches are being reviewed.</p> <hr /><h2><a name="Wiki-with-new-software" href="#Wiki-with-new-software" id="Wiki-with-new-software">Wiki with new software</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/" title="http://wiki.freebsd.org/">Wiki</a></td><td> URL: <a href="http://wiki.freebsd.org/" title="Wiki">http://wiki.freebsd.org/</a></td></tr></table><p> - Contact: + Contact: Josef El-Rayes diff --git a/website/content/en/status/report-2005-01-2005-03.html b/website/content/en/status/report-2005-01-2005-03.html index 39be80069d..b5a710bcb8 100644 --- a/website/content/en/status/report-2005-01-2005-03.html +++ b/website/content/en/status/report-2005-01-2005-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2005-03-2005-06.html b/website/content/en/status/report-2005-03-2005-06.html index 1709b33b44..17a38fabf5 100644 --- a/website/content/en/status/report-2005-03-2005-06.html +++ b/website/content/en/status/report-2005-03-2005-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2005-07-2005-10.html b/website/content/en/status/report-2005-07-2005-10.html index 2b6edd3cf3..a4dda8e00c 100644 --- a/website/content/en/status/report-2005-07-2005-10.html +++ b/website/content/en/status/report-2005-07-2005-10.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2005-10-2005-12.html b/website/content/en/status/report-2005-10-2005-12.html index 9f90c4ab19..1a98c431b3 100644 --- a/website/content/en/status/report-2005-10-2005-12.html +++ b/website/content/en/status/report-2005-10-2005-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2006-01-2006-03.html b/website/content/en/status/report-2006-01-2006-03.html index b033bea25b..64b3eeaf9c 100644 --- a/website/content/en/status/report-2006-01-2006-03.html +++ b/website/content/en/status/report-2006-01-2006-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2006-04-2006-06.html b/website/content/en/status/report-2006-04-2006-06.html index 74949aa934..19a04c6bf1 100644 --- a/website/content/en/status/report-2006-04-2006-06.html +++ b/website/content/en/status/report-2006-04-2006-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2006-06-2006-10.html b/website/content/en/status/report-2006-06-2006-10.html index 3c7795975b..93b0c44f79 100644 --- a/website/content/en/status/report-2006-06-2006-10.html +++ b/website/content/en/status/report-2006-06-2006-10.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2006-10-2006-12.html b/website/content/en/status/report-2006-10-2006-12.html index 5ac6e1d617..857983599e 100644 --- a/website/content/en/status/report-2006-10-2006-12.html +++ b/website/content/en/status/report-2006-10-2006-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2007-01-2007-03.html b/website/content/en/status/report-2007-01-2007-03.html index 146eaa4ef6..570e26e1e2 100644 --- a/website/content/en/status/report-2007-01-2007-03.html +++ b/website/content/en/status/report-2007-01-2007-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2007-04-2007-06.html b/website/content/en/status/report-2007-04-2007-06.html index 5928b362ac..7ac578d87f 100644 --- a/website/content/en/status/report-2007-04-2007-06.html +++ b/website/content/en/status/report-2007-04-2007-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2007-07-2007-10.html b/website/content/en/status/report-2007-07-2007-10.html index dfff2bab56..1b582ac822 100644 --- a/website/content/en/status/report-2007-07-2007-10.html +++ b/website/content/en/status/report-2007-07-2007-10.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2007-10-2007-12.html b/website/content/en/status/report-2007-10-2007-12.html index d06df12d1f..419d4cd9c7 100644 --- a/website/content/en/status/report-2007-10-2007-12.html +++ b/website/content/en/status/report-2007-10-2007-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2008-01-2008-03.html b/website/content/en/status/report-2008-01-2008-03.html index ec1c841207..e437d39108 100644 --- a/website/content/en/status/report-2008-01-2008-03.html +++ b/website/content/en/status/report-2008-01-2008-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2008-04-2008-06.html b/website/content/en/status/report-2008-04-2008-06.html index bfd728f0a4..a70411a8a0 100644 --- a/website/content/en/status/report-2008-04-2008-06.html +++ b/website/content/en/status/report-2008-04-2008-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2008-07-2008-09.html b/website/content/en/status/report-2008-07-2008-09.html index 0a8cb7dcdc..68c3a29158 100644 --- a/website/content/en/status/report-2008-07-2008-09.html +++ b/website/content/en/status/report-2008-07-2008-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2008-10-2008-12.html b/website/content/en/status/report-2008-10-2008-12.html index 42ebc1858c..5fddade08c 100644 --- a/website/content/en/status/report-2008-10-2008-12.html +++ b/website/content/en/status/report-2008-10-2008-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2009-01-2009-03.html b/website/content/en/status/report-2009-01-2009-03.html index 461fd12665..96a311d852 100644 --- a/website/content/en/status/report-2009-01-2009-03.html +++ b/website/content/en/status/report-2009-01-2009-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2009-04-2009-09.html b/website/content/en/status/report-2009-04-2009-09.html index cb69480c70..315aa07f1f 100644 --- a/website/content/en/status/report-2009-04-2009-09.html +++ b/website/content/en/status/report-2009-04-2009-09.html @@ -6,7 +6,6 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" src="../../layout/js/google.js"></script> </head> <body> <div id="containerwrap"> @@ -285,19 +284,19 @@ 2010.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#About-Google-Summer-of-Code-2009">About Google Summer of Code 2009</a></li><li><a href="#BSD-licensed-iconv-(Summer-of-Code-2009)">BSD-licensed iconv (Summer of Code 2009)</a></li><li><a href="#BSD-licensed-text-processing-tools-(Summer-of-Code-2008)">BSD-licensed text-processing tools (Summer of Code 2008)</a></li><li><a href="#Ext2fs-Status-report-(Summer-of-Code-2009)">Ext2fs Status report (Summer of Code 2009)</a></li><li><a href="#libnetstat(3)---networking-statistics-(Summer-of-Code-2009)">libnetstat(3) - networking statistics (Summer of Code 2009)</a></li><li><a href="#pefs---stacked-cryptographic-filesystem-(Summer-of-Code-2009)">pefs - stacked cryptographic filesystem (Summer of Code 2009)</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#BSD#-Project">BSD# Project</a></li><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></li><li><a href="#Grand-Central-Dispatch---FreeBSD-port">Grand Central Dispatch - FreeBSD port</a></li><li><a href="#libprocstat(3)---process-statistics">libprocstat(3) - process statistics</a></li><li><a href="#New-BSD-licensed-debugger">New BSD licensed debugger</a></li><li><a href="#NFSv4-ACLs">NFSv4 ACLs</a></li><li><a href="#The-Newcons-project">The Newcons project</a></li><li><a href="#VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-KDE-Team">FreeBSD KDE Team</a></li><li><a href="#FreeBSD-Ports-Management-Team">FreeBSD Ports Management Team</a></li><li><a href="#Release-Engineering-Status-Report">Release Engineering Status Report</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></li><li><a href="#Modular-Congestion-Control">Modular Congestion Control</a></li><li><a href="#Network-Stack-Virtualization">Network Stack Virtualization</a></li><li><a href="#Stream-Control-Transmission-Protocol-(SCTP)">Stream Control Transmission Protocol (SCTP)</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD/ZFS">FreeBSD/ZFS</a></li><li><a href="#hwpmc-for-MIPS">hwpmc for MIPS</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></li><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li><li><a href="#The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Gecko-Project">FreeBSD Gecko Project</a></li><li><a href="#Portmaster---utility-to-assist-users-with-managing-ports">Portmaster - utility to assist users with managing ports</a></li><li><a href="#Valgrind-suite-on-FreeBSD">Valgrind suite on FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#EuroBSDcon-2009">EuroBSDcon 2009</a></li><li><a href="#FreeBSD-Developer-Summit,-Cambridge-UK">FreeBSD Developer Summit, Cambridge UK</a></li><li><a href="#New-approach-to-the-locale-database">New approach to the locale database</a></li><li><a href="#The-FreeBSD-Forums">The FreeBSD Forums</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="About-Google-Summer-of-Code-2009" href="#About-Google-Summer-of-Code-2009" id="About-Google-Summer-of-Code-2009">About Google Summer of Code 2009</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://socghop.appspot.com/org/home/google/gsoc2009/freebsd" title="http://socghop.appspot.com/org/home/google/gsoc2009/freebsd">FreeBSD GSoC Homepage</a></td><td> URL: <a href="http://socghop.appspot.com/org/home/google/gsoc2009/freebsd" title="FreeBSD GSoC Homepage">http://socghop.appspot.com/org/home/google/gsoc2009/freebsd</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SummerOfCode2009Projects" title="http://wiki.freebsd.org/SummerOfCode2009Projects">FreeBSD GSoC 2009 Wiki</a></td><td> URL: <a href="http://wiki.freebsd.org/SummerOfCode2009Projects" title="FreeBSD GSoC 2009 Wiki">http://wiki.freebsd.org/SummerOfCode2009Projects</a></td></tr></table><p> - Contact: + Contact: Brooks Davis <<a href="mailto:brooks@freebsd.org">brooks@freebsd.org</a>> <br /> - Contact: + Contact: Tim Kientzle <<a href="mailto:kientzle@freebsd.org">kientzle@freebsd.org</a>> <br /> - Contact: + Contact: Robert Watson <<a href="mailto:rwatson@freebsd.org">rwatson@freebsd.org</a>> @@ -311,7 +310,7 @@ our students and mentors of another great year!</p> <hr /><h2><a name="BSD-licensed-iconv-(Summer-of-Code-2009)" href="#BSD-licensed-iconv-(Summer-of-Code-2009)" id="BSD-licensed-iconv-(Summer-of-Code-2009)">BSD-licensed iconv (Summer of Code 2009)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borSoC2009" title="http://wiki.freebsd.org/G%C3%A1borSoC2009">BSDL iconv on FreeBSD wiki</a></td><td> URL: <a href="http://wiki.freebsd.org/G%C3%A1borSoC2009" title="BSDL iconv on FreeBSD wiki">http://wiki.freebsd.org/G%C3%A1borSoC2009</a></td></tr></table><p> - Contact: + Contact: Gbor Kvesdn @@ -330,7 +329,7 @@ private interfaces, etc.).</p> <h3>Open tasks:</h3><ol><li>Fix segfaults in Big5 and HZ modules</li><li>Improve transliteration in reverse encodings</li><li>Improve GNU compatibility by implementing extra features</li><li>Verify POSIX compatibility</li><li>Verify GNU compatibility</li><li>Check performance</li></ol><hr /><h2><a name="BSD-licensed-text-processing-tools-(Summer-of-Code-2008)" href="#BSD-licensed-text-processing-tools-(Summer-of-Code-2008)" id="BSD-licensed-text-processing-tools-(Summer-of-Code-2008)">BSD-licensed text-processing tools (Summer of Code 2008)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/G%C3%A1borSoC2008" title="http://wiki.freebsd.org/G%C3%A1borSoC2008">Wiki page for the project</a></td><td> URL: <a href="http://wiki.freebsd.org/G%C3%A1borSoC2008" title="Wiki page for the project">http://wiki.freebsd.org/G%C3%A1borSoC2008</a></td></tr></table><p> - Contact: + Contact: Gbor Kvesdn <<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>> @@ -371,7 +370,7 @@ catch 8.X, so they will go to HEAD after the release.</p> <h3>Open tasks:</h3><ol><li>Improve sort's sorting and file merging algorithms</li><li>Complete missing features for sort</li><li>Get a modern regex library for FreeBSD</li></ol><hr /><h2><a name="Ext2fs-Status-report-(Summer-of-Code-2009)" href="#Ext2fs-Status-report-(Summer-of-Code-2009)" id="Ext2fs-Status-report-(Summer-of-Code-2009)">Ext2fs Status report (Summer of Code 2009)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/SOC2009AdityaSarawgi" title="http://wiki.freebsd.org/SOC2009AdityaSarawgi">Wiki Page</a></td><td> URL: <a href="http://wiki.freebsd.org/SOC2009AdityaSarawgi" title="Wiki Page">http://wiki.freebsd.org/SOC2009AdityaSarawgi</a></td></tr></table><p> - Contact: + Contact: Aditya Sarawgi @@ -388,7 +387,7 @@ <h3>Open tasks:</h3><ol><li>Ext4 support for FreeBSD</li><li>Directory indexing for ext2fs</li><li>Journaling in ext2fs using gjournal</li></ol><hr /><h2><a name="libnetstat(3)---networking-statistics-(Summer-of-Code-2009)" href="#libnetstat(3)---networking-statistics-(Summer-of-Code-2009)" id="libnetstat(3)---networking-statistics-(Summer-of-Code-2009)">libnetstat(3) - networking statistics (Summer of Code 2009)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/PGJSoc2009" title="http://wiki.FreeBSD.org/PGJSoc2009">Wiki page</a></td><td> URL: <a href="http://wiki.FreeBSD.org/PGJSoc2009" title="Wiki page">http://wiki.FreeBSD.org/PGJSoc2009</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&cd=//&c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83" title="http://p4web.freebsd.org/@md=d&cd=//&c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83">Perforce depot</a></td><td> URL: <a href="http://p4web.freebsd.org/@md=d&cd=//&c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83" title="Perforce depot">http://p4web.freebsd.org/@md=d&cd=//&c=McZ@//depot/projects/soc2009/pgj_libstat/?ac=83</a></td></tr></table><p> - Contact: + Contact: Gbor Pli <<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>> @@ -427,13 +426,13 @@ <hr /><h2><a name="pefs---stacked-cryptographic-filesystem-(Summer-of-Code-2009)" href="#pefs---stacked-cryptographic-filesystem-(Summer-of-Code-2009)" id="pefs---stacked-cryptographic-filesystem-(Summer-of-Code-2009)">pefs - stacked cryptographic filesystem (Summer of Code 2009)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://blogs.freebsdish.org/gleb/" title="http://blogs.freebsdish.org/gleb/">Gleb's Blog</a></td><td> URL: <a href="http://blogs.freebsdish.org/gleb/" title="Gleb's Blog">http://blogs.freebsdish.org/gleb/</a></td></tr><tr><td><a href="http://wiki.freebsd.org/SOC2009GlebKurtsov" title="http://wiki.freebsd.org/SOC2009GlebKurtsov">Project page in FreeBSD wiki</a></td><td> URL: <a href="http://wiki.freebsd.org/SOC2009GlebKurtsov" title="Project page in FreeBSD wiki">http://wiki.freebsd.org/SOC2009GlebKurtsov</a></td></tr></table><p> - Contact: + Contact: Gleb Kurtsou <<a href="mailto:gk@FreeBSD.org">gk@FreeBSD.org</a>> <br /> - Contact: + Contact: Stanislav Sedov @@ -449,7 +448,7 @@ <h3>Open tasks:</h3><ol><li>Implement encrypted name lookup/readir cache</li><li>Optimize sparse files handling and file resizing</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="BSD#-Project" href="#BSD#-Project" id="BSD#-Project">BSD# Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://code.google.com/p/bsd-sharp/" title="http://code.google.com/p/bsd-sharp/">The BSD# project on Google code</a></td><td> URL: <a href="http://code.google.com/p/bsd-sharp/" title="The BSD# project on Google code">http://code.google.com/p/bsd-sharp/</a></td></tr><tr><td><a href="http://www.mono-project.org/" title="http://www.mono-project.org/">Mono (Open source .NET Development Framework)</a></td><td> URL: <a href="http://www.mono-project.org/" title="Mono (Open source .NET Development Framework)">http://www.mono-project.org/</a></td></tr></table><p> - Contact: + Contact: Romain Tartire @@ -490,25 +489,25 @@ without a FreeBSD box can help us fixing bugs more efficiently.</li></ol><hr /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/BuildingFreeBSDWithClang" title="http://wiki.freebsd.org/BuildingFreeBSDWithClang"></a></td><td> URL: <a href="http://wiki.freebsd.org/BuildingFreeBSDWithClang" title="">http://wiki.freebsd.org/BuildingFreeBSDWithClang</a></td></tr></table><p> - Contact: + Contact: Ed Schouten <<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>> <br /> - Contact: + Contact: Roman Divacky <<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>> <br /> - Contact: + Contact: Brooks Davis <<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>> <br /> - Contact: + Contact: Pawel Worach @@ -541,13 +540,13 @@ been updated for a while.</li><li>We also need to get some important fixes into LLVM to get libc compiling and some other smaller issues.</li><li>We can still appreciate more testers on minor platforms (mostly on ARM, PPC and MIPS, but testing on other platforms is also welcome).</li></ol><hr /><h2><a name="FreeBSD-TDM-Framework" href="#FreeBSD-TDM-Framework" id="FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></h2><p> - Contact: + Contact: Rafal Czubak <<a href="mailto:rcz@semihalf.com">rcz@semihalf.com</a>> <br /> - Contact: + Contact: Michal Hajduk @@ -589,17 +588,17 @@ channel.</li><li>Integrate voiceband infrastructure with Zaptel/DAHDI telephony hardware drivers.</li></ol><hr /><h2><a name="Grand-Central-Dispatch---FreeBSD-port" href="#Grand-Central-Dispatch---FreeBSD-port" id="Grand-Central-Dispatch---FreeBSD-port">Grand Central Dispatch - FreeBSD port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://libdispatch.macosforge.org/" title="http://libdispatch.macosforge.org/">GCD / libdispatch web page</a></td><td> URL: <a href="http://libdispatch.macosforge.org/" title="GCD / libdispatch web page">http://libdispatch.macosforge.org/</a></td></tr></table><p> - Contact: + Contact: Robert Watson <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>> <br /> - Contact: + Contact: Stacey Son <<a href="mailto:sson@FreeBSD.org">sson@FreeBSD.org</a>> <br /> - Contact: + Contact: libdispatch mailing list <<a href="mailto:libdispatch-dev@lists.macosforge.org">libdispatch-dev@lists.macosforge.org</a>> </p> @@ -638,12 +637,12 @@ from being modified to use libdispatch. </li></ol><hr /><h2><a name="libprocstat(3)---process-statistics" href="#libprocstat(3)---process-statistics" id="libprocstat(3)---process-statistics">libprocstat(3) - process statistics</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.freebsd.org/viewvc/base/projects/libprocstat/" title="http://svn.freebsd.org/viewvc/base/projects/libprocstat/">libprocstat repository</a></td><td> URL: <a href="http://svn.freebsd.org/viewvc/base/projects/libprocstat/" title="libprocstat repository">http://svn.freebsd.org/viewvc/base/projects/libprocstat/</a></td></tr></table><p> - Contact: + Contact: Stanislav Sedov <<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>> <br /> - Contact: + Contact: Ulf Lilleengen <<a href="mailto:lulf@FreeBSD.org">lulf@FreeBSD.org</a>> @@ -670,7 +669,7 @@ URL: <a href="http://wiki.freebsd.org/TheBsdDebugger" title="Wiki page">http://wiki.freebsd.org/TheBsdDebugger</a></td></tr><tr><td><a href="http://people.freebsd.org/~dfr/ngdb.git" title="http://people.freebsd.org/~dfr/ngdb.git">Repository</a></td><td> URL: <a href="http://people.freebsd.org/~dfr/ngdb.git" title="Repository">http://people.freebsd.org/~dfr/ngdb.git</a></td></tr><tr><td><a href="http://wiki.freebsd.org/200909DevSummit?action=AttachFile&do=view&target=NGDB-200909.pdf" title="http://wiki.freebsd.org/200909DevSummit?action=AttachFile&do=view&target=NGDB-200909.pdf">Slides</a></td><td> URL: <a href="http://wiki.freebsd.org/200909DevSummit?action=AttachFile&do=view&target=NGDB-200909.pdf" title="Slides">http://wiki.freebsd.org/200909DevSummit?action=AttachFile&do=view&target=NGDB-200909.pdf</a></td></tr></table><p> - Contact: + Contact: Doug Rabson <<a href="mailto:"></a>> @@ -692,7 +691,7 @@ maybe support for GDB's remote debugging protocol later.</p> <hr /><h2><a name="NFSv4-ACLs" href="#NFSv4-ACLs" id="NFSv4-ACLs">NFSv4 ACLs</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/NFSv4_ACLs" title="http://wiki.freebsd.org/NFSv4_ACLs"></a></td><td> URL: <a href="http://wiki.freebsd.org/NFSv4_ACLs" title="">http://wiki.freebsd.org/NFSv4_ACLs</a></td></tr></table><p> - Contact: + Contact: Edward Tomasz Napierala @@ -708,7 +707,7 @@ <h3>Open tasks:</h3><ol><li>UFS changes review</li><li>Support for NFSv4 ACLs in tar(1)</li></ol><hr /><h2><a name="The-Newcons-project" href="#The-Newcons-project" id="The-Newcons-project">The Newcons project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Newcons" title="http://wiki.FreeBSD.org/Newcons">Wiki page</a></td><td> URL: <a href="http://wiki.FreeBSD.org/Newcons" title="Wiki page">http://wiki.FreeBSD.org/Newcons</a></td></tr><tr><td><a href="http://people.freebsd.org/~ed/newcons/patches/" title="http://people.freebsd.org/~ed/newcons/patches/">Patchset</a></td><td> URL: <a href="http://people.freebsd.org/~ed/newcons/patches/" title="Patchset">http://people.freebsd.org/~ed/newcons/patches/</a></td></tr></table><p> - Contact: + Contact: Ed Schouten @@ -733,27 +732,27 @@ <h3>Open tasks:</h3><ol><li>Research needs to be done on DRM's codebase.</li><li>Syscons should already be migrated to TERM=xterm to make switching between drivers a bit easier.</li></ol><hr /><h2><a name="VirtualBox-on-FreeBSD" href="#VirtualBox-on-FreeBSD" id="VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/VirtualBox" title="http://wiki.freebsd.org/VirtualBox"></a></td><td> URL: <a href="http://wiki.freebsd.org/VirtualBox" title="">http://wiki.freebsd.org/VirtualBox</a></td></tr></table><p> - Contact: + Contact: Beat Gaetzi <<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>> <br /> - Contact: + Contact: Bernhard Froehlich <<a href="mailto:decke@bluelife.at">decke@bluelife.at</a>> <br /> - Contact: + Contact: Dennis Herrmann <<a href="mailto:dhn@FreeBSD.org">dhn@FreeBSD.org</a>> <br /> - Contact: + Contact: Juergen Lock <<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>> <br /> - Contact: + Contact: Martin Wilke <<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>> @@ -781,22 +780,22 @@ URL: <a href="http://wiki.FreeBSD.org/BugBusting" title="">http://wiki.FreeBSD.org/BugBusting</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="http://people.FreeBSD.org/~linimon/studies/prs/"></a></td><td> URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html"></a></td><td> URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="">http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html</a></td></tr></table><p> - Contact: + Contact: Gavin Atkinson <<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>> <br /> - Contact: + Contact: Mark Linimon <<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>> <br /> - Contact: + Contact: Remko Lodder <<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>> <br /> - Contact: + Contact: Volker Werth <<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>> @@ -856,19 +855,19 @@ URL: <a href="http://freebsd.kde.org" title="">http://freebsd.kde.org</a></td></tr><tr><td><a href="http://miwi.bsdcrew.de/category/kde/" title="http://miwi.bsdcrew.de/category/kde/"></a></td><td> URL: <a href="http://miwi.bsdcrew.de/category/kde/" title="">http://miwi.bsdcrew.de/category/kde/</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/tabthorpe/category/kde" title="http://blogs.freebsdish.org/tabthorpe/category/kde"></a></td><td> URL: <a href="http://blogs.freebsdish.org/tabthorpe/category/kde" title="">http://blogs.freebsdish.org/tabthorpe/category/kde</a></td></tr></table><p> - Contact: + Contact: Thomas Abthorpe <<a href="mailto:tabthorpe@FreeBSD.org">tabthorpe@FreeBSD.org</a>> <br /> - Contact: + Contact: Max Brazhnikov <<a href="mailto:makc@FreeBSD.org">makc@FreeBSD.org</a>> <br /> - Contact: + Contact: Martin Wilke @@ -897,7 +896,7 @@ URL: <a href="http://portsmon.FreeBSD.org/index.html" title="The FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td> URL: <a href="http://www.freebsd.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td> URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p> - Contact: + Contact: Mark Linimon <<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>> @@ -953,7 +952,7 @@ unmaintained ports. As well, the packages on amd64 and sparc64 lag behind i386, and we need more testers for those.</li></ol><hr /><h2><a name="Release-Engineering-Status-Report" href="#Release-Engineering-Status-Report" id="Release-Engineering-Status-Report">Release Engineering Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td> URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p> - Contact: + Contact: Release Engineering Team <<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>> </p> @@ -968,7 +967,7 @@ followed by the release late October or early November.</p> <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsdfoundation.org" title="http://www.freebsdfoundation.org"></a></td><td> URL: <a href="http://www.freebsdfoundation.org" title="">http://www.freebsdfoundation.org</a></td></tr></table><p> - Contact: + Contact: Deb Goodkin <<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>> @@ -997,7 +996,7 @@ URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.freebsdfoundation.org/projects.shtml" title="http://www.freebsdfoundation.org/projects.shtml"></a></td><td> URL: <a href="http://www.freebsdfoundation.org/projects.shtml" title="">http://www.freebsdfoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/" title="http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/"></a></td><td> URL: <a href="http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/" title="">http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/</a></td></tr></table><p> - Contact: + Contact: Lawrence Stewart <<a href="mailto:lstewart@freebsd.org">lstewart@freebsd.org</a>> @@ -1029,7 +1028,7 @@ </li></ol><hr /><h2><a name="Modular-Congestion-Control" href="#Modular-Congestion-Control" id="Modular-Congestion-Control">Modular Congestion Control</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td> URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/" title="http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/"></a></td><td> URL: <a href="http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/" title="">http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/</a></td></tr></table><p> - Contact: + Contact: Lawrence Stewart <<a href="mailto:lstewart@freebsd.org">lstewart@freebsd.org</a>> @@ -1052,17 +1051,17 @@ </li></ol><hr /><h2><a name="Network-Stack-Virtualization" href="#Network-Stack-Virtualization" id="Network-Stack-Virtualization">Network Stack Virtualization</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Image" title="http://wiki.freebsd.org/Image">Wiki VImage overview page (incl. TODO).</a></td><td> URL: <a href="http://wiki.freebsd.org/Image" title="Wiki VImage overview page (incl. TODO).">http://wiki.freebsd.org/Image</a></td></tr><tr><td><a href="http://wiki.freebsd.org/200909DevSummit" title="http://wiki.freebsd.org/200909DevSummit">FreeBSD Developer Summit, 2009, Cambridge, UK.</a></td><td> URL: <a href="http://wiki.freebsd.org/200909DevSummit" title="FreeBSD Developer Summit, 2009, Cambridge, UK.">http://wiki.freebsd.org/200909DevSummit</a></td></tr></table><p> - Contact: + Contact: Bjoern A. Zeeb <<a href="mailto:bz@FreeBSD.ORG">bz@FreeBSD.ORG</a>> <br /> - Contact: + Contact: Marko Zec <<a href="mailto:zec@FreeBSD.ORG">zec@FreeBSD.ORG</a>> <br /> - Contact: + Contact: Robert Watson <<a href="mailto:rwatson@FreeBSD.ORG">rwatson@FreeBSD.ORG</a>> @@ -1107,7 +1106,7 @@ like two firewalls, appletalk, netipx, ... as well as generating regression tests.</p> <hr /><h2><a name="Stream-Control-Transmission-Protocol-(SCTP)" href="#Stream-Control-Transmission-Protocol-(SCTP)" id="Stream-Control-Transmission-Protocol-(SCTP)">Stream Control Transmission Protocol (SCTP)</a></h2><p> - Contact: + Contact: Randall Stewart <<a href="mailto:rrs@FreeBSD">rrs@FreeBSD</a>> @@ -1130,7 +1129,7 @@ moonlights as a Professor at the University of Muenster in Germany (when not doing SCTP coding).</p> <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="FreeBSD/ZFS" href="#FreeBSD/ZFS" id="FreeBSD/ZFS">FreeBSD/ZFS</a></h2><p> - Contact: + Contact: Pawel Dawidek <<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>> @@ -1147,7 +1146,7 @@ </li></ol><hr /><h2><a name="hwpmc-for-MIPS" href="#hwpmc-for-MIPS" id="hwpmc-for-MIPS">hwpmc for MIPS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/FreeBSD/mips" title="http://wiki.freebsd.org/FreeBSD/mips">Main FreeBSD MIPS Page</a></td><td> URL: <a href="http://wiki.freebsd.org/FreeBSD/mips" title="Main FreeBSD MIPS Page">http://wiki.freebsd.org/FreeBSD/mips</a></td></tr><tr><td><a href="http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro" title="http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro">Sub page for the board I am using.</a></td><td> URL: <a href="http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro" title="Sub page for the board I am using.">http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro</a></td></tr></table><p> - Contact: + Contact: George Neville-Neil <<a href="mailto:gnn@freebsd.org">gnn@freebsd.org</a>> @@ -1157,13 +1156,13 @@ code soon.</p> <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-Dutch-Documentation-Project" href="#The-FreeBSD-Dutch-Documentation-Project" id="The-FreeBSD-Dutch-Documentation-Project">The FreeBSD Dutch Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.freebsd.org/docproj/translations.html#dutch" title="http://www.freebsd.org/docproj/translations.html#dutch">Current status of the Dutch translation</a></td><td> URL: <a href="http://www.freebsd.org/docproj/translations.html#dutch" title="Current status of the Dutch translation">http://www.freebsd.org/docproj/translations.html#dutch</a></td></tr></table><p> - Contact: + Contact: Ren Ladan <<a href="mailto:rene@FreeBSD.org">rene@FreeBSD.org</a>> <br /> - Contact: + Contact: Remko Lodder @@ -1178,19 +1177,19 @@ the website and the FAQ.</li></ol><hr /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://doc.bsdgroup.de" title="https://doc.bsdgroup.de"></a></td><td> URL: <a href="https://doc.bsdgroup.de" title="">https://doc.bsdgroup.de</a></td></tr><tr><td><a href="http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede" title="http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede"></a></td><td> URL: <a href="http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede" title="">http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede</a></td></tr></table><p> - Contact: + Contact: Johann Kois <<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>> <br /> - Contact: + Contact: Benedict Reuschling <<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>> <br /> - Contact: + Contact: Martin Wilke @@ -1225,13 +1224,13 @@ URL: <a href="http://www.FreeBSD.org/doc/hu" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td> URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for the FreeBSD Hungarian Documentation Project</a></td><td> URL: <a href="http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for the FreeBSD Hungarian Documentation Project">http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p> - Contact: + Contact: Gbor Kvesdn <<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>> <br /> - Contact: + Contact: Gbor Pli @@ -1250,13 +1249,13 @@ URL: <a href="http://www.FreeBSD.org/es" title="Spanish Web Page for FreeBSD">http://www.FreeBSD.org/es</a></td></tr><tr><td><a href="http://www.FreeBSD.org/doc/es" title="http://www.FreeBSD.org/doc/es">Spanish Documentation for FreeBSD</a></td><td> URL: <a href="http://www.FreeBSD.org/doc/es" title="Spanish Documentation for FreeBSD">http://www.FreeBSD.org/doc/es</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/es/articles/fdp-es/" title="http://www.freebsd.org/doc/es/articles/fdp-es/">Introduction to the FreeBSD Spanish Documentation Project</a></td><td> URL: <a href="http://www.freebsd.org/doc/es/articles/fdp-es/" title="Introduction to the FreeBSD Spanish Documentation Project">http://www.freebsd.org/doc/es/articles/fdp-es/</a></td></tr></table><p> - Contact: + Contact: Jos Vicente Carrasco Vay <<a href="mailto:carvay@FreeBSD.org">carvay@FreeBSD.org</a>> <br /> - Contact: + Contact: Gbor Kvesdn @@ -1267,7 +1266,7 @@ more human resources to keep up with the work and keep the translations up-to-date.</p> <h3>Open tasks:</h3><ol><li>Update the Handbook translation</li><li>Update the web page translation</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p> - Contact: + Contact: Marius Strobl @@ -1325,17 +1324,17 @@ </ul> <h3>Open tasks:</h3><ol></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Gecko-Project" href="#FreeBSD-Gecko-Project" id="FreeBSD-Gecko-Project">FreeBSD Gecko Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO" title="https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO">Gecko TODO</a></td><td> URL: <a href="https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO" title="Gecko TODO">https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO</a></td></tr></table><p> - Contact: + Contact: Beat Gaetzi <<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>> <br /> - Contact: + Contact: Martin Wilke <<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>> <br /> - Contact: + Contact: Andreas Tobler <<a href="mailto:andreast-list@fgznet.ch">andreast-list@fgznet.ch</a>> @@ -1352,7 +1351,7 @@ and has a lot of security vulnerabilities. We can use www/seamonkey instead.</li> - <li>www/xulrunner is superseeded by www/libxul.</li> + <li>www/xulrunner is superseded by www/libxul.</li> </ul> <p>A patch that includes the following changes has been tested on @@ -1374,7 +1373,7 @@ <h3>Open tasks:</h3><ol><li>Remove mozilla, xulrunner and firefox2 from the ports tree.</li><li>The www/firefox35 port should be moved to www/firefox.</li><li>The old (and somewhat stale) Gecko providers mozilla, nvu, xulrunner, flock and firefox also need to be removed.</li></ol><hr /><h2><a name="Portmaster---utility-to-assist-users-with-managing-ports" href="#Portmaster---utility-to-assist-users-with-managing-ports" id="Portmaster---utility-to-assist-users-with-managing-ports">Portmaster - utility to assist users with managing ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://dougbarton.us/portmaster.html" title="http://dougbarton.us/portmaster.html"></a></td><td> URL: <a href="http://dougbarton.us/portmaster.html" title="">http://dougbarton.us/portmaster.html</a></td></tr></table><p> - Contact: + Contact: Doug Barton <<a href="mailto:dougb@FreeBSD.org">dougb@FreeBSD.org</a>> @@ -1396,7 +1395,7 @@ another system.</p> <h3>Open tasks:</h3><ol><li>See the funding proposal.</li></ol><hr /><h2><a name="Valgrind-suite-on-FreeBSD" href="#Valgrind-suite-on-FreeBSD" id="Valgrind-suite-on-FreeBSD">Valgrind suite on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/Valgrind" title="http://wiki.freebsd.org/Valgrind">Valgrind Wiki page</a></td><td> URL: <a href="http://wiki.freebsd.org/Valgrind" title="Valgrind Wiki page">http://wiki.freebsd.org/Valgrind</a></td></tr></table><p> - Contact: + Contact: Stanislav Sedov <<a href="mailto:stas@FreeBSD.org">stas@FreeBSD.org</a>> @@ -1419,13 +1418,13 @@ </li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="EuroBSDcon-2009" href="#EuroBSDcon-2009" id="EuroBSDcon-2009">EuroBSDcon 2009</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2009.eurobsdcon.org/" title="http://2009.eurobsdcon.org/">2009</a></td><td> URL: <a href="http://2009.eurobsdcon.org/" title="2009">http://2009.eurobsdcon.org/</a></td></tr><tr><td><a href="http://2010.eurobsdcon.org/" title="http://2010.eurobsdcon.org/">2010</a></td><td> URL: <a href="http://2010.eurobsdcon.org/" title="2010">http://2010.eurobsdcon.org/</a></td></tr></table><p> - Contact: + Contact: Sam Smith <<a href="mailto:eurobsdcon@ukuug.org">eurobsdcon@ukuug.org</a>> <br /> - Contact: + Contact: Robert Watson @@ -1442,7 +1441,7 @@ </p> <hr /><h2><a name="FreeBSD-Developer-Summit,-Cambridge-UK" href="#FreeBSD-Developer-Summit,-Cambridge-UK" id="FreeBSD-Developer-Summit,-Cambridge-UK">FreeBSD Developer Summit, Cambridge UK</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/200909DevSummit" title="http://wiki.FreeBSD.org/200909DevSummit"></a></td><td> URL: <a href="http://wiki.FreeBSD.org/200909DevSummit" title="">http://wiki.FreeBSD.org/200909DevSummit</a></td></tr></table><p> - Contact: + Contact: Robert Watson <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>> @@ -1463,13 +1462,13 @@ <hr /><h2><a name="New-approach-to-the-locale-database" href="#New-approach-to-the-locale-database" id="New-approach-to-the-locale-database">New approach to the locale database</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.freebsd.org/LocaleNewApproach" title="http://wiki.freebsd.org/LocaleNewApproach">Documentation on FreeBSD wiki</a></td><td> URL: <a href="http://wiki.freebsd.org/LocaleNewApproach" title="Documentation on FreeBSD wiki">http://wiki.freebsd.org/LocaleNewApproach</a></td></tr><tr><td><a href="svn://svn.freebsd.org/base/user/edwin/locale" title="svn://svn.freebsd.org/base/user/edwin/locale">Code</a></td><td> URL: <a href="svn://svn.freebsd.org/base/user/edwin/locale" title="Code">svn://svn.freebsd.org/base/user/edwin/locale</a></td></tr></table><p> - Contact: + Contact: Edwin Groothuis <<a href="mailto:edwin@FreeBSD.org">edwin@FreeBSD.org</a>> <br /> - Contact: + Contact: i18n mailinglist @@ -1508,13 +1507,13 @@ Unicode text format to the required formats and character sets.</li></ol><hr /><h2><a name="The-FreeBSD-Forums" href="#The-FreeBSD-Forums" id="The-FreeBSD-Forums">The FreeBSD Forums</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.freebsd.org/" title="http://forums.freebsd.org/"></a></td><td> URL: <a href="http://forums.freebsd.org/" title="">http://forums.freebsd.org/</a></td></tr></table><p> - Contact: + Contact: FreeBSD Forums Admins <<a href="mailto:forum-admins@FreeBSD.org">forum-admins@FreeBSD.org</a>> <br /> - Contact: + Contact: FreeBSD Forums Moderators diff --git a/website/content/en/status/report-2009-10-2009-12.html b/website/content/en/status/report-2009-10-2009-12.html index bf0b8e3905..a04cc49f05 100644 --- a/website/content/en/status/report-2009-10-2009-12.html +++ b/website/content/en/status/report-2009-10-2009-12.html @@ -6,7 +6,6 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" src="../../layout/js/google.js"></script> </head> <body> <div id="containerwrap"> @@ -280,7 +279,7 @@ happy and successful new year for 2010.</p><p>Please note that the deadline for submissions covering the period between January and March 2010 is April 15th, 2010.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#BSD-licensed-iconv">BSD-licensed iconv</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#3G-USB-support">3G USB support</a></li><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></li><li><a href="#HAST-—-Highly-Available-Storage">HAST — Highly Available Storage</a></li><li><a href="#Intel-XScale-hwpmc(9)-support">Intel XScale hwpmc(9) support</a></li><li><a href="#POSIX-utmpx-for-FreeBSD">POSIX utmpx for FreeBSD</a></li><li><a href="#SUJ-—-Journaled-SoftUpdates">SUJ — Journaled SoftUpdates</a></li><li><a href="#The-webcamd-deamon">The webcamd deamon</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></li><li><a href="#The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#bwn(4)-—-Broadcom-Wireless-driver">bwn(4) — Broadcom Wireless driver</a></li><li><a href="#IP-Payload-Compression-Protocol-support">IP Payload Compression Protocol support</a></li><li><a href="#Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver">Ralink wireless RT2700U/2800U/3000U run(4) USB driver</a></li><li><a href="#Syncing-pf(4)-with-OpenBSD-4.5">Syncing pf(4) with OpenBSD 4.5</a></li><li><a href="#Wireless-mesh-networking">Wireless mesh networking</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#CAM-based-ATA-implementation">CAM-based ATA implementation</a></li><li><a href="#Group-Limit-Increase">Group Limit Increase</a></li><li><a href="#NFSv4-ACL-support">NFSv4 ACL support</a></li><li><a href="#V4L-support-in-Linux-emulator">V4L support in Linux emulator</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li><li><a href="#The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Flattened-Device-Tree-for-embedded-FreeBSD">Flattened Device Tree for embedded FreeBSD</a></li><li><a href="#FreeBSD/ia64">FreeBSD/ia64</a></li><li><a href="#FreeBSD/mips">FreeBSD/mips</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium-web-browser">Chromium web browser</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></li></ul><h3><a href="#Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h3><ul><li><a href="#DAHDI-(Zaptel)-support-for-FreeBSD">DAHDI (Zaptel) support for FreeBSD</a></li><li><a href="#NVIDIA-amd64-driver">NVIDIA amd64 driver</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#AsiaBSDCon-2010-—-The-BSD-Conference">AsiaBSDCon 2010 — The BSD Conference</a></li><li><a href="#BSDCan-2010-—-The-BSD-Conference">BSDCan 2010 — The BSD Conference</a></li><li><a href="#meetBSD-2010-—-The-BSD-Conference">meetBSD 2010 — The BSD Conference</a></li><li><a href="#The-FreeBSD-Forums">The FreeBSD Forums</a></li></ul><h3><a href="#Userland-utilities">Userland utilities</a></h3><ul><li><a href="#BSD-licensed-text-processing-tools">BSD-licensed text processing tools</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="BSD-licensed-iconv" href="#BSD-licensed-iconv" id="BSD-licensed-iconv">BSD-licensed iconv</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv">Sources in the Perforce repository</a></td><td> URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv" title="Sources in the Perforce repository">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2009/gabor_iconv</a></td></tr></table><p> - Contact: + Contact: Gbor Kvesdn <<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>> @@ -292,7 +291,7 @@ patch is expected at the beginning of February.</p> <h3>Open tasks:</h3><ol><li>Enhance conversion tables to make use of enhanced transliteration.</li><li>A performance optimization might be done later.</li></ol><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="3G-USB-support" href="#3G-USB-support" id="3G-USB-support">3G USB support</a></h2><p> - Contact: + Contact: Andrew Thompson @@ -312,22 +311,22 @@ after the future merge of this revision.</p> <hr /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"></a></td><td> URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr></table><p> - Contact: + Contact: Ed Schouten <<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>> <br /> - Contact: + Contact: Roman Divacky <<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>> <br /> - Contact: + Contact: Brooks Davis <<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>> <br /> - Contact: + Contact: Pawel Worach <<a href="mailto:pawel.worach@gmail.com">pawel.worach@gmail.com</a>> @@ -352,12 +351,12 @@ might be solved by either fixing this (short term) or using llvm-mc instead of GNU as for assembling (longer term).</p> <h3>Open tasks:</h3><ol><li>Help with ARM/MIPS/sparc64.</li><li>More testing of clang on 3rd party apps (ports).</li><li>Discussion on integrating LLVM/clang into FreeBSD.</li></ol><hr /><h2><a name="FreeBSD-TDM-Framework" href="#FreeBSD-TDM-Framework" id="FreeBSD-TDM-Framework">FreeBSD TDM Framework</a></h2><p> - Contact: + Contact: Rafal Czubak <<a href="mailto:rcz@semihalf.com">rcz@semihalf.com</a>> <br /> - Contact: + Contact: Michal Hajduk <<a href="mailto:mih@semihalf.com">mih@semihalf.com</a>> @@ -385,7 +384,7 @@ application.</li><li>Test Si3050 codec driver operation with PSTN.</li><li>Fully integrate voiceband infrastructure with Zaptel/DAHDI telephony hardware drivers.</li></ol><hr /><h2><a name="HAST-—-Highly-Available-Storage" href="#HAST-—-Highly-Available-Storage" id="HAST-—-Highly-Available-Storage">HAST — Highly Available Storage</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html" title="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html">Announcement</a></td><td> URL: <a href="http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html" title="Announcement">http://lists.FreeBSD.org/pipermail/freebsd-announce/2009-October/001279.html</a></td></tr></table><p> - Contact: + Contact: Pawel Jakub Dawidek @@ -416,7 +415,7 @@ <p>Thank you!</p> <hr /><h2><a name="Intel-XScale-hwpmc(9)-support" href="#Intel-XScale-hwpmc(9)-support" id="Intel-XScale-hwpmc(9)-support">Intel XScale hwpmc(9) support</a></h2><p> - Contact: + Contact: Rui Paulo <<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>> @@ -432,7 +431,7 @@ URL: <a href="http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html" title="POSIX specification">http://www.opengroup.org/onlinepubs/9699919799/functions/endutxent.html</a></td></tr><tr><td><a href="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c" title="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c">NetBSD's implementation</a></td><td> URL: <a href="http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c" title="NetBSD's implementation">http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/lib/libc/gen/utmpx.c</a></td></tr><tr><td><a href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c" title="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c">OpenSolaris' implementation</a></td><td> URL: <a href="http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c" title="OpenSolaris' implementation">http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getutx.c</a></td></tr></table><p> - Contact: + Contact: Ed Schouten <<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>> @@ -447,7 +446,7 @@ functions.</p> <h3>Open tasks:</h3><ol><li>Get a list of broken ports.</li><li>Fix them to comply to standards.</li><li>Send patches upstream.</li></ol><hr /><h2><a name="SUJ-—-Journaled-SoftUpdates" href="#SUJ-—-Journaled-SoftUpdates" id="SUJ-—-Journaled-SoftUpdates">SUJ — Journaled SoftUpdates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jeffr_tech.livejournal.com/" title="http://jeffr_tech.livejournal.com/"></a></td><td> URL: <a href="http://jeffr_tech.livejournal.com/" title="">http://jeffr_tech.livejournal.com/</a></td></tr></table><p> - Contact: + Contact: Jeff Roberson @@ -476,7 +475,7 @@ journal.</p> <hr /><h2><a name="The-webcamd-deamon" href="#The-webcamd-deamon" id="The-webcamd-deamon">The webcamd deamon</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.selasky.org/hans_petter/video4bsd/" title="http://www.selasky.org/hans_petter/video4bsd/"></a></td><td> URL: <a href="http://www.selasky.org/hans_petter/video4bsd/" title="">http://www.selasky.org/hans_petter/video4bsd/</a></td></tr></table><p> - Contact: + Contact: Hans Petter Selasky @@ -495,22 +494,22 @@ URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/" title="Experimental report pages">http://people.FreeBSD.org/~linimon/studies/prs/</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html">PRs recommended for committer evaluation by the bugbusting team</a></td><td> URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html" title="PRs recommended for committer evaluation by the bugbusting team">http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt" title="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt">Subscription list for the above report)</a></td><td> URL: <a href="http://people.FreeBSD.org/~linimon/recommended_subscribers.txt" title="Subscription list for the above report)">http://people.FreeBSD.org/~linimon/recommended_subscribers.txt</a></td></tr></table><p> - Contact: + Contact: Gavin Atkinson <<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>> <br /> - Contact: + Contact: Mark Linimon <<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>> <br /> - Contact: + Contact: Remko Lodder <<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>> <br /> - Contact: + Contact: Volker Werth <<a href="mailto:vwe@FreeBSD.org">vwe@FreeBSD.org</a>> @@ -547,7 +546,7 @@ <h3>Open tasks:</h3><ol><li>Try to find ways to get more committers helping us with closing PRs that the team has already analyzed.</li></ol><hr /><h2><a name="FreeBSD-Release-Engineering" href="#FreeBSD-Release-Engineering" id="FreeBSD-Release-Engineering">FreeBSD Release Engineering</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td> URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p> - Contact: + Contact: Release Engineering Team <<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>> </p> @@ -564,7 +563,7 @@ <hr /><h2><a name="The-FreeBSD-Foundation-Status-Report" href="#The-FreeBSD-Foundation-Status-Report" id="The-FreeBSD-Foundation-Status-Report">The FreeBSD Foundation Status Report</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/">The FreeBSD Foundation</a></td><td> URL: <a href="http://www.FreeBSDFoundation.org/" title="The FreeBSD Foundation">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="https://twitter.com/freebsdfndation" title="https://twitter.com/freebsdfndation">Follow us on Twitter</a></td><td> URL: <a href="https://twitter.com/freebsdfndation" title="Follow us on Twitter">https://twitter.com/freebsdfndation</a></td></tr></table><p> - Contact: + Contact: Deb Goodkin <<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>> @@ -594,7 +593,7 @@ <p>We are fund-raising for 2010 now! Find out more at <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect">http://www.FreeBSDFoundation.org/donate/</a>.</p> <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="bwn(4)-—-Broadcom-Wireless-driver" href="#bwn(4)-—-Broadcom-Wireless-driver" id="bwn(4)-—-Broadcom-Wireless-driver">bwn(4) — Broadcom Wireless driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&HIDEDEL=NO" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&HIDEDEL=NO">bwn(4) sources in P4</a></td><td> URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&HIDEDEL=NO" title="bwn(4) sources in P4">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/weongyo/wireless/src/sys/dev/bwn&HIDEDEL=NO</a></td></tr></table><p> - Contact: + Contact: Weongyo Jeong <<a href="mailto:weongyo@FreeBSD.org">weongyo@FreeBSD.org</a>> @@ -629,7 +628,7 @@ DMA operation with STA mode. A major patch for siba(4) is being reviewed before committing into 9.0-CURRENT.</p> <h3>Open tasks:</h3><ol><li>MESH/IBSS/HOSTAP mode is not supported.</li><li>LP/N PHYs are not supported.</li></ol><hr /><h2><a name="IP-Payload-Compression-Protocol-support" href="#IP-Payload-Compression-Protocol-support" id="IP-Payload-Compression-Protocol-support">IP Payload Compression Protocol support</a></h2><p> - Contact: + Contact: Bjoern A. Zeeb <<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>> @@ -661,7 +660,7 @@ on an up-to-date unified zlib version in the kernel, which would also fix the last occasional IPcomp hiccups.</li></ol><hr /><h2><a name="Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver" href="#Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver" id="Ralink-wireless-RT2700U/2800U/3000U-run(4)-USB-driver">Ralink wireless RT2700U/2800U/3000U run(4) USB driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.FreeBSD.org/showthread.php?t=7562" title="http://forums.FreeBSD.org/showthread.php?t=7562">Announcement on the FreeBSD Forums</a></td><td> URL: <a href="http://forums.FreeBSD.org/showthread.php?t=7562" title="Announcement on the FreeBSD Forums">http://forums.FreeBSD.org/showthread.php?t=7562</a></td></tr></table><p> - Contact: + Contact: Akinori Furukoshi @@ -679,7 +678,7 @@ it.</li><li>Maintain the code.</li></ol><hr /><h2><a name="Syncing-pf(4)-with-OpenBSD-4.5" href="#Syncing-pf(4)-with-OpenBSD-4.5" id="Syncing-pf(4)-with-OpenBSD-4.5">Syncing pf(4) with OpenBSD 4.5</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/" title="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/">Viewing the changes.</a></td><td> URL: <a href="http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/" title="Viewing the changes.">http://svn.FreeBSD.org/viewvc/base/user/eri/pf45/</a></td></tr><tr><td><a href="http://svn.FreeBSD.org/base/user/eri/pf45/head/" title="http://svn.FreeBSD.org/base/user/eri/pf45/head/">The actual repo to build from.</a></td><td> URL: <a href="http://svn.FreeBSD.org/base/user/eri/pf45/head/" title="The actual repo to build from.">http://svn.FreeBSD.org/base/user/eri/pf45/head/</a></td></tr></table><p> - Contact: + Contact: Ermal Luçi @@ -696,7 +695,7 @@ <h3>Open tasks:</h3><ol><li>pflow(4)/pflog(4)/pfsync(4) need to be made VIMAGE aware.</li><li>More regression testing is needed.</li></ol><hr /><h2><a name="Wireless-mesh-networking" href="#Wireless-mesh-networking" id="Wireless-mesh-networking">Wireless mesh networking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/WifiMesh" title="http://wiki.FreeBSD.org/WifiMesh"></a></td><td> URL: <a href="http://wiki.FreeBSD.org/WifiMesh" title="">http://wiki.FreeBSD.org/WifiMesh</a></td></tr></table><p> - Contact: + Contact: Rui Paulo <<a href="mailto:rpaulo@FreeBSD.org">rpaulo@FreeBSD.org</a>> @@ -709,13 +708,13 @@ link security algorithms and/or coordinated channel access (performance improvement).</p> <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="CAM-based-ATA-implementation" href="#CAM-based-ATA-implementation" id="CAM-based-ATA-implementation">CAM-based ATA implementation</a></h2><p> - Contact: + Contact: Alexander Motin <<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>> <br /> - Contact: + Contact: Scott Long @@ -759,7 +758,7 @@ desired). SAS controllers can support SATA devices and multipliers, so it should fit nicely into the new infrastructure.</li></ol><hr /><h2><a name="Group-Limit-Increase" href="#Group-Limit-Increase" id="Group-Limit-Increase">Group Limit Increase</a></h2><p> - Contact: + Contact: Brooks Davis <<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>> @@ -778,7 +777,7 @@ 8.1-RELEASE.</p> <hr /><h2><a name="NFSv4-ACL-support" href="#NFSv4-ACL-support" id="NFSv4-ACL-support">NFSv4 ACL support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/NFSv4_ACLs" title="http://wiki.FreeBSD.org/NFSv4_ACLs"></a></td><td> URL: <a href="http://wiki.FreeBSD.org/NFSv4_ACLs" title="">http://wiki.FreeBSD.org/NFSv4_ACLs</a></td></tr></table><p> - Contact: + Contact: Edward Tomasz Napierala @@ -788,7 +787,7 @@ is expected to be MFCed in order to make it into FreeBSD 8.1-RELEASE.</p> <h3>Open tasks:</h3><ol><li>Support for NFSv4 ACLs in tar(1).</li><li>MFC.</li></ol><hr /><h2><a name="V4L-support-in-Linux-emulator" href="#V4L-support-in-Linux-emulator" id="V4L-support-in-Linux-emulator">V4L support in Linux emulator</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://opal.com/freebsd/sys/compat/linux/" title="http://opal.com/freebsd/sys/compat/linux/"></a></td><td> URL: <a href="http://opal.com/freebsd/sys/compat/linux/" title="">http://opal.com/freebsd/sys/compat/linux/</a></td></tr></table><p> - Contact: + Contact: J.R. Oldroyd @@ -812,19 +811,19 @@ will need to enhance that driver to add V4L support.</p> <hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de">German Documentation Project Homepage</a></td><td> URL: <a href="http://doc.bsdgroup.de" title="German Documentation Project Homepage">http://doc.bsdgroup.de</a></td></tr></table><p> - Contact: + Contact: Johann Kois <<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>> <br /> - Contact: + Contact: Benedict Reuschling <<a href="mailto:bcr@FreeBSD.org">bcr@FreeBSD.org</a>> <br /> - Contact: + Contact: Martin Wilke @@ -865,12 +864,12 @@ URL: <a href="http://www.FreeBSD.org/doc/hu/" title="Hungarian Documentation for FreeBSD">http://www.FreeBSD.org/doc/hu/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Wiki Page</a></td><td> URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Wiki Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83">Perforce Depot for the FreeBSD Hungarian Documentation Project</a></td><td> URL: <a href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83" title="Perforce Depot for the FreeBSD Hungarian Documentation Project">http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p> - Contact: + Contact: Gbor Kvesdn <<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>> <br /> - Contact: + Contact: Gbor Pli <<a href="mailto:pgj@FreeBSD.org">pgj@FreeBSD.org</a>> @@ -883,7 +882,7 @@ <h3>Open tasks:</h3><ol><li>Translate release notes.</li><li>Add more article translations.</li></ol><hr /><h2><a name="The-FreeBSD-Spanish-Documentation-Project" href="#The-FreeBSD-Spanish-Documentation-Project" id="The-FreeBSD-Spanish-Documentation-Project">The FreeBSD Spanish Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/doc/es/articles/fdp-es/" title="http://www.FreeBSD.org/doc/es/articles/fdp-es/">Introduction to the Spanish Documentation Project</a></td><td> URL: <a href="http://www.FreeBSD.org/doc/es/articles/fdp-es/" title="Introduction to the Spanish Documentation Project">http://www.FreeBSD.org/doc/es/articles/fdp-es/</a></td></tr><tr><td><a href="https://listas.es.FreeBSD.org/mailman/listinfo/doc" title="https://listas.es.FreeBSD.org/mailman/listinfo/doc">Translators' Mailing List</a></td><td> URL: <a href="https://listas.es.FreeBSD.org/mailman/listinfo/doc" title="Translators' Mailing List">https://listas.es.FreeBSD.org/mailman/listinfo/doc</a></td></tr></table><p> - Contact: + Contact: Gbor Kvesdn <<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>> @@ -896,7 +895,7 @@ <h3>Open tasks:</h3><ol><li>Update Handbook translation.</li><li>Update webpage translation.</li><li>Add more article translations.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Flattened-Device-Tree-for-embedded-FreeBSD" href="#Flattened-Device-Tree-for-embedded-FreeBSD" id="Flattened-Device-Tree-for-embedded-FreeBSD">Flattened Device Tree for embedded FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/FlattenedDeviceTree" title="http://wiki.FreeBSD.org/FlattenedDeviceTree">Project wiki pages</a></td><td> URL: <a href="http://wiki.FreeBSD.org/FlattenedDeviceTree" title="Project wiki pages">http://wiki.FreeBSD.org/FlattenedDeviceTree</a></td></tr><tr><td><a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/..." title="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/...">Project P4 branch</a></td><td> URL: <a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/..." title="Project P4 branch">http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/fdt/...</a></td></tr></table><p> - Contact: + Contact: Rafal Jaworowski <<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>> @@ -961,7 +960,7 @@ <p>Work on this project has been sponsored by the FreeBSD Foundation.</p> <h3>Open tasks:</h3><ol><li>Complete missing pieces for PowerPC (PCI bridge driver conversion to FDT).</li><li>Complete ARM support.</li><li>Merge to SVN.</li></ol><hr /><h2><a name="FreeBSD/ia64" href="#FreeBSD/ia64" id="FreeBSD/ia64">FreeBSD/ia64</a></h2><p> - Contact: + Contact: Marcel Moolenaar <<a href="mailto:marcel@FreeBSD.org">marcel@FreeBSD.org</a>> @@ -993,11 +992,11 @@ and bringing them up-to-date.</li></ol><hr /><h2><a name="FreeBSD/mips" href="#FreeBSD/mips" id="FreeBSD/mips">FreeBSD/mips</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/projects/mips/index.html" title="http://www.FreeBSD.org/projects/mips/index.html"></a></td><td> URL: <a href="http://www.FreeBSD.org/projects/mips/index.html" title="">http://www.FreeBSD.org/projects/mips/index.html</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/FreeBSD/mips" title="http://wiki.FreeBSD.org/FreeBSD/mips"></a></td><td> URL: <a href="http://wiki.FreeBSD.org/FreeBSD/mips" title="">http://wiki.FreeBSD.org/FreeBSD/mips</a></td></tr></table><p> - Contact: + Contact: The FreeBSD/mips mailing list <<a href="mailto:mips@FreeBSD.org">mips@FreeBSD.org</a>> <br /> - Contact: + Contact: Warner Losh @@ -1080,7 +1079,7 @@ <h3>Open tasks:</h3><ol><li>We are still investigating how feasible merging all this work into 8-STABLE will be, as it represents a huge leap forward in code stability and quality.</li></ol><hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p> - Contact: + Contact: Marius Strobl @@ -1120,7 +1119,7 @@ <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Chromium-web-browser" href="#Chromium-web-browser" id="Chromium-web-browser">Chromium web browser</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://chromium.jaggeri.com" title="http://chromium.jaggeri.com">test builds and port progress</a></td><td> URL: <a href="http://chromium.jaggeri.com" title="test builds and port progress">http://chromium.jaggeri.com</a></td></tr><tr><td><a href="http://www.links.org/?p=724" title="http://www.links.org/?p=724">first build information</a></td><td> URL: <a href="http://www.links.org/?p=724" title="first build information">http://www.links.org/?p=724</a></td></tr></table><p> - Contact: + Contact: Ben Laurie @@ -1141,7 +1140,7 @@ URL: <a href="http://portsmon.FreeBSD.org/index.html" title="FreeBSD ports monitoring system">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html">The FreeBSD Ports Management Team</a></td><td> URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="The FreeBSD Ports Management Team">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com" title="http://tinderbox.marcuscom.com">marcuscom Tinderbox</a></td><td> URL: <a href="http://tinderbox.marcuscom.com" title="marcuscom Tinderbox">http://tinderbox.marcuscom.com</a></td></tr></table><p> - Contact: + Contact: Mark Linimon @@ -1203,22 +1202,22 @@ unmaintained ports. As well, the packages on amd64 and especially sparc64 lag behind i386, and we need more testers for those.</li></ol><hr /><h2><a name="VirtualBox-on-FreeBSD" href="#VirtualBox-on-FreeBSD" id="VirtualBox-on-FreeBSD">VirtualBox on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/VirtualBox" title="http://wiki.FreeBSD.org/VirtualBox"></a></td><td> URL: <a href="http://wiki.FreeBSD.org/VirtualBox" title="">http://wiki.FreeBSD.org/VirtualBox</a></td></tr></table><p> - Contact: + Contact: Beat Gaetzi <<a href="mailto:beat@FreeBSD.org">beat@FreeBSD.org</a>> <br /> - Contact: + Contact: Bernhard Froehlich <<a href="mailto:decke@bluelife.at">decke@bluelife.at</a>> <br /> - Contact: + Contact: Juergen Lock <<a href="mailto:nox@FreeBSD.org">nox@FreeBSD.org</a>> <br /> - Contact: + Contact: Martin Wilke <<a href="mailto:miwi@FreeBSD.org">miwi@FreeBSD.org</a>> @@ -1266,7 +1265,7 @@ <hr /><br /><h1><a name="Vendor-/-3rd-Party-Software" href="#Vendor-/-3rd-Party-Software" id="Vendor-/-3rd-Party-Software">Vendor / 3rd Party Software</a></h1><br /><h2><a name="DAHDI-(Zaptel)-support-for-FreeBSD" href="#DAHDI-(Zaptel)-support-for-FreeBSD" id="DAHDI-(Zaptel)-support-for-FreeBSD">DAHDI (Zaptel) support for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html" title="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html">Official Announcement</a></td><td> URL: <a href="http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html" title="Official Announcement">http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg39598.html</a></td></tr><tr><td><a href="http://svn.digium.com/svn/dahdi/freebsd/trunk/" title="http://svn.digium.com/svn/dahdi/freebsd/trunk/">SVN repository</a></td><td> URL: <a href="http://svn.digium.com/svn/dahdi/freebsd/trunk/" title="SVN repository">http://svn.digium.com/svn/dahdi/freebsd/trunk/</a></td></tr></table><p> - Contact: + Contact: Max Khon @@ -1325,7 +1324,7 @@ let me know if you can provide a remote access or donate a card.</li></ol><hr /><h2><a name="NVIDIA-amd64-driver" href="#NVIDIA-amd64-driver" id="NVIDIA-amd64-driver">NVIDIA amd64 driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nvnews.net/vbulletin/showthread.php?t=142120" title="http://www.nvnews.net/vbulletin/showthread.php?t=142120">Release Announcement</a></td><td> URL: <a href="http://www.nvnews.net/vbulletin/showthread.php?t=142120" title="Release Announcement">http://www.nvnews.net/vbulletin/showthread.php?t=142120</a></td></tr></table><p> - Contact: + Contact: John Baldwin <<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>> @@ -1337,7 +1336,7 @@ official release announcement.</p> <hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="AsiaBSDCon-2010-—-The-BSD-Conference" href="#AsiaBSDCon-2010-—-The-BSD-Conference" id="AsiaBSDCon-2010-—-The-BSD-Conference">AsiaBSDCon 2010 — The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://2010.AsiaBSDCon.org/" title="http://2010.AsiaBSDCon.org/"></a></td><td> URL: <a href="http://2010.AsiaBSDCon.org/" title="">http://2010.AsiaBSDCon.org/</a></td></tr></table><p> - Contact: + Contact: AsiaBSDCon Information <<a href="mailto:secretary@AsiaBSDCon.org">secretary@AsiaBSDCon.org</a>> </p> @@ -1357,7 +1356,7 @@ web site.</p> <hr /><h2><a name="BSDCan-2010-—-The-BSD-Conference" href="#BSDCan-2010-—-The-BSD-Conference" id="BSDCan-2010-—-The-BSD-Conference">BSDCan 2010 — The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.BSDCan.org/2010/" title="http://www.BSDCan.org/2010/"></a></td><td> URL: <a href="http://www.BSDCan.org/2010/" title="">http://www.BSDCan.org/2010/</a></td></tr></table><p> - Contact: + Contact: BSDCan Information <<a href="mailto:info@BSDCan.org">info@BSDCan.org</a>> </p> @@ -1378,7 +1377,7 @@ <p>Please check the conference web site for more information.</p> <hr /><h2><a name="meetBSD-2010-—-The-BSD-Conference" href="#meetBSD-2010-—-The-BSD-Conference" id="meetBSD-2010-—-The-BSD-Conference">meetBSD 2010 — The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.meetBSD.org" title="http://www.meetBSD.org"></a></td><td> URL: <a href="http://www.meetBSD.org" title="">http://www.meetBSD.org</a></td></tr></table><p> - Contact: + Contact: meetBSD Information <<a href="mailto:info@meetBSD.org">info@meetBSD.org</a>> @@ -1395,13 +1394,13 @@ <p>See the conference main web site for more details.</p> <hr /><h2><a name="The-FreeBSD-Forums" href="#The-FreeBSD-Forums" id="The-FreeBSD-Forums">The FreeBSD Forums</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://forums.FreeBSD.org/" title="http://forums.FreeBSD.org/"></a></td><td> URL: <a href="http://forums.FreeBSD.org/" title="">http://forums.FreeBSD.org/</a></td></tr></table><p> - Contact: + Contact: FreeBSD Forums Admins <<a href="mailto:forum-admins@FreeBSD.org">forum-admins@FreeBSD.org</a>> <br /> - Contact: + Contact: FreeBSD Forums Moderators @@ -1431,7 +1430,7 @@ FreeBSD.</p> <hr /><br /><h1><a name="Userland-utilities" href="#Userland-utilities" id="Userland-utilities">Userland utilities</a></h1><br /><h2><a name="BSD-licensed-text-processing-tools" href="#BSD-licensed-text-processing-tools" id="BSD-licensed-text-processing-tools">BSD-licensed text processing tools</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc" title="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc">Perforce repository</a></td><td> URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc" title="Perforce repository">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/soc2008/gabor_textproc</a></td></tr></table><p> - Contact: + Contact: Gbor Kvesdn <<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>> diff --git a/website/content/en/status/report-2010-01-2010-03.html b/website/content/en/status/report-2010-01-2010-03.html index b0c8d9d3d6..8637964d80 100644 --- a/website/content/en/status/report-2010-01-2010-03.html +++ b/website/content/en/status/report-2010-01-2010-03.html @@ -6,7 +6,6 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" src="../../layout/js/google.js"></script> </head> <body> <div id="containerwrap"> @@ -283,13 +282,13 @@ period between April and June 2010 is July 15th, 2010.</p><hr /><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Google-Summer-of-Code-2010">Google Summer of Code 2010</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Chromium-web-browser">Chromium web browser</a></li><li><a href="#Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></li><li><a href="#EFI-support-for-FreeBSD/i386">EFI support for FreeBSD/i386</a></li><li><a href="#mfsBSD">mfsBSD</a></li><li><a href="#Modular-Congestion-Control">Modular Congestion Control</a></li><li><a href="#NAND-Flash-framework-for-embedded-FreeBSD">NAND Flash framework for embedded FreeBSD</a></li><li><a href="#Out-of-Tree-Toolchain">Out of Tree Toolchain</a></li><li><a href="#PC-BSD-PC-SysInstall-Backend">PC-BSD PC-SysInstall Backend</a></li><li><a href="#The-tbemd-branch">The tbemd branch</a></li><li><a href="#webcamd">webcamd</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Bugbusting-Team">FreeBSD Bugbusting Team</a></li><li><a href="#Release-Engineering-Team">Release Engineering Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#(Virtual)-Network-Stack-resource-cleanup">(Virtual) Network Stack resource cleanup</a></li><li><a href="#802.11n-support">802.11n support</a></li><li><a href="#Atheros-AR9285-support">Atheros AR9285 support</a></li><li><a href="#Enhancing-the-FreeBSD-TCP-Implementation">Enhancing the FreeBSD TCP Implementation</a></li><li><a href="#Experimental-NFS-subsystem-(NFSv4)">Experimental NFS subsystem (NFSv4)</a></li><li><a href="#ipfw-and-dummynet-enhancements">ipfw and dummynet enhancements</a></li><li><a href="#net80211-rate-control-framework">net80211 rate control framework</a></li><li><a href="#TCP/UDP-connection-groups">TCP/UDP connection groups</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#CAM-based-ATA-implementation">CAM-based ATA implementation</a></li><li><a href="#Dynamic-Ticks-in-FreeBSD">Dynamic Ticks in FreeBSD</a></li><li><a href="#geom_sched">geom_sched</a></li><li><a href="#IPv6-without-legacy-IP-kernel">IPv6 without legacy IP kernel</a></li><li><a href="#Multichannel-playback-in-HDA-sound-driver-(snd_hda)">Multichannel playback in HDA sound driver (snd_hda)</a></li><li><a href="#Rewrite-of-FreeBSD-read/write-path-using-vnode-page">Rewrite of FreeBSD read/write path using vnode page</a></li><li><a href="#SUJ:-Journaled-Softupdates">SUJ: Journaled Softupdates</a></li><li><a href="#ZFS">ZFS</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></li><li><a href="#The-FreeBSD-Hungarian-Documentation-Project">The FreeBSD Hungarian Documentation Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#FreeBSD-port-for-libunwind">FreeBSD port for libunwind</a></li><li><a href="#LDAP-support-in-base-system">LDAP support in base system</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm-port-for-TI-DaVinci">FreeBSD/arm port for TI DaVinci</a></li><li><a href="#FreeBSD/ia64">FreeBSD/ia64</a></li><li><a href="#FreeBSD/mips-on-D-Link-DIR-320">FreeBSD/mips on D-Link DIR-320</a></li><li><a href="#FreeBSD/powerpc">FreeBSD/powerpc</a></li><li><a href="#FreeBSD/powerpc64-port">FreeBSD/powerpc64 port</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Portmaster">Portmaster</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#QAT">QAT</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSDCan-2010-—-The-BSD-Conference">BSDCan 2010 — The BSD Conference</a></li><li><a href="#meetBSD-2010----The-BSD-Conference">meetBSD 2010 -- The BSD Conference</a></li></ul><ul></ul><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Google-Summer-of-Code-2010" href="#Google-Summer-of-Code-2010" id="Google-Summer-of-Code-2010">Google Summer of Code 2010</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://socghop.appspot.com/org/home/google/gsoc2010/freebsd" title="http://socghop.appspot.com/org/home/google/gsoc2010/freebsd">FreeBSD GSoC Homepage</a></td><td> URL: <a href="http://socghop.appspot.com/org/home/google/gsoc2010/freebsd" title="FreeBSD GSoC Homepage">http://socghop.appspot.com/org/home/google/gsoc2010/freebsd</a></td></tr><tr><td><a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline" title="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline">GSoC Timeline</a></td><td> URL: <a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline" title="GSoC Timeline">http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline</a></td></tr></table><p> - Contact: + Contact: Brooks Davis <<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>> <br /> - Contact: + Contact: Robert Watson @@ -304,7 +303,7 @@ <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="Chromium-web-browser" href="#Chromium-web-browser" id="Chromium-web-browser">Chromium web browser</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://chromium.jaggeri.com" title="http://chromium.jaggeri.com">Main chromium site</a></td><td> URL: <a href="http://chromium.jaggeri.com" title="Main chromium site">http://chromium.jaggeri.com</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/Chromium" title="http://wiki.FreeBSD.org/Chromium">Build instructions for older patches</a></td><td> URL: <a href="http://wiki.FreeBSD.org/Chromium" title="Build instructions for older patches">http://wiki.FreeBSD.org/Chromium</a></td></tr></table><p> - Contact: + Contact: sprewell <<a href="mailto:chromium@jaggeri.com">chromium@jaggeri.com</a>> </p> @@ -332,25 +331,25 @@ <hr /><h2><a name="Clang-replacing-GCC-in-the-base-system" href="#Clang-replacing-GCC-in-the-base-system" id="Clang-replacing-GCC-in-the-base-system">Clang replacing GCC in the base system</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang"></a></td><td> URL: <a href="http://wiki.FreeBSD.org/BuildingFreeBSDWithClang" title="">http://wiki.FreeBSD.org/BuildingFreeBSDWithClang</a></td></tr><tr><td><a href="http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html" title="http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html"></a></td><td> URL: <a href="http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html" title="">http://lists.FreeBSD.org/pipermail/FreeBSD-current/2010-April/016648.html</a></td></tr></table><p> - Contact: + Contact: Ed Schouten <<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>> <br /> - Contact: + Contact: Roman Divacky <<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>> <br /> - Contact: + Contact: Brooks Davis <<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>> <br /> - Contact: + Contact: Pawel Worach @@ -376,7 +375,7 @@ <p>We need people to try out ClangBSD (see the wiki) and runtime test it. We also would appreciate help with other archs - namely ARM.</p> <h3>Open tasks:</h3><ol><li>Runtime test ClangBSD on amd64/i386.</li><li>Help with ARM/Mips/Sparc64.</li><li>More testing of clang on 3rd party apps (ports).</li><li>Discussion on integrating LLVM/clang into FreeBSD.</li></ol><hr /><h2><a name="EFI-support-for-FreeBSD/i386" href="#EFI-support-for-FreeBSD/i386" id="EFI-support-for-FreeBSD/i386">EFI support for FreeBSD/i386</a></h2><p> - Contact: + Contact: Rui Paulo @@ -387,7 +386,7 @@ now working on trying to boot a kernel.</p> <hr /><h2><a name="mfsBSD" href="#mfsBSD" id="mfsBSD">mfsBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://mfsbsd.vx.sk" title="http://mfsbsd.vx.sk"></a></td><td> URL: <a href="http://mfsbsd.vx.sk" title="">http://mfsbsd.vx.sk</a></td></tr></table><p> - Contact: + Contact: Martin Matuska @@ -410,7 +409,7 @@ prepares drives, sysinstall installs distribution).</li><li>Integrate toolset into FreeBSD source (tools?).</li></ol><hr /><h2><a name="Modular-Congestion-Control" href="#Modular-Congestion-Control" id="Modular-Congestion-Control">Modular Congestion Control</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/" title="http://caia.swin.edu.au/urp/newtcp/"></a></td><td> URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/" title="http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/"></a></td><td> URL: <a href="http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/" title="">http://svn.FreeBSD.org/viewvc/base/projects/tcp_cc_head/</a></td></tr></table><p> - Contact: + Contact: Lawrence Stewart @@ -425,13 +424,13 @@ <h3>Open tasks:</h3><ol><li>Solicit external testing.</li><li>Commit to head.</li></ol><hr /><h2><a name="NAND-Flash-framework-for-embedded-FreeBSD" href="#NAND-Flash-framework-for-embedded-FreeBSD" id="NAND-Flash-framework-for-embedded-FreeBSD">NAND Flash framework for embedded FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153" title="http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153">Project wiki pages</a></td><td> URL: <a href="http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153" title="Project wiki pages">http://wiki.FreeBSD.org/NAND#head-9a32aaa85046b2f9f9219e36ba34947ca47a4153</a></td></tr><tr><td><a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/..." title="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/...">Project P4 branch</a></td><td> URL: <a href="http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/..." title="Project P4 branch">http://p4db.FreeBSD.org/changeList.cgi?FSPC=//depot/projects/nand2/...</a></td></tr></table><p> - Contact: + Contact: Grzegorz Bernacki <<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>> <br /> - Contact: + Contact: Rafal Jaworowski @@ -482,7 +481,7 @@ </ul> <h3>Open tasks:</h3><ol><li>Extend interface with features / options suggested by early adopters of the code.</li><li>Complete, clean up, merge with HEAD.</li></ol><hr /><h2><a name="Out-of-Tree-Toolchain" href="#Out-of-Tree-Toolchain" id="Out-of-Tree-Toolchain">Out of Tree Toolchain</a></h2><p> - Contact: + Contact: Warner Losh @@ -505,7 +504,7 @@ this.</li></ol><hr /><h2><a name="PC-BSD-PC-SysInstall-Backend" href="#PC-BSD-PC-SysInstall-Backend" id="PC-BSD-PC-SysInstall-Backend">PC-BSD PC-SysInstall Backend</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.pcbsd.org" title="http://www.pcbsd.org"></a></td><td> URL: <a href="http://www.pcbsd.org" title="">http://www.pcbsd.org</a></td></tr><tr><td><a href="http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall" title="http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall">pc-sysinstall in Trac</a></td><td> URL: <a href="http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall" title="pc-sysinstall in Trac">http://trac.pcbsd.org/browser/pcbsd/trunk/pc-sysinstall</a></td></tr></table><p> - Contact: + Contact: Kris Moore <<a href="mailto:kmoore@FreeBSD.org">kmoore@FreeBSD.org</a>> @@ -526,7 +525,7 @@ <h3>Open tasks:</h3><ol><li>We are mostly finished migrating to only using gpart instead of fdisk, which gives us some new functionality for dealing with GPT/EFI partitioning schemes.</li></ol><hr /><h2><a name="The-tbemd-branch" href="#The-tbemd-branch" id="The-tbemd-branch">The tbemd branch</a></h2><p> - Contact: + Contact: Warner Losh @@ -565,7 +564,7 @@ collapse.</li><li>Documentation needs to be written for how to use all of this.</li></ol><hr /><h2><a name="webcamd" href="#webcamd" id="webcamd">webcamd</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.selasky.org/hans_petter/video4bsd/" title="http://www.selasky.org/hans_petter/video4bsd/"></a></td><td> URL: <a href="http://www.selasky.org/hans_petter/video4bsd/" title="">http://www.selasky.org/hans_petter/video4bsd/</a></td></tr></table><p> - Contact: + Contact: Hans Petter Selasky @@ -594,25 +593,25 @@ URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html" title="PRs considered 'easy' by the bugbusting team (these are low-hanging fruit)">http://people.FreeBSD.org/~linimon/studies/prs/easy_prs.html</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html" title="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html">summary chart of PRs with tags</a></td><td> URL: <a href="http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html" title="summary chart of PRs with tags">http://people.FreeBSD.org/~linimon/studies/prs/prs_for_all_groups.html</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/AssigningPRs" title="http://wiki.FreeBSD.org/AssigningPRs">Assigning PRs</a></td><td> URL: <a href="http://wiki.FreeBSD.org/AssigningPRs" title="Assigning PRs">http://wiki.FreeBSD.org/AssigningPRs</a></td></tr></table><p> - Contact: + Contact: Gavin Atkinson <<a href="mailto:gavin@FreeBSD.org">gavin@FreeBSD.org</a>> <br /> - Contact: + Contact: Mark Linimon <<a href="mailto:linimon@FreeBSD.org">linimon@FreeBSD.org</a>> <br /> - Contact: + Contact: Remko Lodder <<a href="mailto:remko@FreeBSD.org">remko@FreeBSD.org</a>> <br /> - Contact: + Contact: Volker Werth @@ -670,7 +669,7 @@ by.</li><li>try to find ways to get more committers helping us with closing PRs that the team has already analyzed.</li></ol><hr /><h2><a name="Release-Engineering-Team" href="#Release-Engineering-Team" id="Release-Engineering-Team">Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/releng/" title="http://www.FreeBSD.org/releng/"></a></td><td> URL: <a href="http://www.FreeBSD.org/releng/" title="">http://www.FreeBSD.org/releng/</a></td></tr></table><p> - Contact: + Contact: Release Engineering Team <<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>> </p> @@ -679,7 +678,7 @@ planned for mid July 2010.</p> <hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org" title="http://www.FreeBSDFoundation.org"></a></td><td> URL: <a href="http://www.FreeBSDFoundation.org" title="">http://www.FreeBSDFoundation.org</a></td></tr></table><p> - Contact: + Contact: Deb Goodkin @@ -714,7 +713,7 @@ <a href="http://www.FreeBSDFoundation.org/donate/" shape="rect"> http://www.FreeBSDFoundation.org/donate/</a>.</p> <hr /><br /><h1><a name="Network-Infrastructure" href="#Network-Infrastructure" id="Network-Infrastructure">Network Infrastructure</a></h1><br /><h2><a name="(Virtual)-Network-Stack-resource-cleanup" href="#(Virtual)-Network-Stack-resource-cleanup" id="(Virtual)-Network-Stack-resource-cleanup">(Virtual) Network Stack resource cleanup</a></h2><p> - Contact: + Contact: Bjoern A. Zeeb @@ -739,7 +738,7 @@ <h3>Open tasks:</h3><ol><li>Merge the remaining patches.</li><li>Work on a better teardown model and get to the point where we can free UMA zones without keeping pages for type stability and timers around.</li></ol><hr /><h2><a name="802.11n-support" href="#802.11n-support" id="802.11n-support">802.11n support</a></h2><p> - Contact: + Contact: Rui Paulo @@ -752,7 +751,7 @@ <p>This work is being sponsored by iXsystems, inc.</p> <hr /><h2><a name="Atheros-AR9285-support" href="#Atheros-AR9285-support" id="Atheros-AR9285-support">Atheros AR9285 support</a></h2><p> - Contact: + Contact: Rui Paulo @@ -765,7 +764,7 @@ URL: <a href="http://caia.swin.edu.au/urp/newtcp/" title="">http://caia.swin.edu.au/urp/newtcp/</a></td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/projects.shtml" title="http://www.FreeBSDFoundation.org/projects.shtml"></a></td><td> URL: <a href="http://www.FreeBSDFoundation.org/projects.shtml" title="">http://www.FreeBSDFoundation.org/projects.shtml</a></td></tr><tr><td><a href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" title="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/"></a></td><td> URL: <a href="http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/" title="">http://people.FreeBSD.org/~lstewart/patches/tcp_ffcaia2008/</a></td></tr></table><p> - Contact: + Contact: Lawrence Stewart @@ -782,7 +781,7 @@ be extracted as a patch people can easily test.</p> <h3>Open tasks:</h3><ol><li>Solicit external testing for and commit SIFTR.</li><li>Solicit external testing for and commit reassembly queue autotuning patch.</li></ol><hr /><h2><a name="Experimental-NFS-subsystem-(NFSv4)" href="#Experimental-NFS-subsystem-(NFSv4)" id="Experimental-NFS-subsystem-(NFSv4)">Experimental NFS subsystem (NFSv4)</a></h2><p> - Contact: + Contact: Rick Macklem @@ -801,7 +800,7 @@ URL: <a href="http://info.iet.unipi.it/~luigi/dummynet/" title="main dummynet page">http://info.iet.unipi.it/~luigi/dummynet/</a></td></tr><tr><td><a href="http://www.youtube.com/watch?v=r8vBmybeKlE" title="http://www.youtube.com/watch?v=r8vBmybeKlE">youtube video on dummynet internals</a></td><td> URL: <a href="http://www.youtube.com/watch?v=r8vBmybeKlE" title="youtube video on dummynet internals">http://www.youtube.com/watch?v=r8vBmybeKlE</a></td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/qfq/" title="http://info.iet.unipi.it/~luigi/qfq/">Description of the qfq scheduler</a></td><td> URL: <a href="http://info.iet.unipi.it/~luigi/qfq/" title="Description of the qfq scheduler">http://info.iet.unipi.it/~luigi/qfq/</a></td></tr></table><p> - Contact: + Contact: Luigi Rizzo @@ -845,7 +844,7 @@ ipfw dynamic rules, which currently require exclusive lock on a hash table containing dynamic rules.</li></ol><hr /><h2><a name="net80211-rate-control-framework" href="#net80211-rate-control-framework" id="net80211-rate-control-framework">net80211 rate control framework</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~rpaulo/ratectl.diff" title="http://people.FreeBSD.org/~rpaulo/ratectl.diff"></a></td><td> URL: <a href="http://people.FreeBSD.org/~rpaulo/ratectl.diff" title="">http://people.FreeBSD.org/~rpaulo/ratectl.diff</a></td></tr></table><p> - Contact: + Contact: Rui Paulo @@ -864,12 +863,12 @@ control algorithms for wireless networks, FreeBSD is now an ideal candidate for testing your project!</p> <hr /><h2><a name="TCP/UDP-connection-groups" href="#TCP/UDP-connection-groups" id="TCP/UDP-connection-groups">TCP/UDP connection groups</a></h2><p> - Contact: + Contact: Robert Watson <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>> <br /> - Contact: + Contact: FreeBSD network mailing list <<a href="mailto:freebsd-net@FreeBSD.org">freebsd-net@FreeBSD.org</a>> </p> @@ -916,7 +915,7 @@ features are slated for inclusion in FreeBSD 9.0 (with possible backports to 8-STABLE of some features).</p> <hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="CAM-based-ATA-implementation" href="#CAM-based-ATA-implementation" id="CAM-based-ATA-implementation">CAM-based ATA implementation</a></h2><p> - Contact: + Contact: Alexander Motin @@ -944,7 +943,7 @@ it should fit nicely into new infrastructure.</li></ol><hr /><h2><a name="Dynamic-Ticks-in-FreeBSD" href="#Dynamic-Ticks-in-FreeBSD" id="Dynamic-Ticks-in-FreeBSD">Dynamic Ticks in FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://github.com/oza/FreeBSD-8.0-dyntick" title="http://github.com/oza/FreeBSD-8.0-dyntick">Project page (github).</a></td><td> URL: <a href="http://github.com/oza/FreeBSD-8.0-dyntick" title="Project page (github).">http://github.com/oza/FreeBSD-8.0-dyntick</a></td></tr><tr><td><a href="http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html" title="http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html">My weblog article which describes benchmark of dynamic ticks.</a></td><td> URL: <a href="http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html" title="My weblog article which describes benchmark of dynamic ticks.">http://tsuyoshiozawa.blogspot.com/2010/03/started-to-implement-dynticks-in.html</a></td></tr></table><p> - Contact: + Contact: Tsuyoshi Ozawa @@ -958,13 +957,13 @@ timer interrupt may be ignored (BUG).</li><li>Make callout queue have the tick when the next timer event rise up.</li></ol><hr /><h2><a name="geom_sched" href="#geom_sched" id="geom_sched">geom_sched</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://info.iet.unipi.it/~luigi/geom_sched/" title="http://info.iet.unipi.it/~luigi/geom_sched/"></a></td><td> URL: <a href="http://info.iet.unipi.it/~luigi/geom_sched/" title="">http://info.iet.unipi.it/~luigi/geom_sched/</a></td></tr></table><p> - Contact: + Contact: Luigi Rizzo <<a href="mailto:luigi@FreeBSD.org">luigi@FreeBSD.org</a>> <br /> - Contact: + Contact: Fabio Checconi @@ -996,7 +995,7 @@ geom sched insert ad4 the scheduler.</p> <hr /><h2><a name="IPv6-without-legacy-IP-kernel" href="#IPv6-without-legacy-IP-kernel" id="IPv6-without-legacy-IP-kernel">IPv6 without legacy IP kernel</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&cd=//&c=MNx@//depot/user/bz/noinet/src/sys/?ac=83" title="http://p4web.FreeBSD.org/@md=d&cd=//&c=MNx@//depot/user/bz/noinet/src/sys/?ac=83">P4 workspace</a></td><td> URL: <a href="http://p4web.FreeBSD.org/@md=d&cd=//&c=MNx@//depot/user/bz/noinet/src/sys/?ac=83" title="P4 workspace">http://p4web.FreeBSD.org/@md=d&cd=//&c=MNx@//depot/user/bz/noinet/src/sys/?ac=83</a></td></tr></table><p> - Contact: + Contact: Bjoern A. Zeeb @@ -1020,7 +1019,7 @@ geom sched insert ad4 to help should we further head in the direction of network stack modularization.</p> <hr /><h2><a name="Multichannel-playback-in-HDA-sound-driver-(snd_hda)" href="#Multichannel-playback-in-HDA-sound-driver-(snd_hda)" id="Multichannel-playback-in-HDA-sound-driver-(snd_hda)">Multichannel playback in HDA sound driver (snd_hda)</a></h2><p> - Contact: + Contact: Alexander Motin @@ -1042,13 +1041,13 @@ geom sched insert ad4 especially relayed to multichannel LPCM playback.</li></ol><hr /><h2><a name="Rewrite-of-FreeBSD-read/write-path-using-vnode-page" href="#Rewrite-of-FreeBSD-read/write-path-using-vnode-page" id="Rewrite-of-FreeBSD-read/write-path-using-vnode-page">Rewrite of FreeBSD read/write path using vnode page</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svn.freebsd.org/viewvc/base/user/kib/vm6/" title="http://svn.freebsd.org/viewvc/base/user/kib/vm6/">Branch for the rewrite</a></td><td> URL: <a href="http://svn.freebsd.org/viewvc/base/user/kib/vm6/" title="Branch for the rewrite">http://svn.freebsd.org/viewvc/base/user/kib/vm6/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/VM6" title="http://wiki.FreeBSD.org/VM6"></a></td><td> URL: <a href="http://wiki.FreeBSD.org/VM6" title="">http://wiki.FreeBSD.org/VM6</a></td></tr></table><p> - Contact: + Contact: Konstantin Belousov <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>> <br /> - Contact: + Contact: Peter Holm @@ -1069,7 +1068,7 @@ geom sched insert ad4 or NFS).</p> <h3>Open tasks:</h3><ol><li>We need wider testing and reviews.</li></ol><hr /><h2><a name="SUJ:-Journaled-Softupdates" href="#SUJ:-Journaled-Softupdates" id="SUJ:-Journaled-Softupdates">SUJ: Journaled Softupdates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jeffr_tech.livejournal.com/" title="http://jeffr_tech.livejournal.com/"></a></td><td> URL: <a href="http://jeffr_tech.livejournal.com/" title="">http://jeffr_tech.livejournal.com/</a></td></tr></table><p> - Contact: + Contact: Jeff Roberson <<a href="mailto:jeff@FreeBSD.org">jeff@FreeBSD.org</a>> @@ -1085,19 +1084,19 @@ geom sched insert ad4 <hr /><h2><a name="ZFS" href="#ZFS" id="ZFS">ZFS</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs">Perforce tree for latest ZFSv25 work</a></td><td> URL: <a href="http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs" title="Perforce tree for latest ZFSv25 work">http://perforce.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/user/pjd/zfs</a></td></tr><tr><td><a href="http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome" title="http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome">OpenSolaris ZFS homepage</a></td><td> URL: <a href="http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome" title="OpenSolaris ZFS homepage">http://hub.opensolaris.org/bin/view/Community+Group+zfs/WebHome</a></td></tr></table><p> - Contact: + Contact: Pawel Jakub Dawidek <<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>> <br /> - Contact: + Contact: Martin Matuska <<a href="mailto:mm@FreeBSD.org">mm@FreeBSD.org</a>> <br /> - Contact: + Contact: Xin LI @@ -1135,13 +1134,13 @@ tank dedupratio 4.00x - <h3>Open tasks:</h3><ol><li>Bring ZFS v15 changes to svn -HEAD and MFC.</li><li>Further polish the code in perforce and test for functionality, etc.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><br /><h2><a name="The-FreeBSD-German-Documentation-Project" href="#The-FreeBSD-German-Documentation-Project" id="The-FreeBSD-German-Documentation-Project">The FreeBSD German Documentation Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://doc.bsdgroup.de" title="http://doc.bsdgroup.de"></a></td><td> URL: <a href="http://doc.bsdgroup.de" title="">http://doc.bsdgroup.de</a></td></tr></table><p> - Contact: + Contact: Johann Kois <<a href="mailto:jkois@FreeBSD.org">jkois@FreeBSD.org</a>> <br /> - Contact: + Contact: Benedict Reuschling @@ -1169,13 +1168,13 @@ tank dedupratio 4.00x - URL: <a href="http://www.FreeBSD.org/doc/hu/" title="Hungarian FreeBSD Documentation">http://www.FreeBSD.org/doc/hu/</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="http://wiki.FreeBSD.org/HungarianDocumentationProject">The FreeBSD Hungarian Documentation Project's Web Page</a></td><td> URL: <a href="http://wiki.FreeBSD.org/HungarianDocumentationProject" title="The FreeBSD Hungarian Documentation Project's Web Page">http://wiki.FreeBSD.org/HungarianDocumentationProject</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83" title="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83">The FreeBSD Hungarian Documentation Project's Perforce Repository</a></td><td> URL: <a href="http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83" title="The FreeBSD Hungarian Documentation Project's Perforce Repository">http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@//depot/projects/docproj_hu/?ac=83</a></td></tr></table><p> - Contact: + Contact: Gbor Kvesdn <<a href="mailto:gabor@FreeBSD.org">gabor@FreeBSD.org</a>> <br /> - Contact: + Contact: Gbor Pli @@ -1188,7 +1187,7 @@ tank dedupratio 4.00x - via the email addresses noted above.</p> <h3>Open tasks:</h3><ol><li>Translate release notes.</li><li>Translate articles.</li><li>Translate web pages.</li><li>Read translations, send feedback.</li></ol><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="FreeBSD-port-for-libunwind" href="#FreeBSD-port-for-libunwind" id="FreeBSD-port-for-libunwind">FreeBSD port for libunwind</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.nongnu.org/libunwind/" title="http://www.nongnu.org/libunwind/"></a></td><td> URL: <a href="http://www.nongnu.org/libunwind/" title="">http://www.nongnu.org/libunwind/</a></td></tr></table><p> - Contact: + Contact: Konstantin Belousov @@ -1201,13 +1200,13 @@ tank dedupratio 4.00x - remote unwinding using ptrace(2), very fast setjmp(3) implementation and more interesting features.</p> <hr /><h2><a name="LDAP-support-in-base-system" href="#LDAP-support-in-base-system" id="LDAP-support-in-base-system">LDAP support in base system</a></h2><p> - Contact: + Contact: Xin ZHAO <<a href="mailto:quakelee@geekcn.org">quakelee@geekcn.org</a>> <br /> - Contact: + Contact: Xin LI @@ -1230,7 +1229,7 @@ tank dedupratio 4.00x - <h3>Open tasks:</h3><ol><li>Further code review.</li><li>Make the changes less intrusive.</li><li>Fix issues found in production deployment.</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD/arm-port-for-TI-DaVinci" href="#FreeBSD/arm-port-for-TI-DaVinci" id="FreeBSD/arm-port-for-TI-DaVinci">FreeBSD/arm port for TI DaVinci</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&familyId=1300&tabId=1854" title="http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&familyId=1300&tabId=1854">DaVinci on TI's site</a></td><td> URL: <a href="http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&familyId=1300&tabId=1854" title="DaVinci on TI's site">http://focus.ti.com/dsp/docs/dspplatformscontenttp.tsp?sectionId=2&familyId=1300&tabId=1854</a></td></tr><tr><td><a href="http://p4web.FreeBSD.org/@md=d&cd=//depot/user/jceel/davinci/" title="http://p4web.FreeBSD.org/@md=d&cd=//depot/user/jceel/davinci/">Project branch in P4</a></td><td> URL: <a href="http://p4web.FreeBSD.org/@md=d&cd=//depot/user/jceel/davinci/" title="Project branch in P4">http://p4web.FreeBSD.org/@md=d&cd=//depot/user/jceel/davinci/</a></td></tr></table><p> - Contact: + Contact: Jakub Klama @@ -1262,7 +1261,7 @@ tank dedupratio 4.00x - </ul> <h3>Open tasks:</h3><ol><li>Remaining built-in peripherals drivers (USB, ATA, NAND flash, I2C, DMA engine, sound, video input/output).</li><li>Framework for communicating with DSP core.</li></ol><hr /><h2><a name="FreeBSD/ia64" href="#FreeBSD/ia64" id="FreeBSD/ia64">FreeBSD/ia64</a></h2><p> - Contact: + Contact: Mark Linimon @@ -1295,7 +1294,7 @@ tank dedupratio 4.00x - loaded at a runtime-determined physical address as well as add support for NUMA.</li></ol><hr /><h2><a name="FreeBSD/mips-on-D-Link-DIR-320" href="#FreeBSD/mips-on-D-Link-DIR-320" id="FreeBSD/mips-on-D-Link-DIR-320">FreeBSD/mips on D-Link DIR-320</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD" title="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD"></a></td><td> URL: <a href="http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD" title="">http://wiki.ddteam.net/wiki.cgi?page=DIR-320+FreeBSD</a></td></tr></table><p> - Contact: + Contact: Alexandr Rybalko @@ -1307,7 +1306,7 @@ tank dedupratio 4.00x - <a href="http://ipsec-tools.sourceforge.net/" shape="rect">racoon</a> based router-ipsec image is available.</p> <h3>Open tasks:</h3><ol><li>bfeswitch configuration utility.</li><li>Add router profile.</li><li>Add wifi-router profile.</li><li>Add openvpn-router profile.</li></ol><hr /><h2><a name="FreeBSD/powerpc" href="#FreeBSD/powerpc" id="FreeBSD/powerpc">FreeBSD/powerpc</a></h2><p> - Contact: + Contact: Nathan Whitehorn @@ -1326,7 +1325,7 @@ tank dedupratio 4.00x - <p>Mark Linimon is working on getting us more XServes.</p> <h3>Open tasks:</h3><ol><li>Start the hard work of fixing individual packages.</li></ol><hr /><h2><a name="FreeBSD/powerpc64-port" href="#FreeBSD/powerpc64-port" id="FreeBSD/powerpc64-port">FreeBSD/powerpc64 port</a></h2><p> - Contact: + Contact: Nathan Whitehorn @@ -1340,7 +1339,7 @@ tank dedupratio 4.00x - support planned for IBM Power Systems servers and the Sony PlayStation 3.</p> <hr /><h2><a name="FreeBSD/sparc64" href="#FreeBSD/sparc64" id="FreeBSD/sparc64">FreeBSD/sparc64</a></h2><p> - Contact: + Contact: Marius Strobl @@ -1392,7 +1391,7 @@ tank dedupratio 4.00x - </ul> <hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="Portmaster" href="#Portmaster" id="Portmaster">Portmaster</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://dougbarton.us/portmaster-proposal.html" title="http://dougbarton.us/portmaster-proposal.html"></a></td><td> URL: <a href="http://dougbarton.us/portmaster-proposal.html" title="">http://dougbarton.us/portmaster-proposal.html</a></td></tr></table><p> - Contact: + Contact: Doug Barton @@ -1439,13 +1438,13 @@ tank dedupratio 4.00x - URL: <a href="http://portsmon.FreeBSD.org/index.html" title="">http://portsmon.FreeBSD.org/index.html</a></td></tr><tr><td><a href="http://www.FreeBSD.org/portmgr/index.html" title="http://www.FreeBSD.org/portmgr/index.html"></a></td><td> URL: <a href="http://www.FreeBSD.org/portmgr/index.html" title="">http://www.FreeBSD.org/portmgr/index.html</a></td></tr><tr><td><a href="http://tinderbox.marcuscom.com/" title="http://tinderbox.marcuscom.com/"></a></td><td> URL: <a href="http://tinderbox.marcuscom.com/" title="">http://tinderbox.marcuscom.com/</a></td></tr></table><p> - Contact: + Contact: Thomas Abthorpe <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>> <br /> - Contact: + Contact: Port Management Team @@ -1482,13 +1481,13 @@ tank dedupratio 4.00x - Tier-2 architectures</url>.</li><li>Most ports PRs are assigned, we now need to focus on testing, committing and closing.</li><li>Major commits expected soon include the latest Xorg, KDE4, and Gnome updates.</li></ol><hr /><h2><a name="QAT" href="#QAT" id="QAT">QAT</a></h2><p> - Contact: + Contact: Ion-Mihai Tetcu <<a href="mailto:itetcu@FreeBSD.org">itetcu@FreeBSD.org</a>> <br /> - Contact: + Contact: Josh Paetzel @@ -1503,7 +1502,7 @@ tank dedupratio 4.00x - <h3>Open tasks:</h3><ol><li>Bring VMware server online and provision VMs.</li><li>Refactor QAT code to handle concurrent builds.</li><li>Migrate the existing QAT to the new setup.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="BSDCan-2010-—-The-BSD-Conference" href="#BSDCan-2010-—-The-BSD-Conference" id="BSDCan-2010-—-The-BSD-Conference">BSDCan 2010 — The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.BSDCan.org/2010/" title="http://www.BSDCan.org/2010/"></a></td><td> URL: <a href="http://www.BSDCan.org/2010/" title="">http://www.BSDCan.org/2010/</a></td></tr><tr><td><a href="http://www.BSDCan.org/2010/schedule/" title="http://www.BSDCan.org/2010/schedule/">Tutorials and Talks Schedule</a></td><td> URL: <a href="http://www.BSDCan.org/2010/schedule/" title="Tutorials and Talks Schedule">http://www.BSDCan.org/2010/schedule/</a></td></tr></table><p> - Contact: + Contact: BSDCan Information <<a href="mailto:info@BSDCan.org">info@BSDCan.org</a>> </p> @@ -1524,7 +1523,7 @@ tank dedupratio 4.00x - <p>Please check the conference web site for more information.</p> <hr /><h2><a name="meetBSD-2010----The-BSD-Conference" href="#meetBSD-2010----The-BSD-Conference" id="meetBSD-2010----The-BSD-Conference">meetBSD 2010 -- The BSD Conference</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.meetbsd.org" title="http://www.meetbsd.org"></a></td><td> URL: <a href="http://www.meetbsd.org" title="">http://www.meetbsd.org</a></td></tr></table><p> - Contact: + Contact: meetBSD Information diff --git a/website/content/en/status/report-2010-04-2010-06.html b/website/content/en/status/report-2010-04-2010-06.html index b33bdda59a..6e0b4ddf56 100644 --- a/website/content/en/status/report-2010-04-2010-06.html +++ b/website/content/en/status/report-2010-04-2010-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -292,7 +292,7 @@ utilities) meant to be included in the base system when it is done. It comes with built-in mass patch creation and application commands. It is funded by Google Summer of Code 2010.</p> - <h3>Open tasks:</h3><ol><li>Finish the project.</li><li>Get some testing for it.</li><li>Convince the Port Management Team it is actually a Good + <h3>Open tasks:</h3><ol><li>Finish the project.</li><li>Get some testing for it.</li><li>Convince the Ports Management Team it is actually a Good Thing to have even as an experimental feature.</li><li>Agree upon the policy on which package patches will be created (i.e. from which point in time to which point in time), assuming the "stable" package tree idea has still not gotten @@ -1493,7 +1493,7 @@ </ul> <p>alepulver's Licensing Framework Summer of Code project has made - it into the tree and the Port Management Team is currently + it into the tree and the Ports Management Team is currently assessing the fallout and it will come up with guidelines and documentation in due time.</p> <h3>Open tasks:</h3><ol><li>Looking for help fixing <a href="http://wiki.FreeBSD.org/PortsBrokenOnCurrent" shape="rect">ports diff --git a/website/content/en/status/report-2010-07-2010-09.html b/website/content/en/status/report-2010-07-2010-09.html index 1ce47a640e..c8b206a8e4 100644 --- a/website/content/en/status/report-2010-07-2010-09.html +++ b/website/content/en/status/report-2010-07-2010-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2010-10-2010-12.html b/website/content/en/status/report-2010-10-2010-12.html index d05f131b43..ce80ac375d 100644 --- a/website/content/en/status/report-2010-10-2010-12.html +++ b/website/content/en/status/report-2010-10-2010-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2011-01-2011-03.html b/website/content/en/status/report-2011-01-2011-03.html index d9b86baa4a..91834d3c09 100644 --- a/website/content/en/status/report-2011-01-2011-03.html +++ b/website/content/en/status/report-2011-01-2011-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2011-04-2011-06.html b/website/content/en/status/report-2011-04-2011-06.html index 1228445902..bef80258af 100644 --- a/website/content/en/status/report-2011-04-2011-06.html +++ b/website/content/en/status/report-2011-04-2011-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2011-07-2011-09.html b/website/content/en/status/report-2011-07-2011-09.html index 6f6841e34e..2569d98c47 100644 --- a/website/content/en/status/report-2011-07-2011-09.html +++ b/website/content/en/status/report-2011-07-2011-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2011-10-2011-12.html b/website/content/en/status/report-2011-10-2011-12.html index 1f0a979f5b..e0907eb6b3 100644 --- a/website/content/en/status/report-2011-10-2011-12.html +++ b/website/content/en/status/report-2011-10-2011-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2012-01-2012-03.html b/website/content/en/status/report-2012-01-2012-03.html index 1036ab47c1..3447fd434a 100644 --- a/website/content/en/status/report-2012-01-2012-03.html +++ b/website/content/en/status/report-2012-01-2012-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2012-04-2012-06.html b/website/content/en/status/report-2012-04-2012-06.html index a71dd542d2..a23ad87309 100644 --- a/website/content/en/status/report-2012-04-2012-06.html +++ b/website/content/en/status/report-2012-04-2012-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -277,7 +277,7 @@ relatively high number of new members. Note that this is the second of the four reports planned for 2012.</p><p>Thanks to all the reporters for the excellent work! This report contains 17 entries and we hope you enjoy reading it.</p><p>Please note that the deadline for submissions covering the period - between July and December 2012 is February 17th, 2013.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></li><li><a href="#Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Documentation-Project">FreeBSD Documentation Project</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Port-Management-Team">The FreeBSD Port Management Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD/at91-Improvements">FreeBSD/at91 Improvements</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Multipath-TCP-(MPTCP)-for-FreeBSD">Multipath TCP (MPTCP) for FreeBSD</a></li><li><a href="#SMP-Friendly-pf(4)">SMP-Friendly pf(4)</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm-on-ARM-Fast-Models-Simulator-for-Cortex-A15-MPCore-Processor">FreeBSD/arm on ARM Fast Models Simulator for Cortex-A15 MPCore + between July and December 2012 is February 17th, 2013.</p><hr /><h3><a href="#Projects">Projects</a></h3><ul></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></li><li><a href="#Replacing-the-Regular-Expression-Code">Replacing the Regular Expression Code</a></li></ul><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Documentation-Project">FreeBSD Documentation Project</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Port-Management-Team">The FreeBSD Ports Management Team</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#FreeBSD/at91-Improvements">FreeBSD/at91 Improvements</a></li></ul><h3><a href="#Network-Infrastructure">Network Infrastructure</a></h3><ul><li><a href="#Multipath-TCP-(MPTCP)-for-FreeBSD">Multipath TCP (MPTCP) for FreeBSD</a></li><li><a href="#SMP-Friendly-pf(4)">SMP-Friendly pf(4)</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#The-FreeBSD-Japanese-Documentation-Project">The FreeBSD Japanese Documentation Project</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm-on-ARM-Fast-Models-Simulator-for-Cortex-A15-MPCore-Processor">FreeBSD/arm on ARM Fast Models Simulator for Cortex-A15 MPCore Processor</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#BSD-licensed-Sort-Utility-(GNU-sort(1)-Replacement)">BSD-licensed Sort Utility (GNU sort(1) Replacement)</a></li><li><a href="#FreeBSD-Haskell-Ports">FreeBSD Haskell Ports</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Portbuilder">Portbuilder</a></li><li><a href="#Redports">Redports</a></li><li><a href="#Xorg-on-FreeBSD">Xorg on FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#BSD-Day-2012">BSD-Day 2012</a></li></ul><ul></ul><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="FreeBSD-Services-Control-(fsc)" href="#FreeBSD-Services-Control-(fsc)" id="FreeBSD-Services-Control-(fsc)">FreeBSD Services Control (fsc)</a></h2><p> Contact: Tom @@ -378,7 +378,7 @@ <p>The Core Team would also especially like to thank Dag-Erling Smrgrav for running the election.</p> - <hr /><h2><a name="The-FreeBSD-Port-Management-Team" href="#The-FreeBSD-Port-Management-Team" id="The-FreeBSD-Port-Management-Team">The FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> + <hr /><h2><a name="The-FreeBSD-Port-Management-Team" href="#The-FreeBSD-Port-Management-Team" id="The-FreeBSD-Port-Management-Team">The FreeBSD Ports Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td> URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td> URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td> diff --git a/website/content/en/status/report-2012-07-2012-09.html b/website/content/en/status/report-2012-07-2012-09.html index 9e763df51d..874dd99f89 100644 --- a/website/content/en/status/report-2012-07-2012-09.html +++ b/website/content/en/status/report-2012-07-2012-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -455,7 +455,7 @@ <p>In the third quarter, the Core Team granted access for 2 new committers and took 2 commit bits into safekeeping.</p> - <p>The Core Team worked with the Port Management Team and Cluster + <p>The Core Team worked with the Ports Management Team and Cluster Administrators to set a date to stop providing CVS exports for the ports repository, which is February 28, 2013. In the meantime, the CVS export for 9.1-RELEASE was restored.</p> diff --git a/website/content/en/status/report-2012-10-2012-12.html b/website/content/en/status/report-2012-10-2012-12.html index 759d4ddcc9..5faa616db5 100644 --- a/website/content/en/status/report-2012-10-2012-12.html +++ b/website/content/en/status/report-2012-10-2012-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2013-01-2013-03.html b/website/content/en/status/report-2013-01-2013-03.html index c398eb525f..535fd7b170 100644 --- a/website/content/en/status/report-2013-01-2013-03.html +++ b/website/content/en/status/report-2013-01-2013-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2013-04-2013-06.html b/website/content/en/status/report-2013-04-2013-06.html index d0792bc419..063e9b76c1 100644 --- a/website/content/en/status/report-2013-04-2013-06.html +++ b/website/content/en/status/report-2013-04-2013-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2013-05-devsummit.html b/website/content/en/status/report-2013-05-devsummit.html index d46602d409..5a0794edca 100644 --- a/website/content/en/status/report-2013-05-devsummit.html +++ b/website/content/en/status/report-2013-05-devsummit.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2013-07-2013-09.html b/website/content/en/status/report-2013-07-2013-09.html index b939432207..504d0d0b59 100644 --- a/website/content/en/status/report-2013-07-2013-09.html +++ b/website/content/en/status/report-2013-07-2013-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -289,13 +289,13 @@ commodity hardware, while desktop users will see improvements in X support for new GPUs and for possible X replacements.</p><p>Thanks to all the reporters for the excellent work! This report contains 30 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering between October and - December 2013 is January 14th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Static-Code-Analysis">Static Code Analysis</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#AES-NI-Improvements-for-GELI">AES-NI Improvements for GELI</a></li><li><a href="#Atomic-"close-on-exec"">Atomic "close-on-exec"</a></li><li><a href="#Continuation-of-the-Newcons-Project">Continuation of the Newcons Project</a></li><li><a href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#Reworking-random(4)">Reworking random(4)</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#VirtIO-Network-Multiqueue">VirtIO Network Multiqueue</a></li><li><a href="#VMware-VMXNET3-Driver">VMware VMXNET3 Driver</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Cubieboard2">FreeBSD on Cubieboard2</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/pseries">FreeBSD/pseries</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li><li><a href="#Superpages-for-ARMv7">Superpages for ARMv7</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Capsicum">Capsicum</a></li><li><a href="#LLDB-Debugger-Port">LLDB Debugger Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></li><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#GNUstep-on-FreeBSD">GNUstep on FreeBSD</a></li><li><a href="#X.Org-on-FreeBSD">X.Org on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-Documentation-Project-Primer-Edit">FreeBSD Documentation Project Primer Edit</a></li><li><a href="#The-entities-Documentation-Branch">The entities Documentation Branch</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Download-Manager-Service-for-the-Ports-Collection">Download Manager Service for the Ports Collection</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p> + December 2013 is January 14th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Static-Code-Analysis">Static Code Analysis</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#AES-NI-Improvements-for-GELI">AES-NI Improvements for GELI</a></li><li><a href="#Atomic-"close-on-exec"">Atomic "close-on-exec"</a></li><li><a href="#Continuation-of-the-Newcons-Project">Continuation of the Newcons Project</a></li><li><a href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#Reworking-random(4)">Reworking random(4)</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#VirtIO-Network-Multiqueue">VirtIO Network Multiqueue</a></li><li><a href="#VMware-VMXNET3-Driver">VMware VMXNET3 Driver</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-on-Cubieboard2">FreeBSD on Cubieboard2</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/pseries">FreeBSD/pseries</a></li><li><a href="#FreeBSD/sparc64">FreeBSD/sparc64</a></li><li><a href="#Superpages-for-ARMv7">Superpages for ARMv7</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Capsicum">Capsicum</a></li><li><a href="#LLDB-Debugger-Port">LLDB Debugger Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></li><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#GNUstep-on-FreeBSD">GNUstep on FreeBSD</a></li><li><a href="#X.Org-on-FreeBSD">X.Org on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-Documentation-Project-Primer-Edit">FreeBSD Documentation Project Primer Edit</a></li><li><a href="#The-entities-Documentation-Branch">The entities Documentation Branch</a></li></ul><h3><a href="#Google-Summer-of-Code">Google Summer of Code</a></h3><ul><li><a href="#Download-Manager-Service-for-the-Ports-Collection">Download Manager Service for the Ports Collection</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p> Contact: FreeBSD Core Team <<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>> </p> <p>In the third quarter of 2013, the Core Team focused on officially launching <tt>pkg.freebsd.org</tt>, the Project's official <tt>pkg(8)</tt> repository, in cooperation with the - Port Management Team, the Security Team, and the Cluster + Ports Management Team, the Security Team, and the Cluster Administration Team. At the same time, there are plans to gradually deprecate the use of the old <tt>pkg_add(1)</tt>, allowing <tt>pkg(8)</tt> to be the default binary package @@ -316,7 +316,7 @@ of the src commits being idle more than 12 months have been taken into safekeeping as result of a major cleanup to the repository access file in July, performed by Gavin Atkinson.</p> - <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> + <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="http://www.freebsd.org/doc/en/articles/contributing-ports/"></a></td><td> URL: <a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td> URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td> @@ -325,7 +325,7 @@ URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td> URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout" title="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout"></a></td><td> URL: <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout" title="">http://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout</a></td></tr></table><p> - Contact: FreeBSD Port Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> + Contact: FreeBSD Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> </p> <p>The ports tree contains approximately 24,400 ports, while the PR count exceeds 1,900. In the third quarter, we added four new diff --git a/website/content/en/status/report-2013-09-devsummit.html b/website/content/en/status/report-2013-09-devsummit.html index e1976c430c..5f65e42de3 100644 --- a/website/content/en/status/report-2013-09-devsummit.html +++ b/website/content/en/status/report-2013-09-devsummit.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2013-10-2013-12.html b/website/content/en/status/report-2013-10-2013-12.html index ab8b67c09f..9ddfed6d66 100644 --- a/website/content/en/status/report-2013-10-2013-12.html +++ b/website/content/en/status/report-2013-10-2013-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -294,7 +294,7 @@ testing with Jenkins and Kyua. It is an exciting time for users and developers of FreeBSD!</p><p>Thanks to all the reporters for the excellent work! This report contains 37 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering between January and - March 2014 is April 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#CBSD">CBSD</a></li><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></li><li><a href="#Intel-802.11n-NIC-(iwn(4))-Work">Intel 802.11n NIC (iwn(4)) Work</a></li><li><a href="#Intel-GPU-Driver-Update">Intel GPU Driver Update</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#UMA/ZFS-and-RPC/NFS-Performance-Improvements">UMA/ZFS and RPC/NFS Performance Improvements</a></li><li><a href="#Updated-vt(9)-System-Console">Updated vt(9) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#FreeBSD-on-Cubieboard{1,2}">FreeBSD on Cubieboard{1,2}</a></li><li><a href="#FreeBSD-on-Freescale-i.MX6-processors">FreeBSD on Freescale i.MX6 processors</a></li><li><a href="#FreeBSD-on-Freescale-Vybrid-VF6xx">FreeBSD on Freescale Vybrid VF6xx</a></li><li><a href="#FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/Xen">FreeBSD/Xen</a></li><li><a href="#Intel-IOMMU-(VT-d,-DMAR)-Support">Intel IOMMU (VT-d, DMAR) Support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#auditdistd(8)">auditdistd(8)</a></li><li><a href="#Base-GCC-Updates">Base GCC Updates</a></li><li><a href="#BSDInstall-ZFSBoot">BSDInstall ZFSBoot</a></li><li><a href="#Capsicum-and-Casper">Capsicum and Casper</a></li><li><a href="#Centralized-Panic-Reporting">Centralized Panic Reporting</a></li><li><a href="#FreeBSD-Test-Suite">FreeBSD Test Suite</a></li><li><a href="#The-LLDB-Debugger">The LLDB Debugger</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#X.Org-on-FreeBSD">X.Org on FreeBSD</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p> + March 2014 is April 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#CBSD">CBSD</a></li><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></li><li><a href="#Intel-802.11n-NIC-(iwn(4))-Work">Intel 802.11n NIC (iwn(4)) Work</a></li><li><a href="#Intel-GPU-Driver-Update">Intel GPU Driver Update</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#UMA/ZFS-and-RPC/NFS-Performance-Improvements">UMA/ZFS and RPC/NFS Performance Improvements</a></li><li><a href="#Updated-vt(9)-System-Console">Updated vt(9) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#FreeBSD-on-Cubieboard{1,2}">FreeBSD on Cubieboard{1,2}</a></li><li><a href="#FreeBSD-on-Freescale-i.MX6-processors">FreeBSD on Freescale i.MX6 processors</a></li><li><a href="#FreeBSD-on-Freescale-Vybrid-VF6xx">FreeBSD on Freescale Vybrid VF6xx</a></li><li><a href="#FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/Xen">FreeBSD/Xen</a></li><li><a href="#Intel-IOMMU-(VT-d,-DMAR)-Support">Intel IOMMU (VT-d, DMAR) Support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#auditdistd(8)">auditdistd(8)</a></li><li><a href="#Base-GCC-Updates">Base GCC Updates</a></li><li><a href="#BSDInstall-ZFSBoot">BSDInstall ZFSBoot</a></li><li><a href="#Capsicum-and-Casper">Capsicum and Casper</a></li><li><a href="#Centralized-Panic-Reporting">Centralized Panic Reporting</a></li><li><a href="#FreeBSD-Test-Suite">FreeBSD Test Suite</a></li><li><a href="#The-LLDB-Debugger">The LLDB Debugger</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#X.Org-on-FreeBSD">X.Org on FreeBSD</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p> Contact: FreeBSD Cluster Administration Team <<a href="mailto:admins@">admins@</a>> </p> <p>The FreeBSD Cluster Administration Team consists of the people @@ -358,7 +358,7 @@ In addition to this, there were three commit bits offered for new developers, two committers were upgraded, one commit bit was taken for safekeeping, and one src bit was reactivated.</p> - <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> + <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="http://www.freebsd.org/doc/en/articles/contributing-ports/"></a></td><td> URL: <a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td> URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td> @@ -367,7 +367,7 @@ URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td> URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383"></a></td><td> URL: <a href="http://plus.google.com/communities/108335846196454338383" title="">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p> - Contact: FreeBSD Port Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> + Contact: FreeBSD Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> </p> <p>The FreeBSD Ports collection is a package management system for the FreeBSD operating system, providing an easy and consistent way of @@ -375,7 +375,7 @@ contains approximately 24,500 ports, while the PR count exceeds 1,900.</p> - <p>The FreeBSD Port Management Team ensures that the FreeBSD ports + <p>The FreeBSD Ports Management Team ensures that the FreeBSD ports developer community provides a Ports Collection that is functional, stable, up-to-date, and full-featured. Its secondary responsibility is to coordinate among the committers and @@ -395,9 +395,9 @@ this same time, further enhancements were put into <tt>pkg(8)</tt>, including secure package signing.</p> - <p>Commencing November 1, the Port Management Team undertook a + <p>Commencing November 1, the Ports Management Team undertook a <q>portmgr-lurkers</q> pilot project in which ports committers - could volunteer to assist the Port Management Team for a + could volunteer to assist the Ports Management Team for a four-month duration. The first two candiates are Mathieu Arnold (<tt>mat</tt>) and Antoine Brodin (<tt>antoine</tt>).</p> @@ -422,7 +422,7 @@ <li>Created a <tt>graphics-team</tt> alias, requested by Niclas Zeising.</li> - <li>Worked with the FreeBSD Port Management Team to set up + <li>Worked with the FreeBSD Ports Management Team to set up <tt>portmgr-lurkers</tt> so port managers can move addresses between those two aliases at their discretion.</li> diff --git a/website/content/en/status/report-2014-01-2014-03.html b/website/content/en/status/report-2014-01-2014-03.html index 730c5a3833..1d872024a0 100644 --- a/website/content/en/status/report-2014-01-2014-03.html +++ b/website/content/en/status/report-2014-01-2014-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -292,7 +292,7 @@ development projects. And these are only some of the things that happened! Read on for even more.</p><p>Thanks to all the reporters for the excellent work! This report contains 41 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering between April and - June 2014 is July 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Documentation-Engineering-Team">FreeBSD Documentation Engineering Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ASLR-and-PIE">ASLR and PIE</a></li><li><a href="#Intel-GPU-Driver-Update">Intel GPU Driver Update</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#PCI-SR-IOV-Infrastructure">PCI SR-IOV Infrastructure</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#Updated-vt(4)-System-Console">Updated vt(4) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#bhyve">bhyve</a></li><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#FreeBSD-on-Chromebook">FreeBSD on Chromebook</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li><li><a href="#FreeBSD/armv6hf">FreeBSD/armv6hf</a></li><li><a href="#SMP-on-Multi-Core-ARM-Systems">SMP on Multi-Core ARM Systems</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#auditdistd(8)">auditdistd(8)</a></li><li><a href="#External-Toolchain-Improvements">External Toolchain Improvements</a></li><li><a href="#Forward-Port-FreeBSD-GCC">Forward Port FreeBSD GCC</a></li><li><a href="#FreeBSD-Test-Suite">FreeBSD Test Suite</a></li><li><a href="#LLDB-Debugger-Port">LLDB Debugger Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium">Chromium</a></li><li><a href="#FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></li><li><a href="#GCC-in-the-Ports-Collection">GCC in the Ports Collection</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#libvirt/bhyve-Support">libvirt/bhyve Support</a></li><li><a href="#OpenAFS-on-FreeBSD">OpenAFS on FreeBSD</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#Using-CentOS-6.5-as-Linux-Base">Using CentOS 6.5 as Linux Base</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#ZFS-Chapter-of-the-Handbook">ZFS Chapter of the Handbook</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreeBSD-Participating-in-Summer-of-Code-2014">FreeBSD Participating in Summer of Code 2014</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p> + June 2014 is July 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Documentation-Engineering-Team">FreeBSD Documentation Engineering Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#ASLR-and-PIE">ASLR and PIE</a></li><li><a href="#Intel-GPU-Driver-Update">Intel GPU Driver Update</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#PCI-SR-IOV-Infrastructure">PCI SR-IOV Infrastructure</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#Updated-vt(4)-System-Console">Updated vt(4) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#bhyve">bhyve</a></li><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#FreeBSD-on-Chromebook">FreeBSD on Chromebook</a></li><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li><li><a href="#FreeBSD/armv6hf">FreeBSD/armv6hf</a></li><li><a href="#SMP-on-Multi-Core-ARM-Systems">SMP on Multi-Core ARM Systems</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#auditdistd(8)">auditdistd(8)</a></li><li><a href="#External-Toolchain-Improvements">External Toolchain Improvements</a></li><li><a href="#Forward-Port-FreeBSD-GCC">Forward Port FreeBSD GCC</a></li><li><a href="#FreeBSD-Test-Suite">FreeBSD Test Suite</a></li><li><a href="#LLDB-Debugger-Port">LLDB Debugger Port</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Chromium">Chromium</a></li><li><a href="#FreeBSD-Ada-Ports">FreeBSD Ada Ports</a></li><li><a href="#GCC-in-the-Ports-Collection">GCC in the Ports Collection</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#libvirt/bhyve-Support">libvirt/bhyve Support</a></li><li><a href="#OpenAFS-on-FreeBSD">OpenAFS on FreeBSD</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li><li><a href="#Using-CentOS-6.5-as-Linux-Base">Using CentOS 6.5 as Linux Base</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#ZFS-Chapter-of-the-Handbook">ZFS Chapter of the Handbook</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreeBSD-Participating-in-Summer-of-Code-2014">FreeBSD Participating in Summer of Code 2014</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p> Contact: FreeBSD Cluster Administration Team <<a href="mailto:admins@">admins@</a>> </p> <p>The FreeBSD Cluster Administration Team consists of the people @@ -355,7 +355,7 @@ ported applications. In coordination with the Port Management Team, <tt>pkg_tools</tt> was eventually deprecated and tagged with an End-of-Life date, in order to clear the way for - <tt>pkg(8)</tt>. The Port Management Team also requested a + <tt>pkg(8)</tt>. The Ports Management Team also requested a way to make it possible to track userland ABI and KBI changes reliably for the Ports Collection. Ideally this can be achieved by increasing the value of <tt>__FreeBSD_version</tt> @@ -377,7 +377,7 @@ announce a new member — Warren Block. In early March, the FreeBSD Documentation Engineering Team members assumed responsibility for the FreeBSD Webmaster Team.</p> - <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> + <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td> URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td> URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td> @@ -396,9 +396,9 @@ Culot <<a href="mailto:culot@FreeBSD.org">culot@FreeBSD.org</a>> <br /> - Contact: FreeBSD Port Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> + Contact: FreeBSD Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> </p> - <p>The role of the FreeBSD Port Management Team is to ensure that the + <p>The role of the FreeBSD Ports Management Team is to ensure that the FreeBSD Ports Developer community provides a ports collection that is functional, stable, up-to-date and full-featured. It is also to coordinate among the committers and developers who work on diff --git a/website/content/en/status/report-2014-04-2014-06.html b/website/content/en/status/report-2014-04-2014-06.html index 1a099e3fc5..23adc132a6 100644 --- a/website/content/en/status/report-2014-04-2014-06.html +++ b/website/content/en/status/report-2014-04-2014-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -281,7 +281,7 @@ FreeBSD9.3-RELEASE cycle, and many exciting new features have been added to FreeBSD.</p><p>Thanks to all the reporters for the excellent work! This report contains 24 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering the period from July to - September 2014 is October 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Chelsio-iSCSI-Offload-Support">Chelsio iSCSI Offload Support</a></li><li><a href="#CUSE4BSD">CUSE4BSD</a></li><li><a href="#FreeBSD-and-Summer-of-Code-2014">FreeBSD and Summer of Code 2014</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#pkg(8)">pkg(8)</a></li><li><a href="#QEMU-bsd-user-Enabled-Ports-Building">QEMU bsd-user-Enabled Ports Building</a></li><li><a href="#RPC/NFS-and-CTL/iSCSI-Performance-Optimizations">RPC/NFS and CTL/iSCSI Performance Optimizations</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#PostgreSQL-Performance-Improvements">PostgreSQL Performance Improvements</a></li><li><a href="#Running-FreeBSD-as-an-Application-on-Top-of-the-Fiasco.OC-Microkernel">Running FreeBSD as an Application on Top of the Fiasco.OC + September 2014 is October 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#Chelsio-iSCSI-Offload-Support">Chelsio iSCSI Offload Support</a></li><li><a href="#CUSE4BSD">CUSE4BSD</a></li><li><a href="#FreeBSD-and-Summer-of-Code-2014">FreeBSD and Summer of Code 2014</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#pkg(8)">pkg(8)</a></li><li><a href="#QEMU-bsd-user-Enabled-Ports-Building">QEMU bsd-user-Enabled Ports Building</a></li><li><a href="#RPC/NFS-and-CTL/iSCSI-Performance-Optimizations">RPC/NFS and CTL/iSCSI Performance Optimizations</a></li><li><a href="#ZFSguru">ZFSguru</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#PostgreSQL-Performance-Improvements">PostgreSQL Performance Improvements</a></li><li><a href="#Running-FreeBSD-as-an-Application-on-Top-of-the-Fiasco.OC-Microkernel">Running FreeBSD as an Application on Top of the Fiasco.OC Microkernel</a></li><li><a href="#SDIO-Driver">SDIO Driver</a></li><li><a href="#TMPFS-Stability">TMPFS Stability</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#Updated-vt(4)-System-Console">Updated vt(4) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD/arm64">FreeBSD/arm64</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#The-Graphics-Stack-on-FreeBSD">The Graphics Stack on FreeBSD</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Quarterly-Status-Reports">Quarterly Status Reports</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Core-Team" href="#FreeBSD-Core-Team" id="FreeBSD-Core-Team">FreeBSD Core Team</a></h2><p> Contact: FreeBSD Core Team <<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>> </p> @@ -334,7 +334,7 @@ <p>Three new src commit bits were issued during this quarter, and one was taken into safekeeping.</p> - <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Port Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> + <hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td> URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/"></a></td><td> URL: <a href="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td> URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td> @@ -348,7 +348,7 @@ Culot <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>> <br /> - Contact: FreeBSD Port Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> + Contact: FreeBSD Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> </p> <p>The ports tree slowly approaches the 25,000 ports threshold, while the PR count is slightly below 1800.</p> diff --git a/website/content/en/status/report-2014-07-2014-09.html b/website/content/en/status/report-2014-07-2014-09.html index 5705677da3..a9d4b29bd6 100644 --- a/website/content/en/status/report-2014-07-2014-09.html +++ b/website/content/en/status/report-2014-07-2014-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2014-10-2014-12.html b/website/content/en/status/report-2014-10-2014-12.html index 021b2e7cab..802ad8301b 100644 --- a/website/content/en/status/report-2014-10-2014-12.html +++ b/website/content/en/status/report-2014-10-2014-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -322,7 +322,7 @@ Culot <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>> <br /> - Contact: Port Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> + Contact: Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> </p> <p>As of the end of Q4 the ports tree holds more than 24,000 ports, and the PR count is just over 1,400. As during the diff --git a/website/content/en/status/report-2015-01-2015-03.html b/website/content/en/status/report-2015-01-2015-03.html index 3db2012018..59927fa399 100644 --- a/website/content/en/status/report-2015-01-2015-03.html +++ b/website/content/en/status/report-2015-01-2015-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -346,7 +346,7 @@ Culot <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>> <br /> - Contact: Port Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> + Contact: Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>> </p> <p>As of the end of Q1 the ports tree holds almost 25,000 ports, and the PR count is just over 1,500. The tree saw diff --git a/website/content/en/status/report-2015-04-2015-06.html b/website/content/en/status/report-2015-04-2015-06.html index 9f5fc98249..e7b59d8b3d 100644 --- a/website/content/en/status/report-2015-04-2015-06.html +++ b/website/content/en/status/report-2015-04-2015-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2015-07-2015-09.html b/website/content/en/status/report-2015-07-2015-09.html index 74ca5c551f..a04596c7cb 100644 --- a/website/content/en/status/report-2015-07-2015-09.html +++ b/website/content/en/status/report-2015-07-2015-09.html @@ -6,7 +6,6 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="../../layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" src="../../layout/js/google.js"></script> </head> <body> <div id="containerwrap"> @@ -463,7 +462,7 @@ Allan Jude, Marcelo Araujo, and Andriy Voskoboinyk.</p> <hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="automtud:-Better-Jumbo-Frame-Support" href="#automtud:-Better-Jumbo-Frame-Support" id="automtud:-Better-Jumbo-Frame-Support">automtud: Better Jumbo Frame Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/jmgurney/automtud" title="https://github.com/jmgurney/automtud">jmgurney/automtud on github</a></td><td> URL: <a href="https://github.com/jmgurney/automtud" title="jmgurney/automtud on github">https://github.com/jmgurney/automtud</a></td></tr></table><p> - Contact: + Contact: John-Mark Gurney <<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>> @@ -504,27 +503,27 @@ URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/ptnetmapOnBhyve" title="ptnetmap support in bhyve GSoC project">https://wiki.FreeBSD.org/SummerOfCode2015/ptnetmapOnBhyve</a></td></tr><tr><td><a href="http://docs.FreeBSD.org/cgi/mid.cgi?561187FB.8040506" title="http://docs.FreeBSD.org/cgi/mid.cgi?561187FB.8040506">Windows support</a></td><td> URL: <a href="http://docs.FreeBSD.org/cgi/mid.cgi?561187FB.8040506" title="Windows support">http://docs.FreeBSD.org/cgi/mid.cgi?561187FB.8040506</a></td></tr><tr><td><a href="http://docs.FreeBSD.org/cgi/mid.cgi?56118B2B.2040101" title="http://docs.FreeBSD.org/cgi/mid.cgi?56118B2B.2040101">Illumos support</a></td><td> URL: <a href="http://docs.FreeBSD.org/cgi/mid.cgi?56118B2B.2040101" title="Illumos support">http://docs.FreeBSD.org/cgi/mid.cgi?56118B2B.2040101</a></td></tr></table><p> - Contact: + Contact: Peter Grehan <<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>> <br /> - Contact: + Contact: Neel Natu <<a href="mailto:neel@FreeBSD.org">neel@FreeBSD.org</a>> <br /> - Contact: + Contact: Tycho Nightingale <<a href="mailto:tychon@FreeBSD.org">tychon@FreeBSD.org</a>> <br /> - Contact: + Contact: Allan Jude <<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>> <br /> - Contact: + Contact: Michael Dexter <<a href="mailto:editor@callfortesting.org">editor@callfortesting.org</a>> @@ -581,22 +580,22 @@ URL: <a href="http://llvm.org/releases/3.7.0/docs/ReleaseNotes.html" title="LLVM 3.7.0 Release Notes">http://llvm.org/releases/3.7.0/docs/ReleaseNotes.html</a></td></tr><tr><td><a href="http://llvm.org/releases/3.7.0/tools/clang/docs/ReleaseNotes.html" title="http://llvm.org/releases/3.7.0/tools/clang/docs/ReleaseNotes.html">Clang 3.7.0 Release Notes</a></td><td> URL: <a href="http://llvm.org/releases/3.7.0/tools/clang/docs/ReleaseNotes.html" title="Clang 3.7.0 Release Notes">http://llvm.org/releases/3.7.0/tools/clang/docs/ReleaseNotes.html</a></td></tr><tr><td><a href="https://bugs.freebsd.org/201377" title="https://bugs.freebsd.org/201377">PR 201377 Ports exp-run</a></td><td> URL: <a href="https://bugs.freebsd.org/201377" title="PR 201377 Ports exp-run">https://bugs.freebsd.org/201377</a></td></tr></table><p> - Contact: + Contact: Dimitry Andric <<a href="mailto:dim@FreeBSD.org">dim@FreeBSD.org</a>> <br /> - Contact: + Contact: Ed Maste <<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>> <br /> - Contact: + Contact: Roman Divacky <<a href="mailto:rdivacky@FreeBSD.org">rdivacky@FreeBSD.org</a>> <br /> - Contact: + Contact: Davide Italiano <<a href="mailto:davide@FreeBSD.org">davide@FreeBSD.org</a>> @@ -636,7 +635,7 @@ Test and report issues with the new tool chain. </li></ol><hr /><h2><a name="DTrace-and-TCP" href="#DTrace-and-TCP" id="DTrace-and-TCP">DTrace and TCP</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://svnweb.freebsd.org/changeset/base/287759" title="https://svnweb.freebsd.org/changeset/base/287759">Commit adding trace points replacing TCPDEBUG</a></td><td> URL: <a href="https://svnweb.freebsd.org/changeset/base/287759" title="Commit adding trace points replacing TCPDEBUG">https://svnweb.freebsd.org/changeset/base/287759</a></td></tr></table><p> - Contact: + Contact: George Neville-Neil <<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>> @@ -653,7 +652,7 @@ URL: <a href="http://blog.grem.de/pages/c720.html" title="Blog post on how to get things working">http://blog.grem.de/pages/c720.html</a></td></tr><tr><td><a href="http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.html" title="http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.html">Blog post with links to commits in HEAD</a></td><td> URL: <a href="http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.html" title="Blog post with links to commits in HEAD">http://blog.grem.de/sysadmin/FreeBSD-On-AcerC720-Merged-2015-07-25-23-30.html</a></td></tr><tr><td><a href="http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html" title="http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html">Backported patch for 10.2-RELEASE</a></td><td> URL: <a href="http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html" title="Backported patch for 10.2-RELEASE">http://blog.grem.de/sysadmin/FreeBSD-10.2-On-AcerC720-2015-09-19-17-00.html</a></td></tr></table><p> - Contact: + Contact: Michael Gmelin <<a href="mailto:freebsd@grem.de">freebsd@grem.de</a>> @@ -684,7 +683,7 @@ <p>Thanks to everyone who helped in the process. I couldn't have done it without you (you know who you are).</p> <hr /><h2><a name="High-Availability-Clustering-in-CTL" href="#High-Availability-Clustering-in-CTL" id="High-Availability-Clustering-in-CTL">High Availability Clustering in CTL</a></h2><p> - Contact: + Contact: Alexander Motin <<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>> @@ -734,7 +733,7 @@ <p>This project was sponsored by iXsystems, Inc..</p><hr /><h2><a name="Multipath-TCP-for-FreeBSD" href="#Multipath-TCP-for-FreeBSD" id="Multipath-TCP-for-FreeBSD">Multipath TCP for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://caia.swin.edu.au/urp/newtcp/mptcp/" title="http://caia.swin.edu.au/urp/newtcp/mptcp/">MPTCP for FreeBSD Project Website</a></td><td> URL: <a href="http://caia.swin.edu.au/urp/newtcp/mptcp/" title="MPTCP for FreeBSD Project Website">http://caia.swin.edu.au/urp/newtcp/mptcp/</a></td></tr><tr><td><a href="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/" title="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/">MPTCP for FreeBSD Source Repository</a></td><td> URL: <a href="https://bitbucket.org/nw-swin/caia-mptcp-freebsd/" title="MPTCP for FreeBSD Source Repository">https://bitbucket.org/nw-swin/caia-mptcp-freebsd/</a></td></tr></table><p> - Contact: + Contact: Nigel Williams <<a href="mailto:njwilliams@swin.edu.au">njwilliams@swin.edu.au</a>> @@ -782,12 +781,12 @@ current patch.</p> </li></ol><hr /><h2><a name="Porting-bhyve-to-ARM-based-Platforms" href="#Porting-bhyve-to-ARM-based-Platforms" id="Porting-bhyve-to-ARM-based-Platforms">Porting bhyve to ARM-based Platforms</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm" title="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm">Project Wiki page</a></td><td> URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm" title="Project Wiki page">https://wiki.FreeBSD.org/SummerOfCode2015/PortingBhyveToArm</a></td></tr></table><p> - Contact: + Contact: Mihai Carabas <<a href="mailto:mihai@FreeBSD.org">mihai@FreeBSD.org</a>> <br /> - Contact: + Contact: Peter Grehan <<a href="mailto:grehan@FreeBSD.org">grehan@FreeBSD.org</a>> @@ -811,7 +810,7 @@ <p>Port to ARMv8.</p> </li></ol><hr /><h2><a name="Root-Remount" href="#Root-Remount" id="Root-Remount">Root Remount</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D3693" title="https://reviews.freebsd.org/D3693">Userland code review</a></td><td> URL: <a href="https://reviews.freebsd.org/D3693" title="Userland code review">https://reviews.freebsd.org/D3693</a></td></tr></table><p> - Contact: + Contact: Edward Tomasz Napierala <<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>> @@ -837,7 +836,7 @@ URL: <a href="https://wiki.FreeBSD.org/Graphics" title="Graphics stack roadmap and supported hardware matrix">https://wiki.FreeBSD.org/Graphics</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/graphics/" title="http://blogs.freebsdish.org/graphics/">Graphics stack team blog</a></td><td> URL: <a href="http://blogs.freebsdish.org/graphics/" title="Graphics stack team blog">http://blogs.freebsdish.org/graphics/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-graphics" title="https://github.com/freebsd/freebsd-ports-graphics">Ports development tree on GitHub</a></td><td> URL: <a href="https://github.com/freebsd/freebsd-ports-graphics" title="Ports development tree on GitHub">https://github.com/freebsd/freebsd-ports-graphics</a></td></tr></table><p> - Contact: + Contact: FreeBSD Graphics team <<a href="mailto:freebsd-x11@FreeBSD.org">freebsd-x11@FreeBSD.org</a>> </p> @@ -881,7 +880,7 @@ URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html" title="Roadmap">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/roadmap.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html">Commands</a></td><td> URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html" title="Commands">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/commands.html</a></td></tr><tr><td><a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html" title="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html">A slightly outdated nosh Guide</a></td><td> URL: <a href="http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html" title="A slightly outdated nosh Guide">http://homepage.ntlworld.com./jonathan.deboynepollard/Softwares/nosh/guide/index.html</a></td></tr></table><p> - Contact: + Contact: Jonathan de Boyne Pollard <<a href="mailto:J.deBoynePollard-newsgroups@NTLWorld.COM">J.deBoynePollard-newsgroups@NTLWorld.COM</a>> @@ -971,12 +970,12 @@ advantage of some available <tt>nosh</tt> package mechanisms.</p> </li></ol><hr /><h2><a name="UEFI-Boot-and-Framebuffer-Support" href="#UEFI-Boot-and-Framebuffer-Support" id="UEFI-Boot-and-Framebuffer-Support">UEFI Boot and Framebuffer Support</a></h2><p> - Contact: + Contact: Ed Maste <<a href="mailto:emaste@freebsd.org">emaste@freebsd.org</a>> <br /> - Contact: + Contact: Marcel Moolenaar <<a href="mailto:marcel@freebsd.org">marcel@freebsd.org</a>> @@ -991,7 +990,7 @@ Macs.</p> <h3>Open tasks:</h3><ol><li>Test FreeBSD head and FreeBSD-STABLE snapshots on a variety of UEFI implementations.</li></ol><hr /><h2><a name="ZFS-Code-Sync-with-Latest-Illumos" href="#ZFS-Code-Sync-with-Latest-Illumos" id="ZFS-Code-Sync-with-Latest-Illumos">ZFS Code Sync with Latest Illumos</a></h2><p> - Contact: + Contact: Alexander Motin <<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>> @@ -1020,7 +1019,7 @@ the stable/10 branch. </p> <hr /><h2><a name="ZFS-Support-for-UEFI-Boot/Loader" href="#ZFS-Support-for-UEFI-Boot/Loader" id="ZFS-Support-for-UEFI-Boot/Loader">ZFS Support for UEFI Boot/Loader</a></h2><p> - Contact: + Contact: Eric McCorkle <<a href="mailto:eric@metricspace.net">eric@metricspace.net</a>> @@ -1050,7 +1049,7 @@ URL: <a href="http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug" title="PCIe Hot-plug Perforce Branch">http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/pciehotplug</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/changeset/base/r281874" title="https://svnweb.FreeBSD.org/changeset/base/r281874">Commit adding bridge save/restore</a></td><td> URL: <a href="https://svnweb.FreeBSD.org/changeset/base/r281874" title="Commit adding bridge save/restore">https://svnweb.FreeBSD.org/changeset/base/r281874</a></td></tr><tr><td><a href="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp" title="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp">Github branch with patches</a></td><td> URL: <a href="https://github.com/FreeBSDFoundation/freebsd/tree/pciehp" title="Github branch with patches">https://github.com/FreeBSDFoundation/freebsd/tree/pciehp</a></td></tr></table><p> - Contact: + Contact: John-Mark Gurney <<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>> @@ -1091,12 +1090,12 @@ using a proper state machine.</p> </li></ol><hr /><h2><a name="Cavium-LiquidIO-Smart-NIC-Driver" href="#Cavium-LiquidIO-Smart-NIC-Driver" id="Cavium-LiquidIO-Smart-NIC-Driver">Cavium LiquidIO Smart NIC Driver</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cavium.com/LiquidIO_Application_Acceleration_Adapters.html" title="http://www.cavium.com/LiquidIO_Application_Acceleration_Adapters.html">LiquidIO product page</a></td><td> URL: <a href="http://www.cavium.com/LiquidIO_Application_Acceleration_Adapters.html" title="LiquidIO product page">http://www.cavium.com/LiquidIO_Application_Acceleration_Adapters.html</a></td></tr></table><p> - Contact: + Contact: Stanislaw Kardach <<a href="mailto:kda@semihalf.com">kda@semihalf.com</a>> <br /> - Contact: + Contact: Zyta Racia <<a href="mailto:zr@semihalf.com">zr@semihalf.com</a>> @@ -1149,7 +1148,7 @@ URL: <a href="https://github.com/NuxiNL/cloudlibc" title="CloudABI project page">https://github.com/NuxiNL/cloudlibc</a></td></tr><tr><td><a href="https://github.com/NuxiNL/cloudabi-ports" title="https://github.com/NuxiNL/cloudabi-ports">CloudABI Ports Collection</a></td><td> URL: <a href="https://github.com/NuxiNL/cloudabi-ports" title="CloudABI Ports Collection">https://github.com/NuxiNL/cloudabi-ports</a></td></tr><tr><td><a href="https://www.youtube.com/watch?v=LTHSZGVvLw4" title="https://www.youtube.com/watch?v=LTHSZGVvLw4">CloudABI presentation at FrOSCon</a></td><td> URL: <a href="https://www.youtube.com/watch?v=LTHSZGVvLw4" title="CloudABI presentation at FrOSCon">https://www.youtube.com/watch?v=LTHSZGVvLw4</a></td></tr></table><p> - Contact: + Contact: Ed Schouten <<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>> @@ -1200,12 +1199,12 @@ URL: <a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="FreeBSD PVH DomU wiki page">http://wiki.xen.org/wiki/FreeBSD_PVH</a></td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_Dom0" title="http://wiki.xen.org/wiki/FreeBSD_Dom0">FreeBSD PVH Dom0 wiki page</a></td><td> URL: <a href="http://wiki.xen.org/wiki/FreeBSD_Dom0" title="FreeBSD PVH Dom0 wiki page">http://wiki.xen.org/wiki/FreeBSD_Dom0</a></td></tr><tr><td><a href="http://www.xenproject.org/component/allvideoshare/video/latest/bsdcan-2015-how-to-port-bsd-as-a-xen-on-arm-guest.html" title="http://www.xenproject.org/component/allvideoshare/video/latest/bsdcan-2015-how-to-port-bsd-as-a-xen-on-arm-guest.html">Porting FreeBSD as a Xen ARM guest</a></td><td> URL: <a href="http://www.xenproject.org/component/allvideoshare/video/latest/bsdcan-2015-how-to-port-bsd-as-a-xen-on-arm-guest.html" title="Porting FreeBSD as a Xen ARM guest">http://www.xenproject.org/component/allvideoshare/video/latest/bsdcan-2015-how-to-port-bsd-as-a-xen-on-arm-guest.html</a></td></tr></table><p> - Contact: + Contact: Roger Pau Monn <<a href="mailto:royger@FreeBSD.org">royger@FreeBSD.org</a>> <br /> - Contact: + Contact: Julien Grall <<a href="mailto:julien.grall@citrix.com">julien.grall@citrix.com</a>> @@ -1250,12 +1249,12 @@ </li></ol><hr /><h2><a name="ioat(4)-Driver-Import" href="#ioat(4)-Driver-Import" id="ioat(4)-Driver-Import">ioat(4) Driver Import</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology" title="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology">Wikipedia article on IOAT</a></td><td> URL: <a href="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology" title="Wikipedia article on IOAT">https://en.wikipedia.org/wiki/I/O_Acceleration_Technology</a></td></tr><tr><td><a href="https://svnweb.FreeBSD.org/base?view=revision&revision=r287117" title="https://svnweb.FreeBSD.org/base?view=revision&revision=r287117">Commit importing ioat(4)</a></td><td> URL: <a href="https://svnweb.FreeBSD.org/base?view=revision&revision=r287117" title="Commit importing ioat(4)">https://svnweb.FreeBSD.org/base?view=revision&revision=r287117</a></td></tr></table><p> - Contact: + Contact: Jim Harris <<a href="mailto:jimharris@FreeBSD.org">jimharris@FreeBSD.org</a>> <br /> - Contact: + Contact: Conrad Meyer <<a href="mailto:cem@FreeBSD.org">cem@FreeBSD.org</a>> @@ -1270,7 +1269,7 @@ transparent; applications must be adapted to take advantage of the hardware.</p> - <p>Some I/OAT models support more advanced copying modes, such as + <p>Some I/OAT models support more advanced copying modes, such as XOR; these modes are not yet supported in the <tt>ioat(4)</tt> driver.</p> <p>This project was sponsored by Intel Corporation, and EMC / Isilon Storage Division.</p><h3>Open tasks:</h3><ol><li> @@ -1279,17 +1278,17 @@ </li><li> <p>Support for the more advanced copy modes.</p> </li></ol><hr /><h2><a name="IPsec-Upgrades" href="#IPsec-Upgrades" id="IPsec-Upgrades">IPsec Upgrades</a></h2><p> - Contact: + Contact: George Neville-Neil <<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>> <br /> - Contact: + Contact: John-Mark Gurney <<a href="mailto:jmg@FreeBSD.org">jmg@FreeBSD.org</a>> <br /> - Contact: + Contact: Ermal Lui <<a href="mailto:eri@FreeBSD.org">eri@FreeBSD.org</a>> @@ -1305,17 +1304,17 @@ <p>This project was sponsored by Netgate, and The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li> <p>Performance improvements and other tweaks are ongoing.</p> </li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="Atomics" href="#Atomics" id="Atomics">Atomics</a></h2><p> - Contact: + Contact: Konstantin Belousov <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>> <br /> - Contact: + Contact: Alan Cox <<a href="mailto:alc@FreeBSD.org">alc@FreeBSD.org</a>> <br /> - Contact: + Contact: Bruce Evans <<a href="mailto:bde@FreeBSD.org">bde@FreeBSD.org</a>> @@ -1342,7 +1341,7 @@ speculative execution. More precisely, it specifies the extent to which the machine may visibly reorder memory accesses to optimize performance. Unfortunately, - there are almost as many models as architectures. + there are almost as many models as architectures. Some architectures, for example IA32 or Sparcv9 TSO, are relatively strongly ordered. In contrast, others, like PowerPC or ARM, are very relaxed. In effect, atomics define a @@ -1436,17 +1435,17 @@ include missed barriers in r287556.</li> </ul> <p>This project was sponsored by The FreeBSD Foundation (Konstantin Belousov's work).</p><hr /><h2><a name="FreeBSD-on-Cavium-ThunderX-(arm64)" href="#FreeBSD-on-Cavium-ThunderX-(arm64)" id="FreeBSD-on-Cavium-ThunderX-(arm64)">FreeBSD on Cavium ThunderX (arm64)</a></h2><p> - Contact: + Contact: Dominik Ermel <<a href="mailto:der@semihalf.com">der@semihalf.com</a>> <br /> - Contact: + Contact: Wojciech Macek <<a href="mailto:wma@semihalf.com">wma@semihalf.com</a>> <br /> - Contact: + Contact: Zbigniew Bodek <<a href="mailto:zbb@semihalf.com">zbb@semihalf.com</a>> @@ -1489,7 +1488,7 @@ </li></ol><hr /><h2><a name="FreeBSD-on-the-HiKey-ARMv8-Board" href="#FreeBSD-on-the-HiKey-ARMv8-Board" id="FreeBSD-on-the-HiKey-ARMv8-Board">FreeBSD on the HiKey ARMv8 Board</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64/HiKey" title="https://wiki.FreeBSD.org/arm64/HiKey">HiKey wiki entry</a></td><td> URL: <a href="https://wiki.FreeBSD.org/arm64/HiKey" title="HiKey wiki entry">https://wiki.FreeBSD.org/arm64/HiKey</a></td></tr><tr><td><a href="https://www.96boards.org/products/ce/hikey/" title="https://www.96boards.org/products/ce/hikey/">Hardware description</a></td><td> URL: <a href="https://www.96boards.org/products/ce/hikey/" title="Hardware description">https://www.96boards.org/products/ce/hikey/</a></td></tr></table><p> - Contact: + Contact: Andrew Turner <<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>> @@ -1518,12 +1517,12 @@ <p>Add thermal management.</p> </li></ol><hr /><h2><a name="FreeBSD/arm64" href="#FreeBSD/arm64" id="FreeBSD/arm64">FreeBSD/arm64</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/arm64" title="https://wiki.FreeBSD.org/arm64">FreeBSD arm64 wiki page</a></td><td> URL: <a href="https://wiki.FreeBSD.org/arm64" title="FreeBSD arm64 wiki page">https://wiki.FreeBSD.org/arm64</a></td></tr></table><p> - Contact: + Contact: Andrew Turner <<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>> <br /> - Contact: + Contact: Ed Maste <<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>> @@ -1550,17 +1549,17 @@ </li></ol><hr /><h2><a name="FreeBSD/RISC-V-Port" href="#FreeBSD/RISC-V-Port" id="FreeBSD/RISC-V-Port">FreeBSD/RISC-V Port</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/riscv" title="https://wiki.freebsd.org/riscv">FreeBSD wiki RISC-V</a></td><td> URL: <a href="https://wiki.freebsd.org/riscv" title="FreeBSD wiki RISC-V">https://wiki.freebsd.org/riscv</a></td></tr><tr><td><a href="https://people.freebsd.org/~br/riscv-singleuser.txt" title="https://people.freebsd.org/~br/riscv-singleuser.txt">Single user boot log</a></td><td> URL: <a href="https://people.freebsd.org/~br/riscv-singleuser.txt" title="Single user boot log">https://people.freebsd.org/~br/riscv-singleuser.txt</a></td></tr></table><p> - Contact: + Contact: Ruslan Bukin <<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>> <br /> - Contact: + Contact: Arun Thomas <<a href="mailto:arun.thomas@baesystems.com">arun.thomas@baesystems.com</a>> <br /> - Contact: + Contact: Ed Maste <<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>> @@ -1586,7 +1585,7 @@ <p>This project was sponsored by DARPA, AFRL.</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="mandoc-and-roff-Toolchain" href="#mandoc-and-roff-Toolchain" id="mandoc-and-roff-Toolchain">mandoc and roff Toolchain</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/n-t-roff/heirloom-doctools" title="https://github.com/n-t-roff/heirloom-doctools">Heirloom doctools</a></td><td> URL: <a href="https://github.com/n-t-roff/heirloom-doctools" title="Heirloom doctools">https://github.com/n-t-roff/heirloom-doctools</a></td></tr><tr><td><a href="http://mdocml.bsd.lv/" title="http://mdocml.bsd.lv/">mandoc</a></td><td> URL: <a href="http://mdocml.bsd.lv/" title="mandoc">http://mdocml.bsd.lv/</a></td></tr></table><p> - Contact: + Contact: Baptiste Daroussin <<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>> @@ -1683,12 +1682,12 @@ <tt>mbedtls</tt>.</p> </li></ol><hr /><h2><a name="sesutil(8)" href="#sesutil(8)" id="sesutil(8)">sesutil(8)</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://en.wikipedia.org/wiki/SCSI_Enclosure_Services" title="https://en.wikipedia.org/wiki/SCSI_Enclosure_Services">Wikipedia: SCSI Enclosure Services (SES)</a></td><td> URL: <a href="https://en.wikipedia.org/wiki/SCSI_Enclosure_Services" title="Wikipedia: SCSI Enclosure Services (SES)">https://en.wikipedia.org/wiki/SCSI_Enclosure_Services</a></td></tr></table><p> - Contact: + Contact: Baptiste Daroussin <<a href="mailto:bapt@FreeBSD.org">bapt@FreeBSD.org</a>> <br /> - Contact: + Contact: Allan Jude <<a href="mailto:allanjude@FreeBSD.org">allanjude@FreeBSD.org</a>> @@ -1725,12 +1724,12 @@ </li><li> <p>Add support for <tt>libxo</tt> output types.</p> </li></ol><hr /><h2><a name="truss(1)" href="#truss(1)" id="truss(1)">truss(1)</a></h2><p> - Contact: + Contact: John Baldwin <<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>> <br /> - Contact: + Contact: Bryan Drewery <<a href="mailto:bdrewery@FreeBSD.org">bdrewery@FreeBSD.org</a>> @@ -1767,7 +1766,7 @@ FreeBSD/amd64.</p> </li></ol><hr /><h2><a name="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D3341" title="https://reviews.FreeBSD.org/D3341">Extend libkvm to support cross-debugging of vmcores</a></td><td> URL: <a href="https://reviews.FreeBSD.org/D3341" title="Extend libkvm to support cross-debugging of vmcores">https://reviews.FreeBSD.org/D3341</a></td></tr></table><p> - Contact: + Contact: John Baldwin <<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>> @@ -1807,12 +1806,12 @@ URL: <a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468" title="PR for the new port">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468</a></td></tr><tr><td><a href="https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md" title="https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md">Installation guide</a></td><td> URL: <a href="https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md" title="Installation guide">https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md</a></td></tr><tr><td><a href="https://github.com/gitlabhq/gitlabhq/" title="https://github.com/gitlabhq/gitlabhq/">GitLab Source Tree</a></td><td> URL: <a href="https://github.com/gitlabhq/gitlabhq/" title="GitLab Source Tree">https://github.com/gitlabhq/gitlabhq/</a></td></tr></table><p> - Contact: + Contact: Torsten Zhlsdorff <<a href="mailto:ports@toco-domains.de">ports@toco-domains.de</a>> <br /> - Contact: + Contact: Michael Fausten <<a href="mailto:ports@michael-fausten.de">ports@michael-fausten.de</a>> @@ -1927,7 +1926,7 @@ </li></ol><hr /><h2><a name="Node.js-Modules" href="#Node.js-Modules" id="Node.js-Modules">Node.js Modules</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.assembla.com/spaces/cozycloud/subversion/source" title="https://www.assembla.com/spaces/cozycloud/subversion/source">Node.js modules</a></td><td> URL: <a href="https://www.assembla.com/spaces/cozycloud/subversion/source" title="Node.js modules">https://www.assembla.com/spaces/cozycloud/subversion/source</a></td></tr><tr><td><a href="https://people.FreeBSD.org/~olivierd/porters-handbook/using-nodejs.html" title="https://people.FreeBSD.org/~olivierd/porters-handbook/using-nodejs.html">Pre-draft documentation</a></td><td> URL: <a href="https://people.FreeBSD.org/~olivierd/porters-handbook/using-nodejs.html" title="Pre-draft documentation">https://people.FreeBSD.org/~olivierd/porters-handbook/using-nodejs.html</a></td></tr></table><p> - Contact: + Contact: Olivier Duchateau <<a href="mailto:olivierd@FreeBSD.org">olivierd@FreeBSD.org</a>> @@ -1973,7 +1972,7 @@ URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="Twitter feed">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr">Facebook page</a></td><td> URL: <a href="http://www.facebook.com/portmgr" title="Facebook page">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383">Google+ page</a></td><td> URL: <a href="http://plus.google.com/communities/108335846196454338383" title="Google+ page">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p> - Contact: + Contact: Frederic Culot <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>> @@ -2022,7 +2021,7 @@ the ports tree internals. And if you already do these tasks, many thanks to you! </p> </li></ol><hr /><h2><a name="Ports-on-PowerPC" href="#Ports-on-PowerPC" id="Ports-on-PowerPC">Ports on PowerPC</a></h2><p> - Contact: + Contact: Alexey Dokuchaev <<a href="mailto:danfe@FreeBSD.org">danfe@FreeBSD.org</a>> @@ -2112,7 +2111,7 @@ <br /> Contact: FreeBSD Translators <<a href="mailto:freebsd-translators@FreeBSD.org">freebsd-translators@FreeBSD.org</a>> <br /> - Contact: + Contact: Warren Block <<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>> @@ -2171,7 +2170,7 @@ <p>Develop and test code to translate manual pages.</p> </li></ol><hr /><h2><a name="Website-CSS-Update" href="#Website-CSS-Update" id="Website-CSS-Update">Website CSS Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSD.org/" title="https://www.FreeBSD.org/">FreeBSD Main Site</a></td><td> URL: <a href="https://www.FreeBSD.org/" title="FreeBSD Main Site">https://www.FreeBSD.org/</a></td></tr></table><p> - Contact: + Contact: Warren Block <<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>> @@ -2207,18 +2206,18 @@ complex and ambitious project than it might seem.</p> </li></ol><hr /><br /><h1><a name="Google-Summer-of-Code" href="#Google-Summer-of-Code" id="Google-Summer-of-Code">Google Summer of Code</a></h1><br /><h2><a name="Allwinner-A10/A20-Support" href="#Allwinner-A10/A20-Support" id="Allwinner-A10/A20-Support">Allwinner A10/A20 Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner" title="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner">Wiki page</a></td><td> URL: <a href="https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner" title="Wiki page">https://wiki.FreeBSD.org/FreeBSD/arm/Allwinner</a></td></tr></table><p> - Contact: + Contact: Luiz Otavio O Souza <<a href="mailto:loos@FreeBSD.org">loos@FreeBSD.org</a>> <br /> - Contact: + Contact: Pratik Singhal <<a href="mailto:ps06756@gmail.com">ps06756@gmail.com</a>> </p> <p>The Allwinner A10 and A20 chips are ARM CPUs found in - increasingly common development boards and other devices, such as + increasingly common development boards and other devices, such as the Cubieboard/Cubieboard 2 and the Banana Pi.</p> <p>With the end of a GSoC project by Pratik Singhal, our A10 and @@ -2238,12 +2237,12 @@ <p>Fix <tt>if_dwc</tt> for better performance.</p> </li></ol><hr /><h2><a name="mtree-Parsing-and-Manipulation-Library" href="#mtree-Parsing-and-Manipulation-Library" id="mtree-Parsing-and-Manipulation-Library">mtree Parsing and Manipulation Library</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/mtreeParsingLibrary" title="https://wiki.FreeBSD.org/SummerOfCode2015/mtreeParsingLibrary">Wiki page</a></td><td> URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/mtreeParsingLibrary" title="Wiki page">https://wiki.FreeBSD.org/SummerOfCode2015/mtreeParsingLibrary</a></td></tr></table><p> - Contact: + Contact: Michal Ratajsky <<a href="mailto:michal@FreeBSD.org">michal@FreeBSD.org</a>> <br /> - Contact: + Contact: Brooks Davis <<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>> @@ -2290,22 +2289,22 @@ page.</p> </li></ol><hr /><h2><a name="Multiqueue-Testing" href="#Multiqueue-Testing" id="Multiqueue-Testing">Multiqueue Testing</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/MultiqueueTestingProject" title="https://wiki.FreeBSD.org/SummerOfCode2015/MultiqueueTestingProject">Project Wiki Page</a></td><td> URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/MultiqueueTestingProject" title="Project Wiki Page">https://wiki.FreeBSD.org/SummerOfCode2015/MultiqueueTestingProject</a></td></tr></table><p> - Contact: + Contact: Tiwei Bie <<a href="mailto:btw@FreeBSD.org">btw@FreeBSD.org</a>> <br /> - Contact: + Contact: Hiren Panchasara <<a href="mailto:hiren@FreeBSD.org">hiren@FreeBSD.org</a>> <br /> - Contact: + Contact: George Neville-Neil <<a href="mailto:gnn@FreeBSD.org">gnn@FreeBSD.org</a>> <br /> - Contact: + Contact: Robert Watson <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>> @@ -2346,7 +2345,7 @@ suitable for committing to FreeBSD head.</p> <p>This project was sponsored by Google Summer of Code 2015.</p><hr /><h2><a name="Update-Ficl-in-Bootloader" href="#Update-Ficl-in-Bootloader" id="Update-Ficl-in-Bootloader">Update Ficl in Bootloader</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/SummerOfCode2015/UpdateFiclInBootloader" title="https://wiki.FreeBSD.org/SummerOfCode2015/UpdateFiclInBootloader">Wiki Page</a></td><td> URL: <a href="https://wiki.FreeBSD.org/SummerOfCode2015/UpdateFiclInBootloader" title="Wiki Page">https://wiki.FreeBSD.org/SummerOfCode2015/UpdateFiclInBootloader</a></td></tr></table><p> - Contact: + Contact: Colin Lord <<a href="mailto:clord@FreeBSD.org">clord@FreeBSD.org</a>> @@ -2374,7 +2373,7 @@ <p>This project was sponsored by Google Summer of Code 2015.</p><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/">Foundation website</a></td><td> URL: <a href="http://www.FreeBSDFoundation.org/" title="Foundation website">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td> URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p> - Contact: + Contact: Deb Goodkin <<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>> @@ -2546,7 +2545,7 @@ <hr /><h2><a name="ZFSguru" href="#ZFSguru" id="ZFSguru">ZFSguru</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://zfsguru.com" title="http://zfsguru.com">Home page</a></td><td> URL: <a href="http://zfsguru.com" title="Home page">http://zfsguru.com</a></td></tr><tr><td><a href="http://zfsguru.com/forum/zfsgurudevelopment/1038" title="http://zfsguru.com/forum/zfsgurudevelopment/1038">Forum post on Gnome3 debugging</a></td><td> URL: <a href="http://zfsguru.com/forum/zfsgurudevelopment/1038" title="Forum post on Gnome3 debugging">http://zfsguru.com/forum/zfsgurudevelopment/1038</a></td></tr></table><p> - Contact: + Contact: Jason Edwards <<a href="mailto:jason@zfsguru.com">jason@zfsguru.com</a>> diff --git a/website/content/en/status/report-2015-10-2015-12.html b/website/content/en/status/report-2015-10-2015-12.html index f32802619e..27fba6b54a 100644 --- a/website/content/en/status/report-2015-10-2015-12.html +++ b/website/content/en/status/report-2015-10-2015-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2016-01-2016-03.html b/website/content/en/status/report-2016-01-2016-03.html index 81bd0febdf..9c9b34c510 100644 --- a/website/content/en/status/report-2016-01-2016-03.html +++ b/website/content/en/status/report-2016-01-2016-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2016-04-2016-06.html b/website/content/en/status/report-2016-04-2016-06.html index 4d5a4b77f3..76122aa99e 100644 --- a/website/content/en/status/report-2016-04-2016-06.html +++ b/website/content/en/status/report-2016-04-2016-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2016-07-2016-09.html b/website/content/en/status/report-2016-07-2016-09.html index 7c459a4b4c..89fad935fd 100644 --- a/website/content/en/status/report-2016-07-2016-09.html +++ b/website/content/en/status/report-2016-07-2016-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2016-10-2016-12.html b/website/content/en/status/report-2016-10-2016-12.html index 688a25a99b..74acad6922 100644 --- a/website/content/en/status/report-2016-10-2016-12.html +++ b/website/content/en/status/report-2016-10-2016-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2017-01-2017-03.html b/website/content/en/status/report-2017-01-2017-03.html index aad5c3e851..5160caf340 100644 --- a/website/content/en/status/report-2017-01-2017-03.html +++ b/website/content/en/status/report-2017-01-2017-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2017-04-2017-06.html b/website/content/en/status/report-2017-04-2017-06.html index 5cae9e6f63..150848f41f 100644 --- a/website/content/en/status/report-2017-04-2017-06.html +++ b/website/content/en/status/report-2017-04-2017-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2017-07-2017-09.html b/website/content/en/status/report-2017-07-2017-09.html index 46205b9d94..6ca1fdf2b0 100644 --- a/website/content/en/status/report-2017-07-2017-09.html +++ b/website/content/en/status/report-2017-07-2017-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -880,7 +880,7 @@ This uses the recently added NT_LWPINFO note to extract signal information from process cores.</p> - <p>Hangs that occured when GDB's <tt>kill</tt> command was used + <p>Hangs that occurred when GDB's <tt>kill</tt> command was used were fixed in FreeBSD in r313992.</p> <h3>Open tasks:</h3><ol><li>Figure out why the powerpc <tt>kgdb</tt> targets are not able to unwind the stack past the initial frame.</li><li>Test support for sparc64 binaries and kernels.</li><li>Add support for debugging powerpc vector registers.</li><li>Implement <tt>info proc</tt> commands.</li><li>Implement <tt>info os</tt> commands.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping diff --git a/website/content/en/status/report-2017-10-2017-12.html b/website/content/en/status/report-2017-10-2017-12.html index ecd6b159bb..20067220f5 100644 --- a/website/content/en/status/report-2017-10-2017-12.html +++ b/website/content/en/status/report-2017-10-2017-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2018-01-2018-09.html b/website/content/en/status/report-2018-01-2018-09.html index 7be5653704..bd5b42be19 100644 --- a/website/content/en/status/report-2018-01-2018-09.html +++ b/website/content/en/status/report-2018-01-2018-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2018-09-2018-12.html b/website/content/en/status/report-2018-09-2018-12.html index 860069a86d..8ee5a48415 100644 --- a/website/content/en/status/report-2018-09-2018-12.html +++ b/website/content/en/status/report-2018-09-2018-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2019-01-2019-03.html b/website/content/en/status/report-2019-01-2019-03.html index a33267f558..f825898c08 100644 --- a/website/content/en/status/report-2019-01-2019-03.html +++ b/website/content/en/status/report-2019-01-2019-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2019-04-2019-06.html b/website/content/en/status/report-2019-04-2019-06.html index 2e2787d9a7..ddb4179f59 100644 --- a/website/content/en/status/report-2019-04-2019-06.html +++ b/website/content/en/status/report-2019-04-2019-06.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2019-07-2019-09.html b/website/content/en/status/report-2019-07-2019-09.html index 6bb07e2d42..f2e48e4fd7 100644 --- a/website/content/en/status/report-2019-07-2019-09.html +++ b/website/content/en/status/report-2019-07-2019-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> @@ -1794,14 +1794,14 @@ and December only and the report will probably be out in mid January.</p><p>-- L the faulting instruction is restarted. If fault cannot be handled for any reason, the next action depends on the mode in which - the fault occured. + the fault occurred. If it was in kernel, and the kernel installed a helper, then the helper is called instead of returning to the faulting instruction. Otherwise, a kernel-mode page fault causes a panic.</p> - <p>If the unhandled fault occured in usermode, then all + <p>If the unhandled fault occurred in usermode, then all Unixes send a signal to the thread whose execution caused the exception. POSIX (or diff --git a/website/content/en/status/report-2019-10-2019-12.html b/website/content/en/status/report-2019-10-2019-12.html index b52580a05d..fae55a5912 100644 --- a/website/content/en/status/report-2019-10-2019-12.html +++ b/website/content/en/status/report-2019-10-2019-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2020-01-2020-03.html b/website/content/en/status/report-2020-01-2020-03.html index c70646259e..07511cc616 100644 --- a/website/content/en/status/report-2020-01-2020-03.html +++ b/website/content/en/status/report-2020-01-2020-03.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2020-04-2020-06.html b/website/content/en/status/report-2020-04-2020-06.html index 0f510cf78d..687ed86cf3 100644 --- a/website/content/en/status/report-2020-04-2020-06.html +++ b/website/content/en/status/report-2020-04-2020-06.html @@ -6,7 +6,6 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="../../favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="../layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" src="../../layout/js/google.js"></script> </head> <body> <div id="containerwrap"> @@ -271,8 +270,8 @@ </ul> </div> </div> - <div id="contentwrap"><h1>Introduction</h1><p>This report will be covering FreeBSD related projects between April and June, -and covers a diverse set of topics ranging from kernel updates over userland + <div id="contentwrap"><h1>Introduction</h1><p>This report will be covering FreeBSD related projects between April and June, +and covers a diverse set of topics ranging from kernel updates over userland and ports, as well as third-party work. </p><p>Some highlights picked with the roll of a d100 include, but are not limited to, the ability to forcibly unmount UFS when the underlying media becomes @@ -280,7 +279,7 @@ inaccessible, added preliminary support for Bluetooth Low Energy, a introduction FreeBSD Office Hours, and a repository of software collections called potluck to be installed with the pot utility, as well as many many more things. </p><p>As a little treat, readers can also get a rare report from the quarterly team. -</p><p>Finally, on behalf of the quarterly team, I would like to extend my deepest +</p><p>Finally, on behalf of the quarterly team, I would like to extend my deepest appreciation and thank you to salvadore@, who decided to take down his shingle. His contributions to not just the quarterly reports themselves, but also the surrounding tooling to many-fold ease the work, are immeasurable. @@ -883,7 +882,7 @@ and posted to the official FreeBSD youtube channel. <li><p><a href="mailto:anne@freebsdfoundation.org" shape="rect">Anne Dickison</a> </p> </li></ul> -<p>Sponsor: ScaleEngine Inc. (video streaming) +<p>Sponsor: ScaleEngine Inc. (video streaming) </p><hr /><h2><a name="Quarterly-Status-Reports-Team" href="#Quarterly-Status-Reports-Team" id="Quarterly-Status-Reports-Team">Quarterly Status Reports Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/news/status/" title="https://www.freebsd.org/news/status/">Quarterly status reports</a></td><td> URL: <a href="https://www.freebsd.org/news/status/" title="Quarterly status reports">https://www.freebsd.org/news/status/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-quarterly" title="https://github.com/freebsd/freebsd-quarterly">Git repository</a></td><td> URL: <a href="https://github.com/freebsd/freebsd-quarterly" title="Git repository">https://github.com/freebsd/freebsd-quarterly</a></td></tr></table><p> @@ -924,7 +923,7 @@ write an entry for earlier reports. <li><p>As you might have noticed, last quarterly calls have been sent to freebsd-quarterly-calls@: this is a new mailing list to which you can <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-quarterly-calls" shape="rect">subscribe</a> - to receive calls for quarterly reports. Please note this is a moderated list, + to receive calls for quarterly reports. Please note this is a moderated list, with very low traffic and a high signal to noise ratio. </p> </li> @@ -1207,15 +1206,15 @@ to make it more modular and easier to enhance. This includes <p>You can help by testing and/or commenting on the code reviews. </p><hr /><h2><a name="Bluetooth-Support" href="#Bluetooth-Support" id="Bluetooth-Support">Bluetooth Support</a></h2><p> Contact: Marc Veldman <<a href="mailto:marc@bumblingdork.com">marc@bumblingdork.com</a>> - </p><p>Bluetooth is a wireless technology for creating personal networks, + </p><p>Bluetooth is a wireless technology for creating personal networks, connecting peripherals like keyboards and mice but also speakers and heart rate monitors. </p> -<p>FreeBSD has limited Bluetooth Basic Rate (BR) support and no functional +<p>FreeBSD has limited Bluetooth Basic Rate (BR) support and no functional Bluetooth Low Energy (LE) support. </p> -<p>During this quarter many small improvements have been made to help the -development of Bluetooth LE support. A number of commands have been added to +<p>During this quarter many small improvements have been made to help the +development of Bluetooth LE support. A number of commands have been added to hccontrol(8), mainly to do LE functions. It is now possible to scan for LE devices within range using hccontrol. A panic that occurred when enabling LE support has also been fixed. @@ -1407,7 +1406,7 @@ later in the year. URL: <a href="https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html" title="Intel SDM">https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html</a></td></tr><tr><td><a href="https://software.intel.com/content/www/us/en/develop/download/5-level-paging-and-5-level-ept-white-paper.html" title="https://software.intel.com/content/www/us/en/develop/download/5-level-paging-and-5-level-ept-white-paper.html">Intel whitepaper</a></td><td> URL: <a href="https://software.intel.com/content/www/us/en/develop/download/5-level-paging-and-5-level-ept-white-paper.html" title="Intel whitepaper">https://software.intel.com/content/www/us/en/develop/download/5-level-paging-and-5-level-ept-white-paper.html</a></td></tr></table><p> Contact: Konstantin Belousov <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>> - </p><p>Since its introduction, x86 Long Mode (AKA 64bit execution mode, amd64 + </p><p>Since its introduction, x86 Long Mode (AKA 64bit execution mode, amd64 in FreeBSD terminology) uses 4-level paging structures, which provides 48 bits of virtual address space (LA48). FreeBSD evenly divides the space between userspace and kernel, giving both 47 virtual address @@ -1616,9 +1615,9 @@ Lockless routing lookups will remove lookup bottlenecks, improve both dataplane <p>The initial routing kpi was introduced back in 1980. It was a nice generic approach back then, as no one knew how the protocols would evolve. It has been enormously successful as it was able to survive for 20+ years. </p> -<p>Unfortunately, this kpi does not try to protect subsystem internals from the outside users, resulting in tight coupling with other subsystems. As a result, making changes is hard, leading to compromises and piling technical debt. +<p>Unfortunately, this kpi does not try to protect subsystem internals from the outside users, resulting in tight coupling with other subsystems. As a result, making changes is hard, leading to compromises and piling technical debt. </p> -<h3>Implementation overview</h3> +<h3>Implementation overview</h3> <p>Most changes are based on introduction of the concept of nexthops. Nexthops are separate datastructures, containing all necessary information to perform packet forwarding such as gateway, interface and mtu. They are shared among the routes, providing more pre-computed cache-efficient data while requiring less memory. Interested reader can find more detailed description in <a href="https://reviews.freebsd.org/D24141" shape="rect">D24141</a>. Another overview can be found in Nexthop object <a href="https://linuxplumbersconf.org/event/4/contributions/434/attachments/251/436/nexthop-objects-talk.pdf" shape="rect">talk</a> describing Linux implementation. @@ -1706,7 +1705,7 @@ tradeoff that best suits their needs. <li><p>Resolve issues around backwards compatibility when ZSTD is configured but not used </p> </li></ul> -<p>Sponsor: The FreeBSD Foundation +<p>Sponsor: The FreeBSD Foundation </p><hr /><h2><a name="CheriBSD-2020-Q2" href="#CheriBSD-2020-Q2" id="CheriBSD-2020-Q2">CheriBSD 2020 Q2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.cheri-cpu.org" title="http://www.cheri-cpu.org">CHERI-CPU</a></td><td> URL: <a href="http://www.cheri-cpu.org" title="CHERI-CPU">http://www.cheri-cpu.org</a></td></tr><tr><td><a href="https://fett.darpa.mil" title="https://fett.darpa.mil">DARPA FETT Bug Bounty Program</a></td><td> URL: <a href="https://fett.darpa.mil" title="DARPA FETT Bug Bounty Program">https://fett.darpa.mil</a></td></tr></table><p> @@ -1825,7 +1824,7 @@ Contact: IRC #freebsd-riscv channel on freenode<br clear="none" /> a young and evolving platform, one of our goals is to have FreeBSD be a well-supported option for users as RISC-V hardware increases in availability. </p> -<p>This quarter saw a number of improvements to the boot process. +<p>This quarter saw a number of improvements to the boot process. </p> <p>The <code>physmem</code> interface used by arm and arm64 to enumerate physical memory resources was moved to machine-independent code and adopted on RISC-V. As a @@ -2066,7 +2065,7 @@ so this quarter the kde@ team: <li><p>A great deal of preparation has gone into Qt 5.15. Many ports have been pre-emptively patched for this new -- and last -- LTS release of Qt 5. The update itself has not yet landed, pending a few last bits of fallout. -</p> +</p> </li></ul> <p>The kde@ team would like to thank Antoine for many exp-runs, mikael@ for useful tips, swills@ for patience and kai@ for dealing with WebEngine. @@ -2092,7 +2091,7 @@ part of the build. As a consequence, ports for Haskell libraries have been deprecated and removed. </p> <p>Upgrading GHC became a tedious task for a single person, so a new GitHub -repository was created under the FreeBSD organization - +repository was created under the FreeBSD organization - <a href="https://github.com/freebsd/freebsd-ports-haskell" shape="rect">freebsd-ports-haskell</a>. Right now, work is being done on preparing another GHC upgrade in the <code>ghc-upgrade-810</code> branch. Any contributions are welcome. @@ -2208,7 +2207,7 @@ the history of this port, back to its creation in May 2017. <h3>git</h3> <p>Work on git started <a href="https://news.freshports.org/?s=git&searchsubmit=" shape="rect">back in September</a>. -It was ignored for a while and started back in mid-June with +It was ignored for a while and started back in mid-June with the creation of new git-specific jails for commit ingress (commit processing gitdev) and for the website. </p> @@ -2284,8 +2283,8 @@ py37-virtualenv>0:devel/py-virtualenv the "Ports I Maintain" button (if you are logged in). This feature recently branched out to a new automated watch list option: <code>Watch ports I maintain</code>. </p> -<p>This <a href="https://www.freshports.org/report-subscriptions.php" shape="rect">report subscription</a> -will notify you of any commits to the ports you maintain. Your email +<p>This <a href="https://www.freshports.org/report-subscriptions.php" shape="rect">report subscription</a> +will notify you of any commits to the ports you maintain. Your email address on FreshPorts must match the value in the MAINTAINER field of the port. This is always a daily report. </p> @@ -2420,7 +2419,7 @@ packages. <li><p>to maintain SageMath itself and prepare the next release (9.2 is coming!). </p></li></ul> <hr /><br /><h1><a name="Third-Party-Projects" href="#Third-Party-Projects" id="Third-Party-Projects">Third-Party Projects</a></h1><p>Many projects build upon FreeBSD or incorporate components of - FreeBSD into their project. As these projects may be of interest + FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or @@ -2453,7 +2452,7 @@ to improve this project. Contact: Stephan Lichtenauer <<a href="mailto:sl@honeyguide.eu">sl@honeyguide.eu</a>> </p><p>pot is a jail management tool that <a href="https://www.freebsd.org/news/status/report-2020-01-2020-03.html#pot-and-the-nomad-pot-driver" shape="rect">also supports orchestration through nomad</a>. </p> -<p>Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: A repository of pot flavours and complete images for usage with pot. +<p>Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: A repository of pot flavours and complete images for usage with pot. </p> <p>This should simplify setting up complex software with many packages and ports in comparison to manual configuration: Potluck aims to provide a content library as an additional layer of abstraction, on top of existing infrastructure like pkg, that pot has to offer. </p> diff --git a/website/content/en/status/report-2020-07-2020-09.html b/website/content/en/status/report-2020-07-2020-09.html index 08de9755f4..1126c22ef7 100644 --- a/website/content/en/status/report-2020-07-2020-09.html +++ b/website/content/en/status/report-2020-07-2020-09.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2020-10-2020-12.html b/website/content/en/status/report-2020-10-2020-12.html index 1537096bf0..a471d67739 100644 --- a/website/content/en/status/report-2020-10-2020-12.html +++ b/website/content/en/status/report-2020-10-2020-12.html @@ -6,7 +6,7 @@ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <link rel="shortcut icon" href="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" /> <link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" /> - <script type="text/javascript" href="https://www.FreeBSD.org/layout/js/google.js"></script> + </head> <body> <div id="containerwrap"> diff --git a/website/content/en/status/report-2021-01-2021-03/_index.adoc b/website/content/en/status/report-2021-01-2021-03/_index.adoc index 529e4ada2c..e8b0e484d5 100644 --- a/website/content/en/status/report-2021-01-2021-03/_index.adoc +++ b/website/content/en/status/report-2021-01-2021-03/_index.adoc @@ -1,5 +1,5 @@ --- -title: "Introduction" +title: "FreeBSD Quarterly Status Report 1st Quarter 2021" sidenav: about --- diff --git a/website/content/en/status/report-2021-04-2021-06/_index.adoc b/website/content/en/status/report-2021-04-2021-06/_index.adoc index a10dc5b284..5e8af95720 100644 --- a/website/content/en/status/report-2021-04-2021-06/_index.adoc +++ b/website/content/en/status/report-2021-04-2021-06/_index.adoc @@ -1,5 +1,5 @@ --- -title: "Introduction" +title: "FreeBSD Quarterly Status Report 2nd Quarter 2021" sidenav: about --- diff --git a/website/content/en/status/report-2021-10-2021-12/_index.adoc b/website/content/en/status/report-2021-10-2021-12/_index.adoc new file mode 100644 index 0000000000..2de299e189 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/_index.adoc @@ -0,0 +1,131 @@ +--- +title: "FreeBSD Quarterly Status Report 4th Quarter 2021" +sidenav: about +--- + += Introduction +:doctype: article +:toc: macro +:toclevels: 2 +:icons: font +:!sectnums: +:source-highlighter: rouge +:experimental: +:reports-path: content/en/status/report-2021-10-2021-12 + +This report covers FreeBSD related projects for the period between October and December. It is the fourth of four planned reports for 2021, and contains 19 entries. Highlights include faster boot times, more LLDB work, a base OpenSSH update, and more wireless development. + +Yours, + +Pau Amma, Daniel Ebdrup, John-Mark Gurney, and Joe Mingrone + +''' + +toc::[] + +''' + +[[FreeBSD-Team-Reports]] +== FreeBSD Team Reports + +Entries from the various official and semi-official teams, as found in the link:../../administration/[Administration Page]. + +include::{reports-path}/freebsd-foundation.adoc[] + +''' + +include::{reports-path}/portmgr.adoc[] + +''' + +include::{reports-path}/doceng.adoc[] + +''' + +include::{reports-path}/www.adoc[] + +''' + +[[projects]] +== Projects + +Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. + + +include::{reports-path}/aslr.adoc[] + +''' + +include::{reports-path}/boot-performance.adoc[] + +''' + +include::{reports-path}/lldb.adoc[] + +''' + +include::{reports-path}/ls1027a.adoc[] + +''' + +include::{reports-path}/membarrier-rseq.adoc[] + +''' + +include::{reports-path}/openssh.adoc[] + +''' + +include::{reports-path}/vdso.adoc[] + +''' + +[[kernel]] +== Kernel + +Updates to kernel subsystems/features, driver support, filesystems, and more. + + +include::{reports-path}/avx-bug.adoc[] + +''' + +include::{reports-path}/ena.adoc[] + +''' + +include::{reports-path}/iwlwifi.adoc[] + +''' + +include::{reports-path}/ocf-wg.adoc[] + +''' + + +[[ports]] +== Ports + +Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/office.adoc[] + +''' + +[[third-Party-Projects]] +== Third-Party Projects + +Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. +As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. +The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. + +include::{reports-path}/hellosystem.adoc[] + +''' + +include::{reports-path}/pot.adoc[] + +''' diff --git a/website/content/en/status/report-2021-10-2021-12/aslr.adoc b/website/content/en/status/report-2021-10-2021-12/aslr.adoc new file mode 100644 index 0000000000..21d45d04fe --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/aslr.adoc @@ -0,0 +1,29 @@ +=== Enable ASLR by default for 64-bit executables + +Contact: Dawid Gorecki <dgr@semihalf.com> + +Contact: Marcin Wojtas <mw@semihalf.com> + +Address Space Layout Randomization (ASLR) is an exploit mitigation +technique implemented in the majority of modern operating systems. +It involves randomly positioning the base address of an executable +and the position of libraries, heap, and stack, in a process's address +space. Although over the years ASLR proved to not guarantee full OS +security on its own, this mechanism can make exploitation more difficult. + +The Semihalf team made an effort to switch on the address map +randomization for PIE (Position Independent Executables) & non-PIE 64-bit binaries. +Once the link:https://cgit.freebsd.org/src/commit/?id=b014e0f15bc73d80e[patch] was merged to HEAD, +the ASLR feature became enabled for all 64-bit architectures. + +Additionally, the mentioned change disabled +link:https://www.freebsd.org/cgi/man.cgi?query=sbrk&sektion=2[SBRK], +in order to allow utilization of the bss grow region for mappings. +It has no effect without ASLR, so it was applied to all architectures. + +TODO: + +* Improve stackgap feature implementation. + +* MFC to stable/13 branch. + +Sponsor: Stormshield diff --git a/website/content/en/status/report-2021-10-2021-12/avx-bug.adoc b/website/content/en/status/report-2021-10-2021-12/avx-bug.adoc new file mode 100644 index 0000000000..4b99fab1ab --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/avx-bug.adoc @@ -0,0 +1,30 @@ +=== The AVX bug on amd64 + +Commit: gitref:73b357be92385cbb70ba19e7023a736af2c6b493[repository=src] URL: link:https://cgit.freebsd.org/src/commit/?id=73b357be92385cbb70ba19e7023a736af2c6b493[https://cgit.freebsd.org/src/commit/?id=73b357be92385cbb70ba19e7023a736af2c6b493] + +Contact: Konstantin Belousov <kib@FreeBSD.org> + +Some CPUs support the so called init optimization for XSAVE, but not all CPUs +do. And when they do, 'according to complex internal microarchitectural +conditions', the optimization might happen or not. Basically, this +means that sometimes the CPU does not write all of the state on +XSAVE and records in xstate_bv that it did not. + +On signal delivery, the OS provides the saved context interrupted by +the signal to the signal handler. The context includes all CPU state +available to userspace, including FPU registers (XSAVE area). Also, +on return from the signal handler, context is restored, which +allows the handler to modify the main program flow. +When init optimization kicks in, the OS tries to hide init state +optimization from the signal handler, by filling non-saved parts of +the XSAVE area. + +This is where the problem happens. For states parts 0 (x87) and 1 +(SSE/XMM), Intel CPUs do not provide an enumeration of layout in CPUID, +assuming that the OS knows about the regions anyway. The bug was that +the amd64 kernel hardcoded a 32bit size for the XMM save area, effectively +filling %XMM8-%XMM15 with garbage on signal return when init +optimization kicked in, because only specified part of the SSE save +area was copied from the canonical save area. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2021-10-2021-12/boot-performance.adoc b/website/content/en/status/report-2021-10-2021-12/boot-performance.adoc new file mode 100644 index 0000000000..72e91ff7ea --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/boot-performance.adoc @@ -0,0 +1,33 @@ +=== Boot Performance Improvements + +Links: + +link:https://wiki.freebsd.org/BootTime[Wiki page] URL: link:https://wiki.freebsd.org/BootTime[https://wiki.freebsd.org/BootTime] + +link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[OS boot time comparison] URL: link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html] + +Contact: Colin Percival <cperciva@FreeBSD.org> + +Colin Percival is coordinating an effort to speed up the FreeBSD boot process. +For benchmarking purposes, he is primarily using an EC2 c5.xlarge instance as a +reference platform and is measuring the time between when the virtual machine +enters the EC2 "running" state and when it is possible to SSH into the instance. + +This work started in 2017, and as of the end of September 2021 the FreeBSD boot +time was reduced from approximately 30 seconds to approximately 15 seconds. + +During 2021Q4, further improvements have shaved more time off the boot process, +taking it down to roughly 10 seconds. A further 4 seconds of improvements are +in process. + +In addition, the userland boot process is now being profiled using TSLOG, +making it possible to see flamecharts of the entire boot process; and the +ec2-boot-bench tool is now able to generate MP4 videos of the boot process +by taking snapshots of the EC2 VGA console. + +Issues are listed on the wiki page as they are identified; the wiki page also +has instructions for performing profiling. Users are encouraged to profile +the boot process on their own systems, in case they experience delays which +don't show up on the system Colin is using for testing. + +This work is supported by Colin's FreeBSD/EC2 Patreon. + +Sponsor: https://www.patreon.com/cperciva diff --git a/website/content/en/status/report-2021-10-2021-12/doceng.adoc b/website/content/en/status/report-2021-10-2021-12/doceng.adoc new file mode 100644 index 0000000000..93abcd7c39 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/doceng.adoc @@ -0,0 +1,39 @@ +//// +Quarter: 4th quarter of 2021 +Prepared by: dbaio +Reviewed by: carlavilla, bcr +Last edit: $Date: 2022-01-05 20:07:39 -0300 (Wed, 05 Jan 2022) $ +Version: $Id: doceng-2021-4th-quarter-status-report.adoc 208 2022-01-05 23:07:39Z dbaio $ +//// + +=== Documentation Engineering Team + +Links: + +link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[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/[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[https://www.freebsd.org/administration/#t-doceng] + +Contact: FreeBSD Doceng Team <doceng@FreeBSD.org> + +The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. + +No new documentation commit bit was granted during the last quarter, and only one commit bit was safe kept. + +Several tasks were completed related to the doc tree during the last quarter: + +* A COPYRIGHT file was added in the root directory of the doc repository. The license was also updated to reflect the current toolchain the project is using now. + +* Cleanup of Mailman information in the doc tree. Following mailing lists migration from Mailman to Mlmmj, very old mailing lists were removed; most of the work was made on English documents. + +* Tag FreeBSD docset for 12.3-RELEASE. + +* Update all ports/packages misc/freebsd-doc-*. + +* Move articles/contributors/contrib-* files to the doc shared directory. + +* Add option in documentation Makefile to archive/compress Documentation/HTML offline files, a necessary step before updating https://download.freebsd.org/ftp/. This was after a discussion with clusteradm@ to update the offline assets (HTML/PDF). + +* Add experimental support for EPUB output (books/articles). + +* Talking with clusteradm@ to improve the performance of https://www.freebsd.org and https://docs.freebsd.org. + diff --git a/website/content/en/status/report-2021-10-2021-12/ena.adoc b/website/content/en/status/report-2021-10-2021-12/ena.adoc new file mode 100644 index 0000000000..4f2edefd50 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/ena.adoc @@ -0,0 +1,26 @@ +=== ENA FreeBSD Driver Update + +Links: + +link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README] + +Contact: Michal Krawczyk <mk@semihalf.com> + +Contact: Dawid Gorecki <dgr@semihalf.com> + +Contact: Marcin Wojtas <mw@semihalf.com> + +ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS). +The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used. + +Completed since the last update: + +* Add IPv6 layer 4 checksum offload support to the driver +* Add NUMA awareness to the driver when the RSS kernel option is enabled +* Rework validation of the Tx request ID +* Change lifetime of the driver's timer service +* Avoid reset triggering when the device is unresponsive + +Work in progress: + +* Prototype the driver port to the iflib framework +* Tests of the incoming ENA driver release (v2.5.0) + +Sponsor: Amazon.com Inc diff --git a/website/content/en/status/report-2021-10-2021-12/freebsd-foundation.adoc b/website/content/en/status/report-2021-10-2021-12/freebsd-foundation.adoc new file mode 100644 index 0000000000..59e48b6b46 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/freebsd-foundation.adoc @@ -0,0 +1,151 @@ +=== FreeBSD Foundation + +Links: + +link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] + +link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] + +link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] + +link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] + +link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] + +link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/] + + +Contact: Deb Goodkin <deb@FreeBSDFoundation.org> + +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to +supporting and promoting the FreeBSD Project and community worldwide. Donations +from individuals and corporations are used to fund and manage software +development projects, conferences, and developer summits. We also provide travel +grants to FreeBSD contributors, purchase and support hardware to improve and +maintain FreeBSD infrastructure, and provide resources to improve security, +quality assurance, and release engineering efforts. We publish marketing +material to promote, educate, and advocate for the FreeBSD Project, facilitate +collaboration between commercial vendors and FreeBSD developers, and finally, +represent the FreeBSD Project in executing contracts, license agreements, and +other legal arrangements that require a recognized legal entity. + +Here are some highlights of what we did to help FreeBSD last quarter: + +==== Fundraising Efforts + +We did it! We met our 2021 fundraising goal by raising $1,281,437!! On behalf +of the Foundation, I want to thank you for your financial support last year, +that will help us continue and increase our support for FreeBSD in 2022. In +addition, folks are already sending us their 2022 contributions, which is +incredibly heartwarming! We’ll start updating the fundraising meter for 2022 +by the end of January. + +In this Quarterly Status report you’ll read about many of the areas we funded +in Q4 to improve FreeBSD and advocate for the Project (the two main areas we +spend money on). Check out reports on the externally funded projects like LLDB +support, Raid-Z Expansion, WireGuard, and wifi, as well as, internally supported +work like improved security, tier-1 architecture support, and providing online +opportunities to connect and educate the community. + +If you want to help us continue our efforts, please consider making a donation +towards our 2022 fundraising campaign! https://www.FreeBSDFoundation.org/donate/. + +We also have a Partnership Program for larger commercial donors. You can read about +it at https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program/. + +==== OS Improvements + +During the fourth quarter, Foundation staff and grant recipients committed 472 +src tree changes, 98 ports tree changes, and 11 doc tree changes. This +represents 41%, 41%, and 13% of src, ports, and doc commits identifying a +sponsor. + +You can read about Foundation-sponsored projects in individual quarterly report +entries: + +- The AVX bug on amd64 +- Crypto changes for WireGurard +- Intel Wireless driver support +- LLDB Debugger Improvements +- Base System OpenSSH Update +- sched_getcpu(2), membarrier(2), and rseq(2) syscalls +- VDSO on amd64 + +Here is a small sample of other base system improvements from Foundation +developers this quarter that do not have separate report entries. + +===== kern.proc.pathname canonical hard link + +Some programs adjust their behavior depending on which name was used for +execution. For these programs, it is often important to have a consistent name +in argv[0], sysctl kern.proc.pathname, auxv AT_EXECPATH, and any procfs file +symlink. Before this work, all listed kernel interfaces tried to calculate some +name for the text vnode and returned the result. If the executed binary has +more than one hardlink, the returned names were arbitrarily chosen from the +list of valid names for the file. After work completed this quarter by Foundation +developer Konstantin Belousov, the system now holds the parent directory and the +name of the text file for the running image. This is used to reconstruct the +correct name of the text file when requested. + +===== swapon/swapoff, file swapping + +After work to fix asserts for character device vnode locking, there was a report +that swap on file code broke the VFS locking protocol. Some other regressions +in the swap on file were also identified. For instance, on shutdown, +filesystems were unmounted before swapoff, which makes swapoff panic on page-in. +These bugs were fixed and a link:https://www.freebsd.org/cgi/man.cgi?query=swapoff&apropos=0&sektion=2&manpath=FreeBSD+14.0-current&arch=default&format=html[swapoff(2)] feature was added to avoid some very +conservative estimations for protection against memory and swap space shortages. + +===== fcntl(F_KINFO) + +Application developers often request an interface to return the file path for an +open file descriptor. Our only useful facility for this was kern.proc.filedesc +sysctl, which is somewhat usable, but incurs too high of an overhead when a +process has many open files. A fcntl(F_KINFO) interface was added, which returns +a struct kinfo_file just for the specified file descriptor. Among other useful +data, kinfo_file provides the calculated path, when available. + +==== Continuous Integration and Quality Assurance + +The Foundation provides a full-time staff member and funds projects to improve +continuous integration, automated testing, and overall quality assurance efforts +for the FreeBSD project. + +==== Supporting FreeBSD Infrastructure + +The Foundation provides hardware and support for the Project. In the fourth +quarter of 2021, we began searching for a new Australian mirror server. At the +time of writing, the server is purchased, but with delays obtaining components +and shipping, it may not be active until the second or third quarter of 2022. +Better and faster access to our sites for the Australian FreeBSD community is +coming. + +==== FreeBSD Advocacy and Education + +Much of our effort is dedicated to Project advocacy. This may involve highlighting interesting FreeBSD work, producing literature, attending events, or giving presentations. The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. + +The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups. We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. This all helps provide a healthy ecosystem. We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. We are continuing to attend virtual events and held a virtual vendor summit this past November. + +Check out some of the advocacy and education work we did last quarter: + +* Promoted and participated as a media sponsor for link:https://2021.allthingsopen.org/[ALL Things Open 2021] +* Committed to being a Media Sponsor for link:https://www.socallinuxexpo.org/scale/19x[SCALE 19x] +* Committed to hosting a link:https://stands.fosdem.org/stands/freebsd_project/[stand at FOSDEM 2022] +* Sent out the link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-fall-2021-update/[Fall 2021 Newsletter] +* Held a link:https://www.youtube.com/watch?v=BYTNpuinaPU[FreeBSD Friday talk: The Writing Scholar's Guide to FreeBSD], (link:https://www.coreystephan.com/freebsd-friday/[text equivalent]) +* Gave a Foundation talk at link:http://www.semibug.org/[Semi-Bug], November 16, 2021 +* Gave Foundation and FreeBSD talks at Seagate OSPO, December 9, 2021 +* Helped organize the 2 day link:https://wiki.freebsd.org/DevSummit/202111[FreeBSD Virtual Vendor Summit, November 18-19, 2021]. Videos can be found on the link:https://www.youtube.com/c/FreeBSDProject/videos[Project’s Youtube Channel] +* New blog and video posts: +** link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-fall-2021-update/[FreeBSD Foundation Fall 2021 Update] +** link:https://freebsdfoundation.org/blog/2021-in-review-advocacy/[2021 in Review: Advocacy] +** link:https://freebsdfoundation.org/blog/2021-in-review-infrastructure-support/[2021 in Review: Infrastructure Support] +** link:https://freebsdfoundation.org/blog/2021-in-review-software-development/[2021 in Review: Software Development] +** link:https://freebsdfoundation.org/blog/open-source-summit-2021-conference-recap/[Open Source Summit 2021 Conference Recap] +* New How-To Guide: link:https://freebsdfoundation.org/freebsd-project/resources/freebsd-introduction/[Introduction to FreeBSD] + +We help educate the world about FreeBSD by publishing the professionally produced link:https://freebsdfoundation.org/our-work/journal/[FreeBSD Journal]. As we mentioned previously, the FreeBSD Journal is now a free publication. Find out more and access the latest issues at https://www.FreeBSDfoundation.org/journal/. + +You can find out more about events we attended and upcoming events at https://www.FreeBSDfoundation.org/news-and-events/. + +==== 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://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] +to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2021-10-2021-12/hellosystem.adoc b/website/content/en/status/report-2021-10-2021-12/hellosystem.adoc new file mode 100644 index 0000000000..514ec958d6 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/hellosystem.adoc @@ -0,0 +1,27 @@ +=== helloSystem + +Links: + +link:https://hellosystem.github.io/docs/[Documentation] URL: link:https://hellosystem.github.io/[https://hellosystem.github.io/] + +Contact: Simon Peter <probono@puredarwin.org> + +Contact: `\#helloSystem` on `irc.libera.chat`, mirrored to link:https://matrix.to/#/%23helloSystem:matrix.org?via=matrix.org[`#helloSystem:matrix.org` on Matrix] + +==== What is helloSystem? + +helloSystem is FreeBSD preconfigured as a desktop operating system with a focus on simplicity, elegance, and usability. +Its design follows the “Less, but better” philosophy. + +==== Q4 2021 Status + +* Version 0.7.0 of helloSystem has been published including many contributed features and bugfixes +** helloSystem is now based on FreeBSD 13.0-RELEASE +** Completely reworked Live ISO architecture, resulting in 1/3rd boot time and under 800 MB size (fits a CD-ROM) +** Developer Tools are now a separate download +** Disk Images are increasingly used throughout the system, such as for application distribution and Linuxulator userland deployment +** Many new features and GUI utilities to make the desktop more usable for "mere mortals" without the need for a terminal + +Installable Live ISO images and a full changelog are available at https://github.com/helloSystem/ISO/releases/tag/r0.7.0 + +==== Contributing + +link:https://github.com/helloSystem/hello/blob/master/CONTRIBUTING.md[The project appreciates contributions in various areas]. diff --git a/website/content/en/status/report-2021-10-2021-12/iwlwifi.adoc b/website/content/en/status/report-2021-10-2021-12/iwlwifi.adoc new file mode 100644 index 0000000000..7f3bcb6126 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/iwlwifi.adoc @@ -0,0 +1,23 @@ +=== Intel Wireless driver support + +Links: + +link:https://wiki.freebsd.org/WiFi/Iwlwifi[iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi] + +Contact: Bjoern A. Zeeb <bz@FreeBSD.ORG> + +The Intel Wireless driver update project aims to bring support for newer chipsets along with mac80211 LinuxKPI compat code. +The dual-licensed Intel driver code was ported in the past for the iwm(4) native driver; using the LinuxKPI compat framework allows us to use the driver directly, with only very minor modifications that we hope will be incorporated into the original driver. + +During December the driver, firmware, and all remaining LinuxKPI compatibility code were committed to FreeBSD main (HEAD) and merged to the stable/13 branch. +Further fixes, updates, and improvements will go directly into FreeBSD, meaning the need to apply snapshots is gone and changes can be distributed more timely. + +During the last months we tried to ensure that the latest AX210 chipsets are supported. +The compat code was restructured both to be able to better trace and debug the mac80211 compatibility layer, but also to keep the net80211 and mac80211 state machines for stations better in sync. + +While we keep updating the driver and all the compat code needed for that, the focus remains on stability and adding support for newer 802.11 standards. +The driver is still set to 11a/b/g-only and 11n will be next before we look at 11ac. + +With the code in FreeBSD git we anticipate broader testing and with that also some fallout. +For the latest state of the development, please follow the referenced wiki page and the freebsd-wireless mailing list. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2021-10-2021-12/kde.adoc b/website/content/en/status/report-2021-10-2021-12/kde.adoc new file mode 100644 index 0000000000..fdcfa405af --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/kde.adoc @@ -0,0 +1,38 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] + +link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project aims to package the software from the KDE Community, along with dependencies and related software, for the FreeBSD ports tree. +That includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The KDE team (kde@) is part of desktop@ and x11@ as well, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine. + + +* Just two CMake updates this quarter, ending up with CMake 3.22.1. Some more patches have landed upstream, and CMake is soon to switch to `share/man` for manpages on FreeBSD. When it does, there will be plenty of `pkg-plist` churn. +* Monthly releases of KDE Frameworks, KDE Plasma, and KDE Gear kept the exp-runs going. kde@ would like to thank Antoine for overseeing our many exp-run requests. We are now at KDE Frameworks 5.89 (latest release as of December 2021), link:https://kde.org/announcements/plasma/5/5.23.4/[KDE Plasma Desktop 5.23.4] and link:https://kde.org/announcements/gear/21.12.0/[KDE Gear 21.12]. +* Qt 5 is not receiving any open source updates from the Qt Company, but the KDE Community maintains its own set of patches that backport many fixes from Qt 6. Work is underway to import the KDE patch collection. +* Qt 6 remains tantalizingly close. There hasn't been real progress on the crash-on-exit problem, though. +* *deskutils/kalendar* is a relatively new port that uses KDE technologies for a desktop (appointments) calendar. +* *deskutils/latte-dock*, an alternative launcher for KDE Plasma (and other environments) was updated to each of its bugfix releases. +* *devel/qbs* and *devel/qtcreator* were updated. Qbs (or "Qt Build System") is a declarative build system styled along the lines of declarative QML programs. (Note that Qbs is not used by Qt itself). +* *graphics/digikam* was updated to the latest release and now supports both ImageMagick 6 and ImageMagick 7. Speaking of which, a new `USES=magick` was introduced to simplify ports that depend in ImageMagick. +* *graphics/ksnip*, one of several screenshot-applications for KDE Plasma (and other environments) had a lots-of-bugfixes update. +* *graphics/skanpage* is a new port that scans multiple pages and produces a PDF of the whole. +* *multimedia/qt5-multimedia* now ignores gstreamer-gl (rather than implicitly building with it as a dependency if it is installed a build time). +* *net-im/ruqola* is a Rocket Chat client, updated to the latest release. +* *security/qtkeychain* has a new release. + +Elsewhere in the software stack, kde@ also maintains ports that support the desktop in general. Some highlights are: + +* *devel/libphonenumber* keeps chasing changes to the world's phone numbers (the FreeBSD foundation can be reached at +1.720.207.5142). +* *graphics/poppler* updated this much-used PDF-rendering library. +* *multimedia/pipewire*, the audio-and-video successor to pulseaudio, was updated and now supports SSL as well. +* *net/py-pytradfri* got several updates so you can control your lights from FreeBSD. +* *print/freetype2* was updated to the latest release; relatedly, there was am update to *x11-toolkits/libXft*. +* *print/harfbuzz*, the text-shaping library, was updated for more font type support. +* *sysutils/bsdisks* is an implementation of DBus interfaces for examining disks (drives, partitions, etc.). It is also used for removable-disk notifications. +* *x11-themes/adwaita-qt*, which connects the adwaita theme engine to Qt-based applications, was updated. diff --git a/website/content/en/status/report-2021-10-2021-12/lldb.adoc b/website/content/en/status/report-2021-10-2021-12/lldb.adoc new file mode 100644 index 0000000000..6ed5b3d60b --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/lldb.adoc @@ -0,0 +1,40 @@ +=== LLDB Debugger Improvements + +Links: + +link:https://www.moritz.systems/blog/freebsd-kgdb-support-in-lldb/[Moritz Systems Project Description] URL: link:https://www.moritz.systems/blog/freebsd-kgdb-support-in-lldb/[https://www.moritz.systems/blog/freebsd-kgdb-support-in-lldb/] + +link:https://www.moritz.systems/blog/lldb-serial-port-communication-support/[Progress Report 3] URL: link:https://www.moritz.systems/blog/lldb-serial-port-communication-support/[https://www.moritz.systems/blog/lldb-serial-port-communication-support/] + +link:https://www.moritz.systems/blog/lldb-freebsd-kernel-core-dump-support/[Progress Report 4] URL: link:https://www.moritz.systems/blog/lldb-freebsd-kernel-core-dump-support/[https://www.moritz.systems/blog/lldb-freebsd-kernel-core-dump-support/] + +link:https://github.com/moritz-systems/llvm-project[LLVM Git Repository] URL: link:https://github.com/moritz-systems/llvm-project[https://github.com/moritz-systems/llvm-project] + +link:https://github.com/moritz-systems/libfbsdvmcore[libfbsdvmcore Git Repository] URL: link:https://github.com/moritz-systems/libfbsdvmcore[https://github.com/moritz-systems/libfbsdvmcore] + +Contact: Kamil Rytarowski <kamil@moritz.systems> + +Contact: Michał Górny <mgorny@moritz.systems> + +According to the upstream description, "LLDB is a next generation, +high-performance debugger. It is built as a set of reusable components which +highly leverage existing libraries in the larger LLVM Project, such as the +Clang expression parser and LLVM disassembler." + +FreeBSD includes LLDB in the base system. At present, it has some limitations +compared to the GNU GDB debugger, and does not yet provide a complete +replacement. This project spans from July 2021 to January 2022 and aims to +make LLDB suitable for debugging FreeBSD kernels. + +The earlier part of the project was focused on improving compatibility between +LLDB and other servers implementing the GDB Remote Protocol. This was followed +by implementing a fully-featured serial port support and then support +for FreeBSD kernel core dumps (vmcores). + +The LLDB client gained much improved support for connecting to the remote +server over a serial port, and the LLDB server gained support for accepting +communication over a serial port. This opened the possibility of using LLDB +to debug embedded devices that use the RS232 interface. It can also aid +debugging kernels on regular PCs as it does not rely on the network stack. + +Support for FreeBSD vmcores has also been added to LLDB. This makes it +possible to inspect the crashed kernel state without having to resort to KGDB +or manually convert the vmcore into the standard ELF format supported by LLDB. + +The introduced changes are expected to be shipped with LLDB 14.0. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2021-10-2021-12/ls1027a.adoc b/website/content/en/status/report-2021-10-2021-12/ls1027a.adoc new file mode 100644 index 0000000000..a1c60beb94 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/ls1027a.adoc @@ -0,0 +1,35 @@ +=== NXP LS1028A/1027A SoC support + +Contact: Kornel Dulęba <mindal@semihalf.com> + +Contact: Artur Rojek <ar@semihalf.com> + +Contact: Hubert Mazur <hum@semihalf.com> + +Contact: Wojciech Macek <wma@semihalf.com> + +The Semihalf team has been working on adding the FreeBSD support for the link:https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-processors/layerscape-1028a-applications-processor:LS1028A[NXP LS1028A] SoC, as well as its GPU-less variant (NXP LS1027A). + +NXP LS1028A/LS1027A SoC is a dual-core 64-bit ARMv8 Cortex-A72 application processor with high-speed peripherals such as 2 Time-Sensitive Networking-capable (TSN) Ethernet controllers, quad-port TSN-enabled switch, PCIE, SD/MMC, USB3.0 and others. + +The original support was extended in the following way: + +* ENETC Ethernet link:https://cgit.freebsd.org/src/log/sys/dev/enetc[driver] +** Add support for PHY interrupts +** Fix VID/mcast address hash calculation +** Serialize MDIO transactions +** Allow loading driver as a module +* Improvements in the link:https://cgit.freebsd.org/src/log/sys/dev/sdhci/sdhci_fsl_fdt.c[FSL SDHCI driver] +** Add support for HS200/HS400 modes +** Add full support for software reset +** Provide more accurate clk calculation +** Implement pulse width detection errata +** Fix vccq reconfiguration +* FLEX SPI NOR controller link:https://cgit.freebsd.org/src/log/sys/dev/flash/flexspi/flex_spi.c[driver] +* Additional features: +** TMP461 thermal sensor link:https://cgit.freebsd.org/src/log/sys/dev/iicbus/tmp461.c[driver] +** PCF85063 RTC driver link:https://cgit.freebsd.org/src/log/sys/dev/iicbus/rtc/pcf85063.c[driver] +** TCA6408 I2C GPIO expander link:https://cgit.freebsd.org/src/log/sys/dev/iicbus/gpio/tca6408.c[driver] + +TODO: + +* Improve MMC HS200/HS400 support for other SoCs using the FSL SDHCI controller. + +Sponsor: Alstom Group diff --git a/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc b/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc new file mode 100644 index 0000000000..814598c6aa --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/membarrier-rseq.adoc @@ -0,0 +1,103 @@ +=== sched_getcpu(2), membarrier(2), and rseq(2) syscalls + +Contact: Konstantin Belousov <kib@FreeBSD.org> + +Links: + +link:https://kib.kiev.ua/kib/membarrier.pdf[Linux manpage for membarrier(2)] URL: link:https://kib.kiev.ua/kib/membarrier.pdf[https://kib.kiev.ua/kib/membarrier.pdf] + +link:https://reviews.freebsd.org/D32360[membarrier(2) implementation] URL: link:https://reviews.freebsd.org/D32360[https://reviews.freebsd.org/D32360] + +link:https://kib.kiev.ua/kib/rseq.pdf[Linux manpage for rseq(2)] URL: link:https://kib.kiev.ua/kib/rseq.pdf[https://kib.kiev.ua/kib/rseq.pdf] + +link:https://reviews.freebsd.org/D32505[rseq(2) and userspace bindings implementation] URL: link:https://reviews.freebsd.org/D32505[https://reviews.freebsd.org/D32505] + +Linux provides a set of syscalls that allow to develop mostly +syscall-less scalable algorithms in userspace. The mechanisms are +based on optimistic execution using CPU-local data with the assumption that +rare events like context switches or signal delivery do not occur +for the given calculation, and if they do occur, rollback and restart +is performed. This very high-level approach is used, as I understand, +for implementation of tools like URCU, fast malloc allocators +(tcmalloc) and other userspace infrastructure projects aimed at +large partitioned machines. + +For instance, sched_getcpu(2) syscall returns the CPU id of the CPU +where the current thread is currently executing. On amd64, if +available, we use a RDTSCP or RDPID instruction to query the CPU id without +changing CPU mode, otherwise this is a light-weight syscall. Of +course, the answer provided is obsolete the moment it is created, +even before it is returned to userspace. But it allows seeding values +in some structures that are valid for a long time (at the +CPU speed scale) and are automatically corrected on exceptional +control flow events like context switches, and userspace can either detect +and rollback or sync and rollback with the exceptions. + +There are two cornerstone syscalls that allow userspace to implement +these efficient algorithms: membarrier(2) and rseq(2). + +Membarrier is a facility that helps implementing fast CPU ordering +barriers, typically used for asymmetric/biased locking. In these lock +implementation schemes, the owner of the object often assumes that there +are contenders/parallel threads that need coordinating with. If some +thread starts accessing the same resource, then it is its duty to +ensure correctness. Examples of 'traps' that fast code path +utilize are reads from a dedicated page that is unmapped by contenders, +to switch the fast path to the slow one. Or we could send a signal to all +threads that potentially have access to that object, to insert a +barrier. Or we can use the membarrier(2) facility, which incurs +significantly less overhead than signalling all threads. + +Membarrier(2) inserts a barrier, which is the typical underlying +hardware operation to ensure ordering, into the specified set of CPUs, +if these CPUs are executing the specified thread. If these CPUs are not executing +the targeted threads, it is assumed that sequential consistency guarantees +from the context switch are enough to fulfill the requirement of +membarrier(2). Overall, the fast path can be implemented without slow +instructions, and the slow path injects required fences into the fast path at +the cost of IPI. + +The facility to detect exceptional conditions in the userspace thread +execution was developed in Linux and called rseq(2). It is a feature +often called Restartable Atomic Sequences, which explains the acronym. +The ability to cheaply do that allows code longer than a single +instruction to execute atomically, without the need to propose and +implement unsafe operations like disabling preemption, which is not +feasible for userspace. For instance, code might use CPU-local +resources, which otherwise does not cope well with context switches. +There cannot be an analog of critical_enter(9) in userspace. (A +facility to cheaply block signal delivery exists in FreeBSD, see +sigfastblock(2), but correctly using it is provably too hard to +implement in general-purpose code, esp. because it requires +version-dependent coordination with rtdl and libthr.) + +rseq(2) takes per-thread block of memory, where the thread writes the +current CPU id (see sched_getcpu(2)) and specifies the block of +critical code that must be unwound if an exceptional situation like a +context switch occurred while the block was executing. The fast code +path uses per-cpu data and typically does not need any corrections, +but would a context switch occur, transfer of control to the abort +handler informs userspace about the event. So instead of disabling +context switches, code can cheaply check for one after the calculation +and retry if needed. + +An interesting rseq(2) implementation detail is that it is +impossible (and not needed) to access/update rseq structures from +kernel during the actual context switch, because we cannot access +userspace from under a spinlock. In other words, +threads using rseq do not incur any performance cost from +system-global context switches. Instead, if the process registered for +rseq(2), on any return to user mode we check if any exceptional +events happened while the thread was in the kernel (context switches may happen +only while the thread is in kernel mode), and if a context switch indeed +occurred, we fire an ast to check whether the program counter is inside the +critical section and jump to the abort handler if it is. + +The implementations of membarrier(2) and rseq(2) are clean-room: I used +Linux manual pages as the reference and public discussions of the +features for clarifying corner cases. On Linux/glibc, there was no +stable glibc interface to the rseq facility. One proposed integration was +committed then reverted from glibc. It might be prudent to wait +some more for the rseq(2) interface to stabilize in glibc before providing +it in our libc or to rely on tight integration between kernel +and userspace in our base system, and use ABI tricks like symbol +versioning to evolve the interface. There is no goal to be 100% +compatible with Linux anyway. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2021-10-2021-12/ocf-wg.adoc b/website/content/en/status/report-2021-10-2021-12/ocf-wg.adoc new file mode 100644 index 0000000000..bad8fe033d --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/ocf-wg.adoc @@ -0,0 +1,20 @@ +=== Kernel Crypto changes to support WireGuard + +Contact: John Baldwin <jhb@FreeBSD.org> + +During the past few months, I merged several changes to the kernel to better +support the WireGuard driver. These include extensions to the 'struct +enc_xform' interface to better support AEAD ciphers, changes to 'struct +enc_xform' to support multi-block operations for improved performance, and the +addition of the XChaCha20-Poly1305 AEAD cipher suite to OCF. Additionally, the +kernel now includes a new "direct" API for ChaCha20-Poly1305 operations on +small, flat buffers. A change in review adds an API to support curve25519 +operations. With these changes, the WireGuard driver is mostly able to use +crypto APIs from the kernel rather than its internal implementations. + +In parallel I have been updating the WireGuard driver to use the new +APIs verifying interoperability with the existing driver. One of the +next tasks is to refine these changes (along with some minor bug +fixes) as candidates for upstreaming into the WireGuard driver. + +Sponsor: The FreeBSD Foundation
\ No newline at end of file diff --git a/website/content/en/status/report-2021-10-2021-12/office.adoc b/website/content/en/status/report-2021-10-2021-12/office.adoc new file mode 100644 index 0000000000..9d28d0bcf7 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/office.adoc @@ -0,0 +1,26 @@ +=== FreeBSD Office Team + +Links: + +link:https://wiki.freebsd.org/Office[The FreeBSD Office project] URL: link:https://wiki.freebsd.org/Office[https://wiki.freebsd.org/Office] + +Contact: FreeBSD Office team ML <office@FreeBSD.org> + +Contact: Dima Panov <fluffy@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +The FreeBSD Office team works on a number of office-related software suites and tools such as OpenOffice and LibreOffice. + +Work during this quarter was focused on providing the latest stable release of LibreOffice suite and companion apps to all FreeBSD users. + +Latest and quarterly ports branches got a new branch (7.2) of the LibreOffice suite and updated to the 7.2.4 release while new preleases +such as 7.2.5.RC2 and 7.3.0.RC1 are cooking in the WIP stage area. + +Meanwhile, our link:https://github.org/freebsd/freebsd-ports-libreoffice[WIP repository] got back a working CI instance again, thanks to Li-Wen Hsu. + +Also we are still working on the link:https://github.com/fluffykhv/freebsd-ports-boost[Boost WIP repository] to bring the latest Boost library to the ports. + +We are looking for people to help with the open tasks: + +* The link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=office%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailreporter1=1&emailtype1=substring&query_format=advanced&list_id=374316[open bugs list] contains all filed issues which need some attention +* Upstream local patches in ports + +Patches, comments and objections are always welcome in the mailing list and bugzilla. diff --git a/website/content/en/status/report-2021-10-2021-12/openssh.adoc b/website/content/en/status/report-2021-10-2021-12/openssh.adoc new file mode 100644 index 0000000000..36bebd2fb9 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/openssh.adoc @@ -0,0 +1,25 @@ +=== Base System OpenSSH Update + +Links: + +link:https://www.openssh.com/[OpenSSH] URL: link:https://www.openssh.com/[https://www.openssh.com/] + +link:https://lists.freebsd.org/pipermail/freebsd-security/2021-September/010473.html[Announcement to freebsd-security@] URL: link:https://lists.freebsd.org/pipermail/freebsd-security/2021-September/010473.html[https://lists.freebsd.org/pipermail/freebsd-security/2021-September/010473.html] + +Contact: Ed Maste <emaste@freebsd.org> + +OpenSSH, a suite of remote login and file transfer tools, was updated from +version 8.7p1 to 8.8p1 in the FreeBSD base system. + +*NOTE*: +OpenSSH 8.8p1 disables the ssh-rsa signature scheme by default. +For more information please see the +link:https://lists.freebsd.org/pipermail/freebsd-security/2021-September/010473.html[Important +note for future FreeBSD base system OpenSSH update] mailing list post. + +OpenSSH supports +link:https://en.wikipedia.org/wiki/FIDO2_Project[FIDO]/link:https://en.wikipedia.org/wiki/Universal_2nd_Factor[U2F] +devices, and support is now enabled in the base system. + +Next steps include integrating U2F key devd rules into the base system, +and merging the updated OpenSSH and FIDO/U2F support to stable branches. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2021-10-2021-12/portmgr.adoc b/website/content/en/status/report-2021-10-2021-12/portmgr.adoc new file mode 100644 index 0000000000..d59e709bd1 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/portmgr.adoc @@ -0,0 +1,36 @@ +=== Ports Collection + +Links: + +link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL: link:https://www.FreeBSD.org/ports/[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[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] + +link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] + +link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[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/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/] + +Contact: René Ladan <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +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. + +We currently have 46,700 ports in the Ports Collection according to FreshPorts. +There are currently 2,666 open ports PRs of which 611 are unassigned. +This quarter saw 9,535 commits from 166 committers on the main branch and 644 commits from 62 committers on the quarterly branch. +Compared to last quarter, this means a slight drop in the number of commits although more committers were active, and a slight increase in the number of open PRs. + +During the last quarter, we welcomed Dries Michiels (driesm@) and said goodbye to kuriyama@ and fjoe@. +There was also a change in portmgr: adamw@ stepped down after five years of service and tcberner@ is now a full member of portmgr@. + +Three new USES were introduced: + +* magick to handle dependencies on ImageMagick + +* nodejs to provide support for NodeJS (with a new default version NODEJS=lts) + +* trigger to handle pkg triggers using the TRIGGERS variable + +The default version of PGSQL switched to 13. +Furthermore, INSTALLS_ICONS has been replaced by a trigger on gtk-update-icon-cache and the macro is no longer functional. + +As always, there were some updates to "big" packages: pkg was updated to 1.17.5, Chromium to 94.0.4606.81_3, and Firefox to 95.0.2_1,2. +Ruby 3.1.0 and Python 3.11 are now available for use by users and other ports. diff --git a/website/content/en/status/report-2021-10-2021-12/pot.adoc b/website/content/en/status/report-2021-10-2021-12/pot.adoc new file mode 100644 index 0000000000..aee15c4a5a --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/pot.adoc @@ -0,0 +1,28 @@ +=== Containers & FreeBSD: Pot, Potluck & Potman + +Links: + +link:https://pot.pizzamig.dev[Pot on github] URL: link:https://github.com/pizzamig/pot[https://github.com/pizzamig/pot] + +link:https://potluck.honeyguide.net/[Potluck Repository & Project] URL: link:https://potluck.honeyguide.net/[https://potluck.honeyguide.net/] + +link:https://github.com/hny-gd/potluck[Potluck on github] URL: link:https://github.com/hny-gd/potluck[https://github.com/hny-gd/potluck] + +link:https://github.com/grembo/potman[Potman on github] URL: link:https://github.com/grembo/potman[https://github.com/grembo/potman] + +Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> + +Contact: Stephan Lichtenauer (Potluck) <sl@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org> + +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]. + +In the last quarter, a new release link:https://github.com/pizzamig/pot/releases/tag/0.14.0[0.14.0] with a number of fixes and features like the new copy-in-flv command was made available. + +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. + +Here we again had a busy quarter. All images have been rebuilt for FreeBSD 12.3 and pot 0.13.0. + +Also the images that can be used to build a virtual data center like link:https://potluck.honeyguide.net/blog/nomad-server/[Nomad], link:https://potluck.honeyguide.net/blog/consul/[Consul] and link:https://potluck.honeyguide.net/blog/vault/[Vault] have received a lot more tender love and care and are meanwhile in pre-production use on a cluster at a fintech. + +Not all these changes have yet been committed to the github repository though, this is planned for the next quarter. +Additionally, new images like link:https://github.com/hny-gd/potluck/tree/master/openldap[multi-master OpenLDAP] have been added, too. + +Potman aims to simplify building Pot images with Vagrant and VirtualBox based on the Potluck approach, e.g. as part of a DevOps workflow for software development including testing and publishing them to a repository. + +Here we have not yet made a lot of headway with our plan to utilise Potman in the Potluck library build process but this is still on our TODO-list, like improving the documentation for using the Virtual DC images from the Potluck library. + +As always, feedback and patches are welcome. diff --git a/website/content/en/status/report-2021-10-2021-12/vdso.adoc b/website/content/en/status/report-2021-10-2021-12/vdso.adoc new file mode 100644 index 0000000000..5768a65ec6 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/vdso.adoc @@ -0,0 +1,82 @@ +=== VDSO on amd64 + +Contact: Konstantin Belousov <kib@FreeBSD.org> + +A VDSO, or Virtual Dynamic Shared Object, is a shared object (more +commonly called dynamic library) that is inserted into the executed +image by a joint effort of the kernel and the dynamic linker. It does +not exists on disk as a standalone .so, and there are no instructions +in the ELF format that cause the insertion. It is done by the system +to implement some functionality for the C runtime implementation +components. + +FreeBSD already has a lot of features typically done using VDSO (in +Linux), but really not requiring that complication. The main reason +why it is possible is the often mentioned co-evolution of the kernel +and C runtime. We can naturally introduce features that require +implementation both in kernel, and support in the userspace parts, +since FreeBSD is developed as a whole. Surprisingly, it also allows +the kernel and dynamic linker to know much less (and not enforce +anything) about userspace consumers of interfaces. + +For instance, a syscall-less wall clock was implemented long ago, by +the kernel providing a time hands blob in the shared page, and the C +library knowing about its location and the supported algorithms. +There is no need for a VDSO that interposes some libc symbols or +provides services that are named by known symbols to userland. + +From all the years of experience with this pseudo-VDSO approach, the +only feature that was impossible to implement without providing real +VDSO support was the signal trampoline DWARF annotations, for the +benefit of stack unwinders. + +When the kernel delivers signal to userland, it changes some key +registers (like the instruction pointer, the stack pointer, and +whatever else is needed by the architecture) and pushes the saved +image of the whole usermode CPU state (context) onto the user stack. +Then, control is passed to a small piece of code located in the shared +page (signal trampoline), which calls the user handler function and on +return from the handler issues a sigreturn(2) syscall to reload the +old context. + +From this description, it is clear that the state of the machine +during trampoline execution is quite different from the normal C +calling frames. Unwinders that handle things like C++ exceptions, +Rust panics, or other similar mechanisms in specific language +runtimes, need to understand the specialness of the trampoline frame. +The current approach is to hardcode the detection of the trampoline, +e.g. by matching the instruction pointer against sysctl +kern.proc.sigtramp. + +DWARF annotations are enough to provide the required information to +unwinders to make the trampoline frame not special anymore, but the +problem is that there is no way for unwinders to find the annotation +without introducing even more specialness. Instead, we can insert a +VDSO that only serves to appear in the enumeration of DSOs loaded into +the process, with either dl_iterate_phdr(3) (in-process) or r_debug +(remote), with PT_GNU_EH_FRAME header pointing to the root of DWARF +info. + +This is exactly what the VDSO on FreeBSD does: it wraps signal +trampoline bits and their DWARF annotation (.cfi) into a shared +object, which is put into the shared page and linked by rtld(1) into +the set of preloaded objects upon image activation. + +Efforts were made to strip as many unneeded structures and as much +padding as possible from the VDSO image, because it consumes space in +the shared page. It was pushed as far as the common denominator of +lld and ld.bfd allowed, with several tricks done by linker scripts and +some use of seemingly undocumented linker options. + +We need at least two VDSOs for amd64: a 64-bit one for native binaries +and a 32-bit one for ia32 binaries. With the size of each VDSO around +1.5KB, space becomes really tight in the shared page, which needs +space for other stuff as well, like timehands or random generator +seeds. + +Build scripts enforce that VDSOs do not grow larger than 2K; if they +do, we need to extend shared page to become at least two shared pages. +Scripts also enforce that VDSO are pure position-independent, not +requiring relocations for either code or metadata (.cfi). + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2021-10-2021-12/www.adoc b/website/content/en/status/report-2021-10-2021-12/www.adoc new file mode 100644 index 0000000000..fb99dd5279 --- /dev/null +++ b/website/content/en/status/report-2021-10-2021-12/www.adoc @@ -0,0 +1,25 @@ +=== FreeBSD Website Revamp - WebApps working group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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 will be divided into four phases: + +. Redesign of the Documentation Portal ++ +Create a new design, responsive and with global search. (_Complete_) ++ +Activate an edit link in the Documentation (books/articles) pointing to GitHub and encouraging GitHub pull requests. (_Complete_) + +. Redesign of the Manual Pages on web ++ +Scripts to generate the HTML pages using mandoc. (_Work in progress_) + +. 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. (_Not started_) diff --git a/website/content/en/status/report-2022-01-2022-03/_index.adoc b/website/content/en/status/report-2022-01-2022-03/_index.adoc new file mode 100644 index 0000000000..31ad7d85e7 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/_index.adoc @@ -0,0 +1,152 @@ +--- +title: "FreeBSD Quarterly Status Report First Quarter 2022" +sidenav: about +--- + += Introduction +:doctype: article +:toc: macro +:toclevels: 2 +:icons: font +:!sectnums: +:source-highlighter: rouge +:experimental: +:reports-path: content/en/status/report-2022-01-2022-03 + +include::{reports-path}/intro.adoc[] + +''' + +toc::[] + +''' + +[[FreeBSD-Team-Reports]] +== FreeBSD Team Reports + +Entries from the various official and semi-official teams, as found in the +link:../../administration/[Administration Page]. + +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 that span multiple categories, from the kernel and userspace to the +Ports Collection or external projects. + +include::{reports-path}/accessibility.adoc[] + +''' + +include::{reports-path}/boot-performance.adoc[] + +''' + +[[kernel]] +== Kernel + +Updates to kernel subsystems/features, driver support, filesystems, and more. + +include::{reports-path}/ena.adoc[] + +''' + +include::{reports-path}/gunion.adoc[] + +''' + +include::{reports-path}/rtw88.adoc[] + +''' + +include::{reports-path}/iwlwifi.adoc[] + +''' + +include::{reports-path}/ocf-wg.adoc[] + +''' + +[[architectures]] +== Architectures + +Updating platform-specific features and bringing in support for the new hardware +platform. + +include::{reports-path}/dpaa2.adoc[] + +''' + +[[documentation]] +== Documentation + +Noteworthy changes in the documentation tree, man-pages, or new external +books/documents. + +include::{reports-path}/doceng.adoc[] + +''' + +[[ports]] +== Ports + +Changes affecting the Ports Collection, whether sweeping changes that touch most +of the tree, or individual ports themselves. + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/office.adoc[] + +''' + +include::{reports-path}/gcc.adoc[] + +''' + +include::{reports-path}/portconfig.adoc[] + +''' + +include::{reports-path}/wifibox.adoc[] + +''' + +[[third-Party-Projects]] +== Third Party Projects + +Many projects build upon FreeBSD or incorporate components of FreeBSD into their +project. As these projects may be of interest to the broader FreeBSD community, +we sometimes include brief updates submitted by these projects in our quarterly +report. The FreeBSD project makes no representation as to the accuracy or +veracity of any claims in these submissions. + +include::{reports-path}/hellosystem.adoc[] + +''' + +include::{reports-path}/pot.adoc[] + +''' + +include::{reports-path}/fpart.adoc[] diff --git a/website/content/en/status/report-2022-01-2022-03/accessibility.adoc b/website/content/en/status/report-2022-01-2022-03/accessibility.adoc new file mode 100644 index 0000000000..f30384fed2 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/accessibility.adoc @@ -0,0 +1,20 @@ +=== FreeBSD Accessibility + +Links: + +link:https://wiki.freebsd.org/Accessibility[Accessibility wiki page] URL: link:https://wiki.freebsd.org/Accessibility[https://wiki.freebsd.org/Accessibility] + +link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[List introduction, goals, audience, and ground rules] URL: link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html[link:https://lists.freebsd.org/archives/freebsd-accessibility/2021-October/000000.html] + +Contact: Pau Amma <pauamma@gundo.com> + +Contact: FreeBSD accessibility discussions <freebsd-accessibility@freebsd.org> + +Over the past several months, I've started putting together tools and resources to help make the FreeBSD ecosystem (more) accessible to people with disabilities: + +* a link:https://lists.freebsd.org/subscription/freebsd-accessibility[mailing list] +* a link:https://wiki.freebsd.org/Accessibility[set of wiki pages] including link:https://wiki.freebsd.org/Accessibility/Resources[resources] and a link:https://wiki.freebsd.org/Accessibility/Wishlist[categorized wish list] +* tooling including a link:https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=accessibility&list_id=471790&resolution=---[searchable accessibility Bugzilla keyword] and an link:https://reviews.freebsd.org/project/profile/87/[accessibility Phabricator group] + +I need all the help I can get with: + +* specifying, designing, implementing, and testing the items on the wishlist +* adding to the wishlist in areas were have little or no experience or for things I missed +* moving beyond software and documentation to processes and culture diff --git a/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc b/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc new file mode 100644 index 0000000000..cb159b69f6 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/boot-performance.adoc @@ -0,0 +1,28 @@ +=== Boot Performance Improvements + +Links: + +link:https://wiki.freebsd.org/BootTime[Wiki page] URL: link:https://wiki.freebsd.org/BootTime[https://wiki.freebsd.org/BootTime] + +link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[OS boot time comparison] URL: link:https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html[https://www.daemonology.net/blog/2021-08-12-EC2-boot-time-benchmarking.html] + +Contact: Colin Percival <cperciva@FreeBSD.org> + +Colin Percival is coordinating an effort to speed up the FreeBSD boot process. +For benchmarking purposes, he is primarily using an EC2 c5.xlarge instance as a reference platform and is measuring the time between when the virtual machine enters the EC2 "running" state and when it is possible to SSH into the instance. + +This work started in 2017, and as of the end of December 2021 the FreeBSD boot time was reduced from approximately 30 seconds to approximately 10 seconds. +During 2022Q1, further improvements have shaved more time off the boot process, taking it down to roughly 8 seconds + +Two major issues remain outstanding: + +. The first time an EC2 instance boots, dhclient takes about 2 seconds longer than normal to get an IPv4 address. The cause of this is unknown and requires investigation. + +. IPv6 configuration includes two one-second-long sleep(1) invocations, one from /etc/rc.d/netif and the other from /etc/rc.d/rtsold. +It might be possible to simply remove these; but care is needed to avoid progressing too far in the boot process before IPv6 addresses are configured. +Input from IPv6 experts is required here. + +Issues are listed on the wiki page as they are identified; the wiki page also has instructions for performing profiling. +Users are encouraged to profile the boot process on their own systems, in case they experience delays which don't show up on the system Colin is using for testing. + +This work is supported by Colin's FreeBSD/EC2 Patreon. + +Sponsor: https://www.patreon.com/cperciva diff --git a/website/content/en/status/report-2022-01-2022-03/ci.adoc b/website/content/en/status/report-2022-01-2022-03/ci.adoc new file mode 100644 index 0000000000..87bb1a9da1 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/ci.adoc @@ -0,0 +1,53 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] + +link:https://wiki.freebsd.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.freebsd.org/Jenkins[https://wiki.freebsd.org/Jenkins] + +link:https://wiki.freebsd.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.freebsd.org/HostedCI[https://wiki.freebsd.org/HostedCI] + +link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.freebsd.org/3rdPartySoftwareCI[https://wiki.freebsd.org/3rdPartySoftwareCI] + +link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] + +link:https://lists.freebsd.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.freebsd.org/subscription/dev-ci[https://lists.freebsd.org/subscription/dev-ci] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +The FreeBSD CI team maintains the continuous integration system of the FreeBSD project. +The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results. +The artifacts from those builds are archived in the link:https://artifact.ci.FreeBSD.org[artifact server] for further testing and debugging needs. +The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure. + +During the first quarter of 2022, we continued working with the contributors and developers in the project to fulfil their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD. + +Important changes: + +* link:https://ci.freebsd.org/job/FreeBSD-main-amd64-dtrace_test/[DTrace tests] are running with KASAN now. +* Fixed and resumed the powerpc64le test jobs. + +Retired jobs: + +* The jobs of main branch on mips* were removed. + +Work in progress and open tasks: + +* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) +* Designing and implementing use of CI cluster to build release artifacts as release engineering does +* Collecting and sorting CI tasks and ideas link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[here] +* Testing and merging pull requests in link:https://github.com/freebsd/freebsd-ci/pulls[the FreeBSD-ci repo] +* Reducing the procedures of CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Setting up public network access for the VM guest running tests +* Implementing using bare metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Adding more external toolchain related jobs +* Improving maturity of the hardware lab and adding more hardware under test +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.freebsd.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort! + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc b/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc new file mode 100644 index 0000000000..c78e7c0543 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/clusteradm.adoc @@ -0,0 +1,49 @@ +=== Cluster Administration Team + +Links: + +link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[https://www.freebsd.org/administration/#t-clusteradm] + +Contact: Cluster Administration Team <clusteradm@FreeBSD.org> + +FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications. +In this quarter, the team has worked on the following: + +* Improved web service performance and security +** Moved some critical services to newer machines +** Swept all services to ensure the support of TLS v1.2 and v1.3 and disable v1 and v1.1 +** Enabled dual-stack certificates for the primary FreeBSD web services. + + ECDSA and RSA certificates, preferring ECDSA, discussed with secteam@, benefit the project in favor of security and performance matter. +* Infrastructure improvements at primary site +** Evicted some very old hardware +** Moved cluster internal services to newer hardware +*** Build host +*** Parts of LDAP, kerberos, DNS and NTP +* Installed an additional aarch64 package builder +** ampere3.nyi.freebsd.org +** Identical specs to ampere[12].nyi.freebsd.org +* Moved ftp0.nyi.freebsd.org to an aarch64 machine. +* Main distributed mirror site, download.freebsd.org, enhancements +** Updated link:https://download.freebsd.org/doc/[offline documentation] (PDF and HTML) in the mirrors. + + The old directory `/doc` is now on link:http://ftp-archive.freebsd.org/mirror/FreeBSD-Archive/old-docs/[ftp-archive]; it contains files prior to the Hugo/Asciidoctor migration. +** Moved ports INDEX files to distributed mirror, download.freebsd.org +** Removed `/ftp` from the canonical URLs of files on download.freebsd.org. + + Old URLs are still valid. +* Cleanup of Handbook/Mirrors section + + Much stale information; now there is more info about the official mirrors and locations. Former official mirrors are now named 'Community mirrors'. +* Ongoing day to day cluster administration +** Cluster refresh +** Replacing failed disks +** Babysitting pkgsync + +Work in progress: + +* Improve the package building infrastructure +* Review the service jails and service administrators operation +* Set up powerpc pkgbuilder/ref/universal machines +* Search for more providers that can fit the requirements for a link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] or a link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny mirror] +* Work with doceng@ to improve https://www.freebsd.org and https://docs.freebsd.org +* Improve the web service architecture +* Improve the cluster backup plan +* Improve the log analysis system +* Set up Australia mirror +* Hardware refresh diff --git a/website/content/en/status/report-2022-01-2022-03/doceng.adoc b/website/content/en/status/report-2022-01-2022-03/doceng.adoc new file mode 100644 index 0000000000..cc74e6d63a --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/doceng.adoc @@ -0,0 +1,100 @@ +//// +Quarter: 1st quarter of 2022 +Prepared by: dbaio +Reviewed by: carlavilla +Last edit: $Date: 2022-04-09 09:51:36 -0300 (Sat, 09 Apr 2022) $ +Version: $Id: doceng-2022-1st-quarter-status-report.adoc 221 2022-04-09 12:51:36Z dbaio $ +//// + +=== Documentation Engineering Team + +Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] + +Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] + +Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] + +Contact: FreeBSD Doceng Team <doceng@FreeBSD.org> + +The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. + +No new documentation commit bit was granted during the last quarter, and only one commit bit was safe kept. + +Several tasks were completed related to the doc tree during the last quarter: + +* Fix some issues in the translation workflow with PO files and Weblate related to the po4a program. ++ +More info link:https://lists.freebsd.org/archives/freebsd-translators/2022-February/000029.html[here]. + +* Update link:https://download.freebsd.org/doc/[offline documentation (PDF and HTML)]. ++ +The old directory /doc is now on link:http://ftp-archive.freebsd.org/mirror/FreeBSD-Archive/old-docs/[ftp-archive]; it contains files prior to the Hugo/Asciidoctor migration. + +* Remove Google Analytics from documentation and website. + +* Add last modified information to the documentation and website pages. + +* Tag FreeBSD docset for 13.1-RELEASE. + +* Add the first Indonesian translation to the doc tree. + + +==== FreeBSD Translations on Weblate + +Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] + +Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] + +The translation workflow with Weblate is more mature at this point. +Several issues were fixed between PO files and po4a program. + +We welcome everyone to try our Weblate instance to translate a few documents. + +The first Indonesian translation was added to the FreeBSD project. +We thank Azrael JD for the contribution, and we are looking forward to seeing more Indonesian translations. + +===== Q1 2022 Status + +* 12 languages (1 new language) +* 142 registered users + +===== Languages + +* Chinese (Simplified) (zh-cn) +* Chinese (Traditional) (zh-tw) +* Dutch (nl) +* French (fr) +* German (de) +* Indonesian (id) - Added +* Italian (it) +* Norwegian (nb-no) +* Persian (fa-ir) +* Portuguese (pt-br) +* Spanish (es) +* Turkish (tr) + +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 Website Revamp - WebApps working group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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 will be 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. (_Work in progress_) + +. 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. (_Not started_) diff --git a/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc b/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc new file mode 100644 index 0000000000..b7fdc16a03 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/dpaa2.adoc @@ -0,0 +1,32 @@ +=== NXP DPAA2 support + +Links + +link:https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[Development] URL: https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2] + + +Contact: Dmitry Salychev <dsl@mcusim.org> + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +Some of the NXP SoCs (LX2160A, LS1088A) are shipped with link:https://www.nxp.com/design/qoriq-developer-resources/second-generation-data-path-acceleration-architecture-dpaa2:DPAA2[DPAA2], the second generation of the data path acceleration architecture. +It allows to dynamically configure and wire packet processing "objects" (like DPNI for a network interface, DPMAC for media access controller, etc.) together to form a network-on-a-chip. + +link:https://solidrun.atlassian.net/wiki/spaces/developer/pages/197494288/HoneyComb+LX2+ClearFog+CX+LX2+Quick+Start+Guide[Honeycomb LX2], as one of the powerful ARM64 boards from SolidRun, is also built around NXP LX2160A and lacks on-board GbE support in FreeBSD. +These drivers are about to change it. + +It's still work in progress and a rough implementation of the drivers for some DPAA2 objects is available at the moment. +A new network interface (dpni) can be used on Honeycomb for testing. + +TODO: + +* Update dpaa2_mc_fdt driver for the link:https://www.crowdsupply.com/traverse-technologies/ten64[Traverse Ten64] board + +* Review and fix DPAA2 resources allocation to support as many DPNIs as possible + +* Free driver resources properly + +* Implement CPU affinity for DPIOs and DPNIs + +* Implement cached memory-backed software portals + +* Profile and mitigate bottlenecks + +Sponsor: Bare Enthusiasm :) diff --git a/website/content/en/status/report-2022-01-2022-03/ena.adoc b/website/content/en/status/report-2022-01-2022-03/ena.adoc new file mode 100644 index 0000000000..4f2edefd50 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/ena.adoc @@ -0,0 +1,26 @@ +=== ENA FreeBSD Driver Update + +Links: + +link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README] + +Contact: Michal Krawczyk <mk@semihalf.com> + +Contact: Dawid Gorecki <dgr@semihalf.com> + +Contact: Marcin Wojtas <mw@semihalf.com> + +ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS). +The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used. + +Completed since the last update: + +* Add IPv6 layer 4 checksum offload support to the driver +* Add NUMA awareness to the driver when the RSS kernel option is enabled +* Rework validation of the Tx request ID +* Change lifetime of the driver's timer service +* Avoid reset triggering when the device is unresponsive + +Work in progress: + +* Prototype the driver port to the iflib framework +* Tests of the incoming ENA driver release (v2.5.0) + +Sponsor: Amazon.com Inc diff --git a/website/content/en/status/report-2022-01-2022-03/fpart.adoc b/website/content/en/status/report-2022-01-2022-03/fpart.adoc new file mode 100644 index 0000000000..ecd0a060ff --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/fpart.adoc @@ -0,0 +1,38 @@ +=== Fpart and fpsync + +Links: + +link:https://www.fpart.org[Project site and documentation] URL: link:https://www.fpart.org[https://www.fpart.org] + +link:https://github.com/martymac/fpart[Development] URL: link:https://github.com/martymac/fpart[https://github.com/martymac/fpart] + +link:https://www.freshports.org/sysutils/fpart[Port] URL: link:https://www.freshports.org/sysutils/fpart[https://www.freshports.org/sysutils/fpart] + +Contact: Ganael Laplanche <martymac@FreeBSD.org> + +==== What is fpart ? + +Fpart is a *filesystem partitioner*. It helps you sort file trees and pack them into bags ("partitions"). + +It uses FreeBSD's fts(3) implementation (GNU/Linux builds can also use it as an option), which makes it crawl filesystems very fast. + +A hook facility is provided to trigger actions on the partitions produced. + +==== What is fpsync ? + +Fpsync is a companion script that uses fpart under the hood to parallelize rsync(1) or cpio(1) jobs, making it a simple but powerful data migration tool. Those jobs can be run either locally or remotely (using SSH). Fpsync is link:https://www.fpart.org/links/[often used by researchers and cloud providers] where lots of data need to be moved and clusters are available to speed up transfers. + +==== Q1 2022 Status + +Both tools continued to evolve and saw several bugs fixed; see the link:https://www.fpart.org/changelog/[changelog]. + +Also, a user reported a major bug regarding our fts(3) implementation, which ignores readdir(3) errors. I have reported the bug in our Bugzilla: + +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262038[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262038] + +It should be merged soon (hopefully). + +Last but not least, fpart has been link:https://sill.etalab.gouv.fr/fr/software?id=229[referenced in the French Government's 'SILL']. + +==== Contributing + +If you are interested in contributing, have a look at the link:https://github.com/martymac/fpart/blob/master/TODO[TODO list]. + +Any contribution is welcome, more especially in the field of unit testing. diff --git a/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc b/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc new file mode 100644 index 0000000000..fad2959648 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/freebsd-foundation.adoc @@ -0,0 +1,145 @@ +=== FreeBSD Foundation + +Links: + +link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] + +link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] + +link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] + +link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] + +link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] + +link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/] + +Contact: Deb Goodkin <deb@FreeBSDFoundation.org> + +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. +We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. +We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. + +Here are some highlights from the Foundation for the first quarter of 2022. + +==== Fundraising Efforts + +As promised, we updated our fundraising meter for 2022. So far, we’ve raised over $84,000 towards our 2022 goal of $1,400,000. +We’d like to thank our individual and corporate donors for supporting our efforts this year. +We’d also like to give a big shout out to our Gold Sponsor, Facebook, Silver Sponsors, VMware and Tarsnap, and the companies that provide free hosting for the Project: Bytemark, 365 Data Centers, NYI, NextArray, Sentex Data Communications, and the Computer Science Department at NCTU. + +You can find out how we spent your donations by reading about what we supported in Q1, in this report, and our Spring Newsletter. + +If you haven’t made a donation this year, please consider making a donation now at https://freebsdfoundation.org/donate/. + +We also have a Partnership Program for larger commercial donors. You can find out more at https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/ + +==== OS Improvements + +During the first quarter of 2022, 372 src, 41 ports, and 16 doc tree commits were made that identified The FreeBSD Foundation as a sponsor. +# This represents 16, 0.4, and 5% of the total number of commits in each repository. + +You can read about Foundation-sponsored projects in individual quarterly report entries: + +* Crypto changes for WireGuard +* Intel Wireless driver support + +Here is a small sample of other base system improvements from Foundation developers this quarter that do not have separate report entries. + +==== riscv: Add support for enabling SV48 mode + +SV48 is intended for systems for which a 39-bit virtual address space is insufficient. This change increases the size of the user map from 256GB to 128TB. +The kernel map is left unchanged for now. + +For now SV48 mode is left disabled by default, but can be enabled with a tunable. +Note that extant hardware does not implement SV48, but QEMU does. + +* In pmap_bootstrap(), allocate a L0 page and attempt to enable SV48 mode. + If the write to SATP doesn't take, the kernel continues to run in SV39 mode. +* Define VM_MAX_USER_ADDRESS to refer to the SV48 limit. + In SV39 mode, the region [VM_MAX_USER_ADDRESS_SV39, VM_MAX_USER_ADDRESS_SV48] is not mappable. + +==== Add v3 support to CTF tools + +CTF, the Compact C Type Format, is a representation of type information most often contained within ELF binaries. +This type information is helpful for probing tools like DTrace. +Recent work by Mark Johnston allows different Dtrace providers like the FBT (Function Boundary Tracing) provider to work with version 3 of CTF. + +==== FreeBSD on the Framework Laptop + +Two Foundation staff members, Ed Maste and Mark Johnston, as well as a few developers and community members now each have access to Framework laptops, which are designed to make hardware upgrades, repairs, and customizations straightforward for the average user. The goal of this work is to ensure that the experience running FreeBSD on the laptops matches the stability that FreeBSD users expect. + +Recent improvements and fixes include: + +* Making audio switch appropriately between speakers and the headphone jack when headphones are plugged in or unplugged +* Fixing bug 259230, which would cause a Framework laptop to reboot or power off when the touchpad was used. +* Adding the Tempo Semiconductor 92HD95B HDA codec ID +* Temporarily fixing stalled usb enumeration, bluetooth, and S3 resume. The temporary fix is to avoid attaching to several newer Intel controllers, which require firmware to be loaded, which is different from that implemented by ng_ubt_intel and iwmbtfw, so they are not usable yet. +* Avoiding a 16 second boot delay, by probing the TSC frequency earlier. This lets us use the TSC to implement early DELAY, limiting the use of the sometimes-unreliable 8254 PIT. + +You can follow news about FreeBSD work on the Framework laptop at: https://wiki.freebsd.org/Laptops/Framework_Laptop. + +==== Continuous Integration and Quality Assurance + +The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. + +==== Supporting FreeBSD Infrastructure + +The Foundation provides hardware and support for the Project. +At the time of writing, the server that will become the new Australian mirror has arrived in Australia, has a fresh FreeBSD install and will shortly join the cluster. + +==== FreeBSD Advocacy and Education + +Much of our effort is dedicated to Project advocacy. This may involve +highlighting interesting FreeBSD work, producing literature, attending +events, or giving presentations. The goal of the literature we produce +is to teach people FreeBSD basics and help make their path to adoption +or contribution easier. Other than attending and presenting at events, +we encourage and help community members run their own FreeBSD events, +give presentations, or staff FreeBSD tables. + +The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups. +We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. +This all helps provide a healthy ecosystem. +We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. +We are continuing to attend virtual events and began planning the June 2022 Developer Summit. + +Check out some of the advocacy and education work we did last quarter: + +* Committed to hosting a FreeBSD Workshop at SCALE 19x and serve as a Media Sponsor - July 28-31, 2022 in Los Angeles, CA + +* Participated in the FLOSS Weekly Podcast - January 5, 2022 https://twit.tv/shows/floss-weekly/episodes/662 + +* Sent out the 2021 Impact Report showcasing how we supported the Project last year. https://freebsdfoundation.org/blog/2021-freebsd-foundation-impact-report/ + +* Hosted a stand at FOSDEM 2022 - Videos from the stand can be found at: https://youtube.com/playlist?list=PLugwS7L7NMXxwqIRg1PlhgzhNRi1eVdRQ + +* Participated in the Open Source Voices Podcast - Episode to be aired in late April [note from status report team: the episode has indeed be aired and is now available at https://www.opensourcevoices.org/29; unfortunately, there is and will be no transcript.] + +* Began planning the June 2022 FreeBSD Developers Summit taking place virtually, June 16-17, 2022 https://wiki.freebsd.org/DevSummit/202206 + +* Held a new FreeBSD Friday - How to Track FreeBSD Using Git Pt. 2 https://youtu.be/Fe-dJrDMK_0 + +* Presented at the St. Louis Unix User Group on March 9, 2022 https://ow.ly/1QXn50Ivj75 + +* Served as Admins and were accepted as a mentoring organization for the 2022 Google Summer of Code + +* Held an Office Hours session on Google Summer of Code. https://youtu.be/x-4U1xurmBE + +* Hosted a booth at the virtual Open Source 101 conference on March 29, 2022 + +* New blog posts: + +** link:https://freebsdfoundation.org/blog/raid-z-expansion-feature-for-zfs/[RAID-Z Expansion Feature for ZFS In the Home Stretch] +** link:https://freebsdfoundation.org/blog/whats-ahead-for-freebsd-and-the-foundation-in-2022/[What's Ahead for FreeBSD and the Foundation in 2022] +** link:https://freebsdfoundation.org/blog/work-with-freebsd-in-google-summer-of-code/[Work with FreeBSD in Google Summer of Code] + +* New How-To Guide: link:https://freebsdfoundation.org/freebsd-project/resources/introduction-to-freebsd-jails/[An Introduction to FreeBSD Jails] + +* New FreeBSD Journal Article: link:https://freebsdfoundation.org/wp-content/uploads/2022/04/Contributing-to-FreeBSD-Ports-with-Git.pdf[Contributing to FreeBSD ports with Git] + +We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. +As we mentioned previously, the FreeBSD Journal is now a free publication. +Find out more and access the latest issues at https://www.FreeBSDfoundation.org/journal/ + +You can find out more about events we attended and upcoming events at https://www.FreeBSDfoundation.org/news-and-events/. + +==== 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://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2022-01-2022-03/gcc.adoc b/website/content/en/status/report-2022-01-2022-03/gcc.adoc new file mode 100644 index 0000000000..003d15a7bb --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/gcc.adoc @@ -0,0 +1,28 @@ +=== lang/gcc* ports need some love and attention + +Links: + +link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] + +link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/] + +Contact: toolchain@FreeBSD.org + +Contact: Gerald Pfeifer <gerald@pfeifer.com> + +After about two decades of maintaining FreeBSD's lang/gcc* ports, the time came to hand over the baton and mostly step back. +Alas the baton essentially dropped to the floor, despite multiple calls for help. + +Here are a few specific tasks looking for help: + + * Upgrade GCC_DEFAULT in Mk/bsd.default-versions.mk from 10 to 11, + including fixing the (luckily minor) fall out of an -exp run: + link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378] + + * Three changes to work through with upstream GCC (requires src + expertise, not ports): + + ** upstreaming lang/gcc11/patch-gets-no-more + ** upstreaming lang/gcc11/patch-arm-unwind-cxx-support + ** link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874] + + * We have removed the unmaintained lang/gcc9-devel and lang/gcc10-devel + ports, alas kept lang/gcc11-devel and lang/gcc12-devel which would be + good to see if not weekly, then somewhat regular updates. diff --git a/website/content/en/status/report-2022-01-2022-03/gunion.adoc b/website/content/en/status/report-2022-01-2022-03/gunion.adoc new file mode 100644 index 0000000000..b0058476c7 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/gunion.adoc @@ -0,0 +1,23 @@ +=== A New GEOM Facility, gunion + +Contact: Marshall Kirk McKusick <mckusick@mckusick.com> + +The gunion facility is used to track changes to a read-only disk on a writable disk. +Logically, a writable disk is placed over a read-only disk. +Write requests are intercepted and stored on the writable disk. +Read requests are first checked to see if they have been written on the top (writable disk) and if found are returned. +If they have not been written on the top disk, then they are read from the lower disk. + +The gunion facility can be especially useful if you have a large disk with a corrupted filesystem that you are unsure of how to repair. +You can use gunion to place another disk over the corrupted disk and then attempt to repair the filesystem. +If the repair fails, you can revert all the changes in the upper disk and be back to the unchanged state of the lower disk thus allowing you to try another approach to repairing it. +If the repair is successful you can commit all the writes recorded on the top disk to the lower disk. + +Another use of the gunion facility is to try out upgrades to your system. +Place the upper disk over the disk holding your filesystem that is to be upgraded and then run the upgrade on it. +If it works, commit it; if it fails, revert the upgrade. + +The gunion(8) utility is used to create and manage an instance of a gunion. Further details and usage examples can be found in the gunion(8) manual page. +At this time, gunion(8) is available only in 14.0. + +Sponsor: Netflix diff --git a/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc b/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc new file mode 100644 index 0000000000..07ba012ddd --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/hellosystem.adoc @@ -0,0 +1,28 @@ +=== helloSystem + +Links: + +link:https://hellosystem.github.io/docs/[Documentation] URL: link:https://hellosystem.github.io/[https://hellosystem.github.io/] + +Contact: Simon Peter <probono@puredarwin.org> + +Contact: `\#helloSystem` on `irc.libera.chat`, mirrored to link:https://matrix.to/#/%23helloSystem:matrix.org?via=matrix.org[`#helloSystem:matrix.org` on Matrix] + +==== What is helloSystem? + +helloSystem is FreeBSD preconfigured as a desktop operating system with a focus on simplicity, elegance, and usability. +Its design follows the “Less, but better” philosophy. + +==== Q1 2022 Status + +* Version 0.8.0 of helloSystem is under development and test +** helloSystem 0.8.0 will be based on FreeBSD 13.1-RELEASE +** Experimental Live ISOs using FreeBSD 13.1-BETA3 are available +** Initial support for running Linux AppImage files using an optional Debian runtime +** Initial support for the AppImage format in the user interface +** Improved reliability and performance of mounted archives by using fuse-archive +** Various bugfixes + +Installable experimental Live ISO images are available at https://github.com/helloSystem/ISO/releases/tag/experimental-13.1. + +==== Contributing + +link:https://github.com/helloSystem/hello/blob/master/CONTRIBUTING.md[The project appreciates contributions in various areas]. diff --git a/website/content/en/status/report-2022-01-2022-03/intro.adoc b/website/content/en/status/report-2022-01-2022-03/intro.adoc new file mode 100644 index 0000000000..a24df1bff6 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/intro.adoc @@ -0,0 +1,11 @@ +As things are yet again settling into a new normal, it's once again time for a status report for the FreeBSD Project. + +You may have noticed that this report is also a little on the late side, and it's with regret that it's taken this long to get to it - however, thanks to a few kind souls who've stepped up to the plate, in addition to the folks on the team who do things quietly in the background, future reports should hopefully be more on time. + +So let's get some introductions in order, as yours truly is delighted to accept a hand from Pau Amma who already has been helping with reviews for a while, Lorenzo Salvadore who is stepping up to get some tooling in place to make it less of a chore to make the reports, as well as Sergio Carlavilla who is stepping up to help with all the work that can't be easily automated. + +This report covers a very diverse set of topics including but not limited to accessibility, system boot speed-up, an implementation of GEOM union, changes to the WiFi situation, and many other things. + +We hope you'll enjoy reading it! + +Daniel Ebdrup Jensen, on behalf of the status report team. diff --git a/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc b/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc new file mode 100644 index 0000000000..f1f9990407 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/iwlwifi.adoc @@ -0,0 +1,26 @@ +=== Intel Wireless driver support and LinuxKPI 802.11 compatibility layer + +Links: + +link:https://wiki.freebsd.org/WiFi/Iwlwifi[iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi] + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +The Intel Wireless driver update project aims to bring support for newer chipsets along with mac80211 LinuxKPI compat code. +The dual-licensed Intel driver code was ported in the past for the iwm(4) native driver; using the LinuxKPI compat framework allows us to use the driver directly and gives support to all the latest chipsets, with only minor local modifications. +Some of the changes made while porting the driver to FreeBSD were kindly incorporated into the upstream Linux driver already. + +During the first quarter work continued with about 70 commits. +Updating the driver and firmware reduced differences to the Linux version and gave us bugfixes and improvements. +Changes to the LinuxKPI 802.11 compatibility layer were made to avoid firmware crashes and possible panics for users along with other improvements. + +Auto-loading support for LinuxKPI PCI drivers was comitted. +This means that iwlwifi(4) will now load automatically during boot if a supported card is detected without any user interactions. +Considering the current state of the driver and the next release a decision was made that iwm(4) supported chipsets will continue to attach to iwm(4) for now and only newer and otherwise unsupported chipsets will use the iwlwifi(4) driver. +This is likely going to change in CURRENT as soon as iwlwifi(4) provides better support than iwm(4). + +The code was merged to the stable/13 branch and the current state will be shipped with the upcoming 13.1-RELEASE. + +In addition to The FreeBSD Foundation thanks need to go to all users who have been testing and reporting back or are patiently waiting for the next update. +For the latest state of the development, please follow the freebsd-wireless mailing list. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-01-2022-03/kde.adoc b/website/content/en/status/report-2022-01-2022-03/kde.adoc new file mode 100644 index 0000000000..539e8ba58e --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/kde.adoc @@ -0,0 +1,52 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] + +link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project packages the software from the KDE Community, along with dependencies and related software, for the FreeBSD ports tree. +The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The KDE team (kde@) is part of desktop@ and x11@ as well, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine. + +*KDE Qt Patch Collection* The Qt Company did not release Qt 5.15 updates under Open Source licenses in 2021, leaving the Open Source 5.15 version lagging behind the proprietary release. +Qt 6 is released under an Open Source license, but for the world of Open Source software that requires Qt 5, there is still a need for updates. +The KDE Community fills that need by maintaining a curated set of patches -- generally backported from Qt6 -- to maintain the Open Source version of Qt 5. +FreeBSD ports now use this *KDE Qt Patch Collection*, rather than the outdated last Qt 5.15.2 release from the Qt Company. +This landed both in main and the last quarterly branch for 2021, since it brings important bugfixes. + +==== KDE Stack + +* *KDE Plasma Desktop* (all the `*/plasma5-*` ports) was updated to 5.23.5 at the start of the year. Since this happened very shortly after quarterly was branched, this was MFH'ed. The long-term-support release 5.24 landed mid-february. The FreeBSD ports do not stick to LTS releases, and will follow the regular release schedule. 5.24.3 landed on schedule in March. +* *KDE Gear* (the collection of KDE libraries and applicatious outside of the Frameworks and Plasma Desktop groups) was updated to 21.12.1 and MFH'ed. Monthy releases landed as well: 21.12.2 in February. +* *KDE Frameworks* have a monthly release cadence, so 5.90 landed in January, 5.91 in February and 5.92 in March. +* *KDE PIM* currently does not support Contacts stored in a Google account because Google has changed the available REST API. +* *astro/kstars* received its regularly scheduled updates. +* *deskutils/kalendar* was updated. It has now reached the 1.0 stage. +* *deskutils/kodaskanna* was added to the ports tree. It is a simple QR-code scanner for the desktop. +* *deskutils/latte-dock* is an alternative launcher for use in KDE Plasma Desktop and other environments. It was updated to 0.10.7 as part of its monthly releases. +* *devel/okteta*, an editor and viewer for binary data, was updated to 0.26.7, a regular bugfix release. +* *graphics/digikam*, the digital photography manager, was updated to 7.6.0. (Thanks Dima Panov) +* *graphics/kf5-kimageformats* has a new option enabling libheif and HEIC support. +* *graphics/kontrast* was added to the 'accessibility' category. This is a tool for checking color-combinations (e.g. for a website) for sufficient contrast and readability. +* *graphics/krita* was updated to the next big release, Krita 5. (Thanks Max Brazhnikov) +* *lang/kross-interpreters* was fixed for Ruby 3. (Thanks Yasuhiro Kimura) +* *sysutils/plasma5-discover* was updated to resolve some denial-of-service bugs in KDE infrastructure. +* *www/falkon* was updated. After a two-year wait, a new release of the KDE web browser built on Qt WebEngine (itself a wrapper around Chromium internals) arrived upstream and in ports. +* *x11/plasma5-plasma-workspace* now can properly edit login and account information. + + +==== Related Applications + +* *devel/qtcreator* was updated to version 6. A new versioning model has been introduced by upstream, so this will now jump by major release number regularly. (Thanks to Florian Walpen) +* *irc/quassel* was updated. Quassel is a distributed IRC client (think of it as your own personal IRC bouncer). +* *misc/tellico* was updated. Tellico is a "collection manager", for instance collections of books, music, stamps, or FreeBSD releases. +* *net-im/nheko* was updated. This is one of a dozen Matrix clients available in the ports tree. + +==== Elsewhere + +* *archivers/7-zip* is the preferred tool for dealing with 7zip files; this affacts KDE applications that work with archives (like *archivers/ark*). We would like to thank makc@ for stewarding that update. +* *devel/libphonenumber* has bi-weekly updates to chase the exciting world of telephony details. +* *graphics/poppler* was updated to version 22.01. This version requires C{plus}{plus}17, which pushes a number of consumers to the newer C{plus}{plus} standard as well. Most consumers were fixed in advance. diff --git a/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc b/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc new file mode 100644 index 0000000000..b8f6f51fc8 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/ocf-wg.adoc @@ -0,0 +1,14 @@ +=== Kernel Crypto changes to support WireGuard + +Contact: John Baldwin <jhb@FreeBSD.org> + +During the last quarter, I continued my work to improve the FreeBSD WireGuard driver. +On the FreeBSD side, I added support for the XChaCha20-Poly1305 AEAD cipher. +I also added a dedicated API to support [X]ChaCha20-Poly1035 on small, flat buffers. +Finally, I added an API wrapper for the curve25519 implementation from libsodium. + +For the WireGuard driver, I wrote a series of patches which updates the driver to use crypto APIs such as those mentioned above in place of internal cipher implementations. +The series also includes a fix to avoid scheduling excessive crypto tasks as well as a few other small fixes. +This series is pending review. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-01-2022-03/office.adoc b/website/content/en/status/report-2022-01-2022-03/office.adoc new file mode 100644 index 0000000000..5b1503d300 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/office.adoc @@ -0,0 +1,24 @@ +=== FreeBSD Office Team + +Links: + +link:https://wiki.freebsd.org/Office[The FreeBSD Office project] URL: link:https://wiki.freebsd.org/Office[https://wiki.freebsd.org/Office] + +link:https://lists.freebsd.org/subscription/freebsd-office[The FreeBSD Office mailing list] URL: link:https://lists.freebsd.org/subscription/freebsd-office[https://lists.freebsd.org/subscription/freebsd-office] + +Contact: FreeBSD Office team ML <office@FreeBSD.org> + +Contact: Dima Panov <fluffy@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +The FreeBSD Office team works on a number of office-related software suites and tools such as OpenOffice and LibreOffice. + +Work during this quarter was focused on providing the latest stable release of LibreOffice suite and companion apps to all FreeBSD users. + +During the 2022Q1 period we pushed maintenance patches for the LibreOffice 7.2 port to the quarterly branch and brought the latest, 7.3, releases and all companion libraries such as MDDS, libIxion and more to the ports tree. + +Also we are still working on the link:https://github.com/fluffykhv/freebsd-ports-boost[Boost WIP repository] to bring the latest Boost library to the ports. + +We are looking for people to help with the open tasks: + +* The link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=office%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailreporter1=1&emailtype1=substring&query_format=advanced&list_id=374316[open bugs list] contains all filed issues which need some attention +* Upstream link:https://cgit.freebsd.org/ports/tree/editors/libreoffice/files[local patches in ports] + +Patches, comments and objections are always welcome in the mailing list and Bugzilla. diff --git a/website/content/en/status/report-2022-01-2022-03/portconfig.adoc b/website/content/en/status/report-2022-01-2022-03/portconfig.adoc new file mode 100644 index 0000000000..205201ff8c --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/portconfig.adoc @@ -0,0 +1,18 @@ +=== PortConfig + +Links: + +link:https://gitlab.com/alfix/portconfig/[Repository portconfig] URL: link:https://gitlab.com/alfix/portconfig/[https://gitlab.com/alfix/portconfig/] + +Contact: Alfonso Sabato Siciliano (upstream) <asiciliano@FreeBSD.org> + +Contact: Baptiste Daroussin (port) <bapt@FreeBSD.org> + +FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications. +It is possible to configure a port before the building and installation. +PortConfig is an utility for setting the port options via a Text User Interface. + +As each terminal has different properties PortConfig can be customized via environment variables to set up the User Interface, for example: menu size, theme, borders, and so on; each feature is documented inside the manual. +Further, if a port has a specific 'pkg-help' file, PortConfig will show a Help button to open a "popup" with help information. + +FreeBSD provides thousands of ports therefore it is not feasible to test PortConfig for each use; please report any problem. + +Alfonso would like to thank Baptiste Daroussin for the port, suggestions, help, and testing for this utility and its library. diff --git a/website/content/en/status/report-2022-01-2022-03/portmgr.adoc b/website/content/en/status/report-2022-01-2022-03/portmgr.adoc new file mode 100644 index 0000000000..ade42a0bb4 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/portmgr.adoc @@ -0,0 +1,53 @@ +=== Ports Collection + +Links: + +link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[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[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] + +link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] + +link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[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/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/] + +Contact: René Ladan <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +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. + +Before we start with the usual statistics, portmgr is happy to announce it has successfully restarted its lurker program. +The first two lurkers are pizzamig@ and se@; they will learn about the inner workings of portmgr and bring in new ideas. + +Portmgr also started having bi-weekly meetings, some public results are: + +* restarting the lurker program +* fixes to ports going backwards in version +* dropping DragonFlyBSD version checks in bsd.port.mk +* dropping deprecation notes from ports transitively using Python 2.7 + +Currently we have over 46,800 ports in the Ports Tree. There are currently 2,700 open ports PRs of which 680 are unassigned. +The last quarter saw 9,403 commits to the main branch by 157 committers and 683 commits to the 2022Q1 branch by 63 committers. +Compared to last quarter, this means a slight drop in activity to the main branch and a slight +increase in the number of open PRs. + +No new committers joined during the last quarter, portmgr took one commit bit in for safekeeping because of a lack of recent commits. + +The cluster administration team has provided portmgr with a third aarch64 builder; it is being used for package builds. + +Things that happened in git: + +* Two new USES were introduced: +** elfctl to change an ELF binary's feature control note +** minizip to get the correct library dependency on minizip +* Two keywords got removed: +** fcfontsdir (now handled by USES=fonts) +** glib-schemas, it has been replaced by a trigger +* Default versions that changed: +** Lazarus switched to 2.2.0 +** PHP switched to 8.0 +* Some upgrades to major ports: +** Chromium 100.0.4896.60 +** Electron 13.6.9 +** Firefox 99.0 +** Firefox ESR 91.8.0 +** Gnome 41 +** KDE Frameworks 5.92.0 +** KDE Plasma 5.24.4 diff --git a/website/content/en/status/report-2022-01-2022-03/pot.adoc b/website/content/en/status/report-2022-01-2022-03/pot.adoc new file mode 100644 index 0000000000..cbcb21123d --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/pot.adoc @@ -0,0 +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[https://github.com/bsdpot] + +Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> + +Contact: Stephan Lichtenauer (Potluck) <sl@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@freebsd.org> + +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]. + +As a result of production testing in a real-world cluster deployment, pot and related projects received stability improvements for controlling the pot lifecycle (i.e., pot prepare/start/stop). + +Various attributes and commands have been developed to improve support of nomad orchestration and batch jobs (e.g., change dns config during clone, ability to disable tmpfs, new last-run-stats command). A new pot release will follow soon. + +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. + +Many of the core images like link:https://potluck.honeyguide.net/blog/nomad-server/[Nomad], link:https://potluck.honeyguide.net/blog/consul/[Consul] and link:https://potluck.honeyguide.net/blog/vault/[Vault] that can be used to build a private cloud and orchestration platform, but also e.g. link:https://potluck.honeyguide.net/blog/prometheus/[Prometheus] or link:https://potluck.honeyguide.net/blog/postgresql-patroni/[PostgreSQL Patroni], have reached a stable status over the last quarter and are in production use now. + +To make navigating the evolving pot ecosystem easier, most project resources have been centralized in a dedicated github project: link:https://github.com/bsdpot[https://github.com/bsdpot] + +There, we plan to release ansible playbooks that allow easily creating a FreeBSD based orchestration environment from scratch based on all these tools. + +As always, feedback and patches are welcome. diff --git a/website/content/en/status/report-2022-01-2022-03/releng.adoc b/website/content/en/status/report-2022-01-2022-03/releng.adoc new file mode 100644 index 0000000000..4e91252673 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/releng.adoc @@ -0,0 +1,21 @@ +=== FreeBSD Release Engineering Team + +Links: + +link:https://www.freebsd.org/releases/13.1R/schedule/[FreeBSD 13.1-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.1R/schedule/[https://www.freebsd.org/releases/13.1R/schedule/] + +link:https://www.freebsd.org/releases/13.1R/[FreeBSD 13.1 Release Information] URL: link:https://www.freebsd.org/releases/13.1R/[https://www.freebsd.org/releases/13.1R/] [link added by status report team as this quarterly status report is being published after 13.1-RELEASE has been released] + +link:https://download.freebsd.org/ftp/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/ftp/releases/ISO-IMAGES/[https://download.freebsd.org/ftp/releases/ISO-IMAGES/] + +link:https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/[https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/] + +Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org> + +The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. + +During the first quarter of 2022, the Release Engineering Team completed work on, and submitted to the developers the 13.1-RELEASE schedule. This will be the second point release from the stable/13 branch. +As of this writing, three BETA builds have been run, with at least two RC builds before the final release, currently scheduled for April 21, 2022. + +We look forward to another consistently stable release at the end of this cycle, as well as many more to come for other branches moving forward. + +Additionally throughout the quarter, several development snapshots builds were released for the *main*, *stable/13*, and *stable/12* branches. + +Sponsor: Rubicon Communications, LLC ("Netgate") +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-01-2022-03/rtw88.adoc b/website/content/en/status/report-2022-01-2022-03/rtw88.adoc new file mode 100644 index 0000000000..8d7a852b40 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/rtw88.adoc @@ -0,0 +1,24 @@ +=== Realtek Wireless driver support + +Links: + +link:https://wiki.freebsd.org/WiFi/Rtw88[rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88] + +link:https://wiki.freebsd.org/WiFi/Rtw89[rtw89 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw89[https://wiki.freebsd.org/WiFi/Rtw89] + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +While the Intel Wireless driver update project is the main driver behind the work to bring support for newer chipsets and eventually newer IEEE 802.11 standards support, there is also an ongoing effort to support more drivers. +The next two drivers in the (already longer) queue are Realtek's rtw88 and rtw89. + +While the initial driver porting efforts for rtw88 and rtw89 happened on personal time, the LinuxKPI integration has to be done more and more along the Intel wireless driver work and so thanks are also due to The FreeBSD Foundation. + +The rtw88 driver has started to work on some machines with less than 4GB of main memory and was committed to the FreeBSD git repository for broader testing. +While our version of the driver is aware of these limitations, the problem is currently assumed to be outside the driver in the interactions with LinuxKPI and busdma. + +The rtw89 driver has happily started to send packets and has problems receiving frames at this point. +Further investigation will happen as soon as rtw88 is sorted out and it is expected that rtw89 will then also timely follow into FreeBSD's git repository. + +The currently known requirements to compile both drivers have mostly gone into stable/13 and releng/13.1 already. + +For the latest state of the development, please check the referenced wiki pages and follow the freebsd-wireless mailing list. + +Sponsor: The FreeBSD Foundation (partly) diff --git a/website/content/en/status/report-2022-01-2022-03/wifibox.adoc b/website/content/en/status/report-2022-01-2022-03/wifibox.adoc new file mode 100644 index 0000000000..6edbf18e57 --- /dev/null +++ b/website/content/en/status/report-2022-01-2022-03/wifibox.adoc @@ -0,0 +1,31 @@ +=== Wifibox: Use Linux to drive your wireless card on FreeBSD + +Links: + +link:https://github.com/pgj/freebsd-wifibox[Project GitHub Page] + +link:https://cgit.freebsd.org/ports/tree/net/wifibox[``net/wifibox`` port] + +Contact: PÁLI Gábor János <pali.gabor@gmail.com> + +Wifibox is an experimental project for exploring the ways of deploying a virtualized Linux guest to drive wireless networking cards on the FreeBSD host system. +There have been guides on the Internet to suggest the use of such techniques to improve the wireless networking experience, of which Wifibox aims to implement as a single easy-to-use software package. + +- man:bhyve[8] is utilized to run the embedded Linux system. + This helps to achieve low resource footprint. + It requires an x64 CPU with I/O MMU (AMD-Vi, Intel VT-d), ~150 MB physical memory, and some disk space available for the guest virtual disk image, which can be even ~30 MB only in certain cases. + It works with FreeBSD 12 and later, some cards may require a recent 13-STABLE though. + +- The guest is constructed using https://alpinelinux.org/[Alpine Linux], a security-oriented, lightweight distribution based on https://www.musl-libc.org/[musl libc] and https://busybox.net/[BusyBox]. + +- Configuration files are shared with the host system. The guest uses man:wpa_supplicant[8] so it is possible to import the host's man:wpa_supplicant.conf[8] file without any changes. + +- When configured, man:wpa_supplicant[8] control sockets could be exposed by the guest, which enables use of related utilities directly from the host, such as man:wpa_cli[8] or man:wpa_gui[8] from the ``net/wpa_supplicant_gui`` port/package. + +- Everything is shipped in a single package that can be easily installed and removed. + This comes with an man:rc[8] system service that automatically launches the guest on boot and stops it on shutdown. + +- A workaround is supplied for laptops to support suspend/resume. + +Wifibox has been mainly tested with Intel chipsets so far, and it has shown great performance and stability. +Therefore it might serve as an interim solution until the Intel Wireless support becomes mature enough. +It was confirmed that Wifibox works with Atheros chipsets too, and feedback is more than welcome about others. +Support for Broadcom chipsets is not yet complete, that is currently a work in progress. diff --git a/website/content/en/status/report-2022-04-2022-06/_index.adoc b/website/content/en/status/report-2022-04-2022-06/_index.adoc new file mode 100644 index 0000000000..1d5a0effd4 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/_index.adoc @@ -0,0 +1,164 @@ +--- +title: "FreeBSD Quarterly Status Report Second Quarter 2022" +sidenav: about +--- + += Introduction +:doctype: article +:toc: macro +:toclevels: 2 +:icons: font +:!sectnums: +:source-highlighter: rouge +:experimental: +:reports-path: content/en/status/report-2022-04-2022-06 + +include::{reports-path}/intro.adoc[] + +''' + +toc::[] + +''' + +[[FreeBSD-Team-Reports]] +== FreeBSD Team Reports + +Entries from the various official and semi-official teams, as found in the +link:../../administration/[Administration Page]. + +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 that span multiple categories, from the kernel and userspace to the +Ports Collection or external projects. + +include::{reports-path}/linuxulator.adoc[] + +''' + +include::{reports-path}/golang_riscv64.adoc[] + +''' + +include::{reports-path}/azure.adoc[] + +''' + +[[userland]] +== Userland + +Changes affecting the base system and programs in it. + +include::{reports-path}/lldb.adoc[] + +''' + +include::{reports-path}/makefs-zfs.adoc[] + +''' + +include::{reports-path}/openssh.adoc[] + +''' + +include::{reports-path}/pf.adoc[] + +''' + +[[kernel]] +== Kernel + +Updates to kernel subsystems/features, driver support, filesystems, and more. + +include::{reports-path}/ena.adoc[] + +''' + +include::{reports-path}/blued.adoc[] + +''' + +include::{reports-path}/if_ovpn.adoc[] + +''' + +include::{reports-path}/wifi.adoc[] + +''' + +include::{reports-path}/shp_rand.adoc[] + +''' + +[[architectures]] +== Architectures + +Updating platform-specific features and bringing in support for the new hardware +platform. + +include::{reports-path}/dpaa2.adoc[] + +''' + +include::{reports-path}/superpages.adoc[] + +''' + +[[documentation]] +== Documentation + +Noteworthy changes in the documentation tree, manual pages, or new external +books/documents. + +include::{reports-path}/doceng.adoc[] + +''' + +[[ports]] +== Ports + +Changes affecting the Ports Collection, whether sweeping changes that touch most +of the tree, or individual ports themselves. + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/gcc.adoc[] + +''' + +include::{reports-path}/valgrind.adoc[] + +''' + +include::{reports-path}/pantheon.adoc[] + +''' + +include::{reports-path}/igt-gpu-tools.adoc[] diff --git a/website/content/en/status/report-2022-04-2022-06/azure.adoc b/website/content/en/status/report-2022-04-2022-06/azure.adoc new file mode 100644 index 0000000000..3e24bc2407 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/azure.adoc @@ -0,0 +1,42 @@ +=== 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 <bsdic@microsoft.com> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] + +Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> + +Contact: Wei Hu <whu@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + + +The link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-13_1[13.1-RELEASE image on Azure Marketplace] has been published. + +Work in progress tasks: + +* Automating the image building and publishing process +* Building and publishing ZFS-based images to Azure Marketplace +** The task will be benefited by merging of ZFS support of man:makefs[8] and man:release[7] +*** https://reviews.freebsd.org/D23334 +*** https://reviews.freebsd.org/D34426 +*** https://reviews.freebsd.org/D35248 +* Building and publishing Hyper-V gen2 VM images to Azure Marketplace +** Blocked by https://bugs.freebsd.org/264267 + +The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft. + +Wei Hu and his colleagues in Microsoft are working on several tasks sponsored by Microsoft: + +* Fixing booting issue on Hyper-V gen2 VM in Azure +** https://bugs.freebsd.org/264267 +* Porting Hyper-V guest support to aarch64 + +Open tasks: + +* Update FreeBSD related doc at link:https://docs.microsoft.com[] +* Support FreeBSD in link:https://azure.microsoft.com/services/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 work by Wei Hu and others in Microsoft, and for resources for the rest +Sponsor: The FreeBSD Foundation for everything else diff --git a/website/content/en/status/report-2022-04-2022-06/blued.adoc b/website/content/en/status/report-2022-04-2022-06/blued.adoc new file mode 100644 index 0000000000..25fa04fa40 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/blued.adoc @@ -0,0 +1,54 @@ +=== New Bluetooth(R) configuration daemon: blued + +Links: + +link:https://git.lysator.liu.se/kempe/blued[blued git] URL: https://git.lysator.liu.se/kempe/blued[https://git.lysator.liu.se/kempe/blued] + +Contact: + +Mail: kempe@lysator.liu.se + +IRC: kempe@libera.chat + +==== Introduction + +The blued utility provides an IPC interface that lets an unprivileged user connect to and use Bluetooth devices in a user-friendly way and supports secure simple pairing (public-key cryptography and if the device allows it man-in-the-middle protection). + +==== What is blued? + +There are three parts to blued: a library, a daemon and a command line utility. +The library abstracts away bluetooth details, the daemon manages Bluetooth devices and the command line utility lets users list or scan for Bluetooth devices, pair with a device, or unpair from one. +The command line utility communicates with the daemon via a UNIX socket. + +Unlike bthidd and hcsecd, blued supports secure simple pairing and +provides an IPC. +To get a HID device to work, bthidd is still needed. +A script is provided to pair a Bluetooth device and appropriately configure bthidd so it just works and reconnects without user intervention. + +Once pairing has proven stable and bugs have been ironed out, the plan is to integrate bthidd with/into blued in some way to have HID devices automatically start functioning when paired without the use of an external script. +A long-term goal is to provide a graphical user interface that can list devices and provide a simple one-click setup to connect them. + +==== Installing and using blued v0.1 + +You need the optional `src` component installed in [.filename]#/etc/src#. + +First, make sure link:https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-bluetooth[you have working Bluetooth drivers loaded as explained in the FreeBSD handbook]. + +To test blued, fetch link:https://git.lysator.liu.se/kempe/blued/-/releases/v0.1[the blued v0.1 source code]. +Then compile it, patch your FreeBSD kernel with the patches in [.filename]#kernel_patches#, and recompile the `hci` module as explained in [.filename]#README#. + +I have primarily tested blued on FreeBSD 12.3, but my patches applied cleanly on 13.1 when I tested. +I am not supplying a port at the moment, but it is possible to run the software straight from the build directory or run "make install" that will install all needed files. +Both blued and bluecontrol use capsicum and blued can be configured to drop its root privileges. + +For more information, refer to the `Running blued` section of [.filename]#README#. + +==== Helping out + +===== Testing + +I have only tried this software with my own mouse and realise that a sample size of one single bluetooth device is pretty small. +I'm expecting issues and am greatly looking forward to feedback from others! + +In case of trouble, output from /var/log/debug.log and /var/log/messages as well as a traffic dump from "hcidump -x" while trying to pair will help with troubleshooting. + +===== Contributing + +If you want to get involved with the code and submit patches, you're welcome to link:https://git.lysator.liu.se/kempe/blued[visit the repository] on Lysator's Git. diff --git a/website/content/en/status/report-2022-04-2022-06/ci.adoc b/website/content/en/status/report-2022-04-2022-06/ci.adoc new file mode 100644 index 0000000000..f09b8f6b77 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/ci.adoc @@ -0,0 +1,53 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] + +link:https://wiki.freebsd.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.freebsd.org/Jenkins[https://wiki.freebsd.org/Jenkins] + +link:https://wiki.freebsd.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.freebsd.org/HostedCI[https://wiki.freebsd.org/HostedCI] + +link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.freebsd.org/3rdPartySoftwareCI[https://wiki.freebsd.org/3rdPartySoftwareCI] + +link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] + +link:https://lists.freebsd.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.freebsd.org/subscription/dev-ci[https://lists.freebsd.org/subscription/dev-ci] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +The FreeBSD CI team maintains the continuous integration system of the FreeBSD project. +The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results. +The artifacts from those builds are archived in the link:https://artifact.ci.FreeBSD.org[artifact server] for further testing and debugging needs. +The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure. + +During the second quarter of 2022, we continued working with the contributors and developers in the project to fulfill their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD. + +Important completed tasks: + +* Fixed the hardware failure issue of the CI cluster + +Work in progress tasks: + +* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) +* Designing and implementing use of CI cluster to build release artifacts as release engineering does +* Testing and merging pull requests in link:https://github.com/freebsd/freebsd-ci/pulls[the FreeBSD-ci repo] +* Simplifying CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository +* Updating documents on wiki + +Open or queued tasks: + +* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] +* Setting up public network access for the VM guest running tests +* Implementing use of bare-metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Adding more external toolchain related jobs +* Improving maturity of the hardware lab and adding more hardware for testing +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.freebsd.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort! + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-04-2022-06/clusteradm.adoc b/website/content/en/status/report-2022-04-2022-06/clusteradm.adoc new file mode 100644 index 0000000000..f775273c41 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/clusteradm.adoc @@ -0,0 +1,30 @@ +=== Cluster Administration Team + +Links: + +link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[https://www.freebsd.org/administration/#t-clusteradm] + +Contact: Cluster Administration Team <clusteradm@FreeBSD.org> + +FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications. +In this quarter, the team has worked on the following: + +* Installed a new mirror in Sydney, Australia hosted by IX Australia +* Fixed CI cluster hardware failure +* Set up a new internal monitoring system +* Regular cluster-wide software upgrades +* Regular support for FreeBSD.org user accounts + +Work in progress: + +* Work with the PowerPC team to improve the package builders, universal, and reference machines. +* Plan Hardware refresh, and fixing misc failures in each sites +* Improve the package building infrastructure +* Review the service jails and service administrators operation +* Working with doceng@ to improve deployment of https://www.freebsd.org and https://docs.freebsd.org +* Improve the web service architecture +* Improve the cluster backup plan +* Improve the log analysis system + +We are looking for an additional full mirror site (five servers) in Europe. +See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for our needs. +Offers of additional single-server mirrors (see link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny mirror]) are always welcome too, especially in Europe. diff --git a/website/content/en/status/report-2022-04-2022-06/core.adoc b/website/content/en/status/report-2022-04-2022-06/core.adoc new file mode 100644 index 0000000000..c1c5a75543 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/core.adoc @@ -0,0 +1,26 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team <core@FreeBSD.org> + +The FreeBSD Core Team is the governing body of FreeBSD. + +The twelfth FreeBSD Core Team was elected by active developers. +The core.12 members are: + +* Baptiste Daroussin (bapt, incumbent) +* Benedict Reuschling (bcr) +* Ed Maste (emaste, incumbent) +* Greg Lehey (grog) +* John Baldwin (jhb) +* Li-Wen Hsu (lwhsu) +* Emmanuel Vadot (manu) +* Tobias C. Berner (tcberner) +* Mateusz Piotrowski (0mp) + +On June 10th the outgoing core.11 and incoming core.12 teams held a handover meeting, +and the new Core Team was link:https://lists.freebsd.org/archives/freebsd-announce/2022-June/000034.html[announced on Jun 18]. + +The current Core Team secretary, Muhammad Moinur Rahman (bofh), will step down +after the appointment of a new Core Team secretary and handover tasks completes. + +In this quarter, src commit bits of Kornel Dulęba (kd) and Dmitry Salychev (dsl) have been approved. diff --git a/website/content/en/status/report-2022-04-2022-06/doceng.adoc b/website/content/en/status/report-2022-04-2022-06/doceng.adoc new file mode 100644 index 0000000000..7aafa770ac --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/doceng.adoc @@ -0,0 +1,79 @@ +//// +Quarter: 2nd quarter of 2022 +Prepared by: dbaio +Reviewed by: - +Last edit: $Date: 2022-07-02 22:35:43 -0300 (Sat, 02 Jul 2022) $ +Version: $Id: doceng-2022-2nd-quarter-status-report.adoc 241 2022-07-03 01:35:43Z dbaio $ +//// + +=== Documentation Engineering Team + +Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] + +Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] + +Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] + +Contact: FreeBSD Doceng Team <doceng@FreeBSD.org> + +The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. + +During the last quarter, Graham Perrin (grahamperrin@) and Pau Amma (pauamma@), were granted documentation commit bits. + +Several items are pending and in discussion: + +* Mirroring the Website and Documentation portal with the GeoDNS infrastructure of the project. +* How to handle Trademarks in the documentation. +* Remove outdated translations from the Website and Documentation portal. + +==== FreeBSD Translations on Weblate + +Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] + +Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] + +===== Q2 2022 Status + +* 12 languages +* 152 registered users (9 new users) + +===== Languages + +* Chinese (Simplified) (zh-cn) +* Chinese (Traditional) (zh-tw) +* Dutch (nl) +* French (fr) +* German (de) +* Indonesian (id) +* Italian (it) +* Norwegian (nb-no) +* Persian (fa-ir) +* Portuguese (pt-br) +* Spanish (es) +* Turkish (tr) + +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 Website Revamp - WebApps working group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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 will be 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. (_Work in progress_) + +. 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. (_Not started_) diff --git a/website/content/en/status/report-2022-04-2022-06/dpaa2.adoc b/website/content/en/status/report-2022-04-2022-06/dpaa2.adoc new file mode 100644 index 0000000000..5ebaacf990 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/dpaa2.adoc @@ -0,0 +1,36 @@ +=== NXP DPAA2 support + +Links + +link:https://github.com/mcusim/freebsd-src/commits/lx2160acex7-dev[Change history] + +link:https://github.com/mcusim/freebsd-src/tree/lx2160acex7-dev/sys/dev/dpaa2[Tree] + +Contact: Dmitry Salychev <dsl@FreeBSD.org> + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +Some of the NXP SoCs (LX2160A, LS1088A) are shipped with link:https://www.nxp.com/design/qoriq-developer-resources/second-generation-data-path-acceleration-architecture-dpaa2:DPAA2[DPAA2], the second generation of the data path acceleration architecture. +It allows to dynamically configure and wire packet processing "objects" (DPNI for a network interface, DPMAC for media access controller, etc.) together to form a network-on-a-chip. + +During the last quarter the driver started working well enough to be used on link:https://solidrun.atlassian.net/wiki/spaces/developer/pages/197494288/HoneyComb+LX2+ClearFog+CX+LX2+Quick+Start+Guide[SolidRun' Honeycomb LX2] (ACPI test platform) and Traverse Technologies has produced a link:https://forum.traverse.com.au/t/freebsd-preview-for-ten64/173[FreeBSD preview for (their) Ten64] (used as FDT test platform). + +The driver is still work-in-progress, but is getting close for a review to get the first version into the tree for everyone to benefit from it. + +WIP: + +* FDT MDIO support. FreeBSD currently lacks support for the SPF parts. + +* Driver resources de-allocation to unload dpaa2.ko properly. + +* link:https://github.com/mcusim/freebsd-src/issues[Bug fixes] and improvements. + +TODO: + +* CPU affinity for DPIOs and DPNIs. + +* Cached memory-backed software portals. + +* Bottlenecks mitigation. + +* Further parts (DPSW, DCE, etc.) supported by the hardware. + +Sponsor: Bare Enthusiasm :) + +Sponsor: Traverse Technologies (providing Ten64 HW for testing) diff --git a/website/content/en/status/report-2022-04-2022-06/ena.adoc b/website/content/en/status/report-2022-04-2022-06/ena.adoc new file mode 100644 index 0000000000..e0c9ca6dcb --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/ena.adoc @@ -0,0 +1,32 @@ +=== ENA FreeBSD Driver Update + +Links: + +link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst] + +Contact: Michal Krawczyk <mk@semihalf.com> + +Contact: Dawid Gorecki <dgr@semihalf.com> + +Contact: Marcin Wojtas <mw@FreeBSD.org> + +ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS). +The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used. + +Completed since the last update: + +* Upstream of the ENA driver v2.5.0, which included: + * Improvement to the reset routine handling, + * Extension of the timer service lifetime in order to be able to detect more + hardware failures, + * Fix logic for verifying the Tx request ID, + * Fix IPv6 L4 checksum offload handling for the Tx, + * Add NUMA awareness to the driver. +* Internal review of the upcoming ENA driver release (v2.6.0), including: + * Further reset handling improvements, + * Code cleanup and style fixes, + * Logging improvements, + * Fix to the retrieval of the ENI metrics. + +Work in progress: + +* Testing of the upcoming ENA driver release (v2.6.0). + +Sponsor: Amazon.com Inc diff --git a/website/content/en/status/report-2022-04-2022-06/freebsd-foundation.adoc b/website/content/en/status/report-2022-04-2022-06/freebsd-foundation.adoc new file mode 100644 index 0000000000..1ad6eb9179 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/freebsd-foundation.adoc @@ -0,0 +1,150 @@ +=== FreeBSD Foundation + +Links: + +link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] + +link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] + +link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] + +link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] + +link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] + +link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/] + +Contact: Deb Goodkin <deb@FreeBSDFoundation.org> + +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. +Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. +We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. +We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. + +==== Fundraising Efforts + +First, I’d like to send a big thank you to everyone who gave a financial contribution to our efforts. +We are 100% funded by your donations, so every contribution helps us continue to support FreeBSD in many ways, including some of the work funded and published in this status report. + +Our goal this year is to raise at a minimum $1,400,000 towards a spending budget of around $2,000,000. +As I write this report, we’ve brought in under $200,000 towards that goal. +So, we obviously need to step up our effort of fundraising. +It’s by far the hardest part of my job. +I’d much prefer talking to folks in our community on how we can help you, help create content to recruit more users and contributors to the Project, and understand challenges and painpoints that individuals and organizations have in using FreeBSD, so we can help improve those areas. +Asking for money is not on that list. + +We support FreeBSD in five main areas. +Software development is the largest area we fund with six software developers on staff who step in to implement new +features, support tier 1 platforms, review patches, and fix issues. +You can find out some of the work we did under OS Improvements in this report. +FreeBSD Advocacy is another area that we support to spread the word about FreeBSD at conferences, in presentations online and in-person, tutorials and how-to guides. +We purchase and support hardware for the FreeBSD infrastructure that supports the work going on in the Project. +Virtual and in-person events are organized by the Foundation to help connect and engage community members to share their knowledge and collaborate on projects. +Finally, we provide legal support to the Project when needed and protect the FreeBSD trademarks. + +If you haven't made a donation this year, please consider making one at https://freebsdfoundation.org/donate/. + +We also have a Partnership Program for larger commercial donors. +You can find out more at https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/ + +==== OS Improvements + +During the second quarter of 2022, 243 src, 62 ports, and 12 doc tree commits were made that identified The FreeBSD Foundation as a sponsor. +This represents 10.6, 0.7, and 4.5% of the total number of commits to each repository. + +==== Sponsored Work + +You can read about some of the Foundation-sponsored work in individual quarterly report entries. + +* Base System OpenSSH Update +* Ongoing work on LLDB multiprocess debugging support +* Wireless Status +* ZFS support in makefs + +Other ongoing sponsored work is described here. + +===== FreeBSD Wireguard Improvements + +The aim of the Wireguard project is to improve support for the FreeBSD Wireguard kernel module. +The work by John Baldwin involved adapting the module to use FreeBSD's OCF rather than Wireguard's internal implementations. +It also involved adding new ciphers and API support. +The latest upstream release incorporates this work. + +===== Openstack on FreeBSD + +OpenStack is a cloud system for different types of resources like virtual machines. +However, OpenStack only unofficially supports FreeBSD as a guest system. +That means users can spawn FreeBSD instances on the open cloud platform, but it is not currently possible run OpenStack on FreeBSD hosts. +The goal of this project is port OpenStack components so that FreeBSD can function as an OpenStack host. + +===== Bhyve Issue Support + +The Foundation recently signed a new contract for Bhyve support. +This contract will allow John Baldwin to dedicate time to Bhyve as issues arise, especially security issues. + +===== Handbook Improvement Exploration + +Under sponsorship from the Foundation, Pau Amma wrapped up a mini-project to explore how the Handbook can be improved. +A survey was sent out and the results will be shared soon. + +==== Continuous Integration and Quality Assurance + +The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. + +==== Supporting FreeBSD Infrastructure + +The Foundation provides hardware and support for the Project. +A new Australian mirror was brought online by the Cluster Administration team. +If you are a FreeBSD user in Oceania or southeast Asia, please let us know if download speeds for installer images and packages has improved. + +With your donations, the Foundation purchased new hardware to repair two PowerPC package builders, one for little endian packages (powerpc64le) and the second for big endian packages (powerpc64, powerpc). +The new hardware just arrived at the data center and will be installed soon. +Expect lots of PowerPC packages in the near future. + +==== FreeBSD Advocacy and Education + +Much of our effort is dedicated to Project advocacy. +This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. +The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. +Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. + +The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. +These events can be BSD-related, open source, or technology events geared towards underrepresented groups. +We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. +This all helps provide a healthy ecosystem. +We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. +We are continuing to attend virtual events and planning the June 2022 Developer Summit. +In addition to attending and planning virtual events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD. + +Check out some of the advocacy and education work we did last quarter: + +* Secured our booth and nonprofit sponsor status for All Things Open, October 30-November 2, 2022, Raleigh, NC. +* Finalized our booth and workshop at Scale 19x in Los Angeles, CA on July 28-30. + The FreeBSD workshop will be held Friday,Jul 29, 2022 and you can visit the Foundation at booth 502. +* Confirmed our Silver Sponsorship of EuroBSDcon 2022, September 15-18, Vienna, Austria +* Sponsored and helped organize the June 2022 FreeBSD Developer Summit, June 16-17, 2022. + Videos are available on the link:https://www.youtube.com/c/FreeBSDProject[FreeBSD Project YouTube channel]. +* Celebrated FreeBSD Day June 19, 2022 and throughout the following week. +* Secured our Friends level sponsorship of COSCUP, July30-31, Taiwan +* Published the link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-spring-2022-update/[FreeBSD Foundation Spring 2022 Update] +* New Blog Posts +** link:https://freebsdfoundation.org/blog/lets-talk-about-foundation-funding/[Let's Talk About Foundation Funding] +** link:https://freebsdfoundation.org/blog/new-board-member-interview-cat-allman/[New Board Member Interview: Cat Allman] +** link:https://freebsdfoundation.org/blog/welcome-freebsd-google-summer-of-code-participants/[Welcome FreeBSD Google Summer of Code Participants] +** link:https://freebsdfoundation.org/blog/freebsd-foundation-work-in-the-13-1-release/[FreeBSD Foundation Work in the 13.1 Release] +** link:https://freebsdfoundation.org/blog/foundation-elects-new-officers-interviews-outgoing-board-members/[Foundation Elects New Officers, Interviews Outgoing Board Members] +** link:https://freebsdfoundation.org/blog/help-us-celebrate-freebsd-day-all-week-long/[Help Us Celebrate FreeBSD Day All Week Long] +* New and Updated How-To and Quick Guides: +** link:https://freebsdfoundation.org/freebsd-project/resources/networking-basics-wifi-and-bluetooth/[Networking Basics: WiFi and Bluetooth] +** link:https://freebsdfoundation.org/freebsd-project/resources/audio-on-freebsd/[Audio on FreeBSD] +** link:https://freebsdfoundation.org/freebsd/how-to-guides/installing-freebsd-with-virtualbox-video-guide/[Installing FreeBSD with VirtualBox (Mac/Windows) - Video Guide] +** link:https://freebsdfoundation.org/freebsd-project/resources/an-introduction-to-the-freebsd-operating-system-video/[An Introduction to the FreeBSD Operating System - Video Guide] +** link:https://freebsdfoundation.org/freebsd-project/resources/installing-a-desktop-environment-on-freebsd-video-guide/[Installing a Desktop Environment on FreeBSD - Video Guide] +** link:https://freebsdfoundation.org/freebsd-project/resources/installing-a-port-on-freebsd-video-guide/[Installing a Port on FreeBSD - Video Guide] + +We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. +As we mentioned previously, the FreeBSD Journal is now a free publication. +Find out more and access the latest issues at link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDfoundation.org/journal/]. + +You can find out more about events we attended and upcoming events at link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDfoundation.org/news-and-events/]. + +==== 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://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2022-04-2022-06/gcc.adoc b/website/content/en/status/report-2022-04-2022-06/gcc.adoc new file mode 100644 index 0000000000..7099c4cc4a --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/gcc.adoc @@ -0,0 +1,28 @@ +=== GCC: updating GCC_DEFAULT and other improvements + +Links: + +link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] + +link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[https://gcc.gnu.org/gcc-11/] + +Contact: <toolchain@FreeBSD.org> + +Contact: Gerald Pfeifer <gerald@pfeifer.com> + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + +Contact: Piotr Kubaj <pkubaj@FreeBSD.org> + + * salvadore@ worked on the upgrade of GCC_DEFAULT in Mk/bsd.default-versions.mk from 10 to 11, opening bug reports based on antoine@'s exp-runs and fixing some: many thanks to all those that helped with this task. + The GCC_DEFAULT update from GCC 10 to GCC 11 has now been committed by gerald@ and happened in time for the next quarterly branch. + link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258378] + + * pkubaj@ switched GCC bootstrapping to use Link Time Optimization for GCC itself for GCC 11 and newer by introducing a new option enabled by default. + Building with LTO_BOOTSTRAP enabled requires significant amounts of memory and time. + How much resources are actually needed depends on your configuration (e.g. are you building from ports or with poudriere? What is your architecture?). + To give an idea, link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264949#c17[a user reported needing 5 GiB of tmpfs], while in link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254#c2[PR 265254] a need of about 130 GB of memory is estimated due to an excessive amount of processes spawning (see also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106328). + Consider disabling LTO_BOOTSTRAP in favor of STANDARD_BOOTSTRAP (or disabling BOOTSTRAP altogether) in case that is a problem. + + * pkubaj@ also added lang/gcc12 and lang/gcc13-devel ports and updated lang/gcc9 to 9.5. + + * Help is still needed with these three changes to work through with upstream GCC (requires src expertise, not ports): + + ** upstreaming lang/gcc11/patch-gets-no-more + ** upstreaming lang/gcc11/patch-arm-unwind-cxx-support + ** link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874] diff --git a/website/content/en/status/report-2022-04-2022-06/golang_riscv64.adoc b/website/content/en/status/report-2022-04-2022-06/golang_riscv64.adoc new file mode 100644 index 0000000000..2469697485 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/golang_riscv64.adoc @@ -0,0 +1,12 @@ +=== go on FreeBSD riscv64 + +Links: + +link:https://github.com/golang/go[golang Home Page] URL: link:https://github.com/golang/go[https://github.com/golang/go] + +link:https://github.com/MikaelUrankar/go/tree/freebsd_riscv64[FreeBSD riscv64 github repo] URL: link:https://github.com/MikaelUrankar/go/tree/freebsd_riscv64[https://github.com/MikaelUrankar/go/tree/freebsd_riscv64] + +link:https://github.com/golang/go/issues/53466[FreeBSD riscv64 golang issue] URL: link:https://github.com/golang/go/issues/53466[https://github.com/golang/go/issues/53466] + +Contact: Mikaël Urankar <mikael@FreeBSD.org> + +Contact: Dmitri Goutnik <dmgk@FreeBSD.org> + +Work has been done to port go on FreeBSD riscv64 which builds and passes all run.bash tests, including cgo (tested under QEMU and on Unmatched). +A pull request is created upstream and the proposal has been added to the active column of the proposals project and will be reviewed at the weekly proposal review meetings. diff --git a/website/content/en/status/report-2022-04-2022-06/if_ovpn.adoc b/website/content/en/status/report-2022-04-2022-06/if_ovpn.adoc new file mode 100644 index 0000000000..45186d75e1 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/if_ovpn.adoc @@ -0,0 +1,22 @@ +=== OpenVPN DCO + +Links: + +link:https://reviews.freebsd.org/D34340[D34340] URL: link:https://reviews.freebsd.org/D34340[D34340] + +link:https://community.openvpn.net/openvpn/wiki/DataChannelOffload[OpenVPN wiki] URL: https://community.openvpn.net/openvpn/wiki/DataChannelOffload[OpenVPN wiki] + +Contact: Kristof Provost <kp@FreeBSD.org> + +OpenVPN DCO (or Data Channel Offload) moves OpenVPN data packet processing into the kernel. + +Traditionally OpenVPN uses a tun(4) interface to transmit and receive packets. +In this setup received packets are received by the kernel, passed to the OpenVPN application for decryption, then passed back into the kernel for network stack processing. +This requires several transitions between kernel- and userspace, and naturally imposes a performance cost. + +The new if_ovpn OpenVPN DCO offload driver performs the encryption/decryption entirely within the kernel, improving performance. + +Initial performance testing shows throughput improved from around 660Mbit/s to around 2Gbit/s. + +The userspace OpenVPN code also requires modification to use the new if_ovpn offload driver. +This is expected to be part of a future 2.6.0 OpenVPN release. + +Sponsor: Rubicon Communications, LLC ("Netgate") diff --git a/website/content/en/status/report-2022-04-2022-06/igt-gpu-tools.adoc b/website/content/en/status/report-2022-04-2022-06/igt-gpu-tools.adoc new file mode 100644 index 0000000000..f14115788c --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/igt-gpu-tools.adoc @@ -0,0 +1,28 @@ +=== Feature Complete Port of Intel's igt-gpu-tools + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2022Projects/ImprovingTheLinuxKPICompatibilityLayerForTheFreeBSDGraphicsStack/[FreeBSD Wiki Project Page] URL: +link:https://wiki.freebsd.org/SummerOfCode2022Projects/ImprovingTheLinuxKPICompatibilityLayerForTheFreeBSDGraphicsStack/[https://wiki.freebsd.org/SummerOfCode2022Projects/ImprovingTheLinuxKPICompatibilityLayerForTheFreeBSDGraphicsStack] + +link:https://cdaemon.com/tags/gsoc2022/[Status Reports] URL: +link:https://cdaemon.com/tags/gsoc2022/[https://cdaemon.com/tags/gsoc2022] + +Contact: Jake Freeland <jfree@freebsd.org> + +Intel’s igt-gpu-tools serves as a generic testing suite for drm drivers on Linux. +The igt-gpu-tools suite is separated into tests and tools that target kms, memory management, and command submission. +The utility provides low-level reporting for transparent tracking of kernel changes and efficient debugging of modern drm drivers. + +Porting the project to FreeBSD could introduce greater stability in future releases of FreeBSD’s LinuxKPI-driven drm drivers. +A proper kms-driven testing suite could also increase code output and bring the FreeBSD desktop experience up to speed with the Linux codebase. + +The project officially started under FreeBSD's Google Summer of Code program on June 13, 2022. +My adapted code can compile with non-FreeBSD compatible snippets removed. +The plan is to reimplement these stripped components in a POSIX compliant fashion. + +Notable incompatible code includes: debugfs, libkmod, libprocps, Linux performance events, and Linux userfaultfd. +If you would like to assist in the porting of libkmod or libprocps into the ports tree, don't hesitate to contact me. + +When the FreeBSD compatible code is complete, I will run the modified igt tests using a host of graphics processors on FreeBSD 14.0-CURRENT. +If all is well, the project's diff will be submitted into the ports tree. + +Sponsor: FreeBSD Google Summer of Code diff --git a/website/content/en/status/report-2022-04-2022-06/intro.adoc b/website/content/en/status/report-2022-04-2022-06/intro.adoc new file mode 100644 index 0000000000..0a9a81e13a --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/intro.adoc @@ -0,0 +1,10 @@ +Here is the second quarterly report of 2022, with 26 reports included. + +This quarter the quarterly team managed to publish the report much faster and, hopefully, with much fewer mistakes. +If however you notice some errors, please report them so that we can correct them and also add some automatic checks in our tools to prevent them in the future and stay as efficient as possible in the publication process. + +We would also like to remind you that if for any reason you need more time to submit a quarterly report, the team will wait for you, but please warn us so that we are aware that some report is still missing. + +Many thanks to all those that have chosen to share their work with the FreeBSD community through the quarterly reports. + +Lorenzo Salvadore, on behalf of the status report team. diff --git a/website/content/en/status/report-2022-04-2022-06/kde.adoc b/website/content/en/status/report-2022-04-2022-06/kde.adoc new file mode 100644 index 0000000000..e460dbdafa --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/kde.adoc @@ -0,0 +1,53 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] + +link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project packages the software from the KDE Community, along with dependencies and related software, for the FreeBSD ports tree. +The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The KDE team (kde@) is part of desktop@ and x11@ as well, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine. +The notes below describe *mostly* ports for KDE, but also include items of import to the entire desktop stack. + +==== KDE Stack + +KDE Gear releases happen each quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release each month as well. +These (large) updates land shortly after their upstream release and are not listed separately. + +* *astro/kstars* latest release 3.5.9. +* *deskutils/grantleetheme* got an entry in UPDATING because of some unusual changes to the installed structure of the port. +* *deskutils/kalendar* joined the KDE Gear releases. +* *devel/okteta* updates to the binary (and octal and hexadecimal) data viewer and editor. +* *finance/kraft* needed specific build-fixes for newer KDE Frameworks. +* *games/gcompris-qt* expanded, new releases, and now supports more image formats (needed for some activities). +* *graphics/digikam* no longer needs a SQL server during the build. +* *graphics/krita* was updated to 5.0.5, likely the last 5.0 version. +* *math/labplot* has a huge number of new features in recent releases, well worth looking at if you need any kind of data-plotting. +* *net-im/ruqola* was updated. + This is a Qt-styled Rocket chat application. +* *www/falkon* joined the KDE Gear releases. + +==== Related Applications + +* *archivers/quazip* was updated. +* *deskutils/semantik* updated. +* *devel/py-qt5-pyqt* updated so that the port now pulls in DBus as well. + DBus is needed by nearly all desktop Qt applications, including those written in Python. +* *devel/qcoro* had build issues on certain FreeBSD versions, resolved. +* *devel/qtcreator* updated with each new release. +* *devel/qt5* had its infrastructure updated in ports so it does not produce strange error messages during de-installation. +* *graphics/ksnip* and related libraries updated to recent releases. +* Matrix clients Nheko (*net-im/nheko*) and Neochat (*net-im/neochat*) were updated following releases and library bumps. +* *x11/rsibreak* updated; helps prevent injury while writing long quarterly reports. + +==== Elsewhere + +* *devel/appstream* update supports more application-information. +* *devel/cmake* prefers generic python3 over versioned-python3, if users have multiple python3 ports *and* lang/python3 installed. +* *devel/dbus* updated. +* *graphics/poppler* updated several times. +* *graphics/ImageMagick* (both 6 and 7) updated several times. +* *multimedia/gstreamer* updated. diff --git a/website/content/en/status/report-2022-04-2022-06/linuxulator.adoc b/website/content/en/status/report-2022-04-2022-06/linuxulator.adoc new file mode 100644 index 0000000000..0d6d159d6b --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/linuxulator.adoc @@ -0,0 +1,23 @@ +=== Linux compatibility layer update + +Contact: Dmitry Chagin <dchagin@FreeBSD.org> + +Contact: Edward Tomasz Napierala <trasz@FreeBSD.org> + +The goal of this project is to improve FreeBSD's ability to execute unmodified Linux binaries. +Current support status of specific Linux applications is being tracked at the link:https://wiki.freebsd.org/LinuxApps[Linux app status Wiki page]. + +Implementation of the Y2k38 Linux project is mostly finished; all '*_time64()' system calls are committed. + +The state of the arm64 Linux emulation layer was brought to the state of the amd64 Linux emulation layer: +i.e., implemented the vDSO, machine dependent futexes, signals delivery. + +The thread affinity system calls were modified to implement Linux semantics. + +In total, over 50 bugs were fixed; glibc-2.35 tests suite reports less than 80 failed tests. + +All changes in the Linux emulation layer are merged to the stable/13 branch. + +Initial support for fancy Linux system call tracing has been added to libsysdecode and kdump. +There is ongoing work to make tracing more syscalls work. + +Sponsor: EPSRC (Edward’s work) diff --git a/website/content/en/status/report-2022-04-2022-06/lldb.adoc b/website/content/en/status/report-2022-04-2022-06/lldb.adoc new file mode 100644 index 0000000000..93a93ab088 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/lldb.adoc @@ -0,0 +1,24 @@ +=== Ongoing work on LLDB multiprocess debugging support + +Links: + +link:https://www.moritz.systems/blog/multiprocess-support-for-lldb/[Moritz Systems Project Description] URL: link:https://www.moritz.systems/blog/multiprocess-support-for-lldb/[https://www.moritz.systems/blog/multiprocess-support-for-lldb/] + +link:https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/[Progress Report 1] URL: link:https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/[https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/] + +Contact: Kamil Rytarowski <kamil@moritz.systems> + +Contact: Michał Górny <mgorny@moritz.systems> + +According to the upstream description, "LLDB is a next generation, high-performance debugger. It is built as a set of reusable components which highly leverage existing libraries in the larger LLVM Project, such as the Clang expression parser and LLVM disassembler." + +FreeBSD includes LLDB in the base system. +The previous sponsored projects improved LLDB, to make it a credible debugger for the base system, although it still has a few limitations compared to the contemporary versions of GNU GDB. +This project started in April 2022. +It aims to implement full support for debugging multiple processes simultaneously. + +At the start of the project, LLDB featured very limited support for multiprocess debugging. +The client featured support for debugging multiple independent processes simultaneously via maintaining multiple connections to different server instances. +Thanks to our earlier work, the server was able to process `fork(2)` and `vfork(2)` calls and either detach the newly forked child and continue tracing the parent process, or detach the parent and follow the child (equivalent to GDB's `follow-fork-mode` setting). + +Once the project is finished, LLDB will be able to trace an arbitrary number of forked processes simultaneously (equivalent to GDB's `detach-on-fork off`). +Full support for the multiprocess extension to the GDB Remote Serial Protocol will be implemented, as well as partial support for the non-stop extension that will enable multiple processes to be resumed and stopped independently. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-04-2022-06/makefs-zfs.adoc b/website/content/en/status/report-2022-04-2022-06/makefs-zfs.adoc new file mode 100644 index 0000000000..7c1cf09fd3 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/makefs-zfs.adoc @@ -0,0 +1,22 @@ +=== ZFS support in makefs(8) + +Links: + +link:https://lists.freebsd.org/archives/freebsd-hackers/2022-May/001128.html[Mailing list post] URL: link:https://lists.freebsd.org/archives/freebsd-hackers/2022-May/001128.html[https://lists.freebsd.org/archives/freebsd-hackers/2022-May/001128.html] + +link:https://reviews.freebsd.org/D35248[makefs(8) code review] URL: link:https://reviews.freebsd.org/D35248[link:https://reviews.freebsd.org/D35248] +link:https://reviews.freebsd.org/D34426[release(7) code review] URL: link:https://reviews.freebsd.org/D34426[link:https://reviews.freebsd.org/D34426] + +Contact: Mark Johnston <markj@FreeBSD.org> + +makefs(8) is a utility, originating in NetBSD, that creates file system images entirely in userspace. +It is a useful component of a toolchain to build virtual machine (VM) images since it does not require any special privileges, unlike the approach of formatting a character device, mounting the fresh file system, and copying files onto it. +Moreover, makefs can create reproducible images and aims to minimize resource consumption. +Currently, FreeBSD's makefs can build UFS, cd9660, and msdos (FAT) file system images. + +Recent work enables the creation of ZFS images by makefs. +This makes it easier to build ZFS-based VM images. +makefs' ZFS support includes the ability to create multiple datasets, with each mapped to a directory in the input file hierarchy. +Many ZFS features are not supported however, as the implementation provides only what is needed to get reproducible root pools. + +Follow-up work enables the creation of ZFS-based VM and cloud images by the release(7) framework, using this new makefs extension. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-04-2022-06/openssh.adoc b/website/content/en/status/report-2022-04-2022-06/openssh.adoc new file mode 100644 index 0000000000..75439f4c9b --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/openssh.adoc @@ -0,0 +1,19 @@ +=== Base System OpenSSH Update + +Links: + +link:https://www.openssh.com/[OpenSSH] URL: link:https://www.openssh.com/[https://www.openssh.com/] + +link:https://www.openssh.com/txt/release-8.9[OpenSSH 8.9 release notes] URL:https://www.openssh.com/txt/release-8.9[https://www.openssh.com/txt/release-8.9] + +link:https://www.openssh.com/txt/release-9.0[OpenSSH 9.0 release notes] URL:https://www.openssh.com/txt/release-9.0[https://www.openssh.com/txt/release-9.0] + +Contact: Ed Maste <emaste@freebsd.org> + +OpenSSH, a suite of remote login and file transfer tools, was updated from version 8.8p1 to 9.0p1 in the FreeBSD base system. + +It has not yet been merged to the stable/13 and stable/12 branches. +I anticipate doing so in July. + +*NOTE*: +OpenSSH 9.0p1 switches scp(1) from using the legacy scp/rcp protocol to using the SFTP protocol by default. +The `-O` flag is available to use the previous protocol instead. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-04-2022-06/pantheon.adoc b/website/content/en/status/report-2022-04-2022-06/pantheon.adoc new file mode 100644 index 0000000000..927e225483 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/pantheon.adoc @@ -0,0 +1,26 @@ +=== Pantheon desktop on FreeBSD + +Links: + +link:https://elementary.io/[elementary OS] URL: link:https://elementary.io/[https://elementary.io] + +link:https://codeberg.org/olivierd/freebsd-ports-elementary[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-elementary[https://codeberg.org/olivierd/freebsd-ports-elementary] + + +Contact: Olivier Duchateau <duchateau.olivier@gmail.com> + +The Pantheon desktop environment is designed for elementary OS. +It builds on GNOME technologies (such as Mutter, GNOME Shell, GTK 3 and 4) and it is written in Vala. + +The goal is to have a new desktop for users. +Some features are not well supported, but we can have full session. + +The repository contains Mk/Uses framework `elementary.mk`, official applications, and curated ports which depend of `x11-toolkits/granite` (total of 56 new ports). + +I have submitted several patches, especially: + +* `x11-toolkits/granite7` +* `devel/libgee` update to 0.20.5 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262893[bug #262893] +* `sysutils/bamf` update to 0.5.6 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264203[bug #264203] + +==== Open tasks + +* Add support of user settings (it is very Ubuntu-centric) +* Finish porting wingpanel-indicator-power (power management) diff --git a/website/content/en/status/report-2022-04-2022-06/pf.adoc b/website/content/en/status/report-2022-04-2022-06/pf.adoc new file mode 100644 index 0000000000..e2d14b25d6 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/pf.adoc @@ -0,0 +1,32 @@ +=== pf status update + +Contact: Kristof Provost <kp@FreeBSD.org> + +Contact: Reid Linnemann <rlinnemann@netgate.com> + +==== Ethernet + +pf recently grew support for filtering on Ethernet layer. +See the 2021q2 pf_ethernet report. + +Since then the Ethernet layer filtering has been extended with: + + * anchor support + * ability to look into the layer 3 header, for matching with source/destination IP(v4/v6) addresses + * table support for IP address matching + * direct dispatch to dummynet + * pass Ethernet layer packets directly to dummynet, rather than tagging the packets and relying on layer 3 to handle dummynet + +==== Dummynet + +pf recently started being able to use dummynet for packet scheduling. +This support has been extended and improved, and is now believed to be ready for production. + +One notable fix is that reply-to/route-to'd traffic is now subject to dummynet scheduling as well. + +==== Last match timestamp + +pf now tracks when a rule was last matched. +Similar to ipfw rule timestamps, these timestamps internally are uint32_t snaps of the system "wall time" clock in seconds. (See time(9).) +The timestamp is CPU local and updated each time a rule or a state is matched. + +Sponsor: Rubicon Communications, LLC ("Netgate") diff --git a/website/content/en/status/report-2022-04-2022-06/portmgr.adoc b/website/content/en/status/report-2022-04-2022-06/portmgr.adoc new file mode 100644 index 0000000000..ff41db260c --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/portmgr.adoc @@ -0,0 +1,37 @@ +=== Ports Collection + +Links: + +link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[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[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] + +link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] + +link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[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/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/] + +Contact: René Ladan <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +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. + +The number of ports is slightly above 30,000. +The last quarter saw 9,137 commits by 151 committers on the "main" and 589 commits by 61 committers on the "2022Q2" branch. +At the time of writing, there are 2,700 open ports PRs of which 682 are unassigned. +Compared to the previous quarter, there was a slight decrease in commit activity and a constant number of PRs. +Note: Freshports appears to overcount substantially. +This quarter's ports count was derived differently and is not comparable with the previous quarter's. + +During the last quarter, portmgr +welcomed back salvadore@ but also said goodbye to seven ports committers due to lack of activity. + +In its bi-weekly meetings, portmgr discussed the following topics: +* the future of ca_root_nss +* feasibility of the base system providing certain .pc files +* ways to deal with incompatibilities in kernel module ports on minor version upgrades of the base system + +Following a discussion among developers, portmgr decided to grant all documentation and source +committers approval to fix any documentation-related error in the Ports Tree which does not affect its functionality. + +The following changes were made to the Ports Tree during 2022q2: +* pkg got updated to version 1.18.3, Firefox to version 102.0 and Chromium to version 103.0.50060.53 +* Default versions of GCC, Lazarus, Python and Ruby got updated to respectively 11 (powerpcspe keeps version 8), 2.2.2, 3.9, and 3.0. +* Two new USES were added, gstreamer to support ports based on GStreamer plugins and pytest to help testing with pytest. diff --git a/website/content/en/status/report-2022-04-2022-06/releng.adoc b/website/content/en/status/report-2022-04-2022-06/releng.adoc new file mode 100644 index 0000000000..c0952e35e0 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/releng.adoc @@ -0,0 +1,23 @@ +=== FreeBSD Release Engineering Team + +Links: + +link:https://www.freebsd.org/releases/13.1R/schedule/[FreeBSD 13.1-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.1R/schedule/[https://www.freebsd.org/releases/13.1R/schedule/] + +link:https://www.freebsd.org/releases/13.1R/announce/[FreeBSD 13.1-RELEASE announcement] URL: link:https://www.freebsd.org/releases/13.1R/announce/[https://www.freebsd.org/releases/13.1R/announce/] + +link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[https://download.freebsd.org/releases/ISO-IMAGES/] + +link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[https://download.freebsd.org/snapshots/ISO-IMAGES/] + + +Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org> + +The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. + +During the second quarter of 2022, the Release Engineering Team completed work on the 13.1-RELEASE cycle. +This is the second release from the stable/13 branch. +Throughout the release cycle, three BETA builds and six RC (release candidate) builds have occurred, moving the final release date from April 21, 2022 to May 16, 2022, as some last-minute issues were identified. + +We thank all FreeBSD developers and contributors for testing the 13.1-RELEASE, reporting problems, and being diligent with proposed changes as the cycle progressed. + +Additionally throughout the quarter, several development snapshots builds were released for the *main*, *stable/13*, and *stable/12* branches. + +Sponsor: Rubicon Communications, LLC ("Netgate") +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-04-2022-06/shp_rand.adoc b/website/content/en/status/report-2022-04-2022-06/shp_rand.adoc new file mode 100644 index 0000000000..96d351c478 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/shp_rand.adoc @@ -0,0 +1,17 @@ +=== Shared page address randomization + +Links: + +link:https://reviews.freebsd.org/D35392[D35392] link:https://reviews.freebsd.org/D35393[D35393] +link:https://reviews.freebsd.org/D35349[D35349] + +Contact: Kornel Duleba <mindal@semihalf.com> + +Contact: Marcin Wojtas <mw@FreeBSD.org> + +The shared page is an R/X page that is mapped into each process by the image activator. +It stores the signal trampoline, as well as other metadata e.g. information needed to implement user space timecounters. +Previously it was mapped at the top of the process virtual address space. +With the described changes its address will be randomized. +We plan to turn the feature on by default for 64bit binaries, across all architectures. +Currently the patches are under review and await approval. + +Sponsor: Stormshield diff --git a/website/content/en/status/report-2022-04-2022-06/superpages.adoc b/website/content/en/status/report-2022-04-2022-06/superpages.adoc new file mode 100644 index 0000000000..c6e4d3783a --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/superpages.adoc @@ -0,0 +1,19 @@ +=== Medium-sized superpages on arm64 and beyond + +Contact: Eliot H. Solomon <ehs3@rice.edu> + +Contact: Alan L. Cox <alc@rice.edu> + + +The 64-bit ARM architecture's page table descriptor format contains a flag called the Contiguous bit. +This tells the MMU that it can cache an aligned, physically contiguous group of 16 page table entries which have identical permissions and attributes using only 1 TLB entry. + +The Contiguous bit, as well as the conceptually similar Svnapot extension to the RISC-V architecture, allows for the use of 64 KiB superpages. +These medium-sized superpages can bring to smaller memory objects the address-translation speedup typically associated with more traditional 2 MiB superpages. + +This project focuses on bringing support for medium-sized superpages to FreeBSD. +So far, we have modified the arm64 pmap code to automatically utilize 64 KiB superpages by detecting physically contiguous page table entries and promoting them using the Contiguous bit. +Now, we are working to adapt the kernel's superpage reservation module to support 64 KiB reservations in addition to the current 2 MiB ones. +Adding medium-sized reservations will allow the virtual memory system to explicitly allocate pieces of memory which fit the requirements for superpage promotion, rather than just hoping that they occur by chance. + +Our goal is to accomplish this in a general way that makes it possible to specify multiple arbitrary power-of-two reservation sizes, making it easier to take advantage of hardware features on other architectures like Ryzen's PTE Coalescing, which transparently merges groups of 4 KiB page table entries into medium-sized superpages. + +Sponsor: Department of Computer Science, Rice University diff --git a/website/content/en/status/report-2022-04-2022-06/valgrind.adoc b/website/content/en/status/report-2022-04-2022-06/valgrind.adoc new file mode 100644 index 0000000000..b14521de2a --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/valgrind.adoc @@ -0,0 +1,46 @@ +=== Valgrind - Numerous bugfixes and updates for 13.1 / 14.0 + +Links + +link:https://www.valgrind.org/[Valgrind Home Page] URL: +link:https://www.valgrind.org/[https://www.valgrind.org/] + +link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] +URL: +link:https://www.valgrind.org/docs/manual/dist.news.html[https://www.valgrind.org/docs/manual/dist.news.html] + +Contact: Paul Floyd <pjfloyd@wanadoo.fr> + +A quite significant number of bug fixes have been made to Valgrind on FreeBSD over the past few months. +In particular, the i386 version has largely 'caught up' with its bigger brother amd64. + +The devel/valgrind-devel port has been bumped up to 3.20.0.g20220612,1 which includes all of the following changes. +If you use Valgrind regularly please switch to valgrind-devel. + +Here is a list of changes since the release of Valgrind 3.19.0 (which is the version available with the devel/valgrind port). + +* incorrect signal resumption if a signal arrives when Valgrind is saving the carry flag for a syscall +* fixed reading DWARF debuginfo from PT_LOADs generated by lld post version 9, which splits the RW segment into two parts, this affects mainly shared libraries (.so files) +* on i386 implement correctly the management of thread GDTs which was limiting applications to only ever creating 8192 threads +* make the first page of the 'brk' invalid for addressing +* analysis and cleanup of the regression test suite and in particular tweak the i386 leak tests to not detect possible leaks due to left over pointers in ECX. +* make coredumps readable by lldb +* improve the setting of errno by C allocating functions +* fix building of Valgrind with llvm-devel (15.0.0) + +For FreeBSD 13.1 / 14.0 there are + +* syscall wrappers for funlinkat, copy_file_range, swapoff, shm_open2 +* add K_INFO handling to fcntl +* add handling for new auxv entries +* added some default suppressions for DRD and Helgrind + +There is now an initial version of vgdb invoker support - this allows vgdb to use ptrace to force valgrind to poll for gdb commands. +This is not yet available in the ports versions. + +That does not leave much in the way of outstanding issues. +I expect that 14.0 and newer versions of llvm will keep on requiring support. +Apart from that there is + +* some small problems with error messages getting the correct source +information +* better core dumps (low priority) +* TLS (thread local storage) handling for Helgrind (difficult if not impossible) diff --git a/website/content/en/status/report-2022-04-2022-06/wifi.adoc b/website/content/en/status/report-2022-04-2022-06/wifi.adoc new file mode 100644 index 0000000000..6d70d54153 --- /dev/null +++ b/website/content/en/status/report-2022-04-2022-06/wifi.adoc @@ -0,0 +1,35 @@ +=== Wireless updates + +Links: + +link:https://wiki.freebsd.org/WiFi/Iwlwifi[Intel iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi] +link:https://wiki.freebsd.org/WiFi/Rtw88[Realtek rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88] +link:https://wiki.freebsd.org/WiFi/Rtw89[Realtek rtw89 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw89[https://wiki.freebsd.org/WiFi/Rtw89] + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +The overall project aims to bring support for newer chipsets to FreeBSD currently using LinuxKPI compat code backed by native net80211 and kernel code. +In addition the aim is to continue work towards supporting newer wireless standards. +During the second quarter 40 commits went into FreeBSD CURRENT. +With more users trying multiple drivers support time has also gone up. + +An earlier version of the Intel iwlwifi-derived wireless driver shipped in 13.1-RELEASE bringing this work into a first FreeBSD release. +The iwlwifi driver and firmware were since updated in CURRENT and stable/13 again as part of ongoing development. +Changes in files shared with the upstream Intel Linux version of the driver are now less than 400 lines. +Lately a longer-standing problem for older chipsets was (hopefully) solved allowing iwm(4)-supported cards to work with iwlwifi(4) again after almost three months. +The main focus for the project until the end of the year will most exclusively be getting us to contemporary speeds. + +On April 1st, using the same LinuxKPI infrastructure built mostly with the iwlwifi work, Realtek's rtw88(4) driver got committed into CURRENT. +Due to an issue with DMA the next weeks a workaround was developed and put into the tree so users no longer have to patch the kernel. +The driver still needs a tunable set in loader.conf for machines with more than 4GB of physical memory. +This tunable allowed the driver to be merged to stable/13 in June followed by further updates in CURRENT and stable/13. +As the USB parts for rtw88 based chipsets are prepared to be included in Linux, work has started (needing more time) to prepare FreeBSD to be able to support the USB parts as well. + +During the last months Realtek's rtw89 has already been compiling and remains a work in progress to run stably and associate before it can be enabled in CURRENT. + +Thanks to all the users for testing and reporting back, patiently waiting for the next update, bugfix, or just a reply from me. +It is a great pleasure to work with you! +Keep sending the bug reports to me, but remember that your thanks should go to the FreeBSD Foundation for making most of this possible. + +For the latest state of the development, please follow the freebsd-wireless mailing list and check the wiki pages. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-07-2022-09/_index.adoc b/website/content/en/status/report-2022-07-2022-09/_index.adoc new file mode 100644 index 0000000000..75c2b97022 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/_index.adoc @@ -0,0 +1,168 @@ +--- +title: "FreeBSD Quarterly Status Report Third Quarter 2022" +sidenav: about +--- + += Introduction +:doctype: article +:toc: macro +:toclevels: 2 +:icons: font +:!sectnums: +:source-highlighter: rouge +:experimental: +:reports-path: content/en/status/report-2022-07-2022-09 +:lang: en + +include::shared/{lang}/urls.adoc[] + +include::{reports-path}/intro.adoc[] + +''' + +toc::[] + +''' + +[[FreeBSD-Team-Reports]] +== FreeBSD Team Reports + +Entries from the various official and semi-official teams, as found in the +link:../../administration/[Administration Page]. + +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 that span multiple categories, from the kernel and userspace to the +Ports Collection or external projects. + +include::{reports-path}/openstack-on-freebsd.adoc[] + +''' + +include::{reports-path}/cloud-init.adoc[] + +''' + +[[userland]] +== Userland + +Changes affecting the base system and programs in it. + +include::{reports-path}/bhyve-debug-server-enhancements.adoc[] + +''' + +include::{reports-path}/pjdfstest.adoc[] + +''' + +include::{reports-path}/lldb.adoc[] + +''' + +include::{reports-path}/kinst.adoc[] + +''' + +[[kernel]] +== Kernel + +Updates to kernel subsystems/features, driver support, filesystems, and more. + +include::{reports-path}/ena.adoc[] + +''' + +include::{reports-path}/wtap.adoc[] + +''' + +include::{reports-path}/iwlwifi.adoc[] + +''' + +include::{reports-path}/wifi.adoc[] + +''' + +include::{reports-path}/ufs_snapshots.adoc[] + +''' + +[[architectures]] +== Architectures + +Updating platform-specific features and bringing in support for the new hardware +platform. + +include::{reports-path}/firecracker.adoc[] + +''' + +[[documentation]] +== Documentation + +Noteworthy changes in the documentation tree, manual pages, or new external +books/documents. + +include::{reports-path}/doceng.adoc[] + +''' + +[[ports]] +== Ports + +Changes affecting the Ports Collection, whether sweeping changes that touch most +of the tree, or individual ports themselves. + +include::{reports-path}/calendar-data.adoc[] + +''' + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/gcc.adoc[] + +''' + +include::{reports-path}/lsof.adoc[] + +''' + +[[third-Party-Projects]] +== Third Party Projects + +Many projects build upon FreeBSD or incorporate components of FreeBSD into their +project. As these projects may be of interest to the broader FreeBSD community, +we sometimes include brief updates submitted by these projects in our quarterly +report. The FreeBSD project makes no representation as to the accuracy or +veracity of any claims in these submissions. + +include::{reports-path}/pot.adoc[] diff --git a/website/content/en/status/report-2022-07-2022-09/bhyve-debug-server-enhancements.adoc b/website/content/en/status/report-2022-07-2022-09/bhyve-debug-server-enhancements.adoc new file mode 100644 index 0000000000..bc3f14f68f --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/bhyve-debug-server-enhancements.adoc @@ -0,0 +1,24 @@ +=== bhyve debug server enhancements + +Links: + +link: https://wiki.freebsd.org/SummerOfCode2022Projects/BhyveDebugServerEnhancements[Wiki project page] + +link: https://reviews.freebsd.org/D35826[Differential] + +Contact: Bojan Novković <bojan.novkovic@kset.org> + +The goal of this project was to enhance the functionality of bhyve’s debug server. +Several existing features related to single-stepping are tied to Intel-specific VM mechanisms, which severely impairs bhyve’s debugging functionality on other x86 platforms. +The first goal dealt with extending single-stepping support to AMD hosts. +The second goal was to add support for hardware watchpoints using the guest OS's hardware debugging registers. + +The project was carried out under Google's Summer of Code program and was finished around the end of July. +The project's wiki also contains detailed documentation regarding several implemented mechanisms. + +The changes can be summarized as follows: + +* Support for placing software breakpoints inside virtual machines on AMD platforms, +* Support for single-stepping virtual machines on AMD platforms, +* Support for placing hardware watchpoints inside virtual machines on Intel and AMD platforms. + +Any feedback, comments and discussions are welcome and would be greatly appreciated. + +Sponsor: Google Summer of Code diff --git a/website/content/en/status/report-2022-07-2022-09/calendar-data.adoc b/website/content/en/status/report-2022-07-2022-09/calendar-data.adoc new file mode 100644 index 0000000000..7800956771 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/calendar-data.adoc @@ -0,0 +1,20 @@ +=== Calendar-data: License added + +Links + +link:https://github.com/freebsd/calendar-data[GitHub calendar-data repository] URL: +link:https://github.com/freebsd/calendar-data[https://github.com/freebsd/calendar-data] + + +Contact: Stefan Eßer <se@FreeBSD.org> + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + +Contact: Warner Losh <imp@FreeBSD.org> + +The port deskutils/calendar-data contains calendar files for the BSD calendar program and is maintained by se@. +The data for this port lives in a link:https://github.com/freebsd/calendar-data[GitHub repository], which at the moment is maintained mainly by salvadore@. + +About two years ago, the calendar files in the base repository were removed from there and a new repository was created on GitHub; see also this link:https://reviews.freebsd.org/D26883[Phabricator review about the creation of the associated port]. +This improvement allows calendar files to be updated independently from the base system. + +Unfortunately, when the repository was created, it was forgotten to add a license to it. +The issue has been solved this quarter with this link:https://github.com/freebsd/calendar-data/pull/9[pull request] submitted by salvadore@ and merged by imp@. +Since the data originally came from the src repository, the same licence applies. +If in the past you have contributed to the calendar files with different licensing assumptions, please inform us so that we can license your contributions accordingly or remove them. diff --git a/website/content/en/status/report-2022-07-2022-09/ci.adoc b/website/content/en/status/report-2022-07-2022-09/ci.adoc new file mode 100644 index 0000000000..57957443a2 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/ci.adoc @@ -0,0 +1,55 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] + +link:https://wiki.freebsd.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.freebsd.org/Jenkins[https://wiki.freebsd.org/Jenkins] + +link:https://wiki.freebsd.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.freebsd.org/HostedCI[https://wiki.freebsd.org/HostedCI] + +link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.freebsd.org/3rdPartySoftwareCI[https://wiki.freebsd.org/3rdPartySoftwareCI] + +link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] + +link:https://lists.freebsd.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.freebsd.org/subscription/dev-ci[https://lists.freebsd.org/subscription/dev-ci] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +The FreeBSD CI team maintains the continuous integration system of the FreeBSD project. +The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results. +The artifacts from those builds are archived in the link:https://artifact.ci.FreeBSD.org[artifact server] for further testing and debugging needs. +The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure. + +During the third quarter of 2022, we continued working with the contributors and developers in the project to fulfill their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD. + +Important completed tasks: + +* Expand the artifact storage space for adding more types of artifacts and longer retention period. +* Present Testing/CI Status Update in link:https://wiki.freebsd.org/DevSummit/202209[EuroBSDcon 2022 Developer Summit] +* Add link:https://ci.freebsd.org/job/FreeBSD-main-powerpc-images/[main-powerpc-images] and link:https://ci.freebsd.org/job/FreeBSD-main-powerpcspe-images/[main-powerpcspe-images] + +Work in progress tasks: + +* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) +* Designing and implementing use of CI cluster to build release artifacts as release engineering does +* Testing and merging pull requests in link:https://github.com/freebsd/freebsd-ci/pulls[the FreeBSD-ci repo] +* Simplifying CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository +* Updating documents on wiki + +Open or queued tasks: + +* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] +* Setting up public network access for the VM guest running tests +* Implementing use of bare-metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Adding more external toolchain related jobs +* Improving maturity of the hardware lab and adding more hardware for testing +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.freebsd.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.freebsd.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort! + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-07-2022-09/cloud-init.adoc b/website/content/en/status/report-2022-07-2022-09/cloud-init.adoc new file mode 100644 index 0000000000..0a9236bba9 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/cloud-init.adoc @@ -0,0 +1,22 @@ +=== FreeBSD as a Tier 1 cloud-init Platform + +Links: + +link:https://https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[https://cloud-init.io/] + +link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[https://cloudinit.readthedocs.io/en/latest/] + +link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[cloud-init ongoing refactorization] URL: link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst] + + +Contact: Mina Galić <me+FreeBSD@igalic.co> + +cloud-init is the standard way of provisioning servers in the cloud. +Unfortunately, cloud-init support for operating systems other than Linux is rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform. +To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support. +The broader plan is to lift support across all BSDs. + +The project deliverables include completing an extraction of certain networking classes, implementing man:ifconfig[8] and man:login.conf[5] parsers, implementing IPv6 configuration, creating man:devd.conf[5] rules for Azure, and link:{handbook}[FreeBSD Handbook] documentation about productionizing FreeBSD. + +On the way there, any BSD-related bugs found in modules and documentation will also be fixed. + +People interested in helping with the project can help with testing new features and fixes through package:net/cloud-init-devel[], which will be updated on a weekly basis. +Further, people with access to, and experience with, OpenBSD and NetBSD are also highly welcome to help. + +Sponsor: The FreeBSD Foundation + diff --git a/website/content/en/status/report-2022-07-2022-09/clusteradm.adoc b/website/content/en/status/report-2022-07-2022-09/clusteradm.adoc new file mode 100644 index 0000000000..207b0c47e9 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/clusteradm.adoc @@ -0,0 +1,35 @@ +=== Cluster Administration Team + +Links: + +link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[https://www.freebsd.org/administration/#t-clusteradm] + +Contact: Cluster Administration Team <clusteradm@FreeBSD.org> + +FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications. +In this quarter, the team has worked on the following: + +* Added additional storage to the CI system. +It will help store more artifacts. +* link:https://www.vuxml.org/freebsd/index.html[VuXML] deployed in all official mirrors. +It speeds up the `pkg audit` functionality. +* A new (and additional) monitoring system is in place. +* A few old and faulty machines were decommissioned. +* Moved several services to newer hardware. +* Regular cluster-wide software upgrades +* Regular support for FreeBSD.org user accounts +* Regular disk and parts support (and replacement) for all physical hosts and mirrors. + +Work in progress: + +* git infra: Add `--filter` support. +* Work with the PowerPC team to improve the package builders, universal, and reference machines. +* Site audit at our primary site: inventory of spares and other miscellanea occupying space in our cabinets. +* Discussions with link:https://www.juniper.net/[Juniper] about a donation of new switches for our primary site. +* Plan for a large scale network upgrade at our primary site. +* Cluster refresh (more extended project). +Most cluster machines are running FreeBSD `13-STABLE` or `14-CURRENT` as of 2022-09-30. +Only a handful of machines are still on FreeBSD `12-STABLE`. + +We are looking for an additional full mirror site (five servers) in Europe. +See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for our needs. +Offers of link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[additional single-server mirrors] are always welcome too, especially in Europe. diff --git a/website/content/en/status/report-2022-07-2022-09/core.adoc b/website/content/en/status/report-2022-07-2022-09/core.adoc new file mode 100644 index 0000000000..d09d031861 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/core.adoc @@ -0,0 +1,37 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team <core@FreeBSD.org> + +The FreeBSD Core Team is the governing body of FreeBSD. + +==== Completed Items + +===== New Core Team Secretary + +All members of the Core Team express publicly their gratitude to Muhammad Moinur Rahman (bofh) for serving as the Core Team Secretary for the past two years. + +The Core Team approved Sergio Carlavilla (carlavilla) as the new Core Team secretary. + +===== Procedure to handle GDPR deletion request + +The Core Team has reviewed the procedure to handle GDPR deletions requests with help from Foundation lawysers. +The document is currently being written and will be published after completion. + +===== New Privacy Policy + +The Core Team is working closely with the FreeBSD Foundation to update the Privacy Policy to properly align with current laws and practices found on similar websites such as ours. + +===== Bruce Evans memorial plaque + +The Core Team unanimously votes to allow the memorial plaque for Bruce Evans mentioning him as co-founder of FreeBSD. + +===== EuroBSDCon core team office hour + +On Friday, September 16, the new Core Team presented at link:https://wiki.freebsd.org/DevSummit/202209[EuroBSDcon 2022 Developer Summit]. +The Core Team introduced themselves and talked a bit about their plans for this term. +There were discussions, Q & A, and suggestions from the attendees about the details. + +==== Commit bits + +Core approved reactivating the source commit bit for Konrad Witaszczyk (def@). +Right now Konrad is working at Cambridge University, where he is responsible for developing CheriBSD. diff --git a/website/content/en/status/report-2022-07-2022-09/doceng.adoc b/website/content/en/status/report-2022-07-2022-09/doceng.adoc new file mode 100644 index 0000000000..25b1437bc6 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/doceng.adoc @@ -0,0 +1,110 @@ +//// +Quarter: 3rd quarter of 2022 +Prepared by: fernape +Reviewed by: gjb, dbaio +Last edit: $Date: 2022-09-24 14:24:33 +0200 (Sat, 24 Sep 2022) $ +Version: $Id: doceng-2022-3rd-quarter-status-report.adoc 272 2022-09-24 12:24:33Z dbaio $ +//// + +=== Documentation Engineering Team + +Link: link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] + +Link: link:https://docs.freebsd.org/en/books/fdp-primer/[FreeBSD Documentation Project Primer for New Contributors] + +Link: link:https://www.freebsd.org/administration/#t-doceng[Documentation Engineering Team] + +Contact: FreeBSD Doceng Team <doceng@FreeBSD.org> + +The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. + +During the last quarter: + +* 0mp@ stepped down as Doceng's Secretary, fernape@ joined as the new Secretary. + Doceng would like to thank 0mp@ for his service. + +* eadler@'s doc bit was taken in for safekeeping per his request. + +* A git commit message template was added for the doc repository. + +Items pending and in the discussion: + +* Remove outdated translations from the Website and Documentation portal. + +==== FreeBSD's Documentation Project Primer + +The FDP was link:https://cgit.freebsd.org/doc/commit/?id=311e6e3d5e7476cda9107107d779a145241f11fa[expanded with information on trademark handling]. + +==== Porter's Handbook: + +* The documentation on link:https://cgit.freebsd.org/doc/commit/?id=08dd1185b44003d698b267851f704820c9d492c6[porting Haskell programs was updated]. + +* The link:https://reviews.freebsd.org/D36369[move of WWW from pkg-descr to Makefile was documented]. + +* link:https://cgit.freebsd.org/doc/commit/?id=78deabd3b1b2aabe9960c24d0c7e8df3fb57e607[Qt 6-related documentation has been added] following the import of the library in the ports framework. + +==== FreeBSD Translations on Weblate + +Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] + +Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] + +===== Q3 2022 Status + +* 12 languages +* 148 registered users + + - Gasol Wu joined the Chinese translation team. + - Alvaro Felipe Calle joined the Spanish translation team. + +===== Languages + +* Chinese (Simplified) (zh-cn) (progress: 8%) +* Chinese (Traditional) (zh-tw) (progress: 4%) +* Dutch (nl) (progress: 1%) +* French (fr) (progress: 1%) +* German (de) (progress: 1%) +* Indonesian (id) (progress: 1%) +* Italian (it) (progress: 4%) +* Norwegian (nb-no) (progress: 1%) +* Persian (fa-ir) (progress: 3%) +* Portuguese (pt-br) (progress: 16%) +* Spanish (es) (progress: 15%) +* Turkish (tr) (progress: 2%) + +We want to thank everyone who contributed, translating or reviewing documents. + +Please, promote this effort in your local user group, we always need more volunteers. + +==== FreeBSD Manual Pages Portal + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +The Manual Pages Portal has been redesigned to use man:mandoc[1] for rendering. +A link:https://www.carlavilla.es/[portal preview] is available. +Feedback has been collected and addressed where possible. +There are some remaining non-blocking issues. +Doceng@ would like to move forward with the migration to this new portal. + +Thanks to all of those who reviewed it and provided feedback. + +==== FreeBSD Website Revamp - WebApps working group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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 will be 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_) + +. 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. (_Not started_) diff --git a/website/content/en/status/report-2022-07-2022-09/ena.adoc b/website/content/en/status/report-2022-07-2022-09/ena.adoc new file mode 100644 index 0000000000..e2c01fffd6 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/ena.adoc @@ -0,0 +1,22 @@ +=== ENA FreeBSD Driver Update + +Links: + +link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst[ENA README] URL: link:https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst[https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README.rst] + +Contact: Michal Krawczyk <mk@semihalf.com> + +Contact: David Arinzon <darinzon@amazon.com> + +Contact: Marcin Wojtas <mw@FreeBSD.org> + +ENA (Elastic Network Adapter) is the smart NIC available in the virtualized environment of Amazon Web Services (AWS). +The ENA driver supports multiple transmit and receive queues and can handle up to 100 Gb/s of network traffic, depending on the instance type on which it is used. + +Completed since the last update: + +* Upstream of the ENA driver v2.6.0 and v2.6.1, included: +** Fix for the performance degradation after reset issue on 6-gen instances, +** Fix of the false netmap assertions with KASSERT enabled, +** Code cleanup and style fixes, +** Logging improvements, +** Fix to the retrieval of the ENI metrics. + +Sponsor: Amazon.com Inc diff --git a/website/content/en/status/report-2022-07-2022-09/firecracker.adoc b/website/content/en/status/report-2022-07-2022-09/firecracker.adoc new file mode 100644 index 0000000000..797b9f1e0f --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/firecracker.adoc @@ -0,0 +1,29 @@ +=== FreeBSD/Firecracker + +Links: + +link:https://firecracker-microvm.github.io/[Firecracker VM] + +Contact: Colin Percival <cperciva@FreeBSD.org> + +Firecracker is an open source "microVM" developed by Amazon Web Services; it +is designed for the needs of "serverless" compute environments and has a +particular focus on security and minimalism. + +Starting in June 2022, Colin Percival has been working to port FreeBSD to run +in the Firecracker environment, with significant assistance from other FreeBSD +developers. As of this quarterly report, a set of patches are pending review +which collectively add the needed support to make FreeBSD functional in a +patched version of Firecracker. + +In Q4 Colin intends to finish committing the relevant patches to FreeBSD, +release a kernel and disk image so other FreeBSD users can experiment with +Firecracker, and update and merge Firecracker patches which add PVH boot +support (used by FreeBSD). + +This work has already produced "spinoff" benefits in revealing ways to speed +up the FreeBSD boot process; due to its low overhead and minimal environment, +Firecracker is an excellent context to work on this. + +This work is supported by Colin's FreeBSD/EC2 Patreon. + +Sponsor: https://www.patreon.com/cperciva diff --git a/website/content/en/status/report-2022-07-2022-09/freebsd-foundation.adoc b/website/content/en/status/report-2022-07-2022-09/freebsd-foundation.adoc new file mode 100644 index 0000000000..1d5bcaa638 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/freebsd-foundation.adoc @@ -0,0 +1,201 @@ +=== FreeBSD Foundation + +Links: + +link:https://www.FreeBSDfoundation.org[FreeBSD Foundation] URL: link:https://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] + +link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://FreeBSDFoundation.org/blog/technology-roadmap/] + +link:https://www.FreeBSDfoundation.org/donate/[Donate] URL: link:https://www.FreeBSDfoundation.org/donate/[https://www.FreeBSDFoundation.org/donate/] + +link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/[Foundation Partnership Program] URL: link:https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program[https://www.FreeBSDFoundation.org/FreeBSD-foundation-partnership-program] + +link:https://www.FreeBSDfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDFoundation.org/journal/] + +link:https://www.FreeBSDfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDFoundation.org/news-and-events/] + +Contact: Deb Goodkin <deb@FreeBSDFoundation.org> + +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to +supporting and promoting the FreeBSD Project and community worldwide. Donations +from individuals and corporations are used to fund and manage software +development projects, conferences, and developer summits. We also provide +travel grants to FreeBSD contributors, purchase and support hardware to improve +and maintain FreeBSD infrastructure, and provide resources to improve security, +quality assurance, and release engineering efforts. We publish marketing +material to promote, educate, and advocate for the FreeBSD Project, facilitate +collaboration between commercial vendors and FreeBSD developers, and finally, +represent the FreeBSD Project in executing contracts, license agreements, and +other legal arrangements that require a recognized legal entity. + +==== Fundraising Efforts + +First, I’d like to send a big thank you to everyone who gave a financial +contribution to our efforts. We are 100% funded by your donations, so every +contribution helps us continue to support FreeBSD in many ways, including some +of the work funded and published in this status report. + +We support FreeBSD in five main areas. Software development is the largest area +we fund through staff developers and contractors who implement new features, +support tier 1 platforms, review patches, and fix issues. You can read about +some of the work we did under OS Improvements in this report. FreeBSD Advocacy +is another area that we support to spread the word about FreeBSD at conferences, +in presentations online and in-person, and through tutorials and how-to guides. +We purchase and support hardware for the FreeBSD infrastructure that supports +the work going on in the Project. Virtual and in-person events are organized by +the Foundation to help connect and engage community members to share their +knowledge and collaborate on projects. Finally, we provide legal support to the +Project when needed and protect the FreeBSD trademarks. + +Our goal this year is to raise at a minimum $1,400,000 towards a spending budget +of around $2,000,000. As we enter the last quarter of 2022, our donation total +sits at $167,348, so we still need your help. If you haven't made a donation +this year, please consider making one at https://freebsdfoundation.org/donate/. +We also have a Partnership Program for larger commercial donors. You can find +out more at +https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/ + +==== OS Improvements + +During the third quarter of 2022, 300 src, 36 ports, and 13 doc tree commits +were made that identified The FreeBSD Foundation as a sponsor. Some of that +work has dedicated report entries. + +* FreeBSD as a Tier I cloud-init Platform +* Intel wireless towards 11ac +* LLDB multiprocess debugging support +* OpenStack on FreeBSD +* Snapshots on Filesystems Using Journaled Soft Updates + +The other sponsored work is challenging to concisely summarize. It varies from +complex new features to various bug fixes spanning the src tree. Here is a +small sample to give a flavor of last quarter's work. + +- 240afd8 makefs: Add ZFS support + + This allows one to take a staged directory tree and create a file consisting + of a ZFS pool with one or more datasets that contain the contents of the + directory tree. This is useful for creating virtual machine images without + using the kernel to create a pool; "zpool create" requires root privileges and + currently is not permitted in jails. makefs -t zfs also provides reproducible + images by using a fixed seed for pseudo-random number generation, used for + generating GUIDs and hash salts. makefs -t zfs requires relatively little by + way of machine resources. + +- 36f1526 Add experimental 16k page support on arm64 + + Add initial 16k page support on arm64. It is considered experimental, with no + guarantee of compatibility with userspace or kernel modules built with the + current 4k page size. Testing has shown good results in kernel workloads that + allocate and free large amounts of memory as only a quarter of the number of + calls into the VM subsystem are needed in the best case. + +- 1424f65 vm_pager: Remove the default pager + + It's unused now. Keep the OBJ_DEFAULT identifier, but make it an alias of + OBJT_SWAP for the benefit of out-of-tree code. + +- a889a65 eventtimer: Fix several races in the timer reload code + + In handleevents(), lock the timer state before fetching the time for the next + event. A concurrent callout_cc_add() call might be changing the next event + time, and the race can cause handleevents() to program an out-of-date time, + causing the callout to run later (by an unbounded period, up to the idle + hardclock period of 1s) than requested. + +===== Bhyve Issue Support + +The Foundation contracted John Baldwin to dedicate time to Bhyve as issues +arise, especially security issues. Here is a summary of his 2022q3 work on that +contract. + +- bb31aee bhyve virtio-scsi: Avoid out of bounds accesses to guest requests. +- 62806a7 bhyve virtio-scsi: Tidy warning and debug prints. +- 7afe342 bhyve e1000: Sanitize transmit ring indices. +- c94f30e bhyve: Validate host PAs used to map passthrough BARs. +- 16bedf5 pci: Add helper routines to iterate over a device's BARs. +- baf753c bhyve: Support other schemes for naming pass-through devices. +- fa46f37 bhyve e1000: Skip packets with a small header. +- e7439f6 bhyve xhci: Cache the value of MaxPStreams when initializing an endpoint. + +===== RISC-V Improvements + +At the end of the quarter, the Foundation contracted Mitchell Horne to add and +improve support for RISC-V hardware. Mitchell will also perform general +maintenance such as fixing bugs, handling reports, providing review for new code +changes, and improving source code legibility and documentation. + +==== Continuous Integration and Quality Assurance + +The Foundation provides a full-time staff member and funds projects to improve +continuous integration, automated testing, and overall quality assurance efforts +for the FreeBSD project. You can read about CI activities this quarter in a +dedicated entry. + +==== FreeBSD Advocacy and Education + +Much of our effort is dedicated to Project advocacy. This may involve +highlighting interesting FreeBSD work, producing literature and video tutorials, +attending events, or giving presentations. The goal of the literature we +produce is to teach people FreeBSD basics and help make their path to adoption +or contribution easier. Other than attending and presenting at events, we +encourage and help community members run their own FreeBSD events, give +presentations, or staff FreeBSD tables. + +The FreeBSD Foundation sponsors many conferences, events, and summits around the +globe. These events can be BSD-related, open source, or technology events +geared towards underrepresented groups. We support the FreeBSD-focused events +to help provide a venue for sharing knowledge, working together on projects, and +facilitating collaboration between developers and commercial users. This all +helps provide a healthy ecosystem. We support the non-FreeBSD events to promote +and raise awareness of FreeBSD, to increase the use of FreeBSD in different +applications, and to recruit more contributors to the Project. We are continuing +to attend events both in person and virtual as well as planning the November +Vendor Summit. In addition to attending and planning virtual events, we are +continually working on new training initiatives and updating our selection of +link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to +facilitate getting more folks to try out FreeBSD. + +Check out some of the advocacy and education work we did last quarter: + +* Held a FreeBSD Workshop and Staffed a booth at Scale 19x in Los Angeles, CA on + July 28-30. You can read more about our participation in the + link:https://freebsdfoundation.org/blog/scale19x-conference-report/[SCALE19X + Conference Report] +* Sponsored and attended link:https://coscup.org/2022/en/[COSCUP], July 30-31, Taiwan +* Attended the EuroBSDCon Developer Summit and sponsored and attended + link:https://2022.eurobsdcon.org/[EuroBSDcon 2022], September 15-18, Vienna, + Austria +* link:http://toilers.mines.edu/RMCWiC/2022/home.html[Sponsored and Presented at the Rocky Mountain Celebration of Women in + Computing], September 29-30, 2022. Slides from Deb’s presentation can be found + link:http://toilers.mines.edu/RMCWiC/2022/program.html[here]. +* Published the + link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-summer-2022-update/[FreeBSD + Foundation Summer 2022 Update] +* Continued our participation in Google Summer of Code as both an admin and + mentors. Interviews with some of the Google Summer of Code Students can be + found link:https://freebsdfoundation.org/our-work/latest-updates/[here]. +* Introduced a new + link:https://freebsdfoundation.org/freebsd-project/resources/[FreeBSD + Resources] page that allows for search by type of subject, type of content and + difficulty level. +* New Blog Posts: + +** Guest Post: link:https://freebsdfoundation.org/blog/guest-post-freebsd-in-science/[FreeBSD in Science] +** link:https://freebsdfoundation.org/blog/advocating-for-freebsd-in-2022-and-beyond/[Advocating for FreeBSD in 2022 and Beyond] +** link:https://freebsdfoundation.org/blog/august-foundation-fundraising-update/[August Foundation Fundraising Update] +** link:https://freebsdfoundation.org/blog/sharing-dual-licensed-drivers-between-linux-and-freebsd/[Sharing Dual-Licensed Drivers between Linux and FreeBSD] +* New and Updated How-To and Quick Guides: +** link:https://freebsdfoundation.org/blog/new-freebsd-quick-guide-video-playback-on-freebsd-quick-guide/[FreeBSD Quick Guide: Video Playback on FreeBSD] +** link:https://freebsdfoundation.org/resource/binary-package-management-on-freebsd/[Binary Package Management on FreeBSD] + +We help educate the world about FreeBSD by publishing the professionally +produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is +now a free publication. Find out more and access the latest issues at +link:https://www.FreeBSDfoundation.org/journal/[https://www.FreeBSDfoundation.org/journal/]. + +You can find out more about events we attended and upcoming events at +link:https://www.FreeBSDfoundation.org/news-and-events/[https://www.FreeBSDfoundation.org/news-and-events/]. + +==== 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://www.FreeBSDfoundation.org[https://www.FreeBSDFoundation.org] +to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2022-07-2022-09/gcc.adoc b/website/content/en/status/report-2022-07-2022-09/gcc.adoc new file mode 100644 index 0000000000..3d42964623 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/gcc.adoc @@ -0,0 +1,36 @@ +=== GCC: New maintainer, GCC 12.2 and more + +Links: + +link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] + +link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[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/[https://gcc.gnu.org/gcc-12/] + +Contact: <toolchain@FreeBSD.org> + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + + + * salvadore@ adopted all existing ports corresponding to supported versions of gcc, namely: lang/gcc10, lang/gcc11, lang/gcc11-devel, lang/gcc12, lang/gcc12-devel and lang/gcc13-devel. + At the moment -devel ports are updated weekly, unless a build failure makes it impossible. + Of course, in the latter case, the build failure is fixed and/or reported upstream as soon as possible. + + * link:https://gcc.gnu.org/gcc-12/changes.html[GCC 12.2 has been released]. + Traditionally, FreeBSD waits for the release of the second minor version of GCC to use it as default GCC version, so that most of the software needing to be compiled with GCC has already been ported to the latest major version. + Thus, work has started to update the default GCC version to version 12. + Thank you very much to antoine@ who has already run the first exp-run and to all the contributors, maintainers and committers involved in the process. + link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265948[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2659548] + + * Discussion about LTO keeps going with many different points of view. + If interested, you can read the latest contributions to the topic: link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264949[lang/gcc11: Needs build time warning for /tmp consumption] and link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265254[lang/gcc11: build gets stuck]. + Reminder: LTO_BOOTSTRAP is an option enabled by default. + If you build the port on your machine and its resources consumption is not acceptable, disabling this option will get you a lighter compilation. + + * jbeich@ submitted a patch to expose non-default -stdlib=libc++ support, which has been successfully committed to all relevant ports (gcc >= 11). + link: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265962[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265962] + + * diizzy@ refreshed the mirrors list in the MASTER_SITE_GCC variables, also removing ftp mirrors. The main GCC site is used as fallback. + link: https://reviews.freebsd.org/D36372[https://reviews.freebsd.org/D36372] + + * Help is still needed with these three changes to work through with upstream GCC (requires expertise with the GCC sources and upstream, not with the ports framework): + + ** upstreaming lang/gcc11/patch-gets-no-more + ** upstreaming lang/gcc11/patch-arm-unwind-cxx-support + ** link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256874] diff --git a/website/content/en/status/report-2022-07-2022-09/intro.adoc b/website/content/en/status/report-2022-07-2022-09/intro.adoc new file mode 100644 index 0000000000..f8a991319d --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/intro.adoc @@ -0,0 +1,11 @@ +Here is the third quarterly report for year 2022, with 24 reports included, which is slightly fewer than last quarter. + +I notice that in the past we had quarters with many more reports: often more than 30, sometimes even more than 40. +Thus I would like to encourage all of you to submit reports: reports are useful to share your work, to find help, to have more eyes reviewing your changes, to have more people testing your software, to reach a wider audience whenever you need to tell something to all of the FreeBSD community and in many other cases. +Please do not be shy and do not worry if you are not a native English speaker or if you are not proficient in AsciiDoc syntax: the quarterly team will be glad to help you in whatever you need. + +On the other hand, if you really do not have anything to report, then maybe you might like to join one of the interesting projects described below, or you might be inspired from one of them to do something new, thus having something to report in the future. + +We wish you all a pleasant read. + +Lorenzo Salvadore, on behalf of the status report team. diff --git a/website/content/en/status/report-2022-07-2022-09/iwlwifi.adoc b/website/content/en/status/report-2022-07-2022-09/iwlwifi.adoc new file mode 100644 index 0000000000..d608e7427b --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/iwlwifi.adoc @@ -0,0 +1,25 @@ +=== Intel wireless towards 11ac + +Links: + +link:https://wiki.freebsd.org/WiFi/Iwlwifi[Intel iwlwifi status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Iwlwifi[https://wiki.freebsd.org/WiFi/Iwlwifi] + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +The ongoing project aims to support the latest Intel wireless chipsets on FreeBSD using LinuxKPI compat code backed by native net80211 and kernel code. +In addition work is on the way to support 11n and 11ac standards in the LinuxKPI 802.11 compat code and fill gaps for mostly 11ac in the native net80211 wireless stack. + +For the Intel iwlwifi wireless driver there were no major updates in the last months. +We updated the firmware to the latest publicly available version and fixed some of the most visible bugs. +Work is also on the way to support the D3 power saving code. + +LinuxKPI compat code also got some improvements and fixes which at times were only observable on certain generations of iwlwifi chipsets. + +Changes in net80211 and LinuxKPI compat code for 11n and 11ac have little public visibility so far in order to not break basic support. +Updates to constants based on newer 802.11 standards and other changes without user-visible effect were merged, and +functional changes will follow in the coming months, initially hidden behind compile-time or runtime options. + +Improvements and updates were largely merged back to stable/13 for the benefit of the users tracking this branch and to help with more testing. + +For the latest state of the development, please follow the freebsd-wireless mailing list and check the wiki pages. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-07-2022-09/kde.adoc b/website/content/en/status/report-2022-07-2022-09/kde.adoc new file mode 100644 index 0000000000..91a6500c7e --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/kde.adoc @@ -0,0 +1,43 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] + +link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project packages the software from the KDE Community, along with dependencies and related software, for the FreeBSD ports tree. +The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine. +The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack. + +==== Qt6 Landed + +The big news in the KDE ports is not directly KDE-related. +Qt6 has landed, which prepares us for the next generation of Qt-based applications. + +It is now possible to have `USES=qt:6` to select the new Qt version. +Some ports have been flavorized to make use of the new version. + +KDE itself is not affected: the upstream work on KDE Frameworks for Qt6 is not yet completed. +Most of the KDE Frameworks will compile with Qt6, but that is not important for FreeBSD ports yet. +With package:devel/qt6[] you get Qt 6.4.0, released at the end of the quarter. + +==== KDE Stack + +KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. +These (large) updates land shortly after their upstream release and are not listed separately. + +* KDE Frameworks 5 is now at version 5.98 (latest monthly release from September 2022). +* KDE Gear is now version 22.08.1 (update for September 2022). +* KDE Plasma is now version 5.24.6 (update for July 2022). + +Note that KDE Plasma 5.25 has been released upstream, but is waiting on fixes before it can land in the ports tree (for example, link:https://bugs.kde.org/show_bug.cgi?id=458356[this KActivityManager bug] in KDE's bug-tracker). + +==== Related Ports + +* package:accessibility/qt5-speech[] now supports multiple backends, as well as no-backends, for speech synthesis. +* package:devel/cmake[] was reorganized, so that package:devel/cmake[] is now a metaport that installs package:devel/cmake-core[] and the rest of the CMake suite. (Thanks to diizzy@) The CMake ports were also updated to version 3.24, with attendant changes in ports all over the tree. +* package:net/qt5-network[] has improved compatibility with libressl. +* package:x11/plasma-wayland-protocols[] was updated in advance of KDE Plasma Desktop updates in the next quarter. diff --git a/website/content/en/status/report-2022-07-2022-09/kinst.adoc b/website/content/en/status/report-2022-07-2022-09/kinst.adoc new file mode 100644 index 0000000000..5a8834bd92 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/kinst.adoc @@ -0,0 +1,48 @@ +=== DTrace: Instruction-level dynamic tracing + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2022Projects/InstructionLevelDynamicTracing[Wiki article] URL: link:https://wiki.freebsd.org/SummerOfCode2022Projects/InstructionLevelDynamicTracing[https://wiki.freebsd.org/SummerOfCode2022Projects/InstructionLevelDynamicTracing] + +link:https://reviews.freebsd.org/D36851[Final code review] URL: link:https://reviews.freebsd.org/D36851[https://reviews.freebsd.org/D36851] + + +Contact: Christos Margiolis <christos@FreeBSD.org> + +Contact: Mark Johnston <markj@FreeBSD.org> + +kinst is a new DTrace provider that allows for arbitrary kernel instruction tracing. + +The provider is currently implemented only for amd64, but we plan to port it to other architectures in the future as well. + +kinst probes are created on demand by libdtrace, and a probe can be created for nearly every instruction in the kernel. +Probes take the form of: + + kinst:<module>:<function>:<offset> + +where "module" is the kernel module containing the named function, "function" is the kernel function to be traced, and "offset" is the offset to a specific instruction. +Omitting "offset" causes all instructions in the function to be traced. +Omitting "module" causes DTrace to search all kernel modules for the function. + +For example, to trace the second instruction in amd64_syscall(), first determine the offset of the second instruction: + + # kgdb + (kgdb) disas /r amd64_syscall + Dump of assembler code for function amd64_syscall: + 0xffffffff809256c0 <+0>: 55 push %rbp + 0xffffffff809256c1 <+1>: 48 89 e5 mov %rsp,%rbp + 0xffffffff809256c4 <+4>: 41 57 push %r15 + +The offset is 1. +Then, to trace it: + + # dtrace -n 'kinst::amd64_syscall:1' + +A new "regs" keyword was also added to the D language, providing read-only access to CPU registers at the point where the probe fired. +For example, to trace the contents of the frame pointer (register %rbp on amd64) when the kinst::amd64_syscall:1 probe fires: + + # dtrace -n 'kinst::amd64_syscall:1 {printf("0x%x", regs[R_RBP]);}' + +kinst works similarly to the FBT (function boundary tracing) provider in that it places a breakpoint on the target instruction and hooks into the kernel's breakpoint handler. +It is more powerful than FBT since it can be used to create probes at arbitrary points within a function, rather than at function boundaries. +Because kinst has to be able to trace arbitrary instructions, it does not emulate most of them in software but rather causes the traced thread to execute a copy of the instruction before returning to the original code. + +Planned future work includes porting kinst to additional platforms, especially arm64 and riscv, and developing tooling that can use kinst to trace calls to inline functions using the kernel's debugging symbols. + +Sponsor: Google, Inc. (GSOC 2022) diff --git a/website/content/en/status/report-2022-07-2022-09/lldb.adoc b/website/content/en/status/report-2022-07-2022-09/lldb.adoc new file mode 100644 index 0000000000..04c7a1b761 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/lldb.adoc @@ -0,0 +1,24 @@ +=== Ongoing work on LLDB multiprocess debugging support + +Links: + +link:https://www.moritz.systems/blog/multiprocess-support-for-lldb/[Moritz Systems Project Description] URL: link:https://www.moritz.systems/blog/multiprocess-support-for-lldb/[https://www.moritz.systems/blog/multiprocess-support-for-lldb/] + +link:https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/[Progress Report 1] URL: link:https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/[https://www.moritz.systems/blog/implementing-non-stop-protocol-compatibility-in-lldb/] + +link:https://www.moritz.systems/blog/full-multiprocess-support-in-lldb-server/[Progress Report 2] URL: link:https://www.moritz.systems/blog/full-multiprocess-support-in-lldb-server/[https://www.moritz.systems/blog/full-multiprocess-support-in-lldb-server/] + +Contact: Kamil Rytarowski <kamil@moritz.systems> + +Contact: Michał Górny <mgorny@moritz.systems> + +According to the upstream description, "LLDB is a next generation, high-performance debugger. It is built as a set of reusable components which highly leverage existing libraries in the larger LLVM Project, such as the Clang expression parser and LLVM disassembler." + +FreeBSD includes LLDB in the base system. +The previous sponsored projects improved LLDB, to make it a credible debugger for the base system, although it still has a few limitations compared to the contemporary versions of GNU GDB. +This project started in April 2022. +It aims to implement full support for debugging multiple processes simultaneously. + +At the start of the project, LLDB featured very limited support for multiprocess debugging. +Currently, the server is already able to monitor multiple processes using the multiprocess extension to the GDB Remote Serial Protocol. +The work on implementing the client-side counterpart for this protocol is ongoing. + +Once the project is finished, LLDB will be able to trace an arbitrary number of forked processes simultaneously (equivalent to GDB's `detach-on-fork off`). + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-07-2022-09/lsof.adoc b/website/content/en/status/report-2022-07-2022-09/lsof.adoc new file mode 100644 index 0000000000..136f204feb --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/lsof.adoc @@ -0,0 +1,19 @@ +=== sysutils/lsof major upgrade + +Link: + +link:https://github.com/lsof-org/lsof[lsof project repo] URL: link:https://github.com/lsof-org/lsof[https://github.com/lsof-org/lsof] + +Contact: + +Larry Rosenman <ler@FreeBSD.org> + +package:sysutils/lsof[] had a major upgrade to no longer look in `/dev/kmem` for data, and to use the userland API. +This took a long time to hit the tree, but is finally done. +It fixes man:lsof[8] to work with ZFS again for the first time since 13.0-RELEASE. + +This will make maintenance much easier going forward. + +To the kernel folks: if you make changes that break lsof, please submit a GitHub pull request to https://github.com/lsof-org/lsof. +Please test any changes to the interfaces that lsof uses and make sure they still work. +These all should be userland interfaces now, but please test. + +My thanks to Warner Losh <imp@FreeBSD.org>, Mateusz Guzik <mjg@FreeBSD.org>, and Ed Maste <emaste@FreeBSD.org> for help getting this major change landed. diff --git a/website/content/en/status/report-2022-07-2022-09/openstack-on-freebsd.adoc b/website/content/en/status/report-2022-07-2022-09/openstack-on-freebsd.adoc new file mode 100644 index 0000000000..6624da25e4 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/openstack-on-freebsd.adoc @@ -0,0 +1,42 @@ +=== OpenStack on FreeBSD + +Links: + +link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] + +link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[] + + +Contact: Chih-Hsin Chang <starbops@hey.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +OpenStack is an open-source cloud operating system for different types of resources like virtual and bare-metal machines. +Users can spawn FreeBSD instances on the open cloud platform, but it is not currently possible to run OpenStack control plane on FreeBSD hosts. +The goal of this project is to port key OpenStack components so that FreeBSD can function as an OpenStack host. + +Academic and industrial research groups have been evaluating CHERI-enabled Morello boards since mid-2022. +A resource orchestration platform like OpenStack can improve the speed and cost of provisioning, managing, and recycling those boards. + +Starting in January 2022, Chih-Hsin Chang has been working to port several OpenStack components to run on FreeBSD, including: + +* Keystone (identity service) +* Glance (image service) +* Placement (resource tracking and inventory service) +* Neutron (networking service) +* Nova (compute service) + +Some of the items are still under heavy development. +For instance, due to the design of Neutron, the DHCP servers are placed inside Linux network namespaces. +It is necessary to find an alternative, e.g. `vnet`, on FreeBSD and adapt it. +Most of the time the porting strategy is to make as small of an impact as possible by working around obstacles. +But something like `oslo.privsep` deserves a true porting. +`oslo.privsep` is rooted in Linux capabilities to do the privilege separation work. +Right now we just bypassed any Linux capabilities-related operation inside `oslo.privsep`. +So there is plenty of hackish spots in the source code and configurations currently. +All of these along with the building and installation steps will be collected in the https://github.com/openstack-on-freebsd[project repositories]. + +In Q4 Chih-Hsin plans to focus on porting Neutron and Nova in order to complete the VM lifecycle operations. +The highlights include: + +* DHCP integration +* FreeBSD bridge driver/agent +* Bhyve + Libvirt integration + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc b/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc new file mode 100644 index 0000000000..84b680b904 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/pjdfstest.adoc @@ -0,0 +1,24 @@ +=== Rewrite of pjdfstest + +Links: + +link:https://github.com/musikid/pjdfstest[Github] URL: link:https://github.com/musikid/pjdfstest[https://github.com/musikid/pjdfstest] + +link:https://musikid.github.io/blog/rewrite-pjdfstest/[Blog] URL: https://musikid.github.io/blog/rewrite-pjdfstest/[https://musikid.github.io/blog/rewrite-pjdfstest/] + +Contact: Alan Somers <asomers@FreeBSD.org> + +Back in 2007, Pawel Jakub Dawidek <pjd@FreeBSD.org> wrote pjdfstest, a POSIX file system conformance test tool. +He originally wrote it to validate the port of ZFS to FreeBSD, but it has subsequently been used for other file systems and other operating systems. + +This year, Sayafdine Said <musikid@outlook.com> rewrote it under Google's sponsorship. +The new version has several improvements: + +* More configurable, for better use with other file systems. +* Much faster, largely thanks to said configurability. +* Better test case isolation, making failure easy to debug. +* No longer requires root privileges for all test cases. +* Test cases can be run in a debugger. +* More maintainable, less duplication. + +There are still a couple of lingering PRs to complete, but we expect to wrap those up and add pjdfstest to the ports collection soon. +From there, it will be used both by `/usr/tests` for ZFS and UFS, and by external developers for other file systems. + +Sponsor: Google Summer of Code diff --git a/website/content/en/status/report-2022-07-2022-09/portmgr.adoc b/website/content/en/status/report-2022-07-2022-09/portmgr.adoc new file mode 100644 index 0000000000..62655e0d66 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/portmgr.adoc @@ -0,0 +1,56 @@ +=== Ports Collection + +Links: + +link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[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[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] + +link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] + +link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[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/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/] + +Contact: René Ladan <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +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. + +Currently there are just over 30,500 ports in the Ports Tree. +There are currently just under 2,800 open ports PRs of which 750 are unassigned. +The last quarter saw 9,137 commits by 151 committers on the main branch and 589 commits by 61 committers on the 2022Q3 branch. +Compared to two quarters ago, this means a slight increase in the number of ports, but also a slight increase in the number of (unassigned) ports PRs and a slight decrease in the number of commits made. + +In the last quarter, we welcomed Felix Palmen (zirias@) as a new ports committer, welcomed back Akinori MUSHA (knu@), and said goodbye to Olli Hauer (ohauer@). +We also welcomed Luca Pizzamiglio (pizzamig@) as an official member of portmgr. + +Some large changes in the Ports Tree were made during the last quarter: + +* "Created by" lines have been removed from the top of each Makefile, as a lot of those were outdated. +* WWW: has been moved from each pkg-descr into each Makefile as a variable; the below write-up is from Stefan Eßer (se@) who did the work: + +The description of a port's functionality should end with the URL of a web page that provides further information, such as best practices for usage or configuration. +This information can be displayed with `pkg query -e` for installed packages or `pkg rquery -e` for available packages. +The URL used to be appended to the end of the ports' pkg-descr files, with the prefix "WWW: ", so that tools could extract the URL from the description. +Over time, many of these URLs have become stale, since port updates generally change only the Makefile, not the pkg-descr file. +By moving the definition of these URLs into the Makefiles, maintainers are more likely to update the URL along with other port changes, and tools have easier access to them. +The URLs are now assigned to the WWW macro in the Makefile and can be queried with `make -V WWW` in the port directory. +Tools that process the description contained in the package files still work because the "WWW: " lines at the end are generated from the WWW values in the Makefiles. + +During EuroBSDCon, portmgr@ had a discussion about improving the situation for kernel module packages. +Various possibilities have been discussed. + +The following happened under the hood: + +* one new USES, "vala", was added. +* The default version of Go got bumped to 1.19 +* CMake is now a meta-port +* Initial support for Qt 6 was added, at version 6.3.2 +* Vim no longer installs a system-wide vimrc +* A number of major ports got updated: +** pkg 1.18.4 +** Chromium 106.0.5249.91 +** Firefox 105.0.1 +*** Firefox ESR 102.3.0 +** KDE Applications 22.8.1 +** KDE Frameworks 5.98 +** Rust 1.63.0 +** SDL 2.24.0 +** Xorg server 21.1.4 (overhaul) diff --git a/website/content/en/status/report-2022-07-2022-09/pot.adoc b/website/content/en/status/report-2022-07-2022-09/pot.adoc new file mode 100644 index 0000000000..8d80107ccd --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/pot.adoc @@ -0,0 +1,24 @@ +=== Containers and FreeBSD: Pot, Potluck and Potman + +Links: + +link:https://github.com/bsdpot[Pot organization on github] URL: link:https://github.com/bsdpot[https://github.com/bsdpot] + +Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> + +Contact: Stephan Lichtenauer (Potluck) <sl@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@freebsd.org> + +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]. + +During the last quarter, link:https://github.com/bsdpot/pot/releases/tag/0.15.3[pot 0.15.3] was released. +It contains a number of improvements like mount-out to remove or unmount a previously mount-in folder or filesystem, signal and exec commands, better jail lifecycle handling, and many bug fixes. + +A new version of the Nomad driver, link:https://github.com/bsdpot/nomad-pot-driver/releases/tag/v0.9.0[nomad-pot-driver 0.9.0], was also released with signal and exec support and stability fixes. + +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. + +Since the last status report, link:https://github.com/bsdpot/potluck/commits/master[many changes were committed], including many fixes and improvements to core images like 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/loki[loki]. +Additionally, all images have been rebuilt for FreeBSD 13.1 and 12.3 and to include the current quarterly versions of the packages being used. + +Last not least, Luca held the pot implementation and ecosystem talk link:https://2022.eurobsdcon.org/program/[How far a naive FreeBSD container implementation can go] at EuroBSDCon 2022. + +As always, feedback and patches are welcome. diff --git a/website/content/en/status/report-2022-07-2022-09/releng.adoc b/website/content/en/status/report-2022-07-2022-09/releng.adoc new file mode 100644 index 0000000000..e5589c2543 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/releng.adoc @@ -0,0 +1,18 @@ +=== FreeBSD Release Engineering Team
+
+Links: +
+link:https://www.freebsd.org/releases/12.4R/schedule/[FreeBSD 12.4-RELEASE schedule] URL: link:https://www.freebsd.org/releases/12.4R/schedule/[https://www.freebsd.org/releases/12.4R/schedule/] +
+link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[https://www.freebsd.org/releases/13.2R/schedule/] +
+link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[https://www.freebsd.org/releases/14.0R/schedule/] +
+link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[https://download.freebsd.org/snapshots/ISO-IMAGES/]
+
+Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org>
+
+The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things.
+
+During the third quarter of 2022, the Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/13*, and *stable/12* branches.
+
+Additionally, the schedules for the upcoming 12.4, 13.2, and 14.0 release cycles were published on the Project website.
+
+Sponsor: Rubicon Communications, LLC ("Netgate")
+Sponsor: The FreeBSD Foundation
diff --git a/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc b/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc new file mode 100644 index 0000000000..97aa9e5d1f --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/ufs_snapshots.adoc @@ -0,0 +1,30 @@ +=== Enabling Snapshots on Filesystems Using Journaled Soft Updates + +Links: + +link:https://reviews.freebsd.org/D36491[Milestone 1 Core Changes] URL: link:https://reviews.freebsd.org/D36491[https://reviews.freebsd.org/D36491] + +Contact: Kirk McKusick <mckusick@FreeBSD.org> + +This project will make UFS/FFS filesystem snapshots available when running with journaled soft updates. + +The UFS/FFS filesystem has the ability to take snapshots. +Because the taking of snapshots was added after soft updates were written they were fully integrated with soft updates. +When journaled soft updates were added in 2010, they were never integrated with snapshots. +So snapshots cannot be used on filesystems running with journaled soft updates. + +Snapshots became less important with the support for ZFS on FreeBSD since ZFS can take snapshots quickly and easily. +However there remain two instances where UFS snapshots are still important. +The first is that they allow reliable dumps of live filesystems which avoids possibly hours of down time. +The second is that they allow the running of background fsck. +Similar to the need for scrub in ZFS, fsck needs to be run periodically to find undetected disk failures. +Snapshots allow fsck to be run on live filesystems rather than needing to schedule down time to run it. + +This project has two milestones: + +1. enable snapshots when running with journaled soft updates and ensure that they can be used for doing background dumps on a live filesystem. +This milestone should be completed by the end of 2022. + +2. extend fsck_ffs to be able to do a background check using a snapshot on a filesystem running with journaled soft updates. +This milestone is expected by Q3 of 2023. + +Sponsored by: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-07-2022-09/wifi.adoc b/website/content/en/status/report-2022-07-2022-09/wifi.adoc new file mode 100644 index 0000000000..5b7a5dd00a --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/wifi.adoc @@ -0,0 +1,31 @@ +=== More wireless updates + +Links: + +link:https://people.freebsd.org/~bz/wireless/[Bjoern's Wireless Work In Progress landing page] URL: link:https://people.freebsd.org/\~bz/wireless/[https://people.freebsd.org/~bz/wireless/] + +link:https://wiki.freebsd.org/WiFi/Rtw88[Realtek rtw88 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw88[https://wiki.freebsd.org/WiFi/Rtw88] + +link:https://wiki.freebsd.org/WiFi/Rtw89[Realtek rtw89 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Rtw89[https://wiki.freebsd.org/WiFi/Rtw89] + +link:https://wiki.freebsd.org/WiFi/Mt76[MediaTek mt76 status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Mt76[https://wiki.freebsd.org/WiFi/Mt76] + +link:https://wiki.freebsd.org/WiFi/Ath11k[QCA ath11k status FreeBSD wiki page] URL: link:https://wiki.freebsd.org/WiFi/Ath11k[https://wiki.freebsd.org/WiFi/Ath11k] + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +Currently development is mostly driven by Intel's iwlwifi driver again (see other report). +As the saying goes ''each one helps the other'' so has work on Realtek's rtw89 driver helped find a bug in LinuxKPI bothering iwlwifi users. +For this status report the topic is mostly more drivers, which do need more LinuxKPI support. + +Various work in progress: + + * Realtek's rtw88 PCI is in-tree as-is and after a fruitful discussion with Hans Petter Selasky at EuroBSDCon work on LinuxKPI USB support for the rtw88 USB WiFi dongles will continue. + + * Realtek's rtw89 driver was committed to main but is not connected to the build yet. Scanning already works but packets are not yet passing. Having the driver in-tree already eased testing for users having that chipset in order to identify more unimplemented LinuxKPI bits (some of which will help the other drivers as well) and reduced work for me. + + * The next drivers to probably hit the tree will be based on MediaTek's mt76 driver (for 7921 and 7915) which I have compiling and started testing. + + * Based on requests I am also working on ath11k to support STA mode given some vendors seem to ship Laptops with those chips. + +While some of this clearly benefits from work sponsored by The FreeBSD Foundation for iwlwifi and newer standard support, a lot of this is just free-time work. +If you are interested in any of these drivers I would greatly appreciate if some more hands would help with one or the other. +This could be regularly testing updates to main, writing documentation and updating wiki pages, tracking PRs, trying out patches, helping with work on individual LinuxKPI bits with or without 802.11 work, or simply debugging problems with individual drivers and/or chipsets. +If you are interested in helping with any one of the above, please drop me an email. + +For the latest state of the development, please follow the freebsd-wireless mailing list and check the wiki pages (as soon as they exist). diff --git a/website/content/en/status/report-2022-07-2022-09/wtap.adoc b/website/content/en/status/report-2022-07-2022-09/wtap.adoc new file mode 100644 index 0000000000..e963aac9f6 --- /dev/null +++ b/website/content/en/status/report-2022-07-2022-09/wtap.adoc @@ -0,0 +1,18 @@ +=== wtap(4) enhancement + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2022Projects/AddStaHostapAndAdhocModeToWtapWlanSimulator[Add sta, hostap and adhoc mode to wtap wlan simulator] + +Contact: En-Wei Wu <enweiwu@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +wtap(4) is a net80211(4) Wi-Fi simulator introduced by Monthadar Al Jaberi <monthadar@gmail.com> and Adrian Chadd <adrian@FreeBSD.org> in 2012. +It originally supported 802.11s mesh mode and was used for verification. +During the 2022 Google Summer of Code, En-Wei had been working on bringing sta, hostap, adhoc and monitor modes to it. +The work also covers adding basic tests for net80211(4) with wtap(4), written in atf(7). + +For more details, please check the link:https://wiki.freebsd.org/SummerOfCode2022Projects/AddStaHostapAndAdhocModeToWtapWlanSimulator[project wiki page]. + +Sponsor: Google Summer of Code +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/FreshPorts.adoc b/website/content/en/status/report-2022-10-2022-12/FreshPorts.adoc new file mode 100644 index 0000000000..87cc9f7e2c --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/FreshPorts.adoc @@ -0,0 +1,53 @@ +=== FreshPorts - help wanted + +Links: + +link:https://freshports.org/[FreshPorts] URL: link:https://freshports.org/[https://freshports.org/] + +link:https://news.freshports.org/[FreshPorts blog] URL: link:https://news.freshports.org/[https://news.freshports.org/] + +Contact: Dan Langille <dvl@FreeBSD.org> + +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/[https://www.freshports.org/security/acme.sh/] shows the history of the _acme.sh_ port, back to its creation in May 2017. + +==== Converting the backend repository + +This topic deals with the FreshPorts code repository. +The front end (website) was converted from Subversion to Git several years ago. +The back end, which processes FreeBSD commits and updates the database, is still on Subversion. +I have wanted to convert these repositories to Git for some time. + +I would like help with this please. +I'll give you a copy of the repositories and you give me back several Git repos (one for each). +They will be uploaded to link:https://github.com/FreshPorts[https://github.com/FreshPorts] (our project on GitHub). + +These are the existing Subversion repos: + +* ingress (code for the back end) +* database schema +* backend - monitoring code +* packaging - scripts for cutting new tarballs - deprecated via Git +* daemontools - now misnamed, because the scripts use man:daemon[8] +* periodics - scripts started by man:periodic[8] +* ports - for the FreeBSD packages which install the above. + +==== I won't be running FreshPorts forever + +It's been over 22 years and I know others must take over eventually. +I'd like to start that process now. +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. diff --git a/website/content/en/status/report-2022-10-2022-12/NFS-in-prisons.adoc b/website/content/en/status/report-2022-10-2022-12/NFS-in-prisons.adoc new file mode 100644 index 0000000000..d81a384b57 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/NFS-in-prisons.adoc @@ -0,0 +1,24 @@ +=== Enable the NFS server to run in a vnet prison + +Links: + +link:https://people.freebsd.org/%7Ermacklem/vnet.patch[Source patch for main] URL: link:https://people.freebsd.org/%7Ermacklem/vnet.patch[https://people.freebsd.org/~rmacklem/vnet.patch] + +link:https://people.freebsd.org/%7Ermacklem/nfsd-vnet-prison-setup.txt[Simple Setup Doc] URL: link:https://people.freebsd.org/%7Ermacklem/nfsd-vnet-prison-setup.txt[https://people.freebsd.org/~rmacklem/nfsd-vnet-prison-setup.txt] + +Contact: Rick Macklem <rmacklem@freebsd.org> + +Several users of FreeBSD identified a need to run the NFS server inside a vnet prison. +This turned into a small project, where I now have a patch that does this. +It is currently available at the above link for testing or on Phabricator as link:https://reviews.freebsd.org/D37519[D37519]. +Without this patch, the NFS server cannot be run in a prison. + +Not included in the above patch is the ability to run the man:rpc.tlsservd[8] and man:nfsuserd[8] daemons within the vnet prison. +I do now have patches that allow these daemons to run in the vnet prison along with man:mountd[8] and man:nfsd[8], but I would like to get the above patch into main before adding support for man:rpc.tlsservd[8] or man:nfsuserd[8]. + +At this time, the code needs reviewing and testing. +Hopefully this can be completed in the next few weeks, so that the patch can be committed to `main` and possibly also MFC'd to `stable/13`. + +==== To do + +* Testing the above patch. +* Reviewing the above patch. +* Doing the same for the man:rpc.tlsservd[8] and man:nfsuserd[8] patches. diff --git a/website/content/en/status/report-2022-10-2022-12/_index.adoc b/website/content/en/status/report-2022-10-2022-12/_index.adoc new file mode 100644 index 0000000000..d6ff60e63f --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/_index.adoc @@ -0,0 +1,203 @@ +--- +title: "FreeBSD Status Report Fourth Quarter 2022" +sidenav: about +--- + += Introduction +:doctype: article +:toc: macro +:toclevels: 2 +:icons: font +:!sectnums: +:source-highlighter: rouge +:experimental: +:reports-path: content/en/status/report-2022-10-2022-12 + +include::{reports-path}/intro.adoc[] + +''' + +toc::[] + +''' + +[[FreeBSD-Team-Reports]] +== FreeBSD Team Reports + +Entries from the various official and semi-official teams, as found in the link:../../administration/[Administration Page]. + +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}/status.adoc[] + +''' + +[[projects]] +== Projects + +Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. + +include::{reports-path}/accessibility.adoc[] + +''' + +include::{reports-path}/vessel-status-report.adoc[] + +''' + +include::{reports-path}/NFS-in-prisons.adoc[] + +''' + +include::{reports-path}/pytest-for-atf.adoc[] + +''' + +[[userland]] +== Userland + +Changes affecting the base system and programs in it. + +include::{reports-path}/openssh.adoc[] + +''' + +[[kernel]] +== Kernel + +Updates to kernel subsystems/features, driver support, filesystems, and more. + +include::{reports-path}/ufs_snapshots.adoc[] + +''' + +include::{reports-path}/wifi.adoc[] + +''' + +include::{reports-path}/netlink.adoc[] + +''' + +include::{reports-path}/ddb_ctf.adoc[] + +''' + +[[architectures]] +== Architectures + +Updating platform-specific features and bringing in support for the new hardware platform. + +include::{reports-path}/cheribsd.adoc[] + +''' + +include::{reports-path}/riscv.adoc[] + +''' + +include::{reports-path}/golang_riscv64.adoc[] + +''' + +include::{reports-path}/xen.adoc[] + +''' + +[[cloud]] +== Cloud + +Updating cloud-specific features and bringing in support for new cloud platforms. + +include::{reports-path}/azure.adoc[] + +''' + +include::{reports-path}/cloud-init.adoc[] + +''' + +include::{reports-path}/openstack-on-freebsd.adoc[] + +''' + +[[documentation]] +== Documentation + +Noteworthy changes in the documentation tree, manual pages, or new external books/documents. + +include::{reports-path}/doceng.adoc[] + +''' + +include::{reports-path}/papers.adoc[] + +''' + +[[ports]] +== Ports + +Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. + +include::{reports-path}/FreshPorts.adoc[] + +''' + +include::{reports-path}/portsdb.adoc[] + +''' + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/xfce.adoc[] + +''' + +include::{reports-path}/pantheon.adoc[] + +''' + +include::{reports-path}/budgie.adoc[] + +''' + +include::{reports-path}/gcc.adoc[] + +''' + +include::{reports-path}/biology.adoc[] + +''' + +[[third-Party-Projects]] +== Third Party Projects + +Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. +As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. +The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. + +include::{reports-path}/pot.adoc[] diff --git a/website/content/en/status/report-2022-10-2022-12/accessibility.adoc b/website/content/en/status/report-2022-10-2022-12/accessibility.adoc new file mode 100644 index 0000000000..287fd03e7c --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/accessibility.adoc @@ -0,0 +1,22 @@ +=== Console screen reader infrastructure + +Links: + +link:https://reviews.freebsd.org/D35776[console speaker daemon] URL: link:https://reviews.freebsd.org/D35776[https://reviews.freebsd.org/D35776] + +link:https://reviews.freebsd.org/D35754[kernel support for console screen reader] URL: link:https://reviews.freebsd.org/D35754[https://reviews.freebsd.org/D35754] + +link:https://wiki.freebsd.org/Accessibility/Wishlist/Base[base system accessibility wishlist] URL: link:https://wiki.freebsd.org/Accessibility/Wishlist/Base[https://wiki.freebsd.org/Accessibility/Wishlist/Base] + +Contact: Hans Petter Selasky <hps@selasky.org> + +Contact: FreeBSD accessibility discussions <freebsd-accessibility@freebsd.org> + +This project aims at providing a very basic screen reader usable in console mode (without a GUI) for FreeBSD. +This is an important first step for system administrators using speech to access computers, who previously would have needed a second computer running a terminal emulator to install or configure a FreeBSD server or character-based desktop computer. + +The third and fourth quarters of 2022 saw basic design and some feature testing which looks promising, and a link:https://lists.freebsd.org/archives/freebsd-accessibility/2022-October/000014.html[detailed call for testing with installation procedure] posted. + +This project needs help with the following: + +* Code reviewing +* Usability testing +* Integrating with the FreeBSD installer. + +Sponsor: NVIDIA Networking (for the kernel development part) diff --git a/website/content/en/status/report-2022-10-2022-12/azure.adoc b/website/content/en/status/report-2022-10-2022-12/azure.adoc new file mode 100644 index 0000000000..d694296d43 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/azure.adoc @@ -0,0 +1,42 @@ +=== 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[https://wiki.freebsd.org/MicrosoftAzure] + +link:https://wiki.freebsd.org/HyperV[Microsoft HyperV article on FreeBSD wiki] URL: link:https://wiki.freebsd.org/HyperV[https://wiki.freebsd.org/HyperV] + +Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] + +Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> + +Contact: Wei Hu <whu@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + + +In this quarter, the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-12_4[12.4-RELEASE image] has been published to Azure Marketplace. + +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 +** Blocked by https://bugs.freebsd.org/264267 + +The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft. + +Wei Hu and his colleagues in Microsoft are working on several tasks sponsored by Microsoft: + +* Fixing booting issue on Hyper-V gen2 VM in Azure +** https://bugs.freebsd.org/264267 +* Porting Hyper-V guest support to aarch64 +** https://bugs.freebsd.org/266248 +** https://bugs.freebsd.org/267654 + +Open tasks: + +* Update FreeBSD related doc at link:https://docs.microsoft.com[https://docs.microsoft.com] +* Support FreeBSD in link:https://azure.microsoft.com/services/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 work by Wei Hu and others in Microsoft, and for resources for the rest + +Sponsor: The FreeBSD Foundation for everything else diff --git a/website/content/en/status/report-2022-10-2022-12/biology.adoc b/website/content/en/status/report-2022-10-2022-12/biology.adoc new file mode 100644 index 0000000000..6e685ef73b --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/biology.adoc @@ -0,0 +1,28 @@ +=== Another milestone for biology ports + +Links: + +link:https://github.com/auerlab/biolibc-tools[Biolibc-tools] URL: link:https://github.com/auerlab/biolibc-tools[https://github.com/auerlab/biolibc-tools] + +link:https://github.com/auerlab/fasda[Fast And Simple Differential Analysis] URL: link:https://github.com/auerlab/fasda[https://github.com/auerlab/fasda] + +Contact: Jason Bacon <jwb@FreeBSD.org> + +The biology category in ports continues to grow and mature, and reached another milestone in 2022q4 with the introduction of the rna-seq metaport. + +The fields of genomics, and more generally, bioinformatics, are often referred to as the "wild west" of computational science. +Analyses are typically mired by a lack of clear documentation, and difficulties deploying and using software. +Many scientific software developers do not understand the potential of package managers to simplify their lives and the lives of their users. +As a result, much scientific software is deployed using ad hoc "caveman" installations involving overly complicated and unreliable build systems that either bundle dependencies or attempt to work with random installations thereof. + +Work has been ongoing to make FreeBSD ports a model of how easy scientific software deployment should be. +It now contains a solid core of many of the most commonly used open source applications in biological research. + +This quarter saw the completion of a tool chain for one of the most important types of analysis, known as RNA-Seq. +RNA-Seq measures the abundance of RNA, and hence gene activity, in tissue samples. +All of the tools needed to perform a typical RNA-Seq analysis can now be installed on FreeBSD using: + +`pkg install rna-seq` + +This includes many mature existing tools as well as new tools developed on FreeBSD, such as FASDA and biolibc-tools, easy-to-use replacements for some of the more troublesome tools traditionally used in an RNA-Seq pipeline. + +Software deployments for RNA-Seq that traditionally have taken weeks or longer can now be performed on FreeBSD in a few minutes with a single command. +Scientists can spend their time doing science rather than struggling with IT issues. diff --git a/website/content/en/status/report-2022-10-2022-12/budgie.adoc b/website/content/en/status/report-2022-10-2022-12/budgie.adoc new file mode 100644 index 0000000000..30d6275d47 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/budgie.adoc @@ -0,0 +1,37 @@ +=== Budgie desktop on FreeBSD + +Links: + +link:https://blog.buddiesofbudgie.org/[Buddies of Budgie news] URL: link:https://blog.buddiesofbudgie.org/[https://blog.buddiesofbudgie.org/] + +link:https://codeberg.org/olivierd/freebsd-ports-budgie[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-budgie[https://codeberg.org/olivierd/freebsd-ports-budgie] + + +Contact: Olivier Duchateau <duchateau.olivier@gmail.com> + +Budgie initially developed as the default desktop environment for the former Evolve OS. +Since the 10.6.x releases, improvements have been made to be "agnostic". + +It is built on top of GNOME technologies such as GTK >= 3, GLib, Mutter, libpeas. + +The goal is to have a new desktop for end users. +I have submitted 2 reviews (link:https://reviews.freebsd.org/D37224[D37224] and link:https://reviews.freebsd.org/D37286[D37286] for The FreeBSD Porter's Handbook) so committers can import it. + +These reviews include: + +* Mk/Uses framework `budgie.mk` +* new virtual category (*budgie*) +* 6 applications +* icon theme `x11-themes/tela-icon-theme`. + +During this quarter, I have also submitted several patches (related to this desktop) especially: + +* `x11/gnome-terminal` update to 3.44.2 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267928[bug #267928] +* `x11-wm/mutter` update to 42.6 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267899[bug #267899] +* `x11-toolkits/libwnck3` update to 40.1 link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267898[bug #267898]. + +These bugs are also still open: + +* `devel/libpeas` link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267420[bug #267420] +* `sysutils/gnome-settings-daemon` link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265107[bug #265107]. + +==== Open task + +* Add support of LightDM in FreeBSD Handbook diff --git a/website/content/en/status/report-2022-10-2022-12/cheribsd.adoc b/website/content/en/status/report-2022-10-2022-12/cheribsd.adoc new file mode 100644 index 0000000000..7f70f17729 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/cheribsd.adoc @@ -0,0 +1,32 @@ +=== CheriBSD 22.12 release + +Links: + +link:https://www.cheribsd.org[CheriBSD] URL: link:https://www.cheribsd.org[https://www.cheribsd.org] + +link:https://lists.cam.ac.uk/sympa/info/cl-cheribsd-announce[CheriBSD Announcements list] URL: link:https://lists.cam.ac.uk/sympa/info/cl-cheribsd-announce[https://lists.cam.ac.uk/sympa/info/cl-cheribsd-announce] + +Contact: Brooks Davis <brooks@FreeBSD.org> + +Contact: Edward Tomasz Napierala <trasz@FreeBSD.org> + +Contact: George Neville-Neil <gnn@FreeBSD.org> + +Contact: Jessica Clarke <jrtc27@FreeBSD.org> + +Contact: John Baldwin <jhb@FreeBSD.org> + +Contact: Robert Watson <rwatson@FreeBSD.org> + +Contact: Ruslan Bukin <br@FreeBSD.org> + +CheriBSD extends FreeBSD to implement memory protection and software compartmentalization features supported by the CHERI instruction-set extensions. +There are two active architectural implementations of the CHERI protection model: CHERI-RISC-V and Arm's Morello. +A sketch of CHERI-x86 is also under development. +CheriBSD is a research operating system with a stable baseline implementation into which various new research features have been, or are currently being, merged. + +We have published the 22.12 release of CheriBSD including: + +* A general update of the baseline FreeBSD OS to August 2022. +* Memory-safe adaptation of Direct Rendering Manager (DRM) and Panfrost device driver, which enable a Morello-based desktop system using on-board GPU and HDMI. +These drivers may be used with hybrid or pure-capability kernels. +* An initial set of graphics and desktop CheriABI software packages such as Wayland and portions of KDE to get you up and running with a memory-safe desktop environment. +These components remain under active development, and we anticipate continuing package updates after the CheriBSD release. +* An early research prototype of link:https://github.com/CTSRD-CHERI/cheripedia/wiki/Library-based-Compartmentalisation[library-based compartmentalization], which implements an alternative run-time linker running shared objects in libraries. +This implementation is very much a work-in-progress, and is provided to enable research at other collaborator institutions needing easy access to the prototype. +It is neither complete nor intended to be secure. +* Improved pluggability of experimental heap temporal memory-safety support, which is not yet merged into the main development branch, but will now be easier to use by downloading an alternative kernel and heap allocator libraries provided by Microsoft. +* An updated version of GDB with support for Morello instructions and inspecting memory tags. +* Alpha support for ZFS file systems including support for boot environments. diff --git a/website/content/en/status/report-2022-10-2022-12/ci.adoc b/website/content/en/status/report-2022-10-2022-12/ci.adoc new file mode 100644 index 0000000000..1136a051b6 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/ci.adoc @@ -0,0 +1,53 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[https://ci.FreeBSD.org] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[https://artifact.ci.FreeBSD.org] + +link:https://wiki.FreeBSD.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.FreeBSD.org/Jenkins[https://wiki.FreeBSD.org/Jenkins] + +link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[https://wiki.FreeBSD.org/HostedCI] + +link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[https://wiki.FreeBSD.org/3rdPartySoftwareCI] + +link:https://preview.tinyurl.com/y9maauwg[Tickets related to freebsd-testing@] URL: link:https://preview.tinyurl.com/y9maauwg[https://preview.tinyurl.com/y9maauwg] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[https://github.com/freebsd/freebsd-ci] + +link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[https://lists.FreeBSD.org/subscription/dev-ci] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +The FreeBSD CI team maintains the continuous integration system of the FreeBSD project. +The CI system checks the committed changes can be successfully built, then performs various tests and analysis over the newly built results. +The artifacts from those builds are archived in the link:https://artifact.ci.FreeBSD.org[artifact server] for further testing and debugging needs. +The CI team members examine the failing builds and unstable tests and work with the experts in that area to fix the code or adjust test infrastructure. + +During the fourth quarter of 2022, we continued working with the contributors and developers in the project to fulfill their testing needs and also keep collaborating with external projects and companies to improve their products and FreeBSD. + +Important completed tasks: + +* link:https://ci.FreeBSD.org/job/FreeBSD-main-amd64-gcc9_build/[FreeBSD-main-amd64-gcc9_build] now sends failing reports to the committers whose commits may be related. +* link:https://ci.FreeBSD.org/job/FreeBSD-main-amd64-gcc12_build/[FreeBSD-main-amd64-gcc12_build] has been added. +* link:https://ci.FreeBSD.org/job/FreeBSD-main-powerpc64-images/[FreeBSD-main-powerpc64-images] now also builds bootable APM disk image for Apple G5 baremetal and QEMU -M mac99 (by alfredo@) + +Work in progress tasks: + +* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) +* Designing and implementing use of CI cluster to build release artifacts as release engineering does +* Simplifying CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository +* Improving the hardware test lab and adding more hardware for testing + +Open or queued tasks: + +* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] +* Setting up public network access for the VM guest running tests +* Implementing use of bare-metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Adding more external toolchain related jobs +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://preview.tinyurl.com/y9maauwg[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort! + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/cloud-init.adoc b/website/content/en/status/report-2022-10-2022-12/cloud-init.adoc new file mode 100644 index 0000000000..ead9082e65 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/cloud-init.adoc @@ -0,0 +1,23 @@ +=== FreeBSD as a Tier 1 cloud-init Platform + +Links: + +link:https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[https://cloud-init.io/] + +link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[https://cloudinit.readthedocs.io/en/latest/] + +link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[cloud-init ongoing refactorization] URL: link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst] + +Contact: Mina Galić <me+FreeBSD@igalic.co> + +cloud-init is the standard way of provisioning servers in the cloud. +Unfortunately, cloud-init support for operating systems other than Linux is rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform. +To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support. +The broader plan is to lift support across all BSDs. + +The first milestone has been delivered. +Along with many bug fixes, we now have link:https://github.com/canonical/cloud-init/pull/1779[merged] an man:ifconfig[8] parser, which allows us to retrieve all the information of all network devices, similarly to how on Linux this is done by parsing the contents of `/sys/class/net/<dev>/`. +In the coming weeks, this project will align itself with the Azure developers to do some crucial refactoring. +This will move our new parser further into cloud-init's main execution paths. + +People interested in helping with the project can help with testing new features and fixes through package:net/cloud-init-devel[], which will be updated whenever we make significant commits. +Further, people with access to, and experience with, OpenBSD and NetBSD are also highly welcome to help. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/clusteradm.adoc b/website/content/en/status/report-2022-10-2022-12/clusteradm.adoc new file mode 100644 index 0000000000..9c6697be91 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/clusteradm.adoc @@ -0,0 +1,74 @@ +=== Cluster Administration Team + +Links: + +link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[https://www.freebsd.org/administration/#t-clusteradm] + +Contact: Cluster Administration Team <clusteradm@FreeBSD.org> + +FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications. + +In this quarter, the team has worked on the following: + +* Regular cluster-wide software upgrades + +Two full upgrades to fix and prevent some impacting issues (FreeBSD-EN-22:25.tcp and FreeBSD-EN-22:28.heimdal). +* Regular support for FreeBSD.org user accounts +* Regular disk and parts support (and replacement) for all physical hosts and mirrors. +* Site audit at our primary site +** Inventory of spares and other miscellanea occupying space in our cabinets. +** Inventory of PDUs/power outlet usage and identifying faulty PSUs. +* Identify and fix major DNS issue impacting the project + +The primary DNS servers hosted on HE.net suffered outages for a few days, and new DNS servers were deployed worldwide. +We thank our sponsor link:https://www.metapeer.com/[Metapeer] for providing anycast infrastructure. +* Deploy a new mirror in Frankfurt, Germany + +A replacement for our mirror in Amsterdam (site decommissioned). +Former and new mirror hosted and sponsored by link:https://deploy.equinix.com/[Equinix]. +* Reuse parts of three broken CI machines + +No replacements for these at this moment, awaiting a cluster refresh soon. +* Work with the PowerPC team to improve the PowerPC cluster machines +** Parts like mainboard, NVMe and Power 9 CPU bought through the FreeBSD Foundation. +** Former package builder fixed, and re-deployed as powerpc and powerpc64 package builder. +** Former devref machine reinstalled as a new powerpc64le package builder. +** The cluster has now only these two PowerPC machines in operation. +* Several rounds to free up disk space usage in the cluster machines +* Setup of an experimental search engine for the mailing lists: https://lists.freebsd.org/search +* Fix a bug in the mailing lists archiver, which resulted in some broken links + +All mailing lists archives have been regenerated. + +Work in progress: + +* Large-scale network upgrade at our primary site + +New link:https://www.juniper.net/[Juniper] switches arrived at our primary site to replace the former ones. +We thank link:https://www.juniper.net/[Juniper] for the donation. +* Replace old servers in our primary site and a few mirrors + +Besides the broken CI servers, we have a few old servers with broken disks and faulty PSUs. +This task is in conjunction with the FreeBSD Foundation and donors/sponsors. +* Create a new database for the mailing list search engine to allow searching for mail in the archives from mailman's time + +FreeBSD Official Mirrors Overview: + +Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Taiwan, United Kingdom (full mirror site), United States of America (California, New Jersey [the primary site], and Washington). + +The hardware and network connection have been generously provided by: + +* https://www.bytemark.co.uk/[Bytemark Hosting] +* https://www.bbtower.co.jp[Cloud and SDN Laboratory at BroadBand Tower, Inc] +* https://www.cs.nycu.edu.tw[Department of Computer Science, National Yang Ming Chiao Tung University] +* https://deploy.equinix.com[Equinix] +* https://internet.asn.au/[Internet Association of Australia] +* https://www.isc.org/[Internet Systems Consortium] +* https://www.inx.net.za[INX-ZA] +* https://www.kddi-webcommunications.co.jp/[KDDI Web Communications Inc] +* https://myren.net.my[Malaysian Research & Education Network] +* https://www.metapeer.com[Metapeer] +* https://www.nyi.net/[New York Internet] +* https://nic.br[Nic.br] +* https://your.org[Your.org] + +The Frankfurt single server mirror is now the primary Europe mirror in bandwidth and usage. + +We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site. + +We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch. +United States (West Coast) and Europe (anywhere) are preferable places. + +See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site. diff --git a/website/content/en/status/report-2022-10-2022-12/core.adoc b/website/content/en/status/report-2022-10-2022-12/core.adoc new file mode 100644 index 0000000000..601f5983ca --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/core.adoc @@ -0,0 +1,32 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team <core@FreeBSD.org> + +The FreeBSD Core Team is the governing body of FreeBSD. + +==== Items + +===== Core Team Charter + +A delegation of the current core team is working together with some members of the previous Core Team to draft a core team charter. +There was a face-to-face meeting in the US on December 3 - 4 to discuss the new charter. +The delegation will present to the rest of the core team and discuss the details in the first quarter of 2023. +The same delegation also had a meeting with the FreeBSD Foundation board on December 5th to discuss the collaboration details. + +===== Experimental Matrix IM solution + +The core team is working on evaluating Matrix as an instant messaging tool for the project. +This will make the project's communication channels less dependant on third parties. +The service will be made available to the FreeBSD community to test and evaluate its validity at a later date. + +===== Committer's Guide + +Deprecate BSD-2-Clause-FreeBSD and use BSD-2-Clause. +For more information please refer to the link:https://cgit.freebsd.org/doc/commit/?id=a6e5d24925949785122a9f37f163d58239fd5484[commit]. + +==== Commit bits + +* Core approved the src commit bit for Zhenlei Huang (zlei@) +* Core approved the src commit bit for Corvin Köhne (corvink@) +* Core approved the src commit bit for Sumit Saxon (ssaxena@) +* Core approved the restore of the source commit bit for Paweł Jakub Dawidek (pjd@). diff --git a/website/content/en/status/report-2022-10-2022-12/ddb_ctf.adoc b/website/content/en/status/report-2022-10-2022-12/ddb_ctf.adoc new file mode 100644 index 0000000000..a479c73dac --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/ddb_ctf.adoc @@ -0,0 +1,15 @@ +=== Adding basic CTF support to ddb + +Links: + +link:https://reviews.freebsd.org/D37898[Differential 1] URL: link:https://reviews.freebsd.org/D37898[https://reviews.freebsd.org/D37898] + +link:https://reviews.freebsd.org/D37899[Differential 2] URL: link:https://reviews.freebsd.org/D37899[https://reviews.freebsd.org/D37899] + +Contact: Bojan Novković <bojan.novkovic@kset.org> + +The goal of this project was to extend the ddb kernel debugger to use the kernel's Compact C Type Format (CTF) data and use the newly added features to implement a pretty-printing command in ddb. + +Due to a restrictive execution environment (no IO or memory allocation), ddb can not use existing kernel linker methods to retrieve the kernel's CTF data. +Instead, the first patch adds the ability to load the kernel's CTF data during boot and adds a new kernel linker method used for accessing CTF data from ddb. +The second patch adds a basic interface for using CTF data in ddb and a pretty-printing command built using the newly added interfaces. + +Any feedback, comments, and reviews are welcome and would be greatly appreciated. diff --git a/website/content/en/status/report-2022-10-2022-12/doceng.adoc b/website/content/en/status/report-2022-10-2022-12/doceng.adoc new file mode 100644 index 0000000000..7cd1aab35c --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/doceng.adoc @@ -0,0 +1,92 @@ +//// +Quarter: 4th quarter of 2022 +Prepared by: fernape +Reviewed by: carlavilla@ +Last edit: +Version: +//// + +=== Documentation Engineering Team + +Links: + +link:https://www.freebsd.org/docproj/[FreeBSD Documentation Project] URL: link:https://www.freebsd.org/docproj/[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/[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[https://www.freebsd.org/administration/#t-doceng] + +Contact: FreeBSD Doceng Team <doceng@FreeBSD.org> + +The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. + +During the last quarter: + +* crees@ and zeising@ doc bits were taken in for safekeeping. + +Items pending and in the discussion: + +* link:https://cgit.freebsd.org/doc/commit/?id=4c50528a8678246a6d01765acac8c395434b8c7e[A new document about licensing] has been added to the documentation set. + +==== Porter's Handbook: + +Two new `USES` knobs have been added to the Handbook: + +* link:https://cgit.freebsd.org/doc/commit/?id=0870d76e67a3a4ca2d1169e0fbc0cd8e5b378f7f[New USES = luajit]. +* link:https://cgit.freebsd.org/doc/commit/?id=c94edcebb622c4a35405f591f242132db534cd7b[New USES = llvm]. + +Also: + +* link:https://cgit.freebsd.org/doc/commit/?id=f55bb91726b6ad07362bf8aedb6a3aa9d62bd41f[Erlang facilities] have been documented +* link:https://cgit.freebsd.org/doc/commit/?id=ef23f41eb565c84fc675bc9dbf1810e51c616799[The new CABAL_REVISION knob] has been documented. + +==== FreeBSD Translations on Weblate + +Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] + +Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] + +===== Q4 2022 Status + +* 12 languages +* 150 registered users + +===== Languages + +* Chinese (Simplified) (zh-cn) (progress: 8%) +* Chinese (Traditional) (zh-tw) (progress: 4%) +* Dutch (nl) (progress: 1%) +* French (fr) (progress: 1%) +* German (de) (progress: 1%) +* Indonesian (id) (progress: 1%) +* Italian (it) (progress: 4%) +* Norwegian (nb-no) (progress: 1%) +* Persian (fa-ir) (progress: 3%) +* Portuguese (pt-br) (progress: 16%) +* Spanish (es) (progress: 19%) +* Turkish (tr) (progress: 2%) + +We want to thank everyone who contributed by translating or reviewing documents. + +And please, help promote this effort on your local user group; we always need more volunteers. + +==== FreeBSD Website Revamp - WebApps working group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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 will be 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-2022-10-2022-12/freebsd-foundation.adoc b/website/content/en/status/report-2022-10-2022-12/freebsd-foundation.adoc new file mode 100644 index 0000000000..504c03b973 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/freebsd-foundation.adoc @@ -0,0 +1,121 @@ +=== FreeBSD Foundation + +Links: + +link:https://www.freebsdfoundation.org[FreeBSD Foundation] URL: link:https://www.freebsdfoundation.org[https://www.freebsdfoundation.org] + +link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[https://freebsdfoundation.org/blog/technology-roadmap/] + +link:https://www.freebsdfoundation.org/donate/[Donate] URL: link:https://www.freebsdfoundation.org/donate/[https://www.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/[https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/] + +link:https://www.freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.freebsdfoundation.org/journal/[https://www.freebsdfoundation.org/journal/] + +link:https://www.freebsdfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.freebsdfoundation.org/news-and-events/[https://www.freebsdfoundation.org/news-and-events/] + +Contact: Deb Goodkin <deb@FreeBSDFoundation.org> + +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. +Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. +We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. +We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. + +==== Fundraising Efforts + +Thank you to everyone who made a financial contribution in 2022! +We're still tallying up the totals and will have final numbers soon. +Unfortunately, we did not meet our fundraising goal, which reinforced our need of having someone who can focus on encouraging organizations to invest in FreeBSD. +We will bring someone on board soon to help with that effort. + +In this Quarterly Status report you'll read about many of the areas we funded in Q4 to improve FreeBSD and advocate for the Project (the two main areas we spend money on). +Check out reports on the internally and externally funded projects like Openstack on FreeBSD, Enabling Snapshots on Filesystems Using Journaled Soft Updates, FreeBSD as a Tier 1 cloud-init Platform, and FreeBSD/riscv64 Improvements. +In addition, we provided tons of community engagement and education opportunities virtually and in-person! + +If you want to help us continue our efforts, please consider making a donation towards our 2023 fundraising campaign! +link:https://www.freebsdfoundation.org/donate/[https://www.freebsdfoundation.org/donate/] + +We also have a Partnership Program for larger commercial donors. +You can read about it at link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/]. + +==== OS Improvements + +During the last quarter of 2022, 218 src, 45 ports, and 12 doc tree commits identified the Foundation as a sponsor. +Work was committed under Foundation sponsorship to repositories outside of FreeBSD as well, e.g., to the cloud-init project. +Some of this sponsored work is described in separate report entries: + +* FreeBSD as a Tier 1 cloud-init Platform +* OpenStack on FreeBSD project update +* Wireless Report +* Enabling Snapshots on Filesystems Using Journaled Soft Updates + +Other Foundation work in the src tree included: + +- a variety of additions and fixes from Konstantin Belousov including commits to the virtual memory system (e.g., link:https://cgit.freebsd.org/src/commit/?id=ec201dddfbddd3a77dd3f3afc9b007d0e13e7ad1[ec201dd], link:https://cgit.freebsd.org/src/commit/?id=cd086696c2cb6d23bac3bc749836d36a9280ae98[cd08669], and link:https://cgit.freebsd.org/src/commit/?id=d537d1f12e8829faccd395115193b03b578f1176[d537d1f]), and file systems (e.g., link:https://cgit.freebsd.org/src/commit/?id=37aea2649ff707f23d35309d882b38e9ac818e42[37aea26], link:https://cgit.freebsd.org/src/commit/?id=83aff0f08c525ea3c394f3dd6598665cd369d53c[83aff0f], link:https://cgit.freebsd.org/src/commit/?id=860399eb86cc431412bfbce0ab76c6652e5b6c07[860399e], and link:https://cgit.freebsd.org/src/commit/?id=4d903a1a74d9526aba4d177e89c10f97df5662f2[4d903a1]) +- work from Andrew Turner on arm64 such as link:https://cgit.freebsd.org/src/commit/?id=c15085278cb55bd3c1ea252adf5635bb6800b431[an implementation of per-superpage locks] and link:https://cgit.freebsd.org/src/commit/?id=969935b86b179b2b517ab5d35d943fcb761203c1[the addition of support for an array of hwresets] +- more RISC-V improvements from Mitchell Horne, including link:https://cgit.freebsd.org/src/commit/?id=701923e2a4105be606c5263181b6eb6f546f1a84[improvements to parsing of ISA property strings], link:https://cgit.freebsd.org/src/commit/?id=95b1c27069775dd969cd045888b4ea5aeb53cb7f[optimizations to memory allocation], and various documentation additions and improvements +- follow-up commits to Mark Johnston's work to add ZFS Support to makefs(8) (e.g., link:https://cgit.freebsd.org/src/commit/?id=89585511cc052643a774f64f6450d18e7dd51d4a[work to easily provide ZFS-based VM and cloud images] and link:https://cgit.freebsd.org/src/commit/?id=72a1cb05cd230ce0d12a7180ae65ddbba2e0cb6d[automation for better defaults] from Li-Wen Hsu) +- a variety of work from Ed Maste, including link:https://cgit.freebsd.org/src/commit/?id=38a52bd3b5cac3da6f7f6eef3dd050e6aa08ebb3[an ssh update] and link:https://cgit.freebsd.org/src/commit/?id=86edb11e7491e657e6c75ef6814867021665c377[a switch to LLVM objdump]. + +==== Continuous Integration and Quality Assurance + +The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. +You can read about the latest activity for that work in a separate report entry. + +==== FreeBSD Advocacy and Education + +Much of our effort is dedicated to Project advocacy. +This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. +The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. +Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. + +The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. +These events can be BSD-related, open source, or technology events geared towards underrepresented groups. +We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. +This all helps provide a healthy ecosystem. +We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. +We are continuing to attend events both in person and virtual as well as planning the November Vendor Summit. +In addition to attending and planning virtual events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD. + +Check out some of the advocacy and education work we did last quarter: + +* Sponsored the OpenZFS Developer Summit, October 24-25, 2022 in San Francisco, CA + +* Sponsored All Things Open, October 30-November 2, 2022 in Raleigh, NC + +* Sponsored and helped organize the November 2022 FreeBSD Vendor Summit. +link:https://youtube.com/playlist?list=PLugwS7L7NMXwVfBq5eDRky450jp7LTRJj[Videos from the Summit are available]. + +* Held a new FreeBSD Friday: link:https://youtu.be/t2VLTtHYIcA[An Introduction to FreeBSD Services] by Drew Gurkowski + +* Published the link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-fall-2022-update/[Fall] and link:https://freebsdfoundation.org/news-and-events/newsletter/11982/[Winter] Newsletter updates + +* New Blog Posts + +** link:https://freebsdfoundation.org/blog/meet-the-2022-freebsd-google-summer-of-code-students-koichi-imai/[Meet the 2022 FreeBSD Google Summer of Code Students: Koichi Imai] +** link:https://freebsdfoundation.org/blog/meet-the-2022-freebsd-google-summer-of-code-students-bojan-novkovic/[Meet the 2022 FreeBSD Google Summer of Code Students: Bojan Novković] +** link:https://freebsdfoundation.org/blog/keeping-freebsd-secure-learn-the-whys-and-hows-with-the-freebsd-sec-team/[Keeping FreeBSD Secure: Learn the Whys and Hows with the FreeBSD Sec Team] +** link:https://freebsdfoundation.org/blog/the-freebsd-journal-is-still-free/[The FreeBSD Journal is still Free!] +** link:https://freebsdfoundation.org/blog/eurobsdcon-2022-trip-report-muhammad-moinur-rahman/[EuroBSDCon 2022 Trip Report: Muhammad Moinur Rahman] +** link:https://freebsdfoundation.org/blog/eurobsdcon-2022-trip-report-patrick-mcevoy/[EuroBSDCon 2022 Trip Report: Patrick McEvoy] +** link:https://freebsdfoundation.org/blog/fall-foundation-software-development-update/[Fall Foundation Software Development Update] +** link:https://freebsdfoundation.org/blog/invest-in-freebsd/[Invest in FreeBSD] +** link:https://freebsdfoundation.org/blog/2022-in-review-advocacy/[2022 in Review: Advocacy] +** link:https://freebsdfoundation.org/blog/foundation-sponsors-update-to-wireguard-kernel-port-for-freebsd/[Foundation Sponsors Update to WireGuard Kernel Port for FreeBSD] +** link:https://freebsdfoundation.org/blog/2022-in-review-fundraising-update/[2022 in Review: Fundraising Update] +** link:https://freebsdfoundation.org/blog/2022-in-review-software-development/[2022 in Review: Software Development] +** link:https://freebsdfoundation.org/blog/2022-in-review-continuous-integration-and-quality-assurance-update/[2022 in Review: Continuous Integration and Quality Assurance Update] + +* FreeBSD in the news: + +** link:https://freebsdfoundation.org/news-and-events/latest-news/ampere-getting-cloud-native-with-freebsd-on-oci-ampere-a1-with-terraform/[Ampere: Getting Cloud-Native with FreeBSD on OCI Ampere A1 with Terraform] +** link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-is-well-supported-on-4th-gen-amd-epyc-processors/[FreeBSD is Well Supported on 4th Gen AMD EPYC™ Processors] + +* For a quick review of all the Foundation efforts in 2022, check out our link:https://youtu.be/6ybbeFXFm-I[2022 Thank You Video]. + +We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. +As we mentioned previously, the FreeBSD Journal is now a free publication. +Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[https://www.freebsdfoundation.org/journal/]. + +You can find out more about events we attended and upcoming events at link:https://www.freebsdfoundation.org/news-and-events/[https://www.freebsdfoundation.org/news-and-events/]. + +==== 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://www.freebsdfoundation.org[https://www.freebsdfoundation.org] to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2022-10-2022-12/gcc.adoc b/website/content/en/status/report-2022-10-2022-12/gcc.adoc new file mode 100644 index 0000000000..47ed95c948 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/gcc.adoc @@ -0,0 +1,50 @@ +=== GCC on FreeBSD + +Links: + +link:https://gcc.gnu.org[GCC Project] URL: link:https://gcc.gnu.org[https://gcc.gnu.org] + +link:https://gcc.gnu.org/gcc-11/[GCC 11 release series] URL: link:https://gcc.gnu.org/gcc-11/[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/[https://gcc.gnu.org/gcc-12/] + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + + +==== Update GCC default version to 12 + +Thank you very much to antoine@ for running the necessary exp-runs and to all the contributors, maintainers and committers involved in the process. + +As was noted last quarter, for every major version of GCC, FreeBSD usually awaits the release of the second minor version to update GCC default version. +However next time I would like to attempt to update the default version as soon as the first minor version of GCC 13 is out. +The rationale for awaiting the second minor release was to wait for other operating systems (in particular Linux distributions) to find, report, and fix bugs, so that FreeBSD could focus mainly on FreeBSD-specific cases. +But this also meant that upstream software developers only heard from FreeBSD rarely, and mostly when it concerned FreeBSD only, thus our operating system risks being considered minor and unimportant for them. + +My hope is that software authors can value supporting FreeBSD more as the number of its contributions to other projects also increases. +Of course I understand that this will imply more work for all ports maintainers and I will do my best to help them as much as I can. + +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265948[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2659548] + +==== Resolution of a conflict preventing the installation of multiple GCC versions simultaneously + +Now, lang/gcc11 and lang/gcc12 can be installed at the same time. +This was particularly important for the update of the GCC default version, since a few ports have been kept to compile with GCC 11 for now. + +Note however that at the moment only one -devel GCC port at the time can be installed on your system. +This is because I have patched the standard ports only: for the -devel port I expect upstream to fix the issue soon, by using a link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101491[patch submitted by a FreeBSD user] or link:https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html[my own patch], or using some other solution. + +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257060[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257060] + +==== D language + +D is now enabled in lang/gcc11 and lang/gcc11-devel, thanks to diizzy. +I plan to include D support for higher versions of GCC too, but this cannot be done as easily as for GCC 11 due to bootstrapping issues: starting from GCC 12, the D compiler GDC needs a working GDC to be built. + +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266825[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266825] + +==== Crashes with -fsanitize=address + +Software compiled with GCC using the `-fsanitize=address` switch has been reported to crash. +I have fixed the issue for lang/gcc11, lang/gcc11-devel, lang/gcc12, and lang/gcc12-devel. +I am still working on lang/gcc13-devel. + +Use of the address sanitizer requires ASLR to be disabled. +As GCC gets the code that I am modifying from LLVM, and LLVM is also included in the FreeBSD src repository with some patches that improve ASLR detection and automatically re-run programs with ASLR disabled when necessary, I am also merging those patches. + +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751[https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267751] diff --git a/website/content/en/status/report-2022-10-2022-12/golang_riscv64.adoc b/website/content/en/status/report-2022-10-2022-12/golang_riscv64.adoc new file mode 100644 index 0000000000..e61a41b111 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/golang_riscv64.adoc @@ -0,0 +1,12 @@ +=== go on FreeBSD riscv64 + +Links: + +link:https://github.com/golang/go[golang Home Page] URL: link:https://github.com/golang/go[https://github.com/golang/go] + +link:https://github.com/MikaelUrankar/go/tree/freebsd_riscv64[FreeBSD riscv64 github repo] URL: link:https://github.com/MikaelUrankar/go/tree/freebsd_riscv64[https://github.com/MikaelUrankar/go/tree/freebsd_riscv64] + +link:https://github.com/golang/go/issues/53466[FreeBSD riscv64 golang issue] URL: link:https://github.com/golang/go/issues/53466[https://github.com/golang/go/issues/53466] + +Contact: Mikaël Urankar <mikael@FreeBSD.org> + +Contact: Dmitri Goutnik <dmgk@FreeBSD.org> + +The proposal to add support for FreeBSD riscv64 has been accepted and the patches merged. +golang on FreeBSD riscv64 will be available in golang v1.20 (to be released in February 2023). diff --git a/website/content/en/status/report-2022-10-2022-12/intro.adoc b/website/content/en/status/report-2022-10-2022-12/intro.adoc new file mode 100644 index 0000000000..24751438ea --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/intro.adoc @@ -0,0 +1,11 @@ +The New Year has started and here is the last status report of 2022, including 34 reports. +You will also notice that for the first time a new category has been introduced: the Cloud category. +As FreeBSD keeps up to date with the latest technologies in IT, projects dealing with the cloud make steady improvements, and thus it has been judged that they deserve their own category in the status reports. + +The new category is not the only change about status reports. +Indeed, the status team is revisiting its own workflow to become more efficient. +If you are a report submitter, please ensure to read carefully the report authored by the status team as well as the next Call for Reports emails to keep up with the most recent changes. + +Have a nice read. + +Lorenzo Salvadore, on behalf of the status team. diff --git a/website/content/en/status/report-2022-10-2022-12/kde.adoc b/website/content/en/status/report-2022-10-2022-12/kde.adoc new file mode 100644 index 0000000000..c36dc83dae --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/kde.adoc @@ -0,0 +1,35 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[https://freebsd.kde.org/] + +link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL: link:https://community.kde.org/FreeBSD[https://community.kde.org/FreeBSD] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. +The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine. +The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack. + +==== Infrastructure + +* CMake ports now share a single version number. Various build-flags have been updated for FreeBSD ports builds: under some circumstances, release-flags were ignored and debug-flags applied, which is undesirable. CMake now also refuses to fetch remote sources during a ports build. +* Qt versions are now Qt 5.15.7 (used by KDE) and Qt 6.4.1. Some applications in the ports tree are now "flavored" for Qt5 and Qt6. + +==== KDE Stack + +KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. +These (large) updates land shortly after their upstream release and are not listed separately. + +* KDE Frameworks 5 is now at version 5.101 (latest monthly release from December 2022). This is likely one of the last "Frameworks 5" releases, as the next major series comes closer. +* KDE Gear is now version 22.12.0 (update for December 2022). +* KDE Plasma is now version 5.24.7 (update for October 2022). + +Note that KDE Plasma 5.25 has been released upstream, but is still waiting on fixes before it can land in the ports tree (for example, link:https://bugs.kde.org/show_bug.cgi?id=458356[this KActivityManager bug] in KDE's bug-tracker). + +==== Related Ports + +* package:graphics/krita[] is now version 5.1.3. +* package:graphics/poppler[] was updated multiple times, now at version 22.11. It supports Qt5 and Qt6 through separate ports. +* package:net-im/telegram-desktop[] was now supports Qt5 and Qt6 through flavors. diff --git a/website/content/en/status/report-2022-10-2022-12/netlink.adoc b/website/content/en/status/report-2022-10-2022-12/netlink.adoc new file mode 100644 index 0000000000..b9b307ac96 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/netlink.adoc @@ -0,0 +1,45 @@ +=== Netlink on FreeBSD + +Links: + +link:https://reviews.freebsd.org/D36002[Initial review] URL: link:https://reviews.freebsd.org/D36002[https://reviews.freebsd.org/D36002] + +link:https://static.ipfw.ru/files/netlink.pdf[Netlink talk] URL: link:https://static.ipfw.ru/files/netlink.pdf[https://static.ipfw.ru/files/netlink.pdf] + +Contact: Alexander Chernikov <melifaro@FreeBSD.org> + +Netlink is a communication protocol defined in RFC 3549. +It is an async, TLV-based protocol, providing 1-1 and 1-many communications between kernel and userland. +Netlink is currently used in the Linux kernel to modify, read and subscribe for nearly all networking states. +Interface state, addresses, routes, firewall, rules, fibs, etc, are controlled via Netlink. + +==== Why is Netlink important for FreeBSD? + +POSIX defines an API for base functions/system calls. +There is no such standard for the plethora of protocol/device-level/subsystem-level ioctls. +Each subsystem/driver invents its own protocol, handling format and compatibility. +Extendability is a notable problem in the networking control plane. +For example, it is extremely hard to add properties to the routing socket messages without breaking compatibility. + +Netlink offers unification by providing a standard communication layer and basic easily-extendable message formatting. +It can serve as a "broker", automatically combining requested data from different sources in a single request (example: interface state dump). +Netlink APIs lower the bar for application developers to support FreeBSD, while providing the desired extendability. + +==== Current status + +Netlink has been committed to HEAD. +The code implements a subset of the `NETLINK_ROUTE` subsystem and `NETLINK_GENERIC` framework. + +`NETLINK_ROUTE` supports add/delete/replace operations for routes, nexthops and link-level addresses. +Partial support exists for the interface addresses and interfaces. + +Linuxulator support for Netlink has been committed to HEAD. +It is possible to use the unmodified ip from iproute2 with routes, nexthops, addresses and interfaces. + +The simple userland library, snl(3), that provides convenient abstractions on the netlink socket, has been committed to HEAD. + +The first third-party software, BIRD, link:https://gitlab.nic.cz/labs/bird/-/commit/1e47b9f203aaaad0fb658d40a1670f1d0437f1f8[added experimental FreeBSD Netlink support]. + +==== Next steps + +* Add Netlink to GENERIC +* Make `netstat/route/arp/ndp/ifconfig` use Netlink interfaces (help is appreciated) +* Add FreeBSD Netlink support to ports of FreeRangeRouting (FRRouting (FRR)). diff --git a/website/content/en/status/report-2022-10-2022-12/openssh.adoc b/website/content/en/status/report-2022-10-2022-12/openssh.adoc new file mode 100644 index 0000000000..0a0374de34 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/openssh.adoc @@ -0,0 +1,15 @@ +=== Base System OpenSSH Update + +Links: + +link:https://www.openssh.com/[OpenSSH] URL: link:https://www.openssh.com/[https://www.openssh.com/] + +link:https://www.openssh.com/txt/release-9.1[OpenSSH 9.1 release notes] URL: link:https://www.openssh.com/txt/release-9.1[https://www.openssh.com/txt/release-9.1] + +Contact: Ed Maste <emaste@freebsd.org> + +OpenSSH, a suite of remote login and file transfer tools, was updated from version 9.0p1 to 9.1p1 in the FreeBSD base system. + +It has been merged to the stable branches, is available in FreeBSD 12.4, and will be in the upcoming FreeBSD 13.2. + +A number of bug fixes and minor improvements have been submitted upstream to OpenSSH, and this process will continue with subsequent updates. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/openstack-on-freebsd.adoc b/website/content/en/status/report-2022-10-2022-12/openstack-on-freebsd.adoc new file mode 100644 index 0000000000..3c085974db --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/openstack-on-freebsd.adoc @@ -0,0 +1,54 @@ +=== OpenStack on FreeBSD + +Links: + +link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[https://www.openstack.org] + +link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[https://github.com/openstack-on-freebsd] + + +Contact: Chih-Hsin Chang <starbops@hey.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +OpenStack is an open-source cloud operating system for different resource types like virtual and bare-metal machines. +Users can spawn FreeBSD instances on the open cloud platform, but it is not currently possible to run the OpenStack control plane on FreeBSD hosts. +This project aims to port key OpenStack components so that FreeBSD can function as an OpenStack host. + +In 2022 Q4, we have almost completed the porting work regarding the crucial OpenStack components. +Most of the components/services composing an essential OpenStack cluster are now able to run on FreeBSD hosts, including: + +* Keystone (identity service) +** keystone server +* Glance (image service) +** glance-api +* Placement (resource tracking and inventory service) +** placement-api +* Neutron (networking service) +** neutron-server +** neutron-metadata-agent +** neutron-dhcp-agent +** neutron-openvswitch-agent +* Nova (compute service) +** nova-api +** nova-conductor +** nova-scheduler +** nova-compute +** nova-novncproxy + +The step-by-step documents for constructing a POC can be found link:https://github.com/openstack-on-freebsd/docs[in the `docs` repository]. + +In its design, most of the OpenStack components provide an abstraction layer for the underlying implementations. +For nova, we choose the combination of the `libvirt` driver with the `bhyve` virtualization type enabled. +For neutron, it is the `openvswitch` mechanism driver. +We solved several runtime dependencies and porting issues against the Libvirt, bhyve, and Open vSwitch combinations with minimal effort. +We still have lots of work to undertake to make the changes back to OpenStack upstream. + +TODOs include: + +* Develop a proper alternative execution path in the `oslo_privsep` module for FreeBSD environments +* Develop a new virtualization type, `bhyve`, for nova-compute's `libvirt` driver +* Develop the IP library for FreeBSD under `neutron/agent/freebsd` + +In the first few weeks of 2023, we will focus on breaking through the last mile of the instance spawn path and wrapping up the documentation regarding POC site construction. +We will also try rebasing the porting work to the master branch of OpenStack (now Xena). + +People interested in helping with the project can first help check the documentation by following the installation guide. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/pantheon.adoc b/website/content/en/status/report-2022-10-2022-12/pantheon.adoc new file mode 100644 index 0000000000..422ada8d08 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/pantheon.adoc @@ -0,0 +1,43 @@ +=== Pantheon desktop on FreeBSD + +Links: + +link:https://elementary.io/[elementary OS] URL: link:https://elementary.io/[https://elementary.io] + +link:https://codeberg.org/olivierd/freebsd-ports-elementary[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-elementary[https://codeberg.org/olivierd/freebsd-ports-elementary] + +Contact: Olivier Duchateau <duchateau.olivier@gmail.com> + +The Pantheon desktop environment is designed for elementary OS. +It builds on GNOME technologies (such as Mutter, GTK 3 and 4) and it is written in Vala. +The goal is to have a new desktop for users. + +*13.1-RELEASE or higher is required*, because several core components depend on package:deskutils/xdg-desktop-portal[]. + +The repository contains Mk/Uses framework `elementary.mk`, official applications, and curated ports which depend on package:x11-toolkits/granite[]. + +Since the previous report, we have been updating its related ports, especially: + +* package:deskutils/elementary-calendar[] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267797[update to 6.1.2] +* package:deskutils/iconbrowser[] +* package:graphics/elementary-photos[] +* package:math/elementary-calculator[] +* package:multimedia/elementary-videos[] +* package:x11/elementary-terminal[] +* package:x11-themes/gnome-icons-elementary[] +* package:x11-toolkits/granite7[]. + +Power manager plugins for top panel (wingpanel) and control center (switchboard) are finished. + +A new switchboard plugin is also available, package:net/switchboard-plug-sharing[]. +Ported *Rygel*, GNOME UPnP/DLNA services. + +Submitted other patches for low level libraries such as: + +* package:print/cups-pk-helper[] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266067[update to 0.2.7] required by package:print/switchboard-plus-printers[] +* package:devel/libgee[] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266585[update to 0.20.6] heavily used by the desktop +* package:sysutils/polkit[] update to 122 (https://reviews.freebsd.org/D37137[D37137]) +* package:sysutils/accountsservice[] update to 22.08.8 (https://reviews.freebsd.org/D37679[D37679]). + +==== Open tasks + +* Improve documentation. +* Continue to work on user settings. diff --git a/website/content/en/status/report-2022-10-2022-12/papers.adoc b/website/content/en/status/report-2022-10-2022-12/papers.adoc new file mode 100644 index 0000000000..e83b7ee077 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/papers.adoc @@ -0,0 +1,19 @@ +=== FreeBSD Presentations and Papers + +Links: + +link:https://papers.FreeBSD.org/[FreeBSD Presentations and Papers] URL: link:https://papers.FreeBSD.org/[https://papers.FreeBSD.org] + +Contact: Allan Jude <allanjude@FreeBSD.org> + +Contact: Greg White <gkwhite@gmail.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: Philip Paeps <philip@FreeBSD.org> + +In this quarter, the presentations and papers from those events have been added: + +* BSDCan 2022 +* EuroBSDCon 2022. + +Open tasks: + +* Find and upload missing FreeBSD related presentations and papers +* Issues listed at link:https://github.com/freebsd/freebsd-papers/issues[Open Issues]. diff --git a/website/content/en/status/report-2022-10-2022-12/portmgr.adoc b/website/content/en/status/report-2022-10-2022-12/portmgr.adoc new file mode 100644 index 0000000000..91d2723194 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/portmgr.adoc @@ -0,0 +1,71 @@ +=== Ports Collection + +Links: + +link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL: link:https://www.FreeBSD.org/ports/[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[https://docs.freebsd.org/en/articles/contributing/#ports-contributing] + +link:http://portsmon.freebsd.org/[FreeBSD Ports Monitoring] URL: link:http://portsmon.freebsd.org/[http://portsmon.freebsd.org/] + +link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[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/[http://ftp.freebsd.org/pub/FreeBSD/ports/ports/] + +Contact: René Ladan <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages (through its subsidiary pkgmgr), and personnel matters. +Below is what happened in the last quarter. + +Currently we have just over 31,000 ports in the Ports Tree. +There are currently close to 2900 open ports PRs of which almost 800 are unassigned. +The last quarter saw 8194 commits by 159 committers on the main branch and 657 commits by 53 committers on the 2022Q4 branch. +Compared to the quarter before, this means a small increase in the number of available ports but also in the number of open PRs and a decreasing number of commits made. + +On the personnel front, we welcomed Ronald Klop (ronald@) and said goodbye to bar@ and bhughes@. +We welcomed pizzamig@ as a new official member after a successful lurking period. +We also welcomed three new lurkers: bofh@, ler@, and ygy@. + +Portmgr split itself up into portmgr and pkgmgr. +The new pkgmgr team, currently consisting of antoine@ and bdrewery@, is responsible for building packages and maintaining the package building cluster. + +Four new USES were introduced: + +* llvm to canonicalize ports dependencies on LLVM +* luajit to select a LuaJIT runtime +* octave to help ports depend on Octave and Octave-Forge +* tex to define dependencies on TeX and its various components. + +The following default versions were bumped: + +* Firebird to 3.0 +* GCC to 12 +* Lazarus to 2.2.4 +* Lua to 5.4 +* PHP to 8.1 +* Samba to 4.13 +* Varnish to 6 +* LuaJIT is new and set at "luajit-openresty" for PowerPC64 and "luajit-devel" for all other architectures. + +Three new features were introduced, PIE, RELRO, and BIND_NOW. +Each port can opt out of them by setting the <feature>_UNSAFE variable. +Users can activate or deactivate them globally by setting WITH_<feature> or WITHOUT_<feature>. + +The following major ports were updated to new versions: + +* Chromium 108.0.5359.124 +* Electron 18.3.11, 19.0.15, and 21.2.0 +* Firefox 108.0.1 +* Firefox-ESR 102.6.0 +* gcc 12 +* KDE Plasma 5.24.7, Frameworks 5.101.0, Applications 22.12.0 +* Qt 5.15.7 and 6.4.1 +* Rust 1.66.0 +* SDL 2.26.1 +* Sway 1.8 +* wlroots 0.16.1 +* Wine 7.0.1. + +The exp-run reports are available again. +During the last quarter, antoine@ ran 38 exp-runs to: + +* test port updates +* change default versions +* identify use of IPPROTO_DIVERT in ports +* support PF_DIVERT in Python for FreeBSD 14. diff --git a/website/content/en/status/report-2022-10-2022-12/portsdb.adoc b/website/content/en/status/report-2022-10-2022-12/portsdb.adoc new file mode 100644 index 0000000000..59ad8e5bd0 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/portsdb.adoc @@ -0,0 +1,32 @@ +=== PortsDB: Program that imports the ports tree into an SQLite database + +Links: + +link:https://github.com/yurivict/freebsd-portsdb/[PortsDB] URL: link:https://github.com/yurivict/freebsd-portsdb/[https://github.com/yurivict/freebsd-portsdb/] + +Contact: Yuri Victorovich <yuri@FreeBSD.org> + +I developed the PortsDB project that imports FreeBSD ports into an SQLite database. +The port is package:ports-mgmt/portsdb[]. + +The database can be fully rebuilt in around 20 minutes, after which it can be quickly (in seconds) updated with new commits. + +The database is currently updated hourly: link:https://people.freebsd.org/%7Eyuri/ports.sqlite[https://people.freebsd.org/~yuri/ports.sqlite]. + +PortsDB can be used to query ports using SQL, as a relational database. +External services like Repology, FreshPorts, Portscout, and other similar services can use PortsDB to access information in the ports tree. + +Users can, for example, easily find their broken ports, or port duplicates, or all ports that they maintain that use gmake, among many other possible queries. +Such queries aren't easy to perform by grepping the ports tree. + +Cross-DB queries are also easy to do. +They can combine PortsDB, /var/db/pkg/repo-FreeBSD.sqlite, and /var/db/pkg/local.sqlite. + +All that needs to be done to run PortsDB is ./import.sh, and then ./update.sh after more commits are pulled into the ports repository. + +The periodic script is provided that can simplify integration with cron. +Multiple ready to use SQL queries are also included. + +One particular immediate problem that PortsDB aims to solve is to fix incorrect FreeBSD port versions displayed by Repology. +Repology uses ports INDEX which is missing some required information. +This leads to Repology not being able to distinguish between real versions, and intermediate and made-up versions. +PortsDB should allow Repology to solve this problem. diff --git a/website/content/en/status/report-2022-10-2022-12/pot.adoc b/website/content/en/status/report-2022-10-2022-12/pot.adoc new file mode 100644 index 0000000000..9868faa5dc --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/pot.adoc @@ -0,0 +1,29 @@ +=== Containers and FreeBSD: Pot, Potluck and Potman + +Links: + +link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[https://github.com/bsdpot] + +Contact: Luca Pizzamiglio (Pot) <pizzamig@freebsd.org> + +Contact: Stephan Lichtenauer (Potluck) <sl@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@freebsd.org> + +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]. + +During the last quarter, link:https://github.com/bsdpot/pot/releases/tag/0.15.4[pot 0.15.4] was released. +It again contains a number of improvements like signing pot images as well as many bug fixes. +Also, we welcome two new pot contributors: link:https://github.com/zilti[@zilti] and link:https://github.com/reezer[@reezer]. + +Additionally, there is a new link:https://galaxy.ansible.com/zilti/pot[Ansible pot collection] available. + +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. + +As you can see, we link:https://github.com/bsdpot/potluck/commits/master[had a busy quarter again], this time including improvements to the link:https://github.com/bsdpot/potluck/tree/master/nextcloud-nginx-nomad[Nextcloud] as well as link:https://github.com/bsdpot/potluck/tree/master/jitsi-meet[Jitsi] images. + +Furthermore, we landed pot-based FreeBSD support for sccache-dist server (the server component for distributed compilation of rust and C++ using sccache) and it will be part of the upcoming sccache 0.4.0, see link:https://github.com/mozilla/sccache/pull/1184[mozilla/sccache#1184]. +Once released, this will become available through devel/sccache. + +This means one can build rust projects on FreeBSD targeting a cluster of machines, something that could potentially be integrated into poudriere as well. + +Last but not least, link:https://www.youtube.com/watch?v=b0IB0mc2KTE[Luca's EuroBSDCon 2022 talk] is now available on YouTube. + +As always, feedback and patches are welcome. diff --git a/website/content/en/status/report-2022-10-2022-12/pytest-for-atf.adoc b/website/content/en/status/report-2022-10-2022-12/pytest-for-atf.adoc new file mode 100644 index 0000000000..0d2653aa92 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/pytest-for-atf.adoc @@ -0,0 +1,28 @@ +=== Pytest support for the FreeBSD testing framework + +Links: + +link:https://reviews.freebsd.org/D31084[Initial review] URL: link:https://reviews.freebsd.org/D31084[https://reviews.freebsd.org/D31084] + +link:https://cgit.freebsd.org/src/tree/tests/examples/test_examples.py[Test examples] URL: link:https://cgit.freebsd.org/src/tree/tests/examples/test_examples.py[https://cgit.freebsd.org/src/tree/tests/examples/test_examples.py] + +Contact: Alexander Chernikov <melifaro@FreeBSD.org> + +Native pytest support for man:atf[7] enhances the capabilities of the FreeBSD test suite. + +Pytest simplifies test writing by reducing the amount of boiler-plate code. +It offers several advantages over the existing atf-c and atf-shell bindings. +One of the most important ones is the test parametrization, which allows improving coverage with writing nearly no code. +The other is a rich assert system, offering detailed errors description. +Python man:atf[7] support comes with a number of libraries that abstract a number of commonly-used tasks. +For example, running a test within a VNET jail with man:epair[4] requires adding a single line of code. +Such helpers are especially handy in the networking area, where tests with complex VNET setups are not uncommon. + +==== Current status + +Python support has been committed to HEAD. +Currently, ~80 tests use the Python framework and the number is rising. +Example tests have been committed to show the handling of the typical cases. + +==== Next steps + +* Work on increasing the adoption of the framework +* Rewrite some of the older Python/shell tests in the netinet[6] to pytest (help is appreciated) diff --git a/website/content/en/status/report-2022-10-2022-12/releng.adoc b/website/content/en/status/report-2022-10-2022-12/releng.adoc new file mode 100644 index 0000000000..6a7ff7ec9b --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/releng.adoc @@ -0,0 +1,24 @@ +=== FreeBSD Release Engineering Team + +Links: + +link:https://www.freebsd.org/releases/12.4R/schedule/[FreeBSD 12.4-RELEASE schedule] URL: link:https://www.freebsd.org/releases/12.4R/schedule/[https://www.freebsd.org/releases/12.4R/schedule/] + +link:https://www.freebsd.org/releases/12.4R/announce/[FreeBSD 12.4-RELEASE announcement] URL: link:https://www.freebsd.org/releases/12.4R/announce/[https://www.freebsd.org/releases/12.4R/announce/] + +link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[https://www.freebsd.org/releases/13.2R/schedule/] + +link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[https://www.freebsd.org/releases/14.0R/schedule/] + +link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[https://download.freebsd.org/snapshots/ISO-IMAGES/] + +Contact: FreeBSD Release Engineering Team <re@FreeBSD.org> + +The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. + +During the fourth quarter of 2022, the Release Engineering Team completed work on the 12.4-RELEASE cycle. +This is the final release from the stable/12 branch. +During the release cycle, only one BETA build and two RC (release candidate) builds were needed; overall the release cycle went very smoothly and the release took place on December 5th. + +During the fourth quarter of 2022, the Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/13*, and *stable/12* branches. + +In the first quarter of 2023, the Release Engineering Team will start work on the upcoming 13.2-RELEASE. + +Sponsors: + +Rubicon Communications, LLC ("Netgate") + +The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/riscv.adoc b/website/content/en/status/report-2022-10-2022-12/riscv.adoc new file mode 100644 index 0000000000..a2fe509ea5 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/riscv.adoc @@ -0,0 +1,32 @@ +=== FreeBSD/riscv64 Improvements + +Links: + +link:https://wiki.freebsd.org/riscv[Wiki Homepage] URL: link:https://wiki.freebsd.org/riscv[https://wiki.freebsd.org/riscv] + +Contact: Mitchell Horne <mhorne@FreeBSD.org> + +The FreeBSD/RISC-V project is providing support for running FreeBSD on the link:https://riscv.org[RISC-V Instruction Set Architecture]. + +This quarter I resumed work on improvements to FreeBSD's RISC-V architecture support (riscv64). +Work was focused primarily on small bug-fixes and improvements, and tooling. +A handful of known panics and bug reports were fixed and closed. + +On the performance tooling side, some issues with the use of DTrace on riscv64 were found and addressed. +Specifically, backtraces produced by the `stack()` function were not being captured correctly. +First, a change was made to the compiler flags to ensure that kernel modules always make use of the frame pointer, so that unwinding the kernel stack works as expected. +Second, some tweaks were made to machine-dependent DTrace code in the `profile` and `fbt` providers, making the correct number of frames appear in each backtrace. +Now, DTrace can be used to accurately capture profiling data on this platform, enabling the generation of flamegraphs. + +I also began porting the `hwpmc(4)` driver to run on this platform. +Unlike other ISAs, RISC-V does not standardize the set of counter events that a CPU must support, nor are the programmable event selection registers accessible to the kernel. +To work around this, there is an link:https://github.com/riscv-non-isa/riscv-sbi-doc/blob/master/riscv-sbi.adoc#performance-monitoring-unit-extension-eid-0x504d55-pmu[SBI "Performance Monitoring Unit" extension] which provides an abstracted interface for managing such functionality. +The new `hwpmc(4)` class is written to use this interface. +Current generation RISC-V hardware supports incrementing performance counters, but lacks the counter overflow interrupts required to enable sampling PMCs. + +Work is expected to continue next quarter. +Aside from the in-progress items mentioned, focus will be given to the following areas: + +* Support for newer OS-level extensions such as Page-Based Memory Types (Svpbmt) +* Profiling system performance. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/status.adoc b/website/content/en/status/report-2022-10-2022-12/status.adoc new file mode 100644 index 0000000000..dcc1682c0a --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/status.adoc @@ -0,0 +1,61 @@ +=== Status reports: New workflow + +Links: + +link:https://www.freebsd.org/status/[FreeBSD status reports] URL: link:https://www.freebsd.org/status/[https://www.freebsd.org/status/] + +link:https://github.com/freebsd/freebsd-quarterly[Status reports GitHub repository] URL: link:https://github.com/freebsd/freebsd-quarterly[https://github.com/freebsd/freebsd-quarterly] + +Contact: <status@FreeBSD.org> + +==== Goals of the new workflow + +This quarter the status team has been discussing with doceng@ some improvements to its workflow. +In particular, the team is attempting to merge its GitHub repository into the FreeBSD doc/ repository. + +Here are the reasons for such a change: + +* having two independent repositories requires spending some time to make sure that both are in sync, which is being done manually. +See for example commits such as link:https://github.com/freebsd/freebsd-quarterly/commit/4b8255e604dd0513e841aa8f3dce7741e78b999c[https://github.com/freebsd/freebsd-quarterly/commit/4b8255e604dd0513e841aa8f3dce7741e78b999c], which are not immediately clear in their commit messages about what is being done unless more time is invested to copy commit messages properly; + +* the FreeBSD doc/ repository is self-hosted, while the status repository is hosted on GitHub. +Since the contents of the self-hosted repository are mirrored, nothing is being lost in visibility with the repository merging. + +Some inconsistencies about the name of the team have also been found: the team has been referred to as "quarterly", "quarterly status team", "status", "status team", "monthly" etc. +So this issue is also being addressed. + +Please note that we are still working on these changes and that they might not be completed within the next quarter. +The status team will take care to keep all information about report submissions up to date so that you always know how to submit your reports. + +==== Team naming + +Since "quarterly" might refer to quarterly reports but also to quarterly branches, using "quarterly" only could cause some confusion in some contexts. +"quarterly-status" is likely a bad idea as well, as the frequency of reports publication might need to change in the future. +Thus just "status" has been chosen: this is correct as quarterly status reports contain information about the status of the development of FreeBSD, it is frequency-agnostic and consistent with link:https://www.freebsd.org/status/[its FreeBSD website section]. + +The following link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267813[email addresses have been created]: + +* the main contact address for the status team is now <status@FreeBSD.org>. +Mails sent to `quarterly@FreeBSD.org` will still reach the team, but you are encouraged to use the new address; +* the email address for the status report submissions is now <status-submissions@FreeBSD.org>. +Mails sent to `quarterly-submissions@FreeBSD.org` will still reach the team, but you are encouraged to use the new address; +* the `quarterly-calls` mailing list has been renamed to link:https://lists.freebsd.org/subscription/freebsd-status-calls[status-calls]. +If you were already subscribed to `quarterly-calls`, you do not need to resubscribe. + +==== Report submission + +Three different ways to submit reports will be provided: + +* submitting a review on Phabricator. +A new link:https://reviews.freebsd.org/project/profile/88/[Phabricator group] called "status" link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267812[has been created]. +If you would like to give a hand to the team by reviewing reports we suggest you add yourself to the group 'watchers'; + +* submitting a pull request at link:https://github.com/freebsd/freebsd-doc/pulls[https://github.com/freebsd/freebsd-doc/pulls]; + +* sending an email to `status-submissions@FreeBSD.org`. + +Reviewing processes will proceed as they usually do on each of these channels. + +==== Other changes + +* The repository merging will require reworking some of the existing tools to better integrate with the existent structure of the FreeBSD doc/ repository. + +* The link:https://github.com/freebsd/freebsd-quarterly[status reports GitHub repository] will be archived once the new workflow implementation is completed. diff --git a/website/content/en/status/report-2022-10-2022-12/ufs_snapshots.adoc b/website/content/en/status/report-2022-10-2022-12/ufs_snapshots.adoc new file mode 100644 index 0000000000..de625efb1d --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/ufs_snapshots.adoc @@ -0,0 +1,40 @@ +=== Enabling Snapshots on Filesystems Using Journaled Soft Updates + +Links: + +link:https://reviews.freebsd.org/D36491[Milestone 1 Core Changes] URL: link:https://reviews.freebsd.org/D36491[https://reviews.freebsd.org/D36491] + +Contact: Kirk McKusick <mckusick@FreeBSD.org> + +The goal of this project is to make UFS/FFS filesystem snapshots available when running with journaled soft updates. + +First a bit of background. +Soft updates have been available for UFS/FFS since the mid 1990s. +They eliminate the need for most synchronous disk writes and keep the state of the filesystem sufficiently consistent that it can be put back online after a crash without the need to run fsck(8). +However, it may incorrectly assume that some of its blocks are still in use when in fact they are free. +So, eventually it is necessary to take the filesystem offline to run fsck(8) to reclaim these lost blocks. +The time to run fsck(8) is a function of the number of files in the filesystem and the size of the filesystem. +Large filesystems may take hours to complete an fsck(8). + +Enabling journaling reduces the time spent by fsck(8) cleaning up a filesystem after a crash to a few seconds. +With journaling, the time to recover after a crash is a function of the amount of activity in the filesystem in the minute before the crash. +Journaled recovery time is usually only a few seconds and never exceeds a minute. + +The drawback to using journaling is that the writes to its log add an extra write load to the media containing the filesystem. +Thus a write-intensive workload will have reduced throughput on a filesystem running with journaling. + +Like all journaling filesystems, the journal recovery will only fix issues known to the journal. +Specifically if a media error occurs, the journal will not know about it and hence will not fix it. +Thus when using journaling, it is still necessary to run a full fsck every few months or after a filesystem panic to check for and fix any errors brought on by media failure. + +A full fsck(8) is normally done on an offline filesystem. +However, it can be done by running fsck(8) on a snapshot of a live filesystem. +When running fsck(8) in the background on a live filesystem, the filesystem performance will be about half of normal during the time that the background fsck(8) is running. +Running a full fsck on a UFS filesystem is the equivalent of running a scrub on a ZFS filesystem. + +The first milestone of this project has been completed. +It is now possible to take snapshots when running with journaled soft updates and they can be used for doing background dumps on a live filesystem. + +The second milestone of this project is to extend fsck(8) to be able to do a background check using a snapshot on a filesystem running with journaled soft updates. +This milestone is expected by Q3 of 2023. + +Sponsored by: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/vessel-status-report.adoc b/website/content/en/status/report-2022-10-2022-12/vessel-status-report.adoc new file mode 100644 index 0000000000..653231a8fc --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/vessel-status-report.adoc @@ -0,0 +1,40 @@ +=== Vessel - Integrated Application Containers for FreeBSD + +Links: + +link:https://github.com/ssteidl/vessel[Vessel] URL: link:https://github.com/ssteidl/vessel[https://github.com/ssteidl/vessel] + +Contact: Shane Steidley <ssgriffonuser@gmail.com> + +==== What is Vessel? + +The goal of vessel is to expose the many powerful features of FreeBSD to application developers. +Vessel accomplishes this goal by: + +* Providing a "Docker-like" interface familiar to most application developers for building, running, publishing and pulling container images. +* Tightly integrating with FreeBSD system level interfaces (kqueue process tracing, signal handling, devd.seqpacket, rctl, cpuset) to manage running jails. + +==== How is Vessel different from other jail management systems? + +There are some awesome jail management systems already. +These existing systems do a great job of configuring the jail runtime environment (ZFS dataset, networking, resource control, etc). +After the environment is configured though, it is just handed off to the `jail` program via an exec call. + +In addition to jail configuration and creation, Vessel aims to take the next step and implement an event loop to manage jails based on system events. +An instance of vessel runs alongside each jail to assist with management. +This allows "Fat Jails" and single process jails to run in the foreground and be managed by the vessel-supervisor. + +==== Why make Vessel? + +Vessel has been a side project for a few years. +I initially started it because it was a fun hobby project and I was surprised something similar did not already exist. +It has now become a viable tool that I use for all of my projects. +I believe it will be useful to others as well. + +==== Is help needed? + +Help is always appreciated. +It's a fun project to work on because it can touch on so many portions of FreeBSD. + +* Just using it and reporting any bugs on GitHub would be very useful. +* Whatever sounds fun. +I'm happy to help get people started. diff --git a/website/content/en/status/report-2022-10-2022-12/wifi.adoc b/website/content/en/status/report-2022-10-2022-12/wifi.adoc new file mode 100644 index 0000000000..69267c8714 --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/wifi.adoc @@ -0,0 +1,34 @@ +=== Wireless updates + +Links: + +link:https://people.freebsd.org/%7Ebz/wireless/[Bjoern's Wireless Work In Progress landing page] URL: link:https://people.freebsd.org/%7Ebz/wireless/[https://people.freebsd.org/~bz/wireless/] + + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +During the quarter not much work was publicly visible and admittedly slightly slow. +Behind the scenes wireless work was happening on two fronts: + + * 11n, 11ac, and wpa, + + * more drivers and firmware, problems, testing, and filling gaps for these. + +While the main development for newer standards and the Intel iwlwifi driver is sponsored by the FreeBSD Foundation, I find myself spending a lot of private time with Realtek rtw88 and rtw89, Atheros, and Mediatek mt76 (7921 and 7915) drivers now as well. +Testing changes on bare metal and using bhyve VMs using passthru has become more time-consuming, with the amount of supported chipsets increasing, in order not to break other drivers. +Even different (generations of) chipsets supported by the same driver, at times, behave differently with the same change. + +A separate discussion was brought to me about the size of firmware added to the tree for the already existing drivers and the firmware for more drivers coming. +The chicken-egg problem to solve is having firmware available on the release media; without firmware, a lot of modern laptops will not have any sort of outside communications available at the time of install in their default configuration. +This will be a larger discussion to have to also solve firmware for other drivers, but that discussion will be for another day and place. + +Slightly belatedly I have started to push LinuxKPI and 802.11 changes into the tree at the end of the year and that work will continue into early 2023 at which point more of the aforementioned remaining drivers will also hit the tree. + +One of the main remaining problems to solve is the firmware crashes on interface down/up cycles currently experienced with at least two drivers. + +Thankfully during the last weeks, after my call for help, multiple people have stood up wanting to help with various drivers (especially Realtek and Mediatek). +I hope that after me catching up and pushing things out this can accelerate progress again. + +Thanks again to everyone doing testing, providing debug output, sending in feedback, or using the drivers at this point. + +For the latest state of the development, please use the freebsd-wireless mailing list, and check the landing page, which has links to all wiki pages for each driver status. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2022-10-2022-12/xen.adoc b/website/content/en/status/report-2022-10-2022-12/xen.adoc new file mode 100644 index 0000000000..3070e9b08c --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/xen.adoc @@ -0,0 +1,36 @@ +=== FreeBSD/ARM64 on Xen + +Links: + +link:https://www.xenproject.org/[Xen Project] URL: link:https://www.xenproject.org/[https://www.xenproject.org/] + +link:https://wiki.freebsd.org/Xen[FreeBSD wiki page on Xen] URL: link:https://wiki.freebsd.org/Xen[https://wiki.freebsd.org/Xen] + +Contact: Elliott Mitchell <ehem+freebsd@m5p.com> + +Xen is an open source hypervisor. +Xen is one of the earliest hypervisors and has support for many OSes. +Since FreeBSD 8.0, GENERIC FreeBSD/x86 has been able to run on Xen. +Near the time FreeBSD was ported to run on Xen, work was started on running Xen on ARM. +For a number of years Linux has run fine on Xen/ARM, but FreeBSD hasn't been available. + +Having FreeBSD/ARM64 on Xen means any system capable of having Xen can also have FreeBSD in operation. +Of note, the Raspberry PI 4B has hardware (GICv3) which Xen works with. +If you're okay with Linux handling the hardware, you can use all the hardware of a Raspberry PI 4B. + +In 2014 a proof of concept of running FreeBSD/ARM64 on Xen was done by Julien Grall, but this was never polished for release. +During the past 2 years I've been working towards having this in FreeBSD's tree, so released versions of FreeBSD/ARM64 would run on Xen. +At this point all changes which need to be shared with the x86 Xen source code have been reviewed (not all reviews are on Phabricator). +This now awaits testing by Roger Pau Monné before being committed to FreeBSD's tree. + +I now urgently need someone with a high level of familiarity with the interrupt subsystem of FreeBSD on ARM64 to review (and commit) the ARM-specific portions. +My builds are functional far more often than they fail, and most failures are temporary problems in FreeBSD's tree. +Some significant issues will need to be addressed regarding FreeBSD's interrupt subsystem. + +There is substantial hope of having FreeBSD/ARM64 available for "DomU" (unprivileged) operation for FreeBSD 14.0. +There is potential for FreeBSD/ARM and FreeBSD/RISC-V to run on Xen in short order. +No plans currently exist for having FreeBSD/ARM64 operating as the controlling VM (someone could try to sponsor this). + +==== Thanks + +Thanks to Julien Grall <julien@xen.org> for the Proof of Concept. + +Thanks to Roger Pau Monné <royger@FreeBSD.org> for reviewing changes involving x86. + +Thanks to Mitchell Horne <mhorne@FreeBSD.org> for helping with various FreeBSD/ARM64 issues and addressing a key problem with FreeBSD/ARM64. diff --git a/website/content/en/status/report-2022-10-2022-12/xfce.adoc b/website/content/en/status/report-2022-10-2022-12/xfce.adoc new file mode 100644 index 0000000000..5d011bcbda --- /dev/null +++ b/website/content/en/status/report-2022-10-2022-12/xfce.adoc @@ -0,0 +1,18 @@ +=== Xfce on FreeBSD + +Links: + +link:https://xfce.org/about/news/?post=1671062400[Xfce 4.18 Upstream Release Announcement] URL: link:https://xfce.org/about/news/?post=1671062400[https://xfce.org/about/news/?post=1671062400] + +link:https://www.freshports.org/x11-wm/xfce4[Xfce meta-port on FreshPorts] URL: link:https://www.freshports.org/x11-wm/xfce4[https://www.freshports.org/x11-wm/xfce4] + +Contact: Xfce team <xfce@FreeBSD.org> + +Contact: Guido Falsi <madpilot@FreeBSD.org> + +The FreeBSD Xfce team (xfce@) works to ensure the Xfce desktop environment is maintained and fully functional on FreeBSD. + +This quarter the Xfce team members are pleased to welcome Xfce 4.18 to the FreeBSD ports tree! + +This new release includes many improvements in various parts of the environment, especially in the Thunar file manager. + +Also various upstream packages now include patches that were present in the ports tree. + +For further details, refer to the link:https://xfce.org/about/news/?post=1671062400[Xfce 4.18 Upstream Release Announcement]. diff --git a/website/content/en/status/report-2023-01-2023-03/_index.adoc b/website/content/en/status/report-2023-01-2023-03/_index.adoc new file mode 100644 index 0000000000..bf901affd9 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/_index.adoc @@ -0,0 +1,163 @@ +--- +title: "FreeBSD Status Report First 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-01-2023-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}/status.adoc[] + +''' + +[[userland]] +== Userland + +{userland-desc} + +include::{reports-path}/daemon.adoc[] + +''' + +[[kernel]] +== Kernel + +{kernel-desc} + +include::{reports-path}/ufs_snapshots.adoc[] + +''' + +include::{reports-path}/kinst.adoc[] + +''' + +include::{reports-path}/timerfd.adoc[] + +''' + +[[architectures]] +== Architectures + +{architectures-desc} + +include::{reports-path}/aarch64-kasan.adoc[] + +''' + +include::{reports-path}/bsd-user.adoc[] + +''' + +[[cloud]] +== Cloud + +{cloud-desc} + +include::{reports-path}/cloud-init.adoc[] + +''' + +include::{reports-path}/openstack-on-freebsd.adoc[] + +''' + +[[documentation]] +== Documentation + +{documentation-desc} + +include::{reports-path}/doceng.adoc[] + +''' + +include::{reports-path}/frdp.adoc[] + +''' + +[[ports]] +== Ports + +{ports-desc} + +include::{reports-path}/freshports.adoc[] + +''' + +include::{reports-path}/drm-drivers.adoc[] + +''' + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/fsx.adoc[] + +''' + +include::{reports-path}/gcc.adoc[] + +''' + +include::{reports-path}/valgrind.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-01-2023-03/aarch64-kasan.adoc b/website/content/en/status/report-2023-01-2023-03/aarch64-kasan.adoc new file mode 100644 index 0000000000..01b46dc37b --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/aarch64-kasan.adoc @@ -0,0 +1,23 @@ +=== Kernel Address Sanitizer on AArch64 + +Contact: Kyle Evans <kevans@FreeBSD.org> + +Sanitizers are bug detection facilities which use a combination of instrumentation inserted by the compiler (LLVM in this case) and runtime state tracking to detect bugs in C code. +They can automatically detect many types of C programming bugs, such as use-after-frees and uses of uninitialized variables, which may otherwise require substantial effort to identify. +They are particularly effective in combination with regression testing suites or fuzzing tools such as link:https://github.com/google/syzkaller[syzkaller]. +Unlike tools such as Valgrind, software must be recompiled to enable a given sanitizer, but sanitizers can be used in the kernel. +Kernels with sanitizers enabled incur a significant performance overhead from the runtime, in both CPU utilization and memory usage. + +As of gitref:89c52f9d59fa[repository=src], the kernel address sanitizer that was previously exclusive to amd64 is ported to arm64. + +Prior testing has been done on a decent variety of machines, including: + +- Various Ampere Altra machines +- QEMU +- Microsoft's "Volterra" Devkit +- bhyve (WIP). + +Further testing on other hardware would be both welcomed and appreciated. + +Sponsor: Juniper Networks, Inc. + +Sponsor: Klara, Inc. diff --git a/website/content/en/status/report-2023-01-2023-03/bsd-user.adoc b/website/content/en/status/report-2023-01-2023-03/bsd-user.adoc new file mode 100644 index 0000000000..987183c59f --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/bsd-user.adoc @@ -0,0 +1,55 @@ +=== bsd-user: Upstreaming and Status Report + +Links: + +link:https://qemu.org[QEMU Project] URL: link:https://qemu.org[] + +link:https://github.com/qemu-bsd-user/qemu-bsd-user[FreeBSD bsd-user qemu fork] URL: link:https://github.com/qemu-bsd-user/qemu-bsd-user[] + +link:https://gitlab.com/qemu-project/qemu[QEMU Project's gitlab mirror] URL: link:https://gitlab.com/qemu-project/qemu[] + +Contact: Warner Losh <imp@FreeBSD.org> + +In this quarter, Warner upstreamed two patch sets in the qemu-project repo (with a third pending). +Doug Rabson submitted some optimizations to save a handle to the qemu-user emulator in the kernel for future exec. +Contact has been made with some folks interested in getting bsd-user working on NetBSD. +Summer of Code project to upstream shows some interest. + +==== Upstreaming Efforts + +The sysctl system call was upstreamed this quarter. +Doug's changes were also upstreamed (see below). +Some cleanups around NetBSD and OpenBSD and to generate syscalls on the fly are pending. + +==== Doug Rabson's Changes + +As part of his container work, Doug submitted changes that allows the kernel to cache the emulator used to run programs. +This allows the kernel to directly exec the new binary with that cached emulator. +This simplifies bsd-user and removes one source of difference between it and linux-user. +Doug also provided an important fix that prevented aarch64 from running. + +==== Bug Fixes and Improvements + +In addition to Doug's fixes, Warner cleaned up things a bit this quarter. + +* Warner removed the final bits of 'run on any BSD code' that was present in the emulator. +* While the basic system calls could be emulated between all the BSDs, their system call interface has diverged too much, and it is too feature rich for this to be feasible any time soon. +* Warner had planned to just remove the NetBSD and OpenBSD bits, but there is some interest from at least the NetBSD folks for making things build. +* Now that the NetBSD folks have contact information, and know direction, Warner hopes they will submit a pull request to build bsd-user on NetBSD for NetBSD. +* Warner added SIGSYS support so that we can catch unimplemented system calls sooner, and improved reporting of them to get more data about what fails. +* Warner cleaned up some code in the `blitz` branch. +* We're merged up to 8.0rc1 in upstream in the `blitz` branch we're using to stay current. + +==== Summer of Code Projects + +There's much interest in the bsd-user upstreaming task Warner added to Qemu's project list. +With luck, we'll have a student to fund to do the job of upstreaming all the system calls needed to run simple programs. +With a lot of luck, we'll be able to run any program that does the same thing(s) that clang does (one goal is to have it compile hello world). +Future quarterly reports will provide details, should we be fortunate enough to get a slot for this. + +==== Help Needed + +We can always use help with bsd-user. + +* Pull requests for new system calls are welcome. +* Automation in generating many of the things we do by hand would be helpful (like system call argument tracing). +* Enthusiastic volunteers who want to help me with the upstreaming (many tasks are easy and quick if you don't want to commit). +* Coordination with the NetBSD folks and cleanup they come up with. +* Bug fixes (especially thread bugs) are needed. diff --git a/website/content/en/status/report-2023-01-2023-03/ci.adoc b/website/content/en/status/report-2023-01-2023-03/ci.adoc new file mode 100644 index 0000000000..10b9d26b2e --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/ci.adoc @@ -0,0 +1,52 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] + +link:https://wiki.FreeBSD.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.FreeBSD.org/Jenkins[] + +link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] + +link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] + +link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] + +link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +In the first quarter of 2023, we worked with the project contributors and developers to address their testing requirements. +Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. + +Important completed tasks: + +* link:https://ci.FreeBSD.org/job/FreeBSD-main-aarch64-KASAN_test/[FreeBSD-main-aarch64-KASAN_test] and its supporting jobs have been added. +* link:https://ci.FreeBSD.org/job/FreeBSD-stable-13-amd64-KASAN_test/[FreeBSD-stable-13-amd64-KASAN_test] and its supporting jobs have been added. +* link:https://ci.FreeBSD.org/job/FreeBSD-main-amd64-gcc12_build/[FreeBSD-main-amd64-gcc12_build] now sends failing reports to the committers whose commits may be related. +* Various fixes or workarounds to the tests of non-x86 architectures from trasz@ +* Present Testing/CI Status Update in link:https://wiki.freebsd.org/DevSummit/202303[AsiaBSDCon 2023 Developer Summit] + +Work in progress tasks: + +* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) +* Designing and implementing use of CI cluster to build release artifacts as release engineering does +* Simplifying CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository +* Improving the hardware test lab and adding more hardware for testing +* Merge https://reviews.freebsd.org/D38815 +* Merge https://reviews.freebsd.org/D36257 + +Open or queued tasks: + +* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] +* Setting up public network access for the VM guest running tests +* Implementing use of bare-metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and don't hesitate to join the effort! + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/cloud-init.adoc b/website/content/en/status/report-2023-01-2023-03/cloud-init.adoc new file mode 100644 index 0000000000..54683f6b46 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/cloud-init.adoc @@ -0,0 +1,31 @@ +=== FreeBSD as a Tier 1 cloud-init Platform + +Links: + +link:https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[] + +link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[] + +link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[cloud-init ongoing refactorization] URL: link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[] + +Contact: Mina Galić <freebsd@igalic.co> + +cloud-init is the standard way of provisioning servers in the cloud. +Unfortunately, cloud-init support for operating systems other than Linux is rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform. +To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support. +The broader plan is to lift support across all BSDs. + +This quarter has been going very, very slowly, for personal reasons -- also for lack of access to the right resources. +I have been trying to link:https://github.com/canonical/cloud-init/pull/2003[port the Infiniband functions]. +This has proven difficult, because it falsified my thesis that man:ifconfig[8] is all that is needed to figure out network interfaces on FreeBSD. + +While waiting for resources, I link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269767[debugged a boot panic] and got it fixed: gitref:499171a98c8813e4dc6e085461d5c47750efa555[repository=src]. +This now makes it possible to boot FreeBSD on LXD -- cloud-init's CI platform. +We still need to fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269823[the high CPU usage problem], but there is already an accepted review: link:https://reviews.freebsd.org/D38898[D38898] + +A cloud-init colleague who works for Azure managed to give me access to an link:https://learn.microsoft.com/en-us/azure/architecture/topics/high-performance-computing[HPC VM on Azure]. +Unfortunately, it was only for a limited time, and that was not enough to figure out how to get Infiniband up and running on FreeBSD — a task handled by link:https://github.com/Azure/WALinuxAgent/[Azure Agent] on Linux, but FreeBSD's package:sysutils/azure-agent[] is rather lacking. + +People interested in helping with this project could provide man:ifconfig[8], man:ibstat[8], man:ibv_devinfo[1], etc… link:https://lists.freebsd.org/archives/freebsd-infiniband/2023-February/000005.html[pastes from their Infiniband systems]. +I would also be very happy about getting access to hardware with Infiniband NICs, or hearing from people who have successfully used FreeBSD on Azure HPC with Infiniband. + +If there is interest in that platform, I will direct some energy to fixing Azure Agent. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/clusteradm.adoc b/website/content/en/status/report-2023-01-2023-03/clusteradm.adoc new file mode 100644 index 0000000000..f10cc05ff6 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/clusteradm.adoc @@ -0,0 +1,59 @@ +=== Cluster Administration Team + +Links: + +link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[] + +Contact: Cluster Administration Team <clusteradm@FreeBSD.org> + +FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications. + +In this quarter, the team has worked on the following: + +* Regular support for FreeBSD.org user accounts. +* Regular disk and parts support (and replacement) for all physical hosts and mirrors. +* Improve the PowerPC package builders. +** With new parts obtained through the FreeBSD Foundation, the builders now have new NVMEs with heatsinks and more memory. +It helped to solve the heat issue, and they are building packages faster now. +* Decouple dynamic resources from the main websites. +** Work in coordination with doceng and webmaster to decouple dynamic resources from the websites, www.FreeBSD.org, and docs.FreeBSD.org. + +==== Work in progress + +* Large-scale network upgrade at our primary site. +** New link:https://www.juniper.net/[Juniper] switches arrived at our primary site to replace the former ones. +We thank Juniper for the donation. +* Replace old servers in our primary site and a few mirrors. +** Besides the broken CI servers, we have a few old servers with broken disks and faulty PSUs. +This task is in conjunction with the FreeBSD Foundation and donors/sponsors. +* Deploy infrastructure to mirror the websites. +** Since the FreeBSD website is now mostly static, we have begun deploying infrastructure to mirror www.FreeBSD.org and docs.FreeBSD.org around the world in FreeBSD project-managed mirrors. +* Create a new search database engine for internal FreeBSD.org searching needs like mailing list and docs. + +==== FreeBSD Official Mirrors Overview + +Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Taiwan, United Kingdom (full mirror site), United States of America -- California, New Jersey (primary site), and Washington. + +The hardware and network connection have been generously provided by: + +* https://www.bytemark.co.uk/[Bytemark Hosting] +* Cloud and SDN Laboratory at https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc] +* https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University] +* https://deploy.equinix.com/[Equinix] +* https://internet.asn.au/[Internet Association of Australia] +* https://www.isc.org/[Internet Systems Consortium] +* https://www.inx.net.za/[INX-ZA] +* https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc] +* https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network] +* https://www.metapeer.com/[Metapeer] +* https://www.nyi.net/[New York Internet] +* https://nic.br/[NIC.br] +* https://your.org/[Your.Org]. + +The Frankfurt single server mirror is the primary Europe mirror in bandwidth and usage. + +We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site. + +We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch. +United States (West Coast) and Europe (anywhere) are preferable places. + +See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site. diff --git a/website/content/en/status/report-2023-01-2023-03/core.adoc b/website/content/en/status/report-2023-01-2023-03/core.adoc new file mode 100644 index 0000000000..af73a27605 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/core.adoc @@ -0,0 +1,26 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team <core@FreeBSD.org> + +The FreeBSD Core Team is the governing body of FreeBSD. + +==== Items + +===== Core Team Charter: Draft + +At the first Core Team meeting of 2023, Team delegates from the December 2022 meeting in Boulder, US presented the delegation's conclusions to the entire Team. +The Team will continue to discuss the issues and work together with the FreeBSD Foundation. + +===== FreeBSD annual developers survey + +The Core Team together with the FreeBSD Foundation have decided that the FreeBSD Foundation will be in charge of conducting the annual developers survey. + +===== Matrix IM solution + +The Core Team continues to evaluate Matrix as an IM solution for FreeBSD developers. +An instance has already been prepared and tests are underway. + +==== Commit bits + +* Core approved the src commit bit for Cheng Cui (cc@) +* Core approved the restore of the src commit bit for Joseph Koshy (jkoshy@). diff --git a/website/content/en/status/report-2023-01-2023-03/daemon.adoc b/website/content/en/status/report-2023-01-2023-03/daemon.adoc new file mode 100644 index 0000000000..e941a5cb32 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/daemon.adoc @@ -0,0 +1,27 @@ +=== daemon(8) improvements + +Links: + +man:daemon[8] URL: link:https://man.freebsd.org/daemon/8[] + +link:https://libera.chat/[Libera IRC] URL: link:https://libera.chat/[] + +Contact: Ihor Antonov <mailto:ihor@antonovs.family[]> + +Contact: Kyle Evans <kevans@FreeBSD.org> + +An ongoing effort to improve code quality and supervision capabilities of the `daemon` utility. +Daemon is a tool that can daemonize (send to background) or supervise any running process, automatically restarting it if it crashes. +Daemon is widely used in the ports tree and can be used more in base. + +This quarter `long_opts` support was added and the codebase went through an initial refactoring phase to prepare it for further changes. +There are no functional changes so far but more changes are coming. +Please contact directly or on `#freebsd-dev` on Libera IRC if you encounter unexpected bugs. + +Planned work items for the next quarter: + +- use of kqueue for all event sources +- fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268580[Bug #268580] +- fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236117[Bug #236117] +- fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254511[Bug #254511] +- fix link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212829[Bug #212829] +- `procctl PROC_REAP_ACQUIRE` + +We are looking for feedback, bug reports (old and new) and feature requests. diff --git a/website/content/en/status/report-2023-01-2023-03/doceng.adoc b/website/content/en/status/report-2023-01-2023-03/doceng.adoc new file mode 100644 index 0000000000..3d565d37d7 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/doceng.adoc @@ -0,0 +1,104 @@ +//// +Quarter: 1st quarter of 2023 +Prepared by: fernape +Reviewed by: carlavilla@ +Last edit: +Version: +//// + +=== Documentation Engineering Team + +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 <doceng@FreeBSD.org> + +The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. + +During the last quarter: + +* The doc commit bit for Pau Amma was taken in. +* Lorenzo Salvadore has been proposed as doc committer. carlavilla@ and dbaio@ will mentor him. +* Ryusuke SUZUKI steps down from doceng. doceng would like to thank ryusuke@ for his service. + +Items pending and in the discussion: + +* link:https://cgit.freebsd.org/doc/commit/?id=4c50528a8678246a6d01765acac8c395434b8c7e[A new document about licensing] has been added to the documentation set. + +==== Porter's Handbook: + +Three new `Uses` knobs have been added to the Handbook: + +* link:https://cgit.freebsd.org/doc/commit/?id=407dbb9254e7b6b379b8257f34f7732ed1afc71f[New Uses = ruby]. +* link:https://cgit.freebsd.org/doc/commit/?id=afa1a31005978bac63874fff8a1833f69a81dae3[New Uses = ldap]. +* link:https://cgit.freebsd.org/doc/commit/?id=689f1b026a02bf6d7039bdfec59353196d83ccef[New Uses = budgie]. + +Also: + + * link:https://cgit.freebsd.org/doc/commit/?id=9af61238fc24d4772b3c9e5fbd63fcaee2526699[The NVIDIA install and configure options have been fixed] + * link:https://cgit.freebsd.org/doc/commit/?id=3c6d3dea4a3ee60e7f0033afc9c5bf74e9ae1d31[The Advanced Networking chapter has been improved] + +==== FreeBSD Translations on Weblate + +Link: link:https://wiki.freebsd.org/Doc/Translation/Weblate[Translate FreeBSD on Weblate] + +Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] + +===== Q4 2022 Status + +* 12 languages +* 150 registered users + +===== Languages + +* Chinese (Simplified) (zh-cn) (progress: 14%) +* Chinese (Traditional) (zh-tw) (progress: 11%) +* Dutch (nl) (progress: 1%) +* French (fr) (progress: 1%) +* German (de) (progress: 1%) +* Indonesian (id) (progress: 1%) +* Italian (it) (progress: 10%) +* Korean (ko) (progress: 11%) +* Norwegian (nb-no) (progress: 1%) +* Persian (fa-ir) (progress: 6%) +* Portuguese (pt-br) (progress: 29%) +* Sinhala (si) (progress: 1%) +* Spanish (es) (progress: 37%) +* Turkish (tr) (progress: 5%) + +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 <carlavilla@FreeBSD.org> + +Chapters 1 to 6 have been updated. +Chapter 7 is work in progress. + +==== FreeBSD Website Revamp - WebApps working group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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 will be 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-01-2023-03/drm-drivers.adoc b/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc new file mode 100644 index 0000000000..4f46a41f13 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/drm-drivers.adoc @@ -0,0 +1,51 @@ +=== DRM drivers (i.e. GPU drivers) + +Links: + +link:https://github.com/freebsd/drm-kmod[Git repository on GitHub] URL: link:https://github.com/freebsd/drm-kmod[] + + +Contact: Emmanuel Vadot <manu@FreeBSD.org> + +Contact: Jean-Sébastien Pédron <dumbbell@FreeBSD.org> + +Contact: The Graphics team <freebsd-x11@FreeBSD.org> + +GPUs are driven by DRM drivers. +They are developed specifically for Linux using a permissive license. +Our mission is to port those drivers to FreeBSD to make sure modern GPUs are fully supported. + +We didn't publish a report to share our progress for a long time. +Therefore this status report entry will cover more than just the last quarter. + +==== Update to Linux 5.15 LTS and Linux 5.16 + +As of this status report, the package:graphics/drm-kmod[] meta port still installs the DRM drivers from Linux 5.10 (released on December 13, 2020) on FreeBSD 13.1 and greater. +This version of the driver lacks support for recent GPUs, in particular Intel 12th gen Alder Lake ones. +In the past months, we worked to update the DRM drivers to bring support for more modern AMD and Intel GPUs. + +The `drm-kmod` Git repository `master` branch was first updated to Linux 5.15 (released on October 31, 2021). +This is an LTS branch in Linux and we wanted to take advantage of that. +Thus at that point, we followed two paths: + +* A `5.15-lts` branch was created to backport all bug fixes from Linux 5.15.x patch releases. This work is now available in the `drm-515-kmod` port. +* The porting effort from subsequent Linux versions continued. The `master` branch is now at Linux 5.16 (release on January 9, 2022). + +The Intel driver from Linux 5.15 LTS supports 12th gen GPUs (Alder Lake). +It looks to work on FreeBSD but we only tested it lightly so far. +We still need more of that, that's why package:graphics/drm-kmod[] still installs package:graphics/drm-510-kmod[] instead of package:graphics/drm-515-kmod[]. +At last, FreeBSD should run as a desktop on this GPU generation and several new AMD GPUs, though problems will surely appear through real test and use. + +In the process, we updated firmwares to link:https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git[linux-firmware] 20230210. + +==== Linux 5.17 and future work + +DRM drivers from Linux 5.17 (released on March 20, 2022) were already ported but link:https://github.com/freebsd/drm-kmod/pull/236[this work still sits in its own branch]. + +A couple of issues block further testing and the merge into the `master` branch: + +* Our current integration with man:vt[4], the console/terminal driver, is quite far from the DRM drivers expectations which are based on Linux' fbdev KPI. Something changed in both the Intel and AMD drivers, meaning that man:vt[4] breaks with the 5.17 update. +* The initial Linux 5.17 release does not contain the fixes backported to Linux 5.15 LTS. It seems quite unstable with the Intel 12th gen GPU mentioned earlier. + +To address the issue with our man:vt[4] integration layer, we started to link:https://github.com/freebsd/drm-kmod/pull/243[write a new vt backend specifically to use the fbdev callbacks exposed by the DRM drivers]. +This backend will be provided with the DRM drivers, not the FreeBSD kernel, to make it easier to maintain as the drivers evolve. +This is still a work in progress and locking in particular is tricky to get right. + +Regarding the bad support of Intel 12th gen in the 5.17 update, bug fixes backported to Linux 5.17.x patch releases will probably not be ported as part of this work. +Instead we will focus on Linux 5.18 (released on May 22, 2022) and following. diff --git a/website/content/en/status/report-2023-01-2023-03/frdp.adoc b/website/content/en/status/report-2023-01-2023-03/frdp.adoc new file mode 100644 index 0000000000..69e64ceb15 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/frdp.adoc @@ -0,0 +1,21 @@ +=== The FreeBSD Russian Documentation Project + +Links: + +link:https://docs.freebsd.org/ru/books/faq/[FAQ] URL: link:https://docs.freebsd.org/ru/books/faq/[] + +link:https://www.freebsd.org/ru/[Web] URL: link:https://www.freebsd.org/ru/[] + +Contact: Andrey Zakhvatov <andrey.zakhvatov@gmail.com> + +The FreeBSD Russian Documentation Project current goal is to provide up-to-date Russian translations of the most significant parts of FreeBSD documentation (FAQ, Handbook, Web). +It is important to support Russian-speaking persons with high-quality official technical materials and increase acceptance of the operating system around the globe. +We hope that this activity will receive some support within the Russian-speaking FreeBSD community and lead to an increased number of translated materials. + +FAQ translation was updated and synched with the latest original version. +There is also a very slight progress with web pages updates. + +Check the link:https://docs.freebsd.org/en/books/fdp-primer/translations/[official translation guide] in case you are willing to help. +We will appreciate your help with translation of the following materials: + +* Web pages (easy) +* Handbook sections (only the X11 section is in progress right now) +* Articles diff --git a/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc b/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc new file mode 100644 index 0000000000..60f88ce1d2 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/freebsd-foundation.adoc @@ -0,0 +1,125 @@ +=== FreeBSD Foundation + +Links: + +link:https://www.freebsdfoundation.org[FreeBSD Foundation] URL: link:https://www.freebsdfoundation.org[] + +link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] + +link:https://www.freebsdfoundation.org/donate/[Donate] URL: link:https://www.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://www.freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.freebsdfoundation.org/journal/[] + +link:https://www.freebsdfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.freebsdfoundation.org/news-and-events/[] + +Contact: Deb Goodkin <deb@FreeBSDFoundation.org> + +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. +Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. +We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. +We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. + +==== Fundraising Efforts + +We finally have our 2022 fundraising numbers in and we raised a total of $1,231,096! +We were short of our goal, which forced us to pull around $74,000 from our longer term investments. + +Besides receiving a lot of donations from you our users and contributors, we received larger donations from Juniper, Meta, Arm, Netflix, Beckhoff, Tarsnap, Modirum, Koum Family Foundation, and Stormshield. +I’d like to extend a heartfelt thank you on behalf of the Foundation to everyone, including individuals and corporations, for your financial contributions in 2022! + +This year our budget is around $2,230,000, which includes increased spending towards FreeBSD advocacy and software development. +More than half our budget is allocated towards work directly related to improving FreeBSD and keeping it secure. +To fund the 2023 budget, we increased our fundraising goal and plan on using some of our investment money. +When we received our first million dollar donation, the plan was to use up to 10% of it each year to increase our work to improve FreeBSD, so this has been part of our funding plan for a few years now. + +The 2023 budget is in the process of being approved by the board of directors and will be published once it is approved. + +This quarter we received donations from Juniper, Tarsnap, Microsoft, and Stormshield. +So, we are already off to a great start! +But, we definitely need more to support our planned efforts for 2023. + +If you want to help us continue our efforts, please consider making a donation towards our 2023 fundraising campaign! +link:https://www.freebsdfoundation.org/donate/[] + +We also have a Partnership Program for larger commercial donors. +You can read about it at link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[]. + +==== OS Improvements + +During the first quarter of 2023, 226 src, 39 ports, and 12 doc tree commits identified the Foundation as a sponsor. +Some of this sponsored work is described in separate report entries: + +* Continuous Integration +* Enabling Snapshots on Filesystems Using Journaled Soft Updates +* FreeBSD as a Tier 1 cloud-init Platform +* FreeBSD Release Engineering Team +* Improve the kinst DTrace provider +* OpenStack on FreeBSD + +Other Foundation-sponsored work included: + +* OpenSSH fixes and updates to versions 9.2p1 and 9.3p1 +* a vendor import and update of libpcap to version 1.10.3 +* improvements to tmpfs, msdosfs, and makefs +* the addition of a new kqueue1 syscall +* man page updates +* dtrace and bhyve fixes +* LinuxKPI work + +==== Continuous Integration and Quality Assurance + +The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. +You can read more about CI work in a dedicated report entry. +A current project that is being funded by the FreeBSD Foundation is one to develop a set of scripts to help src developers conduct CI tests themselves. +One of the main goals is to offer more visibility at the pre-commit stage. +link:https://reviews.freebsd.org/D38815[A review for the first milestone] has been submitted. + +==== FreeBSD Advocacy and Education + +Much of our effort is dedicated to the FreeBSD Project advocacy. +This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. +The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. +Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. + +The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. +These events can be BSD-related, open source, or technology events geared towards underrepresented groups. +We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. +This all helps provide a healthy ecosystem. +We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. +We are back to attending events mostly in person and began planning the in person May 2023 Developer Summit, co-located with BSDCan. +In addition to attending and planning events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD. + +Check out some of our advocacy and education work: + +* Hosted a stand at FOSDEM 2023, February 4-5, 2023 in Brussels, Belgium. +Check out the link:https://freebsdfoundation.org/blog/fosdem-2023-conference-report/[trip report]. +* Hosted a table at State of Open Con 2023, February, 7-8, 2023, in London, England. +link:https://freebsdfoundation.org/blog/advocating-for-freebsd-around-the-world/[Read more] about it. +* Sponsored, held a workshop and hosted a booth at SCALE 20x, in March 9-12, 2023, Pasadena, California. +Check out the link:https://freebsdfoundation.org/blog/freebsd-at-scale-20x/[trip report]. +* Sponsored Open Source 101, March 23 2023, in Charlotte, NC. +* Sponsored and began planning the in-person link:https://wiki.freebsd.org/DevSummit/202305[May 2023 Developer Summit] taking place May 17-18, 2023 in Ottawa, Ontario +* Secured our Media Partner sponsorship status and submitted a workshop for link:https://2023.allthingsopen.org/[All Things Open], October 15-17, 2023 in Raleigh, NC. +* Submitted a Workshop proposal for link:https://sfconservancy.org/fossy/[FOSSY], July 13-16, 2023, in Portland, OR. +* The FreeBSD Project was accepted as a link:https://summerofcode.withgoogle.com/programs/2023/organizations/the-freebsd-project[Participating Organization] for Google Summer of Code. +* We held link:https://youtu.be/NpOkTR_d8os[GSoC Office Hours] to help prospective participants with questions. +* Published link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-march-2023/[March Newsletter] + +* Additional Blog Posts + +** link:https://freebsdfoundation.org/blog/under-the-hood-with-freebsd-and-ampere-altra/[Under the Hood with FreeBSD and Ampere Altra] +** link:https://freebsdfoundation.org/blog/under-the-hood-with-freebsd-and-ampere-altra/[New Open Position: FreeBSD Userland Software Developer] - Note: Posting is closed. +** link:https://freebsdfoundation.org/blog/bsdcan-2023-travel-grant-application-now-open/[BSDCan 2023 Travel Grant Application Now Open] - Note: Applications are closed + +* FreeBSD in the News: + +** link:https://freebsdfoundation.org/news-and-events/latest-news/vmblog-state-of-open-con-qa-with-deb-goodkin/[VMBlog State of Open Con Q&A with Deb Goodkin] + +We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. +As we mentioned previously, the FreeBSD Journal is now a free publication. +Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[]. + +You can find out more about events we attended and upcoming events at link:https://www.FreeBSDfoundation.org/news-and-events/[]. + +==== 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://www.freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2023-01-2023-03/freshports.adoc b/website/content/en/status/report-2023-01-2023-03/freshports.adoc new file mode 100644 index 0000000000..4cf385c706 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/freshports.adoc @@ -0,0 +1,49 @@ +=== Freshports: SQL Injection Attack and Help Request + +Links: + +link:https://freshports..org[FreshPorts] URL: link:freshports.org[] + +link:https://news.freshports.org/[FreshPorts blog] URL: link:https://news.freshports.org/[] + +Contact: Dan Langille <dvl@FreeBSD.org> + +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/[] 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. + +==== SQL Injection Attack + +In March, an SQL injection attack was noticed and the website was patched. +Notices were sent out via our Twitter account, our status page, and a notice on the top of each page of the website. +The immediate attack vector was shutdown and soon patched. +Additional preventative patches were added across the website. +Everything we know about has been fixed. +Users were notified and advised to change their passwords. + +Details at: + +* link:https://news.freshports.org/2023/03/24/sql-inejection-issues-fixed/[] +* link:https://news.freshports.org/2023/03/24/freshsource-code-fixes/[] + +==== Help Needed + +It has been over 22 years since FreshPorts started. +Others must take over eventually. +I’d like to start that process now. +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. diff --git a/website/content/en/status/report-2023-01-2023-03/fsx.adoc b/website/content/en/status/report-2023-01-2023-03/fsx.adoc new file mode 100644 index 0000000000..def3b68468 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/fsx.adoc @@ -0,0 +1,18 @@ +=== FSX + +Links: + +link:https://github.com/asomers/fsx-rs[GitHub] URL: https://github.com/asomers/fsx-rs[] +link:https://www.freshports.org/devel/fsx/[FreshPorts] URL: https://www.freshports.org/devel/fsx/[] + +Contact: Alan Somers <asomers@freebsd.org> + +The venerable FSX (File System eXerciser) tool, first written at Apple Computer in the nineties, has been a part of FreeBSD since 5.0. +It stress tests file systems with a stream of randomly generated operations, verifying file data after every read. +However, it has never been installed as part of the OS; it only exists in the source tree. +That makes it difficult to use in CI pipelines. +It has some other limitations, too. + +So this quarter I rewrote the entire tool in Rust. +The rewrite is byte-for-byte compatible with the original, given identical seed values. +Future versions will break backwards-compatibility, however, in order to add new features like `fspacectl` and `copy_file_range`. +The new version can be found in the ports tree, and in time I'll remove the original. diff --git a/website/content/en/status/report-2023-01-2023-03/gcc.adoc b/website/content/en/status/report-2023-01-2023-03/gcc.adoc new file mode 100644 index 0000000000..f5936fef0f --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/gcc.adoc @@ -0,0 +1,24 @@ +=== 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/[] + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + +Contact: Gerald Pfeifer <gerald@pfeifer.com> + +The main news this quarter is the cleaning of old GCC versions from the ports tree: this will allow for a more efficient approach to bugs. + +==== Deprecation of old GCC ports + +The ports tree still contains several ports related to old and unsupported GCC versions. +They are usually needed as dependencies for a few old ports, that it would be better to either update to use a supported GCC release, or deprecate. +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269644[Bug reports] have been created to track the issue and work has already started towards its resolution. +Thanks to all ports contributors who are helping. + +==== Deprecation of USE_GCC=X+ + +Gerald, who maintained the GCC ports for many years until recently, still contributes to the GCC maintenance on FreeBSD by helping simplify the GCC infrastructure in the ports tree, for example by removing special cases that deal with old unsupported GCC versions. + +This quarter the most significant of his changes is probably link:https://cgit.freebsd.org/ports/commit/?id=9b5f5ab8482f105311d01a32260ef32bba4a2628[the removal of support for the `USE_GCC=X+` construct]: any port depending on GCC should set `USE_GCC=yes` if `GCC_DEFAULT` works; if not, it should require a specific version (e.g. `USE_GCC=11`); it cannot ask for a minimal version anymore (e.g. `USE_GCC=11+`). diff --git a/website/content/en/status/report-2023-01-2023-03/intro.adoc b/website/content/en/status/report-2023-01-2023-03/intro.adoc new file mode 100644 index 0000000000..1e233aca94 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/intro.adoc @@ -0,0 +1,8 @@ +Here is the first status report of 2023, including 25 reports: we have our usual team reports, some news about cloud projects, progress in the src, ports and doc trees and more. + +We also provide some information about link:../../releases/13.2R/announce/[13.2-RELEASE], which was postponed to the beginning of 2023Q2; but since this report is being published after the new version release, it is already available for installation. +Users of RELEASE versions can now take advantage of many improvements such as better support for the man:iwlwifi[4] driver or the new man:rtw88[4] driver, topics that have been covered in past status reports. + +Have a nice read. + +Lorenzo Salvadore, on behalf of the status team. diff --git a/website/content/en/status/report-2023-01-2023-03/kde.adoc b/website/content/en/status/report-2023-01-2023-03/kde.adoc new file mode 100644 index 0000000000..18ef0b3a7b --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/kde.adoc @@ -0,0 +1,52 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE FreeBSD] URL: link:https://freebsd.kde.org/[] + +link:https://community.kde.org/FreeBSD[KDE Community FreeBSD] URL:link:https://community.kde.org/FreeBSD[] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. +The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine. +The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack. + +==== Infrastructure + +* The Qt5 ports were updated to the KDE patch collection release 5.15.8. +* The Qt6 ports -- these are not used by KDE yet, but there are many ports that can use Qt6 and have Qt6 flavors -- were updated to release 6.4.2. +Python bindings for the Qt6 release of WebEngine were added. +* The cmake ports were updated to release 3.25.1 and the CPack generator for FreeBSD packages was repaired. +* The package:graphics/poppler[] port -- used by many PDF-viewers -- was updated to release 23.01. +* The package:sysutils/bsdisks[] port -- used as a shim for applications that expect Linux udisks, which means most desktop environments -- was updated to release 0.29. + +==== KDE Stack + +KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. +These (large) updates land shortly after their upstream release and are not listed separately. + +* KDE Frameworks updated to 5.104. +* KDE Gear updated to 22.12.3. +* KDE Plasma Desktop was updated to version 5.27. +This was a long delayed update, due to unresolved issues in the support stack and a misplaced patch from an earlier release of KDE Plasma. +Thanks to arrowd@ and Serenity Cybersecurity, LLC for sorting that out. +* New port package:devel/ktextaddons[] was added to the tree. +This is part of the KDE PIM suite, and slated to become a new KDE Framework in some future release. + +==== Related Ports + +* package:audio/amarok[], one of the most popular KDE audio players of the early 2000's, has been marked deprecated in the ports tree. +It is no longer maintained upstream. +* package:astro/kstars[], an interactive planetarium, was updated to release 3.6.3. +* package:devel/gitqlient[], a graphical user interface for git, was updated to release 1.6.1 with support for new git commands. +* package:devel/okteta[], a hex viewer and editor for binary files, was updated to release 0.26.10. +* package:devel/qcoro[], C++ coroutines with Qt support, was updated to release 0.8.0. +* package:graphics/krita[], an application for painting and graphical work, was updated to release 5.1.5. +* package:graphics/quickqanava[], a graph visualization library, got a real release and an update in the ports tree. +* package:irc/kvirc[], an IRC client, was updated to the latest commit; there is no real release but there are bugfixes. +* package:multimedia/haruna[], a video and audio player, was updated to release 0.10.3. +* package:net-im/neochat[], one of a handful of Matrix clients, was updated to chase a new release of package:net-im/libquotient[]. +There are continuing troubles with compatibility with older FreeBSD releases, leading to the KDE-FreeBSD team to declare FreeBSD 12 releases "effectively unsupported". +* package:net-im/ruqola[], a Rocket Chat client, was updated to release 1.9.1. +* package:security/keysmith[], a two-factor-authentication support application, was updated to release 23.01.0. diff --git a/website/content/en/status/report-2023-01-2023-03/kinst.adoc b/website/content/en/status/report-2023-01-2023-03/kinst.adoc new file mode 100644 index 0000000000..9320736896 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/kinst.adoc @@ -0,0 +1,66 @@ +=== Improve the kinst DTrace provider + +Links: + +link:https://reviews.freebsd.org/D38825[libdtrace: implement inline function tracing] URL: link:https://reviews.freebsd.org/D38825[] + +link:https://reviews.freebsd.org/D38732[dtrace(1): add -d flag to dump D script post-dt_sugar] URL: link:https://reviews.freebsd.org/D38732[] + +Contact: Christos Margiolis <christos@FreeBSD.org> + +Contact: Mark Johnston <markj@FreeBSD.org> + +kinst is a new DTrace provider created by christos@ and markj@ that allows for arbitrary instruction tracing in a kernel function. +kinst has been added to the base system in FreeBSD 14.0. + +link:../report-2022-07-2022-09/#_dtrace_instruction_level_dynamic_tracing[The 2022Q3 status report gives a brief introduction to kinst.] +We're now working on inline function tracing (see review D38825 above) -- a much-requested DTrace feature -- by using kernel DWARF and ELF info to find the call sites of each inline copy and use that information to transform D syntax by turning kinst probes of the form: + +.... + kinst::<inline_func>:<entry/return> + /<pred>/ + { + <acts> + } +.... + +To: + +.... + kinst::<caller_func1>:<offset>, + kinst::<caller_func2>:<offset>, + kinst::<caller_func3>:<offset> + /<pred>/ + { + <acts> + } +.... + +For example: + +.... + # dtrace -dn 'kinst::cam_iosched_has_more_trim:entry { printf("\t%d\t%s", pid, execname); }' + kinst::cam_iosched_get_trim:13, + kinst::cam_iosched_next_bio:13, + kinst::cam_iosched_schedule:40 + { + printf("\t%d\t%s", pid, execname); + } + + dtrace: description 'kinst::cam_iosched_has_more_trim:entry ' matched 3 probes + CPU ID FUNCTION:NAME + 2 79315 cam_iosched_next_bio:13 0 kernel + 2 79316 cam_iosched_schedule:40 0 kernel + 0 79316 cam_iosched_schedule:40 12 intr + 2 79315 cam_iosched_next_bio:13 0 kernel + 2 79316 cam_iosched_schedule:40 0 kernel + 0 79316 cam_iosched_schedule:40 12 intr + ^C +.... + +A new `-d` flag has also been added to man:dtrace[1] which dumps the D script after libdtrace has applied syntactic transformations. + +Further goals include: + +* Implement a `locals` structure in D which stores the local variables of the traced function. + For example with `kinst::foo:<x>`, we could print the local variable `bar` by doing `print(locals->bar)` inside a D script. +* Port kinst to riscv and/or arm64. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/openstack-on-freebsd.adoc b/website/content/en/status/report-2023-01-2023-03/openstack-on-freebsd.adoc new file mode 100644 index 0000000000..b59cf6731d --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/openstack-on-freebsd.adoc @@ -0,0 +1,37 @@ +=== OpenStack on FreeBSD + +Links: + +link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] + +link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[] + + +Contact: Chih-Hsin Chang <starbops@hey.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +This project aims to port key OpenStack components so that FreeBSD can function as an OpenStack host. + +In 2023 Q1, the big news is that we're able to spawn FreeBSD instances with man:bhyve[8] on the OpenStack platform. +But there are still some major limitations regarding the capabilities of the spawned instances that need to be resolved: + +* No self-service networks (only support the flat network) +* No network connectivity inside the instance +* Only support FreeBSD raw images (`FreeBSD-13.1-RELEASE-amd64.raw` tested) +* No disk resize +* No console integration (need to use man:cu[1] command manually) + +The step-by-step documents for constructing a POC site can be found link:https://github.com/openstack-on-freebsd/docs[in the `docs` repository]. +The patched version of each OpenStack component is under the same GitHub organization. + +Also, we attended AsiaBSDCon 2023 at the end of March and gave a short talk about the current project status at the developer summit. +We got precious feedback at the event and will focus on the following for the next quarter: + +* Resolve the Open vSwitch networking issue +* Convert each OpenStack component into FreeBSD ports + +People interested in helping with the project can first help check the documentation by following the installation guide. +And here is an open task for the project: + +* FreeBSD-specific implementation for the oslo.privsep library + +Feedback and help are always welcome. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc b/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc new file mode 100644 index 0000000000..d06ac09bf3 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/pkgbase.live.adoc @@ -0,0 +1,24 @@ +=== PkgBase.live + +Links: + +link:https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/[Website (archive.org)] URL: link:https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/[] + +link:https://codeberg.org/pkgbase/website[Website source] URL: link:https://codeberg.org/pkgbase/website[] + +Contact: Mina Galić <freebsd@igalic.co> + +PkgBase.live _was_ an unofficial repository for the FreeBSD link:https://wiki.freebsd.org/PkgBase[PkgBase project]. +As a service, PkgBase.live was inspired by link:https://up.bsd.lv/[], which provides man:freebsd-update[8] for STABLE and CURRENT branches. + +Hardware for PkgBase was kindly sponsored by a member of the FreeBSD community. +However, as life and projects moved on, they had to decommission the hardware, giving me three months' notice. +In that time, my own life was rather turbulent after a recent move to a different country so I haven't been able to find a replacement. + +For the time being, PkgBase.live is dead. + +The website, and with it the link:https://codeberg.org/pkgbase/website/src/branch/main/howto/howdo.md[How Did She Do it?!] are still available in link:https://codeberg.org/pkgbase/website[Git]. +I highly encourage copy-cats. + +I will also happily accept a new hardware sponsor! + +Please note that I _have_ contacted the FreeBSD Project, and they _are_ working on integrating PkgBase into release engineering. +However, they are not yet ready, they also cannot "simply" take over PkgBase.live because it uses a completely different process. diff --git a/website/content/en/status/report-2023-01-2023-03/portmgr.adoc b/website/content/en/status/report-2023-01-2023-03/portmgr.adoc new file mode 100644 index 0000000000..3859809186 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/portmgr.adoc @@ -0,0 +1,37 @@ +=== 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 <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages (through its subsidiary pkgmgr), and personnel matters. +Below is what happened in this quarter. + +Currently we have around 33,500 ports in the tree. +For these ports, there are 3,021 open problem reports, of which 764 are unassigned. +The first three months of this year saw 9,021 commits by 163 committers for the `main` branch and 701 commits by 55 committers for the `2023Q1` branch. +Compared to `2022Q4`, this means a slight increase in the number of ports, port PRs, ports commits, and active port committers. + +During this quarter, we welcomed Robert Clausecker (fuz@), Vladimir Druzenko (vvd@), Robert Nagy (rnagy@), welcomed back Norikatsu Shigemura (nork@), and said goodbye to Marius Strobl (marius@). +Portgmr added Muhammad Moinur Rahman (bofh@) as a new member after a successful lurkership. + +During the bi-weekly portmgr meetings, the following topics were discussed: + +* improving the situation of binary packages for kernel modules +* ways to measure the impact of ports on their dependencies and how to maintain high-impact ports. + +During this quarter, 32 exp-runs were run to test port updates, updating default versions (LLVM to 15, MySQL to 8.0, Ruby to 3.1), and updating byacc in base. +Furthermore, the default version of Go switched to 1.20 and that of Lazarus to 2.2.6. + +Four new USES were introduced: + +* `budgie` to support ports related to the Budgie Desktop +* `ldap` to provide support for OpenLDAP, with a new default version of 26 (i.e. 2.6) +* `nextcloud` to support Nextcloud applications +* `ruby` to provide support for Ruby ports (formerly `bsd.ruby.mk`). diff --git a/website/content/en/status/report-2023-01-2023-03/pot.adoc b/website/content/en/status/report-2023-01-2023-03/pot.adoc new file mode 100644 index 0000000000..951eb14541 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/pot.adoc @@ -0,0 +1,20 @@ +=== 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) <pizzamig@freebsd.org> + +Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@freebsd.org> + +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]. + +During the last quarter, link:https://github.com/bsdpot/pot/commits/master[pot] received a number of minor fixes but no new version has been released yet. + +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. + +All Potluck images have been rebuilt to include the latest FreeBSD security advisories, a new link:https://github.com/bsdpot/potluck/tree/master/smokeping[Smokeping network latency monitoring image has been added], again a lot of work went into the link:https://github.com/bsdpot/potluck/tree/master/jitsi-meet[Jitsi] image, which unfortunately still seems to have some reliability issues. + +Also, two new blog posts are available showing how easy it is to use Potluck images, link:https://honeyguide.eu/posts/minio-beast-nextcloud/[one explaining how to set up Nextcloud with Minio as object storage and Prometheus for monitoring], link:https://honeyguide.eu/posts/openldap-matrix-blog-post/[one showing how to run your own Matrix Synapse server using OpenLDAP for access management]. + +As always, feedback and patches are welcome. diff --git a/website/content/en/status/report-2023-01-2023-03/releng.adoc b/website/content/en/status/report-2023-01-2023-03/releng.adoc new file mode 100644 index 0000000000..c0ba1045cf --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/releng.adoc @@ -0,0 +1,20 @@ +=== FreeBSD Release Engineering Team + +Links: + +link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[] + +link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[] + +link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] + +link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[] + +Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org> + +The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. + +During the first quarter of 2023, the Release Engineering Team started work on the upcoming 13.2-RELEASE. +As of this writing, the 13.2 cycle has followed the originally set schedule, with the addition of fourth, fifth and sixth RC builds, postponing the final release from the end of March to early April. + +The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/13*, and *stable/12* branches. + +Sponsor: Rubicon Communications, LLC ("Netgate") + +Sponsor: Tarsnap + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/status.adoc b/website/content/en/status/report-2023-01-2023-03/status.adoc new file mode 100644 index 0000000000..361e73e617 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/status.adoc @@ -0,0 +1,43 @@ +=== Status Team + +Links: + +link:https://www.freebsd.org/status/[FreeBSD status reports] URL: link:https://www.freebsd.org/status/[] + +link:https://docs.freebsd.org/en/articles/freebsd-status-report-process/[FreeBSD Status Report Process] URL: https://docs.freebsd.org/en/articles/freebsd-status-report-process/[] + +link:https://github.com/freebsd/freebsd-quarterly[Archived status reports GitHub repository] URL: link:https://github.com/freebsd/freebsd-quarterly[] + +Contact: <status@FreeBSD.org> + +==== The new workflow has started + +In the first quarter of this year, the link:https://reviews.freebsd.org/project/profile/88/[status team] has started implementing the new workflow that was announced at the end of 2022. +Here are some details. + +==== New email addresses + +Last quarter we have announced the creation of new email addresses: + +- <status@FreeBSD.org>, for interacting with the _status_ team directly; +- <status-submissions@FreeBSD.org, for sending reports submissions; +- <freebsd-status-calls@FreeBSD.org>, a mailing list to which you can link:https://lists.freebsd.org/subscription/freebsd-status-calls[subscribe] to get reminders about status report submission deadlines. + +Unfortunately, the mailing list does not work as expected at the moment. +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269893[The issue has been reported] but no solution could be found yet. +However, a work around allowed to send the second and the last reminder to the link:https://lists.freebsd.org/archives/freebsd-status-calls/2023-March/[list]. + +==== Automation + +Some automation has been introduced to ensure that no report submission is lost: + +- on Phabricator a link:https://reviews.freebsd.org/H166[herald rule] automatically blocks any review touching the status reports directory: even if a report submitter forgets to add the _status_ team as reviewer, salvadore@ (member of the _status_ team) will block the patch anyway. +The same rule will also block any review that includes the _status_ team as reviewer, to ensure that at least one member of _status_ has reviewed the patch before commit. +- a link:https://github.com/freebsd/freebsd-doc/blob/main/.github/workflows/label-pull-requests.yml[GitHub action] automatically adds the newly introduced link:https://github.com/freebsd/freebsd-doc/pulls?q=label%3A%22status+report%22[status report] label to any pull request touching the status reports directory. +The GitHub action should be easily modifiable by anyone wanting to apply more labels automatically depending on the path of the modified files. + +More automation is planned. + +==== Documentation reorganization + +The status report link:https://cgit.freebsd.org/doc/diff/website/content/en/status/README?id=7cd49b34af842b2cf247c944b7d8bc3c1bef8fc8[README] and link:https://cgit.freebsd.org/doc/diff/website/content/en/status/howto/_index.adoc?id=7cd49b34af842b2cf247c944b7d8bc3c1bef8fc8[How To] have been updated and merged in one unique document: the link:https://docs.freebsd.org/en/articles/freebsd-status-report-process/[FreeBSD status report process]. +You can check it out to read details about reports submission and publication. +It will be updated regularly as the status team proceeds with the implementation of its new workflow. +In particular, new material about automation is coming soon. diff --git a/website/content/en/status/report-2023-01-2023-03/timerfd.adoc b/website/content/en/status/report-2023-01-2023-03/timerfd.adoc new file mode 100644 index 0000000000..b6d9ec7ee6 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/timerfd.adoc @@ -0,0 +1,20 @@ +=== Native Linux timerfd + +Links: + +link:https://reviews.freebsd.org/D38459[Differential revision] URL: link:https://reviews.freebsd.org/D38459[] + +Contact: Jake Freeland <jfree@FreeBSD.org> + +The timerfd facility is a set of Linux-standard system calls that operate on interval timers. +These timers are analogous to per-process timers but are represented by a file descriptor, rather than a process. +These file descriptors may be passed to other processes, are preserved across man:fork[2], and may be monitored via man:kevent[2], man:poll[2], or man:select[2]. + +A timerfd implementation in FreeBSD already exists for Linux compatibility, but link:https://reviews.freebsd.org/D38459[this differential revision] makes the interface native. +The goal behind this change is to ease the FreeBSD porting process for programs that include timerfd. + +This specific implementation avoids adding new names to the system call table. +Instead, `timerfd_create()` is wrapped by the `specialfd()` system call. +The `timerfd_gettime() and `timerfd_settime()` calls are wrapped `ioctl()` s. + +Developers that wish to support FreeBSD should avoid using timerfd. +The `kqueue()` `EVFILT_TIMER` filter is preferred for establishing arbitrary timers. diff --git a/website/content/en/status/report-2023-01-2023-03/ufs_snapshots.adoc b/website/content/en/status/report-2023-01-2023-03/ufs_snapshots.adoc new file mode 100644 index 0000000000..fab82ef0dd --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/ufs_snapshots.adoc @@ -0,0 +1,13 @@ +=== Enabling Snapshots on Filesystems Using Journaled Soft Updates in 13.2 + +Contact: Marshall Kirk McKusick <mckusick@freebsd.org> + +The ability to make UFS/FFS filesystem snapshots when running with journaled soft updates, and using them for doing background dumps on a live filesystem, was merged to `releng/13.2` during the first quarter of 2023, and lands in FreeBSD 13.2-RELEASE. + +Background dumps are requested by using the `-L` flag to man:dump[8]. + +The details of this project were +link:../report-2022-10-2022-12/#_enabling_snapshots_on_filesystems_using_journaled_soft_updates[described +in the 2022 fourth quarter report]. + +Sponsored by: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-01-2023-03/valgrind.adoc b/website/content/en/status/report-2023-01-2023-03/valgrind.adoc new file mode 100644 index 0000000000..f3aa176ee4 --- /dev/null +++ b/website/content/en/status/report-2023-01-2023-03/valgrind.adoc @@ -0,0 +1,29 @@ +=== Valgrind - Preparing for Valgrind 3.21 + +Links: + +link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[] + +link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[] + +Contact: Paul Floyd <pjfloyd@wanadoo.fr> + +The package:devel/valgrind-devel[] port had an intermediate update which was submitted on 2023-02-20. +This contains most of what will be in the official release of Valgrind 3.21 which is due out shortly after this status report. + +There is a nice improvement to the vgdb interface. +It's now much easier to see which bits of memory are initialized or not. +There are a couple of fixes to the thread checks done by Helgrind. + +For FreeBSD specifically, the address space limit has been raised to be the same as Linux and Solaris on amd64. +It was 32Gbytes and now it is 128Gbytes. +The `kern.proc.pathname.PID` man:sysctl[3] has been fixed so that it returns the path of the guest exe and not that of the Valgrind host. +At the same time I fixed some `_umtx_op` false positives and corrected auxv `AT_EXECPATH` in a way similar to `kern.proc.pathname.PID`. +Syscall wrappers have been added for man:sctp_generic_sendmsg[2] and man:sctp_generic_recvmsg[2]. + +Not yet available in the ports versions of Valgrind, there is a workaround for the use of man:rfork[2]. +Previously, since it is not supported, it would cause Valgrind to abort. +Now it fails gracefully setting either EINVAL or ENOSYS. +The main use of this system call is in man:posix_spawn[3], which will fall back to using man:vfork[2]. + +The man:mknodat[2] syscall wrapper was incorrectly implemented on i386 and has now been fixed. + +There is a reworking of all of the aligned allocation functions so that they behave less like Linux glibc and more like the Valgrind build platform. 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 new file mode 100644 index 0000000000..70a11b6038 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/_index.adoc @@ -0,0 +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 new file mode 100644 index 0000000000..425eab7b02 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/azure.adoc @@ -0,0 +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 <bsdic@microsoft.com> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] + +Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> + +Contact: Wei Hu <whu@FreeBSD.org> + +Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + + +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/batman.adoc b/website/content/en/status/report-2023-04-2023-06/batman.adoc new file mode 100644 index 0000000000..500e7afea6 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/batman.adoc @@ -0,0 +1,21 @@ +=== BATMAN support in the FreeBSD kernel + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/CallingTheBatmanFreeNetworksOnFreeBSD[Wiki page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/CallingTheBatmanFreeNetworksOnFreeBSD[] + +link:https://github.com/obiwac/freebsd-gsoc/pull/1[Source code (Pull Request)] URL: https://github.com/obiwac/freebsd-gsoc/pull/1[] + +Contact: Aymeric Wibo <obiwac@FreeBSD.org> + +BATMAN (Better Approach to Mobile Ad-hoc Networking), as developed and used by the Freifunk project, is a routing protocol for (primarily wireless) multi-hop ad-hoc networks. +Freifunk is a German initiative to build an open Wi-Fi network at city-scale, based on the principles of net-neutrality. +BATMAN's motive is to be a completely decentralized protocol; no one node in the network knows or has to care about the topology of the whole network. + +Support for this protocol is provided by the batman-adv kernel module on Linux, and this project aims to bring that to FreeBSD. +This includes the kernel module itself, but also userland networking libraries and tools necessary to create BATMAN networks. + +Currently, creating interfaces and interacting with them works (with both Linux and FreeBSD userspaces), and packet transmission (kind of) works, although it is incomplete as of yet. +Support for batadv interfaces has been added to man:ifconfig[8] too. + +Mentor: mailto:mmokhi@FreeBSD.org[Mahdi Mokhtari] + +Sponsor: The Google Summer of Code '23 program diff --git a/website/content/en/status/report-2023-04-2023-06/boot-performance.adoc b/website/content/en/status/report-2023-04-2023-06/boot-performance.adoc new file mode 100644 index 0000000000..01ecf983f0 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/boot-performance.adoc @@ -0,0 +1,19 @@ +=== Boot Performance Improvements + +Links: + +link:https://wiki.freebsd.org/BootTime[Wiki page] URL: link:https://wiki.freebsd.org/BootTime[] + +link:https://www.bsdcan.org/events/bsdcan_2023/sessions/session/116/slides/44/BSDCan23-Firecracker.pdf[BSDCan talk slides] URL: link:https://www.bsdcan.org/events/bsdcan_2023/sessions/session/116/slides/44/BSDCan23-Firecracker.pdf[] + +Contact: Colin Percival <cperciva@FreeBSD.org> + +Colin is coordinating efforts to speed up the FreeBSD boot process. + +Recent efforts have moved from EC2 to the Firecracker virtual machine manager, which provides a very minimalist environment; stripping the boot process down to the bare minimum makes it easier to identify the remaining time and determine whether it can be optimized further. + +With some experimental patches to both FreeBSD and Firecracker, it is now possible to boot a FreeBSD kernel in under 20 ms. + +Some of the recent improvements were discussed in Colin's _Porting FreeBSD to Firecracker_ session at BSDCan. + +This work is supported by his FreeBSD/EC2 Patreon. + +Sponsor: https://www.patreon.com/cperciva diff --git a/website/content/en/status/report-2023-04-2023-06/caldera.adoc b/website/content/en/status/report-2023-04-2023-06/caldera.adoc new file mode 100644 index 0000000000..6aa99cb033 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/caldera.adoc @@ -0,0 +1,29 @@ +=== MITRE Caldera on FreeBSD + +Links: + +link:https://caldera.mitre.org/[MITRE Caldera] URL: link:https://caldera.mitre.org/[] + +link:https://www.redcanary.com/[Red Canary] URL: link:https://www.redcanary.com/[] + +Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org> + +MITRE Caldera is a cybersecurity platform designed to easily automate adversary emulation, assist manual red teams, and automate incident response. + +It is built on the MITRE ATT&CK(R) framework and is an active research project at MITRE. + +MITRE Caldera (package:security/caldera[]) was added to the ports tree in April 2023. +This port includes support for the link:https://github.com/redcanaryco/atomic-red-team[Atomic Red Team Project] used by the link:https://github.com/mitre/atomic[MITRE Caldera atomic plugin]. + +The main goal of this work is enhancing visibility of FreeBSD as a useful platform for information security or cybersecurity. + +Additionally, you can test a MITRE Caldera infrastructure easily using link:https://github.com/alonsobsd/caldera-makejail[] or link:https://github.com/AppJail-makejails/caldera[] from link:https://github.com/DtxdF/AppJail[AppJail]. +AppJail is a good tool for managing jail containers from the command line. + +People interested in helping with the project are welcome. + +Current version: 4.2.0 + +==== To Do + +* Add Caldera testing infrastructure makejail. +* Add FreeBSD to platforms officially supported by MITRE Caldera, see link:https://github.com/mitre/caldera/pull/2752[]. +* Add FreeBSD to platforms officially supported by Red Canary, see link:https://github.com/redcanaryco/atomic-red-team/pull/2450[]. diff --git a/website/content/en/status/report-2023-04-2023-06/capsicum-ktracing.adoc b/website/content/en/status/report-2023-04-2023-06/capsicum-ktracing.adoc new file mode 100644 index 0000000000..05e7bc6825 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/capsicum-ktracing.adoc @@ -0,0 +1,230 @@ +=== Security Sandboxing Using man:ktrace[1] + +Links: + +link:https://github.com/jakesfreeland/freebsd-src/tree/ff/ktrace[ktrace branch] URL: link:https://github.com/jakesfreeland/freebsd-src/tree/ff/ktrace[] + + +Contact: Jake Freeland <jfree@FreeBSD.org> + +==== Capsicumization With man:ktrace[1] + +This report introduces an extension to man:ktrace[1] that logs capability violations for programs that have not been Capsicumized. + +The first logical step in Capsicumization is determining where your program is raising capability violations. +You could approach this issue by looking through the source and removing Capsicum-incompatible code, but this can be tedious and requires the developer to be familiar with everything that is not allowed in capability mode. + +An alternative to finding violations manually is to use man:ktrace[1]. +The man:ktrace[1] utility logs kernel activity for a specified process. +Capsicum violations occur inside of the kernel, so man:ktrace[1] can record and return extra information about your program's violations with the `-t p` option. + +Programs traditionally need to be put into capability mode before they will report violations. +When a restricted system call is entered, it will fail and return with `ECAPMODE: Not permitted in capability mode`. +If the developer is doing error checking, then it is likely that their program will terminate with that error. +This behavior made violation tracing inconvenient because man:ktrace[1] would only report the first capability violation, and then the program would terminate. + +Luckily, a new extension to man:ktrace[1] can record violations when a program is **NOT** in capability mode. +This means that any developer can run capability violation tracing on their program with no modification to see where it is raising violations. +Since the program is never actually put into capability mode, it will still acquire resources and execute normally. + +==== Violation Tracing Examples + +The `cap_violate` program, shown below, attempts to raise every type of violation that man:ktrace[1] can capture: + +[source, shell] +---- +# ktrace -t p ./cap_violate +# kdump +1603 ktrace CAP system call not allowed: execve +1603 foo CAP system call not allowed: open +1603 foo CAP system call not allowed: open +1603 foo CAP system call not allowed: open +1603 foo CAP system call not allowed: open +1603 foo CAP system call not allowed: readlink +1603 foo CAP system call not allowed: open +1603 foo CAP cpuset_setaffinity: restricted cpuset operation +1603 foo CAP openat: restricted VFS lookup: AT_FDCWD +1603 foo CAP openat: restricted VFS lookup: / +1603 foo CAP system call not allowed: bind +1603 foo CAP sendto: restricted address lookup: struct sockaddr { AF_INET, 0.0.0.0:5000 } +1603 foo CAP socket: protocol not allowed: IPPROTO_ICMP +1603 foo CAP kill: signal delivery not allowed: SIGCONT +1603 foo CAP system call not allowed: chdir +1603 foo CAP system call not allowed: fcntl, cmd: F_KINFO +1603 foo CAP operation requires CAP_WRITE, descriptor holds CAP_READ +1603 foo CAP attempt to increase capabilities from CAP_READ to CAP_READ,CAP_WRITE +---- + +The first 7 `system call not allowed` entries did not explicitly originate from the `cap_violate` program code. +Instead, they were raised by FreeBSD's C runtime libraries. +This becomes apparent when you trace namei translations alongside capability violations using the `-t np` option: + +[source, shell] +---- +# ktrace -t np ./cap_violate +# kdump +1632 ktrace CAP system call not allowed: execve +1632 ktrace NAMI "./cap_violate" +1632 ktrace NAMI "/libexec/ld-elf.so.1" +1632 foo CAP system call not allowed: open +1632 foo NAMI "/etc/libmap.conf" +1632 foo CAP system call not allowed: open +1632 foo NAMI "/usr/local/etc/libmap.d" +1632 foo CAP system call not allowed: open +1632 foo NAMI "/var/run/ld-elf.so.hints" +1632 foo CAP system call not allowed: open +1632 foo NAMI "/lib/libc.so.7" +1632 foo CAP system call not allowed: readlink +1632 foo NAMI "/etc/malloc.conf" +1632 foo CAP system call not allowed: open +1632 foo NAMI "/dev/pvclock" +1632 foo CAP cpuset_setaffinity: restricted cpuset operation +1632 foo NAMI "ktrace.out" +1632 foo CAP openat: restricted VFS lookup: AT_FDCWD +1632 foo NAMI "/" +1632 foo CAP openat: restricted VFS lookup: / +1632 foo CAP system call not allowed: bind +1632 foo CAP sendto: restricted address lookup: struct sockaddr { AF_INET, 0.0.0.0:5000 } +1632 foo CAP socket: protocol not allowed: IPPROTO_ICMP +1632 foo CAP kill: signal delivery not allowed: SIGCONT +1632 foo CAP system call not allowed: chdir +1632 foo NAMI "." +1632 foo CAP system call not allowed: fcntl, cmd: F_KINFO +1632 foo CAP operation requires CAP_WRITE, descriptor holds CAP_READ +1632 foo CAP attempt to increase capabilities from CAP_READ to CAP_READ,CAP_WRITE +---- + +In practice, capability mode is always entered following the initialization of the C runtime libraries, so a program would never trigger those first 7 violations. +We are only seeing them because man:ktrace[1] starts recording violations before the program starts. + +This demonstration makes it clear that violation tracing is not always perfect. +It is a helpful guide for detecting restricted system calls, but may not always parody your program's actual behavior in capability mode. +In capability mode, violations are equivalent to errors; they are an indication to stop execution. +Violation tracing is ignoring this suggestion and continuing execution anyway, so invalid violations may be reported. + +The next example traces violations from the man:unzip[1] utility (pre-Capsicumization): + +[source, shell] +---- +# ktrace -t np unzip foo.zip +Archive: foo.zip +creating: bar/ +extracting: bar/bar.txt +creating: baz/ +extracting: baz/baz.txt +# kdump +1926 ktrace CAP system call not allowed: execve +1926 ktrace NAMI "/usr/bin/unzip" +1926 ktrace NAMI "/libexec/ld-elf.so.1" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/etc/libmap.conf" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/usr/local/etc/libmap.d" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/var/run/ld-elf.so.hints" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libarchive.so.7" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/usr/lib/libarchive.so.7" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libc.so.7" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libz.so.6" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libbz2.so.4" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/usr/lib/libbz2.so.4" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/liblzma.so.5" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/usr/lib/liblzma.so.5" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libbsdxml.so.4" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libprivatezstd.so.5" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/usr/lib/libprivatezstd.so.5" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libcrypto.so.111" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libmd.so.6" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libthr.so.3" +1926 unzip CAP system call not allowed: readlink +1926 unzip NAMI "/etc/malloc.conf" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/dev/pvclock" +1926 unzip NAMI "foo.zip" +1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/etc/localtime" +1926 unzip NAMI "bar" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip CAP system call not allowed: mkdir +1926 unzip NAMI "bar" +1926 unzip NAMI "bar" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "bar/bar.txt" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "bar/bar.txt" +1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "baz" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip CAP system call not allowed: mkdir +1926 unzip NAMI "baz" +1926 unzip NAMI "baz" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "baz/baz.txt" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "baz/baz.txt" +1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD +---- + +The violation tracing output for man:unzip[1] is more akin to what a developer would see when tracing their own program for the first time. +Most programs link against libraries. +In this case, man:unzip[1] is linking against man:libarchive[3], which is reflected here: + +[source, shell] +---- +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/lib/libarchive.so.7" +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/usr/lib/libarchive.so.7" +---- + +The violations for man:unzip[1] can be found below the C runtime violations: + +[source, shell] +---- +1926 unzip NAMI "foo.zip" +1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD +1926 unzip CAP system call not allowed: open +1926 unzip NAMI "/etc/localtime" +1926 unzip NAMI "bar" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip CAP system call not allowed: mkdir +1926 unzip NAMI "bar" +1926 unzip NAMI "bar" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "bar/bar.txt" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "bar/bar.txt" +1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "baz" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip CAP system call not allowed: mkdir +1926 unzip NAMI "baz" +1926 unzip NAMI "baz" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "baz/baz.txt" +1926 unzip CAP fstatat: restricted VFS lookup: AT_FDCWD +1926 unzip NAMI "baz/baz.txt" +1926 unzip CAP openat: restricted VFS lookup: AT_FDCWD +---- + +In this instance, man:unzip[1] is recreating the file structure contained in the zip archive. +Violations are being raised because the `AT_FDCWD` value cannot be used in capability mode. +The bulk of these violations can be fixed by opening `AT_FDCWD` (the current directory) before entering capability mode and passing that descriptor into man:openat[2], man:fstatat[2], and man:mkdirat[2] as a relative reference. + +Violation tracing may not automatically Capsicumize programs, but it is another tool in the developer's toolbox. +It only takes a few seconds to run a program under man:ktrace[1] and the result is almost always a decent starting point for sandboxing your program using Capsicum. + +Sponsor: FreeBSD Foundation 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 new file mode 100644 index 0000000000..d38c25afb3 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/ci-bootloader.adoc @@ -0,0 +1,21 @@ +=== CI Test Harness For Bootloader + +Links: + +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 <smk@FreeBSD.org> + +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. + +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/ci.adoc b/website/content/en/status/report-2023-04-2023-06/ci.adoc new file mode 100644 index 0000000000..1bec18c9bc --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/ci.adoc @@ -0,0 +1,51 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] + +link:https://wiki.FreeBSD.org/Jenkins[FreeBSD Jenkins wiki] URL: link:https://wiki.FreeBSD.org/Jenkins[] + +link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] + +link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] + +link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] + +link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +In the second quarter of 2023, we worked with the project contributors and developers to address their testing requirements. +Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. + +Important completed tasks: + +* link:https://ci.FreeBSD.org/job/FreeBSD-stable-13-amd64-gcc12_build/[FreeBSD-stable-13-amd64-gcc12_build] job has been added. +* Build environment of main and stable/13 branches has been changed to 13.2-RELEASE, and stable/12 has been changed to 12.4-RELEASE. +* *-build jobs using gcc12 are sending failure reports to link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List]. +* Present Testing/CI Status Update in link:https://wiki.freebsd.org/DevSummit/202305[BSDCan 2023 Developer Summit] + +Work in progress tasks: + +* Designing and implementing pre-commit CI building and testing (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) +* Designing and implementing use of CI cluster to build release artifacts as release engineering does +* Simplifying CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Organizing the scripts in freebsd-ci repository to prepare for merging to src repository +* Improving the hardware test lab and adding more hardware for testing +* Merge link:https://reviews.freebsd.org/D38815[] +* Merge link:https://reviews.freebsd.org/D36257[] + +Open or queued tasks: + +* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] +* Setting up public network access for the VM guest running tests +* Implementing use of bare-metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort! + +Sponsor: The FreeBSD Foundation 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 new file mode 100644 index 0000000000..b0a91ec5ff --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/cirrus.adoc @@ -0,0 +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-doc[FreeBSD doc CI] URL: link:https://cirrus-ci.com/github/freebsd/freebsd-doc[] + +Contact: Brooks Davis <brooks@FreeBSD.org> + +Contact: Ed Maste <emaste@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +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. + +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: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-04-2023-06/cloud-init.adoc b/website/content/en/status/report-2023-04-2023-06/cloud-init.adoc new file mode 100644 index 0000000000..d4a16af4e9 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/cloud-init.adoc @@ -0,0 +1,35 @@ +=== FreeBSD as a Tier 1 cloud-init Platform + +Links: + +link:https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[] + +link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[] + +link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[cloud-init ongoing refactorization] URL: link:https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst[] + +Contact: Mina Galić <freebsd@igalic.co> + +cloud-init is the standard way of provisioning servers in the cloud. +Unfortunately, cloud-init support for operating systems other than Linux has been rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform. +To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support. +The broader plan is to lift support across all BSDs. + +This quarter has been going quite slowly, but I have managed to deliver a new milestone: + +- Ephemeral Networking classes have been rewritten and made platform independent. +These are used by several cloud providers to initialize a temporary network before retrieving the actual configuration. + +- cloud-init has been successfully tested on Vultr. +I hope that with the next release I can convince Vultr to switch their FreeBSD images to cloud-init. + +In addition to that, I have expanded rsyslog support for BSD. +I've also added an rc script for cloud-init's ds-identify, which should make zero-configuration setups orders of magnitude faster: +ds-identify runs first and very quickly guesses the cloud provider the machine is running on. +cloud-init then uses only that guess, instead of iterating and failing through a full list of all possible cloud providers. +People building custom images can easily disable this (by removing ``/usr/local/etc/rc.d/dsidentify``), and providing a specific listing themselves, shave off a few more milliseconds from their boot. + +The next steps will be to keep hacking away at the network refactoring tasks, and to add LXD support for FreeBSD, so it can be included in CI tests. +The latter will include work on link:https://github.com/canonical/lxd/pull/11761[LXD], as well as work on the link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271793[FreeBSD virtio subsystem]. + +As always, I highly welcome early testers to checkout package:net/cloud-init-devel[], and report bugs. +Since the last report, cloud-init's bug tracker has moved from Launchpad to GitHub, so this might reduce some friction. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-04-2023-06/clusteradm.adoc b/website/content/en/status/report-2023-04-2023-06/clusteradm.adoc new file mode 100644 index 0000000000..3843104b3a --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/clusteradm.adoc @@ -0,0 +1,55 @@ +=== Cluster Administration Team + +Links: + +link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[] + +Contact: Cluster Administration Team <clusteradm@FreeBSD.org> + +FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications. + +In this quarter, the team has worked on the following: + +* Regular support for FreeBSD.org user accounts. +* Regular disk and parts support (and replacement) for all physical hosts and mirrors. +* Enable mirroring of link:https://www.FreeBSD.org[] and link:https://docs.FreeBSD.org[] in the FreeBSD project-managed mirrors. +* Cluster refresh, upgrading all hosts and jails to the most recent versions of 14-CURRENT, 13-STABLE, and 12-STABLE. + +==== Work in progress + +* Large-scale network upgrade at our primary site. +** New link:https://www.juniper.net/[Juniper] switches arrived at our primary site to replace the former ones. +We thank Juniper for the donation. +* Replace old servers in our primary site and a few mirrors. +** Besides the broken CI servers, we have a few old servers with broken disks and faulty PSUs. +This task is in conjunction with The FreeBSD Foundation and donors/sponsors. +* Install new CI (Continuous Integration) machines repurposed from the package builders. +* Review the backup configuration of the services running in the FreeBSD cluster. + +==== FreeBSD Official Mirrors Overview + +Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Taiwan, United Kingdom (full mirror site), United States of America -- California, New Jersey (primary site), and Washington. + +The hardware and network connection have been generously provided by: + +* https://www.bytemark.co.uk/[Bytemark Hosting] +* Cloud and SDN Laboratory at https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc] +* https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University] +* https://deploy.equinix.com/[Equinix] +* https://internet.asn.au/[Internet Association of Australia] +* https://www.isc.org/[Internet Systems Consortium] +* https://www.inx.net.za/[INX-ZA] +* https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc] +* https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network] +* https://www.metapeer.com/[Metapeer] +* https://nic.br/[NIC.br] +* https://your.org/[Your.Org] +* https://365datacenters.com/[365 Data Centers] + +The Frankfurt single server mirror is the primary Europe mirror in bandwidth and usage. + +We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site. + +We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch. +United States (West Coast) and Europe (anywhere) are preferable places. + +See link:https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout[generic mirrored layout] for full mirror site specs and link:https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror[tiny-mirror] for a single mirror site. diff --git a/website/content/en/status/report-2023-04-2023-06/compaction.adoc b/website/content/en/status/report-2023-04-2023-06/compaction.adoc new file mode 100644 index 0000000000..fb3eb1f24a --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/compaction.adoc @@ -0,0 +1,21 @@ +=== Physical memory compaction for the FreeBSD kernel + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms[GSoC project wiki page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms[] + +link:https://reviews.freebsd.org/D40575[Differential revision 40575] URL: link:https://reviews.freebsd.org/D40575[] + +link:https://reviews.freebsd.org/D40772[Differential revision 40772] URL: link:https://reviews.freebsd.org/D40772[] + +Contact: Bojan Novković <bnovkov@FreeBSD.org> + +Most modern CPU architectures offer performance boosts by supporting pages that are larger than the standard page size. +Unfortunately, allocating such pages can fail due to a high degree of physical memory fragmentation. +This work implements physical memory compaction as a means of actively reducing fragmentation in running systems. +This work is part of an ongoing Google Summer of Code project, the goal of which is to add various physical memory anti-fragmentation measures to the virtual memory subsystem. + +Differential link:https://reviews.freebsd.org/D40575[D40575] implements a well-known metric used for quantifying the degree of physical memory fragmentation. +Differential link:https://reviews.freebsd.org/D40772[D40772] implements physical memory compaction and adds a daemon that monitors the system and performs compaction when needed. + +Planned future work includes designing an appropriate benchmarking suite, running tests, and tweaking the code using feedback from reviews and test results. +This is still a work in progress, so any testing, reviews, and feedback would be greatly appreciated. + +Sponsor: The Google Summer of Code '23 program diff --git a/website/content/en/status/report-2023-04-2023-06/core.adoc b/website/content/en/status/report-2023-04-2023-06/core.adoc new file mode 100644 index 0000000000..8e97a662f4 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/core.adoc @@ -0,0 +1,40 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team <core@FreeBSD.org> + +The FreeBSD Core Team is the governing body of FreeBSD. + +==== DevSummit 202305 + +The Core Team has presented the status update at the FreeBSD Developer Summit, 17th–18th May. +Slides are available at link:https://wiki.freebsd.org/DevSummit/202305[]. + +==== FreeBSD 14 + +The Core Team is working with other teams to ensure that FreeBSD 14.0-RELEASE will be of the highest quality. + +The Core Team has no objection to mark riscv64sf (64-bit RISC-V soft-float) as https://www.freebsd.org/platforms/[unsupported in 14]. + +==== Meetings with The FreeBSD Foundation + +The Core Team and The FreeBSD Foundation continue to meet regularly to discuss the next steps to take for the management, development, and future of FreeBSD. +The Core Team had two meetings with the Board of Directors of, and employees of, the Foundation. +They discussed how the Foundation can help the Core Team and the Project in general. + +==== Matrix IM solution + +One of the major items in the Core Team updates in DevSummit 202305 was proposing a new project communication solution. + +There is currently a testing instance at matrix-dev.FreeBSD.org setup by clusteradm. +All developers can access the instance with their kerberos credentials, and some public rooms can be joined through Matrix's federation feature. +Please note this instance is for testing and evaluating so no backup or availability is guaranteed. + +The Core Team is still discussing the scope and administration of this service, and collecting feedback from the community. + +==== Code of Conduct Committee + +Code of Conduct Committee (conduct@) is managed by the Core Team now. + +==== Commit bits + +Core approved the src commit bit for Christos Margiolis (christos@). 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 new file mode 100644 index 0000000000..2cae11159f --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/doceng.adoc @@ -0,0 +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 + +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 <doceng@FreeBSD.org> + +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 + +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 <carlavilla@FreeBSD.org> + +link:https://reviews.freebsd.org/D40546[The Network chapter is being reworked]. + +==== FreeBSD Website Revamp - WebApps working group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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/ec2.adoc b/website/content/en/status/report-2023-04-2023-06/ec2.adoc new file mode 100644 index 0000000000..d2d209c598 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/ec2.adoc @@ -0,0 +1,19 @@ +=== FreeBSD on EC2 + +Links: + +link:https://www.patreon.com/cperciva[FreeBSD/EC2 Patreon] URL: https://www.patreon.com/cperciva[] + +Contact: Colin Percival <cperciva@FreeBSD.org> + +FreeBSD is available on both x86 (Intel and AMD) and ARM64 (Graviton) EC2 instances. +Work continues to ensure that upcoming instance types will be supported, including the recently announced M7a "EPYC" instances, which should be supported in FreeBSD 14.0-RELEASE. + +Weekly FreeBSD snapshots were recently changed from "UEFI" boot mode to "UEFI Preferred" boot mode, allowing them to gain the boot performance improvement offered by UEFI while still supporting "bare metal" and "previous generation" instance types which are not compatible with UEFI. +This change will be present in FreeBSD 14.0-RELEASE. + +The EC2 boot scripts were recently updated to support IMDSv2. +This change will be present in FreeBSD 14.0-RELEASE. + +If users of FreeBSD 13.2 require any of these updates, the author can provide FreeBSD "13.2-RELEASE plus updates" AMIs. + +This work is supported by Colin's FreeBSD/EC2 Patreon. diff --git a/website/content/en/status/report-2023-04-2023-06/epoch-netgraph.adoc b/website/content/en/status/report-2023-04-2023-06/epoch-netgraph.adoc new file mode 100644 index 0000000000..786d2bc164 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/epoch-netgraph.adoc @@ -0,0 +1,32 @@ +=== Making Netgraph Lock-Free + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/LocklessSynchronizationBetweenNodesInNetgraph[Wiki Page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/LocklessSynchronizationBetweenNodesInNetgraph[] + +link:https://github.com/zinh88/epoch-netgraph[Repo] URL: link:https://github.com/zinh88/epoch-netgraph[] + +Contact: Zain Khan <zain@FreeBSD.org> + +Netgraph helps us implement custom or complex networking functions by letting us arrange kernel objects called nodes in a graph connected using hooks. +Nodes may perform a well-defined set of actions on incoming packets, and may send the output to another connected node. +To 'send' a packet to a neighbour can also be seen as calling a function on that neighbouring node. + +Now in a pre-SMP world, a thread (or *the* thread) would always see nodes as idle (not busy), so that their functions can immediately be called. +Concurrency introduced the possibility of a busy node. +Moreover, a journey of a packet also needs to take heed of changes in the structure of the graph, for example: the addressed node's path may not remain intact due to no-longer-existing hooks or nodes in between, which may lead to cases such as referring to an object that has been freed. +To counter such disasters, the existing source code uses a topology read-write mutex which protects data flow from restructuring events (and restructuring events from other restructuring events). + +We want to regain the same smooth flow for data which existed when concurrent cpus were not a thing. +That is, data should simply never wait every time there is a restructuring event. +At the same time we also obviously do not want to give the kernel reasons to panic. + +FreeBSD has its own set of concurrency-safe data structures and mechanisms. +One of these mechanisms is Epoch. +Epoch-based reclamation involves waiting for existing read-side critical sections to finish before the data structures need to be modified or reclaimed. + +Because the base system is being modified, this is also going to affect the design choices made before, such as queuing on messages, reference counting. + +This project involves a lot of testing. +For now, some topology protection locks have been removed, and only simple graphs have been tested (with FreeBSD running on a VM). +The real tests should be run on hardware with at least 4 CPU cores, I will do that when I get my hands on one. + +Sponsor: The Google Summer of Code '23 program diff --git a/website/content/en/status/report-2023-04-2023-06/freebsd-foundation.adoc b/website/content/en/status/report-2023-04-2023-06/freebsd-foundation.adoc new file mode 100644 index 0000000000..4673ee207e --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/freebsd-foundation.adoc @@ -0,0 +1,169 @@ +=== FreeBSD Foundation + +Links: + +link:https://www.freebsdfoundation.org[FreeBSD Foundation] URL: link:https://www.freebsdfoundation.org[] + +link:https://freebsdfoundation.org/blog/technology-roadmap/[Technology Roadmap] URL: link:https://freebsdfoundation.org/blog/technology-roadmap/[] + +link:https://www.freebsdfoundation.org/donate/[Donate] URL: link:https://www.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://www.freebsdfoundation.org/journal/[FreeBSD Journal] URL: link:https://www.freebsdfoundation.org/journal/[] + +link:https://www.freebsdfoundation.org/news-and-events/[Foundation News and Events] URL: link:https://www.freebsdfoundation.org/news-and-events/[] + +Contact: Deb Goodkin <deb@FreeBSDFoundation.org> + +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. +Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. +We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. +We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. + +==== Happy 30th birthday, FreeBSD! + +For more than 23 years, we have proudly backed this remarkable operating system and its vibrant community, and we eagerly anticipate supporting them for many more years. +In this update, we will outline our contributions to FreeBSD across multiple domains. +We will touch upon project development initiatives, some of which have detailed reports of their own. +Additionally, we will showcase our advocacy for FreeBSD, our efforts to foster community engagement, and our expansion of partnership endeavors. +Lastly, we will delve into our ongoing work to secure increased funding, enabling us to allocate additional resources to address any gaps within the Project. + +==== Fundraising + +During this quarter, we made significant progress in engaging with commercial FreeBSD users. +To enhance our partnerships with existing and potential commercial users, we hired Greg Wallace as the Director of Partnerships and Research. +His primary objective is to expand our collaborations with commercial users. +Since assuming this position, Greg has hit the ground running, meeting with numerous companies in just one quarter. +These interactions have provided valuable insights into how FreeBSD is being utilized, the challenges faced by users, and areas where the Project can improve. +By understanding these aspects, we can make informed decisions on where to allocate our funding and recognize FreeBSD's unique strengths. +Additionally, the role involves conducting research to identify target markets, explore new opportunities for FreeBSD, and ensure our voice is heard in relevant discussions. +For more details on Greg's objectives and accomplishments, you can refer to his status update below. + +The Foundation extends its heartfelt gratitude to everyone who made financial contributions to support our work. +Besides many individual contributions, we were pleased to receive larger donations from NetApp and Blackberry. +In addition, we received FreeBSD Developer Summit sponsorships from Tarsnap, iXsystems, and LPI. +These sponsorships greatly assist in offsetting our expenses and enable us to offer affordable registration fees to attendees. + +This year our budget is around $2,230,000, which includes increased spending toward FreeBSD advocacy and software development. +More than half of our budget is allocated toward work directly related to improving FreeBSD and keeping it secure. + +By having a dedicated individual focused on partnerships, we can effectively emphasize the significance of investing in our efforts and underscore the long-term viability of the Project to companies. + +Your support plays a crucial role in our mission, and we deeply appreciate your commitment to the FreeBSD community. +Please consider making a donation toward our 2023 fundraising campaign! +link:https://www.freebsdfoundation.org/donate/[] + +For more prominent commercial donors we have the link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[FreeBSD Foundation Partnership Program], which was established in 2017. + +==== Partnership Program + +Hello FreeBSD community. +My name is Greg Wallace. +I joined the Foundation as Director of Partnerships and Research in early April. +link:https://freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-team-members/[This blog introduced me and the role]. +For Partnerships, I am focused on building connections with companies that use FreeBSD. +I have met with several companies to learn about how they use FreeBSD. +Some of these meetings have generated discussions about potential partnership. +I continue to find out about interesting companies using FreeBSD and I am reaching out to them. + +My objective is to get in touch with every company building with and using FreeBSD to listen to their stories. +If this is you and we have not yet connected, please schedule a call on link:https://calendly.com/greg-freebsdfound/30min[my calendar]. + +Some other partnership-related activities this quarter: + +* I created link:https://docs.google.com/presentation/d/1tDCpbfxbqIucmJF6H15vK-ETrQsCMOVtxoqLem_V0Z0/edit?usp=sharing[these slides] about how partnering with the Foundation helps advance FreeBSD. + If you have ideas for how I can improve these slides, or would like me to present them to your organization, please mailto:greg@freebsdfoundation.org[send me an email], or link:https://calendly.com/greg-freebsdfound/30min[schedule a call]. + And please feel free to share the presentation liberally, in whole or in part. +* I worked with my Foundation colleagues to create a number of industry-specific use case slides for a presentation to an industry analyst. +* I am also pursuing grant opportunities with bodies including: +** NSF Secure and Trustworthy Cyberspace (SaTC) +** Sovereign Tech Fund +** NGI. + +In terms of research, my broad aim is to make sure that all of the expertise in this community is reflected in the global conversations on computing performance, security, and energy efficiency. +As a community, we have much to bring to this work. + +So far, I have been tracking and plugging into the following threads: + +* link:https://openforumeurope.org/open-source/[Open Forum Europe] +* link:https://www.nist.gov/chips/research-and-development-program[CHIPS Research and Development]. + +If you have research ideas or are interested in working together in this area, please mailto:greg@freebsdfoundation.org[send me an email], or link:https://calendly.com/greg-freebsdfound/30min[schedule a call]. + +==== OS Improvements + +During the second quarter of 2023, 339 src, 155 ports, and 20 doc tree commits identified The FreeBSD Foundation as a sponsor. +Some of this and other Foundation-sponsored work is described in separate report entries: + +* <<_continuous_integration,Continuous Integration>> +* <<_freebsd_as_a_tier_1_cloud_init_platform,FreeBSD as a Tier 1 cloud-init Platform>> +* <<_openssl_3_in_base,OpenSSL 3 in base>> +* <<_openstack_on_freebsd,OpenStack on FreeBSD>> +* <<_security_sandboxing_using_ktrace1,Security Sandboxing Using ktrace(1)>> +* <<_simd_enhancements_for_amd64,SIMD enhancements for amd64>> + +Here is a sampling of other Foundation-sponsored work: + +* Bug fixes for man:fsck_ffs[8] +* Bug fixes for man:killpg[2] +* Improvements to hwpmc +* Improvements to vmm +* Port fixes and workarounds for LLVM 16 and OpenSSL 3.0 +* Port kinst to RISC-V and related DTrace work +* Update of libfido2 to version 1.9.0 +* Various LinuxKPI 802.11 improvements +* Various RISC-V improvements +* Vendor import and update of tcpdump from version 4.9.3 to version 4.99.4. + +The status of current and past Foundation-contracted work can be viewed on the link:https://freebsdfoundation.org/our-work/projects/[Foundation Projects page]. + +Members of the Foundation's technology team presented at the Developer Summit held in Ottawa, Canada from May 17-18. +This included hosting the GSoC, link:https://wiki.freebsd.org/DevSummit/202305?action=AttachFile&do=view&target=FreeBSD_Foundation_Devsummit_Spring_2023_Day_2.pdf[FreeBSD Foundation] link:https://wiki.freebsd.org/DevSummit/202305?action=AttachFile&do=view&target=FreeBSD_Foundation_Devsummit_Spring_2023_Day_2_part1.pdf[Technical Review], and link:https://docs.google.com/presentation/d/e/2PACX-1vSnEW5Z0ttQOAeqEEY8KHkfiRGeFUm4i8XrYsfY8TNYD--yx1P6MUu2_u-mCcpe6PMMITjeDIgT31CC/pub[Workflow] working group sessions. +Pierre Pronchery spoke about link:https://www.bsdcan.org/events/bsdcan_2023/schedule/speaker/89-pierre-pronchery/[driver harmony between the BSDs] and En-Wei Wu discussed link:https://www.bsdcan.org/events/bsdcan_2023/schedule/session/139-add-operating-modes-to-wtap4/[wtap work] completed under contract with the Foundation. + +==== Continuous Integration and Quality Assurance + +The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. +You can read more about CI work in a dedicated report entry. + +==== Advocacy + +Much of our effort is dedicated to the FreeBSD Project advocacy. +This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. +The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. +Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. + +The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. +These events can be BSD-related, open source, or technology events geared towards underrepresented groups. +We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. +This all helps provide a healthy ecosystem. +We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. +We are grateful to be back to attending events mostly in person. +In addition to attending and planning events, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD. + +Check out some of the advocacy and education work we did: + +* Helped to organize and attended the link:https://wiki.freebsd.org/DevSummit/202305[May 2023 Developer Summit] which took place May 17-18, 2023 in Ottawa, Ontario +* Hosted a table and was the Tote Bag Sponsor of link:https://www.bsdcan.org/2023/[BSDCan], May 17-20, 2023 in Ottawa, Ontario +** Trip reports can be found on the link:https://freebsdfoundation.org/our-work/latest-updates/[blog] +* Celebrated the Project’s 30th Birthday at BSDCan with cake and printed copies of the special link:https://freebsdfoundation.org/past-issues/freebsd-30th-anniversary-special-edition/[30th Anniversary Edition] of the FreeBSD Journal +* Secured a FreeBSD Workshop and Talk at link:https://sfconservancy.org/fossy/[FOSSY], July 13-16, 2023, in Portland, Oregon +* Secured our Silver Sponsorship for link:https://2023.eurobsdcon.org/[EuroBSDCon 2023] taking place September 14-17, 2023 in Coimbra, Portugal +* Secured our booth for link:https://2023.allthingsopen.org/[All Things Open], October 15-17, 2023 in Raleigh, North Carolina +* Began planning the FreeBSD Fall Vendor Summit +* Welcomed two link:https://freebsdfoundation.org/blog/freebsd-foundation-welcomes-new-team-members/[New Team Members]: Greg Wallace and Pierre Pronchery +* Published link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-april-2023/[April] and link:https://freebsdfoundation.org/news-and-events/newsletter/12518/[June] Newsletters +* Celebrated the link:https://freebsdfoundation.org/national-freebsd-day/[FreeBSD Day] and the Project's 30th Anniversary on June 19 and through the week with special videos and blog posts +* Additional Blog Posts: +** link:https://freebsdfoundation.org/blog/eurobsdcon-2023-travel-grant-application-now-open/[EuroBSDcon 2023 Travel Grant Application Now Open] - Note: Applications close August 2, 2023 +** link:https://freebsdfoundation.org/blog/asiabsdcon-2023-trip-report/[AsiaBSDcon Trip Report] +* FreeBSD in the News: +** link:https://freebsdfoundation.org/news-and-events/latest-news/infoworld-happy-30th-freebsd/[InfoWorld: Happy 30th FreeBSD!]. + +We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. +As we mentioned previously, the FreeBSD Journal is now a free publication. +Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[]. + +You can find out more about events we attended and upcoming events at link:https://www.FreeBSDfoundation.org/news-and-events/[]. + +==== 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://www.freebsdfoundation.org[] to find more about how we support FreeBSD and how we can help you! diff --git a/website/content/en/status/report-2023-04-2023-06/gcc.adoc b/website/content/en/status/report-2023-04-2023-06/gcc.adoc new file mode 100644 index 0000000000..9c410652c0 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/gcc.adoc @@ -0,0 +1,48 @@ +=== GCC on FreeBSD + +Links: + +link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] + +link:https://gcc.gnu.org/gcc-10/[GCC 10 release series] URL: link:https://gcc.gnu.org/gcc-10/[] + +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/[] + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + +Upstream has released link:https://gcc.gnu.org/gcc-13[GCC 13]. +As announced in the past status report, I plan to attempt an update of GCC_DEFAULT right from the first GCC 13 release, thus much of this quarter's work has been in preparation of this. + +With the release of GCC 13.1 (first GCC 13 release: I remind that GCC counts minor version releases starting from 1), two new ports have been created in the ports tree: + +* package:lang/gcc13[], tracking GCC 13 releases; +* package:lang/gcc14-devel[], tracking snapshots from the new GCC 14 upstream branch. + +==== The *-devel ports + +Support for .init_array and .fini_array has been enabled. +FreeBSD supports both since commit gitref:83aa9cc00c2d83d05a0efe7a1496d8aab4a153bb[repository=src]. + +The default bootstrap option on i386, amd64, and aarch64 has been reverted from LTO_BOOTSTRAP to STANDARD_BOOTSTRAP: + +- LTO bootstrap produces too many failures on the package builders for those architectures +- LTO_BOOTSTRAP remains available for users who want it. + +Those changes will be forwarded to the production ports. + +==== The production ports + +Upstream has released GCC 13, for which the new port package:lang/gcc13[] has been created. +GCC 11 and GCC 12 have been updated upstream and a new release of GCC 10 is planned. +All corresponding ports now need to be updated. + +To ease the work of both ports maintainers and users, I plan to test and update together all the following changes: + +* updates of package:lang/gcc10[], package:lang/gcc11[], package:lang/gcc12[]; +* update of GCC_DEFAULT to 13; +* enabling of .init_array and .fini_array on the production ports; +* switching back from LTO_BOOTSTRAP to STANDARD_BOOTSTRAP on the production ports. + +This will provide the following advantages: + +* more testing with less exp-runs; +* fewer builds for ports users. 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 new file mode 100644 index 0000000000..8a9b22a242 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/ifapi.adoc @@ -0,0 +1,17 @@ +=== Network Interface API (IfAPI) + +Link: + +link:https://wiki.freebsd.org/projects/ifnet[Original project page] URL: link:https://wiki.freebsd.org/projects/ifnet[] + +Contact: Justin Hibbits <jhibbits@FreeBSD.org> + +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/intro.adoc b/website/content/en/status/report-2023-04-2023-06/intro.adoc new file mode 100644 index 0000000000..d88d819a89 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/intro.adoc @@ -0,0 +1,10 @@ +Here is the second 2023 status report, with 37 entries. + +As you might notice, we have several more reports than last quarter. +This is a great news and shows how much the FreeBSD community is active and always working on providing high quality software. + +In particular, please note that Summer has started and do not miss the amazing projects shared by our Google Summer of Code students. + +Have a nice read. + +Lorenzo Salvadore, on behalf of the Status Team. 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 new file mode 100644 index 0000000000..c24745351d --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/kboot.adoc @@ -0,0 +1,56 @@ +=== FreeBSD support on LinuxBoot + +Contact: Warner Losh <imp@bsdimp.com> + +Links: + +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. +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. +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/kde.adoc b/website/content/en/status/report-2023-04-2023-06/kde.adoc new file mode 100644 index 0000000000..63fdde9ef6 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/kde.adoc @@ -0,0 +1,70 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] + +link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. +The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphical desktop workstation. +The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack. + +==== Infrastructure + +Qt5 ports had various updates: + +* package:devel/qt5-webengine[] was repaired when building with Clang 16. +This is in preparation for the upcoming release of FreeBSD 14. +* package:devel/qt5-qmake[] was repaired to deal with an edge case where installing qmake on an otherwise Qt-less system would cause weird errors. + +Qt6 ports had various updates: + +* package:devel/qt6-tools[] was repaired when building with Clang 16. +This is preparation for the upcoming release of FreeBSD 14. + +The package:accessibility/at-spi2-core[] port -- essential for accessible technologies on the desktop -- was updated to release 2.48.0. + +The package:accessibility/at-spi2-core[] port now has better support for non-X11 desktops. +This is an improvement for Wayland-based systems. +Thanks to Jan Beich for landing that. + +The package:graphics/poppler[] port -- a base for many PDF viewers -- was updated to 23.05. + +The package:ports-mgmt/packagekit-qt[] port is a new addition to the tree to pave the way for graphical package managers on FreeBSD. + +==== KDE Stack + +KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. +These (large) updates land shortly after their upstream release and are not listed separately. + +* KDE Frameworks updated to 5.105, .106 and .107. +* KDE Gear updated to 23.04.0, then .1 and .2 with bugfixes. +* KDE Plasma Desktop was updated to version 5.27.4, then .5 and .6 with bugfixes. + +==== Related Ports + +Deprecations: + +* package:graphics/ikona[], an icon-viewer written in Rust with Qt bindings, has been abandoned upstream. +* package:polish/kadu[], a chat application once popular in Poland, is deprecated and upstream has disappeared. +* package:sysutils/plasma5-ksysguard[], a system monitoring application, is deprecated upstream and will no longer update. + +Updates: + +* package:astro/kstars[], an interactive planetarium, was updated to release 3.6.4. +* package:devel/qcoro[], a C++ coroutines implementation, was updated to 0.9.0. +* package:devel/qtcreator[], an integrated development environment for Qt, C++, and more, was updated to release 10.0.2. +* package:games/gcompris-qt[], an education suite for children aged 3-12, was updated to release 3.2. +* package:graphics/kphotoalbum[], a photo album and display utility, was updated to release 5.10.0. +* package:net-im/tokodon[], a Mastodon social network client, joins KDE Gear. +* package:textproc/kdiff3[], a text-differencing utility, was updated to release 1.10.1. + +New Software: + +* package:devel/kommit[], a Git client, was added. +It is a rename of previous package gitklient. +* package:multimedia/kasts[] is a new podcast-listening and enjoyment application from the KDE community. +* package:textproc/arianna[] is a mobile-oriented e-book reader from the KDE community that makes reading FreeBSD documentation a joy. 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 new file mode 100644 index 0000000000..a359e0d1da --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/linuxulator.adoc @@ -0,0 +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 <dchagin@FreeBSD.org> + +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 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/lldb-kmod.adoc b/website/content/en/status/report-2023-04-2023-06/lldb-kmod.adoc new file mode 100644 index 0000000000..af10d04ffe --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/lldb-kmod.adoc @@ -0,0 +1,20 @@ +=== LLDB Kernel Module Improvement + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement[GSoC Wiki Project] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement[] + +link:https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[Project Codebase] URL: link:https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[] + +Contact: Sheng-Yi Hong <aokblast@FreeBSD.org> + +FreeBSD project uses LLVM as its toolchain. +The LLVM project has bundled with a debugger called LLDB. +In LLDB, the userspace debugging facilities has been well implemented. +However, in the kernel space, there are still some works have to be done. +One of the work is the kernel module debug facility for LLDB - that is, parse the loaded module data provided by the kernel core dump and loading the module objects. +The goal is to implement such plugin for LLDB, and this is an ongoing GSoC Project for now. + +https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[Project Codebase] is the whole code of my work. + +Currently, this is still a work in progress and I am still debugging on it. + +Sponsor: The Google Summer of Code '23 program diff --git a/website/content/en/status/report-2023-04-2023-06/maxcpu.adoc b/website/content/en/status/report-2023-04-2023-06/maxcpu.adoc new file mode 100644 index 0000000000..3c0485946c --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/maxcpu.adoc @@ -0,0 +1,18 @@ +=== Increasing MAXCPU + +Links: + +link:https://reviews.freebsd.org/D36838[Review D36838: amd64: Bump MAXCPU to 1024 (from 256)] URL: https://reviews.freebsd.org/D36838[] + +Contact: Ed Maste <emaste@FreeBSD.org> + +The default amd64 and arm64 FreeBSD kernel configurations currently support a maximum of 256 CPUs. +A custom kernel can be built with support for larger core counts by setting the `MAXCPU` kernel option. +However, commodity systems with more than 256 CPUs are becoming available and will be increasingly common during FreeBSD 14's support lifecycle. +We want to increase the default maximum CPU count to 1024 to support these systems "out of the box" on FreeBSD 14. + +A number of changes have been made to support a larger default `MAXCPU`, including fixing the userland maximum for `cpuset_t` at 1024. +Changes have also been made to avoid static `MAXCPU`-sized arrays, replacing them with on-demand memory allocation. + +Additional work is required to continue reducing static allocations sized by `MAXCPU` and addressing scalability bottlenecks on very high core count systems, but the goal is to release FreeBSD 14 with a stable ABI and KBI with support for large CPU counts. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-04-2023-06/mfsbsd.adoc b/website/content/en/status/report-2023-04-2023-06/mfsbsd.adoc new file mode 100644 index 0000000000..b901fd6612 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/mfsbsd.adoc @@ -0,0 +1,30 @@ +=== Integrate mfsBSD into the release building tools + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools[Wiki Article] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools[] + +link:https://github.com/soobinrho/freebsd-src/tree/integrate-mfsBSD-building[Project repository (integrate-mfsBSD-building branch)] URL: link:https://github.com/soobinrho/freebsd-src/tree/integrate-mfsBSD-building[] + +Contact: Soobin Rho <soobinrho@FreeBSD.org> + +==== What is mfsBSD? + +"mfsBSD is a toolset to create small-sized but full-featured mfsroot based distributions of FreeBSD that store all files in memory (MFS) [Memory File System] and load from hard drive, usb storage device or optical media. +It can be used for a variety of purposes, including diskless systems, recovery partitions and remotely overwriting other operating systems." + +mailto:mm@FreeBSD.org[Martin Matuska] is both the author of the link:https://people.freebsd.org/~mm/mfsbsd/mfsbsd.pdf[mfsBSD white paper] and the maintainer of the link:https://github.com/mmatuska/mfsbsd[mfsBSD repository]. + +==== Purpose + +This project creates an additional target of the weekly snapshots of -current and -stable versions of mfsBSD images in the src/release makefile. +Currently, only the release versions of mfsBSD images are produced, which means they tend to get out of sync with the tools in base. +This project aims to address that problem. + +==== Location + +This is a GSoC 2023 (Google Summer of Code) project. +As such, the official coding period is between May 29, 2023 and August 28, 2023. +As a humble beginner in the open-source community, the author welcomes all comments / suggestions / pull requests in the project repository, which will be the location for all code throughout this period. + +Mentors: mailto:otis@FreeBSD.org[Juraj Lutter] and mailto:jrm@FreeBSD.org[Joseph Mingone] + +Sponsor: The Google Summer of Code '23 program diff --git a/website/content/en/status/report-2023-04-2023-06/nvmf.adoc b/website/content/en/status/report-2023-04-2023-06/nvmf.adoc new file mode 100644 index 0000000000..f9477918e4 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/nvmf.adoc @@ -0,0 +1,40 @@ +=== NVMe over Fabrics + +Links: + +link:https://github.com/bsdjhb/freebsd/tree/nvmf2[nvmf2 branch] URL: link:https://github.com/bsdjhb/freebsd/tree/nvmf2[] + +Contact: John Baldwin <jhb@FreeBSD.org> + +NVMe over Fabrics enables communication with a storage device using the NVMe protocol over a network fabric. +This is similar to using iSCSI to export a storage device over a network using SCSI commands. + +NVMe over Fabrics currently defines network transports for Fibre Channel, RDMA, and TCP. + +The work in the nvmf2 branch includes a userland library ([.filename]#lib/libnvmf#) which contains an abstraction for transports and an implementation of +a TCP transport. +It also includes changes to man:nvmecontrol[8] to add 'discover', 'connect', and 'disconnect' commands to manage connections to a remote controller. + +The branch also contains an in-kernel Fabrics implementation. +[.filename]#nvmf_transport.ko# contains a transport abstraction that sits in between the nvmf host (initiator in SCSI terms) and the individual transports. +[.filename]#nvmf_tcp.ko# contains an implementation of the TCP transport layer. +[.filename]#nvmf.ko# contains an NVMe over Fabrics host (initiator) which connects to a remote controller and exports remote namespaces as disk devices. +Similar to the man:nvme[4] driver for NVMe over PCI-express, namespaces are exported via [.filename]#/dev/nvmeXnsY# devices which only support simple operations, but are also exported as ndaX disk devices via CAM. +Unlike man:nvme[4], man:nvmf[4] does not support the man:nvd[4] disk driver. +man:nvmecontrol[8] can be used with remote namespaces and remote controllers, for example to fetch log pages, display identify info, etc. + +Note that man:nvmf[4] is currently a bit simple and some error cases are still a TODO. +If an error occurs, the queues (and backing network connections) are dropped, but the devices stay around, with I/O requests paused. +`nvmecontrol reconnect` can be used to connect a new set of network connections to resume operation. +Unlike iSCSI which uses a persistent daemon (man:iscsid[8]) to reconnect after an error, reconnections must be made manually. + +The current code is very new and likely not robust. +It is certainly not ready for production use. +Experienced users who do not mind all their data vanishing in a puff of smoke after a kernel panic, and who have an interest in NVMe over Fabrics, can start testing it at their own risk. + +The next main task is to implement a Fabrics controller (target in SCSI language). +Probably a simple one in userland first followed by a "real" one that offloads the data handling to the kernel but is somewhat integrated with man:ctld[8] so that individual disk devices can be exported via iSCSI or NVMe, or via both using a single config file and daemon to manage all of that. +This may require a fair bit of refactoring in ctld to make it less iSCSI-specific. +Working on the controller side will also validate some of the currently under-tested API design decisions in the transport-independent layer. +I think it probably does not make sense to merge any of the NVMe over Fabrics changes into the tree until after this step. + +Sponsored by: Chelsio Communications diff --git a/website/content/en/status/report-2023-04-2023-06/openssl3.adoc b/website/content/en/status/report-2023-04-2023-06/openssl3.adoc new file mode 100644 index 0000000000..c939fdb790 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/openssl3.adoc @@ -0,0 +1,38 @@ +=== OpenSSL 3 in base + +Links: + +link:https://www.openssl.org/source/[OpenSSL Downloads] URL: link:https://www.openssl.org/source/[] + +link:https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/[OpenSSL 3.0 Has Been Released!] URL: link:https://www.openssl.org/blog/blog/2021/09/07/OpenSSL3.Final/[] + +link:https://www.openssl.org/docs/man3.0/man1/openssl-fipsinstall.html[openssl-fipsinstall] URL: link:https://www.openssl.org/docs/man3.0/man1/openssl-fipsinstall.html[] + +Contact: Pierre Pronchery <pierre@freebsdfoundation.org> + +Pierre has been tasked with importing OpenSSL 3 into the base system. + +OpenSSL is a library for general-purpose cryptography and secure communication. +It provides an open source implementation of the SSL and TLS network protocols, which are widely used in applications such as e-mail, instant messaging, Voice over IP (VoIP), or more prominently the global Web (aka HTTPS). +Assuming that the Apache and nginx web servers use OpenSSL, their combined market share for web traffic exceeds 50%, cementing the leadership and critical importance of OpenSSL as part of the infrastructure of the Internet. + +Since its initial release in August 2016, the 1.1 branch of OpenSSL has been adopted by most Linux and BSD systems, while remaining supported by the upstream maintainers through an LTS (long term support) policy. +However, official support is planned to end in the middle of September this year, and it became urgent and necessary to consider adopting its successor for LTS, the 3.0 branch. + +OpenSSL has largely outgrown its ancestor SSLeay, now shipping over half a million single lines of code (SLOC) split in over two thousand files. +Perhaps as a consequence, its build system is relatively complex and normally requires Perl, which was removed from base more than twenty years ago for FreeBSD 5.0-RELEASE. +Thankfully however, it was possible to import and setup OpenSSL 3.0.9 the FreeBSD way, and it is now part of the base system as planned for FreeBSD 14.0-RELEASE. + +To describe OpenSSL 3 as a major release is an understatement. +First, its problematic licensing model has finally been solved, with a complete switch to the Apache License 2.0. +Then, OpenSSL 3 introduces the concept of provider modules. +While obsolete cryptographical algorithms have been isolated to a _legacy_ module, it is also possible to restrict the implementation to the standards part of link:https://en.wikipedia.org/wiki/Federal_Information_Processing_Standards[FIPS] with the _fips_ module. +The latter can then benefit from a dedicated certification process, and be validated officially (like the 3.0.8 release at the time of writing). + +Moreover, the updated library comes with a version bump, as applications using OpenSSL 1.1 need to be recompiled to use 3.0. +Many API functions have been deprecated and replaced with newer, more generic alternatives, however it is still possible to explicitly request older APIs and have OpenSSL 3 expose them accordingly. +This possibility has been leveraged in FreeBSD to help with the transition, where a number of libraries and applications have simply been configured to request the OpenSSL 1.1 API. +These components will be updated progressively over time in order to consume OpenSSL 3's native API instead. + +While there is a known performance impact associated with the update when consuming small input block sizes, it was found to be marginal when working with blocks of 1 KB and above. +Another challenge lies with the FIPS provider module, which currently requires some manual steps in order to have it working. +We are currently looking for a solution to ship FreeBSD with a functional FIPS provider by default. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-04-2023-06/openstack.adoc b/website/content/en/status/report-2023-04-2023-06/openstack.adoc new file mode 100644 index 0000000000..b95a65099c --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/openstack.adoc @@ -0,0 +1,30 @@ +=== OpenStack on FreeBSD + +Links: + +link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] + +link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[] + +Contact: Chih-Hsin Chang <starbops@hey.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +This project aims to port key OpenStack components such as keystone, nova, and neutron, so that FreeBSD can function as an OpenStack host. + +We started porting `nova-novncproxy` and `nova-serialproxy` to increase the ways to access the instance console. +To lower the threshold for people who want to give it a try on the project, we also migrated our development environment from a physical machine to a virtual one. +There is still a problem running bhyve VMs on top of Linux KVM. +A detailed writeup for the issue can be found link:https://hackmd.io/@starbops/SkdJON2un[here]. +Other achievements include: + +* Sorting out network connectivity issues inside the instances +* Able to spawn multiple instances +* Porting from Python 3.8 to 3.9. + +In the next quarter, we will continue working on the console proxy services to make the overall workflow more fluent. + +The step-by-step documents for constructing a POC site can also be found link:https://github.com/openstack-on-freebsd/docs[in the `docs` repository]. +The patched version of each OpenStack component is under the same GitHub organization. + +People interested in helping with the project can first help check the documentation by following the installation guide. +Feedback and help are always welcome. + +Sponsor: The FreeBSD Foundation 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 new file mode 100644 index 0000000000..0e572983cf --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/pf.adoc @@ -0,0 +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 <vegeta@tuxpowered.net> + +Contact: Naman Sood <naman@freebsdfoundation.org> + +Contact: Kristof Provost <kp@FreeBSD.org> + +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: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-04-2023-06/pkgbase.live.adoc b/website/content/en/status/report-2023-04-2023-06/pkgbase.live.adoc new file mode 100644 index 0000000000..b2a8717328 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/pkgbase.live.adoc @@ -0,0 +1,37 @@ +=== PkgBase.live + +Links: + +link:https://alpha.pkgbase.live/[Website] URL: link:https://alpha.pkgbase.live/[] + +link:https://codeberg.org/pkgbase[Source] URL: link:https://codeberg.org/pkgbase[] + +Contact: Mina Galić <freebsd@igalic.co> + +PkgBase.live, an unofficial repository for the FreeBSD link:https://wiki.freebsd.org/PkgBase[PkgBase project], is back alive. + +As a service, PkgBase.live was inspired by link:https://up.bsd.lv/[], which provided man:freebsd-update[8] for STABLE and CURRENT branches. +up.bsd.live itself has gone on hiatus, so it was all the more reason to bring back PkgBase.live. + +Right now, we provide builds for: + +- FreeBSD 13.2-RELEASE +- FreeBSD 13-STABLE +- FreeBSD 14-CURRENT + +each for the following platforms: + +- amd64 +- aarch64 +- armv7 +- i386 + +You may notice that RISCv64 is gone for now. + +The hardware is a powerful VPS in Vultr. +The server and the jails running build jobs and serving packages are "self-hosting", meaning they were installed and are kept up-to-date with PkgBase. + +Because we have not figured out yet how to configure Vultr's IPv6 in FreeBSD jails, PkgBase.live is not available over IPv6 for now. +If you have experience with that, please contact us! + +Along with users and testers, we still link:https://alpha.pkgbase.live/howto/howdo.html[highly encourage copy-cats]. + +Hardware for PkgBase is kindly sponsored by a member of the FreeBSD community. 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 new file mode 100644 index 0000000000..8e420d374d --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/portmgr.adoc @@ -0,0 +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 <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. +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. +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 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 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/pot.adoc b/website/content/en/status/report-2023-04-2023-06/pot.adoc new file mode 100644 index 0000000000..97966e5c34 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/pot.adoc @@ -0,0 +1,25 @@ +=== 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) <pizzamig@FreeBSD.org> + +Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org> + +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]. + +During this quarter, link:https://github.com/bsdpot/pot/releases/tag/0.15.5[Pot 0.15.5] was released, containing a number of bugfixes and link:https://github.com/bsdpot/pot/pull/263[features to set attributes (i.e. jail sysctl variables)] from various contributors. +It will be available in the 2023Q3 quarterly package set. + +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. + +All Potluck containers have been rebuilt as FreeBSD 13.2 based images and are signed with link:https://github.com/bsdpot/pot/pull/242[Pot signify] now. + +link:https://honeyguide.eu/posts/ansible-pot-foundation/[A Beginner's Guide to Building a Virtual Datacenter on FreeBSD with Ansible, Pot and More] has been written, explaining how a complex environment based on Pot and Potluck can be deployed with Ansible playbooks, including example nodes like MariaDB, Prometheus, Grafana, nginx, OpenLDAP or Traefik and container orchestration managed by Nomad and Consul. + +A link:https://github.com/hashicorp/nomad/pull/13343[patch by the pot team] to improve Nomad security, a scheduler and orchestrator which supports Pot through package:sysutils/nomad-pot-driver[], has been accepted upstream and will be part of Nomad 1.6.0. + +As always, feedback and patches are welcome. + +Sponsor: Honeyguide Group diff --git a/website/content/en/status/report-2023-04-2023-06/puppet.adoc b/website/content/en/status/report-2023-04-2023-06/puppet.adoc new file mode 100644 index 0000000000..031d5cc981 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/puppet.adoc @@ -0,0 +1,21 @@ +=== Puppet + +Links: + +link:https://puppet.com/docs/puppet/latest/puppet_index.html[Puppet] URL: link:https://puppet.com/docs/puppet/latest/puppet_index.html[] + + +Contact: Puppet Team <puppet@FreeBSD.org> + +Puppet is a Free Software configuration management tool, composed of a source of trust (Puppet Server) that describes the expected configuration of machines with a domain-specific language, and an agent (Puppet Agent) on each node which enforces that the actual configuration matches the expected one. +An optional database (PuppetDB) can be setup for reporting and describing advanced schemas where the configuration of a machine depends on the configuration of another one. + +The Puppet team is maintaining ports for Puppet and related tools. + +Puppet 8 has been recently released and has been added to the ports tree. + +Puppet 6 has reached End of Life and has been deprecated. +It is now expired. +Users of Puppet 6 are therefore advised to update to Puppet 7 or Puppet 8. + +For now, Puppet 7 remains the default Puppet version for ports depending on Puppet. +The Puppet Community is hard at work making sure the various Puppet modules work with the latest code and at the time of writing this report, updating to Puppet 8 may be challenging. +The situation is getting better every day, and we expect to switch to Puppet 8 as the default version of Puppet in a few months, when the wave of module updates is finished. diff --git a/website/content/en/status/report-2023-04-2023-06/releng.adoc b/website/content/en/status/report-2023-04-2023-06/releng.adoc new file mode 100644 index 0000000000..6cbf1a8cb6 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/releng.adoc @@ -0,0 +1,24 @@ +=== FreeBSD Release Engineering Team + +Links: + +link:https://www.freebsd.org/releases/13.2R/schedule/[FreeBSD 13.2-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.2R/schedule/[] + +link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[] + +link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] + +link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[] + +Contact: FreeBSD Release Engineering Team <re@FreeBSD.org> + +The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. + +During the second quarter of 2023, the Team continued work on 13.2-RELEASE. +The 13.2 cycle had closely followed the set schedule, with the addition of three additional RC builds at the end, and the final RELEASE build and announcement in mid-April. + +In coordination with various teams within the Project management, the FreeBSD Release Engineering Team reconsidered the original schedule for the upcoming 14.0-RELEASE, primarily due to work that was in progress. +The updated schedule was discussed and adjusted slightly to account for some concerns, and ultimately published on the FreeBSD Project website. +The new schedule targets 14.0-RELEASE for October, 2023. + +The Team continued providing weekly development snapshot builds for the `main`, `stable/13`, and `stable/12` branches. +Note, there will no longer be snapshot builds against `stable/12` moving forward. + +Sponsor: Tarsnap + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-04-2023-06/service-jails.adoc b/website/content/en/status/report-2023-04-2023-06/service-jails.adoc new file mode 100644 index 0000000000..5a66d24a20 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/service-jails.adoc @@ -0,0 +1,26 @@ +=== Service Jails -- automatic jailing of rc.d services + +Links: + +link:https://reviews.freebsd.org/D40369[D40369: Extend /usr/bin/service with the possibility to set ENV vars] URL: link:https://reviews.freebsd.org/D40369[] + +link:https://reviews.freebsd.org/D40370[D40370: Infrastructure for automatic jailing of rc.d-services] URL: link:https://reviews.freebsd.org/D40370[] + +link:https://reviews.freebsd.org/D40371[D40371: automatic service jails: some setup for full functionality of the services in automatic service jails] URL: link:https://reviews.freebsd.org/D40371[] + +Contact: Alexander Leidinger <netchild@FreeBSD.org> + +Service jails extend the man:rc[8] system to allow automatic jailing of rc.d services. +A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, ...) by default. +Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (man:vmm[4]). + +If you want to put e.g. local_unbound into a service jail and allow IPv4 and IPv6 access, simply change man:rc.conf[5] to have: +---- +local_unbound_svcj_options=net_basic +local_unbound_svcj=YES +---- + +While this does not have the same security benefits of a manual jail setup with a separate filesystem and IP/VNET, it is much easier to setup, while providing some of the security benefits of a jail like hiding other processes of the same user. + +The patches in the links are a rewrite of link:https://lists.freebsd.org/pipermail/freebsd-jail/2019-February/003710.html[what I presented in 2019]. +The main difference is that an ENV variable is used to do more rational tracking and as such, requires a change to man:service[8]. + +My intent is to commit link:https://reviews.freebsd.org/D40369[D40369] before the branch of `stable/14`. +I will not commit link:https://reviews.freebsd.org/D40370[D40370] or link:https://reviews.freebsd.org/D40371[D40371] before 14.0 is released and both will benefit from more eyes. 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 new file mode 100644 index 0000000000..682724a37a --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/simd.adoc @@ -0,0 +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[] + +Contact: Robert Clausecker <clausecker@FreeBSD.org> + +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 diff --git a/website/content/en/status/report-2023-04-2023-06/squashfs.adoc b/website/content/en/status/report-2023-04-2023-06/squashfs.adoc new file mode 100644 index 0000000000..874062ac88 --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/squashfs.adoc @@ -0,0 +1,20 @@ +=== SquashFS port for FreeBSD kernel + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel[Wiki page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel[] + +link:https://github.com/Mashijams/freebsd-src/tree/gsoc/squashfs[Source code] URL: link:https://github.com/Mashijams/freebsd-src/tree/gsoc/squashfs[] + +Contact: Raghav Sharma <raghav@FreeBSD.org> + +SquashFS is a read-only file system that lets you compress whole file systems or single directories very efficiently. +Support for it has been built into the Linux kernel since 2009 and is very common in embedded Linux distributions. +The goal of this project is to add SquashFS support for the FreeBSD kernel, with the aim of being able to boot FreeBSD from an in-memory SquashFS file system. + +Currently, the driver is compatible with the 13.2 FreeBSD release. +The driver is able to correctly parse the SquashFS disk file with working man:mount[8] support. +Linux SquashFS supports many compression options like zstd, lzo2, zlib, etc... based on the user's preference, and of course, our driver supports all those compressions as well. + +Planned future work includes adding directories, files, extended attributes, and symlinks read support. +The project is still a work in progress under the mentorship from mailto:chuck@FreeBSD.org[Chuck Tuffli] and is expected to complete by the end of the Google Summer of Code program. + +Sponsor: The Google Summer of Code 2023 program diff --git a/website/content/en/status/report-2023-04-2023-06/wazuh.adoc b/website/content/en/status/report-2023-04-2023-06/wazuh.adoc new file mode 100644 index 0000000000..9f75482dba --- /dev/null +++ b/website/content/en/status/report-2023-04-2023-06/wazuh.adoc @@ -0,0 +1,39 @@ +=== Wazuh on FreeBSD + +Links: + +link:https://www.wazuh.com/[Wazuh] URL: link:https://www.wazuh.com/[] + +Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org> + +Wazuh is a free and open source platform used for threat prevention, detection, and response. +It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments. + +The Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data gathered by the agents. +Wazuh features include full integration with https://www.elastic.co/elastic-stack/[Elastic Stack] and https://opensearch.org/[OpenSearch], providing a search engine and data visualization tool through which users can navigate security alerts. + +Wazuh porting to FreeBSD was started by mailto:m.muenz@gmail.com[Michael Muenz]. +His first Wazuh addition to the ports tree was package:security/wazuh-agent[] in September 2021. +In July 2022, I took maintainership of this port and started porting other Wazuh components. + +Currently, all Wazuh components are ported or adapted: package:security/wazuh-manager[], package:security/wazuh-agent[], package:security/wazuh-server[], package:security/wazuh-indexer[], and package:security/wazuh-dashboard[]. + +On FreeBSD, package:security/wazuh-manager[] and package:security/wazuh-agent[] are compiled from Wazuh source code. +package:security/wazuh-indexer[] is an adapted package:textproc/opensearch[] used for storing agents data. +package:security/wazuh-server[] includes FreeBSD-oriented adaptions to configuration files. +Runtime dependencies comprise package:security/wazuh-manager[], package:sysutils/beats8[] (filebeat), and package:sysutils/logstash8[]. +package:security/wazuh-dashboard[] uses an adapted package:textproc/opensearch-dashboards[] and the wazuh-kibana-app plugin generated from wazuh-kibana-app source code for FreeBSD. + +The main goal of this work is enhancing visibility of FreeBSD as a useful platform for information security or cybersecurity. + +Additionally, you can easily test a Wazuh single-node infrastructure (All-in-one) using link:https://github.com/alonsobsd/wazuh-makejail[] or link:https://github.com/AppJail-makejails/wazuh[] from link:https://github.com/DtxdF/AppJail[AppJail]. +AppJail is a good tool for managing jail containers from the command line. + +People interested in helping with the project are welcome. + +Current version: 4.4.4 + +TODO + +* Add Wazuh cluster-mode infrastructure makejail (Work in progress) +* Add FreeBSD to platforms officially supported by Wazuh Inc; see link:https://github.com/wazuh/wazuh-kibana-app/pull/5413[] +* Add FreeBSD SCA Policy (Work in progress) diff --git a/website/content/en/status/report-2023-07-2023-09/_index.adoc b/website/content/en/status/report-2023-07-2023-09/_index.adoc new file mode 100644 index 0000000000..4287d0b3fb --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/_index.adoc @@ -0,0 +1,212 @@ +--- +title: "FreeBSD Status Report Third 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-07-2023-09 + +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}/ci.adoc[] + +''' + +include::{reports-path}/portmgr.adoc[] + +''' + +[[projects]] +== Projects + +{projects-desc} + +include::{reports-path}/desktop-convenience.adoc[] + +''' + +include::{reports-path}/lldb-kmod.adoc[] + +''' + +[[userland]] +== Userland + +{userland-desc} + +''' + +include::{reports-path}/openssl3.adoc[] + +''' + +include::{reports-path}/login_classes.adoc[] + +''' + +[[kernel]] +== Kernel + +{kernel-desc} + +''' + +include::{reports-path}/ufs_snapshots.adoc[] + +''' + +include::{reports-path}/squashfs.adoc[] + +''' + +include::{reports-path}/process_visibility.adoc[] + +''' + +include::{reports-path}/linuxulator.adoc[] + +''' + +[[architectures]] +== Architectures + +{architectures-desc} + +''' + +include::{reports-path}/dpaa2.adoc[] + +''' + +include::{reports-path}/simd.adoc[] + +''' + +include::{reports-path}/mfsbsd.adoc[] + +''' + +[[cloud]] +== Cloud + +{cloud-desc} + +''' + +include::{reports-path}/openstack.adoc[] + +''' + +include::{reports-path}/azure.adoc[] + +''' + +include::{reports-path}/ec2.adoc[] + +''' + +[[documentation]] +== Documentation + +{documentation-desc} + +''' + +include::{reports-path}/doceng.adoc[] + +''' + +include::{reports-path}/freebsd-online-editor.adoc[] + +''' + +include::{reports-path}/expert-system.adoc[] + +''' + +[[ports]] +== Ports + +{ports-desc} + +''' + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/pantheon.adoc[] + +''' + +include::{reports-path}/office.adoc[] + +''' + +include::{reports-path}/wifibox.adoc[] + +''' + +include::{reports-path}/gcc.adoc[] + +''' + +include::{reports-path}/valgrind.adoc[] + +''' + +include::{reports-path}/gitlab.adoc[] + +''' + +include::{reports-path}/portoptscli.adoc[] + +''' + +[[third-Party-Projects]] +== Third Party Projects + +{third-Party-Projects-desc} + +''' + +include::{reports-path}/bsd-cafe.adoc[] + +''' + +include::{reports-path}/pot.adoc[] diff --git a/website/content/en/status/report-2023-07-2023-09/azure.adoc b/website/content/en/status/report-2023-07-2023-09/azure.adoc new file mode 100644 index 0000000000..4fabe12eee --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/azure.adoc @@ -0,0 +1,56 @@ +=== 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 <bsdic@microsoft.com> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] + +Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> + +Contact: Wei Hu <whu@FreeBSD.org> + +Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + + +In this quarter, we have worked mainly on ARM64 architecture support and building and publishing both UFS and ZFS based 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 +* FreeBSD-CURRENT-zfs-testing +* FreeBSD-CURRENT-zfs-gen1-testing + +To use them, when creating a virtual machine: + +. In `Select an Image` step, choose `Community Images` in `Other items` +. Search `FreeBSD` + +We are aiming to provide all those images for 14.0-RELEASE. + +Work in progress tasks: + +* Automating the image building and publishing process and merge to src/release/. +* Building and publishing all supported 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 have fixed several critical bugs in arm64: + +* https://bugs.freebsd.org/267654 +* https://bugs.freebsd.org/272461 +* https://bugs.freebsd.org/272666 + +The root cause was identified and fixed in link:https://cgit.freebsd.org/src/commit/?id=e7a9817b8d328dda04069b65944ce2ed6f54c6f0[e7a9817b8d32: Hyper-V: vmbus: implementat bus_get_dma_tag in vmbus] + +And continue working on improving Microsoft Azure Network Adapter (MANA) support. + +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-07-2023-09/bsd-cafe.adoc b/website/content/en/status/report-2023-07-2023-09/bsd-cafe.adoc new file mode 100644 index 0000000000..5b92d195ee --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/bsd-cafe.adoc @@ -0,0 +1,41 @@ +=== Introducing the BSD Cafe project + +Links: + +link:https://wiki.bsd.cafe/[BSD Cafe project homepage] URL: link:https://wiki.bsd.cafe/[] + +link:https://mastodon.bsd.cafe/[BSD Cafe Mastodon instance] URL: link:https://mastodon.bsd.cafe/[] + +Contact: Stefano Marinelli <stefano@dragas.it> + +We are thrilled to unveil the inaugural component of the BSD Cafe project! + +Months ago, when I first registered the link:https://bsd.cafe/[bsd.cafe] domain, I envisioned a themed bar where friends, acquaintances, and patrons could gather for casual conversations about ++*++BSD systems, Linux, and open-source technology. +Just like any bar, our discussions can encompass a wide array of topics, all while maintaining a spirit of mutual respect. + +BSD Cafe is poised to become a hub for a variety of tools and services, all powered by ++*++BSD. + +Our initial offering is a brand-new instance of link:https://joinmastodon.org/[Mastodon] (open-source +microblogging software and service), serving as a gateway to the fediverse -- a federation of services, many of which use the link:https://www.w3.org/TR/activitypub[ActivityPub] decentralised social networking protocol. +Registration is now open. +The server operates under clearly defined guidelines that promote positive conduct and unequivocally prohibit any form of hate. +Inclusiveness, respect, and constructive dialogue stand as the cornerstones of this instance. + +Our primary server is currently hosted in Finland on a small VM, running on FreeBSD. +Services are partitioned into VNET jails, interconnected within a local area network through a dedicated bridge. +Additionally, we implement a VPN system and have the flexibility to migrate individual jails to more robust machines. + +For multimedia data and cache hosting, we employ a separate physical server (also FreeBSD-based, within a jail), fronted by Cloudflare. +The goal here is to cache and geodistribute data, effectively reducing network congestion on the main VPS. + +Our reverse proxy (frontend), mail server, media server, and the instance itself are all accessible via IPv6. + +At its inception, this Mastodon instance was devoid of preloaded content. +Our intention is for it to grow organically, based on the interests and followers of its users. +At this stage, we have refrained from preemptive blocks. +We strongly encourage users to promptly report anything that they believe requires attention. + +We invite you to join us at link:https://mastodon.bsd.cafe/[] in order to cultivate a community that values constructive interactions and embraces inclusiveness -- a secure and serene space meant for all. + +Furthermore, we have established a website at link:https://wiki.bsd.cafe/[], which will provide an overview of our tools, services, rules, uptime, and more. + +Recently, a Miniflux installation has been performed, so the BSD Cafe users can use it as a personal RSS Feed Reader. +More information: link:https://wiki.bsd.cafe/miniflux-bsd-cafe[]. diff --git a/website/content/en/status/report-2023-07-2023-09/ci.adoc b/website/content/en/status/report-2023-07-2023-09/ci.adoc new file mode 100644 index 0000000000..b237cada8e --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/ci.adoc @@ -0,0 +1,50 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] + +link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://https://tinderbox.freebsd.org[] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] + +link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] + +link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] + +link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] + +link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +In the third quarter of 2023, we worked with the project contributors and developers to address their testing requirements. +Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. + +Important completed tasks: + +* Add jobs for stable/14 branch +* Update the link:https://tinderbox.freebsd.org["Tinderbox" view] of the CI results, now includes test results and the "starting point" of the current failing or unstable series. + * This is mainly done by the Foundation intern, Yan-Hao Wang. His other contributions are in the other entry of this report. + +Work in progress tasks: + +* Designing and implementing pre-commit CI building and testing and pull/merged-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) + * Proof of concept system is in progress. +* Designing and implementing use of CI cluster to build release artifacts as release engineering does +* Simplifying CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Improving the hardware test lab and adding more hardware for testing +* Merge link:https://reviews.freebsd.org/D38815[] +* Merge link:https://reviews.freebsd.org/D36257[] + +Open or queued tasks: + +* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] +* Setting up public network access for the VM guest running tests +* Implementing use of bare-metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort! + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-07-2023-09/core.adoc b/website/content/en/status/report-2023-07-2023-09/core.adoc new file mode 100644 index 0000000000..e77d53003e --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/core.adoc @@ -0,0 +1,41 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team <core@FreeBSD.org> + +The FreeBSD Core Team is the governing body of FreeBSD. + +==== Demise of Hans Petter Selasky + +The FreeBSD Core Team would like to thank Hans Petter Selasky for his years of service. +We were saddened by his death and joined the community in mourning. + +link:https://lists.freebsd.org/archives/freebsd-announce/2023-July/000076.html[In Memoriam]. + +==== Meetings with The FreeBSD Foundation + +The Core Team and The FreeBSD Foundation continue to meet to discuss the next steps to take for the management, development, and future of FreeBSD. +The Core Team had two meetings with the Board of Directors, and employees of, the Foundation. +They discussed how the Foundation can help the Core Team and the Project in general. + +==== Portmgr termlimits + +The Core Team discussed with the Ports Management Team the introduction of a time limit in which a developer can belong to the team. +The proposal was approved by the Ports Management Team and will take effect at the beginning of 2024, with regular lurker programs to have a steady stream of new Ports Management Team members. + +==== Deprecation of 32-bit platforms for FreeBSD 15 + +Work is underway to mark support for 32-bit platforms as "deprecated" for FreeBSD 15. + +==== Matrix IM + +The testing of the Matrix instance and the Element-web client is still in progress. + +The beta is planned to be released after EuroBSDCon in September. + +==== Improve Commit Bit Expiration Policy + +The Core Team will clarify how to update the PGP key once a developer has become Alumni. + +==== EuroBSDCon + +Core Team members met with the FreeBSD Foundation in Coimbra during EuroBSDcon to discuss the direction of the Project. diff --git a/website/content/en/status/report-2023-07-2023-09/desktop-convenience.adoc b/website/content/en/status/report-2023-07-2023-09/desktop-convenience.adoc new file mode 100644 index 0000000000..f20a86311e --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/desktop-convenience.adoc @@ -0,0 +1,25 @@ +=== Filling gaps in the FreeBSD desktop experience + +Links: + +link:https://github.com/outpaddling/qmediamanager[External media manager] URL: link:https://github.com/outpaddling/qmediamanager[] + +link:https://github.com/outpaddling/devd-mount[devd-based automounter] URL: link:https://github.com/outpaddling/devd-mount[] + +link:https://github.com/outpaddling/npmount[SUID mount tool] URL: link:https://github.com/outpaddling/npmount[] + +link:https://github.com/outpaddling/freebsd-update-notify[Popup notification for updates] URL: link:https://github.com/outpaddling/freebsd-update-notify[] + +Contact: Jason Bacon <jwb@FreeBSD.org> + +The package:sysutils/desktop-installer[] port, available for over a decade now, quickly configures a bare FreeBSD system with any desktop environment or window manager. +However, the FreeBSD base and ports collection has been missing some common features that end users expect from a desktop OS. + +The desktop-installer battery monitor script has been enhanced to display popup notifications at various levels of charge/discharge. + +package:deskutils/qmediamanager[], in conjunction with package:sysutils/devd-mount[] and package:sysutils/npmount[], mounts inserted media upon notification from devd, and displays a popup window offering the user options to show filesystem information, open a file manager, reformat, copy a disk image to the device, or unmount. +It provides a convenient and secure way to work with external media such as USB sticks. + +A fourth new port -- package:deskutils/freebsd-update-notify[] -- displays a popup when new base updates are available, or when a configurable time limit has elapsed. +If the user chooses to proceed with updates, the entire system is updated (packages, ports, and base) with man:auto-update-system[1] (a feature of package:sysutils/auto-admin[]). + +These new tools bring the FreeBSD desktop experience a step closer to the convenience of the most popular desktop operating systems. + +The tools are effectively prototypes, stable and reliable, but in need of review. +Feedback from users regarding default behavior and configuration options will be appreciated. diff --git a/website/content/en/status/report-2023-07-2023-09/doceng.adoc b/website/content/en/status/report-2023-07-2023-09/doceng.adoc new file mode 100644 index 0000000000..1488da6997 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/doceng.adoc @@ -0,0 +1,105 @@ +//// +Quarter: 3rd quarter of 2023 +Prepared by: fernape +Reviewed by: carlavilla +Last edit: $Date: 2023-06-30 13:48:30 +0200 (Fri, 30 Jun 2023) $ +Version: $Id: doceng-2023-2nd-quarter-status-report.adoc 416 2023-06-30 11:48:30Z fernape $ +//// + +=== 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[] + +Contact: FreeBSD Doceng Team <doceng@FreeBSD.org> + +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: + +* The search functionality of the documentation portal was moved from DuckDuckGo to our own search engine; for more information, see link:https://cgit.freebsd.org/doc/commit/?id=ac4fd34edfa1e5e2edb6fb9fc61acd782a0ed33b[this commit] +* grahamperrin@'s doc commit bit was taken for safekeeping as per his request +* pluknet@'s doc commit bit was taken for safekeeping as per his request. + +==== Porter's Handbook + +New `USES` knobs have been added to the Handbook: + +* link:https://cgit.freebsd.org/doc/commit/?id=ee08121ef177489c031870601de1cc728de646e5[`USES= ebur128`]. +* link:https://cgit.freebsd.org/doc/commit/?id=4f16184d81f1c02196d91e8d2511f23fd48e8822[`USES= guile`]. + +==== 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/[] + +===== Q3 2023 Status + +* 17 team languages +* 189 registered users + +Four new translators joined Weblate: + +* minso in Korean (ko) and French (fr_FR) +* strgalt-t in German (de_DE) +* bsdmeg in German (de_DE) +* mvsf in Portuguese (pt_BR) + +===== 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: 33%) +* Norwegian (nb-no) (progress: 1%) +* Persian (fa-ir) (progress: 2%) +* Polish (progress: 1%) +* Portuguese (progress: 0%) +* Portuguese (pt-br) (progress: 22%) +* Spanish (es) (progress: 35%) +* 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 <carlavilla@FreeBSD.org> + +* link:https://reviews.freebsd.org/D40546[The Network chapter has been rewritten] +* link:https://cgit.freebsd.org/doc/commit/?id=612b7cc1721224c494c5b2600188e1508bb5611b[The Jails chapter has been rewritten] +* The next section to work on will be the file systems part: UFS, OpenZFS, Other File Systems. + +==== FAQ Working Group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +The idea is to write a new FAQ. +Will be released alongside FreeBSD 14.0. + +==== FreeBSD Website Revamp -- WebApps Working Group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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 will be divided into three phases: + +. Redesign of the Manual Pages on web ++ +Scripts to generate the HTML pages using mandoc. (_Complete, Approved by Doceng, Deploy Date Not Decided Yet_) +Public instance on https://man-dev.FreeBSD.org + +. Redesign of the FreeBSD main website ++ +New design, responsive and dark theme. (_Almost Complete, Presented at EuroBSDCon_) + +. Redesign of the Ports page on web ++ +Ports scripts to create an applications portal. (_Work in progress_) diff --git a/website/content/en/status/report-2023-07-2023-09/dpaa2.adoc b/website/content/en/status/report-2023-07-2023-09/dpaa2.adoc new file mode 100644 index 0000000000..ca15bfdaf0 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/dpaa2.adoc @@ -0,0 +1,35 @@ +=== NXP DPAA2 support + +Links: + +link:https://cgit.freebsd.org/src/tree/sys/dev/dpaa2[DPAA2 in the FreeBSD source tree] URL: link:https://cgit.freebsd.org/src/tree/sys/dev/dpaa2[] + +link:https://github.com/mcusim/freebsd-src[DPAA2 on Github] URL: link:https://github.com/mcusim/freebsd-src[] + +Contact: Dmitry Salychev <dsl@FreeBSD.org> + +Contact: Bjoern A. Zeeb <bz@FreeBSD.org> + +==== What is DPAA2? + +DPAA2 is a hardware-level networking architecture found in some NXP SoCs which contains hardware blocks including Management Complex (MC, a command interface to manipulate DPAA2 objects), Wire Rate I/O processor (WRIOP, packets distribution, queuing, drop decisions), Queues and Buffers Manager (QBMan, Rx/Tx queues control, Rx buffer pools) and others. +The Management Complex runs NXP-supplied firmware which provides DPAA2 objects as an abstraction layer over those blocks to simplify access to the underlying hardware. + +==== Changes from the previous report + +* Isolation between DPAA2 channels link:https://cgit.freebsd.org/src/commit/?id=58983e4b0253ad38a3e1ef2166fedd3133fdb552[improved]. +* Panic under heavy network load link:https://github.com/mcusim/freebsd-src/issues/19[fixed]. +* FDT/ACPI MDIO support. +* NFS root mount link:https://github.com/mcusim/freebsd-src/issues/7[do not hang] on netboot over DPAA2 anymore. +* Drivers link:https://github.com/mcusim/freebsd-src/issues/2[started] to communicate with MC via their own command portals (DPMCP). +* link:https://github.com/mcusim/freebsd-src/issues?q=is%3Aissue+is%3Aclosed[List of all closed issues]. + +==== Work in Progress + +Work on link:https://cgit.freebsd.org/src/commit/?id=2a9021898c4ee2154787da862c238cfeccd655df[dev/sff] started to support SFF/SFP modules in order to test DPAA2 drivers on links above 1 Gbit/s. + +==== Plan + +* Heavy network load tests (2.5 Gbit/s, 10 Gbit/s) and bottlenecks mitigation. +* Cached memory-backed software portals. +* Driver resources de-allocation to unload dpaa2.ko properly. +* Further parts (DPSW, DCE, etc.) supported by the hardware. + +Sponsor: Traverse Technologies (providing Ten64 HW for testing) diff --git a/website/content/en/status/report-2023-07-2023-09/ec2.adoc b/website/content/en/status/report-2023-07-2023-09/ec2.adoc new file mode 100644 index 0000000000..4d8bd061f7 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/ec2.adoc @@ -0,0 +1,17 @@ +=== FreeBSD on EC2 + +Links: + +link:https://www.patreon.com/cperciva[FreeBSD/EC2 Patreon] URL: https://www.patreon.com/cperciva[] + +Contact: Colin Percival <cperciva@FreeBSD.org> + +FreeBSD is available on both x86 (Intel and AMD) and ARM64 (Graviton) EC2 instances. +Work continues to ensure that upcoming instance types will be supported. + +Weekly FreeBSD snapshots now include experimental ZFS-root AMIs for 14.0 and 15.0. +This change will be present in FreeBSD 14.0-RELEASE. + +Work is underway to start publishing experimental "cloud-init" AMIs. +This is expected to arrive in time for FreeBSD 14.0-RELEASE. + +This work is supported by Colin's FreeBSD/EC2 Patreon. diff --git a/website/content/en/status/report-2023-07-2023-09/expert-system.adoc b/website/content/en/status/report-2023-07-2023-09/expert-system.adoc new file mode 100644 index 0000000000..5108604d51 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/expert-system.adoc @@ -0,0 +1,18 @@ +=== FreeBSD Expert System + +Links: + +link:https://github.com/Wang-Yan-Hao/freebsd_expert_system[FreeBSD Expert System] URL: https://github.com/Wang-Yan-Hao/freebsd_expert_system[] + +Contact: Yan-Hao Wang <bses30074@gmail.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Machine Learning and Deep Learning technologies have become increasingly prevalent in today's world, much like the proliferation of ChatGPT. +We are working on developing a ChatGPT plugin that can access the latest FreeBSD data, transforming ChatGPT into a FreeBSD expert system. +We have already scripted data cleaning and built an embedded model to search for relevant information. + +Nevertheless, we require assistance for the following aspect of this project: + +* While I am not an expert in Machine Learning or Deep Learning, we encounter numerous challenges in these domains, such as the adequacy of data cleaning and uncertainties in the final plugin development process. +We would appreciate guidance in this regard. + +Sponsor: FreeBSD Foundation diff --git a/website/content/en/status/report-2023-07-2023-09/freebsd-foundation.adoc b/website/content/en/status/report-2023-07-2023-09/freebsd-foundation.adoc new file mode 100644 index 0000000000..c0afdc79b0 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/freebsd-foundation.adoc @@ -0,0 +1,164 @@ +=== 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 <deb@FreeBSDFoundation.org> + +The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. +Donations from individuals and corporations fund and manage software development projects, conferences, and developer summits. +We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and cluster administration efforts. +We publish marketing material to promote, educate, and advocate for FreeBSD, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. + +This quarter we helped FreeBSD celebrate its 30th anniversary! +This excitement has propelled us to accelerate our efforts to move FreeBSD forward in growth and innovation, which has focused us on identifying key areas we can invest our resources. +At our board meeting in September, we refined our goals to focus on increasing FreeBSD adoption and visibility, diversifying our funding stream, and investing in the community health and long-term stability of the Project. +We are in the process of identifying the key audiences and markets to target, while putting measurable outcomes to these goals. + +In this status report, you will read more about our work to help further FreeBSD's growth and innovation. +We will highlight all the technical work we are doing to improve FreeBSD, both by our internal staff of software developers, as well as external project funding efforts. +You will read about our advocacy work to promote FreeBSD to audiences outside of our community. +Finally, you will see the great efforts made to connect with current and potential commercial users. + +==== Fundraising + +We would like to express our sincere gratitude to all those who generously donated to support our work. +In addition to numerous individual contributions, we are especially grateful for the significant donations from NetApp, Netflix, and ARM. +In Q3 alone, we received $183,842, bringing our total for the year to $375,000. +This year our budget is around $2,230,000, which includes increased spending toward FreeBSD advocacy and software development. +More than half of our budget is allocated toward work directly related to improving FreeBSD and keeping it secure. +By providing a dedicated individual focused on partnerships, we can effectively emphasize the significance of investing in our efforts and underscore the long-term viability of FreeBSD to companies. +Your support is crucial to our mission, and we deeply appreciate your commitment to the FreeBSD community. +Please consider making a donation toward our 2023 fundraising campaign! link:https://freebsdfoundation.org/donate/[] +For our larger commercial donors, check out our updated link:https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/[FreeBSD Foundation Partnership Program]. + +==== Partnerships and Research + +For Partnerships and Research this quarter, progress was made in three key areas: + +First, the link:https://wiki.freebsd.org/EnterpriseWorkingGroup[Enterprise Working Group] started to gather steam with growth up to 58 participants and active projects in four work streams. +These are cloud native, Samba, bhyve manageability, and support for AI workloads. +There is interest in several additional areas and I expect that by the end of this year and Q1 of next year, we will see meaningful feature updates in multiple areas of focus. + +Second, we made good progress working with other open source community members and organizations, notably the link:https://opensource.org/[Open Source Initiative], to advance proposals and technology from the FreeBSD community. +Working with the Open Source Initiative’s link:https://opensource.org/programs/open-policy-alliance/[Open Policy Alliance], we are submitting a response to the US government's request for information on how the US government can support open source security and sustainability. +As part of this, Greg Wallace participated on a panel organized by the Open Policy Alliance at the recent All Things Open conference in Raleigh, North Carolina. +Greg Wallace has also been tracking how the US government incorporates CHERI into its policy recommendations for security by default, link:https://www.cisa.gov/sites/default/files/2023-10/Shifting-the-Balance-of-Cybersecurity-Risk-Principles-and-Approaches-for-Secure-by-Design-Software.pdf[such as this recent report from US and global government security agencies]. +On Page 28, CHERI is listed right after Rust as a key 'Secure by Design' tactic. + +Finally, we continue to strengthen partnerships with a growing number of companies using FreeBSD. +Several conferences aided these relationships, including EuroBSDCon, Open Source Summit, and All Things Open. +We have also developed a new program to support vendor/cloud users that work with the US government. +The program details will be announced at the FreeBSD Vendor Summit. + +==== Advocacy + +Much of our effort is dedicated to the FreeBSD Project advocacy. +This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. +The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. +Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. + +The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. +These events can be BSD-related, open source, or technology events geared towards underrepresented groups. +We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. +This all helps provide a healthy ecosystem. +We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. +We continue to add new events to our yearly roster. +This July, we held a workshop and staffed a table at FOSSY, a new open source conference in Portland, Oregon. +In addition to attending and planning conferences, we are continually working on new training initiatives and updating our selection of link:https://freebsdfoundation.org/freebsd-project/resources/[how-to guides] to facilitate getting more folks to try out FreeBSD. + +Check out some of our advocacy work: + +* Held a workshop and hosted a table at link:https://sfconservancy.org/fossy/[FOSSY], July 13-16, 2023, in Portland, Oregon. +* Friend-level sponsor of COSCUP, July 27-29, 2023, in New Taipei, Taiwan +* Presented at the EuroBSDCon FreeBSD Developer Summit, and sponsored and staffed a table at link:https://2023.eurobsdcon.org/[EuroBSDCon 2023], September 14-17, 2023 in Coimbra, Portugal +* Attended the link:https://events.linuxfoundation.org/open-source-summit-europe/[Open Source Summit, Europe], September 19-21, Bilbao, Spain +* Continued planning the link:https://freebsdfoundation.org/news-and-events/event-calendar/november-2023-freebsd-vendor-summit/[November 2023 FreeBSD Vendor Summit], taking place November 2-3, 2023, in San Jose, California +* Continued to administer our Google Summer of Code program +* Published the link:https://freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-july-2023/[July Newsletter] +* Additional Blog Posts +** link:https://freebsdfoundation.org/blog/advocating-at-events-may-2023-freebsd-dev-summit-and-bsdcan/[Advocating at Events: May 2023 FreeBSD Dev Summit and BSDCan] +** link:https://freebsdfoundation.org/blog/top-ten-reasons-to-upgrade-to-freebsd-13-2/[Top Ten Reasons to Upgrade to FreeBSD 13.2] +** link:https://freebsdfoundation.org/blog/july-2023-software-development-projects-update/[July 2023 Software Development Projects Update] +** https://freebsdfoundation.org/blog/freebsd-for-research-cheri-morello/[FreeBSD for Research: CHERI/Morello] +** Meet the FreeBSD Google Summer of Code Students +*** link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-soobin-rho/[Soobin Rho] +*** link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-raghav-sharma/[Raghav Sharma] +*** link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-sudhanshu-mohan-kashyap/[Sudhanshu Mohan Kashyap] +*** link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-aymeric-wibo/[Aymeric Wibo] +** link:https://freebsdfoundation.org/blog/meet-the-summer-2023-university-of-waterloo-co-op-student-naman-sood/[Meet The Summer 2023 University of Waterloo Co-Op Student: Naman Sood] +** link:https://freebsdfoundation.org/blog/meet-freebsd-foundation-2023-summer-intern-jake-freeland/[Meet FreeBSD Foundation 2023 Summer Intern: Jake Freeland] +* FreeBSD in the News +** link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-joins-osis-open-policy-alliance/[FreeBSD Foundation Joins OSI's Open Policy Alliance] +** link:https://freebsdfoundation.org/news-and-events/latest-news/hackernoon-5-reasons-we-use-open-source-freebsd-as-our-enterprise-os/[Hackernoon: 5 Reasons We Use Open Source FreeBSD as Our Enterprise OS] +** link:https://freebsdfoundation.org/news-and-events/latest-news/what-the-dev-podcast-the-evolution-of-the-freebsd-project/[What the Dev Podcast: The Evolution of the FreeBSD Project]. + +We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. +As we mentioned previously, the FreeBSD Journal is now a free publication. +Find out more and access the latest issues at link:https://www.freebsdfoundation.org/journal/[]. + +You can find out more about events we attended and upcoming events at link:https://freebsdfoundation.org/our-work/events/[]. + +==== OS Improvements + +During the third quarter of 2023, 282 src, 652 ports, and 24 doc tree commits identified The FreeBSD Foundation as a sponsor. +Some of this Foundation-sponsored work is described in separate report entries: + +* <<_enabling_snapshots_on_filesystems_using_journaled_soft_updates,Enabling Snapshots on Filesystems Using Journaled Soft Updates>> +* <<_login_classes_fixes_and_improvements,Login Classes Fixes and Improvements>> +* <<_openssl_3_in_baseimproved,OpenSSL 3 in base -- Improved>> +* <<_openstack_on_freebsd,OpenStack on FreeBSD>> +* <<_process_visibility_security_policies,Process Visibility Security Policies>> +* <<_simd_enhancements_for_amd64,SIMD enhancements for amd64>>. + +Members of the Technology Team attended EuroBSDCon 2023 in Coimbra, Portugal. +Li-Wen Hsu gave a tutorial to help newcomers contribute to FreeBSD. +Before the conference, the FreeBSD Developer Summit took place, where the team presented a link:https://wiki.freebsd.org/DevSummit/202309?action=AttachFile&do=view&target=Foundation_Technology_Team_Devsummit_Fall_2023.pdf[short update on their recent work]. + +Six summer internships or projects wrapped up. + +* link:https://freebsdfoundation.org/blog/meet-freebsd-foundation-2023-summer-intern-jake-freeland/[Jake Freeland] spent the summer working on a link:https://freebsdfoundation.org/project/capsicum-internship/[a Capsicum project] to trace violations, adapt various daemons such as man:syslogd[8], and write documentation. +* link:https://freebsdfoundation.org/blog/meet-the-summer-2023-university-of-waterloo-co-op-student-naman-sood/[Naman Sood] worked on link:https://freebsdfoundation.org/project/networking-summer-internship/[various tasks, mostly related to networking]. +* En-Wei Wu completed link:https://freebsdfoundation.org/project/wireless-internship/[another wireless internship] to improve and extend wtap, the net80211(4) Wi-Fi simulator. +* Yan-Hao Wang worked on a link:https://freebsdfoundation.org/project/documentation-and-testing-internship/[documentation and testing project] to, e.g., build an online man page editor and add test cases for some userspace tools. +* Christos Margiolis completed his link:https://freebsdfoundation.org/project/improving-the-kinst-dtrace-provider/[project to improve the kinst DTrace provider] by implementing inline function tracing and porting kinst to arm64 and riscv. +* In preparation for FreeBSD 14.0, Muhammad Moinur (Moin) Rahman committed over 700 fixes or workarounds for ports affected by recent OpenSSL and LLVM updates. + +For more information about current and past Foundation-contracted work, visit the link:https://freebsdfoundation.org/our-work/projects/[Foundation Projects page]. + +Here is a sampling of other Foundation-sponsored work completed over the quarter: + +* Improved riscv64 CPU identity and feature detection +* Rewrote man:intro[9] man page from scratch +* Performed code maintenance and fixed bugs in the man:hwpmc[4] module and the man:pmc[3] library and tools +* Committed various man:freebsd-update[8] fixes in preparation for FreeBSD 14.0 +* Committed many (37) updates and fixes to the LinuxKPI, iwlwifi, and net802.11 code +* Updated SSH first to OpenSSH 9.3p2, then 9.4p1 +* Patched ssh-keygen to generate Ed25519 keys when invoked without arguments +* Added a clean-room implementation of the Linux man:membarrier[2] system call +* Increased MAXCPU to 1024 on amd64 and arm64 +* Committed fixes for automatic Zenbleed misbehavior/data leaks prevention on affected machines (via chicken bit) +* Reviewed the use of scheduling priorities throughout the kernel for work in progress to harden the rtprio() system call and make it more useful in some cases. + +==== Supporting FreeBSD Infrastructure + +The Foundation provides hardware and two staff members to help support the FreeBSD cluster. +With your donations, the Foundation, in coordination with the Cluster Administration Team, purchased five new package builders, three new web servers, a new firewall/router, two package mirrors, and two new servers for continuous integration. +With the exception of one of the package mirrors, all the new hardware will be located on the east coast of the USA. + +==== Continuous Integration and Quality Assurance + +The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. +You can read more about CI work in a dedicated report entry. + +==== 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-2023-07-2023-09/freebsd-online-editor.adoc b/website/content/en/status/report-2023-07-2023-09/freebsd-online-editor.adoc new file mode 100644 index 0000000000..e733ad42e2 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/freebsd-online-editor.adoc @@ -0,0 +1,27 @@ +=== FreeBSD Online Editor and Man Page Editor + +Links: + +link:https://github.com/Wang-Yan-Hao/FreeBSD-Online-Document-Editor[FreeBSD Online Document Editor] URL: link:https://github.com/Wang-Yan-Hao/FreeBSD-Online-Document-Editor[] + +link:https://github.com/Wang-Yan-Hao/man_page_editor[FreeBSD Online Man Page Editor] URL: link:https://github.com/Wang-Yan-Hao/man_page_editor[] + +Contact: Yan-Hao Wang <bses30074@gmail.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Currently, our document translation process involves using Weblate and direct editing of the link:https://cgit.freebsd.org/doc/[doc] repository. +We acknowledge that this process can be somewhat cumbersome, so we are striving to offer a more convenient alternative, similar to what the wiki community does. +Introducing the Online Document Editor and Man Page Editor, a user-friendly, WYSIWYG static site designed for translating documents and man pages. +Our goal is to consolidate all translation functions within a single platform, making the translation process as straightforward as possible. + +However, we still require assistance with these two projects, as follows: + +1. The Document editor and Man page editor were developed using simple JavaScript. +We are seeking a web developer to assess the code's efficiency since I (Yan-Hao Wang) am not well-versed in front-end development. + +2. We are also seeking a cybersecurity developer to assist us in identifying and addressing security issues within these two projects. +This is crucial to ensure the secure hosting of these projects and mitigate any potential vulnerabilities. + +3. As there is currently no existing JavaScript library to render mandoc, I had to create my own. +However, there are still some concealed errors during the editing process. +We are in need of a JavaScript developer to help rectify these rendering issues. + +Sponsor: FreeBSD Foundation diff --git a/website/content/en/status/report-2023-07-2023-09/gcc.adoc b/website/content/en/status/report-2023-07-2023-09/gcc.adoc new file mode 100644 index 0000000000..31bbde0246 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/gcc.adoc @@ -0,0 +1,25 @@ +=== GCC on FreeBSD + +Links: + +link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] + +link:https://gcc.gnu.org/gcc-10/[GCC 10 release series] URL: link:https://gcc.gnu.org/gcc-10/[] + +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/[] + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + +The process to update GCC default version to GCC 13 has started with an link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273397[exp-run]. Thanks to mailto:antoine@FreeBSD.org[Antoine Brodin] who ran the exp-run and to all other developers and ports maintainers involved. + +The same exp-run contains additional patches as anticipated in last quarterly status report. +In particular, it contains patches to update + +* package:lang/gcc11[] to version 11.4.0; +* package:lang/gcc12[] to version 12.3.0; +* package:lang/gcc13[] to version 13.2.0. + +The reader might remember that I had planned to update GCC default version to GCC 13 as soon as 13.1.0 was out, but as it can be noted the GCC developers were faster to release 13.2.0 than I was working on the GCC ports. + +Most of the bugs reported in the exp-run are due to the same error: `error: expected identifier before '__is_convertible'`. +It seems that the issue is an incompatibility between FreeBSD 12's libcxx and GCC 13 headers. +Please check the link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273397[discussion in the exp-run] for more information and to provide your feedback. diff --git a/website/content/en/status/report-2023-07-2023-09/gitlab.adoc b/website/content/en/status/report-2023-07-2023-09/gitlab.adoc new file mode 100644 index 0000000000..7b2d0e6d83 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/gitlab.adoc @@ -0,0 +1,19 @@ +=== GitLab 16.3 Available + +Link: + +link:https://about.gitlab.com/releases/2023/08/22/gitlab-16-3-released/[Gitlab 16.3 New Features] URL: link:https://about.gitlab.com/releases/2023/08/22/gitlab-16-3-released/[] + +Contact: Matthias Fechner <mfechner@FreeBSD.org> + +GitLab is a DevOps platform. +It brings velocity with confidence, security without sacrifice, and visibility into DevOps success. + +Version 16.3 is now available on FreeBSD: please check the package:www/gitlab-ce[] port. +The upgrade is very important as version 16.3 will be required for all further upgrades. +Upgrade to 16.4 is only possible from GitLab 16.3. + +Documentation for installation can be found at link:https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/install/16.3-freebsd.md?ref_type=heads[]. +Documentation for upgrading is available at https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.1-16.3-freebsd.md?ref_type=heads[]. + +I will wait for the upgrade to 16.4 (which will be released around 20.9. or 22.9., not sure) until ports _quarterly_ branch 2023Q4 is created, to avoid breaking systems that do not use the main branch (_latest_). +GitLab users should always choose the main branch, as described in the installation manual. diff --git a/website/content/en/status/report-2023-07-2023-09/intro.adoc b/website/content/en/status/report-2023-07-2023-09/intro.adoc new file mode 100644 index 0000000000..567a1428fc --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/intro.adoc @@ -0,0 +1,9 @@ +Here is the third 2023 status report, with 32 entries. + +This is the summer quarter and thus it includes many interesting news from Google Summer of Code. +Of course, we also have our usual team reports and many projects share with us their latest news. +Much important work has been done for the first release of FreeBSD 14. + +Have a nice read. + +Lorenzo Salvadore, on behalf of the Status Team. diff --git a/website/content/en/status/report-2023-07-2023-09/kde.adoc b/website/content/en/status/report-2023-07-2023-09/kde.adoc new file mode 100644 index 0000000000..c5b242b096 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/kde.adoc @@ -0,0 +1,60 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] + +link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. +The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphical desktop workstation. +The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack. + +==== Infrastructure + +Qt5 is now on long-term support and updates only rarely. +There was an update to 5.15.10 in this quarter. +Qt6 is now updated with the regular upstream releases, with the 6.5.2 release landing at the end of July and 6.5.3 following later. + +CMake saw no updates this quarter, so we are now lagging by at least one minor release. +The changelog for the latest releases does not have much for FreeBSD, so there is no special reason to upgrade. + +package:sysutils/polkit[] and package:sysutils/consolekit2[] were both updated, bringing improved security policy and console handling to the FreeBSD desktop. +package:x11/sddm[] was updated to provide a better graphical login manager. + +package:multimedia/pipewire[] was updated to version 0.3.81. +This provides multimedia support for desktops such as KDE and GNOME. + + +==== KDE Stack + +KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. +These (large) updates land shortly after their upstream release and are not listed separately. + +* KDE Frameworks reached version 5.110. The KDE Frameworks 5 series is winding down, although it will be six months or so before it enters long-term support upstream. +* KDE Plasma Desktop was updated to version 5.27.8. Just like frameworks, work on KDE Plasma 5 is winding down upstream in favor of KDE Plasma 6. +* KDE Gear updated to 23.08.1. + +==== Related Ports + +The KDE ecosystem includes a wide range of ports -- most maintained by kde@, all building on a shared base of Qt and KDE Frameworks. +The kde@ team updates them all as needed. +This quarter, for instance, tcberner@ and arrowd@ updated or fixed (much more than) this selection of ports: + +* package:astro/merkaartor[] +* package:devel/massif-visualizer[] +* package:finance/alkimia[] +* package:irc/quassel[] +* package:net-im/kaidan[] +* package:sysutils/bsdisks[] +* package:sysutils/k3b[] + +Thanks to jhale@, package:devel/qtcreator[] was updated to 11.0.3, providing another featureful integrated development environment for creating Qt and KDE applications. + +==== Deprecations + +Web browsers are huge, and have a considerable security surface. +The venerable package:www/qt5-webkit[] WebKit port has been slated for removal and consumers have been moved to WebEngine. +The fork of WebKit that we relied on is no longer actively maintained. diff --git a/website/content/en/status/report-2023-07-2023-09/linuxulator.adoc b/website/content/en/status/report-2023-07-2023-09/linuxulator.adoc new file mode 100644 index 0000000000..080e37b4a7 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/linuxulator.adoc @@ -0,0 +1,15 @@ +=== 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 <dchagin@FreeBSD.org> + +The goal of this project is to improve FreeBSD's ability to execute unmodified man:linux[4] binaries. + +As of gitref:22dca7acf775[repository=src], xattr system calls are implemented. +That makes it possible to use Linux rsync. + +As of gitref:bbe017e0415a[repository=src], ioprio system calls are implemented. +That makes it possible to debootstrap Ubuntu 23.04. diff --git a/website/content/en/status/report-2023-07-2023-09/lldb-kmod.adoc b/website/content/en/status/report-2023-07-2023-09/lldb-kmod.adoc new file mode 100644 index 0000000000..7c4b8a9d71 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/lldb-kmod.adoc @@ -0,0 +1,19 @@ +=== LLDB Kernel Module Improvement + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement[GSoC Wiki Project] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/LLDBKernelModuleImprovement[] + +link:https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[Project Codebase] URL: link:https://github.com/aokblast/freebsd-src/tree/lldb_dynamicloader_freebsd_kernel[] + +link:https://github.com/llvm/llvm-project/pull/67106[LLVM PullRequest] URL: link:https://github.com/llvm/llvm-project/pull/67106[] + +Contact: Sheng-Yi Hong <aokblast@FreeBSD.org> + +The LLDB Kernel Module Improvement Project described in the previous quarter report implements DynamicLoader Plugin for FreeBSD Kernel on LLDB. + +All of the work is done -- that is, this plugin can correctly load all kernel modules and their debug files extracted from kernel coredump. + +This plugin has been tested on both x86-64 for relocatable type kernel module and arm64(EC2) for shared library type kernel module. +Both of these platforms show this plugin works well. + +Currently, this plugin prepares to be landed to LLVM codebase in https://github.com/llvm/llvm-project/pull/67106[LLVM PullRequest] + +Sponsor: The Google Summer of Code '23 program diff --git a/website/content/en/status/report-2023-07-2023-09/login_classes.adoc b/website/content/en/status/report-2023-07-2023-09/login_classes.adoc new file mode 100644 index 0000000000..c68fbbe13c --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/login_classes.adoc @@ -0,0 +1,37 @@ +=== Login Classes Fixes and Improvements + +Links: + +link:https://reviews.freebsd.org/D40339[Start of the reviews stack] URL: link:https://reviews.freebsd.org/D40339[] + +Contact: Olivier Certner <olce.freebsd.statusreports@certner.fr> + +==== Context + +Login classes are a mechanism mainly used to set various process properties and attributes at login, depending on the user logging in and the login class he is a member of. +A login class typically specifies resource limits, environment variables and process properties such as scheduling priority and umask. +See man:login.conf[5] for more information. + +==== Changes + +The `priority` and `umask` capabilities now accept the `inherit` special value to explicitly request property inheritance from the login process. +This is useful, e.g., when temporarily logging in as another user from a process with a non-default priority to ensure that processes launched by this user still have the same priority level. + +Users can now override the global setting for the `priority` capability (in [.filename]#/etc/login.conf#) in their local configuration file ([.filename]#~/.login_conf#). +Note however that they cannot increase their priority if they are not privileged, and that using `inherit` in this context makes no sense, since the global setting is always applied first. + +Fixes: + +- Fix a bug where, when the `priority` capability specifies a realtime priority, the final priority used was off-by-one (and the numerically highest priority in the real time class (31) could never be set). +- Security: Prevent a setuid/setgid process from applying directives from some user's [.filename]#~/.login_conf# (directives there that cannot be applied because of a lack of privileges could suddenly become applicable in such a process). + +We have also updated the relevant manual pages to reflect the new functionality, and improved the description of the `priority` and `umask` capabilities in man:login.conf[5]. + +==== Status + +Some of the patches in the series have been reviewed thanks to mailto:kib@FreeBSD.org[Konstantin Belousov] and mailto:imp@FreeBSD.org[Warner Losh]. +Other patches are waiting for reviews (and reviewers, volunteers welcome!), which are not expected to be labored. + +We plan to improve consistency by deprecating the priority reset to 0 when no value for the capability `priority` is explicitly specified, which has been the case for `umask` for 15+ years. + +Sponsor: Kumacom SAS (for development work) + +Sponsor: The FreeBSD Foundation (for some reviews) diff --git a/website/content/en/status/report-2023-07-2023-09/mfsbsd.adoc b/website/content/en/status/report-2023-07-2023-09/mfsbsd.adoc new file mode 100644 index 0000000000..7dca0c593e --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/mfsbsd.adoc @@ -0,0 +1,33 @@ +=== Integrate mfsBSD into the Release Building Tools + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools[Wiki Article] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/IntegrateMfsBSDIntoTheReleaseBuildingTools[] + +link:https://reviews.freebsd.org/D41705[Code Review on Phabricator] URL: link:https://reviews.freebsd.org/D41705[] + +link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-soobin-rho/[FreeBSD Foundation Blog Post] URL: link:https://freebsdfoundation.org/blog/meet-the-2023-freebsd-google-summer-of-code-students-soobin-rho/[] + +Contact: Soobin Rho <soobinrho@FreeBSD.org> + +==== What is mfsBSD? + +"mfsBSD is a toolset to create small-sized but full-featured mfsroot based distributions of FreeBSD that store all files in memory (MFS) [Memory File System] and load from hard drive, USB storage device, or optical medium. +It can be used for a variety of purposes, including diskless systems, recovery partitions and remotely overwriting other operating systems." + +mailto:mm@FreeBSD.org[Martin Matuška] is the creator of mfsBSD. +He is also author of the original (2009) link:https://people.freebsd.org/~mm/mfsbsd/mfsbsd.pdf[mfsBSD white paper], from which the excerpt above is taken. +Upstream mfsBSD is maintained in the link:https://github.com/mmatuska/mfsbsd[repository on GitHub]. + +==== Purpose of this Project + +This project integrates mfsBSD into the FreeBSD release tool set, creating an additional target of mfsBSD images ([.filename]#.img# and [.filename]#.iso# files) in [.filename]#/usr/src/release/Makefile#. +Prior to integration, mfsBSD only existed outside the FreeBSD release tool chain, and only -RELEASE versions were produced. + +With this project, mfsBSD images will be available at the official FreeBSD release page. +You will also be able to build mfsBSD yourself by invoking `cd /usr/src/release && make release WITH_MFSBSD=1`, which will then create [.filename]#mfsbsd-se.img# and [.filename]#mfsbsd-se.iso# at [.filename]#/usr/obj/usr/src/${ARCH}/release/#. + +==== Changes from last quarter + +The code is ready, and is currently under review. +If you would like to get involved with the review process, please feel free to do so! +Here is link:https://reviews.freebsd.org/D41705[my revision]. + +Sponsor: Google, Inc. (GSoC 2023) diff --git a/website/content/en/status/report-2023-07-2023-09/office.adoc b/website/content/en/status/report-2023-07-2023-09/office.adoc new file mode 100644 index 0000000000..b6019f48e1 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/office.adoc @@ -0,0 +1,26 @@ +=== FreeBSD Office Team + +Links: + +link:https://wiki.freebsd.org/Office[The FreeBSD Office project] URL: link:https://wiki.freebsd.org/Office[] + +link:https://lists.freebsd.org/subscription/freebsd-office[The FreeBSD Office mailing list] URL: link:https://lists.freebsd.org/subscription/freebsd-office[] + +Contact: FreeBSD Office team ML <office@FreeBSD.org> + +Contact: Dima Panov <fluffy@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +The FreeBSD Office team works on a number of office-related software suites and tools such as OpenOffice and LibreOffice. + +Work during this quarter was focused on providing the latest stable release of LibreOffice suite and companion apps to all FreeBSD users. + +During the 2023Q3 period we pushed maintenance patches for the LibreOffice port and brought the latest, 7.6.2, release and all companion libraries such as MDDS, libIxion and more to the ports tree. +All prerelease development of LibreOffice ports is carried out in the in link:https://github.com/freebsd/freebsd-ports-libreoffice[LibreOffice WIP repo]. + +Together with LibreOffice, we also updated Boost to the latest, 1.83 release. +Everyone interested in Boost porting can submit patches to the link:https://github.com/fluffykhv/freebsd-ports-boost[Boost WIP repository]. + +We are looking for people to help with the open tasks: + +* The link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=office%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=substring&list_id=650685&order=Bug+Number&query_format=advanced[open bugs list] contains all filed issues which need some attention +* Upstream link:https://cgit.freebsd.org/ports/tree/editors/libreoffice/files[local patches in ports] + +Patches, comments and objections are always welcome in the mailing list and Bugzilla. diff --git a/website/content/en/status/report-2023-07-2023-09/openssl3.adoc b/website/content/en/status/report-2023-07-2023-09/openssl3.adoc new file mode 100644 index 0000000000..b5e8b44bee --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/openssl3.adoc @@ -0,0 +1,18 @@ +=== OpenSSL 3 in base -- Improved + +Links: + +link:https://www.openssl.org/source/[OpenSSL Downloads] URL: link:https://www.openssl.org/source/[] + +Contact: Pierre Pronchery <pierre@freebsdfoundation.org> + +This is a follow-up to the link:https://www.freebsd.org/status/report-2023-04-2023-06/[previous quarterly report] on the link:https://www.freebsd.org/status/report-2023-04-2023-06/#_openssl_3_in_base[integration of OpenSSL 3 into the base system]. + +The most obvious updates since the previous report are certainly the 3.0.10 and then 3.0.11 releases, fixing CVE issues with low to medium severity (link:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2975[CVE-2023-2975], link:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3446[CVE-2023-3446], link:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3817[CVE-2023-3817], link:https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-4807[CVE-2023-4807]). + +However these are not the only changes, and this quarter some issues specific to the integration were fixed, most of which were found while building ports with OpenSSL 3 in the base system. + +Fixes included: + +* Linking the engines and the legacy provider with the libcrypto.so shared object, for proper visibility of symbols, and for which a link:https://cgit.freebsd.org/src/commit/Makefile.inc1?id=1a18383a52bc373e316d224cef1298debf6f7e25[hack was required in the build system]. +* Correcting the list of source files for the FIPS provider. +* Ensuring backward compatibility for the deprecated 0.9.8 API, which was notably helpful for the PAM authentication module from package:security/pam_ssh_agent_auth[], based on OpenSSH's man:ssh-agent[1] authentication mechanism. diff --git a/website/content/en/status/report-2023-07-2023-09/openstack.adoc b/website/content/en/status/report-2023-07-2023-09/openstack.adoc new file mode 100644 index 0000000000..465f875d76 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/openstack.adoc @@ -0,0 +1,36 @@ +=== OpenStack on FreeBSD + +Links: + +link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] + +link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[] + +Contact: Chih-Hsin Chang <starbops@hey.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +OpenStack, an open-source cloud operating system, has been a valuable resource for deploying various resource types on cloud platforms. +However, the challenge has been running OpenStack's control plane on FreeBSD hosts. +Our project's mission is to enable FreeBSD to function seamlessly as an OpenStack host. + +Throughout this quarter, we focused on the last bit of the entire proof of concept (POC), the VM console integration. +The goal is to let users get serial consoles via the OpenStack client to access the VM instances running on the FreeBSD-based OpenStack cluster. +This is also important because right now we do not have a port for the managed DHCP service in Neutron. +Users need to manually configure the correct IP addresses for the VM instances to have network connectivity. +However, man:bhyve[8] does not natively expose serial consoles, so we need to instead export the man:nmdm[4] device over the network. +This is done by a custom proxy called link:https://github.com/openstack-on-freebsd/socat-manager/blob/main/server.py[`socat-manager`], and yes, we leverage man:socat[1] to listen on specific ports allocated by OpenStack `nova-compute` to be integrated into their workflow. +With the aid of another critical part, the link:https://github.com/openstack-on-freebsd/socat-manager/tree/main/hooks[custom Libvirt hook for bhyve], we can connect the two endpoints and make the consoles accessible to the users. +During development of the hook script, we found that the hook interface provided by Libvirt specifically for bhyve was link:https://gitlab.com/libvirt/libvirt/-/issues/528[not well implemented]. +Fortunately, the Libvirt developer link:https://gitlab.com/libvirt/libvirt/-/commit/ad8c4d9d6d09d51a9530ed84fcd2220713aab928[fixed the issue] promptly, and we plan to refine our hook script when the fix is released in the future. + +We also addressed the nested bhyve issue (running bhyve VMs on top of Linux KVM) in our development environment mentioned in link:https://www.freebsd.org/status/report-2023-04-2023-06/#_openstack_on_freebsd[the last quarterly report]. +It is caused by the APIC emulation of the two VT-x features: `VID` and `PostIntr`. + +Our host's CPUs have these two features so we need to disable them at the L1 guest, which acts as a bhyve host, in [.filename]#/boot/loader.conf# to make L2 guests not hanging. +It is crucial for us to be able to work on the project in a fully virtualized environment due to the lack of physical resources. +This could be equally important for people interested in the project, lowering the bar for them to try out or validate the entire POC on their environment without too demanding setup requirements. + +Looking ahead to Q4, our focus is wrapping up the POC with revised documentation and porting to FreeBSD 14.0-RELEASE. +Dependencies that lack the corresponding FreeBSD packages will be ported one by one. +We also aim to rebase our work with OpenStack link:https://releases.openstack.org/antelope/index.html[2023.1 Antelope]. +We invite those interested to explore our documentation and contribute to this project's success. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-07-2023-09/pantheon.adoc b/website/content/en/status/report-2023-07-2023-09/pantheon.adoc new file mode 100644 index 0000000000..6a66de6a03 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/pantheon.adoc @@ -0,0 +1,37 @@ +=== Pantheon desktop on FreeBSD + +Links: + +link:https://elementary.io/[elementary OS] URL: link:https://elementary.io/[] + +link:https://codeberg.org/olivierd/freebsd-ports-elementary[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-elementary[] + +Contact: Olivier Duchateau <duchateau.olivier@gmail.com> + +The Pantheon desktop environment is designed for elementary OS. +It builds on GNOME technologies (such as Mutter, GTK 3 and 4) and it is written in Vala. +The goal is to have a complete desktop environment for end users. + +*13.2-RELEASE or higher is required*, because several core components depend on package:deskutils/xdg-desktop-portal[]. + +The repository contains a file called [.filename]#elementary.mk# for the [.filename]#Mk/Uses# framework, official applications, and curated ports which depend on package:x11-toolkits/granite7[]. + +I have submitted several patches in order to keep these ports up-to-date: + +* package:deskutils/iconbrowser[] +* package:multimedia/elementary-videos[] +* package:x11-themes/gnome-icons-elementary[] +* package:editors/elementary-code[] + +The link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&query_format=advanced&short_desc=elementary-calendar%20elementary-terminal%20granite7&short_desc_type=anywordssubstr[bug reports] for updating the following ports are still open on bugzilla: + +* package:x11-toolkits/granite7[]: Update to 7.3.0 +* package:deskutils/elementary-calendar[]: Update to 7.0.0 +* package:x11/elementary-terminal[]: Update to 6.1.2 + +In the same time, I have also worked on updating the GNOME stack (especially WebKitGTK, libwnck, Mutter, Vala). +I noticed several regressions particularly with package:x11/plank[] (it is related to monitoring open applications). + +Three new applications have been added to the development repository: + +* deskutils/atlas, a map viewer +* deskutils/nimbus, a weather applet +* audio/leopod, podcasts client diff --git a/website/content/en/status/report-2023-07-2023-09/portmgr.adoc b/website/content/en/status/report-2023-07-2023-09/portmgr.adoc new file mode 100644 index 0000000000..1e15ed00e3 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/portmgr.adoc @@ -0,0 +1,45 @@ +=== 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 <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. +Below is what happened in the last quarter. + +* According to INDEX, there are currently 34,600 ports in the Ports Collection. +There are currently 3,000 open ports PRs of which some 730 are unassigned. +The last quarter saw 11,454 commits by 130 committers on the main branch and 828 commits by 37 committers on the 2023Q3 branch. +Compared to last quarter, this means a slight decrease in the number of unassigned PRs, a 10% increase in the number of commits on the main branch but also less backports to the quarterly branch. +The number of ports also grew a bit. + +During Q3 we welcomed Joel Bodenmann (jbo@) as a new ports committer, granted a ports commit bit to mizhka@ who was already a src committer, and took the commit bits of knu@ and uqs@ in for safe-keeping after a year of inactivity. + +Portgmr discussed and worked on the following things during Q3: + +* Some progress has been made on sub-packages and a lightning talk was given by pizzamig@ at EuroBSDCon +* Overhauling some parts of the ports tree (LIB_DEPENDS, PREFIX, MANPREFIX, MANPATH) + +Support for FreeBSD 13.1 was removed from the ports tree as it reached its end-of-life on August 1st. + +The following happened on the infrastructure side: + +* USES for ebur128 and guile were added +* Default versions for Mono, Perl, and PostgreSQL were updated to respectively 5.20, 5.34, and 15 +* Default versions for ebur128, guile, and pycryptography were added at respectively "rust", 2.2, and "rust" +* Updates to major ports that happened were: + +** pkg to 1.20.7 +** chromium to 117.0.5938.132 +** Firefox to 118.0.1 +** KDE to 5.27.8 +** Rust to 1.72.0 +** Wine to 8.0.2 + +During the last quarter, pgkmgr@ ran 18 exp-runs to test various ports upgrades, updates to default versions of ports, and changes to pycryptography. diff --git a/website/content/en/status/report-2023-07-2023-09/portoptscli.adoc b/website/content/en/status/report-2023-07-2023-09/portoptscli.adoc new file mode 100644 index 0000000000..9f5e28fd06 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/portoptscli.adoc @@ -0,0 +1,22 @@ +=== PortOptsCLI -- Ports Collection Accessibility + +Link: + +link:https://gitlab.com/alfix/portoptscli[Project repository] URL: link:https://gitlab.com/alfix/portoptscli[] + +Contact: Alfonso Sabato Siciliano <asiciliano@FreeBSD.org> + +Contact: FreeBSD Accessibility mailing list <freebsd-accessibility@FreeBSD.org> + +FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications. +It is possible to configure a port before the building and installation. +The command `make config` uses package:ports-mgmt/dialog4ports[] and package:ports-mgmt/portconfig[] to set up a port interactively via a text user interface (TUI). + +Unfortunately, screen readers perform poorly with a TUI; it is a well-known accessibility problem. +FreeBSD provides tens of thousands of ports; port configuration is a key feature, but it is inaccessible to users with vision impairment. + +PortOptsCLI (Port Options CLI) is a new utility for setting port options via a command line interface. +Properly, PortOptsCLI provides commands to navigate configuration dialogues (checklists and/or radio buttons) and set up their items interactively. +It is also suitable for a speech synthesizer; currently it is tested with package:accessibility/orca[]. +PortOptsCLI can be installed via the package:ports-mgmt/portoptscli[] port or package. + +Tips and new ideas are welcome. +If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place. diff --git a/website/content/en/status/report-2023-07-2023-09/pot.adoc b/website/content/en/status/report-2023-07-2023-09/pot.adoc new file mode 100644 index 0000000000..66bece95ab --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/pot.adoc @@ -0,0 +1,27 @@ +=== 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) <pizzamig@FreeBSD.org> + +Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org> + +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]. + +During this quarter, link:https://github.com/bsdpot/pot/pull/274[Pot 0.15.6] was finished, adding custom man:pf[4] rule configuration hooks. + +Additionally, link:https://github.com/bsdpot/nomad-pot-driver/releases/tag/v0.9.1[Nomad Pot Driver 0.9.1] that allows setting Pot attributes in Nomad job descriptions was released. + +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. + +Quite a few new container images were made available, e.g. a link:https://github.com/bsdpot/potluck/tree/master/caddy-s3-nomad[Caddy S3 proxy], a link:https://github.com/bsdpot/potluck/tree/master/mastodon-s3[Mastodon instance], and a link:https://github.com/bsdpot/potluck/tree/master/redis-single[Redis container]. +In total there are now 50 containers available that can either be downloaded as ready-made images at link:https://potluck.honeyguide.net/[the Potluck image registry], if you trust our build process, or that you can build yourself from the Pot flavour files stored in the link:https://github.com/bsdpot/potluck[Potluck GitHub repository]. + +The July/August 2023 edition of the FreeBSD Journal contains Luca's link:https://freebsdfoundation.org/wp-content/uploads/2023/08/Pizzamiglio.pdf[Jail Orchestration with pot and nomad] article, explaining how to use Pot and Potluck together with Nomad to orchestrate containers on multiple hosts. + +Last but not least, a patch (gitref:90b1184d93c8[repository=ports]) added build cluster support to the package:devel/sccache[] port. + +As always, feedback and patches are welcome. + +Sponsors: Nikulipe UAB, Honeyguide Group diff --git a/website/content/en/status/report-2023-07-2023-09/process_visibility.adoc b/website/content/en/status/report-2023-07-2023-09/process_visibility.adoc new file mode 100644 index 0000000000..06cf80b33f --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/process_visibility.adoc @@ -0,0 +1,49 @@ +=== Process Visibility Security Policies + +Links: + +link:https://reviews.freebsd.org/D40626[Start of the reviews stack] URL: link:https://reviews.freebsd.org/D40626[] + +Contact: Olivier Certner <olce.freebsd.statusreports@certner.fr> + +==== Context + +FreeBSD implements three built-in security policies that limit which processes are visible to particular users, with the goal of preventing information leaks and unwanted interactions. + +The first one can prevent an unprivileged user from seeing or interacting with processes that do not have the user's UID as their real UID. +It can be activated by setting the sysctl `security.bsd.see_other_uids` to 0 (default is 1). + +The second one can prevent an unprivileged user from seeing or interacting with processes whose credentials do not have any group that the user is a member of. +It can be activated by setting the sysctl `security.bsd.see_other_gids` to 0 (default is 1). + +The third one can prevent an unprivileged user's process from seeing or interacting with processes that are in a jail that is a strict sub-jail of the former. +The jail subsystem already prevents such a process to see processes in jails that are not descendant of its own (see man:jail[8] and in particular the section "Hierarchical Jails"). +One possible use of this policy is, in conjunction with the first one above, to hide processes in sub-jails that have the same real UID as some user in an ancestor jail, because users having identical UIDs in these different jails are logically considered as different users. +It can be activated by setting the sysctl `security.bsd.see_jail_proc` to 0 (default is 1). + +After a review of these policies' code and real world testing, we noticed a number of problems and limitations which prompted us to work on this topic. + +==== Changes + +The policy controlled by the `security.bsd.see_jail_proc` sysctl has received the following fixes and improvements: + +- Harden the `security.bsd.see_jail_proc` policy by preventing unauthorized users from attempting to kill, change priority of or debug processes with same (real) UID in a sub-jail at random, which, provided the PID of such a process is guessed correctly, would succeed even if these processes are not visible to them. +- Make this policy overridable by MAC policies, as are the others. + +The policy controlled by `security.bsd.see_other_gids` was fixed to consider the real group of a process instead of its effective group when determining whether the user trying to access the process is a member of one of the process' groups. +The rationale is that some user should continue to see processes it has launched even when they acquire further privileges by virtue of the setgid bit. +Conversely, they should not see processes launched by a privileged user that temporarily enters the user's primary group. +This new behavior is consistent with what `security.bsd.see_other_uids` has always been doing for user IDs (i.e., considering some process' real user ID and not the effective ID). + +We have updated manual pages related to these security policies, including man:security[7], man:sysctl[8], and man:ptrace[2]. +Several manual pages of internal functions either implementing or leveraging these policies have also been revamped. + +==== Status + +Thanks to the help of mailto:mhorne@FreeBSD.org[Mitchell Horne], mailto:pauamma@gundo.com[Pau Amma], mailto:bcr@FreeBSD.org[Benedict Reuschling] and mailto:emaste@FreeBSD.org[Ed Maste], most of the submitted changes have been reviewed and approved, so they should reach the tree soon. +The patch series starts with https://reviews.freebsd.org/D40626[review D40626]. +From there, click on the "Stack" tab to see the full list of reviews implementing the changes. + +As a later step, we are considering turning the `security.bsd.see_jail_proc` policy on by default (i.e., the default value of the sysctl would become 0) unless there are objections. + +Sponsor: Kumacom SAS (for development work) + +Sponsor: The FreeBSD Foundation (for most of the reviews) diff --git a/website/content/en/status/report-2023-07-2023-09/releng.adoc b/website/content/en/status/report-2023-07-2023-09/releng.adoc new file mode 100644 index 0000000000..c1c52d1bee --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/releng.adoc @@ -0,0 +1,19 @@ +=== FreeBSD Release Engineering Team + +Links: + +link:https://www.freebsd.org/releases/14.0R/schedule/[FreeBSD 14.0-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.0R/schedule/[] + +link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] + +link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[] + +Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org> + +The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. + +During the third quarter of the year, the FreeBSD Release Engineering Team started work on the upcoming 14.0-RELEASE cycle. +As of this writing, BETA3 had been released, with BETA4 to follow shortly after. + +The Release Engineering Team continued providing weekly development snapshot builds for the *main* and *stable/13* branches. + +Sponsor: Tarsnap + +Sponsor: https://www.gofundme.com/f/gjbbsd/ + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-07-2023-09/simd.adoc b/website/content/en/status/report-2023-07-2023-09/simd.adoc new file mode 100644 index 0000000000..f07bee3912 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/simd.adoc @@ -0,0 +1,28 @@ +=== SIMD enhancements for amd64 + +Links: + +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:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[simd(7)] URL: link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[] + +Contact: Robert Clausecker <fuz@FreeBSD.org> + +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, + * either a *baseline* implementation using SSE and SSE2, or 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 `ARCHLEVEL` environment variable. + +While the current project only concerns amd64, the work may be expanded to other architectures like arm64 in the future. + +During the last few months, significant progress has been made on this project. +SIMD-enhanced versions of man:bcmp[3], man:index[3], man:memchr[3], man:memcmp[3], man:stpcpy[3], man:strchr[3], man:strchrnul[3], man:strcpy[3], man:strcspn[3], man:strlen[3], man:strnlen[3], and man:strspn[3] have landed. +Functions man:memcpy[3], man:memmove[3], man:strcmp[3], man:timingsafe_bcmp[3] (see link:https://reviews.freebsd.org/D41673[D41673]), and man:timingsafe_memcmp[3] (see link:https://reviews.freebsd.org/D41696[D41696]) are work in progress. +Unfortunately, the work has not made the cut for FreeBSD 14.0, but it is slated to be part of FreeBSD 14.1. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-07-2023-09/squashfs.adoc b/website/content/en/status/report-2023-07-2023-09/squashfs.adoc new file mode 100644 index 0000000000..70fd1484a4 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/squashfs.adoc @@ -0,0 +1,29 @@ +=== SquashFS driver for FreeBSD kernel + +Links: + +link:https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel[Wiki page] URL: link:https://wiki.freebsd.org/SummerOfCode2023Projects/PortSquashFuseToTheFreeBSDKernel[] + +link:https://github.com/Mashijams/freebsd-src/tree/gsoc/testing[Source code] URL: link:https://github.com/Mashijams/freebsd-src/tree/gsoc/testing[] + +Contact: Raghav Sharma <raghav@FreeBSD.org> + +This quarter we finished SquashFS driver work for the kernel. +We now can mount SquashFS archives on FreeBSD 13.2-RELEASE or greater, and perform all basic read-only filesystem operations. + +Code work includes: + +* Implementing vop_lookup() and vop_readdir() hooks for directory read support. +* Implementing vop_read() and vop_strategy() hooks for files read support. +* Implementing vop_readlink() hook for symlinks read support. + +We also implemented extended attributes interface functions for SquashFS. +All that remains is to implement their kernel interface hooks. + +There were a lot of bug fixes as well. +One major issue was to find out why we can not list the first entry of the root directory, it transpires that SquashFS could have `inode_number` as zero, which the kernel, for some reason, skips while listing dirents. +For now, we fixed it by passing dummy `inode_number`, instead of zero, to dirent. + +The code review is currently ongoing with my mentor mailto:chuck@FreeBSD.org[Chuck Tuffli]. + +I am happy to say that SquashFS will find its place in upcoming FreeBSD releases. + +Sponsor: The Google Summer of Code 2023 program diff --git a/website/content/en/status/report-2023-07-2023-09/ufs_snapshots.adoc b/website/content/en/status/report-2023-07-2023-09/ufs_snapshots.adoc new file mode 100644 index 0000000000..fb755ab7c9 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/ufs_snapshots.adoc @@ -0,0 +1,18 @@ +=== Enabling Snapshots on Filesystems Using Journaled Soft Updates + +Contact: Marshall Kirk McKusick <mckusick@FreeBSD.org> + +This project has made UFS/FFS filesystem snapshots available when running with journaled soft updates. +The details of this project were link:https://www.freebsd.org/status/report-2022-10-2022-12/#_enabling_snapshots_on_filesystems_using_journaled_soft_updates[described in the 2022 fourth quarter report]. + +This project had two milestones: + +The first milestone of this project was to make it possible to take snapshots when running with journaled soft updates and to use them for doing background dumps on a live filesystem. +Background dumps are requested by using the -L flag to man:dump[8]. +This milestone was completed in Q4 of 2022 and was made available in the 13.2 release as link:https://www.freebsd.org/status/report-2023-01-2023-03/#_enabling_snapshots_on_filesystems_using_journaled_soft_updates_in_13_2[described in the 2023 first quarter report]. + +The second milestone of this project was to do a background check using a snapshot on a filesystem running with journaled soft updates. +This milestone was completed in the third quarter of 2023 in time to be included as part of the 14.0 release. +It was also made available in the 13.2-STABLE release. + +Sponsored by: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-07-2023-09/valgrind.adoc b/website/content/en/status/report-2023-07-2023-09/valgrind.adoc new file mode 100644 index 0000000000..2433adc4de --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/valgrind.adoc @@ -0,0 +1,24 @@ +=== Valgrind: valgrind-devel updated for FreeBSD 15 + +Links: + +link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[] + +link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[] + +Contact: Paul Floyd <pjfloyd@wanadoo.fr> + +package:devel/valgrind-devel[] is in the process of being updated. +This contains most of what will be in the official release of Valgrind 3.22 due out in October. + +`memcheck` has been enhanced with some more checks. +It will now report usage of `realloc` with a size of zero. +Such usage is not portable and is deprecated (C23 will make it Undefined Behaviour). +`memcheck` now validates the values used for alignment and sized delete for `memalign`, `posix_memalign`, `aligned_alloc` and all aligned and sized overloads of `operator new` and `operator delete`. +Reading `DWARF` debuginfo is now done in a lazy manner which can improve performance. + +As usual there are numerous small bugfixes. + +Specific to FreeBSD there is now support for FreeBSD 15. +Two extra `_umtx_op` operations are now supported, `UMTX_OP_GET_MIN_TIMEOUT` and `UMTX_OP_SET_MIN_TIMEOUT`. +There is a fix for the use of sysctl kern proc pathname with the guest pid or -1, which previously returned the path of the Valgrind host. +The sysctl will now return the path of the guest. +Support for the `close_range` system call has been added. diff --git a/website/content/en/status/report-2023-07-2023-09/wifibox.adoc b/website/content/en/status/report-2023-07-2023-09/wifibox.adoc new file mode 100644 index 0000000000..bba1507c68 --- /dev/null +++ b/website/content/en/status/report-2023-07-2023-09/wifibox.adoc @@ -0,0 +1,30 @@ +=== Wifibox: Use Linux to Drive your Wireless Card on FreeBSD + +Links: + +link:https://github.com/pgj/freebsd-wifibox[Project GitHub Page] URL: link:https://github.com/pgj/freebsd-wifibox[] + +link:https://cgit.freebsd.org/ports/tree/net/wifibox[net/wifibox port] URL: link:https://cgit.freebsd.org/ports/tree/net/wifibox[] + +Contact: PÁLI Gábor János <pali.gabor@gmail.com> + +Wifibox is an experimental project for exploring the ways of deploying a virtualized Linux guest to drive wireless networking cards on the FreeBSD host system. +There have been guides to describe how to set this up manually, and Wifibox aims to implement those ideas as a single easy-to-use software package. + +* It uses man:bhyve[8] to run the embedded Linux system. +This helps to achieve low resource footprint. +It requires an x64 CPU with I/O MMU (AMD-Vi, Intel VT-d), ~150 MB physical memory, and some disk space available for the guest virtual disk image, which can be even ~30 MB only in certain cases. +It works with FreeBSD 12 and later, some cards may require FreeBSD 13 though. +* The guest is constructed using link:https://alpinelinux.org/[Alpine Linux], a security-oriented, lightweight distribution based on link:https://www.musl-libc.org/[musl libc] and link:https://busybox.net/[BusyBox], with some custom extensions and patches imported from link:https://archlinux.org/[Arch Linux] most notably. +It is shipped with a number of diagnostic tools for better management of the hardware in use. +The recent version features Linux 6.1, but Linux 6.5 is also available as an alternative. +* Configuration files are shared with the host system. +The guest uses man:wpa_supplicant[8] or man:hostapd[8] (depending on the configuration) so it is possible to import the host's man:wpa_supplicant.conf[5] or man:hostapd.conf[5] file without any changes. +* When configured, man:wpa_supplicant[8] and man:hostapd[8] control sockets could be exposed by the guest, which enables use of related utilities directly from the host, such as man:wpa_cli[8] or man:wpa_gui[8] from the package:net/wpa_supplicant_gui[] package, or man:hostapd_cli[8]. +* Everything is shipped in a single package that can be easily installed and removed. +This comes with an man:rc[8] system service that automatically launches the guest on boot and stops it on shutdown. +* It can be configured to forward IPv6 traffic, which is currently an experimental option but turned on by default. + +Wifibox has been mainly tested with Intel chipsets, and it has shown great performance and stability. +Therefore, it might serve as an interim solution whilst FreeBSD matures its support for these chipsets. + +It was confirmed that Wifibox works with Atheros, Realtek, and Mediatek chipsets too, and feedback is more than welcome about others. +Broadcom chips (that are often found in MacBook Pros) can also work, but there are known stability issues. diff --git a/website/content/en/status/report-2023-10-2023-12/_index.adoc b/website/content/en/status/report-2023-10-2023-12/_index.adoc new file mode 100644 index 0000000000..019143f8a0 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/_index.adoc @@ -0,0 +1,163 @@ +--- +title: "FreeBSD Status Report Fourth 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-10-2023-12 + +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[] + +''' + +[[userland]] +== Userland + +{userland-desc} + +''' + +include::{reports-path}/service-jails.adoc[] + +''' + +[[kernel]] +== Kernel + +{kernel-desc} + +''' + +include::{reports-path}/packrat.adoc[] + +''' + +[[architectures]] +== Architectures + +{architectures-desc} + +''' + +include::{reports-path}/armv7.adoc[] + +''' + +include::{reports-path}/simd.adoc[] + +''' + +[[cloud]] +== Cloud + +{cloud-desc} + +''' + +include::{reports-path}/openstack.adoc[] + +''' + +include::{reports-path}/azure.adoc[] + +''' + +include::{reports-path}/ec2.adoc[] + +''' + +[[documentation]] +== Documentation + +{documentation-desc} + +''' + +include::{reports-path}/doceng.adoc[] + +''' + +include::{reports-path}/freebsd-online-editor.adoc[] + +''' + +include::{reports-path}/wiki.adoc[] + +''' + +[[ports]] +== Ports + +{ports-desc} + +''' + +include::{reports-path}/kde.adoc[] + +''' + +include::{reports-path}/gnome-contributions.adoc[] + +''' + +include::{reports-path}/gcc.adoc[] + +''' + +[[third-Party-Projects]] +== Third Party Projects + +{third-Party-Projects-desc} + +''' + +include::{reports-path}/pot.adoc[] diff --git a/website/content/en/status/report-2023-10-2023-12/armv7.adoc b/website/content/en/status/report-2023-10-2023-12/armv7.adoc new file mode 100644 index 0000000000..b093019b52 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/armv7.adoc @@ -0,0 +1,17 @@ +=== armv7 Ports Quality Assurance + +Contact: Robert Clausecker <fuz@FreeBSD.org> + +As part of a long term project to improve the quality of the FreeBSD ports collection for the armv7 architecture, a number of issues in the base system and in various ports have been fixed. +Through this action, the number of binary packages that could be successfully built from the 2023Q4 branch of the ports collection was increased from 30018 (as of 2023-10-04) to 31118 (as of 2023-11-24). + +Two kernel bugs affecting package builds (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267788[PR 267788] and link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274705[PR 274705]) were identified and addressed, with these two alone being responsible for around 900 failed packages. +The most common other causes for build failures include + + * lack of FreeBSD-specific armv7 support code + * data alignment issues (armv7 being one of the few architectures for which we do not support unaligned memory accesses) + * address space exhaustion during the build processes (usually LTO related; link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274705[PR 274705] addressed many cases) + * lack of OpenMP support on armv7 FreeBSD + +If you are a user of the FreeBSD ports collection on armv7, do not hesitate to file a bug report on our link:https://bugzilla.freebsd.org[bug tracker] should there be any issues. + diff --git a/website/content/en/status/report-2023-10-2023-12/azure.adoc b/website/content/en/status/report-2023-10-2023-12/azure.adoc new file mode 100644 index 0000000000..26331823a0 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/azure.adoc @@ -0,0 +1,32 @@ +=== 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 <bsdic@microsoft.com> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-cloud[freebsd-cloud Mailing List] + +Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> + +Contact: Wei Hu <whu@FreeBSD.org> + +Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + + +In this quarter, we have solved all the blocking issues and published the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-14_0[14.0-RELEASE on Azure Marketplace], with complete architecture (amd64, arm64) and VM generation (gen1, gen2) support, available in both UFS and ZFS as the root file system. + +Work in progress tasks: + +* Automating the image building and publishing process and merging to [.filename]#src/release/#. +* Building and publishing snapshot builds to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery]. + +The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft. + +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] +* Port link:https://github.com/Azure/azure-linux-extensions[Linux Virtual Machine Extensions for Azure] + +Sponsor: Microsoft for people in Microsoft, and for resources for the rest + +Sponsor: The FreeBSD Foundation for everything else diff --git a/website/content/en/status/report-2023-10-2023-12/bugmeister.adoc b/website/content/en/status/report-2023-10-2023-12/bugmeister.adoc new file mode 100644 index 0000000000..d023aa8e5f --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/bugmeister.adoc @@ -0,0 +1,47 @@ +=== Bugmeister Team and Bugzilla + +Links: + +link:https://www.freebsd.org/administration/#t-bugmeister[Bugmeister team] URL: link:https://www.freebsd.org/administration/#t-bugmeister[] + +link:https://bugs.freebsd.org/bugzilla/[FreeBSD Bugzilla] URL: link:https://bugs.freebsd.org/bugzilla/[] + +Contact: Bugmeister <bugmeister@FreeBSD.org> + +Some recent maintenance has been done on our Bugzilla instance: + +* the weekly reminder emails now include the correct values for mfc-* Flags queries; +* the Dashboard page has had an obsolete query removed. +(We no longer use the 'patch-ready' Keyword; it was too much paperwork. +Thus, the query on that field was useless.); +* the limit that capped the maximum number of reported PRs at 10000 has been raised to 12500. + +In addition, the Wiki documentation on our Bugzilla has been +updated: + +* the page link:https://wiki.freebsd.org/Bugzilla/SearchQueries[] has been substantially reworked: +** In particular, documentation about how to search on Flag values has been added. +(This may not have been done before.) +Example: search for PRs with Flag 'mfc-stable14' set; +** This page may be of interest to all committers and contributors; + +* the page https://wiki.freebsd.org/Bugmeister/BugmeisterQA has also been updated; +While similar to the above, it is of more specific interest to bugmeister and triagers. + +As well, PRs that are specific to FreeBSD 12 are being culled, as 12 has gone out of support as of 20231231. + +A further effort is being made to document our setup of Bugzilla itself, especially with respect to our customizations. +This is needed to bring our own repository up to date with what is running +on production. + +The number of PRs over the past quarter (and year) has remained consistent. +However, we do seem to be closing incoming PRs more quickly these days. +For reference: link:https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html&days=90[]. + +The overall number of PRs remains around 11,400. + +Bugmeister is also working towards restarting the Bugathons. +See the updated page link:https://wiki.freebsd.org/Bugathons[]. + +Bugmeister would like to thank a number of people who have assisted with bugbusting, including Mina Galić, Graham Perrin, mailto:salvadore@FreeBSD.org[Lorenzo Salvadore], and mailto:fernape@FreeBSD.org[Fernando Apesteguìa], among others. + +In addition, bugmeister would like to thank all the FreeBSD committers who help process the PRs as they come in. +Over the last few months we seem to be much closer to steady-state. diff --git a/website/content/en/status/report-2023-10-2023-12/ci.adoc b/website/content/en/status/report-2023-10-2023-12/ci.adoc new file mode 100644 index 0000000000..fec13a4c7b --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/ci.adoc @@ -0,0 +1,50 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] + +link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://tinderbox.freebsd.org[] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] + +link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] + +link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] + +link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] + +link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +In the fourth quarter of 2023, we worked with the project contributors and developers to address their testing requirements. +Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. + +Important completed tasks: + +* Adding job to build amd64 architecture with GCC 13 (thanks jhb@) +* Adding powerpc64le jobs config for stable-14 (thanks alfredo@) +* Updating the build env of jobs of main and stable/14 branches to 14.0-RELEASE + +Work in progress tasks: + +* Designing and implementing pre-commit CI building and testing and pull/merged-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) +** Proof of concept system is in progress +* Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds +* Simplifying CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Redesigning the hardware test lab and adding more hardware for testing +* Merge link:https://reviews.freebsd.org/D38815[] +* Merge link:https://reviews.freebsd.org/D36257[] + +Open or queued tasks: + +* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] +* Setting up public network access for the VM guest running tests +* Implementing use of bare-metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort! + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-10-2023-12/clusteradm.adoc b/website/content/en/status/report-2023-10-2023-12/clusteradm.adoc new file mode 100644 index 0000000000..da3375e991 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/clusteradm.adoc @@ -0,0 +1,46 @@ +=== Cluster Administration Team + +Links: + +link:https://www.freebsd.org/administration/#t-clusteradm[Cluster Administration Team members] URL: link:https://www.freebsd.org/administration/#t-clusteradm[] + +Contact: Cluster Administration Team <clusteradm@FreeBSD.org> + +FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications. + +In this quarter, the team has worked on the following: + +* Regular support for FreeBSD.org user accounts. +* Regular disk and parts support (and replacement) for all physical hosts and mirrors. +* Enable mirroring of link:https://www.FreeBSD.org[] and link:https://docs.FreeBSD.org[] in the FreeBSD project-managed mirrors. +* Cluster refresh, upgrading all hosts and jails to the most recent versions of 15-CURRENT, 14-STABLE, 13-STABLE, and 12-STABLE. +* Begin sunsetting 12-STABLE infrastructure as the branch approaches its end of life. + +In addition to these projects, with link:https://www.modirum.com[Modirum] generously link:https://github.com/sponsors/ppaeps/[sponsoring Philip's time] for most of October, we were able to bring pkgbase into "preview" production in time for 14.0-RELEASE in November. + +We also installed a new European mirror site in Sjöbo, Sweden, sponsored by Teleservice Skåne AB. +Traffic in Europe is now directed roughly equally between our existing mirror in Frankfurt (sponsored by Equinix) and the new mirror in Sweden. +After well over ten years in service, we plan to decommission our mirror site in the UK during first quarter of 2024. +We would like to thank link:https://www.bytemark.co.uk/[Bytemark Hosting] for supporting this mirror for all this time. + +Next quarter, supported by the FreeBSD Foundation, we plan to bring up a new primary cluster site in Chicago. + +==== FreeBSD Official Mirrors Overview + +Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America -- California, New Jersey (primary site), and Washington. + +The hardware and network connection have been generously provided by: + +* https://www.bytemark.co.uk/[Bytemark Hosting] (decommissioned during 2024Q1) +* Cloud and SDN Laboratory at https://www.bbtower.co.jp/en/corporate/[BroadBand Tower, Inc] +* https://www.cs.nycu.edu.tw/[Department of Computer Science, National Yang Ming Chiao Tung University] +* https://deploy.equinix.com/[Equinix] +* https://internet.asn.au/[Internet Association of Australia] +* https://www.isc.org/[Internet Systems Consortium] +* https://www.inx.net.za/[INX-ZA] +* https://www.kddi-webcommunications.co.jp/english/[KDDI Web Communications Inc] +* https://www.mohe.gov.my/en/services/research/myren[Malaysian Research & Education Network] +* https://www.metapeer.com/[Metapeer] +* https://nic.br/[NIC.br] +* https://your.org/[Your.Org] +* https://365datacenters.com/[365 Data Centers] +* https://www.teleservice.net/[Teleservice Skåne AB] (new since 2023Q4) diff --git a/website/content/en/status/report-2023-10-2023-12/core.adoc b/website/content/en/status/report-2023-10-2023-12/core.adoc new file mode 100644 index 0000000000..b94d88473d --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/core.adoc @@ -0,0 +1,30 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team <core@FreeBSD.org> + +The FreeBSD Core Team is the governing body of FreeBSD. + +Along the release engineering team, the project dedicates the 14.0-RELEASE to the memory of Hans Petter Selasky. + +==== 14.0-RELEASE + +FreeBSD 14.0 was released at the end of 2023Q4. + +The release notes can be found at + + https://www.freebsd.org/releases/14.0R/relnotes/ + + +==== New Release Engineering Team + +After years of serving as the release engineer gjb@ stepped down. + +cperciva@ took over as the new release engineer. +karels@ is serving as the new deputy release engineer. + +Core would like to thank gjb@ for his long tenure and the many timely releases he created. + +==== FreeBSD 2024 Community Survey + +In the end of 2023, Core Team works with the Foundation to do the 2024 +community survey. diff --git a/website/content/en/status/report-2023-10-2023-12/doceng.adoc b/website/content/en/status/report-2023-10-2023-12/doceng.adoc new file mode 100644 index 0000000000..8dfc307351 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/doceng.adoc @@ -0,0 +1,99 @@ +//// +Quarter: 4th quarter of 2023 +Prepared by: fernape +Reviewed by: +Last edit: $Date$ +Version: $Id$ +//// + +=== 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[] + +Contact: FreeBSD Doceng Team <doceng@FreeBSD.org> + +The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. + +During the last quarter: + +Glen Barber stepped down from doceng. +doceng would like to thank gjb@ for his service. + +Ceri Davies' commit bit was taken for safekeeping as per his request. +doceng would like to thank ceri@ for his contributions. + +mhorne@ to be mentored by carlavilla@ to obtain a documentation commit bit. + +==== FreeBSD Handbook: + +The Handbook was updated to show that FreeBSD 14.0 is the latest release. + + +==== 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/[] + +===== Q4 2023 Status + +* 17 team languages +* 203 registered users + +===== 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: 33%) +* Norwegian (nb-no) (progress: 1%) +* Persian (fa-ir) (progress: 2%) +* Polish (progress: 1%) +* Portuguese (progress: 0%) +* Portuguese (pt-br) (progress: 22%) +* Spanish (es) (progress: 35%) +* 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 <carlavilla@FreeBSD.org> + + * link:https://reviews.freebsd.org/D40546[The Network chapter has been rewritten] + * link:https://cgit.freebsd.org/doc/commit/?id=612b7cc1721224c494c5b2600188e1508bb5611b[The Jails chapter has been rewritten] + * The next section to work on will be the file systems part: UFS, ZFS, Other File Systems + +==== FAQ Working Group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +A new FAQ was released alongside FreeBSD 14.0. + +==== FreeBSD Website Revamp - WebApps working group + +Contact: Sergio Carlavilla <carlavilla@FreeBSD.org> + +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 will be divided into three phases: + +. Redesign of the Manual Pages on web ++ +Scripts to generate the HTML pages using mandoc. (_Complete, Approved by Doceng, Deploy Date Not Decided Yet_) +Public instance on https://man-dev.FreeBSD.org + +. Redesign of the FreeBSD main website ++ +New design, responsive and dark theme. (_Almost Complete, Presented at EuroBSDCon_) + +. Redesign of the Ports page on web ++ +Ports scripts to create an applications portal. (_Work in progress_) diff --git a/website/content/en/status/report-2023-10-2023-12/ec2.adoc b/website/content/en/status/report-2023-10-2023-12/ec2.adoc new file mode 100644 index 0000000000..5528094687 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/ec2.adoc @@ -0,0 +1,18 @@ +=== FreeBSD on EC2 + +Links: + +link:https://www.patreon.com/cperciva[FreeBSD/EC2 Patreon] URL: https://www.patreon.com/cperciva[] + +Contact: Colin Percival <cperciva@FreeBSD.org> + +FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances. +Work continues to ensure that upcoming instance types will be supported; most recently, changes were needed to support "7th generation" Intel and AMD instances. + +FreeBSD 14.0-RELEASE shipped with experimental ZFS-root AMIs and "cloud-init" AMIs. +Additional "flavored" FreeBSD AMIs are planned, including "AMI Builder" and "minimal" (no debug symbols). + +A bug in the release-building process which resulted in 14.0-RELEASE AMIs shipping with duplicate lines in /etc/rc.conf has been corrected and future releases should not be affected. + +A bug in the ec2-aws-imdsv2-get utility which resulted in 14.0-RELEASE AMIs not supporting binary user-data files has been corrected and future releases should not be affected. + +This work is supported by Colin's FreeBSD/EC2 Patreon. diff --git a/website/content/en/status/report-2023-10-2023-12/freebsd-foundation.adoc b/website/content/en/status/report-2023-10-2023-12/freebsd-foundation.adoc new file mode 100644 index 0000000000..b2f2eb8237 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/freebsd-foundation.adoc @@ -0,0 +1,133 @@ +=== 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 <deb@FreeBSDFoundation.org> + +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. + +We supported FreeBSD in the following ways during the last quarter of 2023: + +==== OS Improvements + +During the fourth quarter of 2023, 236 src, 47 ports, and 33 doc tree commits identified The FreeBSD Foundation as a sponsor. +Some of this Foundation-sponsored work is described in separate report entries: + +* <<_openstack_on_freebsd,OpenStack on FreeBSD>> +* <<_simd_enhancements_for_amd64,SIMD enhancements for amd64>>. + +Three new contractors started. +Cheng Cui began working full-time on wireless networking. +A main goal for Cheng's project is to assist Bjoern Zeeb with 802.11ac support in iwlwifi. +Tom Jones began work 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. +Olivier Certner joined the FreeBSD Foundation as a general FreeBSD developer. +Some of Olivier's contributions so far include: + +* reviewing, fixing, and hardening several security policies aimed at limiting process visibility, policies that are based on user identity, group membership, or sub-jail membership +* committing fixes in the login class code, including one that allowed unprivileged users to bypass resource limits +* implementing a secure hardware fix for the Zenbleed issue affecting AMD Zen2 processors. + +Here is a sampling of other Foundation-sponsored work completed over the last quarter of 2023: + +* arm64: Add Armv8 rndr random number provider +* net80211, LinuxKPI, and iwlwifi fixes and improvements +* OpenSSL: updates to 3.0.11 and 3.0.12 +* Various freebsd-update fixes in preparation for 14.0 +* ssh: Update to OpenSSH 9.5p1 +* Various iommu fixes +* Various makefs/zfs fixes + +Learn more about our software development work for all of 2023 at https://freebsdfoundation.org/blog/2023-in-review-software-development/. + +==== FreeBSD Infrastructure + +We approved over $100,000 for a cluster refresh that began in late 2023 and will carry over into the new year by purchasing and shipping 15 new servers to 4 racks generously donated by NYI in their new Chicago facility. +The systems specifications were determined by the Cluster Administration team and consist of: + +* 5 package builders +* 3 web servers +* 2 package mirrors +* 2 CI servers +* 2 firewall/router +* 1 admin bastion + +More on our 2023 infrastructure support can be found at: https://freebsdfoundation.org/blog/2023-in-review-infrastructure/. + +==== 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 + +In Q4 I connected with the following people, companies, and organizations: Phil Shafer, who works at Juniper Networks, and I met at All Things Open. +He told me about the libxo library and his continuing work on related issues, like rewriting and filtering output to allow richer options that regular expressions provide. +Sticking with Juniper, I also met Simon Gerraty at the Vendor Summit and heard his talk on link:https://www.youtube.com/live/k-AzShVdAHo?si=otJvsMLc3gqilZSU&t=22069[SecureBoot]. +In alphabetical order, I also met with AMD, Ampere, Center for Internet Security (CIS), Innovate UK, Michael Dexter, Metify, Microsoft, several people at NetApp when I attended their annual conference (Thank you for the invitation!!), NetScaler, NIST, Nozomi Networks, NVIDIA, members of the Open Container Initiative community, OpenSSF, RG Nets, Doug Rabson. + +I greatly appreciated the opportunity to attend NetApp's annual conference in October. +I heard from and connected with experts at NetApp and their partners and customers on topics such as AI and seamless AI data pipelines, hybrid cloud, and green computing. +I took the opportunity to hand out some FreeBSD lapel pins 🙂 and I connected with a FreeBSD user and member of the Enterprise WG whose company is a NetApp Customer. + +In Q4 we link:https://freebsdfoundation.org/news-and-events/latest-news/freebsd-foundation-announces-ssdf-attestation/[announced the new FreeBSD SSDF Attestation] program to help commercial users of FreeBSD comply with new US Government procurement regulations. +This program was informed by valuable feedback from NetApp, Metify, and NIST, and the genesis of the idea came thanks to my involvement with open source policy experts, in particular via the OSI's Open Policy Alliance. + +The link:https://github.com/opencontainers/tob/pull/133[Open Container Initiative Technical Oversight Board voted] in December to approve Doug Rabson's proposal to create a Working Group to extend the OCI runtime specification to support FreeBSD. +Huge thanks to all involved! +An OCI runtime extension for FreeBSD is one of the most frequently requested capabilities and I was happy to play a small role in helping to coordinate this effort so far. + +The Vendor Summit in November was a great event. +Huge props to John Baldwin and Anne Dickison for all the work to organize and orchestrate. +I got a lot out of the event. +Personal highlights were conversations with a diversity of users, the CHERI talk, the end user panel, and Allan's talk on being an upstream first company. +For a full recap on our efforts to strengthen partnerships and increase funding in 2023, check out: link:https://freebsdfoundation.org/blog/2023-in-review-partnerships-and-research/[]. + +==== Advocacy + +From organizing and attending events, to creating technical content that educates, and expanding the coverage of FreeBSD in the media, here is a sample of what we did last quarter to support FreeBSD. + +* Helped organize and sponsor the November 2023 Vendor Summit held at NetApp in San Jose. + Many consider this one of the best summits to date. + Be sure to check out the link:https://youtube.com/playlist?list=PLugwS7L7NMXzSalaF4l_78sfRa2l8xvag&feature=shared[videos]. +* Introduced FreeBSD to new and returning folks at link:https://freebsdfoundation.org/blog/all-things-open-2023-conference-report/[All Things Open] in North Carolina. +* Provided an overview of FreeBSD 14: link:https://freebsdfoundation.org/blog/security-performance-and-interoperability-introducing-freebsd-14/[Security, Performance, and Interoperability; Introducing FreeBSD 14] +* In collaboration with the Core team, released the link:https://freebsdfoundation.org/blog/2024-freebsd-community-survey-is-here/[2024 FreeBSD Community Survey] +* Participated in an interview about FreeBSD: link:https://freebsdfoundation.org/news-and-events/latest-news/what-the-dev-podcast-the-evolution-of-the-freebsd-project/[What the Dev Podcast: The Evolution of the FreeBSD Project] +* Release the link:https://freebsdfoundation.org/past-issues/13099/[September/October 2023] issue of the FreeBSD Journal now with HTML versions of the articles. + +For a full recap of what we did to advocate for FreeBSD in 2023, please check out the Advocacy Year in Review: link:https://freebsdfoundation.org/blog/2023-in-review-advocacy/[] or the monthly newsletters: link:https://freebsdfoundation.org/our-work/latest-updates/?filter=newsletter[]. + +==== Fundraising + +Thank you to everyone who gave us a financial contribution last quarter to help fund our work to support the Project. +You brought us even closer to our goal and we are grateful for your investment in FreeBSD! +We are still receiving donations in the mail and will post the final number in mid-February. + +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-2023-10-2023-12/freebsd-online-editor.adoc b/website/content/en/status/report-2023-10-2023-12/freebsd-online-editor.adoc new file mode 100644 index 0000000000..88bae2050c --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/freebsd-online-editor.adoc @@ -0,0 +1,21 @@ +=== FreeBSD Online Editor and Man Page Editor + +Links: + +link:https://github.com/Wang-Yan-Hao/FreeBSD-Online-Document-Editor[FreeBSD Online Document Editor] URL: link:https://github.com/Wang-Yan-Hao/FreeBSD-Online-Document-Editor[] + +link:https://github.com/Wang-Yan-Hao/man_page_editor[FreeBSD Online Man Page Editor] URL: link:https://github.com/Wang-Yan-Hao/man_page_editor[] + +Contact: Yan-Hao Wang <bses30074@gmail.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +This report provides a continued overview of the FreeBSD online editor and man page editor project, outlining recent efforts to enhance the documentation and manual page editing processes. +In order to optimize the project's structural integrity, we enlisted the expertise of a professional front-end programmer. +We plan to release the editor soon and currently have some tasks that require additional support. + +1. We are actively seeking a qualified individual to conduct a comprehensive front-end security review of the project. + +2. A meticulous inspection of the JavaScript code is imperative to ensure its robustness and efficiency. +We are looking for someone with expertise to thoroughly examine the codebase, identify any issues, and propose enhancements for optimal performance. + +3. Since there is currently no existing JavaScript library for rendering mandoc, I had to create my own. +However, there are still some hidden errors that emerge during the editing process. +We are seeking assistance to fix these rendering issues. diff --git a/website/content/en/status/report-2023-10-2023-12/gcc.adoc b/website/content/en/status/report-2023-10-2023-12/gcc.adoc new file mode 100644 index 0000000000..c9bef54c0d --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/gcc.adoc @@ -0,0 +1,25 @@ +=== GCC on FreeBSD + +Links: + +link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] + +link:https://gcc.gnu.org/gcc-10/[GCC 10 release series] URL: link:https://gcc.gnu.org/gcc-10/[] + +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/[] + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273397[Updating GCC default version to 13] is moving ahead. +Thanks to mailto:antoine@FreeBSD.org[Antoine Brodin] who ran the exp-runs and to all other developers and ports maintainers involved. + +As you might remember from last quarter, additional patches were tested together with the default version updates. +Some of them have already been merged: + +* package:lang/gcc11[] has switched back to STANDARD_BOOTSTRAP and has been updated to 11.4.0; +* package:lang/gcc13[] has been updated to version 13.2.0. + +About half of the open bugs have been fixed, but another half remains. +If you maintain any of the affected ports, please try to fix your port(s) and/or get your port buildable with the compiler in base. + +This quarter many bug reports have also been opened about GCC. +As soon as the default GCC version update is finished, all of those bugs will be addressed. diff --git a/website/content/en/status/report-2023-10-2023-12/gnome-contributions.adoc b/website/content/en/status/report-2023-10-2023-12/gnome-contributions.adoc new file mode 100644 index 0000000000..077c854883 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/gnome-contributions.adoc @@ -0,0 +1,47 @@ +=== State of GNOME 44 + +Links: + +link:https://www.gnome.org/[GNOME] URL: link:https://www.gnome.org/[] + +link:https://codeberg.org/olivierd/freebsd-ports-gnome[Development repository] URL: link:https://codeberg.org/olivierd/freebsd-ports-gnome[] + +Contact: FreeBSD GNOME Team <gnome@FreeBSD.org> + +Contact: Olivier Duchateau <duchateau.olivier@gmail.com> + +GNOME is a full desktop environment which is mainly based on GLib, GTK3/GTK4, and libadwaita. +It provides two window managers or compositors: package:x11-wm/mutter[] and package:x11-wm/metacity[]. + +Currently in the ports collection, package:x11/gnome-shell[] is not supported by upstream anymore. +As it is a lot of work, in order to have GNOME 44 available for users, I decided to split this update, because it impacts several ports. + +As a maintainer of package:x11/budgie[] and Pantheon desktop (a window manager based on package:x11-wm/mutter[], developed for link:https://elementary.io/[elementary OS]) I need more recent versions of some GNOME libraries. + +Firstly I worked on WebKitGTK. +The 4.0 "legacy" API is almost not used by GNOME's libraries. +The bare minimum is the 4.1 API. +I created [.filename]#webkit.mk# for the [.filename]#Mk/Uses# framework, in order to _flavorize_ package:www/webkit2-gtk3[]. +There is an link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275914[ongoing effort], but currently it is too unstable. +Often applications such as Epiphany, mail clients (Geary, Evolution), or the online accounts panel in package:sysutils/gnome-control-center dump core. + +Nonetheless, remainder of desktop is usable and the latest release (44.7) of GNOME Shell is functional. +I have begun sending my first patches for review (as well as those in Bugzilla). + +* link:https://reviews.freebsd.org/D43183[D43183] +* link:https://reviews.freebsd.org/D43230[D43230] +* link:https://reviews.freebsd.org/D43244[D43244] +* link:https://reviews.freebsd.org/D40489[D40489] + +I have also ported the link:https://wiki.gnome.org/Projects/GnomeFlashback[GNOME Flashback] session module. +It depends on package:x11-wm/metacity[] and package:x11-toolkits/libwnck3[]. + +I also maintain a link:https://codeberg.org/olivierd/freebsd-ports-gnome/wiki[documentation], and we can link:https://codeberg.org/olivierd/freebsd-ports-gnome/src/branch/screenshots[see] various desktops available. + +GNOME 45 is almost finished, except for GNOME Shell extensions. +For this release I will focus on Wayland support (link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258042[bug #258042] and link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271836[bug #271836]). + +Tests and patches are welcomed, especially for WebKitGTK. + +Next months I plan to work on: + +* Allowing selecting a session in display manager (gdm), it is regression with our patches. +* Fixing sharing network (VNC, SSH) panel in package:sysutils/gnome-control-center[] and backport for link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275900[bug #275900]. +* Continuing to update applications and libraries for GNOME 45. diff --git a/website/content/en/status/report-2023-10-2023-12/intro.adoc b/website/content/en/status/report-2023-10-2023-12/intro.adoc new file mode 100644 index 0000000000..0e49ade0a6 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/intro.adoc @@ -0,0 +1,11 @@ +Here is the fourth 2023 status report, with 18 entries. + +This is the last 2023 quarter. +As you have probably noticed, this status report comes later than usual and with fewer reports than the preceding quarter. +Indeed, please keep in mind that the last quarter of every year is for many members of our community the quarter of the celebrations for Christmas and for the New Year, which implies that those members will spend more time with their families and will have less time for their favorite voluntary software projects. +Thus there is less to report and reports tend to arrive later. +But finally, here they are. + +Have a nice read. + +Lorenzo Salvadore, on behalf of the Status Team. diff --git a/website/content/en/status/report-2023-10-2023-12/kde.adoc b/website/content/en/status/report-2023-10-2023-12/kde.adoc new file mode 100644 index 0000000000..5cbadf30fe --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/kde.adoc @@ -0,0 +1,62 @@ +=== KDE on FreeBSD + +Links: + +link:https://freebsd.kde.org/[KDE/FreeBSD initiative] URL: link:https://freebsd.kde.org/[] + +link:https://community.kde.org/FreeBSD[FreeBSD -- KDE Community Wiki] URL: link:https://community.kde.org/FreeBSD[] + +Contact: Adriaan de Groot <kde@FreeBSD.org> + +The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. +The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. + +The mailto:kde@FreeBSD.org[KDE team] is part of mailto:desktop@FreeBSD.org[desktop@] and mailto:x11@FreeBSD.org[x11@], building the software stack to make FreeBSD beautiful and usable as a daily-driver graphical desktop workstation. +The notes below describe *mostly* ports for KDE, but also include items that are important for the entire desktop stack. + +==== Infrastructure + +CMake was updated several times and is now version 3.28.1, the latest upstream release. +FreeBSD ports are once again fully up-to-date. + +Qt5 is now on long-term support and updates only rarely. +The KDE patch collection is a community-supported branch of Qt which pulls in upstream patches and fixes from the KDE community, and updated to 5.15.12. +There were several deprecations (see below) in the Qt5 ports. + +Qt6 and KDE's upcoming megarelease of KDE Plasma 6 (scheduled for 2024q1) are the next major milestone for the KDE team. +Qt6 was updated to version 6.6.1 along with the Python bindings for Qt, PySide. +An alpha-release of KDE Frameworks 6 was added to the ports tree. + +==== KDE Stack + +KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. +These (large) updates land shortly after their upstream release and are not listed separately. + +* KDE Frameworks reached version 5.112. + The KDE Frameworks 5 series is winding down, although it will a few months still until it enters long-term support upstream. +* KDE Plasma Desktop was updated to version KDE Plasma 5.27.10. +* KDE Gear updated to 23.08.4. +* KDE Frameworks 6 (alpha) 5.247 was updated in the ports tree. +* KDE Plasma Desktop 6 (beta 2) 5.91.0 was updated in the ports tree. + +==== Related Ports + +The KDE ecosystem includes a wide range of ports -- most maintained by mailto:kde@FreeBSD.org[kde@], all building on a shared base of Qt and KDE Frameworks. +The mailto:kde@FreeBSD.org[KDE team] updates them all as needed. +This quarter the KDE team would like to thank mailto:tcberner@FreeBSD.org[Tobias C. Berner], mailto:arrowd@FreeBSD.org[Gleb Popov] and mailto:jhale@FreebSD.org[Jason E. Hale] again for keeping things up-to-date. + +Many ports have been "flavorized" to support a Qt5 and a Qt6 flavor in the ports tree. + +Special mention to: + +* New port package:x11/xwaylandvideobridge[]. + By design, X11 applications can’t access window or screen contents for Wayland clients. + The video bridge improves Wayland support for screen sharing tools like Discord, MS Teams, Skype, and more. + Screen sharing is fully under the control of the Wayland user. +* Update for package:multimedia/mlt7[] which was updated to 7.20.0. +* Update for package:sysutils/bsdisks[] which was updated to 0.33. +* Bugfix for package:devel/llvm15[] to make package:devel/kdevelop[] work again. +* Security fixes for package:www/qt5-webengine[] and package:www/qt6-webengine[]. + +==== Deprecations + +Web browsers are huge, and have a considerable security surface. +The venerable package:www/qt5-webkit[] WebKit port was removed on the last day of 2023. diff --git a/website/content/en/status/report-2023-10-2023-12/openstack.adoc b/website/content/en/status/report-2023-10-2023-12/openstack.adoc new file mode 100644 index 0000000000..b46fc13337 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/openstack.adoc @@ -0,0 +1,21 @@ +=== OpenStack on FreeBSD + +Links: + +link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] + +link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[] + +Contact: Chih-Hsin Chang <starbops@hey.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +In the fourth quarter, we successfully migrated the originally virtualized OpenStack platform to physical machines running FreeBSD 14.0-STABLE. +The ported OpenStack components include Keystone, Glance, Placement, Neutron, and Nova. +As part of this process, we took the opportunity to update link:https://github.com/openstack-on-freebsd/docs[the installation documentation and the list of dependencies]. + +Moving forward, we encourage users and developers interested in this project to effortlessly recreate the OpenStack platform in their FreeBSD environments following this documentation. +Any issues or difficulties encountered are welcome to be reported on the link:https://github.com/openstack-on-freebsd/admin/issues[GitHub project page]. +Your contributions will contribute to the refinement of our installation documentation and the overall porting efforts. + +In the upcoming quarter, our focus will shift towards incorporating various patches and workarounds generated during the migration process into the project in a more structured code form. +Additionally, we plan to develop FreeBSD ports for each OpenStack component, further streamlining the installation process. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-10-2023-12/packrat.adoc b/website/content/en/status/report-2023-10-2023-12/packrat.adoc new file mode 100644 index 0000000000..be08b5c467 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/packrat.adoc @@ -0,0 +1,63 @@ +=== Packrat - NFS client caching on non-volatile storage + +Contact: Rick Macklem <rmacklem@FreeBSD.org> + +NFSv4.1/4.2 provides support for a feature called delegations. +When a NFSv4.1/4.2 client holds a delegation, the client has certain rights to a file, including a guarantee that no other client will make changes to the file unless the delegation is recalled. +As such, when a client holds a delegation for a file, it can aggressively cache the file's data, knowing that it will not be modified by other clients until it returns the delegation. + +This project is intended to allow the NFSv4.1/4.2 client to aggressively cache file data on client local non-volatile storage, when the client holds a delegation for the file. +I created a patch long ago to try and do this for NFSv4.0, but it was never at a stage where it was worth using. +This project is a complete rewrite of the patch, done in part because NFSv4.1/4.2 plus other recent NFSv4-related changes make doing this more feasible. + +I now have code running fairly well and hope to have a patch ready for others to test this winter. +Early testing shows promise. +For a test run of "make buildkernel", the test with and without packrat enabled performed as follows: + +.NFS operation counts +[cols="1,1,1,1,1,1", frame="none", options="header"] +|=== +| NFS operation counts +| Getattr +| Lookup +| Read +| Write +| Total RPCs + +|with packrats +|433506 +|99254 +|0 +|0 +|371736 + +|without packrats +|2359913 +|97954 +|10748 +|0 +|2318810 + +|=== + +.Elapsed Run Time +[cols="1,1,1", frame="none", options="header"] +|=== +| Elapsed Run Time (sec) +| with packrat +| without packrat + +| +|5561 +|6203 + +|=== + +As you can see, the packrat case ran a little faster and with fewer RPCs. +Although this test was run on my little LAN, it is hoped that a NFSv4.1/4.2 mount over a WAN would show a larger difference in performance. +I will note that the packrat cache was primed by unrolling a tarball of FreeBSD's [.filename]#/usr/src# into the NFSv4.1/4.2 mount. + +This will be very much an experimental feature, but it is hoped it will allow NFS mounts to be used more effectively, particularly in WAN situations, such as a mobile laptop. + +There is still work to be done, particularly with respect to recovery of delegations after a NFSv4.1/4.2 client restart. +Hopefully, the next status report will include a URL that allows downloading of a patch for user testing. diff --git a/website/content/en/status/report-2023-10-2023-12/portmgr.adoc b/website/content/en/status/report-2023-10-2023-12/portmgr.adoc new file mode 100644 index 0000000000..b2e497dfd2 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/portmgr.adoc @@ -0,0 +1,71 @@ +=== 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 <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +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 quarter. + +* According to INDEX, there are currently 31,942 ports in the Ports Collection. +There are currently ~3,100 open ports PRs. +The quarter saw 9,424 commits by 157 committers on the main branch and 781 commits by 71 committers on the 2023Q4 branch. +Compared to last quarter, this means a hefty decrease in the number of commits on the main branch (down from 11,454) and slightly fewer backports to the quarterly branch (down from 828). +The number of ports also fell a bit (down from 34,600). + +In Q4 there were around 9424 commits to main. +The most active committers were: + + sunpoet 2946 + yuri 861 + bofh 793 + jbeich 419 + fuz 324 + eduardo 168 + fernape 160 + jhale 153 + thierry 146 + diizzy 123 + +During Q4 we welcomed Michael Osipov (michaelo) and Timothy Beyer (beyert) as new committers, but sadly also had to say goodbye to bland, sbruno, hselasky and gjb. + +We invited arrowd, flo and riggs to be part of portmgr-lurkers for the next months. + +Support for FreeBSD 12.x was removed at the end of the quarter. + +The end of Q4 also saw the introduction of subpackages to the ports tree. +Similar to when flavors were introduced, new subpackages will require an approval by portmgr before being pushed to the tree. +With subpackages it is possible to create multiple packages from a single build of a port. + +The following happened on the infrastructure side: + +* Packages for 14.0-RELEASE were built +* Poudriere was updated to release-3.4 + +The no-longer maintained package:www/qt5-webkit[] was removed. + +postgresql11, php80, mysql57, percona57, ghostscript9 were removed. + +The following default versions changed: + +* perl to 5.36 +* ghostcript to 10 +* corosync to 3 + +Updates to major ports that happened were: + +* package:ports-mgmt/pkg[] to 1.20.9 +* package:ports-mgmt/poudriere[] to 3.4.0 (subpackage support) +* KDE-bits to plasma-5.27.10, frameworks-5.112, gear-23.08.4, and beta-2 +* package:www/chromium[] to 120.0.6099.129 +* package:www/firefox[] to 121.0 (rc1) +* package:lang/rust[] to 1.74.1 +* ... and many more ... + +During the last quarter, pkgmgr@ ran 26 exp-runs to test various ports upgrades, updates to default versions of ports, subpackage support and base system changes. diff --git a/website/content/en/status/report-2023-10-2023-12/pot.adoc b/website/content/en/status/report-2023-10-2023-12/pot.adoc new file mode 100644 index 0000000000..e82a5eec72 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/pot.adoc @@ -0,0 +1,25 @@ +=== 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) <pizzamig@FreeBSD.org> + +Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org> + +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]. + +During this quarter, link:https://github.com/bsdpot/pot/pull/285[Pot 0.16.0] was released containing link:https://github.com/bsdpot/pot/blob/master/CHANGELOG.md[a number of features and fixes], including link:https://github.com/bsdpot/pot/pull/283[a new setting to prevent direct traffic between VNET pots] and link:https://github.com/bsdpot/pot/pull/275[new attributes] to configure pot stop behavior. +There were also maintenance/stability releases to link:https://github.com/bsdpot/potnet/pull/56[potnet (0.5.0)] and a link:https://github.com/bsdpot/nomad-pot-driver/pull/52[nomad-pot-driver (0.10.0)]. + +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. + +One of the new container images that have been added during the last quarter is link:https://github.com/bsdpot/potluck/tree/master/zincsearch[Zincsearch], a more light-weight alternative to Elasticsearch written in Go. + +The link:https://github.com/bsdpot/potluck/tree/master/mastodon-s3[Mastodon container] is meanwhile powering the public link:https://mastodon.africa[mastodon.africa] instance. + +Also, we got some more publicity: link:https://www.bsdnow.tv/536[BSD Now Episode 536] is titled "Pot-flavored Jails". + +As always, feedback and patches are welcome. + +Sponsors: Nikulipe UAB, Honeyguide Group diff --git a/website/content/en/status/report-2023-10-2023-12/releng.adoc b/website/content/en/status/report-2023-10-2023-12/releng.adoc new file mode 100644 index 0000000000..85b73abbd7 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/releng.adoc @@ -0,0 +1,17 @@ +=== FreeBSD Release Engineering Team + +Links: + +link:https://www.freebsd.org/releases/13.3R/schedule/[FreeBSD 13.3-RELEASE schedule] URL: link:https://www.freebsd.org/releases/13.3R/schedule/[] + +link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] + +link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[] + +Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org> + +The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. + +During the fourth quarter of the year, the Team continued work on 14.0-RELEASE, leading to the final RELEASE build and announcement in November. +Planning has started for the upcoming 13.3-RELEASE and 14.1-RELEASE cycles. + +The Release Engineering Team continued providing weekly development snapshot builds for the *main* and *stable/13* branches, and (after 14.0-RELEASE) started weekly builds for *stable/14*. + +After over a decade as Release Engineering Lead, Glen Barber has retired from the role; his Deputy, Colin Percival, has moved into the Lead role, while Mike Karels has assumed the position of Deputy Release Engineer. diff --git a/website/content/en/status/report-2023-10-2023-12/service-jails.adoc b/website/content/en/status/report-2023-10-2023-12/service-jails.adoc new file mode 100644 index 0000000000..ce0d7fcb6c --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/service-jails.adoc @@ -0,0 +1,33 @@ +=== Service jails -- Automatic jailing of rc.d services + +Links: + +link:https://reviews.freebsd.org/D40370[D40370: Infrastructure for automatic jailing of rc.d-services] URL: link:https://reviews.freebsd.org/D40370[] + +link:https://reviews.freebsd.org/D40371[D40371: automatic service jails: some setup for full functionality of the services in automatic service jails] URL: link:https://reviews.freebsd.org/D40371[] +link:https://reviews.freebsd.org/D42779[D42779: Handbook / rc-article update for Service Jails] URL: link:https://reviews.freebsd.org/D42779[] + +Contact: Alexander Leidinger <netchild@FreeBSD.org> + +Service jails extend the man:rc[8] system to allow automatic jailing of rc.d services. +A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, ...) by default. +Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (man:vmm[4]). + +If you want to put e.g. local_unbound into a service jail and allow IPv4 and IPv6 access, simply change man:rc.conf[5] to have: +---- +local_unbound_svcj_options=net_basic +local_unbound_svcj=YES +---- +Note: all base system services are covered in the patches with either name_svcj_options or a hard-coded disabling of the service jails feature where it does not make sense (e.g. pure services which change the runtime configuration but do not start daemons, or where things are run which can not be run in a sensible way inside a jail). +As such the local_unbound_svcj_options line above is superfluous and serves just as an example about the amount of configuration needed in total. + +While this does not have the same security benefits as a manual jail setup with a separate filesystem and IP/VNET, it is much easier to set up, while providing some of the security benefits of a jail like hiding other processes of the same user. + +Since the link:../report-2023-04-2023-06/#_service_jailsautomatic_jailing_of_rc_d_services[previous service jails status report], the following were added: + +* support for NFS inside jails in the service jails framework (untested), +* the possibility of jailing other service commands than `start` and `stop`, +* service jails options / config for all base system services in the patch in D40371, +* a first step at documenting the service jails in the Handbook. + +Not all services are tested, but all services are covered with a config. + +Any testing and feedback (even as simple as "service X works in a service jail") is welcome. diff --git a/website/content/en/status/report-2023-10-2023-12/simd.adoc b/website/content/en/status/report-2023-10-2023-12/simd.adoc new file mode 100644 index 0000000000..533787f764 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/simd.adoc @@ -0,0 +1,20 @@ +=== SIMD enhancements for amd64 + +Links: + +link:https://freebsdfoundation.org/blog/a-sneak-peek-simd-enhanced-string-functions-for-amd64/[FreeBSD Foundation blog post] URL: link:https://freebsdfoundation.org/blog/a-sneak-peek-simd-enhanced-string-functions-for-amd64/[] + +link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[simd(7)] URL: link:https://man.freebsd.org/cgi/man.cgi?query=simd&sektion=7&manpath=FreeBSD+15.0-CURRENT[] + +link:https://github.com/clausecker/freebsd-src/commits/acceptance-testing[Work currently under acceptance testing] URL: link:https://github.com/clausecker/freebsd-src/commits/acceptance-testing[] + +Contact: Robert Clausecker <fuz@FreeBSD.org> + +The project to enhance the libc with SIMD implementations of string functions for amd64 has now concluded. +In total, SIMD implementations for 17 libc functions have been written, complemented by scalar implementations where needed. +Through this rewrite, performance of these functions on strings with an average length of 64 characters was improved by an average factor of 5.54. +In addition, 9 other library functions were rewritten to call into the SIMD-enhanced routines, conveying benefits without requiring additional assembly implementations. +Please see the FreeBSD Foundation blog post linked above for more details. + +Parts of the SIMD work are already found in the CURRENT branch. +The rest is currently undergoing acceptance testing and will be merged if no problems emerge. +It is planned to back port all improvements to 14-STABLE for inclusion into FreeBSD 14.1. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2023-10-2023-12/wiki.adoc b/website/content/en/status/report-2023-10-2023-12/wiki.adoc new file mode 100644 index 0000000000..9dee9803c1 --- /dev/null +++ b/website/content/en/status/report-2023-10-2023-12/wiki.adoc @@ -0,0 +1,16 @@ +=== FreeBSD Wiki + +Links: + +link:https://wiki.freebsd.org[Wiki] URL: link:https://wiki.freebsd.org[] + +Contact: Wiki administration <wiki-admin@FreeBSD.org> + +Plans are underway to familiarize our audience on Discord with the wiki (there are too many "silos" in our FreeBSD community). +Contact Setesh on the FreeBSD Discord for more information. + +Preliminary work is being done on updating the wiki software itself. +Continuing to run MoinMoin requires a jail with a downrev version of Python. +The MoinMoin project itself seems to have stalled in the middle of a redesign; at a minimum, a complete upgrade of the backend database would be needed. + +Alternatives that are under consideration include MediaWiki and DocuWiki; see link:https://wiki.freebsd.org/Wiki/NextGeneration[]. +Most of the discussion is occurring on Matrix; please contact wiki-admin@FreeBSD.org if you would like to participate. diff --git a/website/content/en/status/report-2024-01-2024-03/audio.adoc b/website/content/en/status/report-2024-01-2024-03/audio.adoc new file mode 100644 index 0000000000..29c5dc9aa2 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/audio.adoc @@ -0,0 +1,32 @@ +=== Audio Stack Improvements + +Contact: Christos Margiolis <christos@FreeBSD.org> + +The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement -- from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs. +This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature. + +So far, my focus has been towards the kernel side of the audio stack, with link:https://reviews.freebsd.org/D43545[D43545] being probably the most requested and notable patch. +I am also working on scrapping the rather outdated "snd_clone" audio device cloning framework of man:sound[4], and replacing it with DEVFS_CDEVPRIV(9) (link:https://reviews.freebsd.org/D44411[D44411]). + +Some of the future tasks include: + +* Attempt to find a better (ideally automatic) way to handle man:snd_hda[4] pin-patching. +* Implement an man:oss[3] library and man:audio[8] utility, in similar fashion to man:mixer[3] and man:mixer[8]. +* Write a bluetooth device management utility. +* Improve man:mixer[3] and man:mixer[8]. +* Improve documentation and test suite where needed. + +A more detailed description can be found link:https://lists.freebsd.org/archives/freebsd-multimedia/2023-December/002088.html[here]. + +You can also follow the development process in link:https://lists.freebsd.org/subscription/freebsd-multimedia[freebsd-multimedia@], where I post regular reports: + +* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-January/002158.html[Report #1] +* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-January/002179.html[Report #2] +* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-January/002209.html[Report #3] +* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-January/002229.html[Report #4] +* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-February/002248.html[Report #5] +* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-February/002252.html[Report #6] +* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-March/002273.html[Report #7] +* link:https://lists.freebsd.org/archives/freebsd-multimedia/2024-March/002286.html[Report #8] + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2024-01-2024-03/azure.adoc b/website/content/en/status/report-2024-01-2024-03/azure.adoc new file mode 100644 index 0000000000..a1e24f66e7 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/azure.adoc @@ -0,0 +1,32 @@ +=== 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 <bsdic@microsoft.com> + +Contact: link:https://lists.freebsd.org/subscription/freebsd-cloud[freebsd-cloud Mailing List] + +Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> + +Contact: Wei Hu <whu@FreeBSD.org> + +Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + + +In this quarter, we have solved all the blocking issues and published the link:https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-13_3[13.3-RELEASE on Azure Marketplace]. + +Work in progress tasks: + +* Automating the image building and publishing process and merging to [.filename]#src/release/#. +* Building and publishing snapshot builds to link:https://learn.microsoft.com/azure/virtual-machines/share-gallery-community[Azure community gallery]. + +The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft. + +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] +* Port link:https://github.com/Azure/azure-linux-extensions[Linux Virtual Machine Extensions for Azure] + +Sponsor: Microsoft for people in Microsoft, and for resources for the rest + +Sponsor: The FreeBSD Foundation for everything else 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 new file mode 100644 index 0000000000..44b96ae426 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/bhyve.adoc @@ -0,0 +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://www.youtube.com/watch?v=f60NCrunXyw[YouTube - vmstated explained] URL: link:https://www.youtube.com/watch?v=f60NCrunXyw[] + +Contact: Chris Moerz <freebsd@ny-central.org> + +==== 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/bsdinstall.adoc b/website/content/en/status/report-2024-01-2024-03/bsdinstall.adoc new file mode 100644 index 0000000000..757e2d0c8e --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/bsdinstall.adoc @@ -0,0 +1,66 @@ +=== Graphical Installer for FreeBSD + +Links: + +link:https://people.defora.org/~khorben/FreeBSD/bsdinstall/bsdinstall%20-%20Now%20with%20Graphics!%20-%20AsiaBSDCon%202024%20-%20WIP%20Session.pdf[Slides from AsiaBSDCon 2024] URL: link:https://people.defora.org/~khorben/FreeBSD/bsdinstall/bsdinstall%20-%20Now%20with%20Graphics!%20-%20AsiaBSDCon%202024%20-%20WIP%20Session.pdf[] + +link:https://github.com/khorben/gbsddialog[gbsddialog] URL: link:https://github.com/khorben/gbsddialog[] + +link:https://youtu.be/jm6byc7N2O4[preview video] URL: link:https://youtu.be/jm6byc7N2O4 + +Contact: Pierre Pronchery <pierre@freebsdfoundation.org> + +The first hurdle to overcome when testing a new Operating System is to get it installed. +What is more, the first impression new users gather from an Operating System is its installation process. +The state of the art for Operating System installers nowadays definitely involves a graphical process. +This is the case for mainstream systems but also for other UNIX systems comparable to link:https://www.freebsd.org[FreeBSD]: link:https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux[RedHat Enterprise Linux], link:https://ubuntu.com/[Ubuntu], https://www.debian.org[Debian GNU/Linux], or even link:https://www.devuan.org[Devuan GNU+Linux] +Regardless of the technical level of the actual user, this is how the platform will be compared in the public eye. + +In practice, FreeBSD has already been derived as a desktop-oriented Operating System by different projects. +Of these, I only found link:https://www.ghostbsd.org[GhostBSD] as a maintained project offering a graphical procedure to install the system. +The objective here was to consider a procedure that FreeBSD could adopt as part of its base system, in order to ship a graphical installer much like the current installer. +However, link:https://ghostbsd-documentation-portal.readthedocs.io/en/latest/user/installation-guide/custom-installation.html#installing-ghostbsd[GhostBSD's installer] relies on a Gtk+ interface driven with Python, implying a hefty footprint on the installation media when adopting FreeBSD's usual image generation procedure. +It would also imply importing and maintaining new projects into the ports tree. + +Instead, with knowledge of the current man:bsdinstall[8] and man:bsdconfig[8] utilities, I envisioned a BSD-licensed replacement for man:Xdialog[1]. +Just like when invoking bsdconfig with the -X switch for graphical mode, it could be dropped in instead of man:bsddialog[1] and allow graphical installation - while sharing the infrastructure of the current installer. +To avoid confusion with the current implementation of Xdialog from the x11/xdialog port, I have named its replacement man:gbsddialog[1]. +It also has to be said that Xdialog is quite obsolete (latest release in 2006) and this shows visually too. + +After creating a Proof-of-Concept prototype past the 14.0 release, I was provided with a 2-months window by the link:https://www.freebsdfoundation.org[FreeBSD Foundation], in order to complete a working implementation. +Thanks to a few shortcuts, I was glad to present the outcome of this effort during the WIP session of link:https://2024.asiabsdcon.org/program.html[AsiaBSDCon 2024], including a working graphical installer. + +Most of the necessary patches are already available for review in link:https://reviews.freebsd.org[FreeBSD's Phabricator]: + +* link:https://reviews.freebsd.org/D44279[D44279 bsdinstall: implement adduser with bsddialog] +* link:https://reviews.freebsd.org/D44280[D44280 bsdinstall: implement rootpass with bsddialog] +* link:https://reviews.freebsd.org/D44670[D44670 bsdinstall: implement timezone with bsddialog] +* link:https://reviews.freebsd.org/D44671[D44671 bsdinstall: allow forcing a specific partitioning mode] +* link:https://reviews.freebsd.org/D44672[D44672 bsdinstall: obtain the dialog binary from $DIALOG] +* link:https://reviews.freebsd.org/D44673[D44673 bsdinstall: handle command-line options in targets] +* link:https://reviews.freebsd.org/D44674[D44674 bsdinstall: add support for graphical mode] + +I have tried to keep these patches in growing order of friction expected before integration. + +The most important objective of this project was to improve bsdinstall, regardless of the success of this integration. +From the items above, it should be noted that D44279, D44280, D44670 are expecting to improve the general look & feel of the installer, even while in text mode. +Similarly, D44671 and D44672 improve the overall versatility of the installer when scripted or customized. +D44673 and D44674 bring it on par with bsdconfig -X, even allowing the graphical installation of jails. + +Some parts are still missing, or made use of shortcuts still unsuitable for integration: + +* The "fetchmissingdists" target was avoided by shipping every component on the installation media; +* The "checksum" and "extract" targets had to be re-implemented with simpler code, degrading the user experience also with the regular installer; +* Creation of the installation media generates an additional, heavy image (almost 8 GB), and is suspected to be hindered by a bug in man:makefs[8]. + +The corresponding code can be found in my link:https://github.com/khorben/freebsd-src/[GitHub fork] in the link:https://github.com/khorben/freebsd-src/tree/khorben/bsdinstall-graphical4[khorben/bsdinstall-graphical4] branch. +As can be guessed from the branch name, depending on the complexity of rebasing operations, combined with the (hopefully) progressive integration of the changes proposed, new branches may be added to keep track of the progress. +(In fact a link:https://github.com/khorben/freebsd-src/tree/khorben/bsdinstall-graphical5[khorben/bsdinstall-graphical5] branch already exists.) + +Still, a lot needs to be done for the installer to reach a new level of maturity overall. +While working on this project, I have received general complaints on the installer, and calls for a complete rewrite. +It is true that the current code base suffers from a number of issues and limitations. +The lack of a graphical installer is one of many symptoms, which range from the lack of recovery from errors, of navigability to previous steps, of a general vision of the installation progress, or of a network-based installer. +In the meantime, this is the installer we have and are familiar with, and I think it can still be saved and improved. + +Special thanks go to Ed Maste and Joe Mingrone for the opportunity, and to Philippe Audeoud, Tobias Berner, Olivier Certner, Jessica Clarke, Olivier Cochard-Labbe, Baptiste Daroussin, Brad Davis, Michael Dexter, Li-Wen Hsu, Mateusz Piotrowski, Alfonso Siciliano, Emmanuel Vadot, and Robert Watson for the feedback, reviews, and encouragements. +(If I missed anyone, you know I did not mean to!) + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2024-01-2024-03/ci.adoc b/website/content/en/status/report-2024-01-2024-03/ci.adoc new file mode 100644 index 0000000000..72ed57b362 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/ci.adoc @@ -0,0 +1,51 @@ +=== Continuous Integration + +Links: + +link:https://ci.FreeBSD.org[FreeBSD Jenkins Instance] URL: link:https://ci.FreeBSD.org[] + +link:https://tinderbox.freebsd.org[FreeBSD CI Tinderbox view] URL: link:https://https://tinderbox.freebsd.org[] + +link:https://artifact.ci.FreeBSD.org[FreeBSD CI artifact archive] URL: link:https://artifact.ci.FreeBSD.org[] + +link:https://wiki.FreeBSD.org/HostedCI[Hosted CI wiki] URL: link:https://wiki.FreeBSD.org/HostedCI[] + +link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rd Party Software CI] URL: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[] + +link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[Tickets related to freebsd-testing@] URL: link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[] + +link:https://github.com/freebsd/freebsd-ci[FreeBSD CI Repository] URL: link:https://github.com/freebsd/freebsd-ci[] + +link:https://lists.FreeBSD.org/subscription/dev-ci[dev-ci Mailing List] URL: link:https://lists.FreeBSD.org/subscription/dev-ci[] + +Contact: Jenkins Admin <jenkins-admin@FreeBSD.org> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +Contact: link:https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing[freebsd-testing Mailing List] + +Contact: IRC #freebsd-ci channel on EFNet + +In the first quarter of 2024, we worked with the project contributors and developers to address their testing requirements. +Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. + +Important completed tasks: + +* With help from clusteradm, the host running test VMs had disk and memory upgraded by reusing the parts of decommissioned machines. +* Update the build environment of stable/13 jobs to 13.3-RELEASE. +* Turn i386 build on main branch to use cross build on amd64. + +Work in progress tasks: + +* Merging link:https://reviews.freebsd.org/D43786[] +* Merging link:https://reviews.freebsd.org/D36257[] +* Adding new hardware purchased by the FreeBSD Foundation to the CI cluster +* Designing and implementing pre-commit CI building and testing and pull/merge-request based system (to support the link:https://gitlab.com/bsdimp/freebsd-workflow[workflow working group]) + * Proof of concept system is in progress. +* Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds +* Simplifying CI/test environment setting up for contributors and developers +* Setting up the CI stage environment and putting the experimental jobs on it +* Redesigning the hardware test lab and adding more hardware for testing + +Open or queued tasks: + +* Collecting and sorting link:https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo[CI tasks and ideas] +* Setting up public network access for the VM guest running tests +* Implementing use of bare-metal hardware to run test suites +* Adding drm ports building tests against -CURRENT +* Planning to run ztest tests +* Helping more software get FreeBSD support in its CI pipeline (Wiki pages: link:https://wiki.FreeBSD.org/3rdPartySoftwareCI[3rdPartySoftwareCI], link:https://wiki.FreeBSD.org/HostedCI[HostedCI]) +* Working with hosted CI providers to have better FreeBSD support + +Please see link:https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals[freebsd-testing@ related tickets] for more WIP information, and do not hesitate to join the effort! + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2024-01-2024-03/cloud-init.adoc b/website/content/en/status/report-2024-01-2024-03/cloud-init.adoc new file mode 100644 index 0000000000..1410966cf0 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/cloud-init.adoc @@ -0,0 +1,34 @@ +=== FreeBSD as a Tier 1 cloud-init Platform + +Links: + +link:https://cloud-init.io/[cloud-init Website] URL: link:https://cloud-init.io/[] + +link:https://cloudinit.readthedocs.io/en/latest/[cloud-init Documentation] URL: link:https://cloudinit.readthedocs.io/en/latest/[] + + +Contact: Mina Galić <freebsd@igalic.co> + +cloud-init is the standard way of provisioning servers in the cloud. +Over the past year and a half, thanks to this FreeBSD support has steadily improved. +This year, together with cloud-init developers and the FreeBSD Foundation, we decided to explicitly focus on making improvements in FreeBSD itself, that will aid the cloud-init team to test future changes to FreeBSD code-paths themselves. +To achieve this goal, I need to make FreeBSD run in LXD (and Incus), under the control of ``lxd-agent`` (or ``incus-agent``). + +Here are some improvements from the recent weeks: + +- I have written a small link:https://codeberg.org/meena/test-cloud-init[testing-framework] (in sh, and I'm slowly porting it to OpenTofu/Terraform), which installs the latest version of package:net/cloud-init-devel[] or package:net/cloud-init[] and runs a couple of standard cloud-init tests. +- To do this, I have created a link:https://pkg.igalic.co/[dedicated public repository] which contains the latest versions of package:net/cloud-init-devel[] and package:net/cloud-init[] for FreeBSD 13 and 14 on amd64 and aarch64. +- I have link:https://codeberg.org/meena/vsock-tests[ported Linux's vsock testing framework to FreeBSD] +- I created a driver skeleton for a link:https://codeberg.org/meena/freebsd-src/src/branch/vsock/sys/dev/virtio/socket[VirtIO Socket driver], based on the HyperV Socket driver. +- In doing so, I made numerous link:https://reviews.freebsd.org/D44517[improvements to HyperV sockets], some of which are accepted, others still need more work. +- I have tested and released the latest 24.1 series cloud-init, where the cloud-init team and I have finally fixed some longstanding bugs, such as link:https://github.com/canonical/cloud-init/pull/4820[moving ``/run/cloud-init``] to [.filename]#/var/run/cloud-init# on BSD, as well as fixing the link:https://github.com/canonical/cloud-init/pull/5061[``homedir`` argument] to ``user_groups`` to actually do something. +- This release also sees numerous fixes to the OpenBSD code-paths from the community and not just me. +- I have also started an official port for OpenBSD, but link:https://marc.info/?l=openbsd-ports&m=170508174230708&w=2[that work has stalled]. + +The work to come, in broad strokes: + +- Finish the FreeBSD VirtIO Socket driver. +- Fix Go's runtime to support VirtIO on FreeBSD. +- Port lxd-agent's dependencies to FreeBSD. +- Port lxd-agent to FreeBSD. + +That work will be interspersed with more improvements to cloud-init on BSDs, and more tests on different cloud providers. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2024-01-2024-03/core.adoc b/website/content/en/status/report-2024-01-2024-03/core.adoc new file mode 100644 index 0000000000..5bec85a164 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/core.adoc @@ -0,0 +1,25 @@ +=== FreeBSD Core Team + +Contact: FreeBSD Core Team <core@FreeBSD.org> + +The FreeBSD Core Team is the governing body of FreeBSD. + +==== 13.3-RELEASE + +FreeBSD 13.3 was released on March 5th, 2024. + +The release announcement is at: + + link:https://www.freebsd.org/releases/13.3R/announce/[] + +Along the release engineering team, the project dedicates the 13.3-RELEASE to Glen Barber, with thanks for his many years of contributions as Release Engineer. + +==== Future of 32-bit platform support + +Core announced link:https://lists.freebsd.org/archives/freebsd-announce/2024-February/000117.html[Future of 32-bit platform support in FreeBSD] for deprecating 32-bit platforms over the next couple of major +releases. + +==== Commit bits + +* Core approved the src commit bit for Bojan Novković (bnovkov@) +* Core reactivated the src commit bits for Mark Peek (mp@),Mark Murray (markm@), and Lawrence Stewart (lstewart@) diff --git a/website/content/en/status/report-2024-01-2024-03/doceng.adoc b/website/content/en/status/report-2024-01-2024-03/doceng.adoc new file mode 100644 index 0000000000..0baa834595 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/doceng.adoc @@ -0,0 +1,61 @@ +//// +Quarter: 1st quarter of 2024 +Prepared by: fernape +Reviewed by: carlavilla +Last edit: $Date$ +Version: $Id:$ +//// + +=== 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[] + +Contact: FreeBSD Doceng Team <doceng@FreeBSD.org> + +The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see link:https://www.freebsd.org/internal/doceng/[FreeBSD Doceng Team Charter]. + +During the last quarter: + +trasz@'s doc commit bit was taken for safekeeping. +trhodes@'s doc commit bit was taken for safekeeping. + +==== 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/Weblateurl[] + +Link: link:https://translate-dev.freebsd.org/[FreeBSD Weblate Instance] URL: link:https://translate-dev.freebsd.org/url[] + +===== Q1 2024 Status + +* 17 team languages +* 189 registered users + +Three new translators joined Weblate: + +* piker3 in Polish team (pl) +* chrislongros in Greek team (el) +* grip in Italian team (it_IT) + +===== Languages + +* Chinese (Simplified) (zh-cn) (progress: 7%) +* Chinese (Traditional) (zh-tw) (progress: 3%) +* Dutch (nl) (progress: 1%) +* French (fr) (progress: 1%) +* German (de) (progress: 1%) +* Greek (el) (progress: 1%) +* Indonesian (id) (progress: 1%) +* Italian (it) (progress: 5%) +* Korean (ko) (progress: 32%) +* Norwegian (nb-no) (progress: 1%) +* Persian (fa-ir) (progress: 3%) +* Polish (progress: 2%) +* Portuguese (progress: 0%) +* Portuguese (pt-br) (progress: 22%) +* Spanish (es) (progress: 36%) +* Turkish (tr) (progress: 2%) + +We want to thank everyone that contributed, translating or reviewing documents. + +And please, help promote this effort on your local user group, we always need more volunteers. 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 new file mode 100644 index 0000000000..87cf09e0a1 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc @@ -0,0 +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 <deb@FreeBSDFoundation.org> + +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. + +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 new file mode 100644 index 0000000000..5abd4feebc --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/freshports.adoc @@ -0,0 +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 <dvl@FreeBSD.org> + +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. +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/gcc.adoc b/website/content/en/status/report-2024-01-2024-03/gcc.adoc new file mode 100644 index 0000000000..1f39cb172e --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/gcc.adoc @@ -0,0 +1,25 @@ +=== GCC on FreeBSD + +Links: + +link:https://gcc.gnu.org/[GCC Project] URL: link:https://gcc.gnu.org/[] + +link:https://gcc.gnu.org/gcc-10/[GCC 10 release series] URL: link:https://gcc.gnu.org/gcc-10/[] + +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/[] + +Contact: Lorenzo Salvadore <salvadore@FreeBSD.org> + +link:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273397[Updating GCC default version to 13] is finally finished. +Thanks to mailto:antoine@FreeBSD.org[Antoine Brodin] who ran the exp-runs and to all other developers and ports maintainers involved. + +As promised in the preceding report, the next goal is to reduce the number of open bugs for GCC ports. +Some work on existing bugs has already started. + +In particular, package:lang/gcc14-devel[] has long stayed out of date due to some issues with building the port without any BOOTSTRAP option. +Thanks to the help of other developers and contributors (a special thank to Mark Millard), I noticed that according to the official documentation link:https://gcc.gnu.org/install/prerequisites.html[building GCC without bootstrap requires a working GCC binary] and thus I switched package:lang/gcc14-devel[] to require that a BOOTSTRAP option is set. +However it has later been stated that bootstrapping GCC using clang and libc++ is link:https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632[officially supported]. +But it has also been stated that this is not a high priority. + +At the moment package:lang/gcc14-devel[] is the only GCC port requiring a BOOTSTRAP option to be set. +The plan is to have all GCC ports for versions greater or equal than 14 (i.e. future GCC ports) to require such an option: even if building without bootstrap is more or less officially supported, being low priority for upstream it increases the burden of maintaining GCC ports for low results. +In case lower versions start to have issues building without bootstrap, I am going to require bootstrap for those as well. 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 new file mode 100644 index 0000000000..46275eb7aa --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/libsys.adoc @@ -0,0 +1,41 @@ +=== libsys + +Contact: Brooks Davis <brooks@FreeBSD.org> + +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 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. + +==== 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/openstack.adoc b/website/content/en/status/report-2024-01-2024-03/openstack.adoc new file mode 100644 index 0000000000..367b4a7d12 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/openstack.adoc @@ -0,0 +1,24 @@ +=== OpenStack on FreeBSD + +Links: + +link:https://www.openstack.org/[OpenStack] URL: link:https://www.openstack.org/[] + +link:https://github.com/openstack-on-freebsd[OpenStack on FreeBSD] URL: link:https://github.com/openstack-on-freebsd[] + +Contact: Chih-Hsin Chang <starbops@hey.com> + +Contact: Li-Wen Hsu <lwhsu@FreeBSD.org> + +The OpenStack on FreeBSD project aims to seamlessly integrate OpenStack cloud infrastructure with the FreeBSD operating system. +It uses FreeBSD's unique features while ensuring compatibility with OpenStack standards. + +In the first quarter of 2024, we made significant progress on the OpenStack on FreeBSD project. +This included submitting a proposal for BSDCan 2024 and attending AsiaBSDCon 2024 to link:https://papers.freebsd.org/2024/asiabsdcon/chang-towards-a-robust-freebsd-based-cloud-porting-openstack-components/[share our porting experiences and gain exposure for the project]. +The feedback received at AsiaBSDCon was particularly valuable and helped in refining the project's direction. +During this period, we also reviewed the project's phase 1 tasks and made necessary adjustments. +We also planned for phases 2 and 3, aligning them with the project's long-term goals. +One technical achievement was verifying the functionality of bhyve serial console over TCP, an important part of the project's infrastructure. +Additionally, we created a link:https://asciinema.org/a/647308[demo video] showcasing the project's progress and features. + +Looking ahead, our focus for the next quarter includes confirming the feasibility of implementing FreeBSD privilege-management user space tools leveraging man:mac[4] and man:priv[9], simplifying installation steps by transitioning to FreeBSD ports, and porting OpenStack Ironic to FreeBSD. +These tasks will enhance the project's capabilities and compatibility. + +Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2024-01-2024-03/packagekit.adoc b/website/content/en/status/report-2024-01-2024-03/packagekit.adoc new file mode 100644 index 0000000000..5757fdde1e --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/packagekit.adoc @@ -0,0 +1,12 @@ +=== PackageKit backend for FreeBSD pkg + +Contact: Gleb Popov <arrowd@FreeBSD.org> + +PackageKit is a small D-Bus daemon program that serves as a backend for "application store" type of apps - most notably Plasma Discover and Gnome Software Center. +The latest PackageKit release features a libpkg backend, which means that you can now use PackageKit-enabled programs on FreeBSD to manage software. +Plasma Discover is already switched to using PackageKit, so you will get it working out of the box once you update your ports/packages. + +If you observe any crashes or bugs in PackageKit please let me know by link:https://github.com/PackageKit/PackageKit/issues[opening an issue upstream]. +If you are interested in contributing, there is a lot of work to do too! + +Sponsor: Serenity Cybersecurity, LLC diff --git a/website/content/en/status/report-2024-01-2024-03/portmgr.adoc b/website/content/en/status/report-2024-01-2024-03/portmgr.adoc new file mode 100644 index 0000000000..f8a65f4472 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/portmgr.adoc @@ -0,0 +1,59 @@ +=== 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 <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. +Below is what happened in the last quarter. + +According to INDEX, there are currently 32,244 ports in the Ports Collection. +There are currently ~3,300 open ports PRs. +The last quarter saw 12,991 commits by 158 committers on the main branch and 888 commits by 61 committers on the 2024Q1 branch. +Compared to last quarter, this means a large increase in the number of commits on the main branch (up from 9,424) and slightly more backports to the quarterly branch (up from 781). +The number of ports also increased (up from 31,942). + +In Q1 there were around 14,127 commits to main: +The most active committers were: +2934 sunpoet +2676 bofh +1297 yuri +748 eduardo +545 jbeich +347 arrowd +233 diizzy +195 yasu +170 ehaupt +164 wen + +A lot has happened in the ports tree in the last quarter, an excerpt of the major software upgrades are: +- pkg 1.21.0 +- New USES: ocaml +- Default version of gcc switched to 13 +- Default version of ruby switched to 3.2 +- Default version of lazarus switched to 3.2.0 +- Default version of go switched to 1.21 +- Chromium updated to 123.0.6312.105 +- Electron-28 updated to 28.2.10 +- Electron-27 updated to 27.3.9 +- Firefox updated to 124.0.2 +- Firefox-esr updated to 115.9.1 +- KDE updated to Frameworks 5 5.115, Frameworks 6 to 6.0.0 Plasma Desktop 5 to 5.27.11, Plasma Desktop 6 to 6.0.2 +- Qt5 updated to 5.15.13 +- Qt6 updated to 6.6.3 +- Python updated to 3.11.9, 3.10.14 and 3.8.10 +- Ruby updated to 3.2.3 +- Rust updated to 1.77.0 +- SDL updated to 2.30.2 +- Sway updated to 1.9 +- wlroots updated to 1.17.2 +- Wine updated to 9.0 +- Xorg server updated to 0.17.2 + + +During the last quarter, pkgmgr@ ran 17 exp-runs to test various ports upgrades, updates to default versions of ports, subpackage support and base system changes. 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 new file mode 100644 index 0000000000..dc41c68822 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/pot.adoc @@ -0,0 +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) <pizzamig@FreeBSD.org> + +Contact: Bretton Vine (Potluck) <bv@honeyguide.eu> + +Contact: Michael Gmelin (Potman) <grembo@FreeBSD.org> + +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]. + +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/releng.adoc b/website/content/en/status/report-2024-01-2024-03/releng.adoc new file mode 100644 index 0000000000..15a4febc98 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/releng.adoc @@ -0,0 +1,16 @@ +=== FreeBSD Release Engineering Team + +Links: + +link:https://www.freebsd.org/releases/13.3R/announce/[FreeBSD 13.3-RELEASE announcement] URL: link:https://www.freebsd.org/releases/13.3R/announce/[] + +link:https://www.freebsd.org/releases/14.1R/schedule/[FreeBSD 14.1-RELEASE schedule] URL: link:https://www.freebsd.org/releases/14.1R/schedule/[] + +link:https://download.freebsd.org/releases/ISO-IMAGES/[FreeBSD releases] URL: link:https://download.freebsd.org/releases/ISO-IMAGES/[] + +link:https://download.freebsd.org/snapshots/ISO-IMAGES/[FreeBSD development snapshots] URL: link:https://download.freebsd.org/snapshots/ISO-IMAGES/[] + +Contact: FreeBSD Release Engineering Team, <re@FreeBSD.org> + +The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. + +During the first quarter of the year, the Team managed 13.3-RELEASE, leading to the final RELEASE build and announcement in March. +Planning has started for the upcoming 14.1-RELEASE cycle. + +The Release Engineering Team continued providing weekly development snapshot builds for the *main*, *stable/14*, and *stable/13* branches. diff --git a/website/content/en/status/report-2024-01-2024-03/ten64-whle-honeycomb.adoc b/website/content/en/status/report-2024-01-2024-03/ten64-whle-honeycomb.adoc new file mode 100644 index 0000000000..2cd21e9767 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/ten64-whle-honeycomb.adoc @@ -0,0 +1,37 @@ +=== Ten64, WHLE-LS1, and HoneyComb + +Links: + +link:https://wiki.freebsd.org/BjoernZeeb/[My wiki page with links to some status] URL: link:https://wiki.freebsd.org/BjoernZeeb/[] + + +Contact: Bjoern A. Zeeb <bz@FreeBSD.ORG> + +Solid-Run's HoneyComb, Traverse Technologies's Ten64 and some versions of Conclusive Engineering's WHLE-LS1 all are NXP based platforms with the Data Path Acceleration Architecture Gen2 (DPAA2). + +Work has happened to support or improve support for peripherals on these boards. + +For DPAA2 I have local changes which will need review (or further discussion): +* Cleanup of memac (MDIO) code reducing bus attachment (ACPI and FDT specific) code into more common code. +* Cleanup of MC bus attachment code (again ACPI, FDT). +* For reasons of mii_fdt.c support on some PHYs on FDT-based platforms restructure MAC/MII code and mostly migrate it out of the network interface (NI). +* Improve Dmitry Salychev's (dsl) initial SFF/SFP code, prototyping a bus similar to MII for SFP with the hope that with more work it can grow into a larger, general FreeBSD framework and hooked it up to DPMAC. +* With this, minimal support (still fairly hacked up) for "managed" SFP+ mode (using the Ten64 terminology) is usable on FDT-based systems using DAC and fiber cables. +* Add more sysctl statistics to DPMAC and NI. +In short, I mostly cleaned up some of the mess I contributed to during the initial bring-up. + +For the LS1088a based WHLE-LS1 systems changes include: +* device-tree file updates. +* Added support for the PCA9546 I2C Switch (committed). +* Added basic support for the PCAL6524 24-bit Fm+ I2C-bus/SMBus I/O expander. +* Added basic support for the PCA9633 4-bit Fm+ I2C-bus LED driver to drive the status LEDs. +* Added support to program the man:rgephy[4] LEDs (which needs to be validated). +* Started testing the eMMC with MMCCAM and GENERIC but had trouble (needs further investigation, seemed fine from firmware for updates). +* Tested one of three PCIe slots and USB fine. + +For the Ten64: +* Most of the basic lifting happened a while ago and it has generally been usable. +* Detecting the VSC8514 PHY as such went in end of last year. +* Used as the default platform to test the DPAA2 changes and SFP/SFP+ code. + +In addition Pierre-Luc Drouin has overhauled the Vybrid I2C support now attaching and working on both FDT- and ACPI-based systems (committed). + +Sponsor: Traverse Technologies (Ten64 hardware a while ago, support) diff --git a/website/content/en/status/report-2024-01-2024-03/valgrind.adoc b/website/content/en/status/report-2024-01-2024-03/valgrind.adoc new file mode 100644 index 0000000000..1d2ed9d039 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/valgrind.adoc @@ -0,0 +1,34 @@ +=== Valgrind: port to arm64 on its way + +Links: + +link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[] + +link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[] +link:https://github.com/paulfloyd/freebsdarm64_valgrind[arm64 port] URL: link:https://github.com/paulfloyd/freebsdarm64_valgrind[] + +Contact: Paul Floyd <pjfloyd@wanadoo.fr> + +The major news, as per the title, is that a port to FreeBSD arm64 (or aarch64) is now ready. +The next steps are to get it reviewed and pushed upstream. + +Valgrind 3.23 is due out at the end of April 2024 and package:devel/valgrind[] will be updated shortly after that. + +package:devel/valgrind-devel[] will get an update as soon as I have pushed the changes for arm64. + +`--track-fds=yes` now checks for and warns about attempts to close a file descriptor more than once. +Handling of closefrom has been improved to use this feature. + +There are some important fixes for FreeBSD 15, in particular handling the new `libsys`. + +Here is a list of smaller bugfixes: + +* Support for FreeBSD 13.3 has been added. +* Added a redirect for `reallocarray`. +* Several fixes for `aio*` functions. +* Added a redirect for `memccpy`. +* There is a fix for `_umtx_op OP_ROBUST_LISTS`. +* Added redirects for C23 `free_sized` and `free_aligned_sized`. +* Correctly propagate the ELF stack protection flags to the guest stack that Valgrind synthesizes. +* Fixes for `--sanity-level-3` and above (only used for Valgrind self-testing at runtime). +* Several fixes to checking done for `semctl`. +* Fixed argument checking for `utrace`. +* Fixed argument checking for `clock_nanosleep`. 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 new file mode 100644 index 0000000000..0f77129009 --- /dev/null +++ b/website/content/en/status/report-2024-01-2024-03/wireless.adoc @@ -0,0 +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 <bz@FreeBSD.org> + +Contact: The FreeBSD wireless mailing list <wireless@FreeBSD.org> + +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]. +That way everyone will see, be able to join in, and the answers will be publicly archived. + +Sponsor: minipci.biz (BE200 hardware) |