1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
|
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:db="http://docbook.org/ns/docbook">
<head>
<title>FreeBSD Quarterly Status Report</title>
<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" />
</head>
<body>
<div id="containerwrap">
<div id="container">
<span class="txtoffscreen"><a href="#content" title="Skip site navigation" accesskey="1">Skip site navigation</a> (1)
<a href="#contentwrap" title="Skip section navigation" accesskey="2">Skip section navigation</a> (2)
</span>
<div id="headercontainer">
<div id="header">
<h2 class="blockhide">Header And Logo</h2>
<div id="headerlogoleft">
<a href="../.." title="FreeBSD">
<img src="../../layout/images/logo-red.png" width="457" height="75" alt="FreeBSD" />
</a>
</div>
<div id="headerlogoright">
<div class="frontdonateroundbox">
<div class="frontdonatetop">
<div>
<b style="display: none;">.</b>
</div>
</div>
<div class="frontdonatecontent">
<a href="https://www.FreeBSDFoundation.org/donate/">Donate to FreeBSD</a>
</div>
<div class="frontdonatebot">
<div>
<b style="display: none;">.</b>
</div>
</div>
</div>
<h2 class="blockhide">Peripheral Links</h2>
<div id="searchnav">
<ul id="searchnavlist"></ul>
</div>
<div id="search">
<form method="get" id="search-form" action="https://duckduckgo.com/" onsubmit="document.getElementById('words').value+=' (site:www.FreeBSD.org OR site:docs.FreeBSD.org OR site:lists.FreeBSD.org OR site:wiki.FreeBSD.org OR site:forums.FreeBSD.org)'">
<h2 class="blockhide">
<label for="words">Search</label>
</h2>
<input type="hidden" name="ka" value="v" />
<input type="hidden" name="kt" value="v" />
<input type="hidden" name="kh" value="1" />
<input type="hidden" name="kj" value="r2" />
<input id="words" name="q" type="text" size="20" maxlength="255" onfocus="if( this.value==this.defaultValue ) this.value='';" value="Search" />
<span> </span>
<input id="submit" name="submit" type="submit" value="Search" />
</form>
</div>
</div>
</div>
<h2 class="blockhide">Site Navigation</h2>
<div id="menu">
<ul class="first">
<li>
<a href="../../">Home</a>
</li>
</ul>
<ul>
<li>
<a href="../../about.html">About</a>
<ul>
<li>
<a href="../../projects/newbies.html">Introduction</a>
</li>
<li>
<a href="../../features.html">Features</a>
</li>
<li>
<a href="../../advocacy/">Advocacy</a>
</li>
<li>
<a href="../../marketing/">Marketing</a>
</li>
<li>
<a href="../../privacy.html">Privacy Policy</a>
</li>
</ul>
</li>
</ul>
<ul>
<li>
<a href="../../where.html">Get FreeBSD</a>
<ul>
<li>
<a href="../../releases/">Release Information</a>
</li>
<li>
<a href="../../releng/">Release Engineering</a>
</li>
</ul>
</li>
</ul>
<ul>
<li>
<a href="../../docs.html">Documentation</a>
<ul>
<li>
<a href="../../doc/en_US.ISO8859-1/books/faq/">FAQ</a>
</li>
<li>
<a href="../../doc/en_US.ISO8859-1/books/handbook/">Handbook</a>
</li>
<li>
<a href="../../doc/en_US.ISO8859-1/books/porters-handbook">Porter's Handbook</a>
</li>
<li>
<a href="../../doc/en_US.ISO8859-1/books/developers-handbook">Developer's Handbook</a>
</li>
<li>
<a href="//www.FreeBSD.org/cgi/man.cgi">Manual Pages</a>
</li>
<li>
<a href="https://papers.FreeBSD.org">Presentations and Papers</a>
</li>
<li>
<a href="../../doc/en_US.ISO8859-1/books/fdp-primer">Documentation Project Primer</a>
</li>
<li>
<a href="../../docs/books.html">All Books and Articles</a>
</li>
</ul>
</li>
</ul>
<ul>
<li>
<a href="../../community.html">Community</a>
<ul>
<li>
<a href="../../community/mailinglists.html">Mailing Lists</a>
</li>
<li>
<a href="https://forums.FreeBSD.org">Forums</a>
</li>
<li>
<a href="../../usergroups.html">User Groups</a>
</li>
<li>
<a href="../../events/events.html">Events</a>
</li>
<li>
<a href="http://freebsdjournal.com">FreeBSD Journal</a>
</li>
<li>
<a href="http://serverfault.com/questions/tagged/freebsd">Q&A (external)</a>
</li>
</ul>
</li>
</ul>
<ul>
<li>
<a href="../../projects/index.html">Developers</a>
<ul>
<li>
<a href="https://wiki.FreeBSD.org/IdeasPage">Project Ideas</a>
</li>
<li>
<a href="https://cgit.FreeBSD.org">Git Repository</a>
</li>
<li>
<a href="https://svnweb.FreeBSD.org">Subversion Repository</a>
</li>
<li>
<a href="https://github.com/freebsd">GitHub Mirror</a>
</li>
<li>
<a href="https://reviews.FreeBSD.org">Code Review (Phabricator)</a>
</li>
<li>
<a href="https://wiki.FreeBSD.org">Wiki</a>
</li>
<li>
<a href="https://ci.FreeBSD.org">Continuous Integration Service</a>
</li>
</ul>
</li>
</ul>
<ul>
<li>
<a href="../../support.html">Support</a>
<ul>
<li>
<a href="../../commercial/commercial.html">Vendors</a>
</li>
<li>
<a href="../../security/">Security Information</a>
</li>
<li>
<a href="https://bugs.FreeBSD.org/search/">Bug Reports</a>
</li>
<li>
<a href="https://www.FreeBSD.org/support.html">Submitting Bug Reports</a>
</li>
</ul>
</li>
</ul>
<ul>
<li>
<a href="https://www.freebsdfoundation.org/">Foundation</a>
<ul>
<li>
<a href="https://www.freebsdfoundation.org/donate/">Monetary Donations</a>
</li>
<li>
<a href="../../donations/index.html#systems">Hardware Donations</a>
</li>
</ul>
</li>
</ul>
</div>
</div>
<div id="content">
<div id="sidewrap">
<div id="sidenav">
<h2 class="blockhide">Section Navigation</h2>
<ul>
<li>
<a href="../../about.html">About</a>
</li>
<li>
<a href="../../features.html">Features</a>
</li>
<li>
<a href="../../applications.html">Applications</a>
</li>
<li>
<a href="../../advocacy/">Advocacy</a>
</li>
<li>
<a href="../../marketing/">Marketing</a>
</li>
<li>
<a href="../../administration.html">Administration</a>
</li>
<li>
<a href="../../news/newsflash.html">News</a>
</li>
<li>
<a href="../../events/events.html">Events</a>
</li>
<li>
<a href="../../news/press.html">Press</a>
</li>
<li>
<a href="../../multimedia/multimedia.html">Multimedia</a>
</li>
<li>
<a href="../../art.html">Artwork</a>
</li>
<li>
<a href="../../logo.html">Logo</a>
</li>
<li>
<a href="../../donations/">Donations</a>
</li>
<li>
<a href="../../copyright/">Legal Notices</a>
</li>
<li>
<a href="../../privacy.html">Privacy Policy</a>
</li>
</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
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
inaccessible, added preliminary support for Bluetooth Low Energy, a introduction to the
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
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.
</p><p>We hope you find the report as interesting as we have,<br clear="none" />
Daniel Ebdrup Jensen (debdrup@), on behalf of the quarterly team.
</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Foundation">FreeBSD Foundation</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Cluster-Administration-Team">Cluster Administration Team</a></li><li><a href="#Continuous-Integration">Continuous Integration</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#FreeBSD-Office-Hours">FreeBSD Office Hours</a></li><li><a href="#Quarterly-Status-Reports-Team">Quarterly Status Reports Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></li><li><a href="#Git-Migration-Working-Group">Git Migration Working Group</a></li><li><a href="#Lua-Usage-in-FreeBSD">Lua Usage in FreeBSD</a></li><li><a href="#Linux-compatibility-layer-update">Linux compatibility layer update</a></li><li><a href="#NFS-over-TLS-implementation">NFS over TLS implementation</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#SoC-audio-framework-and-more-audio-drivers">SoC audio framework and more audio drivers</a></li><li><a href="#bhyve---NVMe-emulation-improvements">bhyve - NVMe emulation improvements</a></li><li><a href="#Bluetooth-Support">Bluetooth Support</a></li><li><a href="#DRM-Drivers-Update">DRM Drivers Update</a></li><li><a href="#DTS-Update">DTS Update</a></li><li><a href="#ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></li><li><a href="#Forcible-Unmount-of-UFS/FFS-Filesystems-on-Disk-Failure">Forcible Unmount of UFS/FFS Filesystems on Disk Failure</a></li><li><a href="#i.MX-8M-support">i.MX 8M support</a></li><li><a href="#Intel-wireless-and-11ac-update">Intel wireless and 11ac update</a></li><li><a href="#amd64-5-Level-Paging-Structures-support">amd64 5-Level Paging Structures support</a></li><li><a href="#Not-transparent-superpages">Not-transparent superpages</a></li><li><a href="#NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></li><li><a href="#amd64-pmap-Fine-grained-pv-lists-locking">amd64 pmap Fine-grained pv lists locking</a></li><li><a href="#Lockless-routing-lookups-and-scalable-multipath">Lockless routing lookups and scalable multipath</a></li><li><a href="#ZSTD-Compression-in-ZFS">ZSTD Compression in ZFS</a></li><li><a href="#CheriBSD-2020-Q2">CheriBSD 2020 Q2</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#Continuous-Integration-on-!x86">Continuous Integration on !x86</a></li><li><a href="#FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Import-of-new-implementation-of-bc-and-dc">Import of new implementation of bc and dc</a></li><li><a href="#Binutils-Retirement">Binutils Retirement</a></li><li><a href="#Run-Time-Dynamic-Linker-improvements">Run-Time Dynamic Linker improvements</a></li><li><a href="#VHDX-support-in-mkimg(1)">VHDX support in mkimg(1)</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#Bastille">Bastille</a></li><li><a href="#KDE-on-FreeBSD">KDE on FreeBSD</a></li><li><a href="#Haskell-on-FreeBSD">Haskell on FreeBSD</a></li><li><a href="#rtsx---Porting-driver-for-Realtek-SD-card-reader-from-OpenBSD">rtsx - Porting driver for Realtek SD card reader from OpenBSD</a></li><li><a href="#Valgrind-updates">Valgrind updates</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#FreeBSD-Translations-on-Weblate">FreeBSD Translations on Weblate</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#FreshPorts">FreshPorts</a></li><li><a href="#PCI-passthrough-with-bhyve-on-Intel-and-for-OpenBSD-guests">PCI passthrough with bhyve on Intel and for OpenBSD guests</a></li><li><a href="#SageMath">SageMath</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#chaifi---a-tool-to-simplify-joining-public-WiFi-networks">chaifi - a tool to simplify joining public WiFi networks</a></li><li><a href="#MixerTUI">MixerTUI</a></li><li><a href="#Potluck---Flavour-&-Image-Repository-for-pot">Potluck - Flavour & Image Repository for pot</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><p>Entries from the various official and semi-official teams,
as found in the <a href="../../administration.html" shape="rect">Administration
Page</a>.</p><br /><h2><a name="FreeBSD-Foundation" href="#FreeBSD-Foundation" id="FreeBSD-Foundation">FreeBSD Foundation</a></h2><p>
Contact: Deb Goodkin <<a href="mailto:deb@FreeBSDFoundation.org">deb@FreeBSDFoundation.org</a>>
</p><p>The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to
supporting and promoting the FreeBSD Project and community worldwide. Funding
comes from individual and corporate donations and is used to fund and manage
software development projects, conferences and developer summits, and provide
travel grants to FreeBSD contributors. The Foundation purchases and supports
hardware to improve and maintain FreeBSD infrastructure and provides resources
to improve security, quality assurance, and release engineering efforts;
publishes marketing material to promote, educate, and advocate for the FreeBSD
Project; facilitates collaboration between commercial vendors and FreeBSD
developers; and finally, represents the FreeBSD Project in executing contracts,
license agreements, and other legal arrangements that require a recognized
legal entity.
</p>
<p>Here are some highlights of what we did to help FreeBSD last quarter:
</p>
<h3>COVID-19 Impact on the Foundation</h3>
<p>Like other organizations, we put policies in place for all of our staff members
to work from home. We also put a temporary ban on travel for staff members.
We are continuing our work supporting the community and Project, but some of
our work and responses may be delayed because of changes in some of our
priorities and the impact of limited childcare for a few of our staff members.
</p>
<h3>Partnerships and Commercial User Support</h3>
<p>We help facilitate collaboration between commercial users and FreeBSD
developers. We also meet with companies to discuss their needs and bring that
information back to the Project. Not surprisingly, the stay at home orders,
combined with our company ban on travel during Q2 made in-person meetings
non-existent. However, the team was able to continue meeting with our partners
and commercial users virtually. These meetings help us understand some of the
applications where FreeBSD is used.
</p>
<h3>Fundraising Efforts</h3>
<p>Last quarter we raised $268,400! Thank you to the individuals and organizations
that stepped in to help fund our efforts. We’d like to thank Netflix, employees
of Nginx, Beckhoff Automation, and Mozilla Foundation for their large
contributions last quarter, which helped bring our 2020 fundraising effort to
$339k. We hope other organizations will follow their lead and give back to help
us continue supporting FreeBSD.
</p>
<p>These are trying times, and we deeply appreciate every donation that has come in
from $5 to $150,000. We’re still here giving 110% to supporting FreeBSD!
</p>
<p>We are 100% funded by donations, and those funds go towards software development
work to improve FreeBSD, FreeBSD advocacy around the world, keeping FreeBSD
secure, continuous integration improvements, sponsoring BSD-related and
computing conferences (even the virtual events!), legal support for the Project,
and many other areas.
</p>
<p>Please consider making a
<a href="https://www.FreeBSDfoundation.org/donate/." shape="rect">donation to help us continue and increase our support for FreeBSD</a>.
</p>
<p>We also have the Partnership Program, to provide more benefits for our larger
commercial donors. Find out more information about the
<a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">partnership program</a>
and share with your companies!
</p>
<h3>OS Improvements</h3>
<p>A number of FreeBSD Foundation grant recipients started, continued working on,
or completed projects during the second quarter. These include:
</p><ul>
<li><p>WiFi improvements
</p></li>
<li><p>Linuxulator application compatibility
</p></li>
<li><p>DRM / Graphics driver updates
</p></li>
<li><p>Zstd compression for OpenZFS
</p></li>
<li><p>Online RAID-Z expansion
</p></li>
<li><p>if_bridge performance improvements
</p>
</li></ul>
<p>You can find more details about most of these projects in other quarterly
reports.
</p>
<p>Staff members also worked on a number of larger projects, including:
</p><ul>
<li><p>Run-Time Dynamic Linker (rtld) improvements
</p></li>
<li><p>Improved FreeBSD support on Microsoft HyperV and Azure
</p></li>
<li><p>Fine-grained locking for amd64 pmap
</p></li>
<li><p>5-level paging structures for amd64
</p></li>
<li><p>Non-transparent superpages
</p></li>
<li><p>Migration to a Git repository
</p></li>
<li><p>Tool chain modernization
</p>
</li></ul>
<p>Many of these projects also have detailed entries in other quarterly report
entries.
</p>
<p>Staff members also put in significant effort in many ways other than larger,
individual projects. These include assisting with code reviews, bug report
triage, security report triage and advisory handling, addressing syzkaller
reports, and ongoing maintenance and bug fixes in functional areas such as the
tool chain, developer tools, virtual memory kernel subsystem, low-level x86
infrastructure, sockets and protocols, and others.
</p>
<h3>University of Waterloo Co-op</h3>
<p>Foundation co-op students Colin, Tiger, and Yang completed their winter 2020
work term during the second quarter, and continued on with the next school term
in their respective programs. Although COVID-19 presented a unique challenge
and prompted an abrupt transition to remote work just over half way through the
term, all three learned a lot and provided positive contributions to the FreeBSD
Project and to the Foundation.
</p>
<p>A few projects that were in progress or completed during the work term were
committed to the FreeBSD tree in the second quarter.
</p>
<h3>Continuous Integration and Quality Assurance</h3>
<p>The Foundation provides a full-time staff member who is working on improving
continuous integration, automated testing, and overall quality assurance
efforts for the FreeBSD project.
</p>
<p>During the second quarter of 2020, Foundation staff continued improving the
Project's CI infrastructure, monitoring regressions and working with
contributors to fix the failing build and test cases. The setting up of VM host
for CI jobs and staging environment is in progress. We are also working with
other teams in the Project for their testing needs. For example, we added jobs
for running full tests on non-x86 architectures. We are also working with many
external projects and companies to improve their support of FreeBSD.
</p>
<p>See the FreeBSD CI section of this report for completed work items and detailed
information.
</p>
<h3>Supporting FreeBSD Infrastructure</h3>
<p>The Foundation provides hardware and support to improve FreeBSD infrastructure.
Last quarter, we continued supporting FreeBSD hardware located around the world.
We started working on getting the new NYI Chicago colocation facility prepared
for some of the new FreeBSD hardware we are planning on purchasing.
NYI generously provides this for free to the Project.
</p>
<h3>FreeBSD Advocacy and Education</h3>
<p>A large part of our efforts are dedicated to advocating for the Project. This
includes promoting work being done by others with FreeBSD; producing advocacy
literature to teach people about FreeBSD and help make the path to starting
using FreeBSD or contributing to the Project easier; and attending and getting
other FreeBSD contributors to volunteer to run FreeBSD events, staff FreeBSD
tables, and give FreeBSD presentations.
</p>
<p>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, to work together on projects, and
to facilitate 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. As is the case
for most of us in this industry, COVID-19 has put our in-person events on hold.
In addition to attending virtual events, we are continually working on new
training initiatives and updating our selection of how-to guides to facilitate
getting more folks to try out FreeBSD.
</p>
<p>Check out some of the advocacy and education work we did last quarter:
</p>
<ul>
<li><p>Silver sponsor of BSDCan 2020. The event was held virtually, June 2-6, 2020
</p></li>
<li><p>Community Sponsor of Rootconf 2020. The event was held virtually, June 19-20, 2020
</p></li>
<li><p>Annual FreeBSD Day, June 19. This year’s celebration was postponed in
support of Juneteeth. However the activities surrounding FreeBSD Day have
been transformed into an ongoing series of online sessions. See
<i>FreeBSD Fridays</i> below for more information.
</p></li>
<li><p>Presented
<a href="https://www.youtube.com/watch?v=Wi5yMvavhQM" shape="rect">27 Years of FreeBSD and Why You Should Get Involved</a>
as part of a Linux Professional Institute series of webinars on June 24, 2020.
</p></li>
<li><p>Attended and presented at the virtual Open Source Summit 2020.
</p></li>
<li><p>Announced <i>FreeBSD Fridays</i>: A series of 101 classes designed to get you
started with FreeBSD. Find out more in the
<a href="https://www.freebsdfoundation.org/blog/announcing-freebsd-fridays-a-series-of-101-classes/" shape="rect">announcement</a>
</p></li>
<li><p>Participated as an Admin for Google Summer of Code 2020
</p></li>
<li><p>Participated in the new FreeBSD Office Hours series including holding our own
Foundation led office hours. Videos from the one hour sessions can be found
on the <a href="https://www.youtube.com/channel/UCxLxR_oW-NAmChIcSkAyZGQ" shape="rect">Project’s YouTube Channel</a>.
You can watch ours <a href="https://www.youtube.com/watch?v=Ji4ux4FWpRU" shape="rect">here</a>.
</p>
</li></ul>
<p>In addition to the information found in the Development Projects update section
of this report, take a minute to check out the latest update blogs:
</p>
<ul>
<li><p><a href="https://www.freebsdfoundation.org/blog/500-if_bridge-performance-improvement/" shape="rect">5x if_bridge Performance Improvement</a>
</p></li>
<li><p><a href="https://www.freebsdfoundation.org/blog/my-experience-as-a-freebsd-foundation-co-op-student/" shape="rect">My Experience as a FreeBSD Foundation Co-Op Student</a>
</p>
</li></ul>
<p>Keep up to date with our latest work in our <a href="https://www.freebsdfoundation.org/news-and-events/newsletter/" shape="rect">Bi-Monthly newsletters</a>.
</p>
<p>Mellanox provided an update on how and why they use FreeBSD in our latest
<a href="https://www.freebsdfoundation.org/freebsd-case-study-mellanox/" shape="rect">Contributor Case Study</a>.
</p>
<p>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
<a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">access the latest issues</a> on the
Journal site.
</p>
<p>You can find out more about
<a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">events we attended and upcoming events</a>.
</p>
<p>We have continued our work with a new website developer to help us improve our
website. Work is nearly complete to make it easier for community members to
find information more easily and to make the site more efficient. We look
forward to unveiling the refreshed site in Q3.
</p>
<h3>Foundation Board Meeting</h3>
<p>Our annual board meeting was held on Tuesday June 2, 2020. We normally hold
this meeting the Tuesday before BSDCan, in Ottawa, Ontario, Canada, but with the
company travel ban, and the conference going virtual, our meeting went virtual
for the first time. The purpose of the annual board meeting is to hold our
board director and officer elections, review work accomplished over the past
year, and put together strategic goals for the upcoming 12 months.
</p>
<p>The board generally has two all-day board meetings each year, this one, and a
more informal one in January, typically held in Berkeley. Both meetings allow
us to connect, reevaluate and discuss new ideas, while assessing what we should
do to help the Project.
</p>
<p>Some of our longer-term goals include Growing User and Developer Communities,
Developing Training and OS Course Content, Improving desktop/laptop experience,
Promoting FreeBSD (as you can see in all the advocacy work listed above), and
Improving Testing Capabilities.
</p>
<p>Results of the director and officer elections were:
</p><ul>
<li><p>Justin Gibbs (President)
</p></li>
<li><p>Benedict Reuschling (Vice President)
</p></li>
<li><p>Kirk McKusick (Treasurer)
</p></li>
<li><p>Philip Paeps (Secretary)
</p></li>
<li><p>Deb Goodkin (Assistant Secretary)
</p></li>
<li><p>Robert Watson (Director)
</p></li>
<li><p>Hiroki Sato (Director)
</p></li>
<li><p>George Neville-Neil (Director)
</p>
</li></ul>
<p>Find out more about the
<a href="https://www.freebsdfoundation.org/about/board-of-directors/" shape="rect">FreeBSD Foundation Board of Directors</a>
on our website.
</p>
<h3>Legal/FreeBSD IP</h3>
<p>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.
</p>
<p>Go to <a href="http://www.FreeBSDfoundation.org/" shape="rect">the FreeBSD Foundation's web site</a> to
find out how we support FreeBSD and how we can help you!
</p><hr /><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>The FreeBSD Core Team is the governing body of FreeBSD.
</p>
<p>The Core Team held 10 meetings during the second quarter of 2020, including a
2020-05-21 joint meeting with members of the FreeBSD Foundation. Here are some
highlights from that meeting:
</p>
<ul>
<li><p>Deb requested guidance on how the Foundation can support the community.
Core and Foundation members believe that more developer support is necessary
to fill gaps in areas where commercial customers do not provide backing.
The clearest example of such a gap is the desktop experience, including
graphics and wireless support. What makes this request different from past
requests is that rather than support for one-time projects, ongoing
positions are necessary for a consistently high-quality desktop experience.
</p>
<p> "FreeBSD not being able to run on your laptop is the first step to
irrelevance." Ed Maste
</p>
</li>
<li><p>Both teams discussed topics for upcoming sessions of FreeBSD Office Hours,
informal FreeBSD video conferences that anyone can attend. Everyone agreed
that the Office Hours have been a useful way for different parts of the
Project to engage with each other and with the wider community. Kudos to
Allan Jude for initiating the Office Hours and for everyone who has helped
make them a success by hosting or attending sessions.
</p>
</li>
<li><p>Both teams agreed that they should meet once per quarter.
</p>
</li></ul>
<p>The second annual community survey closed on 2020-06-16. The purpose of the
survey is to collect data from the public to help guide the Project's efforts
and priorities. As an example, last year's survey results helped initiate the
Project's conversion to Git. Thank you to all who took the time to respond. The
results will be released soon.
</p>
<p>The Core-initiated Git Working Group continued to make progress, but there are
still some remaining issues to be worked out with the translation from
Subversion. Hopefully the new Git src repository will be ready for use this
summer. A <a href="https://cgit-beta.freebsd.org/" shape="rect">beta version</a> has been published for
people to test and a preliminary version of a <code>Using Git for FreeBSD
Development</code> primer will soon be ready to share. Core, the Git Working Group,
and Release Engineering are working towards the goal of releasing 12.2 from the
new Git repository.
</p>
<p>Following the results of a Core-initiated developer survey, The FreeBSD Project
has adopted a new LLVM-derived [code of
conduct](https://www.freebsd.org/internal/code-of-conduct.html).
</p>
<p>The eleventh FreeBSD Core Team was elected by active developers. From a pool of
23, the 9 successful candidates for core.11 are:
</p>
<ul>
<li><p>Sean Chittenden (seanc, incumbent)
</p></li>
<li><p>Baptiste Daroussin (bapt)
</p></li>
<li><p>Kyle Evans (kevans)
</p></li>
<li><p>Mark Johnston (markj)
</p></li>
<li><p>Scott Long (scottl)
</p></li>
<li><p>Warner Losh (imp, incumbent)
</p></li>
<li><p>Ed Maste (emaste)
</p></li>
<li><p>George V. Neville-Neil (gnn)
</p></li>
<li><p>Hiroki Sato (hrs, incumbent)
</p>
</li></ul>
<p>A new Core Team secretary, Muhammad Moinur Rahman (bofh), was unanimously
approved by core.11. The outgoing core team met three times with the new core
team to help with the transition. Core.10 wishes core.11 a successful term.
</p><hr /><h2><a name="FreeBSD-Release-Engineering-Team" href="#FreeBSD-Release-Engineering-Team" id="FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/releases/11.4R/announce.html" title="https://www.freebsd.org/releases/11.4R/announce.html">FreeBSD 11.4-RELEASE announcement</a></td><td>
URL: <a href="https://www.freebsd.org/releases/11.4R/announce.html" title="FreeBSD 11.4-RELEASE announcement">https://www.freebsd.org/releases/11.4R/announce.html</a></td></tr><tr><td><a href="https://www.freebsd.org/releases/11.4R/schedule.html" title="https://www.freebsd.org/releases/11.4R/schedule.html">FreeBSD 11.4-RELEASE schedule</a></td><td>
URL: <a href="https://www.freebsd.org/releases/11.4R/schedule.html" title="FreeBSD 11.4-RELEASE schedule">https://www.freebsd.org/releases/11.4R/schedule.html</a></td></tr><tr><td><a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</a></td><td>
URL: <a href="https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/" title="FreeBSD development snapshots">https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/</a></td></tr></table><p>
Contact: FreeBSD Release Engineering Team <<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>>
</p><p>The FreeBSD Release Engineering Team is responsible for setting
and publishing release schedules for official project releases
of FreeBSD, announcing code slushes, and maintaining the respective
branches, among other things.
</p>
<p>During the second quarter of 2020, the Release Engineering Team started
work on the 11.4-RELEASE cycle, the fifth release from the stable/11
branch. The release cycle went quite smoothly, with both BETA3 and RC3
removed from the schedule. This allowed the final release to occur one
week earlier than originally scheduled, which was announced June 16.
FreeBSD 11.4-RELEASE is expected to be the final 11.x release.
</p>
<p>The FreeBSD Release Engineering Team would like to thank everyone involved
in this cycle for their hard work.
</p>
<p>Additionally throughout the quarter, several development snapshots builds
were released for the <i>head</i>, <i>stable/12</i>, and <i>stable/11</i> branches.
</p>
<p>Much of this work was sponsored by Rubicon Communications, LLC (netgate.com)
and the FreeBSD Foundation.
</p><hr /><h2><a name="Cluster-Administration-Team" href="#Cluster-Administration-Team" id="Cluster-Administration-Team">Cluster Administration Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/administration.html#t-clusteradm" title="https://www.freebsd.org/administration.html#t-clusteradm">Cluster Administration Team members</a></td><td>
URL: <a href="https://www.freebsd.org/administration.html#t-clusteradm" title="Cluster Administration Team members">https://www.freebsd.org/administration.html#t-clusteradm</a></td></tr></table><p>
Contact: Cluster Administration Team <<a href="mailto:clusteradm@FreeBSD.org">clusteradm@FreeBSD.org</a>>
</p><p>The FreeBSD Cluster Administration Team consists of the people responsible for administering the machines that the Project relies on for its distributed work and communications to be synchronised. In this quarter, the team has worked on the following:
</p>
<ul>
<li><p>Upgrade all x86 ref- and universe-machines
</p></li>
<li><p>Setup Amsterdam (PKT) mirror
</p></li>
<li><p>Solve hardware issue for bugzilla and svnweb backend
</p></li>
<li><p>Setup public <a href="https://cgit-beta.freebsd.org" shape="rect">beta git server</a>
</p></li>
<li><p>Decommission CyberOne Data (CYB) mirror
</p></li>
<li><p>Ongoing systems administration work:
</p><ul>
<li><p>Accounts management for committers.
</p></li>
<li><p>Backups of critical infrastructure.
</p></li>
<li><p>Keeping up with security updates in 3rd party software.
</p>
</li></ul>
</li></ul>
Work in progress:
<ul>
<li><p>Setup Malaysia (KUL) mirror
</p></li>
<li><p>Setup Brazil (BRA) mirror
</p></li>
<li><p>Review the service jails and service administrators operation.
</p></li>
<li><p>Infrastructure of building aarch64 and powerpc64 packages
</p><ul>
<li><p>NVME issues on PowerPC64 Power9 blocking dual socket machine from being used as pkg builder.
</p></li>
<li><p>Drive upgrade test for pkg builders (SSDs) courtesy of the FreeBSD Foundation.
</p></li>
<li><p>Boot issues with Aarch64 reference machines.
</p></li></ul>
</li><li><p>New NYI.net sponsored colocation space in Chicago-land area.
</p></li>
<li><p>Work with git working group
</p></li>
<li><p>Check new hardware requirement from other teams
</p></li>
<li><p>Searching for more providers that can fit the requirements for a <a href="https://wiki.freebsd.org/Teams/clusteradm/generic-mirror-layout" shape="rect">generic mirrored layout</a> or a <a href="https://wiki.freebsd.org/Teams/clusteradm/tiny-mirror" shape="rect">tiny mirror</a>
</p></li></ul>
<hr /><h2><a name="Continuous-Integration" href="#Continuous-Integration" id="Continuous-Integration">Continuous Integration</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://ci.FreeBSD.org" title="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
URL: <a href="https://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">https://ci.FreeBSD.org</a></td></tr><tr><td><a href="https://ci.FreeBSD.org/hwlab" title="https://ci.FreeBSD.org/hwlab">FreeBSD Hardware Testing Lab</a></td><td>
URL: <a href="https://ci.FreeBSD.org/hwlab" title="FreeBSD Hardware Testing Lab">https://ci.FreeBSD.org/hwlab</a></td></tr><tr><td><a href="https://artifact.ci.FreeBSD.org" title="https://artifact.ci.FreeBSD.org">FreeBSD CI artifact archive</a></td><td>
URL: <a href="https://artifact.ci.FreeBSD.org" title="FreeBSD CI artifact archive">https://artifact.ci.FreeBSD.org</a></td></tr><tr><td><a href="https://hackmd.io/@FreeBSD-CI" title="https://hackmd.io/@FreeBSD-CI">FreeBSD CI weekly report</a></td><td>
URL: <a href="https://hackmd.io/@FreeBSD-CI" title="FreeBSD CI weekly report">https://hackmd.io/@FreeBSD-CI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/Jenkins" title="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</a></td><td>
URL: <a href="https://wiki.freebsd.org/Jenkins" title="FreeBSD Jenkins wiki">https://wiki.freebsd.org/Jenkins</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HostedCI" title="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</a></td><td>
URL: <a href="https://wiki.freebsd.org/HostedCI" title="Hosted CI wiki">https://wiki.freebsd.org/HostedCI</a></td></tr><tr><td><a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="https://wiki.freebsd.org/3rdPartySoftwareCI">3rd Party Software CI</a></td><td>
URL: <a href="https://wiki.freebsd.org/3rdPartySoftwareCI" title="3rd Party Software CI">https://wiki.freebsd.org/3rdPartySoftwareCI</a></td></tr><tr><td><a href="https://preview.tinyurl.com/y9maauwg" title="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</a></td><td>
URL: <a href="https://preview.tinyurl.com/y9maauwg" title="Tickets related to freebsd-testing@">https://preview.tinyurl.com/y9maauwg</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ci" title="https://github.com/freebsd/freebsd-ci">FreeBSD CI Repository</a></td><td>
URL: <a href="https://github.com/freebsd/freebsd-ci" title="FreeBSD CI Repository">https://github.com/freebsd/freebsd-ci</a></td></tr></table><p>
Contact: Jenkins Admin <<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>>
<br />
Contact: Li-Wen Hsu <<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>>
</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" shape="rect">freebsd-testing Mailing List</a><br clear="none" />
Contact: IRC #freebsd-ci channel on EFNet<br clear="none" />
</p>
<p>The FreeBSD CI team maintains the continuous integration system
for the FreeBSD project. The CI system firstly checks the committed changes
can be successfully built, then performs various tests and analysis over the
newly built results.
The artifacts from the build jobs are archived in the 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. The details of these efforts
are available in the <a href="https://hackmd.io/@FreeBSD-CI" shape="rect">weekly CI reports</a>.
</p>
<p>During the second quarter of 2020, we continue working with the contributors and developers in the project for their testing needs and also keep working with external projects and companies to improve their support of FreeBSD.
</p>
<p>Important changes:
</p><ul>
<li><p>All -test jobs will run tests under <code>/usr/tests</code>, previously only x86 architectures were doing this. See the Continuous Integration on !x86 section in this report for more information.
</p></li>
<li><p>Compression algorithm of disk images on the <a href="https://artifacts.ci.freebsd.org" shape="rect">artifact server</a> has been changed to zstd to speed up compression and decompression.
</p></li>
<li><p>The build and test results will be sent to the <a href="https://lists.freebsd.org/mailman/listinfo/dev-ci" shape="rect">dev-ci mailing list</a> soon. Feedback and help with analysis is very appreciated!
</p>
</li></ul>
New jobs added:
<ul>
<li><p>https://ci.freebsd.org/job/FreeBSD-head-armv7-test/
</p></li>
<li><p>https://ci.freebsd.org/job/FreeBSD-head-aarch64-test/
</p></li>
<li><p>https://ci.freebsd.org/job/FreeBSD-head-mips64-test/
</p></li>
<li><p>https://ci.freebsd.org/job/FreeBSD-head-powerpc64-test/
</p>
</li></ul>
Work in progress:
<ul>
<li><p>Collecting and sorting CI tasks and ideas <a href="https://hackmd.io/@FreeBSD-CI/freebsd-ci-todo" shape="rect">here</a>
</p></li>
<li><p>Testing and merging pull requests in the <a href="https://github.com/freebsd/freebsd-ci/pulls" shape="rect">the FreeBSD-ci repo</a>
</p></li>
<li><p>Setting up a builder dedicated to run jobs using provisioned VMs.
</p></li>
<li><p>Setting up the CI stage environment and putting the experimental jobs on it
</p></li>
<li><p>Implementing automatic tests on bare metal hardware
</p></li>
<li><p>Adding drm ports building tests against -CURRENT
</p></li>
<li><p>Planning to run ztest and network stack tests
</p></li>
<li><p>Adding external toolchain related jobs
</p></li>
<li><p>Improving the hardware lab to be more mature and adding more hardware
</p></li>
<li><p>Helping more 3rd software get CI on FreeBSD through a hosted CI solution
</p></li>
<li><p>Working with hosted CI providers to have better FreeBSD support
</p>
</li></ul>
Please see freebsd-testing@ related tickets for more WIP information, and don't hesitate to join the effort!
<p>Sponsor: The FreeBSD Foundation
</p><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="https://www.FreeBSD.org/ports/" title="https://www.FreeBSD.org/ports/">About FreeBSD Ports</a></td><td>
URL: <a href="https://www.FreeBSD.org/ports/" title="About FreeBSD Ports">https://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</a></td><td>
URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html" title="Contributing to Ports">https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</a></td><td>
URL: <a href="http://portsmon.freebsd.org/index.html" title="FreeBSD Ports Monitoring">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="https://www.freebsd.org/portmgr/index.html" title="https://www.freebsd.org/portmgr/index.html">Ports Management Team</a></td><td>
URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team">https://www.freebsd.org/portmgr/index.html</a></td></tr></table><p>
Contact: René Ladan <<a href="mailto:portmgr-secretary@FreeBSD.org">portmgr-secretary@FreeBSD.org</a>>
<br />
Contact: FreeBSD Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>>
</p><p>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.
</p>
<p>There are currently 2,373 open ports PRs of which 526 are
unassigned, for a total of 39,628 ports. In the last quarter
there were 10,315 commits to HEAD and 476 to the quarterly
branch by respectively 178 and 65 committers. Compared to the
quarter before, this means a significant increase in commits and
also a slight decrease in open PRs.
</p>
<p>During the last quarter, we welcomed Hiroki Tagato (tagattie@).
We said goodbye to seanc@, zleslie@, gnn@ and salvadore@.
</p>
<p>A few default versions got bumped:
</p><ul>
<li><p>Java (new) at 8
</p></li>
<li><p>Lazarus to 2.0.8
</p>
</li></ul>
It is now possible to write pkg scripts in Lua instead of sh.
<p>They have two advantages over their sh versions:
</p><ul>
<li><p>they run in a Capsicum sandbox
</p></li>
<li><p>they respect rootdir, the directory which pkg will use as
the starting point to install all packages under.
</p>
</li></ul>
Some user-facing packages were also updated:
<ul>
<li><p>pkg to 1.14.6
</p></li>
<li><p>Firefox to 78.0.1
</p></li>
<li><p>Thunderbird to 68.10.0
</p></li>
<li><p>Chromium to 83.0.4103.116
</p></li>
<li><p>Ruby to 2.5.8, 2.6.6, and 2.7.1
</p></li>
<li><p>Qt5 to 5.14.2
</p>
</li></ul>
<p>During the last quarter, antoine@ ran 55 exp-runs to test port
version updates, make liblzma use libmd, flavor devel/scons and
Lua ports, add and update library functions in the base system,
make malloc.h usable again, remove as(1) from the base system, and
augment sed(1) with -f.
</p><hr /><h2><a name="FreeBSD-Office-Hours" href="#FreeBSD-Office-Hours" id="FreeBSD-Office-Hours">FreeBSD Office Hours</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/OfficeHours" title="https://wiki.freebsd.org/OfficeHours">Office Hours on the FreeBSD Wiki</a></td><td>
URL: <a href="https://wiki.freebsd.org/OfficeHours" title="Office Hours on the FreeBSD Wiki">https://wiki.freebsd.org/OfficeHours</a></td></tr><tr><td><a href="https://forms.gle/3HjjRx9KMcM3SL4H7" title="https://forms.gle/3HjjRx9KMcM3SL4H7">Poll: What time would you prefer Office Hours be at</a></td><td>
URL: <a href="https://forms.gle/3HjjRx9KMcM3SL4H7" title="Poll: What time would you prefer Office Hours be at">https://forms.gle/3HjjRx9KMcM3SL4H7</a></td></tr><tr><td><a href="https://live.freebsd.org/" title="https://live.freebsd.org/">live.FreeBSD.org: Aggregation of Live streams</a></td><td>
URL: <a href="https://live.freebsd.org/" title="live.FreeBSD.org: Aggregation of Live streams">https://live.freebsd.org/</a></td></tr></table><p>
Contact: Allan Jude <<a href="mailto:allanjude@freebsd.org">allanjude@freebsd.org</a>>
</p><p>Starting on the first of April 2020, the FreeBSD project has started
hosting regular video streams to foster greater communication within
the wider FreeBSD community. The first of these sessions took the form
of a public question and answer session, which drew over 60 participants.
A second session was held two weeks later at a time more appropriate for
those in Asia, but only drew 20 participants. With the help of the FreeBSD
Foundation, we ran a poll to discover what times worked best for the
greatest number of people.
</p>
<p>On May 13th the FreeBSD Foundation hosted a session where the community
could ask questions of or about the foundation. On May 27th many of the
candidates for the new FreeBSD Core Team joined an office hours session to
answer questions from the community. Finally on June 24th another general
question and answer office hours was held.
</p>
<p>Each office hours session consists of a video meeting of some FreeBSD
developers or other subject matter experts, live streamed along with an IRC
chat room for viewers to pose questions to the panel. The stream is recorded
and posted to the official FreeBSD youtube channel.
</p>
<p>If you would like to host an office hours session, please contact:
</p><ul>
<li><p><a href="mailto:allanjude@freebsd.org" shape="rect">Allan Jude</a>
</p></li>
<li><p><a href="mailto:anne@freebsdfoundation.org" shape="rect">Anne Dickison</a>
</p>
</li></ul>
<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>
Contact: Quarterly Status Reports <<a href="mailto:quarterly@FreBSD.org">quarterly@FreBSD.org</a>>
<br />
Contact: Daniel Ebdrup Jensen <<a href="mailto:debdrup@FreeBSD.org">debdrup@FreeBSD.org</a>>
</p><p>The Quarterly Status Reports Team collects and publishes the reports that you are
reading right now.
</p>
<p>Many improvements have been done recently and thus we believe it is useful that
the Quarterly Status Reports Team submits a report. Not all the changes below
are specific to the last quarter, but we list them here anyway since we did not
write an entry for earlier reports.
</p>
<ul>
<li><p>Reports are now built using Makefiles. Among the many advantages, this allows
us to easily sort reports logically. Indeed, starting with 2019Q4, all reports
are sorted logically, while before they were sorted alphabetically within each
category.
</p>
</li>
<li><p>The conversion from markdown to docbook was performed using a python script,
with some known bugs. Salvadore has rewritten the script using perl fixing
most of the bugs. Some features are missing and many improvements are
possible, but the script is very unlikely to receive any change since it will
become obsolete as soon as the conversion to Hugo/AsciiDoctor is completed.
</p>
</li>
<li><p>Another perl script to ease the preparation of the mail version of the
reports was written.
</p>
</li>
<li><p>One more perl script has been written to allow the quarterly team to send
quarterly calls automatically using a cron job. We used it this quarter for
the first time.
</p>
</li>
<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,
with very low traffic and a high signal to noise ratio.
</p>
</li>
<li><p>If you read carefully the last quarterly calls, you should have noticed that
we now ask you to send reports to quarterly-submissions@ instead of
quarterly@. This was done to help the quarterly team distinguishing internal
discussions from submissions. Please keep in mind however that the quarterly
team prefers receiving pull requests, as they ease the administrative work.
</p>
</li></ul>
<p>We would like to thank philip@, from the postmaster team, for having created the
freebsd-quarterly-calls@ mailing list and the quarterly-submissions@ address for
us.
</p><hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><p>Projects that span multiple categories, from the kernel and userspace
to the Ports Collection or external projects.</p><br /><h2><a name="FreeBSD-on-Microsoft-HyperV-and-Azure" href="#FreeBSD-on-Microsoft-HyperV-and-Azure" id="FreeBSD-on-Microsoft-HyperV-and-Azure">FreeBSD on Microsoft HyperV and Azure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/MicrosoftAzure" title="https://wiki.freebsd.org/MicrosoftAzure">FreeBSD on MicrosoftAzure wiki</a></td><td>
URL: <a href="https://wiki.freebsd.org/MicrosoftAzure" title="FreeBSD on MicrosoftAzure wiki">https://wiki.freebsd.org/MicrosoftAzure</a></td></tr><tr><td><a href="https://wiki.freebsd.org/HyperV" title="https://wiki.freebsd.org/HyperV">FreeBSD on Microsoft HyperV</a></td><td>
URL: <a href="https://wiki.freebsd.org/HyperV" title="FreeBSD on Microsoft HyperV">https://wiki.freebsd.org/HyperV</a></td></tr></table><p>
Contact: FreeBSD Integration Services Team <<a href="mailto:bsdic@microsoft.com">bsdic@microsoft.com</a>>
<br />
Contact: Wei Hu <<a href="mailto:whu@FreeBSD.org">whu@FreeBSD.org</a>>
<br />
Contact: Li-Wen Hsu <<a href="mailto:lwhsu@FreeBSD.org">lwhsu@FreeBSD.org</a>>
</p><p>HyperV socket for FreeBSD implemented by Wei was checked into FreeBSD head
branch on May 20th as
<a href="https://svnweb.freebsd.org/changeset/base/r361275" shape="rect">r361275</a>. It supports
guest/host communications without the need for networking. Some HyperV
and Azure features rely on this to be available in guests.
</p>
<p>Details of HyperV Socket is available <a href="https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/make-integration-service" shape="rect">here</a>.
</p>
<p>This project is sponsored by Microsoft.
</p>
<p>Li-Wen is working on the FreeBSD release code related to Azure for the -CURRENT, 12-STABLE and 11-STABLE branches.
The work-in-progress is available <a href="https://reviews.freebsd.org/D23804" shape="rect">here</a>.
The <a href="https://azuremarketplace.microsoft.com/marketplace/apps/thefreebsdfoundation.freebsd-12_1" shape="rect">12.1-RELEASE image on Azure Marketplace</a> is published.
The work on the 11.4-RELEASE image on Azure Marketplace is in progress.
</p>
<p>This project is sponsored by The FreeBSD Foundation.
</p><hr /><h2><a name="Git-Migration-Working-Group" href="#Git-Migration-Working-Group" id="Git-Migration-Working-Group">Git Migration Working Group</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/git_conv" title="https://github.com/freebsd/git_conv">Git conversion tooling repo</a></td><td>
URL: <a href="https://github.com/freebsd/git_conv" title="Git conversion tooling repo">https://github.com/freebsd/git_conv</a></td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="https://lists.freebsd.org/mailman/listinfo/freebsd-git">FreeBSD-git mailing list</a></td><td>
URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" title="FreeBSD-git mailing list">https://lists.freebsd.org/mailman/listinfo/freebsd-git</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/doc" title="https://cgit-beta.FreeBSD.org/doc">Beta doc git repo</a></td><td>
URL: <a href="https://cgit-beta.FreeBSD.org/doc" title="Beta doc git repo">https://cgit-beta.FreeBSD.org/doc</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/ports" title="https://cgit-beta.FreeBSD.org/ports">Beta ports git repo</a></td><td>
URL: <a href="https://cgit-beta.FreeBSD.org/ports" title="Beta ports git repo">https://cgit-beta.FreeBSD.org/ports</a></td></tr><tr><td><a href="https://cgit-beta.FreeBSD.org/src" title="https://cgit-beta.FreeBSD.org/src">Beta src git repo</a></td><td>
URL: <a href="https://cgit-beta.FreeBSD.org/src" title="Beta src git repo">https://cgit-beta.FreeBSD.org/src</a></td></tr></table><p>
Contact: Ed Maste <<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>>
<br />
Contact: Warner Losh <<a href="mailto:imp@FreeBSD.org">imp@FreeBSD.org</a>>
<br />
Contact: Ulrich Spörlein <<a href="mailto:uqs@FreeBSD.org">uqs@FreeBSD.org</a>>
</p><p>Work continues on FreeBSD's migration from Subversion to Git. Ulrich has
iterated on updates to svn2git in order to improve the fidelity of the
conversion, particularly in regards to vendor (contrib) code updates.
We believe the conversion is now at an acceptable state, but may make minor
adjustments if additional issues are found. We expect to push modifications
to the converter every two weeks (first and third Sunday of the month). This
means that commit hashes in the beta repo will remain stable for at least two
weeks at a time, to allow others to test and experiment with the beta repo.
</p>
<p>We are now working on updating FreeBSD processes and documentation.
This includes:
</p><ul>
<li><p>Writing a Git Primer, akin to the existing Subversion primer
</p></li>
<li><p>Updates to the Security Team's tools and processes
</p></li>
<li><p>Release engineering updates
</p></li>
<li><p>Ports and packages process updates
</p>
</li></ul>
<p>Those with an interest in the migration to Git are encouraged to subscribe
to the
<a href="https://lists.freebsd.org/mailman/listinfo/freebsd-git" shape="rect">FreeBSD-git mailing list</a>
and test out the beta src, ports, and/or doc repositories.
</p>
<p>You are also welcome to check out the wiki, issues, README and other documentation at the
<a href="https://github.com/freebsd/git_conv" shape="rect">Git conversion tooling repo</a>.
</p>
<p>We expect to be ready for the migration in the next quarter.
</p>
<p>Sponsor: The FreeBSD Foundation (in part)
</p><hr /><h2><a name="Lua-Usage-in-FreeBSD" href="#Lua-Usage-in-FreeBSD" id="Lua-Usage-in-FreeBSD">Lua Usage in FreeBSD</a></h2><p>
Contact: Ed Maste <<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>>
<br />
Contact: Kyle Evans <<a href="mailto:kevans@FreeBSD.org">kevans@FreeBSD.org</a>>
<br />
Contact: Ryan Moeller <<a href="mailto:freqlabs@FreeBSD.org">freqlabs@FreeBSD.org</a>>
</p><p>Lua is a small, efficient scripting language that FreeBSD imported before
FreeBSD 12.0 for use in the bootloader. Since then, several projects
outside of the bootloader have gained some amount of traction with Lua usage:
</p>
<ul>
<li><p>/usr/libexec/flua is now installed for internal usage
</p></li>
<li><p>makesyscalls.sh was rewritten in Lua
</p></li>
<li><p>pkg has gained support for lua scripts
</p></li>
<li><p>lldb in the base system now supports lua scripting
</p>
</li></ul>
<p>FreeBSD Lua ("flua") is a version of the lua interpreter that has several
modules built-in for convenient usage within the base system. flua is
installed with a non-standard name and in a location not included in $PATH
so that it is not accidentally found by third-party software or configure
scripts. The FreeBSD project makes no guarantees about upgrade cadence or
module stability. That said, it is available for use by downstream projects
and FreeBSD users aware of those limitations.
</p>
<p>Previous work with flua includes, for example, adding libucl support and
future work includes libifconfig support for scripting usage.
</p>
<p>People interested in working with Lua in FreeBSD are welcome to get in
contact to discuss other project ideas. To name a couple of potential
projects, some interesting modules that have not been started but could
prove useful (listed in no particular order):
</p>
<ul>
<li><p>libcrypt
</p></li>
<li><p>libexpat
</p></li>
<li><p>libjail
</p></li>
<li><p>libnv
</p></li>
<li><p>libxo
</p></li></ul>
<hr /><h2><a name="Linux-compatibility-layer-update" href="#Linux-compatibility-layer-update" id="Linux-compatibility-layer-update">Linux compatibility layer update</a></h2><p>
Contact: Edward Tomasz Napierala <<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>>
</p><p>Earlier Linuxulator work focused on code cleanups and improving
diagnostic tools.
Work has now shifted from cleanups to fixing actual applications.
Current status is being tracked at
<a href="https://wiki.freebsd.org/LinuxApps" shape="rect">Linux app status Wiki page</a>.
Initial focus is on applications that don't involve X11, mostly
because they tend to be easier to test and debug, and the bug fixes
are not application-specific.
</p>
<p>Example problems fixed include buggy madvise(2) handling, which could
break applications linked against jemalloc; uname(2) returning wrong
results for 32 bit apps, which caused problems for Steam; recvmsg(2)
and accept(2) being broken in some circumstances, which was breaking
Redis; and missing support for <code>SO_REUSEPORT</code>, <code>SO_SNDBUFFORCE</code>,
<code>SO_RCVBUFFORCE</code>, and <code>SO_PROTOCOL</code>, which spammed the log files when
running the Python regression test suite. The default soft open files
limit is now automatically adjusted to 1024, as several Linux apps
iterate over all the file descriptors up to that limit instead of using
closefrom(2).
</p>
<p>There's ongoing work on cleanups and the debugging framework for Linux
compatibility, such as logging warnings for unrecognized system call
parameters, or adding the <code>compat.linux.debug</code> sysctl to turn the warnings
off.
</p>
<p>The Linux Test Project tests that are being run as part of the
the <a href="https://ci.FreeBSD.org" shape="rect">FreeBSD Continuous Integration infrastructure</a>
has been upgraded to 20200605 snapshot. This raised the number
of test cases from 3670 to 3749, and, predictably, also the number
of failures, from 583 to 647.
</p>
<p>There's still a lot to do:
</p>
<ul>
<li><p>There are pending reviews for patches that add
<a href="https://reviews.freebsd.org/D13209" shape="rect">extended attributes support</a>,
and <a href="https://reviews.freebsd.org/D10275" shape="rect">fexecve(2) syscall</a>, and
they require wrapping up and committing
</p>
</li>
<li><p>There are over <a href="https://ci.freebsd.org/job/FreeBSD-head-amd64-test_ltp/" shape="rect">500 failing LTP tests</a>.
Some of them are false positives, some are easy to fix bugs, and some require adding
new system calls. Any help is welcome.
</p>
</li></ul>
<p>Sponsor: The FreeBSD Foundation
</p><hr /><h2><a name="NFS-over-TLS-implementation" href="#NFS-over-TLS-implementation" id="NFS-over-TLS-implementation">NFS over TLS implementation</a></h2><p>
Contact: Rick Macklem <<a href="mailto:rmacklem@freebsd.org">rmacklem@freebsd.org</a>>
</p><p>In an effort to improve NFS security, an internet draft
which I expect will become an RFC soon specifies the
use of TLS 1.3 to encrypt all data traffic on a Sun RPC
connection used for NFS.
</p>
<p>Although NFS has been able to use sec=krb5p to encrypt data
on the wire, this requires a Kerberos environment and, as
such, has not been widely adopted. It also required that
encryption/decryption be done in software, since only the
RPC message NFS arguments are encrypted.
Since Kernel TLS is capable of using hardware assist to
improve performance and does not require Kerberos, NFS
over TLS may be more widely adopted, once implementations
are available.
</p>
<p>The project to implement this has largely been completed.
The code will slowly be merged into head/current and at least
the kernel portion should be in FreeBSD-13.
</p>
<p>To support clients such as laptops, the daemons that perform the TLS
handshake may optionally handle client X.509 certificates from a
site local CA. There are now exports(5) options to require client(s) to
provide a valid X.509 certificate.
</p>
<p>The code is now available for testing. See:
https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt
Setting up system(s) for testing is still a little awkward, as explained
by the above rough document.
</p>
<p>The main limitation in the current implementation is that it uses TLS1.2
and not TLS1.3. This should change once the KERN_TLS rx patch includes
TLS1.3 support.
Also, testing of pNFS configurations has not yet been done, but will
be tested soon.
</p>
<p>Third party testing would be appreciated.
</p>
<hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><p>Updates to kernel subsystems/features, driver support,
filesystems, and more.</p><br /><h2><a name="SoC-audio-framework-and-more-audio-drivers" href="#SoC-audio-framework-and-more-audio-drivers" id="SoC-audio-framework-and-more-audio-drivers">SoC audio framework and more audio drivers</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/gonzoua/freebsd/tree/rk3399_audio" title="https://github.com/gonzoua/freebsd/tree/rk3399_audio">rk3399_audio</a></td><td>
URL: <a href="https://github.com/gonzoua/freebsd/tree/rk3399_audio" title="rk3399_audio">https://github.com/gonzoua/freebsd/tree/rk3399_audio</a></td></tr></table><p>
Contact: Oleksandr Tymoshenko <<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>>
</p><p>SoC audio framework made a good progress since last report.<br clear="none" /> Support for AUX devices was
added (devices like auxiliary amplifiers that are not part of main CODEC chip). <br clear="none" /> To verify
the framework design following audio drivers were added: recording support for RT5640 CODEC(Firefly-RK3399),
Allwinner I2S, Alwinners sun8i and A64 CODECs (Pine A64+), both recording and playback.<br clear="none" /> Current work in progress
is RK3328 CODEC (Rock64) and ES8316 CODEC (RockPro64 and Pinebook Pro).
</p><hr /><h2><a name="bhyve---NVMe-emulation-improvements" href="#bhyve---NVMe-emulation-improvements" id="bhyve---NVMe-emulation-improvements">bhyve - NVMe emulation improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/search/query/xvbcF20W__Km/" title="https://reviews.freebsd.org/search/query/xvbcF20W__Km/">bhyve NVMe reviews</a></td><td>
URL: <a href="https://reviews.freebsd.org/search/query/xvbcF20W__Km/" title="bhyve NVMe reviews">https://reviews.freebsd.org/search/query/xvbcF20W__Km/</a></td></tr></table><p>
Contact: Chuck Tuffli <<a href="mailto:chuck@freebsd.org">chuck@freebsd.org</a>>
</p><p>The University of New Hampshire InterOperability Laboratory
(a.k.a. UNH IOL) develops a suite of tests to determine if an
NVMe device conforms to the specification and is interoperable
with other NVMe products. This quarter, I undertook getting
bhyve's emulated NVMe device to pass the mandatory tests. Changes
include:
</p><ul>
<li><p>implement Flush command
</p></li>
<li><p>implement Format NVM command
</p></li>
<li><p>implement AER support
</p></li>
<li><p>implement Namespace Identification Descriptor
</p></li>
<li><p>fix Active Namespace list
</p></li>
<li><p>fix queue creation and deletion
</p></li>
<li><p>validate Deallocate range values
</p></li>
<li><p>handle zero length DSM ranges
</p></li>
<li><p>fix Get Log Page command
</p></li>
<li><p>implement SMART data I/O statistics
</p></li>
<li><p>validate the LBA start and count
</p></li>
<li><p>add basic Firmware Commit support
</p></li>
<li><p>add more compliant Get/Set Features
</p></li>
<li><p>add Feature, Interrupt Vector Config
</p></li>
<li><p>fix Get Features, Predictable Latency
</p>
</li></ul>
<p>This was also a good opportunity to restructure parts of the code
to make it more modular and easier to enhance. This includes
</p><ul>
<li><p>convert logging statements to parameterized macros
</p></li>
<li><p>refactor I/O command handling
</p></li>
<li><p>add locks around queue accesses
</p></li>
<li><p>consolidate CQ update
</p></li>
<li><p>base pci_nvme_ioreq size on advertised MDTS
</p>
</li></ul>
<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,
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
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
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.
</p>
<p>Work is still needed to add Attribute Protocol (ATT) and Generic Attribute
Profile (GATT) support.
</p><hr /><h2><a name="DRM-Drivers-Update" href="#DRM-Drivers-Update" id="DRM-Drivers-Update">DRM Drivers Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/freebsd/drm-kmod/" title="https://github.com/freebsd/drm-kmod/">drm-kmod</a></td><td>
URL: <a href="https://github.com/freebsd/drm-kmod/" title="drm-kmod">https://github.com/freebsd/drm-kmod/</a></td></tr></table><p>
Contact: Emmanuel Vadot <<a href="mailto:manu@FreeBSD.Org">manu@FreeBSD.Org</a>>
</p>
<p>The drm drivers for FreeBSD 13-CURRENT have been updated to match Linux 5.3
This brings us a little bit closer to the last LTS release of Linux (5.4).
</p>
<p>The current plan is to first update the driver to match 5.4 and then look
at making it work on FreeBSD-12-STABLE to have it ready for the 12.2 release.
</p>
<p>Sponsor: The FreeBSD Foundation
</p><hr /><h2><a name="DTS-Update" href="#DTS-Update" id="DTS-Update">DTS Update</a></h2><p>
Contact: Emmanuel Vadot <<a href="mailto:manu@FreeBSD.org">manu@FreeBSD.org</a>>
</p><p>DTS files (Device Tree Sources) were updated to be on par with Linux 5.7 for
HEAD and 5.6 for the 12-STABLE branch.
</p><hr /><h2><a name="ENA-FreeBSD-Driver-Update" href="#ENA-FreeBSD-Driver-Update" id="ENA-FreeBSD-Driver-Update">ENA FreeBSD Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README">ENA README</a></td><td>
URL: <a href="https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README" title="ENA README">https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/README</a></td></tr></table><p>
Contact: Michal Krawczyk <<a href="mailto:mk@semihalf.com">mk@semihalf.com</a>>
<br />
Contact: Artur Rojek <<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>>
<br />
Contact: Marcin Wojtas <<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>>
</p><p>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.
</p>
<p>Completed since the last update:
</p><ul>
<li><p>Fixes for Rx refill to improve stability on low memory conditions (also
released as an errata notice for FreeBSD-12.1)
</p></li>
<li><p>Upstream of the v2.2.0 driver, introducing:
</p><ul>
<li><p>Add driver support for the upcoming HW features (reporting Tx drops,
disabling meta caching)
</p></li>
<li><p>Add sysctl tuneables for IO queue number
</p></li>
<li><p>Create IO queues with optional size backoff
</p></li>
<li><p>Rework the way of configration of drbr and Rx ring size to be more robust
and stable
</p></li>
<li><p>New HAL version
</p></li>
<li><p>Driver is now marked as epoch ready
</p></li>
<li><p>Default RSS key is created using RNG to improve security
</p></li>
<li><p>Other minor fixes and improvements
</p></li></ul>
</li><li><p>MFC of the ENA v2.2.0 driver to the FreeBSD 11.4
</p>
</li></ul>
<p>Sponsor: Amazon.com Inc
</p><hr /><h2><a name="Forcible-Unmount-of-UFS/FFS-Filesystems-on-Disk-Failure" href="#Forcible-Unmount-of-UFS/FFS-Filesystems-on-Disk-Failure" id="Forcible-Unmount-of-UFS/FFS-Filesystems-on-Disk-Failure">Forcible Unmount of UFS/FFS Filesystems on Disk Failure</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24088" title="https://reviews.freebsd.org/D24088">Phabricator Details</a></td><td>
URL: <a href="https://reviews.freebsd.org/D24088" title="Phabricator Details">https://reviews.freebsd.org/D24088</a></td></tr></table><p>
Contact: Chuck Silvers <<a href="mailto:chs@freebsd.org">chs@freebsd.org</a>>
<br />
Contact: Kirk McKusick <<a href="mailto:mckusick@mckusick.com">mckusick@mckusick.com</a>>
</p><p>Commit -r361491 on May 25, 2020 enables a UFS file system to do a
forcible unmount when the underlying media fails or becomes
inaccessible. For example when a USB flash memory card hosting a
UFS file system is unplugged.
</p>
<p>The rest of this report describes in more detail how forcible
unmounts are done. Surprisingly, less than 500 lines of file
system code were added or changed.
</p>
<p>The strategy for handling disk I/O errors when soft updates are
enabled is to stop writing to the disk of the affected file system
but continue to accept I/O requests and report that all future
writes by the file system to that disk actually succeed. Then
initiate an asynchronous forced unmount of the affected file system.
</p>
<p>There are two cases for disk I/O errors:
</p>
<ul>
<li><p>ENXIO, which means that this disk is gone and the lower layers
of the storage stack already guarantee that no future I/O to
this disk will succeed.
</p>
</li>
<li><p>EIO (or most other errors), which means that this particular
I/O request has failed but subsequent I/O requests to this
disk might still succeed.
</p>
</li></ul>
<p>For ENXIO, we can just clear the error and continue, because we
know that the file system cannot affect the on-disk state after we
see this error. For EIO or other errors, we arrange for the geom_vfs
layer to reject all future I/O requests with ENXIO just like is
done when the geom_vfs is orphaned. In both cases, the file system
code can just clear the error and proceed with the forcible unmount.
</p>
<p>This new treatment of I/O errors is needed for writes of any buffer
that is involved in a dependency. Most dependencies are described
by a structure attached to the buffer's b_dep field, but some are
created and processed as a result of the completion of the dependencies
attached to the buffer.
</p>
<p>Clearing of some dependencies require a read. For example if there
is a dependency that requires an inode to be written, the disk block
containing that inode must be read, the updated inode copied into
place in that buffer, and the buffer then written back to disk.
</p>
<p>Often the needed buffer is already in memory and can be used. But
if it needs to be read from the disk, the read will fail, so we
fabricate a buffer full of zeroes and pretend that the read succeeded.
This zero'ed buffer can be updated and "written" back to disk.
</p>
<p>The only case where a buffer full of zeros causes the code to do
the wrong thing is when reading an inode buffer containing an inode
that still has an inode dependency in memory that will reinitialize
the effective link count (i_effnlink) based on the actual link count
(i_nlink) that we read. To handle this case we now store the i_nlink
value that we wrote in the inode dependency so that it can be
restored into the zero'ed buffer thus keeping the tracking of the
inode link count consistent.
</p>
<p>Because applications depend on knowing when an attempt to write
their data to stable storage has failed, the fsync(2) and msync(2)
system calls need to return errors if data fails to be written to
stable storage. So these operations return ENXIO for every call
made on files in a file system where we have otherwise been ignoring
I/O errors.
</p>
<p>Sponsor: Netflix
</p><hr /><h2><a name="i.MX-8M-support" href="#i.MX-8M-support" id="i.MX-8M-support">i.MX 8M support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D25274" title="https://reviews.freebsd.org/D25274">D25274</a></td><td>
URL: <a href="https://reviews.freebsd.org/D25274" title="D25274">https://reviews.freebsd.org/D25274</a></td></tr></table><p>
Contact: Oleksandr Tymoshenko <<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>>
</p><p>i.MX 8M is the family of application processors from NXP based on Arm® Cortex®-A53 and Cortex-M4 cores.
The initial code drop for the platform support includes CCM driver and clock implementation, GPC driver,
clock tree for i.MX 8M Quad. Most of the drivers from i.MX 6 can be reused for i.MX 8M systems with relatively minor modifications.
Common changes include adding clock support and extending list of FDT compat strings.
</p>
<p>With the linked patch FreeBSD successfully booted to multiuser with NFS root on Nitrogen8M SBC.
</p><hr /><h2><a name="Intel-wireless-and-11ac-update" href="#Intel-wireless-and-11ac-update" id="Intel-wireless-and-11ac-update">Intel wireless and 11ac update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://lists.freebsd.org/pipermail/freebsd-wireless/2020-April/009055.html" title="https://lists.freebsd.org/pipermail/freebsd-wireless/2020-April/009055.html">Initial project announcement</a></td><td>
URL: <a href="https://lists.freebsd.org/pipermail/freebsd-wireless/2020-April/009055.html" title="Initial project announcement">https://lists.freebsd.org/pipermail/freebsd-wireless/2020-April/009055.html</a></td></tr><tr><td><a href="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless" title="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless">The freebsd-wireless mailing list</a></td><td>
URL: <a href="https://lists.freebsd.org/mailman/listinfo/freebsd-wireless" title="The freebsd-wireless mailing list">https://lists.freebsd.org/mailman/listinfo/freebsd-wireless</a></td></tr></table><p>
Contact: Bjoern A. Zeeb <<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>>
</p><p>The Intel Wireless cards are one of the most commonly used
and asked for in FreeBSD notebooks.
</p>
<p>This project has three main goals:
</p><ul>
<li><p>newer Intel Wireless device support,
</p></li>
<li><p>newer WiFi standards support for Intel Wireless,
</p></li>
<li><p>integration of 802.11ac client support and infrastructure in FreeBSD.
</p>
</li></ul>
<p>The first one is needed as iwm(4) currently does not support
the latest generations of Intel Wireless cards at all.
The second is needed as in FreeBSD iwm(4) does not even support
802.11n.
The third one we want to catch up and use the improvements the
new Wifi standard offers, e.g., speed.
</p>
<p>One of the decisions made was: rather than improving iwm(4)
this work uses the dual-licensed native Linux driver under BSD license
and the linuxkpi framework to stay as close to upstream as possible as
a first step.
This will give us several advantages, such as, the full support for all
cards, quick support for new chipsets, vendor bug fixes, but also the
ability to contribute back.
</p>
<p>At this point the lower level hardware attachments and the firmware
loading and initialisation works.
I plan to release a patchset for testing before mid-July, you can see if
your currently supported or unsupported hardware will be detected.
This first cut will not support any wireless operation yet, which will follow
later in the year.
</p>
<p>If you want to help testing, please watch the freebsd-wireless list.
</p>
<p>Sponsor: The FreeBSD Foundation<br clear="none" />
</p><hr /><h2><a name="amd64-5-Level-Paging-Structures-support" href="#amd64-5-Level-Paging-Structures-support" id="amd64-5-Level-Paging-Structures-support">amd64 5-Level Paging Structures support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D25273" title="https://reviews.freebsd.org/D25273">Patch</a></td><td>
URL: <a href="https://reviews.freebsd.org/D25273" title="Patch">https://reviews.freebsd.org/D25273</a></td></tr><tr><td><a href="https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html" title="https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html">Intel SDM</a></td><td>
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
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
bits.
</p>
<p>In near future Intel CPUs will start providing 5-level paging
structures, i.e. giving 57 bits for virtual addresses (LA57). This
means, with preservation of the existing divide between KVA and UVA,
56 bit for UVA, or 2^9 = 512 times more virtual memory.
</p>
<p>The amd64 pmap was modified to support both LA48 and LA57, defaulting
to LA57 if hardware supports it. The tunable is provided to force
using LA48 even if hardware can do LA57.
</p>
<p>The most interesting part of the patch is the switch from boot paging
mode to LA57. Loaders, either legacy or UEFI, pass control to the
kernel in Long Mode, which implies that the paging is turned on. This
necessarily means that it is LA48 mode. SDM states that paging mode
cannot be switched while Long Mode is active, so kernel has to create
new page table structures, turn Long Mode off, then load new %cr3 and
finally re-enable Long Mode.
</p>
<p>I decided to only provide the larger virtual address space to usermode
for the initial step, leaving KVA layout intact. The main motivation
is that changing KVA arrangements requires changing the auto-tuning
settings, which deserve separate work. Another argument for it is
that most of the kernel memory is non-swappable, so cannot be
over-commited. We have 2:1 ratio of useful KVA to physical memory
(due to direct map), and until machines get more physical address
lines, increasing KVA is not useful.
</p>
<p>After this was decided, creating a 5-level paging structure for kernel
pmap from existing 4-level one is quite straightforward; we need to
add one page for top level, create one PML5 entry to point to existing
PML4 page, and create the famous self-referential entry for
vtopte()/vtopde().
</p>
<p>Care was taken to provide binary compatible layout of UVA for binaries
that cannot be executed correctly with larger address space. For
instance, programs could have knowledge about used bits in the
addresses and used upper bits for other data, or implemented
compressed pointers. Even if system runs in LA57 mode, specific
binary can request LA48-compatible UVA by procctl(2) or by the flag in
the FreeBSD features ELF note.
</p>
<p>Since I do not have access to a machine with LA57, development was
done using QEMU. It would be interesting to try it on the real
hardware.
</p>
<p>Sponsor: The FreeBSD Foundation<br clear="none" />
</p><hr /><h2><a name="Not-transparent-superpages" href="#Not-transparent-superpages" id="Not-transparent-superpages">Not-transparent superpages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24652" title="https://reviews.freebsd.org/D24652">Patch</a></td><td>
URL: <a href="https://reviews.freebsd.org/D24652" title="Patch">https://reviews.freebsd.org/D24652</a></td></tr></table><p>
Contact: Konstantin Belousov <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>>
</p><p>FreeBSD already provides excellent support for superpages, in a
manner completely transparent to applications. It tries to
proactively prevent fragmentation, reserves contiguous runs of the
physical pages for linear allocations in managed objects, and
auto-promote runs of small pages when they form complete superpage.
</p>
<p>The shortcomings of this approach directly follows from its strength:
some applications want to get guaranteed superpage mappings, typically
because the underlying physical memory is also offloaded into a
hardware which also has memory mapping unit. For instance, Infiniband
RMDA adapters do memory registration and remapping, which is more
efficient with large pages. In such cases transparent
(non-guaranteed) support cannot be used.
</p>
<p>The extension was developed for POSIX shared memory subsystem to allow
the creator request that the shared memory object was backed by
physically contiguous pages, with runs of specified size. The mmap(2)
syscall is aware of such objects, and if the requested mapping is
properly aligned, it will be served by superpages.
</p>
<p>The new type of the shared memory objects are backed by a modified
physical pager, which only allocates contiguous physical memory. The
VM ensures that mappings of the objects are never split (clipped) on a
non-superpage boundary. The fault handler is specially optimized to
be very fast by quickly installing the superpage PTE, and to avoid
touching all small pages constituing it.
</p>
<p>Currently the required pmap support is provided for amd64 with 2M and
1G superpage sizes.
</p>
<p>Sponsor: The FreeBSD Foundation<br clear="none" />
</p><hr /><h2><a name="NXP-ARM64-SoC-support" href="#NXP-ARM64-SoC-support" id="NXP-ARM64-SoC-support">NXP ARM64 SoC support</a></h2><p>
Contact: Marcin Wojtas <<a href="mailto:mw@semihalf.com">mw@semihalf.com</a>>
<br />
Contact: Artur Rojek <<a href="mailto:ar@semihalf.com">ar@semihalf.com</a>>
<br />
Contact: Dawid Gorecki <<a href="mailto:dgr@semihalf.com">dgr@semihalf.com</a>>
</p><p>The Semihalf team initiated working on FreeBSD support for the
<a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-based-processors-and-mcus/qoriq-layerscape-arm-processors/qoriq-layerscape-1046a-and-1026a-multicore-communications-processors:LS1046A" shape="rect">NXP LS1046A SoC</a>
</p>
<p>LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors with
integrated packet processing acceleration and high speed peripherals
including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0 for a wide
range of networking, storage, security and industrial applications.
</p>
<p>Completed since the last update:
</p><ul>
<li><p>Improve code in a couple of review cycles and merge following new
features to the FreeBSD-HEAD (r361458 - r361464):
</p><ul>
<li><p>QorIQ platform clockgen driver
</p></li>
<li><p>LS1046A clockgen driver
</p></li>
<li><p>GPIO support for QorIQ boards
</p></li>
<li><p>QorIQ LS10xx AHCI driver
</p></li>
<li><p>VF610 I2C controller support
</p></li>
<li><p>TCA6416 GPIO expander
</p></li>
<li><p>Epson RX-8803 RTC
</p>
</li></ul>
</li></ul>
Todo:
<ul>
<li><p>Upstreaming of the QorIQ SDHCI driver - it is expected to
be submitted/merged to HEAD in the Q3 of 2020.
</p>
</li></ul>
<p>Sponsor: Alstom Group
</p><hr /><h2><a name="amd64-pmap-Fine-grained-pv-lists-locking" href="#amd64-pmap-Fine-grained-pv-lists-locking" id="amd64-pmap-Fine-grained-pv-lists-locking">amd64 pmap Fine-grained pv lists locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24217" title="https://reviews.freebsd.org/D24217">Patch</a></td><td>
URL: <a href="https://reviews.freebsd.org/D24217" title="Patch">https://reviews.freebsd.org/D24217</a></td></tr></table><p>
Contact: Konstantin Belousov <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>>
</p><p>FreeBSD kernel Virtual Memory subsystem handles 'normal' application
memory, i.e. anonymous or file-backed shared and private mappings,
with so called managed pages. Managed page is fully controlled by VM,
which tracks it status. In particular, managed page can be made
read-only for write-back to the file, or unmapped for reuse (paging).
</p>
<p>The machine-dependent VM layer, pmap, must support managed pages, for
instance it must provide operations such as pmap_remove_write() to
downgrade all mappings to read-only, or pmap_remove_all() to unmap
the page from all address spaces. To implement this kind of
operations, while not causing the overhead of scanning all page
tables, pmap must track existing mappings of the page. The
tracking is done by allocating a small data structure 'pv entry'
per mapping, and linking all pv entries for the given page into pv
list.
</p>
<p>Since pv entries come from context of different address spaces, pmap
must provide synchronization to guarantee correctness of the list
structures. Current pmap allocates one mutex per one 2M physical
superpage in NUMA configurations, and MAXCPU == 256 locks hashed by
the page physical address for non-NUMA. The end result is often
undeserved lock aliasing causing pv list locks contention, since all
4k pages in the 2M superpage share the same lock, and reservations
typically cause adjusted pages to come from the same superpage.
</p>
<p>The proposed patch creates a new kernel synchronization primitive
called one byte mutex, which is embedded into the currently unused
padding in machine-dependent portion of the struct vm_page. This way
each page gets dedicated pv list lock without using any more memory.
In the ever-important buildkernel benchmark on non-NUMA config, this
change provides 2x reduction of the system time.
</p>
<p>One complication is that old locking distribution scheme made a
natural fit for superpages promotion and demotion, since all embedded
small pages shared the same pv list lock, and the operations basically
fold/unfold corresponding pv entries. Now the promotion and demotion
operations require taking all locks for constituent small pages, which
provides small but measurable impact on them. It is possible to
optimize it further by providing the 'superlock' on the first page
from the superpage run, but the affected operations are relatively
rare so that it is not even obvious that implementing the optimization
would not slow down other pathes.
</p>
<p>Another important nuance of the pv entries handling is that sometimes
pv entries allocator must not fail. Typically this is required when
kernel makes a call to pmap_enter() which must establish new mapping,
and for managed page this includes allocating the pv entry if existing
cannot be reused. If allocator cannot get a fresh page from the
vm_page_alloc(9), it opts to destroy some other managed mapping to
either get a reusable pv entry from current pmap, or destroy enough
managed mappings from some other pmap to free whole page.
</p>
<p>To do the reclamation, currently all pages from which with pv entries
are allocated, are linked in the global pv chunk list, which is
protected by global (per-NUMA domain) mutex. Any allocation or free
of pv entry has to lock the mutex, which is apparently a contention
point for large machines.
</p>
<p>Patch removes the global list of chunks, instead linking all pmaps in
the global list like it is done on i386 (but for different reason).
Now the global lock is only taken for pmap creation and free, which
corresponds to fork/exec and exit of a process, and when pv allocator
starts reclaiming from other pmaps (which is normally does not
happen).
</p>
<p>Sponsor: The FreeBSD Foundation
</p><hr /><h2><a name="Lockless-routing-lookups-and-scalable-multipath" href="#Lockless-routing-lookups-and-scalable-multipath" id="Lockless-routing-lookups-and-scalable-multipath">Lockless routing lookups and scalable multipath</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7" title="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7">Implementation of scalable multipath</a></td><td>
URL: <a href="https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7" title="Implementation of scalable multipath">https://reviews.freebsd.org/D24141#change-ZOjdMqgDgUr7</a></td></tr></table><p>
Contact: Alexander Chernikov <<a href="mailto:melifaro@FreeBSD.org">melifaro@FreeBSD.org</a>>
</p>
<p>The primary goal of this work is to bring scalable routing multipath implementation, enabled by default. Another goal is enabling high-performance routing lookups.
</p>
<p>Multipath will close long-standing feature gap that modern networking OS must have.
Lockless routing lookups will remove lookup bottlenecks, improve both dataplane and control plane performance for the setups with large number of routes.
</p>
<h3>Background</h3>
<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>
<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.
</p>
<p>Multipath implementation extends nexthop concept further by introducing nexthop groups.
</p>
<p>Each route has a pointer to either nexthops or a nexthop group, decoupling lookup algorithm from the routing stack internals. Both nexthops and nexthop groups are immutable and use epoch(9)-backed reclamation.
</p>
<p>A pre-requisite for lockless routing lookup is the introduction of modular lookup framework, allowing to attach any longest-prefix-match algorithm implementation to any IPv4/IPv6 fib.
</p>
<p>Currently there are plans to use modified DIR-24-8 algorithm from DPDK for both IPv4 and IPv6 families as an example of base lockless implementation.
</p>
<h3>Status</h3>
<ul>
<li><p>Nexthop objects [ DONE ]
</p></li>
<ul>
<li><p>Introduction of nexthop objects [ DONE ]
</p></li>
<li><p>Conversion of old KPI users to the new one [ DONE ]
</p></li>
<li><p>Conversion of route caching to nexthop caching [ DONE ]
</p></li>
<li><p>Conversion of struct <code>rtentry</code> field access to nhop field access [ DONE ]
</p></li>
<li><p>Eliminating old lookup KPI and hiding struct rtentry [ DONE ]
</p></li>
</ul>
<li><p>Multipath [ IN PROGRESS ]
</p></li>
<ul>
<li><p>Switch control plane consumers to use (rtentry, nhop) pairs instead of rtentry to allow multipath changes happen transparently [ 90% DONE ]
</p></li>
<li><p>Introduce nexthop group objects
</p></li>
<li><p>Add mutipath support for the rib (routing information base) manipulation functions
</p></li>
<li><p>Add flowid generation for outbound traffic to enable load balancing
</p></li>
</ul>
<li><p>Modular longest-prefix-match lookup algorithm [ IN PROGRESS ]
</p></li>
<ul>
<li><p>Design control plane framework for attaching algorithms [ 90% DONE ]
</p></li>
<li><p>Port IPv6 lockless lookup algorithm [ DONE ]
</p></li>
<li><p>Port IPv4 lockless lookup algorithm
</p></li>
</ul></ul><hr /><h2><a name="ZSTD-Compression-in-ZFS" href="#ZSTD-Compression-in-ZFS" id="ZSTD-Compression-in-ZFS">ZSTD Compression in ZFS</a></h2><p>
Contact: Allan Jude <<a href="mailto:allanjude@freebsd.org">allanjude@freebsd.org</a>>
</p><p>Zstandard (ZSTD) is a modern high-performance compression
algorithm designed to provide the compression ratios of gzip
while offering much better performance. ZSTD has been adopted
in FreeBSD for a number of other uses, including compressing
kernel crash dumps, as a replacement for gzip or bzip for
compressing log files, and for future versions of pkg(8).
</p>
<p>This effort to complete the integration of ZSTD into ZFS is
sponsored by the FreeBSD Foundation.
</p>
<p>Integrating ZSTD into ZFS will further extend the transparent
compression feature of ZFS by offering higher compression
ratios without the performance penalty associated with gzip.
ZSTD offers compression levels ranging from 1 (low compression)
to 22 (maximum compression), plus ZSTD-Fast levels that offer
less compression but even greater speed. This will allow the
storage administrator to select the performance-vs-compression
tradeoff that best suits their needs.
</p>
<p>Tasks remaining to be completed:
</p>
<ul>
<li><p>Extend ZFS to support compression algorithms with large numbers of levels
</p></li>
<li><p>Solve issues around the inheritence of compression settings
</p></li>
<li><p>Restore compression level when reading blocks from disk
</p></li>
<li><p>Create a future-proofing scheme to handle changing versions of ZSTD
</p></li>
<li><p>Extend ZFS replication to handle backwards compatibility with pools that do not yet support ZSTD
</p></li>
<li><p>Resolve issues around backwards compatibility when ZSTD is configured but not used
</p>
</li></ul>
<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>
Contact: Alex Richardson <<a href="mailto:arichardson@FreeBSD.org">arichardson@FreeBSD.org</a>>
<br />
Contact: Andrew Turner <<a href="mailto:andrew@FreeBSD.org">andrew@FreeBSD.org</a>>
<br />
Contact: Brooks Davis <<a href="mailto:brooks@FreeBSD.org">brooks@FreeBSD.org</a>>
<br />
Contact: Edward Tomasz Napierala <<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>>
<br />
Contact: Jessica Clarke <<a href="mailto:jrtc27@FreeBSD.org">jrtc27@FreeBSD.org</a>>
<br />
Contact: John Baldwin <<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>>
<br />
Contact: Robert Watson <<a href="mailto:rwatson@FreeBSD.org">rwatson@FreeBSD.org</a>>
<br />
Contact: Ruslan Bukin <<a href="mailto:br@FreeBSD.org">br@FreeBSD.org</a>>
</p><p>CheriBSD extends FreeBSD to implement memory protection and software
compartmentalization features supported by the CHERI instruction set
extensions.
</p>
<p>Support for CHERI-RISC-V in CheriBSD has continued to mature this
quarter in tandem with refinements to the CHERI-RISC-V architecture.
We have recently made CheriBSD's "pure capability" (CheriABI) process
environment the default ABI rather than a compatibility layer. It has
grown support for:
</p>
<ul>
<li><p>dynamically linked binaries (previously only statically-linked binaries were supported)
</p></li>
<li><p>C++ including exceptions
</p></li>
<li><p>sealed return address and function pointer capabilities ("sentries") which provide additional CFI protection
</p></li>
<li><p>initial MMU protections for loading and storing tags
</p>
</li></ul>
<p>At this point, CHERI-RISC-V support in CheriBSD is generally on par with
support for CHERI-MIPS.
</p>
<p>Much of this effort has been focused on preparing CheriBSD on
CHERI-RISC-V for inclusion as a demonstrator system in DARPA's Finding
Exploits to Thwart Tampering (<a href="https://fett.darpa.mil" shape="rect">FETT</a>) Bug Bounty
program.
</p>
<p>In addition, work has begun this quarter on porting CheriBSD to Arm's
Morello SoC. Morello is a prototype demonstrator board which adds CHERI
extensions to ARMv8-A.
</p>
<p>We've recently switched to a dev-branch model where active work takes
place on the <code>dev</code> branch and we periodically merge to <code>master</code> with
synchronization between CheriBSD and dependencies like CHERI-LLVM.
</p>
<p>For those interested in what it's like to program for CHERI, we've
recently released a <a href="https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-947.pdf" shape="rect">CHERI C/C++ Programming
Guide</a>.
</p><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><p>Updating platform-specific features and bringing in support
for new hardware platforms.</p><br /><h2><a name="Continuous-Integration-on-!x86" href="#Continuous-Integration-on-!x86" id="Continuous-Integration-on-!x86">Continuous Integration on !x86</a></h2><p>
Contact: Edward Tomasz Napierala <<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>>
</p><p>For quite a while the <a href="https://ci.FreeBSD.org" shape="rect">FreeBSD CI infrastructure</a>
has been running FreeBSD builds and regression tests, making it easy to
spot regressions. While CI was building images for all architectures,
the regression tests were only run on amd64 and i386, which means they
couldn't detect architecture-specific runtime breakage on non-x86
architectures. This poses a problem not only for FreeBSD itself,
but also for people working on FreeBSD forks for !x86, such as the CHERI
project at University of Cambridge and SRI International.
</p>
<p>The goal of this project is to run regression tests on the remaining
architectures supported by FreeBSD: ARM, ARM64, MIPS, POWER, and RISC-V.
The tests are being run using common, mostly machine-independent scripts.
Those required some changes to make it possible to use QEMU in addition
to Bhyve, the hypervisor used for x86 tests. The <code>sysutils/u-boot-qemu-arm</code>
and <code>sysutils/u-boot-qemu-arm64</code> ports were added to the Ports Collection.
Finally, each of the architectures required some tweaks, to account for
different configuration requirements - for example the MIPS kernel
doesn't support VirtIO disks, or even AHCI, whereas on ARM64 the U-Boot
gets confused with more than one VirtIO disk.
</p>
<p>On ARM, we're currently at 52 failures and 590 skipped tests, of 5925
tests ran
(https://ci.freebsd.org/job/FreeBSD-head-armv7-test/lastCompletedBuild/testReport/).
On ARM64 it's 19 failures and 160 skipped
(https://ci.freebsd.org/job/FreeBSD-head-aarch64-test/lastCompletedBuild/testReport/).
On MIPS it's 172 failures and 734 skipped
(https://ci.freebsd.org/job/FreeBSD-head-mips64-test/lastCompletedBuild/testReport/).
For POWER, and RISC-V the results are not available yet.
</p>
<p>Remaining work:
</p>
<ul>
<li><p>Failing regression tests need to be fixed.
</p>
</li>
<li><p>The tests are quite slow on QEMU, for example the ARM64 run takes about
five hours. Running them automatically after each commit would quickly
overload the CI cluster. A solution would be to e.g. run them daily.
</p>
</li>
<li><p>Some of the jobs still fail to produce results: powerpc64 deadlocks at
the end of regression test suite due to an unkillable process, riscv64
panics randomly, and on mips64 kyua(1) often crashes on jemalloc assertion.
Those might be fixed by an upcoming QEMU port update.
</p>
</li></ul>
<p>Sponsor: DARPA
</p><hr /><h2><a name="FreeBSD/RISC-V-Project" href="#FreeBSD/RISC-V-Project" id="FreeBSD/RISC-V-Project">FreeBSD/RISC-V Project</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">Wiki</a></td><td>
URL: <a href="https://wiki.freebsd.org/riscv" title="Wiki">https://wiki.freebsd.org/riscv</a></td></tr></table><p>
Contact: Mitchell Horne <<a href="mailto:mhorne@FreeBSD.org">mhorne@FreeBSD.org</a>>
</p><p>Contact: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-riscv" shape="rect">freebsd-riscv Mailing List</a><br clear="none" />
Contact: IRC #freebsd-riscv channel on freenode<br clear="none" />
</p>
<p>The <i>FreeBSD/RISC-V</i> project is providing support for running FreeBSD on the
<a href="https://riscv.org/" shape="rect">RISC-V Instruction Set Architecture</a>. Since RISC-V is still
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>
<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
result, the kernel is now able to detect and exclude physical memory reserved by
devices or firmware. A bug that prevented the kernel from using physical memory
below its load address was fixed. This typically did not manifest in much waste,
as the kernel is loaded 2MB after the start of physical memory by default. In
future boot configurations, the impact would have been much larger.
</p>
<p>Our port for OpenSBI was updated to v0.8, bringing several new features and
fixes. In particular, it brought the Hardware State Management (HSM) extension,
which can be used to start and stop CPUs. FreeBSD will now use this extension
whenever it detects that it is available.
</p>
<p>There has also been a lot of work done to port FreeBSD's standard bootloader,
<code>loader(8)</code>, to RISC-V. This has big advantages in terms of boot flexibility,
and brings us closer to what's needed to produce official FreeBSD/RISC-V release
images. By leveraging UEFI support from
<a href="https://www.denx.de/wiki/U-Boot/" shape="rect">u-boot</a>, <code>loader.efi</code> can be used in a manner
similar to arm and arm64. Next quarter will likely bring u-boot ports for RISC-V
targets, pending the v2020.07 release. Booting the kernel directly via SBI
firmware will continue to be supported.
</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><p>Changes affecting the base system and programs in it.</p><br /><h2><a name="Import-of-new-implementation-of-bc-and-dc" href="#Import-of-new-implementation-of-bc-and-dc" id="Import-of-new-implementation-of-bc-and-dc">Import of new implementation of bc and dc</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://git.yzena.com/gavin/bc" title="https://git.yzena.com/gavin/bc">Official repository</a></td><td>
URL: <a href="https://git.yzena.com/gavin/bc" title="Official repository">https://git.yzena.com/gavin/bc</a></td></tr><tr><td><a href="https://github.com/gavinhoward/bc/" title="https://github.com/gavinhoward/bc/">Repository mirror on GitHub</a></td><td>
URL: <a href="https://github.com/gavinhoward/bc/" title="Repository mirror on GitHub">https://github.com/gavinhoward/bc/</a></td></tr></table><p>
Contact: Stefan Esser <<a href="mailto:se@FreeBSD.org">se@FreeBSD.org</a>>
<br />
Contact: Gavin D. Howard <<a href="mailto:yzena.tech@gmail.com">yzena.tech@gmail.com</a>>
</p><p>A new version of bc and dc has been imported into FreeBSD-CURRENT
and enabled by default.
An import into 12-STABLE is planned before the end of July, but it
will not be enabled by default (will require "WITH_GH_BC=yes" to
be set in /etc/src.conf).
</p>
<p>This version has been developed by Gavin D. Howard with the goal
to provide a highly portable and POSIX compatible implementation.
It offers GNU bc compatibility and should be a drop-in replacement
for the bc in FreeBSD, except for standard-violating behavior of
the bc currently in FreeBSD (e.g., the modulo operator).
</p>
<p>Additional features:
</p>
<ul>
<li><p>High performance (up to more than a factor of 100 faster than
the current FreeBSD implementation in some tests)
</p></li>
<li><p>support of message catalogs with a large number of languages
supported in the current release (contributions of further
translations are welcome).
</p></li>
<li><p>Extra built-in functions and operators.
</p></li>
<li><p>Extended library of advanced math functions
</p></li>
<li><p>Detailed man-page explaining standard conformant and extended
features
</p></li>
<li><p>One shared binary for bc and dc (bc is not just a pre-processor
that relies on dc for the actual computations)
</p>
</li></ul>
<p>The only dc feature not supported by the dc is the execution of
sub-processes, since the author considers it a security hazard
for a calculator to have.
</p>
<p>This code is also available as a port and package (math/gh-bc or
gh-bc), e.g. for use with a FreeBSD binary release.
</p><hr /><h2><a name="Binutils-Retirement" href="#Binutils-Retirement" id="Binutils-Retirement">Binutils Retirement</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/GPLinBase" title="https://wiki.freebsd.org/GPLinBase">GPL in Base wiki page</a></td><td>
URL: <a href="https://wiki.freebsd.org/GPLinBase" title="GPL in Base wiki page">https://wiki.freebsd.org/GPLinBase</a></td></tr></table><p>
Contact: Ed Maste <<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>>
</p><p>We have been working on migrating to a modern and copyfree or permissively
licensed toolchain for quite some time. In the last quarter we retired two
obsolete GNU bintuils: objdump, and as.
</p>
<p>Many uses of objdump can be replaced with readelf, and llvm-objdump is also
available in the base system. Ports that depend on objdump have been updated
to rely on the GNU binutils port or package.
</p>
<p>The GNU as utility was used by both the base system and by ports. As with objdump, ports
that require GNU as have generally been updated to depend on binutils. One
file in the base system (skein_block_asm.s) proved troublesome during earlier
attempts to migrate to using Clang's integrated assembler (IAS). However,
after the update to Clang 10 (and with some trivial modifications to the
source) IAS can assemble the file.
</p>
<p>Both GNU as and objdump have been removed from FreeBSD-CURRENT and will be
absent from FreeBSD 13.0.
</p>
<h3>TODO</h3>
<p>The final task in the binutils retirement project is to remove GNU GDB 6.1.
It is currently retained for crashinfo(8).
</p>
<p>Sponsor: The FreeBSD Foundation
</p><hr /><h2><a name="Run-Time-Dynamic-Linker-improvements" href="#Run-Time-Dynamic-Linker-improvements" id="Run-Time-Dynamic-Linker-improvements">Run-Time Dynamic Linker improvements</a></h2><p>
Contact: Konstantin Belousov <<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>>
</p><p>Rtld gets some number of small bug fixes and improvements.
</p>
<p>RTLD_DEEPBIND dlopen(3) flag was implemented, despite being a strange
and even unsafe idea, for compatibility with glibc.
</p>
<p>Several improvements to the direct execution mode were made. Most
interesting are perhaps the '-v' switch to report some configuration
parameters for rtld, the ability to specify argv0 different from the
executed binary name, and fixes to properly set osrel/ABI for the
directly executed binary.
</p>
<p>The link_map structure that is used by tools that need to know the
list of loaded shared objects (like gdb and wine) was made more
compatible with glibc, while keeping existing FreeBSD ABI intact.
</p>
<p>In the course of the link_map work, it become apparent that rtld sometimes
needs to report presence of features that cannot be deduced by just a
runtime test for symbol presence or for function behavior. For that,
a scheme of reporting features with uniformingly named symbols was
designed - see the rtld(1) man-page (in CURRENT) for an explanation.
</p>
<p>Position-independent (PIE) binaries on FreeBSD are now marked with the
DF_1_PIE DT_FLAG1 flag. Otherwise, such binaries are just ET_DYN
objects and it is quite hard to distinguish proper dynamically shared
object (DSO) from PIE binary. The problem is that for binaries, the static
linker strips some information which is required for proper loading as a
DSO, and additonally, binaries contains relocations like copy-relocations
that cannot be handled for non-main binaries at all.
</p>
<p>With the flag addition, rtld properly detects binaries and refuses to
load them with dlopen() or as DT_NEEDED dependency. ldd(1) also
misdetected PIE vs. DSO, and required a fix to parse dynamic segments
to not try to dlopen() them.
</p>
<p>Sponsor: The FreeBSD Foundation
</p><hr /><h2><a name="VHDX-support-in-mkimg(1)" href="#VHDX-support-in-mkimg(1)" id="VHDX-support-in-mkimg(1)">VHDX support in mkimg(1)</a></h2><p>
Contact: Oleksandr Tymoshenko <<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>>
</p><p>VHDX is the successor of Microsoft's VHD virtual drive file format. It
increases maximum capacity of the virtual drive to 64TB and introduces features
to better handle power/system failures. <br clear="none" />VHDX is the required format for 2nd
generation Hyper-V VMs.
</p><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
changes that touch most of the tree, or individual ports
themselves.</p><br /><h2><a name="Bastille" href="#Bastille" id="Bastille">Bastille</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/bastillebsd/bastille" title="https://github.com/bastillebsd/bastille">Bastille GitHub</a></td><td>
URL: <a href="https://github.com/bastillebsd/bastille" title="Bastille GitHub">https://github.com/bastillebsd/bastille</a></td></tr><tr><td><a href="https://gitlab.com/bastillebsd-templates" title="https://gitlab.com/bastillebsd-templates">Bastille Templates</a></td><td>
URL: <a href="https://gitlab.com/bastillebsd-templates" title="Bastille Templates">https://gitlab.com/bastillebsd-templates</a></td></tr><tr><td><a href="https://bastillebsd.org" title="https://bastillebsd.org">Bastille Website</a></td><td>
URL: <a href="https://bastillebsd.org" title="Bastille Website">https://bastillebsd.org</a></td></tr></table><p>
Contact: Christer Edwards <<a href="mailto:christer.edwards@gmail.com">christer.edwards@gmail.com</a>>
</p><p>Bastille is an open-source system for automating deployment and management of
containerized applications on FreeBSD.
</p>
<p>Bastille Templates automate container setup allowing you to easily reproduce
containers as needed.
</p>
<p>Bastille is available in ports at <code>sysutils/bastille</code>.
</p>
<h3>Q2 2020 Status</h3>
<p>In Q2 2020 Bastille merged some exciting new features into GitHub. Changes include:
</p>
<ul>
<li><p>experimental support for new <code>Bastillefile</code> template syntax
</p></li>
<li><p>added <code>mount</code> and <code>umount</code> sub-commands
</p></li>
<li><p>added a default <code>Vagrantfile</code> for simple testing
</p></li>
<li><p>experimental support for empty containers
</p></li>
<li><p>improvements to VNET DHCP support
</p></li>
<li><p>cosmetic bugfixes in error output
</p></li>
<li><p>extended config file documentation
</p></li>
<li><p>updated <code>bastille help</code> output
</p></li>
<li><p>option to <code>(-f)</code> force destroy container
</p>
</li></ul>
<code>sysutils/bastille</code> was updated to <code>0.6.20200414</code> (latest).
<p>New Bastille templates added this quarter include:
</p>
<ul>
<li><p>Percona database server
</p></li>
<li><p>Asterisk SIP server
</p></li>
<li><p>dnsmasq DNS/DHCP server (VNET required)
</p></li>
<li><p>nginx pkg server for poudriere
</p>
</li></ul>
<p>Everything mentioned here was done under COVID-19 quarantine. Special thanks to
everyone that contributed during this time.
</p><hr /><h2><a name="KDE-on-FreeBSD" href="#KDE-on-FreeBSD" id="KDE-on-FreeBSD">KDE on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://freebsd.kde.org/" title="https://freebsd.kde.org/">KDE FreeBSD</a></td><td>
URL: <a href="https://freebsd.kde.org/" title="KDE FreeBSD">https://freebsd.kde.org/</a></td></tr><tr><td><a href="https://community.kde.org/FreeBSD" title="https://community.kde.org/FreeBSD">KDE Community FreeBSD</a></td><td>
URL: <a href="https://community.kde.org/FreeBSD" title="KDE Community FreeBSD">https://community.kde.org/FreeBSD</a></td></tr></table><p>
Contact: Adriaan de Groot <<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>>
</p><p>The <i>KDE on FreeBSD</i> project packages the software produced by
the KDE Community for FreeBSD. The software includes a
full desktop environment KDE Plasma, IDE <a href="https://www.kdevelop.org/" shape="rect">KDevelop</a>,
a PIM suite <a href="https://kontact.kde.org/" shape="rect">Kontact</a>
and hundreds of other applications that can be used on
any FreeBSD desktop machine.
</p>
<p>This quarter has been an ever-so-peculiar one. While we are used
to working remotely, collaborating over the internet to update the ports
tree, it's <i>qualitatively</i> different when
the whole world locks down. Meanwhile, software continues to be released,
so this quarter the kde@ team:
</p>
<ul>
<li><p>Restored a patch that closes down a remote TCP held by X11 applications
that use the ICE library. Thanks to Colin Percival for reporting it.
It went missing in one of the port updates. To prevent this in the future,
the patch has been upstreamed. PR 229772.
</p></li>
<li><p>Chased KDE-adjacent software like CMake, Cutelyst, Latte-dock and Nheko
through new releases. In particular CMake takes a lot of effort every
time because it is a build-time dependency of over 2000 ports.
</p></li>
<li><p>graphics/poppler was updated to the latest upstream release. This
is a low-level dependency for many document-viewing applications,
and like CMake requires chasing a lot of other software.
Poppler is one of the components shared between various
software stacks (and "desktop environments") under the desktop@
group, in which kde@ participates.
</p></li>
<li><p>KDE Frameworks release like clockwork, reaching KDE Frameworks 5.70 mid-may.
</p></li>
<li><p>KDE Applications -- the KDE release service, really, which delivers
libraries, applications, and add-ons -- had one large release,
with <a href="https://kde.org/announcements/changelog-releases.php?version=20.04.1" shape="rect">20.04.1</a>
landing in the ports tree also mid-may and its monthly update
20.04.2 in mid-june.
</p></li>
<li><p>Some new Wayland support for KDE Plasma -- we have not tested this on FreeBSD --
has appeared and has been duly packaged.
</p></li>
<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>
</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.
</p>
<p>The next big round of updates for the KDE stack is slated:
CMake 3.18, Qt 5.15 LTS, and KDE Frameworks 5.71.
</p><hr /><h2><a name="Haskell-on-FreeBSD" href="#Haskell-on-FreeBSD" id="Haskell-on-FreeBSD">Haskell on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.haskell.org/" title="http://www.haskell.org/">Haskell language homepage</a></td><td>
URL: <a href="http://www.haskell.org/" title="Haskell language homepage">http://www.haskell.org/</a></td></tr><tr><td><a href="https://github.com/freebsd/freebsd-ports-haskell" title="https://github.com/freebsd/freebsd-ports-haskell">Ports development repo</a></td><td>
URL: <a href="https://github.com/freebsd/freebsd-ports-haskell" title="Ports development repo">https://github.com/freebsd/freebsd-ports-haskell</a></td></tr></table><p>
Contact: Gleb Popov <<a href="mailto:haskell@FreeBSD.org">haskell@FreeBSD.org</a>>
</p><p>Haskell is a general-purpose strictly-typed pure functional language.
The Haskell on FreeBSD projects strives to provide the up-to-date
Haskell toolchain as well as various application written in this language.
</p>
<p>This quarter brought the long-awaited GHC update, which is now at
version 8.8.3. Along the compiler, the Haskell build system frontend,
cabal-install, was also upgraded to 3.0.2.0. During this update, numerous
Haskell ports were updated too.
</p>
<p>All existing ports of Haskell applications were migrated to USES=cabal,
which implements Go-style build proccess - all dependencies are compiled as
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 -
<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.
</p><hr /><h2><a name="rtsx---Porting-driver-for-Realtek-SD-card-reader-from-OpenBSD" href="#rtsx---Porting-driver-for-Realtek-SD-card-reader-from-OpenBSD" id="rtsx---Porting-driver-for-Realtek-SD-card-reader-from-OpenBSD">rtsx - Porting driver for Realtek SD card reader from OpenBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/hlh-restart/rtsx" title="https://github.com/hlh-restart/rtsx">rtsx</a></td><td>
URL: <a href="https://github.com/hlh-restart/rtsx" title="rtsx">https://github.com/hlh-restart/rtsx</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521">PR204521</a></td><td>
URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521" title="PR204521">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521</a></td></tr></table><p>
Contact: Henri Hennebert <<a href="mailto:hlh@restart.be">hlh@restart.be</a>>
</p>
<p>The rtsx driver for Realtek SD card reader has been ported from OpenBSD.
Its development snapshot is available via the <a href="http://freshports.org/sysutils/rtsx-kmod/" shape="rect">sysutils/rtsx-kmod</a> port.
</p>
<p>From March to May 2020, the code has been completed with the help of Gary
Jennejohn (gj@) and Jesper Schmitz Mouridsen (jsm@).
Some tweaks have been imported from the Linux counterpart.
</p>
<p>The driver has been successfully tested with:
</p><ul>
<li><p>RTS5209 under head (Lenovo ThinkPad L520)
</p></li>
<li><p>RTS5227 under stable/11 and releng/12.1
(HP ProBook 430 g2, Lenovo ThinkPad T450/T450s)
</p></li>
<li><p>RTS5229 under releng/12.1 (Lenovo IdeaPad 120S-14IAP)
</p></li>
<li><p>RTS522A under releng/12.1 and head (Intel NUC8i5BE, Lenovo ThinkPad P50s)
</p></li>
<li><p>RTS525A under releng/12.1 (Dell Latitude E5570)
</p></li>
<li><p>RTL8411B under stable/12 (Acer Aspire E 15 E5-576-77W6)
</p>
</li></ul>
The driver should also work for Realtek RTS5249, RTL8402 and RTL8411.
<p>More tests are welcome, especially for the devices not yet tested. These
devices may require more tweaks.
</p>
<p>PR204521 contains the bulk of exchanges for completion of the code.
</p><hr /><h2><a name="Valgrind-updates" href="#Valgrind-updates" id="Valgrind-updates">Valgrind updates</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.freebsd.org/D25452" title="https://reviews.freebsd.org/D25452">Patch for valgrind</a></td><td>
URL: <a href="https://reviews.freebsd.org/D25452" title="Patch for valgrind">https://reviews.freebsd.org/D25452</a></td></tr></table><p>
Contact: Paul Floyd <<a href="mailto:paulf@free.fr">paulf@free.fr</a>>
<br />
Contact: Kyle Evans <<a href="mailto:kevans@FreeBSD.org">kevans@FreeBSD.org</a>>
</p><p>A large amount of work has been done to rebase FreeBSD support on top of
Valgrind 3.17.0, and to address numerous test suite failures. Currently,
almost all of the regression tests pass on amd64. This is a major improvement
over the current state of affairs, in which the Valgrind is quite out of date
and is missing important functionality. Some follow-up work aims to make
FreeBSD an officially supported target platform for Valgrind.
</p>
<p>The devel/valgrind-devel port is in the process of being updated to point at
the new work.
</p><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree, in manpages, or in
external books/documents.</p><br /><h2><a name="FreeBSD-Translations-on-Weblate" href="#FreeBSD-Translations-on-Weblate" id="FreeBSD-Translations-on-Weblate">FreeBSD Translations on Weblate</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/DocTranslationOnWeblate" title="https://wiki.freebsd.org/DocTranslationOnWeblate">Translate FreeBSD on Weblate wiki</a></td><td>
URL: <a href="https://wiki.freebsd.org/DocTranslationOnWeblate" title="Translate FreeBSD on Weblate wiki">https://wiki.freebsd.org/DocTranslationOnWeblate</a></td></tr><tr><td><a href="https://translate-dev.freebsd.org/" title="https://translate-dev.freebsd.org/">FreeBSD Weblate Instance</a></td><td>
URL: <a href="https://translate-dev.freebsd.org/" title="FreeBSD Weblate Instance">https://translate-dev.freebsd.org/</a></td></tr></table><p>
Contact: Danilo G. Baio <<a href="mailto:dbaio@FreeBSD.org">dbaio@FreeBSD.org</a>>
<br />
Contact: Edson Brandi <<a href="mailto:ebrandi@FreeBSD.org">ebrandi@FreeBSD.org</a>>
</p><p>This quarter was improved the renderization of RTL (Right-to-left) languages on the FreeBSD Documentation. We faced this issue after the first RTL language joined the translations effort (fa_IR).
</p>
<p>We are looking forward to receive more languages and translators to the project as well.
</p>
<h3>Q2 2020 Status</h3>
<ul>
<li><p><b>10</b> languages (No new languages)
</p></li>
<li><p><b>80</b> registered users (33 new users since last quarter)
</p>
</li></ul>
<h4>Languages</h4>
<ul>
<li><p>Chinese (Simplified) (zh_CN)
</p></li>
<li><p>Chinese (Traditional) (zh_TW)
</p></li>
<li><p>French (fr_FR)
</p></li>
<li><p>German (de_DE)
</p></li>
<li><p>Italian (it_IT)
</p></li>
<li><p>Norwegian (nb_NO)
</p></li>
<li><p>Persian (fa_IR)
</p></li>
<li><p>Portuguese (pt_BR)
</p></li>
<li><p>Spanish (es_ES)
</p></li>
<li><p>Turkish (tr-TR)
</p>
</li></ul>
<p>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.
</p><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><p>Objects that defy categorization.</p><br /><h2><a name="FreshPorts" href="#FreshPorts" id="FreshPorts">FreshPorts</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freshports.org/" title="http://freshports.org/">FreshPorts</a></td><td>
URL: <a href="http://freshports.org/" title="FreshPorts">http://freshports.org/</a></td></tr><tr><td><a href="http://news.freshports.org/" title="http://news.freshports.org/">FreshPorts blog</a></td><td>
URL: <a href="http://news.freshports.org/" title="FreshPorts blog">http://news.freshports.org/</a></td></tr></table><p>
Contact: Dan Langille <<a href="mailto:dan@langille.org">dan@langille.org</a>>
</p>
<p>FreshPorts, and its sister site, FreshSource, have reported
upon FreeBSD commits for 20 years. They cover all commits,
not just ports.
</p>
<p>FreshPorts tracks the commits and extracts data from the
port Makefiles to create a database of information useful
to both port developers and port users.
</p>
<p>For example, https://www.freshports.org/security/acme.sh/ shows
the history of this port, back to its creation in May 2017.
</p>
<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
the creation of new git-specific jails for commit ingress (commit
processing gitdev) and for the website.
</p>
<p>Serhii (Sergey) Kozlov <a href="https://github.com/FreshPorts/git_proc_commit/blob/master/git-to-freshports/git-to-freshports.py" shape="rect">created a script</a>
to transform GIT commit entries into XML digestible by FreshPorts.
This was a huge step foward for the effort.
</p>
<p>The next step include:
</p>
<ul>
<li><p>incorporate a that script the automated processes of FreshPorts
</p></li>
<li><p>migrate to new test & stage versions of FreshPorts
</p></li>
<li><p>test
</p></li>
<li><p>get ready for prod
</p>
</li></ul>
<h4>Help wanted</h4>
<p>git is not far away now. I could use helpers to
</p>
<ul>
<li><p>review code
</p></li>
<li><p>watch the commits on the devgit websites
</p></li>
<li><p>catch missing stuff
</p>
</li></ul>
Thank you
<h3>Packages</h3>
<p>FreshPorts now displays the packages version available from the
repo sources. This covers all primary tiers (e.g. FreeBSD:12:amd64)
and all secondary tiers (e.g. FreeBSD:13:powerpc64). This helps
uses know what versions they can expect and when then repo was last
built.
</p>
<h3>Dependency lines</h3>
<p>Some things are easiest done via copy/paste. If you are working on a port
Makefile and need to add a new dependency, FreshPorts shows the dependency
line for that port. For example:
</p>
<p><pre xml:space="preserve"><code>
acme.sh>0:security/acme.sh
</code></pre>
</p>
<p>Libraries are also covered by this feature.
</p>
<p>Python ports were recently adjusted to display
</p>
<p><pre xml:space="preserve"><code>
${PYTHON_PKGNAMEPREFIX}virtualenv>0:devel/py-virtualenv
</code></pre>
</p>
<p>instead of
</p>
<p><pre xml:space="preserve"><code>
py37-virtualenv>0:devel/py-virtualenv
</code></pre>
</p>
<p>You can read more about this change in [issue
#73](https://github.com/FreshPorts/freshports/issues/73).
</p>
<h3>Watch ports I maintain</h3>
<p>The <a href="https://www.freshports.org/search.php" shape="rect">search page</a> has long had
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
address on FreshPorts must match the value in the MAINTAINER field of the port.
This is always a daily report.
</p>
<p>From time to time, an infrastructure change will occur which touches your
port. This feature ensures you know about that change.
</p>
<h3>Repology links</h3>
<p>Repology links were requested. This allows you to see what versions of that
port are in the repositories of other systems. A link to repology.org
appears on every port page.
</p>
<h3>Further reading</h3>
<p>Based upon <a href="https://news.freshports.org/2019/09/03/things-you-didnt-know-freshports-can-do/" shape="rect">things you didn’t know FreshPorts can do</a>
</p>
<p>There are many things FreshPorts can do, including search Makefile's and
<code>pkg-plist</code>. This is from a recent blog post:
</p>
<ul>
<li><p>provides example dependency line. e.g. p5-XML-RSS>0:textproc/p5-XML-RSS
</p></li>
<li><p>list of dependencies for a port
</p></li>
<li><p>list of ports depending upon this port
</p></li>
<li><p>see default configuration options
</p></li>
<li><p>what packages install a given file (e.g. bin/unzip)
</p></li>
<li><p>find out what ports a person maintains
</p></li>
<li><p>find Makefiles which contain references to bunzip
</p></li>
<li><p>search results can be plain-text consisting of a list of foo/bar ports
</p></li>
<li><p>the Maximum Effort checkbox on the search page does nothing
</p></li>
<li><p>committers can be notified of sanity test failures after the commit
</p></li>
<li><p>find a commit, any commit, based on SVN revision number, e.g. : https://www.freshports.org/commit.php?revision=352332
</p>
</li></ul>
<h3>Javascript help wanted</h3>
<p>We <a href="https://github.com/FreshPorts/freshports/commit/f620270161dd7818272dfebacacaaf26df5f37e6" shape="rect">recently upgraded</a>
some outdated Javascript modules. This broke our [JavaScript based
graphs](https://www.freshports.org/graphs2.php). We could use some help on
fixing that please. The starting points are listed on that URL. If you need
a working website to play with, please contact me with a ssh public-key.
</p>
<p>Sponsor: hardware provided by iXsystems
</p><hr /><h2><a name="PCI-passthrough-with-bhyve-on-Intel-and-for-OpenBSD-guests" href="#PCI-passthrough-with-bhyve-on-Intel-and-for-OpenBSD-guests" id="PCI-passthrough-with-bhyve-on-Intel-and-for-OpenBSD-guests">PCI passthrough with bhyve on Intel and for OpenBSD guests</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852">bhyve Intel bug report</a></td><td>
URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852" title="bhyve Intel bug report">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852</a></td></tr><tr><td><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392" title="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392">bhyve OpenBSD bug report</a></td><td>
URL: <a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392" title="bhyve OpenBSD bug report">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245392</a></td></tr><tr><td><a href="https://wiki.freebsd.org/bhyve/pci_passthru" title="https://wiki.freebsd.org/bhyve/pci_passthru">PCI passthrough with bhyve (FreeBSD wiki article)</a></td><td>
URL: <a href="https://wiki.freebsd.org/bhyve/pci_passthru" title="PCI passthrough with bhyve (FreeBSD wiki article)">https://wiki.freebsd.org/bhyve/pci_passthru</a></td></tr></table><p>
Contact: Anatoli <<a href="mailto:me@anatoli.ws">me@anatoli.ws</a>>
<br />
Contact: Callum <<a href="mailto:callum@aitchison.org">callum@aitchison.org</a>>
<br />
Contact: Peter Grehan <<a href="mailto:grehan@freebsd.org">grehan@freebsd.org</a>>
</p>
<p>bhyve(8) is a hypervisor that supports running a variety of guest
operating systems in virtual machines. bhyve(8) includes support for PCI
devices passthru, a technique to pass host PCI devices to a virtual
machine for its exclusive control and use.
</p>
<p>For some years, PCI passthrough (ppt) in bhyve was not working on some
Intel systems and for OpenBSD guests due to two bugs. The first one was
crashing FreeBSD host when bhyve was started with ppt on Intel
processors with two VT-d translation units (IOMMU), included in most
Skylake and newer Intel processors.
</p>
<p>The second bug was preventing correct interrupts handling for OpenBSD
guests. As a result, OpenBSD guests running on bhyve were not able to
use any PCI devices passed through to them from the host.
</p>
<p>During the last 2 months the second bug was identified and fixed and
they both were backported to 12.1-RELEASE (p7). So now it's possible to
fully take advantage of PCI passthrough (ppt) with bhyve in a
production-ready RELEASE version.
</p>
<p>The most typical case for ppt is to pass to the guest network adapters
for its complete control, but you can also pass through USB devices
(including external HDDs). Note though, passthrough of VGA and GPU
devices is not supported yet (for more details see the 3rd link).
</p>
<p>A particularly interesting case for ppt is to use OpenBSD guest as a
firewall and a router for a FreeBSD server.
</p>
<p>With ppt you can achieve this all inside a single server. You could pass
to the OpenBSD guest a network adapter connected to the internet and it
would take a complete control of it. After filtering the traffic, it
could pass good packets via virtual network interfaces to other guests
or to the host.
</p>
<p>Once a network adapter is passed through, a FreeBSD host not only
doesn't see it and hence doesn't handle the network traffic, it doesn't
even have to initialize the adapter (e.g. in case of a WiFi card, it's
the guest that loads the firmware).
</p>
<p>In simple terms the host only passes the device interrupts to the guest
as they come from the hardware. Everything related to the device
management happens inside the guest so there's no danger that some
network traffic exploits some issue in the host's network stack and
causes the host to crash or misbehave in other ways.
</p><hr /><h2><a name="SageMath" href="#SageMath" id="SageMath">SageMath</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.sagemath.org/" title="https://www.sagemath.org/">SageMath site</a></td><td>
URL: <a href="https://www.sagemath.org/" title="SageMath site">https://www.sagemath.org/</a></td></tr></table><p>
Contact: Thierry Thomas <<a href="mailto:thierry@FreeBSD.org">thierry@FreeBSD.org</a>>
</p><p>SageMath is a free open-source mathematics software system licensed
under the GPL. It builds on top of many existing open-source packages:
NumPy, SciPy, matplotlib, Sympy, Maxima, GAP, FLINT, R and many more.
Thanks to SageMath it is possible to access their combined power through a
common, Python-based language or directly via interfaces or wrappers.
</p>
<p>The goal is creating a viable free open source alternative to Magma, Maple,
Mathematica and Matlab.
</p>
<p>This is a complex port, with a lot of dependencies, and it has been
broken for some time. Upstream is working on easing its packaging, and
many previously bundled applications can now be replaced by external
packages.
</p>
<p>If you are interested, it would be nice to create a team of maintainers
</p>
<ul>
<li><p>to maintain some of the dependencies;
</p></li>
<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
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.</p><br /><h2><a name="chaifi---a-tool-to-simplify-joining-public-WiFi-networks" href="#chaifi---a-tool-to-simplify-joining-public-WiFi-networks" id="chaifi---a-tool-to-simplify-joining-public-WiFi-networks">chaifi - a tool to simplify joining public WiFi networks</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/gonzoua/chaifi" title="https://github.com/gonzoua/chaifi">chaifi</a></td><td>
URL: <a href="https://github.com/gonzoua/chaifi" title="chaifi">https://github.com/gonzoua/chaifi</a></td></tr></table><p>
Contact: Oleksandr Tymoshenko <<a href="mailto:gonzo@FreeBSD.org">gonzo@FreeBSD.org</a>>
</p><p>chaifi is a TUI (text UI) utility aimed at simplifying the process of joining
public WiFi networks in places like coffee shops or libraries. It replaces the
process of scanning and manually editing wpa_supplicant.conf with an
interactive dialog. The utility is in no way a replacement for full-featured
network managers in major desktop environments. Still, if you're working from a
console or using a tiling window manager, it may save you some seconds (or in
worst case minutes) of your time.
</p><hr /><h2><a name="MixerTUI" href="#MixerTUI" id="MixerTUI">MixerTUI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://gitlab.com/alfix/mixertui" title="https://gitlab.com/alfix/mixertui">mixertui</a></td><td>
URL: <a href="https://gitlab.com/alfix/mixertui" title="mixertui">https://gitlab.com/alfix/mixertui</a></td></tr></table><p>
Contact: Alfonso Sabato Siciliano <<a href="mailto:alfonso.siciliano@email.com">alfonso.siciliano@email.com</a>>
</p><p>MixerTUI is a volume mixer with a Terminal User Interface built on the FreeBSD
sound system. It can show the current Sound Driver configuration and select an
audio device: to get its information, to change the volume or to set it as
default, the last feature allows to switch easily audio from/to laptop and hdmi,
headphones and speakers, and so on.<br clear="none" />
MixerTUI can be installed via the audio/mixertui port.
</p>
<p>I would like to thank the FreeBSD community for the tips, feedbacks and patches
to improve this project.
</p><hr /><h2><a name="Potluck---Flavour-&-Image-Repository-for-pot" href="#Potluck---Flavour-&-Image-Repository-for-pot" id="Potluck---Flavour-&-Image-Repository-for-pot">Potluck - Flavour & Image Repository for pot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://potluck.honeyguide.net/" title="https://potluck.honeyguide.net/">Potluck Repository & Project</a></td><td>
URL: <a href="https://potluck.honeyguide.net/" title="Potluck Repository & Project">https://potluck.honeyguide.net/</a></td></tr><tr><td><a href="https://github.com/hny-gd/potluck" title="https://github.com/hny-gd/potluck">Potluck on github</a></td><td>
URL: <a href="https://github.com/hny-gd/potluck" title="Potluck on github">https://github.com/hny-gd/potluck</a></td></tr><tr><td><a href="https://pot.pizzamig.dev" title="https://pot.pizzamig.dev">pot project</a></td><td>
URL: <a href="https://pot.pizzamig.dev" title="pot project">https://pot.pizzamig.dev</a></td></tr></table><p>
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>
<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>
<p>Pot "flavour" files are provided on [Github]((https://github.com/hny-gd/potluck)) and fed into a Jenkins instance. On the <a href="https://potluck.honeyguide.net/" shape="rect">Potluck Repository</a>, for each flavour, detailed descriptions as well as ready-made images to be imported by pot are provided.
</p>
<p>The initial project has been set up, and three simple flavours, along with <a href="https://potluck.honeyguide.net/blog/jitsi-meet-nomad/" shape="rect">a complete Jitsi Meet instance in a jail</a> has been created as a Proof of Concept that should allow running a fully-fledged video conference system with just a few easy commands within a few minutes.
</p>
<p>As only the initial versions have been set up and implemented so far, general feedback, tests, as well as additional, useful flavours are very welcome!
</p><hr /><a href="../news.html">News Home</a> | <a href="status.html">Status Home</a></div>
<br class="clearboth" />
</div>
<div id="footer">
<span><a href="../../search/index-site.html">Site Map</a> |
<a href="../../copyright/">Legal Notices</a> | © 1995–2021 The FreeBSD Project.
All rights reserved.</span>
<br />
</div>
</div>
</div>
</body>
</html>
|
