From owner-svn-doc-head@FreeBSD.ORG Sun Oct 5 01:33:45 2014
Return-Path: The fisrt RC build for the &os; 10.1 release cycle
+ is now available. ISO images for the amd64, armv6, i386,
+ ia64, powerpc, powerpc64 and sparc64 architectures are available
+ on most of our &os;
+ mirror sites. &os; 10.1 リリースサイクルから
+ 最初のリリース候補版が公開されました (アナウンス)。
+ &os;
+ ミラーサイト から amd64, armv6, i386, ia64, powerpc,
+ powerpc64 および sparc64 アーキテクチャの
+ ISO イメージを入手できます。 やることは簡単です。この
-
- GNATS データベースへのリンクをたどって PR を探して
+
+ Bugzilla データベースへのリンクをたどって PR を探して
どういう作業が必要とされているのか調べ、
それを実際にこなせばよいのです。 もしあなたがコミッターなら、PR をクローズするのに
- edit-pr コマンドが使えます。 もしあなたがコミッターなら、
+ ウェブインタフェースを使って PR をクローズできます。 あなたがコミッターでないなら、次の一文 (注: もちろん英語)
を含むフォローを submit してください。障害報告 (PR) を処理しましょう!
FreeBSD が優れた製品の構築にどのように役立つかについて説明しています。
Argentina.com:
- A Case Study (casestudy-argentina.com) (英語版のみ)
- FreeBSD がどのようにラテンアメリカの大規模 ISP の役に立ったか。
The
Committer's Guide (committers-guide) (英語版のみ)
FreeBSD committers のための入門書です。
This is a draft of the July-September 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 July and + September 2014. This is the third of four reports planned for + 2014.
+ +The third quarter of 2014... was a very busy and productive + time
+ +Thanks to all the reporters for the excellent work! This + report contains 0 entries and we hope you enjoy reading it.
+ +The deadline for submissions covering the period from October + to December 2014 is January 7th, 2015.
+The current designation and estimated lifetimes of the currently - supported branches are given below. The Estimated EoL - (end-of-life) column gives the earliest date on which that - branch is likely to be dropped. Please note that these dates may - be extended into the future, but only extenuating circumstances - would lead to a branch's support being dropped earlier than the - date listed.
+The designation and expected lifetime of all currently supported + branches are given below. The Expected EoL (end-of-life) + column indicates the earliest date on which support for that + branch or release will end. Please note that these dates may be + pushed back if circumstances warrant it.
This is a draft of the July-September 2014 status - report. Please check back after it is finalized, and an + report. Please check back after it is finalized, and an announcement email is sent to the &os;-Announce mailing list.
@@ -206,7 +206,7 @@Lucas is working on a series of small FreeBSD books. The first one, FreeBSD Mastery: Storage Essentials, is underway, and covers GEOM, gpart, MBR, UFS, GELI, GBDE, disk sector - alignment, and more. You can pre-order the book at a discount + alignment, and more. You can pre-order the book at a discount from his web site, or wait for it to hit print and all major ebook retailers.
@@ -250,7 +250,7 @@ on).Still, the Xfce team continues to keep each piece of the Xfce - Desktop up to date. That is why we are working on the next + Desktop up to date. That is why we are working on the next stable release (no date scheduled).
Major changes will be:
@@ -597,16 +597,16 @@This is a Google Summer of code project that aims to provide a noninteractive FreeBSD installation from the network. In the first part, an implementation was added for scripted - bsdinstall(8). It supports variables like: KEYMAP, + bsdinstall(8). It supports variables like: KEYMAP, HOSTNAME, MIRROR, RELEASE, TIMEZONE, DAEMONS, ROOTPWHASH, and USERS. Network configuration, ZFS options, and others are also included.
Second part of project is about booting the fai (Fully Automatic Installer) from network by PXE. Made installer - distro based on mfsbsd. After boot fai looks for + distro based on mfsbsd. After boot fai looks for "bootfile-name" parameter from DHCP server which tell fai - where bsdinstall script located is. Fai supports mac-based + where bsdinstall script located is. Fai supports mac-based config or default, if mac-based file does not exist.
@@ -616,9 +616,9 @@GNOME is a desktop environment and graphical user interface - that runs on top of a computer operating system. GNOME is part - of the GNU Project and can be used with various Unix-like + that runs on top of a computer operating system. GNOME is + part of the GNU Project and can be used with various Unix-like operating systems, including FreeBSD.
The MATE ports were updated to the 1.8 versions.
@@ -707,7 +707,7 @@Hardware context support was added to the i915 driver in both HEAD and 10.1-RELEASE. This will allow us to update libglapi, libGL, dri, libEGL and libglesv2 ports to a newer version of - Mesa. The latest version is already available from our + Mesa. The latest version is already available from our development ports tree (see the links section).
Cairo was updated to 1.12. This will allow the FreeBSD GNOME @@ -772,7 +772,7 @@
Furthermore, a new website and forum is being worked at, replacing the old-fashioned website that offers only limited - functionality. The new website will be linked to the server + functionality. The new website will be linked to the server database, providing real-time updates about the project.
In addition, a new platform for collaborated development is @@ -803,7 +803,7 @@ awry.
A longer version of the 2014 development progress of the - ZFSguru project and information specific to the newly-released + ZFSguru project and information specific to the newly-released 10.1-002 system image can be found in the Links section.
From owner-svn-doc-head@FreeBSD.ORG Tue Oct 7 22:34:57 2014 Return-Path:Deficiencies in the current automounter, amd(8), are a - recurring problem reported by many FreeBSD users. A new + recurring problem reported by many &os; users. A new automounter is being developed to address these concerns.
The automounter is a cleanroom implementation of
@@ -123,7 +123,7 @@
Building on the new in-kernel iSCSI target and initiator stack - released in FreeBSD 10.0, Chelsio Communications has begun + released in &os; 10.0, Chelsio Communications has begun developing an offload interface to take advantage of the hardware offload capabilities of Chelsio T4 and T5 10 and 40 gigabit Ethernet adapters.
@@ -167,7 +167,7 @@ system administrator to configure this feature. The project is entering a testing phase. The code will be released under the BSD license and is expected to be completed later in the - year and ship in FreeBSD 10.2-RELEASE. + year and ship in &os; 10.2-RELEASE.Complete testing
Lucas is working on a series of small FreeBSD books. The +
Lucas is working on a series of small &os; books. The
first one, FreeBSD Mastery: Storage Essentials, is underway,
and covers GEOM, gpart, MBR, UFS, GELI, GBDE, disk sector
alignment, and more. You can pre-order the book at a discount
@@ -216,7 +216,7 @@
Lucas needs to write faster. Xfce is a free software desktop environment for Unix and
- Unix-like platforms including FreeBSD. It aims to be fast and
+ Unix-like platforms including &os;. It aims to be fast and
lightweight while still being visually appealing and easy to
use. ZFS is one of the premier features of FreeBSD and the quality
+ ZFS is one of the premier features of &os; and the quality
of the documentation should match that of other important
features. Much of the original documentation from Sun and
Oracle has disappeared, moved, or is about the proprietary
version of ZFS. The OpenZFS project does not provide much
documentation and instead provides users with a few links,
- including the FreeBSD Handbook. New users have many questions
+ including the &os; Handbook. New users have many questions
about ZFS and yet there exists a great deal more bad advice
about ZFS than proper documentation. After over a year of work, a new ZFS chapter has been added
- to the FreeBSD Handbook. Over 20,000 words describing the
+ to the &os; Handbook. Over 20,000 words describing the
basics of creating, managing and maintaining a ZFS pool, as
well as using some of the advanced features like compression,
deduplication, and delegation. The chapter also contains a
@@ -387,18 +387,18 @@
Technical review by Matt Ahrens (co-creator of ZFS) Improve delegation section Improve tuning section, add recently added sysctls Add section on jails and the jailed property Add FAQ section Add Use Cases section General editing and review In May, &a.rodrigc; led a working group Continuous
- Integration and Testing with Jenkins for FreeBSD at the
- FreeBSD Devsummit in Ottawa. &a.rodrigc; also gave a Jenkins
+ Integration and Testing with Jenkins for &os; at the
+ &os; Devsummit in Ottawa. &a.rodrigc; also gave a Jenkins
presentation at BSDCan. At BSDCan, &a.rodrigc; had some discussions with &a.jmmv;
@@ -488,7 +488,7 @@
eliminate some test failures. One of the tests still results
in a crash in byacc. This is being tracked in PR 193499.
Thomas E. Dickey (byacc maintainer) submitted a patch to fix
- the problem, and this has been committed to FreeBSD. &a.rodrigc; analyzed the cause of some startup errors in
Jenkins when opening a multicast socket. He had some
@@ -497,7 +497,7 @@
open an IPv4 multicast socket, but with an IPv4 multicast
address mapped to an IPv6 address. On Linux, there are
modifications to the JDK itself to work around this. &a.bms;
- said that the work to make the FreeBSD IPv6 stack behave like
+ said that the work to make the &os; IPv6 stack behave like
Solaris would require some work. &a.rodrigc; started writing a Kyua Quickstart Guide. This
@@ -508,28 +508,28 @@
Upstream more fixes to Jenkins for &os;, such as JNA fixes. Automate the build of /usr/tests. Set up more builds based on examples from the existing &os;
+ Tinderbox. Get feedback for improving the Kyua Quickstart Guide. We need more people to join us on freebsd-testing@FreeBSD.org
and help out. We especially need people with devops and
scripting experience to help us set up more builds and tests.
We would also like to integrate with other parts of the
- project, such as Phabricator.
+ project, such as Phabricator. The LLVM address sanitizer (Asan) has been ported to &os;.
The mainline version of LLVM is known to pass all unit and lit
- Asan tests without unexpected failures on FreeBSD 10.0.
A buildbot running sanitizers tests under FreeBSD stable/10 +
A buildbot running sanitizers tests under &os; stable/10 has been established. See the Links section.
In order to make it possible to run programs with sanitizers - checks enabled on FreeBSD a new kernel state named + checks enabled on &os; a new kernel state named kern.proc_vmmap_skip_resident_count has been added. See the Links section.
Note that running Asan tests on stable/10 requires that state to be set to 1.
-A similar work dedicated to add FreeBSD support to the thread +
A similar work dedicated to add &os; support to the thread sanitizer (Tsan) is in progress.
This is a Google Summer of code project that aims to provide
- a noninteractive FreeBSD installation from the network. In
+ a noninteractive &os; installation from the network. In
the first part, an implementation was added for scripted
bsdinstall(8). It supports variables like: KEYMAP,
HOSTNAME, MIRROR, RELEASE, TIMEZONE, DAEMONS, ROOTPWHASH, and
@@ -616,20 +616,20 @@
Documentation, including a howto and handbook. The project
needs more tests in different configurations. Support for
- more than one network interface is planned.
+ more than one network interface is planned.
GNOME is a desktop environment and graphical user interface that runs on top of a computer operating system. GNOME is part of the GNU Project and can be used with various Unix-like - operating systems, including FreeBSD.
+ operating systems, including &os;.The MATE ports were updated to the 1.8 versions.
@@ -661,8 +661,8 @@Finish GNOME 3.12 merge, and start tracking GNOME 3.15 + (development series).
The old graphics stack will be removed with the next update to these ports. See the announcement in the Links @@ -710,7 +710,7 @@ Mesa. The latest version is already available from our development ports tree (see the links section).
-Cairo was updated to 1.12. This will allow the FreeBSD GNOME +
Cairo was updated to 1.12. This will allow the &os; GNOME team to upgrade pango and Gtk+ 3. Unfortunately, the update also revealed that xf86-video-intel 2.7.1 was in a much worse state than previously assumed.
@@ -725,7 +725,7 @@See the "Graphics" wiki page for up-to-date information.
The FreeBSD Python team continued to improve the overall - experience with Python-based software on FreeBSD.
+The &os; Python team continued to improve the overall + experience with Python-based software on &os;.
During the last quarter, the bsd.python.mk bits of
the ports infrastructure were converted to the more modern
@@ -852,15 +852,15 @@
Retire the Python 3 specific port duplicates Convert ports to the new USES syntax More tasks can be found on the team's wiki page (see
+ Links). To get involved, interested people can say hello on IRC
+ and let us know their areas of interest!
Technical review by Matt Ahrens (co-creator of ZFS)
Improve delegation section
Improve tuning section, add recently added sysctls
Add section on jails and the jailed property
Add FAQ section
Add Use Cases section
General editing and review
Technical review by Matt Ahrens (co-creator of + ZFS)
+Improve delegation section
+Improve tuning section, add recently added sysctls
+Add section on jails and the jailed property
+Add FAQ section
+Add Use Cases section
+General editing and review
+Upstream more fixes to Jenkins for &os;, such as JNA fixes.
+Upstream more fixes to Jenkins for &os;, such as JNA + fixes.
Set up more builds based on examples from the existing &os; - Tinderbox.
+ Tinderbox.We need more people to join us on freebsd-testing@FreeBSD.org - and help out. We especially need people with devops and - scripting experience to help us set up more builds and tests. - We would also like to integrate with other parts of the - project, such as Phabricator.
+We need more people to join us on + freebsd-testing@FreeBSD.org and help out. We especially + need people with devops and scripting experience to help us + set up more builds and tests. We would also like to + integrate with other parts of the project, such as + Phabricator.
Documentation, including a howto and handbook. The project - needs more tests in different configurations. Support for - more than one network interface is planned.
+ needs more tests in different configurations. Support for + more than one network interface is planned.The MATE ports were updated to the 1.8 versions.
Now that cairo was updated to 1.12 the merge of GNOME 3 has - started. Currently we are doing test builds to find ports + started. Currently we are doing test builds to find ports broken by the update and pruning ports that do not build any more because of incompatible updates.
@@ -662,7 +685,7 @@Finish GNOME 3.12 merge, and start tracking GNOME 3.15 - (development series).
+ (development series).See the "Graphics" wiki page for up-to-date information.
+See the "Graphics" wiki page for up-to-date + information.
Retire the Python 3 specific port duplicates
Retire the Python 3 specific port duplicates
+Convert ports to the new USES syntax
Convert ports to the new USES syntax
+More tasks can be found on the team's wiki page (see - Links).
More tasks can be found on the team's wiki page (see + Links).
+To get involved, interested people can say hello on IRC - and let us know their areas of interest!
To get involved, interested people can say hello on IRC + and let us know their areas of interest!
+The project adds support for AES-GCM and AES-CTR mode to the + OpenCrypto framework. Both software and AES-NI accelerated + versions are functional and working. Ermal Lu巽i (eri@) is + working on adding support for the additional modes to + IPsec.
+ + +Create test suite for the most common modes.
+Introduce your work. Do not assume that the person reading the - report knows about your project.
- -Show the importance of your work. Status reports are not just - about telling everyone that things were done, they also need to - explain why they were done.
- -What has happened since the last report? Let us know what is new - in this area.
- - -Introduce your work. Do not assume that the person reading + the report knows about your project.
+ +Show the importance of your work. Status reports are not + just about telling everyone that things were done, they also + need to explain why they were done.
+ +What has happened since the last report? Let us know what is + new in this area.
+ + +Work on initial support of the IFC6410 board,which was + stopped due to bricked bootloader, has been started again. + This board has the Qualcomm Snapdragon S4 SoC, featuring the + Krait CPU. This CPU is considered a "platform" for use in + smartphones, tablets, and smartbook devices. Krait has many + similarities with the ARM Cortex-A15 CPU and is also based on + the ARMv7 instruction set. These peripherals are working:
+ +Get MMC driver working. May need more help from + experts.
+現在サポートされているブランチの分類および保守終了予定日は、次のとおりです。 保守終了予定日 の列には、 - そのブランチに対応する最も早い保守終了予定日が記入されています。ただし、 - これらの予定日は延長される可能性があること、また、そうするにふさわしい理由があれば、 - ブランチの保守が記載されている日付よりも早く終了する可能性もあるということにご注意ください。
+ そのブランチもしくはリリースの最も早い保守終了予定日が記入されています。 + ただし、そうするにふさわしい理由があれば、 + これらの予定日は延長される可能性があるということにご注意ください。As of the end of Q3, the ports tree holds a bit more than + 24,000 ports, and the PR count is below 1,400. Despite the + summer holidays the tree saw sustained activity with more than + 9,000 commits and almost 2,000 ports PRs closed!
+ +In Q3, five new developers were granted a ports commit bit. + None were taken in for safekeeping.
+ +On the management side, tabthorpe@ decided to step down from + his portmgr duties in July. No other changes were made to the + team during Q3.
+ +This quarter also saw the release of the third quarterly + branch, namely 2014Q3.
+ +On the QA side, 34 exp-runs were performed to validate + sensitive updates or cleanups.
+ +Last, the 20th anniversary of the ports tree was commemorated + during Q3 and a video was published for this event.
+ + +Tremendous work was done on the PR front in Q3 and we would + be very pleased to see committers dedicate themselves to + closing as many as possible in Q4 as well.
+"Parole de Tux" is a Belgian monthly podcast which talks about + news and technical topics regarding Free and Open Source + Software. For the first time, this episode is dedicated to + &os;. The guest, a &os; developer, sums up the history of the + BSDs and their differences. He then briefly explains similarities + and differences between a typical Linux distribution and &os; + before moving on to the main topic: the graphics stack, and how + &os; performs in this area.
+The fisrt RC build for the &os; 10.1 release cycle +
The first RC build for the &os; 10.1 release cycle
is now available. ISO images for the amd64, armv6, i386,
ia64, powerpc, powerpc64 and sparc64 architectures are available
From owner-svn-doc-head@FreeBSD.ORG Thu Oct 9 22:37:50 2014
Return-Path: I have written SSE/AVX-optimized versions of a few libc
+ I have written SSE/AVX-optimized versions of a few libc
routines for amd64. So far the list includes memcpy,
memset, and strlen. For each routine I have
written a simple regression test as well as performed some
@@ -1049,7 +1049,7 @@
memset have proven trickier as different variants can
behave quite differently on different CPUs. At present, I do not yet have a patch relative to libc. Once
+ At present, I do not yet have a patch relative to libc. Once
I do, this will be suitable for more testing. I'd like to see
some real-world benchmarks that show measurable improvement
before pushing any of this up into the tree. Create a branch that holds a modified libc and is suitable
+ Create a branch that holds a modified libc and is suitable
for testing SDIO is an interface designed as an extension of the existing
+ SD card standard, allowing connection of different peripherals
+ to the host with the standard SD controller. Peripherals
+ currently sold in the general market include WLAN/BT modules,
+ cameras, fingerprint readers, and barcode scanners. SDIO is
+ also used to connect some peripherals in products like
+ Chromebooks and Wandboard. The current main focus of the project is to reimplement the
+ existing MMC/SD stack using the CAM framework. This will
+ allow utilizing the well-tested CAM locking model and debug
+ features. The first version of the code was uploaded on Phabricator for
+ review. The new stack is able to attach to the SD card and
+ bring it to an operational state. The only supported SD
+ controller driver is ti_sdhci which is used by the
+ BeagleBone Black. Modifying other SDHCI-compliant drivers
+ should not be a hard task. At this point, feedback from kernel developers is really
+ needed. This may be done in the form of code review. If
+ the chosen way of implementing the CAM-aware MMC stack is
+ considered correct, then adding code for interacting with SD
+ cards (for example, setting the optimal transfer rates) will
+ be the next task. Write a CAM peripheral driver that implements an interface
+ to the FreeBSD disk(9). It will send MMC I/O
+ commands using the MMC XPT layer. Extending camcontrol(8) to make it possible to
+ send MMC-specific commands directly to the MMC/SD card using
+ pass(4) will greatly assist in developing new features for
+ the stack. Modify the sdhci(4) driver to work with the new
+ stack. This is required to work on the new stack using PC
+ hardware, not only the BeagleBone Black. Deficiencies in the current automounter, amd(8), are a
- recurring problem reported by many &os; users. A new
+ Deficiencies in the current automounter, amd(8), are
+ a recurring problem reported by many &os; users. A new
automounter is being developed to address these concerns. The automounter is a cleanroom implementation of
@@ -116,10 +116,10 @@
integrate with the Lightweight Directory Access Protocol
(LDAP) service. The code is ready to use - it has been committed to 11-CURRENT
- and 10-STABLE, and will ship as part of 10.1-RELEASE. There
- is ongoing work on improving performance and fixing possible
- bugs. The code is ready to use - it has been committed to
+ 11-CURRENT and 10-STABLE, and will ship as part of
+ 10.1-RELEASE. There is ongoing work on improving performance
+ and fixing possible bugs. I have written SSE/AVX-optimized versions of a few libc
- routines for amd64. So far the list includes memcpy,
- memset, and strlen. For each routine I have
- written a simple regression test as well as performed some
- simple microbenchmarks on various AMD and Intel CPUs. I have written SSE/AVX-optimized versions of a few
+ libc routines for amd64. So far the list includes
+ memcpy, memset, and strlen. For
+ each routine I have written a simple regression test as well
+ as performed some simple microbenchmarks on various AMD and
+ Intel CPUs. The simplest routine is strlen which appears to be a
general win in microbenchmarks. memcpy and
memset have proven trickier as different variants can
behave quite differently on different CPUs. At present, I do not yet have a patch relative to libc. Once
- I do, this will be suitable for more testing. I'd like to see
- some real-world benchmarks that show measurable improvement
- before pushing any of this up into the tree. At present, I do not yet have a patch relative to
+ libc. Once I do, this will be suitable for more
+ testing. I'd like to see some real-world benchmarks that show
+ measurable improvement before pushing any of this up into the
+ tree. Create a branch that holds a modified libc and is suitable
- for testing Create a branch that holds a modified libc and is
+ suitable for testing
On the management side, tabthorpe@ decided to step down from - his portmgr duties in July. No other changes were made to the + his portmgr duties in July. No other changes were made to the team during Q3.
This quarter also saw the release of the third quarterly
From owner-svn-doc-head@FreeBSD.ORG Fri Oct 10 00:54:38 2014
Return-Path: We have moved from just being able to produce packages to
+ providing a stable repo of packages for ARMv6. ports-mgmt/poudriere-devel is still the current
+ method for building packages. See previous status report for
+ explanations and details on methods.
bhyve is a hypervisor that runs on the FreeBSD/amd64 + platform. At present, it runs FreeBSD (8.x or later), Linux + i386/x64, OpenBSD i386/amd64, and NetBSD/amd64 guests. + Current development is focused on enabling additional guest + operating systems, and implementing features found in other + hypervisors.
+ +A significant amount of progress has been made since the last + status report. Most importantly, all of this work has been + MFCed to the 10-STABLE branch and will be included in the 10.1 + release.
+ +Support for AMD processors is being developed in the + bhyve_svm SVN project branch. The branch is almost + at feature-parity with mainline Intel VT-x support, and will + be committed into -CURRENT in the near future.
+ +New features added this quarter:
+ +Improve documentation
+CSM BIOS boot support for non UEFI-aware guests
+Add support for virtio-scsi
+Improve virtio-net, add offload features, support multiple + queues
+Implement Intel 82580 and e1000 NIC emulation
+Netmap support
+Flexible networking backend: wanproxy, vhost-net
+Move to a single process model, instead of + bhyveload and bhyve
+Support running bhyve as non-root
+Add filters for popular VM file formats (VMDK, VHD, + QCOW2)
+Implement an abstraction layer for video (no X11 or SDL in + base system)
+Support for VNC as a video output
+Suspend/resume support
+Live Migration
+Nested VT-x support (bhyve in bhyve)
+Support for other architectures (ARM, MIPS, PPC)
+linux-からはじまる名前を持ちます。 - この章では、&linux; アプリケーションをインストールする前に - &linux; バイナリ互換機能が有効であることを前提としています。
The KDE on &os; team focuses on packaging and making sure the + experience of KDE and Qt on &os; is as good as possible.
+ +First of all, we are happy to announce that Alonso Schaich, + longtime contributor to our experimental area51 repositories, + has become a ports committer, mentored by KDE on &os; members + Raphael Kubo da Costa (rakuco@) and Max Brazhnikov + (makc@).
+ +During this quarter, the team has kept most of the KDE and Qt + ports up-to-date, working on the following releases:
+ +Additionally, work on updating the Qt5 ports to the 5.3 + series has begun, and we intend to commit the updated ports in + our experimental area51 repository to the ports tree in + Q4.
+ + +Updating out-of-date ports, see the Links Portscout entry + for a list.
+Committing all the updated ports we have been accumulating + in our experimental repositories into the ports tree.
+The project adds support for AES-GCM and AES-CTR mode to the - OpenCrypto framework. Both software and AES-NI accelerated - versions are functional and working. Ermal Lu巽i (eri@) is - working on adding support for the additional modes to - IPsec.
+The project adds support for the AES-GCM and AES-CTR cryptography + modes to the OpenCrypto framework. + Both software and AES-NI accelerated versions are now functional and + working. + Ermal Lu巽i (eri@) is working on adding support for these additional + modes to IPsec.
The Unified Extensible Firmware Interface (UEFI) provides + boot- and run-time services for x86 and other computers. For + the x86 architecture it replaces the legacy BIOS. This + project will adapt the &os; loader and kernel boot process for + compatibility with UEFI firmware, found on contemporary + servers, desktops, and laptops.
+ +Over the last three months Ed and others refined the existing + UEFI support, and merged it to the stable/10 branch for the + upcoming FreeBSD 10.1 release.
+ +To avoid the risk of a regression, the standard FreeBSD 10.1 + install images continue to use the existing partitioning scheme + and support only legacy BIOS boot. Separate UEFI-enabled + installer images will be included with 10.1.
+
+
The Unified Extensible Firmware Interface (UEFI) provides - boot- and run-time services for x86 and other computers. For - the x86 architecture it replaces the legacy BIOS. This - project will adapt the &os; loader and kernel boot process for - compatibility with UEFI firmware, found on contemporary - servers, desktops, and laptops.
- -Ed and Nathan completed a number of integration tasks over - the past three months. Nathan added a first-stage loader, - boot1.efi, to support chain-loading the rest of the system - from a UFS filesystem. This allows the UEFI boot process to - proceed in a similar fashion as with BIOS boot. Nathan also - added UEFI support to the &os; installer and release image - creation script.
- -The EFI framebuffer requires the vt(4) system - console — a framebuffer driver is not implemented for - the legacy syscons(4) console. Ed added automatic - vt(4) selection to the UEFI boot path.
- -Snapshots are now built as dual-mode images, and should boot - via both BIOS and UEFI. Our plan is to merge the UEFI and - vt(4) work to stable/10 to appear in &os; - 10.1-RELEASE.
- - -To avoid the risk of a regression, the standard FreeBSD 10.1 install images continue to use the existing partitioning scheme and support only legacy BIOS boot. Separate UEFI-enabled - installer images will be included with 10.1.
+ installer images will be included with 10.1.
The &os; Foundation worked with enterprise and university users + to test the new automounter in existing LDAP-based environments, + including some with thousands of map entries.
+The code is ready to use - it has been committed to
11-CURRENT and 10-STABLE, and will ship as part of
10.1-RELEASE. There is ongoing work on improving performance
From owner-svn-doc-head@FreeBSD.ORG Fri Oct 10 20:43:06 2014
Return-Path: Arm64 is the name of the in-progress port of &os; to the
+ ARMv8 CPU when it is in AArch64 mode. Until recently, all ARM
+ CPU designs were 32-bit only. With the introduction of the
+ ARMv8 architecture, ARM has added a new 64-bit mode. This new
+ mode has been named AArch64. Since the last status report, &os; has started to execute
+ userland instructions. This includes implementing more of the
+ needed kernel functions to handle creation of processes.
+ Using clang to compile userland has found a few issues with
+ the version in the base system. These issues are expected to
+ be resolved when clang 3.5 is imported. Initial support for device drivers has been added. This
+ includes the start of the bus_space functions and
+ interrupt handling. This allowed the existing timer and
+ interrupt controller drivers from armv6 to be used as these
+ devices are similar. The FDT data is now being passed from
+ the loader to the kernel using the standard mechanism. The pmap implementation has been changed to be based on the
+ amd64 code. This fixes a number of issues with the old
+ implementation. Boot to multi-user mode Get dynamic libraries working Test on real hardware The Unified Extensible Firmware Interface (UEFI) provides
+ boot- and run-time services for x86 and other computers. For
+ the x86 architecture it replaces the legacy BIOS. This
+ project will adapt the &os; loader and kernel boot process for
+ compatibility with UEFI firmware, found on contemporary
+ servers, desktops, and laptops. Ed and Nathan completed a number of integration tasks over
+ the past three months. Nathan added a first-stage loader,
+ boot1.efi, to support chain-loading the rest of the system
+ from a UFS filesystem. This allows the UEFI boot process to
+ proceed in a similar fashion as with BIOS boot. Nathan also
+ added UEFI support to the &os; installer and release image
+ creation script. The EFI framebuffer requires the vt(4) system
+ console — a framebuffer driver is not implemented for
+ the legacy syscons(4) console. Ed added automatic
+ vt(4) selection to the UEFI boot path. Snapshots are now built as dual-mode images, and should boot
+ via both BIOS and UEFI. Our plan is to merge the UEFI and
+ vt(4) work to stable/10 to appear in &os;
+ 10.1-RELEASE. The Unified Extensible Firmware Interface (UEFI) provides
- boot- and run-time services for x86 and other computers. For
- the x86 architecture it replaces the legacy BIOS. This
- project will adapt the &os; loader and kernel boot process for
- compatibility with UEFI firmware, found on contemporary
- servers, desktops, and laptops. Over the last three months Ed and others refined the existing
- UEFI support, and merged it to the stable/10 branch for the
- upcoming FreeBSD 10.1 release. To avoid the risk of a regression, the standard FreeBSD 10.1
- install images continue to use the existing partitioning scheme
- and support only legacy BIOS boot. Separate UEFI-enabled
- installer images will be included with 10.1. The Unified Extensible Firmware Interface, or UEFI, provides
+ boot- and run-time services for x86 and other computers. For
+ the x86 architecture it replaces the legacy BIOS. This
+ project will adapt the &os; loader and kernel boot process for
+ compatibility with UEFI firmware, found on contemporary
+ servers, desktops, and laptops. Over the last three months Ed and others refined the existing
+ UEFI support and merged it to the stable/10 branch for the
+ upcoming &os; 10.1 release. To avoid the risk of a regression, the standard &os; 10.1
+ install images continue to use the existing partitioning
+ scheme and support only legacy BIOS boot. Separate
+ UEFI-enabled installer images will be included with 10.1. Document manual installation, including dual-boot
+ configurations. Implement boot1.efi for ZFS file systems. Add support for UEFI variables stored in non-volatile
+ memory (NVRAM). Debug boot failures with certain UEFI firmware
+ implementations. Support secure boot. LLDB is the debugger project associated with Clang/LLVM. It
+ supports the Mac OS X, Linux, and &os; platforms, with Windows
+ support under development. It builds on existing components
+ in the larger LLVM project, for example using Clang's
+ expression parser and LLVM's disassembler. Work over the last three months consisted mainly of
+ maintenance, ensuring that the upstream &os; port continues to
+ build and that testsuite failures are promptly addressed. I plan to import a new LLDB snapshot after the base system
+ Clang is updated to 3.5. Some upstream improvements that will
+ be in that import include: A proof-of-concept implementation of kernel debugging support
+ for amd64 was completed as part of Google Summer of Code. It
+ is not ready to be committed, but will form the basis for
+ upcoming kernel debugging support. Port remote debug stub (lldb-gdbserver) from Linux to
+ FreeBSD. Add support for local and core file kernel debugging. Implement, fix or test support on all non-amd64
+ architectures. Verify cross-debugging. Investigate and fix test suite failures. Package LLDB as a port. Enable by default in the base system for working
+ architectures. The vt(4) (aka Newcons) project provides
+ a replacement for the legacy syscons system console.
+ It brings a number of improvements, including better
+ integration with graphics modes and broader character set
+ support. A large number of improvements were committed to
+ vt(4) over the last three months.
+ Jean-Sébastien Pédron fixed significant
+ performance regressions observed with vt_vga,
+ particularly noticeable on virtual machines. Stefan Esser
+ converted and cleaned up all of the keyboard map files for use
+ with vt(4). The EFI framebuffer driver and the ofwfb driver now works
+ with the xf86-video-scfb X11 video driver, supporting
+ native-resolution (albeit unaccelerated) X. The fixes and improvements have all been merged and will be
+ available in the upcoming &os; 10.1 release. Implement the remaining features supported by
+ vidcontrol(1). Write manual pages for vt(4) drivers and kernel
+ interfaces. Support direct handling of keyboard by the kbd
+ device (without kbdmux(4)). CJK fonts. This is in progress. Switch to vt(4) by default. Implement compatibility mode to be able to use single-byte
+ charsets/key-codes in vt(4).
+ The project to update the Intel graphics chipset driver
+ (i915kms) to a recent snapshot of the Linux upstream code
+ continues. A patch with a large chunk of updates has been
+ made available to check for regressions against current
+ functionality, but is not yet expected to provide fully
+ functional new functionality. The GEM I/O ioctl code path
+ has been modified to more closely resemble the Linux code
+ structure (easing future imports).
+ Debian GNU/kFreeBSD is a software distribution produced by
+ Debian, based on the kernel of &os; (instead of Linux) and GNU
+ libc. Around 90% of Debian's software archive has now been
+ ported to it, for amd64 and i386 architectures. It was first
+ released with Debian "squeeze" as a development preview in
+ 2011, featured again in the "wheezy" release, and hopes to be
+ part of the official Debian "jessie" release early 2015. In 2003 there were several attempts to bootstrap a minimal
+ Debian system upon &os; or NetBSD kernels, some also trying to
+ use the native BSD libc. The most successful and
+ longest-lived of these was a "GNU/FreeBSD" chroot bootstrapped
+ by Robert Millan with the GNU libc that most of Debian's core
+ packages were designed to work with. The "k" was later added
+ to the name to reflect that it takes just the kernel from
+ &os;, with most everything else from the Debian archive. We
+ do also package some FreeBSD utilities as needed to boot it
+ and take advantage of certain features. &os; support within GNU libc is now mostly maintained by Petr
+ Salinger, who recently converted it from an older threading
+ implementation based on LinuxThreads to NPTL which is much
+ more compatible with the software we run. We have the GNU
+ compiler toolchain as well as Clang 3.4; Perl, Python and
+ Ruby; and OpenJDK 7, based the on work done in &os;'s own
+ ports collection. We use linprocfs for /proc because
+ much of Debian GNU software expects this. The Linuxulator
+ is not needed at all, but could make for interesting future
+ uses. Porting work mostly focuses now on individual packages'
+ build systems, on preprocessor #ifdefs that do not clearly
+ distinguish between kernel and libc, or fixing testsuites'
+ presumptions of Linux-specific behaviour. In the course of
+ this, we even found the odd &os; kernel bug, including
+ EN-14:06 / CVE-2014-3880. GNU/kFreeBSD has already seen production use, mostly on
+ webservers, email servers and file servers; one such machine
+ has 475 days' uptime receiving around 10,000 emails per day.
+ It has become increasingly practical for desktop/laptop uses
+ thanks largely to new features coming in from &os; 10.1. KMS graphics mean that 3D gaming and high-definition video
+ playback perform brilliantly. We have great support for Intel
+ graphics chipsets, but only an older nvidia Xorg driver. For
+ radeonkms, Robert Millan was able to add firmware-loading
+ support so that non-free binary blobs can be packaged
+ separately, outside of Debian's main archive. Proprietary
+ drivers are not useful to us as they would need to be rebuilt
+ from source to port them. vt(4) was necessary for KMS to not break VT
+ switching. But it has also improved the console's handling of
+ non-ASCII character sets and we do look forward to having
+ console fonts for non-Latin script. We have supported ZFS for some time, even as a root/boot
+ filesystem (using GRUB 2; Robert Millan added the ZFS support
+ which now &os; itself is able to benefit from). Enhancements
+ coming from OpenZFS, especially LZ4 compression, in
+ combination with better memory management and GEOM
+ improvements, mean that "jessie" should see a noticeable
+ performance boost. debian-installer already allows for pre-seeded, unattended
+ installs and there are PXE-bootable install images
+ available. virtio drivers are new to the "jessie" release, enabling
+ support for some public clouds. We are now compiling Xen domU
+ and PVHVM support into our standard kernel builds. We already have userland tools to configure the PF firewall.
+ As an experimenting, we are compiling in IPSEC support by
+ default for the upcoming release, and would like to see it put
+ to good use against present-day privacy and security
+ threats. We try to support uses of Debian GNU/kFreeBSD inside a jail
+ on a &os; host system, and hopefully vice-versa. Some of the
+ jail utilities are not yet packaged, but we have documentation
+ on the Debian Wiki on how to set up jails on "wheezy", which
+ are fully functional. The init system we currently use is a parallel System V-style
+ init, although Debian GNU/Linux will be switching away from
+ that to systemd. For the next release we may switch to
+ OpenRC, which is mostly ported already. Not having systemd or udev, means that we will be unable to
+ support GNOME 3.14 in the upcoming release. We have very good
+ support for XFCE, also have KDE, LXDE and the
+ recently-packaged MATE desktop environment. The Debian
+ software archive provides many alternative window managers for
+ Xorg such as IceWM, dozens of terminal emulators, and so
+ on. As we approach the freeze of the Debian "jessie" release,
+ we would love for anyone to test GNU/kFreeBSD, try to use it
+ for whatever would be useful to you, and let us know what
+ issues you run into. Ask for help on our project mailing list
+ or IRC channel, and let us know of any bugs you find. We
+ still have time to fix problems before release, and we would
+ be happy to improve our documentation any time. At present, I do not yet have a patch relative to
libc. Once I do, this will be suitable for more
- testing. I'd like to see some real-world benchmarks that show
+ testing. I would like to see some real-world benchmarks that show
measurable improvement before pushing any of this up into the
tree.
+
+
+
CAM Target Layer (CTL), used as base for the kernel iSCSI + server, got support for VMWare VAAI and Microsoft ODX + storage acceleration. It permits avoiding network + bottlenecks and improved storage efficiency on sets of large + operations, such as virtual machine (or large file) creation, + initialization to zeros, copy, delete, etc..
+ +VMWare VAAI includes support for these primitives/SCSI + commands: Atomic Test and Set (ATS) — COMPARE AND + WRITE command; Extended Copy (Clone) — SPC-3 subset + of XCOPY commands; Write Same (Zero) — set of WRITE + SAME commands; Dead Space Reclamation (Delete) &mdash UNMAP + command.
+ +Microsoft ODX includes support for these SCSI commands: + POPULATE TOKEN/WRITE USING TOKEN (SPC-4 extensions of + XCOPY), WRITE SAME and UNMAP.
+ +All XCOPY operations are currently limited to one storage host. + ODX operations are currently limited only to iSCSI disks. + Accelerated inter-host copying or copying to/from files on + Samba shares is not implemented and handled by initiators in + the legacy way.
+ +The code is committed to FreeBSD head and stable/10 branches, + and will be present in FreeBSD 10.1 and FreeNAS 9.2.1.8 / + 9.3 releases.
+ + +Full support for thin provisioning, including capacity + usage reporting and thresholds notifications.
+Inter-host XCOPY operations.
+Microsoft ODX includes support for these SCSI commands:
From owner-svn-doc-head@FreeBSD.ORG Sat Oct 11 01:49:34 2014
Return-Path: Add FreeBSD kernel support for Xen Paravirtualised kernels.
+ This project has finally reached a "Proof of Concept" stage
+ on the branch
+
+ projects/amd64_xen_pv Testing and bug reports on various configurations is
+ encouraged! The author is also seeking bounties to help
+ complete the effort and assess potential interest. Please
+ send email if interested. PV kernels are still supported by most cloud providers for a
+ range of configurations, although they are expected to be
+ phased out in the future. Large page support SMP support Debug and cleanup Security vetting Performance tweaks Address Space Layout Randomization (ASLR) is a computer
+ security technique that aids in mitigating low-level
+ vulnerabilities such as buffer overflows. In order to
+ prevent an attacker from knowing where a given
+ exploitable vulnerability lies in memory, ASLR randomizes
+ the memory layout of running applications. FreeBSD lacks behind the industry in exploit mitigation
+ technologies. ASLR is a great first step in implementing
+ such technologies. Future exploit mitigation technologies
+ will rely on ASLR. A lot has happened in the last few months. Shawn Webb gave
+ presentations at both BSDCan 2014 and EuroBSDCon 2014. The
+ presentations were met with a lot of support and backing.
+ At the end of EuroBSDCon, an awesome developer named Ilya
+ Bakulin fixed our ARM bug. Shawn Webb and Oliver Pinter
+ have submitted our patch to Phabricator, FreeBSD's new
+ code review utility. Shawn Webb added an API for allowing
+ a debugger to disable ASLR in order to support
+ deterministic debugging with applications such as lldb or
+ gdb. Oliver Pinter enhanced the performance of our ASLR
+ implementation. A package building exp-run was ran and came
+ out favorably in terms of performance. Shawn Webb bumped up
+ the maximum number of bits allowed to be randomized to 20
+ and set the default to 14. To aid in the upstreaming process of the ASLR project and
+ other security-related projects, Shan Webb and Oliver Pinter
+ founded The HardenedBSD project. It exists primarily to
+ serve as a staging area for bleeding-edge development of
+ security-related projects for FreeBSD prior to being merged
+ upstream. Get more people testing and reviewing our patch Run more performance tests Figure out why the two ports failed in the EXP-RUN.
+ Involve the port maintainers. Test on different architectures (we need help with this)
To aid in the upstreaming process of the ASLR project and
- other security-related projects, Shan Webb and Oliver Pinter
+ other security-related projects, Shawn Webb and Oliver Pinter
founded The HardenedBSD project. It exists primarily to
serve as a staging area for bleeding-edge development of
security-related projects for FreeBSD prior to being merged
From owner-svn-doc-head@FreeBSD.ORG Sat Oct 11 03:42:58 2014
Return-Path: &os; packages for the Tier-1 i386 and amd64 CPU architectures
+ are built by a single very high-performance machine. Other
+ architectures lack equivalent hardware, and we began
+ experimenting with QEMU's user-mode emulation to cross-build
+ packages from an amd64 builder. We have moved from just being able to produce packages to
providing a stable repo of packages for ARMv6. Port remote debug stub (lldb-gdbserver) from Linux to
- FreeBSD.
&os; support within GNU libc is now mostly maintained by Petr @@ -2024,8 +2024,8 @@ Samba shares is not implemented and handled by initiators in the legacy way.
-The code is committed to FreeBSD head and stable/10 branches, - and will be present in FreeBSD 10.1 and FreeNAS 9.2.1.8 / +
The code is committed to &os; head and stable/10 branches, + and will be present in &os; 10.1 and FreeNAS 9.2.1.8 / 9.3 releases.
@@ -2062,7 +2062,7 @@ -Add FreeBSD kernel support for Xen Paravirtualised kernels. +
Add &os; kernel support for Xen Paravirtualised kernels. This project has finally reached a "Proof of Concept" stage on the branch @@ -2139,7 +2139,7 @@ exploitable vulnerability lies in memory, ASLR randomizes the memory layout of running applications.
-FreeBSD lacks behind the industry in exploit mitigation +
&os; lacks behind the industry in exploit mitigation technologies. ASLR is a great first step in implementing such technologies. Future exploit mitigation technologies will rely on ASLR.
@@ -2149,7 +2149,7 @@ presentations were met with a lot of support and backing. At the end of EuroBSDCon, an awesome developer named Ilya Bakulin fixed our ARM bug. Shawn Webb and Oliver Pinter - have submitted our patch to Phabricator, FreeBSD's new + have submitted our patch to Phabricator, &os;'s new code review utility. Shawn Webb added an API for allowing a debugger to disable ASLR in order to support deterministic debugging with applications such as lldb or @@ -2163,7 +2163,7 @@ other security-related projects, Shawn Webb and Oliver Pinter founded The HardenedBSD project. It exists primarily to serve as a staging area for bleeding-edge development of - security-related projects for FreeBSD prior to being merged + security-related projects for &os; prior to being merged upstream. From owner-svn-doc-head@FreeBSD.ORG Sat Oct 11 03:50:55 2014 Return-Path:The project to update the Intel graphics chipset driver (i915kms) to a recent snapshot of the Linux upstream code - continues. A patch with a large chunk of updates has been + continues. A patch with a large chunk of updates has been made available to check for regressions against current functionality, but is not yet expected to provide fully functional new functionality. The GEM I/O ioctl code path @@ -2038,6 +2038,7 @@
Full support for thin provisioning, including capacity usage reporting and thresholds notifications.
Inter-host XCOPY operations.
Large page support
SMP support
Debug and cleanup
Security vetting
Performance tweaks
Address Space Layout Randomization (ASLR) is a computer security technique that aids in mitigating low-level - vulnerabilities such as buffer overflows. In order to + vulnerabilities such as buffer overflows. In order to prevent an attacker from knowing where a given exploitable vulnerability lies in memory, ASLR randomizes the memory layout of running applications.
&os; lacks behind the industry in exploit mitigation - technologies. ASLR is a great first step in implementing - such technologies. Future exploit mitigation technologies + technologies. ASLR is a great first step in implementing + such technologies. Future exploit mitigation technologies will rely on ASLR.
-A lot has happened in the last few months. Shawn Webb gave +
A lot has happened in the last few months. Shawn Webb gave presentations at both BSDCan 2014 and EuroBSDCon 2014. The presentations were met with a lot of support and backing. At the end of EuroBSDCon, an awesome developer named Ilya - Bakulin fixed our ARM bug. Shawn Webb and Oliver Pinter + Bakulin fixed our ARM bug. Shawn Webb and Oliver Pinter have submitted our patch to Phabricator, &os;'s new - code review utility. Shawn Webb added an API for allowing + code review utility. Shawn Webb added an API for allowing a debugger to disable ASLR in order to support deterministic debugging with applications such as lldb or - gdb. Oliver Pinter enhanced the performance of our ASLR - implementation. A package building exp-run was ran and came - out favorably in terms of performance. Shawn Webb bumped up + gdb. Oliver Pinter enhanced the performance of our ASLR + implementation. A package building exp-run was ran and came + out favorably in terms of performance. Shawn Webb bumped up the maximum number of bits allowed to be randomized to 20 and set the default to 14.
To aid in the upstreaming process of the ASLR project and other security-related projects, Shawn Webb and Oliver Pinter - founded The HardenedBSD project. It exists primarily to + founded The HardenedBSD project. It exists primarily to serve as a staging area for bleeding-edge development of security-related projects for &os; prior to being merged upstream.
@@ -2174,15 +2179,19 @@Get more people testing and reviewing our patch
Run more performance tests
Figure out why the two ports failed in the EXP-RUN. Involve the port maintainers.
Test on different architectures (we need help with this)
+Test on different architectures (we need help with + this)
From owner-svn-doc-head@FreeBSD.ORG Sat Oct 11 04:03:43 2014
Return-Path:
ezjail is a very popular jails management utility, + but was only mentioned in passing in the Handbook. This new + section describes basic setup and usage. An in-depth example + shows how to create and configure a jail. It also serves as + an example of how to run a simple caching-only BIND in a + jail.
+ +