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
|
<?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="https://www.FreeBSD.org/favicon.ico" type="image/x-icon" />
<link rel="stylesheet" media="screen,print" href="https://www.FreeBSD.org/layout/css/fixed.css?20130112" type="text/css" />
</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="https://www.FreeBSD.org/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 quarter's FreeBSD developments continue to provide
excitement and promise for further developments. I myself
have a soft spot for manual pages, so it is especially good to
see that we have gained some documentation for writing them
(and I hope that this will translate to more and improved
manual pages in the future!). The core@ entry is also of
particular note, with the introduction of the FCP process and
the recognition of the first non-committer FreeBSD Project Member
(and more). Read on to find out more about these, as well as
improved support for the AMD Zen family of processors (e.g.,
Ryzen), and a whole lot more!</p><p>—Benjamin Kaduk</p><p><hr /></p><p>The deadline for submissions covering the period from October
to December 2017 is January 14, 2017.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li><li><a href="#Ports-Collection">Ports Collection</a></li><li><a href="#The-FreeBSD-Core-Team">The FreeBSD Core Team</a></li><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#FreeBSD-CI">FreeBSD CI</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#Intel-10G-iflib-Driver-Update">Intel 10G iflib Driver Update</a></li><li><a href="#Intel-iWARP-Support">Intel iWARP Support</a></li><li><a href="#pNFS-Server-Plan-B">pNFS Server Plan B</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#AMD-Zen-(family-17h)-support">AMD Zen (family 17h) support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#Updates-to-GDB">Updates to GDB</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSDDesktop">FreeBSDDesktop</a></li><li><a href="#OpenJFX-8">OpenJFX 8</a></li><li><a href="#Puppet">Puppet</a></li></ul><h3><a href="#Documentation">Documentation</a></h3><ul><li><a href="#Absolute-FreeBSD,-3rd-Edition">Absolute FreeBSD, 3rd Edition</a></li><li><a href="#Manual-Pages">Manual Pages</a></li></ul><h3><a href="#Third-Party-Projects">Third-Party Projects</a></h3><ul><li><a href="#The-nosh-Project">The nosh Project</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-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.1R/announce.html" title="https://www.FreeBSD.org/releases/11.1R/announce.html">FreeBSD 11.1-RELEASE Announcement</a></td><td>
URL: <a href="https://www.FreeBSD.org/releases/11.1R/announce.html" title="FreeBSD 11.1-RELEASE Announcement">https://www.FreeBSD.org/releases/11.1R/announce.html</a></td></tr><tr><td><a href="https://www.FreeBSD.org/releases/10.4R/schedule.html" title="https://www.FreeBSD.org/releases/10.4R/schedule.html">FreeBSD 10.4-RELEASE Schedule</a></td><td>
URL: <a href="https://www.FreeBSD.org/releases/10.4R/schedule.html" title="FreeBSD 10.4-RELEASE Schedule">https://www.FreeBSD.org/releases/10.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 freezes, and maintaining the
respective branches, among other things.</p>
<p>The FreeBSD Release Engineering Team continued finalizing the
11.1-RELEASE cycle, with the final release builds starting on
July 21 and the official release announcement email sent on
July 26. Thank you to everyone who helped test 11.1-RELEASE,
ensuring its quality and stability. [1]</p>
<p>FreeBSD 11.1-RELEASE is the second release from the
<tt>stable/11</tt> branch.</p>
<p>Additionally, the FreeBSD Release Engineering Team started the
10.4-RELEASE cycle, with the code slush starting on July 28.
With the final release build expected to start on September 29
and the official announcement overlapping the end of the
quarter, everything is on schedule as of this
writing. [2]</p>
<p>FreeBSD 10.4-RELEASE will be the fifth release from the
<tt>stable/10</tt> branch, and is planned to be the final release
of the 10.x series.</p>
<p>This project was sponsored by The FreeBSD Foundation [1].</p><p>This project was sponsored in part by The FreeBSD Foundation [2].</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 Website</a></td><td>
URL: <a href="https://www.freebsd.org/portmgr/index.html" title="Ports Management Team Website">https://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="https://twitter.com/freebsd_portmgr/" title="https://twitter.com/freebsd_portmgr/">FreeBSD portmgr on Twitter (@freebsd_portmgr)</a></td><td>
URL: <a href="https://twitter.com/freebsd_portmgr/" title="FreeBSD portmgr on Twitter (@freebsd_portmgr)">https://twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="https://www.facebook.com/portmgr" title="https://www.facebook.com/portmgr">FreeBSD Ports Management Team on Facebook</a></td><td>
URL: <a href="https://www.facebook.com/portmgr" title="FreeBSD Ports Management Team on Facebook">https://www.facebook.com/portmgr</a></td></tr><tr><td><a href="https://plus.google.com/communities/108335846196454338383" title="https://plus.google.com/communities/108335846196454338383">FreeBSD Ports Management Team on Google+</a></td><td>
URL: <a href="https://plus.google.com/communities/108335846196454338383" title="FreeBSD Ports Management Team on Google+">https://plus.google.com/communities/108335846196454338383</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 Collection now features over 31,600 ports. There are currently
2671 problem reports, of which 718 are unassigned. This quarter saw
almost 5,900 commits from 175 committers. The number of open PRs grew
compared to last quarter, and outpaced the number of changes.</p>
<p>This quarter, we welcomed Zach Leslie (zleslie@), Luca Pizzamiglio
(pizzamig@), Craig Leres (leres@), Adriaan de Groot (adridg@), and Dave
Cottlehuber (dch@) as new committers. The commit bits of the following
committers were taken in for safekeeping: alonso@ after 19 months of
inactivity, rpaulo@ per his request, and ache@ after he passed away.
Despite several tries and changing mentors, kami@ lacked interest in
completing his mentorship, so his commit bit was also taken in for
safekeeping.</p>
<p>On the infrastructure side, two <tt>USES</tt> values were
removed because they outlived their usefulness:</p>
<ul>
<li><tt>execinfo</tt>: <tt>libexecinfo</tt> is now available in the
base system of all supported FreeBSD versions</li>
<li><tt>twisted</tt>: there is only one Twisted port left</li>
</ul>
<p>The default version of GCC was bumped from 5 to 6. Firefox was updated
to version 56.0 and Chromium to version 61.0.3163.100. The version of
<tt>pkg</tt> itself was updated to 1.10.1.</p>
<p>During this quarter, antoine@ performed 28 exp-runs to test version
updates of major ports, improving <tt>USE_GITHUB</tt> and
<tt>SHEBANG_FILES</tt>, and API changes to the base system.
This quarter, the foundation for ports "flavors" was
committed, though more development and testing will be
performed in the coming quarter before it goes live.</p>
<h3>Open tasks:</h3><ol><li>The PR load needs more attention, as the number of open PRs
has started to increase again.</li></ol><hr /><h2><a name="The-FreeBSD-Core-Team" href="#The-FreeBSD-Core-Team" id="The-FreeBSD-Core-Team">The FreeBSD Core Team</a></h2><p>
Contact: FreeBSD Core Team <<a href="mailto:core@FreeBSD.org">core@FreeBSD.org</a>>
</p>
<p>The new "FreeBSD Community Process" was drafted during BSDCan
earlier this year. The first such document, FCP 0, defines how
the whole process works. After some time for discussion and
revision, FCP 0 was voted on and accepted by core, following the
procedure laid down within that document. Currently the use of FCPs
is entirely optional; we shall see how the community begins to
adopt their usage and evolve the process based on experience.</p>
<p>A draft update to the Code of Conduct has been prepared by the
advisory committee. Core is currently reviewing the text, and
will soon vote on accepting it. Core is keen to avoid the trap of
"rules lawyering". At the moment, the feeling is
that we need to add a preamble to the CoC to articulate the
goals of the project and to act as a general guide to the
exercise of the code.</p>
<p>This quarter has been quite a busy one concerning changes to
the roster of committers and project members. We have elected our
first new Project Member: John Hixson, who will be familiar from
many conferences where he has given presentations and ably
represented iXsystems. A second proposed Project Member was not
accepted by core, but only because core felt that Fedor Uporov
really deserved a commit bit instead.</p>
<p>In addition to Fedor Uporov, please also welcome (in no
particular order) Matt Joras, Marcin Wojtas, Chuck Tuffli, Ilya
Bakulin and Alex Richardson as brand-new committers. We have also
awarded Steven Hurd and Eugene Grosbein src commit bits to go with
their existing ports bits. Welcome back Gordon Tetlow as a src
committer, essential for his new role within secteam. Eric Davis
and Rui Paulo have both decided to hang up their commit bits: we
wish them well in their future endeavours. Finally, we must
report the sad death of Andrey Chernov, who will be sorely missed
by his colleagues and collaborators.</p>
<p>Andrey's death has highlighted another question which is only
going to become more complex over time. Keeping track of
copyrights is already hard enough within a mature source tree with
many contributors, such as the FreeBSD sources. Now we need to
consider trying to keep track of the heirs and beneficiaries of
contributors who have sadly passed away. Core will consult with
the Foundation legal team to discuss possible approaches to
alleviate this.</p>
<p>There have been complaints that the workings of Core are being
kept overly confidential, and that consequently the majority of
the project has too little idea of what is going on. This is
certainly not intentional by Core, and we are keen to open up
Core's business to more general community scrutiny as far as seems
reasonable.</p>
<p>Core dealt with a number of licensing questions:</p>
<ul>
<li>When upstreaming patches and other original works to
VirtualBox or other Oracle properties, pragmatically it works
best to provide them under the terms of the MIT license (one
of two opensource licenses accepted by Oracle). Of course,
this only applies to work upstreamed by or with the permission
of the original author.</li>
<li>The Viking software license is sufficiently BSD-like that
magic constants from their drivers can be used in FreeBSD
code.</li>
<li>There is no separate register of deviations from the allowed
BSD-like licenses in the source tree: any code in the tree
under other than BSD-like license terms can be assumed to have
been approved by core.</li>
<li>At the moment the FreeBSD copyright requirement to include
the copyright notice in redistributions in binary form is
satisfied by making the FreeBSD sources, with all of the
detailed copyright information included in the different source
code files, available alongside pre-compiled system images.
However, this does not necessarily meet the needs of downstream
projects based on FreeBSD, and given the new "packaged base",
adding per-package licensing metadata in a way similar to how
the Ports Collection works is under consideration as an alternative
mechanism.</li>
</ul>
<p>Concerns were raised regarding the pending HardenedBSD entry in the
previous quarterly report prior to publication. The FreeBSD
project welcomes reports from separate (but derived) projects in
quarterly reports and has included similar reports in the past
from other projects (such as TrueOS and pfSense). The HardenedBSD
report was edited for length and to concentrate on activities
during the quarter in question.</p>
<p>Amazon is proposing to set up mirrors of the <tt>freebsd-update</tt> and
<tt>pkg</tt> servers within AWS in order to provide faster
access for EC2 users. These mirrors will be publicly
accessible, but the expectation is that use will primarily be
from within EC2. FreeBSD AMIs will have a preset configuration
that references the Amazon servers.</p>
<p>The old, long-deprecated, and insecure "r-commands"
(<tt>rsh</tt>, <tt>rlogin</tt>, <tt>rcp</tt>) are being removed
from the base system for
12.0-RELEASE. Notice of this was added to the man pages and
release notes in time for 11.1-RELEASE and 10.4-RELEASE. Anyone
requiring these commands for backwards compatibility can use the
new <tt>net/bsdrcmds</tt> port.</p>
<p>Work to replace Heimdal Kerberos in base with the more widely
compatible MIT Kerberos has begun in a new
<tt>projects/krb5</tt> branch. This should not fall afoul of
any US cryptography export regulations: the project is
required to notify the US government that cryptographic
software can be downloaded from FreeBSD servers, and this already
covers MIT Kerberos, already available within ports.</p>
<p>A number of Bay Area FreeBSD User Group-related domain names
are being given up by their original owner. The current BAFUG
organisers have been made aware.</p>
<p>Core has voted on a change to the Doceng voting rules to
provide for a "did not vote" status during doceng
voting similar to how portmgr and core voting operates. The
current requirement for all five members of doceng to register
a vote on issues was proving to be a significant
bottleneck.</p>
<hr /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.FreeBSDFoundation.org/" title="https://www.FreeBSDFoundation.org/">FreeBSD Foundation Website</a></td><td>
URL: <a href="https://www.FreeBSDFoundation.org/" title="FreeBSD Foundation Website">https://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/08/FreeBSD-Foundation-July-August-2017-Update.pdf" title="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/08/FreeBSD-Foundation-July-August-2017-Update.pdf">FreeBSD Foundation Quarterly Newsletter</a></td><td>
URL: <a href="https://www.FreeBSDfoundation.org/wp-content/uploads/2017/08/FreeBSD-Foundation-July-August-2017-Update.pdf" title="FreeBSD Foundation Quarterly Newsletter">https://www.FreeBSDfoundation.org/wp-content/uploads/2017/08/FreeBSD-Foundation-July-August-2017-Update.pdf</a></td></tr></table><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
full-time Release Engineering support; 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>
<p>Fundraising Efforts</p>
<p>Our work is 100% funded by your donations. This year we have
raised over $860,000 from over 500 donors. Our 2017 fundraising
goal is $1,250,00 and we are continuing to work hard to meet
and exceed this goal! Please consider making a donation to
help us continue and increase our support for FreeBSD: <a href="https://www.FreeBSDfoundation.org/donate/" shape="rect">https://www.FreeBSDfoundation.org/donate/</a>.</p>
<p>We also have a new Partnership Program, to provide more benefits
for our larger commercial donors. Find out more information at
<a href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/" shape="rect">https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/</a>
and share with your companies!</p>
<p>OS Improvements</p>
<p>The Foundation improves the FreeBSD operating system by
employing our technical staff to maintain and improve critical
kernel subsystems, add features and functionality, and fix
problems. This also includes funding separate project grants
like the arm64 port, <tt>blacklistd</tt> access control
daemon, and the integration of VIMAGE support, to make sure
that FreeBSD remains a viable solution for research,
education, computing, products and more.</p>
<p>We kicked off or continued the following projects last
quarter:</p>
<ul>
<li>OpenZFS RAID-Z Expansion project</li>
<li>Broadcom Wi-Fi infrastructural improvements
(<tt>bhnd(4)</tt> driver)</li>
<li>Headless mode out-of-the-box for the Beaglebone Black</li>
<li>Extending <tt>bhyve</tt>/ARMv7 features</li>
<li>Porting <tt>bhyve</tt>/ARM to an ARMv8 platform</li>
</ul>
<p>Having software developers on staff has allowed us to jump in
and work directly on projects to improve FreeBSD like:</p>
<ul>
<li>ZFS improvements</li>
<li>New Intel server support</li>
<li><tt>kqueue(2)</tt> updates</li>
<li>64-bit inode support</li>
<li>Stack guard</li>
<li>Kernel Undefined Behavior Sanitizer</li>
<li>Toolchain projects</li>
<li><tt>i915</tt> driver investigation</li>
<li>NVDIMM support in <tt>acpiconf(8)</tt></li>
<li>Continuous integration dashboard (web page and physical
hardware)</li>
<li>FAT filesystem support in makefs(8)</li>
</ul>
<p>Staff and board members continued hosting bi-weekly
conference calls to facilitate efforts for individuals to
collaborate on different technologies.</p>
<p>Release Engineering</p>
<p>The Foundation provides a full-time staff member to lead the
release engineering efforts. This has provided timely and
reliable releases over the last few years.</p>
<p>Last quarter, our full-time staff member worked with the
FreeBSD Release Engineering and Security Teams to finalize
11.1-RELEASE. He also supported the 10.4 release effort, and
has continued producing 10-STABLE, 11-STABLE, and 12-CURRENT
development snapshot builds throughout the quarter. At the
vBSDCon Developer Summit, he gave a presentation on the state
of the release engineering team.</p>
<p>You can find out more about the support we provided to the
Release Engineering Team by reading their status update in
this report.</p>
<p>Supporting FreeBSD Infrastructure</p>
<p>The Foundation provides hardware and support to improve the
FreeBSD infrastructure. Last quarter, we continued supporting
FreeBSD hardware located around the world.</p>
<p>FreeBSD Advocacy and Education</p>
<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.</p>
<p>Here is a list highlighting some of the advocacy and
education work we did last quarter:</p>
<ul>
<li>Organized and ran the Essen FreeBSD Hackathon in Essen
Germany</li>
<li>Sponsored and participated in the FreeBSD Developer Summit
BSDCam, in Cambridge, England</li>
<li>Represented FreeBSD at the ARM Partner Meeting</li>
<li>Presented and taught about FreeBSD at SdNOG 4 in Khartoum,
Sudan</li>
<li>Sponsored and gave presentations and tutorials at
EuroBSDCon in Paris, France</li>
<li>Organized and ran the Paris FreeBSD Developer Summit</li>
<li>Organized and ran the FreeBSD Developer Summit at vBSDCon</li>
<li>Sponsored and attended vBSDCon</li>
<li>Proved travel grants to FreeBSD contributors to attend the
above events.</li>
<li>Sponsored the 2017 USENIX Security Symposium in Vancouver
BC as an Industry Partner</li>
<li>Provided FreeBSD advocacy material</li>
<li>Sponsored the 2017 USENIX Annual Technical Conference in
Santa Clara, CA as an Industry Partner</li>
</ul>
<p>We continued producing FreeBSD advocacy material to help
people promote FreeBSD around the world.</p>
<p>We help educate the world about FreeBSD by publishing the
professionally produced FreeBSD Journal. Last quarter we
published the July/August issue that you can find at <a href="https://www.FreeBSDfoundation.org/journal/" shape="rect">https://www.FreeBSDfoundation.org/journal/</a>.</p>
<p>You can find out more about events we attended and upcoming
events at <a href="https://www.FreeBSDfoundation.org/news-and-events/" shape="rect">https://www.FreeBSDfoundation.org/news-and-events/</a>.</p>
<p>Legal/FreeBSD IP</p>
<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="https://www.FreeBSDfoundation.org/" shape="rect">http://www.FreeBSDfoundation.org</a>
to find out how we support FreeBSD and how we can help you!</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-CI" href="#FreeBSD-CI" id="FreeBSD-CI">FreeBSD CI</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</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><tr><td><a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</a></td><td>
URL: <a href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing" title="freebsd-testing Mailing List">https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing</a></td></tr><tr><td><a href="http://ci.FreeBSD.org" title="http://ci.FreeBSD.org">FreeBSD Jenkins Instance</a></td><td>
URL: <a href="http://ci.FreeBSD.org" title="FreeBSD Jenkins Instance">http://ci.FreeBSD.org</a></td></tr></table><p>
Contact: Jenkins Admins <<a href="mailto:jenkins-admin@FreeBSD.org">jenkins-admin@FreeBSD.org</a>>
</p>
<p>The FreeBSD CI team runs various continuous integration
solutions for FreeBSD, regularly checking that the current state
of the Subversion repository can successfully build, and
performing various tests and analysis upon the build
results.</p>
<p>We have introduced a DTrace test pipeline, with the results
and artifacts available at:</p>
<ul>
<li><a href="https://ci.FreeBSD.org/job/FreeBSD-head-amd64-dtrace_test/" shape="rect">https://ci.FreeBSD.org/job/FreeBSD-head-amd64-dtrace_test/</a></li>
<li><a href="https://artifact.ci.FreeBSD.org/dtrace-test/" shape="rect">https://artifact.ci.FreeBSD.org/dtrace-test/</a></li>
</ul>
<p>We had team meetings at two developer summits during Q3:</p>
<ul>
<li><a href="https://wiki.FreeBSD.org/DevSummit/201708/Testing" shape="rect">BSDcam</a></li>
<li><a href="https://wiki.FreeBSD.org/DevSummit/201709" shape="rect">EuroBSDCon</a></li>
</ul>
<h3>Open tasks:</h3><ol><li>Fix the failing test cases and builds.</li><li>Create builds for additional architectures.</li><li>Add more tests.</li><li>The additional TODO items listed at <a href="https://wiki.FreeBSD.org/Jenkins/TODO" shape="rect">https://wiki.FreeBSD.org/Jenkins/TODO</a>.</li></ol><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="Intel-10G-iflib-Driver-Update" href="#Intel-10G-iflib-Driver-Update" id="Intel-10G-iflib-Driver-Update">Intel 10G iflib Driver Update</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D11727" title="https://reviews.FreeBSD.org/D11727">ixgbe iflib Conversion</a></td><td>
URL: <a href="https://reviews.FreeBSD.org/D11727" title="ixgbe iflib Conversion">https://reviews.FreeBSD.org/D11727</a></td></tr></table><p>
Contact:
Chris
Galazka
<<a href="mailto:krzysztof.galazka@intel.com">krzysztof.galazka@intel.com</a>>
<br />
Contact:
Piotr
Pietruszewski
<<a href="mailto:piotr.pietruszewski@intel.com">piotr.pietruszewski@intel.com</a>>
</p>
<p>The <tt>ix</tt> and <tt>ixv</tt> network interface drivers
support a variety of Intel network interfaces, with line
speeds at 10 Gbit/second.</p>
<p>This quarter, with the help of Matt Macy and Sean Bruno (among
others), we have submitted a review in Phabricator for the
conversion of the <tt>ixgbe</tt> driver to use the new (and evolving)
<tt>iflib</tt> framework.</p>
<p>Stay tuned for the conversion of the 40G driver
(<tt>ixl</tt>), as it is currently being ported to use
<tt>iflib</tt>.</p>
<h3>Open tasks:</h3><ol><li>Additional testing.</li></ol><hr /><h2><a name="Intel-iWARP-Support" href="#Intel-iWARP-Support" id="Intel-iWARP-Support">Intel iWARP Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://reviews.FreeBSD.org/D11378" title="https://reviews.FreeBSD.org/D11378">iWARP for ixl</a></td><td>
URL: <a href="https://reviews.FreeBSD.org/D11378" title="iWARP for ixl">https://reviews.FreeBSD.org/D11378</a></td></tr></table><p>
Contact:
Bartosz
Sobczak
<<a href="mailto:bartosz.sobczak@intel.com">bartosz.sobczak@intel.com</a>>
</p>
<p>iWARP is a protocol suite that enables efficient movement
of data across the network, building on Remote Direct Memory
Access, Direct Data Placement, and Marker PDU Aligned Framing.
It endeavors to avoid unnecessary (local) data copies and to
offload work from the main CPU to dedicated hardware.</p>
<p>An initial commit adding iWARP support for the Intel X722
family of network adapters is under review. This is an
important step towards introducing full iWARP support on
systems equipped with Intel C620 Series Chipsets. Currently,
with the <tt>iw_ixl</tt> driver, only the kVerbs API is
supported.</p>
<h3>Open tasks:</h3><ol><li>Additional testing.</li></ol><hr /><h2><a name="pNFS-Server-Plan-B" href="#pNFS-Server-Plan-B" id="pNFS-Server-Plan-B">pNFS Server Plan B</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt" title="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt">Instructions for Testing</a></td><td>
URL: <a href="http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt" title="Instructions for Testing">http://people.FreeBSD.org/~rmacklem/pnfs-planb-setup.txt</a></td></tr></table><p>
Contact:
Rick
Macklem
<<a href="mailto:rmacklem@FreeBSD.org">rmacklem@FreeBSD.org</a>>
</p>
<p>A pNFS server allows an NFS service to be spread over
multiple servers, separating the MetaData operations from the
Data operations (Read and Write). This project will add the
ability to use FreeBSD systems to create a pNFS service
consisting of a single MetaData Server plus a set of Data
Servers. The Data Servers can be mirrored, so that redundant
copies of the file data are maintained.</p>
<p>The support for non-mirrored Data Servers is now believed
to be complete. Support for mirrored Data Servers using the
Flexible File Layout, which will soon be published as an RFC,
is implemented. However, there is still significant work to
be done, since the current implementation of mirrored Data
Servers does not handle failed Data Servers or their
resilvering/recovery. It is hoped that support for
failure/recovery of Data Servers will be implemented in the
next six months.</p>
<p>The patched FreeBSD sources may now be accessed for testing
via either Subversion or downloading a gzipped tarball.
They consist of a patched kernel and <tt>nfsd</tt> and can be
used on any FreeBSD 11 or later system. The installation
procedure is covered in the linked document.</p>
<h3>Open tasks:</h3><ol><li>Testing by others will be needed, now that the
implementation is available.</li><li>Implementation and testing of mirror failure/recovery.</li></ol><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="AMD-Zen-(family-17h)-support" href="#AMD-Zen-(family-17h)-support" id="AMD-Zen-(family-17h)-support">AMD Zen (family 17h) support</a></h2><p>
Contact:
Conrad
Meyer
cem@FreeBSD.org
<<a href="mailto:"></a>>
</p>
<p>This quarter, a bit of work was done to enhance platform
support for AMD Zen (Ryzen, Threadripper, Epyc) processors:</p>
<ul>
<li>The CPU topology detection code was enhanced to properly
detect Zen dies and CPU Complexes. This gives the scheduler more
locality information to use when making scheduling decisions.</li>
<li>The x86 topology analysis was enhanced to report dies and
CPU Complexes, in addition to the existing reporting on packages,
cores, and threads. An example of the new output is
<tt>FreeBSD/SMP: 1 package(s) x 2 groups x 2 cache groups
x 4 core(s) x 2 hardware threads</tt>.</li>
<li>The amdsmn(4) driver for accessing SMN (System Management
Network) registers was added.</li>
<li>CPU temperature monitoring support for Zen was added to
amdtemp(4).</li>
<li>In cpufreq(4):
<ul>
<li>Added support for decoding Zen P-state information
from Machine State Registers (which is usually not
necessary, since it is largely redundant with ACPI
P-state information, but is potentially useful)</li>
<li>Work around the apparent Ryzen inability to achieve
the P1 state by not busying cores waiting to
transition to it</li>
</ul>
</li>
<li>The intpm(4) smbus driver was fixed to attach to the AMD
FCH (Fusion Controller Hub).</li>
<li>All MCA banks are now enabled and monitored on Zen
CPUs.</li>
<li>Feature-bit decoding was added for: CLZERO, SVM features,
and RAS capabilities.</li>
<li>SHA intrinsic support was added to the aesni(4) driver.
Ryzen is currently the only desktop processor to feature
these intrinsics. Support for these intrinsics is also
present in Intel's Goldmont line of low-end SoCs.</li>
</ul>
<p>Overall, Zen is now a very usable platform for x86
workstations and servers.</p>
<p>This project was sponsored by Dell EMC Isilon.</p><h3>Open tasks:</h3><ol><li>Add HWPMC support for the new performance counters
avilable on the Zen architecture.</li><li>Add support for the CCP (Crypto Co-Processor).</li></ol><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="Updates-to-GDB" href="#Updates-to-GDB" id="Updates-to-GDB">Updates to GDB</a></h2><p>
Contact:
John
Baldwin
<<a href="mailto:jhb@FreeBSD.org">jhb@FreeBSD.org</a>>
<br />
Contact:
Luca
Pizzamiglio
<<a href="mailto:pizzamig@FreeBSD.org">pizzamig@FreeBSD.org</a>>
</p>
<p>The <tt>devel/gdb</tt> port has been updated to GDB 8.0.1.</p>
<p>Support for FreeBSD/aarch64 userland binaries has been committed
upstream. These patches, along with support for debugging
FreeBSD/aarch64 kernels, have been committed to the port.</p>
<p>Upstream patches adding improved support for FreeBSD/arm userland
binaries are currently in review. FreeBSD 12 has recently grown
support for debugging VFP registers via <tt>ptrace()</tt> and
core dumps as part of this work. Support for FreeBSD/arm kernels
will be added to the port after the upstream patches are added
to the port.</p>
<p>Support for <tt>$_siginfo</tt> has been committed upstream.
This uses the recently added NT_LWPINFO note to extract
signal information from process cores.</p>
<p>Hangs that occurred when GDB's <tt>kill</tt> command was used
were fixed in FreeBSD in r313992.</p>
<h3>Open tasks:</h3><ol><li>Figure out why the powerpc <tt>kgdb</tt> targets are not able to
unwind the stack past the initial frame.</li><li>Test support for sparc64 binaries and kernels.</li><li>Add support for debugging powerpc vector registers.</li><li>Implement <tt>info proc</tt> commands.</li><li>Implement <tt>info os</tt> commands.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><p>Changes affecting the Ports Collection, whether sweeping
changes that touch most of the tree, or individual ports
themselves.</p><br /><h2><a name="FreeBSDDesktop" href="#FreeBSDDesktop" id="FreeBSDDesktop">FreeBSDDesktop</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/FreeBSDDesktop/" title="https://github.com/FreeBSDDesktop/">FreeBSDDesktop on GitHub</a></td><td>
URL: <a href="https://github.com/FreeBSDDesktop/" title="FreeBSDDesktop on GitHub">https://github.com/FreeBSDDesktop/</a></td></tr></table><p>
Contact:
Johannes
Dieterich
<<a href="mailto:jmd@freebsd.org">jmd@freebsd.org</a>>
<br />
Contact:
Mark
Johnston
<<a href="mailto:markj@freebsd.org">markj@freebsd.org</a>>
<br />
Contact:
Hans Petter
Selasky
<<a href="mailto:hselasky@freebsd.org">hselasky@freebsd.org</a>>
<br />
Contact:
Matthew
Macy
<<a href="mailto:mmacy@nextbsd.org">mmacy@nextbsd.org</a>>
</p>
<p>The FreeBSDDesktop team is happy to announce the availability of
<tt>graphics/drm-next-kmod</tt>. This port for FreeBSD-CURRENT
(amd64) provides support for the <tt>amdgpu</tt>,
<tt>i915</tt>, and <tt>radeon</tt> DRM
modules using the <tt>linuxkpi</tt> compatibility framework.
The port currently corresponds to the DRM from Linux 4.9 and is in
an experimental state. It works reliably for many testers
with modern GPU hardware (AMD HD7000 series/Tahiti to Polaris
and Intel HD3000/Sandy Bridge to Skylake). Broader testing and
reporting/fixing of bugs is appreciated.</p> <h3>Open tasks:</h3><ol><li>Resolve issues that cause <tt>radeonkms</tt> and
<tt>amdgpu</tt> to fail with EFI boot (though there is a
workaround available).</li><li>Upgrade to Linux 4.10 and higher DRM versions.</li><li>Get feedback from broader testing.</li></ol><hr /><h2><a name="OpenJFX-8" href="#OpenJFX-8" id="OpenJFX-8">OpenJFX 8</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.openjdk.java.net/display/OpenJFX/Main" title="https://wiki.openjdk.java.net/display/OpenJFX/Main">OpenJFX Wiki</a></td><td>
URL: <a href="https://wiki.openjdk.java.net/display/OpenJFX/Main" title="OpenJFX Wiki">https://wiki.openjdk.java.net/display/OpenJFX/Main</a></td></tr><tr><td><a href="https://www.freshports.org/java/openjfx8-devel" title="https://www.freshports.org/java/openjfx8-devel">java/openjfx8-devel</a></td><td>
URL: <a href="https://www.freshports.org/java/openjfx8-devel" title="java/openjfx8-devel">https://www.freshports.org/java/openjfx8-devel</a></td></tr><tr><td><a href="https://www.freshports.org/java/openjfx8-scenebuilder" title="https://www.freshports.org/java/openjfx8-scenebuilder">java/openjfx8-scenebuilder</a></td><td>
URL: <a href="https://www.freshports.org/java/openjfx8-scenebuilder" title="java/openjfx8-scenebuilder">https://www.freshports.org/java/openjfx8-scenebuilder</a></td></tr><tr><td><a href="https://github.com/asciidocfx/AsciidocFX" title="https://github.com/asciidocfx/AsciidocFX">AsciidocFX</a></td><td>
URL: <a href="https://github.com/asciidocfx/AsciidocFX" title="AsciidocFX">https://github.com/asciidocfx/AsciidocFX</a></td></tr></table><p>
Contact:
Tobias
Kortkamp
<<a href="mailto:tobik@FreeBSD.org">tobik@FreeBSD.org</a>>
</p>
<p>OpenJFX is an open source, next generation, client
application platform for desktop and embedded systems,
based on JavaSE. This quarter, the OpenJFX port was
reworked and has received some significant improvements.</p>
<p>More modules are being built. With the new web module we
gain support for applications that have their own builtin
web browser such as AsciidocFX. The new media module
allows JavaFX applications to play audio and video
files.</p>
<p>A port of the JavaFX scenebuilder, a RAD tool for
building JavaFX scenes, was added to the ports tree.</p>
<p>The OpenGL Prism backend for GPU acceleration was enabled
by default.</p>
<p>From a mainainer's and contributor's perspective, the
port was simplified by moving all FreeBSD-local patches to
the ports tree and fetching the upstream sources directly,
instead of using a separate repository for them.</p>
<h3>Open tasks:</h3><ol><li>Upstream some of the patches in the Ports Collection.</li></ol><hr /><h2><a name="Puppet" href="#Puppet" id="Puppet">Puppet</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="https://puppetcommunity.slack.com/messages/C6CK0UGB1/">Puppetlab's FreeBSD Slack Channel</a></td><td>
URL: <a href="https://puppetcommunity.slack.com/messages/C6CK0UGB1/" title="Puppetlab's FreeBSD Slack Channel">https://puppetcommunity.slack.com/messages/C6CK0UGB1/</a></td></tr></table><p>
Contact: Puppet Team <<a href="mailto:puppet@FreeBSD.org">puppet@FreeBSD.org</a>>
</p>
<p>This summer has seen the creation of a puppet@ team to help
maintain the approximately 30 Puppet-related ports in the FreeBSD
Ports Collection.
These ports were previously maintained by various committers,
and from time to time the distributed maintainership
introduced some delays when
updating a port, due to the need to wait for a maintainer's
approval for a related change to a different port.</p>
<p>Puppet 5 is now in the ports tree (as
<tt>sysutils/puppet5</tt>). The C++ version of Facter
(<tt>sysutils/facter</tt>) got a lot of attention and is now a
drop-in replacement for the previous Ruby version
(<tt>sysutils/rubygem-facter</tt>); it is the default facts
source for the Puppet 5 port.</p>
<p>Work continues on bringing in Puppetserver 5 to the ports
tree, and on keeping all the ports up-to-date.</p>
<h3>Open tasks:</h3><ol><li>The <tt>pkg</tt> package provider has some minor issues
(it breaks things when no repos are configured, and is not
working properly from the context of the MCollective package
agent).</li><li>The <tt>databases/puppetdb[345]</tt> and
<tt>sysutils/puppetserver[45]</tt> ports rely on Clojure and
Java, and download compiled jar files instead of building them
from source.</li></ol><hr /><br /><h1><a name="Documentation" href="#Documentation" id="Documentation">Documentation</a></h1><p>Noteworthy changes in the documentation tree or new external
books/documents.</p><br /><h2><a name="Absolute-FreeBSD,-3rd-Edition" href="#Absolute-FreeBSD,-3rd-Edition" id="Absolute-FreeBSD,-3rd-Edition">Absolute FreeBSD, 3rd Edition</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://blather.michaelwlucas.com/archives/3020" title="https://blather.michaelwlucas.com/archives/3020">Official Announcement</a></td><td>
URL: <a href="https://blather.michaelwlucas.com/archives/3020" title="Official Announcement">https://blather.michaelwlucas.com/archives/3020</a></td></tr></table><p>
Contact:
Michael
Lucas
<<a href="mailto:mwlucas@michaelwlucas.com">mwlucas@michaelwlucas.com</a>>
</p>
<p>The first draft of the third edition of <em>Absolute
FreeBSD</em> is finished. It is 220,200 words, or roughly enough to
stun a medium-sized ox. It's on target to be in print before
BSDCan 2018.</p>
<h3>Open tasks:</h3><ol><li>Stare at the wall blankly for a few days.</li><li>Fix all the problems pointed out by dozens of community
reviewers.</li><li>Fix all the problems pointed out by John Baldwin, tech
reviewer extraordinaire.</li><li>Editing. Copyediting. Page layout. Page editing.
Re-editing. Indexing. Edits discovered by indexer.</li><li>Pre-orders should open some time next year.</li><li>Restrain myself from strangling people who ask when the
fourth edition is coming.</li></ol><hr /><h2><a name="Manual-Pages" href="#Manual-Pages" id="Manual-Pages">Manual Pages</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" title="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/">FreeBSD Documentation Project Primer</a></td><td>
URL: <a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" title="FreeBSD Documentation Project Primer">https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/</a></td></tr></table><p>
Contact:
Warren
Block
<<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>>
</p>
<p>Over the last year, interest has increased in manual pages, in
large part due to excellent infrastructure work by Baptiste
Daroussin and others, and promotion by George Neville-Neil and
others. This increased interest has been both gratifying and
problematic. Our man pages are underappreciated gems, but we
have sadly lacked any substantial documentation on how to write
new ones.</p>
<p>In September, I added a new chapter to the
<a href="https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/" shape="rect">FreeBSD
Documentation Project Primer</a> describing the basics of
creating a man page. It includes descriptions of the
markup, section structure, recommended optional material
such as examples, and sample templates for the most common
types of man pages. The Resources section includes links to
several external resources, including the excellent <a href="http://manpages.bsd.lv/mdoc.html" shape="rect">Practical UNIX
Manuals: mdoc</a>.</p>
<p>While this chapter is not a full tutorial, it does begin to fill
in a large gap in our documentation resources and provide a
starting point from which to grow.</p>
<h3>Open tasks:</h3><ol><li>Add more explanation and examples of markup usage.</li><li>Expand the sample templates with additional desired standard
features, like an EXAMPLES section.</li><li>Add more sample templates.</li></ol><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="The-nosh-Project" href="#The-nosh-Project" id="The-nosh-Project">The nosh Project</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/" title="http://jdebp.eu./Softwares/nosh/">Introduction</a></td><td>
URL: <a href="http://jdebp.eu./Softwares/nosh/" title="Introduction">http://jdebp.eu./Softwares/nosh/</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html" title="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html">FreeBSD Binary Packages</a></td><td>
URL: <a href="http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html" title="FreeBSD Binary Packages">http://jdebp.eu./Softwares/nosh/freebsd-binary-packages.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html" title="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html">Installation How-To</a></td><td>
URL: <a href="http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html" title="Installation How-To">http://jdebp.eu./Softwares/nosh/timorous-admin-installation-how-to.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/roadmap.html" title="http://jdebp.eu./Softwares/nosh/roadmap.html">Roadmap</a></td><td>
URL: <a href="http://jdebp.eu./Softwares/nosh/roadmap.html" title="Roadmap">http://jdebp.eu./Softwares/nosh/roadmap.html</a></td></tr><tr><td><a href="http://jdebp.eu./Softwares/nosh/guide/index.html" title="http://jdebp.eu./Softwares/nosh/guide/index.html">A Slightly Outdated User Guide</a></td><td>
URL: <a href="http://jdebp.eu./Softwares/nosh/guide/index.html" title="A Slightly Outdated User Guide">http://jdebp.eu./Softwares/nosh/guide/index.html</a></td></tr><tr><td><a href="http://framagit.org/taca/archnosh" title="http://framagit.org/taca/archnosh">Archnosh</a></td><td>
URL: <a href="http://framagit.org/taca/archnosh" title="Archnosh">http://framagit.org/taca/archnosh</a></td></tr></table><p>
Contact:
Jonathan
de Boyne Pollard
<<a href="mailto:J.deBoynePollard-newsgroups@NTLWorld.COM">J.deBoynePollard-newsgroups@NTLWorld.COM</a>>
</p>
<p>The <tt>nosh</tt> project is a suite of system-level utilities for
initializing, running, and shutting down BSD systems; and for
managing daemons, terminals, and logging. It attempts to
supersede BSD <tt>init</tt>, the Mewburn <tt>rc.d</tt> system,
and OpenRC as used on FreeBSD and TrueOS, drawing inspiration
from Solaris SMF for named milestones, daemontools-encore for
service control/status mechanisms, UCSPI, and IBM AIX for
separated service and system management. It includes a range
of compatibility mechanisms, including shims for familiar
commands from other systems, and an automatic import mechanism
that takes existing configuration data from
<tt>/etc/fstab</tt>, <tt>/etc/rc.conf{,.local}</tt>,
<tt>/etc/ttys</tt>, and elsewhere, applying them to its native
service definitions and creating additional native services.
It is portable (including to Linux) and composable, it
provides a migration path from the world of <tt>systemd</tt> Linux, and
it does not require new kernel APIs. It provides clean
service environments, orderings and dependencies between
services, parallelized startup and shutdown (including
<tt>fsck</tt>), strictly size-capped and autorotated logging,
the service manager as a "subreaper", and uses
<tt>kevent(2)</tt> for event-driven parallelism.</p>
<p>Since the last status report, in December 2015, the project
has seen: restructured and finer-grained packaging that has
fewer conflicts with other toolsets; the addition of
<tt>zsh</tt> completion files; improvements to the virtual
terminal subsystem, keyboard map, mouse support, and ugen and
DECSCUSR support; RFC 5424/5426 remote logging support;
replacement of libkqueue and the C library's environment
handling functions; several new helper commands; support for
Java VM autolocation; improved socket-passing code; an
extended status API and "one-shot" service support;
additional pre-supplied service bundles; support for service
aliases; improved handling of per-user D-Bus services;
improved importing of MySQL, MariaDB, Percona, and OpenVPN
services; improved configuration import support; and extensive
additions to the <tt>nosh</tt> Guide.</p>
<p>On the recently updated roadmap you can see plans for even
more documentation, continuing the work to extend the
capabilities of the networking subsystem, and the scant
handful of <tt>rc.d</tt>-related items remaining. There are
also some ideas still in the speculative or planning phases,
including work that may depend on incorporating <tt>nosh</tt>
support into other software.</p>
<h3>Open tasks:</h3><ol><li>Improve Ansible and SaltStack integration (the maintainer
of the Arch Linux <tt>nosh</tt> integration has some
ideas).</li><li>Command-line completions are still needed for
<tt>bash</tt>, <tt>csh</tt>, and <tt>fish</tt>.</li><li>Document <tt>convert-systemd-units</tt> for use by port
maintainers in making packaged service bundles from
<tt>systemd</tt> unit files.</li><li><tt>nosh</tt> could take advantage of several proposed
features for the base system:
<ul>
<li>the boot loader signaling "emergency" and
"rescue" modes of operation</li>
<li>adding machine-readable status output to
<tt>fsck</tt></li>
<li>adding runtime support for more
<tt>clang</tt>-compilable languages in the early bootstrap
stage</li>
<li>adding hooks for invoking external configuration import
mechanisms</li>
</ul>
</li></ol><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>
|
