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
|
<?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 report covers FreeBSD-related projects between October and
December 2013. This is the last of four reports planned for
2013.</p><p>The last quarter of 2013 was very active for the FreeBSD
community, much like the preceding quarters. Many advances were
made in getting FreeBSD to run on ARM-based System-on-Chip boards
like Cubieboard, Rockchip, Snapdragon, S4, Freescale i.MX6, and
Vybrid VF6xx. FreeBSD is also becoming a better platform for Xen
and the Amazon Elastic Compute Cloud. There are plans for FreeBSD
to become a fully supported compute host for OpenStack. The I/O
stack has again received some performance boosts on
multi-processor systems through work touching the CAM and GEOM
subsystems, and through better adaptation of UMA caches to
system memory constraints for ZFS. The FreeBSD Foundation did an
excellent job in this quarter, and many of their sponsored
projects like VT-d and UEFI support, iSCSI stack, Capsicum, and
auditdistd are about to complete. At the same time, new projects
like Automounter and Intel GPU updates have just been launched.
The Newcons project has been merged into -CURRENT, which will
make it possible to finally move to the latest version of X.Org
in the Ports Collection. Efforts are also under way to improve
testing with Jenkins and Kyua. It is an exciting time for users
and developers of FreeBSD!</p><p>Thanks to all the reporters for the excellent work! This report
contains 37 entries and we hope you enjoy reading it.</p><p>The deadline for submissions covering between January and
March 2014 is April 7th, 2014.</p><hr /><h3><a href="#FreeBSD-Team-Reports">FreeBSD Team Reports</a></h3><ul><li><a href="#FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></li><li><a href="#FreeBSD-Core-Team">FreeBSD Core Team</a></li><li><a href="#FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></li><li><a href="#FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></li><li><a href="#FreeBSD-Release-Engineering-Team">FreeBSD Release Engineering Team</a></li></ul><h3><a href="#Projects">Projects</a></h3><ul><li><a href="#CBSD">CBSD</a></li><li><a href="#Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></li></ul><h3><a href="#Kernel">Kernel</a></h3><ul><li><a href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></li><li><a href="#Intel-802.11n-NIC-(iwn(4))-Work">Intel 802.11n NIC (iwn(4)) Work</a></li><li><a href="#Intel-GPU-Driver-Update">Intel GPU Driver Update</a></li><li><a href="#Native-iSCSI-Stack">Native iSCSI Stack</a></li><li><a href="#New-Automounter">New Automounter</a></li><li><a href="#UEFI-Boot">UEFI Boot</a></li><li><a href="#UMA/ZFS-and-RPC/NFS-Performance-Improvements">UMA/ZFS and RPC/NFS Performance Improvements</a></li><li><a href="#Updated-vt(9)-System-Console">Updated vt(9) System Console</a></li></ul><h3><a href="#Architectures">Architectures</a></h3><ul><li><a href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></li><li><a href="#FreeBSD-on-Cubieboard{1,2}">FreeBSD on Cubieboard{1,2}</a></li><li><a href="#FreeBSD-on-Freescale-i.MX6-processors">FreeBSD on Freescale i.MX6 processors</a></li><li><a href="#FreeBSD-on-Freescale-Vybrid-VF6xx">FreeBSD on Freescale Vybrid VF6xx</a></li><li><a href="#FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></li><li><a href="#FreeBSD/EC2">FreeBSD/EC2</a></li><li><a href="#FreeBSD/Xen">FreeBSD/Xen</a></li><li><a href="#Intel-IOMMU-(VT-d,-DMAR)-Support">Intel IOMMU (VT-d, DMAR) Support</a></li></ul><h3><a href="#Userland-Programs">Userland Programs</a></h3><ul><li><a href="#auditdistd(8)">auditdistd(8)</a></li><li><a href="#Base-GCC-Updates">Base GCC Updates</a></li><li><a href="#BSDInstall-ZFSBoot">BSDInstall ZFSBoot</a></li><li><a href="#Capsicum-and-Casper">Capsicum and Casper</a></li><li><a href="#Centralized-Panic-Reporting">Centralized Panic Reporting</a></li><li><a href="#FreeBSD-Test-Suite">FreeBSD Test Suite</a></li><li><a href="#The-LLDB-Debugger">The LLDB Debugger</a></li></ul><h3><a href="#Ports">Ports</a></h3><ul><li><a href="#FreeBSD-Python-Ports">FreeBSD Python Ports</a></li><li><a href="#GNOME/FreeBSD">GNOME/FreeBSD</a></li><li><a href="#KDE/FreeBSD">KDE/FreeBSD</a></li><li><a href="#Wine/FreeBSD">Wine/FreeBSD</a></li><li><a href="#X.Org-on-FreeBSD">X.Org on FreeBSD</a></li><li><a href="#Xfce/FreeBSD">Xfce/FreeBSD</a></li></ul><h3><a href="#Miscellaneous">Miscellaneous</a></h3><ul><li><a href="#The-FreeBSD-Foundation">The FreeBSD Foundation</a></li></ul><ul></ul><hr /><br /><h1><a name="FreeBSD-Team-Reports" href="#FreeBSD-Team-Reports" id="FreeBSD-Team-Reports">FreeBSD Team Reports</a></h1><br /><h2><a name="FreeBSD-Cluster-Administration-Team" href="#FreeBSD-Cluster-Administration-Team" id="FreeBSD-Cluster-Administration-Team">FreeBSD Cluster Administration Team</a></h2><p>
Contact: FreeBSD Cluster Administration Team <<a href="mailto:admins@">admins@</a>>
</p>
<p>The FreeBSD Cluster Administration Team consists of the people
responsible for administering the machines that the project
relies on for its distributed work and communications to be
synchronised. In the last quarter of 2013, they continued
general maintenance of the FreeBSD cluster across all sites.</p>
<p>In addition to general upkeep tasks, additional
cluster-related items were addressed. Some of these
items include:</p>
<ul>
<li>Added several machines for the Kyua testing framework.</li>
<li>Replaced failed hardware hosting various web services.</li>
<li>Coordinated with the FreeBSD Security Officer and Ports
Management Teams to implement signed binary packages.</li>
<li>Added the <tt>redports.org</tt> machines to the list of
machines managed by the Cluster Administration Team.</li>
<li>Began discussion with contacts at Yandex regarding the
addition of a mirror site for binary packages and Subversion
repositories.</li>
</ul>
<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 constitutes the project's <q>Board of
Directors</q>, responsible for deciding the project's overall
goals and direction as well as managing specific areas of the
FreeBSD project landscape.</p>
<p>In the fourth quarter of 2013, the Core Team finally reached
its previous goal of launching the official repositories for
<tt>pkg(8)</tt>-based binary packages. The Core Team also
unified the commit bit expiration policies for all Project
repositories, allowing committers to idle for 18 months before
their commit bits are automatically taken into safekeeping.
This was then followed by an extension to suspension of cluster
accounts for the committers who lost all of their commit bits.
This helps to improve the security of the Project server cluster
by temporarily disabling inactive accounts. In addition to the
above efforts, Thomas Abthorpe resurrected the <q>Grim
Reaper</q> service which helps to enforce the aforementioned
policy.</p>
<p>With the work of John Baldwin, Hiroki Sato, and others, many
licenses in the base system source code have been revisited and
cleaned up. Furthermore, the Core Team is hoping that the
situation can be improved by introducing periodic automated
checks of the license agreements, and by providing developers
guidelines on questions of licensing. John Baldwin and David
Chisnall have been guiding the work of the FreeBSD Graphics Team on
moving to the newer version of X.Org and related software in the
Ports Collection, in coordination with the switch to Newcons on
FreeBSD 10.x.</p>
<p>It was a busy quarter for the src repository as well. The Core
Team was happy to welcome Jordan K. Hubbard (<tt>jkh</tt>) back,
who has recently returned to the FreeBSD business, and joined
iXsystems as project manager and release engineer of FreeNAS.
In addition to this, there were three commit bits offered for new
developers, two committers were upgraded, one commit bit was taken
for safekeeping, and one src bit was reactivated.</p>
<hr /><h2><a name="FreeBSD-Port-Management-Team" href="#FreeBSD-Port-Management-Team" id="FreeBSD-Port-Management-Team">FreeBSD Ports Management Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/ports/" title="http://www.FreeBSD.org/ports/"></a></td><td>
URL: <a href="http://www.FreeBSD.org/ports/" title="">http://www.FreeBSD.org/ports/</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="http://www.freebsd.org/doc/en/articles/contributing-ports/"></a></td><td>
URL: <a href="http://www.freebsd.org/doc/en/articles/contributing-ports/" title="">http://www.freebsd.org/doc/en/articles/contributing-ports/</a></td></tr><tr><td><a href="http://portsmon.freebsd.org/index.html" title="http://portsmon.freebsd.org/index.html"></a></td><td>
URL: <a href="http://portsmon.freebsd.org/index.html" title="">http://portsmon.freebsd.org/index.html</a></td></tr><tr><td><a href="http://www.freebsd.org/portmgr/index.html" title="http://www.freebsd.org/portmgr/index.html"></a></td><td>
URL: <a href="http://www.freebsd.org/portmgr/index.html" title="">http://www.freebsd.org/portmgr/index.html</a></td></tr><tr><td><a href="http://blogs.freebsdish.org/portmgr/" title="http://blogs.freebsdish.org/portmgr/"></a></td><td>
URL: <a href="http://blogs.freebsdish.org/portmgr/" title="">http://blogs.freebsdish.org/portmgr/</a></td></tr><tr><td><a href="http://www.twitter.com/freebsd_portmgr/" title="http://www.twitter.com/freebsd_portmgr/"></a></td><td>
URL: <a href="http://www.twitter.com/freebsd_portmgr/" title="">http://www.twitter.com/freebsd_portmgr/</a></td></tr><tr><td><a href="http://www.facebook.com/portmgr" title="http://www.facebook.com/portmgr"></a></td><td>
URL: <a href="http://www.facebook.com/portmgr" title="">http://www.facebook.com/portmgr</a></td></tr><tr><td><a href="http://plus.google.com/communities/108335846196454338383" title="http://plus.google.com/communities/108335846196454338383"></a></td><td>
URL: <a href="http://plus.google.com/communities/108335846196454338383" title="">http://plus.google.com/communities/108335846196454338383</a></td></tr></table><p>
Contact: FreeBSD Ports Management Team <<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>>
</p>
<p>The FreeBSD Ports collection is a package management system for
the FreeBSD operating system, providing an easy and consistent way of
installing software packages. The FreeBSD Ports Collection now
contains approximately 24,500 ports, while the PR count exceeds
1,900.</p>
<p>The FreeBSD Ports Management Team ensures that the FreeBSD ports
developer community provides a Ports Collection that is
functional, stable, up-to-date, and full-featured. Its secondary
responsibility is to coordinate among the committers and
developers who work on it. As part of these efforts, we added three
new committers, took in three commit bits for safe keeping, and
reinstated one commit bit in the fourth quarter of 2013.</p>
<p>Ongoing effort went into testing larger changes, as many as eight a
week, including sweeping changes to the tree, moderization of
the infrastructure, and basic quality assurance (QA) runs. Many
iterations of tests against <tt>10.0-RELEASE</tt> were run to
ensure that the maximum number of packages would be available
for the release.</p>
<p>We now have <tt>pkg(8)</tt> packages for the releases 8.3, 8.4,
9.1, 9.2, 10.0 and -CURRENT on <tt>pkg.FreeBSD.org</tt>. During
this same time, further enhancements were put into
<tt>pkg(8)</tt>, including secure package signing.</p>
<p>Commencing November 1, the Ports Management Team undertook a
<q>portmgr-lurkers</q> pilot project in which ports committers
could volunteer to assist the Ports Management Team for a
four-month duration. The first two candiates are Mathieu Arnold
(<tt>mat</tt>) and Antoine Brodin (<tt>antoine</tt>).</p>
<p>Ongoing maintenance goes into <tt>redports.org</tt>, including
QAT runs, ports and security updates.</p>
<h3>Open tasks:</h3><ol><li>As previously noted, many PRs continue to languish; we would
like to see some committers dedicate themselves to closing as many
as possible!</li></ol><hr /><h2><a name="FreeBSD-Postmaster-Team" href="#FreeBSD-Postmaster-Team" id="FreeBSD-Postmaster-Team">FreeBSD Postmaster Team</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/svn-src-stable-10" title="http://lists.freebsd.org/mailman/listinfo/svn-src-stable-10"></a></td><td>
URL: <a href="http://lists.freebsd.org/mailman/listinfo/svn-src-stable-10" title="">http://lists.freebsd.org/mailman/listinfo/svn-src-stable-10</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/ctm-src-10" title="http://lists.freebsd.org/mailman/listinfo/ctm-src-10"></a></td><td>
URL: <a href="http://lists.freebsd.org/mailman/listinfo/ctm-src-10" title="">http://lists.freebsd.org/mailman/listinfo/ctm-src-10</a></td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/ctm-src-10-fast" title="http://lists.freebsd.org/mailman/listinfo/ctm-src-10-fast"></a></td><td>
URL: <a href="http://lists.freebsd.org/mailman/listinfo/ctm-src-10-fast" title="">http://lists.freebsd.org/mailman/listinfo/ctm-src-10-fast</a></td></tr><tr><td><a href="http://www.freebsd.org/doc/en/articles/committers-guide/pgpkeys.html" title="http://www.freebsd.org/doc/en/articles/committers-guide/pgpkeys.html">OpenPGP Keys section in the Committer's Guide</a></td><td>
URL: <a href="http://www.freebsd.org/doc/en/articles/committers-guide/pgpkeys.html" title="OpenPGP Keys section in the Committer's Guide">http://www.freebsd.org/doc/en/articles/committers-guide/pgpkeys.html</a></td></tr></table><p>
Contact: FreeBSD Postmaster Team <<a href="mailto:postmaster@FreeBSD.org">postmaster@FreeBSD.org</a>>
</p>
<p>In the fourth quarter of 2013, the FreeBSD Postmaster Team has
implemented the following items that may be interest of the
general public:</p>
<ul>
<li>Retired the <tt>freebsd-aic7xxx</tt> mailing list.</li>
<li>Created a <tt>graphics-team</tt> alias, requested by Niclas
Zeising.</li>
<li>Worked with the FreeBSD Ports Management Team to set up
<tt>portmgr-lurkers</tt> so port managers can move addresses
between those two aliases at their discretion.</li>
<li>Created the lists associated with the new <tt>stable/10</tt>
branch: <tt>svn-src-stable-10</tt>, <tt>ctm-src-10</tt>, and
<tt>ctm-src-10-fast</tt>.</li>
<li>Redirected the <tt>vbox</tt> alias to the <tt>emulation</tt>
list, requested by Bernhard Fröhlich.</li>
<li>Continued a discussion on current and possible future mail
and spam filtering.</li>
<li>Disbanded <tt>lua</tt> and transferred it to Baptiste
Daroussin, requested by Matthias Andree and Baptiste
Daroussin.</li>
<li>Modified the list moderators/administrators for
<tt>ports-secteam</tt>, requested by Dag-Erling Smørgrav.</li>
<li>Assisted Warren Block with an update to the "OpenPGP Keys
for FreeBSD" section of the Committer's Guide.</li>
</ul>
<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="http://www.FreeBSD.org/releases/10.0R/schedule.html" title="http://www.FreeBSD.org/releases/10.0R/schedule.html">FreeBSD 10.0-RELEASE schedule</a></td><td>
URL: <a href="http://www.FreeBSD.org/releases/10.0R/schedule.html" title="FreeBSD 10.0-RELEASE schedule">http://www.FreeBSD.org/releases/10.0R/schedule.html</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/">FreeBSD Virtual Machine Images</a></td><td>
URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/" title="FreeBSD Virtual Machine Images">http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/VM-IMAGES/</a></td></tr><tr><td><a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/">FreeBSD Development Snapshots</a></td><td>
URL: <a href="http://ftp.FreeBSD.org/pub/FreeBSD/snapshots/ISO-IMAGES/" title="FreeBSD Development Snapshots">http://ftp.FreeBSD.org/pub/FreeBSD/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 finishing the
10.0-RELEASE cycle. The release cycle changed with two
last-minute release candidate builds, each addressing
fixes critical to include in the final release.</p>
<p>The FreeBSD 10.0-RELEASE cycle is expected to be completed by
mid-January, approximately eight weeks behind the original
schedule.</p>
<hr /><br /><h1><a name="Projects" href="#Projects" id="Projects">Projects</a></h1><br /><h2><a name="CBSD" href="#CBSD" id="CBSD">CBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.bsdstore.ru" title="http://www.bsdstore.ru"></a></td><td>
URL: <a href="http://www.bsdstore.ru" title="">http://www.bsdstore.ru</a></td></tr><tr><td><a href="https://github.com/olevole/cbsd" title="https://github.com/olevole/cbsd"></a></td><td>
URL: <a href="https://github.com/olevole/cbsd" title="">https://github.com/olevole/cbsd</a></td></tr></table><p>
Contact:
Oleg
Ginzburg
<<a href="mailto:olevole@olevole.ru">olevole@olevole.ru</a>>
</p>
<p>CBSD is another FreeBSD jail management solution, aimed at
combining various features, such as <tt>racct(8)</tt>,
<tt>vnet</tt>, <tt>zfs(8)</tt>, <tt>carp(4)</tt>, and
<tt>hastd(8)</tt>, into a single tool. This provides a more
comprehensive way to build application servers using
pre-installed jails with a typical set of software, and requires
minimal effort to configure.</p>
<h3>Open tasks:</h3><ol><li>Proper English translation of the website and the
documentation.</li></ol><hr /><h2><a name="Jenkins-Continuous-Integration-for-FreeBSD" href="#Jenkins-Continuous-Integration-for-FreeBSD" id="Jenkins-Continuous-Integration-for-FreeBSD">Jenkins Continuous Integration for FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/" title="http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/">Vendor Summit presentation</a></td><td>
URL: <a href="http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/" title="Vendor Summit presentation">http://www.ixsystems.com/whats-new/jenkins-bhyve-and-webdriver-continuous-integration-testing-on-freenas/</a></td></tr></table><p>
Contact:
Craig
Rodrigues
<<a href="mailto:rodrigc@FreeBSD.org">rodrigc@FreeBSD.org</a>>
</p>
<p>At the November 2013 FreeBSD Vendor Summit, some work was
presented that Craig Rodrigues has been doing with Continuous
Integration and Testing at iXsystems. Craig's presentation
described how iXsystems is using modern best practices for
building and testing the FreeNAS code. Jenkins is a framework
for doing continuous builds and integration that is used by
hundreds of companies. BHyve (BSD Hypvervisor) is the new
virtual machine system which will be part of FreeBSD 10.
Webdriver is a Python toolkit for testing web applications. By
combining these technologies, iXsystems is developing a modern
and sophisticated workflow for testing and improving the quality
of FreeNAS.</p>
<p>Ed Maste from The FreeBSD Foundation was interested in this work,
and based on this interest, it is now being ported to FreeBSD.
Currently, a machine in the FreeBSD cluster has been allocated for
this purpose, where a <tt>bhyve(4)</tt>-based virtual machine
was set up and Jenkins was installed. The remainder is still in
progress.</p>
<h3>Open tasks:</h3><ol><li>Finish setting up Jenkins.</li><li>Add more builds to Jenkins.</li><li>Integrate testing with Jenkins.</li></ol><hr /><br /><h1><a name="Kernel" href="#Kernel" id="Kernel">Kernel</a></h1><br /><h2><a name="GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking" href="#GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking" id="GEOM-Direct-Dispatch-and-Fine-Grained-CAM-Locking">GEOM Direct Dispatch and Fine-Grained CAM Locking</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://people.freebsd.org/~mav/disk.pdf" title="http://people.freebsd.org/~mav/disk.pdf">Slides from EuroBSDCon 2013, also describing this project</a></td><td>
URL: <a href="http://people.freebsd.org/~mav/disk.pdf" title="Slides from EuroBSDCon 2013, also describing this project">http://people.freebsd.org/~mav/disk.pdf</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/260387" title="http://svnweb.freebsd.org/changeset/base/260387">CAM improvements in the stable/10 branch</a></td><td>
URL: <a href="http://svnweb.freebsd.org/changeset/base/260387" title="CAM improvements in the stable/10 branch">http://svnweb.freebsd.org/changeset/base/260387</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/260385" title="http://svnweb.freebsd.org/changeset/base/260385">GEOM improvements in the stable/10 branch</a></td><td>
URL: <a href="http://svnweb.freebsd.org/changeset/base/260385" title="GEOM improvements in the stable/10 branch">http://svnweb.freebsd.org/changeset/base/260385</a></td></tr></table><p>
Contact:
Alexander
Motin
<<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>>
</p>
<p>The CAM and GEOM multi-processor scalability improvement
project has completed. The corresponding code has been committed
to FreeBSD <tt>head</tt> and recently merged to the
<tt>stable/10</tt> branch; it shall appear in
<tt>10.1-RELEASE</tt>.</p>
<p>As part of this project, <tt>cam(4)</tt> (the ATA/SCSI subsystem)
has received more fine-grained locking for better utilization of
multi-core systems. In addition, the locking in <tt>geom(4)</tt>
(the block storage subsystem) has also been polished, and a new
direct dispatch functionality was implemented to spread the load
between multiple threads and processors, and reduce the number
of context switches.</p>
<p>Thanks to these <tt>cam(4)</tt> and <tt>geom(4)</tt> changes,
the peak I/O rate has doubled on contemporary hardware, reaching
up to 1,000,000 IOPS!</p>
<p>This project was sponsored by iXsystems, Inc.</p><h3>Open tasks:</h3><ol><li>Some CAM controller drivers (SIMs) could also be optimized
to get more benefits from this project, utilizing the new locking
models and direct command completions from multiple interrupt
threads.</li></ol><hr /><h2><a name="Intel-802.11n-NIC-(iwn(4))-Work" href="#Intel-802.11n-NIC-(iwn(4))-Work" id="Intel-802.11n-NIC-(iwn(4))-Work">Intel 802.11n NIC (iwn(4)) Work</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr></table><p>
Contact:
Adrian
Chadd
<<a href="mailto:adrian@freebsd.org">adrian@freebsd.org</a>>
</p>
<p>There has been a large amount of work on <tt>iwn(4)</tt> over
the last six months:</p>
<ul>
<li>New hardware support: 2xxx, 6xxx, 1xx series hardware.</li>
<li>Many bugs were fixed, including scanning, association, EAPOL
related fixes.</li>
<li><tt>iwn(4)</tt> now natively works with 802.11n rates from the
net80211 rate control code, rather than mapping non-11n rates to 11n
rates.</li>
</ul>
<h3>Open tasks:</h3><ol><li>There are still some scan hangs, due to how net80211 scans a
single channel at a time. This needs to be resolved.</li><li>The transmit, receive, scan and calibration code needs to be
refactored out of <tt>if_iwn.c</tt> and into separate source
files.</li><li>There still seem to be some issues surrounding 2 GHz
versus 5 GHz association attempts leading to firmware
assertions, especially on the Intel 4965 NIC.</li></ol><hr /><h2><a name="Intel-GPU-Driver-Update" href="#Intel-GPU-Driver-Update" id="Intel-GPU-Driver-Update">Intel GPU Driver Update</a></h2><p>
Contact:
Konstantin
Belousov
<<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>>
</p>
<p>This project will update the Intel graphics chipset driver,
<tt>i915kms</tt>, to a recent snapshot of the Linux upstream
code. The update will provide at least 1.5 years of bugfixes
from the Intel team, and introduce support for the newest
hardware — in particular Haswell and ValleyView. The
IvyBridge code will also be updated. The addition of several
features which are required to update X.Org and Mesa
is also planned.</p>
<p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Native-iSCSI-Stack" href="#Native-iSCSI-Stack" id="Native-iSCSI-Stack">Native iSCSI Stack</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="https://wiki.freebsd.org/Native%20iSCSI%20target"></a></td><td>
URL: <a href="https://wiki.freebsd.org/Native%20iSCSI%20target" title="">https://wiki.freebsd.org/Native%20iSCSI%20target</a></td></tr></table><p>
Contact:
Edward Tomasz
Napierała
<<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>>
</p>
<p>iSCSI is a popular block storage protocol. Under this project,
a new, fast, and reliable kernel-based iSCSI initiator (client)
and target (server) have been implemented.</p>
<p>During October to December, the work focused on performance and
scalability. The target and the initiator now spread the load
over multiple kernel threads, and the locking is optimized to
reduce contention. This makes better use of multiple processor
cores.</p>
<p>Work to finish iSER support is ongoing. All those
optimizations will be gradually merged to <tt>head</tt> in
February, and are expected to merged back to <tt>stable/10</tt>
and finally arrive in <tt>10.1-RELEASE</tt>.</p>
<p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="New-Automounter" href="#New-Automounter" id="New-Automounter">New Automounter</a></h2><p>
Contact:
Edward Tomasz
Napierała
<<a href="mailto:trasz@FreeBSD.org">trasz@FreeBSD.org</a>>
</p>
<p>Research and prototyping has begun on a new project to
implement <tt>autofs(4)</tt> — an automounter filesystem
— and its userland counterpart, <tt>automountd(8)</tt>.
The idea is to provide a very similar user experience to the
automounters available on Linux, MacOS X, and Solaris, including
using the same map format. The automounter will also integrate
with directory services, such as LDAP.</p>
<p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="UEFI-Boot" href="#UEFI-Boot" id="UEFI-Boot">UEFI Boot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/UEFI" title="https://wiki.freebsd.org/UEFI">UEFI wiki page</a></td><td>
URL: <a href="https://wiki.freebsd.org/UEFI" title="UEFI wiki page">https://wiki.freebsd.org/UEFI</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/base/projects/uefi/" title="http://svnweb.freebsd.org/base/projects/uefi/">UEFI project branch</a></td><td>
URL: <a href="http://svnweb.freebsd.org/base/projects/uefi/" title="UEFI project branch">http://svnweb.freebsd.org/base/projects/uefi/</a></td></tr></table><p>
Contact:
Ed
Maste
<<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>>
</p>
<p>The Unified Extensible Firmware Interface (UEFI) provides boot-
and run-time services for x86 computers, and is a replacement for
the legacy BIOS. This project will adapt the FreeBSD loader and
kernel boot process for compatibility with UEFI firmware, found
on contemporary servers, desktops, and laptops.</p>
<p>In 2013, The FreeBSD Foundation sponsored Benno Rice for a short
project to improve the UEFI bootloader. This resulted in a
working proof-of-concept in the UEFI project branch, but it was
not ready to be merged to FreeBSD <tt>head</tt>.</p>
<p>Ed Maste has taken that original work and, with review feedback
from Konstantin Belousov, been preparing it for integration into
FreeBSD <tt>head</tt>. Some changes have been merged to
<tt>head</tt> already. The rest will be merged as they are
refined.</p>
<p>Intel provided a motherboard and CPU for the project, which
proved invaluable for addressing bugs that did not appear while
testing with the QEMU emulator.</p>
<p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Resolve a 32- versus 64-bit <tt>libstand(3)</tt> build issue.</li><li>Merge kernel parsing of EFI memory map metadata.</li><li>Integrate the EFI framebuffer with <tt>vt(9)</tt> (also
known as Newcons).</li><li>Connect <tt>efiloader</tt> to the build.</li><li>Document manual installation for dual-boot configurations.</li><li>Integrate UEFI configuration with the FreeBSD installer.</li><li>Support secure boot.</li></ol><hr /><h2><a name="UMA/ZFS-and-RPC/NFS-Performance-Improvements" href="#UMA/ZFS-and-RPC/NFS-Performance-Improvements" id="UMA/ZFS-and-RPC/NFS-Performance-Improvements">UMA/ZFS and RPC/NFS Performance Improvements</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://docs.freebsd.org/cgi/mid.cgi?52894C92.60905" title="http://docs.freebsd.org/cgi/mid.cgi?52894C92.60905">Discussion of the ZFS/UMA changes</a></td><td>
URL: <a href="http://docs.freebsd.org/cgi/mid.cgi?52894C92.60905" title="Discussion of the ZFS/UMA changes">http://docs.freebsd.org/cgi/mid.cgi?52894C92.60905</a></td></tr></table><p>
Contact:
Alexander
Motin
<<a href="mailto:mav@FreeBSD.org">mav@FreeBSD.org</a>>
</p>
<p>The performance of ZFS and NFS was suboptimal in FreeBSD, so we
have recently investigated some possible improvement paths. The
<tt>uma(9)</tt> memory allocator caching code was improved to
adapt better to system memory constraints. Combined with other
virtual memory subsystem improvements done in the previous
years, it should be safe to actively use <tt>uma(9)</tt> caches
now. Their use in ZFS for ZIO/ARC may be enabled via the
<tt>vfs.zfs.zio.use_uma</tt> <tt>loader(8)</tt> tunable, which
is now the default for amd64, where it is recommended. Use of
<tt>uma(9)</tt> caches for LZ4 compression buffers is
unconditionally enabled on all architectures as it is has no
serious drawbacks. On systems with many CPUs, these changes
doubled the performance in the benchmarks.</p>
<p>Several areas of the NFS server stack (RPC, FHA, DRC) got a
number of fixes and performance optimizations that significantly
improve performance and reduce the CPU usage in a number of
tests. Together with the ZFS memory allocator changes mentioned
above, it was possible to reach 200K NFS block read IOPS and 55K
SPEC NFS IOPS.</p>
<p>The code was committed to <tt>head</tt>. The <tt>uma(9)</tt>
ZFS commits have been already merged to <tt>stable/10</tt>, and
the remainder will be done soon as well.</p>
<p>This project was sponsored by iXsystems, Inc.</p><h3>Open tasks:</h3><ol><li>The SPEC NFS test hits lock congestion on several global
locks in the file system layer when a quite intensive
<tt>READDIRPLUS</tt> NFS request is received. Fixing this
problem could improve performance on large systems even
further.</li></ol><hr /><h2><a name="Updated-vt(9)-System-Console" href="#Updated-vt(9)-System-Console" id="Updated-vt(9)-System-Console">Updated vt(9) System Console</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Newcons" title="https://wiki.freebsd.org/Newcons">Project wiki page</a></td><td>
URL: <a href="https://wiki.freebsd.org/Newcons" title="Project wiki page">https://wiki.freebsd.org/Newcons</a></td></tr></table><p>
Contact:
Aleksandr
Rybalko
<<a href="mailto:ray@FreeBSD.org">ray@FreeBSD.org</a>>
<br />
Contact:
Ed
Maste
<<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>>
<br />
Contact:
Ed
Schouten
<<a href="mailto:ed@FreeBSD.org">ed@FreeBSD.org</a>>
</p>
<p>Colloquially known as Newcons, <tt>vt(9)</tt> is a modern
replacement for the existing, quite old, virtual terminal
emulator called <tt>syscons(4)</tt>. Initially motivated by the
lack of Unicode support in <tt>syscons(4)</tt>, the project was
later expanded to cover the new requirement of supporting Kernel
Mode Switching (KMS).</p>
<p>The project is now approaching completion and is ready for
wider testing, as the related code was already merged to FreeBSD
<tt>head</tt>. Hence, <tt>vt(9)</tt> can be tested easily by
replacing the following two lines in the kernel config file:</p>
<pre xml:space="preserve">device sc
device vga</pre>
<p>with the following ones:</p>
<pre xml:space="preserve">device vt
device vt_vga</pre>
<p>Major highlights:</p>
<ul>
<li>Unicode support.</li>
<li>Double-width character support for CJK characters.</li>
<li><tt>xterm(1)</tt>-like terminal emulation.</li>
<li>Support for Kernel Mode Setting (KMS) drivers
(<tt>i915kms</tt>, <tt>radeonkms</tt>).</li>
<li>Support for different fonts per terminal window.</li>
<li>Simplified drivers.</li>
</ul>
<p>Brief status of supported architectures and hardware:</p>
<ul>
<li>amd64 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) — works.</li>
<li>ARM framebuffer — works.</li>
<li>i386 (VGA/<tt>i915kms</tt>/<tt>radeonkms</tt>) — works.</li>
<li>IA64 — untested.</li>
<li>MIPS — untested.</li>
<li>PPC and PPC64 — works, but without X.Org yet.</li>
<li>SPARC — works on certain hardware (e.g., Ultra 5).</li>
<li><tt>vesa(4)</tt> — in progress.</li>
<li>i386/amd64 nVidia driver — need testing.</li>
<li>Xbox framebuffer driver — need testing.</li>
</ul>
<p>Known Issues:</p>
<ul>
<li>Switching to <tt>vty0</tt> from X.Org on Fatal events will not work.</li>
<li>Certain hardware (e.g., Lenovo X220) get a black screen when
i915kms is preloaded.</li>
<li>Scrolling can be slow;</li>
<li>Screen borders are not cleared when changing fonts.</li>
<li><tt>vt(9)</tt> locks up with the <tt>gallant12x22</tt> font in VirtualBox.</li>
</ul>
<p>This project was sponsored by The FreeBSD Foundation.</p><h3>Open tasks:</h3><ol><li>Create sub-directories for <tt>vt(9)</tt> under
<tt>/usr/share/</tt> to store key maps and fonts.</li><li>Implement remaining features supported by
<tt>vidcontrol(1)</tt>.</li><li>Write the <tt>vt(9)</tt> manual page.</li><li>Support keyboard handled directly by device <tt>kbd</tt>
(without <tt>kbdmux(4)</tt>).</li><li>CJK fonts (in progress).</li></ol><hr /><br /><h1><a name="Architectures" href="#Architectures" id="Architectures">Architectures</a></h1><br /><h2><a name="FreeBSD-Host-Support-for-OpenStack-and-OpenContrail" href="#FreeBSD-Host-Support-for-OpenStack-and-OpenContrail" id="FreeBSD-Host-Support-for-OpenStack-and-OpenContrail">FreeBSD Host Support for OpenStack and OpenContrail</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.openstack.org" title="http://www.openstack.org"></a></td><td>
URL: <a href="http://www.openstack.org" title="">http://www.openstack.org</a></td></tr><tr><td><a href="http://www.opencontrail.org" title="http://www.opencontrail.org"></a></td><td>
URL: <a href="http://www.opencontrail.org" title="">http://www.opencontrail.org</a></td></tr><tr><td><a href="https://github.com/Semihalf/openstack-devstack" title="https://github.com/Semihalf/openstack-devstack"></a></td><td>
URL: <a href="https://github.com/Semihalf/openstack-devstack" title="">https://github.com/Semihalf/openstack-devstack</a></td></tr><tr><td><a href="https://github.com/Semihalf/openstack-nova" title="https://github.com/Semihalf/openstack-nova"></a></td><td>
URL: <a href="https://github.com/Semihalf/openstack-nova" title="">https://github.com/Semihalf/openstack-nova</a></td></tr><tr><td><a href="https://github.com/Semihalf/contrail-vrouter" title="https://github.com/Semihalf/contrail-vrouter"></a></td><td>
URL: <a href="https://github.com/Semihalf/contrail-vrouter" title="">https://github.com/Semihalf/contrail-vrouter</a></td></tr><tr><td><a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" title="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node"></a></td><td>
URL: <a href="https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node" title="">https://blueprints.launchpad.net/nova/+spec/freebsd-compute-node</a></td></tr></table><p>
Contact:
Grzegorz
Bernacki
<<a href="mailto:gjb@semihalf.com">gjb@semihalf.com</a>>
<br />
Contact:
Michał
Dubiel
<<a href="mailto:md@semihalf.com">md@semihalf.com</a>>
<br />
Contact:
Rafał
Jaworowski
<<a href="mailto:raj@semihalf.com">raj@semihalf.com</a>>
</p>
<p>OpenStack is a cloud operating system that controls large pools
of compute, storage, and networking resources in a data center.
OpenContrail is a network virtualization (SDN) solution
comprising a network controller, a virtual router, and an
analytics engine, which can be integrated with cloud
orchestration systems like OpenStack or CloudStack.</p>
<p>The goal of this work is to enable FreeBSD as a fully supported
compute host for OpenStack, using OpenContrail virtualized
networking. The main areas of development are the
following:</p>
<ul>
<li>OpenStack compute driver (<tt>nova-compute</tt>) for the
FreeBSD <tt>bhyve(4)</tt> hypervisor.</li>
<li>OpenContrail vRouter (forwarding-plane kernel module) port
to FreeBSD.</li>
<li>Integration and performance optimizations.</li>
</ul>
<p>The current state of development features a working demo of
OpenStack with compute node components running on a FreeBSD host:</p>
<ul>
<li>The native <tt>bhyve(4)</tt> hypervisor is driven by a
<tt>nova-compute</tt> component for spawning guest instances
and a <tt>nova-network</tt> component for providing simple
networking between those guests.</li>
<li>The <tt>nova-network</tt> approach (based on local host
bridging) is becoming an obsolete technology in OpenStack and
was used here only for demonstration and proof-of-concept
purposes, without exploring all the possible features.</li>
<li>The main objective is to move to OpenContrail-based
networking, therefore becoming compliant with the modern
OpenStack networking API ("neutron").</li>
</ul>
<p>This project was sponsored by Juniper Networks, Inc.</p><h3>Open tasks:</h3><ol><li>Decide how to integrate <tt>bhyve(4)</tt> with
<tt>nova-compute</tt>, either natively or via the
<tt>libvirt</tt> management layer.</li></ol><hr /><h2><a name="FreeBSD-on-Cubieboard{1,2}" href="#FreeBSD-on-Cubieboard{1,2}" id="FreeBSD-on-Cubieboard{1,2}">FreeBSD on Cubieboard{1,2}</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://github.com/tsgan/allwinner_a10/blob/master/if_emac.c" title="https://github.com/tsgan/allwinner_a10/blob/master/if_emac.c">EMAC driver code</a></td><td>
URL: <a href="https://github.com/tsgan/allwinner_a10/blob/master/if_emac.c" title="EMAC driver code">https://github.com/tsgan/allwinner_a10/blob/master/if_emac.c</a></td></tr></table><p>
Contact:
Ganbold
Tsagaankhuu
<<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>>
</p>
<p>Cubieboard is a single-board computer based on the AllWinner
A10 SoC, popular on cheap tablets, phones and media PCs. The
second version enhances the board mainly by replacing the
AllWinner A10 SoC with an AllWinner A20 which contains 2 ARM
Cortex-A7 MPCore CPUs and 2 Mali-400 GPUs (Mali-400MP2). In the
last few months, work has continued on their FreeBSD port, and
some work was done on the EMAC 10/100 Ethernet driver (see
link). The driver is now in a good shape, however the RX side
is very slow and there is need to have an external DMA driver that
can be used in this case.</p>
<hr /><h2><a name="FreeBSD-on-Freescale-i.MX6-processors" href="#FreeBSD-on-Freescale-i.MX6-processors" id="FreeBSD-on-Freescale-i.MX6-processors">FreeBSD on Freescale i.MX6 processors</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-arm/2013-November/006877.html" title="http://lists.freebsd.org/pipermail/freebsd-arm/2013-November/006877.html">Announcement of Wanboard support</a></td><td>
URL: <a href="http://lists.freebsd.org/pipermail/freebsd-arm/2013-November/006877.html" title="Announcement of Wanboard support">http://lists.freebsd.org/pipermail/freebsd-arm/2013-November/006877.html</a></td></tr></table><p>
Contact:
Ian
Lepore
<<a href="mailto:ian@freebsd.org">ian@freebsd.org</a>>
</p>
<p>The i.MX range is a family of Freescale Semiconductor
proprietary microprocessors for multimedia applications based on
the ARM architecture and focused on low power consumption. The
i.MX6x series is based on the ARM Cortex A9 solo, dual, or quad
cores. Initial support for them has been committed to
<tt>head</tt>, and merged to <tt>stable/10</tt>. All members of
the i.MX6 family (Solo, Dual, and Quad core) are supported, but
SMP support on the multi-core SoCs has not yet been enabled.</p>
<p>Initial driver support includes:</p>
<ul>
<li>USB (EHCI)</li>
<li>Ethernet (Gigabit)</li>
<li>SD Card</li>
<li>UART</li>
</ul>
<p>The initial hardware bringup was done on Wandboard hardware,
see the announcement on <tt>freebsd-arm</tt> in the links section
for more information.</p>
<h3>Open tasks:</h3><ol><li>Write drivers for additional on-chip hardware, including
I2C, SPI, AHCI, audio, and video.</li><li>Add support to FreeBSD-crochet script to generate Wandboard
images</li></ol><hr /><h2><a name="FreeBSD-on-Freescale-Vybrid-VF6xx" href="#FreeBSD-on-Freescale-Vybrid-VF6xx" id="FreeBSD-on-Freescale-Vybrid-VF6xx">FreeBSD on Freescale Vybrid VF6xx</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/258057" title="http://svnweb.freebsd.org/changeset/base/258057"></a></td><td>
URL: <a href="http://svnweb.freebsd.org/changeset/base/258057" title="">http://svnweb.freebsd.org/changeset/base/258057</a></td></tr></table><p>
Contact:
Ruslan
Bukin
<<a href="mailto:br@freebsd.org">br@freebsd.org</a>>
</p>
<p>Basic support for the Freescale Vybrid Family VF6xx
heterogeneous ARM Cortex-A5/M4 System-on-Chip (SoC) was added to
FreeBSD <tt>head</tt>. The Vybrid VF6xx family is an
implementation of the new modern Cortex-A5-based low-power ARM
SoC boards. Vybrid devices are ideal for applications including
simple HMI in appliances and industrial machines, secure control
of infrastructure and manufacturing equipment, energy conversion
applications such as motor drives and power inverters,
ruggedized wired and wireless connectivity, and control of
mobile battery-operated systems such as robots and industrial
vehicles.</p>
<p>Supported device drivers:</p>
<ul>
<li>NAND Flash Controller (NFC)</li>
<li>USB Enhanced Host Controller Interface (EHCI)</li>
<li>General-Purpose Input/Output (GPIO)</li>
<li>Universal Asynchronous Receiver/Transmitter (UART)</li>
</ul>
<p>Also supported:</p>
<ul>
<li>Generic Interrupt Controller (GIC)</li>
<li>MPCore timer</li>
<li><tt>ffec</tt> Ethernet driver</li>
</ul>
<h3>Open tasks:</h3><ol><li>Add support for a number of different VF5xx- and VF6xx-based
development boards.</li><li>Expand device driver support, including framebuffer and
other devices.</li></ol><hr /><h2><a name="FreeBSD-on-Newer-ARM-Boards" href="#FreeBSD-on-Newer-ARM-Boards" id="FreeBSD-on-Newer-ARM-Boards">FreeBSD on Newer ARM Boards</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/FreeBSD/arm/Radxa%20Rock" title="https://wiki.freebsd.org/FreeBSD/arm/Radxa%20Rock">FreeBSD on Radxa Rock</a></td><td>
URL: <a href="https://wiki.freebsd.org/FreeBSD/arm/Radxa%20Rock" title="FreeBSD on Radxa Rock">https://wiki.freebsd.org/FreeBSD/arm/Radxa%20Rock</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/256949" title="http://svnweb.freebsd.org/changeset/base/256949"></a></td><td>
URL: <a href="http://svnweb.freebsd.org/changeset/base/256949" title="">http://svnweb.freebsd.org/changeset/base/256949</a></td></tr><tr><td><a href="https://github.com/tsgan/qualcomm" title="https://github.com/tsgan/qualcomm">Some preliminary sources for Snapdragon board IFC6410</a></td><td>
URL: <a href="https://github.com/tsgan/qualcomm" title="Some preliminary sources for Snapdragon board IFC6410">https://github.com/tsgan/qualcomm</a></td></tr></table><p>
Contact:
Ganbold
Tsagaankhuu
<<a href="mailto:ganbold@FreeBSD.org">ganbold@FreeBSD.org</a>>
</p>
<p>Rockchip is a series of SoC (System on Chip) integrated
circuits that are mainly for embedded systems applications in
mobile entertainment devices such as smartphones, tablets, e-books,
set-top boxes, media players, personal video, and MP3 players.
Due to their evolution from the MP3/MP4 player market, most
Rockchip ICs feature advanced media decoding logic but lack
integrated cellular radio basebands. Initial support for the
Rockchip RK3188 (Quad core Cortex A9) SoC is committed to
<tt>head</tt>. Now FreeBSD runs on Radxa Rock and it supports
the following peripherals:</p>
<ul>
<li>Existing DWC OTG driver in host mode</li>
<li>GPIO</li>
</ul>
<p>Some work was also done on initial support for the Qualcomm
Snapdragon S4 SoC, featuring the Krait CPU, which is considered
a "platform" for use in smartphones, tablets, and smartbook
devices. Krait has many similarities with the ARM Cortex-A15
CPU and is also based on the ARMv7 instruction set. A minimal
console driver was written, and FreeBSD's early boot messages can
be now seen on the serial console. The timer driver works too,
and the boot now stops at the mountroot prompt.</p>
<hr /><h2><a name="FreeBSD/EC2" href="#FreeBSD/EC2" id="FreeBSD/EC2">FreeBSD/EC2</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/freebsd-on-ec2/" title="http://www.daemonology.net/freebsd-on-ec2/">FreeBSD/EC2 status page</a></td><td>
URL: <a href="http://www.daemonology.net/freebsd-on-ec2/" title="FreeBSD/EC2 status page">http://www.daemonology.net/freebsd-on-ec2/</a></td></tr><tr><td><a href="http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html" title="http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html">Configinit</a></td><td>
URL: <a href="http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html" title="Configinit">http://www.daemonology.net/blog/2013-12-09-FreeBSD-EC2-configinit.html</a></td></tr></table><p>
Contact:
Colin
Percival
<<a href="mailto:cperciva@freebsd.org">cperciva@freebsd.org</a>>
</p>
<p>An Amazon Machine Image (AMI) is a special type of virtual
appliance that is used to create a virtual machine within the
Amazon Elastic Compute Cloud ("EC2"). It serves as the basic
unit of deployment for services delivered using EC2. Such AMIs
are available for <tt>8.3-RELEASE</tt> and later FreeBSD releases,
and every ALPHA, BETA, and RC of FreeBSD 10.0. Starting from
FreeBSD <tt>10.0-BETA1</tt>, FreeBSD/EC2 images are running
"fully supported" FreeBSD binaries, and starting from
FreeBSD <tt>10.0-RC1</tt>, FreeBSD/EC2 images include a
<tt>"configinit"</tt> system for autoconfiguration using EC2
user-data.</p>
<p>Due to limitations of old (<tt>m1</tt>, <tt>m2</tt>,
<tt>c1</tt>, <tt>t1</tt>) instance types,
<tt>"Windows"</tt>-labelled images are required for those
instance types; however all of the recent instances types
— <tt>m3</tt> (general purpose), <tt>c3</tt> (high-CPU),
and <tt>i2</tt> (high-I/O) — support FreeBSD at the
<tt>"unix"</tt> pricing rates.</p>
<p>The maintainer of this platform considers it to be ready for
production use.</p>
<h3>Open tasks:</h3><ol><li>Hand over the task of building FreeBSD AMIs to the Release
Engineering Team.</li><li>Get Amazon to add <tt>"FreeBSD"</tt> to the list of platforms
supported by EC2, so that it can stop showing up as <tt>"Other
Linux"</tt>.</li></ol><hr /><h2><a name="FreeBSD/Xen" href="#FreeBSD/Xen" id="FreeBSD/Xen">FreeBSD/Xen</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="http://wiki.xen.org/wiki/FreeBSD_PVH">FreeBSD PVH wiki page</a></td><td>
URL: <a href="http://wiki.xen.org/wiki/FreeBSD_PVH" title="FreeBSD PVH wiki page">http://wiki.xen.org/wiki/FreeBSD_PVH</a></td></tr></table><p>
Contact:
Roger
Pau Monné
<<a href="mailto:royger@FreeBSD.org">royger@FreeBSD.org</a>>
<br />
Contact:
Justin T.
Gibbs
<<a href="mailto:gibbs@FreeBSD.org">gibbs@FreeBSD.org</a>>
</p>
<p>Xen is a native (bare-metal) hypervisor providing services that
allow multiple computer operating systems to execute on the same
computer hardware concurrently. Xen 4.4 will bring a
virtualization mode called PVH — PV (paravirtualization)
in an HVM (fully-virtual) container. This is essentially a
paravirtualized guest using paravirtualized drivers for boot and
I/O. Otherwise it uses hardware virtualization extensions,
without the need for emulation.</p>
<p>After merging the changes to improve Xen PVHVM
support, work has shifted on getting PVH DomU support on FreeBSD.
Patches have been posted, and after a couple of rounds of review,
the series looks almost ready for merging into <tt>head</tt>.
Also, very initial patches for FreeBSD PVH Dom0 support has been
posted. So far the posted series only focuses on getting FreeBSD
booting as a Dom0 and being able to interact with the
hardware.</p>
<p>This project was sponsored by Citrix Systems R&D, and Spectra Logic Corporation.</p><h3>Open tasks:</h3><ol><li>Finish reviewing and commit the PVH DomU support.</li><li>Work on PVH Dom0 support.</li></ol><hr /><h2><a name="Intel-IOMMU-(VT-d,-DMAR)-Support" href="#Intel-IOMMU-(VT-d,-DMAR)-Support" id="Intel-IOMMU-(VT-d,-DMAR)-Support">Intel IOMMU (VT-d, DMAR) Support</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/257251" title="http://svnweb.freebsd.org/changeset/base/257251"></a></td><td>
URL: <a href="http://svnweb.freebsd.org/changeset/base/257251" title="">http://svnweb.freebsd.org/changeset/base/257251</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/base/259512" title="http://svnweb.freebsd.org/changeset/base/259512"></a></td><td>
URL: <a href="http://svnweb.freebsd.org/changeset/base/259512" title="">http://svnweb.freebsd.org/changeset/base/259512</a></td></tr></table><p>
Contact:
Konstantin
Belousov
<<a href="mailto:kib@FreeBSD.org">kib@FreeBSD.org</a>>
</p>
<p>An Input/Output Memory Management Unit (IOMMU) is a Memory
Management Unit (MMU) that connects a Direct Memory
Access-capable (DMA-capable) I/O bus to main memory; therefore,
I/O virtualization is performed by the chipset. An example
IOMMU is the graphics address remapping table (GART) used by AGP
and PCI Express graphics cards. Intel has published a
specification for IOMMU technology as Virtualization Technology
for Directed I/O, abbreviated VT-d.</p>
<p>A VT-d driver was committed to <tt>head</tt> and
<tt>stable/10</tt>, so <tt>busdma(9)</tt> is now able to utilize
VT-d. The feature is disabled by default, but it may be enabled
via the <tt>hw.dmar.enable</tt> <tt>loader(8)</tt> tunable
— see the links for more information. The immediate plans
include increasing the support for this kind of hardware by
testing and providing workarounds for specific issues, and
by adding features of the next generation of Intel IOMMU.
Hopefully, the existing and new consumers of VT-d will start to
use the driver soon.</p>
<p>This project was sponsored by The FreeBSD Foundation.</p><hr /><br /><h1><a name="Userland-Programs" href="#Userland-Programs" id="Userland-Programs">Userland Programs</a></h1><br /><h2><a name="auditdistd(8)" href="#auditdistd(8)" id="auditdistd(8)">auditdistd(8)</a></h2><p>
Contact:
Pawel Jakub
Dawidek
<<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>>
</p>
<p>The <tt>auditdistd(8)</tt> daemon is responsible for
distributing audit trail files over TCP/IP networks securely and
reliably. Currently, the daemon uses Transport Layer Security
(TLS) for communication, but only server-side certificates are
verified, based on the certificate's fingerprint. The ongoing
work will make it possible to use client-side certificates and
will support more complete public-key infastructure, which
includes validation of the entire certificate chain, including
revocation checking against Certification Revocation Lists at
every level. From now on, <tt>auditdistd(8)</tt> will support
TLSv1.2 and PFS modes only. In addition, it will be possible to
send audit trail files to multiple receivers.</p>
<p>The work will be completed at the beginning of February
2014.</p>
<p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Base-GCC-Updates" href="#Base-GCC-Updates" id="Base-GCC-Updates">Base GCC Updates</a></h2><p>
Contact:
Pedro
Giffuni
<<a href="mailto:pfg@FreeBSD.org">pfg@FreeBSD.org</a>>
</p>
<p>The GCC compiler in the FreeBSD base system is on its way to
deprecation and is only used by some Tier-2 platforms at this
time. While Clang is much better in many aspects, we still
cannot use all the new features that it
brings in the base system until we can drop GCC completely. As a stop-gap
solution, several bug fixes and features from Apple GCC and
other sources have been ported to our version of GCC 4.2.1
to make it more compatible with Clang. FreeBSD's GCC has added
more warnings and some enhancements like <tt>-Wmost</tt> and
<tt>-Wnewline-eof</tt>. An implementation for Apple's blocks
extension is now available, too, and it will be very useful to
enhance FreeBSD's support for Apple's Grand Central Dispatch
(GCD).</p>
<h3>Open tasks:</h3><ol><li>A merge from <tt>head</tt> to <tt>stable/9</tt> is being
considered but it disables nested functions by default, so the
impact on the Ports Collection needs to be evaluated.</li><li>No further development of GCC 4.2 in the base system is
planned.</li></ol><hr /><h2><a name="BSDInstall-ZFSBoot" href="#BSDInstall-ZFSBoot" id="BSDInstall-ZFSBoot">BSDInstall ZFSBoot</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall" title="http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall"></a></td><td>
URL: <a href="http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall" title="">http://lists.freebsd.org/mailman/listinfo/freebsd-sysinstall</a></td></tr><tr><td><a href="https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE" title="https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE">Original Root-on-ZFS instuctions on the FreeBSD Wiki</a></td><td>
URL: <a href="https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE" title="Original Root-on-ZFS instuctions on the FreeBSD Wiki">https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE</a></td></tr></table><p>
Contact:
Allan
Jude
<<a href="mailto:freebsd@allanjude.com">freebsd@allanjude.com</a>>
<br />
Contact:
Devin
Teske
<<a href="mailto:dteske@FreeBSD.org">dteske@FreeBSD.org</a>>
<br />
Contact:
Warren
Block
<<a href="mailto:wblock@FreeBSD.org">wblock@FreeBSD.org</a>>
</p>
<p>BSDInstall has been the default installation program since
FreeBSD <tt>9.0-RELEASE</tt>. However, it could not utilize
one of the best features of FreeBSD, ZFS.</p>
<p>The ZFSBoot project started at EuroBSDCon 2013 and reached
stable status in December, just in time for
FreeBSD <tt>10.0-RELEASE</tt>. Currently, ZFSBoot implements
root-on-ZFS with 4k partition alignment, optional forced 4k
sectors, optional <tt>geli(8)</tt> full disk encryption, and
support for boot environments.</p>
<p>As part of ZFSBoot, BSDInstall itself also received a number of
updates, including enhanced debugging, more scriptability, a new
keymap selection menu, and a number of other small changes to
streamline the installation process. The new keymap menu allows
the user to test the selected keymap before continuing, to
ensure it is the desired keymap. Minor changes were made to the
network configuration dialogues to make the identification of
wireless interfaces easier.</p>
<p>A number of additional features are also planned. The
user should be able to create additional datasets and adjust the properties on
all datasets in an interactive menu. There should also be integration with BSDConfig
to allow users to install packages and the various other
functionality that was previously provided by
<tt>sysinstall</tt>.</p>
<h3>Open tasks:</h3><ol><li>Interactive dataset editor.</li><li>Dataset property editor.</li><li>Consider using shell <tt>geom(4)</tt> parser.</li><li>BSDConfig integration.</li><li>UFS as a file system option, to allow users to create
encrypted UFS installs.</li><li>Optionally make the boot pool UFS or reside on USB
device(s).</li><li>Further streamline the installation process.</li></ol><hr /><h2><a name="Capsicum-and-Casper" href="#Capsicum-and-Casper" id="Capsicum-and-Casper">Capsicum and Casper</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://freebsdfoundation.blogspot.com/2013/12/freebsd-foundation-announces-capsicum.html" title="http://freebsdfoundation.blogspot.com/2013/12/freebsd-foundation-announces-capsicum.html"></a></td><td>
URL: <a href="http://freebsdfoundation.blogspot.com/2013/12/freebsd-foundation-announces-capsicum.html" title="">http://freebsdfoundation.blogspot.com/2013/12/freebsd-foundation-announces-capsicum.html</a></td></tr></table><p>
Contact:
Pawel Jakub
Dawidek
<<a href="mailto:pjd@FreeBSD.org">pjd@FreeBSD.org</a>>
</p>
<p>Capsicum is a lightweight OS capability and sandbox framework
implementing a hybrid capability system model. The Casper
daemon enables sandboxed application to use functionality
normally unavailable in capability-mode sandboxes.</p>
<p>The Casper daemon, <tt>libcasper</tt>, <tt>libcapsicum(3)</tt>,
<tt>libnv(3)</tt> and Casper services (<tt>system.dns</tt>,
<tt>system.grp</tt>, <tt>system.pwd</tt>, <tt>system.random</tt>
and <tt>system.sysctl</tt>) have been committed to FreeBSD
<tt>head</tt>. The <tt>tcpdump(8)</tt> utility in <tt>head</tt>
now uses the <tt>system.dns</tt> service to do DNS lookups. The
<tt>kdump(1)</tt> utility in <tt>head</tt> now uses the
<tt>system.pwd</tt> and <tt>system.grp</tt> services to convert
user and group identifiers to user and group names.</p>
<p>There is ongoing work to sandbox more applications. If you are
interested in helping to make FreeBSD more secure and would like to
learn about Capsicum and Casper, do not hesitate to contact
Pawel — he can provide candidate programs that could use
sandboxing.</p>
<p>This project was sponsored by The FreeBSD Foundation.</p><hr /><h2><a name="Centralized-Panic-Reporting" href="#Centralized-Panic-Reporting" id="Centralized-Panic-Reporting">Centralized Panic Reporting</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html" title="http://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html">Usage instructions</a></td><td>
URL: <a href="http://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html" title="Usage instructions">http://www.daemonology.net/blog/2013-11-06-automated-freebsd-panic-reporting.html</a></td></tr></table><p>
Contact:
Colin
Percival
<<a href="mailto:cperciva@freebsd.org">cperciva@freebsd.org</a>>
</p>
<p>With the <tt>sysutils/panicmail</tt> port, a mechanism is now
in place for automated submission of
kernel panic reports to a central location. It is hoped that
this will prove useful, as similar systems have for other
operating systems, in identifying common panics so that
developers can be alerted and they can be fixed faster.</p>
<p>In the first two months that this mechanism has been in place,
28 kernel panics have been reported. This is nowhere near enough
to be useful, so readers are strongly encouraged to install the
<tt>sysutils/panicmail</tt> port and follow the instructions to
enable it.</p>
<h3>Open tasks:</h3><ol><li>Get more systems set up to automatically submit panic
reports!</li></ol><hr /><h2><a name="FreeBSD-Test-Suite" href="#FreeBSD-Test-Suite" id="FreeBSD-Test-Suite">FreeBSD Test Suite</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/TestSuite" title="http://wiki.FreeBSD.org/TestSuite">Project page</a></td><td>
URL: <a href="http://wiki.FreeBSD.org/TestSuite" title="Project page">http://wiki.FreeBSD.org/TestSuite</a></td></tr><tr><td><a href="http://kyua1.nyi.FreeBSD.org/" title="http://kyua1.nyi.FreeBSD.org/">Continuous testing infrastructure</a></td><td>
URL: <a href="http://kyua1.nyi.FreeBSD.org/" title="Continuous testing infrastructure">http://kyua1.nyi.FreeBSD.org/</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-testing/2013-December/000109.html" title="http://lists.freebsd.org/pipermail/freebsd-testing/2013-December/000109.html">Mailing list announcement</a></td><td>
URL: <a href="http://lists.freebsd.org/pipermail/freebsd-testing/2013-December/000109.html" title="Mailing list announcement">http://lists.freebsd.org/pipermail/freebsd-testing/2013-December/000109.html</a></td></tr><tr><td><a href="http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html" title="http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html">Blog post</a></td><td>
URL: <a href="http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html" title="Blog post">http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html</a></td></tr></table><p>
Contact:
Julio
Merino
<<a href="mailto:jmmv@FreeBSD.org">jmmv@FreeBSD.org</a>>
</p>
<p>The FreeBSD Test Suite project aims to equip FreeBSD with a
comprehensive test suite that is easy to run out of the box and
during the development of the system. The test suite is
installed into <tt>/usr/tests/</tt> and the <tt>kyua(1)</tt>
command-line tool (<tt>devel/kyua</tt> in the Ports Collection)
is used to run them.</p>
<p>The benefits of having a test suite that is easy to use and
continuously run are obvious: regressions can be caught sooner
rather than later and the Release Engineering Team can better
assess the quality of the tree before deciding to cut a release.
Additionally, because we choose to install the tests, we allow
any end user to perform sanity checks on new installations of
the system on their particular hardware configuration — a
very attractive thing to do when deploying production
servers.</p>
<p>During the last few months, we have added the necessary pieces to
the build system to support building and installing test programs of
various kinds. To demonstrate the functionality of these, some test
programs were added and others were migrated from the old testing tree
in <tt>tools/regression/</tt> to the new layout for tests.</p>
<p>The current test suite should be seen as a proof of concept at this
point: it is only composed of a small set of test programs and the goal
is to get the infrastructure in place before mass-migrating existing
test code and/or importing external tests.</p>
<p>As part of this work, two new releases of Kyua were published.
Of special interest is the addition of a TAP-compliant backend so
that existing tests from <tt>tools/regression/</tt> can be
plugged into the test suite with minimum effort.</p>
<p>As of December 31st, the basic continuous testing
infrastructure is up and running, see the links section for the
home page. For further information, please see the related
announcement and blog post on the subject (also in the links
section).</p>
<h3>Open tasks:</h3><ol><li>We have three machines for the test cluster. At the
moment, only one of them is in use to continuously test amd64 on
both <tt>head</tt> and <tt>stable/10</tt>. We need to figure
out the right level of parallelization to put other machines to
use — but a first easy cut may be to just test different
architectures (with the help of QEMU).</li><li>Related to the above, the Kyua reporting engine needs
significant tuning to make the reports nice and clean. Ideally,
Kyua should be able to coalesce results from different runs into
a single location and generate cohesive reports out of them.
Fixing this is a high priority.</li><li>A tutorial on writing tests for FreeBSD has been proposed for
AsiaBSDCon 2014. The outcome of the proposal is still
unknown, but stay tuned!</li><li>Port, port, and port more tests to the new test suite. A
test suite is worthless if it does not validate stuff. Stay tuned
for a request for help once we have put all basic pieces in
place and have streamlined the migration process.</li></ol><hr /><h2><a name="The-LLDB-Debugger" href="#The-LLDB-Debugger" id="The-LLDB-Debugger">The LLDB Debugger</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/lldb" title="https://wiki.freebsd.org/lldb"></a></td><td>
URL: <a href="https://wiki.freebsd.org/lldb" title="">https://wiki.freebsd.org/lldb</a></td></tr></table><p>
Contact:
Ed
Maste
<<a href="mailto:emaste@FreeBSD.org">emaste@FreeBSD.org</a>>
</p>
<p>LLDB is the debugger in the LLVM family of projects. It
supports Mac OS X, Linux, and FreeBSD, with ongoing work to support
Windows.</p>
<p>In the last quarter of 2013, LLDB gained support for live
(<tt>ptrace(2)</tt>-based) debugging of multithreaded processes
on FreeBSD. Initial FreeBSD MIPS target support has also been
committed, along with a number of endianness fixes in the
general LLDB infrastructure.</p>
<p>The LLDB snapshot in the FreeBSD tree was updated to
<tt>r196322</tt>. Currently disabled by default, it will be
enabled for <tt>amd64</tt> after the import of Clang 3.4.
In the interim, it may be enabled by adding <tt>WITH_LLDB=</tt>
to <tt>src.conf(5)</tt>.</p>
<p>This project was sponsored by DARPA/AFRL, SRI International, and University of Cambridge.</p><h3>Open tasks:</h3><ol><li>Update the in-tree snapshot to build after the Clang 3.4
import.</li><li>Fix <tt>amd64</tt> watchpoints.</li><li>Test and fix the <tt>i386</tt> port.</li><li>Implement FreeBSD ARM support.</li><li>Add support for kernel debugging (live local and remote
debugging, and core files).</li><li>Fix the remaining test suite failures.</li><li>Enable by default on the <tt>amd64</tt> architecture.</li></ol><hr /><br /><h1><a name="Ports" href="#Ports" id="Ports">Ports</a></h1><br /><h2><a name="FreeBSD-Python-Ports" href="#FreeBSD-Python-Ports" id="FreeBSD-Python-Ports">FreeBSD Python Ports</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.FreeBSD.org/Python" title="https://wiki.FreeBSD.org/Python">The FreeBSD Python Team page</a></td><td>
URL: <a href="https://wiki.FreeBSD.org/Python" title="The FreeBSD Python Team page">https://wiki.FreeBSD.org/Python</a></td></tr><tr><td><a href="irc://freebsd-python@irc.freenode.net" title="irc://freebsd-python@irc.freenode.net">IRC channel</a></td><td>
URL: <a href="irc://freebsd-python@irc.freenode.net" title="IRC channel">irc://freebsd-python@irc.freenode.net</a></td></tr></table><p>
Contact: FreeBSD Python Team <<a href="mailto:python@FreeBSD.org">python@FreeBSD.org</a>>
</p>
<p>Python is a widely used general-purpose, high-level programming
language. For many operating systems, Python is a standard
component; it ships with FreeBSD as well. A lot of progress has
been made around the FreeBSD Python ports in the last quarter.</p>
<p>The <tt>devel/py-distribute</tt> port has been replaced by the
refreshed <tt>devel/py-setuptools</tt> port, which comes with a
lot of features that simplify the methods of installing Python
packages. The change also led us to install everything through
Setuptools now, which resembles PyIP a bit and allows us to
perform some major cleanup on the distutils installation
behaviour.</p>
<p>The implicit <tt>lang/python</tt> build and run-time dependency
was removed from the ports infrastructure. Every port now
depends on a specific Python version or on the
<tt>lang/python</tt> metaport. This prevents compatibility
issues for ports that depend on Python 2.x OR
Python 3.x exclusively, but use the <tt>python</tt>
command, which might point to a version of incompatible user
choice.</p>
<p>The <tt>lang/python27</tt> port was updated to version 2.7.6,
and the <tt>lang/python33</tt> port was updated to version
3.3.3, and the <tt>lang/pypy</tt> port was updated to version
2.2.1.</p>
<p>We are currently working on the necessary infrastructure quirks
to support different Python versions for the same port. Most of
the work has been done and needs to be tested before it can be
integrated.</p>
<h3>Open tasks:</h3><ol><li>Develop a high-level and lightweight Python Ports Policy.</li><li>Add support for granular dependencies (for example
<tt>>=1.0</tt> or <tt><2.0</tt>).</li><li>Look at what adding <tt>pip</tt> support looks like.</li><li>Convert all <tt>USE_PYDISTUTILS=easy_install</tt> entries to
<tt>yes</tt> and remove the use of <tt>easy_install</tt> from
the ports infrastructure.</li><li>More tasks can be found on the team's wiki page (see
links).</li></ol><hr /><h2><a name="GNOME/FreeBSD" href="#GNOME/FreeBSD" id="GNOME/FreeBSD">GNOME/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSD.org/gnome/" title="http://www.FreeBSD.org/gnome/"></a></td><td>
URL: <a href="http://www.FreeBSD.org/gnome/" title="">http://www.FreeBSD.org/gnome/</a></td></tr><tr><td><a href="http://svnweb.freebsd.org/changeset/ports/334661" title="http://svnweb.freebsd.org/changeset/ports/334661">Import of MATE</a></td><td>
URL: <a href="http://svnweb.freebsd.org/changeset/ports/334661" title="Import of MATE">http://svnweb.freebsd.org/changeset/ports/334661</a></td></tr></table><p>
Contact: FreeBSD GNOME Team <<a href="mailto:gnome@FreeBSD.org">gnome@FreeBSD.org</a>>
</p>
<p>GNOME is a desktop environment and graphical user interface
that runs on top of a computer operating system. GNOME is part
of the GNU Project and can be used with various Unix-like
operating systems, including FreeBSD.</p>
<p>In this quarter, MATE 1.6 was finally imported into the
Ports Collection, thanks to the efforts of Jeremy Messenger.
MATE is a desktop environment forked from the now-unmaintained
code base of GNOME 2, therefore it is basically a
replacement for GNOME 2. Users wanting
to keep GNOME 2 as their desktop are advised to switch to MATE since
GNOME 2 will be replaced by GNOME 3 in the near
future. This switch will be announced in advance, so people
will have time to move to MATE if they have not already. The
complete MATE-based desktop environment can be installed via the
<tt>x11/mate</tt> port, or, for a minimal install,
<tt>x11/mate-base</tt>.</p>
<p>Our home page is quite out of date. An update for it for
GNOME 3.6 is underway. Part of this update is rewriting
and updating the old GNOME porting guide as a chapter of the
Porter's Handbook.</p>
<p>Another major task required for getting a bleeding-edge GNOME
to build on FreeBSD mostly out-of-the box is moving to JHbuild with
some custom rules. This is done to find and fix compile issues
on other BSDs more quickly.</p>
<h3>Open tasks:</h3><ol><li>GNOME 2 ports still need to be sorted out to evaluate
which GNOME 2 components will be gone or be replaced with
their newer GNOME 3 versions. This task is currently halted
until we can get the documentation into a shape good enough to
gather the issues and document the migration, including how
to avoid the migration if the upgrade is not preferred. (This
does not mean we do not want to know about issues with
upgrading, though).</li><li>Help the X11 Team with Cairo 1.12, since the next
version of GNOME 3 (3.12) will need an up-to-date version
of Pango and GTK 3.</li></ol><hr /><h2><a name="KDE/FreeBSD" href="#KDE/FreeBSD" id="KDE/FreeBSD">KDE/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://FreeBSD.kde.org" title="http://FreeBSD.kde.org">KDE/FreeBSD home page</a></td><td>
URL: <a href="http://FreeBSD.kde.org" title="KDE/FreeBSD home page">http://FreeBSD.kde.org</a></td></tr><tr><td><a href="http://FreeBSD.kde.org/area51.php" title="http://FreeBSD.kde.org/area51.php">area51</a></td><td>
URL: <a href="http://FreeBSD.kde.org/area51.php" title="area51">http://FreeBSD.kde.org/area51.php</a></td></tr><tr><td><a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="http://portscout.freebsd.org/kde@freebsd.org.html">Out-of-date ports</a></td><td>
URL: <a href="http://portscout.freebsd.org/kde@freebsd.org.html" title="Out-of-date ports">http://portscout.freebsd.org/kde@freebsd.org.html</a></td></tr></table><p>
Contact: KDE FreeBSD Team <<a href="mailto:kde@FreeBSD.org">kde@FreeBSD.org</a>>
</p>
<p>KDE is an international free software community producing an
integrated set of cross-platform applications designed to run on
Linux, FreeBSD, Solaris, Microsoft Windows, and OS X systems. The
KDE/FreeBSD Team have continued to improve the experience of KDE
software and Qt under FreeBSD.</p>
<p>During the last quarter, the team has kept most of the KDE and Qt
ports up-to-date, working on the following releases:</p>
<ul>
<li>KDE SC (area51): 4.11.2, 4.11.3, 4.11.4</li>
<li>Qt: 4.8.5 and 5.2 (area51)</li>
<li>PyQt: 4.10.3; SIP: 4.15.2; QScintilla2: 2.8</li>
<li>Qt Creator 2.8.0</li>
<li>KDevelop: 4.5.2</li>
<li>Calligra: 2.7.5</li>
<li>CMake: 2.8.12, 2.8.12.1</li>
</ul>
<p>As a result, according to PortScout, our team has 464 ports
(down from 473), of which 88.15% are up-to-date (down from
98.73%). iXsystems Inc. continues to provide a machine for
the team to build packages and to test updates. iXsystems Inc.
has been providing the KDE/FreeBSD Team with support for quite a
long time and we are very grateful for that.</p>
<p>As usual, the team is always looking for more testers and
porters, so please contact us or visit our home page (see links).
It would be especially useful to have more helping hands on
tasks such as getting rid of the dependency on the defunct HAL
project and providing integration with KDE's Bluedevil Bluetooth
interface.</p>
<h3>Open tasks:</h3><ol><li>Update out-of-date ports, see links for a list.</li><li>Worke on KDE 4.12 and Qt 5.</li><li>Make sure the whole KDE stack (including Qt) builds and
works correctly with Clang and <tt>libc++</tt>.</li><li>Remove the dependency on HAL.</li></ol><hr /><h2><a name="Wine/FreeBSD" href="#Wine/FreeBSD" id="Wine/FreeBSD">Wine/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://wiki.FreeBSD.org/Wine" title="http://wiki.FreeBSD.org/Wine">Wine wiki page</a></td><td>
URL: <a href="http://wiki.FreeBSD.org/Wine" title="Wine wiki page">http://wiki.FreeBSD.org/Wine</a></td></tr><tr><td><a href="http://wiki.FreeBSD.org/i386-Wine" title="http://wiki.FreeBSD.org/i386-Wine">Wine on amd64 wiki page</a></td><td>
URL: <a href="http://wiki.FreeBSD.org/i386-Wine" title="Wine on amd64 wiki page">http://wiki.FreeBSD.org/i386-Wine</a></td></tr><tr><td><a href="http://www.winehq.org/" title="http://www.winehq.org/">Wine homepage</a></td><td>
URL: <a href="http://www.winehq.org/" title="Wine homepage">http://www.winehq.org/</a></td></tr></table><p>
Contact:
Gerald
Pfeiffer
<<a href="mailto:gerald@FreeBSD.org">gerald@FreeBSD.org</a>>
<br />
Contact:
David
Naylor
<<a href="mailto:dbn@FreeBSD.org">dbn@FreeBSD.org</a>>
</p>
<p>Wine is a free and open source software application that aims
to allow applications designed for Microsoft Windows to run on
Unix-like operating systems, such as FreeBSD. The Wine/FreeBSD Team
have continued to improve the experience of Wine under FreeBSD.</p>
<p>During the fourth quarter of 2013, the team has kept Wine
updated by porting:</p>
<ul>
<li>Stable releases: 1.6 and 1.6.1</li>
<li>Development releases: 1.7.4 through 1.7.8</li>
</ul>
<p>The ports have included packages built for <tt>amd64</tt>
(available through the Ports Collection).</p>
<p>The Wine ports have been kept up-to-date with the changes in
the Ports Collection, including some improvements:</p>
<ul>
<li>Building with Clang by default (via <tt>USES=compiler:c11</tt>).</li>
<li>Conditional X11 support (on by default; allowing for
headless instances of Wine).</li>
<li>Staging support and other ports best practices.</li>
</ul>
<p>Support in improving the experience of Wine on FreeBSD is needed.
Key areas including fixing regressions, adding copy protection
scheme support, and fixing regressions when using Wine under
FreeBSD/<tt>amd64</tt>.</p>
<h3>Open tasks:</h3><ol><li>Open Tasks and Known Problems (see links for the wiki
page).</li><li>FreeBSD/<tt>amd64</tt> integration (see links for the i386-Wine
wiki page).</li><li>Porting WoW64 and Wine64.</li></ol><hr /><h2><a name="X.Org-on-FreeBSD" href="#X.Org-on-FreeBSD" id="X.Org-on-FreeBSD">X.Org on FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Graphics" title="https://wiki.freebsd.org/Graphics">X11 roadmap and supported hardware matrix</a></td><td>
URL: <a href="https://wiki.freebsd.org/Graphics" title="X11 roadmap and supported hardware matrix">https://wiki.freebsd.org/Graphics</a></td></tr><tr><td><a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="http://trillian.chruetertee.ch/ports/browser/trunk">Ports-related development repository</a></td><td>
URL: <a href="http://trillian.chruetertee.ch/ports/browser/trunk" title="Ports-related development repository">http://trillian.chruetertee.ch/ports/browser/trunk</a></td></tr><tr><td><a href="http://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014003.html" title="http://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014003.html">CFT for Cairo 1.12 and 8.x survey</a></td><td>
URL: <a href="http://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014003.html" title="CFT for Cairo 1.12 and 8.x survey">http://lists.freebsd.org/pipermail/freebsd-x11/2014-January/014003.html</a></td></tr></table><p>
Contact: FreeBSD X11 Team <<a href="mailto:x11@FreeBSD.org">x11@FreeBSD.org</a>>
</p>
<p>The newer graphics stack (<tt>WITH_NEW_XORG</tt>) is now built
by default on <tt>head</tt> and is provided as binary packages
from the official FreeBSD <tt>pkg(8)</tt> repository for
<tt>11-CURRENT</tt>. The major updates are:</p>
<ul>
<li>X.Org server 1.12.</li>
<li>Mesa 9.1.</li>
<li>Recent Intel and Radeon X.Org drivers, using exclusively
the KMS kernel drivers available in FreeBSD 9.x (Intel) and FreeBSD 10.x
(Radeon).</li>
</ul>
<p>This change makes X.Org on FreeBSD <tt>head</tt> work
out-of-the-box on workstations and laptops based on recent Intel
and Radeon GPUs. FreeBSD 10.x will follow in a few weeks or
months.</p>
<p>Some software has started to require Cairo 1.12, for
example GTK+ 3.10 and Pango. Unfortunately, this version
of Cairo triggers a bug in the old Intel driver (2.7.1,
installed when <tt>WITH_NEW_XORG</tt> is not set), which causes
display artifacts. A "Call For Testers" mail was posted on the
<tt>freebsd-x11</tt> mailing-list (see the links above) to
gather information about the behavior on other configurations
(new Intel driver and non-Intel drivers). As of this writing,
the reports received talk about improvements or, at least, no
change noticed.</p>
<p>To better manage changes such as the <tt>WITH_NEW_XORG</tt> and
the Cairo 1.12 changes mentioned above, we asked on the
<tt>freebsd-x11</tt> mailing-list if people are using
FreeBSD 8.x on their desktop computers and why they do not
upgrade to FreeBSD 9.x or 10.x. So far, we received very few
answers to this.</p>
<p>The Radeon KMS driver in FreeBSD 10.x is now considered
stable, especially now that integrated GPUs are properly
initialized. One of the next steps will be to merge this to
<tt>stable/9</tt>.</p>
<p>A "Graphics" wiki article (see links) was created to centralize
and coordinate the work being done on both the ports and the
kernel. It contains the following important information:</p>
<ul>
<li>A roadmap of the team.</li>
<li>A matrix of supported hardware.</li>
<li>Instructions on upgrading to KMS.</li>
<li>Project status and results.</li>
</ul>
<p>This starting page then points to project- and topic-specific
articles where more detailed information is available.</p>
<h3>Open tasks:</h3><ol><li>Report why FreeBSD 8.x is still used on your desktop and
why moving to FreeBSD 9.x or 10.x is not an option.</li><li>Report about the Cairo 1.12 update on your system.</li><li>See the "Graphics" wiki page for up-to-date information.</li></ol><hr /><h2><a name="Xfce/FreeBSD" href="#Xfce/FreeBSD" id="Xfce/FreeBSD">Xfce/FreeBSD</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="https://wiki.freebsd.org/Xfce" title="https://wiki.freebsd.org/Xfce">The FreeBSD Xfce Team's wiki page</a></td><td>
URL: <a href="https://wiki.freebsd.org/Xfce" title="The FreeBSD Xfce Team's wiki page">https://wiki.freebsd.org/Xfce</a></td></tr><tr><td><a href="https://people.freebsd.org/~olivierd/xfce-core-unstable.html" title="https://people.freebsd.org/~olivierd/xfce-core-unstable.html">Core</a></td><td>
URL: <a href="https://people.freebsd.org/~olivierd/xfce-core-unstable.html" title="Core">https://people.freebsd.org/~olivierd/xfce-core-unstable.html</a></td></tr><tr><td><a href="https://people.freebsd.org/~olivierd/parole-unstable.html" title="https://people.freebsd.org/~olivierd/parole-unstable.html">Parole</a></td><td>
URL: <a href="https://people.freebsd.org/~olivierd/parole-unstable.html" title="Parole">https://people.freebsd.org/~olivierd/parole-unstable.html</a></td></tr></table><p>
Contact: FreeBSD Xfce Team <<a href="mailto:xfce@FreeBSD.org">xfce@FreeBSD.org</a>>
</p>
<p>Xfce is a free software desktop environment for Unix and
Unix-like platforms, such as FreeBSD. It aims to be fast and
lightweight, while still being visually appealing and easy to
use. The FreeBSD Xfce Team has kept most of the Xfce ports
up-to-date, while fixing many issues along the way in this
quarter.</p>
<p>Currently, the following components with the following versions
are available:</p>
<ul>
<li>Applications:</li>
<ul>
<li>Orage (4.10.0)</li>
<li>Midori (0.5.6)</li>
<li>xfce4-terminal (0.6.3)</li>
<li>xfce4-parole (0.5.3, 0.5.4)</li>
</ul>
<li>Panel plugins:</li>
<ul>
<li>xfce4-whiskermenu-plugin (1.2.0, 1.2.1, 1.2.2, 1.3.0)</li>
<li>xfce4-mailwatch-plugin (1.2.0)</li>
<li>xfce4-wmdock-plugin (0.6.0)</li>
</ul>
</ul>
<p>We helped Midori's upstream switch from Waf (Python script)
to CMake. Xfce now also supports Gtk2, Gtk3, and the new
WebKitGtk API, available from the 2.x branch, not present in our
ports tree at the moment, though. Most of the ports now use
stage directories, with only some plugins left to convert.</p>
<p>We also removed obsolete ports:</p>
<ul>
<li><tt>x11-themes/lila-xfwm4</tt> (Xfwm4 theme)</li>
<li><tt>multimedia/xfce4-media</tt> (multimedia player)</li>
<li><tt>net-im/xfce4-messenger-plugin</tt></li>
</ul>
<p>Besides, we followed the development of the Xfce core
components and Parole closely. See the links for documentation
on how to upgrade those libraries.</p>
<h3>Open tasks:</h3><ol><li>Fix Midori's build on DragonFly, through DPorts.</li><li>Fix build of the Granite framework (it is an extension to
Gtk and Midori uses it) on FreeBSD 10 and <tt>head</tt>.
Those are mostly LLVM failures.</li><li>Add support for Berkeley DB 5 and higher to Orage.</li></ol><hr /><br /><h1><a name="Miscellaneous" href="#Miscellaneous" id="Miscellaneous">Miscellaneous</a></h1><br /><h2><a name="The-FreeBSD-Foundation" href="#The-FreeBSD-Foundation" id="The-FreeBSD-Foundation">The FreeBSD Foundation</a></h2><table title="Links" style="white-space: nowrap;"><tr><td>Links</td></tr><tr><td><a href="http://www.FreeBSDFoundation.org/" title="http://www.FreeBSDFoundation.org/"></a></td><td>
URL: <a href="http://www.FreeBSDFoundation.org/" title="">http://www.FreeBSDFoundation.org/</a></td></tr><tr><td><a href="http://www.freebsdfoundation.org/press/2013Dec-newsletter" title="http://www.freebsdfoundation.org/press/2013Dec-newsletter">Semi-annual newsletter</a></td><td>
URL: <a href="http://www.freebsdfoundation.org/press/2013Dec-newsletter" title="Semi-annual newsletter">http://www.freebsdfoundation.org/press/2013Dec-newsletter</a></td></tr><tr><td><a href="http://freebsdjournal.com/" title="http://freebsdjournal.com/">FreeBSD Journal</a></td><td>
URL: <a href="http://freebsdjournal.com/" title="FreeBSD Journal">http://freebsdjournal.com/</a></td></tr></table><p>
Contact:
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. Most of the funding is used to support
FreeBSD development projects, conferences and developer summits,
purchase equipment to grow and improve the FreeBSD infrastructure,
and provide legal support for the Project.</p>
<p>We held our year-end fundraising campaign. We are still
processing donations and will post the final numbers by
mid-January. We are extremely grateful to all the individuals
and organizations that supported us and the Project by making a
donation in 2013. We have already started our fundraising
efforts for 2014.</p>
<p>Some of the highlights from this past quarter include:</p>
<ul>
<li>We sponsored or are sponsoring the following projects:
<ul>
<li>Projects completed last quarter: Capsicum, Casper daemon, and
Intel I/O Memory Management Unit driver.</li>
<li>Projects in progress: Native in-kernel iSCSI stack,
network stack layer 2 modernization, UEFI boot, updated
<tt>vt(9)</tt> system console.</li>
<li>Projects started last quarter: Automounter, Intel
graphics driver update.</li>
</ul>
</li>
<li>Continued work on the FreeBSD Journal, our new online FreeBSD magazine,
which debuts on January 27th (see links).</li>
<li>Sponsored, organized, and ran the Bay Area Developer Summit.</li>
<li>Sponsored and attended the first ever vBSDCon, which had an
impressive attendance.</li>
<li>Sponsored and attended the OpenZFS developer summit.</li>
<li>Represented the foundation at the following conferences: All
Things Open in Raleigh, NC and LISA in Washington, DC.</li>
<li>Sponsored the FreeBSD 20th Birthday Party, held in San
Francisco.</li>
<li>Attended the ICANN meeting in Buenos Aires in November and
gave a short presentation on the change from BIND to unbound in
FreeBSD 10.0 during the ccNSO Tech Day.</li>
<li>Met with a few companies to discuss their FreeBSD use, what
they would like to see supported in FreeBSD, and assist with
collaboration between them and the Project.</li>
<li>Purchased an 80-core server to reside at Sentex for the
Project to use for stability, scalability, and performance
improvements. It is a big step forwards for the Foundation in
providing this kind of hardware to the Project's developers.
It will let us test our scaling to 80 simultaneous cores and
1 TB of RAM. It will also be used to do performance
analysis on large workloads, such as large databases etc.</li>
<li>Acquired a second rack to use at Sentex.</li>
<li>We received a commitment from VMware, Inc. for BSD-licensed
drivers. They also committed to a yearly silver level
donation.</li>
<li>Signed up as a Google Compute trusted tester for the
Project.</li>
<li>Funded a project to produce a white paper titled <q>Managed
Services Using FreeBSD at NYI</q>.</li>
<li>Finally, we published our semi-annual newsletter (see links)
highlighting what we did to support the FreeBSD Project and
Community in 2013.</li>
</ul>
<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>
|
