Date: Fri, 28 Oct 2016 18:59:37 +0000 (UTC) From: Warren Block <wblock@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r49604 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201610281859.u9SIxbge079727@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: wblock Date: Fri Oct 28 18:59:37 2016 New Revision: 49604 URL: https://svnweb.freebsd.org/changeset/doc/49604 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-07-2016-09.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-07-2016-09.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2016-07-2016-09.xml Fri Oct 28 18:10:40 2016 (r49603) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-07-2016-09.xml Fri Oct 28 18:59:37 2016 (r49604) @@ -26,7 +26,7 @@ 2016.</p> <p>The third quarter of 2016 was another productive quarter for - the &os; project and community. [...]</p> + the &os; project and community. [...]</p> <p>Thanks to all the reporters for the excellent work!</p> @@ -110,19 +110,18 @@ <p>Currently, &os; is well proven as a base for routers (<strong>pfSense</strong>, <strong>OPNSense</strong>, <strong>BSDRP</strong>) and NAS (<strong>FreeNAS</strong>, - <strong>zfsGuru</strong>, <strong>NAS4Free</strong>). However, - &os;-based solutions are almost completely absent in the - virtualization area, and <strong>ClonOS</strong> is one of the - attempts to change that. - </p> - - <p>ClonOS is a new free open-source &os;-based platform for virtual - environment creation and management. In the core platform are: - </p> + <strong>zfsGuru</strong>, <strong>NAS4Free</strong>). + However, &os;-based solutions are almost completely absent in + the virtualization area, and <strong>ClonOS</strong> is one of + the attempts to change that.</p> + + <p>ClonOS is a new free open-source &os;-based platform for + virtual environment creation and management. In the core + platform are:</p> <ul> <li>&os; as the host OS</li> - + <li><a href="http://man.FreeBSD.org/bhyve/8">bhyve</a></li>; <li><a href="https://www.xenproject.org/">xen</a></li>; @@ -131,11 +130,11 @@ <li><a href="http://man.freebsd.org/jail/8">jail</a></li>; - <li><a href="https://www.bsdstore.ru/">CBSD</a>; (as a management - tool)</li> + <li><a href="https://www.bsdstore.ru/">CBSD</a>; (as a + management tool)</li> - <li><a href="https://puppet.com/">puppet</a>; (for configuration - management)</li> + <li><a href="https://puppet.com/">puppet</a>; (for + configuration management)</li> <li>additional features such as go-micro services (obtaining VMs, resizing disks, and so on)</li> @@ -144,10 +143,10 @@ <help> <task>We would like to see ClonOS in real-world use. In this - regard we are interested in finding more people and companies who - used &os; in hosting tasks. In addition, it could be great to - work with the developers of existing NAS solutions (zfsGuru, - NAS4Free). + regard we are interested in finding more people and companies + who used &os; in hosting tasks. In addition, it could be + great to work with the developers of existing NAS solutions + (zfsGuru, NAS4Free). </task> </help> </project> @@ -179,20 +178,21 @@ </links> <body> - <p>As in all previous editions of the Google Summer of Code, &os; - was an accepted organization, and we had the chance to mentor 15 - projects. Huge thanks to all our mentors for keeping the high - quality standards that make our community shine.</p> + <p>As in all previous editions of the Google Summer of Code, + &os; was an accepted organization, and we had the chance to + mentor 15 projects. Huge thanks to all our mentors for + keeping the high quality standards that make our community + shine.</p> <p>This year was rather unique in that we accepted for the first time well-known members of the community that are not src committers to co-mentor. We also accepted projects that have - a different upstream than &os;. Both are clear signs that &os; is - growing and adapting to the wider community.</p> + a different upstream than &os;. Both are clear signs that + &os; is growing and adapting to the wider community.</p> <p>This year we are also had administrative issues with Perforce - and have accepted officially the use of external repositories, in - particular github, as requested by students.</p> + and have accepted officially the use of external repositories, + in particular github, as requested by students.</p> <p>12 of 15 projects were successful, which we think is an excellent result for a Google Summer of Code.</p> @@ -208,17 +208,19 @@ <help> <task>The world is changing and we need fresh project ideas. We - need to start looking for those ideas <strong>now</strong>.</task> - + need to start looking for those ideas + <strong>now</strong>.</task> + <task>The project ideas wiki page has been reset and we need to get it populated before applying for the next Google Summer of - Code. Please help unleash the next stream of projects you want to - see in &os;.</task> + Code. Please help unleash the next stream of projects you + want to see in &os;.</task> </help> </project> <project cat='proj'> - <title>CloudABI: Running Untrusted Programs Directly on top of &os;</title> + <title>CloudABI: Running Untrusted Programs Directly on top of + &os;</title> <contact> <person> @@ -243,24 +245,24 @@ </links> <body> - <p>CloudABI is a compact UNIX-like runtime environment inspired by - &os;'s Capsicum security framework. It allows you to safely - run potentially untrusted programs directly on top of &os;, - Linux and macOS, without requiring the use of virtualisation, - jails, etc. This makes it a useful building block for - cluster/cloud computing.</p> + <p>CloudABI is a compact UNIX-like runtime environment inspired + by &os;'s Capsicum security framework. It allows you to + safely run potentially untrusted programs directly on top of + &os;, Linux and macOS, without requiring the use of + virtualisation, jails, etc. This makes it a useful building + block for cluster/cloud computing.</p> <p>Over the last couple of months, several new libraries and applications have been ported over to CloudABI, the most - important addition being Python 3.6. This means that you can now - write strongly sandboxed apps in Python!</p> + important addition being Python 3.6. This means that you can + now write strongly sandboxed apps in Python!</p> - <p>Support for different hardware platforms has also improved. In - addition to amd64 and arm64, we now support i686 and armv6. + <p>Support for different hardware platforms has also improved. + In addition to amd64 and arm64, we now support i686 and armv6. The release of LLVM 3.9 was important to us, as it has - integrated all the necessary changes to support the first three - platforms. Full armv6 support is still blocked on some issues - with LLVM's linker, LLD.</p> + integrated all the necessary changes to support the first + three platforms. Full armv6 support is still blocked on some + issues with LLVM's linker, LLD.</p> </body> <sponsor> @@ -268,13 +270,13 @@ </sponsor> <help> - <task>Play around with CloudABI and let us know what you think of - it! Full support for amd64 and arm64 is part of &os; 11.0. + <task>Play around with CloudABI and let us know what you think + of it! Full support for amd64 and arm64 is part of &os; 11.0. i686 and armv6 support is only available on HEAD, but will be merged to the stable/11 branch in the future.</task> - <task>Interested in Python programming? Give our copy of Python a - try and share your experiences!</task> + <task>Interested in Python programming? Give our copy of Python + a try and share your experiences!</task> <task>Do you maintain pieces of software that could benefit from strong sandboxing? Try building them using the CloudABI cross @@ -325,31 +327,32 @@ </links> <body> - <p>This quarter, the Hyper-V storage driver was greatly improved: - its performance was increased by a factor of 1.2-2 by applying - BUS_DMA and UNMAP_IO, enlarging the request queue, and selecting the - outgoing channel with the LUN considered; TRIM/UNMAP was enabled; - and some critical bugs (PRs 209443, 211000, 212998) were fixed so - that disk hot add/remove and VHDX online resizing should work - now.</p> + <p>This quarter, the Hyper-V storage driver was greatly + improved: its performance was increased by a factor of 1.2-2 + by applying BUS_DMA and UNMAP_IO, enlarging the request queue, + and selecting the outgoing channel with the LUN considered; + TRIM/UNMAP was enabled; and some critical bugs (PRs 209443, + 211000, 212998) were fixed so that disk hot add/remove and + VHDX online resizing should work now.</p> - <p>The VMBus driver also received attention, with enhancements made for - the handling of device hot add/remove.</p> + <p>The VMBus driver also received attention, with enhancements + made for the handling of device hot add/remove.</p> - <p> In the Hyper-V network driver, configurable RSS key and dynamic - MTU change are now supported.</p> + <p> In the Hyper-V network driver, configurable RSS key and + dynamic MTU change are now supported.</p> <p>&os; images on Azure continue to be updated — after - publishing the &os; 10.3 VM image on the global Microsoft Azure in - June, Microsoft also published the VM image on the Microsoft Azure - operated by 21Vianet in China in September.</p> - - <p>Patches have been developed to support PCIe pass-through (also - known as Discrete Device Assignment); this feature allows physical - PCIe devices to be passed through to &os; VMs running on Hyper-V - (Windows Server 2016), giving them near-native performance with low - CPU utilization. The patch to enable the feature will be posted for - review soon.</p> + publishing the &os; 10.3 VM image on the global Microsoft + Azure in June, Microsoft also published the VM image on the + Microsoft Azure operated by 21Vianet in China in + September.</p> + + <p>Patches have been developed to support PCIe pass-through + (also known as Discrete Device Assignment); this feature + allows physical PCIe devices to be passed through to &os; VMs + running on Hyper-V (Windows Server 2016), giving them + near-native performance with low CPU utilization. The patch + to enable the feature will be posted for review soon.</p> </body> <sponsor> @@ -358,7 +361,8 @@ </project> <project cat='gsoc'> - <title><tt>ptnet</tt> Driver and <tt>bhyve</tt> Device Model</title> + <title><tt>ptnet</tt> Driver and <tt>bhyve</tt> Device + Model</title> <contact> <person> @@ -380,21 +384,22 @@ <p>This project provides:</p> <ul> - <li>A new driver (<tt>if_ptnet</tt>) for a paravirtualized network - device, modeled after the netmap API. The driver supports - multi-queue netmap ports, and it is able to work both in netmap - mode and in normal mode.</li> + <li>A new driver (<tt>if_ptnet</tt>) for a paravirtualized + network device, modeled after the netmap API. The driver + supports multi-queue netmap ports, and it is able to work + both in netmap mode and in normal mode.</li> - <li>The emulation of the <tt>ptnet</tt> device model as a module - of the <tt>bhyve</tt> hypervisor.</li> + <li>The emulation of the <tt>ptnet</tt> device model as a + module of the <tt>bhyve</tt> hypervisor.</li> </ul> <p>The <tt>ptnet</tt> device and driver has been introduced to - overcome the performance limitations of TCP/IP networking between - bhyve VMs. Prior to this work, the most performant solution for - VM-to-VM intra-host TCP communication provided less than 2 Gbps TCP - throughput. With <tt>ptnet</tt>, in the same VM-to-VM TCP - communication scenario, it is possible to obtain up to 20 Gbps.</p> + overcome the performance limitations of TCP/IP networking + between bhyve VMs. Prior to this work, the most performant + solution for VM-to-VM intra-host TCP communication provided + less than 2 Gbps TCP throughput. With <tt>ptnet</tt>, in the + same VM-to-VM TCP communication scenario, it is possible to + obtain up to 20 Gbps.</p> </body> <sponsor> @@ -403,8 +408,9 @@ <help> <task>Share <tt>virtio-net</tt> header management code with the - <tt>if_vtnet</tt> driver. In the current code, about 100 lines of - code have been copied and pasted from <tt>if_vtnet.c</tt>.</task> + <tt>if_vtnet</tt> driver. In the current code, about 100 + lines of code have been copied and pasted from + <tt>if_vtnet.c</tt>.</task> </help> </project> @@ -444,9 +450,9 @@ requires some components of Plasma 5, the new major KDE workspace.</p> - <p>The porting of the 0.11 branch is now complete, with new ports - (compared to the previous release). See our wiki page for a - complete list of applications.</p> + <p>The porting of the 0.11 branch is now complete, with new + ports (compared to the previous release). See our wiki page + for a complete list of applications.</p> <p>We also have updates for:</p> @@ -551,9 +557,9 @@ <li><tt>x11-clocks/xfce4-datetime-plugin</tt> (0.6.99)</li> </ul> - <p>Currently, the unstable releases work fine with our Gtk3 ports - available in the ports tree, but in the future, support for 3.18 - will be removed in preference of 3.20.x.</p> + <p>Currently, the unstable releases work fine with our Gtk3 + ports available in the ports tree, but in the future, support + for 3.18 will be removed in preference of 3.20.x.</p> </body> <help> @@ -581,24 +587,26 @@ </links> <body> - <p>This project was started during Google Summer of Code this year. - The aim was to create a library which can convert the audit trail - files in Linux Audit format or the format used by Windows to the BSM - format used by &os; for its audit logs. Apart from that, - I wanted to create a simple command-line tool and extend - <tt>auditdistd</tt> so that it is possible to send non-BSM logs to - it over a secure connection and save those audit - logs on disk, preferably in the BSM format.</p> + <p>This project was started during Google Summer of Code this + year. The aim was to create a library which can convert the + audit trail files in Linux Audit format or the format used by + Windows to the BSM format used by &os; for its audit logs. + Apart from that, I wanted to create a simple command-line tool + and extend <tt>auditdistd</tt> so that it is possible to send + non-BSM logs to it over a secure connection and save those + audit logs on disk, preferably in the BSM format.</p> <p>So far, it is possible to reasonably convert some of the most - common Linux audit log events to BSM, but it still needs a lot of - work. Secondly, I was able to configure <tt>auditdistd</tt> to - communicate with CentOS over an insecure connection. Thirdly, the - command-line tool is usable but not perfect.</p> - - <p>The present work focuses on configuring the secure TLS connection - between CentOS and <tt>auditdistd</tt>. I have already tried using - rsyslogd but was not able to make it work.</p> + common Linux audit log events to BSM, but it still needs a lot + of work. Secondly, I was able to configure + <tt>auditdistd</tt> to communicate with CentOS over an + insecure connection. Thirdly, the command-line tool is usable + but not perfect.</p> + + <p>The present work focuses on configuring the secure TLS + connection between CentOS and <tt>auditdistd</tt>. I have + already tried using rsyslogd but was not able to make it + work.</p> </body> <sponsor> @@ -606,17 +614,18 @@ </sponsor> <help> - <task>I need more examples of rare Linux Audit logs; please send me - some examples if you have any. It is much easier to improve the - conversion process with real-life examples of the audit events you - try to convert.</task> - - <task>Configure <tt>auditdistd</tt> to be able to communicate with some - software on CentOS over TLS in order to receive audit logs. I - was not able to come up with a simple solution for that.</task> + <task>I need more examples of rare Linux Audit logs; please send + me some examples if you have any. It is much easier to + improve the conversion process with real-life examples of the + audit events you try to convert.</task> + + <task>Configure <tt>auditdistd</tt> to be able to communicate + with some software on CentOS over TLS in order to receive + audit logs. I was not able to come up with a simple solution + for that.</task> - <task>Additional open tasks are listed on the Wiki page and in the - TODO file in the root directory of the project.</task> + <task>Additional open tasks are listed on the Wiki page and in + the TODO file in the root directory of the project.</task> </help> </project> @@ -634,33 +643,34 @@ </contact> <body> - <p>Non-Transparent Bridges allow creation of memory windows between - different systems using the regular PCIe links of CPUs as a - transport. During the last quarter, the NTB subsystem gained a - significant set of improvements and fixes:</p> + <p>Non-Transparent Bridges allow creation of memory windows + between different systems using the regular PCIe links of CPUs + as a transport. During the last quarter, the NTB subsystem + gained a significant set of improvements and fixes:</p> <ul> - <li>The code was modularized, utilizing &os;'s NewBus interfaces - to allow support for different hardware types with different - drivers, support for multiple NTB instances in a system, - using the <tt>ntb_transport</tt> module for consumers other - than <tt>if_ntb</tt>, etc.</li> + <li>The code was modularized, utilizing &os;'s NewBus + interfaces to allow support for different hardware types + with different drivers, support for multiple NTB instances + in a system, using the <tt>ntb_transport</tt> module for + consumers other than <tt>if_ntb</tt>, etc.</li> <li>Support for splitting NTB resources between different - applications was added, such as doing direct access to some range - of remote memory and to a virtual network interface between nodes - at the same time, etc.</li> - - <li>The virtual network interface driver gained support for many - modern features, such as multiple queues, new locking, etc.</li> + applications was added, such as doing direct access to some + range of remote memory and to a virtual network interface + between nodes at the same time, etc.</li> + + <li>The virtual network interface driver gained support for + many modern features, such as multiple queues, new locking, + etc.</li> <li>NTB performance and SMP scalability was improved.</li> <li>Multiple workarounds for hardware issues were added.</li> </ul> - <p>The code is committed to the &os; head, stable/11 and stable/10 - branches.</p> + <p>The code is committed to the &os; head, stable/11 and + stable/10 branches.</p> </body> <sponsor> @@ -674,7 +684,8 @@ <task>Support for I/OAT and other DMA offloads.</task> - <task>Creating a more efficient packet transport protocol.</task> + <task>Creating a more efficient packet transport + protocol.</task> <task>Creating a greater variety of NTB applications.</task> </help> @@ -703,19 +714,21 @@ <body> <p>The ZFS code base in &os; regularly gets merges of new code, - staying in sync with latest OpenZFS/Illumos sources. Among other - things, the latest merge included the following improvements:</p> + staying in sync with latest OpenZFS/Illumos sources. Among + other things, the latest merge included the following + improvements:</p> <ul> <li>The ARC now mostly stores compressed data, the same as is stored on disks, decompressing them on demand.</li> - <li>The L2ARC now stores the same (compressed) data as ARC without - recompression, and its RAM usage was further reduced.</li> - - <li>The largest size of indirect block possible has been increased - from 16KB fo 128KB, and speculative prefetching of indirect blocks - is now performed.</li> + <li>The L2ARC now stores the same (compressed) data as ARC + without recompression, and its RAM usage was further + reduced.</li> + + <li>The largest size of indirect block possible has been + increased from 16KB fo 128KB, and speculative prefetching of + indirect blocks is now performed.</li> <li>Improved ordering of space allocation.</li> @@ -748,12 +761,12 @@ <body> - <p>&os; includes support for the Marvell Armada38x platform, which - has been tested and improved in order to gain production quality. - Most of this effort has been invested in development and - benchmarking of the on-chip Gigabit Ethernet (NETA) functionality. - Numerous bug fixes and some new features have been - introduced.</p> + <p>&os; includes support for the Marvell Armada38x platform, + which has been tested and improved in order to gain production + quality. Most of this effort has been invested in development + and benchmarking of the on-chip Gigabit Ethernet (NETA) + functionality. Numerous bug fixes and some new features have + been introduced.</p> <p>Work completed this quarter includes:</p> @@ -763,8 +776,8 @@ <li>Enable multi-port support in PCIe 2.0 driver (<tt>mv_pci_ctrl</tt>).</li> - <li>Introduce an alternative, coherent, <tt>bus_dma</tt> for the - armv7 arch.</li> + <li>Introduce an alternative, coherent, <tt>bus_dma</tt> for + the armv7 arch.</li> <li>AHCI controller support.</li> @@ -772,7 +785,8 @@ <li>Improve the <tt>e6000sw</tt> etherswitch driver.</li> - <li>Fix Marvell bus configuration for numerous interfaces.</li> + <li>Fix Marvell bus configuration for numerous + interfaces.</li> </ul> <p>Along with support for new boards (SolidRun ClearFog and @@ -820,15 +834,16 @@ </links> <body> - <p>The Elastic Network Adapter (ENA) is a 25G SmartNIC developed by - Annapurna Labs based on a custom ARMv8 chip. This is a - high-performance networking card that is available to AWS virtual - machines. It introduces enhancements in network utilization - scalability on EC2 machines running various operating systems, in - particular &os;.</p> - - <p>The goal of &os; enablement is to provide top performance and a - wide range of monitoring and management features such as:</p> + <p>The Elastic Network Adapter (ENA) is a 25G SmartNIC developed + by Annapurna Labs based on a custom ARMv8 chip. This is a + high-performance networking card that is available to AWS + virtual machines. It introduces enhancements in network + utilization scalability on EC2 machines running various + operating systems, in particular &os;.</p> + + <p>The goal of &os; enablement is to provide top performance and + a wide range of monitoring and management features such + as:</p> <ul> <li>multiple queue modes</li> @@ -847,7 +862,8 @@ </ul> <p>The current state offers stable driver operation with good - performance on machines running &os; directly on the hardware.</p> + performance on machines running &os; directly on the + hardware.</p> </body> <sponsor> @@ -893,16 +909,18 @@ <body> <p>Alpine is a family of Platform-on-Chip devices, including - multi-core 32-bit (first-gen Alpine) and 64-bit (Alpine V2) ARM - CPUs, developed by Annapurna Labs.</p> + multi-core 32-bit (first-gen Alpine) and 64-bit (Alpine V2) + ARM CPUs, developed by Annapurna Labs.</p> <p>The primary focus areas of the Alpine platform are - high-performance networking, storage and embedded applications. The - network subsystem features 10-, 25-, and 50-Gbit Ethernet - controllers with support for virtualization, load-balancing, - hardware offload and other advanced features.</p> + high-performance networking, storage and embedded + applications. The network subsystem features 10-, 25-, and + 50-Gbit Ethernet controllers with support for virtualization, + load-balancing, hardware offload and other advanced + features.</p> - <p>A basic patch set has already been committed to HEAD including:</p> + <p>A basic patch set has already been committed to HEAD + including:</p> <ul> <li>PCIe Root Complex support</li> @@ -914,16 +932,17 @@ <li>Updated Alpine HAL</li> <li>Extended MSI support in GICv2 and GICv3 code</li> - </ul> + </ul> <p>Additional work, such as an MSI-X driver and full Ethernet - support, is currently undergoing community review on Phabricator.</p> + support, is currently undergoing community review on + Phabricator.</p> - <p>The multi-user SMP system is stable and fully working, along with - the 1G and 10G Ethernet links.</p> + <p>The multi-user SMP system is stable and fully working, along + with the 1G and 10G Ethernet links.</p> - <p>The interrupt management code has been adjusted to work with the - new INTRNG framework on both ARM32 and ARM64.</p> + <p>The interrupt management code has been adjusted to work with + the new INTRNG framework on both ARM32 and ARM64.</p> </body> <sponsor> @@ -936,7 +955,8 @@ </project> <project cat='doc'> - <title>Documenting the History of Utilities in /bin and /sbin</title> + <title>Documenting the History of Utilities in /bin and + /sbin</title> <contact> <person> @@ -957,23 +977,25 @@ <body> <p>For EuroBSDcon, I began looking into inconsistencies within - components inside our family of operating systems. My workflow - consisted of reading the documentation for a given utility and - checking the history in the revision control system for missing - fixes or functionality in the trees of NetBSD, &os;, OpenBSD, and - DragonFly BSD.</p> + components inside our family of operating systems. My + workflow consisted of reading the documentation for a given + utility and checking the history in the revision control + system for missing fixes or functionality in the trees of + NetBSD, &os;, OpenBSD, and DragonFly BSD.</p> <p>One thing which became obvious very quickly was the - inconsistency between operating systems about where and/or which - version a utility originated in, despite our common heritage.</p> - - <p>I began with working through the man pages in &os;, verifying the - details in pages which already had a history section and making - patches for those which did not.</p> - - <p>From there, changes were propogated out to NetBSD, OpenBSD, and - Dragonfly BSD where applicable (not all utilities originated from - the same source or implementation, for example).</p> + inconsistency between operating systems about where and/or + which version a utility originated in, despite our common + heritage.</p> + + <p>I began with working through the man pages in &os;, verifying + the details in pages which already had a history section and + making patches for those which did not.</p> + + <p>From there, changes were propogated out to NetBSD, OpenBSD, + and Dragonfly BSD where applicable (not all utilities + originated from the same source or implementation, for + example).</p> <p>This was a good exercise in:</p> @@ -981,28 +1003,29 @@ <li>Becoming familiar with <a href="http://mdocml.bsd.lv/man">mandoc</a>.</li>; - <li>Using tools such as the linting functionality in mandoc and - the <tt>igor</tt> documentation script.</li> + <li>Using tools such as the linting functionality in mandoc + and the <tt>igor</tt> documentation script.</li> <li>Becoming familiar with the locations where things are - documented and with external sources of historical information, - such as the BSD Family Tree included in the &os; base - system, and projects like <a href="http://www.tuhs.org">The UNIX - Heritage Society</a> and the <a href="http://man.cat-v.org">manual - library</a> on <a href="http://cat-v.org">cat-v.org</a>; which - hosts copies of manuals such as those shipped with - <a href="https://en.wikipedia.org/wiki/Research_Unix">Research - UNIX</a>. These manuals are not commonly available - elsewhere.</li> + documented and with external sources of historical + information, such as the BSD Family Tree included in the + &os; base system, and projects like + <a href="http://www.tuhs.org">The UNIX Heritage Society</a> + and the <a href="http://man.cat-v.org">manual library</a> + on <a href="http://cat-v.org">cat-v.org</a>; which hosts + copies of manuals such as those shipped with + <a href="https://en.wikipedia.org/wiki/Research_Unix">Research UNIX</a>. + These manuals are not commonly available elsewhere.</li> </ul> </body> <help> - <task>Cover the remaining manuals for userland utilities, and maybe - expand into library and syscall APIs, though I say that without - estimating the feasibility. The history of components originating from a - closed-source operating system is tricky to document, - since older versions are not always available.</task> + <task>Cover the remaining manuals for userland utilities, and + maybe expand into library and syscall APIs, though I say that + without estimating the feasibility. The history of components + originating from a closed-source operating system is tricky to + document, since older versions are not always + available.</task> </help> </project> @@ -1032,22 +1055,23 @@ </links> <body> - <p>&os; provides an API for guest operating systems to access shared folders on - the host so that the kernel driver can expose them to the - guest's userland. This project aims to add such functionality to - the VirtualBox Guest Additions driver.</p> + <p>&os; provides an API for guest operating systems to access + shared folders on the host so that the kernel driver can + expose them to the guest's userland. This project aims to add + such functionality to the VirtualBox Guest Additions + driver.</p> <p>Good progress was made over last few months. Developers were able to mount a filesystem in read-only mode and, with some - limitations, in read-write mode. The implementation still lacks - some critical pieces, but the roadmap is clear.</p> + limitations, in read-write mode. The implementation still + lacks some critical pieces, but the roadmap is clear.</p> </body> <help> <task>Finish the missing pieces.</task> - + <task>Implement proper locking.</task> - + <task>General clean-up and bugfixes.</task> </help> </project> @@ -1079,31 +1103,32 @@ </links> <body> - <p><tt>evdev</tt> is a portable, API-compatible implementation of - the Linux <tt>/dev/input/eventX</tt> interface. It covers a wide - variety of input devices like keyboards, mice, and touchscreens - (with multitouch support), and support for it is implemented in a - lot of existing userland components like Qt, <tt>libinput</tt>, and - <tt>tslib</tt>.</p> + <p><tt>evdev</tt> is a portable, API-compatible implementation + of the Linux <tt>/dev/input/eventX</tt> interface. It covers + a wide variety of input devices like keyboards, mice, and + touchscreens (with multitouch support), and support for it is + implemented in a lot of existing userland components like Qt, + <tt>libinput</tt>, and <tt>tslib</tt>.</p> - <p><tt>evdev</tt> support was started by Jakub Klama as a Google SoC - 2014 project, and later picked up and finished by Vladimir + <p><tt>evdev</tt> support was started by Jakub Klama as a Google + SoC 2014 project, and later picked up and finished by Vladimir Kondratiev. General API and <tt>evdev</tt> support bits for - <tt>ukbd</tt> and <tt>ums</tt> were committed to HEAD. Support was - also added for TI's AM33xx touchstreen controller (the popular - BeagleBone is based on the AM33xx) and the official touschreen for - the Raspberry Pi. Multitouch support for the Raspberry Pi was - successfully demonstarted using the latest Qt development branch.</p> - </body> + <tt>ukbd</tt> and <tt>ums</tt> were committed to HEAD. + Support was also added for TI's AM33xx touchstreen controller + (the popular BeagleBone is based on the AM33xx) and the + official touschreen for the Raspberry Pi. Multitouch support + for the Raspberry Pi was successfully demonstarted using the + latest Qt development branch.</p> + </body> <help> - <task>Documentation. In particular, manual pages are needed for the - KPI.</task> + <task>Documentation. In particular, manual pages are needed for + the KPI.</task> <task>Support additional hardware.</task> - <task>Enable <tt>evdev</tt> support in existing ports, and add new - <tt>evdev</tt>-dependent ports.</task> + <task>Enable <tt>evdev</tt> support in existing ports, and add + new <tt>evdev</tt>-dependent ports.</task> </help> </project> @@ -1135,33 +1160,33 @@ <body> <p>Transparent superpage support has been added. This allows - &os; to create 2MiB blocks with a single pagetable and TLB entry. - This shows a small but significant improvement in the + &os; to create 2MiB blocks with a single pagetable and TLB + entry. This shows a small but significant improvement in the buildworld time on ThunderX machines. Superpages have been - enabled in head and merged to stable/11, but they are - disabled by default on stable/11 due to a lack of testing - there.</p> + enabled in head and merged to stable/11, but they are disabled + by default on stable/11 due to a lack of testing there.</p> <p>Support for the pre-INTRNG interrupt framework has been removed. This means that arm64 requires INTRNG to even build. - This has allowed various cleanups within the arm64 drivers that - interact with the interrupt controller.</p> + This has allowed various cleanups within the arm64 drivers + that interact with the interrupt controller.</p> - <p>The cortex Strings library from Linaro has been imported. The - parts of this that have been shown to be improvements over the - previous C code were attached to the libc build.</p> + <p>The cortex Strings library from Linaro has been imported. + The parts of this that have been shown to be improvements over + the previous C code were attached to the libc build.</p> <p>There is ongoing work to add ACPI support to the kernel. On - ThunderX, &os; can get to the mountroot prompt, however, due to - incomplete ACPI tables the external PCIe support needed to support - the netboot setup in the test cluster is not functional.</p> + ThunderX, &os; can get to the mountroot prompt, however, due + to incomplete ACPI tables the external PCIe support needed to + support the netboot setup in the test cluster is not + functional.</p> <p>Pine64 support has been committed to head. &os; can now boot - to multiuser with SMP enabled. This includes support for clocks, - the secure ID controller, USB Host controller, GPIOs, non-maskable - interrupts, the AXP81x power management unit, cpu freqency and - voltage scaling, MMC, UART, gigabit networking, the watchdog, and - the thermal sensors.</p> + to multiuser with SMP enabled. This includes support for + clocks, the secure ID controller, USB Host controller, GPIOs, + non-maskable interrupts, the AXP81x power management unit, cpu + freqency and voltage scaling, MMC, UART, gigabit networking, + the watchdog, and the thermal sensors.</p> </body> <sponsor> @@ -1193,9 +1218,9 @@ </links> <body> - <p>The KDE on &os; team focuses on packaging the KDE software and - making sure that the experience of KDE and Qt on &os; is as good as - possible.</p> + <p>The KDE on &os; team focuses on packaging the KDE software + and making sure that the experience of KDE and Qt on &os; is + as good as possible.</p> <p>The following big updates were landed in the ports tree this quarter:</p> @@ -1212,15 +1237,16 @@ <li>CMake was updated to versions 3.6.1 and 3.6.2.</li> - <li>An important fix was made to <tt>qmake</tt>, where the clang - version was not correctly detected.</li> + <li>An important fix was made to <tt>qmake</tt>, where the + clang version was not correctly detected.</li> <li>Qt 5.6.1 was committed to ports.</li> - <li>Phonon and its backend to were updated to 4.9.0 in preparation - for Qt 5.6.1.</li> + <li>Phonon and its backend to were updated to 4.9.0 in + preparation for Qt 5.6.1.</li> - <li>Updated the <tt>net-im/telepathy-qt4</tt> port to 0.9.7.</li> + <li>Updated the <tt>net-im/telepathy-qt4</tt> port to + 0.9.7.</li> <li>Various LibreSSL related fixes by Matthew Rezny.</li> @@ -1234,9 +1260,10 @@ work:</p> <ul> - <li>The plasma5 branch has been kept up to date with KDE's upstream and - contains ports for Frameworks 5.26.0, Plasma Desktop 5.8.0, and - Applications 16.08.1 (branches/plasma5).</li> + <li>The plasma5 branch has been kept up to date with KDE's + upstream and contains ports for Frameworks 5.26.0, Plasma + Desktop 5.8.0, and Applications 16.08.1 + (branches/plasma5).</li> </ul> </body> @@ -1255,106 +1282,110 @@ <body> <p>The third quarter started with the handover to the ninth Core team as it took office. With four members returning from the - previous core (Baptiste Daroussin, Ed Maste, George Neville-Neil - and Hiroki Sato), one returning member after a term away (John - Baldwin), and four members new to core (Allan Jude, Kris Moore, - Benedict Reuschling and Benno Rice), the new core team represents - just about the ideal balance between experience and fresh - blood.</p> + previous core (Baptiste Daroussin, Ed Maste, George + Neville-Neil and Hiroki Sato), one returning member after a + term away (John Baldwin), and four members new to core (Allan + Jude, Kris Moore, Benedict Reuschling and Benno Rice), the new + core team represents just about the ideal balance between + experience and fresh blood.</p> <p>Beyond handing over all of the ongoing business, reviewing everything on Core's agenda, and other routine changeover - activities, the first action of the new core was to respond to a - query from Craig Rodrigues concerning how hardware supplied to the - project through donations to the &os; Foundation was being - used.</p> + activities, the first action of the new core was to respond to + a query from Craig Rodrigues concerning how hardware supplied + to the project through donations to the &os; Foundation was + being used.</p> <p>The Foundation does keep records of what hardware has been - supplied over time and has some idea of the original purpose that - hardware was provisioned for, but does not track the current usage - of the project's hardware assets. Cluster administration keeps - their own configuration database, but this is not suitable for - general publication and covers much more than Foundation supplied - equipment. After some discussion it was decided that updated - information about the current disposition of Foundation supplied - equipment should be incorporated in the Foundation's annual - report.</p> - - <p>Ensuring that all of the &os; code base is supplied under open - and unencumbered licensing terms and that we do not infringe on - patent terms or otherwise act counter to any legal requirements - are some of Core's primary concerns. During this quarter, there - were three items of this nature.</p> + supplied over time and has some idea of the original purpose + that hardware was provisioned for, but does not track the + current usage of the project's hardware assets. Cluster + administration keeps their own configuration database, but + this is not suitable for general publication and covers much + more than Foundation supplied equipment. After some + discussion it was decided that updated information about the + current disposition of Foundation supplied equipment should be + incorporated in the Foundation's annual report.</p> + + <p>Ensuring that all of the &os; code base is supplied under + open and unencumbered licensing terms and that we do not + infringe on patent terms or otherwise act counter to any legal + requirements are some of Core's primary concerns. During this + quarter, there were three items of this nature.</p> <ul> <li>Importing Concurrency Kit. In consultation with the - Foundation's legal counsel, it was determined that the relevant - patents on the 'Read Copy Update' synchronization mechanisms - have expired, and consequently the import of selected parts of - concurrency kit was approved.</li> + Foundation's legal counsel, it was determined that the + relevant patents on the 'Read Copy Update' synchronization + mechanisms have expired, and consequently the import of + selected parts of concurrency kit was approved.</li> <li>The proposal to create a shadow GPLv3 toolchain repository - was put to the community. Ultimately the whole idea has been - rendered largely redundant by faster than anticipated progress - at integrating the latest LLVM toolchain on most of the - interesting system architectures. The goal of a GPL-free base - system is within our grasp.</li> - - <li>Reports that GPL code has been pasted into linuxkpi sources - are under investigation. Core would like to stress that great - care must be taken to avoid inadvertent license infringement, - especially when implementing hardware interfaces or similar - where there is limited scope to invent new constants or - otherwise make it clear this is a novel implementation.</li> + was put to the community. Ultimately the whole idea has + been rendered largely redundant by faster than anticipated + progress at integrating the latest LLVM toolchain on most of + the interesting system architectures. The goal of a + GPL-free base system is within our grasp.</li> + + <li>Reports that GPL code has been pasted into linuxkpi + sources are under investigation. Core would like to stress + that great care must be taken to avoid inadvertent license + infringement, especially when implementing hardware + interfaces or similar where there is limited scope to invent + new constants or otherwise make it clear this is a novel + implementation.</li> </ul> <p>Work on LLVM has thrown up problems with the presence of - certain pre-compiled binary-only drivers as part of the GENERIC - kernel. Core has adopted the policy that such binary-only code - should be moved to loadable modules and that the GENERIC kernel - must be compiled entirely from original sources.</p> + certain pre-compiled binary-only drivers as part of the + GENERIC kernel. Core has adopted the policy that such + binary-only code should be moved to loadable modules and that + the GENERIC kernel must be compiled entirely from original + sources.</p> <p>The item that has absorbed the largest portion of Core's *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201610281859.u9SIxbge079727>