From owner-svn-doc-head@FreeBSD.ORG Sun Jan 11 16:05:23 2015
Return-Path: There is growing interest in ARM's 64-bit architecture.
+ Officially named as AArch64, it is also known as ARMv8 and arm64.
+ Andrew Turner started initial work on the FreeBSD/arm64 port at
+ the end of 2012. The &os; Foundation is now collaborating with ARM,
+ Cavium, the Semihalf team, and Andrew Turner to port &os; to
+ arm64, and significant progress was made on the port over the last
+ quarter of 2014. As of the end of the year &os; boots to single-user mode
+ on arm64, executing both static and dynamic applications. Patches
+ in review allow &os; to boot to multi-user mode and these are
+ expected to be merged soon. This includes implementing many stub
+ functions in userland and the kernel. With this, &os; has booted to
+ multi-user mode on both the ARM Foundation Model and the QEMU full
+ system emulation. Cavium has supplied a software simulator of their Thunder X
+ hardware. Bringup of &os; has started on this including writing
+ new drivers for the ARM Generic Interrupt Controller v3 (GICv3)
+ and a preliminary driver for the PCIe root complex. With these,
+ &os; is able to boot on this simulator in preparation for
+ testing on hardware. Further work is progressing to add full PCIe
+ bringup and to add support for the GICv3 Interrupt Translation
+ Services (ITS) for MSI-X. Further improvements have been made to the loader to allow
+ it to take the Flattened Device Tree data from UEFI and pass it to
+ the kernel. In the kernel busdma, CPU identification, and
+ improvements to interrupt handling have been made, along with
+ preliminary KDB support. Hardware for testing the port will be installed in the
+ &os; Test Cluster hosted by Sentex Communications. The first
+ reference platform, Cavium's ThunderX, is expected to arrive
+ in the cluster in mid-January. Bring up and test kernel support on real hardware. Implement remaining userland libraries and binaries. Produce installable images. The main goal of the lemul project is the execution of
multithreaded Linux applications, which requires the glibc library
@@ -1816,7 +1821,8 @@
At present, the linux emulation layer project has
implemented all of the necessary system calls for supporting glibc
- 2.20, and more:
Implement the signalfd() and timerfd +
Implement the signalfd() and timerfd() system calls for the Linuxulator.
Extend xucred support, which is required for - many Linux applications.
+Implement the Priority Inheritance Futexes for + the Linuxulator.
+Extend xucred suppport, which is required for many Linux + applications.
Many &os; utilities provide insight into the operational + state of a running &os; system and as such are used regularly to + monitor the system. These utilities provide their output in a human + readable form and sometimes even optimized for the limited width of + traditional terminals. Often times these utilities are used by other + programs that want to present the output in different ways or as part + of other user interfaces. For such use cases, it is infinitely better + to work with machine-readable output instead of human-readable + output.
+ +Juniper Networks has created a library called libxo, that + makes it easy for utilities to emit output in various + formats. By default the text output is emitted, but with the + introduction of the —libxo option this can be changed to + XML, JSON and HTML. The &os; project has imported this library + into the base system and is in the process of rewriting utilities + to use libxo.
+ +Related to this, &os; now also has the xo utility that + allows scripts to grow the same capabilities. Instead of + using echo or printf in scripts, output can be + done using the xo utility.
+ +The df, w, and wc utilities + have been converted to use libxo. The netstat + utility is in the process of being converted and others are + planned.
+ + +&os; contains a lot of utilities that could benefit from + having the ability to emit various output formats, + too many for a few people to convert in time for &os; 11.0-RELEASE. + If you or your company would like to see a particular + utility converted, consider learning about libxo and + trying to perform the conversion of said utility to help + out.
+The fourth quarter of 2014... was a very busy and productive - time
+The fourth quarter of 2014 included a number of significant improvements to the &os; + system, in particular in compatibility with other systems. This included + significant improvements to the Linux compatibility layer, used to + run Linux binaries on &os;, and the port of WINE, used to run Windows + applications. Hypervisor support improved, with &os; gaining the ability + to run as domain 0 on Xen's new high-performance PVH mode, bhyve gaining + AMD support, and new tools for creating &os; VM images arriving.
+ +This quarter was also an active time for the toolchain, with numerous + improvements to the compiler, debugger, and other components, including + initial support for C++14, which should be complete by + &os; 10.2.
Thanks to all the reporters for the excellent work!
@@ -97,7 +107,7 @@With funding from the &os; Foundation, the &os; forums were migrated to XenForo software. The new software is far more capable and easy to use. While the entire forum team - contributed, &a.danger; did a particularly excellent job + contributed, &a.danger; did an excellent job importing existing users and messages and bringing back the often-requested "Thanks" feature. The upgrade was completed in time to be ready for the influx of new users from the release of @@ -151,8 +161,9 @@
There were several improvements made to the FreeBSD process management last quarter.
+ -Reaper. The facility to allow a process to reliably track the +
The Reaper facility, to allow a process to reliably track the running and exiting state of the whole subtree of the processes, was added. It is intended to improve tools like timeout(1) or poudriere, by making it impossible for the runaway granchild to @@ -161,36 +172,36 @@ references to the Solaris contracts. Committed to HEAD in r275800.
-Total stop. Right now, the FreeBSD suspension code does not - ensures that the system, both from software and from hardware - view, is in the steady and consistent state. One aspect is the - usermode process activity which is not stopped, continuing to +
The FreeBSD suspension code does not + ensure that the system, both software and hardware, + is in the steady and consistent state. One aspect is + usermode process activity, which is not yet stopped, continuing to making requests to the hardware. It is not realistic to expect drivers to be able to correctly handle the calls after SUSPEND_CHILD.
-Together with Peter Holm, we developed a facility to stop - usermode threads at the safe points, where they are known to not +
We developed a facility to stop + usermode threads at safe points, where they are known to not own and to not wait for kernel resources, in particular, not waiting for device requests finishing. It is based on the existing single-threading code, but extending it to allow external - thread to put some process into stopped state. Also, a facility + thread to put some processes into stopped state. Also, a facility to sync filesystems before suspend was added, to ensure that consistent metadata and as much as possilbe of the cached user data are on stable storage, to minimize damage of failed resume.
-The code stressed some parts of the system and lead to - discovery of the unusual numbers of bugs in the different parts of - the system, including process management, buffer cache and syscall +
The code stressed some parts of the system and has lead to + discovery of a numbers of bugs in the different areas, + including process management, buffer cache and syscall handlers. The bugs were fixed, fixes and the features commmitted by a series culminating in r275745.
-Process spinlock changes. During the work described above, it +
During the work described above, it was noted that process spinlock duties are significantly overloaded (the same is true for the process lock). The spinlock - was split into per-feature lock, see r275121. Also, as result, it - was possible to eliminate recursion on it, r275372.
+ was split into per-feature locks, in r275121. Also, as result, it + was possible to eliminate recursion on it, in r275372.pkg(8) is not only the &os; Package Manager, but the - Package Manager for DragonflyBSD. Additionally support has been +
pkg(8) is not only the &os; Package Manager, but also the + Package Manager for DragonflyBSD. Support has been added to build pkg(8) on OS X and Linux. This work will allow other Operating Systems the option of adopting pkg(8) to manage their packages and bring new @@ -372,11 +383,11 @@ reported by mdoc(7) in the FreeBSD manual pages. This greatly improves the quality of our manual pages.
-Most manual pages with remaining issues are from contrib/ for +
Most manual pages with remaining issues are from contrib/, for which changes should be reported and fixed upstream.
The "manlint" target has also been switch to use mandoc - -Tlint which results in the target being way more useful + -Tlint, which results in the target being more useful when working on manual pages.
Some groff(1) vs mandoc(1) formatting @@ -390,12 +401,12 @@ mandoc(1).
Figure out a way to detect non mandoc(1) friendly +
Figure out a way to detect non mandoc(1) unfriendly manpages from ports and create catpages with groff(1) for them.
Remove groff(1) from base.
+Remove groff(1) from the base system.
The initial support for external toolchain only supported +
The initial external toolchain work only supported clang. It has been extended to support recent GCC (4.9.1 has been tested) and recent binutils (2.24 and 2.25).
@@ -454,8 +465,8 @@ the kernel to make sure it is possible to build the kernel with recent GCC (first 4.6 and then 4.9.1) -The build system has been changed to build libc++ as a C++ - stack when a recent enough GCC (4.6+) is used to build world. +
The build system has been changed to build libc++ as the C++ + standard library implementation when a recent enough GCC (4.6+) is used to build world.
To simplify using an external toolchain, the following @@ -549,14 +560,14 @@
This quarter was exciting time for the GNOME Team. We imported GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree. At the same time we removed the old GNOME 2.32 desktop. And two weeks later - we updated GNOME to 3.14.2 and CINNAMON to 2.4.2 which was collected + we updated GNOME to 3.14.2 and CINNAMON to 2.4.2, which was collected while the preparation for the initial GNOME 3.14.0 import was underway.
-We moved our development repo to GitHub. The link is in the links - section. The repo is structured as follows: the master branch +
We moved our development repo to GitHub. + The repo is structured as follows: the master branch is vanilla &os; Ports, and we have theme branches for topics, - like the porting of MATE 1.9 (mate-1.10 branch) and GNOME 3.15 + such as the porting of MATE 1.9 (mate-1.10 branch) and GNOME 3.15 (gnome-3.16 branch). The GNOME 3.14 branch (gnome-3.14) is not used/updated anymore because the content has been committed to ports, but is kept around for the history.
@@ -848,10 +859,10 @@ the Jenkins 1.586 release. This fixed problems with PAM authentication support in Jenkins on FreeBSD [JENKINS-21507]. -xserver was upgraded from 1.12 to 1.14. This is the last version of xserver supporting Mesa 9.1. Changes are described in an article - on the blog. The most noticeable one is probably the switch from + on the blog. The most noticeable one is the switch from the input device detection back-end based on HAL to the one based on - devd. hald(8) is still required by many desktop environments, but + devd(8). hald(8) is still required by many desktop environments, but the X.Org server itself is free from it.
xserver was the last port supporting the WITH_NEW_XORG @@ -1089,14 +1100,14 @@ At the same time, the new-xorg alternate pkg repository was deprecated.
-After discussion, two patent-encumbered options were enabled by - default:
+After discussion, two options were enabled by default:
These two packages now provide a better user experience out-of-the-box. Users who are uncomfortable with the options may unset them and rebuild the ports. There is no need to rebuild @@ -1235,7 +1246,7 @@
During this quarter almost all pending Xen changes have been - committed, enabling the usage of FreeBSD as Dom0 under the new + committed, enabling FreeBSD to be used as Dom0 under the new PVH mode. The set of features supported by FreeBSD is still limited, but it should allow for basic usage of FreeBSD as Dom0. Support for booting Xen from the FreeBSD boot loader will be committed very soon @@ -1309,7 +1320,7 @@
Just before the end of the year, we have updated clang, - llvm and lldb in base to 3.5.0 release. These all contain + llvm and lldb in the base system to 3.5.0 release. These all contain numerous improvements; please see the linked release notes for more detailed information.
@@ -1366,7 +1377,7 @@ of &os;, announcing code freezes and maintaining the respective branches, among other things. -The &os; 10.1-RELEASE cycle completed November 14th, +
The &os; 10.1-RELEASE cycle completed on November 14th, marking the second official release point from the stable/10 branch, just short of three weeks later than the original schedule anticipated.
@@ -1412,8 +1423,8 @@ Some highlights of the work in this area include the following:The ELF Tool Chain project provides BSD licensed +
The ELF Tool Chain project provides BSD-licensed implementations of compilation tools and libraries for building and analyzing ELF objects. It started as part of &os; but has moved to a standalone project to encourage wider participation @@ -1510,8 +1521,8 @@ missing functionality in ELF note parsing is added. ELF Tool Chain's elfcopy provides equivalent functionality to Binutils objcopy, and accepts the same command-line arguments. For it to be - a viable replacement for all uses of objcopy in the base system it - will need to gain support for writing portable exectuable (PE) + a viable replacement for all uses of objcopy in the base system, it + must gain support for writing portable exectuable (PE) format binaries, which are used in by UEFI boot code.
The ELF Tool Chain project does not currently provide @@ -1808,7 +1819,7 @@
The main goal of the lemul project is the execution of - multithreaded Linux applications, which requires the glibc library + multithreaded Linux applications that requires the glibc library version 2.20 or later to be available on &os;. Glibc 2.20 requires a Linux kernel (or emulation thereof) of version 2.6.32 or later. The main obstacle preventing this is that the current @@ -2022,13 +2033,15 @@
-The ports framework's Linux emulation stack was upgraded to +
The ports collection's Linux emulation stack was upgraded to include CentOS 6.6 on November 11. After smoothing out several bugs that had been introduced, we have been able to bump the default version of the Linux userland from Fedora 10 to CentOS 6.6 on December 9. Providing a more - modern Linux userland and supporting libraries allows a great - number of Linux applications to be run on &os;. The goal + modern Linux userland and supporting libraries allows a large + number of Linux applications to be run on &os;.
+ +The goal behind providing an updated Fedora-based userland is to support more desktop-oriented applications, which require newer libraries than are provided by CentOS 6. Providing 64-bit versions of @@ -2293,7 +2306,7 @@ to work with machine-readable output instead of human-readable output.
-Juniper Networks has created a library called libxo, that +
Juniper Networks has created a library called libxo, which
makes it easy for utilities to emit output in various
formats. By default the text output is emitted, but with the
introduction of the —libxo option this can be changed to
From owner-svn-doc-head@FreeBSD.ORG Mon Jan 12 21:14:43 2015
Return-Path: Detailed descriptions of past, present, and future releases.
- Look here first to determine what the latest version of FreeBSD
- is. There are many options for installing FreeBSD, including
- installation from CD-ROM, DVD, USB stick or even directly using
- anonymous FTP, HTTP, or NFS. Depending on the &os; version you want
- to install, please read through the &os; 9.X/10.X
- installation guide or the &os; 8.X
- installation guide before downloading the entire FreeBSD distribution. Modern PCs use the amd64 architecture, including those with
+ Intel® branded processors. Computers with more than
+ 3 GB of memory should use amd64. If the computer is an
+ older, 32-bit only model, use i386. For embedded devices and
+ single-board computers (SBC) such as the Raspberry Pi, Beagle
+ Bone Black, Panda Board, and Zed Board, use the armv6 SD card
+ image. The &os; installer can be downloaded in a number of different
+ formats including CD (disc1), DVD (dvd1), and Network Install
+ (bootonly) sized ISO
+ Disc Images, as well as regular and mini USB memory stick
+ images. Later versions of &os; are also offered as prebuild
+ expandable Virtual Machine images, and as SD Cards for embedded
+ platforms. If you plan on getting FreeBSD via FTP or HTTP, please check
- the listing of mirror
- sites in the handbook to see if there is a site
- closer to you. Note: If you are in doubt of which platform /
- architecture to get, you probably need i386 if you have
- an older computer, and amd64 if you have a newer
- computer. If you are interested in a purely experimental
- snapshot release of FreeBSD-CURRENT (AKA
+ snapshot release of &os;-CURRENT (AKA
&rel.head;-CURRENT), aimed at developers and bleeding-edge
testers only, then please see the &os; Snapshot Releases page. For
@@ -237,16 +177,67 @@
href="&base;/releases/index.html">release information
page. If you plan on getting &os; via HTTP or FTP, please check
+ the listing of mirror
+ sites in the handbook to see if there is a site
+ closer to you. There are many options for installing &os;, including
+ installation from CD-ROM, DVD, USB Memory Stick or even directly
+ using anonymous FTP, HTTP, or NFS. Depending on the &os;
+ version you want to install, please read through the &os; 9.X/10.X
+ installation guide or the &os; 8.X
+ installation guide before downloading the entire &os;
+ distribution. FreeBSD can be acquired on CD-ROM or DVD from &os; can be acquired on CD-ROM or DVD from FreeBSD Mall, or
one of the other CD-ROM
and DVD Publishers. For downloading past releases, please visit the . FreeBSD is widely used as a building block for other commercial
+ &os; is widely used as a building block for other commercial
and open-source operating systems. The projects below are
- widely used and of particular interest to FreeBSD users. FreeNAS is an open
- source storage platform based on FreeBSD and supports sharing
+ source storage platform based on &os; and supports sharing
across Windows, Apple, and UNIX-like systems. PC-BSD is a FreeBSD
+ PC-BSD is a &os;
derivative with a graphical installer and impressive desktop
tools aimed at ease of use for the casual computer
user. pfSense is a free,
- open source customized distribution of FreeBSD tailored for
+ open source customized distribution of &os; tailored for
use as a firewall and router. The FreeBSD Ports Collection is a diverse collection of utility
- and application software that has been ported to FreeBSD. The &os; Ports Collection is a diverse collection of utility
+ and application software that has been ported to &os;. With funding from the &os; Foundation, the &os; forums
- were migrated to XenForo software. The new software is far more
+ were migrated to the XenForo software. The new software is far more
capable and easy to use. While the entire forum team
contributed, &a.danger; did an excellent job
importing existing users and messages and bringing back the
@@ -166,15 +166,15 @@
The Reaper facility, to allow a process to reliably track the
running and exiting state of the whole subtree of the processes,
was added. It is intended to improve tools like timeout(1) or
- poudriere, by making it impossible for the runaway granchild to
- escape the controlling process. Feature was designed based on
- similar facility in the DragonFlyBSD and Linux, with some
- references to the Solaris contracts. Committed to HEAD in
+ poudriere, by making it impossible for the runaway grandchild to
+ escape the controlling process. The feature was designed based on
+ similar facilities in DragonFlyBSD and Linux, with some
+ references to Solaris contracts. Committed to HEAD in
r275800. The FreeBSD suspension code does not
ensure that the system, both software and hardware,
- is in the steady and consistent state. One aspect is
+ is in a steady and consistent state. One aspect is
usermode process activity, which is not yet stopped, continuing to
making requests to the hardware. It is not realistic to expect
drivers to be able to correctly handle the calls after
@@ -187,12 +187,12 @@
existing single-threading code, but extending it to allow external
thread to put some processes into stopped state. Also, a facility
to sync filesystems before suspend was added, to ensure that
- consistent metadata and as much as possilbe of the cached user
+ consistent metadata and as much as possible of the cached user
data are on stable storage, to minimize damage of failed
resume. The code stressed some parts of the system and has lead to
- discovery of a numbers of bugs in the different areas,
+ discovery of a numbers of bugs in different areas,
including process management, buffer cache and syscall
handlers. The bugs were fixed, fixes and the features commmitted
by a series culminating in r275745. Implement flexible dependencies. Test the developement branch. Test the development branch. More developers are needed, check the Issues on Github. Those packages will depend on special version of GCC
+ Those packages will depend on special versions of GCC
(minimalistic cross-built ready GCC) and on binutils. To use
them run: make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc
TARGET_ARCH=powerpc64 Adapt and upstream the aarch64 patches for binutils 2.25. Add more pre seeded configurations. Add more pre-seeded configurations. The FreeBSD GNOME Team maintains the GNOME, MATE and CINNAMON desktop
environments and graphical user interfaces for FreeBSD. GNOME 3 is part
of the GNU Project. MATE is a fork of the GNOME 2 desktop. CINNAMON
- is desktop environment using GNOME 3 technologies but with a GNOME 2
+ is a desktop environment using GNOME 3 technologies but with a GNOME 2
look and feel. This quarter was exciting time for the GNOME Team. We imported
+ This quarter was an exciting time for the GNOME Team. We imported
GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree. At the same
time we removed the old GNOME 2.32 desktop. And two weeks later
we updated GNOME to 3.14.2 and CINNAMON to 2.4.2, which was collected
@@ -847,7 +847,7 @@
Since the last status report, many people have contributed
- help in various areas to help with with Continuous Integration
+ help in various areas to help with Continuous Integration
and Testing in FreeBSD. Some of the highlights include: We migrated our Ports development tree to Git and GitHub. Tracking
changes in the official Ports tree and preparing patches is way
easier. Furthermore, we can accept pull requests. All reasons behind
- this change are detailed on the blog and the workf-low is described
+ this change are detailed on the blog and the workflow is described
on the wiki. The XDC 2014 (X Developer's Conference) was a great conference.
@@ -1328,7 +1328,7 @@
At this point, FreeBSD 10.0 and later provide that support, at least
on x86. In the near future, more components from the llvm.org will
+ In the near future, more components from llvm.org will
be updated in base, with libc++ and libcompiler-rt most likely
being the first. While most ports that were impacted by this update have
+ While most ports that were impacted by this update have
already been fixed, there are still a few that do not work with
the clang 3.5.0 update. The ELF Tool Chain project does not currently provide
replacements for as, ld, and objdump. For &os; these tools will
@@ -1657,7 +1657,7 @@
Improve documentation. Improve documentation. In additional to the PCI infrastructure, individual PCI drivers
+ In addition to the PCI infrastructure, individual PCI drivers
must be extended to implement SR-IOV. An SR-IOV implementation is in
progress for the ixl(4) driver, which supports the Intel XL710 family
of 40G and 10G NICs. Currently it is planned to have this in review
From owner-svn-doc-head@FreeBSD.ORG Tue Jan 13 01:51:37 2015
Return-Path: The fourth quarter of 2014 included a number of significant improvements to the &os;
- system, in particular in compatibility with other systems. This included
+ system. In particular, compatibility with other systems was enhanced. This included
significant improvements to the Linux compatibility layer, used to
run Linux binaries on &os;, and the port of WINE, used to run Windows
applications. Hypervisor support improved, with &os; gaining the ability
@@ -139,7 +139,7 @@
The Reaper facility, to allow a process to reliably track the
- running and exiting state of the whole subtree of the processes,
- was added. It is intended to improve tools like timeout(1) or
+ The Reaper facility was added, allowing a process to reliably track the
+ running and exiting state of the whole subtree of the processes.
+ It is intended to improve tools like timeout(1) or
poudriere, by making it impossible for the runaway grandchild to
escape the controlling process. The feature was designed based on
similar facilities in DragonFlyBSD and Linux, with some
@@ -191,17 +191,17 @@
data are on stable storage, to minimize damage of failed
resume. The code stressed some parts of the system and has lead to
- discovery of a numbers of bugs in different areas,
- including process management, buffer cache and syscall
- handlers. The bugs were fixed, fixes and the features commmitted
+ The code stressed some parts of the system and has led to
+ discovery of a number of bugs in different areas,
+ including process management, buffer cache, and syscall
+ handlers. The bugs were fixed, and the fixes and features commmitted
by a series culminating in r275745. During the work described above, it
was noted that process spinlock duties are significantly
overloaded (the same is true for the process lock). The spinlock
- was split into per-feature locks, in r275121. Also, as result, it
- was possible to eliminate recursion on it, in r275372. To get started clone the Git repo and follow the directions in
+ To get started, clone the Git repo and follow the directions in
the README. More information is available from the Packer and
Vagrant websites. An important part of the development direction for the 1.4
- release has been done on stabilizing the existing features, and
+ release was stabilizing the existing features and
improving the pkg(8) experience on small/embedded
- machines (reduce memory usage, speed up operations). pkg(8) is not only the &os; Package Manager, but also the
Package Manager for DragonflyBSD. Support has been
@@ -340,7 +340,7 @@
This change also fixes an issue with FreeBSD man(1)
- command not able to properly deal with ".so" in gzipped manual
+ This change also fixes an issue with the &os; man(1)
+ command not being able to properly deal with ".so" in gzipped manual
pages. The documentation team has spent a lot of time fixing issues
@@ -386,12 +386,12 @@
Most manual pages with remaining issues are from contrib/, for
which changes should be reported and fixed upstream. The "manlint" target has also been switch to use mandoc
+ The "manlint" target has also been switched to use mandoc
-Tlint, which results in the target being more useful
when working on manual pages. Some groff(1) vs mandoc(1) formatting
- differencies have been spotted and reported to mandoc's upstream
+ Some groff(1) versus mandoc(1) formatting
+ differences have been spotted and reported to mandoc's upstream
developers. Figure out a way to detect non mandoc(1) unfriendly
- manpages from ports and create catpages with groff(1)
+ Figure out a way to detect mandoc(1)-unfriendly
+ manpages in ports and create catpages with groff(1)
for them. The main goal of the external toolchain project is to be able
- to build world and kernel with non default toolchain. It can be
+ to build world and kernel with non-default toolchain. It can be
helpful to:
Those packages will depend on special versions of GCC
(minimalistic cross-built ready GCC) and on binutils. To use
- them run: make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc
+ them, run: make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc
TARGET_ARCH=powerpc64 As a result of this effort, it has been possible to
@@ -504,7 +504,7 @@
Since 2006, initial support for Linux timer function
compatibility support was present but untested.
This update corrects the initial implementation and makes it
- available to the 32bit linuxolator on amd64, not just on i386.
+ available to the 32-bit Linuxulator on amd64, not just on i386.
Starting with &os; 10.1, this enables users to run another
FPGA high-level synthesis toolchain and emulation platform
- on a FreeBSD system.
+ on a &os; system.
The FreeBSD GNOME Team maintains the GNOME, MATE and CINNAMON desktop
- environments and graphical user interfaces for FreeBSD. GNOME 3 is part
+ The &os; GNOME Team maintains the GNOME, MATE, and CINNAMON desktop
+ environments and graphical user interfaces for &os;. GNOME 3 is part
of the GNU Project. MATE is a fork of the GNOME 2 desktop. CINNAMON
is a desktop environment using GNOME 3 technologies but with a GNOME 2
look and feel. This quarter was an exciting time for the GNOME Team. We imported
GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree. At the same
- time we removed the old GNOME 2.32 desktop. And two weeks later
+ time, we removed the old GNOME 2.32 desktop. And two weeks later
we updated GNOME to 3.14.2 and CINNAMON to 2.4.2, which was collected
while the preparation for the initial GNOME 3.14.0 import was
- underway. We moved our development repo to GitHub.
The repo is structured as follows: the master branch
- is vanilla &os; Ports, and we have theme branches for topics,
+ is vanilla &os; Ports, and we have theme branches for topics
such as the porting of MATE 1.9 (mate-1.10 branch) and GNOME 3.15
(gnome-3.16 branch). The GNOME 3.14 branch (gnome-3.14) is not
- used/updated anymore because the content has been committed to
+ used or updated any more because the content has been committed to
ports, but is kept around for the history. MATE 1.10 porting is underway, the latest 1.9 releases are
+ MATE 1.10 porting is under way, the latest 1.9 releases are
available in the mate-1.10 branch. GNOME 3.16 porting is underway, and is available in the
+ GNOME 3.16 porting is under way, and is available in the
gnome-3.16 branch. This quarter, Qt 5.3 was finally committed to the ports tree
- after extensive work that included cleaning up and/or changing a lot of
+ This quarter, Qt 5.3 was finally committed to the ports tree.
+ Extensive work was required, including cleaning up and/or changing a lot of
the Qt5 ports infrastructure to make it both easier to maintain the Qt
ports as well as finally make it possible to build newer versions when
older ones are already installed on the system. Since the last status report, many people have contributed
help in various areas to help with Continuous Integration
- and Testing in FreeBSD. Some of the highlights include: Xfce is a free software desktop environment for Unix and
- Unix-like platforms, such as FreeBSD. It aims to be fast and
+ Unix-like platforms, such as &os;. It aims to be fast and
lightweight, while still being visually appealing and easy to use. During this quarter, the team has kept up-to-date the following
- applications: During this quarter, the team has kept these applications up-to-date: Moreover, we are working on the next stable release, below list
- of ports updated: Moreover, we are working on the next stable release, with these
+ ports being updated: Find workaround when acpi_video(4) is not functional
+ Find workaround when acpi_video(4) is not functional
(panel crashes); OpenBSD seems to have same problem. Cleanup patch in order to add new panel plugin in ports
+ Clean up patch in order to add new panel plugin in ports
tree. Continue to work on documentation, especially the Porter's
- handbook. graphics/gbm and devel/libclc are new ports used
by Mesa to implement OpenCL. The next step is to finish the port for
@@ -1090,7 +1089,7 @@
of xserver supporting Mesa 9.1. Changes are described in an article
on the blog. The most noticeable one is the switch from
the input device detection back-end based on HAL to the one based on
- devd(8). hald(8) is still required by many desktop environments, but
+ devd(8). hald(8) is still required by many desktop environments, but
the X.Org server itself is free from it. xserver was the last port supporting the WITH_NEW_XORG
@@ -1104,7 +1103,7 @@
On the kernel side, Tijl Coosemans added AGP support back to the
TTM memory manager and therefore to the Radeon driver. His work was
- merged back to stable/10 and will be available in FreeBSD
+ merged back to stable/10 and will be available in &os;
10.2-RELEASE. We migrated our Ports development tree to Git and GitHub. Tracking
changes in the official Ports tree and preparing patches is way
- easier. Furthermore, we can accept pull requests. All reasons behind
+ easier. Furthermore, we can accept pull requests. All of the reasons behind
this change are detailed on the blog and the workflow is described
on the wiki. Our next items on the roadmap are: During this quarter almost all pending Xen changes have been
- committed, enabling FreeBSD to be used as Dom0 under the new
- PVH mode. The set of features supported by FreeBSD is still limited,
- but it should allow for basic usage of FreeBSD as Dom0. Support for
- booting Xen from the FreeBSD boot loader will be committed very soon
+ committed, enabling &os; to be used as Dom0 under the new
+ PVH mode. The set of features supported by &os; is still limited,
+ but it should allow for basic usage of &os; as Dom0. Support for
+ booting Xen from the &os; boot loader will be committed very soon
to HEAD. Apart from testing on a variety of hardware, work has now
@@ -1257,8 +1256,8 @@
parity with a traditional PV Dom0 and to declare the PVH ABI as
stable. Regarding guest improvements (running FreeBSD as a DomU),
- there's also ongoing work to add unmapped IO support to Xen blkfront,
+ Regarding guest improvements (running &os; as a DomU),
+ there is also ongoing work to add unmapped IO support to Xen blkfront,
which is blocked pending some modifications to the generic bounce
buffer code. Just before the end of the year, we have updated clang,
- llvm and lldb in the base system to 3.5.0 release. These all contain
- numerous improvements; please see the linked release notes for
+ Just before the end of the year, we updated clang,
+ llvm, and lldb in the base system to 3.5.0 release. These all contain
+ numerous improvements. Please see the linked release notes for
more detailed information. This is the first release that requires C++11 support to build.
- At this point, FreeBSD 10.0 and later provide that support, at least
+ At this point, &os; 10.0 and later provide that support, at least
on x86. In the near future, more components from llvm.org will
@@ -1333,7 +1332,7 @@
being the first. Thanks to Ed Maste, Roman Divacky, Andrew Turner, Justin
- Hibbits and Antoine Brodin for their invaluable help with this
+ Hibbits, and Antoine Brodin for their invaluable help with this
import. There are still some open issues with the ARM, PowerPC
+ There are still some open issues with the ARM, PowerPC,
and Sparc64 architectures, and any help in this area is very much
appreciated. As of the end of Q4 the ports tree holds more than 24,000
ports, and the PR count is just over 1,400. As during the
previous quarter the tree saw a sustained activity with
- almost 6,000 commits and more than 1,600 ports PR closed! In Q4 five new developers were granted a ports commit bit
+ In Q4, five new developers were granted a ports commit bit
(gordon@, jmg@, jmmv@, bofh@, truckman@) and six were taken
in for safekeeping (sylvio@, pclin@, flz@, jsa@, anders@,
motoyuki@). This quarter also saw the release of the fourth quarterly
branch, namely 2014Q4. On QA side 39 exp-runs were performed to validate sensitive
+ On the QA side, 39 exp-runs were performed to validate sensitive
updates or cleanups. 2014 is the year that saw the highest number of commits
in all of our ports tree's history! As for the PR front and
- to keep our beloved tree in such a good shape we would love
+ to keep our beloved tree in good shape, we would love
to see the same commitment from our developers next year! The project's code is located in the FreeBSD Project's
- Subversion repository, at base/user/dchagin/lemul (a
+ The project's code is located in the &os; Project's
+ Subversion repository at base/user/dchagin/lemul (a
little bit old). To facilitate merging the improvements back to
head, several patches have been placed on reviews.FreeBSD.org with
the tag #lemul. Nearly half of the patches have already
@@ -1883,7 +1882,7 @@
Extend xucred suppport, which is required for many Linux
+ Extend xucred support, required for many Linux
applications. The ports have packages built for amd64 (available through the
ports emulators/i386-wine and i386-wine-devel) for &os; 8.4, 9.1+,
- 10.0+ and CURRENT. Accomplishments include: We would like to thank all volunteers who contributed feedback
+ We would like to thank all the volunteers who contributed feedback
or even patches. We would also like to welcome kmoore@ to the Wine
- team. He has been extensively involved in bring wine-compholio to the
+ team. He has been extensively involved in bringing wine-compholio to the
Ports Collection. Future development on Wine will focus on: Maintaining and improving Wine is a major undertaking that
- directly impacts end-users on &os; (including many gamers). If you
- are interested in helping please contact us. We will happily accept
- patches, suggest areas of focus or have a chat. FreeBSD/amd64 integration (see the &os;/amd64 integration (see the i386-Wine wiki page). There is growing interest in ARM's 64-bit architecture.
- Officially named as AArch64, it is also known as ARMv8 and arm64.
- Andrew Turner started initial work on the FreeBSD/arm64 port at
+ Officially named AArch64, it is also known as ARMv8 and arm64.
+ Andrew Turner started initial work on the &os;/arm64 port at
the end of 2012. The &os; Foundation is now collaborating with ARM,
@@ -2229,9 +2228,9 @@
arm64, and significant progress was made on the port over the last
quarter of 2014. As of the end of the year &os; boots to single-user mode
+ As of the end of the year, &os; boots to single-user mode
on arm64, executing both static and dynamic applications. Patches
- in review allow &os; to boot to multi-user mode and these are
+ in review allow &os; to boot to multi-user mode, and these are
expected to be merged soon. This includes implementing many stub
functions in userland and the kernel. With this, &os; has booted to
multi-user mode on both the ARM Foundation Model and the QEMU full
@@ -2279,7 +2278,7 @@
Juniper Networks has created a library called libxo, which
makes it easy for utilities to emit output in various
- formats. By default the text output is emitted, but with the
- introduction of the —libxo option this can be changed to
- XML, JSON and HTML. The &os; project has imported this library
+ formats. By default, text output is emitted, but with the
+ introduction of the --libxo option this can be changed to
+ XML, JSON, and HTML. The &os; project has imported this library
into the base system and is in the process of rewriting utilities
to use libxo. This is a draft of the October–December 2014 status
- report. Please check back after it is finalized, and an
- announcement email is sent to the &os;-Announce mailing
- list. This is a draft of the October–December 2014
+ status report. Please check back after it is finalized, and
+ an announcement email is sent to the &os;-Announce mailing
+ list. This report covers &os;-related projects between October and
December 2014. This is the last of four reports planned for
2014. The fourth quarter of 2014 included a number of significant improvements to the &os;
- system. In particular, compatibility with other systems was enhanced. This included
- significant improvements to the Linux compatibility layer, used to
- run Linux binaries on &os;, and the port of WINE, used to run Windows
- applications. Hypervisor support improved, with &os; gaining the ability
- to run as domain 0 on Xen's new high-performance PVH mode, bhyve gaining
- AMD support, and new tools for creating &os; VM images arriving. This quarter was also an active time for the toolchain, with numerous
- improvements to the compiler, debugger, and other components, including
- initial support for C++14, which should be complete by
- &os; 10.2. The fourth quarter of 2014 included a number of significant
+ improvements to the &os; system. In particular, compatibility
+ with other systems was enhanced. This included significant
+ improvements to the Linux compatibility layer, used to run Linux
+ binaries on &os;, and the port of WINE, used to run Windows
+ applications. Hypervisor support improved, with &os; gaining
+ the ability to run as domain 0 on Xen's new high-performance PVH
+ mode, bhyve gaining AMD support, and new tools for creating &os;
+ VM images arriving. This quarter was also an active time for the toolchain, with
+ numerous improvements to the compiler, debugger, and other
+ components, including initial support for C++14, which should be
+ complete by &os; 10.2. Thanks to all the reporters for the excellent work! With funding from the &os; Foundation, the &os; forums
- were migrated to the XenForo software. The new software is far more
- capable and easy to use. While the entire forum team
- contributed, &a.danger; did an excellent job
- importing existing users and messages and bringing back the
- often-requested "Thanks" feature. The upgrade was completed in
- time to be ready for the influx of new users from the release of
- &os; 10.1, and we have already seen an increase in usage. Developers with an @FreeBSD.org address can contact forum
- administrators to obtain the highly-desired "@" suffix on their
- forum user name along with a Developer flag. We want to thank the Foundation for making this possible, and
the users for their patience and continued presence on the
@@ -128,7 +131,8 @@
Encourage more developers and users to try the new forums. Encourage more developers and users to try the new
+ forums. The Reaper facility was added, allowing a process to reliably track the
- running and exiting state of the whole subtree of the processes.
- It is intended to improve tools like timeout(1) or
- poudriere, by making it impossible for the runaway grandchild to
- escape the controlling process. The feature was designed based on
- similar facilities in DragonFlyBSD and Linux, with some
- references to Solaris contracts. Committed to HEAD in
- r275800. The FreeBSD suspension code does not
- ensure that the system, both software and hardware,
- is in a steady and consistent state. One aspect is
- usermode process activity, which is not yet stopped, continuing to
- making requests to the hardware. It is not realistic to expect
- drivers to be able to correctly handle the calls after
- SUSPEND_CHILD. We developed a facility to stop
- usermode threads at safe points, where they are known to not
- own and to not wait for kernel resources, in particular, not
- waiting for device requests finishing. It is based on the
- existing single-threading code, but extending it to allow external
- thread to put some processes into stopped state. Also, a facility
- to sync filesystems before suspend was added, to ensure that
- consistent metadata and as much as possible of the cached user
- data are on stable storage, to minimize damage of failed
- resume. The Reaper facility was added, allowing a process to reliably
+ track the running and exiting state of the whole subtree of
+ the processes. It is intended to improve tools like
+ timeout(1) or poudriere, by making it impossible for the
+ runaway grandchild to escape the controlling process. The
+ feature was designed based on similar facilities in
+ DragonFlyBSD and Linux, with some references to Solaris
+ contracts. Committed to HEAD in r275800. The FreeBSD suspension code does not ensure that the system,
+ both software and hardware, is in a steady and consistent
+ state. One aspect is usermode process activity, which is not
+ yet stopped, continuing to making requests to the hardware.
+ It is not realistic to expect drivers to be able to correctly
+ handle the calls after SUSPEND_CHILD. We developed a facility to stop usermode threads at safe
+ points, where they are known to not own and to not wait for
+ kernel resources, in particular, not waiting for device
+ requests finishing. It is based on the existing
+ single-threading code, but extending it to allow external
+ thread to put some processes into stopped state. Also, a
+ facility to sync filesystems before suspend was added, to
+ ensure that consistent metadata and as much as possible of the
+ cached user data are on stable storage, to minimize damage of
+ failed resume. The code stressed some parts of the system and has led to
- discovery of a number of bugs in different areas,
- including process management, buffer cache, and syscall
- handlers. The bugs were fixed, and the fixes and features commmitted
- by a series culminating in r275745. During the work described above, it
- was noted that process spinlock duties are significantly
- overloaded (the same is true for the process lock). The spinlock
- was split into per-feature locks in r275121. As result, it
- was also possible to eliminate recursion on it in r275372. During the work described above, it was noted that process
+ spinlock duties are significantly overloaded (the same is true
+ for the process lock). The spinlock was split into
+ per-feature locks in r275121. As result, it was also possible
+ to eliminate recursion on it in r275372. Most system features work, including keyboard, WiFi, sound,
- VESA graphics, touchpad, USB and decent battery life (5 to 6 hours). Packer is a tool for
- creating identical machine images for multiple platforms from a
- single source configuration. Vagrant is a tool to
create and configure lightweight, reproducible, and portable
development environments. To get started, clone the Git repo and follow the directions in
- the README. More information is available from the Packer and
- Vagrant websites. To get started, clone the Git repo and follow the directions
+ in the README. More information is available from the Packer
+ and Vagrant websites. The package development team has released pkg(8) 1.4.
- This release fixes lots of bugs and adds some new features:
+ The package development team has released pkg(8)
+ 1.4. This release fixes lots of bugs and adds some new
+ features:
An important part of the development direction for the 1.4
- release was stabilizing the existing features and
- improving the pkg(8) experience on small/embedded
- machines (reducing memory usage and speeding up operations). pkg(8) is not only the &os; Package Manager, but also the
- Package Manager for DragonflyBSD. Support has been
+ pkg(8) is not only the &os; Package Manager, but
+ also the Package Manager for DragonflyBSD. Support has been
added to build pkg(8) on OS X and Linux. This work
will allow other Operating Systems the option of adopting
pkg(8) to manage their packages and bring new
@@ -321,18 +331,23 @@
Add more regression tests. Package FreeBSD base. Allow using mtree as a plist when creating a package. Implement flexible dependencies. Test the development branch. More developers are needed, check the Issues on Github. This change also fixes an issue with the &os; man(1)
- command not being able to properly deal with ".so" in gzipped manual
- pages. The documentation team has spent a lot of time fixing issues
- reported by mdoc(7) in the FreeBSD manual pages. This
- greatly improves the quality of our manual pages. Most manual pages with remaining issues are from contrib/, for
- which changes should be reported and fixed upstream. The "manlint" target has also been switched to use mandoc
- -Tlint, which results in the target being more useful
- when working on manual pages. Most manual pages with remaining issues are from contrib/,
+ for which changes should be reported and fixed upstream. The "manlint" target has also been switched to use
+ mandoc -Tlint, which results in the target being more
+ useful when working on manual pages. Some groff(1) versus mandoc(1) formatting
- differences have been spotted and reported to mandoc's upstream
- developers. The main goal of the external toolchain project is to be able
- to build world and kernel with non-default toolchain. It can be
- helpful to:
+ to build world and kernel with non-default toolchain. It can
+ be helpful to:
The initial external toolchain work only supported
- clang. It has been extended to support recent GCC (4.9.1 has
- been tested) and recent binutils (2.24 and 2.25). A large number of fixes have been committed to HEAD to support
- incompatible behaviour changes between ld(1) from
- binutils 2.17.50 (the version in base) and binutils 2.24+. A large number of warnings have been deactivated when building
- the kernel to make sure it is possible to build the kernel with
- recent GCC (first 4.6 and then 4.9.1) The initial external toolchain work only supported clang. It
+ has been extended to support recent GCC (4.9.1 has been
+ tested) and recent binutils (2.24 and 2.25). A large number of fixes have been committed to HEAD to
+ support incompatible behaviour changes between ld(1)
+ from binutils 2.17.50 (the version in base) and binutils
+ 2.24+. A large number of warnings have been deactivated when
+ building the kernel to make sure it is possible to build the
+ kernel with recent GCC (first 4.6 and then 4.9.1) The build system has been changed to build libc++ as the C++
- standard library implementation when a recent enough GCC (4.6+) is used to build world.
- To simplify using an external toolchain, the following
pre-seeded configurations have been added to the ports tree:
Those packages will depend on special versions of GCC
(minimalistic cross-built ready GCC) and on binutils. To use
- them, run: make CROSS_TOOLCHAIN=powerpc64-gcc TARGET=powerpc
- TARGET_ARCH=powerpc64 As a result of this effort, it has been possible to
successfully build and run a kernel and world built with GCC
- 4.9.1 and binutils 2.24 on sparc64, amd64 (with minor tweaks for
- amd64), powerpc and powerpc64. Patch and upstream GCC 4.9 to support &os; mips, arm and
aarch64. Adapt and upstream the aarch64 patches for binutils 2.25. Adapt and upstream the aarch64 patches for binutils
+ 2.25. Add more pre-seeded configurations. Since 2006, initial support for Linux timer function
- compatibility support was present but untested.
- This update corrects the initial implementation and makes it
- available to the 32-bit Linuxulator on amd64, not just on i386.
- Starting with &os; 10.1, this enables users to run another
FPGA high-level synthesis toolchain and emulation platform
@@ -530,6 +559,7 @@
The &os; GNOME Team maintains the GNOME, MATE, and CINNAMON desktop
- environments and graphical user interfaces for &os;. GNOME 3 is part
- of the GNU Project. MATE is a fork of the GNOME 2 desktop. CINNAMON
- is a desktop environment using GNOME 3 technologies but with a GNOME 2
- look and feel. This quarter was an exciting time for the GNOME Team. We imported
- GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree. At the same
- time, we removed the old GNOME 2.32 desktop. And two weeks later
- we updated GNOME to 3.14.2 and CINNAMON to 2.4.2, which was collected
- while the preparation for the initial GNOME 3.14.0 import was
- under way. We moved our development repo to GitHub.
- The repo is structured as follows: the master branch
- is vanilla &os; Ports, and we have theme branches for topics
- such as the porting of MATE 1.9 (mate-1.10 branch) and GNOME 3.15
- (gnome-3.16 branch). The GNOME 3.14 branch (gnome-3.14) is not
- used or updated any more because the content has been committed to
- ports, but is kept around for the history. The &os; GNOME Team maintains the GNOME, MATE, and CINNAMON
+ desktop environments and graphical user interfaces for &os;.
+ GNOME 3 is part of the GNU Project. MATE is a fork of the
+ GNOME 2 desktop. CINNAMON is a desktop environment using
+ GNOME 3 technologies but with a GNOME 2 look and feel. This quarter was an exciting time for the GNOME Team. We
+ imported GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree.
+ At the same time, we removed the old GNOME 2.32 desktop. And
+ two weeks later we updated GNOME to 3.14.2 and CINNAMON to
+ 2.4.2, which was collected while the preparation for the
+ initial GNOME 3.14.0 import was under way. We moved our development repo to GitHub. The repo is
+ structured as follows: the master branch is vanilla
+ &os; Ports, and we have theme branches for topics
+ such as the porting of MATE 1.9 (mate-1.10 branch) and GNOME
+ 3.15 (gnome-3.16 branch). The GNOME 3.14 branch (gnome-3.14)
+ is not used or updated any more because the content has been
+ committed to ports, but is kept around for the history. The GNOME website is stale. Work is starting on updating
- the development section. We could use some help here. The GNOME website is stale. Work is starting on updating
+ the development section. We could use some help here. The &os; Core Team constitutes the project's "Board of
- Directors", responsible for deciding the project's overall goals
- and direction as well as managing specific areas of the &os;
- project landscape. During the fourth quarter of 2014, the &os; Core team saw the
culmination of a long-running project to rebuild the &os;
- Forums. The chosen solution was to license XenForo; core would
- like to thank the FreeBSD Foundation for paying the licensing
- costs of this software. Much discussion ensued concerning the "New Support Model"
following Core's meeting at EuroBSDCon in September. It was
@@ -620,9 +650,9 @@
at 11.0-RELEASE. In order to ensure that 10.1-RELEASE shipped with support for
- up-to-date X Windows and KDE4, core approved the switch to 'new
- Xorg' as the default in time for building the packages for that
- release. Git was officially promoted from beta to an officially
supported version control system. Git is available as a
@@ -630,32 +660,32 @@
exported copy from SVN, the primary and only read-write
repository. The &os; git repositories (exported from the
master SVN version control) will shortly be available at
- https://git.freebsd.org/, and core has been active
- in ensuring that there is a sufficient body of Git
- administrators available with access to appropriate
- documentation in order to maintain a good git service. Core mediated in disputes between a number of committers over
some updates to system sources, and fielded complaints about
- code quality of some other work in critical areas.
- While such disagreements will occasionally occur, core is
- promoting the routine use of the Phabricator service in order to
- review work before committal. Catching problems early is in the
- project's best interests, and discussion of changes in an open
- review context should minimize confrontational demands for
- immediate back-out of changes. Core is working on a charter for a proposed new QA team, to
- encompass members of the Release Engineering and Security teams,
- as well as committers with interests in standards compliance.
- It is envisioned that the QA team will take responsibility for
- merging code from HEAD into the STABLE branches, run integration
- testing against those updates and handle merging patches and
- bug-fixes submitted to the &os; project from third parties. During this quarter, core issued two new commit bits, and also
- took two commit bits into safe-keeping. During this quarter, core issued two new commit bits, and
+ also took two commit bits into safe-keeping. The KDE on &os; team focuses on packaging and making sure that the
- experience of KDE and Qt on &os; is as good as possible. The KDE on &os; team focuses on packaging and making sure
+ that the experience of KDE and Qt on &os; is as good as
+ possible. As mentioned last quarter, Alonso Schaich (alonso@) became a
- committer and since then has made good progress helping his mentors
- Raphael Kubo da Costa (rakuco@) and Max Brazhnikov (makc@) maintain all
- Qt and KDE-related ports. This quarter, Qt 5.3 was finally committed to the ports tree.
- Extensive work was required, including cleaning up and/or changing a lot of
- the Qt5 ports infrastructure to make it both easier to maintain the Qt
- ports as well as finally make it possible to build newer versions when
- older ones are already installed on the system. We have also updated KDE in our experimental area51 repository
- and committed several updates to other ports such as KDevelop and KDE
- Telepathy. Overall, we have worked on the following releases:
+ Extensive work was required, including cleaning up and/or
+ changing a lot of the Qt5 ports infrastructure to make it both
+ easier to maintain the Qt ports as well as finally make it
+ possible to build newer versions when older ones are already
+ installed on the system. We have also updated KDE in our experimental area51
+ repository and committed several updates to other ports such
+ as KDevelop and KDE Telepathy. Overall, we have worked on the
+ following releases:
Tobias Berner has contributed patches to update QtCreator to 3.3.0 as
- well as KDE Frameworks 5 ports which are under review for inclusion
- in our experimental area51 repository. Tobias Berner has contributed patches to update QtCreator to
+ 3.3.0 as well as KDE Frameworks 5 ports which are under review
+ for inclusion in our experimental area51 repository. Try to contribute to the work on getting rid of HAL on &os;,
- which seems to be gaining more traction recently. Try to contribute to the work on getting rid of HAL on
+ &os;, which seems to be gaining more traction recently. Add KDE Frameworks 5 ports to our experimental repository. Add KDE Frameworks 5 ports to our experimental
+ repository. Lucas is moving on to &os; books on ZFS, Specialty
- Filesystems, and jails. They will hopefully be available by
+ Filesystems, and jails. They will hopefully be available by
BSDCan 2015. Get status updates on his blog, or follow @mwlauthor on Twitter. Get status updates on his blog, or follow @mwlauthor on
+ Twitter. Improve the maintenance of nodes in the Jenkins cluster
- using devops frameworks such as Saltstack. Xfce is a free software desktop environment for Unix and
- Unix-like platforms, such as &os;. It aims to be fast and
- lightweight, while still being visually appealing and easy to use. During this quarter, the team has kept these applications up-to-date: During this quarter, the team has kept these applications
+ up-to-date: Two new ports have also been added (taken from our repository): Two new ports have also been added (taken from our
+ repository): Moreover, we are working on the next stable release, with these
- ports being updated: Moreover, we are working on the next stable release, with
+ these ports being updated: A FAQ is being written D1305. A FAQ is being written
+ D1305. Find workaround when acpi_video(4) is not functional
- (panel crashes); OpenBSD seems to have same problem. Find workaround when acpi_video(4) is not
+ functional (panel crashes); OpenBSD seems to have same
+ problem. Clean up patch in order to add new panel plugin in ports
tree. Continue to work on documentation, especially the Porter's
Handbook. The project adds support for AES-GCM and AES-CTR mode to the
- OpenCrypto framework. Both software and AES-NI accelerated versions
- are functional, working and committed. Ermal Luçi (eri@) is working
- on adding support for the additional modes to IPsec. Mesa was upgraded to 10.3, then 10.4 for FreeBSD 10.1-RELEASE and
- 11-CURRENT. We test release candidates and therefore this port is
- now usually updated shortly after a new release. Mesa 10.x brings
- huge improvements in terms of OpenGL standards support, performance
- and stability, especially for Radeon owners. Mesa 9.1 is kept for
- &os; 9.x, but we have plans to fix this; see below. graphics/gbm and devel/libclc are new ports used
- by Mesa to implement OpenCL. The next step is to finish the port for
- Mesa's libOpenCL.so, named Clover. This will permit users to run
- OpenCL programs on Radeon GPUs for now. xserver was upgraded from 1.12 to 1.14. This is the last version
- of xserver supporting Mesa 9.1. Changes are described in an article
- on the blog. The most noticeable one is the switch from
- the input device detection back-end based on HAL to the one based on
- devd(8). hald(8) is still required by many desktop environments, but
- the X.Org server itself is free from it. xserver was the last port supporting the WITH_NEW_XORG
- knob. The knob is now completely removed. This was the occasion to
- add WITH_NEW_XORG and WITH_KMS to the list of
- deprecated knobs to help people clean up their make.conf.
- At the same time, the new-xorg alternate pkg repository was
- deprecated. Mesa was upgraded to 10.3, then 10.4 for FreeBSD 10.1-RELEASE
+ and 11-CURRENT. We test release candidates and therefore this
+ port is now usually updated shortly after a new release. Mesa
+ 10.x brings huge improvements in terms of OpenGL standards
+ support, performance and stability, especially for Radeon
+ owners. Mesa 9.1 is kept for &os; 9.x, but we have plans to
+ fix this; see below. graphics/gbm and devel/libclc are new ports
+ used by Mesa to implement OpenCL. The next step is to finish
+ the port for Mesa's libOpenCL.so, named Clover. This will
+ permit users to run OpenCL programs on Radeon GPUs for
+ now. xserver was upgraded from 1.12 to 1.14. This is the last
+ version of xserver supporting Mesa 9.1. Changes are described
+ in an article on the blog. The most noticeable one is the
+ switch from the input device detection back-end based on HAL
+ to the one based on devd(8). hald(8) is
+ still required by many desktop environments, but the X.Org
+ server itself is free from it. xserver was the last port supporting the
+ WITH_NEW_XORG knob. The knob is now completely
+ removed. This was the occasion to add WITH_NEW_XORG
+ and WITH_KMS to the list of deprecated knobs to help
+ people clean up their make.conf. At the same time,
+ the new-xorg alternate pkg repository was deprecated. After discussion, two options were enabled by default: These two packages now provide a better user experience
- out-of-the-box. Users who are uncomfortable with the options may
- unset them and rebuild the ports. There is no need to rebuild
- anything else. On the kernel side, Tijl Coosemans added AGP support back to the
- TTM memory manager and therefore to the Radeon driver. His work was
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
From owner-svn-doc-head@FreeBSD.ORG Tue Jan 13 15:45:28 2015
Return-Path: With funding from the &os; Foundation, the &os; forums
- were migrated to the XenForo software. The new software is
+ were migrated to XenForo software. The new software is
far more capable and easy to use. While the entire forum team
contributed, &a.danger; did an excellent job importing
existing users and messages and bringing back the
From owner-svn-doc-head@FreeBSD.ORG Tue Jan 13 19:23:18 2015
Return-Path: The &os; Foundation is a 501(c)(3) non-profit organization
+ dedicated to supporting and promoting the &os; Project
+ and community worldwide. Most of the funding is used to
+ support &os; development projects, conferences, and developer
+ summits, purchase equipment to grow and improve the &os;
+ infrastructure, and provide legal support for the Project. We ended the year exceeding our fundraising goal, by raising
+ over $2,372,132, from 1670 donors! Thank you to everyone who
+ made a donation in 2014. We produced issues five and six of the &os; Journal,
+ ending the year with over 6300 subscribers, exceeding our
+ first-year goal of 5000 subscribers. We also added the
+ desktop/digital edition, so people can read the magazine from
+ their browsers. We also hosted a meeting with the Journal
+ Editorial Board and worked out the editorial calendar for the
+ next two years. This includes topics and articles for the
+ future issues. We were a gold sponsor of EuroBSDCon 2014, and a sponsor of
+ the preceding Developer Summit. A few of our team members
+ attended, which allowed us to have an informal face-to-face
+ board meeting, with a focus on supporting the European region.
+ Kirk McKusick gave a two-day &os; tutorial and Erwin
+ Lansing helped run the Developer Summit. We sponsored 5
+ &os; contributors to attend the conference. We were a sponsor of the
+ Grace Hopper
+ Conference.
+ Dru Lavigne gave an introduction to &os; presentation, that
+ was well attended. We also sponsored Shteryana Shopova to
+ represent &os;, along with Dru, at our booth. We were a sponsor of
+ MeetBSD.
+ Most of our team members attended this conference.
+ Kirk McKusick gave a talk on BSD history.
+ We also had a booth, and raised over $2,200 in donations.
+ We sponsored one person to attend this conference. George organized and ran the two-day Silicon Valley Vendor
+ and Developer Summit following MeetBSD.
+ A lot of work gets started and accomplished at these summits,
+ for example, Kirk worked with various folks to get the ino64
+ (64-bit inode numbers) project moving.
+ It started in 2011 as a Summer of Code project and has
+ sputtered since getting pushed into the system. Besides the above conferences, we helped promote &os; at
+ the following conferences:
+
+ We visited a few large &os; users in the Bay Area to
+ discuss their use of &os;, plans, and needs, and help
+ facilitate collaboration between them and the Project. Cheryl Blain joined our board, bringing a strong background
+ in business development and fundraising. We received the largest donation in our history, and our
+ treasurer put together an endowment strategy for us to
+ follow. We increased our &os; marketing efforts to help promote
+ and advocate for &os;, as well as educate people on
+ &os;. Some our &os; marketing highlights include:
+ We are producing a monthly newsletter to highlight what we
+ did the previous month to support the &os; Project.
+ We also produced our
+ December
+ semi-annual newsletter. We redesigned and launched phase 1 of our website.
+ It should be easier to navigate and find the information you
+ need to get help from or to help the Foundation. Glen Barber visited the Microsoft main campus and worked with
+ Microsoft Hyper-V developers to resolve outstanding issues
+ with providing &os; images for the Microsoft Azure
+ platform. Glen also visited the NYI colocation facility to install and
+ configure new servers purchased by the Foundation. We finished the 10.1-RELEASE cycle. Our project development staff and contractors have been
+ working on various projects to add features to and improve
+ &os;. Some of their reports are included in this overall
+ report. Some projects that were worked on this quarter were
+ adding support for 64-bit ARM architecture to &os;,
+ integration work on the vt(4) updated console and UEFI boot
+ support, Secure Boot, refining in-kernel iSCSI target and
+ initiator stack, autofs-based automount daemon, migrating to
+ the ELF Tool Chain, and implementing modern AES modes in
+ &os;'s cryptographic framework. To read more about how we helped support the &os; Project
+ and community, read our
+ semi-annual
+ newsletter. &os; is now available on the DigitalOcean platform. &os; is now available on the DigitalOcean platform. &os; virtual private servers with IPv6 support are now
+ available on the DigitalOcean platform in: San Francisco,
+ New York, London, Amsterdam, and Singapore. DigitalOcean is
+ also seeking &os; tutorials, for which they are offering
+ $200 USD each. ²áµî¡¢¸½ºß¡¢¤½¤·¤Æ¾Íè¤Î¥ê¥ê¡¼¥¹¤Ë´Ø¤¹¤ë¾ÜºÙ¤Ç¤¹¡£
- FreeBSD ¤ÎºÇ¿·¤Î¥Ð¡¼¥¸¥ç¥ó¤¬²¿¤«¤ò³Îǧ¤¹¤ë¤Ë¤Ï¡¢
- ¤Þ¤º¤Ï¤³¤Î¥Ú¡¼¥¸¤ò¤´Í÷¤¯¤À¤µ¤¤¡£ FreeBSD ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ë¤Ï¡¢CD-ROM, DVD¡¢USB ¥¹¥Æ¥£¥Ã¥¯¡¢
- ¤½¤·¤Æ¡¢anonymous FTP, HTTP, NFS
- ·Ðͳ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤È¿ô¿¤¯¤Î¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£
-
-
-
- FreeBSD ¤ÎÁ´ÇÛÉÛʪ¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ëÁ°¤Ë¡¢&os; 9.X/10.X
- ¥¤¥ó¥¹¥È¡¼¥ë¥¬¥¤¥É ¤Þ¤¿¤Ï &os; 8.X
- ¥¤¥ó¥¹¥È¡¼¥ë¥¬¥¤¥É ¤ò¡¢
- ¥¤¥ó¥¹¥È¡¼¥ë¥Ð¡¼¥¸¥ç¥ó¤Ë¹ç¤ï¤»¤ÆÄÌÆɤ·¤Æ¤¯¤À¤µ¤¤¡£ ºÇ¶á¤Î PC ¤Ï¡¢Intel® ¥Ö¥é¥ó¥É¤Î¥×¥í¥»¥Ã¥µ¤ò´Þ¤á¡¢
+ amd64 ¥¢¡¼¥¥Æ¥¯¥Á¥ã¤ò»È¤Ã¤Æ¤¤¤Þ¤¹¡£
+ 3 GB °Ê¾å¤Î¥á¥â¥ê¤òÅëºÜ¤·¤Æ¤¤¤ë¥³¥ó¥Ô¥å¡¼¥¿¤Ç¤Ï¡¢
+ amd64 ¤ò»ÈÍѤ¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
+ ¥³¥ó¥Ô¥å¡¼¥¿¤¬¸Å¤¯¡¢32 ¥Ó¥Ã¥È¤Î¥â¥Ç¥ë¤Ç¤¢¤ì¤Ð¡¢i386 ¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£
+ ÁȤ߹þ¤ß¥Ç¥Ð¥¤¥¹¤ä¡¢Raspberry Pi, Beagle, Bone Black, Panda Board,
+ ¤½¤·¤Æ Zed Board ¤È¤¤¤Ã¤¿¥·¥ó¥°¥ë¥Ü¡¼¥É¥³¥ó¥Ô¥å¡¼¥¿ (SBC) ¤Ç¤Ï¡¢
+ armv6 SD ¥«¡¼¥É¥¤¥á¡¼¥¸¤ò»ÈÍѤ·¤Æ¤¯¤À¤µ¤¤¡£ &os; ¤Î¥¤¥ó¥¹¥È¡¼¥é¤Ï¡¢°ìÈÌŪ¤Ê ¥ß¥Ë USB ¥á¥â¥ê¥¹¥Æ¥£¥Ã¥¯¤Î¤Û¤«¤Ë¡¢
+ CD (disc1), DVD (dvd1), ¥Í¥Ã¥È¥ï¡¼¥¯¥¤¥ó¥¹¥È¡¼¥ë (bootonly) ¥µ¥¤¥º¤Î ISO
+ ¥Ç¥£¥¹¥¯¥¤¥á¡¼¥¸¤È¤¤¤Ã¤¿¡¢¤µ¤Þ¤¶¤Þ¤Ê·Á¼°¤Ç¥À¥¦¥ó¥í¡¼¥É¤Ç¤¤Þ¤¹¡£
+ ºÇ¶á¤Î &os; ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ç¤Ï¥Ó¥ë¥ÉºÑ¤ß¤Î²¾ÁÛ¥Þ¥·¥ó¥¤¥á¡¼¥¸¡¢
+ ÁȤ߹þ¤ß¥×¥é¥Ã¥È¥Õ¥©¡¼¥àÍÑ¤Ë¤Ï SD
+ ¥«¡¼¥É¤Î¥¤¥á¡¼¥¸¤âÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ FreeBSD ¤ò FTP ¤ä HTTP ·Ðͳ¤ÇÆþ¼ê¤·¤è¤¦¤È¹Í¤¨¤Æ¤¤¤ë¤Î¤Ê¤é¡¢
- ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î ¥ß¥é¡¼¥µ¥¤¥È
- °ìÍ÷¤«¤é¥Í¥Ã¥È¥ï¡¼¥¯Åª¤Ë¤è¤ê¶á¤¤¥µ¥¤¥È¤òõ¤·¤Æ¤¯¤À¤µ¤¤¡£ Ãí°Õ: ¤É¤Î¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤ä¥¢¡¼¥¥Æ¥¯¥Á¥ã¤òÁª¤Ù¤Ð¤è¤¤¤«¤ï¤«¤é¤Ê¤±¤ì¤Ð¡¢
- ¤ª¤½¤é¤¯¡¢¸Å¤¤¥³¥ó¥Ô¥å¡¼¥¿¤Ç¤¢¤ì¤Ð i386¡¢
- ºÇ¶á¤Î¥³¥ó¥Ô¥å¡¼¥¿¤Ç¤¢¤ì¤Ð amd64 ¤òÁª¤Ö¤È¤è¤¤¤Ç¤·¤ç¤¦¡£ ¤â¤·½ã¿è¤Ë¼Â¸³Åª¤Ê FreeBSD-CURRENT (&rel.head;-CURRENT)
+
+
+ ¤â¤·½ã¿è¤Ë¼Â¸³Åª¤Ê &os;-CURRENT (&rel.head;-CURRENT)
(¤³¤ì¤Ï³«È¯¼Ô¤È²Ì´º¤ËºÇÀèü¤òÄɤ¦¥Æ¥¹¥¿¡¼ÀìÍѤǤ¹) ¤Î snapshot
¥ê¥ê¡¼¥¹¤Ë¶½Ì£¤¬¤¢¤ë¤Î¤Ê¤é¤Ð¡¢&os; ¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È¥ê¥ê¡¼¥¹
@@ -238,14 +177,65 @@
²áµî¡¢¸½ºß¡¢¤½¤·¤Æ¾Íè¤Î¥ê¥ê¡¼¥¹Á´È̤ˤĤ¤¤Æ¤Î¤è¤ê¾Ü¤·¤¤¾ðÊó¤¬Íߤ·¤¤»þ¤Ï¡¢¥ê¥ê¡¼¥¹¾ðÊó¤Î¥Ú¡¼¥¸ ¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£ HTTP ¤â¤·¤¯¤Ï FTP ·Ðͳ¤Ç &os; ¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ëºÝ¤Ë¤Ï¡¢
+ ¥Ï¥ó¥É¥Ö¥Ã¥¯¤Î ¥ß¥é¡¼¥µ¥¤¥È ¤Î°ìÍ÷¤ò¸«¤Æ¡¢
+ ¤¢¤Ê¤¿¤ÎÃÏ°è¤Ë¶á¤¤¥µ¥¤¥È¤òõ¤·¤Æ¤¯¤À¤µ¤¤¡£ &os; ¤Î¥¤¥ó¥¹¥È¡¼¥ë¤Ë¤Ï¡¢CD-ROM, DVD¡¢USB ¥á¥â¥ê¥¹¥Æ¥£¥Ã¥¯¡¢
+ ¤½¤·¤Æ¡¢anonymous FTP, HTTP, NFS
+ ¤òľÀܻȤä¿¥¤¥ó¥¹¥È¡¼¥ë¤Ê¤É¿ô¿¤¯¤ÎÊýË¡¤¬ÍÑ°Õ¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
+ &os; ¤ÎÁ´ÇÛÉÛʪ¤ò¥À¥¦¥ó¥í¡¼¥É¤¹¤ëÁ°¤Ë¡¢
+ ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¥Ð¡¼¥¸¥ç¥ó¤Ë¹ç¤ï¤»¤Æ &os; 9.X/10.X
+ ¥¤¥ó¥¹¥È¡¼¥ë¥¬¥¤¥É ¤Þ¤¿¤Ï &os; 8.X
+ ¥¤¥ó¥¹¥È¡¼¥ë¥¬¥¤¥É ¤òÄÌÆɤ·¤Æ¤¯¤À¤µ¤¤¡£ FreeBSD ¤Î CD-ROM ¤ä DVD ¤Ï¡¢&os; ¤Î CD-ROM ¤ä DVD ¤Ï¡¢FreeBSD Mall ¤â¤·¤¯¤Ï CD-ROM
¤ª¤è¤Ó DVD ¤Î½ÐÈÇ¼Ò ¤«¤é¹ØÆþ¤Ç¤¤Þ¤¹¡£ FreeBSD ¤Ï¡¢
+ &os; ¤Ï¡¢
¾¦ÍѤ䥪¡¼¥×¥ó¥½¡¼¥¹¤Î¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ù¡¼¥¹¤È¤·¤Æ¡¢
Éý¹¤¯ÍøÍѤµ¤ì¤Æ¤¤¤Þ¤¹¡£
- ¹¤¯ÉáµÚ¤·¤Æ¤¤¤Æ¡¢ÆÃ¤Ë FreeBSD
+ ¹¤¯ÉáµÚ¤·¤Æ¤¤¤Æ¡¢ÆÃ¤Ë &os;
¥æ¡¼¥¶¤Î¤ß¤Ê¤µ¤ó¤¬¶½Ì£¤ò»ý¤Á¤½¤¦¤Ê¥×¥í¥¸¥§¥¯¥È¤ò°Ê²¼¤Ç¾Ò²ð¤·¤Þ¤¹¡£ FreeNAS ¤Ï¡¢FreeBSD
+ FreeNAS ¤Ï¡¢&os;
¥Ù¡¼¥¹¤Î¥ª¡¼¥×¥ó¥½¡¼¥¹¤Î¥¹¥È¥ì¡¼¥¸¥×¥é¥Ã¥È¥Õ¥©¡¼¥à¤Ç¤¹¡£
Windows, Apple, UNIX-like ¥·¥¹¥Æ¥à¤«¤é¤Î¶¦Í¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£ PC-BSD ¤Ï¡¢FreeBSD
+ PC-BSD ¤Ï¡¢&os;
¤ò¤â¤È¤Ë¥°¥é¥Õ¥£¥«¥ë¤Ê¥¤¥ó¥¹¥È¡¼¥é¤ÈÈþ¤·¤¤¥Ç¥£¥¹¥¯¥È¥Ã¥×¥Ä¡¼¥ë¤ò²Ã¤¨¡¢
¥«¥¸¥å¥¢¥ë¤Ê¥³¥ó¥Ô¥å¡¼¥¿¥æ¡¼¥¶¤Ç¤â´Êñ¤Ë»È¤¨¤ë¤³¤È¤òÌܻؤ·¤Æ¤¤¤Þ¤¹¡£ pfSense ¤Ï¡¢
¥Õ¥¡¥¤¥¢¥¦¥©¡¼¥ë¤ä¥ë¡¼¥¿¤È¤·¤Æ¤Î»ÈÍѤ˥«¥¹¥¿¥Þ¥¤¥º¤µ¤ì¤¿¡¢
- ¥Õ¥ê¡¼¤Ê¥ª¡¼¥×¥ó¥½¡¼¥¹¤Î FreeBSD ¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó¤Ç¤¹¡£ FreeBSD Ports Collection ¤Ï¡¢FreeBSD ¤ËÍÑ°Õ¤µ¤ì¤¿¡¢
+ &os; Ports Collection ¤Ï¡¢&os; ¤ËÍÑ°Õ¤µ¤ì¤¿¡¢
¤µ¤Þ¤¶¤Þ¤Ê¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤È¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¥½¥Õ¥È¥¦¥§¥¢¤Î¤³¤È¤Ç¤¹¡£ Google Cloud is a cloud computing platform that allows users to
+ run hosted services and servers in a cloud maintained by
+ Google. The goal of this project is to provide an easy way to
+ create and manage &os; installations running on Google
+ Cloud. The good news: FreeBSD 10.1 runs fine. You can create an image and start it
+ up and login via standard ssh, via the gcloud command
+ or via the web console (ssh in a web browser window). More
+ details on how to do all this can be found in the links.
+ Basically, you should be able to gcutil addimage
+ freebsd-101-release-amd64-20150101032704
+ gs://swills-test-bucket/FreeBSD-10.1-RELEASE-amd64-20150101032704.tar.gz Then spin up an image using gcloud compute instances
+ create --zone us-central1-b --image
+ freebsd-101-release-amd64-20150101032704 --boot-disk-size 20GB
+ gtest1 These commands are part of the google-cloud-sdk port, which
+ contains all the commands to interact with Google Cloud. There
+ is also a google-daemon port which is used in running instances to
+ create users and set them up and a google-startup-scripts port which
+ handles running startup/shutdown scripts as specified in node
+ metadata. Additionally, the firstboot-growfs port has been brought back so
+ that new instances will grow their root filesystem. (Thanks to Colin
+ Percival for having created that port initially.) There is also a firstboot-freebsd-update port which can be used
+ to update a system on first boot but is currently disabled. See
+ below. Similarly, the firstboot-pkgs port/scripts will install
+ specified packages on first boot. Overall, Google Cloud Compute is quite nice; instances spin up
+ in about 60 seconds and it is very reasonably priced with
+ automatic discounts for longer term usage. There is a $300 credit
+ for first time users that also makes it free to try out. That
+ credit covers quite a lot of time, and the instances are pretty
+ fast, as well, even the ones without SSDs. The bad news: Google does not make sharing non-official images as easy as
+ AWS, so you have to create your own using my public tar file. The
+ tar was created using the script in the links section. That
+ script can be used to produce customized images, even though there
+ are no official image (nor will there be any time soon). There are some issues running FreeBSD on Google Cloud,
+ listed in the tasks section. The 8 and 16 cpu instances seem to reboot randomly. Repeated UFS panics that Google folks have reported, but
+ I do not think those are particular to Google Cloud. The panic
+ message is "ffs_valloc dup alloc". Running freebsd-update causes the system to become
+ unbootable, so updates do not work. (Reboots work fine
+ otherwise.) There is no gcimagebundle command in the Ports
+ Collectiong so you cannot easily create an image from a running
+ machine. There are a few minor issue with the startup script
+ that is supposed to regenerate ssh keys (for when you
+ create an image from an existing system). 10.1 works, but 10.0 does not boot; other versions remain
+ untested. The kern.vm_guest sysctl node does not detect that it is in a
+ guest. The vtnet driver needs wq disabled on 16 cpu boxes, but
+ is just disabled everywhere for now since that is easier. There is a work needed for the Google
+ safe_format_and_mount command which formats and
+ mounts newly attached disks, but this is just a nicety really. I need to look into irq affinity for vtnet. We need to support virtualized clocks; bryanv@ is
+ working on this. In fact, all his ongoing work in the virt area
+ would probably make things work better. It would be nice if there as the ability to disable the
+ spinner before the loader, which clutters up the console log. The
+ ability to disable it is in HEAD; hopefully it will be MFCd to
+ 10-STABLE before 10.2. There were several improvements made to the FreeBSD process
+ There were several improvements made to &os;'s process
management last quarter. The Reaper facility was added, allowing a process to reliably
track the running and exiting state of the whole subtree of
- the processes. It is intended to improve tools like
- timeout(1) or poudriere, by making it impossible for the
+ its processes. It is intended to improve tools like
+ timeout(1) or poudriere, by making it impossible for a
runaway grandchild to escape the controlling process. The
feature was designed based on similar facilities in
DragonFlyBSD and Linux, with some references to Solaris
@@ -192,8 +191,8 @@
thread to put some processes into stopped state. Also, a
facility to sync filesystems before suspend was added, to
ensure that consistent metadata and as much as possible of the
- cached user data are on stable storage, to minimize damage of
- failed resume. The code stressed some parts of the system and has led to
discovery of a number of bugs in different areas, including
@@ -204,7 +203,7 @@
During the work described above, it was noted that process
spinlock duties are significantly overloaded (the same is true
for the process lock). The spinlock was split into
- per-feature locks in r275121. As result, it was also possible
+ per-feature locks in r275121. As a result, it was also possible
to eliminate recursion on it in r275372. Most system features work, including keyboard, WiFi, sound,
- VESA graphics, touchpad, USB and decent battery life (5 to 6
- hours). The Acer C720 Chromebook is a powerful but inexpensive laptop
+ designed to run Google's Chrome OS. This project aims to
+ bring &os; to the C720, providing an easy way for people to
+ experience &os; on hardware which is widely available and
+ inexpensive. As of this update, most system features work, including the
+ keyboard, WiFi, sound, VESA graphics, touchpad, and USB. The battery
+ life is a reasonable 5 to 6 hours (compare to the published 8.5 hour
+ lifetime for Chrome OS. Package FreeBSD base. Package the &os; base system. mandoc(1) has been made the default manual page
- formatter on HEAD -- man(1) will use mandoc(1) to
+ formatter on HEAD — man(1) will use mandoc(1) to
format manual pages by default, then fall back to
groff(1) if it fails. The documentation team has spent a lot of time fixing issues
- reported by mdoc(7) in the FreeBSD manual pages.
+ reported by mandoc(1) in the FreeBSD manual pages.
This greatly improves the quality of our manual pages. Most manual pages with remaining issues are from contrib/,
@@ -463,7 +469,7 @@
The main goal of the external toolchain project is to be able
- to build world and kernel with non-default toolchain. It can
+ to build world and kernel with a non-default toolchain. It can
be helpful to:
As a result of this effort, it has been possible to
+ As a result of this effort, it is possible to
successfully build and run a kernel and world built with GCC
- 4.9.1 and binutils 2.24 on sparc64, amd64 (with minor tweaks
- for amd64), powerpc and powerpc64. Patch and upstream GCC 4.9 to support &os; mips, arm and
- aarch64. Patch GCC 4.9 to support &os; mips, arm and aarch64 and
+ submit the patches to upstream. We moved our development repo to GitHub. The repo is
structured as follows: the master branch is vanilla
- &os; Ports, and we have theme branches for topics
- such as the porting of MATE 1.9 (mate-1.10 branch) and GNOME
- 3.15 (gnome-3.16 branch). The GNOME 3.14 branch (gnome-3.14)
+ &os; Ports, and we have theme branches for topics
+ such as the porting of MATE 1.9 (the mate-1.10 branch) and GNOME
+ 3.15 (the gnome-3.16 branch). The GNOME 3.14 branch (gnome-3.14)
is not used or updated any more because the content has been
committed to ports, but is kept around for the history. MATE 1.10 porting is under way, the latest 1.9 releases are
+ MATE 1.10 porting is under way; the latest 1.9 releases are
available in the mate-1.10 branch. In order to ensure that 10.1-RELEASE shipped with support for
- up-to-date X Windows and KDE4, core approved the switch to
+ up-to-date X Window Systems and KDE4, core approved the switch to
'new Xorg' as the default in time for building the packages
for that release. Find workaround when acpi_video(4) is not
+ Find a workaround for when acpi_video(4) is not
functional (panel crashes); OpenBSD seems to have same
problem. The project adds support for AES-GCM and AES-CTR mode to the
+ The project adds support for AES-GCM and AES-CTR modes to the
OpenCrypto framework. Both software and AES-NI accelerated
versions are functional, working and committed. Ermal Luçi
(eri@) is working on adding support for the additional modes
@@ -1188,7 +1194,7 @@
We migrated our Ports development tree to Git and GitHub.
Tracking changes in the official Ports tree and preparing
- patches is way easier. Furthermore, we can accept pull
+ patches is much easier. Furthermore, we can accept pull
requests. All of the reasons behind this change are detailed
on the blog and the workflow is described on the wiki. Improve backends (netback, blkback) performance. Improve the performance of the netback and blkback
+ backends. In the near future, more components from llvm.org will be
updated in base, with libc++ and libcompiler-rt most likely
- being the first. Thanks to Ed Maste, Roman Divacky, Andrew Turner, Justin
Hibbits, and Antoine Brodin for their invaluable help with
@@ -1576,7 +1583,7 @@
&os; but has moved to a standalone project to encourage wider
participation from others in the open-source developer
community. &os;'s libelf and libdwarf are now imported from
- upstream source in contrib/elftoolchain. ELF Tool Chain provides a set of tools equivalent to the
GNU Binutils suite. This project's goal is to import these
@@ -1605,7 +1612,7 @@
ELF Tool Chain's readelf will be enabled as well once some
missing functionality in ELF note parsing is added. ELF Tool
- Chain's elfcopy provides equivalent functionality to Binutils
+ Chain's elfcopy provides equivalent functionality to Binutils'
objcopy, and accepts the same command-line arguments. For it
to be a viable replacement for all uses of objcopy in the base
system, it must gain support for writing portable exectuable
@@ -1703,7 +1710,7 @@
October 2014. This has also been merged to 10-STABLE and will
be included in the 10.2 release. A bhyve status update presentation was done at the FreeBSD
+ A bhyve status update presentation was given at the FreeBSD
Vendor Summit in Nov 2014. The slides are available at
The main goal of the lemul project is the execution of
- multithreaded Linux applications that requires the glibc
- library version 2.20 or later to be available on &os;. Glibc
+ The main goal of the Linux emulation layer project
+ is the execution on &os; of
+ multithreaded Linux applications that require the glibc
+ library version 2.20 or later to be available. Glibc
2.20 requires a Linux kernel (or emulation thereof) of version
2.6.32 or later. The main obstacle preventing this is that
the current Linuxulator uses native &os; processes for
@@ -1976,7 +1984,7 @@
Implement the Priority Inheritance Futexes for
+ Implement Priority Inheritance Futexes for
the Linuxulator. The ports collection's Linux emulation stack was upgraded to
+ The Linux emulation stack in the ports collection was upgraded to
include CentOS 6.6 on November 11. After smoothing
- out several bugs that had been introduced, we have been able
+ out several bugs that had been introduced, we were able
to bump the default version of the Linux userland from Fedora
- 10 to CentOS 6.6 on December 9. Providing a more
- modern Linux userland and supporting libraries allows a large
+ 10 to CentOS 6.6 on December 9th. Providing a more
+ modern Linux userland and support libraries allows a large
number of Linux applications to be run on &os;. The goal behind providing an updated Fedora-based userland is
@@ -2173,7 +2181,7 @@
Refactor Mk/bsd.linux-*.mk to facilitate above
+ Refactor Mk/bsd.linux-*.mk to facilitate the above
additions. The most obvious use case for SR-IOV is virtualization. A
hypervisor like bhyve could instantiate a VF for every VM and
use PCI passthrough to assign the VFs to the VMs. This would
allow multiple VMs to share access to the PCI device without
having to do any expensive communication with the hypervisor,
- greatly increasing performance of performing I/O from a
+ greatly increasing the performance of I/O within a
VM. Work on the core PCI infrastructure is complete and
@@ -2274,7 +2282,7 @@
shim
Ensure the signature format properly matches UEFI spec
+ Ensure that the signature format properly matches UEFI spec
requirements. Verify correctly signed, incorrectly signed, and
+ Verify that correctly signed, incorrectly signed, and
unsigned loader components are handled properly. Further improvements have been made to the loader to allow it
to take the Flattened Device Tree data from UEFI and pass it
- to the kernel. In the kernel busdma, CPU identification, and
+ to the kernel. In the kernel, busdma, CPU identification, and
improvements to interrupt handling have been made, along with
preliminary KDB support. Implement remaining userland libraries and binaries. Implement the remaining userland libraries and binaries. We ended the year exceeding our fundraising goal, by raising
over $2,372,132, from 1670 donors! Thank you to everyone who
@@ -2503,7 +2511,7 @@
We were a sponsor of the
Grace Hopper
Conference.
- Dru Lavigne gave an introduction to &os; presentation, that
+ Dru Lavigne gave an "introduction to &os;" presentation, that
was well attended. We also sponsored Shteryana Shopova to
represent &os;, along with Dru, at our booth. Besides the above conferences, we helped promote &os; at
+ In addition to the above conferences, we helped promote &os; at
the following conferences:
We visited a few large &os; users in the Bay Area to
@@ -2592,8 +2601,8 @@
report. Some projects that were worked on this quarter were
adding support for 64-bit ARM architecture to &os;,
integration work on the vt(4) updated console and UEFI boot
- support, Secure Boot, refining in-kernel iSCSI target and
- initiator stack, autofs-based automount daemon, migrating to
+ support, Secure Boot, refining the in-kernel iSCSI target and
+ initiator stack, an autofs-based automount daemon, migrating to
the ELF Tool Chain, and implementing modern AES modes in
&os;'s cryptographic framework. There is also a firstboot-freebsd-update port which can be used
- to update a system on first boot but is currently disabled. See
- below. Similarly, the firstboot-pkgs port/scripts will install
+ to update a system on first boot but is currently disabled (see
+ below). Similarly, the firstboot-pkgs port/scripts will install
specified packages on first boot. Overall, Google Cloud Compute is quite nice; instances spin up
@@ -2675,7 +2684,7 @@
Google does not make sharing non-official images as easy as
AWS, so you have to create your own using my public tar file. The
- tar was created using the script in the links section. That
+ tar file was created using the script in the links section. That
script can be used to produce customized images, even though there
are no official image (nor will there be any time soon). There is no gcimagebundle command in the Ports
- Collectiong so you cannot easily create an image from a running
+ Collection so you cannot easily create an image from a running
machine. The vtnet driver needs wq disabled on 16 cpu boxes, but
+ The vtnet driver needs wq disabled on 16 cpu boxes, but it
is just disabled everywhere for now since that is easier. We need to support virtualized clocks; bryanv@ is
- working on this. In fact, all his ongoing work in the virt area
- would probably make things work better. It would be nice if there as the ability to disable the
+ It would be nice if there was the ability to disable the
spinner before the loader, which clutters up the console log. The
ability to disable it is in HEAD; hopefully it will be MFCd to
10-STABLE before 10.2. This report covers &os;-related projects between October and
December 2014. This is the last of four reports planned for
Modified: head/en_US.ISO8859-1/htdocs/news/status/status.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/status.xml Thu Jan 15 21:17:55 2015 (r46208)
+++ head/en_US.ISO8859-1/htdocs/news/status/status.xml Thu Jan 15 21:38:13 2015 (r46209)
@@ -13,8 +13,8 @@
Use the xml
generator or download and edit the
@@ -58,6 +58,8 @@
The October–December, 2014 Status Report
+ is now available. A brief introduction to FreeBSD for curious Linux users.
+ Covers the installation and updating process, building a
+ basic firewall, installing binary packages, and finally
+ installing and configuring a typical web stack with Apache,
+ PHP, and MySQL. 2014 ǯ
+ 10 ·î – 12 ·î³«È¯¿ÊĽ¥ì¥Ý¡¼¥È
+ ¤¬¸ø³«¤µ¤ì¤Þ¤·¤¿¡£Release
- Information
+
- Choosing an Architecture
-
-
- Install FreeBSD
-
- Choosing an Image
+
+ Download FreeBSD
+
- &os; &rel.current;-RELEASE
-
-
-
+
-
-
+ Version & Platform
- Distribution
- ISO
- Release
-
NotesHardware
-
NotesInstallation
-
NotesErrata
-
-
-
-
- FreeBSD &rel.current;-RELEASE
-
- [View]
- [View]
- [View]
- [View]
-
-
-
- amd64
-
(x86-64, x64)[Distribution]
- [ISO]
-
- [VM Images]
-
-
- arm
-
- [SD Card Image]
-
-
-
- i386
- [Distribution]
- [ISO]
-
- [VM Images]
-
-
- ia64
- [Distribution]
- [ISO]
-
-
-
- powerpc
- [Distribution]
- [ISO]
-
-
-
- powerpc64
- [Distribution]
- [ISO]
-
-
-
- sparc64
- [Distribution]
- [ISO]
-
-
- FreeBSD &rel2.current;-RELEASE
-
- [View]
- [View]
- [View]
- [View]
-
-
-
- amd64
-
(x86-64, x64)[Distribution]
- [ISO]
-
-
-
- i386
- [Distribution]
- [ISO]
-
-
-
- ia64
- [Distribution]
- [ISO]
-
-
-
- powerpc
- [Distribution]
- [ISO]
-
-
-
- powerpc64
- [Distribution]
- [ISO]
-
-
-
- sparc64
- [Distribution]
- [ISO]
-
-
- FreeBSD &rel3.current;-RELEASE
-
- [View]
- [View]
- [View]
- [View]
-
-
-
- amd64
-
(x86-64, x64)[Distribution]
- [ISO]
-
-
-
- i386
- [Distribution]
- [ISO]
-
-
-
- pc98
- [Distribution]
- [ISO]
-
&beta.desc;
+
+
+ Development Snapshots
+
&os; &rel.head;-CURRENT
+
+
+
+
+
+
+
+ Installer Images
+ Virtual Machine Images
+
+
+
+
+
+
+
+
+
+ Install &os;
+
+ Purchase &os; Media
- Past Releases
FreeBSD-derived Operating System Distributions
- &os;-derived Operating System Distributions
+
+
+
@@ -281,11 +273,11 @@
The Ports Collection
-
-
-
-
-
-
- Version & Platform
- Distribution
- ISO
-
-
-
- FreeBSD &betarel2.current;-&betarel2.vers;
-
-
- [View]
-
-
-
- amd64
-
(x86-64, x64)[Distribution]
- [ISO]
-
-
-
- i386
- [Distribution]
- [ISO]
-
-
-
- ia64
- [Distribution]
- [ISO]
-
-
-
- powerpc
- [Distribution]
- [ISO]
-
-
-
- powerpc64
- [Distribution]
- [ISO]
-
-
-
-
- sparc64
- [Distribution]
- [ISO]
- &os; &betarel2.current;-&betarel2.vers;
+
+
+
+
+
+
+ Installer Images
+ Virtual Machine Images
+ Documentation
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
+ Version & Platform
- Distribution
- ISO
- TODO List
- &os; &betarel.current;-&betarel.vers;
+
+
+
-
- FreeBSD &betarel.current;-&betarel.vers;
-
- [View]
-
-
-
- amd64
-
(x86-64, x64)[Distribution]
- [ISO]
-
- [VM Images]
-
-
- arm
- [Distribution]
- [SD Card Image]
-
-
-
- i386
- [Distribution]
- [ISO]
-
- [VM Images]
-
-
-
- ia64
- [Distribution]
- [ISO]
-
-
-
- powerpc
- [Distribution]
- [ISO]
-
-
-
- powerpc64
- [Distribution]
- [ISO]
-
-
+
- sparc64
- [Distribution]
- [ISO]
+ Installer Images
+ Virtual Machine Images
+ Documentation
+
+
+
+
+
+
+
+
+
+
+
&beta.second;
From owner-svn-doc-head@FreeBSD.ORG Mon Jan 12 21:26:37 2015
Return-Path:
From owner-svn-doc-head@FreeBSD.ORG Mon Jan 12 23:08:47 2015
Return-Path:
@@ -478,7 +478,7 @@
-
@@ -862,7 +862,7 @@
-
@@ -480,7 +480,7 @@
-
-
@@ -1115,12 +1114,12 @@
-
-
-
-
-
-
-
-
@@ -993,22 +1053,28 @@
-
-
+
+
+
+
+
+ These flyers are available on the
+ &os;
+ Foundation site
+ for &os; advocates to promote &os; at conferences around
+ the world.
+ We also put ads for the Foundation and &os; in the &os;
+ Journal and USENIX ;login: magazine.
+
+ ¥ê¥ê¡¼¥¹¾ðÊó
+
- ¥¢¡¼¥¥Æ¥¯¥Á¥ã¤ÎÁªÂò
-
-
- FreeBSD ¤Î¥¤¥ó¥¹¥È¡¼¥ë
-
- ¥¤¥á¡¼¥¸¤ÎÁªÂò
+
+ FreeBSD ¤Î¥À¥¦¥ó¥í¡¼¥É
+
- &os; &rel.current;-RELEASE
-
-
-
+
-
-
+ ¥Ð¡¼¥¸¥ç¥ó¤È¥×¥é¥Ã¥È¥Õ¥©¡¼¥à
- ÇÛÉÛ¸µ
- ISO
- ¥ê¥ê¡¼¥¹
-
¥Î¡¼¥È¥Ï¡¼¥É¥¦¥§¥¢
-
¥Î¡¼¥È¥¤¥ó¥¹¥È¡¼¥ë
-
¥¬¥¤¥ÉErrata
-
(Àµ¸íɽ)
-
-
-
- FreeBSD &rel.current;-RELEASE
-
- [View]
- [View]
- [View]
- [View]
-
-
-
- amd64
-
(x86-64, x64)[ÇÛÉÛ¸µ]
- [ISO]
-
- [VM Images]
-
-
- arm
-
- [SD Card Image]
-
-
-
- i386
- [ÇÛÉÛ¸µ]
- [ISO]
-
- [VM Images]
-
-
- ia64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- powerpc
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- powerpc64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- sparc64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
- FreeBSD &rel2.current;-RELEASE
-
- [View]
- [View]
- [View]
- [View]
-
-
-
- amd64
-
(x86-64, x64)[ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- i386
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- ia64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- powerpc
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- powerpc64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- sparc64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
- FreeBSD &rel3.current;-RELEASE
-
- [View]
- [View]
- [View]
- [View]
-
-
-
- amd64
-
(x86-64, x64)[ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- i386
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- pc98
- [ÇÛÉÛ¸µ]
- [ISO]
-
&beta.desc;
- ³«È¯¥¹¥Ê¥Ã¥×¥·¥ç¥Ã¥È
+
+ &os; &rel.head;-CURRENT
+
+
+
+
+
+
+
+ ¥¤¥ó¥¹¥È¡¼¥é¥¤¥á¡¼¥¸
+ ²¾ÁÛ¥Þ¥·¥ó¥¤¥á¡¼¥¸
+
+
+
+
+
+
+
+
+
+ &os; ¤Î¥¤¥ó¥¹¥È¡¼¥ë
+
+ &os; ¥á¥Ç¥£¥¢¤Î¹ØÆþ
- ²áµî¤Î¥ê¥ê¡¼¥¹
FreeBSD ¤ËͳÍ褹¤ë¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó
+ &os; ¤ËͳÍ褹¤ë¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥Ç¥£¥¹¥È¥ê¥Ó¥å¡¼¥·¥ç¥ó
-
-
@@ -282,11 +272,11 @@
+
Ports Collection
-
-
+
-
-
-
-
- ¥Ð¡¼¥¸¥ç¥ó¤È¥×¥é¥Ã¥È¥Õ¥©¡¼¥à
- ÇÛÉÛ¸µ
- ISO
-
-
-
- FreeBSD &betarel2.current;-&betarel2.vers;
-
-
- [View]
-
-
-
- amd64
-
(x86-64, x64)[ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- i386
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- ia64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- powerpc
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- powerpc64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
-
- sparc64
- [ÇÛÉÛ¸µ]
- [ISO]
- &os; &betarel2.current;-&betarel2.vers;
+
+
+
+
+
+
+ ¥¤¥ó¥¹¥È¡¼¥é¥¤¥á¡¼¥¸
+ ²¾ÁÛ¥Þ¥·¥ó¥¤¥á¡¼¥¸
+ ʸ½ñ
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
+ ¥Ð¡¼¥¸¥ç¥ó¤È¥×¥é¥Ã¥È¥Õ¥©¡¼¥à
- ÇÛÉÛ¸µ
- ISO
- TODO ¥ê¥¹¥È
- &os; &betarel.current;-&betarel.vers;
+
+
+
-
- FreeBSD &betarel.current;-&betarel.vers;
-
- [View]
-
-
-
- amd64
-
(x86-64, x64)[ÇÛÉÛ¸µ]
- [ISO]
-
- [VM Images]
-
-
- arm
- [ÇÛÉÛ¸µ]
- [SD Card Image]
-
-
-
- i386
- [ÇÛÉÛ¸µ]
- [ISO]
-
- [VM Images]
-
-
-
- ia64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- powerpc
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
-
- powerpc64
- [ÇÛÉÛ¸µ]
- [ISO]
-
-
+
- sparc64
- [ÇÛÉÛ¸µ]
- [ISO]
+ ¥¤¥ó¥¹¥È¡¼¥é¥¤¥á¡¼¥¸
+ ²¾ÁÛ¥Þ¥·¥ó¥¤¥á¡¼¥¸
+ ʸ½ñ
+
+
+
+
+
+
+
+
+
+
+
&beta.second;
From owner-svn-doc-head@FreeBSD.ORG Thu Jan 15 16:30:15 2015
Return-Path:
-
@@ -2283,12 +2291,12 @@
@@ -2532,8 +2540,9 @@
Fest
+
+ LISA had a great turnout for Dru Lavigne's &os; BoF talk.
Next Quarterly Status Report submissions (October —
- December) due: January 7th, 2015
+ Next Quarterly Status Report submissions (January —
+ March) due: April 7th, 2015
2014
+